CISCO-ETHERNET-ACCESS-MIB

        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.
    
Source file
CISCO-ETHERNET-ACCESS-MIB
Last revised
Identity
ciscoEthernetAccessMIB
Base OID
1.3.6.1.4.1.9.9.466
Imported Objects
CISCO-SMI ciscoMgmt
CISCO-VTP-MIB managementDomainIndex vtpVlanIndex
IF-MIB ifIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC TEXTUAL-CONVENTION (no object page)
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-ETHERNET-ACCESS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-ETHERNET-ACCESS-MIB::ciscoEthernetAccessMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-ETHERNET-ACCESS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-ETHERNET-ACCESS-MIB::ciscoEthernetAccessMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (16)
.1.3.6.1.4.1.9.9.466
.1.3.6.1.4.1.9.9.466.1
.1.3.6.1.4.1.9.9.466.1.1
Integer32
.1.3.6.1.4.1.9.9.466.1.1.1
Integer32
.1.3.6.1.4.1.9.9.466.1.1.2
.1.3.6.1.4.1.9.9.466.1.2
.1.3.6.1.4.1.9.9.466.1.2.1
.1.3.6.1.4.1.9.9.466.1.2.1.1
Enumeration
.1.3.6.1.4.1.9.9.466.1.2.1.1.1
Bits
.1.3.6.1.4.1.9.9.466.1.2.1.1.2
.1.3.6.1.4.1.9.9.466.1.2.2
.1.3.6.1.4.1.9.9.466.1.2.2.1
.1.3.6.1.4.1.9.9.466.1.2.2.1.1
.1.3.6.1.4.1.9.9.466.2
.1.3.6.1.4.1.9.9.466.2.1
.1.3.6.1.4.1.9.9.466.2.2
Dependencies (12) 6 direct · 6 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (1)
Enumeration
other(1)
isolated(2)
community(3)
Conformance Groups (2)
A collection of managed objects defining port types.
.1.3.6.1.4.1.9.9.466.2.2.1
A collection of managed objects defining VLAN types.
.1.3.6.1.4.1.9.9.466.2.2.2
Compliance Statements (1)

OID .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.
Required groups
mandatory ceaPortGroup
mandatory ceaVlanGroup
Object refinements
ObjectAccessSyntaxDescription
ceaUNIVlanType readonly
Write access is not required.
ceaPortType readonly
Write access is not required.