Monitoring Is-Is; System Event Logs - Juniper IGP - CONFIGURATION GUIDE V11.1.X Configuration Manual

IS-IS routing after you issue the protocol shutdown command, you can continue to
configure IS-IS.
Issuing the protocol shutdown command:
NOTE: Rebooting the router does not affect the state of the IS-IS protocol.
protocol shutdown

Monitoring IS-IS

The CLI has commands available for monitoring IS-IS parameters and CLNS
parameters.

System Event Logs

To troubleshoot and monitor IP, use the following system event logs:
Clears the LSP database
Removes all IS-IS routes in the routing information database (RIB)
Deletes all adjacencies with the IS-IS instance
Use to disable the IS-IS protocol without removing the IS-IS configuration.
Example
host1(config-router)#protocol shutdown
Use the no version to reenable the IS-IS protocol.
See protocol shutdown
isisAdjChange IS-IS adjacency up or down events
isisAdjPackets IS-IS adjacency hello packets
isisBfdEvents IS-IS interactions with BFD
isisChecksumErr IS-IS checksum errors
isisGeneral IS-IS system notifications
isisHelloGeneral IS-IS system notifications
isisHelloPackets IS-IS hello packets
isisipv6Log IS-IS IPv6 notifications
isisLdpEvents IS-IS interactions with LDP
isisLocalUpdate IS-IS local LSP packets
isisMplsTeAdvertisements IS-IS MPLS traffic engineering advertisements
isisMplsTeEvents IS-IS MPLS traffic engineering
Chapter 6: Configuring IS-IS
387
Monitoring IS-IS