| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| • |
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 |
0 kbps |
0 kbps |
| Max |
0 kbps |
0 kbps |
|
|
|
|
|
Interface Details
Interface Traffic
|
|
15,443,092 |
13,602,463 |
13,721,372 |
10,958 |
47.048% |
0.080% |
0 |
0 |
0 |
0 |
0.000% |
0.000% |
Interface Errors
Common |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
178,595 |
- |
0.417% |
Rare |
0 |
0 |
- |
- |
Common |
0 |
0 |
- |
- |
Reference |
0 |
0 |
- |
- |
Common |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Common |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
6,259 |
- |
0.015% |
Rare |
0 |
158,894 |
- |
0.371% |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
Rare |
0 |
0 |
- |
- |
0 |
343,748 |
0.000% |
0.804% |
- 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.
|
| 10/16/2007 1:46:05 PM |
SYSTEM |
Interface changed status to DOWN |
|
|
|