GDM G30FP031 05 0A Release Upgrade Procedure

Groove™ G30
FP3.1.0
Release Upgrade Procedure
Issue: A Issue date: Aug 2018
GDM-G30FP031-05-0A
Coriant is continually striving to reduce the adverse environmental

effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner,
safer environment. Please recycle product packaging and follow the
recommendations for power use and proper disposal of our products
and their components.
G30 FP3.1.0 Release Upgrade Procedure
The information in this document is subject to change without notice and describes only the product
defined in the introduction of this documentation. This documentation is intended for the use of
Coriant customers only for the purposes of the agreement under which the document is submitted,
and no part of it may be used, reproduced, modified or transmitted in any form or means without the
prior written permission of Coriant. The documentation has been prepared to be used by professional
and properly trained personnel, and the customer assumes full responsibility when using it. Coriant
welcomes customer comments as part of the process of continuous development and improvement of
the documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given "as is" and all liability arising
in connection with such hardware or software products shall be defined conclusively and finally in a
separate agreement between Coriant and the customer. However, Coriant has made all reasonable
efforts to ensure that the instructions contained in the document are adequate and free of material
errors and omissions. Coriant will, if deemed necessary by Coriant, explain issues which may not be
covered by the document. Coriant will correct errors in this documentation as soon as possible.
IN NO EVENT WILL CORIANT BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR
ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL
OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and other
intellectual property rights according to the applicable laws. Other product names mentioned in this
document may be trademarks of their respective owners, and they are mentioned for identification
purposes only.
Copyright © Coriant 2018. All rights reserved.
2/30 © Coriant
Table of Contents
Table of Contents .................................................................................................................. 3
1 Purpose .......................................................................................................... 6
2 Overview ......................................................................................................... 7
2.1 Upgrade Path .................................................................................................. 7
2.2 Service interruption ......................................................................................... 7
2.3 Management interruption ................................................................................ 8
3 Preparations.................................................................................................... 9
3.1 Material requirements ..................................................................................... 9
3.2 Hardware and software Check ........................................................................ 9
3.2.1 Hardware version check .................................................................................. 9
3.2.2 Software version check ................................................................................. 12
3.3 Alarm Management ....................................................................................... 12
3.4 NE Database Backup .................................................................................... 12
3.5 Clear NE Sessions ........................................................................................ 13
4 TNMS Upgrade ............................................................................................. 14
5 SW Downloading Instructions ....................................................................... 15

5.1 New NE Software .......................................................................................... 15
5.2 NE Software Download ................................................................................. 15
5.3 NE Software Check ....................................................................................... 16
6 Release delivery upgrade instructions ........................................................... 17

6.1 Software Switching........................................................................................ 17
6.2 Reboot .......................................................................................................... 17
6.2.1 Cold reboot cards .......................................................................................... 18
6.2.2 Cold reboot the NE........................................................................................ 18
6.2.3 Warm reboot the NE with FPGA-Upgrade ..................................................... 19
7 Upgrade via Groove Web GUI....................................................................... 20

7.1 Software version check ................................................................................. 20
7.2 NE Database Backup .................................................................................... 20
7.3 NE Software Download ................................................................................. 21
7.4 NE Software Check ....................................................................................... 22
© Coriant 3/30
7.5 Software Switching........................................................................................ 22

7.6 Reboot .......................................................................................................... 23
7.6.1 Cold Reboot cards ........................................................................................ 23
7.6.2 Cold reboot NE ............................................................................................. 24
7.6.3 Warm reboot NE with FPGA-upgrade ........................................................... 24
8 Checking of the package consistency ........................................................... 26

8.1 Alarm verification .......................................................................................... 26
8.2 NE Software Version verification ................................................................... 26
8.3 Re-connect NE.............................................................................................. 28
9 Fallback ........................................................................................................ 29
9.1 Switch to previous version............................................................................. 29
4/30 © Coriant
Contact:
Contact your local Coriant support team.
Summary of changes:
Date Version Summary of changes

2018-08-01 1 First version
© Coriant 5/30
1 Purpose
This document provides detailed guideline to carry out software upgrade of G30
from FP2.1.1 or FP3.0.3 to FP3.1.0.
6/30 © Coriant
2 Overview
This document instructs the steps for upgrading the Node software from FP2.1.1
or FP3.0.3 to FP3.1.0, including the available roll back options.
All the upgrade steps for FP2.1.1 are the same as FP3.0.3.
2.1 Upgrade Path

The following upgrade path is officially supported.
WARNING
! FP1.0.2/FP1.1.1does not supported to upgrade to FP3.1.0 directly. It is
mandatory to upgrade to FP1.1.2 firstly, upgrade to FP3.0.3 secondly.
FP1.1.2 /FP2.0.1/FP2.1.0 does not supported to upgrade to FP3.1.0 directly. It
is mandatory to upgrade to FP2.1.1 firstly.
Original Version Target Version

FP2.1.1
FP3.1.0
FP3.0.3
Table 2.1-1 Upgrade Path
2.2 Service interruption

During the upgrade from FP2.1.1 and FP3.0.3 to FP3.1.0, NE will be cold rebooted
manually once or each card will be cold rebooted separately once.
Cold reboot will impact the traffic.
In order to minimize the impact of traffic on NE, card cold reboot is recommended.
Reboot request cards as shown below
Upgrade path NE Card
Cold Reboot for each
None
card
FP2.1.1 -> FP3.1.0
Cold Reboot None
Warm Reboot with Cold Reboot for

FP3.0.3 -> FP3.1.0
FPGA-Upgrade CHM1G card
Table 2.2-1 Reboot Information
For card cold reboot:
© Coriant 7/30
The traffic on card will be interrupted up to 15 minutes in the worst case during card
rebooting.
For NE cold reboot:

The traffic on the NE will be interrupted for no more than 20 minutes in the worst
case. The NE will be offline up to 10 minutes in the worst case during NE rebooting.
For OCC2 card (with three subcards) cold reboot:

The traffic on the NE will be interrupted up to 45 minutes in the worst case during
upgrade if the firmware of these three subcards need upgraded.
2.3 Management interruption

For card reboot:
During the upgrade, the card will be offline for maximum 15 minutes, the NE is always
online, except GCC was configured in the reboot card without any redundancy.
For NE reboot:
During the upgrade, the NE will be un-reachable for maximum 10 minutes.
8/30 © Coriant
3 Preparations
3.1 Material requirements
Before upgrade, following materials are required. (Table 3.1-1 Material
requirements)
Software Type Recommended Software
MD5 WinMD5 v1.20 or higher version
SSH client Putty 0.60 or higher version
SFTP server Core FTP mini-sftp-server V2.03 or higher version
G30 NE software G30 FP3.1.0 and FP3.0.3 or FP2.1.1 SW
New TNMS software V 17.10.0
Table 3.1-1 Material requirements
3.2 Hardware and software Check

It is important that all the NEs’ hardware versions should be checked.
Contact your next level technical support organization for further assistance if your
hardware or software version doesn’t match the request.
The command to check hardware version is:
show inventory
3.2.1 Hardware version check
It is important that all the NEs’ hardware versions should be reviewed. Only following
hardware versions or higher are supported.
Minimum
Product Number Description
revision
GQS-G30CHASZ-00 G30 chassis A
GPS-G30PSUAC-00 G30 AC power module A
GPS-G30PSUDC-00 G30 DC power module A
GFS-G30FANZZ-00 G30 fan module A
GLS-G30CHM1Z-00 G30 CHM1 card (4x100G) A
© Coriant 9/30
GLS-G30CHM1G-00 G30 CHM1G (4x100G) A

GLS-G30CHM1G-NC G30 CHM1G (4x100G, no encryption) A
G30 CHM2 card(40x10G, 10x40G,
GLS-G30CHM2Z-00 A
4x100G)
G30 CHM2 card(40x10G, 10x40G,
GLS-G30CHM2Z-NC A
4x100G, no encryption)
GLS-G30OCC2Z-00 G30 OCC2 A
GLS-G30OMD96-00 G30 OMD96-2 A
GLS-G30OMD48-SG G30 OMD48-S A
GLS-G30XTM2Z-00 G30 XTM2 A
81.71T-O2PAOSC-R6 OFP2 PREAMP WITH OSC A
OFP2 PRE-AMP AND BOOSTER
81.71T-O2PABA-R6 A
AMP
IR Preamp + OSC Add/Drop, High
81.71T-O2PAOHIR-R6 A
Channel Count OFP2
LR Preamp + OSC Add/Drop, High
81.71T-O2PAOHLR-R6 A
Channel Count OFP2
ER Preamp + OSC Add/Drop, High
81.71T-O2PAOHER-R6 A
Channel Count OFP2
Booster Amplifier OFP2 (BA OFP2),
81.71T-O2BAH-R6 A
High Channel Count
ZXC-O2BAUZZZ-00 OFP2 Booster Amp Ultra High Power A
OFP2 Preamp Ultra High Power
ZXC-O2PAOULR-00 A
Longer Reac
ZXC-O2OPS1ZZ-00 OFP2 1CH OPS Module A
ZXC-O2TDCMZZ-00 OFP2 TDCM A
ZXS-O2OMB8B1-00 OFP2 OMD8 Band1 A
ZXS-O2OMB8B2-00 OFP2 OMD8 Band2 A
ZXS-C20TSTZZ-00 CFP2-ACO GHP A
ZXS-C2ACOTZZ-00 CFP2-ACO CHP A
ZXC-C2OTBDZZ-00 CFP2-ACO Bidirectional A
ZXC-C2OMSTZZ-00 CFP2-ACO MHP A
ZXS-Q8S4ZZZZ-00 QSFP28 100G SR4 A
ZXS-Q8L4ZZZZ-00 QSFP28 100G LR4 B
ZXS-Q8L4ZZDR-00 QSFP28 100G LR4 DR A
ZXS-Q8CWDM4Z-00 QSFP28 100G CWDM4 A
ZXC-Q8PSM4ZZ-00 QSFP28 100G PSM4 A
ZXS-Q8AOCZZZ-03 QSFP28 Active Optical Cable 3m A
ZXS-Q8AOCZZZ-10 QSFP28 Active Optical Cable 10m A
ZXS-Q8FCPSMZ-00 QSFP28 4x8/16GFC A
QSFP28 SR4 Multirate
ZXS-Q8S4ZZMR-00 A
(100GbE,OTU4,32GFC)
ZXS-Q8FCPSMZ-00 QSFP28 4x8/16GFC,PSM A
10/30 © Coriant
81.71T-Q40GSR4-R6 QSFP+ 40GBE INTERFACE - 100 A

ZXS-QPL4ZZZZ-00 QSFP+ 40GE LR4 A
ZXS-QPS4EZZZ-00 QSFP+, 40G eSR4,10GBase-SR A
ZXC-QPI4ZZZZ-00 QSFP+, 40G IR4 A
QSFP+,40GBase-LR4(DR),
81.71T-Q40GLR4-R6 A
OTU3/OTU2/OTU2E/OC192
ZXS-QPE4ZZZZ-00 QSFP+, 40GBase-ER4 A
ZXS-QPFCZZMR-00 QSFP+, 4x FC8G, 4xFC16G A
ZXS-QPQ10GLW-00 QSFP+ 4x10GE LR/W PSM A
ZXS-Q8AOCZDR-01 QSFP28 Active Optical Cable DR 1m A
ZXS-Q8AOCZDR-05 QSFP28 Active Optical Cable DR 5m A
SFP+,10GBASE/8G FC/10G FC-
81.71T-SP10GLR-R6 A
LR/LW 1310 SM 10KM
SFP+,10GBASE/8G FC/10G FC-
81.71T-SP10GSR-R6 A
SR/SW 850 MM 300M
SFP+,DWDM TUNABLE 88 CH LR2
81.71T-SPDWDM-R6 A
80KM
SFP+,1310 SM MULTIRATE SR1
81.71T-SPMRSR1-R6 A
7KM
Table 3.2-1 Hardware version check
NOTICE:
The new support cards and modules must be plugged into the chassis after upgrade
procedure completed. Please check the release note to find the new support cards and
modules information of each release.
© Coriant 11/30
3.2.2 Software version check
Confirm the active software version is G30 FP3.0.3.

show softwareload
Figure 3.2.2-1 Software version check
Confirm the active ‘swload-version’ is ‘FP3.0.3’ and version is ‘GSS-G3003000-BZ

Groove G30 3.0.3 2018-07-10 Copyright 2018 Coriant’.
The ‘swload-version’ for ‘FP2.1.1’ is ‘GSS-G3002110-BZ Groove G30 2.1.1 2018-01-
31 Copyright 2018 Coriant’.
*Note: The ‘softwareload-2’ is empty when delivered from factory.
3.3 Alarm Management

It is recommended that NE is running alarm-free before the upgrade. Please refer to
chapter 7 of the User Guide to clear the existing alarms on the NE.
3.4 NE Database Backup

WARNING
! Even if the database backup has been done before, please backup the
database again to make sure it is up-to-date.
Use the following command to back up the database of the NE to the SFTP/SCP
server:
upload database sftp://username@<sftp IP address>/<filename>.zip
* For example “upload database sftp://groove@172.29.51.227/NE-Name-DBbackup-20180801.zip”
upload database scp://username@<scp IP address>/<filename>.zip
* For example “upload database scp://groove@172.29.51.227/NE-Name-DBbackup-20180801.zip”
Input the SFTP/SCP password when the prompt ‘PASSWORD:’ is on the screen.
12/30 © Coriant
Figure 3.4-1 Database backup
Waiting for the system prompts ‘upload completed’.
Figure 3.4-2 Database backup finish
Check if the database file has been uploaded at the appointed folder of the
SFTP/SCP server.
3.5 Clear NE Sessions

Before the upgrade it is mandatory to stop all the Netconf connection from each
server and clear the Netconf/SSH sessions on NE, only keep the CLI or WebGUI
sessions for upgrade.
Use the following command to show sessions and delete sessions.
show session
delete session-<IP address:port>
Answer ‘y’ for the question ‘Are you sure’?
* For example “delete session-172.29.51.248:60815”
Figure 3.5-1 Delete session
© Coriant 13/30
4 TNMS Upgrade
Please refer to the TNMS release notes and customer documentation for the TNMS
compatibility and upgrade on the CRM portal (http://customer.coriant.com).
14/30 © Coriant
5 SW Downloading Instructions
5.1 New NE Software
The SW load of G30 FP3.1.0 can be found on the CRM (http://customer.coriant.com).
Unzip the downloaded file in same folder from CRM .Copy two files in same folder on
the SFTP server.
*Note: There are 2 files in the system software, same file name but different suffix (.dcr
and .zip). These 2 files should be saved in a same folder.
*If you can’t get the NE SW from above link, please contact your Coriant’s support team.
GROOVE_G30_3.1.0_20180731.dcr, the file size is 1,385 bytes.
MD5 checksum: 550d61cdd07042b715af92914768681c
GROOVE_G30_3.1.0_20180731.zip, the file size is 214,367,039 bytes.
MD5 checksum: b2b6f78a0334e81f343fd9ed4ad2e7b4
Table 5.1-1 FP3.1.0 NE software MD5 checksum
Before implement the software load, make sure the MD5 checksum generated by you
is the same as published in the upgrade procedure.
5.2 NE Software Download

Download the NE SW FP3.1.0 from the server to the NE.
*Downloading new NE software load is mandatory requested every time before upgrading.
Use the following command to download new software load of the NE from the
SFTP/SCP/HTTP server:
*http default is disabled; need to enable before downloading software.
set security http-support enabled
download swimage sftp://<user name>@<sftp server IP>/<NE SW name>
*For example “download swimage sftp://groove@172.29.51.227/GROOVE_G30_3.1.0_20180731”
download swimage scp://<user name>@<scp server IP>/<NE SW name>
*For example “download swimage scp://groove@172.29.51.227/GROOVE_G30_3.1.0_20180731”
download swimage http://<http server IP>/<NE SW name>
*For example “download swimage http://172.29.51.227/GROOVE_G30_3.1.0_20180731”
Input the SFTP/SCP password when the prompt ‘PASSWORD:’ is on the screen.
© Coriant 15/30
Figure 5.2-1 NE software download

Waiting for download completed.
Figure 5.2-2 NE software download finish
5.3 NE Software Check

Once the software downloading is finished, check if the downloaded software version
is correct.
show softwareload
Figure 5.3-1 NE software check
Confirm the active ‘swload-version’ is FP3.0.3 and the inactive ‘swload-version’ is

FP3.1.0 with ‘swload-label’ ‘GSS-G3003100-BZ Groove G30 3.1.0 2018-07-31
Copyright 2018 Coriant’.
16/30 © Coriant
6 Release delivery upgrade instructions

6.1 Software Switching
Input the following command to switch the SW image.
activate swimage
Answer ‘y’ for the question ‘Are you sure?’ y
Figure 6.1-1 NE software switching

NE will switch the NE SW and warm reboot automatically. It will loss communication
from the SSH client.
Figure 6.1-2 SSH disconnected

After 5 minutes, the NE can be connected again.
When the NE is re-connected, use the following command to confirm the NE SW is
switched successfully:
show softwareload
Figure 6.1-3 NE software checking

The FP3.1.0 SW should be active, while FP3.0.3 SW is inactive.
6.2 Reboot
FP2.1.1FP3.1.0 Please select either cold reboot cards separately or cold reboot NE to
finish all the upgrade process. Recommend reboot it same time on both NEs after activate
SW image in order to reduce the traffic interruption interval.
FP3.0.3FP3.1.0 Please warm reboot NE with FPGA-Upgrade and cold reboot CHM1G
card.
© Coriant 17/30
6.2.1 Cold reboot cards

Cold reboot card impacts the traffic related this card.
Cold reboot card steps:
restart card-1/1 cold
*Traffic will be impacted in this step. Refer to chapter 2.2.
Figure 6.2.1-1 cold reboot the card

Check if the operation status of the card is ‘up’.
show card
*It will be maximum 15 minutes to wait for the card becomes operational.
Figure 6.2.1-2 Check card operation status

When upgrading NE software all cards need to cold reboot once. But it must be
reboot separately.
6.2.2 Cold reboot the NE
If the card has been done with cold reboot separately, please skip this chapter.
Cold reboot NE steps:
restart ne cold
*Traffic will be impacted in this step. Refer to chapter 2.2.
Figure 6.2.2-1 cold reboot the NE

Check if the operation status of all the cards are ‘up’.
show card
*It will be maximum 15 minutes to wait for all the cards become operational.
18/30 © Coriant
Figure 6.2.2-2 Check card operation status

6.2.3 Warm reboot the NE with FPGA-Upgrade
If the card has been done the cold reboot separately, please skip this chapter.
Warm reboot NE with FPGA-Upgrade steps:
restart ne warm fpga-upgrade
*Traffic will not be impacted with FPGA hitless upgrade in this step.
Figure 6.2.3-1 warm reboot the NE with FPGA-Upgrade

NOTICE:
If the Groove G30 is interworking with hiT7300, the preemphasis-value of the Line side
should be 0.7. If the value is not 0.7, please reconfigure this value by user and it will impact
the traffic.
Figure 6.2.2-3 preemphasis-value on line side
© Coriant 19/30
7 Upgrade via Groove Web GUI

The Groove Web GUI is a web based element management tool. It’s only supported to
upgrade from FP2.1.1 and FP3.0.3 to FP3.1.0 via the Web GUI.
7.1 Software version check
Figure 7.1-1 Software version check
7.2 NE Database Backup
WARNING
! Even if the database backup has been done before, please also backup the
database again to ensure it is up-to-date.
Figure 7.2-1 Database backup
20/30 © Coriant
Figure 7.2-2 Database backup finish
7.3 NE Software Download
Download the NE SW FP3.1.0 from the server to the NE.
Figure 7.3-1 NE software download
Figure 7.3-2 NE software download finish
© Coriant 21/30
7.4 NE Software Check
Figure 7.4-1 NE software check
7.5 Software Switching
Figure 7.5-2 confirm NE software switching
22/30 © Coriant
Figure 7.5-3 Web GUI disconnected
7.6 Reboot
FP2.1.1FP3.1.0 Please select either cold reboot cards separately or cold reboot NE to
finish all the upgrade process. Recommend reboot it same time on both NEs after activate
the SW image in order to reduce the traffic interruption interval.
FP3.0.3FP3.1.0 Please warm reboot NE with FPGA-Upgrade and cold reboot CHM1G
card.
7.6.1 Cold Reboot cards

Cold reboot card.
Figure 7.6.1-1 Cold reboot card
© Coriant 23/30
Figure 7.6.1-2 select cold reboot card
Figure 7.6.1-3 confirm cold restart card

7.6.2 Cold reboot NE
If the card has been done with cold reboot separately, please skip this chapter.
Figure 7.6.2-1 cold reboot NE

7.6.3 Warm reboot NE with FPGA-upgrade
NE warm reboot with FPGA-upgrade step.
24/30 © Coriant
Figure 7.6.3-1 cold reboot NE
Figure 7.6.3-2 confirm NE cold reboot
© Coriant 25/30
8 Checking of the package consistency

8.1 Alarm verification
Check if there is no un-expected alarms reported after upgrade.

show alarms
Figure 8.1-1 show alarms
8.2 NE Software Version verification
Verity if the SW version, database version and firmware version are correct after
upgrade.
show –rt sw- management
Confirm the following items are correct after upgrade:
1. The active SW load version is ‘FP3.1.0;
2. The active database version is ‘FP3.1.0;
3. Confirmed the fw-state is all current
26/30 © Coriant
Figure 8.2-1 NE software version check
© Coriant 27/30
8.3 Re-connect NE
After NE completely rebooted with FP3.1.0, re-connect the NE by Netconf/WebGUI/CLI

sessions.
28/30 © Coriant
9 Fallback
If the NE is abnormal after upgrade (For example: function problem, traffic does not
return or other unpredictable problem), please rollback the foregone release.
9.1 Switch to previous version

Make sure the software load running on the inactive is FP3.0.3:

Input the following command to switch the SW image.
activate swimage
Answer ‘y’ for the question ‘Are you sure?’.
The NE will do cold reboot automatically. NE will loss communication from the SSH
client.
After 10 minutes, the NE can be connected again.
During fallback the traffic on the NE will interrupt for no more than 20 minutes in the
worst case.
When the NE is re-connected, use the following command to confirm the NE SW is
switched successfully.
After cold reboot completed, reconnect the NE by CLI, check the software load
information:
show –rt sw-management
Confirm the following items are correct after NE SW reboot:
1. The active database version is ‘FP3.0.3;
2. The active SW load version is ‘FP3.0.3;
© Coriant 29/30
3. Confirmed the fw-state is all current
Figure 9.1-3 Software version check
NOTICE:
If the NE cannot be recovered automatically after fallback or fw-state is not current, please
download the FP3.0.3 or FP2.1.1 software load, and switch to previous load and download
backup NE database.
============End of Procedure ============
30/30 © Coriant

GDM G30FP031 05 0A Release Upgrade Procedure

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GDM G30FP031 05 0A Release Upgrade Procedure

Uploaded by

Copyright:

Available Formats

Groove™ G30

Issue: A Issue date: Aug 2018

Coriant is continually striving to reduce the adverse environmental

4 TNMS Upgrade ............................................................................................. 14

5 SW Downloading Instructions ....................................................................... 15

6 Release delivery upgrade instructions ........................................................... 17

7 Upgrade via Groove Web GUI....................................................................... 20

7.5 Software Switching........................................................................................ 22

8 Checking of the package consistency ........................................................... 26

Contact your local Coriant support team.

Date Version Summary of changes

2.1 Upgrade Path

Original Version Target Version

2.2 Service interruption

Warm Reboot with Cold Reboot for

For NE cold reboot:

For OCC2 card (with three subcards) cold reboot:

2.3 Management interruption

3.2 Hardware and software Check

3.2.1 Hardware version check

GLS-G30CHM1G-00 G30 CHM1G (4x100G) A

81.71T-Q40GSR4-R6 QSFP+ 40GBE INTERFACE - 100 A

3.2.2 Software version check

Confirm the active software version is G30 FP3.0.3.

Figure 3.2.2-1 Software version check

Confirm the active ‘swload-version’ is ‘FP3.0.3’ and version is ‘GSS-G3003000-BZ

3.3 Alarm Management

3.4 NE Database Backup

Figure 3.4-1 Database backup

Waiting for the system prompts ‘upload completed’.

Figure 3.4-2 Database backup finish

3.5 Clear NE Sessions

Figure 3.5-1 Delete session

5.2 NE Software Download

Figure 5.2-1 NE software download

Figure 5.2-2 NE software download finish

5.3 NE Software Check

Figure 5.3-1 NE software check

Confirm the active ‘swload-version’ is FP3.0.3 and the inactive ‘swload-version’ is

6 Release delivery upgrade instructions

Figure 6.1-1 NE software switching

Figure 6.1-2 SSH disconnected

Figure 6.1-3 NE software checking

6.2.1 Cold reboot cards

Figure 6.2.1-1 cold reboot the card

Figure 6.2.1-2 Check card operation status

Figure 6.2.2-1 cold reboot the NE

Figure 6.2.2-2 Check card operation status

Figure 6.2.3-1 warm reboot the NE with FPGA-Upgrade

Figure 6.2.2-3 preemphasis-value on line side

7 Upgrade via Groove Web GUI

7.1 Software version check

Figure 7.1-1 Software version check

7.2 NE Database Backup

Figure 7.2-1 Database backup

Figure 7.2-2 Database backup finish

7.3 NE Software Download

Download the NE SW FP3.1.0 from the server to the NE.

Figure 7.3-1 NE software download

Figure 7.3-2 NE software download finish

7.4 NE Software Check

Figure 7.4-1 NE software check

7.5 Software Switching