Thanks. This is the first thing I did. I am interested to know how I can monitor the number of collisions occuring on the access point.
I don't think you can get an exact value (sB, please correct me if I am wrong).
FailedPackets indicates the number of packets that the radio tried to send to a client, but were dropped due to excessive retries (the radio tried to send the packet 16(? the number of retries can't be configured, and I can't find the retry value in the documentation) times, but all of them failed). A high FailedPackets/TxUnicastPackets ratio is BAD.
AckFailure, FCSError and InvalidPLCP are included in the MIB, and you can see them by using ap-utils. http://ap-utils.polesye.net/ They are not shown by simpleMonitor, so I don't know how much to trust these values.
FCSError should indicate the number of packets that were received, but had an invalid CRC checksum (could be caused by collisions, bad signal strength, multipath, interference).
AckFailure should indicate the number of packets that were sent, but no corresponding ACKs were received (due to the receiver not hearing the packet, FCSError on the receiver or collision/corruption of the ACK packet).
InvalidPLCP should indicate the number of packets that were received, but the packet preamble/header was corrupted due to collisions, etc.
-- LarsG
ANNOUNCEMENT WISPCON IV - Can You Ping Me Now? Good! October 27-29, 2003 - Dallas Texas http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm
WISP 101 Boot Camp September 29-October 3, 2003 - Chicago, Illinois http://www.part-15.org/train/wisp/101.html
The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org
