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

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

 Client side request, like ULR, routed through SDC, with Roaming Proxy is

enabled. The routing of ULR was successful, but peer profile at the client peer is

not configured.

- Error Message: “Diameter client peer {some peer name} must have a

peer profile for Roaming Proxy full functionality. Routing of future

requests from server will fail!”

 Routing of “Forwarded” message of server side request, such as CLR, when

roaming is enabled is failed.

- Error Message: “Routing of roaming request from server failed, no

suitable client peer found, at event {some event description}”

- Error Message: After the above message there will be a regular SDC

routing failed message.

Resolution

The following are ways resolve the issue:

 Make sure that the client peer of the SDC through which the ULR messages

have been sent has a non-default peer profile.

 Make sure that the “Forward” routing rule of server side request, such as CLR,

is configured as a roaming proxy and that its related client side, such as ULR, is

also configured with a roaming proxy.

 Make sure no changes were made to SDC configuration in the time gap between

the ULR request and its matching CLR request routing. For example, that the

peer profile name of a client peer was not changed.

CPF Transformation

5.3.1 CPF Dictionary

Each diameter network element holds its own dictionary. A successful diameter connection

between two network elements requires compatible dictionaries that maintain the same AVP

data message format. All AVPs included in a diameter dictionary must have a unique AVP

name.

Mismatch between Multiple AVPs

5.3.1.1.1 Error Description

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

Keine Kommentare

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