Not much of a problem but it looks like vCenter caches the management network and takes a bit of time to refresh after you make a change to the Management
I’ve been meaning to write a post about an issue we experienced in a project for a client earlier in the summer but kept forgetting or was too busy so
I made the mistake in typing in a different Domain ID during a Nexus 1000v deployment (see post: https://blog.terenceluk.com/installing-cisco-nexus-1000v-404sv13b/) with 2 VSMs and had problems configuring the 2 VSMs in
I thought about this several times as to whether I should write this post as it’s part of the steps I had to take while working with Cisco and VMware
Have you ever tried clicking on the Download and Install option for the Nexus 1000v? What you’ll notice is that when you do, you’ll get the following error: An internal
While making the mistake of trying to copy the startup configuration to the running configuration (see post: https://blog.terenceluk.com/problems-copying-startup-config-to/) I managed to have the Nexus 1000v disable SSH access. Long story
This post has nothing to do with the design or functionality of the Nexus 1000v but more of a mistake I managed to make without really thinking. I always joked
As most of you may know, the Nexus 1000v VEM which resides on the ESX/ESXi hosts are automatically deployed if you have VMware Update Manager deployed and while I don’t
