Planning for Disaster Recovery?
Don't Forget your Twinax Users!
Contents
¨ Overview
¨ How a Pure TCP/IP Controller Benefits Your Organization
¨ Eliminate the Need for Active Star Hubs
Overview
For many years now, IBM System/36 and AS/400 users have invested in Twinax infrastructure. This cabling system provided a simple and efficient method of connecting PCs and terminals to the midrange host computer, although access was restricted to interaction with the host computer only, via the Twinax line.
All that changed when IBM released OS/400 V3R7, which supported the Telnet protocol (TN5250e), allowing terminal and printer emulation over TCP/IP. This opened up new possibilities because it enabled Twinax devices to be connected to AS/400s via TCP/IP.
Nowadays, the trend in networking is toward establishing Intranets and Extranets. When designing these systems, organizations may choose to retain all or part of their investment in Twinax. But what happens to these Twinax users when the primary midrange server goes down?
Disaster Recovery Scenarios
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 e-Twin@x 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. The e-Twin@x Controller, as a matter of fact, does this automatically; the users can sign on to the back-up AS/400 and continue to work, without any operator intervention!
What About Locally Attached Twinax Users?
Even locally attached Twinax users can work in this fashion, using the 47xx local e-Twin@x Controller series. These very aggressively priced controllers are designed to work in a local Twinax environment. All the local Twinax cables connect into the 47xx Controller in place of the local Twinax controller resident in the AS/400. The 47xx connects to the AS/400 over the built-in 10/100 MHz Ethernet card, ensuring fast response times. The 47xx Controller will switch over to the back-up AS/400, provided it is on the same IP subnet as the production machine.
Special Features for Switch-Over
The e-Twin@x Controller includes the following special features, which are especially relevant for disaster recovery situations:
DNS Look Up
The e-Twin@x Controller has the ability to configure the AS/400 via a DNS name instead of IP address. A timer in the e-Twin@x Controller refreshes the DNS look up every time it expires. This way, the System Administrator changes the internal DNS server, which lists the AS/400 domain name, and after the timer expires, all the devices are automatically changed to the new IP address.
Auto Reconnect
If the connection to the AS/400 is lost, the e-Twin@x Controller tries to re-establish the connection, without user intervention, after a predetermined time-out period.
Default Rollover
Two AS/400’s can be configured to act as default and back-up, respectively. When the primary (default) AS/400 can no longer be accessed, the e-Twin@x Controller automatically attempts to connect to the secondary (back-up) AS/400. After successful connection to the back-up AS/400, it will stay connected to that AS/400 until the e-Twin@x Controller is reset, which can be done by using a Web browser.
By the way, you can define that the process be reversed if the first host is also defined as a backup system (for the secondary host). In this case, if the backup system fails (or if the TCP/IP interface is terminated), all sessions will be re-connected to the primary system.
Sample configuration using e-Twin@x Controller to connect remote devices
How a Pure TCP/IP Controller Benefits Your Organization
The e-Twin@x Controller will complement the way your organization does business, and allow you to leverage your existing infrastructure while increasing efficiency and lowering communication costs.
The e-Twin@x Controller is a complete hardware and software solution that provides a secure, encrypted connection to the AS/400 over the Internet or WAN, and empowers your local or remote Twinax network to support TCP/IP. It is the only SNA-free, pure TCP/IP controller in existence! Consider these benefits of the e-Twin@x Controller:
¨ Ensures high availability for Twinax users, thanks to robust backup capabilities
¨ Installs in less than 10 minutes, with no AS/400 configuration required!
¨ Can be configured using a dumb terminal, or PC with browser
¨ Supports any Twinax terminal or printer (SCS or IPDS)
¨ Enables remote management of your Twinax devices from anywhere on your LAN, WAN or VPN
¨ Supports a secure connection via the Internet, enabling you to eliminate leased line charges
¨ Scalable, with local and remote models ranging from single-device Twinax support to 112-devices
The e-Twin@x Controller, with Twinax brick attached
We invite you to improve the performance and increase the efficiency of your Twinax network: click here to register for a 30-day trial.
Hidden Costs of Abandoning Twinax
Are you thinking about replacing your Twinax devices with thin clients or PCs with Ethernet terminal emulation? If so, you’re probably doing so to:
¨ update the look and feel of tried-and-true applications
¨ give users access to email and the Internet
¨ replace a costly SNA network with a Frame Relay based network to link remote offices to your AS/400 or iSeries
¨ adopt the TCP/IP network protocol to accommodate non-Twinax groups within the corporation
You’re probably balancing those reasons with the many good reasons to stay Twinax:
¨ your considerable investment in Twinax devices
¨ user and IT familiarity with Twinax
¨ cost of purchasing new devices
¨ safeguarding your secure Twinax environment
¨ retaining user productivity (PC glitches, personal email, web surfing, etc.)
¨ minimizing the strain on limited IT resources
Before you abandon your trusty Twinax environment, consider the following “hidden” costs of such a move:
|
Issue |
|
|
|
|
|
1.
Purchase new terminals (USD$550 each) |
L |
|
L |
L |
|
2.
Re–record Terminal Macros (10mins–30mins) |
|
L |
L |
L |
|
3.
DHCP server requirement |
|
|
L |
L |
|
4.
IP planning |
|
|
L |
L |
|
5.
Citrix? |
L |
|
L |
L |
|
6.
Fat Servers? |
L |
|
L |
L |
|
7.
Boot-up time (Windows takes minutes) |
|
L |
|
|
|
8.
Software license and maintenance costs |
L |
|
L |
|
|
9.
Re-cable? |
L |
|
L |
|
|
10.
Disposal of existing equipment |
L |
|
|
L |
|
11.
Unpacking of new equipment |
|
|
|
L |
|
12.
Program changes for new infrastructure (e.g., Ethernet terminal printer
emulation does not support out queue naming; writers always autostart) |
|
|
L |
L |
|
13.
Changing from ‘Keyboard only’ to mouse and smaller keyboard |
|
L |
|
L |
|
14.
Learning curve for employees |
|
L |
L |
L |
|
15.
New keyboard objections (any change is cause for complaint) |
|
L |
|
|
|
16.
Downtime |
|
L |
L |
|
|
17.
Network planning |
L |
|
|
L |
|
18.
Increased complexity of existing PC Network |
|
|
L |
L |
|
19.
Potential IP addressing mistakes |
|
L |
|
L |
|
20.
New skills required |
|
L |
|
L |
|
21.
Cost of ownership |
L |
|
L |
L |
|
22.
Virus protection? |
L |
|
|
L |
|
23.
Loss of productivity due to increase in new features to play with |
|
L |
|
|
|
24.
Reliability of Windows-based servers for DHCP etc. |
|
L |
|
L |
|
25.
On going management |
|
|
|
L |
|
26.
Increased bandwidth requirements? |
L |
|
|
L |
|
27.
Loss of central control |
|
|
|
L |
|
28.
Terminal life cycle costs (nobody knows how long a Thin Client will
stay current, Dumb Terminals have not changed substantially for over 10
years) |
L |
|
|
|
|
29.
Software changes brought on by IBM, how will you keep up to date? |
L |
|
|
L |
|
30.
Cable distances? |
L |
|
L |
|
|
31.
Noise issues |
|
L |
|
|
|
32.
Dot matrix to Laser printer |
L |
|
L |
|
|
33.
Bar code reading |
L |
L |
L |
|
|
34.
Download times for Browser based devices |
|
L |
|
|
|
35.
Screen size, Windows based emulators have less viewing area due to
menu bars and status bars. |
|
L |
|
|
|
36.
Cut and paste (will it work the same?) |
|
L |
|
|
|
37.
Split screen (will it be the same?) |
|
L |
|
|
|
38.
Different font (is it what you like? |
|
L |
|
|
|
39.
Hot keys (are they the same i.e. Alt PgUp switch session, etc.?) |
|
L |
|
|
|
40.
More configuration options, more chance for problems (Color mapping,
background changes etc.) |
|
L |
L |
|
|
41.
Dial back up issues for new network |
|
L |
|
