04-07-2021 03:14 PM
Hi All,
What a re the proper steps to break an ISL between two MDS9132 switches?
Is it just as easy as removing the connection between the two, or disabling the trunk port, or there is more than that involved?
Appreciate your input.
04-07-2021 05:18 PM
depends on deployment, if the no services critical then your description is correct.
04-08-2021 04:43 AM
It was deployed this way before me and I inherited this solution, so I am not sure if there are or there are no critical services. How do I identify them, which services are they? Can you please elaborate? What prep work should I do prior to breaking the ISL? Can you provide more detailed steps please?
04-08-2021 10:40 AM
most of the questions to be answered by yourself, this is your environment, you need to know what service they are connected.
by the way what is the reason to remove ISL ? - i would have asked first instance.
04-08-2021 10:58 AM
The reason for removing the ISL is to create two separate fabrics - fabric A and fabric B, with one switch per fabric. Currently, there is only fabric A, with two member switches ISL'ed.
Give me an example please, what services you are talking about - SAN, storage, server, or app services? A little more details please regarding "services".
04-09-2021 11:02 PM
The reason for removing the ISL is to create two separate fabrics - fabric A and fabric B, with one switch per fabric. Currently, there is only fabric A, with two member switches ISL'ed.
If you made a decision to split, if the device connected dual-homed, then you can split the devices as you desired to do.
Give me an example please, what services you are talking about - SAN, storage, server, or app services? A little more details please regarding "services".
Services - the device connected to these switches and what is the service you hosted to pass the traffic using these switches.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: