Bryan,
For auto install over frame-relay, the Autoinstall router sends BOOTP
requests over all active DLCIs. The staging router then sends a BOOTP reply
based on determining on exactly which the DLCI the request arrived from. It
then sends the IP address that is configured in the frame-relay map
statement for that particular DLCI to the Autoinstall router via BOOTP
reply.
I dont think Inverse-arp would work because the Autoinstall router would not
be capable of responding to inverse-arp requests since it has blank
configuration (hence no dynamic maps on the staging rouer), which why static
map statements are essential on the staging router.
Regards
Lejoe
On Wed, Apr 22, 2009 at 3:19 AM, Modular <modulartx_at_gmail.com> wrote:
> So there's something within AutoInstall that allows the AI Router to get
> it's IP from the staging/hub router?
> And this has to do with the fact that there's a frame map command on the
> staging/hub router with that IP address
> pointing to/down the PVC assigned to the AI Router? Is the true even if
> Inverse-Arp is disabled?
>
> Thanks,
> Bryan R.
>
> On Tue, Apr 21, 2009 at 9:55 AM, Lejoe <styran_at_gmail.com> wrote:
>
>> Hi Bryan,
>>
>> You dont need any configuration on the Auto Install router R5 (i.e
>> frame-relay map statement etc). If you're doing Autoinstall over Frame-relay
>> the ip address of the auto install router is obtained by the frame-relay map
>> statement configured on the staging device. (so no DHCP either)
>>
>> Regards
>>
>> Lejoe
>>
>> On Tue, Apr 21, 2009 at 5:13 AM, Modular <modulartx_at_gmail.com> wrote:
>>
>>> I've been trying to nail down autoinstall just in case I get the
>>> dreaded
>>> autoinstall over frame-relay scenario
>>> on my Lab. Using info I found on the net I put some notes together on it.
>>> Would some of you mind looking
>>> through my notes and telling me if I'm missing anything or if anything is
>>> wrong?
>>>
>>> Thanks,
>>> Bryan R.
>>>
>>>
>>> ----------------------------------------------------------------------------------------------------------------------
>>> Auto-Install:
>>> Happens in steps:
>>> 1. DHCP to get IP. (optional)
>>> 2. Name-server lookup to get host name.
>>> 3. TFTP server to get config file.
>>>
>>> There are 4 "Functions" involved with this:
>>> 1. DHCP -Gives AI Router an IP.
>>> 2. DNS Server -Gives AI Router it's Name.
>>> 3. TFTP Server -Gives AI Router it's config file.
>>> 4. Hub -Optional. If exists need helper maps pointing to tftp & DNS
>>> servers
>>> AND
>>> "ip name-server" and domain-lookup configured. Possibly DHCP
>>> configured.
>>>
>>> CONFIGURATION:
>>> R5 is AI Router. R1 is the TFTP server, R6 is the DNS server and R4 is a
>>> FR
>>> hub.
>>>
>>> R1: -TFTP Server
>>>
>>> "tftp-server flash:r5-confg"
>>> -Note that the file must be in the flash of the device.
>>>
>>>
>>> R6: -DNS Server
>>>
>>> ip host r5 155.1.0.5
>>> ip dns server
>>> ip domain-lookup
>>>
>>>
>>> R4: -FR Hub & DHCP Server.
>>>
>>> ip domain-lookup
>>> ip name-server 155.1.146.6
>>> interface Serial0/0
>>> ip address 155.1.0.4 255.255.255.0
>>> ip helper-address 155.1.146.1 <-IP's of tftp and dns servers.
>>> ip helper-address 155.1.146.6
>>> encapsulation frame-relay
>>> frame-relay map ip 155.1.0.5 405 broadcast
>>> no frame-relay inverse-arp <-No inverse-arp, so need frame
>>> map on
>>> AI Router.
>>>
>>> ip dhcp exclude-address 155.1.0.1 155.1.0.4
>>> ip dhcp exclude-address 155.1.0.6 155.1.0.255
>>> ip dhcp pool
>>> network 155.1.0.0 /24
>>>
>>>
>>> R5: -AutoInstall router
>>>
>>> interface serial0/0
>>> encapsulation frame-relay
>>> no frame-relay inverse-arp
>>> frame-relay map ip 155.1.0.4 504 broadcast
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Wed Apr 22 2009 - 09:48:20 ART
This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:12 ART