Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2021967.1
Update Date:2017-03-02
Keywords:

Solution Type  Technical Instruction Sure

Solution  2021967.1 :   How to Change DTS Stream Loss Behavior of IXP Process  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  




In this Document
Goal
Solution
 Explanations
 Procedure


Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 7.1 and later
Tekelec

Goal

IXP processes can restart if they are loosing connection (DTS connection).

This behavior can be changed if restart must be avoided.

Solution

Change must be documented in customer engineering document.

Explanations

IXP processes (IxpBuild, IxpOperate, IxpStore) can behave in three different way when loosing DTS connection:

  • Reconnect without offset (0). No restart of IxpBuild.
  • Reconnect with offset (1). Default offset is 1ms. This is to avoid duplicate records. No restart of IxpBuild.
  • Restart (2). Default behavior.

Each process type have his own LongParam parameter:

  • IxpBuild: BldDtsFailureAct
  • IxpOperate: OpDtsFailureAct
  • IxpStore: StoDtsFailureAct

Procedure

  1. Add LongParam
    This command have to be issued on master server of the subsystem (change value to 1):
    echo 'No|BldDtsFailureAct|1|Build behavior in case of DTS disconnection' | iadd -ha -xU -fallowPgmChg -fname -fvalue -fcomment LongParam
  2. Check setting is present and set as expected:
    [cfguser@ixp0001-1b ~]$ igrep -p BldDtsFailureAct LongParam
    allowPgmChg name value comment
    No BldDtsFailureAct 1 Build behavior in case of DTS disconnection
IXP process restart is necessary for the parameter to take effect.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback