MXK Firmware Update Procedure

Our MXK Image Filenames;

MXK 819 (non 10G)
mxup8g.bin
mxup8graw.bin
mxlc48aadslbond.bin
mxk819_http.tar
MXK819 (10G)
mxkup2tg8gtop.bin
mxkup2tg8gtopraw.bin
mxlc48aadslbond.bin
mxk819_http.tar
MXK319 (non 10G)
mxup8g.bin
mxup8grwa.bin
mxlc48aadslbond.bin
mxk319_http.tar

Note: infotbl conversion

IMPORTANT!
Please read this note. Failure to observe the following information and correct any anomalies can result in
a service impacting situation.
On an upgrade from releases prior to2.5, the system performs a data conversion that improves data
storage efficiency and access time.
In release 2.5 Zhone is introducing a new version of the infotbl database that improves performance and
reduces memory consumption. When upgrading from 2.4 to 2.5, infotbl.v8will be converted.
The new database is written to a file named infotbl.v9(from .v8). In the process of the conversion a
temporary copy of the .v9is created, as.v9.tmp, until the conversion is complete.
At the end of the upgrade there will be the following database files on the flash:
infotbl.v9: The new converted database
infotbl.v9.old: The backup version of the new database
infotbl.v8.old: a backup copy of the database prior to conversion
A temporary copy of infotbl.v9.tmp will grow as large as infotbl.v8was before conversion, and then be
renamed. The conversion requires that the flash file system must have free disk space to store 3 times the
current infotbl.v8. Use the dir command and compute the open space required and compare it with the
open space available.

Failure to have this free space will result in a failed upgrade and a truck roll.
After a successful upgrade the infotbl.v8.old should be removed.
When this process is complete the system will initiate an automatic reboot to reclaim unused database
memory. This second boot will only happen once when converting from infotbl.v8 to infotbl.v9.
Subsequent reboots are not affected.
Step 1:
Back up the system configuration locally on the MXK or to the network
before upgrading or downgrading the software.
Zhone recommends that the files are backed up locally to ensure access to
the files.
Back up the system configuration locally to flash memory on the MXK.
a Create a backup directory on the /card1 directory, in this case backup.
zSH> cd /card1
zSH> mkdir backup

b Back up the system configuration to a file named restore with the

dump command to create a database system configuration file.
zSH> cd /card1
zSH> dump file backup/restore

This is the file used to restore the system configuration. The restore
file can be validated using the restore validate <filename>
command.
Optional
If necessary, back up the system configuration to the network.
a Create the destination directory on the TFTP server and make it
writable.
b Back up the system configuration to the TFTP server by entering
dump network with the IP address of the server and the filename to
create a database configuration file.
In this case, 192.168.8.21 mxk.cfg:
zSH> dump network 192.168.8.21 mxk.cfg

Step 2:
Back up the current version of the software files locally on the MXK.
a Create a directory on the MXK for the backup from the /card1
directory.
zSH> cd /card1
zSH> mkdir backup2.0

b Back up the card image .bin files, including the raw.bin file, and the
.tar file for the WebUI into the backup directory. For example:
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>

copy
copy
copy
copy
copy
copy
copy
copy
copy
copy

mxup2tg8g.bin backup2.0/mxup2tg8g.bin
mxup2tg8graw.bin backup2.0/mxup2tg8graw.bin
mxlc48adsl2p.bin backup2.0/mxlc48adsl2p.bin
mxlcgp.bin backup2.0/mxlcgp.bin
mxlc20ae.bin backup2.0/mxlc20ae.bin
mxlc8gp.bin backup2.0/mxlc8gp.bin
mxlc24vdsl2.bin backup2.0/mxlc24vdsl2.bin
tacitmring.bin backup2.0/tacitmring.bin
mxlc20ae1s.bin backup2.0/mxlc20ae1s.bin
mxk823_http.tar backup2.0/mxk823_http.tar

Optional

If necessary, back up the current software files remotely to a TFTP server.

a Create a writable destination directory on the TFTP server for the
software files to reside.
b Upload the card image .bin files, including the raw.bin file, and the
.tar file for the WebUI into a directory on the TFTP server. For
example:
zSH> file upload
zSH> file upload
mxup2tg8graw.bin
zSH> file upload
mxlc48adsl2p.bin
zSH> file upload
zSH> file upload
zSH> file upload
zSH> file upload
zSH> file upload
zSH> file upload
zSH> file upload

192.168.8.21 mxup2tg8g.bin backup2.0/mxup2tg8g.bin

192.168.8.21 mxup2tg8graw.bin backup2.0/
192.168.8.21 mxlc48adsl2p.bin backup2.0/
192.168.8.21
192.168.8.21
192.168.8.21
192.168.8.21
192.168.8.21
192.168.8.21
192.168.8.21

mxlcgp.bin backup2.0/mxlcgp.bin
mxlc20ae.bin backup2.0/mxlc20ae.bin
mxlc8gp.bin backup2.0/mxlc8gp.bin
mxlc24vdsl2.bin backup2.0/mxlc24vdsl2.bin
tacitmring.bin backup2.0/tacitmring.bin
mxlc20ae1s.bin backup2.0/mxlc20ae1s.bin
mxk823_http.tar backup2.0/mxk823_http.tar

Step 3

Download the new software files to the card1 directory.

Use the image download command to download the software.
zSH>
zSH>
zSH>
zSH>
zSH>

cd /card1
image download 192.168.8.21 mxup8g.bin
image download 192.168.8.21 mxup8graw.bin
image download 192.168.8.21 mxlc48aadslbond.bin
file download 192.168.8.21 mxk819_http.tar

Step4

Initialize the flash card's boot partition with the new image on both
primary and standby uplink card (if a standby uplink is present) with the
uplink cards raw file.
Non-redundant uplink card
Enter the following image flash command for a non-redundant
uplink card:
zSH> image flash mxup8graw.bin 1

Step 5

Load the new software by entering systemreboot to reboot the system.

zSH> systemreboot

The system reboots with the new version of the software and may take
several minutes to complete. The systemreboot command does not affect
the existing system configuration.

OH SHIT THERES A PROBLEM!!!!!!

After completing a software upgrade, follow this step only if there is a
problem with the system configuration database that requires the entire
system configuration to be restored.
Restore Previous Configuration
When necessary, restore a previously saved system configuration from a
backup file locally on the MXK.
a Copy the database configuration file from the backup directory to /
card1/onreboot/restore.
zSH> cd /card1
zSH> copy backup/restore /card1/onreboot/restore

b Activate the saved system database configuration file with the

set2default command.
Note: Use the set2default command only when restoring a
system configuration and not when you are only upgrading,
downgrading, or restoring software.
zSH> set2default

The set2default command looks in the card1/onreboot directory for

the file restore and restores the database located in the restore file.
The set2default command replaces all of the system configuration
information and could take some time to complete.
Restore Previous Configuration (Network location)
When necessary, restore a previously saved system configuration from a
TFTP server on the network to the MXK.
a Restore the configuration that was backed up using the file download
command.
To restore the saved system configuration, the path name on the MXK
must be card1/onreboot and the file containing the system
configuration information must be named restore.
zSH> cd /card1
zSH> file download 192.168.8.21 mxk.cfg card1/onreboot/restore

This example shows that the mxk.cfg file on the TFTP server is copied
into the file named restore in the card1/onreboot directory on the
MXK.
b Activate the saved system configuration with the set2default
command.
zSH> set2default

Note: Use the set2default command only when restoring a

system configuration and not when you are only upgrading,
downgrading, or restoring software files.
The set2default command looks in the card1/onreboot directory for
the file restore and restores the database located in the restore file.
The set2default command replaces all of the system configuration
information and could take some time to complete.
Restore Previous Version of Software
Restore a previous version of the software when necessary.
Restore the locally backed up software files
a Change directory to the card1 directory.
zSH> cd /card1

b Use the copy command to restore the software by copying the .bin
files from the backup directory to /card1.
zSH> copy backup2.0/mxup2tg8g.bin mxup2tg8g.bin

zSH>
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>
zSH>

copy
copy
copy
copy
copy
copy
copy
copy
copy

backup2.0/mxup2tg8graw.bin mxup2tg8graw.bin
backup2.0/mxlc48adsl2p.bin mxlc48adsl2p.bin
backup2.0/mxlcgp.bin mxlcgp.bin
backup2.0/mxlc20ae.bin mxlc20ae.bin
backup2.0/mxlc8gp.bin mxlc8gp.bin
backup2.0/mxlc24vdsl2.bin mxlc24vdsl2.bin
backup2.0/tacitmring.bin tacitmring.bin
backup2.0/mxlc20ae1s.bin mxlc20ae1s.bin
backup2.0/mxk823_http.tar mxk823_http.tar

c Initialize the flash card's boot partition with the image of the restored
raw.bin file on both primary and standby uplink card (if a standby
uplink is present).
Non-redundant uplink card
Enter the following image flash command for a non-redundant
uplink card:
zSH> image flash mxup2tg8graw.bin 1
WARNING: This operation will overwrite the boot
partition of the ACTIVE flash disk in port 1.
Continue? (yes or no) [no] yes
Image flash successful

Caution: After entering the image flash command, the system

must return the Image flash successful message.
If this message does not return, the flash operation did not
complete and the uplink will be unusable until the uplink is
properly flashed.
d Load the new software by entering systemreboot.
zSH> systemreboot

The system reboots with the new version of the software and may
take several minutes to complete. The systemreboot command does
not affect the existing system configuration.