[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

3352.0. "duplicate address DC900MX???" by BERFS4::NORD () Tue Mar 12 1996 02:14


	Good morning, good evening and something between,

	imagin a backplane, a DC900MX and a DS900EF, port A (1) of the DC900MX
	and B of the DS900EF are connected together in the backplane. Two
	systems are connected to port 2 and 3 of the DC900MX. Customer has
	had some problems with his systems, so he connected them to port 5 and
	6 of the DC900MX.

	On the console of the systems he saw "... duplicate address ..."

	Hhhhhmmmm, what's going on, who/which/what is doing this duplicate
	address test, and why is this address in use, even if the system is
	connected to a different port of the DC900MX?

	Is there someone out there, who can explain this problem?

	Greetings from

	Wolfgang Nord
	MCS at Berlin at Germany
T.RTitleUserPersonal
Name
DateLines
3352.1May be a loopGIDDAY::STANISLAUSTue Mar 12 1996 08:2010
    
    	May be the system has an FDDI and an Ethernet controller and is
    running DEcnet Phase IV or Phase V in Phase IV addressing mode. In this
    case if you connect the FDDI controller to the DC900MX and the Ethernet
    controller either directly or indirectly (via a DECrepeater) to the
    DS900EF, then you could see this symptom of duplicate address. The
    system will see it's own AA-00-04-00-XX-YY a DEcnet address via the
    DC900MX/DS900EF loop. The DS900EF will also see side-changes.
    
    Alphonse
3352.2NPSS::WADENetwork Systems SupportFri Mar 15 1996 15:3023
    Wolfgang,
    
    What do you mean by,
    
    "
    On the console of the systems he saw "... duplicate address ..." 
    "?
    
    If you are referring to an error log entry in the MAM -
    
    	"duplicate IP address seen in slot x"
    
    This can be caused by a conflict between MAM and module IP addresses.  
    
    I spent a fex minutes in the lab on this.  I forced a "duplicate IP 
    address seen in slot 7" MAM error log entry by giving my IP services 
    module (module in slot 7) the same address as assigned to the MAM OBM IP 
    address.  
    
    Something to check...
                 
    Bill