[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

4213.0. "ROUTEABOUT CENTRAL,CLEARVISN,NO AGENT SECIFIED" by SIOG::R_TAYLOR (Richard Taylor dtn: 822-4159) Thu Feb 13 1997 15:51

    Hello,
    
    I am trying to install a dechub900 (v4.2) as follows:
    
    slot 8 , in band ip: 16.209.160.243, decswitch 900 EF (v1.5.2)
    
    slot 7, portswitch 900 TP (v2.0)
    
    slot 5, routeabout central ew, ip addr on module 16.209.160.242, (v1.1.003)
    
	
    useing Clearvisn v1.0
    
    can see hub ok but when I click on routeabout get "no agent specified
    for the slot mac address" and then get brouter summary screen, but
    cannot see ports to connect to lan on hub. I have a patch lead going
    from port 1, on routeabout, to portswitch to give connectivity to decswitch.
    
    hw_agents.dat has
    
    16.209.160.243 fkm "public" 5 2 BRIDGE #        
    16.209.160.242 brouter "public" 5 2 00-00-f8-48-cb-2c BROUTER #  
    
    It has been suggested that I need a newer version of clearvisn to
    manage the routeabout but version 1.1 will not release until march and I
    cannot wait!
    
    am I missing something obvious here?
    all slaps on the wrist are welcome!
    
    rgds
    
    Richard

T.R	Title	User	Personal Name	Date	Lines
4213.1		NETCAD::DOODY	Michael Doody	`Fri Feb 14 1997 09:01`	9
	The RA Central takes a long time to "wake up" (minutes). You need to wait until the Hub's LCD says that slot is "Up" before starting / refreshing front panel in hubwatch/clearvisn. Failing that, you could try to reset-to-current-settings on the hub, after the routeabout wakes up. -mike
4213.2		NETCAD::MILLBRANDT	answer mam	`Fri Feb 14 1997 10:21`	11
	Additionally, the system that you are running clearVISN on needs to have connectivity to a front port on the RouteAbout, and the RouteAbout needs an IP address on that interface. This is because none of the Comet-based brouter products support the CSNMP gateway, the means by which the Hub MAM passes management requests from clearVISN through the management backplane to the module. Since clearVISN can't get the info through to the modules via the MAM, it must use a cable connection to the device. Dotsie