This week, I am away for Chinese New year break. Right before the break, I had heard some interesting feedback from my close buddy which talked about the topic here. Had been a while we didn’t hear any argument or comment that mentioned Cisco Nexus 1000V is useless or doesn’t meant anything. Previously, I had heard this from many competitors, partners & client previously, so it doesn’t surprise me when my buddy shared his story to me.
Well, there are many users, partner, or even principle who are reluctant to accept changes or new thing, which claimed nexus 1000V doesn’t bring any value while created problems to their day to day job. The main reason behind as they struggling to manage and configured nexus 1000v, mostly because they are just not the right person to manage it. Please do not feel offended with this statement, as I am telling the truth which myself are not the right person to configure SAP, Oracle, BI cognos too. We always need specified specialist and expertise from different area to compliment each others in IT environment.
Adoption to both virtualization and cloud computing, network become the important component of the success to both solutions. For many of the mature deployment and operation in virtualization, network become the uncontrolled piece in the virtual infrastructure which allow administrator to breech the change control management from the production network without proper authority from the network administrators. Some of you may not been agreed with this statement but it does impact the production environment.
The traditional vswitch or dvswitch did not provide control, manage as the physical switching environment in the data center. It allow administrator to provision new virtual machine and connect to network without proper request and change management in place. Let’s imagine, the effect will be the same as unauthorized persons connected a server to the production LAN without a change approval. In physical environment, we can shut off all the unused network ports in data center, in virtual, you will not able to perform this while using vswitch or dvswitch from vmware. Technology limitation for the past previous years does not allow network operation to be fully integrated until the Nexus 1000V from cisco & VMware join develop products come to place. This will allow administrator to manage and control the access level on the virtual environment as it does in physical switch. Transparency and Manageability is possible on virtual layer now. Network performance analysis and troubleshooting become easier compare to previous.
If you are deploying nexus 1000v in your VMware vSphere environment, you may usually hit to the point require to unload VEM, VSM or reconfigure. Today I found some tips just to share here. If you accidentally deleted your VSM which before you unload the VSM from the vCenter, you will either end up having orphan nexus 1000V show up in your vCenter. Even if you try to name the same as previous, it will prompt the error telling you that the previous extension key and your current extension are mismatch.
Recently there are many confusion about these new terms VN-Link & Cisco nexus 1000V which been widely communicated to the IT user groups. Where were the confusion come from? Most of the time, we are getting confuse about what is VN-Link meant by Cisco. Below is some short description you may want to refer to.
Cisco Nexus 1000V is a enhance virtual distributed virtual switch which integrate to the VMware vSphere 4. With Cisco Nexus 1000V, you will contain VSM and VEM, which VSM will be the virtual appliances that host the management of Nexus 1000V, and VEM will be installed on each ESX host that been connected to the Nexus 1000V. I will not go in too details about Nexus 1000V in this post as my intention is to clear up the confusion on the VN-Link meant by Cisco.
