Page 2
The information in this document is subject to change without notice. All contents in this document, including statements, information, and recommendations, are believed to be accurate, but they are presented without warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions contained herein.
Page 3
Preface This configuration guide describes the terminal access related settings. This preface includes the following topics about the documentation: • Audience. • Conventions. • Documentation feedback. Audience This documentation is intended for: • Network planners. • Field technical support and servicing engineers. •...
Page 4
Symbols Convention Description An alert that calls attention to important information that if not understood or followed WARNING! can result in personal injury. An alert that calls attention to important information that if not understood or followed CAUTION: can result in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information.
Page 5
Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
Configuring RTC terminal access About RTC terminal access Terminal access enables a terminal to use a serial interface to access another terminal through routers. Remote terminal connection (RTC) terminal access is a typical application of terminal access. RTC terminal access interconnects a local terminal and a remote terminal through routers for data monitoring and data sharing.
Page 8
TCP/UDP one-to-one transparent transmission between one RTC client and one RTC server. TCP many-to-one transparent transmission between multiple RTC clients and one relay server. UDP one-to-many transparent transmission between one RTC server and multiple RTC clients. TCP or UDP one-to-one transparent transmission Figure 1 shows a typical network diagram for the one-to-one transparent transmission.
UDP one-to-many transparent transmission UDP one-to-many transparent transmission is mainly applied to signal synchronization for unidirectional broadcast communication links. Figure 3 shows a typical network diagram for this type of transmission. The UDP one-to-many transparent transmission procedure takes the following steps: The signal source terminal sends data.
Feature Supported by Description TCP_11_Client, TCP_11_Server, Terminal access VPN instances UDP_11_Client, UDP_11_Server TCP_11_Client, TCP_11_Server, TCP NODELAY TCP_N1_Server Access types supporting Link backup synchronous terminals Compatibility mode support For more information, see Information debugging Terminal Access Debugging Command Manual. RTC terminal access features Source address binding This function specifies the source IP address of the TCP connection initiated from the router.
Page 11
Terminal reset When a terminal fails to communicate with the receiver, you can re-establish communication by pressing the terminal reset hotkey on the terminal. The initiator will disconnect and then re-establish the TCP connection with the receiver. TCP parameter configuration TCP buffers store the data exchanged between the initiator and receiver.
Devices running Comware 3 or Comware 5 can operate only in characteristic mode or compatibility mode. The mode is automatically set and is not user configurable. Devices running Comware 7 can operate in either characteristic or compatibility mode, depending on your configuration.
Terminal templates Most of the important settings of the RTC terminal system are configured in terminal templates on a router. The templates are applied to corresponding interfaces (such as an asynchronous serial interface). The router then creates TTYs and VTYs according to the template configurations. Only one template can be applied to an interface.
RTC terminal access Hardware compatibility MSR2630-XS MSR3600-28-XS MSR3610-XS MSR3620-XS MSR3610-I-XS MSR3610-IE-XS RTC terminal access Hardware compatibility MSR810-LM-GL MSR810-W-LM-GL MSR830-6EI-GL MSR830-10EI-GL MSR830-6HI-GL MSR830-10HI-GL MSR2600-6-X1-GL MSR3600-28-SI-GL Restrictions and guidelines: RTC terminal access configuration If you modify a template that has been applied to an interface, use the update changed-config command to update the configuration.
Configuring the asynchronous TCP RTC one-to-one initiator (TCP_11_Client) About the asynchronous TCP RTC one-to-one initiator The initiator is a TCP_11_Client connected to the monitoring device. The receiver is a TCP_11_Server connected to the monitored device. The TCP_11_Client can initiate a connection request to the TCP_11_Server at any time to obtain the data of the monitored device.
Page 16
auto-close time By default, the automatic link teardown time is 0 seconds, which indicates that no automatic link teardown will be performed. Configure the automatic link establishment time. auto-link time By default, the automatic link establishment time is 0 seconds, which indicates that no automatic link establishment will be performed.
The send buffer size is 2048 bytes. Delay is enabled. The keepalive interval is 50 seconds. The keepalive number is 3. This command takes effect only after a TCP connection is re-established. (Optional.) Configure the password for VTY authentication. vty vty-number password { simple | cipher } string By default, no password for VTY authentication is configured.
For more information about the command, see Interface Command async-mode Reference. Specify the protocol type as STLP for a synchronous serial interface. link-protocol stlp By default, a synchronous serial interface operates in the PPP protocol mode. Apply the template to the interface. rta terminal template-name terminal-number By default, no template is applied to the interface.
Page 19
vty vty-number rtc-server remote p-address terminal-number After this configuration, the template cannot be configured with any RTC client VTYs. argument of the command configured terminal-number vty rtc-server remote on the RTC server must be the same as the argument of the terminal-number command configured on the RTC client.
By default, no password for VTY authentication is configured. To implement terminal access authentication, you must configure terminal access authentication on both the RTC server and the RTC client, and the authentication passwords must be identical for the authentication to succeed. (Optional.) Update the configuration.
Apply the template to the interface. rta terminal template-name terminal-number Configuring the TCP RTC many-to-one relay server (TCP_N1_Server) About this task The initiators are TCP_11_Clients, which are connected to monitoring devices. The receiver is a relay server (TCP_N1_Server) which is not connected to any monitored device. Procedure Enter system view.
Configuring the synchronous UDP RTC one-to-one initiator (UDP_11_Client) About the synchronous UDP RTC one-to-one initiator The initiator is a UDP_11_Client, which is connected to the monitoring device through a synchronous serial interface. The receiver is a UDP_11_Server, which is connected to the monitored device through a synchronous serial interface.
Configuring the synchronous UDP RTC one-to-one receiver (UDP_11_Server) Enabling terminal access on the router Enter system view. system-view Enable terminal access. rta server enable Configuring a terminal template Enter system view. system-view Create a terminal template and enter terminal template view. rta template template-name Create a UDP RTC server VTY.
Configuring the synchronous UDP RTC one-to-many receiver (UDP_1N_Server) About the synchronous UDP RTC one-to-many receiver The initiator is a UDP_11_Client, which is connected to the monitoring device through a synchronous serial interface. The receiver is a UDP_1N_Server, which is connected to the monitored device through a synchronous serial interface.
Display and maintenance commands for RTC terminal access Execute commands in any view and commands in user view. displays reset Task Command display rta { all | statistics | terminal-number { vty-number | Display terminal access information. brief | detail | statistics } } Display states of all RTC client connections display rta relay status accepted by a relay server.
# Enable terminal access. <Sysname> system-view [Sysname] rta server enable # Set the listening port of the server. [Sysname] rta rtc-server listen-port 9000 # Create a terminal template and enter terminal template view. [Sysname] rta template rtcserver # Configure the VTY. [Sysname-rta-template-rtcserver] vty 0 rtc-server remote 10.111.0.12 1 [Sysname-rta-template-rtcserver] vty 0 password simple 123 [Sysname-rta-template-rtcserver] quit...
Page 27
Figure 5 Network diagram GE1/0/1 GE1/0/1 10.111.0.12 10.111.95.10 IP network RTC Client RTC Server S2/2/0 S2/2/0 Central terminal Remote terminal Procedure Configure the RTC server: # Enable terminal access. <Sysname> system-view [Sysname] rta server enable # Set the listening port of the server. [Sysname] rta rtc-server listen-port 9000 # Create a terminal template and enter terminal template view.
# Check that the remote terminal can receive the instruction, and check that the central terminal can receive the requested data from the remote terminal. Example: Configuring asynchronous RTC VPNs Network configuration As shown in Figure 6, central terminal CE A in the monitoring center and remote terminal CE B are in MPLS L3VPN VPNA.
[PEB] interface async 2/2/0 [PEB-Async2/2/0] async mode flow [PEB-Async2/2/0] rta terminal rtcs 2 [PEB-Async2/2/0] quit Configure the RTC client: # Configure MPLS L3VPN. For more information, see MPLS Configuration Guide. # Bind Loopback 1 to VPNA. [PEA] interface loopback 1 [PEA-LoopBack1] ip address 169.254.2.1 32 [PEA-LoopBack1] ip binding vpn-instance vpna [PEA-LoopBack1] quit...
Page 30
Figure 7 Network diagram GE1/0/1 GE1/0/1 GE1/0/2 GE1/0/1 1.1.2.1 Router C Router A 1.1.3.1 1.1.4.1 1.1.1.1 IP network IP network Async2/2/0 Async2/2/0 Router B Terminal A Termina B Procedure Configure TCP_11_Client Router A: # Enable terminal access. <Sysname> system-view [Sysname] rta server enable # Create a terminal template and enter terminal template view.
Verifying the configuration # Check that Terminal A and Terminal B can receive data from each other. Example: Configuring synchronous TCP RTC many-to-one relay Network configuration As shown in Figure 8, Router A and Router C act as TCP_11_Clients and Router B acts as the relay server TCP_N1_Server.
Example: Configuring UDP RTC one-to-many Network configuration As shown in Figure 10, Router A and Router C act as UDP_11_Clients, and Router B acts as a UDP_1N_Server. Configure Router A, Router B, and Router C to enable both Terminal A and Terminal C to receive data from Terminal B: •...
Terminal state is down after terminal access is enabled Symptom Terminal access is enabled by using the command. However, the rta server enable display command displays that the state of a powered terminal is Down Analysis The asynchronous serial interface is configured with the command.
Need help?
Do you have a question about the MSR 810 and is the answer not in the manual?
Questions and answers