Hey all,
I wanted to take a moment to touch on the minimum code level to onboard an ICX switch to RUCKUS Cloud. In order for an ICX to begin the onboarding process to RUCKUS Cloud, they must be running a minimum code level of 8090d. To confirm your ...
Hey all,
I want to take a look at building a stack from scratch. There are many ways to build, edit and manipulate stack units. Extensive details can be found in your respective stacking guide. In this example, I will be using 8095 software and tha...
Hey all,
Let's take look at creating LAGs (LACP and static). LACP (802.3ad) is the most common link-aggregation method. We also offer static LAGs.
To create an LACP LAG named 'testlag' with an auto-generated id, you would issue the following:
I...
Hey all,
I wanted to take a moment to look at spanning tree. By default, ICX switches run 802.1d spanning tree on a per-vlan basis. Ideally, we want to use a protocol with faster convergence such as rapid spanning tree (802.1w). I will go through ...
You do not need a VE in every vlan that the switch is going to pass traffic for. You can have a vlan be purely layer 2 if you would like. If your 8200 deployment is strictly layer 2, the one address you do assign to it is strictly for manageability p...
SZ is not my area of expertise, but they should reconnect on their own to my knowledge. What is the model and code on the switch side? I would recommend 8095m for all 7xxx series being connected to SZ.
It is a bit of a shift. The idea is take the confusion out of having multiple images for each platform and also unifies syntax instead of having different ways to address a box. I think it will be a good change in the long run! Layer 2 features are s...
You will need to put an IP address on a VE, a physical interface or the mgmt port itself. You should use 'ip route 0.0.0.0/0 <GW-address>' to define a default route.
