Maipu MyPower S4100 Series Operating instructions

Maipu Confidential & Proprietary Information Page 1 of 124
Mypower S4100 Troubleshooting
Maipu Communication Technology Co., Ltd
No. 16, Jiuxing Avenue
Hi-tech Park
Chengdu, Sichuan Province
People’s Republic of China - 610041
Tel: [phone]
Fax: [phone]
URL: http:// www.maipu.com
Email: [email protected]

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 2 of 124
All rights reserved. Printed in the People’s Republic of China.
No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any
language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual
or otherwise without the prior written consent of Maipu Communication Technology Co., Ltd.
Maipu makes no representations or warranties with respect to this document contents and specifically disclaims any implied
warranties of merchantability or fitness for any specific purpose. Further, Maipu reserves the right to revise this document
and to make changes from time to time in its content without being obligated to notify any person of such revisions or
changes.
Maipu values and appreciates comments you may have concerning our products or this document. Please address comments
to:
Maipu Communication Technology Co., Ltd
No. 16, Jiuxing Avenue
Hi-tech Park
Chengdu, Sichuan Province
People’s Republic of China - 610041
Tel: [phone]
Fax: [phone]
URL: http:// www.maipu.com
Email: [email protected]
All other products or services mentioned herein may be registered trademarks, trademarks, or service marks of their
respective manufacturers, companies, or organizations.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 3 of 124
Maipu Feedback Form
Your opinion helps us improve the quality of our product documentation
and offer better services. Please fax your comments and suggestions to
(86) 28-85148948, 85148139 or email to [email protected].
Document Title Mypower S4100 Troubleshooting
Product
Version Document
Revision
Number
1.0
Presentation:
(Introductions, procedures, illustrations, completeness, arrangement, appearance)
Good Fair Average Poor
Accessibility:
(Contents, index, headings, numbering)
Good Fair Average Poor
Evaluate this
document
Editorial:
(Language, vocabulary, readability, clarity, technical accuracy, content)
Good Fair Average Poor
Your
suggestions to
improve the
document
Please check suggestions to improve this document:
Improve introduction Make more concise
Improve Contents Add more step-by-step procedures/tutorials
Improve arrangement Add more technical information
Include images Make it less technical
Add more detail Improve index
If you wish to be contacted, complete the following:
Name Company
Postcode Address
Telephone E-mail

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 4 of 124
Contents
Software Upgrade Troubleshooting ..........................................................7
Software Upgrade Troubleshooting...........................................................................7
Port Management Troubleshooting...........................................................9
Basic Idea of Port Management Troubleshooting........................................................9
Common Port Management Troubleshooting.............................................................9
VLAN Troubleshooting ............................................................................ 13
Basic Idea of Vlan Troubleshooting.........................................................................13
Common Vlan Troubleshooting ..............................................................................14
Link Aggregation Troubleshooting ......................................................... 16
Basic Idea of Link Troubleshooting .........................................................................16
Common Link Aggregation Troubleshooting ............................................................16
MSTP Troubleshooting ............................................................................ 20
Basic Idea of MSTP Troubleshooting .......................................................................20
Common MSTP Troubleshooting ............................................................................20
Common MSTP Display Information .......................................................................22
MSTP information:.................................................................................................................22
MSTP Details.........................................................................................................................22
Common MSTP Error Information...........................................................................23
Error Information Checked from MSTP and Reason.................................................................23
Vlan dot1q tunnel Troubleshooting........................................................ 25
Basic Theory of Vlan dot1q tunnel Troubleshooting..................................................25
Common Vlan dot1q tunnel Troubleshooting...........................................................25
L2PC Troubleshooting............................................................................. 29
Basic Idea of L2PC Troubleshooting........................................................................29
Common L2PC Troubleshooting .............................................................................29
L2 Multicast Troubleshooting ................................................................. 31
Basic Idea of L2 Multicast Troubleshooting..............................................................31
Common L2 Multicast Troubleshooting ...................................................................31
802.1x Troubleshooting.......................................................................... 37
Basic Idea of 802.1x Troubleshooting.....................................................................37
Common 802.1x Troubleshooting ..........................................................................38

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 5 of 124
Port Security Troubleshooting................................................................ 41
Basic Idea of Port Security Troubleshooting.............................................................41
Common Port Security Troubleshooting..................................................................41
SPAN Troubleshooting ............................................................................ 43
SPAN Troubleshooting...........................................................................................43
ACL Troubleshooting............................................................................... 45
Basic Idea of ACL Troubleshooting..........................................................................45
Common ACL Troubleshooting...............................................................................45
QoS Troubleshooting............................................................................... 49
Basic Idea of QOS Troubleshooting.........................................................................49
Common QoS Troubleshooting ..............................................................................49
EIPS Troubleshooting ............................................................................. 54
Basic Idea of EIPS Troubleshooting ........................................................................54
Common EIPS Troubleshooting..............................................................................54
802.1AG Troubleshooting ....................................................................... 57
Basic Idea of 802.AG Troubleshooting ....................................................................57
Common 802.1AG Troubleshooting........................................................................58
Super-VLAN Troubleshooting ................................................................. 61
Basic Idea of Super-Vlan Troubleshooting...............................................................61
Common Super-Vlan Troubleshooting ....................................................................62
Loopback Test Troubleshooting.............................................................. 64
Basic Idea of Loopback Test Troubleshooting ..........................................................64
Common Loopback Test Troubleshooting................................................................64
IP SOURCE GUARD Troubleshooting...................................................... 66
Basic Idea of IP SOURCE GUARD Troubleshooting ...................................................66
Common IP SOURCE GUARD Troubleshooting......................................................... 66
OAM Troubleshooting.............................................................................. 69
Basic Idea of OAM Troubleshooting ........................................................................69
Common OAM Troubleshooting..............................................................................69
E-LMI Troubleshooting............................................................................ 72
Basic Idea of E-LMI Troubleshooting.......................................................................72
Common E-LMI Troubleshooting............................................................................72
DHCP SNOOPING Troubleshooting......................................................... 74
Basic Idea of DHCP SNOOPING Troubleshooting......................................................74
Common DHCP SNOOPING Troubleshooting...........................................................74
DYNAMIC ARP INSPECTION Troubleshooting ....................................... 77
Basic Idea of DYNAMIC ARP INSPECTION Troubleshooting.......................................77
Common DYNAMIC ARP INSPECTION Troubleshooting ............................................77

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 6 of 124
TAC Troubleshooting............................................................................... 80
Basic Idea of TAC Troubleshooting .........................................................................80
Common TAC Troubleshooting...............................................................................80
Route Troubleshooting............................................................................ 84
OSPF Troubleshooting...........................................................................................84
Basic Idea of OSPF Troubleshooting .......................................................................................84
Basic Idea of OSPF Neighbor Relation Troubleshooting ............................................................85
Basic Idea of OSPF Route Troubleshooting..............................................................................86
Tools for Removing OSPF Faults.............................................................................................86
OSPF Troubleshooting ...........................................................................................................90
OSPF Error Information Instance............................................................................................96
RIP Troubleshooting.............................................................................................. 97
Basic Idea of RIP Troubleshooting ..........................................................................................97
Tools for Removing RIP Faults................................................................................................97
RIP Troubleshooting ............................................................................................................100
RIP Error Information Instance.............................................................................................102
BGP Troubleshooting........................................................................................... 102
Basic Idea of BGP Troubleshooting .......................................................................................102
Tools for Removing BGP Faults.............................................................................................103
BGP Troubleshooting........................................................................................... 106
BGP Error Information Instance ...........................................................................................108
IS-IS Troubleshooting......................................................................................... 109
Basic Idea of ISIS Troubleshooting.......................................................................................109
Tools for Removing ISIS Faults ............................................................................................109
ISIS Troubleshooting...........................................................................................................111
ISIS Error Information Instance...........................................................................................115
Cluster Management Troubleshooting ................................................. 117
Basic Idea of Cluster Management Troubleshooting ............................................... 117
Common Cluster Management Troubleshooting..................................................... 118
PVLAN Troubleshooting ........................................................................ 120
Basic Idea of PVLAN Troubleshooting.................................................................... 120
Common PVLAN Troubleshooting......................................................................... 120
Voice VLAN Troubleshooting ................................................................ 122
Basic Idea of Voice VLAN Troubleshooting............................................................. 122
Common Voice VLAN Troubleshooting.................................................................. 122
Troubleshooting for Special Applications............................................. 124
Application of the Local Switch Interface Interconnection........................................ 124

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 7 of 124
Software Upgrade
Troubleshooting
This chapter describes the basic idea of analyzing the faults of the
software upgrade modules and the common methods and used commands
of removing the software faults.
Software Upgrade
Troubleshooting
Fault 1: The system prompts connection error when the physical lines and
TFTP/FTP server are normal during the TFTP/FTP upgrade in shell.
Possible Reasons Judging Methods and Solutions
1．During the TFTP/FTP
upgrade, the IP
address of the switch
is not set or the IP
address is not in the
same segment as the
FTP server.
In the config mode, use the interface vlan command to enter
the interface and then use the ip address command to add or
modify the IP address.
2．During the FTP
upgrade, the input file
name in shell does not
carry the correct FTP
path.
When inputting the IOS file name, the correct relative path in
the FTP server should be carried.
For example: When the upgrade file spl-g-6.1.1(bm03-
44).pck is in the directory b of FTP, the input command
should be sysupdate 192.168.1.1 b/spl-g-6.1.1(bm03-
44).pck image ftp a a, but not sysupdate 192.168.1.1
spl-g-6.1.1(bm03-44).pck image ftp a a.
Fault 2: The system always prompts the error of connection failure when
the physical lines and FTP server are normal during the process of starting
the network.
Possible Reasons Judging Methods and Solutions

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 8 of 124
1．The input IOS file is
not the relative path in
the FTP server.
Use the serial port to connect. Press ctrl-c to enter monitor
when re-starting, use the P command to view whether the
filename is the relative path in the FTP server, but not the path
in the flash system of the switch. If not correct, use the C
command to modify the boot parameters to the correct path.
2．The port connected to
the terminal is not dc0
port.
View whether the port connected to the terminal is dc0 port. If
not, re-connect to the dc0 port (note that the network can be
started only via the dc0 port.)
Fault 3: The local loaded IOS file is not correct.
Possible Reasons Judging Methods and Solutions
1．The parameters are set
wrongly.
Use the serial port to connect; press ctrl-c to enter the monitor
during the restarting; use the P command to view the detailed
configuration of the boot parameters and view where is the
problem; and then use the C command to modify the boot
parameters. Or after the system starts, enter the file system
(filesystem) in enable mode, use the show boot-loader
command to view whether the boot parameters are correct. If
not correct, use the bootloader command to set the boot
parameters and re-start the correct IOS.
2．The IOS is deleted. Enter the monitor and use the dir command to view whether
the IOS file is deleted. If yes, use the C command to modify
the boot options. Choose to start from the network or other
IOS to recover; or when the system starts, enter the file
system (filesystem) in the enable mode, use the dir command
to view whether the IOS file is deleted. If yes, use the copy or
sysupdate mode of the network to recover the IOS, or use
boot-loader to enable the existing IOS on flash.
3．The IOS file is placed
in the sub directory of
FLASH or other storage
space.
If the path is wrong when choosing to start the IOS file, even
the IOS file is correct, the loading cannot be performed
correctly. Use the P command in monitor to view the detailed
configuration of the boot parameters and check the selected
IOS file path during the starting. And then use the dir
command to view whether the IOS file is in the path. If not,
use the C command to modify the set path of starting the IOS
file in the boot parameters. Or after the system starts, enter
the file system (filesystem) in enable mode, use the dir
command to view the place of saving the IOS file and then use
the boot-loader command to modify the set path of starting the
IOS file in the boot parameters.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 9 of 124
Port Management
Troubleshooting
This chapter describes the common faults of the port management.
Main contents:
zBasic idea of port management troubleshooting
zCommon port management troubleshooting
Basic Idea of Port Management
Troubleshooting
1. Analyze the physical reason:
Checking method: Use the show port command to view whether the
physical signals are all up and check whether the cables are normal and
whether the device is normal; use the show protocol-state command to
view the spanning tree status.
2. Check the configuration and the parameter setting:
Checking method: View the configurations of the two communication sides
are normal.
Common Port Management
Troubleshooting
Fault 1: The ports cannot communicate or learn MAC addresses.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 10 of 124
Possible Reasons Judging Methods and Solutions
1. Physical problems The ports can become up, but execute the show port
statistics command and find that the number of the frames
received and sent by the port is abnormal or the error statistics
information is increasing. Here, you need to check the physical
problems.
2. The MTU setting of the
port is wrong.
The port becomes up normally and the port indicator shows
that the data is sent and received normally. Execute the show
port statistics command and find that the port can receive
the data frames. Here, you can check whether the MTU setting
of the port is too small, which results in the loss of the packets
whose length is larger than MTU.
3. The MAC address
learning function of the
port is wrong.
The port can become up normally and the port indicator shows
that the port can receive and send data normally. Execute the
show port statistics command and find that the port can
receive the data frames, but the port cannot learn the MAC
addresses for data forwarding.
Here, you can check whether the MAC address learning
function of the port is normal:
1. The MAC address learning function of the port is disabled
and the port cannot learn MAC addresses;
2. The number of the MAC addresses learned by the port
reaches the threshold set on the port or the MAC address
table of the switch is full;
3. The port is configured with the MAC address filtering and
the specified MAC address packets are dropped;
4. The port belongs to
one aggregation group
and the MAC address
learning function of the
aggregation group is
wrong.
When the phenomenon of reason 3 appears, check and find
that the problem described in reason 3 does not exist. Here,
you can check whether the port belongs to one aggregation
group, while the MAC address learning function of the
aggregation group is disabled or the number of the learned
MAC addresses reaches the threshold of the aggregation group
and the data cannot be forwarded.
Fault 2: The uni-directional communication appears among the ports in
one VLAN or the ports cannot communicate with each other completely.
Possible Reasons Judging Methods and Solutions
1. The local switching
capability of the UNI
ports is not enabled.
Two UNI ports belong to one VLAN; the ports can become up
normally and the MAC address learning is normal, but the two
ports cannot communicate with each other or can communicate
at only one direction. However, the two UNI ports can
communicate with the NNI ports normally.
By default, the local switching capability of the UNI ports of the
switch is disabled, that is, in the isolated state. Here, you can
check whether the port sets uni-isolate as isolated state and
modify to community.
2. The port isolation is
set.
Two NNI ports or the UNI ports in the community state belong
to one VLAN; the ports can become up normally; the MAC
address learning is normal, but the two ports cannot
communicate with each other or can communicate at only one

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 11 of 124
direction, or one port can communicate with the other ports
normally.
Here, check whether the port isolation attribute is set on the
ports and whether the ports those cannot communicate with
each other are set as isolated. If yes, cancel the isolated
setting.
Fault 3: After connecting the switch ports, the ports cannot become up.
Possible Reasons Judging Methods and Solutions
1. The port is shutdown. Use the show run port command to check whether the
shutdown is configured on the port. If no, use the show port
command to check whether there is Err-disabled after the link
status down. If yes, check the protocol on the port and you can
also use the sh port 0/x/x status err-disabled command to
check the fault reason. You need to use the no shutdown
command to restore the port.
After the 100M ports are connected with network wires, the
ports cannot become up and the indicators are off.
When the switch ports are configured as UNI ports, the ports
are shutdown and you need to use the no shutdown
command to restore the ports.
2. Duplex rate After the ports are connected with the network wires, the ports
cannot become up and the indicators are off.
Here, maybe the port rate and duplex mode are set wrongly,
which results in the negotiation failure between the two sides
of the link. You can check the peer setting and ensure that the
two sides can negotiate successfully.
3. The MDIX setting of
the port is wrong.
After the ports are connected with the parallel network wires,
the ports cannot become up, the indicators are off and change
to use the crossover network wires; or when using the
crossover network wires, the fault appears, but when changing
to use the parallel network wires, the ports become normal.
It is because that the MDIX setting of the port does not match
the used network wires. You just need to modify the MDIX
setting. By default, the MDIX value of the port is AUTO and the
network wire type can be negotiated automatically.
Fault 4: After the switch ports become up, the ports cannot communicate
with each other.
Possible Reasons Judging Methods and Solutions
The spanning tree status of
the port is wrong. Use the show protocol-state port xxx vlan xx command to view the spanning tree status of the port in VLAN. The
command shows the set port status of MSTP, EIPS, LBD, and
LAC. The ports can forward packets normally only when the set
status of all protocols is forward.
Fault 5: The shutdown/no shutdown command is not executed, but
the ports automatically become up/down.
Possible Reasons Judging Methods and Solutions

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 12 of 124
1. The port is err-
disabled.
After some wrong conditions are found on one port, the port is
shutdown temporarily and the action is called err-disabled,
First, use the show port command to view whether the port is
err-disabled, and then use the show port xxx status err-
disabled command to view which module err-disables the
port.
2. The port is configured
with err-disable
recovery.
You can configure one module port to be restored
automatically. In this way, after the port is err-disabled, enable
one recovery timer. After the timer reaches, the port is
recovered automatically. You can use the show errdisable
command to view the auto recovery configuration of the
module.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 13 of 124
VLAN Troubleshooting
This chapter describes the common problems when using VLAN to help the
network administrator analyze and solve the network faults quickly and
improve the production efficiency of enterprises.
Main contents:
zBasic idea of VLAN troubleshooting
zCommon VLAN troubleshooting
Basic Idea of Vlan
Troubleshooting
1. Analyze whether the VLAN exists;
Checking method: Use the show vlan command to view whether VLAN
exists;
2. Check whether the port belongs to the specified VLAN;
Checking method: Use the show vlan XX command to view whether the
VLAN exists in the specified VLAN;
3. Check whether the port can enable multiple VLANs;
Checking method: View whether mac vlan, IP subnet vlan or protocol vlan
is enabled on the port.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 14 of 124
Common Vlan Troubleshooting
Fault 1: The port type is TRUNK and permits one VLAN, but does not
forward the packets of the VLAN.
Possible Reasons Judging Methods and Solutions
The VLAN is not created. Use the show command to view whether the VLAN exists. If
no, use the vlan XX command to create the Vlan.
ACL is applied on the VLAN
and the packet forwarding is
disabled.
Use the show acl command to view whether the ACL is
applied on the VLAN. If yes, cancel the ACL or set the rule to
permit the packets to pass.
Fault 2: The port is configured with one MAC VLAN or IP VLAN or
PROTOCOL VLAN, but it does not take effect.
Possible Reasons Judging Methods and Solutions
1．mac vlan or ip vlan or
protocol vlan is
enabled on the port,
but the rules of mac
vlan or ip vlan or
protocol vlan are not
set globally.
Use the show mac-vlan and show ip-subnet-vlan, show
protocol-vlan commands to view whether the corresponding
rules are set up.
2．The port is not
configured to the
corresponding VLAN of
mac vlan or ip vlan or
protocol vlan.
Use the show vlan command to view whether the port
belongs to the corresponding VLAN of mac vlan or ip vlan. If
no, add the port to the corresponding VLAN.
3．The packets forwarded
by mac vlan and ip
vlan, protocol vlan do
not match the set
rules.
The global configuration only supports the untag rule, while
the mac-vlan or ip-sub-vlan or protocol vlan packets those
need to be forwarded by the port are tag packets. As a result,
the mac-vlan or ip-sub-vlan or protocol vlan does not take
effect.
Fault 3: Hybrid port cannot switch with TRUNK port.
Possible Reasons Judging Methods and Solutions
The hybrid port cannot be
directly switched to Trunk
port.
When switching the two port modes, you first need to switch to
the access port, and then switch to the hybrid or trunk.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 15 of 124
Fault 4: The communication cannot be performed in one VLAN.
Possible Reasons Judging Methods and Solutions
1．The VLAN is not
created.
Use the show vlan command to view whether the VLAN exists.
If no, create the VLAN manually.
2．Two ports of one
device are both UNI
ports or isolated
ports.
View whether the two ports are both UNI ports. If two ports of
one device are both UNI ports or isolated ports, they cannot
communicate with each other. You can use the port-type
command to modify the uni/nni attribute of the ports.
3．The ports connecting
the two devices send
the data of he VLAN.
One carries tag and
the other does not
carry tag.
Use the show run command to view the VLAN configuration of
the two ports. If one port sends the untag data (such as pvid or
hy vlan XX untag) and the other sends the tag data (such as
trunk vlan XX or hybrid vlan XX tag), the communication cannot
be performed in the VLAN. You can modify the two ports to
both send the tag data or untag data of the VLAN.
Fault 5: Configure multiple MAC VLANs and the system prompts error, but
the number of the configured MAC VLANs does not reach 1000.
Possible Reasons Judging Methods and Solutions
The configured mac vlan
distributes the hardware
resources according to the
hash algorithm and as a
result, the hardware
resources are not enough.
According to hash algorithm, some MACs are distributed with
the fixed segment of MAC-VLAN resources by some rule. If the
foregoing MACs are distributed with the segment of resources
completely, the later MACs cannot be distributed with the
segment of MAC_VLAN resources, so the system prompts that
the resources are not enough. If the MAC_VLAN resources of
other MAC addresses that comply with the rule are idle, they
can be distributed continuously.
If the fault appears, you can delete the mac vlan configuration
that is not in use.
Fault 6: Two VRFs on one device are directly connected and cannot ping
each other.
Possible Reasons Judging Methods and Solutions
By default, all configured
switch interfaces of the
system use one MAC
address.
The mode does not support that multiple interfaces of one
device are interconnected. For example, the L3 packets sent by
the VLAN1 interface need to be received the VLAN2 interface of
the same device. The packet is dropped because the source
MAC and the destination MAC are the same and the VLAN2
interface cannot receive the packet. In this case, you need to
use the mac-address command in the interface to specify the
different MAC addresses for VLAN interfaces so that the
interconnected VLAN interfaces use the different MAC
addresses.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 16 of 124
Link Aggregation
Troubleshooting
Main contents:
zBasic idea of link aggregation troubleshooting
zCommon link aggregation troubleshooting
Basic Idea of Link
Troubleshooting
1. Analyze the link group status:
Checking method: Use the show port command to view whether the
member ports of the link group all become up and check whether the
cables are normal, whether the device is normal, and whether the
environment has the bad influence for the link aggregation.
2. Check whether the status of the link group is normal and whether the
configurations and parameter setting are correct.
Checking method: Use the show link-aggregation group command to
view the status of the link aggregation; use the show link-aggregation
port command to view whether the member port status is normal; use the
debug lac command to locate and remove the fault.
Common Link Aggregation
Troubleshooting
Fault 1: The link groups between two devices cannot aggregate
successfully.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 17 of 124
Possible Reasons Judging Methods and Solutions
1. The aggregation ports
are not added with
the member ports or
the member port
connection of the two
devices is abnormal.
Use the show link-aggregation group command to check
whether the link aggregation ports on the two devices are added
with the member ports and whether the member ports are
interconnected and in the up state. The display when the
member ports are added normally is as follows:
switch#show link-a g
Link Aggregation 2
Mode: LACP Description:
Load balance method: src-mac
Number of ports in total: 2
Number of ports attached: 2
Root port: port 0/25
port 0/24: ATTACHED
port 0/25: ATTACHED
If the member ports are not added, use the link-aggregation
XX active/manual command in the port mode to add.
2. The LACP aggregation
port is set up between
two devices and the
member ports added
to the aggregation
port are in the passive
mode.
Use the show link-aggregation port command to view
whether the member ports added to the aggregation port are in
the passive mode.
switch#show link-aggregation port
port 0/2 link aggregation 1 mode: Passive
selected: YES
attached: YES
lacp_enabled: Lacp_Enabled_Full_Duplex
actor information:
1.000122334450.32768.3=0x0501
Passive LongTimeout Aggregatable IN_SYNC Collecting
Distributing Received Unexpired
partner information:
32768.00017A334401.32768.3=0x0501
Active LongTimeout Aggregatable IN_SYNC Collecting
Distributing Received Unexpired
state machine information:
receive=CURRENT, periodic=NO,
mux=COLLECTING_DISTRIBUTING
If the member ports of the two sides are all in passive mode, the
link aggregation cannot be set up. You need to modify one side
to active mode or two sides to active mode.
3. If one side is dynamic
link aggregation
(LACP) and the other
side is the static link
aggregation (manual),
the aggregation
cannot succeed.
Use the show link-aggregation group command on two
devices to view whether the set link aggregation mode is the
same. If one is dynamic aggregation and the other is the static
aggregation, the aggregation cannot succeed. You need to unify
the aggregation modes of the two sides to static or dynamic.
4. Set up the LACP
dynamic aggregation
and the member ports
are half-duplex.
Use the show port command to view whether the ports are half-
duplex. If it is the half-duplex, do not send LACP packets or set
up link aggregation.
You can use the command to modify the duplex attribute of the
port to solve the problem.
Fault 2: In one aggregation group, some member ports can aggregate
successfully, but the other ports cannot aggregate successfully.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 18 of 124
Possible Reasons Judging Methods and Solutions
1．The number of the
member ports exceeds
the number of the ports
those can aggregate
successfully.
One aggregation group can be added with 8 member ports. At
most eight member ports can aggregate successfully, that is,
the status is ATTACHED. You can modify the LAC priority of the
port to ensure that some ports aggregate successfully first.
switch(config)#port 0/0
switch(config-port-0/0)#lac
switch(config-port-0/0)#lacp port-priority ?
<1-65535> LACP port priority[Default: 32768]
switch(config-port-0/0)#lacp port-priority 1 (the smaller the
priority value, the higher the priority)
2．The port attribute and
the root port attribute
are inconsistent.
When the attribute of the member port is inconsistent with the
attribute of the root port (or the port that aggregate
successfully), the aggregation cannot succeed. It is the most
likely that when the rate or duplex is different, the aggregation
cannot succeed. If the root port is the 1000M rate and the rate
of the other member port is 100M, the member port cannot
aggregate successfully and the status is DETACHED. You can
modify the port rate or select the port with the consistent rate
to add to one aggregation port.
Fault 3: The common ports cannot be added to one aggregation group.
Possible Reasons Judging Methods and Solutions
1．The aggregation group
to which the port is
added does not exist.
When the port is added to one aggregation group, the prompt
information is as follows:
switch(config-port-0/0)#link-a 8 a
Link aggregation 8 is not created yet
The above information indicates that the link group is not
created. First create the link group and then add the port to the
link group.
2．The port is added to
the static aggregation
group in dynamic mode
or added to the
dynamic aggregation
group in static mode.
Use the show link-aggregation group command to view
whether the aggregation group is dynamic or static. For the
dynamic aggregation group, the port can only be added in
active or passive mode; for the static aggregation group, the
port can only be added in manual mode.
For example, the following linl-aggregation 8 is set up in
dynamic mode, the port must be added in active or passive
mode.
switch#show link-aggregation group 8
Link Aggregation 8
Mode: LACP Description:
Load balance method: src-mac
Number of ports in total: 0
Number of ports attached: 0
switch(config)#port 0/0
switch(config-port-0/0)#link-a 8 active
If the port is added in static mode, the following prompt
information is displayed:
switch(config-port-0/0)#link-a 8 manual
Port mode can not be manual in a lacp aggregation

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 19 of 124
3．The port is already
added to the
aggregation group.
When the port is added to the aggregation group, the
following prompt information is displayed:
Switch(config-port-2/17)#link-aggregation 56 active
% port 2/17 is already in a link aggregation
The information indicates that the port is already added to one
aggregation group.
Fault 4: The aggregation group cannot realize the traffic load balance.
Possible Reasons Judging Methods and Solutions
1．The sent data is the
broadcast or multicast
packets.
For the broadcast or multicast packets, the link aggregation
cannot realize the load balance.
2．The sent data is the
single fixed packets.
View whether the sent traffic is one single packets. To realize
the load balance, multiple different data flows (IP or MAC
addresses are different) need to be sent.
3．Whether the type of the
sent packets does not
match the load balance
mode of the set
aggregation group.
View the load balance mode of the link aggregation group. If
the load balance mode is src-mac and the sent traffic is the
flow with variable src-ip, the load balance cannot be realized.
You can use the following command to modify the load balance
mode.
switch(config)#link-aggregation 1 load src-ip
Currently, BM03 provides six balance modes, including based
on source IP, based on source MAC, based on destination IP,
based on destination MAC, based on source and destination IP,
and based on source and destination MAC.
4．The sent packets are
the unknown unicast
packets.
The load balance of the link aggregation traffic is just for the
known unicast packets, that is, the MAC table of the device
should have the destination MAC address entry of the data
flow. You can use the show mac-address command to view
whether the packet is the known unicast packet. If the device
does not have the MAC entry, you can add MAC address
statically or send traffic to add MAC address to form the known
unicast packets.

Mypower S4100 Troubleshooting
Maipu Confidential & Proprietary Information Page 20 of 124
MSTP Troubleshooting
This chapter describes the basic idea of analyzing the MSTP module faults
and common methods and used commands of removing the MSTP faults.
Main contents:
zBasic idea of MSTP troubleshooting
zCommon MSTP troubleshooting
zCommon MSTP prompt information
zCommon MSTP error prompt information
Basic Idea of MSTP
Troubleshooting
Basic idea of analyzing the faults: First check the link and then confirm the
protocol configuration.
First analyze the physical reason, including whether the device works
normally and whether the cables are normal;
Checking method: Use the ping packets to view the flashing status of the
ACT light; test whether the data is forwarded via Forwarding after passing
the MSTP network; use the show spanning-tree mst detail command
on the device to view whether the bridge and port status are correct.
Common MSTP Troubleshooting
Fault 1: MSTP cannot block the port or remove the loop correctly.
Possible Reasons Judging Methods and Solutions