Demo

Switch challenge [ Click here - D9 ]. In this demo involves setting up basic details on the Ethernet ports on the switch, and also defining CDP. Each time the challenge is run it gives a new set of challenge parameters. The switch supports both Layer 2 and Layer 3 activities.

Scope

The CCNP Switch Certification covers the key areas of switching:

• Unit 1 - Introduction to Switching.
• Unit 2 - Switch Port Configuration.
• Unit 3 - VLANs and Trunks.
• Unit 4 - VLAN Trunking Protocol.
• Unit 5 - Aggregated Switch Links.
• Unit 6 - Traditional STP Spanning Tree and Unit 7 Spanning-Tree Configuration.
• Unit 8 - Protecting Spanning-Tree Protocol.
• Unit 9 - Advanced STP.
• Unit 10 - MLS (Multilayered Switching).
• Unit 11 - Enterprise Campus Network Design.
• Unit 12 - High Availability.
• Unit 13 - IP Telephony.
• Unit 14 - Wireless LANs.
• Unit 15 - Securing VLANs.

PART I: BUILDING A CAMPUS NETWORK

Unit 1 - Introduction to Switching

Challenges:

• Challenge_001 Introduction to Switching Lecture.
• Challenge_003 CON_HTTP_and_CDP. This challenge involves the configuration of the console password and to enable the HTTP server. The objectives of this challenge are to: Setup the console password; Enable the HTTP server; Define the HTTP port and define the name server.
• Challenge_004 VTY_SNMP_and_Username. This challenge involves the configuration of the VTY server and SNMP settings. The objectives of this challenge are to: Setup a password on the Telnet session; Define a username and password and Define SNMP parameters.
• Challenge_005 Gateway_and_Host_Table. This challenge involves the configuration of a hosts table. The objectives of this challenge are to: Define the default gateway and Enable an IP hosts table.
• Challenge_006 Ethernet_and_CDP_details. This challenge involves the configuration of ethernet port settings and CDP. The objectives of this challenge are to: Setup a description on FA0/1; Setup a speed on FA0/1; Setup duplex on FA0/1; and Define CDP details.
• Challenge_009 CON_and_VTY_details. This challenge involves the configuration of timeouts for the console. The objectives of this challenge are to: Setup a password on the console; and Define timeouts for the console.
• Challenge_012 Users and_passwords. This challenge involves the configuration of passwords, and usernames. The objectives of this challenge are to: Define the name server; Define the passwords; and Setup usernames and passwords.
• Challenge_014 HostsTable. This challenge involves the configuration of switchports. The objectives of this challenge are to: Define the switchport mode; Enable trunking; and Define spanning-tree costs.
• Challenge_015 Logging. This challenge involves the configuration of logging. The objectives of this challenge are to: Enable logging; Define Syslog server; Define buffer size; and Define logging level
• Challenge_016 HTTP_and_Banners. This challenge involves the configuration of the HTTP server and in creating banners. The objectives of this challenge are to: Enable HTTP; Define the HTTP server port; Define authentication; Define the helper path; Define an access-class number; and Create banners.
• Challenge_017 Clock_and_SubnetZero. This challenge involves the configuration of the clock and boot settings. The objectives of this challenge are to: Define the clock setting; and Define the boot method.
• Challenge_018 DHCP_Server. This challenge involves the configuration of the DHCP server. The objectives of this challenge are to: Setup a DHCP pool; Define the network addresses; Define the DNS-server; Define the NetBIOS server; Setup the lease time; Define the default-router; Define excluded addresses; and Define ping time-out.
• Challenge_019 Services. This challenge involves the configuration of services on the device. The objectives of this challenge are to: Setup services; Define timestamp formats; Disable small TCP servers; and Disable small UDP servers
• Challenge_021 Logging_Timezone_and_HTTP. This challenge involves the setting of logging and HTTP settings. The objectives of this challenge are to: Define a username and password; Setup logging; Define the clock; Define HTTP settings and Restrict HTTP access to a single host.
• Test0 ! Test
• Introduction Test (Test 1) ! Test

Unit 2 -Switch Port Configuration

Challenges:

• Challenge_011 Shutdown_ports. This challenge involves the configuration of the Ethernet ports. The objectives of this challenge are to Setup the first three Ethernet ports.
• Challenge_013 Switchport_mode. This challenge involves the configuration of switchports. The objectives of this challenge are to: Define the switchport mode; Enable trunking; and Define spanning-tree costs.
• Challenge_020 InterfaceRange. This challenge involves the configuration of a range of ports. The objectives of this challenge are to Setup a range of ports.
• Switch Port Configuration Test ! Test

Unit 3 VLANs and Trunks

Challenges:

• tests\lectures\Challenge_015. This is a lecture on VLANs.
• Challenge_002 VLAN_Hostname_Domainname. This challenge involves the configuration an IP address on a VLAN. The objectives of this challenge are to: Setup the VLAN address; Define a domain-name and define the default gateway.
• Challenge_007 VLAN_details. This challenge involves the configuration of VLANs. The objectives of this challenge are to: Setup VLAN 1, and define an IP address; and Setup VLAN 2, and define an IP address.
• Challenge_008 VLAN_2_details. This challenge involves the configuration of switchport access parameters. The objectives of this challenge are to: Setup VLAN 2; and Define switchport access for VLAN 2.
• Challenge_023. This challenge involves defining VLANs. The objectives of this challenge are to: Define and create VLANs and Assign ports of VLANs.
• Challenge_024. This challenge involves defining VLANs. The objectives of this challenge are to: Define and create VLANs; Assign ports of VLANs; and Define the name of a VLAN.
• Challenge_025. This challenge involves defining an extended VLANs (from 1006 to 4096). Extended VLANs are not saved to the VLAN database, Instead they are saved to the configuration file, and can thus be seen in the startup and running configuration (this makes them easier to copy onto other devices).The objectives of this challenge are to: Create an extended VLAN (from 1006 to 4096); and Define extended VLAN details.
• Challenge_026 VMPS. This challenge involves the configuration of VMPS. The objectives of this challenge are to Setup VMPS.
• Challenge_027. It is possible to configure VLANs using a VMPS server. The switch can be a VMPS client, which points to a VMPS server. The objectives of this challenge are to: Define VMPS servers; Define VMPS details; and Define dynamic membership for a port to a VLAN, through the VMPS server.
• Challenge_028 AccessMap. This challenge involves the configuration of an access-map. The objectives of this challenge are to: Define an access list to permit a range of addresses; Define an access-map; and Apply the access-map.
• Challenge_029. This challenge involves the configuration VLAN filtering to drop TCP packets. The objectives of this challenge are to: Define an extended named ACL; and Define the packets to be dropped by the VLAN.
• Challenge_030. This challenge involves the configuration of an access-map. The objectives of this challenge are to: Define an access list to permit a range of addresses; Define an access-map; and Apply the access-map.

4 VLAN Trunking Protocol

Challenges:

• Challenge_031 VTP. This challenge involves the configuration of VTP. The objectives of this challenge are to: Define VTP details; and Enable VTP pruning.
• Challenge_032. VTP (VLAN Trunking Protocol) maintains the consistancy of VLANs across a domain. This includes the addition, deletion and renaming of VLANs across the complete network. One or more changes are automatically updated across the entire network, and thus minimizing configuration errors. There is no way to send VLAN information to other switches, unless VTP is enabled. Only standard-range VLANs are supported (1-1005). Also a trunk route must be enabled for advertisements to be sent. With the Domain, If it is enabled the domain name is set, and the switch will listen to broadcasts for this domain name, otherwise it will ignore them. With the Mode, if VTP is disabled the mode is set to transparent. Any changes in VLANs will not be transmitted to other switches. With a server mode, the switch will transmit all changes in VLANs where as the client mode acts the same but it is not possible to create, change or delete VLANs. The objectives of this challenge are to: Define VTP server mode; Define VTP details; and Enable a trunk route.
• Challenge_033. VTP (VLAN Trunking Protocol) maintains the consistancy of VLANs across a domain. This includes the addition, deletion and renaming of VLANs across the complete network. One or more changes are automatically updated across the entire network, and thus minimizing configuration errors. There is no way to send VLAN information to other switches, unless VTP is enabled. Only standard-range VLANs are supported (1-1005). Also a trunk route must be enabled for advertisements to be sent. The objectives of this challenge are to: Define VTP client mode; Define VTP details; and Enable a trunk route.
• Challenge_034. Mode. If VTP is disabled the mode is set to transparent. Any changes in VLANs will not be transmitted to other switches. With a server mode, the switch will transmit all changes in VLANs where as the client mode acts the same but it is not possible to create, change or delete VLANs. The objectives of this challenge are to: Define VTP transparent.
• Challenge_035 1q. This challenge involves the configuring of 802.1Q tunnelling on a switch port. The objectives of this challenge are to: Define 802.1Q tunneling; and Define tagging of the VLAN ID.
• Challenge_036 l2. This challenge involves the configuring Layer 2 protocol tunneling. The objectives of this challenge are to: Define Layer 2 protocols to tunnel.
• Challenge_057. The Dot1q encapsulation protocol allows for a trunk connection to interconnect VLANs on different switches. The objectives of this challenge are to: Define normal switch port; and Define a trunk port.
• Challenge_058. The Dot1q encapsulation protocol allows for a trunk connection to interconnect VLANs on different switches and define the VLAN to stop trunking on an interface. The objectives of this challenge are to: Define normal switch port; Define a trunk port; and Define a port to stop trunking for a given VLAN.
• Challenge_059. The Dot1q encapsulation protocol allows for a trunk connection to interconnect VLANs on different switches and define the VLAN to stop trunking on an interface. The objectives of this challenge are to: Define normal switch port; Define a trunk port; and Remove a VLAN from trunking.
• Challenge_060. The Dot1q encapsulation protocol allows for a trunk connection to interconnect VLANs on different switches and define the VLAN to be removed from VLAN pruning. The objectives of this challenge are to: Define normal switch port; Define a trunk port; and Remove a VLAN from pruning.
• VLAN Test ! Test.
• Challenge_061 (Test 2) ! InterVLAN Test

5. Aggregated Switch Links

Challenges:

• Challenge_054 EtherChannel. This challenge involves the configuration of a Etherchannel. The objectives of this challenge are to: Define Etherchannel on ports.
• Challenge_055 lacp. This challenge involves configuring LACP (Link Aggregation Control Protocol - IEEE 802.3ad). The LACP packets use EtherChannels to intercommunicate, where the neighours and and port group capabilities are leart and compared with local switch capabilities. In LACP there are roles assigned to the EtherChannel endpoints. Thus the switch with the lowest system priority is then elected to make decisions about what ports are actively participating in the EtherChannel. The objectives of this challenge are to: Configure for LACP (Link Aggregation Control Protocol).

6 Traditional STP Spanning Tree and 7 Spanning-Tree Configuration

Challenges:

• tests\lectures\Challenge_016. This is a lecture on Spanning-tree.
• Challenge_038. This challenge involves the configuration of spanning-tree options. The objectives of this challenge are to: Setup VLANs; and Define spanning-tree settings.
• Challenge_042. The objectives of this challenge are to: Disable spanning-tree on a specific VLAN.
• Challenge_043. This challenge involves defining a primary root switch. The objectives of this challenge are to: Define a primary root switch.
• Challenge_044. This challenge involves defining a secondary root switch which will take over from the primary root switch if it fails. The objectives of this challenge are to: Define a secondary root switch.
• Challenge_045. This challenge involves defining port-priority and path cost for spanning-tree. The objectives of this challenge are to: Define port-priority for spanning-tree; and Define path cost for spanning-tree.
• Challenge_046. This challenge involves defining port-priority and path cost for spanning-tree, and hello-time and forward-time. The objectives of this challenge are to: Define port-priority for spanning-tree; Define path cost for spanning-tree; Define spanning-tree hello-time; and Define spanning-tree forward-time.

8 Protecting Spanning-Tree Protocol

Challenges:

• Challenge_039. This challenge involves enabling port security and the BPDU guard (to defined against spanning-tree attacks). The objectives of this challenge are to: Enable BPDU guard; Enable port-security; Define a maximum number of MAC addresses on a port; and Define a MAC address on a port.
• Challenge_040. This challenge involves the setting up UDLD (Unidirectional Link Detection) which monitors the condition of a link, and identifies if it detects a unidectional link, on which it can shut down the link, and display a message. The objectives of this challenge are to: Enable UDLD; and Apply it on an interface.
• Challenge_041. This challenge involves the setting up UDLD (Unidirectional Link Detection) which monitors the condition of a link, and identifies if it detects a unidectional link, on which it can shut down the link, and display a message. The objectives of this challenge are to: Enable UDLD; and Apply it on an interface.

9 Advanced STP

Challenges:

• Challenge_047. This challenge involves configuring MSTP and RSTP. RSTP (Rapid Spanning Tree Protocol – IEEE 802.1W) and MSTP (Multiple STP – IEEE 802.1S) are used to provide rapid convergence of the spanning-tree protocol. RSTP is the part that allows for rapid convergance and MSTP is used to group VLANs into a single spanning-tree instance. RSTP can converge the spanning-tree instance in less than a second, as apposed to almost 50 seconds for standard 802.1D spanning tree). This type of setup is important in real-time applications such as voice and video traffic. The objectives of this challenge are to: Define MST details; and Enable MSTP and RSTP for rapid convergence of the spanning-tree.
• Challenge_048. This challenge involves configuring a primary root switch for a given instance. The objectives of this challenge are to: Define a primary root; Define MST parameters on the interface, such as cost and port-priority; and Define global MST parameters, such as hello time, forward-time, maximum age, maximum hops and priority.
• Challenge_049. This challenge involves configuring a secondary root switch for a given instance. The objectives of this challenge are to: Define a secondary root; Define MST parameters on the interface, such as cost and port-priority; and Define global MST parameters, such as hello time, forward-time, maximum age, maximum hops and priority.
• Challenge_050. It is possible to create more than one trunk routes, and share traffic between them. Unfortunately loops can occur so STP is used to avoid these. In this case port-priorities are defined for each VLAN, so that specific VLANs take one of the trunk routes. The objectives of this challenge are to: Define VTP details; Define trunk ports (two, in this case); and Define port-priority for the trunk ports.
• Challenge_051. It is possible to create more than one trunk routes, and share traffic between them. Unfortunately loops can occur so STP is used to avoid these. In this case cost vlans are defined for each VLAN, so that specific VLANs take one of the trunk routes. The objectives of this challenge are to: Define VTP details; Define trunk ports (two, in this case); and Define cost values for the trunk ports.
• Challenge_052. This challenge involves the configuration of MST. The objectives of this challenge are to: Define MST.
• Challenge_053 mst. This challenge involves configuring a primary root switch for a given instance, with a point-to-point link for rapid transistions. The objectives of this challenge are to: Define a primary root; Define MST parameters on the interface, such as cost and port-priority; Define global MST parameters, such as hello time, forward-time, maximum age, maximum hops and priority; and Define a point-to-point link for rapid transistions.
• Challenge_056 ! STP Test.

10 MLS (Multilayered Switching)

Challenges:

• tests\lectures\Challenge_017. This is a lecture on MLS.
• Challenge_062. This challenge involves configuring a port (FA0/1) for Layer 3 access. The objectives of this challenge are to: Define Layer 3 access; Define an IP address for FA0/1; Define classless IP addresses; and Define zero-subnet.
• Challenge_063. This challenge involves configuring a static ARP cache, and other ARP details. The objectives of this challenge are to: Define the default gateway (if routing is not enabled); Define a static ARP value; and Define ARP timeout.
• Challenge_064. This challenge involves configuring ICMP Router Discovery Protocol (IDRP), which can be used to dynamically learn routes to other networks. For this it sends out discovery packets. The objectives of this challenge are to: Define Layer 3 operation on FA0/1; Enable IDRP; and Define IDRP details.
• Challenge_065. This challenge involves defining the ports and protocols are used for forwarding broadcast packets (ip forward-protocol), and where there is a broadcast-to-physical translation on an interface ( ip directed-broadcast). The objectives of this challenge are to: Define Layer 3 operation on FA0/1; Define details for forwarding broadcast packets (ip forward-protocol); and Enable the broadcast-to-physical translation on an interface ( ip directed-broadcast).
• Challenge_066. This challenge involves defining the ports and protocols are used for forwarding broadcast packets (ip forward-protocol), and a helper address for broadcasts. The objectives of this challenge are to: Define Layer 3 operation on FA0/1l Define details for forwarding broadcast packets (ip forward-protocol); and Define a helper-address.
• Challenge_067. This challenge involves defining an address to deal with broadcasts ( ip broadcast-address), and the enabling of fast flooding for UDP broadcast ( ip forward-protocol turbo-flood). The objectives of this challenge are to: Define Layer 3 operation on FA0/1; Define details for the broadcast address; and Enable turbo-flooding support.
• Challenge_068. This challenge involves enabling IP routing (ip routing), and configuring RIP. The objectives of this challenge are to: Enable IP routing; and Define RIP details for the network to broadcast into.
• Challenge_069. This challenge involves enabling IP routing (ip routing), and configuring RIP. The objectives of this challenge are to: Enable IP routing; Define RIP version; Define RIP timers; and Disable auto-summary.
• Challenge_070. This challenge involves enabling RIP authentication. The objectives of this challenge are to: Enable IP routing; Define RIP version; Define RIP Version 2; and Define Authenticated RIP.
• Challenge_071. This challenge involves defining summary address and split-horizon. The objectives of this challenge are to: Enable IP routing; Define a summary address; and Define no split-horizon.
• Challenge_072. This challenge involves enabling IGRP authentication. The objectives of this challenge are to: Enable IP routing; and Define IGRP details.
• Challenge_073. This challenge involves enabling OSPF routing. The objectives of this challenge are to: Enable IP routing; and Define OSPF.
• Challenge_074. This challenge involves enabling OSPF routing and interface OSPF details. The objectives of this challenge are to: Enable IP routing; Define OSPF; and OSPF details on an interface.
• Challenge_075. This challenge involves enabling OSPF routing and area details. The objectives of this challenge are to: Enable IP routing; Define OSPF; and OSPF area details.
• Challenge_076. This challenge involves enabling EIGRP authentication. The objectives of this challenge are to: Enable IP routing; and Define EIGRP details.
• Challenge_077. This challenge involves enabling BGP routing. The objectives of this challenge are to: Enable IP routing; Define BGP; and BGP AS details.
• Challenge_078. This challenge involves enabling BGP routing. The objectives of this challenge are to: Enable IP routing; Define BGP; and BGP neighbor details.
• Challenge_079. This challenge involves enabling BGP routing with a route-map. The objectives of this challenge are to: Enable IP routing; Define BGP; and BGP neighbor details with a route-map
• Challenge_080. This challenge involves enabling VRF (VPN Routing Forwarding). The objectives of this challenge are to: Enable IP routing; Define VRF; and Apply VRF forwarding on an interface.
• Challenge_010 Clock_Subnet_zero. This challenge involves the configuration the clock, boot system and DHCP pool. The objectives of this challenge are to: Setup the clock; Define the boot system; and Define the name of the DHCP pool.
• Challenge_081 ! MLS Test

PART II: DESIGN CAMPUS NETWORKS

11 Enterprise Campus Network Design

Challenges:

12 High Availability

Challenges:

• tests\lectures\Challenge_018. This is a lecture on availability.
• Challenge_035. This challenge involves an analysis of HSPF.
• Challenge_082 _standby. This challenge involves the configuration hot standby (HSRP). The objectives of this challenge are to: Define the standby port; and Define HSRP parameters.
• Challenge_083 _standby. The objectives of this challenge are to: Define the standby port; and Define MHSRP parameters.
• Challenge_084 _glbp. Gateway Load Balancing Protocol (GLBP) in the same way as Hot Standby Router Protocol (HSRP) and Virtual Router Redundancy Protocol (VRRP) provides an alternative route for network traffic from a failed router or circuit. It also supports load sharing between a group of redundant routers. This challenge involves the configuration of GLBP. The objectives of this challenge are to: Define GLBP details; and Enable GLBP.
• Challenge_085 _vrrf. Virtual Router Redundancy Protocol (VRRP) in the same way as Hot Standby Router Protocol (HSRP) and Gateway Load Balancing Protocol (GLBP). It provides an alternative route for network traffic from a failed router or circuit. This challenge involves the configuration of VRRF. The objectives of this challenge are to: Define VRRF details; and Enable VRRF.
• Challenge_086 ! Test

PART III: CAMPUS NETWORK SERVICES

13 IP Telephony

Challenges:

• Inline Power. This challenge involves configuring inline power.
• tests\lectures\Challenge_019. This is a lecture on QoS.
• Challenge_097 _classmap. This challenge involves the configuration of QoS. The objectives of this challenge are to: Define interesting traffic with an ACL; and Define QoS parameters.
• Challenge_098 _cbwfq. This challenge involves the configuration of Weighted RR (WRR). The objectives of this challenge are to: Enable QoS globally (mls qos); Define Layer 3 operation (no switchport ); and Define WRR
• Challenge_099 _pq. This challenge involves the configuration of a priority queue (PQ) which has four queues: high, medium, normal and low. The objectives of this challenge are to: Define queue limits; Define protocols to go into queues; and Apply PQ.
• Challenge_100 _pq. This challenge involves the configuration of a custom queue (CQ). Up to 16 queues can be configured. The objectives of this challenge are to: Define queues; andApply CQ.
• Challenge_101. This challenge involves configuring Auto QoS on a switch. The objectives of this challenge are to: Define Auto QoS
• Challenge_102 _mls. This challenge involves the configuring of MLS for Voice in 802.1P priority-tagged frames. The objectives of this challenge are to: Define MLS; Apply to FA0/1; and Define 802.1P frames.
• Challenge_103 _mls. This challenge involves the configuring of MLS for Voice where the CoS value that is received is overwritten with a new value. The objectives of this challenge are to: Define MLS; Define the routing for 802.1Q frames; Apply to FA0/1; and Define the CoS value – 0 lowest priority, 7 highest priority.
• Challenge_104 _mls. This challenge involves the configuring the switch so that the IP phone trusts the CoS value. The objectives of this challenge are to: Define MLS; Define the routing for 802.1Q frames; and Apply to FA0/1.
• Challenge_105 ! QoS Test.

14 Wireless LANs

• Single Autonomous AP. This challenge involves configuring for a single autonomous AP.

PART IV: SECURING SWITCHED NEWORKS

15 Securing VLANs

• Challenge_106 _AccessClass. This challenge involves the configuration of an access-class. The objectives of this challenge are to: Setup an access-list for a single access to the Web server; and Apply the access-list to the Web server.
• Challenge_107 _AccessClass. This challenge involves the configuration to deny access for a single host to the Web server. The objectives of this challenge are to: Define an access-list which denies a single host; and Apply the access-list onto the Web server.
• Challenge_108 _AccessClass. This challenge involves the configuration which permits a single host access to a Telnet server. The objectives of this challenge are to: Define an access-list which permits a single host access to the Telnet server; and Apply the access-list onto the Telnet server.
• Challenge_109 _AccessClass. This challenge involves the configuration which denies a single host access a Telnet server. The objectives of this challenge are to: Define an access-list which denies a single host access to a Telnet server; and Apply the access-list to the Telnet server
• Challenge_110 _AccessClass. This challenge involves the configuration of an restriction on a user. The objectives of this challenge are to: Define a single host access; and Link the access to a user.
• Challenge_111 _MAC. This challenge involves the configuration of switchport restrictions. The objectives of this challenge are to: Define port-security.
• Challenge_112 _SNMP. This challenge involves the configuration of a single host access to SNMP. The objectives of this challenge are to: Define an access-list which permits a single host; and Apply the access-list onto SNMP restrictions.
• Challenge_113 _aaa. This challenge involves the configuration of a local server for AAA. The objectives of this challenge are to: Define AAA; and Define the local server.
• Challenge_114 _aaa. This challenge involves the configuration of a RADIUS server for AAA. The objectives of this challenge are to: Define AAA; and Define the Radius server.
• Challenge_115 _aaa. This challenge involves the configuration of a Tacacs+ server for AAA. The objectives of this challenge are to: Define AAA; and Define the Tacacs + server.
• Challenge_116 _aaa. This challenge involves the configuration of a Tacacs+ server for commands. The objectives of this challenge are to: Define AAA; Define privileges; and Define command authorization for a Tacacs + server.
• Challenge_117 _dot1x. This challenge involves enabling 802.1x authentication. The objectives of this challenge are to: Define AAA; Enable 802.1x; and Define re-authentication.
• Challenge_118 _dot1x. This challenge involves enabling 802.1x authentication with authentication from an AAA server. The objectives of this challenge are to: Enable AAA; Define the Radius server; Enable 802.1x; Define re-authentication; and Define Dot1x timeouts.
• Challenge_119 _sec. This challenge involves the configuration of security of a switch. The objectives of this challenge are to: Define usernames and passwords; Define privilege levels; and Restrict access of users to a single host.
• Challenge_120 _sec. This challenge involves the configuration of security of a switch. The objectives of this challenge are to: Define Tacacs +; and Define accounting for start and stop events.
• Challenge_121 _sec. This challenge involves the configuration of security of a switch based on 802.1x. The objectives of this challenge are to: Define AAA; and Define port authentication.
• Challenge_122 _dot1x. This challenge involves enabling 802.1x authentication. The objectives of this challenge are to: Enable 802.1x; and Define re-authentication.
• Challenge_123 _dhcp_snooping. This challenge involves defending against an attacker depleting the DHCP pool using DHCP snooping. The objectives of this challenge are to: Enable DHCP snooping; and Apply DHCP snooping on an interface.
• Challenge_124 _storm. This challenge involves the setting up storm control. The objectives of this challenge are to: Enable storm control
• Challenge_125 _maclist. This challenge involves the configuration of a MAC ACL. The objectives of this challenge are to: Define a MAC ACL; Define a host to bar from FA0/1; and Apply the MAC ACL on an interface (FA0/1).
• Challenge_126 _SPAN. This challenge involves the configuration of monitors for port spanning. The objectives of this challenge are to: Define monitors for source and destination.
• Challenge_127. MAC address notification allows the tracking of MAC address activity through SNMP using a trap which sends information to an SNMP server when there is activity. The trap interval defines the time that the updates will be send to the SNMP server which can reduce network traffic when there are a great deal of MAC address activity. The objectives of this challenge are to: Define MAC address notification traps; and Define notification details.
• Challenge_128. Secure addresses allow the administrator to define the MAC address of the host which connects to a certain VLAN and interface to be pre-defined. If it does not match, it will not be able to connect. The objectives of this challenge are to: Define secure MAC addresses.
• Challenge_129 _mac_address_table. This challenge involves setting up a static MAC address table. The objectives of this challenge are to: Enable static MAC address table; and Show the MAC address table.
• Challenge_130 _mac_address_not. This challenge involves setting up SNMP MAC notification traps. The objectives of this challenge are to: Enable a MAC SNMP trap; Define an interval time; and Apply the trap on an interface.
• Challenge_131 ! Test

Finaltest

• Challenge_132 ! Test

OTHERS

Multicasting

• Challenge_087 _mult
• Challenge_088 _mult
• Challenge_089 _mult
• Challenge_090 _mult
• Challenge_091
• Challenge_092
• Challenge_093
• Challenge_094
• Challenge_095 _snoop
• Challenge_096 ! Multicast Test