I85PREP
⌘ K
Extreme Networks Associate (ECA) study materials
Extreme Networks Associate (ECA) study resources

Extreme Networks Associate (ECA): ExtremeXOS / Switch Engine and VOSS Configuration Basics

Extreme Networks Associate (ECA) · Work through your exam, one topic at a time.

All guide sections

ExtremeXOS / Switch Engine and VOSS Configuration Basics

The configuration domain tests command-level fluency on both operating systems, and above all that you do not mix them up. Expect questions on CLI modes, port notation, VLAN and IP provisioning, link aggregation, and saving configuration.

CLI models

  • Switch Engine (ExtremeXOS) has no enable mode: after login you type configure and show commands directly, with Tab completion.
  • VOSS uses a hierarchy: enable, then configure terminal, then interface GigabitEthernet 1/1, walking back up the tree to exit.
  • Port notation follows the OS: Switch Engine uses 1:1 (slot:port), VOSS uses 1/1 (slot/port).

The same task in two syntaxes

VLAN 100 named Sales with SVI 10.100.0.1/24, tagged on port 1.

  • Switch Engine: create vlan Sales tag 100; configure vlan Sales add ports 1:1 tagged; configure vlan Sales ipaddress 10.100.0.1/24; enable ipforwarding vlan Sales; save configuration.
  • VOSS: vlan create 100 name Sales type port-mstprstp 0; vlan members add 100 1/1; interface vlan 100 with ip address 10.100.0.1 255.255.255.0 enable; save config.

Link aggregation

  • Switch Engine: enable sharing 1:1 grouping 1:1-1:4 algorithm address-based L3_L4.
  • VOSS: set the LACP key and mode on member ports, then create and enable interface mlt 1 with its members.

Verification commands

show vlan; show ip route on VOSS versus show iproute on Switch Engine; show ports versus show interfaces; show lldp neighbors; show isis adjacencies in a fabric; show configuration or show running-config; and show tech for a support bundle.

Worked example

A VOSS switch loses a new VLAN after a reboot. Reasoning: the change was made in configure mode but never written with save config, so only the runtime configuration held it. The check is to compare show vlan against the saved configuration, then re-apply and save.

Traps

  • Typing enable on Switch Engine, where no such mode exists.
  • Mixing 1:1 and 1/1 syntax within a single answer.
  • Forgetting enable ipforwarding on Switch Engine, so the SVI never routes.
  • Assuming a VLAN edit persists without an explicit save.