EVC Maps
An EVC map classifies traffic ingressing a UNI into an EVC given configured match criteria. It
uniquely identifies a subscriber traffic flow within an EVC and provides the mechanism for
VLAN tag manipulation, Ingress Bandwidth Policing, forwarding, and queuing.
EVC Map Attributes
The attributes of a EVC Map are described in the following sections.
Destination EVC
This attribute defines the name of the EVC that the EVC map is fowarding traffic to and
receiving from. This attribute can also be used to discard traffic matched by the EVC map. An
EVC map is limited to a single EVC connection.
Name
This attribute is an arbitrary string that is used to identify the EVC map. The value must be
unique across all EVC maps defined in the network element and is intended for management
and control purposes. The value is not carried in any field in the Ethernet frame. As an
example, the service provider might use "SCPOP1‐Node3‐Slot2‐Port1" to signify port 1 in slot
2 of node 3 in Santa Clara POP1.
Configuration Status
This attribute indicates the current status of the EVC map. The EVC map can be administra‐
tively enabled, but it can not be in a functional state if it is not fully configured or if there is a
conflict. Table F‐6 lists the possible values.
Possible Value
Running
Missing Connection to EVC
EVC not running
Invalid UNI
Disabled
Duplicate EVC‐map
65K510DEP08-1A
Table F-6. EVC Map Status Values
Definition
Conditions are okay and the EVC map provisioning is applied.
The EVC map is not connected to an EVC or the EVC does not
exist.
The connected EVC is not in the "Running" state.
The EVC map is not connected to a UNI, the connected UNI does
not exist, or the EVC map is not available for Ethernet services.
The EVC map administrative state is disabled.
Another EVC map exists having a conflicting ingress criteria.
Refer to Rule 2 on page F‐2.
Appendix F, NetVanta Examples - EVC Maps
F-7