User guide

Release9.5ReleaseNotes



Issue2,October2009  Page38
4 KnownOpenIssues
Known open issues for Release 9.5 are listed in Table 7.
Table 7: Known open issues
Product Family
Description Discussion and Recommendations
All SM - DNS below a
NATed SM (R9.5)
Microsoft Vista and presumably Windows 7 will not route a
169.254/16 subnet used as the default Canopy subnet since
Microsoft uses 169.254/16 subnet to talk between local
machines. This is not an issue if:
- the PC is connected directly to the NATed SM.
- the NAT/routing CPE underneath the NATed SM
provides DNS services.
However; if a NAT/routing CPE that is not providing DNS
services (e.g. some home routers*) is placed between the SM
and the user’s PC, a Microsoft Vista and Windows 7 machine
will not route to the default 169.254/16 SM IP address space to
access DNS services.
Workaround: Reconfigure the SMs NAT LAN address to a
private IP address such as 192.168/16, 172.16/12, or 10/8.
* Please refer to home router manufacturer documentation to
determine if the router provides DNS services.
All Prizm 3.2 cannot
change LED Panel
Mode.
(9764)
Prizm 3.2 cannot set the LED Panel Mode to Revised Mode.
LEDs are in Legacy Mode by default.
Workaround: Set LED Panel Mode using the GUI.
PMP 100 Downlink
broadcast traffic
on FSK radios can
exhibit packet loss
(9492)
Broadcast Repeat Count on the AP’s Configuration => Radio
page should not be set to 0. Use either 1 or 2 repeats.
Workaround: When using applications such as broadcast video
that make significant use of downlink broadcast packets, set the
parameter to 1. Otherwise, in most cases, leave the parameter
set to the default of 2.
This issue has been resolved for OFDM radios, but can still
affect FSK radios running Release 9.4.2.