SwitchMonitor 10.100.36.1 Int#2 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)

• Internet 10.100.36.1 Telnet SSH Web Syslog • • • • • • • • 2 2 0 0 San Francisco, CA Tim Titus x4413 528k 505k 65k 220k 11.048% 30.423% 17.626% 37.844% JAD0626CGJC (3208410732) c2621 62,914,560 Device 12/31/2007 KR07-8718-12-7301 888-555-1321 SNMPV2C 100.00% 217 days 11:53:06.52

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`	10.100.36.1	Fa0/1: FastEthernet0/1	•	`0.340%`	`0.123%`	`0.088%`	`100,000,000`	`Half`	`up`	`up`	`16.501%`	`5.921%`

HSRP Details

Group	State	Priority	Preempt	Virtual IP	Virtual MAC	Active IP
`1`	Initial	`110`	`TRUE`	`10.100.36.2`	`00-00-0C-07-AC-01`	`10.100.36.1`
`2`	Initial	`100`	`FALSE`	`10.100.36.3`	`00-00-0C-07-AC-02`	`10.100.36.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	`7 kbps`	`4 kbps`
Max	`122 kbps`	`88 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
`000a415eaea1`	`1500`	`ethernetCsmacd`	`13 days 21:38:36.18`	`FAST64POLL`	`FastPoll`

Interface Traffic

	Packets		Broadcasts		% Broadcasts
	Tx	Rx	Tx	Rx	Tx	Rx
Historical	`68,568,738`	`65,316,087`	`13,550,532`	`4,110,762`	`16.501%`	`5.921%`
Last Poll	`669`	`605`	`228`	`66`	`25.418%`	`9.836%`

Interface Errors

Error Counter	Type	Errors		Errors per Packet
Error Counter	Type	Current	Total	Current	Average
Inbound Unknown Protocols	`Common`	`0`	`144`	`-`	`0.000%`
Inbound Discards	`Rare`	`0`	`0`	`-`	`-`
Inbound Errors	`Rare`	`0`	`0`	`-`	`-`
Outbound Discards	`Rare`	`0`	`0`	`-`	`-`
Outbound Errors	`Common`	`0`	`0`	`-`	`-`
Outbound Queue Length	`Reference`	`0`	`0`	`-`	`-`
Single Collision Frames	`Common`	`0`	`5,602`	`-`	`0.004%`
Multiple Collision Frames	`Rare`	`3`	`4,362`	`0.191%`	`0.003%`
Deferred Transmissions	`Common`	`0`	`74,959`	`-`	`0.049%`
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		`3`	`85,067`	`0.191%`	`0.056%`

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.
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.
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.

Interface Notes

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