When running an SMF upgrade of AMF the following happens:
SC-2-1 osafsmfd[4296]: NO STEP: Online installation of new software
(this step is succesful)
SC-2-1 osafsmfd[4296]: NO STEP: Lock deactivation units
SC-2-1 osafamfd[4120]: NO Node is locked, no SI unassigned alarm will be sent
SC-2-1 osafsmfd[4296]: NO STEP: Terminate deactivation units
SC-2-1 osafamfd[4120]: WA avd_msg_sanity_chk: invalid msg id 219, msg type 8, from 2020f should be 218
... (this repeats a number of times)
osafsmfd[4296]: NO Fail to invoke admin operation, rc=SA_AIS_ERR_TIMEOUT (5). dn=[safAmfNode=SC-2,safAmfCluster=myAmfCluster], opId=[3]
osafsmfd[4296]: NO Failed to call admin operation 3 on safAmfNode=SC-2,safAmfCluster=myAmfCluster
Is AMF handling a upgrade properly? Seems that the msg id is missmatched here.
Sounds like we have a problem of snd_msg_id being updated & messages sent (potentially out of order) from multiple threads.
Last edit: Gary Lee 2016-05-03
Rafael says the problem goes away if #517 changes are reverted
What is the upgrade path being followed?
Also please share the traces from AMFD and AMFND and details about no.
of nodes.
Thanks,
Praveen
On 03-May-16 11:00 AM, Gary Lee wrote:
Related
Tickets:
#1802Hi,
What is the upgrade path being followed along with specific changeset and tag?
Also please share the syslog, traces from AMFD and AMFND and details about no.
of nodes. Also steps to reproduce.
Thanks,
Praveen
Maybe someone else can help you with the trace and logs. I am not able to reproduce it on my system. It seems this also shows in a failover case of the active SC without doing any SMF upgrade.
Please find the attached patch 1802.patch and test and share the results.
Thanks
-Nagu
Updated the patch, please find it(1802_mod.patch) attached.
Please perform your testing with 1802_mod.patch and share the results.
@Rafael: Can you please get 1802_mod.patch tested, so that we can push it before 5.0 GA?
Thanks
-Nagu
This ticket needs to be updated with additional information of how to reproduce, traces etc.
Please update with the relevant information.
The latest patch floated avoids this issue.