19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 229: SIP-SGRP Error Log Entries 2 of 2<br />

Error<br />

Type<br />

1537 (i) Any MEDPRO Status <strong>test</strong> (#1392 MIN OFF<br />

1794 (j) MEDPRO Status <strong>test</strong> (#1392) MIN OFF <strong>test</strong> signaling-group grp#<br />

2561 (k) Any Registered to LSP Inline Error MIN OFF<br />

3073 (l) 19 Far-end TLS Certificate Failure<br />

Inline Error<br />

3329 (m) 21 Near-end TLS Certificate failure<br />

Inline Error<br />

3585 (n) IP Signaling Far-end Status Test<br />

(#1675)<br />

3841 -<br />

3942 (o)<br />

Aux<br />

Data<br />

Associated Test Alarm<br />

Level<br />

On/Off<br />

Board<br />

MIN OFF<br />

MIN OFF<br />

MIN OFF<br />

Recommended Action<br />

Notes:<br />

a. Error Type 0: Run the short <strong>test</strong> sequence first. If every <strong>test</strong> passes, run the long <strong>test</strong><br />

sequence. Refer to each appropriate <strong>test</strong>’s description, <strong>and</strong> follow its recommended<br />

procedures.<br />

b. Error Type 1: Failure of the C-LAN hardware (IP-PROCR in S8300 systems) carrying the<br />

signaling group chel.<br />

To determine which C-LAN had been administered for this signaling group, find the<br />

near-end node name on the signaling group form, then find the C-LAN or IP-PROCR<br />

with the same node name on the ip-interfaces form.<br />

Check for <strong>error</strong>s against the CLAN-BD MO.<br />

c. Error Type 18: The signaling group has been busied out by comm<strong>and</strong>. Release the<br />

signaling group, if appropriate, with release signaling-group grp#.<br />

d. Error Type 257: Tracks failures of the SIP signaling-group PING <strong>test</strong>. See Signaling Group<br />

Ping Test (#1387) for <strong>test</strong> failure information.<br />

e. Error Type 513: Tracks excessive round-trip delay of the SIP signaling-group PING <strong>test</strong>, if<br />

the round-trip delay exceeds 4 seconds. See Signaling Group Ping Test (#1387) for <strong>test</strong><br />

failure information.<br />

f. Error Type: 770: Tracks excessive latency <strong>and</strong> packet-loss from background IP<br />

measurements collected by the Media Processor Board. Indicates that <strong>test</strong> packets sent<br />

from a media processor circuit pack to the far-end IP address specified on the<br />

signaling-group form have exceeded the IP latency <strong>and</strong> loss thresholds, as<br />

administered on the system-parameters ip-options form. Exceeding these<br />

thresholds indicates that the IP network may not be providing sufficient quality of service for<br />

830 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

2 of 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!