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.
if tow routers advertise the same prefix to each other, which router is selected to advertise first ? Router1 and Router2 advertise 192.168.1.0/24 to each other, which one will advertise it? Can I control it ? thanks !!
Hi All,Looking for any ideas on this issue i'm currently having. It is very similar to this issues here: https://community.cisco.com/t5/small-business-switches/help-me-to-create-ipv4-based-acls-for-vlans-using-gui/td-p/2645142 I tho...
As I know, VXLAN uses OSPF for its underlay. However, it seems BGP is involved in the underlay, but I cannot figure out the purpose. A VTEP encapsulates a packet, and if OSPF is deployed, every device should be able to route the packet to another VTE...
I use two L3 switches for connecting two sites on MPLS. Each switch has a GE port configured as routed interface connecting to a CE from the provider. OSPF routing appears to be working. Endpoint computers of one location can see those o...