[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

912.0. "Can't change IP Services Slot for DH900..." by CSC32::B_GOODWIN (MCI Mission Critical Support Team) Wed Apr 20 1994 11:37

I just installed a DH900 with 4 DR900TM's in it. I setup the IP services on Slot
2. I was able to get the the DH900 from HUBwatch V2 with out any problems. The
customer then decided to change the configuration slightly and move the DR900TM
from slot 2 to slot 5. I changed the IP services slot in the MAM to slot 5, but
I could never reach the MAM from HUBwatch. The HUBwatch station was directly
connected the the DR900TM I was moving. I then did a factory reset of the MAM
and set up the inband address and told it slot 5 again. I still could not reach
the MAM. I finally moved the DR900TM back to slot 2 and reset the MAM to use
slot 2, it all worked fine. Is there some trick to changing slots for the IP
Services? The DH900 was running V2.2.1 firmware. We used an analyzer to look at
the traffic, we could see HUBwatch doing a "get" to the MAM, but it was not
responding.

Another oddity, I was trying to connect the DR900TM in slot 8 to a different
rail thant the thinwire. I would drag the connection "2" down to another
ethernet rail, it would then bounce back to the "no connection" state. I moved
the DR900TM to slot 7, did a refresh I then could connect "2" to the ethernet
rail. I moved the DR900TM back to slot 8, everything then worked fine. I could
connect "2" to a different ethernet rail.

T.R Title User Personal
Name Date Lines

912.1 Same DR900TM? LEVERS::DRAGON Wed Apr 20 1994 12:18 19

T.R	Title	User	Personal Name	Date	Lines
912.1	Same DR900TM?	LEVERS::DRAGON		`Wed Apr 20 1994 12:18`	19
	A couple of things to keep in mind: 1) The HUBwatch system will remember the MAC of the IP Services module in ARP cache. So if you use the same DR900TM, but in a different slot and with the same IP address, you should be ok. If you use a different DR900TM (different MAC) and the same IP address, then you will have to clear the ARP cache, or wait until it gets forgotten, or use another IP address. 2) The HUBwatch system must be on the same LAN as the IP Services module, or have connectivity to it (ie FDDI bridged to Ethernet). It sounds like both of these were OK in your situation, but may want to double check that the customer physically moved the DR900TM from one slot to another and just didn't have 2 DR900TMs. Regards, Bob

    
    A couple of things to keep in mind:
    
    1) The HUBwatch system will remember the MAC of the IP Services module
       in ARP cache. So if you use the same DR900TM, but in a different
       slot and with the same IP address, you should be ok. If you use a
       different DR900TM (different MAC) and the same IP address, then you
       will have to clear the ARP cache, or wait until it gets forgotten,
       or use another IP address.
    
    2) The HUBwatch system must be on the same LAN as the IP Services
       module, or have connectivity to it (ie FDDI bridged to Ethernet).
    
    It sounds like both of these were OK in your situation, but may want
    to double check that the customer physically moved the DR900TM from
    one slot to another and just didn't have 2 DR900TMs.
    
    Regards,
    Bob