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

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

5.2.1 Request is Not Routed Using the Routing Rows as Expected

Error Description

When traffic is sent to SDC, and then a change is made to the routing table (i.e. added new

rows, or edited existing rows), and then another request is sent to one of the servers, without it

being routed using one of the added routing rows.

Causes

This is due to session stickiness for pools. The already existing session is being reused for the

incoming request, and the sessions bypasses the routing table.

Symptoms

 The pool that should be the destination for the traffic does not accept it (if it is a

different pool than before the routing change).

 Routing scripts, (Check Error in Answer, Handle Server Error, etc.) that belong

to the new routing row that should be selected, do not run.

 The logging is in TRACE mode for TransactionManagement, and a message of

the format “Pool {0} was selected for {1}” did not appear in CPF logs since the

routing change.

Resolution

Change the session ID for the next request or wait for session expiration (default is 30

seconds).

5.2.2 No Pools are Selected for Routing

Error Description

No messages are routed to the pools configured in the routing rule, even though the rule was

correctly configured with the ROUTE action. Error messages display in the log as described in

the Symptoms section below.

1 2 ... 20 21 22 23 24 25 26 27 28 29 30 ... 41 42

Brak uwag

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