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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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 Static Routes

Configuring Static Routes

Static routes are applicable to the networks with simple structures. Proper configuration and usage of static routes improve the network performance and meet the bandwidth requirement of important applications.

Configuring IPv4 Static Routes

On a network, you can accurately control route selection by configuring IPv4 static routes.

Pre-configuration Tasks

Before configuring IPv4 static routes, complete the following task:

  • Configuring link layer parameters and IP addresses for interfaces to ensure network-layer communication between neighbor nodes

Configuration Procedures

You can perform the following configuration tasks (excluding the task of Checking the Configuration) in any sequence as required.

Creating IPv4 Static Routes

Context

When creating static routes, you can specify both the outbound interface and next hop. Alternatively, you can specify only the outbound interface or next hop based on the outbound interface type.
  • Specify the outbound interface for P2P interfaces.

  • Specify the next hop for non broadcast multiple access (NBMA) interfaces.

  • Specify the next hop for broadcast interfaces (for example, Ethernet interfaces).

If you specify the same preference for static routes to the same destination, you can implement load balancing among these routes. If you specify different preferences for static routes, you can implement route backup among the routes.

If the destination IP address and mask are set to all 0s, an IPv4 static default route is configured. By default, no IPv4 static default route is configured.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Configure IPv4 static routes.
    • Run:

      ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] | vpn-instance vpn-instance-name nexthop-address } [ preference preference | tag tag ] * [ permanent ] [ description[ description text ]

      An IPv4 static route is configured on the public network.

    • Run:

      ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } { nexthop-address [ public ] | interface-type interface-number [ nexthop-address ] | vpn-instance vpn-instance-name nexthop-address } [ preference preference | tag tag ] * [ permanent ] [ description[ description text ]

      An IPv4 static route is configured in a VPN instance.

    NOTE:

    To implement load balancing among an Ethernet interface's static route and other static routes, configure the outbound interface and next hop.

  3. Run:

    commit

    The configuration is committed.

(Optional) Setting the Default Preference for IPv4 Static Routes

Context

The default preference of IPv4 static routes affects route selection. When an IPv4 static route is configured, the default preference is used if no preference is specified for the static route.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static default-preference preference

    The default preference of static routes is set.

    By default, the preference of static routes is 60.

    NOTE:

    After the default preference is reconfigured, the new default preference is valid only for new IPv4 static routes.

  3. Run:

    commit

    The configuration is committed.

(Optional) Configuring Static Route Selection Based on Iteration Depth

Context

Route iteration refers to the process of finding the directly-connected outbound interface based on the next hop of a route. The iteration depth indicates the number of times the system searches for routes. A smaller number of route iterations indicates a smaller iteration depth.

When there are multiple static routes with the same prefix but different iteration depths, the system selects the static route with the smallest iteration depth as the active route and delivers it to the FIB table after static route selection based on iteration depth is configured. The other static routes then become inactive. A smaller iteration depth indicates a more stable route.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static selection-rule relay-depth

    Static route selection based on iteration depth is configured.

    By default, static routes are not selected based on iteration depth.

  3. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display static routing-table command to check information about static routes.
  • Run the display ip routing-table command to check brief information about the IPv4 routing table.
  • Run the display ip routing-table verbose command to check detailed information about the IPv4 routing table.

Configuring Dynamic BFD for IPv4 Static Routes

By configuring dynamic BFD to detect IPv4 static routes, you can enable devices to fast detect link changes, improving network reliability.

Pre-configuration Tasks

Before configuring dynamic BFD for IPv4 static routes, complete the following task:

  • Configuring link layer parameters and IP addresses for interfaces to ensure that the link layer protocol on the interfaces is Up

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    bfd

    BFD is enabled globally.

  3. Run:

    quit

    Return to the system view.

  4. (Optional) Run:

    ip route-static default-bfd [ min-rx-interval min-rx-interval ] [ min-tx-interval min-tx-interval ] [ detect-multiplier multiplier ]

    Global BFD parameters are configured for static routes.

    By default, the values of min-rx-interval, min-tx-interval, and detect-multiplier are 1000 ms, 1000 ms, and 3 respectively.

  5. Run:

    ip route-static bfd [ interface-type interface-number ] nexthop-address [ local-address address ] [ min-rx-interval min-rx-interval | min-tx-interval min-tx-interval | detect-multiplier multiplier ] *

    BFD parameters are configured for an IPv4 static route.

    NOTE:

    If interface-type interface-number is not specified, local-address address must be specified.

    If none of min-rx-interval, min-tx-interval, and detect-multiplier is specified, the global default values of BFD parameters are used.

  6. Run:

    ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] } [ preference preference | tag tag ] * bfd enable [ description text ]

    A public network static IPv4 route is bound to a BFD session.

  7. Run:

    commit

    The configuration is committed.

Checking the Configuration

Run the following command to check the configuration.

  • Run the display bfd session { all | discriminator discr-value } [ verbose ] command to check information about the BFD session.

Configuring Static BFD for IPv4 Static Routes

Static BFD for IPv4 static routes enables a device to rapidly detect changes of a link to a destination address of a stack route, improving network reliability.

Pre-configuration Tasks

Before configuring static BFD for IPv4 static routes, complete the following tasks:

  • Configuring link layer parameters and IP addresses for interfaces to ensure network-layer communication between neighbor nodes

  • Configuring BFD sessions

    For details, see "BFD Configuration" in the CX11x&CX31x&CX91x Series Switch Modules - Configuration Guide - Reliability.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] } [ preference preference | tag tag ] * track bfd-session cfg-name [ description text ]

    A public network static IPv4 route is bound to a BFD session.

    NOTE:

    Before binding a static route to a BFD session, ensure that the BFD session and the static route reside on the same link.

  3. Run:

    commit

    The configuration is committed.

Checking the Configuration

Run the following commands to check the previous configuration.

  • Run the display bfd session all [ verbose ] command to check information about the BFD session.

Configuring FRR for IPv4 Static Routes

FRR applies to IP services that are sensitive to packet delay and packet loss. FRR can be configured for IPv4 static routes to implement traffic protection by use of a backup link.

Pre-configuration Tasks

Before configuring FRR for IPv4 static routes, complete the following task:

  • Configuring link layer parameters and IP addresses for interfaces to ensure that the link layer protocol on the interfaces is Up

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ip route-static frr

    FRR is enabled for public network IPv4 static routes.

    NOTE:

    FRR is implemented only on the static routes that are manually configured. That is, FRR cannot be implemented on iterated next hops.

    To implement route backup by configuring FRR for static routes, specify different preferences for these static routes.

    To enable FRR for an Ethernet interface's static route and other static routes, configure the outbound interface and next hop.

  3. Run:

    commit

    The configuration is committed.

Checking the Configuration

Run the following commands to check the previous configuration.

  • Run the display ip routing-table verbose command to check detailed information about the backup outbound interfaces and backup next hops of routes in the routing table.

  • Run the display ip routing-table ip-address [ mask | mask-length ] [ longer-match ] verbose command to check detailed information about the backup outbound interfaces and backup next hops of the routes with specified destination address and mask in the routing table.

  • Run the display ip routing-table ip-address1 { mask1 | mask-length1 } ip-address2 { mask2 | mask-length2 } verbose command to check detailed information about the backup outbound interfaces and backup next hops of routes with specified IP address range in the routing table.

Associating IPv4 Static Routes with NQA

If devices do not support BFD, associate IPv4 static routes with NAQ so that NQA test instances can monitor the link status to improve network reliability.

Pre-configuration Tasks

Before associating IPv4 static routes with NQA, complete the following task:

  • Configuring link layer parameters for interfaces to ensure that the link layer protocol on the interfaces is Up

Procedure

  1. Configure an NQA ICMP test instance.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      nqa test-instance admin-name test-name

      An NQA test instance is created, and the view of the test instance is displayed.

    3. Run:

      test-type icmp

      The test type is set to ICMP.

      NOTE:

      When a static route is associated with an NQA test instance, only ICMP test instances are used to test whether there are reachable routes between the source and destination.

    4. Run:

      destination-address ipv4 ip-address

      The destination address is set.

      In an NQA test instance, you can specify an NQA server by running the destination-address command to configure a destination address for the NQA test instance.

    5. (Optional) Run:

      frequency interval

      The interval for automatically performing an NQA test is set.

      By default, no interval is set, that is, only one test is performed.

    6. (Optional) Run:

      probe-count number

      The number of probes to be sent each time is set for the NQA test instance.

      By default, the number of probes is 3.

      By sending probes multiple times in an NQA test instance, you can accurately estimate network quality based on the collected statistics.

    7. Run:

      start

      The NQA test instance is started.

      The start command can configure an NQA test instance to be started immediately, at a specified time, after a specified delay, or every day. You can perform one of the following operations as required:
      • Run:

        start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]

        The NQA test instance is started immediately.

      • Run:

        start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]

        The NQA test instance is started at a specified time.

      • Run:

        start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]

        The NQA test instance is started after a specified delay.

      • Run:

        start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ]

        The NQA test instance is started every day.

    8. Run:

      commit

      The configuration is committed.

    9. Run:

      quit

      Return to the system view.

  2. Associate static routes with an NQA test instance.
    1. Run:

      ip route-static ip-address { mask | mask-length } { nexthop-address | interface-type interface-number [ nexthop-address ] } [ preference preference | tag tag ] * track nqa admin-name test-name [ description text ]

      IPv4 static routes are associated with an NQA test instance.

      NOTE:

      The destination address of an NQA test instance cannot be the destination address of an associated static route.

      If the static route associated with an NQA test instance is associated with another NQA test instance, the static route is disassociated from the first NQA test instance.

    2. Run:

      commit

      The configuration is committed.

Checking the Configuration

After IPv4 static routes are associated with NAQ, run the following commands to check the configuration.

  • Run the display current-configuration | include nqa command to check the configuration of association between static routes and NQA.

  • Run the display nqa results [ collection ] [ test-instance admin-name test-name ] command to check the NQA test result.

    The NQA test result cannot be displayed automatically. You must run the display nqa results command to view the NQA test result. By default, the command output shows the results of the latest five NQA tests.

Configuring IPv6 Static Routes

On a network, you can accurately control route selection by configuring IPv6 static routes.

Pre-configuration Tasks

Before configuring IPv6 static routes, complete the following task:

  • Configuring link layer parameters and IPv6 addresses for interfaces to ensure network-layer communication between neighbor nodes

Configuration Procedures

You can perform the following configuration tasks (excluding the task of Checking the Configuration) in any sequence as required.

Creating IPv6 Static Routes

Context

When creating static routes, you can specify both the outbound interface and next hop. Alternatively, you can specify only the outbound interface or next hop based on the outbound interface type.
  • Specify the outbound interface for P2P interfaces.

  • Specify the next hop for NBMA interfaces.

  • Specify the outbound interface for broadcast interfaces. If the next hop address is also specified, it does not need to be a link-local address.

If you specify the same preference for static routes to the same destination, you can implement load balancing among these routes. If you specify different preferences for the static routes, you can implement route backup among the routes.

If the destination IP address and mask are set to all 0s, an IPv6 static default route is configured. By default, no IPv6 static default route is configured.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Configure IPv6 static routes.
    • Run:

      ipv6 route-static dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | nexthop-ipv6-address } [ preference preference | tag tag ] * [ description text ]

      An IPv6 static route is configured on the public network.

    • Run:

      ipv6 route-static vpn-instance vpn-instance-name dest-ipv6-address prefix-length { [ interface-type interface-number ] nexthop-ipv6-address | nexthop-ipv6-address [ public ] | vpn-instance vpn-destination-name nexthop-ipv6-address } [ preference preference | tag tag ] * [ description text ]

      An IPv6 static route is configured in a VPN instance.

    NOTE:

    To implement load balancing among an Ethernet interface's static route and other static routes, configure the outbound interface and next hop.

  3. Run:

    commit

    The configuration is committed.

(Optional) Setting the Default Preference for IPv6 Static Routes

Context

The default preference of IPv6 static routes affects route selection. When an IPv6 static route is configured, the default preference is used if no preference is specified for the static route.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ipv6 route-static default-preference preference

    The default preference of IPv6 static routes is set.

    By default, the preference of static routes is 60.

    After the default preference is reconfigured, the new default preference is valid only for new IPv6 static routes.

  3. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display static-route ipv6 routing-table command to check information about IPv6 static routes.
  • Run the display ipv6 routing-table command to check brief information about the IPv6 routing table.
  • Run the display ipv6 routing-table verbose command to check detailed information about the IPv6 routing table.

Configuring FRR for IPv6 Static Routes

FRR applies to IP services that are sensitive to packet delay and packet loss. FRR can be configured for IPv6 static routes to implement link protection.

Pre-configuration Tasks

Before configuring FRR for IPv6 static routes, complete the following task:

  • Configuring link layer parameters and IPv6 addresses for interfaces to ensure that the link layer protocol on the interfaces is Up

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ipv6 route-static frr

    FRR is enabled for public network IPv6 static routes.

    NOTE:

    To implement route backup by configuring FRR for ipv6 static routes, specify different preferences for these static routes.

  3. Run:

    commit

    The configuration is committed.

Checking the Configuration

Run the display ipv6 routing-table verbose command to check information about the backup outbound interfaces and backup next hops of static routes in the routing table.

Configuring Dynamic BFD for IPv6 Static Routes

Dynamic BFD for IPv6 static routes can quickly detect link changes, thus improving network reliability.

Applicable Environment

Preferred IPv6 static routes are delivered to the forwarding table for packet forwarding. An IPv6 static route, however, is incapable of detecting whether or not the link to the next hop is working properly. Binding the IPv6 static route to a BFD session can address this problem, because a BFD session is capable of detecting link changes and informing the routing management module of the changes. If a BFD session detects that a link is interrupted, the routing management module immediately withdraws the IPv6 static route that is bound to the BFD session from the forwarding table and recalculates another active route. In this manner, fast route convergence is implemented.

Pre-configuration Tasks

Before configuring dynamic BFD for IPv6 static routes, complete the following task:

  • Configuring link layer protocol parameters and IPv6 addresses for interfaces to ensure that the link layer protocol on the interfaces is Up

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    bfd

    Global BFD is enabled on the node.

  3. Run:

    quit

    Back to the system view.

  4. (Optional) Run:

    ipv6 route-static default-bfd { min-rx-interval min-rx-interval | min-tx-interval min-tx-interval | detect-multiplier multiplier }*

    The global BFD parameters of the IPv6 static routes on the device are set.

    The default values of the global BFD parameters min-rx-interval, min-tx-interval, and multiplier are 1000 ms, 1000 ms, and 3 respectively.

  5. Run:

    ipv6 route-static bfd [ interface-type interface-number ] nexthop-address [ local-address ipv6-address ] [ detect-multiplier multiplier | min-rx-interval min-rx-interval | min-tx-interval min-tx-interval ]*

    The BFD parameters of an IPv6 static route are set.

    NOTE:

    If interface-type interface-number is not set, local-address ipv6-address must be specified.

    If none of min-rx-interval, min-tx-interval, and detect-multiplier is specified, the global default values of the BFD parameters are used.

  6. Run:

    ipv6 route-static dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | vpn-instance vpn-instance-name nexthop-ipv6-address | nexthop-ipv6-address } [ preference preference | tag tag ]* bfd enable [ description text ]

    A BFD session is bound to an IPv6 static route.

  7. Run:

    commit

    The configuration is committed.

Checking the Configuration

Information about a BFD session can be viewed only after the parameters of the BFD session are set and the BFD session is established.

Run the following commands to check the previous configuration.

  • Run the display bfd session { all | discriminator discr-value } [ verbose ] command to check information about BFD sessions.

  • Run the display current-configuration | include bfd command to check configurations of BFD for IPv6 static routes.

Configuring Static BFD for IPv6 Static Routes

Static BFD for IPv6 static routes enables devices to fast detect link changes, improving network reliability.

Usage Scenario

To use BFD sessions to provide link detection for IPv6 static routes, you can bind IPv6 static routes to BFD sessions. One IPv6 static route can be bound to one BFD session.

Optimal IPv6 static routes are delivered to the forwarding table for packet forwarding. However, IPv6 static routes cannot detect the status of the link to the next hop. You can bind IPv6 static routes to BFD sessions. A BFD session can fast detect changes over a link and inform the routing management system of the changes. The routing management system immediately deletes the static route that is bound to the BFD session from the forwarding table and recalculates another active route. In this manner, fast route convergence is implemented.

Pre-configuration Tasks

Before configuring static BFD for IPv6 static routes, complete the following tasks:

  • Configure link layer protocol parameters and IP addresses for interfaces and ensure that the link layer protocol on the interfaces is Up.

  • Configure a BFD Session. For details, see "BFD Configuration" in the CX11x&CX31x&CX91x Series Switch Modules Configuration Guide-Reliability

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ipv6 route-static dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | vpn-instance vpn-instance-name nexthop-ipv6-address | nexthop-ipv6-address } [ preference preference | tag tag ] * track bfd-session cfg-name [ description text ]

    A BFD session is bound to an IPv6 static route.

  3. Run:

    commit

    The configuration is committed.

Checking the Configurations

Run the following commands to check the previous configuration.

Information about a BFD session can be viewed only after parameters of the BFD session are set and the BFD session is established.

  • Run the display bfd session { all | discriminator discr-value } [ verbose ] command to check information about BFD sessions.

  • Run the display current-configuration | include bfd command to check configurations of BFD for IPv6 static routes.

Associating IPv6 Static Routes with NQA

If devices do not support IPv6 BFD, associate IPv6 static routes with NAQ so that NQA test instances can monitor the link status to improve network reliability.

Pre-configuration Tasks

Before associating IPv6 static routes with NQA, complete the following task:

  • Configuring link layer parameters and IPv6 addresses for interfaces to ensure that the link layer protocol on the interfaces is Up

Procedure

  1. Configure an NQA ICMP test instance.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      nqa test-instance admin-name test-name

      An NQA test instance is created, and the view of the test instance is displayed.

    3. Run:

      test-type icmp

      The test type is set to ICMP.

    4. Run:

      destination-address ipv6 ipv6-address

      A destination address is configured.

      In an NQA test instance, you can specify an NQA server by running the destination-address command to configure a destination address for the NQA test instance.

    5. (Optional) Run:

      frequency interval

      The interval for automatically performing an NQA test is set.

      By default, no interval is set, that is, only one test is performed.

    6. (Optional) Run:

      probe-count number

      The number of probes to be sent each time is set for the NQA test instance.

      By default, the number of probes is 3.

      By sending probes multiple times in an NQA test instance, you can accurately estimate network quality based on the collected statistics.

    7. (Optional) Run:

      interval seconds interval

      The interval at which probe packets are sent is set.

      The default interval is 4 seconds for an NQA ICMP test instance.

      Set the interval based on network quality:

      • If network quality is unsatisfactory, increase the interval to prevent network deterioration caused during the operation of test instances.
      • If network quality is satisfactory, decrease the interval to accelerate the running speed of test instances.

    8. (Optional) Run:

      timeout time

      A timeout period is set for the NQA test instance.

      The default timeout period is 3 seconds.

    9. (Optional) Run:

      fail-percent percent

      A probe failure percentage is set for the NQA test instance.

      The default probe failure percentage is 100%. That is, the test is considered failed only when all probes fail. You can set a probe failure percentage based on network quality.

      NOTE:

      no result may be returned if the following condition is met:

      Interval at which the NQA test is automatically performed ≤ Interval at which probe packets are sent x (Number of sent packets - 1) + Timeout period

      The number of packets sent in an NQA ICMP test instance is the number of probes specified using the probe-count number command.

    10. Run:

      start

      The NQA test instance is started.

      The start command can configure an NQA test instance to be started immediately, at a specified time, or after a specified delay. You can perform one of the following operations as required:
      • Run:

        start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]

        The NQA test instance is started immediately.

      • Run:

        start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]

        The NQA test instance is started at a specified time.

      • Run:

        start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]

        The NQA test instance is started after a specified delay.

      • Run:

        start daily hh:mm:ss to hh:mm:ss [ begin yyyy/mm/dd ] [ end yyyy/mm/dd ]

        The NQA test instance is started every day.

    11. Run:

      commit

      The configuration is committed.

    12. Run:

      quit

      Return to the system view.

  2. Associate static routes with an NQA test instance.
    1. Run:

      ipv6 route-static dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | nexthop-ipv6-address } [ preference preference | tag tag ]* track nqa admin-name test-name [ description text ]

      IPv6 static routes are associated with an NQA test instance.

      NOTE:

      The destination address of an NQA test instance cannot be the destination address of an associated IPv6 static route.

      If the IPv6 static route associated with an NQA test instance is associated with another NQA test instance, the IPv6 static route is disassociated from the first NQA test instance.

    2. Run:

      commit

      The configuration is committed.

Checking the Configuration

After IPv6 static routes are associated with NAQ, run the following commands to check the configuration.

  • Run the display current-configuration | include nqa command to check the configuration of association between static routes and NQA.

  • Run the display nqa results [ test-instance admin-name test-name ] command to check the NQA test result.

    The NQA test result cannot be displayed automatically. You must run the display nqa results command to view the NQA test result. By default, the command output shows the results of the latest five NQA tests.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 57464

Downloads: 3619

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