DX Infrastructure Manager

Expand all | Collapse all

20.3.1 update

Jump to Best Answer
  • 1.  20.3.1 update

    Posted 12 days ago
    i didnt understand how to install the update of 20.3.1

    there are zip filed and there is the OC_Installer

    is there any manual?

    thank you.

  • 2.  RE: 20.3.1 update

    Posted 11 days ago
    As far as I understood it, it's just an update for the OC. Just copy that installer to the UIM server and run it from there to upgrade the OC.

    All the other zip files are probes that need to be imported in the archive of the UIM server.


  • 3.  RE: 20.3.1 update

    Posted 11 days ago
    where i deploy the uimapi package?
    to the Primary HUB or to the Operator Console?
    where i deploy mon config?

  • 4.  RE: 20.3.1 update

    Posted 11 days ago

    UIMAPI is deployed to the OC.


    For UIM 20.3 or later, deploy the uimapi package to the OC robot in your UIM environment to access the uimapi REST APIs.

    The uimapi 20.31 package is released as part of the UIM 20.3.1 patch. The UIM 20.3.1 patch includes various standalone artifacts. Therefore, ensure that you deploy the related 20.3.1 artifacts (mon_config_service 20.31, mon_config_service_ws 20.31, mon_config_service_recon 20.31, mon_config_service_cli 20.31, robot_update 9.32, OC 20.3.1 Upgrade Installer, uimapi 20.31) to access the complete functionality that the patch provides.

  • 5.  RE: 20.3.1 update

    Broadcom Employee
    Posted 11 days ago
    - put Robot 9.32 into archive, deploy to all core robots (hub, oc, cabi)
    - put UIMAPI into archive, deploy to primary hub
    - Double check cryptkey setting synched on all core robots (fully pathed out in raw Configure and certificate.pem files match) and successful DNS lookup
    - run OC on primary hub and specify OC server during upgrade (if possible, it SHOULD show)
    - unzip MCS bundle (it contains 4 packages that need to go into the archive and then onto either Primary Hub or OC)
    -- Stop mon_config_service probe on Hub, Deploy mon_config_service_20.31.zip to the Hub, start mon_config_service
    -- Stop WASP probe on OC server (even though read me says UMP), Deploy mon_config_service_ws_20.31.zip to the OC, Start WASP
    -- Deploy mon_config_service_recon_20.31.zip to the Hub, Activate the eponymous probe that gets created
    -- Deploy mon_config_service_cli_20.31.zip to the Hub
    - Push any other packages as needed (telemetry and SDK)

  • 6.  RE: 20.3.1 update

    Broadcom Employee
    Posted 11 days ago
    One change with the changes in 20.3 it now goes to the OC robot and the URL has changed
    You can get to it via: http://oc servername/uimapi/swagger-ui.html

    Support Engineer

  • 7.  RE: 20.3.1 update

    Posted 11 days ago
    one of you said to deploy uimapi to PH and another to the OC.
    what is the correct answer?

  • 8.  RE: 20.3.1 update

    Broadcom Employee
    Posted 11 days ago
    For UIM 20.3 or later, deploy the uimapi package to the OC robot 

    Support Engineer

  • 9.  RE: 20.3.1 update

    Posted 11 days ago
    thank you,
    i marked justin message as the best answer !
    thank you all

  • 10.  RE: 20.3.1 update
    Best Answer

    Posted 10 days ago
    Edited by Ivan Gasparec 10 days ago
    High-Level Upgrade/Deployment Process
    For the UIM 20.3.1 upgrade, review the following points:
    • Before you upgrade to UIM 20.3.1, verify that your existing environment is using UIM 20.3.0.
    • The UIM 20.3.1 patch does not include any upgrade installer for the UIM Server. The patch contains separate standalone artifacts that you need to deploy manually to upgrade the respective components to 20.3.1. Therefore, ensure that you deploy the latest packages (for example, robot_update, mon_config_service) that are available for 20.3.1.
    • The UIM 20.3.1 patch also includes an upgrade installer for OC. You can run the OC upgrade installer to upgrade OC 20.3.0 to OC 20.3.1.
    • Finally, after upgrading all the appropriate components, you can start using the features that the UIM 20.3.1 patch provides.
    The recommended high-level steps to apply the patch artifacts are as follows:
    • Deploy robot 9.32 to the core robots (for example, hub, OC, CABI).
    • Run the OC 20.3.1 upgrade installer on the primary hub and specify the OC server during the upgrade.
    • Deploy the MCS 20.31 packages as follows:
    • Deactivate the existing mon_config_service probe on the primary hub, deploy the mon_config_service 20.31 package to the primary hub, and activate mon_config_service.
    • Deactivate the wasp probe on the OC robot, deploy the mon_config_service_ws 20.31 package to the OC robot, and activate wasp.
    • Deploy the mon_config_service_recon 20.31 package to the primary hub and activate the probe after it gets created.
    • Deploy the mon_config_service_cli 20.31 package to the primary hub.
    • Deploy the uimapi 20.31 package to the OC robot.
    • Deploy the other packages (uimesdplatelemetry and Perl SDK) as required.