You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Beginning with release 8.0, SBC clusters deployed in an OpenStack cloud must use either OAM node or Direct Single configuration management. For existing clusters that use the SBC HeadEnd configuration model, the following procedure outlines the steps to migrate the cluster and its current configuration to OAM configuration mode, without an interruption in service. This procedure requires steps on both the nodes in the SBC cluster and the Insight EMS that holds the current SBC cluster configuration.

  1. Upgrade the EMS to release 12.0 using the existing replacement upgrade procedure. Refer to Installing and Upgrading Insight EMS. After upgrade, the EMS still holds the HeadEnd-created SBC configuration for the cluster, but it now also supports OAM configuration mode.
  2. Log onto the upgraded EMS.
  3. Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters.

  4. Click the radio button adjacent to the name of the cluster you are migrating. The Details tab for the selected cluster opens by default. 

    Cluster Configuration on EMS

  5. Change the cluster Configuration Type to OAM and then click Save.
  6. Instantiate the OAM nodes with metadata directing them to the EMS. Refer to Specifying Cluster Configuration Mode Parameters in Heat Deployments, or Instantiating SBC SWe on OpenStack using VNFM, depending on your method of deployment. The active OAM registers with the EMS and downloads the HeadEnd-based configuration. The OAM node converts the configuration to the OAM data model and saves it back to the EMS. 
  7. Replacement upgrade the standby SBC with metadata pointing to the OAM node. The upgraded standby SBC registers with the active OAM node and gets the converted configuration from it. The upgraded SBC also registers with the EMS but does not request configuration from it.
  8. Switch over one non-upgraded, active SBC to become the current standby.
  9. Replacement upgrade the current standby with metadata pointing to the OAM node. The upgraded standby SBC boots as a standby, registers with the active OAM node and gets the converted configuration from it. The upgraded SBC also registers with the EMS but does not request configuration from it.
  10. Repeat the previous two steps for all remaining SBCs in the cluster. 
  • No labels