STUDENT PORTAL

LAB

ACCE

ACCE - Lab

Week One: Lab Work

Due: Aug 28, 2020 by 12:59am

Points: 25

This assignment is open until Aug 28, 2020 at 12:59am

Begin Lab:

Lab 1 – CLI & BASH

 

Lab Objectives:

 

In this activity you will:

  • Execute a number of commands on the CLI.

  • Diagnose CLI error messages

  • Navigate CLI

  • Interact with the BASH shell and navigate the Linux file structure.

 

TASK 1: Get Familiar with the running config.

 

Step 1

Execute the following CLI commands on your switch to familiarize yourself with the config.

 

  • show run

  • show lldp neighbors

  • show interfaces status connected

  • show ip route

 

Step 2

Feel free to run other various commands you may be familiar with from other platforms.

 

TASK 2: Edit the running config

 

Step 1

Enter configuration mode and move between different configuration modes

 

Spine1>en

Spine1#config

Spine1(config)#int e1

Spine1(config-if-Et1)#no switchport

Spine1(config-if-Et1)#ip address 10.0.0.1/24

Spine1(config-if-Et1)#int e3,4,5-6

Spine1(config-if-Et3-6)#exit

Spine1(config)#

 

Notice the prompt changes as you enter different configuration contexts.

 

While still configuring in config mode

 

Spine1(config)#show run interface e1

 

Notice that you can use the show command from within the config environment

 

End the config session

 

Spine1(config)# end

 

Compare the show run command with the show startup command. When prompted with the --More-- prompt hit the space bar for the next screen full of information. Specifically look at the configuration for interface E1 and notice the differences between the two configuration files.

 

The show run command shows the content of the configuration file in RAM, while the show startup command shows the content of the configuration file in NVRAM.

 

Now use the copy run start command to copy the running config file into NVRAM and then compare the two files. They should now be identical.

 

Step 2

Create a configuration session.

 

Create a configuration session called enable-telnet and verify that it is listed with the sh conf sessions command.

 

Spine1#conf session enable-telnet

Spine1(config-s-enable)#sh conf sessions

Maximum number of completed sessions: 1

Maximum number of pending sessions: 5

 

  Name             State         User     Terminal

  ------------- ------------- ----------- --------

* enable-telnet    pending       admin    vty9    

 

Make some changes to the configuration. Here is an example enabling telnet, however feel free to add other configuration too. When you are finished exit

 

NOTE: Please don’t make changes that could affect the lab, see lab 1 for Lab Rules

 

Spine1(config-s-enable)#management telnet

Spine1(config-s-enable-mgmt-telnet)#no shut

Spine1(config-s-enable-mgmt-telnet)#end

 

See if the changes you made are in the running config? If you made other changes make sure you check those too.

 

Spine1#sh run section telnet

Spine1#

 

View the pending session and abort your changes.

 

Spine1#sh conf sessions

Maximum number of completed sessions: 1

Maximum number of pending sessions: 5

 

  Name             State         User    Terminal

  ------------- ------------- ---------- --------

  enable-telnet    pending                       

 

Spine1#configure session enable-telnet abort

Spine1#sh configuration sessions

Maximum number of completed sessions: 1

Maximum number of pending sessions: 5

 

  Name    State       User    Terminal

  ---- ----------- ---------- --------

 

Step 3

Show the checkpoints created by the session.

 

NOTE: you may have different checkpoints, however you should have one with a time stamp that is matches your commited change.

 

Spine1#show configuration checkpoint

Maximum number of checkpoints: 20

Filename              Date                 User

--------------  --------------------  ---------------

ckp-20180731-0    2018-07-31 20:19:20 admin

ckp-20180731-0    2018-07-31 20:43:03 admin

ckp-20180731-0    2018-07-31 20:45:54 admin

ckp-20180731-0    2018-07-31 21:12:13 admin

 

Create a new checkpoint.

 

Spine1#config checkpoint save EOS-Lab

Spine1#

 

View the new checkpoint

 

Spine1#show configuration checkpoint

Maximum number of checkpoints: 20

Filename              Date                 User

--------------  --------------------  ---------------

EOS-Lab     2018-07-31 21:23:02 admin     

ckp-20180731-0    2018-07-31 20:19:20 admin

ckp-20180731-0    2018-07-31 20:43:03 admin

ckp-20180731-0    2018-07-31 20:45:54 admin

ckp-20180731-0    2018-07-31 21:12:13 admin

 

View the checkpoints with the dir command

 

Spine1#dir checkpoint:

Directory of checkpoint:/

 

       -rwx         453           Sep 24 12:25  EOS-Lab  

       -rwx         453           Sep 24 12:25  ckp-20180731-0

 

NOTE: Feel free to create checkpoints throughout the labs, however checkpoints created before the next lab will be deleted

 

Delete one of the created checkpoints

 

Spine1#delete checkpoint:EOS-Lab

Spine1#

Spine1#show configuration checkpoint

Maximum number of checkpoints: 20

Filename              Date                 User

--------------  --------------------  ---------------

EOS-Lab     2018-07-31 21:23:02 admin     

ckp-20180731-0    2018-07-31 20:43:03 admin

ckp-20180731-0    2018-07-31 20:45:54 admin

ckp-20180731-0    2018-07-31 21:12:13 admin

 

TASK 3: View the Cli files

 

Step 1 

Enter bash and view the python files for the Cli.

 

Spine1#bash

Arista Networks EOS shell

[admin@ Switch ~]$ cd /usr/lib/python2.7/site-packages/CliPlugin

 

List all the Cli files.

 

[admin@Switch CliPlugin]$ ls *Cli.py

AaaCli.py              FileCli.py                 McastBoundaryCli.py         

AclCli.py              FileSystemMountCli.py      McastCommonCli.py           

AgentPingCli.py        FruCli.py                  MirroringCli.py             

AgentResourceCli.py    FsfCli.py                  MlagConfigCli.py            

AleCountersCli.py      GatedBgpCli.py             MlagShowCli.py              

AleFibCli.py           GmpCli.py                  MlagVrrpCli.py              

AleHaloCli.py          HadoopTracerCli.py         MlagWarningCli.py           

 

Read some of the Cli files

 

[admin@ Switch CliPlugin]$cat VlanCli.py

 

TASK 4: Diagnose CLI error messages

EOS CLI will display different error messages to identify a problem with the command that was entered. You will type different commands and observe the error that you will receive.

 

Step 1

Type this command at the prompt.

 

Switch>c

 

Questions:

  1. What is the error that you received?

 

  1. What does this error mean?

 

 

 

Step 2

Spine1#clock set

 

Questions:

  1. What is the error that you received?

 

  1. What does this error mean?

 

 

 

Step 3      

Spine1#clock set 10:05:00

 

Questions:

  1. What is the error that you received?

 

  1. What does this error mean?

 

 

 

 

TASK 5: Verify command history

 

Step 1

Enter a sequence of commands. The objective is to create a history.

 

  • show clock

  • show ip interface

  • show running-config

  • show startup-config

  • show hostname

 

Step 2

Now use the Up Arrow and Down Arrow to view the history buffer.

 

TASK 6: Filtering parameters

 

Different words such as “begin”, “include” , “section” and “exclude” used along with the pipe “|”  command can be used to view sections of the running configuration. This is very helpful when the administrator is only interested in viewing certain parts of the configuration.

 

Step 1

Type the following command and observe the ouput.

 

Spine1#show running-configuration | begin interface

 

Step 2

Type the following command and observe the ouput.

 

Spine1#show running-configuration | include interface

 

TASK 7: Enter BASH and get familiar with the file structure.

 

Step 1

Enter bash on your switch.

 

  • Type bash

 

End of lab

Status: Not Submitted

Instructor Comments:

John, your work has been great so far.  Please get this submitted on time or your grades will suffer.

logo_arista_blue.png
BlueWhite_150x150.png