-
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.4
-
Quality of Service Overview
- Part 1: Classification
- Part 2: Congestion Management
- Part 3: Congestion Avoidance
-
Part 4: Policing and Shaping
-
Policing and Shaping Overview
-
Configuring Traffic Policing
-
Configuring Traffic Policing
-
Traffic Policing
-
Two-Rate Policer
-
Policer Enhancement---Multiple Actions
-
Percentage-Based Policing and Shaping
-
Modular QoS CLI (MQC) Three-Level Hierarchical Policer
-
ATM Policing by Service Category for SVC/SoftPVC
-
Modular QoS CLI (MQC) Unconditional Packet Discard
-
Control Plane Policing
-
- Regulating Packet Flow
-
- Part 5: Signalling
- Part 6: Link Efficiency Mechanisms
- Part 7: Quality of Service Solutions
- Part 8: Modular Quality of Service Command-Line Interface
- Part 9: Security Device Manager
- Part 10: AutoQoS
-
Table Of Contents
Adding Application Recognition Modules
Prerequisites for Adding Application Recognition Modules
Information About Adding Application Recognition Modules
How to Add Application Recognition Modules
Verifying the Downloaded PDLMs
Configuration Examples for Adding Application Recognition Modules
Verifying the Downloaded PDLMs: Example
Feature Information for Adding Application Recognition Modules
Adding Application Recognition Modules
First Published: April 4, 2006Last Updated: April 4, 2006Adding application recognition modules (also known as Packet Description Language Modules [PDLMs]) is an optional process. However, adding PDLMs extends the functionality of Network-Based Application Recognition (NBAR) by enabling NBAR to recognize additional protocols on your network.
This module contains concepts and tasks for adding application recognition modules (or PDLMs) to your network.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Adding Application Recognition Modules" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Adding Application Recognition Modules
•
•
•
•
Prerequisites for Adding Application Recognition Modules
Before adding application recognition modules (or PDLMs), read the information in the "Classifying Network Traffic Using NBAR" module.
Information About Adding Application Recognition Modules
Before adding application recognition modules (or PDLMs), you should understand the following concepts:
PDLM Functionality
A PDLM is a separate file available on Cisco.com. A PDLM is used to add support for a protocol that is currently not available as part of the Cisco IOS software.
A PDLM extends the list of protocols that NBAR can recognize. PDLMs also allow NBAR to recognize new protocols without requiring you to install a new Cisco IOS image or reconfigure your router.
New PDLMs are released by Cisco only and can be loaded from flash memory. Contact your local Cisco representative to request additions or changes to the set of protocols classified by NBAR.
To view a list of currently available PDLMs, go to the following URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/pdlm
PDLM Versioning
A PDLM adds new protocols to the list of protocols that NBAR supports. Before you download a new PDLM, you need to be aware of the following concepts.
Native and Nonnative PDLMs
A native PDLM is a PDLM that is embedded within the Cisco IOS software. You receive it automatically along with the Cisco IOS software.
A nonnative PDLM is not embedded within the Cisco IOS software. You can download it individually from Cisco.com.
Separate Version Numbers
There are separate version numbers associated with the NBAR software and the Cisco IOS software. These version numbers are used together to maintain the PDLM version.
•
•
Note
Internal Module Names
Both the native and nonnative PDLMs contain internal module names. These internal module names are unique and independent. They are used to indicate the protocol that the PDLM module represents (for example, BitTorrent or DirectConnect), and they are used to control the module version number (for example, module version 3).
Required Conditions
In order for a PDLM (either native or nonnative) to be downloaded or overridden, both of the following conditions much be met:
•
For example, if a PDLM called BitTorrent.pdlm (with the internal module name "bittorrent") is currently at version 3, the resident PDLM (either native or nonnative) with the same internal module name ("bittorrent) is overridden as long as the module version is either 1 or 2.
•
Note
How to Add Application Recognition Modules
This section contains the following tasks:
•
•
Downloading a PDLM
A PDLM is used to add support for a protocol that is currently not available as part of the Cisco IOS software. A PDLM extends the functionality of NBAR by enabling NBAR to recognize additional protocols on the network.
To download (install) a PDLM, perform the following steps.
PDLM Readme Files
Each PDLM has specific Cisco IOS release requirements and specific restrictions that you need to consider before you download a PDLM. These requirements and restrictions, and other helpful information for installing a particular PDLM, are described in a series of PDLM readme files.
To view a list of currently available PDLMs, or to view the readme files for each PDLM, go to the following URL (Cisco login required):
http://www.cisco.com/pcgi-bin/tablebuild.pl/pdlm
Note
Prerequisites
Protocols introduced when you download a PDLM are commonly added to subsequent Cisco IOS releases. Support for the protocol that you would like to add via a PDLM may already be in your Cisco IOS release. Therefore, before you load a PDLM, review the list of NBAR protocols currently supported by the Cisco IOS release that you are using. To check the list of NBAR protocols supported in your Cisco IOS release, enter the match protocol ? command and view the options that appear. The options correspond to the NBAR supported protocols.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Verifying the Downloaded PDLMs
After you download the PDLM, you may want to verify that the PDLM is now on your network. You may also want to check if there are earlier versions of the PDLM already on your network.
To display information about the downloaded PDLMs, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuration Examples for Adding Application Recognition Modules
This section provides the following configuration examples:
•
Downloading a PDLM: Example
In the following example. the Citrix PDLM is downloaded to the router from flash memory:
Router> enable
Router# configure terminal
Router(config)# ip nbar pdlm flash://citrix.pdlm
Router(config)# end
Verifying the Downloaded PDLMs: Example
You can use the output of the show ip nbar pdlm command and the show ip nbar version command to verify information about the downloaded PDLMs on your network.
Sample show ip nbar pdlm Command Output
In this example of the show ip nbar pdlm command, the Citrix PDLM has been loaded from flash memory:
Router# show ip nbar pdlmThe following PDLMs have been loaded:flash://citrix.pdlmSample show ip nbar version Command Output
The following is sample output from the show ip nbar version command:
Router# show ip nbar versionNBAR software version: 31 base Mv: 22 ftp Mv: 23 http Mv: 7, Nv: 3; slot1:http_vers.pdlm4 static-port Mv: 65 tftp Mv: 16 exchange Mv: 17 vdolive Mv: 18 sqlnet Mv: 19 rcmd Mv: 110 netshow Mv: 111 sunrpc Mv: 212 streamwork Mv: 113 citrix Mv: 514 napster Mv: 215 fasttrack Mv: 216 gnutella Mv: 117 kazaa Mv: 6, Nv: 3; slot1:kazaa2_vers.pdlm18 custom-protocols Mv: 119 rtsp Mv: 120 rtp Mv: 221 mgcp Mv: 122 skinny Mv: 123 h323 Mv: 124 sip Mv: 125 rtcp Mv: 1Table 1 describes the fields shown in the display.
Where to Go Next
To classify network traffic on the basis of a custom protocol, see the "Creating a Custom Protocol" module.
Additional References
The following sections provide references related to adding application recognition modules.
Related Documents
QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples
Concepts and information about NBAR
Information about enabling Protocol Discovery
Configuring NBAR using the MQC
Creating a custom protocol
"Creating a Custom Protocol" module
Technical Assistance
Feature Information for Adding Application Recognition Modules
Table 2 lists the release history for this feature.
For information on a feature in this technology that is not documented here, see the "Classifying Network Traffic Using NBAR Features Roadmap" module.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 2 Feature Information for Adding Application Recognition Modules
QoS: DirectConnect PDLM
12.4(4)T
Provides support for the DirectConnect protocol and PDLM. The DirectConnect protocol can now be recognized when using the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC) to classify traffic.
The following sections provide information about the QoS: DirectConnect PDLM feature:
•
NBAR - BitTorrent PDLM
12.4(2)T
Provides support for the BitTorrent PDLM and protocol. The BitTorrent protocol can now be recognized when using the MQC to classify traffic.
The following sections provide information about the NBAR - BitTorrent PDLM feature:
•
NBAR PDLM Versioning
12.3(4)T
Enables the ability to verify the Cisco IOS and NBAR PDLM versions for ensuring software compatibility.
The following sections provide information about the NBAR PDLM Versioning feature:
•
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0804R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
