03-20-2018 02:07 AM
We had 2 fabrics with each 3 switches. We decomissioned the third switch and now have 2 switches / fabric.
Now we have the "Segmented switch" status in the GUI. (See attachment)
Is there any way to get rid of this without any downtime?
03-20-2018 02:48 AM
how the removed switch was connected / ISL - to ?
cascade or mesh ?
befor decomiss, did you check if the switch was set as subordinate or principal ?
03-21-2018 03:06 AM
whit or without, BNA don't resolved the problem and is not a solution.
second, in a small SAN Environments make absolutely no sense to create a Fabric as Mesh, Brocade best practicies is Cascade.
in feew word, it is not easy to remove / decomissioned a switch from a Mesh Fabric, in you case I would suggest - I don't know you config - to reconnect the switch in order to review the config.
then, the best solution is to disconnect another member switch from a Fabric, create a New config and move all path to.
finally disconnect the second Prod. switch and ISL in order to create a New Fabric.
BTW about Mesh Design, the best practices is at least of 4* Switches.
03-21-2018 03:57 AM
Thanks for your reply.
So basically there is no way to get rid of this?
We cannot just decomission a production switch... Can this "Segmented status" cause any impact
on production in the future?
03-21-2018 04:12 AM
you can try to rebuild a Fabric, see this Threads for some details
03-22-2018 08:50 AM - edited 03-22-2018 09:02 AM
I've already tried this on an old switch that had the same problem and it did not solve this issue sadly.
I'm just wondering if this can prove troublesome in the future or will this never have any impact on the fabric?