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.249 ciscoEnhancedImageMIB244 Initial version of the MIB. This MIB has Image table
containing the following information related to the
running IOS image
1. Enti…
1.3.6.1.4.1.9.9.252 cTapMIB380 This module manages Cisco's intercept feature.
1.3.6.1.4.1.9.9.253 ciscoItpXuaMIB3250 The MIB for MTP3 User Adaptation (M3UA) and SCCP User
Adaptation (SUA) for Cisco's IP Transfer Point (ITP)
implementation.

The Cis…
1.3.6.1.4.1.9.9.254 ciscoSlbExtMIB3425 The extended MIB for managing Server Load Balancing
Manager(s). This MIB extends the SLB management
functionality in the CISCO-SL…
1.3.6.1.4.1.9.9.255 ciscoFabricMcastMIB330 Fabric Multicast Resource MIB module.
This MIB module is used for managing/tracking the fabric
multicast resource related informa…
1.3.6.1.4.1.9.9.256 ciscoFabricMcastApplMIB316 Fabric multicast resource MIB module.
This MIB module is used for managing/tracking the fabric
multicast resource application rel…
1.3.6.1.4.1.9.9.257 ciscoFabricHfrMIB390 Cisco Enhanced Benes fabric MIB module.
This MIB module is used for managing/tracking the Ehanced
Benes Fabric entities and/or fa…
1.3.6.1.4.1.9.9.259 ciscoPsaMicrocodeMIB324 Cisco PSA Microcode MIB - Overview

The PSA is the Packet Switching ASIC used
in module like engine 2(E2) line cards in GSR
for IP …
1.3.6.1.4.1.9.9.260 ciscoSsgMIB3218 The MIB Module manages Service Selection Gateway(SSG)
devices.

Service Selection Gateway(SSG) is a switching solution
for service…
1.3.6.1.4.1.9.9.261 ciscoPtopoExtnMIB218 This MIB module contains extensions to the PTOPO-MIB that
provide support to distinguish between bidirectional and
unidirectional…
1.3.6.1.4.1.9.9.262 ciscoVoaMIB214 This MIB module defines objects to configure and manage the
Variable Optical Attenuator (VOA) modules.

VOA modules are typically …
1.3.6.1.4.1.9.9.263 ciscoIgmpSnoopingMIB3286 The MIB module for IGMP Snooping feature.

Internet Group Management Protocol (IGMP) is the protocol used
by IPv4 end hosts to ind…
1.3.6.1.4.1.9.9.264 ciscoOpticalMonitorMIB372 This MIB module defines objects to monitor optical
characteristics and set corresponding thresholds on the
optical interfaces in …
1.3.6.1.4.1.9.9.265 ciscoEntityPfeMib358 The Packet Forwarding Engine technology are Cisco developed
Network Processors, which accelerates certain features in
order to pr…
1.3.6.1.4.1.9.9.268 ciscoWlanVlanMIB341 This MIB module provides network management
support for device VLAN configuration on
IEEE 802.11 wireless LAN.

ACRONYMS
AES
Advanced…
1.3.6.1.4.1.9.9.269 ciscoTBridgeDevIfMIB220 This MIB module provides network management support
for configuration and status information of devices
supporting transparent br…
1.3.6.1.4.1.9.9.270 ciscoSyslogEventExtMIB221 This MIB module extends the Cisco Syslog
MIB and provides network management support
to handle and process Syslog messages as
devi…
1.3.6.1.4.1.9.9.271 ciscoL2DevMonMIB324 This MIB module is for monitoring of active
layer 2 devices by hot standby layer 2 devices
and the configuration of hot standby s…
1.3.6.1.4.1.9.9.272 ciscoDot11IfMIB3212 This MIB module provides network management
support for Cisco IEEE 802.11 Wireless LAN
type device (Access Point) radio interface…
1.3.6.1.4.1.9.9.273 ciscoDot11AssociationMIB2107 This MIB module provides network management
information on IEEE 802.11 wireless device
association management and data packet for…
1.3.6.1.4.1.9.9.275 ciscoBcpMIB225 This MIB module describes the Managed Objects for
of Bridge Control Protocol (RFC2878). This MIB is
influenced by RFC1474.
1.3.6.1.4.1.9.9.276 ciscoIfExtensionMIB3147 A MIB module for extending the IF-MIB (RFC2863)
to add objects which provide additional information
about interfaces not availabl…
1.3.6.1.4.1.9.9.277 ciscoDdpIappMIB322 This MIB module describes the management support for
the Inter-Access Point Protocol (IAPP). IAPP is a
Cisco propriety Data Deli…
1.3.6.1.4.1.9.9.278 ciscoIpProtocolMIB363 The MIB module is for management of information
to support packet filtering on IP protocols.

The cippfIpProfileTable allows users…
1.3.6.1.4.1.9.9.279 ciscoAtmQosMIB367 The MIB is created to provide ATM QoS information in
these areas:

1. Traffic shaping on a per-VC basis
2. Traffic shaping on a pe…
1.3.6.1.4.1.9.9.280 ciscoOutageMIB375 This MIB module describes, stores, and reports outage
related information generated by individual hardware
and software component…
1.3.6.1.4.1.9.9.281 ciscoFabricC12kMIB3135 Cisco Fabric MIB module for c12000 series of routers.
This MIB module is used for managing/tracking the c12000
fabric entities an…
1.3.6.1.4.1.9.9.282 ciscoVsanMIB2104 The MIB module for the management of the Virtual Storage
Networks (VSANs) within the frame work of Cisco's VSAN
Architecture. T…
1.3.6.1.4.1.9.9.284 ciscoFcRouteMIB255 The MIB module for configuring and displaying FC (Fibre
Channel) Route Information.
1.3.6.1.4.1.9.9.285 ciscoPortChannelMIB243 The MIB module for management of Port Channel ports.
In addition to this MIB, CISCO-FC-FE-MIB and interface
mib (rfc2863) will al…
1.3.6.1.4.1.9.9.286 ciscoWwnmgrMIB238 The World Wide Name (WWN) in the fibre channel networking
technology is equivalent to the MAC address in Ethernet.
There are six …
1.3.6.1.4.1.9.9.287 ciscoFspfMIB495 Fabric Shortest Path First (FSPF) MIB.
1.3.6.1.4.1.9.9.288 ciscoRadiusMIB396 MIB module for monitoring and configuring
authentication and logging services using RADIUS
(Remote Authentication Dial In User Se…
1.3.6.1.4.1.9.9.289 ciscoFcFeMIB2352 This is the Cisco fibre element management MIB module.
It covers:
- Cisco extension to the interface MIB ( IF-MIB )
- Contains all…
1.3.6.1.4.1.9.9.290 ciscoVirtualNwIfMIB222 The MIB module for management of virtual network
interfaces to VSAN and VLAN.
1.3.6.1.4.1.9.9.292 ciscoRscnMIB267 The MIB module for the management of the Fibre
Channel's Registered State Change Notification
(RSCN) functionality, which is spec…
1.3.6.1.4.1.9.9.293 ciscoNsMIB267 The MIB module for the management of the Cisco
Name Server which realizes the FC-GS3
requirements for Name Server (NS).
1.3.6.1.4.1.9.9.294 ciscoZsMIB2271 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.295 ciscoFcPingMIB237 The MIB module for the management of the
Fibre Channel Ping functionality.
1.3.6.1.4.1.9.9.296 ciscoFcTraceRouteMIB231 The MIB module for the management of the
Fibre Channel Trace Route functionality.
1.3.6.1.4.1.9.9.297 ciscoFcsMIB2122 The MIB module for the management of a Fabric
Configuration Server (FCS). An FCS is defined
by the FC-GS3 standard. This MIB ena…
1.3.6.1.4.1.9.9.299 ciscoExtScsiMIB268 The Cisco extension to CISCO-SCSI-MIB
which is a copy of the Internet draft,
the SCSI-MIB, from the IETF.

Glossary of terms used i…
1.3.6.1.4.1.9.9.300 ciscoCallHomeMIB3327 The MIB module for the management of Call Home feature
within the framework of Cisco's Call Home architecture.
Customers deployin…
1.3.6.1.4.1.9.9.301 ciscoSyslogExtMIB244 MIB module for configuring and monitoring System Log
related management parameters as defined by RFC 3164.
1.3.6.1.4.1.9.9.302 ciscoDmMIB288 The MIB module for the domain management functionality
defined by the Fibre Channel standards (FC-SW2). For the
purposes of this …
1.3.6.1.4.1.9.9.305 ciscoSystemExtMIB3113 MIB module for monitoring High Availability, SNMP SET
errors and bandwidths. This mib module also provides the
information on co…
1.3.6.1.4.1.9.9.309 ciscoIPIfMIB340 The MIB module for configuring IP characteristics
of the interfaces of a device.
1.3.6.1.4.1.9.9.311 ciscoEpmNotificationMIB348 Notifications directly from hardware and software and processed
notifications from various management applications can be furthe…
1.3.6.1.4.1.9.9.312 ciscoDataCollectionMIB384 The MIB module allows a management application to
select a set of MIB object instances whose values need
to be collected on a per…
1.3.6.1.4.1.9.9.313 ciscoL2ControlMIB3113 The CISCO-L2-CONTROL-MIB is used to control some layer 2
functions, including MAC limit function and unicast
flooding. This devi…