| Lab Activity 9.3.1: Basic router configuration Step 1: Physical Connections. Connect all of the interfaces including: Console: Connect your PC/terminal to the console port via HyperTerminal (9600-8-N-1-no flow) Ethernet: Connect Ethernet ports to a hub or a switch using a straight-through cable. Use a cross-over cable if going directly between Ethernet ports on two routers. Serial: If going directly between two routers, don't forget to connect one port via the DTE cable and the other via the DCE cable. Step 2: Boot up the router. You may use the setup mode (setup dialogue) but this is to help you with configuring the router using the Cisco IOS commands. The setup mode will only allow you to configure the router with the basic features and not with any advanced features. Step 3: Host Name and Passwords. It is a good idea to begin your configuration with the hostname and passwords. This will remind you what router you are configuring and it is also a good idea to add the security of passwords right away. Router(config)# hostname LabC LabC(config)# enable secret class LabC (config)# line vty 0 4 {If you are running EFS, you may increase the number of telnet sessions to more than 5.} LabC (config-line)# login LabC (config-line)# password cisco LabC (config)# line con 0 LabC (config-line)# login LabC (config-line)# password cisco Step 4: Adding IP Addresses. Next lets add the IP addresses, as this is a basic function of configuring routers. Below is an example of configuring both an Ethernet and Serial interface. Don't forget to use the proper subnet mask! For Serial interface with the DCE cable you will need to also add the clocking with the clockrate command. LabC (config)# interface ethernet 0 LabC (config-if)# ip address 223.8.151.1 255.255.255.0 LabC (config-if)# description LAN Network LabC (config-if)# no shutdown LabC (config)# interface serial 0 LabC (config-if)# ip address 204.204.7.1 255.255.255.0 LabC (config-if)# clock rate 56000 {DCE interface only} LabC (config-if)# no shutdown LabC (config-if)# description Network to Lab D LabC (config)# interface serial 1 LabC (config-if)# ip address 199.6.13.2 255.255.255.0 LabC (config-if)# no shutdown LabC (config-if)# description Network to Lab B Step 5a: Adding Dynamic Routing: RIP. If this router will be participating in a dynamic routing protocol like RIP or IGRP, you will need to enable the routing protocol along with those directly connected networks that will be participating. Only use the classful network address, not the subnet address of the network! LabC (config)# router rip LabC (config-router)# network 199.6.13.0 {NOT Subnet Address} LabC (config-router)# network 204.204.7.0 {NOT Subnet Address} Step 5b: Adding Dynamic Routing: IGRP. IGRP uses an autonomous system number or process id. This number must be the same on all routers sharing the same IGRP routing updates. LabC (config)# router igrp 10 {10 = autonomous-system a.k.a. process-id} LabC (config-router)# network 199.6.13.0 {NOT Subnet Address} LabC (config-router)# network 204.204.7.0 {NOT Subnet Address} Step 6: Adding Default Routes. Good candidates for default routes are routers which are known as the boundary router. This is a router which is normally part of a stub network. Inside the stub network, the routers may be participating in a dynamic routing protocol like RIP, but only a static default route is needed to connect the stub network to the Internet. Static routes, including default routes, are propagated with dynamic routing updates. Here are two examples. Either one will work. LabA (config)# ip route 0.0.0.0 0.0.0.0 201.100.11.2 {Adding a default route using a static route.} LabA (config)# ip default-network 201.100.11.0 {Adding a default route using a the default-network command..} Step 7: Adding Static Routes. A static route can be used for various reasons. One reason may be for a router to connect to a stub network. LabB (config)# ip route 205.7.5.0 255.255.255.0 201.100.11.1 LabB (config)# ip route 192.5.5.0 255.255.255.0 201.100.11.1 Step 8: Testing and Monitoring. At this point it is a good idea to start testing your network using various commands. LabC# show ip route LabC # show ip interface brief LabC # show controller s 0 {Shows whether or not the serial cable is DCE or DTE.} LabC # ping ip-address LabC # trace ip-address LabC # debug ip rip {Remember to turn debug off when done, no debug all} LabC # terminal monitor {If using debug from a telnet session, otherwise debug output will go to the console. Caution: This will cause the debug output to go to all telnet sessions on this router.}} LabC # terminal no monitor {To turn off monitoring during a telnet session.} LabC # show cdp neighbors LabC # show ip protocols LabC # show version LabC # show flash Step 9: Finishing up. Once everything is working you may wish to add some commands to make your work easier. LabC (config)# ip host LabB 199.6.13.1 {Mapping names and IP addresses.) LabC (config)# ip name-server 223.8.151.10 {Adding a name server.} LabC (config)# no ip domain-lookup {When there is no domain server.} LabC (config)# banner motd # LabC Router, Authorized Access Only! # LabC (config-router)# passive-interface e 0 {When you do no want to advertise routing tables out of a specific interface.) And don't forget to… LabC # show running-config LabC # copy running-config startup-config Miscellaneous LabC # ? {This command can be used by itself or following at the end of any partial command line.} LabC > enable LabC # disable LabC # configure terminal LabC (config)# exit LabC (config-if)# control-z LabC # clock set 15:10:30 27 May 2000 Editing Commands Control-A: Moves to the beginning of the command line. Control-E: Moves to the end of the command line. Esc-B: Moves back one word. Control F: Moves forward one character. Control-B: Move back one character. Esc F: Moves forward one word. Command History Commands Control P or up arrow key: Recalls last (previous command). Control N or down arrow key: Recalls most recent command Tab key: completes the entry. LabC # show history LabC # terminal history LabC # terminal editing LabC # no terminal editing