In this section:

System Naming Conventions

The following table lists system naming conventions to follow while setting up systems. The system name is used in billing, external PSX queries (if applicable), and system logs. On a HA system, the one system name applies to both units. Each unit has its own hostname as described in the next table. An example system name is WFDSBC01, where:

  • The first three letters represent the physical location of the system (WFD =  Westford).
  • The second three letters identify the system type (SBC).
  • The last two digits identify the SBC (or SBC pair) instance at this particular location.



System Name
Use as Leading
Use as Trailing
Maximum number of characters26  
Letters  [ a-z ] | [ A-Z ](tick)(tick)(tick)
Digits [ 0-9 ](tick)(error)(tick)
Hyphen [ - ](tick)(error)(error)
Period [ . ](error)(error)(error)
Underscore [ _ ](error)(error)(error)
Other special characters(error)(error)(error)

Hostname Naming Conventions

The following table lists local and peer hostname conventions to follow while setting up SBC systems. The SBC hostname consists of the system name with additional characters appended to the system name to distinguish the hostname from the system name.

For an HA system, the local hostname, peer hostname and system name must each be unique. For example, an HA system configured with a system name of “WFDSBC01” has the local hostname and peer hostname named “WFDSBC01a” and “WFDSBC01b”, respectively. 

Hostname is also referred to as "ceName". For example, "local ceName" and "peer ceName" are the equivalent of "local hostname" and "peer hostname".


Hostname / Peer Hostname
Use as Leading
or Trailing Character
Maximum number of characters64 
Letters  [ a-z ] | [ A-Z ](tick)(tick)
Digits [ 0-9 ](tick)(tick)
Hyphen [ - ](tick)(error)
Period [ . ]1(tick)(error)
Underscore [ _ ]2(error)(error)
Other special characters(error)(error)

(1) The period is typically used to specify a fully qualified domain name.

(2) The underscore character ‘_’ is not allowed in either the local hostname or peer hostname because it is not valid for SIP URI and TCP/IP host naming.


Viewing Local Hostname and and Peer Hostname From CLI

One method to view the hostnames is to use the 'show table system serverStatus' CLI command as shown in the example below where the hostnames are listed in the NAME column.

admin@MYSBC-B> show table system serverStatus
                                                                        MGMT                                            LAST                       DAUGHTER
                                          PLATFORM       APPLICATION    REDUNDANCY                    APPLICATION UP    RESTART                    BOARD
NAME     HW TYPE   SERIAL NUM  PART NUM   VERSION        VERSION        ROLE        UP TIME           TIME              REASON      SYNC STATUS    PRESENT
MYSBC-A  SBC 5210  4049120002  821-00430  V06.02.00R000  V06.02.00R000  standby     87 Days 22:45:11  10 Days 22:39:50  switchover  syncCompleted  true
MYSBC-B  SBC 5210  4047120359  821-00430  V06.02.00R000  V06.02.00R000  active      88 Days 00:32:37  27 Days 19:49:49  switchover  syncCompleted  true