Alcatel Carrier Internetworking Solutions 8800 User Manual
Troubleshooting Source Learning
Dshell Troubleshooting
OmniSwitch Troubleshooting Guide
September 2005
page 3-7
Dshell Troubleshooting
The OmniSwitch 6/7/8XXX has a distributed architecture. Source Learning is specific to a NI. Each NI
has a layer 2 pseudo-cam which is which can hold 64K entries. 32K entries are reserved for L2 Source
Addresses which are local to that NI in L2SA table and the rest of 32K entries are reserved for L2 Destina-
tion Addresses which can be from local or remote NI in L2DA table.
has a layer 2 pseudo-cam which is which can hold 64K entries. 32K entries are reserved for L2 Source
Addresses which are local to that NI in L2SA table and the rest of 32K entries are reserved for L2 Destina-
tion Addresses which can be from local or remote NI in L2DA table.
Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel.
Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy
network down time and/or permanent damage to hardware.
Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy
network down time and/or permanent damage to hardware.
If a problem is specific to a NI and the MAC address is not being learned by the switch, then the first step
is to verify from the pseudo-cam of that NI that the MAC address has been learned. There can be a possi-
bility that the NI has learned the MAC but CMM is not reporting that MAC because of IPC messages lost
between the CMM and NI.
is to verify from the pseudo-cam of that NI that the MAC address has been learned. There can be a possi-
bility that the NI has learned the MAC but CMM is not reporting that MAC because of IPC messages lost
between the CMM and NI.
The commands available to troubleshoot this problem are:
slcDumpL2SA: Display all the SA PseudoCAM entries on one slot/slice.
• Format: slcDumpL2SA slot_num, slice_num
slcDumpL2DA: Display all the Destination Address (DA) PseudoCAM entries on one slot/slice.
• Format: slcDumpL2DA slot_num, slice_num
slcLkupL2SA: Display the SA PCAM entries with MAC, VLAN) tuple on a slot/slice, the high 4 bytes of
MAC are MacHi, other 2 bytes are macLo, VLAN non-significant value is 0.
MAC are MacHi, other 2 bytes are macLo, VLAN non-significant value is 0.
Format: slcLkupL2SA slot_num, slice_num, macHi, macLo, vlanId
slcLkupL2DA: Display the DA PCAM entries with (MAC, VLAN} tuple on a slot/slice, the high 4 bytes
of MAC are MacHi, other 2 bytes are macLo, VLAN non-significant value is 0.
of MAC are MacHi, other 2 bytes are macLo, VLAN non-significant value is 0.
• Format: slcLkupL2DA slot_num, slice_num, macHi, macLo, vlanId
Now, if device A connected on slot 8 is unable to communicate to device B in slot 16 then the following
steps can be taken to verify configuration on the NI
steps can be taken to verify configuration on the NI
First look at the source MAC on slot 8 using the command:
Working: [Kernel]->slcDumpL2SA 8,0
Index Mac Address Vlan GlobalPort 4-words content
-------+-------------------+------+-----------+---------------------------------
----
0x371b 00:c0:4f:12:f7:1b 114 250 007200c0 4f12f71b 00000000
0000003a
Total L2 SA entry amount = 1
----
0x371b 00:c0:4f:12:f7:1b 114 250 007200c0 4f12f71b 00000000
0000003a
Total L2 SA entry amount = 1
Look at the source MAC on slot 16:
Working: [Kernel]->slcDumpL2SA 16,0
Index Mac Address Vlan GlobalPort 4-words content
-------+-------------------+------+-----------+---------------------------------
----
0x3538 00:10:a4:b5:b5:38 114 499 00720010 a4b5b538 00000000
----
0x3538 00:10:a4:b5:b5:38 114 499 00720010 a4b5b538 00000000