What Specific Command Can You Use To Register A Server Running Server Core With An Isns Server

Setup iSCSI on Windows Server

1. Last updated

2. Save as PDF

This article applies to Windows Server 2012, 2012R2, 2016, 2019, 2022

1. Overview
2. Setup Using Windows Server and FlashArray Management Tools
   1. Configure MSiSCSI (Part i of 2)
   2. Configure FlashArray Host and Volume
   3. Configure MSiSCSI (Part 2 of two)
   4. Using CHAP with iSCSI
      1. Configure CHAP on the Windows host:
         1. Configure CHAP using PowerShell
         2. Testing Windows Server iSCSI CHAP
   5. Optimizing Latency on Windows Hosts
3. Test Connectivity

Overview

The Pure Storage FlashArray supports the Net Small Computer Systems Interface an Internet Protocol (IP) based storage networking standard for linking data storage facilities. Using iSCSI provides access to the Pure Storage FlashArray by issuing SCSI commands over the TCP/IP network.

The screenshot beneath illustrates iv connected Ethernet Ports (CT0.ETH6/ETH7 and CT1.ETH6/ETH7) in a Pure Storage FlashArray. These ports will be configured on the FlashArray and Windows Server for connectivity in Setup iSCSI Connectivity.

The following steps will configure the MSiSCSI Initiator Service to connect to the Pure Storage FlashArray iSCSI ports using the Windows Server management tools.

Setup Using Windows Server and FlashArray Direction Tools

This section walks through the steps for configuring MSiSCSI using the Graphical User Interface (GUI) tools provided past Windows Server and Pure Storage FlashArray direction interface.

Configure MSiSCSI (Part 1 of ii)

1. OpenServer Managing director. By default Server Manager starts when logging into Windows Server.
2. ClickTools and selectiSCSI Initiatorto beginning the MSiSCSI Initiator Service.
3. The Microsoft iSCSI dialog will open up indicating that the service is not running. ClickYes to starting time the service and also set it to startup automatically when the server reboots.

   

4. After the MSiSCSI Initiator Service has started the Properties dialog will be opened. Click theConfiguration tab to remember the iSCSI Qualified Proper name (IQN).

Write downwards or cutting-and-paste the Initiator Name value.

This step has started the Microsoft iSCSI Service so the Initiator Name could be retrieved which is required for the next department.

Configure FlashArray Host and Volume

Connecting a volume to a configured iSCSI host on the Pure Storage FlashArray is required before configuring MSiSCSI. if a volume is not continued, you volition receive an Dominance Failure.

1. Open thePure Storage FlashArray Directioninterface and log into the FlashArray.
2. Click on theStoragetab.
3. Click on the + in theHosts section and selectCreate Host.

   

4. Select the newly created host, Server01, and then click theEllipsison the acme right, then clickConfigure IQNs.

   

5. TheConfigure iSCSI IQNs dialog box will open. Enter the IQN from the previous section so clickAdd.

   

6. Click on the + in theVolumessection to create a book. For this case the proper nameiSCSI-TestVolume with a size of500GB is beingness used. A different proper noun and size can be used.
   
7. After creating the new volume click the elipsys in the Connected Volumes section and then selectConnect.

   

8. TheConnect Volumes to Host dialog volition open. Select the checkbox next to theiSCSI-TestVolume(or whatever volume proper name was created), so clickConnect.

   

9. Now the new host, Server01, is continued to the new book, iSCSI-TestVolume, with the host port IQN gear up to iqn.1991-05.com.microsoft:server01.

   

Configure MSiSCSI (Role 2 of 2)

In this section the configuration of MSiSCSI will exist continued using the iSCSI Initiator tool.

1. Open Server Manager.
2. ClickTools and selectiSCSI Initiatorto open the iSCSI Initiator Propertiesdialog.
3. Click on theDetect Portal...push button which will display theDiscover Target Portalsdialog.

These are the iSCSI Services that were configured in the Setup iSCSI on the FlashArray topic. These need to be in identify before proceeding.

iv. Enter the IP Address or DNS name for the target ports on the Pure Storage FlashArray. Leave the Port default gear up to 3260.

Echo Step four for each iSCSI service you have configured on the FlashArray. In this example there are four iSCSI services ready on the FlashArray.

v. Once all of the Target Ports accept been configured theDiscoverytabTarget portals list should look like the below example. This could differ based on the number of iSCSI initiators that are in the FlashArray.

half-dozen. Click on theTargetstab select the newly Discovered targetand click theConnectpush. This volition found a connection to the Pure Storage FlashArray iSCSI services.

Before connecting theStatus volition show asInactive.

After connecting theStatus will show equallyConnected.

If a FlashArray volume has not been connected to the host where the iSCSI Initiator Service is being set up you will meet the error,Authorization Failure.

This is the same FlashArray iSCSI Qualified Proper noun (IQN) that tin be seen from the FlashArray management interface.

7. Select the newly connectedDiscovered target and click theBackdrop... push to add sessions to the connection.

8. TheBackdrop dialog will open. ClickAdd session, this will open up up theConnect to Targetdialog.

Best Practice: For best operation out of a single host, viii (eight) iSCSI sessions are recommended. A session is normally created for every target port where a host is continued. If the host is connected to less than viii (8) paths, additional sessions can be configured going to the same target ports.

ix. ClickEnable multi-path and so clickAdvanced... push.

10. In the Advanced Settings dialog select theMicrosoft iSCSI Initiator from theLocal adapter dropdown. Select the advisable IP Address from theInitiator IPdropdown. Select theTarget portal IPfrom the dropdown that will map to the Initiator IP.

Repeat Step nine for all of the Initiator IPs and map to their appropriate Target portal IP.

11. Later completing the setup of the Initiator IPs and Target Portal IPs, click theFavorite Targets tab and all of the configured paths should exist visible.

12. Open up up theFlashArray Managementinterface, click theSystem tab, clickConnections, clickHost Connections, and select the host that was just configured. TheHost Port Connectivityshould showRedundant connections.

If the deployed switches in the fabric support irresolute the Maximum Transmission Unit (MTU) from 1500 to 9000 (referred to as Jumbo Frames), this can exist accomplished using the FlashArray Management GUI, or by running the Windows PowerShell cmdlets from the Pure Storage PowerShell SDK.

Using the FlashArray Management GUI

1. Click on Settings on the left carte du jour.
2. Click on Networkon the top menu.
3. Find the iSCSI Network interfaces and click on the Edit icon located at the end of the row.
4. Change the MTU size and click on Apply.

Using the PowerShell SDK

PS >$FlashArray = New-PfaArray -EndPoint x.21.201.57 -Credentials (Become-Credential) -IgnoreCertificateError PS >Get-PfaNetworkInterfaces -Assortment $FlashArray | Format-Tabular array -AutoSize  PS > Become-PfaNetworkInterfaces -Array $FlashArray | Format-Tabular array -AutoSize  subnet name     enabled  mtu services      netmask       slaves               address                 hwaddr                  speed ------ ----     -------  --- --------      -------       ------               -------                 ------                  -----        ct0.eth0    True 1500 {direction}  255.255.255.0 {}                   x.21.201.55            24:a9:37:00:38:8f  1000000000        ct0.eth1   False 1500 {direction}  64            {}                   2620:125:9004:2021::200 24:a9:37:00:38:8e  1000000000        ct0.eth3   False 1500 {direction}                {}                                           24:a9:37:00:38:91 10000000000        ct0.eth6    True 9000 {iscsi}       255.255.255.0 {}                   10.21.201.59            90:e2:ba:4d:75:51 10000000000        ct0.eth7    True 9000 {iscsi}       255.255.255.0 {}                   10.21.201.61            90:e2:ba:4d:75:50 10000000000        ct1.eth0    True 1500 {direction}  255.255.255.0 {}                   10.21.201.56            24:a9:37:00:39:07  1000000000        ct1.eth1   False 1500 {direction}  64            {}                   2620:125:9004:2021::201 24:a9:37:00:39:06  1000000000        ct1.eth3   False 1500 {direction}                {}                                           24:a9:37:00:39:09 10000000000        ct1.eth6    True 9000 {iscsi}       255.255.255.0 {}                   10.21.201.sixty            ninety:e2:ba:53:ba:nineteen 10000000000        ct1.eth7    True 9000 {iscsi}       255.255.255.0 {}                   10.21.201.62            90:e2:ba:53:ba:xviii 10000000000        replbond    Truthful 1500 {replication} 255.255.255.0 {ct1.eth2, ct0.eth2} 10.21.201.58            92:76:9c:80:b9:77           0        vir0        True 1500 {management}  255.255.255.0 {}                   10.21.201.57            8e:85:63:ff:fd:dd  1000000000        vir1       False 1500 {management}  64            {}                   2620:125:9004:2021::202 ce:f6:e1:ed:26:ec  1000000000         PS >Set-PfaInterfaceMtu -Array $FlashArray -Name 'ct0.eth6' -Mtu 9000 PS >Set-PfaInterfaceMtu -Array $FlashArray -Proper name 'ct0.eth7' -Mtu 9000 PS >Set up-PfaInterfaceMtu -Array $FlashArray -Name 'ct1.eth6' -Mtu 9000 PS >Set-PfaInterfaceMtu -Assortment $FlashArray -Name 'ct1.eth6' -Mtu 9000

Using CHAP with iSCSI

When using the Challenge Handshake Hallmark Protocol (CHAP) with an iSCSI target, it tin can exist a connection that is bi-directional (or "mutual"), which means that the initiator and target both do authentication. Alternatively, it tin can exist a one-way connection which has merely the target authenticating to the initiator.

For more information on using CHAP with FlashArray, please run across this commodity.
For more general data on Windows Server iSCSI, please refer to this Microsoft documentation.

Configure CHAP on the Windows host:

For Windows Server 2008 R2:

Administrative Tools >iSCSI Initiator >Discovery >Avant-garde Enter inbound values when adding a target portal. If using a bi-directional (mutual) connection, employ theGeneral >Hugger-mugger surface area in the iSCSI Initiator Properties dialog to specify a value.

For Windows Server 2012 and later on:

Server Manager >Dashboard >Tools >iSCSI Initiator >Targets >Discovery >Advanced Enter entering values when calculation a target portal. If using a bi-directional (mutual) connexion, apply theConfiguration >CHAP surface area in the iSCSI Initiator Backdrop dialog to specify a value.

As a best do, you should not use a password for CHAP authentication that has hexadecimal characters.

Configure CHAP using PowerShell

Create a iSCSI connexion to a target with one-manner authentication.

Connect-IscsiTarget -NodeAddress iqn.1991-05.com.microsoft:rx-7-iscsitarget01-target -AuthenticationType ONEWAYCHAP -ChapUsername "username" -ChapSecret "123456789012345" -IsPersistent $Truthful

Create a iSCSI connection to a target with bi-directional (mutual) hallmark.

Connect-IscsiTarget -NodeAddress iqn.1991-05.com.microsoft:rx-vii-iscsitarget01-target -AuthenticationType MUTUALCHAP -ChapUsername "username" -ChapSecret "123456789012345" -IsPersistent $True

Optimizing Latency on Windows Hosts

The Windows operating system incorporates a setting for TCPIP called the Delayed Acknowledgement feature. Past changing the default settings, you could possibly reduce the amount of overall network latency when using iSCSI connections. This is a recommended practice, however, the setting changes should be tested in your surroundings before altering a disquisitional production organisation.

Please refer to this iSCSI Best Practices commodity for settings and scripts to help yous with creating or irresolute these settings.

Configuring Volumes with Windows Server

Refer to the below article for configuring volumes with Windows Server.

• Working with Volumes on a Windows Server Host

Test Connectivity

To exam the connectivity from the host to the FlashArray, you tin apply DISKSPD for a basic plumbing test. DISKSPD is a storage load generator/performance exam tool from the Microsoft Windows, Windows Server, and Cloud Server Infrastructure Engineering science teams.

DISKSPD is non recommended for performance testing. The use case mentioned here is to just test the connectivity to the FlashArray.

Running diskspd with the beneath example command line will generate I/O to evaluate connectivity. The<DRIVE_LETTER> in the command line should be the drive letter of the newly connected volume. To acquire how to gear up up a drive letter for a newly continued book see Working with Volumes on a Windows Server Host.

                .\Diskspd.exe -b8K -d3600 -h -L -o16 -t16 -r -w30 -c400M <DRIVE_LETTER>:\io.dat              

The results of the plumbing test should generate similar output as below.

The host tin as well be monitored using the Purity CLI with the below command.

pureuser@myarray-ct0:~# purehost monitor --balance Name      Fourth dimension                     Initiator WWN  Initiator IQN                       Target       Target WWN  Failover  I/O Count  I/O Relative to Max Server01  2017-06-07 09:thirty:06 PDT  -              iqn.1991-05.com.microsoft:server01  (primary)    -           -         500187     99%                                                   iqn.1991-05.com.microsoft:server01  (secondary)              -         506741     100%              

Source: https://support.purestorage.com/Solutions/Microsoft_Platform_Guide/FlashArray_Connectivity/aa2_Setup_iSCSI_on_Windows_Server_2012,_2012_R2,2016_and_2019

Posted by: cordesciediand.blogspot.com

Share this post