CISCO-LPTS-MIB
AI MIB Summary
The CISCO-LPTS-MIB monitors the Local Packet Transport Services subsystem on Cisco routers to track per-protocol flow classifications, trust levels, and associated policer rate limits (PPS) that govern the ingress traffic volume destined for the control plane. It provides visibility into how specific protocols are segmented into distinct flows across line cards and nodes, enabling the verification of traffic policing policies that protect the router's CPU from excessive packet processing.
The MIB module for Local Packet Transport Services(LPTS) related information like the flows and the policer values related to various flows present in the system.
The number of packets coming into the system is controlled by the policer values associated with the protocol. Each protocol is classified into different flows and a rate limit is associated with the flows. Policer is a numerical value controlling the number of packets entering the box.
The flows represent individual, specific protocols. Flow types also represent the degree of trust for a given packet. Ex: BGP packets coming from established session is assigned one flow, packets from configured BGP peer are assigned different flow . Other BGP packets are assigned a third flow.
Definitions:
LPTS - Local Packet Transport Services. It is a network infrastructure subsystem that provides a common facility for transport of packets which are destined towards the router (for-us packets), to the exact applications. In addtion to that, it also provides policing of for-us packets FlowType - Represents individual, specific protocols. Flow also represents the degree of trust for a given packet. LC - Line Cards. Policer - Index to FlowType. CurrentRate - Number of packets allowed into the box in PPS (Packets Per Second). Type - Defines the scope of the flow applicable at a specific node or Line card. Precedence - Precedence is the selection mechanism for a specific Type if more than one Type is configured for the same flow. 'local' FlowType has higher precedence over 'global' and 'static' FlowTypes. 'global' FlowType has higher precedence over 'static' FlowType. nodeID - The line card for which the flow configuration is made.
Main OID:
ciscoLptsMIB.1.3.6.1.4.1.9.9.812
20
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
20 total| Object Name |
|---|
ciscoLptsMIBThe MIB module for Local Packet Transport Services(LPTS)
related information like the flows and the policer
values related to various flows present in the system.
The number of packets coming into the system is controlled
by the policer values associated with the protocol. Each
protocol is classified into different flows and a rate
limit is associated with the flows. Policer is a numerical
value controlling the number of packets entering the box.
The flows represent individual, specific protocols.
Flow types also represent the degree of trust for a given
packet. Ex: BGP packets coming from established session is
assigned one flow, packets from configured BGP peer are
assigned different flow . Other BGP packets are assigned
a third flow.
Definitions:
LPTS - Local Packet Transport Services.
It is a network infrastructure
subsystem that provides a common
facility for transport of packets
which are destined towards the router
(for-us packets), to the exact
applications. In addtion
to that, it also
provides policing of for-us packets
FlowType - Represents individual, specific protocols.
Flow also represents the degree of trust
for a given packet.
LC - Line Cards.
Policer - Index to FlowType.
CurrentRate - Number of packets allowed
into the box in PPS (Packets Per Second).
Type - Defines the scope of the flow applicable at
a specific node or Line card.
Precedence - Precedence is the selection mechanism for
a specific Type if more than one Type is
configured for the same flow. 'local'
FlowType has higher precedence over 'global'
and 'static' FlowTypes. 'global' FlowType has
higher precedence over 'static' FlowType.
nodeID - The line card for which the flow configuration
is made. MODULE-IDENTITY .1.3.6.1.4.1.9.9.812 |
ciscoLptsMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.812.0 |
ciscoLptsMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.812.1 |
clGlobalFlowTableThis table respresents the flows configured globally and
the configuration will be reflected across all the linecards SEQUENCE OF ClGlobalFlowEntry .1.3.6.1.4.1.9.9.812.1.1 |
clGlobalFlowEntryAn entry will be added into clGlobalFlowTable
when LPTS flows configured without any
location specific details. Similarly when the global
LPTS flow config is removed, then type and rate
retained as per Static config file. The entries in this
table can be of Type either 'global' or 'static'. ClGlobalFlowEntry .1.3.6.1.4.1.9.9.812.1.1.1 |
clGlobalFlowIndexAn unique value used to represent a
row in the clGlobalFlowTable Unsigned32 .1.3.6.1.4.1.9.9.812.1.1.1.1 |
clGlobalFlowTypeThis object indicates the flow type name
associated with every flow.
Eg. FlowType could be BGP-Known, BGP-configured
BGP-default.ro SnmpAdminString .1.3.6.1.4.1.9.9.812.1.1.1.2 |
clGlobalTypeThis object indicates an enumeration
which indicates whether LPTS flow
configured across all the linecards are 'global' or
'static' depending on the predecedencero ClFlowType .1.3.6.1.4.1.9.9.812.1.1.1.3 |
clGlobalCurrentRateThis object specifies the rate associated
with the flow type which is configured
globally.rw Unsigned32 UNITS "PPS" .1.3.6.1.4.1.9.9.812.1.1.1.4 |
clLocalFlowTableThis table represents the configurations for the local
flow types & affects a
particular nodeID for which config is applied.
When local flow type is not configured & we have a global
configuration then the clLocalFlowTable has global flow value.
If neither local flow nor the global flows are
configured, then clLocalFlowTable will have static
values derived from the config file. If both the local
flow and global flow is configured, then the local flow
information takes precedence over the global flow
information. SEQUENCE OF ClLocalFlowEntry .1.3.6.1.4.1.9.9.812.1.2 |
clLocalFlowEntryAn entry in clLocalFlowTable will be added when LPTS flows
are configured specific to a location. This table is indexed
based on nodeID and clGlobalFlowIndex. When NMS polls for flow
in clLocalFlowTable, the flow name is retrieved from the
clGlobalFlowTable. When a local configuration is removed for
a flow, then clGlobalCurrentRate will be applied if it
is present, else static rate will be applied. ClLocalFlowEntry .1.3.6.1.4.1.9.9.812.1.2.1 |
clLocalNodeIDThe linecard for which the flow configuration is made. Unsigned32 .1.3.6.1.4.1.9.9.812.1.2.1.1 |
clLocalTypeThis object indicates an enumeration
which indicates LPTS flows
configured specific to a linecardro ClFlowType .1.3.6.1.4.1.9.9.812.1.2.1.2 |
clLocalCurrentRateThis object indicates the packet rate associated
with the flow type with which packets
are accepted or dropped specific to a linecard.ro Unsigned32 UNITS "PPS" .1.3.6.1.4.1.9.9.812.1.2.1.3 |
clLocalAcceptedThis object indicates the total number of packets accepted
on a linecard for a specific flow.ro Counter64 .1.3.6.1.4.1.9.9.812.1.2.1.4 |
clLocalDroppedThis object indicates the total number of packets dropped on
a linecard for a specific flow.ro Counter64 .1.3.6.1.4.1.9.9.812.1.2.1.5 |
clLocalTosValueThis object indicates the type of service.ro Unsigned32 .1.3.6.1.4.1.9.9.812.1.2.1.6 |
ciscoLptsMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.812.2 |
ciscoLptsMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.812.2.1 |
ciscoLptsMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.812.2.2 |