Thank's Shawn,
Quick and clear answer top !
Just one more question :
would it be better to declare the 12Tb SAS drive as a global spare or let it just availaible ?
thank's
↧
Re: MSA2050 sparing question
↧
Re: MSA2050 sparing question
Hello
There two ways to configure spare. One is Global spare and other option is Dynamic spare.
• Global spare. Reserved for use by any fault-tolerant disk group to replace a failed disk.
• Dynamic spare. Available compatible disk that is automatically assigned to replace a failed disk in a fault-tolerant disk group. This option is enabled by default.
When a disk fails, the system looks for a global spare. If it does not find a compatible global spare and the dynamic spares option is enabled, it takes any available compatible disk. If no compatible disk is available, reconstruction cannot start.
So in your case either you configure your 12TB SAS drive as Global spare or let it be as Available but in that case you need to verify if Dynamic spare option enabled or disabled.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
↧
Re: MSA2040 - Expanded size by 2 TB but Allocated size stays still.
I am not sure about the entire setup or configuration of this MSA. However, let me try to help you with the following information.
If you have only one Pool present in the system and you want to add 5 new 1.2TB SAS drives to the existing pool then it's not recommended with current number of drives. The recommended method to increase the volume size is to add a new Virtual Disk Group with the same amount of drives and RAID type as the existing Virtual Disk Group has. MSA uses wide striping which means data will be span accross all VDG in that Pool. I hope you remember that we can't expand existing VDG so we have to create new VDG with new drives and add them into Pool. Now due to mismatch of number of drives in particular VDG you will face performance issue as well as one VDG may run out of space than other VDG which is never recommended.
So solution would be either you buy another 8 new 1.2TB SAS drives and create new VDG with 13 drives with RAID6 like your existing VDG and add it to the same Pool where your existing VDG part of it.
Otherwise create a new VDG with these 5 new 1.2TB SAS drives and add it to other Pool from which new volumes can be created or if any existing volume already here then they can use this expanded space of the Pool as well but keep that in mind existing volumes created from 1st Pool existing VDG space can't use this space. In Virtual storage a Volume is tied to a Pool. This means that a Volume cannot span accross Pools.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
Re: MSA2050 sparing question
Clear for me thank's Subhajit !
Gérard
↧
Re: MSA2050 disable automatic tiering
Hello,
It looks like there is no trial ADS license for MSA, we bought a license ( 2800€ gloup !)
So know we have :
1 pool /diskgroup/volume A with 9 SSDs 800Gb. The volume is flagged as "performance"
1 pool/diksgroup/volume B with 11 SAS 12TB drives and a spare
and we have a performance licence ( gloup ! again )
My understand is that tiering cannot be done as my diskgroup are on different pools.
So what will happen if i create another SAS diskgroup in pool A:
will tiering automaticly start for my existing volume ?
how can tiering been disabled ?
Thank's for all your clear and quick answers.
Gérard
↧
↧
Re: MSA2050 disable automatic tiering
I will try to answer as below,
Q> So what will happen if i create another SAS diskgroup in pool A:
Ans: Tiering will work the moment you add another SAS VDG in Pool A as already SSD VDG exists
Q> will tiering automaticly start for my existing volume ?
Ans: Yes Tiering will start automatically if you add new SAS VDG to the Pool where you have SSD VDG exists
Q> how can tiering been disabled ?
Ans: There is no way to disable Tiering until you un-install the license as this is Automatic feature the moment you install ADS license and it detects different type drive VDG present in the system. Another Option is to configure SSD cache.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
Re: MSA2050 disable automatic tiering
Perfectly clear !
Thank's again Subhajit !
↧
Re: MSA2040 - Expanded size by 2 TB but Allocated size stays still.
Yet another great explanation, thank you!
I will purchase 7 more disks since I can install only 11 more disks (13 installed). My configuration is like;
I have 1 pool that has 1 volume and 1 disk group. And the disk group I have is RAID6, Virtual and has 13 disks installed. So as far as I understand it is not possible to add new disks to my existing disk group instead create a new one. So to equalize the number of disks, am I allowed to reduce the number of existing VDG by 1 to make them 12-12? Also to make sure; I'll be able to use all these space for 1 volume without losing any data right? :)
I am sorry I am software expert and I 'must' deal with storage configuration too, so I don't have much knowledge about robust configuration :)
I am also attaching the whole setup I have under attachments.
Thanks again for enlightening me!
↧
Re: MSA2040 - Expanded size by 2 TB but Allocated size stays still.
There is no option to increase or reduce drives from existing VDG. It's better to take data backup and then delete the existing VDG. Then buy 11 drives and create new VDGs as per your requirement.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
↧
Re: P2000 G3 SAS ERROR ": The firmware version is not compatible, HP SPS-CHASSIS 2028"
Did you tried to reboot both management controller at the same time? YES
if same issue persists then take downtime and reboot storage controllers at the same time YES
If still same issue persists then try to reflash the firmware where Expander module firmware shown as unknown NOT FLASHED, say error
if i flash HPE P2000 G3 MSA Array Systems Controller Firmware TS252P005 or TS252P001 then nothing change exclude version
If still issue persists then we have to replace the hardware
but if i sotdown one of the SC, then other work fine
i think the problem with defferent firmware versions in "Expander controller code versions"
because if i start first SC module B then SC A i see old fw version on screenshot
or bad version in Expansion Modules (EMPs). but it not flash with CAMSPR0146_6G_app_4MB_ai.pmc =) say error
i tied power off MSA and reconnect controllers and flash cards and cables
nothing help =)
↧
Re: P2000 G3 SAS ERROR ": The firmware version is not compatible, HP SPS-CHASSIS 2028"
I have seen the screenshot and it looks to me Controller B internal Expander Controller Code gone back to very old version 1052. It could be issue with Controller B
Please note that Controller internal EXpander Controller is not Enclosure 2 IO modules. They are different. Controller internal EXpander Controller responsible for SAS Out put port or Egress port which we use to connect External Drive enclosures IO modules.
Next suggestion would be,
>> Plan for downtime and Stop Host IO or disconnect Host from MSA
>> Shutdown Controller B
>> Upgrade Controller A to latest firmware TS252P005
>> Disable PFU or Partner Firmware Upgrade on Controller A
>> Power up Controller B and upgrade to TS252P005
>> If still same issue persists then replace Controller B
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
Re: Not access to the management console
Hello,
I bought a mini USB cable and connected to the storage and server with Windows 2008 R2 x64.
I downloaded the driver (cp020153.exe), I installed it but it looks like it is appearing as unknown in the USB device manager.
https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_f7441b0018c143ac88d83572e8
I noticed that in COM Port in the Device Manager, a COM5 (USB-SERIAL) appears.
I tried to use Hyperterminal in Windows XP, it opens but nothing appears after pressing Enter.
I think the connection is not working properly from the mini USB.
NOTE: I have not yet restarted the server where I connected the cable and installed the driver.
Thank you.
↧
Re: Not access to the management console
Try downloading one small software called putty.exe
Then connect the Serial cable to one MSA controller CLI port as shown in the picture of the below document and other side in the Laptop or desktop or the Server.
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03820027
Place the putty.exe file in that Laptop or desktop or server
Check from device manager if you are able to see the COM port. If it's COM5 then open putty file and select option Serial. Then give COM5 under Serial line and Speed as 115200. Then click on open and then press enter. It should ask for MSA userID/Password. Attached is the screenshot of the putty software how it looks like.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
↧
Re: P2000 G3 SAS ERROR ": The firmware version is not compatible, HP SPS-CHASSIS 2028"
thanks, i try upgrade witout PFU
personal A and B
and have the same issue
B internal Expander Controller Code not upgraded
we plan replace Controller B (
if we come up with something i write result here :)
↧
Re: P2000 G3 SAS ERROR ": The firmware version is not compatible, HP SPS-CHASSIS 2028"
Yes kindly update with the solution so that whoever following this forum can get the answer. Also mark the forum as resolved once the issue get fixed as well.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************
↧
Re: Not access to the management console
Hello,
I did a test, but it does not seem to work either.
Can I try with a notebook with Windows 10 Enterprise?
Thank you.
↧
Re: Not access to the management console
Next option to try only hard reboot of Storage controllers
Stop Host IO and disconnect Host from MSA if in production. Then go for hard reboot of Storage Controllers. Remove power. Wait for 5 to 10 minutes so that all drives will spun down. Then reconnect power and then check if you can access Controllers or not.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
↧
MSA 2050 SAN - Basic preperation
Hi Community,
I'm about to prepare 10x MSA 2050 Storage Array and 10x MSA 2050 Storage Enclosures for a customer.
The goal is :
- equip every Array and Enclosure with 24 hard drives
- equip both controllers of every Array with 2 SFP modules
- set the management IPs for both controllers on every Array
Questions:
1. I equip an Enclosure with the HDDs and only connect power to check if every component (PSU, FAN, HDDs) is working. Can I switch off the power just like that and the system is still in basic (almost) manufacturing state?
2. Same question for the Array. Equipping with HDDs and SFP modules. Powering on to check components are working. Do I have to be aware of anything before powering down?
3. I would set IPs with the CLI (described in MSA 2050 User Guide chapter 5). Is this the simplest way? If I set the IPs with " set network-parameters" is it already persistent and can I power down the systems savely by flicking the power switch?
The systems should not be connected to anything else than power the whole time.
Nothing else than IP settings should be set so the customer would have almost default factory configuration.
Thanks for input.
↧
Re: MSA 2050 SAN - Basic preperation
I would suggest you to go through below links to get some important documents links to know more about MSA2050.
If you follow Quick start guide that will help you to know how to start MSA2050 and how to connect MSA2050 expansion disk enclosure. You can't check Expansion disk enclosure without connecting them with Controller Enclosure as Expansion enclosure IO modules not having any seperate SMU access.
It's never recommended to do hard shutdown of Controllers like removing Power cables without shutdown Controllers from CLI or SMU.
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00022365en_us
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-a00017812en_us
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00017714en_us
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00017716en_us&docLocale=en_US
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
↧
Re: MSA 2050 SAN - Basic preperation
Hi,
thanks for the answer.
So basically you would suggest the following order:
- equip Array and Enclosure with HDDs
- connect Enclosure to Array
- Power on Enclosure (wait for LEDs to stop blinking and check for error LEDs)
- Power on Array (wait till ready)
- connect to CLI and perform IP configuration
- shutdown both controllers with cli
-remove power from Enclosure
-remove power from Array
This way they will receive the basic configuration and should be in a healthy state after powering down?
↧