User guide

Managing Your Canopy Network March 2005
Through Software Release 6.1
Issue 1 Page 291 of 425
Canopy System User Guide
Table 48: Upgradability from previous software releases
A module can be directly upgraded
1
from… to…
System
Release
with FPGA
Version
and Boot
Version
System
Release
with FPGA
Version
and Boot
Version
2
121401a7 1.0
Nahum (SP3)
091102xx
3
1.0
3.2.5 091102xx 1.0
121401a7 1.0
3.n.n
091102xx 1.0
4.2.3 091102xx 1.0
4.0.n
4
062403xx 1.1 4.2.3
062403xx (DES)
041403xx (AES)
2.7
4.1.n 062403xx 1.1
4.2.3
062403xx (DES)
041403xx (AES)
2.7
4.2.7 051104xx 3.0
4.2.7 082504xx 3.0
6.0
5
092904xx 3.0
6.1
6
[various] 3.0
NOTES:
1. An upgrade to a particular release may require a unique procedural sequence that depends on
what release the module is being upgraded from.
2. Before an upgrade of system release or FPGA version in any module whose boot block is
Version 2.5, you must upgrade the boot block to Version 2.7.
3. xx indicates any two characters.
4. Do not use the SM Auto-update feature (manually or with the Canopy Network Updater
Tool [CNUT]) to upgrade from Release 4.0.n to Release 4.2. CNUT and SM Auto-update
require Release 4.1 or later.
5. This system release is dedicated to only the 900-MHz AP and SM.
6. Upgrade to Release 6.1 requires CNUT.
21.2.3 System Release 6.1 Compatibility
If you deploy Canopy System Release 6.1, observe the following caveats:
◦ If you implement VLAN
− first upgrade the AP and all SMs in the sector to Release 6.1.
− you do not require VLAN-aware end stations (the SMs are VLAN aware), but
you likely require a VLAN switch in your network.