Cisco

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 HA until I was able

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 in resolving our orphaned Nexus

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 error occurred in the vSphere

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 short, after trying to regenerate

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 with clients about how my

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 recall implementing any vSphere deployments

As stated in my previous posts when deploying the Nexus 1000v (https://blog.terenceluk.com/installing-cisco-nexus-1000v-404sv13b/) please remember to not run the wizard for the installation on the 2nd node as going through the wizard to configure the VSM

There isn’t much on this post as the purpose of it is just to show what a Cisco Nexus 1000v 4.0.4.SV1.3b install looks like. Note: One of the things I noticed while looking for the