DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.


Related articles:

In SBC SWe N:1 and SWe cloud-based systems, 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 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.

Note
  • 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.
  • It is not recommended to delete a dynamic metavariable that is in use as it can cause issues with configuration. Before deleting, ensure that the dynamic metavariable is not in use by any configuration in the system.