Conference netcad::hub_mgnt

    Have you set up IP and SNMP on the terminal server? You must
    add an IP address and enable SNMP on the server.
    The approximate commands are:
    
    set priv
    chang inter addr xx.xx.xx.xx
    chang SNMP sets enabled
    init del 0
    
    
    Set either the HUBwatch config and instal guide or on line help
    of the terminal server for exact syntax....
    
    Bruce

RE:.1  All of this has been done!

SNMP has an address set and all SNMP calls have been enabled.

It's the first one that I am suspicious of.....why is HUBwatch telling us that
that the MAC is unknown for this device?

Also what about the discrepancy between what the documentation is saying for
server image name (>SHOW SERVER) and what we are seeing?

    2 things to try...
    first ping the server from UCX, just to double check it is responding
    to IP.
    
    Assuming it pings, bring the server up as a standalone module in
    HUBwatch (ie give HUBwatch the IP address of the server when you
    start HUBwatch.
    
    Bruce

    
    Make sure that the community name for the DECserver is 'PUBLIC' (upper
    case); if it isn't, the terminal server won't pass management
    information to the Hub agent, so HUBwatch can't read it.
    
    'WWENG2' is the correct image; 'MNENG2' is for the DECserver90M or TL.
    

    Did you check to see that the answer you got to the Ping really came
    from the DECserver?
    
    On unix, you would use:
    
       arp 16.100.240.8
    
    and expect to see a routing table entry with the mac address of the
    server...
    

    Give HUBwatch the direct IP address not the IP name. I notice
    a DETMM in your entry from the agents file a DECserver 900TM is
    a DSRVZ I believe. Look at the SNMP counters on the server to make
    sure they are incrementing when HUBwatch trys to talk with it, if
    they don't change SNMP is not enabled.
    
    Bruce

I think part of the confusion may come from what is really supposed to be in 
HUBWATCH_AGENTS.DAT.

The last few lines of our file is as follows:

16.100.240.100 MKO90 "PUBLIC" 5 2 08-00-2B-A3-B7-2A OTHER
16.100.240.15 hub900 "PUBLIC" 60 5 08-00-2b-a3-54-10 AGENT900
16.100.240.3 bridge_1 "public" 60 5 08-00-2b-bb-02-bc
16.100.240.100 mko90 "PUBLIC" 5 2 08-00-2b-a3-b7-2a
16.100.240.5 hub900-5 "PUBLIC" 60 5 08-00-2B-A3-54-10 AGENT900
16.100.240.6 hub900-6 "PUBLIC" 60 5 08-00-2B-A3-90-C8 AGENT900
16.100.240.8 server_1 "PUBLIC" 60 5 08-00-2B-A3-81-6A AGENT900

What is the last field supposed to read....should it be AGENT900 or DETMM or
what?

I've tried running with variations on this file.

If I tried to bring the hub up now with the following command:

	$ WATCH/AGENT/IP=16.100.240.5/COMM="PUBLIC"

It starts, but it displays a blue background with a single 900TM in the first
slot to the left and leaves some of the options unreachable.

If I comment out the last line and the line with hub900-5, it goes as far as:

HUBwatch for OpenVMS VAX, Revision V2.0.1
(I) HUBWATCH$LIBRARY = SYS$LOGIN
(W) Using community PUBLIC
(I) Slot  2:  status = BROKEN
(I) Slot  3:  status = ONLINE
(I) Slot  4:  status = ONLINE
(I) Slot  5:  status = ONLINE
(I) Slot  6:  status = ONLINE
(I) Slot  8:  status = ONLINE

Then hangs!

I am suspect of the connection.....I can ping all of the above ip addresses
from UCX, but the ULTRIX system sitting right next to it is successful only
part of the time.......

ARP's don't work at all to these addresses.

Netview found these addresses, placed them on the map and is able to PING 
and demand poll all devices.

This is becoming stranger by the minute......I keep checking the physical
connectivity just to make sure it is what I think it is......it is!

When it does work, I can get to both DETMM's but not the DECserver900?

I'm stumped!

If I try to connect as suggested to the DECserver900:

	$ WATCH/AGENT/IP=16.100.240.8/COMM="PUBLIC"

The following occurs:


HUBwatch for OpenVMS VAX, Revision V2.0.1
(I) HUBWATCH$LIBRARY = SYS$LOGIN
(W) Current agent not in the agent table
(W) Unresolved agent node IP name
Can not communicate with specified agent

Al

Is that terminal server on-line?  I tried ping-ing it from here, and
could not reach it.

At VMS:
	$ ucx ping 16.100.240.8
You should have lots of ping messages

At the terminal server console:
	Local> set priv
	Password: <whatever...>
	Local> show internet
		You should see both the IP address and subnet mask.
	Local> show snmp
SNMP State:                ENABLED      Authentication Failure:    ENABLED


Community Name                    Address          GET GETNEXT SET TRAP

PUBLIC                            ANY              ENA  ENA    DIS  DIS
 
	If the top line doesn't say SNMP State: ENABLED, then
	Local> change snmp state enable

	If "ANY" doesn't appear in each community row (or if the IP address
	of your workstation isn't there) then
	Local> change snmp community PUBLIC address any

	In the above example, community PUBLIC has GET and GETNEXT enabled,
	but SET is disabled.  This means you'll be able to monitor this device,
	but not change any settings in it.
	To enable the PUBLIC community, use the command
	Local> change snmp comm public get enable
	Local> change snmp comm public getnext enable

	HUBwatch uses GETNEXT, so make sure both GET and GETNEXT are enabled!

	Natch, if you want to be able to do sets on the server, use the 
	same command, but end it with "set enable"

As far as your agents file goes, the device type isn't really all that 
important.  Its main function is user documentation.  But, a DS900 should
say DSTMM in V2.0

This should work.

Tom Hood
HUBwatch

The problem was the address in SNMP.

Just a reminder.  For the DS90TL/90M/900TM the SNMP community address
(which is shown in the SHOW SNMP command in each community row) is the
address from which the server will accept SNMP connections.  If you 
supply an address there, that is the ONLY address which will be allowed
to talk SNMP using that community.  If you specify ANY (the default), that
community will talk SNMP with anyone.

So, if I wanted my workstation SLINK (ip address 16.20.216.35) to be the only
workstation to be able to talk SNMP to my terminal server, I might type:
	Local> change snmp comm public addr 16.20.216.35

If I wanted to allow many management stations, I'd type:
	Local> change snmp comm public addr any

Tom Hood
HUBwatch