Cisco cBR Converged Broadband Routers DOCSIS Software Configuration Guide for Cisco IOS XE 17.18

Configure RPD

To configure RPD using the 100G interface, use the cable rpd node command. This is an example of configuring RPD.


cable rpd node_313
 identifier badb.ad13.419a
 type shelf
 rpd-ds 0 max-carrier 158
 rpd-ds 0 base-power 32
 rpd-ds 1 max-carrier 158
 rpd-ds 1 base-power 34
 core-interface Hu0/1/8
  principal
  rpd-ds 0 downstream-cable 0/0/19 profile 32
  rpd-us 0 upstream-cable 0/0/38 profile 37
  rpd-us 1 upstream-cable 0/0/39 profile 38
 r-dti 6
 rpd-event profile 0
 rpd-55d1-us-event profile 0

Configure RPD Location Attributes Through CLI

Table 1. Feature History
Feature	Release	Description
New RPD location attributes to configure RPD’s description, latitude, and longitude.	Cisco IOS XE Dublin 17.12.1w	You can now configure RPD's description, latitude, and longitude that helps you to track the location attributes of an RPD seamlessly.

You can now configure attributes such as description, latitude, and longitude for an RPD into the cBR8 router using a CLI command. This helps you to track the location attributes of an RPD seamlessly. The RPD location attributes are saved into the database and then sent to RPD.

Note

When you receive the location configuration attributes through SNMP, the configured location attributes are updated, received and saved to the database.

Device Location Description (description)—Allows the RPD to inform the CCAP core about its location. Use the location description command to configure the RPD location description details. The valid range is 1-255. When you configure the description attribute, the RPD stores its value in its nonvolatile configuration. The valid range is 1-255.
Geo Location Latitude (latitude)—Allows the RPD to inform the CCAP core about the latitude portion of its geographic location. Use the location latitude command to configure the RPD location latitude details. The RPD uses 6-digit notation in the format degree, minute, seconds, ±DDMMSS.S. When you configure the latitude attribute, the RPD stores its value in its nonvolatile configuration.

For example: +123254.7.
Geo Location Longitude (longitude)—Allows the RPD to inform the CCAP core about the longitude portion of its geographic location. Use the location longitude command to configure the RPD location longitude details. The RPD uses 7-digit notation in the format degree, minute, seconds, ±DDDMMSS.S. When you configure the longitude attribute, the RPD stores its value in its nonvolatile configuration.

For example: +2340517.1.

When you get the location configuration attributes through SNMP, you must get the same CLI configured values from the database.

The SNMP set command and the CLI configuration is supported for configuring the RPD location values.

Configuring RDP Location Attributes

To configure the RPD location attributes, execute the following commands:


router#cable rpd <rpd-name>
router#location { description | latitude | longitude }

the device location description for RPD indicates the maximum length which is 255 bytes, geo location latitude +000000.0 for RPD indicates the maximum length that is 9 bytes, and geo location longitude +0000000.0 for RPD indicates the maximum length that is 10 bytes.

The following is the sample output of the cable rpd rpd-location command:

router(conf)#cable rpd rpd-location-test
router(conf)#location desc rpd-loc
router(conf)#location latitude +123456.7
router(conf)#location longitude +1234567.8

The following is the sample output of the show cable rpd location command:

router#show cable rpd location
RPD ID                         : f4db.e6cd.d838
Location Description    : RPD_dev3-details
Latitude                       : +999999.7
Longitude                    : +8888888.8

RPD ID                         : f4db.e6cd.d8bc
Location Description    : RPD_dev2-details
Latitude                       : +565656.1
Longitude                    : +3245432.5

RPD ID                         : f4db.e6cd.d8c8
Location Description    : RPD_dev1-details
Latitude                       : +123456.7
Longitude                    : +8978564.1

Verifying the RPD Location Configuration Attributes

The following is the sample output of the show running-config | i location command:


router#show running-config | i location
 location description CBR8
 location latitude +908070.1
 location longitude +1236098.5

Verify the Values Sent to the RPD

To verify the values sent to the RPD, use the show cable rpd gcp-transaction verbose command as shown in the example below:

router#show cable rpd <MAC> <I/F> gcp-transaction verbose


router#show cable rpd gcp-transaction verbose | s  TYPE_DEVICE
{ T = TYPE_DEVICEALIAS(8), L = 0, V = }
{ T = TYPE_DEVICELOCATION(24), L = 40, V = 
{ T = TYPE_DEVICE_LOCATION_DESCRIPTION(1), L = 12, V = CBR8 }
{ T = TYPE_GEO_LOCATION_LATITUDE(2), L = 9, V = +908070.1}
{ T = TYPE_GEO_LOCATION_LOGITUDE(3), L = 10, V = +1236098.5
{ T = TYPE_DEVICEALIAS(8), L = 0, V = }
{ T = TYPE_DEVICELOCATION(24), L = 40, V = 
{ T = TYPE_DEVICE_LOCATION_DESCRIPTION(1), L = 12, V = CBR8 }
{ T = TYPE_GEO_LOCATION_LATITUDE(2), L = 9, V = +908070.1}
{ T = TYPE_GEO_LOCATION_LOGITUDE(3), L = 10, V = +1236098.5
{ T = TYPE_DEVICEALIAS(8), L = 0, V = }

snmp commands

The SNMP get and SNMP walk commands are used to retrieve the CLI configured values.

The following is an example of SNMP walk on the RPD location:

server > snmpwalk -v2c -c private 2.24.1.1 1.3.6.1.4.1.4491.2.1.31.1.1.6
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.1.0.4.159.49.8.37 = ""
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.2.0.4.159.49.8.37 = STRING: "RPD1"
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.3.0.4.159.49.8.37 = STRING: “CBR8"
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.4.0.4.159.49.8.37 = STRING: “+908070.1"
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.5.0.4.159.49.8.37 = STRING: “+1236098.5“

router#scr f86b.d9ff.fd1e location
RPD ID                         : f86b.d9ff.fd1e
Location Description    : CBR8
Latitude                       : +908070.1
Longitude                    : +1236098.5

The following example shows SNMP using the community private using SNMP version 2c:

For Location:

server > snmpget -v2c -c private 2.24.1.1 
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.3.0.4.159.49.8.37
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.3.0.4.159.49.8.37 = STRING: “CBR8"

For Latitude

server > snmpget -v2c -c private 2.24.1.1 
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.4.0.4.159.49.8.37
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.4.0.4.159.49.8.37 = STRING: “+908070.1“

For Longitude

server > snmpget -v2c -c private 2.24.1.1 
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.5.0.4.159.49.8.37
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.5.0.4.159.49.8.37 = STRING: : “+1236098.5“

server > snmpset -v2c -c private 2.32.1.1 
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.3.0.39.144.11.14.20 s "INDIA"
SNMPv2-SMI::enterprises.4491.2.1.31.1.1.6.1.3.0.39.144.11.14.20 = STRING: "INDIA"

The following is the sample output of the do scr location:

router#do scr location
RPD ID                         : 0027.900b.0e14
Location Description           : Valid
Latitude                       : +123456.7
Longitude                      : +1234567.8

The following is the sample output of the show cable rpd <mac> <i/f> gcp-transaction verbose location:

router#show cable rpd <mac> <i/f> gcp-transaction verbose
router#scr
MAC Address     IP Address       I/F       State        Role HA  Auth Name                          
0027.900b.0e14  ---              Hu2/1/8   online       Pri  Act N/A  RPD_dev1                      
0027.900b.0e20  ---              Hu2/1/8   online       Pri  Act N/A  RPD_dev2                      
0027.900b.0e38  ---              Hu2/1/8   online       Pri  Act N/A  RPD_dev3                      

! = PTP clock out of phaselock occurred, ^ = Default password in use

router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
router#cable rpd RPD_dev1
router#location description ARMY
router#location latitude +123456.7
router#location longitude -9080786.1
router#do scr location
RPD ID                         : 0027.900b.0e14
Location Description           : ARMY
Latitude                       : +123456.7
Longitude                      : -9080786.1

RPD ID                         : 0027.900b.0e20
Location Description           : RPD_dev2-info
Latitude                       : +123123.7
Longitude                      : +2344321.8

RPD ID                         : 0027.900b.0e38
Location Description           : NA
Latitude                       : +000000.0
Longitude                      : +0000000.0

Identifying RPD PTP Clock issues Through SNMP Polling

Table 2. Feature History
Feature Name	Release Information	Feature Description
RPD PTP MIB Update	Cisco IOS XE Dublin 17.12.1x	The following MIB table has been added to the SNMP Polling to identify PTP clock state issues: docsRphyPtpRpdClockStatusTable

In this release, if RPDs get stuck in init(clock) state for any reason, we can poll the converged broadband routers(cBR) for the RPD PTP MIB(docsRphyPtpRpdClockStatusClockState/ docsRphyPtpRpdClockStatusComputedPhaseOffset) and identify the RPDs having PTP issue after the generic control protocol(GCP) is up even before RPD is online.

Previously, a user needed to log into the cBR and check show cable rpd command to determine whether RPDs are stuck in init(clock)/ having any PTP issues.

Support for 2x4 RPD

Table 3. Feature History
Feature Name	Release Information	Feature Description
Support for 2x4 RPD	Cisco IOS XE Dublin 17.12.1x	In this feature, RPD can handle up to 4 upstream ports on the cBR8 core side.

The Range of RPD upstream ports are extended from <0-3> and the commands affected by this are as follows:

To configure

rpd-us <0-3> description <decs>

rpd-us <0-3> base-power-rx-level-1_6Mhz <-20 - 40>

rpd-us <0-3> Upstream-Cable <x/0/y> profile <z>

rpd-us <0-3> Upstream-OOB-varpd <1-32> profile <x>

rpd-us <0-3> static-pseudowire <name>

Note

There is no configuration limitation for MD (Mac Domain) and FN (Fiber Node) on cBR8.

New TLVs RPD Reset Control Operation

Table 4. Feature History
Feature Name	Release Information	Feature Description
New TLVs RPD Reset Control Operation	Cisco IOS XE Dublin 17.12.1w	You can now use the new ResetCtrl TLV option to reset the RPDs on the cBR router. The new TLV with the defined type, length, units, values control the RPD reset operations. Performs hardware reset using TLV40.1.1 on: All RPDs Specific RPD using MAC address Specific RPD interface Specific RPD slot

The following table lists the new ResetCtrl defined type, length, units, values (TLVs) to control RPD reset.

Table 5. New TLVs RPD Reset Control Operation
TLV Type	Length	Units	Access	Value
40.1.1	1	–	R/W	An enumerated value with the following defined values: softReset(1)—Resets the software. hardReset(2)—Performs a power-on reset or an equivalent reset. nvReset(3)—Clears the non-volatile configuration and performs a hard reset. factoryReset(4)—Restores the factory configuration and performs a hard reset.

Clearing the RPD Reset Control Operation

You can perform the reset control for all RPDs together, at the slot level, on the interface, using the IP Address for RPD, or for a specific RPD using the MAC address.

For each reset control operation, you can perform the following TLV 40.1.1 operations on the remote PHY device:

Factory configuration reset
Hardware reset
Non-volatile configuration reset
Software reset

Use the following clear commands to clear the RPD Reset Control configurations:

router#clear cable rpd all reset {factory | hard | non-volatile | soft}
router#clear cable rpd slot no reset {factory | hard | non-volatile | soft}
router#clear cable rpd interface reset {factory | hard | non-volatile | soft}
router#clear cable rpd ip address reset {factory | hard | non-volatile | soft}
router#clear cable rpd mac address reset {factory | hard | non-volatile | soft}

To perform the reset control operation for all RPDs together, use the clear cable rpd all reset command as shown in the example below:

Example

router#clear cable rpd all reset {factory | hard | non volatile | soft}

To perform the reset control operation at the slot level, use the clear cable rpd slot no reset command as shown in the example below:

Example

router#clear cable rpd slot 6 reset {factory | hard | non volatile | soft}

To perform the reset control operation on the interface, use the clear cable rpd interface reset command as shown in the example below:

Example

router#clear cable rpd interface Te6/1/5 reset {factory | hard | non volatile | soft}

To perform the reset control operation for the RPD IP address, use the clear cable rpd ip address reset command as shown in the example below:

Example

router#clear cable rpd 30.85.65.150 reset {factory | hard | non volatile | soft}

To perform the reset control operation for a specific RPD using the MAC address, use the clear cable rpd command as shown in the example below:

Example

router#clear cable rpd 0018.48fe.e643 reset {factory | hard | non volatile | soft}

Verifying the RPD Reset Control Operation

Use the following show command to verify the RPD Reset Control configuration:

router#show cable rpd

To verify the RPD ResetCtrl operation, use the show cable rpd command as shown in the example below:

Example

router#show cable rpd
Load for five secs: 8%/1%; one minute: 7%; five minutes: 7%
Time source is NTP, 13:12:23.636 CST Mon Aug 28 2023

MAC Address IP Address I/F State Role HA Auth Name

0018.48fe.e643 30.85.65.150 Te6/1/5 online Pri Act N/A vecima-rpd

1004.9fb1.1300 30.85.65.153 Te6/1/5 online Pri Act N/A ng13-shelf-node2

! = PTP clock out of phaselock occurred, ^ = Default password in use

router#

Single Command to View Consolidated Logs for an RPD

Table 6. Feature History
Feature Name	Release Information	Feature Description
Single Command to View Consolidated Logs for an RPD	Cisco IOS XE 17.18.1y	This feature introduces a CLI command that consolidates logs for a single RPD. This enhancement allows you to retrieve all logs, in both forward and reverse order, for a specific RPD in using a single command. Command Introduced show cable rpd [ `mac-addresss \| ip address \| id \| name` log [reverse]

Information About Viewing Consolidated Logs for an RPD

The show cable rpd [ mac-addresss | ip address | id | name log [reverse] feature is a diagnostic tool designed to simplify the retrieval of Remote PHY Device (RPD) logs.

What:

This feature introduces a new CLI command that consolidates all logs for a single RPD into one output.

How:

By executing a single command in admin exec mode, users can retrieve all logs for a specific RPD in both forward and reverse chronological order. The system accepts various unique identifiers for the RPD, including MAC address, RPD ID, IP address, or RPD name.

Why:

Previously, users were required to either view all RPD logs at once using the show cable rpd log reverse command or examine logs for a single ten-gigabit core at a time using the show cable modem rpd (name) x tex/x/x log reverse command. This enhancement allows for a more efficient, consolidated view of all logs associated with a specific RPD.

This feature provides a streamlined way to troubleshoot RPDs by aggregating logs from all sources associated with a specific device. The system merges these logs and presents them in reverse chronological order (most recent entries first), ensuring that the most relevant information is displayed prominently. Each log entry includes a timestamp, interface or source identifier, log level, and the message content.

Benefits of Viewing Consolidated Logs for an RPD

Efficiency: Consolidates logs for a single RPD into a single command, reducing the need for multiple queries.
Flexibility: Supports multiple input identifiers (MAC, IP, ID, or Name) for referencing an RPD.
Improved Troubleshooting: Enables users to view logs in reverse chronological order, making it easier to identify the most recent events.
Backward Compatibility: The feature does not interfere with existing CLI commands or workflows.

Commands to Verify Consolidated Logs for an RPD

You can verify the feature by executing the command and reviewing the output. The output displays the RPD ID, Interface, Severity, Time, and Log Information. Here are some sample outputs of the commands:

router#show cable rpd 3473.2d78.80a4 log                
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- --------- -----------------------  -----------------------
3473.2d78.80a4   Te2/1/0    DEBUG     2025-07-21 07:21:24.566  RPD 3473.2d78.80a4 Core Te 2/1/0 change Primary STATE from offline to init(auth) (connecting)
3473.2d78.80a4   Te2/1/0    DEBUG     2025-07-21 07:21:24.566  RPD 3473.2d78.80a4 Core Te 2/1/0 change Primary STATE from init(auth) to init(gcp)
3473.2d78.80a4   Te1/1/0    DEBUG     2025-07-21 07:25:13.511  RPD 3473.2d78.80a4 Core Te 1/1/0 change Primary STATE from offline to init(auth) (connecting)
3473.2d78.80a4   Te1/1/0    DEBUG     2025-07-21 07:25:13.511  RPD 3473.2d78.80a4 Core Te 1/1/0 change Primary STATE from init(auth) to init(gcp)
          
router#show cable rpd 3473.2d78.80a4 log reverse
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- --------- -----------------------  -----------------------
3473.2d78.80a4   Te1/1/0    DEBUG     2025-07-30 10:26:27.669  RPD 3473.2d78.80a4 Core Te 1/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.80a4   Te1/1/0    DEBUG     2025-07-30 10:26:25.641  RPD 3473.2d78.80a4 Core Te 1/1/0 change Primary STATE from init(clksync) to init(l2tp)
3473.2d78.80a4   Te2/1/0    DEBUG     2025-07-30 10:12:11.176  RPD 3473.2d78.80a4 Core Te 2/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.80a4   Te2/1/0    DEBUG     2025-07-30 10:12:08.974  RPD 3473.2d78.80a4 Core Te 2/1/0 change Primary STATE from init(clksync) to init(l2tp)

router#show cable rpd 2002::C0A8:CA93 log
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- ------------ -----------------------  -----------------------
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from offline to init(auth) (connecting)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(auth) to init(gcp)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change GCP STATE from offline to nego (IRA+F3)
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-21 07:24:43.081  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from offline to init(auth) (connecting)
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-21 07:24:43.081  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(auth) to init(gcp)

router#show cable rpd 2002::C0A8:CA93 log reverse
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- ------------ -----------------------  -----------------------
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-30 10:25:02.319  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-30 10:25:00.395  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(clksync) to init(l2tp)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:15:11.259  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:15:09.324  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(clksync) to init(l2tp)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:12:08.352  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(gcp) to init(clksync)

router#show cable rpd name RACK7-GREEN-6x12-RPD4 log
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- ------------ -----------------------  ----------------------
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from offline to init(auth) (connecting)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(auth) to init(gcp)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change GCP STATE from offline to nego (IRA+F3)
          
router#show cable rpd name RACK7-GREEN-6x12-RPD4 log reverse 
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- ------------ -----------------------  -----------------------
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-30 10:25:02.319  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-30 10:25:00.395  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(clksync) to init(l2tp)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:15:11.259  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:15:09.324  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(clksync) to init(l2tp)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:12:08.352  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(gcp) to init(clksync)

router#show cable rpd id 3473.2d78.8062 log
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- ------------ -----------------------  -----------------------
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from offline to init(auth) (connecting)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-21 07:21:21.596  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(auth) to init(gcp)
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-21 07:24:43.081  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from offline to init(auth) (connecting)
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-21 07:24:43.081  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(auth) to init(gcp)
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-21 07:24:43.082  RPD 3473.2d78.8062 Core Te 1/1/0 change GCP STATE from offline to nego (IRA+F4)

router#show cable rpd id 3473.2d78.8062 log reverse
RPD ID           I/F        Severity     Time                     LOG INFORMATION
---------------- ---------- ------------ -----------------------  -----------------------
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-30 10:25:02.319  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-30 10:25:00.395  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(clksync) to init(l2tp)
3473.2d78.8062   Te1/1/0    DEBUG        2025-07-30 10:25:00.394  RPD 3473.2d78.8062 Core Te 1/1/0 change Primary STATE from init(gcp) to init(clksync)
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:15:11.259  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(l2tp) to online
3473.2d78.8062   Te2/1/0    DEBUG        2025-07-30 10:15:09.324  RPD 3473.2d78.8062 Core Te 2/1/0 change Primary STATE from init(clksync) to init(l2tp)

Single Command to View Consolidated Logs for an RPD

Table 7. Feature History
Feature Name	Release Information	Feature Description
RPD Uptime Information Enhancement	Cisco IOS XE 17.18.1y	This feature enhances the following RPD commands to get full uptime (like the SNMP output). Command Introduced show cable rpd `mac-addresss \| ip address \| id \| name` uptime

Information About rouRPD Uptime Information Enhancement

This feature introduces updated Command Line Interface (CLI) commands to provide comprehensive Remote PHY Device (RPD) uptime information.

What:

The feature provides a new, user-friendly format for viewing RPD system uptime. Previously, uptime was displayed in a truncated format (e.g., "8h37m"). The updated commands provide the full uptime in the standard SNMP format (e.g., "Timeticks: (37673001) 4 days, 8:38:00.00").

How:

You can now use the show cable rpd uptime command and its variants to retrieve this detailed information for all RPDs or a specific RPD identified by its MAC address, IP address, ID, or name.

Why:

The previous truncated format lacked the granularity required for precise troubleshooting and monitoring. By adopting the SNMP-style format, administrators can easily correlate RPD uptime with other system logs and SNMP-based monitoring tools, improving operational visibility.

Benefits of rouRPD Uptime Information Enhancement

Improved Clarity: Provides full, non-truncated uptime information in a standard SNMP-compatible format.
Operational Consistency: Aligns CLI output with SNMP MIB data, simplifying the correlation of troubleshooting data.
Flexible Retrieval: Allows for querying uptime across the entire system or for specific RPDs using various identifiers (MAC, IP, ID, or Name).
Backward Compatibility: The new commands are added alongside existing ones, ensuring that legacy workflows remain functional.

Restrictions for RPD Uptime Information Enhancement

The output of these commands is supported only on the Supervisor (SUP) and is not supported on the Cable Line Card (CLC).
Commands must be executed in PRIV_ROOT mode (Privilege Level 15).

Obtaining SysUptime OID in SNMP MIB Using SNMP Query Command

MIB file location: /polaris/vob/ios/sys/MIBS/DOCS-RPHY-MIB.my
MIB OID: 2.39.1.1 1.3.6.1.4.1.4491.2.1.30.1.1.1.1.2

Definition in ASN syntax:
docsRphyRpdDevInfoSysUpTime OBJECT-TYPE
    SYNTAX      TimeStamp
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "This attribute is the time (in hundredths of a second)
         since the RPD was last re-initialized. This value is
         reported by the RPD."
    ::= { docsRphyRpdDevInfoEntry 2 }

lwr-lnx-util-1:~ > snmpwalk -v2c -c public 2.39.1.1 1.3.6.1.4.1.4491.2.1.30.1.1.1.1.2
SNMPv2-SMI::enterprises.4491.2.1.30.1.1.1.1.2.244.219.230.20.0.16 = Timeticks: (8773496) 1 day, 0:22:14.96
SNMPv2-SMI::enterprises.4491.2.1.30.1.1.1.1.2.244.219.230.20.0.22 = Timeticks: (8774012) 1 day, 0:22:20.12
SNMPv2-SMI::enterprises.4491.2.1.30.1.1.1.1.2.244.219.230.20.0.46 = Timeticks: (8773809) 1 day, 0:22:18.09
lwr-lnx-util-1:~ >

Commands to Verify RPD Uptime Information Enhancement

You can verify the feature by executing the command and reviewing the output. The output displays the RPD ID, Interface, Severity, Time, and Log Information. Here are some sample outputs of the commands:

router#show cable rpd info
RPD ID                : f4db.e614.0010
RPD Name              : RPD_dev1
SysUpTime             : Timeticks:(738052) 02:03:00.52
NumCrashFilesAvail    : 3
PrincipalCoreStatus   : 7

RPD ID                : f4db.e614.0016
RPD Name              : RPD_dev3
SysUpTime             : Timeticks:(737494) 02:02:54.94
NumCrashFilesAvail    : 0
PrincipalCoreStatus   : 7

RPD ID                : f4db.e614.002e
RPD Name              : RPD_dev2
SysUpTime             : Timeticks:(737987) 02:02:59.87
NumCrashFilesAvail    : 0
PrincipalCoreStatus   : 7

router#show cable rpd id f4db.e614.0010 info
RPD ID                : f4db.e614.0010
RPD Name              : RPD_dev1
SysUpTime             : Timeticks:(739752) 02:03:17.52
NumCrashFilesAvail    : 3
PrincipalCoreStatus   : 7

router#show cable rpd id f4db.e614.002e info
RPD ID                : f4db.e614.002e
RPD Name              : RPD_dev2
SysUpTime             : Timeticks:(741987) 02:03:39.87
NumCrashFilesAvail    : 0
PrincipalCoreStatus   : 7

router#show cable rpd id f4db.e614.0016 info
RPD ID                : f4db.e614.0016
RPD Name              : RPD_dev3
SysUpTime             : Timeticks:(742893) 02:03:48.93
NumCrashFilesAvail    : 0
PrincipalCoreStatus   : 7

router#show cable rpd name RPD_dev1 info    
RPD ID                : f4db.e614.0010
RPD Name              : RPD_dev1
SysUpTime             : Timeticks:(745853) 02:04:18.53
NumCrashFilesAvail    : 3
PrincipalCoreStatus   : 7

router#show cable rpd name RPD_dev2 info
RPD ID                : f4db.e614.002e
RPD Name              : RPD_dev2
SysUpTime             : Timeticks:(746687) 02:04:26.87
NumCrashFilesAvail    : 0
PrincipalCoreStatus   : 7

router#show cable rpd name RPD_dev3 info
RPD ID                : f4db.e614.0016
RPD Name              : RPD_dev3
SysUpTime             : Timeticks:(746793) 02:04:27.93
NumCrashFilesAvail    : 0
PrincipalCoreStatus   : 7

router#show cable rpd uptime                
RPD ID     : f4db.e614.0010
RPD Name   : RPD_dev1
SysUpTime  : Timeticks:(749353) 02:04:53.53

RPD ID     : f4db.e614.0016
RPD Name   : RPD_dev3
SysUpTime  : Timeticks:(748793) 02:04:47.93

RPD ID     : f4db.e614.002e
RPD Name   : RPD_dev2
SysUpTime  : Timeticks:(749287) 02:04:52.87

router#show cable rpd name RPD_dev1 uptime    
RPD ID     : f4db.e614.0010
RPD Name   : RPD_dev1
SysUpTime  : Timeticks:(757853) 02:06:18.53

router#show cable rpd name RPD_dev2 uptime
RPD ID     : f4db.e614.002e
RPD Name   : RPD_dev2
SysUpTime  : Timeticks:(758787) 02:06:27.87

router#show cable rpd name RPD_dev3 uptime
RPD ID     : f4db.e614.0016
RPD Name   : RPD_dev3
SysUpTime  : Timeticks:(759293) 02:06:32.93

Bias-Free Language

Book Title

RPD Configuration

Results

Chapter: RPD Configuration

RPD Configuration

Configure RPD

Configure RPD Location Attributes Through CLI

Identifying RPD PTP Clock issues Through SNMP Polling

Support for 2x4 RPD

New TLVs RPD Reset Control Operation

Clearing the RPD Reset Control Operation

Verifying the RPD Reset Control Operation

Single Command to View Consolidated Logs for an RPD

Information About Viewing Consolidated Logs for an RPD

Benefits of Viewing Consolidated Logs for an RPD

Commands to Verify Consolidated Logs for an RPD

Single Command to View Consolidated Logs for an RPD

Information About rouRPD Uptime Information Enhancement

Benefits of rouRPD Uptime Information Enhancement

Restrictions for RPD Uptime Information Enhancement

Obtaining SysUptime OID in SNMP MIB Using SNMP Query Command

Commands to Verify RPD Uptime Information Enhancement

Was this Document Helpful?

Contact Cisco