Thursday, June 21, 2012

CDP Basic

CDP is the Cisco Discovery Protocol and is enabled on all router and switch interfaces by default. The switch or router sends a CDP packet out of each interface every 60 seconds, any connected device records the delivery of these packets into a CDP table for a holdtime period of 180 seconds. If after 180 seconds the device has not received any more CDP packets on that interface it removes the entry from the table. CDP can be disabled entirely or on any individual interface.


I begin by connecting to my switch and I check the CDP settings.

switch1#sh cdp
Global CDP information:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is enabled


From the output I can see the CDP time settings and the version. Next I look at the connected devices.

switch1#sh 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
switch2.lab.localFas 0/1 160 S I WS-C2950-2Fas 0/1
switch2.lab.localFas 0/24 160 S I WS-C2950-2Fas 0/24


Here I can see that I have 2 ports (1 & 24) connected to switch2 (also using ports 1 & 24). I can also see that switch2 is a Catalyst 2950.

This is a great summary but for my diagram I could do with knowing the IP address of switch2.


switch1#sh cdp entry * 
-------------------------
Device ID: switch2.lab.local
Entry address(es):
IP address: 10.0.1.211
Platform: cisco WS-C2950-24, Capabilities: Switch IGMP
Interface: FastEthernet0/1, Port ID (outgoing port): FastEthernet0/1
Holdtime : 142 sec

Version :
Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(13)EA1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Tue 04-Mar-03 02:14 by yenanh

advertisement version: 2
Protocol Hello: OUI=0x00000C, Protocol ID=0x0112; payload len=27, value=00000000FFFFFFFF01022505000000000000000CCE3E3EC0FF0000
VTP Management Domain: 'lab.local'
Native VLAN: 1
Duplex: full

-------------------------
Device ID: switch2.lab.local
Entry address(es):
IP address: 10.0.1.211
Platform: cisco WS-C2950-24, Capabilities: Switch IGMP
Interface: FastEthernet0/24, Port ID (outgoing port): FastEthernet0/24
Holdtime : 142 sec

Version :
Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(13)EA1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Tue 04-Mar-03 02:14 by yenanh

advertisement version: 2
Protocol Hello: OUI=0x00000C, Protocol ID=0x0112; payload len=27, value=00000000FFFFFFFF01022505000000000000000CCE3E3EC0FF0000
VTP Management Domain: 'lab.local'
Native VLAN: 1
Duplex: full


This detailed output gives me additional useful information such as the VLAN and the IOS version.

Next I head over to switch2 and look at it's CDP information.


switch2#sh 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
switch1 Fas 0/24 168 S I WS-C2950-2Fas 0/24
switch1 Fas 0/1 168 S I WS-C2950-2Fas 0/1
router1.lab.localFas 0/2 175 R Cisco C831Eth 0
router1.lab.localFas 0/23 175 R Cisco C831Eth 1


Here I can see the connections to switch1 and additional connections to router1. Again I look at the detailed information to get the IP address of the router.


switch2#sh cdp entry *
-------------------------
Device ID: switch1
Entry address(es):
IP address: 10.0.1.210
Platform: cisco WS-C2950-24, Capabilities: Switch IGMP
Interface: FastEthernet0/24, Port ID (outgoing port): FastEthernet0/24
Holdtime : 152 sec

Version :
Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(12c)EA1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Sun 24-Nov-02 23:31 by antonino

advertisement version: 2
Protocol Hello: OUI=0x00000C, Protocol ID=0x0112; payload len=27, value=00000000FFFFFFFF01022505000000000000000C8582C600FF0000
VTP Management Domain: 'lab.local'
Native VLAN: 1
Duplex: full

-------------------------
Device ID: switch1
Entry address(es):
IP address: 10.0.1.210
Platform: cisco WS-C2950-24, Capabilities: Switch IGMP
Interface: FastEthernet0/1, Port ID (outgoing port): FastEthernet0/1
Holdtime : 152 sec

Version :
Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(12c)EA1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Sun 24-Nov-02 23:31 by antonino

advertisement version: 2
Protocol Hello: OUI=0x00000C, Protocol ID=0x0112; payload len=27, value=00000000FFFFFFFF01022505000000000000000C8582C600FF0000
VTP Management Domain: 'lab.local'
Native VLAN: 1
Duplex: full

-------------------------
Device ID: router1.lab.local
Entry address(es):
IP address: 10.0.2.254
Platform: Cisco C831, Capabilities: Router
Interface: FastEthernet0/23, Port ID (outgoing port): Ethernet1
Holdtime : 176 sec

Version :
Cisco IOS Software, C831 Software (C831-K9O3Y6-M), Version 12.4(4)T1, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Thu 22-Dec-05 01:39 by ccai

advertisement version: 2
Duplex: half

-------------------------
Device ID: router1.lab.local
Entry address(es):
IP address: 10.0.1.254
Platform: Cisco C831, Capabilities: Router
Interface: FastEthernet0/2, Port ID (outgoing port): Ethernet0
Holdtime : 176 sec

Version :
Cisco IOS Software, C831 Software (C831-K9O3Y6-M), Version 12.4(4)T1, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Thu 22-Dec-05 01:39 by ccai

advertisement version: 2
Duplex: full


From the output I am able to determine the IP addresses of the connected router interfaces and I can also see that one interface is configured to half duplex. Now I have some good information to begin populating my diagram with.



From here I would probably move to the router and look at the CDP table. But supposing I want to prevent CDP packets from leaving an interface? After all, quite detailed information is included in CDP that you might not want everyone to view.

I connect to the device that I want to stop sending CDP packets and turn CDP off on that particular interface. In my case I would like to stop router1 from sending CDP packets on interface ethernet 1.

router1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
router1(config)#int ethernet 1
router1(config-if)#no cdp enable 
router1(config-if)#end

Now when I check the switch that router1 is connected to I see that the holdtime decreases as the switch receives no CDP packet on the interface until after 180 seconds it reaches 0 and the entry is removed from the table.


switch2#sh 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
switch1 Fas 0/24 159 S I WS-C2950-2Fas 0/24
switch1 Fas 0/1 159 S I WS-C2950-2Fas 0/1
router1.lab.localFas 0/23 6 R Cisco C831Eth 1
router1.lab.localFas 0/2 126 R Cisco C831Eth 0

switch2#sh 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
switch1 Fas 0/24 153 S I WS-C2950-2Fas 0/24
switch1 Fas 0/1 152 S I WS-C2950-2Fas 0/1
router1.lab.localFas 0/23 0 R Cisco C831Eth 1
router1.lab.localFas 0/2 179 R Cisco C831Eth 0

switch2#sh 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
switch1 Fas 0/24 147 S I WS-C2950-2Fas 0/24
switch1 Fas 0/1 147 S I WS-C2950-2Fas 0/1
router1.lab.localFas 0/2 174 R Cisco C831Eth 0

Duplex Configuration : Simplified

Mismatched duplex settings can cause a network connection to perform poorly. Often a duplex mismatch is caused by a PC's network card or routers interface being configured to full or half duplex whilst the switch port being set to auto detect. If there is a duplex mismatch the CDP will report it, and these can be seen on screen by enabling the terminal monitor.

Below I have enabled terminal monitor and error messages are printed to the terminal.

switch1#terminal monitor 
switch1#
03:16:25: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/23 (not half duplex), with router1.lab.local Ethernet1 (half duplex).
switch1#
03:17:25: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/23 (not half duplex), with router1.lab.local Ethernet1 (half duplex).
switch1#

I can see that every 60 seconds as CDP packets are received I receive a warning that there is a duplex mismatch.

To very quickly check all the ports on my switch I use the following show command:

switch1#show interfaces status
Port Name Status Vlan Duplex Speed Type
Fa0/1 connected trunk a-full a-100 10/100BaseTX
Fa0/2 connected 1 a-full a-100 10/100BaseTX
Fa0/3 connected 1 a-full a-100 10/100BaseTX
Fa0/4 notconnect 1 auto auto 10/100BaseTX
Fa0/5 notconnect 1 auto auto 10/100BaseTX
Fa0/6 notconnect 1 auto auto 10/100BaseTX
Fa0/7 notconnect 1 auto auto 10/100BaseTX
Fa0/8 notconnect 1 auto auto 10/100BaseTX
Fa0/9 notconnect 1 auto auto 10/100BaseTX
Fa0/10 notconnect 1 auto auto 10/100BaseTX
Fa0/11 notconnect 1 auto auto 10/100BaseTX
Fa0/12 notconnect 1 auto auto 10/100BaseTX
Fa0/13 notconnect 1 auto auto 10/100BaseTX
Fa0/14 notconnect 1 auto auto 10/100BaseTX
Fa0/15 notconnect 1 auto auto 10/100BaseTX
Fa0/16 notconnect 1 full auto 10/100BaseTX
Fa0/17 notconnect 2 auto auto 10/100BaseTX
Fa0/18 notconnect 2 auto auto 10/100BaseTX
Fa0/19 notconnect 2 auto auto 10/100BaseTX
Fa0/20 notconnect 2 auto auto 10/100BaseTX
Fa0/21 notconnect 2 auto auto 10/100BaseTX
Fa0/22 notconnect 2 auto auto 10/100BaseTX
Fa0/23 connected 2 full 10 10/100BaseTX
Fa0/24 connected trunk a-full a-100 10/100BaseTX
Po5 connected trunk a-full a-100 


From the output I can see that although most ports are set to auto, some are configured with specific speed and duplex settings. Fa0/1,2,3 and fa0/24 are configured to auto for duplex and speed but have detected that the connect devices are set to full duplex and 100Mb.

After connecting to router1 I can use a show command to take a good look at the interface settings and the counters.

router1#show interfaces ethernet 1 
Ethernet1 is up, line protocol is up 
Hardware is PQUICC_FEC, address is 000e.3884.8540 (bia 000e.3884.8540)
Internet address is 10.0.2.254/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, 
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 10Mb/s
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:06, output 00:00:06, output hang never
Last clearing of "show interface" counters 23:42:46
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
3182 packets input, 362199 bytes, 0 no buffer
Received 1581 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
9407 packets output, 644928 bytes, 0 underruns
35 output errors, 377 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out


Example:

router1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
router1(config)#interface ethernet 1
router1(config-if)#duplex full
router1(config-if)#end


I verify the configuration and reset the counters on both interfaces so I can easily see if more issues occur.

router1#clear counters ethernet 1
Clear "show interface" counters on this interface [confirm]
router1#

switch1#clear counters fastEthernet0/23
Clear "show interface" counters on this interface [confirm]
switch1#
04:00:19: %CLEAR-5-COUNTERS: Clear counter on interface FastEthernet0/23 by vty0 (10.0.1.4)


It is always a good idea to configure interfaces on both servers and routers to match those of the switch rather than leave them at auto detect.

Wednesday, June 20, 2012

Network Basics - Explanation



  • Network - A network is a group of computers connected together in a way that allows information to be exchanged between the computers.
  • Node - A node is anything that is connected to the network. While a node is typically a computer, it can also be something like a printer or CD-ROM tower.
  • Segment - A segment is any portion of a network that is separated, by a switch, bridge or router, from other parts of the network.
  • Backbone - The backbone is the main cabling of a network that all of the segments connect to. Typically, the backbone is capable of carrying more information than the individual segments. For example, each segment may have a transfer rate of 10 Mbps (megabits per second), while the backbone may operate at 100 Mbps.
  • Topology - Topology is the way that each node is physically connected to the network (more on this in the next section).
  • Local Area Network (LAN) - A LAN is a network of computers that are in the same general physical location, usually within a building or a campus. If the computers are far apart (such as across town or in different cities), then a Wide Area Network (WAN) is typically used.
  • Network Interface Card (NIC) - Every computer (and most other devices) is connected to a network through an NIC. In most desktop computers, this is an Ethernet card (normally 10 or 100 Mbps) that is plugged into a slot on the computer's motherboard.
  • Media Access Control (MAC) address - This is the physical address of any device -- such as the NIC in a computer -- on the network. The MAC address, which is made up of two equal parts, is 6 bytes long. The first 3 bytes identify the company that made the NIC. The second 3 bytes are the serial number of the NIC itself.
  • Unicast - A unicast is a transmission from one node addressed specifically to another node.
  • Multicast - In a multicast, a node sends a packet addressed to a special group address. Devices that are interested in this group register to receive packets addressed to the group. An example might be a Cisco router sending out an update to all of the other Cisco routers.
  • Broadcast - In a broadcast, a node sends out a packet that is intended for transmission to all other nodes on the network.


What is VLAN -VLAN TUTORIAL FOR BEGINNERS What is VlAN, VLAN fundas, VLAN basics, VLAN for beginners





OSI Network Architecture 7 Layers Model - Simplified


Layer 7: Application Layer
• Defines interface to user processes for communication and data
transfer in network
• Provides standardized services such as virtual terminal, file and job
transfer and operations
Layer 6: Presentation Layer
• Masks the differences of data formats between dissimilar systems
• Specifies architecture-independent data transfer format
• Encodes and decodes data; encrypts and decrypts data; compresses
and decompresses data
Layer 5: Session Layer
• Manages user sessions and dialogues
• Controls establishment and termination of logic links between users
• Reports upper layer errors
Layer 4: Transport Layer

Manages end-to-end message delivery in network
• Provides reliable and sequential packet delivery through
error recovery and flow control mechanisms
• Provides connectionless oriented packet delivery

Layer 3: Network Layer
• Determines how data are transferred between network
devices
• Routes packets according to unique network device addresses
• Provides flow and congestion control to prevent network
resource depletion
Layer 2: Data Link Layer
• Defines procedures for operating the communication
links
• Frames packets
• Detects and corrects packets transmit errors
Layer 1: Physical Layer
• Defines physical means of sending data over network
devices
• Interfaces between network medium and devices
• Defines optical, electrical and mechanical characteristics


Tuesday, June 19, 2012

Troubleshooting Router Crashes


Introduction

When we refer to a "system crash", we mean a situation where the system has detected an unrecoverable error, and has restarted itself.
The errors that cause crashes are typically detected by processor hardware, which automatically branches to special error handling code in the ROM monitor. The ROM monitor identifies the error, prints a message, saves information about the failure, and restarts the system.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, see the Cisco Technical Tips Conventions.

Getting Information About the Crash

When the router crashes, it is extremely important to gather as much information as possible about the crash before you manually reload or power-cycle the router. All information about the crash, except that which has been successfully stored in the crashinfo file, is lost after a manual reload or power-cycle. The following outputs give some indication and information on the crash.
If you have the output of a show version, show stacks, show context, or show tech support command from your Cisco device, you can use Output Interpreter to display potential issues and fixes. To use Output Interpreter , you must be a registered customer, be logged in, and have JavaScript enabled.
CommandDescription
show versionThis command first appeared in Cisco IOS® Software Release10.0. The show version EXEC command displays the configuration of the system hardware, the software version, the names and sources of configuration files and software images, the router uptime, and information on how the system has been restarted.
IMPORTANT: If the router is reloaded after the crash (for example, if it has been power-cycled or the reload command has been issued), this information will be lost, so try to collect it before reloading!
show stacksThis command first appeared in Cisco IOS Software Release 10.0. The show stacks EXEC command is used to monitor the stack usage of processes and interrupt routines. The show stacks output is one of the most indispensable sources of information to collect when the router crashes.
IMPORTANT: If the router is reloaded after the crash (for example, through power-cycle or thereload command), this information will be lost so try to collect it before reloading!
show contextThis command first appeared in Cisco IOS Software Release 10.3. The show context EXEC command is used to display information stored in nonvolatile RAM (NVRAM) when an exception occurs. Context information is specific to processors and architectures, whereas software version and uptime information are not. Context information for different router types could therefore differ. The output displayed from the show context command includes:
  • the reason for the system reboot.
  • stack trace.
  • software version.
  • signal number, code, and router uptime information.
  • all the register contents at the time of the crash.
show tech-supportThis command first appeared in Cisco IOS Software Release 11.2. This command is useful in collecting general information about the router when you report a problem. It includes:
  • show version
  • show running-config
  • show stacks
  • show interface
  • show controller
  • show process cpu
  • show process memory
  • show buffers
console logIf you are connected to the console of the router at the time of the crash, you will see something like this during the crash:
*** System received a Software forced crash *** 
signal= 0x17, code= 0x24, context= 0x619978a0 
PC = 0x602e59dc, Cause = 0x4020, Status Reg = 0x34008002 
DCL Masked Interrupt Register = 0x000000f7 
DCL Interrupt Value Register = 0x00000010 
MEMD Int 6 Status Register = 0x00000000 
Keep this information and the logs before it. Once the router comes up again, do not forget to get the show stacks output.
syslogIf the router is set up to send logs to a syslog server, you will see some information on what happened before the crash on the syslog server. However, when the router is crashing, it may not be able to send the most useful information to this syslog server. So most of the time,syslog output is not very useful for troubleshooting crashes.
crashinfoThe crashinfo file is a collection of useful information related to the current crash, stored in bootflash or flash memory. When a router crashes due to data or stack corruption, more reload information is needed to debug this type of crash than just the output from the normalshow stacks command.
The crashinfo is written by default to bootflash:crashinfo on the Cisco 12000 Gigabit Router Processor (GRP), the Cisco 7000 and 7500 Route Switch Processors (RSPs), and the Cisco 7200 series routers. For the Cisco 7500 Versatile Interface Processor 2 (VIP2), this file is stored by default to bootflash:vip2_slot_no_crashinfo where the slot_no is the VIP2 slot number. For the Cisco 7000 Route Processor (RP), the file is stored by default toflash:crashinfo.
For more details, see Retrieving Information from the Crashinfo File.
core dumpA core dump is a full copy of the router's memory image. This information is not necessary for troubleshooting most types of crashes, but it is highly recommended when filing a new bug. You may need to enable some debugs to add more information into the core dump such as debug sanity, scheduler heapcheck process, and memory check-interval 1.
For more details, see Creating Core Dumps.
rom monitorThe router might end up in ROM monitor after a crash when its config-register setting ends with 0. If the processor is a 68k, the prompt will be ">". You can get the stack trace with the kcommand. If the processor is a reduced instruction set computing (RISC), the prompt will be "rommon 1>". Get the output of stack 50 or show context.

Types of Crashes

The show version and show stacks commands provide you with output that gives you an indication of the type of the crash that occurred, such as bus error, or software forced crash. You can also get crash type information from the crashinfo and show context commands. For some later Cisco IOS Software versions, the crash reasons are not clearly indicated (for example, you see "Signal = x" where x is a number). Refer to Versatile Interface Processor Crash Reason Codes to translate this number into something meaningful. For example, "Signal = 23" translates to a software forced crash. Follow these links to troubleshoot the specific type of crash your router is experiencing:

Router Module Crashes

Sometimes, only a specific router module crashes, and not the router itself. Here are some documents that describe how to troubleshoot crashes on some router modules:

Examples of Output which Indicate the Crash

Router#show version 
Cisco Internetwork Operating System Software 
IOS (tm) RSP Software (RSP-PV-M), Version 12.0(10.6)ST, EARLY DEPLOYMENT
MAINTENANCE INTERIM SOFTWARE 
Copyright (c) 1986-2000 by cisco Systems, Inc. 
Compiled Fri 23-Jun-00 16:02 by richv 
Image text-base: 0x60010908, data-base: 0x60D96000 

ROM: System Bootstrap, Version 12.0(19990806:174725), DEVELOPMENT SOFTWARE 
BOOTFLASH: RSP Software (RSP-BOOT-M), Version 12.0(9)S, EARLY DEPLOYMENT 
RELEASE SOFTWARE (fc1) 

Router uptime is 20 hours, 56 minutes 
System returned to ROM by error - a Software forced crash, PC 0x60287EE8 
System image file is "slot0:rsp-pv-mz.120-10.6.ST" 

cisco RSP8 (R7000) processor with 131072K/8216K bytes of memory. 
R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache 
Last reset from power-on 
G.703/E1 software, Version 1.0. 
G.703/JT2 software, Version 1.0. 
X.25 software, Version 3.0.0. 
Chassis Interface. 
1 EIP controller (6 Ethernet). 
1 VIP2 R5K controller (1 FastEthernet)(2 HSSI). 
6 Ethernet/IEEE 802.3 interface(s) 
1 FastEthernet/IEEE 802.3 interface(s) 
2 HSSI network interface(s) 
2043K bytes of non-volatile configuration memory. 
20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 
16384K bytes of Flash internal SIMM (Sector size 256K). 
No slave installed in slot 7. 
Configuration register is 0x2102 

Router#show stacks 
Minimum process stacks: 
Free/Size   Name 
5188/6000   CEF Reloader 
9620/12000  Init 
5296/6000   RADIUS INITCONFIG 
5724/6000   MDFS Reload 
2460/3000   RSP memory size check 
8176/9000   DHCP Client 

Interrupt level stacks: 
Level    Called Unused/Size  Name 
  1         163   8504/9000  Network Interrupt 
  2       14641   8172/9000  Network Status Interrupt 
  3           0   9000/9000  OIR interrupt 
  4           0   9000/9000  PCMCIA Interrupt 
  5        5849   8600/9000  Console Uart 
  6           0   9000/9000  Error Interrupt 
  7      396230   8604/9000  NMI Interrupt Handler 

System was restarted by error - a Software forced crash, PC 0x602DE884 at 05:07:31 
UTC Thu Sep 16 1999 
RSP Software (RSP-JSV-M), Version 12.0(7)T,  RELEASE SOFTWARE (fc2) 
Compiled Mon 06-Dec-99 19:40 by phanguye 
Image text-base: 0x60010908, database: 0x61356000 
Stack trace from system failure: 
FP: 0x61F73C30, RA: 0x602DE884 
FP: 0x61F73C30, RA: 0x6030D29C 
FP: 0x61F73D88, RA: 0x6025E96C 
FP: 0x61F73DD0, RA: 0x6026A954 
FP: 0x61F73E30, RA: 0x602B94BC 
FP: 0x61F73E48, RA: 0x602B94A8
When a crashinfo is available in bootflash, the following is displayed at the end of the show stacks command:
     
*************************************************** 
******* Information of Last System Crash ********** 
*************************************************** 
    
Using bootflash:crashinfo_20000323-061850. 2000 
CMD: 'sh int fas' 03:23:41 UTC Thu Mar 2 2000 
CMD: 'sh int fastEthernet 6/0/0' 03:23:44 UTC Thu Mar 2 2000 
CMD: 'conf t' 03:23:56 UTC Thu Mar 2 2000 
CMD: 'no ip cef di' 03:23:58 UTC Thu Mar 2 2000 
CMD: 'no ip cef distributed ' 03:23:58 UTC Thu Mar 2 2000 
... 
       
Router#show context 

System was restarted by error - a Software forced crash, PC 0x602DE884 at 
05:07:31 UTC Thu Sep 16 1999 
RSP Software (RSP-JSV-M), Version 12.0(7)T,  RELEASE SOFTWARE (fc2) 
Compiled Mon 06-DEC-99 19:40 by phanguye 
Image text-base: 0x60010908, database: 0x61356000 
       
Stack trace from system failure: 
FP: 0x61F73C30, RA: 0x602DE884 
FP: 0x61F73C30, RA: 0x6030D29C 
FP: 0x61F73D88, RA: 0x6025E96C 
FP: 0x61F73DD0, RA: 0x6026A954 
FP: 0x61F73E30, RA: 0x602B94BC 
FP: 0x61F73E48, RA: 0x602B94A8 

Fault History Buffer: 
RSP Software (RSP-JSV-M), Version 12.0(7)T,  RELEASE SOFTWARE (fc2) 
Compiled Mon 06-DEC-99 19:40 by phanguye 
Signal = 23, Code = 0x24, Uptime 3w0d 
$0 : 00000000, AT : 619A0000, v0 : 61990000, v1 : 00000032 
a0 : 6026A114, a1 : 61A309A4, a2 : 00000000, a3 : 00000000 
t0 : 61F6CD80, t1 : 8000FD88, t2 : 34008700, t3 : FFFF00FF 
t4 : 00000083, t5 : 3E840024, t6 : 00000000, t7 : 00000000 
s0 : 0000003C, s1 : 00000036, s2 : 00000000, s3 : 61F73C48 
s4 : 00000000, s5 : 61993A10, s6 : 61982D00, s7 : 61820000 
t8 : 0000327A, t9 : 00000000, k0 : 61E48C4C, k1 : 602E7748 
gp : 6186F3A0, sp : 61F73C30, s8 : 00000000, ra : 6030D29C 
EPC : 602DE884, SREG : 3400E703, Cause : 00000024 
Error EPC : BFC00000, BadVaddr : 40231FFE

Cisco IOS Upgrade Procedure


Introduction

This document explains how to upgrade a Cisco IOS® software image on Cisco Access Router platforms. The examples provided from the 2600 and 3600 Series Routers also apply to the list of router platforms mentioned. The Cisco IOS Software file names can vary, based on the Cisco IOS Software release, feature set, and platform.
These routers are addressed in this document:
  • Cisco 1000 Series Routers
  • Cisco 1400 Series Routers
  • Cisco 1600-R Series Routers
  • Cisco 1700 Series Routers
  • Cisco 2600 Series Routers
  • Cisco 2800 Series Routers
  • Cisco 3600 Series Routers
  • Cisco 3700 Series Routers
  • Cisco 3800 Series Routers
  • Cisco 4000 Series Routers
  • Cisco 4700 Series Routers
  • Cisco AS5300 Series Routers
  • Cisco MC3810 Series Routers
Note: You must be a registered user and you must be logged in to the Cisco.com website in order to use the troubleshooting tools described in this document. In order to register for the Cisco.com website, visit the Cisco.com Registration page.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the Cisco IOS Software Release 12.0 or later.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Background Information

Several protocols are available to copy the Cisco IOS image into the Cisco routers. The most commonly used protocol is TFTP. Other protocols include ftp, http, https, scp, and rcp. If necessary, you can copy an image from one device to another. For more information, refer to the Copying From One Router to Another section of the How To Copy a System Image from One Device to Another document.
This section describes how to install a TFTP server, how to establish a console session with the router, and the router boot problems.

Install a TFTP Server

A Trivial File Transfer Protocol (TFTP) server application must be installed on a TCP/IP-ready workstation or PC. After the application is installed, you must perform a minimal level of configuration.
  1. Download a TFTP server. Refer to TFTP Server Selection and Use for more information.
  2. Configure the TFTP application to operate as a TFTP server instead of a TFTP client.
  3. Specify the outbound file directory. This is the directory in which the Cisco IOS software images are stored. Most TFTP applications provide a setup routine in order to assist in these configuration tasks.

Establish a Console Session with the Router

Even if it is possible to connect to the router through a Telnet session, Cisco recommends that you connect directly to the router through the console port because, if something goes wrong during the upgrade, you might need to be physically present next to the router to power-cycle it. Moreover, the Telnet connection is lost while the router reboots during the upgrade procedure.
A rolled cable, usually a flat black cable, connects the console port of the router to one of the COM ports of the PC.
When the PC is connected to the console port of the router, open HyperTerminal on the PC, and use these settings:
Speed 9600 bits per second

     8 databits

     0 parity bits

     1 stop bit

     No Flow Control
If garbage characters appear in the HyperTerminal session, either you have not set the HyperTerminal properties properly or the config-register of the router is set to a non-standard value for which the console connection speed is higher than 9600 bps. In order to check the value of the config-register, issue the show version command. The config-register values appears in the last line of the output. Verify that this value is set to 0x2102 or 0x102.
Note: In order for a configuration register change to take effect, you must reload the router.
When you are sure that the console speed is set to 9600 bps on the router side, you should check the HyperTerminal properties. Refer to Applying Correct Terminal Emulator Settings for Console Connections for more information on how to set the HyperTerminal properties.

Router Boot Problems

When you are connected to the console port of the router, you might notice that the router is either in ROMmon or Boot mode. These two modes are used for recovery and diagnostic procedures. If you do not see the usual router prompt, you should use these recommendations in order to proceed with the upgrade procedure installation:
  • The router boots in ROMmon mode, and this message appears when you issue the dir flash: command:
    rommon 1 >dir flash: 
    device does not contain a valid magic number 
    dir: cannot open device "flash:" 
    rommon 2 >
    This error message displays when the Flash is empty or the filesystem is corrupted. Refer to Xmodem Console Download Procedure Using ROMmonfor more information.
    Note: You might also need to consult the Boot Failure procedures specific to your platform. Choose your platform from the Product Support Selector in order to locate these procedures. Look in the Troubleshooting section of each document.
  • The router boots in boot mode with these messages on the console:
    router(boot)>
    device does not contain a valid magic number
    boot: cannot open "flash:"
    boot: cannot determine first file name on device "flash:"
    These error messages display in the console output when the Flash is empty or when the file system is corrupted. Copy a valid image on the Flash as described in the procedures provided in this document.
    Note: You might also need to consult the Boot Failure procedures specific to your platform. Choose your platform from the Product Support Selector in order to locate these procedures. Look in the Troubleshooting section of each document.

Software Installation and Upgrade Procedures

This section covers these topics:

Step 1: Select a Cisco IOS Software Image

Your first step in the upgrade procedure is to select the correct Cisco IOS software release and feature set. This step is very important, and these factors can affect the decision for which Cisco IOS you should select:
  • Memory requirement: The router should have sufficient disk or flash memory to store the Cisco IOS. The router should also have sufficient memory (DRAM) to run the Cisco IOS. If the router does not have sufficient memory (DRAM), the router will have boot problems when it boots through the new Cisco IOS.
  • Interfaces and modules support: You must ensure that the new Cisco IOS supports all the interfaces and modules in the router.
  • Software feature support: You must ensure that the new Cisco IOS supports the features used with the old Cisco IOS.
Refer to How to Choose a Cisco IOS Software Release for information on how to select the correct software version and feature set.

Step 2: Download the Cisco IOS Software Image to the TFTP Server

Download the Cisco IOS Software image onto your workstation or PC from the Download Software Area (registered customers only) .

Step 3: Identify the File System to Copy the Image

The file system type "flash" or "disk" is used to store the Cisco IOS image. The show file system command output shows the list of file systems available on the router. The common "disk/flash" file systems supported in Cisco routers have prefixes such as flash:, slot0:, slot1:, disk0: and disk1:. It should have sufficient space to store the Cisco IOS image. You can use the show file system or the dir file_system command in order to find the free space.
2600#show file system
File Systems:

     Size(b)     Free(b)      Type  Flags  Prefixes
           -           -    opaque     rw   archive:
           -           -    opaque     rw   system:
       29688       20571     nvram     rw   nvram:
           -           -    opaque     rw   null:
           -           -   network     rw   tftp:
           -           -    opaque     ro   xmodem:
           -           -    opaque     ro   ymodem:
*   49807356    20152636     flash     rw   flash:
           -           -    opaque     wo   syslog:

2800#show file system
File Systems:

     Size(b)     Free(b)      Type  Flags  Prefixes
           -           -    opaque     rw   archive:
           -           -    opaque     rw   system:
           -           -    opaque     rw   null:
           -           -   network     rw   tftp:
           -           -    opaque     ro   xmodem:
           -           -    opaque     ro   ymodem:
*   64016384    15470592      disk     rw   flash:#
      245752      239218     nvram     rw   nvram:
           -           -    opaque     wo   syslog:
 
3600#show file system
File Systems:

     Size(b)     Free(b)      Type  Flags  Prefixes
           -           -    opaque     rw   archive:
           -           -    opaque     rw   system:
      129016      126071     nvram     rw   nvram:
           -           -    opaque     rw   null:
           -           -   network     rw   tftp:
*   33030140    20511708     flash     rw   flash:
    16777212    16777212     flash     rw   slot0:
    16515068     8038516     flash     rw   slot1:
           -           -    opaque     rw   xmodem:
           -           -    opaque     rw   ymodem:
3700#show file system
File Systems:

     Size(b)     Free(b)      Type  Flags  Prefixes
           -           -    opaque     rw   archive:
           -           -    opaque     rw   system:
       57336       51389     nvram     rw   nvram:
           -           -    opaque     rw   null:
           -           -   network     rw   tftp:
           -           -    opaque     ro   xmodem:
           -           -    opaque     ro   ymodem:
*   63881216    22765568      disk     rw   flash:#
    31932416    31932416      disk     rw   slot0:#
           -           -    opaque     wo   syslog:
 

Step 4: Prepare for the Upgrade

You should consider these items before you upgrade the Cisco IOS:
  • If the router has sufficient memory (flash, slot or disk), you can store both the old Cisco IOS and the new Cisco IOS. You can boot the router in the ROMMON mode and boot the old Cisco IOS in case of boot failure with new Cisco IOS. This method saves time if you must roll back the Cisco IOS.
  • Backup the configuration from the router because some of the Cisco IOS releases add default configurations. This newly added configuration may conflict with your current configuration. Compare the configuration of the router after the Cisco IOS upgrade with the configuration backed up before the upgrade. If there are differences in the configuration, you must ensure they do not affect your requirements.

Step 5: Verify that the TFTP Server has IP Connectivity to the Router

The TFTP server must have a network connection to the router and must be able to ping the IP address of the router targeted for a TFTP software upgrade. In order to achieve this connection, the router interface and the TFTP server must have an IP address in the same range or a default gateway configured.
Check the IP address of the TFTP server in order to verify this configuration.

Step 6: Copy IOS Image to the Router

Now that you have IP connectivity and can ping between the computer that acts as a TFTP server and the router, you can copy the Cisco IOS Software image into the Flash.
Note: Before you copy the image, ensure that you have started the TFTP server software on your PC, and that you have the file name mentioned in the TFTP server root directory. Cisco recommends that you keep a backup of the router and access server configuration before you upgrade. The upgrade does not affect the configuration, which is stored in nonvolatile RAM [NVRAM]. However, this situation might happen if the right steps are not followed properly.
Note:  In this section you are presented with three examples that describe how to copy the Cisco IOS image. You can use any one of these methods in order to copy the image.

Example 1: Copy the image to flash: from TFTP server

Upgrade the new image from a TFTP server. Use the copy tftp: flash: command in order to copy the image from TFTP server to the flash.
2600>enable
Password:xxxxx 
2600#copy tftp: flash:
Address or name of remote host []? 10.10.10.2

!--- 10.10.10.2 is the IP address of the TFTP server

Source filename []? c2600-adventerprisek9-mz.124-12.bin
Destination filename [c2600-adventerprisek9-mz.124-12.bin]?y 
Accessing tftp://10.10.10.2/c2600-adventerprisek9-mz.124-12.bin...
Erase flash: before copying? [confirm]y 

!--- If there is not enough memory available, erase the Flash.


!--- If you have sufficient memory you can type n and press enter

Erasing the flash filesystem will remove all files! Continue? [confirm]y
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeee ...erased
Erase of flash: complete
Loading c2600-adventerprisek9-mz.124-12.bin from 10.10.10.2 (via Ethernet0/0): !!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 29654656/49807356 bytes]

Verifying checksum...  OK (0xAC8A)
29654656 bytes copied in 56.88 secs (80383 bytes/sec)
The copy process takes several minutes. This time differs from network to network. When the copy process is in progress, messages are displayed that indicate which file has been accessed.
The exclamation point "!" indicates that the copy process is in progress. Each exclamation point indicates that ten packets have transferred successfully. A checksum verification of the image occurs after the image is written to Flash memory.

Example 2: Copy the image to slot1: from TFTP server

Upgrade the new image from a TFTP server. If you choose the slot1: file systems, use the copy tftp: slot1: command in order to copy the image from TFTP server to slot1.
3600#copy tftp: slot1:
Address or name of remote host []? 171.68.173.10

!--- 171.68.173.10 is the IP address of the TFTP server

Source filename []? c3640-i-mz.122-7b.bin
Destination filename [c3640-i-mz.122-7b.bin]?
Accessing tftp://171.68.173.10/c3640-i-mz.122-7b.bin...
Erase slot1: before copying? [confirm]n 

!--- You specify "n" because there is enough memory available.

Loading c3640-i-mz.122-7b.bin from 171.68.173.10 (via Ethernet1/0): 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!
[OK - 5996844/11993088 bytes]

Verifying checksum...  OK (0x13F0)
5996844 bytes copied in 67.708 secs (89505 bytes/sec)
3600#
The copy process takes several minutes. This time differs from network to network. When the copy process is in progress, messages are displayed that indicate which file has been accessed.
The exclamation point "!" indicates that the copy process is in progress. Each exclamation point indicates that ten packets have transferred successfully. A checksum verification of the image occurs after the image is written to Flash memory.

Example 3: Copy the IOS image to flash: from another router

You can configure a router as TFTP server. If you choose the flash: file systems, use the copy tftp: flash: command in order to copy the image from TFTP server to flash.
Router-tftp(config)#tftp-server flash:c7200-a3js-mz.122-15.T16.bin


!--- Router-tftp is configured as the TFTP server.

7200#copy tftp: flash:
Address or name of remote host []? 172.22.1.84
Source filename []? c7200-a3js-mz.122-15.T16.bin
Destination filename [c7200-a3js-mz.122-15.T16.bin]?
Accessing tftp://172.22.1.84/c7200-a3js-mz.122-15.T16.bin...
Erase flash: before copying? [confirm]n
Loading c7200-a3js-mz.122-15.T16.bin from 172.22.1.84 (via GigabitEthernet0/1):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 19187152 bytes]

Verifying checksum...  OK (0x15C1)
19187152 bytes copied in 482.920 secs (39732 bytes/sec)

Step 7: Verify the Cisco IOS Image in the File System

Verify the image in the file system.
2600#dir flash:

Directory of flash:/

    1  -rw-    29654656                    <no date>  c2600-adventerprisek9-mz.1
24-12.bin

49807356 bytes total (20152636 bytes free)

2600#verify flash:c2600-adventerprisek9-mz.124-12.bin

Verifying file integrity of flash:c2600-adventerprisek9-mz.124-12.bin...........
................................................................................

................................................................................
.............................Done!
Embedded Hash   MD5 : 1988B2EC9AFAF1EBD0631D4F6807C295
Computed Hash   MD5 : 1988B2EC9AFAF1EBD0631D4F6807C295
CCO Hash        MD5 : 141A677E6E172145245CCAC94674095A

Signature Verified
Verified flash:c2600-adventerprisek9-mz.124-12.bin
Refer to System Message Guide for information about different %SIGNATURE error messages and the necessary action to be taken.

Step 8: Verify the Configuration Register

config-register value—Use the show version command in order to check this value. The value is displayed in the last line of the show version output. It should be set to 0x2102.
2600#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z. 
2600(config)#config-register 0x2102 
2600(config)#^Z

Step 9: Verify the Boot Variable

IOS image in the flash—If the first file in the Flash is not the Cisco IOS Software image, but a configuration file, or something else, then you need to configure aboot system statement in order to boot the specified image. Otherwise, the router tries to boot with the configuration file or the first file in the Flash, which does not work. If there is only one file in the Flash and it is the Cisco IOS Software image, this step is not necessary.
2600#show run | include boot
boot system flash:c2600-adventerprisek9-mz.123-21.bin

2600#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z. 
2600(config)#no boot system
2600(config)#boot system flash:c2600-adventerprisek9-mz.124-12.bin
2600(config)#^Z
IOS image in the slot1—The boot variable that points to the old Cisco IOS needs to be removed first, and then the router needs to be configured to boot through the new Cisco IOS.
 3600# show run | include boot
boot system slot1:c3640-i-mz.120-22.bin

3600#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z. 
3600(config)#no boot system
3600(config)#boot system  slot1:c3640-i-mz.122-7b.bin
3600(config)#^Z

Step 10: Save the Configuration and Reload the Router

Save the configuration, and reload the Router.
2600# write memory
2610# reload
Proceed with reload? [confirm]
Jan 24 20:17:07.787: %SYS-5-RELOAD: Reload requested by console. Reload Reason:
Reload Command.

Step 11: Verify the Cisco IOS Upgrade

Verify that the router runs with the proper image.
After the reload is complete, the router should run the desired Cisco IOS Software image. Use the show version command in order to verify the Cisco IOS software.
2600#show version
00:22:25: %SYS-5-CONFIG_I: Configured from console by console
Cisco IOS Software, C2600 Software (C2600-ADVENTERPRISEK9-M), Version 12.4(12),
RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Fri 17-Nov-06 11:18 by prod_rel_team

ROM: System Bootstrap, Version 12.2(8r) [cmong 8r], RELEASE SOFTWARE (fc1)

2610 uptime is 22 minutes
System returned to ROM by reload
System image file is "flash:c2600-adventerprisek9-mz.124-12.bin"
Here is the show version output of 3600 router that has Cisco IOS in the slot1:
3600#show version
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-I-M), Version 12.2(7b), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 04-Mar-02 20:23 by pwade
Image text-base: 0x600089A8, data-base: 0x60A6A000

ROM: System Bootstrap, Version 11.1(19)AA, EARLY DEPLOYMENT RELEASE SOFTWARE (f)

Router uptime is 2 minutes
System returned to ROM by reload
System image file is "slot1:c3640-i-mz.122-7b.bin"

cisco 3640 (R4700) processor (revision 0x00) with 59392K/6144K bytes of memory.

Processor board ID 10524422
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Bridging software.
X.25 software, Version 3.0.0.
4 Ethernet/IEEE 802.3 interface(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
4096K bytes of processor board System flash (Read/Write)
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
20480K bytes of processor board PCMCIA Slot1 flash (Read/Write)

Configuration register is 0x2102