At AppNexus every customer has a private VLAN, or Virtual Local Area Network in each datacenter where they operate equipment. Your VLAN is a list sequential of IP addresses that can be assigned to the instances you launch on the AppNexus system. VLAN can consist of 8, 24, 56 or 120 IP addresses (eight addresses in each range are reserved for networking equipment so they can act as if belonging to an individual VLAN). This VLAN provides security by segregating each customer's traffic from AppNexus and other customers' traffic and controlling traffic from the Internet via customer-controlled Access Control List (ACL).


If you run out of IP addresses in your VLAN.

Assignment of new VLANs could take up to workday, as it involves changes in ACL rules for all your VLANs.  As we assign second VLAN temporarily (just for the migration time), you'll have to migrate instances from the old VLAN to the new one.  This doesn't require instance downtime, you'll get detailed instructions on the migration from Support when second VLAN is created.

We will have an API for ACLs. Also the portal.
Relevant tickets: #4128 /#4625/#3952

What about instructions:

1. When you launch new instance, please use "--ip" flag of "manage-instance launch" command to explicitly declare IP address of instance in new address block. – Really it'll be part of instruction – Vladimir

Meanwhile I'll prepare instructions on how to deal with multi-VLAN environment, how to migrate instances from old IP space to the new one with the existing API/CLI functionality, et cetera. – Actually Alexander Novitskiy is communicating with GiftReal (RT:5483) and OpenAds (RT:5118) on this.

Assigning IP addresses from your VLAN

manage-instance launch --name, --cpu-units, --server-id, --memory, --disk, --share-name,
--path, --ip, --upload, --authorized-keys, --async

Further Reading