Comtech EF Data turboIP User Manual
y
™
v4.0
turboIP
TCP/IP Performance Enhancement Prox
User Guide
Part Number MN/TURBOIP.IOM
Revision 6
ii
turboIP
TCP/IP Performance Enhancement Proxy
Comtech EF Data is an ISO 9001
Registered Company
™
v4.0
User Guide
MN/TURBOIPv4.0.IOM
Revision 6
June 20, 2006
CUSTOMER SUPPORT
Contact the Comtech EF Data Customer Support Department for:
Product support or training
Information on upgrading or returning a product
Reporting comments or suggestions concerning manuals
Contact Customer Support using any of the following methods:
Mail: Comtech EF Data
Email: service@comtechefdata.com
Customer Support Department
2114 West 7th Street
Tempe, Arizona 85281 USA
Phone: 480.333.2200 (Main Comtech EF Data Number)
480.333.4357 (Customer Support Desk)
Fax: 480.333.2161
Internet:
www.comtechefdata.com
To return a Comtech EF Data product (in-warranty and out-of-warranty) for repair or
replacement:
1. Request a Return Material Authorization (RMA) number from the Comtech EF Data
Customer Support Department.
2. Be prepared to supply the Customer Support representative with the model number,
serial number, and a description of the problem.
3. To ensure that the product is not damaged during shipping, pack the product in its
original shipping carton/packaging.
4. Ship the product back to Comtech EF Data. (Shipping charges should be prepaid.)
For more information regarding the warranty policies, see Warranty Policy, p. ix.
Table of Contents
CHAPTER 1. OVERVIEW ....................................................................................................1-1
1.1 Introduction ..........................................................................................................................1-1
1.2 TCP/IP Performance Limitations..........................................................................................1-3
1.3 TCP/IP Performance Enhancement Proxy ..........................................................................1-3
1.4 Selective Acceleration..........................................................................................................1-4
1.5 Data and Header Compression ...........................................................................................1-5
1.6 turboIP Physical Description and Specifications..................................................................1-6
CHAPTER 2. FAIL TO WIRE..................................................................................................2-1
2.1 Description ...........................................................................................................................2-1
2.2 Fail to Wire Board Operation ...............................................................................................2-1
2.3 Fail to Wire Board Installed..................................................................................................2-2
2.4 No Fail to Wire Board Installed ............................................................................................2-4
CHAPTER 3. EASYCONNECT™..............................................................................................3-1
3.1 easyConnect™ ON ..............................................................................................................3-1
3.2 Important easyConnect™ Notes...........................................................................................3-2
CHAPTER 4. CONFIGURING TURBOIP™ ........................................................................4–1
4.1 Important Configuration Notes ......................................................................................4–1
4.2 Required Equipment List...............................................................................................4–1
4.3 User Interfaces..............................................................................................................4–2
iii
turboIPv4.0 Revision 6
Getting Started MN/TURBOIPv4.0.IOM
4.4 Configuration Wizard.....................................................................................................4–3
4.4.1 End User License Agreement (EULA) .........................................................................4–4
4.4.2 Configuration Wizard turboIP V4.0 - Summary.......................................................... 4–5
4.4.2.1 Configuration Wizard turboIP V4.0 - User Accounts ...........................................4–7
4.4.2.3 Configuration Wizard turboIP V4.0 – Network Settings for Remote Access .....4–9
4.4.2.4 Configuration Wizard turboIP V4.0 – WAN Transmission Rate.......................4–10
4.4.2.5 Configuration Wizard turboIP V4.0 – DoD Banner ..........................................4–11
4.4.2.6 Configuration Wizard turboIP V4.0 – Web Interface........................................4–12
4.4.2.7 Configuration Wizard turboIP V4.0 – SNMP....................................................4–13
4.5 Menus and Functions - Summary ...............................................................................4–16
4.5.1 CLI - Log In.........................................................................................................4–18
4.5.2 CLI - Configure Interface Menu ..........................................................................4–19
4.5.3 CLI - Gateway Configuration Menu ....................................................................4–20
4.5.3.1 WAN Transmission Rate ................................................................................4–20
4.5.3.2 Maximum Transfer Unit (MTU) .......................................................................4–21
4.5.3.3 Compression ...................................................................................................4–21
4.5.3.4 Congestion Control.......................................................................................... 4–21
4.5.4 CLI - Route Configuration Menu........................................................................4–22
4.5.5 CLI - SNMP Configuration Menu SNMP V2 CLI Menu Display........................ 4–23
4.5.6 CLI - Selective Acceleration Menu ....................................................................4–25
4.5.7 CLI - Administrative Functions Menu ................................................................4–29
4.5.8 Web – Log In .......................................................................................................4–36
4.5.9 Web – Acceleration page ....................................................................................4–37
4.5.10 Web – Interface page ..........................................................................................4–38
4.5.11 Web – Routes page.............................................................................................4–39
4.5.12 Web – Selective Acceleration page.....................................................................4–40
4.5.13 Web – Admin page..............................................................................................4–42
4.6 Upgrade turboIP™ ......................................................................................................4–44
4.6.1 CLI - Upgrade turboIP ........................................................................................4–45
4.6.2 Web - Upgrade turboIP ......................................................................................4–46
4.6.2.1 Web - FTP Upgrade .........................................................................................4–47
4.6.2.2 Web - Upload Upgrade ...................................................................................4–48
iv
turboIPv4.0 Revision 6
Getting Started MN/TURBOIPv4.0.IOM
CHAPTER 5. SNMP .............................................................................................................5-1
5.1 MIBII Support .......................................................................................................................5-1
5.2 Private MIB Support.............................................................................................................5-1
5.2.1 turboIPv3GatewayConfiguration ...........................................................................5–3
5.2.2 turboIPv3Interface .................................................................................................5–6
5.2.3 turboIPv3Route .....................................................................................................5–6
5.2.4 turboIPv3SelectiveAcceleration.............................................................................5–7
5.2.5 turboIPv3QoSStatisticsTable ..............................................................................5–10
5.2.6 turboIPv3Compression........................................................................................5–12
5.2.7 turboIPv3Admin...................................................................................................5–12
5.2.8 turboIPv3AdminInfo.............................................................................................5–13
5.2.9 turboIPv3EventLog..............................................................................................5–13
5.2.10 turboIPv3Statistics...............................................................................................5–14
5.2.11 turboIPv3FailToWire............................................................................................5–16
5.2.12 turboIPv3HTTP....................................................................................................5–16
5.2.13 turboIPv3Notifications .........................................................................................5–17
5.2.14 turboIPv3ProcessNotifications ............................................................................5–18
CHAPTER 6. COPY PROTECTION.....................................................................................6-1
CHAPTER 7. SAMPLE CONFIGURATIONS .......................................................................7-1
7.1 Sample Configurations Introductions ...................................................................................7-1
7.2 Point-to-Point Configuration.................................................................................................7-2
7.3 Point-to-Multipoint Configuration..........................................................................................7-3
7.4 Hub-Spoke Configuration.....................................................................................................7-4
7.5 Dynamic Bandwidth Configuration.......................................................................................7-6
CHAPTER 8. END USER LICENSE AGREEMENT............................................................8–1
v
turboIPv4.0 Revision 6
Getting Started MN/TURBOIPv4.0.IOM
ABOUT THIS MANUAL
This manual provides installation and operation information for Comtech EF Data’s turboIP™
Performance Enhancement Proxy. This document is intended for network designers and operators
responsible for the operation and maintenance of the turboIP™.
CONVENTIONS AND REFERENCES
CAUTIONS AND WARNINGS
Indicates information critical for proper equipment function.
IMPORTANT
CAUTION
Indicates a hazardous situation that, if not avoided, may result in minor or moderate
injury. CAUTION may also be used to indicate other unsafe practices or risks of
property damage.
Indicates a potentially hazardous situation that, if not avoided, could result in
WARN ING
death or serious injury.
METRIC CONVERSION
Metric conversion information is located on the inside back cover of this manual. This
information is provided to assist the operator in cross-referencing non-metric to metric
conversions.
TRADEMARKS
All product names mentioned in this manual may be trademarks or registered trademarks of their
respective companies and are hereby acknowledged.
REPORTING COMMENTS OR SUGGESTIONS CONCERNING THIS MANUAL
Comments and suggestions regarding the content and design of this manual will be appreciated.
To submit comments, please contact the Comtech EF Data Customer Support Department.
vi
turboIPv4.0 Revision 6
Getting Started MN/TURBOIPv4.0.IOM
EMC COMPLIANCE
This is a Class A product. In a domestic environment, it may cause radio interference that
requires the user to take adequate protection measures.
EN55022 COMPLIANCE
This equipment meets the radio disturbance characteristic specifications for information
technology equipment as defined in EN55022
EN50082-1 COMPLIANCE
This equipment meets the electromagnetic compatibility/generic immunity standard as defined in
EN50082-1.
.
FEDERAL COMMUNICATIONS COMMISSION (FCC)
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment.
This equipment generates, uses, and can radiate radio frequency energy. If not installed and used
in accordance with the instruction manual, it may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference, in which case users are required to correct the interference at their own expense.
Note: To ensure compliance, properly shielded cables for DATA I/O shall be used.
More specifically, these cables shall be shielded from end to end, ensuring a
continuous shield.
HIGHLIGHTS OF THIS REVISON
Revised Chapter 8. End User License Agreement
vii
turboIPv4.0 Revision 6
Getting Started MN/TURBOIPv4.0.IOM
Safety Compliance
EN 60950
Applicable testing is routinely performed as a condition of manufacturing on all units to ensure
compliance with safety requirements of EN60950.
This equipment meets the Safety of Information Technology Equipment specification as defined
in EN60950.
LOW VOLTAGE DIRECTIVE (LVD)
The following information is applicable for the European Low Voltage Directive (EN60950):
<HAR> Type of power cord required for use in the European Community.
CAUTION: Double-pole/Neutral Fusing.
!
ACHTUNG: Zweipolige bzw. Neutralleiter-Sicherung.
International Symbols:
Symbol Definition Symbol Definition
Alternating Current.
Fuse.
Protective Earth.
Chassis Ground.
Note: For additional symbols, refer to “Cautions” listed earlier in this preface.
viii
turboIPv4.0 Revision 6
Getting Started MN/TURBOIPv4.0.IOM
WARRANTY POLICY
This Comtech EF Data product is warranted against defects in material and workmanship for a
period of two years from the date of shipment. During the warranty period, Comtech EF Data
will, at its option, repair or replace products that prove to be defective.
For equipment under warranty, the customer is responsible for freight to Comtech EF Data and all
related customs fees, taxes, tariffs, insurance, etc. Comtech EF Data is responsible for the freight
charges only for return of the equipment from the factory to the customer. Comtech EF Data will
return the equipment by the same method (i.e., Air, Express, Surface) as the equipment was sent
to Comtech EF Data.
LIMITATIONS OF WARRANTY
The foregoing warranty shall not apply to defects resulting from improper installation or
maintenance, abuse, unauthorized modification, or operation outside of environmental
specifications for the product, or, for damages that occur due to improper repackaging of
equipment for return to Comtech EF Data.
No other warranty is expressed or implied. Comtech EF Data specifically disclaims the implied
warranties of merchantability and fitness for particular purpose.
EXCLUSIVE REMEDIES
The remedies provided herein are the buyer's sole and exclusive remedies. Comtech EF Data shall
not be liable for any direct, indirect, special, incidental, or consequential damages, whether based
on contract, tort, or any other legal theory.
DISCLAIMER
Comtech EF Data has reviewed this manual thoroughly in order to provide an easy-to-use guide
to the equipment. All statements, technical information, and recommendations in this manual and
in any guides or related documents are believed reliable, but the accuracy and completeness
thereof are not guaranteed or warranted, and they are not intended to be, nor should they be
understood to be, representations or warranties concerning the products described. Further,
Comtech EF Data reserves the right to make changes in the specifications of the products
described in this manual at any time without notice and without obligation to notify any person of
such changes.
If you have any questions regarding the equipment or the information in this manual, please
contact the Comtech EF Data Customer Support Department.
ix
turboIPv4.0 Revision 6
Getting Started MN/TURBOIPv4.0.IOM
This page is intentionally left blank.
x
turboIP™
Performance
Enhancement
Proxy
1.1 INTRODUCTION
This User Guide provides an overview of Comtech EF Data’s turboIP™ Performance
Enhancement Proxy along with instructions on how to configure the turboIP™, starting
from factory default settings, so that it is passing traffic within minutes. It is assumed that
the reader is familiar with general IP networking principles.
1.1.1 DEFINITIONS
Term Meaning
Bridge
Byte
CLI (Command
Line Interface)
Compression
Datagram
easyConnect™
Fail to Wire (FTW)
Frame
Gateway
HTTP (Hyper Test
Transfer Protocol)
kbps (kilobits per
second)
Chapter 1. Overview
In this document, this term refers to a network element that receives
frames from one network interface and forwards them in the direction of
their destination based on their link layer addresses.
Eight bits (see Octet).
The user interface of the turboIP system that is available via the serial port.
A turboIP feature that will attempt both Header and Payload Compression
on all accelerated TCP sessions.
The portion of a PDU that corresponds to the network layer and higher,
that is, that portion that is transferred end to end between IP hosts on
different networks.
The feature of the turboIP system that allows it to operate as a bridge.
turboIP feature that will allow all traffic to automatically bypass the turboIP
in the event of a failure.
A link layer PDU.
A network device used to perform protocol conversions at a specific
protocol layer to interconnect dissimilar networks.
Protocol standard for web access.
A rate of 1,000 bits per second.
1-1
turboIPv4.0 Revision 6
Overview MN/TURBOIP.IOM
Term Meaning
LAN (Local Area
Network)
MB (Megabytes)
Mbps (Megabits
per second)
Management IP
ms (millisecond)
Octet
PDU (Protocol
Data Unit)
RTT (Round Trip
Time)
Selective
Acceleration
Session
SkipWare®
SNMP
turboIP ™
hardware
WAN (Wide Area
Network)
On the turboIP, this refers to the Ethernet port that would be attached to
the LAN.
1,048,576 Bytes (Octets).
A rate of 1,000,000 bits per second.
The IP assigned to the turboIP for management via HTTP or SNMP. On
the turboIP, both the LAN and WAN port can be accessed by the
Management IP.
A rate of 0.001 second.
Eight bits (see Byte).
The messages sent between peer entities in a protocol. The PDU includes
headers generated or consumed by the protocol implementation as well as
the data portion carried by the entity. A PDU may be segmented by a lower
layer protocol.
The elapsed time (in milliseconds) for traffic to be sent from one host and a
response received by the sending host.
The ability to provide a different quality of service to different datagrams.
The term ‘Selective Acceleration’ actually applies to all types of IPv4 traffic,
not just to accelerated sessions.
A single bi-directional TCP connection between two end systems (hosts)
SCPS-TP compliant layer-4 gateway software developed by Global
Protocols. SkipWare also provides many of the gateway (GW) functions of
the turboIP software. Skipware does
(i.e., SNMP, CLI< HTTP, etc.), GPOS, and some other turboIP software.
Simple Network Management Protocol.
The hardware platform provided by Comtech on which the turboIP
software executes.
On the turboIP, this refers to the Ethernet port that would be physically
attached to the outbound satellite equipment.
NOT include management interfaces
1-2
turboIPv4.0 Revision 6
Overview MN/TURBOIP.IOM
1.2 TCP/IP PERFORMANCE LIMITATIONS
Due to its design, TCP/IP does not perform well over impaired links. The link impairment could
be due to delay or noise or both. A typical satellite link suffers due to high delay and high noise.
The main reasons for poor TCP/IP performance over an impaired link can be summarized as:
Slow start algorithm Slow start algorithm allows a TCP sender to increase the data
transmission rate without overwhelming the network. It achieves this
goal by gradually increasing the number of unacknowledged segments
at the start of the session. The time required for an acknowledgement
over the satellite link severely limits the ramp up in transmission rate.
TCP window size The most unacknowledged data that a TCP sender can have
outstanding is limited by the sender’s window size. This limits the
transmission rate in the steady state to Window_Size/Round_Trip_Time
(e.g., for a typical receive windows size of 64 kbytes and satellite round
trip time of 540 ms, the maximum throughput is limited to approximately
121 kbps).
Congestion avoidance
algorithms
The congestion avoidance and control mechanism of TCP attributes
packet loss to network congestion, as opposed to corruption due to
noise in the channel. This leads to drastic reduction in transmission
rates. Recovery from congestion is slowed due to the high round trip
time and noise in the satellite channel.
1.3 TCP/IP PERFORMANCE ENHANCEMENT PROXY
Comtech EF Data’s turboIP™ Performance Enhancement Proxy is designed to alleviate TCP/IP
bottlenecks in an impaired environment (high delay, high bit error rate, or both), while preserving
interoperability with any TCP device. It achieves this by combining TCP with a number of
enhancements that modernize IP transport.
turboIP™ is based on SCPS-TP, the Transport Protocol of SCPS, an open standard specifically
defined for space communications. This standard is open, published, and internationally
distributed. SCPS-TP is an ISO standard (15893), a CCSDS standard (714.0-B-1), and a MILSTD (MIL-STD-2045-44000).
turboIP™ is fully compatible with network devices that use TCP, supporting existing Internet
standards, including network congestion and retransmission schemes. This allows turboIP™ at
one end of the link to operate with TCP devices at the other end of the link without the need for a
peer turboIP™ device, providing partial performance enhancement. However, it is recommended
that TCP traffic pass through a pair of turboIP
take full advantage of the SCPS-TP protocol.
TM
Performance Enhancement Proxies, in order to
1-3
turboIPv4.0 Revision 6
Overview MN/TURBOIP.IOM
The key features of turboIP™ that help alleviate TCP/IP performance bottlenecks are:
Quick Start turboIP™ makes full and immediate use of the links available, eliminating
the inefficiencies of the TCP slow-start algorithm.
Window Scaling turboIP™ supports window sizes up to 1 Gbyte, far exceeding the standard
TCP window size of 64 Kbytes.
Intelligent
Congestion
Control
Rate Pacing
Per-Connection 1turboIP™ Version 4.0 adds Per-Connection Mode to support dynamic
Selective
Negative
Acknowledgments
(SNACKs)
1
Note: With turboIP™ Version 4.0, either Rate Pacing or Pre-Connection Mode can be
selected to optimize TCP acceleration performance.
1
turboIP™ is optimized for real-world, mixed-loss environments. It is capable
of distinguishing data corruption from congestion-induced data loss. Doing
so prevents unnecessary activation of congestion control mechanisms,
which can lead to significant reductions in transmission rates.
turboIP™ meters out bursty traffic at a rate not to exceed the configured
transmission rate of the satellite channel. This prevents the satellite channel
from becoming congested.
bandwidth paths, where the bandwidth may be different for any of the paths
being accelerated by the turboIP.
SNACKs identify specific lost or damaged packets and request
retransmission of those packets. This provides for quicker recovery and
better bandwidth utilization in lossy environments.
Rate Pacing Mode Should be used when the bandwidth path for accelerated TCP
traffic remains constant with the set WAN Transmission Rate.
Per-Connection Mode Should be used to support dynamic bandwidth paths, where the
bandwidth may be different for any of the paths being accelerated
by the turboIP.
1.4 SELECTIVE ACCELERATION
Selective Acceleration implemented by the Comtech turboIP is a mechanism for providing
different quality of service (QoS) for different datagrams. Selective Acceleration only applies to
IPv4 datagrams that are received on the LAN interface and forwarded to the WAN interface.
Selective Acceleration is implemented as an ordered table of rules that determine the QoS to be
provided for traffic passing through the turboIP. The rules have three parts: an accounting part
that specifies the location and status of the rule in the table, a filter part that matches the
datagram’s passing through the turboIP to each rule, and a QoS part that determines how the data
that matches the rule is to be treated. Each rule can specify that either all packets matching the
rule be dropped or the following QoS parameters be applied:
• A priority level
• A maximum data rate (bandwidth) for all traffic matching the rule
• Whether or not to accelerate TCP sessions matching the rule (i.e., invoke
SCPS-TP)
1-4
turboIPv4.0 Revision 6
Overview MN/TURBOIP.IOM
1.5 DA TA AND HEADER COMPRESSION
The turboIP supports header and payload compression of accelerated TCP traffic. Compression is
enabled or disabled by a global setting. If it is enabled, both header and data compression will be
attempted on all new accelerated sessions. Compression will be negotiated during the TCP
connection establishment. Therefore, even if the turboIP has compression enabled, and if the peer
turboIP does not also have compression enabled, then the session will not be compressed.
Data compression on accelerated TCP flows will be handled on a segment-by-segment basis. The
compressibility of each segment payload will be evaluated individually and only those segments
where the impacts would be beneficial will be compressed.
If a session is to be compressed, then the segments corresponding to that session will be
compressed only if:
1. the uncompressed payload length is greater than 90 octets;
and,
2. the compressed length is not larger than two octets smaller than the uncompressed
length.
1.5.1 MINIMUM COMPRESSION RATIO
The compression ratio is defined as the ratio of the sum of the sizes of all TCP segments in an
uncompressed session to the sum of the sizes of the TCP segments if that same session were
compressed. Note that this is different from the definition used in the compression ratio statistic.
A minimum compression ratio of 1.91:1 shall be achieved with the Canterbury corpus and 1.63:1
with the Calgary corpus, when the data is transferred through the turboIP using FTP.
The turboIP shall never produce a compression ratio less than 1 with any data, that is, the size of
the compressed flows shall always be less than or equal to the size that the flow would have been
if compression were disabled for that flow.
1-5
turboIPv4.0 Revision 6
Overview MN/TURBOIP.IOM
1.6 turboIP PHYSICAL DESCRIPTION AND SPECIFICATIONS
Figure 1-1. turboIP Front Panel View
Front Panel Control/LEDs
ON/OFF Recessed power reset switch
POWER Green when power is applied
LAN/LINK Green when LAN Port senses 10/100 Base-T link
LAN/ACT Flashing amber when LAN Port sense s Ethernet Activity
WAN/LINK Green when WAN Port senses 10/100 Base-T link
WAN/ACT Flashing amber when WAN Port senses Ethernet Activity
Figure 1-2. turboIP Rear Panel View
Rear Panel Connectors
CONSOLE EIA-232 Female 9-pin for serial console CLI
WAN RJ-45, 10 Base-T/100 Base-T Ethernet, Auto-Sensing
LAN RJ-45, 10 Base-T/100 Base-T Ethernet, Auto-Sensing
1-6
turboIPv4.0 Revision 6
Overview MN/TURBOIP.IOM
Physical Specifications and Approvals
Temperature Operating: 5° to 45°C (41° to 113°F)
Storage: 0° to 75°C (32° to 138°F)
Humidity Operating: 5 to 95% @ 40°C (104°F), non-condensing
Vibration Operating: 5 to 17 Hz, 0.1” double amplitude displacement
17 to 500 Hz
1.5G acceleration peak-to-peak (maximum)
Shock Operating: 15G acceleration peak (1 ms duration)
Safety UL/CSA/TV/CE/FCC
EMI Meets FCC/VDE Class A
Power Supply 90~132 VAC or 180~260 VAC
@ 47~63 Hz, 150W maximum
Chassis
Dimensions
Weight
Heavy duty steel with aluminum front panel
19.0W x 1.75H x 18.4D inches
(48.3 x 4.45 x 46.7 cm)
12 lbs (5.44 kg)
Cooling Fans Qty. 2, 6.3 CFM sleeve cooling fans (rear)
1-7
turboIPv4.0 Revision 6
Overview MN/TURBOIP.IOM
This page intentionally left blank.
1-8
Chapter 2. Fail to Wire
2.1 DESCRIPTION
The Fail to Wire (FTW) function provides a low-cost solution for high network
availability. If the unit fails, then the installed FTW board allows traffic to bypass the
turboIP™ as if it were simply a wire. This means that a unit failure will not bring down
the whole network. Traffic will continue to pass and, at most, the existing TCP sessions
will be terminated and have to be restarted. The FTW functionality provides network
reliability without the added cost of one-for-one redundancy.
2.2 FAIL TO WIRE BOARD OPERATION
If the turboIP fails (excluding loss of power), then the FTW board switches into “wire”
mode approximately 7 to 10 seconds after the failure. At this time, all traffic is bypassed
around the turboIP. All active TCP sessions will timeout and need to be restarted. Newly
started TCP sessions will be bypassed around the turboIP without acceleration.
If turboIP reboots, then the FTW board switches to wire mode seven to 10 seconds after
the reboot is initiated, and stays in “wire” mode until the reboot is completed. Hence, 7 to
10 seconds is the extent of network outage caused by a reboot of the turboIP.
If the turboIP loses power, then the FTW board immediately switches into “wire” mode.
Approximately one second of traffic is lost during this switch. In addition, all TCP
sessions will timeout and have to be restarted.
While the turboIP is off, the FTW board is in “wire” mode and all traffic is bypassed
around the turboIP. When the turboIP is powered on again, the FTW board switches from
“wire” mode to “normal” mode during which time no traffic passes through the turboIP
for 7 to 10 seconds. After this period, the board will switch back into “wire” mode and
bypass traffic around the turboIP for 33 seconds while turboIP is booting. When the
turboIP finishes bootup, the FTW board switches from “wire” mode to “normal” mode
and the turboIP begins normal operations. About one second of traffic loss is possible
during this final switch.
2-1
turboIPv4.0 Revision 6
Fail to Wire MN/TURBOIP.IOM
2.3 FAIL TO WIRE BOARD INSTALLED
If the Fail to Wire (FTW) board is installed in the turboIP, then the last four characters of
the Unit ID on the Upgrade page will read “FWFD”.
The presence of a FTW board can be verified by looking at the Unit ID on both the HTTP
interface and the CLI interface as shown below.
2-2
turboIPv4.0 Revision 6
Fail to Wire MN/TURBOIP.IOM
2-3
turboIPv4.0 Revision 6
Fail to Wire MN/TURBOIP.IOM
2.4 NO FAIL TO WIRE BOARD INSTALLED
If no FTW board is installed as part of the turboIP, then the last four characters of the
Unit ID on the Upgrade page will read “00FF”. Without a FTW board installed in the
turboIP this feature is unavailable. The unit will detect the absence of FTW capability
and not be able to switch into “wire” mode during possible failures or reboots.
The absence of a FTW board can be verified by looking at the Unit ID on the HTTP
interface and the CLI interface as shown below.
2-4
turboIPv4.0 Revision 6
Fail to Wire MN/TURBOIP.IOM
2-5
turboIPv4.0 Revision 6
Fail to Wire MN/TURBOIP.IOM
This page intentionally left blank.
2-6
Chapter 3. easyConnect™
easyConnect™ is Comtech EF Data’s intelligent networking technology intended to
allow easy integration of turboIP™ into existing networks. It also simplifies design and
installation of a new network. It reduces network reconfiguration that is required when
introducing turboIP into an existing link. easyConnect™ can be turned ON after
turboIP V3.0 or later.
3.1 easyConnect™ ON
With easyConnect™ enabled, turboIP™ can be added to existing links without impacting
existing non-TCP traffic and without having to reconfigure existing network devices. It
also reduces the complexity when designing and installing a new network.
easyConnect™ mode:
All IP and Non-IP traffic is transparently bridged.
IP multicast is transparently bridged
Unicast IP datagrams that do not contain TCP payload are transparently bridged,
and can be assigned a Priority or bandwidth restriction with Selective
Acceleration Rules.
Unicast IP datagrams that contain TCP payload can be assigned a Priority or
bandwidth restriction with Selective Acceleration Rules. Also, Selective
Acceleration can be used to designate which TCP traffic is accelerated and which
is not accelerated.
With easyConnect™ mode, the unit has only one IP address (Management IP Address)
that both the LAN and WAN port will respond to.
3-1
turboIPv4.0 Revision 6
easyConnect MN/TURBOIP.IOM
3.2 Important easyConnect Notes
1. With easyConnect™ mode, the turboIP™ cannot be the default gateway or the
next hop for any locally attached devices. Instead, the turboIP will work as a
IMPORTANT
transparent bridge.
2. For any turboIP
Route Table for TCP traffic to be forwarded through the turboIP. With V4.0,
Route entries are only needed to allow Web access or FTP upgrades of the
turboIP from an outside network
with SW earlier then V4.0, entries must be made into the
3-2
Chapter 4. Configuring turboIP™
4.1 IMPORTANT CONFIGURATION NOTES
1. turboIP™ must be placed in the link such that it has visibility of TCP
traffic in both directions, i.e., the forward traffic as well as the TCP
CAUTION
acknowledgments must go through the unit. If the unit is placed such that it
only has visibility of forward traffic or TCP acknowledgments, all such
TCP sessions through turboIP™ will not be accelerated.
2. During configuration of turboIP™, a reboot is required for the three
following changes; all other changes are immediately in effect:
a. Initial Configuration Wizard
b. Restore to Factory Defaults
c. Upgrading of the Unit
4.2 REQUIRED EQUIPMENT LIST
In addition to the Ethernet cables and Ethernet switches/hubs required to connect
turboIP™ to the network, the following equipment is required for the console connection:
1. DB-9 (female) to DB-9 (male) straight-through modem cable
2. PC running terminal emulation program (such as HyperTerminal)
4–1
turboIPv4.0 Revision 6
Configuring turboIP MN/TURBOIP.IOM
4.3 USER INTERFACES
turboIP™ supports a basic menu-driven interface, which is accessible using the console
port, or a web-based graphical user interface (GUI). The interfaces contain the same
functionality, with one exception. The USERID and PASSWORD are only configurable
via the console connection, for obvious security reasons.
CONSOLE SETTINGS
IMPORTANT
Baud Rate
Data Bits
Parity
Stop Bits
Hardware Flow Control
Software Flow Control
Terminal Emulation
Cable Configuration
38,400 bps
8
None
1
None
None
VT100/VT100J
Straight - Through
1. Entry of the numeric pad’s arrow keys when the NumLock is OFF
will work under Hyperterminal, provided that the client is running
Windows 2000, Service Pack 4. Microsoft has acknowledged a
bug for Hyperterminal shipped with Windows 2000 prior to Service
Pack 2 where the arrow keys were non-functional.
(
http://support.microsoft.com/default.aspx?kbid=263077).
2. Web-based graphical user interface (GUI) CAN ONLY be turned on
in CLI. End-user is required to run Configuration Wizard for initial
setup or log into CLI Menu to ENABLE “Web User Interface.’
4–2
Loading...