As a precaution before upgrading, we would recommend to make a backup copy of your SNMPv3 strings. This is a very simple process that could save a lot of time afterwards if there is an issue after the upgrade with the SNMPv3 strings.
DX NetOps Spectrum all currently supported releases
Unlikely, but possible corruption to happen during an upgrade
There are two methods that you can use to do this.
Link to Modeling Gateway method
The commands (in blue, output in green) are run from the VNM shell (vnmsh) command line, accessed by:
cd $SPECROOT/vnmsh
Then running ./connect
$ ./show models | grep -i GlobalConfig0x100012 GlobalConfig 0x10470 GlobalConfig
$ ./show attributes mh=0x100012 | grep -i SNMPv3Profiles 0x12bd4 oldSNMPv3Profiles0x13388 SNMPv3Profiles 5A.CE.C0.E4.A.BE.A8.8B.A2.56.A.42.C3.E1.47.6B.89.4E.97.96.3F.FF.57.94.5E.12.7F.37.FB.C0.64.E0.BD.C6.C4.5F.3F.55.3D.2E.D.D7.C.81.27.E4.E6.44.D.98.7D.BD.17.33.DB.99.B5.C5.94.FC.79.2F.31.F.D9.3C.5.98.80.7F.DC.B4.C.15.F3.7C.B9.B0.F5.D9.6.8C.DA.67.EE.F8.A3.AC.90.D.9D.48.FE.89.1F.45
./update mh=0x100012 attr=0x13388,val="0"
NOTE: For further details on the ./update command, reference the online guide - TechDocs : DX NetOps Spectrum 25.4 : update - Updates Model and Model Attributes
./update mh=0x100012 attr=0x13388,val="5A.CE.C0.E4.A.BE.A8.8B.A2.56.A.42.C3.E1.47.6B.89.4E.97.96.3F.FF.57.94.5E.12.7F.37.FB.C0.64.E0.BD.C6.C4.5F.3F.55.3D.2E.D.D7.C.81.27.E4.E6.44.D.98.7D.BD.17.33.DB.99.B5.C5.94.FC.79.2F.31.F.D9.3C.5.98.80.7F.DC.B4.C.15.F3.7C.B9.B0.F5.D9.6.8C.DA.67.EE.F8.A3.AC.90.D.9D.48.FE.89.1F.45"
$ ./show attributes mh=0x100012 | grep -i SNMPv3Profiles 0x12bd4 oldSNMPv3Profiles0x13388 SNMPv3Profiles 5A.CE.C0.E4.A.BE.A8.8B.A2.56.A.42.C3.E1.47.6B.89.4E.97.96.3F.FF.57.94.5E.12.7F.37.FB.C0.64.E0.BD.C6.C4.5F.3F.55.3D.2E.D.D7.C.81.27.E4.E6.44.D.98.7D.BD.17.33.DB.99.B5.C5.94.FC.79.2F.31.F.D9.3C.5.98.80.7F.DC.B4.C.15.F3.7C.B9.B0.F5.D9.6.8C.DA.67.EE.F8.A3.AC.90.D.9D.48.FE.89.1F.45