Archiving RPD Logs

Your software release may not support all the features that are documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. The Feature Information Table at the end of this document provides information about the documented features and lists the releases in which each feature is supported.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http://www.cisco.com/ is not required.

Hardware Compatibility Matrix for Cisco Remote PHY Device


Note
Unless otherwise specified, the hardware components introduced in a given Cisco Remote PHY Device Software Release are supported in all subsequent releases.
Table 1. Hardware Compatibility Matrix for the Cisco Remote PHY Device

Cisco HFC Platform

Remote PHY Device

Cisco GS7000 Super High Output Node

Cisco 1x2 / Compact Shelf RPD Software 2.1 and Later Releases

Cisco GS7000 Super High Output Intelligent Node (iNode)

Cisco 1x2 / Compact Shelf RPD Software 4.1 and Later Releases

Cisco Intelligent Remote PHY Device 1x2

  • PID—iRPD-1X2=

  • PID—iRPD-1X2-PKEY=

Note
The -PKEY suffix in the PID indicates units that enable the SCTE-55-2 Out-of-Band protocol support.

Information About Archiving Logs

You can use SCP and TFTP to archive logs to the server.

When an RPD SSH session is closed during an RPD logging archive process, the RPD logging temp file is retained in the RPD file system. In this release, only the latest temp file is retained. The legacy temp files are removed.

Archiving Logs Using SCP or TFTP


Note

Use the absolute path for the save_path parameter.

To archive logs, use the logging command.

To use TFTP to transfer files, use the logging [provision-archive|1588-archive|corefile] tftp <server_ip> <save_path> command.

To use SCP to transfer files, use the logging [provision-archive|1588-archive|corefile] scp <server_ip> <user> <save_path> command.

To archive logs created during RPD provisioning using scp, use the logging provision-archive scp <server_ip> <user> <save_path> command. This is an example of how to archive logs created during RPD provisioning using scp.


Note

  • Use provision-archive to archive logs created during RPD provisioning.

  • Use 1588-archive to archive PTP logs.

  • Use corefile to archieve logs created duing system crashes.

  • <user> is the username of the SCP or TFTP server account to which files are transferred.

  • <save_path> is the absolute or relative path of the folder in the SCP or TFTP server. You must have write permission to access the folder. Make sure that the folder has sufficient space.

  • <server_ip> can be IPv4 or IPv6 address. The server IP address type must be the same as the RPD IP address.

  • For SCP file transfer, type the password of your server account when prompted. For TFTP file transfer, password is not required.

  • RPD should be able to successfully ping the SCP or TFTP server. If the ping is unsuccessful, files are not archived.

 

R-PHY#logging provision-archive scp 198.51.100.1 <user> <save_path>
Wait for archiving logs
Collect tech-support info...
[  370.528323] RPD_CPLD: finish watchdog configuration 2
[  370.550344] RPD_CPLD: finish watchdog configuration 3

Wait for upload archive to server. It would take 3 minutes or more.
RPD logs will be saved in <user>@<server_ip>:/<save_path>/RPD_PROV_10049fc20200_LOG_2018-08-20_00_12_22_419798.tar.gz
 
Host '<server_ip>' is not in the trusted hosts file.
(ssh-rsa fingerprint md5 b6:bb:d4:20:92:47:bb:29:d7:2c:5d:47:7a:a5:c6:8d)
Do you want to continue connecting? (y/n) y
<user>@<server_ip>'s password:
RPD_PROV_10049fc20200_LOG_2018-08-20_00_12_22 100%   61MB   1.9MB/s   00:32   
[Done]

To archive PTP logs using scp, use the logging 1588-archive scp <server_ip> <user> <save_path> command. This is an example of how to archive PTP logs using scp. 


R-PHY#logging 1588-archive scp 198.51.100.1  <user> /tmp
 
wait for archiving 1588 logs
Wait for upload archive to server. It would take 3 minutes or more.
RPD logs are saved in user@198.51.100.1:/tmp/RPD_1588_0027900a0cf8_LOG_1977-01-08_21_26_05_222552.tar.gz
 
Host '198.51.100.1' is not in the trusted hosts file.
(ssh-rsa fingerprint md5 1d:9d:69:0c:17:1e:66:03:11:7e:ff:a3:c1:55:b1:a7)
Do you want to continue connecting? (y/n) user@198.51.100.1's password:
RPD_1588_0027900a0cf8_LOG_1977-01-08_21_26_05 100%   29     0.0KB/s   00:00
[Done]

To archive logs created duing system crashes using scp, use the logging corefile scp <server_ip> <user> <save_path> command. This is an example of how to archive logs created during system crashes using scp. 

R-PHY#logging corefile scp 198.51.100.1  <user> /tmp
 
wait for archiving corefile
Wait for upload archive to server. It would take 3 minutes or more.
RPD logs are saved in user@198.51.100.1:/tmp/RPD_COREFILE_0027900a0cf8_LOG_1977-01-08_21_27_59_522646.tar.gz
jianyzha@198.51.100.1's password:
RPD_COREFILE_0027900a0cf8_LOG_1977-01-08_21_2 100% 9126KB   8.9MB/s   00:01
[Done]

To archive logs created during RPD provisioning using tftp, use the logging provision-archive tftp <server_ip> <save_path> command. This is an example of how to archive logs created during RPD provisioning using tftp. 


R-PHY#logging provision-archive tftp 198.51.100.1 .
 
wait for archiving logs
Collect tech-support info...
 
wait for upload archive to server
RPD provision logs are saved in 198.51.100.1:$TFTP_DIR/./RPD_0027900a0cf8_LOG_1977-01-08_18_20_10_509660.tar.gz
[Done]

To archive PTP logs using tftp, use the logging 1588-archive tftp <server_ip> <save_path> command. This is an example of how to archive PTP logs using tftp. 

R-PHY#logging 1588-archive tftp 198.51.100.1 .
 
wait for archiving 1588 logs
Wait for upload archive to server. It would take 3 minutes or more.
RPD logs are saved in 198.51.100.1:$TFTP_DIR/./RPD_1588_0027900a0cf8_LOG_1977-01-08_21_25_26_352484.tar.gz
[Done]

To archive logs created duing system crashes using tftp, use the logging corefile tftp <server_ip> <save_path> command. This is an example of how to archive logs created during system crashes using tftp. 


R-PHY#logging corefile tftp 198.51.100.1 .
 
wait for archiving corefile
Wait for upload archive to server. It would take 3 minutes or more.
RPD logs are saved in 198.51.100.1:$TFTP_DIR/./RPD_COREFILE_0027900a0cf8_LOG_1977-01-08_21_27_37_782555.tar.gz
[Done]

Feature Information for Archiving Logs

Use Cisco Feature Navigator to find information about the platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to the https://cfnng.cisco.com/ link. An account on the Cisco.com page is not required.


Note

The following table lists the software release in which a given feature is introduced. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 2. Feature Information for Archiving Logs

Feature Name

Releases

Feature Information

Archiving Logs

Cisco 1x2 RPD Software 6.1

This feature was introduced on the Cisco Remote PHY Device.