No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - Device Management

S9300, S9300E, and S9300X V200R012C00

This document describes the configurations of Device Management, including device status query, hardware management, CSS, SVF, PoE, OPS, OIDS, energy-saving management, information center, fault management, NTP, synchronous ethernet, PTP.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Using OIDS to Troubleshoot STP Flapping

Using OIDS to Troubleshoot STP Flapping

Fault Symptom

STP flapping occurs occasionally on an enterprise network. The switch records the following log information:

Apr 21 2018 13:21:46 SWITCH %%01MSTP/4/SET_PORT_FORWARDING(l)[4]:In MSTP process 0 instance 0, MSTP set port GigabitEthernet1/0/22 state as forwarding.
Apr 21 2018 13:21:46 SWITCH %%01MSTP/4/SET_PORT_DISCARDING(l)[5]:In MSTP process 0 instance 0, MSTP set port GigabitEthernet1/0/22 state as discarding.
Apr 21 2018 16:51:16 SWITCH %%01MSTP/4/SET_PORT_FORWARDING(l)[31]:In MSTP process 0 instance 0, MSTP set port GigabitEthernet1/0/22 state as forwarding.
Apr 21 2018 16:51:16 SWITCH %%01MSTP/4/SET_PORT_DISCARDING(l)[32]:In MSTP process 0 instance 0, MSTP set port GigabitEthernet1/0/22 state as discarding.
NOTE:

OIDS can be used to troubleshoot only the faults that occur after the OIDS monitoring function is enabled on the switch.

Procedure

  1. For a dual-MPU or cluster switch, run the collect oids database file to system-master command in the system view to save OIDS database files to the active MPU.
  2. Run the display oids history-event command in any view to check information about the OIDS events generated within the specified period.

    The command output shows that packet loss occurred occasionally in CPU queue 5 and that the time packet loss occurred matches the time the STP flapping log was generated.

    <Quidway> display oids history-event befor date-time 17:00:00 2018-04-21 period 24h
    ----------------------------------------------------------------------
    Slot       : 1
    ObjectName : CPU_Que5
    AttrName   : CPU_Que_Drop_Pkt
    Event      : CPU Queue Drop Pkt
    Time       : 2018-04-21 16:57:38
    State value: 3045
    Slot       : 1
    ObjectName : CPU_Que5
    AttrName   : CPU_Que_Drop_Pkt
    Event      : CPU Queue Drop Pkt
    Time       : 2018-04-21 13:27:04
    State value: 2830
    ----------------------------------------------------------------------
    

  3. Run the display cpu-defend configuration command in any view to check the CAR configuration.

    The command output shows that the STP protocol uses CPU queue 5, indicating that STP flapping was caused by packet loss in this queue.

    <Quidway> display cpu-defend configuration packet-type stp mcu
    Car configurations on mainboard.
    ----------------------------------------------------------------------
    Packet Name         Status     Cir(Kbps)   Cbs(Byte)  Queue  Port-Type
    ----------------------------------------------------------------------
    stp                  Enabled         512       96256      5         NA
    ----------------------------------------------------------------------
    

  4. Run the display cpu-defend statistics mcu command in any view to check CAR packet statistics on the MPU.

    The command output shows that a lot of services are configured on the switch. Run the display cpu-defend configuration mcu or display cpu-defend configuration packet-type packet-type mcu command in any view, finding that the majority of the following services have been sent to CPU queue 5. Many protocol packets have been sent to CPU queue 5.

    CPCAR rate limiting includes: protocol-based rate limiting, queue-based scheduling and rate limiting, and rate limiting for all packets. For details, see Overview of Local Attack Defense. The display cpu-defend statistics mcu command output shows CAR packet statistics based on the protocol rate limit. The output indicates that no STP packets were lost. If too many protocol packets are sent to a specific queue, for example, STP, BGP, OSPF, and TCP packets are all sent to CPU queue 5, the queue-based scheduling and rate limiting will cause flapping of STP that requires packets to be sent in a timely manner. You are advised to optimize the networking and reduce service configurations.

    <Quidway> display cpu-defend statistics mcu
    Statistics on mainboard:
    --------------------------------------------------------------------------------
    Packet Type          Pass(Packet/Byte)   Drop(Packet/Byte)  Last-dropping-time
    --------------------------------------------------------------------------------
    bgp                              68643                   0  -
                                  10034223                   0
    bgp4plus                        187364                   0  -
                                  70958364                   0
    bpdu-tunnel                      37843                   0  -
                                   5428376                   0
    dldp                              4753                   0  -
                                    537289                   0
    lldp                              8637                 623  2018-04-10 13:34:23
                                   1137616               98835
    mpls-ldp                         20015                   0  -
                                   1402188                   0
    mpls-rsvp                        57283                   0  -
                                   3548728                   0
    mpls-ttl-expired                 28376                   0  -
                                   3982737                   0
    nd                               47930                   0  -
                                   3094756                   0
    ospf                             28373                   0  -
                                   4837623                   0
    ospf-hello                       15390                   0  -
                                    983723                   0
    ospfv3                           45297                   0  -
                                   3705728                   0
    pim                             618121                   0  -
                                  79119488                   0
    pimv6                            20257                   0  -
                                   1419128                   0
    ssh                              75839                   0  -
                                   9328197                   0
    stp                              74929                   0  -
                                   9216267                   0
    tcp                              64879                   0  -
                                   4152256                   0
    telnet                            2988                   0  -
                                    191232                   0
    ……
    

Translation
Download
Updated: 2018-09-03

Document ID: EDOC1100038289

Views: 42180

Downloads: 15

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next