Page History
| Noprint | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
In this section:
|
System Name Conventions
The following table lists system naming conventions to follow while setting up SBC 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:
...
...
| 0 | Table |
|---|---|
| 1 | SBC System Name Conventions |
| 3 | SBCHNC |
...
Hostname 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.
| 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. |
| Note |
|---|
Hostname is also referred to as "ceName". For example, "local ceName" and "peer ceName" are the equivalent of "local hostname" and "peer hostname". |
...
| 0 | Table |
|---|---|
| 1 | SBC Hostname Conventions |
| 3 | SBCHNC |
...
(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.
...
| class | pdf6pttext |
|---|
...
| language | none |
|---|
...
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
| Pagebreak |
|---|
Overview
Content Tools