I'll make a trace shortly. The only reason iscsi_tcp is loaded is so that the target can boot its OS and run an iscsiadm discovery. As far as I understand it, iscsiadm still can't discover if there's no route to the target.
We do not need a IP route for discovery thru be2iscsi. Pl use the transport as be2iscsi On Jun 9, 2011 6:15 PM, <[email protected]<mailto:[email protected]>> wrote: > >>Thanks for the speedy reply! > >>I've set the initiator name the same in the bios and in the OS. Do >>they *have* to be different? I can see the logic in having each >>transport have a different name, but it seems not to be the case with >>the other qlogic iscsi HBAs i'm using. > > There is no requirement on the initiator name being same or otherwise but I > generally use the same name. > > I understand that you are able to complete the login from Emulex iscsiselect > (BIOS screen which you get into by pressing > Ctrl-C). You are able to login from iscsiselect and see the LUNS , right? > > I did not understand the part about iscsi_tcp because that is not required > for be2iscsi. > > Can you send your iface. Also, a wireshark trace would be very helpful. > > > -- 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.
