Home/Catalog/LANCITY-MCNS-MIB

LANCITY-MCNS-MIB

AI MIB Summary

The LANCITY-MCNS-MIB module enables SNMP-based monitoring and management of MCNS-compliant cable modems and associated headend devices manufactured by Lancity, specifically tracking physical layer parameters, channel bonding states, and modem registration status.

This is the portion of the Lancity enterprise MIB that applies to MCNS cable modems and related devices.
Main OID:
lancityMcnsMib.1.3.6.1.4.1.482.60
459
Objects
Active
Status
8
Dependencies

Imported Objects

Objects

459 total
Object Name
lcErrKernelFailureSystem tasking failure
TRAP-TYPE
.1.3.6.1.4.1.482.0.100
lcErrNuSendItemFailureNU_Send_Item failed but task will try to send again
TRAP-TYPE
.1.3.6.1.4.1.482.0.101
lcErrUnknownUnknown error SNMP Trap
TRAP-TYPE
.1.3.6.1.4.1.482.0.200
lcErrSystemErrorSystem error, some sort of exception. Displayed are the EPC, Cause, BadVaddr and Status registers.
TRAP-TYPE
.1.3.6.1.4.1.482.0.201
lcErrTestTesting error handling
TRAP-TYPE
.1.3.6.1.4.1.482.0.202
lcErrAssertAssertion failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.203
lcErrShutdownShutdown initiated
TRAP-TYPE
.1.3.6.1.4.1.482.0.204
lcErrFshResetEvent log was cleared.
TRAP-TYPE
.1.3.6.1.4.1.482.0.205
lcErrRptResetEvent reporting set to default values.
TRAP-TYPE
.1.3.6.1.4.1.482.0.206
lcErrSystemError2System error, some sort of exception, further details for the 4700 processor, specifically the ErrorEPC and CacheError registers.
TRAP-TYPE
.1.3.6.1.4.1.482.0.207
lcErrWatchdogResetThe system was reset because the watchdog timer fired. This means the software was not operating normally, in that the watchdog timer should be periodically cleared to prevent this reset from occurring.
TRAP-TYPE
.1.3.6.1.4.1.482.0.208
lcMsgBacktraceInfo about a system error: calling stack display, helpful for problem analysis.
TRAP-TYPE
.1.3.6.1.4.1.482.0.209
lcMsgBacktraceEndedInfo about a system error: calling stack display reached the top and further info is displayed as to whether this was a normal or unexpected termination.
TRAP-TYPE
.1.3.6.1.4.1.482.0.210
lcMsgBacktrace2Info about a system error: called routine arguments display, helpful for problem analysis.
TRAP-TYPE
.1.3.6.1.4.1.482.0.211
lcMsgDSMakeHistoryEntryNuke history trace.
TRAP-TYPE
.1.3.6.1.4.1.482.0.212
lcMsgPowerSwitchCrashhelpful for problem analysis.
TRAP-TYPE
.1.3.6.1.4.1.482.0.213
lcMsgNullEventhelpful for problem analysis.
TRAP-TYPE
.1.3.6.1.4.1.482.0.214
lcErrRegMemoryUnable to allocate memory for initial ranging
TRAP-TYPE
.1.3.6.1.4.1.482.0.300
lcErrRegRestartRegistrationRe-starting registration for modem
TRAP-TYPE
.1.3.6.1.4.1.482.0.301
lcErrRegNoInitSidUnable to allocate initial service ID for modem
TRAP-TYPE
.1.3.6.1.4.1.482.0.302
lcErrRegRangingFailedRanging retries exceeded for modem
TRAP-TYPE
.1.3.6.1.4.1.482.0.303
lcErrRegInvalidRangingInvalid ranging request received from modem
TRAP-TYPE
.1.3.6.1.4.1.482.0.304
lcErrRegRangingTimeoutRanging timed out for modem
TRAP-TYPE
.1.3.6.1.4.1.482.0.305
lcErrRegInvalidRegistrationInvalid registration request received from modem
TRAP-TYPE
.1.3.6.1.4.1.482.0.306
lcErrRegNoModemIpRegistration request from modem did not have Modem IP Address TLV (12).
TRAP-TYPE
.1.3.6.1.4.1.482.0.307
lcErrRegNoIpAtAllRegistration request from modem did not have Modem IP Address TLV (12) or TFTP Server Provisioned Modem Address (20) so IP address 0.0.0.0 was assigned.
TRAP-TYPE
.1.3.6.1.4.1.482.0.308
lcErrRegUnpackingFailUnable to unpack the TLV data in the registration request received from modem
TRAP-TYPE
.1.3.6.1.4.1.482.0.309
lcErrRegRegisteredAlreadyModem is already registered as another SID
TRAP-TYPE
.1.3.6.1.4.1.482.0.310
lcErrRegValidationFailRegistration request data in error, failed validation test.
TRAP-TYPE
.1.3.6.1.4.1.482.0.311
lcErrRegNoRegSidRegistration request failed because no SID was available.
TRAP-TYPE
.1.3.6.1.4.1.482.0.312
lcErrCmctrlGenericEmergencyControl Task fatal error is reported
TRAP-TYPE
.1.3.6.1.4.1.482.0.400
lcErrCmctrlGenericDebugControl Task fatal error is reported
TRAP-TYPE
.1.3.6.1.4.1.482.0.401
lcErrCmctrlUccNotSupportedUpstream Change Channel not currently supported.
TRAP-TYPE
.1.3.6.1.4.1.482.0.402
lcErrCtInvalidEventInvalid ITM type received.
TRAP-TYPE
.1.3.6.1.4.1.482.0.403
lcErrLossOfSynchSynchronization Lost.
TRAP-TYPE
.1.3.6.1.4.1.482.0.404
lcErrAcquiredSynchSynchronization acquired on frequency.
TRAP-TYPE
.1.3.6.1.4.1.482.0.405
lcErrCmctrlUcdCompleteUCD Complete.
TRAP-TYPE
.1.3.6.1.4.1.482.0.406
lcErrCmctrlUccRxUCC received for channel.
TRAP-TYPE
.1.3.6.1.4.1.482.0.407
lcErrRescanRescan cause.
TRAP-TYPE
.1.3.6.1.4.1.482.0.408
lcErrLostPulseLost Pulse.
TRAP-TYPE
.1.3.6.1.4.1.482.0.409
lcErrLostSynchLost Synch.
TRAP-TYPE
.1.3.6.1.4.1.482.0.410
lcErrIrqPhy1FEC Lost Lock.
TRAP-TYPE
.1.3.6.1.4.1.482.0.411
lcErrIrqPhy2Phy2 IRQ.
TRAP-TYPE
.1.3.6.1.4.1.482.0.412
lcErrCtRangeAbortRanging aborted by CMTS
TRAP-TYPE
.1.3.6.1.4.1.482.0.413
lcErrCtTxAdjustmentsTX adjusted by CMTS
TRAP-TYPE
.1.3.6.1.4.1.482.0.414
lcErrCtRangingCompleteRanging Complete
TRAP-TYPE
.1.3.6.1.4.1.482.0.415
lcErrUnexpectedBpduUnexpected spanning tree packet format received
TRAP-TYPE
.1.3.6.1.4.1.482.0.500
lcErrAllocatorInternalInternal inconsistency in Upstream Scheduler due to CMTS malfunction. Contact Customer Support.
TRAP-TYPE
.1.3.6.1.4.1.482.0.600
lcErrAllocatorResourceDownstream transmitter hang reported by scheduler. CMTS is reset to clear transmittter problem. If this happens repeatedly, contact Customer Support.
TRAP-TYPE
.1.3.6.1.4.1.482.0.601
lcErrHedpBufCountErrorInitialization Mismatched Buffer Counts
TRAP-TYPE
.1.3.6.1.4.1.482.0.700
lcErrHedpIpSecurityAlarmIP Address moved from MAC addresss ... to MAC address ....
TRAP-TYPE
.1.3.6.1.4.1.482.0.701
lcErrHedpMacSecurityAlarmMAC Address moved from port & said to port & said
TRAP-TYPE
.1.3.6.1.4.1.482.0.702
lcErrHedpHashResourcesAddress Hash Table resource exhausted
TRAP-TYPE
.1.3.6.1.4.1.482.0.703
lcErrHedpHashLookupAddress Hash Table lookup failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.704
lcErrHedpInvalidMacFrameData Path received an Invalid MAC Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.705
lcErrHedpNonsupportedEhdrData Path received Extended Header that is not supported
TRAP-TYPE
.1.3.6.1.4.1.482.0.706
lcErrHedpInvalidEhdrData Path received invalid or note supported Extended Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.707
lcErrHedpLookupFailedMAC Address was not found when DP was informed of CM's registration/inoperability
TRAP-TYPE
.1.3.6.1.4.1.482.0.708
lcErrHedpMtdDebugDP MTD found null buffer address in enet_tx_desc_get or mac_tx_desc_get
TRAP-TYPE
.1.3.6.1.4.1.482.0.709
lcErrHedpInvalidEhdr28Data Path received invalid Extended Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.710
lcErrHedpInvalidEhdr56Data Path received invalid Extended Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.711
lcErrHedpInvalidEhdr84Data Path received invalid Extended Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.712
lcErrHedpInvalidEhdr112Data Path received invalid Extended Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.713
lcErrHedpMtdOccurredDP MTD occurred debug message
TRAP-TYPE
.1.3.6.1.4.1.482.0.714
lcErrHedpMtdOccurred2DP MTD occurred debug message#2
TRAP-TYPE
.1.3.6.1.4.1.482.0.715
lcErrHedpMtdOccurred3DP MTD occurred debug message#3
TRAP-TYPE
.1.3.6.1.4.1.482.0.716
lcErrHedpDhcpTraceDP DHCP Trace encountered error: invalid ethernet length
TRAP-TYPE
.1.3.6.1.4.1.482.0.717
lcErrHedpDescNotSupportedCATV/Ethernet Rx descriptor received with FIRST + LAST not set
TRAP-TYPE
.1.3.6.1.4.1.482.0.718
lcErrHedpRxTooLongCATV/Ethernet Rx descriptor received with FIRST + LAST not set
TRAP-TYPE
.1.3.6.1.4.1.482.0.719
lcErrHedpDump1dump data
TRAP-TYPE
.1.3.6.1.4.1.482.0.720
lcErrHedpDump2dump data
TRAP-TYPE
.1.3.6.1.4.1.482.0.721
lcErrSmGenericEmergencySystem Manager fatal error is reported. Contact Customer Support.
TRAP-TYPE
.1.3.6.1.4.1.482.0.800
lcErrSmGenericDebugSystem Manager debug information is reported
TRAP-TYPE
.1.3.6.1.4.1.482.0.801
lcErrSmMallocFailureSystem Manager reports: SM_alloc() memory allocation failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.802
lcErrSmFreeFailureSystem Manager reports: SM_free() memory release failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.803
lcErrSmRestartSystem Manager reports: Restart
TRAP-TYPE
.1.3.6.1.4.1.482.0.804
lcErrSmTempTooHighDevice Temperature Exceeded Specified Temperature Threshold
TRAP-TYPE
.1.3.6.1.4.1.482.0.805
lcErrSmProcSpeedNoticeCPU speed detected to be: %d
TRAP-TYPE
.1.3.6.1.4.1.482.0.806
lcSmProcNoTimeServerDhcpTime server not specified in DHCP offer
TRAP-TYPE
.1.3.6.1.4.1.482.0.807
lcSmProcTimeServerDhcpTime server specified in DHCP offer
TRAP-TYPE
.1.3.6.1.4.1.482.0.808
lcSmProcTimeServerContactedTime server contacted
TRAP-TYPE
.1.3.6.1.4.1.482.0.809
lcSmProcTimeServerNotContactedTime server not contacted
TRAP-TYPE
.1.3.6.1.4.1.482.0.810
lcErrSmBadTrapTypeA trap was requested specifying an unknown trap type
TRAP-TYPE
.1.3.6.1.4.1.482.0.811
lcErrSmBadTrapMsgCreationError creating trap packet for a particular trap type
TRAP-TYPE
.1.3.6.1.4.1.482.0.812
lcErrSmMibPrvsnErrorSystem Manager reports: Error processing a provisioned SNMP object
TRAP-TYPE
.1.3.6.1.4.1.482.0.813
lcDhcpMissingBasicA DHCP offer was received which is unacceptable because it lacks either yiaddr, siaddr, or filename. The filename is always needed at the CM; it appears at the CMTS only if TFTP provisioning is required.
TRAP-TYPE
.1.3.6.1.4.1.482.0.814
lcDhcpMissingRequiredA DHCP offer was received which is unacceptable because it lacks an option required by the device. The tag is from RFC2132.
TRAP-TYPE
.1.3.6.1.4.1.482.0.815
lcDhcpMissingRouterA DHCP offer was received which lacks a gateway address.
TRAP-TYPE
.1.3.6.1.4.1.482.0.816
lcSmTimeserverIcmpAn ICMP message (probably destination unreachable) was received when attempting to query the time server.
TRAP-TYPE
.1.3.6.1.4.1.482.0.817
lcErrPrvsnGenericErrorSystem Manager reports: Error processing a provisioned SNMP object
TRAP-TYPE
.1.3.6.1.4.1.482.0.819
lcErrSmGenericInformationSystem Manager reports information
TRAP-TYPE
.1.3.6.1.4.1.482.0.820
lcErrSmTftpFileTooBigTFTP get of Provisioning file failed because the file size received exceeds the receive buffer size
TRAP-TYPE
.1.3.6.1.4.1.482.0.821
lcErrSmDhcpGotNakDHCP received a NAK from the server and the offer is rejected
TRAP-TYPE
.1.3.6.1.4.1.482.0.822
lcErrSmDhcpIncompleteOfferThe DHCP OFFER from the specified server does not have all required fields and is being ignored. A previous log entry will have the specific error describing which entry was missing.
TRAP-TYPE
.1.3.6.1.4.1.482.0.823
lcErrSmDhcpNoOfferDHCP discover received no offers or offers that were silently ignored
TRAP-TYPE
.1.3.6.1.4.1.482.0.824
lcErrSmDhcpSentDeclineDHCP offer declined because it contained an IP address that is in used by another station
TRAP-TYPE
.1.3.6.1.4.1.482.0.825
lcErrSmBootpRelayCantWorkNo IP address is assigned so BOOTP Relay functionality cannot work. This means that CMs behind this CMTS will not register
TRAP-TYPE
.1.3.6.1.4.1.482.0.826
lcErrSmBootpRelayNowWorksIP address is assigned so BOOTP Relay functionality can now work
TRAP-TYPE
.1.3.6.1.4.1.482.0.827
lcErrFiltGenericDebugFilter Module reports debug information
TRAP-TYPE
.1.3.6.1.4.1.482.0.1200
lcErrFiltInvalidFlashValueFilter Module reports an invalid flash value was read
TRAP-TYPE
.1.3.6.1.4.1.482.0.1201
lcErrFiltIpTblEntryNotActiveError attempting to remove IP table entry which is not active
TRAP-TYPE
.1.3.6.1.4.1.482.0.1202
lcErrFiltLlcTblEntryNotActiveError attempting to remove LLC table entry which is not active
TRAP-TYPE
.1.3.6.1.4.1.482.0.1203
lcErrFiltGenericInformationFilter Module reports information
TRAP-TYPE
.1.3.6.1.4.1.482.0.1204
lcErrSmSwUpgradeGenericNoticeSoftware upgrade reports information
TRAP-TYPE
.1.3.6.1.4.1.482.0.1300
lcErrSmSwUpgradeFailSoftware upgrade failure notice
TRAP-TYPE
.1.3.6.1.4.1.482.0.1301
lcErrSmSwUpgradeFailResetSoftware upgrade failure occured resulting in a reset
TRAP-TYPE
.1.3.6.1.4.1.482.0.1302
lcErrSmSwUpgradeCompletionSoftware Upgrade Succeeded
TRAP-TYPE
.1.3.6.1.4.1.482.0.1303
lcErrSmSwUpgradeCancelledSoftware upgrade was cancelled
TRAP-TYPE
.1.3.6.1.4.1.482.0.1304
lcErrSmSwUpgradeOverrideSoftware Upgrade was cancelled by a new request
TRAP-TYPE
.1.3.6.1.4.1.482.0.1305
lcErrSmFlashProgrammingErrorSoftware upgrade flash programming failure
TRAP-TYPE
.1.3.6.1.4.1.482.0.1306
lcErrSmFlashProgrammingErrorResetSoftware upgrade flash programming failure resulting in a reset
TRAP-TYPE
.1.3.6.1.4.1.482.0.1307
lcErrSmFlashEraseFailSoftware upgrade flash erase failure
TRAP-TYPE
.1.3.6.1.4.1.482.0.1308
lcErrSmFlashEraseFailResetSoftware upgrade flash erase failure resulting in a reset
TRAP-TYPE
.1.3.6.1.4.1.482.0.1309
lcErrSmFlashCorruptionResetSoftware Upgrade: unknown flash id
TRAP-TYPE
.1.3.6.1.4.1.482.0.1310
lcErrSmFlashBlockInvalidResetSoftware Upgrade: invalid flash runtime info block
TRAP-TYPE
.1.3.6.1.4.1.482.0.1311
lcErrSmSwUpgradeTftpErrorSoftware upgrade failed, tftp error, upgrade is aborted
TRAP-TYPE
.1.3.6.1.4.1.482.0.1312
lcErrSmSwUpgradeTftpErrorResetSoftware upgrade failed due to a tftp error, system is reset to retry
TRAP-TYPE
.1.3.6.1.4.1.482.0.1313
lcErrSmSwUpgradeAllocFailSoftware upgrade NU_Alloc_Memory failure
TRAP-TYPE
.1.3.6.1.4.1.482.0.1314
lcErrSmSwUpgradeGenericErrorSoftware Upgrade error reported
TRAP-TYPE
.1.3.6.1.4.1.482.0.1315
lcErrSmSwUpgradeProductErrorProduct code in software upgrade file is not correct for the system being upgraded
TRAP-TYPE
.1.3.6.1.4.1.482.0.1316
lcErrSmSwUpgradeTftpMsgThere was a TFTP error during software upgrade. Possible errors are that the upgrade file does not exist, or the docsDevSwServer address is not correct, or the transfer failed in the middle of the transfer.
TRAP-TYPE
.1.3.6.1.4.1.482.0.1317
lcErrScnBadFrequencyDirected by provisioning to unreachable downstream frequency
TRAP-TYPE
.1.3.6.1.4.1.482.0.1400
lcScnTunerBrokenTuner Failure
TRAP-TYPE
.1.3.6.1.4.1.482.0.1401
lcScnTunerHungTuner is not responding
TRAP-TYPE
.1.3.6.1.4.1.482.0.1402
lcScnStartUpBegin Scanning
TRAP-TYPE
.1.3.6.1.4.1.482.0.1403
lcErrCliGeneralConsole Interface failure
TRAP-TYPE
.1.3.6.1.4.1.482.0.1500
lcInfoCliLoginConsole Interface user logged in
TRAP-TYPE
.1.3.6.1.4.1.482.0.1501
lcInfoCliLogoutConsole Interface user logged out
TRAP-TYPE
.1.3.6.1.4.1.482.0.1502
lcInfoCliLoginFailConsole Interface user login fail
TRAP-TYPE
.1.3.6.1.4.1.482.0.1503
lcInfoCliSessionTimeoutConsole Interface user timed out
TRAP-TYPE
.1.3.6.1.4.1.482.0.1504
lcInfoCliCommandConsole Interface command
TRAP-TYPE
.1.3.6.1.4.1.482.0.1505
lcInfoCliConsoleSnmpSetConsole Interface user snmp set
TRAP-TYPE
.1.3.6.1.4.1.482.0.1506
lcInfoCliTelnetSnmpSetTelnet Interface user snmp set
TRAP-TYPE
.1.3.6.1.4.1.482.0.1507
lcErrBcmInitFailureCould not initialize network interface parts
TRAP-TYPE
.1.3.6.1.4.1.482.0.1600
lcMsgNoPowerTablesPower/correction tables for the BCM3037 were not found in the manufacturing block as expected. The power and correction were estimated instead.
TRAP-TYPE
.1.3.6.1.4.1.482.0.1601
lcErrBcmReceiverHwRevThe receiver has an improper hardware revision.
TRAP-TYPE
.1.3.6.1.4.1.482.0.1602
lcErrCmMtdMAX Transit Delay on CATV
TRAP-TYPE
.1.3.6.1.4.1.482.0.1700
lcErrCmPciParityPCI Parity Error
TRAP-TYPE
.1.3.6.1.4.1.482.0.1701
lcErrMibSnmpResetSystem Reset by docsDevResetNow MIB variable
TRAP-TYPE
.1.3.6.1.4.1.482.0.1800
lcMcastJoinGenerated when lcMcastControl is set to trap(4) and an initial IGMP Report is received from the subscriber network.
TRAP-TYPE
.1.3.6.1.4.1.482.0.1850
lcErrGalPciParityPCI parity error detected
TRAP-TYPE
.1.3.6.1.4.1.482.0.1900
lcErrBpEnabledBaseline Privacy configuration settings are present.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2000
lcErrBpHardwareInitFailureFailure initializing hardware.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2001
lcErrBpKeyWriteFailureFailure writing traffic key to hardware.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2002
lcErrBpVectWriteFailureFailure writing initialization vector to hardware.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2003
lcErrBpHardcodedRsaKeyPairUsing hardcoded RSA key pair since flash key invalid.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2004
lcErrHebpAuthEncryptFailureFailure encrypting authorization key.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2100
lcErrHebpHardwareInitFailureFailure initializing hardware.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2101
lcErrHebpKeyWriteFailureFailure writing traffic key to hardware.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2102
lcErrHebpVectWriteFailureFailure writing initialization vector to hardware.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2103
lcErrHebpMacsDontMatchThe Source MAC Address of a BP Key Management message is not equivalent to the MAC Address passed in the message's CM identification field.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2104
lcErrHebpAttemptedPubKeyChangeA CM has made a BP Authorization Request but a CM with the same MAC address, and different public key, is already authorized.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2105
lcErrCruInitFailureThe CMTS hardware could not be initialized due to an FPGA programming failure.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2200
lcErrMfgTlvReadErrorError reading TLV type from flash.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2300
lcErrUcNoHwThe CMTS hardware could not be initialized because the up-converter was not detected.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2400
lcErrUcNoCalThe CMTS hardware could not be initialized because the up-converter calibration data could not be found.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2401
lcErrUcNoLockThe CMTS hardware could not lock onto the downstream frequency.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2402
lcErrUcPowerSupplyThe CMTS up-converter power supply failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.2403
lcErrUcOutputPowerThe CMTS downstream output power could not reach the desired level
TRAP-TYPE
.1.3.6.1.4.1.482.0.2404
lcErrPacDsConfigFailureThe downstream channel configuration is incompatible with the CMTS hardware; the downstream channel is disabled
TRAP-TYPE
.1.3.6.1.4.1.482.0.2500
lcErrPacUsConfigFailureThe upstream channel configuration is incompatible with the CMTS hardware; the upstream channel is disabled
TRAP-TYPE
.1.3.6.1.4.1.482.0.2501
lcPacDsCenterFreqChangeDownstream Center Frequency has been changed
TRAP-TYPE
.1.3.6.1.4.1.482.0.2502
lcPacDsBandwidthChangeDownstream Channel Width has been changed
TRAP-TYPE
.1.3.6.1.4.1.482.0.2503
lcPacDsModulationChangeDownstream Modulation Type has been changed
TRAP-TYPE
.1.3.6.1.4.1.482.0.2504
lcPacDsInterleaveChangeDownstream Interleave has been changed
TRAP-TYPE
.1.3.6.1.4.1.482.0.2505
lcPacDsPowerChangeDownstream Channel Power has been changed
TRAP-TYPE
.1.3.6.1.4.1.482.0.2506
lcErrTestMacHeaderTest being run - MAC Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.2600
lcErrTestEhdr20Test being run - Extended Header
TRAP-TYPE
.1.3.6.1.4.1.482.0.2601
lcIngressAvoidanceActionTakenThe ingress avoidance feature has automatically changed frequency, modulation profile and bandwidth
TRAP-TYPE
.1.3.6.1.4.1.482.0.2700
lcErrCruFrontFanStatusOffFront fan is not functioning properly or is powered down.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2800
lcErrCruFrontFanStatusOnFront fan is now functioning properly.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2801
lcErrCruMiddleFanStatusOffMiddle fan is not functioning properly or is powered down.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2802
lcErrCruMiddleFanStatusOnMiddle fan is now functioning properly.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2803
lcErrCruBackFanStatusOffBack fan is not functioning properly or is powered down.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2804
lcErrCruBackFanStatusOnBack fan is now functioning properly.
TRAP-TYPE
.1.3.6.1.4.1.482.0.2805
lcErrTelnetMallocFailureTelnet reports: TELNET_malloc() memory allocation failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.3000
lcErrTelnetFreeFailureTelnet reports: TELNET_free() memory release failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.3001
lcErrTelnetTcbCreateFailureTelnet reports: TELNET_Init() tcb_create() failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.3002
lcErrTelnetTnCreateListenerFailureTelnet reports: TELNET_Init() tn_create_listener() failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.3003
lcErrTelnetTcpStartFailureTelnet reports: TELNET_Init() tcp_start() failed
TRAP-TYPE
.1.3.6.1.4.1.482.0.3004
lancityMcnsMibThis is the portion of the Lancity enterprise MIB that applies to MCNS cable modems and related devices.
MODULE-IDENTITY
.1.3.6.1.4.1.482.60
lancityMcnsProducts
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.1
lancityMcnsProdIdCMTS
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.1.1
lancityMcnsProdIdCM
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.1.2
lccmtsif
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.2
lcCmtsUpstreamTableDefines properties of upstream channels, from the CMTS.
SEQUENCE OF LcCmtsUpstreamEntry
.1.3.6.1.4.1.482.60.2.1
lcCmtsUpstreamEntryDefines properties of an upstream channel, from the CMTS.
LcCmtsUpstreamEntry
.1.3.6.1.4.1.482.60.2.1.1
lcCmtsUpMinimumMapSizeMinimum number of slots to be mapped in each Map PDU.rw
INTEGER
.1.3.6.1.4.1.482.60.2.1.1.1
lcCmtsUpMaximumMapSizeMaximum number of slots to be mapped in each Map PDU.rw
INTEGER
.1.3.6.1.4.1.482.60.2.1.1.2
lcCmtsUpContentionPerMapThe number of mini-slots allotted to contention (REQ or REQ-DATA) per MAP PDU.rw
INTEGER
.1.3.6.1.4.1.482.60.2.1.1.3
lcCmtsUpRequestDataAllowedSpecifies whether or not the CMTS will allow contention data on this upstream interface.rw
Enumeration
.1.3.6.1.4.1.482.60.2.1.1.4
lcCmtsUpMaxDataInContentionThe number of mini-slots that may be used for a single upstream contention transmission.rw
INTEGER
.1.3.6.1.4.1.482.60.2.1.1.5
lcCmtsUpInitialRangingIntervalThe duration, in microseconds, of the initial ranging interval. This interval is used by unranged modems to enter the network, and so must be long enough to admit the most distant modem.rw
INTEGER UNITS "microseconds"
.1.3.6.1.4.1.482.60.2.1.1.6
lcCmtsUpHighPriorityThresholdWeighting of high priority queue is-a-vis normal priority queue.rw
INTEGER
.1.3.6.1.4.1.482.60.2.1.1.7
lcCmtsUpGuaranteedThresholdPermitted aggregate CIR, as a percentage of the overall channel bandwidth.rw
INTEGER
.1.3.6.1.4.1.482.60.2.1.1.8
lcCmtsUpPublicationDelayA sum of architectural constants, parameters, and network status (RTD) that governs the difference between the publication time of the MAP and its effectiveness.ro
INTEGER UNITS "microseconds"
.1.3.6.1.4.1.482.60.2.1.1.9
lcCmtsUpNFlowControlledMapsThe number of Map PDUs that were generated under flow-controlled (prioritized) conditions.ro
Counter32
.1.3.6.1.4.1.482.60.2.1.1.10
lcCmtsUpNNonFlowControlledMapsThe number of Map PDUs that were generated under FIFO conditions.ro
Counter32
.1.3.6.1.4.1.482.60.2.1.1.11
lcCmtsUpChannelPowerThe CMTS receiver input power level, which is the nominal receive power level for upstream data. This value will be automatically scaled by the CMTS if the channel's width is changed.rw
TenthdBmV
.1.3.6.1.4.1.482.60.2.1.1.12
lcCmtsUpInputPowerWindowThe CMTS receiver input power window (+/- tenths dB) at which a CM is allowed to operated in. This value has the range of 20 -150 tenths of dB which represents windows +/- 2 dB to a window of +/- 15 dB. The theoretical upper limit of this range is 9 dB.rw
TenthdBmV
.1.3.6.1.4.1.482.60.2.1.1.13
lcCmtsCurrentTempCurrent temperature of a CMTS device in degrees Celsius.ro
INTEGER
.1.3.6.1.4.1.482.60.2.2
lcCmtsHighTempThresholdHigh temperature threshold limit of a CMTS device in degrees Celsius, above which an event occurs to signal that the threshold has been exceeded. The device temperature is read once per minute and compared to this threshold value. A trap is sent out if the event's priority indicates that a trap is to be sent (refer to the docsDevEvControlTable object in DOCS-CABLE-DEVICE-MIB). The priority of this event is critical(3).rw
INTEGER
.1.3.6.1.4.1.482.60.2.3
lccmtsUpstreamIngressAvoidance
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.2.4
lcCmtsUpstreamIngressAvoidanceEnableTableDefines which upstreams are enabling this feature and which metrics to use.
SEQUENCE OF LcCmtsIngressAvoidanceEnableEntry
.1.3.6.1.4.1.482.60.2.4.1
lcCmtsIngressAvoidanceEnableEntryDefines which upstreams are enabling this feature and which metrics to use.
LcCmtsIngressAvoidanceEnableEntry
.1.3.6.1.4.1.482.60.2.4.1.1
lcCmtsIngressAvoidanceEnableEnable Ingress Avoidance for the Upstream.rw
Enumeration
.1.3.6.1.4.1.482.60.2.4.1.1.1
lcCmtsMetric1EnableEnable the metric associated with Ingress Avoidance.rw
Enumeration
.1.3.6.1.4.1.482.60.2.4.1.1.2
lcCmtsIngressAvoidanceFrequencyConfigTableDefines the provisioned frequencies per carrier path.
SEQUENCE OF LcCmtsIngressAvoidanceFrequencyConfigEntry
.1.3.6.1.4.1.482.60.2.4.2
lcCmtsIngressAvoidanceFrequencyConfigEntryDefines which upstreams are enabling this feature and which metrics to use.
LcCmtsIngressAvoidanceFrequencyConfigEntry
.1.3.6.1.4.1.482.60.2.4.2.1
lcCmtsCarrierPathIndexCarrier path index for the frequency ranges.
INTEGER
.1.3.6.1.4.1.482.60.2.4.2.1.1
lcCmtsFreqConfigIndexIndex for frequency ranges for each carrier path.
INTEGER
.1.3.6.1.4.1.482.60.2.4.2.1.2
lcCmtsFreqAvailableAllow frequency range to be used for the carrier path.rw
Enumeration
.1.3.6.1.4.1.482.60.2.4.2.1.3
lcCmtsStartFrequencyBeginning frequency in the frequency range (Hz). Range must be within the 5-42 MHz range and start must be less than or equal to stop frequency.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.2.1.4
lcCmtsStopFrequencyEnd frequency in the frequency range (Hz). Range must be within the 5-42 MHz range and start must be less than or equal to stop frequency.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.2.1.5
lcCmtsIngressAvoidanceChangePrefTableDefines carrier paths (Physical Connectivity) and channel groups for each upstream.
SEQUENCE OF LcCmtsIngressAvoidanceChangePrefEntry
.1.3.6.1.4.1.482.60.2.4.3
lcCmtsIngressAvoidanceChangePrefEntryDefines carrier paths (Physical Connectivity) and channel groups for each upstream.
LcCmtsIngressAvoidanceChangePrefEntry
.1.3.6.1.4.1.482.60.2.4.3.1
lcCmtsChangePreferenceDefines which type of change is the prefered change if ingress avoidance detects a problem in the current configuration.rw
Enumeration
.1.3.6.1.4.1.482.60.2.4.3.1.1
lcCmtsIngressAvoidanceThresholdTableDefines threshold for each of the ingress avoidance available metrics.
SEQUENCE OF LcCmtsIngressAvoidanceThresholdEntry
.1.3.6.1.4.1.482.60.2.4.4
lcCmtsIngressAvoidanceThresholdEntryDefines threshold for each of the ingress avoidance available metrics.
LcCmtsIngressAvoidanceThresholdEntry
.1.3.6.1.4.1.482.60.2.4.4.1
lcCmtsMetric1GreenToYellowDefines the green to yellow threshold for a particular metric.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.4.1.1
lcCmtsMetric1YellowToRedDefines the yellow to red threshold for a particular metric. A drop below this level will cause an ingress avoidance action if the metric is enabled.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.4.1.2
lcCmtsIngressAvoidanceProfileTableDefines with profile in the Tranmission table will be used for ingress avoidance. The order from 1-3 is the desired order for profile use.
SEQUENCE OF LcCmtsIngressAvoidanceProfileEntry
.1.3.6.1.4.1.482.60.2.4.5
lcCmtsIngressAvoidanceProfileEntryDefines with profile in the Tranmission table will be used for ingress avoidance. The order from 1-3 is the desired order for profile use.
LcCmtsIngressAvoidanceProfileEntry
.1.3.6.1.4.1.482.60.2.4.5.1
lcCmtsProfileCarrierPathIndexCarrier path index for the profile table.
INTEGER
.1.3.6.1.4.1.482.60.2.4.5.1.1
lcCmtsProfilePreferenceProfile index per carrier path.
INTEGER
.1.3.6.1.4.1.482.60.2.4.5.1.2
lcCmtsStatusDefines whether or not the particular profile is enabled for use in ingress avoidance.rw
Enumeration
.1.3.6.1.4.1.482.60.2.4.5.1.3
lcCmtsTransmissionProfileIndexDescribes the index into the transmission profile table.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.5.1.4
lcCmtsIngressAvoidanceTxProfileTableDefines Modulation Profile and Bandwidth. Coding Efficiency is calculated based on the entries.
SEQUENCE OF LcCmtsIngressAvoidanceTxProfileEntry
.1.3.6.1.4.1.482.60.2.4.6
lcCmtsIngressAvoidanceTxProfileEntryDefines with profile in the Tranmission table will be used for ingress avoidance. The order from 1-3 is the desired order for profile use.
LcCmtsIngressAvoidanceTxProfileEntry
.1.3.6.1.4.1.482.60.2.4.6.1
lcCmtsTxProfileIndexIndex for the transmission profile table.
INTEGER
.1.3.6.1.4.1.482.60.2.4.6.1.1
lcCmtsModulationProfileIndexIndex into the MCNS Upstream Modulation Table.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.6.1.2
lcCmtsBandwidthBandwidth to be used with the modulation profile selected.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.6.1.3
lcCmtsCodingEfficiencyCoding efficiency is calculated based on the modulation profile and bandwidth selected. This number represents information bytes/second for the given settings. This calculation in based on short and long data grants and a min and max size packet transmitted for each type of grant.ro
INTEGER
.1.3.6.1.4.1.482.60.2.4.6.1.4
lcCmtsIngressAvoidanceMetricConfigTableDefines the aging multipliers and calculation timers for each metric.
SEQUENCE OF LcCmtsIngressAvoidanceMetricConfigEntry
.1.3.6.1.4.1.482.60.2.4.7
lcCmtsIngressAvoidanceMetricConfigEntryDefines the aging multipliers and calculation timers for each metric.
LcCmtsIngressAvoidanceMetricConfigEntry
.1.3.6.1.4.1.482.60.2.4.7.1
lcCmtsMetricIndexMetric Index.
INTEGER
.1.3.6.1.4.1.482.60.2.4.7.1.1
lcCmtsAgingMultiplierMetric aging multilpler in hundreths.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.7.1.2
lcCmtsCalculationTimerFrequency at which metrics should be calculated in milliseconds.rw
INTEGER
.1.3.6.1.4.1.482.60.2.4.7.1.3
lcCmtsIngressAvoidanceFreqStatusTableThis table is a status table for all frequency ranges allowed per carrier path.
SEQUENCE OF LcCmtsIngressAvoidanceFreqStatusEntry
.1.3.6.1.4.1.482.60.2.4.8
lcCmtsIngressAvoidanceFreqStatusEntryThis table is a status table for all frequency ranges allowed per carrier path.
LcCmtsIngressAvoidanceFreqStatusEntry
.1.3.6.1.4.1.482.60.2.4.8.1
lcCmtsFreqStatusCarrierPathIndexCarrier Paths for each frequency.
INTEGER
.1.3.6.1.4.1.482.60.2.4.8.1.1
lcCmtsFreqStatusFreqIndexFrequency index for carrier path.
INTEGER
.1.3.6.1.4.1.482.60.2.4.8.1.2
lcCmtsFreqStatusFreqFrequency in Hz.ro
INTEGER
.1.3.6.1.4.1.482.60.2.4.8.1.3
lcCmtsFreqStatusFcDenotes whether or not this is a center frequency.ro
Enumeration
.1.3.6.1.4.1.482.60.2.4.8.1.4
lcCmtsFreqStatusAvailableDenotes whether or not this is available. no - frequency is not available for ingress avoidance. yes - frequency is not being used and is available for ingress avoidance. inuse - frequency is actively being used by an upstream. reserved - frequency is reserved by an upstream channel which is currently down.ro
Enumeration
.1.3.6.1.4.1.482.60.2.4.8.1.5
lcCmtsFreqStatusStatusDenotes status of frequency. Large integers represents the channel is extremely bad. Zero/UNK represents a Good frequency to try.ro
Enumeration
.1.3.6.1.4.1.482.60.2.4.8.1.6
lcCmtsFreqStatusTimeLastUsedDenotes time since this frequency was last used.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.482.60.2.4.8.1.7
lcCmtsFreqStatusUpTimeDenotes up time last time used or current up time on this frequency.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.482.60.2.4.8.1.8
lcCmtsUpstreamIngressAvoidanceHealthTableDisplays the health of each upstream channel.
SEQUENCE OF LcCmtsIngressAvoidanceHealthEntry
.1.3.6.1.4.1.482.60.2.4.9
lcCmtsIngressAvoidanceHealthEntryDisplays the health of each upstream channel.
LcCmtsIngressAvoidanceHealthEntry
.1.3.6.1.4.1.482.60.2.4.9.1
lcCmtsHealthProfileUpstream Ingress Avoidance Profile Index.ro
INTEGER
.1.3.6.1.4.1.482.60.2.4.9.1.1
lcCmtsHealthFcCenter frequency for the upstream channel.ro
INTEGER
.1.3.6.1.4.1.482.60.2.4.9.1.2
lcCmtsHealthUpTimeTime the channel has been up in this configuration.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.482.60.2.4.9.1.3
lcCmtsMetric1StatusCurrent state of the upstream channel using the thresholds set in the threshold table.ro
Enumeration
.1.3.6.1.4.1.482.60.2.4.9.1.4
lcCmtsMetric1ValueCurrent value for the metric.ro
INTEGER
.1.3.6.1.4.1.482.60.2.4.9.1.5
lcCmtsMultiUsConfigTableDefines carrier paths (Physical Connectivity) and channel groups for each upstream.
SEQUENCE OF LcCmtsMultiUsConfigEntry
.1.3.6.1.4.1.482.60.2.5
lcCmtsMultiUsConfigEntryDefines carrier paths (Physical Connectivity) and channel groups for each upstream.
LcCmtsMultiUsConfigEntry
.1.3.6.1.4.1.482.60.2.5.1
lcCmtsCarrierPathDefines physical connectivity to each upstream receiver ifIndexes with the same carrier path cannot operate on the same frequencies.rw
INTEGER
.1.3.6.1.4.1.482.60.2.5.1.1
lcCmtsChannelGroupDefines which upstreams must operate on the same frequencies. Value of zero means that a given upstream is independant of all other upstream channels. Any upstream with the same value must operate on the same frequency.rw
INTEGER
.1.3.6.1.4.1.482.60.2.5.1.2
lcCmtsFrontFanOnCurrent on/off state of the CMTS fan closest to the front of the chassis. If the fan is on, true is returned. If the fan is off, false is returned.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.2.6
lcCmtsMiddleFanOnCurrent on/off state of the CMTS fan closest to the middle of the chassis. If the fan is on, true is returned. If the fan is off, false is returned.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.2.7
lcCmtsBackFanOnCurrent on/off state of the CMTS fan closest to the back of the chassis. If the fan is on, true is returned. If the fan is off, false is returned.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.2.8
lccmtsifconfig
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.2.9
lcCmtsAnnexFEC mode - Default is Annex B which is the North American Standard Annex A is used for Euro DOCSIS.rw
Enumeration
.1.3.6.1.4.1.482.60.2.9.1
lcCmtsFrequencySplitUpstream/Downstream Frequency Split. The standard North American split is 5-42/50-862 MHz. Euro DOCSIS Split is 5-65/100-862 MHz.rw
Enumeration
.1.3.6.1.4.1.482.60.2.9.2
lcEvSyslog2The IP address of a 2nd Syslog server. If 0.0.0.0, syslog transmission is inhibited.rw
IpAddress
.1.3.6.1.4.1.482.60.2.10
lcEvSyslog3The IP address of a 3rd Syslog server. If 0.0.0.0, syslog transmission is inhibited.rw
IpAddress
.1.3.6.1.4.1.482.60.2.11
lcCpeMacToCmMacTableThis is a table to provide a mechanism for finding the MAC address of the CM to which a CPE device is connected. The table is indexed by the MAC address of the device whose associated CM is being sought. There is exactly one row in this table for each MAC address learned by the CMTS. It is possible to have entries in this table that have no associated CM MAC address and those entries are denoted by a CM MAC address of 00 00 00 00 00 00.
SEQUENCE OF LcCpeMacToCmMacEntry
.1.3.6.1.4.1.482.60.2.16
lcCpeMacToCmMacEntryA row in the lcCpeMacToCmMacTable. An entry in this table exists for each MAC address that has been learned by the CMTS and is present in it Forwarding Database.
LcCpeMacToCmMacEntry
.1.3.6.1.4.1.482.60.2.16.1
lcCpeMacA MAC address in the CMTS Forwarding Database. This is the index into the lcCpeMacToCmMacTable.
MacAddress (SNMPv2-TC)
.1.3.6.1.4.1.482.60.2.16.1.1
lcCmMacThe MAC address of the CM to which the index MAC address is connected. For entries learned on the Ethernet side of the CMTS bridge this value will be 00 00 00 00 00 00 which indicates no CM associativity. For a CM MAC entry this value will be the same as the index, that is the MAC address of the CM itself. For a CPE device on the Cable side of the CMTS bridge this value will be the MAC address of the CM to which that CPE device is connected.ro
MacAddress (SNMPv2-TC)
.1.3.6.1.4.1.482.60.2.16.1.2
lcCmCountsTableThis is a table to provide the number of active and registered modems on each upstream and for the entire system. Active modems are those that have performed at least an initial ranging and have not yet been ranging-aborted, ranging-timedout, or de-registered. This table is populated from the Registrar CM entries functions.
SEQUENCE OF LcCmCountsEntry
.1.3.6.1.4.1.482.60.2.19
lcCmCountsEntryA row in the lcCmCountsTable. An entry in this table exists for each upstream channel on the CMTS (1-8) and for the system totals.
LcCmCountsEntry
.1.3.6.1.4.1.482.60.2.19.1
lcCmCountsRowNumA row index into the lcCmCountsTable. Indices 1 through 8 correspond to upstream channels and index 9 corresponds to the system totals.
Counter32
.1.3.6.1.4.1.482.60.2.19.1.1
lcActiveCmCountsThe number of CMs on this channel that have performed an initial ranging and are still marked as operational by the CMTS.ro
Counter32
.1.3.6.1.4.1.482.60.2.19.1.2
lcRegisteredCmCountsThe number of CMs on this channel that are currently registered with the CMTS.ro
Counter32
.1.3.6.1.4.1.482.60.2.19.1.3
lccmif
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.3
lcifcommon
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.4
lccmtsdevice
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5
lccmtsProvisioning
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.1
lcProvisioningControlControls the use of file-based provisioning by the CMTS. If set to: use-dhcp-and-tftp(1) the CMTS will use DHCP to find its IP address, subnet mask, default router, and TFTP server. Configuration parameters will be provisioned from a TFTP'ed parameter file, use-dhcp (2) DHCP will be used to find the IP address, subnet mask, and defaultrouter, but all other parameters will come from NVRAM, use-tftp (3) The CMTS will use NVRAM for its IP address, but other configured parameters will be loaded via TFTP, use-nvram (4) All operational parameters are taken from nonvolatile RAM.rw
Enumeration
.1.3.6.1.4.1.482.60.5.1.1
lcConfigIpAddressThe IP address of the CMTS; provides a writable equivalent of ipAdEntAddr. If set to null (0.0.0.0), the address must be provided through DHCP.rw
IpAddress
.1.3.6.1.4.1.482.60.5.1.2
lcConfigIpSubnetThe subnet mask corresponding to lcConfigIpAddress; provides a writable equivalent of ipAdEntNetMask.rw
IpAddress
.1.3.6.1.4.1.482.60.5.1.3
lcConfigIpGatewayThe Gateway address defines the next hop router (forwarder) destination for non-local IP packets.rw
IpAddress
.1.3.6.1.4.1.482.60.5.1.4
lcConfigTftpAddressThe IP address of the TFTP Server supplying provisioning configuration data.rw
IpAddress
.1.3.6.1.4.1.482.60.5.1.5
lcConfigTftpFilenameThe default filename on the TFTP Server for acquiring provisioning configuration data (may be overridden by DHCP).rw
DisplayString
.1.3.6.1.4.1.482.60.5.1.6
lcConfigTimeServerAddressThe IP address of the Time Server (RFC868) supplying provisioning time.rw
IpAddress
.1.3.6.1.4.1.482.60.5.1.7
lcConfigTimeoffsetTime offset in seconds to apply to provisioned GMT timerw
INTEGER
.1.3.6.1.4.1.482.60.5.1.8
lcConfigSNTPAddressThe IP Address of the SNTP Timer Server supplying provisioning timerw
IpAddress
.1.3.6.1.4.1.482.60.5.1.9
lcSerialPortTableConfiguration of system serial port(s)
SEQUENCE OF LcSerialPortEntry
.1.3.6.1.4.1.482.60.5.2
lcSerialPortEntryInformation for each serial port.
LcSerialPortEntry
.1.3.6.1.4.1.482.60.5.2.1
lcSerialPortNumberIndex for this table.
INTEGER
.1.3.6.1.4.1.482.60.5.2.1.1
lcSerialPortBaudRateBaud rate configured on this Serial Portrw
Enumeration
.1.3.6.1.4.1.482.60.5.2.1.2
lcSerialPortDataBitsNumber of data bits configured on this Serial Portrw
INTEGER
.1.3.6.1.4.1.482.60.5.2.1.3
lcSerialPortParityType of parity configured on this Serial Portrw
Enumeration
.1.3.6.1.4.1.482.60.5.2.1.4
lcSerialPortStopBitsNumber of stop bits configured on this Serial Portrw
Enumeration
.1.3.6.1.4.1.482.60.5.2.1.5
lcSerialPortModemEnableEnable the Serial Port to run with modem leads enabledrw
Enumeration
.1.3.6.1.4.1.482.60.5.2.1.6
lcModemVendorTableThis table defines modems that are allowed to register with this CMTS. Modem vendors are identified by the OUI portion of the MAC address used by the modem for registration. In order to allow further differentiation based on particular models, the entire MAC address may be masked and used to screen registrations.
SEQUENCE OF LcModemVendorEntry
.1.3.6.1.4.1.482.60.5.3
lcModemVendorEntryThis entry identifies a class of modems which are allowed to register with this CMTS.
LcModemVendorEntry
.1.3.6.1.4.1.482.60.5.3.1
lcModemVendorIndexAn arbitrary index defining an instance of this entry. Ordering is not meaningful.
INTEGER
.1.3.6.1.4.1.482.60.5.3.1.1
lcModemVendorControlThis object controls the creation and deletion of rows in this table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.482.60.5.3.1.2
lcModemVendorMacAddressWhen masked, identifies a group of modems that are allowed to register at this CMTS. Note that the LSB of the first octet is the multicast bit; since it cannot identify a modem, it is defined to be zero.rw
MacAddress (SNMPv2-TC)
.1.3.6.1.4.1.482.60.5.3.1.3
lcModemVendorMaskApplied to the MAC address to identify which modems are allowed to register at this CMTS. Ordinarily, the OUI portion is used to identify particular vendors, but arbitrary masks can be used. The LSB of the first octet is the multicast bit and is defined to be zero.rw
MacAddress (SNMPv2-TC)
.1.3.6.1.4.1.482.60.5.3.1.4
lccmtsDPStatistics
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.4
lcDPStatisticsIntervalControls the interval at which data rates are calculated on the CMTS.rw
INTEGER
.1.3.6.1.4.1.482.60.5.4.1
lcDPStatisticsTableThe table contains the last calculated statistics for data rates for each port on the CMTS.
SEQUENCE OF LcDPStatisticsEntry
.1.3.6.1.4.1.482.60.5.4.2
lcDPStatisticsEntryThe Entry contains the last calculated statistics for data rates for one port on the CMTS.
LcDPStatisticsEntry
.1.3.6.1.4.1.482.60.5.4.2.1
lcDPStatisticsTxFrameRateThe last calculated frames per second transmitted on this port.ro
INTEGER
.1.3.6.1.4.1.482.60.5.4.2.1.1
lcDPStatisticsRxFrameRateThe last calculated frames per second received on this port.ro
INTEGER
.1.3.6.1.4.1.482.60.5.4.2.1.2
lcDPStatisticsTxOctetRateThe last calculated octets per second transmitted on this port.ro
INTEGER
.1.3.6.1.4.1.482.60.5.4.2.1.3
lcDPStatisticsRxOctetRateThe last calculated octets per second received on this port.ro
INTEGER
.1.3.6.1.4.1.482.60.5.4.2.1.4
lccmtsDPConfiguration
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.5
lcForwardingModeControls the Forwarding Data Base Learning Mode. If set to none(1), the CMTS uses transparent learning. If set to dhcp-arp(2), the CMTS uses Layer-3 switching based on DHCP and ARP. Mode dhcp-arp(2) is not allowed if FunnelMode is enabled(2). The default is none(1).rw
Enumeration
.1.3.6.1.4.1.482.60.5.5.1
lcProxyArpControls Proxy ARP on the CMTS when it is in transparent learning mode. If set to enable(1), the CMTS responds to an ARP received from the Cable when the IP Address is known and responds to an ARP received from the Ethernet when the IP Address in known to be on the Cable. If set to disable(2), CMTS does not respond to any ARPs. Proxy ARP cannot be enabled if FunnelMode is enabled(2). The default is disabled(2).rw
Enumeration
.1.3.6.1.4.1.482.60.5.5.2
lcProxyArpTimeoutControls the timeout (in seconds) of the Proxy Arp cache entries.rw
INTEGER
.1.3.6.1.4.1.482.60.5.5.3
lcArpSpoofingProtectionControls ARP Spoofing Protection on the CMTS when it is in layer-3 switching mode (Mode B). CMTS must be in MODE B for ARP Spoofing Protection to work. If set to enable(1), the CMTS will not forward or glean information from ARP packets received from the Cable interface whose sender's IP address does not match the IP address for the sender's hardware address as learned from DHCP gleaning. If set to disable(2), the CMTS will forward the ARP packet and will update its ARP cache with the IP address in the ARP.rw
Enumeration
.1.3.6.1.4.1.482.60.5.5.4
lcFunnelModeControls whether or not the CMTS is in Funnel Mode. If set to enable(1), all upstream data packets are sent out the ethernet port. If set to disable(2), all packets are processed normally. Funnel mode is not allowed if ProxyArp is enabled(1) or ForwardingMode is not none(1). The default is disabled(2).rw
Enumeration
.1.3.6.1.4.1.482.60.5.5.5
lcDeregCmAgeTimeThe time-to-live of a CM entry in the FDB for a CM that has been de-registered. This interval is expressed as the number of seconds between de-registration and removal from the FDB. If the CM ranges during this time interval aging is cancelled. The default interval is 172800 seconds (48 hours).rw
INTEGER
.1.3.6.1.4.1.482.60.5.5.6
lcRngNotRegCmAgeTimeThe time-to-live of a CM entry in the FDB for a CM that has performed an initial ranging request but has not yet completed registration. This interval is expressed as the number of seconds between receipt of the initial ranging request and removal from the FDB. If the CM registers this time interval is cancelled. The default interval is 120 seconds.rw
INTEGER
.1.3.6.1.4.1.482.60.5.5.7
lcUsedot1dTpAgingTimeThis object determines whether the default time-to-live of an entry in the FDB as specified by the dot1dTpAgingTime object is to be used or not. This setting is only meaningful for FDB entries learned on the Cable interface when Mode B (DHCP-ARP) forwarding is enabled. If enabled in Mode B, then the DHCP lease time is NOT used to specify the aging time for entries, but rather the setting for dot1dTpAgingTime is used. This object has no effect in Mode A (transparent) bridging mode. The default is disable (do NOT use dot1dTpAgingTime).rw
Enumeration
.1.3.6.1.4.1.482.60.5.5.8
lccmtsHwRevisions
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.6
lccmtsHwRevArbCPLDThe hardware revision number for the Arb CPLD chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.1
lccmtsHwRevTxCPLDThe hardware revision number for the Tx CPLD chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.2
lccmtsHwRevAFFPGAThe hardware revision number for the AFFPGA chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.3
lccmtsHwRevGT64010The hardware revision number for the Galileo GT-64010 chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.4
lccmtsHwRevPLX9080The hardware revision number for the PLX PCI 9080 chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.5
lccmtsHwRevBCM3210The hardware revision number for the Broadcom 3210 chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.6
lccmtsHwRevBCM3033The hardware revision number for the Broadcom 3033 chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.7
lccmtsHwRevSunsetThe hardware revision number for the Sunset transmitter.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.8
lccmtsHwRevDEC21143The hardware revision number for the DEC 21143 Ethernet chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.9
lccmtsHwRevLXT970AThe hardware revision number for the LXT970 Ethernet PHY A chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.10
lccmtsHwRevLXT970BThe hardware revision number for the LXT970 Ethernet PHY B chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.11
lccmtsHwRevRfRxTableThe table contains hardware revision numbers for the chips of each upstream RF receiver channel in the CMTS.
SEQUENCE OF LccmtsHwRevRfRxEntry
.1.3.6.1.4.1.482.60.5.6.12
lccmtsHwRevRfRxEntryThe table contains hardware revision numbers for the chips of one upstream RF receiver channel in the CMTS.
LccmtsHwRevRfRxEntry
.1.3.6.1.4.1.482.60.5.6.12.1
lccmtsHwRevBCM3137The hardware revision number for this Broadcom 3033 chip.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.12.1.1
lccmtsHwRevRipsawThe hardware revision number for this Ripsaw receiver.ro
INTEGER
.1.3.6.1.4.1.482.60.5.6.12.1.2
lccmtsPoliceTolerance
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.7
lccmtsUpPoliceThe tolerance percentage to apply to configured maximum Upstream bit rate. This allows for minor differences in shaping algoithms by not policing to the edge. The default valued is 0% which will police to the edge.rw
INTEGER
.1.3.6.1.4.1.482.60.5.7.1
lccmtsDnPoliceThe tolerance percentage to apply to configured maximum Downstream bit rate. This allows for minor differences in shaping algoithms by not policing to the edge. The default valued is 0% which will police to the edge.rw
INTEGER
.1.3.6.1.4.1.482.60.5.7.2
lccmtsBOOTPRelay
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.8
lccmtsBOOTPRelayControlControls the operation of the CMTS BOOTP Relay function as listed. If set to: disabled(1) The CMTS will process BOOTP/DHCP packets without special relay processing (this is the boot-time default), enabled-relay-only(2) BOOTP/DHCP packets will be intercepted using the relay function described in RFC-1542, and server targets will be selected based not only on non-zero IP addresses in the server target table, but also based on whether the client is a registered CM, or unregistered and assumed to be a CPE host; That is, requests from CMs and CPE hosts may be sent to different servers, if desired. enabled-relay-tagging(3) BOOTP/DHCP packets will be tagged with Agent info containing the MAC address of the modem through which this request originated, in Remote ID format. enabled-cm-only-relay(4) BOOTP/DHCP packets will be intercepted using the relay function described in RFC-1542, and server targets will be selected based on non-zero IP addresses in the server target table for CM hosts ONLY. Requests from CPE hosts will be handled without special relay processing.rw
Enumeration
.1.3.6.1.4.1.482.60.5.8.1
lccmtsBOOTPRelaySvrTargetTableThe table contains BOOTP Server target addresses, and discrimination parameters for selective targeting based upon registered CM addresses.
SEQUENCE OF LccmtsBOOTPRelaySvrTargetEntry
.1.3.6.1.4.1.482.60.5.8.2
lccmtsBOOTPRelaySvrTargetEntryEach entry contains one BOOTP Server target IP address, which can be unicast, multicast or broadcast, and, optionally, discrimination parameters for selective targeting based upon registered CM addresses.
LccmtsBOOTPRelaySvrTargetEntry
.1.3.6.1.4.1.482.60.5.8.2.1
lccmtsBOOTPRelayIndexThe index value which uniquely identifies an entry in the lccmtsBOOTPRelayTable.
INTEGER
.1.3.6.1.4.1.482.60.5.8.2.1.1
lccmtsBOOTPRelaySvrTargetIPThe IP (uni/multi/broad)cast address of targeted BOOTP server(s). If row is notInService(2), this entry is ignored.rw
IpAddress
.1.3.6.1.4.1.482.60.5.8.2.1.2
lccmtsBOOTPRelayClntSelectionMaskControls the selection of BOOTP Servers based upon client status. If set to: target-handles-CM-only(1) Client BOOTP/DHCP packets will be sent to this server address *ONLY* if client is a registered CM, target-handles-CPE-only(2) Client BOOTP/DHCP packets will be sent to this server address *ONLY* if client is NOT a registered CM, i.e presumed to be a CPE/host on the far side of a CM, target-handles-any(3) Any client (CM or CPE) BOOTP/DHCP request will be sent to this server address.rw
Enumeration
.1.3.6.1.4.1.482.60.5.8.2.1.3
lccmtsBOOTPRelaySvrTargetHitsCounts # times a client request was copied to this target, regardless of CM discrimintation.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.2.1.4
lccmtsBOOTPRelayRowStatusControls and reflects the status of rows in this table. Only notInService(2) and active(1) states are supported - default is notInService.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.482.60.5.8.2.1.5
lccmtsBOOTPRelayBadLengthDiscardsCounts # times an outgoing packet was silently dropped, due to having a miscalculated length value.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.3
lccmtsBOOTPRelayLocalOriginDiscardsCounts # times an outgoing packet was silently dropped, due to originating in the CMTS (should never happen!).ro
Counter32
.1.3.6.1.4.1.482.60.5.8.4
lccmtsBOOTPRelayExcessiveHopsDiscardsCounts # times an outgoing packet was silently dropped, due to an excessive hop count before increment.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.5
lccmtsBOOTPRelayGatewayAddrCopiesCounts # times an incoming packet had our (CMTS) address copied into the giaddr field.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.6
lccmtsBOOTPRelayLocalAddrSinksCounts # times an incoming packet was selected for local processing, due to having a CMTS CHADDR.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.7
lccmtsBOOTPRelayWrongGatewayAddrDiscardsCounts # times an incoming packet was silently dropped, due to server inserting the wrong gateway addr (i.e. not ours).ro
Counter32
.1.3.6.1.4.1.482.60.5.8.8
lccmtsBOOTPRelayNoCopyBufDiscardsCounts # times a packet was silently dropped, due to lack of a malloc'd copy buffer.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.9
lccmtsBOOTPRelayMiscSilentDiscardsCounts # times an outgoing packet was silently dropped, due to a variety of reasons not specifically tracked.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.10
lccmtsBOOTPRelayNoEpilBufDiscardsCounts # times an outgoing packet was dropped, due to a lack of Epilogue UDP/IP buffers.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.11
lccmtsBOOTPRelayClntDstPortDiscardsCounts # times an incoming packet was dropped, due to a destination port of BOOTP CLIENT.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.12
lccmtsBOOTPRelayRawRequestsCounts # times an incoming packet was processed as a raw request (subject to further filtering).ro
Counter32
.1.3.6.1.4.1.482.60.5.8.13
lccmtsBOOTPRelayRawRepliesCounts # times an incoming packet was processed as a raw reply (subject to further filtering).ro
Counter32
.1.3.6.1.4.1.482.60.5.8.14
lccmtsBOOTPRelayRqstFromCMCounts # times an incoming request came from a modem.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.15
lccmtsBOOTPRelayRqstFromCPECounts # times an incoming request came from Customer Premises Equipment.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.16
lccmtsBOOTPRelayDPCATVPutsCounts # times an outgoing packet was sent to the cable DP_put routine.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.17
lccmtsBOOTPRelayDPEnetPutsCounts # times an outgoing packet was sent to the ethernet DP_put routine.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.18
lccmtsBOOTPRelayEpilUDPBufSendsCounts # times an outgoing packet was sent to the Epilogue UDP_send routine.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.19
lccmtsBOOTPRelayNullMACTagsCounts # times an outgoing packet was tagged with a null CM macaddress.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.20
lccmtsBOOTPRelayNonNullMACTagsCounts # times an outgoing packet was tagged with a non-null CM macaddress.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.21
lccmtsBOOTPRelayWrongPortRqstDiscardsCounts # times an incoming request packet was discarded due to originating on a port other than cable.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.22
lccmtsBOOTPRelayWrongPortReplyDiscardsCounts # times an incoming reply packet was discarded due to originating on a port other than enet.ro
Counter32
.1.3.6.1.4.1.482.60.5.8.23
lccmtsDNSResolver
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.9
lccmtsDNSResolverControlControls the operation of the DNS Resolver function as listed. If set to: disabled(1) The CMTS will not resolve names into addresses using DNS, returning a blank record for all lookups, enabled(2) DNS reply packets will be processed and the results returned in the response record.rw
Enumeration
.1.3.6.1.4.1.482.60.5.9.1
lccmtsDNSResolverServiceTypeKind of DNS resolution service provided: recursiveOnly(1) indicates a stub resolver. iterativeOnly(2) indicates a normal full service resolver. recursiveAndIterative(3) indicates a full-service resolver which performs a mix of recursive and iterative queries.ro
Enumeration
.1.3.6.1.4.1.482.60.5.9.2
lccmtsDNSResolverServersCfgdThe numbers indicates the total number of enabled servers configured by the operator.ro
INTEGER
.1.3.6.1.4.1.482.60.5.9.3
lccmtsDNSResolverServerTableThis table contains DNS Server addresses, and hierarchical selection parameters for Name Server lookups.
SEQUENCE OF LccmtsDNSResolverServerEntry
.1.3.6.1.4.1.482.60.5.9.4
lccmtsDNSResolverServerEntryEach entry contains one DNS Server target IP address, its dot notation name, and its status (active or notInService).
LccmtsDNSResolverServerEntry
.1.3.6.1.4.1.482.60.5.9.4.1
lccmtsDNSResolverIndexThe index value which uniquely identifies an entry in the lccmtsDNSResolverTable.
INTEGER
.1.3.6.1.4.1.482.60.5.9.4.1.1
lccmtsDNSResolverServerIPThe IP address of a DNS server. If row status is notInService(2), this entry is ignored.rw
IpAddress
.1.3.6.1.4.1.482.60.5.9.4.1.2
lccmtsDNSResolverServerPriorityPrecedence (priority) ordering of this entry in the server lookup hierarchy. Highest legal number is highest priority, lowest number is lowest priority.rw
INTEGER
.1.3.6.1.4.1.482.60.5.9.4.1.3
lccmtsDNSResolverServerNameThe dot notation name of the DNS server.rw
DisplayString
.1.3.6.1.4.1.482.60.5.9.4.1.4
lccmtsDNSResolverRowStatusControls and reflects the status of rows in this table. Only notInService(2) and active(1) states are supported - default is notInService.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.482.60.5.9.4.1.5
lccmtsDevServer
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.5.10
lccmtsDevServerBootStateIf operational(1), the device has completed loading and processing of configuration parameters and the CMTS has completed the Registration exchange. If disabled(2) then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3) then a DHCP Discover has been transmitted and no offer has yet been received. If waitingForDhcpResponse(4) then a DHCP Request has been transmitted and no response has yet been received. If waitingForTimeServer(5) then a Time Request has been transmitted and no response has yet been received. If waitingForTftp(6) then a request to the TFTP parameter server has been made and no response received. If refusedByCmts(7) then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8) then the registration process completed, but the network access option in the received configuration file prohibits forwarding.ro
Enumeration
.1.3.6.1.4.1.482.60.5.10.1
lccmtsDevServerDhcpThe IP address of the DHCP server that assigned an IP address to this device. Returns 0.0.0.0 if DHCP was not used for IP address assignment.ro
IpAddress
.1.3.6.1.4.1.482.60.5.10.2
lccmtsDevServerTimeThe IP address of the Time server (RFC-868).ro
IpAddress
.1.3.6.1.4.1.482.60.5.10.3
lccmtsDevServerTftpThe IP address of the TFTP server responsible for downloading provisioning and configuration parameters to this device.ro
IpAddress
.1.3.6.1.4.1.482.60.5.10.4
lccmtsDevServerConfigFileThe name of the device configuration file read from the TFTP server.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.482.60.5.10.5
lccmdevice
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.6
lcScanningFrequencyTableDefines the frequencies and scanning order used by the modem to find the downstream channel.
SEQUENCE OF LcScanningFrequencyEntry
.1.3.6.1.4.1.482.60.6.1
lcScanningFrequencyEntryDefines a range of channels to be used by the modem to find the downstream channel.
LcScanningFrequencyEntry
.1.3.6.1.4.1.482.60.6.1.1
lcScanControlControls the creation and deletion of rows in this table. See RFC-1903 for definition of enumeration.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.482.60.6.1.1.1
lcScanIndexAn ad-hoc index for defining the scanning order for this table.rw
INTEGER
.1.3.6.1.4.1.482.60.6.1.1.2
lcScanFreqStartThe center frequency of the first channel to scan in this range.rw
Integer32 UNITS "kilohertz"
.1.3.6.1.4.1.482.60.6.1.1.3
lcScanFreqEndThe center frequency of the last channel to scan in this range. This may be higher or lower than lcScanFreqStart.rw
Integer32 UNITS "kilohertz"
.1.3.6.1.4.1.482.60.6.1.1.4
lcScanUseHrcIf TRUE then the range is to use the HRC channels which correspond to the Std/IRC channels whose center frequencies are defined by FreqStart and FreqEnd (i.e. offset the values in FreqStart and FreqEnd before using them).rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.6.1.1.5
lcScanStepThe absolute value of the increment (or decrement) to use in stepping through this range.rw
Integer32 UNITS "kilohertz"
.1.3.6.1.4.1.482.60.6.1.1.6
lcScanChannelWidthThe channel width to use for this range. Only 6000 and 8000 are allowed.rw
Integer32 UNITS "kilohertz"
.1.3.6.1.4.1.482.60.6.1.1.7
lccmAddress
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.6.2
lccmIpAddressThe IP address of the CM; provides a writable equivalent of ipAdEntAddr. If set to null (0.0.0.0), the address must be provided through DHCP.rw
IpAddress
.1.3.6.1.4.1.482.60.6.2.1
lccmIpSubnetThe subnet mask corresponding to lcCMIpAddress; provides a writable equivalent of ipAdEntNetMask.rw
IpAddress
.1.3.6.1.4.1.482.60.6.2.2
lcdevicecommon
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.7
lcTrapTypeTableThe trap type control table contains an entry for each type of trap supported by the system.
SEQUENCE OF LcTrapTypeEntry
.1.3.6.1.4.1.482.60.7.1
lcTrapTypeEntryAn entry in this table defines a particular trap type supported by the system.
LcTrapTypeEntry
.1.3.6.1.4.1.482.60.7.1.1
lcTrapTypeIndexThe variable is the index of this entry in the lcTrapTypeTable.ro
Enumeration
.1.3.6.1.4.1.482.60.7.1.1.1
lcTrapTypeStatusThis variable controls whether this type of trap is generated by this device.rw
Enumeration
.1.3.6.1.4.1.482.60.7.1.1.2
lcBootedAlbumFilenameThe filename that is embedded in the flash album header of the currently booted album software imagero
DisplayString
.1.3.6.1.4.1.482.60.7.2
lcBootedAlbumSequenceNumberThe sequence number of the currently loaded software image.ro
Counter32
.1.3.6.1.4.1.482.60.7.3
lctrapvars
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.7.4
lcAuthFailErrorStatusThe reason for failure to validate the SNMP request. nmAccessTableRestriction(1) indicates that the requesting network management station (NMS) does not have appropriate permission to perform the SNMP request, because it either does not match an ip address in the docsDevNmAccessTable, or the community string in the SNMP request did not match the community string in docsDevNmAccessTable for the requesting NMS, or the docsDevNmAccessControl value specified in the docsDevNmAccessTable for this NMS was not sufficient to allow access for the SNMP request type (either 'get' or 'set'), or finally the SNMP request from this NMS is not accepted on the interface (ethernet or CATV) that the request was received. noWriteAccessToMibVar(2) indicates that an SNMP set request was received for a mib variable whose write access control is set. other(3) indicates an nonspecific error.
Enumeration
.1.3.6.1.4.1.482.60.7.4.1
lcAuthFailCommunityStringThis the community string received in a Get/Set SNMP request that did not pass authentication tests. This object is returned in the authenticationFailure trap.
DisplayString
.1.3.6.1.4.1.482.60.7.4.2
lcAuthFailIpAddrThis is the source address of a Get/Set SNMP request that did not pass authentication tests. This object is returned in the authenticationFailure trap.
IpAddress
.1.3.6.1.4.1.482.60.7.4.3
lcAuthFailInterfaceThis is the interface port on which was received a Get/Set SNMP request that did not pass authentication tests. This object is returned in the authenticationFailure trap.
Enumeration
.1.3.6.1.4.1.482.60.7.4.4
lcIpFiltSendDuThis variable specifies whether a 'destination unreachable' ICMP message is sent when a packet is filtered due to IP protocol filtering.rw
Enumeration
.1.3.6.1.4.1.482.60.7.5
lcMulticastGroup
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.7.6
lcMcastControlAction to take on receiving an IP multicast packet bound for the subscriber network. If pass(1), the CM acts as a bridge, transparently forwarding all multicast packets. If filter(2), all IP multicast packets are discarded. If igmp(3) then the CM acts as an IGMP proxy and only forwards packets whose addresses were requested by the subscriber. If trap(4) then the CM transmits IGMP queries on the subscriber side. On receiving Reports, it transmits an SNMP trap. Multicast packets are forwarded, and presumably blocked by SNMP- managed filters.rw
Enumeration
.1.3.6.1.4.1.482.60.7.6.1
lcMcastAddressTableDescribes the current state of multicast address filtering being performed by the IGMP proxy.
SEQUENCE OF LcMcastAddressEntry
.1.3.6.1.4.1.482.60.7.6.2
lcMcastAddressEntryDescribes the current state of a multicast address controlled by the IGMP proxy.
LcMcastAddressEntry
.1.3.6.1.4.1.482.60.7.6.2.1
lcMcastAddressThe IP multicast address being managed.
IpAddress
.1.3.6.1.4.1.482.60.7.6.2.1.1
lcMcastAdminStateControls addition of static entries or deletion of any entries in this table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.6.2.1.2
lcMcastOperStateReflects the IGMP state of this address. If static(4), the entry was created as a result of management action, and the entry is not subject to the IGMP protocol.ro
Enumeration
.1.3.6.1.4.1.482.60.7.6.2.1.3
lcMcastTtlTime-to-live for this entry. Will return zero for static entries.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.482.60.7.6.2.1.4
lcMcastTrapAddressThe IP multicast address that is included in the lcMcastJoin trap. This object only exists for purposes of inclusion in the trap message.
IpAddress
.1.3.6.1.4.1.482.60.7.6.3
lcRestartFromFactoryDefaultsSetting this object to true(1) causes the device to reset. When restarting, it will have forgotten all configuration parameters that are normally stored in nonvolatile memory. The device will start up as if delivered from the factory. Reading this object always returns false(2).rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.7
lcPhyTableDetermines how the ETHERNET PHYs are configured and operating
SEQUENCE OF LcPhyEntry
.1.3.6.1.4.1.482.60.7.8
lcPhyEntryDetermines how an ETHERNET PHYs is configured and operating
LcPhyEntry
.1.3.6.1.4.1.482.60.7.8.1
lcPhyIndexName/Index for each ETHERNET PHYro
Enumeration
.1.3.6.1.4.1.482.60.7.8.1.1
lcPhyEnableIf true, this PHY may be used. If false, this will not be used.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.8.1.2
lcPhyAutoNegotiateIf true, this PHY autonegotiates if active. If false, this PHY is manually configured if active.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.8.1.3
lcPhyActiveIf true, this PHY is the one being used. If false, this PHY is not being used.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.8.1.4
lcPhySpeedDetermines the speed for this PHY. If lcPhyAutoNegotiate is true, writes to this value are prohibited. If lcPhyAutoNegotiate is false, this PHY will be force to this speed. Valid values are 10000000 and 100000000rw
Integer32
.1.3.6.1.4.1.482.60.7.8.1.5
lcPhyFullDuplexDetermines the duplex mode for this PHY. If lcPhyAutoNegotiate is true, writes to this value are prohibited. If lcPhyAutoNegotiate is false, this PHY will be force to this duplex moderw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.8.1.6
lcStickyYellowTableThis table provides a maintenance-history area where notes about the device may be stored. The contents of this table are entirely for human benefit and have no effect on the operation of the device. Up to 8 entries of up to 80 characters each may be stored.
SEQUENCE OF LcStickyYellowEntry
.1.3.6.1.4.1.482.60.7.9
lcStickyYellowEntryEach entry provides a line of text of maintenance history.
LcStickyYellowEntry
.1.3.6.1.4.1.482.60.7.9.1
lcStickyYellowIndexProvides an index by which to distinguish up to 8 lines of text.
INTEGER
.1.3.6.1.4.1.482.60.7.9.1.1
lcStickyYellowPadContents of this object are for the benefit of a human operator and may be used for any information, such as maintenance history, that the operator wishes to associate with the device. Contents of this object have no effect on the operation of the device. Setting this object to any non-null value either creates the row or overwrites previous text. Setting to the the null string deletes the row. Set's longer than 80 characters are truncated.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.9.1.2
lcResetFiltersSetting this object to true(1) causes the device to reset the following Docsis MIB objects as follows, so that filters are no longer applied to traffic: docsDevFilterLLCDefault is set to accept(2). docsDevFilterIpDefault is set to accept(2). All entries in the docsDevFilterLLCTable are destroyed. All entries in the docsDevFilterIpTable are destroyed. Note that the device is not reset; filters are destroyed on the fly. Reading this object always returns false(2). This object can be used to clear out previously set filters without having to know all the instances of existing entries.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.10
lcResetNmAccessTableSetting this object to true(1) causes the device to destroy all docsDevNmAccessTable entries, such that the table is empty. The DOCSIS Cable Device MIB specifies that it the table is empty, access to SNMP objects is unrestricted. Note that the device is not reset; entries are destroyed on the fly. Reading this object always returns false(2). This object can be used to clear out previously set entries in the docsDevNmAccessTable without having to know all the instances of existing entries.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.11
lcFlashPersistenceSwitchSpecifies the flash persistence behavior of the associated MIB objects. lcFlashPersistenceSwitch MIB object is itself saved to flash. At modem startup, the value of lcFlashPersistenceSwitch is read from flash and used to determine how to initialize the associated MIB objects. At runtime, lcFlashPersistenceSwitch is used to determine whether or not modifications made to the enumerated MIB objects are saved to flash. The factory default is no bits set; thus, none of the enumerated MIB objects are initialized from flash, and subsequent modifications to the enumerated MIB objects are not saved to flash. If a bit value is set at startup, the associated MIB object will be initialized from flash memory, and subsequent modifications will be saved to flash. If a bit is set at runtime, the associated MIB object is immediately written to flash, and subsequent modifications will be saved to flash. If a bit value is not set at startup, factory default values will be used to initialize the associated MIB object, and subsequent modifications will not be saved to flash memory. If a bit is cleared during runtime, subsequent modifications to the associated MIB object will not be saved to flash. The nmAccess(0) bit effects the docsDevNmAccessTable. The llcIpFilters(1) bit effects docsDevFilterLLCDefault, docsDevFilterLLCTable, docsDevFilterIpDefault, and docsDevFilterIpTable.rw
Bits
.1.3.6.1.4.1.482.60.7.12
lcConcatenationEnabledFor modem, this determines if concatenation should be turned on or not, when it is supported by the headend. For headend, this determines if concatenation support is desirable and possible (only possible on 3210B or later chips).rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.13
lcConsoleAccess
OBJECT IDENTIFIER
.1.3.6.1.4.1.482.60.7.14
lcConsoleUserTableDefines user names, passwords, and access privileges for console and telnet access to the device. This table is primarily a repository for user names and passwords, as the accesss rights are actually defined in other tables. This table points to the lcConsoleLevelTable, which in turn may point to docsDevNmAccessTable. Access to this table itself is restricted in the same manner as docsDevNmAccessTable; that is, the operator must have write privileges to be able to read this table (with exception of being able to read their own entry).
SEQUENCE OF LcConsoleUserEntry
.1.3.6.1.4.1.482.60.7.14.1
lcConsoleUserEntryDescribes the attributes of a single user login.
LcConsoleUserEntry
.1.3.6.1.4.1.482.60.7.14.1.1
lcConsoleUserIndexProvides an index to this table. Provides no semantics.
INTEGER
.1.3.6.1.4.1.482.60.7.14.1.1.1
lcConsoleUserStatusControls additions and deletions from this table. May only be set to createAndGo or destroy.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.14.1.1.2
lcConsoleUserNameUser login name, as used for the console or telnet. Deletion of the currently logged in account results in being logged out.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.14.1.1.3
lcConsoleUserPasswordThe user's password, as used for the console or telnet. This is an MD5 hashed string, and returns a 32 character ASCII representation of the hex 16 byte value when a get is attempted. For set operations, the value for the set must be the 32 byte ASCII representation of the 16 byte hex MD5 hash value. See RFC 1321 for MD5 hash operations. The default value is the MD5 hash of the null string.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.14.1.1.4
lcConsoleUserLevelThe index of a row in lcConsoleLevelTable which defines the access privileges for this user. If the referenced row does not exist then access is not allowed.rw
INTEGER
.1.3.6.1.4.1.482.60.7.14.1.1.5
lcConsoleLevelTableDefines access privilege levels for the console and for telnet. Entries in this table are referenced by the lcConsoleUserTable. This table, in turn, will reference docsDevNmAccessTable.
SEQUENCE OF LcConsoleLevelEntry
.1.3.6.1.4.1.482.60.7.14.2
lcConsoleLevelEntryDefines a specific console privilege level in terms of access method and access name.
LcConsoleLevelEntry
.1.3.6.1.4.1.482.60.7.14.2.1
lcConsoleLevelIndexProvides an index to this table, referenced by lcConsoleUserLevel. Provides no ordering or other semantics.
INTEGER
.1.3.6.1.4.1.482.60.7.14.2.1.1
lcConsoleLevelStatusControls additions and deletions from this table. May only be set to createAndGo or destroy.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.14.2.1.2
lcConsoleLevelNameA label which can be attached to this access Level as a mnemonic aid. Not used operationally.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.14.2.1.3
lcConsoleLevelMethodDefines which SNMP access method is used to validate requests from this level. If snmpv1(1), then read-only, read-write, and sundry other privileges are derived from docsDevNmAccessTable and lcNmAccessExtensionTable.rw
Enumeration
.1.3.6.1.4.1.482.60.7.14.2.1.4
lcConsoleLevelSecurityNameIf snmpv1 access is used, this value supplies the community string.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.482.60.7.14.2.1.5
lcTelnetAllowedSessionsIndicates the number of remote telnet access sessions allowed. A value of 0 indicates remote telnet access is denied. A maximum of 5 is allowed.rw
INTEGER
.1.3.6.1.4.1.482.60.7.14.3
lcSessionInactivityTimeoutThe session inactivity timeout value in minutes. A value of 0 indicates no session timeout. The maximum timeout is one week. Applies to all sessions (both Command line and Telnet sessions), but each session maintains a separate inactivity timer. This timer starts after a successful login, and is restarted every time a command is entered. If this timer expires, the associated session is terminated. Termination of the console results in a user logout. Termination of a telnet session results in a user logout and a telnet disconnect process.rw
INTEGER
.1.3.6.1.4.1.482.60.7.14.4
lcNmAccessExtensionTableFurther qualifies the privileges accorded to each row of the docsDevNmAccessTable. This table provides a set of specific privileges for users who are either using SNMPv1 directly or who are using SNMPv1-based access through the console.
SEQUENCE OF LcNmAccessExtensionEntry
.1.3.6.1.4.1.482.60.7.15
lcNmAccessExtensionEntryQualifies the privileges accorded to a row of docsDevNmAccessTable.
LcNmAccessExtensionEntry
.1.3.6.1.4.1.482.60.7.15.1
lcNmAccessAdditionalPrivilegesDefines additional privileges allowed a user. The resetAllowed bit (value 0x80) allows an operator with a read-only account the privilege of resetting the CMTS from either a telnet or console session using the CLI reset command, in addition to all other privileges allowed by the docsDevNmAccessTable for a read/only account. The resetAllowed bit does not allow the user to use the 'factory' option of the reset command. The resetAllowed bit does not allow the user remote SNMP write access to either the docsDevResetNow or the lcRestartFromFactoryDefault MIBs. A read/write entry gets reset ability automatically, so setting resetAllowed for read/write entries is not necessary. The accountManager bit (value 0x40) allows a read/write account to perform the additional account management function of creation, modification, and deletion of accounts, in addition to any other privileges accorded by docsDevNmAccessTable. Read/only accounts do not access the accountManager bit.rw
Bits
.1.3.6.1.4.1.482.60.7.15.1.1
lcIpFiltIcmp9This variable specifies whether ICMP Type 9 packets are forwarded or filtered on all interfaces.rw
Enumeration
.1.3.6.1.4.1.482.60.7.16
LANCITY-MCNS-MIB - SNMP MIB Reference | MIBs Explorer