Server Event Logs - To do with iSCSI???

[timbo343]

I'd be greatfull if someone could advise me on the following. We had an unexpected shutdown on one of the HOSTS last night. We have seen the iSCSI errors before and everything we do we cannot make head and tail of it so im posting out there for some help.

 

EventId 70: Error occurred when processing iSCSI logon request. The request was not retried. Error status is given in the dump data.

 

EventId 1: Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.

 

EventId: 113: iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal

 

Many Thanks

 

l *192.168.0.107 0003260 ROOT\ISCSIPRT\0000_0 .

[Michael]

This is Google's definition, if this helps:

 

iSCSI is a way of connecting storage devices over a network using TCP/IP. It can be used over a local area network (LAN), a wide area network (WAN), or the Internet. iSCSI devices are disks, tapes, CDs, and other storage devices on another networked computer that you can connect to.

 

In theory the problem could be software or hardware related - the fact your server just powered off, I'd be more inclined to say hardware.

[timbo343]

This is Google's definition, if this helps:

 

 

 

In theory the problem could be software or hardware related - the fact your server just powered off, I'd be more inclined to say hardware.

 

Thats my gut feeling too but when we had it installed something wasnt quite right, this was summer 14.

[Michael]

Thats my gut feeling too but when we had it installed something wasnt quite right, this was summer 14.

 

How do you mean something wasn't quite right? Performance issues or just general instability?

[timbo343]

How do you mean something wasn't quite right? Performance issues or just general instability?

 

Just instability. Both servers were setup exactly the same but the problematic one had performance issues with iSCSI and the company who installed it could never get to the bottom of the problem, to the point where it was all installed and configured, then ripped out, taken back to the supplier's office where it all "worked ok" so brought it back after testing for a week.

[pantscat]

Same firmware on the servers?

[Michael]

I guess one possibility is an issue with the motherboard, seeing as all devices (as the iSCSI description describes) connects/communicates everything together.

 

Another thing you could try is download/installing an application which will deliberately stress out the hardware - especially system memory, which can/does go wrong too.

[mikkydoos]

Sounds like board to me.

 

Was it a proper shutdown or just powered off ?

[timbo343]

Same firmware on the servers?

 

I need to check this, this is to be done next week but i haven't updated the FW. I hate doing FW updates the best of times.

 

I guess one possibility is an issue with the motherboard, seeing as all devices (as the iSCSI description describes) connects/communicates everything together.

 

Another thing you could try is download/installing an application which will deliberately stress out the hardware - especially system memory, which can/does go wrong too.

 

May have to download BurnIn - Test (or if anyone has anything better i can test with) ill try it next week.

 

Sounds like board to me.

 

Was it a proper shutdown or just powered off ?

 

As far as i can see it just powered off as all the VMs migrated over to HOST2 and when i logged into them, they all had the unexpected shutdown box.