EasyManua.ls Logo

Cisco SCE2020-4XGBE-SM - Limitations

Cisco SCE2020-4XGBE-SM
512 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
13-10
Cisco SCE 2000 and SCE 1000 Software Configuration Guide
OL-7827-12
Chapter 13 MPLS/VPN Support
Service Control MPLS/VPN Requirements
Limitations
Mutually exclusive system modes
When the system works in MPLS/VPN mode, the following modes are not supported:
The following tunneling modes:
MPLS traffic engineering skip
MPLS VPN skip
L2TP skip
VLAN symmetric classify
TCP Bypass-establishment
DDoS
Value Added Services (VAS) mode
Number of MPLS labels
The choice of the unique VPN site must be based on the BGP label only. The BGP label must be the
innermost label.
The MPLS/VPN solution supports various combinations of labels. See Additional MPLS Pattern
Support.
The system does not support VPNs for which other MPLS-related features, such as MPLS-TE or
MPLS-FRR, are enabled.
Subscriber-related limitations
The following subscriber-related limitations exist in the current solution:
The SM must be configured to operate in Push mode.
VLAN-based subscribers cannot be used.
Introduced subscriber aging is not supported when using VPN-based subscribers.
Maximum number of VPN-based mappings per single subscriber:
200 (standalone)
50 (cascade)
Topology-related limitations
An asymmetrical routing topology in which the traffic may be unidirectional, is not supported, since
the MPLS/VPN solution relies on the bidirectional nature of the traffic for various mechanisms.
TCP related requirements
Number of Upstream TCP Flows – There must be enough TCP flows opening from the subscriber
side on each PE-PE route in each period of time. The higher the rate of TCP flows from the
subscriber side, the higher the accuracy of the mechanism can be.

Table of Contents

Related product manuals