[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

1727.0. "Community names for SLOTS after reset" by KEIKI::WHITE () Mon Nov 28 1994 18:03

    
    	Customer has a DB900MX in a DEChub900, they wanted to hook up their
    Netware Server to the FDDI front panel A/B ports, they have a DAS DEFEA
    in the Netware Server.
    
    	They purchased a BN24B-03 (only one) and cannot get the green
    lights on either the DEFEA or the DB900MS to stop blinking.
    
    	The only change in blinking occurs when plugging the BN24B-03
    back to back in the DEFEA, then both A/B ports on the DEFEA turn
    solid green, but when they try this in the DB900MX A/B ports
    (verified via hubwatch that both ports 1A dn 1B are set to front panel)
    they green lights keep blinking no matter what they try?
    
    	We were told to order another DB900MX but just wanted to confirm
    the diagnosis.
    
    	FWIW - one gothca we ran into during troubleshooting is if the
    DH900 has a non default community setting, and you factory reset the
    hub, having then to re-add the community setting back in via OBM,
    that a complete power shutdown of the hub is required to propagate
    the per port community addresses. i.e. after setting the community
    to hub1 every SLOT will have hub1 as the community address for that
    slot intead of hub1-x where x = SLOT #. The symtom is AGENT not
    RESPONDING for every hub manageable option until power is reset.
    
    					Bill
T.RTitleUserPersonal
Name		DateLines
1727.1NETCAD::SLAWRENCEMon Nov 28 1994 19:2027
    
    It is correct that if you factory reset the hub, then any configuration
    information including the read/write community must be re-entered.
    
    After changing the community, you must do a 'normal' reset in order to
    propogate the community to the slots, but your example is incorrect:
    
    1) Factory reset hub
    
                             Hub community is now 'public' 
                             Slots are 'public-X'
    
    2) Change hub community to 'foobar'
    
                             Hub community is now 'foobar'
                             Slots are 'public-X'
    
    3) Reset hub manager
    
                             Hub community is now 'foobar'
                             Slots are 'foobar-X'
    
    Note that the 'foobar-X' community for the slot applies _only_ to SNMP
    operations made through the IP address of the hub; if the module has
    its own IP address, then it's community must be set through it's
    console (as the IP address was), and will default to 'public'.
1727.2What happens when I do "2 <CR>"?CGOS01::DMARLOWEHave you been HUBbed lately?Mon Nov 28 1994 20:1917
    
>    2) Change hub community to 'foobar'
>    
>                             Hub community is now 'foobar'
>                             Slots are 'public-X'
>    
>    3) Reset hub manager
>    
>                             Hub community is now 'foobar'
>                             Slots are 'foobar-X'
    
    When you reset the hub manager, you will do a (2) Reset with current
    settings.  What effect will this have on a hub with FDDI, 6 Ethernets
    and 400-500 PC's?  Can this be done during the day and not affect
    the users?

    dave
1727.3NitKEIKI::WHITEMon Nov 28 1994 21:018
    
    	Re .1
    
    	After changing the community from public to hub1 but before I do a
    reset of the hub itself, doing a community manage current shows
    hub1 for all the slots, not public-x.
    
    					Bill
1727.4NETCAD::SLAWRENCEWed Nov 30 1994 16:225
    
    That's exactly the problem - HUBwatch is using hub1, but the modules
    are still using public; that's why you need the reset - to propogate
    the correct (hub1) community.
1727.5And if I do that what happens?CGOS01::DMARLOWEHave you been HUBbed lately?Wed Nov 30 1994 16:496
    Scott,
    
    What is the affect of doing a "Reset with Current Settings" on a
    hub in full production, ie. 1 FDDI/6 Ethernets"?
    
    dave
1727.6NETCAD::SLAWRENCEWed Nov 30 1994 17:1918
    
    A "Reset with Current Settings" on a hub with active backplane channels
    will cause a brief interruption on those channels as the hub
    configures the backplane.
    
    For most connections (repeater - repeater or concentrator -
    concentrator, for example ) it is short enough that few if any end-user
    applications (even LAT :-) will notice.  For bridge backplane
    connections, the bridge sees the port state change and goes back into
    the listen/learn cycle (it can't tell that it was reconnected to the
    same LAN), so the break is at least that long (45 seconds, if I
    remember correctly).
    
    I don't have any measurements of how long the interruption is, and it
    may vary depending on the configuration; probably a nice project in
    there for someone; any volunteers :-) ?
1727.7Hit <CR> and run like hell.CGOS01::DMARLOWEHave you been HUBbed lately?Wed Nov 30 1994 17:3414
    I'll suggest to my customer.  They have 2 switches in the hub, one
    for PE to individual servers and the second one supplies switched
    Ethernet to the floors via a 900FP.  They are supporting 400-500
    PC clients.
    
    I'll ask him if he wants to try a reset during the day and watch
    his reaction.  But maybe he would schedule it over a lunch.  I don't
    want to be there when he does it as the support people already cringe
    everytime I come around.  Personally I think I've been given a bum
    rap.  8^)
    
    Let you know what happens.
    
    dave