On 06/08/2011 11:58 AM, Seth Tunstall wrote: > I also see the following errors in syslog: > > [ 4635.562395] (beiscsi_process_cq():1953):CQ Error 13, reset CID > 0xd00...
Is this the first line of the log or is there anything else? It looks like 13 is: #define CXN_KILLED_FIN_RCVD 13 /* Connection got invalidated * internally due to an * incoming TCP FIN. > [ 4635.891964] connection20:0: detected conn error (1011) > [ 4636.151546] (beiscsi_process_cq():1953):CQ Error 13, reset CID > 0xd80... > [ 4636.479385] connection21:0: detected conn error (1011) > [ 4756.947240] session20: session recovery timed out after 120 secs > [ 4757.249571] session21: session recovery timed out after 120 secs > > which, to me, implies that the iscsi adapter can't connect to the > target. I find this a bit strange, since I can ping the card's > interfaces from another machine on the network, they can detect the > targets from the BIOS utility, and I've also had success booting GRUB > from the target. I think we have got a tcp/ip connection, but when we went to send login iscsi pdu to create a session that failed. From the log messages about it looks like we got a FIN from the target which killed the connection. Jay, is my reading of be2iscsi's error code correct? Seth, are your initiator names set correctly? The be2iscsi initiator is going to have a different initiator name than what is set in the bios. The initiator name defaults to what is in /etc/iscsi/initiatorname.iscsi. What target are you using and is there any log info on the target? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
