ServerView Suite Enterprise Edition V2.41

Transcription

1 ServerView Suite ServerView Suite Enterprise Edition V2.41 System Administration within a Domain System Administration within a Domain Sprachen: En Edition May 2009

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Certified documentation according to DIN EN ISO 9001:2000 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2000. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and Trademarks Copyright Fujitsu Technology Solutions GmbH All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers.

3 Contents 1 Preface Target groups Notational conventions Concept of an administration domain User interface Standard applications Starting the ServerView Suite Loading and starting the product as a local Windows application Downloading the product Starting the ServerView Suite Starting the product as a local application under Linux Starting the product using Java Web Start Starting in read and write mode Download procedure Modifying Java policy settings Starting web-based applications Elements of the user interface Menubar and toolbar Setting preferences Selection configurator Hierarchical browser Object table Standard actions Create Modify Delete Clone System Administration within a Domain

4 Contents 5 Application-specific actions "Domain" application Initial creation of a domain and a management server Changing the password of the domain administrator wdmadm Modifying the communication name of the management server Additional configuration steps Adapting the position of rack mountable units Creating a sub-domain Moving objects Creating a user view Integrating different platforms Integrating PRIMEPOWER nodes Integrating PRIMERGY nodes Integrating PRIMEQUEST servers Integrating SPARC Enterprise Servers (M-Series) Integrating SPARC Enterprise Servers (T-Series) Integrating standard Solaris nodes Integrating SNMP-based nodes Integrating blade servers Administering SNMP nodes Preparing SNMP filter Using the MIB browser on nodes "Config" application Switching the LED on and off (SPARC ES and PRIMEQUEST only) Resetting the error state (SPARC ES only) Partition power control Domain-wide file system access (Solaris only) Importing an NFS file system Dynamic Reconfiguration (DR) (PRIMEPOWER only) Boards tab Hardware presentation tab DR actions Hardware presentation Changing the position of a cabinet in the rack Identifying the cabling between a SCSI controller and the disk add-on (PRIMEPOWER only) System Administration within a Domain

5 Contents 5.3 "Diagnostics" application System diagnosis General troubleshooting Event and reaction definitions "Software" application Checking software versions Checking the packages for consistency Event Management (Alarm Service) Integrating third-party MIBs under Linux Software requirements Installation/configuration Starting the Alarm Service Alarm Service components Alarm Manager Alarm Monitor Managing the Alarm List Displaying server information Alarm settings Making settings Filtering servers Editing alarm groups Forwarding alarms General mail forwarding Forwarding mails to the service provider COM port & modem settings Overview of alarm definitions Icons Displaying trap information Special cases Browser and graphical user interface Performance problems Managing PRIMEQUEST systems System Administration within a Domain

6 Contents 7.4 Problems administering the Archive Manager Problems administering the Inventory Manager Problems administering the Performance Manager Creating log files for troubleshooting Abbreviations Index System Administration within a Domain

7 1 Preface ServerView Suite Enterprise Edition combines different system management interfaces for several server families (PRIMEQUEST, PRIMERGY, PRIMEPOWER, SPARC Enterprise Server) into one graphical user interface, which provides a single point of administration for a large amount of servers. This manual describes the basic operation and use of the administration interface ServerView Suite Enterprise Edition (in the following referred to shortly as ServerView Suite). With the assistance of this graphical interface, a set of nodes can be grouped in an administration domain and monitored and administered from a central location. Managed nodes in this case can be Windows, Solaris or Linux nodes, though practically any network components can also be integrated in the domain with SNMP. This manual does not describe the complete functional scope of the ServerView Suite, rather concentrates on the domain administration and an introduction to the basic operation. Individual optional products and applications are each described in separate manuals. In addition, there are a couple of products that are used in different server families. These are also described in separate manuals. I This product previously was known as WebSysAdmin or WSA for short. The abbreviation WSA still appears frequently in the path and file names. 1.1 Target groups This manual is written primarily for system administrators and field engineering staff. Sound operating system and hardware knowledge is required. System Administration within a Domain 7

8 Notational conventions Preface 1.2 Notational conventions The following notational conventions are used in this manual. italics Denote names of commands, system calls, functions, files, procedures, programs etc. as well as menu options and input/output fields from figures in the main body of text. Name (extension) Commands, system calls, functions, files, interfaces etc., are given an extension in brackets if manual pages are available for them. The extension indicates the chapter in which the manual page is described. You can show the manual pages on the screen with the man [see man(1)] command. See the manual command for man itself for information about using this command. To do this, enter man man. fixed-pitch font Indicates system output, such as error messages, messages, notes, file excerpts and program examples. fixed-pitch semi-bold font Denotes user input in examples. Ê Indicates activities to be carried out by the user. I Highlights additional information that should be noted to assist understanding of the surrounding text passages. V Indicates the possible risk of data loss. 8 System Administration within a Domain

9 2 Concept of an administration domain An administration domain is a group of nodes or partitions that are linked via a network and managed jointly. Advantages of administration domains In comparison with administering individual nodes separately, there are a number of advantages to be gained from forming an administration domain: Single point of administration All nodes in a domain are supported jointly from a single administration desktop and no longer have to be operated individually from the respective system console. It is not necessary to call the system console and authorization is only required once. Overall, resources can be optimized. Extensibility An active node including all its resources can be inserted in or removed from the administration domain at any time. Transparency Because an administration domain appears to a user like a single system (single system view), a cluster of nodes can be administered in the same way as a single operating system. Regardless of the node on which the system administrator has started the user interface, he or she can access the disk storage and other peripherals anywhere in the administration domain at any time for the purpose of administration and configuration. Abstraction from the platform level Computers with different operating systems (Windows, Linux, Solaris) can be administered within a domain. Structuring The administration structure of the domains is hierarchical, which means it can be changed easily. System Administration within a Domain 9

10 Concept of an administration domain Maintenance/troubleshooting The logbooks for all nodes in the administration domain can be evaluated more efficiently from a central desktop. Furthermore, the Logging diagnostics system can be configured specifically for each node from a central desktop. The next diagram illustrates an administration domain Figure 1: Example of an administration domain with an administration desktop (PC client) This administration domain comprises five nodes. The five nodes are connected to one another via TCP/IP (Ethernet). Communication is enabled on this basis for administration purposes. The entire computer network is managed from a single administration desktop (single point of administration) via the ServerView Suite user interface. There must be at least one management server ( ) within the administration domain (it is better to have two available for reasons of fail-safe performance), which contains the domain information (node no. 1 and no. 2 in the example). If the ServerView Suite is started on a management server, all nodes in the administration domain can be administered from one point. The three target nodes (agents) appear to the system administrator like a single system (single system view). 10 System Administration within a Domain

11 Concept of an administration domain It is possible to structure and administer not just one domain, rather a variety of domains. This administration structure is referred to as a hierarchical administration domain. As with UNIX file systems, a hierarchical structure of subdomains can be created starting from a root domain. The root domain corresponds here to the root directory, the individual domains to the directories and the nodes to the files in a UNIX directory structure. The next figure shows this type of hierarchical domain structure: Figure 2: Example of a hierarchical domain structure Two general domains Domain1 and Domain2 are mounted below the root domain. Domain1 contains two nodes ("Node1" and "ManagementServer1") as well as a further sub-domain of the type EnterpriseServer with the two nodes ("Partition1" and "Partition2"). Domain2 contains three nodes ("Node3", "Node4" and "ManagementServer3") as well as a further sub-domain of the type High Availability (HA) with the three nodes ("Node2", "ManagementServer2" and "SNMPagent"). Further domains can be added, deleted, unmounted or renamed based on this hierarchical principle. System Administration within a Domain 11

12

13 3 User interface A domain is administered via the user interface of the ServerView Suite. This chapter contains additional information on the following topics: Standard applications Starting the ServerView Suite Starting web-based applications Elements of the user interface 3.1 Standard applications The ServerView Suite currently contains the following standard applications: Domain Hierarchical administration domains can be managed with the Domain application (create, move, delete node etc.). Config This application contains functions for configuring and managing the hardware both for a single node as well as for a number of nodes in an administration domain. Furthermore, dependent on the operating system support is also provided for managing storage devices, multipath device files and file systems. The hardware is presented graphically, e.g. the systems in a shared rack. Users This application offers functions for managing users and groups, for example creating, modifying and deleting user and group definitions or managing user passwords. Furthermore, it is possible to create user roles and issue authorizations. Diagnostics The Diagnostics application offers functions for domain-wide evaluation of log data, for monitoring as well as for administering the log system itself. System Administration within a Domain 13

14 Standard applications User interface Process This application provides an overview of the status of processes currently being executed and allows them to be deleted and signalled, if appropriate. Software This application enables management of the installed software packages (Unix packages) and patches on all nodes in a domain or on a local node. Task The Task application allows the user root to manage task definitions both for a local node as well as for all nodes in a domain. Task definitions correspond to cron jobs and thus entries in the crontab file of the user root. Event (Alarm Service) The Alarm Service offers an Event Console which can be used to monitor all events. Archive This application enables system and operating data of managed servers to be collected and stored centrally. Inventory This application enables the inventory data of multiple managed servers to be exported to Excel, Access or an SQL database. Performance This application enables threshold values to be generated and processed and reports for long-term monitoring of various server parameters to be created. In addition to these standard application, various so-called "third-party" applications, such as ARMTech or Sun Management Center can be integrated optionally. These applications will not be described in any greater detail here. Because the user interface is self-explanatory, the applications can be used intuitively to a large extent. Should questions arise nevertheless, the integrated help texts provide possible answers. For this reason, the explanations below are purposely kept short and concise and are restricted to the essential elements. 14 System Administration within a Domain

15 User interface Starting the ServerView Suite 3.2 Starting the ServerView Suite The ServerView Suite can be started in three ways: 1. As a locally installed application under Windows (recommended) 2. As a locally installed application under Linux 3. On a Windows PC by means of a browser and Java Web Start Starting the product as a local Windows application has a number of advantages: Low main memory requirement Ease of use and good performance Optimal functionality Problem-free IP address resolution Use as a local Windows application requires that the ServerViewSuiteEE.exe file be downloaded beforehand from a management server. The ServerView Suite can be operated in two different access modes: Either for opening an application in write mode or for opening an application in read mode. If you open ServerView Suite in write mode and the desired application has already been opened by another user in write mode, you are queried whether this application should be opened in read mode. This means that an application can only be opened once for writing by one user. This restriction does not apply in read mode. I If you can only open an application in read mode on a management server, this restriction also applies at this time for all other management servers currently in the administration domain. System Administration within a Domain 15

16 Starting the ServerView Suite User interface Loading and starting the product as a local Windows application Downloading the product If you want to work with the ServerView Suite as a local application under Windows, you have to download it first from a server. You have to enter the following in the URL line of the browser to perform the download: e.g.: You are now on the download page of the ServerView Suite, where you can select the product of the same name. Once you have loaded the suite, you can install it like any Windows application. The self-extracting files install automatically in the Programs menu under the Start button in the task bar when the downloaded exe file is executed. You can start the ServerView Suite locally on your PC from here. I The JRE must to be installed beforehand. 16 System Administration within a Domain

17 User interface Starting the ServerView Suite Starting the ServerView Suite When ServerView Suite is started, a welcome screen appears on your monitor: Figure 3: Welcome screen when ServerView Suite is started You can see which actions are running at present during the start phase in the right-hand side of the welcome window. A progress bar can be found at the very bottom of the screen. Various dialog boxes are displayed at startup depending on requirements. In the first dialog box, enter the name of the management server on which you want to work with the ServerView Suite: Figure 4: Dialog box for entering the host name A further dialog box then appears for entering the user name (if only one user root is permitted, the user input field must be predefined as root): System Administration within a Domain 17

18 Starting the ServerView Suite User interface Figure 5: Dialog box for entering the user name and password When secure SSL-based communication exists between the management server and the managed nodes, the dialog box contains an additional line for entering the PEM password: Figure 6: Dialog box for login with SSL 18 System Administration within a Domain

19 User interface Starting the ServerView Suite If the partition configuration of a PRIMEQUEST server has changed, the following dialog box appears: Figure 7: Dialog box for updating the partition information of a PRIMEQUEST server Confirm the dialog box with Ok. Keep in mind to start the Domain application and to press the Refresh all button after the ServerView Suite has started. If there is a number of optional ServerView Suite applications on the server, the following dialog box appears: Figure 8: Dialog box for installing additional applications You can now download additional ServerView Suite applications (recommended) or continue the startup with Continue. If you download additional applications, a new welcome screen appears with an information line in which the application files that are currently being downloaded are displayed. The old status is restored if this load process is aborted and the start process is continued. I Once additional applications have been downloaded, the product has to be restarted. System Administration within a Domain 19

20 Starting the ServerView Suite User interface The welcome screen appears with the icons for the different applications: Figure 9: Welcome screen for ServerView Suite Deactivated applications are grayed out. This may be the case if an application cannot be started on the server concerned, an application is subject to a license fee and needs to be bought. I Some applications (Life Cycle Modules) such as Event, Archive, etc. are password-protected. If you want to start these applications directly in the browser using a URL, you must enter a password. The standard user name and the standard password are admin and you should change these immediately. You can change various settings using the menu item Edit Preferences (e.g. the password for protected applications). You can now start the node administration by clicking one of the application components at the bottom of the screen. I The first time you call this function you should call the Domain application to create the initial structures. 20 System Administration within a Domain

21 User interface Starting the ServerView Suite Starting the product as a local application under Linux Under Linux, you can start the ServerView Suite on a VGA screen or on a LAN console (see the current ServerView Suite EE Installation Guide). If you want to start the user interface in write mode, enter the following at command level: # /opt/smaw/bin/svsee hostname e.g.: /opt/smaw/bin/svsee discover-scm.pdb.fts.net I The -? or -help option outputs the command options. I Please remember that the DISPLAY variable must be set. If you only want to call the user interface in read mode, enter the following: # /opt/smaw/bin/svsee readonly hostname The welcome screen then appears and you continue as described in the previous section (enter user name and password, settings, choice of application components). System Administration within a Domain 21

22 Starting the ServerView Suite User interface Starting the product using Java Web Start Starting in read and write mode Start your browser. If you start the user interface with Java Web Start and want to call it in write mode, enter the following in the URL line: e.g.: If you want to call the user interface with Java Web Start and only want to call it in read mode, enter the following: I The first time you start the application with a specific browser, a welcome page (startup notes) appears with help information. The download procedure is then initiated automatically Download procedure Once the download procedure has been initiated, the next window informs you about the progress of the application files being loaded: Figure 10: Java Web Start: Download procedure I If ServerView Suite has been started with Java Web Start, the text Java Application Window appears in the status line. 22 System Administration within a Domain

23 User interface Starting web-based applications Modifying Java policy settings In case of using Java Web Start GUI, the java policy needs to be changed to be able to start the so-called "Life Cycle" applications. To do this, please download the Java policy template from the download port (" Then edit this file by using a standard text editor, go to the line permission java.io.filepermission "%USERPROFILE%\\browser.pth", "read, write"; and replace the string %USERPROFILE% by the path of your profile on the Windows system (e.g. D:\\Profiles\\USER1). Please note that "\\" needs to be used as delimiters in the path. If the desired browser (Mozilla Firefox or Internet Explorer) has not been installed to the default path, the path needs to be adjusted, too. If changes have been made before by or for other applications, these changes need to be merged into the edited file. Finally, replace the existing policy file (<JRE_HOME>/lib/security/java.policy) by the new one. 3.3 Starting web-based applications Only the following browsers are supported: Internet Explorer 6 and 7 Mozilla/Firefox 2.0 and 3.0 The following special aspects must be borne in mind: 1. Windows: When you start a web-based application (e.g. Event, Archive, Inventory, Performance) for the first time after ServerView Suite has been installed, the browser path is automatically read from the registry. If this process fails, a pop-up window will request you to specify which browser you use by default. System Administration within a Domain 23

24 Starting web-based applications User interface Figure 11: Request to specify the standard browser 2. Linux: When you start a web-based application for the first time after ServerView Suite has been installed, the browser path is not read automatically and a pop-up window will always request you to specify which browser you use by default. After you have clicked on Ok as confirmation, a dialog box will appear in which you must navigate to the directory containing your browser file (normally C:\<program_directory>\Internet Explorer (Windows) or /usr/bin/firefox (Linux)): Figure 12: Dialog box for selecting the standard browser After you have selected the browser file, click on the Execute button. The system now knows your standard browser. 24 System Administration within a Domain

25 User interface Starting web-based applications 3. Java Web Start: The browser path is not read automatically in this case either, and the following dialog box will always request you to specify the browser path: Figure 13: Request to specify the standard browser in the case of Java Web Start A further pop-up window will also request you to configure the Java Policy beforehand: Figure 14: Request to configure the Java Policy in the case of Java Web Start Details on configuring the Java Policy are provided in the section section Modifying Java policy settings on page 23. System Administration within a Domain 25

26 Elements of the user interface User interface I If you want to change the selection for your default browser, you must edit the browser.pth file accordingly. This file is contained in your home directory (under Linux /opt/smaw/public_html, under Windows <profiles_directory>\<username>). 3.4 Elements of the user interface The following diagram shows an example of a window for the Config component, after you have entered the root password: Figure 15: Window for Config component The window comprises the following elements: Menubar and toolbar Selection configurator Hierarchical browser Object table 26 System Administration within a Domain

27 User interface Elements of the user interface When secure SSL-based communication exists between the management server and the managed nodes, a closed padlock icon can be seen at the bottom left: Figure 16: Icon for SSL connection If the connection is not secure, the padlock is open Menubar and toolbar You can execute various functions from the menubar and toolbar. Some of the actions are dependent on the context and cannot always be executed. Actions that cannot be executed in a particular context are grayed out on the screen. Menubar Toolbar Action File Print object list Edit Export object End session Cut object View Copy object to clipboard Insert object from clipboard Set preferences; see section Setting preferences on page 28 Refresh display read in all data again Application Start applications Table 1: Menubar and toolbar functions System Administration within a Domain 27

28 Elements of the user interface User interface Menubar Toolbar Action Applicationspecific menu (the selected tab appears each time, e.g. Nodes) Create object Modify object Delete object Clone object Other possible application-specific actions Help Contents and Index About the ServerView Suite Green: lists all nodes with the status OK Yellow: lists all nodes with the status warning Red: lists all nodes with the status error Light blue: lists all nodes with an unknown status Lists all inaccessible nodes Ochre: lists all nodes that have received a trap which has not been reset Select objects; see section Selection configurator on page 30 Cancel selected object; see section Selection configurator on page 30 Activity indicator Table 1: Menubar and toolbar functions Setting preferences You are offered the Preferences option under Edit in the menubar: 28 System Administration within a Domain

29 User interface Elements of the user interface Figure 17: Window for setting preferences A dialog box appears with several tabs, on which you can make various settings. A practical example of the Refresh tab follows. When you make a multiple selection in the hierarchical browser (see section Hierarchical browser on page 30) it often makes sense not to update the display immediately, rather only when all objects in the list are selected. A delay time of five seconds has therefore been set for example in the next dialog box: Figure 18: Dialog box for setting preferences You will find additional information in the accompanying help text. System Administration within a Domain 29

30 Elements of the user interface User interface Selection configurator The toolbar also offers a selection configurator, which you can use to find objects using the search algorithm for regular expressions and operators. The search output can be restricted as a result. Figure 19: Selection configurator Hierarchical browser The hierarchical browser serves as a navigation aid, which you can use to select the entire administration domain individual nodes or also individual hardware components (the latter only in the Config application). Depending on what you select, the object list (see section Object table on page 34) will show the objects for the entire administration domain, the selected node or the selected hardware component. 30 System Administration within a Domain

31 User interface Elements of the user interface Figure 20: Hierarchical browser in an administration domain: standard view If you first select a node (computer) in the structure by left clicking it and then click the right mouse button, you can start various actions depending on the node, e.g. Show traps, Start MIB browser, Start administration program etc. You can of course also perform the same actions by selecting and clicking in the object list. Figure 21: Starting actions from the hierarchical browser You can select several components by also holding down the CTRL or Shift key as you press the left mouse button. System Administration within a Domain 31

32 Elements of the user interface User interface If you first select a number of components in the structure by left clicking them and then click the right mouse button, you can start various actions at the same time for all selected components. You will only be offered those actions that are possible simultaneously for all selected components. Figure 22: Starting actions on a number of components at the same time There are buttons in the lower part of the hierarchical browser that you can use to change the view of the displayed objects (you will find a practical example of this in section Creating a user view on page 56). Figure 23: Buttons for changing the view Standard Display of domain structure. Cluster Display of existing HA cluster structures. Shared Display of existing shared group structures. Types Display of type structures. The following types are defined: BladeServer, PRIMEPOWER, PRIMERGY, PRIMEQUEST, SPARC Enterprise Server, Other, Linux, Solaris. New... Creation of a user-defined structure view. This button corresponds to the Create user view action (available only in the Domain application). 32 System Administration within a Domain

33 User interface Elements of the user interface Meaning of selected icons in the hierarchical browser: Root domain. General domain without type specification. Enterprise server type domain. High availability type domain. CF cluster. The hardware status of this node is monitored by ServerView (colored). The node is a management server. The cabinet can be addressed (green). Brocade Fibre Channel Switch. NetApp Filer. Unspecified device. User has no authorization for this node. Table 2: Meaning of selected icons in the hierarchical browser Additional status displays: A node in a domain is not available. Yellow: the object is faulty (warning). It can remain in service for the moment but should be replaced at an appropriate time. Red: the object is defective (error) and must be replaced. Black: the object is deactivated. Ochre: an SNMP agent has sent a message. Light blue: the object is in an unknown state. Table 3: Status display icons in the hierarchical browser System Administration within a Domain 33

34 Elements of the user interface User interface Object table The object table comprises the following areas: The upper area comprises the tab bar with the specific objects. The type and number of tabs depends on the application selected. Figure 24: Tab bar ("Config" application) The object list appears below the tab bar. The type and number of objects displayed depends on the tab or sub-tab selected (see below) as well as on the selections made in the hierarchical browser and selection configurator. Figure 25: Object list ("Config" application) The first column in the object list shows the same information about the status of the individual objects as in the hierarchical browser (see above). I The lower area may contain a sub-tab bar. Whether or not it is displayed as well as the type and number of sub-tabs offered depends on the tab selected. Figure 26: Sub-tab bar ("Config" application) 34 System Administration within a Domain

35 4 Standard actions Standard actions refer to repetitive activities in relation to objects, which depending on the tab selected arise in practically all applications. Four actions are involved here Create Modify Delete Clone Because these four standard actions are similar in a technical sense in all applications, they are presented below using the example of the User application. Apart from the four standard actions listed, some applications also offer actions that can be described as advanced standard actions. These include actions, which allow more detailed specification of simple standard actions, such as Create. The Domain application offers such an advanced standard action: Figure 27: Example of an advanced standard action Special features, such as these advanced standard actions, are considered in the next chapter Application-specific actions on page 47 using various examples. Application-specific actions that go beyond the simple standard actions are introduced there. These application-specific actions can be recognized by the fact that they are offered below the separator in addition to the standard actions. The next figure shows the standard actions together with the specific actions of the User application, tab bar Users: System Administration within a Domain 35

36 Create Standard actions Figure 28: The four standard actions with the two specific actions of the User application Following on from the four standard application actions, the two specific actions of the User application, namely Show logins and Change password are offered. 4.1 Create The first and basic action of any application is the creation of an object. This action creates a new user in the User application or adds users to those already created. In order to add a user to an administration domain, click the User icon in the welcome screen (see figure 9 on page 20) after the ServerView Suite has been started; if you had already started the system and you are currently accessing a different component, click Application on the menubar and choose the User application in the sub-menu. You are then shown an object list with all users who have been created on the node or in the domain. I When you click the Name column header, you can influence the order in which user names are displayed (in ascending or descending alphabetical order). There are two equally appropriate possibilities for creating a new user. You can either Ê click the Users entry in the menubar and choose the Create function in the sub-menu or Ê click the button (create object) in the toolbar. 36 System Administration within a Domain

37 Standard actions Create You are then shown a dialog box and can fill in the fields as you require: Figure 29: Dialog box for creating a new user Our example involves a domain comprising a number of nodes, which is shown by the Nodes entry to the top right above. The andy node is selected and a new user called abraham is to be created on this node. The remaining input fields are blank or the defaults are copied over, such as the user id (106). A short entry has only been made in the comment field. System Administration within a Domain 37

38 Create Standard actions When you have filled in the dialog box and confirmed with Ok, the new user s home directory is prompted: Figure 30: Dialog box prompting the home directory when creating a new user You can generally answer Yes to this query. This completes the entire action and an Ok message is issued: Figure 31: Ok message for creating a new user The new abraham user is created on the system and entered in the object list of users with its attributes: Figure 32: Object list with new user (excerpt) I Only the first 5000 (default) users are ever listed in the object list. If there are more than 5000 users, a relevant warning is issued. 38 System Administration within a Domain

39 Standard actions Modify A newly created user is also not displayed in an object list with more than 5000 entries, if (as in our example) it would have to appear at the very beginning alphabetically. This new user can only be found in this case by performing a search using the selection configurator (see the figure 19 on page 30) on the toolbar. I If an action uses several different parameters, these will generally be divided among different tabs. In this example, the parameters of the Create user action are split between the Main and Password tabs (see figure Dialog box for creating a new user on page 37). 4.2 Modify There are three equally appropriate possibilities for changing the attributes of an existing user. You must first select the relevant users in the object list (click with the left mouse button) so that the line appears in blue (inverted). You can then either Ê Ê click the Users entry in the menubar and choose the Modify function in the sub-menu; or select and then click the user with the right mouse button and then choose the Modify function in the sub-menu; or Ê simply double-click the user name (without selecting it first). I Double-clicking an object generally invokes the Modify action even if the object cannot be changed in any way (exception: Diagnostic application). The second approach is shown in the next figure: Figure 33: Sub-menu for modifying a user I The Modify function is not represented via a button in the toolbar. System Administration within a Domain 39

40 Modify Standard actions In this example, a secondary group is selected for the user abraham, to which this user can also belong in addition to the primary group. The secondary group sysadmin is selected, which must be moved to the secondary group list on the left using the Add button: Figure 34: Dialog box for modifying a user 40 System Administration within a Domain

41 Standard actions Modify You can then look at the result of the change in the object list on the Groups tab. The user abraham is now also a member of the secondary group sysadmin : Figure 35: Object list with modified user (excerpt) System Administration within a Domain 41

42 Delete Standard actions 4.3 Delete There are three equally appropriate possibilities for deleting a user from a domain. You first select the relevant user in the object list (click with the left mouse button) so that the line appears in blue (inverted). You can then either Ê click the Users entry in the menubar and choose the Delete function in the sub-menu; or Ê click the button (delete object) in the toolbar; or Ê select and then click the user with the right mouse button and then choose the Delete function in the sub-menu. The third approach is shown in the next figure: Figure 36: Sub-menu for deleting a user Two dialog boxes then follow with confirmation prompts to which you answer Yes each time: Figure 37: First dialog box confirming the deletion of a user 42 System Administration within a Domain

43 Standard actions Delete Figure 38: Second dialog box confirming the deletion of a user The deleted user is then no longer in the user s object table. I A user cannot be deleted globally from all nodes in a domain rather only individually on the respective node. It is possible, however, to delete several users on a node in one action, assuming the appropriate selection is made. The confirmation prompt prior to deletion then refers to the actual overall selection. System Administration within a Domain 43

44 Clone Standard actions 4.4 Clone Cloning a user means copying a previously created user including his or her attributes to other nodes in a domain. There are two equally appropriate possibilities here. You first select the relevant user in the object list (click with left mouse button), so that the line appears in blue (inverted). You can then either Ê Ê click the Users entry in the menubar and choose the Clone function in the sub-menu; or select and then click the user with the right mouse button and then choose the Clone function in the sub-menu. The second approach is shown in the next figure: Figure 39: Sub-menu for cloning a user I The Clone function is not represented via a button in the toolbar. 44 System Administration within a Domain

45 Standard actions Clone When you have selected the user to be cloned and the Clone function, you then have to select the other nodes in the domain to which the user is to be copied in the next dialog box: Figure 40: Dialog box for cloning a user When you confirm the dialog box with Ok, the user abraham is copied to the two nodes chris and georg. There is no Ok message. You can check if the action was successful in the object list of users in the main window. It is only in the event of an error that a relevant message is issued. I If the user id of a user being cloned is already assigned on a different node, cloning is not possible for this node. An error message is issued to this effect. System Administration within a Domain 45

46

47 5 Application-specific actions Application-specific actions were described in general in the chapter Standard actions on page 35 as those actions that are offered in any application in addition to the four possible standard actions Create, Modify, Delete and Clone. These specific actions are obviously very different depending on the application and tab and have very little commonality. The next sections therefore only provide examples of some selected actions from individual applications. Of the standard applications, examples were selected from Domain Config Diagnostics Software Actions that can be defined as typical for the respective application were chosen largely. System Administration within a Domain 47

48 "Domain" application Application-specific actions 5.1 "Domain" application Hierarchical administration domains can be managed with the Domain application. Hierarchical administration domains are structured the same way as file directories, as are familiar, for example, from UNIX. A hierarchical administration domain comprises a root domain, below which any number of domains and nodes can be mounted. The root domain thus corresponds to the root directory, the individual domains correspond to the directories and the nodes to the files in the UNIX directory structure. I You should note that the ServerView Suite is started on a management server. This is the only way you can manage the entire hierarchical administration domain. I Partitions of a PRIMEQUEST server cannot be declared as management server. The next examples assume a starting position of zero where no nodes are configured and the ServerView Suite is being started for the first time. You will be informed step-by-step of how to do the following: Initially create the root domain and the management server Change the communication name of the management server Adapt the position of rack mountable units Create a domain Move an object within a domain Create a separate user view of the hierarchical browser Integrate other platforms Administer SNMP nodes I If you are not using SSL, the Domain application creates a wdmadm user with a default password on all participating nodes. This password can be changed with the User application by choosing the Change password action. 48 System Administration within a Domain

49 Application-specific actions "Domain" application Initial creation of a domain and a management server When the ServerView Suite is started for the first time following installation, the domain domain is created and the server node is created as the management server in this domain. This initial creation is performed automatically and can only be identified for a short time by the progress indicator: Figure 41: Progress indicator for initial start The initial domain created is then displayed with the management server in the hierarchical browser: Figure 42: Initial root domain with automatically created management server I A default password is supplied for the domain administrator wdmadm. This should be changed immediately for security reasons. System Administration within a Domain 49

50 "Domain" application Application-specific actions Changing the password of the domain administrator wdmadm Ê Select the user wdmadm of the management server and start the object action Change password. Figure 43: Selecting user wdmadm and starting Change password 50 System Administration within a Domain

51 Application-specific actions "Domain" application In the Nodes box of the Change user s password window all reachable systems are listed where the user entry exists and where the password will be replaced. I Make sure that all nodes are reachable to change the password consistently on all of them. Figure 44: Change user s password window Ê Ê Enter the new password for the wdmadm user. Reenter the password and click on Ok. System Administration within a Domain 51

52 "Domain" application Application-specific actions Modifying the communication name of the management server The management server created the first time the ServerView Suite is started has as its communication name (i.e. the alias name under which the node can be addressed in the network) the name supplied by the uname command (e.g. "mach1"). If administration is handled via an alternative LAN, the communication name for the node mach1 must be changed before the domain is created. The Modify communication name action is provided for this purpose under the Administration hierarchy tab. This action allows you to change the communication name of the automatically created management server. When you start the Modify communication name action, a dialog box appears with a selection list of all IP addresses configured on the system and their associated communication names. Having selected the desired address and exited the dialog box with Ok, the password must be entered in a second dialog box. If this dialog box is likewise exited with Ok, the system checks whether the password is correct. If it is correct, the communication name and the IP address are changed. All communication layers continue to communicate via this IP address. I The communication name of the management server can be changed only directly after you have installed the ServerView Suite, i.e. before a domain is created. I You can assign the communication name of an alternative LAN in the Create node (cf. figure 51 on page 60) dialog box to create additional nodes. The Communication name input field, which is filled by default with the name supplied with the uname command, can be edited. The system checks whether the communication name entered can be resolved as an IP address and enters this in the Communication address field. Once the node has been created, all communication layers then use this IP address to communicate. It is not possible to retrospectively change the communication names of nodes that exist already. If a different communication name is to be used for a node, this node must be deleted and created again with the new communication name. 52 System Administration within a Domain

53 Application-specific actions "Domain" application Additional configuration steps Once you have created the domains and nodes, additional one-off configuration steps may be necessary or possible. Some examples of such actions are given below. These include: Adapting the position of rack mountable units Creating a sub-domain Moving objects Creating a separate user view of the hierarchical browser Adapting the position of rack mountable units It is possible for a node to contain rack mountable units whose location cannot be established by the system, for example a rack cabinet and SCSI devices. No position is shown for these parts, rather the position must be established explicitly with the Config application on the Hardware Presentation tab (see section Changing the position of a cabinet in the rack on page 105) Creating a sub-domain Once the root domain is available with a management server as a basis, you can create further domains hierarchically. To do this, start the relevant action by choosing Administration hierarchy Create Domain, as illustrated in the next figure: Figure 45: Sub-menu for creating a sub-domain System Administration within a Domain 53

54 "Domain" application Application-specific actions The following dialog box opens where you have to enter the name and group designation of the new domain: Figure 46: Dialog box for creating a domain The new domain under the root domain in our example is called "Headquarters"; in terms of its group this is a general domain. This characterization is the default scenario. I The following restrictions apply for domain and node names in a hierarchical domain: Node names must be unique throughout the domain. Node names may only contain the characters "a-za-z0-9" as well as hyphen (" ") and underscore ("_"). Domain names must be unique within their parent domain. Domain names may include the characters "a-za-z0-9" as well as hyphen (" ") and underscore ("_"); a maximum of 20 characters is permitted. 54 System Administration within a Domain

55 Application-specific actions "Domain" application Moving objects You can move all objects (domains, management servers, nodes) about as required in an administration domain. For example, you can move the management server with the name "clara" from its original position below the root domain to the sub-domain "Headquarters". This positions the console closer to the monitored system, for example in order to perform a software check by clicking the common parent domain. Select the node to be moved in the hierarchical browser or object list with the left mouse button and open the relevant dialog box Ê from the menubar by choosing Administration hierarchy Move or Ê by pressing the right mouse button and choosing the Move option offered to you. When you have selected an action, a dialog box is opened where you can specify a new mountpoint: Figure 47: Dialog box for moving a node The "clara" management server is moved in our example from the "Company" root domain to the "Headquarters" sub-domain. The new position is displayed in the hierarchical browser. System Administration within a Domain 55

56 "Domain" application Application-specific actions Creating a user view In addition to the standard view of the hierarchical browser in the administration domain, you can create any number of user-defined, private views in accordance with your requirements. You can do this either from the menu by selecting Administration hierarchy Create user view or by clicking the New... button in the lower part of the hierarchical browser. A dialog box opens in which you assign a name for your private user view: Figure 48: Dialog box for creating a private user view Once you have concluded the action by selecting Ok, the new user view is inserted as a new button in the lower part of the hierarchical browser. A new user view called "Function" was created in our example. You can now perform various actions within the newly created user view. For example, it s possible to give the domain a new name. You do this by selecting the domain, clicking it with the right mouse button and starting the Rename actions. You can then create the new sub-domain (Administration hierarchy Create Domain) and redistribute the nodes (select the node and start the Move action). 56 System Administration within a Domain

57 Application-specific actions "Domain" application When you have adapted the structure view to suit your requirements, you can switch between the two different views by clicking the buttons. The standard view and the user-defined "Function" view of the hierarchical browser are positioned side by side in the next diagram: Figure 49: Standard view and user-defined view of the hierarchical browser System Administration within a Domain 57

58 "Domain" application Application-specific actions Integrating different platforms The ServerView Suite offers the possibility of administering platforms other than enterprise server systems and displaying events on these systems. These are i.a. PRIMEPOWER nodes PRIMERGY nodes PRIMEQUEST nodes SPARC Enterprise Server Standard Solaris nodes (i.e. Solaris systems on non-primepower machines) SNMP-based nodes (e.g. SAN devices, FC switches etc.) Blade server These platforms are introduced briefly in the next sections. 58 System Administration within a Domain

59 Application-specific actions "Domain" application Integrating PRIMEPOWER nodes I This function is possible only if the PRIMEPOWER ServerView Suite Agent is installed on the node to be integrated. A PRIMEPOWER node is added to the administration domain just like any other normal node. This is done with the Administration hierarchy Create PRIMEPOWER node action: Figure 50: Sub-menu for creating a PRIMEPOWER node Once you have initiated this action, the following dialog box opens where you can enter the attributes for the new node: System Administration within a Domain 59

60 "Domain" application Application-specific actions Figure 51: Dialog box for adding a PERIMEPOWER node The individual fields have the following meaning: Node name You enter the system name of the PRIMEPOWER node in this field. This is the name shown to you with the UNIX uname -n command. Password You enter the root password of the PRIMEPOWER node in this field. Communication name You define the alias name in this field under which the node is addressed in the network. This field is assigned the node name itself by default. However, you can specify the name of a different Ethernet controller configured on the node. Position (before) You define the position at which the new node is to be inserted in the selected hierarchical level in this selection list. 60 System Administration within a Domain

61 Application-specific actions "Domain" application Mgmt server You define in this field whether the PRIMEPOWER node is to be a management server, if possible. Comment You can enter any comment in this field. When the action is concluded with Ok, the new PRIMEPOWER server is created (i.e. added to the administration domain) and is displayed in the hierarchical browser Integrating PRIMERGY nodes Adding an individual PRIMERGY node to the administration domain A PRIMERGY node is added to the administrating domain just like any other normal node. This is done with the Administration hierarchy Create PRIMERGY node action: Figure 52: Sub-menu for the action for creating a PRIMERGY node System Administration within a Domain 61

62 "Domain" application Application-specific actions Once you have started this action, the following dialog box appears: Figure 53: Dialog box for adding an individual PRIMERGY node The root password has to be specified for a Linux node with a ServerView Suite Agent installation. The data is established exclusively via SNMP in the case of Windows nodes. Password input is not necessary. The individual fields have the following meaning: Node name You enter the system name of the node in this field. This is the name shown to you with the UNIX uname -n command. Password You enter the root password of the node in this field. 62 System Administration within a Domain

63 Application-specific actions "Domain" application Communication name You define the alias name in this field under which the node is addressed in the network. This field is assigned the node name itself by default. However, you can specify the name of a different Ethernet controller configured on the node. Communication address This field cannot be edited. The IP address is established automatically in accordance with the communication name. Community name In this field you enter an SNMP user ID that is used during the search. If the community specified here is not supported by a node, it will not be found. The field is preset with the value public. Type of machine This field cannot be edited. The node type is established automatically. Position (before) You can define the position at which the new node is to be inserted in the hierarchical level in this selection list. Administration command This field cannot be edited. The web address, which is to be called with the Start PRIMERGY ServerView Suite action is preconfigured. Comment You can enter any comment in this field. Quotes are not permitted. In our example, a PRIMERGY node was selected with a Windows operating system for which no password has to be specified. The light gray colored fields (machine type, etc.) were detected automatically by the system and filled in. Having concluded the action by pressing Ok, the new node is created (i.e. added to the administration domain) and is displayed in the hierarchical browser. You can now view the system data. I The get access via SNMP must be enabled on the PRIMERGY (see PRIMERGY ServerBooks). System Administration within a Domain 63

64 "Domain" application Application-specific actions Integrating PRIMEQUEST servers PRIMEQUEST servers are computer center servers for business-critical corporate processes under Linux and Windows. I Before adding the PRIMEQUEST to the domain on the management server, setting up the PRIMEQUEST system is required in advance. Please refer to the corresponding description in the current ServerView Suite EE Installation Guide. A PRIMEQUEST server is added to the administration domain using the action Administration hierarchy Create PRIMEQUEST server: Figure 54: Sub-menu for creating a PRIMEQUEST server The following dialog box appears in which you specify the name of the management board in the Management Board field and some access authorizations compatible to PRIMEQUEST MMB Web UI. All partitions contained in this cabinet are then added at once. 64 System Administration within a Domain

65 Application-specific actions "Domain" application Figure 55: Dialog box for adding a PRIMEQUEST server When the action is concluded with Ok, the new PRIMEQUEST server is created (i.e. added to the administration domain) and is displayed in the hierarchical browser. You can now display the system data. I The data is read via SNMP; the SNMP function must therefore be activated on the PRIMEQUEST system. I It can take up to 10 minutes before the presentation in the Life Cycle Modules is correct. For this period the partitions are presented as not managed. System Administration within a Domain 65

66 "Domain" application Application-specific actions Integrating SPARC Enterprise Servers (M-Series) SPARC Enterprise Servers (M-Series) are computer center servers for missioncritical corporate processes under Solaris. A SPARC Enterprise Server (M-Series) is entered in the management domain using the action Administration hierarchy Create SPARC Enterprise Server (M- Series): Figure 56: Sub-menu for creating a SPARC Enterprise Server (M-Series) 66 System Administration within a Domain

67 Application-specific actions "Domain" application The following dialog box appears in which you can specify the name of the management board in the Management Board field. All the partitions which are contained in an M-Series cabinet are then included at once. Figure 57: Dialog box for creating a SPARC Enterprise Server (M-Series) The individual fields have the following meaning: Management board The alias name for the IP address of the active XSCF board of the SPARC Enterprise server can be entered in this field. When you specify an alias name, the system tries to establish the IP address automatically so that no input is required in the Communication address field. If the IP address cannot be established, the specified alias name does not exist. Communication address You can specify the IP address of the SPARC Enterprise server in this field. When you specify an IP address, the system tries to establish the alias name automatically so that no input is required in the Management board field. If no alias name is found, the IP address is likewise entered in the Management board field. System Administration within a Domain 67

68 "Domain" application Application-specific actions Position (before) In this selection list you specify the place in the hierarchy tree where the new node is to be inserted. Type of machine This field cannot be edited. The machine type is established automatically. Administration command This field cannot be edited. The web address, which is to be called with the Start XSCF web console action is preconfigured. Comment You can enter any comment in this field. Quotation marks are not allowed. Action in progress The current status of the creation process is logged in this field. After you have completed the action by clicking on Ok, the new SPARC Enterprise Server (M-Series) is created (i.e. entered in the management domain) and displayed in the hierarchical browser. You can now have the system data displayed. I The data is read using SSH. The SSH function must consequently be activated on the Enterprise Server (for details, please refer to the current ServerView Suite EE Installation Guide). 68 System Administration within a Domain

69 Application-specific actions "Domain" application Integrating SPARC Enterprise Servers (T-Series) SPARC Enterprise Servers (T-Series) are smaller than M-Series computer center servers for mission-critical corporate processes under Solaris. A SPARC Enterprise Server (T-Series) is added to the administrating domain just like any other normal node. This is done with theadministration hierarchy Create SPARC Enterprise Server (T-Series) action: Figure 58: Sub-menu for creating a SPARC Enterprise Server (T-Series) System Administration within a Domain 69

70 "Domain" application Application-specific actions Once you have started this action, the following dialog box appears: Figure 59: Dialog box for creating a SPARC Enterprise Server (T-Series) The individual fields have the following meaning: Node name You can enter the system name of the node in this field. This is the name shown to you with the UNIX uname -n command. When you specify the name, the system tries to establish the IP address automatically so that no input is required in the Communication address field. If the IP address cannot be established, the specified name does not exist. Communication address You can specify the IP address of the SPARC Enterprise server in this field. When you specify the IP address, the system tries to establish the alias name automatically so that no input is required in the Node name field. If no alias name is found, the IP address is likewise entered in the Node name field. Position (before) You can define the position at which the new node is to be inserted in the hierarchical level in this selection list. 70 System Administration within a Domain

71 Application-specific actions "Domain" application Type of machine This field cannot be edited. The machine type is established automatically. Comment You can enter any comment in this field. Quotes are not permitted. Action in progress The current status of the creation process is logged in this field After you have completed the action by clicking on Ok, the new SPARC Enterprise Server (T-Series) is created (i.e. entered in the management domain) and displayed in the hierarchical browser. You can now have the system data displayed. I The data is read using SSH. The SSH function must consequently be activated on the Enterprise Server (for details, please refer to the current ServerView Suite EE Installation Guide). System Administration within a Domain 71

72 "Domain" application Application-specific actions Integrating standard Solaris nodes The following ServerView Suite functions are supported on the standard Solaris nodes: Domain/node management FS/NFS administration (for standard file systems) The User Management, Software, Process and Tasks applications Diagnostics (display of logbook) The following functions are not supported: Configuration and localization of HW resources (cabinets, boards, controllers, storage devices) Graphical presentation Patch management PRIMECLUSTER integration HW diagnostics and associated SNMP events By integrating standard Solaris nodes into the ServerView Suite, the system data for such nodes can be displayed. The prerequisite is that the Solaris nodes have been added first to the administration domain. These activities are presented below. Adding Solaris nodes to the administration domain Standard Solaris nodes are added to the administration domain like any normal nodes. This is done in the Domain application with the Administration hierarchy Create Default Solaris node action: 72 System Administration within a Domain

73 Application-specific actions "Domain" application Figure 60: Dialog box for adding Solaris nodes When you have finished editing the dialog box and concluded the action with Ok, the Solaris node is added to the administration domain of the ServerView Suite. System Administration within a Domain 73

74 "Domain" application Application-specific actions Displaying HW data from SunMC nodes I The software required is SunMC 3.0. If the Sun Management Center is installed on the computer, you can view the system data. Select the Solaris node (either in the hierarchical browser or in the object list) and execute the Start SUN Management Center action: Figure 61: Sub-menu for starting the system display of Solaris nodes If the Solaris node is both a SunMC agent and a SunMC server, the following dialog box appears, querying the access authorization for the SunMC server: 74 System Administration within a Domain

75 Application-specific actions "Domain" application Figure 62: Dialog box for logging on via a SunMC server Once you have logged in correctly, a connection is set up to the Solaris node via the SunMC server and the system data is displayed: Figure 63: Display of system data for a Solaris node You still have to click the hardware symbol in order to display the data. System Administration within a Domain 75

76 "Domain" application Application-specific actions Integrating SNMP-based nodes SNMP (Simple Network Management Protocol) is a standard protocol for the management in heterogeneous networks. It is used under the ServerView Suite for monitoring non UNIX nodes that support SNMP. SNMP is a manager/agent-based protocol. The manager can query the status of the agent with a get request or set the status with a set request. The agent uses traps to inform the manager asynchronously of important events. The SNMP-based nodes include: SAN devices FC switches By integrating these SNMP-based nodes in the ServerView Suite, the system data for such nodes can be displayed. The prerequisite for this is that these SNMP nodes have been added first to the administration domain. These activities are presented below. Adding SNMP-based nodes The adding of SNMP-based nodes to the administration domain is performed by choosing Administration hierarchy Create Other node (SNMP-based): Figure 64: Sub-menu for creating an SNMP node Having initiated this action, the following dialog box opens in which you can select the type of the new SNMP node in the Node type field: 76 System Administration within a Domain

77 Application-specific actions "Domain" application Figure 65: Dialog box for creating an SNMP node The individual attribute fields have the following meaning: Node name The alias name for the IP address of the SNMP node can be entered in this field. When you specify an alias name, the system tries to establish the IP address automatically so that no input is required in the Communication address field. If the IP address cannot be established, the specified alias name does not exist. A Brocade SilkWorm 3200 system was selected as the machine type in our example. Communication address You can specify the IP address of the SNMP node in this field. When you specify an IP address, the system tries to establish the alias name automatically so that no input is required in the Node name field. If no alias name is found, the IP address is likewise entered in the Node name field. System Administration within a Domain 77

78 "Domain" application Application-specific actions Community name In this field you enter an SNMP user ID that is used during the search. If the community specified here is not supported by a node, it will not be found. The field is preset with the value public. Group of machine In this field you preselect the machine types that can be selected in the next field. Type of machine The machine type can be selected from the list. The node type is used for the representation in the hierarchical browser and for the hardware presentation. Position (before) You can define the position at which the new node is to be inserted in the hierarchical level in this selection list. Administration command You can specify a web address in this field, which is to be called when the Start of Administration Program action is invoked. For example, you could specify the web address here for managing the SNMP node. The predefined string %ip% is a placeholder for the IP address from the Communication address field. Comment You can enter any comment in this field. Quotes are not permitted. When the action is concluded with Ok, the new node is created and is displayed in the hierarchical browser. You can now view the system data. Adding SNMP nodes with the SNMP search function You can search a sub-network for IP addresses and add one or more of the located IP addresses to the administration domain. It is attempted here to establish the node type on the basis of the SNMP protocol. 78 System Administration within a Domain

79 Application-specific actions "Domain" application The addition of SNMP nodes using the SNMP search function is performed by choosing Administration hierarchy Create Discover subnet for nodes: Figure 66: Sub-menu for starting the SNMP search function A dialog box appears in which the following details have to be entered: An SNMP community, which is used during the search process. A list of subnet addresses to be searched, in the form xxx.xxx.xxx.xxx, whereby xxx are digits in the range 0 to 255. A subnet mask in dot notation (in the form of a subnet address) or in CIDR notation (as a number in the range 1 to 32). I The subnet mask is restricted in the dialog box to a value range of 8 to 30. The subnet mask determines which bits of the IP address specified in the Subnet address field are used for forming the subnet and therefore establishes the size of the range of host addresses to be examined. Examples of input in dot notation and CIDR notation: 25 corresponds to max. number of hosts = corresponds to corresponds to System Administration within a Domain 79

80 "Domain" application Application-specific actions Figure 67: Dialog box for creating a subnet The subnet ID operates as follows: The Add button is activated after entering a correct subnet address and subnet mask (dot notation or CIDR notation as in the example). If you click the Add button, the actual subnet address and subnet mask is calculated from the values specified in the Subnet address and Subnet mask fields in CIDR notation and added to the list of subnets to be searched. 80 System Administration within a Domain

81 Application-specific actions "Domain" application A number of subnets can be added to the list. If the list is not empty, the Discover and Remove buttons are activated. Clicking the Remove button deletes the selected subnet from the list of subnets. Clicking the Discover button disables all input fields in the dialog box and starts the search. A progress bar appears during the search as well as a message showing the address ranges just examined. Pressing Cancel stops the search process. This may take a while because the system has to wait until the process has actually ended. If the system has already found nodes, these are displayed for further processing. If the search process ends normally or is cancelled and nodes have already been found, the following dialog box is displayed: Figure 68: Dialog box with SNMP parameters This dialog box shows all SNMP nodes that have been detected. The attributes displayed include the IP address, agent name (the IP address is likewise displayed here if it could not be resolved by the name service), the MIB II variable SysObjID and the machine type, which is derived from the respective SysObjID. By clicking the checkbox in the first column, the user determines whether or not the selected node is to be added to the domain (clicked). All nodes can be selected by clicking the Select all button and deselected by clicking the Deselect all button. Clicking the Ok button adds all selected SNMP nodes to the domain if they do not yet belong to the domain. The adding of the nodes may take a while. A progress bar is displayed as well as the name of the node that is currently being System Administration within a Domain 81

82 "Domain" application Application-specific actions added. Clicking the Cancel button after pressing Ok aborts the add process. All nodes added up to this point remain in the domain and the dialog box is closed. Pressing the Cancel button immediately deletes the dialog box from the screen Integrating blade servers A blade server is a server system that comprises a number of full nodes in 19" housing. The individual nodes are termed blades. All nodes of a blade server can be added in one move to an administration domain with the Administration hierarchy Create Blade server action: Figure 69: Sub-menu for creating a blade server The following dialog box appears in which you can specify the name of the management blade server in the Node name field. All blades installed in this cabinet are then added at once. 82 System Administration within a Domain

83 Application-specific actions "Domain" application Figure 70: Dialog box for creating a blade server When the action is concluded with Ok, the new blade server is created and is displayed in a sub-domain in the hierarchical browser in accordance with the naming convention BladeServer_<communication address>. System Administration within a Domain 83

84 "Domain" application Application-specific actions Administering SNMP nodes SNMP is a manager/agent-based protocol. The manager can query the status of the agent with a get request or set the status with a set request. The agent uses traps to inform the manager asynchronously of important events. Various actions are provided for monitoring non-unix nodes that support SNMP, of which we would like to introduce the following two: Prepare SNMP filter Use MIB browser on SNMP nodes Preparing SNMP filter You should prepare the filter such that not all traps are received indiscriminately, rather only specific messages that are required by you. In order to prepare an SNMP filter according to your requirements, start the Edit SNMP filters action on the Administration hierarchy tab. Figure 71: Sub-menu for editing the SNMP filter 84 System Administration within a Domain

85 Application-specific actions "Domain" application A dialog box is then opened where you can change the SNMP filter for the different SNMP managers: Figure 72: Dialog box for changing the SNMP filter To change the SNMP filter, you have to first select a node in the SNMP manager field. All filter entries located for this node are then shown in the table below. When you select a line, the entries are taken over from the table columns to the underlying input fields. You can modify the values here (as in the example) or transfer them to the table using the Add or Modify buttons. A trap filter only permits traps that comply with the filter conditions, where the asterisk (*) stands for all. You can delete the selected entry with the Remove button. If you switch to a different SNMP manager, changes made previously are preserved. The changes only come into effect when you exit the dialog box with the Ok button. System Administration within a Domain 85

86 "Domain" application Application-specific actions Using the MIB browser on nodes The MIB browser is started by selecting a node in hierarchy browser or the node list and clicking the Start MIB Browser menu option in the sub-menu. Figure 73: Sub-menu for starting the MIB browser The following window is displayed: Figure 74: MIB browser window for a node 86 System Administration within a Domain

87 Application-specific actions "Domain" application The MIB structure of the MIBs installed on the SNMP manager of the selected node is shown on the left. The user can navigate through the entire MIB structure. When a node in the structure is selected, the corresponding OID is entered in the text field with the name Oid. The relevant information is displayed for this MIB structure for the selected SNMP node by clicking Read Information. The community name of the Community text field is used for this process. Text can be entered directly in both fields. The values of the MIB variables can continue to be read until the user presses the Ok button. The window then disappears from the screen. System Administration within a Domain 87

88 "Config" application Application-specific actions 5.2 "Config" application I The functions described below depend on the hardware and operating system. Config is the application with the most objects to be administered. A glance at the tab bar shows all components at once: Figure 75: Config tab bar A few major functions are presented below by way of example Switching the LED on and off (SPARC ES and PRIMEQUEST only) In PRIMEQUEST systems you can switch a board s or a cabinet s LED on and off (in the case of SPARC Enterprise Servers, only the cabinet's). You switch on the LED to make the board or cabinet easier to locate. You will find the action for switching a LED on or off under the Boards, Cabinets and Hardware Presentation tabs. The two actions are offered alternately, i.e. when a LED is switched on, "off" is offered, and when it is switched off, "on" is offered. Ê To switch a LED on or off, select the board or cabinet in the object list and open the pull-down menu using the relevant button in the menu bar (see figure 76 on page 88) or by clicking the right mouse button. Figure 76: Switching a LED off 88 System Administration within a Domain

89 Application-specific actions "Config" application Resetting the error state (SPARC ES only) Certain components of a SPARC Enterprise Server are not monitored by means of XSCF software. When a hardware fault in such a component has been corrected, you must reset the error display (red dot in the hierarchical browser) manually. This action is offered for the following objects: Nodes (SPARC Enterprise Server partition) Cabinets Disks Storage devices (DVD/tape) Hardware components in the PCI Box (currently only boards) Ê In the object list, select the hardware component affected (in our example the SPARC Enterprise Server partition dc2-1-p0-p0), and open the pull-down menu using the button provided in the menu bar (see figure 77 on page 89) or using the right mouse button. After you initiate the action, the error display is deleted, i.e. the red dot is no longer displayed in the hierarchical browser. Figure 77: Resetting the hardware error state System Administration within a Domain 89

90 "Config" application Application-specific actions Partition power control I This function is only supported for partitionable systems. Depending on the server type and the partition status you can execute various actions for the partitions of a partitionable server under the Nodes tab: Power-off/power-on for a partition Resetting a partition s operating system Generating a dump of a selected partition (PRIMEPOWER only) Immediate power-off for a partition Restarting a partition s operating system Proceed as follows: Ê To implement partition power control, select the required partition in the object list and open the pull-down menu using the Nodes button in the menu bar (see figure 78 on page 90) or by clicking the right mouse button. Figure 78: Partition power control 90 System Administration within a Domain

91 Application-specific actions "Config" application Domain-wide file system access (Solaris only) The ServerView Suite offers all nodes in the domain the option to access a file system. This section uses an NFS file system to show how this can be managed in a few simple steps. The following tasks are to be performed in this example: An entry should be made on all systems for the file system in the /etc/vfstab file. The file system should be mounted immediately. The system should also be mounted automatically when this system reboots. I In order to enable domain-wide access to an NFS file system, the relevant resource must first be exported on the NFS tab Importing an NFS file system To import an NFS file system, you have to: Ê Change to the File systems tab (Config application). Ê Click the File systems option on the menubar. Ê Now choose the Import network file system option, sub-option Nfs. Figure 79: Selection menu for importing file systems System Administration within a Domain 91

92 "Config" application Application-specific actions The following dialog box is displayed: Figure 80: Dialog box for importing an NFS file system Fill in the dialog box as displayed in the diagram above: Ê Ê In the NFS node field, enter the node on which the file system being imported is located (in the example: OfficeServer). In the NFS path field, enter the path of the file system being imported on the specified node (in the example: /export/documents). 92 System Administration within a Domain

93 Application-specific actions "Config" application Ê Ê Ê Ê I When importing an NFS file system, you can specify both a node name and NFS node path, which do not belong to the domain. In the Nodes list, select all systems that are to receive access to the NFS file system (in the example: Partition1 and Partition2). The options Autom. mount at boot (controlled by the entry in the /etc/vfstab file) and Immediate mount are executed by default and thus lead to the actions required in the example. In the Mountpoint field, you can enter a pathname, which is to be used as the mount point for the NFS file system. The same pathname is used for all selected nodes (in the example: /office_documents). This can subsequently be modified separately for each individual node. All other fields are already assigned default values, which can be copied over here. Click Ok to exit the dialog box. As a result of the previously described actions, the imported NFS file system on the selected node is displayed in the object list on the Usage parameters sub-tab: Figure 81: Object list with imported NFS file system I The search criterion docu was specified with the selection configurator to reduce the number of objects displayed. The NFS file system (in the example: /export/documents) is thus available to all selected NFS clients in the domain with the access rights defined in the dialog box (see figure 80 on page 92). System Administration within a Domain 93

94 "Config" application Application-specific actions Dynamic Reconfiguration (DR) (PRIMEPOWER only) I This function is offered only if the PRIMEPOWER ServerView Suite Agent is installed on all partitions. Dynamic reconfiguration allows you to add and remove system boards on PRIMEPOWER enterprise servers to and from partitions immediately or at next reboot. System boards are displayed in the Config application in the hierarchical browser and in the object table of the Boards tab. Both views display "unused" system boards and their onboard components ("unused" means any DR status other than "configured"). All unused components (available for DR) are marked by black colored dots. In contrast to the red colored dots indicating hardware errors, these black dots are not propagated up the tree to the top (see figure below). System boards available for DR are displayed for each partition to which they can be added. 94 System Administration within a Domain

95 Application-specific actions "Config" application Figure 82: Hierarchical tree displaying unused system board The figure shows the unused system board Systemboard_6. Note that it is shown for all partitions ("zar0", "zar1", "zar2") and that the CPU type is different for unused CPUs. System Administration within a Domain 95

96 "Config" application Application-specific actions Boards tab The Boards tab has a sub-tab called Systemboards DR, which lists all the DRrelevant system boards together with their DR-related properties and allows execution of dynamic reconfiguration: Figure 83: Object table of the Systemboards DR sub-tab The four columns to the extreme right display the settings of the DR-related properties: Kernel Code Lock for Kernel Code I/O Deactivated Memory Deactivated I As there is no DR software installed on the zar1 machine, the columns with the DR-specific parameters are blank. 96 System Administration within a Domain

97 Application-specific actions "Config" application Hardware presentation tab Any component marked as unused by a black colored dot in the hierarchical tree is displayed in gray on the Hardware presentation tab, see system board #6: Figure 84: Unused system board in the Hardware presentation The figure shows a PRIMEPOWER M800 cabinet. System Administration within a Domain 97

98 "Config" application Application-specific actions DR actions The DR action is only available on the Systemboards DR sub-tab. As with other object-specific actions, the DR functions are available in the object-specific menu following selection of the corresponding system board. Because the DR operation takes a number of minutes and is interactive, the ServerView Suite starts the DR operation in a batch job control window, which displays the output of the corresponding DR command and allows the user to answer potential questions. Figure 85: DR batch job control window 98 System Administration within a Domain

99 Application-specific actions "Config" application Disconnect system board The Disconnect action is only available for configured or waiting system boards. After starting the action, the following dialog box is displayed where you can specify further options: immediately the system board is disconnected immediately at next reboot the disconnection is delayed until the next reboot next partition specifies to which partition this system board is to belong in the future. It will be added to the new partition the next time the partition reboots. Figure 86: Dialog box for disconnecting system boards The Disconnect action is only available if the system board has no kernel memory. System Administration within a Domain 99

100 "Config" application Application-specific actions Connect system board Select the system board to be added to the relevant partition, display the objectspecific menu (e.g. right mouse click) and hit Connect. The user can specify in the next dialog box whether the action should be performed immediately or at the next reboot: immediately the system board is connected immediately at next reboot the connection is delayed until the next reboot Figure 87: Dialog box for connecting system boards 100 System Administration within a Domain

101 Application-specific actions "Config" application Move system board The Move action allows the user to move a system board directly from one partition to another. The user can specify in the next dialog box whether the action should be performed immediately or at the next reboot: immediately the system board is connected immediately at next reboot the disconnection is executed when the current partition reboots and the connect is executed when the new partition reboots Note that both partitions have to be rebooted in the specified sequence. next partition drop-down list of all partitions to which the system board may be moved Figure 88: Dialog box for moving system boards Two batch job control windows will pop up in sequence after pressing Ok, the first controlling the disconnection and the second controlling the connection. System Administration within a Domain 101

102 "Config" application Application-specific actions Hardware presentation The configured hardware is presented graphically on the Hardware Presentation tab of the Config application. The type of information displayed depends on what you have selected in the hierarchical browser, i.e. the deeper you go in this hierarchy, the more differentiated the presentation becomes. Two examples should provide an impression of this: Figure 89: Overall hardware presentation for an enterprise server The overall hardware configuration for an enterprise server is shown in this example. The next example shows systemboard 0 of discover-0 node for the same system, i.e. the focussed view of a lower hierarchical level: 102 System Administration within a Domain

103 Application-specific actions "Config" application Figure 90: Hardware presentation of a node s systemboard You will recognize configured hardware modules by their color highlighting in the presentation, where the different colors represent different hardware states (green = object is not faulty etc; for details see the help text). If you position the cursor on a cabinet or on a hardware module configured in the cabinet, a tooltip informs you of the type of cabinet or hardware module in question. By pressing the left mouse button once on an object selected in this way, the input focus is shown in the form of a dotted frame surrounding the cabinet or the hardware module. When the input focus is displayed, you can execute actions on the relevant object by pressing the right mouse button, for example you can change the configuration parameters (of the "hme1" controller in the example). Once you have selected the relevant piece of hardware and initiated the Modify action, the following dialog box opens in our example: System Administration within a Domain 103

104 "Config" application Application-specific actions Figure 91: Dialog box for changing a controller in the hardware presentation Fill in the dialog box in accordance with your requirements and then confirm the changes by pressing Ok. I In the case of hardware modules, which are administered on a different tab (e.g. hard disks), you can execute the same actions under the same conditions at this point as are also possible on the managed tab. 104 System Administration within a Domain

105 Application-specific actions "Config" application Changing the position of a cabinet in the rack Cabinets (or rack mountable cabinets as is the case under the ServerView Suite) that are installed in racks cannot be located automatically. In order to represent the location of such cabinets in the rack correctly, the position must be manually adjusted, i.e. reported specifically to the system. Standard views or defaults are used so that the position of cabinets in racks can be represented in any case in the hierarchical browser and in the Hardware Presentation before this manual adjustment. The next figure shows an excerpt from the hierarchical browser with two such defaults: Figure 92: Browser excerpt with default racks System Administration within a Domain 105

106 "Config" application Application-specific actions The Office domain with the two nodes OfficeServer and WebServer is selected in the excerpt from the hierarchical browser. These two machines are actually located in the same rack. You will see below how this can be displayed in a realistic way. The names of the racks are composed in general according to the following syntax: The (default) rack name appears on the left-hand side before the colon, terminated with a period. This is followed by the (default) position of the cabinet in the rack, which is 1 for defaults (depending on the rack type). The name or ID of the cabinet appears on the right-hand side after the colon. All displays are structured on the basis of this convention. One special feature to note is that the first rack, the primary rack, always takes the name of the node itself (in our example OfficeServer). 106 System Administration within a Domain

107 Application-specific actions "Config" application The overall picture then looks as follows: Figure 93: Sample hardware presentation of two racks with default positioning I The following rule applies for the default representation prior to manual adjustment: The system assumes a separate rack for each installed cabinet. If, for example, you have installed two cabinets in only one rack (as in the example), a second (fictitious) rack is displayed initially as the default in the presentation and in the hierarchical browser. We describe below how to manually adjust the position of the first cabinet in the example. It is assumed that as in the example you are on the Hardware Presentation tab in the Config application. Now click the frame of the cabinet (not an installed device, for example like the power supply!), whose position you want to adjust, and choose the Modify action with the right mouse button. Then choose the Position tab: System Administration within a Domain 107

108 "Config" application Application-specific actions Figure 94: Dialog box for manually adjusting a cabinet position in the rack In the Rack type and Rack name fields in the next dialog box, enter the (freely definable) name and type of the rack in which the cabinet is actually installed. Finally, establish its actual position in the rack in the Cabinet position field. Some racks contain a bar with a scale with the center as the point of origin (no minus entry on the bar!). The digit identifying the position of the lower edge of the cabinet is critical. The lower edge in our example lies at bar position -5 below the point of origin: This is the entry you have to select in the Cabinet position field (if the lower edge were at bar position 5 above the point of origin, you would have chosen +5). You can check in the graphical view whether the position details are realistic. Once you have made your changes in the fields listed above, you can see these in the graphical view by pressing the Apply button. You can test your input in this way before exiting the dialog box with the Ok button and thus store the values in the system. Proceed in the same way to position the second cabinet as described for the first cabinet. 108 System Administration within a Domain

109 Application-specific actions "Config" application After all entries have been adjusted to suit the actual situation, the correct values are displayed in the hierarchical browser and in the hardware presentation: Figure 95: Representation of the cabinet position in the rack following manual adjustment (excerpt) The rack name is now represented correctly as OfficeRack and the position of the cabinets in the rack is also correctly represented as -5 and Identifying the cabling between a SCSI controller and the disk add-on (PRIMEPOWER only) In order to be able to correctly display the location of disks, the cabling to the respective disk tier (cabinet) must be known. This cannot be done automatically in most cases. Instead, a default connection is sometimes displayed. It is easy to check from the hierarchical browser whether cabling is absent because the name of the controller will be missing after the SCSI line. Thus, the name is also missing after the scsi_1 line in the next example (besides the plus sign before the icon), i.e. the cabling information is not available: System Administration within a Domain 109

110 "Config" application Application-specific actions Figure 96: Browser excerpt with no cabling information for SCSI lines The proper connection must be entered if the location is to be displayed correctly in the Hardware Presentation. This is the only way to ensure that the connected devices in a cabinet are displayed at the correct position. You therefore have to manually enter the correct connection in this case or change the defaults. In order to define a SCSI connection manually, first select the relevant controller in the Config application on the Controller tab: 110 System Administration within a Domain

111 Application-specific actions "Config" application Figure 97: Sub-menu for manually identifying a SCSI controller connection Right-click with the mouse and choose the Modify action in the sub-menu to open the next dialog box with the Port tab: System Administration within a Domain 111

112 "Config" application Application-specific actions Figure 98: Dialog box for manually identifying a controller connection On the Port tab in this dialog box, choose both the cabinet and line to which this controller is connected under Connected to. Finally, notify the system of the adjusted connection by pressing Ok. The result is then displayed in the hierarchical browser and in the object table on the SCSI sub-tab: 112 System Administration within a Domain

113 Application-specific actions "Config" application Figure 99: Representation in the hierarchical browser and in the object table following manual identification of the controller cabling Having successfully identified the SCSI controller cabling, the controller name glm1 appears in brackets in the hierarchical browser after the scsi_1 line and the name of the cabinet to which the controller is connected is also displayed in the object table in the Connected to column. Finally, the disks are also displayed in the hierarchical browser under their line. System Administration within a Domain 113

114 "Diagnostics" application Application-specific actions 5.3 "Diagnostics" application System diagnosis The diagnostic system can be configured from the central administration desktop for all nodes in a domain and is used for troubleshooting and diagnostics. Various functions are available for configuration and evaluation purposes. Domain-wide configuration Log administration Among other things, log administration enables the size and number of logbooks to be defined, and components to be assigned to logbooks. Event management Event management allows events and reactions to be defined. All system messages are observed from a monitor. When the defined events occur, the assigned reactions are performed, for example defining a component as defective or information messages for the administration desktop. Domain-wide evaluation Domain-wide evaluation allows all logbooks to be displayed for nodes or their entries. The performance is dependent in this case on the number of nodes and the size and number of logbooks. The system administrator can basically follow two approaches when troubleshooting: 1. General troubleshooting across all nodes in a domain 2. Object-specific troubleshooting for a specific error message The first approach is demonstrated below using an example. 114 System Administration within a Domain

115 Application-specific actions "Diagnostics" application General troubleshooting System administrators must be able to analyze and resolve errors quickly when they occur. One method of reducing the particularly large volume of information in the various logbooks in the administration domain is to use search criteria. Two options are available to you in this case: the selection configurator and the filter action. In the selection configurator (see the description on page 30 earlier) as is also the case with the other applications it is only possible to specify a search criterion plus an operator, in order to search, for example, throughout a domain for all log entries with a specific weighting or for messages from a particular driver. However, the following example uses two criteria (time period and weighting), in order to reduce the result set further. A filter is needed for this purpose. Regardless of the object, the filter action allows serious errors to be sought specifically for a defined period. For example, a system administrator may want to view the most important errors (from EMERGENCY to WARNING), which have occurred in a domain within the last 24 hours. The example assumes a single domain, which comprises the two nodes "OfficeServer" and "WebServer". Since you may want to record all serious errors that occur in the domain, select the top item in the hierarchical browser with the name of the root domain. You can then use the LogEvaluation tab and the Filter function to open the dialog box where you can specify the filter: System Administration within a Domain 115

116 "Diagnostics" application Application-specific actions Figure 100: Object-independent filter Only the key data for the time period and the error weighting is shown in this object-independent filter. The period covers 24 hours and the weighting is set to less than or equal to (<=) WARNING, i.e. all errors that require a reaction soon or immediately. I You are shown the precise format for the date fields by dragging the cursor to the Date (From) entry. When you exit the dialog box with Ok, all hits are shown in the object list: Figure 101: Object list with faulty devices based on a filter 116 System Administration within a Domain

117 Application-specific actions "Diagnostics" application In our example, one faulty object was found on one domain node: a defective fan on the node "WebServer". You can now display the detailed log entry by double-clicking one of the objects: Figure 102: Log evaluation for a faulty fan A log entry is shown with an error description in the Message Text field. It is advisable at this point to switch to the Config application, Hardware Presentation tab, to find additional information about the defective device. The "WebServer" node is highlighted by a red dot in the hierarchical browser of this application to indicate that there is a defective device. If you select this node, you will be shown a graphical representation of the cabinet containing the defective fan. The fan itself is likewise highlighted in red. If you double-click this object, a dialog box opens containing a specification of the error: System Administration within a Domain 117

118 "Diagnostics" application Application-specific actions Figure 103: Cabinet with a defective fan in graphical form as well as a dialog box showing the HW status Event and reaction definitions Event Management uses messages and the frequency with which they occur to define events and trigger reactions in accordance with these events. For example, if you want to take up the option of receiving all system disruptions or warnings throughout the domain by , you have to proceed as follows: 1. Create an event definition. 2. Clone this event definition. 3. Create a reaction definition. 4. Clone this reaction definition. 5. Activate the modified event and reaction definitions. These steps are now illustrated individually using the following example. Step 1: Create event definition Ê Select a suitable entry in the Unit:Event Name column in the object list (in the example: FJSVcsl:FJSVcsl Alarm Message) and right-click it. 118 System Administration within a Domain

119 Application-specific actions "Diagnostics" application The following sub-menu appears: Figure 104: Object list for creating an event definition (excerpt) Ê Click Generate. The following dialog box is displayed: Figure 105: Dialog box for creating an event definition System Administration within a Domain 119

120 "Diagnostics" application Application-specific actions Ê A combination of unit and event name that does not already exist must now be assigned in this dialog box for the Unit:Event Name entry, in our example user:mail-event. All other fields can be accepted unchanged, modified or deleted. For better clarity, our example shows the entry SMAWlog3:Mail to root in the Reactions field as the unit and reaction name and the flag WARNING: in the Message Text field. Click Ok to exit the dialog box. You will now find the new event definition user:mail-event in the object list. Step 2: Clone event definition You have to clone the event definition to transfer it to other systems in the domain. To do this, proceed as follows: Ê Ê Select the entry you just created in the Unit:Event Name column in the object list (in the example: user:mail-event). Now click the Clone action. A dialog box opens where you have to select the destination nodes: Ê Figure 106: Dialog box for cloning an object After you have selected the required node (in the example: zar1), click Ok to exit the dialog box. You will then find the new event definition user:mail-event for all required destination nodes in the object list. 120 System Administration within a Domain

121 Application-specific actions "Diagnostics" application Step 3: Create reaction definition Ê Ê Change to the tab-bar Reactions. Choose a suitable entry in the Unit:Reaction column in the object list (in the example: SMAWlog3:Mail to root) and right-click it. The following sub-menu appears: Figure 107: Object list for creating a reaction definition (excerpt) Ê Click Generate. The following dialog box is then displayed: Figure 108: Dialog box for creating a reaction definition The only fields to edit in this case are Unit:Reaction and Command. System Administration within a Domain 121

122 "Diagnostics" application Application-specific actions Enter user:react-mail in the Unit:Reaction field as the unit and reaction name. Enter the log3mail reaction program in the Command field with the -w and -A options. The -w option causes a mail to be sent to a recipient in the network without waiting for the transfer program to terminate. The -A option requires the user id of the mail recipient as an argument, in our example this is the user root. Ê Click Ok to exit the dialog box. Step 4: Clone reaction definition The reaction definition must also be cloned if it is to be transferred to other systems in the domain. To do this, proceed as described in Clone event definition on page 120. Step 5: Activate modified event and reaction definitions The following steps are required to activate the newly created event and reaction definitions: Ê Ê Change to the tab-bar Events. Click the Activate action. The following dialog box is displayed: Ê Figure 109: Dialog box for activating event/reaction definitions Click Ok to activate the newly created event and reaction definitions. This completes all necessary steps. The new events will now also be monitored and will trigger the required reactions where necessary. 122 System Administration within a Domain

123 Application-specific actions "Software" application 5.4 "Software" application Checking software versions One of the system administrator s main tasks is to maintain the software used. The system administrator therefore has to ensure, for example, that all packages required on the respective systems are available in their current versions. This includes verifying that the same versions are being used on all nodes in a domain to avoid the individual nodes behaving differently. For this purpose, the Software application offers various options to ensure simple administration of the software used. Therefore, if you want to know, for example, whether the same version of a particular package is used on all nodes in the domain, you can establish this as follows: 1. Select the entire domain in the hierarchical browser (click the name of the root domain). 2. Specify the abbreviated form of the required package (see the Pkginst attribute) in the search field of the selection configurator (in the example: SMAWlog3) and click the icon: Figure 110: Searching for installed packages As a result, the example shows an object list with ten packages, which are available with identical versions on all systems: Figure 111: Targeted selection of installed packages System Administration within a Domain 123

124 "Software" application Application-specific actions Checking the packages for consistency The second step involves selecting two packages and checking them for consistency. This is how you do this: Ê Ê Select the packages to be checked in the object list. In the menubar, click the Packages option and choose the Check... action. Figure 112: Menu for checking packages 124 System Administration within a Domain

125 Application-specific actions "Software" application The following dialog box is displayed: Figure 113: Dialog box for checking software packages Choose the options you require from those listed. I The two options Check file attributes and Check file contents are already selected by default. Ê Start the checking process by clicking Ok. A progress indicator in the form of an increasing bar as well as a percent figure show how advanced the checking process is. System Administration within a Domain 125

126 "Software" application Application-specific actions As soon as the checking process is complete, a dialog box is opened containing the result of the checks: Ê Figure 114: Dialog box with the result of a package check I If errors are listed here (e. g. incorrect access rights), you can resolve these if appropriate in a further check run by choosing the Correct known inconsistencies option in the dialog box. Click Ok to exit the dialog box. The checking of packages is now complete. 126 System Administration within a Domain

127 6 Event Management (Alarm Service) The Alarm Service function has a web-based graphical user interface (GUI) where you can obtain reliable, secure information about system faults very rapidly. This user interface can be started in a browser completely independently of the ServerView Suite system. The Alarm Service is based on the analysis of SNMP traps, whose MIBs are available in a special format and are integrated. Before the SNMP traps are displayed as events, filters are evaluated, which define whether and how an event is to be displayed. In addition to the display within the Alarm Service, events can be forwarded (e.g. as , SMS or SNMP traps) and programs can be started for further processing these events. 6.1 Integrating third-party MIBs under Linux Third-party MIBs can be integrated as follows in the Alarm Service under Linux: Ê Ê Ê Ê Stop the SVForwardServer service: # /etc/init.d/sv_fwdserver stop Stop the trpsrvd service: # /etc/init.d/trpsrvd stop Copy the MIB to the directory <installdir>/cgi-bin/serverview/common/mibs <installdir> is /var/www for RHEL and /srv/www for SLES. Then restart the SVForwardServer service: # /etc/init.d/sv_fwdserver start and finally the trpsrvd service: # /etc/init.d/trpsrvd start System Administration within a Domain 127

128 Software requirements Event Management (Alarm Service) 6.2 Software requirements Management server The trap port 162 is occupied by the trap distributor on the management servers. Other applications that require this port have to register with the trap distributor. Agent systems (Solaris only) In order to allow the events of the agent systems to be sent via a trap also, the appropriate EMANATE Master Agent (Version 1.5A0ff) must be installed. Because this product requires at least Solaris 7 (licensing reasons), Solaris 2.6 systems cannot be considered for the Alarm Service! Other systems Other systems (SAN devices, Linux, Windows-based PCs, "Native Solaris" servers) must be configured to send their traps to the system identified as management server. These server systems then send the traps also to the Alarm Service. 6.3 Installation/configuration The Alarm Service is installed automatically when the ServerView Suite is installed. The service is started by activating it. It then configures itself autonomously in the trap distributor and reads the participating systems from a local server list, which is a textual representation of the domain configuration. 128 System Administration within a Domain

129 Event Management (Alarm Service) Starting the Alarm Service 6.4 Starting the Alarm Service You can start the interface for the Alarm Service via an icon on the start screen of the ServerView Suite: Figure 115: Icon for starting the interface of the Alarm Service Apart from the icon on the start screen, you can also start the interface by entering an URL in a browser. The URL for the Alarm Service on a management server is: Both ways of starting the interface for the Alarm Service have the same merit. 6.5 Alarm Service components The Alarm Service has the following components: Alarm Manager Use the Alarm Manager to display and edit all the events recorded in the log file, see the section Alarm Manager on page 130. Alarm Monitor Use the Alarm Monitor to display all the traps received, see the section Alarm Monitor on page 133. Alarm Settings Use the Alarm Settings function to configure the alarm settings. You can, for example, assign alarm actions to an alarm or define a target to which the alarm is to be sent, see section Alarm settings on page 139. System Administration within a Domain 129

130 Alarm Service components Event Management (Alarm Service) Alarm Manager Use Alarm Manager to display, edit and manage all the events recorded in the log file. After starting Alarm Manager the following window opens: Figure 116: Alarm Manager 130 System Administration within a Domain

131 Event Management (Alarm Service) Alarm Service components Count of alarms displays the current alarm entries in the Alarm Manager (listed) and the total number of logged alarms (available). The display update in the Alarm Manager can be enabled or disabled via Automatic refresh. If Automatic refresh is marked, the display is reloaded automatically when an alarm is logged. Otherwise, only the display of logged alarms for Count of alarms available changes. Since some browsers do not support multiple or single selection, a depressed [Shift] or [Ctrl] button can be simulated. Mark either Shift pressed or Ctrl pressed. The alarm overview shows the Receive Time, Alarm Type, Severity, Server, Forwarded to and Acknowledge. A short text message (from the corresponding MIB) appears under Alarm Details. This message describes the selected alarm in more detail. The user can enter a short note under Alarm Note/Action giving more information about the alarm. Use Save to save this information. Use the Filter Settings button to open the Setup Alarm Filter window in which you can define new filter settings: Select Server The alarms are filtered for the selected server. Select Severity The alarms are filtered according to severity. There are two options; alarms that are less than or equal to the specified level of severity and alarms that are greater than or equal to that level. Alarms The alarms are filtered according to status: still open or acknowledged. Time The alarms are filtered according to time. The alarms may be older or younger than the time specified. Open Pagers The alarms are filtered by open pager messages. Open Mgmt Stations The alarms are filtered by open alarms that have sent traps to other management server. The Enable Filter and Disable Filter buttons respectively activate or deactivate the filter settings for the alarm. System Administration within a Domain 131

132 Alarm Service components Event Management (Alarm Service) You can carry out the following actions using the buttons: Alarm Info Opens a window containing detailed information about the alarm from the MIB. Print Delete Prints the alarm list. Deletes all selected alarms. You must acknowledge critical alarms before deleting them. Select all Selects all alarms. AckAlarm Acknowledges all alarms. AckPager The user closes the open pager. AckStation The user closes the open station. Close Save Closes the Alarm Manager window Saves the note under Alarm Note/Action for the selected server in the alarm log. Alarm Actions Opens the Overall Settings window. In this window you can edit alarm actions on the Alarm actions tab and the number of entries in the log list on the Alarm manager tab (see section Making settings on page 140). 132 System Administration within a Domain

133 Event Management (Alarm Service) Alarm Service components Alarm Monitor The Alarm Monitor is used to display all received alarms. After starting the Alarm Monitor the following window opens: Figure 117: Alarm Monitor System Administration within a Domain 133

134 Alarm Service components Event Management (Alarm Service) Under Count of alarms listed you can enter the number of alarm entries that are to be displayed. By entering all all available alarm entries are output. The input is activated with Set. The number of all logged alarms is displayed with available. first displayed indicates the current page. Use the Set button to set the number of entries that will be shown at the same time in the Alarm Monitor window. The default setting is 30 entries; the minimum permitted number of entries is 10. I You should keep the number of entries per page as low as possible so as not to slow performance. Use the Automatic refresh checkbox to select/deselect automatic updating of the Alarm Monitor display. If the Automatic refresh checkbox is selected, the display will be automatically updated each time a new alarm is received. If this checkbox is not selected, only the number of alarms in the Count of alarms available field will be updated. Some browsers do not support multiple or single selections. For these cases you can simulate the [Shift] pressed down and [Ctrl] pressed down keys by selecting the Shift pressed or Ctrl pressed check boxes as required. Page m of n indicates the number of the page currently displayed and the total number of pages. The display changes according to the number set in the Count of alarms listed field. You can scroll through the page listed. The alarm overview displays the current status of Receive Time, Alarm Type, Severity, Server and Forwarded to for the current alarms. The overview also shows if the alarm has been acknowledged (Ack) or logged (Log). Alarm Details contains a short text (from the appropriate MIB) which provides more detailed information about the selected alarm. The following actions can be carried out using buttons: Alarm Info Opens a window containing more detailed information about the alarm from the MIB. Log Writes the selected alarms to the Log list. Print Prints the alarm list. Delete Deletes the selected alarms from the alarm list. 134 System Administration within a Domain

135 Event Management (Alarm Service) Alarm Service components Select all Selects all alarms. Suppress Suppresses the selected alarms reported by selected servers. This is meaningful if the management server is swamped with messages by a server that is not running correctly. Reset Filter Resets the filter settings. Close Closes the Alarm Monitor window. Alarm Manager Calls the Alarm Manager, with which you can view and edit the alarms in the log list (see section Alarm Manager on page 130). Alarm Actions Opens the Overall Settings window. In this window you can edit alarm actions on the Alarm actions tab and the number of entries in the log list on the Alarm manager tab. Test trap Opens the Test Trap window in which you can select the server which shall send a trap to the Alarm Service to test the connection. Use the Test trap button to start the test. Selection Wizard Opens the Alarm Monitor Selection Wizard where you can set the contents of the alarm list to be displayed (see the section Managing the Alarm List on page 136). Server Info Opens the Server Information window displaying information about the server which is the source of the alarm entry selected (see the section Displaying server information on page 138). If you select several alarm entries for various servers, the system will display information about all the servers concerned. System Administration within a Domain 135

136 Alarm Service components Event Management (Alarm Service) Managing the Alarm List In the Alarm Monitor window, select the Selection Wizard button to call up the Alarm Monitor Selection Wizard window. Use this window to manage the contents of the alarm list. Figure 118: Alarm Monitor Selection Wizard The field Count of alarms selected indicates the number of alarms selected for the alarm list. The display depends on the values set in this field. The field Count of alarms available indicates the number of alarm messages received by the Alarm Service. You can select the alarm messages for display in the alarm list using the following four properties: Alarm type (Select Alarm Type) Server (Select Server) Date (Select Time) Alarm severity level (Select Severity) You can combine these selection criteria as required. 136 System Administration within a Domain

137 Event Management (Alarm Service) Alarm Service components Use the buttons listed here to perform the actions described: Close Closes the Alarm Monitor Selection Wizard window. Alarm Info Opens a window displaying detailed information about a selected alarm from the MIB. You can select several alarms and obtain information about all the alarms you select. Log Writes the selected alarm messages to a log file. Delete Deletes the selected alarm messages from the alarm list. Suppress Suppresses the selected alarms reported by selected servers. This is meaningful if the management server is swamped with messages by a server that is not running correctly. Server Info Opens the Server Information window and displays information about the server which is the source of the selected alarm entries (see the section Displaying server information on page 138). If you select several alarm entries for various servers, the system will display information about all the servers concerned. System Administration within a Domain 137

138 Alarm Service components Event Management (Alarm Service) Displaying server information To display detailed information about the server which is the source of an alarm message, go to the Alarm Monitor or the Alarm Monitor Selection Wizard window and click the Server Info button. This will open the Server information window. If you select several alarm entries for various servers, the system will display information about all the servers concerned. Figure 119: Server information The header gives the server name accompanied by a status icon which indicates the current server status. Underneath the status icon there is another icon which indicates whether or not the server is entered in the server list: The server is known, i.e. the server is present in the ServerView server list. The server is unknown, i.e. the server is not present in the ServerView server list. 138 System Administration within a Domain

139 Event Management (Alarm Service) Alarm Service components If the server is in the server list, the server information will be displayed. If the server is not in the server list but has the current status manageable, the Alarm Service will obtain the information directly from the server itself. I You are able to start ServerView S2 for the selected server in this window. To do this, click the status icon in the top right-hand corner. The status display, the server picture and the start command for ServerView S2 are only enabled if ServerView S2 is already installed. To close the Server information window, click the Close button Alarm settings Use the Alarm Settings function in the Alarm Service to define how alarms will be handled. In the Start Alarm Settings window you can select the following options: Use Wizard Default value. The wizard guides you through the individual windows used to set the alarm parameters. Overall Settings Use this to define the overall settings for alarm handling. This opens the Overall Settings window, see section Making settings on page 140. Filter Server This allows you to hide the servers you do not wish to receive alarm messages from. This opens the Filter Server window, see section Filtering servers on page 141. Edit / New Alarmgroup This allows you to define a new alarm group or to edit an existing alarm group. This opens the Edit / New Alarmgroup window, see section Editing alarm groups on page 142. Set / Edit Destinations This allows you to define the settings for forwarding alarms. This opens the Set / Edit Destinations windows, see section Forwarding alarms on page 143. Overview of all Groups Opens the Overview window and displays an overview of all the defined alarm groups; see the section Overview of alarm definitions on page 147. System Administration within a Domain 139

140 Alarm Service components Event Management (Alarm Service) To start, click the Go button. The Exit button closes the window and returns the user to the start window Start Alarm Settings. Buttons The following buttons may be available in the various windows: Next Back Apply Displays the next window. Goes back to the previous window. Confirms and applies the changes you have made. Finish Takes you back to the Start Alarm Settings window. Print Preview Prints the current settings for the relevant window. Help Calls the online help system Making settings In the Overall Settings window you can define the general settings for the handling of alarms. Tab Filter Settings You can define the following filter settings: Set time for repetition in sec Makes a time specification which defines when the same alarm will be permitted again. Filter unknown alarm Filters out unknown alarms. Filter unknown server Filters according to unknown servers. Filter severity <severity> Filters according to the severity of the error. 140 System Administration within a Domain

141 Event Management (Alarm Service) Alarm Service components Tab Delete alarm Specifies when an alarm is to be deleted. The alarm can be deleted when it has reached a specified age, or when a specified number of entries have been made in the Log list. Tab Alarm actions Actions for which incoming alarms are to be triggered. For each of the error categories, you can set whether the entry is to be saved in the Log list and whether a message is to be output. Any combination is possible. Critical errors are always written to the Log list. Tab Alarm manager Here you specify the maximum number of entries that can be written to the Log list and what is to happen when this number has been reached. Pop up warning A message is output. Wrap around System overwrites the oldest entry. Tab Default alarm handling Here you define the action which should by default be instigated in response to an alarm. Pop up a message A message is issued. Store in event log Depending on the system, the alarm is written to the relevant event log Filtering servers In the Filter Server window, you can specify the servers from which the alarms are to be filtered. If the Alarm Service is running on a server and no other servers are entered in the server list, the server is shown as the local host. If this is the case, no additional settings are required. Otherwise all the servers in the server list are shown in the Server List window. You can use the buttons >>> and <<< to select the required server. You can only select one server at a time. Click the Info button to obtain additional information about the server. System Administration within a Domain 141

142 Alarm Service components Event Management (Alarm Service) Editing alarm groups In the Edit / New Alarmgroup window, you can define a new alarm group or edit an existing one. An alarm group is a group of servers and the alarms for this group. For these alarm groups you can specify the reaction to these alarms in the case of specific alarm messages for the servers of the alarm group (see section Forwarding alarms on page 143). To define an alarm group, enter the name of the new group. To edit an existing alarm group, select it from the list of alarm groups. Tab Select Group Here you define the alarm group you would like to edit. Either enter a new group or choose the relevant group from the list. Tab Select Server Use this function to select the servers to be assigned to this alarm group. If the Server of alarm group list is left empty, all the servers (and not only the known servers) will be added to the alarm group. To display an overview of all the servers which have not yet been assigned to an alarm group, select the All button under Known Server. >>> <<< all > < all Info The selected server is added to the alarm group. The selected server is removed from the alarm group. All known servers are added to the alarm group. All known servers are removed from the alarm group. This displays the additional information for the selected server. 142 System Administration within a Domain

143 Event Management (Alarm Service) Alarm Service components Tab Select alarms Here you define the alarms for the alarm group. The selection of the alarms can be filtered in accordance with Severity, Name, File or Source. Additional values are then displayed in the selection list. For example, if you choose Severity, the question weightings are displayed in the list, which you can then select. >>> <<< all > < all Info The selected alarm is added to the alarm list. The selected alarm is removed from the alarm list. All alarms shown are added to the alarm list. All alarms shown are removed from the alarm list. Shows additional information about the selected alarm. Deleting Alarm Groups Use the following method to delete an alarm group: Ê Ê Select the name of the alarm group from the list, or enter the name by hand. Then click the Delete button to delete the alarm group Forwarding alarms In the Set / Edit destinations window you can make settings used to forward alarms. Select an alarm group and then define the actions to be triggered for the servers of this alarm group in the case of specific alarm messages. The actual process of forwarding alarms can be activated or deactivated using the Enabled button. You can specify which of the following are to be implemented for the alarm group: send mail (Mail) output message (Popup) log alarm (Logging) trigger call to a pager or mobile phone (Pager) start an executable program (Execute) System Administration within a Domain 143

144 Alarm Service components Event Management (Alarm Service) trigger a broadcast message (Broadcast) create a trap, which is forwarded to another management server (Station) Depending on the selection you make here, additional windows may be displayed where you must define further settings. For a detailed description of the windows, click the Help button. For more information on mail forwarding, see section General mail forwarding on page 144, section Forwarding mails to the service provider on page 144, and section COM port & modem settings on page General mail forwarding Mail settings When you select the Mail option for forwarding alarms, the Mail Settings window will appear containing predefined mail settings. Select button Properties to enter the Mail Properties (SMTP) window and fill in the fields From with the mailing address (e.g. "Sender@company.com"), SMTP Server with the SMTP server name and Port with the SMTP port number (default: 25). McAfee virus scanner The McAfee virus scanner contains a setting which prevents programs from sending s if they are not registered. To register the mail senders, you must enter the corresponding program name: blat.exe under Windows or smtpm under Linux Forwarding mails to the service provider ServerView offers the option of automatically forwarding ServerView alarms by to the service provider. The service provider can specify which traps are to be forwarded to it. If the mail forwarding to a service provider function is enabled, the service provider will be informed by whenever a certain trap occurs. The service provider can edit the group of traps that trigger an System Administration within a Domain

145 Event Management (Alarm Service) Alarm Service components Activating the mail forwarding function You activate mail forwarding to the service provider in the window Set / Edit Destination, by selecting the alarm group Automatic Service Mail. If you click the Mail button, you can make the necessary settings for mail forwarding to the service provider in the Service Mail Settings window. The input fields in the Service Mail Settings window have the following meanings: Name Mail To Cc Identnumber Meaning address of the Service Center The address to which a copy of the Service mail is to be sent (optional) Unique ID number of the server I This number must be agreed with the service provider. Name Phone Name of the server administrator Telephone number of the server administrator address to be used by the Service Center for queries (optional). Table 4: Input fields in the Service Mail Settings window If you click the Properties button, you can specify additional information on the mail service in the Mail Properties (SMTP) window. From Some mailing systems or special settings of them require a user name or From address to find/declare the right mailing. The From address has to contain the complete address including the domain. For example: "Sender@company.com". SMTP Server The mailing system needs to know the SMTP Server. Port The default Port for SMTP is 25; if you use another one change the portnumber in this field. System Administration within a Domain 145

146 Alarm Service components Event Management (Alarm Service) If you click the Test Address button in the Service Mail Settings window, a test mail is sent to the service provider. The Service Center sends an automatic response to all test mails it receives. In doing so it uses the address specified in the input field. A minimum time period of 600 seconds has been specified for the sending of the identical mails. This ensures that redundant messages are not sent. In the Alarm Monitor, traps that have triggered a service mail are identified in the following manner: This icon identifies a trap that has been forwarded using the service mail function. This icon identifies a trap that has been forwarded using both the normal mail function as well as the service mail function COM port & modem settings In the COM Port & Modem Settings window you specify the settings for the serial interface and the modem connected to this interface. You open the window by: selecting pager forwarding with Pager in the Set / Edit destination window, selecting the function New or Edit in the Set / Edit pager for group <groupname> window, selecting COM & Modem in the Pager Settings window. You can set the following values: The name of the interface available (e.g. COM2 or COM4) The maximum transmission speed (baud rate) The type of data flow control The initialization and reset string for the modem You can also specify which pager service will be dialed: the pager, SMS1 or SMS2. You set the number of data bits, parity and number of stop bits for each service number, and you define the prompt to be used by the pager when it responds. Two services, SMS1 and SMS2, with different protocols can be used to call a GSM mobile telephone. SMS1 uses the Telocator Alphanumeric Protocol (TAP), SMS2 uses the Universal Computer Protocol (UCP). 146 System Administration within a Domain

147 Event Management (Alarm Service) Alarm Service components Baud rate 2400 bps, 1200 bps or 300 bps Data bits 8 Parity none Stop bits 1 Dialing prefix ATDP0,01691 Table 5: Settings for the serial interface I Once you have specified the settings for the serial interface, you can specify whether an alarm should trigger a call to a pager or mobile telephone (see also section Forwarding alarms on page 143) Overview of alarm definitions The Overview window provides an overview of the alarm definitions. This display depends on the sorting order selected under Select root. The Enabled button will be highlighted depending on the settings made previously in the Set / Edit destinations window. System Administration within a Domain 147

148 Alarm Service components Event Management (Alarm Service) Icons You will find a list of the icons in the Alarm Manager and Alarm Monitor windows and their meanings in the following. Red alarm: critical Pink alarm: major Yellow alarm: minor Blue alarm: informational White alarm: unknown The alarm was confirmed by a user entry. Some other executable program was triggered by this alarm. A broadcast message was sent for this alarm. A mail was sent for this alarm. This alarm triggered a pager call. This alarm will be passed on to a management server This alarm will be passed on to the local system event log. The alarm is stored in the database Green: Pager confirmed Yellow: Pager completed Red: Pager present (still active) Green: Forwarding confirmed Yellow: Forwarding completed Red: Forwarding present (still active) Table 6: Meaning of the icons in the Alarm Manager and Alarm Monitor windows 148 System Administration within a Domain

149 Event Management (Alarm Service) Displaying trap information 6.6 Displaying trap information The Alarm Service help system provides detailed information about the default MIBs and traps supported by the Alarm Service. To display this information, start the Alarm Service and then click the Help button. Under Alarms, select the Agent Alarm Information option. The following window providing an overview will be displayed: Figure 120: MIB overview in the Alarm Service - example System Administration within a Domain 149

150 Displaying trap information Event Management (Alarm Service) When you select a MIB, a window with detailed trap information will open; the window will look like this: Figure 121: Detailed information about the traps from a MIB (example) If you want to print out this information, use the Print button in this window. 150 System Administration within a Domain