Network Monitor 10.100.37.100 Int#1 Details

Network Monitor

Poll frequency:	`00:05:00`
Last poll:	`1/19/2012 8:36:59 PM`
Network health:	`DEGRADED (1.0%)`

Device Summary << >>

•

•

Suppressed issue

•

?

Device Name		Device IP Address	Manage Device	OSI Services							# of Int	Oper Up	Oper Down	Admin Down	Location	Contact	Avg Daily Packets		Avg Daily Broadcasts		Avg Daily Broadcast Rate		Last Poll Broadcast Rate		Cisco Specific Information			Description	Expiration Date	Contract ID	Contract Phone	SNMP Version	SNMP Reliability	Uptime
Device Name		Device IP Address	Manage Device	1	2	3	4	5	6	7	# of Int	Oper Up	Oper Down	Admin Down	Location	Contact	Tx	Rx	Tx	Rx	Tx	Rx	Tx	Rx	Chassis ID (Serial Number)	Chassis Type	RAM (Bytes)	Description	Expiration Date	Contract ID	Contract Phone	SNMP Version	SNMP Reliability	Uptime
•	`SF SG 40/8`	`10.100.37.100`	Telnet SSH Web HTTPS	•	•	•	•	•	•	•	`1`	`1`	`0`	`0`	San Francisco	ShoreTel	`51,294k`	`36,537k`	`29k`	`335k`	`0.057%`	`0.909%`	`0.495%`	`1.399%`				Device	`12/31/2012`	`RU8-22312`	`800-555-3200`	`SNMPV2C`	`98.41%`	`0 days 19:10:32.47`

Interface Summary << >>

Interface
Number

Peak
Daily
Error
Rate

Peak Daily Utilization

Interface
Speed

Historical
Broadcast
Percent

Last Poll
Broadcast
Percent

Last Poll
Utilization
Percent

X

MTU

Type

Switch interfaces showing
this MAC address

Tx

Rx

Oper

Tx

Rx

Tx

Rx

Tx

Rx

• Int #1 10.100.37.100 0: fei0 0.000% 0.000% 0.000% 100,000,000 Full* none up up 0.057% 0.909% 0.495% 1.399% 0.000% 0.000% • 001049006f60 1500 ethernetCsmacd 0 days 19:10:32.47 Disabled V2POLL64 FastEther Bordeaux→ Int #15 (3) Chiraz→ Int #11 (1)

Interface Utilization

Current Utilization

View Advanced Stats

Hide Advanced Stats

Bits per second

Bits per second

Bits per second

	Tx	Rx
Min	`0 kbps`	`0 kbps`
Avg	`0 kbps`	`0 kbps`
Max	`0 kbps`	`0 kbps`
95th	`0 kbps`	`0 kbps`
95th %	`0.000%`	`0.000%`

Peak packets per second

Peak broadcasts per second

Packet Loss (Errors per polling period)

Interface Traffic

	Packets		Broadcasts		% Broadcasts
	Tx	Rx	Tx	Rx	Tx	Rx
Historical	`52,525,401`	`37,414,175`	`29,747`	`343,337`	`0.057%`	`0.909%`
Last Poll	`201`	`141`	`1`	`2`	`0.495%`	`1.399%`

Interface Errors

Error Counter	Tracked	Type	Errors		Errors per Packet
Error Counter	Tracked	Type	Current	Total	Current	Average
Inbound Unknown Protocols	•	`Common`	`0`	`1,234`	`-`	`0.001%`
Inbound Discards	•	`Rare`	`0`	`1,234`	`-`	`0.001%`
Inbound Errors	•	`Rare`	`0`	`0`	`-`	`-`
Outbound Discards	•	`Rare`	`0`	`1,234`	`-`	`0.001%`
Outbound Errors	•	`Common`	`0`	`0`	`-`	`-`
Outbound Queue Length	•	`Reference`	`0`	`0`	`-`	`-`
Single Collision Frames	•	`Common`	`0`	`0`	`-`	`-`
Multiple Collision Frames	•	`Rare`	`0`	`0`	`-`	`-`
Deferred Transmissions	•	`Common`	`0`	`0`	`-`	`-`
Carrier Sense Errors	•	`Rare`	`0`	`0`	`-`	`-`
Excessive Collisions	•	`Rare`	`0`	`0`	`-`	`-`
Alignment Errors	•	`Rare`	`0`	`0`	`-`	`-`
FCS Errors	•	`Rare`	`0`	`0`	`-`	`-`
SQE Test Errors	•	`Rare`	`0`	`0`	`-`	`-`
Late Collisions	•	`Rare`	`0`	`0`	`-`	`-`
Internal MAC Transmit Errors	•	`Rare`	`0`	`0`	`-`	`-`
Frame Too Longs	•	`Rare`	`0`	`0`	`-`	`-`
MAC Receive Errors	•	`Rare`	`0`	`0`	`-`	`-`
Error Totals			`0`	`2,468`	`0.000%`	`0.003%`

Network Prescription™

Inbound Discards exist on this interface
Inbound packets had to be discarded because of a lack of available packet receive buffers. This can indicate that the device's internal CPU may be unable to process all of the inbound data that it is receiving.
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

Date/Time	Username	Note