Network Monitor
Poll frequency: 00:05:00
Last poll: 1/19/2012 8:36:59 PM
Network health: DEGRADED (1.0%)
 Map 
 Device List 
 Favorites 
 NetFlow 
 Issues 
 Health 
 Top-10 
 WAN 
 Interfaces 
 Tools 

     
Device Summary << >>
?
General
Traffic
Inventory
Support
Uptime
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
1 2 3 4 5 6 7 Tx Rx Tx Rx Tx Rx Tx Rx Chassis ID
(Serial Number)
Chassis Type RAM
(Bytes)
Muscat 192.168.202.50 Telnet SSH Web HTTPS 26 3 23 0  Santa Clara, CA  Tim Titus 529k 336k 0 147k 0.000% 30.418% 0.000% 29.055%       Device 11/31/2012 480-2381-21A 888-555-8000 SNMPV2C 99.88% 370 days 14:15:31.00

General
Traffic
Details
Poll
Connected
Interface
Number
IP
Address
Description Peak
Daily
Error
Rate
Peak Daily Utilization Interface
Speed
Duplex* Port
VLAN
ID
Status Historical
Broadcast
Percent
Last Poll
Broadcast
Percent
Last Poll
Utilization
Percent
X Queue
Type
MAC Address MTU Type Last Changed Netflow Poll Type
Update

 Devices connected to
this switch port 
Tx Rx Admin Oper Tx Rx Tx Rx Tx Rx MIB-II DetailPoll
Int #13
 swp12 40.266% 0.106% 0.088% 10,000,000 Full 1 up up 0.000% 2.599% 0.000% 2.005% 0.079% 0.062%
001349a44e06 1500 ethernetCsmacd 370 days 13:12:21.00  Disabled V2POLL64 FastEther VLAN #0: 00-60-47-4F-63-54 (192.168.202.1)
Interface Utilization
Current Utilization
Download Excel
 Daily 
 Weekly 
 Monthly 
 Yearly 

     
 Bits per second 
Percent
Peak Percent
Tx Rx
Min 5 kbps 4 kbps
Avg 6 kbps 4 kbps
Max 10 kbps 8 kbps
95th 9 kbps 7 kbps
95th % 0.093% 0.076%
     

Network Prescription™
  • 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.
Interface Notes
Add Note
Date/Time Username Note
 1/16/2011 6:27:51 PM  SYSTEM  Interface changed status to UP