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

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

In this Document

Goal

Solution

Applies to:

Goal

 This document explains the way OVN Host Drivers in ESXi 5.X can be installed and de-installed.

Solution

First and foremost, the commands below should work in most cases to install and update OVN ESXi 5.X host drivers.  However until Xsigo / Oracle releases a VMware "signed" driver, use the first command, Please note you must specify full path to where the OVN ESXi 5.X Host driver zip bundle package resides:

With all the old modules removed we install the new one:

 
If you are installing the xsigo_5.0.1.ESX5E.1-1vmw.500.0.0.406165.zip driver you do not need to include the --no-sig-check because this driver packaged is 'VMware Signed'.

Here are other commands to use when removing and installing Xsigo ESXi 5.0 Host drivers:

Install or upgrade Xsigo ESXi 5.X host drivers

 
Remove Xsigo Host Driver vib bundles

 
To manually remove Xsigo Driver ESXi 5.X vib bundles, follow the instructions below.

There are a number of changes to the ESXi 5.X interface, first and foremost is a reliance on the 'esxcli' command. The three general areas you are going to be concerned with are

esxcli software
esxcli network
esxcli storage

To see the listed options for each command type in 'esxcli software'  to see the options.

NOTE:  You can remove all Xsigo ESXi 5.0 Host driver vib packages at once, however if this command fails for any reason, use the individual commands below to remove each vib package one at a time.   

Here is the command to remove all Xsigo ESXi 5.0 Host driver vib packages at once:

esxcli software vib remove -n net-xsvnic -n scsi-xsvhba -n net-xscore  -n net-ib-basic -n net-mlx4-en

In order to remove the Xsigo ESXi 5.0 host driver vib packages one at a time,  the following steps need to be followed.

You need to locate each of the 6 vibs that drive our software.  I have used bold to show the command and the part of the query results we are concerned with.

Remove each vib in the proper order, xsvnic and xsvhba can be removed in either order though.

Please note that you need the vib name which is located on the left side of the query result (IN BOLD).  EG scsi-vhba is what you would use to remove xsvhba. 

# esxcli software vib remove -n net-xsvnic

Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_net-xsvnic_1.0.0-1vmw.500.0.0.406165
VIBs Skipped:

# esxcli software vib remove -n net-xve

# esxcli software vib remove -n scsi-xsvhba

Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_scsi-xsvhba_1.0.0-1vmw.500.0.0.406165
VIBs Skipped:

# esxcli software vib remove -n net-xscore

Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

Reboot Required: true
VIBs Installed:
VIBs Removed: VMware_bootbank_net-xscore_1.0.0-1vmw.500.0.0.406165
VIBs Skipped:

# esxcli software vib remove -n net-ib-basic

Removal Result

 Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true

VIBs Installed:
VIBs Removed: VMware_bootbank_net-ib-basic_1.0.0-1vmw.500.0.0.40616
VIBs Skipped:

# esxcli software vib remove -n net-mlx4-en

Removal Result

Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true

VIBs Installed:
VIBs Removed: VMware_bootbank_net-mlx4-en_1.0.0-1vmw.500.0.0.406165
VIBs Skipped:

Best Result is to run your greps this way:

 

This is the results when installing the Xsigo ESXi Host drivers:

With all the old modules removed we install the new one:

 Installation Result

Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true

VIBs Installed: VMware_bootbank_net-xscore_5.0.0.EX5E.1-1vmw.500.0.0.406165, VMware_bootbank_net-xsvnic_5.0.0.EX5E.1-1vmw.500.0.0.406165, VMware_bootbank_scsi-xsvhba_5.0.0.EX5E.1-1vmw.500.0.0.406165

 VIBs Removed: VMware_bootbank_scsi-xsvhba_1.0.0-1vmw.500.0.0.406165, VMware_bootbank_net-xsvnic_1.0.0-1vmw.500.0.0.406165, VMware_bootbank_net-xscore_1.0.0-1vmw.500.0.0.406165

 VIBs Skipped: VMware_bootbank_net-mlx4-en_1.0.0-1vmw.500.0.0.406165, VMware_bootbank_net-ib-basic_1.0.0-1vmw.500.0.0.406165

It has been confirmed on ESXi 5.5 systems that the OVN ESXi vib names have changed.  To remove the ESXi 5.5 vib bundles, remove them in the order show below prior to reinstalling the OVN ESXi drviver bundle from scratch or for installing a new version of the OVN ESXi 5.5 driver bundle:

This solution has no attachment