Hi guys,
I installed a clean ESX 3.01 test box with two physical nics. One is connected to my internal network, and the other one the my SAN network. The "SAN" NIC is connected to a GB-switch and the switch has a connection to an Equallogic SAN.
The first NIC has 10.0.0.100 /255.255.255.0 and is configured with the service console.
The second NIC has 192.168.1.100 /255.255.255.0.
I first enabled the iSCSI client on the FW.
I then used networking to configure the VM Kernel on the second NIC. (So 192.168.1.100)
I then enable the iSCSI Software Adapter and added the SAN (192.168.1.10) to the Dynamic Discovery tab. The system does not discovery anything however. I did a rescan/reboot a few times.
- When I select the iscsi software adapter and check the details it does not list an ip address. The field is empty. Is this OK?
Anybody some help? How can I troubleshoot this isse?
I checked the manual and they explain I should add another service console connection on the "SAN" NIC? This sounds strange to me as this NIC is not connected to my normal network. Should I add a service console? And which IP should I use?
I installed a clean ESX 3.01 test box with two physical nics. One is connected to my internal network, and the other one the my SAN network. The "SAN" NIC is connected to a GB-switch and the switch has a connection to an Equallogic SAN.
The first NIC has 10.0.0.100 /255.255.255.0 and is configured with the service console.
The second NIC has 192.168.1.100 /255.255.255.0.
I first enabled the iSCSI client on the FW.
I then used networking to configure the VM Kernel on the second NIC. (So 192.168.1.100)
I then enable the iSCSI Software Adapter and added the SAN (192.168.1.10) to the Dynamic Discovery tab. The system does not discovery anything however. I did a rescan/reboot a few times.
- When I select the iscsi software adapter and check the details it does not list an ip address. The field is empty. Is this OK?
Anybody some help? How can I troubleshoot this isse?
I checked the manual and they explain I should add another service console connection on the "SAN" NIC? This sounds strange to me as this NIC is not connected to my normal network. Should I add a service console? And which IP should I use?