VM Infrastructure Powershell Summary Report v. 2.5

PowerCLI_Logo-150x150

I've completely rewritten my original summary script for much faster performance (From 20 min. to approx. 3 min. in an environment running 60 Hosts, 1300VMs, and 181 Datastores).  Nothing much has changed as far as how or what it reports on, but here is a list of changes:

  1. Much Faster Performance.
  2. CSS can be used to change mouse cursor to hand icon for table header. 
  3. vCPU and Datastore Percent numbers to highlight ‘out of spec’ numbers in customizable variables now.
  4. Custom ico file specifiable. (icon to show up in supported browsers)
  5. Custom JScript specifiable. 
  6. Added some versioning

There is still plenty to be refined about this script, but it’s pretty fast and can give you an overall picture of how your environment is doing.  Plus, it’s a good thing to put in front of management to help them understand what’s going.  I run this script about every hour so I know when I need to allocate additional datastores.

It’s not part of this posted code, but I’ve added code to link cluster names to a more detailed report that shows host information about each cluster.  I’m working on the detailed report portion as it’s still rather cludgy.  Comments are appreciated. \(^o^)/

Click here to see an example of what the generated report looks and feels like. 

Here is the code: Get-SummaryReportv2.5.ps1

Comments

Unknown said…
Hi Im getting error datacenter DDTC was not found. This is beyond modifyable part so I did not touch it, but it seems like it is not correct
August 20, 2012 at 8:43 AM
Zsoldier said…
Edit that line to read what your datacenter node is specified as in your vcenter.
August 20, 2012 at 8:47 AM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more