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.314 ciscoCasIfExtMIB3225 The MIB module is an extension of CISCO-CAS-IF-MIB.
It defines the attributes of a voice interface.
1.3.6.1.4.1.9.9.315 ciscoPortSecurityMIB389 The MIB module for managing Cisco Port Security.
1.3.6.1.4.1.9.9.317 ciscoIscsiGwMIB3145 MIB module for monitoring and configuring iSCSI
gateway functions. An iSCSI gateway represents FC
(Fibre Channel) targets/initiat…
1.3.6.1.4.1.9.9.318 ciscoXgcpMIB3120 This MIB is an enhancement for existing XGCP-MIB.

xGCP is a set of protocols, for example SGCP (Simple
Gateway Control Protocol) …
1.3.6.1.4.1.9.9.319 ciscoPropAtmIfMIB357 This MIB is designed for Propietary ATM (propAtm)
interfaces.
The propAtm interfaces are identified in the ifTable
entries with if…
1.3.6.1.4.1.9.9.321 ciscoMgcMIB343 This MIB is used to support MGC(call agent) and
MGC Group configuration.
The MGC or MGC group configuration is performed
under a s…
1.3.6.1.4.1.9.9.322 ccacSysMIB260 This MIB module provides provisioning and
monitoring Call Admission Control (CAC).
1.3.6.1.4.1.9.9.323 ciscoVoiceAalxProfileMIB387 This MIB defines the objects specific to voice
over ATM or voice over IP. Those objects are
related to the following areas:
1. COD…
1.3.6.1.4.1.9.9.324 ciscoMediaGatewayMIB3107 The MIB module for managing Trunk Media Gateway.

A Media Gateway is a network element that provides conversion
between the audio …
1.3.6.1.4.1.9.9.325 ciscoXgcpExtMIB265 This MIB module is an extension to CISCO-XGCP-MIB.

It defines the parameters related to the following
aspects in xGCP protocols:
*…
1.3.6.1.4.1.9.9.326 ciscoIpLocalPoolMIB357 This MIB defines the configuration and monitoring capabilities
relating to local IP pools.

Local IP pools have the following char…
1.3.6.1.4.1.9.9.329 ciscoFcipMgmtExtMIB375 A MIB module for extending the CISCO-FCIP-MGMT-MIB
to add objects which provide additional information
about FCIP interfaces not …
1.3.6.1.4.1.9.9.330 ciscoSysInfoLogMIB344 This MIB provides the configuration of System Information
Logging feature, which allows a certain number of commands
to be execut…
1.3.6.1.4.1.9.9.331 ciscoCsgMIB386 This MIB supports the Cisco Content Services Gateway
(CSG) product. It includes five traps and four tables
that enable querying C…
1.3.6.1.4.1.9.9.332 ciscoGsp2MIB391 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.333 ciscoGactMIB340 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.334 ciscoGrtMIB3150 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.335 ciscoGsccpMIB3293 The MIB for signalling Connection Control Part(SCCP)
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP…
1.3.6.1.4.1.9.9.336 ciscoGspMIB3273 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.339 ciscoSecureShellMIB240 MIB module for displaying and configuring
accounting and Secure Shell (SSH) related
features in a device.

SSH is a program to log …
1.3.6.1.4.1.9.9.340 ciscoLreCpeMIB321 The MIB module for the Cisco Long Reach Ethernet
Customer Premise Equipment device information.

*** ABBREVIATIONS, ACRONYMS, AND …
1.3.6.1.4.1.9.9.341 ciscoCableQosMonitorMIB357 This is the MIB module for subscriber QoS monitoring
for DOCSIS-compliant Cable Modem Termination Systems
(CMTS).

Several subscrib…
1.3.6.1.4.1.9.9.343 ciscoAuthorizationStatsMibModule225 The Cisco User Authorization Statistics MIB models
counters and objects that are of management
interest.
1.3.6.1.4.1.9.9.344 ciscoEntityDisplayMIB221 This MIB module provides information about the
status of display devices such as Light Emitting
Diodes (LEDs) and alphanumeric di…
1.3.6.1.4.1.9.9.350 ciscoEntityDiagMIB3139 This MIB module defines the managed objects that describe the
online diagnostics capabilities supported by the
physical entities …
1.3.6.1.4.1.9.9.351 ciscoAtmTrunkMIB3102 The MIB for voice and Nx64 over ATM Trunking applications.

The following lists the abbreviations used in this MIB:
AAL ATM …
1.3.6.1.4.1.9.9.356 ciscoVoiceToneCadenceMIB330 The MIB defines the attributes of the programmable
tones specified in ITU-T E.180 Supplement 2.

Each country has its own regulati…
1.3.6.1.4.1.9.9.358 ciscoBbsmMIB320 This mib is designed to send BBSM specific
notifications. There are variables that contain detail data
that are bind to a notifi…
1.3.6.1.4.1.9.9.359 ciscoLicenseMIB352 This MIB module provides objects to view the features
and services that are licensed to run on a system (usually
a network entity…
1.3.6.1.4.1.9.9.360 ciscoImageUpgradeMIB3101 This mib provides, objects to upgrade images on modules in the
system, objects showing the status of the upgrade operation,
and o…
1.3.6.1.4.1.9.9.361 ciscoCommonRolesMIB340 MIB module for managing the common roles between
access methods like Command Line Interface (CLI), SNMP
and XML interfaces.
Every …
1.3.6.1.4.1.9.9.362 ciscoPortStormControlMIB343 The MIB module for managing Cisco Port Storm Control.
1.3.6.1.4.1.9.9.363 ciscoFcSpanMIB249 MIB module for displaying and configuring
Switched Port Analyzer(SPAN) related features
in a Fibre Channel device.

SPAN is a featu…
1.3.6.1.4.1.9.9.364 ciscoPsmMIB3213 The MIB module for the management of the
Port Security Manager (PSM). The PSM
consists of 2 aspects: Port binding and
Fabric bindi…
1.3.6.1.4.1.9.9.365 ciscoFCCMIB342 The MIB module for the management of Fibre Channel
Congestion Control(FCC). FCC is a Cisco proprietary
flow control mechanism tha…
1.3.6.1.4.1.9.9.367 ciscoAAAServerExtMIB277 This MIB is an extension to the CISCO-AAA-SERVER-MIB.
This MIB module enhances the 'casConfigTable' to
include other types of Ser…
1.3.6.1.4.1.9.9.368 36800 Cisco Content Services (CSS) switch product, also known as Arrowpoint, for version 7.40 and later
1.3.6.1.4.1.9.9.369 ciscoLicenseMgrMIB3102 The MIB module for a method of managing license files on
the system.
Licensing mechanism provides more flexibility in supporting
v…
1.3.6.1.4.1.9.9.370 ciscoSslProxyMIB3372 This MIB module is for managing a Secure Socket Layer
(SSL) Proxy device which terminates and accelarates
SSL and Transport Layer…
1.3.6.1.4.1.9.9.371 ciscoIvrMIB3192 The MIB module for the management of Inter-VSAN
routing within the framework of Cisco's
Inter-VSAN Routing (IVR) Architecture. IV…
1.3.6.1.4.1.9.9.372 ciscoIsnsClientMIB316 MIB module for monitoring and configuring Internet
Storage Name Service (iSNS) client.
1.3.6.1.4.1.9.9.373 ciscoFdmiMIB347 Fabric Device Management Interface (FDMI) MIB. This MIB
module defines objects for managing the devices such as
HBA (Host Bus Ada…
1.3.6.1.4.1.9.9.374 ciscoDynamicArpInspectionMIB382 The MIB module is for configuration of Dynamic ARP Inspection
feature. Dynamic ARP Inspection is a security mechanism which
valid…
1.3.6.1.4.1.9.9.375 ciscoFiconMIB3176 This is the FICON (FIber CONnection) MIB module.

FICON is an IBM standard of transport mechanism
for communication between the ma…
1.3.6.1.4.1.9.9.376 ciscoSVIAutostateMIB319 The MIB module is for configuration of the switch virtual
interface (SVI) autostate feature. Autostate feature
is a mechanism to …
1.3.6.1.4.1.9.9.377 ciscoFeatureCtrlMIB353 There are two types of features in the system:

- Regular features
- Optional features

The Regular features may or may not need t…
1.3.6.1.4.1.9.9.378 ciscoSvcInterfaceMIB3115 MIB module for displaying and configuring
SVC (SAN Volume Controller) related features
in the Storage Area Network (SAN) switches…
1.3.6.1.4.1.9.9.379 ciscoItpmMIB347 The MIB for providing information related to
monitoring SS7 links.

This information can be used to manage the state
of software u…
1.3.6.1.4.1.9.9.380 ciscoDhcpSnoopingMIB3127 The MIB module is for configuration of DHCP Snooping
feature. DHCP Snooping is a security mechanism which
uses information gleane…
1.3.6.1.4.1.9.9.381 ciscoDiffServExtMIB249 This MIB is a Cisco extension to the
DIFFSERV-MIB, RFC 3289. This MIB defines
a Fibre Channel (FC) Multi Field filter to
be used i…