Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify parameters for packets that match specific criteria such as ACLs or that have specific lengths. The parameters include the next hop, output interface, default next hop, and default output interface.

A device forwards received packets using the following process:

1. The device uses PBR to forward matching packets.

2. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets.

3. If the routing table-based forwarding fails, the device uses the default next hop or default output interface defined in PBR to forward packets.

4. If the default next hop or default output interface-based forwarding fails, the device uses the default route to forward packets.

PBR includes local PBR and interface PBR.

· Local PBR guides the forwarding of locally generated packets, such as the ICMP packets generated by using the ping command.

· Interface PBR guides the forwarding of packets received on an interface only.

Policy

A policy includes match criteria and actions to be taken on the matching packets. A policy can have one or multiple nodes as follows:

· Each node is identified by a node number. A smaller node number has a higher priority.

· A node contains if-match and apply clauses. An if-match clause specifies a match criterion, and an apply clause specifies an action.

· A node has a match mode of permit or deny.

A policy compares packets with nodes in priority order. If a packet matches the criteria on a node, it is processed by the action on the node. Otherwise, it goes to the next node for a match. If the packet does not match the criteria on any node, it is forwarded according to the routing table.

if-match clause

PBR supports the following types of if-match clauses:

· if-match acl—Sets an ACL match criterion.

· if-match packet-length—Sets a packet length match criterion to match the total length of data packets.

On a node, you can specify multiple types of if-match clauses but only one if-match clause for each type. To match a node, a packet must match all types of the if-match clauses for the node but only one if-match clause of each type.

apply clause

PBR supports the types of apply clauses shown in Table 1. You can specify multiple apply clauses for a node, but some of them might not be executed. The following apply clauses determine the packet forwarding paths in a descending order:

· apply access-vpn vpn-instance

· apply remark-vpn

· apply next-hop

· apply output-interface

· apply default-next-hop

· apply default-output-interface

Table 1 Priorities and meanings of apply clauses

Clause	Meaning	Priority
apply precedence	Sets an IP precedence.	This clause is always executed.
apply ip-df df-value	Sets the Don't Fragment (DF) bit in the IP header.	This clause is always executed.
apply loadshare { next-hop \| output-interface \| default-next-hop \| default-output-interface }	Enables load sharing among multiple next hops, output interfaces, default next hops, and default output interfaces.	Multiple next hops, output interfaces, default next hops, or default output interfaces operate in either primary/backup or load sharing mode. For example: · Primary/backup mode—The first configured output interface is used. When the primary output interface fails, the first configured backup output interface takes over. · Load sharing mode—Multiple output interfaces load share traffic on a per-packet basis in turn, according to the configuration order. Multiple next hops load share traffic according to their weights. By default, the primary/backup mode applies.
apply access-vpn vpn-instance	Sets VPN instances.	If a packet matches a forwarding entry of a specified VPN instance, it is forwarded in the VPN instance.
apply remark-vpn	Marks the VPN instance for matching packets.	This clause must be used together with the apply access-vpn vpn-instance clause.
apply next-hop and apply output-interface	Sets next hops and sets output interfaces.	Only the apply next-hop clause is executed when both are configured.
apply default-next-hop and apply default-output-interface	Sets default next hops and sets default output interfaces.	Only the apply default-next-hop clause is executed when both are configured. They take effect only when no next hop or output interface is set or the next hop and output interface are invalid, and the packet does not match any route in the routing table.
apply continue	Compares packets with the next node upon failure on the current node.	The apply continue clause applies when the apply access-vpn vpn-instance, apply next-hop, apply output-interface, apply default-next-hop, and apply default-output-interface clauses are not configured or become invalid. For example, the specified next hop is unreachable, the specified output interface is down, or the packets cannot be forwarded in the specified VPN instance.

Relationship between the match mode and clauses on the node

Does a packet match all the if-match clauses on the node?	Match mode
Does a packet match all the if-match clauses on the node?	Permit	Deny
Yes.	· If the node is configured with apply clauses, PBR executes the apply clauses on the node. ¡ If the PBR-based forwarding succeeds, PBR does not compare the packet with the next node. ¡ If the PBR-based forwarding fails and the apply continue clause is not configured, PBR does not compare the packet with the next node. ¡ If the PBR-based forwarding fails and the apply continue clause is configured, PBR compares the packet with the next node. · If the node is configured with no apply clauses, the packet is forwarded according to the routing table.	The packet is forwarded according to the routing table.
No.	PBR compares the packet with the next node.	PBR compares the packet with the next node.

A node that has no if-match clauses matches any packet.

PBR and Track

PBR can work with the Track feature to dynamically adapt the availability status of an apply clause to the link status of a tracked object. The tracked object can be a next hop, output interface, default next hop, or default output interface.

· When the track entry associated with an object changes to Negative, the apply clause is invalid.

· When the track entry changes to Positive or NotReady, the apply clause is valid.

For more information about Track-PBR collaboration, see High Availability Configuration Guide.

PBR configuration task list

Tasks at a glance
(Required.) Configuring a policy: · Creating a node · Setting match criteria for a node · Configuring actions for a node
(Required.) Configuring PBR: · Configuring local PBR · Configuring interface PBR

Tasks at a glance

(Required.) Configuring a policy:

· Creating a node

· Setting match criteria for a node

· Configuring actions for a node

(Required.) Configuring PBR:

· Configuring local PBR

· Configuring interface PBR

Configuring a policy

Creating a node

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a node for a policy, and enter its view.	policy-based-route policy-name [ deny \| permit ] node node-number	By default, no policy nodes exist.

Setting match criteria for a node

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter policy node view.	policy-based-route policy-name [ deny \| permit ] node node-number	N/A
3. Set an ACL match criterion.	if-match acl { acl-number \| name acl-name }	By default, no ACL match criterion is set. The ACL match criterion cannot match Layer 2 information.
4. Set a packet length match criterion.	if-match packet-length min-len max-len	By default, no packet length match criterion is set.

NOTE:

An ACL match criterion uses the specified ACL to match packets if the action in ACL rules is permit. If the specified ACL does not exist or the action in ACL rules is deny, no packet is matched.

Configuring actions for a node

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter policy node view.	policy-based-route policy-name [ deny \| permit ] node node-number	N/A
3. Set an IP precedence.	apply precedence { type \| value }	By default, no IP precedence is specified.
4. Set the DF bit in the IP header.	apply ip-df df-value	By default, the DF bit in the IP header is not set.
5. Set VPN instances.	apply access-vpn vpn-instance vpn-instance-name&<1-n>	By default, no VPN instance is specified. You can specify a maximum of n VPN instances for a node. The matching packets are forwarded according to the forwarding table of the first available VPN instance. The value of n is 4.
6. Mark the VPN instance for matching packets.	apply remark-vpn	By default, the VPN instance is not marked for matching packets.
7. Set next hops.	apply next-hop [ vpn-instance vpn-instance-name \| inbound-vpn ] { ip-address [ direct ] [ track track-entry-number ] [ weight weight-value ] }&<1-n>	By default, no next hop is specified. You can specify multiple next hops for backup or load sharing in one command line or by executing this command multiple times. You can specify a maximum of n next hops for a node. The value of n is 4.
8. Enable load sharing among multiple next hops.	apply loadshare next-hop	By default, the next hops operate in primary/backup mode.
9. Set output interfaces.	apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>	By default, no output interface is specified. You can specify multiple output interfaces for backup or load sharing in one command line or by executing this command multiple times. You can specify a maximum of n output interfaces for a node. The value of n is 4.
10. Enable load sharing among multiple output interfaces.	apply loadshare output-interface	By default, the output interfaces operate in primary/backup mode.
11. Set default next hops.	apply default-next-hop [ vpn-instance vpn-instance-name \| inbound-vpn ] { ip-address [ direct ] [ track track-entry-number ] }&<1-n>	By default, no default next hop is specified. You can specify multiple default next hops for backup or load sharing in one command line or by executing this command multiple times. You can specify a maximum of n default next hops for a node. The value of n is 4.
12. Enable load sharing among multiple default next hops.	apply loadshare default-next-hop	By default, the default next hops operate in primary/backup mode.
13. Set default output interfaces.	apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>	By default, no default output interface is specified. You can specify multiple default output interfaces for backup or load sharing in one command line or by executing this command multiple times. You can specify a maximum of n default output interfaces for a node. The value of n is 4.
14. Enable load sharing among multiple default output interfaces.	apply loadshare default-output-interface	By default, the default output interfaces operate in primary/backup mode.
15. Compare packets with the next node upon match failure on the current node.	apply continue	By default, PBR does not compare packets with the next node upon match failure on the current node. This command takes effect only when the match mode of the node is permit.

Configuring PBR

Configuring local PBR

Configure PBR by applying a policy locally. PBR uses the policy to guide the forwarding of locally generated packets. The specified policy must already exist. Otherwise, the local PBR configuration fails.

You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.

Local PBR might affect local services, such as ping and Telnet. Do not configure local PBR unless doing so is required.

To configure local PBR:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Apply a policy locally.	ip local policy-based-route policy-name	By default, no policy is locally applied.

Configuring interface PBR

Configure PBR by applying a policy to an interface. PBR uses the policy to guide the forwarding of packets received on the interface. The specified policy must already exist. Otherwise, the interface PBR configuration fails.

You can apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface.

You can apply a policy to multiple interfaces.

To configure interface PBR:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Apply a policy to the interface.	ip policy-based-route policy-name	By default, no policy is applied to the interface.

Displaying and maintaining PBR

Execute display commands in any view and reset commands in user view.

Task	Command
Display PBR policy information.	display ip policy-based-route [ policy policy-name ]
Display PBR configuration.	display ip policy-based-route setup
Display local PBR configuration and statistics (in standalone mode).	display ip policy-based-route local [ slot slot-number ]
Display local PBR configuration and statistics (in IRF mode).	display ip policy-based-route local [ chassis chassis-number slot slot-number ]
Display interface PBR configuration and statistics (in standalone mode).	display ip policy-based-route interface interface-type interface-number [ slot slot-number ]
Display interface PBR configuration and statistics (in IRF mode).	display ip policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number ]
Clear PBR statistics.	reset ip policy-based-route statistics [ policy policy-name ]

PBR configuration examples

Packet type-based local PBR configuration example

Network requirements

As shown in Figure 1, Router B and Router C cannot reach each other.

Configure PBR on Router A to forward all TCP packets to the next hop 1.1.2.2.

Figure 1 Network diagram

Configuration procedure

1. Configure Router A:

# Configure the IP addresses of GigabitEthernet 1/1/1 and GigabitEthernet 1/1/2.

<RouterA> system-view

[RouterA] interface gigabitethernet 1/1/1

[RouterA-GigabitEthernet1/1/1] ip address 1.1.2.1 24

[RouterA-GigabitEthernet1/1/1] quit

[RouterA] interface gigabitethernet 1/1/2

[RouterA-GigabitEthernet1/1/2] ip address 1.1.3.1 24

[RouterA-GigabitEthernet1/1/2] quit

# Configure ACL 3101 to match TCP packets.

[RouterA] acl advanced 3101

[RouterA-acl-ipv4-adv-3101] rule permit tcp

[RouterA-acl-ipv4-adv-3101] quit

# Configure Node 5 for the policy aaa to forward TCP packets to next hop 1.1.2.2.

[RouterA] policy-based-route aaa permit node 5

[RouterA-pbr-aaa-5] if-match acl 3101

[RouterA-pbr-aaa-5] apply next-hop 1.1.2.2

[RouterA-pbr-aaa-5] quit

# Configure local PBR by applying the policy aaa to Router A.

[RouterA] ip local policy-based-route aaa

2. On Router B, configure the IP address of GigabitEthernet 1/1/1.

<RouterB> system-view

[RouterB] interface gigabitethernet 1/1/1

[RouterB-GigabitEthernet1/1/1] ip address 1.1.2.2 24

3. On Router C, configure the IP address of GigabitEthernet 1/1/2.

<RouterC> system-view

[RouterC] interface gigabitethernet 1/1/2

[RouterC-GigabitEthernet1/1/2] ip address 1.1.3.2 24

Verifying the configuration

# Telnet to Router B on Router A. The operation succeeds. (Details not shown.)

# Telnet to Router C on Router A. The operation fails. (Details not shown.)

# Ping Router C from Router A. The operation succeeds. (Details not shown.)

Telnet uses TCP, and ping uses ICMP. The results show the following:

· All TCP packets sent from Router A are forwarded to the next hop 1.1.2.2.

· Other packets are forwarded through GigabitEthernet 1/1/2.

· The local PBR configuration is effective.

Packet type-based interface PBR configuration example

Network requirements

As shown in Figure 2, Router B and Router C cannot reach each other.

Configure PBR on Router A to forward all TCP packets received on GigabitEthernet 1/1/1 to the next hop 1.1.2.2.

Figure 2 Network diagram

Configuration procedure

1. Make sure Router B and Router C can reach Host A. (Details not shown.)

2. Configure Router A:

# Configure the IP addresses of GigabitEthernet 1/1/2 and GigabitEthernet 1/1/3.

<RouterA> system-view

[RouterA] interface gigabitethernet 1/1/2

[RouterA-GigabitEthernet1/1/2] ip address 1.1.2.1 24

[RouterA-GigabitEthernet1/1/2] quit

[RouterA] interface gigabitethernet 1/1/3

[RouterA-GigabitEthernet1/1/3] ip address 1.1.3.1 24

[RouterA-GigabitEthernet1/1/3] quit

# Configure ACL 3101 to match TCP packets.

[RouterA] acl advanced 3101

[RouterA-acl-ipv4-adv-3101] rule permit tcp

[RouterA-acl-ipv4-adv-3101] quit

# Configure Node 5 for the policy aaa to forward TCP packets to next hop 1.1.2.2.

[RouterA] policy-based-route aaa permit node 5

[RouterA-pbr-aaa-5] if-match acl 3101

[RouterA-pbr-aaa-5] apply next-hop 1.1.2.2

[RouterA-pbr-aaa-5] quit

# Configure interface PBR by applying the policy aaa to GigabitEthernet 1/1/1.

[RouterA] interface gigabitethernet 1/1/1

[RouterA-GigabitEthernet1/1/1] ip address 10.110.0.10 24

[RouterA-GigabitEthernet1/1/1] ip policy-based-route aaa

[RouterA-GigabitEthernet1/1/1] quit

Verifying the configuration

# On Host A, Telnet to Router B that is directly connected to Router A. The operation succeeds. (Details not shown.)

# On Host A, Telnet to Router C that is directly connected to Router A. The operation fails. (Details not shown.)

# Ping Router C from Host A. The operation succeeds. (Details not shown.)

Telnet uses TCP, and ping uses ICMP. The results show the following:

· All TCP packets arriving on GigabitEthernet 1/1/1 of Router A are forwarded to the next hop 1.1.2.2.

· Other packets are forwarded through GigabitEthernet 1/1/3.

· The interface PBR configuration is effective.

Packet length-based interface PBR configuration example

Network requirements

As shown in Figure 3, configure interface PBR to guide the forwarding of packets received on GigabitEthernet 1/1/1 of Router A as follows:

· Set the next hop of packets with a length of 64 to 300 bytes to 150.1.1.2/24.

· Set the next hop of packets with a length of 301 to 1000 bytes to 151.1.1.2/24.

Figure 3 Network diagram

Configuration procedure

1. Configure Router A:

# Configure the IP addresses of GigabitEthernet 1/1/2 and GigabitEthernet 1/1/3.

<RouterA> system-view

[RouterA] interface gigabitethernet 1/1/2

[RouterA-GigabitEthernet1/1/2] ip address 150.1.1.1 24

[RouterA-GigabitEthernet1/1/2] quit

[RouterA] interface gigabitethernet 1/1/3

[RouterA-GigabitEthernet1/1/3] ip address 151.1.1.1 24

[RouterA-GigabitEthernet1/1/3] quit

# Configure RIP.

[RouterA] rip

[RouterA-rip-1] network 192.1.1.0

[RouterA-rip-1] network 150.1.0.0

[RouterA-rip-1] network 151.1.0.0

[RouterA-rip-1] quit

# Configure Node 10 for the policy lab1 to forward packets with a length of 64 to 300 bytes to the next hop 150.1.1.2.

[RouterA] policy-based-route lab1 permit node 10

[RouterA-pbr-lab1-10] if-match packet-length 64 300

[RouterA-pbr-lab1-10] apply next-hop 150.1.1.2

[RouterA-pbr-lab1-10] quit

# Configure Node 20 for the policy lab1 to forward packets with a length of 301 to 1000 bytes to the next hop 151.1.1.2.

[RouterA] policy-based-route lab1 permit node 20

[RouterA-pbr-lab1-20] if-match packet-length 301 1000

[RouterA-pbr-lab1-20] apply next-hop 151.1.1.2

[RouterA-pbr-lab1-20] quit

# Configure interface PBR by applying the policy lab1 to GigabitEthernet 1/1/1.

[RouterA] interface gigabitethernet 1/1/1

[RouterA-GigabitEthernet1/1/1] ip address 192.1.1.1 24

[RouterA-GigabitEthernet1/1/1] ip policy-based-route lab1

[RouterA-GigabitEthernet1/1/1] quit

2. Configure Router B:

# Configure the IP addresses of GigabitEthernet 1/1/2 and GigabitEthernet 1/1/3.

<RouterB> system-view

[RouterB] interface gigabitethernet 1/1/2

[RouterB-GigabitEthernet1/1/2] ip address 150.1.1.2 24

[RouterB-GigabitEthernet1/1/2] quit

[RouterB] interface gigabitethernet 1/1/3

[RouterB-GigabitEthernet1/1/3] ip address 151.1.1.2 24

[RouterB-GigabitEthernet1/1/3] quit

# Configure the loopback interface address.

[RouterB] interface loopback 0

[RouterB-LoopBack0] ip address 10.1.1.1 32

[RouterB-LoopBack0] quit

# Configure RIP.

[RouterB] rip

[RouterB-rip-1] network 10.0.0.0

[RouterB-rip-1] network 150.1.0.0

[RouterB-rip-1] network 151.1.0.0

[RouterB-rip-1] quit

Verifying the configuration

# Execute the debugging ip policy-based-route command on Router A.

<RouterA> debugging ip policy-based-route

<RouterA> terminal logging level 7

<RouterA> terminal monitor

# Ping Loopback 0 of Router B from Host A, and set the data length to 64 bytes. In this way, the total length of the data packet is in the range of 64 to 300 bytes.

C:\>ping –n 1 -l 64 10.1.1.1

Pinging 10.1.1.1 with 64 bytes of data:

Reply from 10.1.1.1: bytes=64 time=1ms TTL=64

Ping statistics for 10.1.1.1:

Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 1ms, Average = 1ms

The debugging information about PBR displayed on Router A is as follows:

*Jun 26 12:04:33:519 2012 RouterA PBR4/7/PBR Forward Info: -MDC=1; Policy:lab1, Node:

10,match succeeded.

*Jun 26 12:04:33:519 2012 RouterA PBR4/7/PBR Forward Info: -MDC=1; apply next-hop 150

.1.1.2.

The output shows that Router A sets the next hop for the received packets to 150.1.1.2 according to PBR. The packets are forwarded through GigabitEthernet 1/1/2.

# Ping Loopback 0 of Router B from Host A, and set the data length to 300 bytes. In this way, the total length of the data packet is in the range of 301 to 1000 bytes.

C:\> ping –n 1 -l 300 10.1.1.1

Pinging 10.1.1.1 with 300 bytes of data:

Reply from 10.1.1.1: bytes=300 time=1ms TTL=64

Ping statistics for 10.1.1.1:

Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 1ms, Average = 1ms

The debugging information about PBR displayed on Router A is as follows:

*Jun 26 12:20:33:610 2012 RouterA PBR4/7/PBR Forward Info: -MDC=1; Policy:lab1, Node:

20,match succeeded.

*Jun 26 12:20:33:610 2012 RouterA PBR4/7/PBR Forward Info: -MDC=1; apply next-hop 151

.1.1.2.

The output shows that Router A sets the next hop for the received packets to 151.1.1.2 according to PBR. The packets are forwarded through GigabitEthernet 1/1/3.

Packet source-IP-based interface PBR configuration example

Network requirements

As shown in Figure 4, Router B and Router C cannot reach each other.

Configure interface PBR to guide the forwarding of packets received on GigabitEthernet 1/1/1 of Router A as follows:

· Set the next hop of packets sourced from 192.168.10.2 to 4.1.1.2/24.

· Set the next hop of other packets to 5.1.1.2/24.

Figure 4 Network diagram

Configuration procedure

1. Make sure Router B can reach Host A and Host B, and Router C can reach Host A and Host B. (Details not shown.)

2. Configure Router A:

# Configure the IP addresses of GigabitEthernet 1/1/2 and GigabitEthernet 1/1/3.

<RouterA> system-view

[RouterA] interface gigabitethernet 1/1/2

[RouterA-GigabitEthernet1/1/2] ip address 4.1.1.1 24

[RouterA-GigabitEthernet1/1/2] quit

[RouterA] interface gigabitethernet 1/1/3

[RouterA-GigabitEthernet1/1/3] ip address 5.1.1.1 24

[RouterA-GigabitEthernet1/1/3] quit

# Configure ACL 2000 to match packets sourced from 192.168.10.2.

[RouterA] acl basic 2000

[RouterA-acl-ipv4-basic-2000] rule 10 permit source 192.168.10.2 0

[RouterA-acl-ipv4-basic-2000] quit

# Configure Node 0 for the policy aaa to forward packets sourced from 192.168.10.2 to next hop 4.1.1.2. Configure Node 1 for the policy aaa to forward other packets to next hop 5.1.1.2.

[RouterA] policy-based-route aaa permit node 0

[RouterA-pbr-aaa-0] if-match acl 2000

[RouterA-pbr-aaa-0] apply next-hop 4.1.1.2

[RouterA-pbr-aaa-0] quit

[RouterA] policy-based-route aaa permit node 1

[RouterA-pbr-aaa-1] apply next-hop 5.1.1.2

[RouterA-pbr-aaa-1] quit

# Configure interface PBR by applying the policy aaa to GigabitEthernet 1/1/1.

[RouterA] interface gigabitethernet 1/1/1

[RouterA-GigabitEthernet1/1/1] ip address 192.168.10.1 24

[RouterA-GigabitEthernet1/1/1] ip policy-based-route aaa

[RouterA-GigabitEthernet1/1/1] quit

Verifying the configuration

# Configure IP address 192.168.10.3/24 for Host B, and specify its gateway address as 192.168.10.1. (Details not shown.)

# Ping Router B from Host A. The operation succeeds. (Details not shown.)

# Ping Router B from Host B. The operation fails. (Details not shown.)

# Ping Router C from Host A. The operation fails. (Details not shown.)

# Ping Router C from Host B. The operation succeeds. (Details not shown.)

The results show the following:

· All packets sourced from 192.168.10.2 are forwarded to the next hop 4.1.1.2.

· Packets sourced from 192.168.10.3 are forwarded to the next hop 5.1.1.2.

· The interface PBR configuration is effective.

07-Layer 3 - IP Routing Configuration Guide

Overview

if-match clause

apply clause

Relationship between the match mode and clauses on the node

PBR and Track

Configuring a policy

Creating a node

Setting match criteria for a node

Configuring actions for a node

Configuring PBR

Displaying and maintaining PBR

PBR configuration examples

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Packet length-based interface PBR configuration example

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us