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

Configuration Guide - IP Routing 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 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).
Controlling RIP Routing Information

Controlling RIP Routing Information

In most cases, multiple protocols run on the same network. Therefore, you need to control routing information of every protocol to meet different networking requirements.

Usage Scenario

To meet the requirements of complex networking, accurately control the sending and receiving of RIP routing information.

Pre-configuration Tasks

Before configuring a router to control RIP routing information, complete the following tasks:

Configuration Procedure

Perform one or more of the following configurations as required.

Configuring RIP to Import External Routes

RIP can import routes from other processes or routing protocols to enrich the RIP routing table.

Context

On a large-scale network, multiple routing protocols may be configured for devices in different areas. In this situation, configure RIP to import routes from other processes or routing protocols to implement inter-area communication.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. (Optional) Run default-cost cost

    The default cost is set for imported routes.

    If you do not specify the cost for external routes, the value 0 takes effect.

  4. Import external routes.

    • To import direct, static, IS-IS, or OSPF routes, or routes of other RIP processes, run the import-route { static | direct | bgp | unr | { isis | ospf | rip } [ process-id ] } [ cost cost | { route-policy route-policy-name | route-filter route-filter-name } ] * command.
    • To import IBGP routes, run the import-route bgp permit-ibgp [ cost cost | { route-policy route-policy-name | route-filter route-filter-name } ] * command or the import-route bgp [ permit-ibgp ] { cost transparent { route-policy route-policy-name | route-filter route-filter-name } | { route-policy route-policy-name | route-filter route-filter-name } cost transparent | cost transparent } command.
    NOTE:

    Import of routes of other protocols may lead to routing loops. Therefore, exercise caution when running the import-route command.

  5. Run commit

    The configuration is committed.

Configuring RIP to Advertise Default Routes

Default routes are destined for 0.0.0.0. By default, RIP does not advertise default routes to its neighbors.

Context

In a routing table, the default route is a route to 0.0.0.0 with mask 0.0.0.0. You can run the display ip routing-table command to check whether the default route is configured. When the destination address of a packet does not match any entry in the routing table, the NE forward this packet along a default route.

If the default route and the destination address of the packet do not exist in the routing table, the NE discards the packet and sends an Internet Control Message Protocol (ICMP) packet, informing the originating host that the destination address or network is unreachable.

After the default-route originate command is run, default routes are advertised to RIP neighbors only when there are default routes in the routing table, and the default route that is learned from a neighbor is deleted.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Run default-route originate [ cost cost | tag tag | { match default | { route-policy route-policy-name [ advertise-tag ] | route-filter route-filter-name } } [ avoid-learning ] ] *

    RIP is enabled to advertise default routes.

  4. Run commit

    The configuration is committed.

Configuring RIP to Filter Received Routes

You can configure an import policy for a device so that the device receives only required routes.

Context

You can configure an import policy by specifying an ACL or IP prefix list to filter received routes. You can also configure a device to receive only the RIP packets from a specified neighbor.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Configure RIP to filter received routes.

    • Run filter-policy acl-number import [ interface-type interface-number ]

      The learned routes are filtered based on the ACL.

    • Run filter-policy gateway ip-prefix-name import

      The routes advertised by neighbors are filtered based on the IP prefix list.

    • Run filter-policy acl-name acl-name import [ interface-type interface-number ]

      The learned routes are filtered based on the named ACL.

    • Run filter-policy ip-prefix ip-prefix-name [ gateway ip-prefix-name ] import [ interface-type interface-number ]

      The routes learned from the specified interface are filtered based on the IP prefix list or interface.

  4. Run commit

    The configuration is committed.

Configuring RIP to Filter the Routes to Be Advertised

You can set conditions to filter the routes to be advertised. Only the routes that meet the conditions can be advertised.

Context

Devices can filter the routing information. To filter the routes to be advertised, you can configure an export filtering policy by specifying the ACL and IP prefix list.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Set the conditions to filter the advertised routes.

    Run any of the following commands as required:

    • Based on the basic ACL:
      1. Run filter-policy { acl-number | acl-name acl-name } export [ bgp | direct | static | unr | { isis | ospf | rip } [ process-id ] | interface-type interface-number ]

      2. Run quit

        Return to the system view.

      3. Run acl { name basic-acl-name { basic | [ basic ] number basic-acl-number } | [ number ] basic-acl-number } [ match-order { config | auto } ]

        The basic ACL view is displayed.

      4. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | source { source-ip-address { source-wildcard | 0 | src-netmask } | any } | time-range time-name | vpn-instance vpn-instance-name ] *

        The rule for the basic ACL is configured.

        When the rule command is run to configure rules for a named ACL, only the source address range specified by source and the time period specified by time-range are valid as the rules.

        When a filtering policy of a routing protocol is used to filter routes:
        • If the action specified in an ACL rule is permit, a route that matches the rule will be received or advertised by the system.

        • If the action specified in an ACL rule is deny, a route that matches the rule will not be received or advertised by the system.

        • If a route has not matched any ACL rules, the route will not be received or advertised by the system.

        • If an ACL does not contain any rules, all routes matching the route-policy that references the ACL will not be received or advertised by the system.

        • If the ACL referenced by the route-policy does not exist, all routes matching the route-policy will be received or advertised by the system.

        • In the configuration order, the system first matches a route with a rule that has a smaller number and then matches the route with a rule with a larger number. Routes can be filtered using a blacklist or a whitelist:

          Route filtering using a blacklist: Configure a rule with a smaller number and specify the action deny in this rule to filter out the unwanted routes. Then, configure another rule with a larger number in the same ACL and specify the action permit in this rule to receive or advertise the other routes.

          Route filtering using a whitelist: Configure a rule with a smaller number and specify the action permit in this rule to permit the routes to be received or advertised by the system. Then, configure another rule with a larger number in the same ACL and specify the action deny in this rule to filter out unwanted routes.

    • Based on the IP prefix:

      Run filter-policy ip-prefix ip-prefix-name export [ bgp | direct | static | unr | { isis | ospf | rip } [ process-id ] | interface-type interface-number ]

  4. Run commit

    The configuration is committed.

Disabling RIP from Receiving Host Routes

You can disable RIP from receiving host routes on a device to prevent the device from receiving a large number of unwanted routes. Such configuration can reduce network resource consumption.

Context

In some situations, the NE may receive a large number of host routes from the same network segment. These routes, useless for routing, consume many network resources. By disabling RIP from receiving host routes, you can configure the NE to reject the received host routes.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Run undo host-route

    RIP is disabled from receiving host routes.

    By default, RIP is allowed to receive host routes.

  4. Run commit

    The configuration is committed.

Disabling the Check on RIP Packets with Cost 0

To communicate with other devices supporting packets with cost 0, prevent the Huawei device from checking the RIP packets with cost 0.

Context

On the live network, not all devices can receive the packets with cost 0. By default, devices do not accept the packets with cost 0. Therefore, RIP interfaces discard the RIP packets with cost 0. To implement communication between Huawei devices and the devices that can accept the packets with cost 0, run the undo zero-metric-check command to allow interfaces to accept the RIP packets with cost 0.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run rip [ process-id ]

    A RIP process is created, and the RIP view is displayed.

  3. Run undo zero-metric-check

    The interface is allowed to receive RIP packets with cost 0.

  4. Run commit

    The configuration is committed.

Follow-up Procedure

To enable the check on the RIP packets with cost 0, run the zero-metric-check command.

Disabling an Interface from Sending Packets

When you do not need an interface connected to an external network to send routing information, disable the interface from sending RIP packets.

Usage Scenario

On the network shown in Figure 7-3, RIP-enabled Network 1 is connected to Network 2 through the edge device Device A. You can disable the interface on Device A from sending packets.

Figure 7-3 Scenario where an interface is disabled from sending packets

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run undo rip output

    The interface is disabled from sending RIP packets.

    By default, an interface is allowed to send RIP packets.

  4. Run commit

    The configuration is committed.

Disabling an Interface from Receiving Packets

If an interface does not need to learn routing information from neighbors, you can disable the interface from receiving RIP packets.

Usage Scenario

On an enterprise network where departments are not allowed to communicate with each other, you can disable interfaces from receiving packets.

On the network shown in Figure 7-4, if you do not want Department 1 to learn routing information about Department 2, you can disable the interface on Device A from receiving packets.

Figure 7-4 Scenario where an interface is disabled from receiving packets

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run undo rip input

    The interface is disabled from receiving RIP packets.

    By default, an interface is allowed to receive RIP packets.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of RIP Routing Information Control

After controlling RIP routing information, verify all activated routes in the RIP database and the running status of RIP.

Prerequisites

RIP routing information has been controlled.

Procedure

  • Run the display rip process-id database command to check all active routes in the RIP database.
  • Run the display rip process-id command to check the running status and configuration of the RIP process.

Example

Run the display rip process-id database command to view the default route and imported route.

<HUAWEI> display rip 100 database
 0.0.0.0/0, cost 0, Default route originate
   172.4.0.0/16, cost 1, ClassfulSumm
       172.4.0.0/16, cost 1, nexthop 192.13.14.1
   20.0.0.0/8, cost 0, ClassfulSumm
       20.20.20.20/32, cost 0, Imported

Run the display rip process-id command to check whether there are interfaces that can only receive host routes but cannot send packets.

<HUAWEI> display rip
  Public VPN-instance
    RIP process      : 1   
       RIP version   : 1
       Preference    : 100 
       Checkzero     : Enabled
       Default-cost  : 0
       Summary       : Enabled
       Host-route    : Disabled
       Maximum number of balanced paths : 3
       Update time   : 30 sec  Age time  : 180 sec
       Suppress time : 0  sec   Garbage-collect time : 120 sec
       Graceful restart  : Disabled
       BFD               : Disabled
       Silent-interfaces : None
       Default Route : Disabled
       Verify-source : Disabled
       Networks :
       172.4.0.0
       Configured peers : None
       Number of routes in database : 4
       Number of interfaces enabled : 3
       Number of VRRP interfaces    : 0
       Triggered updates sent : 3
       Number of route changes : 6
       Number of replies to queries : 1
       Description : RIP 
  Total count for 1 process :
       Number of routes in database : 3
       Number of interfaces enabled : 1
       Number of VRRP interfaces    : 0
       Number of routes sendable in a periodic update : 1
       Number of routes sent in last periodic update : 0
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058916

Views: 33989

Downloads: 49

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