Troubleshooting Md-Vpn; A Share-Mdt Cannot Be Established - HP MSR ASM Configuration Manual

[CEb2-ospf-1-area-0.0.0.0] network 10.11.0.0 0.0.255.255
[CEb2-ospf-1-area-0.0.0.0] quit
[CEb2-ospf-1] quit
Verifying the configuration
# Display the local share-group information of VPN instance a on PE 1.
<PE1> 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.1
# Display the local share-group information of VPN instance b on PE 1.
<PE1> 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.1
# 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

This section describes common MD-VPN problems and how to troubleshoot them.

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
266