SwitchMonitor 10.0.1.76 Int#5 Details

SwitchMonitor

Poll frequency:	`00:05:00`
Last poll:	`2/23/2008 5:06:33 PM`
Network health:	`DEGRADED (3.2%)`

Device Summary << >>

•

•

Suppressed issue

•

?

Device
Name

Managed
IP Address

Manage
Device

OSI Services

H

# 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

Download Excel

Description

Expiration
Date

Contract
ID

Contract
Phone

SNMP
Version

SNMP
Reliability

Uptime

Chassis ID
(Serial Number)

Chassis Type

RAM
(Bytes)

• SC_UserSwitch_1 10.0.1.76 Telnet SSH Web Syslog • • • • • • • • 51 34 17 0 Santa Clara, CA Chris Cromer X4412 97,360k 88,188k 53,009k 2,579k 35.253% 2.842% 50.064% 5.257% FAB0525V1DP cat3548xl 16,777,216 Device 12/31/2007 KR07-8718-12-7301 888-555-1321 SNMPV2C 100.00% 176 days 05:43:09.24

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 #5`		Fa0/4: FastEthernet0/4	•	`10.461%`	`0.937%`	`0.021%`	`100,000,000`	`Full*`	`up`	`up`	`81.778%`	`0.563%`

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	`18 kbps`	`0 kbps`
Max	`1,620 kbps`	`28 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	EtherStats
`00065388acc4`	`1500`	`ethernetCsmacd`	`128 days 01:42:46.11`	`FAST64POLL`	`FastPoll`

Interface Traffic

	Packets		Broadcasts		% Broadcasts
	Tx	Rx	Tx	Rx	Tx	Rx
Historical	`44,517,406`	`9,179,062`	`199,792,289`	`51,984`	`81.778%`	`0.563%`
Last Poll	`262`	`35`	`1,434`	`0`	`84.552%`	`0.000%`

Interface Errors

Error Counter	Type	Errors		Errors per Packet
Error Counter	Type	Current	Total	Current	Average
Inbound Unknown Protocols	`Common`	`0`	`0`	`-`	`-`
Inbound Discards	`Rare`	`0`	`381`	`-`	`0.000%`
Inbound Errors	`Rare`	`0`	`521,945`	`-`	`0.206%`
Outbound Discards	`Rare`	`0`	`0`	`-`	`-`
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`	`90,599`	`-`	`0.036%`
FCS Errors	`Rare`	`0`	`94,223`	`-`	`0.037%`
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`	`381`	`-`	`0.000%`
Error Totals		`0`	`707,529`	`0.000%`	`0.279%`

Network Prescription™

Alignment errors exist on this interface
There may be a Duplex problem on this interface. It appears that this interface is configured for full duplex. Alignment errors were detected with no collisions. There should be only one device connected to the other end of this interface, and that device should also be configured for full duplex. Note: Full duplex connections cannot function properly with a hub. If you need to use a hub, configure this interface for half-duplex. If there is no duplex problem on this interface, there may be a software driver problem. Check to see if all machines can communicate successfully on this segment.
FCS Errors exist on this interface
FCS Errors can be caused by a duplex mismatch on an interface. You should check the duplex settings on this device as well as the device this interface is connected.
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 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.

Interface Notes

Date/Time	Username	Note
1/19/2007 11:07:08 AM	SYSTEM	Interface changed status to UP
1/19/2007 3:52:34 PM	SYSTEM	Interface changed status to DOWN
3/8/2007 2:21:43 PM	SYSTEM	Interface changed status to UP
10/16/2007 1:46:04 PM	SYSTEM	Interface changed status to UP