NANC 219

NPAC Monitoring of SOA/LSMS Associations

Origination Date :06/05/1998

Originator:AT&T

Description:

It has been requested that NPAC Monitoring of SOA and LSMS associations be put into the NPAC SMS at the application (CMIP) layer.  The approach suggested by the requestor would be to alarm whenever aborts are received or sent by the NPAC.  When these alarms occur, the NPAC Personnel would contact the affected Service Provider to work the problem and ensure the association is brought back up.

From this point forward, this change order will deal with the alarm abort option.  The heartbeat abort option is NANC 299.

Final Resolution:

Pure Backwards Compatible:  YES

Sep LNPAWG (Seattle), discussed various options for working the problem of dropped associations (i.e., causes partial failures for the new SP trying to activate).

Options include,

1.)  sending a notification to all SPs that "an SP is currently not associated", then another notifications once it is back up, "all SPs associated".

2.)  stopping an activation request, because an association is down.

3.)  sending a notification to the New SP when an activate is received, that an association is down, "do you still want to activate?".

NEXT STEP:  all SPs should consider issues and potential options for activates during a missing association that will cause a partial failure.

Oct LNPAWG (Kansas City), the conversation migrated away from the three options discussed in Seattle, and back to the NPAC proactively monitoring the association.  This would require the NPAC to provide an attendant notification that a Service Provider is down, then notifying them of their missing association.

NPAC LOE: Low (alarm abort), Med (heartbeat abort),

High (ops costs for all options)

SOA/LSMS LOE: N/A/N/A

June 06 LNPAWG moved to Cancel-Pending

Related Release:

N/A

Status: Closed