AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | IoT | IT Service | Network/System | Infra | Performance | Protocol | SaaS | Security | Service Level | Storage | Linux | VMware | VoIP | Web | Wireless | SNMP

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Cisco » CISCO-LRE-CPE-MIB » Objects

CISCO-LRE-CPE-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CISCO-LRE-CPE-MIB and use it to monitor vendor specific OID's.

CISCO-LRE-CPE-MIB file content

Object view of CISCO-LRE-CPE-MIB:

Scalar Object
clreCpeDot1dTpFdbEntry .1.3.6.1.4.1.9.9.340.1.1.1.1
An entry that supplements the information in the dot1dTpFdbTable table from the BRIDGE-MIB.
clreCpePortEntry .1.3.6.1.4.1.9.9.340.1.2.1.1
Entry containing information for a particular CPE Fast Ethernet port. The entries are created as new CPE devices are discovered. A new CPE device is discovered when the LRE link between that CPE device and the LRE switch becomes operational. These entries are only valid for ifIndexes of ifType ethernetCsmacd(6).
Tabular Object
clreCpeDot1dBasePortIfIndex .1.3.6.1.4.1.9.9.340.1.1.1.1.1
The value of the instance of the ifIndex object, define in MIB-II, for the interface corresponding to this CPE port. The Forwarding database on the switch tracks a MAC address and its associated switch interface in the dot1dTpFdbTable table. This object adds information about which port on the CPE the MAC address was learnt on.
clreCpePortAdminStatus .1.3.6.1.4.1.9.9.340.1.2.1.1.1
The desired state of the CPE port. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all CPE ports start with clreCpePortAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, clreCpePortAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).
clreCpePortAdminSpeed .1.3.6.1.4.1.9.9.340.1.2.1.1.2
This object controls the speed of this CPE Fast Ethernet port. When set to autoDetect(1), the CPE port negotiates with its peer for the optimum speed, either s10000000(10000000) or s100000000(100000000). If the peer does not support the autoDetect(1) capability, the CPE port speed defaults to s10000000(10000000).
clreCpePortAdminDuplex .1.3.6.1.4.1.9.9.340.1.2.1.1.3
This object controls the duplex of this CPE Fast Ethernet port. When set to autoDetect(1), the CPE port negotiates with its peer for the optimum duplex setting, either fullDuplex(2) or halfDuplex(3). If the peer does not support the autoDetect(1) capability, this CPE port's duplex defaults to halfDuplex(3).
clreCpePortAdminProtected .1.3.6.1.4.1.9.9.340.1.2.1.1.4
This object configures a CPE Fast Ethernet port as a protected port when its value is set to true. Data traffic is disallowed between two CPE ports configured as protected ports. When the value of this object is set to false, the protected port property of this CPE port is removed. The value of this object can be set to true only on those CPE ports that support the protected port function.Note that the value of this object represents the desired state of the port. The actual state of the port may have a different value.
clreCpePortOperProtected .1.3.6.1.4.1.9.9.340.1.2.1.1.5
The value represented by this object is the actual protected port state of the CPE port. The object value is true when this CPE port is configured as a protected port. Data packets are not forwarded between two CPE ports configured as protected ports.
Table
clreCpeDot1dTpFdbTable .1.3.6.1.4.1.9.9.340.1.1.1
A table that supplements the information from the BRIDGE-MIB. The BRIDGE-MIB tracks the MAC address to switch interface mapping in the dot1dTpFdbTable. On the long reach ethernet switch, CPE devices connect to the switch interfaces. Each CPE device has one or more ports. This table maps a MAC address on the switch to an interface associated with a CPE port.
clreCpePortTable .1.3.6.1.4.1.9.9.340.1.2.1
A list of LRE CPE port entries. The number of entries is determined by the number of Long Reach Ethernet interfaces (to which the CPE attaches) on the switch and the number of Fast Ethernet ports each CPE supports.
Object Identifier
ciscoLreCpeMIB .1.3.6.1.4.1.9.9.340
The MIB module for the Cisco Long Reach Ethernet Customer Premise Equipment device information. *** ABBREVIATIONS, ACRONYMS, AND SYMBOLS *** CPE - Customer Premise Equipment DSL - Digital Subscriber Loop VDSL - Very High Speed DSL LRE - Long Reach Ethernet
ciscoLreCpeMIBObjects .1.3.6.1.4.1.9.9.340.1
clreCpeDot1dTp .1.3.6.1.4.1.9.9.340.1.1
clreCpePort .1.3.6.1.4.1.9.9.340.1.2
clreCpeMIBNotifications .1.3.6.1.4.1.9.9.340.0
clreCpeMIBNotificationsPrefix .1.3.6.1.4.1.9.9.340.0.0
clreCpeMIBConformance .1.3.6.1.4.1.9.9.340.2
clreCpeMIBCompliances .1.3.6.1.4.1.9.9.340.2.1
clreCpeMIBGroups .1.3.6.1.4.1.9.9.340.2.2
Group
clreCpePortGroup .1.3.6.1.4.1.9.9.340.2.2.2
The collection of MIB objects used to manage and monitor LRE CPE Fast Ethernet ports.
clreCpeDot1dTpGroup .1.3.6.1.4.1.9.9.340.2.2.1
The collection of MIB objects used to monitor the transparent learning bridge on the LRE CPE.