Transit VSAN and its state

[dynamoxxx]

Is it normal to have transit VSAN 30 to be in suspended state? Here is a picture of sample topology.  My DWDM connections are in VSAN 1 and as far as i know VSAN does not become acive unless there are ports assigned to it.  So is it normal to have transit VSAN is suspended state ?

Thanks

[Michael Brown]

Suspended does not sound right.  VSAN 30 should show operational state of 'up' if it had successfully merged across the DWDM.  There will not be any zones or zonesets.

If you look at the link between the 2 MDS, is VSAN 30 in the up state on both sides?

pod4-9509# sh int fc 4/1
fc4/1 is trunking
    Port WWN is 21:37:00:0b:fd:2c:8a:7f
    Peer port WWN is 00:00:00:00:00:00:00:00
    Admin port mode is E, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1
    Speed is 4 Gbps
    Trunk vsans (admin allowed and active) (30)  <----
    Trunk vsans (up)                       (30) <----
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()

If you see VSAN 30 in the initializing or the isolated state, look at the 'show port internal info interface fc 4/1' (in my example) and look for the reason that VSAN 30 is not up.

Hope this helps,

Mike

[dynamoxxx]

Mike,

so the transit VSAN should come even though there are no ports that are member of that VSAN ?  Don't have access to the gear right now, will try it in a few days.

Also is it correct to assume that VSAN 30 should be the only VSAN listed as "Allowed VSANs" in Trunk Config option for my DWDM ports (on 9513 and 9222i)?

Thank you

[Michael Brown · Accepted solution]

Correct on both points...  The VSAN will show operational state:up when the domain successfully gets in sync with another domain in that VSAN.  Or if there local ports that login to the domain.  Suspended would indicate some type of problem.  Even if the VSAN was created and no local devices login, or there is no ISL link to another domain, the operational state would be down.

The idea behind the transit VSAN is to provide isolation between the sites, so by design, it should be the only VSAN that is allowed to traverse the DWDM.  This way zone changes and switch additions/removals on each side are kept local and do not get transported across the DWDM.  Only IVR zone changes, and data between the IVR end devices will use the DWDM circuit.

-Mike

[dynamoxxx]

thank you again, transit VSAN did merge correctly and its state changed to up.

[kmong]

Hi what is your configuration for MDS 9148 connected to the device supporting DWDM?

[dynamoxxx]

not sure what you mean, i have MDS 9222i at each site that connect to each other over DWDM.