LANCITY-MCNS-MIB :: lccmtsDevServerConfigFile

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LANCITY-MCNS-MIB › lccmtsDevServerConfigFile

lccmtsDevServerConfigFile

Module: LANCITY-MCNS-MIB

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

OID (numeric): 1.3.6.1.4.1.482.60.5.10.5

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-only

Description: The name of the device configuration file read from the TFTP server.

What is lccmtsDevServerConfigFile?

Read-only filename of the device configuration file this device fetched from its TFTP server; an operator checks this to confirm a device picked up the intended config file.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.482.60.5.10.5
snmpwalk -v2c -c public <target> LANCITY-MCNS-MIB::lccmtsDevServerConfigFile

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.482.60.5.10.5.1
snmpget -v2c -c public <target> LANCITY-MCNS-MIB::lccmtsDevServerConfigFile.1

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::lccmtsDevServerConfigFile 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.60lancityMcnsMibLANCITY-MCNS-MIB
1.3.6.1.4.1.482.60.5lccmtsdeviceLANCITY-MCNS-MIB
1.3.6.1.4.1.482.60.5.10lccmtsDevServerLANCITY-MCNS-MIB
1.3.6.1.4.1.482.60.5.10.5lccmtsDevServerConfigFileLANCITY-MCNS-MIB