SwitchMonitor
Poll frequency: 00:05:00
Last poll: 2/23/2008 5:01:27 PM
Network health: DEGRADED (3.2%)
 Map 
 Device List 
 Favorites 
 Issues 
 Health 
 Top-10 
 Interfaces 
 Tools 

     
Device Summary << >>
?
General
Traffic
Inventory
Support
Uptime
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
1 2 3 4 5 6 7 Tx Rx Tx Rx Tx Rx Tx Rx 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
Number
IP
Address
Description H Peak
Daily
Error
Rate
Peak Daily Utilization Interface
Speed
Duplex* Status % Broadcasts
Tx Rx Admin Oper Tx Rx
Int #49
 Fa0/48: FastEthernet0/48 0.000% 0.355% 0.114% 100,000,000 Full* up up 59.931% 0.209%
Interface Utilization
Current Utilization
Download Excel
 Daily 
 Weekly 
 Monthly 
 Yearly 

     
 Bits per second 
Percent
Peak Percent
Tx Rx
Min 0 kbps 0 kbps
Avg 35 kbps 1 kbps
Max 354 kbps 113 kbps
     

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 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
Add Note
Date/Time Username Note
 10/16/2007 1:46:05 PM  SYSTEM  Interface changed status to UP