OCCAM-ETHERLIKE-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › OCCAM-ETHERLIKE-MIB

Organization: Occam Networks

Last Updated: 2001-04-27

Category: DSL and Broadband Access

Description: Monitors Ethernet-like interface error counters and collision statistics on Occam Networks DSL broadband equipment.

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 OCCAM-ETHERLIKE-MIB?

OCCAM-ETHERLIKE-MIB is deployed on Occam Networks DSL/broadband access equipment and defines generic objects for monitoring Ethernet-like network interfaces, closely modeled on the IEEE 802.3 CSMA/CD standard that its module description explicitly references. It is intended to expose Ethernet-like interface statistics — error and collision counters that supplement the standard ifTable/EtherLike-MIB view — for the vendor's Ethernet ports. Because it tracks per-interface error conditions typical of an EtherLike-style MIB (collisions, alignment errors, frame check sequence errors), it is fundamentally a hardware/interface-health monitoring module used to detect degraded or failing Ethernet links on the access device. As its own description states, it follows the IEEE 802.3 standard for its object semantics, making it a vendor extension layered on that standard rather than an independent data model. The OCCAM-ETHERLIKE-MIB MIB is typically deployed on Occam Networks DSL/broadband access multiplexers where Ethernet uplinks or subscriber-facing Ethernet ports need error-rate monitoring.

IPNetwork Monitor allows you to monitor SNMP objects defined in OCCAM-ETHERLIKE-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

  • Occam Networks DSL/broadband access multiplexer

Monitoring Examples

No specific object or table names for this MIB were available in the extracted source excerpt, so a concrete polling example can't be grounded in real identifiers here. Based on its module description (an IEEE 802.3-referenced, generic Ethernet-like interface MIB), it would typically be polled for per-interface error and collision counters analogous to the standard EtherLike-MIB's dot3Stats table, where a rising alignment- or FCS-error count on a port would indicate a failing cable or NIC. No sample object names can be honestly cited beyond that generic pattern.

What Can Be Monitored

  • Ethernet collision counts
  • alignment errors
  • frame check sequence (FCS) errors
  • carrier sense errors
  • interface link/duplex status
Imported Objects

From IF-MIB

InterfaceIndex
ifIndexOBJECT-TYPE

From OCCAM-REG-MODULE

occamGenericEtherlikeModulesOBJECT-IDENTITY
occamGenericInterfaceModulesOBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE
enterprises
mib-2
transmission

How to Use in IPNetwork Monitor

Example using dot3StatsSingleCollisionFrames OID:

Select an Occam Networks DSL/broadband access multiplexer (Ethernet-like interface error statistics) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type dot3StatsSingleCollisionFrames into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports a count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

OCCAM Ethernet-like MIB based on RFC 3635 for describing generic objects for Ethernet-like network interfaces including 10 Gb/sec interface support.

Start monitoring Occam Networks DSL/broadband access multiplexer (Ethernet-like interface error statistics) 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 OCCAM-ETHERLIKE-MIB