Adva FSP 3000R7 - Transferring Software to the NCU

Updating the NE Software Release
5 If the node contains legacy modules, update the firmware packages on those
modules.
6 Create a database backup for the new software release in case of an NCU failure.
7 [Optional] If required for security purposes, disable the FTP client, FTP server, or
SSH server.
If you update a protected NCU, the standby NCU will be updated automatically during the
activation of the software release on the active NCU.
Back up the NCU database, as described in “Backing Up the Database” on p.610.
To start the software release update, proceed to “Transferring Software to the NCU” on
p.620.
Transferring Software to the NCU
This procedure describes how to transfer a software release from a file server to the
NCU.
Note
If the software version you wish to update is listed in the Standby
Software Release blade under Node > Software > NCU, the software
is already installed and only needs to be activated.
Requirements
You must be logged on with an ADMINprivilege level account.
Step 1 Select .
Step 2 In the Navigation Tree, select Software > NCU.
Step 3 In the Transfer Software to Standby Area blade, set the Source Location
of the software files to Remote Server.
Step 4 Enter or select:
a) Transfer Protocol.
b) Source IPAddress:
• Default, if the management network is configured to route IP
addresses in the range of the physical IP interfaces.
• System,if the management network is configured to route IP
addresses in the range of the System IP addresses.
c) IPv4/v6 Address of the remote server.
d) User Name and Password to access the remote server following any
case-sensitive rules imposed by the remote server.
e) Directory Path Name on the remote sever, if needed.
Note
If the remote server is a GNE, set Directory Path Name to /cfdisk.
f) File Name for the software configuration file (*.CON file).
620 FSP 3000R7 Maintenance and Troubleshooting Manual - Product Release 16.2 - Document Issue A