Highlighted
nonickman
Copper

Naming issue on older M8024 Switches

Hi,

i found an older 8024 switch in an networking environment which shows messages for frequent Spanning Tree issues on a slot i cannot identify.

The log says: "Spanning Tree Topology Change Received: MSTID: 0 Unit: 0 Slot: 3 Port: 1"

But the ports are shown as Te 1/0/1, Te 1/2/4 which i can understand.

Fw is 4.2 ... and i simply do not have a slot 3 ??

 

0 Kudos
3 Replies
Moderator
Moderator

Re: Naming issue on older M8024 Switches

I believe those are the external facing interfaces. What modules are installed on the switch? What devices connect to those modules? The command show interfaces should give you a list of the interfaces for reference.

Daniel Covey
Dell EMC| Enterprise Support Services
Get support on Twitter:@DellCaresPRO
Download our QRL app:iOS, Android, Windows
Dell Networking Resources

0 Kudos
nonickman
Copper

Re: Naming issue on older M8024 Switches

Hi Daniel,

thanks for this info. I found out it is a switch blade ... but i still cannot identify the port:

Any idea ?

###

<189> FEB 08 16:40:26 XXX TRAPMGR[182082304]: traputil.c(636) 18467 %% Spanning Tree Topology Change Received: MSTID: 0 Unit: 0 Slot: 3 Port: 1


RZ2_Blade-Switch1#show interfaces ?

advanced Advanced interface settings
advertise Show the auto negotiation advertisement information.
configuration Interface configuration
cos-queue Display COS Queue Information.
counters Interface counters
description Interface Description.
detail Interface Detail.
loopback Display the configured Loopback interface information.
mtu Display the configured on interface MTU size.
port-channel Display port-channel configuration information.
random-detect Display Weighted Random Early Discard (WRED)
Information.
status Interface status
switchport Display statistics for the entire switch.
tunnel Display the configured Tunnel interface information.

 


RZ2_Blade-Switch1#show interfaces status

Port Name Duplex Speed Neg Link Flow Control
State Status
--------- ------------------------- ------ ------- ---- ------ ------------
Te1/0/1 DUSP1rc2-ETH2 Full 10000 Auto Up Active
Te1/0/2 DUSP1rc4-ETH2 Full 10000 Auto Up Active
Te1/0/3 DUSP2rc2-ETH2 Full 10000 Auto Up Active
Te1/0/4 DUSP2rc4-ETH2 Full 10000 Auto Up Active
Te1/0/5 DUSC1rc2-ETH2 Full 10000 Auto Up Active
Te1/0/6 DUSC2rc2-ETH2 Full 10000 Auto Up Active
Te1/0/7 DUSD2ci1-ETH2 Full 10000 Auto Up Active
Te1/0/8 DUSa1vm2-VMnic2 Full 10000 Auto Up Active
Te1/0/9 DUSa1vm4-VMnic2 Full 10000 Auto Up Active
Te1/0/10 DUSS2ci1-ETH2 Full 10000 Auto Up Active
Te1/0/11 DUSORRC2 Full 10000 Auto Up Active
Te1/0/12 N/A Unknown Auto Down Inactive
Te1/0/13 N/A Unknown Auto Down Inactive
Te1/0/14 N/A Unknown Auto Down Inactive
Te1/0/15 N/A Unknown Auto Down Inactive
Te1/0/16 N/A Unknown Auto Down Inactive
Te1/1/1 Po1-Ch1-to_RZ2_N7K Full 10000 Off Up Active
Te1/1/2 Full 10000 Off Down Inactive
Te1/1/3 Full 10000 Off Down Inactive
Te1/1/4 Full 10000 Off Down Inactive
Te1/2/1 Po1-Ch2-to_RZ2_N7K Full 10000 Off Up Active
Te1/2/2 Full 10000 Off Down Inactive
Te1/2/3 Full 10000 Off Down Inactive
Te1/2/4 Full 10000 Off Down Inactive

 

 

0 Kudos
Moderator
Moderator

Re: Naming issue on older M8024 Switches

You will probably find that the interfaces in port channel 1 are receiving and sending BPDUs. You can use the show statistics command to view the counters on the interfaces. All the other interfaces are internal server-facing interfaces, and typically should not show any BPDUs. These stats, along with the external facing interfaces only connecting to one device, would leave a high probability that the N7k is where the topology changes are coming in from. 

Have you checked the N7k logging to see if it is receiving any topology changes? Are spanning tree priorities manually configured throughout the network?

Daniel Covey
Dell EMC| Enterprise Support Services
Get support on Twitter:@DellCaresPRO
Download our QRL app:iOS, Android, Windows
Dell Networking Resources

0 Kudos