RE: Non-TCP/IP based remote AS/400 connectivity solution

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

We have an old protocol converter with a modem attached.  It is a Trulynk
box under the name of Black Box.  Be dial into that at 19200, not too bad
for 5250 emulation only.  Rock solid and not dependant on your ethernet.
BUT cheaper would be to add a second ethernet card on a different IOP on a
different BUSS.  Then create a *virtualip on your AS400 with a route from
each physical ethernet card's IP.  Now if one ethernet fails, you can
reconnect to the same virtual IP via the secondary route.  Now both routes
can be in different subnets if you have multiple subnets.  I would
definitely plug each ethernet card into different switches.  So if you have
a space on an IOP in your system for a second Ethernet, much cheaper than
protocol converters and modems.  Provides automatic failover for all IP
connectively including SNAoverIP.

Chris Bipes

-----Original Message-----
From: Chuck Lewis

Guys,

Can't speak for Cynthia so she will have to clarify this, but my read on
what she said was if TCP/IP was shutdown or something, another non-TCP/IP
method would be needed to access the system. The ONLY reason this even
occurred to be is because last month, per our IBM CE, I had to reset the IOP
that our IBM 9427 (problem child) tape unit is on. Well that also controls
our Ethernet card. So I knew it would knock down all of our branches. So
that night at home, not thinking to clearly :-) I connected to our AS/400
via our VPN (VERY fast) and started this process. And my session
terminates... So I fire up PC/Anywhere and get in fine (but slow) and see
that of course my remote VPN session would have ended since TCP/IP was
ended. I let the IOP reset complete and then fired it back up...