No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - IP Unicast Routing

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Establishing IS-IS Neighbor Relationships

Establishing IS-IS Neighbor Relationships

Context

The methods to establish IS-IS neighbor relationships on a broadcast network and a P2P network are different. Therefore, you need to set different IS-IS attributes for interfaces of different types:
  • On a broadcast network, IS-IS needs to select the designated intermediate system (DIS). You can set the DIS priority for IS-IS interfaces to enable the device with the highest DIS priority to be elected as the DIS.

  • On a P2P network, IS-IS does not need to select the DIS. Therefore, the DIS priority does not need to be configured for interfaces. To ensure P2P link reliability, configure IS-IS to establish neighbor relationships on P2P interfaces in 3-way mode for unidirectional link fault detection.

    Generally, IS-IS checks the IP addresses of received Hello packets. Neighbor relationships can be established only when the IP address carried in a received Hello packet and the address of the interface that receives the Hello packet are on the same network segment. If the IP addresses of the two P2P interfaces are on different network segments, and the isis peer-ip-ignore command is run on the two interfaces, IS-IS does not check the peer IP address. The neighbor relationship can be correctly established on the two P2P interfaces.

Procedure

  • Establish an IS-IS neighbor relationship on a broadcast link.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ipv6 enable

      IPv6 is enabled on the interface.

    5. Run isis ipv6 enable [ process-id ]

      IPv6 is enabled on the interface.

      After this command is run, IS-IS establishes neighbor relationships and floods LSPs through this interface.
      NOTE:

      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.

    6. Run isis circuit-level [ level-1 | level-1-2 | level-2 ]

      The level of the interface is configured.

      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.

      NOTE:

      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.

    7. (Optional) Run isis dis-priority priority [ level-1 | level-2 ]

      The DIS priority is set for the interface. A larger value indicates a higher priority.

      By default, the DIS priority of Level-1 and Level-2 broadcast interfaces is 64.

    8. (Optional) Run isis silent

      The interface is suppressed.

      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.

    9. Run commit

      The configuration is committed.

  • Establish an IS-IS neighbor relationship on a P2P link.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    4. Run ipv6 enable

      IPv6 is enabled on the interface.

    5. Run isis ipv6 enable [ process-id ]

      IPv6 IS-IS is enabled on the interface.

    6. Run isis circuit-level [ level-1 | level-1-2 | level-2 ]

      The level of the interface is configured.

      By default, the level of an interface is Level-1-2.

    7. Run isis circuit-type p2p

      The network type of the interface is set to 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.

    8. Run isis ppp-negotiation { 2-way | 3-way [ only ] }

      The negotiation mode is specified for the interface.

      By default, the negotiation mode is 3-way.

    9. Run isis peer-ip-ignore

      IS-IS is configured not to check the IP addresses of received Hello packets.

      By default, IS-IS checks the IP addresses of received Hello packets.

    10. Run isis ppp-osicp-check

      OSICP negotiation status check is configured on the interface.

      By default, the OSICP negotiation status of a PPP interface does not affect the status of an IS-IS interface.

      NOTE:

      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.

    11. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074760

Views: 45399

Downloads: 58

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next