OSM Migration Guide Abstract This guide introduces the HP NonStop™ Open System Management (OSM) Interface. It is intended for anyone who uses OSM to monitor or service an HP NonStop S-series server. It describes OSM requirements; how to migrate from Compaq TSM to OSM (including coexistence and fallback issues); and how to install, configure, and start OSM server components and processes. Product Version N.A. Supported Release Version Updates (RVUs) This publication supports G06.
Document History Part Number Product Version Published 527273-005 N.A April 2004 527273-007 N.A. September 2004 527273-008 N.A.
OSM Migration Guide Index Figures What’s New in This Manual v Manual Information v New and Changed Information Tables v About This Guide vii Who Should Use This Guide vii What’s in This Guide vii Where to Get More Information viii Notation Conventions viii 1. Introduction to OSM Primary Goals 1-1 Major Benefits 1-1 OSM Client Interfaces 1-2 Migration Checklist 1-2 2.
. OSM Client-Based Components Contents Starting OSM Persistent Processes 3-4 Other OSM Server Processes 3-5 $SYSTEM.SYSnn.RALPRVD and $SYSTEM.SYSnn.RALPRVNP $SYSTEM.SYSnn.EVNTPRVD 3-5 $SYSTEM.SYSnn.IAPRVD 3-5 $SYSTEM.SYSnn.SECPRVD 3-6 $SYSTEM.SYSnn.TACLPRVD 3-6 $SYSTEM.SYSnn.APPRVD 3-6 $SYSTEM.SYSnn.OEVPRVD 3-6 $SYSTEM.SYSnn.SPDIST2 3-6 $SYSTEM.SYSnn.FDIST 3-6 OSM Server Files 3-6 4. OSM Client-Based Components Tools Formerly Bundled With TSM 4-1 5.
B. Memory Guidelines for OSM Contents B. Memory Guidelines for OSM C. Configuring Remote Services Configure Modem for Dial-In and Dial-Out C-1 Create Windows User Name C-2 Configure Carbon Copy 5.7 or Microsoft NetMeeting for Dial-In C-3 Configure Carbon Copy 5.
Tables Contents Tables Table 2-1. Table 3-1. Table 5-1. Table 5-2.
What’s New in This Manual Manual Information OSM Migration Guide Abstract This guide introduces the HP NonStop™ Open System Management (OSM) Interface. It is intended for anyone who uses OSM to monitor or service an HP NonStop S-series server. It describes OSM requirements; how to migrate from Compaq TSM to OSM (including coexistence and fallback issues); and how to install, configure, and start OSM server components and processes. Product Version N.A.
New and Changed Information What’s New in This Manual OSM Migration Guide —527273-008 vi
About This Guide This guide introduces and describes how to prepare for and get started with the HP NonStop Open System Management (OSM) Interface. OSM replaces TSM as the system management tool of choice for NonStop S-series servers. Who Should Use This Guide This guide is intended for anyone who uses OSM to monitor or service a NonStop S-series server.
Where to Get More Information About This Guide Where to Get More Information NonStop S-Series Hardware Installation and FastPath Guide – Describes how to install and start a NonStop S-series server for the first time. It includes information about installing server hardware, cabling system enclosures, installing and starting system consoles, installing external system devices, starting the server, and configuring the server after startup.
General Syntax Notation About This Guide General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name italic computer type.
General Syntax Notation About This Guide … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [ , new-value ]… [ - ] {0|1|2|3|4|5|6|7|8|9}… An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char…" Punctuation.
1 Introduction to OSM The HP NonStop Open System Management (OSM) Interface replaces TSM as the system management tool of choice for NonStop S-series servers.
OSM Client Interfaces Introduction to OSM OSM Client Interfaces OSM contains these system management applications and tools. • • • • • OSM Service Connection – A Java-based application, with client and server delivered on a site update tape (SUT) and accessed from a system console or qualified PC through a Microsoft Internet Explorer browser session. OSM Guided Procedures – Provide the same functionality as TSM guided procedures.
2 Preparing for OSM This section describes how to prepare for migration to OSM software, including: • • • • System Console Requirements on page 2-1 Server Software Requirements on page 2-2 Upgrading the Server Software on page 2-4 Preparing the Hardware and LAN Environment on page 2-4 System Console Requirements To run OSM client software, your system console must meet the following minimum requirements: • • • Microsoft Windows 2000 Professional or Microsoft Windows XP Professional operating system.
Server Software Requirements Preparing for OSM Server Software Requirements OSM requires the G06.08 RVU or later. All supported RVUs prior to G06.21 require one or more Prerequisite SPRs for OSM. For G06.21, there are no prerequisites, but you need the OSM Server SPR. Starting with G06.22, no additional SPRs are required (unless you want new functionality released in a later RVU). However, there is one Recommended SPR for Improved OSM Performance, available at G06.15 and later.
OSM Server SPR Preparing for OSM Section 4, OSM Client-Based Components, describes the OSM client-based SPRs. Migrating to the G06.25 RVU (or later) When migrating to G06.25 or later, DSM/SCM automatically identifies the eight OSM SPRs that have been dropped from the SUT because they are replaced by T0682. When presented with the following dialog box, click Continue without selecting to retain any of the obsoleted OSM SPRs.
Recommended SPR for Improved OSM Performance Preparing for OSM Recommended SPR for Improved OSM Performance During periods of peak processor usage, OSM server performance is significantly better if the NSK CRE/RTL (T1269) product is installed on the system rather than the Native CRE/RTL (T8431) product. This is because of more efficient heap management in T1269. T1269 is available on G06.15 and later SUTs.
3 OSM Server-Based Components This section provides information about OSM server-based components: • • • • • OSM Server-Based SPR on page 3-1 Optional OSM Configuration on page 3-2 Starting OSM Persistent Processes on page 3-4 Other OSM Server Processes on page 3-5 OSM Server Files on page 3-6 OSM Server-Based SPR Starting with G06.25, the OSM server-based components are combined into a single SPR, T0682AAA. It replaces the following OSM SPRs (which were available on G06.22 through G06.24 SUTs).
Optional OSM Configuration OSM Server-Based Components Optional OSM Configuration It is not necessary to create a configuration file to use OSM with the default settings. However, if you want to alter any default settings or take advantage of any of the following features, you must create and use an OSMCONF file: • • • • Configuring additional TCP/IP stacks for high-speed Starting OSM Persistent Processes through ServerNet adapter ports.
Enabling System Inventory Files OSM Server-Based Components and $ZTCP1 TCP/IP stacks. (This is the same configuration used when configuring TSM through a dedicated service LAN.) To increase OSM performance, you can choose to connect to the server through dedicated ports on an E4SA, FESA, or GESA CRU.
Starting OSM Persistent Processes OSM Server-Based Components Starting OSM Persistent Processes Once you have installed all required server-based OSM and requisite SPRs from the SUT (using DSM/SCM) and completed any desired configuration changes (see Optional OSM Configuration on page 3-2), use this TACL command to invoke the OSM Configuration script and start the OSM persistent processes: RUN $SYSTEM.ZOSM.
Other OSM Server Processes OSM Server-Based Components Other OSM Server Processes This section describes the other OSM server processes that are started by the OSM persistent processes described in the preceding section. For each of these processes, the process name is dynamically assigned. $SYSTEM.SYSnn.RALPRVD and $SYSTEM.SYSnn.RALPRVNP Launched by $ZCMOM, these Resource Access Layer Providers are responsible for: • • • Interacting with SP and subsystems such as Storage, SLSA, etc.
$SYSTEM.SYSnn.SECPRVD OSM Server-Based Components $SYSTEM.SYSnn.SECPRVD Launched by: $ZCMOM, the Security Providers are responsible for user authentication. The maximum number that can be running simultaneously is eight. $SYSTEM.SYSnn.TACLPRVD Launched by $ZCMOM, the TACL Providers are responsible for performing embedded TACL actions (Reload Processor). The maximum number that can run simultaneously is eight. $SYSTEM.SYSnn.
OSM Server Files OSM Server-Based Components $SYSTEM.ZSERVICE The following OSM server files reside in $SYSTEM.ZSERVICE: Note. Many of these files have different names from their TSM equivalents (as noted below), to avoid conflicts with those equivalent files generated by TSM. File Name Description OSMINI Default configuration file delivered with OSM on the SUT.
OSM Server Files OSM Server-Based Components OSM Migration Guide —527273-008 3 -8
4 OSM Client-Based Components Starting with G06.22, OSM client-based components are installed on new system console shipments and also delivered by an OSM installer on the HP NonStop System Console (NSC) Installer CD. The NSC CD also delivers all other client software required for managing and servicing NonStop S-series servers. Installation instructions are included in the NonStop System Console Installer Guide. Starting with G06.
Tools Formerly Bundled With TSM OSM Client-Based Components For service providers, the CSSI Intranet site is: http://cssi.cac.cpqcorp.net/. Also, the Hardware Service and Maintenance CD contains a snapshot of the intranet version of the CSSI Web along with the HSM libraries.
5 Getting Started With OSM Applications This section introduces the OSM client interfaces, providing the following information for each application: • • • • Overview of basic purpose and functionality Description of enhancements and functional differences between OSM and TSM (for server-side differences, see Section 3, OSM Server-Based Components) Procedure for how to launch and log on to OSM applications and related tools Reference to documentation for how to use the applications The OSM client interfac
User Interface Getting Started With OSM Applications Figure 5-1. Management Window for the OSM Service Connection IE Menu Bar OSM Menu Bar (view pane) (details pane) (tree pane) (overview pane) VST001.vsd OSM-Specific Interface Differences This list describes some of the changes between the visual display in the OSM Service Connection Management window and that of the TSM Service Application: • • • • There is no longer a tab to switch between System and Cluster views in the tree pane.
Getting Started With OSM Applications • • • Functional Differences Group icons are smaller so that you can view more groups without scrolling. More consistent naming conventions, in the format object_type object_name (group.module.slot (if applicable)). For example, a disk named $K001-P is identified as: Disk $K001-P (1.1.15). Resource attributes are arranged in logical subgroups under the resource object. Some attribute names have changed.
Getting Started With OSM Applications • • • • • Functional Differences System Status Window on page 5-8 Alarm and Attribute Suppression on page 5-9 OSM Rediscover Actions on page 5-11 Snapshot Functionality on page 5-11 Miscellaneous Changes on page 5-14 Multi-Resource Actions Dialog Box The most significant enhancement, in terms of new and changed functionality, is the Multi-Resource Actions dialog box. It is available from the Display menu.
Getting Started With OSM Applications Functional Differences upper to the lower resource list. Click Perform Action to initiate the Power Off action. The Progress bar and the circle to the left of each disk resource indicate the status of the action on each resource (whether the action has completed on that resource, whether it succeeded or failed). Click Action Summary to get more information about actions that fail.
Getting Started With OSM Applications Functional Differences Using the Multi-Resource Actions Dialog Box for Firmware Updates The Multi-Resource Actions dialog box replaces these TSM menu options and buttons: • • • • SP Actions Single SP Firmware Update Firmware Update SWAN Fast Firmware Update To perform a firmware update on just one resource, you can also right-click the object, select Actions, and perform the Firmware Update action from the Actions dialog box.
Getting Started With OSM Applications Functional Differences Using the Multi-Resource Actions Dialog Box for a Resource Summary The Multi-Resource Actions dialog box allows you to view a summary of any or all resources of the same type (replacing and expanding upon the TSM Disk Summary functionality). Figure 5-5.
Getting Started With OSM Applications Functional Differences with Alarm and Attribute Suppression. Alarms not suppressed are represented by a Service State value other than OK (Attention Required or Service Required). Figure 5-6. Problem Summary Dialog Box VST007.vsd System Status Window If you are monitoring several systems simultaneously, OSM offers a more convenient tracking method of systems than resizing all of your Management windows. Figure 5-7.
Functional Differences Getting Started With OSM Applications Propagation of Subcomponent Problems As with TSM, alarms and problem attributes on resources in the OSM Service Connection are propagated up to parent objects. However, instead of displaying Subcomponent State attributes (on the Attributes tab) for the parent object, the OSM Tree pane displays a special icon over parent objects to indicate problems with subcomponents (as Figure 5-8 illustrates). Figure 5-8.
Getting Started With OSM Applications Functional Differences resource’s icon changes to show a yellow check mark. No container objects, up to and including the system icon, now show degraded conditions. Figure 5-9. Before Applying Attribute Suppression Figure 5-10. After Applying Attribute Suppression Suppressing Problem Attributes To suppress a problem attribute, select the attribute (in either the Attributes tab or the Attributes dialog box), right-click, and select Suppress. (See Figure 5-9.
Getting Started With OSM Applications Functional Differences you bring the tape drive up and then it returns to the Hard Down state, that value is no longer suppressed. Permanent suppression continues to suppress a value of Hard Down for this tape drive until you unsuppress it. Neither temporary nor permanent suppression is tied to your current OSM Service Connection session. They remain suppressed in future client sessions until unsuppressed.
Getting Started With OSM Applications Functional Differences Saving Snapshots Snapshots are created and saved manually from within the OSM Service Connection. Select Save Snapshot from the OSM Tools menu. The suggested (default) name includes the system name and the date and time that the snapshot was created. The default location is ZSUPPORT>OSM>snapshots on your PC’s local disk.
Getting Started With OSM Applications Functional Differences 3. In the Load Snapshot File dialog box, navigate to the snapshot file you want to view and click Open. The snapshot looks like a regular OSM Service Connection session, except that “(SNAPSHOT)” appears in the title bar and the system icon in the view pane (\STAR3 in this example) is gray instead of yellow or green, which is used to indicate status in active OSM Service Connection sessions.
Getting Started With OSM Applications Establishing an OSM Service Connection Session Limitations: • • You cannot use an existing OSM browser window to load a new snapshot or to start a new OSM Service Connection session. You cannot be logged on to a server and have a snapshot loaded at the same time in the same window. However, you can be logged on to a server and view a snapshot by using two separate browser windows.
Getting Started With OSM Applications Establishing an OSM Service Connection Session Figure 5-11. OSM Service Connection Home Page Method 2: Without Client Installation or Bookmarks 1. Launch a new* Internet Explorer browser window. 2. In the Internet Explorer Address dialog box, enter a system URL. Either: http://system_IP_address:9990 (example: http://155.155.155.155:9990) http://system_host_name:9990 (http://himaxb.cac.cpqcorp.net:9990) 3. Press Enter. 4. Proceed to Logging On.
Getting Started With OSM Applications Establishing an OSM Service Connection Session Logging On 1. The first time you try to establish an OSM Service Connection session, you are prompted to “download Java Runtime Environment.” Select Open and install it according to instructions (accepting typical and default options). After the installation wizard finishes, restart the PC. 2.
Getting Started With OSM Applications Establishing an OSM Service Connection Session 4. In the Log On dialog box, enter a valid user name and password and click Log on. Starting with G06.24, an OSM Service Connection session is launched in a secondary Internet Explorer browser window to eliminate the standard IE toolbar buttons which took up screen space and were largely incompatible with OSM.
Getting Started With OSM Applications OSM Low-Level Link OSM Low-Level Link The OSM Low-Level Link (LLL) enables you to communicate with a server even when the NonStop Kernel operating system is not running. Also, some actions that are performed on a running server, such as starting the system or priming a processor for reload, require you to use the OSM Low-Level Link.
Getting Started With OSM Applications OSM Event Viewer OSM Event Viewer Like the OSM Service Connection, the OSM Event Viewer is a browser-based application that is installed and resides on your server and is accessed through an Internet Explorer browser session on your system console. The OSM Event Viewer allows you to retrieve, view, and save events from any EMS formatted log files ($0, $ZLOG, or an alternate collector) for rapid assessment of system problems.
Getting Started With OSM Applications Functional Differences Figure 5-13.
Getting Started With OSM Applications Launching and Logging On Functionality differences in the OSM Event Viewer • • • • • Text Search can be done during event filtering, not just after retrieval. Built-in filters for pass or fail criteria (no need to write compiled filter) Instead of using a configuration edit file to override event query defaults, simply save the current query as an Internet Explorer Favorite.
Getting Started With OSM Applications OSM Notification Director OSM Notification Director The OSM Notification Director (ND) is a component of the OSM client software package that receives information about the servers for which it is configured in the form of incident reports. You can display these incident reports within the Notification Director and forward (or have them automatically dialed out) to remote service providers.
Getting Started With OSM Applications Manually Starting and Stopping Manually Starting and Stopping If you do not configure OSM Notification Director to run as a Windows service, you must manually open it every time you start your system console. To start or stop the Notification Director manually (for the current Windows session only): Start>Programs>HP OSM>OSM Notification Director>Start (or Stop) Note. Starting or stopping manually does not change the status of the ND as a persistent Windows service.
OSM Guided Procedures Getting Started With OSM Applications Table 5-1. OSM Guided Procedures TSM Guided Procedure Guided Procedure Within OSM Service Connection Replace PMF, IOMF, SNDA, SEB, and MSEB OSM guided procedures are launched by performing a Replace action on the CRU to be replaced. Configure ServerNet Node OSM guided procedure is launched by Add Node to ServerNet Cluster action on the System object. Replace Switch Component OSM Guided procedure launched by Replace action.
6 TSM Coexistence and Fallback You can have both OSM and TSM software installed and, in most cases, running on your NonStop S-series servers and system consoles. This section describes OSM and TSM coexistence issues and how to fall back to using only TSM if necessary. Coexistence Issues Coexistence issues include some TSM functionality that is disabled by OSM, specific situations in which OSM is required or strongly recommended, and other situations where you can use OSM or TSM, but not both.
Fallback Issues TSM Coexistence and Fallback Fallback Issues This section describes fallback steps to be performed if you need to revert to TSM instead of OSM for managing your NonStop S-series servers. Note. TSM does not support certain functionality in the G06.22 RVU and later. 1. If you uninstalled TSM components (not necessary for migrating to OSM), reinstall those TSM components.
A Migrating Your Registry Settings The procedures in this section are designed to save you time and effort in the event that you are migrating to new system consoles, but they are not required to use OSM software. The more systems you manage, the more time you can save by migrating and leveraging your TSM and OSM registry settings. The procedures assume that your systems will be running OSM server software instead of or in addition to TSM software.
Leveraging Your OSM Registry Settings Migrating Your Registry Settings 9. Enter regedit and click OK. 10. In the Registry Editor, navigate to HKEY_LOCAL_MACHINE>SOFTWARE>Hewlett Packard>OSM>Configuration and select CurrSystem 11. From the Edit menu, select Delete (and close the Registry Editor dialog box). 12. When you launch the OSM Low-Level Link or OSM Notification Director, you should see the same system names that were listed in your TSM system list.
B Memory Guidelines for OSM For the minimum hardware and software requirements for OSM, see Section 2, Preparing for OSM. This section provides guidelines to help you determine how much additional PC memory (beyond the minimum of 256 MB) you might need to run OSM, as determined by your needs. Because the OSM Service Connection uses Java-based routines for faster, more accurate display of system status, OSM requires more PC memory than TSM.
Memory Guidelines for OSM Example 2: A customer has two 16-processor production nodes and a 4-processor development node. They are not clustered together. The customer runs one session per system on each of two consoles. There are 18 enclosures and no cluster switches.
C Configuring Remote Services This section describes how to configure the following remote services on your Windows 2000 or Windows XP-based NonStop system console: • • Dial-in, using Carbon Copy 5.7 or Microsoft NetMeeting Dial-out, using the OSM Notification Director The steps include: • • • • • • • Configure Modem for Dial-In and Dial-Out on page C-1. Create Windows User Name on page C-2. Configure Carbon Copy 5.7 or Microsoft NetMeeting for Dial-In on page C-3.
Create Windows User Name Configuring Remote Services 5. Click Start>Settings>Control Panel and double-click Phone and Modem Options. 6. Select the Modems tab. If the correct modem type, Microcom Deskporte 28.8P Plug & Play, MultiTech MT2834BA (or BL), MultiTech MT5634ZBA, or MultiTech ZBA-USB-V90 (USB modem) is already configured correctly, skip to Create Windows User Name; otherwise, continue with step 7. 7. The modem entry must match the physical modem vendor and model numbers.
Configure Carbon Copy 5.7 or Microsoft NetMeeting for Dial-In Configuring Remote Services 5. Right-click the Users Directory. 6. Select the New User action. 7. Enter Username = "GCSC," Full Name = "Global Customer Support Center," Password and Confirm Password = "austin." 8. Make sure that only Password Never Expires is selected. You might have to deselect User must change password at next logon. 9. Click Create, Click Close. 10. Close the Computer Management and Administrative Tools windows.
Configure Carbon Copy 5.7 Configuring Remote Services 13. From the Options menu, select Communications. 14. Select the Wait For Call tab. 15. From the list of Connection Types, select TCP/IP Network. If it is not available in the list, reboot the system console and then perform this Configure Carbon Copy 5.7 procedure again. Make sure that no other Connection Types entries are selected on this screen.
Configure Microsoft NetMeeting Configuring Remote Services Configure Microsoft NetMeeting 1. Click Start>Programs>Accessories>Communications>NetMeeting. 2. If the NetMeeting application window starts, skip to step 9. If the NetMeeting installation wizard starts, continue with step 3. 3. Click Next. 4. Fill in the First Name, Last Name, and E-mail address fields with “GCSC.” Click Next. 5. Deselect Logon on to directory server when NetMeeting starts. 6.
Configure OSM Notification Director (ND) for Each Host Server Configuring Remote Services Configure OSM Notification Director (ND) for Each Host Server 1. At the Primary system console, start the OSM Notification Director. 2. From the Systems menu, select Configure\systemname for the host server to be configured. 3. Enter a valid NSK Super Group User Name and Password (for example, Super.Tandem, compaq. This must be a valid username and password that is valid on the \systemname selected.
Configuring Remote Services Configure OSM Notification Director (ND) for Dial-In and Dial-Out Configure OSM Notification Director (ND) for Dial-In and Dial-Out If you are configuring the OSM Notification Director for Dial-in/dial-out and this system console was already set up for using the TSM ND, skip steps 1-10 and proceed to step 11.
Configure OSM Notification Director (ND) for Dial-In and Dial-Out Configuring Remote Services Enter the current date and time. If you have two or more system consoles, the Service Access Name must be unique. To make them unique ensure the 2 digit minute value is different between the system consoles. 4. Click OK. Exit the Registry Editor. 5. In the OSM Notification Director, click the File menu and select Dial-in/Dial-out Configuration. 6.
Configure OSM Notification Director (ND) for Dial-In and Dial-Out Configuring Remote Services At the GCSC, the successful Registration Dial-out can be viewed by the GCSC analyst on the Compaq Remote Gateway (CRG) at: AMER/EMEA: http://txncrg01.txn.cpqcorp.net:8943/gateway/main.asp or http://16.74.7.105:8943/gateway/main.asp. AP: http://gcscrgap1.aum.cpqcorp.net:8943/gateway/main.asp or http://16.176.196.24:8943/gateway/main.asp.
Configure Incoming Connections Configuring Remote Services 10. To view the SAN (system consoles) registered data as stored in the CRG, Click the Customers link. Find the console you are looking for. There may be more than one entry for each customer name, but the SAN names will be unique. Click the Customer Name link for the SAN-related details. You can sort the display by clicking the column titles. 11. Don't forget to update the OSCDB database with the correct information.
If No Incoming Connections Icon Configuring Remote Services 11. Enter the From and To IP addresses. By default the From IP address should be 192.231.36.77 and the To IP address should be 192.231.36.78. These match the default Subnet of the system console and the SPs as was shipped by HP.
Reconfigure System Standby and Hibernate Mode Configuring Remote Services 13. Click OK, then click Next, click Finish. The TR/DTR light on the modem should be lit. 14. Reboot the system console. 15. If any problems, Check: • • • Control Panel>Phone and Modem Options: Ensure that the correct modem is still configured.
D Troubleshooting This section lists problems that can occur under particular conditions or configurations and describes how to avoid or recover from the problems. OSM Service Connection Problems “Malicious Alerts” message during OSM client installation If your PC has script blocking enabled in recent version of Norton Anti-Virus, you will get a “Malicious Alerts” message during OSM client installation. To recover: Disable script blocking in Norton Anti-Virus during installation.
OSM Low-Level Link Problems Troubleshooting “Error 500,” “Page cannot be displayed,” or “Initial Analysis in Progress” (after providing user name and password) If one of the panes in the OSM Management window displays an “Error 500” or “Page cannot be displayed” message, or if the Server Status on the view pane title bar reports “Initial Analysis in Progress,” you have attempted to establish a service connection before OSM server software has fully discovered the system.
OSM Event Viewer Problems Troubleshooting OSM Event Viewer Problems Cannot establish Event Viewer session with a system $ZOEV may not be running on the server. Start it by using: scf start process $zzkrn.#osm-oev Saved events are not the ones you intended to save When you save a page of events (returned by the Event Viewer) after using the Next button, the events that are saved may not be the ones you intended (because of an Internet Explorer preference setting).
OSM Notification Director Problems Troubleshooting OSM Migration Guide —527273-008 D- 4
E Uninstalling TSM This section contains optional instructions for removing TSM software from your system console. You need not remove TSM software to install and use OSM. (See Section 6, TSM Coexistence and Fallback.) In fact, during the migration from TSM to OSM, you can save time by leveraging your existing TSM system list. (Launching and Logging On on page 5-18 describes how OSM automatically creates OSM bookmarks from your TSM system list.
Uninstalling TSM OSM Migration Guide —527273-008 E- 2
Index A E ADDTOSCF command 3-4 alarms, suppression 5-11 attributes, suppression 5-10 event viewer see also OSM Event Viewer F B browser-based applications OSM Event Viewer 4-1 OSM Service Connection 4-1 C falling back to TSM 6-2 firmware updates, using the Multi-Resource Actions dialog box 5-6 G goals and benefits of OSM 1-1 Carbon Copy C-3 client interfaces 1-2 client-based OSM components 4-1 OSM Console Tools 4-1 OSM Low-Level Link 4-1 OSM Notification Director 4-1 coexistence, OSM and TSM 6-1 co
N Index N Netmeeting C-5 nondedicated operations LAN configuring stacks for 3-2 planning for 2-4 NonStop Open System Management (OSM), introduction 1-1 notification director see also OSM Notification Director use only one, OSM or TSM 6-1 O OSM Event Viewer comparison to TSM Event Viewer 5-20 launching and logging on 5-21 overview 5-19 troubleshooting D-3 OSM guided procedures comparison to TSM 5-24 overview, list 5-23 OSM Low-Level Link launching and logging on 5-18 overview 5-18 troubleshooting D-2 OSM
S Index requirements prerequisite SPRs 2-2 server software 2-2 system console 2-1 system console memory B-1 S ServerNet cluster OSM required for layered topology 6-1 use OSM on all nodes 6-1 server-based OSM components 3-1 server-based OSM SPR 2-2, 3-1 service connection see also OSM Service Connection snapshots limitations 5-14 loading 5-12 saving 5-12 SP Tool 4-1, 5-18 starting OSM persistent processes 3-4 suppressing problem attributes 5-10 suppression of alarms 5-11 System Status window 5-8 T2751, r
W Index OSM Migration Guide —527273-008 Index -4
