Enabling adjacency change logging – H3C Technologies H3C S10500 Series Switches User Manual

Page 25

Advertising
background image

18

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter EVI IS-IS process view.

evi-isis process-id

N/A

3.

Specify a routing policy for the
EVI IS-IS process.

filter-policy policy-name

By default, an EVI IS-IS process is
not associated with any routing

policy.

Enabling adjacency change logging

Adjacency change logging enables an EVI IS-IS process to send a log message to the information center

when an adjacency change occurs. With the information center, you can set log message filtering and

output rules, including output destinations. For more information about using the information center, see

Network Management and Monitoring Configuration Guide.
To enable adjacency change logging:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter EVI IS-IS process view.

evi-isis process-id

N/A

3.

Enable adjacency change
logging.

log-peer-change enable

By default, adjacency change
logging is enabled.

Configuring Graceful Restart for an EVI IS-IS process

Enable Graceful Restart for the peer EVI IS-IS processes at two ends of an EVI tunnel to guarantee

nonstop forwarding while the peer EVI IS-IS processes are re-establishing their adjacency after a process
restart or active/standby switchover occurs.
If Graceful Restart is enabled, the adjacency hold time equals the greater of the following values:

The restart interval.

The EVI IS-IS hello interval multiplied by the hello multiplier.

If the edge device is a DED, its hello interval is one-third of the hello interval set by using the evi isis timer

hello command.
To configure Graceful Restart for an EVI IS-IS process:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter EVI IS-IS process
view.

evi-isis process-id

N/A

3.

Enable Graceful Restart.

graceful-restart

By default, EVI IS-IS Graceful Restart is
disabled.

Advertising