Now the ADC is deployed. We can begin to manage it. The ADC Manager has this advantage: you can edit or view the individual ADC without having to open it up, saving time. All of these functions may be done within the ADC itself, it should be noted.
Here is the dashboard for the individual ADC. It's not the Device Management dashboard. If you don't know how to get here, click one of your ADC's on the Device Management page, as shown below:
Shows information about the individual ADC device. The connected IP is the ADC's IP.
The hostname part of the FQDN, such as www.
Note: You can specify the @ symbol to denote the zone root. The value substituted for @ is the preceding $ORIGIN directive.
|Serial Number||Serial Number of the ADC|
|Firmware version||Firmware version of the ADC|
|Connected IP||IP of the ADC connected to the Manager|
1. Open Console. Pulls up a console black box through which you can edit the ADC, without going into the ADC itself.
2. Access GUI. Brings you into the managed ADC - no longer in the Manager; we're in the ADC. Note: On that ADC web page the IP address will not show the normal ADC IP; it will show the Manager's IP with the port number (the port number used to connect to the ADC).
As in: xx.xxx.xxx.xxx:yyyyy
The 'x' belongs to the manager, whereas the 'y' is the port number.
|1. FortiGuard Services Information||
Displays the status of FortiGuard services, their expiration dates. When you hover over it, the See More will make you jump to System.
|2. System Resources||Shows the percentage utilization of CPU, RAM, and Disk by the ADC. Hover over it to see the usage for a particular time stamp.|
|3. VS Status||Shows the status of the virtual servers for this particular ADC. Hover over it to see the number of devices that are, for example, 'healthy,' or 'unhealthy.'|
|4. Log Summary||
Shows information received from the logs of this particular ADC. Hover over it to see the number of Logs that are in, say, 'warning.' Also hover over it to go into Global Repository > Log. This is a comprehensive page that shows all the logs for not just this ADC, but every ADC connected to the Manager.
Emergency—The system has become unstable.
Alert—Immediate action is required.
Critical—Functionality is affected.
Error—An error condition exists and functionality could be affected.
Warning—Functionality might be affected.
|5. VS Throughputs||Shows how much traffic is coming into the VS's of the ADC and how much is going out. Hover over it to see the time stamp.|
The Server Load Balance>Logical Topology page uses the tree-view format to show the internal configuration of each virtual server on the FortiADC. See the FortiADC Handbook for more information.
Under Service, gives 'at a glance' information about Virtual Server, Real Server, and Health Check.
To configure a virtual server, see the Create New button on the top right. Follow the steps detailed in the Virtual Server section of the FortiADC Handbook. You can ignore the bottom half of the guide, which deals with advanced configuration. Essentially, you are configuring a virtual server from within the Manager.
You can also create a real server inside the VS. This real server will show up below, on the same page, under Real Server.
To configure a real server, click the Create New button on the top right. Follow the steps detailed here in the Real Server section of the FortiADC Handbook.
Displays status of health checks. For more information, see the Health Check section of the FortiADC Handbook.