Unsolved
This post is more than 5 years old
2 Intern
•
20.4K Posts
0
1648
IVR-NAT conversion
Hello folks,
i need to upgrade my 9513 and 9222i to 5.2.6a from 4.2.7d. As i am looking at the release notes i will first need to upgrade to 5.0.8 and then to 5.2.6a.
One caveat that i see is that we currently use IVR without IVR-NAT and this configuration is no longer supported in 5.2.x. Release notes provide the commands to migrate to IVR-NAT mode that seem to be relatively simple. I understand that this will require an outage.
Has anyone done this recently, any pitfalls ? Did your IVR topology, zones stay intact ?
Thanks
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
January 4th, 2013 05:00
Interesting question you've got there, Mr D!
In what version is IVR NAT not supported anymore?
We're already running on 5.0(4) and we're going to 5.2(6a/8), so we might have the same issue then.....
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 4th, 2013 06:00
If you are using IVR-NAT today you are ok but if you are not then you will need to conver to IVR-NAT first before you upgrade to 5.2.x
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
January 7th, 2013 02:00
IVR NAT was needed when you wanted to zone 2 nodes in VSANs with the same VSAN number, right? I don't recall ever having to configure this.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 7th, 2013 04:00
show ivr | inc NAT
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 7th, 2013 04:00
you need IVR-NAT when VSANs have the same domain id
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
January 7th, 2013 12:00
right. Thanks. I'll run this on my MDS 92xx switches![](https://prod-care-community-cdn.sprinklr.com/community/687062f5-603c-4f5f-ab9d-31aa7cacb376/ReIVRNATconversion-4c36a6d0-47df-4632-a9c3-1718b6145f5c-1712163707)
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 8th, 2013 05:00
sorry but you are in the same boat as i am, have to schedule an outage to convert to IVR-NAT before you upgrade to 5.2.x . I am working with my customer on scheduling a good time (obviously will do one fabric at a time), when did you plan on upgrading ?
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
January 8th, 2013 05:00
Aha, I'm not using it right now.
Thanks for warning me about this![](https://prod-care-community-cdn.sprinklr.com/community/687062f5-603c-4f5f-ab9d-31aa7cacb376/ReIVRNATconversion-35764f92-693b-41d8-ab57-80ba714817a8-1712163707)
ScottHolmanColt
19 Posts
0
January 30th, 2013 00:00
Did you ever complete the IVR to IVR-NAT conversion? Was it as simple as following the steps in the release note?
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
January 30th, 2013 01:00
We're still planning, but we're now evaluating the risks. Will it really only be a short disruption without any reconfiguration or do we need to reconfigure zones after IVR NAT is enabled?
I found these steps:
If you are using IVR non-NAT mode, migrate to IVR-NAT mode before you upgrade to NX-OS
Release 5.2(1). IVR non-NAT mode is deprecated in NX-OS Release 5.2(1).
Note In dual SAN fabrics, IVR traffic can use one fabric while the other fabric is migrating. Only
IVR traffic is disrupted during the migration. Regular traffic within the VSAN is not
disrupted during the migration.
To migrate to IVR-NAT mode, follow these steps:
1. Stop or divert all applications on servers that depend on IVR.
– If CFS distribution is not enabled for IVR, then perform steps 2 through 4 on all switches where IVR is enabled.
– If CFS distribution is enabled for IVR, then enter the ivr commit command following step 2, step 3, and step 4 to distribute the changes to other switches.
2. Deactivate the IVR zone set by entering the no ivr zoneset activate command.
3. Enable IVR NAT by entering the ivr nat command.
4. Activate the IVR zone set by entering the ivr zoneset activate command.
5. Start or reestablish all application that were stopped in step 1.
17
The network can now run in IVR-NAT mode.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 30th, 2013 03:00
Scott,
going to do it in 3 weeks, will come back with results
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
February 15th, 2013 04:00
3 Weeks from Jan 30 is about next weekend. When will you be upgrading, D?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
February 15th, 2013 04:00
business pushed back, doing the IVR part next Friday
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
February 15th, 2013 05:00
Keep us informed!
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
February 22nd, 2013 19:00
ok, just finished the process, steps i followed:
After, as you can see one RDF port dropped
5. Enable IVR "ivr nat"
6. Commit "ivr commit"
7. Verify IVR NAT is enabled "sh ivr | grep NAT", output should look like this:
8. Activate IVR zoneset, i had to specify force otherwise it would not activate "ivr zoneset activate name IVR-A force"
9. Commit "ivr commit"
10. Verify IVR zoneset is active "sh ivr zoneset active", run it on all switches that participate in IVR topology.
11. Verify RDF is back
All looks good, "copy run start". Grab a beer/wine/non-alcoholic beverage![](https://prod-care-community-cdn.sprinklr.com/community/687062f5-603c-4f5f-ab9d-31aa7cacb376/ReIVRNATconversion-cb8fd902-2cf2-4e92-bc21-d8c7eaa76d7a-1712163707)