Most Cisco networking hardware, with the exception of the Cisco PIX firewall series, ships with the Cisco Inter-network Operating System, or IOS. IOS hardware includes network routers, switches, and other similar devices. The basic design of most of this hardware controls the types of memory a device is equipped with, and what functions the various types of Cisco memory serve. At the hardware level, there are four main types of Cisco memory: DRAM, EPROM, NVRAM, and Cisco Flash Memory. DRAM, or Dynamic Random Access Memory caters to two main device requirements. The first of these is known as Processor Memory which is reserved for exclusive access by the CPU, which it uses when executing software running on the Cisco IOS platform. Processor Memory also stores crucial data that is used constantly, like the configuration settings in current use, and any routing tables. The second is Shared Memory, also known as I/O Memory, or Cisco Packet Memory. The function of Packet Memory is simple and self-explanatory: Data coming in and being sent out is buffered to the Packet Memory portion of the available DRAM before it is transmitted over the network interface. EPROM, or Erasable Programmable Read-Only Memory is usually referred to as a BootROM. EPROM is generally programmed at some point during the latter stages of manufacture, and cannot generally be changed by consumers. In Cisco devices, EPROM is generally loaded with two crucial firmware components. The first is a boot loader which takes over should the device fail to find a valid bootable image in Flash Memory, and provides alternate boot options. If even this failsafe should fail, the second firmware application installed on Cisco EPROM is used, the ROM Monitor. ROM Monitor has a user interface and includes options for troubleshooting failures of the ROM chips. In Cisco devices, NVRAM, or Non-Volatile Random Access Memory, stores important configuration information that is used by IOS during boot and by some programs during startup, which is stored in the Startup Configuration File. NVRAM also allows the functionality provided by the Cisco Software Configuration Register, which allows a device to be booted and selection from multiple Cisco IOS images that may be available in Flash Memory. It is sometimes called Shared Memory. Cisco Flash Memory is the most diverse of each of these types, and it comes in many forms, however, its primary use is to store a bootable Cisco IOS image from which a device can start. Most devices have onboard Flash memory from which the device boots, however, some equipment – particularly higher-end hardware like Cisco GSR routers – also have the capability to boot from an image stored on a Cisco Flash Memory card, which is removable. Regardless of the memory type, it is important to find a memory reseller who is reliable. Things to look for when choosing a memory reseller are that they have memory for every Cisco device in stock, offer a warranty on the memory, and have technical people with whom you can speak if you have any problems.
Posts Tagged ‘nvram’
Knowing Copy running-config and startup-config
June 6th, 2009
feed Another common configure network commands are copy running-config and startup-config. Those commands create the backup copy of the running configuration in the NVRAM. The show configuration command can be used to check the contents of the NVRAM. The show running-config command displays active settings in the current terminal session. Here the example list of parameters for the copy command that use running-config and startup-config.
R1#copy ?
 /erase         Erase destination file system.
 flash:         Copy from flash: file system
 ftp:           Copy from ftp: file system
 null:          Copy from null: file system
 nvram:         Copy from nvram: file system
 rcp:           Copy from rcp: file system
 running-config   Copy from current system configuration       ÂÂ
  startup-config   Copy from startup configuration              ÂÂ
  system:        Copy from system: file system
 tftp:          Copy from tftp: file system
 xmodem:        Copy from xmodem: file system
 ymodem:        Copy from ymodem: file system
R1#copy running-config ?
 flash:         Copy to flash: file system
 ftp:           Copy to ftp: file system
 null:          Copy to null: file system
 nvram:         Copy to nvram: file system
 rcp:           Copy to rcp: file system
 running-config Update (merge with) current system configuration
 startup-config Copy to startup configuration
 system:        Copy to system: file system
 tftp:          Copy to tftp: file system
R1#copy running-config
When Configure Command Changing
February 8th, 2009
feed The concept behind the configure command is changing, or configuring, active parameters by processing configuration commands from a source. The configure overwrite-network version of the command is an exception, though. When this command is entered, it copies a configuration file from a TFTP server to the NVRAM, without any processing.
Tags: 
