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
(Optional) Interface type.
(Optional) Port number of the interface.
(Optional) Specifies the histograms representing the last 60 seconds, the last 60 minutes, and the last 72 hours of interface utilization.
(Optional) Specifies the histograms representing the last 60 seconds of interface utilization.
(Optional) Specifies the histograms representing the last 60 minutes of interface utilization.
(Optional) Specifies the histograms representing the last 72 hours of interface utilization.
(Optional) Specifies both the input histograms and the output histograms.
(Optional) Specifies the input histograms.
(Optional) Specifies the output histograms.
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
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.
Hi All, I have had a few issues with my Packet tracer network recently. The main one being I have finally been able to ping through my firewall to my corp lan but cant ping from the corp lan back to the switches below. The next main issue ...
I have two WAN lines, one internet line 30 Mbps and the other is WAN line connected to the branch with 20 Mbps:My question is which is better to support this bandwidth and better throughput: CISCO router 888/k9, or, CISCO router 2911/k9
I am trying to ping my isp ip address (aka loopback 1) and loopback 10 to PC1 and PC2. Whenever I ping both ip addresses and default gateway from pc1 to pc2 it works. However, when I'm trying to ping my isp ip addresss (220.127.116.11) and loopback 10 ip address...
Hi! I need some help understanding EIGRP feasible distance calculation. To reach the 10.10.11.0 network from R4, the feasible distance is 5120. R4 reports its feasible distance to R3.... R3 has now a reported distance of 5120 to reach the 10.10...
Good day all, Migrating an ASA5505 to 5506 and am attempting to replicate the below high level setup but the logic of 'You cannot assign the same VLAN to multiple subinterfaces' is causing problems. My ASA5505 is trunked to a switch and trunked to an...