rn024stn-M3UA

Please download to get full document.

View again

of 6
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Categories
Published
rn024stn-M3UA
  Dialogic ®  DSI Signaling Software Release Notes - M3UA for Solaris 1 Dialogic ®  DSI Signaling Software Release Notes M3UA for Solaris Document Reference: RN024STN Publication Date: November 2009 Contents M3UA for Solaris - V6.00 ............................................................................................... 2    M3UA for Solaris - V6.00 2 M3UA for Solaris - V6.00 1   Overview This is a major release of the m3ua module. This release provides more flexible and easier to use Layer Management control over system restart and the ongoing network activation state. This makes it easier to develop new applications, and supports more sophisticated resilience models. Some of these resilience models require the use of the new Development Package component RMM and updated S7_MGT module. This release of M3UA is accompanied by a major update of the M3UA Programmer's Manual (Issue 4) adding clarification to the message based configuration interface and extending the management interface supporting users wishing to directly configure and control M3UA. This release is also accompanied by a major update to the SIGTRAN Host Programmer's manual (Issue 7) for users configuring the system using config.txt configuration files. This deprecates the use the MBM module which had previously assisted in the activation of M3UA hosts. Functionality present in MBM has now been integrated into M3UA while maintaining backwards compatibility. Other changes in this release include new functionally and enhancements in the areas of alarms, statistics and timer configuration. This release also improves the robustness of the M3UA ASP and AS state machines. A number of race conditions in these state machines have been removed which could lead to start-up and conformance issues. This release is largely backwards compatible with the previous release although users no longer need to run the MBM utility. Refer to section 3.1 below for full details. 1.1   Applicability All users are advised to migrate to this new version of M3UA. Existing users who have deployed systems using the MBM utility should refer to section 3.1 below for details of how to remove the MBM utility as it is no longer required. 2   New Functionality 2.1   Data Throughput Rate Alarm The existing M3UA management indications used for monitoring the systems licensed data throughput have been extended. The system now supports a user configurable throughput threshold, expressed as a percentage of the licensed throughput and defaulting to 80%. When this throughput limit is exceeded a management indication is sent to the configured management module. When the throughput falls back below an abatement threshold (default 40%) an abatement indication is generated.  Dialogic ®  DSI Signaling Software Release Notes - M3UA for Solaris 3 The existing License event indication message ‘MGT_MSG_LIC_EVENT (0x0f23)’ has been extended to report these new throughput alarm event indications. The new event type and event indication codes used are shown below. Event Type Mnemonic Value LICEVENT_TYPE_THROUGHPUT_ALARM 4 Event Indication Mnemonic Value LICEVENT_THROUGHPUT_ALARM_INACTIVE 0 LICEVENT_THROUGHPUT_ALARM_ACTIVE 1 The existing throughput statistics message ‘MGT_MSG_R_THR_STATS (0x6f21)’ has been extended to report the number of times the throughput alarm has fired and the duration for which the throughout has exceeded the alarm threshold. These are returned in the alarm_count and alarm_duration parameters. The existing License Status message ‘MGT_MSG_R_LIC_STATUS (0x6f22)‘ has been extended to indicate whether the throughput alarm is currently active. If the ‘Throughput Alarm State’ is set to one then the throughput alarm is currently active. It will be set to zero if not active. The throughput alarm onset and abatement thresholds can be set to user defined values using the new message ‘MGT_MSG_SET_THR_ALARM (0x5f27)’. This message can also be used to disable the alarm by setting the onset and abate thresholds to zero. The Onset threshold defines the level at which the throughput alarm should fire expressed as a percentage of the licensed throughput. The Abate threshold defines the level at which the throughput alarm should abate expressed as a percentage of the licensed throughput. This must be less than the onset threshold. The full message definition for all messages is contained within the M3UA programmer’s Manual. 2.2   M3UA Automatic Activation Previously the activation and reactivation of ASPs and ASs was a manual process performed by layer management (or MBM on a S7_MGT / config.txt system). This required construction of an activation state machine to ensure proper initialization and recovery from all possible failure scenarios. This release sees the addition of automatic AS and ASP activation to M3UA itself without the need for the use of MBM or for the user to implement an activation state machine. This functionality is enabled by setting the new 'Auto Activate' options in the M3U_MSG_ASP_UP_REQ and M3U_MSG_ASP_ACT_REQ messages. When these options are enabled M3UA will try and maintain the ASP and AS in an UP or ACTIVE state respectively. The reception of an M3U_MSG_ASP_DOWN_REQ or M3U_MSG_ASP_INACT_REQ will result in the ‘Auto Activate’ option being cleared. The M3U_MSG_ASP_UP_REQ, M3U_MSG_ASP_ACT_REQ, M3U_MSG_ASP_DOWN_REQ and M3U_MSG_ASP_INACT_REQ messages are defined in the M3UA Programmer’s Manual.  M3UA for Solaris - V6.00 4 M3UA also supports a new message M3U_MSG_ACTIVATE which can be used to activate the association, bring the ASP up and activate the AS across the association with just a single message. This message also causes the ‘Auto Activate’ options to be set for the ASP and AS. The corresponding M3U_MSG_DEACTIVATE clears the ‘Auto Activate’ flags and deactivates the association forcing the ASP and AS to be down and inactive. These messages are defined in the M3UA Programmer’s Manual. Note:  The M3U_MSG_ACTIVATE and M3U_MSG_DEACTIVATE messages were previously supported by the deprecated MBM module and called MBM_MSG_ACTIVATE and MBM_MSG_DEACTIVATE respectively. S7_MGT automatically generates M3U_MSG_ACTIVATE for all associations after successfully configuring the system. 2.3   M3UA Peer Acknowledgement Time Out A new timer T(ack) has been introduced to the ASP and AS state machines which is started when a response is expected from the peer. Should the timer expire without a response being received then M3UA will give a negative confirmation to Layer Management or, if the ‘Auto Activate’ option is set will retransmit the request to the peer. The negative confirmation uses the same message type as is used for a positive confirmation but with the status field set to a non-zero value. The default value for T(ack) is two seconds. This can be changed using the new timer configuration message M3U_MSG_CNF_TIMERS described later. 2.4   M3UA Peer Activation Request Blocking Previously M3UA would never refuse a peer request to ACTIVATE or bring UP an AS or ASP. If the peer sent an M3UA UP or ACTIVATE request then it would automatically be accepted. In this release M3UA supports an option to reject peer requests. This is enabled by sending an M3U_MSG_ASP_DOWN_REQ or M3U_MSG_ASP_INACT_REQ with the ‘Auto Deactivate’ option set. This option is cleared by sending a subsequent message without this option set or by sending any UP or Activate request. 2.5   M3UA Timer Configuration Message M3UA supports a number of timers which take default values as suggested by the M3UA RFCs or otherwise. A new timer configuration message M3U_MSG_CNF_TIMERS (0x72fc) defined in the M3UA programmer’s Manual is available to change these timer values if required. 2.6   M3UA AS Pending State Buffering When a redundant remote application operating in an Active Standby mode experiences a fault causing the Active system to fail M3UA will enter a Pending state. While in this state M3UA will buffer messages for the application while waiting for the standby unit to Activate. If the T(recovery) timer expires before the standby unit has activated then the buffered messages will be discarded and the AS will move from Pending to Inactive.
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks