Lab Objective:
The focus of this lab is to understand basic SNMP, logging and switch management implementation and configuration in Cisco IOS Catalyst switches.
Lab Topology:
The lab network topology is illustrated below:
|
IMPORTANT NOTE If you are using the www.howtonetwork.net racks, please begin each and every lab by shutting down all interfaces on all switches and then manually re-enabling only the interfaces that are illustrated in this topology. |
Task 1
Configure VTP as following on the switches illustrated in the topology:
- Switches DLS1 and DLS2 should be VTP servers
- Switches ALS1 and ALS2 should be VTP clients
- The switches should reside in VTP domain ‘CCNP’
- The VTP domain should be secured using the password ‘CCNP’
- All switches should run VTP version 2
Task 2
Configure trunking on all switches and allow DTP to negotiate the trunking protocol. Assign the FastEthernet0/1 interface on switch ALS1 to VLAN 100.
Task 3
Configure switch DLS1 as the root bridge for VLAN 100, with switch DLS2 as the secondary (backup) root bridge. Next, configure the following SVIs and interfaces on the switches:
- DLS1: Interface VLAN 100: IP address 100.1.1.1/24
- DLS2: Interface VLAN 100: IP address 100.1.1.2/24
- ALS1: Interface VLAN 100: IP address 100.1.1.3/24
- ALS2: Interface VLAN 100: IP address 100.1.1.4/24
Finally, configure R1s FastEthernet 0/0 interface with the IP address 100.1.1.254.
Task 4
Configure SNMP on switches ALS1 and ALS2 as follows:
- Community string LEVEL1 should provide read only access from 192.168.1.0/24
- Community string LEVEL2 should provide read write access from 192.168.2.0/24
- SNMP traps for VTP should be sent to 10.1.1.253 using community LEVEL1
- SNMP traps for STP should be sent to 10.1.1.254 using community LEVEL2
Task 5
Configure logging on switches DLS1 and DLS2 as follows:
- Informational log messages should be sent to hosts 10.1.1.253 and 10.1.1.254
- Debugging log messages should be stored in the local buffer
- Log messages should include the date, time, millisecond values and local time zone
- Log messages should include a sequence number
- The local switch buffer size should be restricted to 10, 000
Task 6
For effective time management, configure Network Time Protocol as follows:
- Router RI should be configured as the NTP server
- All switches should synchronize their time with router R1
- All network devices should reside in the EST (GMT -5) time zone
- All network devices should adjust time for daylight saving
Task 7
For effective configuration management, configure the Cisco IOS Command Scheduler to automatically save the configurations on switches DLS1 and DLS2 every 8 hours.
Lab Validation
Task 1
| DLS1(config)#vtp mode server DLS1(config)#vtp domain CCNP DLS1(config)#vtp password CCNP DLS1(config)#vtp version 2 |
| DLS2(config)#vtp mode server DLS2(config)#vtp domain CCNP DLS2(config)#vtp password CCNP DLS2(config)#vtp version 2 |
| ALS1(config)#vtp version 2 ALS1(config)#vtp mode client ALS1(config)#vtp domain CCNP ALS1(config)#vtp password CCNP |
| ALS2(config)#vtp version 2 ALS2(config)#vtp mode client ALS2(config)#vtp domain CCNP ALS2(config)#vtp password CCNP |
NOTE: It is important to change the VTP version prior to configuring a switch as a VTP client. When the switch is in client mode, you cannot change the VTP version as shown below:
| ALS2(config)#vtp version 2 Cannot modify version in VTP client mode |
Task 2
| DLS1(config)#interface range fasteth 0/7, fasteth 0/9, fasteth 0/11 DLS1(config-if-range)#switchport DLS1(config-if-range)#no shutdown DLS2(config-if-range)#exit |
| DLS2(config)#interface range fasteth 0/7, fasteth 0/9, fasteth 0/11 DLS2(config-if-range)#switchport DLS2(config-if-range)#no shutdown DLS2(config-if-range)#exit |
| ALS1(config)#interface range fastethernet 0/7 , fastethernet 0/9 ALS1(config-if-range)#no shutdown ALS1(config)#interface fastethernet 0/1 ALS1(config-if)#switchport mode access ALS1(config-if)#switchport access vlan 100 ALS1(config-if)#no shutdown |
| ALS2(config)#interface range fastethernet 0/7 , fastethernet 0/9 ALS2(config-if-range)#no shutdown |
Following this, verify your configuration using the show interfaces trunk command:
| DLS1#show interfaces trunk
Port Mode Encapsulation Status Native vlan |
| ALS1#show interfaces trunk
Port Mode Encapsulation Status Native vlan |
Task 3
To complete this task, you first need to configure VLAN 100 on the VTP server devices prior to configuring the VLAN interfaces (SVIs) on the switches. This task is completed as follows:
| DLS1(config)#vlan 100 DLS1(config-vlan)#exit DLS1(config)#spanning-tree vlan 100 priority 4096 DLS1(config)#interface vlan 100 DLS1(config-if)#ip address 100.1.1.1 255.255.255.0 DLS1(config-if)#exit |
| DLS2(config)#vlan 100 DLS2(config-vlan)#exit DLS2(config)#spanning-tree vlan 100 priority 8192 DLS2(config)#interface vlan 100 DLS2(config-if)#ip address 100.1.1.2 255.255.255.0 DLS2(config-if)#exit |
| ALS1(config)#interface vlan 100 ALS1(config-if)#ip address 100.1.1.3 255.255.255.0 ALS1(config-if)#exit |
| R1(config)#interface fastethernet 0/0 R1(config-if)#ip address 100.1.1.254 255.255.255.0 R1(config-if)#exit |
Next, verify your STP configuration using the show spanning-tree commands:
| ALS2#show spanning-tree vlan 100
VLAN0100 Bridge ID Priority 32868 (priority 32768 sys-id-ext 100) Interface Role Sts Cost Prio.Nbr Type |
Finally, verify IP connectivity between the switches using a simple ping:
| R1#ping 100.1.1.0
Type escape sequence to abort. |
Task 4
| ALS1(config)#access-list 1 permit 192.168.1.0 0.0.0.255 ALS1(config)#access-list 2 permit 192.168.2.0 0.0.0.255 ALS1(config)#snmp-server community LEVEL1 ro 1 ALS1(config)#snmp-server community LEVEL2 rw 2 ALS1(config)#snmp-server enable traps vtp ALS1(config)#snmp-server enable traps stp ALS1(config)#snmp-server host 10.1.1.253 traps version 2c LEVEL1 vtp ALS1(config)# snmp-server host 10.1.1.254 traps version 2c LEVEL2 stp |
| ALS2(config)#access-list 1 permit 192.168.1.0 0.0.0.255 ALS2(config)#access-list 2 permit 192.168.2.0 0.0.0.255 ALS2(config)#snmp-server community LEVEL1 ro 1 ALS2(config)#snmp-server community LEVEL2 rw 2 ALS2(config)#snmp-server enable traps vtp ALS2(config)#snmp-server enable traps stp ALS2(config)#snmp-server host 10.1.1.253 traps version 2c LEVEL1 vtp ALS2(config)# snmp-server host 10.1.1.254 traps version 2c LEVEL2 stp |
Verify your SNMP configuration using the show snmp commands:
| ALS1#show snmp Chassis: FAB0540Y20Z 0 SNMP packets input 0 Bad SNMP version errors 0 Unknown community name 0 Illegal operation for community name supplied 0 Encoding errors 0 Number of requested variables 0 Number of altered variables 0 Get-request PDUs 0 Get-next PDUs 0 Set-request PDUs 0 SNMP packets output 0 Too big errors (Maximum packet size 1500) 0 No such name errors 0 Bad values errors 0 General errors 0 Response PDUs 0 Trap PDUs SNMP global trap: disabled SNMP logging: enabled |
Task 5
| DLS1(config)#logging on DLS1(config)#logging host 10.1.1.253 DLS1(config)#logging host 10.1.1.254 DLS1(config)#logging trap informational DLS1(config)#logging buffered debugging DLS1(config)#logging buffered 10000 DLS1(config)#service timestamps log datetime msec localtime DLS1(config)#service sequence-numbers DLS1(config)#exit |
| DLS2(config)#logging on DLS2(config)#logging host 10.1.1.253 DLS2(config)#logging host 10.1.1.254 DLS2(config)#logging trap informational DLS2(config)#logging buffered debugging DLS2(config)#logging buffered 10000 DLS2(config)#service timestamps log datetime msec localtime DLS2(config)#service sequence-numbers DLS2(config)#exit |
Verify your configuration using the show logging commands:
| DLS2#show logging Syslog logging: enabled (0 messages dropped, 14 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: disabled Log Buffer (10000 bytes): 000082: *Mar 1 00:51:56.759: %SYS-5-CONFIG_I: Configured from console by console |
Task 6
| R1(config)#ntp master R1(config)#clock summer-time EST recurring R1(config)#clock timezone EST -5 May 1 01:40:00.000: %SYS-6-CLOCKUPDATE: System clock has been updated from 03:34:46 EST Wed Apr 10 2002 to 21:40:00 EST Sat Apr 30 2011 |
| DLS1(config)#ntp server 100.1.1.254 DLS1(config)#clock summer-time EST recurring DLS1(config)#clock timezone EST -5 |
| DLS2(config)#ntp server 100.1.1.254 DLS2(config)#clock summer-time EST recurring DLS2(config)#clock timezone EST -5 |
| ALS1(config)#ntp server 100.1.1.254 ALS1(config)#clock summer-time EST recurring ALS1(config)#clock timezone EST -5 |
| ALS2(config)#ntp server 100.1.1.254 ALS2(config)#clock summer-time EST recurring ALS2(config)#clock timezone EST -5 |
Following this configuration, use the show ntp status and show ntp associations commands to validate NTP. The show ntp status command shows whether or not the device is synchronized with the specified NTP server, the server stratum and server IP address. This command also includes the time received from the server. On the NTP master, the local Loopback address 127.127.7.1 is used as the NTP server IP address. This can be viewed below:
| R1#show ntp status Clock is synchronized, stratum 8, reference is 127.127.7.1 nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**16 reference time is D1673875.D60DC757 (21:40:05.836 EST Sat Apr 30 2011) clock offset is 0.0000 msec, root delay is 0.00 msec root dispersion is 15875.02 msec, peer dispersion is 15875.02 msec |
All other devices show the IP address of the NTP server, which is 100.1.1.254, as shown below:
| DLS1#show ntp status Clock is synchronized, stratum 9, reference is 100.1.1.254 nominal freq is 250.0000 Hz, actual freq is 249.9999 Hz, precision is 2**18 reference time is D167397B.173143D3 (21:44:27.090 EST Sat Apr 30 2011) clock offset is 0.0928 msec, root delay is 2.50 msec root dispersion is 1750.17 msec, peer dispersion is 875.05 msec |
The show ntp associations [detail] command provides information about each NTP server, including the stratum information as shown below:
| DLS1#show ntp associations detail 100.1.1.254 configured, our_master, sane, valid, stratum 8 ref ID 127.127.7.1, time D16739B5.D60C5557 (21:45:25.836 EST Sat Apr 30 2011) our mode client, peer mode server, our poll intvl 64, peer poll intvl 64 root delay 0.00 msec, root disp 375.03, reach 77, sync dist 752.274 delay 2.50 msec, offset 1.0837 msec, dispersion 375.99 precision 2**16, version 3 org time D16739BB.172AB9E9 (21:45:31.090 EST Sat Apr 30 2011) rcv time D16739BB.173610D7 (21:45:31.090 EST Sat Apr 30 2011) xmt time D16739BB.168E92A1 (21:45:31.088 EST Sat Apr 30 2011) filtdelay = 2.50 2.50 2.50 2.52 2.52 2.50 0.00 0.00 filtoffset = 1.08 0.09 0.08 0.06 0.04 0.02 0.00 0.00 filterror = 0.02 0.99 1.01 1.02 1.04 1.05 16000.0 16000.0 |
Task 7
| DLS1(config)#kron policy-list Save-Configuration DLS1(config-kron-policy)#cli write memory DLS1(config-kron-policy)#exit DLS1(config)#kron occurrence Auto-Management in 8:00 recurring DLS1(config-kron-occurrence)#policy-list Save-Configuration DLS1(config-kron-occurrence)#exit |
Following this configuration, use the show kron schedule command for validation:
| DLS1#show kron schedule Kron Occurrence Schedule Auto-Management inactive, will run again in 0 days 07:58:25 |
Final Switch Configurations
DLS1
|
DLS1#term len 0 Current configuration : 4401 bytes DLS1# |
DLS2
|
DLS2#term len 0 Current configuration : 4262 bytes DLS2# |
ALS1
|
ALS1#term len 0 Current configuration : 1458 bytes ALS1# |
ALS2
|
ALS2#term len 0 Current configuration : 1390 bytes ALS2# |
Final Router Configurations
R1
|
R1#term len 0 Current configuration : 890 bytes R1# |
