8 confirmation of mpls communication [route-os7, 2 confirming ldp session state, 3 confirming the peering information of mp-bgp – Hitachi GR2000 Series User Manual

Page 145: 2 confirming ldp session state -45, 3 confirming the peering information of mp-bgp -45, Figure 5-83. display of ldp session state -45

Advertising
background image

Confirmation of interface state and routing state

GR2K-GA-0015

5-45

Ver. 07-02

5.8

Confirmation of MPLS Communication [ROUTE-OS7]

5.8.1

Confirming the IPv4 unicast routing information in an MPLS network.

Confirm the IPv4 unicast routing information in an MPLS network according to
Subsection 5.3.1, “Confirming the route to destination address”. In MPLS
communication, the route to the local address of remote LSR (the IP address of a
BGP peer or Targeted LDP peer) must exist. Confirm the route to an MPLS
communication peer and the route to the local address of remote LSR.

VPN communication can be performed when the route to remote LSR is a multipath.
However, IPv4 communication other than VPN is not used as MPLS communication.
It operates as a load balance during normal IPv4 communication.

5.8.2

Confirming LDP Session State

Execute a show mpls ldp command and confirm that the operational state of LDP
session is up.

The basic LDP session for which the output interface of the route to a destination
address is specified must be established when MPLS communication is performed.

The targeted LDP session to remote LSR must be established when EoMPLS (L2-VPN)
communication is performed. Also confirm that the peer address of the targeted LDP
session is the local address of a remote exit edge router.

Figure 5-83 Display of LDP session state

5.8.3

Confirming the peering information of mp-BGP

IPv4-VPN must be contained in the negotiation of a BGP capability parameter by the
BGP peering information to a remote edge router. Execute a show ip bgp neighbors
command according to Subsection 5.3.4, “Confirming the peering information of
BGP4
”. and confirm that IPv4-VPN is displayed in BGP capability negotiation. Also
confirm that the remote IP address is a local address.

The VPN route that is not mapped using VPN map information is not stored when
-keep-none-vpn is specified. When you want to relearn a VPN route because of the
addition of VPN configuration, disconnect the relevant peer once using a clear ip bgp
command or re-advertise a VPN route from the peer.

> show mpls ldp

total:3

Interface Name Local Remote Status Sent Received

T (localhost) 10.3.3.3 10.1.1.1 UP 5 10

toR2 172.16.1.1 172.16.1.2 UP 5 10

toR3 172.16.2.1 172.16.2.2 UP 11 11

Advertising