Setup guide

If you change the number of virtual interfaces on the BIG-IP VE system after a binary MCPD database

has been created, the system does not detect the change when subsequently rebooted. To ensure that the

system properly detects the new or removed interfaces, type the command rm /var/db/mcpd* at the

BIG-IP VE command prompt, and reboot the system.

HA events due to BIG-IP VE inactivity

If the VMware hypervisor runs the BIG-IP VE software for fewer than four minutes continuously (for

example, due to a manual suspension or the timeout of network disk I/O), high-availability failure events

occur. The system might note a failure and restart key system processes and trigger failover if within a

high-availability (HA) group. This is intended system behavior.

VMware vSwitch Promiscuous Mode

When the VMware vSwitch Promiscuous Mode is set to Reject, the VLAN group transparency mode,

Opaque, will not be able to pass packets.

Virtual network interface status is wrong

The BIG-IP VE system reports the status of host-only network interfaces as UNINITIALIZED, even

though the interface is functioning normally.

Auto-licensing and the default management route

If you have not dened a default route to the management port, the default interface 1.1 is used, which

does not work. To prevent this from occurring, verify that you have dened a default route for the

management port before attempting to activate a license.

BIG-IP licensing and User Configuration Sets

When you import a User Conguration Set (UCS) from another BIG-IP system or BIG-IP VE system,

the system overwrites the local license with the license contained in the UCS. To work around this issue,

you can re-license the local system after importing the UCS by accessing a backup copy of the license

le, located in /config/bigip.license.bak. Also, when importing a UCS, ensure that the host

names of the two systems differ. When the host names differ, the system correctly imports only the

conguration data that is common to both the originating platform and the target platform. If the host

names match, the system attempts to import all of the UCS conguration data, which can cause the

import process to fail.

Use of SNMP OID for RMON tables

Setting the source OID for RMON alarm, event, and history tables generates an error message. This

OID will be disabled in future releases.

Media speed messages in log file

When starting the BIG-IP VE system or when removing an interface from a VLAN, the system logs

media-related messages to the le /var/log/ltm. You can ignore these messages.

The virtual switch clears the QoS field in 802.1q headers

A hypervisor's Layer 2 bridging device might remove quality of service (QoS) classication from

packets.

BIG-IP

Virtual Edition Setup Guide for VMware ESX

or ESXi