User guide
Release9.5ReleaseNotes
Issue2,October2009 Page51
13. Initiate the Update operation.
14. Monitor the update progress through the Network Tree.
15. Allow the update to run, leaving CNUT/Prizm active, until all involved SMs are upgraded.
An AP enabled for Auto-update
a. updates all registered or registering P7/8/9 SMs that require an upgrade.
b. waits for 20 minutes of no upgrade or new P7/8/9 registration activity.
c. updates all registered or registering P10 SMs that require an upgrade.
d. waits for 20 minutes of no upgrade or new P10 registration activity.
e. updates all registered or registering P11 SMs that require an upgrade.
f. waits for 20 minutes of no upgrade or new P11 registration activity.
g. continues this cycle until Auto-update is disabled (using CNUT or Prizm) or until the
AP is rebooted.
With this algorithm, any SMs that are not properly upgraded are found by CNUT or Prizm
on a subsequent cycle and then successfully upgraded, without operator action.
There will be quiet times during a sector upgrade due to the 20-minute inactivity timer,
followed by active updating of SMs.
With CNUT 3.20 or Prizm 3.2, the operator can choose the update order among
P7/P8/P9 SMs, P10 SMs, and P11 SMs by setting the SM Autoupdate Configuration. For
example, sectors with no P7/8/9 SMs should be set to upgrade P10 SMs first and not
upgrade P7/P8/P9 SMs to avoid a 20 minute wait until upgrade of P10 SMs begins.
16. After the upgrade appears to have completed, Refresh/Discover.
17. Verify that the Software Version for each module is shown as CANOPY 9.5.
18. If any SM completed the software loading and then failed to reboot, or did reboot but
CNUT or Prizm displayed a message such as “Reboot failed” or
“Failed to find Element in update. Cannot open new telnet connection to device”, and if
the rest of the sector successfully upgraded and became stable on Release 9.5, perform
the following steps:
a. Refresh/Discover.
b. Check whether the resulting elements list shows the SM as operating on the new
release.
c. If it does not, reboot the problem SM.
d. Check whether the SM is shown as operating on Release 9.5.
e. If it is not, re-initiate the upgrade of the SM using CNUT or Prizm.
19. Disable SM Auto-update on CNUT or Prizm, according to CNUT help file or Prizm
documentation.
7.4.1 Settingthe RegionCode
After a sector or link or standalone module has been upgraded to Release 9.5, confirm that the
Region Code on each module is set to the local region. If needed, set the Region Code and
associated parameters correctly on each module, Save Changes, and Reboot.
On new APs or BHMs, or APs or BHMs that have been reset to factory defaults, the Region Code
must be set before the module will transmit.