[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

2739.0. "PORTswitch 900FP Ethernet group names" by ZPOVC::HWCHOY (On a foul day, you can complain forever.) Tue Sep 12 1995 04:43

    Hi, I've many PORTswitch 900FP where I setup mappings for front-panel
    ports to Ethernet channel groups. In the mapping matrix, I assign names
    to each Ethernet groups (essentially they match up with the backplane
    Ethernet channel names to help reduce confusion). However, I find that
    these names disappear when the module is reset (power cycle or using
    the console to "reset with current"). I have seen this problem on some
    20+ PORTswitch 900FP so it is not a module problem. HUBwatch is v3 and
    v4.
    
    Can someone address this or let me know if they have manage to make the
    names stick. Thanx.
    
    rgds,
    hw
T.RTitleUserPersonal
Name
DateLines
2739.1It's RealNETCAD::DRAGONTue Sep 12 1995 12:5315
    
    Hi,
    
    	What you are seeing is real. The names assigned to the Port Groups
        get cleared on a reset. I think the basic underlying problem is
        that the MIB does not specify that this read-write object is 
        non-volatile. So, a reset clears it. Since there is no reason to
        clear these values and probably every reason to not clear them, 
        on a reset with current settings, it would seem that the MIB should 
        be changed to define this object as non-volatile and as such the
        implementation of it changed. (See pcomConIntLanName).
    
    Just my $.02,
    Bob
    
2739.2Gimme a nameZPOVC::HWCHOYOn a foul day, you can complain forever.Wed Sep 13 1995 14:147
    So who should I contact to have this rectified? I can assure whoever it
    is that when the customer realises what happens they will certainly
    demand a fix. I firmly believe we should fix things before it is
    labeled a BUG.
    
    rgds,
    hw
2739.3more that just mib defsNETCAD::CURRIERThu Sep 14 1995 16:395
    Data that is to survive a power cycle or a reset must be stored in
    NVRAM.   NVRAM is expen$ive.  This is always a factor in deciding what
    data is non-volatile.
    
    
2739.4Another customer seeing this as problemNPSS::LIZOTTENetwork Product SupportTue Oct 15 1996 15:4011
2739.5CSC32::D_PERRINWed Oct 16 1996 15:586
2739.6bogus arrangement in large netsPASAGE::PLUNKETTWed Oct 16 1996 17:473
2739.7Recovery Manager could helpNETCAD::GILLISWed Oct 23 1996 20:4526
2739.8CV2.0 Recovery Manager will back up PORTswitch group namesNETCAD::GILLISFri Nov 01 1996 13:1626
2739.9Muchas graciasPASAGE::PLUNKETTThu Nov 07 1996 12:4710