If you are upgrading from a previous release that sent SNMP notifications, you need to update the MIB in your SNMP receiver. The MIB definition in rtvapm\common\lib\SL-RTVIEW-EM-MIB.txt has changed to include a new field for this.
Some alerts are no longer used by the monitor. To remove the unused alerts from the Alert Administration display, remove all entries for SolMsgRouterMsgEgressUtilHigh, SolMsgRouterMsgIngressUtilHigh, SolMsgRouterByteEgressUtilHigh and SolMsgRouterByteIngressUtilHigh from the ALERTDEFS ALERTLEVELS database table. You can configure thresholds and overrides for the new alerts in the Alert Administration display.
If you enabled alert persistence, remove SolMsgRouterMsgEgressUtilHigh, SolMsgRouterMsgIngressUtilHigh, SolMsgRouterByteEgressUtilHigh and SolMsgRouterByteIngressUtilHigh from the ALERT_PERSIST_TABLE and ALERT_PERSIST_TABLE_CENTRAL to prevent errors about these alerts in the log file at startup.
Also note that if you have stored alert history, the old alert will be in the alert history. It is up to user discretion whether to keep the old alerts in history or not.
If you use SEMP, note that a request has been added to the supplied pollers_sl.xml and groups_sl.xml files. You may need to merge these updates with any changed versions of these files.
Note: HA connections from previous versions will automatically be split into two standalone connections. No user action is required. For details see the Release Notes.