In this section:

Related articles:

For SBC SWe N:1 HA or cloud-based deployments, the metaVariableDynamic table enables you to define additional metavariables to add to the metadata in an existing SBC deployment. The metavariable values in the table become available to the SBC 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.

 Command Syntax

To add a new metavariable to the system metaVariableDynamic table, execute the command:

%set system metaVariableDynamic <ceName of the SBC instance> name <name of the metavariable> value <value to assign to the metavariable>

Command Parameters

ParameterLength/RangeDescription
<ceName>1 - 255 charThe name of the instance, followed by a dash and the HA IP address. See the configuration example below for an example of the format.
name1 - 255 charThe name of an interface definition parameters. Refer to Metadata and Userdata Format on OpenStack for the interface variable format.
value 0 - 255 charThe value you want to assign to the parameter.

Configuration Example

Use the following commands to add a new metavariable to the metavaVariableDynamic table. You must run the commands twice to create the variables on both the active and standby nodes. Refer to Using Dynamic Metavariables to Add a SIP Signaling Port for a complete example using the metavaVariableDynamic table. 

set system metaVariableDynamic isbctest-10.34.195.79 name IF4.IPV4 value 10.34.196.80
[ok]
commit
[ok]
Commit complete.
set system metaVariableDynamic isbctest-10.34.195.80 name IF4.IPV4 value 10.34.196.80
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 a parameter value 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.