Boot Configuration
Boot Configuration defines the location from which the console server loads the operating system. The console server can
boot from its internal firmware or from the network. By default, the console server boots from internal firmware in Flash
memory. Clicking
System- Boot Configuration
displays the Boot Configuration screen.
If you need to boot from the network, make sure the following prerequisites are met:
•
A TFTP server must be available on the network
•
A firmware file must be downloaded from Avocent and made available on the TFTP server
•
The boot filename and the IP address of the TFTP server is known
To configure boot configuration:
1.
Click
System - Boot Configuration
.
2.
Under Boot Mode, select
From Flash
, and select
Image 1
or
Image 2
.
-or-
Select
From Network
and enter the following information:
•
Appliance IP Address: Enter the fixed IP address or a DHCP assigned IP address to the console server.
•
TFTP Server IP: Enter the IP address of the TFTP boot server.
•
Filename: Enter the filename of the boot firmware.
3.
Using the drop-down menu, select whether the Watchdog Timer is enabled. If the Watchdog Timer is enabled,
the console server reboots if the software crashes.
4. Using the drop-down menu, select the console port speed and click
Save
.
Information
Click
System - Information
to view the console server’s identity, versions, power and CPU information.
Usage
Click
System - Usage
to view memory and Flash usage.
3.3.4 Network
Click
Network
to view and configure the Hostname, DNS, IPv6, Bonding, IPv4 and IPv6 static routes, Hosts, Firewall, IPSec
(VPN) and SNMP network options.
Settings
Click
Network - Settings
to make changes to the configured network settings.
From this page, an administrator can configure the console server's hostname and DNS settings, which includes the primary
and secondary DNS, domain and search addresses. An administrator can also enable IPv6 and configure it to get the DNS
and/or domain from DHCPv6.
For a fault tolerant network configuration, the Bonding option may be selected to combine eth0 and eth1 into a single high-
availability network interface using the active-backup bonding mode. Interface eth0 is the normal active interface with eth1
as the backup; if the carrier signal is lost on eth0, eth1 becomes the active interface. The eth0 MAC address is always used
in bonding mode, no matter which interface is active.
NOTE: After enabling or disabling bonding, you must reboot the console server for the change to take effect.
Vertiv™ | Avocent® ACS800/8000 Advanced Console Server Installer/User Guide
22
