VLAN member is in use (Fabric Attach) when add/remove a port from a vlan

[zhulin211]

Hey, I am new to Extreme world, I get error to add or remove a port from a vlan (VLAN member is in use (Fabric Attach)),   is this the only workaround to get it fixed --Solution: BOSS (ERS): Can't remove port from VLAN (Port in use by Fabric Attach) | Extreme Portal 

and if I change or delete MLT, the switch will lose connection to Core switch, correct?

appreciate if anyone can give some lights or suggestions.

thanks.

[Yoann_Jonard · Accepted solution]

Hello Zhulin,

If you are in the exact same scenario described in the KB (not only the same symptoms, but the same cause), you should follow it to get rid of the message yes, and it will definitely have an impact on the connectivity.

If you need to perform this change (deleting MLT etc.) remotely without physical console access, we have found the "script run" command to be the best. It allows you to put multiple configuration lines in a single file on a tftp server, and the switch will download it then execute the commands. The problem if you copy paste all at once the commands in the shell, is that they will be executed one by one. And as soon as you paste the command to delete the MLT you will lose the connectivity and the other CLI commands won't be pasted to your CLI. That's why you need to use the script command, but you need to be extra sure of your commands syntax and flow.

However, since you are new to Extreme as you stated, and Fabric Attach may not be easy at first, I would just double check if this message is not just normal behavior. Here are some things to know about FA :

1. You cannot manually add a VLAN dynamically created by Fabric Attach to a port.
2. I'm not sure on this one but I think you cannot remove a FA VLAN from a port as well. It is the end-system connected to the FA-enabled port which asks for the VLAN creation (or its deletion when it's disconnected).
3. If your end-devices are not Fabric Attach compatible and you have Fabric Attach configured on the uplink, you need to create the VLAN differently (with the command: i-sid #I-SID vlan #VLAN). Tag it on the ports where it's needed. Don't touch your uplink.
4. There is a specific command on the FA servers (your core switches probably) for the management VLAN of the ERS to be propagated through FA.

Anyway, this change must be performed out of business hours. You can also use the command "reload minutes-to-wait 5" before doing anything. This way if you make a mistake, the switch will reboot in 5 minutes without saving the configuration and you will get your access back.