FibeAir Software Upgrade Procedure (Rev3.3)

Software UpgradeProcedure

0.0 Table of Content

TITLE

PAGE

20.0 Table of Content

1.0 Scope and Purpose32.0 General33.0 Introduction34.0 Required Accessories45.0 Software Download using CeraView55.1General55.2Record the Existing Software Versions55.3Configure CeraView - TFTP Parameters55.4CeraView Configuration File - TFTP Parameters65.5Software Download76.0 Software Download using Hyper-Terminal96.1General96.2Record the Existing Software Versions96.3Download IDC Software Version96.4Download MUX Software Version106.5Download ODU Software Version106.6Clearing Downloaded Software Versions117.0 Acceptance Tests after Download12APPENDIX 1 Field Upgrade Form14

1.0 Scope and Purpose

The purpose of the following document is to specify the procedure for IDUs and ODUs software versions upgrade using software download.

Ceragon elements can be upgraded easily locally (on-site) or remotely using CeraView management application.

2.0 General

Ceragons authorization is required for any software upgrade.

Such authorization will be granted only to customers that were trained by Ceragon for such activity.

Customer must verify with Ceragon that software upgrade is possible and should there be any further requirements.

It is recommended to upgrade spare units first, before operational units.

This way customer will provide himself experience with the upgrade process and will have replacement units in case of problems.

Software upgrade details should be recorded in a Field Upgrade Form (Appendix 1) and sent to Ceragon upon completion of the upgrade.

3.0 Introduction

Ceragons FibeAir IDU is designed to include an indoor unit controller (IDC) and a multiplexer (MUX) cards and the FibeAir ODU is designed to include an outdoor unit controller (ODC) card. Each of these has an associated software version to maintain; and the software may be upgraded to add new feature/functionality to the equipment.

The three software types are stored on EPROMs on the IDC, MUX and ODC cards.

When IDU or ODU are shipped from Ceragon, the software versions are burnt into the EPROMs and stored there. These software versions are referred as the Boot version.

The FibeAir terminal must be reset (via software or hard power reset) to implement the new software. Upon radio reset, the new software version will become the currently operating version.

If you download new software version again, the latest software version will overwrite the previously downloaded software version and the previously downloaded software version will be erased.

The only way to activate the Boot software version is to clear the downloaded software version via the Hyper-Terminal.

If more than one card should be upgraded, download software to IDC, MUX and ODC in this order. Reset the terminal only after the successful download to all cards is completed.

4.0 Required Accessories

Software upgrade might hold great benefit to customers.

However, they involve downtime for the link (at least two minutes), as the terminals must be reset to activate the new software.

Before starting the upgrade, verify that you have the following items:

This Software Upgrade guide

Software versions for download

(For TFTP download)

IP connectivity to the units to be upgraded (either locally or remotely)

(For Hyper-terminal download)

Laptop with Hyper-Terminal connection to the IDU

9 pin null-modem cable for the IDU-laptop connection

5.0 Software Download using CeraView5.1GeneralIn order to assure the upgrades success, please follow these steps carefully and according their order.

Please note that you can perform the upgrade at any time without interrupting the link. The new software versions will take affect only after rebooting the IDUs.

The CeraView software download can be performed locally or remotely via SNMP (TFTP, Trivial File Transfer Protocol).

5.2 Record the Existing Software Versions

The System Information provided for every FibeAir radio terminal includes the software versions for IDU, ODU and MUX. It is recommended to review/record the currently operating software versions for IDU, ODU and MUX prior to completing a software upgrade.

5.2.1 Launch CeraView

5.2.2 Go to File ( Local ( System Information5.2.3 View the existing software versions for IDU, ODU and MUX in the System Information screen

5.2.4 Record these software versions on the Field Upgrade Form

5.3 Configure CeraView - TFTP Parameters

For CeraView versions 1.53 and above.

The TFTP parameters of the CeraView configuration application should be set prior to starting the CeraView software download.

5.3.1 Create new folder in drive C named dwld (C:\dwld) and store the download files in it.

5.3.2 Click Start ( Programs ( CeraView ( CeraView Config. The CeraView Configuration screen will be opened.

5.3.3 Select File Transfer Configuration tab.

5.3.4 In TFTP Server Address field enter the IP address of the computer.

5.3.5 In TFTP Files Location field browse and enter the folder path where the download files are located.

5.3.6 In TFTP Timeout leave the default value of 90 seconds.

5.3.7 In TFTP Retries leave the default value of 4.

5.3.8 In Use Internal TFTP Server field select True.

5.3.9 Click Apply to save changes.

5.4 CeraView Configuration File - TFTP Parameters

For CeraView versions below 1.53, the configuration file of the CeraView should be edited prior to starting the CeraView software download.

Upon successful installation of the CeraView element management application, a file named CeraView.cfg is created and stored.

The default file location is C:\Program Files\CeraView\config. The file may be opened using WordPad.

This file contains all the configuration of the CeraView application, including the RSD (Remote Software Download) parameters.

5.4.1 Create new folder in drive C named dwld (C:\dwld) and store the download files in it.

5.4.2 Open CeraView.cfg file using Notepad.

5.4.3 Set rsdServerRootDir as the full path of the directory of the files to be downloaded. If this directory is not correctly configured, the software download will not work properly.5.4.4 Set the rsdServerIp as the IP address of the host that the tftp server is running on (the PC IP address).

5.4.5 Set rsdUseInternalServer (only for windows platforms)- True: use internal (CeraViews) tftp server application- False: use of other (external) tftp server application

5.4.6 Save the file

Cfg file example:

rsdServerRootDir =c:/dwld

rsdServerIp =192.168.1.100

rsdTftpRTimeOut = 10

rsdTftpRetry = 4

rsdUseInternalServer = trueNote: If the CeraView.cfg file is configured while the CeraView application is open, you must close Ceraview and then reopen it so all changes will take place.5.5 Software Download

An authorized user (proper username/password access required) may upgrade the IDC, MUX and ODC software versions of a FibeAir radio terminal using the following procedure.

5.5.1 Launch CeraView

5.5.2 Go to File ( Local ( Software Download. The Software Download screen will appear.

5.5.3 Click Browse for the IDC, MUX and/or ODC software versions to be downloaded. Only the files that were stored in the rsdServerRootDir (in the CeraView.cfg file) will be available to choose.5.5.4 Click Choose for the files to be downloaded.5.5.5 Check the Reset box if you wish to have the radio automatically reset upon completion of the software download.

5.5.6 Click Apply to start the IDU software download process. A progress bar indicating the TFTP download will indicate the download progress.

5.5.7 Upon successful completion of software download, a message indicating TFTP download succeeded will be displayed in the Download Log.

5.5.8 MUX and ODU TFTP Download will be followed by MUX Internal Download and ODU Internal Download processes.

5.5.9 Click Close to close the window, and exit the Software Download screen.

5.5.10 If you did not select the Reset option, you will need to reset the IDUs to implement the new software version.

5.5.11 After the IDU was rebooted, Launch CeraView and go to File ( Local ( System Information and verify the software versions for IDU, ODU and MUX were accepted.

6.0 Software Download using Hyper-Terminal6.1GeneralIn order to assure the upgrades success, please follow these steps carefully and according their order.

Please note that you can perform the upgrade at any time without interrupting the link. The new software versions will take affect only after rebooting the IDUs.

6.2 Record the Existing Software Versions

6.2.1 Open Hyper-Terminal session

6.2.2 Select System Status (2) from the Main Menu

6.2.3 View the existing software versions for ODC (ODU controller), MUX (Multiplexer card) and Manager (IDC card).

6.2.4 Record these software versions on the Field Upgrade Form

6.3 Download IDC Software Version


6.3.2 Select System Control (3) from the Main Menu6.3.3 Select Download Software (2)

6.3.4 Select Download Manager Software (X)

6.3.5 Right click with the mouse in the Hyper-Terminal screen and select Send File6.3.6 Browse for the path of file of the new software that you wish to download

6.3.7 Select Xmodem as the protocol and click Send6.3.8 Monitor the file as it sends on the screen. Verify that the countdown is in progress (IDC download can take up to 30 minutes). Verify that no errors are reported

If you intend to download the MUX or ODC software versions as well, wait till the download is finished and continue to Sec 6.4 or Sec 6.56.3.9 When download is finished, reboot the IDU (no upload is needed). Wait 2 minutes before you access the IDU

Important! Do not reboot the IDU before 2 minutes passed or during the download process

6.3.10 Verify that the new software was downloaded successfully (Sec 6.2 above).

6.4 Download MUX Software Version



6.4.4 Select Download MUX Software (M)


6.4.7 Select Xmodem as the protocol and click Send6.4.8 Monitor the file as it sends on the screen. Verify that the countdown is in progress. Verify that no errors are reported

6.4.9 When download is finished, you will be asked to upload the software

6.4.10 In the System Control Menu select Upload Software (3)

6.4.11 Select Upload MUX Software (M)

6.4.12 Monitor the Hyper-Terminal screen as the software uploaded until you will see the confirmation that the Upload was successful

If you intend to download the ODC version as well, continue to Sec 6.56.4.13 When upload is finished, reboot the IDU. Wait 2 minutes before you access the IDU

Important! Do not reboot the IDU before 2 minutes passed or during the download or upload process


6.5 Download ODU Software Version

Important! ATPC must be disabled during ODU software download



6.5.4 Select Download ODU Software (O)


6.5.7 Select Xmodem as the protocol and click Send6.5.8 Monitor the file as it sends on the screen. Verify that the countdown is in progress. Verify that no errors are reported

6.5.9 When download is finished, you will be asked to upload the software

6.5.10 In the System Control Menu select Upload Software (3)

6.5.11 Select Upload ODU Software (O)

6.5.12 Monitor the Hyper-Terminal screen as the software uploaded until you will see the confirmation that the Upload was successful

6.5.13 When upload is finished, reboot the IDU. Wait 2 minutes before you access the IDU

Important! Do not reboot the IDU before 2 minutes passed or during the download or upload process


6.6 Clearing Downloaded Software Versions

Clearing the downloaded software version(s) might be required should there be any problems with the downloaded software.

Clearing downloaded software will return the product to its Boot version (the version that was sent with the product from Ceragon), and not to the last version downloaded.



6.6.4 For clearing the Manager software, select Clear Manager Software (CX)

6.6.5 For clearing the MUX software, select Clear MUX Software (CM)

6.6.6 For clearing the ODU software, select Clear ODU Software (CO)

6.6.7 After you receive a message that the software was cleared, reboot the IDU and wait 2 minutes before you access the IDU

Important! Do not reboot the IDU before 2 minutes passed or during the clearing process

6.6.8 Verify that the new software versions were cleared successfully and the units now have their Boot version active (Sec 6.2 above).

7.0 Acceptance Tests after DownloadUpgrading software version will not require reconfiguration of the link.

However, it is recommended that after each upgrade, the customer will verify the full configuration of the link and change configuration is necessary.

In addition, the customer must verify that the upgrade was successful and that the link, in its new configuration, functions properly.

Therefore, the following acceptance tests must be performed.

7.1 Configuration verification

7.1.1 Link configuration is according to link planning

7.1.2 The new interfaces are recognized in the Physical View screen of the CeraView

7.2 Link verification

7.2.1 LOF and BER leds of the IDUs front panel are green7.2.2 EOW verification7.2.3 Received signal level (RSL) is according to the level before the upgrade

7.2.4 Radio Bit Error Rate (BER) is 10E-11 or higher

7.2.5 ATPC is working properly (RSL=Reference level)

7.2.6 After connecting test-equipment or end-equipment to the Line Interfaces, all leds on the front panel of the IDU are green

7.3 Line interfaces verification

7.3.1 Connect SDH/SONET/ATM test equipment to the 155Mbps Main Channel interface and verify error free operation (1 hour minimum is recommended)

7.3.2 When working with a Fast Ethernet interface or DS-3/E3, connect the appropriate test equipment to verify error free operation (Packet Analyzer for Fast Ethernet or PDH analyzer for DS-3/E3)

7.3.3 Connect a PDH analyzer to verify error free operation of the T1/E1 wayside channel

7.4 Management verification

7.4.1 Verify that you can manage the link and that using the CeraView you are able to perform changes to the links configuration (i.e. channel frequency, Tx power, etc)

7.4.2 If you do not have maintenance window to perform the above-mentioned tests (as they might affect the traffic), change the Tx power (3 dB up or down) at both sides and see that the RSL changes accordingly7.4.3 Verify that the CeraView reports the correct parameters when performing the above

7.4.4 Verify that there are no active alarms on the link

7.4.5 In case the management station is remotely located (Network Operation Center), verify that the management station can manage the link and receive traps

APPENDIX 1 Field Upgrade Form

The following form should be completed for each upgraded unit.

FIELD UPGRADE FORM

0. GENERAL INFORMATION

0.1 Customer:

0.2 Radio model:0.3 Configuration:

0.4 Site Name and address:

1. HARDWARE & SOFTWARE UPGRADE

1.1 Product name:

1.2 Part Number:1.3 Serial Number:

Configuration before upgrade

Configuration after upgrade

1.4 Main Ch #1:1.5 Main Ch #1:

1.6 Main Ch #2:1.7 Main Ch #2:

1.8 Wayside Ch:1.9 Wayside Ch:

1.10 IDC s/w ver:1.11 IDC s/w ver:

1.12 MUX s/w ver:1.13 MUX s/w ver:

1.14 ODC s/w ver:1.15 ODC s/w ver:

Warranty seals broken: YES NO

On-site Software Download Remote Software Download

2. REASON FOR UPGRADE

3. ACCEPTANCE TESTS AFTER UPGRADE

3.1 Configuration Verification:Acc. to link planning Yes

3.2 Link Verification: Pass

3.3 Line Interfaces Tests: Pass

3.4 Management Verification: Pass

4. REMARKS/NOTES

5. UPGRADED BY

5.1 Upgraded byName + Title:

Company:Date:

5.2 Upgrade Authorized byName + Title:

Company:Date:

FibeAir Software Upgrade Procedure

Rev 3.1

FibeAir Software Upgrade Procedure

Page 3 of 14

_1029130466.bin

Documents

FibeAir Software Upgrade Procedure (Rev3.3)