Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    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+.

    View all the pages
    Page
    of 2513
    Add page 1281 to Favourites
    image text
    Enable zoom 
    							 145 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure a C-BSR for an 
admin-scope zone.  c-bsr group 
group-address  { mask | 
mask-length  } [  hash-length 
hash-length  | priority  priority  ] *  No C-BSRs are configured for an 
admin-scope zone by default. 
 
 
NOTE: 
The 
group-address { mask | mask-length } parameter of the  c-bsr group command can specify the 
multicast groups the C-BSR serves, in the range of 239.0.0.0/8. 
 
•   Configure C-BSRs for the global-scope zone 
Perform the following configuration on the routers  that you want to configure as C-BSRs in the 
global-scope zone.  
To configure a C-BSR for  the global-scope zone: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.
  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure a C-BSR for the 
global-scope zone.  c-bsr global 
[ hash-length 
hash-length  | priority  priority  ] * No C-BSRs are configured for the 
global-scope zone by default.
 
 
Configuring multicast source registration 
Within a PIM-SM domain, the source-side DR sends  register messages to the RP, and these register 
messages have different multicast source or group addr esses. You can configure a filtering rule to filter 
register messages so that the RP can serve specific multicast groups. If the filtering rule denies an (S, G) 
entry, or if the filtering rule does not define the action for this entry, the RP will send a register-stop 
message to the DR to stop the registration process for the multicast data.  
Configuration guidelines 
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 an d for the sake of interoperability, do not use this 
method of checksum calculation. 
When receivers stop receiving multicast data addressed to a certain multicast group through the RP (that 
is, the RP stops serving the receivers of that multicast group), or when the RP starts receiving multicast 
data from the 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 multicast data 
and starts a register-stop timer. Befo re the register-stop timer expires, the DR sends a null register message 
(a register message without encapsulated 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.
    Add page 1282 to Favourites
    image text
    Enable zoom 
    							 146 
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 source-side DRs.  
Configuration procedure 
To configure register-related parameters:   
Step  Command  Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure a filtering rule for 
register messages.  register-policy 
acl-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. 
By default, the checksum is 
calculated based on the header of 
register messages. 
 
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. 
 
 
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 multicast packet along the RPT. You can disable the switchover from RPT 
to SPT.  
 
 IMPORTANT: 
For an HP 5500 EI switch, once a multicast forwardin
g entry is created, subsequent multicast data will not
be encapsulated in register messages before being forwarded even if 
a register outgoing interface is 
available. To avoid forwarding failure, do not use the  spt-switch-threshold infinity command on a switch
that might become an RP (a static RP or a C-RP). 
 
To configure SPT switchover:   
Step  Command  Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A
    Add page 1283 to Favourites
    image text
    Enable zoom 
    							 147 
Step Command  Remarks 
3.  Disable  SPT switchover.  spt-switch-threshold infinity
 
[  group-policy  acl-number 
[ order  order-value ] ]
  Optional. 
By default, the device switches to the 
SPT immediately after it receives the 
first multicast packet. 
 
Configuring BIDIR-PIM 
BIDIR-PIM configuration task list  
Task Remarks 
Enabling PIM-SM 
Required. 
Enabling BIDIR-PIM Required. 
Configuring an RP Configuring a static RP 
Required. 
Use any a

pproach. 
Configuring a C-RP 
Enabling auto-RP 
Configuring C-RP timers globally Optional. 
Configuring a BSR Configuring a C-BSR 
Required. 
Configuring a BIDIR-PIM domain border Optional. 
Configuring global C-BSR parameters Optional. 
Configuring C-BSR timers Optional. 
Disabling BSM semantic fragmentation Optional. 
Configuring an admin-scope zone 
boundary Enabling administrative scoping 
Optional.
  
Configuring administrative scoping Optional. 
Configuring C-BSRs for each admin-scope 
zone and the global-scope zone Optional. 
Configuring PIM common features 
Optional. 
 
Configuration prerequisites 
Before you configure BIDIR-PIM, complete the following tasks:  
•  Configure a unicast routing protocol so that a ll devices in the domain can reach each other. 
•   Determine the IP address of a static RP and the AC L that defines the range of the multicast groups 
to be served by the static RP. 
•   Determine the C-RP priority and the ACL that defines the range of multicast groups to be served by 
each C-RP. 
•   Determine the legal C-RP address range and the ACL  that defines the range of multicast groups to 
be served. 
•   Determine the C-RP-Adv interval.  
•   Determine the C-RP timeout.
    Add page 1284 to Favourites
    image text
    Enable zoom 
    							 148 
•  Determine the C-BSR priority. 
•   Determine the hash mask length. 
•   Determine the ACL defining the legal BSR address range. 
•   Determine the BS period. 
•   Determine the BS timeout.  
Enabling PIM-SM 
Because BIDIR-PIM is implemented on the basis of PIM-SM, you must enable PIM-SM before enabling 
BIDIR-PIM. To deploy a BIDIR-PIM domain, enable PIM- SM on all non-border interfaces of the domain.  
 
 IMPORTANT: 
On a router, all interfaces in the same VPN instance must operate in the same PIM mode. 
 
Enabling PIM-SM globally 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 PIM-SM. 
pim sm  Disabled by default 
 
Enabling PIM-SM for 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
  Not 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 the 
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 PIM-SM. 
pim sm  Disabled by default. 
 
For more information about the ip vpn-instance, route-distinguisher , and ip binding vpn-instance  
commands, see IP Routing Command Referenc
e. 
For more information about the  multicast routing-enable command, see IP Multicast Command 
Reference .
    Add page 1285 to Favourites
    image text
    Enable zoom 
    							 149 
Enabling BIDIR-PIM 
Perform this configuration on all routers in the BIDIR-PIM domain. 
To  e n ab l e  B I D I R- PI M :  
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Enable 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 PIM 
network, static RP configuration is a tedious job. Generally, static RP configuration is just used as a 
backup means for the dynamic RP election mechan ism to enhance the robustness and operation 
manageability of a multicast network. 
 
  CAUTION: 
In a PIM network, if both PIM-SM and BIDIR-PIM 
are enabled, do not configure the same RP to serve 
PIM-SM and BIDIR-PIM simultaneously to avoid 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 BIDIR-PIM, a static RP can be specified with a virtual IP address. For example, if the IP addresses of the 
interfaces at the two ends of a link are 10.1.1.1/24 and 10.1.1.2/24, you can specify a virtual IP address, 
like 10.1.1.100/24, for the static RP. As a result, the link becomes an RPL.  
 
  IMPORTANT: 
You must perform static RP configuration on all routers in the PIM-SM domain and specify the same RP 
address.  
 
Perform this configuration on all routers in the BIDIR-PIM domain. 
To configure a static RP: 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure a static RP for 
BIDIR-PIM.  static-rp
 rp-address  [ acl-number  ] 
[ preferred  ] bidir  No static RP by default
    Add page 1286 to Favourites
    image text
    Enable zoom 
    							 150 
Configuring a C-RP 
In a BIDIR-PIM domain, you can configure routers that int e n d  t o  b e c o m e  t h e  R P  a s  C - R Ps .  T h e  B S R  c o l l e c t s  
the C-RP information by receiving the C-RP-Adv messages from C-RPs or auto-RP announcements 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 recommend s 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 BIDIR-PIM domain.  
To configure a C-RP:  
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance  vpn-instance-name  ] N/A 
3.  Configure an interface to be a 
C-RP for BIDIR-PIM.  c-rp 
interface-type interface-number 
[  group-policy  acl-number | 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 BIDIR-PIM domain. 
•   An RP can serve multiple multicast groups or all multicast groups. Only one RP can forward multicast 
traffic for a multicast group at a moment. 
 
Enabling auto-RP 
Auto-RP announcement and discovery messages are addressed to the multicast group addresses 
224.0.1.39 and 224.0.1.40. With auto-RP enabled on a device, the device can receive these two types 
of messages and record the RP information carried in such messages. 
To enable auto-RP:  
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Enable auto-RP. 
auto-rp enable  Disabled by default 
 
Configuring C-RP timers globally 
To enable the BSR to distribute the RP-set information within the 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 IP address togeth er with the RP-set information in its bootstrap 
messages. The BSR then floods the bootstrap me ssages to all PIM routers in the network.
    Add page 1287 to Favourites
    image text
    Enable zoom 
    							 151 
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 within the timeout interval, 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 public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  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 configuration of other timers in BIDIR-PIM, see 
Configuring 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, PIM domain border, global  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 public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure an interface as a 
C-BSR.   c-bsr 
interface-type 
interface-number [ hash-length  
[ priority  ] ]  No C-BSRs are configured by 
default.
 
4.  Configure a legal BSR 
address range.   bsr-policy
 acl-number   Optional. 
No restrictions on BSR address 
range by default.
 
Configuring a BIDIR-PIM domain border 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A
    Add page 1288 to Favourites
    image text
    Enable zoom 
    							 152 
Step Command Remarks 
2.  Enter interface view.  interface 
interface-type 
interface-number   N/A 
3.
  Configure a BIDIR-PIM 
domain border.   pim bsr-boundary  By default, no 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 public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure the hash mask 
length.   c-bsr hash-length 
hash-length Optional. 
30 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 public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  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 
2.  Enter public network PIM 
view or VPN instance PIM 
view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Disable the BSM semantic 
fragmentation function.  undo bsm-fragment
 enable   By default, the BSM semantic 
fragmentation function is enabled.
    Add page 1289 to Favourites
    image text
    Enable zoom 
    							 153 
 
Configuring administrative scoping 
With administrative scoping disabled, a BIDIR-PIM domain has only one BSR. The BSR manages the 
whole network. To manage your network more effectively and specifically, partition the BIDIR-PIM 
domain into multiple admin-scope zones. Each admin-scope zone maintains a BSR, which serves a 
specific multicast group range. The global scope zone  also maintains a BSR, which serves all the rest 
multicast groups. 
Enabling administrative scoping 
Before you configure an admin-scope zone, you must enable administrative scoping first.  
Perform the following configuration on all routers in the BIDIR-PIM domain.  
To enable administrative scoping: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Enable administrative 
scoping.   c-bsr admin-scope 
Disabled by default 
 
Configuring an admin-scope zone boundary 
The boundary of each admin-scope zone is formed by ZBRs. Each admin-scope zone maintains a BSR, 
which serves a specific multicast group range. Multicast protocol packets (such as assert messages and 
bootstrap messages) that belong to this range 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 a multicast 
forwarding boundary.  multicast boundary 
group-address 
{  mask  | mask-length }   By default, no multicast forwarding 
boundary is configured. 
 
 
 NOTE: 
The 
group-address { mask | mask-length } part of the  multicast boundary  command can be used to 
specify the multicast groups an admin-scope zone  serves, in the range of 239.0.0.0/8. For more 
information about the  multicast boundary command, see 
IP Multicast Command Reference.   
Configuring C-BSRs for each admin-sc ope zone and the global-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.
    Add page 1290 to Favourites
    image text
    Enable zoom 
    							 154 
All the routers use the same hash algorithm to get the RP address corresponding to the specific multicast 
group.  
Configure C-BSRs for each admin-scope zone and the global-scope zone. 
You can configure the hash mask length and C-BSR priority globally, in an admin-scope zone, and in the 
global scope zone.  
•   The values configured in the global scope zone or admin-scope zone have preference over the 
global values.  
•   If you do not configure these parameters in the global scope zone or admin-scope zone, the 
corresponding global values will be used.  
For configuration of global C-BSR parameters, see  Configuring global C-BSR parameters.
  
•   Configure C-BSRs for each admin-scope zone 
Perform the following configuration on the router s 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 public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure a C-BSR for an 
admin-scope zone.  c-bsr group 
group-address  { mask | 
mask-length  } [  hash-length 
hash-length  | priority  priority  ] *  No C-BSRs are configured for an 
admin-scope zone by default. 
 
 
NOTE: 
The 
group-address { mask | mask-length } parameter of the  c-bsr group command can specify the 
multicast groups the C-BSR serves, in the range of 239.0.0.0/8. 
 
•   Configure C-BSRs for the global-scope zone 
Perform the following configuration on the routers  that you want to configure as C-BSRs in the 
global-scope zone.  
To configure a C-BSR for  the global-scope zone: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter public network PIM view 
or VPN instance PIM view.  pim
 [ vpn-instance 
vpn-instance-name  ]  N/A 
3.
  Configure a C-BSR for the 
global-scope zone.  c-bsr global 
[ hash-length 
hash-length  | priority  priority  ] * No C-BSRs are configured for the 
global-scope zone by default.
 
Configuring PIM-SSM 
 
 IMPORTANT: 
PIM-SSM needs the support of IGMPv3. Be sure to en
able IGMPv3 on PIM routers with multicast receivers.
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide