Skip to main content

How to Connect Cisco Switches/Routers with Cisco Network Assistant

This post is about how to configure a Cisco standalone Device so that it may be connected with Cisco Network Assistant (CNA) Successfully.
In production Networks, Cisco devices are often configured with basic required configuration for successful connection of CNA with the Cisco Devices and most of the time you do not need to configure them specially for CNA Connection.So for successful connectivity between a Cisco Device and a PC with CNA Installed is two part process.First of all we focus on how to configure a Cisco Switch then we will install CNA on a PC and Connect it with the switch.
Configure a Switch with ip http server command in Global Configuration mode
Switch(config)#ip http server
Define a Vlan and SVI, assign an IP Address from a Private IP Address Range so that it can be connected with CNA. Here I am configuring VLAN 100, with SVI 100 and IP Address Subnet as 172.16.100.0/24
Switch>en
Switch#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)#vlan 100
Switch(config-vlan)#exit
Switch(config)#interface vlan 100


%LINK-5-CHANGED: Interface Vlan100, changed state to up
Switch(config-if)#ip add 172.16.100.1 255.255.255.0
This was all the configs on a Switch/router, now download Cisco CNA from here and install on your PC.
Connect an Ethernet Cross Over Cable with your PC’s Network Interface card and the other end with any of the Switch’s Fast Ethernet port.
Set the IP Address of PC’s NIC as shown in the snap below
Launch CNA by double clicking its icon on your PC’s Desktop
Click on Connect Icon, Enter the IP Address of the Switch, that we just have configured (172.16.100.1).
Click OK and You are connected to the Switch.

Comments

Popular posts from this blog

What is Cisco Supervisor Engine?

Supervisor Engine is a module that is installed in the Cisco Chassis-based Catalyst Switches or Routers. Supervisor engine contains nearly all the same components of a fixed Cisco Switches or Routers. These Supervisor engines come in a variety of different types with different functionalities and are installed in the Switches/Router Chassis as per requirements of the network types.

Benefits of Supervisor Engines
By installing Latest Supervisor Engines in your existing investments (Switches and Routers) you can scale system performance and integrate next-generation services into your Networks.
Within a single multilayer switch chassis, two supervisor modules with integrated route processors can be used to provide hardware redundancy. If an entire supervisor module fails, the other module can pick up the pieces and continue operating the switch.
The supervisor engine contains the following integrated daughter cards that perform forwarding and routing and provide the protocols supported …

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.