Using the New Interface History Feature
VERSION 1
The “history” command is new with 15.1T. This, along with the new “show interface history” command, allows an interface to maintain utilization history in a graphical format similar to CPU history.
This history can be maintained as either packets per second (pps) or bit per second (bps). Along with the rate, the user can monitor the many/various interface counters. As with CPU history, there are graphs for the last 60 seconds, last 60 minutes and last 72 hours. Separate graphs are maintained for input and output. This is a total of 6 graphs.
This allows the Technical Assistance Center (TAC) to be able to look back in time at the interface(s) in question and see rates and counters. Problems in the network can then be investigated and determined if they relate to an interface and the counter(s) that are being incremented at that time interval.
The show interface history command allows a display of all 6 graphs or only a subset based on needs:
show interface [type number] history [all | 60sec | 60min | 72hour] [both | input |
output] Syntax Description
type
(Optional) Interface type.
number
(Optional) Port number of the interface.
all
(Optional) Specifies the histograms representing the last 60 seconds, the last 60 minutes, and the last 72 hours of interface utilization.
60sec
(Optional) Specifies the histograms representing the last 60 seconds of interface utilization.
60min
(Optional) Specifies the histograms representing the last 60 minutes of interface utilization.
72hour
(Optional) Specifies the histograms representing the last 72 hours of interface utilization.
both
(Optional) Specifies both the input histograms and the output histograms.
input
(Optional) Specifies the input histograms.
output
(Optional) Specifies the output histograms.
Example:
The following was configured under gigabitethernet 0/1:
history BPS input-drops output-drops unknown-protocol-drops multicast
Router# show interface gigabitethernet 0/1 history 60min
5689688755455324777665666876546
10
9 *
8 ** ** *
7 *# ##* *** #*
6 *###### ####* **###* *
5 ########## *# ############* *
4 ############# *#############**
3 ############## ###############*
2 ###############################
1 ###############################
0….5….1….1….2….2….3….3….4….4….5….5….6
0 5 0 5 0 5 0 5 0 5 0
3333333333333333333333333333331
Mlcst 556555555565555555555565535555700000000000000000000000000000
22322111111 121221211211
57149774766867 133175814422022
iDrop 425727636924219265454496840996600000000000000000000000000000
GigabitEthernet0/1 input rate(mbits/sec) (last 60 minutes)
* = maximum # = average
5677678656555434767665666866545
10
9
8 * *
7 ** *# * * *
6 *#####* * ##*** ***##*
5 *#########*** #####*######* *
4 #############* *#############**
3 #############**###############*
2 ###############################
1 ###############################
0….5….1….1….2….2….3….3….4….4….5….5….6
0 5 0 5 0 5 0 5 0 5 0
Unkno 000000000000000000000000000000000000000000000000000000000000
oDrop 000000000000000000000000000000000000000000000000000000000000
GigabitEthernet0/1 output rate(mbits/sec) (last 60 minutes)
* = maximum # = average
Explanation of the above:
The input rate histogram shows that the input rate peaked at 9 Mbps at 4 minutes prior to the command execution. During that one-minute interval, there were 35 input multicast packets and 247 input drops. The counter values in the histogram should be read vertically.
The output rate histogram shows that the output rate reached 8 Mbps twice; once 7 minutes prior and the second time 26 minutes prior to the command execution. There were no unknown protocol drops and no output drops during the last 60 minutes.
show interfaces history *is* included in the show tech-support. So if it’s configured you will get the output in the show tech.
