IVR-NAT conversion

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

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

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.

show ivr | inc NAT

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

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

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 ?

Aha, I'm not using it right now.

Thanks for warning me about this

Did you ever complete the IVR to IVR-NAT conversion? Was it as simple as following the steps in the release note?

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.

Scott,

going to do it in 3 weeks, will come back with results

3 Weeks from Jan 30 is about next weekend. When will you be upgrading, D?

business pushed back, doing the IVR part next Friday

Keep us informed!

ok, just finished the process, steps i followed:

1. backup IVR zoneset to TFTP server
2. Deactivate IVR zoneset: "no ivr zoneset activate"
3. Commit: "ivr commit"
4. At this point i would stopped and see what was going one, here are my RDF groups before and after commit

$ symcfg list -sid 1234 -RA ALL
Symmetrix ID: 00000000001234
                 S Y M M E T R I X    R D F    D I R E C T O R S                
                                         Remote        Local    Remote        
Ident  Symb  Num  Slot  Type       Attr  SymmID        RA Grp   RA Grp  Status
RF-7H   07H  119     7  RDF-R1       -   000123456789  11 (0A)  11 (0A) Online
RF-10H  10H  122    10  RDF-R1       -   000123456789  11 (0A)  11 (0A) Online
Legend for Connection Status:
(X) : Fibre Port is Connected to a Fibre Port (HBA, Switch or RF Director)
 : Fibre Port is Not Connected.

After, as you can see one RDF port dropped

$ symcfg list -sid 1234 -RA ALL
Symmetrix ID: 0000000001234
                 S Y M M E T R I X    R D F    D I R E C T O R S                
                                         Remote        Local    Remote        
Ident  Symb  Num  Slot  Type       Attr  SymmID        RA Grp   RA Grp  Status
RF-7H   07H  119     7  RDF-BI-DIR   -   -             11 (0A)   -      Online
RF-10H  10H  122    10  RDF-R1       -   000123456789  11 (0A)  11 (0A) Online
Legend for Connection Status:
(X) : Fibre Port is Connected to a Fibre Port (HBA, Switch or RF Director)
 : Fibre Port is Not Connected.

5. Enable IVR "ivr nat"

6. Commit "ivr commit"

7. Verify IVR NAT is enabled "sh ivr | grep NAT", output should look like this:

9513a(config)# sh ivr |grep NAT
Inter-VSAN NAT mode status
FCID-NAT is enabled

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

$ symcfg list -sid 1234 -RA ALL
Symmetrix ID: 00000000001234
                 S Y M M E T R I X    R D F    D I R E C T O R S                
                                         Remote        Local    Remote        
Ident  Symb  Num  Slot  Type       Attr  SymmID        RA Grp   RA Grp  Status
RF-7H   07H  119     7  RDF-R1       -   000123456789  11 (0A)  11 (0A) Online
RF-10H  10H  122    10  RDF-R1       -   000123456789  11 (0A)  11 (0A) Online
Legend for Connection Status:
(X) : Fibre Port is Connected to a Fibre Port (HBA, Switch or RF Director)
 : Fibre Port is Not Connected.

All looks good, "copy run start". Grab a beer/wine/non-alcoholic beverage