An Mvrf Cannot Be Created - HP MSR ASM Configuration Manual

enabled on the MTI interface. PIM adjacencies can be established between the same VPN instance
on different PE devices only after the MTI interface obtains an IP address and gets PIM enabled.
Solution
1. Use the display multicast-domain vpn-instance share-group command to verify that the same
share-group address has been configured for the same VPN instance on different PE devices.
2. Use the display pim interface command to verify that PIM is enabled on at least one interface of the
same VPN on different PE devices and the same PIM mode is running on all the interfaces of the
same VPN instance on different PE devices and on all the interfaces of the P router.
3. Use the display ip routing-table command to verify that a unicast route exists from the VPN
instance on the local PE device to the same VPN instance on each remote PE device.
4. Use the display bgp peer command to verify that the BGP peer connections have been correctly
configured.

An MVRF cannot be created

Symptom
A VPN instance cannot create an MVRF correctly.
Analysis
If PIM-SM is running in the VPN instance, the BSR information for the VPN instance is required.
•
Otherwise, the VPN instance's MVRF cannot be correctly established.
If PIM-SM is running in the VPN instance, the RP information for the VPN instance is required. If a
•
unicast route to the RP is not available, this means that a PIM adjacency has not been correctly
established between the public network and the VPN instance, and thus VPN instance cannot
correctly establish its MVRF.
The customer DR must have a route to the VPN RP.
•
Solution
1. Use the display pim bsr-info command to verify that the BSR information exists on the public
network and VPN instance. If not, verify that a unicast route exists to the BSR.
2. Use the display pim rp-info command to view the RP information. If no RP information is available,
verify that a unicast route exists to the RP. Use the display pim neighbor command to verify that the
PIM adjacencies have correctly established on the public network and the VPN.
3. Use the ping command to check the connectivity between the VPN DR and the VPN RP.
267