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 1211 to Favourites
    image text
    Enable zoom 
    							 75 
Figure 27  Changing an RPF route 
 
 
As shown in Figure 27, when no static multicast route is configured, Switch C’s RPF neighbor on the path 
back to Source is Switch A. The multicast information from Source travels along the path from Switch A 
to Switch C, which is the unicast route between the two routers. When a static multicast route is 
configured on Switch C and Switch B is configured  as Switch C’s RPF neighbor on the path back to 
Source, the multicast information from Source travels from Switch A to Switch B and then to Switch C.  
Creating an RPF route 
When a unicast route is blocked, multicast traffic forw arding might be stopped because of lack of an RPF 
route. By configuring a static multicast route for a gi ven multicast source, you can create an RPF route so 
that a multicast routing entry is created to guide multicast traffic forwarding regardless of whether a 
unicast route is available.  
Figure 28  Creating an RPF route 
 
 
As shown in Figure 28, the RIP domain and  the OSPF domain are unicast isolated from each other. When 
no static multicast route is configured, the hosts (Receivers) in the OSPF domain cannot receive the 
multicast packets that the multicast source (Source) sent in the RIP domain. After you configure a static 
Vlan-int10 1.1.1.2/24
Vlan-int10
1.1.1.1/24 Vlan-int20
2.2.2.2/24
Vlan-int20
2.2.2.1/24
Source
192.168.0.1/24
Source/Mask
Multicast Routing Table Static on Switch C
192.168.0.0/24
Interface
Vlan-int10
RPF neighbor/Mask
1.1.1.1/24
Source/Mask
Multicast Routing Table Static on Switch D
192.168.0.0/24
Interface
Vlan-int20
RPF neighbor/Mask
2.2.2.2/24 OSPF domain
RIP domain
Switch A Switch B Switch CSwitch D
Receiver
Receiver
Multicast packetsMulticast static route
    Add page 1212 to Favourites
    image text
    Enable zoom 
    							 76 
multicast route on Switch C and Switch D, specifying Switch B as the RPF neighbor of Switch C and 
specifying Switch C as the RPF neighbor of Switch D, the receivers can receive multicast data that the 
multicast source sent. 
 
  NOTE: 
•  Static multicast routes only affect RPF check but cannot guide multicast forwarding.  
•   A static multicast route is effective only on the multicast router on which it is confi
gured, and will not be
advertised throughout the network or redistributed to other routers. 
 
Multicast traceroute 
You can use the multicast traceroute utility to trace the path that a multicast stream flows down from the 
first-hop router to the last-hop router. 
Concepts in multicast traceroute 
•   Last-hop router—If one of the interfaces of a router connects to the subnet that contains the given 
destination address, and if the router can forward multicast streams from the given multicast source 
onto that subnet, that router is  called the last-hop router.  
•   First-hop router —The router that directly connects to the multicast source is called the first-hop 
router.  
•   Querier —The router that sends multicast traceroute requests is called the querier. 
Introduction to multicast traceroute packets 
A multicast traceroute packet is a special IGMP pac ket that is different from common IGMP packets in 
that its IGMP Type field is set to 0x1F or 0x1E and its destination IP address is a unicast address. The 
following types of multicast traceroute packets are available:  
•   Query, with the IGMP Type field set to 0x1F,  
•   Request, with the IGMP Type field set to 0x1F, and  
•   Response, with the IGMP Type field set to 0x1E.  
Process of multicast traceroute 
1. The querier sends a query to the last-hop router.  
2. After receiving the query, the last -hop router turns the query packet into a request packet by adding 
a response data block (which contai ns its interface addresses and packet statistics) to the end of 
the packet. It then forwards the request packet  through unicast to the previous hop for the given 
multicast source and group.  
3.  From the last-hop router to the multicast source, each hop adds a response data block to the end 
of the request packet and unicasts  it to the previous hop.  
4. When the first-hop router receives the request pac ket, it changes the packet type to indicate a 
response packet. Then, it sends the complete d packet through unicast to the querier.  
Configuration task list 
 
Task  Remarks 
Enabling IP multicast routing  Required
    Add page 1213 to Favourites
    image text
    Enable zoom 
    							 77 
Task  Remarks 
Configuring multicast routing and 
forwarding Configuring static multicast routes 
Optional 
Configuring a multicast routing policy Optional 
Configuring a multicast forwarding range Optional  
Configuring the multicast forwarding table size Optional 
Tracing a multicast path Optional 
 
 IMPORTANT: 
IP multicast does not support secondary IP addre
ss segments. Namely, multicast can be routed and 
forwarded only through primary IP addresses even if  secondary addresses are configured on the ports. 
For more information about primary  and secondary IP addresses, see 
Layer 3— IP Services Configuration
Guide.   
Enabling IP multicast routing 
Before you configure any Layer 3 multicast functionality, you must enable IP multicast routing.  
Enabling IP multicast routing 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
 
 
Enabling IP multicast routing 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 a route 
distinguisher (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. 
 
For more information about the ip vpn-instance and route-distinguisher  commands, see IP Routing 
Command Referenc
e. 
Configuring multicast routing and forwarding  
Configuration prerequisites 
Before you configure multicast routing and forwarding, complete the following tasks:
    Add page 1214 to Favourites
    image text
    Enable zoom 
    							 78 
•  Configure a unicast routing protocol so that all  devices in the domain are interoperable at the 
network layer. 
•   Enable PIM (PIM-DM or PIM-SM). 
•   Determine the maximum number of downstream nodes  for a single multicast forwarding table entry. 
•   Determine the maximum number of entries in the multicast forwarding table. 
Configuring static multicast routes 
By configuring a static multicast route for a given multicast source, you can specify an RPF interface or an 
RPF neighbor for multicast traffic from that source. If you want to remove a specific static multicast route, 
use the  undo ip rpf-route-static  command, if you want to remove all static multicast routes, use the delete 
ip rpf-route-static  command.  
To configure a static multicast route: 
 
Step  Command  Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure a static 
multicast route.  ip rpf-route-static 
[ vpn-instance vpn-instance-name  ] 
source-address  { mask  | mask-length } [ protocol  
[ process-id  ] ] [ route-policy  policy-name ] 
{  rpf-nbr-address |  interface-type interface-number  } 
[ preference  preference ] [ order  order-number  ]  No static multicast route 
configured by default.
 
3.  Delete static 
multicast routes.  delete ip rpf-route-static 
[ vpn-instance 
vpn-instance-name  ]  Optional. 
 
 
IMPORTANT: 
When you configure a static multicast route, you cannot specify an RPF neighbor
 by providing the type 
and number (
interface-type interface-number) of the interface if the interf ace of the RPF neighbor is a 
Layer 3 Ethernet interface, Layer 3  aggregate interface, Loopback interf ace, or VLAN interface. Instead,
you can specify such an RPF neighbor only by its address (
rpf-nbr-address).   
Configuring a multicast routing policy 
You can configure the router to determine the RPF ro ute based on the longest match principle. For more 
information about RPF route selection, see  RPF check process.  
B

y configuring per-source or per-source-and-group load splitting, you can optimize the traffic delivery 
when multiple data flows are handled.  
Configuring a multicast routing policy for the public network 
 
Step  Command  Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure the device to select 
the RPF route based on the 
longest match.   multicast longest-match  The route with the highest priority is 
selected as the RPF route by 
default.
 
3.  Configure multicast load 
splitting.  multicast load-splitting
 { source | 
source-group  }  Optional. 
Disabled by default.
    Add page 1215 to Favourites
    image text
    Enable zoom 
    							 79 
 
Configuring a multicast routing policy in a VPN instance 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter VPN instance view. 
ip vpn-instance vpn-instance-name  N/A 
3.  Configure the device to 
select the RPF route based 
on the longest match.  multicast longest-match  The route with the highest priority 
is selected as the RPF route by 
default. 
4.
  Configure multicast load 
splitting.  multicast load-splitting
 { source | 
source-group  }  Optional. 
Disabled by default.  
 
Configuring a multicast forwarding range 
Multicast packets do not travel without a boundary 
in a network. The multicast data corresponding to 
each multicast group must be transmitted within a definite scope.  
You can configure a forwarding boundary specific to a particular multicast group on all interfaces that 
support multicast forwarding. A multicast forwarding boundary sets the boundary condition for the 
multicast groups in the specified range. If the destination address of a multicast packet matches the set 
boundary condition, the packet will not be forwarded. After you configure an interface as a multicast 
boundary, the interface can no longer forward multic ast packets—including packets sent from the local 
device—or receive multicast packets.  
To configure a multicast forwarding range:  
 
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 }   No forwarding boundary by 
default.  
 
Configuring the multicast forwarding table size 
Configuration guidelines 
The switch maintains the corresponding forwarding entry for each multicast packet that it receives. 
Excessive multicast routing entries, however, can exhaust the switch’s memory and cause lower 
performance. You can set a limit on the number of en
tries in the multicast forwarding table based on the 
networking situation and the performance requirements. If the configured maximum number of multicast 
forwarding table entries is smaller than the current va lue, the forwarding entries in excess are not deleted 
immediately. Instead, the multicast  routing protocol that runs on the switch deletes them. The switch no 
longer adds new multicast forwarding entries until th e number of existing multicast forwarding entries 
comes down below the configured value.  
When forwarding multicast traffic, the switch replicates a copy of the multicast traffic for each 
downstream node and forwards the traffic. Therefore, each of these downstream nodes forms a branch 
of the multicast distribution tree. You can configure the maximum number of downstream nodes (the
    Add page 1216 to Favourites
    image text
    Enable zoom 
    							 80 
m a x i m u m  n u m b e r  o f  o u t g o i n g  i n t e r f a c e s ) ,  f o r  a  s i n g l e   entry in the multicast forwarding table to lessen the 
burden on the switch for replicating multicast traffic. If the configured maximum number of downstream 
nodes for a single multicast forwarding entry is smaller than the current number, the downstream nodes 
in excess are not deleted immediatel y. Instead, the multicast routing protocol that runs on the switch 
deletes them. The switch no longer adds new multic ast forwarding entries for newly added downstream 
nodes until the number of existing downstream nodes comes down below the configured value. 
Configuration procedure 
To configure the multicast forwarding table size for the public network:   
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Configure the maximum 
number of entries in the 
multicast forwarding table.  multicast forwarding-table
 
route-limit  limit  Optional. 
2000 by default. 
3.
  Configure the maximum 
number of downstream nodes 
for a single multicast 
forwarding entry.  multicast forwarding-table 
downstream-limit 
limit  Optional. 
128 by default. 
 
To configure the multicast forwarding table size in a VPN instance:   
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter VPN instance view. 
ip vpn-instance vpn-instance-name N/A 
3.  Configure the maximum 
number of entries in the 
multicast forwarding table.  multicast forwarding-table
 
route-limit  limit  Optional. 
2000 by default.  
4.
  Configure the maximum 
number of downstream nodes 
for a single route in the 
multicast forwarding table.  multicast forwarding-table 
downstream-limit 
limit  Optional. 
128 by default. 
 
Tracing a multicast path 
You can run the 
mtracert command to trace the path down which the multicast traffic flows from a given 
first-hop router to the last-hop router.  
To trace a multicast path: 
 
Task Command Remarks 
Trace a multicast path.  mtracert 
source-address  
[ [ last-hop-router-address  ] 
group-address  ]  Available in any view
    Add page 1217 to Favourites
    image text
    Enable zoom 
    							 81 
Displaying and maintaining multicast routing and 
forwarding 
 
Task Command Remarks 
Display multicast boundary 
information.  display multicast [ all-instance
 | vpn-instance 
vpn-instance-name  ] boundary [ group-address  [ mask | 
mask-length  ] ] [ interface  interface-type 
interface-number ] [ |  { begin | exclude  | include  } 
regular-expression  ]   Available in any 
view 
Display multicast 
forwarding table 
information. display multicast [ all-instance
 | vpn-instance 
vpn-instance-name  ] forwarding-table  [ source-address 
[  mask  { mask  | mask-length  } ] | group-address  [ mask 
{  mask  | mask-length  } ] | incoming-interface  
{  interface-type interface-number  | register  } | 
outgoing-interface { exclude  | include  | match  } 
{  interface-type interface-number  | register  } | statistics  | 
slot  slot-number  ] * [ port-info  ] [ | { begin |  exclude | 
include  } regular-expression ]  Available in any 
view
 
Display the DF information 
of the multicast forwarding 
table .  display multicast [ all-instance
 | vpn-instance 
vpn-instance-name  ] forwarding-table  df-info  
[  rp-address  ] [ slot slot-number  ] [ | { begin  | exclude  | 
include  } regular-expression ]   Available in any 
view 
Display information about 
the multicast routing table.
 display multicast [ all-instance
 | vpn-instance 
vpn-instance-name  ] routing-table [ source-address 
[  mask  { mask  | mask-length  } ] | group-address  [ mask 
{  mask  | mask-length  } ] | incoming-interface  
{  interface-type interface-number  | register  } | 
outgoing-interface { exclude  | include  | match  } 
{  interface-type interface-number  | register  } ] * [ |  
{  begin |  exclude | include  } regular-expression  ] Available in any 
view
 
Display information about 
the static multicast routing 
table.  display multicast routing-table
 [ all-instance | 
vpn-instance  vpn-instance-name  ] static [ source-address 
{  mask-length  | mask } ] [ | { begin | exclude | include  } 
regular-expression  ]   Available in any 
view
 
Display RPF route 
information about the 
specified multicast source.
 display multicast [ all-instance | vpn-instance 
vpn-instance-name
 ] rpf-info source-address 
[  group-address  ] [ | { begin  | exclude  | include  } 
regular-expression  ]  Available in any 
view
 
Clear forwarding entries 
from the multicast 
forwarding table.
 reset multicast 
[ all-instance | vpn-instance 
vpn-instance-name  ] forwarding-table  { { source-address 
[  mask  { mask  | mask-length  } ] | group-address  [ mask 
{  mask  | mask-length  } ] | incoming-interface  
{  interface-type interface-number  | register  } } * | all  } Available in user 
view
 
Clear routing entries from 
the multicast routing table.
 reset multicast 
[ all-instance | vpn-instance 
vpn-instance-name  ] routing-table { { source-address  
[  mask  { mask  | mask-length  } ] | group-address  [ mask 
{  mask  | mask-length  } ] | incoming-interface  
{  interface-type interface-number  | register  } } * | all  } Available in user 
view
    Add page 1218 to Favourites
    image text
    Enable zoom 
    							 82 
 IMPORTANT: 
The 
reset  command clears the information in the multicast routin
g table or the multicast forwarding table,
and thus might cause failure of multicast transmission. 
 
When a routing entry is deleted from the multicast routing table, the corresponding forwarding entry is 
also deleted from the multicast forwarding table. 
When a forwarding entry is deleted from the multicas t forwarding table, the corresponding routing entry 
is also deleted from the multicast routing table. 
For more information about desi gnated forwarder (DF), see Configuring PIM (available only on the HP 
5

500 EI) . 
Configuration examples 
Changing an RPF route 
Network requirements 
PIM-DM runs in the network. All switches in the network support multicast. Switch A, Switch B, and Switch 
C run OSPF. Typically, Receiver can receive the multicast data from Source through the path: Switch A to 
Switch B, which is the same as the unicast route.  
Perform the following configuration so that Receiver can receive the multicast data from Source through 
the path: Switch A to Switch C to Switch B, which is different from the unicast route.  
Figure 29  Network diagram  
 
 
Configuration procedure 
1. Configure IP addresses and unicast routing: 
Configure the IP address  and subnet mask for each interface as per  Figure 29. (Details not sh
own.) 
Multicast static route
Switch A Switch B
Switch CVlan-int102
30.1.1.2/24
Vlan-int103
40.1.1.2/24
Vlan-int200 50.1.1.1/24 Vlan-int103
40.1.1.1/24 Vlan-int101
20.1.1.2/24
Vlan-int101
20.1.1.1/24
Vlan-int102 30.1.1.1/24 Vlan-int100
10.1.1.1/24
Source Receiver
50.1.1.100/24 10.1.1.100/24
PIM-DM
    Add page 1219 to Favourites
    image text
    Enable zoom 
    							 83 
Enable OSPF on the switches in the PIM-DM domain. Ensure the network-layer interoperation 
among the switches in the PIM-DM  domain. Make sure that the switches can dynamically update 
their routing information by leveraging the unicast routing protocol. (Details not shown.)  
2.  Enable IP multicast routing, and enable PIM-DM and IGMP: 
# Enable IP multicast routing on Switch B, enable  PIM-DM on each interface, and enable IGMP on 
VLAN-interface 100. 
 system-view 
[SwitchB] multicast routing-enable 
[SwitchB] interface vlan-interface 100 
[SwitchB-Vlan-interface100] igmp enable 
[SwitchB-Vlan-interface100] pim dm 
[SwitchB-Vlan-interface100] quit 
[SwitchB] interface vlan-interface 101 
[SwitchB-Vlan-interface101] pim dm 
[SwitchB-Vlan-interface101] quit 
[SwitchB] interface vlan-interface 102 
[SwitchB-Vlan-interface102] pim dm 
[SwitchB-Vlan-interface102] quit 
# Enable IP multicast routing on Switch A, and enable PIM-DM on each interface. 
 system-view 
[SwitchA] multicast routing-enable 
[SwitchA] interface vlan-interface 200 
[SwitchA-Vlan-interface200] pim dm 
[SwitchA-Vlan-interface200] quit 
[SwitchA] interface vlan-interface 102 
[SwitchA-Vlan-interface102] pim dm 
[SwitchA-Vlan-interface102] quit 
[SwitchA] interface vlan-interface 103 
[SwitchA-Vlan-interface103] pim dm 
[SwitchA-Vlan-interface103] quit 
The configuration on Switch C is similar to the configuration on Switch A. (Details not shown.)  
# Use the  display multicast rpf-info  command to view the RPF route to Source on Switch B.  
[SwitchB] display multicast rpf-info 50.1.1.100 
 RPF information about source 50.1.1.100: 
     RPF interface: Vlan-interface102, RPF neighbor: 30.1.1.2 
     Referenced route/mask: 50.1.1.0/24 
     Referenced route type: igp 
     Route selection rule: preference-preferred 
     Load splitting rule: disable 
The output shows that the current RPF route on Swit ch B is contributed by a unicast routing protocol 
and the RPF neighbor is Switch A.  
3.  Configure a static multicast route: 
# Configure a static multicast route on Switch B, specifying Switch C as its RPF neighbor on the 
route to Source. 
[SwitchB] ip rpf-route-static 50.1.1.100 24 20.1.1.2 
4. Verify the configuration:
    Add page 1220 to Favourites
    image text
    Enable zoom 
    							 84 
# Use the  display multicast rpf-info  command to view the information about the RPF route to Source 
on Switch B.  
[SwitchB] display multicast rpf-info 50.1.1.100 
 RPF information about source 50.1.1.100: 
     RPF interface: Vlan-interface101, RPF neighbor: 20.1.1.2 
     Referenced route/mask: 50.1.1.0/24 
     Referenced route type: static multicast 
     Route selection rule: preference-preferred 
     Load splitting rule: disable 
The output shows that the RPF route on Switch B has changed. It is now the configured static 
multicast route, and the RPF neighbor is now Switch C.  
Creating an RPF route 
Network requirements 
PIM-DM runs in the network and all switches in the network support IP multicast. Switch B and Switch C 
r u n  OS P F,  a n d  h ave  n o  u n ic a s t  ro u t e s  t o  Swi t ch  A .  Ty pically, Receiver can receive the multicast data from 
Source 1 in the OSPF domain. 
Perform the following configuration so that Receiver can receive multicast data from Source 2, which is 
outside the OSPF domain.  
Figure 30  Network diagram 
 
 
Configuration procedure 
1. Configure IP addresses and unicast routing: 
Configure the IP address  and subnet mask for each interface as per  Figure 30. (Details not sh
own.) 
Enable OSPF on Switch B and Switch C. Ensure  the network-layer interoperation among Switch B 
and Switch C. Make sure that the switches can dynamically update their routing information by 
leveraging the unicast routing protocol. (Details not shown.)  
2.  Enable IP multicast routing, and enable PIM-DM and IGMP: 
# Enable IP multicast routing on Switch C, enable PIM-DM on each interface, and enable IGMP on 
VLAN-interface 100.
    All HP manuals Comments (0)

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