Troubleshooting Md-Vpn Configuration; Unable To Establish A Share-Mdt - 3Com MSR 50 Series Configuration Manual

1308 C 75: M
HAPTER ULTICAST
Troubleshooting
MD-VPN
Configuration
Unable to Establish a
Share-MDT
VPN C
ONFIGURATION
<PE1> display multicast-domain vpn-instance a share-group
MD local share-group information for VPN-Instance: a
Share-group: 239.1.1.1
MTunnel address: 1.1.1.1
# View the share-group information of VPN instance a on PE 2.
<PE2> display multicast-domain vpn-instance a share-group
MD local share-group information for VPN-Instance: a
Share-group: 239.1.1.1
MTunnel address: 1.1.1.2
# View the share-group information of VPN instance b on PE 2.
<PE2> display multicast-domain vpn-instance b share-group
MD local share-group information for VPN-Instance: b
Share-group: 239.2.2.2
MTunnel address: 1.1.1.2
# View the share-group information of VPN instance a on PE 3.
<PE3> display multicast-domain vpn-instance a share-group
MD local share-group information for VPN-Instance: a
Share-group: 239.1.1.1
MTunnel address: 1.1.1.3
# View the share-group information of VPN instance b on PE 3.
<PE3> display multicast-domain vpn-instance b share-group
MD local share-group information for VPN-Instance: b
Share-group: 239.2.2.2
MTunnel address: 1.1.1.3
Symptom
A share-MDT can be established. PIM adjacencies can 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
■
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.