Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Anleitung zur Fehlerbehebung PDF herunterladen (Seite 34)

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

1. Take a Wireshark capture of the failed transaction.

2. Compare the message coming into the SDC to the message coming out of the SDC

to see at what step Wireshark could not parse the AVPs.

3. Search for the failed AVP code and length value in the message coming into the

SDC at the segments where Wireshark was not able to parse the message coming

out of the SDC.

4. Identify the last AVP before the failed AVP from the error log.

5. Check the AVP definition in the used dictionary and compare it to the AVP which

was sent to SDC.

6. Correct any dictionary mistake according to the actual sent data and the latest 3GPP

Diameter application codes and identifiers specification document (for example, TS

29.230).

7. In case of conflict between the received data and the latest diameter application

specification document, more detailed specification documents (such as TS 29.272

in the described example) should be referenced to verify that there are no mistakes

in the diameter application specification document.

5.3.3 Configured Transformation Does Not Take Effect

Error Description

After configuring a Diameter Identity for some Routing Rules, the configured transformation

does not take place. For example, the Destination Host/Realm of some request was not

changed as was when the request was routed through SDC.

Causes

After the configuration, the request on which the transformation rule was configured was

wrong, as it was a request from an existing session.

Symptoms

There are no special log errors/warnings for this problem.

1 2 ... 29 30 31 32 33 34 35 36 37 38 39 40 41 42

Keine Kommentare

Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Anleitung zur Fehlerbehebung Seite 34