1. Download the firmware to ROADM degree 1 using one of these methods:
a. Using the swupgrade download to directly download the firmware
swupgrade download sftp://ross:********@<server>:/home/ross/dcp-release-8.1.7.tarb. SCP the firmware using the sftpuser then doing an internal download (This is the method I've found to work best)
SCP the firmware files from your machine into the /swupgrade/ directory using the sftpuser user
scp -P 122 /Users/ross/Desktop/R8.1.7_A/dcp-release-8.1.7.tar sftpuser@172.18.2.160:/swupgrade/Now that the files are on the ROADM, download them from the swupgrade directory so the swupgrade manager can use them
swupgrade download file:/swupgrade/dcp-release-8.1.7.tar2. Apply the new firmware. Running this command from degree 1 will also apply the firmware to any other degrees on the same node.
swupgrade set boot dcp-release-8.1.73. Reboot all degrees. This should NOT be service affecting.
reboot1. SSH into the shell controller
2. Navigate to /container/
/container/3. Use the print command to show the container's status. It should show as running
print4. Stop and remove the container
stop 0
remove 05. Use curl to transfer the new shelf controller image to the controller
curl -T /Users/ross/Desktop/R8.1.7_A/dcp-shelf-controller-release-8.1.7.tar ftp://172.18.2.160/install-tmp/ --user adminYou should now see the image on the controller by running
/file/print6. Add a new container
add envlist=dcp_envs file=install-tmp/dcp-shelf-controller-release-8.1.7.tar interface=veth1 logging=yes start-on-boot=yes mounts=persistent,sslUse print to check on the status of the container. It will say extracting for a few minutes then change to stopped once complete. The container CANNOT be started when in the extracting status!
7. Start the new container
start 08. From one of the DCP-R, verify the controller shows the new version. It may take several minutes for the devices to sync up again.
show version9. Reboot the shelf controller (I've been told before, by SmartOptics Engineering, that the whole shelf does NOT need to be rebooted. This makes sense since it's just a container. But is against the official documentation)
/system/reboot