Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Migrating to IP from SNA

We have the following network set-up:

Remote Mainframe -- 3745 -- 64K Leased Line -- 3720 -- Central Mainframe

The traffic between the Remote Mainframe and the Central Mainframe is SNA.

The Central Mainframe also has a CIP connection to a Cisco 7507.

We would like to decommission the 3720, and migrate from SNA to IP. What options do we have for achieving this objective?

We would appreciate URLs giving network design scenarios and sample configurations for achieving this SNA to IP migration, in addition to your suggestions.

Thanks in advance for your help.

  • Server Networking
2 REPLIES
Silver

Re: Migrating to IP from SNA

I am not fully understand your question. When you says that migrating from SNA to IP, do you mean to run IP on the mainframe? Or do you want to replace the 64K leased line by an IP network.

In general, there are two main choices.

1. Use either SNI or subarea routing

Replace the 3720 by one of 3745, OSA, or CIP. Then, go to the following for different scenarios:

http://www.cisco.com/warp/public/697/fep.html

2. SNASw and APPN

You may have to implement this option some time in the future because I heard a rumor that IBM has stopped selling 3745.

Again, replace the 3720 by one of 3745, OSA, and CIP. You enable APPN on both mainframes. Set up an ISA or RTP connection between the mainframes. You can also set up SNASw on a router between the mainframes. There are too many possibilities. Check out the following URL on SNASw designs:

http://www.cisco.com/warp/public/cc/pd/ibsw/snasw/tech/

New Member

Re: Migrating to IP from SNA

Hi Ayaz,

You have a couple of choices. DLSw+ to provide IP transport in the network, while still using layer 2 SNA protocols in the Mainframes, or add a CIP to the remote Mainframe and use Enterprise Extender for end to end IP.

A good llink for the first choice is;

http://www.cisco.com/warp/customer/697/fep.html

For the second option, all of the configuration is done in the Mainframes. The network only handles IP data. You can add a CIP (or CPA) to the remote Mainframe, the CIPs may use either CLAW or CMPC+ protocols, and do not need to know that SNA is being transported. Try this link for a sample of most of the Mainframe definitions;

http://www.cisco.com/warp/customer/100/snasw.html

There is also an IBM redbook that (although it contains some obsolete information) covers this;

http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg245957.html

352
Views
0
Helpful
2
Replies