The first thing I wanted to look at was my vCenter plugin URLs. These are the addresses used to talk with the plugin. If they were hard coded using an IP address, they’d need to be updated to either a new IP address or a DNS name. I figured it would be easiest to use DNS names going forward, so that IP changes are trivial.
The fastest way to dump all of the URLs for my plugins was to crank out a quick PowerCLI script. You can snag a copy from my PowerCLI GitHub repo.
Most of them were fine, or pointed towards the local server itself, but a few — such as my vCenter Operations Manager plugin — would need to be fixed.
I learned the hard way a few years ago that changing IP addresses for appliances isn’t trivial. Read this article from Chris so you don’t have any gotchas with your VMware environment when IP changes need to happen.
- Flexible NFV with Array Networks - August 7, 2017
- Cloud onRamp – Making The Cloud More Local For Your Users - July 26, 2017
- Feeling Your Flow with Plixer - July 19, 2017
- What Are ASICs? A Human Example - July 11, 2017
- Migrating to Healthcare Cloud Apps With Acadia and Viptela - June 5, 2017
- FutureWAN – The SD-WAN Education You Need - May 26, 2017
- Linksys and the Resurgence of the SMB - May 8, 2017
- Review – Docker Networking Cookbook - February 13, 2017
- The Future of SD-WAN Is Now! - January 10, 2017
- How Kindred Healthcare Uses SD-WAN to Secure Patient Data - December 2, 2016