In a complex network topology, you might only have a few IVR-enabled VSANs. To reduce the amount of traffic to non-IVR-enabled VSANs, you can configure service groups that restrict the traffic to the IVR-enabled VSANs. A maximum of 16 IVR service groups are allowed in a network. When a new IVR-enabled switch is added to the network, you must update the service groups to include the new VSANs.
When configuring IVR service groups, consider these guidelines:
If you use service groups with IVR auto topology mode, you should enable IVR and configure your service groups first, then distribute them with CFS before setting the IVR auto topology mode.
The CFS distribution is restricted within the service group only when the IVR VSAN topology is in IVR auto topology mode.
You can configure as many as 16 service groups in a network.
When a new IVR-enabled switch is added to the network, you must update the service group to include the new VSANs.
The same VSAN and AFID combination cannot be a member of more than one service group, otherwise, a CFS merge will fail.
The total number of AFID and VSAN combinations in all the service groups combined cannot exceed 128. The maximum number of AFID and VSAN combinations in a single service group is 128.
The IVR service group configuration is distributed in all IVR-enabled switches. IVR data traffic between two end devices belonging to a service group stays within that service group. For example, two members (for example, pWWN 1 and pWWN 2) cannot communicate if they belong to the same IVR zone and they belong to different service groups.
During a CFS merge, service groups with the same name would be merged, as long as there are no conflicts with other service groups.
If the total number of service groups exceeds 16 during a CFS merge, the CFS merge fails.
CFS distributes service group configuration information to all reachable SANs. If you do not enable CFS distribution, you must ensure that the service group configuration is the same on all IVR-enabled switches in all VSANs.
IVR end devices belonging to an IVR service group are not exported to any AFID or VSAN outside of its service group.
When at least one service group is defined and an IVR zone member does not belong to the service group, that IVR zone member is not able to communicate with any other device.
All AFID and VSAN combinations that are part of an IVR VSAN topology but are not part of any user-defined service group are members of the default service group. The identifier of the default service group is 0.
By default, IVR communication is permitted between members of the default service group. You can change the default policy to deny. The default policy is not part of ASCII configuration.
Service Group Activation
A configured service group must be activated. Like zone set activation or VSAN topology activation, the activation of a configured service group replaces the currently active service group, if any, with the configured one. There is only one configured service group database and one active service group database. Each of these databases can have up to 16 service groups.
Cisco Nexus 7000 Series.
IVR requires the FCoE license for each F-series module. FCoE enabled in a storage VDC does not require the Advanced Services License.
IVR also requires the Storage Enterprise License.
For a complete explanation of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.
Guidelines and Limitations
IVR has the following guidelines and limitations:
All border switches in the fabric must be Cisco SAN switches. Other switches in the fabric can be non-Cisco switches.
IVR must be enabled in the storage VDC.
Not added to virtual domains
QoS for IVR Zones
Configuring a Service Group
1.ivr service-group namegroup-name
4.ivr service-group activate[default-sg-deny]
Command or Action
ivr service-group namegroup-name
switch(config)# ivr service-group name IVR-SG1
Configures the IVR service group and enters IVR server group configuration mode.