Extreme Certified Professional - Extreme Switching study materials
Extreme Certified Professional - Extreme Switching study resources

Extreme Certified Professional - Extreme Switching study plan

Extreme Certified Professional - Extreme Switching · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Extreme Switching Architecture and Hardware Fundamentals & Initial Configuration, Management Access, and Software Updates

  • Identify the major Extreme Switching hardware families (e.g., X435, X465, X590, X695, VSP, 5000 series) and their target use cases, port densities, and stacking capabilities from official datasheets.

  • Diagram the ExtremeXOS architecture: control plane vs. data plane, process separation, and how the CLI and management interfaces map to system components.

  • List the default management access methods (console, SSH, Telnet, HTTP/HTTPS, SNMP) and the commands to enable, disable, and secure each one.

  • Outline the software update workflow: image download, alternate boot partition, and commit/reboot steps using ExtremeXOS commands.

  • Compare ExtremeXOS and VSP Operating System (VOSS) CLI conventions, including command hierarchy and configuration save behavior.

Your checkpoint

Create a one-page reference sheet listing hardware families, default management ports, and the exact CLI steps for a safe software upgrade.

Week 2

Initial Configuration, Management Access, and Software Updates & Monitoring, Troubleshooting, and Operations

  • Configure a switch from factory defaults: hostname, management IP, default gateway, NTP, and syslog, then verify connectivity.

  • Enable secure management access (SSH, HTTPS) and disable insecure protocols (Telnet, HTTP) using ACLs and user accounts with appropriate privilege levels.

  • Perform a software upgrade and rollback in a lab or simulator, documenting the commands and verification steps.

  • Use show commands (show version, show configuration, show management, show log) to verify configuration and system health.

  • Set up SNMPv3 and syslog destinations for centralized monitoring, and confirm log messages are received.

Your checkpoint

Produce a verified configuration script (or CLI transcript) that brings a switch from factory default to a secured, monitored state with proof of successful upgrade/rollback.

Week 3

VLANs, Spanning Tree, and Layer 2 Redundancy

  • Create and manage VLANs (port-based, tagged/untagged) and verify VLAN membership using show vlan and show ports information.

  • Configure 802.1Q trunking between two switches and confirm VLAN propagation with ping tests and MAC address tables.

  • Configure STP variants (STP, RSTP, MSTP) and tune parameters (bridge priority, port cost, edge ports) to control root bridge election.

  • Implement Layer 2 redundancy features such as Extreme Standby Router Protocol (ESRP) or VRRP for gateway redundancy, and verify failover.

  • Troubleshoot common Layer 2 loops and misconfigurations using show spanning-tree, show l2stats, and log analysis.

Your checkpoint

Build a three-switch lab topology with redundant links, multiple VLANs, and STP/ESRP failover; submit a topology diagram and CLI evidence of converged state and failover test.

Week 4

VLANs, Spanning Tree, and Layer 2 Redundancy & Link Aggregation and Load Sharing

  • Configure link aggregation groups (LAGs) using static and LACP modes, and verify load sharing with show lag and traffic tests.

  • Explain hashing algorithms used for LAG load balancing and adjust hash settings where supported.

  • Implement multi-switch link aggregation (MLAG) or equivalent stacking-based aggregation, and verify redundancy by disabling a member link.

  • Tune STP and LAG interaction to avoid loops and ensure fast convergence (e.g., edge ports, BPDU guard).

  • Document a troubleshooting sequence for LAG not forming, including checking LACP timers, member port states, and configuration mismatches.

Your checkpoint

Create a LAG/MLAG configuration guide with tested commands, verification outputs, and a failover test report showing uninterrupted traffic.

Week 5

IP Routing and Layer 3 Forwarding on Switches

  • Configure VLAN interfaces (SVIs) and enable IP forwarding, then verify routing between directly connected subnets.

  • Configure static routes and a default route, and test reachability with traceroute and show iproute.

  • Enable and tune OSPF (area, cost, authentication) on switches, and verify neighbor adjacencies and route propagation.

  • Implement policy-based routing or route maps (if supported) to control traffic flow, and validate with show commands.

  • Troubleshoot Layer 3 issues using show iparp, show iproute, and debug commands, focusing on ARP and routing table inconsistencies.

Your checkpoint

Build a multi-VLAN routed topology with OSPF and static routes; submit a routing table excerpt and a traceroute proving correct path selection.

Week 6

IP Routing and Layer 3 Forwarding on Switches & Network Security, Authentication, and Access Control

  • Configure DHCP relay and helper addresses on VLAN interfaces, and verify clients obtain addresses from a central server.

  • Implement network security using ACLs (standard and extended) to filter traffic between VLANs, and test with permitted/denied flows.

  • Configure 802.1X port authentication with RADIUS, including supplicant, authenticator, and authentication server roles, and test authentication success/failure.

  • Set up MAC-based authentication or captive portal (if applicable) and integrate with the existing RADIUS infrastructure.

  • Apply best practices for management plane security: strong passwords, privilege levels, and restricted management access via ACLs.

Your checkpoint

Produce a security configuration checklist and a test report showing ACL enforcement, 802.1X authentication, and DHCP relay working in a lab.

Week 7

Monitoring, Troubleshooting, and Operations

  • Use monitoring tools (show commands, SNMP polling, sFlow) to collect interface statistics, CPU, and memory utilization.

  • Configure and interpret port mirroring for traffic analysis, and capture packets to troubleshoot a simulated issue.

  • Analyze syslog and trap messages to identify common faults (link flapping, STP topology changes, authentication failures).

  • Perform a structured troubleshooting exercise: given a broken lab scenario, isolate and fix the issue using a documented methodology.

  • Create a runbook for routine operations: backup configuration, schedule software updates, and monitor health checks.

Your checkpoint

Write a troubleshooting case study (problem, investigation steps, root cause, resolution) based on a lab scenario, including relevant show command outputs.

Week 8

Extreme Switching Architecture and Hardware Fundamentals & Initial Configuration, Management Access, and Software Updates & VLANs, Spanning Tree, and Layer 2 Redundancy & Link Aggregation and Load Sharing & IP Routing and Layer 3 Forwarding on Switches & Network Security, Authentication, and Access Control & Monitoring, Troubleshooting, and Operations

  • Review all domains using a practice exam or flashcards, focusing on weak areas identified in previous weeks.

  • Reconfigure a switch from scratch within 30 minutes to reinforce initial configuration and management access.

  • Explain key architecture and hardware concepts (e.g., stacking, high availability, packet flow) in your own words.

  • Troubleshoot a complex multi-domain scenario combining VLANs, LAGs, routing, and security.

  • Finalize a one-page cheat sheet summarizing critical commands and concepts for each domain.

Your checkpoint

Complete a timed practice exam (at least 60 questions) with a score of 80% or higher, and submit a revised cheat sheet covering all domains.

Milestones

Week 4: Successfully build a redundant Layer 2 topology with VLANs, STP, ESRP/VRRP, and LAG/MLAG, and demonstrate failover with minimal disruption.

Week 6: Configure and verify inter-VLAN routing with OSPF, ACLs, DHCP relay, and 802.1X authentication in a lab environment.

Week 8: Score 80% or higher on a timed practice exam covering all domains, and demonstrate a from-scratch switch configuration within 30 minutes.