From: Snow, Tim (timothy.snow@eds.com)
Date: Mon Sep 15 2003 - 22:15:10 GMT-3
Chandru,
Is it possible for you to install a sniffer on the lan segment where your
TFTP server is, I'd be interested in seeing the filename that the new router
is requesting.
Per the following snippet from cisco, the router.cfg file should have worked
even without the "ip host router 172.16.6.6"
After acquiring an IP address acquired from the RARP, DHCP, or BOOTP server,
the new router will attempt to resolve its hostname from a network
configuration file or from a DNS service.
The new router will first attempt to resolves its IP address-to-hostname
mapping by sending a TFTP broadcast requesting the file "network-confg" or
"cisconet.cfg".
The network configuration file is a configuration file generally shared by
several routers. In this case, it is used to map the IP address of the new
router to the name of the new router. The network configuration file must
reside on a reachable TFTP server and must be globally readable. For
example, to assign a hostname of "rtr1" to a new router with the address
192.168.10.2, the following line must appear in the network configuration
file:
ip host rtr1 192.168.10.2
If the new router cannot locate and download a "network-confg" or a
"cisconet.cfg" file, or if the IP address-to-hostname mapping does not match
the newly acquired IP address, the new router sends a DNS broadcast request.
If a DNS server is available and has an entry that maps the acquired IP
address of the new router to its name, the new router successfully resolves
its name.
If DNS does not have an entry that maps the new router's address to its
name, the new router cannot resolve its hostname. The new router will then
attempt to download a default configuration file ("router-confg",
"router.cfg", or "ciscortr.cfg") from the TFTP server. If this attempt also
fails, the router will enter Setup mode, or, if using Frame Relay-based
AutoInstall, will enter user EXEC mode.
If you can't get it to work, I'll try and simulate your setup tonight and
see what I can find. Do let me know.....
Tim
-----Original Message-----
From: chandru lohana [mailto:chandrul@gtllimited.com]
Sent: Monday, September 15, 2003 10:04 AM
To: ccielab@groupstudy.com
Subject: Autoinstall over Frame-relay
hi ,
I am trying Autoinstall over Frame-relay Scenario..as under
TFTP server-eth0-- R1 S0( existing router) ----FR switch ----- S0 R2 new
config of router R1 :- existing router :-
int s0
encap fr
no shut
clockrate 128000
int s0.1 multi-point
ip address 172.16.6.5 255.255.255.0
fr map ip 172.16.6.6 100 br
ip helper address 172.16.9.183
ip ospf priority 255
int e0
ip address 172.16.9.5 255.255.255.0
router ospf 1
network 172.16.6.0 0.0.0.255 area 0
IP address of TFTP server 172.16.9.183 attached to ethernet
I have created two files in tftproot directory
1. network-confg containg the host name of new router
ip host router 172.16.6.6
2. another file router.cfg with config for new router ..
Nowwhen I do autoinstall on new router I get IP address on the frame-relay
interface of new router i.e 172.16.6.6
and TFTP server also starts pinging 172.16.6.6 for some ( 2 minutes) and
then PING BREAKS .. and the new router is not able to download and any
filer from TFTP ....
I have stated debug ip udp on EXISTING ROUtter AND COMMUNICATION FROM
172.16.6.6 (68) TO 255.255.255.255(67) 172.16.6.5 (67) TO 172.16.9.183
HAPPENS AND EW ROUTER TRIES TO GET THE FILE S VIA BOOTP BROADCAST AND ALSO
VIA PORT 53 dns BORADCAST BUT WITHOT ANY SUCCESS..
WILL BE OBLIGED IF SOMEBODY CAN HELP..
THANKS AND REGARDS
CHANDRU LOHANA
***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:28 GMT-3