07-21-2010 08:37 AM - edited 03-06-2019 12:07 PM
Hi !
I'm in my final preparation of my CCNP certification BSCI exam, my exam is schedule to next Friday, so rapid answer will be appreciated. For final preparation I had buy How2Pass test exam to test my knowledge before going to the test center. I find I had some difficulties with IP multicast subject about troobleshooting.....
in the following question (see attach filed ng43.zip)
I answer to this question by :
The RP for this network ==> because the RPF ip address is set to 0.0.0.0 for the entry (*,224.1.1.1) the local IP address of this router is : 10.127.0.7 base on RP information
The multicast source of this router is serial 1/4 interface ==> the incomming interface is serial 1/4 for the entry (172.16.8.1,224.1.1.1) and the source multicast server will be at the IP address 172.16.8.1 and the next hop to reach this IP address is 10.139.16.130 base on RPF nbr information in this entry.
Because I did not sucessfully answer this question on the first time I also read the link provide on Cisco website for explanation :
http://www.cisco.com/en/US/docs/ios/12_2/switch/command/reference/xrfscmd6.html#wp1056899
which after reading help me to understand some point, but also raised some question.....
in the following output
The following is sample output from the show ip mroute command for a router operating in sparse mode:
Router# show ip mrouteIP Multicast Routing TableFlags: D - Dense, S - Sparse, C - Connected, L - Local, P - PrunedR - RP-bit set, F - Register flag, T - SPT-bit setTimers: Uptime/ExpiresInterface state: Interface, Next-Hop, State/Mode(*, 224.0.255.3), uptime 5:29:15, RP is 198.92.37.2, flags: SCIncoming interface: Tunnel0, RPF neighbor 10.3.35.1, DvmrpOutgoing interface list:Ethernet0, Forward/Sparse, 5:29:15/0:02:57(198.92.46.0/24, 224.0.255.3), uptime 5:29:15, expires 0:02:59, flags: CIncoming interface: Tunnel0, RPF neighbor 10.3.35.1Outgoing interface list:Ethernet0, Forward/Sparse, 5:29:15/0:02:57
my understanding the RP for the group 224.0.255.3 is 198.92.37.2 and the next hop to RP is 10.3.35.1. But in the second entry if the group 224.0.255.3 is used in sparse mode why is it not appear the R flag to tell this entry is pointing toward the RP like it is explain in table 45 in the same pages
R - RP-bit set | Indicates that the (S, G) entry is pointing toward the rendezvous point (RP). The RP is typically a prune state along the shared tree for a particular source. |
also in the table 45 I would like understand the following :
RP | Address of the rendezvous point router. For routers and access servers operating in sparse mode, this address is always 0.0.0.0. |
Base on my understanding the RP this entry will on the IP address of the RP in sparse mode, in dense mode because theire is no RP the value will be set to 0..... is had in error here ??
also in the following I find some contradiction base on what I had understand :
Someone can help me to understand !
Thanks a lot !
07-21-2010 01:38 PM
Hello Christian,
>> my understanding the RP for the group 224.0.255.3 is 198.92.37.2 and the next hop to RP is 10.3.35.1. But in the second entry if the group 224.0.255.3 is used in sparse mode why is it not appear the R flag to tell this entry is pointing toward the RP like it is explain in table 45 in the same pages
I would say that when the source is known switchover to SPT (source based tree) is already happened because switchover happens after first packet is received. This is something not explained in several books but it happens almot immediately with default settings.
so RPT is used to draw a tree
>>(*, 224.0.255.1), uptime 0:57:31, expires 0:02:59, RP is 224.0.0.0, flags: DC
Incoming interface: Null, RPF neighbor 224.0.0.0, Dvmrp well, A DVMRP tunnel is really legacy stuff I would not waste time on this 224.0.0.0 could not be an RP address in the same way we think of it (it is not a unicast address !!!)
Hope to help
Giuseppe
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: