Hostnames
Configuring the Hostname of a Device by Using a Configuration Group
The hostname of a Junos OS or Junos OS Evolved device is its identification. A network device must have its identity established to be accessible on the network. That is perhaps the most important reason to have a hostname, but a hostname has other purposes.
The software uses the configured hostname as part of the command prompt and to prepend log files and other accounting information. The hostname is also used anywhere else when knowing the device identity is important. For these reasons, we recommend hostnames be descriptive and memorable.
You can configure the hostname at the [edit system]
hierarchy level, a procedure shown in Configuring a Device’s Unique Identity for the Network. Optionally, instead of configuring the hostname at the [edit
system]
hierarchy level, you can use a configuration group,
as shown in this procedure. This is a recommended best practice for
configuring the hostname, especially if the device has dual Routing
Engines. This procedure uses groups called re0
and re1
as an example.
Starting with Junos OS Release 13.2R3, if you configure hostnames that are longer than the CLI screen width, regardless of the terminal screen width setting, the commit operation occurs successfully. Even if the terminal screen width is less than the hostname length, commit is successful.
In Junos OS releases earlier than Release 13.2R3, if you configured
such hostnames by using the host-name hostname
statement at the [edit system]
hierarchy level
and the the terminal screen width was less than the length of the
hostname by using the set cli screen-width
statement, a
foreign file propagation (ffp) failure error message is displayed
when you attempt to commit the configuration. In such a case, because
of the ffp failure, the commit operation does not complete and you
cannot recover the router unless you make the modification in the
backend in the juniper.conf.gz file
and commit the change from the shell prompt.
To set the hostname using a configuration group:
Mapping the Hostname of the Switch to IP Addresses
To map a hostname of a switch to one or more IP
addresses, include the inet
statement at the [edit
system static-host-mapping hostname]
hierarchy
level:
[edit system] static-host-mapping { hostname { inet [ addresses ]; alias [ aliases ]; } }
hostname is the name
specified by the host-name
statement at the [edit
system]
hierarchy level.
For each host, you can specify one or more aliases.
See Also
Example: Configuring the Name of the Switch, IP Address, and System ID
The following example shows how to configure the switch name, map the name to an IP address and alias, and configure a system identifier:
[edit] user@switch# set system host-name switch1 [edit] user@switch# set system static-host-mapping switch1 inet 192.168.1.77 [edit] user@switch# set system static-host-mapping switch1 alias sj1 [edit] user@switch# set system static-host-mapping switch1 sysid 1921.6800.1077 [edit] user@switch# show system { host-name switch-sj1; static-host-mapping { switch-sj1 { inet 192.168.1.77; alias sj1; sysid 1921.6800.1077; } } }