ap site commissioning procedure

AP Site Commissioning Procedure

Networks & Enterprise Wireless Broadband (WiBB)


Page-2

Revision History

Revision Date Description

00.00.01 10/08/2006 Initial Creation 00.00.02 10/25/2006 Review Updates 01.00.00 11/14/2006 Changing Doc Rev Number per Release Binder

Review 01.00.01 11/20/2006 Update to ap software version 2.16.13 01.00.02 12/01/2006 Fixing Boot Parameter printouts 01.00.03 12/11/2006 Add warning text for RFHead code load. 01.00.04 01/03/2007 Update Doc for Trial Pack C. 01.00.05 01/12/2007 Review Updates 01.00.06 01/23/2007 Remove 512 MB restriction. 01.00.07 02/06/2007 Modified AP Diagnostics procedure 01.00.08 02/19/2007 Removed “manual LMT updates” section 01.00.08 02/21/2007 Corrected Typo – reference to Appendix D 01.00.09 02/27/2007 Update modem upgrade paths 01.00.0A 03/01/2007 Added Boot Param Verification. 01.00.0B 03/06/2007 Revisions 01.00.0C 03/08/2007 Remove extra BL version references and appendix B. 01.01.00 03/27/2007 M4 document updates 01.01.01 04/12/2007 M3 document updates and incorporated workaround

described in wimax_a_ap_001 01.01.02 04/27/2007 Added site commissioning archive procedure. 01.01.03 10/22/2007 Added step to check system time before running

apcommission.


Page-3

Table of Contents DEFINITIONS, ACRONYMS, AND ABBREVIATIONS ........................................................................ 4 SCOPE OF THIS DOCUMENT..................................................................................................... 5 PREREQUISITES ..................................................................................................................... 6 REQUIRED EQUIPMENT ........................................................................................................... 6 REQUIRED SOFTWARE ............................................................................................................ 6 EQUIPMENT AND SOFTWARE SETUP......................................................................................... 6 SITE COMMISSIONING INFORMATION COLLECTION ..................................................................... 8 JUMPER REMOVAL VERIFICATION........................................................................................... 10 BOOT PARAMETER VERIFICATION .......................................................................................... 10 SOFTWARE UPDATE ............................................................................................................. 12 SITE COMMISSIONING ........................................................................................................... 12 INSTALLATION AND NETWORK CONNECTIVITY VERIFICATION...................................................... 13 APPENDIX A - MANUAL SOFTWARE UPGRADE OF A SITE CONTROLLER. .................................... 14

Configuring Equipment and Software ......................................................................... 14 Updating the software on the Site Controller. ............................................................. 14

APPENDIX B – REMOVED ...................................................................................................... 17 APPENDIX C – AP DIAGNOSTICS............................................................................................ 18


Page-4

Definitions, Acronyms, and Abbreviations AP Access Point

BCU Baseband Control Unit

BS Base Station

EMS Element Management System

FQDN Fully Qualified Domain Name

FRU Field Replaceable Unit

FTP File Transfer Protocol

HTC Hardware Test Code

HTTPS Hyper Text Transfer Protocol over SSL

IP Internet Protocol

LMT Local Maintenance Terminal

MOP Method of Procedure

SSL Secure Socket Layer

TFFS True Flash File System

WiBB Wireless Broadband


Page-5

Scope of this Document This document describes the procedures for initial software installation and configuration of an Access Point for M3 on pilot hardware. The assumption of the documents is that all prerequisite steps have been completed and all specified equipment has been acquired prior to starting the procedure. The Equipment and Software Setup procedure should be performed while the laptop still has an internet connection. All procedures in this document assume an understanding of Microsoft Windows, Windows networking and standard Windows tools such as WinZip and Internet Explorer.


Page-6

Prerequisites • Hardware installation procedure is complete. • All necessary cabling has been completed for the backhaul. • The RF head(s) have been installed, are powered, and have been connected to the

Access Point. • Hardware Configuration is correct. (See release notes for supported hardware

configuration.) • The site has not previously been commissioning.

Required Equipment

• Laptop with a DB9 serial port installed with the Microsoft Windows XP operating system.

• Serial Cable – DB9 Male to DB9 female cable • Category 5 or greater crossover Ethernet cable.

Required Software • Tera Term Pro version 2.3 or greater

(http://hp.vector.co.jp/authors/VA002416/teraterm.html) or equivalent terminal emulator.

• freeFTPd version 1.0.1.1 or later (http://www.freeftpd.com/?ctt=download) or equivalent ftp server.

• WinZip version 7.0 or later. • Official Access Point Software Distribution(dapsc_factory.tgz and dapsc_full.tgz).

Equipment and Software Setup Tera Term Pro Setup(only needs to be performed one time.)

1. Download and install Tera Term Pro. 2. Use the default settings to install, unless they do not work for the laptop being used.

Laptop and Network Setup(only needs to be performed one time.).

1. Configure the ethernet interface that will be networked with the Site Controller. Set the address to 144.190.240.2.

2. Configure the subnet mask to be 255.255.240.0. WinZip(only needs to be performed one time, if manual software update is necessary)

1. Download and install Winzip 2. Use the default setting to install, unless they do not work for the laptop being used.

freeFTPd Setup (only needs to be performed one time, if manual software update is necessary)

1. Download and install freeFTPd. 2. Use the default setting for the installation, unless the laptop being used requires

different settings. 3. Start freeFTPd. 4. Double click the Users menu option to open the users window.


Page-7

5. Click the Add button. a. Login should be “apftp” b. Authorization should be set to “Password stored as SHA1 hash” c. Password should be set to “apftp” d. Confirmation password should be setup to “apftp” e. All other settings should be correct.

6. Create the directory specified as the ftproot directory on the FTP setup page 7. Create an apftp directory under the ftproot directory.

Official Access Point software. (only necessary if manual software update is required.)

1. Copy the dapsc_full.tgz file to the apftp directory under the ftp root directory ("C:\Program Files\freeFTPd\ftproot\apftp" is the default path to the ftp root directory.

2. Copy the dapsc_factory.tgz file to the apftp directory under the ftp root directory. 3. Rename dapsc_full.tgz to dapsc.tgz apftp directory under the ftp root directory. 4. Extract the dapsc_factory.tgz file using WinZip. 5. Copy the zImage_codeload.elf file to the apftp directory under the ftp root directory.

Note: When you are finished, you should have these 2 files in the apftp directory under the ftp root directory: dapsc.tgz and zImage_codeload.elf


Page-8

Site Commissioning Information Collection Obtain the following information prior to commissioning your site: Site Commissioning Related Parameters: These parameters are necessary for network and initial account setup for the access point.

AP Domain Name(FQDN): ____________________________________________ Note for TPC and beyond the VLAN id is now entered in decimal instead of hexadecimal format. External Vlan ID(1-2303, 2432-4094): ____________________________________ AP IP Configuration Method(0=static, 1 = dynamic): ________________________ See the “Provisioning on the DHCP Server” section of the “WiMAX Network IP Planning” document for details on DHCP server configuration.

The following information will be required if you do not use a dynamic configuration. AP IP Address(IPv4 Backhaul IP address): ___________________________ Subnet Mask(IPv4): _____________________________________________ Default Gateway IP Address(IPv4): ________________________________ Primary DNS Server IP Address(IPv4): ______________________________ Secondary DNS Server IP Address(IPv4): ____________________________ EMS Address (IPv4): ____________________________________________

Backhaul Auto negotiation (0 = disabled, speed, duplex and auto mdi x are user specified, 1 = enable auto negotiation): Select disable (0) auto negotiation for the workaround described in wimax_a_ap_001 Bulletin

The following information will be required if you do not use autonegotiation. Backhaul Duplex(0 = half duplex, 1 = full duplex): Select full duplex (1) for the workaround described in wimax_a_ap_001 Bulletin Backhaul Link Speed(0 = 10 Mbit, 1 = 100Mbit, 2 = Select 100Mbit (1) for the workaround described in wimax_a_ap_001 Bulletin Backhaul Auto MDI X(0 = disabled, 1 = enabled): Select MDIX enabled (1) for the workaround described in wimax_a_ap_001 Bulletin

Enter the account name for the local admin account: apadmin Enter the password for the local admin account: ______________________ Enter the password for the root account: ___________________________________

LMT Security Certificate Related Parameters: These parameters will be used to generate the LMT security certificate used to provide the secure http connection between the access point LMT and a web browser.


Page-9

Country Name(2 letter code) (US is the default): _______________________________ Organization Name (eg company): __________________________________________ Organization Unit Name (eg section): ________________________________________ Common Name (AP Domain Name(FQDN)): _________________________________


Page-10

Jumper Removal Verification 1. Remove all jumpers on all site controllers. 2. Remove all jumpers on all modems.

Boot Parameter Verification Site Controller(Procedure repeated for each site controller) 3. Connect a serial cable from your laptop to the Site Controller’s front panel serial port 4. Start Tera Term Pro on the laptop.

a. Select serial connection and the appropriate Com port on the window that will open in Tera Term (This will most likely be Com 1).

b. Select the “Setup” drop down menu and select “Serial port”. Use serial settings 9600 baud, 8 bit data, no parity, 1 stop bit, no flow control.

5. Power up the Site Controller. You should see the bootloader appear in your terminal application. If it doesn’t appear try to reset the Site Controller. Press any key to stop the autoboot (except “@”). You may have to press and hold a key to stop the boot and release the key when the “[SC Boot]:” prompt appears.

6. Use the “p” command to print the boot parameters. 7. Verify that they match the following:

boot device : tffs unit number : 0 processor number : 0 host name : host file name : /usr/app/scimg/zImage_911.elf inet on ethernet (e) : 144.190.240.1:fffff000 host inet (h) : 144.190.16.1 user (u) : apftp ftp password (pw) : apftp flags (f) : 0x8

Site Controller Linux cmd string params AutoIP base ipAddr : 144.190.15.0:fffff000 root : nfs root : 144.190.0.1 gateIpAddr : console dev : ttyS0 Console baud : 9600 misc. :

8. If the parameters do not match or have extra lines that are not shown here, please notify customer support.

Modem(Procedure repeated for each modem) 1. Connect a serial cable from your laptop to the Modem’s front panel serial port 2. Start Tera Term Pro on the laptop.




Page-11

3. Power up the Modem. You should see the bootloader appear in your terminal application. If it doesn’t appear try to reset the modem. Press any key to stop the autoboot (except “@”). You may have to press and hold a key to stop the boot and release the key when the “[BHP Boot]:” prompt appears.

4. Use the “v” command to get the current boot loader version.(Example output shown below). The line of interest is the BL version. This example shows the boot loader at version BL02.06.01.

CPU: MPC8548E - Security Engine Rev 1 Version: VxWorks 6.2 BL version: BL02.06.01 BSP version: BS02.06.01

5. Use the “p” command to print the boot parameters. 6. If the bootloader version(BL Version) is greater than or equal to BL02.06.01,

Verify that they match the following: boot device : mottsec unit number : 2 processor number : 0 host name : host file name : /usr/app/modimg/vxWorks.911 host inet (h) : 144.190.0.1 user (u) : apftp ftp password (pw) : apftp flags (f) : 0x8 Modem AutoIP Address Base AutoIP base ipAddr : 144.190.0.0:fffff000

7. If the bootloader version(BL version) is less than BL02.06.01 but greater than or equal to BL02.03.03, Verify that they match the following: boot device : tffs unit number : 0 processor number : 0 host name : host file name : /usr/app/modimg/vxWorks.911 host inet (h) : 144.190.0.1 user (u) : apftp ftp password (pw) : apftp flags (f) : 0x8 Modem AutoIP Address Base AutoIP base ipAddr : 144.190.0.0:fffff000

8. If the bootloader version does not fall into either of these categories or the parameters

do not match or have extra lines that are not shown here, please notify customer support immediately.


Page-12

Software Update

1. Connect a serial cable from your laptop to the Site Controller’s front panel serial port 2. Connect Crossover Ethernet cable between the Site Controller front Ethernet port

(debug port) and the laptop Ethernet adapter. 3. Start Tera Term Pro on the laptop.

c. Select serial connection and the appropriate Com port on the window that will open in Tera Term (This will most likely be Com 1).

d. Select the “Setup” drop down menu and select “Serial port”. Use serial settings 9600 baud, 8 bit data, no parity, 1 stop bit, no flow control.

4. Power up the Site Controller. You should see the bootloader appear in your terminal application. If the bootloader prompt does not appear, try a reset of the BCU.

5. If the Software load on the controller is prior to a TPC load or the load is not known, Perform the manual software update procedure of each site controller (See Appendix A) Note: The software version is displayed during startup of the AP.

6. Proceed to the site commissioning section. NOTE: When upgrading from any version of software prior to the TPC software, you must perform the site commissioning procedure, even if yourprevious access point had been commissioned. NOTE: The modems will not go active until the AP is bootstrapped and a valid configuration file has been pushed from the EMS.

Site Commissioning

1. Install all Modems and the Site Controller if they are not already installed. 2. Connect a serial cable from your laptop to the Site Controller’s front panel serial port 3. Connect Crossover Ethernet cable between the Site Controller front Ethernet port

(debug port) and the laptop Ethernet adapter. 4. Start a Tera Term Pro on the laptop. 5. Select serial connection and the appropriate Com port on the window that will open in

Tera Term (This will most likely be Com 1). 6. Select the “Setup” drop down menu and select “Serial port”. Use serial settings 9600

baud, 8 bit data, no parity, 1 stop bit, no flow control. 7. Boot the Site Controller 8. A message will appear on the console indicating that site commissioning data is not

valid. Site Commissioning must be performed if there is no site commissioning data. If site commissioning data exists and is valid, the application will start up and run.

9. When the AP completes initialization or when a login prompt appears. Login as root. User: root, password: The password you entered during the site commissioning procedure above.

10. Check the system time using the command: /bin/date and verify that the system time displayed is valid – a valid system time is considered to be anything from year 2000 to year 2037.


Page-13

• If the year does not fall within the valid range (e.g. if you see 1970 or 1999), you must set a valid system time before continuing. Run the following commands to set a valid system time and to sync the system time to the hardware clock. You can set it to the current time if you wish or to the time specified in the example below. /bin/date --set=”10/13/2007 12:00:00” /sbin/hwclock --systohc

11. Run the site commissioning application using the command: ”/usr/app/bin/apcommission”

12. Enter the appropriate data from the information collected during the pre-commissioning steps from the Site Commissioning Related Parameters section when prompted. Notes: • The data in the pre-commissioning step is in the same order as the site

commissioning application requests it. • During the creation of the local admin account, the default user name is apadmin

13. Enter “1” to commit commissioning data (site controller will continue to boot at this point).

14. Enter the appropriate LMT Certificate information collected during the pre-commissioning steps from the LMT Security Certificate Related Parameters section when prompted.

15. Reboot the site controller. 16. If you wish to archive the site commissioning data, perform the following procedure:

a. When the AP completes initialization or when a login prompt appears. Login as root. User: root, password: The password entered during the site commissioning procedure above..

b. Run the following command: /usr/app/bin/apcommission –print > /data/site_commissioning_data.txt

c. Transfer the file /data/site_commissioning_data.txt to an appropriate host in the network via sftp. This may be the EMS or another host running a sftp server.

17. At this point the modems will begin the software loading process. Wait for the modems to come up (they should reboot twice). Note the modem will not reach mac_state=2 and RF head code load will not happen. This is expected behavior.

18. Install(push in) all modems and site controllers at this time. 19. Proceed to Appendix B to perform AP diagnostics and set the sector ID for each RF

head that is present on the AP. Note: run apdiagnostics with all modems pushed in. 20. Reboot the site controller Installation and Network connectivity verification 1. Following Site Commissioning, the site controller should be booted. 2. Ping the EMS address provided during the Site Commissioning steps.


Page-14

Appendix A - Manual Software Upgrade of a Site Controller. Reminder: Each Site Controller should be loaded with all other boards unplugged. Configuring Equipment and Software

1. Connect a serial cable from your laptop to the Site Controller’s front panel serial port 2. Connect Crossover Ethernet cable between the Site Controller front Ethernet port

(debug port) and the laptop Ethernet adapter. 3. Start Tera Term Pro on the laptop.



4. Configure the Ethernet interface on the laptop that will be networked with the Site Controller. It should have a static IP 144.190.240.2 with a subnet mask of 255.255.240.0.

Updating the software on the Site Controller.

1. Unplug all other Site Controller and Modem boards before proceding. 2. Power up the Site Controller. You should see the bootloader appear in your terminal

application. If it doesn’t appear try to reset the Site Controller. Press any key to stop the autoboot.

3. At the [SC Boot] prompt use the “c” command to change the boot parameters. Configure them as follows – you can also type “h” to get a help menu. The ones in red should be updated for this procedure. All other parameters should be left as is by pressing the Enter key. Note “error erasing address….” messages are normal and can be ignored during this procedure. Note the parameters in black may not match exactly with when you see.

'.' = clear field; '-' = go to previous field; ^D = quit boot device : tffs0 mottsec1 processor number : 0 host name : host file name : /usr/app/scimg/zImage_911.elf zImage_codeload.elf inet on ethernet (e) : 144.190.240.1:fffff000 inet on backplane (b): host inet (h) : 144.190.16.1 144.190.240.2 gateway inet (g) : user (u) : apftp ftp password (pw) (blank = use rsh): apftp flags (f) : 0x8 target name (tn) : startup script (s) : other (o) :


Page-15

error erasing address 0xffff8000 . . . Site Controller Linux cmd string params '.' = clear field; '-' = go to previous field; ^D = quit AutoIP base ipAddr : 144.190.15.0:fffff000 root : nfs root : 144.190.0.1 gateIpAddr : console dev : ttyS0 Console baud : 9600 misc. : error erasing address 0xffff8000 . . .

4. Boot using the “@” command. The Linux Codeload kernel should boot and you should

see the Site Controller Codeload banner. Follow the prompts to enter things such as your FTP server IP, username/password. Once you’ve entered these parameters, the script will run on its own until codeload is complete. Here is sample output – the items in red and underlined are the parameters that should be entered. Note: If an error is made while entering the FTP server IP, the username, or the password, <ctrl>u may clear the field. If not, please start over from the beginning of this procedure.

5. When the following prompts appear, enter the information shown below.

Enter one of the following codeload options. You should use [u] ONLY if you've codeloaded this Site Controller with the [n] option previously using the version of the APSW Site Controller Codeload Kernel specified above. [n] new (use this option if unsure) [u] upgrade (faster) n ******************************************************** ** THE FOLLOWING FILE MUST BE ON THE FTP SERVER: ** ** dapsc.tgz ** ** ** ** NOTE: The Wind River FTP Server will not work with ** ** this script. ** ******************************************************** FTP Server IP --> 144.190.240.2 FTP Username --> apftp


Page-16

FTP Password --> apftp

6. Wait for the following text to appear. This indicates the codeload procedure is complete.

******************************************************** ******************************************************** ** SITE CONTROLLER FILESYSTEM CODELOAD COMPLETED ** ** Log File: /codeload.log ** ******************************************************** ********************************************************

7. At this point the Site Controller software should be updated. Reboot the Site Controller using the reboot command.

8. Unplug this site controller and proceed to all other controllers. If this is the last controller, proceed to the modem installs if necessary.


Page-17

Appendix B – Removed Appendix B has been removed This page intentionally left Blank.


Page-18

Appendix C – AP Diagnostics NOTE: The BCU will be taken out of service to run AP Diagnostics. When AP Diagnostics is completed, the controllers must be rebooted to bring the site back to active. 1. Connect to the serial port of the ACTIVE controller. 2. Verify all boards (redundant SC, alarm card, modem(s), power supplies) are installed in the BCU cage. 3. Log in as root. 4: Start the AP Diagnostics application “apdiag” in the /usr/app/bin directory.

root@unknown:/root> /usr/app/bin/apdiag

5: The BCU must be in “Test” mode to run AP Diagnostics. If it is not, apdiag will prompt the user to place the BCU in Test mode. To ensure a site is not inadvertently taken out of service, apdiag will ask the user to enter “1” twice before starting Test mode.

Motorola WiMAX AP Diagnostic Tool Copyright (C) 2006-2007 Motorola, Inc. WARNING: BCU is not in Test mode! Enter '1' to place the BCU in Test mode, or any other key to exit: 1 This will take the BCU out of service! If you're sure you want to continue, enter '1' or any other key to exit: 1 Please wait...

6: Once the BCU is in test mode, the Main Menu will appear. At this point, please allow the modems to finish booting (may take up to three minutes if the site was not previously commissioned). To enter the BCU diagnostics submenu, choose option “1”.

Motorola WiMAX AP Diagnostic Tool Copyright (C) 2006-2007 Motorola, Inc. ****** Main Menu ****** Choose from the following options: 1) BCU Diagnostics 2) Site Controller Diagnostics 3) Modem Diagnostics ?) Help E) Exit > 1

****** BCU Diagnostics Sub-menu ****** Choose from the following tests: 1) BCU Information 2) Site Initialization Procedure ?) Help E) Exit to Main Menu


Page-19

>

7: Type “2” to begin the Site Installation Procedure.

> 2 Running test, please wait...

During this procedure, verify the following: A. Verify all installed boards are listed as “PRESENT”:

FRU Status: ---------- Alarm Card: PRESENT Controller 1 (slot 2): PRESENT Controller 2 (slot 3): NOT Present Modem 1 (slot 4): PRESENT Modem 2 (slot 5): NOT Present Modem 3 (slot 6): NOT Present Modem 4 (slot 7): NOT Present Power Supply 1: PRESENT Power Supply 2: PRESENT Power Supply 3: PRESENT MSO: PRESENT

B. Verify none of the BCU alarms are “ALARMED”. If an alarm is triggered, resolve the condition (usually by replacing the applicable FRU). A Door Alarm can be expected if a BCU door is open.

BCU Alarms Status: ----------------- Power Supply 1 Voltage Alarm: Not Alarmed Power Supply 1 Temperature Alarm: Not Alarmed Power Supply 1 Input Alarm: Not Alarmed Power Supply 1 Output Alarm: Not Alarmed Power Supply 2 Voltage Alarm: Not Alarmed Power Supply 2 Temperature Alarm: Not Alarmed Power Supply 2 Input Alarm: Not Alarmed Power Supply 2 Output Alarm: Not Alarmed Power Supply 3 Voltage Alarm: Not Alarmed Power Supply 3 Temperature Alarm: Not Alarmed Power Supply 3 Input Alarm: Not Alarmed Power Supply 3 Output Alarm: Not Alarmed Customer Power Alarm: Not Alarmed GPS Power Alarm: Not Alarmed MSO Fault Alarm: Not Alarmed Relay 1 Alarm: Not Alarmed Relay 2 Alarm: Not Alarmed Cabinet Under-Temperature Alarm: Not Alarmed Cabinet Over-Temperature Alarm: Not Alarmed surge Alarm: Not Alarmed Door 1 Alarm: Not Alarmed Door 2 Alarm: Not Alarmed

C. Verify all GPSR self tests have “Passed”. If any of these test fail, replace the GPSR and re-run the test. In a lab setup, the Antenna Status may fail (due to an Under-Current alarm) if the GPS antenna is not connected directly to the GPSR.

GPSR Self Test Results: ----------------------


Page-20

Channel 1 Correlation: Passed Channel 2 Correlation: Passed Channel 3 Correlation: Passed Channel 4 Correlation: Passed Channel 5 Correlation: Passed Channel 6 Correlation: Passed Channel 7 Correlation: Passed Channel 8 Correlation: Passed Channel 9 Correlation: Passed Channel 10 Correlation: Passed Channel 11 Correlation: Passed Channel 12 Correlation: Passed Manuf. Data Checksum Status: Passed Oscillator Checksum Status: Passed Temp Sensor Checksum Status: Passed ROM Status: Passed RAM Status: Passed Temperature Sensor Status: Passed RTC Status: Passed Antenna Status: Passed

D. Verify satellite status.

Satellite Status: ---------------- Maximum visible satellites: 12 Channel Sat. ID Mode Signal IODE ------- ------- ---- ------ ---- 1 21 0 0 100 2 26 5 52 11 3 18 8 54 8 4 29 8 48 211 5 7 8 45 2 6 6 5 45 48 7 9 8 49 197 8 22 8 51 195 9 3 0 0 0 10 0 0 0 0 11 0 0 0 0 12 0 0 0 0

E. Verify the TCXO in each Site Controller is “Good”. If the TCXO has failed, the associated Site Controller will need to be replaced.

TCXO Status: ----------- Controller Slot TCXO Status ---------- ---- ----------- SC1 2 Good SC2 3 Good

F. For each modem, verify the FRU Part Number and Serial Number match the numbers that are located on the 2 tabs that lock the modems into the BCU. Then verify the correct RF Heads are listed as “Connected”: Perform this step for each modem.

Information for Modem 1: ----------------------- EID Information: --------------- Board Type: 0x0013, 0x0003 FRU Part Number: STLN6398GA FRU Serial Number: 170G6T04W0


Page-21

Description: WiMax Modem HAL Compatibility: {0x01, 0x01, 0x00} MAC Address: 00:E0:0C:F9:EB:58 MAC Mask: 0x0003 (4 addresses) Kit Number: STLN6398GA Kit Serial Number: 170G6T04W0 User Defined Field: Running test, please wait... RF Head Connection Status: ------------------------- RF Head 1 (Fiber Port A): Connected, Sector ID = 255, RF Head Type = Small (DAP) RF Head 2 (Fiber Port B): NOT connected RF Head 3 (Fiber Port C): NOT connected

G. Finally, for each connected RF Head, verify the communication connection has been established, and enter the correct sector ID (0-based) for the RF Head:

Connection to RF Head 1 on modem in slot 5 established! Changing Sector ID for RF Head 1, Modem 1 Enter Sector ID (0 to 3), or 'E' to leave unchanged: 2 Running test, please wait... RF Head successfully set to sector 2

8: If any test fails, re-run the test when the problem is fixed. Note that each test can be run individually. For example, to set a sector ID from the Main Menu, choose 3 for the Modem menu, enter the modem number, choose 2 for the RF Head Menu, enter 1 when prompted for an RF head number, then enter the sector ID as above. At any time, entering “?” will print a help screen. 9: Reboot the controllers when finished.


Page-22

ap site commissioning procedure

Documents

ap completes

local admin

fru part number

ftp server

manual software

select serial

manual software

ftp root directory