It *shouldn't* cause any issues. Hopefully this has already been done but a best practice is to block ports that aren't in use (the ones connected to the 2105 to be powered down). This way, when the cables are removed, the switch shouldn't report status changes back through the SAN. "Back in the day", depending on the switches, firmware, software, etc there were sometimes RSCN storms generated by relatively innocuous events; for some of our older servers on the SAN results were, as they say, unpredictable.
_______________________________________________________________________________ Karl S Huf | Senior Vice President | World Wide Technology 840 S Canal, Chicago, IL, 60607 | phone (312)630-6287 | k...@ntrs.com Please visit northerntrust.com CONFIDENTIALITY NOTICE: This communication is confidential, may be privileged and is meant only for the intended recipient. If you are not the intended recipient, please notify the sender ASAP and delete this message from your system. IRS CIRCULAR 230 NOTICE: To the extent that this message or any attachment concerns tax matters, it is not intended to be used and cannot be used by a taxpayer for the purpose of avoiding penalties that may be imposed by law. For more information about this notice, see http://www.northerntrust.com/circular230 P Please consider the environment before printing this e-mail. IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> wrote on 02/09/2011 03:59:20 PM: > From: "McBride, Catherine" <cmcbr...@kable.com> > To: <IBM-MAIN@bama.ua.edu> > Date: 02/09/2011 04:08 PM > Subject: IBM 2105 "Shark" decommissioning > Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> > > At long last we're taking down our IBM 2105. My question has to do with > the fact that the 2105 shares a McData switch with another SAN, and that > other SAN is live production. Powering down the 2105 and carefully > removing the cables and electrical power source should have no negative > effect on the McData switch or second SAN, correct? All cables and > power feeds are clearly marked, and we readily know which cables are the > correct ones. Anything else we need to be concerned about? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
