question on concurrent code upgrades in AIX&ESS environments

We have had a number of challenges for the past 3-4 years doing concurrent firmware/code upgrades to the ESS (we use 2105-800). The hardware is sold as concurrent code update capable and of course (rightfully so) the powers that be feel we should not need downtime to accomplish them?

We have had at least 3 service affecting episodes with them (downtime caused by LVM errors in AIX) that was directly relate to the ESS, or in one case SDD.

- Am I the only one that has this kind of "luck"?
- does your site allow concurrent updates, or do you take downtime?

I would truly appreciate any and all feedback. We really need to do a 'sanity check' for this process and re-think it. thanks.

Note: if you are reluctant to clutter up the list or if folks feel its off-topic please e-mail me directly. Dave.miller@xxxxxxx<mailto:Dave.miller@xxxxxxxx>.





---------------------------------
David Milller
Baystate Health System
Springfield, MA
dave.miller@xxxxxxx<mailto:dave.miller@xxxxxxx>

-------------------------------------------------------------------------------------------------------------------------------------------------
Fools ignore complexity. Pragmatists suffer it. Experts avoid it. Geniuses remove it (Alan J. Perlis)
-------------------------------------------------------------------------------------------------------------------------------------------------




-----------------------------------------
CONFIDENTIALITY NOTICE: This email communication and any
attachments may contain confidential and privileged information for
the use of the designated recipients named above. If you are not
the intended recipient, you are hereby notified that you have
received this communication in error and that any review,
disclosure, dissemination, distribution or copying of it or its
contents is prohibited. If you have received this communication in
error, please reply to the sender immediately or by telephone at
(413) 794-0000 and destroy all copies of this communication and any
attachments. For further information regarding Baystate Health's
privacy policy, please visit our Internet web site at
http://www.baystatehealth.com.

Relevant Pages

  • Re: Sp2 nodes outside of a frame
    ... power will be the problem ... attachments may contain confidential and privileged information for the ... communication in error and that any review, disclosure, dissemination, ... this communication and any attachments. ...
    (AIX-L)
  • two xntpd processes
    ... CONFIDENTIALITY NOTICE: This email communication and any ... attachments may contain confidential and privileged information for ...
    (AIX-L)
  • AIX networking question
    ... CONFIDENTIALITY NOTICE: This email communication and any ... attachments may contain confidential and privileged information for ...
    (AIX-L)
  • Re: Korn shell help
    ... CONFIDENTIALITY NOTICE: This email communication and any attachments may ... contain confidential and privileged information for the use of the ...
    (AIX-L)
  • Re: Question on unmirroring rootvg before mksysb
    ... CONFIDENTIALITY NOTICE: This email communication and any attachments may ... contain confidential and privileged information for the use of the ... 794-0000 and destroy all copies of this communication and any attachments. ...
    (AIX-L)