Thanks Basil. I took a look over the MAN page. It goes into quite a bit of detail but doesn't seem to cover our particular scenario. Specifically, on a filer already serving data, how do we disable the iscsi protocol for interface X across vfiler0 and all non-default vfilers while not disrupting iscsi services on the dedicated iscsi interface.

To help illustrate:

*Vfiler1>iscsi portal show* *IP Address TCP Port TPGroup Interface* *X.X.X.X 3260 1000 mgmt-interface* *Y.Y.Y.Y 3260 1001 iscsi-interface*

*Pfiler>iscsi portal show* *IP Address TCP Port TPGroup Interface* *X.X.X.Y 3260 1000 mgmt-interface* *Y.Y.Y.X 3260 1001 iscsi-interface* *Z.Z.Z.Z 3260 1002 replication-interface*

The goal is to disable iscsi services on the mgmt-interface and the replication-interface in both the pfiler and the vfiler. Both the pfiler and vfiler are currently serving data. All iscsi initiators are connected via the iscsi interface in both the vfiler and pfiler.

Im still digging into it, but based on what I've read, it looks like I should be able to run...

*Pfiler>iscsi interface disable mgmt-interface* *Pfiler>iscsi interface disable replication-interface*

...to effectively disable iscsi services on the non-iscsi interfaces in BOTH the pfiler and vfiler. The expectation is that disabling iscsi on the aforementioned interfaces results in the non-iscsi-network-portals being removed from both the Pfiler and Vfiler.

*Vfiler1>iscsi portal show* *IP Address TCP Port TPGroup Interface* *Y.Y.Y.Y 3260 1001 iscsi-interface*

*Pfiler>iscsi portal show* *IP Address TCP Port TPGroup Interface* *Y.Y.Y.X 3260 1001 iscsi-interface*

I am not sure if it will work out this way so just looking for some perspective. Is it the correct command to use? Will running it from the Pfiler result in the portals in both the pfiler and vfiler being removed? There are some other commands that look like they may apply to this use case but so far iscsi interface disable seems the most logical.

Thanks, Phil

On Mon, Feb 9, 2015 at 5:09 PM, Basil basilberntsen@gmail.com wrote:

Take a look at the section for the iscsi interface command on the iscsi man page ( https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_iscsi.1.html). I've never done it, but it looks like these commands should do what you need.

On Mon, Feb 9, 2015 at 4:20 PM, Philbert Rupkins < philbertrupkins@gmail.com> wrote:

...

Hello Toasters,

We have a client looking to limit iscsi services to a dedicated interface. It looks like, by default, ONTAP is running iSCSI portals on all interfaces in both the pfiler (vfiler0) and all vfilers.

Is "iscsi interface disable" on vfiler0 (physical filer) the best way to get rid of all of the extraneous iscsi portals? Will running "iscsi interface disable" on the physical filer get rid of the iscsi portal(s) on the physical filers and vfilers?

Not sure if I'll need to run a portal/tpgroup specific command or if "iscsi interface disable" will get rid of the portals.

8.1.3 7-Mode.

Thanks, Phil

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

I really appreciate the feedback! "iscsi tpgroup destroy" was the other command I was actually looking at however it states the following.

*iscsi tpgroup destroy [-f] <tpgroup_name>*

*Destroy a user-defined target portal group. Any network interfaces which are members of the tpgroup are assigned by ONTAP back to their system default tpgroups.*

Because the tpgroups I would destroy were created automatically by ONTAP, I assume they are the "system default tpgroups." The MAN page doesnt seem to indicate whether or not the system default tpgroups can be destroyed. It only says the interfaces will be returned to the system default tpgroups which implies that we are destroying a non-default tpgroup that we created manually.

On Tue, Feb 10, 2015 at 10:17 AM, Basil basilberntsen@gmail.com wrote:

I wish I could be more definitive, but I've literally never used iSCSI on Netapp. That said, it seems like your system has a TPGroup set up for each interface on each filer, like X.X.X.*X* port 3260 on vfiler1 and X.X.X.*Y* port 3260 on vfiler0 (which you call Pfiler) both seem to contain only a single interface, mgmt-interface. If this works the way it seems like it should, you could simply delete the TPGroup and that would stop iSCSI traffic from being sent to the management interface.

On Tue, Feb 10, 2015 at 11:03 AM, Philbert Rupkins < philbertrupkins@gmail.com> wrote:

...

Thanks Basil. I took a look over the MAN page. It goes into quite a bit of detail but doesn't seem to cover our particular scenario. Specifically, on a filer already serving data, how do we disable the iscsi protocol for interface X across vfiler0 and all non-default vfilers while not disrupting iscsi services on the dedicated iscsi interface.

To help illustrate:

*Vfiler1>iscsi portal show* *IP Address TCP Port TPGroup Interface* *X.X.X.X 3260 1000 mgmt-interface* *Y.Y.Y.Y 3260 1001 iscsi-interface*

*Pfiler>iscsi portal show* *IP Address TCP Port TPGroup Interface* *X.X.X.Y 3260 1000 mgmt-interface* *Y.Y.Y.X 3260 1001 iscsi-interface* *Z.Z.Z.Z 3260 1002 replication-interface*

The goal is to disable iscsi services on the mgmt-interface and the replication-interface in both the pfiler and the vfiler. Both the pfiler and vfiler are currently serving data. All iscsi initiators are connected via the iscsi interface in both the vfiler and pfiler.

Im still digging into it, but based on what I've read, it looks like I should be able to run...

*Pfiler>iscsi interface disable mgmt-interface* *Pfiler>iscsi interface disable replication-interface*

...to effectively disable iscsi services on the non-iscsi interfaces in BOTH the pfiler and vfiler. The expectation is that disabling iscsi on the aforementioned interfaces results in the non-iscsi-network-portals being removed from both the Pfiler and Vfiler.

*Vfiler1>iscsi portal show* *IP Address TCP Port TPGroup Interface* *Y.Y.Y.Y 3260 1001 iscsi-interface*

*Pfiler>iscsi portal show* *IP Address TCP Port TPGroup Interface* *Y.Y.Y.X 3260 1001 iscsi-interface*

I am not sure if it will work out this way so just looking for some perspective. Is it the correct command to use? Will running it from the Pfiler result in the portals in both the pfiler and vfiler being removed? There are some other commands that look like they may apply to this use case but so far iscsi interface disable seems the most logical.

Thanks, Phil

On Mon, Feb 9, 2015 at 5:09 PM, Basil basilberntsen@gmail.com wrote:

...

Take a look at the section for the iscsi interface command on the iscsi man page ( https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_iscsi.1.html). I've never done it, but it looks like these commands should do what you need.

On Mon, Feb 9, 2015 at 4:20 PM, Philbert Rupkins < philbertrupkins@gmail.com> wrote:

...

Hello Toasters,

We have a client looking to limit iscsi services to a dedicated interface. It looks like, by default, ONTAP is running iSCSI portals on all interfaces in both the pfiler (vfiler0) and all vfilers.

Is "iscsi interface disable" on vfiler0 (physical filer) the best way to get rid of all of the extraneous iscsi portals? Will running "iscsi interface disable" on the physical filer get rid of the iscsi portal(s) on the physical filers and vfilers?

Not sure if I'll need to run a portal/tpgroup specific command or if "iscsi interface disable" will get rid of the portals.

8.1.3 7-Mode.

Thanks, Phil

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters