GEN-MIB

MIB Reference — IPNetwork Monitor

All MIBsGEN-MIB

Category: Device Management, Vendor: GDC

Description:

Generic MIB providing common management objects for basic device identification and status monitoring.

Imported Objects

From RFC1155-SMI

enterprises

What Is GEN-MIB?

GEN-MIB is a generic base MIB tied to LANNET/Madge networking equipment (LANNET was an Ethernet/Token Ring hub and probe vendor later absorbed into Madge Networks), providing baseline device identification and management objects shared across the LANNET/Madge product line. Categories exposed include basic device identity/registration arcs (lannet, madge, lntOID), a device manager object group, and a network probe object group, plus box-level identification. Its use in monitoring emphasizes confirming basic hardware presence and identity — that a LANNET/Madge box or RMON-style probe is present and identifiable to the management station — rather than deep performance counters. It works alongside LANNET/Madge's more specific product MIBs (hub, bridge, probe modules) that build on this generic base. It is deployed on legacy LANNET/Madge Ethernet or Token Ring hubs and network probes in older enterprise LAN environments. GEN-MIB SNMP monitoring is therefore limited to identity and presence checks rather than the richer traffic or performance counters found in companion LANNET/Madge product MIBs.

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

What Can Be Monitored

  • device identification/type
  • device manager presence
  • network probe module status
  • chassis/box identifier

Supported Devices

  • LANNET/Madge Ethernet or Token Ring hub
  • LANNET/Madge network probe device

Monitoring Examples

An admin would use the deviceMgr object group to confirm the identity/type of a LANNET/Madge managed device, and the probe branch to confirm an RMON-style network probe module is present and reachable on the box. lBoxOID identifies the specific chassis/box, useful when multiple LANNET/Madge units are managed from one console and need to be distinguished. Because the objects captured here are registration-level identifiers, deeper counters such as per-port traffic would live in companion LANNET/Madge product MIBs.

OIDs
OID symbolicOID numericTypeAccessDescription
lannet1.3.6.1.4.1.81
lntOID1.3.6.1.4.1.81.17
lBoxOID1.3.6.1.4.1.81.17.1
lUnknownBoxOID1.3.6.1.4.1.81.17.1.1
lLET18BoxOID1.3.6.1.4.1.81.17.1.2
lLET3BoxOID1.3.6.1.4.1.81.17.1.3
lLET36BoxOID1.3.6.1.4.1.81.17.1.4
lLET18EBoxOID1.3.6.1.4.1.81.17.1.5
lLERT40BoxOID1.3.6.1.4.1.81.17.1.6
lLET10BoxOID1.3.6.1.4.1.81.17.1.7
lFDX100BoxOID1.3.6.1.4.1.81.17.1.8
lSTACKBoxOID1.3.6.1.4.1.81.17.1.9
lLET20BoxOID1.3.6.1.4.1.81.17.1.10
lLET36_01_02BoxOID1.3.6.1.4.1.81.17.1.11
visageBoxOID1.3.6.1.4.1.81.17.1.12
visage16155BoxOID1.3.6.1.4.1.81.17.1.13
letM770BoxOID1.3.6.1.4.1.81.17.1.14
m770BoxOID1.3.6.1.4.1.81.17.1.15
m770AtmOID1.3.6.1.4.1.81.17.1.16
cajunP330OID1.3.6.1.4.1.81.17.1.17
cajunP130OID1.3.6.1.4.1.81.17.1.18
cajunP360OID1.3.6.1.4.1.81.17.1.19
smartDevicesOID1.3.6.1.4.1.81.17.2
unknownDeviceOID1.3.6.1.4.1.81.17.2.1
lsaOID1.3.6.1.4.1.81.17.2.2
iasOID1.3.6.1.4.1.81.17.2.3
collage530OID1.3.6.1.4.1.81.17.2.4
eaxOID1.3.6.1.4.1.81.17.2.5
lsfOID1.3.6.1.4.1.81.17.2.6
lsa2OID1.3.6.1.4.1.81.17.2.7
mmlsOID1.3.6.1.4.1.81.17.2.8
visage26OID1.3.6.1.4.1.81.17.2.9
lbt155plusOID1.3.6.1.4.1.81.17.2.10
cajunP120OID1.3.6.1.4.1.81.17.2.11
visage26PlusOID1.3.6.1.4.1.81.17.2.12
cajunP333ROID1.3.6.1.4.1.81.17.2.13
cajunP122OID1.3.6.1.4.1.81.17.2.14
cajunP330AtmOID1.3.6.1.4.1.81.17.2.15
deviceMgr1.3.6.1.4.1.81.20
probe1.3.6.1.4.1.81.22
madge1.3.6.1.4.1.494

FAQ

What is GEN-MIB used for when managing legacy LANNET/Madge hubs?
It supports identity and presence checks - confirming that a LANNET/Madge Ethernet or Token Ring hub, or an RMON-style network probe, is present and identifiable to the management station via its device manager and network probe object groups plus a chassis/box identifier.

Why wouldn't GEN-MIB be enough for detailed traffic monitoring on these devices?
Because GEN-MIB only exposes baseline identity and box-level data such as device type and presence, richer traffic or performance counters live in LANNET/Madge's more specific hub, bridge, and probe product MIBs that build on this generic base.

RFC description

Generic MIB module providing common SNMP object definitions for general device management, typically including system information, device status, and basic configuration parameters across various network devices.

Start monitoring LANNET/Madge Ethernet or Token Ring hub / network probe (legacy) 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 GEN-MIB