Configuring dynamic system id to host name mapping, Enabling the logging of neighbor state changes – H3C Technologies H3C SR8800 User Manual

Page 182

Advertising
background image

166

Step Command

Remarks

3.

Configure a system ID to host
name mapping for a remote

IS.

is-name map sys-id map-sys-name

A system ID can only correspond to
a host name.

Configuring dynamic system ID to host name mapping

You need to configure a static system ID to host name mapping for any other router in a network. When

a new router is added into the network or a mapping needs to be modified, perform configuration on all

routers.
You can configure dynamic system ID to host name mapping. To do so, you must configure a host name

for each router in the network. Each router advertises the host name in dynamic host name CLVs to other
routers. At last, all routers in the network have all the mappings to generate a mapping table.
In addition, you can configure a name for the DIS in a broadcast network to help check the origin of LSPs

in the LSDB.
To configure dynamic system ID to host name mapping:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter IS-IS view.

isis [ process-id ] [ vpn-instance
vpn-instance-name ]

N/A

3.

Specify a host name
for the router.

is-name sys-name

No specified by default.

4.

Return to system view.

quit

N/A

5.

Enter interface view.

interface interface-type
interface-number

N/A

6.

Configure a DIS name. isis dis-name symbolic-name

Optional.
Not configured by default.
This command takes effect only on a
router with dynamic system ID to host

name mapping configured.
This command is not supported on P2P

interfaces.

Enabling the logging of neighbor state changes

To enable the logging of neighbor state changes:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter IS-IS view.

isis [ process-id ] [ vpn-instance
vpn-instance-name ]

N/A

3.

Enable the logging of
neighbor state changes.

log-peer-change

Enabled by default

Advertising