3Com Router User Manual

							POS Access Service Configuration97
■Avoiding the dial-up time problem and fast connecting to the transaction 
processing center.
■Reducing the number of occupied communication links, hence saving the 
communications cost greatly.
■Avoiding the problem of service queuing as it is as though each POS terminal 
device enjoys a dedicated line (except the networking is comprised of the POS 
terminal and the POS concentrator). 
■The POS access feature can be combined with other services of the router, i.e., 
dumb terminal, SNA, and VoIP, which brings a wide market and provides users 
with integrated solutions.
POS Access Service 
Configuration
 
POS access service configuration includes:
■Enable POS access server
■Configure POS access port
■Configure POS application interface
■Configure POS application
■Configure POS multi-application map
■Bind the source address of TCP connection
1Enable POS Access Server
To implement the POS access service, the POS access server must first be started.
Please perform the following configuration in system view. 
Ta b l e 72   Start POS server
By default, the system disables the POS access server.
2Configure POS Access Port
Only configured as a POS access port can the interface provide POS access service.
At present, the interfaces of the 3Com Router series, which can be used for POS 
access service, include the asynchronous interface, AUX port, the 
synchronous/asynchronous interface, and the FCM interface.
Please perform the following configuration in asynchronous interface view or FCM 
interface view. 
Ta b l e 73   Configure POS access port
By default, the asynchronous interface and FCM interface operate in protocol 
mode, that is, no POS access port is configured.
Only when the active interface operates in protocol mode can the command be 
configured.
OperationCommand
Enable POS access serverpos-server enable
Disable POS access serverundo pos-server enable
OperationCommand
Configure the POS access interfaceasync mode pos pos-id  
						

							98CHAPTER 7: POS TERMINAL ACCESS SERVICE
If the FCM interface is used as POS access interface undo modem cannot be 
configured. If another interface is used as the POS access interface undo modem 
must be configured.
Since POS access does not support flow control, the interface should be 
configured with the flow-control none command.
If the POS access port is connected to the POS terminal in asynchronous mode, 
and the POS asynchronous port does not send a DSR-DTR signal, it is necessary to 
configure the command undo detect dsr-dtr on the interface. If the POS access 
port is connected to the FCM interface via dial-up, it is unnecessary to configure 
the undo detect dsr-dtr command.
3Configure POS Application 
The POS access router connects to the UNIX FEP in the following two ways: 
asynchronous connection and TCP/IP connection. The commands used for 
configuring the POS application are different in the two modes. Connecting to the 
UNIX FEP through the Ethernet is called a TCP/IP connection, while connecting 
through the asynchronous serial port is called asynchronous connection. No 
matter how the connected is made, it is necessary to configure the POS 
application to UNIX FEP for the terminal. 
Please perform the following configuration in system view. 
Ta b l e 74   Configure a POS application
By default, no POS application is configured by the system.
4Configure POS Application Interface
POS application interface should operate in posapp mode.
Please perform the following configuration in asynchronous interface view. 
Ta b l e 75   Configure the asynchronous connection interface to operate in POS application 
mode
When the POS access router is connected to the UNIX FEP in asynchronous mode, 
the interface should operate in posapp mode.
This command can be configured only when the active interface is configured with 
the command async mode protocol
Only after the command undo modem is configured, can data be transceived 
normally.
OperationCommand
Configure a POS application in asynchronous 
connectionpos-server app flow app-number 
interface-type interface-number
Delete a POS application in asynchronous 
connectionundo pos-server app flow 
app-number
Configure a POS application in TCP/IP 
connectionpos-server app tcp app-number 
ip-address port-number
Delete a POS application in TCP/IP connectionundo pos-server app tcp 
app-number
OperationCommand
Configure the operation mode of POS application 
interfaceasync mode posapp 
						

							POS Access Service Configuration99
POS access does not support flow control, therefore, the interface should be 
configured with the flow-control none command.
5Configure POS Multi-Application Map
POS multi-application is a kind of POS access function, which sends the packets 
from a POS terminal device to different POS applications according to the packet 
destination addresses. For TCP/IP connection, an application is marked by two 
parts, IP address and port number, that is, the different applications may have 
different IP addresses or share the same IP address but have different port 
numbers. The packets can be sent to different applications according to the 
destination address number. When the destination address number has a 
corresponding entry in the mapping table, the packet will be sent to the 
application corresponding to the entry. If there is no entry matching the 
destination address, the packet will be sent to the default application.
Please perform the following configuration in system view. 
Ta b l e 76   Configure POS multi-application mapping table
By default, no POS multi-application mapping table is configured.
At present, the 3Com Router series support up to 32 applications.
6Bind the Source Address of TCP Connection
When several POS terminal devices multiplex one TCP connection to set up 
relations with the application of the host, for the sake of security, it is necessary to 
hide the true IP address of the up TCP connection in the access service, and set 
another IP address for the source address instead. At the same time, to perform 
the backup of the link, the terminal access server provides the function of binding 
the source address of the TCP connection.
The principle of binding the source address of the TCP connection is to configure 
an IP address on the other interface that is not used on the router (Dial-up 
interface is recommended), the unnumbered IP address is the address of the up 
TCP connection on the terminal access server. Using the 
undo pos-server 
source-ip
 command, you can remove the binding of TCP source address and the 
IP address of the TCP connection will be restored to the real IP address of the 
original physical interface.
Please perform the following configurations in system view.
Ta b l e 77   Bind the source address of TCP connection
By default, the source address of the TCP connection is not bound.
Please note that this command can be applied only in the application in the TCP 
connection, and the application state is that the TCP connection has not been 
OperationCommand
Configure the POS multi-application mapping tablepos-server map { des-code | 
default } app-number
Delete the POS multi-application mapping tableundo pos-server map  { 
des-code | default }
OperationCommand
Bind the source address of TCP connectionpos-server source-ip app-number 
ip-address
Remove the binding of the source address of 
the TCP connectionundo pos-server source-ip 
app-number 
						

							100CHAPTER 7: POS TERMINAL ACCESS SERVICE
implemented otherwise, the system will prompt as follows to indicate that the 
configuration has failed: 
App-state is wrong.
7Set the parameters of FCM used during Modem negotiation
In the POS access application, the Modem on the FCM card usually acts as the 
called party, and the Modem embedded in the POS terminal acts as the calling 
party. In the Modem communication, the POS terminal originates a call after the 
called party detects the calling signal, it will answer and send an answer tone to 
the POS terminal. After the POS terminal receives answer tone, both sides begin 
the Modem negotiation (V.22). For a system with poor network quality, the short 
answer tone may cause Modem negotiation failure. On the router, in the case that 
you can see a constant UP and DOWN on the Modem port, without data being 
transmitted or received, just enlarge the value of ANSWERTIME.
After the negotiation reached, communication begins. The POS terminal adopts 
SDLC protocol, and the retransmission mechanism is used between the 
monitoring frame and the data frame to deal with abnormal occasions. The 
parameter PACKET INTERVAL is used to set the timeout value. For big packets 
(greater than 512 bytes), the system should enlarge the timeout value.
To improve the utilization of the POS access port, and to avoid a POS terminal 
being occupied for a long time, it is necessary to manage individual transaction 
times through configuring the parameter TRADETIME. If the maximum transaction 
time is exceeded after the POS terminal is dialed, the router will disconnect to 
unblock the resource.
In general, the default values of the parameters can satisfy the demands of 
application, but in abnormal occasions you need to modify some parameters.
Please perform the following configurations in system view.
Ta b l e 78   Set the parameters of FCM used during Modem negotiation
Display and Debug 
POS AccessPerform the following configuration in all views.
Ta b l e 79   Display and debug POS access 
OperationCommand
Set the parameters of FCM used 
during Modem negotiationpos-server fcm [ answertime time ] [ 
tradetime time ] [ packetinterval time ]
Restore the parameters of FCM 
used during Modem negotiationnoundo pos-server fcm [answertime time ] 
[tradetime time ] [ packetinterval time 
]
OperationCommand
Clear the counter of the displayed 
information.reset pos 
Clear the number of times that negotiation 
fails or the number of times of disconnection 
due to transaction timeout to zeroreset fcm
Display the brief information of POS 
application.display pos-app 
Display the brief information of POS interfacedisplay pos-interface 
Display the number of times that negotiation 
fails or the number of times of disconnection 
due to transaction times outdisplay fcm
Enable the debugging of POS applicationdebugging pos-app [ app-number ] 
						

							Typical Configuration Example of POS Access Service101
Typical Configuration 
Example of POS 
Access Service Configuration Example when the Router is Located at the FEP Side in 
TCP/IP Mode
I. Networking Requirements
Three POS terminals access the Router A located at the FEP side through the FCM 
card and connect to UNIX A (10.1.1.1) and UNIX B (10.1.1.2) in TCP/IP mode.
II. Networking Diagram
Figure 42   Networking diagram when the router is located at the FEP side in TCP/IP mode
III. Configuration Procedures
1Enable POS access server
[Router] pos-server enable
2Configure the POS application to UNIX A in TCP/IP connection mode, the 
application is 0.
[Router] pos-server app tcp 0 10.1.1.1 9010
3Configure the POS application to UNIX B in TCP/IP connection mode, the 
application is 1. 
[Router] pos-server app tcp 1 10.1.1.2 9020
4Configure the POS multi-application mapping table (to map the packet whose 
destination address is 01f1 to application 0). 
[Router] pos-server map 01f1 0
5Configure the POS multi-application mapping table (to map the packet whose 
destination address is 01f2 to application 1).
[Router] pos-server map 01f2 1
6Configure the Ethernet interface Ethernet 0.
[Router] interface ethernet 0
[Router-Ethernet0] ip address 10.1.1.3 255.255.255.0
7Configure the POS access interface FCM0
[Router] interface fcm0
[Router-FCM0] async mode pos 1
8Configure POS access interface FCM1
[Router] interface fcm1
[Router-FCM1] async mode pos 2
Enable the debugging of POS access interfacedebugging pos-interface [ pos-id 
]
UNIX B
PSTN
UNIX A 10. 1. 1.1/24
FCM
10.1.1.3/24E0
POS
term inal
10.1.1.2/24
Quidw ay
POS
term inal
POS
term inal
Router 
						

							102CHAPTER 7: POS TERMINAL ACCESS SERVICE
9Configure POS access interface FCM2
[Router] interface fcm2
[Router-FCM2] async mode pos 3
Configuration Example when the Router is Located at the FEP Side in 
Asynchronous Connection Mode
I. Networking Requirements
Three POS terminals access the Router A located at the FEP side through the FCM 
and connect to UNIX A (10.1.1.1) and UNIX B (11.1.1.1) in asynchronous 
connection mode.
II. Networking Diagram
Figure 43   Networking diagram when the router is located at the FEP side in asynchronous 
connection mode
III. Configuration Procedure
1Start the POS access server.
[Router] pos-server enable
2Configure the POS application to UNIX A in asynchronous connection mode, the 
connected interface is async 0, the application sequence number is 0.
[Router] pos-server app flow 0 async 0
3Configure the POS application to UNIX B in asynchronous connection mode, the 
connected interface is async 1, the application sequence number is 1.
[Router] pos-server app flow 1 async 1
4Configure the POS multi-application mapping table (to map the packet whose 
destination address is 01f1 to application 0).
[Router] pos-server map 01f1 0
5Configure the POS multi-application mapping table (to map the packet whose 
destination address is 01f2 to application 1).
[Router] pos-server map 01f2 1
6Configure POS access interface FCM0.
[Router] interface fcm0
[Router-FCM0] async mode pos 1
7Configure POS access interface FCM1.
[Router] interface fcm1
[Router-FCM1] async mode pos 2
8Configure POS access interface FCM2.
[Router] interface fcm2
PSTN
11.1.1.1/2410.1.1.1/24
A0
A1
FCM
POS
term inal11.1.1.2/24 Quidw ay
POS
term inalPOS
term inal
11.1.1.1/24UNIX B
UNIX A
Router 
						

							Typical Configuration Example of POS Access Service103
[Router-FCM2] async mode pos 3
9Configure Async 0 to operate in POS application mode.
[Router] interface async 0
[Router-Async0] undo modem
[Router-Async0] flow-control none
[Router-Async0] async mode posapp
10Configure Async 1 to operate in POS application mode.
[Router] interface async 1
[Router-Async1] undo modem
[Router-Async1] flow-control none
[Router-Async1] async mode posapp
Configuration Example when the Router is Located at the Commercial 
Client Side in TCP/IP Connection Mode
I. Networking Requirements
Three POS terminals access the 3Com Router series located at the commercial 
client through the asynchronous serial port and connect to UNIX host (10.1.1.1) in 
TCP/IP connection mode.
II. Networking Diagram
Figure 44   Networking diagram when the router is located at commercial client in TCP/IP 
connection mode.
III. Configuration Procedures
1Configure Router A
aStart the POS access server.
[RouterA] pos-server enable
bConfigure the POS application to destination UNIX host in TCP/IP connection 
mode. 
[RouterA] pos-server app tcp 0 10.1.1.1 9010
cConfigure POS default multi-application mapping table (to map the packet 
which cannot be matched with any application to the application).
[RouterA] pos-server map default 0
dConfigure POS access interface 0.
[RouterA] interface async 0
[RouterA-Async0] undo modem
[RouterA-Async0] flow-control none
[RouterA-Async0] undo detect dsr-dtr
[RouterA-Async0] async mode pos 1
eConfigure POS access interface 1.
UNIX FEP
IP
10.1.1.1/24 10.1.1.2/
24 172. 17. 0.2/
24 172. 17. 0.1/
24
E0
A1
A2 A0
S0
POS
term inal
Quidw ay  B
POS
term inal
POS
term inalQuidw ay  A
Router ARouter B 
						

							104CHAPTER 7: POS TERMINAL ACCESS SERVICE
[RouterA] interface async 1
[RouterA-Async1] undo modem
[RouterA-Async0] flow-control none
[RouterA-Async0] undo detect dsr-dtr
[RouterA-Async1] async mode pos 2
fConfigure POS access interface 2.
[RouterA] interface async 2
[RouterA-Async2] undo modem
[RouterA-Async0] flow-control none
[RouterA-Async0] undo detect dsr-dtr
[RouterA-Async2] async mode pos 3
gConfigure the route to Router B (take the static route as example).
[RouterA-Async2] quit
[RouterA] ip route-static 10.1.1.2 255.255.255.0 serial 0
2Configure Router B
aConfigure the Ethernet interface Ethernet 0.
[RouterB] interface ethernet 0
[RouterB-Ethernet0] ip address 10.1.1.2 255.255.255.0 
						

							III
INTERFACE
Chapter 8Interface Configuration Overview
Chapter 9Configuring LAN Interface
Chapter 10Configuring WAN Interface
Chapter 11Configuring Logical Interface 
						

							106