| Displaying Information About the Access Server |
|
|
Field | Description |
|
|
Send Failure Reasons | Mask providing information about the type or |
| types of send failure encountered if the Send |
| Failures counter is not zero. This is a |
| cumulative mask.The following are the bits |
| defined in the mask: |
| Bit |
| 0 |
| 1 |
| 4 |
| 5 |
| 8 |
| 9 |
| If a reason for send failures is heartbeat errors |
| and the access server characteristic |
| HEARTBEAT is enabled for a transceiver that |
| supports heartbeat, you can usually expect up |
| to about 200 such errors daily. This number |
| does not indicate a network problem. |
| If a reason for send failures is heartbeat errors |
| and the transceiver being used does not support |
| heartbeat, check to see whether you have |
| heartbeat enabled. The send failures count will |
| reflect the heartbeat errors generated from the |
| transceiver not responding to checks of its |
| heartbeat circuitry. Disable the access server |
| characteristic HEARTBEAT to eliminate the |
| spurious generation of heartbeat errors. |
Receive Failures | Number of packets that were received with an |
| error condition. For more information, refer to |
| the Receive Failure Reasons field. This counter |
| should be 0 or a low value such as 1 or 2 daily. |
|
|
Managing the Access Server