Verifying The Green Vrf Ip Routing Table - Avaya 8600 Technical Configuration Manual

3.8 Verifying the Green VRF IP routing table

In the previous section we have seen how BGP selects VPNv4 routes to accept into the Green VRF BGP
table space. The next step is to populate the IP routing table for the VRF.
Step 1 – Verify the Green VRF IP routing table
CLI: Site3:5# show ip route info vrf green
ACLI: Site3:5# show ip route vrf green
Result:
================================================================================
================================================================================
DST MASK
--------------------------------------------------------------------------------
0.0.0.0 0.0.0.0
10.1.10.0 255.255.255.0
10.1.11.0 255.255.255.0
10.1.20.0 255.255.255.0
10.1.21.0 255.255.255.0
10.1.30.0 255.255.255.0
10.1.31.0 255.255.255.0
10.1.40.0 255.255.255.0
10.1.41.0 255.255.255.0
10.1.50.0 255.255.255.0
10.1.51.0 255.255.255.0
11 out of 11 Total Num of Route Entries, 14 Total Num of Dest Networks displayed.
--------------------------------------------------------------------------------
TYPE Legend:
I=Indirect Route, D=Direct Route, A=Alternative Route, B=Best Route, E=Ecmp Route,
U=Unresolved Route, N=Not in HW, F=Replaced by FTN,
PROTOCOL Legend:
v=Inter-VRF route redistributed
Comments:
The BGP VPNv4 routes have been installed in the Green VRF with the V flag set.
Note that the Next Hop address in the VRF IP routing table is different from the Next Hop address in the
VRF BGP routing table in section 3.7 step 2. The Next Hop address in the BGP routing table is in fact the
IP encapsulation address to use to encapsulate packets within the IPVPN. The Next Hop address in the
VRF IP routing table is therefore derived by performing a lookup for the BGP Next Hop address inside the
GRT IP Routing table.
Hence, for Site3, the BGP Next Hop address for network 10.1.10.0/24 was 172.16.1.1 (see Section 3.7,
Step2). The Next Hop to reach 172.16.1.1 in the GRT IP routing table is the Next Hop corresponding to
IP route 172.16.1.0/24 i.e. 10.0.99.1 (see Section 3.3, Step4, Result for Site3). Hence this also becomes
the Next Hop for network 10.1.10.0/24 in the Green VRF IP routing table and the NH VRF is set to Glob~
= GRT.
In the BGP routing table we also had two separate default routes (one from Site1 and one from Site2) yet
the Next Hop for both those routes was identical. Therefore only a single default route is installed in the
Green VRF. The next hop for the default route is again based on a lookup for the BGP Next Hop
(172.16.0.1) in the GRT IP routing table. Since that is the CLIP#3 address which exists on both Site1 and
Site2, OSPF will have selected one or the other. In this case Site2 was selected and so the Next Hop for
Network Design Implementation to Provide L2 & L3 VPN Connectivity
November 2010
IP Route - VRF green
NEXT
10.0.99.2
10.0.99.1
10.0.99.1
10.0.99.2
10.0.99.2
10.1.30.1
10.1.31.1
10.0.99.4
10.0.99.4
10.0.99.5
10.0.99.5
between Sites using SMLT and IPVPN-Lite for ERS 8600
Technical Configuration Guide
NH INTER
VRF COST FACE PROT AGE TYPE PRF
Glob~ 0 3999 BGP 0
Glob~ 0 3999 BGP 0
Glob~ 0 3999 BGP 0
Glob~ 0 3999 BGP 0
Glob~ 0 3999 BGP 0
- 1 130 LOC 0
- 1 131 LOC 0
Glob~ 0 3999 BGP 0
Glob~ 0 3999 BGP 0
Glob~ 0 3999 BGP 0
Glob~ 0 3999 BGP 0
V=IPVPN Route
avaya.com
IBV 175
IBV 175
IBV 175
IBV 175
IBV 175
DB 0
DB 0
IBV 175
IBV 175
IBV 175
IBV 175
113