Pocket ViewPoint User Guide Version 2.0 Part Number 545765-002 Abstract This manual describes the installation, configuration, and usage of Pocket ViewPoint Software Version H02 on a HP NonStop™ system. Supported Release Version Updates (RVU’s) This publication supports H06.10 and J06.03 all subsequent H & J-series RVUs until otherwise indicated by a replacement publication.
Table of Contents Part Number............................................................................................................................................. 1 Abstract.................................................................................................................................................... 1 Supported Release Version Updates (RVU’s) ...................................................................................... 1 Document History ................................
-4-1 Overview.............................................................................................................................................. 29 3-4-2 Description........................................................................................................................................... 29 3-5 Process Search............................................................................................................................................ 30 3-5-1 Overview................
Table of Figures Figure 1 Overview........................................................................................................................................................ 5 Figure 2 Functional Overview ...................................................................................................................................... 7 Figure 3 Main Screen.........................................................................................................................................
1 Introduction Pocket ViewPoint provides real-time, wireless monitoring of performance and events on NonStop servers. Using any smartphone or handheld device with a browser and internet capability, the product provides current information about your NonStop servers, anytime, anywhere. This document describes the installation, configuration and usage of Pocket ViewPoint. 1-1 Product Overview Figure 1 Overview Pocket ViewPoint is a smart phone based solution designed to monitor a NonStop system.
1-1-1 Architecture Figure 2 High-level Architecture Pocket ViewPoint is a smartphone browser-based application. It has several components that can be classified under the following groups: Web Server Engine Pocket ViewPoint Core Functions CPU, Process and Measure Metric Collectors Helper Objects and utilities Web Server Engine The Web Server is comprised of LISTAPP and PROCMAN. LISTAPP is the TCP/IP listener and PROCMAN is the process manager.
Helper Objects The CSVRAPP, CPROCAPP and PSVRAPP collect CPU and Process metrics and are needed to display CPU and process information. However additional objects are needed in Pocket ViewPoint. These are FINFO, FINFLIB and FDIST. FINFO and FINFLIB are needed to find out files that a process has opened and FDIST is the EMS event distributor that is used in Events. [Back to TOC] 1-1-2 Functional Overview Figure 2 Functional Overview The CSVRAPP collects CPU information.
1-1-3 User Interface Pocket ViewPoint is a smartphone browser based application. To access PVP, open the smartphone browser and enter your nonstop IP address and port number where PVP is installed. The main screen is basically the CPU busy screen for all available CPU’s. The image below shows this screen: Figure 3 Main Screen In general, there are 5 links on each page 1.CPU - It shows the busy percentage of all available CPUs 2.Process - It shows the list of busiest processes on the system. 3.
1-2 Install Process Overview 1-2-1 General There are three ways to install the product: Wizard Installation, Manual Installation and IPSETUP. a) Wizard Installation is the recommended install process; see section 2-2-2 for details. Wizard Installation will guide you through each step of the process allowing you to set parameters as you move from one step to the next. b) For manual installation please refer to section 2-2-3.
2 Installation and Configuration Installation of Pocket ViewPoint can be done either using the Wizard Installation, Manual Installation or IPSETUP. The Wizard Installation automates most of the install steps but requires Java Run Time on the PC where the installer is run. Configuration data is collected through user input and then the particular configuration files of PVP are updated and pushed to the NonStop server. This process greatly simplifies and streamlines the PVP install process.
2-1-2 Licensing Pocket ViewPoint requires a runtime license key. To request a license key, visit the following website www.hppocketviewpoint.com/License/PVPRegistration.asp The license will then be sent to the email address provided during the registration process. On receiving the email, follow the instructions in the email to activate Pocket ViewPoint. [Back to TOC] 2-2 Installation There are 3 different ways to install PVP namely: o PVPInstall.exe: The PC–based wizard installer for PVP.
* PVPEVTS * PSVRAPP * PVPBAMIM (Manual/IPSETUP installs only) * PVPCONF * PVPTMPAK * STOPPVP * STRTPVP Start/Stop Table 1 Obey Files – NonStop File Name Code RWEP Description STRTPVP 101 NUNU Obey script file to start Pocket ViewPoint. STOPPVP 101 NUNU Obey script file to stop Pocket ViewPoint.
Table 3 Object & Executable Files – NonStop File Name Code RWEP Description FINFLIB,FINFO 800 NNNN Privileged code files required to display list of files opened by a process.
2-2-1-4 Configuration Defaults/Initial Settings For PROCMAN object PROCMAN object is the process manager that creates and manages the listener process, Pocket ViewPoint and the related plug-in processes. The assigns and params that are to be passed to the PROCMAN object are specified in STRTPP file. ASSIGN PROGCONFn, [STRTPVP] Up to 20 programs can be configured to be managed by the process managers. The configuration file for each of the programs is specified using the PROGCONFn assign.
Common features in all installer pages: Once you have a compatible Java version, you may start the install. The wizard will ask for inputs to determine the configuration in several steps. Each step is represented by a page or wizard window. Most of the pages have the following buttons: Help - Display the particular help window. Help can also be activated by pressing the keyboard help key, which is typically F1.
Figure 4 Wizard Installation – Welcome Screen Clicking on ‘No’ brings up a dialog box asking the user the install Web ViewPoint first. The installer will then shut down. a. Clicking on ‘Yes’ will bring up the next screen. Here the user chooses whether to install PVP on one node ore multiple nodes: Figure 5 Wizard Installation – Single-node/Muti-node selection b.
Figure 6 Wizard Installation – Single-node configuration Alternately, if you are installing PVP on multiple nodes, you can choose the ‘Multi-node’ option. This screen will accept address of multiple nodes/residents. While a single set of WVP and PVP locations are to be entered at the bottom, you will get a chance to review these again before beginning the installation for each node separately: Figure 7 Wizard Installation – Multi-node configuration c.
Figure 8 Wizard Installation – Pocket ViewPoint Parameters d. Once the configuration is entered, the configuration entered in the previous screens is listed here for review. Clicking on ‘Finish’ will take you to the logon screen, Figure 9 Wizard Installation – Summary Screen e. Once the configuration is confirmed, the logon screen shows up. This screen prompts you to enter the userid and password to log on to the node/resident.
Figure 10 Wizard Installation – Logon Screen f. The Wizard prompts you for more information through the following screens. This includes a confirmation for the TCPIP program name (required to verify if the port specified is available): Figure 11 Wizard Installation –TCPIP Program Name g. Once the environment is verified, the transfer of files begins, including that of the configuration, binary and OBEY files.
Figure 12 Wizard Installation – File Transfer h. If the installation is successful, the following screen shows up. If an error occurs during any step of the process, the same screen shows with details of the error: Figure 13 Wizard Installation – Installation Status The last screen gives you a message to launch Pocket ViewPoint from your smartphone browser. i. Figure 14 Wizard Installation – Installation Status This completes the installation of Pocket ViewPoint.
During the obeying of files, a STRTPVP error may be generated. This occurs due to the command to stop the processes may not result in the process(es) being stopped. The recovery is to “Skip Command”. After a new install user might encounter an error ems message “CSVR:Could not open file WDSM001 Error 11”. CPROCAPP creates the WDSM001 file which CSVRAPP attempts to open.
c. Obey the Install file ‘INSTPVP’: i. Set the working volume as $system.zpvp5 (default) or as $vol.subvol (location where the PVP files have been transferred to in the NonStop). ii. Issue the command ‘OBEY INSTPVP’ 1. Actions taken: a. Sets the file codes of the objects and obey files b. Sets the file securities c. Opens the PVPCONF file in edit mode User input required to set the following: i. WVP-PORT number ii. PVP port number iii. License file location d.
c. If you plan to run the Guardian version of PVP, use DSM/SCM to accept and install the new software onto the system if you wish to do so. Otherwise, you can now run PVP directly from either the installation subvolume or product subvolume. 2-2-4-3 Considerations For a detailed explanation of how to use DSM/ SCM and receive new software in DSM/ SCM, please refer to the DSM/ SCM User’s Guide.
i) Pick a pair of names for your new resident and non-resident template files. Make sure files do not already exist with these names. For our example, let us assume that the new names will be: NewRes (for the new resident template) NewNRes (for the new non-resident template) j)Enter the following command to create the new template files. > INSTALL^TEMPLATES NewRes NewNRes CURRENT^TEMPLATES $SYSTEM.ZTEMPL NewRes and NewNRes are created in your current subvolume, which we had set to $SYSTEM.SYS00 in step h.
3 Using Pocket ViewPoint This section provides the operational details on the command and control of PVP, with screenshots on the various options. 3-1 Application Activation PVP consists of the collection module (for CPU, Process metrics collection) and User Interface module (to render HTML/Javascript). The Collector program’s (csvrapp and psvrapp) are processes that run 24*7 and collect CPU and process information. The UI program is launched when a user accesses PVP through the browser.
Username/Alias Enter the Username/Alias for which you wish to logon with. The keyboard control opens when this field is selected. Password Enter the password for the Username for which you wish to logon with. The keyboard control opens when this field is selected. CPU Monitor 3-2-1 Overview By default, Pocket ViewPoint will graph the busy percentage of all available CPUs.
3-2-2 Description The graph will automatically refresh at every 20 seconds (fixed). Indicates CPU Busy % is less than 80% - Normal Indicates CPU Busy % is greater than 80% and less than 90% - Warning Indicates CPU Busy % is greater than 90% - Critical To view Process information for any CPU, simply tap on the CPU of interest. Figure 17 Process summary Per CPU The information is displayed in a grid format, where information for each process is organized by row.
3-3 Process Busy List 3-3-1 Overview The Process page enables you to monitor the list of the busiest processes on your system. This information can be obtained and shown per individual CPU or for the system as a whole. The information is displayed in a grid, where information for each process is organized in a row. The list is sorted by CPU busy percentage in descending order. For a detailed view of a process, tap the process’ name.
3-4 Process Details 3-4-1 Overview This page shows you the specific details of the process selected. Figure 19 Process Detail Screen 3-4-2 Description Ancestor – Name of the Ancestor Process (process which created this process). Owner – Guardian Group and User name, under which the process is running. For remote processes, this is displayed as group id, user id. Program – The object file name of process, excluding volume and sub-volume names.
[Back to TOC] 3-5 Process Search 3-5-1 Overview Figure 20 Process Search Search Process/Program text box at the top right allows you to specify the following selection criteria and retrieve a list of matching processes. 3-5-2 Description Wildcards can be specified in the Process name or Program name. Process name – Search on the process name. Example: $ZTN0 - searches for $ZTN0 process. $ZTN* - searches for all processes with process name beginning with $ZTN.
3-6 Event Settings 3-6-1 Overview Here you can specify criteria to limit which events are displayed. Figure 21 Event Screen 3-6-2 Description Following parameters are available: Collector - Select the name of an EMS collector process from which Events should be displayed using the dropdown menu. By default, Pocket ViewPoint selects $0 from the Server to which you are connected. Show - The user can specify different filter criteria for the events to be displayed.
that is linked to the current Pocket ViewPoint. Also, you can select a maximum of 5 ownersubsystems, but the sum of length of the subsystems should be less than 26 characters) Figure 22 Event Screen – Owner-Subsystem Start From - You can specify a From Date-Time (YYYY-MM-DD HH:MM:SS) or not specify anything. If no start information is provided, then displayed EMS messages will start from the current date-time and go backwards in time (descending order).
3-7 Event Viewer 3-7-1 Overview Event Viewer shows the last 10 (fixed) of EMS messages based on default criteria on the setting page.Figure 23 Event Viewer 3-7-2 Description Based on these settings, you may see messages from the EMS Collector on an available node of an Expand network. Clicking on the previous arrow shows the previous 10 events from the 1st time stamp on the current page. And clicking on Next arrow shows the next 10 events (if available) from the last timestamp on the current page.
Figure 24 Event Details Screen To see Token Dump information for any of the events, you can tap on Owner.SSID.Event# for any event.
4 Appendix 4-1-1 Software Support Support for Event Analyzer Plug-in is available through HP's 24-hour Global Mission Critical Support Centers (GMCSC) throughout the world. In the U.S. please call 1-800-255-5010. International numbers please see: http://h71014.www7.hp.com/gcscphone.html 4-1-2 Error & Advisory Messages (EMS Events) This section lists all EMS Events that can be generated specifically from the Pocket ViewPoint application conditions and processing. Pocket ViewPoint EMS SSID: TANDEM.
b) Occurs on the “__ns_start_backup” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. It could occur due to various reasons, e.g. invalid process handle (Error 2). Effect: The process which generates this EMS message or its backup will not be started. Depending on the cause functionality may be affected. Recovery: For Primary Process, the error type and sub type can be located in the "Guardian Procedure Calls" reference manual.
Cause: The process could not be opened. The EMS Event indicates the error value returned by the Guardian Procedure call FILE_OPEN_. Effect: Any future I/O Operations with the Process will fail. Recovery: Recovery will depend on the specific Guardian error returned. Make sure that the file exists before being opened. If the max numbers of File Opens have been reached, then close all open file handles and then try again.
PVIEWPT 143 : Error opening File : Relating to function or activity: The File could not be opened to perform I/O Operation. Cause: The file could not be opened. The EMS Event indicates the error value returned by the Guardian Procedure call FILE_OPEN_. Effect: Any future I/O Operations on the file will fail. Recovery: Make sure that the file exists before being opened.
PVIEWPT 325 : siGetFileOpens:Child process not responding: Cause: The FINFO process spawned by the POCKETVP does not respond to the parent process with the list of files . Effect: The list of files opened for a process will not be displayed. Recovery: n/a PVIEWPT 361 Process in use Cause: Listener process name mentioned in the STRTWVP file is already in use. (PARAM LISTENER-PROCESS) . Effect: Pocket ViewPoint will not start.
5.2 AWAITIOX error when reading from $RECEIVE 5.3 Unable to get process information for Process Manager process (PROCMAN) 5.4 Unable to open new Primary Process Manager process (PROCMAN) 6 Unable to open $RECEIVE after work done Effect: The Process dies. Recovery: Make sure that the process gets the correct parameters from the Process Manager and restart Pocket ViewPoint.