Lsp Ping Over Vpws And Vpls; Vpls Scalability And Performance Targets; Pseudowire Redundancy For P2P Atom Cross-Connects - Cisco CRS Configuration Manual
Ios xr virtual private network
Hide thumbs
Also See for CRS:
- Configuration manual (430 pages) ,
- User manual (304 pages) ,
- Command reference manual (155 pages)
Table of Contents
Advertisement
LSP Ping over VPWS and VPLS
LSP Ping over VPWS and VPLS
For Cisco IOS XR software, the existing support for the Label Switched Path (LSP) ping and traceroute
verification mechanisms for point-to-point pseudowires (signaled using LDP FEC128) is extended to cover
the pseudowires that are associated with the VFI (VPLS). Currently, the support for the LSP ping and traceroute
for LDP signalled FEC128 pseudowires is limited to manually configured VPLS pseudowires. In addition,
Cisco IOS XR software supports LSP ping for point-to-point single-segment pseudowires that are signalled
using LDP FEC129 AII-type 2 applicable to VPWS or signalled using LDP FEC129 AII-type 1 applicable
to VPLS. For information about Virtual Circuit Connection Verification (VCCV) support and the ping mpls
pseudowire command, see the Cisco IOS XR MPLS Command Reference for the Cisco CRS Router.
VPLS Scalability and Performance Targets
The Cisco CRS-1 router employs the ternary content addressable memory (TCAM) to meet the performance
and scalable targets over VPLS.
The following table below describes the scalability and performance targets for the Cisco CRS-1 router.
Table 2: VPLS Scalability and Performance Targets
Performance
Maximum bridge domains per Line Card
Maximum bridge domains per system
Maximum MACs per bridge domain
Maximum MACs per Line Card
Maximum MACs per system
Maximum attachment circuits per bridge domain
Maximum pseudowires per bridge domain
Maximum pseudowires per system
Pseudowire Redundancy for P2P AToM Cross-Connects
Backup pseudowires (PW) are associated with the corresponding primary pseudowires. A backup PW is not
programmed to forward data when inactive. It is activated only if a primary PW fails. This is known as
pseudowire redundancy. The primary reason for backing up a PW is to reduce traffic loss when a primary
PW fails. When the primary PW is active again, it resumes its activity.
A primary PW can be associated with only one backup PW. Similarly, a backup PW can be associated with
only one primary PW.
Cisco IOS XR Virtual Private Network Configuration Guide for the Cisco CRS Router, Release 6.1.x
68
Implementing Multipoint Layer 2 Services
Scalability Target
1024
1024
15999
65536
65536
4085
256
16340
Advertisement
Table of Contents
