What Happens As Your Router Boots Up The "Power-On Self-Test" checks the Router Hardware. This includes the CPU (Central Processor Unit), memory, and interfaces. The "Bootstrap Program", which is stored in ROM, runs itself The "Bootfield" is read to find out the proper Operating System source. The "Operating System Image" is loaded into RAM. (Random Access Memory) The "Configuration File" saved in NVRAM is loaded into the RAM. The Configuration File is then executed one line at a time. If no "Configuration File" is found in NVRAM, the Cisco IOS will offer you the chance to use the "Initial Configuration Dialog". This is a set of Questions for you to answer to do a basic configuration. Since in our theoretical New Router there is no NVRAM configuration This "Setup Dialog" will be one of the first things we see. You should also start to see the following on your VT100 Terminal Program: System Bootstrap, Version 12.0(1), SOFTWARE Copyright (c) 1986-2001 by Cisco Systems Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause... if you are viewing this at Home please put your hands on your head an wait for the FBI to arrive. (and other such legal fineprint as necessary!) After reading this legal information very carefully, a brandnew Router should enter automatically into what is called the "System Configuration Dialog". Also called the "Setup Dialog". It should ask you "Would you like to enter the initial configuration dialog? [yes|no]:" But we are going to type in "NO" when it asks us if we want to use the "System Configuration Dialog", because putting in the commands ourselves, will let us learn exactly how to properly configure a Router. Besides if you are a Cisco person, you like doing things the hard way! As they always say, "The more difficult and challenging, the better!"

Simple Operating Instructions CTRL-A goes to the "Beginning" of the Line. CTRL-E goes to the "End" of the Line. CTRL-B go "Back One Character". (can also use LEFT Arrow key) CTRL-F go "Forward One Character". (can also use RIGHT Arrow key) ESCAPE-B go "Backward to the Beginning of the Next Word". ESCAPE-F go "Forward to the Beginning of the Next Word". Note that using the ARROW Keys is limited to those using a VT-100 Terminal Emulation.

Fancy Editing Tricks If the end of a line goes too long, it will not automatically wrap to the next one. Instead the Cisco IOS command shell gives you a dollar sign $. This indicates that you are an over-achiever and have typed too much, at least too much to be shown on the screen. Your line would now look like this: Router#$ this is a way too long line that is full of sound and fury Note that the $ goes after the Router Prompt. If you keep typing is will shift over as you type, hiding more of the beginning of the sentence. Router#$long line that is full of sound and fury, signifying nothing! You can get back to the beginning of your Novel by typing CTRL-A Router# For Demo Purposes Only this is a long line that is full of $ If you want to you can turn off these Advance Editing Tools by simplying typing in Terminal No Editing at the prompt. Since this would be a silly thing to do, please turn them back on by typing in the two words Terminal Editing.

Command History! Now then, you just typed in a Real Long Command (RLC) and you realize that you made a mistake in one word and want a second chance to do it right again. Well, the Cisco IOS makes this Real Easy! The Router keeps the last 10 commands you issued in its HISTORY, which is a special memory Buffer which holds the "Command History". (note here that a "Buffer" is a memory space for storing things...) If you are using the VT-100 Emulator we talked about before, simply do the following. Press the UP Arrow key to go back to the previous command. Press the DOWN Arrow key to go back to the previous command. If you are a poor unfortunate without VT-100 you can use these instead: CTRL-P takes you to the "Previous" command. CTRL-N takes you to the "Next" commands. Putting the Command show history in at the prompt gives you the list of the last 10 commands you have typed in. Router# show history Command One Command Two Command Three Command Four Command Five Command Sixx - (with a mistake!) Command Six - (fixed now) Command Eight - "There is No Command 7!" Command Nine Command Ten You can increase the size of your HISTORY buffer by using the command: Terminal History Size Router# Terminal History Size 99 The above command would give you 99 commands to play with! Hope you noticed the SHOW part of the command above, we will be using a lot more of SHOW commands to look at various things!

Using HELP to make a Banner Telling you how "Context Sensitive Help" works is nice, but a simple example of how to use it should make it clearer. A Banner is simply a message that pops up on the screen it is related to the old UNIX "Message of the Day" or MOTD. In order to set a Banner you have to be in Router Config mode. Let's start out at the User Exec prompt and look for "Configure" (remember that User Exec is limited and has No Privileges!) Router>? (here is where you type in the Question Mark) Exec commands: access-enable clear connect disconnect disable enable exit help lat lock login logout Create a temporary Access-List entry Reset functions Open a terminal connection Disconnect an existing network connection Turn off privileged commands Turn on privileged commands Exit from the EXEC Description of the interactive help system Open a lat connection Lock the terminal Log in as a particular user Exit from the EXEC --more-- Here you will note two things: 1. There is no "Configure" command listed for User Exec Mode (Like we said, you can't do much as a poor ordinary User!) 2. There is an "Enable" command to get you into Enable Mode. (Privileged!) 3. The list ends up with the word "--more--" Which simply means that there are more commands not yet listed. If you press the "Return" key you'll get another screenful of commands, but since they are in alphabetical order, you already know "Configure" is not an available command. Anyway, let's take the hint and get into Enable Mode. Router> (type in the command enable) Router# (note again that the Prompt sign changes to a # symbol) Now let's see what new and different commands are available! Router# Type in a ? Router#? Exec commands: access-enable access-template bfe clear clock configure connect copy debug disable disconnect enable erase exit help Create a temporary Access-List entry Create a temporary Access-List entry For manual emergency modem setting Reset functions Manage the system clock Enter configuration mode Open a terminal connection Copy configuration or image date Debugging functions (see also "undebug") Turn off privileged commands Disconnect an existing network connection Turn on privileged commands Erase flash or configuration memory Exit from the EXEC Description of the interactive help system --more-- Notice that in the Priveleged (Enable) Mode you have different commands. From here it is possible to enter the Global command configure and begin to actually change the configuration of your router! Just to show more of the Help functions, how about we type in: configure (space) ? (the empty space is Very Important!) Router# (type in configure ? here) This will give us a list of the "Options" for the configure command. Router#configure ? Memory Network Terminal This gives us the 3 choices of places to load a configuration from. Mostly we've just been using the Terminal, since we are doing setup, but we'll later show you how to use the Network or Memory to load Configs. In order to properly configure your Router's various Elements it is good to get familiar with what they are and how you can show them. So next let's take a closer look at our Router's Elements using the all-important "Show" commands.

Using The SHOW Commands Most SHOW command can be viewed from the regular USER Exec mode. Some SHOW commands can only be viewed from the Priviledged Exec (Enable) mode. None of the SHOW commands can be used from the (config) mode. This will just give you an error and you will feel very silly! If you've been busily configuring stuff like Interfaces and Protocols, and forget to change back to the plain old Router# or Router prompt using a Show command will not work. All you get is an error message. Router# show _______ (right!) Router(config-if)# show _______ (wrong!) If you type in the command Show, a space, and then a Question Mark, at the proper Enable Mode "Router#" prompt, the Help function will give you a long list of the multitudinous show commands. Router#show ? show access-expression show access-list show apple interface show apple route show appletalk show atm show bridge show cam show cam dynamic show cdp neighbors show config And so on going down through the entire alphabet...! Luckily, you do not need to memorize all these right away for the tests. There are, however, several show commands that are very useful for taking a closer look at what your router has in it and what it's doing.

Show Version The show version command gives you information on what version of the Cisco Internetwork Operating System your router is using. It also gives you lots of other basic information on things such as "how long the router has been up", "how the system was started", "what processor" and "how much memory" and "where the system image file was loaded from." Show version will also show you what interfaces the router has. router# type in show version (you can also type in sh ver for short) Router> (type in show version router>show version Cisco Internetwork Operating System Software IOS (tm) 3000 software (IGS-I-L, Version 11.1(11) RELEASE SOFTWARE (fc1) Copyright (c) 1986-1999 by Cisco Systems, Inc. Compiled Tue 24-Jun-97 12:20 by jaturner Image text-base: 0x0301E644, data-base 0x00001000 ROM: System Bootstrap, Version 11.0(10c), SOFTWARE ROM: 3000 Bootstrap Software (IGS-BOOT-R), Version 11.0(10c) RELEASE SOFTWARE (fc1) Router uptime is 12 minutes System restarted by power-on System image file is "flash:igs-i-l.110-16", booted via flash cisco 2500 (68030) processor (revision N) with 2048K/2048K bytes of memory. Processor board ID 06267777, with hardware revision 00000000 Bridging software X.25 software, Version 2.0, NET2,, BFE and GOSIP compliant. 1 Ethernet/IEEE 802.3 interface. 2 Serial network interfaces. 32K bytes of non-volatile configuration memory. 8192K bytes of rocessor board System flash (Read ONLY) Configuration register is 0x2102

Show Memory The show memory command shows what memory is allocated by the management system for which purposes. Router> (type in show memory Router>show memory There are two Memory Charts that get shown. 1. A Summary Router>:show memory Head Total(b) Used(b) Free(b) Lowest(b) Largest(b) Processor EA90C 5326580 2056220 3270360 3270360 3231192 I/O 600000 2097152 465264 1631888 1579032 1631720 2. A Detailed Block by Block memory chart. Allocator PC Summary for: Processor pc=0x031FDE54, size=000963416, count=000056, name=List Elements pc=0x031D8060, size=000462508, count=000312, name=*Packet Data* pc=0x03217BAE, size=000287992, count=000068, name=Interrupt Stack pc=0x031D8028, size=000178496, count=000312, name=*Packet Header* pc=0x031DCDEC, size=000115040, count=000008, name=Fair Queueing pc=0x031C2BD2, size=000049196, count=000001, name=Exec pc=0x031DDBA8, size=000044660, count=000011, name=*Hardware IDB* pc=0x031957E4, size=000040840, count=000010, name=TTY data pc=0x03214150, size=000033516, count=000063, name=Process pc=0x0322E6F4, size=000032808, count=000001, name=Cfg EEPROM Copy pc=0x031DDBBE, size=000025124, count=000011, name=*Software IDB* pc=0x034A829A, size=000014468, count=000001, name=Init pc=0x034A81F4, size=000014464, count=000001, name=Init pc=0x03AA68C2, size=000013644, count=000001, name=Init pc=0x03A772B6, size=000013644, count=000028, name=ATMSIG-SHOW pc=0x031A2D10, size=000013512, count=000197, name=Parser 01:13:41: %SYS-3-CPUHOG: Task ran for 2008 msec (19/19), process = Exec, PC = 31 7A068. -Traceback= 320F2A6 317A070 318F4A4 31904A2 318F54C 31C2EBE 31C3028 31C3332 31A18F0 31B605C Linkage pc=0x031368E0, size=000012044, count=000001, name=Init pc=0x0320BCD8, size=000012032, count=000084, name=Watched Boolean pc=0x032B17D0, size=000011420, count=000001, name=DHCPD Message Workspace pc=0x0320BEE8, size=000011040, count=000064, name=Process Events --More-- As you can see the SHOW MEMORY command gives you lots of detailed information about the memory contained within your router.

Show Processes A Process is part of a Program, or if it is small, it can be the entire Program. It's sort of like having a troupe of Jugglers, each item they are tossing up in the air is one Process. As long as they keep them all going, everything is fine. If not you can use SHOW PROCESSES to do a little troubleshooting! The show processes command shows you all the active processes, in the form of a chart containing the following information in Columns: PID - The ID number of each Process. Q - The Queue priority TY - This is the Status of the Process PC - Program Counter. Runtime - The amount of CPU time in milliseconds used by the Process Invoked - This is the amount of time the Process has been invoked. uSecs - The CPU time in milliseconds for each Process invocation. Stacks - This shows both the "low watermark" / "total stack space" in bytes. TTY - Shows you which terminal controls the process. Process - Finally, this actually gives you the Name of the process! Router> (type in show processes Router>show processes CPU utilization for five seconds: 7%/7%; one minute: 9%; five minutes: 12% PID QTy PC Runtime (ms) Invoked uSecs Stacks TTY Process 1 Csp 32134FE 8 872 9 736/1000 0 Load Meter 2 M* 0 3632 82 44292 2960/4000 0 Exec 3 Lst 3203DC6 14300 960 14895 3736/4000 0 Check heaps 4 Cwe 3209FB6 0 1 0 3724/4000 0 Pool Manager 5 Mst 318E706 0 2 0 3700/4000 0 Timers 6 Mwe 311F992 8 2 4000 3696/4000 0 Serial Backgroun 7 Lwe 323C858 340 78 4358 3684/4000 0 ARP Input 8 Mwe 33877A6 0 3 0 3704/4000 0 DDR Timers 9 Mwe 339B8CA 0 2 0 5712/6000 0 Dialer event 10 Lwe 34BE0AC 36 2 18000 3684/4000 0 Entity MIB API 11 Mwe 3125CA2 0 1 0 3732/4000 0 SERIAL A'detect 12 Cwe 320D770 0 1 0 3740/4000 0 Critical Bkgnd 13 Mwe 31E55AA 696 547 1272 4756/6000 0 Net Background 14 Lwe 31857B2 16 7 2285 5604/6000 0 Logger 15 Msp 319E1D4 172 4347 39 3568/4000 0 TTY Background 16 Msp 31E4EB6 3084 4415 698 3736/4000 0 Per-Second Jobs 17 Msi 3235488 40 4351 9 3724/4000 0 Partition Check 18 Hwe 31E5014 0 1 0 3712/4000 0 Net Input 19 Csp 31EC442 68 873 77 3728/4000 0 Compute load avg 20 Msp 31E4EE4 4740 75 63200 3776/4000 0 Per-minute Jobs 21 Mwe 309D71E 0 1 0 3824/4000 0 SYNCCD2430 Helpe --More--

SHOW STACKS A Stack is basically a portion of the Memory that is used to monitor the internal operations of a program. Stacks are usually ordered in a "Last In, First Out" (LIFO) data structure. The SHOW STACKS command looks at the manner in which the Cisco Router's Processes and Interupts utilize these stacks. If there was a Reboot caused by a crash, then using SHOW STACKS will reveal the reason for that reboot. Router> (type in show stacks Router>show stacks Minimum process stacks: Free/Size Name 2704/4000 Setup 3256/4000 Autoinstall 2776/4000 DNS Snoop 2680/4000 Init 1720/2000 LAPB Timer 5400/6000 BootP Resolver 3460/4000 RADIUS INITCONFIG 4632/5000 DHCP Client 3524/4000 Exec Interrupt level stacks: Level Called Unused/Size Name 1 0 3000/3000 CL-CD2430 transmit interrupts 2 0 3000/3000 CL-CD2430 receive interrupts 3 33 2772/3000 Serial interface state change interrupt 4 23 2872/3000 Network interfaces 5 10771 2896/3000 Console Uart

SHOW BUFFERS A Buffer is portion of Memory set aside for data to wait around in while waiting to catch the next bus out. Buffers are sort of like Bus Stops, but some are Bigger (like a Bus Station), and some of them are very large, like an Airport! SHOW BUFFERS lets you see the size of the Small, Middle, Big, Very Big, Large, and Huge buffers. Also gives statistics on their usage. Kind of like Baseball scores. Router> (type in show buffers Router>show buffers Buffer elements: 500 in free list (500 max allowed) 128 hits, 0 misses, 0 created Public buffer pools: Small buffers, 104 bytes (total 56, permanent 50): 54 in free list (20 min, 150 max allowed) 87 hits, 2 misses, 0 trims, 6 created 0 failures (0 no memory) Middle buffers, 600 bytes (total 28, permanent 25): 28 in free list (10 min, 150 max allowed) 76 hits, 1 misses, 0 trims, 3 created 0 failures (0 no memory) Big buffers, 1524 bytes (total 50, permanent 50): 47 in free list (5 min, 150 max allowed) 19 hits, 0 misses, 0 trims, 0 created 0 failures (0 no memory) VeryBig buffers, 4520 bytes (total 10, permanent 10): 10 in free list (0 min, 100 max allowed) 0 hits, 0 misses, 0 trims, 0 created 0 failures (0 no memory) Large buffers, 5024 bytes (total 0, permanent 0): 0 in free list (0 min, 10 max allowed) 0 hits, 0 misses, 0 trims, 0 created 0 failures (0 no memory) Huge buffers, 18024 bytes (total 0, permanent 0) : 0 in free list (0 min, 4 max allowed) 0 hits, 0 misses, 0 trims, 0 created 0 failures (0 no memory) Interface buffer pools: Ethernet0 buffers, 1524 bytes (total 32, permanent 32): 8 in free list (0 min, 32 max allowed) 24 hits, 0 fallbacks 8 max cache size, 8 in cache BRI0 buffers, 1524 bytes (total 4, permanent 4): 3 in free list (0 min, 4 max allowed) 3 hits, 0 fallbacks 1 max cache size, 1 in cache BRI0:1 buffers, 1524 bytes (total 16, permanent 16): 12 in free list (0 min, 16 max allowed) 12 hits, 0 fallback 4 max cache size, 4 in cache BRI0:2 buffers, 1524 bytes (total 16, permanent 16): 12 in free list (0 min, 16 max allowed) 12 hits, 0 fallbacks 4 max cache size, 4 in cache Serial0 buffers, 1524 bytes (total 32, permanent 32): 7 in free list (0 min, 32 max allowed) 25 hits, 0 fallbacks 8 max cache size, 8 in cache Serial1 buffers, 1524 bytes (total 32, permanent 32): 7 in free list (0 min, 32 max allowed) 25 hits, 0 fallbacks 8 max cache size, 8 in cache Serial2 buffers, 1524 bytes (total 8, permanent 8) : 6 in free list (0 min, 8 max allowed) 6 hits, 0 fallbacks 0 max cache size, 0 in cache Serial3 buffers, 1524 bytes (total 8, permanent 8): 6 in free list (0 min, 8 max allowed) 6 hits, 0 fallbacks 0 max cache size, 0 in cache CD2430 I/O buffers, 1524 bytes (total 20, permanent 20): 10 in free list (0 min, 20 max allowed) 10 hits, 0 fallbacks

SHOW FLASH We'd already discussed what Flash Memory is early, but a reminder can't hurt. Flash Memory An Electronically Erasable and Re-Programmable memory chip. The "Flash" contains the full Operating System, or "Image". This allows you to Upgrade the OS without removing chips. SHOW FLASH tells you how Big the Flash Memory is and what it is doing. Again lots of good statistics to use in troubleshooting your Router. Router> (type in show flash Router>show flash System flash directory: File Length Name/status 1 11780820 12-04T.bin [11780884 bytes used, 4996332 available, 16777216 total] 16384K bytes of processor board System flash (Read ONLY)

SHOW INTERFACES SHOW INTERFACES is like the Swiss Army knife of troubleshooting. It gives you information on all the Interfaces in your Router. Since the Interfaces are where all the real work takes place being able to see what they are doing is very helpful. Router> (type in show interfaces Router>show interfaces BRI0 is administratively down, line protocol is down Hardware is BRI MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 5 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions BRI0:1 is administratively down, line protocol is down Hardware is BRI MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, Encapsulation HDLC, loopback not set reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 5 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions BRI0:2 is administratively down, line protocol is down Hardware is BRI MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 5 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions Ethernet0 is administratively down, line protocol is down Hardware is Lance, address is 0010.7b3a.dea6 (bia 0010.7b3a.dea6) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 252/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 01:17:16, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 14 packets output, 840 bytes, 0 underruns 14 output errors, 0 collisions, 1 interface resets 0 babbles, 0 late collision, 0 deferred 14 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out Serial0 is administratively down, line protocol is down Hardware is HD64570 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 never, output 01:17:18, output hang never Last clearing of "show interface" counters 01:17:18 Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 5 packets output, 853 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=down DSR=down DTR=down RTS=down CTS=down Serial1 is administratively down, line protocol is down Hardware is HD64570 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 never, output 01:17:50, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/2/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 6 packets output, 132 bytes, 0 underruns 0 output errors, 0 collisions, 3 interface resets 0 output buffer failures, 0 output buffers swapped out 23 carrier transitions DCD=down DSR=down DTR=down RTS=down CTS=down Serial2 is administratively down, line protocol is down Hardware is CD2430 in sync mode MTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 6 packets output, 1992 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=down DSR=down DTR=down RTS=down CTS=down Serial3 is administratively down, line protocol is down Hardware is CD2430 in sync mode MTU 1500 bytes, BW 115 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0 (size/max/drops); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 6 packets output, 1992 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions DCD=down DSR=down DTR=down RTS=down CTS=down

SHOW PROTOCOLS A Protocol is an agreed-upon method of speaking to others. Sort of like having a conference call and all of us agreeing, "Let's all speak Swahili..." SHOW PROTOCOLS lets you know if everyone is speaking Swahili properly. If they are not, then the Router will tell you, "Line Protocol is down. Even if the Interface is UP, if the Line Protocol isn't working, nothing works. All of our Interfaces will be listed as Administratively Down since we have not yet turned any of them on. In fact, since we are only doing the basic Setup of one Router in this tutorial, we don't actually have anyone else to talk Swahili with, do we? Router> (type in show protocols Router>show protocols Global values: Internet Protocol routing is enabled BRI0 is administratively down, line protocol is down BRI0:1 is administratively down, line protocol is down BRI0:2 is administratively down, line protocol is down Ethernet0 is administratively down, line protocol is down Serial0 is administratively down, line protocol is down Serial1 is administratively down, line protocol is down Serial2 is administratively down, line protocol is down Serial3 is administratively down, line protocol is down

SUMMARY As you can see, the SHOW commands give you an inside view of your router. There are many, many show commands, and you will get to know most of them!

Protocols This next section of the Systems Configuration Dialog is for Protocols. Protocols are simply things we agree upon for communicating stuff. Like when the Phone rings, you pick it up and say "Hello". That is part of a Protocol. Then the person who called you says "Hello" and you start talking. Anyway, please configure the following Protocols: First you will be configuring the Router to use the Simple Network Management Protocol. (which is anything but simple but does help Manage Networks) Configure SNMP Network Management? [yes]: (press return) Community String [Public]: (press return again) Now you get asked if you want to use the OSI Connectionless Network Service. (trust us, you do not need this protocol right now) Configure CLNS? [NO]: (just say No to CLNS!) Next we pretend you are a Mac fanatic with a huge Multi-Zone Network! Configure AppleTalk? [no]: (write in "no" here or press RETURN) Configure IPX? [no]: (write in "no" here or press RETURN) You can also safely say "NO" to Banyan Vines, Xerox XNS, and Digital' DECnet. They are still being used out there somewhere... but not by you, not today! Configure Vines? [no]: Configure XNS? [no]: Configure DECnet? [no]: The next Question asks if you want to configure Bridging. Now this is only Transparent Bridging, which you don't need right now, so go ahead and say "No". Configure Bridging? [no]: (write in "no" here or press RETURN) Now we get into the main Protocol for the whole Internet, which of course is named the "Internet Protocol" or "IP" for short. Configure IP? [yes]: (say Yes to IP please!) Now it asks if you to want to use the Interior Gateway Routing Protocol This Protocol does IP Routing for you, but you don't want it Now, okay? Configure IGRP? [yes]: (write in "No" please) You don't want the Apollo Routing Protocol either, unless you're on the Moon? Configure Apollo? [no]: (nope - don't want this...)

Interface Configuration Well, that's enough for the Global Configuration stuff for now. We'll be moving on to the even more complicated Interface junk. If you remember, an Interface is something that you plug into. Without these there is no connection to anything and you just spent a couple thousand dollars on a Router for nothing. You will notice that most of your Configurations you'll be doing start out with Global Configuration commands And then go on to do some Interface Configuration commands Personally I think this is a plot by evil Space Aliens... So you thought you were almost finished, eh? Systems Configuration Dialog - Part 2 Revenge of the Interfaces! Okay, what you will actually see next in the Dialog is: Configuring Interface Parameters: Configuring Interface Ethernet0: Cisco Routers come with a number of different Interfaces. One of them is, of course, the one marked Console that you attached your computer to. The one mentioned above, Ethernet0, is your Interface that goes to your Ethernet "Local Area Network". Is this Interface in use? [no] (write in "Yes") Saying "Yes" turns on the Ethernet0 Interface. This is a good thing! Configure IP Address on this Interface? [no} Answer "Yes" or you won't get very far on the network. Now you need to pick out an IP Address! This is my favorite part in all the Computer textbooks, You know, the part where they tell you to ask your System Administrator what numbers you should put in for an IP Address... which is fine as long as YOU are not the Sys Admin, right? Well, since we are setting this up for a home-use test laboratory, we can use one of the 3 Networks assigned for "Private" use to steal our Internet Protocol (IP) Addresses from. Let's pick the Class A address, "10.0.0.1" to use, cause it's easy. Put it in when the Systems Configuration Dialog asks you: IP Address for this Interface: Put in "10.0.0.1" here. IP Addresses, Subnet Masks, & Cisco Confusions! Then it will ask for the Number of Bits in the Subnet "Field", which basically tells the Router which part of the 10.0.0.1 is the Subnet Part. Warning! This is going to get a Bit confusing! (yes, Pun intended, sorry) Since this is a Classful Class A address the default is 8 bits. So the Subnet Mask looks like 1111 1111 . 0000 0000 . 0000 0000 . 0000 0000 (I put space between each set of 4 numbers cause it's easier to read) Which for reasons of convenience is written in Decimal as 255.0.0.0 It is actually a lot easier to see What is really going on in Binary Bits, since anything that is a One gets counted as a Network address, and anything that is a Zero is just a humble Host address for a lowly computer. Of course Cisco doesn't count the Class A Network bits, so the correct "Bits in Subnet Field" they want is "Zero". (0) Basically Cisco doesn't usually count Subnet Mask bits unless they are above and beyond the call of Classful IP addressing. Even when it'd be simpler just to look at the number of 1's and go, "Hey, there's 8 ones in that Subnet Mask!" We'll have to go over all this IP addressing stuff later over a good Rootbeer... Number of Bits in Subnet Field?: (try "0") The Router now spits out the following Interesting Info: Class A Network is 10.0.0.0, 0 Subnet Bits; Mask is 255.0.0.0 I suppose right now you are breathing a sigh of relief, expecting that the worst is over and it's all downhill sailing from here. Well, in this case you are correct, since we are not going to try IPX/SPX, Appletalk, Banyan Vines, Decnet, or any of the other interested protocols yet. Actually using SETUP is the easy way to get a Router up and running, but as we mentioned earlier, doing things the easy way means that you don't have to learn as much. And for the Cisco tests, you had better take the time to learn everything!

*