McAfee M4050 Troubleshooting Guide - Page 29

Explanation of CatOS show port Command Counters, Counter, Description, Possible Causes

Get McAfee M4050 - Network Security Platform PDF manuals and user guides
UPC - 731944582832
View all McAfee M4050 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

McAfee® Network Security Platform 6.0 Troubleshooting Network Security Platform Counter Alignment Errors FCS Xmit-Err Rcv-Err UnderSize Single Collisions Multiple Collisions Explanation of CatOS show port Command Counters Description Possible Causes Alignment errors are a count of the number of frames received that do not end with an even number of octets and have a bad CRC. These are the result of collisions at half-duplex, duplex mismatch, bad hardware (NIC, cable, or port), or a connected device generating frames that do not end with on an octet and have a bad FCS. FCS error count is the number of frames that were transmitted or received with a bad checksum (CRC value) in the Ethernet frame. These frames are dropped and not propagated onto other ports. These are the result of collisions at half-duplex, duplex mismatch, bad hardware (NIC, cable, or port), or a connected device generating frames with bad FCS. This is an indication that the internal This is an indication of excessive input rates of transmit buffer is full. traffic. This is also an indication of transmit buffer being full. The counter should only increment in situations in which the switch is unable to forward out the port at a desired rate. Situations such as excessive collisions and 10 Mb ports cause the transmit buffer to become full. Increasing speed and moving the link partner to full-duplex should minimize this occurrence. This is an indication that the receive buffer is full. This is an indication of excessive output rates of traffic. This is also an indication of the receive buffer being full. This counter should be zero unless there is excessive traffic through the switch. In some switches, the Out-Lost counter has a direct correlation to the Rcv-Err. These are frames that are smaller than 64 bytes (including FCS) and have a good FCS value. This is an indication of a bad frame generated by the connected device. Single collisions are the number of times the transmitting port had one collision before successfully transmitting the frame to the media. This is an indication of a half-duplex configuration. Multiple collisions are the number of This is an indication of a half-duplex times the transmitting port had more configuration. than one collision before successfully transmitting the frame to the media. 20

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
McAfee® Network Security Platform 6.0
Troubleshooting Network Security Platform
20
Explanation of CatOS show port Command Counters
Counter
Description
Possible Causes
Alignment
Errors
Alignment errors are a count of the
number of frames received that do
not end with an even number of
octets and have a bad CRC.
These are the result of collisions at half-duplex,
duplex mismatch, bad hardware (NIC, cable, or
port), or a connected device generating frames
that do not end with on an octet and have a bad
FCS.
FCS
FCS error count is the number of
frames that were transmitted or
received with a bad checksum
(CRC value) in the Ethernet frame.
These frames are dropped and not
propagated onto other ports.
These are the result of collisions at half-duplex,
duplex mismatch, bad hardware (NIC, cable, or
port), or a connected device generating frames
with bad FCS.
Xmit-Err
This is an indication that the internal
transmit buffer is full.
This is an indication of excessive input rates of
traffic. This is also an indication of transmit
buffer being full. The counter should only
increment in situations in which the switch is
unable to forward out the port at a desired rate.
Situations such as excessive collisions and 10
Mb ports cause the transmit buffer to become
full. Increasing speed and moving the link
partner to full-duplex should minimize this
occurrence.
Rcv-Err
This is an indication that the receive
buffer is full.
This is an indication of excessive output rates of
traffic. This is also an indication of the receive
buffer being full. This counter should be zero
unless there is excessive traffic through the
switch. In some switches, the Out-Lost counter
has a direct correlation to the Rcv-Err.
UnderSize
These are frames that are smaller
than 64 bytes (including FCS) and
have a good FCS value.
This is an indication of a bad frame generated
by the connected device.
Single
Collisions
Single collisions are the number of
times the transmitting port had one
collision before successfully
transmitting the frame to the media.
This is an indication of a half-duplex
configuration.
Multiple
Collisions
Multiple collisions are the number of
times the transmitting port had more
than one collision before
successfully transmitting the frame
to the media.
This is an indication of a half-duplex
configuration.