Description

This article explains why chassis cluster nodes may not display the right system host-name after setting the system host-name under global system level.

Symptoms

The host-name of my chassis cluster nodes are not displayed as expected. This causes confusion when checking the device status and system logs.

Example: 

root@SRX220# show | display set

set groups node0 system host-name SRX220_1 <--here, the expected host-name
set groups node1 system host-name SRX220_2 <--here, the expected host-name
set apply-groups "${ NODE }"
set system host-name SRX220 <-- here, the unexpected host-name 
set chassis cluster redundancy-group 0 node 0 priority 250
set chassis cluster redundancy-group 0 node 1 priority 100
set interfaces fab0 fabric-options member-interfaces ge-0/0/5
set interfaces fab1 fabric-options member-interfaces ge-3/0/5

root@SRX220# run show log messages
Aug 5 03:27:27 SRX220 mgd[3119]: UI_CMDLINE_READ_LINE: User 'root', command 'run show log messages '

Solution

Do not set system host-name XXX again in the global CLI level.

Example: 

set groups node0 system host-name SRX220_1
set groups node1 system host-name SRX220_2
set apply-groups "${ NODE }"
set system syslog file messages any any
set chassis cluster redundancy-group 0 node 0 priority 250
set chassis cluster redundancy-group 0 node 1 priority 100
set interfaces fab0 fabric-options member-interfaces ge-0/0/5
set interfaces fab1 fabric-options member-interfaces ge-3/0/5

{primary:node0}[edit]
root@SRX220_1# run show log messages
Aug 5 03:31:08 SRX220_1 mgd[3119]: UI_CMDLINE_READ_LINE: User 'root', command 'run show log messages '

Modification History

2020-06-12: Article reviewed for accuracy; no changes required.

Related Information