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+.
375 Step Command Remarks 3. Configure the IPv6 SSM group range. ssm-policy acl6-number Optional. FF3x::/32 by default, here x refers to any legal group scope. Configuring IPv6 PIM common features For the configuration tasks in this section: • In IPv6 PIM view, the configuration is effective on all interfaces. In interface view, the configuration is effective on only the current interface. • If the same function or parameter is configured in both IPv6 PIM view and interface view, the configuration in interface view has preference over the configuration in PIM view, regardless of the configuration sequence. IPv6 PIM common feature configuration task list Task Remarks Configuring an IPv6 multicast data filter Optional Configuring a hello message filter Optional Configuring IPv6 PIM hello options Optional Configuring the prune delay Optional Configuring IPv6 PIM common timers Optional Configuring join/prune message sizes Optional Configuring IPv6 PIM to work with BFD Optional Setting the DSCP value for IPv6 PIM messages Optional Configuration prerequisites Before you configure IPv6 PIM common features, 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. • Configure IPv6 PIM-DM (or IPv6 PIM-SM or IPv6 PIM-SSM). • Determine the IPv6 ACL rule for filtering IPv6 multicast data. • Determine the IPv6 ACL rule defining a legal source address range for hello messages. • Determine the priority for DR election (global value/interface level value). • Determine the IPv6 PIM neighbor timeout time (global value/interface value). • Determine the prune message delay (global value/interface level value). • Determine the prune override interval (global value/interface level value). • Determine the prune delay. • Determine the hello interval (global value/interface level value). • Determine the maximum delay between hello message (interface level value).
376 • Determine the assert timeout time (global value/interface value). • Determine the join/prune interval (global value/interface level value). • Determine the join/prune timeout (global value/interface value). • Determine the IPv6 multicast source lifetime. • Determine the maximum size of join/prune messages. • Determine the maximum number of (S, G) entries in a join/prune message. • Determine the DSCP value for IPv6 PIM messages. Configuring an IPv6 multicast data filter Configuration guidelines I n e i t h e r a n I P v 6 P I M - D M d o m a i n o r a n I P v 6 P I M - S M d o m a i n , r o u t e r s c a n c h e c k p a s s i n g - b y I P v 6 m u l t i c a s t data based on the configured filtering rules and de termine whether to continue forwarding the IPv6 multicast data. In other words, IPv6 PIM routers can act as IPv6 multicast data filters. These filters can help implement traffic control on one hand, and control the information available to downstream receivers to enhance data security on the other hand. Generally, a smaller distance from the filter to the IPv6 multicast source results in a more remarkable filtering effect. T h i s f i l t e r w o r k s n o t o n l y o n i n d e p e n d e n t I P v 6 m u l t i c ast data but also on IPv6 multicast data encapsulated in register messages. Configuration procedure To configure an IPv6 multicast data filter: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure an IPv6 multicast group filter. source-policy acl6-number No IPv6 multicast data filter by default Configuring a hello message filter Along with the wide applications of IPv6 PIM, the security requirement for the protocol is becoming increasingly demanding. The establishment of correct IPv6 PIM neighboring relationships is a prerequisite for secure application of IPv6 PIM. To guide against IPv6 PIM message attacks, you can configure a legal source address range for hello messages on interfaces of routers to ensure the correct IPv6 PIM neighboring relationships. To configure a hello message filter: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A
377 Step Command Remarks 3. Configure a hello message filter. pim ipv6 neighbor-policy acl6-number No hello message filter by default NOTE: With the hello message filter configured, if hello messages of an existing IPv6 PIM neighbor fail to pass the filter, the IPv6 PIM neighbor will be removed automatically when it times out. Configuring IPv6 PIM hello options IPv6 PIM hello options In either an IPv6 PIM-DM domain or an IPv6 PIM-SM domain, the hello messages sent among routers contain the following configurable options: • DR_Priority (for IPv6 PIM-SM only)—Priority for DR election. The higher the priority is, the easier it is for the router to win DR election. You can configure this parameter on all the routers in a multi-access network directly connected to IPv6 multicast sources or receivers. • Holdtime —The timeout time of IPv6 PIM neighbor reachability state. When this timer times out, if the router has received no hello message from an IPv6 PIM neighbor, it assumes that this neighbor has expired or become unreachable. • LAN_Prune_Delay —The delay of prune messages on a multi-a ccess network. This option consists of LAN-delay (namely, prune message delay), override-interval, and neighbor tracking flag. If the LAN-delay or override-interval values of differen t IPv6 PIM routers on a multi-access subnet are different, the largest value takes effect. If you want to enable neighbor tracking, be sure to enable the neighbor tracking feature on all IPv6 PIM routers on a multi-access subnet. The LAN-delay setting will cause the upstream routers to delay forwarding received prune messages. The override-interval sets the length of time that a downstream router can wait before sending a prune override message. When a router receives a prun e message from a downstream router, it does not perform the prune action immediately. Instead, it ma intains the current forwarding state for a period of LAN-delay plus override-interval. If the downstream router needs to continue receiving IPv6 multicast data, it must send a join message within the prune ov erride interval. Otherwise, the upstream route will perform the prune action when the period of LAN-delay plus override-interval times out. A hello message sent from an IPv6 PIM router contains a generation ID option. The generation ID is a random value for the interface on which the hello message is sent. Normally, the generation ID of an IPv6 PIM router does not change unless the status of the router changes (for example, when IPv6 PIM is just enabled on the interface or the device is restarted) . When the router starts or restarts sending hello messages, it generates a new generation ID. If an IPv6 PIM router finds that the generation ID in a hello m e s s a g e f r o m t h e u p s t r e a m r o u t e r h a s c h a n g e d , i t a s s u m e s that the status of the upstream neighbor is lost or that the upstream neighbor has changed. In this case, it triggers a join message for state update. If you disable join suppression (namely, enable ne ighbor tracking), be sure to disable the join suppression feature on all IPv6 PIM routers on a multi-access subnet. Otherwise, the upstream router will fail to explicitly track join messages from downstream routers. Configuring hello options globally Step Command Remarks 1. Enter system view. system-view N/A
378 Step Command Remarks 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure the priority for DR election. hello-option dr-priority priority Optional. 1 by default. 4. Configure IPv6 PIM neighbor timeout time. hello-option holdtime interval Optional. 105 seconds by default. 5. Configure the prune message delay time (LAN-delay). hello-option lan-delay interval Optional. 500 milliseconds by default. 6. Configure the prune override interval. hello-option override-interval interval Optional. 2,500 milliseconds by default. 7. Disable join suppression. hello-option neighbor-tracking Enabled by default. Configuring hello 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 priority for DR election. pim ipv6 hello-option dr-priority priority Optional. 1 by default. 4. Configure IPv6 PIM neighbor timeout time. pim ipv6 hello-option holdtime interval Optional. 105 seconds by default. 5. Configure the prune message delay time (LAN-delay). pim ipv6 hello-option lan-delay interval Optional. 500 milliseconds by default. 6. Configure the prune override interval. pim ipv6 hello-option override-interval interval Optional. 2500 milliseconds by default. 7. Disable join suppression. pim ipv6 hello-option neighbor-tracking Enabled by default. 8. Configure the interface to reject hello messages without a generation ID. pim ipv6 require-genid By default, hello messages without Generation_ID are accepted. Configuring the prune delay Configuring the prune delay interval on an upstream router in a shared network segment can make the upstream router not perform the prune action imme diately after receiving the prune message from its downstream router. Instead, the upst ream router maintains the current forwarding state for a period of time that the prune delay interval defines. In this pe riod, if the upstream router receives a join message from the downstream router, it cancels the prune action. Otherwise, it performs the prune action. To configure the prune delay time
379 Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure the prune delay interval. prune delay interval Optional. 3 seconds by default, which equals the prune pending time. Configuring IPv6 PIM common timers IPv6 PIM common timers IPv6 PIM routers discover IPv6 PIM neighbors and maintain IPv6 PIM neighboring relationships with other routers by periodically sending hello messages. After receiving a hello message, an IPv6 PIM router waits a random period, which is smaller than the maximum delay between hello messages, before sendin g a hello message. This avoids collisions that occur when multiple IPv6 PIM routers send hello messages simultaneously. An IPv6 PIM router periodically sends join/prune mess ages to its upstream for state update. A join/prune message contains the join/prune timeout time. The up stream router sets a join/prune timeout timer for each pruned downstream interface. Any router that has lost assert election will prune its downstream interface and maintain the assert state for a period of time. When the assert state times out, the assert loser will resume IPv6 multicast forwarding. When a router fai l s to rec eive subsequent I P v6 mu l tic ast data from the I P v6 mu l tic ast sou rc e S, the router does not immediately delete the corresponding (S, G) entry. Instead, it maintains the (S, G) entry for a period of time—namely, the IPv6 multicast source lifetime—before deleting the (S, G) entry. Configuring IPv6 PIM common 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 hello interval. timer hello interval Optional. 30 seconds by default. 4. Configure the join/prune interval. timer join-prune interval Optional. 60 seconds by default. 5. Configure the join/prune timeout time. holdtime join-prune interval Optional. 210 seconds by default. 6. Configure assert timeout time. holdtime assert interval Optional. 180 seconds by default. 7. Configure the IPv6 multicast source lifetime. source-lifetime interval Optional. 210 seconds by default.
380 Configuring IPv6 PIM common timers 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 hello interval. pim ipv6 timer hello interval Optional. 30 seconds by default. 4. Configure the maximum delay between hello messages. pim ipv6 triggered-hello-delay interval Optional. 5 seconds by default. 5. Configure the join/prune interval. pim ipv6 timer join-prune interval Optional. 60 seconds by default. 6. Configure the join/prune timeout time. pim ipv6 holdtime join-prune interval Optional. 210 seconds by default. 7. Configure assert timeout time. pim ipv6 holdtime assert interval Optional 180 seconds by default. NOTE: If no special networking requirements are raised, use the default settings. Configuring join/prune message sizes A l arg e s ize of a joi n/pru ne message might res u l t i n loss of a larger amount of information if a message is lost. You can set a small value for the size of each join/prune message to reduce the impact in case of the loss of a message. By controlling the maximum number of (S, G) entries in a join/prune message, you can effectively reduce the number of (S, G) entries sent per unit of time. IMPORTANT: If IPv6 PIM snooping–enabled switches are deployed in the IPv6 PIM network, be sure to set a value no greater than the IPv6 path MTU for the maximum size of each join/prune message on the receiver-side edge IPv6 PIM devices. To configure join/prune message sizes: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter IPv6 PIM view. pim ipv6 N/A 3. Configure the maximum size of each join/prune message. jp-pkt-size packet-size Optional. 8100 bytes by default. 4. Configure the maximum number of (S, G) entries in a join/prune message. jp-queue-size queue-size Optional. 1020 by default.
381
Configuring IPv6 PIM to work with BFD
IPv6 PIM uses hello messages to elect a DR for a multi-access network. The elected DR will be the only
multicast forwarder on the multi-access network.
If the DR fails, a new DR election process will start after t h e D R i s a g e d o u t. H oweve r, i t m i g h t t a ke a l o n g
period of time. To start a new DR election process i mmediately after the original DR fails, you can enable
IPv6 PIM to work with Bidirectional Forwarding Detection (BFD) on a multi-access network to detect
failures of the links among IPv6 PIM neighbors. You must enable IPv6 PIM to work with BFD on all IPv6
PIM-capable routers on a multi-access network, so that the IPv6 PIM neighbors can fast detect DR failures
and start a new DR election process.
Before you configure this feature on an interface, be sure to enable IPv6 PIM-DM or IPv6 PIM-SM on the
interface.
To enable IPv6 PIM to work with BFD:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter interface view.
interface interface-type interface-number N/A
3. Enable IPv6 PIM to
work with BFD. pim ipv6 bfd enable
Disabled by default
For more information about BFD, see High Availability Configuration Guide .
Setting the DSCP value for IPv6 PIM messages
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter IPv6 PIM view.
pim ipv6 N/A
3. Set the DSCP value for IPv6
PIM messages. dscp
dscp-value Optional.
By default, the DSCP value in IPv6
PIM messages is 48.
Displaying and maintaining IPv6 PIM
Task Command Remarks
Display the BSR information in the
IPv6 PIM-SM domain and locally
configured C-RP information in
effect.
display pim ipv6 bsr-info
[ |
{ begin | exclude | include }
regular-expression ]
Available in any view
Display information about IPv6
unicast routes used by IPv6 PIM.
display pim ipv6 claimed-route
[ ipv6-source-address ] [ | { begin |
exclude | include }
regular-expression ]
Available in any view
382
Task Command Remarks
Display the number of IPv6 PIM
control messages.
display pim ipv6 control-message
counters
[ message-type { probe |
register | register-stop } |
[ interface interface-type
interface-number | message-type
{ assert | bsr | crp | graft |
graft-ack | hello | join-prune |
state-refresh } ] * ] [ | { begin |
exclude | include }
regular-expression ]
Available in any view
Display the DF information of IPv6
BIDIR-PIM. display pim ipv6 df-info
[ rp-address ] [ | { begin | exclude
| include } regular-expression ] Available in any view
Display information about
unacknowledged graft messages.
display pim ipv6 grafts
[ | { begin
| exclude | include }
regular-expression ]
Available in any view
Display the IPv6 PIM information
on an interface or all interfaces.
display pim ipv6 interface
[ interface-type interface-number ]
[ verbose ] [ | { begin | exclude |
include } regular-expression ]
Available in any view
Display information about
join/prune messages to send.
display pim ipv6 join-prune mode
{
sm [ flags flag-value ] | ssm }
[ interface interface-type
interface-number | neighbor
ipv6-neighbor-address ] *
[ verbose ] [ | { begin | exclude |
include } regular-expression ]
Available in any view
Display IPv6 PIM neighboring
information.
display pim ipv6 neighbor
[ interface interface-type
interface-number |
ipv6-neighbor-address | verbose ]
* [ | { begin | exclude | include }
regular-expression ]
Available in any view
Display information about the IPv6
PIM routing table.
display pim ipv6 routing-table
[ ipv6-group-address
[ prefix-length ] |
ipv6-source-address
[ prefix-length ] |
incoming-interface [ interface-type
interface-number | register ] |
outgoing-interface { include |
exclude | match } { interface-type
interface-number | register } |
mode mode-type | flags flag-value
| fsm ] * [ | { begin | exclude |
include } regular-expression ]
Available in any view
Display the RP information.
display pim ipv6 rp-info
[ ipv6-group-address ] [ | { begin |
exclude | include }
regular-expression ]
Available in any view
383 Task Command Remarks Reset IPv6 PIM control message counters. reset pim ipv6 control-message counters [ interface interface-type interface-number ] Available in user view IPv6 PIM configuration examples IPv6 PIM-DM configuration example Network requirements Receivers receive VOD information through multicast. The receiver groups of different organizations form stub networks, and one or more receiver hosts exist in each stub network. The entire IPv6 PIM domain is operating in the dense mode. Host A and Host C are multicast receivers in two stub networks N1 and N2. MLDv1 runs between Switch A and N1 and between Switch B/Switch C and N2. Figure 103 Network diagram Device Interface IPv6 address Device Interface IPv6 address Switch A Vlan-int100 1001::1/64 Switch D Vlan-int300 4001::1/64 Vlan-int103 1002::1/64 Vlan-int103 1002::2/64 Switch B Vlan-int200 2001::1/64 Vlan-int101 2002::2/64 Vlan-int101 2002::1/64 Vlan-int102 3001::2/64 Switch C Vlan-int200 2001::2/64 Vlan-int102 3001::1/64
384
Configuration procedure
1. Enable IPv6 forwarding and configure IPv6 addresses and IPv6 unicast routing:
Enable IPv6 forwarding on each switch and config ure the IPv6 address and prefix length for each
interface as per Figure 103. (Details not shown.)
Conf
igure OSPFv3 on the switches in the IP v6 PIM-DM domain to ensure network-layer
reachability among them. (Details not shown.)
2. Enable IPv6 multicast routing, and enable IPv6 PIM-DM and MLD:
# Enable IPv6 multicast routing on Switch A, enable IPv6 PIM-DM on each interface, and enable
MLD on VLAN-interface 100, wh ich connects Switch A to N1.
system-view
[SwitchA] multicast ipv6 routing-enable
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] mld enable
[SwitchA-Vlan-interface100] pim ipv6 dm
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 103
[SwitchA-Vlan-interface103] pim ipv6 dm
[SwitchA-Vlan-interface103] quit
The configuration on Switch B and Switch C is similar to that on Switch A.
# Enable IPv6 multicast routing on Switch D, and enable IPv6 PIM-DM on each interface.
system-view
[SwitchD] multicast ipv6 routing-enable
[SwitchD] interface vlan-interface 300
[SwitchD-Vlan-interface300] pim ipv6 dm
[SwitchD-Vlan-interface300] quit
[SwitchD] interface vlan-interface 103
[SwitchD-Vlan-interface103] pim ipv6 dm
[SwitchD-Vlan-interface103] quit
[SwitchD] interface vlan-interface 101
[SwitchD-Vlan-interface101] pim ipv6 dm
[SwitchD-Vlan-interface101] quit
[SwitchD] interface vlan-interface 102
[SwitchD-Vlan-interface102] pim ipv6 dm
[SwitchD-Vlan-interface102] quit
3. Verify the configuration:
Use the display pim ipv6 interface command to view the IPv6 PIM configuration and running status
on each interface. For example:
# Display IPv6 PIM information on Switch D.
[SwitchD] display pim ipv6 interface
Interface NbrCnt HelloInt DR-Pri DR-Address
Vlan300 0 30 1 4001::1
(local)
Vlan103 0 30 1 1002::2
(local)
Vlan101 1 30 1 2002::2
(local)