# VOSS / EXOS command translator > A side-by-side reference between VOSS (Fabric Connect / SPBM) and EXOS. Search a task or command to see how each CLI expresses it - and where EXOS has no equivalent. - Tool: https://ronutz.com/en/tools/voss-exos-translator - Family: Networking --- ## What it does This is a reference translator between **VOSS** (Extreme's Fabric Connect / SPBM) and **EXOS**. It lays common tasks side by side so you can see how each command line expresses them, and it is explicit where EXOS has no equivalent - because EXOS does not run SPBM at all. It is a reference, not a config generator: every command is grounded in Extreme documentation, but you should adapt names, ports, and numbers to your own network and verify before applying anything. ## The key difference EXOS and VOSS are different operating systems that run on Extreme's universal hardware. VOSS is fabric-native: it builds an SPBM fabric with IS-IS, nicknames, B-VLANs, and I-SIDs. EXOS does not support SPBM. It joins a Fabric Connect network as a **Fabric Attach** edge (an FA Proxy or Client), and the VOSS FA Server provisions the I-SID for it. So for the fabric-core tasks - the SPBM instance, the nickname, the B-VLANs, an L3 VSN - there simply is no EXOS command, and the tool says so plainly. ## How to use it Type a task or a fragment of a command (for example `i-sid`, `nickname`, `vlan`, or `fabric attach`) and the table filters to the matching rows. Each row shows the concept, the VOSS command(s), the EXOS command(s) or a note that there is no equivalent, and a short explanation. Clear the box to see the whole table. ## What it is not It does not generate a deployable configuration, and it does not translate an arbitrary config file line by line. Fabric configuration is high-impact and platform-specific; this tool is meant to help you learn and cross-reference the two CLIs, not to produce config you would paste into a live switch unchecked. ## Standards and references - [Extreme Fabric Installation & Configuration Student Guide (2024): EXOS does not support SPBM; works with fabric via Fabric Attach](https://documentation.extremenetworks.com/FABRICENGINE/SW/91/FabricEngineUserGuide/) - the EXOS-does-not-run-SPBM fact and the Fabric Attach integration model - [Extreme Portal How To: Configure L3VSN (VOSS SPBM/IS-IS, L2 VSN, and L3 VSN CLI)](https://extreme-networks.my.site.com/ExtrArticleDetail?an=000082930) - verified VOSS router isis / spbm / nick-name / b-vid / vlan i-sid / ipvpn commands - [Extreme VOSS command reference: vlan i-sid and vlan members syntax](https://documentation.extremenetworks.com/VOSS/SW/89/vossuserguide/GUID-1BC71501-66E0-4458-807F-CB320C884AD4.shtml) - vlan i-sid and vlan members add syntax - [ExtremeXOS Command Reference / User Guide: create vlan, configure vlan add ports, Fabric Attach, IS-IS](https://documentation.extremenetworks.com/exos_30.4/GUID-AC9E8550-3F33-409F-9689-E85BF305B749.shtml) - EXOS VLAN, Fabric Attach, and IS-IS command syntax ## Related reading - [VOSS vs EXOS: Two Extreme Operating Systems](https://ronutz.com/en/learn/voss-vs-exos.md): Extreme ships universal hardware that boots either EXOS or VOSS (Fabric Engine). This is what actually differs - a traditional-Ethernet OS with an intuitive CLI versus a fabric-native OS built on SPBM - and the three boundaries at which they interconnect.