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 1341 to Favourites
    image text
    Enable zoom 
    							 205 
[SwitchC-bgp] router-id 2.2.2.2 
[SwitchC-bgp] peer 192.168.1.1 as-number 100 
[SwitchC-bgp] import-route ospf 1 
[SwitchC-bgp] quit 
# Redistribute BGP routes into OSPF on Switch B.  
[SwitchB] ospf 1 
[SwitchB-ospf-1] import-route bgp 
[SwitchB-ospf-1] quit 
# Redistribute BGP routes into OSPF on Switch C.  
[SwitchB] ospf 1 
[SwitchB-ospf-1] import-route bgp 
[SwitchB-ospf-1] quit 
5. Configure MSDP peers: 
# Configure an MSDP peer on Switch B.  
[SwitchB] msdp 
[SwitchB-msdp] peer 192.168.1.2 connect-interface vlan-interface 101 
[SwitchB-msdp] quit 
# Configure an MSDP peer on Switch C.  
[SwitchC] msdp 
[SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101 
[SwitchC-msdp] peer 192.168.3.2 connect-interface vlan-interface 102 
[SwitchC-msdp] quit 
# Configure MSDP peers on Switch E.  
[SwitchE] msdp 
[SwitchE-msdp] peer 192.168.3.1 connect-interface vlan-interface 102 
[SwitchE-msdp] quit 
6. Verify the configuration: 
Use the  display bgp peer  command to view the BGP peering  relationships between the switches. 
For example:  
# Display information about BGP peer ing relationships on Switch B.  
[SwitchB] display bgp peer 
 
 BGP local router ID : 1.1.1.1 
 Local AS number : 100 
 Total number of peers : 1                 Peers in established state : \
1 
 
  Peer                    AS  MsgRcvd  MsgSent OutQ PrefRcv Up/Down  Sta\
te 
 
  192.168.1.2            200       24       21    0       6 00:13:09 Est\
ablished 
# Display information about BGP peering relationships on Switch C.  
[SwitchC] display bgp peer 
 
 BGP local router ID : 2.2.2.2 
 Local AS number : 200 
 Total number of peers : 1                 Peers in established state : \
1
    Add page 1342 to Favourites
    image text
    Enable zoom 
    							 206 
  Peer                    AS  MsgRcvd  MsgSent OutQ PrefRcv Up/Down  Sta\
te 
 
  192.168.1.1            100       18       16    0       1 00:12:04 Est\
ablished 
To view the BGP routing table information on the switches, use the  display bgp routing-table 
command. For example:  
# Display BGP routing table information on Switch C.  
[SwitchC] display bgp routing-table 
 
 Total Number of Routes: 5 
 
 BGP Local router ID is 2.2.2.2 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? - incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
* >  1.1.1.1/32         192.168.1.1     0                     0       10\
0? 
* >i 2.2.2.2/32         0.0.0.0         0                     0       ? \
* >  192.168.1.0        0.0.0.0         0                     0       ? \
* >  192.168.1.1/32     0.0.0.0         0                     0       ? \
* >  192.168.1.2/32     0.0.0.0         0                     0       ? \
When the multicast source in PIM-SM 1 (Source 1) and the multicast source in PIM-SM 2 (Source 
2) send multicast information, receivers in PIM- SM 1 and PIM-SM 3 can receive the multicast data. 
You can use the  display msdp brief  command to view the brief information of MSDP peering 
relationships between the switches. For example:  
# Display brief information about MSDP  peering relationships on Switch B.  
[SwitchB] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  1            1            0            0            0            0 
 
  Peers Address     State     Up/Down time    AS     SA Count   Reset C\
ount 
  192.168.1.2        Up        00:12:27       200    13         0 
# Display brief information about MSDP peering relationships on Switch C.  
[SwitchC] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  2            2            0            0            0            0 
 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  192.168.3.2       Up       00:15:32        200    8          0 
  192.168.1.1       Up       00:06:39        100    13         0 
# Display brief information about MSDP peering relationships on Switch E.  
[SwitchE] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
    Add page 1343 to Favourites
    image text
    Enable zoom 
    							 207 
  1            1            0            0            0            0 
 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  192.168.3.1       Up       01:07:08        200    8          0 
# Display detailed MSDP peer information on Switch B.  
[SwitchB] display msdp peer-status 
MSDP Peer Information of VPN-Instance: public net 
  MSDP Peer 192.168.1.2, AS 200 
  Description: 
  Information about connection status: 
    State: Up 
    Up/down time: 00:15:47 
    Resets: 0 
    Connection interface: Vlan-interface101 (192.168.1.1) 
    Number of sent/received messages: 16/16 
    Number of discarded output messages: 0 
    Elapsed time since last connection or counters clear: 00:17:51 
  Information about (Source, Group)-based SA filtering policy: 
    Import policy: none 
    Export policy: none 
  Information about SA-Requests: 
    Policy to accept SA-Request messages: none 
    Sending SA-Requests status: disable 
  Minimum TTL to forward SA with encapsulated data: 0 
  SAs learned from this peer: 0, SA-cache maximum for the peer: none 
  Input queue size: 0, Output queue size: 0 
  Counters for MSDP message: 
    Count of RPF check failure: 0 
    Incoming/outgoing SA messages: 0/0 
    Incoming/outgoing SA requests: 0/0 
    Incoming/outgoing SA responses: 0/0 
    Incoming/outgoing data packets: 0/0 
Inter-AS multicast configuration by leveraging static RPF peers 
Network requirements 
As shown in Figure 61, AS 100 and AS 200 run OSPF within each AS, and run BGP between each other.   
PIM-SM 1 belongs to AS 100, and PIM-SM 2 and PIM-SM 3 belong to AS 200. Each PIM-SM domain 
has at least one multicast source or receiver.  
Loopback 0 is configured as a C-BSR and a C-RP of the related PIM-SM domain on Switch A, Switch D, 
and Switch G, respectively.  
According to the RPF principle, the device can receive SA messages that pass the filtering policy from its 
static RPF peers. To share multicast source information among PIM-SM domains without changing the 
unicast topology structure, configure MSDP peering  relationships for the RPs of the PIM-SM domains and 
configure static RPF peering relationships for the  MSDP peers to share multicast source information 
among the PIM-SM domains.
    Add page 1344 to Favourites
    image text
    Enable zoom 
    							 208 
Figure 61 Network diagram 
 
Device Interface IP address Device Interface IP address 
Source 1  - 192.168.1.100/24  Switch D  Vlan-int105  10.110.5.1/24 
Source 2  - 192.168.3.100/24  Vlan-int103 10.110.3.2/24 
Switch A  Vlan-int101  10.110.1.1/24  Loop0 2.2.2.2/32 
 Vlan-int102 10.110.2.1/24 Switch  E Vlan-int105 10.110.5.2/24 
 Loop0 1.1.1.1/32  Vlan-int300 192.168.3.1/24 
Switch B  Vlan-int101  10.110.1.2/24 Switch F Vlan-int106 10.110.6.1/24 
 Vlan-int100 192.168.1.1/24  Vlan-int104 10.110.4.2/24 
 Vlan-int103 10.110.3.1/24 Switch G Vlan-int106 10.110.6.2/24 
Switch C  Vlan-int102  10.110.2.2/24  Vlan-int400 192.168.4.1/24 
 Vlan-int200 192.168.2.1/24  Loop0 3.3.3.3/32 
 Vlan-int104 10.110.4.1/24     
Configuration procedure 
1. Configure IP addresses and unicast routing: 
Configure the IP address  and subnet mask for each interface as per  Figure 61. (Details not sh
own.) 
Configure OSPF for interconnection between the sw itches. Ensure the network-layer interoperation 
in each AS, and ensure the dynamic update of  routing information among the switches through a 
unicast routing protocol. (Details not shown.) 
2.  Enable IP multicast routing, enable PIM-SM and IGMP, and configure a PIM-SM domain border: 
# Enable IP multicast routing on Switch C, enable  PIM-SM on each interface, and enable IGMP on 
the host-side interface VLAN-interface 200.  
 system-view 
[SwitchC] multicast routing-enable 
[SwitchC] interface vlan-interface 102 
[SwitchC-Vlan-interface102] pim sm 
[SwitchC-Vlan-interface102] quit 
Vlan-int103
V la n
-i
n
t1 0
4
Switch B
Switch A
Source 1
AS 100
PIM-SM 1 PIM-SM 3
PIM-SM 2
Loop0
Switch D Switch E
Switch F
Switch G
Source 2
Vlan-int102
Vl an -
int
101
Vlan-int103 Vlan-int105Vlan-int106
Loop0
Receiver Receiver
Loop0
BGP peers
Vlan-int1
01
Vlan-int105 Vlan-int106
Vlan-
int
30 0 Vl
an-
int40 0
AS 200
V
l
a
n -
i
n t
1
0 4Vlan-int102
Vlan-int
200
Vlan-int100
Switch C
    Add page 1345 to Favourites
    image text
    Enable zoom 
    							 209 
[SwitchC] interface vlan-interface 200 
[SwitchC-Vlan-interface200] igmp enable 
[SwitchC-Vlan-interface200] pim sm 
[SwitchC-Vlan-interface200] quit 
[SwitchC] interface vlan-interface 104 
[SwitchC-Vlan-interface104] pim sm 
[SwitchC-Vlan-interface104] quit 
The configuration on Switch A, Switch B, Switch D, Switch E, Switch F, and Switch G is similar to 
that on Switch C. (Details not shown.) 
# Configure PIM domain borders on Switch B.  
[SwitchB] interface vlan-interface 103 
[SwitchB-Vlan-interface103] pim bsr-boundary 
[SwitchB-Vlan-interface103] quit 
The configuration on Switch C, Switch D, and Switch  F is similar to that on Switch B. (Details not 
shown.) 
3.  Configure C-BSRs and C-RPs: 
# Configure Loopback 0 as a C-BSR and a C-RP on Switch A.  
[SwitchA] pim 
[SwitchA-pim] c-bsr loopback 0 
[SwitchA-pim] c-rp loopback 0 
[SwitchA-pim] quit 
The configuration on Switch D and Switch G is simi lar to that on Switch A. (Details not shown.) 
4. Configure BGP, and redistribute BGP routin g information into OSPF, and OSPF routing 
information into BGP: 
# Configure the EBGP peer, and redistribute  OSPF routing information on Switch B.  
[SwitchB] bgp 100 
[SwitchB-bgp] router-id 1.1.1.2 
[SwitchB-bgp] peer 10.110.3.2 as-number 200 
[SwitchB-bgp] import-route ospf 1 
[SwitchB-bgp] quit 
# Configure the EBGP peer, and redistribute OSPF routing information on Switch D.  
[SwitchD] bgp 200 
[SwitchD-bgp] router-id 2.2.2.2 
[SwitchD-bgp] peer 10.110.3.1 as-number 100 
[SwitchD-bgp] import-route ospf 1 
[SwitchD-bgp] quit 
# Configure the EBGP peer, and redistribute OSPF routing information on Switch C. 
[SwitchC] bgp 100 
[SwitchC-bgp] router-id 1.1.1.3 
[SwitchC-bgp] peer 10.110.4.2 as-number 200 
[SwitchC-bgp] import-route ospf 1 
[SwitchC-bgp] quit 
# Configure the EBGP peer, and redistribute  OSPF routing information on Switch F.  
[SwitchF] bgp 200 
[SwitchF-bgp] router-id 3.3.3.1 
[SwitchF-bgp] peer 10.110.4.1 as-number 100
    Add page 1346 to Favourites
    image text
    Enable zoom 
    							 210 
[SwitchF-bgp] import-route ospf 1 
[SwitchF-bgp] quit 
# Redistribute BGP routing information into OSPF on Switch B. 
[SwitchB] ospf 1 
[SwitchB-ospf-1] import-route bgp 
[SwitchB-ospf-1] quit 
# Redistribute BGP routing information into OSPF on Switch D. 
[SwitchD] ospf 1 
[SwitchD-ospf-1] import-route bgp 
[SwitchD-ospf-1] quit 
# Redistribute BGP routing information into OSPF on Switch C. 
[SwitchC] ospf 1 
[SwitchC-ospf-1] import-route bgp 
[SwitchC-ospf-1] quit 
# Redistribute BGP routing information into OSPF on Switch F. 
[SwitchF] ospf 1 
[SwitchF-ospf-1] import-route bgp 
[SwitchF-ospf-1] quit 
5. Configure MSDP peers and static RPF peers: 
# Configure Switch D and Switch G as the MSDP  peers and static RPF peers of Switch A.  
[SwitchA] ip ip-prefix list-dg permit 10.110.0.0 16 greater-equal 16 less-equal 32 
[SwitchA] msdp 
[SwitchA-msdp] peer 10.110.3.2 connect-interface vlan-interface 101 
[SwitchA-msdp] peer 10.110.6.2 connect-interface vlan-interface 102 
[SwitchA-msdp] static-rpf-peer 10.110.3.2 rp-policy list-dg 
[SwitchA-msdp] static-rpf-peer 10.110.6.2 rp-policy list-dg 
[SwitchA-msdp] quit 
# Configure Switch A as the MSDP peer and static RPF peer of Switch D.  
[SwitchD] ip ip-prefix list-a permit 10.110.0.0 16 greater-equal 16 less\
-equal 32 
[SwitchD] msdp 
[SwitchD-msdp] peer 10.110.1.1 connect-interface vlan-interface 103 
[SwitchD-msdp] static-rpf-peer 10.110.1.1 rp-policy list-a 
[SwitchD-msdp] quit 
# Configure Switch A as the MSDP peer and static RPF peer of Switch G.  
[SwitchG] ip ip-prefix list-a permit 10.110.0.0 16 greater-equal 16 less\
-equal 32 
[SwitchG] msdp 
[SwitchG-msdp] peer 10.110.2.1 connect-interface vlan-interface 106 
[SwitchG-msdp] static-rpf-peer 10.110.2.1 rp-policy list-a 
[SwitchG-msdp] quit 
6. Verify the configuration: 
Use the  display bgp peer  command to view the BGP peering re lationships between the switches. 
I f  t h e  c o m m a n d  g i v e s  n o  o u t p u t  i n f o r m a t i o n  o n  S w i t c h  A ,  i t  m e a n s  t h a t  n o  B G P  p e e r i n g  r e l a t i o n s h i p  
has been established between Switch A and Swit ch D, or between Switch A and Switch G.  
When the multicast source in PIM-SM 1 (Source 1) and the multicast source in PIM-SM 2 (Source 
2) send multicast information, receivers in PIM- SM 1 and PIM-SM 3 can receive the multicast data.
    Add page 1347 to Favourites
    image text
    Enable zoom 
    							 211 
You can use the display msdp brief  command to view the brief information of MSDP peering 
relationships between the switches. For example:  
# Display brief MSDP peer information on Switch A.  
[SwitchA] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  2            2            0            0            0            0 
 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  10.110.3.2        Up       01:07:08        ?      8          0 
  10.110.6.2        Up       00:16:39        ?      13         0 
# Display brief MSDP peer information on Switch D.  
[SwitchD] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  1            1            0            0            0            0 
 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  10.110.1.1        Up       01:07:09        ?      8          0 
# Display brief MSDP peer information on Switch G.  
[SwitchG] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  1            1            0            0            0            0 
 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  10.110.2.1        Up       00:16:40        ?      13         0 
Anycast RP configuration 
Network requirements 
As shown in  Figure 62, t he PIM-SM domain has multiple multicast sources and receivers. OSPF runs 
within the domain to provide unicast routes.  
Configure the Anycast RP application so that the receiver-side DRs and the source-side DRs can initiate 
a join message to their respective RPs that are the topologically nearest to them.  
On Switch B and Switch D, configure the interface Loopback 10 as a C-BSR, and Loopback 20 as a C-RP.   
The router ID of Switch B is 1.1.1.1, and the router ID of Switch D is 2.2.2.2. Set up an MSDP peering 
relationship between Switch B and Switch D.
    Add page 1348 to Favourites
    image text
    Enable zoom 
    							 212 
Figure 62 Network diagram 
 
Device Interface  IP address Device Interface IP address 
Source 1  — 10.110.5.100/24  Switch C  Vlan-int101  192.168.1.2/24 
Source 2  — 10.110.6.100/24  Vlan-int102 192.168.2.2/24 
Switch A  Vlan-int300  10.110.5.1/24 Switch D Vlan-int200 10.110.3.1/24 
 Vlan-int103 10.110.2.2/24  Vlan-int104 10.110.4.1/24 
Switch B  Vlan-int100  10.110.1.1/24  Vlan-int102 192.168.2.1/24 
 Vlan-int103 10.110.2.1/24  Loop0 2.2.2.2/32 
 Vlan-int101 192.168.1.1/24  Loop10 4.4.4.4/32 
 Loop0 1.1.1.1/32  Loop20 10.1.1.1/32 
 Loop10 3.3.3.3/32 Switch E Vlan-int400 10.110.6.1/24 
 Loop20 10.1.1.1/32  Vlan-int104 10.110.4.2/24  
Configuration procedure 
1. Configure IP addresses and unicast routing: 
Configure the IP address  and subnet mask for each interface as per  Figure 62. (Details not sh
own.) 
Configure OSPF for interconnection between the sw itches. Ensure the network-layer interoperation 
among the switches, and ensure the dynamic updat e of routing information between the switches 
through a unicast routing protocol. (Details not shown.) 
2.  Enable IP multicast routing, and enable PIM-SM and IGMP: 
# Enable IP multicast routing on Switch B, enable  PIM-SM on each interface, and enable IGMP on 
the host-side interface VLAN-interface 100.  
 system-view 
[SwitchB] multicast routing-enable 
[SwitchB] interface vlan-interface 100 
[SwitchB-Vlan-interface100] igmp enable 
[SwitchB-Vlan-interface100] pim sm 
[SwitchB-Vlan-interface100] quit 
L oo p0
Lo
op20
L
oop2 0
Loo
p0
V
la n
-in
t1 0
1 Vla n
-in t
1 01
V
la
n -
i
n t
1
0 2 V
l
a
n -
in t
1
0 2
V
la
n
-i
n
t1 0
3
V
la
n -
i
n
t1
03
V la n
-in
t1 0
4
V l
a
n-
in t
1
04
    Add page 1349 to Favourites
    image text
    Enable zoom 
    							 213 
[SwitchB] interface vlan-interface 103 
[SwitchB-Vlan-interface103] pim sm 
[SwitchB-Vlan-interface103] quit 
[SwitchB] interface Vlan-interface 101 
[SwitchB-Vlan-interface101] pim sm 
[SwitchB-Vlan-interface101] quit 
[SwitchB] interface loopback 0 
[SwitchB-LoopBack0] pim sm 
[SwitchB-LoopBack0] quit 
[SwitchB] interface loopback 10 
[SwitchB-LoopBack10] pim sm 
[SwitchB-LoopBack10] quit 
[SwitchB] interface loopback 20 
[SwitchB-LoopBack20] pim sm 
[SwitchB-LoopBack20] quit 
The configuration on Switch A, Switch C, Switch D, and Switch E is similar to the configuration on 
Switch B.  
3.  Configure C-BSRs and C-RPs: 
# Configure Loopback 10 as a C-BSR and  Loopback 20 as a C-RP on Switch B.  
[SwitchB] pim 
[SwitchB-pim] c-bsr loopback 10 
[SwitchB-pim] c-rp loopback 20 
[SwitchB-pim] quit 
The configuration on Switch D is similar to the configuration on Switch B.  
4. Configure MSDP peers: 
# Configure an MSDP peer on Loopback 0 of Switch B. 
[SwitchB] msdp 
[SwitchB-msdp] originating-rp loopback 0 
[SwitchB-msdp] peer 2.2.2.2 connect-interface loopback 0 
[SwitchB-msdp] quit 
# Configure an MSDP peer on Loopback 0 of Switch D. 
[SwitchD] msdp 
[SwitchD-msdp] originating-rp loopback 0 
[SwitchD-msdp] peer 1.1.1.1 connect-interface loopback 0 
[SwitchD-msdp] quit 
5. Verify the configuration: 
You can use the  display msdp brief  command to view the brief information of MSDP peering 
relationships between the switches.  
# Display brief MSDP peer information on Switch B.  
[SwitchB] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  1            1            0            0            0            0 
 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  2.2.2.2           Up       00:10:17        ?      0          0
    Add page 1350 to Favourites
    image text
    Enable zoom 
    							 214 
# Display brief MSDP peer information on Switch D.  
[SwitchD] display msdp brief 
MSDP Peer Brief Information of VPN-Instance: public net 
  Configured   Up           Listen       Connect      Shutdown     Down \
  1            1            0            0            0            0 
 
  Peers Address    State    Up/Down time    AS     SA Count   Reset Cou\
nt 
  1.1.1.1           Up       00:10:18        ?      0          0 
To view the PIM routing information on the switches, use the display pim routing-table command. 
When Source 1 (10.110.5.100/24) sends multicast data to multicast group G (225.1.1.1), Host 
A joins multicast group G. By comparing the PIM routing information displayed on Switch B with 
that displayed on Switch D, you can see that Swit ch B acts now as the RP for Source 1 and Host 
A. 
# Display PIM routing information on Switch B.  
[SwitchB] display pim routing-table 
 VPN-Instance: public net 
 Total 1 (*, G) entry; 1 (S, G) entry 
 
 (*, 225.1.1.1) 
     RP: 10.1.1.1 (local) 
     Protocol: pim-sm, Flag: WC 
     UpTime: 00:15:04 
     Upstream interface: Register 
         Upstream neighbor: NULL 
         RPF prime neighbor: NULL 
     Downstream interface(s) information: 
     Total number of downstreams: 1 
         1: Vlan-interface100 
             Protocol: igmp, UpTime: 00:15:04, Expires: - 
 
 (10.110.5.100, 225.1.1.1) 
     RP: 10.1.1.1 (local) 
     Protocol: pim-sm, Flag: SPT 2MSDP ACT 
     UpTime: 00:46:28 
     Upstream interface: Vlan-interface103 
         Upstream neighbor: 10.110.2.2 
         RPF prime neighbor: 10.110.2.2 
     Downstream interface(s) information: 
     Total number of downstreams: 1 
         1: Vlan-interface100 
             Protocol: pim-sm, UpTime:  - , Expires:  - 
# Display PIM routing information on Switch D.  
[SwitchD] display pim routing-table 
No information is output on Switch D. 
Host A has left multicast group G. Source 1 has  stopped sending multicast data to multicast group 
G. When Source 2 (10.110.6.100/24) sends multic ast data to G, Host B joins G. By comparing 
the PIM routing information displayed on Switch B  with that displayed on Switch D, you can see 
that Switch D acts now as the RP for Source 2 and Host B.
    All HP manuals Comments (0)

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