Purpose
Steps to take to determine cause and next steps when receiving FSC7C54 (Proc copy switch) alert.
Troubleshooting Steps
Please pull logs (refer to doc id 1311008.1) and send them into VSM support for review and cause determination.
1. Pull VTSS basefile logs (see doc id 1232935.1) and "crunch" them by uploading to SPLAT (tapesupport.us.oracle.com)
2. Review hic_stat.dia and determine if proc copy switch was manual due to CSE maintenance or hardware issue.
A. Search for "CSE Entering Maintenance Menus" prior to MIM with FSC7C54, and see if FSE performed maintenance. For example, non-disruptive code upgrade requires proc copy switch to apply code on ISPs to non-master. Or if ISP is IML'ed for a GSR (Guided Service Repair) a proc copy switch may be required.
In these cases, no further action is required.
B. If not FSE induced, review logs for other causes and take appropriate action.
1) Review SPLAT output tabs (Summary, Critical FSCs, Support Actions, etc...).
2) Can also open hic_stat.dia and look for the FSC7C54. Work back to previous FSC(s) logged that occurred within minutes of 7C54. Look up FSC(s) and see if it can cause a proc copy switch (use FSC lookup table on tapesupport.us.oracle.com to get FSC description). Also search Knowledgebase for troubleshooting any FSCs found.
3) If cause still not known, look in pfaelg4a file(s). Again look for FSC7C54 and work backward to find previous FSC logged in previous few minutes of the 7C54. Look up FSC(s) and see if it can cause a proc copy switch (use FSC lookup table on tapesupport.us.oracle.com to get FSC description). Also search Knowledgebase for troubleshooting any FSCs found.
4) Finally, may have to pull statesave files for further investigation (see doc id 1367391.1).
Attachments
This solution has no attachment