Conference netcad::hub_mgnt

3825.0. "Add Failed error on DECSwitch 900EF when connecting to a LAN" by KERNEL::CHOPRAA () Thu Aug 29 1996 13:57

Hi,

I have a customer who gets the add failed error message when connecting to a
backplane lan segment.  The dechib 900 configuration is as follows.

Slot 1	Decrepeater 900TM
Slot 2	Decrepeater 90C
Slot 3	DecBrouter 90T2
Slot 4	PortSwitch 900TP
Slot 5 	Decswitch 900EF	 V1.5.2
Slot 6  Decserver 90L+
Slot 7 	Decserver 90L+
Slot 8  Decserver 900TM (running WWENG1 - Non Nas s/w)
Hubwatch V4.1.1; MAM 4.2

There are 5 ethernet lans in addition to the default thinwire.  The Portswitch
in slot 4 has port 6 connected to a lan segment and port 7 connected to the
default thinwire.  The Decswitch 900EF in slot 5 has port 3 connected to the
default thinwire and port 7 connected to a lan segment.  All other modules each
have one connection to the default thinwire.  There are no FDDI 
LANs/connections.

If we try to form any other connections from the Decswitch 900EF to any lan
segments, we get the ADD FAILED error message.

Deleting a LAN and re-trying the ADD still fails with the same error message.

Using the hubwatch trace facility, I see the following

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>> XMT:[SET] to 111.111.111.115 [cr_hub], community=public
>>    Status = NO_ERROR, Id = 841348421, Errindex=0, Varbinds=1
>>>  vb(1) INTEGER:[chasPortSubtypeSelect.7]=[8]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<< RCV:[GET-RESPONSE] from 111.111.111.115 [cr_hub], community=public
<<    Status = NO_ERROR, Id = 841348421, Errindex=0, Varbinds = 1
<<<  vb(1) INTEGER:[chasPortSubtypeSelect.7]=[8]
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>> XMT:[SET] to 111.111.111.115 [cr_hub], community=public
>>    Status = NO_ERROR, Id = 841348422, Errindex=0, Varbinds = 3
>>>  vb(1) INTEGER:[chasConnEntryStatus.7]=[2]
>>>  vb(2) INTEGER:[chasConnSegment.7]=[4]
>>>  vb(3) INTEGER:[chasConnPort.7]=[7]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<<RCV:[GET-RESPONSE] from 111.111.111.115 [cr_hub], community=public
<<   Status=NO_SUCH, id = 841348422, Errindex=1, Varbinds=3
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


Any information would be appreciated.

Anil Chopra                             Tel:  01256-373746 (Direct line)
UK Comms Support                        DTN:  7833-3746
Digital Customer Support Centre         Fax:  01256-841494
Multivendor Customer Services           Internet:  [email protected]

Apparently this problem can occur if the bridge has a 
duplicate IP address assigned to it.

In this case a power cycle of the bridge resolved the 
problem which implies it wasn't a duplicate address 
problem.

Anil