Hello: We had an incident of high XCFAS on two monoplexes recently when we upgraded one of our CECs. The Capacity Planning team noticed this increase and asked us to investigate. In the SYSLOG for the two monoplexes, we saw that the monoplexes "noticed" the CF paths at IPL, but they did not use the CF because they are monplexes.
After we CONFIGed the CF path offline to one monoplex, the XCFAS CPU on that monplex dropped to less than 1%. So, we ran an XES trace on the monoplex and CONFIGed the CF path back online, and we could see recurring path testing by XES. So we varied the CF offline to that monplex and its XCFAS CPU again dropped, and the path entries in the XES trace stopped completely. So, we took the CF paths offline to the second monoplex and his XCFAS CPU % dropped. The HCD gens were changed to omit the CF links to LPARs that do not require a CF (this had been our usual configuration but the links were included this time by accident). We did not open a PMR because we believed there was already documentation in "Setting Up a SYSPLEX" which discusses CONFIG OFFLINE CF links that are not in use. This issue might be significant even for a parallel sysplex, which might contain defined links to CFs that are meant as standbye CFs. It seems particularily odd for a monoplex, however. regards, Joe D'Alessandro ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
