Avaya S8700 Maintenance Manual page 1900

For multi-connect configurations

Hide thumbs Also See for S8700:

Table of Contents

Maintenance-Object Repair Procedures

System Technician-Demanded Tests:

Descriptions and Error Codes

Always investigate tests in the order presented in the following table when

inspecting errors in the system.

Order of Investigation

Packet Bus Port Health Inquiry test (#567)

Clear Error Counters (#270)

D = Destructive, ND = Nondestructive

Clear Error Counters (#270)

This test is not an actual test in the strict sense of the word. Many circuit packs

have counters in the Angel firmware. The circuit pack's Angel continuously runs

port self-tests on idle ports and keeps track of any errors it detects by

incrementing a firmware counter. When the counter value reaches some preset

threshold, the Angel sends a single CCMS (Control Channel Message Set) error

message uplink to the Avaya MultiVantage™ software. No more error messages

of that type are sent uplink until the Avaya MultiVantage™ software sends a

downlink message to clear the counter. This strategy keeps a failed port/circuit

pack from flooding the Avaya MultiVantage™ software with a continuous string of

identical error messages. This test is used to clear the counter, so that if the port

continues to fail during or after Avaya MultiVantage™ software demanded testing,

the Angel will send a message to indicate that fact.

This test is only used to send a downlink message to the Angel on the

Maintenance/Test circuit pack. Since the Angel normally provides no uplink

response to this message, this test should never abort or fail.

Table 8-482. Test #270 Clear Error Counters

Issue 1 May 2002

Description / Recommendation

This test should never abort.

This test should never fail.

1. Retry the command at 1-minute intervals up to 5 times.

2. If the test continues to fail, escalate the problem.

The message to clear the Maintenance/Test circuit pack's counter for

Background Maintenance Failures has been sent.

Continued on next page

Troubleshooting