User guide

Release 9.4.2 Release Notes
Issue 1, May 2009 Page 17
Table 7: Previous Notes
ID
Description
Discussion and Recommendations
-
Changes to
boxTemperature
OIDs
Starting with Release 9.4 the boxTemperature (1.3.6.1.4.1.161.19.3.3.1.5)
OID (which returned an octet string value) is no longer valid. Two new OIDS
which return integer values are added:
boxTemperatureC
Object ID: 1.3.6.1.4.1.161.19.3.3.1.35
Syntax: INTEGER
Access: read-only
Status: current
Radio temperature in Celsius.
boxTemperatureF
Object ID: 1.3.6.1.4.1.161.19.3.3.1.36
Syntax: INTEGER
Access: read-only
Status: current
Radio temperature in Fahrenheit.
-
More accurate
Received Power
readings for P10
900-MHz radios
For P10 900-MHz radios, Release 9.4 included improvements in the
accuracy of the displayed Received Power based on improvements in
temperature measurement. The displayed Received Power may be lower or
higher than for the same radio running a previous release. The actual
performance of the radio has not changed. With this accuracy improvement,
P10 900-MHz radios should see less variation of displayed Received Power
over time (as temperature changes) and from radio to radio.
8484
Procedures for
saving an XML file
of a spectrum
graph
When the SpectrumAnalysis.xml button is clicked on the SM’s Tools =>
Spectrum Analyzer page or the AP’s Tools => Remote Spectrum Analyzer
page, the spectrum graph is redisplayed using XML and XSL if the browser
supports XSL. To save the underlying XML file, right click and select “Save
Target As” on a Windows PC, or equivalent action for other operating
systems.
8172
SM scan
frequencies not
“cancelled” by
SNMP actions
If you make frequency changes on the SM GUI, and then back them out
using SNMP, the Reboot Required message remains on the GUI.
Workaround:
If it says Reboot Required, go ahead and reboot, just to clear the message.
8241
Avoid power
cycling modules
during upgrading
Power cycling a module while it is upgrading can cause anomalous events,
such as rebooting every time you try to access the GUI.
Recovery: Attempt to upgrade again. If CNUT reports the module as
upgraded and refuses to upgrade again, downgrade the module and then
upgrade it again.