VoIP PBX Carroll Communications is an authorized Avaya business partner
  IP Office Platform
  Carroll Communications Home
  Avaya IP Office 500
  IP Office 406 r2
  IP Office 412
  Avaya IP Office Telephones
  Avaya Voice Mail Pro
  Phone Manager Pro
  IP Office Manager
  IP Office Soft Console
  Avaya Conferencing Center
  Compact Business Center
  Short Codes
  Avaya Data Networking
  IP Office Expansion Modules
  IP Office Licenses
  Centrales Telefonicas
  Voice over IP Phone Systems
  IP Office 403

Business VoIP PBX
Telecommunications Consulting
Phone Locale Settings
IP Office Tek Tips
Phone System Quote
 
Panasonic Headsets
Tek Tips 100-200
IP Office telephone systems
about us | phone equipment | voip solutions | avaya partner acs telephone systems | site map | contact us

Avaya IP Office

The Avaya IP Office platform is the ultimate in converged voice and data technology. IP Office brings a combination of voice and data applications formerly reserved for only the largest corporations. Cutting edge customer service with easy to use tools is now available to the smallest of businesses.

Avaya IP Office Technical Tips
 
732-280-3200
   

EMEA IP Office Technical Tip
056: How to decode SysMon generated “FEC::ReceiverError”
messages
*Release Date: 1 March 2005

This Technical Tip has been raised in response to numerous requests into the Tier3 organisation asking what the “FEC::ReceiverError” messages mean and how to decode the associated error number provided.

The FEC (Fast Ethernet Controller device) controls data that is to be sent/received to/from the IP Office and the Local Area Network (LAN). All FEC errors are therefore related to problems on the LAN.

The FEC Receiver Error message is output to the SysMonitor screen/log and is output when the Trace Options -> System -> Print option is enabled (refer to the SysMonitor screenshot below).

Note that the System -> Print option is enabled when Default Tracing is set (i.e. when the application is first installed and when the “Default All” button is selected.)

Please also note that the information contained within this Technical Tip will be incorporated into the next release of IP Office System Monitor Documentation, when it will also be added to the on-line knowledge base.

Typical message produced on SysMonitor

PRN: IP403_FEC::ReceiverError 804

Message Format

PRN: PLATFORM_FEC::ReceiverError ABCD

Where

PRN: This message is output when the SysMonitor System/Print option is enabled.

PLATFORM This parameter is used to indicate the IP Office unit type (or platform) reporting the error. Possible values are:- IP401NG, IP403, IP406, IP406V2 [reports IP405 in Version 2.1(27)] and IP412.

ABCD This is the actual error code. It is a decoded of the “Ethernet Receive Buffer Descriptor” packet – refer to Table 2. It is formatted as 4 octets - A, B, C and D. The important information is contained within the last 6 bits of this packet - refer to Table 2. Please note that if the most
significant octet (i.e. A) is 0 (zero) then it is not printed out and the error code is only 3 octets long (i.e. BCD).

Where are the errors generated and what do they mean?

FEC::ReceiverError Codes are derived from the FEC generated “Ethernet Receive Buffer Descriptor (RxBD)”.

Table 1 (below) shows the bits within the RxBD that are used to generate the error codes (note that the bits that are labeled as “N/U” are NOT used in the FEC error decoding mechanism although they may actually be non zero).

Receive Buffer Descriptor (RxBD)

Octet
A
B
C
D
Value
8
4
2
1
8
4
2
1
8
4
2
1
8
4
2
1
Bit
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Option
N/U
N/U
N/U
N/U
L
0
0
N/U
N/U
N/U
LG
NO
SH
CR
OV
TR

Note :- Bits 0, 1, 2, and 3 correspond to octet A (value equivalent to 8 for bit 0, 4 for bit 1, 2 for bit 2 and 1 for bit 3), bits 4, 5, 6 and 7 correspond to octet B (value equivalent to 8 for bit 4, 4 for bit 5, 2 for bit 6 and 1 for bit 7), bits 8, 9, 10 and 11 correspond to octet C
(value equivalent to 8 for bit 8, 4 for bit 9, 2 for bit 10 and 1 for bit 11) and bits 12, 13, 14 and 15 correspond to octet D (value equivalent to 8 for bit 12, 4 for bit 13, 2 for bit 14 and 1 for bit 15).

Table 2 (below) provides additional useful information relating to each bit in the
Received Buffer Descriptor (RxBD).


Receive Buffer Descriptor (RxBD) Field Description

Bits Name Description
4 L Last in frame, written by FEC.
0 - The buffer is not the last in a frame.
1 - The buffer is the last in a frame.
10 LG If this bit is set it indicates that the received frame length exceeds 2047 bytes. This should never occur; if it does it indicates a mis-configured LAN. Note that this bit is valid only if bit 4 (the L bit) is set.
11 NO If this bit is set it indicates that a non-octet-aligned frame (i.e. a frame that contained a number of bits that was not divisible by 8) has been received and the CRC check that occurred at the preceding byte boundary generated an error. This problem may occur in half-duplex networks at a low rate and is probably caused by bad network configuration. Note that this bit is valid only if bit 4 (the L bit) is set. Note also that if this bit is set bit 13 (the CR bit) will NOT be set.
12 SH If this bit is set it indicates that a frame was received whose length is less than the minimum defined for this channel. This problem may occur in half-duplex networks at a low rate and is probably caused by bad network configuration.
13 CR If this bit is set it indicates that a received frame, although an integral number of octets in length, contains a CRC error. The probable cause of this type of error is noise (induced from motors or switchgear equipment) or poor network
terminations. If large numbers of CRC errors are being observed then it probably indicates a wiring probleonly valid if bit 4 (the L bit) is set.
14 OV If this bit is set it indicates that a receive FIFO overrun occurred during frame reception. If this bit is set, the other status bits, 10 (LG), 11 (NO), 12 (SH), and 13 (CR) lose their normal meaning and are cleared. This error is normally
observed when the software running in the unit is unable to service the received packet. Note that this bit is only valid if bit 4 (the L bit) is set.
15 TR This bit is set when the receive frame is truncated before the end of frame marker is received, i.e. the received packet is very large. This is a similar error to bit 10 (the LG bit) being set. This should never occur; if it does it indicates a
mis-configured LAN.

What do these errors mean?

If copious amounts of FEC::ReceiverError messages are being output to the SysMonitor log on a regular basis it is a sure sign that you are experiencing problems on your Local area Network, or more specifically on the local subnet that the IP Office is connected to.


What can I do to find out why these errors are being produced?

Further investigation will need to be carried to ascertain exactly what the problem is and what the root cause is. There are many specialised Network Troubleshooting and Network Analyser tools/applications on the market that will help you pinpoint exactly the
cause of the problem being experienced.

One of these specialised tools/applications should be employed; this functionality is NOT provided by the SysMonitor application.

Avaya IP Office

1-800-429-0077

Avaya 4630 IP Telephone Compact business center: one of many tools for use with the IP Office Another great telephone by Avaya

 

about | avaya voice mail | avaya one x quick edition | Boston phone systems | vm pro | contact us
PO BOX 186 Spring Lake, New Jersey 07762
1-800-429-0077 ::: 732-280-3200
copyright 2008 CarrollCommunications.com All Rights Reserved.