Network Monitor 10.0.12.7 Int#24 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
•	`SC_User_SW2`	`10.0.12.7`	Telnet SSH Web HTTPS	•	•	•	•	•	•	•	`58`	`25`	`33`	`7`	SC IT	dlit@cpa2biz.com	`36,148k`	`35,089k`	`67,228k`	`3,928k`	`65.033%`	`10.069%`	`68.203%`	`18.463%`				Device	`-`	`XF-827AZ-212`	`888-555-3415`	`SNMPV2C`	`100.00%`	`106 days 14:21:23.40`

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

Devices connected to
this switch port

Tx

Rx

Oper

Tx

Rx

Tx

Rx

Tx

Rx

• Int #24 24: 24 (Path Solutions) 13.432% 6.736% 32.313% 10,000,000 Half 8 up up 84.982% 0.898% 88.131% 2.395% 0.158% 0.058% • 3c4a92fbc4e8 9216 ethernetCsmacd 106 days 13:50:29.12 Disabled V2POLL64 FastEther VLAN #6: 00-0A-41-5E-AE-A0 (10.0.1.1)

Interface Utilization

Current Utilization

View Advanced Stats

Hide Advanced Stats

Bits per second

Bits per second

Bits per second

	Tx	Rx
Min	`12 kbps`	`5 kbps`
Avg	`17 kbps`	`17 kbps`
Max	`673 kbps`	`3,231 kbps`
95th	`19 kbps`	`11 kbps`
95th %	`0.199%`	`0.114%`

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	`61,342,541`	`56,422,827`	`347,114,491`	`511,413`	`84.982%`	`0.898%`
Last Poll	`623`	`652`	`4,626`	`16`	`88.131%`	`2.395%`

Interface Errors

Error Counter	Tracked	Type	Errors		Errors per Packet
Error Counter	Tracked	Type	Current	Total	Current	Average
Inbound Unknown Protocols	•	`Common`	`0`	`0`	`-`	`-`
Inbound Discards	•	`Rare`	`0`	`0`	`-`	`-`
Inbound Errors	•	`Rare`	`0`	`45`	`-`	`0.000%`
Outbound Discards	•	`Rare`	`0`	`0`	`-`	`-`
Outbound Errors	•	`Common`	`0`	`27`	`-`	`0.000%`
Outbound Queue Length	•	`Reference`	`0`	`0`	`-`	`-`
Single Collision Frames	•	`Common`	`5`	`1,110,732`	`0.085%`	`0.239%`
Multiple Collision Frames	•	`Rare`	`6`	`724,856`	`0.101%`	`0.156%`
Deferred Transmissions	•	`Common`	`0`	`0`	`-`	`-`
Carrier Sense Errors	•	`Rare`	`0`	`0`	`-`	`-`
Excessive Collisions	•	`Rare`	`0`	`27`	`-`	`0.000%`
Alignment Errors	•	`Rare`	`0`	`0`	`-`	`-`
FCS Errors	•	`Rare`	`0`	`6`	`-`	`0.000%`
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			`11`	`1,835,666`	`0.186%`	`0.394%`

Network Prescription™

Interface configured for half-duplex operation
This interface should be configured for full-duplex operation to prevent collisions from occurring and error rates rising.
Collisions exist on this interface
This can be eliminated by configuring the interface and device to work in full-duplex mode. This may not be possible if more than one device is connected to this interface. If this interface is plugged into a single device, then full-duplex may be enabled (providing the network card can recognize full duplex). If this interface has a hub plugged in, then full-duplex operation cannot be enabled.
Excessive Collisions exist on this interface
Excessive collisions should not normally occur on a network segment. This is usually caused be poor wiring or failing hardware (faulty NIC or transceiver). Check all of the devices on this interface.
FCS Errors exist on this interface
FCS Errors can occur when a cable has noise or crosstalk. This may occur continuously if a poor quality cable is used, or intermittently if a network cable is located near an AC power source or heavy machinery that is used infrequently. A cable tester should be deployed on this segment to investigate the exact source of this problem.
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.
Outbound Errors exist on this interface
Packets were discarded because the transmitting machine does not possess enough resources to transmit packets. Check to see how much free memory exists on this device.

Interface Notes

Date/Time	Username	Note