A10 Application Delivery Controller (ADC) Load Balancer

Details

Support: Level 2

Connecting to SIP

FireMon strives to provide up-to-date product information, however we are not always aware when vendors change their device UI. If any Configure the Device procedure differs from your device version (UI location of fields, not information needed), please consult your device's user guide.

To add an A10 ADC Load Balancer device, complete the following steps.

Step 1: Configure the Device

The A10 device is a CLI-based retrieval over SSH port 22 and does require both username and enable username credentials.

  • You will need to create a user account for both.

  1. Log in to the A10 dashboard.

  2. Click System > Admin >Users tab.

  3. Click Create to add an admin user account.

    1. Enter a Username and Password.

    2. Select Access of CLI, Web, and aXAPI.

    3. Select a Trust Host of IPv4 Address.

    4. Select a Privilege Type of Global.

    5. Select a Privilege of Read/Write/HM.

    6. Click Create.

  4. Repeat the steps above to create the Enable account, but set the Privilege to Read.

Below are the retrieval commands used for off offline configuration retrieval.

Command Saved to RAW File

show admin detail

 users
show interfaces interface
show running-config running-config
show interface management interface-mgmt
show slb template applications
show partition partition-info
show ip route all route
show ip route mgmt route-mgmt
show ipv6 route ipv6-route
show access-list access-list

 

Step 2: Onboard the Device in the Administration Module

Contact FireMon Support to receive a specific device pack (a .jar file) if it was not included in the FMOS GA release. Review the steps to upload a device pack.

After onboarding, if you change any device settings, confirm that those updates were automatically applied to the discovered devices.
  1. On the toolbar, click DeviceDevices.
  2. Click Create, and then click A10 > ADC.
  1. General Properties section.
To prevent errors in device group-level device maps and incorrect reporting data, all devices added in Administration must have unique IP addresses. If devices with duplicate IP addresses must be added within a domain, it is strongly recommended that those devices be separated into discrete device groups, where no duplicate IP addresses are included in the same device group. Devices with duplicate IP addresses will cause errors in the All Devices device map, and may cause incorrect data in reports, even if they are in discrete device groups.
  1. In the Name box, type the name of the device as you want to see it in SIP.
  2. In the Description box, type an optional description of the device being added.
  3. In the Management IP Address box, type the IP address of the device.
  4. In the Data Collector Group box, select the IP address of the data collector group that will collect data from this device.
  5. In the Central Syslog Server box, select the syslog server from the list (optional).
Syslog fields are optional if the device uses the same IP for syslog and management.
A central syslog server is required only if syslog messages come from a different IP. A central syslog server must be created before it can be assigned to a device. To track usage via syslog, the device must support Level 3+.
  1. In the Syslog Match Names box, type the syslog match name (optional). You can enter multiple comma-separated names.
  2. By default, the Automatically Retrieve Configuration checkbox is selected.
  3. In the External ID box, type a unique identifier to be used when the device identifier is different than what is displayed in SIP.
  1. Collection Configuration is enabled on the management station or by duplicating and then editing the default configuration (Device > Collection Configuration). Default is what is set on the installed device pack.
  1. Device Settings section.

Credentials

  1. In the User Name box, type the administrator user name that was created during device configuration.
  2. In the Password box, type the administrator password that was created during device configuration.
  1. In the Enable User Name box, type the user name that is used to log into “read” mode, which restricts administrative access to this device.
  1. In the Enable Password box, type the password that is used to log into “read” mode, which restricts administrative access to this device.

Retrieval

  • By default, the Protocol is SSH and the Port is 22.

  1. Monitoring section.

Log Monitoring

Select the Enable Log Monitoring checkbox to use for Rule Usage Analysis.

  • Track Usage Via is set to Syslog.
  • Log Update Interval is set to 10 (minutes); this number determines how often usage data is sent to the application server.

Change Monitoring

Select the Enable Check for Change checkbox to enable checking for configuration changes after the specified interval, and perform a retrieval if changes are detected.

  • Enter an optional Alternate Syslog Source IP.

  1. Advanced section.

  • File Retrieval Options: Select the Use Batch Config Retrieval checkbox only if you are manually sending configurations for this device via your data collector's batchconfig directory. While this option is enabled, online retrievals will be disabled.

  • SSH Key Options: Select the Automatically Update SSH Keys checkbox if you want the data collector to automatically update the SSH key for a device when a conflict occurs.

  1. Enforcement section.

Select an Enforcement Option from the list:

  •  Allow All: All automation is allowed (enforcement, change, manual).

  • Manual Only: When selected all changes must be manually pushed for this device.

  •  Prevent All: No automation is allowed.

  • Window Only: Automation can only take place in the assigned enforcement window.

If this device is assigned to an enforcement or change window, it will be listed. If no assignment, changes must be manually pushed for this device.

  1. Supplemental Routes section.

Supplemental routes cannot be added until after a retrieval normalizes successfully. You can perform a manual retrieval before continuing.

  1. Click Add.

  2. Complete fields in the Add Supplemental Routes dialog box:

  • Select an Interface.
If you select an Interface, you will not need to select a virtual router and next virtual router. If no interface is selected, you will need to select a Virtual Router and Next Virtual Router.
  • Type the Destination IP address.
  • Type the Gateway IP address.
  • Select a Virtual Router.
  • Select a Next Virtual Router.
  • Switch the Drop toggle to enable (disabled = Accept).
  • Click Add.

  1. Click Save.

Step 3: Verify Communication

Because automatically retrieving a configuration is enabled by default, there is nothing for you to do. Security Manager will automatically attempt to retrieve a device configuration.

To do a manual retrieval, select the device row, click the Menu icon and then click Retrieve Configuration.

It may take up to 15 minutes to see the status result of the retrieval.