A.1 Health Check Procedures
Note:
If syscheck fails on any server during pre-upgrade Checks or in early checks stating that "cpu: FAILURE:: No record in alarm table for FAILURE", see Workaround to Resolve Syscheck Error for CPU Failure.If the 31201 - Process Not Running alarm displays, for instance, as cmsoapa, then run Workaround to Fix cmsoapa Restart.
- In the Primary SDS NOAM VIP, verify status. Expand Status & Manage click Server.
Figure A-5 Server
- Verify Server Status is Normal (Norm) for Alarm (Alm), Database (DB), Reporting Status, and Processes (Proc).
Figure A-6 Server Status
If any other server status displays, it appears in a colored box.
Note:
Other server states include Err, Warn, Man, and Unk.Note:
Post-Upgrade, upgraded servers have an Alm status of Err due to the Event ID (s): 32532 Server Upgrade Pending Accept/Reject expected alarm. This alarm displays until the upgrade is accepted and may be ignored at this time.Note:
During any time of upgrade in case 31149- DB Late Write Nonactive alarm is seen, please ignore it. This alarm does not have any effect on any functionality.If 31201 - Process Not Running alarm is getting raised for Instance as cmsoapa then run Workaround to Fix cmsoapa Restart to solve this issue.
- In the Primary SDS NOAM VIP, verify connection counts. Expand Communication Agent select Maintenance click Connection.
Figure A-7 Connection
- Verify all Connection Counts show equivalent counts (that is, n of n InService for Automatic or y of y InService for Configured)
Figure A-8 Maintenance
Note:
DPs show a Configured Connections Count of 1 of 2 InService for Active/Standby configurations. This is normal and can be ignored. - In the Primary SDS NOAM VIP, view alarm status. Expand Alarms & Events click View Active.
Figure A-9 View Active
- In the Primary SDS NOAM VIP, create Alarms and Events report. Click Export.
Figure A-10 Export
- Click OK.
Figure A-11 OK
- The name of the exported alarms CSV file displays in the Tasks tab.
Figure A-12 Tasks
- In the Primary SDS NOAM VIP, save the Alarms and Events report. Click Report
Figure A-13 Report
Figure A-14 View Active Alarms
- Click Save on the Alarms and Events report and click Save on the File Download screen.
Figure A-15 Save
Figure A-16 Save
- Select a directory on a local disk drive to store the active Alarms and Events report and click Save.
Figure A-17 Save As
- In the Primary SDS NOAM VIP, create Network Element report. Before 8.x, expand Configuration click Network Elements.
Figure A-18 Network Elements
- Expand Configuration, select
Networking and click
Networks.
Figure A-19 Networks
- Click Report.
Figure A-20 Report
- The Network Element Report is generated.
Figure A-21 Network Element Report
- In the Primary SDS NOAM VIP, save the Network Element report. Click Save on the Network Element report and click Save on the File Download screen.
Figure A-22 Save
Figure A-23 Save File
- Select a directory on a local disk drive to store the Network Element report and click Save.
Figure A-24 Save As
- In the Primary SDS NOAM VIP, create the Servers report. Expand Configuration click Servers.
Figure A-25 Servers
- Click Report.
Figure A-26 Report
Figure A-27 Server Report
- In the Primary SDS NOAM VIP, save the Servers report. Click Save on the Servers report and click Save on the File Download screen.
Figure A-28 Save
Figure A-29 Save File
- Select a directory on a local disk drive to store the Servers report and click Save.
Figure A-30 Save Server Report
- In the Primary SDS NOAM VIP, create Server Groups the report. Expand Configuration click Server Groups.
Figure A-31 Server Groups
- Click Report.
Figure A-32 Report
Figure A-33 Sever Groups Report
- In the Primary SDS NOAM VIP, save the Servers report. Click Save on the Server Groups report and click Save on the File Download screen.
Figure A-34 Save
Figure A-35 Save File
- Select a directory on a local disk drive to store the Server Groups report and click Save.
Figure A-36 Save Server Report
- Verify OAM HA Role status, expand Status & Manage click HA
Figure A-37 HA
- Verify the OAM HA Role for all servers shows either Active or Standby.
Figure A-38 OAM HA Role
Note:
An OAM HA Role shown as Observer is allowed when the server role is Query Server.