Ip Vpn Requirements And Recommendations - Avaya 8800 Planning And Engineering, Network Design

MPLS IP VPN and IP VPN Lite
RTs must be configured in such a way as to be unique for each IP VPN.
Since each VRF can be configured with any number of RTs (either as import, export or both) this
allows each VRF to be part of any number of overlapping IP VPNs. The use of RT can also be
exploited to achieve a number of different IP VPN topologies, from any-to-any (meshed) where all
VRFs in the same IP VPN have the same import and export RT, to hub and spoke topologies where
the hub nodes use one export RT (configured as import RT on spokes) and a different import RT
(configured as export RT on the spokes). Topologies with multiple hub sites can also be achieved.
Figure 120: IP VPN hub and spoke
In terms of configuration both the RD and the RT are configured with the same format and are
usually configured in the same VRF context on the PE device.
The route target frame format is identical to the route distinguisher as shown in
IPv4 Address on page 241.

IP VPN requirements and recommendations

To use IP VPN, you require R or RS modules, as well as the 8692 SF/CPU with SuperMezz or 8895
SF/CPU. You also require the appropriate license.
The Avaya Ethernet Routing Switch 8800/8600 supports IP VPN over 802.3ad (MLT)
Partial-HA (P-HA) is supported by IP VPN. P-HA means that a module can be enabled and
configured when the system is running in the HA mode. The configuration database is synchronized
between the Master and Slave CPU, so that, on failover, the module starts with the same
configuration that the Master CPU executed. After failover, the Standby CPU (new Master) starts the
module with the synchronized configuration, and does not carry over the runtime state information
for the module from the previous Master CPU. If a module communicates with peers externally, the
session is reestablished. P-HA support allows modules to run in the HA mode. Although the module
is restarted with the most recent configuration, the failover time is improved compared to a single
SF/CPU restart in non-HA mode.
VPN tunnel dampening is not supported.
June 2016 Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
Figure 119: VPN-
242