Previous Topic: Configuration OptionsNext Topic: Backbone LAN Parameters


Grid Parameters

These parameters are different for each grid on the Backbone LAN and are usually (but not necessarily) specified directly on the command line.

grid_id

This parameter is specified as two integers, in the form M/N. The M value must always be 1. The N value must be an integer between 1 and 31 inclusive. The grid_id is used as part of the name of virtual machines belonging to a specific grid.

grid_desc

Free text description of the grid. Optional.

Default: (empty)

controller_name

(Optional) Specifies the DNS name for the grid controller (for example, grid1.3tera.net). If empty, the controller_ip IP address is used instead.

Default: Empty

Note: For all commands except new, this parameter identifies the grid that you want to access. To modify the controller_name setting with the set command, use new_controller_name= the-new-name.

controller_ip

Specifies the IP address for the grid controller (for example, 172.24.213.111). This parameter is mandatory for the 'new' command.

Note: For all commands except new, this parameter identifies the grid that you want to access. To modify the controller_ip setting with the set command, use new_controller_ip= the-new-address.

ips

Specifies the IP addresses available for use by applications. This value is a comma-separated list of IP address ranges. Up to eight ranges can be specified. Each range has one of the following formats: [pri+]range[/(prefix[+gateway]] or [pri:]range[/(prefix[:gateway]]. The two formats differ only in the field separator (: or +). Use the + separator when specifying IPv6 ranges because : is used as a syntax element in the IPv6 address itself.

For IPv4 addresses range can be specified either as a.b.c.d-A.B.C.D, or as a.b.c.d-N. The latter form is treated as if a.b.c.d-a.b.c.N was specified.

For IPv6 addresses, range is specified as addr1-addr2. The addresses are specified in the standard IPv6 notation: 8 words of 16 bits in hexadecimal notation, with colons as separators. Contiguous zero words can be abbreviated with the zero-fill token ::, for example, ::30 is expanded to 0:0:0:0:0:0:0:30. prefix is either a CIDR prefix (1..31 or 1..128 for IPv6) or a netmask, in the decimal IP address form (a.b.c.d). The netmask form can be used only with IPv4 ranges; for IPv6 only a CIDR prefix is valid. Specifying a prefix is optional. If omitted, it is assumed that all addresses are 'local' (proxy-ARP setup). If the prefix is set with no gateway (see later), then the IP range is 'closed'. The range can be used only to communicate between appliances on the grid.

gateway specifies a default gateway for the IP range.

The pri: prefix can be added to identify an IP range as "private". The normal (public) IP ranges are intended for use by applications to communicate with the public Internet. They contain valid unique IP addresses routed to the grid public LAN. The private ranges are for use by applications on the same grid to communicate with each other and are not necessarily routable. Both "public" and "private" IP addresses in this context refer to IP addresses used on the grid's external (public-facing) network. Communications between components of the same application over the grid backbone network are managed internally and automatically by CA AppLogic® for System z. Currently, there is no support for using the backbone for communication between separate applications on the same grid.

The ips= setting is mandatory, at least one IP range must be specified. CA AppLogic® for System z restricts incoming and outgoing traffic to the external network to packets that have a destination or source address in the specified ranges. An application that accidentally or deliberately uses an address outside of the allowed ranges is not able to communicate. The assigned IP address ranges are also displayed on the controller dashboard.

Example: ./aldo set grid=mygrid ips=1.2.3.2-9/24:1.2.3.1 (application IP range: 1.2.3.2-1.2.3.9, netmask=255.255.255.0, and gateway: 1.2.3.1)

new_grid

Specifies a new grid name. Use this parameter with the set command. Similar to the controller_ip and controller_name parameters, the grid= parameter is used to identify the grid, not to change a setting.

account_id

Specifies the account name that is assigned to the grid administrator by CA Technologies. This setting is required when installing a new grid and it must be a valid name that is registered in the CA Technologies user database. The ID is checked before installation, together with the account_key (see later).

account_key

Specifies the name of a file containing a private SSH key identifying the user account. This setting is required to install a new grid and the specified key must be valid. When changing the account assigned to an existing grid with the aldo set command, both account_id and account_key must be specified.

tag

(Optional) Specifies a grid billing tag. This value is a free-form printable text that you want to include in all billing reports that this grid generates. The tag can be used to add keywords to the billing reports. Tagging facilitates organizing reports from multiple grids by using customized searches through the billing data.

app_dns1, app_dns2, and app_dns3

Define the name servers for use by applications. These values are informational only, and are displayed with the application IP ranges (see ips earlier) on the grid dashboard. If not specified with the new command, they are filled in from the data that is specified for the grid controller (the ext_dns* values).

Note: Changing the ext_dns values on an existing grid does not automatically update the app_dns values displayed on the dashboard.