Involved Products and Versions

All products and versions

Networking

As shown in Figure 1-1, Eth-Trunk3 is created between Switch-1 and Switch-2, and Eth-Trunk20 is created between Switch-2 and Switch-3. An Eth-Trunk is created between Switch-2 and the NE40E. Eth-Trunk1 is located on Switch-2, and Eth-Trunk1.43 is located on the NE40E.

Figure 1-1 Networking diagram for the fault that the IPTV service is abnormal after a switch is powered off and reset

Fault Symptom

After Switch-2 restarts, users connected to the OLT encounter abnormal IPTV services and cannot watch live TV programs.

Cause Analysis

The interface Eth-Trunk20 of Switch-2 receives PIM Hello packets from other interfaces and forwards them to the NE40E. In this case, the NE40E does not become the PIM DR, and traffic cannot be imported to the connected OLT. As a result, users cannot watch multicast programs.

Troubleshooting Procedure

                          Step 1     Simulate users' multicast requests in the OLT. It is found that multicast entries can be generated on Switch-1 in a short period.

<Switch-1> display igmp-snooping port-info verbose
 
The port information of Group 239.16.10.6 on VLAN 43:
Time of this group has been up : 00:00:06
 
The port information of (0.0.0.0, 239.16.10.6):
Time of this source has been up : 00:00:06
Port Table on this source(0.0.0.0):
No.1
Port name : Eth-Trunk10
Time of this port has been up as a host-port : 00:00:06
Remain time of port expire as dynamic host-port : 00:02:06
Host-port flags : Dynamic

                          Step 2     Log in to the NE40E and check the downstream interface Eth-Trunk1.43. It is found that there are five PIM neighbors and the PIM DR of VLAN 43 is not the NE40E. Therefore, the NE40E cannot import multicast traffic to the OLT.

<NE40E> display pim neighbor  
VPN-Instance: public net
Total Number of Neighbors = 11
 
Neighbor        Interface     Uptime   Expires  Dr-Priority BFD-Session  
219.150.177.33  GE1/1/0       32w:5d   00:01:39 1           N 
219.150.179.173 GE1/1/1       32w:5d   00:01:45 1           N 
219.150.177.133 GE2/1/0       32w:5d   00:01:38 1           N 
219.150.179.13  GE2/1/1       32w:5d   00:01:20 1           N 
10.138.12.1    Eth-Trunk1.43 3d:09h   00:01:45 1           N 
10.138.10.1    Eth-Trunk1.43 3d:09h   00:01:45 1           N 
10.138.6.1     Eth-Trunk1.43 3d:09h   00:01:45 1           N 
10.137.244.1   Eth-Trunk1.43 3d:09h   00:01:45 1           N 
10.138.8.1     Eth-Trunk1.43 3d:09h   00:01:45 1           N

                          Step 3     Log in to Switch-2 and print debugging information. It is found that PIM Hello packets with five different source IP addresses are received from Eth-Trunk20.

*43.3358195201 Switch-2 SNPG/7/PACKET:Received Packet (protocol = 103) from 10.138.8.1 to 224.0.0.13, type 0x20 on (VLAN 43 Eth-Trunk20 ) (SNPG_INIT2161)
*43.3358195202 Switch-2 SNPG/7/QUERY:Received hello packet with unsupported option: 65004,option ignored (SNPG_ROUTER1175)
*43.3358195202 Switch-2 SNPG/7/QUERY:Received pim hello packet. (SNPG_ROUTER1194)
*43.3358195203 Switch-2 SNPG/7/PACKET:Received a pim hello Packet from 10.138.8.1 to 224.0.0.13 (SNPG_INIT2220)
*43.3358195204 Switch-2 SNPG/7/PACKET:Received Packet (protocol = 103) from 10.137.244.1 to 224.0.0.13, type 0x20 on (VLAN 43 Eth-Trunk20 ) (SNPG_INIT2161)
*43.3358195212 Switch-2 SNPG/7/QUERY:Received hello packet with unsupported option: 65004,option ignored (SNPG_ROUTER1175)
*43.3358195212 Switch-2 SNPG/7/QUERY:Received pim hello packet. (SNPG_ROUTER1194)
*43.3358195213 Switch-2 SNPG/7/PACKET:Received a pim hello Packet from 10.137.244.1 to 224.0.0.13 (SNPG_INIT2220)
*43.3358195214 Switch-2 SNPG/7/PACKET:Received Packet (protocol = 103) from 10.138.12.1 to 224.0.0.13, type 0x20 on (VLAN 43 Eth-Trunk20 ) (SNPG_INIT2161)
*43.3358195214 Switch-2 SNPG/7/QUERY:Received hello packet with unsupported option: 65004,option ignored (SNPG_ROUTER1175)
*43.3358195215 Switch-2 SNPG/7/QUERY:Received pim hello packet. (SNPG_ROUTER1194)
*43.3358195215 Switch-2 SNPG/7/PACKET:Received a pim hello Packet from 10.138.12.1 to 224.0.0.13 (SNPG_INIT2220)
*43.3358195216 Switch-2 SNPG/7/PACKET:Received Packet (protocol = 103) from 10.138.10.1 to 224.0.0.13, type 0x20 on (VLAN 43 Eth-Trunk20 ) (SNPG_INIT2161)
*43.3358195217 Switch-2 SNPG/7/QUERY:Received hello packet with unsupported option: 65004,option ignored (SNPG_ROUTER1175)
*43.3358195217 Switch-2 SNPG/7/QUERY:Received pim hello packet. (SNPG_ROUTER1194)
*43.3358195218 Switch-2 SNPG/7/PACKET:Received a pim hello Packet from 10.138.10.1 to 224.0.0.13 (SNPG_INIT2220)
*43.3358195219 Switch-2 SNPG/7/PACKET:Received Packet (protocol = 103) from 10.138.6.1 to 224.0.0.13, type 0x20 on (VLAN 43 Eth-Trunk20 ) (SNPG_INIT2161)
*43.3358195219 Switch-2 SNPG/7/QUERY:Received hello packet with unsupported option: 65004,option ignored (SNPG_ROUTER1175)
*43.3358195220 Switch-2 SNPG/7/PACKET:Received a pim hello Packet from 10.138.6.1 to 224.0.0.13 (SNPG_INIT2220)

                          Step 4     Check Switch-2. It is found that there are two multicast upstream interfaces in VLAN 43. Eth-Trunk20 was generated three days ago.

<Switch-2> display igmp-snooping router-port vlan 43
Port Name     UpTime     Expires     Flags 
---------------------------------------------------------------------
VLAN 43, 2 router-port(s)
Eth-Trunk1    15w:5d     00:01:35    DYNAMIC 
Eth-Trunk20  3d:09h    00:01:23    DYNAMIC

                          Step 5     Check the Eth-Trunk20 configuration on Switch-2. Run the undo port trunk allow-pass vlan 43 command to remove VLAN 43 to restore the current service.

[Switch-2-Eth-Trunk20] display this
#
interface Eth-Trunk20
 port link-type trunk
 undo port trunk allow-pass vlan 1
 port trunk allow-pass vlan 43 46 51 54 70 87 90 to 92 95 to 96 501 to 772 885 to 899
 traffic-policy tttt outbound
 undo port trunk allow-pass vlan 43

----End