| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| • |
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 |
| |
|
 |
 |
 |
|
|
Tx |
Rx |
| Min |
0 kbps |
0 kbps |
| Avg |
14 kbps |
3 kbps |
| Max |
244 kbps |
57 kbps |
|
|
|
|
|
Interface Details
Interface Traffic
|
|
259,297,696 |
227,968,030 |
327,171,903 |
3,942,560 |
55.787% |
1.700% |
690 |
471 |
1,404 |
17 |
67.049% |
3.484% |
Interface Errors
Common |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
21,959 |
- |
0.003% |
Rare |
0 |
0 |
- |
- |
Common |
0 |
0 |
- |
- |
Reference |
0 |
0 |
- |
- |
Common |
0 |
146,258 |
- |
0.018% |
Rare |
0 |
106,480 |
- |
0.013% |
Common |
5 |
2,177,151 |
0.194% |
0.266% |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
5 |
2,451,848 |
0.194% |
0.300% |
- 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 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.
|
| 10/16/2007 1:46:05 PM |
SYSTEM |
Interface changed status to UP |
|
|
|