This appendix contains information about the equipment requirements for the Configuration Exercises in this book, along with the configuration commands for the backbone routers. This appendix is organized into the following sections:
This book provides Configuration Exercises to give you practice in configuring routers. If you have access to real hardware, you can try these exercises on your routers; this appendix provides a list of recommended equipment and configuration commands for the backbone routers. However, even if you do not have access to any routers, you can go through the exercises and keep a log of your own running configurations or just read through the solutions. Commands used and solutions to the Configuration Exercises are provided within the exercises in each chapter.
In the Configuration Exercises in this book, the network is assumed to consist of two pods, each with four routers. The pods are interconnected to a backbone. You configure one of the pods, pod 1. No interaction between the two pods is required, although you might see some routes from the other pod in your routing tables in some exercises if you have it configured. In most of the exercises, the backbone has only one router; in some cases, another router is added to the backbone. Each of the Configuration Exercises in this book assumes that you have completed the previous chapters’ Configuration Exercises on your pod.
The equipment listed in Table B-1 is for two pods (each with four routers) and the backbone (with three routers).
Table B-1. Configuration Exercise Equipment Requirements for Two Pods and the Backbone
Quantity | Required Product Description | Recommended Product Number |
|---|---|---|
3 | PC, with one COM port, running Hyperterminal. One per pod and one for the backbone. The backbone PC must also have a 10/100 Ethernet interface; it may also function as a Trivial File Transfer Protocol (TFTP) server and would therefore also have TFTP server software installed. (Refer to the “TFTP Server Setup” section for more information.) | — |
3 | A/B/C/D switch to connect the pod or backbone PC to the router’s console port. | — |
1 | 4-port 10/100 switch to interconnect the backbone routers and the backbone PC. | Any switch with 410/100 ports |
4 | Router with 1 FastEthernet port and 1 serial port (2 per pod). | Cisco 2811 (with 1 WIC 2 A/S installed) |
4 | Router with 2 serial ports and 1 FastEthernet port (2 per pod). | Cisco 2811 (with 1 WIC 2 A/S installed) |
2 | Router with 1 FastEthernet port and 1 serial port (for the backbone BBR1 and BBR2 routers). | Cisco 2811 (with 1 WIC 2 A/S installed) |
10 | 2-port async/sync serial WAN interface card for 2811 routers. | WIC 2 A/S |
10 | Version 12.4(4)T1 Cisco IOS advanced IP services software for the pod and backbone BBR1 and BBR2 routers (refer to your router’s documentation for Flash and RAM memory requirements). | c2800nm-advipservicesk9-mz.124-4.T1 |
1 | Router with 1 Ethernet port and 6 serial ports (for the Frame_Switch Frame Relay backbone). | Cisco 3620 (with NM-1E module installed in slot 0 [on the right] and NM-8A/S module installed in slot 1 [on the left]) |
1 | Version 12.1(15) or later Cisco IOS Enterprise Plus software for the Frame_Switch Frame Relay backbone router (refer to your router’s documentation for Flash and RAM memory requirements). | c3620-js-mz.121-15 |
1 | 8-port asynchronous/synchronous serial network module (for the Frame_Switch Frame Relay backbone router; 6 serial ports required). | NM-8A/S |
1 | 1-port Ethernet Network Module (for the Frame_Switch Frame Relay backbone router). | NM-1E |
11 | Power cord, 110V. | CAB-AC |
10 | V.35 Female data terminal equipment/data circuit-terminating equipment (DTE/DCE) crossover cable | CAB SS 2660x |
4 | Ethernet crossover CAT5 cable. | — |
3 | Ethernet straight-through CAT5 cable. | — |
Key Point: Configuration Exercise Equipment
The Configuration Exercise diagrams and configurations provided in this book assume that the equipment stated in Table B-1 is used. If you use different routers or modules, you must adjust the connections and configurations accordingly.
Key Point: TFTP Functionality Not Required
The backbone PC is referred to as the TFTP server in this appendix and throughout the Configuration Exercises in the rest of the book. However, the Configuration Exercises do not actually use the TFTP functionality; the backbone PC’s IP address is only used as a destination for pings, during connectivity testing in some of the exercises.
If you want to save your configurations to a TFTP server, you should install TFTP server software on the backbone PC.
The TFTP server should be configured with the static IP address 10.254.0.254 255.255.255.0. The default gateway on the TFTP server should be set to its own address, 10.254.0.254. (If you set the default gateway to be one of the core routers, you must change this setting during the Configuration Exercises, because not all core routers can be reached at all times.)
Chapter 9, “Implementing IP Multicast,” includes an IP multicast Configuration Exercise. This exercise assumes that multicast traffic is coming from the backbone, using the 224.x.x.x addresses (where x is the pod number). During our testing, we used a Cisco proprietary traffic generator running on the router that is configured as the Frame Relay switch. Any traffic generator that can generate packets to the 224.x.x.x addresses will suffice.
The network consists of the following:
Two pods, each with four routers named PxR1, PxR2, PxR3, and PxR4, where x = the pod number
Two backbone routers, named BBR1 and BBR2
A third backbone router used as a Frame Relay switch, named Frame_Switch
Figure B-1 shows the Configuration Exercise setup diagram.
Note
Figure B-1 is also posted on the Cisco Press website so that you can print it and copy it when you are doing the Configuration Exercises. See the section “Online Material” in the introduction for details.
The backbone router addresses shown in Figure B-1 are in the configurations provided in the “Backbone Router Configurations” section later in this appendix. The addresses shown for the pod routers will be configured in the Configuration Exercises.
Note
The backbone switch shown between the backbone devices in Figure B-1 is not shown in subsequent Configuration Exercise network diagrams.
The Frame Relay backbone 3620 router requires six serial ports. All interfaces on the 3620 router are DCE. The Serial 0/0/1 interfaces on the PxR1 routers are DCE. The Serial 0/0/0 interfaces on the PxR3 routers are DCE. All other serial interfaces are DTE.
The Frame_Switch Frame Relay backbone router interfaces should be cabled as shown in Table B-2. (Note that interfaces S1/4 and S1/5 on Frame_Switch are unused.)
The BBR1 and BBR2 Fa0/0 router interfaces and the TFTP server (backbone PC) should be connected to the backbone switch.
The remaining pod router interfaces should be cabled as shown in Table B-3.
The backbone routers need to be configured only one time, before the first Configuration Exercise. The text of the configurations is provided in the following sections. To use the configurations, create text files from the information provided. These configurations are written to be sent using the Transfer, Send Text File menu command in Hyperterminal into the devices’ console port. Each configuration assumes that the router has no configuration. In other words, it assumes that the startup configuration has been erased and that the router has been reloaded.
Note
The backbone router configurations are also posted as text files on the Cisco Press website. See the section “Online Material” in the introduction for details.
Note
You might need to modify the configurations provided so that they work with the specific routers you are using. For example, if you have routers with fixed interfaces where we used routers with modular interfaces, you have to change how the interfaces are referenced.
Before sending a configuration file, go into privileged EXEC mode on the router. The configurations have config t commands at the beginning, followed by the necessary configuration commands, and then commands to save the configuration into nonvolatile random-access memory (NVRAM).
Note
In each of the configurations provided, the enable secret password is set to sanfran, and the vty password is set to cisco; you might want to change these passwords.
The last command in each configuration is copy run start. If you create your own text files, enter a carriage return after this command and then another carriage return. This ensures that the configuration is saved and that the router returns to the privileged EXEC prompt.
When testing similar configurations, we ran into a problem on some 3640 routers. Loading the files from Hyperterminal was too fast for the 3640. It would lose some of the commands, and then the rest of the file would get mixed up. To fix this problem in Hyperterminal, do the following:
Select File, Properties.
Click the Settings tab.
Click the ASCII Settings button.
Set the Line Delay to 200 milliseconds. (You might have to increase the line delay further if you get errors.)
Example B-1 provides the text of the configuration file for the BBR1 router.
Example B-1. BBR1 Configuration
! !BBR1 configuration exercise configuration ! ! This file is designed to be copied and pasted into an erased router, at ! the # prompt. ! ! This configuration was tested with the c2800nm-advipservicesk9-mz.124-4.T1 IOS image ! conf t service timestamps debug datetime service timestamps log datetime no service password-encryption ! hostname BBR1 ! enable secret sanfran ! resource policy ! ip subnet-zero ! ip cef ! no ip domain lookup ip multicast-routing ! voice-card 0 no dspfarm ! ip host bbr1 10.254.0.1 172.31.1.3 172.31.2.3 ip host bbr2 10.254.0.2 172.31.11.4 172.31.22.4 ip host Frame_Switch 10.254.0.3 ip host tftp 10.254.0.254 ! ip host P2R4 10.2.3.4 10.2.2.4 ip host P2R3 10.2.1.3 10.2.3.3 ip host P2R2 10.2.2.2 10.2.0.2 172.31.2.2 172.31.22.2 ip host P2R1 10.2.1.1 10.2.0.1 172.31.2.1 172.31.22.1 ! ip host P1R4 10.1.3.4 10.1.2.4 ip host P1R3 10.1.1.3 10.1.3.3 ip host P1R2 10.1.2.2 10.1.0.2 172.31.1.2 172.31.11.2 ip host P1R1 10.1.1.1 10.1.0.1 172.31.1.1 172.31.11.1 ! interface FastEthernet0/0 description Backbone LAN Connection ip address 10.254.0.1 255.255.255.0 ip pim sparse-dense-mode duplex half speed auto no shutdown ! interface Serial0/0/0 description Interface for Frame Relay Multipoint bandwidth 128 no ip address ip pim sparse-dense-mode encapsulation frame-relay no fair-queue cdp enable no frame-relay inverse-arp frame-relay lmi-type cisco no shutdown ! interface Serial0/0/0.1 multipoint description Frame Relay DLCI 111 and 112 for Pod 1 ip address 172.31.1.3 255.255.255.0 ip pim sparse-dense-mode ip rip send version 1 2 ip receive version 1 2 ip ospf network non-broadcast ip ospf priority 50 cdp enable frame-relay map ip 172.31.1.1 111 broadcast frame-relay map ip 172.31.1.2 112 broadcast ! interface Serial0/0/0.2 multipoint description Frame Relay DLCI 121 and 122 for Pod 2 ip address 172.31.2.3 255.255.255.0 ip pim sparse-dense-mode ip rip send version 1 2 ip rip receive version 1 2 ip ospf network non-broadcast ip ospf priority 50 cdp enable frame-relay map ip 172.31.2.1 121 broadcast frame-relay map ip 172.31.2.2 122 broadcast ! ! router eigrp 1 network 10.254.0.0 0.0.0.255 network 172.31.0.0 distribute-list 1 in no auto-summary no eigrp log-neighbor-changes ! router ospf 1 router-id 100.100.100.100 log-adjacency-changes redistribute connected metric 50 subnets network 172.31.0.0 0.0.255.255 area 0 neighbor 172.31.2.1 neighbor 172.31.2.2 neighbor 172.31.1.1 neighbor 172.31.1.2 ! router rip version 2 passive-interface FastEthernet0/0 network 10.0.0.0 network 172.31.0.0 distribute-list 1 in no auto-summary ! router bgp 64998 no synchronization bgp log-neighbor-changes network 10.254.0.0 mask 255.255.255.0 network 172.31.1.0 mask 255.255.255.0 network 172.31.2.0 mask 255.255.255.0 neighbor 10.254.0.2 remote-as 64999 neighbor 10.254.0.3 remote-as 64997 neighbor 172.31.1.1 remote-as 65001 neighbor 172.31.1.2 remote-as 65001 neighbor 172.31.2.1 remote-as 65002 neighbor 172.31.2.2 remote-as 65002 no auto-summary ! ip classless ip route 192.168.1.0 255.255.255.0 172.31.1.1 ip route 192.168.2.0 255.255.255.0 172.31.2.1 ip route 192.168.11.0 255.255.255.0 172.31.1.2 ip route 192.168.22.0 255.255.255.0 172.31.2.2 ! ip http server no ip http secure-server ! access-list 1 deny 0.0.0.0 access-list 1 permit any ! control-plane ! line con 0 exec-timeout 60 0 privilege level 15 logging synchronous line aux 0 line vty 0 4 exec-timeout 5 0 password cisco logging synchronous login ! ntp server 10.254.0.2 end copy run start
Example B-2 provides the text of the configuration file for the BBR2 router.
Example B-2. BBR2 Configuration
! !BBR2 configuration exercise configuration ! ! This file is designed to be copied and pasted into an erased router, at ! the # prompt. ! ! This configuration was tested with the c2800nm-advipservicesk9-mz.124-4.T1 IOS image ! conf t service timestamps debug datetime service timestamps log datetime no service password-encryption ! hostname BBR2 ! enable secret sanfran ! resource policy ! ip subnet-zero ! ip cef ! no ip domain lookup ip multicast-routing ! voice-card 0 no dspfarm ! ip host bbr1 10.254.0.1 172.31.1.3 172.31.2.3 ip host bbr2 10.254.0.2 172.31.11.4 172.31.22.4 ip host Frame_Switch 10.254.0.3 ip host tftp 10.254.0.254 ! ip host P2R4 10.2.3.4 10.2.2.4 ip host P2R3 10.2.1.3 10.2.3.3 ip host P2R2 10.2.2.2 10.2.0.2 172.31.2.2 172.31.22.2 ip host P2R1 10.2.1.1 10.2.0.1 172.31.2.1 172.31.22.1 ! ip host P1R4 10.1.3.4 10.1.2.4 ip host P1R3 10.1.1.3 10.1.3.3 ip host P1R2 10.1.2.2 10.1.0.2 172.31.1.2 172.31.11.2 ip host P1R1 10.1.1.1 10.1.0.1 172.31.1.1 172.31.11.1 ! interface FastEthernet0/0 description Backbone LAN Connection ip address 10.254.0.2 255.255.255.0 ip pim sparse-dense-mode duplex half speed auto no shutdown ! interface Serial0/0/0 description Interface for Frame Relay Multipoint bandwidth 128 no ip address ip pim sparse-dense-mode encapsulation frame-relay no fair-queue no frame-relay inverse-arp frame-relay lmi-type cisco no shutdown ! interface Serial0/0/0.1 multipoint description Frame Relay DLCI 211 and 212 for Pod 1 ip address 172.31.11.4 255.255.255.0 ip pim sparse-dense-mode ip ospf network point-to-multipoint cdp enable frame-relay map ip 172.31.11.1 211 broadcast frame-relay map ip 172.31.11.2 212 broadcast no frame-relay inverse-arp ! interface Serial0/0/0.2 multipoint description Frame Relay DLCI 221 and 222 for Pod 2 ip address 172.31.22.4 255.255.255.0 ip pim sparse-dense-mode ip ospf network point-to-multipoint cdp enable frame-relay map ip 172.31.22.1 221 broadcast frame-relay map ip 172.31.22.2 222 broadcast ! ! router eigrp 1 network 10.0.0.0 distribute-list 1 in no auto-summary no eigrp log-neighbor-changes ! router ospf 1 router-id 200.200.200.200 log-adjacency-changes redistribute connected metric 50 subnets network 172.31.0.0 0.0.255.255 area 0 ! router bgp 64999 no synchronization bgp log-neighbor-changes network 10.254.0.0 mask 255.255.255.0 network 172.31.11.0 mask 255.255.255.0 network 172.31.22.0 mask 255.255.255.0 neighbor 10.254.0.1 remote-as 64998 neighbor 10.254.0.3 remote-as 64997 neighbor 172.31.11.1 remote-as 65001 neighbor 172.31.11.2 remote-as 65001 neighbor 172.31.22.1 remote-as 65002 neighbor 172.31.22.2 remote-as 65002 no auto-summary ! ip classless ! ip http server no ip http secure-server ! access-list 1 deny 0.0.0.0 access-list 1 permit any ! control-plane ! line con 0 exec-timeout 60 0 privilege level 15 logging synchronous line aux 0 line vty 0 4 exec-timeout 5 0 password cisco logging synchronous login ! ntp master 2 ! end copy run start
Example B-3 provides the text of the configuration file for the Frame_Switch Frame Relay backbone router.
Example B-3. Frame_Switch Configuration
! !Frame_Switch configuration exercise configuration ! ! This file is designed to be copied and pasted into an erased router, at ! the # prompt. The configuration is based on 3620 Router with Ethernet ! in slot 0 and an 8-port Serial Module in slot 1. ! ! This configuration was tested with the c3620-js-mz.121-15 IOS image ! conf t service timestamps debug uptime service timestamps log uptime service password-encryption ! hostname Frame_Switch ! enable secret sanfran ! ip subnet-zero ip cef ! no ip domain-lookup ! ip host bbr1 10.254.0.1 ip host bbr2 10.254.0.2 ip host Frame_Switch 10.254.0.3 ip host tftp 10.254.0.254 ! frame-relay switching ! interface Loopback0 ip address 10.97.97.97 255.255.255.0 ! interface Ethernet0/0 description Backbone LAN Connection ip address 10.254.0.3 255.255.255.0 no shutdown ! interface Serial1/0 description to P1R1 Serial 0/0/0 no ip address encapsulation frame-relay clockrate 115200 frame-relay intf-type dce frame-relay route 111 interface Serial1/6 111 frame-relay route 122 interface Serial1/1 221 frame-relay route 211 interface Serial1/7 211 no shutdown ! interface Serial1/1 description to P1R2 Serial 0/0/0 no ip address encapsulation frame-relay clockrate 115200 frame-relay intf-type dce frame-relay route 112 interface Serial1/6 112 frame-relay route 212 interface Serial1/7 212 frame-relay route 221 interface Serial1/0 122 no shutdown ! interface Serial1/2 description to P2R1 Serial 0/0/0 no ip address encapsulation frame-relay clockrate 115200 frame-relay intf-type dce frame-relay route 121 interface Serial1/6 121 frame-relay route 122 interface Serial1/3 221 frame-relay route 221 interface Serial1/7 221 no shutdown ! interface Serial1/3 description to P2R2 Serial 0/0/0 no ip address encapsulation frame-relay clockrate 115200 frame-relay intf-type dce frame-relay route 122 interface Serial1/6 122 frame-relay route 221 interface Serial1/2 122 frame-relay route 222 interface Serial1/7 222 no shutdown ! interface Serial 1/4 no ip address shutdown ! interface Serial 1/5 no ip address shutdown ! interface Serial 1/6 description to BBR1 Serial 0/0/0 no ip address encapsulation frame-relay clockrate 115200 frame-relay intf-type dce frame-relay route 111 interface Serial1/0 111 frame-relay route 112 interface Serial1/1 112 frame-relay route 121 interface Serial1/2 121 frame-relay route 122 interface Serial1/3 122 no shutdown ! interface Serial 1/7 description to BBR2 Serial 0/0/0 no ip address encapsulation frame-relay clockrate 115200 frame-relay intf-type dce frame-relay route 211 interface Serial1/0 211 frame-relay route 212 interface Serial1/1 212 frame-relay route 221 interface Serial1/2 221 frame-relay route 222 interface Serial1/3 222 no shutdown ! router eigrp 1 network 10.0.0.0 auto-summary no eigrp log-neighbor-changes ! router bgp 64997 no synchronization bgp log-neighbor-changes network 10.97.97.0 mask 255.255.255.0 neighbor 10.254.0.1 remote-as 64998 neighbor 10.254.0.2 remote-as 64999 no auto-summary ! ip classless ! ip http server ! control-plane ! line con 0 exec-timeout 60 0 privilege level 15 logging synchronous line aux 0 line vty 0 4 exec-timeout 5 0 password cisco logging synchronous login ! ntp server 10.254.0.2 ! end copy run start