Cisco Show Ip For Mac Address

IP Accounting is a very useful accounting feature in Cisco IOS, but it’s not as well known as other features, such as NetFlow. The fact that Cisco has considered replacing IP Accounting by adding new features to NetFlow potentially turns IP Accounting into a corner case solution. However, compared to NetFlow, IP Accounting offers some advantages that make it an interesting feature to investigate: easy results retrieval via a MIB and limited resource consumption. Furthermore, access-list accounting currently cannot be solved with the NetFlow implementation. Note that NetFlow recently added the export of the MAC address as a new information element. Refer to coverage of NetFlow Layer 2 and the Security Monitoring Exports feature in Chapter 7, “NetFlow.”

IP Accounting comes in four variations:

  1. IP Accounting MAC Address uses the Cisco IP Statistics MIB to collect incoming and outgoing packets and bytes per MAC address. There is a maximum of 512 entries per physical interface per direction (ingress or egress).
  2. Show mac-address table or show mac-address-table will give you the interface (the given name, not the name you assign it) and MAC Addresses. Some switches/ios versions have a slight variation of the command. That's why I showed it two different ways. It will show multiple MAC addresses on the uplink port that connects to other switches.
  3. First of, I am pretty new to these products. I have an issues in our organization. No MAC addresses or IP addresses appear on ports for cisco devices entered into our NMS. We are using UDT 3.0.2, NCM 7.2.2. Other regions in our organization are not having the same problems with their cisco equipm.
  • Basic IP Accounting, which this book calls “IP Accounting (Layer 3)”
  • IP Accounting Access Control List (ACL)
  • IP Accounting MAC Address
  • IP Accounting Precedence

Note that Cisco documentation is not always consistent for the different IP Accounting features. Therefore, this book uses the command-line interface (CLI) commands as titles, except for “IP Accounting Access Control List,” where the related CLI command is ip accounting access-violations.

To display the Address Resolution Protocol (ARP) table statistics, use the show ip arp command. Displays the ARP table information learned only due to a request for a nonactive Cisco First Hop Redundancy Protocol (FHRP) address. Duration since the switch with a MAC address was mapped to the IP address.

This chapter discusses in detail each flavor of IP Accounting, using a basic structure. First, the fundamentals are explained, followed by an overview of CLI operations, and then SNMP operations. It concludes by comparing the IP Accounting features to the questions raised in Chapter 2, “Data Collection Methodology”:

  • What to collect?
  • Where and how to collect?
  • How to configure?
  • Who is the user?
  • Potential scenarios.

IP Accounting (Layer 3)

IP Accounting (Layer 3) collects the number of bytes and packets processed by the network element on a source and destination IP address basis. Only transit traffic that enters and leaves the router is measured, and only on an outbound basis. Traffic generated by the router or traffic terminating in the router is not included in the accounting statistics. IP Accounting (Layer 3) collects individual IP address details, so it can be used to identify specific users for usage-based billing. To provide the operator with the opportunity of “snapshot” collections in the network, IP Accounting (Layer 3) maintains two accounting databases: an active database and a checkpoint database. The active collection process always updates the active database and therefore constantly increments the counters while packets pass the router. To get a snapshot of the traffic statistics, a CLI command or SNMP request can be executed to copy the current status from the active database to the checkpoint database. This copy request can be automated across the network to be executed at the same time, and a Network Management application can later retrieve the accounting details from the checkpoint database to present consistent accounting data to the operator. The checkpoint database offers a “frozen” snapshot of the complete network. Trying to achieve the same result by synchronously polling entire MIB tables across multiple network elements would introduce some inaccuracies, and hence no real “frozen” snapshots. The collected data can be used for performance and trending applications that require collections at regular intervals. The snapshot function is unique to IP Accounting.

IP Accounting (Layer 3) Principles

The principles of IP Accounting (Layer 3) can be summarized as follows:

  • IP Layer 3 outbound (egress) traffic is collected.
  • Only transit traffic that enters and leaves the router is collected; traffic that is generated by the router or terminated in the router is not included.
  • IP Accounting (Layer 3) also collects IPX traffic. In this case, IPX source and destination addresses are reported instead of IP addresses.
  • Egress MPLS core traffic collection is a new feature.
  • Active and checkpoint databases enable “snapshot” collections.
  • Collection data is accessible via CLI and SNMP; however, the initial configuration must be done via CLI. To retrieve the collection results via SNMP, you need to enable SNMP first. When configuring SNMP, distinguish between read-only access and read-write access. For more details about SNMP configuration, see Chapter 4, “SNMP and MIBs.”
  • The MIB contains only 32-bit SNMP counters.

Supported Devices and IOS Versions

The following list defines the devices and Cisco IOS Software releases that support IP Accounting (Layer 3):

  • IP Accounting (Layer 3) was introduced in IOS 10.0.
  • It is supported on all routers, including Route Switch Module (RSM) and Multilayer Service Feature Card (MSFC), except for the Cisco 12000. Note that IP Accounting cannot account for MLS-switched traffic on the Catalyst 6500/7600, so it collects only a subset of traffic on these platforms.
  • It is supported on all physical interfaces and logical subinterfaces.
  • IP Accounting (Layer 3) runs on the top of all switching paths, except for autonomous switching, silicon switching engine (SSE) switching, and distributed switching (dCEF) on the interface. On the Cisco 7500 router, IP Accounting (Layer 3) causes packets to be switched on the Route Switch Processor (RSP) instead of the Versatile Interface Processor (VIP), which can cause additional performance degradation.

CLI Operations

Notable commands for configuring, verifying, and troubleshooting IP Accounting (Layer 3) are as follows:

  • router(config-if)# ip accounting output-packets

    enables IP Accounting (Layer 3) for output traffic on the interface.

  • router(config)# ip accounting-list [ip address] [ip address mask]

    defines filters to control the hosts for which IP Accounting (Layer 3) information is kept. The filters are similar to an aggregation scheme and can be used to reduce the number of collected records. If filters are applied, details such as number of packets and bytes are kept only for the traffic that matches the filters, while all others are aggregated into “transit records.”

  • router(config)# ip accounting-transitscount

    controls the number of transit records that are stored in the IP Accounting (Layer 3) database. Transit entries are those that do not match any of the filters specified by the global configuration command ip accounting-list. If no filters are defined, no transit entries are possible. The default number of transit records that are stored in the IP Accounting (Layer 3) database is 0.

    Note that the term “transit” in this case refers to packets that are not matched by the filter statements. In the IP Accounting (Layer 3) definition, “transit” refers to packets that traverse the router, compared to traffic that is generated at the router or destined for the router.

  • router(config)# ip accounting-thresholdcount

    sets the maximum number of accounting entries to be created. The accounting threshold defines the maximum number of entries (source and destination address pairs) that are accumulated. The default accounting threshold is 512 entries, which results in a maximum table size of 12,928 bytes. The threshold counter applies to both the active and checkpoint tables.

    The threshold value depends on the traffic mix, because different traffic types create different records for the source and destination address pairs. Whenever the table is full, the new entries (overflows) are not accounted. However, show ip accounting displays the overflows: “Accounting threshold exceeded for X packets and Y bytes.” Alternatively, these values are available in the MIB: actLostPkts (lost IP packets due to memory limitations) and actLostByts (total bytes of lost IP packets). You should monitor the overflows number, at least during the deployment phase, to find the right balance between the number of entries and memory consumption.

  • router# show ip accounting [checkpoint] output-packets

    displays the active accounting or checkpoint database.

  • router# clear ip accounting

    copies the content of the active database to the checkpoint database and clears the active database afterward.

  • router# clear ip accounting checkpoint

    clears the checkpoint database.

SNMP Operations

The OLD-CISCO-IP-MIB has two tables:

  • lipAccountingTable, the active database
  • lipCkAccountingTable, the checkpoint database

The MIB variable actCheckPoint must be read first and then set to the same value that was read to copy the active database into the checkpoint database. After a successful SNMP set request, actCheckPoint is incremented by 1. Setting actCheckPoint is the equivalent of the clear ip accounting CLI command. A Network Management application can retrieve the MIB variable lipCkAccountingTable to analyze stable data in the checkpoint database. There is no SNMP variable to erase the content of the checkpoint database; however, setting actCheckPoint again flushes the checkpoint database and copies the content of the active database.

Details of the IP Accounting MIB (OLD-CISCO-IP-MIB) are as follows:

  • Active database—The lipAccountingTable table contains four relevant components:

    • — actSrc is the active database source.
    • — actDst is the active database destination.
    • — actPkts is the active database packets.
    • — actByts is the active database bytes.

    The table indexes are actSrc and actDst.

  • Checkpoint database—The lipCkAccountingTable table contains four relevant components:

    • — ckactSrc is the checkpoint database source.
    • — ckactdDst is the checkpoint database destination.
    • — ckactPkts is the checkpoint database packets.
    • — ckactByts is the checkpoint database bytes.

    The table indexes are ckactSrc and ckactDst.

  • actCheckPoint MIB variable

Examples (CLI and SNMP)

The following example provides a systematic introduction for configuring and monitoring IP Accounting (Layer 3) and displays the results for both CLI and SNMP.

Initial Configuration

Initially, both the active database (lipAccountingTable) and checkpoint database (lipCkAccountingTable) are empty, as shown from the router CLI and from the SNMP tables.

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

The IP Accounting (Layer 3) configuration is straightforward:

Collection Monitoring

After configuring IP Accounting (Layer 3), the active database populates:

The corresponding MIB table shows the identical entries:

At this point, the checkpoint database is still empty. The active database content is cleared by copying its content to the checkpoint database:

As an alternative, the clear ip accounting mechanism can be mimicked by using the actCheckPoint MIB variable procedure. That means reading the content of the MIB variable and setting it again to the same value that was read:

The two entries just discussed are now in the checkpoint database, but the active database is empty:

Packet Tracer Cisco CLI Commands list

Here is the detailed Cisco router configuration commands list, which can be implemented with packet tracer. Packet tracer is a network simulator used for configuring and creating the virtual cisco devices and network. There are also some other similar software but Cisco IOS output will be same on all simulators.

Related Article: PowerShell vs Command prompt

To configure any device in packet tracer you are required to open or access its CLI. You can do it by clicking any device and then navigating to CLI tab. Once you are at CLI you can perform all Cisco Commands here.

Cisco IOS supports numerous command modes which can be practice with packet tracer, followings are the main command modes of cisco CLI with specific commands to navigate from one mode to other.

ModeSymbolHow to access this modeCommand for leaving this mode
User EXEC ModeRouter >Default mode after booting. Press enter for accessing this.Use exit command
Privileged EXEC modeRouter #Use enable command from user exec mode for entering into this modeexit
Global Configuration modeRouter(config)#Use configure terminal command from privileged exec modeExit or Ctrl+Z for user EXEC mode
Interface ConfigurationRouter(config-if)#Use interface <interface name+number> command from global configuration modeUse exit command to return in global mode
ROMMONROMMON >Enter reload command from privileged exec mode. Press CTRL + C key combination during the first 60 seconds of booting process.Use exit command.

IOS commands are not case sensitive it means that you can use them in uppercase, lowercase, or mixed case, but passwords are case sensitive. Therefore make sure you type it in correctly. In any mode, you can obtain a list of commands available on that mode by entering a question mark (?).

How to Change the Cisco Router name

You can change the cisco router name by using command hostname in global configuration mode.

How to set the Enable password:

You can set the password for protecting enable mode by following command: (Following command will set the password to cisco)

How to set the telnet password on Cisco:

You can access the cisco router remotely by VTY lines, these are the Virtual Terminal lines for access router, you can set password on these line by using the following commands:

Router(config)#line vty 0 4

Router(config-line)#password Cisco

Router(config-line)#no login

Above command will set the telnet password to “Cisco”.

How to set the IP address to Cisco interface:

You can set the IP address to any Cisco device interface by using the following commands:

Router(config)#interface <interface name&number>

Latest version of daz studio. Router(config-if)#ip address <IP address> <subnet mask>

How to enable a port or interface

Router(config-if)#no shut


How to check the IP address of all interfaces:

You can use the “show ip interface brief” command in Privileged EXEC mode for checking the IP address of all interface of Cisco device.

How to save the configurations:

You can use the following command for router configuration to Nvram for use at next boot up

Router#copy running-config startup-config

How to configure the access-list on Cisco:

You can configure the access-list on cisco by using following commands:

Router(config)#Access-list <number> <permit deny> <ip> <mask>

Router(config-if)#ip access-group <number> <in out>


Router(config)#Access-list <number> <permit deny> <protocol> <from ip and mask> <to ip and mask> <port number>



Command Example:

Router(config)#access-list 2 deny

Router(config)#interface fastEthernet 4/0

Router(config-if)#ip access-group 2 in

How to configure the default route on Cisco:

Following command will set the default route to

Router(config)# ip route

How to create a static route on Cisco router

Router(config-router)#ip route [destination_network] [mask] [next-hop_address

you can set a static route by using above command example is also given below:

Router(config-router)#ip route



RIP Configuration Commands
Router(config)#Router ripEnable RIP routing on router.
Router(config-router)#Network <network ip address>Define the network which you want to advertise in RIP. E.g. Network
OSPF Configuration Commands
Router(config)#Router ospf <process-id>Enable OSPF routing on router. Process-id is any number & must be same for all networks in AS.
Router(config-router)#Network < ip address> <wild cardmask>IP address is the IP of network which will be advertise in OSPF and wild card mask will represent the network bits. E.g. network is equilent to
EIGRP configuration Commands
Router(config)#Router eigrp <AS number>AS number is a number must be same for networks which are desired to connect with each other. E.g. Router eigrp 1
Router(config-router)#Network < ip address>Advertise network in EIGRP
Router(config-router)#no auto-summaryDisable auto summay

How to set banner message on Cisco Device:

banner motd <banner start identification> banner message <banner end identification>

Command Example:

banner motd #Unauthorized access to this device is prohibited!#

Above command with set the banner to “Unauthorized access to this device is prohibited”

Famous Show Commands in Privileged EXEC Mode

You can run all these command for checking different setting of Cisco device in privileged EXEC mode:

Show Version

Show running-config

Show Vlan

Show mac-address-table

Show clock

Show privilege

Show interface <interface name>
show ip route

Show controllers

show cdp neighbors

Show memory

Show protocols

Show startup-config

Show Flash

Show spanning-tree

Verifying Commands for Network Connectivity

You can use these commands to verify network connectivity for your router

router# enable

router# ping [ip-address hostname]

Command Example:

router# ping

Cisco Show Ip Address

(A reply response from host will verify the connectivity)

How to telnet any host:

Cisco Show Ip For Mac Address Windows 10

telnet {ip-address hostname}

Find Ip From Mac Cisco

e.g. router# telnet

Show Mac Address Cisco Router

Related Article: NMAP Commands Linux

Comments are closed.