ccatano2000's Posts

turns out to be an issue with the Nexus SV version and VMware.. Here is the posted solution from support This issue is mostly a result of multiple fail overs between VSM's in an HA configurati... See more...
turns out to be an issue with the Nexus SV version and VMware.. Here is the posted solution from support This issue is mostly a result of multiple fail overs between VSM's in an HA configuration. To restore connectivity issue perform the following..    1. Login to the ESX host.    2. Restart the DPA with the following command.       /etc/init.d/vem-v1xx-vssnet-dpa restart This issue has been fixed in the following version..     * Cisco Nexus 1000v 4.0(4)SV1(3) So after issuing the above commands,  must upgrade our Nexus platform to version 1000v 4.0(4)SV1(3) thanks all, chris
Hi All, i had to vacate a blade chassis for repair this weekend,  the predeployment tasks included vacating all hosts in that chassis so it could be powered down..  upon doing this I vmotioned a... See more...
Hi All, i had to vacate a blade chassis for repair this weekend,  the predeployment tasks included vacating all hosts in that chassis so it could be powered down..  upon doing this I vmotioned all vms off of these hosts onto others... All hosts are in a drs/ha cluster with distributed network switches.  Upon vmotioning,  five vm's didnt have network connectivity afterwards.  I had to go into their settings, disconnect the virtual network, and then reconnect it in order to get it to ping and server packets.  Has anyone else seen this,  any ideas as to what might have caused this.  i am performing an RCA and just wanted to see if other companies had experienced this issue and what might be a fix.  We are running esx1 4.0 on HP Blade systems.  thanks a bunch, chris
I did put the $ sign in and I got this as a result.... ESXHOST1 443 root Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true t... See more...
I did put the $ sign in and I got this as a result.... ESXHOST1 443 root Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true Default PSP for VMW_SATP_ALUA is now VMW_PSP_RR true true I performed it to 11 LUNs,  which is why I believe we see 11 confirmations,  and I performed it on all 16 hosts in the cluster,  so the above return is only for one host, but I did get 16 of them.  Then I rescanned all HBA's went in to verify the changes and it worked great !!  Stoked, Thanks LucD !!!
Hi LucD, I think I have this pretty close to working properly,  I have one more quick question.  So the goal is to as you know login to an entire cluster and change thrree parameters on a spe... See more...
Hi LucD, I think I have this pretty close to working properly,  I have one more quick question.  So the goal is to as you know login to an entire cluster and change thrree parameters on a specified set of LUNs on all hosts in that cluster.  based on our previous threads ,  heres what I have... my question is now that we have specified the exact LUNS,  what do I put in the "naa.00xxxxxxxxxxx" values for the esxcli.nmp values ?  is it going to be "$luns" below is the code I think will encompass everything.  how does it look ? Connect-VIServer-Server MyVsphereServer -User User1 -Password Password1 foreach($esx in Get-Cluster ProductionCluster02 | Get-VMHost) { Connect-VIServer -Server $esx.Name -User <esx-user> -Password <esx-pswd> $esxcli = Get-EsxCli -Server $esx.Name $luns = "naa.600xxxxxxxxxxxxxxxx0000","naa.600xxxxxxxxxxxxxxxx0001","naa.600xxxxxxxxxxxxxxxx0002", "naa.600xxxxxxxxxxxxxxxx0003","naa.600xxxxxxxxxxxxxxxx0004","naa.600xxxxxxxxxxxxxxxx0005", "naa.600xxxxxxxxxxxxxxxx0006","naa.600xxxxxxxxxxxxxxxx0007","naa.600xxxxxxxxxxxxxxxx0008", "naa.600xxxxxxxxxxxxxxxx0009","naa.600xxxxxxxxxxxxxxxx0010" Connect-VIServer -Server ESXSERVER01 -User root -Password Password01 $esxcli = Get-EsxCli $luns | %{ esxcli.nmp.device.setpolicy($null,$_, "VMW_PSP_RR") esxcli.nmp.device.setpolicy($null,"naa.00xxxxxxxxxxxxxxx", "VMW_PSP_RR") esxcli.nmp.roundrobin.setconfig($null,"naa.00xxxxxxxxxxxxxxx",1,"iops",$null) Disconnect-VIServer $esx.Name .........Since we are calling the luns above,  what do I put in for the "Naa's"  would it look like this ? Connect-VIServer-Server MyVsphereServer -User User1 -Password Password1 foreach($esx in Get-Cluster ProductionCluster02 | Get-VMHost) { Connect-VIServer -Server $esx.Name -User <esx-user> -Password <esx-pswd> $esxcli = Get-EsxCli -Server $esx.Name $luns = "naa.600xxxxxxxxxxxxxxxx0000","naa.600xxxxxxxxxxxxxxxx0001","naa.600xxxxxxxxxxxxxxxx0002", "naa.600xxxxxxxxxxxxxxxx0003","naa.600xxxxxxxxxxxxxxxx0004","naa.600xxxxxxxxxxxxxxxx0005", "naa.600xxxxxxxxxxxxxxxx0006","naa.600xxxxxxxxxxxxxxxx0007","naa.600xxxxxxxxxxxxxxxx0008", "naa.600xxxxxxxxxxxxxxxx0009","naa.600xxxxxxxxxxxxxxxx0010" Connect-VIServer -Server ESXSERVER01 -User root -Password Password01 $esxcli = Get-EsxCli $luns | %{ esxcli.nmp.device.setpolicy($null,$_, "VMW_PSP_RR") esxcli.nmp.device.setpolicy($null,"$luns", "VMW_PSP_RR") esxcli.nmp.roundrobin.setconfig($null,"$luns",1,"iops",$null) Disconnect-VIServer $esx.Name
awesome that makes sense ! I noticed you answered my other post too about multiple luns at once... is it possible to incorporate the two sets of code to perform the three functions to all the LU... See more...
awesome that makes sense ! I noticed you answered my other post too about multiple luns at once... is it possible to incorporate the two sets of code to perform the three functions to all the LUNS defined by :     $luns= "naa.1","naa.2", "naa.3"..... So I could essentially perform the iops, default path, and current path adjustments to the cluster for all specified LUNS1-3 or so ? or should I break it up into individual lun operations ? Thanks for your help,  I hope Im not being to much of a pest, but it is nice to get the right direction from a pro ! Chris
thanks again LUCD, So, essentially what I am doing is defining them prior to calling them from the script right ? i use    $LUNS = "NAA1", "NAA2", "NAA3".....etc    to define the desired lun... See more...
thanks again LUCD, So, essentially what I am doing is defining them prior to calling them from the script right ? i use    $LUNS = "NAA1", "NAA2", "NAA3".....etc    to define the desired luns to modify,  then I call the script below which references "$LUNS=" right ? thanks again for all your help,  I cant wait to give it a try. chris
Thanks that is awesome !! I really appreciate it, If I am gathering it correctly,  you are saying that since I have 16 hosts....say host1-5 ,  I would have 5 of each of those lines as such ? ... See more...
Thanks that is awesome !! I really appreciate it, If I am gathering it correctly,  you are saying that since I have 16 hosts....say host1-5 ,  I would have 5 of each of those lines as such ? Connect-VIServer-Server MyVsphereServer -User User1 -Password Password1 foreach($esx in Get-Cluster ProductionCluster02 | Get-VMHost) {     Connect-VIServer -Server ESXHOST1-User <esx-user> -Password <esx-pswd>      Connect-VIServer -Server ESXHOST2 -User <esx-user> -Password <esx-pswd>      Connect-VIServer -Server ESXHOST3 -User <esx-user> -Password <esx-pswd>      Connect-VIServer -Server ESXHOST4 -User <esx-user> -Password <esx-pswd>      Connect-VIServer -Server ESXHOST5 -User <esx-user> -Password <esx-pswd>     $esxcli = Get-EsxCli -Server ESXHOST1     $esxcli = Get-EsxCli -Server ESXHOST2      $esxcli = Get-EsxCli -Server ESXHOST3      $esxcli = Get-EsxCli -Server ESXHOST4      $esxcli = Get-EsxCli -Server ESXHOST5     $esxcli.nmp.satp.setdefaultpsp("VMW_PSP_RR","VMW_SATP_ALUA")     $esxcli.nmp.device.setpolicy($null,"naa.00xxxxxxxxxxxxxxx", "VMW_PSP_RR")     $esxcli.nmp.roundrobin.setconfig($null,"naa.00xxxxxxxxxxxxxxx",1,"iops",$null)     Disconnect-VIServer ESXHOST1          Disconnect-VIServer ESXHOST2      Disconnect-VIServer ESXHOST3      Disconnect-VIServer ESXHOST4      Disconnect-VIServer ESXHOST5 sorry I am loving the PowerCLI,  but still very new to it....  I appreciate your help.. Also,  after setting the IOPS to 1 does the host need to be rebooted ?  or just rescan the HBA'S ? thanks again !
Does anyone know how I can modify the below scripts to include a list of say 10 luns, rather than a single one ? Connect-VIServer -Server ESXSERVER01 -User root -Password Password01 esxcli... See more...
Does anyone know how I can modify the below scripts to include a list of say 10 luns, rather than a single one ? Connect-VIServer -Server ESXSERVER01 -User root -Password Password01 esxcli = Get-EsxCli esxcli.nmp.device.setpolicy($null,"naa.600xxxxxxxxxxxxxxxxxxxx0000", "VMW_PSP_RR") I want to be able to have it set the policy for LUNS naa.600xxxxxxxxxxxxxxxx0000 through naa.600xxxxxxxxxxxxxxxxxxxx0010 ...  How do I list them  in the script ? would I do them semicolon seperated as such : esxcli.nmp.device.setpolicy($null,"naa.600xxxxxxxxxxxxxxxxxxxx0000";"naa.600xxxxxxxxxxxxxxxxxxxx0001";"naa.600xxxxxxxxxxxxxxxxxxxx0002", "VMW_PSP_RR") ???
Hi All, I am trying to adjust some of our LUN and storage configurations for a particular cluster and set of LUNS. We have ESX4i and I am using PowerCLI to script it. I am having some trouble ... See more...
Hi All, I am trying to adjust some of our LUN and storage configurations for a particular cluster and set of LUNS. We have ESX4i and I am using PowerCLI to script it. I am having some trouble though getting it work properly and dont have enough PowerCLI skills to find out whats wrong.. I have looked at everything and think I am close. heres what I want to do : Login to all the hosts in a cluster at the same time and change the current path selection to Round Robin, set the default path selection to round robin, and set the IOPS to 1. below is the code I am using, can someone please tell me where I am messing up ..thanks ! to connect to the cluster first I am using : Connect-VIServer-Server MyVsphereServer -User User1 -Password Password1 foreach($esx in Get-Cluster ProductionCluster02 | Get-VMHost) { then I issue the following to set the default policy going forward to Round Robin : $esxcli.nmp.satp.setdefaultpsp("VMW_PSP_RR","VMW_SATP_ALUA")} Then I issue the following to set the current path policy to Round Robin : $esxcli.nmp.device.setpolicy($null,"naa.00xxxxxxxxxxxxxxx", "VMW_PSP_RR") Then I issue the following to set the IOPS to 1 instead of 1000 $esxcli.nmp.roundrobin.setconfig($null,"naa.naa.00xxxxxxxxxxxxxxx",1,"iops",$null) } When I login to a single host and run this one at a time using the Connect-viserver and putting the actual host name, not the virtual center server name in there and run it one at a time it works... So all together I want to change on multiple hosts, the above three functions at once... Here is what it looks like all together. Connect-VIServer-Server MyVsphereServer -User User1 -Password Password1 foreach($esx in Get-Cluster ProductionCluster02 | Get-VMHost) { $esxcli.nmp.satp.setdefaultpsp("VMW_PSP_RR","VMW_SATP_ALUA")} { $esxcli.nmp.device.setpolicy($null,"naa.00xxxxxxxxxxxxxxx", "VMW_PSP_RR")} { $esxcli.nmp.roundrobin.setconfig($null,"naa.00xxxxxxxxxxxxxxx",1,"iops",$null) } This is failing...can anyone give me a suggestion as to why ? or do you have any suggestions for a better approach ? thanks guys, chris
Hi all, I am fairly new to using PowerCLI,  but have already seen the benefits of using it to help manage and administer a large infrastructure,  we have about 50 hosts using esx4i,  and it has... See more...
Hi all, I am fairly new to using PowerCLI,  but have already seen the benefits of using it to help manage and administer a large infrastructure,  we have about 50 hosts using esx4i,  and it has been very useful.  I have a problem though in trying to run a health check,  I want to create a batch file that calls a .ps1 script and then schedule it as a task...  However,  here is the batch file code : C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" -command "&{c:\scripts\myscript.ps1}" it comes up with this in the cmd prompt after running the batch file : Please specify a VI Server name eg....       powershell.exe vCheck.ps1 MyvCenter However I have the Connect-Viserver connection code in the myscript.ps1 ... The script runs great from PowerCLI ,  does anyone know what I am missing ?  Thanks for your help....any input would be appreciated. chris
Hi all, I am fairly new to using PowerCLI,  but have already seen the benefits of using it to help manage and administer a large infrastructure,  we have about 50 hosts using esx4i,  and it has ... See more...
Hi all, I am fairly new to using PowerCLI,  but have already seen the benefits of using it to help manage and administer a large infrastructure,  we have about 50 hosts using esx4i,  and it has been very useful.  I have a problem though in trying to run a health check,  I want to create a batch file that calls a .ps1 script and then schedule it as a task...  However,  here is the batch file code : C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" -command "&{c:\scripts\myscript.ps1}" it comes up with this in the cmd prompt after running the batch file : Please specify a VI Server name eg....       powershell.exe vCheck.ps1 MyvCenter However I have the Connect-Viserver connection code in the myscript.ps1 ... The script runs great from PowerCLI ,  does anyone know what I am missing ?  Thanks for your help....any input would be appreciated. chris
Thanks it worked great,  no vm shutdowns or anything,  was able to change the NTP, DNS, and root password,  then add the hosts into the new VC and clusters and then re-enable HA...  Long day,  b... See more...
Thanks it worked great,  no vm shutdowns or anything,  was able to change the NTP, DNS, and root password,  then add the hosts into the new VC and clusters and then re-enable HA...  Long day,  but went smooth.
I found this in a previous post,  has anyone experienced this before with version esx 4i ? I believe the issue was that during a create or delete snapshots operation,  the virtual machine was un... See more...
I found this in a previous post,  has anyone experienced this before with version esx 4i ? I believe the issue was that during a create or delete snapshots operation,  the virtual machine was unexpectedly powered off with the symptoms :  The create or delete snapshot task fails,  and the virtual machine is powered off with error. This issue occurs when one of the files required by the virtual machine has been opened by another application during a Create or Delete Snapshot operation while a Virtual machine is running, all the disk files are momentarily closed and reopened. During this window, the files could be opened by another Virtual machine, management process, or third-party utility. If that application creates and maintains a lock on the required disk files, the Virtual machine cannot reopen the file and resume running. We will look through the ESX logs to verify this first and should look at the NETAPP snapmanager settings for this particular vm and ensure that it is set to quiesce the disk prior to snapshots since it is a Sql server and is very write intensive.
hi all, We had a production sql server power off unexpectedly right after getting a failed snapshot error.  the snapshot was taken by our NetApp storage device for its backup.  I understand that... See more...
hi all, We had a production sql server power off unexpectedly right after getting a failed snapshot error.  the snapshot was taken by our NetApp storage device for its backup.  I understand that if the operating state of the memory is not preserved at the time of the snapshot revert,  it will power off. We are using esx4i and know that NetApp and vmware fixed this issue in version 3.5 u4 .   Has anybody seen this or have any suggestions on what could be the root cause or a fix ? Thanks for your time, chris
Hi all, We are pulling a failing EVA 8300 from our ESX 4i infrastructure,  I have evacuated all LUNS onto new Symmetrix storage,  so was going to get all the old LUN labels and NAA id's to give... See more...
Hi all, We are pulling a failing EVA 8300 from our ESX 4i infrastructure,  I have evacuated all LUNS onto new Symmetrix storage,  so was going to get all the old LUN labels and NAA id's to give to the storage team to reclaim on the old device. I wanted to ask you if you had any input or suggestions on the safest way to procede. I am proposing that we unpresent the LUNs on the storage side first to ensure that nothing in production falls offline,  then after verification that all the unpresented LUNs were in fact the old ones,  we can have them delete the LUNs and I can remove them from VC.. Or should I remove them from VC first and then have the storage team unpresent them ?  ... what do you recommend.. What I want to avoid is having a mislabeled LUN get deleted that in fact has production vms on it... I guess thats what the NAA's are for correct ? Have a great friday, chris
got it !  thanks. Chris
Thanks Troy, I appreciate your verification on this. Chris
Hi Troy, thats perfect,  the hardware is staying the exact same, just want to move it under a new VC for administration,  but all physical elements will remain the same...  I figured all the co... See more...
Hi Troy, thats perfect,  the hardware is staying the exact same, just want to move it under a new VC for administration,  but all physical elements will remain the same...  I figured all the configs were on the hosts,  storage, networking...etc and all the vm's will be running there regardless of the VC membership,  so I guess that is very good for us !  so will I do a "remove" or a "disconnect" on the hosts to be migrated ? thanks again, chris
Hi Troy, Thanks for your help the other day,  that was awesome, I had another issue I am facing and was wondering your input,  it kind of follows this same discussion path,  only the versions o... See more...
Hi Troy, Thanks for your help the other day,  that was awesome, I had another issue I am facing and was wondering your input,  it kind of follows this same discussion path,  only the versions of ESX4i are the same... I am preparing to migrate our 23 ESX4i hosts out of our virtual center here and move them into the new datacenter and cluster setup in our production datacenter in chicago....  All the hardware and configurations will remain the same,  we just want to add them to the new production Virtual Center ... Here is what I am planning on doing,  has anybody had good experience with this that maybe sees a flaw... I guess what I am wondering is if I migrate all the VM's off the host, put it into maintenance mode, remove it from the current vc infrastructure,  then add it to the new vc,  how do I get the VM's on there ??? So,  can I leave the VM's  on the host,  remove it from the current VC,  then add it to the new VC without interrupting the running virtual machines ? In this case it would be quite simple.... is there any way to avoid powering down the guests ? Please advise, Thanks a bunch, chris
Hi all, I am preparing to migrate our 23 ESX4i hosts out of our virtual center here and move them into the new datacenter and cluster setup in our production datacenter in chicago....  All the ... See more...
Hi all, I am preparing to migrate our 23 ESX4i hosts out of our virtual center here and move them into the new datacenter and cluster setup in our production datacenter in chicago....  All the hardware and configurations will remain the same,  we just want to add them to the new production Virtual Center ... Here is what I am planning on doing,  has anybody had good experience with this that maybe sees a flaw... I guess what I am wondering is if I migrate all the VM's off the host, put it into maintenance mode, remove it from the current vc infrastructure,  then add it to the new vc,  how do I get the VM's on there ??? So,  can I leave the VM's  on the host,  remove it from the current VC,  then add it to the new VC without interrupting the running virtual machines ? In this case it would be quite simple.... Please advise, Thanks a bunch, chris