Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

multicast problem in Fram-relay

hub and spoke

r1

| |

r2 r3

the frame-relay interface of the three routers are in one subnet

frame-relay map with broadcast

pim dense-mode

r2's ethernet interface join one multicast group:239.1.1.1

r1 can ping this multicast address,but r3 can not.

what's the problem?

5 REPLIES
VIP Purple

Re: multicast problem in Fram-relay

Can you post the configs ?

New Member

Re: multicast problem in Fram-relay

r1(hub)

int s0

ip add 10.10.1.1 255.255.0.0

encapsulation fram-relay

ip pim dense-mode

r2(spoke)

int s0

ip add 10.10.1.2 255.255.0.0

ip pim dense-mode

encapsulation frame-relay

int e0

ip add 10.100.1.2 255.255.255.0

ip pim dense-mode

ip igmp join-group 239.1.1.1

r3(spoke)

int s0

ip add 10.10.1.3 255.255.0.0

encapsulation fram-relay

ip pim dense-mode

New Member

Re: multicast problem in Fram-relay

Since this is a hub and spoke you would have yo add the ip pim nbma-mode

New Member

Re: multicast problem in Fram-relay

it doesn't work

New Member

Re: multicast problem in Fram-relay

When a multicast packet arrives on r1, it creates (*,G) state containing all interfaces that possibliy need to forward traffic (PIM neighbours, IGMP groups). To actually forward traffic, (S,G) state is set up. The incoming interface is the one, where the packet is received from, the OIL contains the rest of the interfaces from (*,G).

Sinde the frame relay interface is the incoming interface, your packet is not forwarded out of this interface again and therefore does not get from r2 to r3.

NBMA mode does not help either, because it can only collect the additional information form SM joins

The most effective solution is to use subinterfaces.

95
Views
0
Helpful
5
Replies
CreatePlease to create content