Got it

[Troubleshooting case] L2 Packet Loss Caused by Loops on Sx700 Series Switches

191 0 1 0 0

Hello!

This time I bring you an interesting case about Layer 2 packet loss caused by loops on Sx700 series Switches, and how to troubleshoot it. Hope you find it useful.


Networking

As shown in Figure 1, a switch is connected to an enterprise network through a leased line. The switch functions as a Layer 2 aggregation switch, and an NE80 functions as the gateway.


1

Network where layer 2 packet loss occurs


Fault Symptom

Enterprise network users complain that the network has a slow response to their service requests. When the NE80 pings a terminal on the enterprise network, packet loss occurs.


Cause Analysis

A loop exists on the downstream network of GE10/0/6. As a result, the MAC address of the NE80 flaps between GE10/0/6 and GE12/0/0 of the switch. When GE10/0/6 learns the MAC address of the NE80, user packets cannot be forwarded to the gateway.


Troubleshooting Procedure

  1. Enable MAC address flapping detection on the switch and check alarms.

        Note: Alarm information differs for fixed and modular switches of different versions. The following alarm information is only used as an example.

#Jul 28 09:59:34 2012 Switch L2IF/4/mac_flapping_alarm:OID 1.3.6.1.4.1.2011.5.25.42.2.1.7.12The mac-address has flap value

The preceding alarm information indicates that MAC address flapping occurs.


    2. Set the NE80 MAC address to a static MAC address on GE12/0/0.

        The loop on the downstream network of GE10/0/6 is eliminated.


Conclusions and Suggestions

To locate Layer 2 packet loss and intermittent disconnection problems, first check whether MAC address flapping occurs in addition to checking basic factors such as network cables, optical power of optical modules, and interface status. Then configure a static MAC address and check whether the problems are resolved. Configuring a static MAC address only prevents loops. To eliminate loops, configure a loop prevention protocol.


Source: https://support.huawei.com/enterprise/es/doc/EDOC1000057760?section=j007


That’s all folks, hope you found this troubleshooting case useful, and don’t forget to comment if you have further concerns or remarks.

Thank you very much!


#HESC

#OneHuawei

#MVE



Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.