Netgear XSM4324FS Software Setup Manual Software Version 12.x - Page 27

About obtaining a configuration file, Host-specific configuration file

Page 27 highlights

M4300 Intelligent Edge Series Fully Managed Stackable Switches About obtaining a configuration file After obtaining IP addresses for both the switch and the TFTP server, the Auto Install process attempts to download a configuration file. A host-specific configuration file is downloaded, if possible. Otherwise, a network configuration file is used as a bridge to get the final configuration. For more information, see Host-specific configuration file on page 27 and Default network configuration file on page 27. Host-specific configuration file If the DHCP server specifies a bootfile name, the switch attempts to download a host-specific configuration file. The switch makes three unicast TFTP requests for the specified bootfile. If the unicast attempts fail, or if a TFTP server address was not provided, the Auto Install process stops. No broadcast attempts are made. Note: The bootfile is required for a file type of *.cfg. The bootfile cannot be named fastpath.cfg, startup-config, or hpc_broad.cfg. These names are reserved. Default network configuration file If the switch cannot find the specified bootfile or the bootfile name from the DHCP server, the switch attempts to download the default network configuration file (fp-net.cfg). The switch issues TFTP requests for a network configuration file in the same manner that it attempts to download a host-specific configuration file. The default network configuration file must contain IP address-to-host name mappings using the command ip host hostname address. If the default network configuration file does not contain the switch IP address, the switch uses DNS to attempt to resolve its host name. The following example is a sample fp-net.cfg file: config ... ip host switch_to_setup 192.168.1.10 ip host another_switch 192.168.1.11 ... exit When a host name is determined, the switch issues a TFTP request for a file named hostname.cfg, in which hostname is the first eight characters of the switch's host name. If the switch cannot map its IP address to a host name, Auto Install sends TFTP requests for the default configuration file host.cfg. Use the Auto Install Configuration 27 Software Setup Manual

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33

M4300 Intelligent Edge Series Fully
Managed
Stackable Switches
Use the Auto Install Configuration
Software Setup Manual
27
About obtaining a configuration file
After obtaining IP addresses for both the switch and the TFTP server, the Auto Install process
attempts to download a configuration file. A host-specific configuration file is downloaded, if
possible. Otherwise, a network configuration file is used as a bridge to get the final
configuration. For more information, see
Host-specific configur
a
tion file
on page
27
and
Default network configur
a
tion file
on page
27
.
Host-specific configuration file
If the DHCP server specifies a bootfile name, the switch attempts to download a host-specific
configuration file. The switch makes three unicast TFTP requests for the specified bootfile. If
the unicast attempts fail, or if a TFTP server address was not provided, the Auto Install
process stops. No broadcast attempts are made.
Note:
The bootfile is required for a file type of
*.cfg
. The bootfile cannot be
named
fastpath.cfg
,
startup-config
, or
hpc_broad.cfg
.
These names are reserved.
Default network configuration file
If the switch cannot find the specified bootfile or the bootfile name from the DHCP server, the
switch attempts to download the default network configuration file (
fp-net.cfg
). The switch
issues TFTP requests for a network configuration file in the same manner that it attempts to
download a host-specific configuration file.
The default network configuration file must contain IP address–to–host name mappings
using the command
ip host
hostname address
. If the default network configuration file
does not contain the switch IP address, the switch uses DNS to attempt to resolve its host
name.
The following example is a sample
fp-net.cfg
file:
config
...
ip host switch_to_setup 192.168.1.10
ip host another_switch 192.168.1.11
... <other hostname definitions>
exit
When a host name is determined, the switch issues a TFTP request for a file named
hostname
.cfg
, in which
hostname
is the first eight characters of the switch’s host name.
If the switch cannot map its IP address to a host name, Auto Install sends TFTP requests for
the default configuration file
host.cfg
.