After hardware installation is completed, you are ready to create a basic BIG-IP® software configuration.
The first step in configuring the BIG-IP software is to run the Setup utility to perform tasks such as activating the BIG-IP system license and provisioning BIG-IP modules. You then set up a base BIG-IP system network consisting of trunks, VLANs, and self IP addresses, as well as a management IP address for each blade in the VIPRION® cluster. You also define your Domain Name System (DNS) servers and your NTP servers.
This illustration shows a basic VLAN and trunk configuration for a standalone VIPRION system. In the illustration, the VIPRION chassis is configured with a cluster containing two active blades. Note that each VLAN consists of two interfaces, one per slot. After setting up this basic configuration, you can adjust the configuration later as needed.
Basic VLAN and trunk configuration on a VIPRION system
During VIPRION® setup, before you provision the system, you must decide:
The total disk space that the system normally allocates to vCMP is determined by the size of each application volume (one per blade) that the system creates during vCMP provisioning.
By default, the BIG-IP system allocates all but 30 gigabytes of reserve disk space per blade to vCMP. Reserve disk space is the amount of disk space that the system reserves for other uses during provisioning, such as for installing other versions of the BIG-IP® system in the future. The reserved disk space also protects against any potential resizing of the file system.
Before you begin, confirm that you have done the following:
For VIPRION® platforms, F5 Networks® strongly recommends that you create a trunk for each of the BIG-IP® system internal and external networks, and that each trunk contains interfaces from all slots in the cluster.
For example, a trunk for the external network should contain the external interfaces of all blades in the cluster. Configuring a trunk in this way prevents interruption in service if a blade in the cluster becomes unavailable and minimizes use of the high-speed backplane when processing traffic.
Also, you should connect the links in a trunk to a vendor switch on the relevant network.
For the most basic BIG-IP® system configuration with redundancy enabled, you typically create multiple VLANs. That is, you create a VLAN for each of the internal and external networks, as well as a VLAN for high availability communications. You then associate each VLAN with the relevant interfaces of all cluster members on that network.
For example, for a system with a two-slot cluster, you might associate the external VLAN with interfaces 2.1/1 and 2.1/2, where 2.1/1 is on slot 1 and 2.1/2 is on slot 2.
If your hardware platform supports ePVA, you have the additional option of configuring double tagging (also known as Q-in-Q tagging) for a VLAN.
VLANs represent a logical collection of hosts that can share network resources, regardless of their physical location on the network. You create a VLAN to associate physical interfaces with traffic destined for a specific address space. For the most basic BIG-IP® system configuration with redundancy enabled, you typically create multiple VLANs. That is, you create a VLAN for each of the internal and external networks, as well as a VLAN for high availability communications. If your hardware platform supports ePVA, you have the additional option of configuring double tagging (also known as Q-in-Q tagging) for a VLAN.
When you do not intend to provision the vCMP® feature, you typically create self IP addresses when you initially configure the BIG-IP® system on the VIPRION® platform.
If you plan to provision vCMP, you do not need to create self IP addresses during initial BIG-IP configuration. Instead, the host administrator creates VLANs for use by guests, and the guest administrators create self IP addresses to associate with those VLANs.
A self IP address that you create within a guest enables the guest to route application traffic through the associated VLAN or VLAN group. On vCMP systems, a guest administrator creates self IP addresses and associates them with VLANs created on the host that a host administrator published to the guest during initial guest creation.
For example, you can type 255.255.255.0.
After you perform initial BIG-IP ®configuration, you have a standalone VIPRION® system that contains these configuration items:
After the VIPRION® is configured with a base BIG-IP® network, the next step depends on whether you intend to use the vCMP® feature:
For more information on configuring the vCMP feature, BIG-IP product modules, and redundancy, access the F5 Networks® Knowledge web site at http://support.f5.com..