This table contains the traffic related statistics for two
categories of protocols. The first category of protocols are
identified using the protocol handlers of the entity which
provides the content services. These typically includes
protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns
which use well-known ports and for which deep packet inspection
upto the application layer has been performed. The second
category contains those protocols which have been identified
using the NBAR classification engine and are known as NBAR
protocols. These typically consist of the various peer-to-peer
(P2P) protocols which do not use a standard port range.
This table is indexed on entPhysicalIndex which identifies the
entity that provides the content services, ccspsInspectionMethod
which denotes the type of inspection method used to identify the
protocol, and ccspsProtocolName which is the name of the
protocol.
Parsed from file CISCO-CONTENT-SERVICES-MIB.mib
Module: CISCO-CONTENT-SERVICES-MIB
This table contains the traffic related statistics for two
categories of protocols. The first category of protocols are
identified using the protocol handlers of the entity which
provides the content services. These typically includes
protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns
which use well-known ports and for which deep packet inspection
upto the application layer has been performed. The second
category contains those protocols which have been identified
using the NBAR classification engine and are known as NBAR
protocols. These typically consist of the various peer-to-peer
(P2P) protocols which do not use a standard port range.
This table is indexed on entPhysicalIndex which identifies the
entity that provides the content services, ccspsInspectionMethod
which denotes the type of inspection method used to identify the
protocol, and ccspsProtocolName which is the name of the
protocol.
This table contains the traffic related statistics for two
categories of protocols. The first category of protocols are
identified using the protocol handlers of the entity which
provides the content services. These typically includes
protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns
which use well-known ports and for which deep packet inspection
upto the application layer has been performed. The second
category contains those protocols which have been identified
using the NBAR classification engine and are known as NBAR
protocols. These typically consist of the various peer-to-peer
(P2P) protocols which do not use a standard port range.
This table is indexed on entPhysicalIndex which identifies the
entity that provides the content services, ccspsInspectionMethod
which denotes the type of inspection method used to identify the
protocol, and ccspsProtocolName which is the name of the
protocol.
Parsed from file CISCO-CONTENT-SERVICES-MIB.my.txt
Company: None
Module: CISCO-CONTENT-SERVICES-MIB
This table contains the traffic related statistics for two
categories of protocols. The first category of protocols are
identified using the protocol handlers of the entity which
provides the content services. These typically includes
protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns
which use well-known ports and for which deep packet inspection
upto the application layer has been performed. The second
category contains those protocols which have been identified
using the NBAR classification engine and are known as NBAR
protocols. These typically consist of the various peer-to-peer
(P2P) protocols which do not use a standard port range.
This table is indexed on entPhysicalIndex which identifies the
entity that provides the content services, ccspsInspectionMethod
which denotes the type of inspection method used to identify the
protocol, and ccspsProtocolName which is the name of the
protocol.
ccsProtocolStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF CcsProtocolStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the traffic related statistics for two categories of protocols. The first category of protocols are identified using the protocol handlers of the entity which provides the content services. These typically includes protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns which use well-known ports and for which deep packet inspection upto the application layer has been performed. The second category contains those protocols which have been identified using the NBAR classification engine and are known as NBAR protocols. These typically consist of the various peer-to-peer (P2P) protocols which do not use a standard port range. This table is indexed on entPhysicalIndex which identifies the entity that provides the content services, ccspsInspectionMethod which denotes the type of inspection method used to identify the protocol, and ccspsProtocolName which is the name of the protocol." ::= { ccsStats 6 }
ccsProtocolStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF CcsProtocolStatsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains the traffic related statistics for two categories of protocols. The first category of protocols are identified using the protocol handlers of the entity which provides the content services. These typically includes protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns which use well-known ports and for which deep packet inspection upto the application layer has been performed. The second category contains those protocols which have been identified using the NBAR classification engine and are known as NBAR protocols. These typically consist of the various peer-to-peer (P2P) protocols which do not use a standard port range. This table is indexed on entPhysicalIndex which identifies the entity that provides the content services, ccspsInspectionMethod which denotes the type of inspection method used to identify the protocol, and ccspsProtocolName which is the name of the protocol." ::= { ccsStats 6 }
Vendor: Cisco
Module: CISCO-CONTENT-SERVICES-MIB
[Automatically extracted from oidview.com]
ccsProtocolStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF CcsProtocolStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the traffic related statistics for two categories of protocols. The first category of protocols are identified using the protocol handlers of the entity which provides the content services. These typically includes protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns which use well-known ports and for which deep packet inspection upto the application layer has been performed. The second category contains those protocols which have been identified using the NBAR classification engine and are known as NBAR protocols. These typically consist of the various peer-to-peer (P2P) protocols which do not use a standard port range. This table is indexed on entPhysicalIndex which identifies the entity that provides the content services, ccspsInspectionMethod which denotes the type of inspection method used to identify the protocol, and ccspsProtocolName which is the name of the protocol." ::= { ccsStats 6 }
ccsProtocolStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF CcsProtocolStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the traffic related statistics for two categories of protocols. The first category of protocols are identified using the protocol handlers of the entity which provides the content services. These typically includes protocols like http, ftp, rtsp, sip, pop3, imap, smtp, wap and dns which use well-known ports and for which deep packet inspection upto the application layer has been performed. The second category contains those protocols which have been identified using the NBAR classification engine and are known as NBAR protocols. These typically consist of the various peer-to-peer (P2P) protocols which do not use a standard port range. This table is indexed on entPhysicalIndex which identifies the entity that provides the content services, ccspsInspectionMethod which denotes the type of inspection method used to identify the protocol, and ccspsProtocolName which is the name of the protocol." ::= { ccsStats 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.597.1.2.6.1 | ccsProtocolStatsEntry | 32 | 32 | Each row in this table contains the traffic related statistics for a supported application layer protocol. An entry is added in t… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.597.1.2.1 | ccsGlobalStatsTable | 1 | 27 | This table contains the global statistical information in content billing feature. |
| 1.3.6.1.4.1.9.9.597.1.2.2 | ccsUserDbTable | 1 | 17 | Table of User Database Server. Entries are added to this table via ccsUserDbRowStatus in accordance with the RowStatus convention. |
| 1.3.6.1.4.1.9.9.597.1.2.3 | ccsBMATable | 1 | 23 | A table of billing mediation agents (BMAs). Columnar objects can be modified when the row is 'active'. Rows can be created and de… |
| 1.3.6.1.4.1.9.9.597.1.2.4 | ccsQuotaMgrTable | 1 | 23 | Table of quota managers. Columnar objects can be modified when the row is 'active'. Rows can be created and destroyed. Entries ar… |
| 1.3.6.1.4.1.9.9.597.1.2.5 | ccsLoadStatistics | 6 | 90 | None |
| 1.3.6.1.4.1.9.9.597.1.2.7 | ccsBillingPlanStatsTable | 1 | 6 | This table contains the statistics of subscribers for all configured Billing Plans. |