Removing MPxIO devices without a reboot on Solaris 10

In the Marvel universe, can a human have a baby with any non-human?

First-year PhD giving a talk among well-established researchers in the field

How come I was asked by a CBP officer why I was in the US?

What is the line crossing the Pacific Ocean that is shown on maps?

Architecture of networked game engine

Does anycast addressing add additional latency in any way?

What happens when your group is victim of a surprise attack but you can't be surprised?

Can a US president have someone sent to prison?

Why is C++ initial allocation so much larger than C's?

How can I set command-line parameters through `.emacs` file?

Why is Madam Hooch not a professor?

Is adding a new player (or players) a DM decision, or a group decision?

Fitting a mixture of two normal distributions for a data set?

Does squid ink pasta bleed?

Links to webpages in books

Should I include salary information on my CV?

Bash echo $-1 prints hb1. Why?

Why cruise at 7000' in an A319?

What would Earth look like at night in medieval times?

Is my Rep in Stack-Exchange Form?

Does the posterior necessarily follow the same conditional dependence structure as the prior?

STM Microcontroller burns every time

Using “sparkling” as a diminutive of “spark” in a poem

Counting occurrence of words in table is slow



Removing MPxIO devices without a reboot on Solaris 10







.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















I'm performing a storage migration between two fiber channel connected EMC arrays. I've already moved the data from the disks on the old array to the disks on the new array. Now I want to remove the old disks from the OS so the array can be un-zoned without the OS noticing and raising alerts because disks have disappeared. I really don't want to have to reboot to achieve this.



I can do this without issue with non-MPxIO disks, but for MPxIO disks my usual technique isn't working.



My usual technique is to use



luxadm -e offline /dev/rdsk/cXtXdXs2
devfsadm -Cvc disk


Here's an example. This is in my test lab which isn't connected to EMC arrays, but an old SENA (A5100), but it should work the same for any FC connected disks. As you can see it doesn't work at all



v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0
v480:root $ luxadm -e offline /dev/rdsk/c6t20000020371AC414d0s2
v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0


Trying to remove the underlying devices doesn't work either



v480:root $ luxadm -e offline /dev/rdsk/c5t22d0s2
Error: Invalid pathname (/dev/rdsk/c5t22d0s2)
v480:root $ luxadm -e offline /dev/rdsk/c2t22d0s2
Error: Invalid pathname (/dev/rdsk/c2t22d0s2)


Does anyone know how this is done?










share|improve this question






















  • I've always had to reboot. No idea on this.

    – ewwhite
    Jun 21 '15 at 21:18

















1















I'm performing a storage migration between two fiber channel connected EMC arrays. I've already moved the data from the disks on the old array to the disks on the new array. Now I want to remove the old disks from the OS so the array can be un-zoned without the OS noticing and raising alerts because disks have disappeared. I really don't want to have to reboot to achieve this.



I can do this without issue with non-MPxIO disks, but for MPxIO disks my usual technique isn't working.



My usual technique is to use



luxadm -e offline /dev/rdsk/cXtXdXs2
devfsadm -Cvc disk


Here's an example. This is in my test lab which isn't connected to EMC arrays, but an old SENA (A5100), but it should work the same for any FC connected disks. As you can see it doesn't work at all



v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0
v480:root $ luxadm -e offline /dev/rdsk/c6t20000020371AC414d0s2
v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0


Trying to remove the underlying devices doesn't work either



v480:root $ luxadm -e offline /dev/rdsk/c5t22d0s2
Error: Invalid pathname (/dev/rdsk/c5t22d0s2)
v480:root $ luxadm -e offline /dev/rdsk/c2t22d0s2
Error: Invalid pathname (/dev/rdsk/c2t22d0s2)


Does anyone know how this is done?










share|improve this question






















  • I've always had to reboot. No idea on this.

    – ewwhite
    Jun 21 '15 at 21:18













1












1








1








I'm performing a storage migration between two fiber channel connected EMC arrays. I've already moved the data from the disks on the old array to the disks on the new array. Now I want to remove the old disks from the OS so the array can be un-zoned without the OS noticing and raising alerts because disks have disappeared. I really don't want to have to reboot to achieve this.



I can do this without issue with non-MPxIO disks, but for MPxIO disks my usual technique isn't working.



My usual technique is to use



luxadm -e offline /dev/rdsk/cXtXdXs2
devfsadm -Cvc disk


Here's an example. This is in my test lab which isn't connected to EMC arrays, but an old SENA (A5100), but it should work the same for any FC connected disks. As you can see it doesn't work at all



v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0
v480:root $ luxadm -e offline /dev/rdsk/c6t20000020371AC414d0s2
v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0


Trying to remove the underlying devices doesn't work either



v480:root $ luxadm -e offline /dev/rdsk/c5t22d0s2
Error: Invalid pathname (/dev/rdsk/c5t22d0s2)
v480:root $ luxadm -e offline /dev/rdsk/c2t22d0s2
Error: Invalid pathname (/dev/rdsk/c2t22d0s2)


Does anyone know how this is done?










share|improve this question














I'm performing a storage migration between two fiber channel connected EMC arrays. I've already moved the data from the disks on the old array to the disks on the new array. Now I want to remove the old disks from the OS so the array can be un-zoned without the OS noticing and raising alerts because disks have disappeared. I really don't want to have to reboot to achieve this.



I can do this without issue with non-MPxIO disks, but for MPxIO disks my usual technique isn't working.



My usual technique is to use



luxadm -e offline /dev/rdsk/cXtXdXs2
devfsadm -Cvc disk


Here's an example. This is in my test lab which isn't connected to EMC arrays, but an old SENA (A5100), but it should work the same for any FC connected disks. As you can see it doesn't work at all



v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0
v480:root $ luxadm -e offline /dev/rdsk/c6t20000020371AC414d0s2
v480:root $ stmsboot -L | grep /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c5t22d0 /dev/rdsk/c6t20000020371AC414d0
/dev/rdsk/c2t22d0 /dev/rdsk/c6t20000020371AC414d0


Trying to remove the underlying devices doesn't work either



v480:root $ luxadm -e offline /dev/rdsk/c5t22d0s2
Error: Invalid pathname (/dev/rdsk/c5t22d0s2)
v480:root $ luxadm -e offline /dev/rdsk/c2t22d0s2
Error: Invalid pathname (/dev/rdsk/c2t22d0s2)


Does anyone know how this is done?







solaris-10






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jun 21 '15 at 21:14









Pete StubbsPete Stubbs

63 bronze badges




63 bronze badges












  • I've always had to reboot. No idea on this.

    – ewwhite
    Jun 21 '15 at 21:18

















  • I've always had to reboot. No idea on this.

    – ewwhite
    Jun 21 '15 at 21:18
















I've always had to reboot. No idea on this.

– ewwhite
Jun 21 '15 at 21:18





I've always had to reboot. No idea on this.

– ewwhite
Jun 21 '15 at 21:18










1 Answer
1






active

oldest

votes


















0














I found the answer to this question in the Solaris docs. It boils down to unconfiguring (cfgadm -c unconfigure) the device using the device wwn given by cfgadm -al and cleaning up with devfsadm. The difficulty then is identifying the wwns that correspond to the MPxIO device you want to remove. This little script should print the device wwn and it's corresponding device file.



 fcinfo hba-port | awk '/HBA Port WWN: / HBAwwn=$NF /OS Device Name:/ print $NF, HBAwwn' | sed 's//dev/cfg///g' | while read ctlr HBAwwn
do
fcinfo remote-port -sp $HBAwwn | awk '/Remote Port WWN: / rpwwn=$NF /OS Device Name/ print "'$ctlr'::" rpwwn, $NF'
done


eg.



 c0::500000e010f3eaf2 /dev/rdsk/c0t1d0s2
c0::500000e010f23c62 /dev/rdsk/c0t0d0s2
c5::21000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2
c2::22000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2


So here to drop /dev/rdsk/c6t20000020371AC414d0s2 you would run



 cfgadm -c unconfigure c5::21000020371ac414 c2::22000020371ac414
devfsadm -Cvc disk


Oracle call MPxIO 'StorageTek Traffic Manager software' or STMS which made the docs harder to find.



The Solaris 11 equivalent docs are here. They look almost identical to the Solaris 10 ones. I haven't been able to find docs for earlier version but the lack of the fcinfo command and pre-leadville FC drivers must make it a real chore.






share|improve this answer

























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f700585%2fremoving-mpxio-devices-without-a-reboot-on-solaris-10%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I found the answer to this question in the Solaris docs. It boils down to unconfiguring (cfgadm -c unconfigure) the device using the device wwn given by cfgadm -al and cleaning up with devfsadm. The difficulty then is identifying the wwns that correspond to the MPxIO device you want to remove. This little script should print the device wwn and it's corresponding device file.



     fcinfo hba-port | awk '/HBA Port WWN: / HBAwwn=$NF /OS Device Name:/ print $NF, HBAwwn' | sed 's//dev/cfg///g' | while read ctlr HBAwwn
    do
    fcinfo remote-port -sp $HBAwwn | awk '/Remote Port WWN: / rpwwn=$NF /OS Device Name/ print "'$ctlr'::" rpwwn, $NF'
    done


    eg.



     c0::500000e010f3eaf2 /dev/rdsk/c0t1d0s2
    c0::500000e010f23c62 /dev/rdsk/c0t0d0s2
    c5::21000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2
    c2::22000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2


    So here to drop /dev/rdsk/c6t20000020371AC414d0s2 you would run



     cfgadm -c unconfigure c5::21000020371ac414 c2::22000020371ac414
    devfsadm -Cvc disk


    Oracle call MPxIO 'StorageTek Traffic Manager software' or STMS which made the docs harder to find.



    The Solaris 11 equivalent docs are here. They look almost identical to the Solaris 10 ones. I haven't been able to find docs for earlier version but the lack of the fcinfo command and pre-leadville FC drivers must make it a real chore.






    share|improve this answer



























      0














      I found the answer to this question in the Solaris docs. It boils down to unconfiguring (cfgadm -c unconfigure) the device using the device wwn given by cfgadm -al and cleaning up with devfsadm. The difficulty then is identifying the wwns that correspond to the MPxIO device you want to remove. This little script should print the device wwn and it's corresponding device file.



       fcinfo hba-port | awk '/HBA Port WWN: / HBAwwn=$NF /OS Device Name:/ print $NF, HBAwwn' | sed 's//dev/cfg///g' | while read ctlr HBAwwn
      do
      fcinfo remote-port -sp $HBAwwn | awk '/Remote Port WWN: / rpwwn=$NF /OS Device Name/ print "'$ctlr'::" rpwwn, $NF'
      done


      eg.



       c0::500000e010f3eaf2 /dev/rdsk/c0t1d0s2
      c0::500000e010f23c62 /dev/rdsk/c0t0d0s2
      c5::21000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2
      c2::22000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2


      So here to drop /dev/rdsk/c6t20000020371AC414d0s2 you would run



       cfgadm -c unconfigure c5::21000020371ac414 c2::22000020371ac414
      devfsadm -Cvc disk


      Oracle call MPxIO 'StorageTek Traffic Manager software' or STMS which made the docs harder to find.



      The Solaris 11 equivalent docs are here. They look almost identical to the Solaris 10 ones. I haven't been able to find docs for earlier version but the lack of the fcinfo command and pre-leadville FC drivers must make it a real chore.






      share|improve this answer

























        0












        0








        0







        I found the answer to this question in the Solaris docs. It boils down to unconfiguring (cfgadm -c unconfigure) the device using the device wwn given by cfgadm -al and cleaning up with devfsadm. The difficulty then is identifying the wwns that correspond to the MPxIO device you want to remove. This little script should print the device wwn and it's corresponding device file.



         fcinfo hba-port | awk '/HBA Port WWN: / HBAwwn=$NF /OS Device Name:/ print $NF, HBAwwn' | sed 's//dev/cfg///g' | while read ctlr HBAwwn
        do
        fcinfo remote-port -sp $HBAwwn | awk '/Remote Port WWN: / rpwwn=$NF /OS Device Name/ print "'$ctlr'::" rpwwn, $NF'
        done


        eg.



         c0::500000e010f3eaf2 /dev/rdsk/c0t1d0s2
        c0::500000e010f23c62 /dev/rdsk/c0t0d0s2
        c5::21000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2
        c2::22000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2


        So here to drop /dev/rdsk/c6t20000020371AC414d0s2 you would run



         cfgadm -c unconfigure c5::21000020371ac414 c2::22000020371ac414
        devfsadm -Cvc disk


        Oracle call MPxIO 'StorageTek Traffic Manager software' or STMS which made the docs harder to find.



        The Solaris 11 equivalent docs are here. They look almost identical to the Solaris 10 ones. I haven't been able to find docs for earlier version but the lack of the fcinfo command and pre-leadville FC drivers must make it a real chore.






        share|improve this answer













        I found the answer to this question in the Solaris docs. It boils down to unconfiguring (cfgadm -c unconfigure) the device using the device wwn given by cfgadm -al and cleaning up with devfsadm. The difficulty then is identifying the wwns that correspond to the MPxIO device you want to remove. This little script should print the device wwn and it's corresponding device file.



         fcinfo hba-port | awk '/HBA Port WWN: / HBAwwn=$NF /OS Device Name:/ print $NF, HBAwwn' | sed 's//dev/cfg///g' | while read ctlr HBAwwn
        do
        fcinfo remote-port -sp $HBAwwn | awk '/Remote Port WWN: / rpwwn=$NF /OS Device Name/ print "'$ctlr'::" rpwwn, $NF'
        done


        eg.



         c0::500000e010f3eaf2 /dev/rdsk/c0t1d0s2
        c0::500000e010f23c62 /dev/rdsk/c0t0d0s2
        c5::21000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2
        c2::22000020371ac414 /dev/rdsk/c6t20000020371AC414d0s2


        So here to drop /dev/rdsk/c6t20000020371AC414d0s2 you would run



         cfgadm -c unconfigure c5::21000020371ac414 c2::22000020371ac414
        devfsadm -Cvc disk


        Oracle call MPxIO 'StorageTek Traffic Manager software' or STMS which made the docs harder to find.



        The Solaris 11 equivalent docs are here. They look almost identical to the Solaris 10 ones. I haven't been able to find docs for earlier version but the lack of the fcinfo command and pre-leadville FC drivers must make it a real chore.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 29 '15 at 10:20









        Pete StubbsPete Stubbs

        63 bronze badges




        63 bronze badges



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Server Fault!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f700585%2fremoving-mpxio-devices-without-a-reboot-on-solaris-10%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

            Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

            What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company