Applies To:

Show Versions Show Versions

Manual Chapter: Performing Initial System Configuration
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

If you have followed the instructions in Setting Up the VIPRIONTM Platform, you should now have the following items:
A license for the BIG-IP® system software
A cluster named default that contains four cluster members (that is, slots)
With this setup, you are now ready to perform additional configuration tasks so that the VIPRIONTM system can process application traffic, and if you have a redundant system configuration, remain available in the event of failover. These configuration tasks consist of creating various BIG-IP system objects on the system. Specifically, the objects you create are:
The VIPRION system creates these configuration objects on the primary blade, and then the cluster synchronization process automatically propagates the configuration objects to those other blades.
If you have implemented a redundant system configuration, the standby cluster is capable of processing traffic in the event that the active cluster becomes unavailable.
The VIPRION system provides the flexibility you need to deploy the system in almost any physical or logical networking environment. For simplicity, however, the remainder of this chapter contains the procedures for implementing the most common configuration:
The first procedure involves configuring BIG-IP system objects on the cluster, for processing application traffic. If you have a redundant system configuration, you must perform these configuration tasks on both units of the configuration. For more information, see Setting up the system to process application traffic.
The second procedure pertains to redundant system configurations only, specifically with respect to configuring an additional VLAN to use for failover between clusters. Again, if you have a redundant system configuration, you must perform this configuration task on both units of the redundant system configuration. For more information, see Setting up VLANs for redundancy.
To process application traffic, you must first configure some BIG-IP system network objects, such as VLANs, self IP addresses, and trunks, and then some local traffic objects such as a virtual server and a load balancing pool.
Important: F5 Networks recommends that you assign a management IP address to each cluster member (slot), and that you cable the management interface on each blade to the management network. This ensures that whenever the blade with the primary designation changes, you can still access the cluster using the cluster IP address. For information on assigning management IP addresses to cluster members, see Chapter 3, Managing Clusters.
The first set of tasks consists of configuring some BIG-IP system objects, namely an external and an internal trunk, an external and an internal VLAN, and a self IP address for each VLAN.
Figure 2.1 shows the resulting configuration.
Important: Before you perform the following procedure, F5 Networks recommends that you read some background material on BIG-IP system VLANs, trunks, and self IP addresses. You can find this information in the most recent version of the BIG-IP® Network and System Management Guide.
1.
On the peer (vendor) switch on the external network, create a trunk that includes the four external interfaces to which you have physically connected the external interfaces of the four blades.
Note: If the peer switch is configured to use Link Aggregation Control Protocol (LACP), you must enable LACP.
a)
On the Main tab of the navigation pane, expand Network, and click Trunks.
The Trunks screen opens.
b)
At the upper right corner of the screen, click Create.
The New Trunk screen opens.
c)
Assign the name trunk_ext, and assign an external interface of blade 1 to the trunk.
e)
Click Finished.
4.
a)
On the Main tab of the navigation pane, expand Network, and click VLANs.
The VLANs screen opens.
b)
On the upper right corner of the screen, click Create.
The New VLAN screen opens.
c)
Configure a VLAN named external, assigning trunk_ext as an untagged interface.
d)
Click Finished.
a)
On the Main tab of the navigation pane, expand Network, and click Self IPs.
The Self IPs screen opens.
b)
At the upper right corner of the screen, click Create.
The New Self IP screen opens.
c)
In the IP Address box, type an IP address.
d)
In the Netmask box, type a netmask for the IP address.
e)
From the VLAN list, select external.
f)
Click Finished.
6.
On the Main tab of the navigation pane, expand Network, and click Interfaces.
The Interfaces screen opens.
7.
Verify the status of the blade 1 external interface.
The interface (link) assigned to trunk_ext should appear as UP.
b)
On the VIPRION system, create a trunk named trunk_int that includes one of blade 1s internal blade interfaces.
c)
Create an internal VLAN named internal, assigning trunk_int as an untagged interface.
After configuring the VLANs, self IP addresses, and trunks, you can configure one or more virtual servers and their associated load balancing pools. For information on configuring these objects, see the Configuration Guide for BIG-IP® Local Traffic Management.
By now, you have configured the BIG-IP system objects required for processing application traffic. If you have a redundant system configuration, you have configured an additional VLAN, with a self IP address, that the two units can use for failover communication.
The system ensures that the configuration data is synchronized to all blades in the cluster. This synchronization process occurs immediately after you perform each configuration transaction on the primary blade.
Figure 2.2 shows the effect of cluster synchronization on a second blade within the cluster. The figure shows that the system has propagated the configuration data of the primary blade to the secondary blade.
The system is now ready to process application traffic. Whenever you make configuration changes to the cluster in the future, the system automatically ensures that those changes are synchronized across all blades in the cluster.
If you are planning to set up a redundant system configuration (that is, cluster-to-cluster failover capability), F5 recommends that you create an additional VLAN on each system of the redundant system configuration. This additional VLAN is used for the two clusters to communicate with each other before, during, and after failover. Note that you can create a trunk to assign to this VLAN, rather than assigning individual interfaces.
You can then create a self IP address for the new VLAN. Use the following procedure to create this VLAN and its self IP address. After you have followed this procedure, and cluster synchronization has occurred, the system is ready to fail over if the active cluster becomes unavailable in the future.
1.
On the Main tab of the navigation pane, expand Networks, and click VLANs.
The VLANs screen opens.
3.
Configure a VLAN named HA, assigning the interface or trunk that the VLAN will use to communicate with its peer before, during, and after failover.
You assign this interface (or trunk) as an untagged interface.
4.
Click Finished.
5.
On the Main tab of the navigation pane, click Self IPs.
The Self IPs screen opens.
a)
At the upper right corner of the screen, click Create.
The New Self IP screen opens.
b)
In the IP Address box, type a unique IP address.
Note: This self IP address does not need to be a floating IP address.
c)
In the Netmask box, type a netmask for the IP address.
d)
From the VLAN list, select HA.
e)
Click Finished.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)