topic Re: Switch 4120 in ExtremeSwitching (EXOS/Switch Engine)

Switch 4120

Jose_Chaves — Fri, 14 Feb 2025 15:21:57 GMT

Hi,

Need help putting a 4120 on the network.

I have EXOS connected via FA and need to install a 4120, but I don't have all the commands to do like a normal Exos.

Regards,

Re: Switch 4120

Bartek — Mon, 17 Feb 2025 10:02:26 GMT

Hi,

The 4000 Series are ExtremeCloud IQ managed Layer 2 switches. As far as I know you should onboard your switch to ExtremeCloud IQ first (one switch requires one XIQ Pilot license):

Add device SN to your XIQ account devices list.
Make sure your switch is able to obtain IP address with valid DNS setup and is able to connect to XIQ.

I believe XIQ onboarding is prerequisite to manage your switch

Re: Switch 4120

Jose_Chaves — Wed, 19 Mar 2025 20:53:48 GMT

I’m trying to onboard on a XIQ-SE.

The switch is getting IP and connecting to the XIQ-SE.

Then the XIQ-SE configures the switch profile (username, password, SNMP, etc.) and I lose connectivity to the switch.

The switch creates the VLAN were we first got the IP (in this case 101) but does not request the i-sid for it via FA.

The config that I have on the VSP port is:

interface GigabitEthernet 1/10

default-vlan-id 0

no shutdown

no spanning-tree mstp force-port-state enable

fa enable

no fa message-authentication

fa management i-sid 20010 c-vid 101

exit

On the XIQ-SE, I have the site created. On that site I have the “ZTP+ Device Defaults” configured with:

Basic Management:

Use Discovered: IP and Management Interface

NTP Server: x.x.x.x

Admin Profile: Lab_Profile

Configuration/Upgrade:

Configuration Updates: Always

Firmware Updates: Never (I have also tried with Always)

Device Protocols/Features:

All enable except LACP, MVRP, VXLAN and DVR Leaf

Global IP to Site Mapping:

I have the range for the IP of the switch.

The switch version is the 33.2.1.12 and the XIQ-SE is the 24.10.

Is there something missing?

Re: Switch 4120

Jose_Chaves — Sun, 23 Mar 2025 12:03:31 GMT

Hi,

After some more debugs I find out that the problem was in the Spanning-tree.
After onboarding the switch, the XIQ-SE configures the switch port using the Port template “Interswitch”, that has “loop protection” enable. I have disabled the “loop protection” in the “Interswitch” template and it is working.
The strange thing is that it has worked before and I didn’t change anything in the config, just do a “unconfigure switch all” to repeat the process and make sure that everything was working.
Is this the template that was supposed to be applied to a port when a VSP is connected to a EXOS via Fabric Attached?
The config that I have in the VSP porti is:
interface GigabitEthernet 1/10
encapsulation dot1q
exit

interface GigabitEthernet 1/10
default-vlan-id 0
no shutdown
no spanning-tree mstp force-port-state enable
fa
fa enable
no fa message-authentication
fa management i-sid 20010 c-vid 101
exit

I can’t have the port configured whit Auto-Sense because the I have several floors in the building connected to the VSP and each floor was its management i-sid.

The final idea is to have LAG in the uplink ports connected to the VSP, but I still struggling whit that, can anyone also help in this point?

Best regards,
Jose Chaves

Re: Switch 4120

Bartek — Mon, 24 Mar 2025 09:10:00 GMT

Hi,

To create LAG you need to add VSP switch ports to MTL group and just apply FA config to created MLT.

mlt 1
mlt 1 name "MLT_TO_EXOS"
mlt 1 mem 1/10, ... //and other LAG members
mlt 1 encap dot1q
interface mlt 1
fa enable
no fa message-authentication
fa managemet i-sid 20010 c-vid 101
exit

FA will do the rest with your EXOS