To upgrade the vCPAA software using a CLI

WARNING

Equipment Damage

Do not add, modify, or delete the content of the last stable version of the boot files. They must be preserved in case they are required as a secondary image.

Before you begin

The following procedure describes Nokia’s recommendations for using a CLI to install or upgrade the software on a vCPAA. Variations on this procedure are possible, depending on your system and requirements.

Place the installation or upgrade files in a location that is accessible using FTP or SCP.

For information about 7701 CPAA software files, see Table 2-1, 7701 CPAA files.

Steps


1	Back up the existing configuration files for the CPAA that you are planning to upgrade. Ensure that the following files are backed up: bof.cfg CPAA configuration file See “To create a 7701 CPAA backup policy” in the NSP NFM-P Control Plane Assurance Manager User Guide.
2	Ensure that the serial port is connected to a terminal server, then open a Telnet session on that connection.
3	Create a directory on the CPAA for the upgrade files. Use the following commands: `A:CPAA_name# file↵` `A:CPAA_name>file cf3:\ # md new_load↵` `A:CPAA_name>file cf3:\ # cd new_load↵` `A:CPAA_name# exit↵`
4	Use FTP or SCP to copy the new boot.tim and both.tim files to the directory created in Step 3. If you use FTP, you must enable FTP on the CPAA. Use the following commands: `A:CPAA_name# configure system security↵` `A:CPAA_name>config>system>security# ftp-server↵` `A:CPAA_name>config>system>security# user user_name↵` `A:CPAA_name>config>system>security>user$ password password↵` `A:CPAA_name>config>system>security>user$ access ftp↵` `A:CPAA_nameconfig>system>security>user$ exit all↵` `A:CPAA_name# admin save↵` For FTP, use binary mode.
5	Confirm that the file transfer is successful.
6	Modify the bof.cfg to designate the primary and secondary image locations. Use the existing primary-image path as the secondary-image path. Use the new_load path created in Step 3 as the primary-image path. Use the following commands: `A:CPAA_name# bof↵` `A:CPAA_name>bof# secondary-image cf1:\previous primary-image path\both.tim↵` `A:CPAA_name>bof# primary-image cf1:\new_load\both.tim↵` `A:CPAA_name>bof# save↵` You can view the current bof.cfg configuration by using the `show bof` command.
7	Reboot the appliance, then stop the boot process to configure the boot parameters by clicking on any key when the following message appears: `Press any key to stop auto-boot...↵` This may take several minutes.
8	Type p (for print) to view the content of the NVRAM.DAT file. You can enter ? to view other command options and information.
9	Type c (change) to change the content of the NVRAM.DAT file. Configure the parameters: `boot device : ata=0,2 ↵` `unit number : 0 ↵` `processor number : 0 ↵` `host name : host_name↵` `file name : boot_load_pathname/boot.tim↵` `inet on ethernet (e) : management_port_IP_address:ffffffff↵` `inet on backplane (b): ftp_server_IP_address↵` `host inet (h) : ftp_server_IP_address↵` `gateway inet (g) : gateway_IP_address↵` `user (u) : ftp_username↵` `ftp password (pw) : ftp_password↵` `flags (f) : 0x0↵` `target name (tn) : CPAA_name↵` Some of the NVRAM.DAT parameters are optional, depending on the option configured for `boot device`. For example, the inet on backplane, host inet, gateway inet, user, and ftp password parameters apply when you boot from the network, when the boot device is fei. However, the inet on ethernet (e) parameter is not optional. See Table 2-1, 7701 CPAA files. The following is a sample configuration: `boot device : ata=0,2↵` `unit number : 0↵` `processor number : 0↵` `host name : ↵` `file name : cf3:\new_load\boot.tim↵` `inet on ethernet (e) : management_port_IP_address:ffffffff↵` `inet on backplane (b): 0.0.0.0↵` `host inet (h) : 0.0.0.0↵` `gateway inet (g) : 0.0.0.0↵` `user (u) : ↵` `ftp password (pw) : ↵` `flags (f) : 0x0↵` `target name (tn) : CPAA_name↵`
10	Enter @ to save the changes and continue the boot process.
11	Wait for the system to reboot. The system is fully rebooted when the login prompt appears. Note: The contents of the NVRAM.DAT file can be changed during a reboot, as required. See Table 2-1, 7701 CPAA files for a description of the parameters.
12	Verify that the upgrade was successful by using the `show version` command. End of steps

Use subject to agreed restrictions on disclosure and use.