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.181 ciscoWirelessLinkMetricsMIB4141 This is the MIB Module for the Cisco Wireless Radio
Point to MultiPoint interface link metrics
specification.

Glossary

The followin…
1.3.6.1.4.1.9.9.183 ciscoGprsAccPtMIB3338 This MIB module supports access point configuration
for GGSN in a GPRS system. GPRS [1] is a GSM network
providing mobile wireles…
1.3.6.1.4.1.9.9.184 ciscoPimMIB336 This MIB module defines the cisco specific variables
for Protocol Independent Multicast (PIM) management.
These definitions are a…
1.3.6.1.4.1.9.9.185 ciscoBertMIB246 The MIB module to configure and perform Bit Error Rate Testing
(BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces.
Bit error rate…
1.3.6.1.4.1.9.9.187 ciscoBgp4MIB4170 An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Proto…
1.3.6.1.4.1.9.9.188 cGtpMIB3248 This MIB module manages the GPRS Tunnelling Protocol
(GTP) on GGSN and SGSN.

GPRS provides wireless access to packet data network…
1.3.6.1.4.1.9.9.189 ciscoPortQosMIB3114 Cisco PORT QOS MIB - Overview

This MIB module is for the management of Cisco's
per port rate-limiting and traffic shaping on L3
sw…
1.3.6.1.4.1.9.9.190 ciscoVoiceAppsMIB340 The MIB Module for the management of Cisco Voice
Applications. This MIB is designed to work in
conjunction with the SYSAPPL-MIB …
1.3.6.1.4.1.9.9.191 ciscoIpUplinkRedirectMIB311 This MIB module is for the configuration of
Cisco IP Uplink Redirect feature.
1.3.6.1.4.1.9.9.192 ciscoGprsChargingMIB3315 This MIB module manages the charging related
function on the GGSN node of a GPRS system.

The following diagram illustrates a simp…
1.3.6.1.4.1.9.9.194 ciscoPppoeMIB389 Cisco PPPoE sessions management MIB Module.
1.3.6.1.4.1.9.9.195 ciscoEntityExtMIB370 This MIB is an extension of the ENTITY-MIB
specified in RFC2737.

This MIB module contains Cisco-defined extensions
to the entit…
1.3.6.1.4.1.9.9.197 ciscoDistDirMIB3123 Cisco Distributed Director MIB.

The Cisco Distributed Director provides global Internet
scalability and increased performance as …
1.3.6.1.4.1.9.9.198 ciscoRfSupMIB365 This MIB was designed to complement the CISCO-RF-MIB by
providing additional optional status and configuration control
for redund…
1.3.6.1.4.1.9.9.199 ciscoSmFileDownloadMIB323 The MIB module for downloading files to the Service
Modules specifically designed for an architecture
containing a controller car…
1.3.6.1.4.1.9.9.201 ciscoSwitchUsageMIB315 This MIB defines objects related to statistics
for the usage of switch fabric. The switch fabric
is used by the incoming packets …
1.3.6.1.4.1.9.9.202 ciscoOscpMIB352 The MIB module for managing the Cisco Optical
Supervisory Channel Protocol (OSCP). The OSCP is used
to determine and maintain wav…
1.3.6.1.4.1.9.9.204 ciscoXdslLineMIB232 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
different t…
1.3.6.1.4.1.9.9.215 ciscoMacNotificationMIB372 This MIB module is for configuration of the MAC notification
feature. MAC notification is a mechanism to inform monitoring
device…
1.3.6.1.4.1.9.9.216 ciscoContentNetworkMIB334 This MIB module defines objects for Content Network devices.

A Content Network is a collection of devices that optimizes the
deli…
1.3.6.1.4.1.9.9.217 ciscoCat6kCrossbarMIB3210 The Catalyst 6000 Crossbar MIB provides instrumentation for
configuration and operation of the crossbar switching fabric
module, …
1.3.6.1.4.1.9.9.218 ciscoIfThresholdMIB365 ciscoIfthresholdMIB
1.3.6.1.4.1.9.9.219 ciscoVoiceDnisMIB324 The MIB module provides management support for Dialer
Number Information Service (DNIS) mapping. A DNIS
entry is associated with…
1.3.6.1.4.1.9.9.220 ciscoPaeMIB3231 Cisco Port Access Entity (PAE) module for managing
IEEE Std 802.1x.

This MIB provides Port Access Entity information
that are eith…
1.3.6.1.4.1.9.9.221 ciscoEnhancedMemPoolMIB387 New MIB module for monitoring the memory pools
of all physical entities on a managed system.
1.3.6.1.4.1.9.9.222 ciscoEnhancedWredMIB370 Cisco WRED MIB - Overview
Cisco Weighted Random Early Detection/Drop (WRED)
is a method which avoids traffic congestion on an
outp…
1.3.6.1.4.1.9.9.223 ciscoWanNcdpMIB358 This MIB module is intended for the management of network clock
distribution and the Network Clock Distribution Protocol (NCDP)
i…
1.3.6.1.4.1.9.9.224 ciscoDevExcepReportMIB329 This mib defines the SNMP objects to report
exceptions to north-bound NMS.

The devices implementing this MIB monitor
the status of…
1.3.6.1.4.1.9.9.225 ciscoLagMIB356 Cisco Link Aggregation module for managing IEEE Std
802.3ad.

This MIB provides Link Aggregation information that are
either exclud…
1.3.6.1.4.1.9.9.226 ciscoNDEMIB417 The Netflow Data Export (NDE) MIB provides instrumentation for
configuration and operation of the Netflow Data Export feature.

A …
1.3.6.1.4.1.9.9.227 ciscoItpAclMIB345 The MIB for managing access lists that control
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP Trans…
1.3.6.1.4.1.9.9.228 ciscoItpRtMIB347 This MIB is for managing information required to
route messages transported over Signalling System
No. 7 (SS7) Network via Cisco …
1.3.6.1.4.1.9.9.229 ciscoDs1ExtMIB2129 The MIB module to describe DS1/E1 interface objects. This is
an extension to the standard DS1/E1 MIB (RFC 2495).

Unless mentioned…
1.3.6.1.4.1.9.9.230 ciscoItpActMIB329 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signalling System No. 7(SS7) Network.
This…
1.3.6.1.4.1.9.9.231 ciscoItpTextualConventions00 The defines textual conventions used by to manage
devices related to the SS7 network. The
relevant ITU documents describing this…
1.3.6.1.4.1.9.9.232 ciscoItpSpMIB3384 The MIB for managing Signalling Points and its
associated messages transported over Signalling
System No. 7 (SS7) Network via Ci…
1.3.6.1.4.1.9.9.233 ciscoItpSccpMIB3194 The MIB for Signaling Connection Control Part(SCCP)
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP …
1.3.6.1.4.1.9.9.234 ciscoWanTopologyMIB383 A management station can use this MIB module for the
maintenance of persistent topology information of the
PNNI network. Previous…
1.3.6.1.4.1.9.9.235 ciscoImaMIB260 The MIB module describes Cisco IMA objects.
This is an extension to the standard of
ATM Forum IMA version 1.1, AF-PHY-0086.001
Spe…
1.3.6.1.4.1.9.9.236 ciscoWanSctMgmtMIB218 MIB module to manage SCT files in a node.

SCTs (Service Class Templates) are nodal configuration files,
which define the traffic …
1.3.6.1.4.1.9.9.237 ciscoNmsApplHealthMIB339 This MIB defines Cisco NMS Application (cna) Health
Status Notifications and the related objects. These
notifications will be sen…
1.3.6.1.4.1.9.9.238 ciscoIGMPFilterMIB245 IGMP Filter configuration MIB. This MIB provides a
mechanism for users to configure the system to intercept
IGMP joins for IP Mul…
1.3.6.1.4.1.9.9.240 cGgsnMIB3389 This MIB module manages the Gateway GPRS Support
Node (GGSN) devices.

A GGSN device provides interworking with external
packet-dat…
1.3.6.1.4.1.9.9.241 cggsnQosMIB289 This MIB module manages the Quality of Service
parameters of GGSN in a GPRS system.

GGSN is the Gateway GPRS Support Node in the …
1.3.6.1.4.1.9.9.242 ciscoCableAvailabilityMIB360 This is the MIB module for management of Hot Standby
Connection to Connection Protocol (HCCP) features. HCCP is
a Cisco proprieta…
1.3.6.1.4.1.9.9.243 ciscoHealthMonitorMIB322 Health Monitor MIB module.

The Health Monitor uses a model based on events of varying
severity and frequency, and predefined rule…
1.3.6.1.4.1.9.9.244 ciscoNbarProtocolDiscoveryMIB384 Cisco NBAR Protocol Discovery MIB

NBAR - Network Based Application Recognition is
an intelligent classification engine that reco…
1.3.6.1.4.1.9.9.245 ciscoGtpDirectorMIB335 This MIB module defines objects that are used to
manage GTP Director Module.

In the GPRS network, the APN is the identifier that
s…
1.3.6.1.4.1.9.9.246 ciscoL2TunnelConfigMIB365 This MIB module is for layer 2 tunneling related configurations
on a device.

Tunneling allows separate local networks to be consi…
1.3.6.1.4.1.9.9.248 ciscoItpSp2MIB330 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signaling System No. 7(SS7) Network.
This …