cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
536
Views
0
Helpful
18
Replies

No MSDP SA?

KGrev
Beginner
Beginner

Hi,

We are setting up msdp peering between two RP's.

We have yet to get it fully functioning but when we do "show ip msdp summary" or "show ip msdp peer",  there is a "?" for the SA.

We do get logs that the peer is up.

The commend we are using is

Router A = "ip msdp peer "routerB" connect-source loopback1"

Router B = "ip msdp peer "routerA" connect-source loopback1"

Our peer is up but we are not sharing multicast groups yet.

 

Thank you for any advice.

18 Replies 18

Harold Ritter
Cisco Employee
Cisco Employee

Hi @KGrev ,

> We have yet to get it fully functioning but when we do "show ip msdp summary" or "show ip msdp peer",  there is a "?" for the SA.

You probably mean that you see a "?" for the AS, right? This is not a problem.

> Our peer is up but we are not sharing multicast groups yet.

To determine if you get SA information, you need to do a "sh ip msdp sa-cache"

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Harold,

Thank you for your response.

>To determine if you get SA information, you need to do a "sh ip msdp sa-cache"

         When we use this command at Router B, we can see groups from Router A. However, we don't see groups from router B on router A. Additionally we cannot reach the groups from client devices trying to join distant groups from the other router.

Hi @KGrev ,

Did you configure the following command on both RPs?

ip msdp originator-id Loopback1

Regards,

 

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Sir,

Thank you for the advice. We had not configured that.
So far it's looking the same though. Router A shows two SA entries for
groups in router B. But we cannot join them from vlans on Router A.

Hi @KGrev ,

Do you have a RPF from router A towards the source? Can you do a "show ip mroute" on router A to verify?

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Harold, thanks for hanging with me so long.

When I do a "show ip msdp sa-cache" on router A, I can see a group we made for 239.22.22.22 from a device off of router B.

When I type "show ip mroute 239.22.22.22" on router A, it says group not found.

When i type "show ip rpf 10.2.6.11"(device hosting on router B)

   RPF information for Net-Admin-PC216 (10.2.6.11)

   RPF interface: Port-channel50

   RPF Neighbor: ? (10.2.22.1)

  RPF route/mask: 10.2.0.0/16

RPF type: unicast (static)

Doing distance-preferred lookups across tables

RPF topology: ipv4 multicast base, originated from ipv4 unicast base.

Hi @KGrev ,

What platforms are the RPs? Can you share the multicast configuration for router A and B?

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

cisco_forums2.jpg

Harold,

I hope this is helpful. Sorry I am unable to send a full config file. Tried to include the details you would need.

Hi @KGrev ,

What do you see on Router A after the source becomes active?

show ip msdp sa-cache

show ip mroute 232.22.22.22 10.2.x.x

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

@Harold Ritter 

Router_A_CSCO9500#show ip msdp sa-cache
MSDP Source-Active Cache - 2 entries
(10.2.X.X, 239.4.4.4), RP 10.2.A.B, AS ?,23:49:30/00:05:03, Peer 10.2.A.B
(10.2.X.X, 239.22.22.22), RP 10.2.A.B, AS ?,23:49:30/00:05:03, Peer 10.2.A.B
Router_A_CSCO9500#show ip mroute 239.22.22.22 10.2.X.X
Group 239.22.22.22 not found
Router_A_CSCO9500#show ip mroute 239.22.22.22
Group 239.22.22.22 not found
Router_A_CSCO9500#

Hi @KGrev ,

> Router_A_CSCO9500#show ip mroute 239.22.22.22
> Group 239.22.22.22 not found
It looks like there is no active receiver with router A as their RP. Can you make sure there is an active receiver and test again.

Regards,

 

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

 

@Harold Ritter 

We have a PC connected to vlan 214 trying to pull a video feed from this group. The same pc is able to pull video feeds from other groups but not from Router B. There only way the group shows as mroute is when I apply a static join group to the vlan.

interface Vlan214
ip address 10.224.G.G 255.255.255.0
no ip redirects
no ip proxy-arp
ip mtu 1500
ip pim neighbor-filter PIM_NEIGHBORS
ip pim sparse-mode
ip igmp access-group IGMP_JOIN_FILTER
end

Extended IP access list PIM_REGISTER_FILTER
10 deny ip any host 239.6.6.6
15 permit ip any any (246 matches)
20 deny ip any any log-input (255 matches)

Extended IP access list IGMP_JOIN_FILTER
10 deny ip any host 239.6.6.6 log-input
20 permit ip any any (5819475 matches)

B1560-38A-CSCO9500#conf t
B1560-38A-CSCO9500(config)#int vlan 214
B1560-38A-CSCO9500(config-if)#ip igmp join-group 239.22.22.22

B1560-38A-CSCO9500#show ip mroute 239.22.22.22

IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group, c - PFP-SA cache created entry,
* - determined by Assert, # - iif-starg configured on rpf intf,
e - encap-helper tunnel flag, l - LISP Decap Refcnt Contributor
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.22.22.22), 00:00:10/00:02:49, RP 10.224.A.B, flags: BCL
Bidir-Upstream: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan214, Forward/Sparse, 00:00:10/00:02:49

 

 

 

@KGrev ,

Can you remove the "ip igmp join-group 239.22.22.22"  from vlan 214 and do a "sh ip igmp group".

Also, do you really need the local RP (10.224.A.B) to be configured as pim bidir? 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

@Harold Ritter 

I removed the join group after the test.

 

B1560-38A-CSCO9500#show ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.255.255.254 Vlan219 17w4d 00:02:15 10.224.219.32 Ac
239.255.255.250 Vlan234 5w1d 00:02:48 10.224.234.12 Ac
239.255.255.250 Vlan222 7w2d 00:02:09 10.224.222.52 Ac
239.255.255.250 Vlan193 12w0d 00:02:59 10.224.193.250 Ac
239.255.255.250 Vlan192 12w0d 00:02:57 10.224.192.250 Ac
239.255.255.250 Vlan195 17w4d 00:02:42 10.224.195.10 Ac
239.255.255.250 Vlan214 47w1d 00:02:38 10.224.214.101 Ac
239.255.255.250 Vlan194 49w0d 00:02:05 10.224.194.227 Ac
239.255.255.250 Vlan230 49w0d 00:02:57 10.224.230.45 Ac
239.255.255.250 Vlan219 49w0d 00:02:18 10.224.219.250 Ac
239.202.0.2 Vlan194 03:12:40 00:02:05 10.224.194.224 Ac
239.202.0.2 Vlan214 5d02h 00:02:42 10.224.214.178 Ac
239.202.0.2 Vlan218 1w6d 00:02:36 10.224.218.170 Ac
239.202.0.1 Vlan194 03:12:40 00:02:06 10.224.194.224 Ac
239.202.0.1 Vlan214 5d02h 00:02:38 10.224.214.57 Ac
239.202.0.1 Vlan218 17w4d 00:02:42 10.224.218.171 Ac
239.210.21.104 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.210.21.109 Port-channel51 7w2d 00:01:59 10.2.H.H Ac
239.210.21.111 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.254.21.102 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.140.21.102 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.140.21.101 Vlan214 2d03h 00:02:41 10.224.214.178 Ac
239.140.21.101 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.130.21.101 Port-channel51 7w2d 00:02:03 10.2.H.H Ac
239.130.21.102 Port-channel51 7w2d 00:02:03 10.2.H.H Ac
239.50.21.207 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.10.21.40 Port-channel51 7w2d 00:02:02 10.2.H.H Ac
239.10.21.41 Port-channel51 7w2d 00:02:00 10.2.H.H Ac
239.10.21.42 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.10.21.43 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.10.21.44 Port-channel51 7w2d 00:01:56 10.2.H.H Ac
239.10.21.45 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.10.21.46 Port-channel51 7w2d 00:01:54 10.2.H.H Ac
239.10.21.47 Port-channel51 7w2d 00:01:58 10.2.H.H Ac
239.10.21.35 Vlan194 00:22:00 00:02:09 10.224.194.227 Ac
239.10.21.35 Vlan214 1w3d 00:02:44 10.224.214.57 Ac
239.10.21.35 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.10.21.36 Port-channel51 7w2d 00:01:58 10.2.H.H Ac
239.10.21.37 Vlan214 1w3d 00:02:46 10.224.214.178 Ac
239.10.21.37 Port-channel51 7w2d 00:02:03 10.2.H.H Ac
239.10.21.38 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.10.21.39 Port-channel51 7w2d 00:02:03 10.2.H.H Ac
239.10.21.57 Port-channel51 7w2d 00:02:00 10.2.H.H Ac
239.10.21.56 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.10.21.59 Port-channel51 7w2d 00:01:55 10.2.H.H Ac
239.10.21.58 Port-channel51 7w2d 00:01:58 10.2.H.H Ac
239.10.21.61 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.10.21.60 Port-channel51 7w2d 00:02:54 10.2.H.H Ac
239.10.21.63 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.10.21.62 Port-channel51 7w2d 00:02:54 10.2.H.H Ac
239.10.21.49 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.10.21.48 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.10.21.51 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.10.21.50 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.10.21.53 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.10.21.52 Port-channel51 7w2d 00:02:03 10.2.H.H Ac
239.10.21.55 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.10.21.54 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.110.21.102 Port-channel51 7w2d 00:01:59 10.2.H.H Ac
239.120.21.101 Port-channel51 7w2d 00:01:57 10.2.H.H Ac
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.120.21.102 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.90.21.48 Port-channel51 7w2d 00:02:54 10.2.H.H Ac
239.90.21.49 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.90.21.45 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.90.21.44 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.90.21.47 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.90.21.46 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.90.21.41 Port-channel51 7w2d 00:02:02 10.2.H.H Ac
239.90.21.40 Port-channel51 7w2d 00:01:59 10.2.H.H Ac
239.90.21.43 Port-channel51 7w2d 00:02:02 10.2.H.H Ac
239.90.21.42 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.90.21.37 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.90.21.36 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.90.21.39 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.90.21.38 Port-channel51 7w2d 00:01:56 10.2.H.H Ac
239.90.21.33 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.90.21.32 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.90.21.35 Port-channel51 7w2d 00:02:01 10.2.H.H Ac
239.90.21.34 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.10.21.78 Port-channel51 7w2d 00:01:59 10.2.H.H Ac
239.10.21.79 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.10.21.76 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.10.21.77 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.10.21.74 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.40.21.104 Port-channel51 7w2d 00:02:02 10.2.H.H Ac
239.10.21.75 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.10.21.72 Port-channel51 7w2d 00:01:56 10.2.H.H Ac
239.10.21.73 Port-channel51 7w2d 00:01:58 10.2.H.H Ac
239.10.21.70 Port-channel51 7w2d 00:01:57 10.2.H.H Ac
239.40.21.101 Vlan194 01:09:29 00:02:13 10.224.194.227 Ac
239.10.21.71 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.40.21.101 Port-channel51 7w2d 00:01:57 10.2.H.H Ac
239.10.21.68 Port-channel51 7w2d 00:02:01 10.2.H.H Ac
239.40.21.102 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.10.21.69 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.40.21.103 Port-channel51 7w2d 00:02:55 10.2.H.H Ac
239.10.21.66 Port-channel51 7w2d 00:01:54 10.2.H.H Ac
239.10.21.67 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.10.21.64 Port-channel51 7w2d 00:02:58 10.2.H.H Ac
239.10.21.65 Port-channel51 7w2d 00:02:57 10.2.H.H Ac
239.10.21.93 Port-channel51 7w2d 00:02:59 10.2.H.H Ac
239.10.21.82 Port-channel51 7w2d 00:02:03 10.2.H.H Ac
239.10.21.81 Port-channel51 7w2d 00:02:56 10.2.H.H Ac
239.10.21.80 Port-channel51 7w2d 00:01:58 10.2.H.H Ac
239.22.22.22 Vlan214 00:38:38 00:02:40 10.224.214.132 Ac
232.44.44.233 Vlan234 5w1d 00:02:45 10.224.234.12 Ac
224.0.1.17 Vlan218 2w5d 00:02:45 10.224.218.17 Ac
224.0.1.16 Vlan218 2d04h 00:02:38 10.224.218.16 Ac
224.0.1.19 Vlan218 2w5d 00:02:36 10.224.218.19 Ac
224.0.1.21 Vlan218 2w5d 00:02:43 10.224.218.21 Ac
224.0.1.20 Vlan218 2w5d 00:02:40 10.224.218.20 Ac
224.0.1.23 Vlan218 2w5d 00:02:39 10.224.218.25 Ac
224.0.1.22 Vlan218 2w5d 00:02:45 10.224.218.22 Ac
224.0.1.24 Vlan218 2w5d 00:02:40 10.224.218.24 Ac
224.0.1.12 Vlan218 2w5d 00:02:42 10.224.218.12 Ac
224.0.1.13 Vlan218 2w5d 00:02:37 10.224.218.13 Ac
224.0.1.14 Vlan218 4d02h 00:02:36 10.224.218.14 Ac
224.0.1.15 Vlan218 2w5d 00:02:42 10.224.218.15 Ac
224.0.1.52 Vlan218 2w5d 00:02:42 10.224.218.52 Ac
224.0.1.60 Vlan230 49w0d 00:02:57 10.224.230.40 Ac
224.0.1.40 Loopback0 49w0d 00:02:18 10.224.236.1
225.0.0.73 Vlan2004 2w5d 00:02:20 10.2.17.0 Ac
B1560-38A-CSCO9500#

 

About the pim bidir. Maybe you could advise us on that as well. Router A also connects to Router C. Router C is hosting groups that Router A needed to share also. At the time we configured that, we did not know about "MSDP", some helpful Cisco forum members helped us get that working in this way. I believe it was because we only wanted to share a small list of groups referenced by an acl filter. But im not an expert lol.

Getting Started

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:

Recognize Your Peers