Skip navigation

How Did I pass 300-101 Cisco Certified Network Professional Routing and Switching Exam Certification?

A Few years back, I’d been trying my luck in smearing for vital positions in major corporations, but it seems like the odds were not in my favor. I was intended to go with 300-101 exam questions that moment I was totally blanked, how I would pass my Cisco CCNP Routing and Switching certification exam.  I went through numerous exam material providers,  but couldn’t find any reliable material.  After struggling hard, I suddenly loomed to (TestsChamp). I never assumed that passing 300-101 exam dumps would be so easy. I scored 95% on my Cisco 300-101 exam with the help of TestsChamp updated exam material.

My Review of 300-101 Exam Practice Questions

While I was looking for the Cisco 300-101 exam questions and answers, I could not find a lot of rationalized study material; I never assumed that TestsChamp  would happen to me as sanction. I was worried, how to go about Cisco Certified Network Professional Routing and Switching Certification exam. I had not many options to consider, so I gave it a shot and it actually worked.

How I Prepared 300-101 Exam in One Week?

I finally passed Cisco Certified Network Professional Routing and Switching certification in the first try. The practice software of greatly reduces the burden of preparation by offering you the absolute real questions that one can come across in the 300-101 exam. I downloaded the practice software soon after the purchase from website and started practicing 300-101 exam.  All the exam questions were updated and accurate. The expert team prepares the exam material after analyzing the situations and needs to current curriculum.

300-101 Exam - Recommendations

Before buying the product, I got a chance to go through the material and get familiar with the interface. In fact, when I purchased the study material for Cisco 300-101 exam so, TestsChamp kept me informing with the amendments made by companies and experts. TestsChamp gave me 90 days free updates, which helped me to prepare for Cisco 300-101 exam to make Cisco Certified Network Professional Routing and Switching certified.

I can never thanks enough to for helping and accommodation me to prepare for Cisco Certified Network Professional Routing and Switching certification exam. I can totally relate myself to this exam material now even in future I will only be relying on TestsChamp to excel in my certification exam with leaving no stone unturned.



We have 4 ESXi 5.5 Hosts with shared storage and all ESXi hosts are behind a hardware firewall.

On all ESXi Hosts there was one vmnic connected to the prod-dmz on a switch.

I wanted to add another switch for redundancy, so I did.

I connected on the ESXi Hosts a vmnic, used earlier by another vSS, to the vSS attached to prod-dmz on the second switch, on the external firewall the two switches are on two nics on the firewall with link aggregation.

Everything actually went well - but some vms lost the network. Out of 46 Servers, 7 lost the network, even though everything was "green", I didn't see any differences to all other servers. Also the guest operating systems were CentOS5, Windows Server 2008 and 2012 - other servers with the same OS didn't have the problem. Also the affected vms were on two different ESXi hosts.

The affected machines were able to ping themselves and other vms in the same DMZ but not the GatewayIP  of the firewall internal nic. The other vms were able to ping and access everything.

It drove me nuts.

Than after some network troubleshooting I realized on a windows machine the warning that the media was disconnected.


What helped was changing the network adapter of the affected vms to another Switch, saving, editing it back to the wanted switch.

Some Linux machines needed a restart of the network, others didn't.


So just in case somebody changes nics between switches and has the same problem, this might help.


(btw if you cannot delete an old vSS after having moved all vms to another switch, remove the snapshots of the vms - if not possible rename the old switch first, afterwards you can delete it. The affected vms weren't the ones with snapshots in the above mentioned network problem).



I've been working on putting together Step-by-Step How-To's for installing and configuring NSX as well as vCAC.  Below are links that have the Step-by-Step overview for both NSX and vCAC.  Be sure to check back as additional use cases and more advanced configuration are being posted regularly.


NSX 6.1 Walk-Though

vCAC 6.x Walk-Through

In my previous NSX articles we covered installing and configuring NSX, We discussed deploying/configuring Transport Zones, Logical Switches, Logical RoutersEdge Gateways, and connecting the Logical and Edge Gateways.  With all these completed we now have an environment that with the appropriate routes and transport traffic from our physical network to our logical networks that we deployed.  The missing price is the routes.  We could go and configure a bunch of static routes throughout all the NSX routers and our physical routers, but that wouldn’t be fun.  It also wouldn’t be automated.  In this post I am going to walk through configuring the NSX routers to use OSPF for route distribution.


[Read More]

This article builds on my previous article Deploying an Edger Gateway.  In this article we are going to connect the Edge router we deployed in my previous post to the Logical Router we deployed in the post Deploying Logical Distributed Routers.  In order to link these together we will need to deploy a Logical Switch to be used as a transit network between the Edge Gateway and the Logical Router.


[Read More]

So far we have deployed (2) Logical Switches and (1) Distributed Logical Router and deployed a VM on to each logical switch.  Our VM’s can communicate with each other across the Distributed Logical Router, but they can’t communicate to anything else.  What we now need to do is deploy an Edge Gateway that we will configure to communicate upstream to the physical network and downstream to the logical network.  Where we could technically just connect the Distributed Logical Router upstream to your physical network, it’s not really a best practice approach and it’s not a supported approach when integrating with vCAC.


[Read More]

If you are familiar with “Network Scopes” from vCNS then “Transport Zones” should be familiar to you.  If not here is some useful information to know regarding these Zones.

Transport Zones dictate which clusters can participate in the use of a particular network.  Prior to creating your transport zones some thought should go into your network layout and what you want to be available to each cluster.  Below are some different scenarios for transport zones.

In the “MoaC” environment I have three clusters.  There is a Management Cluster in which all management servers are hosted included all components of NSX which will include all Logical and Edge routers that we have not yet configured, but this concept is important to know.  I will not be placing any routers in any other cluster than my management cluster.  I then have a Services cluster which will be hosting all of my provisioned machines that are not part of the core infrastructure, and finally I have a desktop cluster in which I will be hosting VDI desktop instances.


[Read More]

I know your excited to get right down to the meat of the installtion, but there is some housekeeping that we need to get out of the way first.  There are a number of pre-requisites that we need to ensure exist in the environment first.



  1. A properly configured vCenter Server with at least one cluster. (Ideally (2) clusters – (1) Management Cluster & 1(1) Cluster for everything else.)
  2. Cluster should have at least (2) hosts. (More would be better.  Memory will be important)
  3. You will need to be using Distributed Virtual Switches (DvSwitch) NOT Standard vSwitches.
  4. If you are NOT running vSphere 5.5 you will need to have your physical switches configured for Multicast. (Unicast requires vSphere 5.5)
  5. You will need a vLAN on your physical network that you can utilize for VXLAN.

To give you an idea below is the configuration for the “MoaC” lab that I will be working in.

MoaC Configuration

  • vCenter 5.5 U2b
  • (3) Clusters
    • Management Cluster with (2) vSphere  ESXi 5.5 U2 Hosts
      • 32GB Memory
      • Cluster only DvSwitch using NIC Teaming
    • Services Cluster with (4) vSphere ESXi 5.5 U2 Hosts
      • 196GB Memory
      • Cluster only DvSwitch using LAG.
    • Desktop Cluster with (2) vSphere ESXi 5.5 U2 Hosts
      • 112GB Memory
      • Cluster only DvSwitch using LAG.
  • Physical vLAN trunked to all vSphere hosts in all clusters.


[Read More]

I am tring to assing IP address to newlly clonned virtual machine with CLI

"Get-VMGuestNetworkInterface -VM w2k8 -HostUser administrator -HostPassword abc -GuestUser  root -GuestPassword  xyz"

But I am getting error as below:


Get-VMGuestNetworkInterface -VM w2k8
Get-VMGuestNetworkInterface : 2/27/2013 12:42:09 PM    Get-VMGuestNetworkInterface        Failed to authenticate with the
guest operating system using the supplied credentials.   
At line:1 char:1
+ Get-VMGuestNetworkInterface -VM w2k8
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-VMGuestNetworkInterface], ViError
    + FullyQualifiedErrorId : Client20_VmGuestServiceImpl_GetGuestAuthentication_ViError,VMware.VimAutomation.ViCore.Cmdlets.C


PowerCLI version 5.0

VCenter server version:5.0

ESX version:5.0

Add used credintials are correct.

Please suggest if i m missing something here.