Verifying the configuration, Troubleshooting md-vpn, A share-mdt cannot be established – H3C Technologies H3C S12500 Series Switches User Manual
Page 298: Symptom, Analysis
282
[CEb2] pim
[CEb2-pim] c-bsr loopback 1
[CEb2-pim] c-rp loopback 1
[CEb2-pim] quit
# Configure OSPF.
[CEb2] ospf 1
[CEb2-ospf-1] area 0.0.0.0
[CEb2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0
[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
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