From: k c (jwongccie@yahoo.com.hk)
Date: Sat Dec 06 2003 - 01:51:30 GMT-3
Assume only two routers, one is newly installed, the other is connected to this new router with config file stored. Can this router serve as DHCP and TFTP server? If yes, do it need to set ip helper-address on the interface connected to the new router?
"Howard C. Berkowitz" <hcb@gettcomm.com> wrote:At 9:47 PM +0000 12/5/03, Ken.Farrington@barclayscapital.com wrote:
>How the hell does autoinstall work :) been looking at the docs and its all
>cricket to me?
The daddy router has the seed and plants it in the mommy router...
No, that's probably not it. Autoinstall, more likely, was designed
by someone on Really Good Drugs. Let us tell the Christmas Story of
Autoinstall, and how the DNS and TFTP Servers at the North Pole
autoinstall configurations in Nice, not Naughty, routers.
When you get to the First Level of Understanding of Autoinstall, you
will think it's a magnificent joke. Anything that uses something
called SLARP must be a Monty Python routine. True Enlightenment
comes when you realize it is NOT a joke.
Reindeer probably get involved somewhere. (there's a URL at the end
if you don't like stories). This is a generic description; you'll
want to look at the URL for specific variations for specific
interface types.
Begin on Christmas morning, when the new router awakens.
1. I am a newly awakened router. I know nothing...I think.
2. Instinctively, I know that I can request an IP address on some interface,
in some interface-dependent way like SLARP or DHCP.
I get an IP address. If I don't, I die.
3. Now I know my IP address. First, I send out a TFTP request for a file
called cisconet.cfg. This is the First Magic File Name to ask for.
If I get it, it will contain ip host statements from which I can map
my IP address to a hostname. If I can map that way, I go to step 8.
4. If I don't get the First Magic File, I broadcast a reverse DNS lookup
and see if there's a nice DNS server that will tell me my name. If
I learn my True Name, I go to step 8.
5. If DNS thinks I'm naughty and won't talk to me, I try to TFTP again,
this time looking for the Second Magic File, network-confg. If I get the
Second Magic File, I learn my True Name from its IP host statements and
go to step 8.
6. If there is no Second Magic File Fairy, I TFTP again, invoking the name
of the Third Magic File, router-confg. If I succeed, I learn my True
Name and go to step 8.
7. If I can't get the Third Magic File, I TFTP again for the Fourth Magic
File, cisconet.cfg. If I don't get this, I go back to Step 3, and try
again, three times. If I get the Fourth Magic File, I learn my True
Name and go to step 8. If I fail on the third retry, I go to step 9.
No, you don't have to wear ruby slippers and click your heels each time
you recycle. Admittedly, I'd find it interesting to see how you
a. Put ruby slippers on a router. How many?
b. Click them.
8. I TFTP for the file [True Name].cfg. If I get this, it is my real
real configuration for the router. It tucks this into
NVRAM, then copies it into RAM and starts to run with the new config.
9. If all else fails, I go into the setup dialogue and hope there's a
nice human at my console.
If you don't have magic in your heart, go look at
http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_configuration_guide_chapter09186a00800ca667.html
>
>I have a 1600 on an FR connection to a "staging router".
>It is running IOS (tm) 1600 Software (C1600-SY-L), Version 12.0(7)T, - so
>crap code
>
>Does this code work, docs say it should from 10.3 for autoinstall over FR?
>
>How do you get the "new" router to kick of the process. ?
>
>I am soo lost :(
>
>Many thx
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:36 GMT-3