cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

3294
Views
5
Helpful
4
Replies
kalashnikovsg
Beginner

MDS VSAN ISOLATION (Isolation due to domain not allowed)

Hello!

Im trying to connect MDS 9148 to existing fabric. I have an issue with one of vsan (31). All other vsan work fine. Ports for vsan 31 are in Isolated state. I see a reason of this behavior: Isolation due to domain not allowed. But I don't understand why? I didnt configure static domain ID.

From MDS 9148:

VSAN 31
The local switch is the Principal Switch.

Local switch run time information:
State: Stable
Local switch WWN: 20:1f:8c:60:4f:d3:f5:11
Running fabric name: 20:1f:8c:60:4f:d3:f5:11
Running priority: 140
Current domain ID: 0x2b(43)

Local switch configuration information:
State: Enabled
FCID persistence: Enabled
Auto-reconfiguration: Disabled
Contiguous-allocation: Disabled
Configured fabric name: 20:01:00:05:30:00:28:df
Optimize Mode: Enabled (Scale Restart)
Configured priority: 140
Configured domain ID: 0x00(0) (preferred)

Principal switch run time information:
Running priority: 140

Interface Role RCF-reject
---------------- ------------- ------------
fc1/1 Isolated Disabled
fc1/2 Isolated Disabled
fc1/3 Isolated Disabled
fc1/4 Isolated Disabled
---------------- ------------- ------------

From upstream MDS:

fc1/1, Vsan 31 - state(down), state reason(Isolation due to domain not allowed
), fcid(0x000000)
port init flag(0x10000),
Lock Info: resource [fc1/1, vsan 31]
type[0] p_gwrap[(nil)]
FREE @ 397798 usecs after Sat Nov 12 19:19:53 2016
type[1] p_gwrap[(nil)]
FREE @ 398099 usecs after Sat Nov 12 19:19:53 2016
type[2] p_gwrap[(nil)]
FREE @ 208668 usecs after Sat Nov 12 19:19:53 2016
0x501f5202
current state [TE_FSM_ST_ISOLATED_DM_ZS]
RNID info not found.
first time elp: 0
Peer ELP Revision: 3

4 REPLIES 4
santkumd528
Beginner

were you able to resolve this?

This seems to be caused by a domain conflict.  If the vsan comes online with a domain that's already in use in the fabric, when you try to merge, the two domains knock-heads and the result is isolating the vsan.

I had this happen tonight, 3 vsans, 1, 104, and 204.   1 and 204 worked, 104 did not.  Searching the domain list I found it was owned by another switch in the fabric.  (Dumb luck)

Setting the preferred Domain ID on the new switch to something unused and issuing a disruptiveRestart on the vsan fixed the problem, merge happened without issue.

JesseGilleland
Beginner

This seems to be caused by a domain conflict.  If the vsan comes online with a domain that's already in use in the fabric, when you try to merge, the two domains knock-heads and the result is isolating the vsan.

I had this happen tonight, 3 vsans, 1, 104, and 204.   1 and 204 worked, 104 did not.  Searching the domain list I found it was owned by another switch in the fabric.  (Dumb luck)

Setting the preferred Domain ID on the new switch to something unused and issuing a disruptiveRestart on the vsan fixed the problem, merge happened without issue.

Thanks for sharing, I’ve never seen that before.