[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

2927.0. "Problem with DecSwitch as Ip services module!" by CSC32::YOUNGWIRTH () Mon Oct 30 1995 13:16

    
    	There appears to be a problem when using Hubwatch to manage a HUB
    and access that hub through a DecSwitch 900EF which is the IP services 
    module.
    DecHub Firmware 4.0.1
    DecSwitch 900 EF firmware 1.5
    HubWatch DOS v4.0.1
    
    If they add another DecSwitch 900EF to the hub and access the Hub
    through it they can manage the Hub. 
    
    Am I missing something????
    Is there any fix for this other than getting another module (DRP900TM) 
    to use as the IP services module??
    
    					Thank You
    					Mark Youngwirth
T.RTitleUserPersonal
Name		DateLines
2927.1Get more info on the general health of the 900EF....NETCAD::BATTERSBYMon Oct 30 1995 14:0721
    >> DecHub Firmware 4.0.1
    >> DecSwitch 900 EF firmware 1.5
    >> HubWatch DOS v4.0.1
    
    These revs aren't the very latest revisions. But on the surface
    of things this shouldn't really affect whether the 900EF behaves
    properly as the IP services module in a HUB. Sounds like it must 
    be determined whether the suspect 900EF is really good or bad, so
    perhaps this should be the approach. So some questions are in order. 
    
    - Have you asked if there are any error log entries in the module
      that appears to not be working?
    - Has the customer verified that there is an IP address assigned
      to the non working module?
    - Does the suspect module pass diagnostics (module ok led lit?)
    - Has the suspect module been tried in a different slot in the HUB?
    - Has the customer described the led behavior for you, when asked
      whether a specific port comes up into forwarding, or has the
      customer described for you which leds are on and which are off etc.?
    
    Bob
2927.2Not sure whats happening now!CSC32::YOUNGWIRTHMon Oct 30 1995 16:2351
    
    
    
    
    
    Things have changed! The other answers are below in case you still need
    them.
    
    They upgraded the HUB and the DSW900EF 
        HUB 4.0.1
        DSW900EF 1.5.2
    Now he can be attached to IP services module and make changes to the
    same module in hubwatch.
    
    Butttttt....
    
    Now when they unplug a module they say they are losing the stub
    connections.
    
    I will need to check this out further. This is a Canadian customer 
    so there are some things lost in the translation.
    
    I may just have to have someone on site check it out.
    
    If I need more help I will respond later.
    
    				Thank You
    				Mark Youngwirth
    
    - Have you asked if there are any error log entries in the module
      that appears to not be working?
    NO
    
    - Has the customer verified that there is an IP address assigned
    Yes
    
    - Does the suspect module pass diagnostics (module ok led lit?)
    Yes
    
    - Has the suspect module been tried in a different slot in the HUB?
    Yes, In fact they have put 2 DSW900EFs in the same hub and then
    configured each one while having the other one be the IP services
    module. It does not appear to be slot specific, just whether it is the
    IP services module.
    
    - Has the customer described the led behavior for you, when asked
      whether a specific port comes up into forwarding, or has the
      customer described for you which leds are on and which are off
      etc.?
2927.3NETCAD::DOODYMichael DoodyTue Oct 31 1995 08:585
    That is normal. When you remove a module, it's connections are
    deleted. (Unless they enabled FDDI Auto Healing, and the switch is
    connected to a backplance FDDI ring).
    
    -Mike