Terminal access refers to the access of a
terminal device to a router through an asynchronous interface for data intercommunications
with remote UNIX servers or other terminal devices.
Terminal access initiator is the device
that initiates the TCP connection request to the peer. As the TCP connection
client, a terminal access initiator is usually a router, while as the TCP
connection server, a receiver can be a UNIX front end processor (FEP) or a
router. Both the UNIX server and the UNIX FEP mentioned in this manual refer to
an FEP with the UNIX operating system and server program installed.
Once a TCP connection is established, a
router, functioning as the terminal access initiator or receiver, can
transparently transmit the data from the terminal device to the peer over the
TCP connection. Transparent means that no manual or extra operation is
required.
Terminal access is widely used in systems
adopting the UNIX-server to terminal model, for example, bank, post office,
revenue office, customhouse, and civil aviation systems. The diverse terminal
access applications fall into four categories: TTY terminal access, Telnet
terminal access, and RTC (remote terminal connection) terminal access. The
client and server in RTC terminal access are used for the connection of
monitoring center and monitored terminals, while TTY terminal access and Telnet
terminal access are for the scenarios where the initiator is a router and the
receiver is a UNIX server. They have different features and functions, which
are described in the following sections.
In TTY terminal access, a router acts as
the terminal access initiator while a UNIX server acts as the receiver over the
TCP connection, and the router transparently transmits data between terminals
and the UNIX server. The application service interacts with the initiator (the
router) via the ttyd program running on the UNIX server and sends the service
interfaces to the terminals at the business sites, implementing interactive
service processing.
The TTY terminal access solution implements
the fixed terminal number function and offers many enhanced functions such as
dynamic multi-service switching, realtime screen saving, terminal reset, and
data encryption. Meanwhile, the UNIX server provides professional terminal
management software, enriching the system functions while simplifying the
management. In addition, the combination of terminal access and router makes remote
offices possible and implements IP telephony easily, delivering a solution for
high efficient networks with various functions.
The following is a typical networking
diagram for TTY terminal access.
Figure 1-1 Network diagram for TTY terminal
access
In Figure 1-1, the terminals at the business sites are connected to the router at the subsidiary bank through terminal access-enabled routers, and are thus connected to the UNIX FEPs. The UNIX FEPs, which run the banking
services, send various service interfaces through the routers to the terminals,
while the information entered by operators at the business sites are
transferred to the UNIX FEPs, implementing the data exchange between the
business sites and the subsidiary bank.
Telnet terminal access is the remote login
function of a terminal by using the standard Telnet client mode. In Telnet
terminal access, a Telnet connection is first established between the router
and the UNIX FEP before a data channel is set up between the terminal and the
UNIX FEP.
Telnet terminal access on routers supports
these basic functions:
l
A terminal supports up to eight virtual
terminals, and the virtual terminals on a terminal can employ TTY terminal
access or Telnet terminal access.
l
Virtual terminal switching through a menu
l
Quick virtual terminal switching
l
Screen saving on the terminal
The typical networking scheme for Telnet
terminal access is similar to that for TTY terminal access.
Remote terminal connection (RTC), another
typical way for terminal access, utilizes routers to connect local terminals to
remote terminals for data intercommunications. It includes two modes:
synchronous mode and asynchronous mode.
I. Asynchronous RTC
As shown in Figure 1-2, both the monitoring terminals at the data center and the monitored terminals at the remote end are connected to the routers through asynchronous interfaces, implementing data intercommunications over the IP
network. Generally, the router connecting the monitoring terminals at the data
center acts as the terminal access initiator (the RTC client) and can initiate
connections at any time to obtain data from the monitored terminals. The router
connecting the monitored terminals acts as the terminal access receiver (the
RTC server) and is always ready to receive the connection requests from the
data center and send monitored data in response.
Figure 1-2 Network diagram for async RTC
This kind of RTC can be used for the following
purposes:
l
Managing and monitoring remote terminals from
the data center.
l
Collecting data on the remote terminals.
l
Fulfilling the functions of a multiplexing
device and transmitting data over IP networks for easy network upgrade.
II. Synchronous RTC
Synchronous RTC can be used in two types of
networking schemes: one-to-one and many-to-one.
1)
Synchronous RTC in one-to-one topology
Figure 1-3 Synchronous RTC in one-to-one
topology
Similar to asynchronous RTC application
mode, either of the monitoring terminal in the data center and the remote
monitored terminal is connected to the synchronous interface of a router in
this topology.
2)
Synchronous RTC in many-to-one topology
(specially for synchronous radar access)
As shown in Figure
1-4, multiple radars are connected to the routers serving as their RTC clients to synchronize information with each other through a sync server, which forwards data transparently. Note that the sync server is not a sync
RTC server. No sync RTC server is required in many-to-one topology.
Figure 1-4 Synchronous RTC in many-to-one topology
Synchronous RTC works on these principles:
l
When a radar needs to synchronize its
information to the others, it initiates a connection request to the sync server
through its RTC client.
l
When the sync server, whose responsibility is to
listen to connection requests from the RTC clients, receives the request, it
establishes a TCP connection.
l
After the TCP connection is successfully
established, the RTC client that initiates the connection request sends the
data packets of the radar to the sync server.
l
Upon receiving the data packets, the sync server
copies them into each of the buffers of the other RTC clients and forwards them
out.
l
Upon receiving the data packets, each of the RTC
clients except for the connection initiator forwards the data packets to its
radar. The information synchronization among radars is thus done.
Note that the sync server is not a
traditional terminal access server; it does not connect terminals together, but
helps in synchronizing information among radars. You can configure one of the
RTC clients as the sync server to reduce cost.
At present, only
the fixed serial interfaces of the 8SAE card support synchronous RTC.
III. HDLC over UDP
1)
Introduction to HDLC over UDP
With the widespread use of IP, the previous
physical network is far from satisfying the demands of growing services. It is
needed to expand the network capacity. In addition, delay in data transmission
exists in the previous HDLC over TCP application due to the extensive use of
voice services and the features of TCP. Considering the fact that voice data
transmission places lower requirement on reliability, UDP can be adopted to
transmit data. The HDLC over UDP now has become a new method for voice data
transmission. It has the advantages as follows:
l
Does not require TCP handshaking, which shortens
the transmission process;
l
Places less strict requirement for data
reliability and does not need to save data upon transmission failure, thus
cutting down the time interval between data frames;
l
Does not perform retransmission upon failure,
which drastically reduces time delay.
2)
Work mechanism of HDLC over UDP
One-to-one HDLC over UDP is a UDP-based
one-to-one data transparent transmission method. A serial terminal transmits
data to the router connected with it through synchronous serial port. The
router, according to the previously configured information, transmits the data
to its peer router via IP network by using UDP service. The peer router further
sends the received data to its connected terminal. This is the process of
one-to-one transparent transmission of synchronous data on serial terminal over
IP network.
One-to-many HDLC over UDP is a UDP-based
one-to-many synchronous data transparent transmission method generally used for
voice data transmission that places lower requirement on reliability and higher
requirement on a small time delay. One data sender and multiple data receivers
exist when data is transmitted in one-to-many HDLC over UDP mode, thereby
implementing one to many data transmission.
3)
Basic concepts in HDLC over UDP
l
Server end and client end
The concepts of server end and client end
are not defined for UDP. However, to transmit data, the interface IP address
and port number for transparent transmission at either router must be fixed.
The one with fixed interface IP address and port number is the server end, and
the peer router is the client end, which knows the IP address and port number beforehand.
l
Serial terminal
In this manual, the terminal equipped with
serial port is referred to as serial terminal. The serial terminal generates
the data to be transmitted transparently, and it is connected to the
synchronous serial port of the router through its synchronous serial port. The
transmission rate between the serial terminal and the router is 9600 bps.
l
Server-end transparent transmission router
The server-end transparent transmission
router, with fixed interface IP address and pre-defined port number, is used
for transparent transmission. The IP address and port number of the client end
can be specified at the server end. Only the client with the same IP address
and port number with the specified ones can access the server.
l
Client-end transparent transmission router
The client-end transparent transmission
router is the peer router of the server-end transparent transmission router.
Its interface IP address used for transparent transmission can be unfixed, i.e.
variable, during transmission. The local port number can be user-defined or
system-generated. The client end must specify the IP address and port number of
the server end.
The following figure illustrates the
terminal access features.
Figure 1-5 Network diagram for terminal
access functions
I. Fixed terminal numbering
As shown in Figure 1-5, the terminal access program running on the router enables the terminals (TTYs) to access the UNIX FEPs. The terminals are connected to the router through async serial interfaces. The router numbers all the
terminals. On the other side, the router connects to multiple UNIX FEPs across
the network. Each UNIX FEP runs multiple applications (APPs). Terminal access
numbers the applications running on the FEPs serially. The numbering of the
terminals and the applications and the special processing of the router
contribute to the mapping between the terminals and the banking applications,
implementing fixed terminal numbering.
Note that this function is available only
for TTY terminal access.
II. Virtual terminal switching
The characteristics of banking services
require each bank to provide services such as deposit services and public
services. However, a terminal at a business site can only process one type of
service. To solve this problem, the terminal access feature of the router
implements the virtual terminal switching function, enabling a terminal to
process multiple services and to switch between the services dynamically.
Terminal access divides each terminal into
eight VTYs logically, each of which can be configured to correspond to an
application. An operator of a terminal can press the virtual terminal switching
menu hotkey to bring up the virtual terminal switching menu and select a
virtual terminal to switch to it dynamically. This allows more flexible use of
terminal access.
In addition, terminal access provides the
screen saving function. When an operator switches from service 1 to service 2,
the operating interface of service 1 is automatically saved. When the operator switches
from service 2 back to service 1, the original operating interface is
automatically restored. If the original operating interface is lost, the
operator can use the terminal redrawing function to recover it.
TTY terminal access and Telnet terminal access
support the virtual terminal switching function.
III. Terminal access networking
mode
Based on its rich experience in financial
field, H3C Technology offers two terminal access networking modes to satisfy
the needs of customers: one-to-one and many-to-one.
Terminal access is typically used in
one-to-one mode. In this mode, each terminal communicates with the UNIX server
over a TCP connection. The advantage of this mode is that the optimum
communication quality and speed can always be achieved, even over a low speed
link when you only need to adjust some parameters to obtain a very high
terminal echo speed. Massive printing requirements of users can also be
satisfied in this mode. This mode supports all the functions of the terminal
access feature. Generally, you are recommended to use one-to-one mode.
Many-to-one access mode applies to
scenarios where the FEPs have to support a large number of terminals and the
load is heavier than that in one-to-one mode. In this mode, the traffic to the
same application on all terminals is multiplexed onto a single TCP link.
Compared to other solutions such as one-to-one mode and dumb terminals with
Telnet, this mode can considerably reduce the consumption of UNIX server
sockets. Many-to-one mode supports only a portion of the functions of the
terminal access feature.
In both many-to-one and one-to-one modes, a
terminal access specific protocol is employed for data encryption to satisfy the
special requirements of financial users on security of sensitive data. This ensures
the user data security to the utmost, vindicating the benefit of users.
Currently, the terminal access function supports
all the mainstream UNIX versions on the market: SCO OpenServer 5.0.5, SCO
UnixWare 7.1 (supporting only one-to-one mode), Sun OS 5.7, IBM AIX 4.3.3, HP
UX 10.20 and 11.0. Support for other UNIX versions will be included in the
future version of terminal access.
IV. Data encryption
Due to the extensive use of terminal access
in banking systems, the requirement for data security becomes higher and
higher. Using the terminal access data encryption function can encrypt the data
transmitted between the terminal access router and UNIX FEPs to improve data
security. Data encryption is mainly for TTY and Telnet terminal access.
Data encryption between the router and the
UNIX FEPs is implemented by software. The following figure illustrates the
encryption procedure.
Figure 1-6 Data encryption procedure
between the router and the UNIX FEPs
As shown in Figure
1-6, traffic encryption between the terminal access router and the UNIX FEPs is implemented by a program running on terminal access router and the UNIX ttyd program running on FEP.
V. Source IP address binding
The TTY terminal access receiver is a UNIX
server. The ttyd program running on the UNIX server needs to authenticate the
IP address of the connected router. When dialup is deployed on the WAN for
redundancy, if the primary link goes down, the router will enable the backup
interface. At the moment, the IP address of the router will change, causing the
ttyd program to fail the authentication. To avoid this problem, you can bind a
source IP address for the application on the router, making the application use
a fixed IP address to establish the TCP connection with the UNIX server. This
is what is called source IP address binding.
To bind a source IP address, you must
configure an IP address for a free interface on the router (the loopback or
dialer interface is recommended) at first, and then use that IP address as the
source IP address of the upstream TCP connection on the router. Source IP
address binding hides the real source IP address of the TCP connection and thus
can satisfy the special security requirements of users.
1.2.2 Terminal Access Functionality
The following table lists the functionality
supported by terminal access.
Table 1-1
Terminal Access Functionality
|
Item
|
Supported terminal access type
|
|
Source address binding
|
All
|
|
Terminal menu
|
TTY, Telnet
|
|
Fast virtual terminal service switching
|
TTY, Telnet
|
|
Virtual terminal redrawing
|
TTY
|
|
Idle timeout of the connection
|
All
|
|
Terminal number fixing
|
TTY
|
|
Data encryption (terminal side)
|
TTY, Telnet
|
|
Data encryption (UNIX side)
|
TTY
|
|
Auto-link
|
TTY, Telnet, sync/async RTC client
|
|
Automatic link teardown
|
All
|
|
One-to-one access
|
TTY
|
|
Many-to-one access
|
TTY
|
|
Terminal display language configuration
|
TTY, Telnet
|
|
Screen saving
|
TTY, Telnet
|
|
Data read blocking on the terminal access
receiver
|
TTY
|
|
Terminal reset
|
TTY, Telnet
|
|
Connectivity test
|
TTY
|
|
Terminal receiving delay
|
TTY, Telnet
|
|
TCP buffer configuration ( tcp sendbufsize,
tcp recvbufsize)
|
All
|
|
TCP keepalive configuration
|
All
|
|
TCPNODELAY attribute configuration
(nodelay)
|
All
|
|
Driver buffer and sending buffer configurations
|
All
|
|
Threshold configuration for automatic virtual
terminal switching failure times
|
Async RTC client
|
|
Virtual terminal switching rule
configuration on the receiver side.
|
Async RTC server
|
|
RTC terminal authentication
|
Async RTC client, async RTC server
|
|
Terminal access multi-instance
|
TTY, Telnet, async RTC client, sync RTC
client
|
|
Statistics support
|
All
|
|
Debugging information support
|
All
|
TCP buffers (tcp
send buffer/tcp recv buffer)
are intended for buffering the packets to be sent to or received from the TCP
connections. Driver buffer/send buffer is for buffering packets to be received
from or sent to the terminals.
The following table describes the main
specifications of the terminal access initiator.
Table 1-2
Specifications of the terminal access initiator
|
Item
|
Description
|
|
Maximum number of TTYs supported by the
router
|
255. The actual number of TTYs depends on
the number of the async/sync serial interfaces on the router. For TTY
terminal access, it also depends on the number of the UNIX FEPs, meaning the number
of the ttyp processes.
|
|
Maximum number of APPs supported by the
router
|
2040
|
|
Maximum number of VTYs supported by each
TTY
|
8
|
|
Types of interfaces supported by terminal
access
|
Async serial interface: 3AS, 8AS, 16AS,
8ASE, 16ASE
Sync serial interface: 2SA, 4SA, 2S1B, 8LSA,
4SAE, 8SAE
Modem dialup interface: 1/2/6/12 AM
|
|
Terminal emulation type
|
VT100
|
|
Terminal baud rate
|
300 bps to 115,200 bps
|
The following table describes the main
specifications of the terminal access receiver.
Table 1-3
Specifications of the terminal access receiver
|
Item
|
Description
|
|
Supported maximum number of TTYs
|
255. The actual number of TTYs depends on
the number of the async/sync serial interfaces on the router.
|
|
Maximum number of remote terminal
connection APPs
|
2048
|
|
Maximum number of VTYs supported by each
TTY
|
8
|
The following table describes the main
specifications of the terminal access UNIX FEP.
Table 1-4
UNIX FEP Specifications
|
Item
|
Description
|
|
Maximum
number of virtual terminals supported by a UNIX FEP
|
250
|
|
Supported UNIX versions
|
SCO OpenServer 5.0.5
SCO UnixWare 7.1 (only for one-to-on
mode)
Sun OS 5.7
IBM AIX 4.3.3
HP UX 10.20,11.0
|
This chapter describes the procedure and
methods for configuring terminal access. If you are familiar with terminal
access configuration, you may skip this chapter.
When configuring terminal access, you must
configure the initiator and receiver as needed respectively. For RTC, both the
initiator and the receiver are routers, while for TTY terminal access and
Telnet terminal access, the initiator is a router and the receiver is a UNIX
FEP.
The commands for configuring the terminal
access initiator can be divided into these three types according to their
functions: basic configuration command, enhanced configuration command, and
displaying and debugging command. The basic configuration commands are those
that are required for the terminal access initiator to operate normally. The
enhanced configuration commands are those required to utilize the enhanced
functions provided by the terminal access initiator. The displaying and
debugging commands are those for displaying and debugging the terminal access
initiator. You can find a concise syntax description of the basic and enhanced
configuration commands in the text and the complete syntax description in
Appendix B. The introduction to the displaying and debugging commands is in
Appendix B.
The commands for configuring the terminal
access initiator can be executed in system view, interface view, or terminal
template view respectively. Most basic configuration commands and all enhanced
configuration commands must be executed in terminal template view. All
debugging commands must be executed in user view, while the displaying commands
can be executed in any view.
Most important configuration tasks must be
accomplished in the template. Once establishing a template, you can enter
template view to perform configuration tasks, just as you do with an interface.
You can configure the router parameters that are relatively fixed and save the
settings to the template. When applying the template to the appropriate
interface, (an async interface, for example), you create a TTY according to the
contents of the template and the specified terminal number, and set up a
virtual terminal on the basis of the configuration information in the template.
If you modify a template that was applied to an interface, you may use the
update command to update the terminal configuration. For ease of use, you can
configure multiple templates and apply them to appropriate interfaces.
For RTC, the initiator is the router
connecting the monitoring device. For TTY and Telnet terminal access, the
initiator is the router connecting the terminal.
Terminal access divides each terminal into eight VTYs logically,
each of which can be configured to correspond to an application. You can
configure the connection type and attributes for each VTY.
I. Enabling terminal access
Enabling terminal access is a must for
operation.
Perform the following configuration in
system view.
Table 2-1
Enable terminal access
|
To do…
|
Use the command…
|
Remarks
|
|
Enable terminal access
|
rta server enable
|
—
|
|
Disable terminal access
|
undo rta server enable
|
—
|
II. Entering terminal template
view
Perform the following configuration in system
view.
Table 2-2 Create and enter a terminal template view
|
To do…
|
Use the command…
|
Remarks
|
|
Create a template and enter its view
|
rta template template-name
|
—
|
In template view, you can continue with the
basic configuration and other enhanced configuration tasks. To delete a
template, execute the undo rta template template-name command in
system view.
When you configure
this command, if the specified template does not exist, the system creates it
and then enters its view.
III. Configuring the template
Most terminal access configuration tasks
must be accomplished in template view. Such tasks include the following:
l
Configure TTY terminal access (configure the
virtual terminal type as TTY)
The basic configuration must be done first.
Perform the following configuration in template view.
Table 2-3
Basic TTY terminal access configuration
|
To do…
|
Use the command…
|
Remarks
|
|
Configure a virtual terminal
|
vty vty-number
tty remote ip-address port mode [source srcip]
|
—
|
Up to eight virtual terminals (0 to 7) can
be configured on a terminal. Each virtual terminal corresponds to a service
application on the UNIX server. You must configure such parameters as the
access mode, the peer address, and the port number for each virtual terminal.
TTY virtual terminal and Telnet virtual terminal can be configured in a same
template, but they cannot be configured together with the other types of
virtual terminals.
After finishing the basic configuration,
you must perform some enhanced configuration according to your application
requirements in template view. To remove a configured virtual terminal, execute
the undo vty vty-number command. For detailed configuration,
refer to the relevant contents in Chapter 3 “TTY Terminal
Access Configuration”.
l
Configure Telnet terminal access (configure the
virtual terminal type as Telnet)
The basic configuration must be done first.
Perform the following configuration in template view.
Table 2-4
Basic Telnet terminal access configuration
|
To do…
|
Use the command…
|
|
Configure a virtual terminal
|
vty vty-number
telnet remote ip-address [port] [source
src-ip]
|
After finishing the basic configuration,
you must perform some enhanced configuration according to your application
requirements in template view. To remove a configured virtual terminal, execute
the undo vty vty-number command. For detailed configuration,
refer to the relevant contents in Chapter 4 “Telnet Terminal
Access Configuration”. Telnet virtual terminal and TTY virtual terminal can be
configured in a same template, but they cannot be configured together with the
other types of virtual terminals.
l
Configure RTC (Only configuration of the
terminal access initiator is given here. The virtual terminal type is
rtc-client.)
The basic configuration must be done first.
Perform the following configuration in template view.
Table 2-5
Basic RTC terminal access configuration
|
To do…
|
Use the command…
|
|
Configure a virtual terminal
|
vty vty-number
rtc-client remote ip-address port [ host-id ] [
source src-ip ]
|
After finishing the basic configuration,
you must perform some enhanced configuration according to your application
requirements in template view. To remove a configured virtual terminal, execute
the undo vty vty-number command. For detailed configuration,
refer to the relevant contents in Chapter 5 “RTC Configuration”.
IV. Applying the template to an
interface
After finishing template configuration, you
must apply the template to an appropriate interface to create a terminal for
terminal access. To apply the template to an async interface, follow these
steps:
Step 1: Enter the async interface view.
Perform the following configuration in
system view:
interface async interface-number
Step 2: Apply the template to the async
interface.
Perform the following configuration in the async
interface view:
undo async mode
async mode terminal terminal-name tty-number
For synchronous RTC terminal access, you
must apply the template to a sync interface. To do so, perform the following
configuration:
sync mode terminal template tty-number
All enhanced configuration commands must be
executed in template view. When you apply a terminal template to an interface,
all configurations made for the template are applied to the interface. If you
modify a template that has been applied to an interface, you must execute the update
changed-config command in template view to make the changes take effect.
You are recommended to complete all terminal template configurations before
applying the template to an interface.
A template can be applied to multiple interfaces, as long as you
specify different TTY numbers.
For TTY terminal access, you must configure
the receiver and the UNIX FEP. For detailed configuration, refer to Chapter 3 “TTY Terminal
Access Configuration”.
For Telnet terminal access, there is no
need to configure the receiver and the UNIX FEP.
For RTC, you must configure the router
acting as the receiver. The required configuration procedure is similar to that
for the initiator. The difference is that you must configure the virtual
terminal as the RTC server. Note that the RTC initiator and receiver have
different configurable options. For detailed configuration, refer to Chapter 5 “RTC Configuration”.
Chapter 3
TTY Terminal Access Configuration
Refer to section 1.1
“Introduction to Terminal Access”.
Perform the configuration described in the
following sections according to the procedure in Chapter
2 “Terminal Access Configuration”.
I. Enabling/Disabling terminal
access
Perform the following configuration in
system view.
Table 3-1
Enable/Disable terminal access
|
To do…
|
Use the command…
|
|
Enable terminal access
|
rta server enable
|
|
Disable terminal access
|
undo rta server enable
|
By default, terminal access is not enabled.
This configuration task merely enables the
terminal access function. To implement terminal access, you must continue to
complete the following configuration. Once the router successfully establishes
a TCP connection with the UNIX server, the terminal will enter a logon
interface.
The undo rta
server enable command only disables terminal access; it does not clear the
settings of the application, terminal, and virtual terminals.
II. Configuring a virtual terminal
Perform the following configuration in
terminal template view.
Table 3-2
Configure a TTY virtual terminal
|
To do…
|
Use the command…
|
|
Configure a virtual terminal
|
vty vty-number
tty remote ip-address port mode [source src-ip]
|
|
Remove a configured virtual terminal
|
undo vty vty-number
|
Up to eight virtual terminals can be
configured for a terminal, and each virtual terminal corresponds to an
application on the UNIX server.
vty-number
refers to the virtual terminal number and ranges from 0 to 7, each of which corresponds
to a virtual terminal. tty specifies the virtual terminal as a TTY one.
ip-address and port refer to the IP address of the UNIX server and
the listening port for the virtual terminal application. mode can be 1
or 0, indicating the one-to-one or many-to-one access mode respectively.
For information about the two access modes,
refer to section 1.2 “Terminal Access Features”. If you do not want to use the actual IP address of the initiating router as the source IP address of the TCP connection, you can reconfigure here. The IP address of the loopback interface or dialer interface
of the router is usually used as the source address of the TCP connection for
dialup redundancy and address hiding. You can use the rta source-ip
command in system view to configure a global source address for the TCP
connection.
III. Applying a terminal template
Apply a configured terminal template to a
terminal and assign a terminal number to the terminal.
Perform the following configuration in
async interface view.
Table 3-3
Apply a terminal template
|
To do…
|
Use the command…
|
|
Apply a terminal template
|
async mode terminal template-name tty-number
|
|
Remove the application of a terminal
template
|
undo async mode
|
template-name is the name of the terminal template. tty-number is the
terminal number to be assigned.
You are recommended to complete all basic and enhanced terminal
template configurations before applying the template to an interface. If you
have to modify the template, remember to use the update changed-config command
to make your changes take effect.
Follow these steps to bind the source IP
address: First, configure an IP address for a free interface on the router. You
are recommended to use the loopback interface or dialer interface. Then, use
the IP address of the interface as the source IP address of the upstream TCP
connection by configuring the rta source-ip command. Note that you must
configure a route to the IP address on the UNIX server.
Use the undo form of the rta source-ip
command to cancel the source IP address binding. After the source IP address
binding is canceled, the source IP address of the newly established TCP
connection is the IP address of the actual physical interface.
You can configure the source IP address
binding in two views: terminal template view and system view.
When performing basic configuration in
terminal template view, you can configure a source IP address binding for each
VTY you configured. The source IP address bound in system view is global, and
will be used as the source IP address of the connection established by a VTY
with no source address specified.
Perform the following configuration in
system view.
Table 3-4
Configure the source IP address binding
|
To do…
|
Use the command…
|
|
Configure the source IP address binding
|
rta source-ip ip-address
|
|
Remove the source IP address binding
|
undo rta source-ip
|
By default, no source IP address binding is
configured for any application.
l
After you configure the source IP address
binding, the TCP connection must be reestablished to use the source IP address.
l
The IP address to be bound must have been
specified to an interface on the router.
II. Configuring the virtual
terminal description
Perform the following configuration in
terminal template view.
Table 3-5
Configure a description for a virtual terminal
|
To do…
|
Use the command…
|
|
Configure a description for a virtual
terminal
|
vty vty-number
description string
|
|
Delete the description of a virtual
terminal
|
undo vty vty-number description
|
III. Setting the virtual terminal
switching prompt menu hotkey
You ca
