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+.
95 Task Remarks Enabling the IGMP host tracking function Optional Setting the DSCP value for IGMP messages Optional Configuring IGMP SSM mapping Enabling SSM mapping Optional Configuring SSM mappings Optional Configuring IGMP proxying Enabling IGMP proxying Optional Configuring multicast forwarding on a downstream interface Optional For the configuration tasks in this section: In IGMP view, the configuration is effective on all interfaces. In interface view, the configuration is effective on only the current interface. If a feature is not configured on an interface in inte rface view, the global configuration in IGMP view will apply to that interface. If a feature is configured in both IGMP view and interface view, the configuration in interface view will be given priority. Configuring basic IGMP functions Configuration prerequisites Before you configure basic IGMP functions, complete the following tasks: • Configure any unicast routing protocol so that a ll devices in the domain are interoperable at the network layer. • Configure PIM-DM or PIM-SM. • Determine the IGMP version. • Determine the multicast group and multicast source addresses for static group member configuration. • Determine the ACL rule for multicast group filtering. • Determine the maximum number of multicast groups that an interface can join. Enabling IGMP To configure IGMP, you must enable IGMP on the interface for which the multicast group memberships will be established and maintained. Enabling IGMP for the public network Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IP multicast routing. multicast routing-enable Disabled by default 3. Enter interface view. interface interface-type interface-number N/A 4. Enable IGMP. igmp enable Disabled by default
96 Enabling IGMP in a VPN instance Step Command Remarks 1. Enter system view. system-view N/A 2. Create a VPN instance and enter VPN instance view. ip vpn-instance vpn-instance-name N/A 3. Configure an RD for the VPN instance. route-distinguisher route-distinguisher No RD is configured by default. 4. Enable IP multicast routing. multicast routing-enable Disabled by default. 5. Enter interface view. interface interface-type interface-number N/A 6. Bind the interface with a VPN instance. ip binding vpn-instance vpn-instance-name By default, an interface belongs to the public network, and is not bound with any VPN instance. 7. Enable IGMP. igmp enable Disabled by default. For more information about the ip vpn-instance, route-distinguisher , and ip binding vpn-instance commands, see IP Routing Command Reference. For more information about the multicast routing-enable command, see IP Multicast Command Reference . Configuring IGMP versions Because the protocol packets of diff erent IGMP versions vary in structure and type, you must configure the same IGMP version for all routers on the same subnet before IGMP can work properly. Configuring an IGMP version globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A 3. Configure an IGMP version globally. version version-number IGMPv2 by default Configuring an IGMP version on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure an IGMP version on the interface. igmp version version-number IGMPv2 by default
97 Configuring static joining Configuration guidelines After an interface is configured as a static member of a multicast group or a multicast source group, it will act as a virtual member of the multicast group to receive multicast data addressed to that multicast group for the purpose of testing multicast data forwarding. Before you can configure an interface of a PIM-SM switch as a static member of a multicast group or a multicast source and group, if the interface is PIM-SM enabled, it must be a PIM-SM DR. If the interface is enabled with IGMP but not with PIM-SM, it must be an IGMP querier. For more information about PIM-SM and DR, see Configuring PIM (available only on the HP 5500 EI) A stati c member port does not respond to queries from the IGMP querier. When you configure a port as a static member port or remove this configuration on the port, the port does not unsolicitedly send any I G M P r e p o r t o r I G M P l e a v e m e s s a g e . I n o t h e r w o r d s , t h e p o r t i s n o t a r e a l m e m b e r o f t h e m u l t i c a s t g r o u p or the multicast source and group. Configuration procedure To configure an interface as a statically connected member of a multicast group or a multicast source and group: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the interface as a static member of a multicast group or a multicast source and group. igmp static-group group-address [ source source-address ] An interface is not a static member of any multicast group or multicast source and group by default. Configuring a multicast group filter To restrict the hosts on the network attached to an interface from joining certain multicast groups, you can set an ACL rule on the interface as a packet filter so that the interface maintains only the multicast groups the match the criteria. To configure a multicast group filter: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure a multicast group filter. igmp group-policy acl-number [ version-number ] By default, no multicast group filter is configured on an interface, and hosts on an interface can join any valid multicast group.
98 Setting the maximum number of multicast groups that an interface can join Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the maximum number of multicast groups that the interface can join. igmp group-limit limit 2000 by default. NOTE: This configuration takes effect for dynamically joined multicast groups but not for statically configured multicast groups. Adjusting IGMP performance For the configuration tasks described in this section: • The configuration in IGMP view is effective on all interfaces, whereas the configuration in interface view is effective only on the current interface. • If the same feature is configured in both IGMP view and interface view, the configuration in interface view is given priority, regardless of the configuration sequence. Configuration prerequisites Before adjusting IGMP performance, complete the following tasks: • Configure any unicast routing protocol so that a ll devices in the domain are interoperable at the network layer. • Configure basic IGMP functions. • Determine the startup query interval. • Determine the startup query count. • Determine the IGMP general query interval. • Determine the IGMP querier’s robustness variable. • Determine the maximum response time for IGMP general queries. • Determine the IGMP last-member query interval. • Determine the other querier present interval. • Determine the DSCP value for IGMP messages. Configuring IGMP message options IGMP queries include group-specific queries and group-and-source-specific queries, and multicast groups change dynamically, so a device cannot ma intain the information for all multicast sources and groups. For this reason, when an IGMP router receives a multicast packet but cannot locate the outgoing
99 interface for the destination multicast group, it must use the Router-Alert option to pass the multicast packet to the upper-layer protocol for processing. For more information about the Router-Alert option, see RFC 21 13 . An IGMP message is processed differently depending on whether it carries the Router-Alert option in the IP header: • By default, for the consideration of compatibility, the switch does not verify the Router-Alert option but processes all the IGMP messages that it received. In this case, IGMP messages are directly passed to the upper-layer protocol, whether or not the IGMP messages carry the Router-Alert option. • To enhance the switch performance and avoid unnecessary costs, and also for the consideration of protocol security, you can configure the switch to discard IGMP messages that do not carry the Router-Alert option. Configuring IGMP packet options globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A 3. Configure the router to discard any IGMP message that does not carry the Router-Alert option. require-router-alert By default, the switch does not check the Router-Alert option. 4. Enable insertion of the Router-Alert option into IGMP messages. send-router-alert By default, IGMP messages carry the Router-Alert option. Configuring IGMP packet options on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the interface to discard any IGMP message that does not carry the Router-Alert option. igmp require-router-alert By default, the switch does not check the Router-Alert option. 4. Enable insertion of the Router-Alert option into IGMP messages. igmp send-router-alert By default, IGMP messages carry the Router-Alert option. Configuring IGMP query and response parameters IGMP query and response parameters On startup, the IGMP querier sends IGMP general queries at the startup query interval, which is one-quarter of the IGMP general query interval. The numb er of queries, or the startup query count, is user configurable.
100 After startup, the IGMP querier periodically send s IGMP general queries at the IGMP general query interval to check for multicast group members on the network. You can modify the IGMP general query interval based on actual condition of the network. The IGMPv2 querier sends IGMP group-specific queries at the IGMP last-member query interval when it receives an IGMP leave message. The IGMPv3 querier sends IGMP group-and-source-specific queries at the IGMP last-member query interval when it receives a multicast group and multicast mapping change report. The number of queries, or the last-member query count, equals the robustness variable—the maximum number of packet retransmissions. A multicast listening host starts a delay timer for each multicast group it has joined when it receives an IGMP query (general query, group-specific query, or group-and-source-specific query). The timer is i n i t i a l ize d t o a r a n d o m v a l u e i n t h e r a n g e o f 0 t o t h e m a xi m u m re s p o n s e t i m e d e r i ve d i n t h e I G M P q u e r y. When the timer value decreases to 0, the host sends an IGMP report to the corresponding multicast group. Configuration guidelines To speed up the response of hosts to IGMP querie s and avoid simultaneous timer expirations causing IGMP report traffic bursts, you must properly set the maximum response time. • For IGMP general queries, the maximum response time is set by the max-response-time command. • For IGMP group-specific queries and IGMP group-and-source-specific queries, the maximum response time equals the IGMP last-member query interval. When multiple multicast routers exist on the same subnet, the IGMP querier is responsible for sending IGMP queries. If a non-querier router receives no IGMP query from the querier when the other querier present interval expires, it considers that the querier as having failed and starts a new querier election. Otherwise, the non-querier router resets the other querier present timer. In the configuration, make sure that the other querie r present interval is greater than the IGMP general query interval. Otherwise, the IGMP querier might change frequently on the network. Also make sure that the IGMP general query interval is greater than the maximum response time for IGMP general queries. Otherwise, multicast group members might be wrongly removed. The configurations of the maximum response time for IGMP general queries, the IGMP last-member query interval and the IGMP other querier present in terval are effective only for IGMPv2 and IGMPv3. Configuration procedure To configure IGMP query and response parameters globally: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A 3. Configure the IGMP querier’s robustness variable. robust-count robust-value 2 by default. 4. Configure the startup query interval. startup-query-interval interval By default, the startup query interval is 1/4 of the IGMP general query interval. 5. Configure the startup query count. startup-query-count value By default, the startup query count is set to the IGMP querier’s robustness variable.
101 Step Command Remarks 6. Configure the IGMP general query interval. timer query interval 60 seconds by default. 7. Configure the maximum response time for IGMP general queries. max-response-time interval 10 seconds by default. 8. Configure the IGMP last-member query interval. last-member-query-interval interval 1 second by default. 9. Configure the other querier present interval. timer other-querier-present interval By default, the other querier present interval is [ IGMP general query interval ] × [ IGMP robustness variable ] + [ maximum response time for IGMP general queries ] / 2. To configure IGMP query and response parameters on an interface: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure the IGMP querier’s robustness variable. igmp robust-count robust-value 2 by default. 4. Configure the startup query interval. igmp startup-query-interval interval By default, the startup query interval is 1/4 of the IGMP general query interval. 5. Configure the startup query count. igmp startup-query-count value By default, the startup query count is set to the IGMP querier’s robustness variable. 6. Configure the IGMP general query interval. igmp timer query interval 60 seconds by default. 7. Configure the maximum response time for IGMP general queries. igmp max-response-time interval 10 seconds by default. 8. Configure the IGMP last-member query interval. igmp last-member-query-interval interval 1 second by default 9. Configure the other querier present interval. igmp timer other-querier-present interval By default, the other querier present interval is [ IGMP general query interval ] × [ IGMP robustness variable ] + [ maximum response time for IGMP general queries ] / 2. Configuring IGMP fast-leave processing In some applications, such as ADSL dial-up networking , only one multicast receiver host is attached to a port of the IGMP querier. To allow fast response to the leave messages of the host when it switches
102 frequently from one multicast group to another, you c a n e n ab l e I GM P fas t - l e ave p ro c ess i ng o n t h e I GM P querier. With fast-leave processing enabled, after receiving an IGMP leave message from a host, the IGMP querier directly sends a leave notification to the upstream without sending IGMP group-specific queries or IGMP group-and-source-specific queries. Thus, the leave latency is reduced on one hand, and the network bandwidth is saved on the other hand. Configuring IGMP fast-leave processing globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A 3. Configure IGMP fast-leave processing. fast-leave [ group-policy acl-number ] Disabled by default Configuring IGMP fast-leave processing on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Configure IGMP fast-leave processing. igmp fast-leave [ group-policy acl-number ] Disabled by default NOTE: • The IGMP fast-leave processing configuration is effective only if the switch is running IGMPv2 or IGMPv3. • The IGMP fast-leave processing configuration is effective on Layer 3 interfaces other than VLAN interfaces, including Layer 3 Ethernet ports, Layer 3 aggregate interfaces, and Tunnel interfaces. Enabling the IGMP host tracking function With the IGMP host tracking function, the switch can record the information of the member hosts that are receiving multicast traffic, including the host IP address, running duration, and timeout time. You can monitor and manage the member hosts according to the recorded information. Enabling the IGMP host tracking function globally Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view/VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A
103 Step Command Remarks 3. Enable the IGMP host tracking function globally. host-tracking Disabled by default Enabling the IGMP host tracking function on an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable the IGMP host tracking function on the interface. igmp host-tracking Disabled by default Setting the DSCP value for IGMP messages Step Command Remarks 1. Enter system view. system-view N/A 2. Enter public network IGMP view or VPN instance IGMP view. igmp [ vpn-instance vpn-instance-name ] N/A 3. Set the DSCP value for IGMP messages. dscp dscp-value Optional By default, the DSCP value in IGMP messages is 48. Configuring IGMP SSM mapping Because of some possible restrictions, some receiver hosts on an SSM network might run IGMPv1 or IGMPv2. To provide SSM service support for these receiver hosts, configure the IGMP mapping feature on the last-hop router. Before you configure the IGMP SSM mapping feature, complete the following tasks: • Configure any unicast routing protocol so that a ll devices in the domain are interoperable at the network layer. • Configure basic IGMP functions. Enabling SSM mapping Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A 3. Enable the IGMP SSM mapping feature. igmp ssm-mapping enable Disabled by default
104
NOTE:
To ensure SSM service for all hosts on a subnet, re gardless of the IGMP version running on the hosts,
enable IGMPv3 on the interface that forw ards multicast traffic onto the subnet.
Configuring SSM mappings
By performing this configuration multiple times, you can map a multicast group to different multicast
sources.
If IGMPv3 is enabled on a VLAN interface of a switch , and if a port in that VLAN is configured as a
simulated host, the simulated host will send IGMPv3 re ports even if you did not specify a multicast source
when you configure simulated joining with the igmp-snooping host-join command. In this case, the
corresponding multicast group will not be created based on the configured IGMP SSM mappings. For
more information about the igmp-snooping host-join command, see IP Multicast Command Reference.
To configure an IGMP SSM mapping:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter public network
IGMP view or VPN
instance IGMP view. igmp
[ vpn-instance vpn-instance-name ]
N/A
3. Configure an IGMP SSM
mapping. ssm-mapping
group-address { mask |
mask-length } source-address
No IGMP mappings are
configured by default.
Configuring IGMP proxying
Configuration prerequisites
Before you configure the IGMP proxying feature, complete the following tasks:
•
Configure any unicast routing protocol so that a ll devices in the domain are interoperable at the
network layer.
• Enable IP multicast routing.
Enabling IGMP proxying
You can enable IGMP proxying on the interface in the direction toward the root of the multicast
forwarding tree to make the switch serve as an IGMP proxy.
Configuration guidelines
Each switch can have only one interface serving as the proxy interface. In scenarios with multiple
instances, IGMP proxying is configured on only one interface per instance.
You cannot enable IGMP on an interface with IGMP proxying enabled. Moreover, only the igmp
require-router-alert , igmp send-router-alert , and igmp version commands can take effect on such an
interface.
You cannot enable other multicast routing protocols (such as PIM-DM or PIM-SM) on an interface with
IGMP proxying enabled, or vice versa. However, the source-lifetime, source-policy , and ssm-policy