Troubleshooting Md-Vpn - HP A8800 Configuration Manual

# Display the local share-group information of VPN instance a on PE 4.
<PE4> display multicast-domain vpn-instance a share-group local
MD local share-group information for VPN-Instance: a
Share-group: 239.1.1.1
MTunnel address: 1.1.1.4
# Display the local share-group information of VPN instance b on PE 4.
<PE4> display multicast-domain vpn-instance b share-group local
MD local share-group information for VPN-Instance: b
Share-group: 239.4.4.4
MTunnel address: 1.1.1.4

Troubleshooting MD-VPN

A share-MDT cannot be established
Symptom
A share-MDT cannot be established. PIM adjacencies cannot be established between the same VPN
instance's interfaces on different PE devices.
Analysis
On different PE devices, the same share-group must be configured for the same VPN instance. A
•
share-group address uniquely identifies a share-MDT. If different share-group addresses have been
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. 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.
285