Avaya 8600 Technical Manual page 41

TYPE Legend:
I=Indirect Route, D=Direct Route, A=Alternative Route, B=Best Route, E=Ecmp Rout
e,
U=Unresolved Route, N=Not in HW, F=Replaced by FTN,
PROTOCOL Legend:
v=Inter-VRF route redistributed
On each ERS8600 in the switch cluster verify the following information:
Option Verify
NH VRF All local routes learned, in this case by 8600-2, via the locally attached CE router with
display a ―NH VRF‖ value of blue via VLAN 3000 using a protocol of OSPF. All external
INTERFACE
routes from ERS8600-1 and ERS8600-3 are learned via BGP via VLAN 1010.
PROT
For all external routes learned, the Type will be displayed with ―V‖ to indicate an IP-VPN
TYPE
route.
If the VRF routes are not showing up or missing: a) ensure that the IGP protocol (OSPF
in this example) is up and operation and peered with each neighbor, b) ensure that LDP
is operational, c) ensure that you have PE-PE connectivity by performing an ‗mplsping'
to the remote PE CLIP address and d) ensure that you ping the VRF interfaces.
For example, in reference to ERS8600-2, ensure that it can ping PE routers 8600-1 and
8600-3 as follows using CLIP addresses:

ERS8600-2:5# ping 10.91.1.1 source ipvpn (NNCLI: ping-mpls
ipv4 10.92.1.1/32)
10.91.1.1 is alive


ERS8600-2:5# ping 10.93.1.1 source ipvpn
10.93.1.1 is alive
In reference to ERS8600-2, for the blue VRF, ensure that it can ping the VRF interfaces
from 8600-2 and 8600-3:

ERS8600-1:5# ping 10.91.10.1 vrf blue source 10.92.10.1
10.91.10.1 is alive

ERS8600-2:5# ping 10.93.10.1 vrf blue source 10.92.10.1
10.93.10.1 is alive

Please note that you must specify a source address when attempting to ping a VRF
address
July 2010
IV-VPN (MPLS) for ERS 8600 Technical Configuration Guide
V=IPVPN Route
avaya.com
41