01-01 ip routing overview

Quidway NetEngine40 Configuration Guide - IP Routing Contents
Quidway NetEngine40 Configuration Guide - IP Routing Quidway NetEngine40 Configuration Guide - IP Routing 1 IP Routing Overview
About This Chapter
The following table shows the contents of this chapter. Description
This section describes the information of the IP routing This section describes the information of the routing This section describes the information of the routing management. 1.1 Overview of IP Routing and the Routing Table
The section covers the following topics that you need to know before you configure IP routing and routing table: 1.1.1 Route and Route Segments
Routers are necessary for the selection of the route on the Internet. When a router receives an IP packet, it selects an appropriate path (through a network) based on the destination address of the packet. It then forwards the packet to the next router in the path. The packet is thus transferred from one router to the next along the path. The last router delivers the packet to its destination. In from host A to host C, a packet should go through three networks and two routers. Thus, if a node is connected to another node in a network, a route segment exists between these two nodes. Hence, they are known as the adjacent nodes on the Internet. Based on the same principle, adjacent routers are two routers connected to the same network. The number of route segments between a router and hosts in the same network is counted as zero. In arrows represent these segments. A router is not concerned about the physical links that constitute this route segment. Figure 1-1 Route segments
When the size of the networks vary considerably, the length of the route segments may also vary. So when the actual length of the path is measured, for different networks, the number of route segments is multiplied by a weighted coefficient. Consider a router in a network as a node in the network, and a route segment on the Internet as a link. Then routing on the Internet is similar to the routing in a simple network. Routing through a few routing segments may not be always the ideal way. For example, routing through three LAN route segments may be much faster than routing through two WAN route segments. Quidway NetEngine40 Configuration Guide - IP Routing 1.1.2 Route Selection Through the Routing Table
Routing Table
The routing table is the key for a router to forward the packets. Each router maintains a routing table in its memory. Each entry of this table specifies the physical interface of the router through which a packet should be sent to a subnet or a host. The packet can thus reach the next router in the path or the destination host if it is a directly connected network. According to the sources, the routes in the routing table can be divided into the following three categories: The route in the link layer protocol (also called interface route or direct route) The static route manually configured by the network manager The Contents of the Routing Table
A routing table has the following key entries: Destination address: it is used to identify the destination IP address or the destination network address of the IP packet. Network mask: it is combined with the destination address to give the address of the network segment where the destination host or router is located. Thus, they are used to identify the network address of the destination host or the router. For example, if the destination address is 129.102.8.10 and the mask is 255.255.0.0, then the address of the network where the host or the router is located is 129.102.0.0. The mask is made up of several consecutive "1"s. These "1"s can be expressed either in the dotted decimal format or in a number of consecutive "1"s in the mask. Outgoing interface: it indicates the interface through which an IP packet should be forwarded. Next hop IP address: it indicates the next router that an IP packet passes through. Preference added to the IP routing table for a route: there may be different next hops to the same destination. These routes may be discovered by different routing protocols, or they can just be the manually configured static routes. The route with the highest preference (the smallest value) is selected as the current optimal route. According to different destinations, the routes can be divided into the following categories: Subnet route: the destination is a subnet. In addition, based on whether the destination location is directly connected to the router or not, routes fall into the following types: Direct route: the router is directly connected to the network in which the destination is located. Indirect route: the router is not directly connected to the network in which the destination is located. Set a default route to prevent the routing table from having a large number of entries. All the packets that fail to match a suitable entry in the routing table are forwarded through this default route. As shown in Figure 1-2, Router A is connected with three networks. Thus it has three IP addresses a interfaces. ows the routing table. Figure 1-2 Routing table
1.2 Overview of Routing Protocols
This section covers the following routing protocols: 1.2.1 Static Route and Dynamic Route
Besides static routes, the NE40 supports dynamic routing protocols, such as RIP, OSPF, IS-IS, and BGP. Static routes can be easily configured on a system. They have lower system requirements. They are applicable to simple, stable, and small-scale networks. Static routes cannot automatically adapt to the changes in the network topology. Thus they must be manually configured. With their routing algorithms, dynamic routing protocols can automatically adapt to the changes of network topology. So they are applicable to the network equipped with a certain Quidway NetEngine40 Configuration Guide - IP Routing quantity of Layer 3 devices. However, dynamic routes are quite complicated and difficult to configure. They have higher system requirements. They also occupy certain network resources. 1.2.2 Classification of Dynamic Routing Protocols
Dynamic routing protocols can be classified on the following conditions: According to the Range of Functions
According to the range of functions, the routing protocols can be divided into: Interior Gateway Protocol (IGP): runs inside an AS, such as RIP, OSPF and IS-IS. Exterior Gateway Protocol (EGP): runs between different ASs, such as BGP. According to the Algorithm
According to the Algorithm, the routing protocols can be divided into: Distance-Vector Routing Protocol: includes RIP and BGP (BGP is also called Path-Vector). Link-State Routing Protocol: includes OSPF and IS-IS. The above algorithms mainly differ in the method for route discovery and calculation. According to the Types of Destination Addresses
According to the types of destination addresses, the routing protocols can be divided into: Unicast Routing Protocol: includes RIP, OSPF, BGP, and IS-IS. Multicast Routing Protocol: includes DVMRP, PIM-SM, and PIM-DM. This manual mainly describes the Unicast Routing Protocol. For details of the Multicast Routing Protocol, refer to the Quidway NetEngine40Series Universal Switching RoutersConfiguration Guide - IP Multicast. Static routes are managed in the router together with the dynamic routes discovered by routing protocols. All these routes can be shared between different routing protocols. 1.2.3 Routing Protocols and Route Preferences
Different routing protocols (as well as the static route) may learn different routes to the same destination, but not all these routes are optimal. At a certain moment, only one routing protocol determines the current route to a specific destination. Each of these routing protocols (including the static route) is set to a preference. When there are multiple routing information sources, the route learned by the routing protocol with the highest preference becomes the current route. Routing protocols and the default preferences (the smaller is the value, the higher is the preference) of the routes learned by them are shown in In , 0 indicates the direct route and 255 indicates any route learnt from unreliable sources. The smaller is the value, the higher is the preference. Table 1-1 Routing protocols and their default preferences for the routes
Routing Protocol or Route Type
Preference of the Corresponding Route
Except for direct route, the preferences of various routing protocols can be manually configured to meet the user's requirements. In addition, the preferences for each static route can be different. 1.2.4 Load Balancing and Route Backup
Load Balancing:
The NE40 supports the multi-route mode. That is, the NE40 permits the configuration of multiple routes with the same destination and the same preference. If no route with higher preference reaches the destination, all routes with the same preference are adopted. Routers at the IP layer send packets to the destination through various paths. Thus the load balancing is realized. For the same destination, a specified routing protocol may find multiple routes. If the routing protocol has the highest preference among all active routing protocols, these multiple routes are regarded as currently valid routes. Thus, load balancing of the IP traffic is ensured at the routing protocols layer. So far, the routing protocols that support load balancing are RIP, OSPF, BGP, and IS-IS. Static route also supports load balancing. Route Backup:
The NE40 supports the route backup to improve the network reliability. You can configure multiple routes to the same destination based on the actual situation. The route with the highest preference is called the active route. The other routes with descending preferences are called backup routes. Generally, the main route forwards packets. When the link has some faults, the route becomes inactive, and the router chooses a backup route to forward the data. The process realizes the switch from the main route to the backup route. When the main route is recovered, the router recovers its corresponding route and chooses the route again. Because the route has the Quidway NetEngine40 Configuration Guide - IP Routing highest preference, the router chooses the main route to send the data. That is the switch from the backup route to the main route. 1.2.5 Sharing of Routing Information Between Protocols
The algorithms of various routing protocols are different. Thus they may discover different routes. This brings about the problem of sharing the learned routes between the routing protocols. A router can import the information of another routing protocol. Each protocol has its own route import mechanism. For the details, refer to the description "Importing an External Route" in the configuration guide of the corresponding routing protocol. 1.3 Routing Management
The section covers the following topics: 1.3.1 Displaying of the Routing Table
To locate the routing problems, you should first view the information in the routing table. Some commands for displaying routing information are shown in The display command can be used in all views.
Table 1-2 Displaying the routing table
display ip routing-table
display ip routing-table verbose
display ip routing-table ip-address [ mask |
mask-length ] [ longer-match ] [ verbose ]
display ip routing-table ip-address1 { mask1 |
mask-length1 } ip-address2 { mask2 |
mask-length2 } [ verbose ]
display ip routing-table acl acl-number
[ verbose ]
display ip routing-table ip-prefix
ip-prefix-name [ verbose ]
display ip routing-table protocol protocol
[ inactive | verbose ]
display ip routing-table statistics
display ip routing-table vpn-instance
vpn-instance-name [ filter-option ] display ip routing-table vpn-instance
vpn-instance-name [ filter-option ] verbose
1.3.2 Displaying and Debugging of the Routing Management
Module
As shown in o use the display and the debugging commands in the routing
management module is one method to settle the routing problem.
The display command can be used in all views, while the debugging command can be used
only in the user view.
Table 1-3 Displaying and Debugging the routing management module
display rm interface [ interface-type
display rm ipv6 interface [ interface-type
display rm interface vpn-instance
debugging rm all
debugging rm backup
debugging rm ipv4 { bfd | im | urt | usr | msr |
rcom [ ip-prefix ip-prefix-name ] | rr }
debugging rm ipv6 { im | urt | usr | rcom
[ ip-prefix ip-prefix-name ] | rr }
debugging rm job
debugging rm policy [ ip-prefix
debugging rm system
debugging rm task
debugging rm timer

Source: ftp://vovao.telesystems.ua/docs/Huawei/Huawei/NE40%20V300R003/31503055-Quidway%20NetEngine40%20Series%20Universal%20Switching%20Routers%20Configuration%20Guide-IP%20Routing(V300R003_01)/01-01%20IP%20Routing%20Overview.pdf