SwitchMonitor 10.100.36.60 Int#2 Details

• Denver 10.100.36.60 Telnet SSH Web Syslog • • • • • • • • 2 2 0 0 Denver, CO Tim Titus x4413 668k 668k 17k 25k 2.501% 3.701% 4.812% 7.264% 12027437 c1601 16,777,216 Device - 127-726-321UV56 650-555-8710 SNMPV2C 100.00% 232 days 02:19:08.84

Interface Summary << >>

Interface Number		IP Address	Description	H	Peak Daily Error Rate	Peak Daily Utilization		Interface Speed	Duplex*	Status		% Broadcasts
Interface Number		IP Address	Description	H	Peak Daily Error Rate	Tx	Rx	Interface Speed	Duplex*	Admin	Oper	Tx	Rx
•	`Int #2`	192.168.201.1	Se0: Serial0	•	`13.113%`	`67.563%`	`68.042%`	`128,000`	`-`	`up`	`up`	`3.089%`	`2.918%`

Interface Utilization

Current Utilization

Download Excel

View Advanced Stats

Hide Advanced Stats

	Tx	Rx
Min	`0 kbps`	`0 kbps`
Avg	`14 kbps`	`15 kbps`
Max	`122 kbps`	`122 kbps`

Peak packets per second

Peak broadcasts per second

Packet Loss (Errors per polling period)

Interface Details

MAC Address	MTU	Type	Last Changed	Poll Type
MAC Address	MTU	Type	Last Changed	MIB-II
	`1500`	`propPointToPointSerial`	`103 days 02:56:16.95`	`FAST64POLL`

Interface Traffic

	Packets		Broadcasts		% Broadcasts
	Tx	Rx	Tx	Rx	Tx	Rx
Historical	`73,270,798`	`77,785,249`	`2,335,804`	`2,337,783`	`3.089%`	`2.918%`
Last Poll	`486`	`554`	`35`	`35`	`6.718%`	`5.942%`

Interface Errors

Error Counter	Type	Errors		Errors per Packet
Error Counter	Type	Current	Total	Current	Average
Inbound Unknown Protocols	`Common`	`0`	`4`	`-`	`0.000%`
Inbound Discards	`Rare`	`0`	`0`	`-`	`-`
Inbound Errors	`Rare`	`0`	`3`	`-`	`0.000%`
Outbound Discards	`Rare`	`0`	`2,089,557`	`-`	`1.342%`
Outbound Errors	`Common`	`0`	`0`	`-`	`-`
Outbound Queue Length	`Reference`	`0`	`0`	`-`	`-`
Error Totals		`0`	`2,089,564`	`0.000%`	`1.342%`

Network Prescription™

Inbound Errors exist on this interface
Inbound errors are packets that are mal-formed, but are enclosed in a valid frame. This can be caused by a bad NIC driver or protocol driver on the sending device. To track down this error, you will need to connect a packet analyzer in front of this interface to capture the actual mal-formed packet to determine which device is at fault.
Inbound Unknown Protocols exist on this interface
This interface received a valid frame with a protocol that was unrecognized. (Example: If AppleTalk is configured on two devices, and these two devices send AppleTalk broadcasts to each other, all other devices on the network will also receive the broadcast frames. These devices will not know what to do with the AppleTalk packets and will discard them.) If you encounter a lot of Inbound Unknown Protocols on an interface, you should consider setting up VLANs and separating devices that don't need to communicate via other protocols. Broadcasts can steal CPU attention on a machine (each broadcast generates a system interrupt and requires the CPU to evaluate the frame). If your network is saturated with many protocols, up to 5% of your computer's CPU cycles can be dedicated to processing and discarding these broadcast packets.
Outbound Discards exist on this interface
Packets were discarded because the transmitting machine may have run out of outbound packet buffers. This can occur if there is not enough outbound bandwidth available to transmit all requested data. It is suggested that you increase the bandwidth of this link, or increase the number of transmit buffers on this device,

Interface Notes

Add Note

Date/Time	Username	Note
1/7/2007 6:44:58 PM	SYSTEM	Interface changed status to DOWN
1/7/2007 6:49:59 PM	SYSTEM	Interface changed status to UP
10/16/2007 1:46:06 PM	SYSTEM	Interface changed status to UP