POS terminal access commands -- auto-connect enable

Use auto-connect enable to enable automatic connection for a POS application template that uses the permanent TCP connection mode. The router automatically initiates a connection to the FEP for the POS application template.

Use undo auto-connect enable to disable automatic connection.

Syntax

auto-connect enable

undo auto-connect enable

Default

Automatic connection is disabled. The router does not automatically initiate a connection to the FEP for a POS application template.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This feature takes effect only on POS application templates that use the permanent TCP connection mode:

· If enabled for a POS application template that uses permanent TCP connection mode, this feature takes effect immediately.

· If enabled for a POS application template that uses temporary TCP connection mode, this feature takes effect when the template's TCP connection mode changes to permanent.

T he established permanent TCP connection is used only for nontransparent transmissions between terminals and the FEP.

Examples

# Enable automatic connection to the FEP from POS application template 1 that uses the permanent TCP connection mode.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] auto-connect enable

Related commands

posa server enable

timer auto-connect

POS terminal access commands -- backup app

Use backup app to specify a backup POS application template.

Use undo backup app to restore the default.

Syntax

backup app app-id

undo backup app

Default

No backup POS application template is specified.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

app-id: Specifies a backup POS application template by its ID, in the range of 1 to 1024.

Usage guidelines

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. This command is applicable only to TCP-based POS application templates.

If the specified application template does not exist or is not TCP type, this command can be configured but it does not take effect.

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

POS terminal access commands -- caller-number enable

Use caller-number enable to enable sending of the caller ID in packets sent to the FEP.

Use undo caller-number enable to disable sending of the caller ID.

Syntax

caller-number enable

undo caller-number enable

Default

Sending of the caller ID to the FEP is disabled.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This command is applicable only to TCP-based POS application templates.

This feature is supported only for FCM or AM POS terminal devices.

· For an AM POS terminal device, this feature takes effect only when the application template is configured in temporary TCP connection mode.

· For an FCM POS terminal device, this feature takes effect only when the application template is configured in nontransparent mode.

· The caller ID format differs for FCM and AM POS terminals.

Examples

# Configure POS application template 1 in TCP mode. Enable sending of the caller ID.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] mode temporary

[Sysname-posa-app1] caller-number enable

POS terminal access commands -- description

Use description to set a description for a POS application template.

Use undo description to restore the default.

Syntax

description text

undo description

Default

No description is set for a POS application template.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

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 to ChinaBank1.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] description ChinaBank1

POS terminal access commands -- display fcm statistics

Use display fcm statistics to display POS access statistics on FCM interfaces.

Syntax

display fcm statistics [ interface fcm { interface-number | interface-number:setnumber.subnumber } ]

Views

Any view

Default command level

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

interface fcm { interface-number | interface-number:setnumber.subnumber }: Specifies an FCM interface or FCM subinterfaces. The interface-number argument represents the interface number of a physical FCM interface. The interface-number:setnumber.subnumber argument represents subinterfaces of the FCM interface channelized from an E1POS CE1/PRI interface. If no interface is specified, this command displays POS statistics for all physical FCM interfaces and subinterfaces of FCM interfaces channelized from E1POS CE1/PRI interfaces.

Usage guidelines

If you restart the router or execute the reset fcm statistics command, the statistics will be deleted.

Examples

# Display POS statistics for FCM 2/1/0.

<Sysname> display fcm statistics interface fcm 2/1/0

Interface TerminalID ConnectFailed TimedOut Transactions (Total/Success)

Fcm2/1/0 5 20 30 100/20

Table 1 Command output

Field | Description
Interface | POS access port, which must be an FCM interface.
TerminalID | ID of the POS terminal template. If no POS terminal template is bound, this field displays a hyphen (-).
ConnectFailed | Number of dial-up negotiation failures.
TimedOut | Number of disconnections because of transaction timeouts.
Transactions | Number of transactions for an FCM interface. · Total—Total number of transactions. · Success—Number of transactions for which packets were successfully forwarded. A transaction counted in this statistic is also counted in the TimedOut statistic when the transaction times out.

Related commands

reset fcm

POS terminal access commands -- display posa connection terminal

Use display posa connection terminal to display connection information for POS terminal templates.

Syntax

display posa connection terminal [ terminal-id ]

Views

Any view

Default command level

network-admin

network-operator

mdc-admin

mdc-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, this command displays connection information for all POS terminals.

Examples

# Display connection information for all POS terminal templates.

<Sysname> display posa connection terminal

Total TCP connections : 2

Total FCM connections : 1

Total flow connections: 1

Max concurrent trades : 65535

Current non-TCP trades: 2

Current TCP trades : 60

ID Type Interface SrcIP:SrcPort DstIP:DstPort trades

1 TCP - 192.168.100.100:1319 192.168.100.236:3000 10

1 TCP - 192.168.100.100:1320 192.168.100.236:3000 20

5 TCP - 192.168.100.200:1323 192.168.100.236:4000 30

6 FCM Fcm10/0:0.0 - - 1

7 Flow Asy1/0 - - 1

# Display connection information for POS terminal template 1.

<Sysname> display posa connection terminal 1

ID Type Interface SrcIP:SrcPort DstIP:DstPort trades

1 TCP - 192.168.100.100:1319 192.168.100.236:3000 10

1 TCP - 192.168.100.100:1320 192.168.100.236:3000 20

Table 2 Command output

Field | Description
Total TCP connections | Total number of current TCP connections.
Total FCM connections | Total number of current FCM connections.
Total flow connections | Total number of current flow connections.
Max concurrent trades | Max number of concurrent transactions that is supported by the system.
Current non-TCP trades | Total number of current non-TCP concurrent transactions.
Current TCP trades | Total number of current TCP concurrent transactions.
ID | ID of the POS terminal template.
Type | Access modes of POS terminal template: · Flow—Flow access mode. · FCM—FCM dial-up access mode. · TCP—TCP access mode.
Interface | POS access interface. For TCP access, this field displays a hyphen (-).
SrcIP | Source IP address of the connection. For non-TCP access, this field displays a hyphen (-).
SrcPort | Source port of the connection. For non-TCP access, this field displays a hyphen (-).
DstIP | Source IP address of the connection. For non-TCP access, this field displays a hyphen (-).
DstPort | Destination port of the connection. For non-TCP access, this field displays a hyphen (-).
Trades | Number of concurrent transactions of the connection.

POS terminal access commands -- 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

mdc-admin

mdc-operator

Parameters

app-id: Specifies a POS application template by its ID, in the range of 1 to 1024. If no application template is specified, this command displays statistics for all POS application templates.

Usage guidelines

Statistics collection for an application template applies to all instances that use the application template.

Statistics for an application template will be deleted if you perform one of the following tasks:

· Delete the application template.

· Restart the router.

· Execute the reset posa statistics command.

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 3 Command output

Field | Description
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 because of a full buffer.
OutDiscarded | Number of outgoing packets discarded because of link failures.

Related commands

reset posa statistics

POS terminal access commands -- display posa statistics terminal

Use display posa statistics terminal to display POS terminal template statistics.

Syntax

display posa statistics terminal [ terminal-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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, this command displays statistics for all POS terminal templates.

Usage guidelines

Statistics collection for a terminal template applies to all instances that use the terminal template.

Statistics for a terminal template will be deleted if you perform one of the following tasks:

· Delete the terminal template.

· Restart the router.

· Execute the reset posa statistics command.

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 4 Command output

Field | Description
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 because of a full buffer or failures to obtain transaction numbers.
OutDiscarded | Number of outgoing packets discarded because of link failures.
Notified | Number of notification packets sent to the POS terminal for the following failures: · Failures to map packets to POS applications. · Failures to obtain transaction numbers. · Failures to forward packets to the FEP.

Related commands

reset posa statistics

POS terminal access commands -- display posa status app

Use display posa status app to display POS application state information.

Syntax

display posa status app [ app-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

app-id: Specifies a POS application template by its ID, in the range of 1 to 1024. If no application template is specified, this 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 - Asy2/1/0 - Down

9 TCP Permanent - 192.168.4.1:20 Unlinked

11 TCP Permanent - 192.4.5.5:111 Unlinked

30 TCP Temporary - 192.168.7.52:4000 Multilink(10)

31 Flow - - - -

Table 5 Command output

Field | Description
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: · Permanent—Permanent TCP connection mode. · Temporary—Temporary TCP connection mode. For the flow mode, this field displays a hyphen (-).
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. N indicates the number of TCP connections. · Blocked—The POS application template is blocked because of 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 (-).

POS terminal access commands -- display posa status terminal

Use display posa status terminal to display POS terminal state information.

Syntax

display posa status terminal [ terminal-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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, this 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

2 TCP - 2000 Error

3 FCM Fcm2/10/0:0.0 - Down

254 TCP - 3000 Multilink(2)

255 Flow Asy2/1/0 - Up

Table 6 Command output

Field | Description
TerminalID | ID of the POS terminal template.
Type | POS terminal access mode: Flow, FCM (dial-up access), 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 the FCM or flow access mode, this field displays a hyphen (-).
State | Connection state of the POS terminal. For the flow or FCM 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. N indicates the number of TCP connections. · Error—The entry is not available.

POS terminal access commands -- 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

mdc-admin

Usage guidelines

This command takes effect only on TCP-based POS application templates.

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 POS application handshaking to detect the state of an FEP. This feature also allows an FEP to detect the reachability of the router.

With handshaking 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

POS terminal access commands -- ip

Use ip to configure the IP address and port number of the corresponding FEP for a POS application template.

Use undo ip to restore the default.

Syntax

ip ip-address port port-number

undo ip

Default

No IP address or port number is configured for the POS application template.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

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 only 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. Set the IP address and port number of the FEP for POS application template 1 to 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 to 1.1.1.2 and 3001 for POS application template 1.

[Sysname-posa-app1] ip 1.1.1.2 port 3001

Connections for the application have been reset.

Related commands

posa app

POS terminal access commands -- 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

mdc-admin

Parameters

permanent: Sets the TCP connection mode to permanent mode.

temporary: Sets the TCP connection mode to temporary mode.

Usage guidelines

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. The router establishes a dedicated TCP connection with the FEP for each POS transaction in transparent mode, regardless of the TCP connection mode of the application template. In this case, the router can establish concurrent TCP connections with the FEP.

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.

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

POS terminal access commands -- negotiation hookoff

Use negotiation hookoff to set the hook off delay time for an FCM card after the FCM interface receives the ringing current.

Use undo negotiation hookoff to remove the configuration.

Syntax

negotiation hookoff delaytime

undo negotiation hookoff

Default

The hook off delay time for an FCM card is 500 milliseconds.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

delaytime: Specifies the hook off delay time for an FCM card, in the range of 100 to 6000 milliseconds.

Examples

# Set the hook off delay time to 2000 milliseconds for the FCM card after FCM 2/4/0 receives the ringing current.

<Sysname> system-view

[Sysname] interface fcm 2/4/0

[Sysname-Fcm2/4/0] negotiation hookoff 2000

POS terminal access commands -- negotiation no-carrier-detect retry

Use negotiation no-carrier-detect retry to set the maximum number of successive no-carrier states allowed to be detected before the FCM card hangs up.

Use undo negotiation no-carrier-detect retry to remove the configuration.

Syntax

negotiation no-carrier-detect retry retries

undo negotiation no-carrier-detect retry

Default

An FCM card hangs up if a no-carrier state is detected.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

retries: Specifies the maximum number of successive no-carrier states allowed to be detected before the FCM card hangs up. The value is in the range of 1 to 1000.

Examples

# Set the maximum number of successive no-carrier states allowed to be detected to 20 for FCM 2/4/0.

<Sysname> system-view

[Sysname] interface fcm 2/4/0

[Sysname-Fcm2/4/0] negotiation no-carrier-detect retry 20

POS terminal access commands -- negotiation scramble-binary1

Use negotiation scramble-binary1 to set the modem negotiation scramble-binary1 time.

Use undo negotiation scramble-binary1 to remove the configuration.

Syntax

negotiation scramble-binary1 scramble-binary1time

undo negotiation scramble-binary1

Default

The modem negotiation scramble-binary1 time is 250 milliseconds.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

scramble-binary1time: Specifies the modem negotiation scramble-binary1 time, in the range of 100 to 1500 milliseconds.

Examples

# Set the modem negotiation scramble-binary1 time to 200 milliseconds for FCM 2/4/0.

<Sysname> system-view

[Sysname] interface fcm 2/4/0

[Sysname-Fcm2/4/0] negotiation scramble-binary1 200

POS terminal access commands -- negotiation silence

Use negotiation silence to set the modem negotiation silence time.

Use undo negotiation silence to remove the configuration.

Syntax

negotiation silence silencetime

undo negotiation silence

Default

The modem negotiation silence time is 0 milliseconds.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

silencetime: Specifies the modem negotiation silence time, in the range of 0 to 3000 milliseconds.

Usage guidelines

Silence time is the time interval from when the FCM card hooks off to when the FCM card sends a packet.

Silence time is used for the handshaking between a POS terminal and the FCM card. The silence time must be shorter than the maximum waiting time of a POS terminal and longer than the off-hook detection time of a POS terminal.

· If the silence time is longer than the maximum waiting time, the POS terminal considers that there is no data from the FCM card and hangs up.

· If the silence time is shorter than the off-hook detection time, the FCM card will send data to the POS terminal before the POS terminal successfully detected the off-hook of the FCM card. As a result, the POS terminal cannot receive the data.

Examples

# Set the modem negotiation silence time to 100 milliseconds.

<Sysname> system-view

[Sysname] interface fcm 2/4/0

[Sysname-Fcm2/4/0] negotiation silence 100

POS terminal access commands -- negotiation unscramble-binary1

Use negotiation unscramble-binary1 to set the modem negotiation unscramble-binary1 time.

Use undo negotiation unscramble-binary1 to remove the configuration.

Syntax

negotiation unscramble-binary1 un scramble-binary1time

undo negotiation unscramble-binary1

Default

The modem negotiation unscramble-binary1 time is 400 milliseconds.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

unscramble-binary1time: Specifies the modem negotiation unscramble-binary1 time, in the range of 300 to 1500 milliseconds.

Examples

# Set the modem negotiation unscramble-binary1 time to 900 milliseconds for FCM 2/4/0.

<Sysname> system-view

[Sysname] interface fcm 2/4/0

[Sysname-Fcm2/4/0] negotiation unscramble-binary1 900

POS terminal access commands -- posa app

Use posa app to create a POS application template and enter its view, or enter the view of an existing POS application template.

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 templates exist.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

app-id: Specifies an ID for the POS application template, in the range of 1 to 1024.

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.

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 2/7/0.

<Sysname> system-view

[Sysname] posa app 1 type flow

[Sysname-posa-app1] quit

[Sysname] interface Async 2/7/0

[Sysname-Async2/7/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

POS terminal access commands -- posa auto-stop-service enable

Use posa auto-stop-service enable to enable automatic shutdown of the listening ports for TCP-based POS terminal templates when all FEPs are unreachable.

Use undo posa auto-stop-service enable to disable automatic shutdown of the listening ports for TCP-based POS terminal templates.

Syntax

posa auto-stop-service enable

undo posa auto-stop-service enable

Default

The router does not automatically shut down the listening ports for TCP-based POS terminal templates.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

An FEP is unreachable when one of the following occurs:

· The router fails to initiate a connection to the FEP, for example, the linking time for the connection expires.

· The router is disconnected from the FEP because of the keepalive failure.

When all FEPs that correspond to TCP-based POS application templates are unreachable, the router automatically shuts down the listening ports for all TCP-based POS terminal templates. When any of the FEPs becomes reachable, the router automatically opens the listening ports for all TCP-based POS terminal templates.

Examples

# Enable automatic shutdown of the listening ports for TCP-based POS terminal templates.

<Sysname> system-view

[Sysname] posa auto-stop-service enable

POS terminal access commands -- posa bind app

Use posa bind app to bind a POS application template to an interface.

Use undo posa bind app to restore the default.

Syntax

posa bind app app-id

undo posa bind app

Default

No POS application template is bound to an interface.

Views

Asynchronous interface view

Synchronous/asynchronous interface view

Predefined user roles

network-admin

mdc-admin

Parameters

app-id: Specifies a POS application template by its ID, in the range of 1 to 1024.

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.

Before binding a POS application template to an interface, create the POS application template in flow mode in system view.

To bind a new POS application template to the interface, first execute the undo posa bind app command to remove the existing POS application template binding.

Bind different application templates to different interfaces.

You cannot bind both a POS terminal template and a POS application template to the same interface.

The connection mode of the specified POS application template must be flow mode.

Examples

# Create POS application template 2 in flow mode.

<Sysname> system-view

[Sysname] posa app 2 type flow

[Sysname-posa-app2] quit

# Bind Async 2/1/0 to POS application template 2.

<Sysname> system-view

[Sysname] interface async 2/1/0

[Sysname-Async2/1/0] posa bind app 2

Related commands

posa app

POS terminal access commands -- 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 template to the interface.

Use undo posa bind terminal to restore the default.

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

Asynchronous interface view

Physical AM interface view

Physical FCM interface view

Synchronous/asynchronous interface view

Predefined user roles

network-admin

mdc-admin

Parameters

terminal-id: Specifies a POS terminal template by its 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 1024. 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 a terminal template to an interface not operating in asynchronous mode, the state of the terminal template is Error.

Bind different terminal templates to different interfaces.

You cannot bind both a POS terminal template and a POS application template to the same interface.

Use the following guidelines when you specify the app app-id option:

· The POS terminal template bound to an interface cannot be switched between nontransparent mode and transparent mode. To assign a new POS application template to the POS terminal template, first execute the undo posa bind terminal command to remove the existing POS application template binding.

· In transparent mode, 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 2/1/0 as the access interface of POS terminal template 1.

<Sysname> system-view

[Sysname] interface async 2/1/0

[Sysname-Async2/1/0] posa bind terminal 1

Related commands

posa app

POS terminal access commands -- posa bind terminal first-terminal-id

Use posa bind terminal first-terminal-id to bulk-configure the subinterfaces of the current interface as POS access interfaces.

Use undo posa bind terminal first-terminal-id to restore the default.

Syntax

posa bind terminal first-terminal-id first terminal-id [ app-list app-list ] [ reassemble ]

undo posa bind terminal first-terminal-id

Default

Subinterfaces of an interface are not POS access interfaces of any POS terminal templates.

Views

Channelized AM interface view

Channelized FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

first-terminal-id: Specifies the start terminal template ID in the range of 1 to 255. The specified terminal template and the subsequent terminal templates (maximum ID 255) will be bound to FCM or AM subinterfaces in ascending order of terminal template IDs.

app-list app-list: Sets POS terminal templates to operate in transparent mode and specifies the POS application templates to be associated with the POS access interfaces. The app-list argument represents a list of POS application template IDs, which can contain the following elements separated by commas:

· Single application template ID, in the range of 1 to 1024.

· Hyphen-connected application template ID range, in format of start ID-end ID, for example 1-14. The start ID must be smaller than the end ID. The value range for the start ID and end ID is 1 to 1024.

· Colon-connected value, for example, 16:13. The number before the colon represents a POS application template ID in the range of 1 to 1024. The number after the colon (1 to 30) represents the number of subinterfaces to which the specified POS application template ID will be bound.

For example, the list of 1-14,15,16:13,127-128 indicates the subinterfaces numbered 1 to 14 are bound to the POS application template IDs of 1 to 14, the subinterface numbered 15 is bound to the POS application template ID 15, the subinterfaces numbered 16 to 28 are bound to the POS application template ID 16, and the subinterfaces numbered 29 to 30 are bound to the POS application template IDs of 127 to 128.

The application template ID list cannot contain spaces. If no application template ID is specified, this command configures the POS terminal templates to operate in nontransparent mode.

reassemble: Reassembles packet fragments on the router before sending them to FEPs in transparent mode. If you do not specify this option, the router sends packet fragments to FEPs without reassembling them. Only channelized AM interfaces support this option.

Usage guidelines

Support for this command depends on the interface types that the device supports.

Multiple FCM subinterfaces can be created from an E1POS CE1/PRI interface and multiple AM subinterfaces can be created from an E1DM CE1/PRI interface. For information about creating FCM and AM subinterfaces, see Interface Configuration Guide.

For this command to be successfully executed, make sure the following requirements are met:

· The number of the specified POS terminal templates must be no less than the number of the subinterfaces. For example, if you set the first terminal template ID to 251 and the current interface has more than five FCM subinterfaces, the configuration will fail because of insufficient terminal template IDs.

· The number of the specified POS application templates must be equal to the number of the subinterfaces.

· The specified terminal templates must be FCM/AM terminal templates and none of the terminal templates can be bound to another interface.

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.

If FEPs do not support fragments reassembling, specify the reassemble option to enable the router to reassemble packet fragments in transparent mode.

Examples

# FCM2/4/0:15 has 30 subinterfaces. Bulk-configure the 30 subinterfaces as the access interfaces for POS terminal templates with the IDs of 1 to 30. Bind the 30 subinterfaces to POS application template IDs of 1 to 30.

<sysname> system-view

[sysname] interface fcm 2/4/0:15

[sysname-Fcm2/4/0:15] posa bind terminal first-terminal-id 1 app-list 1-30

Related commands

posa app

posa bind terminal

POS terminal access commands -- posa connection-threshold terminal

Use posa connection-threshold terminal to set the concurrent connection threshold for POS terminals.

Use undo posa connection-threshold terminal to restore the default.

Syntax

posa connection-threshold terminal { fcm fcm-threshold-value | tcp tcp-threshold-value }

undo posa connection-threshold terminal { fcm | tcp }

Default

The concurrent connection threshold is 4096 for TCP access mode and 255 for FCM dial-up access mode.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

fcm fcm-threshold-value: Specifies the concurrent connection threshold for FCM dial-up access mode, in the range of 1 to 255.

fcm fcm-threshold-value: Specifies the concurrent connection threshold for TCP access mode, in the range of 1 to 4096.

Usage guidelines

The router generates SNMP notifications for fcm-connection-exceed or tcp-connection-exceed events when the following requirements are met:

· SNMP notification is enabled for fcm-connection-exceed or tcp-connection-exceed events.

· Number of FCM or TCP concurrent connections exceeds the threshold.

Connections can still be established after the concurrent connections threshold is exceeded.

Examples

# Set the TCP concurrent connection threshold to 200.

<Sysname> system-view

[Sysname] posa connection-threshold terminal tcp 200

Related commands

snmp-agent trap enable posa

POS terminal access commands -- posa fcm

Use posa fcm to set FCM parameters for modem negotiation.

Use undo posa fcm to restore the default for an FCM parameter.

Syntax

posa fcm { answer-time time1 | idle-time time2 | trade-time time3 }*

undo posa fcm { answer-time | trade-time | idle-time }

Default

The answering time is 2000 milliseconds. The idle time is 180 seconds. The transaction time is 12000000 milliseconds.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

answer-time time1: Specifies the answering time in the range of 500 to 2000 milliseconds.

idle-time time2: Specifies the maximum idle time for the link, in the range of 1 to 12000 seconds.

trade-time time3: Specifies the maximum time of a single transaction, in the range of 30000 to 12000000 milliseconds.

Usage guidelines

Typically, the modem on the router usually acts as the called party and the built-in modem in the POS terminal acts as the calling party. In a basic modem communication, the POS terminal originates a call to the called party, which answers and sends an answer tone to the POS terminal after detecting the calling signal. After the POS terminal receives the answer tone, both parties begin modem negotiation (V.22).

For a system with poor network quality, a short answer tone may cause a modem negotiation failure. If the interface comes up and down, without data being transmitted or received, you need to enlarge the value of answer-time.

To improve the efficiency of the POS access interface, and to avoid a POS terminal occupying system resources for a long period of time, manage individual transaction times by configuring parameters trade-time and idle time. If the maximum transaction time or the maximum idle time is exceeded, the router actively disconnects the corresponding POS terminal to release the link resource.

Typically, the default values of FCM parameters can meet the application demands. You can customize these parameters as needed.

Examples

# Change answer-time to 800 milliseconds, trade-time to 1200000 milliseconds (20 minutes), and idle-time to 6 seconds.

<Sysname> system-view

[Sysname] posa fcm answer-time 800

[Sysname] posa fcm trade-time 1200000

[Sysname] posa idle-time 6

POS terminal access commands -- posa map

Use posa map to configure POS application mapping entries.

Use undo posa map to remove POS application mapping entries.

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 entries are configured.

Views

System view

Predefined user roles

network-admin

mdc-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 1024. If the specified application template ID does not exist, the configuration is allowed but it does not take effect.

Usage guidelines

The POS terminal access device matches the originator address and/or destination address in the TPDU header of a received POS packet against the configured POS application mapping table. If the TPDU originator address, destination address, or both addresses match an entry in the POS application mapping table, the packet is sent to the specified POS application template. If no match is found, the packet is sent to the default POS application template.

You can configure multiple POS application mapping entries for the same POS application template. The entry that has both the originator and destination addresses has the highest priority. The default entry has the lowest priority.

The router supports up to 1024 POS application mapping entries, including the default mapping entry.

If you change the destination FEP of a mapping entry during a transaction, the connection will not be removed. However, it might affect the ongoing POS transaction.

Examples

# Configure a POS application mapping entry that maps packets destined for 01f1 to POS application template 2.

<Sysname> system-view

[Sysname] posa map destination 01f1 app 2

# Configure a default POS application mapping entry that maps unmatched packets to POS application template 1.

<Sysname> system-view

[Sysname] posa map default app 1

Related commands

posa app

POS terminal access commands -- posa server enable

Use posa server enable to enable the POS access service.

Use undo posa server enable to disable the POS access service.

Syntax

posa server enable

undo posa server enable

Default

The POS access service is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

To implement POS access, enable the POS access service.

If you configure POS functions incorrectly, the functions will not take effect. For example, you specify an unavailable TCP port as the source port for an application template. The display posa status command displays the POS terminal/application template state as Error after you enable the POS access service. After you fix the problem (for example, correct the TCP source port for the application template), you can re-enable the POS access service.

Examples

# Enable the POS access service.

<Sysname> system-view

[Sysname] posa server enable

Related commands

display posa status

POS terminal access commands -- posa statistics caller-id

Use posa statistics caller-id to add a caller ID statistical item. The router counts the packets exchanged between the POS terminal and the FEP for the caller ID.

Use undo posa statistics caller-id to remove the specified caller ID statistical item.

Syntax

posa statistics caller-id caller-number

undo posa statistics caller-id caller-number

Default

No caller ID statistical item is configured.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

caller-number: Specifies a caller ID, a string of 1 to 64 characters. It can contain only digits and letters, such as 01012345678. A caller ID is typically all digits, but letters can also be used.

Usage guidelines

This feature applies only to POS terminals using dial-up access mode.

If you configure the same caller ID multiple times, no error message is displayed.

The router supports a maximum of 64 caller ID statistical items.

Examples

# Add a statistical item for caller ID 01012345678 to count the packets between the POS terminal and the FEP.

<Sysname> system-view

[Sysname] posa statistics caller-id 01012345678

POS terminal access commands -- posa statistics caller-ip

Use posa statistics caller-ip to create a source IP statistical item. The source IP statistical item specifies a source IP or source IP segment. The router counts the packets that are sourced from the source IP and IP segment.

Use undo posa statistics caller-ip to remove the specified source IP statistical item.

Syntax

posa statistics caller-ip group-id ip-address ip-mask

undo posa statistics caller-ip group-id

Default

No source IP statistical item is configured.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

group-id: Specifies an ID for the source IP statistical item, in the range of 1 to 64.

ip-address: Specifies a source IP address or source IP segment in dotted decimal notation.

ip-mask: Specifies a mask in dotted decimal notation.

Usage guidelines

This feature applies only to POS terminals template using TCP.

Source IP segment can overlap each other or be the same.

POS terminal packets that match multiple source IP statistical items are counted for all the matched IP statistical items.

Examples

# Create source IP statistical item 1 so that the router will count the packets that are sourced from IP segment 10.0.1.0/24.

<Sysname> system-view

[Sysname] posa statistics caller-ip 1 10.0.1.0 255.255.255.0

POS terminal access commands -- posa terminal

Use posa terminal to create a TCP access POS terminal template.

Use undo posa terminal to delete the specified POS terminal template.

Syntax

posa terminal terminal-id type tcp listen-port port [ idle-time time ] [ https | ssl ]

undo posa terminal terminal-id

Default

No TCP access POS terminal templates exist.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

terminal-id: Specifies a POS terminal template ID in the range of 1 to 255.

type tcp: Specifies TCP mode.

listen-port port: Specifies a listening port number in the range of 1 to 65535.

idle-time time: Specifies the idle timeout for the POS terminal template, in the range of 1 to 1440 minutes. The default value of 0 indicates that no limit is set for the idle time.

https: Uses HTTPS connections to communicate with the POS terminal.

ssl: Uses SSL-based TCP connections to communicate with the POS terminal.

Usage guidelines

For flow or dial-up access mode, a corresponding terminal template is created automatically when you specify an access interface for the POS terminal. For TCP access mode, you need to create a template manually.

Do not set the same listening port number for multiple TCP access terminal templates. To set a new listening port number for the TCP access terminal template, first execute the undo posa terminal command to remove the existing listening port number setting.

If a POS terminal template does not exchange any packet with a POS terminal during the specified idle timeout period, the POS terminal template disconnects from the POS terminal.

If you specify the https or ssl keyword, execute the posa terminal ssl-server-policy command to specify the SSL server policy that the device uses to establish HTTPS or SSL connections with POS terminals.

Examples

# Create TCP access POS terminal template 1, set its listening port number to 3000, and configure the device to communicate with the POS terminal through HTTPS.

<Sysname> system-view

[Sysname] posa terminal 1 type tcp listen-port 3000 https

Related commands

posa bind terminal

posa terminal ssl-server-policy

POS terminal access commands -- posa terminal description

Use posa terminal terminal-id description to configure a description for a POS terminal template.

Use undo posa terminal terminal-id description to delete the POS terminal template description.

Syntax

posa terminal terminal-id description text

undo posa terminal terminal-id description

Default

No description is configured for a POS terminal template.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

terminal-id: Specifies a POS terminal template by its ID, in the range of 1 to 255.

text: Specifies a description for the POS terminal template, a case-sensitive string of 1 to 32 printable characters except question marks (?).

Usage guidelines

You can configure a description for a POS terminal template before creating the POS terminal template.

Examples

# Configure the description as shopping1 for POS terminal template 1.

<Sysname> system-view

[Sysname] posa terminal 1 description shopping1

Related commands

posa terminal

POS terminal access commands -- posa terminal ssl-server-policy

Use posa terminal ssl-server-policy to specify an SSL server policy for TCP-based POS terminal templates.

User undo posa terminal ssl-server-policy to restore the default.

Syntax

posa terminal ssl-server-policy policy-name

undo posa terminal ssl-server-policy

Default

No SSL server policy is specified for TCP-based POS terminal templates.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

policy-name: Specifies an SSL server policy by its name, a case-insensitive string of 1 to 31 characters.

Usage guidelines

Execute this command if you specify the https or ssl keyword of the posa terminal command. The device uses the SSL server policy parameters to establish HTTPS or SSL connections with POS terminals.

Examples

# Specify SSL server policy policy1 for TCP-based POS terminal templates.

<Sysname> system-view

[Sysname] posa terminal ssl-server-policy policy1

Related commands

posa terminal

ssl server-policy (see Security Command Reference)

POS terminal access commands -- posa tpdu-replace

Use posa tpdu-replace to configure a TPDU destination address replacement policy. The router uses the policy to replace the TPDU destination addresses of packets before looking up the application mapping table.

Use undo posa tpdu-replace to delete a TPDU destination address replacement policy.

Syntax

posa tpdu-replace match terminal { terminal-id | any } destination { des-code | any } to des-code

undo posa tpdu-replace match terminal { terminal-id | any } [ destination { des-code | any } ]

Default

The router does not replace the TPDU destination address.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

terminal terminal-id: Specifies a POS terminal template by its ID. The router replaces the TPDU destination address for all packets sent by the terminal with the target destination address.

terminal any: Specifies all POS terminal templates. The router replaces the TPDU destination address for packets sent by any terminal with the specified target destination address.

destination des-code: Specifies the TPDU destination address to be replaced. The router replaces the matched TPDU destination addresses with the specified target destination address.

destination any: Sets the TPDU destination address to be replaced to any address. The router replaces the TPDU destination address for packets sent by any matched terminal with the specified target destination address.

to des-code: Specifies the target TPDU destination address.

Usage guidelines

You can configure multiple TPDU destination address replacement policies. The router uses the policies in the following order of decreasing priority:

· Policies configured with both the terminal-id and the des-code arguments.

· Policies configured with both the terminal-id argument and the destination any keywords.

· Policies configured with both the terminal any keywords and the des-code argument.

· Policies configured with both the terminal any and the destination any keywords.

The router uses the original TPDU destination address as the source address to send reply messages to POS terminals.

Examples

# Configure the router to replace the TPDU destination address of POS packets destined for 0002 with 0003 for terminal 1.

<Sysname> system-view

[Sysname] posa tpdu-replace match terminal 1 destination 0002 to 0003

Related commands

tpdu-change

POS terminal access commands -- posa trade-limit tcp

Use posa trade-limit tcp to set the TCP concurrent transaction threshold.

Use undo posa trade-limit tcp to restore the default.

Syntax

posa trade-limit tcp limit-value

undo posa trade-limit tcp

Default

No limit is set to the number of concurrent transactions on a TCP connection.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

limit-value: Specifies the concurrent transaction threshold for each TCP connection, in the range of 0 to 65535. The value of 0 indicates that no limit is set to the number of TCP concurrent transactions.

Usage guidelines

You can install licenses to increase the concurrent transaction threshold for each TCP connection supported by the device. If the device does not support the licenses, or no licenses are installed, the threshold varies by device model. For more information about licenses, see Fundamentals Configuration Guide.

If the TCP concurrent transaction threshold is configured, the router discards the packets that exceed the threshold. If SNMP notification is also enabled for tcp-trade-exceed events, the router generates notifications by using the following scheme:

1. The router generates a notification when the number of concurrent transactions on a TCP connection exceeds the threshold for the first time.

2. The router does not generate any notifications before the number of concurrent transactions on that TCP connection drops below 90% the threshold.

3. After the number of concurrent transactions drops below 90% of the threshold, the router continues to generate a notification when the threshold is exceeded.

This scheme prevents frequent SNMP notifications in case of heavy transaction traffic.

Examples

# Set the TCP concurrent transaction threshold to 1024.

<Sysname> system-view

[Sysname] posa trade-limit tcp 1024

Related commands

snmp-agent trap enable posa

POS terminal access commands -- posa trade-timeout

Use posa trade-timeout to set the timeout for each transaction.

Use undo posa trade-timeout to restore the default.

Syntax

posa trade-timeout timeout-value

undo posa trade-timeout

Default

The timeout for each transaction is 240 seconds.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

timeout-value: Specifies the timeout for each transaction, in the range of 1 to 240 seconds.

Usage guidelines

The timeout timer is set when the router receives a transaction packet from a POS terminal. If the router receives no reply from the FEP before the timer expires, the transaction times out. The router discards the reply packet that is received after the timer expires.

If the network condition is poor, do not configure a small transaction timeout. A small transaction timeout might cause the router to reassign the transaction number of an expired transaction to a new transaction. Then, the router treats the reply to the expired transaction as the reply to the new transaction.

Examples

# Set the timeout for each transaction to 120 seconds.

<Sysname> system-view

[Sysname] posa trade-timeout 120

POS terminal access commands -- reset fcm statistics

Use reset fcm statistics to clear statistics for FCM interfaces.

Syntax

reset fcm statistics [ interface fcm { interface-number | interface-number:setnumber.subnumber } ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

interface fcm { interface-number | interface-number:setnumber.subnumber }: Specifies an FCM interface or FCM subinterfaces. The interface-number argument represents the interface number of a physical FCM interface. The interface-number:setnumber.subnumber argument represents subinterfaces of the FCM interface channelized from an E1POS CE1/PRI interface. If no interface is specified, this command displays POS statistics for all physical FCM interfaces and subinterfaces of FCM interfaces channelized from E1POS CE1/PRI interfaces.

Examples

# Clear POS statistics for all physical FCM interfaces and subinterfaces of FCM interfaces channelized from E1POS CE1/PRI interfaces.

<Sysname> reset fcm statistics

Related commands

display fcm statistics

POS terminal access commands -- reset posa connection terminal

Use reset posa connection terminal to disconnect TCP connections between the router and POS terminal devices.

Syntax

reset posa connection terminal { all | destination-ip ip-addr2 | destination-port port-number | source-ip ip-addr1 }

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

all: Disconnects all TCP connections between the router and POS terminal devices.

destination-ip ip-addr2: Specifies a destination IP address.

destination-port port-number: Specifies a destination port number in the range of 1 to 65535.

source-ip ip-addr1: Specifies a source IP address.

Usage guidelines

This command disconnects a single or multiple TCP connections based on the specified source IP address, destination IP address, and destination port number.

The number of disconnections is displayed when you execute this command.

Examples

# Disconnect all TCP connections between the router and POS terminal devices.

<Sysname> reset posa statistics

100 connections have been deleted.

POS terminal access commands -- reset posa statistics

Use reset posa statistics to clear statistics for a POS application template or terminal template.

Syntax

reset posa statistics [ app [ app-id ] | terminal [ terminal-id ] ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

app-id: Specifies a POS application template by its ID, in the range of 1 to 1024.

terminal-id: Specifies a POS terminal template by its ID, in the range of 1 to 255.

Usage guidelines

This command clears the statistics that are displayed with the display posa statistics app and display posa statistics terminal commands. The statistics counters restart at 0.

When you use this command to clear statistics for an application template or terminal template that does not exist, the router does not display an error message.

Examples

# Clear statistics for all POS application templates and POS terminal templates.

<Sysname> reset posa statistics

Related commands

display posa statistics app

display posa statistics terminal

POS terminal access commands -- snmp-agent trap enable posa

Use snmp-agent trap enable posa to enable SNMP notifications for POS terminal access.

Use undo snmp-agent trap enable posa to disable SNMP notifications for POS terminal access.

Syntax

snmp-agent trap enable posa [ app-state-change | fcm-connection-exceed | fcm-link-failure | fcm-physical-failure | server-state-change | tcp-connection-exceed | tcp-trade-exceed | terminal-hangup ] *

undo snmp-agent trap enable posa [ app-state-change | fcm-connection-exceed | fcm-link-failure | fcm-physical-failure | server-state-change | tcp-connection-exceed | tcp-trade-exceed | terminal-hangup ] *

Default

SNMP notifications for all POS terminal access events are enabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

app-state-change: Enables notifications for POS application template state changes.

fcm-connection-exceed: Enables notifications for FCM concurrent connections exceeding the threshold events.

fcm-link-failure: Enables notifications for negotiation failures on the FCM link layer.

fcm-physical-failure: Enables notifications for negotiation failures on the FCM physical layer.

server-state-change: Enables notifications for POS access server state changes.

tcp-connection-exceed: Enables notifications for TCP concurrent connections exceeding the threshold events.

tcp-trade-exceed: Enables notifications for TCP concurrent transactions exceeding the threshold events.

terminal-hangup: Enables notifications for POS terminal hangups.

Usage guidelines

This feature enables generating SNMP notifications for POS access events. For POS terminal access notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.

If you do not specify any keywords, this command enables or disables SNMP notifications for all types of POS access events.

Examples

# Disable SNMP notifications for FCM physical layer negotiation failures.

<Sysname> system-view

[Sysname] undo snmp-agent trap enable posa fcm-physical-failure

Related commands

posa connection-threshold terminal

posa trade-limit tcp

POS terminal access commands -- source ip

Use source ip to specify a source address for TCP connections.

Use undo source ip to restore the default.

Syntax

source ip ip-address

undo source ip

Default

No source address for TCP connections is specified.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

ip-address: Specifies a source IP address for a TCP connection. The address can be any unicast IPv4 address except the loopback address. Make sure the FEP is reachable from this IP address.

Usage guidelines

By default, the router uses the IP address of the interface bound to the application template to initialize a TCP connection to the FEP. For security purposes, you can use this command to specify an IP address as the source IP address.

Changing of the source address also deletes all existing TCP connections for the application template.

Examples

# Set the source address to 1.1.1.1 for POS application template 1. All existing connections for application template 1 are deleted.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] source ip 1.1.1.1

Connections for the application have been reset.

POS terminal access commands -- source port

Use source port to specify a source port number for TCP connections. The router must use the specified source port number to establish a TCP connection with the FEP.

Use undo source port to restore the default.

Syntax

source port port-number

undo source port

Default

No source port number is specified for TCP connections. The POS application template uses an available port number randomly assigned by the system to establish a TCP connection with the FEP.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

port-number: Specifies a source port number for TCP connections, in the range of 4000 to 4999.

Usage guidelines

If you specify a source port for a POS application template in temporary TCP connection mode, only one connection from the application template to the FEP can be created.

Changing the source port number also deletes all existing TCP connections for the application template.

The specified source port number must not be assigned to any other POS application template and must be different from the listening port number for the POS terminal. If you specify a source port number that is the same as the port number of any other system process, the source port does not take effect. You can use display posa status command to see which TCP ports have been occupied by other system processes.

Examples

# Set the source port number to 4001 for POS application template 1. All existing connections for application template 1 are deleted.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] source port 4001

Connections for the application have been reset.

POS terminal access commands -- tcp keepalive

Use tcp keepalive to configure TCP keepalive parameters for a POS application template.

Use undo tcp keepalive to restore the default.

Syntax

tcp keepalive interval interval count counts

undo tcp keepalive

Default

TCP keepalive packets are sent every 2 seconds. The router tears down the TCP connection to the POS application template if no reply is received during three sending intervals.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

interval interval: Specifies the keepalive interval in the range of 1 to 7200 seconds.

count counts: Specifies the keepalive number in the range of 2 to 100.

Usage guidelines

The configuration takes effect immediately.

The timeout of a TCP connection is the keepalive interval multiplied by the keepalive number. If no reply is received before the timeout timer expires, the router tears down the TCP connection.

Examples

# Configure TCP-based POS application template 1. Set the keepalive interval to 100 seconds and the keepalive number to 4.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] tcp keepalive interval 100 count 4

POS terminal access commands -- tcp linking-time

Use tcp linking-time to configure the timeout for the TCP connection request to the FEP. The timeout is the maximum time that the POS application template can stay in TCP linking state.

Use undo tcp linking-time to restore the default.

Syntax

tcp linking-time time

undo tcp linking-time

Default

The maximum TCP linking time is 20 seconds.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

time: Specifies the maximum TCP linking time, in the range of 1 to 20 in seconds.

Usage guidelines

If the maximum TCP linking time expires, the TCP connection request is canceled and the transaction fails. This command also specifies the maximum time that the router waits for the FEP to respond to a caller ID negotiation packet from an AM POS terminal device.

The configuration takes effect only for TCP connections established after this command is executed.

Examples

# Set the maximum TCP linking time to 10 seconds for POS application template 1.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] tcp linking-time 10

POS terminal access commands -- threshold answer-tone

Use threshold answer-tone to set the modem negotiation answer-tone threshold.

Use undo threshold answer-tone to restore the default.

Syntax

threshold answer-tone answertonetime

undo threshold answer-tone

Default

The modem negotiation answer-tone threshold varies by device model.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

answertonetime: Specifies the modem negotiation answer-tone threshold, in the range of 1 to 42 -dBm.

Examples

# Set the modem negotiation answer-tone threshold to -41 dBm for FCM 2/1/0.

<Sysname> system-view

[Sysname] interface fcm 2/1/0

[Sysname–Fcm2/1/0] threshold answer-tone 41

POS terminal access commands -- threshold rlsdoff

Use threshold rlsdoff to set the RLSD turn-off threshold for modem negotiation.

Use undo threshold rlsdoff to restore the default.

Syntax

threshold rlsdoff rlsdofftime

undo threshold rlsdoff

Default

The RLSD turn-off threshold for modem negotiation is -48 dBm.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

rlsdofftime: Specifies the RLSD turn-off threshold in the range of 0 to 75 -dBm.

Examples

# Set the RLSD turn-off threshold to -74 dBm for FCM 2/1/0.

<Sysname> system-view

[Sysname] interface fcm 2/1/0

[Sysname–Fcm2/1/0] threshold rlsdoff 74

POS terminal access commands -- threshold rlsdon

Use threshold rlsdon to set the RLSD turn-on threshold for modem negotiation.

Use undo threshold rlsdon to restore the default.

Syntax

threshold rlsdon rlsdontime

undo threshold rlsdon

Default

The RLSD turn-on threshold for modem negotiation is -43 dBm.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

rlsdofftime: Specifies the RLSD turn-on threshold in the range of 0 to 75-dBm.

Examples

# Set the RLSD turn-on threshold to -73 dBm for FCM 2/1/0.

<Sysname> system-view

[Sysname] interface fcm 2/1/0

[Sysname–Fcm2/1/0] threshold rlsdon 73

POS terminal access commands -- threshold txpower

Use threshold txpower to set the transmission power threshold for modem negotiation.

Use undo threshold txpower to restore the default.

Syntax

threshold txpower txpowertime

undo threshold txpower

Default

The modem negotiation transmission power threshold is -10 dBm.

Views

FCM interface view

Predefined user roles

network-admin

mdc-admin

Parameters

rlsdofftime: Specifies the modem negotiation transmission power threshold, in the range of 1 to 42 -dBm.

Examples

# Set the modem negotiation transmission power threshold to -40 dBm for FCM 2/1/0.

<Sysname> system-view

[Sysname] interface fcm 2/1/0

[Sysname–Fcm2/1/0] threshold txpower 40

POS terminal access commands -- timer auto-connect

Use timer auto-connect to set the interval between auto connections to the FEP for the POS application template.

Use undo timer auto-connect to restore the default.

Syntax

timer auto-connect interval

undo timer auto-connect

Default

A POS application template automatically initiates a connection to the FEP every 10 minutes.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

interval: Specifies the interval at which the POS application template automatically initiates a connection to the FEP, in the range of 1 to 1440 minutes.

Usage guidelines

This command is applicable only to POS application templates that use permanent TCP connection mode.

Before the router successfully establishes a permanent TCP connection with the FEP for a POS application template, the router automatically initiates connections to the FEP at the specified interval.

Examples

# Set the auto connection interval for the POS application template 1 to 1 minute.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] timer auto-connect 1

Related commands

auto-connect enable

POS terminal access commands -- timer hello

Use timer hello to set the interval for a POS application template to send handshaking packets.

Use undo timer hello to restore the default.

Syntax

timer hello interval

undo timer hello

Default

A POS application template sends handshaking packets every 1 minute.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

interval: Specifies the interval at which the POS application template sends handshake packets, in the range of 1 to 600 minutes.

Usage guidelines

After you enable handshaking for an application template and specify the interval, the router sends handshaking packets to the FEP at the specified interval.

Examples

# Set the handshaking interval time for POS application template 1 to 10 minutes.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] timer hello 10

Related commands

hello enable

POS terminal access commands -- timer quiet

Use timer quiet to set the quiet time for a POS application template.

Use undo timer quiet to restore the default.

Syntax

timer quiet interval

undo timer quiet

Default

The quiet time for a POS application template is 600 minutes.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

interval: Specifies the quiet time for the POS application template, in the range of 10 to 600 minutes.

Usage guidelines

When a POS terminal launches a transaction, the router tries to establish a TCP connection with the FEP. If the FEP is unreachable, the router places the FEP to blocked state and starts the quiet timer.

The configuration takes effect immediately and the quiet timer restarts at 0.

Examples

# Set the quiet timer for POS application template 1 to 500 minutes.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] timer quiet 500

Related commands

backup app

POS terminal access commands -- tpdu-change

Use tpdu-change to configure the TPDU address change policy. The router uses the policy to change either the TPDU originator or destination addresses of packets before sending them to FEPs.

Use undo tpdu-change to restore the default.

Syntax

tpdu-change { destination | source }

undo tpdu-change

Default

The router changes the TPDU originator address.

Views

POS application template view

Predefined user roles

network-admin

mdc-admin

Parameters

destination: Changes the TPDU destination addresses of packets.

source: Changes the TPDU originator addresses of packets.

Usage guidelines

FEPs require the change of either the originator or destination address in the TPDU field. Determine the TPDU address change policy according to the requirements of FEPs.

In nontransparent mode, modifying the TPDU address change policy also removes all permanent TCP connections governed by the application template.

Examples

# Configure the router to change the TPDU destination address of packets sent to the FEP that corresponds to POS application template 1.

<Sysname> system-view

[Sysname] posa app 1 type tcp

[Sysname-posa-app1] tpdu-change destination

Connections for the application have been reset.