Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 3

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: corrected typo

Add_workflow_for_techpubs
AUTH1eyoustra
REV5bscoggins
REV6bscoggins
REV3llokesh
REV1alipman

 

Info
iconfalse

Related articles:

In SBC SWe Cloud deployments, metadata configures values related to the SBC interfaces such as IP addresses and gateways. This information initially comes during instantiation from metadata found in Heat templates or configuration drives.

SBC SWe Cloud provides the metaVariableDynamic table you can populate with additional metavariables to add to the metadata in an existing deployment. The metavariable values in the table become available to the instance without having to rebuild it. For example, you can add the metavariable values needed to configure an additional SIP signaling port in a deployed SBC instance. Refer to Using Dynamic Metavariables to Add a SIP Signaling Port for a detailed example.

The table is not intended to make changes to existing configuration. You cannot add metavariables to the table to override values that were already defined during instantiation.

Info
titleNote
  • You cannot add an entry to the system metaVariableDynamic table, if the entry already exists in the system metaVariable table.
  • When you add an entry in the metaVariableDynamic table, make sure to add an entry for each of the nodes in the cluster (active and standby).
  • If you make a change to the parameter values in the system metaVariableDynamic table, that change is reflected only after the application is restarted.