Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Procedure
Rev 3.1
0.0 Table of Content 1.0 Scope and Purpose 2.0 General 3.0 Introduction 4.0 Required Accessories 5.0 Software Download using CeraView
5.1 General Record the Existing Software Versions Configure CeraView - TFTP Parameters CeraView Configuration File - TFTP Parameters Software Download
2 3 3 3 4 4
5 5 5 6 7
8 9 9 9 10 11
11 13
Page 2 of 14
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
FibeAir Software Upgrade Procedure Page 3 of 14
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.
Page 4 of 14
5.1
General
In 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).
Page 5 of 14
5.2.17 Set the rsdServerIp as the IP address of the host that the tftp server is running on (the PC IP address). 5.2.18 Set rsdUseInternalServer (only for windows platforms) - True: use internal (CeraViews) tftp server application - False: use of other (external) tftp server application 5.2.19 Save the file Cfg file example: rsdServerRootDir =c:/dwld rsdServerIp =192.168.1.100
FibeAir Software Upgrade Procedure Page 6 of 14
rsdTftpRTimeOut = 10 rsdTftpRetry = 4 rsdUseInternalServer = true Note: 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.
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.2.20 Launch CeraView 5.2.21 Go to File Local Software Download. The Software Download screen will appear. 5.2.22 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.2.23 Click Choose for the files to be downloaded. 5.2.24 Check the Reset box if you wish to have the radio automatically reset upon completion of the software download. 5.2.25 Click Apply to start the IDU software download process. A progress bar indicating the TFTP download will indicate the download progress.
5.2.26 Upon successful completion of software download, a message indicating TFTP download succeeded will be displayed in the Download Log. 5.2.27 MUX and ODU TFTP Download will be followed by MUX Internal Download and ODU Internal Download processes. 5.2.28 Click Close to close the window, and exit the Software Download screen. 5.2.29 If you did not select the Reset option, you will need to reset the IDUs to implement the new software version.
FibeAir Software Upgrade Procedure Page 7 of 14
5.2.30 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.
Page 8 of 14
In 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.
Page 9 of 14
6.2.18 Select Download MUX Software (M) 6.2.19 Right click with the mouse in the Hyper-Terminal screen and select Send File 6.2.20 Browse for the path of file of the new software that you wish to download 6.2.21 Select Xmodem as the protocol and click Send 6.2.22 Monitor the file as it sends on the screen. Verify that the countdown is in progress. Verify that no errors are reported 6.2.23 When download is finished, you will be asked to upload the software 6.2.24 In the System Control Menu select Upload Software (3) 6.2.25 Select Upload MUX Software (M) 6.2.26 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.5 6.2.27 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.2.28 Verify that the new software was downloaded successfully (Sec 6.2 above).
download or upload process 6.2.42 Verify that the new software was downloaded successfully (Sec 6.2 above).
Page 11 of 14
7.1.2 The new interfaces are recognized in the Physical View screen of the CeraView 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 Link verification LOF and BER leds of the IDUs front panel are green EOW verification Received signal level (RSL) is according to the level before the upgrade Radio Bit Error Rate (BER) is 10E-11 or higher ATPC is working properly (RSL=Reference level) 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 accordingly 7.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
Page 12 of 14
0.3 Configuration:
1. HARDWARE & SOFTWARE UPGRADE 1.1 Product name: 1.2 Part Number: 1.3 Serial Number: Configuration before upgrade Configuration after upgrade
Page 13 of 14
1.4 Main Ch #1: 1.6 Main Ch #2: 1.8 Wayside Ch: 1.10 IDC s/w ver: 1.12 MUX s/w ver: 1.14 ODC s/w ver: Warranty seals broken: On-site Software Download 2. REASON FOR UPGRADE
1.5 Main Ch #1: 1.7 Main Ch #2: 1.9 Wayside Ch: 1.11 IDC s/w ver: 1.13 MUX s/w ver: 1.15 ODC s/w ver: YES NO
3. ACCEPTANCE TESTS AFTER UPGRADE 3.1 Configuration Verification: 3.2 Link Verification: 3.3 Line Interfaces Tests: 3.4 Management Verification: 4. REMARKS/NOTES
Yes
5. UPGRADED BY
5.1 Upgraded by Name + Title: Company: 5.2 Upgrade Authorized by Name + Title: Company: Date: Date:
Page 14 of 14