H3C MSR810 Bedienungsanleitung

H3C MSR 810 & 2600 & 3600 Routers

Comware 7 Terminal Access Configuration Guide

New H3C Technologies Co., Ltd.

http://www.h3c.com

Software version: MSR-CMW710-R0809

Document version: 6W400-20200823

No part of this manual may be reproduced or transmitted in any form or by any means without prior written

consent of New H3C Technologies Co., Ltd.

Trademarks

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this

document are the property of their respective owners.

Notice

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.

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.

•

Network administrators.

Conventions

The following information describes the conventions used in the documentation.

Command conventions

Convention

Description

Boldface Bold text represents commands and keywords that you enter literally as shown.

Italic Italic text represents arguments that you replace with actual values.

[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.

{ x | y | ... }

Braces enclose a set of required syntax choices separated by vertical bars, from which

you select one.

[ x | y | ... ]

Square brackets enclose a set of optional syntax choices separated by vertical bars,

from which you select one or none.

{ x | y | ... } *

Asterisk marked braces enclose a set of required syntax choices separated by vertical

bars, from which you select a minimum of one.

[ x | y | ... ] *

Asterisk marked square brackets enclose optional syntax choices separated by vertical

bars, from which you select one choice, multiple choices, or none.

&<1-n> The argument or keyword and argument combination before the ampersand (&) sign

can be entered 1 to n times.

# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention

Description

Boldface Window names, button names, field names, and menu items are in Boldface. For

example, the New User window opens; click OK.

> Multi-level menus are separated by angle brackets. For example, File > Create >

Folder.

Symbols

Convention

Description

WARNING! An alert that calls attention to important information that if not understood or followed

can result in personal injury.

CAUTION:

An alert that calls attention to important information that if not understood or followed

can result in data loss, data corruption, or damage to hardware or software.

IMPORTANT:

An alert that calls attention to essential information.

NOTE:

An alert that contains additional or supplementary information.

TIP:

An alert that provides helpful information.

Network topology icons

Convention

Description

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that

supports Layer 2 forwarding and other Layer 2 features.

Represents an access controller, a unified wired-WLAN module, or the access

controller engine on a unified wired-WLAN switch.

Represents an access point.

Represents a wireless terminator unit.

Represents a wireless terminator.

Represents a mesh access point.

Represents omnidirectional signals.

Represents directional signals.

Represents a security product, such as a firewall, UTM, multiservice security

gateway, or load balancing device.

Represents a security module, such as a firewall, load balancing, NetStream, SSL

VPN, IPS, or ACG module.

Examples provided in this document

Examples in this document might use devices that differ from your device in hardware model,

configuration, or software version. It is normal that the port numbers, sample output, screenshots,

and other information in the examples differ from what you have on your device.

Documentation feedback

You can e-mail your comments about product documentation to info@h3c.com.

We appreciate your comments.

Contents

Configuring RTC terminal access ··································································1

About RTC terminal access ·······························································································································1

Network devices in RTC terminal access···································································································1

Typical applications of RTC terminal access ·····························································································1

RTC terminal access feature list················································································································3

RTC terminal access features····················································································································4

RTC terminal access specifications···········································································································6

Terminal templates·····································································································································7

Restrictions: Hardware compatibility with RTC terminal access········································································7

Restrictions and guidelines: RTC terminal access configuration·······································································8

RTC terminal access tasks at a glance··············································································································8

Configuring the asynchronous TCP RTC one-to-one initiator (TCP_11_Client)················································9

About the asynchronous TCP RTC one-to-one initiator·············································································9

Asynchronous TCP RTC one-to-one initiator tasks at a glance·································································9

Enabling terminal access on the router······································································································9

Configuring a terminal template·················································································································9

Configuring a TTY user line ·····················································································································11

Applying the terminal template to an interface·························································································11

Configuring the asynchronous TCP RTC one-to-one receiver (TCP_11_Server) ···········································12

Asynchronous TCP RTC one-to-one receiver tasks at a glance······························································12

Enabling terminal access on the router····································································································12

Configuring a terminal template···············································································································12

Configuring a TTY user line ·····················································································································14

Applying the terminal template to an interface·························································································14

Configuring the TCP RTC many-to-one relay server (TCP_N1_Server) ·························································15

Configuring the synchronous UDP RTC one-to-one initiator (UDP_11_Client)···············································16

About the synchronous UDP RTC one-to-one initiator ············································································16

Enabling terminal access on the router····································································································16

Configuring a terminal template···············································································································16

Applying the terminal template to an interface·························································································16

Configuring the synchronous UDP RTC one-to-one receiver (UDP_11_Server) ············································17

Enabling terminal access on the router····································································································17

Configuring a terminal template···············································································································17

Applying the terminal template to an interface·························································································17

Configuring the synchronous UDP RTC one-to-many receiver (UDP_1N_Server)·········································18

About the synchronous UDP RTC one-to-many receiver ········································································18

Enabling terminal access on the router····································································································18

Applying the terminal template to an interface·························································································18

Display and maintenance commands for RTC terminal access ······································································19

RTC terminal access configuration examples··································································································19

Example: Configuring asynchronous TCP RTC one-to-one ····································································19

Example: Configuring synchronous TCP RTC one-to-one ······································································20

Example: Configuring asynchronous RTC VPNs·····················································································22

Example: Configuring asynchronous TCP RTC many-to-one relay·························································23

Example: Configuring synchronous TCP RTC many-to-one relay···························································25

Example: Configuring UDP RTC one-to-one backup link ········································································26

Example: Configuring UDP RTC one-to-many·························································································28

Troubleshooting RTC terminal access·············································································································29

Failure to establish a terminal connection································································································29

Terminal state is down after terminal access is enabled··········································································30

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.

Network devices in RTC terminal access

The following types of network devices are used in RTC terminal access:

•

Terminal—Aterminal refers to a character device that is generally connected to a router

through a serial interface cable.

•

Initiator—An initiator refers to a router that sends a connection request and acts as the RTC

client of the connection.

•

Receiver—A receiver refers to a router that responds to a connection request and acts as the

RTC server of the connection.

•

Relay server—A relay server provides functions similar to a receiver, except that the relay

server is not directly connected to terminals. Instead, the relay server is connected to multiple

initiators and manages them in different forwarding groups according to the listening port

numbers. Data received from an initiator is forwarded to other initiators in the same group.

NOTE:

In an actual network, the receiver and the relay server are not both deployed.

Connections between an initiator and a receiver can use either TCP or UDP. After a connection is

established between an initiator and a receiver, the initiator and receiver can transparently transmit

data from the local terminal to the remote terminal over the connection. The transmission is

transparent in that no manual or extra operation is required.

Typical applications of RTC terminal access

RTC terminal access has the following purposes:

•

Enabling a monitoring device to manage and monitor remote terminals.

•

Sharing data among multiple terminals such as radar devices.

•

Collecting data from remote terminals.

•

Synchronizing signal data on a broadcast communication network.

RTC terminal access supports synchronous mode and asynchronous mode.

•

Asynchronous mode—In asynchronous mode, an initiator and a receiver support only TCP

connections between them, including the following types:

TCP 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.

•

Synchronous mode—In synchronous mode, an initiator and a receiver support TCP or UDP

connections, including the following types:

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. Router A

initiates a monitoring request to access the data on the monitored terminal. Router B receives the

monitoring request and sends the data of the monitored terminal to Router A. TCP RTC transparent

transmission can ensure high reliability of the data transmitted, but it has a certain forwarding delay.

Because voice service does not require high reliability, the UDP RTC transparent transmission is

mainly applied to voice transmission.

Figure 1 Network diagram

TCP many-to-one transparent transmission

Some terminal devices, such as radars, need to share data with one another. RTC terminal access

provides many-to-one relay forwarding based on TCP. Routers connecting these terminals are

connected to one relay server, which forwards data received from a router to other routers in the

same group.

Figure 2 Network diagram

RTC Client RTC Server

Monitoring

terminal Minitored

terminal

Router A Router B

IP network

RTC Client

RTC ClientRelay Server

Router A

Router B Router C

Router D

IP network

IP network IP network

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:

1. The signal source terminal sends data.

2. The RTC server sends the data to all RTC clients.

3. The RTC clients forward the data to the signal receiver terminals and do not respond to the RTC

server.

Figure 3 Network diagram

RTC terminal access feature list

The following table lists the features supported by RTC terminal access. "All" in this table means that

the feature is supported by all RTC access types, which include the following:

•

TCP_11_Client (RTC TCP one-to-one client).

•

TCP_11_Server (RTC TCP one-to-one server).

•

TCP_N1_Server (relay server).

•

UDP_11_Client (RTC UDP one-to-one client).

•

UDP_11_Server (RTC UDP one-to-one server).

•

UDP_1N_Server (RTC UDP one-to-many server).

Feature Supported by Description

Source address binding TCP_11_Client N/A

Fast VTY service switching TCP_11_Client N/A

Connection idle timeout TCP_11_Client, TCP_11_Server, N/A

Automatic link establishment TCP_11_Client N/A

Automatic link teardown TCP_11_Client, TCP_11_Server, N/A

Terminal reset TCP_11_Client N/A

TCP parameter configuration TTCP_11_Client, TCP_11_Server,

TCP_N1_Server N/A

Terminal buffer parameter

configuration TTCP_11_Client, TCP_11_Server,

TCP_N1_Server N/A

RTC terminal authentication TCP_11_Client, TCP_11_Server,

TCP_11_Server N/A

Broadcast

communication

RTC Client

RTC Server

Router A

Router B

Router C

Signal receiver

terminal

Signal receiver

terminal

Signal source

terminal

Feature Supported by Description

Terminal access VPN instances TCP_11_Client, TCP_11_Server,

UDP_11_Client, UDP_11_Server N/A

TCP NODELAY TCP_11_Client, TCP_11_Server,

TCP_N1_Server N/A

Link backup Access types supporting

synchronous terminals N/A

Compatibility mode support All N/A

Information debugging All For more information, see

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. You

can use this function for the following purposes:

•

For stable status—Use the IP address of a stable interface, for example, a loopback interface

or a dialer interface, as the TCP source IP address.

•

For security or some other reason—Specify a TCP source IP address to hide the IP address

of the physical interface that is used in the upstream TCP connection.

Make sure the receiver and the interface whose IP address is used as the TCP source address can

reach each other.

Fast VTY service switching

In RTC terminal access, each terminal is logically divided into eight virtual type terminals (VTYs).

Each VTY can be configured to correspond to a service, which is also known as an application. On a

terminal, you can press the hotkey to bring up the VTY switching menu and select a VTY.

Connection idle timeout

The initiator and receiver are automatically disconnected from each other when the following

conditions are met:

•

A connection idle timeout has been set.

•

No data is transmitted between the initiator and receiver during the connection idle timeout

period.

Automatic link establishment

You can enable this function and configure the automatic link establishment time in terminal template

view. When the terminal is successfully connected to the initiator, the initiator automatically

establishes a TCP connection to the receiver after the specified auto establishment time.

If this function is disabled, the initiator establishes a TCP connection to the receiver only when you

enter a character on the terminal.

Automatic link teardown

You can enable this function and configure the automatic teardown time for the terminal in terminal

template view. When the terminal and the initiator are disconnected from each other, the terminal

enters down state. After the automatic teardown time, the initiator automatically tears down the TCP

connection to the receiver. The TCP connection always remains active if the automatic link teardown

function is disabled.

Andere Handbücher für MSR810

Dieses Handbuch passt für folgende Modelle

Inhaltsverzeichnis

Andere H3C WLAN-Router Handbücher

H3C

H3C CR19000-16 Bedienungsanleitung

H3C

H3C MSR 20-1X Bedienungsanleitung

H3C

H3C MSR810 Benutzerhandbuch

H3C

H3C MSR 930 Bedienungs- und Wartungshandbuch

H3C

H3C MSR810 Betriebsanleitung

H3C

H3C MSR810 Bedienungsanleitung

H3C

H3C MSR900-E Routers Bedienungsanleitung

H3C

H3C SR6616 Bedienungsanleitung

H3C

H3C Magic BX54 Bedienungsanleitung

H3C

H3C Magic NX30 Bedienungsanleitung

H3C

H3C Magic NX15 Bedienungsanleitung

H3C

H3C MSR 800 Bedienungsanleitung

H3C

H3C MSR900-E Routers Bedienungs- und Wartungshandbuch

H3C

H3C MSR810 Bedienungs- und Wartungshandbuch

H3C

H3C MSR 800 Bedienungsanleitung

Beliebte WLAN-Router Handbücher anderer Marken

Airlogic

Airlogic AirSync Class 1 Betriebsanleitung

Samsung

Samsung WCH730B Bedienungsanleitung

NETGEAR

NETGEAR PowerLINE WiFi 1000 Series Bedienungsanleitung

Askey

Askey RAC2V1K Bedienungsanleitung

Alloy

Alloy WLF2454AP-S Bedienungsanleitung

TELEFONICA

TELEFONICA USB Adapter Bedienungsanleitung

TP-Link

TP-Link TL-WR542G Bedienungsanleitung

Hama

Hama 53120 Bedienungsanleitung

Intellinet

Intellinet 524582 Bedienungsanleitung

Asus

Asus RT-N10P Bedienungsanleitung

D-Link

D-Link DIR-506L Bedienungsanleitung

Sapido

Sapido GR297n Bedienungsanleitung

Asus

Asus DSL-N55U Bedienungsanleitung

AMTC

AMTC WR7502 Bedienungsanleitung

Compaq

Compaq CP-2W - iPAQ Connection Point Bedienungsanleitung

SMC Networks

SMC Networks WBR14-N2 FICHE Bedienungsanleitung

Draytek

Draytek Vigor2120 Series Bedienungsanleitung

Sitecom

Sitecom WLR-4000 Bedienungsanleitung