Last input: Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.
Last Output: Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.
Great, thanks for your input (to both of the repliers).
Now for another question related to this.
I'm wondering if there's any sort of utility that could use that data to show inactive ports over a series of switches.
For example, we have about 20 switches deployed. Is there some utility that I could use that would analyze all switches and show what ports haven't seen any activity for x number of hours/days/weeks, etc? I'm fairly certain that we have a number of ports out there that are hooked up, but not required.
I'd prefer to do it without getting into an elaborate SNMP thing. I do however have CW2K v2.0 if that'd somehow work?
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...