Home > Articles > Networking > Network Administration & Management

This chapter is from the book

IP Accounting Precedence

The IP Accounting Precedence feature provides IP precedence-related traffic accounting information. The collection per interface consists of the total number of packets and bytes for each of the eight IP Precedence values, separately per direction (send and receive).

IP Accounting Precedence does not collect individual IP or MAC addresses, so it cannot be used to identify a specific user for usage-based billing, except in cases where the (sub)interface can serve as user identifier. There is no concept of a checkpoint database. Regarding QoS operations, it is important to distinguish between ingress and egress traffic on an interface:

  • For incoming packets on the interface, the accounting statistics are gathered before input CAR/Distributed CAR (DCAR) is performed on the packet. Therefore, if CAR/DCAR changes the precedence on the packet, it is counted based on the old precedence setting with the show interface precedence command.
  • For outgoing packets on the interface, the accounting statistics are gathered after output features such as DCAR, Distributed Weighted Random Early Detection (DWRED), and Distributed Weighted Fair Queuing (DWFQ) are performed on the packet.

IP Accounting Precedence Principles

The principles of IP Accounting Precedence can be summarized as follows:

  • Both inbound and outbound traffic is collected for eight IP precedence classes.
  • IP Accounting Precedence is supported on physical interfaces and subinterfaces.
  • There is no concept of a checkpoint database.
  • Individual IP or MAC addresses are not collected.
  • Collection data is accessible via CLI and SNMP. However, all configuration changes need to be done via CLI, because the CISCO-IP-STAT-MIB has no read-write parameters.
  • The MIB contains 32-bit and 64-bit SNMP counters.
  • To retrieve the collection results via SNMP, you have to enable SNMP on the network element first. When configuring SNMP, distinguish between read-only access and read-write access. For more details about SNMP configuration, see Chapter 4.

Supported Devices and IOS Versions

The following list defines the devices and Cisco IOS Software releases that support IP Accounting Precedence:

  • IP Accounting Precedence was introduced in IOS 11.1CC.
  • It is supported on CEF, dCEF, and optimum switching.
  • It supports Virtual Routing and Forwarding (VRF) interfaces but does not support tunnel interfaces.
  • It is supported on all routers, including the RSM and MSFC, except for the Cisco 12000.

CLI Operations

Notable commands for configuring, verifying, and troubleshooting IP Accounting Precedence are as follows:

  • router(config-if)# ip accounting precedence {input | output}, where:
    • input performs accounting based on IP precedence on received packets.
    • output performs accounting based on IP precedence on transmitted packets.
  • router# show interface [type number] precedence

    displays information for all interfaces configured for IP Accounting Precedence. To display information for a single interface, enter the appropriate values for the type number arguments.

  • router# clear counters [interface-type interface-number]

    clears interface counters. Because the IP Accounting Precedence entries are stored per interface, the clear counters command clears all IP Accounting Precedence entries. Note that this function is different from the IP Accounting MAC Address feature. The clear counters command does not delete the content of the cipPrecedenceTable MIB table. An analogy would be the clear counters command that clears the number of bytes and packets in the output of show interface while the SNMP counters in the ifTable are not cleared. Note also that the clear counters command is applicable globally for all interfaces or for a single interface.

SNMP Operations

IP Accounting Precedence can be configured only by using the CLI. Collection data can be read but not deleted via SNMP. It can be deleted using the CLI command clear counters. CISCO-IP-STAT-MIB supports 32-bit and 64-bit counters.

The IP Accounting Precedence part of the MIB consists of two tables with separate 32-bit counters and 64-bit counters:

  • cipPrecedenceTable—The 32-bit counter table for IP Accounting Precedence contains four variables:

    • cipPrecedenceDirection is the object’s data source (incoming or outgoing traffic).
    • cipPrecedenceIpPrecedence is the IP precedence value this object is collected on, with a total of eight different precedence values (0 to 7).
    • cipPrecedenceSwitchedPkts is the number of packets per IP precedence value (cipPrecedenceIpPrecedence).
    • cipPrecedenceSwitchedBytes is the number of bytes per IP precedence value (cipPrecedenceIpPrecedence).

    The indexes of the three tables are ifIndex, cipPrecedenceDirection, and cipPrecedenceIpPrecedence

  • cipPrecedenceXTable—The 64-bit counter extension table for IP Accounting Precedence contains two variables:

    • cipPrecedenceHCSwitchedPkts is the number of packets per IP precedence value (cipPrecedenceIpPrecedence). This object is the 64-bit version of cipPrecedenceSwitchedPkts.
    • cipPrecedenceHCSwitchedBytes is the number of bytes per IP precedence value (cipPrecedenceIpPrecedence). This object is the 64-bit version of cipPrecedenceSwitchedBytes.

    The three table indexes are ifIndex, cipPrecedenceDirection, and cipPrecedenceIpPrecedence.

Examples (CLI and SNMP)

The following example provides a systematic introduction to configuring and monitoring IP Accounting Precedence and displays the results for both CLI and SNMP.

Initial Configuration

Initially, there are no IP Accounting Precedence entries.

In this configuration, both IP Accounting Precedence input and output are enabled:

router(config-if)#interface serial 0/0
router(config-if)#ip accounting precedence input
router(config-if)#ip accounting precedence output
router(config-if)#exit

Collection Monitoring

The entries populate:

router#show interfaces precedence
Serial0/0
  Input
            Precedence 6:    8 packets, 467 bytes
  Output
            Precedence 0:    6 packets, 504 bytes
            Precedence 6:    11 packets, 863 bytes

The corresponding MIB table shows the identical entries.

The router is accessed with SNMP2c (SNMP version 2c), the read community string is public, and the SNMP tool net-snmp is used:

SERVER % snmpwalk -c public -v 2c <router> cipPrecedenceTable
cipPrecedenceSwitchedPkts.1.input.0 = Counter32: 0
cipPrecedenceSwitchedPkts.1.input.1 = Counter32: 0
cipPrecedenceSwitchedPkts.1.input.2 = Counter32: 0
cipPrecedenceSwitchedPkts.1.input.3 = Counter32: 0
cipPrecedenceSwitchedPkts.1.input.4 = Counter32: 0
cipPrecedenceSwitchedPkts.1.input.5 = Counter32: 0
cipPrecedenceSwitchedPkts.1.input.6 = Counter32: 8
cipPrecedenceSwitchedPkts.1.input.7 = Counter32: 0
cipPrecedenceSwitchedPkts.1.output.0 = Counter32: 6
cipPrecedenceSwitchedPkts.1.output.1 = Counter32: 0
cipPrecedenceSwitchedPkts.1.output.2 = Counter32: 0
cipPrecedenceSwitchedPkts.1.output.3 = Counter32: 0
cipPrecedenceSwitchedPkts.1.output.4 = Counter32: 0
cipPrecedenceSwitchedPkts.1.output.5 = Counter32: 0
cipPrecedenceSwitchedPkts.1.output.6 = Counter32: 11
cipPrecedenceSwitchedPkts.1.output.7 = Counter32: 0
cipPrecedenceSwitchedBytes.1.input.0 = Counter32: 0
cipPrecedenceSwitchedBytes.1.input.1 = Counter32: 0
cipPrecedenceSwitchedBytes.1.input.2 = Counter32: 0
cipPrecedenceSwitchedBytes.1.input.3 = Counter32: 0
cipPrecedenceSwitchedBytes.1.input.4 = Counter32: 0
cipPrecedenceSwitchedBytes.1.input.5 = Counter32: 0
cipPrecedenceSwitchedBytes.1.input.6 = Counter32: 467
cipPrecedenceSwitchedBytes.1.input.7 = Counter32: 0
cipPrecedenceSwitchedBytes.1.output.0 = Counter32: 504
cipPrecedenceSwitchedBytes.1.output.1 = Counter32: 0
cipPrecedenceSwitchedBytes.1.output.2 = Counter32: 0
cipPrecedenceSwitchedBytes.1.output.3 = Counter32: 0
cipPrecedenceSwitchedBytes.1.output.4 = Counter32: 0
cipPrecedenceSwitchedBytes.1.output.5 = Counter32: 0
cipPrecedenceSwitchedBytes.1.output.6 = Counter32: 863
cipPrecedenceSwitchedBytes.1.output.7 = Counter32: 0

The table indexes are as follows:

  • ifIndex

    In this case it is 1, which represents serial 0/0:

    Router #show snmp mib ifmib ifIndex serial 0/0
              Interface = Serial0/0, ifIndex = 1
    
  • cipPrecedenceDirection: input or output
  • cipPrecedenceIpPrecedence: a value from 0 to 7

For example, the entry (Input, Precedence 6, 8 packets, 467 bytes) is represented in the SNMP table by

cipPrecedenceSwitchedBytes.1.input.6 = Counter32: 467

In a situation where the counters are small, polling cipPrecedenceXTable, which contains the high-capacity counter counter64, returns the same results as polling cipPrecedenceTable.

Finally, the IP Accounting Precedence counters can be cleared, either specifically for the interface or globally for all interfaces:

router(config)#clear counters [serial 0/0]
router#show interfaces precedence
Serial0/0
  Input
           none
        Output
           none

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020