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.
To Next Page
Loading...
Need help?
General
