When an ACR is configured by using an IP address on an ESX server, IP address matching is performed before access to the StorSimple volumes is enabled. This means that only the connections that match the specific IP address can access the volumes. If the server in question has multiple IP addresses, but the ACRs are configured so that not all the paths to the network are included, the user may experience connectivity issues.
For example, assume that the host server has two IP addresses, 10.2.43.60 (iSCSI) and 10.2.43.61 (management). These can be used to connect to the respective StorSimple volumes. Then, the user creates an ACR and associates it with only one of these IP addresses—10.2.43.60, for example. In this scenario, there is a network path (for 10.2.43.61) for which no ACR is defined. If there's more than one network path to the server, the ACRs must be configured to include all those paths.
If a user has this configuration, he or she is likely to encounter connectivity issues. For example, if the user's initiator connection that uses the iSCSI IP address stops, and the initiator connects again by using the management IP address (with the virtual machine kernel enabled), the user can connect this time. However, the StorSimple volumes will not be exposed. Therefore, the volumes will disappear.