Bug ID 622133: VCMP guests may incorrectly obtain incorrect MAC addresses

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP vCMP(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
13.0.0, 12.1.3, 11.6.2

Opened: Oct 12, 2016
Severity: 3-Major

Symptoms

vCMP guests may be re-configured to use MAC addresses based off an all zero MAC address (00:00:00:00:00:00). The 'tmsh show net vlan' command will show the vlan interfaces having mostly 0's in the MAC address: ------------------------------------- Net::Vlan: external ------------------------------------- Interface Name external Mac Address (True) 00:00:00:00:00:01 MTU 1500 Tag 3702 Customer-Tag ------------------------------------- Net::Vlan: internal ------------------------------------- Interface Name internal Mac Address (True) 00:00:00:00:00:02 MTU 1500 Tag 3703 Customer-Tag

Impact

This can cause network issues and conflicts if occurring on multiple guests in the same VLAN as the same MAC addresses will be used.

Conditions

For this to manifest the vCMP host vcmpd process will have to have had a prior crash or be killed. In this scenario vcmpd on restart uses a default zero-base MAC address for the guests. The guests will not use the new zero-based MAC until services are restarted on the guest, on which the new MAC address will take effect.

Workaround

Restart the guest from the hypervisor.

Fix Information

vCMP no longer uses zero-based MACs on vcmpd crash/kill.

Behavior Change