iSCSIPrt Event ID's 7, 20, and 34

blkfoot
blkfoot used Ask the Experts™
on
On Sunday we applied Windows updates through WSUS to all servers.  When I came in Monday morning 4 servers had iSCSIPrt errors (Event ID 7, 20, and 34) reporting every few minutes.  These servers are Windows Server 2003 R2 SP2 servers with shares to a LeftHand SAN solution over iSCSI.  We were able to fix 2 of the servers by updating the iSCSI Initiator to the latest version and removing the LeftHand MPIO software but my two Exchange servers that are in a cluster still report all errors.  I have changed out CAT6 cables with no change and I have checked the switch to verify no packet errors.  Suggestions?

Event Type:      Error
Event Source:      iScsiPrt
Event Category:      None
Event ID:      7
Date:            7/8/2008
Time:            2:24:24 PM
User:            N/A
Computer:      EXCH1
Description:
The initiator could not send an iSCSI PDU. Error status is given in the dump data.

Event Type:      Error
Event Source:      iScsiPrt
Event Category:      None
Event ID:      20
Date:            7/8/2008
Time:            2:24:24 PM
User:            N/A
Computer:      EXCH1
Description:
Connection to the target was lost. The initiator will attempt to retry the connection.

Event Type:      Information
Event Source:      iScsiPrt
Event Category:      None
Event ID:      34
Date:            7/8/2008
Time:            2:24:26 PM
User:            N/A
Computer:      EXCH1
Description:
A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
YES -- UNDO THE UPDATES and STOP the system from auto-updating.  Just because M$ is delivering these "updates" doesn't mean they are secure and well tested.  The only SAFE system immune from crashes is one that either NEVER accepts M$ hotfix updates, or only takes updates that are PROVEN to not cause problems after 3 months of being released.

WSUS is what M$ wants you to do -- that doesn't mean it is good for your computers -- it just generates more $$$$$ for M$ -- and if you have problems, well, that's just your fault, isn't it?

Undo the updates, and turn off auto updating.  ONLY apply updates manually that have been proved to be reliable in the long term.
blkfootIT Services Administrator

Author

Commented:
Well, since I approve the updates after researching them prior to deploying through WSUS your solution is not what I am looking for nor do I believe it is the answer.  Does anyone else have some constructive ideas?  Thanks!
How many of the iSCSI ports on the SAN are you using?  Are they on seperate subnets from each other and from your LAN?  If you're using multiple iSCSI ports on the SAN and have not put the servers on seperate subnets, it may be that these ports have become confused and are now rejecting connections.  


Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

blkfootIT Services Administrator

Author

Commented:
Sorry for the delay in responding.  The SAN is on a separate subnet from the LAN and all other iSCSI connections appear to be functioning properly.  In fact, Exch2 which is the primary in the Exchange cluster is has all drives connected to the SAN but it is still throwing those errors in the event log.  Exch1 which is the secondary is the cluster connects one drive but not the other two.
IT Services Administrator
Commented:
After multiple reboots the errors have corrected themselves.

Commented:
Thats no real solution. Sorry!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial