topic Re: x.25,SNA-QLLC, SVC, CISCO, CONFIGURATION, HELP in Server Networking

x.25,SNA-QLLC, SVC, CISCO, CONFIGURATION, HELP

m.villargonzalez — Wed, 10 Oct 2001 14:44:40 GMT

Our main production is based on X25 network : SNA QLLC major part.

We want to replace our 3745 (and NCP,NPSI), and we're planning to

implement a solution based in CISCO routers.

Our actual configuration is

HostIBM(S/390) ----> 3745 (with NPSI) ---> x.25 cloud

The future configuration will be

HostIBM(S/390)--> OSA Fenet --> lan Ethrnet --->

--->Cisco ---> x.25(SVC's) cloud

Don't ask why DON'T Cisco with CIP, this is not my decision.

Now, for X.25 call-out(npsi), I have my switched major nodes where each PU has

a macro PATH with DIALNO=... and GRPNM=..., everything is OK.

But for the future configuration

Where can I find information or samples? About the configuration needed in

the Cisco Router and Switched Major Nodes. Someone could send me samples

or a Internet Address. I have found samples for Cisco with CIP but not for

my case with OSA Fenet.

Re: x.25,SNA-QLLC, SVC, CISCO, CONFIGURATION, HELP

skoretsk — Wed, 10 Oct 2001 17:21:44 GMT

Hi Miguel,

You'll find sample configurations at these URLs:

http://www.cisco.com/warp/customer/488/54.html

http://www.cisco.com/warp/customer/488/qllc_index.html

The sdlc partner mac address would be the mac address you define on OSA Fenet (just like the mac address you define on the CIP adapter). The switch major node definitions should be same as the ones you're using now.

Cisco's X.25 IOS support is not a replacement for FEP NPSI. Cisco supports (1) X.25 over TCP/IP (XOT), which supports X.25 sessions between two native X.25 endpoints across a router network, and (2) QLLC, which supports router transport of SNA over X.25. PCNE is not supported on Cisco routers.

Re: x.25,SNA-QLLC, SVC, CISCO, CONFIGURATION, HELP

m.villargonzalez — Mon, 03 Dec 2001 16:26:25 GMT

I think it is not enough, because the samples are all token-ring -- router -- X.25

Now in my Switched NOdes in the macro DIALNO I am

pointing to a X.25 address, and when I have

Host/IBM --FENET -- Router --- X.25

I'll have to point to a virtual-mac.

I am looking for a sample that shows : first the situation when it uses HostIBM <-> 3745 with NPSI <-> x.25, with the Switched Node. And second the situation when it is converted to

HOstIBM <-> Fats Ethernet <-> Router <-> X.25

Re: x.25,SNA-QLLC, SVC, CISCO, CONFIGURATION, HELP

riccardo_romani — Fri, 04 Jan 2002 16:28:03 GMT

hi , could you please help me suggesting a good configuration for the follow design:

P.S. our customer has only one router (ios ver. 12.1)

os390--->osa/2 tkr--->router 3640-->cloud x25--->qllc native device (as400)

i have to perform a dial-out operation , we're migrating from 3745-npsi to router

with qllc.

Using the example with dlsw , the router doesn't perform the call to remote x.121

address , using SRB is ok only after the second call , in fact in the first one the router

forward the qxid before the virtual circuit is up conseguently the response from

remote device doesn' return and the VC remain up ; in the second call all is ok

because of the VC is already up so the exchange id is ok and the session start.

Thanks in advance

Re: x.25,SNA-QLLC, SVC, CISCO, CONFIGURATION, HELP

skoretsk — Fri, 04 Jan 2002 20:13:20 GMT

Hi Riccardo,

You didn't provide the configuration you tried. Some general comments:

Each "qllc dlsw" statement on an interface requires a different subaddress, in other words:

qllc dlsw

qllc dlsw subaddr 01

The subaddress are digits after the X.121 address in calls in or calls out.

If the SDLC is always initiating the connection, the customer could do something like this:

interface Serial1

encapsulation x25

x25 address 1632065

x25 map qllc 4000.2210.0001 1210066

x25 map qllc 4000.2210.0002 1222221

qllc dlsw vmacaddr 4000.2210.0001 2

i.e. use vmac pools and don't specify a partner. Note, I changes the mac address to make pools simpler. A partner is only needed if the qllc side initiates the connection to an SDLC partner.

If qllc can initiate the connection then you can do something like this:

interface Serial1

encapsulation x25

x25 address 1632065

x25 map qllc 4000.2210.0001 1210066

x25 map qllc 4000.2211.0001 1222221

qllc dlsw vmacaddr 4000.2210.0001 partner 4000.3174.00c1

qllc dlsw vmacaddr subaddr 11 4000.2211.0001 partner 4000.3174.00c2

In the above example,

The partner qllc device would call 1632065 to connect with sdlc C1.

The partner qllc device would call 163206511 to connect with sdlc C2.

Hope this helps.

Regards, Steve