User Guide
Table Of Contents
- Revision History
- PLEASE READ THESE SAFETY PRECAUTIONS!
- Document Overview
- AB-Access Overview
- AB-Access
- RF Design and Planning
- Static Configurations
- CLIP_T
- CLIP_S
- Hybrid CLIP_S
- 1483_T
- 1483_S
- Native ATM
- Extender
AB-Access Config & User Guide 5.5 Axxcelera Broadband Wireless
July 27, 2004 Company Confidential Page 16 of 129
You can send individual files from DOS or LINUX; unlike the upgrade scripts. The reason
for this is that the upgrade script is using expect scripting and can only be run from a Unix based OS.
One note about the rupee-dos is that it can only be run be a true DOS based OS (Win95 or Win98 not
NT). NT uses a Virtual DOS Machine (NTVDM) and will not work with the rupee-dos command.
WARNING
If you rupee a file or files to a unit and do not reboot the unit, and
then rupee another file or files to the unit only the last set of files will
be saved to the flash.
4.6.1
LINUX
1. Make sure you can ping the unit that you want to send files to.
2. Change to the directory that the configuration files are in. The rupee-unix file must
also reside in this directory.
3. To upload individual files:
./rupee-unix –p atmos –d 2 –r <IP Address> <file> <file>
Note: You might have to change the permissions on the rupee-unix
command using “chmod”
chmod +x ./rupee-unix
4.6.2
DOS
1. Make sure you can ping the unit that you want to send files to.
2. Change to the directory that the configuration files are in. The rupee-unix file must
also reside in this directory.
3. To upload individual files:
rupee-dos –p atmos –d 2 –r <IP Address> <file> <file>
4.6.3
Rupee Option Definitions
-p <passwd> Specifies the password to use to allow write access to the AP/SU.
-d 2 Display debug level 2. Allows you to see what is being sent to the
unit.