The following is tentative information that I was able to gather about the undocumented   1.3.6.1.4.1.762.2.5.*   MIB variables used in Lucent-powered wireless access points like the Apple Airport and Lucent RG1000. These variables are used in wireless link testing; the procedure for this is outlined below, identifying the role of 27 of the variables in this group. I’ve used these successfully in constructing a link-test Java application.

Wireless Link Testing

Wireless link testing seems to require several steps:

1. Set the following OID’s to the specified values:
• Set value to 50:
  • 1.3.6.1.4.1.762.2.5.5.1
  • 1.3.6.1.4.1.762.2.5.5.2
  • 1.3.6.1.4.1.762.2.5.5.3
• Set value to 3:
  • 1.3.6.1.4.1.762.2.5.4.1
  • 1.3.6.1.4.1.762.2.5.4.2
  • 1.3.6.1.4.1.762.2.5.4.3

I don’t know what these values represent, but the following stuff won’t work if these sets are not done…. Note that this and the other “sets” below require that the SNMP read/write community name (“password”) be used.

2. Retrieve the value of OID  1.3.6.1.4.1.762.2.5.1.0;  this gives the number of wireless hosts known to the access point. I’ve found this to be somewhat glitchy, at least with the Apple Airport Base Station: it often takes a number of tries before the value returned is the actual number of hosts (a value of 0 being returned in the interim).
3. Determine which index corresponds to which host by retrieving the value of some of the following OID’s:

 

1.3.6.1.4.1.762.2.5.2.1.3.n	Wireless host name
1.3.6.1.4.1.762.2.5.2.1.11.n	Wireless host MAC address

In the above,  n  is one of the indices from 1 to the number of hosts retrieved in the previous step. Use this information to select the wireless host whose link is to be tested. (Note, however, that I’ve seen the index value / host mapping change between retrievals…  not sure why…) Interestingly, this permits testing of any of the wireless links, not just the one corresponding to the host doing the SNMP queries. In fact, this can be done from any host, even one that’s not part of the wireless network.

4. For the selected host index  n,  set the values of the following MIB’s:

 

OID	Value	Meaning
1.3.6.1.4.1.762.2.5.2.1.27.n	1500	Packet size?
1.3.6.1.4.1.762.2.5.2.1.26.n	25	?
1.3.6.1.4.1.762.2.5.2.1.25.n	88	Number of packets to send?

This sets the value of parameters for link test polling, which begins as soon as the last parameter (number of packets?) is set.

5. Read the values of the following OID’s to retrieve statistics about the link quality polling. In the following, “local” refers to the base station, while “remote” refers to the wireless host on the link being tested. (I _think_ this is correct, but I might have it backward…)

 

Local signal strength, current	1.3.6.1.4.1.762.2.5.2.1.32.n
Local signal strength, minimum	1.3.6.1.4.1.762.2.5.2.1.36.n
Local signal strength, maximum	1.3.6.1.4.1.762.2.5.2.1.40.n
Local noise strength, current	1.3.6.1.4.1.762.2.5.2.1.33.n
Local noise strength, minimum	1.3.6.1.4.1.762.2.5.2.1.37.n
Local noise strength, maximum	1.3.6.1.4.1.762.2.5.2.1.41.n
Local signal-to-noise ratio, current	1.3.6.1.4.1.762.2.5.2.1.35.n
Local signal-to-noise ratio, minimum	1.3.6.1.4.1.762.2.5.2.1.39.n
Local signal-to-noise ratio, maximum	1.3.6.1.4.1.762.2.5.2.1.43.n
Local packets received successfully (?)	1.3.6.1.4.1.762.2.5.2.1.30.n
Local packets received total	1.3.6.1.4.1.762.2.5.2.1.31.n
Remote signal strength, current	1.3.6.1.4.1.762.2.5.2.1.44.n
Remote signal strength, minimum	1.3.6.1.4.1.762.2.5.2.1.48.n
Remote signal strength, maximum	1.3.6.1.4.1.762.2.5.2.1.52.n
Remote noise strength, current	1.3.6.1.4.1.762.2.5.2.1.45.n
Remote noise strength, minimum	1.3.6.1.4.1.762.2.5.2.1.49.n
Remote noise strength, maximum	1.3.6.1.4.1.762.2.5.2.1.53.n
Remote signal-to-noise ratio, current	1.3.6.1.4.1.762.2.5.2.1.47.n
Remote signal-to-noise ratio, minimum	1.3.6.1.4.1.762.2.5.2.1.51.n
Remote signal-to-noise ratio, maximum	1.3.6.1.4.1.762.2.5.2.1.55.n
Remote packets received successfully (?)	1.3.6.1.4.1.762.2.5.2.1.28.n
Remote packets received total	1.3.6.1.4.1.762.2.5.2.1.29.n

To do repetitive testing, repeat steps 4 and 5; when finished testing, set the value of OID  1.3.6.1.4.1.762.2.5.2.1.25.n  to  0.