MD3000i iSCSI host RHEL4 connetion problems

Similar Questions

• Fundamental and MD3000i ISCSI concepts

  Hi all

  I try to understand the concepts in a MS Windows and especially the MD3000i iscsi environment and online help does not help much. I understand that you need an innitiator on a host to connect to a target. A target is a San with a large logic unit number or multiple LUNS. A target may have a gigabit ethernet port or two. Each NETWORK adapter on the target must have a unique IP address. This is the case with MD3000i with one controller or connection "simplex". Let's say I set up 4 starts: exchange, sharepoint, sql, and files. These 4 starts will connect to 4 servers. Each server has two NETWORK adapter, an intranet, an iscsi network.  I only use a single NIC on the MD3000i, as I understand it, if I put the IP address of the target when configuring host innitiator on 4 servers. This means that a 1 GB connection is shared between 4 servers. Is this correct?

  Second, by presenting the diskgroup to the appropriate host, avoid a host 'touch' the another diskgroup host?

  For example, using the second NIC on the MD3000i, I will divide halved. I have to point two servers to a new IP address in the MS innitator and attend the diskgroup these two hosts correctly in the MD3000i. Is this a correct concept?

  Is it possible to combine two network cards on the MD3000i so that its total output/bandwidth is 2 GB?

  Now we have a second controller, which makes things more confusing for me. At this point, I would like to note that I speak not of "high availability of applications. In one controller, a controller has 4 starts. IIF this controller 0 failed, I'll lose data. In one two controllers, two controllers are configured as active/active. My understanding is that controller 0 can now own one or all four starts (or 2 own diskgroup and controller 1 has the diskgroup remaining, 3, and 4). So, in this case, my server must point to the 2 different IP addresses on the second controller. For simplicity, all IP addresses are the same subnet. Assuming that the controller 0 is broken, the diskgroup 1.2 will change ownership to controller 1.  Now, controller 1 will hold 4 starts. However, my server 1.2 will lose the iscsi network connectivity. In order for me to get the data back, I'll have to reconfigure the iscsi innitator pointing to the IP address of the controller 1. The question is, what IP addresses on the two network adapters on controller 1.

  I understand that if I want to achieve high availability of applications, I have 2 network cards on the server dedicated for iscsi between two controllers.

  I read this article and it has confused me more:

  http://support.Dell.com/support/eDOCS/systems/MD3000i/multlang/TS/FR483-info%20update/FR483A00MR.PDF

  According to this article: "two network cards on a controller can be aggregated to provide optimal performance. A host can be configured to simultaneously use the bandwidth of both ports on a controller of virtual disks, held by the access controller". This means that the total production is 2gbs? So in my case, is it possible to do it when I have a NETWORK to the iscsi network interface card? How to configure the host to take advantage of this?

  I know that I have a lot of questions, since it is a new concept for me. Thanks in advance for your time.

  
  

• While playing online games, I get this message. McAfee service as host encountered a problem and must close.

  Error messages

  I have Windows XP Home Edition. While playing online games, I get this message. McAfee service as host encountered a problem and must close. McAfee, as tried to help him stop for a day, then did it again. As MS sent me on this forum as everyone has an answer to this problem.

  Microsoft Security Essentials is an antivirus which is free.  You can also get www.malwarebytes.org for malware.

  Steve

• Hosted wireless network problem

  I'm currently located in a place where the WiFi you buy will only link with one device and the IP and MAC addresses to confirm the device before you connect to the internet. I am to avoid paying for both (laptop and smartphone) devices through a wireless network but my laptop using Microsoft Virtual WiFi Miniport Adapter. However, when I start the hosted network, either through the "netsh wlan start hostednetwork" command in the command prompt or via the software free virtual router Manager, my computer freezes completely and does not respond to anything except a hard stop. When I started this, everything worked well and I could use the network hosted without any problems, but in the last few weeks, I had to shut my computer down several times a day because of this problem. Can someone help me understand why my computer keeps freezing? Any help will be greatly appreciated.

  To help you, we suggest that you try to check on the link below:

  WiFi/SoftAP virtual fails to start with "the hosted network could not be started" on Windows 7 and Windows Server 2008 R2

  An update on the result.

• Unable to connect to the MKS: the certificate of the remote host has these problems:

  Hello

  We have a host of ESXi 4 cluster running any vSphere 4.1.  Recently, I started to upgrade to update 2 and all the additional fixes.  After the upgrade of the vCentre server to the latest version (or maybe before I can't noticed) an of are hosts began to show the following error whenever I tried to connect to the console of any guest on this host.

  Unable to connect to the MKS: the certificate of the remote host has these problems:

  It lists any problems at all and no error display in the event log that it simply does not work.  I had a prod around the internet and found nothing.  I then rebuilt the host to exclude and the problem remains.

  Any help would be much appreciated.

  Thanks in advance

  David

  If you can connect to the Console remotely using VMware Infrastructure (VI) Client connected directly to the host, take a look at vmware KB to connect to a remote virtual machine fails with the error: the certificate of the remote host has these problems

  but more generally - remove host to vCenter inventory and then add the host to the back, take a look at opening in the console of the virtual machine after a new installation of ESXi or ESX fails with the error: the host certificate chain is not complete and could not connect to the MKS: the certificate of the remote host has these problems

• with vSphere and Dell MD3000i iSCSI design

  I installed a server ESX 4 (the first of three for this cluster), and a SAN Dell MD3000i iSCSI connected through two switches Dell PowerConnect 2816.

  Now I read the VMware 'iSCSI SAN configuration guide', and I wanted to just make sure I did the design correcly.

  I have connected a Teddy ESX (vmnic1) to one of the pSwitch and another (vmnic5) in the second. This pSwitch SAN iSCSI ports are connected, so that one of the switches carry the 10.10.10.x subnet and the other the 10.10.11.x (see IP plan below)

  The two natachasery have a vSwitch each (a do not share), a portgroup each and are configured on different subnets, IP (see attached screenshot)

  Plan of intellectual property:

  Port iSCSI-10 group (VMkernel): 10.10.10.1

  Port group iSCSI-11 (VMkernel): 10.10.11.1

  0-0 SAN controller: 10.10.10.10

  SAN 0-1 controller: 10.10.11.10

  Controller 1-0 San: 10.10.10.11

  SAN 1-1 controller: 10.10.11.11

  By using this configuration, I could see four different paths for each LUN. and I was able to make the ESX Server will switch to different switches/controllers as I unplug the vmnic1 network cables and vmnic5, one at a time.

  Then I found the section on 'esxcli' configuration guide and multipathing configuration, which I carried out in accordance with the instructions ("esxcli swiscsi nic add - n vmk0 d vmhba34" and "esxcli swiscsi nic add - n vmk1 vmhba34 d ')

  Now I have eight different paths for each logic unit number, three of whom are 'Active' and an 'active (i/o)' (see my screen attached the capture).

  So, my questions are:

  1. the eight paths to each LUN really normal in designs of iSCSI?

  2. is my vSwitch/Teddy/pSwitch correct design choices?

  Thanks in advance!

  / Anders

  @hennish,

  As long as your new design continues to meet your needs of failover and workload, your infrastructure design should be fine.

  But you might want to take a look at this design Dell. In particular, step 12 that configures multiple paths in round-robin policy using the VI GUI client, for

  Each LUN exposed to the ESX Server. This allows balancing on two

  Active paths to the LUN. After completing this step, you should see2 "IO Active" paths.

  Kind regards

  KongY@Dell Inc.

• faild to connect to the MD3000i iSCSI

  Hello!

  Our company bougth a MD3000i storage, PowerConnect 5448 switch and we have some 360-390 Optiplex745-755 and workstation. I installed everything step by step, I can config the storage with disk MD management, and I installed Microsoft iSCSI initiator.

  The ethernet ports and iSCSI ports have obtained the IP address, name of the initiator is the same as

  the name of the initiator of the host.

  Well, the problem is that an initiator cannot connect to the MD3000i.

  What's wrong?

  
  

• not visible on the ESXi LUN iSCSI hosts

  So I have a bit of a strange and hoping the community can help me to understand. In my lab at the House, I have 3 x ESXi 5.1 Build 799733 hosts x 2 guests are the same hardware (BUD Intel) and the other host an old HP flat desk. I am running CE Nexenta 3.1.3.5 on a Microserver HP which provided the iSCSI storage to HP desktop computer. The 2 new Intel NUC VMware hosts however, I am unable to get any iSCSI storage visible to them. Software iSCSI adapter is enabled, peut vmkping storage to the host and the target will appear on the static discovery tab. The configuration appears to be identical between the 2 However, the hardware is different... I have a new analysis on the host and no devices appear. Now the obvious answer is there must be a security issue on the side of Nexenta... but the 3 hosts are all part of the same group initiator. Confirmed and copied the IQN name over and over again. I still think that this is maybe a matter of Nexenta, but maybe it's something else.

  Check the vmkernel.log file contains the following information after a new analysis...

  (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1547: device rescan time 17 msec (total number of 5 devices)

  (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1550: Filesystem probe time 85 msec (4 of 5 surveyed devices)

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) SFS: 4972: pilot no. FS claimed "on the remote control": unsupported

  Anyone got any ideas?

  Problem solved.

  Appears that it was a problem of connection iSCSI ports. There is only a single teddy bear in each of these hosts and allowing the port bindings vmkernel on initiator iSCSI under 'Network Configuration' result not being iSCSI target devices is not visible. Removed the vmkernel port binding and made a new analysis. Cameras then showed upward.

• ISCSI EqualLogic PS6000 path problem

  Hello

  I have a PS6000 2 Powerconnect 5524 and 2 R710

  Ports 1 and 2 of my san are Switch1 and ports 3 and 4 switch 2, ports are marked on VLAN10 one two swjtches, they ar not stacked

  The legs of my san ports are:

  Port 1 10.10.1.10 switch 1
  2 port 10.10.1.20 switch 1
  Port 3 10.10.1.30 switch 2
  4 port 10.10.1.50 switch 2

  Virtual IP San: 10.10.1.200

  My R610 has an vmnic3 on switch1 and a vmnic5 of the switch2, ports are VLAN10 taggued

  With this configuration I IC see my 4 way san

  If I place a 10.10.1.50 on vmnic3/vmk0 switch1 ISCSI1 vmkernel port I see my san 10.10.1.10, 10.10.1.20, or 10.10.1.200

  If I place a vmkernel ISCSI2 port 10.10.1.60 on vmnic5/vmk1 the switch2 I cannot see my san

  If I delete ISCSI1, I can see my san ISCSI2 and vmnic5

  If I place ISCSI1 and ISCSI2 on VLANs separated, I can see my san on two NICs, so I have 4 path to the San

  I have seen that:

  ~ # esxcfg - road - l
  VMkernel itineraries:
  Interface of network gateway subnet mask
  10.10.1.0 255.255.255.0 subnet local vmk0
  10.10.3.0 255.255.255.0 subnet local vmk4
  10.10.4.0 255.255.255.0 subnet local vmk3
  by default 0.0.0.0 10.10.1.254 vmk0

  Perhaps a road problem?

  THX

  I have install up to EQLs with vSphere several times. Dell and EQL recommend a one-to-one ratio of iSCSI VMkernel ports to physical network interface cards. If you have 2 NICs per host dedicated to iSCSI, you should have 2 VMkernel ports on each host (and remember, they must be configured exactly the name of vMotion work). They also recommend the same number of network adapters on each host that you have on the SAN controller - SAN 4 controller iSCSI NIC - 4 NICs per server for iSCSI.

  Despite the paths physical and network cards redundant, each VMkernel port is only a single logical path.

  Here's how I would do it with a series 6000 EQL (4 ports per controller)

  R710 #1:

  VMkernel Port 1 - NIC physics 1 - switch A

  VMkernel Port 2 - Phyiscal NIC 2 - switch has

  VMkernel Port 3 - NIC physical 3 - switch B

  VMkernel Port 4 - NIC physical 4 - switch B

  R710 #2:

  VMkernel Port 1 - NIC physics 1 - switch A

  VMkernel Port 2 - Phyiscal NIC 2 - switch has

  VMkernel Port 3 - NIC physical 3 - switch B

  VMkernel Port 4 - NIC physical 4 - switch B

  4 port .1Q between switch A and B, allowing all the VLANS to pass through. As said Andre, all cards on the same iSCSI network interface VLAN. I don't see why you would need or want to several VLANS iSCSI.

  Reference Dell EQL:

  Connect 2 network by each switch controller cards, for each controller is multichannel through two switches.

  In this configuration, VMware will see 4 paths to the storage, which is what it should be, if you have 4 NICs per controller. You will also get full in this configuration redundancy, given that each host has 2 paths by switch.

  I am very familiar with EQLs, so if you have any other questions just ask. I'll actually implement a PS4000 this week.

• The profiles breaks iSCSI host configuration

  I determined that host profiles do not support configuring vSS correctly to for iSCSI jumbo frame support.

  How the host profiles work when applied is that they will seduce all of the existing switches and then re - set their place, problem with the way in which it does this is that it supports all the features required. I.e. Jumbo frames.

  I can get my understanding confirmed (host profiles are not fully cooked) and ask the next question.

  Is it possible to tell a host profile to ignore elements like a vSS configuration? My review, it appears that once the host profile was created from a host of sample you can not say NOT to implement parts of it.

  Fix - now host profiles are not fully cooked.

  -Matt

  VCP, VCDX #52, Unix Geek, Nerd of storage

• VMware vsphere essentials more and Dell MD3000i iSCSI - virtual disk not on preferred path

  Hello world

  I am trying to set up our new vmware vsphere essentials plus the facility. We have 2 x Dell R710 servers running vmware esx4 and have a md3000i SAN.

  Each server has a network cable to connect to a network SAN controller.

  vmserver1 a vmnic6 IP 192.168.130.110 the IP controller connection 0 192.168.130.101

  vmserver1 has IP 192.168.130.111 vmnic4 connection to controller 1 IP 192.168.130.102

  vmserver2 a vmnic 6 IP 192.168.131.110 the IP controller connection 0 192.168.131.101

  vmserver2 has IP 192.168.131.111 vmnic4 connection to controller 1 IP 192.168.131.102

  Whenever I start a virtual server it causes the dell md3000i start flashes orange, and management tool says disc not on favorite virtual path.

  After entering the tool configuration and affecting the path preferred, from the commencement to vmware, even with a single connected server it causes the error.

  I tried to configure vmware to use direct fixed and alternate paths.

  I did a quick search on Google and found these sites:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  http://en.community.Dell.com/support-forums/storage/f/1216/t/19269507.aspx

  Strange configuration.

  Looks like you are using some cross cable?

  Each host must have 2 vSwitches, each with a port vmkernel on one of the two iSCSI network.

  Each host must reach all 4 of the MD3000i (test with the vmkping command) interface.

  See also:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  André

• VMs in transition to the new host - host license expiration problem

  I have a fully licensed host ESX 3 (+ VC with license server Foundation) and I'm in the process of setting up 2 x ESX 3.5 and hosts SAN new to replace the one 3.02.

  I have not quite allowed to have all 3 of the hosts running at the same time.

  I was evaluating esx 3.5 on the hosts, but they are now expired and I don't have the chance to test VCB.  (had held by other issues and a holiday in the middle)

  I don't want to redo a straight change in case there are problems with the virtual machines on the new host, so I had to migrate virtual machines one or two at a time. (which is also a pain as the 2 x host ESX 3.5 of assessment will not add to the virtual Center due to licensing)

  Other that reinstall ESX 3.5 to get another 60 days (and having to reconfigure ISCSI etc) is there a better way to do it?

  Reinstall everything 3.5 host for a new evaluation period.

  ---

  VMware vExpert 2009

  http://blog.vadmin.ru

• Work of WMI provider host arrested product problem

  Product
  WMI provider host

  Problem
  Stopped working

  Date
  05/06/2011 08:49

  Status
  Report sent

  Signature of the problem
  Problem event name: InPageError
  Error state code: c0000185
  Type of media loopholes: 00000003
  The system version: 6.0.6002.2.2.0.768.3
  Locale ID: 2057
  Additional information 1: 98bf
  More information 2: ce216bd729d8327bd55aa53db1c6e74b
  Additional information 3: afcd
  Additional information 4: 8ccbc43fbd32957371994687dec426a2

  Additional information about the problem
  Bucket ID: 511421

  Hello

  I suggest you to refer to this link and check if it helps:

  http://support.Microsoft.com/kb/935553

  It will be useful.

• USB - If xHCI USB host controller driver problem

  My new Windows 8 in Sony VAIO found the problem with the USB - IF xHCI USB host controller driver, who couldn't reinstall Windows. What should do? I have not done the recovery discs! Please answer...

  Thank you

  I saw this post today and the information provided helped me to solve this problem.

  Click here

  http://www.eightforums.com/hardware-drivers/17161-Intel-wiusb-driver-not-working-properly.html

  The link essentially says to visit the Intel Web site and use the Intel driver update utility. The utility automatically searches your computer for devices that are eligible for an update. Hope this helps you because it has helped me. Also I have updated my wireless driver while I was using the Intel drivers update utility as a newer driver has recently been made available.

  It worked for me; However, I ended up having to uninstall the old drivers Intel WiDi, then by restarting my computer before the setup.exe file would go and install on my computer (dell inspiron). I created a restore point in case it did not work, but everything seems to work smoothly!

  I must also stress that just remove the driver Intel WiDi also got rid of the yellow exclamation, and unless you plan to try to connect wirelessly to your computer to your TV, I don't think it's something you need. Here is a link that explains what is the driver:

  http://www.Intel.com/content/www/us/en/architecture-and-technology/Intel-wireless-display.html

• Start impulse tool hosted in Tomcat problem

  I have the pulse.war file that is hosted in an instance of Tomcat and I'm doing it to connect to my cluster Gemfire 7 via a Web address as a JMX Manager running. The Locator and my node gemfire one cache server in the cluster also seem to communicate and working properly and I can start the Pulse app but I don't see any stats on my cluster gemfire in the web interface of Pulse. Moreover, in the file journal of catalina.out to the Tomcat server where I am under pressure, I am repeating stack trace as follows:

  INFO: [Pulse] create new Cluster Thread...
  January 29, 2013 17:55:09 com.vmware.gemfire.tools.pulse.internal.data.Cluster updateData
  INFO: Data of the cluster update [pulse] Cluster: idcprdgflocator1:20003
  January 29, 2013 17:55:09 com.vmware.gemfire.tools.pulse.internal.data.Cluster$ isConnected JMXDataUpdater
  INFO: [pulse] connection not found. Get new connection...
  January 29, 2013 17:55:09 com.vmware.gemfire.tools.pulse.internal.data.Cluster$ JMXDataUpdater getJMXConnection
  INFO: [Pulse] use Locator = true
  January 29, 2013 17:55:09 com.vmware.gemfire.tools.pulse.internal.data.Cluster$ JMXDataUpdater getJMXConnection
  INFO: Host Locator [pulse]: idcprdgflocator1 and port: 20003
  January 29, 2013 17:55:09 com.vmware.gemfire.tools.pulse.internal.data.Cluster$ JMXDataUpdater getJMXConnection
  INFO: [Pulse] index found jmx Manager Details: host 10.50.30.199 port 1099
  java.rmi.ConnectException: connection refused to host: 127.0.0.1; nested exception is:
  java.net.ConnectException: connection refused
  at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
  at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
  at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
  at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
  at javax.management.remote.rmi.RMIServerImpl_Stub.newClient (unknown Source)
  at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2329)
  at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:279)
  at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
  to com.vmware.gemfire.tools.pulse.internal.data.Cluster$ JMXDataUpdater.getJMXConnection (Cluster.java:2101)
  to com.vmware.gemfire.tools.pulse.internal.data.Cluster$ JMXDataUpdater.isConnected (Cluster.java:2168)
  to com.vmware.gemfire.tools.pulse.internal.data.Cluster$ JMXDataUpdater.updateData (Cluster.java:2199)
  at com.vmware.gemfire.tools.pulse.internal.data.Cluster.updateData(Cluster.java:1170)
  at com.vmware.gemfire.tools.pulse.internal.data.Cluster.run(Cluster.java:1141)
  Caused by: java.net.ConnectException: connection refused
  at java.net.PlainSocketImpl.socketConnect (Native Method)
  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
  at java.net.Socket.connect(Socket.java:529)
  at java.net.Socket.connect(Socket.java:478)
  at java.net.Socket. < init > (Socket.java:375)
  at java.net.Socket. < init > (Socket.java:189)
  at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
  at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
  at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
  ... 12 more
  java.lang.NullPointerException
  to com.vmware.gemfire.tools.pulse.internal.data.Cluster$ JMXDataUpdater.updateData (Cluster.java:2209)
  at com.vmware.gemfire.tools.pulse.internal.data.Cluster.updateData(Cluster.java:1170)
  at com.vmware.gemfire.tools.pulse.internal.data.Cluster.run(Cluster.java:1141)

  Please let me know if you need more information or log files and I can post it.

  Thank you

  Tom

  Try as I might, I can't reproduce this problem. The important part here is that the gemfire node doesn't seem to know its own host name at startup while make other systems. (seems to have amnesia). It is easy enough reproducing the opposite

  If you want, I would ask you to try more than two things.

  Create an explicit entry in/etc/hosts on the node of gemfire for himself - that is to say:

  127.0.0.1 localhost

  10.50.38.205 ccnscupadsgf01 ccnscupadsgf01.carecorenational.com

  #127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4

  : 1 localhost localhost.localdomain localhost6 localhost6.localdomain6

  At times, GemFire uses JNDI calls to resolve names, so in order to avoid any possible being introduced by Tomcat, strangeness might simply start a server using gfsh:

  gfsh start server - locators = IDCPRDGFLOCATOR1 [20003] - name = locator1

  For both tests, looking for a line, the newspaper, as:

  Concluded that membership in the Group GF70 with ID 10.50.38.205 (7967): 29066

  Except that it must contain the hostname of the server and not the IP address.

  And then

  _MonitoringRegion_10.50.38.205 (7967) region initialization29066

  Should also appear with the host name,

  Thank you for your pateince.

  -Jens