Static NAT — Ensures delivery of specific traffic to a particular server on the internal network. For example, LinkProof uses Static NAT, meaning predefined addresses are mapped to a single internal host to load balance traffic to the host among multiple transparent traffic connections. This ensures that the return traffic uses the same path and also allows traffic to that single host to use multiple ISPs transparently. You assign multiple Static Smart NAT addresses to the internal server, typically one for each ISP address range.

Dynamic NAT — Enables LinkProof to hide various network elements located behind LinkProof. Using this feature, LinkProof replaces the original source IP address and source port of a packet that is with the configured NAT IP address and a dynamically allocated port before forwarding the request to the group. The network elements whose addresses are translated can be servers or other local hosts. You can set different NAT addresses for different ranges of intercepted addresses.

No Nat — Enables a simple configuration where internal hosts have IP addresses that belong to a range of one of the group servers.

Select a data center based on the geographical location of the client (GSLB). The selection is made via the DNS Rule Network metric:

The DNS Network metric now lets you define the network using the legacy range or a Network Class (either the IP or Region type).

In addition, the selection can be made based on the geographical location of the DNS client (LDNS) or on the geographical location of the actual client, if its IP address is present in the DNS request (EDNS0 extension).

Select a link based on the geographical location (LinkProof):

For inbound traffic, the selection is made based on the geographical location of the client. The selection is made via a DNS Rule Network metric (the same as for GSLB).

For outbound traffic, the selection is made based on the geographical location of the destination

Provide different services based on the user’s geographical location. For example:

Traffic from French customers should go to group of servers that have French content.

Response traffic to a customer from Afghanistan should be compressed due to high latency.

Block traffic from/to certain countries.

Enforce different bandwidth/rate limits per geolocation.

rdwr-cookie name – Retrieves the name configured for the cookie.

rdwr-cookie site-ip <value> – Retrieves the site IP identifier from the value of the persistency cookie inserted by Alteon (relevant only for cookie insert persistency mode).

Quick Application Setup do not work with this extended ID length and currently work only with a maximum ID length of 32 characters.

The DPM dashboard only displays short IDs that are not longer than 50 characters.

APM can be enabled on a service where its virtual service ID

does not include a period (‘.‘)

contains up to 245 characters

SNMP supports an OID of a maximum 128 digit length, including the parameter OID and the key. Alteon implements a special mechanism that lets you browse the table (GetNext), Get a specific object, or change (Set) a specific parameter.

However, you cannot create a new object with a long ID via SNMP.

When configured long IDs, some audit log messages might be displayed distorted

From WBM ─ Configuration perspective > system > Management access > Management protocol > HTTPS

From CLI─ /cfg/sys/access/https

Note: In a virtualization environment on a VX WBM, setting intermediate certificate for management connection is not available. Workaround is to use the CLI for this setting. (DE18454)

From WBM ─ Application Delivery > Server Resources > Health Checks.

From CLI ─ cfg/slb/advh/cert