Troubleshooting end-user can’t ping gateway successfully

In an STP-enablednetwork with dual core switches, a client accessing the network cannot ping thegateway successfully.

2.3.1   Possible Causes

1) STA between the core and access switches is incorrect.

2) The MSTP domain configuration between the core and access switches is incorrect.

3) The allowed VLANs configured for interfaces between switches aredifferent, which causes abnormal data communication.

4) Other functions (such as RLDP and BPDU Guard) are configured for interfaces between switches, which causes that the interfaces are shut down and in non-forwarding status.

2.3.2   Troubleshooting Procedure

Step 1: Check the STP status between the access and core switches.

Step 2: Check the link configurations between the access and coreswitches.

Step 3: Check the VLAN interconnectivity between the access and core switches.

Step 4: Check whether the interfaces of the access and core switches are in the forwarding state.

Step 5: Check the MAC addresses of the clients connecting the access and core switches.

Step 6: Collect fault information and submit cases to Ruijie Service Portal.

Step1: Check the STP status between the access and coreswitches.

1. Check the status of the interfaces between the access and core switches (including the convergence switches) and ensure that the instances to which the member VLANs of the interfaces belong are in theforwarding state.

show spanning-tree interface xx

If the instances to which the member VLANs of the interfaces belong are not in the forwarding state, go to Step 2.

Step2: Check the link configurations between the accessand core switches.

1. Check whether the VLAN instances of the interfaces between the access and core switches are consistent. If the VLAN instance configurations in MSTP are incorrect, STA cannot be conducted in the same MSTP domain. If different STP modes are configured on different switches,certain unexpected results may occur.

The checking method is as follows:

1) Run the show run commandto check instance-related content in the STP configuration.

2) Check the MSTP configurations of all switches in the topology and ensure that the MSTP domain configurations are consistent.

Step3: Check the VLAN interconnectivity between the accessand core switches.

1. Check whether the interfaces between the accessand core switches allow member VLANs, that is, whether there is data of allowed VLANs passing the dual uplink links.

show run interface xxx //Display theVLAN configuration of an interface.

2. Check the configurations of VLAN allowed by aninterface. Incorrect configurations may cause that the actual data forwardingis incompliant with the VLAN-instance mapping rule.

For example, in a dual-core topology,based on MSTP, the interface of a VLAN corresponding to an instance on anaccess-layer convergence switch is in the forwarding state. However, the VLAN has not been configured, which blocks data flowing.

3. Set the spanning-tree cost of interfaces tomodify the shape of the spanning tree, and ensure that the VLAN configurationson the interfaces and the forwarding state are consistent.

Step4: Check whether the interfaces between the access and core switches are in the forwarding state.

1. Check whether the interfaces between the accessand core switches are in the forwarding state. Because of RLDP or BPDU Guard,the interfaces may be blocked or shut down. Particularly, check whether certain functions supported block the interfaces.

Run the following command for checking: show interface status.

Notes

To ensure that RSTP or MSTP on Ruijie switches and H3C switches are compatible, you need to configure the packet format on H3C switch interfaces as compliant with the 802.1S standard by using the stp compliance command. In addition, you need to configure the default path cost to be calculated according to the IEEE 802.1t standard by using the dot1t command. If the above are not configured, the H3C switches will shut down the interfaces connecting to Ruijie switches.

Step5: Check the MAC addresses of clients connecting the access and core switches.

Check the MAC addresses of the clients connecting the access and core switches by running the show mac-address-table command. If the MAC addresses of the clients are all displayed, and the MAC addresses can still be learned after the clear mac-address-table command is executed, the fault may not be caused by STP.

If the MAC addresses of the clients are not displayed on the core switches but available on the access switches, unplug either of the dual links. If the fault remains, go to Step 6.

Step6: Collect fault information and submit cases toRuijie Service Portal.

If the fault is not rectified through the preceding steps, collect the following information and the analysis information obtained in steps 1 to 4. Submit cases to Ruijie Service Portal for further handling.

Collect the network topology informationon all STP-enabled devices.

show runnig-config

show spanning-tree

show spanning-tree summary

show spanning-tress interface xx (Switch interface)

show version

show version slot //Chassis switch slot