This demonstration is attaching a windows 2016 server to AM E four IAI array. Before we begin, it is important to understand the layout. The me four has four ice cai ports on each controller. The ice ports are cabled redundantly to two different switches dedicated to IKE traffic ports. Zero and two are on one subnet while ports one and three are on the second subnet. The server has 2 10 gig nicks dedicated for IKEY traffic.
Prior to starting the deployment, all IP S should be defined on a planning worksheet to avoid any confusion to help better identify individual ports. I use a standard format for the IP schema. Let's take a look at it. First, I use a class B subnet and use either one or two in the second octet to signify what subnet it is in. I also use a one or two on the first digit of the third octet to identify what controller the port is on. In addition, the last matches the controller's management. IP you can see here all ports are on controller.
A have a one and end in 1 28 matching the management port for ports on controller B the third octet starts with two and the fourth octet matches the management port IP of 129. Finally, the third digit of the third octet is the port number. If this had been a dual protocol system with both fiber channel and II, there would only be two ports in each subnet, not four. After reviewing your worksheet, it's time to cable the server and assign IP S to the next. After the cabling is complete, open network connections, I renamed the Knicks to better identify them. We aren't using I PV six on the network.
So I'll disable I PV six and assign an I PV four address for each submit. I'm not replicating to another subnet. So I won't need a gateway. I'll repeat for the second Nick. I recommend pinging all IP S on the network. This simple step can prevent hours of frustration, later, troubleshooting connectivity issues. I'm not going to demonstrate ping here but I have tested all IP S next step is to install and configure MP IO. This will take two reboots. First is installing MP IO open server manager, then add roles and features.
Click next, next, next, until you get to features, scroll down to multi pa IO select it and click next, click install, then click close and reboot when completed after the server reboots, open server manager and click tools, then MP IO click on discover multi paths, select, add support for Cuzzi devices, then click the add button and yes, the server will now reboot again. Next is configuring the initiator, open server manager. Click on tools. Then I as the initiator, the first time I initiator is run, you will need to click. Yes, to have it start automatically when the server reboots, click on the discovery tab.
Then discovery portal, use your planning worksheet and add the IP of one of the ports on controller A that's on the first subnet. If you copy and paste, make sure there are no spaces after the IP address repeat, adding a second portal from the other subnet and choose a port from controller. B, click on the targets tab, highlight the discovered target and click connect, select enable multi pa and click advanced change the local adapter from default to Microsoft IAY initiator. Then select the IP for the first I Nick. Next in the target portal IP. Choose the first IP listed in the same subnet click. OK? And OK.
Repeat three more times for the first Nick connecting to all ports on the first subnet after the first Nick is complete repeat for the second Nick connecting to all its targets on that Subnet. After all connections are made, you can click on the favorite targets tab to see each path. If you click details, you can see specific information about each path. Next is running the host setup wizard log in to the me storage manager on the home page, click on action, then host set up, confirm you've met all the prerequisites and click next type a name for the host name. Typically you would use the real host name. I'm just gonna use Windows server one, select the initiator and click next.
If this is going to be part of a cluster, you can either create a new host group or add to an existing one. This will be a standalone server. So I'm selecting do not group this host. Click next to continue by default, 2 100 gig lines will be created one in each pool. I recommend renaming the volume to include the server names. You can edit the size change, pool, ownership add and remove the number of volumes to create when you have the volumes. How you want them. Click next review and click configure host, click yes or no, depending if you have another host ready to be configured.
In most cases you will click no open disk manager and rescan disc, right? Click on the new disc and bring it online, right? Click on it again and choose initialized disc, right? Click on the unallocated space and follow the wizard to format the volume. Go back into the ice initiator and click on auto configure that completes this demo. The volume is now accessible to the server with multi pathing configured.
