Support for NAS servers.
1 post • Page 1 of 1
Hello guys, 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
1) Yes2) Yes3) Yes4) Yes, edge devices do not have to participate in IVR directly There is really not too much to consider that you haven covered. You will of course need to create ivr zones and an ivrzoneset. I have not used the FM Wizard. When configuring via CLI you can do auto topology discovery or manual, I normally do manual, not sure what the wizard ends up doing.
Thank you Brian. A couple more questions, lets say i decide to configure using the cli, do these steps make sense: Lets assume that all VSANs are already created, transit vsan 30 has been merged. 1) Define which VSAN will participate in IVR ( these steps need to be done on 9222i and 9513 ? ) switch(config)# ivr vsan-topology databaseswitch(config-ivr-topology-db)# autonomous-fabric-id 1 switch 20:00:00:05:30:01:1b:b8 vsan-ranges 10,20,30 switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch 20:00:00:05:30:01:1b:b8 vsan-ranges 110,200,30 switch(config)# ivr vsan-topology activate 2) I don see any option to define my vsan 30 (transit) as the way of "communication", will IVR automatically select VSAN 30 just because its merged ?3) If i am not running IVR auto mode, what would my next step to be ? Lets say i create an IVR zone on 9513, just because i ran "ivr vsan-topology activate" does not mean that it got pushed to 9222i right ? I have to manually "push" that to 9222i ? If yes, how do i do that ? Am i missing anything else ? Thank you
Yes you are correct in your configuration of a topology. The steps are as follows: 1. Make sure FC Domain IDs are unique 2. enable ivr on 9513 and 9222i"ivr enable" 3. Turn on CFS for IVR on both 9513 and 9222i"ivr distribute" 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 ivrzonemember pwwn 21:00:00:00:00:00:00:00 vsan 10member pwwn 21:00:22:22:33:33:33:33 vsan 20 7. Create IVR zoneset (done on 1 switch) ivr zoneset name ivrzonesetmember ivrzone 8. Activate IVR Zoneset (done on 1 switch) ivr zoneset activate name ivrzoneset You need to have an active zoneset. If you don 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 VSANs in your topology) 9. Commit (done on 1 switch)ivr commit 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 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.
Brian, can you please expand on step 8, i got a little lost there. So i have my IVR zoneset, i add my members to it and i activate my zoneset. How is this process different from any regular zoneset activation ? I am trying to understand why would i need to add the "force" option? Also what do you mean that "it will automatically add ivr zones to your current zones" ? IVR Zones will reside in the IVR zoneset, they don mess with existing zonesets in regular VSANs ?8. Activate IVR Zoneset (done on 1 switch) ivr zoneset activate name ivrzoneset You need to have an active zoneset. If you don 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 VSANs in your topology) Thank you so much for taking the time to explains all this. Great help.