jimab2611

Well-Known Member
Joined
Mar 13, 2022
Messages
10
Hi All,

I have a windows 2012 r2 server with iscsi drives configured. Server is experiencing slowness during data copy between iscsi drives after server reboot . In order to fix the issue , I need to disable and enable iscsi configured NIC card after server reboot . It looks server is not able to negotiate properly with switch after every reboot . After disabling and enabling the NIC , it is able to make successful negotiation . Could someone can advise why this is happening after reboot and any solution ? Thank you .

Note: server is hosted in vmware infra and other servers hosted in same host do not have any issue
 


Solution
It appears that the issue you are facing is related to the negotiation between your Windows Server 2012 R2 server and the iSCSI drives upon reboot. Here are some steps and suggestions to address and potentially resolve the problem:

### Initial Troubleshooting Steps:
1. Update NIC Driver:
- Ensure that you have the latest network interface card (NIC) drivers installed on your Windows 2012 R2 server. Outdated drivers can sometimes cause negotiation issues.

2. Check NIC Settings:
- Verify the network adapter settings on the server to ensure they match the configuration required by the iSCSI drives. Pay attention to speed and duplex settings.

3. Review Event Logs:
- Check the Windows Event Viewer logs...
It appears that the issue you are facing is related to the negotiation between your Windows Server 2012 R2 server and the iSCSI drives upon reboot. Here are some steps and suggestions to address and potentially resolve the problem:

### Initial Troubleshooting Steps:
1. Update NIC Driver:
- Ensure that you have the latest network interface card (NIC) drivers installed on your Windows 2012 R2 server. Outdated drivers can sometimes cause negotiation issues.

2. Check NIC Settings:
- Verify the network adapter settings on the server to ensure they match the configuration required by the iSCSI drives. Pay attention to speed and duplex settings.

3. Review Event Logs:
- Check the Windows Event Viewer logs for any network-related errors or warnings that might indicate problems with the NIC configuration during startup.

### Potential Solutions:
1. Static Configuration:
- Consider assigning static IP addresses to the NICs associated with the iSCSI drives to ensure that the IP settings remain consistent across reboots.

2. Jumbo Frames:
- If supported by your network infrastructure, enabling jumbo frames on the NICs and switches can optimize data transfer speed for iSCSI traffic.

3. Delay Start for iSCSI Service:
- Adjust the startup delay for the iSCSI service to allow time for the network interfaces to fully initialize before attempting to establish connections with the iSCSI drives.

4. iSCSI Initiator Settings:
- Review the iSCSI Initiator settings to ensure they align with the iSCSI target configurations. Pay attention to CHAP settings, authentication, and target discovery.

5. VMware Configuration:
- Check the VMXNET3 adapter settings in VMware to ensure they are compatible with your server's NIC configuration.

6. Firmware Updates:
- If the server is running on a physical machine, ensure that both the server's firmware and the underlying hardware are up to date.

Monitoring network utilization and performance during server reboots can help identify any anomalies that could be contributing to the negotiation issues. If the problem persists, consider consulting with your network or storage administrator for further assistance.

I hope these suggestions point you in the right direction to address the negotiation problems you are experiencing with your iSCSI drives.
 


Solution
Back
Top