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.
- Accessing Security Insights with SolarWinds Network Insight For Cisco ASA - June 7, 2018
- McKesson’s SD-WAN Journey to Cost Savings - May 31, 2018
- Unlocking VXLAN with Mellanox - May 30, 2018
- Solving Complexity with SD-WAN at National Instruments - May 15, 2018
- Detecting Cryptocurrency Mining with Vectra Cognito - April 13, 2018
- Extreme Networks SLX Platform – Extremely Easy Analytics - April 9, 2018
- Succeeding With SaaS and Viptela Cloud On-Ramp - April 5, 2018
- Treating Your Cloud Like an SD-WAN Branch - March 21, 2018
- Taking SD-WAN Even Wider at Acadia - March 14, 2018
- Gaining Visibility with ObserverLive - March 13, 2018