Observer Management Server : Assets and Asset Groups : How to manage software versions using OMS
   
How to manage software versions using OMS
 
Page Contents
How to download upgrades for upgrade policies to use
How to create an upgrade policy
How to disable an upgrade policy
How to delete an upgrade policy
How to update asset groups
How to update individual assets
How to modify the global upgrade policy
Upgrade Version settings
Assets and asset groups can be upgraded or downgraded according to the upgrade policy applied to them.
The initial set up required for managing asset software versions is complex. However, it is complex only due to the need to plan transfer and installation times, select which assets to control, and understand the upgrade policy precedence. This setup process only needs to be performed when necessary, so it becomes easier to maintain after initial setup.
If you are setting up an upgrade policy and version control for the first time, we recommend following each step in order.
If you are modifying an existing upgrade policy or fine-tuning the version control, you can choose to follow the step(s) that are most relevant.
These are the overall steps for managing software versions using OMS, and each is described in fuller detail in other sections:
1. Configure the settings for version control using How to download upgrades for upgrade policies to use.
2. Create an upgrade policy using How to create an upgrade policy.
3. Try applying an upgrade policy to either of the following:
a. An asset group using How to update asset groups.
b. An individual asset using How to update individual assets.
4. Learn about the hierarchy of upgrade policies and what policy takes effect using Understanding which upgrade policy is in effect on assets.
 
 
How to download upgrades for upgrade policies to use
Created: 2014-08-04   Revised: 2015-05-11
Upgrade policies, that are configured to transfer or install new software versions, rely on files downloaded from VIAVI by OMS. Configure your download settings to ensure new versions are brought into OMS and can be pushed to assets using an upgrade policy.
Some settings must remain configured for OMS to automatically download software upgrades for upgrade policies make use of. Otherwise, upgrade policies that are configured to transfer or install new software versions must wait for an OMS administrator to manually check for and download these files from the VIAVI upgrade repository.
Note: Firmware updates to the capture card are bundled with Observer software upgrades. During installation of an Observer software upgrade, any firmware updates available to your capture card will be applied.
To ensure software upgrades are automatically being downloaded for your upgrade policies to make use of, follow these steps:
1. Starting in the dashboard, click Version > Upgrade Versions.
2. Select one by clicking a table row.
3. Click the preferences icon .
4. Ensure Check for upgrades is selected in the General Preferences area, as it is enabled by default.
If selected, OMS periodically checks for upgrades. Scheduled transfers and installs rely on knowing if new versions exist.
5. In the Download Preferences area, configure a Download upgrades schedule to be Daily or Day of Week and set one or more time frames for downloads to occur.
Example: For example, click Daily. Next, ensure the Daily Schedule check box is selected. Then, click the plus symbol (+) to create a new time frame. Finally, click the newly created time frame to adjust the hours when downloads can occur, and click OK.
6. Click the accept icon .
 
You successfully configured OMS to automatically check for upgrades and download them according to a schedule. The downloaded upgrades are used by upgrade policies configured to transfer or install software upgrades.
 
How to create an upgrade policy
Created: 2014-08-04   Revised: 2014-08-04
Create and use an upgrade policy to automate the transfer and installation of software upgrades to assets or asset groups.
To create an upgrade policy:
1. Starting in the dashboard, click Version > Upgrade Policies.
2. Click the new icon .
3. Complete the fields shown using information in Settings and options of an upgrade policy.
4. Click Accept.
 
You successfully created an upgrade policy. If you apply the upgrade policy to an asset or asset group, the upgrade policy takes effect.
 
Settings and options of an upgrade policy
Created: 2013-02-07   Revised: 2015-09-29
The upgrade policy settings control the upgrade behavior of assets. These behaviors take effect after the upgrade policy is applied to an asset or asset group.
 
Name
The name of this upgrade policy.
Description
Upgrade policy descriptions are optional.
Allow to auto-upgrade
Sets if this upgrade policy is active.
If selected, the upgrade policy is enabled. Assets that subscribe to an enabled upgrade policy are automatically upgraded.
Also allow to auto-downgrade to the current OMS version
If selected, Observer Platform applications running later versions than OMS is distributing are automatically downgraded.
Limit upgrade transfer speed to
Sets the preferred maximum transfer speed in kilobits per second.
Use the value '0' to disable this bandwidth restriction.
Transfer schedule
This sets the window of time OMS can transfer upgrade data to assets.
Scheduling the upgrade transfer does not define when the transfer should start or finish.
Install schedule
This sets the window of time OMS can initiate an upgrade installation of your assets.
Scheduling the upgrade installation does not define when the upgrade installation should start or finish.
 
How to disable an upgrade policy
Created: 2014-12-11   Revised: 2014-12-11
You can temporarily discontinue an upgrade policy by disabling it. Each asset configured to use a disabled upgrade policy will use the global upgrade policy instead.
To disable an upgrade policy:
1. Starting in the dashboard, click Version > Upgrade Policies.
2. Click an upgrade policy to select it.
3. Click the edit icon .
4. Clear Allow to auto-upgrade.
5. Click Accept.
 
Any assets that are assigned the disabled upgrade policy now use the global upgrade policy. This continues until the disabled upgrade policy is re-enabled. For details about the global upgrade policy, see How to modify the global upgrade policy.
 
How to delete an upgrade policy
Created: 2015-01-06   Revised: 2018-10-05
Delete an upgrade policy to remove it from the assigned assets and asset groups it was assigned to, plus from OMS. Assets and asset groups without an upgrade policy will immediately begin using the default upgrade policy instead.
To delete an upgrade policy:
1. Starting in the dashboard, click Version > Upgrade Policies.
2. Click an upgrade policy to select it.
3. Click the garbage can icon .
4. Click Yes to confirm the deletion.
 
The upgrade policy has been deleted from OMS. Assets and asset groups that were assigned this upgrade policy now use the default upgrade policy instead.
 
How to update asset groups
Created: 2013-02-07   Revised: 2014-07-28
All assets in an asset group can follow the same upgrade behavior. Use an upgrade policy on an asset group to control the upgrading behavior of the entire group.
Before following these steps, an upgrade policy must have already been created.
To use an upgrade policy to update asset groups managed by OMS:
1. Starting in the dashboard, click Version > Upgrade Policies.
2. Applying an upgrade policy is an easy drag-and-drop operation from the Upgrade policies list to an asset group in the Asset Groups table.
The name of the upgrade policy appears in the Upgrade Policy column of the table, confirming that it has been applied.
 
Now, when an asset either obtains a license from OMS or is contacted by OMS (approximately every hour), OMS verifies that the client has the active version and upgrades or downgrades if necessary.
 
How to update individual assets
Created: 2013-02-07   Revised: 2014-07-28
Individual assets can also have an upgrade policy applied to them.
Before following these steps, an upgrade policy must have already been created.
To use an upgrade policy to update software on a per-asset basis:
1. Starting in the dashboard, click Version > Upgrade Policies.
2. Applying an upgrade policy is an easy drag-and-drop operation from the Upgrade policies list to an asset in the Assets table.
The name of the upgrade policy appears in the Upgrade Policy column of the table, confirming that it has been applied.
 
Now, when an asset either obtains a license from OMS or is contacted by OMS (approximately every hour), OMS verifies that the client has the active version and upgrades or downgrades if necessary.
 
How to modify the global upgrade policy
Created: 2014-12-01   Revised: 2018-10-05
To affect the upgrade policy of all assets that are not specifically given an upgrade policy, you can modify the global upgrade policy.
By default, all assets use the Global Upgrade Policy as an upgrade policy unless explicitly changed.
To modify the global upgrade policy:
1. Starting in the dashboard, click Version > Upgrade Policies.
2. In the rightmost pane, click Global Upgrade Policy to select it.
3. Click the edit icon .
4. Modify the global upgrade policy.
5. Click Accept.
 
Now, any asset or asset group not given an upgrade policy will follow the settings in the global upgrade policy.
 
Upgrade Version settings
Created: 2014-11-15
Some settings affect the downloading of available upgrade versions, the port used, and if any applications should be excluded.
 
Check for upgrades
If selected, OMS periodically checks for upgrades. Scheduled transfers and installs rely on knowing if new versions exist.
If cleared, users must manually check for available upgrades before any scheduled transfers or installs can occur.
Automatically match OMS version
If selected, the active version will automatically be set to match the OMS version.
Upgrade server port
Sets which TCP port is used by the upgrade file server.
The default port is 8008.
Preferred speed (Kbps)
Sets the preferred maximum transfer speed in kilobits per second.
Use the value '0' to disable this bandwidth restriction.
Download upgrades
Schedules the download of available upgrade versions.
Downloaded versions will not automatically install unless an installation schedule or upgrade policy allows it.
Expert Console Observer
If selected, this upgrade policy does not apply to Expert Console Observer.
Observer
If selected, this upgrade policy does not apply to Observer.
Observer Infrastructure
If selected, this upgrade policy does not apply to OI.
Observer Apex
If selected, this upgrade policy does not apply to Apex.