Reference record for OID 1.3.6.1.4.1.9.9.613

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
613
Node name
ciscoEvcMIB
Numeric OID
1.3.6.1.4.1.9.9.613
URN notation
urn:oid:1.3.6.1.4.1.9.9.613
Type
OBJECT IDENTIFIER
ASN.1 notation

{1 3 6 1 4 1 9 9 613}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoEvcMIB(613)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/9/613
  • /ISO/Identified-Organization/6/1/4/1/9/9/613
  • /ISO/3/6/1/4/1/9/9/613
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoEvcMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoEvcMIB
  • /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoEvcMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoEvcMIB
  • Additional combinations skipped.

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: Circitor

Metro Ethernet services can support a wide range of
applications and subscriber needs easily, efficiently
and cost-effectively. Using standard Ethernet interfaces,
subscribers can set up secure, private Ethernet Virtual
Connections, to connect their sites together and connect
to business partners, suppliers and the Internet.

This MIB module defines the managed objects and notifications
describing Ethernet Virtual Connections.

Ethernet Virtual Connections (EVC), are defined by the Metro
Ethernet Forum (MEF), as an association between two or more
UNIs. Frames within an EVC can only be exchanged among the
associated UNIs. Frames sent into the MEN via a particular
UNI must not be delivered back to the UNI from which it
originated.

Along an EVC path, there are demarcation flow points on
associated ingress and egress interface, of every device,
through which the EVC passes. A service instance represents
these flow points where a service passes through an interface.

From an operational perspective, a service instance serves
three purposes:
1. Defines the instance of a particular EVC service on
a specific interface and identifies all frames that
belongs to that particular service/flow.
2. To provide the capability of applying the configured
features to those frames belonging to the service.
3. To optionally define how to forward those frames in
the data-path.

The association of a service instance to an EVC depicts
an instance of an Ethernet flow on a particular interface
for an end-to-end (UNI-to-UNI) Ethernet service for a
subscriber.

The following diagram illustrates the association of
EVC, UNIs and service instances. UNI physical ports
are depicted as 'U', and service instances as 'x'.

CE MEN MEN CE

| | | | () | | | |
| |
| | | | () | | | |

^ ^
| |


This MIB module addresses the functional areas of network
management for EVC, including:

The operational mode for interfaces that are providing
Ethernet service(s).

The service attributes regarding an interface behaving
as UNI, such as CE-VLAN mapping and layer 2 control
protocol (eg. stp, vtp, cdp) processing.

The provisioning of service instances to define flow
points for an Ethernet service.

The operational status of EVCs for notifications
of status changes, and EVC creation and deletion.

Definition of terms and acronyms:

B-Tag: Backbone Tag field in Ethernet 802.1ah frame

CE: Customer Edge

CE-VLAN: Customer Edge VLAN

CoS: Class Of Service

EVC: Ethernet Virtual Connection

I-SID: Service Instance Identifier field in Ethernet
802.1ah frame

MAC: Media Access Control

MEN: Metro Ethernet Network

NNI: Network to Network Interface

OAM: Operations Administration and Management

PPPoE: Point-to-Point Protocol over Ethernet

Service frame: An Ethernet frame transmitted across the
UNI toward the service provider or an Ethernet frame
transmitted across the UNI toward the Subscriber.

Service Instance: A flow point of an Ethernet service

Service provider: The organization providing Ethernet
service(s).

Subscriber: The organization purchasing and/or using
Ethernet service(s).

UNI: User Network Interface
The physical demarcation point between the
responsibility of the service provider and
the responsibility of the Subscriber.

UNI-C: User Network Interface, subscriber side

UNI-N: User Network Interface, service provider side

VLAN: Virtual Local Area Network

Parsed from file CISCO-EVC-MIB.mib
Module: CISCO-EVC-MIB

Alternative description: Cisco

Metro Ethernet services can support a wide range of
applications and subscriber needs easily, efficiently
and cost-effectively. Using standard Ethernet interfaces,
subscribers can set up secure, private Ethernet Virtual
Connections, to connect their sites together and connect
to business partners, suppliers and the Internet.

This MIB module defines the managed objects and notifications
describing Ethernet Virtual Connections.

Ethernet Virtual Connections (EVC), are defined by the Metro
Ethernet Forum (MEF), as an association between two or more
UNIs. Frames within an EVC can only be exchanged among the
associated UNIs. Frames sent into the MEN via a particular
UNI must not be delivered back to the UNI from which it
originated.

Along an EVC path, there are demarcation flow points on
associated ingress and egress interface, of every device,
through which the EVC passes. A service instance represents
these flow points where a service passes through an interface.

From an operational perspective, a service instance serves
three purposes:
1. Defines the instance of a particular EVC service on
a specific interface and identifies all frames that
belongs to that particular service/flow.
2. To provide the capability of applying the configured
features to those frames belonging to the service.
3. To optionally define how to forward those frames in
the data-path.

The association of a service instance to an EVC depicts
an instance of an Ethernet flow on a particular interface
for an end-to-end (UNI-to-UNI) Ethernet service for a
subscriber.

The following diagram illustrates the association of
EVC, UNIs and service instances. UNI physical ports
are depicted as 'U', and service instances as 'x'.

CE MEN MEN CE

| | | | () | | | |
| |
| | | | () | | | |

^ ^
| |


This MIB module addresses the functional areas of network
management for EVC, including:

The operational mode for interfaces that are providing
Ethernet service(s).

The service attributes regarding an interface behaving
as UNI, such as CE-VLAN mapping and layer 2 control
protocol (eg. stp, vtp, cdp) processing.

The provisioning of service instances to define flow
points for an Ethernet service.

The operational status of EVCs for notifications
of status changes, and EVC creation and deletion.

Definition of terms and acronyms:

B-Tag: Backbone Tag field in Ethernet 802.1ah frame

CE: Customer Edge

CE-VLAN: Customer Edge VLAN

CoS: Class Of Service

EVC: Ethernet Virtual Connection

I-SID: Service Instance Identifier field in Ethernet
802.1ah frame

MAC: Media Access Control

MEN: Metro Ethernet Network

NNI: Network to Network Interface

OAM: Operations Administration and Management

PPPoE: Point-to-Point Protocol over Ethernet

Service frame: An Ethernet frame transmitted across the
UNI toward the service provider or an Ethernet frame
transmitted across the UNI toward the Subscriber.

Service Instance: A flow point of an Ethernet service

Service provider: The organization providing Ethernet
service(s).

Subscriber: The organization purchasing and/or using
Ethernet service(s).

UNI: User Network Interface
The physical demarcation point between the
responsibility of the service provider and
the responsibility of the Subscriber.

UNI-C: User Network Interface, subscriber side

UNI-N: User Network Interface, service provider side

VLAN: Virtual Local Area Network

Alternative description: MIBdepot

Metro Ethernet services can support a wide range of
applications and subscriber needs easily, efficiently
and cost-effectively. Using standard Ethernet interfaces,
subscribers can set up secure, private Ethernet Virtual
Connections, to connect their sites together and connect
to business partners, suppliers and the Internet.

This MIB module defines the managed objects and notifications
describing Ethernet Virtual Connections.

Ethernet Virtual Connections (EVC), are defined by the Metro
Ethernet Forum (MEF), as an association between two or more
UNIs. Frames within an EVC can only be exchanged among the
associated UNIs. Frames sent into the MEN via a particular
UNI must not be delivered back to the UNI from which it
originated.

Along an EVC path, there are demarcation flow points on
associated ingress and egress interface, of every device,
through which the EVC passes. A service instance represents
these flow points where a service passes through an interface.

From an operational perspective, a service instance serves
three purposes:
1. Defines the instance of a particular EVC service on
a specific interface and identifies all frames that
belongs to that particular service/flow.
2. To provide the capability of applying the configured
features to those frames belonging to the service.
3. To optionally define how to forward those frames in
the data-path.

The association of a service instance to an EVC depicts
an instance of an Ethernet flow on a particular interface
for an end-to-end (UNI-to-UNI) Ethernet service for a
subscriber.

The following diagram illustrates the association of
EVC, UNIs and service instances. UNI physical ports
are depicted as 'U', and service instances as 'x'.

CE MEN MEN CE

| | | | () | | | |
| |
| | | | () | | | |

^ ^
| |


This MIB module addresses the functional areas of network
management for EVC, including:

The operational mode for interfaces that are providing
Ethernet service(s).

The service attributes regarding an interface behaving
as UNI, such as CE-VLAN mapping and layer 2 control
protocol (eg. stp, vtp, cdp) processing.

The provisioning of service instances to define flow
points for an Ethernet service.

The operational status of EVCs for notifications
of status changes, and EVC creation and deletion.

Definition of terms and acronyms:

B-Tag: Backbone Tag field in Ethernet 802.1ah frame

CE: Customer Edge

CE-VLAN: Customer Edge VLAN

CoS: Class Of Service

EVC: Ethernet Virtual Connection

I-SID: Service Instance Identifier field in Ethernet
802.1ah frame

MAC: Media Access Control

MEN: Metro Ethernet Network

NNI: Network to Network Interface

OAM: Operations Administration and Management

PPPoE: Point-to-Point Protocol over Ethernet

Service frame: An Ethernet frame transmitted across the
UNI toward the service provider or an Ethernet frame
transmitted across the UNI toward the Subscriber.

Service Instance: A flow point of an Ethernet service

Service provider: The organization providing Ethernet
service(s).

Subscriber: The organization purchasing and/or using
Ethernet service(s).

UNI: User Network Interface
The physical demarcation point between the
responsibility of the service provider and
the responsibility of the Subscriber.

UNI-C: User Network Interface, subscriber side

UNI-N: User Network Interface, service provider side

VLAN: Virtual Local Area Network

ciscoEvcMIB — Cisco, Cisco MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies

Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. Using standard Ethernet interfaces, subscribers can set up secure, private Ethernet Virtual Connections, to connect their sites together and connect to business partners, suppliers and the Internet. This MIB module defines the managed objects and notifications describing Ethernet Virtual Connections. Ethernet Virtual Connections (EVC), are defined by the Metro Ethernet Forum (MEF), as an association between two or more UNIs. Frames within an EVC can only be exchanged among the associated UNIs. Frames sent into the MEN via a particular UNI must not be delivered back to the UNI from which it originated. Along an EVC path, there are demarcation flow points on associated ingress and egress interface, of every device, through which the EVC passes. A service instance represents these flow points where a service passes through an interface. From an operational perspective, a service instance serves three purposes: 1. Defines the instance of a particular EVC service on a specific interface and identifies all frames that belongs to that particular service/flow. 2. To provide the capability of applying the configured features to those frames belonging to the service. 3. To optionally define how to forward those frames in the data-path. The association of a service instance to an EVC depicts an instance of an Ethernet flow on a particular interface for an end-to-end (UNI-to-UNI) Ethernet service for a subscriber. The following diagram illustrates the association of EVC, UNIs and service instances. UNI physical ports are depicted as 'U', and service instances as 'x'. CE MEN MEN CE ------- ------- ------- ------- | | | | () | | | | | |--------Ux x|--( )--|x xU--------| | | | | | () | | | | ------- ------- ------- ------- ^ ^ | | -------- EVC --------- This MIB module addresses the functional areas of network management for EVC, including: The operational mode for interfaces that are providing Ethernet service(s). The service attributes regarding an interface behaving as UNI, such as CE-VLAN mapping and layer 2 control protocol (eg. stp, vtp, cdp) processing. The provisioning of service instances to define flow points for an Ethernet service. The operational status of EVCs for notifications of status changes, and EVC creation and deletion. Definition of terms and acronyms: B-Tag: Backbone Tag field in Ethernet 802.1ah frame CE: Customer Edge CE-VLAN: Customer Edge VLAN CoS: Class Of Service EVC: Ethernet Virtual Connection I-SID: Service Instance Identifier field in Ethernet 802.1ah frame MAC: Media Access Control MEN: Metro Ethernet Network NNI: Network to Network Interface OAM: Operations Administration and Management PPPoE: Point-to-Point Protocol over Ethernet Service frame: An Ethernet frame transmitted across the UNI toward the service provider or an Ethernet frame transmitted across the UNI toward the Subscriber. Service Instance: A flow point of an Ethernet service Service provider: The organization providing Ethernet service(s). Subscriber: The organization purchasing and/or using Ethernet service(s). UNI: User Network Interface The physical demarcation point between the responsibility of the service provider and the responsibility of the Subscriber. UNI-C: User Network Interface, subscriber side UNI-N: User Network Interface, service provider side VLAN: Virtual Local Area Network

Source records

ciscoEvcMIB

Status in source: unspecified.

Names: ciscoEvcMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoEvcMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313230353231303030305a22"
    ],
    "ORGANIZATION",
    "\"Cisco Systems, Inc.\"",
    "CONTACT-INFO",
    "\"Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-ethermibs@cisco.com\"",
    "DESCRIPTION",
    "\"Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. Using standard Ethernet interfaces, subscribers can set up secure, private Ethernet Virtual Connections, to connect their sites together and connect to business partners, suppliers and the Internet. This MIB module defines the managed objects and notifications describing Ethernet Virtual Connections. Ethernet Virtual Connections (EVC), are defined by the Metro Ethernet Forum (MEF), as an association between two or more UNIs. Frames within an EVC can only be exchanged among the associated UNIs. Frames sent into the MEN via a particular UNI must not be delivered back to the UNI from which it originated. Along an EVC path, there are demarcation flow points on associated ingress and egress interface, of every device, through which the EVC passes. A service instance represents these flow points where a service passes through an interface. From an operational perspective, a service instance serves three purposes: 1. Defines the instance of a particular EVC service on a specific interface and identifies all frames that belongs to that particular service/flow. 2. To provide the capability of applying the configured features to those frames belonging to the service. 3. To optionally define how to forward those frames in the data-path. The association of a service instance to an EVC depicts an instance of an Ethernet flow on a particular interface for an end-to-end (UNI-to-UNI) Ethernet service for a subscriber. The following diagram illustrates the association of EVC, UNIs and service instances. UNI physical ports are depicted as 'U', and service instances as 'x'. CE MEN MEN CE ------- ------- ------- ------- | | | | () | | | | | |--------Ux x|--( )--|x xU--------| | | | | | () | | | | ------- ------- ------- ------- ^ ^ | | -------- EVC --------- This MIB module addresses the functional areas of network management for EVC, including: The operational mode for interfaces that are providing Ethernet service(s). The service attributes regarding an interface behaving as UNI, such as CE-VLAN mapping and layer 2 control protocol (eg. stp, vtp, cdp) processing. The provisioning of service instances to define flow points for an Ethernet service. The operational status of EVCs for notifications of status changes, and EVC creation and deletion. Definition of terms and acronyms: B-Tag: Backbone Tag field in Ethernet 802.1ah frame CE: Customer Edge CE-VLAN: Customer Edge VLAN CoS: Class Of Service EVC: Ethernet Virtual Connection I-SID: Service Instance Identifier field in Ethernet 802.1ah frame MAC: Media Access Control MEN: Metro Ethernet Network NNI: Network to Network Interface OAM: Operations Administration and Management PPPoE: Point-to-Point Protocol over Ethernet Service frame: An Ethernet frame transmitted across the UNI toward the service provider or an Ethernet frame transmitted across the UNI toward the Subscriber. Service Instance: A flow point of an Ethernet service Service provider: The organization providing Ethernet service(s). Subscriber: The organization purchasing and/or using Ethernet service(s). UNI: User Network Interface The physical demarcation point between the responsibility of the service provider and the responsibility of the Subscriber. UNI-C: User Network Interface, subscriber side UNI-N: User Network Interface, service provider side VLAN: Virtual Local Area Network\"",
    "REVISION",
    [
      "literal",
      "223230313230353231303030305a22"
    ],
    "DESCRIPTION",
    "\"- Added following objects to cevcSITable: * cevcSICreationType * cevcSIType - Added following objects to cevcSIForwardBdTable: * cevcSIForwardBdNumberBase * cevcSIForwardBdNumber1kBitmap * cevcSIForwardBdNumber2kBitmap * cevcSIForwardBdNumber3kBitmap * cevcSIForwardBdNumber4kBitmap - Added MacSecurityViolation OID subtree and following objects: * cevcMacAddress * cevcMaxMacConfigLimit * cevcSIID - Deprecated cevcEvcNotificationGroup and added cevcEvcNotificationGroupRev1 and added cevcMacSecurityViolationNotification - Deprecated cevcSIGroup and added cevcSIGroupRev1 and added cevcSICreationType and cevcSIType - Deprecated cevcSIForwardGroup and added cevcSIForwardGroupRev1 and added the new objects mentioned in cevcSIForwardBdTable - Added CevcMacSecurityViolationCause Textual convention - Added new ciscoEvcMIBComplianceRev2\"",
    "REVISION",
    [
      "literal",
      "223230303830353031303030305a22"
    ],
    "DESCRIPTION",
    "\"- Added following enums to cevcSIOperStatus: * deleted(4) * errorDisabled(5) * unknown(6) - Added following named bits to cevcSIMatchEncapValid: * payloadTypes(3) * priorityCos(4) * dot1qNativeVlan(5) * dot1adNativeVlan(6) * encapExact(7) - The Object cevcSIMatchEncapPayloadType is replaced by new object cevcSIMatchEncapPayloadTypes to support multiple payload types for service instance match criteria. - Added new object cevcSIMatchEncapPriorityCos to cevcSIMatchEncapTable. - Added new Compliance ciscoEvcMIBComplianceRev1. - Added new Object Group cevcSIMatchCriteriaGroupRev1. - Miscellaneous updates/corrections.\"",
    "REVISION",
    [
      "literal",
      "223230303731323230303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "613",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201205210000Z"
    ],
    [
      "ORGANIZATION",
      "Cisco Systems, Inc."
    ],
    [
      "CONTACT-INFO",
      "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-ethermibs@cisco.com"
    ],
    [
      "DESCRIPTION",
      "Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. Using standard Ethernet interfaces, subscribers can set up secure, private Ethernet Virtual Connections, to connect their sites together and connect to business partners, suppliers and the Internet. This MIB module defines the managed objects and notifications describing Ethernet Virtual Connections. Ethernet Virtual Connections (EVC), are defined by the Metro Ethernet Forum (MEF), as an association between two or more UNIs. Frames within an EVC can only be exchanged among the associated UNIs. Frames sent into the MEN via a particular UNI must not be delivered back to the UNI from which it originated. Along an EVC path, there are demarcation flow points on associated ingress and egress interface, of every device, through which the EVC passes. A service instance represents these flow points where a service passes through an interface. From an operational perspective, a service instance serves three purposes: 1. Defines the instance of a particular EVC service on a specific interface and identifies all frames that belongs to that particular service/flow. 2. To provide the capability of applying the configured features to those frames belonging to the service. 3. To optionally define how to forward those frames in the data-path. The association of a service instance to an EVC depicts an instance of an Ethernet flow on a particular interface for an end-to-end (UNI-to-UNI) Ethernet service for a subscriber. The following diagram illustrates the association of EVC, UNIs and service instances. UNI physical ports are depicted as 'U', and service instances as 'x'. CE MEN MEN CE ------- ------- ------- ------- | | | | () | | | | | |--------Ux x|--( )--|x xU--------| | | | | | () | | | | ------- ------- ------- ------- ^ ^ | | -------- EVC --------- This MIB module addresses the functional areas of network management for EVC, including: The operational mode for interfaces that are providing Ethernet service(s). The service attributes regarding an interface behaving as UNI, such as CE-VLAN mapping and layer 2 control protocol (eg. stp, vtp, cdp) processing. The provisioning of service instances to define flow points for an Ethernet service. The operational status of EVCs for notifications of status changes, and EVC creation and deletion. Definition of terms and acronyms: B-Tag: Backbone Tag field in Ethernet 802.1ah frame CE: Customer Edge CE-VLAN: Customer Edge VLAN CoS: Class Of Service EVC: Ethernet Virtual Connection I-SID: Service Instance Identifier field in Ethernet 802.1ah frame MAC: Media Access Control MEN: Metro Ethernet Network NNI: Network to Network Interface OAM: Operations Administration and Management PPPoE: Point-to-Point Protocol over Ethernet Service frame: An Ethernet frame transmitted across the UNI toward the service provider or an Ethernet frame transmitted across the UNI toward the Subscriber. Service Instance: A flow point of an Ethernet service Service provider: The organization providing Ethernet service(s). Subscriber: The organization purchasing and/or using Ethernet service(s). UNI: User Network Interface The physical demarcation point between the responsibility of the service provider and the responsibility of the Subscriber. UNI-C: User Network Interface, subscriber side UNI-N: User Network Interface, service provider side VLAN: Virtual Local Area Network"
    ],
    [
      "Revisions",
      [
        [
          "201205210000Z",
          [
            "DESCRIPTION",
            "- Added following objects to cevcSITable: * cevcSICreationType * cevcSIType - Added following objects to cevcSIForwardBdTable: * cevcSIForwardBdNumberBase * cevcSIForwardBdNumber1kBitmap * cevcSIForwardBdNumber2kBitmap * cevcSIForwardBdNumber3kBitmap * cevcSIForwardBdNumber4kBitmap - Added MacSecurityViolation OID subtree and following objects: * cevcMacAddress * cevcMaxMacConfigLimit * cevcSIID - Deprecated cevcEvcNotificationGroup and added cevcEvcNotificationGroupRev1 and added cevcMacSecurityViolationNotification - Deprecated cevcSIGroup and added cevcSIGroupRev1 and added cevcSICreationType and cevcSIType - Deprecated cevcSIForwardGroup and added cevcSIForwardGroupRev1 and added the new objects mentioned in cevcSIForwardBdTable - Added CevcMacSecurityViolationCause Textual convention - Added new ciscoEvcMIBComplianceRev2"
          ]
        ],
        [
          "200805010000Z",
          [
            "DESCRIPTION",
            "- Added following enums to cevcSIOperStatus: * deleted(4) * errorDisabled(5) * unknown(6) - Added following named bits to cevcSIMatchEncapValid: * payloadTypes(3) * priorityCos(4) * dot1qNativeVlan(5) * dot1adNativeVlan(6) * encapExact(7) - The Object cevcSIMatchEncapPayloadType is replaced by new object cevcSIMatchEncapPayloadTypes to support multiple payload types for service instance match criteria. - Added new object cevcSIMatchEncapPriorityCos to cevcSIMatchEncapTable. - Added new Compliance ciscoEvcMIBComplianceRev1. - Added new Object Group cevcSIMatchCriteriaGroupRev1. - Miscellaneous updates/corrections."
          ]
        ],
        [
          "200712200000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}
  • Cisco · Publisher's source file: CISCO-EVC-MIB.my

    Module: CISCO-EVC-MIB

    Published definition
    ciscoEvcMIB MODULE-IDENTITY
        LAST-UPDATED    "201205210000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "Cisco Systems
                Customer Service
    
                Postal: 170 W Tasman Drive San Jose, CA  95134
                USA
    
                Tel: +1 800 553-NETS
    
                E-mail: cs-ethermibs@cisco.com"
        DESCRIPTION
            "Metro Ethernet services can support a wide range of
            applications and subscriber needs easily, efficiently
            and cost-effectively.  Using standard Ethernet interfaces, 
            subscribers can set up secure, private Ethernet Virtual 
            Connections, to connect their sites together and connect 
            to business partners, suppliers and the Internet.
    
            This MIB module defines the managed objects and notifications
            describing Ethernet Virtual Connections.
    
            Ethernet Virtual Connections (EVC), are defined by the Metro
            Ethernet Forum (MEF), as an association between two or more
            UNIs.  Frames within an EVC can only be exchanged among the
            associated UNIs.  Frames sent into the MEN via a particular
            UNI must not be delivered back to the UNI from which it 
            originated.  
    
            Along an EVC path, there are demarcation flow points on 
            associated ingress and egress interface, of every device, 
            through which the EVC passes.  A service instance represents
            these flow points where a service passes through an interface.  
    
            From an operational perspective, a service instance serves 
            three purposes: 
                1.  Defines the instance of a particular EVC service on
                    a specific interface and identifies all frames that
                    belongs to that particular service/flow.
                2.  To provide the capability of applying the configured 
                    features to those frames belonging to the service.
                3.  To optionally define how to forward those frames in
                    the data-path.  
    
            The association of a service instance to an EVC depicts
            an instance of an Ethernet flow on a particular interface
            for an end-to-end (UNI-to-UNI) Ethernet service for a 
            subscriber.
    
            The following diagram illustrates the association of
            EVC, UNIs and service instances.  UNI physical ports
            are depicted as 'U', and service instances as 'x'.
    
                CE             MEN            MEN            CE
              -------        -------        -------        -------
              |     |        |     |   ()   |     |        |     |
              |     |--------Ux   x|--(  )--|x   xU--------|     |
              |     |        |     |   ()   |     |        |     |
              -------        -------        -------        -------
                             ^                    ^
                             |                    |
                             -------- EVC ---------
    
            This MIB module addresses the functional areas of network
            management for EVC, including:
    
                The operational mode for interfaces that are providing
                Ethernet service(s).
    
                The service attributes regarding an interface behaving
                as UNI, such as CE-VLAN mapping and layer 2 control 
                protocol (eg. stp, vtp, cdp) processing.
    
                The provisioning of service instances to define flow 
                points for an Ethernet service.
    
                The operational status of EVCs for notifications
                of status changes, and EVC creation and deletion.
    
            Definition of terms and acronyms:
    
                B-Tag: Backbone Tag field in Ethernet 802.1ah frame
    
                CE: Customer Edge
    
                CE-VLAN: Customer Edge VLAN
    
                CoS: Class Of Service
    
                EVC: Ethernet Virtual Connection
    
                I-SID: Service Instance Identifier field in Ethernet 
                802.1ah frame
    
                MAC: Media Access Control
    
                MEN: Metro Ethernet Network 
    
                NNI: Network to Network Interface
    
                OAM: Operations Administration and Management
    
                PPPoE: Point-to-Point Protocol over Ethernet
    
                Service frame: An Ethernet frame transmitted across the 
                UNI toward the service provider or an Ethernet frame 
                transmitted across the UNI toward the Subscriber.
    
                Service Instance: A flow point of an Ethernet service
    
                Service provider: The organization providing Ethernet
                service(s).
    
                Subscriber: The organization purchasing and/or using 
                Ethernet service(s).
    
                UNI: User Network Interface
                     The physical demarcation point between the 
                     responsibility of the service provider and 
                     the responsibility of the Subscriber.
    
                UNI-C: User Network Interface, subscriber side
    
                UNI-N: User Network Interface, service provider side
    
                VLAN: Virtual Local Area Network"
        REVISION        "201205210000Z"
        DESCRIPTION
            "- Added following objects to cevcSITable:
            * cevcSICreationType
            * cevcSIType
            - Added following objects to cevcSIForwardBdTable:
             * cevcSIForwardBdNumberBase
             * cevcSIForwardBdNumber1kBitmap
             * cevcSIForwardBdNumber2kBitmap
             * cevcSIForwardBdNumber3kBitmap
             * cevcSIForwardBdNumber4kBitmap
            - Added MacSecurityViolation OID subtree and following objects:
            * cevcMacAddress
            * cevcMaxMacConfigLimit
            * cevcSIID
            - Deprecated cevcEvcNotificationGroup and added
                    cevcEvcNotificationGroupRev1 and added 
                    cevcMacSecurityViolationNotification
            - Deprecated cevcSIGroup and added cevcSIGroupRev1
             and added cevcSICreationType and cevcSIType
            - Deprecated cevcSIForwardGroup and added cevcSIForwardGroupRev1
             and added the new objects mentioned in cevcSIForwardBdTable
            - Added CevcMacSecurityViolationCause Textual convention
            - Added new ciscoEvcMIBComplianceRev2"
        REVISION        "200805010000Z"
        DESCRIPTION
            "- Added following enums to cevcSIOperStatus:
            * deleted(4)
            * errorDisabled(5)
            * unknown(6)
    
            - Added following named bits to cevcSIMatchEncapValid:
            * payloadTypes(3)
            * priorityCos(4)
            * dot1qNativeVlan(5)
            * dot1adNativeVlan(6)
            * encapExact(7)
    
            - The Object cevcSIMatchEncapPayloadType is replaced by
            new object cevcSIMatchEncapPayloadTypes to support multiple
            payload types for service instance match criteria.
    
            - Added new object cevcSIMatchEncapPriorityCos to 
            cevcSIMatchEncapTable.
    
            - Added new Compliance ciscoEvcMIBComplianceRev1.
    
            - Added new Object Group cevcSIMatchCriteriaGroupRev1.
    
            - Miscellaneous updates/corrections."
        REVISION        "200712200000Z"
        DESCRIPTION
            "Initial version of this MIB module."
        ::= { ciscoMgmt 613 }
    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndexOrZero'], 'CISCO-TC': ['CiscoCosList'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32', 'Gauge32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanId', 'VlanIdOrNone'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download CISCO-EVC-MIB.my
    Source location: CISCO-EVC-MIB::ciscoEvcMIB.
    Source version and references

    Downloaded: 2026-10-19T00:18:11.263560+00:00.

  • Cisco MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. Cisco support.

    Module: CISCO-EVC-MIB

    Published definition
    ciscoEvcMIB MODULE-IDENTITY
        LAST-UPDATED    "201205210000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "Cisco Systems
                Customer Service
    
                Postal: 170 W Tasman Drive San Jose, CA  95134
                USA
    
                Tel: +1 800 553-NETS
    
                E-mail: cs-ethermibs@cisco.com"
        DESCRIPTION
            "Metro Ethernet services can support a wide range of
            applications and subscriber needs easily, efficiently
            and cost-effectively.  Using standard Ethernet interfaces, 
            subscribers can set up secure, private Ethernet Virtual 
            Connections, to connect their sites together and connect 
            to business partners, suppliers and the Internet.
    
            This MIB module defines the managed objects and notifications
            describing Ethernet Virtual Connections.
    
            Ethernet Virtual Connections (EVC), are defined by the Metro
            Ethernet Forum (MEF), as an association between two or more
            UNIs.  Frames within an EVC can only be exchanged among the
            associated UNIs.  Frames sent into the MEN via a particular
            UNI must not be delivered back to the UNI from which it 
            originated.  
    
            Along an EVC path, there are demarcation flow points on 
            associated ingress and egress interface, of every device, 
            through which the EVC passes.  A service instance represents
            these flow points where a service passes through an interface.  
    
            From an operational perspective, a service instance serves 
            three purposes: 
                1.  Defines the instance of a particular EVC service on
                    a specific interface and identifies all frames that
                    belongs to that particular service/flow.
                2.  To provide the capability of applying the configured 
                    features to those frames belonging to the service.
                3.  To optionally define how to forward those frames in
                    the data-path.  
    
            The association of a service instance to an EVC depicts
            an instance of an Ethernet flow on a particular interface
            for an end-to-end (UNI-to-UNI) Ethernet service for a 
            subscriber.
    
            The following diagram illustrates the association of
            EVC, UNIs and service instances.  UNI physical ports
            are depicted as 'U', and service instances as 'x'.
    
                CE             MEN            MEN            CE
              -------        -------        -------        -------
              |     |        |     |   ()   |     |        |     |
              |     |--------Ux   x|--(  )--|x   xU--------|     |
              |     |        |     |   ()   |     |        |     |
              -------        -------        -------        -------
                             ^                    ^
                             |                    |
                             -------- EVC ---------
    
            This MIB module addresses the functional areas of network
            management for EVC, including:
    
                The operational mode for interfaces that are providing
                Ethernet service(s).
    
                The service attributes regarding an interface behaving
                as UNI, such as CE-VLAN mapping and layer 2 control 
                protocol (eg. stp, vtp, cdp) processing.
    
                The provisioning of service instances to define flow 
                points for an Ethernet service.
    
                The operational status of EVCs for notifications
                of status changes, and EVC creation and deletion.
    
            Definition of terms and acronyms:
    
                B-Tag: Backbone Tag field in Ethernet 802.1ah frame
    
                CE: Customer Edge
    
                CE-VLAN: Customer Edge VLAN
    
                CoS: Class Of Service
    
                EVC: Ethernet Virtual Connection
    
                I-SID: Service Instance Identifier field in Ethernet 
                802.1ah frame
    
                MAC: Media Access Control
    
                MEN: Metro Ethernet Network 
    
                NNI: Network to Network Interface
    
                OAM: Operations Administration and Management
    
                PPPoE: Point-to-Point Protocol over Ethernet
    
                Service frame: An Ethernet frame transmitted across the 
                UNI toward the service provider or an Ethernet frame 
                transmitted across the UNI toward the Subscriber.
    
                Service Instance: A flow point of an Ethernet service
    
                Service provider: The organization providing Ethernet
                service(s).
    
                Subscriber: The organization purchasing and/or using 
                Ethernet service(s).
    
                UNI: User Network Interface
                     The physical demarcation point between the 
                     responsibility of the service provider and 
                     the responsibility of the Subscriber.
    
                UNI-C: User Network Interface, subscriber side
    
                UNI-N: User Network Interface, service provider side
    
                VLAN: Virtual Local Area Network"
        REVISION        "201205210000Z"
        DESCRIPTION
            "- Added following objects to cevcSITable:
            * cevcSICreationType
            * cevcSIType
            - Added following objects to cevcSIForwardBdTable:
             * cevcSIForwardBdNumberBase
             * cevcSIForwardBdNumber1kBitmap
             * cevcSIForwardBdNumber2kBitmap
             * cevcSIForwardBdNumber3kBitmap
             * cevcSIForwardBdNumber4kBitmap
            - Added MacSecurityViolation OID subtree and following objects:
            * cevcMacAddress
            * cevcMaxMacConfigLimit
            * cevcSIID
            - Deprecated cevcEvcNotificationGroup and added
                    cevcEvcNotificationGroupRev1 and added 
                    cevcMacSecurityViolationNotification
            - Deprecated cevcSIGroup and added cevcSIGroupRev1
             and added cevcSICreationType and cevcSIType
            - Deprecated cevcSIForwardGroup and added cevcSIForwardGroupRev1
             and added the new objects mentioned in cevcSIForwardBdTable
            - Added CevcMacSecurityViolationCause Textual convention
            - Added new ciscoEvcMIBComplianceRev2"
        REVISION        "200805010000Z"
        DESCRIPTION
            "- Added following enums to cevcSIOperStatus:
            * deleted(4)
            * errorDisabled(5)
            * unknown(6)
    
            - Added following named bits to cevcSIMatchEncapValid:
            * payloadTypes(3)
            * priorityCos(4)
            * dot1qNativeVlan(5)
            * dot1adNativeVlan(6)
            * encapExact(7)
    
            - The Object cevcSIMatchEncapPayloadType is replaced by
            new object cevcSIMatchEncapPayloadTypes to support multiple
            payload types for service instance match criteria.
    
            - Added new object cevcSIMatchEncapPriorityCos to 
            cevcSIMatchEncapTable.
    
            - Added new Compliance ciscoEvcMIBComplianceRev1.
    
            - Added new Object Group cevcSIMatchCriteriaGroupRev1.
    
            - Miscellaneous updates/corrections."
        REVISION        "200712200000Z"
        DESCRIPTION
            "Initial version of this MIB module."
        ::= { ciscoMgmt 613 }
    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndexOrZero'], 'CISCO-TC': ['CiscoCosList'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32', 'Gauge32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanId', 'VlanIdOrNone'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download CISCO-EVC-MIB

    Related source files and packages:


    Source location: CISCO-EVC-MIB::ciscoEvcMIB.
    Source version and references

    Downloaded: 2026-10-24T02:14:08.157397+00:00.

  • Netdisco MIB archive copies · Publisher's source file: CISCO-EVC-MIB.my

    Vendor MIB copy from the Netdisco archive.

    Module: CISCO-EVC-MIB

    Published definition
    ciscoEvcMIB MODULE-IDENTITY
        LAST-UPDATED    "201205210000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "Cisco Systems
                Customer Service
    
                Postal: 170 W Tasman Drive San Jose, CA  95134
                USA
    
                Tel: +1 800 553-NETS
    
                E-mail: cs-ethermibs@cisco.com"
        DESCRIPTION
            "Metro Ethernet services can support a wide range of
            applications and subscriber needs easily, efficiently
            and cost-effectively.  Using standard Ethernet interfaces, 
            subscribers can set up secure, private Ethernet Virtual 
            Connections, to connect their sites together and connect 
            to business partners, suppliers and the Internet.
    
            This MIB module defines the managed objects and notifications
            describing Ethernet Virtual Connections.
    
            Ethernet Virtual Connections (EVC), are defined by the Metro
            Ethernet Forum (MEF), as an association between two or more
            UNIs.  Frames within an EVC can only be exchanged among the
            associated UNIs.  Frames sent into the MEN via a particular
            UNI must not be delivered back to the UNI from which it 
            originated.  
    
            Along an EVC path, there are demarcation flow points on 
            associated ingress and egress interface, of every device, 
            through which the EVC passes.  A service instance represents
            these flow points where a service passes through an interface.  
    
            From an operational perspective, a service instance serves 
            three purposes: 
                1.  Defines the instance of a particular EVC service on
                    a specific interface and identifies all frames that
                    belongs to that particular service/flow.
                2.  To provide the capability of applying the configured 
                    features to those frames belonging to the service.
                3.  To optionally define how to forward those frames in
                    the data-path.  
    
            The association of a service instance to an EVC depicts
            an instance of an Ethernet flow on a particular interface
            for an end-to-end (UNI-to-UNI) Ethernet service for a 
            subscriber.
    
            The following diagram illustrates the association of
            EVC, UNIs and service instances.  UNI physical ports
            are depicted as 'U', and service instances as 'x'.
    
                CE             MEN            MEN            CE
              -------        -------        -------        -------
              |     |        |     |   ()   |     |        |     |
              |     |--------Ux   x|--(  )--|x   xU--------|     |
              |     |        |     |   ()   |     |        |     |
              -------        -------        -------        -------
                             ^                    ^
                             |                    |
                             -------- EVC ---------
    
            This MIB module addresses the functional areas of network
            management for EVC, including:
    
                The operational mode for interfaces that are providing
                Ethernet service(s).
    
                The service attributes regarding an interface behaving
                as UNI, such as CE-VLAN mapping and layer 2 control 
                protocol (eg. stp, vtp, cdp) processing.
    
                The provisioning of service instances to define flow 
                points for an Ethernet service.
    
                The operational status of EVCs for notifications
                of status changes, and EVC creation and deletion.
    
            Definition of terms and acronyms:
    
                B-Tag: Backbone Tag field in Ethernet 802.1ah frame
    
                CE: Customer Edge
    
                CE-VLAN: Customer Edge VLAN
    
                CoS: Class Of Service
    
                EVC: Ethernet Virtual Connection
    
                I-SID: Service Instance Identifier field in Ethernet 
                802.1ah frame
    
                MAC: Media Access Control
    
                MEN: Metro Ethernet Network 
    
                NNI: Network to Network Interface
    
                OAM: Operations Administration and Management
    
                PPPoE: Point-to-Point Protocol over Ethernet
    
                Service frame: An Ethernet frame transmitted across the 
                UNI toward the service provider or an Ethernet frame 
                transmitted across the UNI toward the Subscriber.
    
                Service Instance: A flow point of an Ethernet service
    
                Service provider: The organization providing Ethernet
                service(s).
    
                Subscriber: The organization purchasing and/or using 
                Ethernet service(s).
    
                UNI: User Network Interface
                     The physical demarcation point between the 
                     responsibility of the service provider and 
                     the responsibility of the Subscriber.
    
                UNI-C: User Network Interface, subscriber side
    
                UNI-N: User Network Interface, service provider side
    
                VLAN: Virtual Local Area Network"
        REVISION        "201205210000Z"
        DESCRIPTION
            "- Added following objects to cevcSITable:
            * cevcSICreationType
            * cevcSIType
            - Added following objects to cevcSIForwardBdTable:
             * cevcSIForwardBdNumberBase
             * cevcSIForwardBdNumber1kBitmap
             * cevcSIForwardBdNumber2kBitmap
             * cevcSIForwardBdNumber3kBitmap
             * cevcSIForwardBdNumber4kBitmap
            - Added MacSecurityViolation OID subtree and following objects:
            * cevcMacAddress
            * cevcMaxMacConfigLimit
            * cevcSIID
            - Deprecated cevcEvcNotificationGroup and added
                    cevcEvcNotificationGroupRev1 and added 
                    cevcMacSecurityViolationNotification
            - Deprecated cevcSIGroup and added cevcSIGroupRev1
             and added cevcSICreationType and cevcSIType
            - Deprecated cevcSIForwardGroup and added cevcSIForwardGroupRev1
             and added the new objects mentioned in cevcSIForwardBdTable
            - Added CevcMacSecurityViolationCause Textual convention
            - Added new ciscoEvcMIBComplianceRev2"
        REVISION        "200805010000Z"
        DESCRIPTION
            "- Added following enums to cevcSIOperStatus:
            * deleted(4)
            * errorDisabled(5)
            * unknown(6)
    
            - Added following named bits to cevcSIMatchEncapValid:
            * payloadTypes(3)
            * priorityCos(4)
            * dot1qNativeVlan(5)
            * dot1adNativeVlan(6)
            * encapExact(7)
    
            - The Object cevcSIMatchEncapPayloadType is replaced by
            new object cevcSIMatchEncapPayloadTypes to support multiple
            payload types for service instance match criteria.
    
            - Added new object cevcSIMatchEncapPriorityCos to 
            cevcSIMatchEncapTable.
    
            - Added new Compliance ciscoEvcMIBComplianceRev1.
    
            - Added new Object Group cevcSIMatchCriteriaGroupRev1.
    
            - Miscellaneous updates/corrections."
        REVISION        "200712200000Z"
        DESCRIPTION
            "Initial version of this MIB module."
        ::= { ciscoMgmt 613 }
    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndexOrZero'], 'CISCO-TC': ['CiscoCosList'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32', 'Gauge32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanId', 'VlanIdOrNone'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download CISCO-EVC-MIB.my

    Related source files and packages:


    Source location: CISCO-EVC-MIB::ciscoEvcMIB.
    Source version and references

    Downloaded: 2026-10-24T15:28:09.052011+00:00.

ciscoEvcMIB

Status in source: unspecified.

Names: ciscoEvcMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoEvcMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303830353031303030305a22"
    ],
    "ORGANIZATION",
    "\"Cisco Systems, Inc.\"",
    "CONTACT-INFO",
    "\"Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-ethermibs@cisco.com\"",
    "DESCRIPTION",
    "\"Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. Using standard Ethernet interfaces, subscribers can set up secure, private Ethernet Virtual Connections, to connect their sites together and connect to business partners, suppliers and the Internet. This MIB module defines the managed objects and notifications describing Ethernet Virtual Connections. Ethernet Virtual Connections (EVC), are defined by the Metro Ethernet Forum (MEF), as an association between two or more UNIs. Frames within an EVC can only be exchanged among the associated UNIs. Frames sent into the MEN via a particular UNI must not be delivered back to the UNI from which it originated. Along an EVC path, there are demarcation flow points on associated ingress and egress interface, of every device, through which the EVC passes. A service instance represents these flow points where a service passes through an interface. From an operational perspective, a service instance serves three purposes: 1. Defines the instance of a particular EVC service on a specific interface and identifies all frames that belongs to that particular service/flow. 2. To provide the capability of applying the configured features to those frames belonging to the service. 3. To optionally define how to forward those frames in the data-path. The association of a service instance to an EVC depicts an instance of an Ethernet flow on a particular interface for an end-to-end (UNI-to-UNI) Ethernet service for a subscriber. The following diagram illustrates the association of EVC, UNIs and service instances. UNI physical ports are depicted as 'U', and service instances as 'x'. CE MEN MEN CE ------- ------- ------- ------- | | | | () | | | | | |--------Ux x|--( )--|x xU--------| | | | | | () | | | | ------- ------- ------- ------- ^ ^ | | -------- EVC --------- This MIB module addresses the functional areas of network management for EVC, including: The operational mode for interfaces that are providing Ethernet service(s). The service attributes regarding an interface behaving as UNI, such as CE-VLAN mapping and layer 2 control protocol (eg. stp, vtp, cdp) processing. The provisioning of service instances to define flow points for an Ethernet service. The operational status of EVCs for notifications of status changes, and EVC creation and deletion. Definition of terms and acronyms: B-Tag: Backbone Tag field in Ethernet 802.1ah frame CE: Customer Edge CE-VLAN: Customer Edge VLAN CoS: Class Of Service EVC: Ethernet Virtual Connection I-SID: Service Instance Identifier field in Ethernet 802.1ah frame MAC: Media Access Control MEN: Metro Ethernet Network NNI: Network to Network Interface OAM: Operations Administration and Management PPPoE: Point-to-Point Protocol over Ethernet Service frame: An Ethernet frame transmitted across the UNI toward the service provider or an Ethernet frame transmitted across the UNI toward the Subscriber. Service Instance: A flow point of an Ethernet service Service provider: The organization providing Ethernet service(s). Subscriber: The organization purchasing and/or using Ethernet service(s). UNI: User Network Interface The physical demarcation point between the responsibility of the service provider and the responsibility of the Subscriber. UNI-C: User Network Interface, subscriber side UNI-N: User Network Interface, service provider side VLAN: Virtual Local Area Network\"",
    "REVISION",
    [
      "literal",
      "223230303830353031303030305a22"
    ],
    "DESCRIPTION",
    "\"- Added following enums to cevcSIOperStatus: * deleted(4) * errorDisabled(5) * unknown(6) - Added following named bits to cevcSIMatchEncapValid: * payloadTypes(3) * priorityCos(4) * dot1qNativeVlan(5) * dot1adNativeVlan(6) * encapExact(7) - The Object cevcSIMatchEncapPayloadType is replaced by new object cevcSIMatchEncapPayloadTypes to support multiple payload types for service instance match criteria. - Added new object cevcSIMatchEncapPriorityCos to cevcSIMatchEncapTable. - Added new Compliance ciscoEvcMIBComplianceRev1. - Added new Object Group cevcSIMatchCriteriaGroupRev1. - Miscellaneous updates/corrections.\"",
    "REVISION",
    [
      "literal",
      "223230303731323230303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "613",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200805010000Z"
    ],
    [
      "ORGANIZATION",
      "Cisco Systems, Inc."
    ],
    [
      "CONTACT-INFO",
      "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-ethermibs@cisco.com"
    ],
    [
      "DESCRIPTION",
      "Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. Using standard Ethernet interfaces, subscribers can set up secure, private Ethernet Virtual Connections, to connect their sites together and connect to business partners, suppliers and the Internet. This MIB module defines the managed objects and notifications describing Ethernet Virtual Connections. Ethernet Virtual Connections (EVC), are defined by the Metro Ethernet Forum (MEF), as an association between two or more UNIs. Frames within an EVC can only be exchanged among the associated UNIs. Frames sent into the MEN via a particular UNI must not be delivered back to the UNI from which it originated. Along an EVC path, there are demarcation flow points on associated ingress and egress interface, of every device, through which the EVC passes. A service instance represents these flow points where a service passes through an interface. From an operational perspective, a service instance serves three purposes: 1. Defines the instance of a particular EVC service on a specific interface and identifies all frames that belongs to that particular service/flow. 2. To provide the capability of applying the configured features to those frames belonging to the service. 3. To optionally define how to forward those frames in the data-path. The association of a service instance to an EVC depicts an instance of an Ethernet flow on a particular interface for an end-to-end (UNI-to-UNI) Ethernet service for a subscriber. The following diagram illustrates the association of EVC, UNIs and service instances. UNI physical ports are depicted as 'U', and service instances as 'x'. CE MEN MEN CE ------- ------- ------- ------- | | | | () | | | | | |--------Ux x|--( )--|x xU--------| | | | | | () | | | | ------- ------- ------- ------- ^ ^ | | -------- EVC --------- This MIB module addresses the functional areas of network management for EVC, including: The operational mode for interfaces that are providing Ethernet service(s). The service attributes regarding an interface behaving as UNI, such as CE-VLAN mapping and layer 2 control protocol (eg. stp, vtp, cdp) processing. The provisioning of service instances to define flow points for an Ethernet service. The operational status of EVCs for notifications of status changes, and EVC creation and deletion. Definition of terms and acronyms: B-Tag: Backbone Tag field in Ethernet 802.1ah frame CE: Customer Edge CE-VLAN: Customer Edge VLAN CoS: Class Of Service EVC: Ethernet Virtual Connection I-SID: Service Instance Identifier field in Ethernet 802.1ah frame MAC: Media Access Control MEN: Metro Ethernet Network NNI: Network to Network Interface OAM: Operations Administration and Management PPPoE: Point-to-Point Protocol over Ethernet Service frame: An Ethernet frame transmitted across the UNI toward the service provider or an Ethernet frame transmitted across the UNI toward the Subscriber. Service Instance: A flow point of an Ethernet service Service provider: The organization providing Ethernet service(s). Subscriber: The organization purchasing and/or using Ethernet service(s). UNI: User Network Interface The physical demarcation point between the responsibility of the service provider and the responsibility of the Subscriber. UNI-C: User Network Interface, subscriber side UNI-N: User Network Interface, service provider side VLAN: Virtual Local Area Network"
    ],
    [
      "Revisions",
      [
        [
          "200805010000Z",
          [
            "DESCRIPTION",
            "- Added following enums to cevcSIOperStatus: * deleted(4) * errorDisabled(5) * unknown(6) - Added following named bits to cevcSIMatchEncapValid: * payloadTypes(3) * priorityCos(4) * dot1qNativeVlan(5) * dot1adNativeVlan(6) * encapExact(7) - The Object cevcSIMatchEncapPayloadType is replaced by new object cevcSIMatchEncapPayloadTypes to support multiple payload types for service instance match criteria. - Added new object cevcSIMatchEncapPriorityCos to cevcSIMatchEncapTable. - Added new Compliance ciscoEvcMIBComplianceRev1. - Added new Object Group cevcSIMatchCriteriaGroupRev1. - Miscellaneous updates/corrections."
          ]
        ],
        [
          "200712200000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}
  • Preserved mibdepot archive

    Module: CISCO-EVC-MIB

    Published definition
    ciscoEvcMIB MODULE-IDENTITY
        LAST-UPDATED    "200805010000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "Cisco Systems
                Customer Service
    
                Postal: 170 W Tasman Drive San Jose, CA  95134
                USA
    
                Tel: +1 800 553-NETS
    
                E-mail: cs-ethermibs@cisco.com"
        DESCRIPTION
            "Metro Ethernet services can support a wide range of
            applications and subscriber needs easily, efficiently
            and cost-effectively.  Using standard Ethernet interfaces, 
            subscribers can set up secure, private Ethernet Virtual 
            Connections, to connect their sites together and connect 
            to business partners, suppliers and the Internet.
    
            This MIB module defines the managed objects and notifications
            describing Ethernet Virtual Connections.
    
            Ethernet Virtual Connections (EVC), are defined by the Metro
            Ethernet Forum (MEF), as an association between two or more
            UNIs.  Frames within an EVC can only be exchanged among the
            associated UNIs.  Frames sent into the MEN via a particular
            UNI must not be delivered back to the UNI from which it 
            originated.  
    
            Along an EVC path, there are demarcation flow points on 
            associated ingress and egress interface, of every device, 
            through which the EVC passes.  A service instance represents
            these flow points where a service passes through an interface.  
    
            From an operational perspective, a service instance serves 
            three purposes: 
                1.  Defines the instance of a particular EVC service on
                    a specific interface and identifies all frames that
                    belongs to that particular service/flow.
                2.  To provide the capability of applying the configured 
                    features to those frames belonging to the service.
                3.  To optionally define how to forward those frames in
                    the data-path.  
    
            The association of a service instance to an EVC depicts
            an instance of an Ethernet flow on a particular interface
            for an end-to-end (UNI-to-UNI) Ethernet service for a 
            subscriber.
    
            The following diagram illustrates the association of
            EVC, UNIs and service instances.  UNI physical ports
            are depicted as 'U', and service instances as 'x'.
    
                CE             MEN            MEN            CE
              -------        -------        -------        -------
              |     |        |     |   ()   |     |        |     |
              |     |--------Ux   x|--(  )--|x   xU--------|     |
              |     |        |     |   ()   |     |        |     |
              -------        -------        -------        -------
                             ^                    ^
                             |                    |
                             -------- EVC ---------
    
            This MIB module addresses the functional areas of network
            management for EVC, including:
    
                The operational mode for interfaces that are providing
                Ethernet service(s).
    
                The service attributes regarding an interface behaving
                as UNI, such as CE-VLAN mapping and layer 2 control 
                protocol (eg. stp, vtp, cdp) processing.
    
                The provisioning of service instances to define flow 
                points for an Ethernet service.
    
                The operational status of EVCs for notifications
                of status changes, and EVC creation and deletion.
    
            Definition of terms and acronyms:
    
                B-Tag: Backbone Tag field in Ethernet 802.1ah frame
    
                CE: Customer Edge
    
                CE-VLAN: Customer Edge VLAN
    
                CoS: Class Of Service
    
                EVC: Ethernet Virtual Connection
    
                I-SID: Service Instance Identifier field in Ethernet 
                802.1ah frame
    
                MAC: Media Access Control
    
                MEN: Metro Ethernet Network 
    
                NNI: Network to Network Interface
    
                OAM: Operations Administration and Management
    
                PPPoE: Point-to-Point Protocol over Ethernet
    
                Service frame: An Ethernet frame transmitted across the 
                UNI toward the service provider or an Ethernet frame 
                transmitted across the UNI toward the Subscriber.
    
                Service Instance: A flow point of an Ethernet service
    
                Service provider: The organization providing Ethernet
                service(s).
    
                Subscriber: The organization purchasing and/or using 
                Ethernet service(s).
    
                UNI: User Network Interface
                     The physical demarcation point between the 
                     responsibility of the service provider and 
                     the responsibility of the Subscriber.
    
                UNI-C: User Network Interface, subscriber side
    
                UNI-N: User Network Interface, service provider side
    
                VLAN: Virtual Local Area Network"
        REVISION        "200805010000Z"
        DESCRIPTION
            "- Added following enums to cevcSIOperStatus:
            * deleted(4)
            * errorDisabled(5)
            * unknown(6)
    
            - Added following named bits to cevcSIMatchEncapValid:
            * payloadTypes(3)
            * priorityCos(4)
            * dot1qNativeVlan(5)
            * dot1adNativeVlan(6)
            * encapExact(7)
    
            - The Object cevcSIMatchEncapPayloadType is replaced by
            new object cevcSIMatchEncapPayloadTypes to support multiple
            payload types for service instance match criteria.
    
            - Added new object cevcSIMatchEncapPriorityCos to 
            cevcSIMatchEncapTable.
    
            - Added new Compliance ciscoEvcMIBComplianceRev1.
    
            - Added new Object Group cevcSIMatchCriteriaGroupRev1.
    
            - Miscellaneous updates/corrections."
        REVISION        "200712200000Z"
        DESCRIPTION
            "Initial version of this MIB module."
        ::= { ciscoMgmt 613 }
    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndexOrZero'], 'CISCO-TC': ['CiscoCosList'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32', 'Gauge32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanId', 'VlanIdOrNone'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download CISCO-EVC-MIB.my.txt
    Source location: CISCO-EVC-MIB::ciscoEvcMIB.
    Source version and references

    Archived: 2026-10-19T00:22:08.189429+00:00.

  • Preserved circitor archive

    Module: CISCO-EVC-MIB

    Published definition
    ciscoEvcMIB MODULE-IDENTITY
        LAST-UPDATED    "200805010000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "Cisco Systems
                Customer Service
    
                Postal: 170 W Tasman Drive San Jose, CA  95134
                USA
    
                Tel: +1 800 553-NETS
    
                E-mail: cs-ethermibs@cisco.com"
        DESCRIPTION
            "Metro Ethernet services can support a wide range of
            applications and subscriber needs easily, efficiently
            and cost-effectively.  Using standard Ethernet interfaces, 
            subscribers can set up secure, private Ethernet Virtual 
            Connections, to connect their sites together and connect 
            to business partners, suppliers and the Internet.
    
            This MIB module defines the managed objects and notifications
            describing Ethernet Virtual Connections.
    
            Ethernet Virtual Connections (EVC), are defined by the Metro
            Ethernet Forum (MEF), as an association between two or more
            UNIs.  Frames within an EVC can only be exchanged among the
            associated UNIs.  Frames sent into the MEN via a particular
            UNI must not be delivered back to the UNI from which it 
            originated.  
    
            Along an EVC path, there are demarcation flow points on 
            associated ingress and egress interface, of every device, 
            through which the EVC passes.  A service instance represents
            these flow points where a service passes through an interface.  
    
            From an operational perspective, a service instance serves 
            three purposes: 
                1.  Defines the instance of a particular EVC service on
                    a specific interface and identifies all frames that
                    belongs to that particular service/flow.
                2.  To provide the capability of applying the configured 
                    features to those frames belonging to the service.
                3.  To optionally define how to forward those frames in
                    the data-path.  
    
            The association of a service instance to an EVC depicts
            an instance of an Ethernet flow on a particular interface
            for an end-to-end (UNI-to-UNI) Ethernet service for a 
            subscriber.
    
            The following diagram illustrates the association of
            EVC, UNIs and service instances.  UNI physical ports
            are depicted as 'U', and service instances as 'x'.
    
                CE             MEN            MEN            CE
              -------        -------        -------        -------
              |     |        |     |   ()   |     |        |     |
              |     |--------Ux   x|--(  )--|x   xU--------|     |
              |     |        |     |   ()   |     |        |     |
              -------        -------        -------        -------
                             ^                    ^
                             |                    |
                             -------- EVC ---------
    
            This MIB module addresses the functional areas of network
            management for EVC, including:
    
                The operational mode for interfaces that are providing
                Ethernet service(s).
    
                The service attributes regarding an interface behaving
                as UNI, such as CE-VLAN mapping and layer 2 control 
                protocol (eg. stp, vtp, cdp) processing.
    
                The provisioning of service instances to define flow 
                points for an Ethernet service.
    
                The operational status of EVCs for notifications
                of status changes, and EVC creation and deletion.
    
            Definition of terms and acronyms:
    
                B-Tag: Backbone Tag field in Ethernet 802.1ah frame
    
                CE: Customer Edge
    
                CE-VLAN: Customer Edge VLAN
    
                CoS: Class Of Service
    
                EVC: Ethernet Virtual Connection
    
                I-SID: Service Instance Identifier field in Ethernet 
                802.1ah frame
    
                MAC: Media Access Control
    
                MEN: Metro Ethernet Network 
    
                NNI: Network to Network Interface
    
                OAM: Operations Administration and Management
    
                PPPoE: Point-to-Point Protocol over Ethernet
    
                Service frame: An Ethernet frame transmitted across the 
                UNI toward the service provider or an Ethernet frame 
                transmitted across the UNI toward the Subscriber.
    
                Service Instance: A flow point of an Ethernet service
    
                Service provider: The organization providing Ethernet
                service(s).
    
                Subscriber: The organization purchasing and/or using 
                Ethernet service(s).
    
                UNI: User Network Interface
                     The physical demarcation point between the 
                     responsibility of the service provider and 
                     the responsibility of the Subscriber.
    
                UNI-C: User Network Interface, subscriber side
    
                UNI-N: User Network Interface, service provider side
    
                VLAN: Virtual Local Area Network"
        REVISION        "200805010000Z"
        DESCRIPTION
            "- Added following enums to cevcSIOperStatus:
            * deleted(4)
            * errorDisabled(5)
            * unknown(6)
    
            - Added following named bits to cevcSIMatchEncapValid:
            * payloadTypes(3)
            * priorityCos(4)
            * dot1qNativeVlan(5)
            * dot1adNativeVlan(6)
            * encapExact(7)
    
            - The Object cevcSIMatchEncapPayloadType is replaced by
            new object cevcSIMatchEncapPayloadTypes to support multiple
            payload types for service instance match criteria.
    
            - Added new object cevcSIMatchEncapPriorityCos to 
            cevcSIMatchEncapTable.
    
            - Added new Compliance ciscoEvcMIBComplianceRev1.
    
            - Added new Object Group cevcSIMatchCriteriaGroupRev1.
    
            - Miscellaneous updates/corrections."
        REVISION        "200712200000Z"
        DESCRIPTION
            "Initial version of this MIB module."
        ::= { ciscoMgmt 613 }
    Module imports
    {'IF-MIB': ['ifIndex', 'InterfaceIndexOrZero'], 'CISCO-TC': ['CiscoCosList'], 'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32', 'Gauge32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['VlanId', 'VlanIdOrNone'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download CISCO-EVC-MIB.mib
    Source location: CISCO-EVC-MIB::ciscoEvcMIB.
    Source version and references

    Archived: 2026-10-19T00:22:15.688226+00:00.

Information from Circitor

ciscoEvcMIB MODULE-IDENTITY
    LAST-UPDATED    "200805010000Z"
    ORGANIZATION    "Cisco Systems, Inc."
    CONTACT-INFO
            "Cisco Systems
            Customer Service

            Postal: 170 W Tasman Drive San Jose, CA  95134
            USA

            Tel: +1 800 553-NETS

            E-mail: cs-ethermibs@cisco.com"
    DESCRIPTION
        "Metro Ethernet services can support a wide range of
        applications and subscriber needs easily, efficiently
        and cost-effectively.  Using standard Ethernet interfaces, 
        subscribers can set up secure, private Ethernet Virtual 
        Connections, to connect their sites together and connect 
        to business partners, suppliers and the Internet.

        This MIB module defines the managed objects and notifications
        describing Ethernet Virtual Connections.

        Ethernet Virtual Connections (EVC), are defined by the Metro
        Ethernet Forum (MEF), as an association between two or more
        UNIs.  Frames within an EVC can only be exchanged among the
        associated UNIs.  Frames sent into the MEN via a particular
        UNI must not be delivered back to the UNI from which it 
        originated.  

        Along an EVC path, there are demarcation flow points on 
        associated ingress and egress interface, of every device, 
        through which the EVC passes.  A service instance represents
        these flow points where a service passes through an interface.  

        From an operational perspective, a service instance serves 
        three purposes: 
            1.  Defines the instance of a particular EVC service on
                a specific interface and identifies all frames that
                belongs to that particular service/flow.
            2.  To provide the capability of applying the configured 
                features to those frames belonging to the service.
            3.  To optionally define how to forward those frames in
                the data-path.  

        The association of a service instance to an EVC depicts
        an instance of an Ethernet flow on a particular interface
        for an end-to-end (UNI-to-UNI) Ethernet service for a 
        subscriber.

        The following diagram illustrates the association of
        EVC, UNIs and service instances.  UNI physical ports
        are depicted as 'U', and service instances as 'x'.

            CE             MEN            MEN            CE
          
          |     |        |     |   ()   |     |        |     |
          |     |
          |     |        |     |   ()   |     |        |     |
          
                         ^                    ^
                         |                    |
                         

        This MIB module addresses the functional areas of network
        management for EVC, including:

            The operational mode for interfaces that are providing
            Ethernet service(s).

            The service attributes regarding an interface behaving
            as UNI, such as CE-VLAN mapping and layer 2 control 
            protocol (eg. stp, vtp, cdp) processing.

            The provisioning of service instances to define flow 
            points for an Ethernet service.

            The operational status of EVCs for notifications
            of status changes, and EVC creation and deletion.

        Definition of terms and acronyms:

            B-Tag: Backbone Tag field in Ethernet 802.1ah frame

            CE: Customer Edge

            CE-VLAN: Customer Edge VLAN

            CoS: Class Of Service

            EVC: Ethernet Virtual Connection

            I-SID: Service Instance Identifier field in Ethernet 
            802.1ah frame

            MAC: Media Access Control

            MEN: Metro Ethernet Network 

            NNI: Network to Network Interface

            OAM: Operations Administration and Management

            PPPoE: Point-to-Point Protocol over Ethernet

            Service frame: An Ethernet frame transmitted across the 
            UNI toward the service provider or an Ethernet frame 
            transmitted across the UNI toward the Subscriber.

            Service Instance: A flow point of an Ethernet service

            Service provider: The organization providing Ethernet
            service(s).

            Subscriber: The organization purchasing and/or using 
            Ethernet service(s).

            UNI: User Network Interface
                 The physical demarcation point between the 
                 responsibility of the service provider and 
                 the responsibility of the Subscriber.

            UNI-C: User Network Interface, subscriber side

            UNI-N: User Network Interface, service provider side

            VLAN: Virtual Local Area Network"
    REVISION        "200805010000Z"
    DESCRIPTION
        "- Added following enums to cevcSIOperStatus:
        * deleted(4)
        * errorDisabled(5)
        * unknown(6)

        - Added following named bits to cevcSIMatchEncapValid:
        * payloadTypes(3)
        * priorityCos(4)
        * dot1qNativeVlan(5)
        * dot1adNativeVlan(6)
        * encapExact(7)

        - The Object cevcSIMatchEncapPayloadType is replaced by
        new object cevcSIMatchEncapPayloadTypes to support multiple
        payload types for service instance match criteria.

        - Added new object cevcSIMatchEncapPriorityCos to 
        cevcSIMatchEncapTable.

        - Added new Compliance ciscoEvcMIBComplianceRev1.

        - Added new Object Group cevcSIMatchCriteriaGroupRev1.

        - Miscellaneous updates/corrections."
    REVISION        "200712200000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 613 }

Information from Cisco SMIv1

Source file: Download CISCO-EVC-MIB-V1SMI.my · Publisher's file

Publisher path: cisco/cisco-mibs/main/v1/CISCO-EVC-MIB-V1SMI.my; 127,451 bytes

Source file: Download CISCO-EVC-MIB-V1SMI.my.txt

File: cisco/CISCO-EVC-MIB-V1SMI.my.txt; 108,114 bytes

ciscoEvcMIB OBJECT IDENTIFIER ::= { ciscoMgmt 613 }

Information from OID Repository

Vendor: Cisco
Module: CISCO-EVC-MIB

[Automatically extracted from oidview.com]

Information from MIBdepot

ciscoEvcMIB MODULE-IDENTITY
    LAST-UPDATED    "200805010000Z"
    ORGANIZATION    "Cisco Systems, Inc."
    CONTACT-INFO
            "Cisco Systems
            Customer Service

            Postal: 170 W Tasman Drive San Jose, CA  95134
            USA

            Tel: +1 800 553-NETS

            E-mail: cs-ethermibs@cisco.com"
    DESCRIPTION
        "Metro Ethernet services can support a wide range of
        applications and subscriber needs easily, efficiently
        and cost-effectively.  Using standard Ethernet interfaces, 
        subscribers can set up secure, private Ethernet Virtual 
        Connections, to connect their sites together and connect 
        to business partners, suppliers and the Internet.

        This MIB module defines the managed objects and notifications
        describing Ethernet Virtual Connections.

        Ethernet Virtual Connections (EVC), are defined by the Metro
        Ethernet Forum (MEF), as an association between two or more
        UNIs.  Frames within an EVC can only be exchanged among the
        associated UNIs.  Frames sent into the MEN via a particular
        UNI must not be delivered back to the UNI from which it 
        originated.  

        Along an EVC path, there are demarcation flow points on 
        associated ingress and egress interface, of every device, 
        through which the EVC passes.  A service instance represents
        these flow points where a service passes through an interface.  

        From an operational perspective, a service instance serves 
        three purposes: 
            1.  Defines the instance of a particular EVC service on
                a specific interface and identifies all frames that
                belongs to that particular service/flow.
            2.  To provide the capability of applying the configured 
                features to those frames belonging to the service.
            3.  To optionally define how to forward those frames in
                the data-path.  

        The association of a service instance to an EVC depicts
        an instance of an Ethernet flow on a particular interface
        for an end-to-end (UNI-to-UNI) Ethernet service for a 
        subscriber.

        The following diagram illustrates the association of
        EVC, UNIs and service instances.  UNI physical ports
        are depicted as 'U', and service instances as 'x'.

            CE             MEN            MEN            CE
          
          |     |        |     |   ()   |     |        |     |
          |     |
          |     |        |     |   ()   |     |        |     |
          
                         ^                    ^
                         |                    |
                         

        This MIB module addresses the functional areas of network
        management for EVC, including:

            The operational mode for interfaces that are providing
            Ethernet service(s).

            The service attributes regarding an interface behaving
            as UNI, such as CE-VLAN mapping and layer 2 control 
            protocol (eg. stp, vtp, cdp) processing.

            The provisioning of service instances to define flow 
            points for an Ethernet service.

            The operational status of EVCs for notifications
            of status changes, and EVC creation and deletion.

        Definition of terms and acronyms:

            B-Tag: Backbone Tag field in Ethernet 802.1ah frame

            CE: Customer Edge

            CE-VLAN: Customer Edge VLAN

            CoS: Class Of Service

            EVC: Ethernet Virtual Connection

            I-SID: Service Instance Identifier field in Ethernet 
            802.1ah frame

            MAC: Media Access Control

            MEN: Metro Ethernet Network 

            NNI: Network to Network Interface

            OAM: Operations Administration and Management

            PPPoE: Point-to-Point Protocol over Ethernet

            Service frame: An Ethernet frame transmitted across the 
            UNI toward the service provider or an Ethernet frame 
            transmitted across the UNI toward the Subscriber.

            Service Instance: A flow point of an Ethernet service

            Service provider: The organization providing Ethernet
            service(s).

            Subscriber: The organization purchasing and/or using 
            Ethernet service(s).

            UNI: User Network Interface
                 The physical demarcation point between the 
                 responsibility of the service provider and 
                 the responsibility of the Subscriber.

            UNI-C: User Network Interface, subscriber side

            UNI-N: User Network Interface, service provider side

            VLAN: Virtual Local Area Network"
    REVISION        "200805010000Z"
    DESCRIPTION
        "- Added following enums to cevcSIOperStatus:
        * deleted(4)
        * errorDisabled(5)
        * unknown(6)

        - Added following named bits to cevcSIMatchEncapValid:
        * payloadTypes(3)
        * priorityCos(4)
        * dot1qNativeVlan(5)
        * dot1adNativeVlan(6)
        * encapExact(7)

        - The Object cevcSIMatchEncapPayloadType is replaced by
        new object cevcSIMatchEncapPayloadTypes to support multiple
        payload types for service instance match criteria.

        - Added new object cevcSIMatchEncapPriorityCos to 
        cevcSIMatchEncapTable.

        - Added new Compliance ciscoEvcMIBComplianceRev1.

        - Added new Object Group cevcSIMatchCriteriaGroupRev1.

        - Miscellaneous updates/corrections."
    REVISION        "200712200000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 613 }

Information from Cisco

ciscoEvcMIB MODULE-IDENTITY
    LAST-UPDATED    "201205210000Z"
    ORGANIZATION    "Cisco Systems, Inc."
    CONTACT-INFO
            "Cisco Systems
            Customer Service

            Postal: 170 W Tasman Drive San Jose, CA  95134
            USA

            Tel: +1 800 553-NETS

            E-mail: cs-ethermibs@cisco.com"
    DESCRIPTION
        "Metro Ethernet services can support a wide range of
        applications and subscriber needs easily, efficiently
        and cost-effectively.  Using standard Ethernet interfaces, 
        subscribers can set up secure, private Ethernet Virtual 
        Connections, to connect their sites together and connect 
        to business partners, suppliers and the Internet.

        This MIB module defines the managed objects and notifications
        describing Ethernet Virtual Connections.

        Ethernet Virtual Connections (EVC), are defined by the Metro
        Ethernet Forum (MEF), as an association between two or more
        UNIs.  Frames within an EVC can only be exchanged among the
        associated UNIs.  Frames sent into the MEN via a particular
        UNI must not be delivered back to the UNI from which it 
        originated.  

        Along an EVC path, there are demarcation flow points on 
        associated ingress and egress interface, of every device, 
        through which the EVC passes.  A service instance represents
        these flow points where a service passes through an interface.  

        From an operational perspective, a service instance serves 
        three purposes: 
            1.  Defines the instance of a particular EVC service on
                a specific interface and identifies all frames that
                belongs to that particular service/flow.
            2.  To provide the capability of applying the configured 
                features to those frames belonging to the service.
            3.  To optionally define how to forward those frames in
                the data-path.  

        The association of a service instance to an EVC depicts
        an instance of an Ethernet flow on a particular interface
        for an end-to-end (UNI-to-UNI) Ethernet service for a 
        subscriber.

        The following diagram illustrates the association of
        EVC, UNIs and service instances.  UNI physical ports
        are depicted as 'U', and service instances as 'x'.

            CE             MEN            MEN            CE
          
          |     |        |     |   ()   |     |        |     |
          |     |
          |     |        |     |   ()   |     |        |     |
          
                         ^                    ^
                         |                    |
                         

        This MIB module addresses the functional areas of network
        management for EVC, including:

            The operational mode for interfaces that are providing
            Ethernet service(s).

            The service attributes regarding an interface behaving
            as UNI, such as CE-VLAN mapping and layer 2 control 
            protocol (eg. stp, vtp, cdp) processing.

            The provisioning of service instances to define flow 
            points for an Ethernet service.

            The operational status of EVCs for notifications
            of status changes, and EVC creation and deletion.

        Definition of terms and acronyms:

            B-Tag: Backbone Tag field in Ethernet 802.1ah frame

            CE: Customer Edge

            CE-VLAN: Customer Edge VLAN

            CoS: Class Of Service

            EVC: Ethernet Virtual Connection

            I-SID: Service Instance Identifier field in Ethernet 
            802.1ah frame

            MAC: Media Access Control

            MEN: Metro Ethernet Network 

            NNI: Network to Network Interface

            OAM: Operations Administration and Management

            PPPoE: Point-to-Point Protocol over Ethernet

            Service frame: An Ethernet frame transmitted across the 
            UNI toward the service provider or an Ethernet frame 
            transmitted across the UNI toward the Subscriber.

            Service Instance: A flow point of an Ethernet service

            Service provider: The organization providing Ethernet
            service(s).

            Subscriber: The organization purchasing and/or using 
            Ethernet service(s).

            UNI: User Network Interface
                 The physical demarcation point between the 
                 responsibility of the service provider and 
                 the responsibility of the Subscriber.

            UNI-C: User Network Interface, subscriber side

            UNI-N: User Network Interface, service provider side

            VLAN: Virtual Local Area Network"
    REVISION        "201205210000Z"
    DESCRIPTION
        "- Added following objects to cevcSITable:
        * cevcSICreationType
        * cevcSIType
        - Added following objects to cevcSIForwardBdTable:
         * cevcSIForwardBdNumberBase
         * cevcSIForwardBdNumber1kBitmap
         * cevcSIForwardBdNumber2kBitmap
         * cevcSIForwardBdNumber3kBitmap
         * cevcSIForwardBdNumber4kBitmap
        - Added MacSecurityViolation OID subtree and following objects:
        * cevcMacAddress
        * cevcMaxMacConfigLimit
        * cevcSIID
        - Deprecated cevcEvcNotificationGroup and added
                cevcEvcNotificationGroupRev1 and added 
                cevcMacSecurityViolationNotification
        - Deprecated cevcSIGroup and added cevcSIGroupRev1
         and added cevcSICreationType and cevcSIType
        - Deprecated cevcSIForwardGroup and added cevcSIForwardGroupRev1
         and added the new objects mentioned in cevcSIForwardBdTable
        - Added CevcMacSecurityViolationCause Textual convention
        - Added new ciscoEvcMIBComplianceRev2"
    REVISION        "200805010000Z"
    DESCRIPTION
        "- Added following enums to cevcSIOperStatus:
        * deleted(4)
        * errorDisabled(5)
        * unknown(6)

        - Added following named bits to cevcSIMatchEncapValid:
        * payloadTypes(3)
        * priorityCos(4)
        * dot1qNativeVlan(5)
        * dot1adNativeVlan(6)
        * encapExact(7)

        - The Object cevcSIMatchEncapPayloadType is replaced by
        new object cevcSIMatchEncapPayloadTypes to support multiple
        payload types for service instance match criteria.

        - Added new object cevcSIMatchEncapPriorityCos to 
        cevcSIMatchEncapTable.

        - Added new Compliance ciscoEvcMIBComplianceRev1.

        - Added new Object Group cevcSIMatchCriteriaGroupRev1.

        - Miscellaneous updates/corrections."
    REVISION        "200712200000Z"
    DESCRIPTION
        "Initial version of this MIB module."
    ::= { ciscoMgmt 613 }

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.613.0 ciscoEvcMIBNotifications15
1.3.6.1.4.1.9.9.613.1 ciscoEvcMIBObjects6128
1.3.6.1.4.1.9.9.613.2 ciscoEvcMIBConformance220

Siblings (706)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.383 ciscoCidsMIB3183 Cisco Intrusion Detection System MIB. Provides
trap definitions for the evAlert and evError
elements of the IDIOM (Intrusion Det…
1.3.6.1.4.1.9.9.384 ciscoDot11AntennaMIB211 This MIB is intended to be implemented on 802.11
Access Points and Wireless Bridges to provide
information about the antennas con…
1.3.6.1.4.1.9.9.385 ciscoUnityMIB3101 The MIB Module for the management of Cisco Unity server.
Cisco Unity is a Unified Communications solution that provides
advanced,…
1.3.6.1.4.1.9.9.386 ciscoModuleAutoShutdownMIB336 The CISCO-MODULE-AUTO-SHUTDOWN-MIB is used to configure
the module automatic shutdown feature. Modules will be
reset by the syste…
1.3.6.1.4.1.9.9.387 ciscoNetflowMIB3206 The Netflow MIB provides a simple and easy method
to get NetFlow cache information, current NetFlow
configuration and statistics.…
1.3.6.1.4.1.9.9.388 ciscoVirtualSwitchMIB3128 This MIB module defines the managed objects that support the
virtual switch architecture.

The virtual switch concept combines sev…
1.3.6.1.4.1.9.9.389 ciscoVoiceCasModuleMIB322 This MIB is used to support Programmable
CAS signaling Bit configuration on modules
that support voice traffic.

This MIB will enab…
1.3.6.1.4.1.9.9.390 ciscoCableDiagMIB333 This MIB module defines objects for managing cable
diagnostic test capabilites supported by the Cisco devices.

Cable diagnostic t…
1.3.6.1.4.1.9.9.391 ciscoFcspMIB346 MIB module for managing Fibre Channel Security for the
fibre channel devices.

This MIB is used to configure and monitor the
Fibre-…
1.3.6.1.4.1.9.9.392 ciscoRemoteAccessMonitorMIB3200 Acronyms and Definitions
The following acronyms and terms are used in this
document:

IPSec: Secure IP Protocol

VPN: Virtual Priv…
1.3.6.1.4.1.9.9.393 ciscoVoiceConnectivityMIB344 This MIB module provides connectivity related
information for devices (e.g., 'connectivity between
voice gateway, phones, gatekee…
1.3.6.1.4.1.9.9.394 ciscoIpTapMIB328 This module manages Cisco's intercept feature for IP.

This MIB is used along with CISCO-TAP2-MIB to
intercept IP traffic. CISCO-T…
1.3.6.1.4.1.9.9.395 cisco802TapMIB320 This module manages Cisco's intercept feature for
802 (layer 2) streams.

This MIB is used along with CISCO-TAP2-MIB to
intercept 8…
1.3.6.1.4.1.9.9.396 ciscoMlrMIB3190 The MIB for providing information about Multi-layer
Routing(MLR). This MIB will provide information used to
control and measure S…
1.3.6.1.4.1.9.9.397 ciscoH225MIB1176 Cisco H225 MIB module. This module consists of H225
call signaling and H225 RAS (Registration, Admission
and Status). These are p…
1.3.6.1.4.1.9.9.398 ciscoMauExtMIB323 A MIB module for extending the MAU-MIB (RFC 3636)
to add objects which provide additional management
information about MAU or Jac…
1.3.6.1.4.1.9.9.399 ciscoTap2MIB369 This module manages Cisco's intercept feature.
This MIB replaces CISCO-TAP-MIB. This MIB defines
a generic stream table that cont…
1.3.6.1.4.1.9.9.400 ciscoUserConnectionTapMIB213 This module manages Cisco's intercept feature for
user connections.

This MIB is used along with CISCO-TAP2-MIB to
intercept user t…
1.3.6.1.4.1.9.9.401 ciscoBridgeExtMIB334 A MIB module for extending BRIDGE-MIB specified in RFC 1493.
1.3.6.1.4.1.9.9.402 ciscoPowerEthernetExtMIB383 A MIB module for extending the POWER-ETHERNET-MIB
(RFC3621) to add objects which provide additional
management information about …
1.3.6.1.4.1.9.9.405 ciscoDnsServerMIB3408 The MIB module for entities implementing the server side
of the Domain Name System (DNS) protocol.
P. Mockapetris, 'Domain names …
1.3.6.1.4.1.9.9.407 ciscoAtmTrunkStatMIB3101 The MIB module contains ATM Trunk statistics.

TERMINOLOGY

PVC: Permanent Virtual Circuit
OAM: Operation and Management
CRC: Cyclic…
1.3.6.1.4.1.9.9.408 ciscoSnmpNotificationExtMIB313 This MIB extends the functionality provided
by SNMP-NOTIFICATION-MIB.
This MIB provides for the aging of the
notification filters …
1.3.6.1.4.1.9.9.409 ciscoSnmpVacmExtMIB211 The management information definitions to extend
the View-based Access Control Model (RFC3415) for
SNMP.

This MIB extends the 'SN…
1.3.6.1.4.1.9.9.411 ciscoVlanTranslationMIB327 The MIB module for the management of VLAN translations.

VLAN translation refers to the ability of the device
to translate between…
1.3.6.1.4.1.9.9.412 ciscoSnmpTargetExtMIB230 This MIB is an extension of the SNMP-TARGET-MIB
specified in RFC3413.

This MIB module contains Cisco-defined extension
to the sn…
1.3.6.1.4.1.9.9.413 ciscoDot11SsidSecMIB271 This MIB module provides network management
support for Cisco IEEE 802.11 Wireless LAN
devices association and authentication.

ACR…
1.3.6.1.4.1.9.9.414 ciscoPoePdMIB317 This MIB is intended for devices powered by
external power sources, in particular Power
Over Ethernet (PoE or formerly called inl…
1.3.6.1.4.1.9.9.415 ciscoWlanManMIB313 This MIB module provides network management
and configuration support for IEEE 802.11
Wireless LAN devices.

ACRONYMS

HTTP
Hypertext …
1.3.6.1.4.1.9.9.416 ciscoDot11QosMIB349 This MIB module provides network management
support for QoS on wireless LAN devices. The
objects defined in this MIB provide equ…
1.3.6.1.4.1.9.9.420 ciscoUnityExpressMIB3179 The MIB Module for the management of the Cisco Unity
Express (CUE) service. CUE is a voicemail service that
runs in a Cisco rout…
1.3.6.1.4.1.9.9.421 ciscoDpvmMIB355 The MIB module for the management of the
Dynamic Port Vsan Membership (DPVM) module.
DPVM provides the ability to assign (virtual
…
1.3.6.1.4.1.9.9.422 ciscoIPsecTc00 This MIB module defines the textual conventions
used in the IPsec suite of MIBs. This includes
Internet DOI numbers defined in RF…
1.3.6.1.4.1.9.9.423 ciscoIkeConfigMIB393 This is a MIB Module for configuring and viewing IKE
parameters and policies.

Acronyms
The following acronyms are used in this do…
1.3.6.1.4.1.9.9.424 ciscoCableMeteringMIB353 This is the MIB module for Usage Based Metering for the
DOCSIS-compliant Cable Modem Termination Systems (CMTS).

Usage Based Mete…
1.3.6.1.4.1.9.9.426 ciscoLinkErrorMonitorMIB334 The MIB module for managing Link Error Monitoring
Feature on devices.

Link Error Monitoring Feature provides a mechanism
to monito…
1.3.6.1.4.1.9.9.427 ciscoZsExtMIB333 The MIB module for the management of zoning within
the framework of Cisco's Zoning Server (ZS) Archi-
tecture which realizes the …
1.3.6.1.4.1.9.9.428 ciscoIkeFlowExtMIB318 This MIB module is an extension to
CISCO-IKE-FLOW-MIB and contains Cisco Specific
extensions for monitoring IKE.

It is for monito…
1.3.6.1.4.1.9.9.429 ciscoIkeFlowMIB380 This is a MIB module for monitoring the structures
and status of IPsec control flows based on Internet
Key Exchange protocol. The…
1.3.6.1.4.1.9.9.430 ciscoFcDeviceAliasMIB314 The MIB module for the management of Device
Aliases in a Fibre Channel Fabric. A Fibre
Channel fabric consists of devices such as
…
1.3.6.1.4.1.9.9.431 ciscoIPsecProvisioningMIB398 IPSec is the next-generation network layer crypto
framework described in RFC2401-2411.
This MIB defines the IPsec configurations.
…
1.3.6.1.4.1.9.9.432 ciscoEnhancedIpsecFlowMIB3330 This is a MIB Module for monitoring the structures
and status of IPSec-based networks. The MIB has been
designed to be adopted as…
1.3.6.1.4.1.9.9.433 ciscoCFSMIB3102 This MIB applies to one or more of a set of devices
which have connectivity through some kind of 'fabric'.
Many features which ru…
1.3.6.1.4.1.9.9.434 ciscoIpNetworkDiscoveryMIB, ciscoIsnsIpNetDiscoveryMIB358 MIB to provide the information about the disjoint
IP networks connected to the various gigabit ethernet
interfaces in the 'Fabric…
1.3.6.1.4.1.9.9.435 ciscoFcMulticastMIB314 MIB module for monitoring and configuring
Fibre Channel Multicast feature.
1.3.6.1.4.1.9.9.436 ciscoDNSClientMIB328 The MIB module for entities implementing the client
side of the Domain Name System (DNS) protocol.
1.3.6.1.4.1.9.9.437 ciscoPortTrackMIB218 A MIB to configure the Port-Track feature.

When a link goes down, all the services which depend
on the link are notified of the o…
1.3.6.1.4.1.9.9.438 ciscoIPsecSignalingMIB3140 This MIB Module models status, performance and failures
of a protocol with the generic characteristics of signalling
protocols us…
1.3.6.1.4.1.9.9.439 ciscoCcmeMIB3338 This MIB allows management of Cisco CallManager Express
(CCME) feature in Cisco IOS. CCME is optional software
feature that enabl…
1.3.6.1.4.1.9.9.441 ciscoSrstMIB3149 This MIB allows management of Cisco Survivable Remote
Site Telephony (SRST) feature in Cisco IOS. SRST is
an optional software fe…