Refer to the exhibit.
Two multicast domains are configured as shown and connected with MSDP, but the two domains
are unable to communicate. Which two actions can you take to correct the problem? (Choose two.)
A.
Change the peering IP address in AS 65220 to 10.0.0.20.
B.
Change the peering AS on R2 to 65210.
C.
Verify that UDP port 639 is open.
D.
Verify that TCP port 139 is open.
E.
Change the MSDP originator-id to GigabitEthernet 0/0/0 on both routers.
F.
Change the MSDP peering IP address on R2 to 172.16.1.13.
B : why changing the peer as ? it’s well configured
There is no correct answers as per given configuration output
A and C
TCP/UDP 639 is MSDP default port number
B Is Wrong, even if the AS number is not configured with the right value, it is just for display and does not affect the peering (AS per Cisco Docs).
I believe A & C
remote-as as-number
(Optional) Autonomous system number of the MSDP peer. This is used for display purposes only.
There are cases where a peer might appear to be in another autonomous system (other than the one it really resides in) when you have an MSDP peering session but do not have a BGP peer session with that peer. In this case, if the prefix of the peer is injected by another autonomous system, it is displayed as the autonomous system number of the peer (and is misleading).
Sorry, C can’t be related as MSDP uses TCP and not UDP
Any one know the real answer yet?
– A & B should be correct, but I think here is an error in answer A: It should be “Change the peering IP address in AS 65210 to 10.0.0.20”
– AS number is relevant to decide if the MSDP neighbor in same PIM domain or not (same AS -> same PIM Domain)
– MSDP use TCP port 639, not UDP.