Re: [Veritas-vx] changing vxdmp iopolicy on live volumes
Thank you! I think you hit the nail on the head with this one. After doing some research I do not have the netapp apm installed. (Though the ASL is installed.) Now I'm off to find where on the symantec website I can find the netapp apm and make sure I get all the asl/apm versions setup correctly. Romeo On Fri, Nov 21, 2008 at 5:32 PM, Joshua Fielden [EMAIL PROTECTED] wrote: Using vxdmpadm disable ctlr=cX to disable one path administratively (or other individual disable syntax as-needed) is the best-practice for doing SAN work. Iopolicy can be set on the fly -- are you sure you have the correct ASL/APM packages for NetAPP storage for your version? Having the wrong/missing APM (Array Policy Module) can cause problems during administrative path work. Cheers, jf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Romeo Theriault Sent: Friday, November 21, 2008 4:11 PM To: veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] changing vxdmp iopolicy on live volumes I was under the impression that changing vxdmp's iopolicy on the fly was supported. I recently changed a live Solaris 9 hosts vxdmp iopolicy from round-robin to singleactive and a handful of it's FCP SAN volumes went offline with read/write errors. I quickly switched the iopolicy back to round-robin and was able to get the offlined volumes back online with some fsck's, etc All of the volumes have two paths through different FCP cards and switches. So was I wrong, is changing the iopolicy on vxdmp not a safe thing to do? Should I have done something differently? This is what I did: vxdmpadm setattr enclosure FAS30500 iopolicy=singleactive On a related topic, the person whom I've replaced didn't leave the FCP switch passwords behind so we need to reboot the switches to their bootprom to reset the passwords. I was really hoping that I'd be able to change the iopolicy on the Solaris/Veritas machines to singleactive and then change their primary controller for a time being so I could reboot the FCP switches one at a time to reset their passwords, thus removing the need to shutdown all of the machines. Is this possible? Thanks for any hints and help on the matter, -- Romeo Theriault System Administrator Information Technology Services -- Romeo Theriault System Administrator Information Technology Services Ph#: 207-561-3517 Em@: [EMAIL PROTECTED] ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
[Veritas-vx] changing vxdmp iopolicy on live volumes
I was under the impression that changing vxdmp's iopolicy on the fly was supported. I recently changed a live Solaris 9 hosts vxdmp iopolicy from round-robin to singleactive and a handful of it's FCP SAN volumes went offline with read/write errors. I quickly switched the iopolicy back to round-robin and was able to get the offlined volumes back online with some fsck's, etc All of the volumes have two paths through different FCP cards and switches. So was I wrong, is changing the iopolicy on vxdmp not a safe thing to do? Should I have done something differently? This is what I did: vxdmpadm setattr enclosure FAS30500 iopolicy=singleactive On a related topic, the person whom I've replaced didn't leave the FCP switch passwords behind so we need to reboot the switches to their bootprom to reset the passwords. I was really hoping that I'd be able to change the iopolicy on the Solaris/Veritas machines to singleactive and then change their primary controller for a time being so I could reboot the FCP switches one at a time to reset their passwords, thus removing the need to shutdown all of the machines. Is this possible? Thanks for any hints and help on the matter, -- Romeo Theriault System Administrator Information Technology Services ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] changing vxdmp iopolicy on live volumes
Using vxdmpadm disable ctlr=cX to disable one path administratively (or other individual disable syntax as-needed) is the best-practice for doing SAN work. Iopolicy can be set on the fly -- are you sure you have the correct ASL/APM packages for NetAPP storage for your version? Having the wrong/missing APM (Array Policy Module) can cause problems during administrative path work. Cheers, jf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Romeo Theriault Sent: Friday, November 21, 2008 4:11 PM To: veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] changing vxdmp iopolicy on live volumes I was under the impression that changing vxdmp's iopolicy on the fly was supported. I recently changed a live Solaris 9 hosts vxdmp iopolicy from round-robin to singleactive and a handful of it's FCP SAN volumes went offline with read/write errors. I quickly switched the iopolicy back to round-robin and was able to get the offlined volumes back online with some fsck's, etc All of the volumes have two paths through different FCP cards and switches. So was I wrong, is changing the iopolicy on vxdmp not a safe thing to do? Should I have done something differently? This is what I did: vxdmpadm setattr enclosure FAS30500 iopolicy=singleactive On a related topic, the person whom I've replaced didn't leave the FCP switch passwords behind so we need to reboot the switches to their bootprom to reset the passwords. I was really hoping that I'd be able to change the iopolicy on the Solaris/Veritas machines to singleactive and then change their primary controller for a time being so I could reboot the FCP switches one at a time to reset their passwords, thus removing the need to shutdown all of the machines. Is this possible? Thanks for any hints and help on the matter, -- Romeo Theriault System Administrator Information Technology Services ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
