- Code: Select all
[ProxyDetector] VMFS LUNs: ['SCST_FIO iSCSI Disk (eui.6130383331393732)'], NAS volumes: <no>
[ProxyDetector] Detecting storage access level for proxy [VMware Backup Proxy]
Testing proxy ip [10.0.0.13], netmask [255.255.255.0]
Testing host ip [10.0.0.4]
Host [Veeam] - IP address [10.0.0.13] is in the same subnet as host [10.0.0.4] IP [10.0.0.4]. Subnet mask [255.255.255.0].
Proxy [VMware Backup Proxy] - is in the same subnet as host [VMware ESXi 6.0.0 build-4192238]
[ProxyDetector] Proxy [VMware Backup Proxy]: Detecting san access level
[ProxyDetector] Proxy [VMware Backup Proxy]: disks ['6000C298767CA7A9EDCF98E0083B9C74566972747561','6366306363323838766565616D20']
[ProxyDetector] Proxy [VMware Backup Proxy]: No disks are are accessible through san but can failover to network
[ProxyDetector] Detected san storage access level for proxy [VMware Backup Proxy] - [SameSubnetwork]
[ProxyDetector] Detected mode [nbd] for proxy [VMware Backup Proxy]
I've read and re-read the various docs that talk about direct SAN access, and don't see anything that helps. I'm wondering if the proxy code is only aware of the 10.0.0.0/24 IP address, whereas the iSCSI initiator is using 192.168.2.0/24? I'll open a case if need be, just want to skip that if anyone sees anything obvious...