|
Question : Multicast Routing - Invalid Source Address? 239.1.1.1
|
|
I am building an exact replica (with newer IOS) of an existing router to deploy at a site for troubleshooting purposes. There is static on the line when calling from inside to the outside world. The phone company demands we replace our hardware before they send anybody to do extensive testing on each PRI.
Anyways, here's my problem. The existing 1760 has a command line "ip mroute 239.1.1.1 255.255.255.255 172.30.251.1" to establish a static multicast route for our overhead paging. However, when I put that command into my new router, I get "invalid source address" referring to the 239.1.1.1. I cannot find any way for the router to take this command. My boss and I think it might be because this router isn't live on the network yet and the router won't take the static route because it can't negotiate the route. Is that likely? Or could it be something else....
For reference, the only other place the 239.1.1.1 shows up in the config is here:
interface FastEthernet0/0.4 encapsulation dot1Q 4 ip address 172.20.4.1 255.255.255.0 ip pim sparse-dense-mode ip igmp join-group 239.1.1.1 ip igmp join-group 239.1.1.2 ip cgmp service-policy output l3tol2mark
Any ideas?
|
Answer : Multicast Routing - Invalid Source Address? 239.1.1.1
|
|
the MROUTE assumes directly connected interface to find the source address the problem you are having is in relation to the RPF (reverse path forwarding) which means that your router before it will forward multicast needs to be able to reach your source of the multicast stream.
Thanks scott
|
|
|