Avaya 8600 Technical Configuration Manual page 112

Ethernet routing switch
Hide thumbs Also See for 8600:
Table of Contents

Advertisement

Svc Label: 524289
RD -Type: IPADDR
RT -Type: ASNUM
Type: ASNUM
10.1.50.0/24
Svc Label: 524289
RD -Type: IPADDR
RT -Type: ASNUM
Type: ASNUM
10.1.51.0/24
Svc Label: 524289
RD -Type: IPADDR
RT -Type: ASNUM
Type: ASNUM
Comments:
Note that the Green VRF on Site3 has accepted all the VPNv4 Routes originating from every other Green
VRF (10.1.x.x) from the other 4 Sites. These Routes were accepted with RT 65000:60010.
Note also that two default routes are accepted from the Internet VRF on both Site1 and Site2. These
Routes were accepted with RT 65000:60000
Option
PEER REM ADDR
NEXTHOP ADDRESS
ORG
LOC PREF
SVC LABEL
Network Design Implementation to Provide L2 & L3 VPN Connectivity
November 2010
Value: 172.16.4.1:1
Value: 65000:60010
Value: 65000:60001
10.0.0.5
172.16.5.1
Value: 172.16.5.1:1
Value: 65000:60010
Value: 65000:60001
10.0.0.5
172.16.5.1
Value: 172.16.5.1:1
Value: 65000:60010
Value: 65000:60001
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).
Hence, with IPVPN-Lite, this constitutes the other purpose of the RD.
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
between Sites using SMLT and IPVPN-Lite for ERS 8600
Technical Configuration Guide
INC 100
524289
INC 100
524289
avaya.com
112

Advertisement

Table of Contents
loading

Table of Contents