Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Guida alla Risoluzione dei Problemi Scaricare il pdf (Pagina 29)

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

When CPF loads a diameter dictionary, that has two AVPs defined with the same name, but

with different commands or vendor IDs, only the first AVP is saved in the application.

5.3.1.1.2 Causes

Using a diameter dictionary in which the AVP name is not unique.

5.3.1.1.3 Symptoms

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

The diameter dictionary used by CPF contains several AVPs that do not have a unique AVP

name.

For example, the following two AVPs contain the same name and command, but different

vendor IDs.

<avp name="Service-Selection" code="493" format="utf8String" mRule="must"

vendorId="10415"/>

<avp name="Service-Selection" code="493" format="utf8String" mRule="must"

vendorId="0"/>

This results in a mismatch between the two AVPS, as they are not unique, though they have

the same name and the following message displays in the log file:

ERROR [10155] Diameter Dictionary (SDC dictionary v9): Mismatch between AVP

definition <Content Definition 3GPP-Charging-Characteristics 13 10415 UTF8String>

and <Content Definition 3GPP-Charging-Characteristics 13 UTF8String>: Trying to

load two AVPs with identical names and different codes. [jmsContainer-1_11]

[DiameterDictionary.mismatchDetected()]

2013-10-15 15:23:23,006 ERROR [10155] Diameter Dictionary (SDC dictionary v9):

Mismatch between AVP definition <Content Definition Service-Selection 493 10415

UTF8String> and <Content Definition Service-Selection 493 UTF8String>: Trying to

load two AVPs with identical names and different codes. [jmsContainer-1_11]

[DiameterDictionary.mismatchDetected()]

5.3.1.1.4 Resolution

For diameter application messages, use the super dictionary. The super dictionary contains

only AVPs with unique names.

The base part of the super dictionary contains messages with application ID 0. These messages

are used by more than one diameter Interface (application ID).

The following are options on how to resolve different AVP dictionary issues:

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

Nessun commento

Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Guida alla Risoluzione dei Problemi Pagina 29