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

ME60 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is ME60 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 IPv6 Static Route Detection

Configuring IPv6 Static Route Detection

With IPv6 static route detection, if a link through which an IPv6 static route travels fails, a rapid link switchover is performed, preventing lengthy service interruptions.

Usage Scenario

Unlike dynamic routes, static routes do not have a detection mechanism. As a result, administrator intervention is required if a fault occurs on the network. To prevent the need for administrator intervention, deploy IPv6 static route detection to implement automatic rapid link switchover if a link failure occurs. IPv6 static route detection prevents lengthy service interruptions.

The following IPv6 static route detection methods are available:

  • BFD for IPv6 static routes: After BFD for IPv6 static routes is configured, each static route can be bound to a BFD session. BFD for IPv6 static routes implements millisecond-level detection. BFD is classified as static BFD or dynamic BFD.
  • Network quality analysis (NQA) for IPv6 static routes: Although BFD for IPv6 static routes implements fast link fault detection, it cannot be deployed in some scenarios (when Layer 2 devices exist on the network, for example) because both ends of the link must support BFD. NQA for IPv6 static routes, however, can monitor the link status of a static route even when only one end supports NQA. NQA for IPv6 static routes implements second-level detection.
    NOTE:

    Only one of the IPv6 static route detection methods can be deployed. Therefore, choose one based on the live network requirements.

Pre-configuration Tasks

Before configuring IPv6 static route detection, configure link-layer protocol parameters and IPv6 addresses for interfaces to ensure that the link layer protocol of each interface is Up.

Configuring Dynamic BFD for IPv6 Static Routes

Dynamic 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 on the public network, you can bind 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 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, configure parameters of the link layer protocol and IPv6 addresses for interfaces and 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

    Return to the system view.

  4. (Optional) Run ipv6 route-static default-bfd [ detect-multiplier multiplier ] [ min-rx-interval min-rx-interval ] [ min-tx-interval min-tx-interval ]

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

  5. Run ipv6 route-static bfd [ interface-type interface-number | vpn-instance vpn-destination-name ] nexthop-address local-address 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, or detect-multiplier is specified, the default values of the BFD parameters are used globally.

  6. Run either of the following commands as required:

    • Run ipv6 route-static dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | vpn-instance vpn-destination-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 on the public network.

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

      A BFD session is bound to an IPv6 static route on the VPN network.

    NOTE:

    The outbound interface and next hop IP address specified when binding the IPv6 static route to a BFD session must be the same as those specified when configuring BFD parameters for the IPv6 static route.

  7. Run commit

    The configuration is committed.

Checking the Configurations

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.

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

    If a BFD session has been established, the status of the BFD session is Up. Run the display current-configuration | include bfd command in the system view, and you can see that the BFD session has been bound to a static route.

# Run the display bfd session command. The following command output shows that the BFD session is in the Up state.

<HUAWEI> display bfd session all
(w): State in WTR 
(*): State is invalid
--------------------------------------------------------------------------------
Local  Remote PeerIpAddr      State     Type      InterfaceName
--------------------------------------------------------------------------------
10    20      2001:db8:1::2   Up    S_IP_PEER  -
--------------------------------------------------------------------------------
     Total UP/DOWN Session Number : 1/0

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 on the public network, 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 HUAWEI ME60 Multiservice Control Gateway Configuration Guide - Network Reliability.

Procedure

  • Configure a BFD Session.
    1. Run system-view

      The system view is displayed.

    2. Run bfd

      BFD is globally enabled.

    3. Run quit

      The system view is displayed.

    4. Run bfd session-name bind peer-ipv6 ipv6-address

      The binding between a BFD session for IPv6 and a peer IPv6 address is created and the BFD session view is displayed.

    5. Run discriminator local discr-value

      The local discriminator of a static BFD session is set.

    6. Run discriminator remote discr-value

      The remote discriminator of a static BFD session is set.

      NOTE:

      For details of optional procudures when configuring BFD session, See the HUAWEI ME60 Multiservice Control Gateway Configuration Guide - Network Reliability.

    7. Run commit

      The configuration is committed.

  • Associating an IPv6 Static Route with a BFD Session.
    1. Run system-view

      The system view is displayed.

    2. Run either of the following commands as required:

      • 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 on the public network.

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

        A BFD session is bound to an IPv6 static route on the VPN network.

    3. Run commit

      The configuration is committed.

Checking the Configurations

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.

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

    If a BFD session has been established, the status of the BFD session is Up. Run the display current-configuration | include bfd command in the system view, and you can see that the BFD session has been bound to a static route.

# Run the display bfd session command. The following command output shows that the BFD session is in the Up state.

<HUAWEI> display bfd session all
(w): State in WTR 
(*): State is invalid
--------------------------------------------------------------------------------
Local  Remote PeerIpAddr      State     Type      InterfaceName
--------------------------------------------------------------------------------
10    20      2001:db8:1::2   Up    S_IP_PEER  -
--------------------------------------------------------------------------------
     Total UP/DOWN Session Number : 1/0

Configuring NQA for IPv6 Static Routes

If a IPv6 static route is associated with a network quality analysis (NQA) test instance, NQA tests the link status periodically. If NQA detects a fault along the associated IPv6 static route, the IPv6 static route is deleted, and traffic is switched to another route.

Usage Scenario

On live networks, the link status of IPv6 static routes must be monitored in real time so that a link switchover can be performed immediately if a link fails. Bidirectional Forwarding Detection (BFD) for IPv6 static routes can implement detection within milliseconds. However, BFD for IPv6 static routes requires that both ends of a link support BFD.

NQA for IPv6 static routes can monitor the link status of static routes as long as one end supports NQA.

If a link fails, an NQA test instance immediately detects the fault and instructs the routing management module to delete the IPv6 static route associated with the NQA test instance from the IPv6 routing table. Traffic is then forwarded over another link.

Pre-configuration Tasks

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

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

Procedure

  • Configuring an ICMP NQA 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 test instance view 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.

      Once you configure a destination address for the NQA test instance, an NQA server is specified.

    5. Run any of the following commands:

      • 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 } } ]
      • 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 } } ]
      • start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } } ]
      • start daily hh:mm:ss to hh:mm:ss [ begin { yyyy/mm/dd | yyyy-mm-dd } ] [ end { yyyy/mm/dd | yyyy-mm-dd } ]

      An NQA test instance is started.

      NOTE:

      For details of optional procedures when configuring an ICMP NQA test instance, see the HUAWEI ME60 Multiservice Control Gateway Configuration Guide - System Monitor.

    6. Run commit

      The configuration is committed.

  • Associating an IPv4 Static Route with an NQA Test Instance.
    1. Run system-view

      The system view is displayed.

    2. Run either of the following commands as required:

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

        An IPv6 static route is associated with an NQA test instance on the public network.

      • Run ipv6 route-static vpn-instance vpn-source-name dest-ipv6-address prefix-length { interface-type interface-number [ nexthop-ipv6-address ] | vpn-instance vpn-destination-name [ nexthop-ipv6-address ] | nexthop-ipv6-address [ public ] } [ preference preference | tag tag ]* track nqa admin-name test-name [ description text ]

        An IPv6 static route is associated with an NQA test instance on the VPN network.

    3. Run commit

      The configuration is committed.

      NOTE:
      Precautions for associating a static route with an NQA test instance are as follows:
      • The destination address of an NQA test instance cannot be the destination address of an associated static route.
      • If the static route associated with one NQA test instance is associated with another NQA test instance, the association between the static route and the original NQA test instance is deleted.
      • An NQA test instance must have been created before you associate it with a static route.

Checking the Configurations

Run the following commands to check the previous configuration.

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

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

    NOTE:
    The NQA test results cannot be displayed automatically. You need to run the display nqa results command to view the results.

# Run the display current-configuration | include nqa command to view the configurations of NQA for IPv6 static routes. For example:

<HUAWEI> display current-configuration | include nqa
 ipv6 route-static 3::4 128 3::3 track nqa admin1 test1
 nqa test-instance admin1 test1

Run the display nqa results command to view the NQA test results.

<HUAWEI> display nqa results test-instance admin test
 NQA entry(admin, test) :testflag is active ,testtype is icmp
  1 . Test 9 result   The test is finished
   Send operation times: 1              Receive response times: 1
   Completion:success                 RTD OverThresholds number: 0
   Attempts number:1                    Drop operation number:0
   Disconnect operation number:0        Operation timeout number:0
   System busy operation number:0       Connection fail number:0
   Operation sequence errors number:0   RTT Stats errors number:0
   Destination ip address:3::3
   Min/Max/Average Completion Time: 80/80/80
   Sum/Square-Sum  Completion Time: 80/6400
   Last Good Probe Time: 2011-06-13 20:46:45.5
   Lost packet ratio: 0 %
For an ICMP NQA test, you can view the minimum, maximum, and average times for receiving ICMP Echo Reply packets displayed in Min/Max/Average Completion Time and packet loss ratio displayed in Lost packet ratio. In this example, the packet loss ratio is 0%, indicating that the link is running properly.
NOTE:

testflag is active is displayed only when the frequency interval command is configured for an NQA test instance. If the frequency interval command is not configured for an NQA test instance, the NQA test is performed only once, and testflag is inactive is displayed.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20607

Downloads: 15

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