SwitchMonitor 10.0.1.77 Int#1 Details

SwitchMonitor

Poll frequency:	`00:05:00`
Last poll:	`2/23/2008 5:01:27 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_2 10.0.1.77 Telnet SSH Web Syslog • • • • • • • • 51 22 29 0 Santa Clara, CA Chris Cromer, X4412 47,125k 42,484k 36,538k 2,534k 43.673% 5.630% 57.551% 11.015% FAB0526M22L cat3548xl 16,777,216 Device 10/31/2008 IJ08-3121-00-3208 888-555-1321 SNMPV2C 100.00% 176 days 05:48:33.33

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 #1`	10.0.1.77	VL1: VLAN1	•	`-na-`	`0.030%`	`0.048%`	`10,000,000`	`-`	`up`	`up`	`0.000%`	`66.855%`

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	`1 kbps`	`2 kbps`
Max	`3 kbps`	`4 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
`000653eed800`	`1500`	`ethernetCsmacd`	`176 days 05:47:44.58`	`FAST64POLL`	`FastPoll`

Interface Traffic

	Packets		Broadcasts		% Broadcasts
	Tx	Rx	Tx	Rx	Tx	Rx
Historical	`62,183,527`	`61,867,611`	`0`	`124,791,880`	`0.000%`	`66.855%`
Last Poll	`458`	`457`	`0`	`586`	`0.000%`	`56.184%`

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`	`136`	`-`	`0.000%`
Inbound Errors	`Rare`	`0`	`0`	`-`	`-`
Outbound Discards	`Rare`	`0`	`0`	`-`	`-`
Outbound Errors	`Common`	`0`	`0`	`-`	`-`
Outbound Queue Length	`Reference`	`0`	`64,181`	`-`	`0.026%`
Single Collision Frames	`Common`	`0`	`0`	`-`	`-`
Multiple Collision Frames	`Rare`	`0`	`2,420,744`	`-`	`0.973%`
Deferred Transmissions	`Common`	`0`	`160`	`-`	`0.000%`
Carrier Sense Errors	`Rare`	`0`	`0`	`-`	`-`
Excessive Collisions	`Rare`	`0`	`7,707,256`	`-`	`3.097%`
Alignment Errors	`Rare`	`0`	`0`	`-`	`-`
FCS Errors	`Rare`	`0`	`0`	`-`	`-`
SQE Test Errors	`Rare`	`0`	`0`	`-`	`-`
Late Collisions	`Rare`	`0`	`2,461,984`	`-`	`0.989%`
Internal MAC Transmit Errors	`Rare`	`0`	`0`	`-`	`-`
Frame Too Longs	`Rare`	`0`	`45`	`-`	`0.000%`
MAC Receive Errors	`Rare`	`0`	`0`	`-`	`-`
Error Totals		`0`	`12,590,325`	`0.000%`	`5.060%`

Network Prescription™

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.
Deferred Transmissions exist on this interface
Deferred transmissions are transmissions that could not be sent because the physical medium was busy. If this error occurs frequently, you should consider increasing the bandwidth of this link, or employing full duplex switches to reduce the traffic on this segment.
Late Collisions exist on this interface
This network segment may be too long. This network segment may be too long, or have more than five hubs end to end. The LateCollision count for this interface It is rare to have FCS errors on an interface. A bad or failing NIC or transceiver, faulty wiring, or a bad network card driver may cause this error. If this error just started to occur, investigate what changed on the network recently.
Another source of late collisions can be a switch that is configured for low-latency forwarding. Configure your switches for the "store-and-forward" method of forwarding to remedy this error.
Frame Too Long errors exist on this interface
A Network Card Driver may need to be replaced. Some unusually long frames have been detected on this interface. This may mean that a network card driver may need to be replaced (one device on this segment is sending frames that are too long).
This kind of error can happen when this device does not recognize VLAN tagging, and a device on this segment is transmitting VLAN tags on the end of every frame. If this is the case, try to enable VLAN recognition on this interface, or replace the device with a VLAN aware device.
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.

Interface Notes

Date/Time	Username	Note
10/16/2007 1:46:05 PM	SYSTEM	Interface changed status to UP