Open as PDF
Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0
Chapter 3 Creating a FlexUNI/EVC Ethernet Policy
Overview of FlexUNI/EVC Support in ISC
Device Roles with FlexUNI/EVC
Presently, ISC has U-PE, PE-AGG and N-PE devices. The basic PE device role association of ISC
continues for FlexUNI/EVC policy and service requests. In this release of ISC, there are no changes
made to the PE role assignment. A device having FlexUNI/EVC capabilities will not call for a change
in the existing role assignment in ISC. However, FlexUNI/EVC capabilities in ISC are supported only
for interfaces on N-PE and not on PE-AGG or U-PE devices.
Note ISC does not support customer edge devices (CEs) for FlexUNI/EVC. If the access port contains any
DSLAMS, non-Cisco Ethernet devices and/or other Cisco devices that are not supported by ISC, such
nodes and beyond are not in the scope of ISC. In such cases, from the ISC perspective, the interface on
the first ISC-managed device is the UNI.
Topology Overview for FlexUNI/EVC
This section provides examples of various topologies supported with FlexUNI/EVC. As mentioned in
the note at the end of section
Device Roles with FlexUNI/EVC, page 3-5, ISC does not support customer
edge devices (CEs) with FlexUNI/EVC. References to the term “CE” in the following topology
variations (such as “CE directly connected” and so on) is only to indicate how the customer or third-party
devices connect to the N-PE. For all the cases involving FlexUNI/EVC, the CE is not supported in ISC.
Also, any provider device that is not supported by ISC, and which is used in the access circuit, marks the
boundary for the scope of ISC, beyond which no devices (that is, towards the CE, and including the
unsupported node) is managed by ISC.
CE Directly Connected and FlexUNI
With this combination, the UNI is the interface on a supported line card, with EVC capability configured.
ISC does not configure ISC’s standard UNI functionality (for example, port-security, storm control, and
Layer 2 Protocol Tunneling). This is because of lack of command support on the FlexUNI/EVC-capable
hardware. Operators can use templates to configure relevant platform supported parameters to realize
any of these features not provided by ISC. ISC configures only the service instance with VLAN
manipulations and pseudowire, VPLS, or local-connect on the UNI. NPCs are not needed while creating
such links because NPCs are only required when there are access nodes between the N-PE and CE. Other
intermediate Ethernet access nodes are not involved in this topology.
CE Directly Connected and No FlexUNI
This is similar to the UNI on N-PE case in ISC. The FlexUNI/EVC service request can be used to create
such links with older Cisco 7600 platforms (that is, N-PE interfaces without FlexUNI/EVC capability),
but with plans of adding one or more future links with EVC support. If not, one could use the existing
ERS/EWS/ERMS/EMS functionality in ISC. NPCs are not needed while creating such links because
NPCs are only required when there are access nodes between the N-PE and CE. Other intermediate
Ethernet access nodes are not involved in this topology.
CE Not Directly Connected and FlexUNI
This topology involves the following configurations:
• UNI on a U-PE or PE-AGG to which the CE is connected.