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.743 ciscoCdstvCsStatsMIB383 This MIB module defines objects describing the caching and
streaming statistics objects that facilitate the management of
the Cis…
1.3.6.1.4.1.9.9.744 ciscoIpslaVideoMIB373 IP SLA is a capability which utilizes active monitoring for
network performance. It can be used for network
troubleshooting, net…
1.3.6.1.4.1.9.9.745 ciscoEntitySensorExtMIB321 This MIB is extension to ENTITY-SENSOR-MIB(RFC 3433). This MIB
also defines the notifications applicable for sensors reported
in …
1.3.6.1.4.1.9.9.747 ciscoEntityStateExtMIB322
1.3.6.1.4.1.9.9.748 ciscoIpAddressPoolMIB396 This MIB modules defines objects that describe common aspects
of IP address pools.

IP Address Pool Manager
=======================
…
1.3.6.1.4.1.9.9.749 ciscoCdstvBwmgrMIB321 This MIB module defines Bandwidth Manager configuration objects
that facilitate the management of the Cisco Content Delivery
Syst…
1.3.6.1.4.1.9.9.750 ciscoCdstvIngestTuningMIB318 This MIB module defines ingest tuning configuration objects
that facilitate the management of the Cisco Content Delivery
System f…
1.3.6.1.4.1.9.9.751 ciscoCdstvAuthmgrMIB325 This MIB module defines objects that describe the configuration
of the authentication manager for the Cisco Content Delivery
Syst…
1.3.6.1.4.1.9.9.753 ciscoVideoSessionMIB3145 This MIB module complements the CISCO-VOICE-DIAL-CONTROL-MIB,
which provides voice telephony peer information, by providing
manag…
1.3.6.1.4.1.9.9.754 ciscoCdstvServerMIB382 This MIB module defines server configuration that
faciliate the management of the Cisco Content Delivery System
for TV (CDS-TV) …
1.3.6.1.4.1.9.9.755 ciscoCdstvIsaMIB3145 This MIB module defines ISA configuration objects that
faciliate the management of the Cisco Content Delivery System
for TV (CDS-…
1.3.6.1.4.1.9.9.756 ciscoEntityPerformanceMIB356 This MIB module defines managed objects that facilitate to
monitor performance of any physical entity, which are listed in
the EN…
1.3.6.1.4.1.9.9.757 ciscoSbcStatsMIB3106 The main purpose of this MIB is to define the statistics
information for Session Border Controller application. This MIB
categori…
1.3.6.1.4.1.9.9.758 ciscoTelepresenceExchangeSystemMIB3173 The main purpose of this MIB is to provide product
component level configuration, status, statistics,
events, and alarm notificat…
1.3.6.1.4.1.9.9.759 ciscoGdoiMIB3213 This MIB module defines objects for managing the GDOI protocol.

Copyright (c) The IETF Trust (2010). This version of this MIB
mo…
1.3.6.1.4.1.9.9.760 ciscoPtpMIB3198 The MIB module for PTPv2 (IEEE1588 - 2008)

Overview of PTPv2 (IEEE 1588-2008)

This IEEE standard defines a protocol enabling prec…
1.3.6.1.4.1.9.9.761 ciscoNetsyncMIB3104 The Synchronous Ethernet (SyncE) MIB is defined
for monitoring network synchronization based on
ITU-T G.781 clock selection.

Sync…
1.3.6.1.4.1.9.9.762 ciscoWanOptimizationMIB3302 This MIB is for managing Wide Area Network (WAN) Optimization
systems. The objective of WAN optimization system is to reduce
as m…
1.3.6.1.4.1.9.9.763 ciscoVideoTc00 This MIB module defines a collection of common video-related
textual conventions to be used in Cisco MIBS for video-capable
produ…
1.3.6.1.4.1.9.9.764 ciscoUbeMIB212 This MIB describes objects used for managing Cisco
Unified Border Element (CUBE).

The Cisco Unified Border Element (CUBE) is a Ci…
1.3.6.1.4.1.9.9.765 ciscoFlowCloneMIB344 This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software en…
1.3.6.1.4.1.9.9.766 ciscoIpslaVideoProfileMIB329 IP SLA is a capability which utilizes active monitoring for
network performance. It can be used for network
troubleshooting, net…
1.3.6.1.4.1.9.9.767 ciscoLwappDot11ClientRmMIB364 This MIB is intended to be implemented on all those
devices operating as Central controllers, that
terminate the Light Weight Acc…
1.3.6.1.4.1.9.9.768 ciscoEntitySensorHistoryMIB220 This MIB module defines objects that describe collections and
measurement information for each sensor supporting historical
data …
1.3.6.1.4.1.9.9.769 ciscoMediaQualityMIB3214 This MIB module enhances the DIAL-CONTROL-MIB
(RFC2128) by providing call information and voice
and video quality statistics of c…
1.3.6.1.4.1.9.9.770 ciscoTcpMetricsMIB422 This MIB module defines objects that describe the quality
metrics of TCP streams.

GLOSSARY
============

Flow Monitor - a hardware o…
1.3.6.1.4.1.9.9.771 ciscoMediaMetricsMIB438 This MIB module defines objects that describe the quality
metrics of Media streams.

GLOSSARY
============

Flow Monitor - a hardware…
1.3.6.1.4.1.9.9.772 ciscoPfrMIB3303 This MIB module defines objects that describe Performance
Routing (PfR). Standard routing protocols base routing
decisions on re…
1.3.6.1.4.1.9.9.773 ciscoSwitchRateLimiterMIB328 This MIB module defines management objects for the
Switch Rate Limiter features on Cisco Layer 2 and
Layer 3 devices.

Rate limits …
1.3.6.1.4.1.9.9.774 ciscoVdcMIB390 CISCO-VDC-MIB
1.3.6.1.4.1.9.9.775 ciscoSelectiveVrfDownloadMIB341 This MIB module defines objects describing selective
VRF download. The selective VRF download feature makes
a best effort to dow…
1.3.6.1.4.1.9.9.776 ciscoNetflowLiteMIB356 This MIB provides a method to configure Netflow-lite feature
and get information in these areas:

1. Exporter config information a…
1.3.6.1.4.1.9.9.777 ciscoDsgIfExtMIB315 A MIB module for extending the DSG-IF-MIB (ITU-T J.128
10/2008) to add objects which provide additional
management information ab…
1.3.6.1.4.1.9.9.778 ciscoLwappRFMIB3143
1.3.6.1.4.1.9.9.779 ciscoPmonMIB314 ciscoPmonMIB MODULE-IDENTITY
LAST-UPDATED "201201030000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Custom…
1.3.6.1.4.1.9.9.782 ciscoSubscriberIdentityTcMIB00 This MIB module defines textual conventions describing
subscriber session identities. A subscriber session identity
consists of …
1.3.6.1.4.1.9.9.783 ciscoDynamicTemplateTcMIB00 This MIB module defines textual conventions used by the
CISCO-DYNAMIC-TEMPLATE-MIB and MIB modules that use and expand
on dynamic…
1.3.6.1.4.1.9.9.784 ciscoDynamicTemplateMIB3152 This MIB defines objects that describe dynamic templates. A
dynamic template is a set of configuration attributes that a
system …
1.3.6.1.4.1.9.9.785 ciscoSubscriberSessionTcMIB00 This MIB module defines textual conventions describing
subscriber sessions.
1.3.6.1.4.1.9.9.786 ciscoSubscriberSessionMIB3187 This MIB defines objects describing subscriber sessions, or
more specifically, subscriber sessions terminated by a RAS. A
subscr…
1.3.6.1.4.1.9.9.789 ciscoFlowMetadataMIB330 The MIB module for managing Cisco medianet flow metadata.
Metadata, in the simplest form, is data that qualifies
other data. Flow…
1.3.6.1.4.1.9.9.790 ciscoSwitchCefMIB333 This MIB module defines management objects for the
CEF features on Cisco Layer 2 and Layer 3 devices.

Definition of some of the t…
1.3.6.1.4.1.9.9.791 ciscoAppNavMIB251 ciscoAppNavMIB MODULE-IDENTITY
LAST-UPDATED "201206070000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Cust…
1.3.6.1.4.1.9.9.792 ciscoLwappDhcpMIB354
1.3.6.1.4.1.9.9.793 ciscoMspMIB354 Objective of media services proxy is to provide media services
to end-points and its flows identified by a set of
protocols. Medi…
1.3.6.1.4.1.9.9.798 ciscoLocalAuthUserMIB340 This MIB module defines objects describing users
authenticated locally by a Network Access Server (NAS).

+
| | | …
1.3.6.1.4.1.9.9.800 ciscoMediatraceMIB3191 Mediatrace helps to isolate and troubleshoot network
degradation problems by enabling a network administrator
to discover an Inte…
1.3.6.1.4.1.9.9.801 ciscoFabricPathTopologyMIB340 This MIB module defines managed objects that facilitate
the management of Cisco's FabricPath Topology technology.
1.3.6.1.4.1.9.9.803 ciscoSwitchFabricMIB330 This MIB module defined managed objects that
facilitates the management of switching fabric
information in a Cisco switch.
1.3.6.1.4.1.9.9.804 ciscoHardwareIpVerifyMIB313 This MIB module defines management objects for
configuration and monitoring of the Intrusion
Detection System (IDS) that checks f…