< Home

display isis last-peer-change

Function

The display isis last-peer-change command displays changes in IS-IS neighbor relationships.

Format

display isis process-id last-peer-change

display isis last-peer-change [ process-id | vpn-instance vpn-instance-name ]

Parameters

Parameter Description Value
process-id Specifies the IS-IS process ID. The value is an integer ranging from 1 to 65535.
vpn-instance vpn-instance-name Displays neighbor information about the multi-instance IS-IS process in the specified VPN instance. The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

The display isis last-peer-change command is used to view the latest at most 100 records on each IS-IS process.

Example

# Display changes in IS-IS neighbor relationships.

<sysname> display isis last-peer-change
                      Peer change information for ISIS(1)
                      -----------------------------------

Time      : 2011-03-28 09:30:34
System Id : 0000.0000.0002
Type      : L1 LAN
Interface : GigabitEthernet0/0/6
State     : IPv4 -> IPv4/IPv6
Details   : Protocol change 
Table 1 Description of the display isis last-peer-change command output

Item

Description

Time

Time at which a neighbor relationship changes

System Id

System ID of the host

Type

Current neighbor type:
  • L1 LAN
  • L2 LAN
  • P2P

Interface

Interface on which an IS-IS neighbor relationship is established

State

Changes in the IS-IS neighbor relationship status:
  • Init -> Up
  • Up -> Down
  • Up -> Init
  • Down -> Up
  • IPv4/IPv6 -> IPv4
  • IPv4/IPv6 -> IPv6
  • IPv4 -> IPv4/IPv6
  • IPv6 -> IPv4/IPv6
  • IPv4 -> IPv6
  • IPv6 -> IPv4
  • L12 -> L2
  • L2 -> L12

Details

Details on IS-IS neighbor relationship changes, including causes:
  • Circuit down
  • BFD down
  • BFD6 down
  • Hold timer expired
  • New adjacency created
  • Clear neighbour
  • Multiple P2P adjacency
  • Adjacency usage mismatch
  • Internal error
  • Memory low
  • P2P circuit ID conflict
  • Area mismatch
  • Three way down
  • Three way init
  • Three way up
  • Protocol change
  • Mt usage mismatch
  • Peer state change
  • Peer level change
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >