7708 M3UAASPAssocEndPtConflict

Recommended Action

Verify the detected local SCTP endpoint conflicts are resolved.

First determine all the SG objects (M3UA ASP Associations, M3UA SCTP Servers and SUA SCTP Servers) conflicting with the M3UA ASP Association that raised this alarm. To identify the SG objects, use the following procedure:

1. Note the Instance Id value of this alarm.
2. Click Event Context link to open the ASP Association object that raised this alarm.
3. Note the Slot, Local IP Address 1, Local IP Address 2 and Local Port values.
4. For all hostnames used to configure the local SCTP endpoint, either click IP Networking > Hostname Resolution or access the appropriate DNS Server to determine the list of IP addresses mapping those hostnames.
5. To determine all the M3UA ASP Associations conflicting with the M3UA ASP Association that raised this alarm, click Alarms > Minor > 7708 and perform the following for all alarm instances whose Instance Id is different from the one observed in step 1 and slot value matches the one observed in step 3:
   1. Click Event Context to open the ASP Association that raised the alarm.
   2. If the Local Port value matches the one observed in step 3, note the Local IP Address 1 and Local IP Address 2 values.
   3. If hostnames are used to configure the local SCTP endpoint of this ASP Association, either click IP Networking > Hostname Resolution or access the appropriate DNS Server to determine the list of IP addresses mapping those hostnames.
6. To determine all the M3UA SCTP Servers conflicting with the M3UA ASP Association that raised this alarm, click Signaling Gateway > M3UA > M3UA SCTP Servers and perform the following for all M3UA SCTP Severs instances whose Slot value matches the one observed in step 3:
   
   1. If Port value matches the one observed in step 3, note the IP Address 1 and IP Address 2 values.
   2. If hostnames are used to configure this M3UA SCTP Server, either click IP Networking > Hostname Resolution or access the appropriate DNS Server to determine the list of IP addresses mapping those hostnames.
7. To determine all the SUA SCTP Servers conflicting with the M3UA ASP Association that raised this alarm, click Signaling Gateway > SUA > SUA SCTP Servers and perform the following for all SUA SCTP Severs instances whose Slot value matches the one observed in step 3:
   
   1. If Port value matches the one observed in step 3, note the IP Address 1 and IP Address 2 values.
   2. If hostnames are used to configure this SUA SCTP Server, either click IP Networking > Hostname Resolution or access the appropriate DNS Server to determine the list of IP addresses mapping those hostnames.

8. Compare the list of IP addresses from step 4 against the list of IP addresses from steps 5, 6 and 7 to determine all the SG objects (M3UA ASP Associations, M3UA SCTP Servers and SUA SCTP Servers) conflicting with the M3UA ASP Association that raised this alarm. 
   For a summary of all of the run-time conflict scenarios involving an M3UA ASP Association, see Table Run-time Object Conflicts on Signaling Gateway Object Conflicts.

Once all the conflicting SG objects (including the M3UA ASP Association object that raised this alarm) are identified, perform one or more of the following actions to resolve the conflict:

• For SUA/M3UA SCTP Servers, perform one of the following actions until the conflict is completely resolved:
  1. Modify the Port value to a unique value.
     
  2. Modify the IP Address 1 and IP Address 2 values to non-conflicting values.
     

  3. Modify the hostname configurations so they resolve to non-conflicting IP addresses.

     Tip

     Modifying the hostname configurations may take up to one minute to take effect.

  4. Delete the SUA/M3UA SCTP Server.
      
• For M3UA ASP Associations, perform one of the following actions until the conflict is completely resolved:

  1. Modify the hostname configurations so that they resolve to non-conflicting IP addresses.

     Tip

     Modifying the hostname configurations may take up to one minute to take effect.

  2. Delete the M3UA ASP Association.