|
|
Table Of Contents
Network-Based Application Recognition and Distributed Network-Based Application Recognition
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Attaching a Traffic Policy to an Interface
Monitoring and Maintaining NBAR
Configuring a Traffic Policy with NBAR
show ip nbar protocol-discovery
Network-Based Application Recognition and Distributed Network-Based Application Recognition
Feature History
12.0(5)XE2
The NBAR feature was introduced. The first implementation of the NBAR feature was available on Cisco 7100 and Cisco 7200 series routers.
12.1(1)E
Subport classification of HTTP traffic by host name for NBAR was introduced. The variable-field-name value options were also added to the match protocol command.
12.1(2)E
Support for the Citrix, Novadigm, and Printer protocols for NBAR was introduced.
12.1(5)T
This feature was introduced for the Cisco IOS Release 12.1 T train. NBAR became available on Cisco 2600 and 3600 series routers.
12.1(6)E
The dNBAR feature, which introduced NBAR functionality on the Cisco 7500 series router with a VIP and the Catalyst 6000 family switch with a FlexWAN module, was introduced.
12.1(10)EC
NBAR was introduced for Cisco 7100 uBR and Cisco 7200 uBR routers.
12.1(11b)E
The match protocol rtp command was introduced on the Cisco IOS Release 12.1 E train.
12.1(12c)E
The match protocol gnutella and match protocol fasttrack commands were added because Gnutella and FastTrack became available as NBAR-supported protocols.
12.1(13)E
NBAR was released on the Catalyst 6000 family switch without a FlexWAN module.
12.2(2)T
This feature was introduced on Cisco 1700 series routers.
12.2(4)T3
The dNBAR feature introduced NBAR functionality on the Cisco IOS Release 12.2 T train. This feature was introduced for the Cisco 7500 series router with a VIP only.
12.2(8)T
The match protocol rtp command was introduced, allowing NBAR to classify Real-Time Transport Protocol (RTP) traffic.
The Cisco 3700 also became available. The initial release of the Cisco 3700 supported NBAR.
12.2(14)S
NBAR and dNBAR were introduced in Cisco IOS Release 12.2 S. The 12.2 S version of NBAR includes everything available on the 12.1 E and 12.2 T implementations of NBAR with the exception of platform support for platforms not supported by 12.2 S.
12.3(4)T
NBAR PDLM Versioning was introduced. This feature introduced versioning of PDLM protocols and the show ip nbar version command. See the "IP NBAR PDLM Module Versioning" section for additional information regarding this feature.
The NBAR User-Defined Custom Application Classification feature was introduced. See the "Classification of Custom Applications" section for additional information on the enhancements to the custom protocol that were introduced as part of this feature.
The NBAR Extended Inspection for HTTP Traffic feature was introduced. This feature allows NBAR to scan TCP ports that are not well-known and identify HTTP traffic traversing these ports.
12.3(2)XE
NBAR was introduced on Cisco 800 series routers.
To see if NBAR is supported in other platforms, see the "Supported Platforms" section of this document.12.3(7)T
Restrictions on the number of bytes of payload that could be inspected by NBAR were removed. NBAR can now inspect the full packet payload.
12.3(8)T
NBAR was introduced on Cisco 800 series routers running Cisco IOS Release 12.3 T.
This document provides information for the Network-Based Application Recognition (NBAR) and the Distributed Network-Based Application Recognition (dNBAR) features. This document contains all of the updates made to the NBAR and dNBAR features.
Before proceeding, it is important to note that the dNBAR feature, which introduced NBAR on the Cisco 7500 with a Versatile Interface Processor (VIP) and the Catalyst 6000 family switch with a FlexWAN module, is identical in implementation to NBAR. Therefore, unless otherwise noted, the term NBAR is used throughout this document to describe both the NBAR and dNBAR feature. The term dNBAR is used only when appropriate.
This document includes information on the benefits of NBAR, supported platforms, restrictions, definitions, and new and revised command syntax.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
•
•
Feature Overview
The purpose of IP Quality of Service (QoS) is to provide appropriate network resources (bandwidth, delay, jitter, and packet loss) to applications. QoS maximizes the return on investments on network infrastructure by ensuring that mission critical applications get the required performance and noncritical applications do not hamper the performance of critical applications.
IP QoS can be deployed by defining classes or categories of applications. These classes are defined by using various classification techniques available in Cisco IOS software. After these classes are defined and attached to an interface, the desired QoS features, such as Marking, Congestion Management, Congestion Avoidance, Link Efficiency mechanisms, or Policing and Shaping can then be applied to the classified traffic to provide the appropriate network resources amongst the defined classes.
Classification, therefore, is an important first-step in configuring QoS in a network infrastructure.
NBAR is a classification engine that recognizes a wide variety of applications, including web-based and other difficult-to-classify protocols that utilize dynamic TCP/UDP port assignments. When an application is recognized and classified by NBAR, a network can invoke services for that specific application. NBAR ensures that network bandwidth is used efficiently by classifying packets and then applying Quality of Service (QoS) to the classified traffic. Some examples of class-based QoS features that can be used on traffic after the traffic is classified by NBAR include:
•
•
•
•
•
Note
Note
For information on the class-based features that can be used to forward NBAR-classified traffic, see the individual feature modules for the particular class-based feature as well as the Cisco IOS Quality of Service Solutions Guide.
Many of the non-NBAR classification options for QoS are documented in the "Modular Quality of Service Command-Line Interface" section of the Cisco IOS Quality of Service Solutions Guide. These commands are configured using the match command in class map configuration mode.NBAR introduces several new classification features that identify applications and protocols from Layer 4 through Layer 7:
•
•
•
•
NBAR can classify static port protocols. Although access control lists (ACLs) can also be used for this purpose, NBAR is easier to configure and can provide classification statistics that are not available when using ACLs.
NBAR includes a Protocol Discovery feature that provides an easy way to discover application protocols that are transversing an interface. The Protocol Discovery feature discovers any protocol traffic supported by NBAR. Protocol Discovery maintains the following per-protocol statistics for enabled interfaces: total number of input and output packets and bytes, and input and output bit rates. The Protocol Discovery feature captures key statistics associated with each protocol in a network that can be used to define traffic classes and QoS policies for each traffic class.
Benefits
Ability to Identify and Classify Network Traffic by Protocol
Identifying and classifying network traffic is an important first step in implementing QoS. A network administrator can more effectively implement QoS in a networking environment after identifying the amount and the variety of applications and protocols running on a network.
NBAR gives network administrators the ability to see the variety of protocols and the amount of traffic generated by each protocol. After gathering this information, NBAR allows users to implement classes of traffic. These classes of traffic can then be used to provide different levels of service for network traffic, therefore allowing better network management by providing the right level of network resources for network traffic.
NBAR Application Notes
The following section provides information on several topics that could be useful to individuals configuring NBAR in their networks. The following topics are covered in this section:
•
•
•
•
•
•
•
•
Catalyst 6000 Family Switches without FlexWAN Modules Application Notes
When NBAR is enabled on a Catalyst 6000 without a FlexWAN module interface, all traffic flows entering or leaving the NBAR-enabled interface will be processed in software on the Multilayer Swich Feature Card 2 (MSFC2).
The following other restrictions should also be noted when running NBAR:
•
•
The following table provides configuration results when NBAR is added to an interface. The results vary depending on the current configuration of the policy map on the interface.
Table 1 NBAR Behavior Descriptions
Packet Description Language Module
An external Packet Description Language Module (PDLM) can be loaded at run time to extend the NBAR list of recognized protocols. PDLMs can also be used to enhance an existing protocol recognition capability. PDLMs allow NBAR to recognize new protocols without requiring a new Cisco IOS image or a router reload.
New PDLMs will only be released by Cisco and can be loaded from Flash memory. Please 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 or to download a PDLM, go to the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/pdlm
Classification of HTTP by URL, Host, or MIME
NBAR can classify application traffic by looking beyond the TCP/UDP port numbers of a packet. This is subport classification. NBAR looks into the TCP/UDP payload itself and classifies packets on content within the payload such as transaction identifier, message type, or other similar data.
Classification of HTTP by URL, host, or Multipurpose Internet Mail Extension (MIME) type is an example of subport classification. NBAR classifies HTTP traffic by text within the URL or host fields of a request using regular expression matching. HTTP URL matching in NBAR supports most HTTP request methods such as GET, PUT, HEAD, POST, DELETE, and TRACE. NBAR uses the UNIX filename specification as the basis for the URL or host specification format. The NBAR engine then converts the specified match string into a regular expression.
NBAR recognizes HTTP packets containing the URL and classifies all packets that are sent to the source of the HTTP request. Figure 1 illustrates a network topology with NBAR in which Router Y is the NBAR-enabled router.
Figure 1 Network Topology with NBAR
When specifying a URL for classification, include only the portion of the URL following the www.hostname.domain in the match statement. For example, for the URL www.cisco.com/latest/whatsnew.html, include only /latest/whatsnew.html.
Host specification is identical to URL specification. NBAR performs a regular expression match on the host field contents inside an HTTP packet and classifies all packets from that host. For example, for the URL www.cisco.com/latest/whatsnew.html, include only www.cisco.com.
For MIME type matching, the MIME type can contain any user-specified text string. A list of the Internet Assigned Numbers Authority (IANA)-supported MIME types can be found at:
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/media-types
In MIME type matching, NBAR classifies the packet containing the MIME type and all subsequent packets, which are sent to the source of the HTTP request.
NBAR supports URL and host classification in the presence of persistent HTTP. NBAR does not classify packets that are part of a pipelined request. With pipelined requests, multiple requests are pipelined to the server before previous requests are serviced. Pipelined requests are a less commonly used type of persistent HTTP request.
In Cisco IOS Release 12.3(4)T, the NBAR Extended Inspection for HTTP Traffic feature was introduced. This feature allows NBAR to scan TCP ports that are not well-known and identify HTTP traffic traversing these ports. HTTP traffic classifications are no longer restrained to the well-known and defined TCP ports.
Classification of Citrix ICA Traffic by Application Name
NBAR can classify Citrix Independent Computing Architecture (ICA) traffic and perform subport classification of Citrix traffic based on Citrix published applications. NBAR can monitor Citrix ICA client requests for a published application destined to a Citrix ICA Master browser. After the client requests to the published application, the Citrix ICA Master browser directs the client to the server with the most available memory. The Citrix ICA client then connects to this Citrix ICA server for the application.
NBAR statefully tracks Citrix ICA server client messages and classifies requests for given Citrix application names and traffic. A Citrix application is named when published on a Citrix ICA server. NBAR performs a regular expression match using a user-specified application name string on the contents of the Citrix ICA control packets carrying the published application name. Therefore, users need to specify a regular expression that will result in a match for the published application name if they want to match a specified application. See the match protocol citrix command in the " Command Reference" section for additional information.
Citrix ICA clients can be configured in various modes. NBAR cannot distinguish among Citrix applications in all modes of operation. Therefore, network administrators might need to collaborate with Citrix administrators to ensure that NBAR properly classifies Citrix traffic.
A Citrix administrator can configure Citrix to publish Citrix applications individually or as the entire desktop. In the Published Desktop mode of operation, all applications within the published desktop of a client use the same TCP session. Therefore, differentiation among applications is impossible, and NBAR can only be used to classify Citrix applications as aggregates (by looking at port 1494).
The Published Application mode for Citrix ICA clients is recommended when you use NBAR. In Published Application mode, a Citrix administrator can configure a Citrix client in either seamless or non-seamless (windows) modes of operation. In non-seamless mode, each Citrix application uses a separate TCP connection, and NBAR can be used to provide interapplication differentiation based on the name of the published application.
Seamless mode clients can operate in one of two submodes: session sharing or non-session sharing. In seamless session sharing mode, all clients share the same TCP connection, and NBAR cannot differentiate among applications. Seamless sharing mode is enabled by default on some software releases.
In seamless non-session sharing mode, each application for each particular client uses a separate TCP connection. NBAR can provide interapplication differentiation in seamless non-session sharing mode.
Session sharing can be turned off using the following steps:
Step 1
Step 2
[HKLM]\SYSTEM\CurrentControlSet\Control\Citrix\WFSHELL\TWI
Value name: "SeamlessFlags", type DWORD, possible value` 0 or 1Setting this registry value to 1 overrides session sharing. Note that this flag is SERVER GLOBAL.
Note
RTP Payload Type Classification
RTP is a packet format for multimedia data streams. It can be used for media-on-demand as well as interactive services such as Internet telephony. RTP consists of a data and a control part. The control part is called Real-time Transport Control Protocol (RTCP). It is important to note that the NBAR RTP Payload Type Classification feature does not identify RTCP packets, and that RTCP packets run on odd numbered ports while RTP packets run on even-numbered ports.
The data part of RTP is a thin protocol providing support for applications with real-time properties such as continuous media (such as audio and video), which includes timing reconstruction, loss detection, and security and content identification. RTP is discussed in RFC 1889 and RFC 1890.
The RTP payload type is the data transported by RTP in a packet, for example audio samples or compressed video data.
NBAR RTP Payload Type Classification not only allows one to statefully identify real-time audio and video traffic, but it also can differentiate on the basis of audio and video CODECs to provide more granular Quality of Service. The RTP Payload Type Classification feature, therefore, looks deep into the RTP header to classify RTP packets.
NBAR RTP Payload Type Classification was first introduced in Cisco IOS Release 12.2(8)T and is also available in Cisco IOS Release 12.1(11b)E.
Classification of Custom Applications
The custom protocol supports static port-based protocols and applications that are not currently supported in NBAR. This functionality allows mapping of static TCP and UDP port numbers to custom protocol within NBAR. The custom protocol is also available as a PDLM if your version of Cisco IOS supports NBAR but not the custom protocol.
The initial custom NBAR application had the following features that were later enhanced in Cisco IOS Release 12.3(4)T:
•
•
In Cisco IOS Release 12.3(4)T, the User-Defined Custom Application Classification feature was introduced and the following enhancements to custom protocols were introduced:
•
•
•
•
For additional information on the enhancements to the custom protocol that were introduced in Cisco IOS Release 12.3(4)T, see the ip nbar custom command reference in this document.
Pre-12.3(4)T Custom Application Example
In the following example, a gaming application that runs on TCP port 8877 needs to be classified using NBAR. You can use custom-01 to map TCP port 8877 by entering the following command:
Router(config)#ip nbar port-map custom-01 tcp 8877
It is important to note that this configuration is also supported on Cisco IOS releases released after Release 12.3(4)T but is required on all prior releases.12.3(4)T and Later Custom Application Examples
In the following example, the custom protocol app_sales1 will identify TCP packets with a source port of 4567 and contain the term "SALES" in the fifth byte of the payload:ip nbar custom app_sales1 5 ascii SALES source tcp 4567
In the following example, the custom protocol virus_home will identify UDP packets with a destination port of 3000 and contain "0x56" in the seventh byte of the payload:ip nbar custom virus_home 7 hex 0x56 dest udp 3000
In the following example, custom protocol media_new will identify TCP packets with a destination or source port of 4500 and that have a value of 90 at the sixth byte of the payload:ip nbar custom media_new 6 decimal 90 tcp 4500
In the following example, custom protocol msn1 will look for TCP packets with a destination or source port of 6700:ip nbar custom msn1 tcp 6700
In the following example, custom protocol mail_x will look for UDP packets with a destination port of 8202:ip nbar custom mail_x destination udp 8202
In the following example, custom protocol mail_y will look for UDP packets with destination ports between 3000 and 4000 including 3000 and 4000 as well as port 5500:ip nbar custom mail_y destination udp range 3000 4000 5500Classification of Peer-to-Peer File-Sharing Applications
Gnutella and FastTrack are peer-to-peer file-sharing protocols that became classifiable using NBAR in Cisco IOS Release 12.1(12c)E.
The match protocol gnutella file-transfer "regular-expression" and match protocol fasttrack file-transfer "regular-expression" commands are used to enable Gnutella and FastTrack classification in a traffic class. The regular-expression variable can be expressed as "*" to indicate that all FastTrack or Gnutella traffic be classified by a traffic class.
In the following example, all FastTrack traffic is classified into class map nbar:
class-map match-all nbar match protocol fasttrack file-transfer "*"Similarly, all Gnutella traffic is classified into class map nbar in this example:
class-map match-all nbar match protocol gnutella file-transfer "*"Wildcard characters in a regular expression can also be used to identify specified Gnutella and FastTrack traffic. These regular expression matches can be used to match based on a filename extension or on a particular string in a filename.
In the following example, all Gnutella files that have the ".mpeg" extension will be classified into class map nbar.
class-map match-all nbar match protocol gnutella file-transfer "*.mpeg"In the following example, only Gnutella traffic that contains the characters "cisco" is classified:
class-map match-all nbar match protocol gnutella file-transfer "*cisco*"The same examples can be used for FastTrack traffic:
class-map match-all nbar match protocol fasttrack file-transfer "*.mpeg"or
class-map match-all nbar match protocol fasttrack file-transfer "*cisco*"Applications that use FastTrack include KaZaA, Grokster, and Morpheus (although newer versions of Morpheus use Gnutella).
Some of the applications that use Gnutella include:
•
•
•
•
•
•
•
•
•
•
•
•
•
IP NBAR PDLM Module Versioning
A Packet Description Language Module (PDLM) is used to add a new protocol to the list of supported NBAR protocols. Before downloading PDLMs, users should understand some of the interdependencies between the versioning of NBAR in the Cisco IOS code and the PDLM file itself. The following definitions help define some of the aspects of NBAR and PDLM versioning and the interdependencies required between the two before a new protocol can be supported in NBAR via a PDLM download.
The following version numbers are kept by the Cisco IOS software:
•
•
The following version numbers is kept by the PDLM:
•
See the show ip nbar version command reference in this document for additional information on IP NBAR PDLM Module Versioning.
Supported Protocols
NBAR is capable of classifying the following three types of protocols:
•
•
•
Table 2 Non-UDP and Non-TCP Protocols
EGP
IP
8
Exterior Gateway Protocol
egp
12.0(5)XE2
12.1(1)E
12.1(5)TEIGRP
IP
88
Enhanced Interior Gateway Routing Protocol
eigrp
12.0(5)XE2
12.1(1)E
12.1(5)TGRE
IP
47
Generic Routing Encapsulation
gre
12.0(5)XE2
12.1(1)E
12.1(5)TICMP
IP
1
Internet Control Message Protocol
icmp
12.0(5)XE2
12.1(1)E
12.1(5)TIPINIP
IP
4
IP in IP
ipinip
12.0(5)XE2
12.1(1)E
12.1(5)TIPSec
IP
50, 51
IP Encapsulating Security Payload/Authentication Header
ipsec
12.0(5)XE2
12.1(1)E
12.1(5)T
1 Indicates the Cisco IOS maintenance release that first supported the protocol. This table is updated when a protocol is added to a new Cisco IOS release train.
Table 3 TCP and UDP Static Port Protocols
BGP
TCP/UDP
179
Border Gateway Protocol
bgp
12.0(5)XE2
12.1(1)E
12.1(5)TCU-SeeMe
TCP/UDP
7648, 7649
Desktop videoconferencing
cuseeme
12.0(5)XE2
12.1(1)E
12.1(5)TCU-SeeMe
UDP
24032
Desktop video conferencing
cuseeme
12.0(5)XE2
12.1(1)E
12.1(5)TDHCP/
BOOTPUDP
67, 68
Dynamic Host Configuration Protocol/ Bootstrap Protocol
dhcp
12.0(5)XE2
12.1(1)E
12.1(5)TDNS
TCP/UDP
53
Domain Name System
dns
12.0(5)XE2
12.1(1)E
12.1(5)TFinger
TCP
79
Finger user information protocol
finger
12.0(5)XE2
12.1(1)E
12.1(5)TGopher
TCP/UDP
70
Internet Gopher Protocol
gopher
12.0(5)XE2
12.1(1)E
12.1(5)THTTP
TCP
802
Hypertext Transfer Protocol
http
12.0(5)XE2
12.1(1)E
12.1(5)THTTPS
TCP
443
Secured HTTP
secure-http
12.0(5)XE2
12.1(1)E
12.1(5)TIMAP
TCP/UDP
143, 220
Internet Message Access Protocol
imap
12.0(5)XE2
12.1(1)E
12.1(5)TIRC
TCP/UDP
194
Internet Relay Chat
irc
12.0(5)XE2
12.1(1)E
12.1(5)TKerberos
TCP/UDP
88, 749
Kerberos Network Authentication Service
kerberos
12.0(5)XE2
12.1(1)E
12.1(5)TL2TP
UDP
1701
L2F/L2TP tunnel
l2tp
12.0(5)XE2
12.1(1)E
12.1(5)TLDAP
TCP/UDP
389
Lightweight Directory Access Protocol
ldap
12.0(5)XE2
12.1(1)E
12.1(5)TMS-PPTP
TCP
1723
Microsoft Point-to-Point Tunneling Protocol for VPN
pptp
12.0(5)XE2
12.1(1)E
12.1(5)TMS-
SQLServerTCP
1433
Microsoft SQL Server Desktop Videoconferencing
sqlserver
12.0(5)XE2
12.1(1)E
12.1(5)TNetBIOS
TCP
137, 139
NetBIOS over IP (MS Windows)
netbios
12.0(5)XE2
12.1(1)E
12.1(5)TNetBIOS
UDP
137, 138
NetBIOS over IP (MS Windows)
netbios
12.0(5)XE2
12.1(1)E
12.1(5)TNFS
TCP/UDP
2049
Network File System
nfs
12.0(5)XE2
12.1(1)E
12.1(5)TNNTP
TCP/UDP
119
Network News Transfer Protocol
nntp
12.0(5)XE2
12.1(1)E
12.1(5)TNotes
TCP/UDP
1352
Lotus Notes
notes
12.0(5)XE2
12.1(1)E
12.1(5)TNovadigm
TCP/UDP
3460-3465
Novadigm Enterprise Desktop Manager (EDM)
novadigm
12.1(2)E
12.1(5)TNTP
TCP/UDP
123
Network Time Protocol
ntp
12.0(5)XE2
12.1(1)E
12.1(5)TPCAnywhere
TCP
5631, 65301
Symantec PCAnywhere
pcanywhere
12.0(5)XE2
12.1(1)E
12.1(5)TPCAnywhere
UDP
22, 5632
Symantec PCAnywhere
pcanywhere
12.0(5)XE2
12.1(1)E
12.1(5)TPOP3
TCP/UDP
110
Post Office Protocol
pop3
12.0(5)XE2
12.1(1)E
12.1(5)TPrinter
TCP/UDP
515
Printer
printer
12.1(2)E
12.1(5)TRIP
UDP
520
Routing Information Protocol
rip
12.0(5)XE2
12.1(1)E
12.1(5)TRSVP
UDP
1698, 1699
Resource Reservation Protocol
rsvp
12.0(5)XE2
12.1(1)E
12.1(5)TSFTP
TCP
990
Secure FTP
secure-ftp
12.0(5)XE2
12.1(1)E
12.1(5)TSHTTP
TCP
443
Secure HTTP
secure-http
12.0(5)XE2
12.1(1)E
12.1(5)TSIMAP
TCP/UDP
585, 993
Secure IMAP
secure-imap
12.0(5)XE2
12.1(1)E
12.1(5)TSIRC
TCP/UDP
994
Secure IRC
secure-irc
12.0(5)XE2
12.1(1)E
12.1(5)TSLDAP
TCP/UDP
636
Secure LDAP
secure-ldap
12.0(5)XE2
12.1(1)E
12.1(5)TSMTP
TCP
25
Simple Mail Transfer Protocol
smtp
12.0(5)XE2
12.1(1)E
12.1(5)TSNMP
TCP/UDP
161, 162
Simple Network Management Protocol
snmp
12.0(5)XE2
12.1(1)E
12.1(5)TSNNTP
TCP/UDP
563
Secure NNTP
secure-nntp
12.0(5)XE2
12.1(1)E
12.1(5)TSOCKS
TCP
1080
Firewall security protocol
socks
12.0(5)XE2
12.1(1)E
12.1(5)TSPOP3
TCP/UDP
995
Secure POP3
secure-pop3
12.0(5)XE2
12.1(1)E
12.1(5)TSSH
TCP
22
Secured Shell
ssh
12.0(5)XE2
12.1(1)E
12.1(5)TSTELNET
TCP
992
Secure Telnet
secure-telnet
12.0(5)XE2
12.1(1)E
12.1(5)TSyslog
UDP
514
System Logging Utility
syslog
12.0(5)XE2
12.1(1)E
12.1(5)TTelnet
TCP
23
Telnet Protocol
telnet
12.0(5)XE2
12.1(1)E
12.1(5)TX Windows
TCP
6000-6003
X11, X Windows
xwindows
12.0(5)XE2
12.1(1)E
12.1(5)T
1 Indicates the Cisco IOS maintenance release that first supported the protocol. This table is updated when a protocol is added to a new Cisco IOS release train.
2 In Release 12.3(4)T, the NBAR Extended Inspection for HTTP Traffic feature was introduced. This feature allows NBAR to scan TCP ports that are not well-known and identify HTTP traffic traversing these ports.
Table 4 TCP and UDP Stateful Protocols
Citrix ICA
TCP/UDP
Citrix ICA traffic by application name
citrix
citrix app12.1(2)E
12.1(5)TFTP
TCP
File Transfer Protocol
ftp
12.0(5)XE2
12.1(1)E
12.1(5)TExchange
TCP
MS-RPC for Exchange
exchange
12.0(5)XE2
12.1(1)E
12.1(5)TFastTrack
FastTrack
For a list of common FastTrack applications, see the " Classification of Peer-to-Peer File-Sharing Applications" section of this document.
fasttrack
12.1(12c)E
Gnutella
TCP
Gnutella
For a list of common Gnutella applications, see the " Classification of Peer-to-Peer File-Sharing Applications" section of this document.
gnutella
12.1(12c)E
HTTP
TCP
HTTP with URL, MIME, or host classification
http
12.0(5)XE2
12.1(1)E
12.1(5)T
(HTTP host classification is not available on the 12.0 XE release train)Napster
TCP
Napster traffic
napster
12.1(5)T
Netshow
TCP/UDP
Microsoft Netshow
netshow
12.0(5)XE2
12.1(1)E
12.1(5)Tr-commands
TCP
rsh, rlogin, rexec
rcmd
12.0(5)XE2
12.1(1)E
12.1(5)TRealAudio
TCP/UDP
RealAudio Streaming Protocol
realaudio
12.0(5)XE2
12.1(1)E
12.1(5)TRTP
TCP/UDP
Real-Time Transport Protocol Payload Classification
rtp
12.2(8)T
SQL*NET
TCP/UDP
SQL*NET for Oracle
sqlnet
12.0(5)XE2
12.1(1)E
12.1(5)TStreamWorks
UDP
Xing Technology Stream Works audio and video
streamwork
12.0(5)XE2
12.1(1)E
12.1(5)TSunRPC
TCP/UDP
Sun Remote Procedure Call
sunrpc
12.0(5)XE2
12.1(1)E
12.1(5)TTFTP
UDP
Trivial File Transfer Protocol
tftp
12.0(5)XE2
12.1(1)E
12.1(5)TVDOLive
TCP/UDP
VDOLive Streaming Video
vdolive
12.0(5)XE2
12.1(1)E
12.1(5)T
1 Indicates the Cisco IOS maintenance release that first supported the protocol. This table is updated when a protocol is added to a new Cisco IOS release train.
Restrictions
The NBAR feature does not support the following:
•
•
•
•
•
•
•
•
•
•
NBAR is not supported on the following logical interfaces:
•
•
•
Note
However, NBAR Protocol Discovery is supported on interfaces where tunneling or encryption is used. You can enable Protocol Discovery directly on the tunnel or on the interface where encryption is performed to gather key statistics on the various applications that are traversing the interface. The input statistics also show the total number of encrypted/tunneled packets received in addition to the per-protocol breakdowns.In order to run Distributed NBAR on a Cisco 7500 series router, you must be using a processor that has 64 MB of DRAM or more. At the time of this publication, the following processors met this requirement:
•
•
•
Memory Management
NBAR uses approximately 150 bytes of DRAM for each flow that requires stateful inspection. (See Table 4 for a list of stateful protocols supported by NBAR that require stateful inspection.) When NBAR is configured, it allocates 1 MB of DRAM to support up to 5000 concurrent flows. NBAR checks to see if it needs more memory to handle additional concurrent stateful flows. If such a need is detected, NBAR expands its memory usage in increments of 200 Kb to 400 Kb.
Related Features and Technologies
•
•
•
•
•
•
•
Related Documents
•
•
•
•
•
•
Supported Platforms
To view the platforms that support NBAR and when NBAR support was introduced, check Feature Navigator.
Determining Platform Support Through Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Feature Navigator. Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image.
Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Feature Navigator home page at the following URL:
Supported Standards, MIBs, and RFCs
Standards
•
•
•
•
•
•
MIBs
The CISCO-NBAR-PROTOCOL-DISCOVERY MIB is a MIB that utilizes Cisco NBAR Protocol Discovery in SNMP. For information on the CISCO-NBAR-PROTOCOL-DISCOVERY MIB, see the Network-Based Application Recognition Management Information Base document.
To obtain lists of supported MIBs by platform and Cisco IOS Release, and to download MIB modules, go to the Cisco MIB web site on cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Prerequisites
CEF
You must enable Cisco Express Forwarding (CEF) before you configure NBAR. For more information on CEF, refer to the Cisco IOS Release 12.2 Cisco IOS Switching Services Configuration Guide.
Configuration Tasks
The NBAR feature has two components: one component monitors applications traversing a network, and the other that classifies traffic by protocol.
In order to monitor applications traversing a network, Protocol Discovery needs to be enabled.
The ability to classify traffic by protocol using NBAR and then applying QoS to the classified traffic is configured using the Modular QoS CLI.
The Modular QoS CLI is a CLI structure that allows users to create traffic policies and attach these policies to interfaces. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to classify traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.
Modular QoS CLI configuration includes the following three steps:
Step 1
Step 2
Step 3
NBAR traffic classification occurs as part of the traffic class configuration.
For additional information on the Modular Quality of Service Command-Line Interface, see the "Configuring the Modular Quality of Service Command-Line Interface" section of the Cisco IOS Quality of Service Solution Guide on Cisco.com.
See the following sections for configuration tasks for the NBAR feature. Each task in the list is identified as either optional or required:
•
•
•
•
•
Enabling Protocol Discovery
Use the ip nbar protocol-discovery command in order to enable monitoring of applications on a particular interface:
Configuring a Traffic Class
Use the class-map configuration command to define a traffic class and the match criteria that will be used to classify network traffic when attached to an interface. When using NBAR to classify traffic, the match protocol command will be entered in class map configuration mode.
Configuring a Traffic Policy
Use the policy-map configuration command to specify the QoS policies, such as Traffic Policing, Traffic Shaping, Low Latency Queueing, Class-Based Marking, Class-Based Weighted Fair Queueing or others, to apply to traffic classes defined by a traffic class. A traffic policy does not classify and forward traffic until being attached to an interface.
For additional information on policy map options in the Modular Quality of Service Command-Line Interface, see the Modular Quality of Service Command-Line Interface document on Cisco.com.
Attaching a Traffic Policy to an Interface
A traffic policy is not active until it has been attached to an interface. Use the service-policy interface configuration command to attach a traffic policy to an interface and to specify the direction in which the policy should be applied (on either packets coming into the interface or packets leaving the interface).
.
Use the no service-policy [input | output] policy-map-name command to detach a policy map from an interface.
Downloading PDLMs
To extend or enhance the list of protocols recognized by NBAR through a Cisco-provided PDLM, use the ip nbar pdlm command after downloading the PDLM.
Router(config)# ip nbar pdlm pdlm-nameSpecifies the PDLM used to extend or enhance the NBAR list of protocols.
Note
http://www.cisco.com/cgi-bin/tablebuild.pl/pdlmVerifying the Configuration
Use the show policy-map [interface [interface-spec [input | output [class class-name]]]] command to display the configuration of a policy map and its associated class maps. Forms of this command are listed in the table below.
Troubleshooting Tips
•
•
RTP is the only currently available heuristic protocol. If the error message or the error message documentation recommends an action to a heuristic protocol, take the recommended action on RTP.
Monitoring and Maintaining NBAR
NBAR can determine which protocols and applications are currently running on a network. NBAR includes the Protocol Discovery feature that provides an easy way of discovering application protocols operating on an interface so that appropriate QoS policies can be developed and applied. With Protocol Discovery, you can discover any protocol traffic supported by NBAR and obtain statistics associated with that protocol. To monitor and maintain the NBAR feature, use the following commands:
Configuration Examples
This section provides the following configuration examples:
•
Configuring a Traffic Policy with NBAR
In the following example, all SQL*Net traffic leaving fastethernet interface 0/1 is marked with the IP precedence value of 4. In the example, NBAR is used to identify SQL*Net traffic, while the treatment of SQL*Net traffic (in this case, it is forwarded with the IP precedence bit set as 4) is determined by the traffic policy configuration (the set ip precedence 4 command in policy-map class configuration mode).
Router(config)# class-map sqlnettrafficRouter(config-cmap)# match protocol sqlnetRouter(config)# policy-map sqlsetipprec1Router(config-pmap)# class sqlnettrafficRouter(config-pmap-c)# set ip precedence 4Router(config)# interface fastethernet 0/1Router(config-if)# service-policy output sqlsetipprec1Adding a PDLM
In the following example, the FastTrack PDLM, which has already been downloaded to the Flash drive, is added as an NBAR-supported protocol:
Router(config)#ip nbar pdlm flash://fasttrack.pdlmCommand Reference
This section documents new and enhanced commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
•
Note
ip nbar custom
To extend the capability of NBAR Protocol Discovery to classify and monitor additional static port applications or to allow NBAR to classify non-supported static port traffic, use the ip nbar custom global configuration command.
ip nbar custom name [offset format value] [source|destination] [tcp | udp] [range start end | port-number]
no ip nbar custom name [offset format value] [source|destination] [tcp | udp] [range start end | port-number]
Syntax Description
Defaults
If source or destination is not specified, traffic flowing in both directions is inspected if the custom protocol is enabled in NBAR.
Command Modes
Global configuration
Command History
Usage Guidelines
More than 30 custom applications can be created on the router.
NBAR can support up to 128 protocols total.
If the variable keyword is entered while configuring the custom protocol, traffic statistics for the variable will appear in some NBAR class map show outputs.
Up to 24 variable values per custom protocol can be expressed in class maps. For instance, in the following configuration, 4 variables are used and 20 more "scid" values could be used.
ip nbar custom ftdd field scid 125 variable 1 tcp range 5001 5005class-map active-craftmatch protocol ftdd scid 0x15match protocol ftdd scid 0x21class-map passive-craftmatch protocol ftdd scid 0x11match protocol ftdd scid 0x22Examples
In the following example, the custom protocol app_sales1 will identify TCP packets with a source port of 4567 and contain the term "SALES" in the fifth byte of the payload:ip nbar custom app_sales1 5 ascii SALES source tcp 4567
In the following example, the custom protocol virus_home will identify UDP packets with a destination port of 3000 and contain "0x56" in the seventh byte of the payload:ip nbar custom virus_home 7 hex 0x56 dest udp 3000
In the following example, custom protocol media_new will identify TCP packets with a destination or source port of 4500 and that have a value of 90 at the sixth byte of the payload:ip nbar custom media_new 6 decimal 90 tcp 4500
In the following example, custom protocol msn1 will look for TCP packets with a destination or source port of 6700:ip nbar custom msn1 tcp 6700
In the following example, custom protocol mail_x will look for UDP packets with a destination port of 8202:ip nbar custom mail_x destination udp 8202
In the following example, custom protocol mail_y will look for UDP packets with destination ports between 3000 and 4000 including 3000 and 4000 as well as port 5500:ip nbar custom mail_y destination udp range 3000 4000 5500ip nbar pdlm
To extend or enhance the list of protocols recognized by NBAR through a Cisco-provided Packet Description Language Module (PDLM), use the ip nbar pdlm global configuration command. Use the no form of this command to unload a PDLM if it was previously loaded.
ip nbar pdlm pdlm-name
no ip nbar pdlm pdlm-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used in global configuration mode to extend the list of protocols recognized by a given version of NBAR or to enhance an existing protocol-recognition capability. NBAR can be given an external PDLM at run time. In most cases, the PDLM enables NBAR to recognize new protocols without requiring a new Cisco IOS image or a router reload. Only Cisco can provide you with a new PDLM.
To view a list of currently available PDLMs or to download a PDLM, go to the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/pdlmExamples
The following example configures NBAR to load the citrix.pdlm PDLM from Flash memory on the router:
ip nbar pdlm flash://citrix.pdlmRelated Commands
ip nbar port-map
To configure NBAR to search for a protocol or protocol name using a port number other than the well-known port, use the ip nbar port-map global configuration command. Use the no form of this command to look for the protocol name using only the well-known port number.
ip nbar port-map protocol-name [tcp | udp] port-number
no ip nbar port-map protocol-name [tcp | udp] port-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used in global configuration mode to tell NBAR to look for the protocol protocol-name, using a port number or numbers other than the well-known (IANA-assigned) port number. For example, use this command to configure NBAR to look for Telnet on a port other than 23. From 1 to 16 ports can be specified with this command. Port number values can range from 0 to 65535.
Examples
The following example configures NBAR to look for the protocol SQL*NET on port numbers 63000 and 63001 instead of on the well-known port number:
ip nbar port-map sqlnet tcp 63000 63001Related Commands
show ip nbar port-map
Displays the current protocol-to-port mappings in use by NBAR.
ip nbar protocol-discovery
To configure NBAR to discover traffic for all protocols known to NBAR on a particular interface, use the ip nbar protocol-discovery interface configuration command. Use the no form of this command to disable traffic discovery.
ip nbar protocol-discovery
no ip nbar protocol-discovery
Syntax Description
None
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ip nbar protocol-discovery command to configure NBAR to keep traffic statistics for all protocols known to NBAR. Protocol Discovery provides an easy way to discover application protocols traversing an interface so that QoS policies can be developed and applied. The Protocol Discovery feature discovers any protocol traffic supported by NBAR. Protocol Discovery can be used to monitor both input and output traffic and may be applied with or without a service policy enabled.
Examples
The following example configures Protocol Discovery on an Ethernet interface:
interface ethernet 1/3ip nbar protocol-discoveryRelated Commands
show ip nbar protocol-discovery
Displays the statistics gathered by the NBAR Protocol Discovery feature.
match protocol
To match traffic by a particular protocol, use the match protocol class map configuration mode command. Use the no form of this command to turn off traffic matching by protocol type.
match protocol protocol-name [variable-field-name value]
no match protocol protocol-name [variable-field-name value]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class map configuration
Command History
Usage Guidelines
This command can be used to match protocols that are known to NBAR. See the tables in the "Supported Protocols" section for a list of protocols currently supported by NBAR.
The variable-field-name value is used in conjunction with the variable field-name field-length options that are entered when you create a custom protocol using the ip nbar custom command. The variable option allows NBAR to match based on a specific value of a custom protocol. For instance, if ip nbar custom ftdd 125 variable scid 2 tcp range 5001 5005 is entered to create a custom protocol, and then a class map using the match protocol ftdd scid 804 is created, the created class map will match all traffic entering or leaving TCP ports 5001-5005 that have value "804" at byte 125.
Up to 24 variable values per custom protocol can be expressed in class maps. For instance, in the following configuration, 4 variables are used and 20 more "scid" values could be used.
ip nbar custom ftdd field scid 125 variable 1 tcp range 5001 5005class-map active-craftmatch protocol ftdd scid 0x15match protocol ftdd scid 0x21class-map passive-craftmatch protocol ftdd scid 0x11match protocol ftdd scid 0x22Examples
The following example configures NBAR to match FTP traffic:
match protocol ftpIn the following example, custom protocol ftdd is created using a variable. A class map matching this custom protocol based on the variable is also created. In this example, class map matchscidinftdd will match all traffic entering or leaving TCP ports 5001-5005 that has the value "804" at byte 125. The variable scid is 2 bytes in length.
ip nbar custom ftdd 125 variable scid 2 tcp range 5001 5005class-map matchscidinftdd match protocol ftdd scid 804The same example above can also be done using hexadecimal values in the class map as follows:
ip nbar custom ftdd 125 variable scid 2 tcp range 5001 5005class-map matchscidinftdd
match protocol ftdd scid 0x324In the following example, the variable keyword is used while creating a custom protocol, and class maps are configured to classify different values within the variable field into different traffic classes. Specifically, in the example below, variable scid values 0x15, 0x21, and 0x27 will be classified into class map active-craft while scid values 0x11, 0x22, and 0x25 will be classified into class map passive-craft.
ip nbar custom ftdd field scid 125 variable 1 tcp range 5001 5005class-map active-craftmatch protocol ftdd scid 0x15match protocol ftdd scid 0x21match protocol ftdd scid 0x27class-map passive-craftmatch protocol ftdd scid 0x11match protocol ftdd scid 0x22match protocol ftdd scid 0x25match protocol citrix
To configure NBAR to match Citrix traffic, use the match protocol citrix class map configuration mode command. Use the no form of this command to disable NBAR from matching Citrix traffic.
match protocol citrix [app application-name-string]
no match protocol citrix [app application-name-string]
Syntax Description
app
Specifies matching of an application name string.
application-name-string
Specifies string to be used as the subprotocol parameter.
Defaults
No default behavior or values.
Command Modes
Class map configuration
Command History
Usage Guidelines
Entering the match protocol citrix command without any other keywords establishes all Citrix traffic as successful match criteria.
Examples
The following example configures NBAR to match all Citrix traffic:
match protocol citrixThe following example configures NBAR to match Citrix traffic with the application name of packet1:
match protocol citrix app packet1match protocol fasttrack
To configure NBAR to match FastTrack peer-to-peer traffic, use the match protocol fasttrack class map configuration mode command. Use the no form of this command to disable NBAR from matching FastTrack traffic.
match protocol fasttrack file-transfer "regular-expression"
no match protocol fasttrack file-transfer "regular-expression"
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class map configuration
Command History
Usage Guidelines
To specify that all FastTrack traffic be identified by the traffic class, use "*" as the regular expression.
Some applications that use FastTrack include KaZaA, Grokster, and Morpheus (although newer versions of Morpheus use Gnutella).
Examples
The following example configures NBAR to match all FastTrack traffic:
match protocol fasttrack file-transfer "*"In the following example, all FastTrack files that have the ".mpeg" extension will be classified into class map nbar:
class-map match-all nbar match protocol fasttrack file-transfer "*.mpeg"The following example configures NBAR to match FastTrack traffic that contains the string "cisco":
match protocol fasttrack file-transfer "*cisco*"
match protocol gnutella
To configure NBAR to match Gnutella peer-to-peer traffic, use the match protocol gnutella class map configuration mode command. Use the no form of this command to disable NBAR from matching Gnutella traffic.
match protocol gnutella file-transfer "regular-expression"
no match protocol gnutella file-transfer "regular-expression"
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class map configuration
Command History
Usage Guidelines
To specify that all Gnutella traffic be identified by the traffic class, use "*" as the regular expression.
Some applications that use Gnutella include:
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following example configures NBAR to match all Gnutella traffic:
match protocol gnutella file-transfer "*"In the following example, all Gnutella files that have the ".mpeg" extension will be classified into class map nbar:
class-map match-all nbar match protocol gnutella file-transfer "*.mpeg"In the following example, only Gnutella traffic that contains the characters "cisco" is classified:
class-map match-all nbar match protocol gnutella file-transfer "*cisco*"match protocol http
To configure NBAR to match HTTP traffic by URL, host, or MIME type, use the match protocol http class map configuration mode command. Use the no form of this command to disable NBAR from matching HTTP traffic by URL, host, or MIME type.
match protocol http [url url-string | host hostname-string | mime MIME-type]
no match protocol http [url url-string | host hostname-string | mime MIME-type]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class map configuration
Command History
Usage Guidelines
In Cisco IOS Release 12.3(4)T, the NBAR Extended Inspection for HTTP Traffic feature was introduced. This feature allows NBAR to scan TCP ports that are not well-known and identify HTTP traffic traversing these ports. This feature is enabled automatically when a service policy containing the match protocol http command is attached to an interface.
When matching by MIME type, the MIME type can contain any user-specified text string. Refer to the following web page for the IANA-registered MIME types:
ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/media-types
When matching by MIME type, NBAR matches a packet containing the MIME type and all subsequent packets until the next HTTP transaction.
When matching by host, NBAR performs a regular expression match on the host field contents inside the HTTP packet and classifies all packets from that host.
HTTP URL matching supports GET, PUT, HEAD, POST, DELETE, and TRACE. When matching by URL, NBAR recognizes the HTTP packets containing the URL, and then matches all packets that are part of the HTTP request. When specifying a URL for classification, include only the portion of the URL following www.hostname.domain in the match statement. For example, in the URL www.anydomain.com/latest/whatsnew.html, include only /latest/whatsnew.html.
To match the www.anydomain.com portion, use the host name matching feature. The URL or host specification strings can take the form of a regular expression with the following options:
Examples
The following example classifies, within class map foo, HTTP packets based on any URL containing the string whatsnew/latest followed by zero or more characters:
class-map foomatch protocol http url whatsnew/latest*The following example classifies, within class map foo, packets based on any host name containing the string cisco followed by zero or more characters:
class-map foomatch protocol http host cisco*The following example classifies, within class map foo, packets based on the JPEG MIME type:
class-map foomatch protocol http mime "*jpeg"match protocol rtp
To configure NBAR to match RTP traffic, use the match protocol rtp class map configuration mode command. Use the no form of the command to disable NBAR from matching RTP traffic.
match protocol rtp [audio | video | payload-type payload-string]
no match protocol rtp [audio | video | payload-type payload-string]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class map configuration
Command History
Usage Guidelines
Entering the match protocol rtp command without any other keywords establishes all RTP traffic as successful match criteria.
RTP is a packet format for multimedia data streams. It can be used for media-on-demand as well as interactive services such as Internet telephony. RTP consists of a data and a control part. The control part is called Real-time Transport Control Protocol (RTCP). It is important to note that the NBAR RTP Payload Type Classification feature does not identify RTCP packets, and that RTCP packets run on odd-numbered ports while RTP packets run on even-numbered ports.
The payload type field of an RTP packet identifies the format of the RTP payload and is represented by a number. NBAR matches RTP traffic based on this field in the RTP packet, so a working knowledge of RTP and RTP payload types is helpful if you want to configure NBAR to match RTP traffic. The RTP Request for Comments is RFC 1889.
Examples
The following example configures NBAR to match all RTP traffic:
class-map foomatch protocol rtpThe following example configures NBAR to match RTP traffic with the payload-types 0, 1, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, and 64:
class-map foomatch protocol rtp payload-type "0, 1, 4-0x10, 10001b-10010b, 64"show ip nbar pdlm
To display the currently loaded Packet Description Language Modules (PDLMs), use the show ip nbar pdlm privileged EXEC command.
show ip nbar pdlm
Syntax Description
None
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to display a list of all the PDLMs that have been loaded into NBAR using the ip nbar pdlm command.
Examples
In this example of the show ip nbar pdlm command, the citrix.pdlm PDLM has been loaded from Flash memory:
show ip nbar pdlmThe following PDLMs have been loaded:flash://citrix.pdlmRelated Commands
ip nbar pdlm
Extends or enhances the list of protocols recognized by NBAR through a PDLM.
show ip nbar port-map
To display the current protocol-to-port mappings in use by NBAR, use the show ip nbar port-map privileged EXEC command.
show ip nbar port-map [protocol-name]
Syntax Description
Defaults
This command displays port assignments for NBAR protocols.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to display the current protocol-to-port mappings in use by NBAR. When the ip nbar port-map command has been used, the show ip nbar port-map command displays the ports assigned by the user to the protocol. If the no ip nbar port-map command has been used, the show ip nbar port-map command displays the default ports. The protocol-name variable can also be used to limit the display to a specific protocol.
Examples
The following example displays the show ip nbar port-map command:
show ip nbar-port-mapport-map bgp udp 179port-map bgp tcp 179port-map cuseeme udp 7648 7649port-map cuseeme tcp 7648 7649port-map dhcp udp 67 68port-map dhcp tcp 67 68port-map dns udp 53port-map dns tcp 53Related Commands
ip nbar port-map
Configures NBAR to search for a protocol or protocol name using a port number other than the well-known port.
show ip nbar protocol-discovery
To display the statistics gathered by the NBAR Protocol Discovery feature, use the show ip nbar protocol-discovery privileged EXEC command.
show ip nbar protocol-discovery [interface interface-spec] [stats {byte-count | bit-rate | packet-count}][{protocol protocol-name | top-n number}]
Syntax Description
Defaults
Statistics for all interfaces on which the Protocol Discovery feature is enabled are displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show ip nbar protocol-discovery command to display statistics gathered by the Protocol Discovery feature for NBAR. This command, by default, displays statistics for all interfaces on which Protocol Discovery is currently enabled. The default output of this command includes, in the following order, input bit rate (bps), input byte count, input packet count, and protocol name.
Protocol Discovery can be used to monitor both input and output traffic and may be applied with or without a service policy enabled. Protocol Discovery gathers statistics for packets switched to output interfaces. These statistics are not necessarily for packets that exited the router on the output interfaces, because packets may have been dropped after switching for various reasons, including policing at the output interface, access lists, or queue drops.
Examples
The following example displays partial output of the show ip nbar protocol-discovery command for an Ethernet interface:
show ip nbar protocol-discovery interface FastEthernet 6/0FastEthernet6/0Input OutputProtocol Packet Count Packet CountByte Count Byte Count5 minute bit rate (bps) 5 minute bit rate (bps)------------------------ ------------------------ ------------------------igrp 316773 026340105 03000 0streamwork 4437 73672301891 3392133000 0rsvp 279538 14644319106191 6736240 0ntp 8979 7714906550 6942600 0...Total 17203819 15168493619161397327 509670346114179000 6620000Related Commands
show ip nbar version
To display information related to the versioning of the NBAR software in your IOS version or the version of an NBAR PDLM within NBAR on your Cisco IOS router, use the show ip nbar version privileged EXEC command.
show ip nbar version [PDLM-name]
Syntax Description
PDLM-name
(Optional) Specifies the name of a specific PDLM whose information will be provided in the command output.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command treats all protocols that were added to NBAR after the initial NBAR release as PDLMs, including protocols that were added into the Cisco IOS code without a user having to download a PDLM from Cisco.com. PDLMs downloaded from Cisco.com and incorporated into NBAR by the user also appear when the show ip nbar version command is entered.
When using NBAR, various elements within NBAR are assigned versioning numbers. These versioning numbers become significant when you want to download a PDLM. PDLMs, which are also versioned, can only be downloaded to NBAR on a particular Cisco IOS release if the PDLM versioning numbers are compatible with the NBAR version numbers in the Cisco IOS code.
The following NBAR-related version information is available:
•
•
The following version numbers are kept by the PDLM:
•
The show ip nbar version command provides version information for PDLMs already loaded onto the Cisco IOS software.
Examples
The following example displays the show ip nbar version command output:
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: 1In this output, the following values map to the following definitions:
•
•
•
For the same network setup, the following example shows the output if a specific protocol with a PDLM is specified in the show ip nbar version CLI.
Router# show ip nbar version httphttp Mv: 7, Nv: 3; slot1:http_vers.pdlmRelated Commands
ip nbar pdlm
Downloads a PDLM onto a router to add support for additional protocols in NBAR.
Glossary
Modular QoS CLI—Modular Quality of Service Command-Line Interface. A CLI for QoS features that makes configuring and implementing packet classification and QoS policies easier than with the existing CLI.
PDLM—Packet Description Language Module. A file containing Packet Description Language statements used to define the signature of one or more application protocols.
Stateful protocol—A protocol that uses TCP and UDP port numbers that are determined at connection time.
Static protocol—A protocol that uses well-defined (predetermined) TCP and UDP ports for communication.
Subport classification—The classification of network traffic by information contained in the packet payload; that is, information found beyond the TCP or UDP port number.
Appendix
Sample Configuration
Below is a sample of how NBAR can be used.
E-Express Inc.'s network administrators wish to enforce the following policies on a 64-Kb WAN link:
•
•
•
Follow the steps below to configure the above policies:
Step 1
Router(config)# class-map match-all http_transactRouter(config-cmap)# match protocol http url "/transact/*"Router(config)# class-map match-all http_secureRouter(config-cmap)# match protocol secure-httpRouter(config)# class-map match-any ecommerceRouter(config-cmap)# match class-map http_transactRouter(config-cmap)# match class-map http_secureStep 2
Router(config)# access-list 101 permit ip 10.0.0.1 0.0.0.0 10.0.0.3 0.0.0.0Router(config)# class-map match-all super_networkRouter(config-cmap)# match access-group 101Step 3
Router(config)# class-map match-any audio_videoRouter(config-cmap)# match protocol http mime "audio/*"Router(config-cmap)# match protocol http mime "video/*"Router(config)# class-map match-any web_imagesRouter(config-cmap)# match protocol http url "*.gif"Router(config-cmap)# match protocol http url "*.jpg|*.jpeg"Router(config)# class-map match-any av_im_webRouter(config-cmap)# match class-map audio_videoRouter(config-cmap)# match class-map web_imagesStep 4
Router(config)# policy-map e-expressRouter(config-pmap)# class ecommerceRouter(config-pmap-c)# bandwidth 32Router(config-pmap-c)# class super_networkRouter(config-pmap-c)# bandwidth 10Router(config-pmap-c)# class av_im_webRouter(config-pmap-c)# police 10000 conform transmit exceed dropStep 5
Router(config)# interface hssi1/0Router(config-if)# service-policy output e-express
Posted: Mon May 2 17:31:29 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
