Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NfDown Notification Handling #93

Merged
merged 6 commits into from
Jan 24, 2023

Conversation

vthiruveedula
Copy link
Contributor

  1. refer to the latest util/drsm 1.0.9.
  2. NfDownNotification handling

@vthiruveedula vthiruveedula force-pushed the dev-nfinstance branch 3 times, most recently from e984bb4 to 6178ead Compare January 9, 2023 18:00
oam/routers.go Outdated
@@ -100,4 +102,10 @@ var routes = Routes{
"/active-ues",
HTTPGetActiveUes,
},
{
"Amf Instance Down Notificatication",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo : *Notification

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@@ -41,7 +43,9 @@ func InitAmfContext(context *context.AMFContext) {
config := factory.AmfConfig
logger.UtilLog.Infof("amfconfig Info: Version[%s] Description[%s]", config.Info.Version, config.Info.Description)
configuration := config.Configuration
context.NfId = uuid.New().String()
if context.NfId == "" {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the case when NfId wont be null ??

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Network Instance Id will be empty when the amf comes up first, so first-time NfId should be generated, later we should use the same NfId.

logger.ConsumerLog.Errorf("Remove NF Subscription Failed Problem[%+v]", problemDetails)
} else if err != nil {
logger.ConsumerLog.Errorf("Remove NF Subscription Error[%+v]", err)
if notificationData.Event == models.NotificationEventType_DEREGISTERED {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need this check. will the amf instance down reach here with some other event type ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are two events currently, PROFILE_Changed or DEREGISTRED, so entry from the cache must be deleted only in case of DEREGISTERED

@vthiruveedula
Copy link
Contributor Author

retest please

1. Handling NF Down Notification from NRF
2. refer new util version 1.0.9(nfinstanceid added in keepalive and
   chunk table)
3. removing subscription from NRF when the target NF instance is down
Copy link
Contributor

@badhrinathpa badhrinathpa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@badhrinathpa badhrinathpa merged commit a4759db into omec-project:master Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants