iSCSI initiator problems after ESX 3.5 upgrade

Information

Title: 

iSCSI initiator problems after ESX 3.5 upgrade

Author(s): 

Xtravirt (Paul Davey)

Target Audience: 

Technical - Novice

First Published: 

2 March 2009

Products: 

VMware ESX

UID: 

XD10034

Having trouble seeing your ISCSI targets using the S/W initiator since upgrading to ESX 3.5?

One of the possible reasons is the required port in the ESX firewall is no longer automatically opened under ESX 3.5  To open it - click the Security Profile link under the configuration tab of your ESX hosts and then click properties, check the ESX S/W ISCSI Initiator tick-box and click OK. This will allow the iSCSI target discovery traffic through the firewall - you should then be able to pick up your iSCSI targets by rescanning the software iSCSI initiator under the Storage Adapters section.

References

References: 

1. Nil

Links: 

1. Nil