UNSOLVED

dynamox

updated

14 years ago

D

dynamox

11 Legend

•

20419 Posts

•

87439 Points

0

1965

January 3rd, 2013 13:00

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

    6 Operator

    •

    5739 Posts

    574

    0

    Posted 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

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    574

    0

    Posted 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

    6 Operator

    •

    5739 Posts

    574

    0

    Posted 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

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    574

    0

    Posted January 7th, 2013 04:00

    show ivr | inc NAT

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    574

    0

    Posted January 7th, 2013 04:00

    you need IVR-NAT when VSANs have the same domain id

  • RRR

    6 Operator

    •

    5739 Posts

    574

    0

    Posted January 7th, 2013 12:00

    right. Thanks. I'll run this on my MDS 92xx switches

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    574

    0

    Posted 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

    6 Operator

    •

    5739 Posts

    574

    0

    Posted January 8th, 2013 05:00

    Aha, I'm not using it right now.

    Thanks for warning me about this

  • 574

    0

    Posted 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

    6 Operator

    •

    5739 Posts

    169

    0

    Posted 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.