Downloadable - Hewlett-Packard

More documents

Recommendations

Info

More then one cascading corrective filter can be applied to an event, while only one noncascading corrective filter can apply. Cascading corrective filters are executed first and than the non-cascading corrective filters. • Cascading Corrective Filters The optional CASCADE attribute of the CORRECTIVE_FILTER class determines the cascading policy for the filter. By default this attribute value is FALSE. This reflects the current behavior of corrective filters. If the value of the CASCADE attribute is TRUE, the next appropriate filter is executed. This allows the definition of filters using the standard action routines, and have them cascading to modify multiple attributes of the event. Cascading filters are executed first and then the non-cascading filters (in each subset the evaluation order remains unchanged: lexicographic order). The cascading policy of a filter is defined at creation and cannot be modified. • Example Creating a Cascading Corrective Filter The following FCL command creates a corrective filter with the cascade attribute set to true: create mcc 0 corrective_filter maloja - Input Discriminator Construct = { - ( LogicalOp = And ), - ( LogicalOp = Item, - Item = ( FType = equality, - relationAssertion = - ( ( ( OSI_SYSTEM, LOG, ALARM_RECORD ) , - Perceived Severity ) , Minor ) ) ), - ( LogicalOp = End ) }, - Target = "alarm_generator_am", - Action = "SetProbableCause", - Parameters = { "ApplicationSubsystemFailure" }, - Cascade = True 6.5.4 TeMIP dictionary comparison enhancement This feature has been implemented to minimize dictionary comparison time. 6.5.4.1 Generalities An important performance enhancement has been done on the temip_dict_compare tool that compares two TeMIP dictionaries. The mcc_msl tool has been modified in order to add time information internally in the dictionary, for each dictionary update. This update is fully transparent for the user. 50
Each dictionary branch is now time stamped and the new algorithm for comparison can operate. It is possible to get benefit of this enhancement for TeMIP directors using an "old" dictionary, by migrating a non-time stamped dictionary through the new “–u” mcc_msl option. In a TeMIP platform containing multiple directors, the good way of migrating and propagating a dictionary is: On a TFRV500L01P04 director 1: • Do "/usr/opt/temip/bin/mcc_msl -u" to migrate an “old” dictionary with the new time stamped dictionary format. • Do “/usr/opt/temip/bin/mcc_ptb” to re-build the parse table. • Reload Dictionary using: “manage reloaddictionary mcc 0” • Propagate the new dictionary to all the other TeMIP directors via the /usr/opt/temip/bin/temip_synchro_data tool. After this operation, all the directors will have an identical time stamped dictionary. 6.5.4.2 Interoperability A TFRV500L01P04 TeMIP director with a “new” dictionary can operate with a TFRV500L01P02 TeMIP director with an “old” dictionary. It is also possible to compare both dictionaries but the performance enhancement of the dictionary comparison cannot operate. A “new” dictionary” can be propagated to a TFRV500L01P02 director and used by it. There will be no real time interoperability issue but the comparison will be possible. Notes: • It is impossible to modify a “new” dictionary (via mcc_msl) from a TFRV500L01P02 director due to the fact that the TFRV500L01P02 mcc_msl tool does not support the new dictionary format. • If a TeMIP platform contains both TFRV500L01P02 directors and TFRV500L01P04 directors and if updates of the dictionary from the V500L01P02 director are mandatory on a “new” dictionary, a TFRV500L01P02 Epatch will be necessary to provide the mcc_msl supporting the new dictionary format. This Epatch could also provide the new enhanced temip_dict_cmp tool. The workaround of this issue is to update the dictionary from the TFRV500L01P04 director and propagate it to all the other directors. 6.5.5 Add Environment variable for Assign Target in NOTIF_FM (PR#15382) 51
Page 1 and 2: hp OpenView TeMIP TeMIP Framework M
Page 3 and 4: Contents Preface ..................
Page 5 and 6: Preface These Release Notes describ
Page 7: Chapter 1 Introduction The current
Page 10 and 11: 2.3 Third-Party Products Compatibil
Page 12 and 13: • Restart the TeMIP director (whi
Page 14 and 15: 4. Un-install all eventual installe
Page 16 and 17: Perform the following actions on th
Page 18 and 19: TFRTFCV50001P004 TFRDBV50001P004 TF
Page 20 and 21: 1. Start the TeMIP SystemMate deplo
Page 22 and 23: 3.5 Manual Operations If you want t
Page 25 and 26: Chapter 4 Fixed Problems in TFRV500
Page 27 and 28: 16416 16171 15550 14034 8994 1190 E
Page 29 and 30: Ref Component Description Workaroun
Page 31 and 32: 5.2 New Known Problems Reported in
Page 33 and 34: Chapter 6 Important Notes 6.1 Upgra
Page 35 and 36: 2. Continue using the Orbix E2A ASP
Page 37 and 38: IT_CONFIG_DOMAINS_DIR /var/opt/temi
Page 39 and 40: Stringified IOR is: ([string/coded
Page 41 and 42: If this file does not exist yet, co
Page 43 and 44: The TeMIP Event Filtering and Corre
Page 45 and 46: Environment Variables Configuration
Page 47 and 48: Then an access module can be config
Page 49: } /* initialization*/ void initiali
Page 53: _hostname[oracle] sqlplus /nolog SQ

Downloadable - Hewlett-Packard

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?