Hello we are having a code upgrade on NS960 for flare it is from 4.30.0.5.512 to 4.30.0.5.524 and for DART it is from 6.0.41-3 to 6.0.61.0. What are the precautions we need to take before the upgrade. I know there will be down time for shares and exports on data mover(rebooting all at a time). After the reboot will the NFS exports will be in hung state do we need to reboot and then manually mount the exports again? In case of CIFS we use AD group policy script in order to map the shares to users. What precautions we need to take in case od CIFS?
Thank You Rainer and dynamox for the info. I have one more question, the CE performed a pre health check of the array and the report has few LUN's which have read and write cache disabled, trespassed and auto assign enabled with severity level as warning. Does this effect the LUN's or IO's during the upgrade.
if CIFS shares are already mapped, your users might have to double click on the drive to re-establish the session, other then that if they are not doing any activity during the reboot ..they will not know anything happened.
are you using this array for regular FC storage ..or NAS only ? If you are using it for regular FC storage i see there could be instances where read/write cache could be disabled on individual LUNs ..but if it's NAS only array that would be a concern.
then you are fine. Traspassed is not a big deal because when support upgrades the flare, it will trepass LUNs back and forth between SPA and SPB. Which LUNs have auto-assigned enabled ?
Rainer_EMC
6 Operator
•
8645 Posts
982
0
Posted September 20th, 2012 10:00
CIFS – nothing
NFS – nothing if you have hard mounts – if not your clients need to re-mount