I guess it's if you setup a MSDP peer with a BGP AS, but don't use BGP as
the transport protocol:
[STUF}-{R1}-----{R2}-----{R3}----{STUFF}
BGP 10--}{------OSPF-----}{---BGP 20--}
You can tell R1 who peers with R3 via MSDP that it's in remote-as 20,
because if the peering is via BGP then the AS is learnt, thus pointless.
I cant see a reason why you would use it to tell MSDP that the peer is in a
different AS.....
Not much help, but your point is true, it does seem kinda pointless. Unless
it's something to do with the RPF check? I have had issues with MSDP over
an OSPF backbone, it seems to like BGP for RPF reasons.
\Sam.
On Fri, Dec 20, 2013 at 4:41 PM, Matt Sherman <matt.sherman2_at_gmail.com>wrote:
> Hi,
>
> What's the point of the "remote-as" option in the msdp peer configuration?
> MSDP seems to work without it.
>
> Thanks,
> Matt
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Fri Dec 20 2013 - 16:52:26 ART
This archive was generated by hypermail 2.2.0 : Wed Jan 01 2014 - 20:26:19 ART