Reset Search



How to convert an RBT-4102 access point to work with a HiPath controller

« Go Back


TitleHow to convert an RBT-4102 access point to work with a HiPath controller
Upgrading an existing thin (RoamAbout Switch Solution) or thick (Stand Alone) RBT-4102 to be part of a solution. 
  • IdentiFi
  • RBT-4102
  • All firmware versions
* *Please note the process defined below is to move an RBT-4102 from Trapeze thin mode to HiPath thin mode. If the RBT-4102 is in stand alone mode\legacy mode, follow the code upgrade steps documented in the RBT-4102 user manuals using the HiPath image. Once the unit has been converted to the HiPath image it cannot be converted back to support Trapeze or stand alone mode\legacy mode.** 

The RBT-4102 access point conversion process is divided into four steps: 

1. Completing the prerequisites. 

2. Downloading the RBT-4102 HiPath image. 

3. Installing the RBT-4102 HiPath image on the RBT-4102 access point. 

4. Deploying the RBT-4102 HiPath access point to a HiPath Wireless Controller. 

Note: You must ensure the following prerequisites are satisfied before attempting to complete this conversion process. 

You need to know the IP address or have physical access to the deployed RBT-4102 access point that you want to convert. 

You need access to a network, which includes the following: 

DHCP server for IP assignment 
TFTP server to save your RBT-4102 HiPath image 
**HiPath Wireless Controller must be deployed and available for RBT-4102 access point discovery.** 

To download the RBT-4102 HiPath image, do the following: 

1. Take the access point down off the wall and power down the unit. 

2. Attach a console cable that is connected to a laptop to the comm port of the RBT-4102 access point and open any comm program. For example, use Hyperterm or Putty. 

3. Hold the reset button down for approximately 20-30 seconds.The reset button is located next to the network port. 

Eventually you will see the following message displayed in the comm session. 

CPU: Motorola MPC82xx ADS - HIP7 
Version: VxWorks5.5.1 
BSP version: 1.2/1 
Bootcode version: 1.0.5 
Creation date: Oct 13 2005, 22:48:22 
Press any key to stop auto-boot... 

boot device : fs 
unit number : 0 
processor number : 0 
host name : host 
file name : /fl/ets-img.bin 
flags (f) : 0x0 
fsLoad: Found boot image /fl/ets-img.bin! 
fsLoad: Size of boot image is 168371 
fsLoad: Successfully inflated image. 
Starting at 0x10000... 
GO 0 entry_addr 10C00000 .... 
AP Boot Loader version 29 
Stage 1 boot code build 
access point startup 
Enabled MAC 
created thread for boot code code delete 
entered boot code code delete 
AP Reset: Reverting boot code 

4. Once you see the above message AP Reset: Reverting boot code, release the RBT-4102 access point reset button. 

The RBT-4102 access point reboots and is assigned an IP address by the network DHCP server. If a DHCP server is not available, the RBT-4102 access point reboots to its default IP address, 

5. Open your Web browser and go to:
and download the RBT-4102 HiPath image.  An upgraded RBT-4102 AP is expected to be sufficiently compatible with a controller running firmware as high as 8.x, so that the controller can then push its latest thin image to the AP (explained in more detail below). 

6. Unzip the file, and save it to a TFTP server. 

7. You can install the RBT-4102 HiPath image using the RBT-4102 access point Web GUI or CLI commands. 

Using the RBT-4102 Access Point Web GUI (Thick Stand Alone mode) 

1. Connect the RBT-4102 access point to your network. 

2. Open your Web browser and type the RBT-4102 access point’s IP address in the address bar. For example, 

3. Log on to the RBT-4102 access point with the credentials admin and password. 

4. Navigate to the local upgrade option via the Administration option, and browse to the RBT-4102 HiPath image you downloaded. 

5. Upgrade the RBT-4102 access point with the RBT-4102 HiPath image.The RBT-4102 access point reboots once it has completed. 

**If the discovery process initially fails to the HiPath controller, the RBT-4102 access point continues to run its discovery process. If after 5 minutes the RBT-4102 access point continues to fail in its discovery process, the RBT-4102 access point returns back to its stand alone mode. If this occurs, you must start the conversion process from the beginning.**
Additional notes

Using CLI Commands 

1. Connect the RBT-4102 access point to your network. 

2. Connect to the RBT-4102 access point console by using the serial port, or remotely by telnet or SSH if you know the RBT-4102 access point’s IP address. 

3. Log on to the RBT-4102 access point with the credentials admin and password. 

4. Use the following command to copy the HiPath image on to the RBT-4102 access point. 

RoamAbout 4102#copy tftp file 

The following message is displayed: 

1. Application image 
2. Config file 
3. Boot block image 
Select the type of download<1,2,3>: 

5. Type 1 to select the image file and then type the image file and TFTP server information. For example: 
TFTP Source file name:AP4102-V6R0.90013.22.img 
TFTP Server IP: 

The following message is displayed if the copy command was successful: 
Please wait... 
Firmware version of system is V1.1.51 and Updating Run-Time code v01.02.20 NOW! 
This firmware is compatible with hardware. 
The software was properly copied over to the system and a reset is needed in order for the 
software changes to take place. 
RoamAbout 4102#reset board 
Reboot system now? <y n>: 

6. Type y to reboot the RBT-4102 access point. 

7. If you are connected to the RBT-4102 access point via the console, capture the conversion log. The conversion log will help to troubleshoot an unsuccessful conversion attempt if the system fails to load the image. 

If the conversion was successful, when the RBT-4102 access point reboots it automatically begins the discovery process to determine its own IP address and the IP address of the HiPath Wireless Controller. When the discovery process is successful, the RBT-4102 access point registers with the HiPath Wireless Controller. 

The RBT-4102 access point is now ready for deployment and configuration.



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255