issues creating IVR zones in MDS 9710

[Gilberto Marcos]

Hello I hope some one can help.

We have several MDS switches in a customer network, recently they had to add more IVR zones, but when the customer try to add one new IVR zone

SAN12(config)# ivr zone name
IVR_mxoccsapcwd01_fcs2_new_MXOCCSTGSV1_SV2_N1P7_N2P14
Fabric is changing. Please retry the request later

We have check and we don't see any lock in the fabric.

Have someone has faced this issue?

Regards

[Bhavin Yadav]

Hi Gilberto,
Few things you can do but I would recommend opening Cisco TAC case for deeper troubleshooting on IVR.
This issue could be anything – past IVR / zoning config issues, or any other config issues. Following commands may help:

Check for any cfs or zoning locks: show cfs lock Show zone status | i VSAN|session
(session: none) means there are no zone locks Resolve any lock issues if they exist.

Option one: Configure ivr on new switch:
feature ivr
ivr nat
ivr distribute

Option two: Remove switch from the ivr config
ivr vsan-topology database no autonomous-fabric-id switch-wwn vsan-ranges
ivr vsan-topology activate
ivr commit

The above may help but otherwise, Cisco TAC is your best bet.

[Gilberto Marcos]

Hello Bhavin.

Thank you for your answer. Right now the MDS device don't have PSS support. The Customer project manager is working on that.

We have a troubleshooting session and we were able to notice the following trying to commit the ivr changes on the devices.

MXOCCSAN02(config)# sh ivr session status

Last Action Time Stamp     : Wed Dec  1 13:29:10 2021

Last Action                : Commit

Last Action Result         : Fail

Last Action Failure Reason : cfs(0x40b3002b)- Lock failed

MXOCCSAN04(config)# sh ivr session status

Last Action Time Stamp     : Wed Dec  1 13:10:13 2021

Last Action                : Commit

Last Action Result         : Fail

Last Action Failure Reason : cfs(0x40b3002b)- Lock failed

MXOCCSAN12(config)# sh ivr session status

Last Action Time Stamp     : Wed Dec  1 11:29:32 2021

Last Action                : Commit

Last Action Result         : Success

Last Action Failure Reason : none

Also we are trying to upgrade the MDS, but when checking for the instal all impact we got the following:

Notifying services about system upgrade.                                                                                    [#                   ]   0% -- FAIL.
Service "zone" returned error: Zone change in progress, ISSU rejected. (0x402000EF)

Pre-upgrade check failed. Return code 0x402000EF (Zone change in progress, ISSU rejected.).

We try to find the lock trough the fabric and we did not find anything.

Have you face something like that?

Regards