This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Whats VOSS option when initializing new 5520 switches?

Whats VOSS option when initializing new 5520 switches?

Go to solution
Keith9
Contributor III

‎02-09-2021 04:48 PM

We are rolling out new 5520 switches at our locations and one of the questions you get when you first power on a new device prior to its initial configuration is Would you like to change the switch OS to VOSS?  What is VOSS?

 

What benefits does it have?  Is it good?  Any references you can provide as to why one would choose this option over EXOS would be appreciated.

0 Kudos
1 ACCEPTED SOLUTION

Go to solution
EXTR_Paul
Extreme Employee

‎02-10-2021 06:40 PM

VOSS is the Switch O/S that runs on VSP switches.  Traditionally this was seen on Avaya VSPs. But has continued to be developed with the newest Extreme VSPs.(4900, 7400, 8600).   And now going forward Extreme switches will give customers the options to run the unified hardware platforms in either EXOS or VOSS mode on the 5000 series.

VOSS’s main differentiator compared to traditional switches comes to topology deployment and inter-switch communication.  In a regular switch, inter-switch links will be L2 trunks or Routed interfaces.  Switches running VOSS uses Shortest Path Bridging (SPBm) as single protocol for the topology. And allows you to deploy Layer 2, Layer 3, or VRF services at the network edge only.  you don’t need to touch every single link or switch in the network.

 

As for Pro’s/Con’s.

VSPs can’t stack.  So when you need high density switch ports.  It makes sense to deploy the switches in EXOS mode.

However, I do have customers who deploy VSPs in the closet.  They simply use SPBm has the inter-switch protocol.  But you do need to be mindful how many switches you are cascading in the IDF. 

 

VSPs are great for Data Center, Core and Distribution because you can get very creative in topology designs.  And VOSS switches do support clusters of two with MC-LAG/vIST.

VSPs are also great for CCTV deployments because SPBm routes multicast traffic natively.  No need for PIM, rendezvous points, manually setting queirier addresses or igmp ranges.   Yuck.

 

Another caveat is if you are using XMC/Control with L7 policies it makes sense to deploy the switch in EXOS.  Today VOSS does not support Policy.

IMHO, if your network is a single switch or just a simple topology of 4 or 6 switches it really doesn’t matter what you use, EXOS or VOSS.

But VOSS really shines when you have dozens and dozens, or hundreds of switches in a single fabric.  The ease of configuration is something to be seen.   12 lines of switch code and you are off.

Here is a great paper talking about it.

https://documentation.extremenetworks.com/TCG-TSG/SPBVOSS_TCG_CG.pdf?_ga=2.240576579.1362158379.1612...

View solution in original post

11 REPLIES 11

Go to solution
Bill_Handler
Contributor II

‎02-09-2021 05:31 PM

Keith,

 

I mostly agree with Mig - VOSS for Core/Distribution/Aggregation layer, but I think XOS at the edge is better with regard to loop protection on the edge ports using ELRP.

The SPBM fabric is truly amazing with how it works, and the integration with XOS via Fabric Attach is awesome.  Couple that with ExtremeControl (NAC) and it is nearly bulletproof.

Just my opinion…

Thanks,

Bill

0 Kudos

Go to solution
Miguel-Angel_RO
Valued Contributor II

‎02-09-2021 05:07 PM

Keith,

 

There are thousands of pages in the manuals describing what is VOSS.

It will be difficult to summarize it all in posts d973928df3764348a0b8d52cc37e2dfb_1f601.png

 

VOSS is the OS used to enable and drive the SPBM Fabric.

If I’m asked what is my choice, it will be with no hesitation VOSS for the cores, backbones and edge switches.

 

To put the question the other way around, check what can bring an SPBM Fabric to your needs.

Just a summary:

  • No more spanning tree
    • use multiple uplinks between different switches in an active-active way without loops
  • Get rid of the configuration of the VLANs on the uplinks, all is managed at the end points with i-sids
  • Get rid of the protocol stacks as IGMP, RIP, OSPF, STP, etc in your backbone
    • all is replaced by only one protocol (isis)
  • reduce your time to deploy new or modify services
  • reduce by far human errors
  • increase scalability
  • and more and more

Click on VOSS d973928df3764348a0b8d52cc37e2dfb_1f61c.png

 

Mig

 

GTM-P2G8KFN