Enabling IPv6 IS-IS for Interfaces of Different Network Types

An interface can send IPv6 Hello packets to establish neighbor relationships and floods LSPs only after you enable IPv6 IS-IS on it. You can configure different IS-IS attributes for interfaces of different network types.

Context

The establishment modes of IS-IS neighbor relationships are different on a broadcast network and on a P2P network. Different IS-IS attributes can be configured for interfaces on different types of networks.

IS-IS is required to select a DIS on a broadcast network. Configure the DIS priorities of IS-IS interfaces so that the interface with the highest priority will be selected as the DIS.

The network types of the IS-IS interfaces on both ends of a link must be the same; otherwise, the IS-IS neighbor relationship cannot be established between the two interfaces. For example, if the type of an interface on a peer device is P2P, you can configure the type of an interface on the local device to P2P so that an IS-IS neighbor relationship can be established between the two devices.

IS-IS on a P2P network is not required to select a DIS. Therefore, you do not need to configure DIS priorities. To ensure the reliability of P2P links, configure IS-IS to use the three-way handshake mode for IS-IS neighbor relationship establishment so that faults on a unidirectional link can be detected.

Procedure

Configure the DIS priority of an IS-IS interface.
1. Access the system view.
  system-view
2. Access the interface view.
  interface interface-type interface-number
3. Enable IPv6 on the interface.
  ipv6 enable
4. Enable IPv6 IS-IS on the interface.
  isis ipv6 enable [ process-id ]
  
  After this command is run, IS-IS establishes neighbor relationships and floods LSPs through this interface.
  
  Loopback interfaces are not used to establish neighbor relationships. If IS-IS is enabled on a loopback interface, IS-IS advertises the routes of the network segment where the interface resides through other IS-IS interfaces.
5. Set the level of the interface.
  isis circuit-level [ level-1 | level-1-2 | level-2 ]
  
  By default, the level of an interface is Level-1-2.
  
  When two Level-1-2 devices establish IS-IS neighbor relationship, they establish both Level-1 and Level-2 neighbor relationships. To allow the two Level-1-2 devices to establish only Level-1 or Level-2 neighbor relationship, change the level of interfaces.
  
  Changing the level of an IS-IS interface is valid only when the level of the IS-IS device is Level-1-2. If the level of the device is not Level-1-2, the level of the device determines the level of the established neighbor relationship.
6. (Optional) Set a DIS priority for the interface.
  isis dis-priority priority [ level-1 | level-2 ]
  
  A larger value indicates a higher priority.
  
  By default, the DIS priority of Level-1 and Level-2 broadcast interfaces is 64.
7. (Optional) Suppress the interface.
  isis silent [ advertise-zero-cost ]
  
  By default, an IS-IS interface is not suppressed.
  
  When an IS-IS interface is suppressed, the interface no longer sends or receives IS-IS packets. The routes of the network segment where the interface resides, however, can still be advertised to other IS-IS devices within the same AS.
Establish an IS-IS neighbor relationship on a P2P link.
1. Access the system view.
  system-view
2. Access the interface view.
  interface interface-type interface-number
3. Enable IPv6 on the interface.
  ipv6 enable
4. Enable IPv6 IS-IS on the interface.
  isis ipv6 enable [ process-id ]
5. Configure the level of the interface.
  isis circuit-level [ level-1 | level-1-2 | level-2 ]
  
  By default, the level of an interface is Level-1-2.
6. Set the network type of the interface to P2P.
  isis circuit-type p2p
  
  By default, the network type of an interface is determined by the physical type of the interface.
  
  When the network type of an IS-IS interface changes, the interface configuration changes accordingly:
  - After a broadcast interface is simulated as a P2P interface using the isis circuit-type p2p command, the interval for sending Hello packets, number of Hello packets that IS-IS does not receive from a neighbor before the neighbor is declared Down, interval for retransmitting LSPs on a P2P link, and various IS-IS authentication modes are restored to the default settings; other configurations such as the DIS priority, DIS name, and interval for sending CSNPs on a broadcast network become invalid.
  - After the undo isis circuit-type command is run to restore the default network type of an IS-IS interface, the interval for sending Hello packets, number of Hello packets that IS-IS does not receive from a neighbor before the neighbor is declared Down, interval for retransmitting LSPs on a P2P link, various IS-IS authentication modes, DIS priority, and interval for sending CSNPs on a broadcast network are restored to the default settings.
7. Set the negotiation mode for the interface.
  isis ppp-negotiation { 2-way | 3-way [ only ] }
  
  By default, the negotiation mode is 3-way.
8. Configure IS-IS not to check the IP addresses of received Hello packets.
  isis peer-ip-ignore
  
  By default, IS-IS checks the IP addresses of received Hello packets.
9. Configure OSICP negotiation status check on the interface.
  isis ppp-osicp-check
  
  By default, the OSICP negotiation status of a PPP interface does not affect the status of an IS-IS interface.
  
  This command applies only to PPP interfaces and is invalid for other P2P interfaces.
  
  After this command is run, the OSICP negotiation status of a PPP interface affects the status of an IS-IS interface. When PPP detects that the OSI network fails, the link status of the IS-IS interface goes Down and the routes of the network segment where the interface resides are not advertised through LSPs.