Eaton Network-M2 User Manual page 266

The alarm list has been cleared after an upgrade
8.9.2 Symptom
SNMPv3 connectivity is not properly working after a restore settings on a 1.7.0 version or above.
8.9.3 Cause
The SNMPv3 was configured prior to 1.7.0.
In that case, SNMPv3 configuration is not well managed by the Save and by the Restore settings.
8.9.4 Action
Reconfigure your SNMPv3 users and passwords on versions 1.7.0 or above and Save the settings.
The SNMPv3 configuration can then be Restored.
8.10 The alarm list has been cleared after an upgrade
8.10.1 Symptom
After a FW upgrade, the alarm list has been cleared and is now empty.
8.10.2 Action
The alarm list has been saved on a csv file and can be retrieved using Rest API calls.
8.10.2.1 Authenticate:
curl --location --request POST
--header 'Content-Type: application/json'
--data-raw '{ "username":"admin", "password":"supersecretpassword", "grant_type":"password",
"scope":"GUIAccess" }'
8.10.2.2 Get Alarm Log Backup:
curl --location --request GET
downloadBackup' \
--header 'Authorization: Bearer {{access_token}}'
8.11 The Network Module fails to boot after upgrading the
firmware
8.11.1 Possible Cause
The IP address has changed.
Note: If the application is corrupt, due to an interruption while flashing the firmware for example, the boot will be done on previous
firmware.
Troubleshooting – 266
'https://{{domain}}/rest/mbdetnrs/1.0/oauth2/token'
\
'https://{{domain}}/rest/mbdetnrs/1.0/alarmService/actions/
\