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

Option
PEER REM ADDR
NEXTHOP ADDRESS
ORG
LOC PREF
SVC LABEL

3.11 Verifying the Red VRF IP routing table

In the previous section we have seen how BGP selects VPNv4 routes to accept into the Red VRF BGP
table space. The next step is to populate the IP routing table for the VRF.
Again, for the Red VRF, we will be looking at the resulting VRF IP routing table on one of the Cluster
nodes (Site1).
Step 1 – Verify the Red VRF IP routing table
CLI: Site1:5# show ip route info vrf red
ACLI: Site1:5# show ip route vrf red
Result:
================================================================================
================================================================================
DST MASK
--------------------------------------------------------------------------------
0.0.0.0 0.0.0.0
10.2.10.0 255.255.255.0
10.2.11.0 255.255.255.0
10.2.20.0 255.255.255.0
10.2.21.0 255.255.255.0
10.2.30.0 255.255.255.0
10.2.31.0 255.255.255.0
10.2.40.0 255.255.255.0
Network Design Implementation to Provide L2 & L3 VPN Connectivity
November 2010
Verify
This is the BGP neighbor who advertised the VPNv4 Route.
With IPVPN-Lite, the next hop address for the VPN-v4 route is directly derived
from the IP address included in the RD of the VPN-v4 route itself. This IP
address constitutes the outer IP Destination address which will be used to
IPinIP encapsulate any IP packets which need to be delivered from the local
VRF to an IP destination which matches the VPNv4 IPv4 route. (The Source IP
address used in the outer IPinIP encapsulation is always the IP address
configured in the RD of the local ingress VRF).
Origin Type of the BGP Route. INC = Incomplete and is the correct Origin Type
for VPNv4 routes
BGP LocalPref for the VPNv4 Route. Setting the LocalPref can be used to
influence BGP Path selection when the same BGP route is learnt from different
peers. By default this is set to 100
This is an MPLS label. From a control plane perspective (BGP) there is no
difference between IPVPN-Lite and RFC4364 MPLS Based IPVPNs. Hence for
every VPNv4 route advertised by BGP a corresponding MPLS VPN-label is
associated with the VPNv4 route within the BGP Update. With IPVPN-Lite this
MPLS label is simply not used and can be ignored
IP Route - VRF red
NEXT
10.255.91.20
10.2.10.1
10.2.11.1
10.0.99.2
10.0.99.2
10.0.99.3
10.0.99.3
10.0.99.4
between Sites using SMLT and IPVPN-Lite for ERS 8600
Technical Configuration Guide
NH INTER
VRF COST FACE PROT AGE TYPE PRF
inte~ 1 3991 VRF 0
- 1 210 LOC 0
- 1 211 LOC 0
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
avaya.com
IB 150
DB 0
DB 0
IBV 175
IBV 175
IBV 175
IBV 175
IBV 175
117