ServerWORKS Manager README.TXT Release notes for ServerWORKS Manager Version 4.2 Copyright (c) Digital Equipment Corporation 1995, 1999 This README.TXT is intended for the ServerWORKS Manager user. Its purpose is to provide additional product information and corrections to the user documentation. *Any section that is marked by an asterisk (*) in this file is included only in this English-language version. All unmarked sections are included in the translated versions. When information in the readme longer applies, the text is removed. The section numbers remain. Numbering is not changed. *It is recommended that you view and print the readme file from Wordpad or Word for Windows instead of Notepad. Contents 1.0 Introduction 2.0 What's New in ServerWORKS Manager Version 4.2 3.0 Installation and Performance Issues 4.0 ServerWORKS Manager Application Issues 5.0 ServerWORKS Manager SNMP Agent Issues 6.0 Platform-Specific Information 7.0 ClientWORKS Issues 8.0 Technical Support 9.0 Trademarks 1.0 Introduction ServerWORKS Manager is a workgroup and server management Product for DIGITAL servers. ServerWORKS Manager uses Simple Network Management Protocol V1 (SNMP V1) to monitor the network for problems, identifying Them quickly to help you avoid expensive downtime. ServerWORKS Manager consists of: - ServerWORKS Manager Console - ServerWORKS Manager Applications - ServerWORKS Manager Agents - ServerWORKS Manager Tutorial - ClientWORKS - Mylex Global Array Manager (GAM) - StorageWORKS Command Console (SWCC) *2.0 What's New in ServerWORKS Manager Version 4.2. What's new in the SW 4.2 NT agents: - Support for NT 4.0 Service Pack 4 - Support for the latest Digital Clusters for NT release/servicepack - Support for the Compaq AlphaServer DS20 - Updates to the PCIM agents to provide more data. (1) New temperature probe information displying the actual temperature values. (2) More SCSI storage device stats (Vendor, Model and FWREV). (3) Unsupported SCSI stats are now displayed as N/A as opposed to 0 values. (4) Multiple SCSI Controllers are now displayed. (5) ASR button removed as element is now supported. - Changes to the Server Management agent and Minimal Health Application - Additional support for NetWare agents. 2.1 Integration with Insight Manager ServerWORKS supports application launch with context for Compaq Insight Manager. Insight Manager is available in English only. If you plan to Use Insight Manager to view either DIGITAL servers or Compaq servers, ou must obtain your own copy. If you are discovering Compaq servers with ServerWORKS, you will notice new Compaq icons. As always,you can use any bitmap you want to represent a particular object. 2.1.1 The merger of Compaq and Digital means you get both DIGITAL agents and Insight Manager agents when you integrate. The Installation and User Guide had gone to print when the decision was made to include both agents for users. Therefore,in the manual, you are advised to make a selection of either or both. In fact, both types of agents are installed. *2.1.2 Not all features of Insight Manager are supported on ServerWORKS, although the function may not be disabled. For more information on the differences in the functionality and displays of Insight Manager and ServerWORKS, refer to the integration document (integrat.pdf) included on the Insight manager CD-ROM. 2.1.3 When using filters on Insight Manager to show only NT 4.0 systems some DIGITAL systems may not appear if they are using variations on the version of NT 4.0. To modify the "Windows NT 4.00" filter to include your version of the OS. On Insight Manager: 1. Open the Device box associated with the system, and click the Filter button. 2. Select Setup Filters from the menu. 2. Select Filter Type->Operating System. This displays the current OS filters. 3. Select the Windows NT 4.00 filter, and click the Edit button. A dialog box will appear listing all of the operating systems that Insight Manager has detected. Each one is associated with a checkbox. 4. Click on the checkbox associated with your operating system version. 6. Click the Next -> Finish. 7. Close the Setup Filters dialog box. The Windows NT 4.00 filter should now display your server. 2.2 New Platform Agents ServerWORKS agents now support these new or enhanced hardware platforms: *- DIGITAL Server 5215 *- DIGITAL Server 5225 *- DIGITAL Server 3225 *- DIGITAL Server 3215R *- DIGITAL Server 3220R - DIGITAL Server 500 233 - DIGITAL Server 3205 2300 - DIGITAL Server 1200 2266 - DIGITAL Server 1200 2300R - DIGITAL Server 1200 2333R - DIGITAL Server 5210 2333 - DIGITAL Server 3210 2333 - DIGITAL Server 7105 1200 - DIGITAL Server 9100 1200 - DIGITAL Server 9105 1200 - AlphaServer 8200, AlphaServer8400 2.2.1 Third-Party Integration You can integrate power management software from Exide and APC. To integrate Exide's OnliNet or APC's Power Chute, refer to the documentation supplied by that vendor. Exide and APC supply utilities that enable you to perform the integration. Once integrated, you can use ServerWORKS to discover Exide and APC devices. 2.2 ServerWORKS Enterprise Manager Integration Guide is not internationalized. It is available in English only. 2.4 CA Unicenter TNG/ServerWORKS integration requires you to install Microsoft Data Access Components (MDAC) V2.0 prior to installation of CA UniCenter TNG/ServerWORKS Integration, even though you have already installed MDAC 1.5c prior to installing ServerWORKS Manager Console. Install V2.0 if you get the following message:"Unable to open database." 2.5 After you complete the CA TNG/Unicenter integration using the instructions in the ServerWORKS Manager Enterprise Integration Guide, you can perform an additional task to enable the icons to change from unknown node type to DIGITAL server types. Although you can choose the icon from a menu command, internal code from Unicenter causes a significant delay. A more efficient method is to use the following procedure: 1. Open a command window and execute the following commands: awservices start unicntrl start uni 2. From start menu run TNG You also have the option to monitor polling events from a command window. Type the following command: start awm_catch POLL_EVENT SNMP 3.0 Installation and Performance Issues *During installation it may be necessary to use Alt/Tab key combination to view the correct installation screen or minimize a window for easiest viewing. 3.1 If you have factory-installed software on older servers, the version of setupapi.dll, which is used during the uninstall of ServerWORKS is incompatible with ServerWORKS V4.0 or greater. During an uninstall the mfc42.dll is removed. To fix this either reinstall ServerWORKS to get the newer version of the file or copy mfc42.dll from the \swmgr directory to the winnt\system32 directory. 3.2 Anytime the database utility refreshes the database or the existing database is replaced by the empty database, you must reintegrate DIGITAL third-party applications using the third-party reintegration Buttons provided in the installation procedure. These third-party Applications include RSM, RMC, Mylex and Storage Works Command Console (SWCC) version 2.0. Other vendors (such as APC) ship a component in their kit that does the installation and removal of the ServerWORKS integration. 3.3 When a user brings up the Alarm Configuration tool and selects a number of objects to operate on, each object is probed by SNMP for the object's capabilities and alarm settings. This alarm synchronization may take an unusually long time on NetWare systems, due to the low priority of the NetWare SNMP extension agent process on that platform. See section 5.1.3 below for information on obtaining a patch for this problem. 3.4 When you install SWCC on a Windows 95 Japanese system, you may see an error message as the installation closes down, even though the installation and integration with ServerWORKS Manager Console have been completed successfully. You can safely ignore this error message. 3.5 Do not install ServerWORKS V4.0 or greater and its server management agent on a Windows NT Version 3.51 system. ServerWORKS V4.0 or greater and its agents are not supported on NT 3.51. 3.5.1 ServerWORKS cannot be installed on a network drive. 3.5 You must install Microsoft Data Access Pack (ODBC Version 3.5) in its entirety to ensure proper updating of the ServerWORKS Manager database. See the file \ODBC35\readme.txt for more information. 3.6 After you install the mandatory Microsoft Data Access Pack and ServerWORKS Manager Console, exiting the Control Panel applet "ODBC Data Source Administrator" can result in an error under some versions of Windows 95. To avoid this problem or fix it once it occurs, install the Microsoft Data Access Components by running \MDAC15\mdac_95.exe from the ServerWORKS installation CD-ROM. Follow the online instructions provided by Microsoft. 3.7 At the end of the ServerWORKS Manager installation, you may see a message indicating that MSRD2X32.dll was unable to register itself in the system registry. Install the Microsoft Data Access Components by running \MDAC15\mdac_95.exe from the ServerWORKS installation CD-ROM. Follow the online instructions provided by Microsoft. 3.8 If you install an enterprise manager that uses port 162 for SNMP-trap, there will be a conflict with ServerWORKS. The application that is started first takes the trap port. Therefore, you cannot run an enterprise manager simultaneously with ServerWORKS unless you change the trap port for the enterprise manager. 3.9 If you upgrade the agents to Version 4.0, be sure that you upgrade the ServerWORKS Manager Console to Version 4.0 or greater as well. 3.11 Upgrading from ServerWORKS Manager V3.1 or earlier. You should first upgrade to ServerWORKS Manager 3.2. ServerWORKS Manager 3.2 is a prerequisite for upgrading to ServerWORKS V4.0 or greater. You can also upgrade from ServerWORKS V3.3. 3.12 Digital Clusters ServerWORKS V4.0 or greater does not support managing DIGITAL Clusters V1.0 on Windows NT V3.51. You must upgrade to DIGITAL Clusters V1.1 on Windows NT V4.0. 3.12.1 Cluster applications (SQL, Exchange and Lotus Notes)are not represented correctly unless they are created using the following rules. 1) The naming convention (ntcObjectName in svrclu.mib of MIB Browser of ServerWORKS Manager) used when created in the Microsoft Cluster Administrator or Digital Cluster Administrator must contain the name of the application. Ex: object name=westcoastSQLcluster 2) The object type must be IP address. Do not use application as the object type. The IP Address must also be a valid, not fictional, address. 3.13 You cannot run ServerWORKS 4.0 or greater agents on one server in a cluster and ServerWORKS V3.3 agents on another server in the cluster. 3.14 The POD database has a limitation of 64 characters on the display name. Therefore, the file share name in NT Server. Management through ServerWORKS has the same limitation. 3.15 Enterprise Manager Integration 3.15.1 The Tivoli TME10/NetView integration package for Digital UNIX is located on the CD-ROM. You install this package on a computer running Digital UNIX. You will find two files in the directory DUNIX: - install.sh - Installs the integration package DECPNV.tar - DECPNV.tar - Contains the integration package files Setup your environment to install.sh as follows: 1. Install Tivoli TME10/NetView on the Digital UNIX machine. 2. As the installer, use the root logon. 3. Provide five MB of disk space. To install: 1. As root, navigate to the DUNIX directory. 2. Double-click on the install.sh script. 2. The install script is automatic, but does require that you acknowledge information at various points in the set- up. At completion, install provides two summaries: - a list of the files copied - a list of any errors encountered during the installation When the installation is complete, the temporary disk space, on the Digital UNIX system space is recovered. You can delete the two summary logs. ServerWORKS Manager 4.0 or greater provides integration with Tivoli TME10 NetView. The procedure for integrating the two products is documented in the DIGITAL ServerWORKS Manager Enterprise Management Integration Guide. This section of the readme calls your attention to the following considerations: 1. You may notice Alarm Configuration requires some time to run its first activation. This is because cacheinformation is being built up for reuse later. Also, the more alarms on the target node, the longer Alarm Configuration will take to acquire its information. 2. If ODBC is already installed when ServerWORKS for Tivoli TME10 NetView is installed, you MUST reboot the machine prior to running Tivoli TME10 NetView. 3. System Browser can be programmed to use snmp get/set communities other than the default "public". To do this: a. Make sure ServerWORKS for Tivoli TME10 NetView is NOT running b. Locate the file DecDiscover.reg in the following directory: $INSTALL_DIR\ov\registration\C\DEC c. Go to the following line: Command: ... smb.exe -c public -d public -f1 ... (where the ... (ellipsis) indicate omitted text ) d. To change the snmp get/set community, use the -c option to specify the get community, and/or the -d option for snmp set. 4. To uninstall the ServerWORKS integration package from Tivoli TME10 NetView w/o Uninstalling NetView itself, do this: a. Start the TME10 NetView application. b. Close all maps that show DIGITAL resources. c. Select Exit from NetView's File menu to close NetView. d. Load the ServerWORKS CD. e. Double click on the unInstal.bat icon. f. During uninstall, the MIB Loader dialog box is displayed. Press Close to exit it. g. Start the TME10 NetView application. h. From the NetView's Options menu, select Trap Settings ... Note: if Trap Settings menu item is not shown, you must switch to advanced menus mode. To do this, Select Console Settings from NetView's Options menu. Find the "Menus at startup" edit box, and set it to Advanced. Press Apply then OK. You must now close and restart NetView to force the menu option to take effect. i. In the "Select an enterprise" group box, select the svrMgt enterprise. 3.15.2 This README.TXT is intended for the ServerWORKS for Hewlett-Packard OpenView user. This README augments the DIGITAL ServerWORKS Manager, Enterprise Management Integration Guide. The user should consult that guide first. This document is intended to contain information that broke too late to make the printing deadline of the guide. When you first run Alarm Configuration, it may start slowly. This is because cache information is being built up for later reuse. Subsequently, it will start faster. Alarm Configuration's delay at start is proportional to the number of alarms on the selected node. The more alarms there are, the more information that must be acquired, and the longer Alarm Configuration takes to start. If ODBC is already installed when ServerWORKS for Hewlett- Packard OpenView is installed, you MUST reboot the machine prior before running HP OpenView. System Browser can be programmed to use snmp get/set communities other than the default "public". To do this: 1. Make sure ServerWORKS for Hewlett-Packard OpenView is NOT running. 2. Locate the file DecDiscover.reg in the following directory: $INSTALL_DIR\registration\C\DEC 3. Go to the following line: Command: ... smb.exe -c public -d public -f1 ... where the ... (ellipsis) indicates omitted text 1. To change the snmp get/set community, use the -c option to specify the get community, and/or the -d option for snmp set. To uninstall the ServerWORKS integration package from Hewlett-Packard OpenView without uninstalling OpenView, perform these steps: 1. Start the HP OpenView application. 2. Close all maps that show DIGITAL resources. 3. Click File --> Exit to close OpenView. 4. Load the ServerWORKS CD. 5. From the Start menu, select Programs --> Command Prompt. 6. Navigate to the ServerWORKS' OpenView directory on the CD-ROM For example, if the CD is in drive D:, type the following at the command prompt (do not include the command prompt) C:\> or D:\> ): C:\> D: D:\> cd SWMgr\SWM_US\SWMgrHOV 7. Set the OV_DIR environment variable to the OpenView bin directory. To do this, use a command like: set OV_DIR=X:\OpenViewDir\bin where, * X:\ is the drive where OpenView is installed, and * OpenViewDir is where you installed OpenView. You can check that the OpenView\bin directory is correct by finding ovw.exe there. The full command line (including the command prompt) might look like the following: D:\SWMgr\SWM_US\SWMgrHOV> set OV_DIR=C:\OpenView\bin 8. Start the uninstall program using the uninstall command. For example, this might be: D:\SWMgr\SWM_US\SWMgrHOV> uninstall 9. When the MIB Loader dialog box is displayed, click Close. 10. Start the HP OpenView application. 11. From the OpenView's Options menu, select Event Configuration. 12. In the "Enterprises" group box, select the svrMgt enterprise. 13. In turn, select each item in the "Events for Enterprise svrMgt ..." group box (there are four items), and from the Event Configuration menu choose Edit --> Events -->Delete. For example, select svrThrHighExc and press Edit --> Events -->Delete. 14. In the "Enterprises" group box select the svrMgr enterprise, and from Event Configuration's menu select Edit --> Enterprises --> Delete. 15. Press Event Configuration's File --> Close to exit the Event Configuration dialog box. 16. Click Map --> Exit to close OpenView. 17. Start the HP OpenView application. NOTE: If you double-click an icon that formerly was a DIGITAL resource, you get the interface category icon plus some other icons that may include: Environment, Network, Storage and System. These extra categories are artifacts left in the OpenView database, and require that the resource be deleted and rediscovered. To do this, navigate to the map that contains the DIGITAL resource as an icon, then select Delete from OpenView's Object menu. After deleting all DIGITAL resources, or at least the ones you want to do on this pass, close and restart OpenView. When you first start of OpenView, you may receive error messages about an undefined DIGITAL field. If this occurs, simply close and restart OpenView. 3.15.3 When using OpenView or NetView and using System Browser, you can display graphs of thermal sensor information only in degrees Fahrenheit. Selecting Celsius as the unit of measure has no effect. 3.16 Community names behave differently under Windows NT V4.0 SP4. Community names used by ServerWORKS agents must be defined with read/write access so ServerWORKS can perform Get and Set operations. Installation of the Service Pack makes all SNMP communities read-only. With SP4, the user must set the access type for a community name to read/write. 3.17 TCPIP names for Cluster Servers. If you are installing DIGITAL Cluster for NT or Microsoft Clusters for NT, the TCPIP host name for a node must be the same as the network computer name. ServerWORKS does not support IP Discovery of clusters if the node name and computer name are different. Set the names in the Network applet of the Control Panel. For example, when you are installing the Microsoft for NT Cluster software the following prompt appears: "Enter the administrative name associated with this network and specify the role it will play in the cluster." The administrative name is the computer name that you find on the Identification page of the Network applet in the Computer Name field. The name must match the Host Name on the Protocols-Microsoft TCPIP Properties-DNS page of the Network applet. 3.17.1 Install ServerWORKS agents for NetWare on one system at a time. Select One system from the server list on the Select Component screen. Although you can select multiple systems from the list, agents are not installed successfully. 3.18. Both ServerWORKS and ClientWORKS install agents on non-server platforms and you may have agents from both applications on a desktop system. Generally, the agents of both applications report as expected. However, if you uninstall ServerWORKS after you have installed ClientWORKS on a DMI 2.0-complient computer with temperature and voltage probes, the ServerWORKS uninstall program uninstalls the ClientWORKS agents for these objects. Conversely, uninstalling ClientWORKS uninstalls the ServerWORKS agents for these objects. 3.19 The following messages are generated by Minimal Health and may appear in the Event Viewer. "Contact lost with server. Minimal Health terminating." followed by a log code: This message means that SNMP was stopped for some reason. The reason may be that you manually stopped it, which is not a problem. The message might also indicate a serious network or SNMP problem. "No Managed Devices Found for Template Entry..." followed by an OID and other information about a device: This message is normal and simply means that this system does not contain the named piece of hardware to monitor. The device is identified by the OID. 3.20 The Minimal Health application is not available for Alpha NT in ServerWORKS 4.0 or greater. You can continue to use the minimal health feature built into the ServerWorks 3.3 server management sub-agent by deselecting the "Digital Server Management Agent" item on the "Select Optional Agent Components" screen during an agent upgrade installation. 3.21 It is strongly recommended that you create a new database when you install ServerWORKS V4.0 or greater instead of using a previously installed database. You can remove the previously installed version of ServerWORKS V3.2 or V3.3 during the installation of V4.0 or greater by selecting the option "Remove the installed ServerWORKS." By converting an existing V3.2 or V3.3 database, you may lose some of the information. You will see the prompt "Some database information is not converted." For example, all the information about alarm actions may not be converted. If you choose to retain the old database, ServerWORKS converts it to the correct format. At that time, the Select Database dialog box opens and prompts you to select the database to convert. If you have installed into the same directory as the previous version, choose "PCMGR.MDB" and click OK. When the conversion is complete, the database is copied to the installation directory. 3.22 While the server client is initializing, you cannot access the server from ServerWORKS Manager Console. If you attempt to do this you may see the error: SNMP Error 40. This indicates the server agent is busy. 3.23 WBEM and Insight Manager do not support Digital clusters. Only objects that are identified as server.Digital objects or server.Compaq objects support WBEM and Insight Manager. *3.24 SNMP.EXE Leaks Memory When Queried On Windows NT 4.0 SP4 systems, SNMP.exe produces substantial memory leaks when accessed or queried. Messages such as "Your system is running low on virtual memory" appear when this occurs. Microsoft has a supported fix to correct this problem. The fix has not been fully regression tested and should only be used if a system is demonstrating the specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT service pack that contains this fix. If you are experiencing this problem, download the fix from the Microsoft hotfix web site. You can find the download by searching the Knowledge Base for Q196270.txt. This article gives further details about the problem, its correction, and support from Microsoft. You can find the hotfix at: ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/ hotfixes-postSP4/Sms-fix/ This hotfix has been posted this Internet location as Smsfixi.exe (x86) and Smsfixa.exe (Alpha). This hotfix was updated on December 17, 1998. 4.0 ServerWORKS Manager Application Issues If you want to run ServerWORKS Manager continuously, you are advised to use Windows NT V4.0, a more robust operating system than Windows 95. If you run ServerWORKS Manager continuously on a Windows 95 system with minimal memory resources, the continuous reception of alarms may cause creeping memory consumption, or "memory leaks." To prevent memory leaks, you are advised to install Microsoft Data Access Pack (ODBC Version 3.5). You can also improve the configuration by changing your network drivers setting. Expand the buffer space from 2K to 64K. This may improve system resource utilization. 4.2 Winsock Proxy Service ServerWORKS Manager does not function on a system configured to use a Winsock Proxy service. Several ServerWORKS Manager components need to communicate with each other across TCP connections using predefined TCP port numbers. In some cases the Winsock Proxy architecture prevents these connections from succeeding. 4.3 Viewer Limitation When an object is replicated in multiple views, status updates are reflected only in the view where the object is directly manipulated. All other views containing the object are updated only after you collapse and re-expand them. 4.4 You might receive hundreds, even thousands of alarms. Displaying the alarms requires memory resources and disk space. If you anticipate large numbers of alarms, consider increasing your memory resources and the disk capacity. Also consider moving the ODBC data source to its own disk. Use the ODBC applet in Control Panel to do this. 4.4.1 To view alarms on a single system, select the system with a single click in ServerWORKS Manager. From the tool menu, select the View Alarms icon. The resulting display will show you all the alarms your console has recorded. Select the "Show Filtered Alarms" to invoke the filter to view only the alarms from the selected system. 4.5 Menu Items 4.5.1 Edit menu item "Find" "Find" finds an object only at the level at which the highlighted item resides. Using the keyboard, you can work around these restrictions by pressing the first letter of the name of the object you want to find. 4.5.2 Edit menu items "Cut," "Copy," "Paste" When a viewer is first selected or created, the CUT/COPY/PASTE menu items are all enabled. To enable the correct actions, select another viewer, then select the desired view. You cannot paste an object other than a Collection object from the clipboard into a viewer if another object in the viewer is already selected. You must deselect the object by clicking anywhere in the viewer and then select "Paste," or use "Drag and Drop." 4.5.3 The Main Menu Item Edit>Insert fails to show a connection item. You can still insert a connection object but must use the Map palette to do so. 4.5.4 Due to last minute changes by Microsoft in the Windows 95 and Windows 98 operating system regarding graphics, printing of a graph is not supported. However, you can copy the graph to the Clipboard and print it from a word processor or graphics program of your choice. To copy the graph, use Alt + Print Screen to copy the graph to the Clipboard. Then paste the bitmap into the application. 4.6 Selecting Background Bitmaps for Map Viewer The location shown for background bitmaps in the "Browse" dialog is "SWMgr". The actual location is \SWMgr\database\backgrnd. To select a background bitmap for the Map Viewer, reset the location to \SWMgr\database\backgrnd. 4.7 IP Address Report The IP Address Report in the Japanese version of ServerWORKS Manager is not fully internationalized. The header portion of the window is in English not in Japanese. 4.8 System Browser 4.8.1 When you graph network statistics, the first point is not displayed until one full sample interval has elapsed. If the sampling interval is long, the graphing tool may appear unresponsive. For example, if the default is 60 seconds, the first point is not displayed until 70 seconds have elapsed. 4.8.2 When you start the graphing tool, it waits for the first sample before displaying data. The delay can be longer than the sampling interval if the network is congested and the retry limit (2) and wait time for retries (10 seconds each) are exhausted. The tool starts the graph when it successfully receives the first sample. 4.8.3 When a system contains a primary and a backup (secondary) cooling fan, the System Browser Environment information for Cooling Systems reports the secondary fan as a BACKUP fan under all circumstances. The display status does not change if the secondary fan is currently running or if it was physically removed from the system. 4.8.5 Content no longer applies. 4.8.6 After you install MS Cluster GAM and SWCC agents, you may experience a problem running discovery or starting the System Browser. To work around this issue, increase the timeout and use the Internet Control Message Protocol (ICMP). You can perform these operations: on a selected object in a map or view. From the Actions menu, choose Properties. On the Polling page, increase the timeout and select SNMP as the polling protocol. ServerWORKS does not support SWCC agents on cluster objects. To associate a cluster object with SWCC agents, use the Actions-Properties-Application Launch command. Refer to Chapter 7 of the Installation and User Guide for details about associating objects with an application. 4.8.7 Some systems may report details in hex notation. For example, in systems with two or more processors, one of which is an empty slot, you may see a display in hex of the Prior System Processor, Details for the Selected Entry, and Revision. Firmware may appear as "unknown." This occurs when you switch between processors. Because the empty slot never had a real value, the value is displayed as ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff. 4.8.8 Foreign language versions do not support the System Groups FRU and Cluster tabs components of the System Browser. 4.8.9 Name resolution by Domain Name Server (DNS) and Windows Internet Name Server (WINS) produce different host names. DNS returns the full name, for example SERVER1.DOMAIN.COM, while WINS returns only SERVER1. 4.9 Alarm Configuration Tool 4.9.1 The threshold entered for a network interface cannot exceed 32767. 4.9.2 When you create a threshold alarm using the "Relative to Current Value" method of computation, the value is calculated correctly and converted to a new "Absolute" value. Do not be concerned that an alarm created with the "Relative to Current Value" method is then displayed as "Absolute" by the console during the modification process. The value will be set and triggered correctly relative to the current value. 4.9.3 In the Application Launch tab of the Action Setup dialog, the specified filename must include the full path name and extension. For example, "c:\programdirectory\filename.exe". If a directory d:\sample includes the files sample.exe, sample01.bmp, and sample02.bmp, and you set the application launch File Name to "d:\sample\sample.exe" in an action, the sample.exe runs but does not get the correct bitmaps. This is because the current working directory is not d:\sample. You can launch the sample.exe program directly as an alarm action by creating a batch file, such as sample.bat, with the following lines: d: cd \sample start sample.exe Set up the application launch File Name as "sample.bat" in the action; the sample.exe program will launch correctly. 4.9.4 The following SNMP traps from the DIGITAL Server Management MIB are automatically set for all objects of type Server.Digital after IP Discovery: svrMgtsvrThrHighExceptTrap svrMgtsvrThrMediumExceptTrap svrMgtsvrThrLowExceptTrap svrMgtsvrThrInformationExceptTrap These traps appear in the "SNMP Traps" list in the "Add New SNMP Trap Alarms" dialog. They do not appear in the "Currently Defined Alarms" list, which displays only alarms set by the user, but if you try to add an alarm for one of these traps, you receive the message, "Alarm already exists." 4.9.5 The default alarm state( in the Alarm Configuration setup) for component status - MEMORY is set to FAILED. With this setting you may not receive traps if you are getting parity errors only. We recommend you add the warning(move warning to the right window) state to the failed state. This will ensure you'll get traps even when the memory is only showing parity errors. During successful agent installation you will be asked if you want to restart the SNMP service and associated components. If the installation is in doubt, for instance by canceling at some stages, you will not be offered the restart choice so that you have the opportunity to repair the situation before starting SNMP. If your pager account requires a PIN number, the PIN number terminated by the "#" character must precede the numeric message in the Pager Message field. To display this field, go to the Add New Component Status Alarms dialog and click Actions. This field is displayed in the "New User" or "User Properties" dialog in the Action Directory Setup. 4.9.6 For the Windows NT Agent, if a server is running the ServerWORKS agent, Version 4.0 or greater, the server stores all alarms except for network interface inbound packets and network interface outbound packets, which are stored on the management console. When one user sets up component status or component threshold alarms on environmental sensors, the alarms can be viewed, deleted, modified, disabled, or enabled by another user on a different machine. If a user adds such an alarm and tries to modify it immediately, without performing any other action in the tool, it is possible for another user to delete the alarm from a different machine in the interim. When this occurs, the user who added the alarm receives the message, "Error getting item information from the host. Deleting the alarm." *4.9.7 You may find that on setting more than one alarm, the following message appears: "Operation timed out." In fact, the alarms may have been set. To see if the alarms were accepted, press F5 to refresh the alarm list and see the currently set alarms. 4.9.8 Content no longer applies. 4.9.9 You can set a maximum of 500 alarms on a server. If you set more than 500, the system may indicate that the alarms were set successfully, but in fact they are not. In addition, you may see a message "Apply unsuccessful." or "Operation timed out". This may also indicate you have reached the limit. You can use the MIB Browser to query MIB group svrmgr-svrAlarms for the server you are trying to set alarms on. If variable svrAlarmNextThrindex is equal to "-1", then you have reached the alarm limit for the server. 4.9.10 If a user sets an action that uses email and does not set up email in Microsoft Exchange, a runtime error appears with a message regarding the missing .dll. The problem is corrected by setting up Exchange and a user profile using the instructions in the manual. 4.9.11 You must install the correct modem software through the Control Panel Modems applet before you set up an action with paging or attempt to send a pager message. When you set up an action that includes paging, you make sure the maximum length for the message is supported by your pager. For example, if your pager supports only 80 characters, do not choose 240 characters as the maximum length. 4.9.12 Minimal Health agents for NetWare and SCO UNIX have not changed from ServerWORKS V3.3. Minimal health Windows NT in ServerWORKS 4.0 or greater offers additional functionality beyond that offered in V3.3. Enabling and disabling Minimal Health agents on NetWare systems is not supported. Minimal Health alarms can be deleted and then restored. If you delete a minimal health alarm and then want to restore the alarm, you must turn off minimal health first. Then turn on minimal health alarms. 4.9.13 Version 2.x agents are not supported on SCO or NetWare, therefore certain areas of the alarm configuration are not available(grayed out) if you are configuring alarms for servers using these operating systems. 4.9.14 To use ServerWORKS agents or Compaq Agents for DIGITAL Servers with NetWare, you must also use SNMP.NLM V3.04 or greater. If you use an earlier version of SNMP.NLM, you may experience abnormal termination of the agents. 4.9.15 On servers using NetWare, the HOSTS file is required by the Compaq HMMO utility (CPQHMMO.NLM) in order to support Web-based management. This file must be in the SYS:ETC sub-directory and requires the IP name and address of the server. 4.10 Companion and Third Party Applications 4.10.2 When installing any companion or third party application with ServerWORKS Manager, you must shut down all ServerWORKS Manager components before starting any installation or integration process. 4.10.3 StorageWorks Command Console (SWCC) *StorageWorks Command Console is not internationalized. *When using SWCC with any supported third party applications, storage objects manually selected to view with that application may not be seen until the OK dialog box is closed and the screen is refreshed. You may experience problems running StorageWorks Command Console Version 2.0 on the following platforms: Windows 95 B (The OEM Edition) Windows NT V4.0 Service Pack 3 You may not be able to start SWCC Command. Console 2.0 Local to configure a RAID box (BA-310 or BA-450). When you try to set up the Controller error '31037'. A patch to fix this problem is contained on the SWCC CD. On the SWCC CD 1. Locate the OLEPROC32.DLL. 2. Copy the file to \windows\system32. This replaces an existing file. 3. Reinstall SWCC>. 4.10.4 Mylex MIBs A new MIB for Mylex GAM Version 2.10 has been added to ServerWORKS Manager Version 4.0 or greater. Use the file MLXRAID.MIB with Mylex GAM Version 2.10 and later. Use the file MLXGAM.MIB with Mylex GAM Version 2.05 and earlier. 4.10.5 Mylex GAM Installation The Mylex GAM installation ends by integrating with ServerWORKS Manager Console. After you see the message "ServerWORKS integration successful," you may see a dialog box titled "OleMainThreadWndName: SETDLL.EXE - Application Error," followed by a message and An OK button. Press the "OK" button. Another dialog will appear. Press the "OK" button again. You can safely ignore these messages. 4.10.6 TPChanger Utility The TPChanger utility is an unsupported standalone executable stored in the working directory (the default is drive:\Program Files\Digital\SWMgr). TPChanger allows you to add, delete, and change information related to third- party applications. This third-party information is stored in the Access database of ServerWORKS Manager in the tables applicant, appl_type, and appl_gr, and in the swmgr.ini file. Using TPChanger, you can: --Add third-party applications after you have installed the ServerWORKS setup program --Correct information such as the location of the three files that are associated with any third-party application: the application executable, C:\xxx.exe, the third-party DLL, C:\xxx.dll, the toolbar bitmap for the application, C:\xxx.bmp -- Delete third-party applications that are no longer needed The TPChanger utility is currently provided only in English. See the TPChanger help for detailed instructions on using the utility. 4.10.7 If a host does not have a valid translatable IP address entry, ServerWORKS IP Discovery Wizard uses the address as the name. As a result, when you launch applications with the , an address is passed to the application. Examples of the results of passing an address as the follow. Example 1: Suppose that a Microsoft NT Cluster host has a primary adapter set up with 1.1.2.2 as the address, and the primary adapter is used as the heartbeat adapter. IP Discovery finds the adapter and uses it as the primary adapter for the machine. When IP Discovery tries to reverse-translate the name, it cannot do so because there is no name available from any of the translation mechanisms such as WINS or DNS. IP Discovery is forced to use the address as the name. Some applications can accept the address as the name, but others cannot. Another implication of using addresses as is that when Cluster heartbeat adapters are isolated and cannot be routed to, launched applications cannot connect to these hosts. DIGITAL recommends that you use valid network addresses that are accessible if you want to manage these systems. Example 2: If a host uses a dead-end address (an address that is not accessible to the management console machine because of routing or network mask restrictions) as the Cluster heartbeat adapter, you may experience application launch problems, because the management console cannot make a live connection to the managed host. IP Discovery is able to detect all adapters, regardless of routing, because the agents will expose adapter addresses across a single host boundary. This results in the launch of an application with a name or address that is unreachable because there is no IP route to use to reach it. The result: the application is launched with a host name or host address of a host adapter, which, although it exists, is disjointed from the reachable IP network and is hidden from the management console. Solutions: Manually modify the properties of the IP host and use another accessible host name that maps to an accessible adapter. For example: WOLFPCK2 has 2 physical adapters, with 3 IP addresses. The first is: Interface Name Interface Address WOLFPCK2 16.151.24.1 MSCLUSTER 16.151.24.2 1.1.2.2(Cluster Heartbeat adapter) 1.1.2.2 The simple fix is to make the following manual changes to the names in the ServerWORKS Manager Property of the host WOLFPCK2 Interface property page: WOLFPCK2 16.151.24.1 MSCLUSTER 16.151.24.2 WOLFPCK2 1.1.2.2 When you launch an application, it will always use the name WOLFPCK2. Use official DNS addresses for all adapters and make sure they are all routable (no dead end addresses). Order your primary and secondary adapters so that the heartbeat adapter is not the first in the list. Do this in the Network control panel. (The adapters get out of order because Windows NT setup chooses which to place first based upon the hardware configuration--IRQ, PCI bus opposition, and so on--rather than actual application usage. 4.11 NT Server Management 4.11.1 To display a hidden server, you must edit the registry of the hidden server. Look under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanman Server\Parameters for the value "hidden." Delete this entry and restart the server to make the server visible to ServerWORKS. 4.11.2 ServerWORKS Manager NT Management functions manage NT servers. LAN Manager server management is not officially supported. PATHWORKS V6.0 Server for OpenVMS does not adhere to the NT Server Management protocol correctly. It fails to UNICODE the share names and will fail not only for ServerWORKS Manager functions, but also some Windows NT utilities. 4.12 Tutorial The ServerWORKS Manager tutorial is designed for screen resolutions of 800 x 600 and higher. On some types of monitors, however, the tutorial may not display correctly. If you experience display problems with the tutorial such as overwritten or scrambled text, run the tutorial on a different monitor or at a higher resolution. Users of some monitors that are set for more than 256 colors may find that a navigation button skips the next display window. This is rare, but should you experience this, run the tutorial on a different monitor, or adjust the monitor to a higher resolution and reduce the number of colors to 256. 4.13 Poller 4.13.1 If you leave the Poller running continuously, you may encounter system problems as memory continues to be allocated but not released. Generally, you will receive an error message indicating that virtual memory is low. If the system freezes, try the following steps in the order shown until the system responds: 1. Stop and restart the Poller 2. Close ServerWORKS Manager and all related applets, and restart ServerWORKS 4.13.2 If you stop the Poller while you have an SNMP object selected, functions on the screen will appear to be active but will not respond. 4.13.3 It is strongly recommended that you run only one instance of ServerWORKS. Multiple instances of ServerWORKS consoles can be started if both the Explorer and Discovery windows are maximized before the second instance is running. If more than one instance is running, terminating any one of them terminates the Poller. When the Poller is stopped, no information is passed to the remaining console. You may also encounter this problem if a ViewerUpdateObject occurs on the selected SNMP object while the focus is set somewhere other than in the Hierarchical Viewer. If you experience this problem, stop and restart all ServerWORKS Manager components. 4.14 Database Utility The ServerWORKS Database Utility reports an incorrect version of the database. For ServerWORKS Manager Version 4.0 or greater, the correct database version is 3.2.1. The database utility accepts up to 99999 records in the alarm archive table. However, the more records you allow, the more memory and disk resources are required to store and display them. If you attempt to enter fewer than 500 alarms, you are prompted with a message to change the amount. Note that the message incorrectly states a maximum of 2500 alarms. As noted above, you can set up to 99999 as a maximum. 4.14 If you change the status colors in Options>Object Configuration and exit, you may not see the changes reflected until you restart ServerWORKS Manager. 5.0 ServerWORKS Manager SNMP Agent Issues 5.01 When setting up your Digital Server to except only SNMP Packets from specified nodes, it is important that you include the internal loopback address, 127.0.0.1. This will allow the Server Management agent (SvrMgt) and the CMADS agents to communicate with the Server System Agent (SvrSys). If the internal loopback address is not included in the list of nodes, the event log will contain messages that the agents could not communicate with the SvrSys agent. If the message persists, there may be a problem with SNMP or the SvrSys agent. *5.02 In order for CMADS agents to recognize your node, you must add your node address to the list of nodes in SNMP Properties. To do this, open the Control Panel->Network->Services. Choose the SNMP Service and click Properites. Choose the Security tab. Then select "Accept SNMP Packets from These Host." Click Add. Then enter your node IP address, click Add again. Click OK, them Close to exit from the Network applet. 5.1 Novell NetWare Management Agent 5.1.1 During the NetWare installation, if you have previously installed NWSNUT.NLM, you are asked whether you want to overwrite the previous installation. You can safely answer "No." On NetWare 3.12 installations, you should apply the latest CLIB.NLM patches to insure proper references for ServerWORKS Manager Agent use. 5.1.3 There is a known problem in NetWare Versions 4.1 and 3.12. In those versions, the priority of the IP service is set too low, forcing a wait of 2-5 seconds for an SNMP response. (One symptom of the problem is described in section 3.3.) You can obtain a NetWare patch for this problem from Novell's web site at: http://support.novell.com For the name and location of the latest patch, you can enter a search for tcpn0x in the Novell Knowledgebase search box at http://preview.provo.novell.com/search or contact Novell support for more information. 5.1.4 The size of the data for a diskette drive is always reported as 1.44 MB. The status of the drive is reported as not functional. 5.1.5 If you are connected to multiple NetWare servers and you want to install the Server Agent for Novell NetWare on a particular server, use the mouse to select that server from the "Install Components" dialog. If you use the keyboard arrow keys to scroll through the list of servers in order to select the server, all the boxes you pass over will become checked. You can uncheck them only by using the mouse. *5.1.7 In order to perform SNMP Set operations from the ServerWORKS Console on servers running NetWare, the NetWare SNMP ControlCommunity community string must be set to public on the target server. You can accomplish this by adding the following line to the autoexec.ncf configuration file: Load SNMP ControlCommunity=public Furthermore, it is essential that the Load command (above) precede any other Load command that imlicitly load SNMP. in the autoexec.ncf file. For example, the above Load command must precede the Load TCPIP command and the Load IPXRTRNM command. IF the order of the Load commands is reversed, the ControlCommunity will not be set to public and the SNMP Set operations will not work. The most obvious side effect of non-working SNMP Set operating is you cannot configure alarms using the ServerWORKS Alarm Configuration tool. 5.1.8 An attempt to enable the watchdog timer from the autoexec.ncf configuration file may result in an error. As a result of this error the watchdog timer is not enabled as expected. When this error occurs the error messages displayed on the system console are as follows: Loader cannot find public symbol: sw_setup_watchdog_timer for module SW_WDT.NLM Loader cannot find public symbol: sw_get_platform for module SW_WDT.NLM Load file referenced undefined public variable. Module SW_WDT.NLM NOT loaded This error is due to a timing problem between the loading of the Netware agents (DIGDRV.NLM)and the loading of SW_WDT.NLM. Therefore in order to enable the watchdog timer, the user must issue the LOAD SW_WDT.NLM command from the system console after the Netware OS is fully initialized. 5.2 Windows NT Management Agent 5.2.1 On Windows NT, the following variables from the HR MIB, RFC1514, may be set with SNMP-SET operations: - hrFSLastFullBackupDate - hrLastPartialBackupDate The following variables cannot be set, even though they are defined to be read/write in the MIB. Attempts to set these variables return the error NoSuchName: - hrSystemDate - hrSystemInitialLoadDevice - hrSystemInitialLoadParameters - hrStorageSize 5.2.2 The NT agent cannot obtain the status of a tape drive without affecting the device, so it reports the status of all tape drives as "unknown." 5.2.3 If the SNMP service is running, an error occurs when an attempt is made to delete a partition using the Disk Administrator. The SNMP service must be stopped before the partition is deleted. This is a limitation of Windows NT. Contact Microsoft support for more information. 5.2.4 When multiple network interface cards are configured, the standard Windows NT SNMP agent sometimes reports a false network interface descriptor (ifDescr in MIB II). Contact Microsoft support for more information. 5.2.5 The default maximum number of threshold alarms that can be set on a Windows NT server or a Novell server is 500. The default maximum number of threshold alarms for SCO is 250. 5.2.5 When the operating system has been running for over 49.7 days, the time stamp in the trap messages will be inaccurate due to overflow of the 32-bit millisecond result. 5.3 SCO UNIX Management Agent 5.3.1 In order to save disk space yet still get a valid value for CPU Utilization, the agent installation creates an additional sar file that is used to maintain statistics on a daily basis. The default sar file and settings are not affected. 5.3.2 When you install the SCO UNIX Management Agent, you may receive the following messages: kernel check failed, kernel = (null), code = Unknown Press return to continue You may safely continue the installation by pressing the Return key. *Cron may not be running - call your system administrator: No such device or address. *To avoid this error, install the agent from the multi user mode. 5.3.3 The device descriptor for diskette drives is dependent on the last device driver used. It is always reported as either 1.44 MB, 720 KB, or auto-sense regardless of the actual media in the drive. 5.3.4 The storage size of the diskette is reported only when a diskette is mounted as a UNIX file system. 5.3.5 When the counter for Unicast Packets Received (ifInUCastPkts in MIB-II) reaches the maximum limit of 4.2 billion, it starts to decrement. If this happens, the utilization value is only an approximation. Contact SCO support for more information. Setting up the agent incorrectly may cause the console to show an error when you attempt to set up an alarm. This usually occurs because of a failure to make the agent allow writes or to ensure that it is in the same community. 5.3.7 For a system running the Version 3.1 SCO UNIX 5.04 agent, no information is returned on disk partitions when you select the Storage icon and the Disk Partitions tab within the System Browser. Information on disk partitions is reported correctly for systems running the SCO UNIX 5.02 agent. In addition, the status of the SCSI disk drive is always reported as unknown. 5.3.8 When you try to set all alarms except processor and disk alarms on a SCO UNIX server, you may receive the message, "Error! Apply Unsuccessful." This is probably due to a permission problem. See the man page for snmpd and snmpd.comm. 5.4 Windows NT Agent on AlphaServer 800 and DIGITAL Server 3000 (Alpha processor-based only.) The Windows NT Agent uses the Remote Console Manager (RMC) to monitor the environment on the AlphaServer 800 and Alpha-based DIGITAL Server 3000 systems. The agent must send the correct escape sequence, which is currently the following default sequence (depending on the firmware version): rcm or rmc NOTE: If you experience a problem obtaining environment information, verify the RMC escape sequence. If the escape sequence has been changed, the agent cannot obtain information. Look in the event log. The error message "Comm1 Port failed" may indicate the password problem. *5.4.1 After installing NT 4.0 Service Pack 4, various Alpha-based systems have experienced problems with the updated SCSI drivers SYMC810.SYS and SYMC8XX.SYS. These problems have ranged from event log entries and device timeouts to system crashes. Contact Microsoft support for more information. While not directly related, the NT agents perfrom operations at startup that may exacerbate the bad behavior of these drivers. We suggest setting the SNMP service to manual startup to facilitate recovery before installing NT Service Pack 4.0 in case these problems are present on your Alpha system. If these problems are present, they may be alleviated by reverting to the version of the appropriate driver from NT 4.0 Service pack 3 or the NT 4.0 CD-ROM. See section 6.8 for additional information regarding system recovery. 5.5 Open VMS Agent For OpenVMS V6.2 or higher, you must obtain TCP/IP Services for OpenVMS V4.2 (or higher). During the configuration of TCP/IP Services, you must turn on SNMP. @ucx$config Configuration Options: Choose SNMP Choose SNMP Server ENABLE. EXIT out. 6.0 Platform-Specific Information 6.1 Prioris ZX 6000MP and DIGITAL Server 7000 Series 6.1.1 The speed for the 16MB 60 nanosecond SIMMs on a ZX 6000MP system may be reported as 70 nanoseconds. 6.1.2 It is important to adhere to the requirements for memory configuration as defined in the ZX 6000MP User Guide. If the requirements are not followed, SIMM information may be reported incorrectly. In addition, in the case of SIMMS, although only one SIMM may be faulty, two SIMMs may be shown as faulty because each SIMM is part of a pair. Refer to the ZX 6000MP User Guide for more information. 6.1.3 The server may return a degree sign in its OCP temperature display. This degree sign is misinterpreted as a series of hexadecimal characters separated by colons. 6.1.4 The SCO and NetWare Agents always report a "Warning" status on SIMM pairs and DIMMs that have single-bit ECC errors. Reboot the server as soon as possible to determine whether the problem persists. If it does, replace both SIMMs or the faulty DIMM. 6.2 Prioris HX 6000 and DIGITAL Server 5000 Series 6.2.1 Although only one SIMM may be faulty, a "Warning" status is always reported on SIMM pairs that have single-bit ECC errors. If you use DIMMs, a warning appears on the single DIMM. Reboot the server and run the diagnostics as soon as possible to determine whether the problem persists. If it does, replace the SIMMs or DIMM. 6.2.2 The server may return a degree sign in its OCP temperature display. This degree sign is misinterpreted as a series of hexadecimal characters separated by colons. 6.3 Prioris MX 6200/6266 and DIGITAL Server 3000 Series 6.3.1 Although only one SIMM may be faulty, a "Warning" status is always reported on SIMM pairs that have single-bit ECC errors. If you use DIMMs, a warning appears on the single DIMM. Reboot the server and run the diagnostics as soon as possible to determine whether the problem persists. If it does, replace the SIMMs or DIMM. 6.3.2 Although only one SIMM may be faulty, a "Warning" status is always reported on SIMM pairs that have single-bit ECC errors. If you use DIMMs, a warning appears on the single DIMM. Reboot the server and run the diagnostics as soon as possible to determine whether the problem persists. If it does, replace the SIMMs or DIMM. For this series, -12 volts is not present, but it is reported with a status of OK and a reading of zero volts. 6.4. Prioris XL 6000 Series 6.4.1 To allow the ServerWORKS Manager Agent to detect defective memory components, the XL 6000 Server must be configured with System Setup and the System Configuration Utility using the following settings: System Setup: Memory Error Detection - ECC SMM Feature - Enable Event Logging - Enable System SERR Detection - Enable System Memory Scrubbing - Enable System Configuration Utility: System Management Option Event Logging & ECC Memory - Enable PCI System Error Detection - Enable Note: The Use of PCI System Error Detection requires that all PCI cards be PCI 2.1 compliant so that parity errors, if they occur, do not cause the system to hang. DIMMs should be placed in consecutive order for the ECC error detection to report the proper slot number. If an ECC error is reported, reboot the server and run the diagnostics at your earliest convenience. 6.4.2 There is no support for setting the Asset Number in the FRU Data for the Prioris XL 6000 server. When you uninstall the Windows NT Agent on the Prioris XL 6000, a reboot is required to stop the Intel DISMIC and MEMDRV drivers. 6.5 If you are using Alarm Configuration on NT 4.0 to retrieve file system information about Storage Devices, SNMP may time out before the alarm is fully set. If it times out, you will see a message indicating that SNMP has timed out. You may also see a display of the alarms you have been setting. Verify that the alarm as shown is the alarm you were setting. In a time out, a previous alarm may appear if the new alarm could not be set. 6.6 Content no longer applies. 6.7 Alphaserver 800 or Digital Server 3000/ Alphaserver 1200/4100 or Digital Server 5000/7000 You may experience system problems, including crashes, on certain Alpha servers after installing Service Pack 3. Windows NT 4.0 Service Pack 3 installs an earlier revision of the system hardware abstraction layer (HAL). Digital recommends that you update the system HAL after installing Service Pack 3. To update the system HAL, locate the floppy diskette labeled Hardware Support Disk for Window NT 4.0 that you received with your server. Make sure that it has a part number of AK-R1SHG-CA or later; for example AK-R1SHH-CA. Note: If your floppy diskette is earlier than AK-R1SHG-CA , use a Web Browser and go to the following HTML link: http://www.windows.digital.com/support/sysoft.asp. Click on the appropriate system model to get the latest HAL and the latest installation instructions. For Alphaserver 800 or Digital Server 3000, follow these steps: 1. Rename Halpinna.dll to hal.dll. 2. Copy the renamed file manually to the \os\winnt40 directory. For Alphaserver 1200/4100 or Digital Server 5000/7000, follow these steps: 1. Rename Halrawmp.dll to hal.dll 2. Copy the renamed file manually to the \os\winnt40 directory. 6.7 If you have more than 2GB of system memory, you will need to obtain the IMAGECFG.EXE file from the Support directory of your Windows NT 4.0 Enterprise Edition, DISK 2. Run the file on SNMP.EXE in order to make the SNMP image large address aware. For example: imagecfg.exe -1 %SystemRoot%\System32\SNMP.EXE If you do not do this, the NT system call GlobalMemoryStatus() will return an incorrect value of 7FFFFFF hex for physical memory available instead of the actual correct value. 6.8 Digital Server 7000/AlphaServer 4000 systems with RRD46 CD-ROM drive using Windows NT are not compatible with the SYMC8XX drivers. If you have an RRD46 CD-ROM drive installed, and you install the ServerWORKS agents prior to ServerWORKS V4.0 or greater, the system may crash. To alleviate this condition: 1. When you reboot the system, hit the spacebar when prompted to use the "use last known good" boot feature to boot the system without starting the ServerWORKs agents. 2. In the %systemroot%\system32\drivers area, delete the file DECSSM.SYS. 3. In the control panel, set SNMP to startup Manual. 4. Reboot the system. 5. From the WEB or from a V4.0 ServerWORKs CD (or newer), install the Digital ServerWORKs agents which will install a patched DECSSM.SYS file 6. In the control panel, start the SNMP service to verify this was the problem. 7. If the system boots OK with the new DECSSM.SYS file, in the control panel, set SNMP startup to automatic. If the "last known good" boot feature fails, you can: 1. Move the boot drive to another NT system. 2. Mount the device on the other system. 3. Open %systemroot%\system32\drivers. 4. Delete DECSSM.SYS. 4.1 Return drive to original system and restart. 5. After the system has rebooted, In the Control Panel, set SNMP startup to Manual while you work on the problem. 6. Reboot the system. 7. From the WEB or a V4.0 ServerWORKs CD (or newer), install the Digital ServerWORKs agent which will install patched DECSSM.SYS file. 7.0 ClientWORKS Issues Always refer to the ClientWORKS readme for the most complete and most recent information on ClientWORKS. 7.1 Installing the SNMP Subagent If your existing ClientWORKS installation did not include the SNMP subagent but you now want to run the subagent, you must install the SNMP subagent separately. Remember that you must reboot after any ClientWORKS installation or deinstallation. 7.2 Related Hardware Notes When a hardware shutdown due to excessive temperature is required, allow enough time for the system to cool off before re-booting. Refer to your hardware documentation for recommended cooling intervals. This precaution prevents erroneous temperature thresholds from being displayed in the SMART Monitor utility. 7.3 Uninstalling ClientWORKS on DIGITAL Server 500 ClientWORKS may delete a registry key during an uninstall. This random problem is detected when you attempt to install ServerWORKS agents. You see the following message: "Hidden console of WowVdm, Virtual Device driver format in the registry is invalid, choose close to terminate the application." To correct the problem use the registry editor to add a key to: HKEY_LOCAL_MACHINE\ System\CurrentControlSet\Control\VirtualDeviceDrivers Then add a value to this key, named VDD of type REG_MULTI_SZ. 8.0 Technical Support Technical support information is available from the web site at: http://www.windows.digital.com/support/support.asp 9.0 Trademarks AlphaServer, DIGITAL, ServerWORKS, ManageWORKS, POLYCENTER, StorageWorks, ClientWORKS, and Prioris are trademarks of Digital Equipment Corporation. Compaq, Insight manager, and WBEM are trademarks of Compaq Computer Co. Hewlett-Packard is a registered trademark and OpenView is a trademark of Hewlett Packard Company. NetView/6000 AIX is a registered trademark of International Business Machines Corporation. Novell and NetWare are registered trademarks of Novell, Inc. Microsoft, Windows, Windows 95, and Windows 98 are registered trademarks and Windows NT is a trademark of Microsoft Corporation. SCO UNIX is a trademark of Santa Cruz Operations, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd.