BRI-PORT error log entries and recommended actions

Last Updated : Sep 29, 2023 |
Prolog information
BRI-PORT Error Log Entries
Error type
Aux data
Associated test
Alarm level for BRI-PORT
Alarm level for ABRI-PORTATT-PORT LGATE-PT ATTE-PT
On/Off board
Command to resolve the error
0
0
Any
Any
Any
Any
test port location
1
Level 1 Status Inquiry (#621)
WRN
Any 1
OFF
test port location r 2
18
busyout port location
WRN
OFF
release port location
130
WRN
ON
test port location
257
EPF Inquiry (#622)
WRN
Any 1
OFF
test port location
513
46222
(d)
(d)
ON
769
0
WRN
MAJ
OFF
1281
BRI NPE Crosstalk (#617)
MIN
WRN 1
ON
test port location l r 2
1537
46210
CRC Error Counter (#623)
WRN
Any1
OFF
1793
BRI Port Local TDM Looparound (#619)
MIN
WRN1
ON
test port location l r 2
3841
46208
3842
0
3843
0
3844
46223
3845
3846
TEI
3847
0
1. Major and Minor alarms on this MO may be downgraded to Warning alarms based on the value used in set options.
Notes:
  1. Error type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures.
  2. Error type 1: The Level 1 Status Inquiry fails or when the BRI detects that Level 1 has been deactivated on the port. Refer to the repair procedures for Level 1 Status Inquiry Test 621.
    Aux data blank: The Level 1 Status Inquiry failed. Aux data 32773: the BRI-LINE media module detected that Level 1 has been deactivated.
  3. Error type 130: The media module has been removed or has been insane for more than 11 minutes. To clear the error, replace or reinsert the media module.
  4. Error type 257: The EPF Status Inquiry fails due to an overcurrent condition or when the BRI-LINE media module detects that the EPF is in an over current condition. The aux data field contains one of the following values:
    • blank – This indicates that the EPF Status Inquiry failed due to an overcurrent condition.
    • 40988 – This indicates that the BRI-LINE media module has detected an overcurrent condition and has turned the EPF off.
    Execute the short test sequence, and see the repair procedures for Test #622.
  5. Error type 513: The media module is having problems transmitting data to the packet bus, thus affecting the conveyance of signaling information over the D-Channel. With Aux Data 46222, this error occurs when the packet bus transmit buffers overflow. This condition probably indicates a hardware problem. The BRI-PORT Alarm Level for the error with Aux Data 46222 is MINOR/WARNING, and the ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT Alarm Level is MAJOR/MINOR/WARNING. With Aux Data 0, this error occurs whenever the packet bus transmit FIFO buffers overflow. This condition can be caused by an on-board hardware problem as well as by problems on the packet bus that disrupt the BRI circuit pack’s ability to transmit data onto the packet bus. Use troubleshooting procedures for both on-board hardware problems and potential off-board packet bus problems. See Isolating and repairing packet-bus faults in Maintenance Procedures for Avaya Aura® Communication Manager, Branch Gateways and Serversfor more information about troubleshooting the packet bus. The BRI-PORT Alarm Level for the error with Aux Data 0 is MINOR, and the ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT Alarm Level is MAJOR.
  6. Error type 769: The BRI NPE Crosstalk Test 617 fails. Run the long test sequence, and note the results of Test #617.
  7. Error type 1281: A port’s associated broadcast-signaling links have too much traffic related to link establishment. This could occur if an endpoint on this port is sending link establishment traffic on a port level broadcast link or if there are Level 1 problems on the port. Check the error logs for Level 1 errors. If Level 1 problems exist, follow the repair procedures listed for Test #621. Software will suspend activity to this port for 75 minutes when the port is alarmed due to this error. The service suspension does not occur if the port is an ABRI-PORT/LGATE-PT/ATTE-PT/ATT-PORT. If this problem persists, replace the endpoint or endpoints associated with this port. If replacing the endpoints does not fix the problem, follow normal escalation procedures.
  8. Error type 1537: The port receives an invalid frame over the D-Channel. When CRC errors exceed five within 15 minutes, the port is taken out of service for five seconds. If five more CRC errors are received within 15 minutes of the first set of five errors, the port is taken out of service for one minute. If five more CRC errors are received within 15 minutes of the last five, the port is taken out of service for 15 minutes.
    This error is most likely due to a problem with the wiring to the set or adjunct, interference on the wiring due to a noise source, or no termination that is an open circuit. It usually does not indicate a problem with the circuit pack.
    • Check the wiring to the endpoints or the adjunct.
    • If the problem persists, replace the endpoints or adjuncts, or escalate the problem.
  9. Error type 1793: The BRI Port Local TDM Looparound Test 619 fails. Run the long test sequence, and note the results of Test #619.
    There are no recommended actions for the following Error Types. The Error Types are simply provided as additional data that may prove useful while troubleshooting.
  10. Error type 3841: A Layer 1 Transmission error is detected for the port. Run the long test sequence, and note the results of the Layer 1 Transmission Error Counter Test 624.
  11. Error type 3842: A BRI port supports up to three Terminal Endpoint Identifiers (TEIs). This error occurs when the switch receives a request for a fourth TEI on a port. Check the number of endpoints administered for this port.
  12. Error type 3843: SPID initialization request is made from an endpoint and the switch determines that the SPID value is invalid or is a duplicate of another SPID that is already initialized at Layer 3 on the port. Check the administration of the endpoints.
  13. Error type 3844: The circuit pack detects an overflow of its receive buffers. Run the long test sequence, and note the results of the Receive FIFO Error Counter Test 625.
  14. Error type 3845: The BRI Port Local LAN Looparound Test 618 fails. Run the long test sequence, and note the results of Test #618.
  15. Error type 3846: Most likely occurs when the Terminal Endpoint Identifier (TEI) administered for the ASAI or Avaya endpoint does not match the TEI administered in the ASAI or Avaya adjunct. Check the switch administration of the TEI against that of the adjunct and make sure that both are using the same TEI.
  16. Error type 384: Sets on the port do not support layer-3 initialization. Consult the Service Set documentation.