| |
|
Interfaces with peak daily utilization rates greater than 80% or error rate greather than 3% sorted by Comm fail, Error rate, and Utilization
Muscat
192.168.202.50 |
Int #3 |
swp02
- 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.
- 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.
|
40.774% |
0.100% |
0.078% |
Muscat
192.168.202.50 |
Int #13 |
swp12
- 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.
- 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.
|
40.680% |
0.110% |
0.091% |
Router
10.100.36.65 |
Int #7 |
swx 0/3: swx 0/3: Fast Ethernet (BCM53xx)
- Interface configured for half-duplex operation
This interface should be configured for full-duplex operation to prevent collisions from occurring and error rates rising.
- 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.
- Late Collisions exist on this interface
This condition can occur with Ethernet switches that are configured for low-latency forwarding (like Fast-Forwarding or Fragment-Free forwarding) when multiple switches are daisy-chained together. If multiple switches are daisy-chained together, it is recommended that switches be configured for the "store-and-forward" method of forwarding to remedy this error.
- Outbound Errors exist on this interface
Packets were discarded because the transmitting machine does not possess enough resources to transmit packets. Check to see how much free memory exists on this device.
|
15.857% |
0.001% |
0.003% |
Internet
10.100.36.1 |
Int #1 |
Fa0/0: FastEthernet0/0 (WAN side <FG726>)
- Interface configured for half-duplex operation
This interface should be configured for full-duplex operation to prevent collisions from occurring and error rates rising.
- 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.
- Excessive Collisions exist on this interface
Excessive collisions should not normally occur on a network segment. This is usually caused be poor wiring or failing hardware (faulty NIC or transceiver). Check all of the devices on this interface.
- 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.
- Late Collisions exist on this interface
This condition can occur with Ethernet switches that are configured for low-latency forwarding (like Fast-Forwarding or Fragment-Free forwarding) when multiple switches are daisy-chained together. If multiple switches are daisy-chained together, it is recommended that switches be configured for the "store-and-forward" method of forwarding to remedy this error.
- 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.
- 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.
- Outbound Discards exist on this interface
Packets were discarded because the transmitting machine may have run out of outbound packet buffers. This can occur if there is not enough outbound bandwidth available to transmit all requested data. It is suggested that you increase the bandwidth of this link, or increase the number of transmit buffers on this device,
- Outbound Errors exist on this interface
Packets were discarded because the transmitting machine does not possess enough resources to transmit packets. Check to see how much free memory exists on this device.
|
14.462% |
2.045% |
2.901% |
SC_User_SW2
10.0.12.7 |
Int #24 |
24: 24 (Path Solutions)
- Interface configured for half-duplex operation
This interface should be configured for full-duplex operation to prevent collisions from occurring and error rates rising.
- 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.
- Excessive Collisions exist on this interface
Excessive collisions should not normally occur on a network segment. This is usually caused be poor wiring or failing hardware (faulty NIC or transceiver). Check all of the devices on this interface.
- 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.
- Outbound Errors exist on this interface
Packets were discarded because the transmitting machine does not possess enough resources to transmit packets. Check to see how much free memory exists on this device.
|
9.789% |
2.973% |
1.957% |
Chiraz
10.100.37.3 |
Int #11 |
ifc11 (Slot: 1 Port: 11): Nortel Ethernet Switch 470-48T Module - Port 11
- 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 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.
- 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 Discards exist on this interface
Inbound packets had to be discarded because of a lack of available packet receive buffers. This can indicate that the device's internal CPU may be unable to process all of the inbound data that it is receiving.
- 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.
|
3.365% |
0.002% |
0.001% |
| 6 total interfaces listed |
|
|
|
