IVR problems

[kevin.cooney]

A customer recently added some new IVR zones using some older, unused VSANs. After activation of the zonesets, only VSANs between one set of switches are connected, and an existing IVR zone in between a different set of VSANs no longer works. Knowing next to nothing outside of basic MDS zoning, I'm spinning my wheels trying to determine what is wrong.

What would prevent a VSAN in one switch from communicating to a VSAN in another switch while other IVR zones in the same pair of switches works OK?

SANSW_SITE1_A (vsan 11) to SANSW_SITE2_A (vsan 12) - devices in new IVR zone here can communicate

SANSW_SITE1_B (vsan 21) to SANSW_SITE2_B (vsan 22) - devices in new IVR zone do not communicate; a separate IVR zone connecting vsan 41 to vsan42 has stopped working as well.  Other IVR zones in different vsans still work.

All I can do it look at the configuration of the "B" switches to see what could have been mis-configured but nothing jumps out at me.

[dynamoxxx]

Kevin,

run "sh ivr vsan-topology" and figure out if the WWN of switch in question is listed as well as the appropriate VSAN #.  

[kevin.cooney]

All switches are shown and all VSANs appear to be correct.

They are using device-alias for IVR zone members. Should they be using pwwn?

[dynamoxxx]

device-alias is the preferred way.  Can you share output from "sh ivr vsan-topology"

[kevin.cooney]

TAC case was opened and "fcns refresh all vsan <transit vsan #>" command was recommended for the two switches in question.  This fixed the problem.