Server Management Agent for Linux User s Guide Server Management 2.0 and Higher March 2008
.
unisys imagine it. done. Server Management Agent for Linux User s Guide Server Management 2.0 and Higher March 2008 3839 6420 003
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data rights clauses. Unisys is a registered trademark of Unisys Corporation in the United States and other countries. All other brands and products referenced in this document are acknowledged to be the trademarks or registered trademarks of their respective holders.
Trademarks and copyright * Linux is a registered trademark of Linus Torvalds in the United States and other countries. * Red Hat is a registered trademark or trademark of Red Hat, Inc. in the United States or in the other countries. * VMware and ESX Server are registered trademarks or trademarks of VMware, Inc. * All other product and company names are trademarks or registered trademarks of their respective owners. Names used in sample application are all fictitious. They are not related to the names of real products, corporations, or people. 3839 6420-003 i
3839 6420-003 ii
CONTENTS 1. Products Overview: Server Management Manager & Server Management Agent... 1 1.1. Detection of Server Failures... 2 1.2. Management of Server Operating Statuses... 3 1.3. Central Management of Distributed Servers... 4 2. Installation... 5 2.1. Preparation before Setup... 5 2.2. Installation procedure... 7 2.3. Uninstallation procedure... 8 2.4. Silent Installation... 9 3. Monitoring Functions... 13 3.1. General Properties... 14 3.2. CPU Load Monitoring... 15 3.3. Syslog Monitoring... 17 3.4. Storage Monitoring... 18 3.5. File System Monitoring... 21 3.6. Network (LAN) Monitoring... 22 4. Report Setting Function... 25 4.1. Flow of Report Setting... 26 4.2. Base Setting... 27 4.2.1. Setting of Report Method... 28 4.2.2. Other Setting... 30 4.3. Destination Setting... 31 4.3.1. Changing the Setting of Destination IDs... 32 4.3.2. Adding Destination IDs... 36 4.4. Agent Events Setting... 37 4.4.1. Setting Destination (Agent Event)... 38 4.5. Syslog Events Setting... 40 4.5.1. Setting Destination (Syslog Event)... 42 4.5.2. Adding of Syslog Monitoring Event Sources... 44 4.5.3. Adding of Syslog Monitoring Events... 46 4.5.4. Deleting of Syslog Monitoring Event Sources... 47 4.5.5. Deleting of Syslog Monitoring Events... 48 Appendix A... 49 NOTE... 49 3839 6420-003 iii
3839 6420-003 iv
1. Products Overview: Server Management Manager & Server Management Agent Server Management Manager and Server Management Agent are software packages for server management aimed at the stable operation and the efficient management of servers. This software tracks configuration information and operation statuses of the server resources, detects server failures, and reports the alert to the system administrator, to prevent or quickly respond to such failures. Importance of server management To ensure stable server operations, you need to reduce the workload for server management. Stable server operations Server shutdowns directly lead to a loss of your business opportunities and profits. Therefore, you always need to ensure complete operations. In case of a server failure, you will have to notice it as early as possible to track down the cause and take necessary measures. If you quickly recover the system from the failure, you ll be able to minimize profit (cost) losses. Reduction of the workload for server management It takes a large workforce to manage servers, especially in a large system or when using servers in a remote location. Reduction of the workload for server management leads to cost reduction. What are Server Management Manager and Server Management Agent? Server Management Manager and Server Management Agent are server management software packages that manage and monitor servers on the network. If you introduce this software, you will be able to obtain/manage/monitor information on configuration, performance, and failures. In addition, you will be able to notice a failure by notification from the reporting function on a real-time basis. Effectiveness of Server Management Manager and Server Management Agent Server Management Manager and Server Management Agent are very effective for various needs within a system environment that is getting increasingly diversified and complicated. Detection of server failures Server Management Agent collects a variety of failure information and checks system statuses. When it detects an abnormality, it reports the alert to Server Management Manager. Prevention of server failures Server Management Agent supports a preventive maintenance function that predicts failure occurrences. Central management of distributed servers Server Management Manager offers GUI interfaces that allow you to efficiently manage servers distributed on a network. 3839 6420-003 1
1.1. Detection of Server Failures Server Management Manager and Server Management Agent detect an abnormality that can lead to a failure at an early stage and send failure information to the administrator immediately. In case of a failure, Server Management Agent detects it and reports the alert to Server Management Manager. Then, Server Management Manager displays the received alert in the Alert Viewer and changes the status colors of the server or its components so that you can identify the failure location at a glance. Furthermore, you can respond to failures quickly by referring to the description of the failures and the appropriate actions. 3839 6420-003 2
1.2. Management of Server Operating Statuses Server Management Agent manages and monitors various server components. You can use Server Management Manager s Data Viewer to access information that is managed and monitored by Server Management Agent. 3839 6420-003 3
1.3. Central Management of Distributed Servers Server Management Manager provides outstanding GUIs to centrally manage distributed servers on the network. Its Explorer-style screen displays components in a hierarchical manner so that you can manage servers efficiently. Central management of servers To manage servers, Server Management Manager uses the following types of GUIs: Operation Window It creates and manages a map of servers connected on a network. You can make hierarchical maps based on setup locations, organizations, or purposes. DataViewer It displays server resource components in an Explorer style. It changes the status colors of abnormal server components so that you can easily identify failure locations. Alert Viewer It manages failure alerts from all servers in a unified manner. It receives alerts immediately when a failure occurs in a server so that you can notice any failure on the network instantaneously. 3839 6420-003 4
2. Installation 2.1. Preparation before Setup 1. Check necessary packages The following packages are needed to use Server Management Agent. If there are any packages that are not installed, install them. [SUSE LINUX Enterprise Server9 SP3] and [SUSE LINUX Enterprise Server10] - net-snmp (a) - net-snmp-devel (a) - newt (b) - newt-devel (b) - portmap - slang - slang-devel - compat-libstdc++ (a) The net-snmp and net-snmp-devel package require a version 5.1.3.1-0.13. (b) The newt and newt-devel package require a version higher than 0.51.6-5. [Red Hat Enterprise Linux AS 4 Update3 or more] and [Red Hat Enterprise Linux AS 5] - net-snmp - net-snmp-devel - net-snmp-utils - newt - newt-devel - portmap - slang - slang-devel - compat-libstdc++ [VMware ESX Server 3] - net-snmp - net-snmp-utils - newt - portmap - slang - compat-libstdc++ 2. Environment settings of snmpd Modify the environment setting file of snmpd (snmpd.conf) to set a community privilege to "READ WRITE. Edit the environment setting file using vi commands, etc. For details of the settings, see the online manual for snmpd.conf. 3839 6420-003 5
The path for the snmpd.conf file is different depending on your distribution. SLES9, SLES10 : /etc/snmpd.conf RHEL4, RHEL5, VMware ESX Server 3 : /etc/snmp/snmpd.conf 3. snmpd start setting Execute the following command so that the snmpd service starts automatically. # /sbin/chkconfig snmpd on 4. portmap start setting Execute the following command so that the portmap service starts automatically. # /sbin/chkconfig portmap on Execute the following command to start portmap. # /etc/init.d/portmap start 5. Setting firewall When the firewall is enabled, you need to open ports used by Server Management Manager and Agent. Refer to "7. Ports used by Server Management Manager and Agent" in section "5. Notes" for details of the setting. 6. Setting SELinux (RHEL4 and RHEL5) Server Management Agent uses snmpd. Execute the following commands and disable the limitation of snmpd if SELinux is enabled. # setsebool -P snmpd_disable_trans 1 # /etc/init.d/snmpd restart Confirm the status of SELinux is "enabled" by executing the sestatus command. # sestatus -v SELinux status: enabled : : 3839 6420-003 6
2.2. Installation procedure The following describes the procedures for installing the Server Management Agent alone. For the installation procedures as a part of the Unisys Server Management System, refer to the Server Management 2.0 Installation and Configuration Guide (8216 3452). 1. Log in to the system as the root user. 2. Set the installation CD-ROM to the CD-ROM drive. 3. Execute the following command to mount the CD-ROM. In this example, the mount point is assumed to be "/media/dvdrecorder. # mount /media/dvdrecorder 4. Execute the following command to install the package. The command that you execute is different depending on your distribution. Except the ES3000 on SLES9, SLES10, RHEL4, RHEL5 # /media/dvdrecorder/sma/linux/smainst.sh -i Except the ES3000 on VMware ESX Server 3 # /media/dvdrecorder/sma/linux/smainst_vmware.sh -i For the ES3000 on SLES9, SLES10, RHEL4, RHEL5 # /media/dvdrecorder/sma/linux/smainst.sh -ip For the ES3000 on VMware ESX Server 3 # /media/dvdrecorder/sma/linux/smainst_vmware.sh -ip 5. Execute the following command to unmount the CD-ROM. # umount /media/dvdrecorder 6. Execute the following command and confirm whether the package was correctly installed. Except the ES3000 # rpm -qa grep Esmpro-common For the ES3000 # rpm -qa grep Esmpro-common # rpm -qa grep Esmpro-type3 7. Execute the following commands for setting up system information. (Product name, model name, and chassis type) # cd /opt/nec/esmpro_sa/tools #./sethwinf 8. Restart Server Management Agent. # sync # /opt/nec/esmpro_sa/bin/esmrestart 3839 6420-003 7
2.3. Uninstallation procedure 1. Log in to the system as the root user. 2. Execute the following commands to uninstall the package: Except the ES3000 # rpm -e Esmpro-common # sync For the ES3000 # rpm -e Esmpro-type3 # rpm -e Esmpro-common # sync 3. Execute the following commands and confirm whether the package is correctly uninstalled. Except the ES3000 # rpm -qa grep Esmpro-common For the ES3000 # rpm qa grep Esmpro-type3 # rpm qa grep Esmpro-common If no result is returned, the package was correctly uninstalled. The snmpd service has been stopped after uninstalling the package of Server Management Agent. Start the snmpd service manually. 3839 6420-003 8
2.4. Silent Installation The Server Management Agent setup program supports the silent installation. Set Up Program Directory To set up Server Management Agent, the files that are stored in the following directory in the installation CD-ROM are needed. /SMA/LINUX the directory that contains the Server Management Agent setup program (smainst.sh or smainst_vmware.sh). Installation To perform the silent installation, you should execute the following three steps. Step 1. Editing nechwid file (In Case of ES3000, Go to Step2) Copy /SMA/LINUX/nechwid included on the CD-ROM to HDD and edit it. The nechwid file has the following default settings. Item Default value Note Server Name 'Other' Vendor Name 'Other' Chassis Type FF Other type 1. Server Name You can set the server name of the target server. You can replace 'Other' strings. Specify it within 79 alphanumeric characters. The strings are displayed on the Data Viewer of Server Management Manager. Section ProductName Value (default) Other 2. Vendor Name You can set the vendor name of the target server. You can replace 'Other' strings. Specify it within 79 alphanumeric characters. The strings are displayed the Data Viewer of Server Management Manager. Section Manufacturer Value (default) Other 3839 6420-003 9
3. Chassis Type You can set the chassis type of the target server. Select one of the following, and set it: Parameter Mean 01 Rack mount 05 Full Tower 06 Desktop FF Other The chassis image bitmap is displayed on the Data Viewer of Server Management Manager. Section Value (default) Note Type FF Other type Step 2. Run setup program Execute the following command to run the setup program. The command that you execute is different depending on your distribution. Except the ES3000 on SLES9, SLES10, RHEL4, RHEL5 # {full path}/smainst.sh -i -f "<full path>/nechwid" Except the ES3000 on VMware ESX Server 3 # {full path}/smainst_vmware.sh -i -f "<full path>/nechwid" For the ES3000 on SLES9, SLES10, RHEL4, RHEL5 # {full path}/smainst.sh -ip For the ES3000 on VMware ESX Server 3 # {full path}/smainst_vmware.sh ip {full path} : The directory which stored the smainst.sh or the smainst_vmware.sh program <full path> : The directory which stored the edited nechwid file Step 3. Restart Server Management Agent Execute the following commands and restart Server Management Agent for the change to take effect. # sync # /opt/nec/esmpro_sa/bin/esmrestart 3839 6420-003 10
Uninstallation To perform the silent uninstallation, you should execute the following procedure. To uninstall the program Execute the following commands to uninstall the program. The command that you execute is different depending on your distribution. For SLES9, SLES10, RHEL4, RHEL5 # {full path}/smainst.sh -e For VMware ESX Server 3 # {full path}/smainst_vmware.sh -e {full path} : The directory which stored the smainst.sh or the smainst_vmware.sh program The snmpd service has been stopped after uninstalling of Server Management Agent. Start the snmpd service manually. 3839 6420-003 11
3839 6420-003 12
3. Monitoring Functions This section explains the monitoring function that Server Management Agent offers. To change the setting of each monitoring function, use the Control Panel (ESMagntconf). Method of starting the Control Panel (ESMagntconf) On VMware ESX Server 3, execute the following command and change the value of the LANG environment variable temporarily before starting the Control Panel (ESMagntconf). # export LANG=en_US 1. Log in to the system as the root user. 2. Move to the directory where Server Management Agent is installed. # cd /opt/nec/esmpro_sa 3. Move to the directory where ESMagntconf is stored. # cd bin 4. Start the Control Panel (ESMagntconf). #./ESMagntconf 3839 6420-003 13
3.1. General Properties Settings From the [General Properties] screen, you can set the following information. To display the [General Properties] screen, select "General" on the Control Panel (ESMagntconf). Enable the Manager to modify SNMP Setting "Enable the Manager to modify SNMP Setting" specifies whether the Server Management Manager can modify server operation parameters via SNMP. When checked, it is enabled. When not checked, it is disabled. (Set using the space key.) SNMP Community Select the community name that Server Management Agent uses to collect information on the local machine. The community name displayed in the list is the community name registered in SNMP environmental configuration file (snmpd.conf). (Select using the "UP/DOWN" arrow keys.) Select a community name that has the privilege to read from localhost. Rack Name The rack name can be set when the server is a rack mount type. It is possible to manage each rack by setting the rack name. The maximum length of the rack name is 63 characters, and you can use A-Z, a-z, 0-9, '.', '_' or '-'. 3839 6420-003 14
3.2. CPU Load Monitoring Functions When Server Management Agent detects a high-loaded CPU, it will issue a message to the syslog and will report the alert to Server Management Manager. With Server Management Manager s DataViewer, you can check which CPU has unusual usage. Since the function monitors load statuses either by individual CPUs or CPU total, you can monitor a server as one package regardless of the individual CPUs. Settings From the [CPU Load] screen, you can set the following information. To display the [CPU Load] screen, select "CPU" on the Control Panel (ESMagntconf). CPU load monitoring is not performed at the default settings. If you need to monitor the CPU load, change the settings to perform monitoring. You do not have to change threshold values of the CPU load rates. Although you may specify any values, the threshold values near the current values could cause the Agent to issue alerts frequently. When you change CPU load values, be careful not to cause alerts to be issued frequently due to the setting of the values. Sample Interval(s) Specify the CPU load monitoring cycle. Sample Interval can be set to 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30, or 60 seconds. (Select using the "UP/DOWN" arrow keys.) The default value is 10 seconds. Utilization Rate Specify the utilization rate of the CPU load monitoring. Utilization Rate can be set to load for 1 min, 5 min, 30 min, 1 hour, 1 day, or 1 week. (Select using the "UP/DOWN" arrow keys.) The default value is 1 minute. CPU s Item Select the CPU (individual or total CPU) for which you want to set the threshold. (Select using the "UP/DOWN" arrow keys.) Enable Threshold To enable the monitoring function of the CPU load factor, check this field. (Set using the space key.) The threshold can only be set when checked. 3839 6420-003 15
Threshold Set the warning and fatal thresholds. The default values of warning and fatal thresholds are as follows. Monitoring Item Fatal(Report) Fatal(Reset) Warning(Report) Warning(Reset) CPU load factor (%) 100 97 95 92 Fatal: The Report field specifies the high CPU load limit that generates a fatal alert. The Fatal alert is reset when the CPU load decreases to lower than the threshold in the Reset field. Warning: This is similar to the fatal fields, except a warning alert is generated or reset. When the CPU load exceeds the amount in the Report field, a Warning alert is generated. The Warning alert is reset when the CPU load decreases to lower than the threshold in the Reset field. 3839 6420-003 16
3.3. Syslog Monitoring Functions Server Management Agent monitors, based on the key word, a monitoring event logged to syslog and then reports the content of the event to Server Management Manager. You can add new event sources and monitoring events and delete unnecessary event sources and monitoring events, according to the system environment. Server Management Agent can monitor the messages logged into syslog by other applications and report the messages to Server Management Manager. Settings From the [Syslog Properties] screen, you can set the following information. To display the [Syslog Properties] screen, select "Syslog" on the Control Panel (ESMagntconf). Refer to "4.5. Syslog Event Setting" for how to add/delete syslog monitoring events. Server Management Agent monitors the syslog "/var/log/messages. Monitor Interval Specify the monitoring interval of Syslog event monitoring. The range is 10 to 3600 seconds. The default value is 300 seconds. 3839 6420-003 17
3.4. Storage Monitoring Functions Server Management Agent prevents some possible troubles by using the function "Hard disk prefailure prediction." "Hard disk prefailure prediction" judges whether there might be a problem if you continue to use the hard disk. When some problems are detected, it will issue a message to the syslog and will report the alert to Server Management Manager. Because the failing hard disk, where the error incidence is high, can be recognized before the hard disk actually breaks down, you can do a preventive exchange. Server Management supports "Hard disk prefailure prediction" using S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology). S.M.A.R.T. is a function used by a hard disk to monitor several items by itself. A hard disk gives an alert to Server Management Manager when the hard disk itself predicts a potential serious problem. 1) Only a single hard disk is monitored. 2) The storage devices that are not the SCSI/IDE connections are not monitored, such as USB. 3) The storage monitoring is not supported when the OS or HDD device does not support a S.M.A.R.T function. Settings From the [Storage Properties] screen, you can change the Sample Interval of Storage Monitoring Service, mode of hard disk prefailure prediction function, and can reset the status of an exchanged hard disk. To display the [Storage Properties] screen, select "Storage" on the Control Panel (ESMagntconf). Sample Interval(s) Specify the sampling interval. The range is 1 to 3600 seconds. The default value is 60 seconds. When you press [Default], the sample interval will be set to the default value. 3839 6420-003 18
HD Prefailure Prediction To enable the monitoring function of the HD Prefailure Prediction, check this field. (Set using the space key.) This field is checked by default. You cannot set the mode of each hard disk individually. All hard disks work in the same mode with the mode of hard disk prefailure prediction turned on or off. Reset Status Device (HD) Select a hard disk that needs to be reset. (Select using the "UP/DOWN" arrow keys.) [Reset Status] Reset the status information of the hard disk selected in "Device (HD). (For instance, use this button when you exchange hard disks.) When you replace a hard disk, you have to reset the status information to monitor the new disk. The procedure for adding a storage monitoring device Server Management Agent supports storage monitoring. The following are the main functions of storage monitoring. Management of configuration information for the storage devices connected to SCSI or IDE. Hard Disk, CD-ROM, a TAPE device, an optical memory device, etc., are contained in a storage device. By default, these storage monitoring functions manage the devices that can be identified as IDE devices by the OS. If you want to add the other devices to the management object of storage monitoring, you must change the setting of the management object. Refer to the following process. 1. Investigate the device driver name of the SCSI or IDE controller connected with the storage devices that you want to manage. 2. Execute the following command to stop ESMstrg service: # /etc/init.d/esmstrg stop 3. Open the following file using vi command, etc. /opt/nec/esmpro_sa/data/storage.inf 3839 6420-003 19
4. Add the device driver name (you investigated in step 1) to the [Management Port] section in "storage.inf" For example In the case of adding the adp94xx driver. [Management Port] [Management Port] adp94xx 5. Add the device driver name to the [Diagnostic Port] section. 6. Close the "storage.inf. 7. Execute the following command to start ESMstrg service: # /etc/init.d/esmstrg start 8. Check the below items. "ESMstrg" has started normally. The additional devices wanted for monitoring are displayed in DataViewer. In case the monitoring device is a hard disk, the "Status" item displays "Device is Normal" on the [HardDisk] - [General] Information View in DataViewer. 3839 6420-003 20
3.5. File System Monitoring Functions This function monitors the file system s free space based on the free disk space (MB). When Server Management Agent detects space shortages, it will issue a message to the syslog and report the alert to Server Management Manager. With the Server Management Manager s DataViewer, you can check which drive is short of free space. Settings From the [File System] screen, you can set the following information. To display the [File System] screen, select "File System" on the Control Panel (ESMagntconf). 1) You cannot monitor the network drives and the file system on removable drives (such as CD-ROMs). 2) You cannot monitor a file system of less than 100 MB. Sample Interval(s) Specify the sampling interval. The range is 1 to 3600 seconds. The default value is 60 seconds. When you press [Default], the sample interval will be set to the default value. Filesystem Select a file system to change threshold and/or monitoring mode. (Select using the "UP/DOWN" arrow keys.) Disable Threshold When checked, the free space of the file system is not monitored. (Set using the space key.) Enable Threshold (The amount of free bytes) When checked, the free space of the file system is monitored. (Set using the space key.) The threshold can only be set when checked. This field is checked by default. Threshold Set the warning and fatal thresholds. The default values of warning and fatal thresholds are as follows. When you press [Default], the thresholds will be set to default values. Monitoring Item Fatal Warning Free space (unit: MB) 1 percent of the capacity 10 percent of the capacity 3839 6420-003 21
3.6. Network (LAN) Monitoring Functions If there are many abandoned or error packets during a unit time (monitoring interval), the LAN monitoring function will determine that some failure has occurred in the network, issue a message to the syslog, and report the alert to Server Management Manager. The function checks LAN-related failures based on its percentage in relation to all packets sent/received during a monitoring interval. Therefore, there is a possibility that a message is registered due to a temporary increase in load. However, if such a condition is recovered immediately, there will be no problem. If it is not recovered immediately or such failures occur frequently, check the network environment including hardware and distribute the load. By default, the LAN monitoring function is off. If you want to monitor the LAN devices, you must change the setting of ESMlan daemon. Refer to the following process. 1. Execute the following command and set up so that the ESMlan service starts automatically. # /sbin/chkconfig ESMlan on 2. Start ESMlan service. # /etc/init.d/esmlan start Settings From the [LAN Properties] screen, you can set the following information. To display the [LAN Properties] screen, select "LAN" on the Control Panel (ESMagntconf). Sample Interval(s) Specify the sampling interval. The range is 1 to 3600 seconds. The default value is 180 seconds. Network Hardware Error (%) Specify the threshold of the percentage of Network Hardware error in total transmission and reception packets per monitoring cycle. Specify 0 when you want a report as soon as the error is detected. When the network cable is pulled out or the HUB power switch is off, a Network Hardware error occurs. Each error occurs for the following reasons. Error Reason Alignment Errors Broken packets for collision FCS Errors Broken packets for collision Carrier Sense Errors Cable disconnected, Cable defect, or Transceiver defect The range is 0 to 100 percent. The default value is 50 percent. 3839 6420-003 22
Transmission Retry (%) Specify the threshold of the percentage of collision and delay packets in total transmission packets per monitoring cycle. Transmission Retry will occur when the server is under the high network load. The range is 10 to 50 percent. The default value is 35 percent. Transmission Abort (%) Specify the threshold of the percentage of packets disposed due to excess collisions errors, etc., in total transmission packets per monitoring cycle. Transmission Abort will occur when the server is under the high network load. The range is 10 to 50 percent. The default value is 35 percent. 3839 6420-003 23
3839 6420-003 24
4. Report Setting Function This section explains the report setting for where and when an event is to be reported. To change the report setting, use the Control Panel (ESMamsadm). Method of starting the Control Panel (ESMamsadm) On VMware ESX Server 3, execute the following command and change the value of the LANG environment variable temporarily before starting the Control Panel (ESMamsadm). # export LANG=en_US 1. Log in to the system as the root user. 2. Move to the directory where Server Management Agent is installed. # cd /opt/nec/esmpro_sa 3. Move to the directory where ESMamsadm is stored. # cd bin 4. Start the Control Panel (ESMamsadm). #./ESMamsadm 3839 6420-003 25
4.1. Flow of Report Setting To report the alert by using SNMP as the report method When Server Management Agent was installed, the setting to report the alert by using SNMP as the report method for monitor events was almost completely established. The report preparation is completed by setting the IP address of Server Management Manager for the base setting. Refer to "4.2.1.1. Base Setting of Manager (SNMP)" for details of the setting. To report the alert by using the report methods other than SNMP 1. Perform the Base Setting. (Base Setting) Refer to "4.2.1.2. Base Setting of Manager (TCP_IP In-Band)" for the basic setting to report the alert by using TCP_IP In-Band as the report method. Refer to "4.2.1.3. Base Setting of Manager (TCP_IP Out-of-Band)" for the basic setting to report the alert by using TCP_IP Out-of-Band as the report method. 2. Set the list of report destinations. (Destination Setting) Refer to "4.3.1.1.Address Setting when Manager (TCP_IP In-Band) is used as a report method" for the address setting to report the alert by using TCP_IP In-Band as a report method. Refer to "4.3.1.2.Address Setting when Manager (TCP_IP Out-of-Band) is used as a report method" for the address setting to report the alert by using TCP_IP Out-of-Band as a report method. 3. Set monitor events and associate monitor events with report destinations. (Agent Event Setting, Syslog Event Setting) Agent Events are monitor events that Server Management Agent originally detects. Syslog Events indicate monitor events that the Syslog monitoring function detects. 3839 6420-003 26
4.2. Base Setting Here you set enabling/disabling reporting methods, trap destinations of Manager Report (SNMP), enabling/disabling the shutdown function in the event of an error, and waiting time before the shutdown. When you disable a reporting method, the method will not perform reporting for any monitoring items. When you disable the shutdown function, the remote shutdown function from Server Management Manager will be disabled, and the shutdown/reboot function as the action after reporting will also be disabled. Select "Base Setting" on the Control Panel (ESMamsadm) and the [Base Setting] screen opens. Report The list of report methods is displayed. Other The list of the other settings is displayed. [close] Closes the [Base Setting] screen. 3839 6420-003 27
4.2.1. Setting of Report Method Enable/Disable reporting methods and set the trap destinations of Manager Report (SNMP). Base Setting of Manager (SNMP) Enable/Disable Manager Report (SNMP) and set the trap destinations for this method. Select "Manager (SNMP)" on the [Base Setting] screen, then the [SNMP Trap Setting] screen opens. Enable the function Enable/Disable Manager Report (SNMP). When checked, it is active. (Set using the space key.) Trap Destination IP The list of IP addresses of the system in which Server Management Manager is installed and is specified as the destination is displayed. [Add] New IP address is added to the "Trap Destination IP. [Remove] IP address selected from the "Trap Destination IP" is deleted. [ok] Settings are saved and this screen closes. [cancel] This screen closes without saving changes. The destination for the trap sent from Server Management Agent should be added to "Trap Destination IP" on the [SNMP Trap Setting] screen. Server Management Agent does not use the trap destination set in snmpd.conf. (In other words, the trap sent from Server Management Agent is not sent to the destination set in snmpd.conf.) 3839 6420-003 28
Base Setting of Manager (TCP_IP In-Band) Enable/Disable Manager Report (TCP_IP In-Band). Select "Manager (TCP_IP In-Band)" on the [Base Setting] screen and the [Enable/Disable] screen opens. Enable the function Enable/Disable Manager (TCP_IP In-Band). When checked, it is active. (Set using the space key.) [ok] Settings are saved and this screen closes. [cancel] This screen closes without saving changes. Base Setting of Manager (TCP_IP Out-of-Band) Enable/Disable Manager Report (TCP_IP Out-of-Band). Select "Manager (TCP_IP Out-of-Band)" on the [Base Setting] screen and the [Enable/Disable] screen opens. Enable the function Enable/Disable Manager (TCP_IP Out-of -Band). When checked, it is active. (Set using the space key.) [ok] Settings are saved and this screen closes. [cancel] This screen closes without saving changes. When you use Manager Report (TCP_IP Out-of-Band), make sure to select "Permit discretionary authentication including clear text" for the encryption setting in the RAS (Remote Access Service) setting on the Server Management Manager side. 3839 6420-003 29
4.2.2. Other Setting Specify the time that elapses before shutdown. Select "Shutdown Delay" on the [Base Setting] screen and the [Shutdown Setting] screen opens. Enable the function Enable/Disable the shutdown function. When checked, it is active. (Set using the space key.) Shutdown Delay The range is 0 to 1800 seconds. The default value is 20 seconds. If you specified "Shutdown" for "Action After Report," or the shutting down request from Server Management Manager has occurred, the shutdown is started after the time set here has passed. [ok] Settings are saved and this screen closes. [cancel] This screen closes without saving changes. 3839 6420-003 30
4.3. Destination Setting Here you will change, add and/or delete destination IDs. Select "Destination ID Setting" on the Control Panel (ESMamsadm) and the [Destination ID Setting] screen opens. ID Name The list of the registered Destination IDs is displayed. Message Method: Address: The report method of the ID selected from "ID Name" is displayed. The address information of the ID selected from "ID Name" is displayed. [Add...] New Destination ID is added. Press this button to open the [ID Setting] screen. If you have registered a Destination ID that has different destinations using the same reporting method, you can send messages to multiple addresses with this method. [Modify...] Press to modify the setting of the Destination ID selected from "ID Name. [Delete...] The Destination ID selected from "ID Name" is deleted. "SNMP, "TCP_IP IN-BAND" and "TCP_IP OUT-OF-BAND" are set as the default. You cannot delete them. When you delete a Destination ID, it will also be deleted from events to be monitored. [close] Closes the [Destination ID Setting] screen. 3839 6420-003 31
4.3.1. Changing the Setting of Destination IDs Change the setting of Destination IDs registered in the list. Select the Destination ID you want to change from "ID Name" on the [Destination ID Setting] screen and press [Modify...] to open the [ID Setting] screen. The setting steps are different by the report methods. [Setting Method] Press [Address...] and [Schedule...] to set where and when to report. 1) While modifying the settings, you cannot modify "ID" and "Method. (read only) 2) When "Manager (SNMP)" has been selected as the "Method, even if [Address...] is pressed, the address setting screen is not displayed because it is not necessary to set the address. Address Setting when Manager (TCP_IP In-Band) is used as a report method When [Address...] is pressed when "Manager (TCP_IP In-Band)" has been selected as the "Method" on the [ID Setting] screen, the [Manager (TCP_IP In-Band) Setting] screen opens. IP Address (or Host Name) Set IP address (or Host Name) of Server Management Manager. 3839 6420-003 32
Port Number The port number used for the communication between sockets can be set. For this number, the value must be the same for Server Management Agent and Server Management Manager. (The default value is 31134 for both of Server Management Agent and Server Management Manager.) Do not change the value as long as the default value works. If the default value does not work, set the port number in the range of 6001 to 65535. When you press [Default], the port number will be set to the default value (31134). If a modification is made, be sure to also modify the setting for Server Management Manager. This modification is made in the following manner on the server in which Server Management Manager is installed. [How to modify] 1. Click the "Setting" - "Base Setting" menu on Alert Manager. The [Base Setting] dialog box appears. 2. Select "Receive from Agent (TCP/IP)" and click [Configure...]. The [Receive from Agent (TCP/IP) Setting] dialog box appears. 3. Set the port number in the "Port Number" field on the [Receive from Agent(TCP/IP) Setting] dialog box. [ok] Settings are saved and this screen closes. [cancel] This screen closes without saving changes. Address Setting when Manager (TCP_IP Out-of-Band) is used as a report method When [Address...] is pressed when "Manager (TCP_IP Out-of-Band)" has been selected as the "Method" on the [ID Setting] screen, the [Manager (TCP_IP Out-of -Band) Setting] screen opens. 3839 6420-003 33
IP Address (or Host Name) Set IP address (or Host Name) of Server Management Manager. Select Remote Access Service Entry Set the Phone Number, the User, and the Password. Port Number The port number used for the communication between sockets can be set. For this number, the value must be the same for Server Management Agent and Server Management Manager. (The default value is 31134 for both of Server Management Agent and Server Management Manager.) Do not change the value as long as the default value works. If the default value does not work, set the port number in the range of 6001 to 65535. When you press [Default], the port number will be set to default value (31134). If a modification is made, be sure to also modify the setting for Server Management Manager. This modification is made in the following manner on the server in which Server Management Manager is installed. [How to modify] 1. Click the "Setting" - "Base Setting" menu on Alert Manager. The [Base Setting] dialog box appears. 2. Select "Receive from Agent (TCP/IP)" and click [Configure...]. The [Receive from Agent (TCP/IP) Setting] dialog box appears. 3. Set the port number in the "Port Number" field on the [Receive from Agent(TCP/IP) Setting] dialog box. [ok] Settings are saved and this screen closes. [cancel] This screen closes without saving changes. 3839 6420-003 34
Schedule Setting Set the report Schedule for each Destination ID. Retry Interval Set the retry interval. The range is 1 to 30 minutes. The default value is 5 minutes. Reporting Expiration Time Set the maximum retry time. The range is 0 to 240 hours. The default value is 72 hours. If you set 0 hour, no report is reported. Reporting Time Table Set the reportable time periods. Only the alerts that occur during the reportable time are reported. It is possible to specify a time period of 1 hour. The default value is 24 hours. An alert that occurs outside the reportable time is not reported immediately. When the reportable time comes, it is reported. (The event is reserved until then.) [ok] Settings are saved and this screen closes. [cancel] This screen closes without saving changes. 3839 6420-003 35
4.3.2. Adding Destination IDs Add Destination IDs to the list. The setting steps differ by the report methods. [Setting Method] 1. Input an ID name. 2. Select a report method. (Select using the "UP/DOWN" arrow keys.) 3. Press [Address...] to set the address on the displayed screen. 4. Press [Schedule...] to set the report schedule on the displayed screen. 5. Press [ok]. When "Manager (SNMP)" has been selected as the "Method, even if the [Address...] button is pressed, the address setting screen is not displayed because it is not necessary to set the address. 3839 6420-003 36
4.4. Agent Events Setting Set monitor events of Server Management Agent and associate monitor events with report destinations. If monitor events of Server Management Agent occur, alerts will be sent to destinations set up here. Select "Agents Events Setting" on the Control Panel (ESMamsadm) and the [Agents Events Setting] screen opens. Source The list of the source names is displayed. Operation on source Operation on source can be selected. ON: Select this item when you set the report destination for all event IDs of the selected source at the same time OFF: Select this item if you set the following. - When you individually set the report destination to each event ID of the selected Source - When you modify the setting of the monitor event Event ID The Event ID from the source selected in "Source" is displayed. When "ON" is selected in "Operation on source, "ALL" is displayed in "Event ID. Trap Name The trap name of selected Event ID is displayed. [Set...] Sets the selections based on "Operation on source. Pressing this button displays the [Monitor Event Setting] screen. See 4.4.1 Setting Destination. [close] The [Agents Events Setting] screen closes. 3839 6420-003 37
4.4.1. Setting Destination (Agent Event) The following are the methods of specifying the report destination: 1. Specify the report destination for each monitor event individually. 2. Specify the same report destination for all event IDs under each source at the same time. To specify the report destination for each monitor event individually Not only the report destination but also Action After Report, Deal Method, etc., can be set. [Setting Method] 1. Start the Control Panel (ESMamsadm) and select "Agents Events Setting. 2. Select the source name from "Source. (Select using the "UP/DOWN" arrow keys.) 3. Select "OFF" from "Operation on source. (Set using the space key.) 4. Select the Event ID for which you want to modify the setting from "Event ID. (Select using the "UP/DOWN" arrow keys.) 5. Press [Set...] and the [Monitor Event Setting] screen opens. 6. Select the ID to be reported from "Destination ID List. 7. Pressing [Add] moves the ID to "Report to. 8. To delete IDs from "Report to, select the ID from "Report to" and press [Remove] to move the ID to "Destination ID List. 9. Press [ok]. 3839 6420-003 38
Action After Report Select either "Shutdown, "Reboot, or "None" from the list and specify an action after report. (Select using the "UP/DOWN" arrow keys.) Deal Method Specify the action method to the reported item. The limit is 507 alphanumeric characters. To specify the same report destination for all event IDs under each source at the same time [Setting Method] 1. Start the Control Panel (ESMamsadm), and select "Agents Events Setting. 2. Select the source name from "Source. (Select using the "UP/DOWN" arrow keys.) 3. Select "ON" from "Operation on source. (Set using the space key.) 4. Press [Set...] and the [Monitor Event Setting] screen opens. 5. Select the ID to be reported from "Destination ID List. 6. Pressing [Add] moves the ID to "Report to. 7. To delete IDs from "Report to, select the ID from "Report To" and press [Remove] to move the ID to "Destination ID List. 8. Press [ok]. Even if the [Monitor Event Setting] screen is opened again after this setting is done, nothing is displayed in "Report to. Confirm the setting individually in each event. 3839 6420-003 39
4.5. Syslog Events Setting You can link the setting of syslog monitoring events with the report to monitoring events. If monitor events occur, alerts will be sent to destinations set up here. You can arbitrarily add and delete new event sources and new monitoring events in addition to events registered beforehand according to the system environment. Monitoring syslog events is performed at intervals of 5 minutes. You can change the monitoring interval of Syslog event monitoring. Refer to "3.3. Syslog Monitoring" for the method to modify monitoring interval. Select "Syslog Events Setting" on the Control Panel (ESMamsadm) and the [Syslog Events Setting] screen opens. Source The list of the source name is displayed. Operation on source Operation on source can be selected. ON: Select this item if you set the following. - When you set the report destination for all event IDs of the selected source at the same time. - When you add or delete the source of the syslog monitoring events. OFF: Select this item if you set the following. - When you individually set the report destination to each event ID of the selected Source. - When you add or delete the monitor event or modify the setting of the monitor event. Event ID The Event ID list from the source selected in "Source" is displayed. When "ON" is selected in "Operation on source, "ALL" is displayed in "Event ID. 3839 6420-003 40
Trap Name The trap name of the selected Event ID is displayed. [close] The [Syslog Events Setting] screen closes. For the following buttons, a part of the function varies according to the selection situation of "Operation on source. [Add...] ON: OFF: [Del...] ON: OFF: [Set...] ON: OFF: [Test] ON: OFF: Add the source of the syslog monitoring events. Pressing this button displays the [Add Syslog Item] screen. Add the syslog monitoring event under the selected source. Pressing this button displays the [Add Syslog Item] screen. Delete the selected source of the syslog monitoring events. Delete the syslog monitoring event selected in "Event ID. Specify the report destination for to all Event IDs of the selected source at the same time. Pressing this button displays the [Syslog Application Setting] screen. Modify the setting of the monitor event selected from "Event ID. Specify the report destination to the monitor event selected from "Event ID. Pressing this button displays the [Syslog Application Setting] screen. This button is not available. For the test report, press this button. 3839 6420-003 41
4.5.1. Setting Destination (Syslog Event) The following are the methods of specifying the report destination: 1. Specify the report destination for each monitor event individually. 2. Specify the same report destination for all event IDs under each source at the same time. To specify the report destination for each monitor event individually Not only the report destination but also Action After Report, Deal Method, etc., can be set. [Setting Method] 1. Start the Control Panel (ESMamsadm) and select "Syslog Events Setting. 2. Select the source name from "Source. (Select using the "UP/DOWN" arrow keys.) 3. Select "OFF" from "Operation on source. (Set using the space key.) 4. Select the Event ID for which you want to modify the setting from "Event ID. (Select using the "UP/DOWN" arrow keys.) 5. Press [Set...] and the [Syslog Application Setting] screen opens. 6. Select the ID to be reported from "Destination ID List. 7. Pressing [Add] moves the ID to "Report to. 8. To delete IDs from "Report to, select the ID from "Report to" and press [Remove] to move the ID to "Destination ID List. 9. Press [ok]. 3839 6420-003 42
Action After Report Select either "Shutdown, "Reboot, or "None" from the list and specify an action after report. (Select using the "UP/DOWN" arrow keys.) Deal Method Specify the action method to the reported item within 507 alphanumeric characters. Report Count The report is done when the key word is registered in Syslog at the same frequency as the setting here. Monitoring Time Table Set the reportable time periods. Only the alerts that occur during the reportable time are reported. It is possible to specify 1 hour. The default value is 24 hours. To specify the same report destination for all event IDs under each source at the same time [Setting Method] 1. Start the Control Panel (ESMamsadm) and select "Syslog Events Setting. 2. Select the source name from "Source. (Select using the "UP/DOWN" arrow keys.) 3. Select "ON" from "Operation on source. (Set using the space key.) 4. Press [Set...] and the [Syslog Application Setting] screen opens. 5. Select the ID to be reported from "Destination ID List. 6. Pressing [Add] moves the ID to "Report to. 7. To delete IDs from "Report to, select the ID from "Report to" and press [Remove] to move the ID to "Destination ID List. 8. Press [ok]. Even if the [Syslog Application Setting] screen is opened again after this setting is done, nothing is displayed in "Report to. Confirm the setting individually in each event. 3839 6420-003 43
4.5.2. Adding of Syslog Monitoring Event Sources According to the system environment, you can arbitrarily add new event sources. Add new event sources here when you want to monitor the event that applications other than Server Management Agent register. You register the first new monitoring event when registering a new event source. [Setting Method] 1. Start the Control Panel (ESMamsadm) and select "Syslog Events Setting. 2. Select "ON" from "Operation on source. (Set using the space key.) 3. Press [Add...], and then the [Add Syslog Item] screen opens. 4. Input Source, Event ID, Keyword, Trap Name and Deal Method. 5. Press [Done]. Source Specify the source name within 40 alphanumeric characters. It is displayed in the "source" column at the alert viewer of Server Management Manager. Event ID Specify Event ID using 8 alphanumeric characters (hexadecimal number) according to the following naming rule for event IDs. The format of Event ID is "x0000yyy. (For example: 40000101, 800002AB, C0000101) Select one as follows, and set it in "x": 4: Specifies information events. The color of the icon displayed in Server Management Manager s Alert Viewer is green. 8: Specifies warning events. The color of the icon displayed in Server Management Manager s Alert Viewer is yellow. C: Specifies abnormal events. The color of the icon displayed in Server Management Manager s Alert Viewer is red. Set an arbitrary hexadecimal number to "yyy. The range is 001 to FFF. 3839 6420-003 44
Keyword1, Keyword2, Keyword3 Specify the character string for which Server Management Agent can uniquely specify the message registered in Syslog within 256 alphanumeric characters. When the message including all keywords is detected from Syslog, the full text of the message is reported to Server Management Manager. It is displayed in the "Details" column of an alert viewer of Server Management Manager. Trap Name Specify the outline of the report message within 79 alphanumeric characters. It is displayed in the "Outline" column of an alert viewer of Server Management Manager. Deal Method Specify the action method to the reported item within 507 alphanumeric characters. It is displayed in the "Action" column of an alert viewer of Server Management Manager. The maximum number of events that can be registered is 1000. *Keep in mind that the amount of the disk used and the amount of the memory used are increased by the number of registered events. Source, Event ID, Keyword1, and Trap Name are indispensable. 3839 6420-003 45
4.5.3. Adding of Syslog Monitoring Events Responding to the system environment, you can add a new Syslog Monitoring event under the Syslog Monitoring Event Source that has already been registered. [Setting Method] 1. Start the Control Panel (ESMamsadm) and select "Syslog Events Setting. 2. Select the source name from "Source. (Select using the "UP/DOWN" arrow keys.) 3. Select "OFF" from "Operation on source. (Set using the space key.) 4. Press [Add...] and the [Add Syslog Item] screen opens. 5. Input Event ID, Keyword, Trap Name and Deal Method. Refer to "4.5.2 Adding of Syslog Monitoring Event Sources" for details. 6. Press [Done]. The maximum number of events that can be registered is 1000. *Keep in mind that the amount of the disk used and the amount of the memory used are increased by the number of registered events. Event ID, Keyword1, and Trap Name are indispensable. 3839 6420-003 46
4.5.4. Deleting of Syslog Monitoring Event Sources The source of the Syslog Monitoring event can be deleted from the Syslog event watch. When you delete an event source, all monitoring events contained in that source will be deleted. Certain monitoring event resources are registered with Server Management Agent by default. You cannot delete them. [Setting Method] 1. Start the Control Panel (ESMamsadm) and select "Syslog Events Setting. 2. Select the source name that you want to delete from "Source. (Select using the "UP/DOWN" arrow keys.) 3. Select "ON" from "Operation on source. (Set using the space key.) 4. Press [Del...]. 3839 6420-003 47
4.5.5. Deleting of Syslog Monitoring Events You can delete an event source from Syslog event monitoring. The predetermined watch event that Server Management Agent registers cannot be deleted. [Setting Method] 1. Start the Control Panel (ESMamsadm) and select "Syslog Events Setting. 2. Select the source name from "Source. (Select using the "UP/DOWN" arrow keys.) 3. Select "OFF" from "Operation on source. (Set using the space key.) 4. Select Event ID that you want to delete from "Event ID. (Select using the "UP/DOWN" arrow keys.) 5. Press [Del...]. 3839 6420-003 48
Appendix A NOTE Keep the following limitations in mind when using Server Management Agent: 1. The issue of the net-snmp packages version "5.1.2-11.EL4.7" on RHEL4U4 EM64T In Server Management Manager, the following phenomena are generated by the issue of the net-snmp packages, when the net-snmp packages version "5.1.2-11.EL4.7" included in RHEL4U4 EM64T is installed on the machine that is an object of management. 1) In the Autodiscovery function, when the fourth octet of the IP address of the machine that is an object of management is 128 or more, the machine cannot be discovered automatically. [Evasion plan] Please do either of the following: Use the net-snmp packages of which the version is "5.1.2-11.EL4.6" on the machine that is an object of management. (This issue is not included in the net-snmp packages of which the version is "5.1.2-11.EL4.6") Register the machine that is an object of management manually using the Icon Palette. (From [View] Menu of the Operation Window, select [Icon Palette]). 2) When the count of the SNMP request transmission from Server Management Manager exceeds 2,147,483,648 times, the SNMP request to the machine that is an object of management fails. If an error has occurred, it becomes impossible to do the following for the machine that is an object of management: Start the DataViewer Watch Server Status Automatic Data Collection [Assistance] As a standard where the phenomenon is generated, the SNMP request exceeds 2,147,483,648 times after about 400 days, when the following setting and operating are done for 255 machines that are an object of management. Start the DataViewer (5 times per day) "every 30 minutes" is set to the Collection Cycle in Automatic Data Collection function. "1 minute" is set to Server Status Polling Interval. [Evasion plan] Please do either of the following: Use the net-snmp packages of which the version is "5.1.2-11.EL4.6" on the machine that is an object of management. (This issue is not included in the net-snmp packages of which the version is "5.1.2-11.EL4.6") Restart ESM Base Service regularly on Server Management Manager side. The count of the SNMP request transmission is cleared. 3839 6420-003 49
3) In the Local Polling function of Server Management Manager, the following phenomena are generated, when RHEL4U4 EM64T is installed on the machine that is an object of management. -1 The following error message is displayed and polling cannot be started when a negative value is set for maximum value, minimum value, or each threshold. "Could not set thresholds on the server. Please refer to Recovery Action for errors in DataViewer Help." -2 The following error message is displayed and it is not possible to reset it, even if the [Reset] button is pressed. "Could not set thresholds on the server. Please refer to Recovery Action for errors in DataViewer Help." 2. Logical CPU information and Memory Usage On VMware ESX Server 3, Logical CPU information and Memory Usage that Server Management Agent treats are not the entire values of the system but the values allocated in the service console. 3. The transmission speed of the network on DataViewer The transmission speed of the network might not be correctly displayed on the network tree of the DataViewer, according to the specification of hardware and the specification of driver. 4. The type of the network interface on DataViewer The type of the network interface supported by Server Management Manager is only Ethernet and Loopback. Other types of network interface might not be correctly displayed on the network tree of the DataViewer. 5. Expansion Bus Device Information on DataViewer When operating system is SUSE Linux, "Expansion Bus Device" information is not displayed on the DataViewer. 6. segfault s message Segfault is very uncommonly generated on an EM64T system when the following services stop: ESMamvmain, ESMcmn, and ntagent. This does not influence the operation of Server Management Agent, but the following messages might be registered in Syslog. kernel: ESMamvmain[XXXXX]: segfault at XXXXXXXXXXXXXXXX rip XXXXXXXXXXXXXXXX rsp XXXXXXXXXXXXXXXX error X * "XXXXX" represents alphanumeric characters. It changes by the situation. 7. Ports used by Server Management Manager and Agent Server Management Manager and Agent use the following ports. If a firewall is placed between Manager and Agent, or if the firewall is enabled on your system, open the following ports. 3839 6420-003 50
Between Manager and Agent Function Manager (Port) Direction Agent (Port) Protocol Remarks Operation Window (Autodiscovery) - - icmp icmp Operation Window (Server Status Polling) Undetermined 161 UDP snmp / DataViewer / Server Down Detection Report to Manager (SNMP) 162 Undetermined UDP snmp-trap Report to Manager (TCP/IP In-Band) 31134 Undetermined TCP - Report to Manager (TCP/IP Out-of-Band) - The upper direction shows the direction at start-up, and the lower shows the return. - For the setting of the port number for the Report to Manager (TCP/IP In-Band), refer to "4.3.1.1.Address Setting when Manager (TCP_IP In-Band) is used as a report method. - For the setting of the port number for the Report to Manager (TCP/IP Out-of-Band), refer to "4.3.1.2.Address Setting when Manager (TCP_IP Out-of-Band) is used as a report method. - "Undetermined" means that the unoccupied port at the communication start-up will be selected. Between Manager and Manager Function Manager (Port) Direction Manager (Port) Protocol Remarks Inter-Manager Communication Undetermined 8806 TCP - - The port number can be changed in the Remote Manager dialog box by selecting Operation Window menu [Option], [Customize], [Remote Manager]. - "Undetermined" means that the unoccupied port at the communication start-up will be selected. Between Manager and Mail Server Function Manager(Port) Direction Mail Server(Port) Protocol Remarks Internet Mail Undetermined 25 TCP smtp - The port number for the Internet Mail can be changed by the following method on Server Management Manager. 1) Click the Setting - Base Setting menu on Alert Manager and the Base Setting dialog box appears. 2) Select the Internet Mail and click Configure on the Base Setting dialog box and the Internet Mail setting dialog box appears. 3) Set the port number to SMTP Port number on Internet Mail Setting dialog box. - "Undetermined" means that the unoccupied port at the communication start-up will be selected. Agent for Linux uses internal ports Function Port Protocol Environment Remarks Agent Function more than 32767 tcp Using the function of Agent The port which the Agent uses is more than 32767. portmap Function 111 udp Using the function of - portmap - In case of enabling Firewall to lo interface, open the above ports. 3839 6420-003 51
8. The issue of I/O ports occupation by pnpacpi For the ES3000 on SLES10, pnpacpi occupies I/O ports of OpenIPMI. Set following BOOT OPTION by OS start menu. pnpacpi=off 9. The issue of OpenIPMI on VMware ESX Server 3.0.0 and 3.0.1 Apply these patches to solve the performance problem of the OpenIPMI driver. For the ES3000 on VMware3.0.0 ESX-1000074 http://kb.vmware.com/selfservice/microsites/search.do?language=en_us&cmd=displaykc&externalid=1000074 ESX-8005537 http://kb.vmware.com/selfservice/microsites/search.do?language=en_us&cmd=displaykc&externalid=8005537 ESX-6530518 http://www.vmware.com/support/vi3/doc/esx-6530518-patch.html For the ES3000 on VMware3.0.1 ESX-1271657 http://www.vmware.com/support/vi3/doc/esx-1271657-patch.html 3839 6420-003 52
2008 Unisys Corporation. All rights reserved. *38396420-003* March 2008 3839 6420 003