Hitachi GR2000 Series - Manual (Page 250)

Hitachi Gigabit Router GR2000 Series Enhanced Version Operations - Device Management Overview
7-84 GR2K-GA-0015
Ver. 07-02
7.11.2.2 Check transfer state
Specify detailed parameters at intervals using the show mpls 12transport command,
and check to see if the input packets and output packets have increased in number.
When both the input packets and the output packets have increased in number:
Check to see if there is any part where the MPLS packets used in the
EoMPLS(L2-VPN) communication cannot be transferred, within the circuit of the
MPLS network which the VC passes through when communication cannot be
maintained. The circuit of the MPLS network to be used in EoMPLS(L2-VPN)
communication needs to be able to transfer a maximum of 1530 bytes of MPLS
packets, without fragmentation. If there is an environment in which 1530 bytes
of MPLS packets can be transferred without being fragmented, the
EoMPLS(L2-VPN) communication should be normal. If that is the case, the
problem seems to be a phenomenon specific to the sites that cannot
communicate. Check the operation of the two sites.
When the output packets have not increased in number:
The MPLS packets to be used in the EoMPLS(L2-VPN) communication have not
been received from the remote LSR. Check the state of the remote LSR.
When the input packets have not increased in number:
This unit is not receiving any frame from the access circuit. Check the state of
the hub, router and other elements connected to the access circuit.
7.11.3 There is no IP-VPN route information
If there is no VPN route information in the route information acquired by the unit,
isolate the cause by following the fault analysis method described below.
7.11.3.1 Communication with the remote site
*
Note: In EoMPLS(L2-VPN) communication, the IP address of the targeted LDP peer must be the
local address of the remote exit edge router. If the IP address of the targeted LDP peer is
the address of the interface of the remote exit router, actual L2-VPN communication
cannot be maintained, even if VC is established.
Table 7-34 Fault analysis method for VPN route
Item
No.
Confirmation contents and command Remedy
1 Check to see if the result of BGP
capability negotiation contains an
IPv4-VPN.
show ip bgp neighbor xx.xx.xx.xx
(Specify the address in xx.xx.xx.xx.) If there is an IPv4-VPN, go to item 2.
If there is no IPv4-VPN, correct the configuration definition
information.
2 Check vpnmap of the configuration
definition information to see if the
correspondence of the VPN information
is correct. If the configuration definition information is correct, go to item 3.
If the configuration definition information is not correct, correct the
configuration definition.