Re: Addition: IP over SNA connection (X.21)

Philipp,

Can you print the line description and send it? You can print it like this:

    dsplind lind(line-name) output(*print)

If there are any controllers or devices associated with the line can you
print these, too?

   dspctld ctld(controller-name) output(*print)
   dspdevd devd(device-name) output(*print)

It's OK if the descriptions are in German!
Patrick

---
IBM AS/400 communications, FTP automation, and eCommerce
software and consulting services.

http://www.patownsend.com

----- Original Message -----
From: "Philipp Rusch" <philipp.rusch@rusch-edv.de>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, March 16, 2001 10:59 AM
Subject: Re: Addition: IP over SNA connection (X.21)


> Hello Patrick,
>
> to be honest: I tried X.25 descriptions, too, but they didn't work at all.
> My hardware setup is like this:
>
> AS/400 -- X.21 int. -- X.21 to ISDN(64K) converter box ---
telecom-line ---
> --- other side: ISDN(64K) to X.21 converter box --- X.21 int.--- AS/400
>
> These boxes are configured to dial the other end by themselves, if you
take up
> the
> signal "C" line at the X.21 interface, so the AS/400 thinks it is a
permanent
> line.
>
> I did not come far with my X.25 defintions (shall I take X.21 or SDLC ? Is
this
> a *PVC or a *SVCBOTH link ?) ...
> I will port the details of my current line and controller desc. when I am
back
> in the office.
>
> Any help much appreciated ...
>
> Thanks, Philipp
>
>
> Patrick Townsend schrieb:
>
> > Philipp,
> >
> > Oops. I forgot to engage brain before responding. Is the X.21 definition
> > running SNA over X.25? Or just SNA? If it is running X.25 I would
implement
> > IP over X.25 rather than trying to tunnel IP through the existing SNA
> > protocol. If you are not running X.25 can you post the line, SNA
controller,
> > and SNA device descriptions?
> >
> > Patrick
> >
> > ---
> > IBM AS/400 communications, FTP automation, and eCommerce
> > software and consulting services.
> >
> > http://www.patownsend.com
> >
> > ----- Original Message -----
> > From: "Philipp Rusch" <Philipp.Rusch@rusch-edv.de>
> > To: <MIDRANGE-L@midrange.com>
> > Sent: Friday, March 16, 2001 12:51 AM
> > Subject: Addition: IP over SNA connection (X.21)
> >
> > > Hello Patrick and others,
> > > there is no way to define SSAPs to an X.21 line description,
> > > this is something totally different from ethernet.
> > > BTW my ethernet lines have SSAP "12" enabled for SNA on both ends.
> > > I guess, that IP over SNA is not the complete set of IP functions
> > > as is SNA over IP, because help-text only mentions "socket-appli-
> > > cations" as possible usage for that functionality.
> > > My goal is to use ip AND sna on the existing sna connection between
> > > those two sites.
> > >
> > > Regards, Philipp
> > >
> > >
> > > Patrick Townsend schrieb:
> > >
> > > > Have you added the SSAP entry (12) you need for TCP/IP? This is on
the
> > line
> > > > configuration.
> > > >
> > > > Patrick
> > > > ---
> > > > IBM AS/400 communications, FTP automation, and eCommerce
> > > > software and consulting services.
> > > >
> > > > http://www.patownsend.com
> > > >
> > > > ----- Original Message -----
> > > > From: "Philipp Rusch" <Philipp.Rusch@rusch-edv.de>
> > > > To: "Midrange List" <MIDRANGE-L@midrange.com>
> > > > Sent: Thursday, March 15, 2001 2:22 PM
> > > > Subject: IP over SNA connection (X.21)
> > > >
> > > > > Hello all,
> > > > > here is another request to all those, who managed it already ...
> > > > > Setup is as follows:
> > > > > SNA connection over X.21 line (ISDN) from one AS/400 to another,
> > > > > works perfectly. We now wanted to add TCP/IP to that link, to be
> > > > > able to route the PC traffic over the same (leased) line.
> > > > > I defined (cfgips) an ip over sna interface on both ends, defined
> > > > > the *ips routes, mapped SNA-names to ip-adresses, no chance at all
> > > > > to get even a ping to work over that line !
> > > > >
> > > > >          ---------                       ---------
> > > > >  Eth.   | AS/400  |                     | AS/400  | Eth.
> > > > >  LAN A  | "SYS_A" | X.21           X.21 | "SYS_B" | LAN B
> > > > >  -------O         O------/....... /-----O         O-------
> > > > > 192.168 |         |     192.168..       |         | 192.168.1.250
> > > > > 142.7   |         | 145.7       145.250 |         |
> > > > >          ---------                       ---------
> > > > >
> > > > >
> > > > > With NETSTAT I see routes to each system on the other end, but
> > > > > no telnet or ping gets through ... even when I try to ping only
> > > > > the X.21-side of the same machine gets no response !
> > > > > E.g. lets say I am on sys_a and ping to 192.168.145.7 which is
listed
> > > > > under netstat as directly connected interface - no answer !
> > > > > (WRKIPSIFC says active to that line)
> > > > >
> > > > > I can't get it to work ... am I on the wrong path ?
> > > > >
> > > > > Any help appreciated, thanks in advance.
> > > > >
> > > > > Regards from germany, Philipp Rusch
> > > > >
> > > > >  -----------------------------------------------------------------
> > > > > | EDV Beratung Rusch          EDP Consulting Rusch
|
> > > > > | Philipp Rusch               Mailto: Philipp.Rusch@rusch-edv.de
|
> > > > > | Am Errlich 9                WWW   : http://www.rusch-edv.de/
|
> > > > > | D-61191 Rosbach,
|
> > > > > | Germany
|
> > > > > | Phone: (+49) 6003 3972      Mobile : (+49) 172 89 86 230
|
> > > > > | Fax  : (+49) 6003 3795
|
> > > > > |
|
> > > > >  -----------------------------------------------------------------
> > > > >
> > > > >
> > > > > +---
> > > > > | This is the Midrange System Mailing List!
> > > > > | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
> > > > > | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
> > > > > | To unsubscribe from this list send email to
> > > > MIDRANGE-L-UNSUB@midrange.com.
> > > > > | Questions should be directed to the list owner/operator:
> > > > david@midrange.com
> > > > > +---
> > > >
> > > > +---
> > > > | This is the Midrange System Mailing List!
> > > > | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
> > > > | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
> > > > | To unsubscribe from this list send email to
> > MIDRANGE-L-UNSUB@midrange.com.
> > > > | Questions should be directed to the list owner/operator:
> > david@midrange.com
> > > > +---
> > >
> > > +---
> > > | This is the Midrange System Mailing List!
> > > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> > > | To unsubscribe from this list send email to
> > MIDRANGE-L-UNSUB@midrange.com.
> > > | Questions should be directed to the list owner/operator:
> > david@midrange.com
> > > +---
> >
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
david@midrange.com
> > +---
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---