First step MSDP peer the Establishment
1. respective show Run | S MSDP
Check Configuration and make adjustments
if there's an error in the back of Connect-source,
The original IP MSDP sa-filterout will disappear .
need to add
2. determine the two RP address
Guaranteed ground level up to
with Source Ping a bit .
3. determine the interface where the RP address is located
if the multi-interface RP addresses are consistent with configuration determination
4. Show IP MSDP peer ensures that neighbors are established properly
Step two: Building a shared tree
1. View this side whether the RP has been set up accordingly (*,G)
R2#shwoip Mroute
A, only (*224.0.1.40) But the back is attached stopped
Check to see if the server has have a RP- Related Settings and Query the local RP address on peer MSDP peers
and Check the next router
B, if both (*, group address) but with stopped
also indicates that this side has no relevant RP Settings
Strategy
--- individual group numbers for the PIM protocol Auto: 224.0.1.39224.0.1.40
BSR : 224.0.0.13
C, If the table key is successful check the next router
2 , follow the topology from RP to client finds next route for direction
R2#shwoip Mroute
repeat the last round But make sure the bottom-level gets to the RP
until the correct table entry is found
or find the client
3 , guarantee the source of DR has the correct table entry R6#showip PIM interface
Show IP Mroute
1 if not, check if the source is added to the group
2 Check that the appropriate interface is PIM-enabled
R6#showip PIM Interface
to determine the correct DR
Special Note If the client is a loopback for the router
or a switch. SVI you need plus IP PIM space-mode
4. finally determine whether the shared tree was successful on the RP
Step three The establishment of the source tree
1 , Ping Group address at source
A , on this side RP show IP Mroute
See if have ( S * G)
1.if not, check the source to the origin of the source to the RP address of the accessibility
Note Check Incoming interface
2 , check the source has no RP(dynamic plus mapping)
B , in the peer-to-peer RP Show Ipmroute
See if have ( S * G)
1, check whether to establish a normal neighbor relationship with the peer (preferably intermediate router to check)
and check the interface configuration for adjustments Note You need to establish a neighbor under the interface of the RPF check
If two lines are not IPPIM configured , view the peer
R2#show IP RPF 10.1.1.13
Failed, no route exists
2, according to the order of the check of the MSDP at the edge of more than multicast
Note Whether its BGP multicast neighbor is established
if no mulicast is more unicast
C , finally determine if the peer has established the correct ( S, *g)
D , view on this side is the export correct ?
Check the intermediate router if it is not correct whether there is a multicast delimitation
Pay special attention to whether you have a route to the source because the back router is converted from a shared tree to a shortest tree
an RPF check is required
2 . Check the source tree of the route after the RP is set up in turn
until the client client does not need to establish a source tree but requires a route with a source
3 , from this side The RP starts checking the rear router in turn
Show IP Mroute
If it does not exist Check Neighbor
if an interface error is entered
Check the show IPRPF Source Address
interface to adjust the RPF checksum
4 , in the source ping Group address
if it does not pass
check whether there are policies in turn
generally this side There will be more policies before the RP
Special attention Multicast ( UDP) go to unicast (ICMP) back pay particular attention to the use of trance generally not applicable
MSDP the wrong idea of the line