User guide

Release9.5ReleaseNotes



Issue2,October2009  Page41
ID Description Discussion and Recommendations
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.
None Managing module
accounts and
passwords
The best security practice is to be aware the unit starts with root and
admin accounts, to plan your approach to accounts, and set passwords for
all accounts.
A module that either is fresh from the factory or has been operator-reset to
factory defaults has two user accounts: root and admin, both with
ADMINISTRATOR level permissions.
To secure a module, access the Account => Change Users Password tab
and add a password to each of these accounts. Adding a password to only
one account still leaves the other open. Furthermore, an account without a
password will accept any password potentially giving the impression the unit
is protected when it isn’t.
Alternatively, an operator’s practices may be to delete the admin account or
delete the root account and replace them with their own account(s). By
default Prism and CNUT use the root account to manage the module, so if
you delete root accounts on modules you will need to make coordinated
changes to Prizm and CNUT to access them with your own accounts.
7808 Use up to 16
alphanumeric
characters in user
account names,
passwords, and
Community
Strings
SNMP doesn’t do data-entry checking, so more than 16 characters may be
entered, but only 16 characters will be saved and displayed.
You can set Community Strings that include characters like
~`!@#$%^&;*()_+[]{}|;:,./<>? from the GUI, but SNMP only accepts
alphanumeric characters and SNMP get or set commands will return errors.
7442 Timed Spectrum
Analyzer settings
anomaly
Values of Timed Spectrum Analyzer duration and Spectrum Analysis on
Boot get saved by clicking any button on the page, not just when clicking
Save Changes or Start Time Spectrum Analysis (which is typical
operation for other pages).
None Best Practice is to
set SM to same
Region Code as
AP
When an SM registers to an AP, it assumes the Region Code and
associated parameters of the AP, disregarding any Region code set in the
SM by you. However, the best practice is still for you to set a Region Code
in the SM so that displayed options are consistent with the region.
4831 Details on pinging
Canopy modules
A ping size larger than 1494 Bytes to a Canopy module times out and fails.
However, a ping of this size or larger to a system that is behind a Canopy
module typically succeeds. It is generally advisable to ping such a system,
since Canopy handles that ping with the same priority as is given all other
transport traffic. The results are unaffected by ping size and by the load on
the Canopy module that brokers this traffic.
5298 AP may be listed
twice in AP
Evaluation tab
To help during aiming, the Tools => AP Evaluation tab maintains AP entries
for 15 minutes. If the frequency of an AP is changed, for 15 minutes the AP
is listed twice in the AP Evaluation tab, once with the former frequency, and
once with the new.