[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

2692.0. "HUBwatch 4.0 can't manage DS90M ports" by DRAC::DSMAIL () Wed Aug 30 1995 08:56

    
    
    Hello,
    
    I'm experience problems managing DECserver90M from HUBwatch 4.0
    in a DEChub90.
    
    Actually the DECserver appears on the screen but I can not manage
    the ports, ie: changing the speed or the flow control and so on.
    The modified values are not kept even after the 'save' function.
    
    The DECserver is a flash version with firmware v4.1, hardware v4.0
    and loads the MNENG2 from its flash ...after 5 minutes of decompressing
    the binary.
    
    The DECagent90 has the firmware rev 2.1.3, I know there is a 'bad' 
    rev. 3.0 and the last one 3.0.1 is not yet installed.
    
    Do I upgrade the DECagent or there are some other hint to take care?
    
    Any help will be appreciate.
    
    Jordi Manchon
    Network Services
    Barcelona -SPAIN-

T.R	Title	User	Personal Name	Date	Lines
2692.1		SLINK::HOOD	Maine state bird: The black fly	`Wed Aug 30 1995 12:51`	6
	What happens when you double-click the DECserver bezel? Which platform are you running HUBwatch (Windows or Unix)? Tom Hood
2692.2	Dumb or deaf DS90M ?	DRAC::DSMAIL		`Thu Aug 31 1995 08:47`	12
	When I double click the DECserver I get the 'fligth simulator' screen, then when I double click over a single port and I want to change for instance the speed or the flow control it let me do it, I applied and the when I come back and forth the modified values don't appear modified and I get the old -by default- values. The plattform is Windows. I can manage other modules on the same hub without any problem, DECrepeaters, DECBrouters, PacketProbe etc... Jordi Manchon
2692.3	More questions	SLINK::HOOD	Maine state bird: The black fly	`Thu Aug 31 1995 11:40`	35
	> the when I come back and forth the modified values don't appear > modified and I get the old -by default- values. "Jordi, what do you mean when you type 'come back and forth'"? "Tom, why do you ask that?" "Well, Jordi. If you mean you go look at the server and it hasn't changed, that means one thing. If you mean the HUBwatch screen has flipped the value you changed back to the original value, that means another." "Tom, what does it mean if the server hasn't changed?" "That means you haven't reset the port. Unlike every other kind of hub device, the DECserver maintains two sets of books. There's the 'SET' characteristics, which temporarily modify a parameter until the next port logout, port reset, or server reset. And then there's the 'DEF' characteristics, which are stored in the server's NVRAM, which are invoked after the next port logout, port reset, or server reset. In HUBwatch, (or with any other SNMP tool) you are changing the 'DEF' characteristics." "What if I meant the HUBwatch screen has flipped the value back?" "Then, there's something wrong. Make sure you've got SNMP SETs enabled in the DECserver (although HUBwatch is supposed to give a 'SET Failed' message). Or maybe there's a HUBwatch bug." "I don't know if you answered my question, Tom." "Please let me know how things work out." - Tom Hood Who really, really, really, really, really, really would like to be in Maine right now, getting an early start on the Labor Day holiday weekend.