Installation and Administrator's Guide REFERENCE 86 A2 95ER 03 NOVASCALE NovaScale Master 5.
NOVASCALE NovaScale Master 5.2-x Server Add-ons Installation and Administrator's Guide Software February 2008 BULL CEDOC 357 AVENUE PATTON B.P.
The following copyright notice protects this book under Copyright laws which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works. Copyright © Bull SAS 2008 Printed in France Suggestions and criticisms concerning the form, content, and presentation of this book are invited. A form is provided at the end of this book for this purpose.
Table of Contents Table of Contents ..................................................................................................... v List of Figures .........................................................................................................vii List of Tables.......................................................................................................... viii Preface..................................................................................................................
2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.4 Prerequisites ........................................................................................................... 10 Installing Free Management Server Add-ons from the CD-ROM..................................... 10 Installing Payable Management Server Add-ons Packages ........................................... 12 Uninstalling NovaScale Master Server Add-on Components .........................................
List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 1-1. 2-1. 2-2. 2-3. 2-4. 3-1. 3-2. 3-3. 3-4. 3-5. 3-6. 3-7. 3-8. 3-9. 3-10. 3-11. 3-12. 3-13. 3-14. 3-15. 3-16. 3-17. 3-18. 3-19. 3-20. 3-21. 3-22. 3-23. 3-24. 3-25. 3-26.
Figure Figure Figure Figure Figure Figure Figure Figure 3-42. 3-43. 3-44. 3-45. 3-46. 3-47. 3-48. 3-49. JOnAS Architecture ....................................................................................................69 JOnAS configuration ..................................................................................................70 JOnAS domains .........................................................................................................70 JOnAS properties.........................
Preface Scope and Audience of this Manual NovaScale Master Server Add-ons are Bull products, which provide extension to NovaScale Master for managing Bull Intel platforms specific devices or tools. Administration environments can include different platforms from the NovaScale Universal or Intensive Series, Express 5800 Series or EvolutiveLine Blade Series servers. In order to monitor a specific item, NovaScale Master Server Add-ons configuration must be customized.
Highlighting The following highlighting conventions are used in this book: Bold Identifies commands, keywords, files, structures, directories and other items whose names are predefined by the system. Also identifies graphical objects such as buttons, labels and icons that the user selects. Italics Identifies chapters, sections, paragraphs and book names to which the reader must refer for details.
Chapter 1. NovaScale Master Server Add-ons Concepts 1.1 1.1.1 NovaScale Master Overview NovaScale Master monitoring ensures the following tasks: • Monitoring NovaScale machines: NovaScale Master checks if these hosts are accessible, using the ping command from the System Manager. The machines to be monitored are either explicitly specified by the administrator or selected by a discovery mechanism.
Management Console Provides third-party management tools for the end-user station running the NovaScale Master console WEB GUI. Management Agent Provides instrumentation and administration tools for monitored servers. Management Agent must be installed on each server to monitor. Figure 1-1. NovaScale Master Architecture Note: NovaScale Master for Windows and Linux are distributed on the same CD-ROM. 1.1.2 Monitoring A Service (or monitoring service) defines how specific host elements are monitored.
1.1.3 Event Reception NovaScale Master can receive SNMP traps from any SNMP agent. SNMP traps enable an agent to notify the NovaScale Master Server of significant events via an unsolicited SNMP message. SNMP Traps must be defined in a MIB (Management Information Base). 1.1.4 Hardware Manager A Hardware Manager manages hardware for one or a set of servers. 1.1.5 Storage Manager A Storage Manager manages storage for one or a set of servers or/and bays. 1.1.
1.2 NovaScale Master Server Add-ons NovaScale Master Server Add-ons deliver optional management packages to extend NovaScale Master Server. A NovaScale Master Server Add-on provides functional links (monitoring, GUI call, reporting ...) between a NovaScale Master Server and a third-party management tool. Some free Server Add-ons are distributed on the NovaScale Master Add-ons CD-ROM. Note: There is a difference between the Server Add-on and the third-party management tool.
Chapter 2. NovaScale Master Server Add-ons Installation and Configuration 2.1 General Installation Requirements Before installing NovaScale Master, check that the environment meets the software and hardware requirements described below. 2.1.1 Supported Operating Systems NovaScale Master Server Add-ons operate on Linux and Windows operating systems. The principal Requirements are the NovaScale Master Server pre-installation and its own requirements. See NovaScale Master Installation Guide for details. 2.
2.1.5 Operational Requirements Server Add-ons NSMasterGAMTT Target Tools Linux GAM version 6.02.31 or higher. Windows GAM version 6.02-32 or higher. Important: Contact web site to download the above versions. If not on-line, contact the Bull support team. Note: For IA32 machines the following previous versions are supported: Linux GAM version 6.02-21 or higher Windows GAM version 6.02-22 or higher. NSMasterLSICIM LSI CIM provider version 3.06 or higher. Important: Contact
2.2 2.2.1 Installing NovaScale Master Server Add-ons for Windows Prerequisites To install NovaScale Master Server Add-ons on Windows: 2.2.2 • The user must be a member of an Administrators group. The default administrator login is Administrator. • The installation program requires the Internet Explorer WEB browser. Other browsers, such as Netscape or Mozilla, cannot be used to install NovaScale Master on Windows. • Management Server Add-ons are to be installed on the server dedicated to management.
Figure 2-1. Windows Installation - NovaScale Master Welcome Page 4. Click Install Now to open the Install page, which allows the selection of the required NovaScale Master component: − Management Server Add-ons and provides the following information: − What to install? − What to do now? Figure 2-2. Windows Installation - NovaScale Master Install Page 8 NovaScale Master 5.
5. Select Management Server Add-ons, then Windows 32 bits or Windows 64 bits operating system according to server type. 6. Click the selected Add-ons Install Now link to install the Server Add-ons package. The wizard prompts for a destination folder. The default value can be changed if required. At the end of the installation process, Management Server Add-ons components are automatically operational. 2.2.3 Installing Payable Management Server Add-ons Packages These are auto-extractible packages.
2.3 2.3.1 Installing NovaScale Master Server Add-ons for Linux Prerequisites To install NovaScale Master Server Add-ons on Linux: • The user must be logged as root. • The installation program requires the Mozilla WEB browser (Version >1.4.3 or Firefox): If Mozilla is not installed, launch another WEB browser and open file: /product /index.html It is advised to uninstall the previous version of Mozilla before installing a new version.
Figure 2-3. Linux Installation - NovaScale Master Welcome Page 5. Click Install Now to open the Install page, which allows the selection of the required NovaScale Master component: − Management Server Add-ons and provides the following information: − What to install? − What to do now? Figure 2-4. Linux Installation - Selecting NovaScale Master Components 6. Select Install Management Server Add-ons. Chapter 2.
7. Select the Linux 32 bits or Linux 64 bits operating system according to server type. 8. Install the selected NovaScale Master Server Add-ons packages as described below. cd /product/mgtpack/NSMaster/linux rpm –Uhv NSMaster-5.1-x.noarch.rpm 2.3.3 Installing Payable Management Server Add-ons Packages These are RPM packages. To install a package just launch it from any logical device: rpm -Uhv NSMaster-5.2-x.noarch.rpm 2.3.4 2.3.
2.4 Monitoring Configuration Configuring NovaScale Master Monitoring consists mainly in specifying the parameters required for monitoring tasks. Most configuration tasks are performed via the NovaScale Master Configuration GUI (Graphical User Interface). NovaScale Master Server Add-ons extend the Monitoring configuration default rules the Administrator can customize. New monitoring categories and services are provided. 2.4.
• cloning services, to define new monitored elements. One or more services are created, with different names from the original names. All properties can be edited except the check command. For instance, to monitor a specific logical drive on a Windows system, clone the C service and modify the check command parameters, • customizing categories, to restrict monitoring a whole category to a list of hosts, • creating a category, to assign a set of cloned services to this category.
Chapter 3. NovaScale Master Server Add-ons Description NovaScale Master Server Add-ons provides different functional items for each Management Package. 3.1 3.1.1 Internal Storage (Free) NSMasterGAMTT for LSI MegaRAID 320-2x Management GAMTT (or GAM) is the LSI tool used to survey, configure and control RAID provided by LSI MegaRAID Ultra320 SCSI cards. See http://www.lsilogic.com/products/megaraid/index.html for more information or to download the GAMTT install package.
NSMaster Server machine Console machine NSMaster Server LSI-Logic NS Master Server GAM client SNMP gamtt trap mngr add-on SNMP service (host OS) GAM server GAM SNMP agent LSI-Logic GAM driver LSI-Logic Target machine HBA(megaRAID0) Figure 3-1. GAM Monitoring Components 3.1.1.1 Default Categories & Services (independent of OS type) Targeted OS Any Table 3-1.
Notes: • This category is based on the GAMTT management product from LSI. This tool and especially its SNMP interface is a requirement for the following GAMTTraid monitoring services. Check that this tool works on the targeted OS, if you want to monitor with it in NOVASCALE Master. • The previous ” MegaRAID” category (NOVASCALE Master release 4.0) is based on PowerConsolePlus management product from LSI. These two management products are functionally redundant but not compatible.
3.1.2 NSMasterLSICIM for LSI 22320 Chip Management LSI CIM is the LSI tool used to survey, configure and control RAID provided by LSI MegaRAID 22320 SCSI cards. See http://www.lsilogic.com/products/megaraid/index.html for more information or to download the LSI CIM install package. Note: This tool runs on NovaScale machines under Linux or Windows. The corresponding NovaScale Master Add-on creates monitoring links between NovaScale Master and the LSI CIM provider.
3.1.2.1 Default Categories & Services (independent of OS type) Targeted OS Any Model Any Category LsiCIM Service RAIDStatus check_LSICIM CTRLstatus Table 3-2. Check command check_LSICIM_ctrl LSI CIM monitoring services Note: This category is based on the LSI CIM management product. This tool is a requirement for the following LsiCIM monitoring services. Check that this tool works on the targeted OS, if you want to monitor with it in NovaScale Master. LsiCIM Category 3.1.2.
Input Name of the controller to check Note: The name of the controller must be protected with a quote if the name contains blank characters. Output See the output of the check_LSICIM shell command in Appendix A. Default syntax for ”LsiCIM.CTRLstatus” is inactive: check_LSICIM!’ctrlname’ 20 NovaScale Master 5.
3.1.3 NSMasterMegaRaidSAS (LSI MegaRAID SAS (IR) Management) The corresponding NovaScale Master Add-on creates monitoring links between NovaScale Master and the LSI MegaRAID SAS(IR) SNMP agent. It supports the adapters from MegaRAID SAS/SATA Value and Feature Line and the LSI SAS ICs 1064, 1068 and 1078.
3.1.3.1 Default Categories & Services (independent of OS type) Targeted OS Any Any Table 3-3. Model Any Any Category MegaRaidSAS MegaRaidSAS_IR Service Check command Status check_MegaRAIDSAS Alerts No check (SNMP trap receiver) Status check_MegaRAIDSAS_IR Alerts No check (SNMP trap receiver) MegaRaid SAS (IR) monitoring services Note: This category is based on the MegaRAID SAS (IR) SNMP agent. This SNMP interface is a requirement for the following MegaRaidSAS(-IR) monitoring services. 3.
3.2 3.2.1 External Storage Server Add-ons NSMasterStoreWayFDA (StoreWay FDA Management) The corresponding NovaScale Master Add-on creates monitoring links between NovaScale Master and the StoreWay FDA SNMP agent and WEB GUI. NSMaster Server machine iSM Client (Windows) machine NSMaster Server NEC NS Master Server iSM client StoreWay SNMP FDA trap mngr software add-on hardware iSM Server SNMP agent StoreWay FDA NEC Target StoreWay FDA subsystem iSM Server machine Figure 3-4.
3.2.1.2 StoreWayFDA Category Status For StoreWay FDA hosts managed via its SNMP agent. This service checks the StoreWay FDA status reported by the SNMP agent. Alerts For StoreWay FDA hosts. When an alert is sent from the StoreWay FDA SNMP agent, it is processed by the NovaScale Master Server. Note: The Armg2_4.mib mib is integrated in the NovaScale Master application.
3.3 3.3.1 Virtualization Server Add-ons Overview The NovaScale Master Server Virtualization Add-ons deliver an optional management package to manage virtual machines. A virtualization Add-on can provide: 3.3.1.1 • Supervision features to detect abnormalities and notify them to defined entities, • Administration features to perform actions on elements. Definitions Virtualization Add-ons use specific topology elements: 3.3.1.
Level 0: Root Level 1: Virtual Manager Level 2: Virtual Platform Level 3: natif OS Level 3: VM host Figure 3-5. Virtual Managers view Under the root node, the first node is the Virtual Manager that administrates the Virtual Platform. The Virtual Platform contains the native host and the VM hosts. When you select a node, information about the elements are displayed in the Application pane. Figure 3-6. Virtual Manager information pane 3.3.2 3.3.2.
The VMwareESX Add-on retrieves VM and native OS monitoring information via the VMware Service Console SNMP interface and allows the Web Virtual Interface to be launched from the NovaScale Master Console. The following figure shows the link between each component: NSMaster Server machine Console machine NSMaster Server NSMaster Console VI Web URL NovaScale Master server VMwareESX Add-on SNMP trap manager SNMP Agent Mgmt Web Server Service Console VMware ESX server ESX machine Figure 3-7.
3.3.2.2.1 ESX Virtual Platform To configure an ESX Virtual Platform, click the VMware ESX link in the Virtualization part of the Topology domain. The list of all configured platforms appears, as in the following example: Figure 3-8. ESX Virtual Platforms page It is possible: • To create a new ESX Virtual Platform using the New button • To edit or delete a resource using the Edit link • To edit a virtual machine using the link.
• SNMP Configuration: used to configure SNMP interface data. • Virtualization Platform: used to describe the Vmware ESX platform virtual machine. ESX Server Host Properties name ESX host short name. This name is displayed in the NovaScale Master Console views. Click Select to choose a defined host from the NSMaster host list. model Host model (see the NovaScale Master Administrator’s Guide for values). network name ESX host network name (hostname or IP address).
Figure 3-10. ESX Virtual Machines pane Virtual Machines Re-Discovery Re-Discovery is required to check that the current NSMaster configuration still matches the VMware ESX configuration in order to: • Add virtual machine not yet registered in the VMware ESX Virtualization Platform • Remove virtual machine no more defined in the VMware ESX configuration.
Figure 3-11. Host Topology modification confirmation If you do not agree, click the NO button to return to the platform edition page, otherwise click the YES button to create the virtual platform. Related ESX Virtualization platform Objects When an ESX Virtualization platform is defined, related objects are automatically generated to configure the specific Supervision linked to this type of NovaScale server. The following table describes the objects generated during the creation of the platform. Type 3.3.
Add a virtual machine to a platform Adding a virtual machine is performed by checking the corresponding line in Virtual Machines part of the platform edition form and setting the host characteristics in NSMaster Configuration table zone (by filling in the corresponding fields or by selecting an already defined host). Note: When you edit a Virtualization platform, only the Virtual Machines defined as part of the NovaScale Master platform are displayed.
Monitoring Services Monitoring services defined for the native OS are associated with the VMwareESX category.
Figure 3-12. VMware category properties pane Note: During ESX Platform definition, all services are defined and activated for the ESX server and for each VM. To deactivate the monitoring of one service, set status (Monitoring attributes part) to inactive. 3.3.2.3 Nagios Check Commands check_esx_server The configurable NovaScale Master service check command syntax is: check_esx_server!!%!% See the check_esx3 command in Appendix A for parameters details.
check_esx_snmp The configurable NovaScale Master service check command syntax is: check_esx_snmp! See the check_esx3 command in Appendix A for parameters details. check_esx_mem The configurable NovaScale Master service check command syntax is: check_esx_mem!!! See the check_esx3 command in Appendix A for parameters details.
Indicators Applied to the VM Host Indicator Corresponding Service _vmCPU vmCPU _vmMemory vmMemory Note: During ESX Platform definition, all indicators are defined and activated for the ESX server and for each VM. To deactivate the reporting of one indicator, set to inactive. Beware, if you deactivate the corresponding service, the indicator will no longer be collected. 3.3.2.
VMwareESX Reporting From the platform or host elements, you can access reporting information by selecting Indicators Trends from the Reporting menu. From the host element, you can display indicators related to this host as shown in the following figure: Figure 3-14. VMwareESX reporting information From the platform element, you can display indicators related to all platform elements. Chapter 3.
3.3.3 3.3.3.1 NSMasterHyperNova for ”HyperNova” Management Overview The HyperNova server is a virtualization layer that abstracts processor, memory, storage and networking resources into multiple virtual machines. The HyperNova Add-on provides functional links to manage the virtual machines hosted by the HyperNova server, by requesting the administration tool, HyperNova Master (HN Master). The following figure shows the link between each component: Figure 3-15. HyperNova Add-on components 3.3.3.
3.3.3.2.1 HyperNova Virtualization Platform To configure a HyperNova Virtualization Platform, click the HyperNova link in the Virtualization part of the Topology domain. The list of all configured platforms appears, as in the following example: Figure 3-16. HyperNova Virtualization Platforms page It is possible: • To create a new HyperNova Virtualization Platform using the New button • To edit or delete a resource using the Edit link • To edit a virtual host using the link.
Virtualization Server Properties name Server host short name. This name is displayed in the NovaScale Master Console views. Click Select to choose a defined host from the NSMaster host list. model Host model (see the NovaScale Master Administrator’s Guide for values). network name Server network name (hostname or IP address). HTTP Configuration SSL mode To enable or disable SSL mode for HTTP Default value: no Note: SSL option in not available on Windows platform.
Notes: • When you select an already defined host, you cannot change its network name and OS. But, The Select contains a Default Option that correspond to the VM name, that can be edited. • If the VM name contains space(s), they are replaced by underscore(s) in the host label.
Note: How to Add, Delete or Modify Virtual Machine is detailed in 3.3.3.2.2 Virtual Machine Edition, on page 43. After edition: • Click the OK button to validate your edition • Or click Cancel to return to Virtual Platforms pages without changes • Or click Delete to remove the Virtual Platform and maintain the hosts corresponding to the VMs and the Virtualization server • Or click DeleteAll to remove the Virtual Platform and the hosts corresponding to the VMs and the Virtualization server.
host HNMaster Host corresponding to the virtualization layer and hosting the HNMaster application, as defined in the Virtualization Server configuration part. hostgroup hostgroup representing the physical platform, named . manager Virtualization manager representing the management interface, named < platformName>_HNMaster categories and services The HyperNova category and related services are instantiated for the HNMaster host.
Modify a virtual machine defined in a platform To modify the name of the NSMaster host corresponding to a virtual machine, enter the new name in the corresponding field or choose it in the list of already defined hosts in NovaScale Master by clicking the Select button. To modify other characteristics as netName or OS, Host edition form must be used. Note: To get the Host edition form corresponding to the virtual machine, click the Hostname link displayed in the global platforms page.
Figure 3-21. Virtual Machine Properties pane Note: During HyperNova Platform definition, all services are defined and activated for the server and for each VM. To deactivate the monitoring of one service, set status (Monitoring attributes part) to inactive. 3.3.3.2.4 Domain0 Supervision The monitoring functions to control the resources of the domain0 are not automatically setup at the platform definition. To enable them, you have to activate the corresponding categories and services. Chapter 3.
HyperNova Add-on delivers the following monitoring definitions: Category Dom0SystemLoad Service CPU(*) Memory(*) Processes(*) Users Swap(*) Zombies Dom0FileSystems All(*) /usr Dom0LinuxServices syslogd(*) Dom0Syslog AuthentFailures RootAccess(*) indicates services that are automatically activated when the corresponding category is instantiated. (*) Examples To activate the de Dom0SystemLoad related services, do as follows: 1. Click the Categories/Services link in the Supervision tab. 2.
3. Click the manage categories link and choose the Add from an unused category template (user or predefined) option to display the categories available for the corresponding hosts. Figure 3-23. Available categories for domain0 Host 4. Select the Dom0SystemLoad category and click Add from the selected category. 5. The edition form for the corresponding category is displayed with all fields filled in. Click the Ok button. 6.
Note: The Zombies and Users services are not present. To activate them, you have to explicitly associate them to the hosts (see below). To activate the Users service, do as follows: 1. Click the manage services link of the Dom0SystemLoad category and choose the option Add from a service template (user or predefined) to display the available services. Figure 3-25. Available services for Dom0SystemLoad category 48 2. Select the Users service and click Add from the selected services.
Figure 3-26. Users service for domain0 Host To get detailed information about the Categories and Services configuration, refer to the NovaScale Master Administrator's Guide. 3.3.3.3 Nagios Check Commands check_hn_server_status The configurable NovaScale Master service check command syntax is: check_hn_server_status See the check_NSM_hypernova_xen command in Appendix A for parameters details.
The following table lists the commands used by the services. Category.Service Dom0SystemLoad.CPU check_cpuload Dom0SystemLoad.Memory check_memory Dom0SystemLoad.Processes check_procs Dom0SystemLoad.Users Dom0SystemLoad.Zombies Dom0SystemLoad.Swap Dom0FileSystems.All Dom0FileSystems./usr Dom0LinuxServices.syslogd Dom0Syslog.AuthentFailures Dom0Syslog.RootAccess 3.3.3.4 Command check_procs check_swap check_disks.pl check_procs check_log2.
Figure 3-27. Virtual Platform monitoring Chapter 3.
3.3.4 3.3.4.1 NSMasterViosLPAR ”ViosLPAR” Management Overview Dynamic logical partitioning (LPAR) is a system architecture delivered on IBM systems that allows the division of a single server into several completely independent virtual servers or logical partitions.
3.3.4.2.1 VIOS Virtualization Platform To configure a VIOS Virtualization Platform, click the IBM VIOS link in the Virtualization part of the Topology domain. The list of all configured platforms appears, as in the following example: Figure 3-29. IBM VIOS Virtualization Platforms page It is possible: • To create a new VIOS Virtualization Platform using the New button • To edit or delete a resource using the Edit link • To edit a virtual host using the link.
Besides the characteristics (name and description) of the main object, the properties of a VIOS virtual platform are divided into three parts: • Virtual I/O Server: used to define the physical machine and the native OS. • SSH authentication: used to define properties related to SSH authentication. • Logical partitions: used to describe the VIOS Virtualization platform logical partitions. Virtual I/O Server Properties name Server host short name.
• the center part displays Partitions properties as defined on the VIO server. • the right part allows you to edit the main properties (name, network name and OS) of the corresponding NSMaster host. The host can be edited only if the corresponding partition is selected. You can select an already defined host by clicking the select button or you can create a host by completing the corresponding fields. Figure 3-31.
Figure 3-32. Logical Partitions display after Discovery failure Logical Partitions Re-Discovery Re-Discovery is required to check that the current NSMaster configuration still matches the Vios configuration in order to: • add logical partition not yet registered in the VIOS Virtualization platform • remove logical partitions no more defined in the Vios configuration.
After edition: • Click the OK button to validate your edition • Or click Cancel to return to Virtual Platforms pages without changes • Or click Delete to remove the Virtual Platform and maintain the hosts corresponding to the VMs and the Virtualization server • Or click DeleteAll to remove the Virtual Platform and the hosts corresponding to the VMs and the Virtualization server.
categories and services The VIOS category and related services are instantiated for the Vios host. The VirtualMachine category and related services are instantiated for each LPAR host. performance indicators An indicator representing the percentage of processing pool utilization is defined for the Vios host. An indicator representing the percentage of CPU usage is defined for each LPAR host. 3.3.4.2.
Note: To get the Host edition form corresponding to the logical partition, click the Hostname link displayed in the global platforms page. Delete all logical partitions and corresponding hosts. To delete all logical partitions and corresponding hosts, use the DeleteAll button of the VIOS Virtualization platform Edition form. Beware: the Vios server and the platform will be also deleted from the NovaScale Master configuration. 3.3.4.2.
Figure 3-35. VIOS.UsedPool Service Properties pane Note: During VIOS Platform definition, all services are defined and activated for the server and for each LPAR. To deactivate the monitoring of one service, edit it and set its status (Monitoring attributes part) to inactive. Reporting indicators A performance indicator is defined for the Vios host to describe the utilization of the processing pool. This indicator is identified as _UsedPool.
Figure 3-36. VIOS indicators Note: The collections of all these indicators is activated during the VIOS Platform definition. To deactivate some of them, edit the indicator and set its status to inactive. 3.3.4.3 Nagios Check Commands check_vios _status The configurable NovaScale Master service check command syntax is: check_vios_status!! See the check_NSM_vios_ivm command in Appendix A for parameters details.
check_vios_lpar_used_cpu!!! !!>!! ! See the check_NSM_ vios_ivm command in Appendix A for parameters details. 3.3.4.4 NovaScale Master Console 3.3.4.4.1 Operation From the Virtual Manager or from any element of the Virtual Platform, you can launch the IVM Web Interface by selecting the following cascading menu: Operation → Virtualization → IVM Figure 3-37.
From the platform element, you can display monitoring information related to all elements by selecting Monitoring menus. For instance, you can view all services of the hosts in the platform, as shown in the following figure: Figure 3-38. VIOS monitoring 3.3.4.4.3 VIOS Reporting From the Vios host , you can display reporting indicators to get evolution of the processing pool utilization.
Figure 3-39. VIOS reporting 64 NovaScale Master 5.
3.4 3.4.1 Bull Products Server Add-ons NSMasterDD4A for Bull “Dynamic Domains For Applications” Management The Dynamic Domains For Applications (DDFA) software is a tool that can be used on the Linux operating system for simulating the partitioning of a multi-CPU machine at application level. Dynamic Domains for Applications can be used with standard Linux distributions and can be managed using the Webmin standard administration tool.
NovaScale Master Server Add-ons provides the default Bull product categories by Management Package described below. 3.4.1.1 Default Categories & Services Proposed for Linux Hosts Targeted OS Linux Model Any Category DynamicDomains Service All Check command check_dd4a Default Table 3-5. 3.4.1.2 DDF4 categories and services DynamicDomains Category All Service For NovaScale and Express5800 Linux hosts with the Dynamic Domains management tool.
3.4.2 NSMasterBVS for Bull Video Services Management Bull Video Services (BVS) software is a tool that can be used with standard Linux distributions and Windows and can be managed using Web server. See the Bull Video Services User’s Guide for more information. You can install BVS from the Bull Video Services CD (ref 36673900-xxx). Note: BVS 4.1 runs on Linux and Windows machines and uses an integrated Web server for management.
3.4.2.1 3.4.2.2 BullVideoServices Category Streaming For NovaScale hosts acting as Bull video server. This service checks the status of the video streaming service. Recording For NovaScale hosts acting as Bull video server. This service checks the status of the video recording service. Datagrams For NovaScale hosts acting as Bull video server. This service checks the status of the video datagram errors.
3.4.3 3.4.3.1 NSMasterJOnAS for JOnAS Management JOnAS Overview JOnAS is a pure Java, open source, application server. Its high modularity allows to it to be used as: • A J2EE server, for deploying and running EAR applications (i.e. applications composed of both web and ejb components) • An EJB container, for deploying and running EJB components (e.g.
JOnAS administrators are responsible for the configuration and administration of JOnAS servers running within a management domain. 3.4.3.3 JOnAS Monitoring Information NovaScale Master retrieves domain and server monitoring information from JOnAS (administrator or master) server via the WEB services. Note: WEB services are operational only if the “conf/server.xml” file on JOnAS (administrator or master) server is correctly configured as: The localhost value must be replaced by the DNS host name. 3.4.3.
Figure 3-45.
other servers 3.4.3.5 the selected servers will be monitored by NovaScale Master. JOnAS Category and Service The definition of a domain creates or updates a JOnAS category and creates one service by JOnAS server identified by the JOnAS server name. Figure 3-46. JOnAS category and services The check_NSM_JOnAS command defined for the service, returns the state of the server (RUNNING, STOPPED, FAILED, UNREACHABLE). If the server is running, the following attributes are returned: 3.4.3.
3.4.3.7 NovaScale Master Console JOnAS Monitoring Representation The JOnAS category groups services monitoring for all the servers in the domain. Figure 3-48. JOnAS category view Launching the jonasAdmin Application The JOnAS administration tool, jonasAdmin, can be contextually launched from a host node on the NovaScale Master console by clicking: Operations -→ Application -→ jonasAdmin Figure 3-49. jonasAdmin launching Chapter 3.
74 NovaScale Master 5.
Appendix A. Check Commands for Customizable Services of Add_ons This chapter describes the usage of the check commands by customizable services. These commands are Linux commands. They run only under CYGWIN on Windows. Internal Storage Management NSMasterGAMTT check_gamttRAID check_gamttRAID uses the following shell (PERL) command: Usage check_gamttraid -H [-C ] [-p ] [-t ] { [-A {ALL|}] | [-P {ALL|..}] | [-L {ALL|.
• WARNING: At least one ”logical drive” or one ”physical device” is in a WARNING state. • CRITICAL: At least one ”logical drive” or one ”physical device” is in a CRITICAL state. • UNKNOWN All other types of processing errors (bad parameter, no response, and so on…). Note: In the case of multiple errors, the global state will be the worst one; CRITICAL > WARNING > OK.
Examples: • If global state is OK: > check_gamttraid -H GAMTT RAID OK > > check_gamttraid -H -P 0.0.1 GAMTT RAID PD OK > > check_gamttraid -H -L 0.
NSMasterLSICIM check_LSICIM check_LSICIM uses the following shell (PERL) command: Usage check_LSICIM –H [-C ] -H, --hostname Hostname or IP address of target to check -C, --ctrlname Name of the controller to check Note: The name of the controller must be protected with a quote if the name contains blank characters. Return code OK (0), WARNING (1), CRITICAL (2), UNKNOWN (3) • OK: All ”Controllers” run normally.
worst state detected for an element of this controller (LD and PD) ”logical drive” number ”logical drive” type: IM ”logical drive” status as reported by the LSI CIM provider ”channel” number target number ”physical device” manufacturer ”physical device” model ”physical device” status as reported by the LSI CIM provider Examples: $ ./check_LSICIM -H 172.31.50.
NSMasterMegaRaidSAS check_MegaRaidSAS(_IR) check_MegaRaidSAS(_IR) uses the following shell (PERL) command: Usage check_MegaRaidSAS(_IR) -H [-C ] [-p ] [-t ] { [-A {ALL|}] | [-P {ALL|}] | [-L {ALL|
global state descriptor The first line shows the global state. The syntax is: MegaRAID SAS [CT |PD |LD ] ”CT ” if ”-A”. ”PD ” if ”-P”. ”VD ” if ”-L”. state descriptor by controller They may be present after the global state descriptor if an error exists.
> check_MegaRaidSAS-H < hostname > -P 0.2 MegaRAID SAS PD OK > > check_MegaRaidSAS-H < hostname > -L 0.
External Storage Management NSMasterStoreWayFDA check_NECFDA check_NECFDA uses the following shell (PERL) command: Usage check_necfda -H [-C ] [-p ] [-t ] [-f ] -H, --hostname Hostname or IP address of the target to check -C, --community SNMP community string (defaults to ”public”) -p, --port SNMP port (defaults to 161) -t, --timeout Seconds before timing out (defaults to Nagios timeout value) -f, --format ”0” Carriage Retu
Examples: 84 • If the global state is « OK » > check_necfda -H necfda OK > • If the global state is CRITICAL or WARNING, only errors are displayed : • When the return code is UNKNOWN: > check_necfda -H necfda CRITICAL > > check_necfda -H necfda WARNING > > check_necfda -H necfda UNKNOWN - snmp query timed out > > check_necfda -H necfda UNKNOWN - no data received > NovaScale Master 5.
Virtualization Management NSMasterVMwareESX check_esx3 The Nagios check commands used by NMasterVMwareESX Add-on uses the shell (PERL) command check_esx3. Usage check_esx3 -H esxname [-N|-M|-B] [-C community] [-v virtualhost] [-l thing [-w warn -c crit]] [-t timeout] -H Hostname or IP address of the ESX server to check -N,-M,-B set context for check execution -N for Nagios mode, -M for MRTG mode, -B for NSMaster mode.
Output: VHosts: / up: (), . Example: check_esx3 –H esx -C public –w 50% -c 0% VHosts: 2/4 up: nsmvm5(OFF), nsmvm1(ON), nsmvm3(ON), nsmvm4(OFF) Status is set to WARNING if more than 50% of VMs are down. Status is set to CRITICAL if all VMs are down. Note: The list of VMs used to establish ESX server status corresponds to all the VMs declared on the ESX server and not only to those declared on the NovaScale Master ESX platform.
check_esx_vm The check_esx3 shell is called with the following syntax: check_esx3 -B -H -C -v -l STATE Output: OK VHost is up (ID: ) CRITICAL VHost is down (ID: ) Example: check_esx_vm –H esx -C public –v nsmvm1 –l STATE VHost nsmvm1 is up (ID: 48) Status is set to OK if the VM is up. Status is set to CRITICAL if the VMs are down. Note: The VMname is that declared on the ESX server (this name can be different from the NSMaster hostname).
check_esx_vm_cpu The check_esx3 shell is called with the following syntax: check_esx3 -B -H -C -v -l CPU -w % -c % Output: CPU usage is on nsmvm1 (
NSMasterHyperNova check_NSM_hypernova_xen The Nagios check commands used by NMasterHyperNova Add-ons uses the shell (PERL) command check_NSM_hypernova_xen. Usage check_NSM_hypernova_xen -H [-m ][-t timeout] -H Hostname or IP address of the HyperNova server to check -v name of the virtual host to check -h, --help Display help Return code OK(0), WARNING(1), CRITICAL(2), UNKNOWN(3). Output The output is the StatusText as setting by HNMaster.
Output: : StatusText as returned by HNMaster Example: check_NSN_hypernova_xen –H hnserver –m VM1 VM1: VM inactive Status is set to WARNING. Note: The VMname is those declared on the HyperNova Server (this name can be different from the NSMaster hostname). NSMasterViosLpar check_NSM_vios_ivm The Nagios check commands used by NMasterViosLPAR Add-on uses the shell (PERL) command check_NSM_vios_ivm.
-e Sample time in minutes used to perform calculation on utilization. Default value is 5. -w Warning threshold -c Critical threshold. -h, --help Display help Return code OK(0), WARNING(1), CRITICAL(2), UNKNOWN(3). Output The output depends on the type of check performed. See below to get detailed information.
Note: The check_vios_lpar_status command is based on Lpar state obtained by the lssyscfg IVM command. Examples: 1. check_NSM_vios_ivm –H 192.168.207.60 –U padmin –I id_dsa_nsm –N ivm1 l part1 Output: Logical partition part1 on ivm1: Running Return code: OK. 2. check_NSM_vios_ivm –H 192.168.207.60 –U padmin –I id_dsa_nsm –N ivm1 l part2 Output: Logical partition part2 on ivm1: Not Available Return code: CRITICAL.
Output: Logical partition on ( units entitled) - processing utilization on mn : % Note: The check_vios_lpar_used_CPU command is based on cycles metrics (entitled_cycles,capped_cycles,uncapped_cycles ) obtained by the lslparutil IVM command. Examples: check_NSM_vios_ivm –H 192.168.207.60 –U padmin –I id_dsa_nsm -N ivm1 –l part1 -I CPU–e 5 –w 10% –c 20% Output : Logical partition part1 on blade_js21 (0.
Bull Products Management NSMasterDD4A check_DynamicDomains check_DynamicDomains uses the check_DD4A shell (PERL) command: Usage check_DD4A -H [-w ] [-D ] -H, --hostname Hostname or IP address of target to check -D, --domain ALL | ALL domains or a specific one: -w, –-web WEB HTML output format Return code OK (0), WARNING (1), CRITICAL (2), UNKNOWN (3) • OK: All ”Dynamic Domains” run normally.
If -D is used, the command output displays the defined Dynamic Domain name with its number of used CPUs, its CPU load (and the associated threshold) and its number of tasks. Examples: • check_DD4A -H • check_DD4A -H -D ALL 4 Dyn.Domains. - domain2 : WARNING CPUs: 4 / 4, tasks: 70 load: 80% ( > 75% ) - domain3 : CRITICAL CPUs: 4 / 4, tasks: 110 load: 100% ( > 75% ) • check_DD4A -H -D default default : OK CPUs: 7 / 8, tasks: 37 load: 0.56% ( < 75% ) Appendix A.
NSMasterBVS check_BVS check_BullVideoServices uses the check_BVS shell (PERL) command: Usage check_BVS -H -S {Streaming|Recording|Datagrams} [{–p } | { -l -t }] [-w] -H, --hostname Hostname or IP address of target to check -S, --service Streaming|Recording|Datagrams -p, --period | -l -t indicates to the Bull Video Server the period in seconds to calculate the average values -w, --web WEB HTML output format Return code OK (0), WARNING (1), CRITIC
‘Streaming’ service Status global status of ‘Streaming’ service Channels number of channels used for streaming (average) Rate average rate in MB/s Load percentage of disk rate in relation to a value declared on BVS server Example: check_BVS -H -S Streaming Status: OK channels: 17.00, rate (MB/s): 38.84, load: 12.
Service Inaccessible In case of inaccessible service only the RC will be displayed. Example: check_BVS -H -S Status: UNREACHABLE 98 NovaScale Master 5.
NSMasterJOnAS Check_JOnAS Check_JOnAS uses the following shell (PERL) command: Usage check_JOnAS -H -N -a -d -s -p [-u -p ] [ -m] -w -H host host name -N network name network name -a JOnAS server name Administrator or master -d domain name -s target server name -p port number -u user name(mandatory if called outside NSMaster) -p password
The jonas server in jonas domain is RUNNING on nsmaster.frcl.bull.fr Memory allocated = 57700 used = 39949 Threads = 95 HTTP requests count = 0 Committed transactions count = 0 check_JOnAS -H frcls6260 –N frcls6260.frcl.bull.fr -a instance1 -d jonas -s instance1 -p 9000 -m The instance1 (master)server in jonas domain is RUNNING on frcls6260 Memory allocated = 64315 used = 36359 Threads = 98 HTTP requests count = 478157905 Committed transactions count = 0 100 NovaScale Master 5.
Index check_NECFDA, 24, 83 A alerts, 1 Alerts Service, 17, 22, 24 All Service, 66 Armg2_4.
LsiCIM Category, 19 G GAM, 15 GAMTT, 15 M GAMTTraid Category, 17 MegaRAID, 15 GUI, 13 configuration tasks, 13 starting, 13 megaraid.
service, 2 Service Cloning, 14 Creating, 14 Customization, 13 Customizing, 14 U Uninstallation (Linux), 12 Uninstallation (Windows), 9 Upgrading (Linux), 12 ServiceStatus, 17, 22, 24 Upgrading (Windows), 9 SNMP traps, 3 URL NovaScale Master main page, 13 Storage Manager, 3 Storage Server, 23 StoreWay FDA Management, 23 V StoreWayFDA Category, 24 VIOS Monitoring, 62 Streaming Service, 68 VIOS Reporting, 63 ViosLPAR, 52 T thresholds, 1 Virtualization Manager, 3 virtualization platform, 38, 52 Vir
104 NovaScale Master 5.
Technical publication remarks form Title: Reference: NovaScale Master 5.2-x Server Add-ons Installation and Administrator's Guide 86 A2 95ER 03 Date: February 2008 ERRORS IN PUBLICATION SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION Your comments will be promptly investigated by qualified technical personnel and action will be taken as required. If you require a written reply, please include your complete mailing address below.
Technical publications ordering form To order additional publications, please fill in a copy of this form and send it via mail to: BULL CEDOC 357 AVENUE PATTON B.P.
BULL CEDOC 357 AVENUE PATTON B.P.
