Re: iSCSI LIF migrate

sva_kaminski · ‎2012-04-26

Hi, we have an 4 node cmode Cluster running Data ONTAP 8.1RC2.

We want to migrate an iSCSI LIF from one node to another node, but we get an error that iSCSI LIF migration is not supported. Below i paste the command and the output of it:

cmode::> network interface migrate -vserver sc-prod -lif cmode-01_e0a -dest-node cmode-04 -dest-port e0a

Error: command failed: iSCSI or FCP LIFs do not support LIF migrate

cmode::>

In the documentation there is nothing about migration with iSCSI LIFs.

Hope anyone could help us.

Thank you

mrinal · ‎2012-04-26

Hi Sva,

You are correct the Network Admin Guide for 8.1 Cluster-Mode does not state if iSCSI LIF's can or cannot be migrated.

To answer your question.... If you are looking to create a new path for the client path to access a LUN then you will need to create a new LIF on the node in question. This is indirectly implied in Page 45 of the guide "Failover groups do not apply in a SAN iSCSI or FC environment."

We will look to add this information in the next update to the guides.

Hope this helps.

sva_kaminski · ‎2012-04-29

Hi Mrinal,

sorry for my late response and thank you for the quick answer.

We wanted a migration of the iSCSI LIF, to change all active ressources

from one node to another node, so that we can remove one HA-Pair from the

cluster.

Now we have created additional LIF's and make them accessible to the server

and then remove the node and his LIFs.

Thank you very much -

Bye Sven

Von: Mrinal Devadas <xdl-communities@communities.netapp.com>

An: Sven Kaminski <sven.kaminski@sva.de>,

Datum: 26.04.2012 16:52

Betreff: Re: iSCSI LIF migrate - Re: iSCSI LIF migrate

NetApp Online Community

Re: iSCSI LIF migrate

created by Mrinal Devadas in cmode - View the full discussion

Hi Sva,

You are correct the Network Admin Guide for 8.1 Cluster-Mode does not

state if iSCSI LIF's can or cannot be migrated.

To answer your question.... If you are looking to create a new path for

the client path to access a LUN then you will need to create a new LIF on

the node in question. This is indirectly implied in Page 45 of the guide "

Failover groups do not apply in a SAN iSCSI or FC environment."

We will look to add this information in the next update to the guides.

Hope this helps.

Reply to this message by replying to this email -or- go to the message on

NetApp Community

Start a new discussion in cmode by email or at NetApp Community

slava · ‎2012-05-31

Hello Sva,

Mrinal was right. The iSCSI LIFs can't be migrated.

The multipath driver on the host side is taking care of such situation.

You just need to move all data lif's (not iscsi) to be ready to evacuate nodes from c-mode.

sva_kaminski · ‎2012-05-31

Ich bin bis 14.06.2012 abwesend.

Thank you for your message. I will be back in the office on Thursday 14.

Juni and will reply to you as soon as possible when I return.

In urgent NetApp cases please contact Helmut Schulz

Mobile:+49 151 55005797

E-Mail: Helmut.Schulz@sva.de

or the Office in Wiesbaden

+49 6122 536 0

Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht "[cmode] -

Re: iSCSI LIF migrate" gesendet am 01.06.2012 02:42:44.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während

diese Person abwesend ist.

radhikat · ‎2012-05-31

Hi,

This information will be included in the Network Management Guide in the upcoming release.

Thanks,

Radhika

sva_kaminski · ‎2012-06-01

Ich bin bis 14.06.2012 abwesend.

Thank you for your message. I will be back in the office on Thursday 14.

Juni and will reply to you as soon as possible when I return.

In urgent NetApp cases please contact Helmut Schulz

Mobile:+49 151 55005797

E-Mail: Helmut.Schulz@sva.de

or the Office in Wiesbaden

+49 6122 536 0

Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht "[cmode] -

Re: iSCSI LIF migrate" gesendet am 01.06.2012 08:30:52.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während

diese Person abwesend ist.

mitchellcipriano · ‎2014-03-19

Hi,

I have netapp cluster mode simulator and have configured one node on this. I created ISCSI LIF using a STATIC ip( iscsi_lif) but ISCSI initiator utility on widnows 7 on my laptop is unable to find it. I also can not ping it.

Please tell me why iSCSI lif is unpigable and how to resolve it

cluster1::> network interface show

Logical Status Network Current Current Is

Vserver Interface Admin/Oper Address/Mask Node Port Home

----------- ---------- ---------- ------------------ ------------- ------- ----

cluster1-01

clus1 up/up 169.254.82.197/16 cluster1-01 e0c true

clus2 up/up 169.254.16.148/16 cluster1-01 e0d true

main up/up 10.2.2.174/23 cluster1-01 e0a true

cluster1-vs01

iscsi_lif up/up 10.2.2.141/23 cluster1-01 e0b true

vs01_lif2 up/down 20:02:00:50:56:97:60:cf

cluster1-01 0c true

5 entries were displayed.

madden · ‎2014-11-03

Hi

FC/iSCSI LIFs can be migrated if they are administratively disabled.

Here is an example of moving a iSCSI LIF from e4b-31 to e4c-31:

sdt-cdot1::> net int show -data-protocol iscsi

Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
sdt-vs-san1 sdt-vs-san1-01-iscsi1 up/up 10.64.31.38/24 sdt-cdot1-01 e4b-31 true
sdt-vs-san1 sdt-vs-san1-02-iscsi1 up/up 10.64.31.39/24 sdt-cdot1-02 e4b-31 true

sdt-cdot1::> net int modify -vserver sdt-vs-san1 -lif sdt-vs-san1-02-iscsi1 -status-admin down

sdt-cdot1::> net int modify -vserver sdt-vs-san1 -lif sdt-vs-san1-02-iscsi1 -home-port e4c-31

sdt-cdot1::> net int modify -vserver sdt-vs-san1 -lif sdt-vs-san1-02-iscsi1 -status-admin up

sdt-cdot1::> net int show -data-protocol iscsi

Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
sdt-vs-san1 sdt-vs-san1-01-iscsi1 up/up 10.64.31.38/24 sdt-cdot1-01 e4b-31 true
sdt-vs-san1 sdt-vs-san1-02-iscsi1 up/up 10.64.31.39/24 sdt-cdot1-02 e4c-31 true
2 entries were displayed.

sdt-cdot1::>

Of course, you must have multipathing working for this to be non-disruptive for your hosts, but it does avoid any need to 'touch' the host to add/remove paths.

Cheers,
Chris Madden
Storage Architect, NetApp EMEA