User guide
Release9.5ReleaseNotes
Issue2,October2009 Page33
3 ResolvedIssues
Issues resolved in Release 9.5 are listed in Table 6.
Table 6: Issues resolved in Release 9.5
Ref #
Description Explanation
11590 PMP 400 and
PTP 200 OFDM
potential radio
communication
failure
Due to an issue in previous releases, PMP 400 and PTP 200 OFDM
modules have a potential to drop the radio communication link (appear to
fail) as they age.
This issue does not affect PMP 100 and PTP 200 FSK modules.
10402 NTP Event Log
Beginning with Release 9.4, new PermLogs were added for the NTP client
to notify the user of reasons why the time may not have been updated via
NTP. These logs were put into the radio Event Log. Customers reported
that the event log was filling up with messages.
Starting with Release 9.5, these event logs have been moved to the
Configuration => Time page on the AP under NTP Update Log.
The new OID to retrieve this log via SNMP is:
Name: ntpLogSNMP
OID: 1.3.6.1.4.1.161.19.3.1.7.33
Description: EventString
The NTP Update Log will show the last 20 events for NTP time updates.
NTP will try to update the time every 5 minutes.
11147 AP SNMP
Queries impact
VoIP traffic
In prior releases, somewhat degraded VoIP performance could be
observed while simultaneously running SNMP queries.
This is resolved in Release 9.5.
9798 Ranging issues
at maximum
settings
(Applies to 4.9 &
5.4GHz OFDM –
PMP 49400 and
54400)
Some ranging issues have been resolved.
Previously, due to occasional ranging issues at higher settings, a sector
configured for a Max Range of 11 miles or greater should have
its Downlink Data set no higher than 80%. Max Range and Data
Downlink are set on the AP's Configuration => Radio page.
Sectors configured for a Max Range of 10 miles or less were not affected
by this limitation.
9711 ARP table shows
00-00-00-00-00-
00 for the NAT
WAN interface
The SM’s Statistics => ARP page shows the correct physical address for
the IP address as shown in the Public RF NAT Table further down on the
page.