The default pathing policy for a LUN can be changed (for example from Fixed to Round Robin). This can be a LUN on an iSCSI or FC array (or FCoE for that matter).
When I refer to pathing policy I'm refering to what you may have seen if you've ever clicked manage path's on a VMFS datastore and see it set to Fixed, Round Robin (RR) or Most Recently Used (MRU).
In this example I will be changing the default pathing policy for an EqualLogic array from Fixed to Round Robin.
Before I get into how to change the multi-pathing policy, it's important to understand the below 3 plugins (NMP, SATP and PSP):
I recently came across a vCenter/Update Manager server which had been built whilst been joined to one domain. Then later it has been removed from that domain and joined to a different one.
i.e. from "something.local" to "managed.something.com"
As such VMware vSphere Update Manager has not been reconfigured as was not working correctly (even though the service was running), giving the following errors:
"Plug-in is unavailable for the following server(s) : server.something.local"
"There was an error connecting to VMware vSphere Update Manager [server.managed.something.com]"
"The request failed because the server name 'server.something.local' could not be resolved"
Welcome to the final part 4 of my vCenter Orchestrator series! Don't worry I'm sure I'll do more vCO blogs in addition to this series, it's product with a huge amount of possibilities and as I gain experience with it I'll try and share that with you!
We have now deployed vCO as a virtual appliance, configured it and ran a couple of workflows to see how it works and integrates with vSphere Web Client.
We're going to take the integration with vSphere Web Client just a little bit further. In the previous part 3, you saw a vCenter Orchestrator context menu, from which we ran a workflow.
It's possible modify that context menu and add additional workflows, both existing and new to that context menu.
And you can choose whether thats the context menu at the Datacenter level, cluster, folder, VM and so on.
In the first 2 parts we deployed and configured vCOPS foundation edition.
vCenter Operations Manager 5.8 (vCOPS) - Part 2 Configuring vCOPs and Introduction to vCOPS Foundation
Now in this 3rd instalment we are going to upgrade from vCOPS foundation to standard edition.
Standard edition still only requires the virtual appliance (vApp) and is simply upgraded by assigning a license key and the vCOPS edition changes on fly.
Share this blog post on social media:Tweet
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.