Solution, An mvrf cannot be created, Symptom – H3C Technologies H3C S12500 Series Switches User Manual

Page 299: Analysis

Advertising
background image

283

configured for a VPN instance on different PE devices, a share-MDT cannot be established for that

VPN instance on different PE devices.

The same PIM mode must run on all the interfaces of the same VPN instance on different PE devices
and on all the interfaces of the P router. Otherwise, a share-MDT cannot be correctly built for the

VPN instance and PIM adjacencies cannot be established between the VPN instance on the local

PE device and the same VPN instance on the remote PE device.

BGP and unicast route configurations are prerequisites for the MTI interface to obtain an IP address
automatically, and PIM is enabled on at least one interface of the VPN instance so that PIM can be

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.

Check the share-group address: 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.

Check the running PIM mode: 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.

Check unicast routes. 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.

Check BGP peer configuration: 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, check whether 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,
check whether a unicast route exists to the RP. Use the display pim neighbor command to check

whether 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.

Advertising