Applies To:

Show Versions Show Versions

Manual Chapter: Creating a Device Template for an AWS Cloud
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Creating a Device Template for an AWS Cloud

What details are needed in a device template for AWS?

There isn't much you need to configure for an AWS device template. Just identify the correct port and NTP server to use, and then specify the admin credentials and you are all set.

Before you create a device template for a service scaling group

This is a list of things you'll need to set up your device template for auto-scaling BIG-IP VE devices.

Before you create your device template, you might want to gather some, or all, of the following information specific to creating the BIG-IP VE devices that deploy to the service scaling group (SSG). These things include:
  • If you want to specify the port for communication between BIG-IQ and the BIG-IP VE devices, determine what you want to use.
  • The licenses to use for licensing new BIG-IP VE devices.
  • The NTP server and timezone you want the BIG-IP VE devices to use.
  • The lookup server IP address, host name, or FDQN of the first DNS to use, as well as the NTP server and timezone you want the BIG-IP VE devices to use.
  • The VLAN interface for the virtual or physical port to connect the BIG-IQ to your managed devices, an optional tag you want to use in the packet header of this VLAN, and an optional frame size (MTU).
  • The self IP addresses you want to use for the BIG-IP VE devices as well as the port lockdown settings. If you use an IP pool alias, you'll need to get the one you specified for your cloud environment, because they must be the same.
  • Static route settings you want to use for newly-created BIG-IP VE devices. These routes are displayed in the destination column of your routing table.
  • Set up the admin user credentials to access the devices in the SSG.
    Note: If you're using local authentication with a password enforcement policy, you'll have to meet the criteria it specifies for the admin account you created for accessing BIG-IP VE devices.

Create a new device template for AWS

Before you start creating your template, it's a good idea to gather any details you might need for the template property objects.


You create a new device template to specify settings AWS applies to devices in the service scaling group (SSG).

  1. At the top of the screen, click Devices then, on the left, click DEVICE TEMPLATES.
  2. Click the Create button.
  3. After you name this template, click the Add/Remove button. Select the objects you want to add, and click OK.

    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. The table lists the object types you can configure along with details about how the SSG uses those details.

    Object This is where you specify: Notes
    Configuration

    You can specify a management port for communication between BIG-IQ and the BIG-IP VE devices in the SSG.

    By default, port 8443 is used, but you can configure a different port if needed.

    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.
    User accounts

    The username you specify for devices in a service scaling group must be admin.

    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.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.

Additional Comments (optional)