Conference netcad::hub_mgnt

Unfortunetly, ping isn't a very good test of SNMP manageability.  Some things 
to look for...

(0) If you're running the Network Access Server software, then, yes, slot
    polling in the DECagent 90 can be enabled.

(1) Double check that there is an entry in your agents file for the 
    DECserver 90TL?  If not, then HUBwatch cannot talk to it.  Add it thru
    the Community pull-down, Manage Table option, Add button.

(2) Is the DECserver 90TL's MAC address in your agents file correct?  The
    MAC is used as an index so that HUBwatch can figure out the IP address
    of the DECserver 90TL.  Use the Community pull-down, Manage Table option
    to get to the info in your agents file.  Single-click on the Select box
    for the DECserver, and press the Agent Options button to verify the
    MAC address.  If it's missing or incorrect, add or change it. in the 
    Agent Options window and press OK.

(3) Can you manage it as a stand-alone device?  From the Manage Table window,
    double-click on the DECserver 90TL's record.  You should end up with a
    front-panel view of a single module, containing only your terminal server.
    You should be able to manage it that way without any problems.  If you
    cannot, then...

(4) Is your DECserver 90TL correctly configured for SNMP management?  Either
    connect directly to it or TELNET to it, then:
	$ telnet 16.2.26.1
	Trying...16.2.26.1
	Connected to .
	Escape character is '^]'.

	# (enter the access password here (default is ACCESS))

       Network Access SW V1.0 for DS90TL (BL54-15)
	(c) Copyright 1993, Digital Equipment Corporation - All Rights Reserved
	Please type HELP if you need assistance
	Enter username> xxx
	Local> set priv
	Password> (enter the priv password (default is SYSTEM))
	Local> show snmp
  
	SNMP State:        ENABLED      Authentication Failure:    ENABLED

	Community Name            Address          GET GETNEXT SET TRAP

	PUBLIC                    ANY              ENA  ENA    ENA  DIS

     If:- SNMP state is not enabled 
	- GET, GETNEXT, and SET are not enabled for the community
	- address isn't either ANY or the address of the workstation from 
	  which you're running HUBwatch
	- Community Name doesn't match one of the DECserver 90TL communities
	  in your HUBwatch agents file.
     then it won't work.

If you got through steps 1-4 and didn't see anything funky, then I'd suggest
taking a few weeks vacation (fishing, boating, or hiking are recommended).  
If that's inconvenient, give me a call and I'll see what we can do.

Tom Hood
KINd-of-a-HUBwatch-DECserver-PERson
dtn 226-6776

    re: .1
    That's a great reply!!!!!!!
    You got a laugh out of me for that one.
    
    I'll take the boating vaction please or maybe I just need another beer.
    
    Anyway I had missed point number 2...add the DECserver 90TL ethernet
    address. I added this then deselected and reselected the DECagent
    and it is now working.
    
    thanks for that,
    Mike

I am using HUBwatch for ULTRIX v1.1 and DECagent v1.1. When I display a 16 slot
hub, all modules are shown correctly. However, the command line message
"Slot 12 unreachable" appears. The module in slot 12 is a DECserver 90TL. Other
modules in slots 9-16 (repeaters) can be managed as expected.

If I double click on the DECserver in slot 12 I get a "timed out" window message
and the following messages appear at the command line :

(W) DS90/TL/90M : SNMP Timeout in SUMMARY_B group
(W) DS90/TL/90M : SNMP Timeout in SUPPORT group, ports 1:4
(W) DS90/TL/90M : SNMP Timeout in SUPPORT group, ports 5:8

I have checked the configuration as .1 suggests.

I can manage the DECserver 90TL in standalone mode by selecting it in the Agents
Table, but I don't see the LEDs go green when there is an active session.

If I delete the DECserver from slot 12 of the hub view and add it again, I am 
able to manage it without receiving the warning messages. If I then exit HUBwatch
then rerun HUBwatch for that hub, I am unable to manage the DECserver in slot 12
again!

Any thoughts?

Thanks,

Paul.

Paul,

Your symptoms suggest that HUBwatch cannot get the 90TL's IP address when it
is in the hub.  Triple check that you've got the correct MAC address in your
agents file.  [The DECagent 90 tells HUBwatch the MAC address of the 90TL.
HUBwatch then goes to the agents file to get the IP address of the 90TL.]
If HUBwatch doesn't know the TL's IP address, it cannot manage it.

Also, what rev software are you running in the 90TL?

	Local> SHOW SERVER
	DECserver 90TL V1.1 BL44F-10A  LAT V5.1  ROM 2.0.0  Uptime:  5 21:00:10
 	                    -----
	                    Software rev

-or-
	Network Access SW V1.1 for DS90TL BL55-16  ROM 2.0.0  Uptime:1 19:08:45
	                                  ----
If you've got the Network Access Software (BL55 or grtr), you don't need to 
tell the DECagent 90 anything about the 90TL (but it must still appear in
your agents file!).  If you've got the BL44 stuff, you've got to add the
90TL to the agent THROUGH HUBWATCH, with slot-polling DISABLED.

Tom H
Ex-DECserver person for HUBwatch

Well, I had a closer look at the hubwatch_agents file .....

The 90TL in slot 12 had an entry that was correct,  however

The entry for a 90TL in slot 5 had the same MAC address as slot 12 !!

So I corrected the slot 5 90TL entry, deleted the two modules from the hub then
added the modules back into the hub.

Now it all works OK.

Paul

PS the delay has been due to holiday and not embarrasment 8^)