HP P2000 G3 e iscsi ESXI5

Similar Questions

• recovery passwrd hp p2000 G3 fc/iscsi

  Hello

  How are you?

  I forgot my phone password

  device name: san storage

  model: hp p2000 G3 fc/iscsi controller

  How my password recovery?

  How my password recovery?

  Thank you

  Hello

  I understand that you forgot your password,

  If you have a tool rest of password you use.

  otherwise you will need to perform the recovery, you can do this by tapping the F11 key at startup, recovery

  or if you have the disk, you can do the recovery.

• vSphere on HP P2000 (aka Lefthand) - iSCSI issue

  We are looking at one of the models of the HP lefthand SAN Pxxxx I have some questions about how the device communicates via iSCSI. I read that it is extensible by adding nodes which also increases your bandwidth. I also read articles on how the writing/recieve max limitted by a single NETWORK card of 1 GB. Here is the article: http://frankdenneman.wordpress.com/2009/10/11/lefthand-san-lessons-learned/

  Now my question for ESX or vSphere on the lefthand device is, can you add NIC to increase my band bandwidth iSCSI for host of the ESX host? Say if I add a 4 HP NIC port, can I configure it to a pipe of 4 GB iSCSI and which will be by writing/recieve max speed? By section of the link, all iSCSI connections are limitted in writing/recieve in a single network adapter.

  By the link, it looks like all links and/or "allegiance connection" is limited to the unit from left to a single NETWORK card, which is of 1 GB. If this is true, then there is really no reason to buy the additional NETWORK adapter

  Any contribution is appreciated.

  Thank you

  COS,

  See the link to the doc HP running vsphere on the left.

  http://h20195.www2.HP.com/v2/GetPDF.aspx/4AA3-0261ENW.PDF

  The iscsi configuration guide is below.

  http://www.VMware.com/PDF/vSphere4/r40_u1/vsp_40_u1_iscsi_san_cfg.PDF

  Also take a look at this article

  http://virtualgeek.typepad.com/virtual_geek/2009/09/a-multivendor-post-on-using-iSCSI-with-VMware-vSphere.html

  Best regards

  DC

• How to use 4 x 1 GB for software iSCSI NETWORK interface card.

  Hello. I have a HP P2000 G3, with iSCSI connections 4 x 1 GB. I have 4 free 1 GB NIC on my 5.5 esxi server. IM wondering how I could put things upwards, so it would use iSCSI 4x1Go at the same time, so I would get a 4 Gbps to my SAN connection. Is this possible? I read something about iSCSI multi-trip and Port binding, but is all a bit confusing. It seems to me which is used for failover? I tried to put in place using a multipathing guide and got to the top and his display I 8 paths to my SAN, but it seems that a NETWORK adapter is used when considering my switch activity.

  Any help would be appreciated.

  Take a look at this blog post: http://www.virtualtothecore.com/en/howto-configure-a-small-redundant-iscsi-infrastructure-for-vmware/

• Deploy ESXi 5 with HP P2000 G3

  Hi all.

  I'm trying to deploy ESXi on our new equipment, which is:

  HP DL360 G7

  HP P2000 G3 10GB iSCSI

  HP NC522SFP iSCSI adapter

  I was not able to connect ESXi to the table so far. It seems possible only when I add a "software iSCSI adapter. Is it necessary or not? Here are my steps so far:

  1 added new vSwitch with the VMkernel connection type

  2. include the paths of two data from my card iSCSI (listed as vmnic4 and vmnic5)

  3. go in "storage adapters". Strangely, I see 4 devices (vmhba33-vmhba36). I expect two if I'm not mistaken.

  4. go in the properties of each.

  5. go in "Network Configuration".

  6 Add the binding of ports

  At this point, I don't see my storage interfaces.

  If I repeat this procedure after the addition of iSCSI Software and try to add links to it, I see my 10 GB interfaces.

  Sorry if not being not clear enough. I will be happy to provide you with more details. In general, if there is a document of VMware explaining how to deploy it in my case, I would be grateful for a link.

  Also, I saw that - same ESXi seems to recognize the adapter ' HP provides another driver. Tried to install this driver and sees no difference. Inside storage adapters, it is always referred to as "Broadcom iSCSI adapter".

  Thank you

  GRP wrote:

  I see. Strange however, since this card has been recommended/supplied by HP itself. Looks like a low end (even if the price was not very cheap...), the way that describe you. So, to have this way of the card we will face a drop in performance (compared with a HBA)? Clearly, this means our ESXi host will run its virtual machines slower, because it will also have to manage the iSCSI traffic?

  Not at all.

  Software iSCSI in ESXi, has demonstrated in many places to be as fast, if not not not faster, that the use of unloading iSCSI in hardware cards.

  Install the adapter software - it is a correct and generally recommended to set up this server.

• Suggestion of hardware

  Hello guys

  We will use the ESX Server and I need suggestions for material, here's the list of what we buy, could you please check what I forget?

  Any advise?

  We will have total 12 servers who virtualize

  Here's what I mean

  XHP DL580 G7 E7540 40 GB 4 P 3

  20 X HP 146GB 6G SAS 15K 2.5 DP PLUG

  6 X HP STORAGEWORKS 4GB PCI-E HBA

  1 x HP P2000 G3 FC/ISCSI DUAL CONT SF

  20 X HP 300GB 6G SAS 10K PLUG

  2 X HP DISK ENCLOSURE D2700

  1 X HP MDS9124 8 PORTS ACTIVE FABRIC SWI

  8 X HP LC - LC 5 M CABLE SET

  1 X VMWARE ADV ACC 6PRO

  1 X VMWARE ADV ACC 1Y PSN 6PROC

  Could you please tell me what I forget on the virtual platform of Vmwae?

  Thank you

  Yes. 2 switches for redundancy.

  Your host should also have redundandt NIC. Having 2 NICs for Public traffic going to the network switch/router.

  2 NICs for SAN traffic. If you use fiber then HBA. Those who go directly to the fiber switches, which then connect to the San.

  You may also have a separate network for your vCenter management traffic and/or the vmotion, etc. fault tolerance. This would require and additional 2 cards network and VLAN separated.

• ESXi5: File server: 8TB iSCSI LUN

  I'll put up an ESXi5 and plan to host my server files on it. The file server uses storing a Raid6 NAS available on iSCSI (with MPIO).

  The server storage is about 8 TB, which will be shared via a Windows 2008R2 Guest VM.

  Now I need to find the best options to expose the storage for Windows.

  Looks like my options are:

  -Use VMFS on iSCSI and vmdk files ordinary LUN.

  -Use RDM (do not know if it works with iSCSI) and provide a RAW disk to the vm file server.

  -Use of iSCSI directly from the Windows VM (can cause a high CPU utilization), prove less effective.

  The most common and options of would apply we would be the first option, however I would be worried to have my WHOLE being in a single VMDK file file server (or several)? If it gets corrupted, I would I lose its content business? Is this something that happens? Especially since this is managed ethernet (iSCSI)?

  Really this all come down to: vmdk is safe, and is there a way to get it back where the vmdk file is corrupt (in the same case).

  Additional info:

  I didn't need the partition of data to be snapshoted if I snapshot files server.

  Thank you!

  I mounted the iscsi Target inside the bone of the VM. Works very well. I also have a secondary backup iscsi NAS for increased security outside (even RAID 6 is not flawless) and I do weekly backups of my virtual machines to a different data store. Storage of the user in a vmdk files is a bad choice. If all this is corrupt (or just the OS) you will have a hard time to retrieve data from a VMFS partition. There are very few options to read under Windows or Linux. Better safe than sorry

  Concerning

  Tony

• Need suggestion for storage on the server ESXi5 iSCSI configuration

  Hi friends,

  I am new to vmware & I want t know if I have physical iSCSI card installed in my ESXi 5 & it connect directly to the server and then again I want to configure virtual SCSI for connection to the VM card? If so, why?

  Thank you and best regards,

  Pradip

  See page 63 of the http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf link

• ESXi5 + iSCSI NAS with MPIO, fairly reliable for file server?

  I look at the different options to learn where to run a file server. The most logical choice would be to run a Windows Server 2008R2 in an ESX host using the esx storage, however the esx use accesed by iSCSI NAS storage. I'm worried about losing files due to corruption of either the VMFS or VM-file, this could happen with any type of storage, but the fact that the system of whole files be stored in a single VMdisk care.

  I have a few other options, such as:

  (1) host the files directly on the NAS Server (it is supported)

  (2) set up a number of logic of the NAS unit directly in the comments of Windows Server (avoiding the use of a VM disk)

  The approach let ESXi dealing with iSCSI would be more integrated, but I will be more at risk? If something happens to the VMdisk I would lose all the files it contains, it is probably something (power loss, iscsi network failure?), are there any tools to recover a corrupted vmdisk?

  Thank you

  You'll be fine using an iSCSI LUN in ESX.  Your NAS device should be the biggest concern (if you lose the storage, you would lose any protocol any way).  Just make sure that it is a business device.  You could also potentially use NFS from your NAS device (if supported).  As with any environment, make sure that you back up!  You will not be at risk using iSCSI as an RDM.

• ASM & iSCSI - disk has gone forever

  I installed Centos 5.9 (don't ask...), my storage is a drive Bay of 10 scsi drives connected via the iscsi Protocol, and I installed grid Infrastructure 11.2.0.3 (software only).

  I was setting up ASM, but when I added the candidate disks, it never ended, then I canceled. After several futile attempts to get it to work, I decided to reboot the server.

  I think I saw her because before restarting the server, I had uninstalled ASMLib.

  The server wouldn't start due to errors related to the disks. After doing a bit of magic, I disabled the connection on the discs and was able to start, but now I have some problems when you try to connect to the disks:

  starting at $ /etc/init.d/iscsid

  $ chkconfig--add iscsi

  $ chkconfig iscsi on

  $ iscsiadm m - t sendtargets Pei 10.9.254.2 discovery

  10.9.254.1:3260, 1 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  10.9.254.9:3260, 2 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  10.9.254.2:3260, 3 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  10.9.254.10:3260, 4 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  10.9.254.3:3260, 5 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  10.9.254.11:3260, 6 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  10.9.254.4:3260, 7 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  10.9.254.12:3260, 8 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  Then I try to connect to the Portal 10.9.254.2 (I'm not sure how to determine what portal should I use, but it used to work before):

  $ iscsiadm, node m t iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc - l Pei 10.9.254.2

  But it never ends, so I have to cancel it. Looks like it's connected and work:

  $ iscsiadm-m session

  TCP: [8] 10.9.254.1:3260, 1 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  TCP: [9] 10.9.254.3:3260, 5 iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc

  .. .but it does not work:

  $ iscsiadm m - session-P3

  (...)

  Attached SCSI devices:

  ************************

  The host number: 5 status: running

  SCSI5 Channel 00 Id 0 Lun: 0

  Attached scsi disk sda status: unknown

  Furthermore, I can't see the disks! (sda, sdb, sdc,...)

  $ ls-l/dev/s *.

  lrwxrwxrwx 1 root root 3 6 Feb 17:05 / dev/scd0-> sr0

  CRW - 1 root root 0, 21 6 Feb 17:05 / dev/sg0

  CRW - 1 root root 1, 21 feb 26 12:30 / dev/sg1

  CRW - 1 root root 21, 10 Feb 26 14:31 / dev/sg10

  CRW - 1 root root 21, 2 feb 26 12:32 / dev/sg2

  CRW - 1 root root 21, 3 Feb 26 13:02 / dev/sg3

  CRW - 1 root root 21, 4 feb 26 13:02 / dev/sg4

  CRW - 1 root root 21, 5 feb 26 13:31 / dev/CE5

  CRW - 1 root root 21, 6 feb 26 13:33 / dev/CE6

  CRW - 1 root root 21, 7 feb 26 14:01 / dev/CE7

  CRW - 1 root root 21, 8 Feb 26 14:01 / dev/sg8

  CRW - 1 root root 21, 9 Feb 26 14:30 / dev/sg9

  CRW - 1 root root 10, 231 6 Feb 17:05 / dev/snapshot

  BRW - rw - 1 root disk 11, 0 6 Feb 17:05 / dev/sr0

  lrwxrwxrwx 1 root root 15 6 Feb 17:05 / dev/stderr->/proc/self/fd/2

  lrwxrwxrwx 1 root root 15 6 Feb 17:05 / dev/stdin->/proc/self/fd/0

  lrwxrwxrwx 1 root root 15 6 Feb 17:05 / dev/stdout->/proc/self/fd/1

  CRW - 1 root root 4, 0 6 Feb 14:04 / dev/systty

  The strange thing here is just beginning, in/proc/partitions I can see only of sda. But the remaining machines appear progresively... after an hour, I can see all the:

  $ cat/proc/partitions

  name major minor #blocks

  292935982 0 104 cciss/c0d0

  104 1 104391 cciss/c0d0p1

  cciss/c0d0p2 2 104 292824787

  253 0 286720000 dm - 0

  1 253 6094848 dm - 1

  8 0 96679680 sda

  8 16 96679680 sdb

  8 32 96679680 SDC

  8 48 96679680 SDS

  8 64 96679680 sde

  8 80 96679680 homeless

  96679680 96 8 sdg

  8 112 96679680 sdh

  8 128 96679680 sdi

  8 144 96679680 LDS

  8 160 96679680 sdk

  8 176 96679680 sdl

  At the end of the day, I see 2 devices as 'unknown' and others as 'running '. But I can't even fdisk them:

  $ fdisk-l/dev/sda

  Nothing is returned. We will try to create a partition:

  $ fdisk/dev/sda

  Unable to open/dev/sda

  I can't access any device of sdX, because there is not one in/dev.

  This is the log that I got when I tried to connect to the target using the iscsiadm command:

  6 Feb 15:16:55 kernel bat-cvracdb02: scsi5: iSCSI Initiator on TCP/IP

  6 Feb 15:16:55 bat-cvracdb02 kernel: vendor: HP model: P2000 G3 iSCSI Rev: T250

  6 Feb 15:16:55 kernel bat-cvracdb02: Type: the Direct access ANSI SCSI revision: 05

  6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: 193359360 512-byte hdwr (99000 MB) sectors

  6 Feb 15:16:55 bat-cvracdb02 kernel: sda: write protect is off

  6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: drive cache: write back

  6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: 193359360 512-byte hdwr (99000 MB) sectors

  6 Feb 15:16:55 bat-cvracdb02 kernel: sda: write protect is off

  6 Feb 15:16:55 bat-cvracdb02 kernel: SCSI device sda: drive cache: write back

  6 Feb 15:16:56 bat-cvracdb02 iscsid: Connection1:0 to [target: iqn.1986 - 03.com.hp:storage.p2000g3.121514b3cc, Portal: 10.9.254.2,3260] by [iface: default] now works

  6 Feb 15:17:05 bat-cvracdb02 kernel: sda: < 3 > connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295476749, last ping 4295481749, now 4295486749

  6 Feb 15:17:05 core bat-cvracdb02: connection1:0: detected error conn (1011)

  6 Feb 15:17:06 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)

  6 Feb 15:17:06 bat-cvracdb02 udevd-event [3628]: wait_for_sysfs: waiting for ' / sys/devices/platform/host5/session1 / target5:0:0 / 5:0:0:0 / ioerr_cnt' failed

  6 Feb 15:17:09 iscsid bat-cvracdb02: could not online LUN 0 err 2.

  6 Feb 15:17:09 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)

  6 Feb 15:17:24 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295495002, last ping 4295500002, now 4295505002

  6 Feb 15:17:24 core bat-cvracdb02: connection1:0: detected error conn (1011)

  6 Feb 15:17:24 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)

  6 Feb 15:17:27 iscsid bat-cvracdb02: could not online LUN 0 err 2.

  6 Feb 15:17:27 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)

  6 Feb 15:17:37 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295508253, last ping 4295513253, now 4295518253

  6 Feb 15:17:37 core bat-cvracdb02: connection1:0: detected error conn (1011)

  6 Feb 15:17:38 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)

  6 Feb 15:17:40 iscsid bat-cvracdb02: could not online LUN 0 err 2.

  6 Feb 15:17:40 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)

  6 Feb 15:17:50 kernel bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295521254, last ping 4295526254, now 4295531254

  6 Feb 15:17:50 kernel bat-cvracdb02: connection1:0: detected error conn (1011)

  6 Feb 15:17:51 iscsid bat-cvracdb02: kernel reported connection iSCSI error state (1011) 1:0 (3)

  6 Feb 15:17:53 bat-cvracdb02 iscsid: could not online LUN 0 err 2.

  6 Feb 15:17:53 bat-cvracdb02 iscsid: connection1:0 is operational after recovery (1 attempts)

  6 Feb 15:18:03 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295534255, last ping 4295539255, now 4295544255

  6 Feb 15:18:03 core bat-cvracdb02: connection1:0: detected error conn (1011)

  6 Feb 15:18:04 bat-cvracdb02 iscsid: reported core connection iSCSI error state (1011) 1:0 (3)

  6 Feb 15:18:06 iscsid bat-cvracdb02: could not online LUN 0 err 2.

  6 Feb 15:18:06 iscsid bat-cvracdb02: connection1:0 is operational after recovery (1 attempts)

  6 Feb 15:18:12 bat-cvracdb02 avahi-daemon [3321]: invalid query package.

  6 Feb 15:18:16 bat-cvracdb02 last message repeated 6 times

  6 Feb 15:18:16 core bat-cvracdb02: connection1:0: ping timeout of 5 seconds, recv timeout expires 5, last rx 4295547259, last ping 4295552259, now 4295557259

  6 Feb 15:18:16 core bat-cvracdb02: connection1:0: detected error conn (1011)

  6 Feb 15:18:16 bat-cvracdb02 kernel: sd 5:0:0:0: error code not supported

  6 Feb 15:18:16 bat-cvracdb02 kernel: sd 5:0:0:0: SCSI error: return code = 0x000e0000

  6 Feb 15:18:16 bat-cvracdb02 kernel: result: hostbyte = DID_TRANSPORT_DISRUPTED driverbyte = DRIVER_OK, SUGGEST_OK

  6 Feb 15:18:16 bat-cvracdb02 kernel: error of the buffer i/o on device sda, logical block 0

  6 Feb 15:18:17 bat-cvracdb02 iscsid: reported core connection iSCSI error state (1011) 1:0 (3)

  6 Feb 15:18:19 bat-cvracdb02 iscsid: could not online LUN 0 err 2.

  6 Feb 15:18:19 bat-cvracdb02 iscsid: connection1:0 is operational after recovery (1 attempts)

  I also tried to reinstall ASMLib, network and iscsi tools.

  I'm tired of this problem, please kindly share ideas. No one could help me on the Centos forum.

  Finally, I solved this.

  I had to use MPIO, because when I accesed drives node of the wave, all was fine, but when I accessed the other node disks, disks began to show problems.

• The upgrade to ESXi 4.1 with storage iSCSI software to ESXi 5.5

  I intend to upgrade ESXi 4.1 with which I have attached to ESXi 5.5 iSCSI software storage

  I've updated all my guests who were on the SAN storage with no problems.

  I would like to know that if it there's nothing I should take care before I update the host connected iSCSI to ESXi 5.5, as for the hosts with SAN attached storage I made to remove the cables of SAN before upgrading the host.

  Also, if all known problems, you will be informed during the upgrade to ESXi 4.1 to ESXi 5.5 with iSCSI Software storage, please let me know?

  If there is no different process to upgrade coz in ESXi 4.1 I do not see this link ports of iSCSI vmkernel ports software iSCSI but I know in ESXi5.5 we have to or I just launch a procedure of standard upgrade via the Update Manager and everything will be taken care?

  Thanks in advance

  With ESXi prior to version 5, linking ports had to be done via command line. However, if it has been configured correctly, you should be able to upgrade to ESXi 5.5 (assuming that the host has not been previously updated since version 3). BTW. the last time that I disconnected the host of storage for an upgrade has been with ESX 3.0.

  André

• iSCSI Initiator Port Group error

  Problem adding in the vmk second to an existing iSCSI vSwitch.  Original config was 2 vmks - all worked successfully.  1 vmk has been removed to solve network problems.

  Re-created the 2nd vmk, but when going down one of the cards the unused category as soon as active network OK is selected the message "this vmkernel port group contains a NETWORK card.

  which is related to an iSCSI initiator.  Change its settings could disrupt the connection to the iSCSI data store"is displayed.  The response options are Yes or no.  A screenshot is attached.

  vCenter is version 5.0 U1b.  The host is ESXi5.0 U2 and mode of maintenance with none of the guests.  The host on the local disk not stop SAN.  I can safely click Yes, then go back and

  move the vmnic or is there a better way to fix this problem.  Thank you.

  Thanks for sharing the information. Please try below steps:

  Step 1. Remove links in the existing port and reboot the host.

  Step 2. Change the port iSCSI and vmnic preferred value to active group and move the second unused NETWORK card.

  Step 3. Change group 2-port iSCSI and vmnic preferred value in the active State and move the other card unused NETWORK.

  Step 4. Add vmk1 and vmk2 under links in the port iScsi initiator network configuration.

  I hope steps above will help to solve the problem. If you encounter the error even if you please let me know.

• Questions of ESXi 5.1 ISCSI--&gt; cannot establish a network connection (continued)

  Hello world

  I had a problem there not too long ago (thread link below) where my ESXi hosts could not establish a connection with an IBM DS3500 on start up and "rescan", however their connectivity worked correctly without any problem after commissioning and when a "rescan" finished. We determined that the most likely cause was the unit IBM itself. However, I wasn't completely satisfied.

  In order to deepen the question and dismiss my guests being the problem, I created a unit ISCSI myself with two new hosts of ESXi 5.1 (version 1157734).

  ESXi signals that it cannot connect to the initiator ISCSI (network error) - but it can run virtual machines and browse data stores?

  The configuration is the following:

  Test environment:

  2 x ESXi 1157734 hosts

  1 x server Freenas ISCSI (ZFS R10)

  At the start of my ESXi hosts in the test environment, download the same error as our production environment. They also put on the same error message (in the event log) when I "rescan" map of the ISCSI software. However, once the scan is finished, I can't see any error message and everything continues as it should (Round robin, active active). I can get a brilliant flow also. It's as if the errors are almost... false positives?

  Example of the error message (test environment):

  Connection to the iSCSI target

  IQN.2011 - 03.org.example.istgt:iscsi on vmhba35

  @ vmk2 has failed. The iSCSI initiator couldn't

  establish a network connection to the target.

  error

  17/10/2013-08:33:35

  ESXi hosts are configured as follows:

  Test environment:

  • (ESXi hosts) Two network cards for ISCSI, one for VM traffic
    • NIC1: 10.20.20.2/24, NIC2: 10.30.30.2/24
  • (Freenas) Two network cards installed on the ISCSI device (dedicated to ISCSI traffic)
    • NIC1: 10.20.20.1/24, NIC2: 10.30.30.1/24
  • ESXi is set to round robin, which works properly (I can max on both ports at the same time)
  • Two VMKs are related to the ISCSI Software initiator and defined to dynamically discover the two ISCSI addresses
  • Unity of ISCSI and the hosts are not on the VLAN, the switch is dedicated to ISCSI traffic (However in the production, the two networks are separated by VLAN.) I removed the in the test environment to simplify everything)
  • The vSwitches (who hold a single VMK for ISCSI) are fixed:
    • "Promiscuous" mode: reject
    • Change of MAC address: accept
    • Forged passes: accept
    • The traffic shaping: disabled
    • No NIC teaming (obviously)
    • Each VMK inherits the settings of these

  Quick points:

  • My hosts use VMware approved NIC in my test environment. My production environment runs on full VMware hardware approved
  • Can I use ping of vmk join each each VMK ISCSI initiator
  • I can use the nc-z target_ip 3260 command to check connectivity to the port
  • The ISCSI test has two network adapters, each on 1 Gbps ports
    • I can get around 800mbps per port when copying lots of files (both ports are active)
    • I see no error in copying a large number of virtual machines around, or backup files
  • I only see errors on start up and "rescan".
  • I have two network adapters on each host ESXi dedicated for ISCSI. Each NETWORK card has a single VMK. A single mapped port on ISCSI, the other is mapped to port B (I used to have two VMKs by nic, but I removed that in order to simplify everything)
  • I have updated the firmware on our switch of production. No results
  • I've used 4 different switches in order to avoid a network problem. No results
  • I tested ESXi versions 5.0, 5.1 (799733 & 1157734), all have the same mistakes
  • The ISCSI ports are on different networks according to the VMware (I was told not to put on the same network VMKs)

  Any ideas? It's starting to drive me up the wall. Any help would be greatly appreciated

  I've seen several times in recent months and was beginning to think it is specific to the HP P2000 units because it's the only time wherever I saw him! I now believe that ESX/iSCSI rather than issues of driver or table.

  On my last install, I found that errors occur as soon as the table is connected, i.e. before any storage is displayed.

  Single host ESX, no guests. 2 Intel adapters to 2 HP past by dedicated HP P2000 1 GB table with all 8 wired ports.

  All roads are good, all lights are in the State expected.

  It did not affect the use of the storage in question to any site, so there has been no need / a momentum of any further investigation.

  B! 886y annoying however!

• RS 5 with netapp SRA, FCOE site iSCSI with RDM

  Hi team, could someone please help to veify if it works in this scenario.

  We have PROD site running vmware vcenter 5.0, esxi5.0, SRM 5.0, Netapp 3210 ONTAP8.1 version file server. The VMs are windows Server2008, MS SQL2008 as major DB. Virtual RDM database files. Only FCOE for this site. AD is a physical Server 2003. The rest are virtual machines

  We offer you to have SRM for DR site deployment. The DR site is synchronized with netapp SRA snapmirrror, controlled by the console SRM5.0. Recovery site has no FCOE, only iSCSI and NFS license availble. Always RDM but using iScsi. vCenter 5.0, 5.0, netapp ONTAP8.1 2040 esxi.

  My questions are:

  1. If VMware SRM support DR failover for this case with the different protocol, PROD is FCoE, iscsi DR

  2. If the SRM supports failover with RDM in our case

  3. If the AD DR Server site need to be installed as a new best practices, or we will have to use SRM to switch production announced on website of Dr. What is recommended.

  4. If the physical AD can be kept as the common way and always taken SRM supported

  5. to the recovery site, which is the best practice? To use NFS to store data and iSCSI for iscsi? Or store data and RDM using iSCSI LUNS to simplify?

  
  

  Thank you!
  

  1. Yes
  2. Yes
  3. I would recommend if possible having a domain controller AD, already running on the DR site - it may be a virtual machine
  4. Yes, the PROD site domain controller can be physical
  5. I'd keep all compatible iSCSI so so -.

• a few questions about ESXi and SAN CF with HP P2000 G3

  Hello everyone!

  I am new to ESXi and SAN, then I need help for her.

  I have Encolosure C7000 system with 4 blades BL460c already installed ESXi 5.1U1 (HP custome ISO image). Everything works fine now, but I do not understand something:

  -What is the management network which I use vSphare Client to connect to? It is a private network to manage ESXi servers what difference with VMnetwork used by Virtual Machines? Because I've set up an IP address for this connection manually, but it is of course separate with IP addresses, I used on Virtual Machines.

  -If my system has problem, so I have to reinstall ESXi, license keys can be used again? Already, I have 8 license key for 4 blades (2 CPUs per server), but they have not yet used. Because I am new to ESXi, cause I had to reinstall ESXi several times to understand.

  -When I install successful ESXi, I don't know how to start working with SAN. What should I configure P2000 before it be plugged into the SAN switch? Or I can plug it then config later? Because I don't see it on the ESXi server. And on the OS I installed on the Guest Virtual Machines, I see nothing new in Device Manager. I thought that this guest operating system will detect the mezzanine card. But I see only mezzanine card that connect to the P2000 by SAN switch in ESXi (see image here http://img203.imageshack.us/img203/684/dsc04088k.jpg ). To my knowledge, I think that ESXi server have to detect the P2000 as hardware device. Can someone teach me step by step install and configure a San on ESXi? Or show me a tutorial because I searched but only iSCSI results.

  My devices:

  01 7.1 HP BLc7000 CTO 3 IN LCD ROHS Encl.

  04 BL460c G8 servers HP FlexFabric 8.5 10 Gb 2 p 554FLB FIO blade adapter

  02 7.3 HP B-series 8/12 c BladeSystem SAN Switch

  01 HP P2000 G3 MSA FC Dual Controller

  Thanks for any help, sugession or comment!

  -What is the management network which I use vSphare Client to connect to? It is a private network to manage ESXi servers what difference with VMnetwork used by Virtual Machines? Because I've set up an IP address for this connection manually, but it is of course separate with IP addresses, I used on Virtual Machines.

  Yes, it's a separate network used only for traffic management between ESXi hosts and vCenter - it is also the network used to connect to the environment - that's different, then the network used by your virtual machines

  -If my system has problem, so I have to reinstall ESXi, license keys can be used again? Already, I have 8 license key for 4 blades (2 CPUs per server), but they have not yet used. Because I am new to ESXi, cause I had to reinstall ESXi several times to understand.

  Yes the license keys can be reused, and if you use vCenter licenses will be managed by vCenter

  -When I install successful ESXi, I don't know how to start working with SAN. What should I configure P2000 before it be plugged into the SAN switch? Or I can plug it then config later? Because I don't see it on the ESXi server. And on the OS I installed on the Guest Virtual Machines, I see nothing new in Device Manager. I thought that this guest operating system will detect the mezzanine card. But I see only mezzanine card that connect to the P2000 by SAN switch in ESXi (see image here http://img203.imageshack.us/img203/684/dsc04088k.jpg ). To my knowledge, I think that ESXi server have to detect the P2000 as hardware device. Can someone teach me step by step install and configure a San on ESXi? Or show me a tutorial because I searched but only iSCSI results.

  Yes, you will be able to configure the San later - by default, the virtual machine will not see the SAn, as it is virtualized by your ESXi host - all the VM will see is a virtual SCSi disk - this doc's guide to vmware for storage - http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-511-storage-guide.pdf - you can visit the website of HP they might have documentation on configuring P2000 for vSphere -.