Page History

System Naming Convention

The system name is used in billing, external PSX queries (if applicable), and system logs. On an HA system, one system name applies to both units and each unit has its own instances as described in Instance Naming Convention section. 

...

The following table lists system naming convention to follow while setting up SBC SWe systems:

Y = Supported

N = Not Supported

Caption
0 Table 1 SBC System Naming Convention 3 SBCHNC
Convention/Character System Name Use as Leading Character Use as Trailing Character Maximum number of characters 26 Letters  [ a-z ] | [ A-Z ] Y YY Digits [ 0-9 ] Y N Y Hyphen [ - ] Y NN Period [ . ] NN N Underscore [ _ ] NN N Other special characters NN N

Changing Default System Name

To change the default system name, provide the customization script in the Post-Creation tab of the Launch Instance. For more details on the Post-Creation tab, refer to Instantiating and Configuring Installing SBC SWe on OpenStackVirtual Platforms.

{
  "SystemName" :<custom system name>"
}

Hostname/Instance Naming Convention

The default name of instance are "vsbc1" and "vsbc2". You can only modify instance names while instantiating.

...

The following table lists hostname/instance naming convention to follow while setting up SBC SWe systems:

Y = Supported

N = Not Supported 

Caption
0 Table 1 SBC Hostname/Instance Naming Convention 3 SBC Hostname/Instance Naming Convention
Convention/Character Instance Name Use as Leading Character Use as Trailing Character Maximum number of characters 64 Letters  [ a-z ] | [ A-Z ] Y YY Digits [ 0-9 ] Y N Y Hyphen [ - ] Y NN Period [ . ]1 Y NN Underscore [ _ ]2 NN N Other special characters NN N

Changing Default Instance Name

To change the default instance name, provide the customization script in the Post-Creation tab of the Launch Instance. For more details on the Post-Creation tab, refer to Instantiating and Configuring Installing SBC SWe on OpenStackVirtual Platforms.

{
 "CEName" :<custom instance name>
}

VNFC and Cluster Naming Convention

The following table lists VNFC and Cluster naming convention to follow while instantiating VNFC and creating clusters:

Y = Supported

N = Not Supported

Caption
0 Table 1 VNFC and Cluster Naming Convention 3 VNFC and Cluster Naming Convention
Convention/Character Instance Name Use as Leading Character Use as Trailing Character Maximum number of characters 64 Letters  [ a-z ] | [ A-Z ] Y YY Digits [ 0-9 ] Y N Y Hyphen [ - ] Y NN Period [ . ]1 NN N Underscore [ _ ]2 NN N Other special characters NN N

Checking Server Name using CLI

To know the server name, execute show table system serverAdmin. In the below example, vsbc1 is the server name.

admin@vsbc1> show table system serverAdmin
       ACTUAL
       CE      COREDUMP             MODULAR                PKT PORT
NAME   NAME    PROFILE   ROLE       TYPE     HW TYPE       SPEED       HW SUB TYPE
-------------------------------------------------------------------------------------
vsbc1  vsbc1   default   primary    false    ConnexIP5000  speed1Gbps  virtualCloud
vsbc2  none    default   secondary  false    ConnexIP5000  -           virtualCloud

Checking System Name using CLI

To know the system name, execute show table system serverAdmin. In the below example, vsbcSystem1 is the system name.

...