> > Hi, > > > > within the following lines you can see the result of the current > > scsi-nodes > > > > [EMAIL PROTECTED]:~# iscsiadm -m node > > 192.168.2.202:3260,1 iqn.2002-10.com.infortrend:raid.sn7455070.30 > > 192.168.1.202:3260,1 iqn.2002-10.com.infortrend:raid.sn7455070.10 > > 192.168.2.201:3260,1 iqn.2002-10.com.infortrend:raid.sn7455070.20 > > 192.168.1.201:3260,1 iqn.2002-10.com.infortrend:raid.sn7455070.00 > > [EMAIL PROTECTED]:~# iscsiadm -m session > > tcp: [1] 192.168.2.202:3260,1 > > iqn.2002-10.com.infortrend:raid.sn7455070.30 tcp: [2] > > 192.168.1.202:3260,1 iqn.2002-10.com.infortrend:raid.sn7455070.10 tcp: > > [3] 192.168.2.201:3260,1 iqn.2002-10.com.infortrend:raid.sn7455070.20 > > tcp: [4] 192.168.1.201:3260,1 > > iqn.2002-10.com.infortrend:raid.sn7455070.00
My question is -- will this be the order even if i reboot? Obviously the order of the nodes defines the order of the session. Will allways it be the same order? > > will this order allways be the same? In case of yes, I could prevent > > administration via udev -- and deal with this situation. > > If not, it may be hard to map changing identifiers via udev, right? > What do you mean with changing identifiers? SCSI ID of the disk/volume > should not change.. Only if the order changes, I will need to use this udev, hopefully. Klemens
pgpLGbVf3i27N.pgp
Description: PGP signature
