Solved: IVR: How to select 2 transit VSANs at the same time.

blagoy.popov · ‎08-25-2005

Hi ,

Have somebody had problems with this issue? When I create IVR zone with the Wizard in the Fabric Manager, eventhough I have two(2) transit VSANs between the boxes it does not let me choose both of them . After i choose one of them and then look at IVR topology the second transit VSAN had not been included in the IVR topology.

To make it more complicated: Becouse first transit VSAN has only 2Gb FC links and the second 1G FCIP links, the first VSAN has better FSPF cost and all traffic goes through it . But the grate confusion for me is when I disconnect the primary link, eventhoug the second vsan is not in the IVR topology the traffic starts going through it.

How can I make both VSANs to be visible in the IVR topology at the same time becouse like it is right now it os not really clear in the configuration ( eventhough everything is working just fine )

Thanks a lot in advance.

Blago

j.sargent · ‎08-25-2005

It will not let you select two transit VSANs at once because a single switch can not balance the IVR traffic over more than a single VSAN at once. If the default transit VSAN goes down, it will select another transit VSAN with the least-cost path, which is the VSAN on your FCIP link. This is the way it should work. You can not specify an explicit transit VSAN as if to make it a static route...which might be confusing you. Perhaps that ability will be added in a future version of code...?

So when you document your configuration, just make sure you document that it will automatically fail over to the next least-cost transit VSAN available in the fabric. Obviously, for a VSAN to be able to participate as a transit VSAN, the switch must have IVR enabled.

I would suggest pages 17-10 through 17-13 of the Configuration Guide as a reference. Hope that helps clear things up a bit...

View solution in original post

j.sargent · ‎08-25-2005

It will not let you select two transit VSANs at once because a single switch can not balance the IVR traffic over more than a single VSAN at once. If the default transit VSAN goes down, it will select another transit VSAN with the least-cost path, which is the VSAN on your FCIP link. This is the way it should work. You can not specify an explicit transit VSAN as if to make it a static route...which might be confusing you. Perhaps that ability will be added in a future version of code...?

So when you document your configuration, just make sure you document that it will automatically fail over to the next least-cost transit VSAN available in the fabric. Obviously, for a VSAN to be able to participate as a transit VSAN, the switch must have IVR enabled.

I would suggest pages 17-10 through 17-13 of the Configuration Guide as a reference. Hope that helps clear things up a bit...

blagoy.popov · ‎08-25-2005

Thanks a lot. I did not think about this. Well if this is the reason, hopefuly it will change in future releases becouse it is somehow unclear. Anyway thanks one more time.

Best regads, Blago