How to prevent VSAN0001 segmentation

[Guest]

Hello guys, When i connect a new switch to my fabric, i always see VSAN0001 segments. We are not using VSAN001 for anything, its state is down ..it does not really affect anything but i just hate to see it listed like that. Other than setting "trunk allow" vsan 1 ..anything else i can do ? 

[Guest]

I don believe there is anything you can do here, it is the expected/normal behavior, as even though it is down, it is in fact segmented.  Like you, I typically don use VSAN1.  There may be something in FM you can do to "Hide suspended VSANs" or something, I am not sure. Brian

[Guest]

Hello On the 1st Cisco SAN course I went on 2-3 years back, the instructer told us it was good practice to always trunk vsan 1. I can remeber why to be honest!  And no, I don use it for anything either. At least you get a nice clean screen in FM. Steven

[Guest]

There is no reason to trunk VSAN1 or any VSAN for that matter unless its actually being used.   There are some bugs out there where you need to trunk the Port VSAN, however I would not even do this unless you are hitting those bugs.  For example, say the Port VSAN for fc1/1 (TE Port) is 2, so then you may need to trunk VSAN 2 to avoid certain bugs.  But this is a bug issue, not a design issue. VSAN1 is bad because its the default port VSAN.  Not using VSAN1 is a good practice as this way if someone plugs in a switch and it starts to trunk, you are not introducing fabric instability and other undesired behavior.   I am pretty sure older FMs did not show the VSAN001s as segmented, (3.3), I believe later on this showed this way, and thats why I thought maybe there is a preference option to display it this way, or it may just be the changed behavior of FM. Brian

[Guest]

i just tried something.  I suspended VSAN 1 on both switches and now segmentation is gone. Right now i am playing with two test servers but in the future my DWDM ports will be in VSAN 1, so i wonder if suspending VSAN 1 would case any harm.