Page History

Panel

In this section:

Table of Contents

maxLevel	4

Excerpt

System Naming Conventions

The following table lists system naming conventions to follow while setting up

Spacevars

0	series4

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.

Convention/Character	System Name	Use as Leading Character	Use as Trailing Character
Maximum number of characters	26	N/A	N/A
Letters [ a-z ] \| [ A-Z ]
Digits [ 0-9 ]
Hyphen [ - ]
Period [ . ]
Underscore [ _ ]
Other special characters

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.

Info

title	Note

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.

Info

title	Note

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

Convention/Character	Hostname / Peer Hostname	Use as Leading Character	Use as a Trailing Character
Maximum number of characters	64	N/A	N/A
Letters [ a-z ] \| [ A-Z ]
Digits [ 0-9 ]
Hyphen [ - ]
Period [ . ]¹
Underscore [ _ ]²
Other special characters

(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.
(results are shortened for brevity)

Div

class	pdf6pttext

Code Block

language	none

admin@MYSBC-B> show table system serverStatus
                                                                        MGMT                                            LAST                       DAUGHTER
     

NAME   HW TYPE                 SERIAL NUM                     PLATFORM       APPLICATION    REDUNDANCY                    APPLICATION UP    RESTART                    BOARD
NAME     HW TYPE   SERIAL NUM  PART NUM   VERSION        VERSION        ROLE        UP TIME          TIME  TIME           REASON   REASON      SYNC STATUS    PRESENT

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
MYSBC-A ---
vsbc1  Sonus SBC 5210SWe  4049120002BCA90399-FC5B-431D-BD11-E44630812070  821-00430     V06V12.0200.00R00000A008  V06V12.0200.00R00000A008  active standby     876 Days 2200:4559:1105  106 Days 2200:3956:5037  switchoverserverRestart  syncCompleted
vsbc2  true
MYSBC-BSonus  SBC 5210SWe  40471203592203A41B-CBCF-41BD-B280-A3700F0690CA  821-00430     V06V12.0200.00R00000A008  V06V12.0200.00R00000A008  activestandby      886 Days 00:3259:3706  276 Days 1900:4954:4917  switchoverserverRestart  syncCompleted  true

Space shortcuts

Page tree

Versions Compared

Old Version 1

New Version Current

Key

System Naming Conventions

Hostname Naming Conventions

Viewing Local Hostname and and Peer Hostname From CLI