1. Manuals
  2. Brands
  3. Maipu Manuals
  4. Switch
  5. MyPower S4100 Series
  6. Troubleshooting manual

Maipu Mypower S4100 Troubleshooting Manual

Hide thumbs Also See for Mypower S4100:
Table of Contents

Advertisement

Quick Links

See also: Installation Manual
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: (86) 28-85148850, 85148041
Fax: (86) 28-85148948, 85148139
URL: http://
www.maipu.com
Email:
overseas@maipu.com
Maipu Confidential & Proprietary Information
Page 1 of 124

Advertisement

Table of Contents
loading

Related Manuals for Maipu Mypower S4100

Summary of Contents for Maipu Mypower S4100

  • Page 1 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: (86) 28-85148850, 85148041 Fax: (86) 28-85148948, 85148139 URL: http:// www.maipu.com Email: overseas@maipu.com Maipu Confidential & Proprietary Information...
  • Page 2 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.
  • Page 3 Mypower S4100 Troubleshooting 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 overseas@maipu.com. Document Title Mypower S4100 Troubleshooting Product Document...

  • Page 4: Table Of Contents

    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 Maipu Confidential & Proprietary Information Page 4 of 124...
  • Page 5 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 Maipu Confidential & Proprietary Information Page 5 of 124...
  • Page 6 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 Maipu Confidential & Proprietary Information Page 6 of 124...

  • Page 7: Software Upgrade Troubleshooting

    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 Maipu Confidential & Proprietary Information Page 7 of 124...
  • Page 8 (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. Maipu Confidential & Proprietary Information Page 8 of 124...

  • Page 9: Port Management Troubleshooting

    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. Maipu Confidential & Proprietary Information Page 9 of 124...
  • Page 10 VLAN; the ports can become up normally; the MAC set. address learning is normal, but the two ports cannot communicate with each other or can communicate at only one Maipu Confidential & Proprietary Information Page 10 of 124...
  • Page 11 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 Maipu Confidential & Proprietary Information Page 11 of 124...
  • Page 12 After the timer reaches, the port is recovery. recovered automatically. You can use the show errdisable command to view the auto recovery configuration of the module. Maipu Confidential & Proprietary Information Page 12 of 124...

  • Page 13: Vlan Troubleshooting

    VLAN exists in the specified VLAN; 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. Maipu Confidential & Proprietary Information Page 13 of 124...

  • Page 14: Common Vlan Troubleshooting

    The hybrid port cannot be When switching the two port modes, you first need to switch to directly switched to Trunk the access port, and then switch to the hybrid or trunk. port. Maipu Confidential & Proprietary Information Page 14 of 124...
  • Page 15 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. Maipu Confidential & Proprietary Information Page 15 of 124...

  • Page 16: Link Aggregation Troubleshooting

    Common Link Aggregation Troubleshooting Fault 1: The link groups between two devices cannot aggregate successfully. Maipu Confidential & Proprietary Information Page 16 of 124...
  • Page 17 You can use the command to modify the duplex attribute of the port to solve the problem. are half-duplex. Fault 2: In one aggregation group, some member ports can aggregate successfully, but the other ports cannot aggregate successfully. Maipu Confidential & Proprietary Information Page 17 of 124...
  • Page 18 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 Maipu Confidential & Proprietary Information Page 18 of 124...
  • Page 19 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. Maipu Confidential & Proprietary Information Page 19 of 124...

  • Page 20: Mstp Troubleshooting

    Common MSTP Troubleshooting Fault 1: MSTP cannot block the port or remove the loop correctly. Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 20 of 124...
  • Page 21 Fault 3: When Maipu switch is connected to Cisco switch, the two switches cannot take part in the MSTP calculation. Possible Reasons Judging Methods and Solutions It is the fault of the View whether the port becomes up via the indicator.

  • Page 22: Common Mstp Display Information

    MSTP configuration mode. Old Cisco version When the area configuration parameters are the same and if Maipu supports un-standard switch and Cisco switch are not in the same area, maybe because MSTP protocol. Cisco version is too old and the sent packets are not standard. You need to configure spanning-tree mst cisco pre-standard interoperability on Maipu device port.

  • Page 23: Common Mstp Error Information

    To avoid the un-necessary calculation caused by the configuration, the commands do not take effect at once after being input. They can take effect only after the active configuration pending Maipu Confidential & Proprietary Information Page 23 of 124...
  • Page 24 TIME parameters. 2 * (forward_time-1) >= When configuring the FORWARD-TIME, MAX-AGE, and max_age >= 2 * (hello_time+1) HELLO-TIME parameters, the three parameters should meet the above condition. Maipu Confidential & Proprietary Information Page 24 of 124...

  • Page 25: Vlan Dot1Q Tunnel Troubleshooting

    QinQ ingress and egress is correct. The ingress and egress both belong to out vlan. Common Vlan dot1q tunnel Troubleshooting Fault 1: QinQ cannot communicate normally. Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 25 of 124...
  • Page 26 Use the show run command to view whether the port is configured with vlan dot1q-tunnel enable. If not, the VLAN on the port. MAPPING communication can be performed only when QinQ is enabled on the ingress port. Maipu Confidential & Proprietary Information Page 26 of 124...
  • Page 27 (mapping) entry. If the packet received by the port does not match the selective vlan dot1q-tunnel (mapping) entry, drop the packet, so the common TAG frame cannot be forwarded via the port normally. Maipu Confidential & Proprietary Information Page 27 of 124...
  • Page 28 QinQ out tag of H02 is 0X8100. Here, you can modify the tpid of the port to 0X9100, so as to realize the interconnection with the QinQ of Cisco device. The configured command: SW2(config-port-0/23)#frame-tag tpid 0X9100 Maipu Confidential & Proprietary Information Page 28 of 124...

  • Page 29: L2Pc Troubleshooting

    L2PC is be transmitted by the tunnel enabled to be consistent with the vlan that needs to be packet. transmitted by the tunnel packet. Maipu Confidential & Proprietary Information Page 29 of 124...
  • Page 30 L2PC shutdown. If yes, check why the peer the protocol. After becoming switch sends the tunnel packets or modify the network up, the port receives the connection. tunnel packets of the protocol. Maipu Confidential & Proprietary Information Page 30 of 124...

  • Page 31: L2 Multicast Troubleshooting

    L2 multicast protocol to confirm the problem further. Common L2 Multicast Troubleshooting Fault 1: The receiver cannot receive the multicast flow. Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 31 of 124...
  • Page 32 Maybe L2 static multicast forbidden port is configured. Use the show l2-multicast mac-entry static command to view whether the port of the receiver is forbidden. If yes, the configuration needs to be deleted. Maipu Confidential & Proprietary Information Page 32 of 124...
  • Page 33 VLAN the route port belongs, as route port are wrong. follows: switch# show ip igmp snooping mrouter Vlan SourceAddr Ports ---- --------- -------- Maipu Confidential & Proprietary Information Page 33 of 124...
  • Page 34 0/0/40 of the static multicast group, it can receive the multicast data flow. Fault 5: The video jitter appears after enabling IGMP snooping for VOD. Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 34 of 124...
  • Page 35 VLAN and multicast sub VLAN. Use the show run igmp snooping command on the switch to view the configuration, whether IGMP Snooping is enabled globally and in multicast VLAN and multicast sub VLAN. Maipu Confidential & Proprietary Information Page 35 of 124...
  • Page 36 Use the show run int command to view whether the sub VLAN is configured with interface. If not, configure interface on the sub VLAN. Other possible reasons Refer to fault 1. Maipu Confidential & Proprietary Information Page 36 of 124...

  • Page 37: 802.1X Troubleshooting

    View whether the AAA configuration on the device and the 802.1X parameter setting on the port are correct, and analyze the problem according to the 802.1X authentication theory (you can enable the 802.1X debug information to help analyze). Maipu Confidential & Proprietary Information Page 37 of 124...

  • Page 38: Common 802.1X Troubleshooting

    To solve the problem, you can use the dot1x max-authfail and dot1x timeout quiet- period commands to modify the maximum authentication Maipu Confidential & Proprietary Information Page 38 of 124...
  • Page 39 Guest VLAN cannot be applied on the dynamic VLAN. For is the dynamic VLAN. example, if the vlan id specified by Guest VLAN is the vlan automatically created by gvrp, Guest VLAN does not take effect. Maipu Confidential & Proprietary Information Page 39 of 124...
  • Page 40 Possible Reasons Judging Methods and Solutions In port-based mode, the After being configured as the single-host mode, only the user single-host mode is set. that passes the authentication can access the extranet. Maipu Confidential & Proprietary Information Page 40 of 124...

  • Page 41: Port Security Troubleshooting

    View whether the device configuration and parameter setting are correct and analyze the problem further according to the port security theory. Common Port Security Troubleshooting Fault 1: The port security based on MAC or IP does not take effect. Maipu Confidential & Proprietary Information Page 41 of 124...
  • Page 42 By default, the port security that enables the IP or MAC rule does not age. The system ages the MAC address only when port-security aging static is configured and port-security <0-1440> aging time is configured as non-0. Maipu Confidential & Proprietary Information Page 42 of 124...

  • Page 43: Span Troubleshooting

    And then add the port to the mirroring destination port. Maipu Confidential & Proprietary Information Page 43 of 124...
  • Page 44 STP and LACP as STP and LACP protocol protocol are enabled, the mirroring protocol packets are directly packets. transmitted to CPU and cannot be mirrored. Maipu Confidential & Proprietary Information Page 44 of 124...

  • Page 45: Acl Troubleshooting

    If not, add the corresponding ACE rules. empty ACL. For example, the following ACL is configured with one ACE rule. sw201#show access mac access-list extended 3001 10 permit any any precedence 5 vlan-id 100 Maipu Confidential & Proprietary Information Page 45 of 124...
  • Page 46 ACL is to permit source ip 10.0.0.1 and deny the packet forwarding of other source IP 10.0.0.0/24 segment, but according to the following ACL, 10.0.0.1 is blocked. ip access-list standard 1 10 deny 10.0.0.0 0.0.0.255 Maipu Confidential & Proprietary Information Page 46 of 124...
  • Page 47 256 ACEs, so it may appear that the hardware resources are not enough and enabling ACL on the object fails. For example, port 0/0/2 and port 0/0/3 are Maipu Confidential & Proprietary Information Page 47 of 124...
  • Page 48 After increasing the number of Port IPV6 ACL IN resources by the multiples of 2, save the configuration and restart the system so that you can apply IPv6 ACL on the port. Maipu Confidential & Proprietary Information Page 48 of 124...

  • Page 49: Qos Troubleshooting

    View whether the configuration is correct and whether the applied rules can take effect normally. Common QoS Troubleshooting Fault 1: QoS does not take effect. Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 49 of 124...
  • Page 50 64. When the input value 4096. is not 64, the drive adjusts to be the minimum integer of 64 larger than the current value. The burst-size Maipu Confidential & Proprietary Information Page 50 of 124...
  • Page 51 Priority Module Number Resource Quantity Module Name Protocol Send To Cpu IN VOICE VLAN IN ipsg function IN Port MAC ACL IN Port IP ACL IN Port IPV6 ACL IN Maipu Confidential & Proprietary Information Page 51 of 124...
  • Page 52 All rate limitation indexes of QoS are for L2 bps and should The reference index is L3 bps, not L2 bps. refer to L2 bps statistics to evaluate the QoS rate limitation traffic. Maipu Confidential & Proprietary Information Page 52 of 124...
  • Page 53 The problem appears when the network is blocked. You can not ensure enough priority remark high priority for the data to ensure the priority for the VoIP and video data. forwarding. Maipu Confidential & Proprietary Information Page 53 of 124...

  • Page 54: Eips Troubleshooting

    Checking method: View the configurations of the EIPS main node and transmission node, edge node, and edge assistant node. Run the EIPS debug commands to locate the problems further. Common EIPS Troubleshooting Fault 1: The EIPS ring status is FAULT. Maipu Confidential & Proprietary Information Page 54 of 124...
  • Page 55 Block state to the Forward state, which results in the loop. Fault 3: The EIPS control packets of the transmission node cannot be received. Maipu Confidential & Proprietary Information Page 55 of 124...
  • Page 56 When the public ports of the edge node are disconnected, the Hello packets of the sub ring retrace via the main node of the main ring and the status of the sub ring is still complete. Maipu Confidential & Proprietary Information Page 56 of 124...

  • Page 57: 802.1Ag Troubleshooting

    Check whether the port belongs to instance vlan. Checking method: Use the show vlan command to view whether the ethernet cfm port belongs to the instance vlan. Maipu Confidential & Proprietary Information Page 57 of 124...

  • Page 58: Common 802.1Ag Troubleshooting

    MPID information address information on the on the device. If not, ping Ethernet can be executed only after device. learning the remote MPID information. Maipu Confidential & Proprietary Information Page 58 of 124...
  • Page 59 Therefore, you need to input the appropriate TLL value when executing the link Maipu Confidential & Proprietary Information Page 59 of 124...
  • Page 60 Mypower S4100 Troubleshooting tracking. By default, the TTL value is 64. The maximum TTL can reach 255. Maipu Confidential & Proprietary Information Page 60 of 124...

  • Page 61: Super-Vlan Troubleshooting

    Checking method: View whether the ports are added to Sub-Vlan. arp proxy enable must be enabled for the user communication between different sub-vlans. Checking method: Use the show super-vlan command to view whether the specified super-vlan enables arp proxy enable. Maipu Confidential & Proprietary Information Page 61 of 124...

  • Page 62: Common Super-Vlan Troubleshooting

    It indicates that the number of the added suv-vlans exceeds 8 and you cannot add more. Fault 3: Different sub-vlans in one super-vlan cannot perform the L3 communication. Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 62 of 124...
  • Page 63 Use the show Super-Vlan command to view whether the with arp proxy. super-vlan is configured with arp proxy enable. Different suv- vlans can perform L3 communication only when the arp proxy enable command is configured. Maipu Confidential & Proprietary Information Page 63 of 124...

  • Page 64: Loopback Test Troubleshooting

    Check the configuration and parameter setting. Check whether the configuration and parameter setting are reasonable. Common Loopback Test Troubleshooting Fault 1: The loopback test does not take effect. Maipu Confidential & Proprietary Information Page 64 of 124...
  • Page 65 The loop ports all need to The two ports that form the loop both need to enable the enable the loopback test. loopback test, so as to generate alarms for the loop. Maipu Confidential & Proprietary Information Page 65 of 124...

  • Page 66: Ip Source Guard Troubleshooting

    SOURCE GUARD rules. Check the configuration and parameter setting. View whether the configuration and parameter setting are reasonable. Common IP SOURCE GUARD Troubleshooting Fault 1: IP SOURCE GUARD does not take effect. Maipu Confidential & Proprietary Information Page 66 of 124...
  • Page 67 However, when restarting the loading configuration script, the resources are first distributed to the port with small serial number, which makes the original valid binding entries of the port with large serial number become invalid and the original Maipu Confidential & Proprietary Information Page 67 of 124...
  • Page 68 Mypower S4100 Troubleshooting invalid binding entries of the port with small serial number become valid. Maipu Confidential & Proprietary Information Page 68 of 124...

  • Page 69: Oam Troubleshooting

    The connection between You can use the command to view whether the connection devices is cut off. between the devices is normal and whether the ports are in the up state. Maipu Confidential & Proprietary Information Page 69 of 124...
  • Page 70 The OAM link monitoring can take effect only when the is up neighbor status is up. If the neighbor cannot be set up, solve the neighbor problem according to the fault. Maipu Confidential & Proprietary Information Page 70 of 124...
  • Page 71 The default threshold (high/low) of the link detection is none. parameters are set correctly Set the high and low threshold of the link detection and the on the port related protocol actions. Maipu Confidential & Proprietary Information Page 71 of 124...

  • Page 72: E-Lmi Troubleshooting

    CE and PE is up and whether the connection between the two ports is normal. Common E-LMI Troubleshooting Fault 1: The EVC information of PE cannot be got from the CE device. Maipu Confidential & Proprietary Information Page 72 of 124...
  • Page 73 PE port to EVC, it indicates that the EVC is not created: RH02_199.3(config-port-0/0)#evc qinq bind ee a evc ee does not exist! Here, you need to create the EVC first. Maipu Confidential & Proprietary Information Page 73 of 124...

  • Page 74: Dhcp Snooping Troubleshooting

    View whether related items active. Check the configuration and parameter setting View whether configuration parameter configuration reasonable. Common DHCP SNOOPING Troubleshooting Fault 1: DHCP SNOOPING cannot be enabled. Maipu Confidential & Proprietary Information Page 74 of 124...
  • Page 75 After the port is shutdown by err-disable because the received function is not enabled. DHCP packets exceeds the limitation, you need to execute the command errdisable recovery cause dhcp-snooping in the Maipu Confidential & Proprietary Information Page 75 of 124...
  • Page 76 The default interval from shutdown to up is 5 minutes. The interval can be modified by the errdisable recovery interval command. Maipu Confidential & Proprietary Information Page 76 of 124...

  • Page 77: Dynamic Arp Inspection Troubleshooting

    IP SOURCE GUARD rule. Check the configuration and parameter setting View whether configuration parameter configuration reasonable. Common DYNAMIC ARP INSPECTION Troubleshooting Fault 1: DYNAMIC ARP INSPECTION cannot be enabled on the port. Maipu Confidential & Proprietary Information Page 77 of 124...
  • Page 78 Fault 4: The port cannot become up after being shutdown by err-disable because the received arp packets exceeds the limitation. Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 78 of 124...
  • Page 79 The default interval from shutdown to up is 5 minutes. The interval can be modified by the errdisable recovery interval command. Maipu Confidential & Proprietary Information Page 79 of 124...

  • Page 80: Tac Troubleshooting

    Common TAC Troubleshooting Fault 1: The client returns login failure message Possible Reasons Judging Methods and Solutions The shared keys of When the device and the authentication server have the same Maipu Confidential & Proprietary Information Page 80 of 124...
  • Page 81 If yes, whether the transparent device, the switch is transmission function is configured. If not, configure the switch used but not accordingly. configured with eapol- relay function. Maipu Confidential & Proprietary Information Page 81 of 124...
  • Page 82 PS and change it to the proper value. time, the role default action is Deny. Fault 5: After the authentication failed, the user cannot the security resources including virus server Possible Reasons Judging Methods and Solutions Maipu Confidential & Proprietary Information Page 82 of 124...
  • Page 83 Check the vlan id of the default role on the ps. Then, run the with default roles on the show vlan command to check whether the corresponding id device exists. If not, add the id. Maipu Confidential & Proprietary Information Page 83 of 124...

  • Page 84: Route Troubleshooting

    Ensure all connections are normal. Ensure OSPF is configured and no fault occurs. Ensure the states of all neighbors are Full or Two-way. Ensure all neighbors are in the neighbor table. Maipu Confidential & Proprietary Information Page 84 of 124...

  • Page 85: Basic Idea Of Ospf Neighbor Relation Troubleshooting

    Only when the network status is NBMA and PTMP, the network is in the Attempt status. You need to specify the neighbor. Therefore, you need to check whether the neighbor is properly configured and then test whether the neighbor is available through ping command. Maipu Confidential & Proprietary Information Page 85 of 124...

  • Page 86: Basic Idea Of Ospf Route Troubleshooting

    OSPF database has relevant route LSA. Step 5: Calculate the route to the destination through the relevant LSA. Tools for Removing OSPF Faults Maipu switch provides many tools for finding OSPF faults. The show tools and the debug tools are as follows. Show Tools...
  • Page 87 2.2.2.1 0.0.0.0 area 0 network 129.255.0.0 0.0.255.255 area 0 exit interface vlan500 ip address 129.255.19.20 255.255.0.0 exit interface loopback0 ip address 2.2.2.1 255.255.255.255 exit Switch_B router ospf 64 log-adjacency-changes Maipu Confidential & Proprietary Information Page 87 of 124...
  • Page 88 The OSPF process ID, router ID, OSPF network type, and the cost value of the interface OSPF packet transmission delay, status, and priority of the interface DR router ID and DR IP address of the network Maipu Confidential & Proprietary Information Page 88 of 124...
  • Page 89 Address Interface 11.0.0.1 1 Full/BDR 00:00:37 129.255.19.10 vlan500 The OSPF neighbor table covers: the ID of the local process connecting the neighbor, the neighbor router ID, neighbor priority, neighbor status, dead Maipu Confidential & Proprietary Information Page 89 of 124...

  • Page 90: Ospf Troubleshooting

    OSPF interface of the Open the debug ip ospf packet hello to print the following error two negotiation information: OSPF RECV Area 0.0.0.0 172.160.3.9 -> 224.0.0.5: parties are not OSPF: Authentication error; Maipu Confidential & Proprietary Information Page 90 of 124...
  • Page 91 Point to point network mode: hello interval is 40 seconds; Point to multiple-point network mode: hello interval is 120 seconds; Broadcast network mode: hello interval is 40 seconds; NBMA network mode: hello interval is 120 seconds; Maipu Confidential & Proprietary Information Page 91 of 124...
  • Page 92 NSSA area, the local configuration should be NSSA area; if the opposite configuration is common OSPF area, the local configuration should be common OSPF area. Maipu Confidential & Proprietary Information Page 92 of 124...
  • Page 93 Open the debug ip ospf packet hello detail to find that the RtrPriority fields of hello packets sent and received at the interface are 0. Solution: Configure the interface or a neighbor interface priority to non- Maipu Confidential & Proprietary Information Page 93 of 124...
  • Page 94 Show ip ospf route, there is no route about the forward address Show ip route ospf, external route is not added Solution: Ensure that in the area of the forward address or between areas, Maipu Confidential & Proprietary Information Page 94 of 124...
  • Page 95 External route summary is ineffective on the router where redistribution is not performed. Solution: Perform external route summary on the ASBR. Fault 6: OSPF inter-area route summary failed Maipu Confidential & Proprietary Information Page 95 of 124...

  • Page 96: Ospf Error Information Instance

    HELLO: Router Id collision Note According to the previous error information, you can change the OSPF configuration parameters to ensure that the parameters of the two negotiation parties are the same. Maipu Confidential & Proprietary Information Page 96 of 124...

  • Page 97: Rip Troubleshooting

    Tools for Removing RIP Faults Maipu switch provides many tools for finding RIP faults. The show tools and the debug tools are as follows. Show Tools Show ip route rip To quickly display the paths learned through RIP and added to the core routing table.
  • Page 98 : No 4) Passive interface : Disabled 5) Standby interface : None 6) RIP packets send : Enable 7) RIP packets send version : v2 8) RIP packets receive : Enable Maipu Confidential & Proprietary Information Page 98 of 124...
  • Page 99 RIP configuration information and the default configuration information. RIP routing table information: Swtich-A#show ip route rip Codes: C - connected, S - static, R - RIP, O - OSPF, OE-OSPF External, M - Management Maipu Confidential & Proprietary Information Page 99 of 124...

  • Page 100: Rip Troubleshooting

    Use the show run command to check the configuration or use the debug ip rip events command to check the debug information. You can determine the version according to 2d16h: RIP: ignored version 1 (illegal version). Maipu Confidential & Proprietary Information Page 100 of 124...
  • Page 101 ID can be configured. Therefore, you should ensure that the network ID is correct, for example, if a ultra- network ID is configured, the switch interface cannot be added to the RIP interface table. Maipu Confidential & Proprietary Information Page 101 of 124...

  • Page 102: Rip Error Information Instance

    Step 3: Through the collected information, you can generally locate the fault. Then, use the debug tool provided by the system to analyze the packet interaction to find out the cause of the fault. Maipu Confidential & Proprietary Information Page 102 of 124...

  • Page 103: Tools For Removing Bgp Faults

    Mypower S4100 Troubleshooting Tools for Removing BGP Faults Maipu switch provides many tools for finding BGP faults. The show tools and the debug tools are as follows. Show Tools Show ip bgp <CR> To display all IPv4 unicast routing items in the BGP routing table.
  • Page 104 21.1.1.2 remote-as 2 The BGP version, peer router ID. Neighbor status The status, event, error event, and the time of receiving update packets before the BGP neighbor. Maipu Confidential & Proprietary Information Page 104 of 124...
  • Page 105 D e b u g T o o l s debug ip bgp events: Display the BGP event information. debug ip bgp keepalives: Display the receiving and sending information about the BGP keepalive. Maipu Confidential & Proprietary Information Page 105 of 124...

  • Page 106: Bgp Troubleshooting

    How to find out the cause: directly-connected peer Check whether the peer address can be pinged. address is lost from the Solution: routing table. You can add routes to ensure that the peers are connected. Maipu Confidential & Proprietary Information Page 106 of 124...
  • Page 107 Reset the neighbor after the policy configuration is modified. related with the You can use the clear ip bgp to perform soft reset or hard reset. Change weights related with the BGP Change assignment list Maipu Confidential & Proprietary Information Page 107 of 124...

  • Page 108: Bgp Error Information Instance

    The AS number is incorrect when you configure (Open Message Error) subcode 2 (bad AS the peer and the AS number is not the actual AS number) of the peer. Note Maipu Confidential & Proprietary Information Page 108 of 124...

  • Page 109: Is-Is Troubleshooting

    Then, use the debug tool provided by the system to analyze the packet interaction to find out the cause of the fault. Tools for Removing ISIS Faults Maipu switch provides many tools for finding ISIS faults. The show tools and the debug tools are as follows. Show Tools show isis: Check the configuration of the ISIS, including interface running topology, GR, NET address, and route maximum.
  • Page 110 Diagnose ISIS events, including ISIS neighbor. debug isis is-reach-info: Diagnose the process of creating available information between IS protocols. debug isis nsf: Diagnose the interactive process of ISIS GR. Maipu Confidential & Proprietary Information Page 110 of 124...

  • Page 111: Isis Troubleshooting

    ISIS process is matched. Open the debug isis adj- packets to see the prompt message: area address mismatch. Solution: Check the NET address configuration of the ISIS process in the two Maipu Confidential & Proprietary Information Page 111 of 124...
  • Page 112 Recv IIH have same source ID with local system, discard; show run router isis, you can also see whether the system ID is set to the neighbor system ID. Solution: Maipu Confidential & Proprietary Information Page 112 of 124...
  • Page 113 ISIS processes are the same. Solution: Set the metric types set in the two ISIS processes to the same value. Fault 3:IS-IS redistribution failed Possible Judging Methods and Solutions Reasons Maipu Confidential & Proprietary Information Page 113 of 124...
  • Page 114 Check whether the ACL is correct. Solution: Change the corresponding ACL to the right setting. Fault 5: ISIS route summary failed Fault ISIS Judging Methods and Solutions route summary failed Possible Reasons Maipu Confidential & Proprietary Information Page 114 of 124...

  • Page 115: Isis Error Information Instance

    Indicates that the maximum area addresses of the two parties IIH packet prompt are not matched. message; Max area addresses mismatch Information 2: Indicates that the NET addresses are not matched. IIH packet prompt message; area address mismatch Maipu Confidential & Proprietary Information Page 115 of 124...
  • Page 116 IPv4 interface address the opposite IP address). mismatch Information 7: Indicates that the LSP/SNP authentication types or LSP/SNP packet prompt authentication parameters are not matched. information: Authentication Failure Maipu Confidential & Proprietary Information Page 116 of 124...

  • Page 117: Cluster Management Troubleshooting

    Check the result of topology collection is correct. Method: use the show cluster topo information command to check whether the topology collection result is correct. Check whether the status of the member device is correct. Maipu Confidential & Proprietary Information Page 117 of 124...

  • Page 118: Common Cluster Management Troubleshooting

    Fault 3: The status is incorrect after the member is added Possible Judging Methods and Solutions Reasons The member is not Use the show cluster topo information command to check whether the Maipu Confidential & Proprietary Information Page 118 of 124...
  • Page 119 The member In addition, use the show cluster mcmp member command through status changes telnet to check whether the member status is active. when the command switch transmits program files to members Maipu Confidential & Proprietary Information Page 119 of 124...

  • Page 120: Pvlan Troubleshooting

    Check whether the corresponding pvlan is configured. Method: use the show private-vlan command to check whether the required pvlan association is configured. Common PVLAN Troubleshooting Fault 1: Failed to configure a port to a PVLAN Maipu Confidential & Proprietary Information Page 120 of 124...
  • Page 121 The configuration of PVLAN is in conflict with UNI type, configuration QinQ, port isolation, and 802.1X (for details, see the configuration manual). In the process of configuration, the configuration is conflict will be removed. Maipu Confidential & Proprietary Information Page 121 of 124...

  • Page 122: Voice Vlan Troubleshooting

    MAC address is in the range matched by OUI address. Common Voice VLAN Troubleshooting Fault 1: The source MAC address of the sent packets is matched, but the packets are not forwarded through Voice Vlan. Maipu Confidential & Proprietary Information Page 122 of 124...
  • Page 123 Check the configuration of the port to see whether the ACL or the ACL or other rule is other port security rule (the rule is not allowed at the port) is enabled configured Maipu Confidential & Proprietary Information Page 123 of 124...

  • Page 124: Troubleshooting For Special Applications

    Configure different MAC addresses for the switching interfaces through the mac-address command in the interface to ensure the L3 communication in the two interconnected switching interfaces. Maipu Confidential & Proprietary Information Page 124 of 124...

Table of Contents