- Silver, 250 points or more
Please answer my questions regarding IVR considering my design, see picture attached:
Considering all VSANs have unique id, so IVR-NAT is not required.
1) I am going to configure transit VSAN 30, this VSAN will only contain ports that provide DWDM connectivity ?
2) I will create transit VSAN ( VSAN 30) on both 9513 and 9222i switch, that will be the only VSAN allowd to be trunked, so essentially VSAN 30 will merge.
3) IVR is enabled on both 9513 and 9222i, VSAN 10 needs to be able to talk to devices on VSAN 110, VSAN 20 needs to be able to talk to devices in VSAN 200. When i run IVR Wizard for the very first time, do i need to select VSAN 10, 110, 20, 200 and VSAN 30 which is my transit VSAN ?
4) If i have a host that is directly plugged-in into my edge 9134, can it be IVR zoned to an array plugged-in directly into 9124e, considering 9134 and 9124e do not support IVR but they are connected to switches that have IVR enabled.
Looking at my design are there any questions that i should be asking ?
Thank you very much
Ok, I see what your asking now. The Port VSAN for those DWDM ports doesn't matter. Although I typically make a TE VSAN and just put those in it. It can be whatever you want, and yes you just want to trunk the Transit VSAN.
In general, you want default zone deny for all VSAN's in my opinion. I rely on zoning. You can make default zone permit, but I would advise against it in most situations and in the transit VSAN for sure since there are no members in that VSAN that should be originating or destinating any traffic.
I like default zone deny, so nothing can talk unless I specifically zone it.
Yes you are correct in your configuration of a topology.
The steps are as follows:
1. Make sure FC Domain ID's are unique
2. enable ivr on 9513 and 9222i
3. Turn on CFS for IVR on both 9513 and 9222i
4. Define IVR Topology (done on 1 switch)
Your topology is correct
5. Activate Topology (done on 1 switch)
"ivr vsan-topology activate"
You only need to do the above from the switch you defined the topology on.
6. Create IVR zones: (done on 1 switch)
ivr zone name ivrzone
member pwwn 21:00:00:00:00:00:00:00 vsan 10
member pwwn 21:00:22:22:33:33:33:33 vsan 20
7. Create IVR zoneset (done on 1 switch)
ivr zoneset name ivrzoneset
8. Activate IVR Zoneset (done on 1 switch)
ivr zoneset activate name ivrzoneset
You need to have an active zoneset. If you don't then you need to add the "force" parameter to the above. After you activate an IVR Zoneset, it will automatically add ivr zones to your current zones (for those VSAN's in your topology)
9. Commit (done on 1 switch)
So IVR modifies your zonesets, after running the above you can look at your activate zonesets and see what its done.
You are correct in that you don't actually define your transit VSAN as a way of communication, that is figured out automatically.
As far as running ivr vsan-toplogy activate and that automatically being pushed to the 9222i, that is accomplished via CFS, so you have to make sure you have enabled IVR and CFS on both switches.