Default Aggregation 131

Selecting the Default Aggregation Action

The default aggregation action is the method of aggregation applied to network devices which have a DNS name, but which are not contained within one of the local DNS domains.

There are three default aggregation actions, from which you can select and apply one to non-local DNS domains. In the following examples, it is assumed that acme.com is not in the Local Domain Specification.

Automatic This describes the “standard” default aggregation action. Traffix Manager builds up a tree of DNS domains for aggregation purposes.

When aggregation becomes necessary, all devices in each of the lowest DNS domains will be aggregated into a single device, to represent each domain. For example, all devices in the domain engineering.acme.com are aggregated into a single device, representing engineering.acme.com.

When all domains at this lowest level have been aggregated, Traffix Manager then aggregates each domain at the next level. Following this example, engineering.acme.com and office.acme.com are both aggregated to acme.com.

You cannot undo aggregation. If you add an aggregated DNS domain to a local domain, all newly discovered addresses will be mapped to the (aggregated) representative device.

The two default aggregation actions described below provide you with control over how devices are aggregated. However, if the maximum device limit is reached and the default action is not automatic, automatic aggregation is attempted, to make room for new local devices.

Aggregate at DNS Layer By selecting this option you specify a DNS layer and a direction. This direction can be either From name, or From tail.

Aggregate from name allows you to specify any layer above the name of the device.

If layer 1 above the name is selected, the device office.acme.com is aggregated into the device representing the DNS domain acme.com.

Page 131
Image 131
HP Transcend Traffix Manager manual Selecting the Default Aggregation Action