Static routing test report
First, the experimental requirements:
1. Based on the IP network itself subnet 172.16.0.0/16
2. In addition to R2 - R4 each have two router interfaces loopback
PC 3.R1 in automatically obtain IP address
4. The whole network up
5. minimize routing entries
6.R4 - normal walking 100M line between R5, 100M fault walk 10M, backup
Second, the experimental topology:
Third, the experimental procedures and processes:
1. division address
- Roads to divide 172.16.0.0/30, 172.16.0.0/19 loopback to divide
- Loopback functions as an interface: TCP test Router / IP protocol stack is working (no default this interface, need to be manually created)
Loopback configuration interface:
r2 (config) #interface loopback 1 // create the loopback interface
r2 (config-if) #ip address 172.16.32.1 255.255.240.0 // loopback interface IP address
- Loopback address in the following table:
2. Establish topology map, indicating the address
- Topology is as follows:
3. Configure the IP address and loopback address for the router:
As shown below:
4. Let the PC under R1 automatically obtain an IP address
- Achieved through DHCP
DHCP: Dynamic Host Configuration Protocol - centralized distribution and management of IP addresses
DHCP configuration:
r1 (config) #ip dhcp pool ccnp // Create DHCP pond
r1 (dhcp-config) #network 172.16.128.0 255.255.255.252 // pond can develop within this issued IP address of the network segment
r1 (dhcp-config) # default-router 172.16.128.1 // specified gateway, activate the interface (the interface can process data packets DHCP)
r1 (dhcp-config) # dns-server 114.114.114.114 // specify a DNS server
- Commonly used DNS server:
- 114.114.114.114
- 8.8.8.8
- 180.76.76.76
- Automatically obtain an IP address in the following figure:
The IP address is written to PC4:
6. Implement the whole network up to:
1) within the network using static routing to achieve up
Static routing configuration:
Use the next hop wording:
r1(config)#ip route 172.16.0.8 255.255.255.252 172.16.0.2
Network_IP_address next hop
1) Anti-empty interface ring:
- Configuring empty interface route to the network segment are summarized in the black hole router
r2(config)#ip route 172.16.32.0 255.255.224.0 null 0
3) Use a floating static route to achieve normal walking 100M, 100M fault walk 10M, to achieve the purpose of the backup path
- Destined for a target segment has multiple paths can be managed by modifying the distance when configuring a static route, to achieve the purpose of the backup path
r5(config)#ip route 172.16.0.0 255.255.255.252 172.16.0.21 5
Administrative distance
- Change management distance without static route entry table, but the configuration takes effect only when the preferred path is disconnected, the path before adding the entry table, as shown below:
100M off when no routing table:
100M off when the routing table:
4) Use the default route up the entire network
- Finding a match at all directly connected, static and dynamic routing later still no match to only match the default
- The default configuration, to each router configuration (ip route 0.0.0.0 0.0.0.0 an interface ip address), then a loopback configuration on the external network connected to the router
r5 (config-if) #ip address 1.1.1.1 255.255.255.0 // loopback
r1 (config) #ip route 0.0.0.0 0.0.0.0 172.16.0.2 // default configuration
- View the routing table, the default route indicated by *
r2#show ip route
7. Detection:
- 100M path is disconnected with PC3 ping PC4, check whether the whole network up
- With PC1 ping 1.1.1.1
Upon examination, the entire network has been up to