Symptom
MSR Unicast-To-Multicast
Multicast Service Reflection for Unicast-To-Multicast conversion does not work when the destination IP to be translated in the configuration is a subset of the IP subnet on the corresponding Vif interface and the translated source IP falls into the same subset. The IP packets will be dropped and the multicast route for (S, G) will not be generated.
For example, with the following configuration
interface Vif1
ip address 10.1.1.1 255.255.255.0
ip service reflect gi0/0/0 destination 10.1.1.0 to 239.1.1.0 mask-len 28 source 10.1.1.2
end
IP packets from Gi0/0/0 whose destination reside in 10.1.1.0/28 will be dropped with drop cause Ipv4mcRpfFailed.
Conditions
IOS-XE 17.9.1.a
MSR Unicast-To-Multicast
When the destination IP to be translated in the configuration is a subset of the IP subnet on the corresponding Vif interface and the translated source IP falls into the same subset. For example:
interface Vif1
ip address 10.76.254.1 255.255.255.0
ip service reflect GigabitEthernet0/0/1.130 destination 10.76.254.10 to 239.76.1.10 mask-len 32 source 10.76.254.10
end
Workaround
Please follow these configuration guides for unicast-to-multicast Service Reflection
1. Do not pick subset addresses on the Vif interface to get translated.
For example, the destination addresses 10.1.2.0/24 to be translated don't fall into subset of 10.1.1.0/24
interface Vif1
ip address 10.1.1.1 255.255.255.0
ip service reflect destination 10.1.2.0 to 239.1.1.0 mask-len 24 source 10.1.1.2
end
2. If the destination addresses have to be in the subset on the Vif interface, pick source address out of the same subset.
For example, the destination addresses 10.1.1.0/28 to be translated do fall into subset of 10.1.1.0/24, but the source address 10.1.1.16 doesn't.
interface Vif1
ip address 10.1.1.1 255.255.255.0
ip service reflect destination 10.1.1.0 to 239.1.1.0 mask-len 28 source 10.1.1.16
end
Further Problem Description
