Skip to main content

Preparing the ESXi Hypervisor for multiple NIC Usage




Step 1:

  • Open the vSphere Client and proceed to ConfigurationNetworking and click Add Networking
ISCSI-mountVmware-01.png

Step 2:

  • Select VMKernel and click Next
ISCSI-mountVmware-02.png

Step 3:

  • Create a new network switch and select a NIC located on another subnet
ISCSI-mountVmware-03.png

Step 4:

  • Enter a new name for this new network and click next
ISCSI-mountVmware-04.png

Step 5:

  • Enter an IP Address and Subnet address for this secondary NIC and click next
ISCSI-mountVmware-05.png

Step 6:

  • Final Confirmation Settings
ISCSI-mountVmware-06.png

Step 7:

  • The second network has been added to this Hypervisor
ISCSI-mountVmware-07.png

Step 8:

  • Repeat this process for each additional network to be added to the Hypervisor

Step 9:



Mounting the iSCSI Target on the ESXi Hypervisor

Overview: This section will guide the administrator in mounting iSCSI Targets on the Synology DiskStation to the ESXi Hypervisor.

Step 1:

  • Within the Configuration tab, click on Storage Adapters, select the iSCSI Software Adapter and click Properties
ISCSI-mountVmware-08.png

Step 2:

  • In this example, the iSCSI Initiator is disabled, click Configure to configure the settings of the iSCSI Initiator
ISCSI-mountVmware-09.png

Step 3:

  • Enable the iSCSI Initiator
ISCSI-mountVmware-10.png

Step 4:

  • Once the iSCSI Initiator is enabled, click on Dynamic Discovery
ISCSI-mountVmware-11.png

Step 5:

  • Enter the primary IP Address of the Synology DiskStation
ISCSI-mountVmware-12.png

Step 6:

  • If mounting for MPIO, enter the secondary IP address of the Synology DiskStation, located within the secondary subnet of the ESXi Hypervisor
    • The preceding direction may skipped for non-MPIO Environments
ISCSI-mountVmware-13.png

Step 7:

  • Rescan the Host Bus Adapter
ISCSI-mountVmware-14.png

Step 8:

  • The iSCSI Initiator has detected the target on the Synology DiskStation.
ISCSI-mountVmware-15.png

Step 9:

  • Right Click on the Target and click Manage Paths
    • The preceding direction may skipped for non-MPIO Environments
ISCSI-mountVmware-16.png

Step 10:

  • Select Round Robin (VMWare)
    • The preceding direction may skipped for non-MPIO Environments
  • Note that within the Path Management, that the ESXi Hypervisor is using two paths (via two subnets) to mount the same iSCSI Target.
ISCSI-mountVmware-17.png

Step 11:


Formatting the iSCSI Target for usage within the ESXi Hypervisor

Overview: This section of the article will guide the administrator in formatting the iSCSI Target for usage within ESXi Hypervisor

Step 1:

  • Within the Configuration tab, click on Storage, and click Add Storage
ISCSI-mountVmware-19.png

Step 2:

  • Select Disk/LUN and click Next
ISCSI-mountVmware-20.png

Step 3:

  • Find the iSCSI Target, and click Next
ISCSI-mountVmware-21.png

Step 4:

  • Review the current disk layout and click Next
ISCSI-mountVmware-22.png

Step 5:

  • Enter a new datastore name for this new storage.
ISCSI-mountVmware-23.png

Step 6:

  • Select a block size to use for this new storage
    • Using default settings is recommended
ISCSI-mountVmware-24.png

Step 7:

  • Final Confirmation Settings
ISCSI-mountVmware-25.png

Step 8:

  • The new datastore has been added...
ISCSI-mountVmware-26.png

Step 9:

  • ...and is ready for use
ISCSI-mountVmware-27.png

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s