Hi All
I have EQL 6210 , 3 boxex
1. 6210-S
2. 6210-X
3. 6210-E
Multiple volumes are mounted with windows and linux based blade servers.
one specific volume is mounted with linux based physical server and SAP DB is running on it.
I am getting messages in group manager GUI "ISCSI login to target from imitator was closed , ISCSI connection failure , Reset received on the connection: for this SAP DB volume.Snapshot is attached.
Please help to identify and resolve the issue.
Hello.
When I try to replicate volumes, it works fine, except for two volumes. When I click it and "Create replica",
I get the following error: "Operation failed -- some members may be unreachable".
Any ideas what could be causing this? Any information would be greatly appreciated.
Hi All,
I have a PS6110 which had a battery failure on the controller.
I have swapped the controller and all hardware is showing up as OK now.
But the array is still saying critical error.
Status view:
And these are the latest event logs:
Do I have to clear any status?
Everything seems to be working just fine.
Thanks
Hello
We have just discovered that we have very slow performance on our SAN.
This is our environment :
4 - PS6010 and 1 - PS6110 - firmware 6.011
All are full with 15k sas disk and RAID 50, we have 10GB controllers , MTU 9000
We use DELL N4064f switches in stack , with MTU 9000 , flow control, STP disabled as recommended
clients are Dell servers with ixgbe controllers
OS is Debian Jessie ( but tested with redhat 6 )
we use openiscsi :
node.session.timeo.replacement_timeout = 86400
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.noop_out_interval = 0
node.conn[0].timeo.noop_out_timeout = 0
node.session.err_timeo.abort_timeout = 15
node.session.err_timeo.lu_reset_timeout = 30
node.session.err_timeo.tgt_reset_timeout = 30
node.session.initial_login_retry_max = 8
node.session.cmds_max = 1024
node.session.queue_depth = 128
node.session.xmit_thread_priority = -20
node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
node.session.iscsi.FirstBurstLength = 262144
node.session.iscsi.MaxBurstLength = 16776192
node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144
node.conn[0].iscsi.MaxXmitDataSegmentLength = 0
discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
and some tuning in the OS via udev:
ACTION=="add", SUBSYSTEM=="scsi" , RUN+="/bin/sh -c 'echo 60 > /sys$$DEVPATH/timeout'"
SUBSYSTEM=="block", ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/read_ahead_kb}="2048", ATTR{queue/max_sectors_kb}="4096", ATTR{queue/nr_requests}="1024" , ATTR{queue/scheduler}="noop"
if we use IOperf to test the network card between servers all is ok : more than 9GB/s
if we test the read / write speed of the SAN it's very slow compared that we can expect :
root@server1:~# dd if=/dev/sdc of=/dev/null ***=4k count=500000
500000+0 records in
500000+0 records out
2048000000 bytes (2.0 GB) copied, 20.4069 s, 100 MB/s
root@server1:~# dd if=/dev/zero of=/root/testfile ***=4k count=500000 oflag=direct
500000+0 records in
500000+0 records out
2048000000 bytes (2.0 GB) copied, 429.087 s, 4.8 MB/s
root@xen0dmzi10:~# dd if=/dev/zero of=/root/testfile ***=4M count=500 oflag=direct
500+0 records in
500+0 records out
2097152000 bytes (2.1 GB) copied, 29.7126 s, 70.6 MB/s
In SanHQ , network and IO are very low ( 2% for network )
If you have any advise ?
I'm open to any test.
Getting desperate here now.
purchased refurbished ps6510e from third party reseller - have been flatly refused access to dell's site for support based on that.
got it connected to 2 R720 servers via teamed 10gb SFP+ cables through an 8024F switch to SAN with redundant 10gb connections on dual controllers. configured on private network for iscsi traffic only with private addresses for each of the servers, switch, san individual nics and san group ip.
configured corporate / management network for servers / san / switch management with works perfectly.
the 2 servers (2012r2) can communicate between each other via the 20gb links. no communication with san via ping or linking iscsi connectors at all. servers can ping each other and switch, not san. CLI to san - cant ping anything - not even its own individual ip addresses. SAN web interface reports which switch ports (15+16) it is plugged into on the switch so it knows it exists and is connecting to it seemingly happily.
switch configured according to guidelines from dell white papers, jumbo frames, LAG's. I have swapped 10gb connections between servers and san groups, and whichever combination of connections, servers talk, san doesn't.
web interface and SAN HQ all report everything to be hunky dory. only error is about free space as we have provisioned volumes to take up everything.
any bright ideas as to what has gone fundamentally wrong most welcomed.
We have Veeam doing vm backups, which generates volume snapshots on our SAN. The issue is, even though "delete oldest snapshot" is checked on the volume's snapshot policy, and "borrow space as needed" is unchecked, eventually the snapshot space fills up and the volume is taken offline.
Does anyone know a solution to this? I'd think "delete oldest snapshot" would solve this issue, but it doesn't.
Thanks
Hello:
We recently updated our VSM appliance to 4.5.2 and noticed that within vCenter, the EqualLogic storage provider was no longer listed under 'Storage Providers' after the upgrade. Attempts to register vCenter with the VASA provider have all failed. Here is everything we have tried:
- Restart vCSA (Running 5.5.0, build 3721164)
- Unregistered and Re-registered Dell VSM from vCenter
- Tried new VASA credentials than what we would normally use (in case there was some weird caching or confusion with the normal ones)
- Register VASA. Attempted multiple times. Hangs at "Waiting 90 seconds for VMware vCenter to register with the VASA Provider..." We left it for 72 hours at one point with no success.
Took a look at the 'setup.sh-xxxxxxxx.log' files on the appliance. Looks like this (IP's edited):
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/local/asmve/webapps/ROOT.war/WEB-INF/lib/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/local/asmve/webapps/vasa1.war/WEB-INF/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See www.slf4j.org/codes.html for an explanation.
vCenter version: 5.5
VASA URL: https://10.x
Querying providers:
No providers found.
Registering provider: 10.x:8443/.../vasaService
Calling register provider task.....
error
Task failed with error: null
Calling register provider task.....
error
Task failed with error: null
The 'Calling register provider task....' error is repeated over and over, making the log file massive. Ctrl-C must be issued in console to stop the registration attempts.
Any advice on how to make this work?
Thanks.
Hello,
We currently have 1 EQL group which has 1 EQL PS6100XS member. The PS6100XS member currently has 3 datastores. Running ESXi 6.0 u2 and MEM kit 1.3.0.410095 (dell-eql-mem-esx6-1.3.0.410095). The ESXi Host has 4 NICs dedicated to EQL iSCSI. All networking is confirmed to be setup correctly with proper ESXi iSCSI Port Binding.
Prior to installing the Dell MEM kit on the ESXi Host, the active paths to the EQL vSphere datastore shows 4 paths. After installing the Dell MEM kit, it properly sets the pathing to DELL_PSP_ROUTED but reduces the paths to 2 for each datastore:
Note: there isn't a high volume of traffic yet on the datastores since this is a relatively new environment.
Any thoughts as to why there are only 2 active paths showing and not 4?
-Saud
I have an old PS4000 that is no longer under warranty and had a failed drive. I decided to "reset" the PS4000 and remove the bad drive assuming that the array will be created fresh and automatically assign a spare. This has not happened and although the array was created its complaining about the lack of drives or what it expected to have installed. Are the equallogics not capable of running with less than a full population of disks? Is there a way I can assign a hot spare since this did not happen automatically? I left slot 15 unpopulated. Is this the slot that the array would normally use as a hot spare?
Thanks
Troy
Does the VSM and Equallogic management network all have to be on the same subnet? I cannot connect to the equallogic groups with the VSM. Im using this in a DMZ environment, but the management ports on the Equallogic are connected to the internal network. Should I place the management ports on the DMZ network?
Hi all,
I'm looking to see if there are ANY scenarios for seeing the dreaded "unsupported drive" error message other than a drive that doesn't have EQL firmware on it. Initially we accidentally ordered a W347K to replace a failed 600GB disk, which isn't EQL branded, so not surprisingly we saw the unsupported drive message. Then we ordered an EQL branded disk from a third party and installed it. The label looks like a dell/EQL/enterprise storage label with p/n 02R3X, and it spins up and looks like it should work fine, but we get the same unsupported drive error. DOA disk? Firmware mismatch? Anything else it could be? I'm thinking the vendor somehow overwrote the Equallogic firmware, or printed their own label and slapped it on over the top of a generic seagate label. I don't have a way to physically look at the disk myself so I'm probably drawing a couple of unfair conclusions.
Thanks,
Hi, I wanted some advice on changing the ip addresses and subnet.
I have a group with 3 equallogics, currently the group ip and the individual ip addresses are in the same subnet as the main network (though separated on different switches). The management ports are not enabled. (Don't ask, it's just the way it is!!!)
What I want to do is change all the iscsi ports to another subnet, enable the management ports on the original subnet.
How do I best do this without downtime (if possible)?
Should I do the following
1. Change 1 nic on each server to the new subnet
2. Change eth1 on each equallogic to the new subnet
3. Change the Group IP to the new subnet
4. Connect targets in iscsi initiator on the servers to the new IP
5. Change the remainder of the nics on servers and equallogic to new subnet
6. Enable management nics on old subnet
Buongiorno,
mi serve quotazione per n.1 disco sas da 450GB da 10krpm per un EqualLogic PS4000X fuori garanzia
come posso fare?
grazie mille
All of our offices replicate data every night between SANs (Equallogic PS6100). There is one Replica Set that periodically will have a LARGE transfer size that is unexplained...I'm hoping someone has some insight of what could possibly be causing this? An example of what the size is and what the size should be compared to other replica sets....is as follows. The one is question is SAVPROJECTS....
Replica Set Transfer Size
RDUPROJECTS 5.29GB
CHSPROJECTS 39.01GB
ILMPROJECTS 7.01GB
CLTPROJECTS 28.35GB
SAVPROJECTS 167.70GB
We are running SANHQ 3.0.2 on Windows 2008 R2 and planning to upgrade to 3.2.0. Can we perform inplace upgrade. I was reading documentation it says that SANHQ dont support windows 2008 R2 only Windows 2012 R2.
How we can export all data and configuration and restore on current SANHQ and restore on new windows 2012 Server with SANHQ 3.2.0?
Thanks
Hi all,
I have a serious problem with replication between our main and DR sites. Basically all our replications have failed after a restart of our network and storage infrastructure. (I know :( This was not my idea)
The error I get is Status Partner down
If I test the partnership it returns login to partner xx.xxx failed
partner ip address = incorrect ip address
AFAIK non of the partner ips have changed and the account details are correct.
I am fairly new to equallogic support so would greatly value any troubleshooting advice!
Regards!
Just checking to see if I am able to post yet :)
I seem to have lost 3.27TB of space on my SAN and I cannot figure it out.
I'll keep it simple for now:
3TB volume, thin provisioned, 2.34TB in use.
Snapshot space is set to 150%.
3.27TB Snapshot space in use.
Number of snapshots = '0'
My question is - what could be using this space (see screenshot)?
I use VEEAM for backups of the Servers within this volume, but nothing is currently running.
I cannot delete snapshots, as there aren't any - I can create new snapshots fine and delte those, but this chunk of space remains.
I'll try to keep this simple:
I have (amongst others) a 3TB volume on my Dell Equallogic SAN.
It is thin provisioned, with 2.34TB in actual use.
I have it set to keep 1 snapshot but at present, number of snapshots = 0
Despite there being 0 snapshots, the snapshot space is reporting as 3.27TB in use (see attached screenshot)
It is backed up by VEEAM (may or may not be related) but no backups are currently running.
This is a mystery to me.
I'm operating an EQL PS6100 storage array in a disconnected site where items must be (absolutely no exceptions) scrutinized before they are sent out. Diagnostics from the array are encrypted and are not human-readable. I've been able to work with Support without diagnostic logs but am now running into a recurring issue.
I'd like to get these logs to Dell in an effort to identify a root cause. Is there a way to generate unencrypted logs or a certificate of sorts offered by Dell which indicates the data which is found in the logs themselves?
Thanks for any input.