Manual Chapter : Optimizing Configuration Management with Templates

Applies To:

Show Versions Show Versions

BIG-IQ Centralized Management

  • 6.0.1
Manual Chapter

Optimizing Configuration Management with Templates

About configuration templates

BIG-IQ® can manage multiple devices simultaneously. These devices can be located in several data centers that may be located in many different locations. To help you easily manage required configuration changes to DNS, NTP, SMTP, and Syslog for a large number of devices, you can use configuration templates.
To start, you create a configuration template, then deploy that template to certain devices. This can save a significant amount of time because you are not required to log in to each device individually to make configuration changes.

Create a device template for auto-scaled BIG-IP VE devices

You create a new device template to specify a base configuration to create devices in a service scaling group (SSG). When you deploy the SSG, BIG-IQ uses the device template settings to create new virtual devices in your cloud environment.
  1. At the top of the screen, click
    then, on the left, click
  2. Click the
  3. After you name this template, click the
    button. Select the objects you want to add, and click
    The system adds the objects to the template. A yellow circle displays next to each object to let you know that you need to provide an initial value.
    This is where you specify:
    The text for a hostname prefix and/or suffix to help you identify new BIG-IP VE devices in the you cloud environment.
    The default route and management port used to communicate between BIG-IQ and the BIG-IP VE devices in the SSG.
    You must configure a hostname so that you can identify issues revealed through device specific analytics.
    You can use any port except for 8443.
    Specific license pool you want to use to license new BIG-IP VE devices.
    You must specify a license pool for the devices in an SSG.
    Components you want installed on new BIG-IP VE devices.
    You must at least select Local Traffic Manager (LTM). You also need Application Visibility and Reporting (AVR) so that analytic data from your devices can trigger scaling events.
    DNS & NTP
    Details about the lookup and NTP server settings and time zone.
    You must specify an NTP server so all of the devices in the SSG have the same time reference. This must be a server that has the same time as the managing BIG-IQ system.
    Management IP
    Select an IP pool from the menu, then select an option:
    If you select an
    IP Pool
    IP Pool Alias
    , type the alias of the IP pool.
    If you select
    , the DHCP service on that network will provide an IP address. 
    If you select an
    IP Pool
    IP Pool Alias
    , you'll the VMware tools installed for the template. Refer to the following article for instructions:
    Interface for the virtual or physical port to connect BIG-IQ to your managed devices.
    Optional tag you want to use in the packet header of this VLAN and Optional frame size (MTU).
    You must specify a VLAN for the devices in an SSG.
    By default, BIG-IP devices use the standard Ethernet frame size of 1518 bytes (1522 bytes if VLAN tagging is used) with the corresponding MTU of 1500 bytes. For BIG-IP devices that support Jumbo Frames, you can specify another MTU value.
    IP address and VLAN details, including port lockdown options.
    You must specify self IP addresses for the devices in an SSG.
    You must specify self IP addresses for the devices in an SSG.
    Do not remove or rename the external self IP or application deployments to this SSG will fail.
    For an IPv4 address, you must specify a /32 IP address per RFC 3021. You must type the full netmask. Specifying the prefix length in bits is not supported.
    If you use an IP pool for your self IP addresses, the pool name you specify in the template must match the name you specify when you configure the VMware environment.
    Static route settings for new BIG-IP VE devices.
    For destination, you can use the self IP address for this route. It displays in the destination column of the routing table
    Root account
    Root user account for new BIG-IP VE devices.
    It is good practice to provide root access so that you can access the devices for troubleshooting.
    User accounts
    Select the role and specify a user name and password for users you want to provide access to new BIG-IP VE devices.
    In addition to alphanumeric input, you can use all punctuation characters for the password.
    Or, if you are using local authentication and have created a
    password enforcement policy, the password must meet the criteria specified in the password enforcement policy.
When you finish defining your new template, you can use it to create a new application that deploys to your BIG-IP devices.

Deploying a configuration template to managed devices

You must create a configuration template before you can deploy it to a managed device.
Deploying a configuration template saves time when you want to make a similar change to several managed BIG-IP devices.
  1. At the top of the screen, click
  2. On the left, click
  3. Near the top of the screen, click the
  4. From the
    Config Template
    list, select the template you want to deploy.
  5. In the
    Deployment Name
    field, specify the name for this configuration template deployment.
  6. From the
    list, click the devices you want to deploy the configuration template to, and then click
    to move it to the
  7. Click the
    button at the bottom of the screen, navigating to the components required for this template, and specifying the configuration.
  8. Click the
BIG-IQ applies this configuration to the specified BIG-IP devices.