BOS eTwinax (e-Twin@x) TCP/IP Controller
| BOS eTwinax (e-Twin@x) TCP/IP Controller |
4616: Supports up to 16 Twinax addresses (includes 8 Port Brick)
4656: Supports up to 56 Twinax addresses (includes 8 Port Brick)
4612: Supports up to 112 Twinax addresses (includes 16 Port - 2 x 8 Port Brick)
e-Twinst@r with Active Star Topology
4816: Supports up to 16 Twinax addresses (includes 8 Port RJ45 Hub)
4828: Supports up to 28 Twinax addresses (includes 8 Port RJ45 Hub)
4856: Supports up to 56 Twinax addresses (includes 8 Port RJ45 Hub)
4812: Supports up to 112 Twinax addresses (includes 1 x 16 Port RJ45 Hub)
4600: Additional 8-Port Twinax connector brick including second twinax board (16 ports)
| 4691 BX6058-1 e-Twin@x Controller 1 device | |
| 4693 e-Twin@x Controller 3 device (2 port Y cable) | BOS 4693 e-Twin@x Controller 3 device (2 port Y cable) (Twinax) Fully refurbished with 90-day warranty 4693 BX6058 |
| 4608 e-Twin@x Controller 8 device (8 Port Twinax Brick) | |
| 4610 e-Twin@x Controller 14 device (2 port Y cable) | |
| 4616 e-Twin@x Controller 16 device (8 port Twinax Brick) | |
| 4628 e-Twin@x Controller 28 device (8 port Twinax Brick) | |
| 4656 e-Twin@x Controller 56 device (8 port Twinax Brick) | |
| 4612 e-Twin@x Controller 112 device (2 x 8 port Twinax Brick) | BOS 4612 e-Twin@x Controller 112 device (2 x 8 port Twinax Brick) Fully refurbished with 90-day warranty 4612 BX6058 |
| 4808 e-Twinstar Integrated RJ45 Hub Controller 8 device 8 RJ45 connectors | BOS 4808 e-Twinst@r Controller 8 device 8 RJ45 connectors Fully refurbished with 90-day warranty 4808 e-Twinstar Controller |
| 4816 e-Twinstar Controller 16 device 8 RJ45 connectors | |
| 4828 e-Twinstar Controller 28 device 8 RJ45 connectors | |
| 4856 e-Twinstar Controller 56 device 8 RJ45 connectors | |
| 4602 SECURIT-e + RAS 2 Port | |
| 4605 Dial Backup feature (requires 4602)> | |
| 4600 Additional 8-Port Brick (Factory install only, 46xx series) | |
| 4800 16-Port RJ45 HUB (48xx series, factory install only, replaces base 8-port hub) | |
| MCON ONE Year Warranty Extension - available at time of purchase only | |
| MCON2 TWO Year Warranty Extension - available at time of purchase only |
BOS e-Twinax Controller
Move your Twinax network forward with the best state-of-the-art pure TCP/IP solution. The e-Twinax Controller leverages your investment in Twinax.
- Supports all Twinax display stations, printers (both SCS and IPDS),and existing cabling.
- Blazing Speed. Pure TCP/IP drives your Twinax or Twinax Ethernet network--easy to configure and maintain, and routable.
- Eliminates SNA, AnyNet and MPTN traffic.
- Easy setup. Hardware and software solution.Remote management via a Web browser, saving you valuable technical resources.
- Unbeatable uptime and disaster recovery.The only Anynet alternative (MPTN) with pure TCP/IP.
Tests show that IPDS printing takes one third the number of TCP/IP packets to print the same document via native TCP/IP than via SNA. Imagine the performance improvement by moving a 56K frame relay circuit supporting a number of IPDS printers using SNA to TCP/IP with an e-Twinax Controller!
Our easy to install Twinax controller improves performance of your twinax network while protecting your investment. The controller supports all Twinax display stations, SCS and IPDS printers, and existing cabling.
Anynet (MPTN) vs TCP/IP: Pros & Cons
Problems with Areas Anynet (MPTN)
As users started to use Anynet, flaws began to appear, particularly when large amounts of data needed to be transported. Typical problems included disconnecting sessions and slow performance. These problems were not readily apparent on local networks; they were much more prevalent when the timing between the host and device is delayed. In recent tests we tried to establish a connection across the Internet. We were able to get a session started using a PC with the NS/Router, however within three minutes of working with this session it disconnected. We also tried connecting with a remote controller, which used the same protocol. We were able to vary on the controller, however the terminals on the controller never established a connection.
TCP/IP Makes its Entrance
In recent years IBM has focused their development on TN5250. With the arrival of V4R2 (and later PTFs to support older versions) IBM supported TN5250e and TN3270e. This enhanced TCP/IP support enabled the AS/400 and 3270 hosts to support device naming and SCS printer support. For the first time, users could really take advantage of native TCP/IP support on these hosts. IPDS was also supported directly with TCP/IP using PPD/PPR (a special protocol developed for this specific purpose). Recent versions of Client Access (Client Access Express) contain support for native TCP/IP only, providing proof that IBM's direction is to provide better support for native TCP/IP on these host computers.
Advantages of TCP/IP over Anynet (MPTN)
Because TN5250 and TN3270 use native support on the system, they do not require as many CPU cycles to make use of it. TN5250e and TN3270e do not have the timing limitations that SNA has, therefore these protocols can be used over the Internet with no problem. IBM has realized this and that is one of the reasons that Client Access Express supports SSL encryption, to enable users who want to connect using the Internet a way to do so without encountering security issues. Recent tests show that IPDS printing takes three times the number of TCP/IP packets to print the same document via SNA than via native TCP/IP. Imagine the effect on the performance of a 56K frame relay circuit supporting a number of IPDS printers using SNA!
IBM 5494 Controller has been Withdrawn
The IBM 5494 Controller was discontinued at the end of 1999, and now both Perle and NLynx are developing TN5250 controllers of their own. BOScom clearly leads the field with its e-Twin@x Controller, since it uses the same TCP/IP protocol as the very stable and field-tested BOS-NOVA TCP/IP TN5250e emulator, which has been installed and working on hundreds of thousands PCs since 1997. For experience and state-of-the-art technology, choose BOScom.
Overview of e-Twinax ControllerThe e-Twin@x Controller is the only SNA-free, pure TCP/IP Controller in existence. It moves your twinax network forward in 5 important ways:
Advantages
- Replaces SNA connectivity and Anynet protocol with simple, easy-to-configure TN5250e TCP/IP
- Serves as a secure, low cost connection from your remote branches to the AS/400 using the Internet, saving a fortune in leased line expenses
- Includes a built-in 2- or 6-port* Remote Access Server (RAS), complete with AS/400 client RAS software, built-in firewall and support for RADIUS standards
- Housed in a compact 1 U communications Controller that fits into standard 19" rack-mount communications cabinets
- Provides IP over Twinax connection to a local or remote AS/400, allowing Twinax-attached PCs to benefit from IP applications such as e-Mail, Web browsers and Microsoft Networking, while running up to 5 times faster when used with BOS IP over Twinax drivers
- Supports up to 112 Twinax devices; upgrades to expand the number of devices supported from 8 up to 56, are software-based and can be applied either on-site or remotely, via the Internet
- Provides an interface to Citrix Metaframe supporting Twinax technology or other corporate intranet computing for PCs using IP over Twinax
Secure, Reliable, Low Cost Connection using the Internet
When the traditional SDLC connection is replaced with a Wide Area Network (WAN) connection using TCP/IP, the e-Twin@x Controller can be used to maintain legacy Twinax devices (such as high-speed printers and dumb terminals) at your remote sites. In this configuration, all the devices will appear on the AS/400 as TN5250 devices, and all PC devices can connect to the AS/400 either by using dumb terminal emulation or by installing the e-Twin@x version of BOSANOVA TCP/IP or IBM TCP/IP drivers to connect to the AS/400 over TCP/IP.
Secure connection via the Internet using modem(s) for a mixed Twinax and LAN environment
The e-Twin@x Controller can be connected to the AS/400 via the Internet, saving you a fortune in leased line expenses. Requirements are minimal:
- Local site: a fixed connection to the Internet and BOS' Java-based SECURIT-e ServerTM, which can be run on the AS/400, and any PC or Mini Computer with a Windows, Unix-based or Linux operating system.
- Remote site: a connection to the Internet, either via a dial up account or using a leased line to a local ISP.
Configuration and Maintenance with Ease
The e-Twin@x Controller is managed via a standard Web browser, which enables all of the units to be managed from a central point anywhere on the network, or via a modem dialed in to the RAS. Configuration can also be done using a dumb terminal attached to any of the ports. The Controller software can also be updated over the network or via dial-in. Terminals, PCs or printers can be added to the Controller very simply using a plug-and-play feature in Auto mode. The device name can be changed at any time, without restarting the Controller. The Controller also verifies the host connection, including which PTFs are installed for each OS version.
Configuration and management can be done via standard Web browser from anywhere on the network
e-Twin@x Controller as an IP Gateway
The e-Twin@x Controller connects to the network using a standard network hub, which is attached to the local office via a standard IP router. Ethernet PCs can be connected to the same network hub as the Controller for mixed Ethernet and Twinax infrastructures.
With the TCP/IP drivers loaded on the PC, the user can take full advantage of the WAN, and get:
- Support for e-Mail
- Printer and file sharing on the network
- Ability to access and run Intranet applications
- Implementation of server-centric computing such as Citrix Metaframe.
Overcome Network Instability and Printing Problems
Dial Backup*
The Dial Backup feature ensures improved uptime for Controllers that are connected to an AS/400 using a LAN connection (via the Internet routers or a separate Frame Relay network). If the LAN connection fails, the Dial Backup provides (via an attached modem) an additional method to connect to the AS/400. Two configurations are available: Always, which provides a simultaneous connection at all times; and "On LAN Failure, which causes the Controller to activate the modem connection only when LAN connectivity failure is detected.
* Optional
Automatic Session Recovery
In the event that a router on a frame-relay network disconnects and then re-connects, users of remote Twinax-attached devices can choose to resume their current session. The e-Twin@x Controller can be set to automatically recover the session, within a user-defined time period, ensuring smooth and efficient operations even in cases of network instability.
Customized Object for Specialty Printers
The e-Twin@x Controller supports a wide variety of Twinax printers, including label and barcode printers that are often called upon to deal with special printing requirements such as oversized fonts, graphics, and unusual page sizes. A parameter can be set to instruct the host to send a pure data stream through the e-Twin@x Controller, allowing it to override the original complex formatting commands with simplified commands that are supported by most printer models, before releasing the job to the destination printer.
e-TwinSt@r Series Reduces Need for Need for Active Star Hubs
The e-TwinSt@r Series Controller includes a built-in unit featuring 8 (or 16) RJ45 sockets. Twinax devices working over CAT5 lines are connected directly to the Controller, saving the cost of an active star hub and eliminating the need for power sources and additional space in the communications closet, as well as the extra set-up and maintenance time.
E-mail on Dumb Twinax Terminals*
Basic e-mail functionality, known as TwinMailTM, is supported on dumb Twinax terminals. In addition to sending and receiving e-mail, TwinMail includes a personal address book that can be organized according to user-defined preferences.
* Optional
PC Remote Access
The e-Twin@x Controller supports a 2- or 6-port* Remote Access Server (RAS), providing remote PC users with network access in addition to AS/400 access. Remote users can dial in to the e-Twin@x Controller and gain access to the network using the RAS. This RAS includes a firewall for restricting access per user to specific IP devices or ports (e.g. one group of users may be allowed access to the AS/400 for display emulation, but not file transfer). The RAS also automatically logs all remote access activity. The RAS component can use the services of any RADIUS server for authentication, if required.
* Optional
Model 4608 & 4808 e-Twinax Controller (e-Twin@x / BX6058)
Support for 8 Twinax Addresses / Devices Over any TCP/IP Connection
e-Twinax Controller - Model 4608 & 4808
Connect Up To 8 Twinax Devices Over IP to a New Power9, Power8, Power7 or Any iSeries AS/400 - Local or Remote
Overview
The e-Twinax Controller is a "Twinax-to-IP" controller that can be used to connect Twinax devices to an IBM Power9, Power8, Power7 or any iSeries or AS/400 over any IP connection, locally or remotely.
The simplest way to look at the e-Twinax Controller is as an "External Twinax Workstation Controller". You can even use your current IBM 8-port Twinax "Brick" on it.
Some models also support an 8-port RJ45 "Brick". Each RJ45 port is just like a Twinax Host Port with an RJ45 Balun on it.
When used remotely, it is a replacement for SDLC Remote Controllers such as the IBM 5494 and 5394, the Perle 594e, 494e and 394, and other IBM compatible Twinax controllers from I-O Corp., Decision Data and Idea.
It will support Twinax Display Stations and Twinax Printers (SCS and IPDS).
Being it uses TN5250e as it's communication protocol, it does not require any SNA protocols. In addition, it does not require DLSw (Data Link Switching) as IBM 5494s and other Twinax Controllers do.
Technical Specifications - 4608 & 4808 eTwinax Controller
Devices Supported
Ports
4608 - 8 Twinax Host Ports
4808 - 8 Twinax Host Ports or 8 RJ45 Host Ports
Each RJ45 Host Port is equivalent to a Twinax Port with a Twinax to RJ45 Balun installed
Each Host Port will support up to a maximum of 7 devices using any standard Twinax address (0, 1, 2, 3, 4, 5, 6) up to a maximum total of 8 devices/addresses across all 8 ports.
Displays
Partial List - 5251, 5291, 3179-2, 3180, 3196, 3197C, 3197D, 3476, 3477, 3486, 3487, 3488 and compatibles by CLI, Decision Data, I-O, Memorex-Telex, Praim, etc. (not all features are supported such as shared addressing, mouse support, imaging, etc.
Printers
SCS Printers - IBM 3812-1, 4214, 5219, 5224, 5225, 5256, 5262, 6262, 6400, 6500, Printronix P5000, P6000, P7000, P8000 and compatibles
IPDS Printers - IBM 3812-2, 4224, 4230, 4234, 4247, 6400, 6500, Printronix P5000, P6000, P7000, P8000 and compatibles
Other Printers - Most printers and printing devices such as thermal printers, card printers, etc. with built in Twinax interfaces or external Twinax interface protocol converters
Workstations/PCs
Supports all PCs with Twinax 5250 emulation (TDLC) and BOS, CompuMaster, NLynx, IBM or IBM-compatible Emulation Cards
Host System Requirements
AS/400 Operating System
OS/400 V3R2 or higher
AS/400 Internal Features
AS/400 Ethernet LAN Connection
* Required
RJ45 Host Port Option (e-TwinStar) Eliminates Need for Active Star Hubs
The e-Twinax Controller now has an optional model that includes a built-in unit featuring 8 (or 16) RJ45 sockets. Twinax devices working over CAT5 lines are connected directly to the Controller, saving the cost of an active star hub and eliminating the need for power sources and additional space in the communications closet, as well as the extra set-up and maintenance time. The RJ45 Ports of this option operate just as a Twinax port with an RJ45 Balun attached to it.
If you need to connect more Twinax Devices than the number of physical ports on an e-Twinax Controller, please read the explanation in the next section. The e-Twinax Controller model must be able to support the number of devices you need to connect.
The e-TwinStar (4800 Series) is available in models with support for 8, 16, 28, 56 or 112 Twinax addresses/devices. The 4800 Series is fully upgradeable from one model to the next allowing for growth from 8 to a full 112 device support. The 4800 Series also supports connection of the 8-Port Twinax Brick as the e-Twinax 4600 Series as well as the IBM 8-Port Twinax Brick from your existing Internal Twinax Workstation Controllers.
Upgrades are made by simple entering a new software key in the configuration section of the e-Twinax. You can upgrade remote locations by accessing the upgrade portion of the configuration over your WAN. Upgrading is done while the controller is in full operation. There is no need to have those users connected to it brought down. This eliminates the need other controllers have to bring them down while increasing their device capacity or adding options.
Explanation of Device Support for the eTwinax and RJ45 Ports of e-Twinax Controller
As with the standard AS/400 8-port "Twinax Brick" from the Twinax Workstation Controller, each Host Port (Twinax or RJ45) of the e-Twinax will support up to a maximum number of 7 device addresses (0, 1, 2, 3, 4, 5, 6), up to the maximum number of devices the particular model controller will support. This convention holds true to all Twinax or RJ45 Host Ports of S/36, S/38, AS/400, iSeries and all IBM, Decision Data, I-O, Idea, and Perle Remote Controllers except for the very old 5251-12 and 5294 controllers that only supported a maximum of 4 addresses per Host Port.
For example, an IBM 5394-01B Controller has three Twinax Host Ports. Three ports with 7 devices each would total 21. The 5394-01B only supports 16. You can distribute those 16 device addresses across those three ports however you see fit. That could be 7 on the first port, 7 on the second port and 2 on the third port. You could also have 6, 6 and 4 or any other combination that totals 16 device addresses with a maximum of 7 on any one port.
Another example is the 4616 (Twinax Host Ports) and 4816 (RJ45 Host Ports) of the e-Twinax Controllers. Both of these models will support 16 Twinax addresses/devices but only have 8 physical ports. Using the same logic as with the 5394-01B example, you can connect devices to ANY of these 8 ports as long as the total number of addresses used is 16 or less. For example you could use the same 7, 7, and 2 on the first three Host Ports as with the 5394. Being these models have 8 Host Ports, you could also put 2 devices on each port for a total of 16. You could also have 4, 4, 4 and 4 on four of the 8 Host Ports or any other combination that totals 16 device addresses with a maximum of 7 on any one of the 8 ports.
If you need to connect more physical devices than the number of ports you have two options.
First, you can "cable-through" your Twinax devices from one to the next using actual Twinax cables. Using this method you can connect up to 7 devices to a single Host Port. If you are using multiple session terminals, the number of physical devices would be less as each Host Port will only support 7 addresses.
Second, you can add a Twinax-to-RJ45 Active Star Hub such as the Gemini Express Active Star Hub to your setup. These Active Star Hubs connect to one of the controllers Host Ports either by Twinax Cable or Category 5 (CAT5) cable, and expand the single port to 7 RJ45 ports corresponding with the device addresses available on that port of 0, 1, 2, 3, 4, 5, and 6. This is the same whether the e-Twinax Controller has Twinax Host Ports or RJ45 Host Ports. In this implementation each Twinax Device would be required to have a Twinax-to-RJ45 Balun on it to allow connection with a CAT5 cable.
The RJ45 Host Ports of the e-Twinax Controller are operationally the same as a Twinax Host Port with an RJ45 Balun attached to it.