Oracle Fabric Interconnect F1-15
 
Oracle Fabric Interconnect F1-4
 
Oracle Fabric Manager
 

PLA-Support>Sun Systems>SAND>Network>SN-SND: Oracle Virtual Networking
 

In this Document

Symptoms

Cause

Solution

Applies to:

Symptoms

Servers are losing their IP addresses/connectivity after a reboot, re-attempting to enter the IP address triggers a warning that its being already used by another NIC. The TCP/IP page is greyed out except for the gateway. But the server is still pingable.

Cause

The root cause of this issue is a bug in Oracle Fabric Manager (OFM) versions prior to 3.3.0 (3.2.X and earlier) that would generate a "Phantom" vNIC on Windows Hosts using HA vNIC pairs.

Solution

This resolution is applicable only to HA-vNIC pairs created using OFM version 3.2 and prior to it

First check:

1.  Version of windows that is running on these servers? ex: Windows 2008 R2

2.  Confirm if these servers have firmware packages 2.8.8 (with 2. 7.0 or 2.7.7.10 FW + 2.8.6 option ROM) or 2.8.6 FW package (with 2.7.0 or 2.7.7.10 FW + 2.7.9 option ROM) and not 2.8.7

3.  Confirm if the 2.7.4.37 WHQL host drivers version for the servers are installed.

4. Also confirm if there are any third party network teaming utilites running on the these servers which will interfere with Xsigo's environment. If yes, uninstall it.

5. Also, Please confirm if they have access to the hosts via ILO/DRAC

Following is the resolution to remove the phantom vnics.

1. Take a snapshot of the vnic details page so that you can note the vnic 'details' from the chassis OFM server or the Chassis according to the below procedures.

From the OFM: On the left navigation pane, click Physical Servers tab, select the server, click on vNIC's tab, click on the HA-vNIC (that needs to be deleted from XMS v3.2 and again created from the Chassis.). Take a screen shot of the General settings tab and also the ethernet properties tab to note the termination port, MAC address, VLAN ID, MTU settings, Trunk or access mode


-- OR --

From the Chassis :

From the admin prompt, take a screen shot of the below command to note down the mac-addr, interface its terminated to, mtu settings, ha-vnic name, vLAN ID, mode, qos.

( "havnic pair name" = Replace it by the vnic name assigned by you )

2. Delete the HA-vNIC on the XMS from

     a. Physical Server page-->Physical Server-->vNIC/s as well as the
     b. I/O template page -->I/O template name--> vNIC/s

3. Verify on both the Chassis whether the HA-vNIC pair has been deleted

At the admin prompt:

 
4. Login into the host now via DRAC or ILO , Showphantom *vnic* (to check) and then delete it with phantomremove *vnic* commands as shown below.
 
On windows host, run the command prompt as an administrator:
 
- Cd to C:\windows\system32\xsigo\xginstdev64.exe showphantom *vnic*          --> To check  
(for 32bit OS replace xginstdev64 by xginstdev32.exe)
 
- Cd to C:\windows\system32\xsigo\xginstdev64.exe phantomremove *xsigo*      --> To remove
(for 32bit OS replace xginstdev64.exe by xginstd32.exe)

5. Add the HA-vNIC pair via the CLI (with the same vNIC name, termination port, MTU settings,  vlan ID, mode (access or trunk)  and the MAC address --> Similar to the snapshot you took in step 1 (via the OFM server or the Chassis)

How to add a HA-vNIC pair across 2 directors

Log into the first I/O Director
— Create a vNIC
— Give the vNIC the same name
— Assign the vNIC to the same server profile
— Bind the vNIC to the same physical interface card (slot/port)
--- Configure the correct access vlan ID, mac address (if you need the same MAC address for the vNIC otherwise can exclude it), mode (access or trunk) noted in step 1.
— Configure the new vNIC as the primary vNIC in a high-availability vNIC pair as shown in the example below
 
00:13:97:04:E1:AB

At the admin prompt:
Chassis1#add vnic havnic.test1 12/1 -access-vlan=1 -mac-id=00:13:97:04:E1:AB -mode=trunk  ha -primary
 

Confirm the above configuration by:
Chassis1#show vnic havnic.test1 -detail     (Note down the mac address here and also observe that the vNIC shows primary )

Now, Log into the second I/O Director
— Create a vNIC
— Give the vNIC the same name
— Assign the vNIC to the same server profile
— Bind the vNIC to the same physical interface card (slot/port)
--- Configure the same vlan ID, mode (access or trunk)
— Configure the new vNIC as the secondary NIC in a high-availability vNIC pair
— Enter the primary vNIC’s MAC address
 
At the admin prompt:
Chassis2#add vnic havnic.test1 12/1 -access-vlan=1 -mode=trunk ha -secondary -mac=00:13:97:04:E1:AB

Note: The MAC address in the above command should be the same MAC address of the primary vNIC created on the director/chassis1

Confirm the above configuration by:
Chassis2#show vnic havnic.test1 -detail (The vNIC should show as standby here)

This solution has no attachment