dlsw/snasw/cip config in one router

[xh_liu]

my request is:

remote site use dlsw connect to datacenter,

and datacenter router config dlsw/snasw/cip only use one router which connect to 2 ibm host by 2 cip port technology.

who can give me a config example about the datacenter router by above request?

many thanks.

[dmccullo]

The hard part of answering is guessing what form of SNASw upstream connectivity you want to use. The most common connectivity is EE - HPR/IP, and for that IP path to route over ethernet from the DLSw+/SNASw router through a layer 3 Cat6k to an OSA interface on a mainframe. A CIP (or CPA) can be used instead for this upstream path, and then the question would be whether to use CMPC+ or CLAW for the channel protocol. I would suggest CLAW if the traffic is primarily interactive, and CMPC+ if it is batch. Alternatively, you could use LLC for upstream connectivity, using the CSNA channel protocol. I don't have complete configurations for each of these variations, but you should be able to paste together a good configuration from the samples at this link. http://cisco.com/en/US/partner/tech/tk331/tk336/tech_digest09186a0080091af1.html

Please let us know if you need more information.

Best regards, Dan

[xh_liu]

yes, here is use CSNA.

The final config like this:

!

source-bridge ring-group 999

dlsw local-peer peer-id x.x.x.x promiscuous

dlsw icannotreach sap F0

!

!

interface Loopback0

ip address x.x.x.x 255.255.255.255

!

!

interface Channel1/0

no ip address

no keepalive

csna 0130 00

csna 0140 02

lan TokenRing 18

source-bridge 18 1 999

adapter 25 4000.7206.0025

adapter 29 4000.7206.0029

!

interface Channel2/0

no ip address

no keepalive

csna 0130 00

csna 0140 02

lan TokenRing 19

source-bridge 19 1 999

adapter 26 4000.7206.0026

adapter 30 4000.7206.0030

!

interface Virtual-TokenRing0

no ip address

ring-speed 16

source-bridge 102 1 999

source-bridge spanning

!

interface Virtual-TokenRing1

mac-address 1234.cccc.cccc

no ip address

ring-speed 16

source-bridge 103 1 999

source-bridge spanning

!

snasw cpname xxxx.xxxx

snasw port CIP Virtual-TokenRing0

snasw port VDLCDOWN vdlc 999 mac 1234.5555.5555

snasw port LLCQUS GigabitEthernet0/2

snasw link HOSTQ103 port CIP rmac 4000.7206.0025

snasw link HOSTQ104 port CIP rmac 4000.7206.0026

snasw link HOSTQ101 port CIP rmac 4000.7206.0029

snasw link HOSTQ102 port CIP rmac 4000.7206.0030

!

Can you give me any comments about such a config?

[dmccullo]

This looks about right, if what you want to do is route SNA traffic to either LPAR-3 or LPAR-4 based on where the application is located, and at least one of these LPARs is an APPN NNS.

The only things that look problematic are the duplicate "unitadd" values, the last 2 digits of the "csna" statements, and the "adapno" values, the first 2 digits of the "adapter" statements. Not that I can say for sure that they're wrong, just something to double check against mainframe definitions. It's also common to specify one of the links as preferred for the NNS connection, and to specify the desired link for the DLUS, though neither of these is absolutely necessary.

The more important comment is that you are setting this up now, and a critical component - the CPA, has reached end of sale. As mentioned in the earlier reply, the more common approach is to use HPR/IP through an OSA interface for the upstream connection.

Best regards, Dan