On 09/03/2009 03:01 PM, ofero wrote: > What do you mean that it can not log in or log out ? >
It cannot create/destroy sessions. It cannot log into a target and find disks then later log out of the target and remove the disks. > lsmod shows the following output when I grep for bnx > > # lsmod | grep bnx > bnx2i 99104 0 > cnic 72984 1 bnx2i > scsi_transport_iscsi 67153 5 bnx2i,ib_iser,iscsi_tcp,libiscsi > bnx2 208520 0 > scsi_mod 196569 9 > bnx2i,ib_iser,iscsi_tcp,libiscsi,scsi_transport_iscsi,sg,scsi_dh,cciss,sd_mod > > That must mean that the iscsi module is loaded. But how do I ensure > that I am using the iscsi offload transport which is offered by the > NIC ? Again, I am trying to understand what is happening in the > documentation provided by HP in > http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01309558/c01309558.pdf > Ok, so what happened is that broadcom or some vendor forked the open-iscsi code for the pacakges mentioned in that manual. I am not 100% sure what they did. > According to this document the binding to the Accelerated iSCSI > offload is done by updating the node.transport_name property of the > node with the transport name for the NIC which is listed in the > following command > > # dmesg | grep "bnx2i: netif" > > From this command I can see that the transport name is > bcm570x-410100. > > But if I list the node properties > > # iscsiadm --mode node --targetname<targetname> -P 3 > > I can not see that there is any property with the name > node.transport_name. Only iface.transport_name. iface.transport_name and node.transport_name are the same thing. They changed names at some point. Depending on the tools version there should be some compat code so you can use either. If you do discovery then do iscsiadm -m node -T your_target -o update -n iface.transport_name -v bcm570x-410100 value does it get picked up as the iface.transport_name? And then if you do iscsiadm -m node -T your_target -l Does the command work? If you then do iscsiadm -m session -P 3 There should be a Transport or Iface Transport field that has the bcm* value set in the first command. Or if you do iscsiadm -m session the first string you would see the bcm string. It would be something like: # iscsiadm -m session tcp [2] 10.15.84.19:3260,2 iqn.1992-08.com.netapp:sn.33615311 Instead of tcp it would be bcm570x-410100 and then your target values would be in there. > > Where can I see the current value of the node.transport_name > property ? > Are you using the iscsi tools that came from open-iscsi.org or that came with your distro, or are you using tools from broadcom or HP? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
