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
MENU
Support Documentation

NE40E V800R010C10SPC500 Configuration Guide - IP Routing 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP Routing
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).
Configuring Basic IPv4 IS-IS Functions

Configuring Basic IPv4 IS-IS Functions

This section describes how to configure basic IPv4 IS-IS functions.

Usage Scenario

To deploy IS-IS on an IPv4 network, configure basic IS-IS functions for communication between different nodes on the network.

Other IS-IS functions can be configured only after basic IS-IS functions are configured.

Configuring basic IPv4 IS-IS functions includes the following operations:

  1. Create IPv4 IS-IS processes.

  2. Configure IPv4 IS-IS interfaces.

Pre-configuration Tasks

Before configuring basic IPv4 IS-IS functions, complete the following tasks:

  • Configure a link layer protocol.

  • Assign an IP address to each interface to ensure IP connectivity.

Configuration Procedures

Creating an IPv4 IS-IS Process

To configure basic IPv4 IS-IS functions, first create an IPv4 IS-IS process and enable IPv4 IS-IS interfaces.

Context

To create an IPv4 IS-IS process, perform the following operations:

  • Create an IS-IS process and configure the NET of a device.

  • (Optional) Configure the level of a device.

    Configure the device level based on the network planning. If no device level is configured, IS-IS establishes separate neighbor relationships for Level-1 and Level-2 devices and maintains two identical LSDBs, consuming excessive system resources.

  • (Optional) Configure IS-IS host name mapping.

    After IS-IS host name mapping is configured, a host name rather than the system ID of a device is displayed when you run a display command. This configuration improves the maintainability on an IS-IS network.

  • (Optional) Enable IS-IS adjacency strict-check.

    If both IPv4 and IPv6 run on a network, and the IPv6 topology type of this network is standard or compatible, enable IS-IS adjacency strict-check to ensure that an IS-IS adjacency is established only when both IPv4 and IPv6 go Up. IS-IS adjacency strict-check improves network reliability and prevents traffic losses.

  • (Optional) Enable the alarm function for the number of LSPs in the LSDB.

    An IS-IS-capable router may advertise a large number of LSPs due to an excessive number of external routes received because of incorrect configurations or attack packets. In this situation, you can configure alarm and clear alarm thresholds for the number of LSPs in the LSDB. When the proportion of the number of LSPs to the maximum number of LSPs in the LSDB exceeds the alarm threshold, an alarm is generated; when the proportion of the number of LSPs to the maximum number of LSPs in the LSDB falls below the clear alarm threshold, a clear alarm is generated.

  • (Optional) Configure IS-IS to add purge originator identification (POI) TLV to purge LSPs.

    In most cases, a Purge packet (LSP with Remaining Lifetime 0) does not carry any information about the router that generated the Purge packet. Without such information, troubleshooting is difficult if a network problem occurs. To address this issue, you can configure IS-IS to add POI TLV to purge LSPs. If a dynamic hostname has been configured for the local device, the hostname TLV is also added to the purge LSPs, which facilitates troubleshooting.

  • (Optional) Disable automatic IS-IS system ID recovery in case of conflicts.

    If the same system ID is configured for more than one device on the same network, network flapping may occur.

Procedure

  • Create an IS-IS process and configure the NET of a device.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      An IS-IS process is created, and the IS-IS process view is displayed.

      The process-id parameter specifies the ID of an IS-IS process. The default value of process-id is 1. To associate an IS-IS process with a VPN instance, run the isis process-id vpn-instance vpn-instance-name command.

    3. Run network-entity net

      A NET is configured.

      NET of IS-IS consists of three parts:

      • Part one is the area ID that is variable (1 to 13 bytes), and the area IDs of the devices in the same area are identical.

      • Part two is the system ID (6 bytes) of this device, which must be unique in the whole area and backbone area.

      • Part three is the last byte "SEL", whose value must be "00".

      For example, the NET of IS-IS device can be configured as 10.1234.6e9f.0001.00.
      • An area ID is used to uniquely identify an area in the same IS-IS domain. All routers in the same Level-1 area must share the same area ID, while routers in the same Level-2 area can have different area IDs.
      • The system ID must be unique in the whole area and backbone area.
      • When configuring multiple NETs, ensure that they share the same system ID.

      Configuring loopback interface addresses based on NETs is recommended to ensures that a NET is unique on the network. If NETs are not unique, route flapping will easily occur.

      System ID used in IS-IS can be obtained in the following way: extend each part of the IP address to 3 bits, add 0 to the front of any part that is shorter than 3 bits, divide the extended address into three parts, with each part consisting of four decimal digits, and the reconstructed address is the system ID.

    4. (Optional) Run description description

      A description is configured for the IS-IS process.

      Configuring a description for an IS-IS process facilitates device maintenance and management. The description is not advertised through LSPs.

    5. Run commit

      The configuration is committed.

  • (Optional) Configure the level of a device.
    1. Run is-level { level-1 | level-1-2 | level-2 }

      The level of the router is configured.

    2. Run commit

      The configuration is committed.

  • (Optional) Configure IS-IS host name mapping.
    1. Run is-name symbolic-name

      IS-IS dynamic host name mapping is configured. The system ID of the local device is mapped to the specified host name.

      The value of symbolic-name is contained in LSP packets and advertised to other IS-IS devices.

      symbolic-name rather than the system ID of the local IS-IS device is displayed on another IS-IS device.

    2. Run is-name map system-id symbolic-name

      IS-IS static host name mapping is configured. The system ID of a peer IS-IS device is mapped to the specified host name.

      This command configuration takes effect only on the local IS-IS device. The value of symbolic-name will not be added to LSP packets.

      If dynamic host name mappings are configured on an IS-IS network, the mappings on the network override those configured on the local router.

    3. Run commit

      The configuration is committed.

  • (Optional) Enable IS-IS adjacency strict-check.
    1. Run adjacency-strict-check enable

      IS-IS adjacency strict-check is enabled.

    2. Run commit

      The configuration is committed.

  • (Optional) Enable the alarm function for the number of LSPs in the LSDB.
    1. Run lsdb limit limit-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

      The alarm function is enabled for the number of LSPs in the LSDB.

      NOTE:

      upper-limit-value must be greater than or equal to lower-limit-value.

    2. Run commit

      The configuration is committed.

  • (Optional) Configure IS-IS to add POI TLV to purge LSPs.
    1. Run purge-originator-identification enable [ always ]

      IS-IS is configured to add POI TLV to purge LSPs. If a dynamic hostname has been configured for the local device, the hostname TLV is also added to the purge LSPs.

      • If the purge-originator-identification enable command is run and the send-only parameter is specified when configuring authentication, generated purge LSPs do not carry the POI TLV or hostname TLV.

      • If the purge-originator-identification enable command is run and HMAC-MD5 authentication is configured, generated purge LSPs do not carry the POI TLV or hostname TLV. If the purge-originator-identification enable command is run and authentication of another type is configured or no authentication is configured, generated purge LSPs carry the POI TLV and hostname TLV.

      • If the purge-originator-identification enable always command is run, generated purge LSPs carry the POI TLV and hostname TLV, regardless of whether authentication is configured or whether the send-only parameter is specified when configuring authentication.

    2. Run commit

      The configuration is committed.

  • (Optional) Disable automatic IS-IS system ID recovery in case of conflicts.
    1. Run quit

      Return to the system view.

    2. Run isis system-id auto-recover disable

      Automatic IS-IS system ID recovery is disabled in case of conflicts.

    3. Run commit

      The configuration is committed.

Configuring an IPv4 IS-IS Interface

To configure an interface on an IS-IS device to send Hello packets or flood LSPs, IS-IS must be enabled on this interface.

Context

The level of an IS-IS device and level of an interface determine the level of a neighbor relationship. By default, Level-1 and Level-2 neighbor relationships will be established between two Level-1-2 devices. If only one level of neighbor relationships is required, you can configure the level of an interface to prevent the establishment of neighbor relationships of the other level.

After IS-IS is enabled on an interface, the interface will automatically send Hello packets, attempting to establish neighbor relationships. If a peer device is not an IS-IS device or if an interface is not expected to send Hello packets, suppress the interface. Then this interface only advertises routes of the network segment where the interface resides but does not send Hello packets. This suppression improves the link bandwidth usage.

Procedure

  • Configure an IS-IS interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run isis enable [ process-id ]

      An IS-IS interface is configured.

      After this command is run, the IS-IS device uses the specified interface to send Hello packets and flood LSPs.
      NOTE:

      No neighbor relationship needs to be established between loopback interfaces. Therefore, if this command is run on a loopback interface, the routes of the network segment where the loopback interface resides will be advertised through other IS-IS interfaces.

    4. Run commit

      The configuration is committed.

  • (Optional) Configure the level of an IS-IS interface.
    1. Run isis circuit-level [ level-1 | level-1-2 | level-2 ]

      The level of the interface is configured.

      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 IS-IS device is not a Level-1-2, the level of the IS-IS device determines the level of the adjacency to be established.

    2. Run commit

      The configuration is committed.

  • (Optional) Suppress an IS-IS interface.
    1. Run isis silent [ advertise-zero-cost ]

      The IS-IS interface is suppressed.

      A suppressed IS-IS interface does not send or receive IS-IS packets. The routes of the network segment where the interface resides, however, can still be advertised to other routers within the area.

    2. Run commit

      The configuration is committed.

(Optional) Configuring the costs for IPv4 IS-IS Interfaces

Configuring the IS-IS interface costs can control IS-IS route selection.

Context

The link cost of an IS-IS interface can be an interface cost, global cost, or automatically calculated cost which take effect in descending order.

  • The interface cost takes effect only on a specified interface.

  • The global cost takes effect only on all interfaces.

  • The automatically calculated cost is a cost automatically calculated based on the interface bandwidth.

The default cost of an IS-IS interface is 10, and the default cost style is narrow.

Procedure

  • Configure the IS-IS cost type.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      The IS-IS view is displayed.

    3. Run cost-style { { compatible | narrow-compatible } [ relax-spf-limit ] | { narrow | wide | wide-compatible } }

      The IS-IS cost type is configured.

      The cost range of an interface and the cost range of routes that the interface receives vary with the cost style.

      • If the cost type is narrow, the cost of an interface ranges from 1 to 63. The maximum cost of routes that the interface receives is 1023.

      • If the cost style is narrow-compatible or compatible, the cost of an interface ranges from 1 to 63. The cost of routes that the interface receives is related to the parameter relax-spf-limit.

        • If relax-spf-limit is not specified, the route cost is determined by the following rules:

          If the cost of the route is not greater than 1023 and the link cost of every interface through which the route passes is smaller than or equal to 63, the local device accepts the actual cost of the route.

          If the cost of the route is not greater than 1023, but the link cost of an interface through which the route passes is greater than 63, the device can learn only the routes to the network segment where the interface resides and the routes imported by the interface. The local device considers the cost of the route as the actual one and accepts the route but discards subsequent routes forwarded by the interface.

          If the cost of the route is greater than 1023, the device can learn only the routes to the interface on which the link cost of the route exceeds 1023 for the first time. The link cost of each interface through which the route passes before the route reaches this interface is not greater than 63. The local device can learn routes to the network segment where the interface resides and the routes imported by the interface. The local device considers the cost of the routes as 1023 and accept them but discards subsequent routes forwarded by the interface.

        • If relax-spf-limit is specified, the route cost is determined by the following rules:

          There is no limit on link costs of interfaces or route costs. The local device considers the cost of each route as the actual one and accepts the routes.

      • If the cost style is wide-compatible or wide, the cost of the interface ranges from 1 to 16777214 or maximum (16777215). When the cost is maximum, the neighbor TLV with cost 16777215 generated on the link is used for route calculation but for the transmission of TE information. The maximum cost of a received route is 0xFFFFFFFF.

    4. Run commit

      The configuration is committed.

  • Configure the cost for an IS-IS interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run isis [ topology topology-name ] cost cost [ level-1 | level-2 ]

      A cost is configured for IS-IS interface.

      The cost set using the isis cost command takes effect only on this interface.

    4. Run commit

      The configuration is committed.

  • Configure the global IS-IS cost.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      The IS-IS view is displayed.

    3. Run circuit-cost { cost | maximum } [ level-1 | level-2 ]

      The global IS-IS cost is configured.

      The cost set using the circuit-cost command takes effect on all interfaces.

    4. Run commit

      The configuration is committed.

  • Enable IS-IS to automatically calculate interface costs.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      The IS-IS view is displayed.

    3. Run bandwidth-reference value

      The reference value of the bandwidth is configured.

    4. Run auto-cost enable [ compatible ]

      IS-IS is enabled to automatically calculate the interface cost.

      • If the cost style of the system is wide or wide-compatible, when auto-cost enable command is configured, Interface cost = (Bandwidth-reference/Interface bandwidth) x 10, and when auto-cost enable compatible command is configured, Interface cost = (Bandwidth-reference/Interface bandwidth).
        NOTE:

        If the interface cost calculated through this formula is greater than 16777214, 16777214 is used as the interface cost for route calculation. That is, the interface cost will never be greater than 16777214.

        The auto-cost enable command can be run on Eth-Trunk interfaces as same with on physical interfaces. If the command is run on an Eth-Trunk interface, the bandwidth of the Eth-Trunk interface is equal to the total bandwidth of all its member interfaces.

      • If the cost-style is narrow, narrow-compatible, or compatible, the cost of each interface is determined by the interface bandwidth range. Table 9-1 lists the interface costs corresponding to different interface bandwidth ranges.

        Table 9-1 Mapping between IS-IS interface costs and interface bandwidth

        Cost

        Bandwidth Range

        60

        Interface bandwidth ≤ 10 Mbit/s

        50

        10 Mbit/s < interface bandwidth ≤ 100 Mbit/s

        40

        100 Mbit/s < interface bandwidth ≤ 155 Mbit/s

        30

        155 Mbit/s < interface bandwidth ≤ 622 Mbit/s

        20

        622 Mbit/s < Interface bandwidth ≤ 2.5 Gbit/s

        10

        Interface bandwidth > 2.5 Gbit/s
      NOTE:

      To change the cost of a loopback interface, run the isis cost command only in the loopback interface view.

    5. Run commit

      The configuration is committed.

(Optional) Configuring IPv4 IS-IS Attributes on Networks of Different Types

Different IS-IS attributes can be configured for different types of network interfaces.

Context

The establishment mode of IS-IS neighbor relationships on a broadcast network is different from that 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 is 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. If the type of an interface on the neighbor is P2P, you can configure the interface type 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. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run isis dis-priority priority [ level-1 | level-2 ]

      The DIS priority is configured on the interface. The greater the value, the higher the priority.

    4. (Optional) Run isis dis-name symbolic-name

      A name is configured for the DIS to facilitate maintenance and management.

    5. Run commit

      The configuration is committed.

  • Configure the network type of an IS-IS interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run isis circuit-type p2p

      The network type of the interface is set to P2P.

      When the network type of an IS-IS interface changes, interface configurations change accordingly.

      • After a broadcast interface is configured as a P2P interface using the isis circuit-type p2p command, the default values of the interval at which Hello packets are sent, the number of Hello packets that IS-IS fails to receive from a neighbor before declaring the neighbor Down, the interval LSPs are retransmitted on a P2P link, and various IS-IS authentication modes take effect. Consequently, other configurations such as the DIS priority, DIS name, and interval at which CSNPs are sent on a broadcast network become invalid.

      • After the undo isis circuit-type command is run to restore the network type, the default values of the interval at which Hello packets are sent, the number of Hello packets that IS-IS fails to receive from a neighbor before declaring the neighbor Down, the interval LSPs are retransmitted on a P2P link, the IS-IS authentication mode, the DIS priority, and the interval at which CSNPs are sent on a broadcast network take effect.

    4. Run commit

      The configuration is committed.

  • Set the negotiation mode for the establishment of neighbor relationships.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

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

      The negotiation mode is specified on the interface.

      The isis ppp-negotiation command can only be used for the establishment of the neighbor relationships on P2P links. In the case of a broadcast link, you can run the isis circuit-type p2p command to set the link type to P2P, and then run the isis ppp-negotiation command to set the negotiation mode for the establishment of the neighbor relationship.

    4. Run commit

      The configuration is committed.

  • Configure OSICP negotiation check on PPP interfaces.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run isis ppp-osicp-check

      The OSICP negotiation status is checked on a PPP interface.

      The isis ppp-osicp-check command is applicable only to PPP interfaces. This command 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 route to the network segment where the interface resides is not advertised through LSPs.

    4. Run commit

      The configuration is committed.

  • Configure the scale of the Hello packets sent on the IS-IS interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

      NOTE:

      3 and 4 are mutually exclusive. Run the command as needed.

    3. Run isis small-hello

      The Hello packets without the padding field are configured to be sent on the interface.

    4. Run isis padding-hello

      The standard Hello packets without the padding field are configured to be sent on the interface.

    5. Run commit

      The configuration is committed.

  • Prevent IS-IS from checking whether the IP addresses of received Hello packets are on the same network segment.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run isis peer-ip-ignore

      IS-IS is prevented from checking whether the IP addresses of received Hello packets are on the same network segment.

    4. Run commit

      The configuration is committed.

(Optional) Enabling LSP Fragment Extension on an IPv4 IS-IS Device

If the LSP capacity is insufficient, newly imported routes and new TLVs fail to be added to LSP fragments. In this case, you can use LSP fragment extension to increase the LSP capacity, restoring the LSP space. When the LSP space is restored, the system automatically attempts to re-add these routes and TLVs to LSP fragments.

Context

The lsp-fragments-extend command enables LSP fragment extension on an IS-IS device in a specified mode and at a specified level. One LSP fragment occupies only one byte and therefore a maximum of 256 fragments are supported. If there are a great number of LSPs and the number of fragments exceeds 256, some information is lost. LSP fragment extension is introduced to address such a problem. You can run the virtual-system command to configure one or more virtual systems to support more than 256 LSP fragments.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run isis [ process-id ]

    An IS-IS process is created, and the IS-IS process view is displayed.

  3. Run lsp-fragments-extend [ [ level-1 | level-2 | level-1-2 ] | [ mode-1 | mode-2 ] ] *

    LSP fragment extension is enabled on an IS-IS device, and a specified mode and level are specified.

(Optional) Enabling the Type-132 TLV in LSPs to Carry the IPv4 Address of Only One IS-IS Interface

To implement interworking between Huawei and non-Huawei devices, you need to enable the type-132 TLV in LSPs to carry the IP address of only one IS-IS interface on the Huawei device.

Context

By default, on Huawei devices, the type-132 TLV in LSPs carries the IP addresses of all IS-IS interfaces. However, on some non-Huawei devices, the type-132 TLV in LSPs carries the IP address of only one IS-IS interface. To implement interworking between Huawei devices and these non-Huawei devices, enable the type-132 TLV in LSPs to carry the IP address of only one IS-IS interface on the Huawei devices.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run isis [ process-id ]

    An IS-IS process is created, and its view is displayed.

  3. Run advertise one-interface-address

    The type-132 TLV in LSPs is enabled to carry the IP address of only one IS-IS interface.

  4. Run commit

    The configuration is committed.

Verifying the Basic IPv4 IS-IS Configuration

After configuring basic IPv4 IS-IS functions, check information about IS-IS neighbors, interfaces, and routes.

Prerequisites

The configurations of basic IPv4 IS-IS functions are complete.

Procedure

  1. Run the display isis name-table [ process-id | vpn-instance vpn-instance-name ] command to check the mapping from the name of the local device to the system ID.
  2. Run the display isis peer [ verbose ] [ process-id | vpn-instance vpn-instance-name ] command to check information about IS-IS neighbors.
  3. Run the display isis interface [ verbose ] [ process-id | vpn-instance vpn-instance-name ] command to check information about IS-IS interfaces.
  4. Run the display isis route [ process-id | vpn-instance vpn-instance-name ] [ ipv4 ] [ verbose | [ level-1 | level-2 ] | ip-address [ mask | mask-length ] ] * command to check information about IS-IS routes.

Example

Run the display isis name-table command to view the mappings between host names and system IDs.

<HUAWEI> display isis name-table
                       Name table information for ISIS(1) Level-1



System ID            Hostname                            Type
-------------------------------------------------------------------------------
1111.1111.1111       DeviceA                             DYNAMIC
2222.2222.2222       DeviceB                             DYNAMIC

Run the display isis peer command. The command output shows the status of an IS-IS neighbor, DeviceB. System Id is displayed as DeviceB.

<HUAWEI> display isis peer

Run the display isis interface verbose command to view information about IS-IS interfaces. The command output shows that the DIS status of a broadcast interface is Yes, the priority of the DIS is 20, and that the cost of the interface is 30.

<HUAWEI> display isis interface verbose
  Suppress Base               :  NO
  IPv6 Suppress Base          :  NO

  Extended-Circuit-Id Value   :  0000000000
  Circuit State               :  OSI:UP   / IP:UP   / MTU:UP   / IPBorrow:UP   /
                                 BandWidth:UP   / IsEnable:UP   / Interface:UP  
  Circuit Ipv6 State          :  OSI:UP   / IP:UP   / MTU:UP   / IPBorrow:UP   /
                                 BandWidth:UP   / IsEnable:DOWN / Interface:UP

Run the display isis route command to view information about IS-IS routes. The command output shows a route with destination network segment 12.1.1.0/24 and next hop address 23.1.1.0/24.

<HUAWEI> display isis route
                         Route information for ISIS(1)
                         -----------------------------

                        ISIS(1) Level-2 Forwarding Table
                        --------------------------------

IPV4 Destination     IntCost    ExtCost ExitInterface   NextHop         Flags
-------------------------------------------------------------------------------
12.1.1.0/24          40         NULL    GE1/0/2         23.1.1.1        A/-/-/-
23.1.1.0/24          10         NULL    GE1/0/2         Direct          D/-/L/-

     Flags: D-Direct, A-Added to URT, L-Advertised in LSPs, S-IGP Shortcut,
                               U-Up/Down Bit Set
Translation
简体中文
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 53994

Downloads: 209

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

Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.