Upgrading AP
Firmware From Cloud Base

The following
procedure enables bulk APs (that have established IPsec tunnel) to contact the
CloudBase. This is achieved by issuing the Factory Recovery from Cisco RMS to
the bulk devices and thus upgrading the bulk APs to the latest Firmware.

Run
massFactoryRestore.sh to trigger factory recovery for
the list of EIDs mentioned in the previous step. For information on how to
execute
massFactoryRestore.sh, see the
Cisco RAN Management System Administration Guide.

Run
GetDeviceData.sh (see the
Cisco RAN Management System Administration Guide) to
find list of APs mentioned in the CloudBaseUpgradeEID.txt that have been
upgraded with the latest firmware.

Note

If APs have
not contacted RMS then the firmware of these APs may not show the latest
version.

Single APs can also be
upgraded to the latest firmware from the CloudBase. To perform an upgrade,
initiate factory recovery from DCC UI for individual APs. For more information,
see "Resetting a Device" section in the
Cisco RAN Management System Administration Guide.

Upgrading AP
Firmware From RMS

The following
procedure enables single or bulk APs (that have established IPsec tunnel) to
download firmware files from RMS, thereby, upgrading the single or bulk APs to
the latest firmware.

Save the available firmware files to your desktop or machine that
is used to access the BAC UI. Save the files in the format <AP Software
Version>_<filename>. For example, if AP needs to upgrade to software
version BV3.5.11.5, then save the five files in the format given below.

BV3.5.11.5_SCF.sig

BV3.5.11.5_SCF.xml

BV3.5.11.5_rootfs.bin

BV3.5.11.5_standard-kernel.bin

BV3.5.11.5_ubiqfs.bin

Step 3

Log in to the BAC UI using 'bacadmin' credentials.

Example:

https://<CentralNode _eth1_IPAddress>/adminui/

Select the
Configuration option on the BAC UI landing page.

Click the
Files tab.

In the Files tab, click
Add to open the Add Files page.

From the File Type drop-down list, select the
Firmware File.

Click
Browse to browse and select the firmware file saved
locally as described in Step 2. For example, BV3.5.11.5_SCF.sig.

Enter the File Name of the file selected in the previous step.
The filename should reflect the selected firmware file name. For example,
BV3.5.11.5_SCF.sig.

Step 4

Repeat Step 3 for the remaining four files: BV3.5.11.5_SCF.xml,
BV3.5.11.5_rootfs.bin, BV3.5.11.5_standard-kernel.bin, and
BV3.5.11.5_ubiqfs.bin.

Initiating Firmware Upgrade on Individual or Bulk FAPs

The following procedures describe
how to Initiate firmware upgrade on individual or bulk of FAPs in a controlled
manner to ensure that the system is not overloaded.

Note

Ensure that the firmware upgrade related custom properties are not
enabled at any Group, Class of Service, Provisioning Group, and CWMP Defaults
level.

Initiating Firmware
Upgrade on Individual FAPs

Post the update API
xml from the OSS to initiate firmware upgrade on a single FAP. This sets the
firmware upgrade related custom properties at the device level on the BAC and
initiates the connection request on the device. On receiving the connection
request from the device, BAC initiates the firmware download by comparing the
software version of FAP on the device with the properties set via xml. Sample
xml is shown below:

For any device if
the connection request fails, firmware upgrade is initiated on that device
after it connects with an inform having 0 BOOTSTRAP/1 BOOT/2 PERIODIC/6
CONNECTION REQUEST event codes.

Initiating Firmware
Upgrade on Bulk FAPs

Continuously post
the xml given in
Initiating Firmware Upgrade on Individual FAPs
to initiate bulk AP upgrades for a selected set of a devices at a uniform rate
of two per second from the OSS for the allowed number of hours in the day. Use
the
GetDeviceData script to monitor the status of the
firmware upgrade and analyze the GetDeviceData report for device software
versions at the end of the day.

Ensure that there is
at least an hour gap after the firmware upgrade initiation and firmware upgrade
completion before running the
GetDeviceData script.

Note

Until the
firmware upgrade gets disabled (as mentioned in
Disabling Firmware Upgrade on Individual or Bulk FAPs),
if any FAP (for which firmware upgrade custom properties are set in BAC) gets a
different firmware version from CloudBase after Factory Recovery, then its
firmware version changes based on the settings provided at the device level on
BAC (when it contacts RMS).

Disabling Firmware
Upgrade on Individual or Bulk FAPs

The following procedures describe
how to disable firmware upgrade on individual or bulk of FAPs in a controlled
manner to ensure that the system is not overloaded.

Disabling Firmware
Upgrade on Individual FAPs

Post the update API
xml from the OSS to disable firmware upgrade on a single FAP (after it is moved
to the intended software) to remove firmware upgrade related custom properties
at the device level on the BAC. Sample xml is shown below

Irrespective of
the connection request status on the device, firmware upgrade is disabled on
the device when the corresponding custom properties are removed from the device
level on the BAC.

Disabling Firmware
Upgrade on Bulk FAPs

Continuously post
the xml given in
Disabling Firmware Upgrade on Individual FAPs
to disable firmware upgrades (after the upgrade is completed on a selected set
of devices) on bulk of APs for a selected set of a devices at a uniform rate of
two per second from the OSS for the allowed number of hours in the day.

Upgrading AP
Firmware Post RMS 5.1 MR Hotfix Installation

The older LTE FAP firmware is not compatible with the RMS 5.1 MR
hotfix software. Therefore, immediately after installing the hotfix, upgrade
the LTE FAP firmware. This includes adding the firmware images to RMS and
setting the firmware properties.

The following firmware files are required to perform the LTE AP
software upgrade:

Save the
available firmware files to your desktop or machine that is used to access the
BAC UI. Save the files in the format <AP Software
Version>_<filename>. For example, if AP needs to upgrade to software
version DSV4.0.6T.130116, then save the five files in the format given below.

DSV4.0.6T.130116_SCF.sig

DSV4.0.6T.130116_SCF.xml

DSV4.0.6T.130116_rootfs.bin

DSV4.0.6T.130116_standard-kernel.bin

DSV4.0.6T.130116_ubiqfs.bin

Step 3

Log in to the
BAC UI using 'bacadmin' credentials.

Example:

https://<CentralNode _eth1_IPAddress>/adminui/

Select the
Configuration tab on the BAC UI landing page.

Click the
Files
tab.

In the Files
tab, click
Add to
open the Add Files page.

From the
File Type drop-down list, select the
Firmware
File.

Click
Browse
to browse and select the firmware file saved locally as described in Step 2.
For example, DSV4.0.6T.130116_SCF.sig.

Enter the
Filename of the file selected in the previous step. The filename should reflect
the selected firmware file name. For example, DSV4.0.6T.130116_SCF.sig.

Step 4

Repeat Step 3
for the remaining four files: DSV4.0.6T.130116_SCF.xml,
DSV4.0.6T.130116_standard-kernel.bin, DSV4.0.6T.130116_rootfs.bin and
DSV4.0.6T.130116_ubiqfs.bin.

Enabling Firmware
Upgrade Properties

Procedure

Step 1

Log in to the
BAC UI using 'bacadmin' credentials.

Example:

https://<CentralNode _eth1_IPAddress>/adminui/

Step 2

Remove the
firmware-related properties, if any present, for specific devices:

Select the
Devices tab on the BAC UI landing page.

Click on
the device ID to view the list of device properties in the Modify Device page.

Click
Delete against the property name that is
to be deleted.

Click
Submit.

Repeat
steps 2a to 2d for all those devices that has firmware related properties at
the device level.

Similarly,
remove the properties present at any group level.

Step 3

Update the
firmware properties at the Class of Service (CoS) level.

Select the
Configuration tab on the BAC UI landing page.

Click on
'activated-DSV4.0.0T.0 ' CoS to view the list of CoS properties in the Modify
Class of Service page.

Click
Delete against the
'FIRMWARE-UPGRADE-LTE-ENABLE' property, which has the 'false' value.

In the same
Modify Class of Service page, add the following properties and values:

FIRMWARE-UPGRADE-LTE-ENABLE = true

FIRMWARE-UPGRADE-LTE-VERSION = DSV4.0.6T.130116

FIRMWARE-UPGRADE-LTE-IMAGE = DSV4.0.6T.130116_SCF.xml

Click
Submit.

Repeat
steps 3a to 3e for the 'baseline-DSV4.0.0T.0 ' CoS.

Initiating Firmware
Upgrade on Bulk LTE FAPs

Note

It is not mandatory to initiate and verify firmware upgrade in the
maintenance window. The AP can download firmware upgrade when it contacts RMS.

This file
must contain only the above two CoS values. For more details on triggering mass
connection requests, refer to the "massCr.sh" section of the "Operational
Tools" chapter in the
Cisco RAN
Management System Administration Guide.

This file
must contain only the above two CoS values. For more details on get device
data, refer to the "getDeviceData.sh" section of the "Operational Tools"
chapter in the
Cisco RAN
Management System Administration Guide.

Ensure that
there are no errors as shown (see bold text) in the example.

Step 5

Open the
'device-data.csv' file from the output directory (as
highlighted in the example in the previous step) and verify that the software
version of all the LTE FAPs are matching and should be 'DSV4.0.6T.130116'.

RMS Installation
Sanity Check

Note

Verify that there are no install related errors or exceptions in the
ova-first-boot.log present in "/root" directory. Proceed with the following
procedures only after confirming from the logs that the installation of all the
RMS nodes is successful.

Post RMS 5.1
Upgrade Tasks

Run the reassign
Opstool on the Central node as ciscorms user to associate the existing EIDs
with the new groups:

Note

The following
reassignment should be performed for a set of 50,000 FAPs in each maintenance
window.