The Best Way to Keep Twinax
Users Working
Is With a Pure TCP/IP Controller
In
most disaster recovery scenarios these days TCP/IP is the protocol of
choice for switching between machines. Most solutions to switch users from
the primary AS/400 to the back-up AS/400 require that the IP address under
which the AS/400 appears be changed. For example, say that the production
AS/400 has IP address 10.1.1.10, while the back-up AS/400 normally uses
10.1.1.20. In the event of a disaster, the back-up AS/400 switches to
10.1.1.10. All the PC users using TN5250 do not have to change their
settings; they simply restart their sessions and sign back on.
What Happens to Twinax Users?
In
the same scenario, Twinax users suffer a harsher plight. During disaster
recovery the local Twinax users can be left without any access to the
back-up AS/400. Remote Twinax users usually can be switched over using
some scripts on the AS/400, however is often a challenge.
Is There a Better Way?
IP-based
Twinax controllers like the
I-O Corporation Xip
Controller can easily switch between
AS/400’s because they treat Twinax users the same way they treat the PC
users, once the session is reset. Once the
Xip Controller is connected
to the back-up iSeries, the users can sign
right back on.
What About Locally Attached Twinax Users?
Even
locally attached Twinax users can work in this fashion, using the
Xip
Controller series. These
controllers are designed to work in a local Twinax environment.
The
local Twinax cables connect into the Xip Controllers in place of the local
Twinax controller resident in the AS/400. The Xip
connects over the Ethernet LAN to the AS/400
with it's integrated 10/100 MHz Ethernet card, ensuring fast response times.
You simply switch the Xip Controller to the
back-up AS/400.
For More Information
