This preface describes who should read the Cisco Service Control Application for Broadband Reference Guide, how it is organized, its document conventions, and how to obtain documentation and technical assistance.
This guide assumes a basic familiarity with the concept of the Cisco Service Control solution, the Service Control Engine (SCE) platforms, and related components.
|
Cisco Service Control Release |
Part Number |
Publication Date |
|---|---|---|
|
Release 3.0.5 |
OL-8410-03 |
November, 2006 |
Added the following new feature:
|
Cisco Service Control Release |
Part Number |
Publication Date |
|---|---|---|
|
Release 3.0.3 |
OL-8410-02 |
May, 2006 |
Added the following new feature:
Media Flow RDR (see also Table RPT_MEDIA)
Added the following section to the document:
|
Cisco Service Control Release |
Part Number |
Publication Date |
|---|---|---|
|
Release 3.0.0 |
OL-8410-01 |
December, 2005 |
Created the Cisco Service Control Application for Broadband Reference Guide.
Chapters 1, 2, 3 of this document are based on Appendixes B, C, D of the Release 2.5.5 Cisco Service Control Application for Broadband User Guide.
This guide provides information about the data structures created and used by SCA BB. It is intended for:
The administrator who is responsible for daily operation of the Cisco Service Control solution
Integrators who are developing applications on top of SCA BB
This guide is organized as follows:
|
Chapter |
Title |
Description |
|---|---|---|
|
Chapter 1 |
Describes the default service configuration provided with the Service Control Application for Broadband (SCA BB). | |
|
Chapter 2 |
Lists the various RDRs produced by the Service Control Engine (SCE) platform and gives their structure, describes the columns and fields of each RDR, and states under what conditions each kind of RDR is generated. Also provides field-content information for fields generated by Service Control components (such as tags), and a description of the Periodic RDR Zero Adjustment Mechanism. | |
|
Chapter 3 |
Presents the different database tables used for storing RDRs (after their conversion by an adapter), and a description of the table columns (field names and types). | |
|
Chapter 4 |
Describes the location and structure of CSV files pertaining to service configuration, subscriber management, and data collection management. | |
|
Chapter 5 |
Describes that part of the Cisco SCE proprietary MIB that provides configuration and runtime status for SCA BB. |
The following publications are available for the Service Control Application for Broadband:
Cisco Service Control Application for Broadband User Guide
Cisco Service Control Application for Broadband Service Configuration API Programmer Guide
Cisco Service Control Management Suite Collection Manager User Guide
Cisco Service Control Management Suite Subscriber Manager User Guide
Cisco Service Control Application Reporter User Guide
Cisco Service Control Engine (SCE) Software Configuration Guide
This document uses the following conventions:
|
Convention |
Description |
|---|---|
|
boldface font |
Commands and keywords are in boldface. |
|
italic font |
Arguments for which you supply values are in italics. |
|
[ ] |
Elements in square brackets are optional. |
|
{x | y | z} |
Alternative keywords are grouped in braces and separated by vertical bars. |
|
[x | y | z] |
Optional alternative keywords are grouped in brackets and separated by vertical bars. |
|
string |
A nonquoted set of characters. Do not use quotation marks around the string, or the string will include the quotation marks. |
|
|
Terminal sessions and information that the system displays are in |
|
|
Information you must enter is in |
|
|
Arguments for which you supply values are in |
|
< > |
Nonprinting characters, such as passwords, are in angle brackets. |
|
[ ] |
Default responses to system prompts are in square brackets. |
|
!, # |
An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. |
Means reader take note. Notes contain helpful suggestions or references to materials not covered in this manual.
Means reader be careful. In this situation, you might do something that could result in loss of data.
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package that ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
Registered Cisco Direct Customers can order Cisco Product documentation from the networking Products MarketPlace:
Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at any time, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to http://www.cisco.com.
The Cisco Technical Assistance Center (TAC) website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website http://www.cisco.com/tac.
P3 and P4 level problems are defined as follows:
P3—Your network is degraded. Network functionality is noticeably impaired, but most business operations continue.
P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to http://tools.cisco.com/RPF/register/register.do.
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at http://www.cisco.com/tac/caseopen.
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
P1 and P2 level problems are defined as follows:
P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
This chapter describes the default service configuration provided with the Service Control Application for Broadband (SCA BB). The default service configuration serves as a starting point for creating a service configuration tailored to customers’ needs.
Filter rules allow you to instruct the Service Control Engine (SCE) platform to ignore some types of flow based on the flow’s Layer 3 and Layer 4 properties, and transmit the flows unchanged.
The following table lists the filter rules defined in the default service configuration.
Table 1.1. Filter Rules
|
Flow Filter Name |
Default State |
Description |
|---|---|---|
|
ICMP Filter |
Active |
Applies to ICMP packets, packets bypass the policy engine and are mapped to CoS BE |
|
DNS (to network) |
Active |
Applies to UDP packets, network-side port is equal to 53, packets bypass the policy engine and are mapped to CoS BE |
|
DNS (to subscriber) |
Active |
Applies to UDP packets, subscriber-side port is equal to 53, packets bypass the policy engine and are mapped to CoS BE |
|
net-bios (to network) |
Active |
Applies to UDP packets, network-side port is equal to 137, packets bypass the policy engine and are mapped to CoS BE |
|
net-bios (to subscriber) |
Active |
Applies to UDP packets, subscriber-side port is equal to 137, packets bypass the policy engine and are mapped to CoS BE |
|
eDonkey UDP (to network) |
Active |
Applies to UDP packets, network-side ports in the range 4661 to 4665, packets bypass the policy engine and are mapped to CoS BE |
|
eDonkey UDP (to subscriber) |
Active |
Applies to UDP packets, subscriber-side ports in the range 4661 to 4665, packets bypass the policy engine and are mapped to CoS BE |
|
eMule UDP (to network) |
Active |
Applies to UDP packets, network-side ports in the range 4670 to 4674, packets bypass the policy engine and are mapped to CoS BE |
|
eMule UDP (to subscriber) |
Active |
Applies to UDP packets, subscriber-side ports in the range 4670 to 4674, packets bypass the policy engine and are mapped to CoS BE |
|
eMule UDP 2 (to network) |
Active |
Applies to UDP packets, network-side ports in the range 5670 to 5674, packets bypass the policy engine and are mapped to CoS BE |
|
eMule UDP 2 (to subscriber) |
Active |
Applies to UDP packets, subscriber-side ports in the range 5670 to 5674, packets bypass the policy engine and are mapped to CoS BE |
|
eMule UDP 3 (to network) |
Active |
Applies to UDP packets, network-side ports in the range 5780 to 5784, packets bypass the policy engine and are mapped to CoS BE |
|
eMule UDP 3 (to subscriber) |
Active |
Applies to UDP packets, subscriber-side ports in the range 5780 to 5784, packets bypass the policy engine and are mapped to CoS BE |
|
BGP Filter |
Inactive |
Applies to TCP packets, network-side port is equal to 179, packets bypass the policy engine and are mapped to CoS BE |
|
DHCP Filter |
Inactive |
Applies to UDP packets, network-side ports in the range 67 to 68, packets bypass the policy engine and are mapped to CoS BE |
|
OSPF Filter |
Inactive |
Applies to OSPFIGP packets, packets bypass the policy engine and are mapped to CoS BE |
|
IS-IS Filter |
Inactive |
Applies to ISIS packets, packets bypass the policy engine and are mapped to CoS BE |
|
IGRP Filter |
Inactive |
Applies to IGP packets, packets bypass the policy engine and are mapped to CoS BE |
|
EIGRP Filter |
Inactive |
Applies to EIGRP packets, packets bypass the policy engine and are mapped to CoS BE |
|
HSRP Filter 1 |
Inactive |
Applies to UDP packets, network-side IP is equal to 224.0.0.2, packets bypass the policy engine and are mapped to CoS BE |
|
HSRP Filter 2 |
Inactive |
Applies to UDP packets, network-side port is equal to 1985, packets bypass the policy engine and are mapped to CoS BE |
|
HSRP Filter 3 |
Inactive |
Applies to UDP packets, subscriber-side port is equal to 1985, packets bypass the policy engine and are mapped to CoS BE |
|
RIP Filter 1 |
Inactive |
Applies to UDP packets, network-side IP is equal to 224.0.0.9, packets bypass the policy engine and are mapped to CoS BE |
|
RIP Filter 2 |
Inactive |
Applies to UDP packets, network-side port is equal to 520, packets bypass the policy engine and are mapped to CoS BE |
|
RIP Filter 3 |
Inactive |
Applies to UDP packets, subscriber-side port is equal to 520, packets bypass the policy engine and are mapped to CoS BE |
|
RADIUS Filter |
Inactive |
Applies to UDP packets, network-side port is equal to 1812, packets bypass the policy engine and are mapped to CoS BE |
|
RADIUS Filter (early deployment) |
Inactive |
Applies to UDP packets, network-side ports in the range 1645 to 1646, packets bypass the policy engine and are mapped to CoS BE |
Protocols are divided into four groups:
Generic Protocols—These protocols are used for transactions that were not mapped to a service by one of the more specific protocol types.
Signature-Based Protocols—Protocols classified according to a Layer 7 application signature. This group includes the most common protocols, such as HTTP and FTP, and a large group of popular P2P protocols.
IP Protocols—Protocols (such as ICMP), other than TCP and UDP protocols, identified according to the IP protocol number of the transaction.
Port-Based Protocols—TCP and UDP protocols that are classified according to their well-known ports. The default configuration includes more than 600 common port-based protocols.
You may add new protocols (for example, to classify a new gaming protocol that uses a specific port) and edit or remove existing ones.
The tables in the following sections list the protocols defined in the default service configuration.
The three generic protocols (IP, TCP, and UDP) serve as default containers for classifying transactions of the relevant type (IP, TCP, or UDP) that were not classified as belonging to a more specific protocol.
A transaction is classified as belonging to one of the generic protocols if it meets both the following conditions:
It was not classified as belonging to a signature-based protocol.
It was not classified as belonging to an IP or port-based protocol that is specifically mapped to a service.
Table 1.2. Generic Protocols
|
Protocol Name |
ID |
Description |
|---|---|---|
|
Generic IP |
10 |
Any non-TCP/UDP transaction where the related IP protocol is not specifically mapped to a service. |
|
Generic TCP |
0 |
Any TCP transaction that does not match any signature-based protocol, and where the related port-based protocol (if it exists) is not specifically mapped to a service. |
|
Generic UDP |
1 |
Any UDP transaction that does not match any signature-based protocol, and where the related port-based protocol (if it exists) is not specifically mapped to a service. |
A transaction is classified as belonging to one of the signature-based protocols if it is carried on the protocol’s well-known port or matches the protocol’s signature.
Table 1.3. Signature-Based Protocols
|
Protocol Name |
ID |
TCP Ports |
UDP Ports |
|---|---|---|---|
|
CUWorld |
117 |
|
|
|
DHCP Sniff |
33 |
|
|
|
DingoTel |
42 |
|
|
|
DNS |
933 |
|
|
|
FTP |
4 |
21 |
|
|
Generic Non-Established TCP See note following table |
126 |
|
|
|
Generic Upload/Download See note following table |
127 |
|
|
|
GoogleEarth |
118 |
|
|
|
Hopster |
115 |
|
|
|
HTTP Browsing |
2 |
80, 8080 |
|
|
HTTP Tunnel |
55 |
|
|
|
ICQ |
119 |
|
|
|
IRC |
62 |
|
|
|
Jabber |
116 |
|
|
|
MMS |
6 |
1755 |
|
|
Mobile MMS |
46 |
|
|
|
NNTP |
15 |
119 |
|
|
NTP |
54 |
|
|
|
POP3 |
9 |
110 |
|
|
PTT Winphoria |
61 |
|
|
|
|
52 |
|
|
|
RTSP Streaming |
5 |
554, 1554, 7070 |
|
|
Sling |
112 |
|
|
|
SMTP |
8 |
25 |
|
|
STUN |
114 |
|
|
|
Thunder |
50 |
|
|
|
UC |
48 |
|
|
|
Yahoo Messenger |
40 |
5000-5001 |
5000-5001 |
|
imap |
59 |
143 |
143 |
|
radius |
738 |
|
|
|
tftp |
60 |
69 |
69 |
Generic Non-Established TCP—TCP flows that are not established properly (syn-ack is missing) are mapped to this protocol.
Generic Upload/Download—Transactions that have download packet flow characteristics and do not match a more specific signature are classified to this protocol. This protocol applies to downloads both from the network side and from the subscriber side.
Table 1.4. Signature-Based P2P Protocols
|
Protocol Name |
ID |
TCP Ports |
UDP Ports |
|---|---|---|---|
|
AntsP2P |
113 |
|
|
|
BaiBao |
43 |
|
|
|
BitTorrent |
24 |
6881-6889 |
|
|
Dijjer |
120 |
|
|
|
DirectConnect |
19 |
411-413 |
|
|
Entropy |
125 |
|
|
|
Exosee |
121 |
|
|
|
FastTrack KaZaA File Transfer |
14 |
|
|
|
FastTrack KaZaA Networking |
13 |
1214 |
|
|
Filetopia |
31 |
|
|
|
Freenet |
107 |
|
|
|
Furthur |
123 |
|
|
|
Gnutella File Transfer |
12 |
|
|
|
Gnutella Networking |
11 |
6346-6349 |
|
|
Hotline |
20 |
|
|
|
Konspire2b |
1031 |
6085 |
6085 |
|
Kontiki |
124 |
|
|
|
LOCO |
5123 |
|
|
|
Manolito |
22 |
|
|
|
Mute |
34 |
|
|
|
Napster |
32 |
|
|
|
NeoNet |
37 |
|
|
|
NodeZilla |
35 |
|
|
|
PeerEnabler |
122 |
|
|
|
Poco |
51 |
|
|
|
PPLive |
44 |
|
|
|
PPStream |
49 |
|
|
|
Rodi |
111 |
|
|
|
Share |
27 |
|
|
|
Soulseek |
29 |
|
|
|
SSDP |
53 |
|
|
|
TVAnts |
109 |
|
|
|
Warez/FileCroc |
39 |
|
|
|
Waste |
36 |
|
|
|
WinMX/OpenNap |
16 |
6257, 6699 |
6257 |
|
Winny |
17 |
7742-7745, 7773 |
|
|
eDonkey |
18 |
4661-4665, 4672-4673, 4711, 5662, 5773, 5783 |
4661-4665, 4672-4673, 4711, 5662, 5773, 5783 |
|
guruguru |
66 |
|
|
|
iTunes |
30 |
|
|
|
kuro |
67 |
|
|
|
soribada |
69 |
|
|
|
v-share |
71 |
|
|
Table 1.5. Signature-Based VoIP Protocols
|
Protocol Name |
ID |
TCP Ports |
UDP Ports |
|---|---|---|---|
|
H323 |
28 |
1720 |
|
|
ICQ VoIP |
110 |
|
|
|
MGCP |
38 |
|
2427, 2727 |
|
Primus |
108 |
|
|
|
RTP |
57 |
|
|
|
SIP |
23 |
5060-5061 |
5060-5061 |
|
Skinny |
41 |
|
|
|
Skype |
25 |
|
|
|
Yahoo Messenger VoIP |
45 |
33033 |
|
This section lists the IP protocols supported by SCA BB.
Table 1.6. IP Protocols
|
IP Protocol Number |
Protocol Name |
Protocol ID |
|---|---|---|
|
0 |
HOPOPT |
756 |
|
1 |
ICMP |
757 |
|
2 |
IGMP |
758 |
|
3 |
GGP |
759 |
|
4 |
IP |
760 |
|
5 |
ST |
761 |
|
6 |
Generic TCP |
0 |
|
7 |
CBT |
762 |
|
8 |
EGP |
763 |
|
9 |
IGP |
764 |
|
10 |
BBN-RCC-MON |
765 |
|
11 |
NVP-II |
766 |
|
12 |
PUP |
767 |
|
13 |
ARGUS |
768 |
|
14 |
EMCON |
769 |
|
15 |
XNET |
770 |
|
16 |
CHAOS |
771 |
|
17 |
Generic UDP |
1 |
|
18 |
MUX |
772 |
|
19 |
DCN-MEAS |
773 |
|
20 |
HMP |
774 |
|
21 |
PRM |
775 |
|
22 |
XNS-IDP |
776 |
|
23 |
TRUNK-1 |
777 |
|
24 |
TRUNK-2 |
778 |
|
25 |
LEAF-1 |
779 |
|
26 |
LEAF-2 |
780 |
|
27 |
RDP |
781 |
|
28 |
IRTP |
782 |
|
29 |
ISO-TP4 |
783 |
|
30 |
NETBLT |
784 |
|
31 |
MFE-NSP |
785 |
|
32 |
MERIT-INP |
786 |
|
33 |
SEP |
787 |
|
34 |
3PC |
788 |
|
35 |
IDPR |
789 |
|
36 |
XTP |
790 |
|
37 |
DDP |
791 |
|
38 |
IDPR-CMTP |
792 |
|
39 |
TP++ |
793 |
|
40 |
IL |
794 |
|
41 |
IPv6-Over-IPv4 |
795 |
|
42 |
SDRP |
796 |
|
43 |
IPv6-Route |
797 |
|
44 |
IPv6-Frag |
798 |
|
45 |
IDRP |
799 |
|
46 |
RSVP |
800 |
|
47 |
GRE |
801 |
|
48 |
MHRP |
802 |
|
49 |
BNA |
803 |
|
50 |
ESP |
804 |
|
51 |
AH |
805 |
|
52 |
I-NLSP |
806 |
|
53 |
SWIPE |
807 |
|
54 |
NARP |
808 |
|
55 |
MOBILE |
809 |
|
56 |
TLSP |
810 |
|
57 |
SKIP |
811 |
|
58 |
IPv6-ICMP |
812 |
|
59 |
IPv6-NoNxt |
813 |
|
60 |
IPv6-Opts |
814 |
|
61 |
any host internal protocol |
815 |
|
62 |
CFTP |
816 |
|
63 |
any local network |
817 |
|
64 |
SAT-EXPAK |
818 |
|
65 |
KRYPTOLAN |
819 |
|
66 |
RVD |
820 |
|
67 |
IPPC |
821 |
|
68 |
any distributed file system |
822 |
|
69 |
SAT-MON |
823 |
|
70 |
VISA |
824 |
|
71 |
IPCV |
825 |
|
72 |
CPNX |
826 |
|
73 |
CPHB |
827 |
|
74 |
WSN |
828 |
|
75 |
PVP |
829 |
|
76 |
BR-SAT-MON |
830 |
|
77 |
SUN-ND |
831 |
|
78 |
WB-MON |
832 |
|
79 |
WB-EXPAK |
833 |
|
80 |
ISO-IP |
834 |
|
81 |
VMTP |
835 |
|
82 |
SECURE-VMTP |
836 |
|
83 |
VINES |
837 |
|
84 |
TTP |
838 |
|
85 |
NSFNET-IGP |
839 |
|
86 |
DGP |
840 |
|
87 |
TCF |
841 |
|
88 |
EIGRP |
842 |
|
89 |
OSPFIGP |
843 |
|
90 |
Sprite-RPC |
844 |
|
91 |
LARP |
845 |
|
92 |
MTP |
846 |
|
93 |
AX.25 |
847 |
|
94 |
IPIP |
848 |
|
95 |
MICP |
849 |
|
96 |
SCC-SP |
850 |
|
97 |
ETHERIP |
851 |
|
98 |
ENCAP |
852 |
|
99 |
any private encryption scheme |
853 |
|
100 |
GMTP |
854 |
|
101 |
IFMP |
855 |
|
102 |
PNNI |
856 |
|
103 |
PIM |
857 |
|
104 |
ARIS |
858 |
|
105 |
SCPS |
859 |
|
106 |
QNX |
860 |
|
107 |
A/N |
861 |
|
108 |
IPComp |
862 |
|
109 |
SNP |
863 |
|
110 |
Compaq-Peer |
864 |
|
111 |
IPX-in-IP |
865 |
|
112 |
VRRP |
866 |
|
113 |
PGM |
867 |
|
114 |
any 0-hop protocol |
868 |
|
115 |
L2TP |
869 |
|
116 |
DDX |
870 |
|
117 |
IATP |
871 |
|
118 |
STP |
872 |
|
119 |
SRP |
873 |
|
120 |
UTI |
874 |
|
121 |
SMP |
875 |
|
122 |
SM |
876 |
|
123 |
PTP |
877 |
|
124 |
ISIS |
878 |
|
125 |
FIRE |
879 |
|
126 |
CRTP |
880 |
This section lists the TCP/UDP port-based protocols defined in the SCA BB default service configuration.
Table 1.7. Port-Based Protocols (Ports 1 to 500)
|
Protocol Name |
ID |
TCP Ports |
UDP Ports |
|---|---|---|---|
|
compressnet |
900 |
2-3 |
2-3 |
|
RJE |
901 |
5 |
5 |
|
Echo |
902 |
7 |
7 |
|
Discard |
903 |
9 |
9 |
|
systat |
904 |
11 |
11 |
|
daytime |
905 |
13 |
13 |
|
qotd |
906 |
17 |
17 |
|
msp |
907 |
18 |
18 |
|
chargen |
908 |
19 |
19 |
|
ftp-data |
909 |
20 |
20 |
|
ssh |
910 |
22 |
22 |
|
telnet |
911 |
23 |
23 |
|
nsw-fe |
912 |
27 |
27 |
|
msg-icp |
913 |
29 |
29 |
|
msg-auth |
916 |
31 |
31 |
|
dsp |
917 |
33 |
33 |
|
time |
918 |
37 |
37 |
|
rap |
919 |
38 |
38 |
|
rlp |
920 |
39 |
39 |
|
graphics |
921 |
41 |
41 |
|
name |
922 |
42 |
42 |
|
nicname |
923 |
43 |
43 |
|
mpm-flags |
924 |
44 |
44 |
|
mpm |
925 |
45 |
45 |
|
mpm-snd |
926 |
46 |
46 |
|
ni-ftp |
927 |
47 |
47 |
|
auditd |
928 |
48 |
48 |
|
tacacs |
929 |
49 |
49 |
|
re-mail-ck |
930 |
50 |
50 |
|
la-maint |
931 |
51 |
51 |
|
xns-time |
932 |
52 |
52 |
|
xns-ch |
934 |
54 |
54 |
|
isi-gl |
935 |
55 |
55 |
|
xns-auth |
936 |
56 |
56 |
|
xns-mail |
937 |
58 |
58 |
|
ni-mail |
938 |
61 |
61 |
|
acas |
939 |
62 |
62 |
|
whois |
940 |
63 |
63 |
|
covia |
941 |
64 |
64 |
|
tacacs-ds |
942 |
65 |
65 |
|
sql*net |
943 |
66 |
66 |
|
bootps |
944 |
67 |
67 |
|
bootpc |
945 |
68 |
68 |
|
gopher |
947 |
70 |
70 |
|
netrjs-1 |
948 |
71 |
71 |
|
netrjs-2 |
949 |
72 |
72 |
|
netrjs-3 |
950 |
73 |
73 |
|
netrjs-4 |
951 |
74 |
74 |
|
deos |
952 |
76 |
76 |
|
finger |
953 |
79 |
79 |
|
hosts2-ns |
954 |
81 |
81 |
|
xfer |
955 |
82 |
82 |
|
mit-ml-dev |
956 |
83, 85 |
83, 85 |
|
ctf |
957 |
84 |
84 |
|
mfcobol |
958 |
86 |
86 |
|
kerberos |
959 |
88 |
88 |
|
su-mit-tg |
960 |
89 |
89 |
|
dnsix |
961 |
90 |
90 |
|
mit-dov |
962 |
91 |
91 |
|
npp |
963 |
92 |
92 |
|
dcp |
964 |
93 |
93 |
|
objcall |
965 |
94 |
94 |
|
supdup |
966 |
95 |
95 |
|
dixie |
967 |
96 |
96 |
|
swift-rvf |
968 |
97 |
97 |
|
tacnews |
969 |
98 |
98 |
|
metagram |
970 |
99 |
99 |
|
newacct |
971 |
100 |
|
|
hostname |
972 |
101 |
101 |
|
iso-tsap |
973 |
102 |
102 |
|
gppitnp |
974 |
103 |
103 |
|
acr-nema |
975 |
104 |
104 |
|
csnet-ns |
976 |
105 |
105 |
|
3com-tsmux |
977 |
106 |
106 |
|
rtelnet |
978 |
107 |
107 |
|
snagas |
979 |
108 |
108 |
|
pop2 |
980 |
109 |
109 |
|
sunrpc |
981 |
111 |
111 |
|
mcidas |
982 |
112 |
112 |
|
auth |
983 |
113 |
113 |
|
audionews |
984 |
114 |
114 |
|
sftp |
985 |
115 |
115 |
|
ansanotify |
986 |
116 |
116 |
|
uucp-path |
987 |
117 |
117 |
|
sqlserv |
988 |
118 |
118 |
|
cfdptkt |
989 |
120 |
120 |
|
erpc |
990 |
121 |
121 |
|
smakynet |
991 |
122 |
122 |
|
NTP |
992 |
123 |
123 |
|
ansatrader |
993 |
124 |
124 |
|
locus-map |
994 |
125 |
125 |
|
nxedit |
995 |
126 |
126 |
|
locus-con |
996 |
127 |
127 |
|
gss-xlicen |
997 |
128 |
128 |
|
pwdgen |
998 |
129 |
129 |
|
cisco-fna |
999 |
130 |
130 |
|
cisco-tna |
1000 |
131 |
131 |
|
cisco-sys |
1001 |
132 |
132 |
|
statsrv |
1002 |
133 |
133 |
|
ingres-net |
1003 |
134 |
134 |
|
epmap |
128 |
135 |
135 |
|
profile |
129 |
136 |
136 |
|
netbios-ns |
130 |
137 |
137 |
|
netbios-dgm |
131 |
138 |
138 |
|
netbios-ssn |
132 |
139 |
139 |
|
emfis-data |
133 |
140 |
140 |
|
emfis-cntl |
134 |
141 |
141 |
|
bl-idm |
135 |
142 |
142 |
|
uma |
137 |
144 |
144 |
|
uaac |
138 |
145 |
145 |
|
iso-tp0 |
139 |
146 |
146 |
|
iso-ip |
140 |
147 |
147 |
|
jargon |
141 |
148 |
148 |
|
aed-512 |
142 |
149 |
149 |
|
sql-net |
143 |
150 |
150 |
|
hems |
144 |
151 |
151 |
|
bftp |
145 |
152 |
152 |
|
sgmp |
146 |
153 |
153 |
|
netsc-prod |
147 |
154 |
154 |
|
netsc-dev |
148 |
155 |
155 |
|
sqlsrv |
149 |
156 |
156 |
|
knet-cmp |
150 |
157 |
157 |
|
pcmail-srv |
151 |
158 |
158 |
|
nss-routing |
152 |
159 |
159 |
|
sgmp-traps |
153 |
160 |
160 |
|
snmp |
154 |
161 |
161 |
|
snmptrap |
155 |
162 |
162 |
|
cmip-man |
156 |
163 |
163 |
|
cmip-agent |
157 |
164 |
164 |
|
xns-courier |
158 |
165 |
165 |
|
s-net |
159 |
166 |
166 |
|
namp |
160 |
167 |
167 |
|
rsvd |
161 |
168 |
168 |
|
send |
162 |
169 |
169 |
|
print-srv |
163 |
170 |
170 |
|
multiplex |
164 |
171 |
171 |
|
cl/1 |
165 |
172 |
172 |
|
xyplex-mux |
166 |
173 |
173 |
|
mailq |
167 |
174 |
174 |
|
vmnet |
168 |
175 |
175 |
|
genrad-mux |
169 |
176 |
176 |
|
xdmcp |
170 |
177 |
177 |
|
nextstep |
171 |
178 |
178 |
|
bgp |
172 |
179 |
179 |
|
ris |
173 |
180 |
180 |
|
unify |
174 |
181 |
181 |
|
audit |
175 |
182 |
182 |
|
ocbinder |
176 |
183 |
183 |
|
ocserver |
177 |
184 |
184 |
|
remote-kis |
178 |
185 |
185 |
|
kis |
179 |
186 |
186 |
|
aci |
180 |
187 |
187 |
|
mumps |
181 |
188 |
188 |
|
qft |
182 |
189 |
189 |
|
gacp |
183 |
190 |
190 |
|
prospero |
184 |
191 |
191 |
|
osu-nms |
185 |
192 |
192 |
|
srmp |
186 |
193 |
193 |
|
IRC |
187 |
194 |
194 |
|
dn6-nlm-aud |
188 |
195 |
195 |
|
dn6-smm-red |
189 |
196 |
196 |
|
dls |
190 |
197 |
197 |
|
dls-mon |
191 |
198 |
198 |
|
smux |
192 |
199 |
199 |
|
src |
193 |
200 |
200 |
|
at-rtmp |
194 |
201 |
201 |
|
at-nbp |
195 |
202 |
202 |
|
at-3 |
196 |
203 |
203 |
|
at-echo |
197 |
204 |
204 |
|
at-5 |
198 |
205 |
205 |
|
at-zis |
199 |
206 |
206 |
|
at-7 |
200 |
207 |
207 |
|
at-8 |
201 |
208 |
208 |
|
qmtp |
202 |
209 |
209 |
|
z39.50 |
203 |
210 |
210 |
|
914c/g |
204 |
211 |
211 |
|
anet |
205 |
212 |
212 |
|
ipx |
206 |
213 |
213 |
|
vmpwscs |
207 |
214 |
214 |
|
softpc |
208 |
215 |
215 |
|
CAIlic |
209 |
216 |
216 |
|
dbase |
210 |
217 |
217 |
|
mpp |
211 |
218 |
218 |
|
uarps |
212 |
219 |
219 |
|
imap3 |
213 |
220 |
220 |
|
fln-spx |
214 |
221 |
221 |
|
rsh-spx |
215 |
222 |
222 |
|
cdc |
216 |
223 |
223 |
|
masqdialer |
217 |
224 |
224 |
|
direct |
218 |
242 |
242 |
|
sur-meas |
219 |
243 |
243 |
|
inbusiness |
220 |
244 |
244 |
|
link |
221 |
245 |
245 |
|
dsp3270 |
222 |
246 |
246 |
|
subntbcst_tftp |
223 |
247 |
247 |
|
bhfhs |
224 |
248 |
248 |
|
set |
225 |
257 |
257 |
|
yak-chat |
226 |
258 |
258 |
|
esro-gen |
227 |
259 |
259 |
|
openport |
228 |
260 |
260 |
|
nsiiops |
229 |
261 |
261 |
|
arcisdms |
230 |
262 |
262 |
|
hdap |
231 |
263 |
263 |
|
bgmp |
232 |
264 |
264 |
|
x-bone-ctl |
233 |
265 |
265 |
|
sst |
234 |
266 |
266 |
|
td-service |
235 |
267 |
267 |
|
td-replica |
236 |
268 |
268 |
|
http-mgmt |
237 |
280 |
280 |
|
personal-link |
238 |
281 |
281 |
|
cableport-ax |
239 |
282 |
282 |
|
rescap |
240 |
283 |
283 |
|
corerjd |
241 |
284 |
284 |
|
fxp-1 |
242 |
286 |
286 |
|
k-block |
243 |
287 |
287 |
|
novastorbakcup |
244 |
308 |
308 |
|
entrusttime |
245 |
309 |
309 |
|
bhmds |
246 |
310 |
310 |
|
asip-webadmin |
247 |
311 |
311 |
|
vslmp |
248 |
312 |
312 |
|
magenta-logic |
249 |
313 |
313 |
|
opalis-robot |
250 |
314 |
314 |
|
dpsi |
251 |
315 |
315 |
|
decauth |
252 |
316 |
316 |
|
zannet |
253 |
317 |
317 |
|
pkix-timestamp |
254 |
318 |
318 |
|
ptp-event |
255 |
319 |
319 |
|
ptp-general |
256 |
320 |
320 |
|
pip |
257 |
321 |
321 |
|
rtsps |
258 |
322 |
322 |
|
texar |
259 |
333 |
333 |
|
pdap |
260 |
344 |
344 |
|
pawserv |
261 |
345 |
345 |
|
zserv |
262 |
346 |
346 |
|
fatserv |
263 |
347 |
347 |
|
csi-sgwp |
264 |
348 |
348 |
|
mftp |
265 |
349 |
349 |
|
matip-type-a |
266 |
350 |
350 |
|
matip-type-b |
267 |
351 |
351 |
|
dtag-ste-sb |
268 |
352 |
352 |
|
ndsauth |
269 |
353 |
353 |
|
bh611 |
270 |
354 |
354 |
|
datex-asn |
271 |
355 |
355 |
|
cloanto-net-1 |
272 |
356 |
356 |
|
bhevent |
273 |
357 |
357 |
|
shrinkwrap |
274 |
358 |
358 |
|
nsrmp |
275 |
359 |
359 |
|
scoi2odialog |
276 |
360 |
360 |
|
semantix |
277 |
361 |
361 |
|
srssend |
278 |
362 |
362 |
|
rsvp_tunnel |
279 |
363 |
363 |
|
aurora-cmgr |
280 |
364 |
364 |
|
dtk |
281 |
365 |
365 |
|
odmr |
282 |
366 |
366 |
|
mortgageware |
283 |
367 |
367 |
|
qbikgdp |
284 |
368 |
368 |
|
rpc2portmap |
285 |
369 |
369 |
|
codaauth2 |
286 |
370 |
370 |
|
clearcase |
287 |
371 |
371 |
|
ulistproc |
288 |
372 |
372 |
|
legent-1 |
289 |
373 |
373 |
|
legent-2 |
290 |
374 |
374 |
|
hassle |
291 |
375 |
375 |
|
nip |
292 |
376 |
376 |
|
tnETOS |
293 |
377 |
377 |
|
dsETOS |
294 |
378 |
378 |
|
is99c |
295 |
379 |
379 |
|
is99s |
296 |
380 |
380 |
|
hp-collector |
297 |
381 |
381 |
|
hp-managed-node |
298 |
382 |
382 |
|
hp-alarm-mgr |
299 |
383 |
383 |
|
arns |
300 |
384 |
384 |
|
ibm-app |
301 |
385 |
385 |
|
asa |
302 |
386 |
386 |
|
aurp |
303 |
387 |
387 |
|
unidata-ldm |
304 |
388 |
388 |
|
ldap |
305 |
|
389 |
|
uis |
306 |
390 |
390 |
|
synotics-relay |
307 |
391 |
391 |
|
synotics-broker |
308 |
392 |
392 |
|
meta5 |
309 |
393 |
393 |
|
embl-ndt |
310 |
394 |
394 |
|
netware-ip |
311 |
396 |
396 |
|
mptn |
312 |
397 |
397 |
|
kryptolan |
313 |
398 |
398 |
|
iso-tsap-c2 |
314 |
399 |
399 |
|
work-sol |
315 |
400 |
400 |
|
ups |
316 |
401 |
401 |
|
genie |