CISCO-ETHERNET-ACCESS-MIB

All MIBs › CISCO-ETHERNET-ACCESS-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2007-09-14

Category: Cisco Devices, Network Interfaces

Description: Provides management objects for configuring and monitoring Cisco Ethernet access interfaces and service demarcation features.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-ETHERNET-ACCESS-MIB?

CISCO-ETHERNET-ACCESS-MIB provides management objects for Cisco edge/access devices that sit at the customer-facing boundary of a Metro Ethernet network, mapping subscriber traffic into the service provider's network over CAT5 or fiber access media. It exposes port-level configuration and capability data (port type, capability flags) and VLAN-mapping tables for UNI (User-Network Interface) ports, including maximum supported NNI and UNI/VLAN-community port counts. Its monitoring relevance is configuration/capability-status oriented: administrators check ceaPortType/ceaPortCapability to confirm an edge port is correctly provisioned for its access technology and use ceaUNIVlanTable to verify VLAN-to-community mappings are correct for subscriber traffic separation, rather than tracking physical sensors. It is a Cisco extension layered on top of general interface (IF-MIB) and VLAN MIBs, adding Metro Ethernet edge-device semantics. It is deployed on Cisco Metro Ethernet edge/access devices used by service providers to demarcate and map customer Ethernet services. Engineers can download the CISCO-ETHERNET-ACCESS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-ETHERNET-ACCESS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco Metro Ethernet edge/access device

Monitoring Examples

An operator would poll ceaPortTable/ceaPortEntry for ceaPortType and ceaPortCapability on a given access port to confirm it's configured for the expected UNI role, and check ceaUNIVlanTable/ceaUNIVlanEntry's ceaUNIVlanType to verify subscriber VLANs are mapped into the correct community. Comparing configured port counts against ceaMaxNNIPorts/ceaMaxUNIVlanCommunityPorts would reveal whether the device is nearing its supported scale limits for new subscriber turn-ups.

What Can Be Monitored

access port type/capability
UNI VLAN-to-community mapping
NNI port count vs maximum
UNI/VLAN community port scale

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-VTP-MIB

managementDomainIndex	OBJECT-TYPE
vtpVlanIndex	OBJECT-TYPE

From IF-MIB

ifIndex

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoEthernetAccessMIB	1.3.6.1.4.1.9.9.466			The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to an edge device in an organizations network, e.g. a Metro Ethernet network. An edge device, is a customer located equipment, this is the first device which will connect the Service Provider's network and map subscriber traffic into the next layer. The access media could be either CAT5 or fiber. The access device (edge device) can be designed for DSL, Ethernet or other technologies, however, this MIB is designed for Ethernet. Terminology: UNI - User to Network Interface NNI - Network to Network Interface. ENI - Enhanced Network Interface. Enhanced UNI port. module/device - In an environment (specifically, in an SNMP context) consisting of a single chassis which can contain multiple cards, the term 'module' refers to a card and the term 'device' refers to the whole chassis. In an environment where multiple chassis are 'stacked' together, the term 'module' refers to a chassis and the term 'device' refers to the whole stack. In an environment containing only a single chassis without removable cards, the terms 'device' and 'module' both refer to the chassis and its contents.
ciscoEthernetAccessMIBObjects	1.3.6.1.4.1.9.9.466.1
ceaGlobals	1.3.6.1.4.1.9.9.466.1.1
I32 ceaMaxNNIPorts	1.3.6.1.4.1.9.9.466.1.1.1	Integer32	read-only	The max number of interfaces per module for which the ceaPortType can have the value 'nni'. The value of 0 is returned by this object if there is no limitation to the number of NNI ports.
I32 ceaMaxUNIVlanCommunityPorts	1.3.6.1.4.1.9.9.466.1.1.2	Integer32	read-only	The maximum number of ports on this device for which the ceaUNIVlanType object can have the value 'community'. The value of 0 is returned by this object if there is no limitation to the number of UNI VLAN Communities.
ceaConfig	1.3.6.1.4.1.9.9.466.1.2
ceaPortTable	1.3.6.1.4.1.9.9.466.1.2.1		not-accessible	This table contains Ethernet port specific information. There exists an entry for each Ethernet port with an ifType of 6 (ethernetCsmacd) in this table. Note that the maximum number of NNI ports that can be configured per module on this device is given by the value of ceaMaxNNIPorts.
ceaPortEntry	1.3.6.1.4.1.9.9.466.1.2.1.1		not-accessible	A set of Ethernet port specific parameters for a device which can be configured with a mixture of port types defined by the ceaPortType object.
INT ceaPortType	1.3.6.1.4.1.9.9.466.1.2.1.1.1	INTEGER	read-write	The current configuration of the port. Only ports that are supported by the ceaPortCapability object can be set. Unspecified port type is any other port type than NNI, UNI or ENI. unspecified = Not UNI, or NNI, or ENI uni = User to Network Interface port type. nni = Network to Network Interface port type. eni = Enhanced UNI port type.
BIT ceaPortCapability	1.3.6.1.4.1.9.9.466.1.2.1.1.2	Bits	read-only	Types supported by the Ethernet port. If a port doesn't support the port type the ceaPortType will not allow set of the unsupported type. nni = Port supports NNI. uni = Port supports UNI. eni = Port supports ENI.
ceaUNIVlanTable	1.3.6.1.4.1.9.9.466.1.2.2		not-accessible	This table contains UNI VLAN information for all the VLANs which currently exist on this device. The number of UNI ports that can belong to a VLAN type 'community' is limited by the ceaMaxUNIVlanCommunityPorts object.
ceaUNIVlanEntry	1.3.6.1.4.1.9.9.466.1.2.2.1		not-accessible	There is an entry in this table for each VLAN that exist on this device.
CEA ceaUNIVlanType	1.3.6.1.4.1.9.9.466.1.2.2.1.1	CeaVlanUNIType	read-write	Indicates the VLAN type defined for the UNI VLAN.
ciscoEthernetAccessMIBConform	1.3.6.1.4.1.9.9.466.2
cEthernetAccessMIBCompliances	1.3.6.1.4.1.9.9.466.2.1
cEthernetAccessMIBCompliance	1.3.6.1.4.1.9.9.466.2.1.1			The compliance statement for entities that implement the CISCO-ETHERNET-ACCESS-MIB. Implementation of this MIB is mandatory for any platform that have Ethernet UNI/NNI capable interfaces.
cEthernetAccessMIBGroups	1.3.6.1.4.1.9.9.466.2.2
ceaPortGroup	1.3.6.1.4.1.9.9.466.2.2.1			A collection of managed objects defining port types.
ceaVlanGroup	1.3.6.1.4.1.9.9.466.2.2.2			A collection of managed objects defining VLAN types.

RFC description

Manages Ethernet edge/access devices for Metro Ethernet and subscriber traffic mapping.

Start monitoring Cisco Metro Ethernet edge/access device with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-ETHERNET-ACCESS-MIB

What Is CISCO-ETHERNET-ACCESS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description