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

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).
Adjusting OSPFv3 Route Selection

Adjusting OSPFv3 Route Selection

By adjusting OSPFv3 route selection, you can enable OSPF to meet the requirements of complex networks.

Usage Scenario

To meet the requirements of complex networks, you can adjust OSPFv3 route selection rule by configuring the following OSPFv3 route attributes:

  • Cost on the OSPFv3 interface

  • Load balancing among equal-cost routes

Pre-configuration Tasks

Before adjusting OSPFv3 route selection, complete the following tasks:

Configuration Procedures

Perform one or more of the following configurations as required.

Setting the Link Cost on an OSPFv3 Interface

OSPFv3 can automatically calculate the link cost for an interface based on the interface bandwidth. You can also set the link cost for the interface.

Context

You can control the route cost by setting different link costs for OSPFv3 interfaces.

Perform the following steps on the router that runs OSPFv3:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run ospfv3 cost cost [ instance instance-id ]

    The link cost is set on the OSPFv3 interface.

    If you do not set the cost of an OSPFv3 interface using the ospfv3 cost cost command, OSPFv3 automatically calculates the cost for the interface based on the interface bandwidth. The calculation formula is as follows: Cost of the interface = Bandwidth reference value/Interface bandwidth. The integer of the calculated result is the cost of the interface. If the calculated result is smaller than 1, the cost value is 1. Changing the bandwidth reference value can change the cost of an interface.

    Perform the following steps to change the bandwidth reference value:

    1. Run system-view

      The system view is displayed.

    2. Run ospfv3 [ process-id ]

      OSPFv3 is enabled, and the OSPFv3 view is displayed.

    3. Run bandwidth-reference value

      The bandwidth reference value is set.

    4. Run commit

      The configuration is committed.

  4. Run commit

    The configuration is committed.

Setting the Maximum Number of Equal-Cost Routes

Routes of the same routing protocol with the same destination and cost are called equal-cost routes, and traffic can be load-balanced among these routes.

Context

Perform the following steps on the router that runs OSPFv3:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ospfv3 [ process-id ]

    The OSPFv3 view is displayed.

  3. Run maximum load-balancing number

    The maximum number of equal-cost routes is set.

    If the number of equal-cost routes is greater than number specified in the maximum load-balancing command, routes are selected for load balancing based on the following criteria:

    1. Route priority: Routes with smaller priority values are selected for load balancing. For details about route priority configuration, see 4.
    2. Interface index: If routes have the same priority, those with greater interface index values are selected for load balancing.
    3. Next hop IP address: If routes have the same priority and interface index, those with larger IP addresses are selected for load balancing.

  4. (Optional) Run nexthop neighbor-id interface-type interface-number weight weight-value

    The preference for equal-cost routes is set.

    OSPFv3 selects a next hop from these equal-cost routes according to the weight. The smaller the weight is, the higher the route preference is.

  5. Run commit

    The configuration is committed.

Setting the convergence priority for OSPFv3 routes

You can adjust and optimize route selection by setting the convergence priority for OSPFv3 routes.

Context

To set the convergence priority of OSPFv3 routes based on a specified IPv6 prefix list takes effect on the public network only.

OSPFv3 route calculation, link-state advertisement (LSA) flooding, and LSDB synchronization can be implemented according to the configured priority. Therefore, route convergence can be controlled.

When an LSA meets multiple priorities, the highest priority takes effect.

OSPFv3 calculates LSAs in the sequence of intra-area routes, inter-area routes, and AS external routes. This command enables OSPFv3 to calculate the three types of routes separately according to the specified route calculation priorities. Convergence priorities are critical, high, medium, and low. To speed up the processing of LSAs with the higher priority, during LSA flooding, the LSAs need to be placed into the corresponding critical, high, medium, and low queues according to priorities.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ip_ipv6-prefix ipv6-prefix-name [ index index-number ] { deny | permit } ipv6-address prefix-length [ match-network ] [ greater-equal greater-equal-value ] [ less-equal less-equal-value ]

    The IPv6 prefix list is configured.

  3. Run ospfv3 [ process-id ]

    The OSPFv3 process is started and OSPFv3 view is displayed.

  4. Run prefix-priority { critical | high | medium } ipv6-prefix ipv6-prefix-name

    The convergence priority for OSPFv3 routes is set.

  5. Run commit

    The configuration is committed.

Verifying the Configuration of OSPFv3 Route Selection

After setting OSPF route attributes, verify information about OSPFv3 interfaces and the routing table.

Prerequisites

OSPFv3 route attributes have been configured.

Procedure

  • Run the display ospfv3 [ process-id ] interface [ no-peer | area area-id ] [ interface-type interface-number ] command in any view to view information about an OSPFv3 interface.
  • Run the display ospfv3 [ process-id ] routing command in any view to view information about an OSPFv3 routing table.
  • Run the display ospfv3 [ process-id ] ecmp-group command in any view to view information about OSPFv3 ECMP groups.

Example

Run the display ospfv3 interface command to view priorities of OSPFv3 interfaces.

<HUAWEI> display ospfv3 interface
GE1/0/0 is up, line protocol is up
  Interface ID 0x102
  IPv6 Prefixes
    FE80::2E0:FFF:FE4E:F101 (Link-Local Address)
    2000::1/64
  OSPFv3 Process (1), Area 0.0.0.1, Instance ID 0
    Router ID 1.1.1.1, Network Type BROADCAST, Cost: 1
    Transmit Delay is 1 sec, State Full, Priority 1
    No designated router on this link
    No backup designated router on this link
    Timer interval configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:02
    Neighbor Count is 0, Adjacent neighbor count is 0

Run the display ospfv3 routing command to view the destination addresses, link costs, and next hops of OSPFv3 routes.

<HUAWEI> display ospfv3 routing
 Codes : E2 - Type 2 External, E1 - Type 1 External, IA - Inter-Area
 OSPFv3 Process (1)
   Destination                                Metric
     Nexthop
   2000:1::/64                                 3124
     via FE80::1441:0:E213:1, GigabitEthernet1/0/0
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055018

Views: 47863

Downloads: 201

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