HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
55 Displaying and maintaining PIM snooping Task Command Remarks Display PIM snooping neighbor information. display pim-snooping neighbor [ vlan vlan-id ] [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] Available in any view Display PIM snooping routing entries. display pim-snooping routing-table [ vlan vlan-id ] [ slot slot-number ] [ | { begin | exclude | include } regular-expression ] Available in any view Display the statistics information of PIM messages learned by PIM snooping. display pim-snooping statistics [ | { begin | exclude | include } regular-expression ] Available in any view Clear the statistics information of PIM messages learned by PIM snooping. reset pim-snooping statistics Available in user view PIM snooping configuration example Network requirements As shown in Figure 20 , Source 1 sends multicast data to multicast group 224.1.1.1, and Source 2 sends multicast data to multicast group 225.1.1.1. Receiver 1 belongs to multicast group 224.1.1.1, and Receiver 2 belongs to multicast group 225.1.1.1. Router C and Ro uter D run IGMP on their interface GigabitEthernet 1/0/1. Router A, Router B, Router C, and Router D run PIM-SM, and interface GigabitEthernet 1/0/2 on Router A acts as a C-BSR and C-RP. Configure IGMP snooping and PIM snooping on Switch A so that Switch A forwards PIM messages and multicast data to only the routers that are interested in the multicast data. Figure 20 Network diagram
56 Configuration procedure 1. Assign IP addresses: Configure an IP address and subnet ma sk for each interface according to Figure 20. (Details not shown.) 2. Configure Router A: # Enable IP multicast routing, enable PIM-SM on each interface, and configure interface GigabitEthernet 1/0/2 as a C-BSR and C-RP. system-view [RouterA] multicast routing-enable [RouterA] interface gigabitethernet 1/0/1 [RouterA-GigabitEthernet1/0/1] pim sm [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim sm [RouterA-GigabitEthernet1/0/2] quit [RouterA] pim [RouterA-pim] c-bsr gigabitethernet 1/0/2 [RouterA-pim] c-rp gigabitethernet 1/0/2 3. Configure Router B: # Enable IP multicast routing, and enable PIM-SM on each interface. system-view [RouterB] multicast routing-enable [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] pim sm [RouterB-GigabitEthernet1/0/1] quit [RouterB] interface gigabitethernet 1/0/2 [RouterB-GigabitEthernet1/0/2] pim sm 4. Configure Router C: # Enable IP multicast routing, enable PIM-SM on each interface, and enable IGMP on GigabitEthernet 1/0/1. system-view [RouterC] multicast routing-enable [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] pim sm [RouterC-GigabitEthernet1/0/1] igmp enable [RouterC-GigabitEthernet1/0/1] quit [RouterC] interface gigabitethernet 1/0/2 [RouterC-GigabitEthernet1/0/2] pim sm 5. Configure Router D: The configuration on Router D is similar to that on Router C. (Details not shown.) 6. Configure Switch A: # Enable IGMP snooping globally. system-view [SwitchA] igmp-snooping [SwitchA-igmp-snooping] quit
57 # Create VLAN 100, assign GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4 to this VLAN, and enable IGMP snooping and PIM snooping in the VLAN. [SwitchA] vlan 100 [SwitchA-vlan100] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] pim-snooping enable [SwitchA-vlan100] quit 7. Verify the configuration: # On Switch A, display the PIM snooping neighbor information of VLAN 100. [SwitchA] display pim-snooping neighbor vlan 100 Total number of neighbors: 4 VLAN ID: 100 Total number of neighbors: 4 Neighbor Port Expires Option Flags 10.1.1.1 GE1/0/1 02:02:23 LAN Prune Delay \ 10.1.1.2 GE1/0/2 03:00:05 LAN Prune Delay \ 10.1.1.3 GE1/0/3 02:22:13 LAN Prune Delay \ 10.1.1.4 GE1/0/4 03:07:22 LAN Prune Delay \ The output shows that Router A, Router B, Router C, and Router D are PIM snooping neighbors. # On Switch A, display the PIM snooping routing information of VLAN 100. [SwitchA] display pim-snooping routing-table vlan 100 slot 1 Total 2 entry(ies) FSM Flag: NI-no info, J-join, PP-prune pending VLAN ID: 100 Total 2 entry(ies) (*, 224.1.1.1) Upstream neighbor: 10.1.1.1 Upstream port: GE1/0/1 Total number of downstream ports: 1 1: GE1/0/3 Expires: 00:03:01, FSM: J (*, 225.1.1.1) Upstream neighbor: 10.1.1.1 Upstream port: GE1/0/2 Total number of downstream ports: 1 1: GE1/0/4 Expires: 00:01:05, FSM: J The output shows that Switch A will forward th e multicast data intended for multicast group 224.1.1.1 to only Router C, and forward the multicast data intended for multicast group 225.1.1.1 to only Router D.
58 Troubleshooting PIM snooping PIM snooping does not work Symptom PIM snooping does not work on the switch. Analysis IGMP snooping or PIM snooping is not enabled on the switch. Solution 1. Use the display current-configuration command to check the status of IGMP snooping and PIM snooping. 2. If IGMP snooping is not enabled, enter system view and use the igmp-snooping command to enable IGMP snooping globally. Then, enter VLAN view and use the igmp-snooping enable and pim-snooping enable commands to enable IGMP snooping and PIM snooping in the VLAN. 3. If PIM snooping is not enabled, enter VLAN view and use the pim-snooping enable command to enable PIM snooping in the VLAN. Some downstream PIM-capable routers cannot receive multicast data Symptom In a network with fragmented join/prune messages, some downstream PIM-capable routers cannot receive multicast data. Analysis PIM snooping cannot reassemble mess ages, and it cannot maintain the status of downstream routers that the join/prune message fragments carry. To ensure the normal operation of the system, PIM snooping must broadcast join/prune message fragments in the VLAN. However, if the VLAN has a PIM-capable router that has the join suppression function enable d, the broadcast join/prune message fragments might suppress the join messages of other PIM-capable ro uters in the VLAN. As a result, some PIM-capable routers cannot receive the multicas t data destined for a specific multicast group because their join messages are suppressed. To solve this problem, disable the join suppression function on all PIM-capable routers that connect to the PIM snoop ing-capable switch in the VLAN. Solution 1. Use the pim hello-option neighbor-tracking command to enable the neighbor tracking function on the interfaces of PIM routers that co nnect to the PIM snooping-capable switch. 2. If a PIM-capable router cannot be enabled with th e neighbor tracking function, you have to disable PIM snooping on the switch.
59 Configuring multicast VLANs Overview In the traditional multicast programs-on-demand mode shown in Figure 21, w hen hosts (Host A, Host B and Host C) that belong to different VLANs requir e multicast programs-on-demand service, the Layer 3 device, Router A, must forward a separate copy of the multicast traffic in each user VLAN to the Layer 2 device, Switch A. This results in not only waste of network bandwidth but also extra burden on the Layer 3 device. Figure 21 Multicast transmission without multicast VLAN The multicast VLAN feature configured on the Layer 2 device is the solution to this issue. With the multicast VLAN feature, the Layer 3 device replicates the multicast traffic only in the multicast VLAN instead of making a separate copy of the multicast traffic in each user VLAN. This saves network bandwidth and lessens the burden on the Layer 3 device. The multicast VLAN feature can be implemented in sub-VLAN-based multicast VLAN and port-based multicast VLAN. Sub-VLAN-based multicast VLAN As shown in Figure 22, Host A, Host B, and Host C are in different user VL ANs. On Switch A, configure VLAN 10 as a multicast VLAN, configure all the user VLANs as sub-VLANs of VLAN 10, and enable IGMP snooping in the multicast VLAN. Source Receiver Host A Multicast packetsVLAN 2 VLAN 3 VLAN 4 VLAN 2 VLAN 3 VLAN 4 Switch A Receiver Host B Receiver Host CRouter A IGMP querier
60 Figure 22 Sub-VLAN-based multicast VLAN After the configuration, IGMP snooping manages router ports in the multicast VLAN and member ports in the sub-VLANs. When forwarding multicast data to Switch A, Router A sends only one copy of multicast data to Switch A in the multicast VLAN, and Switch A distributes the data to the multicast VLAN’s sub-VLANs that contain receivers. Port-based multicast VLAN As shown in Figure 23, Ho st A, Host B, and Host C are in different user VLANs. All the user ports (ports with attached hosts) on Switch A are hybrid ports. On Switch A, configure VLAN 10 as a multicast VLAN, assign all the user ports to VLAN 10, and enable IG MP snooping in the multicast VLAN and all the user VLANs. Figure 23 Port-based multicast VLAN After the configuration, if Switch A receives an IGMP message on a user port, it tags the message with the multicast VLAN ID and relays it to the IGMP querier, so that IGMP snooping can uniformly manage the router port and member ports in the multicast VLAN. When Router A forwards multicast data to Switch A, it sends only one copy of multicast data to Switch A in the multicast VLAN, and Switch A distributes the data to all the member ports in the multicast VLAN. Source Router A IGMP querier VLAN 2 VLAN 3 VLAN 4 Switch A Receiver Host A Receiver Host B Receiver Host C Multicast packets VLAN 2 VLAN 3 VLAN 4 VLAN 10 (Multicast VLAN) Source VLAN 2 VLAN 3 VLAN 4 GE1/0/1 GE1/0/2 GE1/0/3 GE1/0/4 Switch A Multicast packets Receiver Host A Receiver Host B Receiver Host C Router A IGMP querier VLAN 10 (Multicast VLAN)
61 For more information about IGMP snooping, router ports, and member ports, see Configuring IGMP sn ooping . For more information about VLAN tags, see Layer 2—LAN Switching Configuration Guide . Multicast VLAN configuration task list Task Remarks Configuring a sub-VLAN-based multicast VLAN Required Use either approach. Configuring a port-based multicast VLAN Configuring user port attributes Configuring multicast VLAN ports NOTE: If you have configured both sub-VLAN-based mult icast VLAN and port-based multicast VLAN on a device, the port-based multicast VLAN configuration is given preference. Configuring a sub-VLAN-based multicast VLAN Configuration prerequisites Before you configure sub-VLAN-based multicast VLAN, complete the following tasks: • Create VLANs as required. • Enable IGMP snooping in the VLAN to be configured as a multicast VLAN. Configuration guidelines • You cannot configure multicast VLAN on a device with IP multicast routing enabled. • The VLAN to be configured as a multicast VLAN must exist. • The VLANs to be configured as sub-VLANs of the multicast VLAN must exist and must not be multicast VLANs or sub-VLANs of any other multicast VLAN. • The total number of sub-VLANs of a multicast VLAN must not exceed the maximum number the system can support. Configuration procedure In this approach, you configure a VLAN as a multicast VLAN and configure user VLANs as sub-VLANs of the multicast VLAN. To configure a sub-VLAN-based multicast VLAN: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the specified VLAN as a multicast VLAN and enter multicast VLAN view. multicast-vlan vlan-id By default, a VLAN is not a multicast VLAN.
62 Step Command Remarks 3. Configure the specified VLANs as sub-VLANs of the multicast VLAN. subvlan vlan-list By default, a multicast VLAN has no sub-VLANs. Configuring a port-based multicast VLAN When you configure a port-based multicast VLAN, you must configure the attributes of each user port and then assign the ports to the multicast VLAN. A user port can be configured as a multicast VLAN port only if it is an Ethernet port, or Layer 2 aggregate interface. In Ethernet interface view or Layer 2 aggregate interf ace view, configurations that you make are effective on only the current port. In port group view, configurations that you make are effective on all ports in the current port group. Configuration prerequisites Before you configure a port-based multicast VLAN, complete the following tasks: • Create VLANs as required. • Enable IGMP snooping in the VLAN to be configured as a multicast VLAN. • Enable IGMP snooping in all the user VLANs. Configuring user port attributes Configure the user ports as hybrid ports that permit packets of the specified user VLAN to pass, and configure the user VLAN to which the user ports belong as the default VLAN. Configure the user ports to permit packets of the multicast VLAN to pass and untag the packets. Thus, after receiving multicast packets tagged with the multicast VLAN ID from the upstream device, the Layer 2 device untags the multicast packets and forwards them to its downstream device. To configure user port attributes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view or port group view. • Enter interface view or port group view: interface interface-type interface-number • Enter interface view or port group view: port-group { manual port-group-name | aggregation agg-id } Use either command. 3. Configure the user port link type as hybrid. port link-type hybrid Access by default
63 Step Command Remarks 4. Specify the user VLAN that comprises the current user ports as the default VLAN. port hybrid pvid vlan vlan-id VLAN 1 by default 5. Configure the current user ports to permit packets of the specified multicast VLANs to pass and untag the packets. port hybrid vlan vlan-id-list untagged By default, a hybrid port permits only packets of VLAN 1 to pass. For more information about the port link-type, port hybrid pvid vlan , and port hybrid vlan commands, see Layer 2—LAN Switching Command Reference. Configuring multicast VLAN ports Configuration guidelines In this approach, you configure a VLAN as a multicast VLAN and assign user ports to it. You can do this by either adding the user ports in the multicast VLAN or specifying the multicast VLAN on the user ports. These two methods provide the same result. You cannot configure multicast VLAN on a device with multicast routing enabled. The VLAN to be configured as a multicast VLAN must exist. A port can belong to only one multicast VLAN. Configuration procedure To configure multicast VLAN ports in multicast VLAN view: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the specified VLAN as a multicast VLAN and enter multicast VLAN view. multicast-vlan vlan-id By default, a VLAN is not a multicast VLAN. 3. Assign ports to the multicast VLAN. port interface-list By default, a multicast VLAN has no ports. To configure multicast VLAN ports in interface view or port group view: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure the specified VLAN as a multicast VLAN and enter multicast VLAN view. multicast-vlan vlan-id By default, a VLAN is not a multicast VLAN. 3. Return to system view. quit N/A
64 Step Command Remarks 4. Enter interface view or port group view. • Enter interface view: interface interface-type interface-number • Enter port group view: port-group manual port-group-name Use either command. 5. Configure the current port as a member port of the multicast VLAN. port multicast-vlan vlan-id By default, a user port does not belong to any multicast VLAN. Displaying and maintaining multicast VLAN Task Command Remarks Display information about a multicast VLAN. display multicast-vlan [ vlan-id ] [ | { begin | exclude | include } regular-expression ] Available in any view Multicast VLAN configuration examples Sub-VLAN-based multicast VLAN configuration example Network requirements As shown in Figure 24, IGMPv2 runs on Router A, and IGMPv2 snooping runs on Switch A, Switch B, and Switch C. Router A acts as the IGMP querier. The multicast source sends multicast data to multicast g r o u p 224 .1.1.1. H o s t A , H o s t B , H o s t C , a n d H o s t D a r e r e c e i v e r s o f t h e m u l t i c a s t g r o u p. T h e h o s t s b e l o n g to VLAN 2 through VLAN 5 respectively. Configure the sub-VLAN-based multicast VLAN feature on Switch A so that Router A just sends multicast data to Switch A through the multicast VLAN and Switch A forwards the traffic to the receivers that belong to different user VLANs.