Page History

Add_workflow_for_techpubs

AUTH1
REV5
REV6
REV3
REV1

Panel

In this section:

Table of Contents

maxLevel	4

In the OpenStack environment,when cloud instances are launched through Heat, metadata and userdata are populated automatically by the Heat template when . The SBC SWe cloud instances are launched through Heat. The metadata and userdata you provide in the your template are essential to ensuring that the SBC SWe instance you deploy can initialize correctly. To be interpreted correctly, the metadata and userdata must be provided in the proper JSON format. The example Heat templates

Spacevars

0	company

provides include metadata and userdata sections in the proper required format. When editing or copying these sections to create your own Heat template, be sure to maintain the format. The following sections describe the SBC SWe metadata and userdata.

Info
For AWS and OpenStack, there is now a common REST API command for accessing/showing/listing instantiation data such as meta-data and user-data. For details, refer to the REST-API-Reference-Guide.

Metadata Format

Code Block

# Mgt0 interface
   
"IF0" : { 
        "Port":"Mgt0",
		"DHCP": "<Dhcp_flag>",
        "GWV4":"<IP_Address>",
        "IPV4":"<IP_Address/Subnet_Prefix>",
        "GWV6" :"<IP_Address>",
        "IPV6":"<IP_Address/Subnet_Prefix>",
        "FIPV4":"<IP_Address>",
},
   
# Ha0 interface
 "IF1" : {
        "Port" : "Ha0",
		"DHCP": "<Dhcp_flag>",
        "GWV4":"<IP_Address>",
        "IPV4":"<IP_Address/Subnet_Prefix>",
        "FIPV4":"<IP_Address>",
  },
  
# IP interface Pkt0.111
"IF2":  {
        "Port" :"Pkt0",
		"DHCP": "<Dhcp_flag>",
        "GWV4":"<IP_Address>",
        "IPV4":"<IP_Address/Subnet_Prefix>",
        "GWV6" :"<IP_Address>",
        "IPV6":"<IP_Address/Subnet_Prefix>",
        "FIPV4":"<IP_Address>",
        "RNat":"true",
        "VlanId":"111"
  },
},
  
# Secondary IP for Pkt0.111   
"AltIP2" : {
        "IFName":"IF2",
        "IP": "<IP_Address>",
        "FIPV4":"<IP_Address>"
 }
  
# Another Secondary IP for Pkt0.111 
"AltIP3" : {
        "IFName":"IF2",
        "IP": "<IP_Address>",
        "FIPV4":"<IP_Address>"
 }
 
# IP interface Pkt0.222
"IF3":  {
        "Port":"Pkt0",
		"DHCP": "<Dhcp_flag>",
        "GWV4":"<IP_Address>",
        "IPV4":"<IP_Address/Subnet_Prefix>",
        "GWV6" :"<IP_Address>",
        "IPV6":"<IP_Address/Subnet_Prefix>",
        "FIPV4":"<IP_Address>",
        "RNat":"true",
        "VlanId":"222" 
  },
   
# Secondary IP for Pkt0.222
"AltIP4" : {
        "IFName":"IF3",
        "IP": "<IP_Address>",
        "FIPV4":"<IP_Address>", 
 },
   
# IP interface Pkt1.333
"IF4":  {
        "Port":"Pkt1",
		"DHCP": "<Dhcp_flag>",
        "GWV4":"<IP_Address>",
        "IPV4":"<IP_Address/Subnet_Prefix>",
        "GWV6" :"<IP_Address>",
        "IPV6":"<IP_Address/Subnet_Prefix>",
        "FIPV4":"<IP_Address>",
        "RNat":"true",
        "VlanId":"333"
  },
   
# Secondary IP for Pkt1.333
"AltIP5" : {
        "IFName":"IF4",
        "IP": "<IP_Address>",
        "FIPV4":"<IP_Address>"
},

ClusterIp: "<RG_IP>"

If a port needs to be part of multiple VLANs, IF definitions including the port must be repeated for each VLAN IDs, as follows:

Code Block

"IF3": {
"GWV4": "<IP_Address>",
"DHCP": "<Dhcp_flag>",
"Port": "Pkt1",
"VlanId": "<VLAN_ID_1>",
"IPV4": "<IP_Address/Subnet_Prefix>"
},

"IF4": {
"GWV4": "<IP_Address>",
"DHCP": "<Dhcp_flag>",
"Port": "Pkt1",
"VlanId": "<VLAN_ID_2>",
"IPV4": "<IP_Address/Subnet_Prefix>"
},

"IF5": {
"GWV4": "<IP_Address>",
"DHCP": "<Dhcp_flag>",
"Port": "Pkt1",
"VlanId": "<VLAN_ID_3>",
"IPV4": "<IP_Address/Subnet_Prefix>"
}

Pagebreak

Example

of

Metadata

Code Block

language	none

#Interface definition for the Mgt0 port.
"IF0" : {
        "Port":"Mgt0",
		"DHCP": "False",
        "GWV4":"10.0.0.1",
        "IPV4":"10.0.0.24/24",
        "GWV6" :"fd00:10:2b50:4000::1",
        "IPV6":"fd00:10:2b50:4000::1/64",
        "FIPV4":"10.14.52.108",
},
   
# JSON for the Ha0 interface
 "IF1" : {
        "Port" : "Ha0",
		"DHCP": "False",
        "GWV4":"192.168.100.1",
        "IPV4":"192.168.100.24/24",
  },
  
# JSON for the IP interface Pkt0.2007
"IF2":  {
        "Port" :"Pkt0",
		"DHCP": "False",
        "GWV6" :"fd00:10:6b21:2007::1",
        "IPV6":"fd00:10:6b21:2007::1001/64",
        "VlanId":"2007"
  },
# JSON for the IP interface Pkt1.2008

"IF3":  {
        "Port" :"Pkt1",
		"DHCP": "False",
        "GWV6" :"fd00:10:6b21:2008::1",
        "IPV6":"fd00:10:6b21:2008::1001/64",
        "VlanId":"2008"
  },
},
  
# Secondary IP for Pkt0.2007 
"AltIP2" : {
        "IFName":"IF2",
        "IP": "fd00:10:6b21:2007::1002",
}
  
# Another Secondary IP for Pkt0.2007
"AltIP3" : {
        "IFName":"IF2",
        "IP": "fd00:10:6b21:2007::1003",
},

ClusterIp: "192.168.100.25"

Info

title	Note

Ensure the alternate IP definitions have corresponding IF names.
IF dictionary names are any name prefixed by IF .

Example : IF-ABC, IFASD, IF_AS, and so on.

The name for an alternate IP address on a port can be constructed with port/vlan VLAN information.

Example: The second alternate IP address for pkt0's first VLAN IP interface can be named as PKT0_V01_ALT_IP_02.

The maximum length of the name is 255 characters.

This section describes individual parameters within the SBC metadata:

Interface Definition Format

Code Block

"IF3IFX" : { {
        "Port": "Pkt0<Port_Name>",
		"DHCP": "False<Dhcp_flag>",
        "GWV4RNat": "10.0.3.1<True|False>",
        "IPV4GWV4": "10.0.3.187/24"<IP_Address>",
        "GWV6IPV4": "fd00:10:6b50:4350::6"<IP_Address/Subnet_Prefix>",
        "IPV6GWV6" : "fd00:10:6b50:4350::69/64"<IP_Address>",
        "FIPV4IPV6": "54.32.21.12"<IP_Address/Subnet_Prefix>",
        "RNatFIPV4": "true<IP_Address>",
        "VlanId":"222<VLAN_ID>"
  }

Anchor

	Interface Parameter Table
	Interface Parameter Table

The elements which constitutes can constitute an interface definition:

Caption

0	Table
1	Interface Definition Parameters
3	Interface Definition

Parameters	Description
IFXIFX	Interface definition name This element is the name of the dictionary which contains the information of the port. Here, "IF" is a key word, and it can be appended with any name/identifier for X. Example: IF_Pkt0, IFMgt0, IF-MediaPort. Note: The name provided for Interface the interface definition is used in Alternate an alternate IP definition. A link is formed between the two definitions based on the Interface interface definition name.
Port	Port Name One of – Mgt0, Ha0, Pkt0, Pkt1. This indicates the actual port to which the definition belongs to.
DHCP	This flag is used to	DHCP	This flag is used to enable or disable the DHCP. If the DHCP is set to False, you need to provide fixed IP for each ports.
Port	Port Name One of – Mgt0, Ha0, Pkt0, Pkt1. This indicates the actual port to which the definition belongs to.

RNat	Reverse NAT flag Values: True: To consider FIPV4 entity using value provided in the dictionary. False: To configure FIPV4 using SMM rules, and ignore the FIPV4 value provided. Default value - True
GWV4	Gateway IP	IPV4	Primary IP on the Private Port + Prefix - v4 Should be provided only in case of DHCP disabled on the port requires V4 address. Example: 10.54.116.53/23	GWV4	Gateway IP v4 Should be provided only in case of DHCP disabled on the port requires V4 address. Note : GWV4 and Note : GWV4 and IPV4 are interdependent, both have to be provided in noDHCP V4 scenario.
IPV6IPV4	Primary IP on the Private Port + Prefix - v6v4 Should be provided only in case of DHCP disabled on the port requires v6 V4 address. Example: fd00:10:6b50:4350::69/6410.54.116.53/23
GWV6	Gateway IP v6 Should be provided only in case of DHCP disabled on the port requires v6 address. Note : GWV6 and IPV6 are interdependent, both have to be provided in noDHCP v6 scenario.
FIPV4IPV6	Floating IP associated on the Port. Provide when the Floating IP is associated (in DHCP enabled and disabled scenario) with the port. Private Port + Prefix - v6 Should be provided only in case of DHCP disabled on the port requires v6 address. Example : fd00:10:6b50:4350::69/64
FIPV4	Floating IP associated on the Port. Provide when the Floating IP is associated (in DHCP enabled and disabled scenario) with the port.	RNat	Reverse NAT flag Values: True: To consider FIPV4 entity using value provided in the dictionary. False: To configure FIPV4 using SMM rules, and ignore the FIPV4 value provided. Default value - True
VlanId	ID of the VLAN.

Alternate IP Definition

Alternate An alternate IP definition contains the information of for an additional IP addresses address associated with the a port. For each additional IP address added to the port, there has to be corresponding ALT IP definition. The maximum number of ALT IP (alternate IP address) that can be associated with a port is restricted to 14following is an example definition with the parameters explained in the table that follows the example.

Code Block
"AltIP3" : { "IFName":"IF2", "IP": "10.2.0.7", "FIPV4":"aaa.bbb.ccc.eee" }

Caption

0	Table
1	Alternate IP Definition Parameters
3	Alternate IP Definition

Parameter	Description
AltIP3	Alternate IP (ALT IP) definition name/identifier .Alternate IP address associated with a port. This identifier does not have any restriction on naming, AltIP3 is an example. Example Other examples for ALT IP identifier : Alt_Pkt0_AX, ALT_PKT0_01, signaling_Pkt0_05.
IFName	Interface definition Namename Indicates the Makes an association between the ALT IP address and the an existing interface definition. When the user changes If you change the interface definition name (i.e IFX IFX name), the user you must simultaneously change the IFName value in this definition. Otherwise, the link between the ALT IP and it's its associated port is lost.
IP	IPV4 or IPV6 address IP address that needs to be associated associate with the port. User can type v4 or v6 Specify an IPv4 or IPv6 address, based on what the IP version the parent interface dictionary definition contains. When IF definition has v4/v6 address, the ALT IP definition also must have only v4/v6 address. In case of dual-stack scenario, since, Interface dictionary has both V4 and V6 addresses, the ALT IP definition can also have v4 and v6 addresses. But both have to In a dual-stack scenario, the interface definition has both IPv4 and IPv6 addresses, you can also have IPv4 and IPv6 ALT IP addresses. They must be defined in separate ALT dictionaryIP definitions, each pointing to it's the parent dictionarydefinition.
FIPV4	Floating IP on the Alternate IP If Use this parameter to specify the value of a floating IP is associated to associate with the ALT (alternate/additional) IP, the value against this field must contain the floating IP. Note: The RNat flag which is defined in the interface dictionary definition is an interface-wide entity. If the RNat flag is disabled in the interface dictionarydefinition, the FIP value provided in the ALT IP definition is not considered while populating the metaVariables metavariables for this port.

Cluster IP

The parameter ClusterIp is used for to form a Redundancy Group (RG) formation during startup. You must pass HA0 the IP address of one of the nodes of in the RG as in the ClusterIp parameter. The format is shown below.

Code Block
ClusterIp: "<RG_IP>"

Caption

0	Table
1	Cluster IP Parameters
3	Cluster IP

Parameter	Description
ClusterIp	ClusterIP is the IP address of one of the nodes in the RG used for Redundancy Group ( RG ) formation on startup.

UserData

Userdata Format

Code Block

{
 "CERole" : "CERole",
 "CEName" : "CEName",
 "SystemName" : "SystemName",
 "SbcPersonalityType" : "SbcPersonalityType",
 "EmsUsername" : "EmsUsername",
 "EmsPassword" : "EmsPassword",
 "EmsIP" : "EmsIP",
 "EmsDownloadConfig" : "EmsDownloadConfig",
 "ConfigDownloadName" : "ConfigDownloadName",
 "EmsPrivateNodeParameters" : { "cluster_id": "","vnfc_id":""}
}

Info
The Userdata JSON is present under the write_file directory `/opt/sonus/conf/userData.json`.

Example of Userdata

user_data_format: RAW
user_data:
str_replace:
template: |
#cloud-config
users:
- name: admin
ssh-authorized-keys:
- "adminSshKey"
lock_passwd: false
- name: linuxadmin
ssh-authorized-keys:
- "linuxAdminSshKey"
lock_passwd: false
runcmd:
- usermod -p '"adminPassword"' admin
- usermod -p '"linuxAdminPassword"' linuxadmin
 
write_files:
- content: |
{
 "CERole" : "CERole",
 "CEName" : "CEName",
 "SystemName" : "SystemName",
 "SbcPersonalityType" : "SbcPersonalityType",
 "SbcMgmtMode" : "Mgmt_mode",
 "EmsUsername" : "EmsUsername",
 "EmsPassword" : "EmsPassword",
 "EmsIP" : "EmsIP",
 "EmsDownloadConfig" : "EmsDownloadConfig",
"TemplateName" : "TemplateFileName",
"TemplateVersion" : "Template_Version",
 "EmsPrivateNodeParameters" : { "cluster_id": "","vnfc_id":""}
}
path: /opt/sonus/conf/userData.json
bootcmd:
- /opt/sonus/bin/mountVolume.sh -v "cinderVolumeIdForLogs"

Info
The Userdata JSON is present under the write_file directory `/opt/sonus/conf/userData.json`.

Example Userdata

Code Block

{
  "CERole"                  : "ACTIVE",
  "CEName"                  : "vsbc1",
  "SystemName"              : "vsbcsystem",
  "SbcPersonalityType"      : "msbc",
  "SbcMgmtMode"             : "distributed",
  "EmsUsername"             : "restuser",
  "EmsPassword"             : "sonus123",
  "EmsIP"                   : [ "10.54.58.184", "10.54.58.185" ],
  "EmsDownloadConfig"       : "True",
  "TemplateName"            : "heatRgActiveTemplate.yaml",
  "TemplateVersion"         : "V07.01.00",
  "EmsPrivateNodeParameters": { "cluster_id": "MSBC" , "vnfc_id": "Msbc1_N1" }
}

Info

title	Note:

Beginning with release 7.1, you must include SSH keys or passwords in the Heat template to log into the SBC CLI or linux shell. Because they are more secure, SSH key fields are mandatory in the Heat templates.
You can use the ssh-keygen command to generate keys. This command generates two files id_rsa and id_rsa.pub in your /home/<user>/.ssh directory. The contents of the id_rsa.pub file contains the input value for the keys in the template. Optionally, keys can also be protected using a passphrase.
Use man ssh-keygen for more options.

Passwords are optional fields.The password input is not plain text, it is a hash of the password. The hash password can be generated using the command: mkpasswd --method=SHA-512 --rounds=4096
Use man mkpasswd for more options.

Caption

Code Block

{
  "CERole"                  : "ACTIVE",
  "CEName"                  : "vsbc1",
  "SystemName"              : "vsbcsystem",
  "SbcPersonalityType"      : "msbc",
  "EmsUsername"             : "restuser",
  "EmsPassword"             : "sonus123",
  "EmsIP"                   : [ "10.54.58.184", "10.54.58.185" ],
  "EmsDownloadConfig"       : "True",
  "ConfigDownloadName"      : "savedMSBCconfiguration",
  "EmsPrivateNodeParameters": { "cluster_id": "MSBC" , "vnfc_id": "Msbc1_N1" }
}

Caption

0	Table
1	OpenStack Userdata Parameter Description

Parameter	Description
adminSshKey	Specifies the public SSH key to log into the SBC CLI as the `admin` user.
linuxAdminSshKey	Specifies the public SSH key to log into the SBC shell as the linuxadmin user.
adminPassword	The hash of the password to log into the SBC CLI as the `admin` user.
linuxAdminPassword	The hash of the password to log into the SBC shell as the linuxadmin user.
CERole	Assigned role for the
Parameter	Length	Example	Description
CERole	N/A	Active	Assigned role of SBC instance. Allowed Valuevalues: Active Standby
CEName	Specifies the actual CE name of the SBC instance. For more information, see System and Instance Naming Conventions. CEName requirements: Must start with an alphabetic character. Can only contain alphabetic characters and/or numbers. No special characters. Cannot exceed 64 characters in length.
vsbc1 SystemName	Specifies the actual CE system name of the SBC instance. For more information, see System and Instance Naming Conventions. CEName RequirementsSystemName requirements: Must start with an alphabetic character. Only Can only contain alphabetic characters and/or numbers. No special characters. Cannot exceed 64 26 characters in length
SystemName	26	vsbcSystem	Specifies the actual system name of the SBC instance. For more information, see System and Instance Naming Conventions. System Requirements: Must start with an alphabetic character. Only contain alphabetic characters and/or numbers. No special characters. Cannot exceed 26 characters in length.
SbcPersonalityType	N/A	ssbc	Specifies the SBC personality type. Allowed Value: isbc ssbc msbc
EmsUsername	N/A	restuser	Specifies the REST log in credentials of EMS. Default Value: restuser
EmsPassword	N/A	sonus123	Specifies the REST log in credentials of EMS. Default Value: sonus123
.
SbcPersonalityType	Specifies the SBC personality type. Allowed values: isbc ssbc msbc
SbcMgmtMode	Specifies the SBC management mode. Allowed values: centralized - a 1:1 HA redundancy model where one active instance is backed up by one standby instance. In centralized mode, the SBC configuration is synchronized between active and standby SBCs. distributed - an N:1 redundancy model where up to N active instances are backed up by a single standby instance. In this mode, each node is configured separately, and the configuration on active and standby instances are not synchronized. The instances in such deployments also have homogeneous configuration.
EmsUsername	Specifies the REST username for logging into EMS. Default value: "None" If the SBC SWe is not integrated with an EMS, this parameter should be set to "None".
EmsPassword	Specifies the REST password for logging into EMS. Default value: "None" If the SBC SWe is not integrated with an EMS, this parameter should be set to "None".
EmsIP	Specifies the EMS instance IPv4 or IPv6 address(es).	EmsIP	N/A For IPv4 Standalone EMS IP address as - "aaaa:bbbb:cccc:dddd" Geographical Redundancy EMS IP address as: ["aaaa:bbbb:cccc:dddd","aaaa:bbbb:cccc:dddd"] For IPv6 Standalone EMS IP address as - "aaaa:bbbb:cccc:dddd::xx" Geographical Redundancy EMS IP address as: ["aaaa:bbbb:cccc:dddd::xx","aaaa:bbbb:cccc:dddd::yy"]
EmsDownloadConfig	Whether configuration should be downloaded from the EMS.	Specifies the EMS instance for IPv4 and IPv6 address.	Default value: True Allowed values: True False
TemplateName	Specifies the name of the template file.
TemplateVersion	Specifies the software version associated with the template.
EmsPrivateNodeParameters	EmsPrivateNodeParameters	64	N/A	Specifies the EMS private node parameters. `cluster_id` - Unique to one ID for a specific cluster in a cloud environment which can contain one or more SBC instances. vnfc_id - Unique ID specified for SBC instance. `vnfc_id` - Unique ID specified for an SBC instance. The EMS identifies the nodes based on the VNFC-ID. If you reuse an existing VNFC-ID, the EMS will interpret it as a re-registration request and overwrite the existing data on the cloud node. The cluster ID and vnfc ID both allows hyphen.
EmsDownloadConfig	N/A	True	Whether Configuration needs to be downloaded from EMS. Default value: True Allowed Value: True False
ConfigDownloadName	64	savedMSBCconfiguration1	The SBC configuration name can contain only letters, numbers, dashes (-), apostrophes ('), underscores (_), colons (:) and spaces

Meta Variables

allow hyphens and cannot exceed 64 characters in length.

cinderVolumeIdForLogs

(Optional) Specifies the Cinder volume ID that you want to attach for logs.

Cinder volume length must be between 1 and 8 characters. allowed values: "^[A-Za-z0-9]{1}[-A-Za-z0-9]*[A-Za-z0-9]{1}$"

Metavariables

Interface-related information (contents of interface and ALT IP definitionsInterface related information (contents of Interface and ALT IP definition) provided in userdata and/or metadata is flattened down into key-value pairs, which is used for CLI configurationcan be retrieved using the CLI.

A An example metavariable table for the a 4:1 M-SBC is shown below:

Code Block

admin@vMsbcl> show table system metavariable
CE NAME             NAME        VALUE
------------------------------------------------------
vMsbcl-10.10.20.17  IFO.GWV6 	fd00:10:6b50:43AO::1
vMsbcl-10.10.20.17  IF0.IPV6 	FD00:10:6B50:43AO::DO
vMsbcl-10.10.20.17  IFO.Port 	MgtO
vMsbcl-10.10.20.17  IFl.GWV4 	10.10.20.1
vMsbcl-10.10.20.17  IFl.IPV4 	10.10.20.17
vMsbcl-10.10.20.17  IFl.Port 	HaO
vMsbcl-10.10.20.17  IF2.GWV6 	FD00:10:6B50:4D74::1
vMsbcl-10.10.20.17  IF2.IPV6 	FD00:10:6B50:4D74::DO
vMsbcl-10.10.20.17  IF2.Port 	PktO
vMsbcl-10.10.20.17  IF3.GWV6 	FD00:10:6B50:4D70::1
vMsbcl-10.10.20.17  IF3.IPV6 	FD00:10:6B50:4D70::9
vMsbcl-10.10.20.17  IF3.Port 	PktO
vMsbcl-10.10.20.17  IF4.GWV4 	10.54.226.129
vMsbcl-10.10.20.17  IF4.IPV4 	10.54.226.138
vMsbcl-10.10.20.17  IF4.Port 	PktO
vMsbcl-10.10.20.17  IF5.GWV4 	10.54.226.193
vMsbcl-10.10.20.17  IFS.IPV4 	10.54.226.202
vMsbcl-10.10.20.17  IFS.Port 	PktO
vMsbcl-10.10.20.17  IF6.GWV4 	10.10.13.1
vMsbcl-10.10.20.17  IF6.IPV4 	10.10.13.17
vMsbcl-10.10.20.17  IF6.Port 	Pktl
vMsbcl-10.10.20.17  IF2.Vlan!dVlanid 	313
vMsbcl-10.10.20.17  IF3.Vlan!dVlanid 	309
vMsbcl-10.10.20.17  IF4.Vlan!dVlanid 	311
vMsbcl-10.10.20.17  IFS.Vlan!dVlanid 	312
vMsbcl-10.10.20.17  IFO.PrefixV6 60
vMsbcl-10.10.20.17  IFl.PrefixV4 24
vMsbcl-10.10.20.17  IF2.PrefixV6 64
vMsbcl-10.10.20.17  IF3.PrefixV6 64
vMsbcl-10.10.20.17  IF4.PrefixV4 26
vMsbcl-10.10.20.17  IF5.PrefixV4 26
vMsbcl-10.10.20.17  IF6.PrefixV4 24
vMsbc2-10.10.20.18  IFO.GWV6 	fd00:10:6b50:43AO::1
vMsbc2-10.10.20.18  IF0.IPV6 	FD00:10:6B50:43AO::Dl
vMsbc2-10.10.20.18  IFO.Port 	MgtO
vMsbc2-10.10.20.18  IFl.GWV4 	10.10.20.1
vMsbc2-10.10.20.18  IFl.IPV4 	10.10.20.18
vMsbc2-10.10.20.18  IFl.Port 	HaO
vMsbc2-10.10.20.18  IF2.GWV6 	FD00:10:6B50:4D74::1
vMsbc2-10.10.20.18  IF2.IPV6 	FD00:10:6B50:4D74::Dl
vMsbc2-10.10.20.18  IF2.Port 	PktO
vMsbc2-10.10.20.18  IF3.GWV6 	FD00:10:6B50:4D70::1
vMsbc2-10.10.20.18  IF3.IPV6 	FD00:10:6B50:4D70::A
vMsbc2-10.10.20.18  IF3.Port 	PktO
vMsbc2-10.10.20.18  IF4.GWV4 	10.54.226.129
vMsbc2-10.10.20.18  IF4.IPV4 	10.54.226.139
vMsbc2-10.10.20.18  IF4.Port 	PktO
vMsbc2-10.10.20.18  IF5.GWV4 	10.54.226.193
vMsbc2-10.10.20.18  IFS.IPV4 	10.54.226.203
vMsbc2-10.10.20.18  IFS.Port 	PktO
vMsbc2-10.10.20.18  IF6.GWV4 	10.10.13.1
vMsbc2-10.10.20.18  IF6.IPV4 	10.10.13.18
vMsbc2-10.10.20.18  IF6.Port 	Pktl
vMsbc2-10.10.20.18  IF2.Vlan!dVlanid 	313
vMsbc2-10.10.20.18  IF3.Vlan!dVlanid 	309
vMsbc2-10.10.20.18  IF4.Vlan!dVlanid 	311
vMsbc2-10.10.20.18  IFS.Vlan!dVlanid 	312
vMsbc2-10.10.20.18  IFO.PrefixV6 60
vMsbc2-10.10.20.18  IFl.PrefixV4 24
vMsbc2-10.10.20.18  IF2.PrefixV6 64
vMsbc2-10.10.20.18  IF3.PrefixV6 64
vMsbc2-10.10.20.18  IF4.PrefixV4 26
vMsbc2-10.10.20.18  IF5.PrefixV4 26
vMsbc2-10.10.20.18  IF6.PrefixV4 24
vMsbc3-10.10.20.19  IFO.GWV6 	fd00:10:6b50:43AO::1
vMsbc3-10.10.20.19  IF0.IPV6 	FD00:10:6B50:43AO::D2
vMsbc3-10.10.20.19  IFO.Port 	MgtO
vMsbc3-10.10.20.19  IFl.GWV4 	10.10.20.1
vMsbc3-10.10.20.19  IFl.IPV4 	10.10.20.19
vMsbc3-10.10.20.19  IFl.Port 	HaO
vMsbc3-10.10.20.19  IF2.GWV6 	FD00:10:6B50:4D74::1
vMsbc3-10.10.20.19  IF2.IPV6 	FD00:10:6B50:4D74::D2
vMsbc3-10.10.20.19  IF2.Port 	PktO
vMsbc3-10.10.20.19  IF3.GWV6 	FD00:10:6B50:4D70::1
vMsbc3-10.10.20.19  IF3.IPV6 	FD00:10:6B50:4D70::B
vMsbc3-10.10.20.19  IF3.Port 	PktO
vMsbc3-10.10.20.19  IF4.GWV4 	10.54.226.129
vMsbc3-10.10.20.19  IF4.IPV4 	10.54.226.140
vMsbc3-10.10.20.19  IF4.Port 	PktO
vMsbc3-10.10.20.19  IF5.GWV4 	10.54.226.193
vMsbc3-10.10.20.19  IFS.IPV4 	10.54.226.204
vMsbc3-10.10.20.19  IFS.Port 	PktO
vMsbc3-10.10.20.19  IF6.GWV4 	10.10.13.1
vMsbc3-10.10.20.19  IF6.IPV4 	10.10.13.19
vMsbc3-10.10.20.19  IF6.Port 	Pktl
vMsbc3-10.10.20.19  IF2.Vlan!dVlanid 	313
vMsbc3-10.10.20.19  IF3.Vlan!dVlanid 	309
vMsbc3-10.10.20.19  IF4.Vlan!dVlanid 	311
vMsbc3-10.10.20.19  IFS.Vlan!dVlanid 	312
vMsbc3-10.10.20.19  IFO.PrefixV6 60
vMsbc3-10.10.20.19  IFl.PrefixV4 24
vMsbc3-10.10.20.19  IF2.PrefixV6 64
vMsbc3-10.10.20.19  IF3.PrefixV6 64
vMsbc3-10.10.20.19  IF4.PrefixV4 26
vMsbc3-10.10.20.19  IF5.PrefixV4 26
vMsbc3-10.10.20.19  IF6.PrefixV4 24
vMsbc4-10.10.20.26  IFO.GWV6 	fd00:10:6b50:43AO::1
vMsbc4-10.10.20.26  IF0.IPV6 	FD00:10:6B50:43AO::D9
vMsbc4-10.10.20.26  IFO.Port 	MgtO
vMsbc4-10.10.20.26  IFl.GWV4 	10.10.20.1
vMsbc4-10.10.20.26  IFl.IPV4 	10.10.20.26
vMsbc4-10.10.20.26  IFl.Port 	HaO
vMsbc4-10.10.20.26  IF2.GWV6 	FD00:10:6B50:4D74::1
vMsbc4-10.10.20.26  IF2.IPV6 	FD00:10:6B50:4D74::D9
vMsbc4-10.10.20.26  IF2.Port 	PktO
vMsbc4-10.10.20.26  IF3.GWV6 	FD00:10:6B50:4D70::1
vMsbc4-10.10.20.26  IF3.IPV6 	FD00:10:6B50:4D70::12
vMsbc4-10.10.20.26  IF3.Port 	PktO
vMsbc4-10.10.20.26  IF4.GWV4 	10.54.226.129
vMsbc4-10.10.20.26  IF4.IPV4 	10.54.226.147
vMsbc4-10.10.20.26  IF4.Port 	PktO
vMsbc4-10.10.20.26  IF5.GWV4 	10.54.226.193
vMsbc4-10.10.20.26  IFS.IPV4 	10.54.226.211
vMsbc4-10.10.20.26  IFS.Port 	PktO
vMsbc4-10.10.20.26  IF6.GWV4 	10.10.13.1
vMsbc4-10.10.20.26  IF6.IPV4 	10.10.13.26
vMsbc4-10.10.20.26  IF6.Port 	Pktl
vMsbc4-10.10.20.26  IF2.Vlan!d 	313
vMsbc4-10.10.20.26  IF3.Vlan!d 	309
vMsbc4-10.10.20.26  IF4.Vlan!d 	311
vMsbc4-10.10.20.26  IFS.Vlan!d 	312
vMsbc4-10.10.20.26  IFO.PrefixV6 60
vMsbc4-10.10.20.26  IFl.PrefixV4 24
vMsbc4-10.10.20.26  IF2.PrefixV6 64
vMsbc4-10.10.20.26  IF3.PrefixV6 64
vMsbc4-10.10.20.26  IF4.PrefixV4 26
vMsbc4-10.10.20.26  IF5.PrefixV4 26
vMsbc4-10.10.20.26  IF6.PrefixV4 24
vMsbcS-10.10.20.11  IFO.GWV6 	fd00:10:6b50:43AO::1
vMsbcS-10.10.20.11  IF0.IPV6 	FD00:10:6B50:43AO::CA
vMsbcS-10.10.20.11  IFO.Port 	MgtO
vMsbcS-10.10.20.11  IFl.GWV4 	10.10.20.1
vMsbcS-10.10.20.11  IFl.IPV4 	10.10.20.11
vMsbcS-10.10.20.11  IFl.Port 	HaO
vMsbcS-10.10.20.11  IF2.GWV6 	FD00:10:6B50:4D74::1
vMsbcS-10.10.20.11  IF2.IPV6 	FD00:10:6B50:4D74::CA
vMsbcS-10.10.20.11  IF2.Port 	PktO
vMsbcS-10.10.20.11  IF3.GWV6 	FD00:10:6B50:4D70::1
vMsbcS-10.10.20.11  IF3.IPV6 	FD00:10:6B50:4D70::3
vMsbcS-10.10.20.11  IF3.Port 	PktO
vMsbcS-10.10.20.11  IF4.GWV4 	10.54.226.129
vMsbcS-10.10.20.11  IF4.IPV4 	10.54.226.132
vMsbcS-10.10.20.11  IF4.Port 	PktO
vMsbcS-10.10.20.11  IF5.GWV4 	10.54.226.193
vMsbcS-10.10.20.11  IFS.IPV4 	10.54.226.196
vMsbcS-10.10.20.11  IFS.Port 	PktO
vMsbcS-10.10.20.11  IF6.GWV4 	10.10.13.1
vMsbcS-10.10.20.11  IF6.IPV4 	10.10.13.11
vMsbcS-10.10.20.11  IF6.Port 	Pktl
vMsbcS-10.10.20.11  IF2.Vlan!dVlanid 	313
vMsbcS-10.10.20.11  IF3.Vlan!dVlanid 	309
vMsbcS-10.10.20.11  IF4.Vlan!dVlanid 	311
vMsbcS-10.10.20.11  IFS.Vlan!dVlanid 	312
vMsbcS-10.10.20.11  IFO.PrefixV6 60
vMsbcS-10.10.20.11  IFl.PrefixV4 24
vMsbcS-10.10.20.11  IF2.PrefixV6 64
vMsbcS-10.10.20.11  IF3.PrefixV6 64
vMsbcS-10.10.20.11  IF4.PrefixV4 26
vMsbcS-10.10.20.11  IF5.PrefixV4 26
vMsbcS-10.10.20.11  IF6.PrefixV4 24
[ok] [2017-08-04 12:26:35]

The sample metaVariables metavariable names are used for configuration:

Code Block

set addressContext default ipInterfaceGroup LIG1 ipInterface LIG1_V4 ipVarV4 IF2.IPV4 prefixVarV4 IF2.PrefixV4 vlanTagVar IF5.VlanId portName pkt0 state enabled mode inService
set addressContext default ipInterfaceGroup LIG2 ipInterface LIG2_V4 ipVarV4 IF3.IPV4 prefixVarV4 IF3.PrefixV4 ipPublicVarV4 IF3.FIPV4 portName pkt1 state enabled mode inService
set addressContext default zone ZONE_AS sipSigPort 3 ipInterfaceGroup LIG2 ipVarV4 IF3.IPV4 ipPublicVarV4 IF3.FIPV4 state enabled
set system dsbc dsbcSigPort ipInterfaceGroup SVzIMSMediaIPv6 ipVarV6 PKT0_V02_ALT_IP_01.IP mode inService state enabled
commit

Pagebreak

Space shortcuts

Page tree

Versions Compared

Old Version 7

New Version 8

Key

Metadata Format

Example

Metadata

Interface Definition Format

Alternate IP Definition

Cluster IP

Userdata Format

Example Userdata

Meta Variables

Metavariables