CCNA Super Lab 1
Technologies Covered
Basic Device Configuration
Interface Configuration
Virtual LAN (VLAN) Configuration
IP Addressing
Frame Relay
RIP Routing
TCL Scripts / Lab Verification
The purpose of this lab is to help you understand basic router and switch configuration, as well as the purpose of these devices. This lab will cover the OSI model, and what layer different technologies are in on that model.
Your goal for this lab is to configure a fully routed network so that each device can communicate with every other device.
Do not worry about not fully understanding how everything works for this lab. Topics covered in this lab may not be covered in class for several weeks. This lab is to give you a general overview of how networking works, and how the devices are configured. All of this material will be covered at least once more in future labs.
Basic Device Configuration
When starting a lab, there are some basic things that will need to be done on every device. The following should be done at the start of every lab:
Configure the device hostname
Disable domain-name lookup
Configure password encryption
Set console timeout
Configure “logging synchronous” on the console line
Configure passwords
Important: When configuring passwords on any lab, on any device, always use ‘ccie’.
Here is an example from router R1:
Router>
Router>enable
Router#config
Configuring from terminal, memory, or network [terminal]? t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#hostname R1
R1(config)#no ip domain-lookup
R1(config)#service password-encryption
R1(config)#enable secret ccie
R1(config)#line con 0
R1(config-line)#exec-timeout 0 0
R1(config-line)#password ccie
R1(config-line)#logging synchronous
Using the above example as a guide, do the basic device configuration on the remaining devices in your pod.
Interface Configuration
When a router boots with no configuration for the first time, all of its interfaces are shut down. When a switch boots with no configuration, all interfaces are not shut down by default. In order to facilitate proper communication between devices the interfaces used in this lab will be enabled; all other interfaces should be shutdown.
To start, shut down all unused interfaces on the switches. To do this, use the interface range command, and the shutdown command.
CAT1(config)#interface range fa0/1 - 24
CAT1(config-if-range)#shutdown
CAT1(config-if-range)#
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/2, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/3, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/4, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/5, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/6, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/7, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/8, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/9, changed state to administratively down
00:03:40: %LINK-5-CHANGED: Interface FastEthernet0/10, changed state to administratively down
00:03:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/11, changed state to down
00:03:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/18, changed state to down
00:03:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/23, changed state to down
00:03:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/24, changed state to down
CAT1(config-if-range)#interface range fa0/2, fa0/3, fa0/6, fa0/24
CAT1(config-if-range)#no shutdown
CAT1(config-if-range)#
00:04:16: %LINK-3-UPDOWN: Interface FastEthernet0/2, changed state to down
00:04:16: %LINK-3-UPDOWN: Interface FastEthernet0/3, changed state to down
00:04:16: %LINK-3-UPDOWN: Interface FastEthernet0/6, changed state to down
00:04:16: %LINK-3-UPDOWN: Interface FastEthernet0/24, changed state to up
00:04:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/24, changed state to up
To bring an interface up, use the no shutdown command. It may sound counter intuitive to use ‘no shutdown’ however in IOS whenever you want to remove a command you simply put a ‘no’ in front of it. In this case router interfaces have the shutdown command applied to them by default thus it must be removed with the no shutdown command before the interface will pass traffic.
R1(config)#interface fa0/1
R1(config-if)#no shutdown
R1(config-if)#
*Aug 11 20:38:41.019: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
*Aug 11 20:38:42.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up
To bring up serial interfaces, additional commands are required. A serial interface represents a point to point link between two devices. Either side of a serial link is different; one side of the cable has a pin that provides a clock signal for the other device, the Data Circuit-Terminating Equipment (DCE). The other side is called the Data Terminal Equipment or DTE. To make serial interfaces work, you must configure a clock rate on the DCE. On the pod diagrams, the DCE is denoted by a red circle. To set the clock rate of an interface, use the clock rate command. As a rule we use a clock rate of 64000 in the labs as that is the highest common clock rate that is advisable on our equipment.
R2(config)#interface s0/1/0
R2(config-if)#clock rate 64000
R2(config-if)#no shutdown
R2(config-if)#
*Aug 11 20:43:45.627: %LINK-3-UPDOWN: Interface Serial0/1/0, changed state to down
R5(config)#interface s0/0/0
R5(config-if)#no shutdown
R5(config-if)#
*Aug 11 21:03:03.195: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
*Aug 11 21:03:04.195: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
|
Layer 7 - Application |
|
Layer 6 - Presentation |
|
Layer 5 - Session |
|
Layer 4 - Transport |
|
Layer 3 – Network |
|
Layer 2 - Data Link · CDP · Protocol Status · Ethernet |
|
Layer 1 - Physical |
Using the above example as a guide, disable all unnecessary interfaces on the switches, and enable all necessary interfaces on the routers. Use the Physical Lab diagram as a guide to determine which interfaces are needed.
Confirmation: There are a
number of commands to verify layer 2 connectivity.
Use the show interface
command to verify line and protocol status.
R1#show interface fa0/1
FastEthernet0/1 is up, line protocol is up
Hardware is MV96340 Ethernet, address is 001a.2f52.6a79 (bia 001a.2f52.6a79)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:04, output 00:00:02, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
47 packets input, 19042 bytes
Received 47 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
44 packets output, 8006 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
R2#show interface s0/1/0
Serial0/1/0 is up, line protocol is up
Hardware is GT96K Serial
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input 00:00:08, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/1/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 1158 kilobits/sec
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
48 packets input, 4774 bytes, 0 no buffer
Received 46 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
51 packets output, 5820 bytes, 0 underruns
0 output errors, 0 collisions, 8 interface resets
0 output buffer failures, 0 output buffers swapped out
24 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
Use the show cdp neighbors command to verify layer 2 adjacencies.
R1#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
CAT2 Fas 0/1 172 S I WS-C3560- Fas 0/1
R2#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
CAT1 Fas 0/0 160 S I WS-C3560- Fas 0/2
R5 Ser 0/1/0 120 R S I 2811 Ser 0/0/0
R3#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
CAT2 Fas 0/1 144 S I WS-C3560- Fas 0/3
CAT1 Fas 0/0 139 S I WS-C3560- Fas 0/3
R5 Ser 0/1/0 170 R S I 2811 Ser 0/0/1
R4#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
CAT2 Fas 0/1 140 S I WS-C3560- Fas 0/4
R5#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
R2 Ser 0/0/0 177 R S I 2811 Ser 0/1/0
R3 Ser 0/0/1 149 R S I 2811 Ser 0/1/0
R6#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
CAT1 Fas 0/0 125 S I WS-C3560- Fas 0/6
CAT1#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone
Device ID Local Intrfce Holdtme Capability Platform Port ID
R2 Fas 0/2 179 R S I 2811 Fas 0/0
R3 Fas 0/3 129 R S I 2811 Fas 0/0
R6 Fas 0/6 161 R S I 2811 Fas 0/0
CAT2 Fas 0/24 126 S I WS-C3560-2Fas 0/24
CAT2#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone
Device ID Local Intrfce Holdtme Capability Platform Port ID
R3 Fas 0/3 124 R S I 2811 Fas 0/1
R1 Fas 0/1 146 R S I 2811 Fas 0/1
R4 Fas 0/4 137 R S I 2811 Fas 0/1
CAT1 Fas 0/24 176 S I WS-C3560-2Fas 0/24
VLAN Configuration
In order for two devices on an Ethernet network to communicate, they must be on the same LAN. On most switches that you may be familiar with, this means connecting devices to the same switch. This works great if you want every device to be able to talk with each other. Sometimes you may need to have two devices talking to each other, and another two devices talking to each other, but not be able to talk between the two groups. For instance, you have an accounting and a marketing department, and you want them to be able to communicate within their individual departments, but not between departments, for security reasons. You could buy another switch, put one department on one switch, and the other department on the other switch, or you could use VLANs. By configuring ports for one department in one VLAN, and ports for the other department in another VLAN, you are separating the computers as if they were plugged into different switches. Devices in one VLAN cannot talk to devices in another VLAN without first going through a router. This would, for example, allow you to put security measures in place on the router to allow only approved traffic between the computers in different departments.
|
Layer 7 - Application |
|
Layer 6 - Presentation |
|
Layer 5 - Session |
|
Layer 4 - Transport |
|
Layer 3 – Network |
|
Layer 2 - Data Link · VLANs · Switches · MAC Addresses |
|
Layer 1 - Physical |
Now let’s say this company is in a multi-story building. Unfortunately, the marketing and accounting departments are dispersed between two floors, and there is a switch on each floor. We could run two cables between them, one for the accounting VLAN, and one for the marketing VLAN, but this is not very scalable. Instead, we can use one cable between the two switches and setup VLAN trunking. What VLAN trunking allows us to do is to use one cable between two switches to transmit data from different VLANs while maintain separation between those VLANs. The way this works is that when a switch sends data out of an interface configured as a trunk, it puts a special tag in the frame indicating what VLAN that data belongs to. When the adjacent switch receives this data frame, it looks at this tag to determine what VLAN it belongs to.
VLANs and switches operate at layer 2 of the OSI model. MAC addresses are layer 2 addresses used for communicating Ethernet LANs.
To configure a port to be in a VLAN, use the switchport access vlan command and the switchport mode access command on the switch.
CAT1(config)#interface fa0/2
CAT1(config-if)#switchport access vlan 23
% Access VLAN does not exist. Creating vlan 23
CAT1(config-if)#switchport mode access
CAT1(config-if)#interface fa0/3
CAT1(config-if)#switchport access vlan 34
% Access VLAN does not exist. Creating vlan 34
CAT1(config-if)#switchport mode access
CAT1(config-if)#interface fa0/6
CAT1(config-if)#switchport access vlan 16
% Access VLAN does not exist. Creating vlan 16
CAT1(config-if)#switchport mode access
To configure a trunk between two switches, use the switchport trunk encapsulation dot1q command, the switchport trunk allowed vlan command, and the switchport mode trunk command.
CAT1(config)#interface fa0/24
CAT1(config-if)#switchport trunk encapsulation dot1q
CAT1(config-if)#switchport trunk allowed vlan 16,23,34
CAT1(config-if)#switchport mode trunk
CAT1(config-if)#
00:15:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/24, changed state to down
00:15:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/24, changed state to up
Configure all Ethernet ports to be in the correct VLAN. Use the physical and logical diagrams to determine which VLAN each port should be in. Using the example above as a guide, configure a trunk between CAT1 and CAT2.
Confirmation: Use the show vlan brief command to verify VLAN port configuration.
CAT1#show vlan brief
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/1, Fa0/4, Fa0/5, Fa0/7
Fa0/8, Fa0/9, Fa0/10, Fa0/11
Fa0/12, Fa0/13, Fa0/14, Fa0/15
Fa0/16, Fa0/17, Fa0/18, Fa0/19
Fa0/20, Fa0/21, Fa0/22, Fa0/23
Gi0/1, Gi0/2
16 VLAN0016 active Fa0/6
23 VLAN0023 active Fa0/2
34 VLAN0034 active Fa0/3
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup
CAT2#show vlan brief
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/2, Fa0/5, Fa0/6, Fa0/7
Fa0/8, Fa0/9, Fa0/10, Fa0/11
Fa0/12, Fa0/13, Fa0/14, Fa0/15
Fa0/16, Fa0/17, Fa0/18, Fa0/19
Fa0/20, Fa0/21, Fa0/22, Fa0/23
Gi0/1, Gi0/2
16 VLAN0016 active Fa0/1
23 VLAN0023 active Fa0/3
34 VLAN0034 active Fa0/4
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup
Use the show interfaces trunk command to verify VLAN trunking.
CAT1#show interfaces trunk
Port Mode Encapsulation Status Native vlan
Fa0/24 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa0/24 16,23,34
Port Vlans allowed and active in management domain
Fa0/24 16,23,34
Port Vlans in spanning tree forwarding state and not pruned
Fa0/24 16,23,34
CAT2#show interfaces trunk
Port Mode Encapsulation Status Native vlan
Fa0/24 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa0/24 16,23,34
Port Vlans allowed and active in management domain
Fa0/24 16,23,34
Port Vlans in spanning tree forwarding state and not pruned
Fa0/24 16,23,34
IP Addressing
|
Layer 7 - Application |
|
Layer 6 - Presentation |
|
Layer 5 - Session |
|
Layer 4 - Transport |
|
Layer 3 – Network · IP Address · Ping |
|
Layer 2 - Data Link |
|
Layer 1 - Physical |
IP addresses are hierarchical addresses used for communication between devices on different layer 2 segments. Each Layer 2 segment is assigned a subnetwork of IP addresses, the size of these subnetworks is determined by the subnet mask. For the purposes of this lab all subnet masks will be set to 255.255.255.0 or a /24.
To put an IP address on an interface, use the ip address command. The syntax for this command is
ip address <ip address> <mask>
R1(config)#interface fa0/1
R1(config-if)#ip address 172.16.16.1 255.255.255.0
R2(config)#interface fa0/0
R2(config-if)#ip address 172.16.23.2 255.255.255.0
R2(config-if)#interface s0/1/0
R2(config-if)#ip address 192.168.25.2 255.255.255.0
Some commands in IOS overwrite the previous command, while others add on. The ip address command overwrites the previous IP address, and replaced it with the new one.
Using the diagrams, finish addressing the remaining Ethernet and Serial interfaces. Do not configure the interfaces that are connected to the Frame Relay Switch (FRS).
Confirmation: To verify IP addressing, use the show ip interface brief command.
R1#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 unassigned YES unset administratively down down
FastEthernet0/1 172.16.16.1 YES manual up up
Serial0/0/0 unassigned YES unset administratively down down
Serial0/0/1 unassigned YES unset administratively down down
Serial0/1/0 unassigned YES unset administratively down down
Serial0/1/1 unassigned YES unset administratively down down
R2#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 172.16.23.2 YES manual up up
FastEthernet0/1 unassigned YES unset administratively down down
Serial0/0/0 unassigned YES unset administratively down down
Serial0/0/1 unassigned YES unset administratively down down
Serial0/1/0 192.168.25.2 YES manual up up
Serial0/1/1 unassigned YES unset administratively down down
R3#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 172.16.34.3 YES manual up up
FastEthernet0/1 172.16.23.3 YES manual up up
Serial0/0/0 unassigned YES unset administratively down down
Serial0/0/1 unassigned YES unset administratively down down
Serial0/1/0 192.168.35.3 YES manual up up
Serial0/1/1 unassigned YES unset administratively down down
R4#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 unassigned YES unset administratively down down
FastEthernet0/1 172.16.34.4 YES manual up up
Serial0/0/0 unassigned YES unset administratively down down
Serial0/0/1 unassigned YES unset administratively down down
Serial0/1/0 unassigned YES unset administratively down down
Serial0/1/1 unassigned YES unset administratively down down
Serial0/2/0 unassigned YES unset administratively down down
Serial0/2/1 unassigned YES unset administratively down down
R5#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 unassigned YES unset administratively down down
FastEthernet0/1 unassigned YES unset administratively down down
Serial0/0/0 192.168.25.5 YES manual up up
Serial0/0/1 192.168.35.5 YES manual up up
Serial0/1/0 unassigned YES unset administratively down down
Serial0/1/1 unassigned YES unset administratively down down
Serial0/2/0 unassigned YES unset administratively down down
Serial0/2/1 unassigned YES unset administratively down down
R6#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 172.16.16.6 YES manual up up
FastEthernet0/1 unassigned YES unset administratively down down
Serial0/0/0 unassigned YES unset administratively down down
Serial0/0/1 unassigned YES unset administratively down down
Serial0/1/0 unassigned YES unset administratively down down
Serial0/1/1 unassigned YES unset administratively down down
To test Layer 3 connectivity, use the ping command. Each device should be able to ping its neighbors. Do not worry if the first ping or two fails.
R1#ping 172.16.16.6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.16.6, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/4 ms
R2#ping 172.16.23.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.23.3, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms
R2#ping 192.168.25.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.25.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms
R3#ping 172.16.23.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.23.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
R3#ping 172.16.34.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.34.4, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms
R3#ping 192.168.35.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.35.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms
R4#ping 172.16.34.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.34.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
R5#ping 192.168.25.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.25.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/28 ms
R5#ping 192.168.35.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.35.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms
R6#ping 172.16.16.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.16.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Frame Relay
|
Layer 7 - Application |
|
Layer 6 - Presentation |
|
Layer 5 - Session |
|
Layer 4 - Transport |
|
Layer 3 – Network |
|
Layer 2 - Data Link · Frame Relay |
|
Layer 1 - Physical |
Frame Relay is a Layer 2 protocol used for Wide Area Networking. Companies with multiple offices will often use frame-relay in their wide area network (WAN).
For addressing, frame relay uses a field called the Data Link Connection Identifier (DLCI). On the logical diagram, the numbers in the clouds represent the DLCI. For example, for R1 to send data to R3 it uses DLCI 103, and to send data to R2 it uses DLCI 102. For R2 to send data back to R1, it uses DLCI 201. The network between R1, R2 and R3 is called a full mesh network, as each router has a Permanent Virtual Circuit (PVC) to each other device. The network between R1 and R4 is called a point to point network.
To configure the Frame Relay Switch (FRS), use the configuration posted on the lab list page.
To configure frame relay on an interface, use the encapsulation frame-relay, no frame-relay inverse-arp and frame-relay map ip commands. The syntax for the frame-relay map ip command is
frame-relay map ip <ip address> <dlci> broadcast
R1(config)#interface s0/0/0
R1(config-if)#ip address 10.0.123.1 255.255.255.0
R1(config-if)#encapsulation frame-relay
R1(config-if)#no frame-relay inverse-arp
R1(config-if)#frame-relay map ip 10.0.123.1 102
R1(config-if)#frame-relay map ip 10.0.123.3 103 broadcast
R1(config-if)#frame-relay map ip 10.0.123.2 102 broadcast
R1(config-if)#no shutdown
R1(config-if)#
*Aug 11 21:01:16.163: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
*Aug 11 21:01:27.163: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
R2(config)#interface s0/0/0
R2(config-if)#ip address 10.0.123.2 255.255.255.0
R2(config-if)#encapsulation frame-relay
R2(config-if)#no frame-relay inverse-arp
R2(config-if)#frame-relay map ip 10.0.123.1 201 broadcast
R2(config-if)#frame-relay map ip 10.0.123.2 201
R2(config-if)#frame-relay map ip 10.0.123.3 203 broadcast
R2(config-if)#no shutdown
R2(config-if)#
*Aug 11 21:06:06.791: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
*Aug 11 21:06:17.791: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
R3(config)#interface s0/0/0
R3(config-if)#ip address 10.0.123.3 255.255.255.0
R3(config-if)#encapsulation frame-relay
R3(config-if)#no frame-relay inverse-arp
R3(config-if)#frame-relay map ip 10.0.123.1 301 broadcast
R3(config-if)#frame-relay map ip 10.0.123.2 302 broadcast
R3(config-if)#frame-relay map ip 10.0.123.3 301
R3(config-if)#no shutdown
R3(config-if)#
*Aug 11 21:37:55.975: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
*Aug 11 21:38:06.975: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
R4(config)#interface s0/0/0
R4(config-if)#ip address 10.0.14.4 255.255.255.0
R4(config-if)#encapsulation frame-relay
R4(config-if)#no frame-relay inverse-arp
R4(config-if)#frame-relay map ip 10.0.14.4 401
R4(config-if)#frame-relay map ip 10.0.14.1 401 broadcast
R4(config-if)#no shutdown
R4(config-if)#
*Aug 11 20:55:12.027: %LINK-3-UPDOWN: Interface Serial0/0/0, changed state to up
*Aug 11 20:55:23.027: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
To configure frame relay on a point to point sub-interface, use the frame-relay interface-dlci command.
R1(config)#interface s0/0/0.14 point-to-point
R1(config-subif)#ip address 10.0.14.1 255.255.255.0
R1(config-subif)#frame-relay interface-dlci 104
R1(config-fr-dlci)#exit
R1(config-subif)#
Using the commands above, configure frame relay on all applicable devices.
Confirmation: To verify frame relay, use the show frame-relay pvc, show frame-relay map, and show frame-relay lmi commands.
R1#show frame-relay pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 3 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:09:30, last time pvc status changed 00:05:59
DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:09:31, last time pvc status changed 00:05:01
DLCI = 104, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0.14
input pkts 0 output pkts 3 in bytes 0
out bytes 1029 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 3 out bcast bytes 1029
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:09:22, last time pvc status changed 00:02:32
R1#show frame-relay map
Serial0/0/0 (up): ip 10.0.123.2 dlci 102(0x66,0x1860), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 10.0.123.1 dlci 102(0x66,0x1860), static,
CISCO, status defined, active
Serial0/0/0 (up): ip 10.0.123.3 dlci 103(0x67,0x1870), static,
broadcast,
CISCO, status defined, active
Serial0/0/0.14 (up): point-to-point dlci, dlci 104(0x68,0x1880), broadcast
status defined, active
R1#show frame-relay lmi
LMI Statistics for interface Serial0/0/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 57 Num Status msgs Rcvd 58
Num Update Status Rcvd 0 Num Status Timeouts 0
Last Full Status Req 00:00:36 Last Full Status Rcvd 00:00:36
R2#show frame-relay pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 2 0 0 0
Switched 0 0 0 0
Unused 1 0 0 0
DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:10:42, last time pvc status changed 00:10:24
DLCI = 203, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:10:41, last time pvc status changed 00:09:06
DLCI = 204, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:10:38, last time pvc status changed 00:06:38
R2#show frame-relay map
Serial0/0/0 (up): ip 10.0.123.1 dlci 201(0xC9,0x3090), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 10.0.123.2 dlci 201(0xC9,0x3090), static,
CISCO, status defined, active
Serial0/0/0 (up): ip 10.0.123.3 dlci 203(0xCB,0x30B0), static,
broadcast,
CISCO, status defined, active
R2#show frame-relay lmi
LMI Statistics for interface Serial0/0/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 65 Num Status msgs Rcvd 67
Num Update Status Rcvd 0 Num Status Timeouts 0
Last Full Status Req 00:00:48 Last Full Status Rcvd 00:00:48
R3#show frame-relay pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 2 0 0 0
Switched 0 0 0 0
Unused 1 0 0 0
DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:11:43, last time pvc status changed 00:11:28
DLCI = 302, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:11:45, last time pvc status changed 00:11:30
DLCI = 304, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:11:41, last time pvc status changed 00:08:41
R3#show frame-relay map
Serial0/0/0 (up): ip 10.0.123.1 dlci 301(0x12D,0x48D0), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 10.0.123.2 dlci 302(0x12E,0x48E0), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 10.0.123.3 dlci 301(0x12D,0x48D0), static,
CISCO, status defined, active
R3#show frame-relay lmi
LMI Statistics for interface Serial0/0/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 71 Num Status msgs Rcvd 72
Num Update Status Rcvd 0 Num Status Timeouts 0
Last Full Status Req 00:00:52 Last Full Status Rcvd 00:00:52
R4#show frame-relay pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 1 0 0 0
Switched 0 0 0 0
Unused 2 0 0 0
DLCI = 401, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 3 output pkts 0 in bytes 1029
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:00:22, last time pvc status changed 00:00:22
DLCI = 402, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:00:14, last time pvc status changed 00:00:14
DLCI = 403, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:00:15, last time pvc status changed 00:00:15
R4#show frame-relay map
Serial0/0/0 (up): ip 10.0.14.1 dlci 401(0x191,0x6410), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 10.0.14.4 dlci 401(0x191,0x6410), static,
CISCO, status defined, active
R4#show frame-relay lmi
LMI Statistics for interface Serial0/0/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 3 Num Status msgs Rcvd 3
Num Update Status Rcvd 0 Num Status Timeouts 0
Last Full Status Req never Last Full Status Rcvd 00:00:22
To test Layer 3 connectivity, use the ping command. Each device should be able to ping its neighbors.
R1#ping 10.0.123.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/115/120 ms
R1#ping 10.0.123.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
R1#ping 10.0.123.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
R1#ping 10.0.14.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.14.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/113/116 ms
R1#ping 10.0.14.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.14.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
R2#ping 10.0.123.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
R2#ping 10.0.123.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/113/120 ms
R2#ping 10.0.123.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
R3#ping 10.0.123.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/56 ms
R3#ping 10.0.123.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
R3#ping 10.0.123.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/114/120 ms
R4#ping 10.0.14.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.14.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/56 ms
R4#ping 10.0.14.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.14.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/115/120 ms
RIP Routing
|
Layer 7 - Application |
|
Layer 6 - Presentation |
|
Layer 5 - Session |
|
Layer 4 - Transport |
|
Layer 3 – Network · Routing |
|
Layer 2 - Data Link |
|
Layer 1 - Physical |
At this point in the lab, each router can send data to routers that are adjacent to itself. In order for routers to know how to get to all of the networks, you must configure a routing protocol. A routing protocol advertises what networks that router knows how to get to. Other routers then learn this information, and are able to send data to those networks. In this lab we will be configuring the RIP routing protocol.
To configure RIP, use the router rip, version 2, no auto-summary, and the network commands. The syntax for the network command is
network <network address>
The network command begins sending routing updates out all matching interfaces while at the same time it begins advertising all networks matching the statement to neighboring routers.
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#network 10.0.0.0
R1(config-router)#network 172.16.0.0
R1(config-router)#no auto-summary
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#network 10.0.0.0
R2(config-router)#network 172.16.0.0
R2(config-router)#network 192.168.25.0
R2(config-router)#no auto-summary
R3(config)#router rip
R3(config-router)#version 2
R3(config-router)#network 10.0.0.0
R3(config-router)#network 172.16.0.0
R3(config-router)#network 192.168.35.0
R3(config-router)#no auto-summary
R4(config)#router rip
R4(config-router)#version 2
R4(config-router)#network 10.0.0.0
R4(config-router)#network 172.16.0.0
R4(config-router)#no auto-summary
R5(config)#router rip
R5(config-router)#version 2
R5(config-router)#network 192.168.25.0
R5(config-router)#network 192.168.35.0
R5(config-router)#no auto-summary
R6(config)#router rip
R6(config-router)#version 2
R6(config-router)#network 172.16.0.0
R6(config-router)#no auto-summary
The network command does not overwrite previous commands; it adds a new entry with the new network address. To remove a network command, use the no network command.
R6(config-router)#network 172.17.0.0
R6(config-router)#no network 172.17.0.0
Using the above examples and the network diagrams, finish configuring RIP on all of the routers.
Confirmation: To verify routing, there are a number of commands at your disposal. Over time, you will learn many ways to diagnose and troubleshoot routing problems. Start off with the show ip protocols command.
R1#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 14 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/1 2 2
Serial0/0/0 2 2
Serial0/0/0.14 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.16.0.0
Routing Information Sources:
Gateway Distance Last Update
10.0.14.4 120 00:00:05
10.0.123.3 120 00:00:12
10.0.123.2 120 00:00:26
Distance: (default is 120)
R2#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 17 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
Serial0/0/0 2 2
Serial0/1/0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.16.0.0
192.168.25.0
Routing Information Sources:
Gateway Distance Last Update
10.0.123.1 120 00:00:26
10.0.123.3 120 00:00:21
192.168.25.5 120 00:00:06
172.16.23.3 120 00:00:01
Distance: (default is 120)
R3#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 26 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
FastEthernet0/1 2 2
Serial0/0/0 2 2
Serial0/1/0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.16.0.0
192.168.35.0
Routing Information Sources:
Gateway Distance Last Update
192.168.35.5 120 00:00:10
10.0.123.1 120 00:00:08
10.0.123.2 120 00:00:18
Gateway Distance Last Update
172.16.34.4 120 00:00:07
172.16.23.2 120 00:00:19
Distance: (default is 120)
R4#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 19 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/1 2 2
Serial0/0/0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.16.0.0
Routing Information Sources:
Gateway Distance Last Update
10.0.14.1 120 00:00:07
172.16.34.3 120 00:00:07
Distance: (default is 120)
R5#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 9 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
Serial0/0/0 2 2
Serial0/0/1 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
192.168.25.0
192.168.35.0
Routing Information Sources:
Gateway Distance Last Update
192.168.35.3 120 00:00:15
192.168.25.2 120 00:00:04
Distance: (default is 120)
R6#show ip protocols
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 12 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
172.16.0.0
Routing Information Sources:
Gateway Distance Last Update
172.16.16.1 120 00:00:19
Distance: (default is 120)
Now try the show ip route command. You will use this command a lot. Using your book or the internet, find out what each of the columns means.
R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
R 192.168.25.0/24 [120/1] via 10.0.123.2, 00:00:24, Serial0/0/0
172.16.0.0/24 is subnetted, 3 subnets
R 172.16.34.0 [120/1] via 10.0.123.3, 00:00:04, Serial0/0/0
[120/1] via 10.0.14.4, 00:00:01, Serial0/0/0.14
R 172.16.23.0 [120/1] via 10.0.123.3, 00:00:04, Serial0/0/0
[120/1] via 10.0.123.2, 00:00:24, Serial0/0/0
C 172.16.16.0 is directly connected, FastEthernet0/1
10.0.0.0/24 is subnetted, 2 subnets
C 10.0.14.0 is directly connected, Serial0/0/0.14
C 10.0.123.0 is directly connected, Serial0/0/0
R 192.168.35.0/24 [120/1] via 10.0.123.3, 00:00:05, Serial0/0/0
R2#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.25.0/24 is directly connected, Serial0/1/0
172.16.0.0/24 is subnetted, 3 subnets
R 172.16.34.0 [120/1] via 172.16.23.3, 00:00:17, FastEthernet0/0
[120/1] via 10.0.123.3, 00:00:07, Serial0/0/0
C 172.16.23.0 is directly connected, FastEthernet0/0
R 172.16.16.0 [120/1] via 10.0.123.1, 00:00:18, Serial0/0/0
10.0.0.0/24 is subnetted, 2 subnets
R 10.0.14.0 [120/1] via 10.0.123.1, 00:00:18, Serial0/0/0
C 10.0.123.0 is directly connected, Serial0/0/0
R 192.168.35.0/24 [120/1] via 192.168.25.5, 00:00:00, Serial0/1/0
[120/1] via 172.16.23.3, 00:00:18, FastEthernet0/0
[120/1] via 10.0.123.3, 00:00:08, Serial0/0/0
R3#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
R 192.168.25.0/24 [120/1] via 192.168.35.5, 00:00:22, Serial0/1/0
[120/1] via 172.16.23.2, 00:00:03, FastEthernet0/1
[120/1] via 10.0.123.2, 00:00:01, Serial0/0/0
172.16.0.0/24 is subnetted, 3 subnets
C 172.16.34.0 is directly connected, FastEthernet0/0
C 172.16.23.0 is directly connected, FastEthernet0/1
R 172.16.16.0 [120/1] via 10.0.123.1, 00:00:21, Serial0/0/0
10.0.0.0/24 is subnetted, 2 subnets
R 10.0.14.0 [120/1] via 172.16.34.4, 00:00:13, FastEthernet0/0
[120/1] via 10.0.123.1, 00:00:22, Serial0/0/0
C 10.0.123.0 is directly connected, Serial0/0/0
C 192.168.35.0/24 is directly connected, Serial0/1/0
R4#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
R 192.168.25.0/24 [120/2] via 172.16.34.3, 00:00:19, FastEthernet0/1
[120/2] via 10.0.14.1, 00:00:17, Serial0/0/0
172.16.0.0/24 is subnetted, 3 subnets
C 172.16.34.0 is directly connected, FastEthernet0/1
R 172.16.23.0 [120/1] via 172.16.34.3, 00:00:19, FastEthernet0/1
R 172.16.16.0 [120/1] via 10.0.14.1, 00:00:17, Serial0/0/0
10.0.0.0/24 is subnetted, 2 subnets
C 10.0.14.0 is directly connected, Serial0/0/0
R 10.0.123.0 [120/1] via 172.16.34.3, 00:00:20, FastEthernet0/1
[120/1] via 10.0.14.1, 00:00:18, Serial0/0/0
R 192.168.35.0/24 [120/1] via 172.16.34.3, 00:00:20, FastEthernet0/1
R5#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.25.0/24 is directly connected, Serial0/0/0
172.16.0.0/24 is subnetted, 3 subnets
R 172.16.34.0 [120/1] via 192.168.35.3, 00:00:22, Serial0/0/1
R 172.16.23.0 [120/1] via 192.168.35.3, 00:00:22, Serial0/0/1
[120/1] via 192.168.25.2, 00:00:08, Serial0/0/0
R 172.16.16.0 [120/2] via 192.168.35.3, 00:00:22, Serial0/0/1
[120/2] via 192.168.25.2, 00:00:08, Serial0/0/0
10.0.0.0/24 is subnetted, 2 subnets
R 10.0.14.0 [120/2] via 192.168.35.3, 00:00:23, Serial0/0/1
[120/2] via 192.168.25.2, 00:00:10, Serial0/0/0
R 10.0.123.0 [120/1] via 192.168.35.3, 00:00:23, Serial0/0/1
[120/1] via 192.168.25.2, 00:00:10, Serial0/0/0
C 192.168.35.0/24 is directly connected, Serial0/0/1
R6#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
R 192.168.25.0/24 [120/2] via 172.16.16.1, 00:00:24, FastEthernet0/0
172.16.0.0/24 is subnetted, 3 subnets
R 172.16.34.0 [120/2] via 172.16.16.1, 00:00:24, FastEthernet0/0
R 172.16.23.0 [120/2] via 172.16.16.1, 00:00:24, FastEthernet0/0
C 172.16.16.0 is directly connected, FastEthernet0/0
10.0.0.0/24 is subnetted, 2 subnets
R 10.0.14.0 [120/1] via 172.16.16.1, 00:00:24, FastEthernet0/0
R 10.0.123.0 [120/1] via 172.16.16.1, 00:00:24, FastEthernet0/0
R 192.168.35.0/24 [120/2] via 172.16.16.1, 00:00:25, FastEthernet0/0
TCL Scripts / Lab Verification
|
Layer 7 - Application |
|
Layer 6 - Presentation |
|
Layer 5 - Session |
|
Layer 4 - Transport |
|
Layer 3 – Network · Ping |
|
Layer 2 - Data Link |
|
Layer 1 - Physical |
At the end of each lab, you will need to verify that everything is working. To do this, you will need to ping from each device to every IP address in your network. This is not practical to do by hand, so we will use a handy tool called TCL (Pronounced tickle) scripts.
The basic syntax for this command is
tclsh
foreach address {
<address 1>
<address 2>
<address 3>
<…>
} {
ping $address
}
tclquit
R1#tclsh
R1(tcl)#foreach address {
+>(tcl)#10.0.14.1
+>(tcl)#10.0.14.4
+>(tcl)#10.0.123.1
+>(tcl)#10.0.123.2
+>(tcl)#10.0.123.3
+>(tcl)#172.16.16.1
+>(tcl)#172.16.16.6
+>(tcl)#172.16.23.2
+>(tcl)#172.16.23.3
+>(tcl)#172.16.34.3
+>(tcl)#172.16.34.4
+>(tcl)#192.168.25.2
+>(tcl)#192.168.25.5
+>(tcl)#192.168.35.3
+>(tcl)#192.168.35.5
+>(tcl)#} {
+>(tcl)# ping $address
+>(tcl)#}
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.14.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/114/120 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.14.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/113/120 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.123.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.16.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.16.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.23.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.23.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.34.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.34.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.25.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.25.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/88 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.35.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.35.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/88 ms
For any ping that fails, go back and recheck the previous sections of the lab. Do the best you can to troubleshoot. If you cannot figure it out, call over a TA to give you a hand.
Once you have verified that the script works on every device, submit it to WebCT to be graded.