* Besides defining the IVR zone membership, you can choose to specify a set of transit VSANs to provide connectivity between two edge VSANs:

+

* In addition to defining the IVR zone membership, you can choose to specify a set of transit VSANs to provide connectivity between two edge VSANs:

** If two edge VSANs in an IVR zone overlap, then a transit VSAN is not required (though not prohibited) to provide connectivity.

** If two edge VSANs in an IVR zone overlap, then a transit VSAN is not required (though not prohibited) to provide connectivity.

** If two edge VSANs in an IVR zone do not overlap, you may need one or more transit VSANs to provide connectivity. Two edge VSANs in an IVR zone will not overlap if IVR is not enabled on a switch that is a member of both the source and destination edge VSANs.

** If two edge VSANs in an IVR zone do not overlap, you may need one or more transit VSANs to provide connectivity. Two edge VSANs in an IVR zone will not overlap if IVR is not enabled on a switch that is a member of both the source and destination edge VSANs.

Line 48:

Line 48:

* Border switches require Cisco SAN-OS Release 1.3(1) or higher.

* Border switches require Cisco SAN-OS Release 1.3(1) or higher.

-

* A border switch must be a member of two or more VSANs.

* A border switch must be a member of two or more VSANs.

-

* A border switch that facilities IVR communications must be IVR enabled.

* A border switch that facilities IVR communications must be IVR enabled.

2. Select the <span style="font-style: normal">'''<font color="Black">CFS</font>'''</span> tab to verify that the Oper column is enabled and the Global column is enabled for CFS distribution. Check the LastResult column for the status of the last CFS action.

+

2. Click the <span style="font-style: normal">'''<font color="Black">CFS</font>'''</span> tab to verify that the Oper column is enabled and the Global column is enabled for CFS distribution. Check the LastResult column for the status of the last CFS action.

To use IVR, you must obtain the correct licenses for the IVR features you are using and install those licenses on every IVR-enabled switch in your fabric. '''Table 13-3 shows which license to purchase based on the IVR feature you are using and the module or chassis you have enabled IVR on.

+

To use IVR, you must obtain the correct licenses for the IVR features you are using and install those licenses on every IVR-enabled switch in your fabric. Table 13-3 shows which license to purchase based on the IVR feature you are using and the module or chassis you have enabled IVR on.

<div align="left">

<div align="left">

Line 448:

Line 446:

----

----

-

{{Note |If you are using IVR over FCIP and Fibre Channel, you need the ENTERPRISE_PKG as well as the appropriate SAN extension license as shown in '''Table 13-3'''.}}

+

{{Note |If you are using IVR over FCIP and Fibre Channel, you need the ENTERPRISE_PKG as well as the appropriate SAN extension license as shown in Table 13-3.}}

----

----

----

----

-

'''Tip: ''' Be sure to enter the correct chassis serial number when purchasing your license packages. Choose Switches > Hardware and check the SerialNo Primary for the switch chassis in Fabric Manager or use the show license host-id CLI command to obtain the chassis serial number for each switch that requires a license. Your license will not operate if the serial number used does not match the serial number of the chassis you are installing the license on.

+

'''Tip: ''' Be sure to enter the correct chassis serial number when purchasing your license packages. Choose '''Switches''' > '''Hardware''' and check the SerialNo Primary for the switch chassis in Fabric Manager or use the '''show license host-id''' CLI command to obtain the chassis serial number for each switch that requires a license. Your license will not operate if the serial number used does not match the serial number of the chassis you are installing the license on.

::'''Explanation''' Inter-VSAN zone set activation failed in the listed VSAN. This could be an intermittent, regular zone set activation error. The activation will be retried after the number of seconds listed in the message.

+

::'''Explanation''' Inter-VSAN zone set activation failed in the listed VSAN. This might be an intermittent, regular zone set activation error. The activation is retried after the number of seconds listed in the message.

::'''Recommended Action''' No action is required.

::'''Recommended Action''' No action is required.

-

:Introduced Cisco MDS SAN-OS Release 2.1(2).

+

+

:This message is introduced in Cisco MDS SAN-OS Release 2.1(2).

Line 542:

Line 541:

::'''Explanation''' Inter-VSAN zone set activation failed.

::'''Explanation''' Inter-VSAN zone set activation failed.

::'''Recommended Action''' No action is required.

::'''Recommended Action''' No action is required.

-

:Introduced Cisco MDS SAN-OS Release 1.3(1).

+

+

:This message is introduced in Cisco MDS SAN-OS Release 1.3(1).

Line 548:

Line 548:

::'''Explanation''' Inter-VSAN zone set activation failed in the VSAN.

::'''Explanation''' Inter-VSAN zone set activation failed in the VSAN.

::'''Recommended Action''' No action is required.

::'''Recommended Action''' No action is required.

-

: Introduced Cisco MDS SAN-OS Release 1.3(1).

+

+

:This message is introduced in Cisco MDS SAN-OS Release 1.3(1).

Line 554:

Line 555:

::'''Explanation''' Inter-VSAN zone set activation failed with VSAN shown in the error message. This could be an intermittent regular zone set activation error. The activation retried in the number of seconds shown in the error message.

::'''Explanation''' Inter-VSAN zone set activation failed with VSAN shown in the error message. This could be an intermittent regular zone set activation error. The activation retried in the number of seconds shown in the error message.

::'''Recommended Action''' No action is required.

::'''Recommended Action''' No action is required.

-

:Introduced Cisco MDS SAN-OS Release 1.3(3).

+

+

:This message is introduced in Cisco MDS SAN-OS Release 1.3(3).

Line 560:

Line 562:

::'''Explanation''' This switch does not have the lowest switch world wide name (sWWN) in the VSAN. Only the inter-VSAN (IVR) enabled switch with the lowest sWWN can add the IVR zones to the regular active zone set in a VSAN. This switch is waiting until the IVR switch with the lowest sWWN adds the IVR zone and reactivates the zone set.

::'''Explanation''' This switch does not have the lowest switch world wide name (sWWN) in the VSAN. Only the inter-VSAN (IVR) enabled switch with the lowest sWWN can add the IVR zones to the regular active zone set in a VSAN. This switch is waiting until the IVR switch with the lowest sWWN adds the IVR zone and reactivates the zone set.

::'''Recommended Action''' No action is required.

::'''Recommended Action''' No action is required.

-

:Introduced Cisco MDS SAN-OS Release 2.0(1b).

+

+

:This message is introduced in Cisco MDS SAN-OS Release 2.0(1b).

Line 596:

Line 599:

No active zone set.

No active zone set.

|

|

-

No zone set has been activated. See the '''"Troubleshooting Zone Set Activation"''' section to activate a zone set on an IVR-enabled switch, or use the <span style="font-style: normal">'''<font color="Black">force</font>'''</span> option when activating the IVR zone set.

+

No zone set has been activated. See the "Troubleshooting Zone Set Activation" section to activate a zone set on an IVR-enabled switch, or use the <span style="font-style: normal">'''<font color="Black">force</font>'''</span> option when activating the IVR zone set.

Or use the i<span style="font-style: normal">'''<font color="Black">vr virtual-fcdomain-add vsan-ranges </font>'''</span>CLI command to add existing and future virtual domains to the domain list for the selected VSANs.

+

Use the <span style="font-style: normal">'''<font color="Black">ivr virtual-fcdomain-add vsan-ranges </font>'''</span>CLI command to add existing and future virtual domains to the domain list for the selected VSANs.

One or more switches in the VSAN are not running Cisco MDS SAN-OS Release 2.1(1a) or later.

One or more switches in the VSAN are not running Cisco MDS SAN-OS Release 2.1(1a) or later.

|

|

-

Upgrade to the Cisco SAN-OS release required for the IVR features you want to use. See [#wp49702 TableÂ 13-1] and [ts_sw.html#wpxref37306 <span class="cXRef_Color" style="font-weight: normal">ChapterÂ 2, "Troubleshooting Installs, Upgrades, and Reboots."</span>]

+

Upgrade to the Cisco SAN-OS release required for the IVR features you want to use. See Table 13-1 and Chapter 2, "Troubleshooting Installs, Upgrades, and Reboots."

|}

|}

Line 782:

Line 785:

=== Host Does Not Have Write Access to Storage ===

=== Host Does Not Have Write Access to Storage ===

-

<span class="cBoldNormal">SymptomÂ Â Â </span> Host does not have write access to storage.

+

'''Symptom''' Host does not have write access to storage.

<div align="left">

<div align="left">

{| id="wp45602table45600" width="80%" border="1" cellpadding="3"

{| id="wp45602table45600" width="80%" border="1" cellpadding="3"

-

|+ TableÂ 13-12 Host Does Not Have Write Access to Storage

+

|+ '''Table 13-12 Host Does Not Have Write Access to Storage'''

|- align="left" valign="bottom"

|- align="left" valign="bottom"

! scope="col" |

! scope="col" |

Line 812:

Line 815:

IVR uses CFS to distribute the IVR configuration. If you enable IVR auto topology, it also uses CFS to distribute and update the IVR VSAN topology on all switches. In rare cases, you may encounter problems where CFS locks IVR so that you cannot modify the configuration.

IVR uses CFS to distribute the IVR configuration. If you enable IVR auto topology, it also uses CFS to distribute and update the IVR VSAN topology on all switches. In rare cases, you may encounter problems where CFS locks IVR so that you cannot modify the configuration.

Or use the <span style="font-style: normal">'''<font color="Black">show ivr pending-diff</font>'''</span> CLI command to determine if you have a pending configuration change. Use <span style="font-style: normal">'''<font color="Black">ivr commit </font>'''</span>to commit this change or i<span style="font-style: normal">'''<font color="Black">vr abort</font>'''</span> to discard the changes and free up the session lock. If you do not have pending configuration changes, use the <span style="font-style: normal">'''<font color="Black">clear ivr session</font>'''</span> CLI command to free the session lock.

+

Use the <span style="font-style: normal">'''<font color="Black">show ivr pending-diff</font>'''</span> CLI command to determine if you have a pending configuration change. Use <span style="font-style: normal">'''<font color="Black">ivr commit </font>'''</span>to commit this change or <span style="font-style: normal">'''<font color="Black">ivr abort</font>'''</span> to discard the changes and free up the session lock. If you do not have pending configuration changes, use the <span style="font-style: normal">'''<font color="Black">clear ivr session</font>'''</span> CLI command to free the session lock.

:'''Error Message''' IVR-2-CFS_PEER_LOST_WITHIN_SESSION: CFS peer with switch wwn [chars]was lost in the middle of an active CFS session. Abort the CFS session and reenter the configuration changes.

-

was lost in the middle of an active CFS session. Abort the CFS session and re-enter

+

::'''Explanation''' Due to port flaps (enable and disable of the VSAN), link outages, switch restarts and so on, a CFS peer switch of IVR was lost. The current configuration changes will not be applied to this peer until the peer merges with this switch. The CFS merge can fail if the configuration at the lost peer conflicts with the changes made in this session. Also, IVR auto topology could be out of sync with this peer. We recommend that you discard this CFS session using the '''ivr abort''' command and then reenter the configuration changes. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

-

the configuration changes.

+

::'''Recommended Action''' No action is required.

-

</span>

+

:: This message is introduced in Cisco MDS SAN-OS Release 2.0(1b).

-

<span class="cBoldNormal">ExplanationÂ Â Â </span> Due to port flaps (enable and disable of the VSAN), link outages, switch restarts and so on, a CFS peer switch of IVR was lost. The current configuration changes would not be applied to this peer until the peer merges with this switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made in this session. Also, IVR auto topology could be out of sync. with this peer. We recommend that you discard this CFS session using i'''vr abort''' command and then re-enter the configuration changes. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

::'''Explanation''' An error occurred while merging the configuration. The reason for the failure is shown in the error message.

+

::'''Recommended Action''' If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

<span class="cBoldNormal">ExplanationÂ Â Â </span> An error occurred while merging the configuration. The reason for the failure is shown in the error message.

+

-

+

-

<span class="cBoldNormal">Recommended ActionÂ Â Â </span> If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Reconfigure your fabric before merging to reduce the number of VSANs or topology entries. See Appendix C, "Configuration Limits for Cisco MDS SAN-OS Release 3.x."

|- align="left" valign="top"

|- align="left" valign="top"

|

|

Line 900:

Line 895:

Conflicting user-configured IVR VSAN topology database entries.

Conflicting user-configured IVR VSAN topology database entries.

|

|

-

Enable IVR auto topology on both fabrics before the merge and remove any user-configured IVR VSAN topology database entries.

+

Enable IVR auto-topology on both fabrics before the merge and remove any user-configured IVR VSAN topology database entries.

|}

|}

</div>

</div>

-

<br />

+

<br/>

== Troubleshooting the IVR Wizard ==

== Troubleshooting the IVR Wizard ==

-

The IVR wizard in Fabric Manager simplifies the process of configuring IVR across your fabric. The IVR wizard automatically checks for the appropriate Cisco SAN-OS version across the switches in the VSAN and determines which IVR features the switches are capable of. (See [#wp49702 TableÂ 13-1].)

+

The IVR wizard in Fabric Manager simplifies the process of configuring IVR across your fabric. The IVR wizard automatically checks for the appropriate Cisco SAN-OS version across the switches in the VSAN and determines which IVR features the switches are capable of. (See Table 13-1.)

This section describes the following warning or error dialog boxes that display when you configure IVR using the Fabric Manager IVR wizard:

This section describes the following warning or error dialog boxes that display when you configure IVR using the Fabric Manager IVR wizard:

+

* Warning: Not All Switches Are IVR NAT Capable or Are Unmanageable

+

* Error: The Following Switches Do Not Have Unique Domain IDs

+

* Error: Pending Action/ Pending Commits

+

* Error: Fabric Is Changing. Please Retry the Request Later

-

â¢[[Image:blank.gif]][#wp45941 Warning: Not All Switches Are IVR NAT Capable or Are Unmanageable]

+

=== Warning: Not All Switches are IVR NAT Capable or are Unmanageable ===

-

+

-

â¢[[Image:blank.gif]][#wp45916 Error: The Following Switches Do Not Have Unique Domain IDs]

=== Warning: Not All Switches Are IVR NAT Capable or Are Unmanageable ===

+

-

<span class="cBoldNormal">SymptomÂ Â Â </span> Warning: Not all switches are IVR NAT capable or are unmanageable.

+

'''Symptom''' Warning: Not all switches are IVR NAT capable or are unmanageable.

<div align="left">

<div align="left">

{| id="wp46004table46002" width="80%" border="1" cellpadding="3"

{| id="wp46004table46002" width="80%" border="1" cellpadding="3"

-

|+ TableÂ 13-15 Not All Switches Are IVR NAT Capable or Are Unmanageable

+

|+ '''Table 13-15 Not All Switches are IVR NAT Capable or are Unmanageable'''

|- align="left" valign="bottom"

|- align="left" valign="bottom"

! scope="col" |

! scope="col" |

Line 942:

Line 933:

One or more switches in the fabric are not running Cisco MDS SAN-OS Release 2.1(1a) or later.

One or more switches in the fabric are not running Cisco MDS SAN-OS Release 2.1(1a) or later.

|

|

-

Upgrade to the Cisco SAN-OS release required for the IVR features you want to use. See [#wp49702 TableÂ 13-1] and [ts_sw.html#wpxref37306 <span class="cXRef_Color" style="font-weight: normal">ChapterÂ 2, "Troubleshooting Installs, Upgrades, and Reboots."</span>]

+

Upgrade to the Cisco SAN-OS release required for the IVR features you want to use. See Table 13-1 and Chapter 2, "Troubleshooting Installs, Upgrades, and Reboots."

|- align="left" valign="top"

|- align="left" valign="top"

|

|

Line 956:

Line 947:

=== Error: The Following Switches Do Not Have Unique Domain IDs ===

=== Error: The Following Switches Do Not Have Unique Domain IDs ===

-

<span class="cBoldNormal">SymptomÂ Â Â </span> The following switches do not have unique domain IDs.

+

'''Symptom''' The following switches do not have unique domain IDs.

<div align="left">

<div align="left">

{| id="wp46250table46248" width="80%" border="1" cellpadding="3"

{| id="wp46250table46248" width="80%" border="1" cellpadding="3"

-

|+ TableÂ 13-16 The Following Switches Do Not Have Unique Domain IDs

+

|+ '''Table 13-16 The Following Switches Do Not Have Unique Domain IDs'''

Troubleshooting IVR

This chapter describes how to troubleshoot and resolve inter-VSAN routing (IVR) configuration issues in the Cisco MDS 9000 Family of multilayer directors and fabric switches. It includes the following sections:

Prior to Cisco MDS SAN-OS Release 2.1(1a), IVR required unique domain IDs for all switches in the fabric. As of Cisco MDS SAN-OS Release 2.1(1a), you can enable IVR Network Address Translation (NAT) to allow non-unique domain IDs. This feature simplifies the deployment of IVR in an existing fabric where non-unique domain IDs might be present.

Note:

By default, IVR-NAT is not enabled.

Configuration Guidelines

This section provides guidelines for configuring components that can affect IVR, and includes the following topics:

Transit VSANs

Border Switches

Transit VSANs

Follow these guidelines when configuring transit VSANs:

In addition to defining the IVR zone membership, you can choose to specify a set of transit VSANs to provide connectivity between two edge VSANs:

If two edge VSANs in an IVR zone overlap, then a transit VSAN is not required (though not prohibited) to provide connectivity.

If two edge VSANs in an IVR zone do not overlap, you may need one or more transit VSANs to provide connectivity. Two edge VSANs in an IVR zone will not overlap if IVR is not enabled on a switch that is a member of both the source and destination edge VSANs.

Traffic between the edge VSANs traverses only the shortest IVR path.

Transit VSAN information is common to all IVR zones. Sometimes a transit VSAN can also be an edge VSAN in another IVR zone.

Border Switches

Always follow these guidelines when configuring border switches:

Border switches require Cisco SAN-OS Release 1.3(1) or higher.

A border switch must be a member of two or more VSANs.

A border switch that facilities IVR communications must be IVR enabled.

IVR Issues

This section describes the problems associated with IVR. This section includes the following topics:

IVR Licensing Issues

Cannot Enable IVR

IVR Network Address Translation Fails

IVR Zone Set Activation Fails

Border Switch Fails

Traffic Does Not Traverse IVR Path

Link Isolated

Persistent FC ID for IVR Failed

LUN Configuration Failure in IVR Zoning

Host Does Not Have Write Access to Storage

Locked IVR CFS Session

CFS Merge Failed

IVR Licensing Issues

To use IVR, you must obtain the correct licenses for the IVR features you are using and install those licenses on every IVR-enabled switch in your fabric. Table 13-3 shows which license to purchase based on the IVR feature you are using and the module or chassis you have enabled IVR on.

Table 13-3 License Requirements for IVR

IVR Feature

Chassis or Module Type

License Required

Number of Licenses

IVR over Fibre Channel and IVR NAT over Fibre Channel

All

ENTERPRISE_PKG

One per IVR-enabled chassis

IVR over FCIP

MDS 9216i 1

None

None

MPS-14/2

SAN_EXTN_OVER_IPS2

One per module running IVR over FCIP

MPS-18/4 or MPS-18/4 FIPS

SAN_EXTN_OVER_MPS_184_FIPS

IPS-8

SAN_EXTN_OVER_IP

IPS-4

SAN_EXTN_OVER_IPS4

1Cisco MDS 9216i enables the SAN_EXTENSION features without a license for the two Gigabit Ethernet ports on the integrated supervisor card.

Note:

If you are using IVR over FCIP and Fibre Channel, you need the ENTERPRISE_PKG as well as the appropriate SAN extension license as shown in Table 13-3.

Tip: Be sure to enter the correct chassis serial number when purchasing your license packages. Choose Switches > Hardware and check the SerialNo Primary for the switch chassis in Fabric Manager or use the show license host-id CLI command to obtain the chassis serial number for each switch that requires a license. Your license will not operate if the serial number used does not match the serial number of the chassis you are installing the license on.

Cannot Enable IVR

Purchase and install the appropriate licenses. See the "IVR Licensing Issues" section.

Switch not running Cisco SAN-OS Release 1.3(1) or later.

Upgrade to the Cisco SAN-OS release required for the IVR features you want to use. See Table 13-1 and Chapter 2, "Troubleshooting Installs, Upgrades, and Reboots."

Using IVR auto topology but CFS distribution is not enabled.

Choose Fabricxx > All VSANs > IVR, set the Global drop-down menu to enable, and click Apply Changes in Fabric Manager. Or use the ivr distribute CLI command before enabling IVR.

IVR Network Address Translation Fails

Symptom IVR NAT fails.

Table 13-5 IVR NAT Fails

Symptom

Possible Cause

Solution

IVR NAT fails.

Internal message payload uses destination ID.

IVR NAT modifies the destination ID in the Fibre Channel header. If this same destination ID appears inside the message payload, Cisco SAN-OS may not detect it and IVR NAT fails. Disable IVR NAT and ensure that all domain IDs are unique. Refer to the Cisco MDS 9000 Family configuration guides at the following website for a list of payloads that work with IVR NAT when the payload includes the destination ID:

Explanation Inter-VSAN zone set activation failed in the listed VSAN. This might be an intermittent, regular zone set activation error. The activation is retried after the number of seconds listed in the message.

Explanation Inter-VSAN zone set activation failed with VSAN shown in the error message. This could be an intermittent regular zone set activation error. The activation retried in the number of seconds shown in the error message.

Explanation This switch does not have the lowest switch world wide name (sWWN) in the VSAN. Only the inter-VSAN (IVR) enabled switch with the lowest sWWN can add the IVR zones to the regular active zone set in a VSAN. This switch is waiting until the IVR switch with the lowest sWWN adds the IVR zone and reactivates the zone set.

Recommended Action No action is required.

This message is introduced in Cisco MDS SAN-OS Release 2.0(1b).

Symptom IVR zone set activation fails.

Table 13-6 IVR Activation Fails

Symptom

Possible Cause

Solution

IVR zone set activation fails.

Overlapping domain IDs.

Use static domain IDs to assign unique domain IDs to each switch in the VSAN or use IVR NAT. Choose Fabricxx > All VSANs > Domain Manager in Fabric Manager or use the fcdomaindomaindomain-id [static | preferred]vsanvsan-id CLI command

Default zone policy is permit.

Choose Zone > IVR > Edit Local Full Zone Database in Fabric Manager. Right-click the IVR zone set that you want to activate and select Activate. Check the Create Active Zone Set if none Present check box or use the force option with the ivr zoneset activate CLI command.

Default zone policy is deny and no active zone set present.

No active zone set.

No zone set has been activated. See the "Troubleshooting Zone Set Activation" section to activate a zone set on an IVR-enabled switch, or use the force option when activating the IVR zone set.

Border Switch Fails

If an IVR-enabled switch fails, you must update the IVR topology to reflect this change if you are not using auto topology.

Use the ivr vsan topology auto CLI command to automatically reconfigure the IVR topology, or use the ivr vsan topology database CLI command to manually reconfigure the IVR topology.

Traffic Does Not Traverse IVR Path

Symptom Traffic does not traverse the IVR path.

Table 13-8 Traffic Does Not Traverse IVR Path

Symptom

Possible Cause

Solution

Traffic does not traverse the IVR path.

Fabric includes an SN5428 or MDS 9020 switch and you have not added the IVR virtual domains to the remote VSAN domain lists.

Choose Fabricxx > All VSANs > IVR and click the Action tab in Fabric Manager. Fill in the Create Virtual Domains for VSAN field and click Apply Changes. Click the CFS tab, and set ConfigAction to commit, and click Apply Changes.

Use the ivr virtual-fcdomain-add vsan-ranges CLI command to add existing and future virtual domains to the domain list for the selected VSANs.

Repeat this on all edge VSANs.

Internal message payload uses destination ID.

See the "IVR Network Address Translation Fails" section.

Devices are in different IVR service groups.

Verify the IVR service groups. Choose Fabricxx > All VSANs > IVR and click the Service Group tab in Fabric Manager.

Use the show ivr service-group CLI command.

Move the VSANs into the same IVR service group. Choose Fabricxx > All VSANs > IVR and click the Service Group tab in Fabric Manager.

Use the ivr service-group activate CLI command to activate this change. If CFS is enabled, use the ivr commit CLI command to commit this change.

Choose Fabricxx > All VSANs > IVR and click the Action tab in Fabric Manager.Fill in the Create Virtual Domains for VSAN field and click Apply Changes. Click the CFS tab and set ConfigAction to commit, and click Apply Changes.

Use the show fcdomain domain-list CLI command to verify a domain overlap. Use the ivr widthdraw domain CLI command to remove the overlapped domain. Use persistent FC IDs to reassign the overlapped domain. Use the ivr virtual-fcdomain-add vsan-ranges CLI command to add existing and future virtual domains to the domain list for the selected VSANs.

Repeat this on all edge VSANs.

Internal message payload uses destination ID.

See the "IVR Network Address Translation Fails" section.

Persistent FC ID for IVR Failed

Symptom Persistent FC ID for IVR failed.

Table 13-10 Persistent FC ID for IVR Failed

Symptom

Possible Cause

Solution

Persistent FC ID for IVR failed.

Selected virtual FC ID does not match the assigned virtual domain.

Use the show ivr fcdomain database CLI command to verify the virtual domain ID. Use the native-autonomous-fabric-num CLI command to assign the virtual domain and then use the pwwn CLI command to map the pWWN to an appropriate FC ID that matches the virtual domain ID.

Refer to the Cisco MDS 9000 Family configuration guides for the related procedure to configure Persistent FC IDs for IVR.

LUN Configuration Failure in IVR Zoning

Symptom LUN configuration failed in IVR zoning.

Table 13-11 LUN Configuration Failure in IVR Zoning

Symptom

Possible Cause

Solution

LUN configuration failed in IVR zoning.

One or more switches in the VSAN are not running Cisco MDS SAN-OS Release 2.1(1a) or later.

Upgrade to the Cisco SAN-OS release required for the IVR features you want to use. See Table 13-1 and Chapter 2, "Troubleshooting Installs, Upgrades, and Reboots."

Host Does Not Have Write Access to Storage

Symptom Host does not have write access to storage.

Table 13-12 Host Does Not Have Write Access to Storage

Symptom

Possible Cause

Solution

Host does not have write access to storage.

Host is a member of a read-only zone.

If a host is a member of a read-only zone, the host has no write access to any IVR zone it may be a member of. Remove the host from the read-only zone.

Locked IVR CFS Session

IVR uses CFS to distribute the IVR configuration. If you enable IVR auto topology, it also uses CFS to distribute and update the IVR VSAN topology on all switches. In rare cases, you may encounter problems where CFS locks IVR so that you cannot modify the configuration.

Symptom Locked IVR CFS session.

Table 13-13 Locked IVR CFS Session

Symptom

Possible Cause

Solution

Locked IVR CFS session.

CFS did not give up the session lock for IVR after the last commit or an IVR configuration change is pending and has not been committed.

Choose Fabricxx > All VSANs > IVR and click the CFS tab in Fabric Manager. Set the ConfigView As drop-down menu to pending and verify the pending configuration changes. Set the ConfigAction drop-down menu to commit to save these changes, abort to discard the changes, or clear to clear the session lock.Click Apply Changes.

Use the show ivr pending-diff CLI command to determine if you have a pending configuration change. Use ivr commit to commit this change or ivr abort to discard the changes and free up the session lock. If you do not have pending configuration changes, use the clear ivr session CLI command to free the session lock.

CFS Merge Failed

If a CFS merge fails, you may see the following system messages:

Error Message IVR-2-CFS_PEER_LOST_WITHIN_SESSION: CFS peer with switch wwn [chars]was lost in the middle of an active CFS session. Abort the CFS session and reenter the configuration changes.

Explanation Due to port flaps (enable and disable of the VSAN), link outages, switch restarts and so on, a CFS peer switch of IVR was lost. The current configuration changes will not be applied to this peer until the peer merges with this switch. The CFS merge can fail if the configuration at the lost peer conflicts with the changes made in this session. Also, IVR auto topology could be out of sync with this peer. We recommend that you discard this CFS session using the ivr abort command and then reenter the configuration changes. You can alternatively use Fabric Manager and/or Device Manager instead of the command line method.

Recommended Action No action is required.

This message is introduced in Cisco MDS SAN-OS Release 2.0(1b).

Error Message IVR-3-MERGE_FAILED: [chars].

Explanation An error occurred while merging the configuration. The reason for the failure is shown in the error message.

Recommended Action If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco Systems, contact Cisco Technical Support.

Use either the ivr vsan topology auto CLI command to automatically reconfigure the IVR topology, or the ivr vsan topology database CLI command to manually reconfigure the IVR topology.

Maximum number of VSANs or IVR VSAN topology entries reached.

Reconfigure your fabric before merging to reduce the number of VSANs or topology entries. See Appendix C, "Configuration Limits for Cisco MDS SAN-OS Release 3.x."

Conflicting entries in the AFID database.

Modify the conflicting entries in the AFID database.

Conflicting user-configured IVR VSAN topology database entries.

Enable IVR auto-topology on both fabrics before the merge and remove any user-configured IVR VSAN topology database entries.

Troubleshooting the IVR Wizard

The IVR wizard in Fabric Manager simplifies the process of configuring IVR across your fabric. The IVR wizard automatically checks for the appropriate Cisco SAN-OS version across the switches in the VSAN and determines which IVR features the switches are capable of. (See Table 13-1.)

This section describes the following warning or error dialog boxes that display when you configure IVR using the Fabric Manager IVR wizard:

Warning: Not All Switches Are IVR NAT Capable or Are Unmanageable

Error: The Following Switches Do Not Have Unique Domain IDs

Error: Pending Action/ Pending Commits

Error: Fabric Is Changing. Please Retry the Request Later

Warning: Not All Switches are IVR NAT Capable or are Unmanageable

Symptom Warning: Not all switches are IVR NAT capable or are unmanageable.

Table 13-15 Not All Switches are IVR NAT Capable or are Unmanageable

Symptom

Possible Cause

Solution

Warning: Not all switches are IVR NAT capable or are unmanageable.

One or more switches in the fabric are not running Cisco MDS SAN-OS Release 2.1(1a) or later.

Upgrade to the Cisco SAN-OS release required for the IVR features you want to use. See Table 13-1 and Chapter 2, "Troubleshooting Installs, Upgrades, and Reboots."

One or more switches in the fabric cannot communicate with Fabric Manager or are not Cisco SAN-OS switches.

Determine if any of the problem switches are required in the IVR topology. If not, ignore this message and proceed with the IVR configuration. If they are required, choose Switches and check the Status column to determine the cause and address the problem.

Error: The Following Switches Do Not Have Unique Domain IDs

Symptom The following switches do not have unique domain IDs.

Table 13-16 The Following Switches Do Not Have Unique Domain IDs

Symptom

Possible Cause

Solution

The following switches do not have unique domain IDs.

The listed switches have duplicate domain IDs in two or more VSANs in your proposed IVR configuration.

Choose Fabricxx > All VSANS > Domain Manager and set the ConfigDomainId to a unique number and set the Config Type drop-down menu to static in Fabric Manager. Set the Restart drop-down menu to disruptive and click Apply Changes. This triggers a disruptive restart to make the running domain ID match the configured domain ID.

Use IVR NAT. This may require upgrading to Cisco MDS SAN-OS Release 2.1(1a) or later.

Error: Pending Action/ Pending Commits

Symptom Pending action on pending commit error displays.

Table 13-17 Pending Action/Pending Commits

Symptom

Possible Cause

Solution

Pending action on pending commit error displays.

A separate IVR configuration change that was not committed.

IVR has pending changes that were not committed. Choose Fabricxx > All VSANS > IVR and click the CFS tab in Fabric Manager. Set the View Config As drop-down menu to pending and verify the pending configuration changes. Set the ConfigAction drop-down menu to commit to save these changes or abort to discard the changes. Click Apply Changes.

The IVR CFS session was not unlocked after the last commit.

Choose Fabricxx > All VSANS > IVR and click the CFS tab in Fabric Manager. Set the ConfigAction drop-down menu to clear to remove the session lock. Click Apply Changes.

Error: Fabric Is Changing. Please Retry the Request Later

This error may occur if there are different versions of Cisco SAN-OS on the IVR-enabled switches. You should upgrade all IVR-enabled switches to the same version of Cisco SAN-OS.