EqualLogic PS6000s in a group hybrid

Similar Questions

• VMWare using only 1 IP of EqualLogic PS6000

  I have a new configuration of vSphere with 2 hosts ESXi (Dell R610s) and all my a new EqualLogic PS6000 storage. I use the Broadcom NIC for iSCSI (all other traffic exceeds a secondary NIC 4port). Right now I use 2 ethernet ports on the R610s and PS6000 for iSCSI. I followed the instructions in the document "setting up VMWare vSphere software iSCSI...". "Dell for 2 different iSCSI VMKernel interfaces configuration. The PS6000 uses an IP address of the 10.30.1.1 group and the 2 network cards are 10.30.100.1 and 10.30.100.2 (all with a 255.255.0.0 netmask). The problem I have is when I connect the R610s to the PS6000 via the IP 10.30.1.1, the PS6000 only redirects them to 10.30.100.1, forcing all traffic from these two hosts in the same VM. I tried connecting a computer non - ESX (my Mac desktop computer), and it sends me to 10.30.100.2, so this interface works without a doubt. What I'm trying to understand now, that is exactly how I have VMWare to connect two IPS to distribute the load between the two interfaces on the PS6000. The PS6000 reports 2 connections by volume of each ESX host.

  Does anyone have an idea what I should look next?

  Thank you.

  I opened several requests for EQL support about something similar to this.  In many cases when I migrated a table in an existing pool, or when I activated interfaces more I don't see connections spread.  I saw the following:

  -Select Eth1 and Eth2, wait a few hours, run IOMeter tests, all connections are always on Eth0

  -Restart the controller, now all connections are on Eth1 and Eth2 with none on Eth0

  -Wait as the rest of the weekend and check Monday, iscsi connections are balanced.

  The above situations have happened to me a few times and I have been informed that the balancer connection will be finally doing things.  I think something has changed with this code over time, it was that the balancer spreads connections very quickly.

  Ben

• EqualLogic PS6000 Serires IP address changing

  Hello

  My logic equal group IP is 192.168.0.1 and my two other members of storage are 192.168.0.2 and 192.168.0.3 no port management "management of ports are not configured and is unable to be present due to the direction and iscsi are on the same subnet.

  I would like to change the IP address of the 172.16.10.2 group and my two 172.16.10.3 storage 172.16.10.4 "I want to get rid of the subnet 192.x in preparations of iscsi with the exception of the management ports."

  If I change the ip group at 172.16.10.2 and activate 1 Ethernet ports on the two members with IP 172.16.10.3 172.16.10.4, this group will still be intact and members can see each other in the group without problem?  or what I need to reset the devices of storage and everything again?

  * This is not a production system and contains no data on this subject yet.*

  Thank you

  Hello

  You don't have to reset the berries to change IP addresses.  Just do it slowly, I prefer the serial port as it will always be available when you change IPS.  At some point, you have a PC that has access to both networks.

  PS6000, alias Type 7 controller does not have a dedicated port of Mgmt.  If you want to use out-of-band management, you will lose the last GbE port for this feature.

  So assuming that you do not want to lose a GbE port, you must change a port on each Member new subnet...  This updates the internal members IP addresses table so that they will always stay in contact with each other.  When you get down to the last port, change the IP address of the Group on the new subnet.  Then change the default gateway for the new subnet on all members.  Then finally replace the last network ports on all members of the new subnet.

  I suggest you then restart the two members, a moment.

  If you have a contract of support in place, Dell support can help you in this process.

  Kind regards

• EqualLogic PS6000 member space free vs free space pool

  Hello

  I have a single group, member disk usage details are capacity total members 12.22 TB, used by volumes 8.17 TB snaps and Replica 90meg and free member space 4.04 TB. This varies widely details then realized to the pool area, capacity becomes 12.22 TB (it's a replication target so delegate area's TB 11.55) reserved for snapshots is 2.5 G reserved volumes 109.8 G is reserved for the replication of 50 G, free space 518.94 G.

  The two figures in the clear mind 4.04 CT for the verses 518 G for the pool member. The free members area includes all free space currently used by the reserve of replica for each volume may be replicated?

  Hi Mark,

  The difference is pool view shows how much has been allocated, Member discovers how much actually was written out of this allowance.

  Kind regards

• 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.

• Equallogic PS6000 + ESX iSCSI storage redundancy: LUN disappears when 1 switch off!

  Hello everyone, this is my first post here

  OK, so as the title says, I'm working on the redundancy under ESX. Because network configurations can be quite confusing I just did a quick draft of our infrastructure with one of my 3 ESX host and will try to explain as clearly as possible, the configuration details.

  In my ESX host, I configured a new vswitch with the vmkernel and vmnetwork joined 4 (NIC 2,3,4 and 5) my card NETWORK is configured as active in the collection of NETWORK adapters (also tried to put 2 according to availability) method of failover is Beacon probe (also tried with the status of link)

  On another VSwitch I have the console service with the NIC (NIC 1 and 6) 2 of the joint.

  My 2 switches are connected by a SHIFT of 4 links and the RSTP Protocol is active and works (although I have a lot of broadcasting activities, as soon as I connect my LAN switch to the SAN switches, but that's another story)

  My SAN is connected with 2 links on A button and switch B 2 for each controller. I created 3 volumes on the SAN that is each configured in my host ESX 3. So far, everything is great.

  Now, I pull the power plug from the switch a. switch B takes the lead and I can still ping SAN network lan switch, I can ping my small guest VM but the virtual machine itself quickly dies. I can't even it reboot or I get an error message indicating that the file is not found. So I go to my store of data, and it is when I see that it's empty! I need to open any new analysis of the LUN to again access to the data store and start my VM.

  From my point of view, although ESX detects that some links are down when I pull the cord, the iSCSI session just dies on me and will not "restart". I read stuff on multiple paths, but the "manage paths" button is grayed out, I'm not even sure that's what I need.

  So basically, as you can see I am quite new to all this and completely lost when it comes to things of redundancy, hell, I didn't even know on the tree covering weight before yesterday! So, if any of you guys can give me some advice on the realization of redundancy I look forward ^^

  Thank you very much!

  I wouldn't put my vmnetwork and my storage on the same vSwitch network.  I separate them into their own vSwitch and use two natachasery for each vSwitch.

  Once you have the traffic separated out, I'll make sure a vmkping, and not a ping to the storage target runs through each physical NIC.  Remove all cables and one at a time to create works of course routing their connection.

  -KjB

  VMware vExpert

  -KjB

  VMware vExpert

• Can PS5000 and PS6210 - be in the same group?

  Hi all

  I have 2 PS6210 Equallogic units in a group, it is possible to add one of my old PS5000 devices to the group or do I need to keep them in separate groups?

  Thank you very much

  Eric

  Yes, you can... but:

  -The FW 7.x is the last for PS5000 and all members of a group must run the same version. So if you already upgraded your 6210 to 8.x you cannot add the PS5000

  -There is a guide of best practices on mix 1 and 10 GbE

  -As long as your PS5000 have a valid support contract youre allowed to download and deploy the latest FW version... think.  Members with and without the support of the same group is not allowed and will be trouble.

  I suggest to run the PS5000 on his own band.

  Kind regards

  Joerg

• Aggregation of links for Equallogic

  A few questions on the Equallogic aggregation and link:

  The physical cable how can I use to set my Berry of EQuallogic iSCSI on my physical switch Cisco 7 K? 2 or 4?

  How aggregation of links can I use: LACP?

  Thank you!

  Hello

  EqualLogic doesn't support grouping/collage/LACP, etc...   You must configure MPIO on the guests instead.

  Kind regards

• EqualLogic SAN and Jumbo frames

  I can't get the jumbo frames to work on our Equallogic PS6000.  We have the following configuration PS6000-> Dell PowerConnect 6248 (bunk)-> Windows 2008 Server.

  The network cards on the SAN has been set at 9000 MTU, ports on switches are set to MTU 9216 and the NIC on Server 2008 is fixed to 9014 with active RX & Tx flow control.

  When the server connects to the SAN, newspapers account connection iSCSI target to the initiator "172.21.X.X:3260, iqn.2001-05.com.equallogic:0-8a0906-xxxxxxxxxxx-23a001a955452af6-server1" ' 172.21.X.X:49156, iqn.1991 - 05.com.microsoft:server1' managed, using the length of the standard framework.

  When I ping the SAN of Server 2008 with a shitload of 8972 bytes, it works very well.

  C:\Users\system>ping 172.21.x.x f-l 8972
  Ping 172.21.x.x with 8972 bytes of data: reply from 172.21.x.x: bytes = 8972 times<1ms ttl="255" reply="" from="" 172.21.x.x:="" bytes="8972"><1ms ttl="255" reply="" from="" 172.21.x.x:="" bytes="8972"><1ms ttl="255" reply="" from="" 172.21.x.x:="" bytes="8972"><1ms ttl="">

  Why 8972?  Told that some genius on the internet.  Any help would be greatly appreciated.

  Well we got it to work.  On Server 2008, we have Broadcom and Intel network adapters.  For our tests, we were just using the Broadcom NIC.  Properties Advanced NETWORK adapter, we initially have the value package Jumbo 9014 and it did not work.  So, we opened the Broadcom Advanced Control Suite that came with the NIC and searched and found that there are two parameters that need to be addressed.  There is a jumbo packet definition which has been set at 9014, which is what we wanted it in the advanced NIC Properties.  There is another parameter, MTU, which can be seen on the advanced NIC Properties.  It has been set at 1500.  Once we define to 9000, frames jumbo started working.  We then uncabled Broadcom NIC and wired the card NETWORK Intel and the value of frames 9014 on advanced network adapter properties.  Once we have that frame has worked on this NETWORK adapter, no other measures were needed.  If it's working now.  Thanks to everyone for their help.

• PS6000 convert RAID5 in RAID10

  I have a PS6000 in a group of 3 members (in its own pool of storage) I want to convert RAID5 in RAID10. All LUNS have been removed, but the option to change from RAID5 to anything else is grayed out.

  How can I update?

  You cannot move from a larger capacity RAID 5 at a smaller level as R10.  Which is never been supported.  The only way is to reset it and recreate.  You can save the configuration and restore it.  That would save some time you recreate the configuration.  If it is a member of an existing group, then remove the group, who must be able to deliver.

  Kind regards

• Set up new network iSCSI for VCenter

  Originally when we configure our environment VSphere, that we could not have our network engineers set up a separate subnet for iSCSI traffic.  Now, I have this ability and plan configuration.  I will be using our maintenance window to make this change instead of driving through the sectoral approach.

  My questions are about what communication is necessary between the two subnets, if necessary.  I will bind to the vmk ESXi iSCSI on the new subnet and they are the separate vSwitches but I'm not clear if the two networks require that any communication on the VCenter server.  The management network and LAN traffic will remain where it is in my plan will and so one of the network adapters on each host ESXi. Our network engineers want the two subnets to be completely separated, because this new iSCSI subnet will speak also to our recovery for SAN replication site, which brings me to another question. in order to use the software EqualLogic Auto - SnapShot Manager\VMWare Edition, she wants to be able to talk to the iSCSI network and the VCenter.  Anyone here used this feature without SRM?  I'm not planning to allow the SRM software currently in production, only half of my servers are VMs where all are as in DR and slightly different configs, so until I can duplicate both slots and fully use SRM I'll wait.

  I am also having a different subnet created only for devices management and applications such as updates of HQ of EqualLogic SAN, head of group and the servers, devices, etc.  It would be a more ideal situation to move the VCenter for?

  FYI, VSphere 4.1, ESXi 4.1, EquaLogic PS6000

  Also, I use FT and VMotion on different VLAN internal to the production of LAN and those will not change.

  Any idea or clarification is appreciated, I would like some feedback before .

  Welcome to the community - there is no need for vCenter communicate to your iSCSI subnet - all communication is handled by the ESX/ESXi hosts if ther EqualLogic can't answer to and his need to connect to vCenter.

• 4.3.6 7.0.1 downgrade firmware for a PS6010

  So I know this is probably VERY discouraged, but we try to consolidate this PS6010 with some older units as a PS4000, that all run along happily in 4.3.6.  I feel that you cannot add an Equallogic to an existing group, unless it corresponds to the revision of the firmware from the rest of the members of the group.

  Is this possible via any means? (I already know that it is not possible through the user interface)  I am sure my brick system if I try to force-load for example images on microSD cards?  OK, I already tried this but received a message like "The NVSRAM present in the system is newer than the version found on the controller" Version 16 was on the system (somewhere) and version 11 on the controller that I provided an image.  My next thought was to clear the room and the NVSRAM batteries in hopes of controllers that they will forget that they already had a newer version, but it seems not the best idea.

  Someone at - it experience with this sort of thing?  It is obviously not something that will be most of the people tried, but well, there are a lot of smart people on this forum.

  Thank you!

  Hello

  Downgrade, do not correct an option.  There is also concern with FW level according to the hard drives in the 6010.  Some readers require the latest firmware on the table.

  Don

• Possibility to change the speed of ethernet interface

  Hello

  I have two groups of a PS5000 and a single PS6000 on each group.

  1. on the active controller of the PS5000 on both groups, only eth0 and eth1 shows the speed of 1 Gbps. eth2 watch 10 Mbps. are not all ports of 1 Gbps of three ports?

  2. on the active controller of ONE of the PS6000 eth3 shows 10 Mbps, while on the active of the other PS6000 controller all four ports are 1 Gbps. Why?

  I'm running V5.2.2 on all members

  It would be possible that this feature to specify the last port of an EQL as a dedecited mgmt port comes with a later version of the firmware. Your 5.2.2 is not up-to-date.

  OK, if you check the IP addresses of all the ports and they are all located in the same subnet you have not dedeciated mgmt in use. If all ports must show 1 Gbit/s if they are active. If you take a look at the switch port velocity it will show?

  Kind regards

  Joerg

• Connection to multiple iSCSI SAN ESXi

  I have a pretty small configuration that consists of 2 Dell R710s and an EqualLogic PS6000s. Our iSCSI Setup has been configured as indicated by this resource with the support of Pro from Dell.

  My question is, if I have a vSwitch with 4 ports related to my EqualLogic VMkernel can I also use this vSwitch and VMkernels to connect to a network SAN OpenFiler?

  Yes, you can.

  Diego

• comments or mounted VMFS iSCSI?

  I'm stuck. I'm about to do some conversions from P - to-V, but before I do I want to make sure I have properly configure my storage. Any help would be GREATLY appreciated.

  Setup

  Reference Dell R710 running ESXi 4

  Dell EqualLogic PS6000 iSCSI SAN

  Currently, I have a few very large volumes on the SAN (2.0 1.5 TB) to be my warehouses up to some comments from Suse Linux ES. I have volumes/data warehouses for the operating system itself that I ride the big volumes/data warehouses in the sharing of files/Home areas, etc.. Although the 2.0 TB 1.5 we should last awhile, I fear I might have to increase the storage space in the next 2 years. What I read, I can not simply to increase the size of the volume on the SAN and then increase the VMFS datastore. If this is true, who can put me in a difficult position later.

  So my question is - I'd be better off using an initiator iSCSI in the prompt to mount these volumes directly from the SAN? I would gain the ability to resize these volumes in the future?

  I'm losing sleep over this...

  Thank you

  Jason

  I think that the answer will almost always come down 'it depends' rather than a "this is how you should do it."  You will need to run instant EqualLogic or replication on this large LUN?  If so, it might make more sense to have it as an iSCSI attached inside the guest volume and not a VMDK file on a VMFS storage.  You will always be able to expand the LUNS on the fly if you need to.  That way the snapshot might be conscious application, but I don't know if the EqualLogic Host Integration Toolkit supports Linux (maybe, not sure).

  If you attach it inside the comments rather than VMFS volumes then you will need to do multiple paths inside the host, rather than the ESX level.  Not better/worse, just different.

  Make sure you understand all your needs before making any design decisions that will be difficult to change in the future.