User's Manual

F–2
PacketMax 100 User Manual, 10007306, Rev J
Chapter F. Troubleshooting
F.2 Booting SS from network
Symptoms
SS does not come up during installation of AIM. This happens when the installation
process in on the last screen of AIM, which has the CINR and RSSI graph. AIM
reports that SS is not connected and you will see that your Ethernet link of PC is
going up and down continuously. After that you cannot telnet to SS IP Address. There
will be no long beep for ARM1 bootup.
Resolution
This usually happens because AIM tool tries to write the value of frequency and other
parameters, that the user has configured, into NVRAM. While writing to NVRAM if
there is some weak signal received, than ARM1 causes MPI error and that results in
ARM0 also being rebooted. If ARM0 is in middle of writing parameters to NVRAM and
ARM1 made ARM0 reboot itself, than NVRAM gets corrupted. Also the bootline on
SS is corrupted and it falls back to default bootline, which is to boot from network. To
restore bootline back to original values, follow the procedure as below:
1. Connect the Ethernet port of your laptop to the SS using a crossover cable.
2. Change the IP address of your Ethernet card to 192.168.2.55.
To achieve this, follow the instructions below :
a. Double click on the Network Connections icon in the control panel.
b. Double click on Network card to which SS is connected and a screen as
displayed in
Figure F-1 appears.
SS cannot register all its
service flow.
If the number of SSs registering
exceeds the number of supported SSs
configure in the BS.
Move the SS to another sector.
If the SS’s configuration file specifies a
larger number of Classifiers.
Reduce number of Classifiers.
The SS’s configuration file specifies
Service Flows for which the BS does
not have any reserved bandwidth.
Install more capacity or move the SS to
another sector.