Solved: NSO Upgrade from 3.4.8 to 4.4.3

pralala · ‎11-09-2017

Hi,
We have a situation where we are trying to upgrade to above versions. In 3.4.8, the java-vm is not enabled. We want to enable it in 4.4.3. We have enabled it in the init XML files.
When it tries to load those XML files, I think it is ignoring and not really enabling the JVM as those "leaf" are already present and NSO does not want to mess around with configs that were previously created.

Following snippet is from Developer Guide:

When using XML files for initialization of CDB, the complete contents of the files is used. On upgrade however, doing this could lead to modification of the user's existing configuration - e.g., we could end up resetting data that the user has modified since CDB was first initialized. For this reason two restrictions are applied when loading the XML files on upgrade:

• Only data for elements that are new as of the upgrade, i.e., elements that did not exist in the previous schema, will be considered.

• The data will only be loaded if all old, i.e., previously existing, optional/dynamic parent elements and instances exist in the current configuration.

Could anyone help in guiding what would be the perfect solution for this? (Even for writing upgrade package, we may have to enable JVM which is not really enabled while the upgrade is happening)

REGARDS,

Pratik Lala

Jan Lindblad · ‎11-10-2017

Right. So what the User Guide is trying to say is that the XML-init files in the database directory are only used when either there is no database files at all (i.e. the database is completely empty, gone), or if there is a software upgrade and some completely new YANG leaf:s have been introduced. If so, those leaf:s, and only those leaf:s, are initialized from the XML-init files.

Since the leaf:s in question here, java-vm control data, has always existed in NSO, the XML-init files will not be consulted here. Otherwise any configurations you had made would be overwritten (every time you start NSO). Not good.

But if, as in this case, you really do want to change the configuration to whatever is in the XML-init file, you can simply go to NSO CLI config mode and load it. Check that the results is what you wanted and commit.

View solution in original post

Jan Lindblad · ‎11-10-2017

Right. So what the User Guide is trying to say is that the XML-init files in the database directory are only used when either there is no database files at all (i.e. the database is completely empty, gone), or if there is a software upgrade and some completely new YANG leaf:s have been introduced. If so, those leaf:s, and only those leaf:s, are initialized from the XML-init files.

Since the leaf:s in question here, java-vm control data, has always existed in NSO, the XML-init files will not be consulted here. Otherwise any configurations you had made would be overwritten (every time you start NSO). Not good.

But if, as in this case, you really do want to change the configuration to whatever is in the XML-init file, you can simply go to NSO CLI config mode and load it. Check that the results is what you wanted and commit.

pralala · ‎11-14-2017

Thank you Jan for the response!