Netgear GSM7212F GSM5212P/GSM7212P/GSM7212F/GSM7224P Setup Manual - Page 22

Netgear GSM7212F Manual

Page 22 highlights

7000 Series Managed Switch the specified bootfile. If the unicast attempts fail, or if a TFTP server address was not provided, Auto Install process stops. No Broadcast attempts are made. Note: The bootfile is required to have a file type of *.cfg. The bootfile cannot have the following names: fastpath.cfg, startup-config and hpc_broad.cfg. These are reserved Default Network Configuration File Attempts are made to download a default network configuration file with the name fp-net.cfg if the specified bootfile cannot be found, a failure occurs in the download, or the switch was not provided a specific bootfile name by the DHCP server. The switch issues TFTP requests for a network configuration file in the same manner as it attempts to download a host-specific configuration file. The default network configuration file should have IP address to host-name mappings using the command ip host . If the default network configuration file does not contain the switch IP address, the switch uses DNS to attempt to resolve its host name. A sample fp-net.cfg file follows: config ...ip host switch_to_setup 192.168.1.10 ip host another_switch 192.168.1.11 ... exit Once a host name has been determined, the switch then issues a TFTP request for a file named .cfg file, where is the first eight characters of the switch's host name. If the switch is unable to map its IP address to a host name, Auto Install sends TFTP requests for the default configuration file host.cfg. The following table summarizes the config files that can be downloaded, and the order in which they are sought. Order Sought 1 File Name .cfg Description Final File Sought Host-specific config file, ending in a *.cfg file Yes extension Default network config file No 2 fp-net.cfg Auto Install Configuration 22

  • 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
  • 34
  • 35
  • 36

Auto Install Configuration
22
7000 Series Managed Switch
the specified bootfile. If the unicast attempts fail, or if a TFTP server address was not
provided, Auto Install process stops. No Broadcast attempts are made.
Note:
The bootfile is required to have a file type of *.cfg. The bootfile
cannot have the following names: fastpath.cfg, startup-config and
hpc_broad.cfg. These are reserved
Default Network Configuration File
Attempts are made to download a default network configuration file with the name fp-net.cfg if
the specified bootfile cannot be found, a failure occurs in the download, or the switch was not
provided a specific bootfile name by the DHCP server. The switch issues TFTP requests for a
network configuration file in the same manner as it attempts to download a host-specific
configuration file.
The default network configuration file should have 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.
A sample fp-net.cfg file follows:
config
...
ip host switch_to_setup 192.168.1.10
ip host another_switch 192.168.1.11
... <other hostname definitions>
exit
Once a host name has been determined, the switch then issues a TFTP request for a file
named
<hostname>.cfg
file, where <hostname> is the first eight characters of the switch’s
host name.
If the switch is unable to map its IP address to a host name, Auto Install sends TFTP requests
for the default configuration file host.cfg.
The following table summarizes the config files that can be downloaded, and the order in
which they are sought.
Order
Sought
File Name
Description
Final File
Sought
1
<bootfile>.cfg
Host-specific config file, ending in a *.cfg file
extension
Yes
2
fp-net.cfg
Default network config file
No