Not supported by SBC SWe Lite in this release.
This article describes the steps necessary to apply ASM Roll-up updates on SBC 1000/2000 nodes with System Release 2.2.x or higher.
In this section:
SBC security patches and software updates protect your ASM from vulnerability to malicious viruses and security threats. To keep your ASM up-to-date, do the following:
Depending on the size of the update and the number of updates being installed, the reboot may take several minutes and possibly up to an hour.
Ribbon publishes Update Packs on a regular basis through the Ribbon Support Portal. The Update Packs work with Windows Update and other Non-Windows updates in order to keep the ASM up-to-date. The Update Packs contain a list of tested and authorized Windows updates, or specific installation packages such as Lync Cumulative Updates.
There are two methods of updating the ASM:
The ASM needs to have access to the Internet and specifically to the Microsoft Windows Support website.
As the SBC 1k/2k ASM employs Microsoft's Windows Server operating system, it is necessary to periodically download Windows Updates. Updates are normally downloaded directly to the ASM from the Microsoft Windows Update website. In some cases, the ASM may be installed in a network that does not have Internet access to Microsoft's Windows Update website, therefore the ASM requires an alternative method to download Windows Updates. For more information, see Installing a WSUS.
Two types of ASM Roll-up Update .pkg files are provided and they include the following:
Package | File Examples |
---|---|
Windows Update Includes:
| ASM-ROLL-UP-UPDATES_2019-05.zip |
MS Lync Server Cumulative Updates Includes:
| ASM-UPDATES-LYNC2013_CU1-Apr2016_UX1k2k-release3.0.x-and-later.zip ASM-UPDATES-LYNC2013_CU1-9_UX1k2k-release2.2.x.zip |
You must install the Microsoft Cumulative Update on your main server before applying the CU on the SBA.
In the left navigation pane, go to Application Solution Module > Install ASM Update.
Browse to the roll-up (.pkg) file.
Select ASM Update (.pkg file)
Click OK. The installation begins and the Progress bar reflects the upload progress.
The ASM Update installation sequence is shown below:
ASM Installation Progress - Step 1
ASM Installation Progress - Step 2
ASM Installation Progress - Step 3
After a successful upload of a windows update .pkg file, the Update State field in the Windows Update panel changes to Updates Available - Install.
Once the .pkg file is uploaded to the node, the Operational Status pane, the Update State field changes to Updates Available - Install.
To install the updates:
In the WebUI, click the Tasks tab.
In the left navigation pane, go to Application Solution Module > Operational Status.
Operational Status
If required, click Restart ASM Now (this is not always required). A reboot may or may not be required. This button will appear only if a reboot is required.
The Windows Update installation sequence is shown below:
Depending on the size of the update, the reboot may take several minutes.
Windows Update - Step 1
Windows Update - Step 2
Windows Update - Step 3
Windows Update - Step 4
Windows Update - Step 5
Windows Update - Step 6
Windows Update - Step 7
Windows Update - Step 8
Wndows Update - Step 9
Windows Update - Step 10
Field Name | Description |
---|---|
Most Current Roll-Up | Specifies the latest Ribbon Package applied on the ASM. |
Update State | Specifies the state of the Windows Update System. |
Restart Required | Specifies the need to restart Windows to finalize an action executed on the ASM. |
Additional Info | Specifies more information about the update status (such as, number of updates available or failure details). |
This section describes the requirements and procedure for installing ASM Updates using the REST interface.
curl.exe --cookie PHPSESSID=$PHPSESSID -k -i https://134.56.226.215/rest/sbaconfig?action=sbaupgrade -F sbaInstallFilename=@ASM_Rollup_2014-01.pkg
<?xml version="1.0"?><root> <status> <http_code>200</http_code> </status> </root>
$url = "https://134.56.226.215/rest/sbaactionstatus" Invoke-RestMethod -Uri $url -Method GET -WebSession $MyPs <?xml version="1.0"?> <root> <status> <http_code>200</http_code> </status> <sbaactionstatus href="https://134.56.226.215/rest/sbaactionstatus"> <rt_Success>1</rt_Success> <rt_ActionType>15</rt_ActionType> <rt_PercentComplete>100</rt_PercentComplete> <rt_Duration>0</rt_Duration> <rt_StatusText>updates installed</rt_StatusText> <rt_AllActionsBitmap>127</rt_AllActionsBitmap> <rt_ActionStartTime>0</rt_ActionStartTime> </sbaactionstatus> </root>
Query
$url = "https://134.56.226.215/rest/sbaconfig" Invoke-RestMethod -Uri $url -Method GET -WebSession $ps
Response
<?xml version="1.0"?> <root> <status> <http_code>200</http_code> </status> <sbaconfig href="https://192.168.123.53/rest/sbaconfig"> <AclEnable>1</AclEnable> <DHCPEnabled>0</DHCPEnabled> . . . <rt_UpdateState>1</rt_UpdateState> . . <VersionNumber>101</VersionNumber> </sbaconfig> </root>
Query
$url = "https://134.56.226.215/rest/sbaconfig?action=installwindowsupdates" Invoke-RestMethod -Uri $url -Method POST -Body "" -WebSession $ps
Response
<?xml version="1.0"?> <root> <status> <http_code>200</http_code> </status> </root>
Action end on status
$url = "https://134.56.226.215/rest/sbaactionstatus" Invoke-RestMethod -Uri $url -Method GET -WebSession $MyPs <?xml version="1.0"?> <root> <status> <http_code>200</http_code> </status> <sbaactionstatus href="https://134.56.226.215/rest/sbaactionstatus"> <rt_Success>1</rt_Success> <rt_ActionType>35</rt_ActionType> <rt_PercentComplete>100</rt_PercentComplete> <rt_Duration>7050</rt_Duration> <rt_StatusText>Install Updates complete</rt_StatusText> <rt_AllActionsBitmap>127</rt_AllActionsBitmap> <rt_ActionStartTime>0</rt_ActionStartTime> </sbaactionstatus> </root