User guide

Release 9.4.2 Release Notes
Issue 1, May 2009 Page 26
3. Add the appropriate .pkg3 file(s) to the managed packages list. Depending on the
package downloaded in section 7.3, Obtaining Upgrade Packages, you will have one or
more of the following .pkg3 files:
 CANOPY94_2BUILDOFFICIAL_DES.pkg3
 CANOPY94_2BUILDOFFICIAL_AES.pkg3
 CANOPY94_2BUILDOFFICIAL_OFDM_DES.pkg3
 CANOPY94_2BUILDOFFICIAL_OFDM_AES.pkg3
4. Consider rebooting APs on sectors you plan to update to eliminate any memory
fragmentation issues and ensure there is space to hold the new image.
5. Just before doing any updates, use Refresh/Discover to confirm that all SMs are active.
6. Choose the elements that you want to update at this time: a selection of elements,
a network branch, or the entire network. Most operators gain experience by upgrading
a portion of their network at a time, depending on network size and their own procedures.
7. Use Prizm or CNUT to confirm use of SM Auto-update, as appropriate. With SM Auto-
update, SMs are updated by their AP instead of by CNUT, which significantly reduces the
time needed for updating an entire network. In addition, SM Auto-update must be used to
update any SMs that have their Network Accessibility parameter set to Local, as these
SMs are not addressable by CNUT or Prizm over the network.
8. Initiate the Update operation.
9. Monitor the update progress through the Network Tree.
10. 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.12 or Prizm 3.1 with Patch 7, 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.
11. After the upgrade appears to have completed, Refresh/Discover.
12. Verify that the Software Version for each module is shown as CANOPY 9.4.2.
13. 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.4.2,
perform the following steps: