Previous Page: Monitoring and Resolving Communication Problems  Next Page: Unable to Communicate with Server, -625 Errors

Suspected Multiprocessing Problems

If you suspect a multiprocessing problem, complete the following steps. You will be able to eliminate most probable causes.

  1. Make sure the secondary processors are functioning properly.

    If the server is already up, stop all processors except Processor 0. In NetWare Remote Manager, click the Processor link in the navigation frame. Click the Stop Processor link for each processor online except processor 0. (Processor 0 cannot not be taken offline.)

    If the server is down, bring up the server and then stop all processors.

    If the problem still occurs, go to Step 2. If not, go to Step 4.

  2. To verify that this is not an interrupt issue, remove the PSM. Then reboot the server; only processor 0 will start.

    The MPS14.PSM, CPQMPK.PSM or *.PSM in the STARTUP.NCF file is the interrupt abstraction layer and communicates with the APIC (Advanced Programmable Interrupt Controller) rather than the PIC for interrupt handing in the machine.

    If the problem still occurs, it not a multiprocessing issue. If it no longer occurs, go to Step 3.

  3. Make sure you have the latest machine updates (current ROM BIOS, etc.).

    If you confirm that your hardware is current and the problem still occurs, it's possible that you are using a new version that wasn't available at the time NetWare 6 was released. Whatever is different about the hardware requires a newer PSM to work with the machine.

    HINT:  Problems that occur only in a multiprocessing environments are not necessarily MP problems. More likely, it is an issue with a piece that has been loaded in an MP environment and that does not function properly.

  4. Gather information as explained in Using a Troubleshooting Methodology. View the STARTUP.NCF and AUTOEXEC.NCF to determine what software pieces are running. Check with the software vendors and developers and tell them what steps you have taken and give them enough information to duplicate the problem.

If the problem still occurs, follow the troubleshooting steps in Using a Troubleshooting Methodology, search the Novell Knowledgebase, and contact a Novell Support Provider.



  Previous Page: Monitoring and Resolving Communication Problems  Next Page: Unable to Communicate with Server, -625 Errors