Local Packet Transport Services (LPTS) maintains tables describing all packet flows destined for the secure domain router (SDR), making sure that packets are delivered to their intended destinations.
For a complete description of the LPTS commands listed in this module, refer to the LPTS Commands
Cisco ASR 9000 Series
Aggregation Services Router IP Addresses and Services Command
The following prerequisites are required to implement LPTS:
You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
Information About Implementing LPTS
To implement LPTS features mentioned in this document you must understand the following concepts:
LPTS uses two components to accomplish this task: the port arbitrator and flow managers.
The port arbitrator and flow managers are processes that maintain the tables that describe
packet flows for a logical router, known as the Internal Forwarding Information Base
(IFIB). The IFIB is used to route received packets to the correct Route Processor or line
card for processing.
LPTS interfaces internally with all applications that receive packets from outside the
router. LPTS functions without any need for customer configuration. However, LPTS
show commands are provided that allow customers to monitor
the activity and performance of LPTS flow managers and the port arbitrator.
In Cisco IOS XR, the control packets, which are destined to the Route Processor (RP), are policed using a set of ingress policers in the incoming line cards. These policers are programmed statically during bootup by LPTS components. The policers are applied based on the flow type of the incoming control traffic. The flow type is determined by looking at the packet headers. The policer rates for these static ingress policers are defined in a configuration file, which are programmed on the line card during bootup.
You can change the policer values based on the flow types of these set of ingress policers. You are able to configure the rate per policer per node (locally) and globally using the command-line interface (CLI); therefore, overwriting the static policer values.
How to Implement LPTS
This section contains instructions for the following task:
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.