LANCITY-MCNS-MIB :: lcErrSmBootpRelayCantWork

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LANCITY-MCNS-MIB › lcErrSmBootpRelayCantWork

lcErrSmBootpRelayCantWork

Module: LANCITY-MCNS-MIB

OID (symbolic): LANCITY-MCNS-MIB::lcErrSmBootpRelayCantWork

OID (numeric): 1.3.6.1.4.1.482.0.826

Node type: NOTIFICATION-TYPE

Description: No IP address is assigned so BOOTP Relay functionality cannot work. This means that CMs behind this CMTS will not register

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' LANCITY-MCNS-MIB::lcErrSmBootpRelayCantWork
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.482.0.826

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:63995->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (225717243) 26 days, 2:59:32.43
  SNMPv2-MIB::snmpTrapOID.0 = OID: LANCITY-MCNS-MIB::lcErrSmBootpRelayCantWork

Start monitoring LanCity/Bay Networks CMTS head-end or cable modem (MCNS/DOCSIS-style) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LANCITY-MCNS-MIB::lcErrSmBootpRelayCantWork OID value, configure state conditions and alerts, and monitor any LanCity/Bay Networks CMTS head-end or cable modem (MCNS/DOCSIS-style) from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.482lancityLANCITY-MIB
Numeric OIDNameModule
1.3.6.1.4.1.482.0.826lcErrSmBootpRelayCantWorkLANCITY-MCNS-MIB