If the Secure Access Link (SAL) in your Avaya Aura solution is not operating normally, Avaya Support will not receive alarms and other important messages originating from the various components and applications in your system. Neither will Avaya Support be able to connect to your system for remote diagnosis. If you suspect a malfunctioning SAL in your system, try this procedure.
If you do not see results similar to those shown in the ping and wget examples following these troubleshooting steps, contact your corporate IT organization.
Ping for server DNS or proxy server reachability:
ping 135.9.69.123
Pinging 135.9.69.123 with 32 bytes of data:
Reply from 135.9.69.123: bytes=32 time=111ms TTL=54
Reply from 135.9.69.123: bytes=32 time=101ms TTL=54
Reply from 135.9.69.123: bytes=32 time=100ms TTL=54
Reply from 135.9.69.123: bytes=32 time=100ms TTL=54
Ping statistics for 135.9.69.123:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 111ms, Average = 103ms
Ping for Avaya support server reachability
ping support.avaya.com
Pinging support.avaya.com [198.152.212.23] with 32 bytes of data:
Reply from 198.152.212.23: bytes=32 time=101ms TTL=244
Reply from 198.152.212.23: bytes=32 time=101ms TTL=244
Reply from 198.152.212.23: bytes=32 time=101ms TTL=244
Reply from 198.152.212.23: bytes=32 time=102ms TTL=244
Ping statistics for 198.152.212.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 101ms, Maximum = 102ms, Average = 101ms
WGET for HTTP response from Avaya support
wget http://support.avaya.com
HTTP request sent, awaiting response... 200 OK