Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Instrukcja Naprawy Pobierz pdf (Strona 27)

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

timeout, and since clients usually do not respond to requests, the pending timeout will be

invoked and cause another endless cycle of requests that will be sent to the client.

Causes

A bad “Handle Server Error” script is configured for the routing row that was selected for the

request.

Resolution

In the “Handle Server Error” script, reconfigure the “answerFromServer” parameter for any

RemoteNodeEvent. For example, for CANNOT_ROUTE and TIMEOUT there are no answers

from server, so answerFromServer cannot be returned.

5.2.4 Routing of Server Side Request (CLR) Fails

Error Description

A CLR request arrives and is then forwarded (based on a forward routing rule) to a client peer

whose name appears as the Destination-Host AVP of the request. When this routing rule is

configured as a Roaming Proxy, and then post transformation is done on the Destination-Host

AVP before the request searches for the destination peer with this name. If after post

transformation, the peer with this name is not found, then routing fails.

Causes

A server side request, such as CLR is generated in response to a client side request, such as

ULR (when a CLR is sent by the server then the Destination-Host AVP is taken from the

Origin-Host of the ULR). The routing rule of the client side requests must also be marked as

roaming proxy otherwise the CLR routing will fail.

Each client peer at the SDC from where the ULR messages come from must have a peer

profile (not default), because a peer profile name is used at translation of the destination peer.

Symptoms

The following section describes the error conditions and their relevant error messages.

1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 41 42

Brak uwag

Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Instrukcja Naprawy Strona 27