Troubleshooting - IP Multicast

Transcription

1 rtel Secure Router 8000 Series Troubleshooting - IP Multicast Release: Document Revision: NN A

2 rtel Secure Router 8000 Series Release: 5.3 Publication: NN Document status: Standard Document release date: 30 March 2009 Copyright 2009 rtel Networks All Rights Reserved. Printed in Canada, India, and the United States of America LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. rtel, the rtel logo, and the Globemark are trademarks of rtel Networks. All other trademarks are the property of their respective owners. ATTENTION For information about the safety precautions, read "Safety messages" in this guide. For information about the software license, read "Software license" in this guide.

3 rtel Secure Router 8000 Series Contents Contents About this document IGMP troubleshooting IGMP overview IGMP troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure FAQs Diagnostic tools display commands debugging commands PIM troubleshooting PIM overview PIM-DM principle PIM-SM principle PIM-DM troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure PIM-SM troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure RPT troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure Issue (30 March 2009) rtel Networks Inc. i

4 Contents rtel Secure Router 8000 Series 2.5 RP source tree troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure Static RP troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure BSR-RP troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure BSR troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure PIM-SM SPT troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure FAQs Diagnostic tools display commands debugging commands MSDP troubleshooting MSDP overview MSDP troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure Troubleshooting cases FAQs Diagnostic tools display commands debugging commands ii rtel Networks Inc. Issue (30 March 2009)

5 rtel Secure Router 8000 Series Contents Alarms Logs Multicast VPN troubleshooting MD VPN overview Important concepts in MD VPN Troubleshooting MD VPN Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure Switch-MDT troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure FAQs Diagnostic tools display commands debugging commands Index... i-1 Issue (30 March 2009) rtel Networks Inc. iii

6

7 rtel Secure Router 8000 Series Figures Figures Figure 1-1 IGMP typical network Figure 1-2 IGMP troubleshooting flowchart Figure 2-1 PIM-DM typical networking Figure 2-2 PIM-DM troubleshooting flowchart Figure 2-3 PIM-SM typical networking Figure 2-4 PIM-SM troubleshooting flowchart Figure 2-5 RPT troubleshooting flowchart Figure 2-6 RP source tree troubleshooting flowchart Figure 2-7 Static RP troubleshooting flowchart Figure 2-8 BSR-RP troubleshooting flowchart Figure 2-9 BSR troubleshooting flowchart Figure 2-10 PIM-SM SPT troubleshooting flowchart Figure 3-1 MSDP typical networking Figure 3-2 MSDP troubleshooting flowchart Figure 3-3 MSDP typical networking Figure 4-1 Typical networking of MD VPN Figure 4-2 MD VPN troubleshooting flowchart Figure 4-3 MD VPN typical networking Figure 4-4 Switch-MDT troubleshooting flowchart Issue (30 March 2009) rtel Networks Inc. v

8

9 rtel Secure Router 8000 Series Tables Tables Table 1-1 Description of the display igmp group command output Table 1-2 Description of the display igmp interface command output Table 1-3 Description of the display interface command output Table 1-4 Description of the display igmp routing-table command output Table 1-5 Description of the display igmp ssm-mapping command output Table 2-1 Description of the display pim interface command output Table 2-2 Description of the display pim interface verbose command output Table 2-3 Description of the display pim neighbor command output Table 2-4 Description of the display pim routing-table command output Table 2-5 Description of the display pim bsr-info command output Table 2-6 Description of the display pim rp-info command output Table 2-7 Description of the display pim rp-info [ group-address ] command output Table 2-8 Description of the display multicast routing-table command output Table 2-9 Description of the display multicast forwarding-table command output Table 2-10 Description of the display multicast rpf-info command output Table 3-1 Description of the display msdp brief command output Table 3-2 Description of the display msdp peer-status command output Table 3-3 Description of the display msdp sa-cache command output Table 3-4 Description of the display msdp sa-count command output Table 4-1 display multicast-domain vpn-instance share-group command output Table 4-2 display multicast-domain vpn-instance switch-group receive command output Table 4-3 display multicast-domain vpn-instance switch-group send command output Issue (30 March 2009) rtel Networks Inc. vii

10 rtel Secure Router 8000 Series Contents Contents About this document...1 Issue (30 March 2009) rtel Networks Inc. i

11

12 rtel Secure Router 8000 Series About this document About this document Overview This section describes the organization of this document, product version, intended audience, conventions, and update history. Related versions The following table lists the product versions to which this document relates. Product name rtel Secure Router 8000 Series Version V200R005 Intended audience The intended audiences of this document are: Network operators Network administrators Network maintenance engineers Organization The following table identifies four chapters in this document. Chapter Description 1 IGMP troubleshooting This chapter describes the knowledge related to Internet Group Management Protocol (IGMP) troubleshooting, including IGMP overview, troubleshooting flowchart, troubleshooting procedure in a typical network, troubleshooting cases, diagnostic tools, and frequently asked questions (FAQ). Issue (30 March 2009) rtel Networks Inc. 1

13 About this document rtel Secure Router 8000 Series Chapter Description 2 PIM troubleshooting This chapter describes the knowledge related to Protocol Independent Multicast (PIM) troubleshooting, including PIM overview, troubleshooting flowchart, troubleshooting procedure in a typical network, troubleshooting cases, diagnostic tools, and FAQs. 3 MSDP troubleshooting This chapter describes the knowledge related to Multicast Source Discovery Protocol (MSDP) troubleshooting, including MSDP overview, troubleshooting flowchart, troubleshooting procedure in a typical network, troubleshooting cases, diagnostic tools, and FAQs. 4 Multicast VPN troubleshooting This chapter describes the knowledge related to multicast virtual private network (VPN) troubleshooting, including multicast VPN overview, troubleshooting flowchart, troubleshooting procedure in a typical network, troubleshooting cases, diagnostic tools, and FAQs. Conventions Symbol conventions The following table defines the symbols in this document. Symbol Description Indicates a hazard with a high level of risk that, if you do not avoid, results in death or serious injury. Indicates a hazard with a medium or low level of risk which, if you do not avoid, can result in minor or moderate injury. Indicates a potentially hazardous situation that, if you do not avoid, can cause equipment damage, data loss, and performance degradation or unexpected results. Indicates a tip that can help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text. General conventions Convention Times New Roman Description rmal paragraphs use Times New Roman. 2 rtel Networks Inc. Issue (30 March 2009)

14 rtel Secure Router 8000 Series About this document Convention Boldface Italic Courier New Description Names of files, directories, folders, and users use boldface. For example, log in as user root. Book titles use italics. Terminal display uses Courier New. Command conventions Convention Boldface Italic Description The keywords of a command line use boldface. Command arguments use italics. [ ] Items (keywords or arguments) in square brackets [ ] are optional. { x y... } Alternative items are grouped in braces and separated by vertical bars. Select one of the items. [ x y... ] Optional alternative items are grouped in square brackets and separated by vertical bars. Select one or none of the items. { x y... } * Alternative items are grouped in braces and separated by vertical bars. Select a minimum of one or a maximum of all of the items. [ x y... ] * &<1-n> # Optional alternative items are grouped in square brackets and separated by vertical bars. Select many or none of the items. You can repeat the parameter before the ampersand sign (&) 1 to n times. A line that begins with the number sign (#) indicates comments. GUI conventions Convention Boldface Description Buttons, menus, parameters, tabs, windows, and dialog titles use boldface. For example, click OK. > Multilevel menus use boldface and a greater-than sign (>) separates the menu choices. For example, choose File > Create > Folder. Issue (30 March 2009) rtel Networks Inc. 3

15 About this document rtel Secure Router 8000 Series Keyboard operation Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, press Ctrl+Alt+A means you press the three keys at the same time. Press the keys in turn. For example, press Alt, A means you press the two keys one after the other. Mouse operation Action Click Double-click Drag Description Press and release the primary mouse button without moving the pointer. Quickly press the primary mouse button twice without moving the pointer. Press and hold the primary mouse button and move the pointer to a specific position. Update history Updates between document versions are cumulative. The latest document version contains all updates made to previous versions. Updates in Issue 1.0 ( 6 June 2008 ) The first commercial release. 4 rtel Networks Inc. Issue (30 March 2009)

16 rtel Secure Router 8000 Series Contents Contents 1 IGMP troubleshooting IGMP overview IGMP troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure FAQs Diagnostic tools display commands debugging commands Issue (30 March 2009) rtel Networks Inc. i

17

18 rtel Secure Router 8000 Series Figures Figures Figure 1-1 IGMP typical network Figure 1-2 IGMP troubleshooting flowchart Issue (30 March 2009) rtel Networks Inc. iii

19

20 rtel Secure Router 8000 Series Tables Tables Table 1-1 Description of the display igmp group command output Table 1-2 Description of the display igmp interface command output Table 1-3 Description of the display interface command output Table 1-4 Description of the display igmp routing-table command output Table 1-5 Description of the display igmp ssm-mapping command output Issue (30 March 2009) rtel Networks Inc. v

21

22 rtel Secure Router 8000 Series 1 IGMP troubleshooting 1 IGMP troubleshooting About this chapter The following table describes the contents of this chapter. Section Description 1.1 IGMP overview This section provides the content you must understand before you troubleshoot the Internet Group Management Protocol (IGMP). 1.2 IGMP This section provides notes about configuring IGMP, and provides the IGMP troubleshooting flowchart and the troubleshooting procedure for a typical IGMP network. 1.3 FAQs This section lists frequently asked questions (FAQ) and their answers. 1.4 Diagnostic tools This section describes common diagnostic tools: display commands and debugging commands. Issue (30 March 2009) rtel Networks Inc. 1-1

23 1 IGMP troubleshooting rtel Secure Router 8000 Series 1.1 IGMP overview In the TCP/IP protocol suite, the Internet Group Management Protocol (IGMP) manages the IP multicast members. IGMP sets up and maintains the multicast group relation between IP hosts and their directly-connected multicast routers. The multicast host must support IGMP. The host can join or leave the multicast group at any position and at any time. limit to the number of group members exists. Through IGMP, the multicast router learns if receivers, namely group members of a certain multicast group, exist on the network segment that connects with each interface. The IP host that runs IGMP stores information about the multicast groups it has joined. The router and the host interact in the following manner: The router sends the member query packet to hosts on the local network periodically. The IP host responds to the IGMP member query from the local multicast router by sending the IGMP member report and declares that it joins a certain group. The router then refreshes the local member information according to the received IGMP member report. If no report is received by the deadline, the multicast router believes that there is no member of a specific multicast group on the network segment, and thus cancels forwarding the multicast data. IGMP provides three versions: IGMPv1: defined by RFC1112 IGMPv2: defined by RFC2236, this version is the most common version. IGMPv3 1.2 IGMP troubleshooting This section covers the following topics: Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure Typical networking Figure 1-1 shows a typical IGMP network. Use the following network as an example to explain the IGMP troubleshooting. 1-2 rtel Networks Inc. Issue (30 March 2009)

24 rtel Secure Router 8000 Series 1 IGMP troubleshooting Figure 1-1 IGMP typical network RouterA POS2/0/ /24 GbE1/0/ /24 RouterB POS2/0/ /24 PIM network RouterC POS2/0/ /24 GbE1/0/ /24 GbE1/0/ /24 Ethernet N1 Ethernet N2 HostA Receiver HostB Leaf network HostC Receiver HostD As shown in Figure 1-1: The receiver receives the video on demand (VoD) information in multicast mode. Different receivers constitute the leaf network. Each leaf network uses one or more receivers. Host A and Host C are two receivers of multicast information on two leaf networks. IGMPv2 runs between the routers and the leaf network Configuration notes Item Subitem tes Configuring IGMP Enabling the IP multicast route Enabling the IGMP functions Configuring the IGMP version Setting the IGMP parameter Configuring the IGMP group policy Configuring the IP address of the interface Check the networking Ensure the multicast is enabled. Ensure the interface status is normal. Ensure that all the routers on the same network segment run the same IGMP version. Ensure the IGMP interfaces of all the routers on the same network segment are configured with the same parameters. Ensure the access control list configured on the interface does not limit the group G to join the multicast. Ensure the interface and the host are on the same network segment. Ensure the networking is correct. Issue (30 March 2009) rtel Networks Inc. 1-3

25 1 IGMP troubleshooting rtel Secure Router 8000 Series The following configure example uses the configuration on Router A as an example to explain the configuration of IGMP. The following configuration commands relate only to IGMP. For the detailed configuration, see rtel Secure Router 8000 Series Configuration Guide - IP Routing (NN ). Configuring IGMP # Enable multicast on Router A: [RouterA] multicast routing-enable # Enable the IGMP on the interface through which Router A connects to the leaf network: [RouterA-GigabitEthernet1/0/0] ip address [RouterA-GigabitEthernet1/0/0] igmp enable # Configure the IGMP version to 2: [RouterA-GigabitEthernet1/0/0] igmp version 2 #Enable the IGMP and the Protocol Independent Multicast-Dense Mode (PIM-DM) at the same time: [RouterA-GigabitEthernet1/0/0] pim dm [RouterA-GigabitEthernet1/0/0] quit # Enable PIM-DM on the interface through which Router A connects with the other router. [RouterA] interface pos 2/0/0 [RouterA-Pos2/0/0] ip address [RouterA-Pos2/0/0] pim dm [RouterA-Pos2/0/0] quit Configuring unicast routing # Configure the Open Shortest Path First (OSPF) unicast routing protocol: [RouterA] ospf 1 [RouterA-ospf-1] area [RouterA-ospf-1-area ] network [RouterA-ospf-1-area ] network [RouterA-ospf-1-area ] quit Troubleshooting flowchart In the network shown in Figure 1-1, after you configure IGMP, the (*, G) entry does not appear on the Router A when Host A sends the join message of group G. Figure 1-2 shows the troubleshooting flowchart. 1-4 rtel Networks Inc. Issue (30 March 2009)

26 rtel Secure Router 8000 Series 1 IGMP troubleshooting Figure 1-2 IGMP troubleshooting flowchart IGMP group information on interface Multicast is enabled Enable the multicast Fault is removed? Interface state is normal Esure shutdown is not configured on interface and line and IP address are proper Fault is removed? IGMP is enabled on interface Enable IGMP Fault is removed? ACL is configured Ensure ACL permits the group information Fault is removed? Seek technical support End Troubleshooting procedure The steps of troubleshooting are as follows: Step 1 Check whether the router is enabled with the multicast. Run the display current-configuration command on the router that directly connects to the client segment to check the current configuration on the router. If the output does not contain the multicast routing-enable command, rtel recommends that you run the command in the system view to enable the multicast function. Then add other necessary IGMP configurations. In a multicast network, rtel recommends that you enable the multicast function on all routers. Step 2 Check that the interface status is normal. On the current router, use the display igmp interface interface-type interface-number command to specify the interface on the router that directly connects with the client segment. Check whether the information on the outgoing interface appears. Issue (30 March 2009) rtel Networks Inc. 1-5

27 1 IGMP troubleshooting rtel Secure Router 8000 Series If no information appears, you can infer that the interface status is abnormal. The troubleshooting procedure is as follows: 1. Check whether the interface is configured with the shutdown command. Run the display current-configuration interface interface-type interface-number command to check the current configuration on the interface. If the shutdown command appears in the display, run the undo shutdown command in the interface view to cancel the configuration. 2. Check that the interface line is correct. The line fault can also lead to the down state of the interface. If the line is incorrectly connected, adjust the networking and the interface line. 3. Check that the interface is configured with an IP address. Run the display current-configuration interface interface-type interface-number command to check the interface address. If the interface is not configured with an IP address or the address and the host are not on the same segment, reset the IP address of the interface. If the interface address and the host address are not on the same network segment, the received group member report is discarded. When configuring the multicast network, ensure that all the IP addresses of the interfaces directly connect with the client and the host address is on the same network segment. Step 3 Check that the interface is enabled with IGMP. Run the display current-configuration interface interface-type interface-number command on the current router to check the configuration on the interface that directly connects to the client. If the display does not contain the igmp enable command, it means IGMP is not enabled. You need to run the igmp enable command in the interface view to enable IGMP. Step 4 Check whether the interface is configured with the access control list (ACL). Run the display current-configuration interface interface-type interface-number command on the current router to check the configuration on the interface that directly connects to the client. If the display includes the igmp group-policy acl-number [ ] command, it means the multicast group filter is configured on the interface. IGMP filters the join message according to the specified ACL. Check the group range permitted in the ACL. If G is not in the range, modify the ACL or cancel the command. Ensure that IGMP can serve the member of G. ----End If the fault persists, contact rtel technical personnel. 1-6 rtel Networks Inc. Issue (30 March 2009)

28 rtel Secure Router 8000 Series 1 IGMP troubleshooting 1.3 FAQs Q: How does the IGMP on the shared network segment elect the querier? A: The shared network segment refers to the segment shared by multiple multicast routers. On the shared segment, all the multicast routers that run IGMP can receive the member report from the host. Only one router needs to send the member query. An election mechanism must be initiated. In IGMPv1, the multicast routing protocol decides the election of the querier. In IGMPv2, on the shared segment, the multicast router with the smallest IP address is the querier. Q: How does the IGMP judge whether a group member exists on the network segment? A: In IGMPv1, the host does not send a message when it leaves a multicast group. After the response of the member query times out, the multicast router learns that all the members left the multicast group. In IGMPv2, after leaving a multicast group, a host sends a leaving group message. After receiving a leave message, the querier sends the specific group query message. In the specific group query, the destination IP address is the IP address of the multicast group and the group address is the IP address of the multicast group. If a group member exists on the network segment, it responds with a report message. If the querier receives no response message after the timer times out, the querier judges that no member of the group exists on the network segment. Q: Why is the relation between IGMP members among different routers on the same network segment not consistent? A: IGMP provides three versions. The router and the host with different versions are compatible. All the routers on the same network segment must use the same version; if not, the relation between IGMP group members becomes disordered. Run the display igmp interface interface-type interface-number command on all the routers on the same network segment to check the IGMP version. Ensure that all the routers on the same segment use the same version. Q: Why is the IGMP member relation inconsistent even though routers on the same network segment use the same IGMP version? A: The router that runs IGMP maintains multiple parameters on each interface. The parameters affect each other. The situation is complex. If routers on the same network segment are configured with different parameters, the relation between IGMP group members becomes disordered. The main parameters that can be configured by IGMP are as follows: robust-count: used to adjust the robustness of the IGMP router Issue (30 March 2009) rtel Networks Inc. 1-7

29 1 IGMP troubleshooting rtel Secure Router 8000 Series The IGMP router can lose IGMP report messages of robust-count minus one. The greater the robust-count is, the more reliable the IGMP router. The timeout time of the group increases with the robust-count. By default, the robust-count is 2. query-interval: indicates the interval of sending the general query message by the IGMP querier periodically The smaller the query-interval is, the more sensitive the IGMP router. The IGMP packets increase at the same time. By default, the query-interval is 60 seconds. max-response-time: indicates the maximum response time of the general-group query This parameter manages the deadline by which the host sends a report message. The time that the host actually responds is any value from 0 to query-response interval. The shorter the query-response time is, the faster the speed of IGMP routers receiving the information of multicast members. The IGMP packets increase at the same time. By default, the max-response-time is 10 seconds. relation-interval: The IGMP router manages the timeout time of each group according to the relation-interval. Within the relation-interval, if no member relation report is received, the router considers the group to be expired and then deletes information about the group. The following formula indicates the relation-interval and the preceding three parameters: relation-interval = robust-count x query-interval + response-interval. other-querier-present: If there are multiple routers on the same network segment, the router with the smallest IP address is elected as the querier. The new querier is elected only when the querier loses its effect or a router with a smaller IP address is added. Each router other than the querier maintains a timer. If no query message is received by the router within other-querier-present, the querier is considered unavailable. The new querier is then elected. other-querier-present = robust-count x query-interval Start-query-interval: When the querier starts, it sends general query messages at the start-query-interval. Start-query-times: When the querier starts, it sends general query messages by the times of the start-query-times. Last-member-query-interval: It controls the deadline on which the host sends the report message. The smaller the last-member-query-interval, the quicker the querier responses to the exit of the host from the group. By default, the last-member-query-interval is 1 second. Last-member-query-times: When the querier receives a leave message sent by the host, the querier sends specified query messages of the number specified by last-member-query-times according to last-member-query-interval. By default, the value of last-member-query-times equals the robust-count. The multiple parameters on the IGMP interface restrict each other. Therefore, the parameters on the IGMP interface of all the routers on the same network segment must be the same. Run the display igmp interface interface-type interface-number command on all the routers on the same network segment to check the IGMP parameters. Ensure all the parameters are the same. 1-8 rtel Networks Inc. Issue (30 March 2009)

30 rtel Secure Router 8000 Series 1 IGMP troubleshooting Q: The interface is enabled with Source Specific Multicast (SSM) mapping and IGMP. In addition, the interface is configured with the static mapping policy. The interface can receive the IGMPv1 and IGMPv2 reports. Why does the translated (S, G) not appear in the forwarding table? A: After the querier is configured with SSM mapping, when the querier receives the IGMPv1 and IGMPv2 report (*, G), SSM mapping checks the group address. The querier can translate the received IGMPv1 and IGMPv2 packet into one or multiple include sources (S, G) and thus enable the SSM function only when the group address is within the SSM range and you configure the matching command of SSM Mapping. The possible causes for the fault are: G is not in the SSM range. Run the display current-configuration configuration pim command in the PIM view to check the specified SSM range on the current router. Check whether G is within the SSM range. The G is not in static mapping policy of the source group of the SSM mapping. Run the display igmp ssm-mapping group command to check the SSM mapping information about the specified source/group address configured on the current router. Check whether group G is specified with the proper mapping policy. Check whether the mask is the same. 1.4 Diagnostic tools display commands Command display version display current-configuration display igmp group display igmp interface Description Displays the version information. The version number is used to locate the code error. Displays the configuration on the current router. The command displays all the configurations on the router. Displays information about the group. Check whether the specific group information exists. Displays the IGMP version information and the configuration of the timer, querier address, and group filter on the interface. Check whether the interface status and configuration are normal. display igmp group The command checks information about the member of the specified multicast group or the group on a certain interface. Issue (30 March 2009) rtel Networks Inc. 1-9

31 1 IGMP troubleshooting rtel Secure Router 8000 Series The display igmp group command displays information about the multicast group that the downstream host dynamically joins by sending the IGMP joining message. The display igmp group static command displays information about the multicast group that the host statically joins by configuring command lines on the current router. The display igmp group ssm-mapping command displays information about the multicast group of the enabled SSM mapping. <rtel> display igmp group IGMP interface group report information of VPN-Instance: public net GigabitEthernet1/0/0 ( ): Total 2 IGMP Group reported Group Address Last Reporter Uptime Expires :01:44 00:00: :02:04 00:01:15 Table 1-1 Description of the display igmp group command output Item Group address Last Reporter Uptime Expires Description Address of the multicast group Indicates the last host that reports to be the member of the group. After the host sends the member report, the report of the host of other groups is suppressed. That does not mean the host is the only member of the multicast group. Indicates the period from the discovery of the multicast group to the current time Time that the member is deleted from the IGMP group table in the format of hour: minute: second. display igmp interface The command checks the IGMP configuration and the running information on the interface. If the IGMP configuration and the running information on an interface do not exist, it means the interface is not enabled with IGMP. The possible causes are: The system is not enabled with the multicast function. Therefore, you cannot enable IGMP on the interface. The interface is not configured with the IP address. Therefore, you cannot enable IGMP on the interface. The interface state is Down. Therefore, you cannot enable IGMP on the interface. <rtel> display igmp interface gigabitethernet 1/0/0 GigabitEthernet1/0/0( ): IGMP is enabled Current IGMP version is 2 Value of query interval for IGMP(in seconds): 60 Value of other querier timeout for IGMP(in seconds): 0 Value of maximum query response time for IGMP(in seconds): rtel Networks Inc. Issue (30 March 2009)

32 rtel Secure Router 8000 Series 1 IGMP troubleshooting Querier for IGMP: (this router) Table 1-2 Description of the display igmp interface command output Item GigabitEthernet1/0/0( ) IGMP is enabled Current IGMP version Value of query interval for IGMP Value of other querier time out for IGMP Value of maximum query response time for IGMP Querier for IGMP Description Indicates the interface name (IP address). IGMP is enabled on the interface. Indicates the IGMP version number used by the interface. By default, it is 2. Using the igmp version command, you can configure the version number. Indicates the interval of sending the IGMP query on the interface in seconds. The default is 60 seconds. Using the igmp timer query command, you can configure the interval. Indicates the timeout time of the IGMP querier in seconds. The default is 120 seconds. Using the igmp timer other-querier-present command, you can configure the timeout time. Indicates the maximum response time to the IGMP query in seconds. The default is 10 seconds. Using the igmp max-response-time command, you can configure the value. Indicates the querier on the interface. In IGMPv1, the multicast routing protocol decides the election of the querier. In IGMPv2, the router with smallest IP address is elected as the querier. display interface <rtel> display interface ethernet 1/0/1 Ethernet1/0/1 current state : UP Line protocol current state : UP IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is e2e-ca5d Internet Address is /24 Description : rtel Series, Ethernet1/0/1 Interface The Maximum Transmit Unit is 1500 Media type is twisted pair 10Mbps-speed mode, full-duplex mode Output queue : (Urgent queue : Size/Length/Discards) 0/50/0 Output queue : (Protocol queue : Size/Length/Discards) 0/500/0 Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0 Last 5 minutes input rate 282 bytes/sec, 4 packets/sec Issue (30 March 2009) rtel Networks Inc. 1-11

33 1 IGMP troubleshooting rtel Secure Router 8000 Series Last 5 minutes output rate 98 bytes/sec, 1 packets/sec Input: 1918 packets, bytes 923 broadcasts, 121 multicasts 0 errors, 0 runts, 0 giants, 0 CRC, 0 collisions, 0 BD errors 0 packets with dribble condition detected Output:576 packets, bytes 3 broadcasts, 0 multicasts 0 errors, 0 underruns, 0 collisions 0 packets had been deferred Table 1-3 Description of the display interface command output Item Ethernet1/0/1 current state : Description Physical status of the Ethernet 1/0/1: Up: indicates the interface is in the enabled state. Down: indicates that a fault occurs on the physical interface. Administratively Down: If the network administrator runs the shutdown command on the interface, the status of the interface is displayed as Administratively Down. Line protocol current state : IP Sending Frames' Format is The software running on the interface is in the enabled state. If the software is not properly processed or the interface is not configured with the IP address, the link protocol of the interface is in the Down state. The Ethernet frame sent by the interface The frames that the Ethernet can identify: Ethernet_II Ethernet_SNAP Hardware address is Internet Address is Description : The Maximum Transmit Unit is Media type is twisted pair 10Mbps-speed mode full-duplex mode The Media Access Control address of the interface IP address and mask length set on the interface Description about an interface, which is convenient for users to know the function of the interface The maximum transmission unit of an interface. The default value is 1500 bytes. The packet with a size greater than the maximum transmission unit is fragmented and then sent. The packet cannot be fragmented, it is discarded. Media type of the interface is the twisted pair. The rate is 10 Mb/s. For the 10/100 Mb/s interface, you can run the speed command to change the working rate of the interface. The working mode is full-duplex. For the circuit interface with 10/100 Mb, you can run the duplex command to the change the setting on the interface rtel Networks Inc. Issue (30 March 2009)

34 rtel Secure Router 8000 Series 1 IGMP troubleshooting Item Output queue : (Urgent queue : Size/Length/Discards ) 0/50/0 Output queue : (Protocol queue : Size/Length/Discards ) 0/500/0 Output queue : (FIFO queuing : Size/Length/Discards ) 0/75/0 Last 5 minutes input rate 282 bytes/sec, 4 packets/sec Last 5 minutes output rate 98 bytes/sec, 1 packets/sec Input: 1918 packets, bytes broadcasts multicasts errors runts giants CRC collisions 0 packets with dribble condition detected Output:576 packets, bytes underruns packets had been deferred Description The meaning of the Size/Length/Discards field is as follows: Size: number of the packets in the queue. Length: the maximum size of the queue, expressed by the number of packets. Discards: the number of the packets discarded because the queue is full. Checking the relation between Discards and Size and the relation between Discards and Length, you can judge whether the performance of the interface meets the requirement. For example, if the value of Discards is greater, the router does not process the packets timely. If the situation lasts for a long time, you need a more powerful router. Indicates the rate of the byte and the packets that pass through the interface in the last five minutes. If the interface is in the hybrid mode, that is, it reads about all the packets on the LAN, you can use the field to test the traffic. If the interface is not in the hybrid mode, that is, it records only the traffic sent and received by itself, the field displays only the traffic sent and received by the interface. The total number of the packets and bytes received on the interface The number of the received or sent broadcast packets The number of the received or sent multicast packets The number of the error packets detected at the physical layer The number of the received packets that are smaller than 64 bytes The number of the received packets that are greater than 1500 bytes The number of the received packets whose length is proper but the cyclic redundancy check is incorrect The number of the packet collisions detected when received or sent The number of the received packets containing the dribble condition. Error dribble indicates that the size of the frame is too large. The number of the packets and bytes sent by the interface The number of the packets that cannot be sent because the speed at which the interface reads the cache is lower than the forwarding rate. The number of packets that cannot be forwarded because the timeout of the delay Issue (30 March 2009) rtel Networks Inc. 1-13

35 1 IGMP troubleshooting rtel Secure Router 8000 Series display igmp routing-table This command checks the IGMP routing table on a router. The display igmp routing-table can display all IGMP routing entries on a router. The display igmp routing-table static command can display only the IGMP routing entries that are generated by the statically joined multicast groups. <rtel> display igmp routing-table IGMP routing table of VPN-Instance: public net Total 1 entry (*, ) List of 1 downstream interface GigabitEthernet6/2/0 ( ), Protocol: IGMP Table 1-4 Description of the display igmp routing-table command output Item IGMP routing table of VPN-Instance: public net Total 1 entry Description IGMP routing table of the public network Total number of the IGMP routing entry (*, ) Number entry, (* G) List of 1 downstream interface GigabitEthernet6/2/0 ( ) Protocol The only one downstream interface Interface number (address) Protocol type: IGMP display igmp ssm-mapping <rtel> display igmp ssm-mapping IGMP SSM-Mapping conversion table of VPN-Instance: public net Total 2 entries ( , ) ( , ) Total 2 entries matched Table 1-5 Description of the display igmp ssm-mapping command output Item IGMP SSM-Mapping conversion table of VPN-Instance: public net Total 2 entries Description IGMP SSM-mapping conversion table of the public network instance Total number of the SSM mapping entries ( , ) Number entry The group is mapped to the source Total 2 entries matched Total number of the matching entries 1-14 rtel Networks Inc. Issue (30 March 2009)

36 rtel Secure Router 8000 Series 1 IGMP troubleshooting debugging commands Command debugging igmp debugging igmp ssm-mapping Description Enables the IGMP debugging. Enables the SSM mapping debugging. Issue (30 March 2009) rtel Networks Inc. 1-15

37 rtel Secure Router 8000 Series Contents Contents 2 PIM troubleshooting PIM overview PIM-DM principle PIM-SM principle PIM-DM troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure PIM-SM troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure RPT troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure RP source tree troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure Static RP troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure BSR-RP troubleshooting Typical networking Configuration notes Issue (30 March 2009) rtel Networks Inc. i

38 Contents rtel Secure Router 8000 Series Troubleshooting flowchart Troubleshooting procedure BSR troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure PIM-SM SPT troubleshooting Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure FAQs Diagnostic tools display commands debugging commands ii rtel Networks Inc. Issue (30 March 2009)

39 rtel Secure Router 8000 Series Figures Figures Figure 2-1 PIM-DM typical networking Figure 2-2 PIM-DM troubleshooting flowchart Figure 2-3 PIM-SM typical networking Figure 2-4 PIM-SM troubleshooting flowchart Figure 2-5 RPT troubleshooting flowchart Figure 2-6 RP source tree troubleshooting flowchart Figure 2-7 Static RP troubleshooting flowchart Figure 2-8 BSR-RP troubleshooting flowchart Figure 2-9 BSR troubleshooting flowchart Figure 2-10 PIM-SM SPT troubleshooting flowchart Issue (30 March 2009) rtel Networks Inc. iii

40

41 rtel Secure Router 8000 Series Tables Tables Table 2-1 Description of the display pim interface command output Table 2-2 Description of the display pim interface verbose command output Table 2-3 Description of the display pim neighbor command output Table 2-4 Description of the display pim routing-table command output Table 2-5 Description of the display pim bsr-info command output Table 2-6 Description of the display pim rp-info command output Table 2-7 Description of the display pim rp-info [ group-address ] command output Table 2-8 Description of the display multicast routing-table command output Table 2-9 Description of the display multicast forwarding-table command output Table 2-10 Description of the display multicast rpf-info command output Issue (30 March 2009) rtel Networks Inc. v

42

43 rtel Secure Router 8000 Series 2 PIM troubleshooting 2 PIM troubleshooting About this chapter The following table describes the contents of this chapter. Section Description 2.1 PIM overview This section provides the knowledge you need before you troubleshoot the Protocol Independent Multicast (PIM). 2.2 PIM-DM troubleshooting This section provides notes about configuring PIM-Dense Mode (DM), the PIM-DM troubleshooting flowchart, and the troubleshooting procedure in a typical PIM-DM network. 2.3 PIM-SM troubleshooting This section provides notes about configuring PIM-Sparse Mode (SM), the PIM-SM troubleshooting flowchart, and the troubleshooting procedure in a typical PIM-SM network. 2.4 RPT troubleshooting This section provides notes about configuring a rendezvous point tree (RPT), the RPT troubleshooting flowchart, and the troubleshooting procedure in a typical RPT network. 2.5 RP source tree troubleshooting This section provides notes about configuring the rendezvous point (RP) source tree, the RP source tree troubleshooting flowchart, and the troubleshooting procedure in a typical RP source tree network. 2.6 Static RP troubleshooting This section provides notes about configuring static RP, the static RP troubleshooting flowchart, and the troubleshooting procedure in a typical PIM-SM network. 2.7 BSR-RP troubleshooting This section provides notes about configuring the BootStrap Router (BSR)-RP, the BSR-RP troubleshooting flowchart, and the troubleshooting procedure in a typical BSR-RP network. Issue (30 March 2009) rtel Networks Inc. 2-1

44 2 PIM troubleshooting rtel Secure Router 8000 Series Section Description 2.8 BSR troubleshooting This section provides notes about configuring the BSR, the BSR troubleshooting flowchart, and the troubleshooting procedure in a typical BSR network. 2.9 PIM-SM SPT troubleshooting This section provides notes about configuring PIM-SM shortest path tree (SPT), the PIM-SM SPT troubleshooting flowchart, and the troubleshooting procedure in a typical PIM-SM SPT network FAQs This section lists frequently asked questions and their answers Diagnostic tools This section describes common diagnostic tools: display commands and debugging commands. 2-2 rtel Networks Inc. Issue (30 March 2009)

45 rtel Secure Router 8000 Series 2 PIM troubleshooting 2.1 PIM overview PIM stands for Protocol Independent Multicast. The multicast route can work in coordination only with the unicast route. The multicast route is independent from a specific unicast routing protocol. The unicast routing protocols that provide the routing information for PIM include the static route, Routing Information Protocol (RIP), Open Shortest Path First (OSPF), Intermediate System-to-Intermediate System (IS-IS), and Border Gateway Protocol (BGP). By using the unicast routing information, PIM can exert the Reverse Path Forwarding (RPF) mechanism and create multicast routes. The Any-Source Multicast (ASM) model has two modes: PIM-DM PIM-SM The realization of the Source-Specific Multicast (SSM) model needs partial PIM-SM technology PIM-DM principle For more information about PIM, see rtel Secure Router 8000 Series Configuration Guide - IP Routing (NN ). PIM-DM assumes that at least one multicast group member exists on each network segment in the initialization. The multicast packet is sent to all the routers on the network, which consumes the bandwidth and CPU of the router. To optimize resource utilization, PIM-DM prunes the branch that does not forward multicast data. The branch that contains the receiver of multicast data is reserved. The pruned branch can become active and receive the multicast data afresh periodically. To reduce the time taken by the pruned branch to restore the forwarding state, PIM-DM adopts the graft mechanism to restore the multicast forwarding automatically. PIM-DM featuring spread and prune is suitable only for small-scale LANs with dense multicast group members. The spread and prune technology is not recommended for a WAN. In PIM-DM, the forwarding path of the data packet is a tree with the multicast source as the root, the transmission path as the branch, and the receiver as the leaf. The tree adopts the shortest path from the multicast source to the receiver, the Shortest Path Tree (SPT) PIM-SM principle PIM-SM assumes no multicast member exists on all the network segments during the initialization. The multicast forwarding path is set up only when a host sends the join message. PIM-SM chooses a certain router as the rendezvous point (RP). Using the RP as the root, PIM-SM constructs and maintains a multicast forwarding tree, called RPT. PIM-SM implements the multicast forwarding in the following manner: Issue (30 March 2009) rtel Networks Inc. 2-3

46 2 PIM troubleshooting rtel Secure Router 8000 Series 1. The Designated Router (DR) at the client-end performs the joining process to the RP. The routers on the path then set up or update the (*, G) forwarding entry. The new RPT branch is created. 2. The DR on the source end registers on the RP. When the registration packet reaches the RP, the RP performs the join process to the DR on the source end. The routers on the path set up the (S, G) forwarding entry. The source tree between RP and the source is set up. 3. The multicast source sends the multicast data to the RP along the source tree. The data is then sent to the receiver along the RP tree (RPT). The routers on the RPT set up the (S, G) forwarding entry. 4. The DR on the receiver side receives the multicast data and performs the join process to the multicast source. The routers on the path set up the (S, G) forwarding entry or add some downstream interface. Thus, the SPT branch is created. 5. Along the SPT, the packet reaches the DR on the receiver end. The routers on the path update the upstream interface of the (S, G) forwarding entry. At the same time, the prune is triggered. The transmission path that does not agree with the SPT is deleted hop-by-hop upstream. 6. The switchover from the RPT to SPT ends. The packet reaches the receiver only along the SPT. PIM-SM is suitable for a large-scale network where the group member spread widely. Through the RP, the multicast forwarding reduces the bandwidth consumed by the data packet and the control packet, and thus reduces the cost of the router. 2.2 PIM-DM troubleshooting This section covers the following topics: Typical networking Configuration notes Troubleshooting flowchart Troubleshooting procedure Typical networking Figure 2-1 shows a typical network. Use the following network as an example to explain the PIM-DM troubleshooting. 2-4 rtel Networks Inc. Issue (30 March 2009)