MSDP peer

From: Bit Gossip (bit.gossip@chello.nl)
Date: Fri Jan 26 2007 - 12:52:53 ART

• Next message: Maxim Kurushkin: "NAT question"
• Previous message: Noble: "Re: SP Track using Dynamips"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi Group,
I notice that msdp behaves differently from what I expect.
I have a very simple setup:
s1 (lo0 10.3.70.7)
s2 (lo0 10.3.80.8)
r4 (lo0 10.2.40.4)

s1#show run | in msdp
ip msdp peer 10.3.80.8 connect-source Loopback0
ip msdp cache-sa-state

s2#show run | in msdp
ip msdp peer 10.3.70.7 connect-source Loopback0
ip msdp peer 10.2.40.4 connect-source Loopback0

r4#show run | in msdp
ip msdp peer 10.3.80.8 connect-source Loopback0

s1 ---MSDP--- s2 ---MSDP--- r4

There is no BGP, only IGP for loopback reachabilty.

According to
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_c/ipcpt3/1cfmsdp.htm#wp1001330

'Before configuring MSDP, the addresses of all MSDP peers must be known
in BGP or MBGP. If that does not occur, you must configure MSDP default
peering when you configure MSDP.'

So, as I have not configured default-peer, s2 should not pass SA from s1
to r4.

Actually it does! Why?

r4# show ip msdp sa-cache
MSDP Source-Active Cache - 1 entries
(10.1.1.123, 224.56.78.9), RP 10.3.70.7, AS ?,00:06:24/00:05:11, Peer
10.3.80.8

Thanks,
Luca.

• Next message: Maxim Kurushkin: "NAT question"
• Previous message: Noble: "Re: SP Track using Dynamips"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Thu Feb 08 2007 - 23:46:57 ART