Fortinet FortiADC Load Balancer

Fortinet FortiADC is Application Delivery Controller (ADC) that ensures application availability, application security, and application optimization. FortiADC can be deployed as a physical or virtual machine (VM) or as a Cloud solution.

Load balancer model

The FortiADC pattern builds the BMC Discovery load balancer model based on additional details obtained via REST API calls for the following configured items:

Virtual Servers (API path /api/load_balance_virtual_server)
Pools (API path /api/load_balance_pool)
Real Servers (API path /api/load_balance_real_server)

Virtual Servers are modeled as Load Balancer Services, Pools are modeled as Load Balancer Pools, and Real Servers are modeled as Load Balancer Members.

Any configuration no longer reported is removed from the model.

To fully discover Fortinet FortiADC Load Balancer, the following credentials should be configured:

SNMP credentials to discover the FortiADC device itself
Fortinet FortiADC REST API credentials to discover the Load Balancer model elements.

The examples of the credentials in the Discovery user interface:

Triggers

Pattern	Trigger node	Attribute	Condition	Argument
FortiADC	NetworkDevice	vendor	=	"Fortinet"
		model	matches regex	"^FortiADC\b"

Modeled Components

Load Balancer instance

The pattern creates a Load balancer instance with the following attributes:

Attributes	Value
key	"%device.key%/Fortinet FortiADC"
type	"Fortinet FortiADC"
version	FortiADC version
name	"Fortinet FortiADC %version% on %device.name%" or "Fortinet FortiADC on %device.name%" if the version is missing

Load Balancer service

The pattern creates a Load balancer service with the following attributes:

Attributes	Value
key	"%lb_instance.key%/%lb_service_name%/%lb_service_port%"
name	Service name
ip_addr	Service IP address
port	Service port
dns_names	Service DNS name, if available
state	Service state, if present: "Healthy" "Unhealthy" "Dead" "Init"
status	Service status, if present: "Enable" "Disable" "Maintain"
type	Service type: "Layer 2" "Layer 4" "Layer 7"
profile	Service profile name
scope	Discovery scope, if present
description	Service description, if available

Load Balancer pool

The pattern creates a Load Balancer pool with the following attributes:

Attributes	Value
key	"%lb_instance.key%/%lb_pool_name%"
name	Pool name
state	Pool state, if present: "Healthy" "Unhealthy" "Dead" "Init"
type	Pool type, if present: "Static" "Dynamic"
address_type	Address type of the pool, if present: "IPv4" "IPv6"

Load Balancer member

The pattern creates a Load Balancer member with the following attributes:

Attributes	Value
key	"%lb_instance.key%/%lb_member_name%/%lb_member_port%"
ip_addr	Member IP address
port	Member port
name	Member name
status	Member status, if present: "Enable" "Disable" "Maintain"
type	Member type, if present: "Static" "Dynamic"
scope	Discovery scope, if present
fqdn	Member FQDN, if available