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 RIPng

Configuring RIPng

RIPng is widely used on small-sized IPv6 networks to discover routes and generate routing information.

Configuring Basic RIPng Functions

Basic RIPng functions include creating RIPng processes and enabling RIPng on interfaces. The basic RIPng functions must be configured before you use RIPng features.

Pre-configuration Tasks

Before configuring basic RIPng functions, complete the following tasks:

  • Enabling IPv6 on the switch modules

  • Configuring IPv6 addresses for interfaces to ensure that neighboring nodes are reachable at the network layer

Configuration Flowchart

Creating RIPng processes is the prerequisite for enabling RIPng on interfaces.

Enabling RIPng

Context

Enabling RIPng is the prerequisite for all RIPng-related configurations. If you run the RIPng commands in the interface view before enabling RIPng, the configurations take effect only after RIPng is enabled.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ripng [ process-id ] [ vpn-instance vpn-instance-name ]

    RIPng is enabled and the RIPng view is displayed.

    If a VPN instance is specified, the RIPng process belongs to this VPN instance. If no VPN instance is specified, the RIPng process belongs to a public network instance.

  3. (Optional) Run:

    description text

    Descriptions for RIPng processes are configured.

  4. Run:

    commit

    The configuration is committed.

Enabling RIPng on Interfaces

Context

After RIPng is enabled on an interface, devices can exchange RIPng routing information through this interface.

Procedure

  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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

    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:

    ripng process-id enable

    RIPng is enabled on the specified interface.

    NOTE:

    If IPv6 is not enabled in the interface, this command cannot be run.

    If RIPng needs to be enabled on multiple interfaces of a switch modules, repeat steps 2 and 3.

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display ripng [ process-id | vpn-instance vpn-instance-name ] command to check the configuration of the RIPng process.
  • Run the display ripng process-id route [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number ] [ neighbor-address neighbor-address ] command to check all the RIPng routes that are learned from other switch moduleses.
  • Run the display default-parameter ripng command to check the default RIPng configuration.
  • Run the display ripng process-id statistics interface { all | interface-type interface-number [ neighbor neighbor-ipv6-address | verbose ] } command to check statistics about RIPng interfaces.

Avoiding Routing Loops

You can configure split horizon and poison reverse to prevent routing loops.

Pre-configuration Tasks

Before configuring split horizon and poison reverse, complete the following task:

Configuration Process

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

Configuring Split Horizon

Context

Split horizon can prevent routing loops.

Procedure

  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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

    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:

    ripng split-horizon

    Split horizon is configured.

    NOTE:
    • By default, split horizon is enabled except on the NBMA network.
    • If both split horizon and poison reverse are configured, only poison reverse takes effect.

  5. Run:

    commit

    The configuration is committed.

Configuring Poison Reverse

Context

Poison reverse can prevent routing loops.

Procedure

  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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

    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:

    ripng poison-reverse

    Poison reverse is enabled.

    NOTE:

    If both split horizon and poison reverse are configured, only poison reverse takes effect.

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display ripng process-id interface [ interface-type interface-number ] [ verbose ] command to view information about the RIPng interface.

Controlling RIPng Routing

You can control RIPng routing in a network with a complicated environment.

Pre-configuration Tasks

Before configuring RIPng route attributes, complete the following task:

Configuration Process

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

Configuring RIPng Preference

Context

When different routing protocols discover the routes to the same destination, set the RIPng preference to select the required route.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ripng [ process-id ] [ vpn-instance vpn-instance-name ]

    The RIPng view is displayed.

  3. Run:

    preference { preference | route-policy route-policy-name } *

    The RIPng preference is set.

    By default, the RIPng preference is 100.

  4. Run:

    commit

    The configuration is committed.

Configuring Additional Metrics of an Interface

Context

Configuring the additional metrics on a RIPng interface can change the route selection sequence.

The additional metric is the metric (hop count) to be added to the original metric of a RIPng route. You can specify commands to set additional metrics for incoming and outgoing RIPng routes.

Procedure

  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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

    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 the following commands as required:

    • Run the ripng metricin value command to set the additional metric for receiving routes. By default, an interface does not add the metric to a received RIPng route.
    • Run the ripng metricout { value | { acl6-number | acl6-name acl6-name | ipv6-prefix ipv6-prefix-name } value1 } command to set the additional metric for advertising routes. By default, the metric that is added to the RIPng route sent by an interface is 1.
    NOTE:
    • The ripng metricin command is used to add an additional metric to an incoming route. After this route is added to the routing table, its metric in the routing table changes. Running this command affects route selection on the local device and other devices on the network.
    • The ripng metricout command is used to add an additional metric to an outgoing route. When this route is advertised, an additional metric is added to this route, but the metric of the route in the routing table does not change. Running this command does not affect route selection on the local device but other devices on the network.

  5. Run:

    commit

    The configuration is committed.

Setting the Maximum Number of Equal-Cost Routes

Context

By setting the maximum number of equal-cost RIPng routes, you can change the number of routes for load balancing.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ripng [ process-id ] [ vpn-instance vpn-instance-name ]

    RIPng is enabled and the RIPng view is displayed.

  3. Run:

    maximum load-balancing number

    The maximum number of equal-cost routes is set. The default value is 16.

  4. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display ripng [ process-id | vpn-instance vpn-instance-name ] command to view the running status and configurations of RIPng.
  • Run the display ripng process-id database [ verbose ] [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number [ neighbor neighbor-address ] ] command to view all the active routes in the RIPng database.
  • Run the display ripng process-id route [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number ] [ neighbor-address neighbor-address ] command to view all RIPng routes learned from other devices.

Controlling RIPng Route Advertisement

On a complex network, RIPng route advertisement must be accurate.

Pre-configuration Tasks

Before controlling RIPng route advertisement, complete the following task:

Configuration Process

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

Configuring RIPng Route Summarization

Context

Route summarization can reduce the routing table size and minimize impact of route flapping on the network.

Procedure

  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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

    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:

    ripng summary-address ipv6-address prefix-length [ avoid-feedback ]

    RIPng route summarization is configured.

    By default, a RIPng router does not advertise summarized IPv6 addresses.

  5. Run:

    commit

    The configuration is committed.

Advertising a Default Route

Context

In an IPv6 routing table, a default route is a route to network ::/0. If the destination address of a packet does not match any entry in the routing table, the packet is sent through a default route.

There are two methods to advertise RIPng default routes. You can configure a device to advertise RIPng default routes according to networking requirements.

Procedure

  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.

    If an Ethernet interface already has Layer 2 configuration, this command fails to be executed on the interface. Before running this command on the interface, delete all the Layer 2 configuration of the interface.

    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:

    ripng default-route { only | originate } [ cost cost | tag tag ]*

    The device is configured to advertise RIPng default routes.

    By default, there is no default route in the RIPng routing domain.

    Configure the device to advertise default routes according to networking requirements:

    • only: configures the device to advertise only IPv6 default routes (::/0), suppressing the advertisement of other routes.If the local device is located on the network edge and the details of the local network need to be hidden, you can set this parameter to enable the devices on other networks to access the local network only through the local device.

    • originate: configures the device to advertise IPv6 default routes (::/0) without affecting the advertisement of other routes.If the local device is located on the network edge and some details of the local network need to be hidden, you can set this parameter to enable the devices on other networks to use the default route when connecting to certain devices on the local network.

    The device advertises generated RIPng default routes using Update packets through a specified interface regardless of whether these routes exist in the local IPv6 routing table.

  5. Run:

    commit

    The configuration is committed.

Configuring a RIPng Process to Import External Routes

Context

A RIPng process can import the routes learned by other processes or routing protocols to enrich its routing information.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ripng [ process-id ] [ vpn-instance vpn-instance-name ]

    The RIPng view is displayed.

  3. (Optional) Run:

    default-cost cost

    The default cost of external routes to be imported is set.

    By default, the default cost of RIPng routes is 0.

    If no cost is set for external routes to be imported, the default cost is used.

    NOTE:

    When a RIPng process imports IBGP routes, routing loops may occur. Therefore, exercise caution before you configure this function.

  4. Run:

    import-route { direct | static | { isis | ospfv3 | ripng } [ process-id ] | bgp [ permit-ibgp ] } [ cost cost | route-policy route-policy-name ] *

    External routes are imported.

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display ripng process-id database [ verbose ] [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number [ neighbor neighbor-address ] ] command to check all activated routes in the RIPng database.
  • Run the display ripng process-id route [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number ] [ neighbor-address neighbor-address ] command to check all the RIPng routes that are learned from other switch moduless.

Improving RIPng Network Performance

You can adjust and optimize the RIPng network performance by configuring RIPng functions in special network environments, such as configuring RIPng timers, setting the interval for sending packets, and setting the maximum number of packets to be sent.

Pre-configuration Tasks

Before improving RIPng network performance, complete the following task:

Configuration Process

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

Configuring RIPng Timers

Context

RIPng uses 4 timers: Update, Age, Suppress, and Garbage-collect. Changing the timer values affects the convergence speed of RIPng routes.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ripng [ process-id ] [ vpn-instance vpn-instance-name ]

    The RIPng process is enabled and the RIPng view is displayed.

  3. Run:

    timers ripng update age suppress garbage-collect

    RIPng timers are configured.

    NOTE:
    • RIPng timers take effect immediately after being changed.

    • Route flapping occurs if the values of the four times are set improperly. The relationship between the values is as follows: update must be smaller than age and suppress must be smaller than garbage-collect. For example, if the update time is longer than the aging time, and a RIPng route changes within the update time, the switch modules cannot inform its neighbors of the change on time.

    • You must configure RIPng timers based on the network performance and uniformly on all the routers running RIPng. This avoids unnecessary network traffic or route flapping.

    By default, the Update timer is 30s; the Age timer is 180s; the Suppress timer is 0s; the Garbage-collect timer is four times the Update timer, namely, 120s.

    In practice, the Garbage-collect timer is not fixed. If the Update timer is set to 30s, the Garbage-collect timer may range from 90s to 120s.

    Before permanently deleting an unreachable route from the routing table, RIPng advertises this route (with the metric being set to 16) by periodically sending Update packets four times. Subsequently, all the neighbors know that this route is unreachable. Because a route may not always become unreachable at the beginning of an Update period, the Garbage-collect timer is actually three or four times the Update timer.

  4. Run:

    commit

    The configuration is committed.

Enabling Zero Field Check for RIPng Packets

Context

In a RIPng packet, some fields must be zero. These fields are called zero fields. When receiving a packet, a RIPng process checks the zero fields of the packet. If the value of a zero field in the packet is not 0, the RIPng process discards the packet.

Enabling zero field check on RIPng Update packets can improve network security.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ripng [ process-id ] [ vpn-instance vpn-instance-name ]

    The RIPng view is displayed.

  3. Run:

    checkzero

    Zero field check is enabled for RIPng packets.

  4. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display ripng [ process-id | vpn-instance vpn-instance-name ] command to check the configuration of the RIPng process.
  • Run the display ripng process-id database [ verbose ] [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number [ neighbor neighbor-address ] ] command to check all activated routes in the RIPng database.
  • Run the display ripng process-id interface [ interface-type interface-number ] [ verbose ] command to check information about the RIPng interface.
  • Run the display ripng process-id neighbor [ neighbor-address neighbor-address ] [ verbose ] command to check information about RIPng neighbors.
  • Run the display ripng process-id route [ destination-address destination-address [ mask-length ] ] [ interface interface-type interface-number ] [ neighbor-address neighbor-address ] command to check all the RIPng routes that are learned from other switch moduleses.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 57154

Downloads: 3617

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