This tutorial explains how to configure static routing step by step in detail including advantage of static routing and disadvantage of static routing. Learn how to enable, configure, manage and delete static route in Cisco router with practical example in packet tracer.
Static routing is the most secure way of routing. It reduces overhead from network resources. In this type of routing we manually add routes in routing table. It is useful where numbers of route are limited. Like other routing methods static routing also has its pros and cons.
NE40E Series Universal Service Routers: Access product manuals, HedEx documents, product images and visio stencils.
- Detail: 02354367 Huawei NetEngine NE40E-X3 Series Router CR5P03BASD71 NE40E-X3 Basic Configuration (Include NE40E-X3 Chassis, 2 MPUs, 2 DC Power, without Software Charge and Document) Condition: Brand New Sealed. Availability: IN STOCK.
- The NE40E lays the foundation for enterprise services with a system availability of 99.999%. Quick Specs Figure 1 shows the appearance of Huawei Router -CR52-NE40E-X3-BASE-DC. Table 1 shows the Quick Specs. Product Code Huawei Router - CR52-NE40E-X3-BASE-DC Switching Capacity 1.08 Tbit/s Forwarding Performance 540 Mpps.
Advantage of static routing
- It is easy to implement.
- It is most secure way of routing, since no information is shared with other routers.
- It puts no overhead on resources such as CPU or memory.
Disadvantage of static routing
- It is suitable only for small network.
- If a link fails it cannot reroute the traffic.
To explain static routing, I will use packet tracer network simulator software. You can use any network simulator software or can use a real Cisco devices to follow this guide. There is no difference in output as long as your selected software contains the commands explained in this tutorial.
Create a practice lab as shown in following figure or download this pre-created practice lab and load in packet tracer
If require, you can download the latest as well as earlier version of Packet Tracer from here. Download Packet Tracer
| Device | Connected from | Connected to | IP Address |
| PC0 | FastEthernet0 | Router0’s FastEthernet0/0 | 10.0.0.2/8 |
| Router0 | FastEthernet0/0 | PC0’s FastEthernet0 | 10.0.0.1/8 |
| Router0 | Serial 0/0/0 | Router1’s serial0/0/0 | 192.168.0.253/30 |
| Router1 | Serial0/0/0 | Router0’s Serial0/0/0 | 192.168.0.254/30 |
| Router1 | Serial0/0/1 | Router2’s Serial0/0/0 | 192.168.0.249/30 |
| Router2 | Serial0/0/0 | Router1’s Serial0/0/1 | 192.168.0.250/30 |
| Router2 | Serial0/0/1 | Router3’s Serial0/0/0 | 192.168.0.245/30 |
| Router3 | Serial0/0/0 | Router2’s Serial0/0/1 | 192.168.0.246/30 |
| Router3 | FastEthernet0/0 | PC1’s FastEthernet0 | 20.0.0.1/8 |
| PC1 | FastEthernet0 | Router1’s FastEthernet0/0 | 20.0.0.2/8 |
Assign IP address to PCs
Assign IP address 10.0.0.2/8 to PC0.
Repeat same process for PC1 and assign IP address 20.0.0.2/8.
Assign IP address to interfaces of routers
Double click Router0 and click CLI and press Enter key to access the command prompt of Router0.
Two interfaces FastEthernet0/0 and Serial0/0/0 of Router0 are used in this topology. By default interfaces on router are remain administratively down during the start up.
We need to configure IP address and other parameters on interfaces before we could actually use them for routing. Interface mode is used to assign IP address and other parameters. Interface mode can be accessed from global configuration mode. Following commands are used to access the global configuration mode.
From global configuration mode we can enter in interface mode. From there we can configure the interface. Following commands will assign IP address on FastEthernet0/0.
interface fastEthernet 0/0 command is used to enter in interface mode.
ip address 10.0.0.1 255.0.0.0 command will assign IP address to interface.
no shutdown command will bring the interface up.
exit command is used to return in global configuration mode.
Serial interface needs two additional parameters clock rate and bandwidth. Every serial cable has two ends DTE and DCE. These parameters are always configured at DCE end.
We can use show controllers interface command from privilege mode to check the cable’s end.
Fourth line of output confirms that DCE end of serial cable is attached. If you see DTE here instead of DCE skip these parameters.
Now we have necessary information let’s assign IP address to serial interface.
Router#configure terminal Command is used to enter in global configuration mode.
Router(config)#interface serial 0/0/0 Command is used to enter in interface mode.
Router(config-if)#ip address 192.168.0.253 255.255.255.252 Command assigns IP address to interface. For serial link we usually use IP address from /30 subnet.
Router(config-if)#clock rate 64000 And Router(config-if)#bandwidth 64 In real life environment these parameters control the data flow between serial links and need to be set at service providers end. In lab environment we need not to worry about these values. We can use these values.
Router(config-if)#no shutdown Command brings interface up.
Router(config-if)#exit Command is used to return in global configuration mode.
We will use same commands to assign IP addresses on interfaces of remaining routers. We need to provided clock rate and bandwidth only on DCE side of serial interface. Following command will assign IP addresses on interface of Router1.
Router1
Now we know how to assign IP addresses on interfaces. We will use same commands to assign IP addresses on interfaces of Router2.
Router2
Repeat same process for Router3
Router3
Great job we have finished our half journey. Now routers have information about the networks that they have on their own interfaces. Routers do not exchange network information between them on their own. We need to implement a mechanism that insists them to share this information. This mechanism is called routing.
There are two types of routing static and dynamic. In this article we will use static method of routing.
Command to configure the static route
We have two commands to configure the static route.
Or
ip route
This is the base command that adds new routes in routing table.
destination_network_#[subnet_mask]
This is the first parameter. It specifies the destination network address. We need to provide subnet mask if we are using sub-network. Sub-networks are the smaller network created from one large network in subnetting. If we are not using sub-network then we can omit the subnet mask value. It will parse automatically.
IP_address_of_next_hop_neighbor / interface_to_exit
This parameter provides a way to reach the destination network. Both commands use separate way to assign this value. First command provides the IP address of next hop neighbor. It tells router that if it receives a packet for destination [that we set in previous parameter], forward that packet to this next hop neighbor IP address.
Second command also do the same job but in different way. It specifies exit interface instead of next hop IP address. It tells router that if it receives a packet for the destination specified by previous parameter then exits that packet from this interface. Device attached on other end of this interface will take care of the packet.
administrative_distance
Administrative distance is the trustworthiness of route. Route with the lowest AD value will be chosen while forwarding the packet. By default static route has two AD values depending on the previous parameter. If you have used next hop neighbor IP address, then the default AD value will be 1. If you have used exit interface, then the default AD value will be 0. This parameter allows us to create multiple static routes for the same destination. For example we can create primary and backup path for the destination network. To create backup path, we need to set AD value to higher than default, such as 2 or 3. With this configuration router will use primary path. Due to some reason if primary route fails, the router will start using backup route automatically.
permanent
When a route goes down router will remove that from routing table. Permanent parameter will keep this route in routing table even if it goes down. Its optional parameter we can omit it. If we omit it, router will remove this route from routing table if it goes down. You might use this parameter for security reason if you never want packets to take another path.
Now we are familiar with IP route command and its parameters lets implement it in our network.
Configure Static Route
By default when a packet arrives in interface, router checks destination filed in packet and compare it with routing table. If it finds a match for destination network then it will forward that packet from related interface. If it does not find a match in routing table then it will discard that packet. This is the default behavior of router. We do not need to configure directly connected networks.
Run following command from global configuration mode in routers.
Router0
This command instructs router that when you receive a packet for 20.0.0.0 network give it to 192.168.0.254. Network 10.0.0.0 is directly connected so we do not need to configure it here.
Router1
On this router both networks are reachable via other routers so we need to configure route for both networks 10.0.0.0 and 20.0.0.0.
Router2
Same as Router1 again we need configure route for both networks on this router.
Router3
Network 20.0.0.0 is directly connected so we only need to configure network 10.0.0.0 on this router.
That’s all we need to switch packet from one network to another. To verify the result we can use ping command. Access the command prompt of PC1 and use ping command to test the connectivity from PC0.
Good going we have successfully implemented static routing in our network. For cross check we have uploaded a configured topology. You can use this if you are not getting the same output.
How to Delete Static Route
In static routing we have to manage all routes manually. If any route goes down, we have to remove that manually. Removing a route in static routing is easier than you think. All you need to do is just add a keyword no before the same command that we have used to configure the static route.
no ip route command is used to remove the route from routing table. Following commands will remove the route from their respective routes.
Router0
Router1
Router2
Router3
Configure Default Route
Static routing solves one more network problem. It can redirect all unmatched packets to a certain port. This feature is extremely helpful in several situations. We can set a default route for internet connection or we can implement a security measurement to deal with all matched packet.
By default Routers are configured to drop the packet if destination address is not found in routing table. Default route will override this behavior. If no match for destination network is found in routing table then it would be forwarded to the default route. Thus default route is a way to deal with all unmatched packets.
Following command will set default route
Or
Above command sets destination network to 0.0.0.0/0 that represents all networks.
That’s all for this article. In next article we will configure dynamic routing.
Huawei NE40E Universal Service Router is a high-end router. Huawei NE40E is positioned as the edge or convergence router on the IP backbone network. The NE40E series routers, including Huawei NE40E-X16, Huawei NE40E-X8 and Huawei NE40E-X3, are suitable for networks of different scales. Huawei NE40E-X3/X8/X16 product architecture includes the following:
Physical Architecture
The physical architecture includes the following systems:
- Power distribution system
- Functional host system
- Heat dissipation system
- Network management system
All systems except the network management system (NMS) are located in an integrated cabinet. The power distribution system consists of power modules working in n+n backup mode.
The functional host system comprises the system backplane,/Main Processing Units (MPUs), Line Processing Units (LPUs), Switch and Fabric Units (SFUs). It is connected to the NMS through NMS interfaces. The functional host system processes data as well as monitors and manages the entire system, including the power distribution system and heat dissipation system.
Logical Architecture
The logical architecture of the NE40E consists of the following planes:
- Data plane
- Control and management plane
- Monitoring plane
The data plane is responsible for high speed processing and non-blocking switching of data packets. It encapsulates or decapsulates packets, forwards IPv4/IPv6/MPLS packets, performs QoS as well as scheduling and internal high-speed switching, and collects statistics.
The control and management plane completes all control and management functions for the system and is the core of the entire system. Control and management units provide control system status. They process, maintain, manage and provide reporting for protocols and signals.
The monitoring plane monitors the ambient environment to ensure secure and stable operation of the system. It detects voltage levels, controls system power-on and-off, monitors temperature, and controls fan modules. When a unit fails, the monitoring plane isolates the faulty unit promptly so that other parts of the system can continue to run normally.
Software Architecture
Software of the NE40E consists of the Routing Process System (RPS), power monitoring system, fan monitoring system, Forwarding Support Unit (FSU), and Express Forwarding Unit (EFU).
The RPS, which includes IPOS software, VRP software, and product-adaptation software, is the control and management module that runs on the MPU. The RPS on the active MPU and the one on the standby MPU back up each other. RPSs support IPv4/IPv6, MPLS, LDP, and routing protocols, calculate routes, establish LSPs and multicast distribution trees, generate unicast, multicast, and MPLS forwarding tables, and they deliver information concerning all the preceding mentioned to the LPU.
Data Forwarding Process
The Packet Forwarding Engine (PFE) adopts a Network Processor (NP) or an Application Specific Integrated Circuit (ASIC) to implement high-speed packet routing. External memory types include Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), and Net Search Engine (NSE). The SRAM stores forwarding entries; the DRAM stores packets; the NSE performs searching routing table.
Data forwarding processes can be divided into upstream and downstream processes based on the direction of the data flow.
Ne40e M2k
- Upstream process: The Physical Interface Card (PIC) encapsulates packets to frames and then sends them to the PFE. On the PFE of the inbound interface, the system decapsulates the frames and identifies the packet types. It then classifies traffic according to the QoS configurations on the inbound interface. After traffic classification, the system searches the Forwarding Information Base (FIB) for the outbound interfaces and next hops of packets to be forwarded. To forward an IPv4 unicast packet, for instance, the system searches the FIB for the outbound interface and next hop according to the destination IP address of the packet. Finally, the system sends the packets containing information about outbound interfaces and next hops to the traffic management (TM) module.
- Downstream process: Information about packet types that have been identified in the upstream process and about the outbound interfaces is encapsulated through the link layer protocol and the packets are stored in corresponding queues for transmission. If an IPv4 packet whose outbound interface is an Ethernet interface, the system needs to obtain the MAC address of the next hop. Outgoing traffic is then classified according to the QoS configurations on the outbound interfaces. Finally, the system encapsulates the packets with new Layer 2 headers on the outbound interfaces and sends them to the PIC.
Huawei Ne40e Manual
More related topics
The introduction of NetEngine40E series universal service router
Huawei NE Series Routers Overview
The product characteristic of NE40E