LANCITY-MCNS-MIB: View SNMP OID List / Download MIB

This is the portion of the Lancity enterprise MIB that applies to MCNS cable modems and related devices.

Defines properties of upstream channels, from the CMTS.

Defines properties of an upstream channel, from the CMTS.

Minimum number of slots to be mapped in each Map PDU.

Maximum number of slots to be mapped in each Map PDU.

The number of mini-slots allotted to contention (REQ or REQ-DATA) per MAP PDU.

Specifies whether or not the CMTS will allow contention data on this upstream interface. Enumeration: 'adaptive': 3, 'disallowed': 2, 'allowed': 1.

The number of mini-slots that may be used for a single upstream contention transmission.

The 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.

Weighting of high priority queue is-a-vis normal priority queue.

Permitted aggregate CIR, as a percentage of the overall channel bandwidth.

A sum of architectural constants, parameters, and network status (RTD) that governs the difference between the publication time of the MAP and its effectiveness.

The number of Map PDUs that were generated under flow-controlled (prioritized) conditions.

The number of Map PDUs that were generated under FIFO conditions.

The 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.

The 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.

Current temperature of a CMTS device in degrees Celsius.

High 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).

Defines which upstreams are enabling this feature and which metrics to use.

Defines which upstreams are enabling this feature and which metrics to use.

Enable Ingress Avoidance for the Upstream. Enumeration: 'on': 1, 'off': 0.

Enable the metric associated with Ingress Avoidance. Enumeration: 'on': 1, 'off': 0.

Defines the provisioned frequencies per carrier path.

Defines which upstreams are enabling this feature and which metrics to use.

Carrier path index for the frequency ranges.

Index for frequency ranges for each carrier path.

Allow frequency range to be used for the carrier path. Enumeration: 'yes': 1, 'no': 0.

Beginning 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.

End 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.

Defines carrier paths (Physical Connectivity) and channel groups for each upstream.

Defines carrier paths (Physical Connectivity) and channel groups for each upstream.

Defines which type of change is the prefered change if ingress avoidance detects a problem in the current configuration. Enumeration: 'profile': 1, 'frequency': 2.

Defines threshold for each of the ingress avoidance available metrics.

Defines threshold for each of the ingress avoidance available metrics.

Defines the green to yellow threshold for a particular metric.

Defines 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.

Defines with profile in the Tranmission table will be used for ingress avoidance. The order from 1-3 is the desired order for profile use.

Defines with profile in the Tranmission table will be used for ingress avoidance. The order from 1-3 is the desired order for profile use.

Carrier path index for the profile table.

Profile index per carrier path.

Defines whether or not the particular profile is enabled for use in ingress avoidance. Enumeration: 'on': 1, 'off': 0.

Describes the index into the transmission profile table.

Defines Modulation Profile and Bandwidth. Coding Efficiency is calculated based on the entries.

Defines with profile in the Tranmission table will be used for ingress avoidance. The order from 1-3 is the desired order for profile use.

Index for the transmission profile table.

Index into the MCNS Upstream Modulation Table.

Bandwidth to be used with the modulation profile selected.

Coding 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.

Defines the aging multipliers and calculation timers for each metric.

Defines the aging multipliers and calculation timers for each metric.

Metric Index.

Metric aging multilpler in hundreths.

Frequency at which metrics should be calculated in milliseconds.

This table is a status table for all frequency ranges allowed per carrier path.

This table is a status table for all frequency ranges allowed per carrier path.

Carrier Paths for each frequency.

Frequency index for carrier path.

Frequency in Hz.

Denotes whether or not this is a center frequency. Enumeration: 'yes': 1, 'no': 0.

Denotes 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. Enumeration: 'yes': 1, 'inuse': 2, 'reserved': 3, 'no': 0.

Denotes status of frequency. Large integers represents the channel is extremely bad. Zero/UNK represents a Good frequency to try. Enumeration: 'unk': 0.

Denotes time since this frequency was last used.

Denotes up time last time used or current up time on this frequency.

Displays the health of each upstream channel.

Displays the health of each upstream channel.

Upstream Ingress Avoidance Profile Index.

Center frequency for the upstream channel.

Time the channel has been up in this configuration.

Current state of the upstream channel using the thresholds set in the threshold table. Enumeration: 'green': 2, 'yellow': 1, 'red': 0.

Current value for the metric.

Defines carrier paths (Physical Connectivity) and channel groups for each upstream.

Defines carrier paths (Physical Connectivity) and channel groups for each upstream.

Defines physical connectivity to each upstream receiver ifIndexes with the same carrier path cannot operate on the same frequencies.

Defines 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.

Current 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.

Current 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.

Current 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.

FEC mode - Default is Annex B which is the North American Standard Annex A is used for Euro DOCSIS. Enumeration: 'annexA': 0, 'annexB': 1.

Upstream/Downstream Frequency Split. The standard North American split is 5-42/50-862 MHz. Euro DOCSIS Split is 5-65/100-862 MHz. Enumeration: 'euroDOCSIS': 1, 'standard': 0.

The IP address of a 2nd Syslog server. If 0.0.0.0, syslog transmission is inhibited.

The IP address of a 3rd Syslog server. If 0.0.0.0, syslog transmission is inhibited.

This 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.

A 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.

A MAC address in the CMTS Forwarding Database. This is the index into the lcCpeMacToCmMacTable.

The 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.

This 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.

A row in the lcCmCountsTable. An entry in this table exists for each upstream channel on the CMTS (1-8) and for the system totals.

A row index into the lcCmCountsTable. Indices 1 through 8 correspond to upstream channels and index 9 corresponds to the system totals.

The number of CMs on this channel that have performed an initial ranging and are still marked as operational by the CMTS.

The number of CMs on this channel that are currently registered with the CMTS.

Controls 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. Enumeration: 'use-tftp': 3, 'use-nvram': 4, 'use-dhcp-and-tftp': 1, 'use-dhcp': 2.

The 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.

The subnet mask corresponding to lcConfigIpAddress; provides a writable equivalent of ipAdEntNetMask.

The Gateway address defines the next hop router (forwarder) destination for non-local IP packets.

The IP address of the TFTP Server supplying provisioning configuration data.

The default filename on the TFTP Server for acquiring provisioning configuration data (may be overridden by DHCP).

The IP address of the Time Server (RFC868) supplying provisioning time.

Time offset in seconds to apply to provisioned GMT time

The IP Address of the SNTP Timer Server supplying provisioning time

Configuration of system serial port(s)

Information for each serial port.

Index for this table.

Baud rate configured on this Serial Port Enumeration: 'baudrate64k': 64000, 'baudrate56k': 57600, 'baudrate76k': 76800, 'baudrate28800b': 28800, 'baudrate14400b': 14400, 'baudrate1200b': 1200, 'baudrate4800b': 4800, 'baudrate12000b': 12000, 'baudrate19200b': 19200, 'baudrate96k': 96000, 'baudrate115k': 115200, 'baudrate7200b': 7200, 'baudrate38k': 38400, 'baudrate9600b': 9600, 'baudrate2400b': 2400.

Number of data bits configured on this Serial Port

Type of parity configured on this Serial Port Enumeration: 'even': 3, 'none': 1, 'odd': 2.

Number of stop bits configured on this Serial Port Enumeration: 's15bit': 2, 's2bit': 3, 's1bit': 1.

Enable the Serial Port to run with modem leads enabled Enumeration: 'disabled': 2, 'enabled': 1.

This 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.

This entry identifies a class of modems which are allowed to register with this CMTS.

An arbitrary index defining an instance of this entry. Ordering is not meaningful.

This object controls the creation and deletion of rows in this table.

When 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.

Applied 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.

Controls the interval at which data rates are calculated on the CMTS.

The table contains the last calculated statistics for data rates for each port on the CMTS.

The Entry contains the last calculated statistics for data rates for one port on the CMTS.

The last calculated frames per second transmitted on this port.

The last calculated frames per second received on this port.

The last calculated octets per second transmitted on this port.

The last calculated octets per second received on this port.

Controls 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). Enumeration: 'none': 1, 'dhcp-arp': 2.

Controls 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). Enumeration: 'enable': 1, 'disable': 2.

Controls the timeout (in seconds) of the Proxy Arp cache entries.

Controls 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. Enumeration: 'enable': 1, 'disable': 2.

Controls 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). Enumeration: 'enable': 1, 'disable': 2.

The 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).

The 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.

This 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). Enumeration: 'enable': 1, 'disable': 2.

The hardware revision number for the Arb CPLD chip.

The hardware revision number for the Tx CPLD chip.

The hardware revision number for the AFFPGA chip.

The hardware revision number for the Galileo GT-64010 chip.

The hardware revision number for the PLX PCI 9080 chip.

The hardware revision number for the Broadcom 3210 chip.

The hardware revision number for the Broadcom 3033 chip.

The hardware revision number for the Sunset transmitter.

The hardware revision number for the DEC 21143 Ethernet chip.

The hardware revision number for the LXT970 Ethernet PHY A chip.

The hardware revision number for the LXT970 Ethernet PHY B chip.

The table contains hardware revision numbers for the chips of each upstream RF receiver channel in the CMTS.

The table contains hardware revision numbers for the chips of one upstream RF receiver channel in the CMTS.

The hardware revision number for this Broadcom 3033 chip.

The hardware revision number for this Ripsaw receiver.

The 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.

The 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.

Controls 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. Enumeration: 'disabled': 1, 'enabled-relay-tagging': 3, 'enabled-cm-only-relay': 4, 'enabled-relay-only': 2.

The table contains BOOTP Server target addresses, and discrimination parameters for selective targeting based upon registered CM addresses.

Each 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.

The index value which uniquely identifies an entry in the lccmtsBOOTPRelayTable.

The IP (uni/multi/broad)cast address of targeted BOOTP server(s). If row is notInService(2), this entry is ignored.

Controls 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. Enumeration: 'target-handles-CPE-only': 2, 'target-handles-CM-only': 1, 'target-handles-any': 3.

Counts # times a client request was copied to this target, regardless of CM discrimintation.

Controls and reflects the status of rows in this table. Only notInService(2) and active(1) states are supported - default is notInService.

Counts # times an outgoing packet was silently dropped, due to having a miscalculated length value.

Counts # times an outgoing packet was silently dropped, due to originating in the CMTS (should never happen!).

Counts # times an outgoing packet was silently dropped, due to an excessive hop count before increment.

Counts # times an incoming packet had our (CMTS) address copied into the giaddr field.

Counts # times an incoming packet was selected for local processing, due to having a CMTS CHADDR.

Counts # times an incoming packet was silently dropped, due to server inserting the wrong gateway addr (i.e. not ours).

Counts # times a packet was silently dropped, due to lack of a malloc'd copy buffer.

Counts # times an outgoing packet was silently dropped, due to a variety of reasons not specifically tracked.

Counts # times an outgoing packet was dropped, due to a lack of Epilogue UDP/IP buffers.

Counts # times an incoming packet was dropped, due to a destination port of BOOTP CLIENT.

Counts # times an incoming packet was processed as a raw request (subject to further filtering).

Counts # times an incoming packet was processed as a raw reply (subject to further filtering).

Counts # times an incoming request came from a modem.

Counts # times an incoming request came from Customer Premises Equipment.

Counts # times an outgoing packet was sent to the cable DP_put routine.

Counts # times an outgoing packet was sent to the ethernet DP_put routine.

Counts # times an outgoing packet was sent to the Epilogue UDP_send routine.

Counts # times an outgoing packet was tagged with a null CM macaddress.

Counts # times an outgoing packet was tagged with a non-null CM macaddress.

Counts # times an incoming request packet was discarded due to originating on a port other than cable.

Counts # times an incoming reply packet was discarded due to originating on a port other than enet.

Controls 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. Enumeration: 'disabled': 1, 'enabled': 2.

Kind 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. Enumeration: 'recursiveAndIterative': 3, 'iterativeOnly': 2, 'recursiveOnly': 1.

The numbers indicates the total number of enabled servers configured by the operator.

This table contains DNS Server addresses, and hierarchical selection parameters for Name Server lookups.

Each entry contains one DNS Server target IP address, its dot notation name, and its status (active or notInService).

The index value which uniquely identifies an entry in the lccmtsDNSResolverTable.

The IP address of a DNS server. If row status is notInService(2), this entry is ignored.

Precedence (priority) ordering of this entry in the server lookup hierarchy. Highest legal number is highest priority, lowest number is lowest priority.

The dot notation name of the DNS server.

Controls and reflects the status of rows in this table. Only notInService(2) and active(1) states are supported - default is notInService.

If 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. Enumeration: 'forwardingDenied': 8, 'waitingForDhcpOffer': 3, 'refusedByCmts': 7, 'unknown': 10, 'waitingForTimeServer': 5, 'waitingForTftp': 6, 'operational': 1, 'disabled': 2, 'other': 9, 'waitingForDhcpResponse': 4.

The 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.

The IP address of the Time server (RFC-868).

The IP address of the TFTP server responsible for downloading provisioning and configuration parameters to this device.

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

Defines the frequencies and scanning order used by the modem to find the downstream channel.

Defines a range of channels to be used by the modem to find the downstream channel.

Controls the creation and deletion of rows in this table. See RFC-1903 for definition of enumeration.

An ad-hoc index for defining the scanning order for this table.

The center frequency of the first channel to scan in this range.

The center frequency of the last channel to scan in this range. This may be higher or lower than lcScanFreqStart.

If 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).

The absolute value of the increment (or decrement) to use in stepping through this range.

The channel width to use for this range. Only 6000 and 8000 are allowed.

The 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.

The subnet mask corresponding to lcCMIpAddress; provides a writable equivalent of ipAdEntNetMask.

The trap type control table contains an entry for each type of trap supported by the system.

An entry in this table defines a particular trap type supported by the system.

The variable is the index of this entry in the lcTrapTypeTable. Enumeration: 'warmstartTrap': 2, 'coldstartTrap': 1, 'lcMcastJoinTrap': 9, 'newRootTrap': 7, 'linkDownTrap': 4, 'linkUpTrap': 3, 'authenticationFailureTrap': 5, 'topologyChangeTrap': 6.

This variable controls whether this type of trap is generated by this device. Enumeration: 'noTrap': 2, 'sendTrap': 1.

The filename that is embedded in the flash album header of the currently booted album software image

The sequence number of the currently loaded software image.

The 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: 'other': 3, 'noWriteAccessToMibVar': 2, 'nmAccessTableRestriction': 1.

This the community string received in a Get/Set SNMP request that did not pass authentication tests. This object is returned in the authenticationFailure trap.

This is the source address of a Get/Set SNMP request that did not pass authentication tests. This object is returned in the authenticationFailure trap.

This 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: 'ethernet': 1, 'other': 3, 'catv': 2.

This variable specifies whether a 'destination unreachable' ICMP message is sent when a packet is filtered due to IP protocol filtering. Enumeration: 'on': 1, 'off': 2.

Action 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. Enumeration: 'discard': 2, 'igmp': 3, 'trap': 4, 'pass': 1.

Describes the current state of multicast address filtering being performed by the IGMP proxy.

Describes the current state of a multicast address controlled by the IGMP proxy.

The IP multicast address being managed.

Controls addition of static entries or deletion of any entries in this table.

Reflects 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. Enumeration: 'nonmember': 1, 'delaying': 2, 'static': 4, 'idle': 3.

Time-to-live for this entry. Will return zero for static entries.

The IP multicast address that is included in the lcMcastJoin trap. This object only exists for purposes of inclusion in the trap message.

Setting 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).

Determines how the ETHERNET PHYs are configured and operating

Determines how an ETHERNET PHYs is configured and operating

Name/Index for each ETHERNET PHY Enumeration: 'aux1': 2, 'primary': 1.

If true, this PHY may be used. If false, this will not be used.

If true, this PHY autonegotiates if active. If false, this PHY is manually configured if active.

If true, this PHY is the one being used. If false, this PHY is not being used.

Determines 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 100000000

Determines 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 mode

This 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.

Each entry provides a line of text of maintenance history.

Provides an index by which to distinguish up to 8 lines of text.

Contents 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.

Setting 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.

Setting 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.

Specifies 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. Bits: 'nmAccess': 0, 'llcIpFilters': 1.

For 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).

Defines 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).

Describes the attributes of a single user login.

Provides an index to this table. Provides no semantics.

Controls additions and deletions from this table. May only be set to createAndGo or destroy.

User login name, as used for the console or telnet. Deletion of the currently logged in account results in being logged out.

The 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.

The 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.

Defines 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.

Defines a specific console privilege level in terms of access method and access name.

Provides an index to this table, referenced by lcConsoleUserLevel. Provides no ordering or other semantics.

Controls additions and deletions from this table. May only be set to createAndGo or destroy.

A label which can be attached to this access Level as a mnemonic aid. Not used operationally.

Defines 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. Enumeration: 'snmpv1': 1.

If snmpv1 access is used, this value supplies the community string.

Indicates the number of remote telnet access sessions allowed. A value of 0 indicates remote telnet access is denied. A maximum of 5 is allowed.

The 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.

Further 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.

Qualifies the privileges accorded to a row of docsDevNmAccessTable.

Defines 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. Bits: 'accountManager': 1, 'resetAllowed': 0.

This variable specifies whether ICMP Type 9 packets are forwarded or filtered on all interfaces. Enumeration: 'on': 1, 'off': 2.

System tasking failure

NU_Send_Item failed but task will try to send again

Unknown error SNMP Trap

System error, some sort of exception. Displayed are the EPC, Cause, BadVaddr and Status registers.

Testing error handling

Assertion failed

Shutdown initiated

Event log was cleared.

Event reporting set to default values.

System error, some sort of exception, further details for the 4700 processor, specifically the ErrorEPC and CacheError registers.

The 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.

Info about a system error: calling stack display, helpful for problem analysis.

Info 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.

Info about a system error: called routine arguments display, helpful for problem analysis.

Nuke history trace.

helpful for problem analysis.

helpful for problem analysis.

Unable to allocate memory for initial ranging

Re-starting registration for modem

Unable to allocate initial service ID for modem

Ranging retries exceeded for modem

Invalid ranging request received from modem

Ranging timed out for modem

Invalid registration request received from modem

Registration request from modem did not have Modem IP Address TLV (12).

Registration 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.

Unable to unpack the TLV data in the registration request received from modem

Modem is already registered as another SID

Registration request data in error, failed validation test.

Registration request failed because no SID was available.

Control Task fatal error is reported

Control Task fatal error is reported

Upstream Change Channel not currently supported.

Invalid ITM type received.

Synchronization Lost.

Synchronization acquired on frequency.

UCD Complete.

UCC received for channel.

Rescan cause.

Lost Pulse.

Lost Synch.

FEC Lost Lock.

Phy2 IRQ.

Ranging aborted by CMTS

TX adjusted by CMTS

Ranging Complete

Unexpected spanning tree packet format received

Internal inconsistency in Upstream Scheduler due to CMTS malfunction. Contact Customer Support.

Downstream transmitter hang reported by scheduler. CMTS is reset to clear transmittter problem. If this happens repeatedly, contact Customer Support.

Initialization Mismatched Buffer Counts

IP Address moved from MAC addresss ... to MAC address ....

MAC Address moved from port & said to port & said

Address Hash Table resource exhausted

Address Hash Table lookup failed

Data Path received an Invalid MAC Header

Data Path received Extended Header that is not supported

Data Path received invalid or note supported Extended Header

MAC Address was not found when DP was informed of CM's registration/inoperability

DP MTD found null buffer address in enet_tx_desc_get or mac_tx_desc_get

Data Path received invalid Extended Header

Data Path received invalid Extended Header

Data Path received invalid Extended Header

Data Path received invalid Extended Header

DP MTD occurred debug message

DP MTD occurred debug message#2

DP MTD occurred debug message#3

DP DHCP Trace encountered error: invalid ethernet length

CATV/Ethernet Rx descriptor received with FIRST + LAST not set

CATV/Ethernet Rx descriptor received with FIRST + LAST not set

dump data

dump data

System Manager fatal error is reported. Contact Customer Support.

System Manager debug information is reported

System Manager reports: SM_alloc() memory allocation failed

System Manager reports: SM_free() memory release failed

System Manager reports: Restart

Device Temperature Exceeded Specified Temperature Threshold

CPU speed detected to be: %d

Time server not specified in DHCP offer

Time server specified in DHCP offer

Time server contacted

Time server not contacted

A trap was requested specifying an unknown trap type

Error creating trap packet for a particular trap type

System Manager reports: Error processing a provisioned SNMP object

A 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.

A DHCP offer was received which is unacceptable because it lacks an option required by the device. The tag is from RFC2132.

A DHCP offer was received which lacks a gateway address.

An ICMP message (probably destination unreachable) was received when attempting to query the time server.

System Manager reports: Error processing a provisioned SNMP object

System Manager reports information

TFTP get of Provisioning file failed because the file size received exceeds the receive buffer size

DHCP received a NAK from the server and the offer is rejected

The 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.

DHCP discover received no offers or offers that were silently ignored

DHCP offer declined because it contained an IP address that is in used by another station

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

IP address is assigned so BOOTP Relay functionality can now work

Filter Module reports debug information

Filter Module reports an invalid flash value was read

Error attempting to remove IP table entry which is not active

Error attempting to remove LLC table entry which is not active

Filter Module reports information

Software upgrade reports information

Software upgrade failure notice

Software upgrade failure occured resulting in a reset

Software Upgrade Succeeded

Software upgrade was cancelled

Software Upgrade was cancelled by a new request

Software upgrade flash programming failure

Software upgrade flash programming failure resulting in a reset

Software upgrade flash erase failure

Software upgrade flash erase failure resulting in a reset

Software Upgrade: unknown flash id

Software Upgrade: invalid flash runtime info block

Software upgrade failed, tftp error, upgrade is aborted

Software upgrade failed due to a tftp error, system is reset to retry

Software upgrade NU_Alloc_Memory failure

Software Upgrade error reported

Product code in software upgrade file is not correct for the system being upgraded

There 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.

Directed by provisioning to unreachable downstream frequency

Tuner Failure

Tuner is not responding

Begin Scanning

Console Interface failure

Console Interface user logged in

Console Interface user logged out

Console Interface user login fail

Console Interface user timed out

Console Interface command

Console Interface user snmp set

Telnet Interface user snmp set

Could not initialize network interface parts

Power/correction tables for the BCM3037 were not found in the manufacturing block as expected. The power and correction were estimated instead.

The receiver has an improper hardware revision.

MAX Transit Delay on CATV

PCI Parity Error

System Reset by docsDevResetNow MIB variable

Generated when lcMcastControl is set to trap(4) and an initial IGMP Report is received from the subscriber network.

PCI parity error detected

Baseline Privacy configuration settings are present.

Failure initializing hardware.

Failure writing traffic key to hardware.

Failure writing initialization vector to hardware.

Using hardcoded RSA key pair since flash key invalid.

Failure encrypting authorization key.

Failure initializing hardware.

Failure writing traffic key to hardware.

Failure writing initialization vector to hardware.

The Source MAC Address of a BP Key Management message is not equivalent to the MAC Address passed in the message's CM identification field.

A CM has made a BP Authorization Request but a CM with the same MAC address, and different public key, is already authorized.

The CMTS hardware could not be initialized due to an FPGA programming failure.

Error reading TLV type from flash.

The CMTS hardware could not be initialized because the up-converter was not detected.

The CMTS hardware could not be initialized because the up-converter calibration data could not be found.

The CMTS hardware could not lock onto the downstream frequency.

The CMTS up-converter power supply failed

The CMTS downstream output power could not reach the desired level

The downstream channel configuration is incompatible with the CMTS hardware; the downstream channel is disabled

The upstream channel configuration is incompatible with the CMTS hardware; the upstream channel is disabled

Downstream Center Frequency has been changed

Downstream Channel Width has been changed

Downstream Modulation Type has been changed

Downstream Interleave has been changed

Downstream Channel Power has been changed

Test being run - MAC Header

Test being run - Extended Header

The ingress avoidance feature has automatically changed frequency, modulation profile and bandwidth

Front fan is not functioning properly or is powered down.

Front fan is now functioning properly.

Middle fan is not functioning properly or is powered down.

Middle fan is now functioning properly.

Back fan is not functioning properly or is powered down.

Back fan is now functioning properly.

Telnet reports: TELNET_malloc() memory allocation failed

Telnet reports: TELNET_free() memory release failed

Telnet reports: TELNET_Init() tcb_create() failed

Telnet reports: TELNET_Init() tn_create_listener() failed

Telnet reports: TELNET_Init() tcp_start() failed