H3C MSR Series User manual

H3C MSR Series Routers
Terminal Access Command Reference(V7)
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: MSR-CMW710-R0007
Document version: 6W100-20140320

Copyright © 2014, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,
SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of
Hangzhou H3C Technologies Co., Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Preface
The H3C MSR documentation set includes 15 command references, which describe the commands and
command syntax options available for the H3C MSR Series Routers.
The Terminal Access Command Reference(V7) describes the Terminal Access configuration commands.
This preface includes:
•Audience
•Conventions
•About the H3C MSR documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
These configuration guides apply to the following models of the H3C MSR series routers:
Model
MSR 2600 •MSR 26-30
MSR 3600
•MSR 36-10
•MSR 36-20
•MSR 36-40
•MSR 36-60
•MSR3600-28
•MSR3600-51
MSR 5600
•MSR 56-60
•MSR 56-80
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the routers

Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
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 at least 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.
Symbols
Convention Descri
p
tion
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.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
About the H3C MSR documentation set
The H3C MSR documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Product description and
specifications Marketing brochures Describe product specifications and benefits.

Cate
g
or
y
Documents Pur
p
oses
Hardware specifications
and installation
Installation guide Provides a complete guide to hardware installation
and hardware specifications.
MSR Series Routers
Interface Module Manual
Provide the hardware specifications of cards.
Software configuration
MSR Series Routers
Configuration guides(v7)
Describe software features and configuration
procedures.
MSR Series Routers
Command references(v7)
Provide a quick reference to all available
commands.
Operations and
maintenance Release notes
Provide information about the product release,
including the version history, hardware and software
compatibility matrix, version upgrade information,
technical support information, and software
upgrading.
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents]—Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions]—Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download]—Provides the documentation released with the
software version.
Technical support
servic[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
POS terminal access commands································································································································· 1
backup app·······························································································································································1
caller-number enable················································································································································1
description·································································································································································2
display posa connection terminal···························································································································3
display posa statistics app ······································································································································4
display posa statistics terminal································································································································5
display posa status app···········································································································································6
display posa status terminal ····································································································································7
hello enable ······························································································································································8
ip ················································································································································································9
mode······································································································································································· 10
posa app································································································································································ 11
posa bind app ······················································································································································· 12
posa bind terminal ················································································································································ 13
posa map ······························································································································································· 14
posa server enable················································································································································ 15
posa statistics caller-id ·········································································································································· 16
posa statistics caller-ip ·········································································································································· 17
posa terminal ························································································································································· 17
posa terminal description ····································································································································· 18
reset posa connection terminal ···························································································································· 19
reset posa statistics················································································································································ 19
snmp-agent trap enable posa ······························································································································ 20
source ip································································································································································· 21
source port ····························································································································································· 22
tcp keepalive·························································································································································· 22
tcp linking-time······················································································································································· 23
timer hello······························································································································································· 24
timer quiet ······························································································································································ 24
tpdu-change ··························································································································································· 25
Index ············································································································································································· 1

1
POS terminal access commands
backup app
Use backup app to specify a backup POS application template.
Use undo backup app to remove the backup POS application template.
Syntax
backup app app-id
undo backup app
Default
No backup application template is configured.
Views
POS application template view
Predefined user roles
network-admin
Parameters
app-id: Specifies a backup POS application template by its ID, in the range of 1 to 31.
Usage guidelines
This command is applicable only to TCP-based POS application templates. If the specified application
template does not exist or is not TCP type, the command can be configured but it does not take effect.
If the FEP corresponding to an application template is unreachable, the router initializes a TCP
connection to the FEP that corresponds to the backup application template.
Examples
# Create TCP-based application template 1.
<Sysname> system-view
[Sysname] posa app 1 type tcp
# Create TCP-based application template 2, and specify its backup application template as application
template 1.
<Sysname> system-view
[Sysname] posa app 2 type tcp
[Sysname-posa-app2] backup app 1
Related commands
timer quiet
caller-number enable
Use caller-number enable to enable sending of the caller number in packets sent to the FEP.

2
Use undo caller-number enable to disable sending of the caller number.
Syntax
caller-number enable
undo caller-number enable
Default
Sending of the caller number is disabled.
Views
POS application template view
Predefined user roles
network-admin
Usage guidelines
This function is supported only for AM POS terminal devices.
This function takes effect only when the application template is configured in temporary TCP connection
mode.
Examples
# Configure POS application template 1 in TCP mode. Enable sending of the caller number.
<Sysname> system-view
[Sysname] posa app 1 type tcp
[Sysname-posa-app1] mode temporary
[Sysname-posa-app1] caller-number enable
description
Use description to set a description for a POS application template.
Use undo description to delete the description.
Syntax
description text
undo description
Default
No description is set for a POS application template and the POS application template is displayed on
the MIB management platform as an empty string.
Views
POS application template view
Predefined user roles
network-admin

3
Parameters
text: Specifies a description, a case-sensitive string of 1 to 32 printable characters except question marks
(?).
Examples
# Create a TCP-based POS application template and set the description as ChinaBank1.
<Sysname> system-view
[Sysname] posa app 1 type tcp
[Sysname-posa-app1] description ChinaBank1
display posa connection terminal
Use display posa connection terminal to display connection information for TCP-based POS terminals.
Syntax
display posa connection terminal [ terminal-id ]
Views
Any view
Default command level
network-admin
network-operator
Parameters
terminal-id: Specifies a POS terminal template by its ID, in the range of 1 to 255. If no terminal template
is specified, the command displays connection information for all TCP-based terminals.
Examples
# Display connection information for all TCP-based terminals.
<Sysname> display posa connection terminal
TerminalID SourceIP SourcePort DestinationPort DestinationIP
1 192.168.100.1 1319 3000 192.168.100.236
1 192.168.100.1 1320 3000 192.168.100.236
5 192.168.100.2 1323 4000 192.168.100.236
5 192.168.100.2 1324 4000 192.168.100.236
Table 1 Command output
Field Descri
p
tion
TerminalID ID of the POS terminal template.
SourceIP Source IP address of the connection.
SourcePort Source port of the connection.
DestinationPort Destination port of the connection.
DestinationIP Source IP address of the connection.

4
display posa statistics app
Use display posa statistics app to display POS application template statistics.
Syntax
display posa statistics app [ app-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
app-id: Specifies a POS application template by its ID, in the range of 1 to 31. If no application template
is specified, the command displays statistics for all POS application templates.
Usage guidelines
The statistics will be deleted if you perform one of the following tasks:
•Delete an application.
•Restart the router.
•Execute reset posa statistics command.
Statistics collection for an application template applies to all instances that use the application template.
Examples
# Display all POS application template statistics.
<Sysname> display posa statistics app
ID Received Sent PktErr DisErr InDiscarded OutDiscarded
1 100 100 0 0 0 3
2 60 70 0 0 0 0
3 100 10 0 0 0 0
Table 2 Command output
Field Descri
p
tion
ID ID of the POS application template.
Received Number of packets received from FEPs (including PktErr and DisErr, not including
InDiscarded).
Sent Number of packets sent to FEPs (not including OutDiscarded).
PktErr Number of packets in incorrect format.
DisErr Number of packets failed to be distributed to POS terminal templates.
InDiscarded Number of incoming packets discarded due to a full buffer.
OutDiscarded Number of outgoing packets discarded due to link failures.
Related commands
reset posa statistics

5
display posa statistics terminal
Use display posa statistics terminal to view POS terminal template statistics.
Syntax
display posa statistics terminal [ terminal-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
terminal-id: Specifies a POS terminal template by its ID in the range of 1 to 255. If no terminal template
is specified, the command displays statistics for all POS terminal templates.
Usage guidelines
If the specified terminal does not exist, there is no command output or error message.
The statistics will be deleted if you perform one of the following:
•Delete an application
•Restart the router
•Execute reset posa statistics command
Statistics collection for a terminal template applies to for all instances that use the terminal template.
Examples
# Display all POS terminal template statistics.
<Sysname> display posa statistics terminal
ID Received Sent PktErr MapErr InDiscarded OutDiscarded Notified
1 100 50 2 2 0 5 2
2 60 70 0 10 1 6 0
3 100 100 0 0 1 3 0
4 3 0 0 0 0 3 0
Table 3 Command output
Field Descri
p
tion
ID ID of the POS terminal template.
Received Number of packets received from a POS terminal device (including PktErr and
MapErr, not including InDiscarded).
Sent Number of packets sent to an application template (not including Outdiscarded
and Notified).
PktErr Number of packets in incorrect format received from a POS terminal device.
MapErr Number of packets failed to be mapped to application templates.
InDiscarded Number of incoming packets discarded due to a full buffer.
OutDiscarded Number of outgoing packets discarded due to link failures.

6
Field Descri
p
tion
Notified Number of notification packets sent to the POS terminal when application mapping
failures or forward failures occur.
Related commands
reset posa statistics
display posa status app
Use display posa status app to view POS application state information.
Syntax
display posa status app [ app-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
app-id: Specifies a POS application template by its ID, in the range of 1 to 31. If no application template
is specified, the command displays state statistics for all POS application templates.
Examples
# Display state information for all POS application templates.
<Sysname> display posa status app
AppID Type Mode Interface IPAddr:Port State
1 TCP Temporary - 192.168.7.254:1000 linked
2 TCP Temporary - 192.168.7.224:1000 Error
3 Flow - Asy1/0 - Down
9 TCP Normal - 192.168.4.1:20 Unlinked
11 TCP Normal - 192.4.5.5:111 Unlinked
30 TCP Temporary - 192.168.7.52:4000 Multilink(10)
31 Flow - - - -
Table 4 Command output
Field Descri
p
tion
AppID ID of the POS application template.
Type Connection mode of the POS application template: flow or TCP.
Mode
TCP connection mode of the POS application template:
•Normal—Permanent TCP connection mode.
•Temporary—Temporary TCP connection mode.
For the flow mode, this field displays a hyphen (-).

7
Field Descri
p
tion
Interface
Interface of the POS application template.
If no interface is configured, or the POS application is in TCP mode, this field
displays a hyphen (-).
IPAddr:Port
IP address and port number of the FEP for the POS application template.
If no IP address and port number are configured, or the POS application is in flow
mode, this field displays a hyphen (-).
State
Connection state of the POS application template.
For the flow mode:
•Up—The connection has been established.
•Down—The connection has been terminated.
For the TCP mode:
•Unlinked—The connection has not been established.
•Linking—The connection is being established.
•Linked—The connection has been established.
•Multilink(N)—Multiple TCP connections have been established for the POS
application. Nindicates the number of TCP connections.
•Blocked—The POS application template is blocked due to application fault.
•Error—The mapping entry for the application template is not available because
the mapping entry failed to be enabled (TCP connection failed to be bound to
a source port).
If no interface, IP addresses or port number is configured, this field displays a
hyphen (-).
display posa status terminal
Use display posa status terminal to view POS terminal state information.
Syntax
display posa status terminal [ terminal-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
terminal-id: Specifies a POS terminal by its ID, in the range of 1 to 255. If no terminal template is
specified, the command displays state information for all POS terminal templates.
Examples
# Display state information for all POS terminal templates.
<Sysname> display posa status terminal
TerminalID Type Interface ListenPort State
1 TCP - 2000 Unlinked

8
2 TCP - 2000 Error
254 TCP - 3000 Multilink(2)
255 Flow Asy1/0 - Up
Table 5 Command output
Field Descri
p
tion
TerminalID ID of the POS terminal template.
Type POS terminal access mode: Flow or TCP.
Interface
Access interface.
If no interface is configured, or the POS terminal is in the TCP access mode, this
field displays a hyphen (-).
ListenPort
Listening port for a POS terminal.
If no interface is configured, or the POS terminal is in flow access mode, this
field displays a hyphen (-).
State
Connection state of the POS terminal.
For the flow access mode:
•Up—The connection has been established.
•Down—The connection has been terminated.
For the TCP access mode:
•Unlinked—The connection has not been established.
•Linking—The connection is being established.
•Linked—The connection has been established.
•Multilink(N)—Multiple TCP connections have been established for the POS
terminal. Nindicates the number of TCP connections.
•Error—The entry is not available.
hello enable
Use hello enable to enable handshaking for a POS application template.
Use undo hello enable to disable handshaking for a POS application template.
Syntax
hello enable
undo hello enable
Default
Handshaking for POS application templates is disabled.
Views
POS application template view
Predefined user roles
network-admin
Usage guidelines
This command takes effect only on TCP-based POS application templates.

9
By default, the router communicates with an FEP only when there are packets from a POS terminal. If the
FEP is faulty, the current transaction might fail or be delayed. To solve this problem, you can enable the
POS application handshaking function to detect the state of an FEP. This function also allows an FEP to
detect the reachability of the router.
With handshaking is enabled for an application template, the router initiates a connection to the
corresponding FEP for the application template at a specific interval. The interval is configured by using
the timer hello command. When the TCP connection is established, the router sends to the FEP a packet
with an empty data field (fixed as 00056000000000). The FEP does not respond to the packet.
•For an application template using the temporary TCP connection mode, the router initiates a new
connection at every interval.
•For an application template using the permanent TCP connection mode, the router uses the existing
TCP connection to send a packet. If no TCP connection exists, the router creates a TCP connection
and keeps the TCP connection after the handshaking.
The handshaking will change the state of the current POS application. If the POS application is in
blocked state, it will switch to non-blocked state when the handshaking succeeds. If the POS application
is in non-blocked state, it will switch to blocked state when the handshaking fails. For an application
template using the temporary TCP connection mode, the FEP state change notifications will not be sent
when handshakes succeed.
Examples
# Enable handshaking for POS application templates.
<Sysname> system-view
[Sysname] posa app 1 type tcp
[Sysname-posa-app1] hello enable
Related commands
timer hello
ip
Use ip to configure the IP address and port number of the corresponding FEP for a POS application
template.
Use undo ip to remove the configuration.
Syntax
ip ip-address port port-number
undo ip
Default
No IP address or port number is specified for the POS application template.
Views
POS application template view
Predefined user roles
network-admin

10
Parameters
ip-address: Specifies the IP address of the FEP. The address can be any unicast IPv4 address except the
loopback address.
port-number: Specifies the port number of the FEP, in the range of 1 to 65535.
Usage guidelines
This command applies to POS application templates in TCP mode.
You can specify only one IP address and port number for a POS application template. Modifying the IP
address or port number also removes all existing TCP connections that use this template.
Examples
# Create POS application template 1 in TCP mode. Specify the IP address and port number of the FEP
for POS application template 1 as 1.1.1.1 and 3000.
<Sysname> system-view
[Sysname] posa app 1 type tcp
[Sysname-posa-app1] ip 1.1.1.1 port 3000
# Modify the IP address and port number of the FEP for POS application template 1 to 1.1.1.2 and 3001.
[Sysname-posa-app1] ip 1.1.1.2 port 3001
Connections for the application have been reset.
Related commands
posa app
mode
Use mode to configure the TCP connection mode for a POS application template.
Use undo mode to remove the configuration.
Syntax
mode { permanent |temporary }
undo mode
Default
The TCP connection mode of a POS application template is the permanent mode.
Views
POS application template view
Predefined user roles
network-admin
Parameters
permanent: Specifies the TCP connection mode as permanent mode.
temporary: Specifies the TCP connection mode as temporary mode.
Usage guidelines
This command takes effect only on POS application templates operating in TCP mode.
If you switch between permanent and temporary modes, the TCP connections already established by the
POS application template are terminated.

11
•In temporary mode, the router terminates the TCP connection to the FEP when a POS transaction
finishes. The router establishes another TCP connection for a new transaction. The router can
establish concurrent TCP connections with the FEP.
•In permanent mode, for POS transactions in nontransparent transport mode, the router maintains
the TCP connection to the FEP when the first POS transaction finishes. The router uses the TCP
connection to transfer subsequent POS packets.
If an application template is bound to a POS terminal for transparent transport, the router creates a
dedicated TCP connection for the terminal, regardless of the TCP connection mode of the application
template. In this case, the router can establish concurrent TCP connections with the FEP.
Examples
# Create POS application template 1 in TCP mode. Specify the temporary TCP connection mode for POS
application 1.
<Sysname> system-view
[Sysname] posa app 1 type tcp
[Sysname-posa-app1] mode temporary
Connections for the application have been reset.
The output shows that the permanent TCP connection already established by the POS application
template is deleted.
Related commands
posa app
posa app
Use posa app to create a POS application template and enter its view.
Use undo posa app to remove the POS application template.
Syntax
posa app app-id type { flow | tcp }
undo posa app app-id
Default
No POS application is created.
Views
System view
Predefined user roles
network-admin
Parameters
app-id: Specifies an ID for the POS application template, in the range of 1 to 31.
type: Configures the connection mode in which the POS application template communicates with the
FEP:
•flow—Specifies the flow mode.
•tcp—Specifies the TCP mode.

12
Usage guidelines
You must specify a unique ID for each application template on the router. You cannot change the
connection mode for an existing application template.
For an application template in flow mode, bind it to an Async, Serial, or Aux interface after it is created
so that it can take effect.
Examples
# Create POS application template 1 in flow mode. Bind POS application template 1 to Async 7/0.
<Sysname> system-view
[Sysname] posa app 1 type flow
[Sysname-posa-app1] quit
[Sysname] interface Async 7/0
[Sysname-Async7/0] posa bind app 1
# Create POS application template 2 in TCP mode.
<Sysname> system-view
[Sysname] posa app 2 type tcp
Related commands
posa bind app
posa bind app
Use posa bind app to bind a POS application template to an interface.
Use undo posa bind app to remove the binding.
Syntax
posa bind app app-id
undo posa bind app
Default
No POS application is bound to an interface.
Views
Asynchronous interface view, synchronous/asynchronous interface view
Predefined user roles
network-admin
Parameters
app-id: Specifies a POS application template by its ID in the range of 1 to 31.
Usage guidelines
The connection mode of the specified POS application template must be flow.
Before binding a POS application template to an interface, create the POS application template in flow
mode in system view.
You can bind only one POS application template to an interface. Use the undo posa bind app command
to remove the existing POS application template before binding a new application template to the
interface.

13
Bind different application templates to different interfaces.
You cannot bind both a POS terminal template and a POS application template to the same interface.
You can use this command on a synchronous/asynchronous interface only when the interface is
operating in asynchronous mode. If you bind an application template to an interface not operating in
asynchronous mode, the state of the application template is Error.
Examples
# Create POS application template 2 in flow mode.
<Sysname> system-view
[Sysname] posa app 2 type flow
[Sysname-posa-app2] quit
# Bind interface Async 1/0 to POS application template 2.
<Sysname> system-view
[Sysname] interface async1/0
[Sysname-Async1/0] posa bind app 2
Related commands
posa app
posa bind terminal
Use posa bind terminal to configure the current interface as the access interface of a POS terminal
template by binding the POS terminal to the interface.
Use undo posa bind terminal to remove the configuration.
Syntax
posa bind terminal terminal-id [ app app-id ]
undo posa bind terminal
Default
An interface is not an access interface of any POS terminal template.
Views
AM interface view, asynchronous interface view, synchronous/asynchronous interface view
Predefined user roles
network-admin
Parameters
terminal-id: Specifies a POS terminal template ID in the range of 1 to 255.
app app-id: Specifies a POS application template by its ID, in the range of 1 to 31. This option specifies
the POS application template to be associated with the POS terminal template in transparent mode. The
specified application template must be an existing TCP-based application template. If no application
template is specified, it indicates that the terminal template is operating in nontransparent mode.
Usage guidelines
You can use this command on a synchronous/asynchronous interface only when the interface is
operating in asynchronous mode. If you bind an application template to an interface not operating in
asynchronous mode, the state of the application template is Error.

14
You can bind only one POS terminal template to an interface. You cannot bind the same POS terminal
template to multiple interfaces.
You cannot bind both a POS terminal template and a POS application template to the same interface.
The POS terminal template bound to an interface cannot be switched between nontransparent mode and
transparent mode, and the associated application template cannot be changed. You can remove the
binding and re-configure it.
In transparent mode, you can associate only one POS application template with a POS terminal template,
but you can associate multiple POS terminal templates with one POS application template.
If the specified application template does not exist or is not in TCP mode, the configuration is allowed but
it does not take effect. Related transactions will fail.
Examples
# Configure Async 1/0 as the access interface of POS terminal template 1.
<Sysname> system-view
[Sysname] interface async 1/0
[Sysname-Async1/0] posa bind terminal 1
Related commands
posa app
posa map
Use posa map to configure a POS application mapping entry.
Use posa undo map to remove the configuration.
Syntax
posa map { { default | destination des-code | source src-code } * } app app-id
undo posa map { { default | destination des-code |source src-code } * }
Default
No POS application mapping entry is configured.
Views
System view
Predefined user roles
network-admin
Parameters
default: Specifies a default POS application template, to which packets that do not match any mappings
are sent.
destination des-code: Specifies the destination address in the TPDU header of a POS packet. It is a
four-hexadecimal-digit string such as FFFF to identify a bank, and is generally assigned from the
transaction center.
source src-code: Specifies the originator address in the TPDU header of a POS packet. It is a string of four
hexadecimal digits such as 0001 to identify a POS terminal.
app app-id: Specifies a POS application template by its ID, in the range of 1 to 31.