Check out part #2 of the MSA Best Practice video series. Part #2 focuses on updating Expansion Module Firmware.
https://www.youtube.com/watch?v=_a-FaQcWhBc&feature=youtu.be
Remeber to maximize your MSA availability, it is important to keep the firmware current. Make sure to visit https://www.hpe.com/storage/MSAFirmware
Stay tuned for Part #3 which will cover updating MSA drive firmware.
Cheers!
/Kipp
Hi everyone!!
I'm Yujiro Toda which is taking charge of configuration support of the storage products from Japan. As a result I have checked various documnets into the HPE web site included Japan and US site, though I could not find them, so we have a few questions about MSA 1050 and MSA2052 products as followings:
Q1 . What's the CPU type name on MSA 1050/2052 ?
Q2. How many the number of CPU core on the a controller?
Q3. Could the MSA 1050 and MSA 2052 run NAS and SAN into the same contoroller in the same time?
Please let me know if you know these correct answer above questions.
Best Regards,
Yujiro Toda
Hello,
I have an MSA 2040 that I can not access to the management console.
Does it just reboot the storage to return with access?
Is there any option without the need to restart storage?
As I can not restart using the management, to reboot I have to take out the power cables, right?
Thank you.
Try to access controllers directly connecting them through Serial cable (Part number:592266-001)
Please find the guide to connect to Controller CLI port,
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03820027
Then restart both management controller,
# restart mc both
This will not restart or reboot storage controllers so no impact in production
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************
Hello,
I can ping the management IP.
I read that I can try restarting using (telnet). Is this work?
restart mc a and restart mc b
Thank you.
if you are able to ping management IPs then issue could be something else but common to both controllers.
You can try clear temp files of the management system as well as browser.
You can try different browser
You can try accessing SMU from different system
You can disconnect LAN cable of one of the controller management port and take one seperate LAN cable and connect to your Laptop or desktop directly.......then configure your Laptop IP in Controller IP range......then try to access SMU
If issue only with SMU access but you are able to access CLI with management IP then you can try restarting of management controllers as well
# restart mc a
# restart mc b
or
# restart mc both
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Q1:
MSA has no "Classic CPU" (Intel/AMD), it has a special ASIC (like a Raid Kontroller).
https://en.wikipedia.org/wiki/Application-specific_integrated_circuit
Q2:
As using a ASIC it have no Cores.
Q3:
It is a Block Storage only, it has no Operating System and no NAS or File Services.
What are the size reocmmendations for volumes in a hyper-v environment. Should we create one large volume and present to the hyper-v hosts then format smaller disks on the host, maybe have a volume on the MSA for vhd/x's? Or multiple smaller volumes around system needs? IE larger volume for file servers smaller for a dns server with no storage requirements?
We have an MSA 2052 with 2 x SSDs and 6 HDD with FC connection into 2 x D360.
Thanks in advance
I would suggest you to go through the below White paper and HPE MSA 2050/2052 storage and Microsoft Windows Server 2016 Implementation Guide,
http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-a00038738en_us-1.pdf
https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00015961enw
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hi,
When asking this type of question take into consideration what hardware you currently have now and what your future growth might be. With your current amount of drives, 2 SSDs and 6 HDDs, you are going to be limited with the size of the volumes you can present to your hosts. Making two Pools will further reduce your volume size which might not fit your current needs.
However, your future growth might be better suited to two pools which would load balance the host IO across both controllers. You may want to consider creating one pool now and in the future purchasing additional SSDs and HDDs to create another pool on the B controller. At that time you could also get a performance license to utilitze the SSDs in both pools.
Good luck!
Shawn
Thank you Subhajit our problem, we have looked and looked but there doesn't seem to be a recommendation that says, use one large volume for data because, or one small volume for vhd/x/s to protect against data growth using up space for server OS. My thoughts were to have one volume for the vhdx/s and one for the main file server and another for any data on other servers, mostly there would be nil as they are providing services not file serving. I could then expand volumes if I need with the remainder. However my work mate suggested one large volume is easier to manage then slice it up at the OS level.
Robert
I would recommend to go with single Pool and single large Volume as your setup not so big. This will help you to get the Automatic tier feature which in turn will help to improve performance as well.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hi all：
If I want to add a single disk to a disk group in a pool to expand the disk group,
How to do can fulfil this ask?
Hi
Now I have expanded the available disk space to a particular vdisk as in the picture(san.jpg) where it was intially 2 TB and after expanding its 3.1 TB which is mapped to a server but the server says its still 2 TB(as in server.jpg) and I am not able to see the expanded volume.
Do I have to do any additional configuration in order to replicate in the server?
Try to stop production or application running on this MSA volume. Unpresent/unmap the volume from MSA and represent/remap the same
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hi all,
We have two MSA 2040 SAN with the information mentioned below:
Vendor : HP MSA 2040 SAN
Mode : SPS-CHASSIS
Number of Disks : 6 (4 disks in RAID 10 and 2 disks are spared)
Midplane Serial Number :
Part Number : 639410-001
MIdplane Type : 2U24-6Gv2
Enclosure Power : 125.28
This dual controller SAN is connected to 2 Oracle DBs server via FC ports to controller A and B which are in Active-Active ULP Mode for each server. We are supposed to load up second SAN which is entirely same as the first one to implement SAN redundancy.
Based on our investigation the best design is using two SAN switches to connect two ports from each controller module to the first switch to facilitate I/O traffic, and connect two ports from each controller module to the second switch to facilitate replication to get full redundancy and avoid the potential single point of failure inherent to using a single switch. But I want to know what if we eliminate the switch and just connect two SANs together? Please consider that our second SAN storage does not have any configuration, we want to make sure adding it to cluster will not affect our production environment.
If you want to eliminate SAN Switch and implement replication then this is not supported as per HPE official document. Please refer the below document (page no 13),
https://h20195.www2.hpe.com/v2/getpdf.aspx/4aa1-0977enw.pdf
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
It's not possible to include drives in existing Virtual Disk Groups. This is as per design limitation in MSA2050 or MSA Virtual Array technology.
If you have requirement to increase Pool space then you have to create new Virtual Disk Group with new drives and add the VDG to the pool.
MSA2050 is Virtual Array and this is not like legacy MSA arrays like P2000 where you can add drives to existing Vdisk to increase Vdisk space.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Thanks for your reply,
Do you know what happend if direct connection is used between two systems?
Regards,
I am not sure........we follow what is officially supported because if we implement something which is not supported by HPE then any further issue arise or any furture issue we will not get support from HPE.
I would request you to mark my previous reply as solution so that whoever following this forum will get proper answer
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************