Hello!
I have 3 disk groups on my MSA 2050 and going to remove 1 group. I do it by the way that described in manual and VDRAIN process starts. So, all data from removing disk group not going to be deleted, it's just roaming to other disk group. But I do not need these data ! I want to clear, purge it at all! Is it possible, without deleting all pool? Or may be it is possible to delete disk group without VDRAIN?
Thank You.
Hello,
I have tried RESETUSER and RESTOREDEFAULTS logins with the SN on the controllers but the login does not work. Has anyone been able to sucessfully do this on an MSA1050?
Thanks!
I have this error is one of my P2000 G3 Sans and for the life of me I cant find a resolution. Anyone have any insights.
Hi, I just want to verify that I have upgraded to firmware TS252P001.
It does not say that TLSv1.0 is disabled.
How can I check if the following is disabled in the firmware?
Is there any methods to go around checking?
We have an MSA P2000 G3 iSCSI SAN that I want to move into a different datacenter network.
What is the best, easiest way to go about this??
e.g. the current management network is 172.23.0.xxx and the new datacenter management network is 172.31.0.xxx
I also need to redo the LUNs, it presently has four (4) LUNs and I want to make it have only two (2) LUNs.
Should I just connect a notebook to one of the management network ports and reconfigure it using the wizard??
Thank you, Tom
Hi!
We have a MSA2312i with a RAID 5 (5 disk SAS + 1 SPARE) . These disks were of 300Gb , we have replaced them with new disks 600Gb (1 disk for time) and we want to know if we can expand the volume with the new space..... The expand volume option in web interface is in gray ...... Thanks
good! I have a serious problem with a 1050 msa. I've been with the cabin down all day because of a problem with the disk group created. It appears to me in quarentena after a possible failure with the cache flash. attached logs sent to HPE support:
Line 5068: A1538 2019-09-05 17:46:45 207 INFORMATIONAL A scrub-vdisk job completed. No errors were found. (vdisk: dgA01, SN: 00c0ff3c6b090000910c845b00000000)
Line 5070: A1540 2019-09-06 17:46:50 206 INFORMATIONAL A scrub-vdisk job was started. (vdisk: dgA01, SN: 00c0ff3c6b090000910c845b00000000)
Line 5082: A1552 2019-09-06 20:53:04 485 WARNING A vdisk was quarantined to prevent writing invalid data that may exist on the controller that logged this event. (vdisk: dgA01, SN: 00c0ff3c6b090000910c845b00000000) (signature mismatch reason code: 2)
Line 5533: B314 2019-09-06 21:00:48 173 INFORMATIONAL A vdisk was dequarantined. (vdisk: dgA01, SN: 00c0ff3c6b090000910c845b00000000) (vdisk status: FTOL, mode: AUTO)
Line 5534: B315 2019-09-06 21:00:48 590 ERROR A vdisk has been quarantined because of a flush restore failure (name: dgA01, SN: 00c0ff3c6b090000910c845b00000000)
Line 265603: dgA01 0004 V 00c0ff3c6b090000910c845b00000000 22e571000 0-999
A1660 2019-09-09 11:49:43 509 ERROR The metadata volume for a storage pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (storage pool: A, SN: 00c0ff3c6b090000930c845b01000000)
A1558 2019-09-06 20:53:06 509 ERROR The metadata volume for a storage pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (storage pool: A, SN: 00c0ff3c6b090000930c845b01000000)
A1598 2019-09-06 21:04:36 509 ERROR The metadata volume for a storage pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (storage pool: A, SN: 00c0ff3c6b090000930c845b01000000)
A1624 2019-09-09 11:34:01 509 ERROR The metadata volume for a storage pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (storage pool: A, SN: 00c0ff3c6b090000930c845b01000000)
A1660 2019-09-09 11:49:43 509 ERROR The metadata volume for a storage pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (storage pool: A, SN: 00c0ff3c6b090000930c845b01000000)
B320 2019-09-06 21:00:50 509 ERROR The metadata volume for a storage pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (storage pool: A, SN: 00c0ff3c6b090000930c845b01000000)
Hello,
For a need to fix a vulnerability, I am looking for a command to disable the SSH server from supporting SSH1 clients.
I found on the internet a command "undo ssh server compatible-ssh1x" but it concerns the switchs, is it the same thing for Disk Array "StorageWorks MSA" ?
Thank you in advance,
Hi Experts
I have a HP Gen 9 server ( Live server of the client and not the test system ) .. accidently one of the logical group in that server was setup in RAID 6 and we wanted it to be in RAID 5. Please suggest a way to migrate from RAID 6 to RAID 5 without losing a single data. Server is having P440 Array Controller.
Prompt response will be highly appreciated.
thanks.
Afternoon Folks,
Im looking at two separate MSA 2040 SAS based dual controller systems(12G SAS) (one is in production and the other is decomissioned)
We have seen a controller fail on the production unit and would like to use one of the identical controllers from the decomissioned unit to replace it. Could anyone point me to the procedure for doing this, for example would we need to clear down the controller from the decomissioned unit before inserting it into the production SAN as a replacement.
Realise there is a procedure here for replacement using a new part, but this would be for a controller part that is from another system so just checking the difference.
Any helpful advice is welcome.
Kind Regards
Hello,
Please explain the differences between two identical controllers:
Is it possible to use them in pairs in one chassis?
We tried to install B instead of the failed A (the second A was installed the same chassis), but we did not succeed. Because the controller did not fit into the chassis ...
Maybe we did something wrong, but it seemed that B really was not suitable for this chassis.
Explain, please.
Hello,
For a need to fix a vulnerability, I am looking for a command to disable the SSH server from supporting SSH1 clients.
I found on the internet a command "undo ssh server compatible-ssh1x" but it concerns the switchs, is it the same thing for Disk Array "StorageWorks MSA" ?
Thank you in advance,
We have a P2000 G3 Smart Array controler (A) that errored after a power cut with (Degraded). The Network was dropping in and out.
We could still get in by Controller (B) I restarted/reseated the controler (A) but got the same error so we shut down controller (A) and installed the Replacement Controller ,we'll call this (A2)
After 30 Min the new controler (A2) still showed as Degraded so we decided to put the origional controller (A) back in.
The Firmware started updating (B)! aparently the controller (A2) had a newer firmware. The update finished but now controller (B) show no details in the system overview now!
Controler (A) still degraded but can see the Vdisks still.
Any ideas??? I'm worried a shutdown may make it worse as the VMs are still on and working,
Hi There,
Is anyone else out there using a HPE c7000 and MSA 2040 in a software iSCSI implmentation (I have two HPE 5700 switches providing the storage network). One 10GB connection (with a standby) to the storage using SFP-DAC cables. I'm using VMWARE 6.7. The VMWARE datastore is on SAS 10K disks in a RAID 6 config. The blades are CL460c's Gen9. (Power is set to MAX in the BIOS)
I've built a test VM Windows 2012 server 1 CPU 4GB RAM - One 40GB
I then run this test.
DiskSpd.exe -c15G -d300 -r -w40 -t8 -o32 -b64K -Sh -L c:\temp\testfile.dat
What performance are you getting. I'm not sure what is good for an MSA 2040.
While running the test above I also run performance monitor and specifically look at the counter "Average Disk sec/Transfer" . The average is alway around 0.262 when Microsoft says it should be around 0.005. Thats whats really bugging me.
Appreciate it if you can run the test (as close to the config above would be great)
Hi There
I've been reading the best practice guide for the 2040 and I'm stumped by volume tiering.
The document seems to be suggesting that "busy" data will "AUTOMATICALLY" move to volumes with a higher Tier - which as far as I can see if physically impossible.
quote from the best practive "As data is later accessed by the host application, data will be moved to the most appropriate tier"
Image if there are two volumes - One is "No Affinity" and one is "Performance". These two volumes are presented to a Windows 2016 server and mounted as the D: and E: drives. Imagine that the data on the D: drive started to get very busy - Is the best practice doucment trying to tell me that the data will be moved from the D: drive to the E: drive - that to me seems impossible. Its actually something you'd never want to happen.
ta
Hi,
I present storage from my 2040 to my esxi hosts - they then mount it as a datastore.
I then build VMs on that datastore. The local disks on that datastore are vmdk local storage. (For example the C: is a vmdk)
However, some of my VM's require iSCSI their own storage. (For example the S: drive is an iSCSI drive).
I was thinking of doing the following. Pool A is reserved for VMDK storage (SSD disks)
Pool B is reserved for the NAS (iSCSI) storage for the VM's (SSD disks).
Is that a good way to go about it?
ta.
Hello,
I am a newbie to replication technolgies with HPE MSA 2052s. We are replacing 2 * P2000 arrays in remote geographical locations linked over a WAN connection. I am testing this set up at present with 2 arrays in the same cabinet & same ethernet switch.
The migrating the existing workloads from P2000 is easy enough. Primary site will be running 2 ESXi hosts with HP MSA2052 connected with direct attachment through FC. The VMs on the hosts will be approx 11Tb in size total, genearting approx 10Gb of change daily. We have appox. 21Tb of usable space with 2 * 800Gb SSDs used as performance tier
The intention is to use 2 * iSCSI ports for remote replication between primary & secondary site. Been advised to use virtual replication & do not want to affect the 'on-line day' will utilise scheduled replications 3 times a day.
A number of parameters are confusing me in setting up the replication set.
Do I want to choose Discard or Queue Latest? (Queue latest seems to be the default).
Do I want a Secondary Snapshot history? If so do I need a retention snapshot history of greater than 1? Do I want to keep Primary Snapshot history? & what should be retention priority - I am guessing Never Delete would not be good option if I want to preserve disk space!
Primarily the remote replication will be used for DR site recovery & not recovery of VMs from point in time.
Second last question - I am guessing that the Enable overcommitment of pool setting should be set as ON, other internal snapshots may grow & we run out of space.
Last question - In testing scheduled replication - continually get these errors.
Scheduler: The scheduler was unable to complete the replication. - Command is taking longer to complete than anticipated. (task: du-msa-01, task type: Replicate)
EVENT ID:#A2238
EVENT CODE:362
EVENT SEVERITY:Error
Normally happens 20 secs after replication completed successfully.
Firmware version is VL270R001-01
Many Thanks
Allan Clark
hi guys
i have msa 2050 i connected 2 port to my server as backup and redundant,when i create volume and map it to injector in my windows server i see 2 voulme created.one online and one offline.so where is the problem?
as you see i create 2 voulme one for sql and another for db.but show 4 voulme.
Hi all,
I've got an odd issue on an old P2000 G3 MSA storage system. It has 2 controllers both of which are working fine and a number of expansion units (again all working as expected). I noted that it was reporting that controller B's network management port was 'degraded' . Sure enough 'show system' is reporting the system as degraded and I can see a red X against the controller B manangement port. Show FRUS however says alll subcompoents are in OK state, show controllers again is fine, show cache-parameters is OK,... I can also connect to the system over ssh on both controllers. What I can't seem to do is connect to the WEBUI on controller B. I've tried restart MC to see if that helps. No. I've also run ping tests from both controllers.
Controller A can ping its gateway with no issues. It can also ping controller B. Controller B however is reporting it cannot or can only intermittently ping the default gateway and it's partner controller A.
So all a bit odd really. If it was failed I'd expect no access at all, yet I can ssh onto it.
Both controller are running TS230P006 which I am guessing is pretty old however we had not seen any issues until recently.
My next plan is probably to fail everything onto controller A and then re-seat controller B to see if the issue clears. If not I guess the next step is a new controller but given the issues I've had in the past being sent controllers with way newer firmware and then having the controllers refuse to talk to each other that will be a last resort.
If anyone has seen this type of issue before or has any suggestions it would be most welcome.
thanks
Ad.
