1. Add modules to several routers and configure ip addresses for PCs.
At the same time, I am used to adding modules to the vro. the commonly used ports are s0/0/0.
It is a 2811 vro. The topology of www.2cto.com is as follows: 2. Configure several routers (basic configuration and Frame Relay configuration) Here I will take R1 as an example, because R2 and R3 are similar. Ontinue with configuration dialog? [Yes/no]: no
Router> en
Router # conf t
Router (config) # host R1
R1 (config) # int s0/0/0
R1 (config-if) # cl ra 64000
R1 (config-if) # no shut
% LINK-5-CHANGED: Interface Serial0/0/0, changed state to up
R1 (config-if) # encapsulation frame-relay
% LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
Fra
R1 (config-if) # frame-relay lm-type cisco
R1 (config-if) # int s0/0/0.1 point-to-point
% LINK-5-CHANGED: Interface Serial0/0/0.1, changed state to up
% LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0.1, changed state to up
R1 (config-subif) # ip add 192.168.1.1 255.255.255.0
R1 (config-subif) # frame-relay interface-dlci 102
R1 (config-subif) # ex
R1 (config) # int s0/0/0.2 point-to-point
R1 (config-subif) # ip add 192.168.2.1 255.255.255.0
R1 (config-subif) # frame-relay interface-dlci 103
R1 (config-subif) # ex
R1 (config) # router rip
R1 (config-router) # net 192.168.10.1
R1 (config-router) # net 192.168.1.1
R1 (config-router) # net 192.168.2.1
R1 (config-router) # ^ Z
Note: R2 and R3 are configured in the same way, but note the correspondence: that is, 102 of R1 and 201 of R2 are in the same network segment, 103 of R1 and 301 of R3 are in the same network segment, and 203 of R2 and 302 of R3 are in the same network segment. The objective of configuring the rip Protocol is to ensure the connectivity of the entire network. Of course, other protocols like ospf can also be used. 3. Configure the intermediate network and cloud. here we need to pay attention to the correspondence, that is, the correspondence of the frame relay module. In other words, we need to ensure that the Network is smooth (there is a going back ). 4. Check whether the network is actually connected, that is, use the ping command to check www.2cto.com. This shows that the network connectivity is good, the lab is successful, and the network can communicate, to achieve higher security, you must use other protocols and other devices. R1 # ping 192.168.3.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.3.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 63/85/94 MS
R1 # ping 192.168.3.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 47/57/63 MS
R1 # ping 192.168.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 172/184/188 MS
R2 # ping 192.168.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 62/62/63 MS
R2 # ping 192.168.10.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.10.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 64/87/94 MS
R2 # ping 192.168.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.10.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 47/59/63 MS
R2 # ping 192.168.20.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.20.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/12/15 MS
R2 # ping 192.168.30.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 93/93/94 MS
R2 # ping 192.168.3.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.3.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 47/59/63 MS
R2 # ping 192.168.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 110/119/125 MS
R3 # ping 192.168.30.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.10, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 16/27/32 MS
R3 # ping 192.168.30.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/29/32 MS
R3 # ping 192.168.30.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 31/31/32 MS
R3 # ping 192.168.30.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.30.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/6/16 MS
R3 # ping 192.168.3.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 47/59/63 MS