The Internal Components of a Cisco Router and Switch

The Internal Components of a Cisco Router and Switch

Bootstrap
Bootstrap is stored in the microcode of the ROM, the bootstrap is bringing a router up during initialization. It will boot the router and then load the IOS.

POST
POST (power-on-self-test) is stored in the microcode of the ROM, the POST is used to check the basic functionality of the router hardware and determine which interfaces are present.

ROM monitor
ROM monitor stored in the microcode of the ROM monitor is used for manufacturing, testing, and troubleshooting.

Mini-IOS
Mini-IOS called the RXBOOT or boot loader by Cisco, the mini-IOS is a small IOS in ROM that can be used to bring up an interface and load a Cisco IOS into flash memory. The mini-IOS can also perform a few other maintenance operations.

RAM
RAM (randomly used to hold packet buffers, ARP cache, routing table, and also access memory) is the software and data structure that allows the router to function. Running configuration is stored in RAM, and most routers expand the IOS from flash into RAM upon boot.

ROM
ROM (read-only memory) is used to start and maintain the router. Hold the POST and the bootstrap program, as well as the mini-IOS. Flash memory stores the Cisco IOS by default. Flash memory is not erased when the router is reloaded. It is EEPROM (electronically erasable programmable read-only memory) created by Intel.

NVRAM
NVRAM (nonvolatile RAM) is used to hold the router and switch configuration. NVRAM is not erased when the router or switch is reloaded and does not store an IOS. The configuration is stored in NVRAM.

Configuration register
Configuration register used to control how the router boots up. This value can be found as the last time of the show version command output and by default is set to 0x2102, which tells the router to load the IOS from flash memory as well as to load the configuration from NVRAM.

Comments

What is of NBAR (network- based application recognition),classification QOS How to configure NBAR?

When we implement Quality of Service (QoS ) the first step is classification, by default our router does not care about what kind of IP packets it is. Our router just looks at the routing table to find the correct destination IP address and forwards. When we configure QoS technologies like queuing, policing, or shaping before doing first we have to identify what kind of traffic is running on our routers so we can figure out what kind of application it belongs to. This is classification. What is Quality of Service (QOS)? What is Modular Quality of service CLI (MQC)? What is Classification and marking? What are IP Precedence and DSCP Values? What is AF and EF? Once we identify our traffic (classify). Now we can mark and apply QoS policy to it. There are a few methods on IOS routers for classification: Header inspection It is a simple classification method and it works really good but has some disadvantages. Let’s say we configure our router all th...

What is Classification and marking? What is IP Precedence and DSCP Values? What is AF and EF?

Classification and Marking Classification and marking are the processes of identifying the priority of each packet. This is the first step of QOS control and should be done near the source hosts. Classification is the process of identifying and categorising traffic into classes, typically based upon incoming interface IP precedence, DSCP Source or Destination address. Application classification is the most fundamental QOS building block. Without classification, all packets are treated the same. The table lists the criteria of classification Marking Marking is the QOS feature component that colours a packet so it can be identified and distinguished from other packets in QOS treatment. Commonly used markers: link-layer: COS (ISL, 802.1q), MPLS EXP bits,...

What are BGP RR Cluster and BGP RR refelector? CCIE LAB

Route Reflector Cluster A BGP-enabled router or BGP speakers. By default BGP speaker routers do not advertise iBGP-learned prefixes to iBGP peer routers - this has to be done to maintain loop prevention. RFC4456 introduces the route reflection feature which helps to remove the need of full mesh configuration between iBGP speakers routers. When the route reflector reflects a route, it creates and modifies an optional non-transitive attribute called CLUSTER_LIST by adding its own cluster ID to it. This attribute is used for loop prevention: when a BGP router receives update which CLUSTER_LIST contains router's own cluster ID, this update is discarded. Route reflector Route Reflector scalable alternative to an ibgp full mesh its allow a BGP speaker (route reflector –RR) to advertise route received from an ibgp peer to other ibgp peers. note:client update server. Server update to all the remaining clients. All client should establish neighbor with only servers . client will...

edgarnetwork

Search This Blog