-
Cisco IOS IP Application Services Command Reference
-
Introduction
-
carrier-delay (tracking) through forwarding-agent
-
ip accounting through ip sctp authenticate
-
ip tcp adjust-mss through ipv6 tcp adjust-mss
-
mls ip install-threshold through platform trace runtime process forwarding-manager module wccp
-
sctp through show ip sctp statistics
-
show ip sockets through show sockets
-
show tcp through start-forwarding agent
-
threshold metric through track timer
-
Index
-
Feedback
Contents
mls ip install-threshold through platform trace runtime process forwarding-manager module wccp
- mls ip install-threshold
- mls ip reflexive ndr-entry tcam
- object (tracking)
- platform trace runtime process forwarding-manager module wccp
mls ip install-threshold
To install the configured ACL thresholds, use the mls ip install-threshold command in global configuration mode.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
The mls ip install-threshold command is active only when you enable the mls ip reflexive ndr-entry tcam command.
mls ip reflexive ndr-entry tcam
To enable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR, use the mls ip reflexive ndr-entry tcam command in global configuration mode. To disable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR, use the no form of this command.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.
When you enter the mls ip reflexive ndr-entry tcamcommand, the reflexive ACL dynamic entries are installed in TCAM instead of in NetFlow.
Examples
This example shows how to enable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR:
Router(config)# mls ip reflexive ndr-entry tcamThis example shows how to disable the shortcuts in TCAM for the reflexive TCP/UDP entries when installed by the NDR:
Router(config)# no mls ip reflexive ndr-entry tcamobject (tracking)
To specify an object for a tracked list, use the object command in tracking configuration mode. To remove the object from the tracked list, use the no form of this command.
object object-number [not] [ weight weight-number ]
no object object-number [not] [ weight weight-number ]
Syntax Description
Command History
Release
Modification
12.3(8)T
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
12.2SX
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
15.1(3)T
This command was modified. The valid range of the object-number argument increased to 1000.
15.1(1)S
This command was modified. The valid range for the object-number argument increased to 1000.
12.2(50)SY
This command was modified. The valid range for the object-number argument increased to 1000.
Usage Guidelines
As of Cisco IOS Release 15.1(3)T, 15.1(1)S and 12.2(50)SY, a maximum of 1000 objects can be tracked. Although 1000 tracked objects can be configured, each tracked object uses CPU resources. The amount of available CPU resources on a router is dependent upon variables such as traffic load and how other protocols are configured and run. The ability to use 1000 tracked objects is dependent upon the available CPU. Testing should be conducted on site to ensure that the service works under the specific site traffic conditions.
Examples
The following example shows two serial interfaces (objects) that are in tracked list 100. The Boolean “not” negates the state of object 2, resulting in the tracked list regarding object 2 as down when it is up.
Router(config)# track 1 interface serial2/0 line-protocol Router(config)# track 2 interface serial2/1 line-protocol Router(config-track)# exit Router(config)# track 100 list boolean and Router(config-track)# object 1 Router(config-track)# object 2 notRelated Commands
Command
Description
show track
Displays tracking information.
threshold weight
Specifies a threshold weight for a tracked list.
track list threshold percentage
Tracks a list of objects as to the up and down object states using a threshold percentage.
track list threshold weight
Tracks a list of objects as to the up and down object states using a threshold weight.
platform trace runtime process forwarding-manager module wccp
To enable Forwarding Manager Route Processor and Embedded-Service-Processor trace messages for the Web Cache Communication Protocol (WCCP) process, use the platform trace runtime process forwarding-manager module wccp command in global configuration mode. To disable debug messages, use the no form of this command.
platform trace runtime slot slot bay bay process forwarding-manager module wccp level level
no platform trace runtime slot slot bay bay process forwarding-manager module wccp
Syntax Description
slot
Shared Port Adapter (SPA) Interprocessor, Embedded Service Processor or Route Processor slot.
Valid options are:
- F0 --Embedded Service Processor slot 0
- R0 --Route Processor slot 0
- F1 --Embedded Service Processor slot 1
- R1 --Route Processor slot 1
bay
Chassis bay to configure.
Valid options are:
- 0
- 1
level level
Selects the trace level. The trace level determines how much information about a module should be stored in the trace buffer or file.
Valid options are:
- debug --Provides debug-level output.
- emergency --Provides information about an issue that makes the system unusable.
- error --Provides information about a system error.
- info --Informational purposes only.
- noise --All possible trace messages for the module are logged. The noise level is always equal to the highest possible tracing level.
- notice --Provides information regarding a significant issue, but the router is still working normally.
- verbose --All possible tracing messages are sent.
- warning --Provides information about a system warning.
Command Default
The default tracing level for every module on the Cisco ASR 1000 Series Routers is notice.
Usage Guidelines
Trace level settings are leveled: every setting will contain all messages from the lower setting plus the messages from its own setting. For instance, setting the trace level to 3 (error) ensures that the trace file contains all output for the 0 (emergencies), 1 (alerts), 2 (critical), and 3 (error) settings. Setting the trace level to 4 (warning) ensures that all trace output for the specific module is included in that trace file.
All trace levels are not user-configurable. Specifically, the alert, critical, and notice tracing levels cannot be set by users. If you wish to trace these messages, set the trace level to a higher level that will collect these messages.
When setting trace levels, it is also important to remember that the setting is not done in a configuration mode, so trace level settings are returned to their defaults after every router reload.
Caution
Setting tracing of a module to the debug level or higher can have a negative performance impact. Setting tracing to the debug level or higher should be done with discretion.
Caution
Setting a large number of modules to high tracing levels can severely degrade performance. If a high level of tracing is needed in a specific context, it is almost always preferable to set a single module on a higher tracing level rather than setting multiple modules to high tracing levels.
