DOCS-RPHY-MIB: View SNMP OID List / Download MIB

This MIB module contains the management objects for the Remote PHY Device (RPD) management. Copyright 2016-2017 Cable Television Laboratories, Inc. All rights reserved.

This table identifies the RPD for which the details and statistics are being provided.

The conceptual row of docsRphyRpdDevInfoTable.

This attribute specifies a globally unique 6-byte identifier for the RPD. By convention, an RPD SHOULD use the MAC address of the lowest numbered Ethernet port facing the CIN.

This attribute is the time (in hundredths of a second) since the RPD was last re-initialized. This value is reported by the RPD.

This attribute provides the number of crash files.

This table provides data that uniquely identifies the RPD.

The conceptual row of docsRphyRpdDevIdentificationTable.

This attribute identifies the RPD manufacturer. The format is vendor proprietary.

This attribute is the IANA-assigned SMI Network Management Private Enterprise Code of the vendor, as specified in RFC 5612.

This attribute is the model name and number used by the vendor to identify the RPD. The format is vendor proprietary.

This attribute is the serial number of the RPD. The format is vendor proprietary.

This attribute reports the device name assigned by the operator and represents a 'handle' for the RPD.

This attribute is a short text description of the RPD provided by the RPD manufacturer.

This attribute is the revision number of the hardware of the RPD. The format is vendor proprietary.

This attribute is the version number of the software currently running on the RPD. The format is vendor proprietary.

This attribute reports the version number of the boot ROM currently installed on the RPD. The format is vendor proprietary.

This attribute reports the IANA-assigned SMI Network Management Private Enterprise Code of the RPD's US burst receiver manufacturer, as specified in RFC 5612.

This attribute reports the model number used by the vendor to identify the RPD's US burst receiver. The format is vendor proprietary.

This attribute reports the driver version of the RPD's US burst receiver. The format is vendor proprietary.

This attribute reports the serial number of the RPD's US burst receiver. The format is vendor proprietary.

This attribute reports the version of the RCP protocol supported by the RPD.

This attribute reports the version of the RCP schema supported by the RPD.

This table provides location details for the RPD. The values are populated via a management interface or other automatic mechanisms (e.g. GPS).

The conceptual row of docsRphyRpdDevLocationTable.

This attribute is short text description of where the RPD has been installed, such as a street address. The format is specific to the operator.

This attribute is the latitudinal coordinate of the RPD location, expressed as a 6-byte long string as described in ISO 6709-2008 (6 digit degrees, minutes, seconds: +/-DDMMSS.S). For example: -750015.1

This attribute is the longitudinal coordinate of the RPD location, expressed as a 7-byte long string as described in ISO 6709-2008 (7 digits degrees, minutes, seconds: +/-DDDMMSS.S). For example: -0750015.1

This table provides a list of CCAP-Cores to which the RPD is authenticated, including the CCAP-Core on which the MIB is polled. For each CCAP-Core entry, the RPD indicates if that CCAP-Core is the principal Core. These values are provided by the CCAP-Core on initialization.

The conceptual row of docsRphyRpdDevCoresConnectedTable.

This attribute provides the MAC address of the CCAP-Core identified in the row entry and acts as a key.

This attribute specifies the IP address type for docsRphyRpdDevCoresConnectedAddress.

This attribute provides the IPv4 or IPv6 address of the CCAP-Core.

This attribute indicates if the CCAP-Core is the principal core. If true, this attribute indicates that this CCAP-Core is the principal core.

This attribute provides the name of the CCAP-Core as conveyed to the RPD.

This attribute provides the IANA-assigned SMI Network Management Private Enterprise Code of the vendor, as specified in RFC 1700.

This table provides information about the principal capabilities and constraints of the RPD.

The conceptual row of docsRphyRpdDevCapabilitiesTable.

This attribute provides the number of downstream unidirectional RF ports available on the RPD.

This attribute provides the number of upstream unidirectional RF ports available on the RPD.

This attribute provides the number of 10 Gigabit Ethernet ports supported by the RPD.

This attribute provides the number 1 Gigabit Ethernet ports supported by the RPD.

This attribute provides the number of downstream SC-QAM channels supported per downstream RF port.

This attribute provides the number of downstream DOCSIS 3.1 channels supported per downstream RF port.

This attribute provides the number of upstream SC-QAM channels supported per upstream RF port.

This attribute provides the number of upstream DOCSIS 3.1 channels supported per upstream RF port.

This attribute provides the number of downstream SCTE 55-1 channels supported per downstream RF port.

This attribute provides the number of upstream SCTE 55-1 channels supported per upstream RF port.

This attribute provides the number of SCTE 55-2 modules supported.

This attribute provides the number of upstream demodulators per SCTE 55-2 modules supported.

This attribute provides the number of narrowband digital forward channels supported per downstream RF port.

This attribute provides the number of narrowband digital return channels supported per upstream RF port.

This attribute provides the number of distinct PSP flows supported by the RPD on downstream data pseudowires.

This attribute provides the number of distinct PSP flows supported by the RPD on upstream data pseudowires.

This attribute provides the number of asynchronous MPEG video channels supported per downstream RF port.

This attribute provides the number of CW tone generators supported per downstream RF port.

This attribute provides the lowest frequency supported by the CW tone generators.

This attribute provides the highest frequency supported by the CW tone generators.

This attribute provides the maximum power level supported by the dedicated CW tone generators, expressed in TenthdBmV.

This attribute indicates if a QAM channel can be configured as a CW tone. A value of true indicates a QAM channel can be configured as a CW tone. A value of false indicates a QAM channel cannot be configured as a CW tone.

This attribute reports whether the RPD supports UDP encapsulation on L2TPv3 pseudowires. A value of true indicates the RPD supports UDP encapsulation on L2TPv3 pseudowires. A value of false indicates the RPD does not support UDP encapsulation on L2TPv3 pseudowires.

This attribute indicates Flow Tags support capability. If the attribute returns a value of true, the RPD supports Flow Tags on OFDMA channels. A Flow Tag is a 32-bit identifier of a MAC hardware resource (typically a Service Flow). The Flow Tag can be assigned to the scheduled SID by the CCAP Core. The RPD provides Flow Tags in UEPI headers for OFDMA channels. If the attribute returns a value of false, the RPD does not support Flow Tags.

This attribute indicates Frequency Tilt support capability. If the attribute returns a value of true, the RPD supports Frequency Tilt settings on DS RF Ports. If the attribute returns a value of false, the RPD does not support Frequency Tilt settings.

This attribute indicates the range of tilt settings that the RPD supports.

This attribute indicates buffer depth monitoring alert supported by the RPD. For each bit set to 1, the RPD is capable of monitoring buffer depth on the corresponding types of downstream channels. Bits: 'ofdmChannels': 0, 'ndfChannels': 3, 'scQamVideoChannels': 2, 'scte551Channels': 4, 'scQamDocsisChannels': 1, 'scte552Channels': 5.

This attribute indicates configuration of the output buffer depth supported by the RPD. This capability is only applicable to DOCSIS downstream channels. For each bit set to 1, the RPD is capable of configuring output buffer depth of the corresponding types of downstream channels. Bits: 'ofdmChannels': 0, 'scQamDocsisChannels': 1.

This attribute indicates the minimum interval needed by the RPD to process a UCD message received via GCP. This interval is equivalent to CM UCD processing time defined in MULPIv3.1 but its duration can be longer. The maximum value of the RPD UCD Processing time is 50000 usec. The minimum value RPD UCD Processing time is equal to CM UCD processing time (1500 usec for each changed SC-QAM channel or 2000 usec for each changed upstream OFDMA channel) defined in MULPIv3.1.

This attribute indicates the minimum Null grant interval needed by the RPD in the first MAP with incremented UCD change count. The RPD uses the Null grant in the first map to programs registers of its burst receiver during this interval. The maximum value of the RPD UCD Change Null Grant Time is 4000 usec for each changed channel. The minimum value of the RPD UCD Change Null Grant Time is defined in MULPIv3.1.

This attribute indicates whether the RPD supports Multi-Section Timing and MER reporting as opposed to just reporting a single average Timing and MER. More detail is documented in the UEPI Probe Pseudowire format of R-UEPI. notSupported: The RPD does not support Multi-Section Timing and MER Reporting supportType1: The RPD supports equally spaced non-overlapping sections supportType2: The RPD supports fully flexible sections and spacing of non-overlapping sections. Enumeration: 'supportType2': 2, 'supportType1': 1, 'notSupported': 0.

This table provides RPD channel reachability constraints. In some RPD implementations, an Ethernet interface might not have connectivity to all channels on a port of the RPD. This table is only populated if reachability constraints exist on the RPD.

The conceptual row of docsRphyRpdDevChanReachabilityTable.

This attribute identifies the Ethernet port on the RPD that has the connectivity constraint.

This attribute identifies the RF port with which the Ethernet port has a connectivity constraint.

This attribute identifies the type of channel that is supported within the specified channel index range on this RF port from the specified Ethernet interface. A row entry will be created for each channel type with a constraint. Absence of a row for a channel type means there is no constraint for that channel type.

This attribute identifies the first channel of the specified channel type in the range of channels that does not have connectivity to the specified Ethernet port.

This attribute identifies the last channel of the specified channel type in the range of channels that does not have connectivity to the specified Ethernet port.

This table provides the allocation status for the downstream channel resources on the RPD on a per DS RF port basis as well as for the upstream channel resources on a per US RF port basis.

The conceptual row of docsRphyRpdDevDsUsRfPortAllocTable.

This attribute provides the index of the downstream or upstream RF port for which resource allocation is being reported.

This attribute indicates whether the allocation applies to the upstream or downstream RF Port.

This attribute provides the number of allocated SC-QAM channels on this RF port.

This attribute provides the number of allocated DOCSIS 3.1 channels on this RF port.

This attribute provides the number of allocated SCTE 55-1 channels on this RF port.

This attribute provides the number of allocated narrowband digital forward channels (for DS RF Ports) or narrowband digital return channels (for US RF Ports) on this RF port.

This table provides details about each tunnel session between the RPD and each CCAP Core with which the RPD is associated from the RPD's point of view The attributes in this table are used to create an entry for each L2TPv3 tunnel (session) terminated at an R-PHY entity (RPD).

The conceptual row of docsRphyRpdDevL2tpSessionInfoTable. A row entry is created for every session the RPD terminates and there may be entries for sessions with different CCAP-Cores if the RPD is connected with one or more auxiliary cores.

This attribute indicates whether the IP address provide in docsRphyRpdDevL2tpSessionInfoLocalLcceIpAddr is IPv4 or IPv6.

This attribute provides the local LCCE IP address on the RPD of the session detailed in the row entry.

This attribute provides the value of the session ID assigned to the session by the RPD.

This attribute indicates whether the IP address provide in docsRphyRpdDevL2tpSessionInfoRemoteLcceIpAddr is IPv4 or IPv6.

This attribute provides the remote-side LCCE IP address of the session detailed in the row entry.

This attribute provides the value of the session ID assigned to the session by the remote peer (RPD).

This attribute provides the MAC address of the CCAP Core with which this session terminates. The CCAP Core sends its MAC address to the RPD periodically via the DOCSIS SYNC MAC Message in the Source Address field.

This attribute indicates the control connection identifier (CCID) for this session.

This attribute provides the UDP Port reported by the RPD when the DEPI session uses L2TPv3 Header Over UDP. This attribute reports a value of 0 when the session is running with the L2TPv3 Session IP Header. This port number is negotiated between the CCAP Core and the RPD according to the L2TPv3 RFC.

This attribute provides an ASCII string constructed with the form: RemoteEndId=(pp:mmm:ccc), ... { repeated for multiple endpoints } where pp is the 0-based port num signaled in the RemoteEndId AVP mmm is the channel-type enum value from the RemoteEndId AVP ccc is the channel number from the RemoteEndId AVP.

This attribute specifies whether the session is an MPT session or PSP session. Enumeration: 'psp': 1, 'mpt': 2.

This attribute specifies the type of DEPI MPT or DEPI PSP session. Enumeration: 'pspBwReqScQam': 7, 'pspNdf': 20, 'mcm': 3, 'mptLegacy': 1, 'pspRngReqOfdma': 11, 'pspProbe': 9, 'pspDepiMultichannel': 4, 'pspUepiScQam': 5, 'psp551Fwd': 16, 'pspMapOfdma': 13, 'pspSpecman': 14, 'pspBwReqOfdma': 8, 'pspPnm': 15, 'pspRngReqScQam': 10, 'psp551Ret': 17, 'pspLegacy': 2, 'psp552Fwd': 18, 'pspNdr': 21, 'pspUepiOfdma': 6, 'psp552Ret': 19, 'pspMapScQam': 12.

This attribute indicates the maximum MTU negotiated between the CCAP Core and the RPD during the session establishment process. It considers the header subtractions as indicated in the DEPI specification.

This attribute indicates the maximum MTU traversing the CIN from CCAP Core to the RPD. This is calculated by the CCAP Core by procedures such as MTU discovery as described in the DEPI specification.

This attribute provides the RPD's CIN interface MTU and is read as the value of the following L2TPV3 AVP transmitted by the RPD during session setup: DEPI Downstream PW UEPI Upstream PW DEPI Remote MTU AVP (ICRP) UEPI Remote MTU AVP (ICRP).

This attribute provides the CCAP Core's CIN interface MTU and is read as the value of the following L2TPv3 AVP as received by the device during session setup: DEPI Downstream PW UEPI Upstream PW DEPI Local MTU AVP (ICRQ) UEPI Local MTU AVP (ICRQ).

The error code raised when the session is in an error state. 'invalidMACInterfaceValue' Indicates wrong assignment of the CCAP Core MAC interface ifIndex. 'invalidInterfaceValue' Indicates wrong assignment of the CCAP Core Downstream interface ifIndex 'noResourcesForInterfaceIfIndex' Indicates the CCAP Core has no more resources to assign a session to this entry. 'l2tpv3Error' An L2TPv3 StopCCN or CDN message was issued 'ifAdminStatusSetToDown' Indicates the ifAdminStatus was set to down and the session was torn down. Enumeration: 'none': 1, 'invalidInterfaceValue': 3, 'noResourcesForInterfaceIndex': 4, 'l2tpv3Error': 5, 'invalidMACInterfaceValue': 2, 'ifAdminStatusSetToDown': 6.

The attribute contains the sysUptime when the entry was turned active.

This attribute provides the current status of the pseudowire from the point of view of the specific reporting entity (RPD). Values are as follows: 'other' indicates a vendor-specific operational status. 'up' indicates that the pseudowire is ready to pass packets. 'down' indicates that pseudowire signaling is not yet finished, or indications available at the service level indicate that the pseudowire is not passing packets. 'testing' indicates that AdminStatus at the pseudowire level is set to test. 'dormant' indicates that the pseudowire is not in a condition to pass packets but is in a 'pending' state, waiting for some external event. 'notPresent' indicates that some component is missing to accomplish the setup of the pseudowire. It can be a configuration error, incomplete configuration, or a missing H/W component. 'lowerLayerDown' indicates one or more of the lower-layer interfaces responsible for running the underlying PSN is not in OperStatus 'up' state. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'testing': 4, 'up': 2, 'down': 3, 'other': 1, 'notPresent': 6.

The attribute provides the status of the pseudowire in the local node. If the 'other' bit is set, it indicates that an additional vendor-specific status is reported. If none of the bits are set, it indicates no faults are reported. Bits: 'servicePwRxFault': 2, 'servicePwTxFault': 3, 'other': 0, 'pwNotForwarding': 1, 'psnPwRxFault': 4, 'psnPwTxFault': 5.

The attribute provides the value of sysUpTime when the session entered its current OperStatus state from the point of view of the specific reporting entity (RPD).

This table provides statistics about each tunnel session between the RPD and each CCAP Core with which the RPD is associated from the RPD's point of view.

The conceptual row of docsRphyRpdDevL2tpSessionStatsTable. This table is an augmentation of docsRphyL2tpSessionInfoTable.

This attribute indicates the count of session packets that were received out of sequence from the point of view of the reporting entity. It is vendor dependent the re-sequence of packets. Implementations that do not re-sequence packets also increase the value of ifInDiscards for the respective entry.

This table reports information about an RPD's diagnostic self test results.

The conceptual row of docsRphyRpdDevDiagStatusTable. This table returns at least one row indicating pass or failure for the diagnostic self test.

This attribute reports the probable cause of the diagnostic test error condition. Probable causes may be related to: - Communications error - Quality of Service error - Processing error - Equipment error - Environmental error The format for values returned are vendor-specific. When the self test result is a pass, this attribute returns 'Self Test Passed'.

This attribute reports a free form text description of the diagnostic test error condition. This provides supplemental information for the ProbableCause. When the self test result is a pass, this attribute returns 'No errors found'.

This attribute reports the severity level for the diagnostic test error condition. Severity levels are based on the DOCSIS event priority levels. When the self test result is a pass, this attribute returns 'information'.

This table reports the DEPI IP multicast sessions currently joined by an RPD.

The conceptual row of docsRphyRpdDevDepiMcastSessionTable. A row entry of this table represents one DEPI IP Multicast session replicated to one RPD. The indexing provides the RPD unique identifier and the (S,G) IP address pair that uniquely identifies an IP multicast session. The CCAP Core creates a row entry when it confirms an RPD has joined a DEPI IP multicast session. The CCAP Core deletes the row entry when it confirms an RPD has left the DEPI IP multicast session or disconnects its GCP session with the CCAP Core.

This key attribute reports whether the IP addresses provided in GroupIpAddr, SourceIpAddr, LocalLcceIpAddr and RemoteLcceIpAddr are IPv4 or IPv6.

This key attribute reports the group (destination) address of an IP multicast session transmitted via DEPI multicast.

For Source Specific Multicast (SSM), this key attribute reports the source IP address of an IP multicast session transmitted via DEPI multicast. For Any-Source Multicast (ASM) sessions, this attribute reports the all-0s IP address.

This attribute reports the RPD local LCCE IP address of the L2TPv3 DEPI control session that instructed the RPD to join the IP multicast session.

This attribute reports the RPD remote LCCE IP address (i.e. on the CCAP Core) of the L2TPv3 control session that instructed the RPD to join the IP multicast session.

This attribute reports the L2TPv3 Session ID assigned by the CCAP Core to the DEPI IP multicast session. The value is assigned according to the referenced specification in the range 0x80000001 through 0x8000FFFF.

This attribute reports the last time the RPD has joined this session.

This table reports event log information for an RPD.

The conceptual row of docsRphyRpdDevEventLogTable.

This key attribute provides relative ordering of the events in the event log. This attribute will always increase except when (a) the log is reset (b) the device reboots and does not implement non-volatile storage for this log, or (c) it reaches the value 2^31. The next entry for all the above cases is 1.

This attribute provides the local RPD time when this event was created.

When an event reports only one event occurrence, this attribute will have the same value as the corresponding instance of FirstTime. When an event reports multiple event occurrences, this attribute will record the local RPD time when the most recent occurrence for this event occurred.

This attribute provides the number of consecutive event occurrences reported by this event. This starts at 1 with the creation of this event occurrence and increments by 1 for each subsequent duplicate event occurrence.

This attribute provides the priority level of this event, as defined by Annex B. These are ordered from most serious (emergency) to least serious (debug).

This attribute provides the identifier of this event, as defined by Annex B.

This attribute provides the message text of this event, as defined by Annex B.

This table provides per-RPD counts of upstream SCTE 55-1 cells sent to a Network Controller.

The conceptual row of docsRphyRpdDevOob551UsChanStatusTable. A row entry of this table represents counts that are updated by the CCAP Core, which parses each upstream SCTE 55-1 packet and uses the power level and packet status (which are really cell status) bits in those packets to determine how to update the counters.

This key attribute reports the RPD RF port number carrying this SCTE 55-1 US channel.

This key attribute reports the demodulator ID (channel number) for this SCTE 55-1 US channel.

This attribute indicates whether the IP address provide in docsRphyRpdDevOob551UsChanStatusNcIpAddr is IPv4 or IPv6.

This attribute reports the IP host address of the Network Controller receiving the cells on this SCTE 55-1 US channel.

This attribute indicates whether the IP address provide in docsRphyRpdDevOob551UsChanStatusArpdSrcIpAddr is IPv4 or IPv6.

This attribute reports the virtual ARPD source IP host address used when sending cells to the Network Controller.

This attribute reports the number of perfect cells received by the demodulator for this SCTE 55-1 US channel. Perfect cells have status 0 in the US SCTE 55-1 OOB packet.

This attribute reports the number of errored cells received by the demodulator for this SCTE 55-1 US channel that were successfully corrected. Corrected cells have status 1 in the US SCTE 55-1 OOB packet.

This attribute reports the number of errored cells received by the demodulator for this SCTE 55-1 US channel that could not be corrected. Uncorrectable cells have status 3 in the US SCTE 55-1 OOB packet.

This attribute reports the total of all cells received for this SCTE 55-1 US channel.

This attribute reports the average power level from nominal of all received MAC Cells by the demodulator for this upstream SCTE 55-1 channel in tenths of a dB. The six power level bits 1 in the US SCTE 55-1 OOB packet report the nominal power per cell in units of 0.5 dB.

This attribute reports the maximum power level from nominal of all received MAC Cells by the demodulator for this upstream SCTE 55-1 channel in tenths of a dB.

This attribute reports the minimum power level from nominal of all received MAC Cells by the demodulator for this upstream SCTE 55-1 channel in tenths of a dB.

TThis attribute reports the value of sysUpTime on the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this attribute reports a zero value.

This table provides status information for the crash analysis data files.

The conceptual row of docsRphyRpdDevCrashDataFileStatusTable. A row entry of this table represents a file that is available in the device for upload or for which an upload is in progress.

This key attribute uniquely identifies a crash analysis file.

This attribute contains the name of the crash analysis file, stored in the device that is available to be uploaded to the server. Filenames are defined by the application that creates them. The RPD SHOULD generate crash analysis files with names which include RPD's unique id and a timestamp. The timestamp indicates the time when the crash has occurred with granularity of one second. The RPD SHOULD format the timestamp in the form 'Unix time', which is defined as the number of seconds that have elapsed since midnight Coordinated Universal Time (UTC), Thursday, 1 January 1970. For example, a crash file name 'RPD_crash_dump_id_00000187ADF_time_1403405123' indicates that the file was generated by RPD with Unique ID of 00.00.00.18.7A.DF on Sunday 22nd June 2014 02:45:23 AM.

This attribute reflects the status of the crash data file. The possible values are listed below. other(1) - Any condition not covered by the other defined values. availableForUpload(2) - The file is available to be uploaded. uploadInProgress(3) - The file is currently being uploaded. The file is not available for another upload in this state. uploadCompleted(4) - The file was successfully uploaded. The file is available for another upload. uploadPending(5) - The file has been selected for upload but a condition does not allow the upload to take place. The upload will start when the condition blocking uploads has been removed. For example, another upload that is currently in progress could cause this value to be returned. uploadPending status can also indicate a situation where the RPD is waiting to retry the upload after the initial attempt(s) has failed. The file is not available for another upload in this state. uploadCancelled(6) - An upload was cancelled before it completed. The file is available for another upload. error(7) - An error occurred and the file was not successfully uploaded. The file is available for another upload. Enumeration: 'availableForUpload': 2, 'uploadCompleted': 4, 'other': 1, 'uploadPending': 5, 'error': 7, 'uploadInProgress': 3, 'uploadCancelled': 6.

This table provide individual upstream signal quality values for RPDs.

The conceptual row of docsRphyRpdDevUsSignalQualityTable. A row entry of this table represents the upstream signal quality values of a single RPD

This key attribute reports the RPD RF port number carrying this US channel. This corresponds to the attribute RpdUsRfPortNum of the RpdUsRfPortRef object in the configuration Information Model.

This attribute corresponds to the ifIndex of the Upstream Physical Channel of the CCAP Core for this US channel. Note that with upstream virtual combining, this attribute corresponds to the same CCAP Core ifIndex for different RPD unique Ids.

This attribute reports an in-channel received average Modulation Error Ratio (MER). An RxMER sample is defined as an estimate, provided by the demodulator, of the ratio: (average constellation energy with equally likely symbols) / (average squared magnitude of error vector) RxMER is measured just prior to FEC (trellis/Reed-Solomon) decoding. RxMER includes the effects of the HFC channel as well as implementation effects of the modulator and demodulator. Error vector estimation may vary among demodulator implementations. The CCAP Core RxMER is averaged over a given number of bursts at the burst receiver, which may correspond to transmissions from multiple users. In the case of S-CDMA mode, RxMER is measured on the de-spread signal. For OFDMA channels, this attribute always reports 0.

This attribute reports RxMerSamples which is a statistically significant number of bursts for the CCAP Core, processed to arrive at the RxMER value. For the CCAP Core, the MER measurement includes only valid bursts that are not in contention regions. For OFDMA channels, this attribute always reports 0.

This attribute reports the count of codewords received on this channel without error. This includes all codewords, whether or not they were part of frames destined for this device. Reference: OFDMA FEC Error Reporting section of this specification.

This attribute reports the count of codewords received on this channel with correctable errors. This includes all codewords, whether or not they were part of frames destined for this device. Reference: OFDMA FEC Error Reporting section of this specification.

This attribute reports the count of codewords received on this channel with uncorrectable errors. This includes all codewords, whether or not they were part of frames destined for this device. Reference: OFDMA FEC Error Reporting section of this specification.

This table reports entities that exist within each Remote PHY Node that is communicating with the CCAP Core. Because the entities exist within the Remote PHY Nodes and not the CCAP Core, the RPDs communicate this information to the CCAP core via GCP. This object is based on the entPhysicalTable object specified in the ENTITY-MIB from RFC 4133. See the reference for additional requirements.

Information about a particular physical entity. Each entry provides objects (docsRphyRpdIfPhysEntityDescr, docsRphyRpdIfPhysEntityVendorType, and docsRphyRpdIfPhysEntityClass) to help an NMS identify and characterize the entry and objects (docsRphyRpdIfPhysEntityContainedIn and docsRphyRpdIfPhysEntityParentRelPos) to help an NMS relate the particular entry to other entries in this table.

This key attribute reports an arbitrary value that uniquely identifies the physical entity. Index values for different physical entities are not necessarily contiguous.

A textual description of physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity and should be set to a distinct value for each version or model of the physical entity.

An indication of the vendor-specific hardware type of the physical entity. Note that this is different from the definition of MIB-II's sysObjectID. An agent should set this object to an enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of docsRphyRpdIfPhysEntityClass is used to indicate the general type of hardware device. If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent, then the value { 0 0 } is returned.

The value of docsRphyRpdIfPhysEntityIndex for the physical entity that 'contains' this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity. Note that the set of 'containment' relationships define a strict hierarchy; that is, recursion is not allowed. In the event that a physical entity is contained by more than one physical entity (e.g., double-wide modules), this object should identify the containing entity with the lowest value of docsRphyRpdIfPhysEntityIndex.

An indication of the general hardware type of the physical entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity, or the primary class if there is more than one entity. If no appropriate standard registration identifier exists for this physical entity, then the value 'other(1)' is returned. If the value is unknown by this agent, then the value 'unknown(2)' is returned.

An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as docsRphyRpdIfPhysEntityEntries that share the same instance values of each of the docsRphyRpdIfPhysEntityContainedIn and docsRphyRpdIfPhysEntityClass objects. An NMS can use this object to identify the relative ordering for all sibling components of a particular parent (identified by the docsRphyRpdIfPhysEntityContainedIn instance in each sibling entry). If possible, this value should match any external labeling of the physical component. For example, for a container (e.g., card slot) labeled as 'slot #3', docsRphyRpdIfPhysEntityParentRelPos should have the value '3'. Note that the docsRphyRpdIfPhysEntityEntry for the module plugged in slot 3 should have an docsRphyRpdIfPhysEntityParentRelPos value of '1'. If the physical position of this component does not match any external numbering or clearly visible ordering, then user documentation or other external reference material should be used to determine the parent-relative position. If this is not possible, then the agent should assign a consistent (but possibly arbitrary) ordering to a given set of 'sibling' components, perhaps based on internal representation of the components. If the agent cannot determine the parent-relative position for some reason, or if the associated value of docsRphyRpdIfPhysEntityContainedIn is '0', then the value '-1' is returned. Otherwise, a non-negative integer is returned, indicating the parent-relative position of this physical entity. Parent-relative ordering normally starts from '1' and continues to 'N', where 'N' represents the highest positioned child entity. However, if the physical entities (e.g., slots) are labeled from a starting position of zero, then the first sibling should be associated with an docsRphyRpdIfPhysEntityParentRelPos value of '0'. Note that this ordering may be sparse or dense, depending on agent implementation. The actual values returned are not globally meaningful, as each 'parent' component may use different numbering algorithms. The ordering is only meaningful among siblings of the same parent component. The agent should retain parent-relative position values across reboots, either through algorithmic assignment or use of non-volatile storage.

The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name (e.g., 'console') or a simple component number (e.g., port or module number, such as '1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of docsRphyRpdIfPhysEntityName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.

The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present). Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific hardware revision string is associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.

The vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.

The vendor-specific software revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific software programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.

The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present). On the first instantiation of a physical entity, the value of docsRphyRpdIfPhysEntitySerialNum associated with that entity is set to the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown or non-existent, the docsRphyRpdIfPhysEntitySerialNum will be set to a zero-length string instead. Note that implementations that can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the docsRphyRpdIfPhysEntitySerialNum object. Agents that cannot provide non-volatile storage for the docsRphyRpdIfPhysEntitySerialNum strings are not required to implement write access for this object. Not every physical component will have a serial number, or even need one. Physical entities for which the associated value of the docsRphyRpdIfPhysEntityIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique serial numbers. An agent does not have to provide write access for such entities and may return a zero-length string.

The name of the manufacturer of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present). Note that comparisons between instances of the docsRphyRpdIfPhysEntityModelName, docsRphyRpdIfPhysEntityFirmwareRev, docsRphyRpdIfPhysEntitySoftwareRev, and the docsRphyRpdIfPhysEntitySerialNum objects are only meaningful amongst docsRphyRpdIfPhysEntityEntries with the same value of docsRphyRpdIfPhysEntityMfgName. If the manufacturer name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.

The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself. If the model name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.

This object is an 'alias' name for the physical entity, as specified by a network manager, and provides a non-volatile 'handle' for the physical entity. On the first instantiation of a physical entity, the value of docsRphyRpdIfPhysEntityAlias associated with that entity is set to the zero-length string. However, the agent may set the value to a locally unique default value, instead of a zero-length string.

This object is a user-assigned asset tracking identifier (as specified by a network manager) for the physical entity and provides non-volatile storage of this information. On the first instantiation of a physical entity, the value of docsRphyRpdIfPhysEntityAssetID associated with that entity is set to the zero-length string. Not every physical component will have an asset tracking identifier or even need one. Physical entities for which the associated value of the docsRphyRpdIfPhysEntityIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique asset tracking identifier. An agent does not have to provide write access for such entities and may instead return a zero-length string. If no asset tracking information is associated with the physical component, then this object will contain a zero-length string.

This object indicates whether or not this physical entity is considered a 'field replaceable unit' by the vendor. If this object contains the value 'true(1)', then this docsRphyRpdIfPhysEntityEntry identifies a field replaceable unit. For all docsRphyRpdIfPhysEntityEntries that represent components permanently contained within a field replaceable unit, the value 'false(2)' should be returned for this object.

This object contains the date of manufacturing of the managed entity. If the manufacturing date is unknown or not supported, the object is not instantiated. The special value '0000000000000000'H may also be returned in this case.

This object contains identification information about the physical entity. The object contains URIs; therefore, the syntax of this object must conform to RFC 3986, Section 3. Multiple URIs may be present and are separated by white space characters. Leading and trailing white space characters are ignored. If no URI identification information is known about the physical entity, the object is not instantiated. A zero-length octet string may also be returned in this case.

This object contains identification information about the physical entity. The object contains a Universally Unique Identifier, the syntax of this object must conform to RFC 4122, Section 4.1. A zero-length octet string is returned if no UUID information is known.

If the entity represents an ifTable interface on the CCAP Core, this attribute provides the ifIndex assigned by the CCAP Core to that entity. Otherwise, this attribute returns a value of zero.

This table contains one row per physical sensor represented by an associated row in the docsRphyRpdIfPhysEntityTable. See the reference for additional requirements.

Information about a particular physical sensor. An entry in this table describes the present reading of a sensor, the measurement units and scale, and sensor operational status. Entries are created in this table by the agent. The CCAP Core SHOULD create an entry for each physical sensor at the same time as the associated Entity table instance. The CCAP Core SHOULD delete an entry if the associated Entity table entry is deleted.

This attribute reports the type of data returned by the associated Value attribute. The CCAP Core SHOULD set the value during instance creation. The CCAP Core SHOULD NOT change the value during operation.

This attribute reports a data scaling factor, represented with an International System of Units (SI) prefix. The actual data units are determined by examining this attribute together with the associated SensorType attribute. This attribute is defined together with SensorType and Precision. Together, these three attributes are used to identify the semantics of the Value attribute.

This attribute reports the number of decimal places of precision in fixed-point sensor values returned by the associated Value attribute. This attribute should be set to '0' when the associated SensorType value is not a fixed-point type: e.g., 'percentRH(9)', 'rpm(10)', 'cmm(11)', or 'truthvalue(12)'.

This attribute reports the most recent measurement obtained by the RPD for this sensor. To correctly interpret the value of this object, the associated SensorType, SensorScale, and SensorPrecision attributes must also be examined.

The operational status of the sensor.

A textual description of the data units that should be used in the display of SensorValue.

This attribute reports the value of RpdSysUpTime at the time the status and/or value of this sensor was last obtained by the RPD.

This attribute reports an indication of the frequency that the CCAP Core updates the associated Value object, represented in milliseconds. The value zero indicates: - the sensor value is updated on demand - the sensor value is updated when the sensor value changes (event-driven) - the RPD does not know the update rate.

This table provides details about the Ethernet interfaces on the RPD. The attributes of this object are based on the ifTable/ifXTable specified in RFC 2863. The CCAP Core MUST create an instance of this object for every Ethernet interface on the RPD. See the reference for additional requirements.

An entry containing management information applicable to a particular interface. The Ethernet IfIndex is chosen by the RPD.

This key attribute reports a unique index for this Ethernet port interface.

A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.

This attribute reports a textual string representing a name that describes the interface. The CCAP Core MUST populate this object with the ID that is used in GCP for this port.

This attribute reports an Alias for the interface. On the first instantiation of an interface, the value of Alias associated with that interface is the zero-length string. As and when a value is written into an instance of Alias through a network management operation, then the RPD retains the supplied value in the Alias instance associated with the same interface for as long as that interface remains instantiated, including across all re-initializations/reboots of the network management system, including those which result in a change of the interface's EnetPortIndex value.

This attribute reports the type of interface. Additional values for Type are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention. The types are defined in the IANAifType-MIB. The value reported by this attribute is ethernetCsmacd.

This attribute reports the size of the largest packet which can be sent/received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface.

This attribute reports the interface's address at its protocol sub-layer. For example, for an 802.x interface, this attribute normally contains a MAC address. The interface's media-specific MIB defines the bit and byte ordering and the format of the value of this attribute. For interfaces which do not have such an address (e.g., a serial line), this attribute reports an octet string of zero length.

This attribute reports the state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with AdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, AdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state). Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This attribute reports the current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If AdminStatus is down(2) then ifOperStatus should be down(2). If AdminStatus is changed to up(1), then OperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'unknown': 4, 'testing': 3, 'up': 1, 'down': 2, 'notPresent': 6.

This attribute reports the value of RpdSysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this attribute reports a zero value.

This attribute reports whether linkup/linkdown traps are generated for this interface. A value of true indicates that traps are enabled. A value of false indicates that traps are disabled.

This attribute reports an estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this attribute reports a value of 'n' then the speed of the interface is somewhere in the range of 'n-500,000' to 'n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this attribute reports the nominal bandwidth.

This attribute reports a value of '2' (false) if this interface only accepts packets/frames that are addressed to this interface. This attribute reports a value of '1' (true) when the station accepts all packets/frames transmitted on the media. The value of PromiscuousMode does not affect the reception of broadcast and multicast packets/frames by the interface.

This attribute reports the value 'true' if the interface sublayer has a physical connector and the value 'false' otherwise.

This table reports statistics for the Ethernet interfaces on the RPD. The attributes of this object are based on the ifTable/ifXTable specified in RFC 2863. The CCAP Core MUST create an instance of this object for every EnetIf object instance. Discontinuities in the value of these counters can occur at reinitialization of the managed system, and at other times as indicated by the value of CounterDiscontinuityTime. See the reference for additional requirements.

An entry containing statistical information applicable to a particular RPD ethernet interface.

The total number of octets received on the interface, including framing characters.

The total number of octets transmitted out of the interface, including framing characters.

The total number of frames received on the interface, including framing characters.

The total number of frames transmitted out of the interface, including framing characters.

The number of octets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer.

The total number of octets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.

The number of frames, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer.

The total number of frames that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent.

The number of octets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses.

The total number of octets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses.

The number of frames, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses.

The total number of frames that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses.

The number of octets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer.

The total number of octets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent.

The number of frames, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer.

The total number of frames that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent.

The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.

The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.

For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character- oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol.

For packet-oriented interfaces, the number of outbound packets that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the number of outbound transmission units that could not be transmitted because of errors.

For packet-oriented interfaces, the number of packets received via the interface which were discarded because of an unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol multiplexing the number of transmission units received via the interface which were discarded because of an unknown or unsupported protocol. For any interface that does not support protocol multiplexing, this counter will always be 0.

The value of sysUpTime on the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 object contained in the docsRphyRpdIfEnetStatsTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.

If the RPD implements an Entity for an Ethernet port (which is optional), this table provides the mapping between the RPD's EnetPortIndex as signaled in GCP and the corresponding docsRphyRpdIfPhysEntityIndex assigned by the CCAP Core to report that entity. See the reference for additional requirements.

An entry in docsRphyRpdIfRpdEnetToCoreEntityMapTable.

The value of this attribute must match the value of docsRphyRpdIfPhysEntityIndex for the row in docsRphyRpdIfPhysEntityTable that reports the RPD Ethernet port signaled in GCP with EnetPortIndex.

This table maps certain CCAP Core ifTable interfaces identified with an ifIndex to an RPD interface identified in GCP. See the reference for additional requirements.

An entry in docsRphyRpdIfCoreToRpdMapTable. An entry exists for each RPD interface directly represented in the CCAP ifTable. The IfIndex corresponds to a CCAP Core ifIndex for one of the following interface types implemented on an RPD: - docsCableDownstream(128) - docsCableUpstreamChannel(205) - docsCableUpstreamRfPort(255) - docsCableDownstreamRfPort(256) - docsCableDownstreamOfdm(277) - docsCableUpstreamOfdma(278) Note that this table does not contain an instance for ifType ethernetCsmacd(6) because the Ethernet ports of the RPD are considered internal to a logical CCAP and are not reported in the CCAP ifTable.

This attribute specifies the MAC address associated with the lowest numbered CIN facing Ethernet port. The value of this attribute matches the value of the docsRphyRpdDevInfoUniqueId attribute from the docsRphyRpdDevInfoTable.

This attribute reports the direction of an RF port, which together with RpdRfPortIndex uniquely identifies an RF port on the RPD. The RF port direction is signalled in the GCP 'RfPortType' TLV 13.2 for an RF port interface or implied by the value of the GCP 'RfChannelType' TLV 12.2 for an RF channel interface.

This attribute reports the Index of an RF port on an RPD, which together with RpdRfPortDirection uniquely identifies an RF port on the RPD. The value matches the value signaled in GCP 'RfPortIndex' TLV 12.1 or the GCP 'RfPortIndex1' TLV 13.1.

For RF channel interfaces, This attribute reports the type of the channel as signaled in the GCP 'RfChannelType' TLV 12.2. For RF port interfaces, this attribute must be set to other(0). Each value of this attribute corresponds to a separate sequence of channel indices.

For interfaces corresponding to RF channels, this attribute reports the channel of the type specified in RpdRfChannelType, and matches the value signaled in the GCP 'RfChannelIndex' TLV 12.3. For RF port interfaces, this attribute reports 0.

This table maps certain RPD interface identified via GCP integers to an ifIndex reported by the CCAP Core. This table instruments the same information as the docsRphyRpdIfCoreToRpdMapTable, but with different indexing than that table. See the reference for additional requirements.

An entry in docsRphyRpdIfRpdToCoreMapTable. An entry exists for each RPD interface directly represented in the CCAP ifTable. The index 'CoreIfIndex' corresponds to a CCAP core ifIndex for one of the following interface types implemented on an RPD: - docsCableDownstream(128) - docsCableUpstreamChannel(205) - docsCableUpstreamRfPort(255) - docsCableDownstreamRfPort(256) - docsCableDownstreamOfdm(277) - docsCableUpstreamOfdma(278) Note that this table does not contain an instance for ifType ethernetCsmacd(6) because the Ethernet ports of the RPD are considered internal to a logical CCAP and are not reported in the CCAP ifTable.

This attribute reports the direction of an RF port, which together with RpdRfPortIndex uniquely identifies an RF port on the RPD. The RF port direction is signalled in the GCP 'RfPortType' TLV 13.2 for an RF port interface or implied by the value of the GCP 'RfChannelType' TLV 12.2 for an RF channel interface.

This attribute reports the Index of an RF port on an RPD, which together with RpdRfPortDirection uniquely identifies an RF port on the RPD. The value matches the value signaled in GCP 'RfPortIndex' TLV 12.1 or the GCP 'RfPortIndex1' TLV 13.1.

For RF channel interfaces, This attribute reports the type of the channel as signaled in the GCP 'RfChannelType' TLV 12.2. For RF port interfaces, this attribute must be set to other(0). Each value of this attribute corresponds to a separate sequence of channel indices.

For interfaces corresponding to RF channels, this attribute reports the channel of the type specified in RpdRfChannelType, and matches the value signaled in the GCP 'RfChannelIndex' TLV 12.3. For RF port interfaces, this attribute reports 0.

This key attribute reports the CCAP Core IfIndex for the RPD Interface identified in GCP.

The table containing per-RPD IPv4-specific information.

An entry containing IPv4-specific information for a specific RPD.

The default value inserted into the Time-To-Live field of the IPv4 header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.

This attribute reports the value of RpdSysUpTime on the most recent occasion at which an instance of the Ipv4Interface object was added or deleted, or when a ReasmMaxSize or an EnableStatus attribute of the Ipv4Interface object was modified.

The table containing per-RPD IPv6-specific information.

An entry containing IPv6-specific information for a specific RPD.

The default value inserted into the Hop Limit field of the IPv6 header of datagrams originated at this entity whenever a Hop Limit value is not supplied by the transport layer protocol.

This attribute reports the value of RpdSysUpTime on the most recent occasion at which an instance of the Ipv6Interface object was added or deleted or when a ReasmMaxSize, InterfaceIdentifier, EnableStatus, ReachableTime, RetransmitTime, or Forwarding attribute of the Ipv6Interface object was modified.

This attribute reports the value of RpdSysUpTime on the most recent occasion at which an instance of the ipIfStats object was added or deleted.

The table containing per-interface IPv4-specific information.

An entry containing IPv4-specific information for an RPD's ethernet port.

The indication of whether IPv4 is enabled (up) or disabled (down) on this interface. This object does not affect the state of the interface itself, only its connection to an IPv4 stack. The IF-MIB should be used to control the state of the interface. Enumeration: 'down': 2, 'up': 1.

The time between retransmissions of ARP requests to a neighbor when resolving the address or when probing the reachability of a neighbor.

The table containing per-interface IPv6-specific information.

An entry containing IPv6-specific information for an RPD's ethernet port.

The Interface Identifier for this interface. The Interface Identifier is combined with an address prefix to form an interface address. By default, the Interface Identifier is auto-configured according to the rules of the link type to which this interface is attached. A zero length identifier may be used where appropriate.

The indication of whether IPv6 is enabled (up) or disabled (down) on this interface. This object does not affect the state of the interface itself, only its connection to an IPv6 stack. The IF-MIB should be used to control the state of the interface. Enumeration: 'down': 2, 'up': 1.

The time a neighbor is considered reachable after receiving a reachability confirmation.

The time between retransmissions of Neighbor Solicitation messages to a neighbor when resolving the address or when probing the reachability of a neighbor.

This table provides statistics for IP Packets sent or received by an RPD's own IP Address. It is modeled after the IP-MIB IpIfStatsTable described in RFC 4293; however, all counters are 64 bit. Discontinuities in the value of these counters can occur at re-initialization of the management system, and at other times as indicated by the value of the DiscontinuityTime attribute in this table.

An interface statistics entry containing objects for a particular interface and version of IP.

This key attribute reports the IP version of this entry.

The total number of input IP datagrams received, including those received in error.

The total number of octets received in input IP datagrams, including those received in error.

The number of input IP datagrams discarded due to errors in their IP headers, including version number mismatch, other format errors, hop count exceeded, errors discovered in processing their IP options, etc.

The number of input IP datagrams discarded because no route could be found to transmit them to their destination.

The number of input IP datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., ::0). For entities that are not IP routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.

The number of locally-addressed IP datagrams received successfully but discarded because of an unknown or unsupported protocol. When tracking interface statistics, the counter of the interface to which these datagrams were addressed is incremented. This interface might not be the same as the input interface for some of the datagrams.

The number of input IP datagrams discarded because the datagram frame didn't carry enough data.

The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.

The total number of datagrams successfully delivered to IP user-protocols (including ICMP).

The total number of IP datagrams that local IP user- protocols (including ICMP) supplied to IP in requests for transmission.

The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in docsRphyRpdIpIfStatsOutForwDatagrams if any such datagrams met this (discretionary) discard criterion.

The total number of IP datagrams that this entity supplied to the lower layers for transmission.

The total number of octets in IP datagrams delivered to the lower layers for transmission.

The number of IP multicast datagrams received.

The total number of octets received in IP multicast datagrams.

The number of IP multicast datagrams transmitted.

The total number of octets transmitted in IP multicast datagrams.

The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity.

The minimum reasonable polling interval for this entry. This object provides an indication of the minimum amount of time required to update the counters in this entry.

This table contains addressing information relevant to the entity's interfaces. This table does not contain multicast address information. Note well: When including IPv6 link-local addresses in this table, the entry must use an InetAddressType of 'docsRphyRpdIpv6z' in order to differentiate between the possible interfaces.

An address mapping for a particular interface.

The address type of docsRphyRpdIpAddressAddr.

The IP address to which this entry's addressing information pertains. The address type of this object is specified in AddrType. Implementors need to be aware that if the size of Addr exceeds 116 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.

This attribute reports a unique index for this Ethernet port interface.

The type of address. broadcast(3) is not a valid value for IPv6 addresses (RFC 3513). Enumeration: 'unicast': 1, 'broadcast': 3, 'anycast': 2.

This attribute reports the prefix length associated with this address.

The origin of the address.

The status of the address, describing if the address can be used for communication. In the absence of other information, an IPv4 address is always preferred(1).

The value of sysUpTime at the time this entry was created. If this entry was created prior to the last re- initialization of the local network management subsystem, then this object contains a zero value.

The value of sysUpTime at the time this entry was last updated. If this entry was updated prior to the last re- initialization of the local network management subsystem, then this object contains a zero value.

The IP Address Translation table used for mapping from IP addresses to physical addresses. The Address Translation tables contain the IP address to 'physical' address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. While many protocols may be used to populate this table, ARP and Neighbor Discovery are the most likely options.

Each entry contains one IP address to `physical' address equivalence.

The type of NetAddress.

The IP Address corresponding to the media-dependent 'physical' address. The address type of this object is specified in AddressType. Implementors need to be aware that if the size of NetAddress exceeds 115 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.

The media-dependent 'physical' address.

This attribute reports the value of RpdSysUpTime at the time this entry was last updated. If this entry was updated prior to the last re-initialization of the local network management subsystem, then this attribute contains a zero value.

The type of mapping. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant Type attribute. The 'dynamic(3)' type indicates that the IP address to physical addresses mapping has been dynamically resolved using e.g., IPv4 ARP or the IPv6 Neighbor Discovery protocol. The 'static(4)' type indicates that the mapping has been statically configured. Both of these refer to entries that provide mappings for other entities addresses. The 'local(5)' type indicates that the mapping is provided for an entity's own interface address. Enumeration: 'static': 4, 'other': 1, 'dynamic': 3, 'invalid': 2, 'local': 5.

The Neighbor Unreachability Detection state for the interface when the address mapping in this entry is used. If Neighbor Unreachability Detection is not in use (e.g. for IPv4), this object is always unknown(6). Enumeration: 'unknown': 6, 'probe': 4, 'invalid': 5, 'delay': 3, 'reachable': 1, 'stale': 2, 'incomplete': 7.

The table used to describe the default routers known to the RPD.

Each entry contains information about a default router known to the RPD.

This key attribute reports the type of IP address in the Address attribute.

The IP address of the default router represented by this row. The address type of this object is specified in AddressType. Implementers need to be aware that if the size of Address exceeds 115 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.

The remaining length of time, in seconds, that this router will continue to be useful as a default router. A value of zero indicates that it is no longer useful as a default router. It is left to the implementer of the MIB as to whether a router with a lifetime of zero is removed from the list. For IPv6, this value should be extracted from the router advertisement messages.

An indication of preference given to this router as a default router as described in the Default Router Preferences document. Treating the value as a 2 bit signed integer allows for simple arithmetic comparisons. For IPv4 routers or IPv6 routers that are not using the updated router advertisement format, this object is set to medium (0). Enumeration: 'high': 1, 'medium': 0, 'reserved': -2, 'low': -1.

The table of system-wide per-version, per-message type ICMP counters.

A conceptual row in the docsRphyRpdIpIcmpMsgStatsTable. The system should track each ICMP type value, even if that ICMP type is not supported by the system. However, a given row need not be instantiated unless a message of that type has been processed, i.e., the row for Type=X MAY be instantiated before but is required to be instantiated after the first message with Type=X is received or transmitted. After receiving or transmitting any succeeding messages with Type=X, the relevant counter must be incremented.

The IP version of the statistics. Statistics are provided for each IP version supported.

The ICMP type field of the message type being counted by this row. Note that ICMP message types are scoped by the address type in use.

The number of input packets for this AF and type.

The number of output packets for this AF and type.

This table provides details for every session that terminates at the CCAP Core from the CCAP Core's point of view. There will be multiple sessions for each RPD with which the CCAP Core is associated.

The conceptual row of docsRphyCcapL2tpSessionInfoTable. A row entry is created for every session the CCAP-Core terminates.

This attribute indicates whether the IP address provide in docsRphyCcapL2tpSessionInfoLocalLcceIpAddr is IPv4 or IPv6.

This attribute provides the local LCCE IP address on the CCAP Core of the session detailed in the row entry.

This attribute provides the value of the session ID assigned to the session by the CCAP Core.

This attribute indicates whether the IP address provide in docsRphyCcapL2tpSessionInfoRemoteLcceIpAddr is IPv4 or IPv6.

This attribute provides the remote-side LCCE IP address of the session detailed in the row entry.

This attribute provides the value of the session ID assigned to the session by the remote peer (CCAP Core).

This attribute provides the MAC address of the CCAP Core with which this session terminates. The CCAP Core sends its MAC address to the RPD periodically via the DOCSIS SYNC MAC Message in the Source Address field.

This attribute indicates the control connection identifier (CCID) for this session.

This attribute provides the UDP Port reported by the CCAP Core when the DEPI session uses L2TPv3 Header Over UDP. This attribute reports a value of 0 when the session is running with the L2TPv3 Session IP Header. This port number is negotiated between the CCAP Core and the RPD according to the L2TPv3 RFC.

This attribute provides an ASCII string constructed with the form: RemoteEndId=(pp:mmm:ccc), ... { repeated for multiple endpoints } where pp is the 0-based port num signaled in the RemoteEndId AVP mmm is the channel-type enum value from the RemoteEndId AVP ccc is the channel number from the RemoteEndId AVP.

This attribute specifies whether the session is an MPT session or PSP session. Enumeration: 'psp': 1, 'mpt': 2.

This attribute specifies the type of DEPI MPT or DEPI PSP session. Enumeration: 'pspBwReqScQam': 7, 'pspNdf': 20, 'mcm': 3, 'mptLegacy': 1, 'pspRngReqOfdma': 11, 'pspProbe': 9, 'pspDepiMultichannel': 4, 'pspUepiScQam': 5, 'psp551Fwd': 16, 'pspMapOfdma': 13, 'pspSpecman': 14, 'pspBwReqOfdma': 8, 'pspPnm': 15, 'pspRngReqScQam': 10, 'psp551Ret': 17, 'pspLegacy': 2, 'psp552Fwd': 18, 'pspNdr': 21, 'pspUepiOfdma': 6, 'psp552Ret': 19, 'pspMapScQam': 12.

This attribute indicates the maximum MTU negotiated between the CCAP Core and the RPD during the session establishment process. The MTU is the layer 3 payload of a layer 2 frame.

This attribute indicates the maximum MTU traversing the CIN from CCAP Core to the RPD. This is calculated by the CCAP Core by procedures such as MTU discovery as described in the DEPI specification.

This attribute provides the RPD's CIN interface MTU and is read as the value of the following L2TPV3 AVP transmitted by the RPD during session setup: DEPI Downstream PW UEPI Upstream PW DEPI Remote MTU AVP (ICRP) UEPI Remote MTU AVP (ICRP).

This attribute provides the CCAP Core's CIN interface MTU and is read as the value of the following L2TPv3 AVP as received by the device during session setup: DEPI Downstream PW UEPI Upstream PW DEPI Local MTU AVP (ICRQ) UEPI Local MTU AVP (ICRQ).

This attribute returns true if the CCAP Core includes DOCSIS MAP messages and other MAC Management messages in the interface entry associated with this control entry. The CCAP Core determines whether the interface includes DOCSIS messages as part of the payload.

The error code raised when the session is in an error state. 'invalidMACInterfaceValue' Indicates wrong assignment of the CCAP Core MAC interface ifIndex. 'invalidInterfaceValue' Indicates wrong assignment of the CCAP Core Downstream interface ifIndex 'noResourcesForInterfaceIfIndex' Indicates the CCAP Core has no more resources to assign a session to this entry. 'l2tpv3Error' An L2TPv3 StopCCN or CDN message was issued 'ifAdminStatusSetToDown' Indicates the ifAdminStatus was set to down and the session was torn down. Enumeration: 'none': 1, 'invalidInterfaceValue': 3, 'noResourcesForInterfaceIndex': 4, 'l2tpv3Error': 5, 'invalidMACInterfaceValue': 2, 'ifAdminStatusSetToDown': 6.

The attribute contains the sysUptime when the entry was turned active.

This attribute provides the current status of the pseudowire from the point of view of the specific reporting entity (CCAP-Core). Values are as follows: 'other' indicates a vendor-specific operational status. 'up' indicates that the pseudowire is ready to pass packets. 'down' indicates that pseudowire signaling is not yet finished, or indications available at the service level indicate that the pseudowire is not passing packets. 'testing' indicates that AdminStatus at the pseudowire level is set to test. 'dormant' indicates that the pseudowire is not in a condition to pass packets but is in a 'pending' state, waiting for some external event. 'notPresent' indicates that some component is missing to accomplish the setup of the pseudowire. It can be a configuration error, incomplete configuration, or a missing H/W component. 'lowerLayerDown' indicates one or more of the lower-layer interfaces responsible for running the underlying PSN is not in OperStatus 'up' state. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'testing': 4, 'up': 2, 'down': 3, 'other': 1, 'notPresent': 6.

The attribute provides the status of the pseudowire in the local node. If the 'other' bit is set, it indicates that an additional vendor-specific status is reported. If none of the bits are set, it indicates no faults are reported. Bits: 'servicePwRxFault': 2, 'servicePwTxFault': 3, 'other': 0, 'pwNotForwarding': 1, 'psnPwRxFault': 4, 'psnPwTxFault': 5.

The attribute provides the value of sysUpTime when the session entered its current OperStatus state from the point of view of the specific reporting entity (CCAP-Core).

This table represents a PSP Flow of L2TP session or for those sessions, which do not have PSP Flows, represents entire session. In the latter case the PSP Flow Id by convention is zero.

The conceptual row of docsRphyCcapL2tpSessionFlowTable. This is an extension to docsRphyCcapL2tpSessionInfoTable for the CCAP Core.

This attribute identifies a PSP Flow within the session. For sessions which do not have PSP Flows, this attribute is zero.

This table provides statistics for every session that terminates at the CCAP-Core from the CCAP Core's point of view. It also provides statistics about each tunnel session between the RPD and each CCAP Core with which the RPD is associated from the RPD's point of view.

The conceptual row of docsRphyCcapL2tpSessionStatsTable. This table is an augmentation of docsRphyCcapL2tpSessionFlowTable.

This attribute indicates the count of session packets that were received out of sequence from the point of view of the reporting entity. It is vendor dependent the re-sequence of packets. Implementations that do not re-sequence packets also increase the value of ifInDiscards for the respective entry.

This table provides measurements on the latency on the CIN link for the session as measured by the CCAP-Core. These measurements are based on the DEPI latency measurement, specified in the Remote Downstream External PHY Interface Specification.

The conceptual row of docsRphyCcapCinLatencyTable. A row entry is created for every session the CCAP Core terminates. This table is an augmentation of docsRphyCcapL2tpSessionFlowTable for the CCAP Core.

This attribute indicates the latest latency measurement on this session.

This attribute indicates the sysUpTime value of the last time the docsRphyCcapCinLatencyPerfLastVal attribute was updated.

This attribute provides the time interval used to measure periodically the CIN latency per DEPI session. Active measurement of CIN latency applies to active DEPI sessions only. This attribute is constrained to 420 seconds to prevent Master Clock counter overruns. A value zero indicates no CIN latency measurements are configured to be performed.

This table provides sequence of recent measurements of the CIN latency on the network as measured by the CCAP Core. When the table is full, the oldest measurement is replaced with a new one. This table is based on the docsIfMCmtsDepiSessionCinLatencyPerfTable object defined in the DOCS-IF-M-CMTS-MIB and has been extended for Remote PHY.

The conceptual row of docsRphyCcapSessionCinDsLatencyStatsTable. A row entry is created for every session the CCAP Core terminates. This is an extension to docsRphyCcapL2tpSessionFlowTable for the CCAP Core.

This attribute indicates the interval sequence where the CIN latency measurement was taken. It is valid in an implementation that overrides the oldest sequence number entry with the most recent measurement.

This attribute indicates the CIN latency value measured for the session referenced by this entry.

This attribute provides the sysUpTime value for the last time docsRphyCcapCinLatencyPerfVal was updated.

This attribute represents the subject name exactly as it is encoded in the X509 certificate. The organizationName portion of the certificate's subject name must be present. All other fields are optional. Any optional field present must be prepended with (carriage return, U+000D) (line feed, U+000A). Ordering of fields present must conform to the following: organizationName countryName stateOrProvinceName localityName organizationalUnitName organizationalUnitName= commonName

This attribute represents the issuer name exactly as it is encoded in the X509 certificate. The commonName portion of the certificate's issuer name must be present. All other fields are optional. Any optional field present must be prepended with (carriage return, U+000D) (line feed, U+000A). Ordering of fields present must conform to the following: commonName countryName stateOrProvinceName localityName organizationalUnitName organizationalUnitName=

This attribute represents the certificate's serial number, represented as an octet string.

This attribute indicates how the certificate reached the CCAP Core. Other (4) means that it originated from a source not identified above. Enumeration: 'externalDatabase': 3, 'snmp': 1, 'authentInfo': 5, 'compiledIntoCode': 6, 'other': 4, 'configurationFile': 2.

This attribute represents an X509 DER-encoded CCAP Core certificate.

This attribute represents the SHA-1 hash of the CCAP Core certificate.

The compliance statement for RPD management features.

Group of objects implemented in CCAP Cores which represent RPD managed objects derived via the GCP protocol.

Group of objects implemented in CCAP Cores.

Group of objects implemented to support security in CCAP Core.