Page 3
The H3C MSR documentation set includes 14 configuration guides, which describe the software features for the H3C MSR Series Routers and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
Page 4
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 5
Obtaining documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support & Documents > Technical Documents]—Provides hardware installation, software...
Configuring POS terminal access This chapter describes how POS terminal access operates and how to configure POS terminal access. Overview The point of sale (POS) access service is a smart card service. It enables a POS terminal to access a bank card accounting system.
For a POS terminal template using TCP access mode, a TCP connection is referred to as an instance • for the terminal template, and a terminal template can have multiple instances. For a POS terminal using dial-up or flow access mode, a physical link is referred to as an instance •...
Page 10
No service queuing because each POS terminal uses a dedicated line (except networks consisting • of POS concentrator and POS terminals). Figure 2 Network diagram In POS flow access mode, the following methods are available for connecting a POS terminal to the router: Method 1—Directly connect the RS-232 interface of the POS terminal to the asynchronous interface •...
Figure 3 Network diagram for POS TCP access POS application template connection modes A POS application template communicates with an FEP either through a TCP connection or a flow connection, depending on the connection mode of the FEP to the POS access device. Upon receiving a packet from a POS terminal, the POS access device processes the packet as follows: Encapsulates the packet according to the connection mode of the corresponding POS application template.
Figure 4 Network diagram of POS application connections Ethernet POS terminal device IP network Flow connection Ethernet POS Router terminal device Bank FEP 1 (POS access device) IP network Bank FEP 2 Ethernet POS terminal device IP packet RS485 transmmission media RS232 Cascade mode of POS access devices You can also connect POS terminals to POS access devices in cascade mode, as shown in...
Use temporary TCP connection mode for POS applications on Router A. • TPDU Transport Protocol Data Unit (TPDU) is a field in a POS packet. A TPDU header is five bytes in length and includes the following options: ID—One byte. It identifies the TPDU type. Typically, the correct packet type is 0x60. The incorrect •...
POS application mapping The router uses the POS application mapping table to send packets from POS terminals to different FEPs. The router sends packets according to the originator address and destination address in the TPDU header of the packets. The router must operate in nontransparent mode to implement POS application mapping. Figure 6 shows a typical example of application mapping.
C: Caller-IP = 192.167.0.0, mask = 255.255.0.0 When a POS terminal sends packets with source IP address 192.168.1.2, the packets are counted for both item A and item B. Statistics based on caller numbers This method collects statistics for POS terminals that do not use TCP access. When POS terminals transact with the FEPs, the router counts the packets based on the configured caller numbers.
If both the primary and backup FEPs are in non-blocked state, the router initiates a connection with • the primary FEP. If the connection fails, with the backup FEP. If only one FEP is in non-blocked state, the router initiates a connection with the FEP in non-blocked •...
Enabling the POS access service Step Command Remarks Enter system view. system-view Enable the POS access By default, the POS terminal posa server enable service. access service is disabled. Configuring a POS terminal template The configurations vary with the POS terminal access modes. Configuring a POS terminal template in TCP access mode Step Command...
POS access interface. To specify a POS application template Specify the current interface posa bind terminal terminal-id by the app keyword, H3C recommends as a POS access interface. [ app app-id ] that you configure the template first. For more information, see "Configuring a...
Page 19
Step Command Remarks Changes to the keepalive parameters take effect immediately. When the TCP (Optional.) Configure the connections are terminated because of TCP keepalive parameters tcp keepalive interval time the keepalive detection mechanism, it for the POS application count counts will not trigger the switch between the template.
Step Command Remarks By default, no backup POS application template is specified. This command is applicable only to (Optional.) Specify the TCP-based POS application templates. If backup POS application backup app app-id the specified application template does template. not exist or is not TCP type, the command can be configured but it does not take effect.
Configuring POS terminal packet statistics Perform this task to configure the router to collect POS terminal packet statistics based on source IP addresses or caller numbers. To configure POS packet statistics collection: Step Command Remarks Enter system view. system-view • To create a source IP group for Use either command.
Verifying the configuration The POS terminal device sends a POS request packet. The router processes the packet and forwards it to the bank FEP. The FEP receives the request packet and responds with a reply packet. The POS terminal device receives the reply packet. POS access devices cascade mode configuration example Network requirements As shown in...
# Specify the IP address and port number of the corresponding FEP as 10.1.1.1 and 2000. [RouterB-posa-app1] ip 10.1.1.1 port 2000 [RouterB-posa-app1] quit # Configure terminal template 1 in TCP mode, and configure its listening port number as 3200. [RouterB] posa terminal 1 type tcp listen-port 3200 # Configure a default application mapping entry to map all packets to application template 1.
Page 26
[RouterA-posa-app1] hello enable [RouterA-posa-app1] timer hello 10 # Specify application template 2 as the backup application template. [RouterA-posa-app1] backup app 2 # Set the quiet timer for POS application template 1 to 10 minutes. [RouterA-posa-app1] timer quiet 10 [RouterA-posa-app1] quit Configure POS application template 2: # Configure application template 2 in TCP mode.
Backup FEP configuration example (transparent mode) Network requirements In transparent mode, a pair of primary and backup FEPs can provide service for only one POS terminal. As shown in Figure 1 1, FEP-A (primary FEP) and FEP-B (backup FEP) provide service for the AM POS terminal.
Page 28
Verifying the configuration Follow these steps to verify the backup FEP function for the POS terminal that uses AM 5/0: Send a POS packet from the POS terminal when FEP-A is reachable. Router A forwards the packet to FEP-A. FEP-A receives the packet and responds with a reply packet. The POS terminal device receives the reply packet successfully.
Need help?
Do you have a question about the MSR Series and is the answer not in the manual?
Questions and answers