What's New in This Guide

This section introduces the documentation updates for release 23.4.x.

Release 23.4.6-F89025-14, March 2025

  • Added step 9 in the Preupgrade Tasks section to validate that there are no Database backup is running during NRF upgrade.
  • Added a note in the Upgrade Tasks section to check if there are no database backup is in progress during the NRF upgrade.
  • Added a note about NRF to accept the 3GPP compliant value for nfSetId attribute for the global.deprecatedList parameter in the following sections:

Release 23.4.6- F89025-13, January 2025

Release 23.4.5- F89025-12, October 2024

  • Updated the release number to 23.4.6 in the entire document.
  • Updated the image tag details in the Pushing the Images to Customer Docker Registry section.
  • Updated the upgrade paths in the Supported Upgrade Paths section.
  • Updated the rollback paths in the Supported Rollback Paths section.
  • Updated the following parameters in the cnDBTier Requirement section:
    • The recommended value of global.ndb.datamemory parameter is changed from 1GB to 2 GB.
    • The recommended value of global.additionalndbconfigurations.ndb.MaxNoOfExecutionThreads parameter is changed from 5 to 6.
  • Added the following parameters in the cnDBTier Requirement section:
    • global.additionalndbconfigurations.mysqld.ndb_batch_size
    • global.additionalndbconfigurations.mysqld.ndb_blob_write_batch_bytes
  • Updated the resource requirements for cnDBTier services in the cnDBTier Services section.
  • Added a note in the Upgrading NRF section to modify the value of global.additionalndbconfigurations.ndb.HeartbeatIntervalDbDb parameter to 1250 while performing cnDBTier upgrade.
  • Added a note in the Upgrade Strategy section to perform in-service upgrade in maintenance window.
  • Added the NRF site which is under recovery is receiving the traffic, perform the controlled shutdown procedure to isolate the site in the Prerequisites section.
  • Added Post Fault Recovery section with the procedure to recover NRF traffic after fault recovery.
  • Updated the Graceful Shutdown of NRF Deployment section with the NRF behavior after fault recovery using controlled shutdown feature.
  • Added a note in the Rolling Back NRF section to use the mysql_native_password authentication plugin for altering the users.

Release 23.4.4- F89025-11, August 2024

  • Updated the release number to 23.4.4 in the entire document.
  • Updated the image tag details in the Pushing the Images to Customer Docker Registry section.
  • Updated the upgrade paths in the Supported Upgrade Paths section.
  • Updated the rollback paths in the Supported Rollback Paths section.
  • Added a note in the Upgrading NRF section to provide reference to the cnDBTier Resource Requirement for allocating the cnDBTier resources before upgrading NRF.
  • Added a note in the Upgrading NRF section to mention that, in the georeplicated NRF deployments, the difference between the NRF release versions for all the georedundant sites cannot be more than 1.

Release 23.4.3- F89025-10, July 2024

Release 23.4.2- F89025-09, July 2024

  • Updated the name of the following messageCopy parameters in the document from message-copy to messageCopy in the Ingress Gateway Microservice section.
    • ingressgateway.messageCopy.enabled
    • ingressgateway.messageCopy.copyPayload
    • ingressgateway.messageCopy.topicName
    • ingressgateway.messageCopy.ackRequired
    • ingressgateway.messageCopy.retryOnFailure
    • ingressgateway.messageCopy.security.enabled
    • ingressgateway.messageCopy.security.protocol
    • ingressgateway.messageCopy.security.tlsVersion
    • ingressgateway.messageCopy.security.saslConfiguration.username
    • ingressgateway.messageCopy.security.saslConfiguration.password
    • ingressgateway.messageCopy.security.saslConfiguration.k8SecretName
    • ingressgateway.messageCopy.security.saslConfiguration.k8NameSpace
    • ingressgateway.messageCopy.security.saslConfiguration.fileName
  • Updated the name of the following messageCopy parameters in the document from message-copy to messageCopy in the Egress Gateway Microservice section.
    • egressgateway.messageCopy.enabled
    • egressgateway.messageCopy.copyPayload
    • egressgateway.messageCopy.topicName
    • egressgateway.messageCopy.ackRequired
    • egressgateway.messageCopy.retryOnFailure
    • egressgateway.messageCopy.security.enabled
    • egressgateway.messageCopy.security.protocol
    • egressgateway.messageCopy.security.tlsVersion
    • egressgateway.messageCopy.security.saslConfiguration.username
    • egressgateway.messageCopy.security.saslConfiguration.password
    • egressgateway.messageCopy.security.saslConfiguration.k8SecretName
    • egressgateway.messageCopy.security.saslConfiguration.k8NameSpace
    • egressgateway.messageCopy.security.saslConfiguration.fileName.ccaHeaderValidation
  • Added the extraContainers parameter in the document to control the usage of extra container when DEBUG tool is ENABLED in the following sections:

Release 23.4.2- F89025-06, April 2024

Release 23.4.1- F89025-05, March 2024

Release 23.4.0- F89025-04, March 2024

Release 23.4.0- F89025-03, February 2024

Release 23.4.0- F89025-02, January 2024

Release 23.4.0- F89025-01, December 2023