Configuring an M3UA Configured ASP

The M3UA Application Servers Processes (ASPs) may be configured as

• Single Association ASPs
• Multi Association ASPs 

Configuring an M3UA Single Association ASP

You can preconfigure ASPs by entering the IP address and port number of the ASP. Each ASP is given an ID number. You can also associate a Routing Context (an attribute belonging to a specific AS) with a configured ASP, which then links the ASP to that AS, as described in the RFC4666, Sections 4.3.4.3.

Configured Routing Contexts can be grouped by defining a Remote Routing Context. An ASP may be activated for the group of configured routing contexts by sending a single ASP Active message that contains only the remote routing context. All notifications and acknowledgment messages pertaining to any Application Server in the group will contain the remote routing context.

After you configured an ASP, the Routing Context may also be configured (for more information, see To create an M3UA Routing Context).

If you set the ASP Management attribute on the M3UA Server Configuration screen (refer to Configuring an M3UA SCTP Server) to CONFIGURED ONLY, then only preconfigured ASPs can connect to the system. 

To create an M3UA Configured ASP

To configure an M3UA Configured ASP

To create an M3UA Routing Context

To configure an M3UA Routing Context

Aborting an M3UA SCTP Association 

To abort an M3UA SCTP Association, this association has to be terminated. Taking down (terminating) an SCTP Association can be used to change the state of an Application Server from Active to Down state. This functionality is useful when maintenance is required to modify an Application Server Routing Key. To allow these changes, the following must be performed through the SG application in the Web UI:

1. Terminate the SCTP Association between the DSC Platform M3UA and the given ASP (see To terminate an M3UA SCTP Association).  

   Tip

   As an alternative to manual association termination, the relevant Application Server Process (ASP) that is responsible for activating the AS can send an ASP Down message or terminate the given SCTP Association in order to change the AS state.

   This action does not a block re-connection attempts. In order to block re-connection attempts, the SCTP Server to which the ASP connects should be set to DISABLED (refer to To activate or deactivate all M3UA SCTP Servers). Disabling the SCTP Server does not affect existing ASP SCTP Associations.

     

2. Deactivate the ASP (see To activate or deactivate an M3UA Configured ASP).
   You can deactivate the ASP using the DEACTIVATE action in the M3UA Configured ASP Configuration screens.

   This action terminates the SCTP Association and blocks a re-connection attempt.

     

3. You can now delete the M3UA AS as required.
      

To terminate an M3UA SCTP Association

To activate or deactivate an M3UA Configured ASP

Configuring an M3UA Multi Association ASP

The license-dependant Multi Association Application Server Process (ASP) requires you to configure point-to-point SCTP Associations. These associations are grouped to represent one ASP which can be a client or a server connection where one end point is defined as a client while the other is defined as a server.

All SCTP Associations of a Multi Association ASP have the same role where an ASP can be configured to use M3UA RFC4666, Sections 4.3.4.3 or the proprietary V2 implementation.

To create an M3UA Multi Association ASP

To configure an M3UA Multi Association ASP

To configure an M3UA Multi Association ASP SCTP Configuration

To create an M3UA Multi Association ASP Association

To view an M3UA Multi Association ASP Association

To create an M3UA Multi Association RC

To configure an M3UA Multi Association RC

Viewing All M3UA Multi Association ASPs

Follow the instructions in this section to view a summary of all M3UA Multi Association ASPs.

To view all M3UA Multi Association ASPs

1. From the Main Menu, click SG.
   
   
2. Click M3UA.
   
   
3. Click M3UA Multi ASPs.

Enabling IMF with M3UA Single or Multi Association ASP

The SG provides the ability to copy M3UA ASP messages to the Integrated Monitoring Feed (IMF) for traffic analysis on a Global and ASP level. For more information about the IMF, refer to Configuring the Integrated Monitoring Feed.

In order for a dynamic M3UA ASP to send all inbound/outbound DATA, ASPTM and NOTIFY messages to the IMF interface, the Global IMF Support for the M3UA must be ENABLED. Then any individual ASP level IMF Support may be ENABLED. 

If the Global and ASP level IMF Support attributes are disabled, then no action is taken.

To disable the IMF Support attribute for all M3UA (single and multi-association) ASPs, use the Reset IMF action.