This post is more than 5 years old
5 Posts
0
30758
June 12th, 2015 08:00
PS4000 group, "Target failed to respond in time to a Task Management request."
Hey everyone,
About a year ago I was able to re-purpose a PS4000 SAN and an older proliant server to make a small Hyper-V network. It has always ran great and hasn't given me any problems. Recently I acquired a second PS4000 and proliant server... so I added the second SAN to the original SAN group with the intention of making a second volume in the group for my second server to use.
The problem I'm having is that my second server can seemingly connect to the second volume via iScsi, but once it's connected I can't format the drive or anything. Attempting to initialize and format the drive just goes on forever, disk management seemingly freezes. There is an error in the event viewer saying "Target failed to respond in time to a Task Management request." Additionally the SAN group even log shows the event "iSCSI session to target was closed. iSCSI intra-group connection failure. Reset received on the connection.
If anyone could give me some insight on this it would be greatly appreciated... I'm pretty new to the SAN world. The only difference between the two servers is that one is Server 2012 and the other one is 2012 R2.
Traemandir
5 Posts
0
June 23rd, 2015 09:00
I figured it out.... just wanted to post my answer here just in case anyone else is having the same problem.
While upgrading the firmware on the SAN was important, what resolved the issue was actually upgrading the firmware on my server's NIC card. In my case, there was a firmware upgrade utility for my HP NC382T NIC in my Proliant DL380 G7 server on HP's support site. While using the utility, I found that the iScsi portion of the firmware was very out of date, and was prompted to upgrade it. After upgrading the firmware and reinstalling the drivers for good measure, the iScsi conenction worked perfectly.
Thank you everyone for your input!
Traemandir
5 Posts
0
June 12th, 2015 13:00
The switch setup we have is very humble, it's nothing fancy. Both SANs and Hyper-V servers are connected to a single Cisco Catalyst 2960-x. The ports should be fine, I don't think any VLANs are configured on the switch. Both SANs reply to pings from their respective IP addresses, and they were able to establish connections to each other as a SAN group without any problems.
I don't think it's using jumbo frames as one of the events in the SAN group says "iSCSI login to target successful, using standard frame length."
They both are running firmware version 02.03.
Again just reiterate: We have two servers, srv01 and srv02. We have two SANs together in one SAN group, hosting two volumes, vol01 and vol02. srv02 can initially connect to vol02 with iScsi but can't do anything with the drive, events are logged about losing connection. Srv01 works great with vol01, and can even connect to vol02 with no problems for testing purposes. srv01 is running Server 2012 and srv02 is running 2012 R2.
Thank you for your input thus far ...
Origin3k
4 Operator
•
2.3K Posts
0
June 13th, 2015 00:00
About the "disk management seemingly freezes" issue..... i seen this earlier this year during a deploymend for a new hyper-v setup. These guys never read a EQL deployment guide and struggeling about the following:
- They create a network bond/lag within the 2012R2 and Switch. Something that an EQL doesnt like
- The ASM was installed together with a rescent version of the Broadcom BACS utilitiy and the later one have a big flaw that if you specify things like MTU that under the hood the tool does something different. The Dell Support was already aware about that issue and was able to help
Regards,
Joerg
Traemandir
5 Posts
0
June 15th, 2015 06:00
You are right, I was reading the wrong number... firmware version is V4.3.6 (R130042) for both.
No, I'm not trying to connect both servers to the same volume. My group is hosting two volumes, one for each server... srv02 can't completely connect to vol02.
Okay ... I'll take a look today and see if I can get into the settings for that switch and get back to you here.
Traemandir
5 Posts
0
June 18th, 2015 06:00
Okay,
So I backed up the data and took the SANs off of production to upgrade them, they are now running V7.1.2, which is the latest I have access to.
The problem still persists... but I took this time while they are not in use to do some testing. Other servers running Server 2012 can connect to the volume perfectly fine .... it appears to be a problem with the Server 2012 R2 operating system, or the specific server itself. Any more thoughts?