Verifying IP network connections - iSCSI, Windows

You verify Internet Protocol (IP) network connections by using ping tests to ensure the host and array are able to communicate.

1. Select Start > All Programs > Accessories > Command Prompt, and use the Windows CLI to run one of the following commands, depending on whether jumbo frames are enabled:
   • If jumbo frames are not enabled, run this command:

     ping -s <hostIP> <targetIP>
     

   • If jumbo frames are enabled, run the ping command with a payload size of 8,972 bytes. The IP and ICMP combined headers are 28 bytes, which when added to the payload, equals 9,000 bytes. The -f switch sets the don’t fragment (DF) bit. The -l switch allows you to set the size. These options allow jumbo frames of 9,000 bytes to be successfully transmitted between the iSCSI initiator and the target.

     ping -l 8972 -f <iSCSI_target_IP_address>
     

   In this example, the iSCSI target IP address is 192.0.2.8.

   C:\>ping -l 8972 -f 192.0.2.8
   Pinging 192.0.2.8 with 8972 bytes of data:
   Reply from 192.0.2.8: bytes=8972 time=2ms TTL=64
   Reply from 192.0.2.8: bytes=8972 time=2ms TTL=64
   Reply from 192.0.2.8: bytes=8972 time=2ms TTL=64
   Reply from 192.0.2.8: bytes=8972 time=2ms TTL=64
   Ping statistics for 192.0.2.8:
     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
   Approximate round trip times in milli-seconds:
     Minimum = 2ms, Maximum = 2ms, Average = 2ms
   

2. Issue a ping command from each host’s initiator address (the IP address of the host Ethernet port used for iSCSI) to each controller iSCSI port. Perform this action from each host server in the configuration, changing the IP addresses as necessary.
   Note: If the command fails (for example, returns Packet needs to be fragmented but DF set), verify the MTU size (jumbo frame support) for the Ethernet interfaces on the host server, storage controller, and switch ports.