Verifying Ip Connectivity Within The Red Ipvpns - Avaya 8600 Technical Configuration Manual

10.2.41.0 255.255.255.0
10.2.50.0 255.255.255.0
10.2.51.0 255.255.255.0
11 out of 11 Total Num of Route Entries, 13 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:
Just as described in the Comments of section 3.8 step 1 for the Green VRF, the BGP VPNv4 routes have
been installed in the Red VRF with the V flag set.
When looking at the VRF IP routing table at a Cluster Site1 (or Site2) there is one notable difference (and
this applies to both the Green VRF and the Red VRF; simply that we looked at Site3 for the Green VRF in
section 3.8 and we are now looking at Site1 for the Red VRF).
In the BGP routing table (section 3.10 step 2), this time we have only 1 default route (from Site2) but not
from Site1. Yet Site1 is advertising a default route for it's Internet VRF. The reason why this default route
does not appear in the BGP routing table is because Site1 cannot have a peering to itself.
Yet this route still needs to be leaked from the Internet VRF on Site1 to the Red VRF on Site1 and this is
automatically accomplished by an intra-VRF redistribution which is automatically handled by the system,
based on the export and import RTs configured on the local VRFs.
The Preference value (PRF) for intra-VRF routes is 150. The Preference value for IBGP routes is 175.
Therefore the intra-VRF default route local to Site1 is preferred (and therefore installed in the Red VRF IP
routing table) over the default route from the Red BGP routing table.
Also note that the installed default route has NH-VRF = internet and Next Hop address = the IP interface
of FW1.
Therefore, Internet bound traffic from the Red VRF at Site1 will always use FW1 over VLAN3991. If FW1,
or the interface/link to it, fails, the Next Hop for the default route will immediately change to FW2 over
VLAN3992 and Internet bound traffic from Site1 will now be directly switched to FW2.

3.12 Verifying IP connectivity within the Red IPVPNs

Step 1 – Verify that each Site can reach each other Site
CLI/ACLI:
Site1:5# ping 10.2.20.1 vrf red source 10.2.10.1
Site1:5# ping 10.2.30.1 vrf red source 10.2.10.1
Site1:5# ping 10.2.40.1 vrf red source 10.2.10.1
Site1:5# ping 10.2.50.1 vrf red source 10.2.10.1
Result:
10.2.20.1 is alive
10.2.30.1 is alive
10.2.40.1 is alive
Network Design Implementation to Provide L2 & L3 VPN Connectivity
November 2010
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
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
118