Chapter 3: Operation System information
Page
3-27
Re- Registration
Requests
When a SM/BHS makes a Registration Request, the AP/BHM checks its local
session database to see whether it was registered earlier. If the AP/BHM
concludes that the SM/BHS is currently in session database, then the request
increments the value of this field.
Typically, a Re-Registration Requests is the case where both:
• SM/BHS attempts to reregister for having lost communication with the
AP/BHM.
• AP/BHM has not yet observed the link to the SM/BHS as being down.
It is possible for a small period of time if there is no downlink traffic and
AP/BHM still assumes the session is up, but the SM/BHS, loses session and
quickly re-connects before the AP/BHM knew the session had dropped. This
is how a re-registration happens.
If the number of sessions is significantly greater than the number for other
SMs or BHS, then this may indicate a link problem (check mounting,
alignment, receive power levels) or an interference problem (conduct a
spectrum scan).
CC Priority The field displays Color Code Priority (ICC, Primary, Secondary or Tertiary)
of all connected SM.
AirDelay
This field displays the distance of the SM/BHS from the AP/BHM in meters,
nanoseconds and bits. At close distances, the value in this field is unreliable.
PPPoE state This field displays the current PPPoE state (whether configured) of the
SM/BHS.
Timeout
This field displays the timeout in seconds for management sessions via
HTTP, ftp access to the SM/BHS. 0 indicates that no limit is imposed.
Power tab
Table 122 Power tab attributes
To Next Page
Loading...
Need help?
General
