Thanks for the clarification and no, these systems aren't licensed for SnapDrive, nor are the Filers (a 8.1.x 7-mode HA pair). Time to look at the PowerShell solution, along with Diskpart.
tmac> You could installed the snapdrive software (it needs a license, tmac> either host based or filer/storage based) to install.
tmac> You should also look at http://support.netapp.com/matrix and tmac> plug in your system as best as you can to see which version tmac> would be supported in your case.
tmac> Once snapdrive is installed, go Server Manager and you will see something like this: tmac> Inline image 1
tmac> --tmac
tmac> Tim McCarthy tmac> Principal Consultant tmac> 443-228-TMAC (Google Voice) tmac> 214-279-3926 (eFAX)
tmac> [na_cert_dm] [rhce] [na_cert_ie]
tmac> Clustered ONTAP Clustered ONTAP tmac> NCDA ID: XK7R3GEKC1QQ2LVD RHCE6 110-107-141 NCSIE ID: C14QPHE21FR4YWD4 tmac> Expires: 27 October 2016 Current until Aug 02, 2016 Expires: 29 tmac> October 2016
tmac> On Mon, Mar 2, 2015 at 11:06 AM, John Stoffel john@stoffel.org wrote:
tmac> I dunno... I forgot to include that I'm a Unix/Linux and Netapp tmac> storage guy, not a Windows admin at all, but I need to work on getting tmac> something working.
tmac> So would the PowerShell suggestion, SnapDrive or diskpart be the tmac> better tools?
tmac> you mean besides SnapDrive? tmac> --tmac
tmac> Tim McCarthy
tmac> On Mon, Mar 2, 2015 at 10:25 AM, John Stoffel john@stoffel.org wrote:
tmac> Guys,
tmac> Trying to map LUNs presented to a Windows host back to the source tmac> Netapp Volume/Lun using something equivilent to the 'sanlun' command I tmac> can use on Unix systems.
tmac> I tried installing the Windows HUK (Host Utilities Kit) but burried in tmac> the release notes is a cute little statment that 'sanlun' isn't tmac> available on there.
tmac> Is there *any* tool which I can use from Windows to show me the Netapp tmac> volume and lun name from the Windows side of things?
tmac> Thanks, tmac> John tmac> _______________________________________________ tmac> Toasters mailing list tmac> Toasters@teaparty.net tmac> http://www.teaparty.net/mailman/listinfo/toasters
You know, another avenue:
Find out the IQN / WWPN of the Windows host. On the netapp, look at "igroup show". Find out which igroup it maps to. Then on the the netapp, "lun show -m" which should spit out all the luns and the LUN ID's and the igroup. Find your igroup, notice which LUN ID is which Then go back to your windows host and match the LUN ID to get which path is which.
--tmac
*Tim McCarthy* *Principal Consultant*
On Mon, Mar 2, 2015 at 11:23 AM, John Stoffel john@stoffel.org wrote:
Thanks for the clarification and no, these systems aren't licensed for SnapDrive, nor are the Filers (a 8.1.x 7-mode HA pair). Time to look at the PowerShell solution, along with Diskpart.
tmac> You could installed the snapdrive software (it needs a license, tmac> either host based or filer/storage based) to install.
tmac> You should also look at http://support.netapp.com/matrix and tmac> plug in your system as best as you can to see which version tmac> would be supported in your case.
tmac> Once snapdrive is installed, go Server Manager and you will see something like this: tmac> Inline image 1
tmac> --tmac
tmac> Tim McCarthy tmac> Principal Consultant tmac> 443-228-TMAC (Google Voice) tmac> 214-279-3926 (eFAX)
tmac> [na_cert_dm] [rhce] [na_cert_ie]
tmac> Clustered ONTAP Clustered ONTAP tmac> NCDA ID: XK7R3GEKC1QQ2LVD RHCE6 110-107-141 NCSIE ID: C14QPHE21FR4YWD4 tmac> Expires: 27 October 2016 Current until Aug 02, 2016 Expires: 29 tmac> October 2016
tmac> On Mon, Mar 2, 2015 at 11:06 AM, John Stoffel john@stoffel.org wrote:
tmac> I dunno... I forgot to include that I'm a Unix/Linux and Netapp tmac> storage guy, not a Windows admin at all, but I need to work on getting tmac> something working.
tmac> So would the PowerShell suggestion, SnapDrive or diskpart be the tmac> better tools?
tmac> you mean besides SnapDrive? tmac> --tmac
tmac> Tim McCarthy
tmac> On Mon, Mar 2, 2015 at 10:25 AM, John Stoffel john@stoffel.org wrote:
tmac> Guys,
tmac> Trying to map LUNs presented to a Windows host back to the source tmac> Netapp Volume/Lun using something equivilent to the 'sanlun' command I tmac> can use on Unix systems.
tmac> I tried installing the Windows HUK (Host Utilities Kit) but burried in tmac> the release notes is a cute little statment that 'sanlun' isn't tmac> available on there.
tmac> Is there *any* tool which I can use from Windows to show me the Netapp tmac> volume and lun name from the Windows side of things?
tmac> Thanks, tmac> John tmac> _______________________________________________ tmac> Toasters mailing list tmac> Toasters@teaparty.net tmac> http://www.teaparty.net/mailman/listinfo/toasters
tmac> You know, another avenue: tmac> Find out the IQN / WWPN of the Windows host. tmac> On the netapp, look at "igroup show". tmac> Find out which igroup it maps to. tmac> Then on the the netapp, "lun show -m" which should spit out all the luns and the LUN ID's and the tmac> igroup. tmac> Find your igroup, notice which LUN ID is which tmac> Then go back to your windows host and match the LUN ID to get which path is which.
This is what we've been doing, and it's a total pain and prone to confusion. Esp since I have igroups with a bunch of Netapp and Backup hosts in them, so I'm paranoid about unmapping a lun and then not being able to match it back to the host it's supposed to be used by.
This is just simple with 'sanlun lun show' and I'm annoyed it's such a hassle from the Windows side of the world, but that's probably my windows ignorance and lack of desire to work on Windows showing. Heh.
Thank you for all the suggestions, I do appreciate them!
"I have igroups with a bunch of Netapp and Backup hosts in them"
Your igroups should have windows (and possibly backup) hosts in them, unless you're feeding LUNs to another Netapp.
On Mon, Mar 2, 2015 at 11:38 AM, John Stoffel john@stoffel.org wrote:
tmac> You know, another avenue: tmac> Find out the IQN / WWPN of the Windows host. tmac> On the netapp, look at "igroup show". tmac> Find out which igroup it maps to. tmac> Then on the the netapp, "lun show -m" which should spit out all the luns and the LUN ID's and the tmac> igroup. tmac> Find your igroup, notice which LUN ID is which tmac> Then go back to your windows host and match the LUN ID to get which path is which.
This is what we've been doing, and it's a total pain and prone to confusion. Esp since I have igroups with a bunch of Netapp and Backup hosts in them, so I'm paranoid about unmapping a lun and then not being able to match it back to the host it's supposed to be used by.
This is just simple with 'sanlun lun show' and I'm annoyed it's such a hassle from the Windows side of the world, but that's probably my windows ignorance and lack of desire to work on Windows showing. Heh.
Thank you for all the suggestions, I do appreciate them! _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Duh... I goofed here. I've got a bunch of Windows, ESX and Solaris hosts accessing LUNs on this 8.1.x 7-mode cluster. I'm interested in mapping the Windows view to things to the Netapp view of things.
I'm right now downloading the OnCommand® Workflow Automation 2.2.1 package to install on my Windows 2008R2 x86_64 server as a test. Hopefully this will give me the details I want. But maybe not.
Trying to figure out how to grab just the core Powershell library if at all possible, so I could just install that small (ideally) part onto my Window(s) systems to help make this all easier down the line.
Thanks for all the feedback and suggestions.
Basil> "I have igroups with a bunch of Netapp and Backup hosts in them" Basil> Your igroups should have windows (and possibly backup) hosts in them, unless you're feeding LUNs Basil> to another Netapp.
Basil> On Mon, Mar 2, 2015 at 11:38 AM, John Stoffel john@stoffel.org wrote:
tmac> You know, another avenue: tmac> Find out the IQN / WWPN of the Windows host. tmac> On the netapp, look at "igroup show". tmac> Find out which igroup it maps to. tmac> Then on the the netapp, "lun show -m" which should spit out all the luns and the LUN Basil> ID's and the tmac> igroup. tmac> Find your igroup, notice which LUN ID is which tmac> Then go back to your windows host and match the LUN ID to get which path is which.
Basil> This is what we've been doing, and it's a total pain and prone to Basil> confusion. Esp since I have igroups with a bunch of Netapp and Backup Basil> hosts in them, so I'm paranoid about unmapping a lun and then not Basil> being able to match it back to the host it's supposed to be used by.
Basil> This is just simple with 'sanlun lun show' and I'm annoyed it's such a Basil> hassle from the Windows side of the world, but that's probably my Basil> windows ignorance and lack of desire to work on Windows showing. Basil> Heh.
Basil> Thank you for all the suggestions, I do appreciate them! Basil> _______________________________________________ Basil> Toasters mailing list Basil> Toasters@teaparty.net Basil> http://www.teaparty.net/mailman/listinfo/toasters
-
Basil -
John Stoffel -
tmac