26.1.3 Lab – Configure Protections for Passwords and Terminal Lines Answers

• Recommend

Lab -Configure Protections for Passwords and Terminal Lines (Answers Version)

Answers Note: Red font color or gray highlights indicate text that appears in the instructor copy only.

Topology

Addressing Table

Objectives

Part 1: Build the Network and Configure Basic Device Settings

Part 2: Explore Password Protection Options

Part 3: Configure and Verify Terminal Line Protection Options

Background / Scenario

Securing your network devices starts at the most basic level — physical security. Physical security establishes restricted physical access to the devices. Most of the time you will connect to devices from a remote location. This makes securing remote access extremely important. In this lab, you will explore several different methods of protecting both local and remote access to your devices.

Note: This lab is an exercise in configuring options available for passwords and remote access protection and does not necessarily reflect network troubleshooting best practices.

Note: The routers used with CCNP hands-on labs are Cisco 4221 with Cisco IOS XE Release 16.9.4 (universalk9 image). The switches used in the labs are Cisco Catalyst 3650s with Cisco IOS XE Release 16.9.4 (universalk9 image) and Cisco Catalyst 2960s with Cisco IOS Release 15.2(2) (lanbasek9 image). Other routers, switches, and Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the commands available and the output produced might vary from what is shown in the labs. Refer to the Router Interface Summary Table at the end of the lab for the correct interface identifiers.

Note: Make sure that the switches have been erased and have no startup configurations. If you are unsure, contact your instructor.

Answers Note: Refer to the Answers Lab Manual for the procedures to initialize and reload devices.

Required Resources

• 1 Router (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or comparable)
• 1 Switch (Cisco 3650 with Cisco IOS XE Release 16.9.4 universal image or comparable)
• 1 Switch (Cisco 2960 with Cisco IOS Release 15.2(2) lanbasek9 image or comparable)
• 2 PCs (Operating system of choice with terminal emulation program installed)
• Console cables to configure the Cisco IOS devices via the console ports
• Ethernet cables as shown in the topology

Part 1:Build the Network and Configure Basic Device Settings

In Part 1, you will set up the network topology and configure basic settings and interface addressing on routers.

Step 1:Cable the network as shown in the topology.

Attach the devices as shown in the topology diagram, and cable as necessary.

Step 2:Configure basic settings for each device.

1. Console into each device, enter global configuration mode, and apply the basic settings. The startup configurations for each device are provided below.

Router R1

hostname R1

no ip domain lookup

banner motd # R1, Password and Terminal Protection #

line con 0

exec-timeout 0 0

logging synchronous

exit

interface g0/0/1

ip address 192.168.1.1 255.255.255.0

no shutdown

exit

ip dhcp excluded-address 192.168.1.1 192.168.1.5

ip dhcp pool HOST_ADDRESSING

network 192.168.1.0 255.255.255.0

default-router 192.168.1.1

exit

end

Switch D1

hostname D1

no ip domain lookup

banner motd # D1, Password and Terminal Protection #

line con 0

exec-timeout 0 0

logging synchronous

exit

interface vlan 1

ip address 192.168.1.2 255.255.255.0

no shutdown

exit

ip default-gateway 192.168.1.1

interface g1/0/23

spanning-tree portfast

switchport mode access

no shutdown

exit

interface g1/0/11

spanning-tree portfast

switchport mode access

no shutdown

exit

interface range g1/0/5-6

switchport mode trunk

channel-group 1 mode active

no shutdown

exit

interface range g1/0/1-4, g1/0/7-10, g1/0/12-22, g1/0/24, g1/1/1-4

shutdown

exit

end

Switch A1

hostname A1

no ip domain lookup

banner motd # A1, Password and Terminal Protection #

line con 0

exec-timeout 0 0

logging synchronous

exit

interface vlan 1

ip address 192.168.1.3 255.255.255.0

no shutdown

exit

ip default-gateway 192.168.1.1

interface range f0/1-2

switchport mode trunk

channel-group 1 mode active

no shutdown

exit

interface range f0/3-24, g0/1-2

shutdown

exit

interface f0/23

switchport mode access

spanning-tree portfast

no shutdown

exit

end

2. Set the clock on each device to UTC time.
3. Save the running configuration to startup-config.
4. Verify that PC 2 receives an IP address via DHCP.
5. Verify that D1, A1, PC 1 and PC 2 can ping R1 interface G0/0/1.

Part 2:Explore Password Protection Options

Cisco device configuration files are simply text files. They are commonly backed up onto various media and stored in different, hopefully secure, places. Contained in the configuration, whether stored as a file or displayed on screen, are the various passwords used to access the device. An unauthorized individual having access to these files or output could use the information to gain access to the devices.

Note: There are many instances where passwords are used to protect protocol operations, but those are beyond the scope of this lab. This lab is focused on CLI access to the network device.

Step 1:Examine the password command.

1. The password command or parameter is used in several different ways. The most basic of these is configuring a password for the console line.

R1(config)# line con 0

R1(config-line)# password ?

0Specifies an UNENCRYPTED password will follow

7Specifies a HIDDEN password will follow

LINEThe UNENCRYPTED (cleartext) line password

2. The options presented at this point might be confusing. The default is 0, which is to say “the string that follows is unencrypted”. You are not even required to use the zero; you just supply the password string in its unencrypted form. The 7 option is used when you are configuring an already-obfuscated password. In this example, we will use the plaintext string cisco123.

R1(config-line)# password cisco123

3. Now that the password is entered, add the login command, which configures the device to allow someone to log in if they supply the configured password. Without the login command, the password does not function.

R1(config-line)# login

4. Test the login requirement by exiting from the console and then logout of the router. Then attempt to reconnect to the router. You should be prompted for a password and denied if the password you supply is incorrect.

R1(config-line)# end

R1# logout

R1 con0 is now available

Press RETURN to get started.

R1, Protect Passwords and Terminal Lines

User Access Verification

Password: <entered incorrect password and pressed return>

Password: <entered correct password, cisco123>

R1>

5. The problem with the password command is that the password string is stored in plaintext. Go into privileged EXEC mode and issue the command show run | section line con and examine the output. As you can see, the password string is available for all to see in plaintext. Excluding using the secret keyword, this default behavior applies to any system or user password command.

R1> enable

R1# show run | section line con

line con 0

exec-timeout 0 0

password cisco123

logging synchronous

login

transport input none

stopbits 1

Step 2:Secure passwords with type 7 encryption.

1. Type 7 encryption is a very weak encryption that is easily reversible. When configured, type 7 encryption is applied to all plaintext passwords, including system and user passwords that include the password command.Enable type 7 encryption for all plaintext passwords as shown.

R1# configure terminal

R1(config)# service password-encryption

R1(config)# exit

2. When the service password-encryption is enabled, all plaintext entries are a bit more complex.

R1# show run | include password

service password-encryption

password 7 060506324F41584B56

However, do not let the apparent complexity mislead you. A string encrypted to type 7 is not considered secure. Search the internet for “Cisco Type 7 Password Cracker” and you will find many sites and even mobile apps that will reverse the encryption. Try one and you will see that the type 7 string is quickly and easily changed to plaintext.

Type 7 encryption is the most protection the local device can provide to a terminal line. To provide any more security, you must use a local login database, covered next, or use Authentication, Authorization and Accounting (AAA), which is covered in another lab.

Step 3:Secure passwords with type 5 encryption.

Type 5 encryption uses a 128-bit MD5 hash to secure the password. The device creates a hash out of the configuration entry, and then subsequent login attempts subject the supplied password string to the same hashing algorithm. If the hashes match, then the password string entered was the same as that stored on the device. Use the secret parameter to create a type 5 password. You should be familiar with the secret parameter from creating an enable secret password. In this case, our goal is to secure logins to the device, so we use the secret parameter as a part of the username command.

1. On all your devices, configure a local user named admin with the password string cisco123 using type 5 encryption.

R1(config)# username admin secret cisco123

2. Examine the output of show run | include username and you will see that the string is marked as a type 5 and looks very different from the type 7 passwords you saw earlier.

R1# show run | include username

username admin secret 5 $1$Ft4s$VepVuV73QfKNBlR4wMXff1

3. To use this enhanced password, issue the command login local in the console line configuration. This instructs the device to prompt for a username and password and compare the responses to the local database.

R1(config)# line con 0

R1(config-line)# login local

R1(config-line)# end

4. Now completely disconnect and attempt to log in again, you will see that you are now prompted for a username followed by a password.

R1, Protect Passwords and Terminal Lines

User Access Verification

Username: admin

Password: <enter correct password, cisco123>

R1>

Do not let the apparent complexity of a type 5 password mislead you. A string encrypted to type 5 is not considered secure. Search the internet for “Cisco Type 5 Password Cracker” and you will find many sites that will reverse the encryption. Try one and you will see that the type 5 string is quickly and easily changed to plaintext.

Step 4:Secure passwords with type 9 encryption.

With type 7 and type 5 passwords being so easy to circumvent, Cisco added support for type 8 and type 9 passwords. Type 8 passwords use Password-Based Key Derivation Function 2 (PBKDF2) with sha256 as the hashing function, while type 9 uses the SCRYPT hashing function, which also uses sha256, but in a different manner. Both types are considered uncrackable. SCRYPT is more computationally intense.

To use a type 9 password, add the algorithm-type parameter to your command before the secret parameter.

1. Create a privileged EXEC password using a type 9 password. Set the password string as cisco123.

R1(config)# enable algorithm-type scrypt secret cisco123

2. Reconfigure the admin account you configured earlier to use a type 9 password. Use the same password string, cisco123.

R1(config)# username admin algorithm-type scrypt secret cisco123

3. To see the results of these entries, issue the command show run | include secret 9. As you can see, the output strings are much longer than type 7 or type 5.

R1# show run | include secret 9

enable secret 9 $9$o.TVpUa5sYEeTU$WAA3GDD6u7GAK19Wcnh5hH325RLlG2H5EHA2ALY.GqU

username admin secret 9 $9$r5fycGQrMSV.7k$W49OJ3RnrybJjPLLpgKpqwaSja52GiKMYEQCdhwyxsg

Part 3:Configure and Verify Terminal Line Protection Options

Now that the passwords are secure, consider the protocols used to remotely access the management plane. The default remote access protocols are Telnet, which is unsecure, and Secure Shell (SSH). SSH is a protocol which provides a secure remote access connection to network devices. Communication between the client and server is encrypted in both SSH version 1 and 2. However, implement SSH version 2 when possible because it uses a more enhanced security encryption algorithm.

Step 1:Configure SSH support.

1. SSH uses crypto keys. Devices running IOS XE will generate self-signed certificates at startup. These certificates will not match our implementation, and so they need to be removed.

Note: Do not do this in a production environment without a clear understanding of the crypto systems being used. It may result in a device being unreachable and inaccessible.

Use the crypto key zeroize global configuration command to clear all existing keys.

R1(config)# crypto key zeroize

% All keys will be removed.

% All router certs issued using these keys will also be removed.

Do you really want to remove these keys? [yes/no]: yes

R1(config)#

*Feb 11 16:24:57.826: %CRYPTO_ENGINE-5-KEY_DELETED: A key namedhas been removed from key storage

*Feb 11 16:24:57.826: %CRYPTO_ENGINE-5-KEY_DELETED: A key namedhas been removed from key storage

*Feb 11 16:24:57.827: %SSH-5-DISABLED: SSH 1.99 has been disabled

2. To configure SSH on a Cisco device, at a minimum, you will need to configure a hostname, domain name, correct time, and a username database for authentication. In this lab, you have already configured a hostname, set the clock, and configured a user, admin. To complete the basic SSH configuration, you will configure a domain name for all the devices. Use theip domain name command to set the domain name to CCNP.EIGHT. The IOS syntax has been updated from theip domain-name to ip domain name command.

Note: The domain name used here is obviously made up. If your devices must be integrated into your organization’s DNS infrastructure, then you must use your organization’s domain name.

R1(config)# ip domain name CCNP.EIGHT

3. After meeting the prerequisites, generate a crypto key. Keys can be of varying sizes, but 2048 bits is considered a safe size. The command to do this will vary slightly between different devices and operating systems.

R1(config)# crypto key generate rsa modulus 2048

The name for the keys will be: R1.CCNP.EIGHT

% The key modulus size is 2048 bits

% Generating 2048 bit RSA keys, keys will be non-exportable…

[OK] (elapsed time was 2 seconds)

R1(config)#

*Feb 11 16:27:28.354: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named R1.CCNP.EIGHT has been generated or imported by crypto-engine

*Feb 11 16:27:28.355: %SSH-5-ENABLED: SSH 1.99 has been enabled

*Feb 11 16:27:28.543: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named R1.CCNP.EIGHT.server has been generated or imported by crypto-engine

4. The console output shows that SSH 1.99 has been enabled, which means that the device supports connections using both SSH version 1 and SSH version 2. SSH version 1 has some flaws in implementation, so it should be avoided. To restrict the device support to just SSH version 2, issue the command ip ssh version 2.

R1(config)# ip ssh version 2

5. You should also restrict the period of time the authentication process is allowed to take and how many authentication attempts a user is given using the ip ssh time–out and ip ssh authentication-retries commands. The timeout value governs how long the device will wait for the authentication process (username and password) to complete. The default is 120 seconds. Restricting this time helps to ensure availability. Set it to 60 seconds or less. The authentication retry value, which defaults to 3, dictates how many attempts a user gets to put the correct password in before they are disconnected. Setting it to 2 is a common practice.

R1(config)# ip ssh time-out 30

R1(config)# ip ssh authentication-retries 2

6. Now configure the vty lines to access incoming SSH connections with the transport input ssh command. This command disables all support for Telnet on the vty lines.

R1(config)# line vty 0 4

R1(config-line)# transport input ssh

7. Lastly, configure the vty lines to query the local user database using the command login local.

R1(config-line)# login local

Test your SSH configuration by attempting to SSH from PC 1 and PC 2 to R1. Both attempts should be successful. Issue the show ssh command to view both established SSH sessions to R1.

R1# show ssh

Connection Version ModeEncryptionHmacStateUsername

02.0INaes256-ctrhmac-sha2-256 Session startedadmin

02.0OUTaes256-ctrhmac-sha2-256 Session startedadmin

12.0INaes256-ctrhmac-sha2-256 Session startedadmin

12.0OUTaes256-ctrhmac-sha2-256 Session startedadmin

Step 2:Add Timers to the vty lines.

With the default configuration, after a user is connected, the system will not disconnect the session until there has been 10 minutes without activity. This is an old default setting that needs to be changed to help keep your system secure.

1. Change the default inactivity timer to a shorter period using the exec-timeout [minutes] {seconds} command. Different organizations have different requirements for this value. For our purposes, set the exec-timeout on the vty lines to 3 minutes.

R1(config)# line vty 0 4

R1(config-line)# exec-timeout 3 0

2. On certain devices (the router only in our case) you can give the connected user a warning that they are about to be disconnected using the logout-warning [seconds] command. Configure a logout warning for 1 minute.

R1(config-line)# logout-warning 60

3. On certain devices (the router only in our case), you have the option to use an absolute timeout, which disconnects the user no matter if they are active or not. For our purposes, configure this value to be 15 minutes using the absolute-timeout [minutes] command.

R1(config-line)# absolute-timeout 15

4. Test these tweaks to your SSH configuration by attempting to SSH from PC 2 to one of the devices and delay your password response to see what happens. Try again and put in the wrong password until it disconnects you. Log in one more time and let the terminal line remain inactive until you get disconnected.

Step 3:Restrict Access to the vty lines at Layer 3.

Up to this point you have configured and secured access to the terminal lines by creating encrypted passwords, eliminating Telnet in favor of SSH version 2, and tuned SSH timers to help keep things secure. But none of this controls who can attempt to connect to your devices. To do this, configure and apply an access list.

1. Create a standard access list, either numbered or named, that permits only the host at 192.168.1.50 to access the vty lines.

R1(config)# ip access-list standard VTY-CONTROL

R1(config-std-nacl)# permit host 192.168.1.50

R1(config-std-nacl)# deny any log

R1(config-std-nacl)# exit

R1(config)#

2. Apply the access list to the vty lines using the access-class [name | number] in command.

R1(config)# line vty 0 4

R1(config-line)# access-class VTY-CONTROL in

R1(config-line)# exit

3. Test your ACL by attempting to connect to R1 from PC 2. The connection attempt should fail, while connection attempts from PC 1 should succeed.
4. As a challenge, configure D1 and A1 with secure passwords and SSH support for the terminal lines with restricted access.

Reflection Questions

1. What additional security can be configured on a Cisco device when implementing SSH?

Type your answers here.

Specify only SSH version 2, setting or adjusting timeout features and implementing an ACL

2. How can you implement type 9 passwords using scrypt and avoid using the console and vty line passwords with type 7 encryption?

Type your answers here.

Create a local username and specify the algorithm-type scrypt secret <password> and then apply the login local command on the console and vty lines answer,

Router Interface Summary Table

Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many interfaces the router has. There is no way to effectively list all the combinations of configurations for each router class. This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device. The table does not include any other type of interface, even though a specific router may contain one. An example of this might be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be used in Cisco IOS commands to represent the interface.

End of document

Device Configs

Router R1

R1# show run

Building configuration…

Current configuration : 2154 bytes

!

version 16.9

service timestamps debug datetime msec

service timestamps log datetime msec

service password-encryption

platform qfp utilization monitor load 80

no platform punt-keepalive disable-kernel-core

!

hostname R1

!

boot-start-marker

boot-end-marker

!

enable secret 9 $9$o.TVpUa5sYEeTU$WAA3GDD6u7GAK19Wcnh5hH325RLlG2H5EHA2ALY.GqU

!

no aaa new-model

!

no ip domain lookup

ip domain name CCNP.EIGHT

ip dhcp excluded-address 192.168.1.1 192.168.1.5

!

ip dhcp pool webuidhcp

!

ip dhcp pool HOST_ADDRESSING

network 192.168.1.0 255.255.255.0

default-router 192.168.1.1

!

login on-success log

!

subscriber templating

!

multilink bundle-name authenticated

!

spanning-tree extend system-id

!

username admin secret 9 $9$r5fycGQrMSV.7k$W49OJ3RnrybJjPLLpgKpqwaSja52GiKMYEQCdhwyxsg

!

redundancy

mode none

!

interface GigabitEthernet0/0/0

no ip address

negotiation auto

!

interface GigabitEthernet0/0/1

ip address 192.168.1.1 255.255.255.0

negotiation auto

!

interface Serial0/1/0

no ip address

shutdown

!

interface Serial0/1/1

no ip address

shutdown

!

ip forward-protocol nd

no ip http server

ip http secure-server

!

ip ssh time-out 30

ip ssh authentication-retries 2

ip ssh version 2

!

ip access-list standard VTY-CONTROL

permit 192.168.1.50

denyany log

!

control-plane

!

banner motd ^C R1, Protect Passwords and Terminal Lines ^C

!

line con 0

exec-timeout 0 0

password 7 060506324F41584B56

logging synchronous

login local

transport input none

stopbits 1

line aux 0

stopbits 1

line vty 0 4

access-class VTY-CONTROL in

exec-timeout 3 0

logout-warning 60

absolute-timeout 15

login local

transport input ssh

!

end

Switch D1

D1# show run

Building configuration…

Current configuration : 4780 bytes

!

version 16.9

no service pad

service timestamps debug datetime msec

service timestamps log datetime msec

service password-encryption

no platform punt-keepalive disable-kernel-core

!

hostname D1

!

vrf definition Mgmt-vrf

!

address-family ipv4

exit-address-family

!

address-family ipv6

exit-address-family

!

enable secret 9 $9$v5KPK.XpGk.aCU$TtzrlKCXOdn89AgfNuk7v217.V8JF/gH97IaHzeXTBM

!

no aaa new-model

switch 1 provision ws-c3650-24ps

!

no ip domain lookup

ip domain name CCNP.EIGHT

!

login on-success log

!

license boot level ipservicesk9

!

diagnostic bootup level minimal

!

spanning-tree mode rapid-pvst

spanning-tree extend system-id

!

username admin secret 9 $9$qI/1sX6pTYz7bU$zVzBAGqfGJMZourfs0o8Pbl1FvBvGHN2M.Znlcp.//E

!

redundancy

mode sso

!

transceiver type all

monitoring

!

!

class-map match-any system-cpp-police-topology-control

description Topology control

class-map match-any system-cpp-police-sw-forward

description Sw forwarding, L2 LVX data, LOGGING

class-map match-any system-cpp-default

description Inter FED, EWLC control, EWLC data

class-map match-any system-cpp-police-sys-data

description Learning cache ovfl, High Rate App, Exception, EGR Exception, NFLSAMPLED DATA, RPF Failed

class-map match-any system-cpp-police-punt-webauth

description Punt Webauth

class-map match-any system-cpp-police-l2lvx-control

description L2 LVX control packets

class-map match-any system-cpp-police-forus

description Forus Address resolution and Forus traffic

class-map match-any system-cpp-police-multicast-end-station

description MCAST END STATION

class-map match-any system-cpp-police-multicast

description Transit Traffic and MCAST Data

class-map match-any system-cpp-police-l2-control

description L2 control

class-map match-any system-cpp-police-dot1x-auth

description DOT1X Auth

class-map match-any system-cpp-police-data

description ICMP redirect, ICMP_GEN and BROADCAST

class-map match-any system-cpp-police-stackwise–virt-control

description Stackwise Virtual

class-map match-any non-client-nrt-class

class-map match-any system-cpp-police-routing-control

description Routing control and Low Latency

class-map match-any system-cpp-police-protocol-snooping

description Protocol snooping

class-map match-any system-cpp-police-dhcp-snooping

description DHCP snooping

class-map match-any system-cpp-police-system-critical

description System Critical and Gold Pkt

!

policy-map system-cpp-policy

!

interface Port-channel1

switchport mode trunk

!

interface GigabitEthernet0/0

vrf forwarding Mgmt-vrf

no ip address

negotiation auto

!

interface GigabitEthernet1/0/1

shutdown

!

interface GigabitEthernet1/0/2

shutdown

!

interface GigabitEthernet1/0/3

shutdown

!

interface GigabitEthernet1/0/4

shutdown

!

interface GigabitEthernet1/0/5

switchport mode trunk

channel-group 1 mode active

!

interface GigabitEthernet1/0/6

switchport mode trunk

channel-group 1 mode active

!

interface GigabitEthernet1/0/7

shutdown

!

interface GigabitEthernet1/0/8

shutdown

!

interface GigabitEthernet1/0/9

shutdown

!

interface GigabitEthernet1/0/10

shutdown

!

interface GigabitEthernet1/0/11

switchport mode access

spanning-tree portfast

!

interface GigabitEthernet1/0/12

shutdown

!

interface GigabitEthernet1/0/13

shutdown

!

interface GigabitEthernet1/0/14

shutdown

!

interface GigabitEthernet1/0/15

shutdown

!

interface GigabitEthernet1/0/16

shutdown

!

interface GigabitEthernet1/0/17

shutdown

!

interface GigabitEthernet1/0/18

shutdown

!

interface GigabitEthernet1/0/19

shutdown

!

interface GigabitEthernet1/0/20

shutdown

!

interface GigabitEthernet1/0/21

shutdown

!

interface GigabitEthernet1/0/22

shutdown

!

interface GigabitEthernet1/0/23

switchport mode access

spanning-tree portfast

!

interface GigabitEthernet1/0/24

shutdown

!

interface GigabitEthernet1/1/1

shutdown

!

interface GigabitEthernet1/1/2

shutdown

!

interface GigabitEthernet1/1/3

shutdown

!

interface GigabitEthernet1/1/4

shutdown

!

interface Vlan1

ip address 192.168.1.2 255.255.255.0

!

ip default-gateway 192.168.1.1

ip forward-protocol nd

ip http server

ip http secure-server

ip ssh time-out 30

ip ssh authentication-retries 2

ip ssh version 2

!

!

ip access-list standard VTY-CONTROL

permit 192.168.1.50

denyany log

!

!

control-plane

service-policy input system-cpp-policy

!

banner motd ^C D1, Protect Passwords and Terminal Lines ^C

!

line con 0

exec-timeout 0 0

password 7 00071A1507545A545C

logging synchronous

login local

stopbits 1

line aux 0

stopbits 1

line vty 0 4

access-class VTY-CONTROL in

exec-timeout 3 0

login local

transport input ssh

line vty 5 15

login

!

end

Switch A1

A1# show run

Building configuration…

Current configuration : 2375 bytes

!

version 15.2

no service pad

service timestamps debug datetime msec

service timestamps log datetime msec

service password-encryption

!

hostname A1

!

boot-start-marker

boot-end-marker

!

enable secret 9 $9$8MhlI2gmExj3cH$RqXK4fuaeOk5zK.4ua9IMAW3I0CGCpA.iIewKW29ZFs

!

username admin secret 9 $9$l8ilZ7.QkFeEbq$2o.wMWKR7/y2jHthzI8z0I6.CAoxHces5ovRCkBzrqs

no aaa new-model

system mtu routing 1500

!

no ip domain-lookup

ip domain-name CCNP.EIGHT

!

spanning-tree mode rapid-pvst

spanning-tree extend system-id

!

vlan internal allocation policy ascending

!

interface Port-channel1

switchport mode trunk

!

interface FastEthernet0/1

switchport mode trunk

channel-group 1 mode active

!

interface FastEthernet0/2

switchport mode trunk

channel-group 1 mode active

!

interface FastEthernet0/3

shutdown

!

interface FastEthernet0/4

shutdown

!

interface FastEthernet0/5

shutdown

!

interface FastEthernet0/6

shutdown

!

interface FastEthernet0/7

shutdown

!

interface FastEthernet0/8

shutdown

!

interface FastEthernet0/9

shutdown

!

interface FastEthernet0/10

shutdown

!

interface FastEthernet0/11

shutdown

!

interface FastEthernet0/12

shutdown

!

interface FastEthernet0/13

shutdown

!

interface FastEthernet0/14

shutdown

!

interface FastEthernet0/15

shutdown

!

interface FastEthernet0/16

shutdown

!

interface FastEthernet0/17

shutdown

!

interface FastEthernet0/18

shutdown

!

interface FastEthernet0/19

shutdown

!

interface FastEthernet0/20

shutdown

!

interface FastEthernet0/21

shutdown

!

interface FastEthernet0/22

shutdown

!

interface FastEthernet0/23

switchport mode access

spanning-tree portfast edge

!

interface FastEthernet0/24

shutdown

!

interface GigabitEthernet0/1

shutdown

!

interface GigabitEthernet0/2

shutdown

!

interface Vlan1

ip address 192.168.1.3 255.255.255.0

!

ip default-gateway 192.168.1.1

ip http server

ip http secure-server

ip ssh time-out 30

ip ssh authentication-retries 2

ip ssh version 2

!

ip access-list standard VTY-CONTROL

permit 192.168.1.50

denyany log

!

banner motd ^C A1, Protect Passwords and Terminal Lines ^C

!

line con 0

exec-timeout 0 0

password 7 030752180500701E1D

logging synchronous

login local

line vty 0 4

access-class VTY-CONTROL in

exec-timeout 3 0

login local

transport input ssh

line vty 5 15

login

!

end

• Recommend