3.2.8 DuplicateLocalityFoundInForeignNF

Table 3-12 DuplicateLocalityFoundInForeignNF

Field	Details
Description	'Duplicate Locality found for Foreign NF'
Summary	'Duplicate locality for remote Region. namespace: {{$labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}},scpFqdn: ' {{$labels.scpFqdn}} ', timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} and value = {{ $value }} '
Severity	Major
Condition	This alert is raised when a foreign SCP is registered with a duplicate locality from the current region.
OID	1.3.6.1.4.1.323.5.3.35.1.2.3002
Metric Used	ocscp_notification_duplicate_foreign_location
Recommended Action	Cause: When a foreign SCP profile is accepted, but its MateScpInfo localities overlap with the local SCP’s serving or mate localities. Diagnostic Information: Check if ocscp_notification_duplicate_foreign_location = = 1. Group by NF type: sum by (nfType) (ocscp_notification_duplicate_foreign_location) Determine a specific instance: ocscp_notification_duplicate_foreign_location{nfInstanceId="<id>"} Look for WARN: "Common Serving or Mate localities found between local SCP and foreign SCP Look for pegging from pegInterScpMetrics in ForeignSCPRuleProcessorImp Verify the row for nfInstanceId has duplicateRemoteLocality=true (and the NF is foreign) Recovery: Ensure that the foreign SCP’s serving and MateScpInfo localities do not overlap with the local SCP’s serving or mate localities. Update the foreign SCP's profile and re-register it. After the profile is corrected and processed, the gauge automatically drops to 0 on the next REGISTERED event with no overlap (or clears on DEREGISTERED). For any assistance, contact My Oracle Support.