2.7.2 Insert

The Diameter, and then Troubleshooting with IDIH, and then Configuration, and then Traces [Insert] screen is used to create a new trace.

Note:

A maximum of 100 traces may be inserted.

The fields are described in Traces Elements.

1. Select Diameter, and then Troubleshooting with IDIH, and then Configuration, and then Traces.
2. Click Insert.

   The Diameter, and then Troubleshooting with IDIH, and then Configuration, and then Traces [Insert] screen appears.

3. Enter a trace name in the Trace Name field.
   The name must meet these requirements:

   • Maximum length of 32 characters
   • Valid characters are alphanumeric and underscore. Must contain at least one alpha and must not start with a digit
4. Select a Trace Location by selecting either Site Trace or the Network Trace.
5. Select a Content Type from the Content Type options.
   There are seven Content Types supported: Non-success answers, Requests, Answers, Ad Hoc Requests, Ad Hoc Answers, User Identity, and Equipment Identity.
6. The Content Type field determines what Content Values are available.

   If the Content Type is set to Non-success answers, then no other content values are available.

   If the Content Type is set to Requests, then the user may select an Application-ID, Command-Code, Origin-Host, Origin-Realm, Destination-Host, and/or Destination-Realm. Application-ID and Command-Code option, which contain a pre-defined list of supported Diameter/RADIUS interfaces. Additionally, all other parameters may be left blank as wild cards.

   If the Content Type is set to Answers, then the user may select an Application-ID, Command-Code, Origin-Host, and/or Origin-Realm. Application-ID and Command-Code option, which contain a pre-defined list of supported Diameter/RADIUS interfaces. Additionally, all other parameters may be left blank as wild cards.

   If the Content Type is set to Ad Hoc Requests, then the user may select an Application-ID, Command-Code, Origin-Host, Origin-Realm, Destination-Host, and/or Destination-Realm. Additionally, an optional content value is available to select an AVP to be checked. Application-ID and Command-Code options contain a pre-defined list of supported Diameter/RADIUS interfaces to which the user may also add. Additionally, all other parameters may be left blank as wild cards.

   Note:

   The optional AVP is based on what AVPs are configured in the AVP Dictionary. For further information about the AVP Dictionary, see Oracle Communications Diameter Signaling Router Diameter User Guide.

   Note:

   For a non-grouped AVP all operators for the specified data type are allowed. For a grouped AVP only the Exists and Does not exist operators are allowed.

   If the Content Type is set to Ad Hoc Answers, then the user may select an Application-ID, Command-Code, Origin-Host, and/or Origin-Realm. Additionally, an optional content value is available to select an AVP to be checked. Application-ID and Command-Code are selected from pulldown lists and contain a pre-defined list of supported Diameter/RADIUS interfaces to which the user may also add. Additionally, all other parameters may be left blank as wild cards.

   Note:

   The optional AVP is based on what AVPs are configured in the AVP Dictionary. For further information about the AVP Dictionary, see Oracle Communications Diameter Signaling Router Diameter User Guide.

   Note:

   For a non-grouped AVP all operators for the specified data type are allowed. For a grouped AVP only the Exists and Does not exist operators are allowed.

   If the Content Type is set to User Identity, then the user may select an Application-ID. The Application-ID option lists a pre-defined list of supported Diameter/RADIUS interfaces, although the user cannot add anything new to the list.

   Note:

   After an Application-ID is selected, the user can specify a user in the associate AVP as the criteria for selecting messages, which is identified by either IMSI or MSISDN.

   If the Content Type is set to Equipment Identity, then the user may select an Application-ID. The Application-ID option lists a pre-defined list of supported Diameter/RADIUS interfaces, although the user cannot add anything new to the list.

   Note:

   After an Application-ID is selected, the user can specify equipment in the associated AVP as the criteria for selecting messages, which is identified by IMEI.
7. Select a Scope Type from the Scope Type options.
   The scope for a trace can be for a specific Connection, specified Peers, specified DSR Applications, or All messages.
8. Select a Scope Value from the Scope Value options
   The scope value is determined by which Scope Type is selected.
9. Enter a number of matches for the trace to find in the Number of Matches field.

   Note:

   A maximum of 1000 matches is permitted.
10. Enter a duration time for the trace in the Time of Duration field.
    The duration can be up to 96 hours.
11. Enter a comment describing the trace in the Notes field.

    Note:

    Entering a value in the Notes field is optional.