The maintenance system allows the system administrator to:
Obtain inventory and status information upon request for hardware and software on the system
Initiate maintenance operations such as shutdown, startup and the invokation of diagnostics
See unsolicited status changes for components that generate events via either the fault or maintenance systems
Maintenance draws heavily from v2.0 of the emerging industry standard DMI (Desktop Management Interface). This allows us to adopt the functionality provided by a third party DMI Service Provider as well as the functionality provided by third party DMI compliant components.
The administrator's interface to the maintenance system is through the maintenance GUI (Graphical User Interface) accessed through the SMP (System Management Product) window. The maintenance GUI presents a tree view of the system based on the physical arrangement of it. Each object in the tree can be selected to present a property sheet displaying relevant object information such as important object attributes, states and diagnostics procedures which can be run on the object.
Alarms and events logged to the fault manager are forwarded to the maintenance system which can then forward them to registered management applications such as the GUI.
Severity Major
Description An unexpected software exception occurred in the network interface diagnostic.
Impact The network diagnostic is non-functional.
Recovery Action This is a software bug. Contact your Nortel service organization.
Technical Support Action This is a software bug. Contact the Nortel product support team.
Severity Debug
Description DmiListGroups call failed
Impact Affects the overall functionality of Maintenance Server
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiRemoteRegister call failed
Impact Maintenance Server cannot register with Dmi SP as a management application
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiUnregister call failed
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiListComponents call failed
Impact Affects the overall functionality of Maintenance Server
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiGetMultiple call failed
Impact Affects the overall functionality of Maintenance Server
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiAddRow call failed
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiListClassNames call failed
Impact Affects the overall functionality of Maintenance Server
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiGetAttribute call failed
Impact Affects the overall functionality of Maintenance Server
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Debug
Description DmiListAttributes call failed
Impact Affects the overall functionality of Maintenance Server
Recovery Action Not Applicable
Technical Support Action Check if DMI SP is running and that it's database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup. Look up the return code to find the DMI specific error.
Severity Major
Description The Maintenance Server waits for the instrumentation code to came up. After 30 minutes the server decides that the objects which have a mapping in DMI components are not instrumented and won't try any more to find the instances for that object.
Impact Some managed objects will have no instances and therefore they cannot be seen by the client GUI.
Recovery Action Use Control Panel/Services applet to stop and restart instrumentation service (meaning, if both the System Information Server (SIS) and the EMCI Server (EMCI) are up then start and restart SIS; if both are down then start EMCI and then start SIS; if EMCI is up and SIS is down then restart SIS; and if EMCI is down and SIS is up then stop SIS, start EMCI and restart SIS.) Both services should be automatic.
Technical Support Action Check if the instrumentation code is available and if the required MIF files are properly installed. See DMI documentation for details.
Severity Major
Description The DMI Service Provider is not running.
Impact Unable to obtain maintenance information or to perform maintenance operations.
Recovery Action Use the control panel/services applet to stop and restart Win32SL and/or the Maintenance Server.
Technical Support Action Look up the return code to find the cause of the problem. It may be necessary to uninstall and reinstall the DMI Service Provider. Before doing so backup the MIF database (sldb.dmi), uninstall the DMI SP, reinstall the DMI SP and restore the database file. (This may require you to stop the Win32SL service.).
Severity Major
Description Maintenance server is unable to start due to some internal initialization errors.
Impact Unable to obtain maintenance information or to perform maintenance operations.
Recovery Action Use the control panel/services applet to stop and restart Win32SL and/or the Maintenance Server.
Technical Support Action Look up the return code to find the cause of the problem. Another cause can be the failure to create some synchronization objects, or a RPC runtime error. It may be necessary to reboot the machine to fix the problem.
Severity Major
Description The maintenance server component mapping table cannot be initialized
Impact Unable to obtain maintenance information or to perform maintenance operations
Recovery Action Use the control panel/services applet to stop and restart Win32SL and/or Maintenance Server.
Technical Support Action Look up the return codes to find the root cause. See if correct MIF files are installed using support tools. Check if the DMI SP database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi file from a backup.
Severity Major
Description The Maintenance Server cannot initialize managed objects to DMI mapping
Impact Unable to obtain maintenance information or to perform maintenance operations
Recovery Action Use the control panel/services applet to stop and restart Win32SL.
Technical Support Action Look up the rc and extra error code to find the cause of the problem. Make sure that the DMI group "NORTEL|NGen Mapping|001" is installed. See if correct MIF files are installed using support tools. See if there is enough free disk space for memory swap files - a memory leak may have occurred. It may be necessary to reboot the machine to fix the problem.
Severity Major
Description Maintenance server cannot convert DMI rows to managed object instances
Impact The functionality of the maintenance server is limited. Cannot provide any information at the managed object instance level
Recovery Action Use the control panel/services applet to stop and restart Win32SL.
Technical Support Action Look up the rc and extra error code to find out the cause of the problem. Make sure that the DMI group "NORTEL|NGen Mapping|001" is installed. See if correct MIF files are installed using support tools. See if there is enough free disk space for memory swap files - a memory leak may have occurred. It may be necessary to reboot the machine to fix the problem.
Severity Minor
Description An error occurs trying to register maintenance server to receive indications from DMI Service Provider. A workaround would be to manually refresh the client Maintenance GUI.
Impact The server will not receive indications from DMI SP.
Recovery Action Use the control panel/services applet to stop and restart the DMI SP and/or the Maintenance Server.
Technical Support Action See if correct MIF files are installed using support tools. Check if the DMI SP database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup.
Severity Debug
Description An error has occurred when Maintenance Server service was stopped.
Impact Not Applicable
Recovery Action Call your NORTEL support organization.
Technical Support Action Look up the return code to find the cause of the problem. Kill the nbmnts.exe process using the task manager. If the problem persists a system reboot may be required to clear the problem.
Severity Minor
Description Maintenance server couldn't forward an event to the client Maintenance GUI (eg. alarms, courtesy down complete, diagnostic complete)
Impact Registered clients don't receive the event and the event is lost.
Recovery Action Check to see if the client was up during time of event - refresh the client Maintenance GUI manually. Use the control panel/services applet to stop and restart the DMI SP and/or the Maintenance Server.
Technical Support Action If the problem persists a system reboot may be required to clear the problem.
Severity Minor
Description The Maintenance Server cannot update internal mapping tables as a result of installing a new component into DMI SP database
Impact The managed objects described by the new installed component can not be seen by the Maintenance Server
Recovery Action Call your NORTEL support organization.
Technical Support Action Look up the return code to find out the cause of the problem.
Severity Information
Description Maintenance Server was notified that a component has been deleted from DMI SP database
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description Maintenance Server was notified that a new language has been installed for an existent component
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description Maintenance Server was notified that a language has been deleted for an existent component
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description Maintenance S+B146erver was notified that a new group has been added to an existing component
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description Maintenance Server was notified that a group has been deleted from an existing component
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description Maintenance Server received a SubscriptionNotice indication from DMI SP
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description The service identified by the reporting managed object is up and running.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description The service identified by the reporting managed object has shut down.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Maintenance Server cannot monitor a started diagnostic
Impact The Maintenance GUI will not receive any indications that a diagnostic has completed its task.
Recovery Action Retry diagnostics. Stop and restart the DMI SP and/or the Maintenance Server. If the problem persists a system reboot may be necessary to clear the problem.
Technical Support Action Look up the rc and extra error code to identity the cause of the problem. Check if DMI SP is working correctly. See if there is enough free space on disk to accommodate the swap files (a potential memory problem exists) a reboot may be necessary.
Severity Information
Description The DMI BIOS does not exist on this machine - therefore less detail will be available.
Impact Some system information details will not be available for maintenance.
Recovery Action Not Applicable
Technical Support Action Check to platform type. If the platform is supposed to support the DMI BIOS, then contact the development organization.
Severity Minor
Description Unable to obtain platform type
Impact Platform specific information and maintenance trees will be incorrect
Recovery Action Platform type must have been set for an install to have occurred. If a new install has just occurred try a reinstall. If it is not a new install then the registry may have been corrupted since then - attempt to set platform type again using support tools.
Technical Support Action Either the system BIOS is not recognized by this NGen software release or the registry keys for platform type are incorrect. Check to see if system has been installed correctly, examine registry and if necessary set correct platform type manually using support tools.
Severity Major
Description System information service unable to build up its internal tables of component information.
Impact System information service will fail to start and maintenance information will not be accessible.
Recovery Action Stop and restart the System Information Service. The problem most likely arises in a system with low memory so a reboot may be necessary.
Technical Support Action System most likely out of memory. Check return codes and if appropriate reboot the system.
Severity Minor
Description System information service unable to initialize the diagnostics interfaces.
Impact System information service diagnostics for serial ports will not be available.
Recovery Action Use the control panel/services applet to stop and start the Symposium System Information Service. The DMI SP (WIn32SL) and Maintenance Server may also need to be restarted.
Technical Support Action Check the return codes. If the problem persists a system reboot may be required to clear the problem. See if correct MIF files are installed using support tools. Check if the DMI SP database is corrupt. If it is stop the Win32SL, delete the database (sldb.dmi) from the disk and restart DMI SP. Reinstall all the Nortel MIF files that are located in the mifs\backup directory. Or if possible restore the sldb.dmi from a backup.
Severity Minor
Description System information service unable to use list of active alarms to initialize states of components.
Impact Maintenance will report components experiencing critical alarms as being healthy.
Recovery Action Check fault return codes. See if the Fault Service is running. Stop and restart the Fault and the System Information Service.
Technical Support Action Look up the return code to identify the cause of the problem.
Severity Minor
Description System Information Service unable to obtain forward alarms from fault.
Impact Maintenance GUI will not receive forwarded alarms and components experiencing difficulty will not have their states updated.
Recovery Action Use the control panel/services applet to stop and restart the Fault Server and System Information Service.
Technical Support Action Look up the return code to identify the root cause of the problem.
Severity Major
Description Software Error: an Operating System function call failed.
Impact The diagnostic interface will not be initialized (no start-up or run-time run-time diagnostics ) or the diagnostic operation from the GUI will not behave as expected.
Recovery Action Retry the diagnostic operation. If problem persists, contact your Nortel service organization.
Technical Support Action If repeatable, this could indicate a problem in the diagnostics interface library software. Please contact the Nortel product support team.
Severity Major
Description Software Error: An invalid (NULL) pointer was passed to a function.
Impact The diagnostic interface will not be initialized (no start-up or run-time run-time diagnostics ) or the diagnostic operation from the GUI will not behave as expected.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software error in either the diagnostics or maintenance libraries, or one of the component instrumentation servers. Please contact the Nortel product support team.
Severity Major
Description Software Error: A lower level base software function failed.
Impact The diagnostic interface will not be initialized (no start-up or run-time diagnostics ) or the diagnostic operation from the GUI will not behave as expected.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software error in one of the Nortel base libraries. Please contact the Nortel product support team.
Severity Major
Description Software Error: Attempt to use an invalid device handle.
Impact The diagnostic interface will not be initialized (no start-up or run-time run-time diagnostics ) or the diagnostic operation from the GUI will not behave as expected.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software error in one of the Nortel base libraries. Please contact the Nortel product support team.
Severity Major
Description Software Error: Invalid parameter passed to function.
Impact The diagnostic interface will not be initialized (no start-up or run-time run-time diagnostics ) or the diagnostic operation from the GUI will not behave as expected.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software error originating from either the maintenance server, component instrumentation servers, or maintenance or diagnostics libraries. Please contact the Nortel product support team.
Severity Minor
Description Could not access value in Windows NT Registry.
Impact A value that was expected to be in the Windows NT Registry was not found. The diagnostic operation will proceed using a default value.
Recovery Action Contact your Nortel service organization.
Technical Support Action This may be a SysOps configuration or script installation issue. Contact your Nortel product support team.
Severity Major
Description Could not allocate virtual memory for the diagnostic interface library.
Impact The system cannot allocate virtual memory..
Recovery Action This may be caused by a software problem, or a bad memory component. Restart system and run memory diagnostics. Contact your Nortel service organization if diag fails or problem persists.
Technical Support Action Run PCDIAGS memory testing. Identify any faulty components and replace. If diags pass, and problem persists after system is back in service, call Nortel product support team re possible software causes (e.g. memory leak, or virtual memory size setting).
Severity Major
Description The diagnostic function library could not convert a string to the UNICODE character set.
Impact The diagnostics are non-functional. Diagnostic requests from the GUI will fail.
Recovery Action This may be caused by a software bug or a corruption in the DMI MIF database. Re-install the server software and restart the system. Contact Nortel if problem persists.
Technical Support Action Shutdown Maintenance Server, System Information, and EMCI services. Run nbdmi2_ci support utility: List then DeleteComponent ids for System Info and EMCI Services; re-install nbmntsiss.mif and nbemcis.mif files (AddComponent), then restart services.
Severity Major
Description An unexpected software exception occurred in the diagnostic function library.
Impact The diagnostics are non-functional. Diagnostic requests or info from the GUI fail or the System Information Service or EMCI Service crashes.
Recovery Action This is a software bug. Contact your Nortel service organization.
Technical Support Action This is a software bug. Contact the Nortel product support team.
Severity Minor
Description A required diagnostic group is missing from a MIF file.
Impact The diagnostics are non-functional. Diagnostic requests or info from the GUI fail.
Recovery Action Call your Nortel service organization.
Technical Support Action You may need to install an updated MIF file. Ensure that all software has been installed for the current release. Contact Nortel product support team if problem persists.
Severity Major
Description An error was returned from a DMI function call. The diagnostic request was rejected by the function library because a low level call to the DMI Service Provider or Component Instrumentation failed.
Impact The diagnostic interface for the requested diag id is not available. This usually indicates an invalid request.
Recovery Action An invalid diagnostic operation was likely requested. Check prerequisite conditions, and operational states of target object before making diag request.
Technical Support Action See admin action. If request was valid but problem persists, call Nortel Product support team.
Severity Minor
Description Failed to register with DMI Service Provider.
Impact Diagnostics not available. The maintenance GUI is not functioning.
Recovery Action It is likely that the DMI Service Provider Service (win32sl) has not started. Start the win32sl service from the Services applet on the Nortel application server.
Technical Support Action See admin action.
Severity Major
Description Software error: received error code from NBsm_QueryService API.
Impact The diagnostic interface is not available. The start-up diagnostics may not have run.
Recovery Action This may be a software installation problem. Re-install the Nortel application server software and restart the system. If problem persists, contact your Nortel service organization.
Technical Support Action Ensure that the Maintenance Server and Win32SL services are installed and functioning.
Severity Minor
Description Unable to initialize diagnostics since a required server is not yet running.
Impact The diagnostics are unavailable. Diagnostics requests from the maintenance GUI fail.
Recovery Action Restart the indicated service on the Nortel application server.
Technical Support Action See admin action.
Severity Major
Description Unable to locate the indicated managed object in the maintenance server mapping table.
Impact The diagnostics are unavailable. Diagnostics requests from the maintenance GUI fail.
Recovery Action Ensure that all software for this release on the Nortel application software is installed. Try stopping and restarting the Maintenance Server, and System Information Service. Call your Nortel service organization if problem persists.
Technical Support Action This could indicate a software error or incorrect installed nbmntsiss.mif file. Use nbdmi2_ci utility to remove and replace MIF file independent of software installation. Contact the Nortel product support team if problem persists.
Severity Major
Description Software Error: A lower level base software function failed.
Impact The diagnostic interface will not be initialized (no start-up or run-time diagnostics ) or the diagnostic operation from the GUI will not behave as expected.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software error in one of the Nortel base libraries. Please contact the Nortel product support team.
Severity Major
Description An unexpected data type was encountered in the Desktop Management Interface for diagnostics. Usually, expected an integer but received something else (like a string).
Impact The specific diagnostic request fails. This may result in incomplete start-up diagnostics or inability to run diagnostics from the maintenance GUI.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software or MIF file syntax error. Report the problem to the Nortel technology organization.
Severity Major
Description An unexpected number of keys was encountered in the Desktop Management Interface for one of the diagnostics groups.
Impact The specific diagnostic request fails. This may result in incomplete start-up diagnostics or inability to run diagnostics from the maintenance GUI.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software or MIF file syntax error. Report the problem to the Nortel technology organization.
Severity Major
Description An unexpected number of rows was encountered in the Desktop Management Interface for one of the diagnostics groups.
Impact The specific diagnostic request fails. This may result in incomplete start-up diagnostics or inability to run diagnostics from the maintenance GUI.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software or MIF file syntax error. Report the problem to the Nortel technology organization.
Severity Major
Description An unacceptable value was returned for an attribute in the Desktop Management Interface for one of the diagnostic groups.
Impact The specific diagnostic request fails. This may result in incomplete start-up diagnostics or inability to run diagnostics from the maintenance GUI.
Recovery Action If the problem persists, please contact you Nortel support organization.
Technical Support Action This could indicate a software or MIF file syntax error. Report the problem to the Nortel technology organization.
Severity Major
Description The diagnostic function interface is not registered with the DMI Service Provider service.
Impact Until the diagnostic interface is registered, there are no start-up diagnostics or ability to run diagnostics from the maintenance GUI.
Recovery Action Stop/re-start Maintenance Server, System Information Service, and EMCI Server (or reboot server system). Wait at least 1/2 hour after boot to Windows NT. Retry diagnostic request. If problem persists, contact your Nortel support organization.
Technical Support Action See admin actions. If problem persists, this may indicate a software or MIF file error. Report the problem to the Nortel technology organization.
Severity Minor
Description A thread used in the diagnostic interface software failed to stop by itself.
Impact A small amount of memory may be lost. If this problem occurs repeatedly, there is a potential impact on the system performance as the memory loss would be cumulative each time a diagnostic is run.
Recovery Action If problem occurs once or twice, there is no cause for concern. If problem persists, the system performance could degrade with repeated running of diagnostics. Reboot server and do not run diagnostics. Report problem to your Nortel Service organization.
Technical Support Action See admin actions. This indicates a software bug. Report the problem to the Nortel technology organization.
Severity Minor
Description There is a syntax error in the call format string for at least one of the diagnostic ids in the MIF file.
Impact The specific diagnostic request fails.
Recovery Action There may be a corruption of the MIF database or an invalid MIF file installed. Re-install the current version of the server software.
Technical Support Action This may indicate a bug in the MIF file. See NTPs for MIF file name. Using the nbdmi2_ci utility (ListComponents, DeleteComponent, AddComponent), re-install the MIF file. Then reboot to WinNT and retry diagnostic request after 1/2 hr.
Severity Minor
Description This indicates a software error in which the data structure which controls the diagnostic interface for the specified target is invalid.
Impact The specific diagnostic request fails. If the inventory table entries are severely corrupted, all diagnostic requests may fail.
Recovery Action Stop/re-start Maintenance Server, System Information Service, and EMCI Server (or reboot server system). Wait at least 1/2 hour after boot to Windows NT. Retry diagnostic request. If problem persists, contact your Nortel support organization.
Technical Support Action This may indicate a bug in the component server software which calls the diagnostics APIs. The component servers affected are currently the System Information Service and the EMCI Server. Report problem to Nortel Product Support organization.
Severity Minor
Description The Nortel application server received a request to stop a diagnostic which is not already running.
Impact The specific diagnostic request fails.
Recovery Action Please ensure that you only try to stop diagnostics which are already running.
Technical Support Action Not Applicable
Severity Major
Description This indicates a software or MIF file error in which the language of the MIF file is unknown.
Impact All diagnostic requests fail.
Recovery Action There may be a corruption of the MIF database or an invalid MIF file or language installed. Re-install the current version of the server software.
Technical Support Action Using the nbdmi2_ci utility (ListComponents, DeleteComponent, AddComponent), re-install the MIF file and any language extensions. Then reboot to WinNT and retry diag request after 1/2 hr. See NTP for detailed instructions. Contact Nortel Product Support.
Severity Minor
Description A diagnostic process on the Nortel application server crashed unexpectedly.
Impact The specific diagnostic request returns this Event Code as it's error code. The target object is disabled until successfully re-tested. Repetitive testing of this diagnostic may result in memory leaks and eventual degredation of system performance.
Recovery Action The diagnostic process associated with a diagnostic request unexpectedly terminated due to a software fault or user initiated termination (CTRL-C or CTRL-BREAK at server keyboard). If not user initiated, contact your Nortel Service organization.
Technical Support Action If diagnostic termination was not user initiated (by CTRL-C or CTRL-BREAK), there is likely a software bug or hardware fault on the Nortel application server. Cross reference the indicated exception code with NTP and/or Microsoft documentation.
Severity Critical
Description A diagnostic process on the Nortel application server may have been manually terminated (such as via a CTRL-C). However, the configuration information for this diagnostic states that manually stopping it puts hardware into an un-recoverable state.
Impact The specific diagnostic request returns this Event Code as it's error code. The target object is disabled until successfully re-tested. Hardware may now be unstable. The target object hardware may need a system power cycle before it will function again.
Recovery Action Shutdown the application server and turn the power on/off (remove/insert circuit pack if hardware is on an IPE shelf). Wait at least 1/2 hour after boot to WinNT before trying diagnostic request again. Do not type CTRL-C or CTRL-BREAK at server keyboard.
Technical Support Action If diagnostic termination was not user initiated (by CTRL-C, or from GUI screen), there is likely an undetected software bug or hardware fault on the Nortel application server. Call Nortel Product Support for debugging assistance.
Severity Major
Description The software mechanism which prevents simultaneous requests from running the specified diagnostic is broken and does not fix itself.
Impact All further requests for running this diagnostic on any target fail.
Recovery Action Reboot the application server. Wait at least 1/2 hour (for all services to complete initialization) after booting to Windows NT before attempting maintenance or diagnostics operations via the client GUI. Report problem to Nortel Service Organization.
Technical Support Action This is likely a software bug. Contact the Nortel Product Support team and technology organization for investigation.
Severity Minor
Description The diagnostic request was rejected because the operational state of the target object is not OffDuty or Disabled.
Impact Not Applicable The user must put the target into the proper maintenance state prior to requesting the diagnostic to run.
Recovery Action Select the maintenance property sheet for the target object and courtesy down before attempting to run a diagnostic on that object. Also, ensure that the identified prerequisite conditions are performed prior to running the diagnostic.
Technical Support Action Select the maintenance property sheet for the target object and courtesy down before attempting to run a diagnostic on that object. Also, ensure that the identified prerequisite conditions are performed prior to running the diagnostic.
Severity Critical
Description The time period for which the diagnostic interface server software waits for diagnostic processes to return results was exceeded by at least one diagnostic process. This could be because of abnormal termination or lock-up of the diagnostic process.
Impact A diagnostic process may have locked up due to a hardware problem preventing software from continuing. Depending on the nature of the fault which caused the process to fail to respond, the platform may not be able to be put into service.
Recovery Action Reboot the application server and allow start-up diagnostics to complete (when diagnostic process windows stop popping up on the screen). If any of the black diagnostic windows does not disappear, record what it says on the screen and call Nortel.
Technical Support Action A diagnostic process may have locked up due to hardware problem (e.g., a problem with a DSP Carrier card's PCI bus interface). Record info from server screen and logs. Replace any suspected faulty hardware. Call Nortel Product Support for investigation.
Severity Minor
Description The logic within the diagnostic interface for the server only allows re-testing of disabled targets with the diag id that previously failed.
Impact A diagnostic process may have locked up due to a hardware problem preventing software from continuing. Depending on the nature of the fault which caused the process to fail to respond, the platform may not be able to be put into service.
Recovery Action Reboot the application server and allow start-up diagnostics to complete (when diagnostic process windows stop popping up on the screen). If any of the black diagnostic windows does not disappear, record what it says on the screen and call Nortel.
Technical Support Action A diagnostic process may have locked up due to hardware problem (e.g., a problem with a DSP Carrier card's PCI bus interface). Record logs and info from server screen. Replace any suspected faulty hardware. Call Nortel Product Support for investigation.
Severity Minor
Description The prerequisite conditions for the specified diagnostic require that diagnostics on some of the dependent objects be sucessfully completed first.
Impact Not Applicable The user must run and pass the diagnostics in the indicated order.
Recovery Action Courtesy down (take OffDuty) and run the prerequisite diagnostics for some of the dependent objects before trying this diag id again.
Technical Support Action Not Applicable The user must run and pass the diagnostics in the indicated order.
Severity Minor
Description The last diag id which was run on the target must be specified in order to retrieve results.
Impact Not Applicable The diagnostic results for the indicated last diag id on the specified target should be queried.
Recovery Action The diagnostic results for the indicated last diag id on the specified target should be queried.
Technical Support Action The diagnostic results for the indicated last diag id on the specified target should be queried.
Severity Major
Description A diagnostic failed. In order to clear the 'Disabled' maintenance state or allow other diag ids to run on the target object, the indicated diag id must be successfully re-run (i.e. must pass) for the target object.
Impact The diagnostic results for the indicated diag id on the specified target should be queried for possible Field Replaceble Unit(s) (FRU) info. Replace the hardware according to the probability of that FRU causing the diagnostic failure. Re-test.
Recovery Action The diagnostic results for the indicated diag id on the specified target should be queried for possible Field Replaceble Unit(s) (FRU) info. Replace the hardware according to the probability of that FRU causing the diagnostic failure. Re-test.
Technical Support Action Follow admin actions. If problem persists, you may investigate further by looping the diag continuously from the command line (see NTP). Ensure that no call processing resources are using the affected hardware (courtesy down) prior to testing this way.
Severity Major
Description A software timeout occurred waiting for the start of the thread which monitors a diagnostic.
Impact Unable to retrieve result of diagnostic. If diagnostic allows Stop, unable to stop diagnostic.
Recovery Action The problem may be due to excessive traffic on the system or a virtual memory leak which significantly affects system performance. Resolve the performance problem before attempting diagnostics again.
Technical Support Action To reset diagnostics: Stop & Restart the Nortel Maintenance Server, and System Information Services. Then KILL the EMCI Service (use Task Manager); then Start the EMCI Service. Do not Stop the EMCI Service as this would bring down calls.
Severity Major
Description The diag id could not be run since the target object instance is not currently present in the system.
Impact Diagnostic can only be run on target object hardware that is currently present in the system.
Recovery Action Ensure that the target object device is present and powered up before attempting diagnostics. Examine the maintenance property sheet (in Maintenance Admin screen) to ensure that target is OffDuty or Disabled before attempting diagnostics.
Technical Support Action Ensure that the target object device is present and powered up before attempting diagnostics. Examine the maintenance property sheet (in Maintenance Admin screen) to ensure that target is OffDuty or Disabled before attempting diagnostics.
Severity Minor
Description The diagnostic could not be run due to a previous failure on selected target.
Impact User error. Existing fault must be cleared first by running and passing failing diagnostic .
Recovery Action Refer to Diagnostic Results Log (select Last Result button to regenerate the last diag result) for potential replaceable devices (FRUs). If hardware is identified faulty, replace FRU and re-run previously failing diag.
Technical Support Action If there's an FRU list in Diag Results Log, replace part(s) according to probability. If diag fails but no FRU list, software or installation error (contact Product Support). Rerun failing diag id on target (must pass). Then retry the new request.
Severity Minor
Description This is an event that is used to simulate errors via the diagnostics API test driver.
Impact There is no product impact. This event is only generated by designer test software.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Maintenance general return code.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to access the DMI Service Provider.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Component or group not installed in MIF database.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Group not found in MIF database.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description NBmnt Ci mapping table full (obsolete).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error listing DMI groups.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to register with DMI as management application.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to deregister from DMI as a management application.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to register groups/attrs with DMI as component instrumentation.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to obtain pragma string from DMI (obsolete).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Invalid parameters have been passed to an API.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Invalid environment for RPC.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Shut down Maintenance Server error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description the calling client is already registered to receive indications.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Generic RPC error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Maintenance error forming RPC binding to DMI SP as part of calling DMI management I/F or error binding for events forwarding.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Maintenance error releasing RPC binding to DMI SP as part of calling DMI management I/F.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to list DMI components.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to allocate memory.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to create a temporary file (obsolete)
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error writing in temporary file (obsolete).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Feature not implemented.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The string instance for an object doesn't match the correspondent DMI key list.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description DmiGetMultiple call failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The specified object key/ids cannot be found in the mapping tables.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description DmiGetSubscriptionAddress call failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description DmiAddRow call failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description There is no mapping between managed object key and DMI componentId/groupId.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description DmiListClassNames call failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to allocate memory.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description DmiGetAttribute call failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description DmiListAttributes call failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to start RPC server for reverse RPC notifications.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to create the mutex to synchronize event delivery.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error trying to delete an invalid entry in forwarding table.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to forward an event to the registered clients.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to originate an event via DMI SP.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Invalid state transition attempted with NBmnt_eSetState.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Invalid state transition attempted.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error setting one or more dmi attribute(s).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The server doesn't have yet the information for an object, but it still trying to get the information from the component instrumentation.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error getting diagnostics list.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Cannot start/stop a diagnostic.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error getting diagnostics result.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Component's Verify attribute is not set to 0x07 = This component exists, and is functioning correctly.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description DMI group not found.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Time out passed in monitoring started diagnostic completion.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Maintenance server unable to deliver an event to the client.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Maintenance instance rules API unable to generate instance from supplied parameters.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Bad data format in FRU information file.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Alarm list file from fault is bad.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to open a remote file (obsolete).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error using memory mapping driver (mapmem.sys). Driver not on system or not installed properly in registry.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Date Modified 98/06/03
Severity Not Applicable
Description Error using DeviceIoControl to instruct driver (mapmem.sys) to map in memory for DMIBIOS header.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Could not find DMIBIOS header. DMIBIOS may not exist on this machine.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error using DeviceIoControl to instruct driver (mapmem.sys) to map in memory for DMIBIOS structures.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description NULL pointer incorrectly returned when mapping in DMIBIOS memory.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Software Error: An Operating System function call failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Software Error: An invalid (NULL) pointer was passed to a function.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Software Error: A lower level base software API failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Software Error: Attempt to use an invalid device handle.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Software Error: Invalid parameter passed to function.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Could not access value in Windows NT Registry.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Could not allocate memory.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The diagnostic function library could not convert a string to the UNICODE character set.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description An unexpected software exception occurred in the diagnostic function library.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description A required diagnostic group is missing from a MIF file.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description An error was returned from a DMI function call. The diagnostic request was rejected by the function library because a low level call to the DMI Service Provider or Component Instrumentation failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Failed to register with DMI Service Provider.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Software error: received error code from NBsm_QueryService API.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to initialize diagnostics since a required server is not yet running.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Unable to locate the indicated managed object in the maintenance server mapping table.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Software Error: A lower level base software function failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description An unexpected data type was encountered in the Desktop Management Interface for diagnostics. Usually, expected an integer but received something else (like a string).
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description An unexpected number of keys was encountered in the Desktop Management Interface for one of the diagnostics groups.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description An unexpected number of rows was encountered in the Desktop Management Interface for one of the diagnostics groups.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description An unacceptable value was returned for an attribute in the Desktop Management Interface for one of the diagnostic groups.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The diagnostic function interface is not registered with the DMI Service Provider service.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description A thread used in the diagnostic interface software failed to stop by itself.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description There is a syntax error in the call format string for at least one of the diagnostic ids in the MIF file.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description This indicates a software error in which the data structure which controls the diagnostic interface for the specified target is invalid.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The Nortel application server received a request to stop a diagnostic which is not already running.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description This indicates a software or MIF file error in which the language of the MIF file is unknown.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description A diagnostic process on the Nortel application server crashed unexpectedly.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description A diagnostic process on the Nortel application server may have been manually terminated (such as via a CTRL-C). However, the configuration information for this diagnostic states that manually stopping it puts hardware into an un-recoverable state.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The software mechanism which prevents simultaneous requests from running the specified diagnostic is broken and does not fix itself.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The diagnostic request was rejected because the operational state of the target object is not OffDuty or Disabled.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The time period for which the diagnostic interface server software waits for diagnostic processes to return results was exceeded by at least one diagnostic process. This could be because of abnormal termination or lock-up of the diagnostic process.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The logic within the diagnostic interface for the server only allows re-testing of disabled targets with the diag id that previously failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The prerequisite conditions for the specified diagnostic require that diagnostics on some of the dependent objects be sucessfully completed first.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The NBdgn_miDiagResults API must specify the last diag id which was run on the target.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description A diagnostic failed. In order to clear the 'Disabled' maintenance state or allow other diag ids to run on the target object, the indicated diag id must be successfully re-run (i.e. must pass) for the target object.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable