On a side note, I was always taught to use boot tftp:// as a last effort to get the boxes booted, if it can't load anything else.  
For example:

boot system flash disk0:s72033-pk9sv-mz.122-18.SXD7.bin
boot system flash sup-bootflash: s72033-pk9sv-mz.122-18.SXD5.bin
boot system tftp tftpserver:/cisco/6500/sup720/s72033-pk9sv-mz.122-18.SXD7.bin

To tell you the truth I've never even considered doing it.  Personally I want to rely on the network to boot my network infrastructure.  Maybe I'm crazy, but that introduces too many variables for my taste.


nb 


On 9/27/06, Bill Marquette <[EMAIL PROTECTED]> wrote:
On 9/27/06, Jan Zorz <[EMAIL PROTECTED]> wrote:
>
> I am exploring the idea of booting all cisco routers from tftp server. As we
> have redundant pfsense config, first idea would be to boot them from pfsense
> (CARP ip).
>
> Any thoughts or ideas, why this is not a good way to do it?

Other than the blue boxes bad design?

> Any future plans to include tftp server into pfsense distro?

Nope.  We're a firewall, not a server.

--Bill

Reply via email to