Redline Communications Inc. AN100UA 用户手册
Red
MAX
™
Base Station
User Manual
Doc. #70-00058-01-01
Proprietary Redline Communications © 2007
July 13, 2007
Page 98 of 119
- Same DL channel frequency as the UL channel frequency of this SC
- Same Cyclic Prefix
- Same channel size (i.e., 7 MHz)
If a long preamble was received, but no DL-Map was detected, the following message
will be entered into the event log:
will be entered into the event log:
WARNING: Unknown Interference was detected on the UL channel
This second message does not necessarily indicate interference from another base station,
and may be the result of cross-interference from subscribe stations.
and may be the result of cross-interference from subscribe stations.
7.7 Re-Ranging
Log
Message
The log message 're-ranging' is recorded by the base station when a registered subscriber
initiates a network entry sequence.
There are two common reasons for this event:
1. When network entry is complete, the subscriber retains its 'registered' state by
initiates a network entry sequence.
There are two common reasons for this event:
1. When network entry is complete, the subscriber retains its 'registered' state by
sending data traffic to the base station. When there is no data traffic, the SU-O sends
only periodic ranging requests each 25 seconds. Under no-traffic conditions, it may
take the base station more than 25 seconds to declare a subscriber unavailable and
mark it as de-registered. During the same 25 second period, the subscriber may
declare the base station to be unavailable (i.e., due to poor link conditions) and begin
attempts to re-register. In this scenario, the subscriber is attempting to re-register
before the base station has declared the subscriber to be failed.
only periodic ranging requests each 25 seconds. Under no-traffic conditions, it may
take the base station more than 25 seconds to declare a subscriber unavailable and
mark it as de-registered. During the same 25 second period, the subscriber may
declare the base station to be unavailable (i.e., due to poor link conditions) and begin
attempts to re-register. In this scenario, the subscriber is attempting to re-register
before the base station has declared the subscriber to be failed.
2. This condition may also result from a loss of connectivity between a subscriber and
the DHCP server or TOD server. When remote management is enabled on the
subscriber (managedSS=1), the subscriber must communicate with the DHCP server
and the ToD server specified in the obtained lease. If communication cannot be
established within two minutes, the subscriber will reset and repeat the attempt.
subscriber (managedSS=1), the subscriber must communicate with the DHCP server
and the ToD server specified in the obtained lease. If communication cannot be
established within two minutes, the subscriber will reset and repeat the attempt.
7.8
Troubleshooting the Web Interface
These troubleshooting steps assume that the status LEDs on the front panel of the
terminal indicates normal function.
1. Open a Web browser and attempt to login to the base station terminal. If the terminal
terminal indicates normal function.
1. Open a Web browser and attempt to login to the base station terminal. If the terminal
does not respond by displaying the login dialog box, check that the correct IP address
is being used. The factory default address is listed in the Troubleshooting section.
The IP address may have been changed during installation. For correct operation the
host computer and the terminal must appear to be on the same subnet. Ensure that the
IP address for the PC is set to the same subnet as the terminal. For example, the IP
address should only differ in the last octet (i.e., 192.168.101.X).
is being used. The factory default address is listed in the Troubleshooting section.
The IP address may have been changed during installation. For correct operation the
host computer and the terminal must appear to be on the same subnet. Ensure that the
IP address for the PC is set to the same subnet as the terminal. For example, the IP
address should only differ in the last octet (i.e., 192.168.101.X).
2. The next test is to verify the IP address is reachable from the computer. Use the ping
command to test the connection between the terminal and host computer. The system
always responds to ping frames less that 577 bytes in length.
always responds to ping frames less that 577 bytes in length.
If the ping test is successful the host computer was able to send and receive packets.
The problem may be with the Internet browser or related settings on the host
computer. Re-boot the host computer to try to resolve the problem.
The problem may be with the Internet browser or related settings on the host
computer. Re-boot the host computer to try to resolve the problem.