{"id":169,"date":"2009-07-10T17:31:29","date_gmt":"2009-07-10T16:31:29","guid":{"rendered":"http:\/\/mccltd.net\/blog\/?p=169"},"modified":"2010-02-08T19:39:44","modified_gmt":"2010-02-08T19:39:44","slug":"cisco-boot-sequence","status":"publish","type":"post","link":"http:\/\/darenmatthews.com\/blog\/?p=169","title":{"rendered":"Cisco Boot Sequence"},"content":{"rendered":"

Booting up the Router<\/strong><\/p>\n

Cisco routers can boot Cisco IOS software from these locations:<\/p>\n

1. Flash memory
\n2. TFTP server
\n3. ROM (not full Cisco IOS)<\/p>\n

There are some options which provide flexibility and fallback alternatives:Default boot sequence for Cisco IOS software:<\/strong>
\n1. NVRAM
\n2. Flash (sequential)
\n3. TFTP server (network boot)
\n4. ROM (partial IOS)<\/p>\n

Note: boot system commands can be used to specify the primary IOS source and fallback sequences.<\/p>\n

Booting up the router and locating the Cisco IOS<\/p>\n

1. POST (power on self test)
\n2. Bootstrap code executed
\n3. Check Configuration Register value (NVRAM) which can be modified using the config-register command<\/p>\n

0 = ROM Monitor mode
\n1 = ROM IOS
\n2 – 15 = startup-config in NVRAM<\/p>\n

4. Startup-config file: Check for boot system commands (NVRAM)
\nIf boot system commands in startup-config
\na. Run boot system commands in order they appear in startup-config to locate the IOS
\nb. [If boot system commands fail, use default fallback sequence to locate the IOS (Flash, TFTP, ROM)?]<\/p>\n

If no boot system commands in startup-config use the default fallback sequence in locating the IOS:
\na. Flash (sequential)
\nb. TFTP server (netboot)
\nc. ROM (partial IOS) or keep retrying TFTP depending upon router model<\/p>\n

5. If IOS is loaded, but there is no startup-config file, the router will use the default fallback sequence for locating the IOS and then it will enter setup mode or the setup dialogue.
\n6. If no IOS can be loaded, the router will get the partial IOS version from ROM
\n===================================================================<\/p>\n

Default (normal) Boot Sequence<\/p>\n

Power on Router – Router does POST – Bootstrap starts IOS load – Check configuration register
\nto see what mode the router should boot up in (usually 0x102 to 0x10F to look in NVRAM) – check the startup-config file in NVRAM for boot-system commands (normally there aren’t any) – load IOS from Flash.<\/p>\n

Boot System Commands<\/p>\n

Router(config)# boot system flash IOS filename\u00a0\u00a0 – boot from FLASH memory
\nRouter(config)# boot system tftp IOS filename tftp server ip address\u00a0\u00a0 – boot from a TFTP server
\nRouter(config)# boot system rom\u00a0\u00a0 – boot from system ROM<\/p>\n

Configuration Register Command<\/p>\n

Router(config)# config-register 0x10x (where that last x is 0-F in hex)<\/p>\n

When the last x is:
\n0 = boot into ROM Monitor mode
\n1 = boot the ROM IOS
\n2 – 15 = look in startup config file in NVRAM<\/p>\n

\n\n\n\n
<\/td>\n<\/td>\n\n\n\n\n
\n

\n

Booting up the Router<\/span><\/strong><\/p>\n

Cisco routers can boot Cisco IOS software from these locations:<\/p>\n

1. Flash memory
\n2. TFTP server
\n3. ROM (not full Cisco IOS)<\/p>\n

Multiple source options provide flexibility and fallback alternatives<\/p>\n

Locating the Cisco IOS Software<\/strong><\/p>\n

Default boot sequence for Cisco IOS software:<\/p>\n

1. NVRAM
\n2. Flash (sequential)
\n3. TFTP server (network boot)
\n4. ROM (partial IOS)<\/p>\n

Note:<\/strong> boot system commands can be used to specify the primary IOS source and fallback sequences.<\/p>\n

Booting up the router and locating the Cisco IOS<\/strong><\/p>\n

1.<\/strong> POST (power on self test)
\n2.<\/strong> Bootstrap code executed
\n3.<\/strong> Check Configuration Register value (NVRAM) which can be modified using the config-register command<\/p>\n

0<\/strong> = ROM Monitor mode
\n1<\/strong> = ROM IOS
\n2 – 15<\/strong> = startup-config in NVRAM<\/p>\n

4.<\/strong> Startup-config file: Check for boot system commands (NVRAM)
\nIf boot system commands in startup-config
\na.<\/strong> Run boot system commands in order they appear in startup-config to locate the IOS
\nb.<\/strong> [If boot system commands fail, use default fallback sequence to locate the IOS (Flash, TFTP, ROM)?]<\/p>\n

If no boot system commands in startup-config use the default fallback sequence in locating the IOS:
\na.<\/strong> Flash (sequential)
\nb.<\/strong> TFTP server (netboot)
\nc.<\/strong> ROM (partial IOS) or keep retrying TFTP depending upon router model<\/p>\n

5.<\/strong> If IOS is loaded, but there is no startup-config file, the router will use the default fallback sequence for locating the IOS and then it will enter setup mode or the setup dialogue.
\n6.<\/strong> If no IOS can be loaded, the router will get the partial IOS version from ROM<\/p>\n

===================================================================<\/p>\n

Default (normal) Boot Sequence<\/strong><\/p>\n

Power on Router – Router does POST – Bootstrap starts IOS load – Check configuration register
\nto see what mode the router should boot up in (usually 0x102 to 0x10F to look in NVRAM) – check the startup-config file in NVRAM for boot-system commands (normally there aren’t any) – load IOS from Flash.<\/p>\n

Boot System Commands<\/strong><\/p>\n

Router(config)# boot system flash IOS filename<\/em> – boot from FLASH memory<\/span>
\nRouter(config)# boot system tftp IOS filename<\/em> tftp server ip address<\/em> – boot from a TFTP server<\/span>
\nRouter(config)# boot system rom \u00a0 – boot from system ROM<\/span><\/p>\n

Configuration Register Command<\/strong><\/p>\n

<\/strong>Router(config)# config-register 0x10x (where that last x is 0-F in hex)<\/em><\/p>\n

When the last x is:
\n0<\/strong> = boot into ROM Monitor mode
\n1<\/strong> = boot the ROM IOS
\n2 – 15<\/strong> = look in startup config file in NVRAM<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Booting up the Router Cisco routers can boot Cisco IOS software from these locations: 1. Flash memory 2. TFTP server 3. ROM (not full Cisco IOS) There are some options which provide flexibility and fallback alternatives:<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[83],"tags":[],"_links":{"self":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/169"}],"collection":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=169"}],"version-history":[{"count":2,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/169\/revisions"}],"predecessor-version":[{"id":362,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/169\/revisions\/362"}],"wp:attachment":[{"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=169"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=169"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/darenmatthews.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=169"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}