Troubleshooting Md Vpn; A Default-Mdt Cannot Be Established - HP MSR1002-4 Configuration Manual

Flexnetwork msr series
Hide thumbs Also See for MSR1002-4:
Table of Contents

Advertisement

232.1.1.1
232.3.3.3
# Display information about the remote default-group for IPv4 multicast transmission in each VPN
instance on PE 1.
[PE1] display multicast-domain default-group remote
MD remote default-group information:
Group address
232.1.1.1
232.3.3.3
# Display information about the local default-group for IPv4 multicast transmission in each VPN
instance on PE 4.
[PE4] display multicast-domain default-group local
MD local default-group information:
Group address
232.1.1.1
233.3.3.3
# Display information about the remote default-group for IPv4 multicast transmission in each VPN
instance on PE 4.
[PE4] display multicast-domain default-group remote
MD remote default-group information:
Group address
232.1.1.1
232.3.3.3

Troubleshooting MD VPN

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

A default-MDT cannot be established

Symptom
The default-MDT cannot be established. PIM neighboring relationship cannot be established
between PE devices' interfaces that are in the same VPN instance.
Solution
To resolve the problem:
1.
Use the display interface command to examine the MTI interface state and address
encapsulation on the MTI.
2.
Use the display multicast-domain default-group command to verify that the same
default-group address has been configured for the same VPN instance on different PE devices.
3.
Use the display pim interface command to verify the following:
PIM is enabled on a minimum of one interface of the same VPN on different PE devices.
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.
4.
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.
5.
Use the display bgp peer command to verify that the BGP peer connections have been
correctly configured.
1.1.1.1
MTunnel0
1.1.1.1
MTunnel1
Source address
Next hop
4.4.4.4
2.2.2.2
4.4.4.4
2.2.2.2
Source address
Interface
4.4.4.4
MTunnel0
4.4.4.4
MTunnel1
Source address
Next hop
1.1.1.1
3.3.3.3
1.1.1.1
3.3.3.3
a
b
VPN instance
a
b
VPN instance
a
b
VPN instance
a
b
255

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents