09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

Signaling Group Ping Test (#1387)<br />

Note:<br />

Note: Multiple failures of this test will cause this signaling group’s associated H.323 or<br />

SIP B-Channels to be taken out of service (OOSFE). This will allow incoming<br />

calls to be made when the far-end comes up before the near end has detected it.<br />

The signaling group will be left in service, but in the far end bypass state.<br />

If the PING is successful, the test looks at the PING round-trip delay. If a round-trip delay of<br />

greater than 4 seconds is reported, a separate error is logged. Excessive round-trip delays<br />

within the signaling group will not take the signaling group out of service.<br />

The standard PING command can be executed using the C-LAN board’s address and far-end<br />

IP address from the signaling group screen to see the actual round-trip delay.<br />

This test runs on H323-SGR (H.323 Signaling Group) and SIP-SGRP (SIP Signaling Group).<br />

Table 622: Signaling Group Ping Test (#1387) 1 of 2<br />

Error<br />

Code<br />

None<br />

1<br />

2<br />

Test<br />

Result<br />

Description / Recommendation<br />

ABORT Internal Error.<br />

1. Retry the command at 1-minute intervals up to 3 times.<br />

7 ABORT Destination unreachable.<br />

1. Verify that the C-LAN has been administered with an IP-Route that<br />

enables the C-LAN to reach the far-end IP address.<br />

2. Once verified, enter test sig-group grp# and verify that the<br />

Signaling Group Ping test (#1387) passes.<br />

1005 ABORT Configuration for this test is incorrect.<br />

1. If Layer 3 or LRQ is enabled for this H.323/SIP signaling group, this<br />

error can be ignored. There is no need to run the ping test.<br />

2. Verify that the link is in service with status port or status link.<br />

Verify that the routing table has destinations that are reachable<br />

through this port.<br />

3. Repeat the test.<br />

4. If the test aborts with Error Code 7 after step 2 is verified, escalate the<br />

problem.<br />

1 of 2<br />

Communication Manager Release 5.0 Issue 4 January 2008 2007

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

Saved successfully!

Ooh no, something went wrong!