_______________________________________________ Release Notes for DECss7 V3.1-E/ITU-T DIGITAL OpenVMS Platform Revision/Update Information: Edition: August 1999 ________________________________________________________________ V3.1-E/ITU-T August 3, 1999 The information in this document is subject to change without notice and should not be construed as a commitment by Compaq Computer Corporation or its affiliated companies. Compaq Computer Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used and copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Compaq Computer Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © 1999 Compaq Computer Corporation. All rights reserved. Trademarks: COMPAQ, the Compaq logo, the Digital logo, and DECss7 Registered in U.S. Patent and Trademark Office. Other product names mentioned herein may be the trademarks of their respective companies. This document was prepared using DEC DOCUMENT, Version 3.2. _________________________________________________________________ Contents Preface................................................... v 1 New Features in DECss7 V3.1-A 1.1 Software Environment.......................... 1-1 1.1.1 Mandatory patches......................... 1-1 1.1.2 DECnet transport setup.................... 1-1 1.2 Different Release levels of the TCAP API...... 1-2 1.3 Wildcarding of Entity Instances............... 1-2 1.3.1 The ss7_mgt_show_next Routine............. 1-3 1.3.2 Wildcarding of Instances of Multi-instantiable Entity Classes......... 1-5 1.3.3 Wildcarding in S7MP....................... 1-11 1.3.4 The DECss7 Management ss7_mgt_show_next Routine and GUP........................... 1-12 2 Change History 2.1 Changes between V3.1-A and V3.1-B............. 2-1 2.1.1 Cannot send more than 252 bytes in UNITDATA (S30-191)........................ 2-1 2.1.2 S7MP may sometimes crash while a trace file is still open (S30-262).............. 2-1 2.1.3 The first S7MP command following a comment line is not executed (S31-163)............ 2-1 2.1.4 FEP crash when receiving a corrupted TCAP message (S31-166)......................... 2-2 2.1.5 TCP connection lost on keep alive message reception (S31-173)....................... 2-2 2.1.6 PPLRTL.................................... 2-2 2.2 Changes between V3.1-B and V3.1-C............. 2-2 2.2.1 BEP crashes if entity names are not padded to 64 characters (S31-118)................ 2-2 iii 2.2.2 The GTT rule modification is not effective until the platform is stopped and restarted (S31-190)....................... 2-3 2.2.3 FEP in timeout state on SENDMSG command (S31-194)................................. 2-3 2.2.4 API management problem (S31-218).......... 2-3 2.2.5 Corrupted associations after halt button used (S31-220)............................ 2-3 2.2.6 TCAP_ENABLE_INDIC called from thread fails with accvio (S31P-011).................... 2-4 2.2.7 ENAEVT/DISEVT does not work on wildcarded BEP subentities (S31P-014)................ 2-4 2.3 Changes between V3.1-C and V3.1-D............. 2-4 2.3.1 DUPLISU characteristic is lost when the DNSES board is restarted (S30-279)........ 2-4 2.3.2 ANSI protocol does not check LI when greater than 2 (S31-178).................. 2-4 2.3.3 Spurious blank in S7MP configuration file (S31-224)................................. 2-5 2.3.4 Overloading of SS7 links (S31-227)........ 2-5 2.3.5 FEP crash when application with appid 1 or 255 dies (S31-234)........................ 2-5 2.3.6 MGT command output is not complete when node is unreachable (S31-246)............. 2-5 2.3.7 Error from STARLET when using GUPPORT with ISUPMP (S31P-037)......................... 2-6 2.3.8 TCAP Application cannot be put in service (S31P-041)................................ 2-6 2.3.9 When a TCAP application is disabled under load, it cannot be re-enabled (S31P-042)................................ 2-6 2.3.10 CONGPROC and CRITCONGPROC FEP attributes not updated when application dies (S31P-045)................................ 2-7 2.3.11 CRITCONGPROC FEP attribute is not reset after congestion (S31P-046)............... 2-7 2.4 Changes between V3.1-D and V3.1-E............. 2-7 2.4.1 User application could crash when calling ss7_sccp_decode_party_address (S31-261)... 2-7 2.4.2 Number of max GTT rules increased from 2000 to 4000 (S31-266).................... 2-7 iv 2.4.3 User distribution function ss7_ud_zzz_fep_indication called twice (S31-269)........................... 2-8 2.4.4 Output List incomplete when Node Unreachable message received (S31-271).... 2-8 2.4.5 Bad incrementation of counters for SCCP relay function (S31-276).................. 2-8 2.4.6 SAVE_CONFIG fails with SLTUSE=DEACT (S31-282)................................. 2-10 2.4.7 Constant SS7_K_INVALID_ATTRIBUTE missing (S31P-052)................................ 2-10 3 Known Problems 3.1 Known Problems................................ 3-1 3.1.1 Crash of FEP/BEP/DIR process if a connection problem occurs (S24-082)....... 3-1 3.1.2 Low Priority of FEP Process May Cause SS7 Link Failure (S25-047).................... 3-1 3.1.3 Platform overload: Traffic peak........... 3-2 3.1.4 DNBE1 - Traffic restrictions.............. 3-3 3.1.5 Inconsistent state of Related LINK and DATA_LINK Entities........................ 3-6 3.2 New Problems in V3.1-E........................ 3-7 4 Documentation Errors and Omissions 4.1 Incomplete Description of the report_cause Parameter of the ss7_tcap_notice_indication Routine (S31-092)............................. 4-1 4.1.1 Description............................... 4-1 4.1.2 Solution.................................. 4-1 4.2 Inappropriate Platform Tuning for the Portable API (S31-127)................................. 4-1 4.2.1 Description............................... 4-1 4.2.2 Solution.................................. 4-1 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual....... 4-2 4.3.1 trap_param................................ 4-3 4.3.2 Traps Mapped on DECss7 Events............. 4-3 4.3.3 Traps Mapped on PSI....................... 4-18 v 4.3.4 Traps Reported at Agent Initialization Time and Traps Reporting Platform Inconsistencies........................... 4-18 4.3.5 Solution.................................. 4-19 4.4 The NBBUFF characteristic of FEP_SUBSYSTEM missing....................................... 4-20 4.4.1 Description............................... 4-20 4.4.2 Solution.................................. 4-20 Tables 3-1 Inconsistent states of Data Link and Link...................................... 3-6 3-2 Consistent states of Data Link and Link... 3-7 4-1 trapParam Indexed objects................. 4-3 4-2 Traps mapped on DECss7.................... 4-3 4-3 Traps mapped on PSI....................... 4-18 4-4 Traps Reported at Agent Initialization Time...................................... 4-18 4-5 Traps Reported when Inconsistencies are Detected.................................. 4-19 4-6 FEP_SUBSYSTEM Characteristic Attributes... 4-20 vi _________________________________________________________________ Preface This document serves as the release notes for DECss7 V3.1- E/ITU-T, which implements the ITU-T (formerly known as CCITT) protocol. It presents the new features in the base release, the change history since the base release, and any known problems. Intended Audience These release notes are intended for anyone interested in using DECss7 in their ITU-T network. DECss7 Documentation Set Refer to the following manuals for more information about DECss7. o DIGITAL DECss7 Technical Description o DIGITAL DECss7 Installation Guide o DIGITAL DECss7 Management Application Development Guide o DIGITAL DECss7 Entity Reference Manual o DIGITAL DECss7 Platform User's Guide o DIGITAL DECss7 S7MP Reference Manual o DIGITAL DECss7 Application Development Guide o DIGITAL DECss7 Troubleshooting Guide You are advised to read the Technical Description before reading any other book in the documentation set. v Conventions______________________________________________________ Convention_______Meaning___________________________________ Subsystem Systems supporting DECss7 are referred to as subsystems. $ The default Digital Command Language prompt. / (slash) This symbol is used to indicate that a qualifier will appear as the next item of a command. - (hyphen) This symbol must be used to connect two lines of the same command when the command carries over onto the next line. In examples, a key name (usually abbreviated) shown within a box indicates that you press a key on the keyboard; in text, a key name is not enclosed in a box. In this example, the key is the Return key. (Note that the Return key is not usually shown in syntax statements or in all examples; however, assume that you must press the Return key after entering a command or responding to a prompt). A sequence such as indicates that you must hold down the key labelled Ctrl while you press another key or a pointing device button. In examples and procedures, a key combination is enclosed in a box. XXX In filenames or routine names, XXX stands for the protocol variant: ANSI, CCITT, FT _________________or_CHINA._________________________________ vi 1 _________________________________________________________________ New Features in DECss7 V3.1-A This chapter describes the new features of DECss7 V3.1-A. 1.1 Software Environment DECss7 V3.1-A needs DIGITAL OpenVMS V7.1 and DECnet-Plus V7.1 to run. 1.1.1 Mandatory patches The software patches can be obtained through your COMPAQ representative, or directly from the following web site: http://ftp.service.digital.com/public/vms/ The following patches are mandatory for OpenVMS: o ALPSYS09_071 o ALPBASE02_071 The following patches are mandatory for DECnet: o ECO 2 (DEC-AXPVMS-DNVOSIECO02-V0701-4.PCSI) 1.1.2 DECnet transport setup Before running any DECss7 command procedures or processes, make sure that the following command has been executed. You may execute it manually, or place it at the end of the SYSTARTUP_VMS.COM command procedure: $ MCR NCL SET SESSION TRANSPORT PRECEDENCE {NSP} New Features in DECss7 V3.1-A 1-1 New Features in DECss7 V3.1-A 1.2 Different Release levels of the TCAP API 1.2 Different Release levels of the TCAP API DECss7 V3.1-E makes it possible for TCAP applications to use different release levels of the TCAP API. The version of the TCAP API supplied with previous releases of DECss7 up to V3.1-4 is retained for backward compatibility. The new release of the TCAP API is the only one supported by the user documentation as of V3.1-E. The earlier release of the TCAP API is linked by default unless you explicitly define ss7_tcap_96_api at compile time to enable the application to use the new TCAP API. Use the following qualifier to define the new release of the TCAP API: /DEFINE=SS7_TCAP_96_API The main differences between the two release levels of the API concern: o The signatures of the routines o The routine parameters: the older release level has fewer parameters o The constants defined There is no change in the levels of implementation for the ITU-T routines, but users of the newer API (ss7_tcap_96_ API) must fill all parameters using null values for those parameters that are not applicable to the ITU CCITT Blue Book or the ITU-T White Book. 1.3 Wildcarding of Entity Instances The DECss7 Wildcarding capability allows a management application to perform a request on all or a set of entity instances of a specific class. In this case, the entity name contains one or more asterisk (*) characters instead of one or more instance IDs. This feature is not to be confused with the ability to distribute requests to all the FEP subsystems in a DECss7 platform, sometimes known as the global view facility. Distributed requests also make use of the asterisk (*) character, which in this case is used to replace the name of a specific FEP_SUBSYSTEM entity. 1-2 New Features in DECss7 V3.1-A New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances The distinction between the use of the two wildcards is that they are applied at different levels in the entity hierarchy. See the DECss7 Entity Reference Manual for details of the DECss7 entity trees and of the individual entities and their attributes. For the Wildcarding capability, the asterisk replaces an instance ID in a specific entity class. The entity class must of course be instantiable more than once. Wildcarding cannot be applied to single instance entities, such as the SS7 Level entities, nor can it be applied to the top level entities in the DECss7 entity trees, that is, the FEP_SUBSYSTEM and the BEP_SUBSYSTEM entities. The distributed request capability has its wildcard applied only to the FEP_SUBSYSTEM entity, the top level in the hierarchy. Wildcards cannot be applied for any reason to the BEP_ SUBSYSTEM entity. 1.3.1 The ss7_mgt_show_next Routine The wildcarding capability introduces a new Management API routine ss7_mgt_show_next. This routine shows some or all of the attribute values of an entity instance of a given class code. This entity is the next entity to the entity specified by the entity_name parameter. This routine can only be applied to multi-instantiable entities; there is no next entity for single instance entities. It targets an entity that satisfies all the following conditions: o belongs to the same class as the entity identified by the input parameter entity_name (that is, the class of the last child entity) o has for its parent entity[1] instance ID the same value as or the next higher value to the entity identified by the input parameter entity_name; (the routine tries ____________________ [1] The class name is established by progressing in a directly linear fashion from highest parent to lowest child through the parent-child entity hierarchy. For example, MTP3, DESTINATION, ROUTE, or MTP3, LINKSET, LINK, or TCPCM, SITE, HOST, CONNECTION. New Features in DECss7 V3.1-A 1-3 New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances first to find the next instance with the same parent instance ID) o if it has the same parent entity instance ID, it has the next higher value for its instance ID to the entity identified by the input parameter entity_name; if it has the next higher parent instance ID, it has the lowest instance ID of that parent entity's child entities If an entity exists that meets all these conditions, it is the next entity. The last instance of the entity is the entity that satisfies all the following conditions: o belongs to the same class as the entity identified by the input parameter entity_name o has the highest value for its parent's instance ID[1] o has the highest value for its own instance ID When there is no next entity to provide the last entity, the value SS7_NOOTHERINSTANCE is returned. If the target entity name includes wildcarded instance IDs, the targeted entity instance is arrived at by using the lowest matching instance ID at each level of the entity hierarchy where a wildcard is used. (See Targetting Wildcarded Entity Instances for the principle on which an entity instance is targeted.) This routine can also be used to examine all or some of the attribute values of a subset of instances of a given class code by providing a range of instance IDs. It shows step by step all the entity instances of a given class code using the following algorithm: ss7_mgt_show_next(wildcarded entity name) while response code != NOOTHERINSTANCE loop ss7_mgt_show_next(entity name returned in the last output list) end loop To check all or some of the attribute values of a subset of instances of a given class code a range must be delimited. For example, to check attribute values for all destinations in the range 100 to 200, the algorithm is: 1-4 New Features in DECss7 V3.1-A New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances ss7_mgt_show_next("FEP * MTP3 DESTINATION 99" input list) while response code != NOOTHERINSTANCE and then destination id returned in the last output list <= 200 loop ss7_mgt_show_next(entity name returned in the last output list) end loop If required, the SHOW_NEXT_AND_RESET functionality can be activated to show some attribute values and to reset the counters on the next entity. The attributes are specified in input_list, which contains a set of attribute identifiers. This is a Show_List. Possible STATUS values for input_list are: NO_STATUS. SHOW_NEXT_AND_RESET. When STATUS is set to SHOW_NEXT_AND_RESET in the input_ list parameter the SHOW_NEXT_AND_RESET functionality for resetting the counters on the entity concerned is activated. This routine uses the same type of TLV structure for its input list as the ss7_mgt_show routine. See the description of this routine in the DECss7 Management Application Development Guide. There is an input_list for three types of Show_List: this routine can be used to display all the attributes of all attribute groups, all the attributes in one or more attribute groups, or individual attributes of one or more attribute groups. 1.3.2 Wildcarding of Instances of Multi-instantiable Entity Classes The asterisk (*) wildcard character can replace the instance ID of multi-instantiable entities. Instances of the following entities can be wildcarded: o TRUNK o DATA_LINK o DESTINATION o LINKSET o APPLICATION o ROUTE New Features in DECss7 V3.1-A 1-5 New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances o LINK o MTP_BEP o SCCP_BEP o TCAP_BEP o USER_APPL Wildcarding applies to the instance ID only. You cannot wildcard the class code of these entities. Therefore, the following syntax is valid: FEP_SUBSYSTEM DENTI MTP3 LINKSET * FEP_SUBSYSTEM * MTP3 LINKSET 2 LINK * FEP_SUBSYSTEM DENTI MTP3 LINKSET * LINK * BEP_SUBSYSTEM PADOVA TCAP_BEP * Erroneous Application of a Wildcard If you apply a wildcard to the wrong category, a failure value is returned. If you apply the wildcard to the class name of a single instance entity, the value SS7_INVWILDENT is returned. The single instance entities are the SS7 Level entities (MTP2, MTP3, SCCP, and TCAP_FEP) . If you substitute a wildcard for a class code, such as LINKSET or LINK, the value SS7_INVWILDENT is returned. If you apply a wildcard to the subsystem instance of the BEP_SUBSYSTEM, the failure value SS7_NODEUNREACH is returned, because the distributed request mechanism is not implemented on the BEP subsystems. Targetting Wildcarded Entity Instances If you wildcard instance IDs at different levels in the entity hierarchy, the request targets the lowest level reference in the entity hierarchy. For example, if you apply the ENABLE action with the following syntax: FEP_SUBSYSTEM * MTP3 LINKSET * LINK * it will enable all the LINK instances in all the linksets, provided that you have previously enabled all the LINKSET 1-6 New Features in DECss7 V3.1-A New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances instances. You cannot target instances in more than one entity class with the same request. If you use a wildcard to designate all the instances of a higher level entity class, the request still targets the instances of the lower level entity class. For example, if you apply the ENABLE action with the following syntax: FEP_SUBSYSTEM * MTP3 LINKSET * LINK 1 it will enable each LINK instance designated as link 1 in all the linksets. Management Request Routines that Do Not Support Wildcarding The following Request routines do not support wildcarding: o ss7_mgt_create o ss7_mgt_show o ss7_mgt_sccp_disable_report o ss7_mgt_sccp_enable_report o ss7_mgt_ACTION with the following action codes: - SS7_MGT_K_ACT_CONNECT - SS7_MGT_K_ACT_DISCONNECT - SS7_MGT_K_ACT_SAVE_CONFIG - SS7_MGT_K_ACT_RECONFIGURE - SS7_MGT_K_ACT_LOAD_GTT_STBY - SS7_MGT_K_ACT_SWITCH_GTT_TABLE - SS7_MGT_K_ACT_COPY_GTT_ACTIVE If these routines are called with a wildcarded instance ID of a multi-instantiable entity as indicated in Section 1.3.2, the failure value SS7_WILDNOTSUPP is returned. The output list returned is: - Response_Code: SS7_WILDNOTSUPP - Timestamp: BinAbsTim New Features in DECss7 V3.1-A 1-7 New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances If these routines are called with a wildcarded category that does not match the instance ID of a multi-instantiable entity as indicated in Section 1.3.2, that is with the wildcard applied to: o The class name of a single instance entity o A class code the failure value SS7_INVWILDENT is returned. The output list returned is: - Response_Code: SS7_INVWILDENT - Timestamp: BinAbsTim Management Request Routines that Support Wildcarding The following Request routines support wildcarding: o ss7_mgt_action with the following actions: - SS7_K_ACT_ENABLE_ENTITY - SS7_K_ACT_DISABLE_ENTITY - SS7_K_ACT_ACTIVATE - SS7_K_ACT_DEACTIVATE - SS7_K_ACT_LINKTEST - SS7_K_ACT_LOOPBACK - SS7_K_ACT_INHIBIT - SS7_K_ACT_UNINHIBIT - SS7_K_ACT_INIT_LINK_CTL - SS7_K_ACT_CLOSE_DIALOGS o ss7_mgt_add o ss7_mgt_delete o ss7_mgt_disable_event o ss7_mgt_enable_event o ss7_mgt_modify o ss7_mgt_remove o ss7_mgt_show_next 1-8 New Features in DECss7 V3.1-A New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances o ss7_mgt_sccp_send_primitive These management routines operate on each entity that matches the set of entity instances defined through the wildcarded instance IDs. The operation is applied in ascending order of instance ID. If an error occurs on one or more of the entity instances, processing is not interrupted. Processing continues with the next entity instance (if there is one). Only one output list is returned from the FEP or the BEP subsystem. The following reponse values can be returned: SS7_NORMAL When the operation is performed successfully on each affected entity instance. SS7_PARTCOMPLETED When the operation is successfully performed on some of the affected entity instances; that is, at least one value SS7_NORMAL is returned. Information messages are logged as SYSLOG messages to indicate what types of error occurred and on which entity instances. SS7_MULTIPLEERROR When the operation is not performed on any of the affected entity instances and different errors occurred; that is, there is no value SS7_NORMAL returned. Information messages are logged as SYSLOG messages to indicate what types of error occurred and on which entity instances. A failure value not specific to wildcarding When the operation is not performed on any of the affected entity instances and the error that occurred is the same for all instances; that is, there is no value SS7_NORMAL returned. The value returned is one of the failure values allowed for the routine applied. The name of the entity instance returned in the output list is the last instance processed. ________________________ Note ________________________ The following actions: o SS7_K_ACT_INIT_LINK New Features in DECss7 V3.1-A 1-9 New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances o SS7_K_ACT_ACTIVATE o SS7_K_ACT_DEACTIVATE o SS7_K_ACT_INHIBIT o SS7_K_ACT_UNINHIBIT o SS7_K_ACT_LOOPBACK o SS7_K_ACT_LINKTEST when performed on a DATA_LINK or LINK entity return SS7_NORMAL when the action is successful, whether the data link or the link is located on the local or a remote FEP machine. ______________________________________________________ If these management routines are called with a wildcarded entity instance ID that does not match the instance ID of a multi-instantiable entity as indicated in Section 1.3.2, that is with the wildcard applied to: o The class name of a single instance entity o A class code the failure value SS7_INVWILDENT is returned. The output list returned is: - Response_Code: SS7_INVWILDENT - Timestamp: BinAbsTim Management Consolidation Routines With the introduction of the Wildcarding facility, the first of the special cases described in the ss7_mgt_conso_ answer routine is no longer valid. This case concerns the consolidation of responses to the following directives on the LINK entity: o INHIBIT o UNINHIBIT o LOOPBACK o LINKTEST o ACTIVATE 1-10 New Features in DECss7 V3.1-A New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances o DEACTIVATE and to the INIT_LINK_CTL directive on the DATA_LINK entity. See the description of the ss7_mgt_conso_answer routine in the DECss7 Management Application Development Guide. Note that in the special case that concerns the consolidation of attributes with values that vary between FEPs, this consolidation now applies to responses returned through the ss7_mgt_show and ss7_mgt_show_next routines. There is the following addition to the list of the attributes that can vary between FEPs: The list of remote processes considered to be congested or critically congested New characteristics apply to the following entities: - SS7_K_FEPS_CONGPROCLIST (FEP_SUBSYSTEM) - SS7_K_BEPS_CONGPROCLIST (BEP_SUBSYSTEM) - SS7_K_MTPB_CONGPROCLIST (MTP_BEP) - SS7_K_SCCB_CONGPROCLIST (SCCP_BEP) - SS7_K_TCAB_CONGPROCLIST (TCAP_BEP) - SS7_K_FEPS_CRITCONGPROCLIST (FEP_SUBSYSTEM) - SS7_K_BEPS_CRITCONGPROCLIST (BEP_SUBSYSTEM) - SS7_K_MTPB_CRITCONGPROCLIST (MTP_BEP) - SS7_K_SCCB_CRITCONGPROCLIST (SCCP_BEP) - SS7_K_TCAB_CRITCONGPROCLIST (TCAP_BEP) A consolidated list is returned of all processes from all the FEPS concerned by the request. If the same process is reported by different FEPs, it is reported once only in the consolidated list. 1.3.3 Wildcarding in S7MP The following new S7MP commands for displaying data always support the use of wildcards: o SHNEXT o SHNRESET New Features in DECss7 V3.1-A 1-11 New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances Some S7MP commands support wildcarding only if the correct mode is set. Use the SET MODE command with the /SHOWWILD qualifier to set wildcarding mode on or off for the following commands: o SHOW o SHRESET The /SHOWWILD qualifier is set to ON by default. To turn it off, use the following command: SET MODE /SHOWWILD = OFF To turn it on again, use the following command: SET MODE /SHOWWILD = ON When the wildcarding mode is on, the S7MP SHOW and SHRESET commands support the use of wildcards to replace the instance IDs of multi-instantiable entities. When the wildcarding mode is off, the S7MP SHOW and SHRESET commands do not support the use of wildcards to replace the instance IDs of multi-instantiable entities. ________________________ Note ________________________ This behaviour of the SHOW and SHRESET commands, where the ability to support the use of wildcards can be turned on or off by setting the /SHOWWILD mode, is specific to S7MP. The DECss7 directives SHOW and SHOW_ AND_RESET do not support wildcarding; the Management API routine ss7_mgt_show, with or without the STATUS value SHOW_AND_RESET, does not support wildcarding. ______________________________________________________ 1.3.4 The DECss7 Management ss7_mgt_show_next Routine and GUP The DECss7 Management routine ss7_mgt_show_next provides a means of addressing a SHOW_NEXT directive to a user application that uses the GUP API. The DECss7 Management SHOW_NEXT directive is applied to an instance of the USER_ APPL entity. This entity can be wildcarded only in an ss7_ mgt_show_next request. 1-12 New Features in DECss7 V3.1-A New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances Wildcarding of Instances of the USER_APPL entity The wildcard character asterisk (*) can be substituted for the instance ID of the USER_APPL entity in an ss7_mgt_ show_next request. The instance ID of a USER_APPL entity is the name of the highest entity in a user-defined entity hierarchy. DECss7 Management requires the following syntax: BEP_SUBSYSTEM USER_APPL |* [ |* ...] An example of a user-defined entity hierarchy using wildcarded syntax is: BEP_SUBSYSTEM PADOVA USER_APPL * CIRCUITGROUP * CIRCUIT * and: BEP_SUBSYSTEM PADOVA USER_APPL * BRIDGE * LINE * DECss7 only handles user-defined entities at the level of the USER_APPL entity. The rest of the entity hierarchy is of no interest and must be managed by the user application. Therefore, even if the entity names of user-defined subordinate entities appear in the syntax, DECss7 discounts them. DECss7 Management handles a wildcard at the level of the USER_APPL instance ID only for the GUP API. If the instance IDs of any subordinate user-defined entities are wildcarded, the user application must handle the wildcarding of these instances. ________________________ Note ________________________ The instance IDs are the only part of an entity name that can be wildcarded in DECss7. ______________________________________________________ If any request other than ss7_mgt_show_next applies a wildcard to the USER_APPL entity, the failure return value is SS7_REJFAILED (wildcard not allowed). New Features in DECss7 V3.1-A 1-13 New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances Response of the GUP API to ss7_mgt_show_next The ss7_mgt_show_next request activates the SHOW_NEXT callback in the GUP API. If the instance of the USER_APPL entity is wildcarded, the targeted entity will be the first known instance in alphabetical order. For example, if the instances of the USER_APPL entity are ISUP and SWITCH, ISUP will be the targeted instance. If the instance of the USER_APPL entity is not wildcarded, the rules for targetting the entity instance are: o If the syntax does not refer to child entities of the USER_APPL entity, the targeted instance of the USER_ APPL entity is the next known USER_APPL instance in alphabetical order. For example, if the instances of the USER_APPL entities are ISUP, MAP, and SWITCH: BEP_SUBSYSTEM PADOVA USER_APPL ISUP the targeted instance from this syntax is MAP. o If the syntax refers to child entities of the USER_APPL entity, the targeted entity is the one specified by the full entity name and the user application is responsible for finding the next instance. For example: BEP_SUBSYSTEM PADOVA USER_APPL SWITCH CIRCUIT_GROUP 2 CIRCUIT 12 The user application must find the next instance of the CIRCUIT entity. If there is no known next instance of the USER_APPL entity in alphabetical order, the response value returned is SS7_ NOOTHERINSTANCE. To activate this behaviour of the GUP API you must use the compile time flag SS7_GUP_V31P_API when you compile your application. Enter the following with the command on the compiler command line: CC/DECC /DEFINE=SS7_GUP_V31P_API 1-14 New Features in DECss7 V3.1-A New Features in DECss7 V3.1-A 1.3 Wildcarding of Entity Instances This compile time flag provides access to the version of the GUP API with the ss7_user_init routine that has a new parameter, version, and the list_of_callbacks parameter that has the SHOW_NEXT indication: Synopsis unsigned int ss7_user_init ( char* identification, unsigned long identification_length, unsigned long version, ss7_gup_callbacks_vector_t* list_of_callbacks ); version The input parameter version is for backwards compatibility. It determines which version of the GUP API the application uses and therefore whether the SHOW_NEXT feature is available or not. The value of this parameter must be set to SS7_K_USER_V31P_API, which is defined in the file SS7_ MGT_K_COMMON.H. . New Features in DECss7 V3.1-A 1-15 2 _________________________________________________________________ Change History 2.1 Changes between V3.1-A and V3.1-B 2.1.1 Cannot send more than 252 bytes in UNITDATA (S30-191) Description When sending an SCCP UNITDATA message with the maximum allowable user data size (255 bytes according to Q.713 section 4.10 Table 11) DECss7 SCCP API returns an SCCP Notice message and S7MP receives a "SEGERR" event. It is only possible to send 252 bytes of user data in SCCP Unitdata messages. Solution This problem has been corrected. 2.1.2 S7MP may sometimes crash while a trace file is still open (S30-262) Description The S7MP management utility process may crash when an EXIT command is performed while a trace file is still open. Solution This problem has been corrected. 2.1.3 The first S7MP command following a comment line is not executed (S31-163) Description A script file containing a comment line (a line starting with a "!") is not correctly executed by S7MP when the script file is defined as the standard input device ($ DEFINE TT SCRIPT_FILE.S7MP). The first S7MP command following the comment line is not executed by S7MP. Solution This problem has been corrected. Change History 2-1 Change History 2.1 Changes between V3.1-A and V3.1-B 2.1.4 FEP crash when receiving a corrupted TCAP message (S31-166) Description It may occur that the FEP process crashes if a corrupted TCAP message is received. The TCAP message must contain a length byte coded as long form (length > 128 coded on length-128 bytes). If the length is badly formatted, a crash will result. Solution This problem has been corrected. 2.1.5 TCP connection lost on keep alive message reception (S31-173) Description The TCPCM connection drops at the reception of the keep alive timer (KEEPALITIM). Solution This problem has been corrected. 2.1.6 PPLRTL A special version of PPLRTL.EXE is included in this kit. It solves the cluster deadlock problems. 2.2 Changes between V3.1-B and V3.1-C 2.2.1 BEP crashes if entity names are not padded to 64 characters (S31-118) Description When using the DECss7 management API, with the length of the entity names different from 64 characters, the BEP may crash or some commands (e.g. ss7_mgt_create, ss7_mgt_show, ss7_mgt_enable_event, ...) may be rejected. Solution This problem has been corrected. 2-2 Change History Change History 2.2 Changes between V3.1-B and V3.1-C 2.2.2 The GTT rule modification is not effective until the platform is stopped and restarted (S31-190) Description The modification of GTT rule translation appears to have been successful when you use the gtt_rule_show, but in fact the bahaviour of the platform remains as defined by the GTT rules before the modification was made. The modification is only effective if the platform is stopped and restarted. Solution This problem has been corrected. 2.2.3 FEP in timeout state on SENDMSG command (S31-194) Description The FEP enters the timeout state just after the SENDMSG command is performed and DPCNBMAX <= 2. Solution This problem has been corrected. 2.2.4 API management problem (S31-218) Description Problems happen when using the management API in order to disable, enable, block and unblock ISUP circuits asynchronously. Some commands seem not to be executed (reception of timeout). Solution This problem has been corrected by adding a delay. 2.2.5 Corrupted associations after halt button used (S31-220) Description After halting members of a distributed platform with the HALT button, these members cannot be reintegrated into the platform after reboot. Solution This problem has been corrected. Change History 2-3 Change History 2.2 Changes between V3.1-B and V3.1-C 2.2.6 TCAP_ENABLE_INDIC called from thread fails with accvio (S31P-011) Description An application that creates a thread from which one of the following function is called, fails with access violation: ss7_is41_enable_indic() ss7_tcap_enable_indic() ss7_sccp_enable_indic() ss7_mtp_enable_indic() Solution This problem has been corrected. 2.2.7 ENAEVT/DISEVT does not work on wildcarded BEP subentities (S31P-014) Description The S7MP ENAEVT/DISEVT management commands on wildcarded BEP subentities do not work. For example: ENAEVT BEP BEP_NAME TCAP */ALL => does not enable events DISEVT BEP BEP_NAME TCAP */... => does not disable events Solution This problem has been corrected. 2.3 Changes between V3.1-C and V3.1-D 2.3.1 DUPLISU characteristic is lost when the DNSES board is restarted (S30-279) Description For some reasons, the DNSES board restarts by itself. In that case, the MTP2 DUPLISU characteristic is lost and the FW doesn't ensure the report of 2 consecutives FISUs. Solution This problem has been corrected. 2.3.2 ANSI protocol does not check LI when greater than 2 (S31-178) Description On ANSI protocol, no matching is done between LI and the size of the MSU when LI > 2. 2-4 Change History Change History 2.3 Changes between V3.1-C and V3.1-D Solution This problem has been corrected. The DNBC4 firmware must be updated using ss7configure to make this change effective. 2.3.3 Spurious blank in S7MP configuration file (S31-224) Description Under S7MP, there is a problem in configuration files when a blank follows a continuation line (-) character. Solution This problem has been corrected. 2.3.4 Overloading of SS7 links (S31-227) Description Links are overloading because messages are being bounced back and forth. Solution This problem has been corrected. 2.3.5 FEP crash when application with appid 1 or 255 dies (S31-234) Description When a GDI application created with application id 1 or 255 dies, the FEP crashes. Solution This problem has been corrected. 2.3.6 MGT command output is not complete when node is unreachable (S31-246) Description When a MGT command is issued by a MGT application (including S7MP and ISUPMP) to an UNREACHABLE node, the DIR process returns the proper error code to the caller, i.e., NODE UNREACHABLE, but some parameters are missing. The field Entity_name must be the FULL NAME but actually contains only the NODE name. For example, when "ENABLE FEP COCTO MTP3 LINKSET 1 LINK 1" is issued with the node COCTO not present from the point of view of the DIR process, the entity name in the response is Change History 2-5 Change History 2.3 Changes between V3.1-C and V3.1-D "FEP_SUBSYSTEM COCTO" instead of "FEP_SUBSYSTEM COCTO MTP3 LINKSET 1 LINK 1". Solution This problem has been corrected. 2.3.7 Error from STARLET when using GUPPORT with ISUPMP (S31P-037) Description When using the GUPPORT API with ISUP and the MGTPORT API with ISUPMP, STARLET reports in SS7logfile the error: Feb 10 17:50:41 BITIX SS7 [2605]: DECss7 message from APPLI ISUP C Feb 10 17:50:41 BITIX SS7 [2605]: @SS7-F-UNEXCPERR, Unexpected subsystem error ["starlet__qio.cpp":441] Feb 10 17:50:41 BITIX SS7 [2605]: Status is : @SS7-F-SOFTERROR, service not implemented Solution A call to QIOW has been replaced by a call to QIO (like the original version). Indeed, in that case QIOW is not compulsory. 2.3.8 TCAP Application cannot be put in service (S31P-041) Description When a TCAP application designed over the non portable API is created and then enabled, the managment returns the "EXCEPTION IN ACTION" message and the application is not put in service. Solution This problem has been corrected. 2.3.9 When a TCAP application is disabled under load, it cannot be re-enabled (S31P-042) Description If a TCAP application is disabled under traffic and then it is re-enabled, the FEP sends network messages to this application copy, but these messages are never delivered to the application. After a while the FEP enters congestion. Solution This problem has been corrected. 2-6 Change History Change History 2.3 Changes between V3.1-C and V3.1-D 2.3.10 CONGPROC and CRITCONGPROC FEP attributes not updated when application dies (S31P-045) Description The CONGPROC and CRITCONGPROC FEP attributes are not updated when an application dies. Solution This problem has been corrected. 2.3.11 CRITCONGPROC FEP attribute is not reset after congestion (S31P-046) Description The CRITCONGPROC FEP attribute is not reset after an application exits the congestion state. Solution This problem has been corrected. 2.4 Changes between V3.1-D and V3.1-E 2.4.1 User application could crash when calling ss7_sccp_decode_party_address (S31-261) Description User application could crash randomly (due to garbage in the stack) when calling ss7_sccp_decode_party_address. Solution This problem has been corrected. 2.4.2 Number of max GTT rules increased from 2000 to 4000 (S31-266) Description The product limitation for the max number of GTT rules is 2000. Customer requested that this value be increased. Solution The limitation for the max number of GTT rules has been raised to 4000. Change History 2-7 Change History 2.4 Changes between V3.1-D and V3.1-E 2.4.3 User distribution function ss7_ud_zzz_fep_indication called twice (S31-269) Description The user distribution function ss7_ud_zzz_fep_indication (where zzz = MTP, SCCP, TCAP) is called twice when a FEP re-joins a platform. Solution This problem has been corrected. 2.4.4 Output List incomplete when Node Unreachable message received (S31-271) Description In dual-monolithic platform, when shutting down one of the two machines and sending MGT messages to it, the other one receives an incomplete output list. Indeed, the Instance Id of the Entity Name when Entity is a User Application is 8 octets long max (see MADG V3.1-P section 2.3.4.3 fig 2-10). However, this field should contain, for example: "isup tkgp 1 tk 4 cct 1 /stat", i.e., the command which fails. Solution The size of the field Instance Id of the Entity Name when Entity is a User Application is now 64 octets long (with padding to 0x20 - space at the end of the instance id). This field is updated with the complete command when it fails. 2.4.5 Bad incrementation of counters for SCCP relay function (S31-276) Description When using the SCCP relay function, an incoming message, correctly translated on the FEP level, is redirected to the network according to the value of the DPC. However, the counters at the SCCP level are badly incremented. S7MP_C> sho fep * sccp /cou FEP target list : SMFT00 Number of FEP target : 1 2-8 Change History Change History 2.4 Changes between V3.1-D and V3.1-E Attribute Group : Counters SCCP Creation Time (CREATIME) : SS7_K_NO_CONSO Nb software errors (SWNBERROR) : 0 Class 0&1 Msg Sent (SNT01) : 1 Class 0 Msg Sent (SNT0) : 0 Class 1 Msg Sent (SNT1) : 0 <= ERROR UDTS Messages Sent (UDTSNT) : 0 Class 0&1 Msg Rcv (RCV01) : 1 Class 0 Msg Rcv (RCV0) : 0 Class 1 Msg Rcv (RCV1) : 1 Local SSN Msg Rcv (LSSNRCV) : 0 UDTS Messages Received (UDTSRCV) : 0 Unknown Reason Routing Fail. (NUNRSRF) : 0 Unequipped User Routing Fail. (NUNQURF) : 0 Prohibited SSN Routing FaiL. (NPSSNRF) : 0 Congested SSN Routing Failure (NCSSNRF) : 0 Prohibited SPC Routing Fail. (NPSPCRF) : 0 Congested SPC Routing Failure (NCSPCRF) : 0 Syntax Error (NSYNTXER) : 0 SCCP Mgt requests dicarded (NMGTRQDISC) : 0 Msg disc : not delivered (DISTDISC) : 0 Msg not sent to others subs. (USERDISC) : 0 NGTT_OK msg received (NGTTOK) : 1 NGTT_NOTRANS msg received (NGTTNOTRANS) : 0 OVF msg received (OVF) : 0 NGTT_MTPFAIL msg received (NGTTMTPFAIL) : 0 NGTT_SSNFAIL msg received (NGTTSSNFAIL) : 0 NRELAYED_UDT msg received (NRELAYEDUDT) : 1 XUDT msg received (XUDTRCV) : 0 XUDT msg sent (XUDTSNT) : 0 XUDTS msg received (XSUDTRCV) : 0 XUDTS msg sent (XSUDTSNT) : 1 <= ERROR Number of Segmentation error (NSEGERR) : 0 Number of Reassembly error (NREAERR) : 0 Number of discarded segment (SEGMDISC) : 0 Solution This problem has been corrected. Change History 2-9 Change History 2.4 Changes between V3.1-D and V3.1-E 2.4.6 SAVE_CONFIG fails with SLTUSE=DEACT (S31-282) Description Issuing "SAVE_CONFIG FEP *" after having created a link with the SLTUSE=DEACT attribute, is not stored in the SS7_ SAVE_CONFIG.DAT file. Solution This problem has been corrected. 2.4.7 Constant SS7_K_INVALID_ATTRIBUTE missing (S31P-052) Description The constant SS7_K_INVALID_ATTRIBUTE associated to the STATUS field of the OUTPUT LIST AddRem_Status in ss7_mgt_ add() routine is missing. Solution This problem has been corrected. 2-10 Change History 3 _________________________________________________________________ Known Problems This chapter lists the known problems of DECss7 that are unresolved at V3.1-E/ITU-T. 3.1 Known Problems 3.1.1 Crash of FEP/BEP/DIR process if a connection problem occurs (S24-082) Description This problem occurs only when DECnet is used as the transport protocol. If a problem occurs when a connection is being established, the connection between two processes is closed by one of the two parties. On the other party, an indication is sent to the DECss7 process by the DECnet shareable image (advising that the connection has closed). Solution Ensure there is a 10 seconds delay between the start of each DECss7 process. 3.1.2 Low Priority of FEP Process May Cause SS7 Link Failure (S25-047) Description When a FEP process is started with a priority lower than the other user processes, a high CPU load may lead to the loss of SS7 link alignment. This problem can occur because the FEP cannot send the acknowledgemnt on each link within the period allowed by the T7 timer. The links go down because of the excessive delay in acknowledgement; that is, when the T7 timer expires at the remote end, the links are dropped. Known Problems 3-1 Known Problems 3.1 Known Problems Solution The workaround for this problem is to accord the FEP higher priority than all the user processes. Use the SH SYS command to obtain the FEP process ID and the SET PROCESS command to set the new, higher priority of the FEP. For example: $ SH SYS . . . $ SET PROC /ID= /PRIORITY= 3.1.3 Platform overload: Traffic peak _______________________ Caution _______________________ A medium level problem has been identified on this kit. This problem occurs only with DNBE1 or DNBT1 interface boards. ______________________________________________________ When the platform is overloaded because the traffic peaks, leading the FEP to enter into congestion, it may appear that the FEP temporarily consumes additional memory. When the traffic comes back to normal, the platform recovers properly from congestion, but the memory is not released. This does not prevent normal platform behaviour. If the traffic peak lasts long enough: o the entire memory could be used up and the FEP must be restarted o it may look as if the FEP cannot communicate with the board and the FEP must be restarted The conditions leading to this problem are considered difficult to produce. The problem is currently being analyzed, and the fix will be available in a future maintenance release of DECss7 V3.1. 3-2 Known Problems Known Problems 3.1 Known Problems 3.1.4 DNBE1 - Traffic restrictions Description Above the limits defined hereafter, the system may become too congested and the connection between the FEP and the boards may be lost. In such a case, the event SS7_K_TRNK_LOST is raised, and all the data-links already created on the boards fail in the OUT_OF_SERVICE state and are shown as 'SS7_K_DTLK_ UNKNOWN' from the management part. (See paragraph "Event SS7_K_TRNK_LOST" below.) DNBx1 board performance Depending on the number of links and the size of the messages, a DNBx1 HIGH PERFORMANCE board is able to handle from 800 to 850 TPS, using 100% of the board's CPU. FEP performance A 2-CPU AlphaServer 4100 5/466 is able to handle 30 links at 1 erlang split between 2 DNBE1 boards, totaling 1395 TPS, using 88% of the CPU. It should be able to handle 32 links with the remaining 12% of the CPU, totaling 1480 TPS. A 2-CPU AlphaServer 4100 5/533 is able to handle 48 links at 0.72 erlang split between 2 DNBE1 boards, totaling 1607 TPS, using 76% of the CPU. It should be able to handle more links, or more TPS (depending on the message size, around 2000 to 2200 TPS). Performance examples Using the following software configuration: o DIGITAL UNIX V4.0D o DECss7 V3.1-1 ITU-T o DNBE1 HIGH PERFORMANCE boards, firmware version 3.1/2.2 o MGTS V10.0 o Message size: 172 bytes for both incoming and outgoing messages With the following hardware configuration: Known Problems 3-3 Known Problems 3.1 Known Problems 1) Configuration 5/466 o BEP: Alpha Server 4100 5/466 1 CPU, 256 MB memory, 4 Application copies (TCAP loopback) o FEP: Alpha Server 4100 5/466 2 CPU, 256 Mb memory, 2 DNBE1 HIGH PERFORMANCE boards Test results Total links Links on Links on Link load TPS on FEP CPU TPS on TPS on on the FEP 1st board 2nd board (erlang) the FEP idle 1st board 2nd board 30 16 14 1 1395 12% 744 651 16 16 0 1 744 55% 744 0 24 24 0 0.75 837 50% 837 0 Notes: o 1 TPS = 1 TCAP Begin message in and 1 TCAP End message out o For the 24 links test, the maximum level of performance of the board has been reached 2) Configuration 5/466 o BEP: Alpha Server 4100 5/466 1 CPU, 256 MB memory, 4 Application copies (TCAP loopback) o FEP: Alpha Server 4100 5/533 2 CPU, 256 Mb memory, 2 DNBE1 HIGH PERFORMANCE boards Test results Total links Links on Links on Link load TPS on FEP CPU TPS on TPS on on the FEP 1st board 2nd board (erlang) the FEP idle 1st board 2nd board 32 16 16 0.80 1190 35% 595 595 48 24 24 0.72 1607 24% 803 803 Notes: o 1 TPS = 1 TCAP message in and 1 TCAP message out o Test Duration: 2 hours o The maximum level of performance of the board has been reached during this test (24 links at 0.72 erlang, with 172 bytes message) 3-4 Known Problems Known Problems 3.1 Known Problems Event SS7_K_TRNK_LOST After reception of the event CNTLOST (SS7_K_TRNK_CNTLOST) on a trunk, the status of all data-links from this trunk become 'SS7_K_DTLK_UNKNOWN' (as seen from the management part) and are failed in state OUT-OF-SERVICE (from the board part). The following workaround can be used to counteract this problem: 1. Deactivate and disable all links of all linksets associated with the trunk For example: DEACTIVATE FEP FEP1 MTP3 LINKSET 1 LINK 1 DEACTIVATE FEP FEP1 MTP3 LINKSET 1 LINK 2 WAIT 5 DISABLE FEP_SUBSYSTEM FEP1 MTP3 LINKSET 1 LINK 2 DISABLE FEP_SUBSYSTEM FEP1 MTP3 LINKSET 1 LINK 1 2. Disable and delete the trunk and the associated data- links For example: DISABLE FEP FEP1 MTP2 DATA_LINK 1 DISABLE FEP FEP1 MTP2 DATA_LINK 2 DISABLE FEP FEP1 MTP2 TRUNK 1 DELETE FEP FEP1 MTP2 DATA_LINK 1 DELETE FEP FEP1 MTP2 DATA_LINK 2 DELETE FEP FEP1 MTP2 TRUNK 1 3. Re-create and re-enable the trunk and its associated data-links For example: CREATE FEP_SUBSYSTEM FEP1 MTP2 TRUNK 1 /DEVNAME=PT37E /FEP=FEP1 CREATE FEP_SUBSYSTEM FEP1 MTP2 DATA_LINK 1 /DEVNAME=PT37E1 /FEP=FEP1 CREATE FEP_SUBSYSTEM FEP1 MTP2 DATA_LINK 2 /DEVNAME=PT37E2 /FEP=FEP1 ENABLE FEP_SUBSYSTEM FEP1 MTP2 TRUNK 1 ENABLE FEP_SUBSYSTEM FEP1 MTP2 DATA_LINK 1 ENABLE FEP_SUBSYSTEM FEP1 MTP2 DATA_LINK 2 4. Enable links associated with the trunks: Known Problems 3-5 Known Problems 3.1 Known Problems For example: ENABLE FEP_SUBSYSTEM FEP1 MTP3 LINKSET 1 LINK 1 ENABLE FEP_SUBSYSTEM FEP1 MTP3 LINKSET 1 LINK 2 5. Init the data-links For example: INIT_LINK FEP_SUBSYSTEM FEP1 MTP2 DATA_LINK 1 INIT_LINK FEP_SUBSYSTEM FEP1 MTP2 DATA_LINK 2 _______________________ Caution _______________________ This S7MP script is an example with one trunk and two links. If you write a management application, you can handle the CNTLOST event and perform all given actions to restart the trunk. ______________________________________________________ 3.1.5 Inconsistent state of Related LINK and DATA_LINK Entities Description For platforms where DNBE1 or DNBT1 devices are installed and configured for use with DECss7, congestion on the host can occur in the event of excessive data flow. This condition can lead to the loss of messages and indications at the interface of the firmware and the host. This in turn can lead to inconsistency in the states of the data link at the MTP2 level and the related link at the MTP3 level. The condition of excessive data flow is identified by the inconsistent states of the data link and its related link. The inconsistent states are given in Table 3-1. Table_3-1_Inconsistent_states_of_Data_Link_and_Link________ Alternative Inconsistent Entity_Inconsistent_State_________State____________________ DATA_ SS7_K_DTLK_OUT_OF_SERVICE SS7_K_DTLK_OUT_OF_SERVICE LINK LINK___SS7_K_LINK_FAILED__________SS7_K_LINK_AVAILABLE_____ 3-6 Known Problems Known Problems 3.1 Known Problems These inconsistent states occur instead of the expected consistent states, shown in Table 3-2, which are required for the SS7 links to work correctly. Table_3-2_Consistent_states_of_Data_Link_and_Link__________ Alternative Consistent Entity_Consistent_State___________State____________________ DATA_ SS7_K_DTLK_INITIAL_ SS7_K_DTLK_IN_SERVICE LINK ALIGNMENT LINK___SS7_K_LINK_FAILED__________SS7_K_LINK_AVAILABLE_____ As a result of one or other of the inconsistent states, the data link may never align. Solution The following workaround can be used to counteract this problem. 1. Deactivate the link at the MTP3 level 2. Activate the link at the MTP3 level For example: DEACTIVATE FEP DENTI MTP3 LINKSET 1 LINK 1 ACTIVATE FEP DENTI MTP3 LINKSET 1 LINK 1 3.2 New Problems in V3.1-E No new restrictions or problems have been found in V3.1-E. Known Problems 3-7 4 _________________________________________________________________ Documentation Errors and Omissions This chapter lists documentation errors and omissions applicable to the DECss7 documentation set. 4.1 Incomplete Description of the report_cause Parameter of the ss7_tcap_notice_indication Routine (S31-092) 4.1.1 Description The description of the report_cause parameter of the ss7_ tcap_notice_indication_xxx routine is incomplete. This parameter is an unsigned long, but only the byte of lower order of this unsigned long is meaningful and DECss7 does not reset the other bytes to 0. Therefore, only the value of the last byte must be used. 4.1.2 Solution The DECss7 Application Development Guide has been updated accordingly for the next release of the documentation. 4.2 Inappropriate Platform Tuning for the Portable API (S31-127) 4.2.1 Description In the DECss7 Platform User's Guide the section Setting the size of the Management API mailbox is inappropriate and must be removed. Tuning of this nature cannot be done under the portable API, which is the only type of API supported in the user documentation. 4.2.2 Solution This section has been removed for the next release of the documentation. Documentation Errors and Omissions 4-1 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual This chapter describes the indexed objects in the MIB structure dependent on the trapParam inaccessible object. They are not mapped onto DECss7 Constants. These objects are dependent on the containment tree illustrated in Figure 4-1. Other traps are mapped onto DECss7 events or PSI, and others are reported at Agent initialization time or report platform inconsistencies. Table 4-2 lists the traps mapped onto DECss7 events. Table 4-3 lists the traps mapped onto PSI. Table 4-4 lists the traps reported at Agent Initialization time. Table 4-5 lists the traps reporting platform inconsistencies. 4-2 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual 4.3.1 trap_param Table 4-1 shows the trapParam indexed objects. Table_4-1_trapParam_Indexed_objects______________________________ MIB_Object_(OID)____Description__________________________________ trapTime(1) The DECss7 timestamp of trap trapType (2) The type of the trap trapEntityName Entity name of the DECss7 Event (3) trapNodeName (4) Node name field of the DECss7 PSI trapProcessName If the Process Type is APPL, the ProcessName (5) will match The Process Name field of the DECss7 PSI trapCause(6) The probable cause of the last received trap trapSeverity (7) The severity of the last received trap trapText (8) Supplementary information about the event trapPlatformId Platform ID (99)_____________________________________________________________ 4.3.2 Traps Mapped on DECss7 Events Table 4-2 lists the traps mapped onto the different DECss7 Events. The traps are listed in groups according to the DECss7 component. Table_4-2_Traps_mapped_on_DECss7_________________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ FEP fepCongestionOn SS7_K_FEPS_CS_ Begin FEP Subsystem CONGON alarm congestion. fepCongestionOff SS7_K_FEPS_CS_ End FEP Subsystem CONGOFF alarm no longer congested. (continued on next page) Documentation Errors and Omissions 4-3 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ fepStorageError SS7_K_FEPS_STOERR Info Storage error. alarm fepLogFileFull SS7_K_FEPS_LOGFULL Info Log file full. alarm fepConnectLostWithSuSS7_K_FEPS_CONLOST Info Connection alarm with another subsystem lost. fepAssoLostWithApplCSS7_K_FEPS_ Info Association COPYASSOLOST alarm with an Application copy lost. fepCongestionHigh SS7_K_CS_CONGHIGH Info FEP Subsystem alarm highly congested. DATA_LINK dtlkLinkFailAllReasoSS7_K_DTLK_MAJFAIL Begin Link failure alarm for all reasons. dtlkExcessDelayAck SS7_K_DTLK_XSDACK Begin Excessive alarm delay of ACK dtlkExcessErrorRate SS7_K_DTLK_XSERRATE Begin Excessive alarm error rate. dtlkExcessRemoteCongSS7_K_DTLK_XSRCONG Begin Excessive alarm remote congestion. dtlkCongestionStart SS7_K_DTLK_STACONG Begin Start of alarm congestion. dtlkInitialAlignFailSS7_K_DTLK_ALIFAIL Begin Initial alarm alignment failure. (continued on next page) 4-4 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ dtlkStartRemProcOutaSS7_K_DTLK_REMOUT Begin Start of alarm remote processor outage. dtlkEndRemProcOutageSS7_K_DTLK_REMREC End End of remote alarm processor outage. dtlkLinkInService SS7_K_DTLK_INS End Link in alarm service. dtlkCongestionEnd SS7_K_DTLK_ENDCONG End End of alarm congestion. dtlkCongestionDiscarSS7_K_DTLK_CONGDISC Info Congestion alarm discard. dtlkDriverInfo SS7_K_DTLK_DRIVINF Info Driver alarm information. TRUNK trunkConnectionLost SS7_K_CNT_LOST Begin Connection alarm lost. trunkCriticalAlarm SS7_K_CRITALRM Begin Critical alarm alarm. trunkConnectionRecovSS7_K_CNTREC End Connection alarm recovered. trunkCriticalAlarmOfSS7_K_CRITALRMOFF End Critical alarm alarm off. MTP3 mtp3OrigMsuDiscardInSS7_K_MTP3_MSUDISC Info Originating alarm MSUs discarded because of invalid PC. mtp3TfmTcmRejected SS7_K_ Info TFM or TCM TFMTCMREJECTED alarm rejected. (continued on next page) Documentation Errors and Omissions 4-5 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ mtp3CongestionStarteSS7_K_MTP3_CONG Begin Congestion alarm started. mtp3NoMoreCongestionSS7_K_MTP3_NOCONG End No longer alarm congested. DESTINATION destStartOfInaccess SS7_K_DEST_STAINAC Begin Start of alarm Inaccessibility. destCongested SS7_K_DEST_CONG Begin Destination alarm congested. destEndOfInaccess SS7_K_DEST_ENDINAC End End of alarm Inaccessibility. destNoMoreCongestionSS7_K_DEST_NOCONG End End of alarm congestion. destMsuDiscardedInacSS7_K_DEST_ Info MSU discarded MSUINACPC alarm because of inaccessible PC. destTempoDestCreatedSS7_K_DEST_ Info Temporary TEMPODESTCREATED alarm destination created. destTempoDestDeletedSS7_K_DEST_ Info Temporary TEMPODESTDELETED alarm destinantion deleted. ROUTE routeRestricted SS7_K_ROUT_ Begin Route RESTRICTED alarm restricted. routeProhibited SS7_K_ROUT_ Begin Route PROHIBITED alarm prohibited. routeAllowed SS7_K_ROUT_ALLOWED End Route allowed. alarm routeDisabled SS7_K_ROUT_DISABLED Info Route alarm disabled. (continued on next page) 4-6 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ LINKSET linksetStartOfUnavaiSS7_K_LKST_ Begin Start of STAUNAVAIL alarm Linkset un- availability. linksetEndOfUnavail SS7_K_LKST_ End End of Linkset STOUNAVAIL alarm unavailabil- ity. The Linkset is available. LINK linkMsgDiscarded SS7_K_LINK_RCVIDPC Info Invalid DPC alarm received. linkMsgDiscarded SS7_K_LINK_RCVINI INFO Invalid NI alarm received. linkMsgDiscarded SS7_K_LINK_RCVISIO Info Invalid SIO alarm received. linkMsgDiscarded SS7_K_LINK_RCVIHC Info Invalid HC alarm received. linkMsgDiscarded SS7_K_LINK_RCVILGH Info Message with alarm invalid octet count received. linkMsgDiscarded SS7_K_LINK_RCVIPROT Info Unexpected alarm message received. linkMsgDiscarded SS7_K_LINK_RCVISLC Info Invalid SLC alarm received. linkT2TimeOut SS7_K_LINK_TIM2TO Info T2 timer alarm timeout. linkT5TimeOut SS7_K_LINK_TIM5TO Info T5 timer alarm timeout. (continued on next page) Documentation Errors and Omissions 4-7 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ linkSlInhibited SS7_K_LINK_SLINH Begin SL inhibited. alarm linkSlUninhibited SS7_K_LINK_SLUNIH End SL alarm uninhibited. linkInhibitDenied SS7_K_LINK_INHDEN Info Inhibition alarm denied. linkUninhibitNotPossSS7_K_LINK_UINHNPOS Info Uninhibit not alarm possible. linkLocalAutoChangeOSS7_K_LINK_ACHOVER Begin Local alarm automatic changeover. linkSiRestoration SS7_K_LINK_LRESTO End SL alarm restoration. linkLfuSent SS7_K_LINK_LFUSNT Info LFU sent. alarm linkLfuReceived SS7_K_LINK_LFURCV Info LFU Received. alarm linkSltSuccess SS7_K_LINK_SLTSUCC Info SLT success. alarm linkSltFailed SS7_K_LINK_SLTFAIL Info SLT failed. alarm linkInhibReqTimeOut SS7_K_LINK_ Info Link SLTOINHIB alarm inhibition request timeout. linkUninhibReqTimeOuSS7_K_LINK_ Info Link SLTOUNINHIB alarm uninhibition request timeout. linkRemLinkInhibitedSS7_K_LINK_ Begin Remote Link SLINHIBITREM alarm inhibited. (continued on next page) 4-8 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ linkRemLinkUninhibitSS7_K_LINK_ End Remote Link SLUNINHIBITREM alarm uninhibited. linkCongestedInTb SS7_K_LINK_TBCONG Begin Link congested alarm in TB. linkNotCongestedInTbSS7_K_LINK_TBNOCONG End Link not alarm congested in TB. linkUpuSent SS7_K_LINK_EVUPUSNT Info UPU messages alarm sent. linkUpuReceived SS7_K_LINK_EVUPURCV Info UPU messages alarm received. SCCP sccpRoutingFailure SS7_K_SCCP_UNSRF Info Routing alarm failure, reason unknown. sccpRoutingFailure SS7_K_SCCP_UNQURF Info Routing alarm failure, unequipped user. sccpRoutingFailure SS7_K_SCCP_PSSNRF Info Routing alarm failure, Prohibited SSN. sccpRoutingFailure SS7_K_SCCP_PSPCRF Info Routing alarm failure, Prohibited SPC. sccpRoutingFailure SS7_K_SCCP_CSSNRF Info Routingfailure, alarm Congested SSN. (continued on next page) Documentation Errors and Omissions 4-9 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ sccpRoutingFailure SS7_K_SCCP_CSPCRF Info Routing alarm failure, Congested SPC. sccpSyntaxErrors SS7_K_SCCP_SYNTXERR Info Syntax Error. alarm sccpGttFailure SS7_K_SCCP_GTT_ Info Error while ERRORA alarm translating the given GT. sccpMgmtReqDiscardedSS7_K_SCCP_ Info SCCP MGTREQDISC alarm Management request discarded. sccpSegmentationErroSS7_K_SCCP_SEGERR Info SCCP alarm Segmentation error. sccpReassemblyError SS7_K_SCCP_REAERR Info SCCP alarm Reassembly error. sccpRemoteProblem SS7_K_SCCP_REMDELPB Info SCCP remote alarm problem. TCAP tcapUnknownSccpMsgRcSS7_K_TCAF_USPRRCV Info Unknown SCCP alarm Primitives received. tcapTcNoticeIndNotSeSS7_K_TCAF_NDNOTICE Info TC_NOTICE alarm indication cannot be sent. tcapPAbortSent SS7_K_TCAF_IDURSNT Info P_ABORT not alarm recognized Transaction_ id. (continued on next page) 4-10 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ tcapPAbortSent SS7_K_TCAF_ABUMTSNT Info P_ABORT alarm unrecognized message type. tcapPAbortSent SS7_K_TCAF_ABUTPSNT Info P_ABORT sent alarm incorrect TP. tcapPAbortSent SS7_K_TCAF_ Info P_ABORT sent ABBFTPSNT alarm incorrect TP format. TCPCM tcpcmConnectionRefusSS7_K_TCPM_ Info TCPCM CONNREFUS alarm Connection refused. SITE tcpSiteMsgDiscarded SS7_K_SITE_MSGDISC Info Messages alarm discarded. CONNECTION tcpconnFailure SS7_K_CONN_FAILURE Info Connection alarm attempt failed. tcpconnOK SS7_K_CONN_OK Info Connection alarm established. tcpconnBroken SS7_K_CONN_BROKEN Info Connection alarm broken. tcpconnTransportErroSS7_K_CONN_ERROR Info Transport alarm level error. BEP bepCongestionOn SS7_K_BEPS_CS_ Begin BEP subsystems CONGON alarm congested. bepCongestionHigh SS7_K_BEPS_CS_ Info BEP subsystems CONGHIGH alarm highly congested. (continued on next page) Documentation Errors and Omissions 4-11 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ bepCongestionOff SS7_K_BEPS_CS_ End BEP subsystems CONGOFF alarm no longer congested. bepSubsysFailure SS7_K_BEPS_SYSFAIL Info Subsystem alarm failure. bepLogFileFull SS7_K_BEPS_LOGFULL Info Log file full. alarm bepConnectLostWithSuSS7_K_BEPS_CONLOST Info Connection alarm lost with another subsystem. MTP_BEP mtpBepCongestionOn SS7_K_MTPB_CS_ Begin MTP_BEP CONGON alarm congestion on. mtpBepCongestionOff SS7_K_MTPB_CS_ End MTP_BEP CONGOFF alarm congestion off. mtpBepCongestionHighSS7_K_MTPB_CS_ Info MTP_BEP highly CONGHIGH alarm congested. SCCP_BEP sccpBepCongestionOn SS7_K_SCCB_CS_ Begin SCCP_BEP CONGON alarm congestion on. sccpBepCongestionOffSS7_K_SCCB_CS_ End SCCP_BEP CONGOFF alarm congestion off. sccpBepCongestionHigSS7_K_SCCB_CS_ Info SCCP_BEP CONGHIGH alarm highly congested. (continued on next page) 4-12 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ sccpBepMsgRcvWrongSsSS7_K_SCCB_CS_ Info Message BADSSN alarm received with incorrect SSN. TCAP_BEP tcapBepPAbortRcv SS7_K_TCAB_UNTRCV Info P_ABORT alarm Received, unrecognized message type. tcapBepPAbortRcv SS7_K_TCAB_UTPRCV Info P_ABORT alarm received, incorrect TP. tcapBepPAbortRcv SS7_K_TCAB_BFTPRCV Info P_ABORT alarm received, incorrect TP format. tcapBepPAbortRcv SS7_K_TCAB_IDURRCV Info P_ABORT alarm received, unrecognized Transaction_ id. tcapBepPAbortRcv SS7_K_TCAB_RLRCV Info P_ABORT alarm received, resource limitation. tcapBepPAbortRcv SS7_K_TCAB_ADPRCV Info P_ABORT alarm received, abnormal dialogue portion. tcapBepPAbortSent SS7_K_TCAB_UMTSNT Info P_ABORT sent, alarm unrecognized message type. (continued on next page) Documentation Errors and Omissions 4-13 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ tcapBepPAbortSent SS7_K_TCAB_UPTSNT Info P_ABORT sent, alarm incorrect TP. tcapBepPAbortSent SS7_K_TCAB_BFTPSNT Info P_ABORT sent, alarm incorrect TP format. tcapBepPAbortSent SS7_K_TCAB_IDURSNT Info P_ABORT sent, alarm unrecognized Transaction_ id. tcapBepPAbortSent SS7_K_TCAB_RLSNT Info P_ABORT sent, alarm resource limitation. tcapBepPAbortSent SS7_K_TCAB_ADPSNT Info P_ABORT sent, alarm abnormal dialogue portion. tcapBepRejectRcv SS7_K_TCAB_CTRCV Info Reject alarm received, not global. tcapBepRejectRcv SS7_K_TCAB_UNCRCV Info Reject alarm received, unrecognized component. tcapBepRejectRcv SS7_K_TCAB_MTCRCV Info Reject alarm received, mistyped component. tcapBepRejectRcv SS7_K_TCAB_BSCTRCV Info Reject alarm received, badly structured component. (continued on next page) 4-14 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ tcapBepRejectRcv SS7_K_TCAB_ULIRCV Info Reject alarm received, unrecognized linked_id. tcapBepRejectRcv SS7_K_TCAB_RRIDRCV Info Reject alarm received, unrecognized invoke_id, RR problem. tcapBepRejectRcv SS7_K_TCAB_REIDRCV Info Reject alarm received, unrecognized invoke_id, RE problem. tcapBepRejectRcv SS7_K_TCAB_RRURCV Info Reject alarm received, unexpected RR. tcapBepRejectRcv SS7_K_TCAB_REURCV Info Reject alarm received, unexpected RE. tcapBepRejectRcv SS7_K_TCAB_DIDRCV Info TC user alarm duplicate invoke_id received. tcapBepRejectRcv SS7_K_TCAB_UOPRCV Info TC user alarm unrecognized operations received. tcapBepRejectRcv SS7_K_TCAB_MTPRCV Info TC user alarm mistyped parameters received. (continued on next page) Documentation Errors and Omissions 4-15 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ tcapBepRejectRcv SS7_K_TCAB_RLIRCV Info TC user alarm resource limitation received. tcapBepRejectRcv SS7_K_TCAB_IRRCV Info TC user alarm initiating release received. tcapBepRejectRcv SS7_K_TCAB_ULRRCV Info TC user alarm unexpected linked response received. tcapBepRejectRcv SS7_K_TCAB_ULORCV Info TC user alarm unexpected linked operation received. tcapBepRejectRcv SS7_K_TCAB_UERRCV Info TC user alarm unrecognized error received. tcapBepRejectRcv SS7_K_TCAB_UEXRCV Info TC user alarm unexpected error received. tcapBepRejectRcv SS7_K_TCAB_PRRRCV Info TC user alarm mistyped parameter RR received. tcapBepRejectRcv SS7_K_TCAB_PRERCV Info TC user alarm mistyped parameter RE received. (continued on next page) 4-16 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-2_(Cont.)_Traps_mapped_on_DECss7_________________________ trap Supplementary trap_Name___________DECss7_Event_Mapped___Severity_Information___ tcapBepNoMoreBegin SS7_K_TCAB_ Begin No more Begin NOMOREBEGIN alarm messages. tcapBepBeginAcceptedSS7_K_BEGINAGAIN End Begin messages alarm accepted again. tcapBepCongestionOn SS7_K_TCAB_CS_ Begin TCAP_BEP CONGON alarm Congestion on. tcapBepCongestionOffSS7_K_TCAB_CS_ End TCAP_BEP CONGOFF alarm Congestion off. tcapBepCongestionHigSS7_K_TCAB_CS_ Info TCAP_BEP CONGHIGH alarm highly congested. INAP_SRF inapSrfFailure SS7_ISRF_FAILURE Info INAP_SRF alarm failure. inapSrfTsrfTimeout SS7_ISRF_TOTSRF Info TSRF timer alarm timeout. inapSrfErrorCancel SS7_ISRF_ERRCANCEL Info Error on alarm cancel. inapSrfErrorOpRcv SS7_ISRF_ERRPA Info Error on alarm PlayAnnouncement. inapSrfErrorOpRcv SS7_ISRF_ERRPC Info Error on alarm PromptAndCollect. inapSrfErrorOpRcv SS7_ISRF_UNKNOWNOP Info Unknown alarm operation received. inapSrfErrorOnARI SS7_ISRF_ERRARI Info Error on __________________________________________alarm____AssistRequestInstruction. Documentation Errors and Omissions 4-17 Documentation Errors and Omissions 4.3 Chapter on MIB Structure (trapParam) missing from the DECss7 Entity Reference Manual 4.3.3 Traps Mapped on PSI Table 4-3 lists the traps mapped on PSI. Table_4-3_Traps_mapped_on_PSI____________________________________ trap trap_Name_________Severity______trap_Cause_______________________ BepProcessDown Info alarm The BEP process is down. BepProcessUp Info alarm The BEP process is up. FepProcessDown Info alarm The FEP process is down. FepProcessUp Info alarm The FEP process is up. DirProcessDown Info alarm The DIR process is down. DirProcessUp Info alarm The DIR process is up. LastProcessIndicatInfo_alarm____Last_process_indication_received. 4.3.4 Traps Reported at Agent Initialization Time and Traps Reporting Platform Inconsistencies Table 4-4 lists the traps reported at Agent Initialization time and Table 4-5 gives the trap that reports platform inconsistencies. Table_4-4_Traps_Reported_at_Agent_Initialization_Time____________ trap trap_Name_________Severity______trap_Cause_______________________ AgentInitStarted Info alarm Agent initialization started AgentInitSuccessfuInfo alarm Agent initialization successful AgentStopped Info alarm Agent is stopped AgentInitFailedEveInfo alarm Agent initialization failed because of enable_events request ________________________________failure._________________________ 4-18 Documentation Errors and Omissions Documentation Errors and Omissions Structure (trapParam) missing from the DECss7 Entity Reference Manual Table_4-5_Traps_Reported_when_Inconsistencies_are_Detected_______ trap trap_Name_________Severity______Supplementary_Information________ Platform Info alarm If FEP inconsistencies are Inconsistency detected on a given platform, the DECss7 global_view interface will return an error message which will cause the agent to ________________________________emit_a_specific_trap.____________ 4.3.5 Solution The DECss7 Entity Reference Manual will be updated accordingly for the next release of the documentation. Documentation Errors and Omissions 4-19 Documentation Errors and Omissions 4.4 The NBBUFF characteristic of FEP_SUBSYSTEM missing 4.4 The NBBUFF characteristic of FEP_SUBSYSTEM missing 4.4.1 Description In the DECss7 Entity Reference Manual the NBBUFF characteristic of FEP_SUBSYSTEM entity is missing. Table_4-6_FEP_SUBSYSTEM_Characteristic_Attributes________________ Default Name_____________Symbol_______________Syntax_________Operation__Value Number of SS7_K_FEPS_NBBUFF Unsigned32 > Settable > = 4316 Buffers for 2 at the Free Creation Buffers Pool Only Number of buffers allocated for the free buffers pool. NBBUFF depends primarily on VIRTUALPAGECNT (system parameter) and PGFLQUOTA (UAF parameter), and secondly on the page file size. If NBBUFF is too big, the exception "insufficient virtual memory" is raised at image start up. VIRTUALPAGECNT is approximately equal to (19500 + NBBUF). PGFLQUOTA equals VIRTUALPAGECNT and page file size should be greater than_PGFLQUOTA.__________________________________________________________ _________________________________________________________________ 4.4.2 Solution The DECss7 Entity Reference Manual will be updated accordingly for the next release of the documentation. 4-20 Documentation Errors and Omissions