covert parcel
Hi all!
We are excited to deploy new ASA AFF A250, AFF C250 and FAS2820 to replace our AFF200, FAS2650. Old stuff is at 9.10.1P7.
A250 will be for production databases via FC, C250 for snapmirror destination of A250 data and FAS2820 for CIFS/NFS. FC SAN swithches will be brocade G720, old are Brocade 6510. Anything particular that we should be careful of? Except disabling default QoS on volumes and luns when created from GUI? I've heard that some storage underperformed because of them! Yikes! Thinks that we are thinking about:
- AFAIK they will be 9.13.1 out of the box. Go to 9.14.1 P-latest or sit on 9.13.1 P-latest? 9.14.1 is on P2 so I think that we will stick to our P3 rule and sit on 9.13.1.
- Switchless clusters so no vol move migration for us. Snapmirror is currently on 1Gbps so data will be copied by database guys with their tools over FC. CIFS/NFS data will be maybe copied over SnapMirror but we are considering also XCP or some linux copies.
- Disable QoS on LUNs/VOLs to remove iops performance limit so databases can behave nicely.
- Move two db2 host links from old FC switches to new FC switches present new lun and let them copy data.
- Standard WWPN zoning from switch side, stay on defaults NPIV etc.
- We are so happy with new System Manager so we will for first time try to deploy with GUI to make things fast! Creating local tiers and snapmirrors, luns, fc svms, updating ONTAP and firmware DQP are so fast in new System Manager so I will give my fingers and CLI rest. But one caveat is default QoS on vols and luns- we will disable it after creation.
- Server guys told us that hosts are on linux centos 7 but they will upgrade them to rhel later. They all have Emulex LPe31002-M6 with 12.6 firmware supported by broadcom. Netapp ASA and C-Series is on interop list for that HBA. FC Switch will se it also.
Any advices? Or tips? Or to what we should look like these unfortunate default QoS policies? Thanks!
barren ore
inland bone
agile halo