Here is the result of removing startup-config, erasing flash, removing the
IOS from the TFTP server and putting a default IOS on the TFTP server. It
does work as it should now! Thanks again for helping...
Cisco4000#erase startup-config
Erasing the nvram filesystem will remove all files! Continue? [confirm]
[OK]
Erase of nvram: complete
Cisco4000#erase flash
Erasing the flash filesystem will remove all files! Continue? [confirm]
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Erase of flash: complete
Cisco4000#reload
System configuration has been modified. Save? [yes/no]: no
Proceed with reload? [confirm]
01:40:19: %SYS-5-RELOAD: Reload requested
System Bootstrap, Version 4.14(7), SOFTWARE
Copyright (c) 1986-1994 by cisco Systems
4000 processor with 32768 Kbytes of main memory
--- System Configuration Dialog ---
Refer to the 'Getting Started' Guide for additional help.
Default settings are in square brackets '[]'.
Configuring interface IP parameters for netbooting:
Configuring interface Serial0:
Is this interface in use? [yes]: IP address for this interface: IP
add
ress for this interface: IP address for this interface: 1.0.0.1
Number of bits in subnet field [0]:
Class A network is 1.0.0.0, 0 subnet bits; mask is 255.0.0.0
Configuring interface Serial1:
Is this interface in use? [yes]:
IP address for this interface: 2.0.0.1
Number of bits in subnet field [0]:
Class A network is 2.0.0.0, 0 subnet bits; mask is 255.0.0.0
Configuring interface TokenRing0:
Is this interface in use? [yes]: n
Configuring interface Ethernet0:
Is this interface in use? [yes]:
Media-type 10BaseT or AUI? [10BaseT]:
IP address for this interface: 192.168.0.1
Number of bits in subnet field [0]:
Class C network is 192.168.0.0, 0 subnet bits; mask is 255.255.255.0
Booting cisco2-4000 from 192.168.0.109:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK -
4650
060/16108530 bytes]
F3: 9176+4640852+165008 at 0x12000
Self decompressing the image :
#################################################
############################################################################
####
##################################################################### [OK]
-----Original Message-----
From: Leigh Anne Chisholm [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 12, 2000 11:33 AM
To: Pierre-Alex; Cisco
Subject: RE: netboot
If you have any boot system commands in your config file, a net boot will
NOT be attempted. Here's a groupstudy message I posted last month that
explains the boot sequence...
-----Original Message-----
From: Leigh Anne Chisholm [mailto:[EMAIL PROTECTED]]
Sent: November 6, 2000 6:29 PM
To: A.Strobel; Cisco@Groupstudy. Com
Subject: RE: Boot Sequence
If the configuration register value on a Cisco router has been set to
0x2102, and the router is unable to load a valid IOS image from Flash, the
router will:
1. Attempt a net boot using the boot field value in the configuration
register to determine the filename to use when requesting the IOS image to
be downloaded.
NOTE: If there is a boot system command stored in the startup-config file,
a net boot will NOT be attempted.
2. If a valid IOS image cannot be found, the router attempts to boot from
the RXBOOT file in ROM.
3. If this file cannot be found, the router continues to boot from ROM
Monitor. An IOS can be sent to the router via Xmodem through the console or
AUX port if an AUX port exists.
Configuration registers and boot sequences seemed to be one of those poorly
explained and understood areas - so recently as part of a project I've been
working on, I spent a bit of time researching how exactly these processes
work. When I first removed my IOS images from Flash, I didn't get the net
boot attempt--like as Adam and Raul described. However, once I removed my
boot system command from the startup-config file, I received the message:
%Error opening tftp://255.255.255.255/cisco2-C1600 (Timed out)boot of
"cisco2-C1600"
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Pierre-Alex
Sent: December 12, 2000 6:48 AM
To: Cisco
Subject: netboot
"If there are no boot commands in the configuration file, the router
attempts to boot the first file in system Flash memory. If no file is found
in system Flash memory, the router attempts to netboot a default file whose
name is derived from the value of the boot field (for example: cisco2-4000).
If the netboot attempt fails, the boot helper image in boot Flash will boot
up"
QUESTION:
Why is not netboot working the way it is suppose to?
WHAT I DID:
My virtual configuration setting register is set to 0x2102. (Which means I
am allowing netboot in case of failure)
In my startup-config I have told the router to load the IOS from the TFTP
server (located on e0)
I have removed the IOS from the TFTP server and I have erased flash. (To
force netboot)
I have put a renamed copy of my IOS at the root of the TFTP server. Since I
am using 0x2102, the name the router will search during netboot will be
cisco2-4000.bin. (Just in case I copied the IOS as: cisco2-4000.bin and
Cisco2-4000)
WHAT I GOT:
Copyright (c) 1986-1994 by cisco Systems
4000 processor with 32768 Kbytes of main memory
Illegal IP keyword - classless
Booting c4000-js-mz.120-2a.bin ..... [File not found]
Network load failed
INTERPRETATION:
The netboot failed or was never attempted!??
***************************Can you Help: did I miss something? did the
router actually tried netboot? I have no clues...
THANKS
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
