Which are the basic CLI Commands to know by memory

Ola_CISCO

Hello,

I am currently studying for my CCNA cert, and I have recently started to use Packet Tracer, which is very good. I was wondering if anyone could suggest some basic CLI commands that I should know by memory when setting up practice networks in Packet Tracer.

Monkerz

All of them. I constantly have to dig down in my vault to pull out a command I need.

After using them for a while, they will come second nature to you.

Timber Wolf

Best way to learn is by just keep labbing. And every time you start a new lab clear devices and start from scratch every time. You will find that you just start to memorize commands you use in the lab.

networker050184

Just keep playing with it and the commands will stick. What commands are most important to know depends on what you are doing really. Show ip route isn't going to be very helpful when setting up a L2 switch, but very important if you are setting up a routed network.

Ola_CISCO

Thanks guys,

I'll keep practicing with the labs!

Moki99

Make sure you know all your show commands.

kal#4

sh ip route --- sh ip int brief----sh run

---

sh protocols

---

sh service-module s0/0/0 P

---

sh access-lists

fredmoogie

i'm gonna break up into 2 categories: routing & switching

a. routing commands

Router Commands List

b. switching

Cisco Switch Commands | Cisco Networking | Asked and Answered

note: some are overlap

Ola_CISCO

i'm gonna break up into 2 categories: routing & switching

a. routing commands

Router Commands List

b. switching

Cisco Switch Commands | Cisco Networking | Asked and Answered

note: some are overlap

Thanks for this "fredmoogie" -- this has given me more direction to help me to structure the commands!

Ola_CISCO

Thanks fredmoogie, this has been very helpful

SteveO86

They will stick in time. The key is not have every command memorized but knowing when/how to use to them

thedrama

You should know generally the ones which help you troubleshoot the device such as beginning with show.

sh cdp
sh cdp ne/ne de
sh ip int bri
sh ip route
sh interfaces
sh version
sh ip protocols
sh protocols
sh arp
sh run
ping
telnet

Trifidw

sh int status
sh run int fa0/0
sh arp
sh mac-
sh vlan

Excellent1

I'd also make it a point to toss in some debugs, as well:

debug ip ospf adj
debug eigrp packets
etc

Comes in handy when troubleshooting, especially if some show commands have been disabled in sims.

Agent6376

sh run int [interface] - Great for saving time combing through the sh run output to find the interface in question's config. (Trifidw beat me to this one)
sh run | s ip nat ---> Good for checking what translations you have configured, what list you used for nat, etc. Using the section or include commands with show run are good all around, not just with nat.
sh debug ---> You'd be amazed at how often people forget they're debugging something, and the router or switch runs at sub-par performance because of it.

Ola_CISCO

Thanks guys, these are very helpful indeed.

Webmaster

Incomplete and lots of overlap of basic commands, but maybe still useful. It was a list of supported commands for a sim I 'was' developing.

Swich Commands

Router Commands

alxx

don't forget
show controllers
show controller _ _ _ _ _

Useful as they can tell you if a cable is disconnected etc

alliasneo

I alwyas try to configure a lab from scratch each time I want to try something. I fire up packet tracer and get going. At CCENT/CCNA level I can generally get something together in 20mins or less depending on what I'm doing. This takes me through all of the basic commands in no time at all.

Conf t
int _____
ip address ___
no shut

switchport mode access
sh ip int brief

ip dhcp pool _____
network _____
default-router______

line vty 0 4
login
password


these are the main one's I use to get set up but I'm now going for my CCNA so I'm using a lot of switching commands like Sh Spanning-tree and sh vtp.

But yeah you just find you build up more and more as you build your network, you think 'oh I need to see if this is up or is this working'? and then you find the command just comes to you.

I remember when I was in Sem 1 of my CCNA course at college and the teach was showing us how to copy the commands in to notepad and then copy and paste them in to the router and I have NEVER used this because by typing the command each time it really sticks and this is why I constantly build a network from the ground up.

Ola_CISCO

Thanks for the tip alliasneo, what type of topology do you use, when you set up your networks?

alliasneo

it really depends on what I'm working on. Sometimes it's switches only but I make sure telnet all works ok and I rename the switches and give them passwords and then I start with the configuration. I'd say on every device I set up:

name
password
telnet vty lines
logging synchronous
no ip domain lookup
Service password encryption

If I'm just setting up some routers connected to pc i tend to use something like this:


and then add to it later or set it up again later on

Ola_CISCO

Nice one, allasneo, going to start working through this on packet tracer!

mgmguy1

alliasneo wrote: »

it really depends on what I'm working on. Sometimes it's switches only but I make sure telnet all works ok and I rename the switches and give them passwords and then I start with the configuration. I'd say on every device I set up:

name
password
telnet vty lines
logging synchronous
no ip domain lookup
Service password encryption

If I'm just setting up some routers connected to pc i tend to use something like this:


and then add to it later or set it up again later on

Very nice I am going to try this on packet tracer as well.

NCIT

Thanks Johan!