Cisco Cisco Aironet 340 Ethernet Bridges Guia Do Utilizador
13 - 10 Aironet 340 Series Bridge
remote Aironet 340 Series Bridge.
3.
Select the password option and type the access password for the
remote PC, host, or the console. Press ENTER.
4.
Select the filename option type the name of the firmware file you are
sending to the PC, host, or Aironet 340 Series Bridge (including
drive and directory). Press ENTER.
drive and directory). Press ENTER.
If uploading to another Aironet 340 Series Bridge, the filename
option must have a value even though the value is not used by the
remote Aironet 340 Series Bridge.
option must have a value even though the value is not used by the
remote Aironet 340 Series Bridge.
5.
Select the put option. The unit will begin an FTP session to the
remote host PC or Aironet 340 Series Bridge.
Uploading the Unit’s configuration (Config)
You may use this option to save the configuration on a remote host or PC
in a format suitable for later downloading using FTP or BOOTP.
in a format suitable for later downloading using FTP or BOOTP.
You are first prompted for the name of the file to be created on the
remote system. Once the filename is entered the transfer will begin.
remote system. Once the filename is entered the transfer will begin.
Downloading Using the Internet Boot Protocol (Bootp/DHCP)
The Bootp/DHCP option is enabled by default when the Aironet 340
Series Bridge is powered on. The process for downloading firmware
files using the Bootp/DHCP parameter is:
Series Bridge is powered on. The process for downloading firmware
files using the Bootp/DHCP parameter is:
1.
On power up, the Aironet 340 Series Bridge will issue boot protocol
requests to see if there are any Bootp or DHCP servers on the infra-
structure that have been configured with the unit infrastructure
address.
structure that have been configured with the unit infrastructure
address.
2.
If no response is found, the request is repeated up to 30 times with a
4 second wait after the first request. It then doubles the time
between requests for each additional retry. If there is still no
response, the unit gives up.
between requests for each additional retry. If there is still no
response, the unit gives up.
3.
If multiple responses are received, the unit will pick a DHCP server
over a Bootp server.