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+.
365 Configuring IPv6 multicast source registration Configuration guidelines Wi t h i n a n I P v 6 P I M - S M d o m a i n, t h e s o u rc e - s i d e D R s ends register messages to the RP, and these register messages have different IPv6 multicast source or IPv6 multicast group addresses. You can configure a filtering rule to filter register messages so that th e RP can serve specific IPv6 multicast groups. If the filtering rule denies an (S, G) entry, or if the filtering rule does not define an action for this entry, the RP will send a register-stop message to the DR to stop the registration process for the IPv6 multicast data. In view of information integrity of register messages in the transmission process, you can configure the device to calculate the checksum based on the en tire register messages. However, to reduce the workload of encapsulating data in register messages and for the sake of interoperability, HP does not recommend this method of checksum calculation. When receivers stop receiving data addressed to a cert ain IPv6 multicast group through the RP (that is, the RP stops serving the receivers of that IPv6 multicast group), or when the RP starts receiving IPv6 multicast data from the IPv6 multicast source along the SPT, the RP sends a register-stop message to the source-side DR. After receiving this message, the DR stops sending register messages encapsulated with IPv6 multicast data and starts a regi ster-stop timer. Before the register-stop timer expires, the DR sends a null register message (a register message without multicast data) to the RP. If the DR receives a register-stop message during the register probe time, it will reset its register-stop timer. Otherwise, the DR starts sending register messages with encapsulated data again when the register-stop timer expires. The register-stop timer is set to a random value chosen uniformly from the interval (0.5 times register_suppression_time, 1.5 times register_suppression_time) minus register_probe_time. Configure a filtering rule for register messages on all C-RP routers, and configure them to calculate the checksum based on the entire register messages. Conf igure the register suppression time and the register probe time on all routers that might become IPv6 source-side DRs. Configuration procedure To configure register-related parameters: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure a filtering rule for register messages. register-policy acl6-number Optional. No register filtering rule by default. 4. Configure the device to calculate the checksum based on the entire register messages. register-whole-checksum Optional. Based on the header of register messages by default. 5. Configure the register suppression time. register-suppression-timeout interval Optional. 60 seconds by default. 6. Configure the register probe time. probe-interval interval Optional. 5 seconds by default.
366 Disabling SPT switchover If an HP 5500 EI switch acts as an RP or the receiver-side DR, it initiates an SPT switchover process by default upon receiving the first IPv6 multicast packet along the RPT. You can disable the switchover from RPT to SPT. IMPORTANT: For an HP 5500 EI switch, once an IPv6 multicast forwardin g entry is created, subsequent IPv6 multicast data will not be encapsulated in register messages be fore being forwarded even if a register outgoing interface is available. Therefore, to avoid forwarding failure, do not use the spt-switch-threshold infinity command on a switch that might become an RP (namely, a static RP or a C-RP). To configure SPT switchover: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Disable the SPT switchover. spt-switch-threshold infinity [ group-policy acl6-number [ order order-value ] ] Optional. By default, the device switches to the SPT immediately after it receives the first IPv6 multicast packet from the RPT. Configuring IPv6 BIDIR-PIM IPv6 BIDIR-PIM configuration task list Task Remarks Enabling IPv6 PIM-SM Required. Enabling IPv6 BIDIR-PIM Required. Configuring an RP Configuring a static RP Required. Use any a pproach. Configuring a C-RP Enabling embedded RP Configuring C-RP timers globally Optional. Configuring a BSR Configuring a C-BSR Required. Configuring an IPv6 BIDIR-PIM domain border Optional. Configuring global C-BSR parameters Optional. Configuring C-BSR timers Optional. Disabling BSM semantic fragmentation Optional. Configuring IPv6 administrative scoping Enabling IPv6 administrative scoping Optional. Configuring an IPv6 admin-scope zone boundary Optional. Configuring C-BSRs for each admin-scope zone Optional.
367 Task Remarks Configuring IPv6 PIM common features Optional. Configuration prerequisites Before you configure IPv6 BIDIR-PIM, complete the following tasks: • Enable IPv6 forwarding and configure an IPv6 unic ast routing protocol so that all devices in the domain can communicate with each other at Layer 3. • Determine the IPv6 address of a static RP and the IP v6 ACL that defines the range of IPv6 multicast groups to be served by the static RP. • Determine the C-RP priority and the IPv6 ACL that defines the range of IPv6 multicast groups to be served by each C-RP. • Determine the legal C-RP address range and the IPv6 ACL that defines the range of IPv6 multicast groups to be served. • Determine the C-RP-Adv interval. • Determine the C-RP timeout. • Determine the C-BSR priority. • Determine the hash mask length. • Determine the IPv6 ACL defining the legal BSR address range. • Determine the BS period. • Determine the BS timeout. Enabling IPv6 PIM-SM You must enable IPv6 PIM-SM before enabling IPv6 BIDIR-PIM because IPv6 BIDIR-PIM is implemented on the basis of IPv6 PIM-SM. To deploy an IPv6 BIDIR- PIM domain, enable IPv6 PIM-SM on all non-border interfaces of the domain. IMPORTANT: On a router, all interfaces in the same VPN inst ance must operate in the same IPv6 PIM mode. To enable IPv6 PIM-SM: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IPv6 multicast routing. multicast ipv6 routing-enable Disabled by default 3. Enter interface view. interface interface-type interface-number N/A 4. Enable IPv6 PIM-SM. pim ipv6 sm Disabled by default For more information about the multicast ipv6 routing-enable command, see IP Multicast Command Reference .
368 Enabling IPv6 BIDIR-PIM Perform this configuration on all routers in the IPv6 BIDIR-PIM domain. To enable IPv6 BIDIR-PIM: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Enable IPv6 BIDIR-PIM. bidir-pim enable Disabled by default Configuring an RP An RP can be manually configured or dynamically elected through the BSR mechanism. For a large IPv6 PIM network, static RP configuration is a tedious job. Generally, static RP configuration is just a backup means for the dynamic RP election mechanism to enhance the robustness and operation manageability of a multicast network. IMPORTANT: In an IPv6 PIM network, if both IPv6 PIM-SM and IPv6 BIDIR-PIM are enabled, do not confi gure the same RP to serve IPv6 PIM-SM and IPv6 BIDIR-PIM simultan eously to avoid IPv6 PIM routing table errors. Configuring a static RP If only one dynamic RP exists in a network, manually configuring a static RP can avoid communication interruption because of single-point failures and avoid frequent message exchange between C-RPs and the BSR. In IPv6 BIDIR-PIM, a static RP can be specified with a virtual IPv6 address. For example, if the IPv6 addresses of the interfaces at the two ends of a link are 1001::1/64 and 1001::2/64, you can specify a virtual IPv6 address, like 1001::100/64, for the static RP. As a result, the link becomes an RPL. IMPORTANT: You must perform static RP configuration on all rout ers in the IPv6 PIM-SM domain and specify the same RP address. Perform this configuration on all routers in the IPv6 BIDIR-PIM domain. To configure a static RP: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure a static RP for IPv6 BIDIR-PIM. static-rp ipv6-rp-address [ acl6-number ] [ preferred ] bidir No static RP by default Configuring a C-RP In an IPv6 BIDIR-PIM domain, you can configure routers that intend to become the RP as C-RPs. The BSR collects the C-RP information by receiving the C-RP-Adv messages from C-RPs or auto-RP announcements
369
from other routers and organizes the information into an RP-set, which is flooded throughout the entire
network. Then, the other routers in the network calculate the mappings between specific group ranges
and the corresponding RPs based on the RP-set. HP recommends that you configure C-RPs on backbone
routers.
To guard against C-RP spoofing, configure a legal C-RP address range and the range of multicast groups
to be served on the BSR. In addition, because every C-BSR has a chance to become the BSR, you must
configure the same filtering policy on all C-BSRs in the IPv6 BIDIR-PIM domain.
To configure a C-RP:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter IPv6 PIM view.
pim ipv6 N/A
3. Configure an interface to be a
C-RP for IPv6 BIDIR-PIM. c-rp
ipv6-address [ { group-policy
acl6-number | scope scope-id } |
priority priority | holdtime
hold-interval |
advertisement-interval
adv-interval ] * bidir No C-RP is configured by default.
NOTE:
• When you configure a C-RP, ensure a relatively large bandwidth between this C-RP and the other
devices in the IPv6 BIDIR-PIM domain.
• An RP can serve multiple IPv6 multicast groups or all IPv6 multicast
groups. Only one RP can forward
multicast traffic for an IPv6 multicast group at a moment.
Enabling embedded RP
With the embedded RP feature enabled, the router can resolve the RP address directly from the IPv6
multicast group address of an IPv6 multicast packets. This RP can replace the statically configured RP or
the RP dynamically calculated based on the BSR mechanism. Thus, the DR does not need to know the RP
address beforehand.
Perform this configuration on all routers in the IPv6 BIDIR-PIM domain.
To enable embedded RP:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter IPv6 PIM view.
pim ipv6 N/A
3. Enable embedded RP.
embedded-rp [ acl6-number ] Optional.
By default, embedded RP is
enabled for IPv6 multicast groups
in the default embedded RP
address scopes.
NOTE:
The default embedded RP address scopes are FF7x ::/12 and FFFx::/12, where x refers to any legal
address scope. For more information about the Scope field, see Multicast overview.
370 Configuring C-RP timers globally To enable the BSR to distribute the RP-Set information within the IPv6 BIDIR-PIM domain, C-RPs must periodically send C-RP-Adv messages to the BSR. The BSR learns the RP-Set information from the received messages, and encapsulates its own IPv6 address togeth er with the RP-Set information in its bootstrap messages. The BSR then floods the bootstrap mess ages to all IPv6 routers in the network. Each C-RP encapsulates a timeout value in its C-RP -Adv messages. After receiving a C-RP-Adv message, the BSR obtains this timeout value and starts a C-RP ti meout timer. If the BSR fails to hear a subsequent C-RP-Adv message from the C-RP when the timer times out, the BSR assumes the C-RP to have expired or become unreachable. The C-RP timers need to be configured on C-RP routers. To configure C-RP timers globally: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure the C-RP-Adv interval. c-rp advertisement-interval interval Optional. 60 seconds by default. 4. Configure C-RP timeout time. c-rp holdtime interval Optional. 150 seconds by default. For more information about the configuratio n of other timers in IPv6 PIM-SM, see Configuring IPv6 PIM common timer s . Configuring a BSR Configuration guidelines Before you configure a BSR, make sure that you are familiar with BSR election process, BSR legal address against BSR spoofing, IPv6 PIM domain border, glo bal C-BSR parameters, C-BSR timers, and bootstrap message fragments (BSMFs). They operate the same wa y as in the PIM-SM domain. For more information, see Configuration guidelines . Configuring a C-BSR Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure an interface as a C-BSR. c-bsr ipv6-address [ hash-length [ priority ] ] No C-BSRs are configured by default. 4. Configure a legal BSR address range. bsr-policy acl6-number Optional. No restrictions on BSR address range by default.
371 Configuring an IPv6 BIDIR-PIM domain border Perform the following configuration on routers that you want to configure as the IPv6 BIDIR-PIM domain border. To configure an IPv6 BIDIR-PIM domain border: 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 IPv6 BIDIR-PIM domain border. pim ipv6 bsr-boundary By default, no IPv6 BIDIR-PIM domain border is configured. Configuring global C-BSR parameters Perform the following configuration on C-BSR routers. To configure global C-BSR parameters: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure the hash mask length. c-bsr hash-length hash-length Optional. 126 by default. 4. Configure the C-BSR priority. c-bsr priority priority Optional. 64 by default. Configuring C-BSR timers Perform the following configuration on C-BSR routers. To c o n fig u re C - BS R t i me rs : Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure the BS period. c-bsr interval interval Optional. For the default value, see the note after this table. 4. Configure the BS timeout timer. c-bsr holdtime interval Optional. For the default value, see the note after this table. Disabling BSM semantic fragmentation Step Command Remarks 1. Enter system view. system-view N/A
372
Step Command Remarks
2. Enter IPv6 PIM view.
pim ipv6 N/A
3. Disable the BSM semantic
fragmentation function. undo bsm-fragment
enable By default, the BSM semantic
fragmentation function is enabled.
Configuring IPv6 administrative scoping
With administrative scoping disabled, an IPv6 BIDIR-PIM domain has only one BSR. The BSR manages
the whole network. To manage your network more effectively and specifically, you can partition the IPv6
BIDIR-PIM domain into multiple admin-scope zones.
Each admin-scope zone maintains a BSR, which
serves a specific multicast group range. The global sc ope zone also maintains a BSR, which serves all the
rest multicast groups.
Enabling IPv6 administrative scoping
Before you configure an IPv6 admin-scope zone, you must enable IPv6 administrative scoping first.
Perform the following configuration on all routers in the IPv6 PIM-SM domain.
To enable IPv6 administrative scoping:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter IPv6 PIM view.
pim ipv6 N/A
3. Enable IPv6 administrative
scoping. c-bsr admin-scope
Disabled by default
Configuring an IPv6 admin-scope zone boundary
The boundary of each IPv6 admin-scope zone is fo rmed by ZBRs. Each admin-scope zone maintains a
BS R, wh ich s er ves a s p e ci fic I P v 6 mu l t ic as t g rou p ra n g e. I P v 6 mu l t ic as t p a cke ts ( s uch as ass er t m e ssa g e s
and bootstrap messages) that belong to this ra nge cannot cross the admin-scope zone boundary.
Perform the following configuration on routers that you want to configure as a ZBR.
To configure an admin-scope zone boundary:
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 IPv6 multicast
forwarding boundary. multicast ipv6 boundary
{
ipv6-group-address prefix-length
| scope { scope-id | admin-local |
global | organization-local |
site-local } } By default, no IPv6 multicast
forwarding boundary is
configured.
For more information about the multicast ipv6 boundary command, see IP Multicast Command
Reference .
373
Configuring C-BSRs for each admin-scope zone
In a network with administrative scoping enabled, group-range-specific BSRs are elected from C-BSRs.
C-RPs in the network send advertisement messages to the specific BSR. The BSR summarizes the
advertisement messages to form an RP-set and advertises it to all routers in the specific admin-scope zone.
All the routers use the same hash al gorithm to get the RP address corresponding to the specific multicast
group.
You can configure the hash mask length and C-BSR priority globally, only in an IPv6 admin-scope zone,
or both globally and in an IPv6 admin-scope zone.
• The values configured in the IPv6 admin-scope zo ne have preference over the global values.
• If you do not configure these parameters in the IPv6 admin-scope zone, the corresponding global
values will be used.
For configuration of global C-BSR parameters, see Configuring global C-BSR parameters.
Perform the following configuration on the routers that you want to configure as C-BSRs in admin-scope
zones.
To configure a C-BSR for an admin-scope zone:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter IPv6 PIM view.
pim ipv6 N/A
3. Configure a C-BSR for
an admin-scope zone. c-bsr
scope { scope-id | admin-local |
global | organization-local | site-local }
[ hash-length hash-length | priority
priority ] * No C-BSRs are configured for an
admin-scope zone by default.
Configuring IPv6 PIM-SSM
IMPORTANT:
The IPv6 PIM-SSM model needs the support of MLDv2.
Be sure to enable MLDv2 on IPv6 PIM routers with
receivers attached to them.
IPv6 PIM-SSM configuration task list
Task Remarks
Enabling IPv6 PIM-SM Required
Configuring the IPv6 SSM group range Optional
Configuring IPv6 PIM common features Optional
Configuration prerequisites
Before you configure IPv6 PIM-SSM, complete the following tasks:
• Enable IPv6 forwarding and configure an IPv6 unic ast routing protocol so that all devices in the
domain are interoperable at the network layer.
374 • Determine the IPv6 SSM group range. Enabling IPv6 PIM-SM Configuration guidelines The SSM model is implemented based on some subsets of IPv6 PIM-SM. Therefore, you must enable IPv6 PIM-SM before configuring IPv6 PIM-SSM. When you deploy an IPv6 PIM-SSM domain, enable IPv6 PIM-SM on all non-border interfaces of routers. All the interfaces of the same device must operate in the same IPv6 PIM mode. Configuration procedure To enable IPv6 PIM-SSM: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable IPv6 multicast routing. multicast ipv6 routing-enable Disabled by default 3. Enter interface view. interface interface-type interface-number N/A 4. Enable IPv6 PIM-SM. pim ipv6 sm Disabled by default For more information about the multicast ipv6 routing-enable command, see IP Multicast Command Reference . Configuring the IPv6 SSM group range Configuration guidelines Whether the information from an IPv6 multicast source is delivered to the receivers based on the IPv6 PIM-SSM model or the IPv6 PIM-SM model depends on whether the group address in the (S, G) channel subscribed by the receivers falls into the IPv6 SSM group range. All IPv6 PIM-SM-enabled interfaces assume that IPv6 multicast groups within this address range are using the IPv6 SSM model. Make sure that the same IPv6 SSM group range is configured on all routers in the entire domain. Otherwise, IPv6 multicast data cannot be delivered through the IPv6 SSM model. When a member of an IPv6 multicast group in the IPv6 SSM group range sends an MLDv1 report message, the device does not trigger a (*, G) join. Configuration procedure Perform the following configuration on all routers in the IPv6 PIM-SSM domain. To configure the IPv6 SSM group range: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A