signaling
Panel | ||||||
---|---|---|---|---|---|---|
In this section:
|
System and instance names are assigned during instantiation. You can edit the userdata values that specify these names in the template file you are using during instantiation. Refer to Instantiating SBC SWe on OpenStack using Heat Templates or Instantiating SBC SWe on AWS. If you deploy using VNFM, you can set the system name during the instantiation process. The default instance names are set within the VNFD file. Refer to Instantiating SBC SWe on OpenStack using VNFM.
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 instance name as described in the Instance Naming Convention section.
The default system name is vsbcSystem
. An example system name is WFDSBC01
, where:
...
Caption | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
|
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 Installing SBC SWe on Virtual Platforms.
Code Block | ||
---|---|---|
| ||
{
"SystemName" :<custom system name>"
} |
...
The default name of instance are "vsbc1" and "vsbc2". You can only modify instance names while instantiating.
If you are providing an instance name, the instance must be configured with the same name and used for all accounting, logging, PSX and EMS communications. Instance The instance name is specific to an instance.
The following table lists hostname/lists the instance naming convention to follow while setting up SBC SWe systems:
...
Caption | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
|
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 Installing SBC SWe on Virtual Platforms.
Code Block | ||
---|---|---|
none | ||
{
"CEName" :<custom instance name>
} |
...
Caption | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
|
...
To know the server name, execute show the instance names, execute show table system serverAdmin
. In the below example, vsbc1 is the server nameceName provided in the userdata.
Code Block | ||
---|---|---|
| ||
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 |
To know the system name, execute show execute show table system
serverAdminadmin actualSystemName
. In the below example, vsbcSystem1 vsbcSystem is the system namename given in the userdata.
Code Block | ||
---|---|---|
| ||
admin@vsbc1> show table system admin actualSystemName UTIL MONITOR UTIL STATS MINIMUM MINI ACTUAL LOCAL EXTERNAL MONITOR NUM OF AUDIT NUMBER OF NUMB SYSTEM AUTHENTICATION AUTHENTICATION STATS PAST LOG DSP MISMATCH MINIMUM UPPERCASE LOWE NAME NAME CLUSTER ID LOCATION CONTACT ENABLED ENABLED STATE INTERVAL INTERVAL STATE ACTION LENGTH CHARS CHAR ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- vsbcSystem vsbcSystem sbc-signaling Unknown Unknown true false enabled 5 4 enabled preserveRedundancy 8 1 1 |
...