Readme and Release notes for release 1.7.1.11 (CSM) IBM Cluster Systems Management 1.7.1.11 CSM-1.7.1.11-x86-Linux Readme

• In the CSM for AIX and Linux V1.7.1 Command and Technical Reference the second example for the lsswtopol command has a syntax error.
  The command is documented as:
  lsswtopol -n 2 -F frame:cage:port:location
  The correct syntax is:
  lsswtopol -n 2 -F frame:cage:port:location:
  
  
• When using Live Partition Mobility (LPM) function to move CSM Managed Node from one Managed System to another, some of the node attributes (Lpar_ID, HWModel, HWType, etc...) will get out of sync as a result.

Workaround:

CSM won't adjust to dynamic changes, so user need to use the chnode, rmnode, and definenode commands as appropriate to manually update the CSM definitions to match what they have done with partition mobility. Otherwise, it could result in actions being performed on the wrong LPARs.



• When the rpower on/off command is issued, rpower query output can not indicate the true rpower status for the nodes managed by IVM 2.1.1 or lower. This is caused by an event subscription module, which will be fixed in IVM2.1.2.

Workaround:

Restart IBM.HWCTRLRM to register CSM event again after the event subscription is cleared up on IVM. Please follow the steps below:

On IVM:

1. Stop cimserver by command: /usr/ios/sbin/climgr cimserver stop
2. Delete files in /opt/freeware/cimom/pegasus/etc/repository/root#ibmsd/instances
3. Start cimserver by command: /usr/ios/sbin/climgr cimserver start

On the CSM Management Server:
     Restart IBM.HWCTRLRM

• The rpower query output for the nodes managed by IVM 2.0.0.0 or higher will stuck after IVM is rebooted.

Workaround:

Run rpower -n < node_name > refresh or restart IBM.HWCTRLRM to refresh the rpower state.

• If the BladeCenter Advanced Management Module firmware version is BPET46C, BPET46G or BPET46H, the rpower reboot command against the blades managed by the AMM will fail with error "Communications failed".

Workaround:

Upgrade the AMM firmware to BPET46J or higher.

• When you do a full OS install with SLES9 SP3 x86_64 on x3550/x3650, the OS can be installed successfully. However, the network is not available.

Workaround:

1. Download the latest bnx2 driver from Broadcom website.
2. Recompile the latest driver for the SMP kernel and put the driver in the /csminstall/csm/drivers/2.6.5-7.244-smp/x86_64/ directory.
3. Recompile the latest driver for single processor and put the driver in the /csminstall/csm/drivers/22.6.5-7.244-default/x86_64 directory.
4. Execute csmsetupinstall, installnode .
• If you have run copycds for normal SLES10 SP1 ISOs, and wants to use csmsetupinstall with -p flag to install SLES10 SP1 Update1 distribution for JS22 machines, they will have to remove the original directory /csminstall/Linux/SLES/10/ppc64/SP1 first, otherwise csmsetupinstall will not copy the new SLES10 SP1 Update1 ISOs since the target directory in /csminstall has already been there.

Workaround:

Remove the original directory /csminstall/Linux/SLES/10/ppc64/SP1 before csmsetupinstall -p is run.

• When running DCEM with Korean language, if you click on Reports tab ---> select a report ----> click View button, ----> click on Command tab, The Strings Device names , Device groups are not displayed and fields are truncated due to small window size.

Workaround:

Enlarge the window.

• When running DCEM with a language such as Korean which has no alphabetic characters, if you click on Browse button of Name, The Column heading "Description" contains a shortcut character such as "korean_translation(D)". Some of the shortcut strings are not working. There are two "Name" strings on file. The string for column heading is without shortcut function now.

Workaround:

There isn't workaround for this problem.

If a node's IP or MAC address is changed, getadapters or csmsetupinstall may fail to get the node's MAC address.

Workaround:

Check the arp entry on the Install Server and the gateway machine, if an old permanent arp entry for this node exists, remove it with arp command.

When nfs-utils has been installed, running installms with -f option will fail:


installms -f -p . Creating the required directories for CSM. ... ... installms: Failed to install Management Server Operating System  Prerequisites Packages! About to copy CSM  command binaries. Successfully copied CSM command binaries. installms: Installation of CSM was unsuccessful (rc = 1).

Workaround:

1. Remove nfs-utils rpm from the CSM Management Server manually by executing the rpm command with -e option.
2. Run installms with -f option again.

When running a dsh command in which the last character is a semicolon (';') and semicolon is not a delimiter of shell command, dsh will ignore this semicolon, and may cause the command to fail. For example, the following command will fail:


find /tmp -name RATSTempFile -exec ls -l {} \;

Workaround:

Add an additional semicolon at the end of shell command, for example:


  find /tmp -name RATSTempFile -exec ls -l {} \;;

If you attempt to do a cross service level diskless installation between management server and diskless node (RHEL4GA= > RHEL4QU3) or use a user-defined warewulf template using warewulf 2.6.2, the installation will fail due to a warewulf bug. Please upgrade your warewulf packages to version 2.6.3 or higher to resolve this problem.

When upgrading SLES nodes using the "you" InstallMethod , sometimes the SLES online_update tool does not upgrade all the RPMs to the latest levels, and the SPident tool reports that some of the packages are not at the correct service pack level. This is a SUSE problem, and the workaround is to use the rpm -U command to manually update the missing packages reported by SPident.

After migrating to CSM 1.5.1.2 or later versions (from a version prior to CSM 1.5.1.2) , both an "A" and a "B" side appear in the Cluster Peer Domain for single-sided FSP servers when using commands such as frame -l or lsrhws -e . For Power5 clusters with the High Performance Switch, having both the "A" and "B" side in the Cluster Peer Domain for single-sided FSP servers could affect the function and performance of the High Performance Switch Network Manager (HPSNM).
Use the following one-time workaround after upgrading CSM to permanently remove the duplicates from the Cluster Peer Domain and refresh the High Performance Switch Network Manager (if one is present). Run all of these commands on the Management Server.


1. chswnm -d (Stops the High Performance Switch Network Manager.)
2. rmrhws -s 'Element_Type=="FSP"' (Removes all FSPs from the Cluster Peer Domain.)
3. hwsda -s SP (Adds the FSPs back to the Cluster Peer Domain correctly.)
4. wait for 12 minutes (Allows hardware server time to re-establish connections to all FSPs.)
5. chswnm -a (Starts the High Performance Switch Network Manager.)

CSM is turning off the hardware flow control on the node when installing System x nodes with Red Hat EL. Without the hardware flow control being enabled, if you are monitoring the install in an rconsole window, eventually the screen gets garbled because of SOL being unreliable.
Workaround:


1. Enable the hardware flow control after the node boot and before the OS installation start. Modify the node PXE file under directory /tftpboot/pxelinux.cfg/, or modify template files install.pxe, install_HTTP.pxe or install_UUID.pxe under directory /opt/csm/install/ based on the the install protocol. Here is an example of install_UUID.pxe modification:
   

        [root@mn2 install]# diff -u install_UUID.pxe~ install_UUID.pxe     --- install_UUID.pxe~   2006-10-05 20:14:24.000000000 -0400     +++ install_UUID.pxe    2006-10-05 20:14:45.000000000 -0400     @@ -3,4 +3,4 @@     DEFAULT csm     LABEL csm     KERNEL csm/#KS_LEVEL#z     -APPEND utf8 nofb root=/dev/ram console=tty1 console=#CONSOLE_DEVICE#, \      #CONSOLE_SPEED# ks=file:/ks initrd=csm/#CLIENT_IP#.gz       ksdevice=#ADAPTER_NAME# \      #RAMDISK_SIZE# #ADDITIONAL_KERNEL_PARAM#     +APPEND utf8 nofb root=/dev/ram console=tty1 console=#CONSOLE_DEVICE#, \      #CONSOLE_SPEED#n8r ks=file:/ks initrd=csm/#CLIENT_IP#.gz      ksdevice=#ADAPTER_NAME# \      #RAMDISK_SIZE# #ADDITIONAL_KERNEL_PARAM#     

2. Enable the hardware flow control after the OS installation started. Modify the kickstart file to enable the hardware flow control. Here is an example of kickstart file modification:
   

        [root@mn3 kickstart.RedHatEL-AS4]# diff -u mn4.clusters.com-kickstart \   mn.clusters.com-kickstart.orig      --- mn4.clusters.com-kickstart  2006-10-26 20:45:56.000000000 -0400      +++ mn4.clusters.com-kickstart.orig     2006-10-26 20:44:45.000000000 -0400      @@ -202,7 +202,7 @@      util-linux       %pre      -stty crtscts /tmp/foo.py < 

lshwstat returns inaccurate readings for CPU temperature for System x 3455 servers. When running the lshwstat command with the "temp" or "cputemp" options, an inaccurate reading may be returned for CPU temperature. For example, the command may return a temperature for CPU #1 of 3 degrees C. Also, in a single-CPU x3455 server, a temperature of -128 degrees C may be returned for the non-existent CPU.

When you run csmsetupinstall command to setup diskless nodes with install server, it will fail to install YUM packages on install server. The error message is similar to:
js22cdls06.clusters.com: syncServers.client: Failed to install Install Server YUM Packages!

Workaround:

1. Rerun csmsetupinstall command will fix this problem.

¹ "Linux Update Packages" refer to Linux-based BIOS update tools used by the rfwflash command. These packages are available for x86-based eServer and xSeries servers.

• When installing SLES10 SP3 on x86_64 nodes, during the first reboot process after the OS installation, the rsct packages can't be installed because of the errors below:
  
  ......
  Installing Managed Node RSCT Packages ...
  makenode: Failed to install Managed Node RSCT Packages!
  makenode: An error occurred while installing CSM packages.
  Command rpm printed out:
  error: Failed dependencies:
  libstdc++.so.5 is needed by src-1.3.0.4-09252.i386
  libstdc++.so.5 is needed by rsct.core-2.5.4.0-09252.i386
  libstdc++.so.5(GLIBCPP_3.2) is needed by rsct.core-2.5.4.0-09252.i386
  libstdc++.so.5 is needed by rsct.core.utils-2.5.4.0-09252.i386
  libstdc++.so.5 is needed by rsct.core.cimrm-2.5.4.0-09252.i386
  libstdc++.so.5(GLIBCPP_3.2) is needed by rsct.core.cimrm-2.5.4.0-09252.i386
  libstdc++.so.5(GLIBCPP_3.2.2) is needed by rsct.core.cimrm-2.5.4.0-09252.i386
  MN_EX = 1
  
  The lib libstdc++.so.5 is in package libstdc++33-32bit which should be installed by pattern "base-32bit" through our autoyast file but it is not installed. This is a SLES10 SP3 bug, please refer to the Novell bugzilla 542277 for details. [Bug 56420] Novell542277- SLES10 SP3 GMC: on x86_64 "libstdc++33-32bit" is not installed using "base-32bit" pattern

Workaround 1:

Modify the autoyast template files /opt/csm/install/yastcfg.SLES10-x86_64.xml and /opt/csm/install/yastcfg.SLES10-x86_64-DC.xml to add package libstdc++33-32bit in "package" tag explicitly. Then issue csmsetupinstall and installnode.

Workaround 2:

After the OS installation, login the node and install libstdc++33-32bit manually then issue updatenode from MS.

Longevity: This is a SLES10 SP3 bug that may be fixed in the next Service Pack release.

• In the CSM Cluster-Ready Hardware Server environment, beginning with HMC V7.3.5.0, Open Source software "openslp" is used to setup SLP service on the HMC. It does not support the Broadcast package for SLP discovery, instead, openslp uses the Multicase package.
  
  As a result, CSM has changed the hardware discovery mechanism from Broadcast to Multicast, which requires Multicast support to be enabled on Ethernet switches.

Workaround:

For some Ethernet switches, Multicast support is enabled by default, such as Cisco Catalyst 2960 Series Switches. If it is not enabled by default, refer to your Switch Guides to enable Multicast.

• SELinux is disabled in the RedHatEL 5.3 default kickstart templates. This means that SELinux on RedHat EL 5.3 CSM managed nodes installed with default kickstart template file is disabled. This is due to a Red Hat SELinux bug that prevents the CSM and RSCT packages from being installed after the operating system installation.

Workaround:

If required, enable SELinux manually after the CSM full installation completes.

• CSM does not support Java5 communication to HMC version7 with SNIA/SSL.

Workaround:

Use Java 1.4 (or lower) version or set environment variable HC_JAVA_PATH=/usr/java14.

• When launching dsh command through DCEM, the dsh command will always fail with the error "Host is not responding. No command will be issued to this host".
  

Workaround:

Before running the command, clear the option "Before running commands, verify that targets are responding" in the Options tab.

• When executing a remote command via dsh on SLES 9 nodes, the remote command might fail because the command cannot be found on the nodes.

Workaround:

You need to specify the full path of the remote command.

• When installing SLES 10 managed nodes, the monitorinstall -r/-R command may not display the correct RPM name that is being installed, it sometimes displays "installing prep" instead of the RPM name.
• When running the mkflashfiles command without the "-f" flag, the command will attempt to process all the update code files it finds in the /csminstall/csm/fw directory. The command will not distinguish between different files for the same target platform (for example, the directory contains two BIOS update packages for System x3650 servers at two different BIOS levels). In this scenario it is possible the later version of the update package will be processed first, and then be overwritten by the older version of the package. For this reason, IBM recommends that only one update package per target platform reside in the /csminstall/csm/fw directory.
• CSM cannot be used to upgrade the SLES operating system on a node with an IDE hard drive, such as an BladeCenter HS20. The workaround is to reinstall the node with the new SLES service level instead of upgrading it.
• The installation of perl-RPM2 rpm will fail due to dependencies not matching the versions of the libraries in RHEL4.4 QU and later release . If you want to install perl-RPM2 rpm, you will need to recompile the perl-RPM2 package and copy it into the CSM package directories (or re-run copycsmpkgs with the recompiled perl-RPM2 file in the -p path).
• The CSM management server cannot connect to the Baseboard Management Controller (BMC) of a System x3455 server while the x3455 is performing a PXE boot broadcast during power up. This is due to a limitation in the x3455 that prevents access to the LAN interface of the BMC while the PXE boot broadcast is running. This blackout period can last anywhere from 30 seconds to one minute or more. During this time, the BMC will not respond to ping requests, and any power control or remote console requests will return a "Baseboard Management Controller is not responding" message. The behavior of a remote console session that was previously open when the PXE boot occurs depends on the setting of the csmconfig attribute "BMCConsoleKeepAlive". If the attribute is set to 0 (the default setting), there will be no indication that the session is lost, other than the console being non-responsive. The console session must be closed and then restarted when the BMC is available. If the attribute is set to 1, a message will be written to the console approximately 50 seconds after the IPMI session is lost, and the session will be closed. The session must be restarted when the BMC is available.
• The rfwflash command cannot be used to flash the Baseboard Management Controller (BMC) firmware on target nodes running Linux Operating System versions lower than Red Hat 4 QU3 or SLES 9 SP3.
  
  Customers that require BMC updates on older versions of the Operating System will need to manually install the OSA IPMI Driver and the IBM IPMI Mapping Layer for Linux packages on the target node before flashing the BMC. Note that the Mapping Layer package for Linux will be a source rpm.
  
  These packages are available for download from the IBM Support Web Site at http://www.ibm.com/support. To install the driver and mapping layer software, follow these steps:
  
1. Ensure that the packages for rpm, gcc, glibc, and kernel-source appropriate for the Operating System on the target node are installed.
2. Remove any existing installations of the OSA IPMI Driver and IBM IPMI Mapping Layer software.
3. Copy the new OSA Driver and IBM IPMI Mapping Layer packages to a temporary directory.
4. Use the rpm -i command to build and install the OSA IPMI drivers. If the build or installation fail, refer to the build.log file in the /usr/osa/ directory for more information. Once the errors detailed in the build.log file have been corrected, run the build_osadrv script located in the same directory to try the build and install steps again.
5. Run the ipmi_load script.
6. Build the IBM IPMI Mapping Layer installation package by running the command rpmbuild --rebuild . Note the name of the output Mapping Layer rpm written by the rpmbuild command.
7. Install the IBM IPMI Mapping Layer rpm.
• The rpower -b option is not working for System x 3455 nodes. The "-b" option to allow selection of the boot device to be used on the next power on or reboot does not work on System x 3455 servers. Any boot device specified will be ignored and the server will boot according to the boot order set in BIOS.
• Selected Linux Update Packages¹ that initiate DOS-based updates do not run under Red Hat EL 4 or SUSE LINUX Enterprise Server 9 Linux. These packages can usually be identified by their size, which is typically 2 MB or higher, compared to the standard lflash based package, which is usually under 1 MB.
• Selected Linux Update Packages¹ that initiate DOS-based updates cannot be run in a pre-Operating System environment. These packages modify the Master Boot Record of the target server to run DOS. In the pre-Operating System environment, the MBR is not available. These packages can usually be identified by their size, which is typically 2 MB or higher, compared to the standard lflash based package, which is usually under 1MB.
• The rfwflash command does not support flashing JS20 blade servers in a pre-Operating System environment. The JS20 servers must be managed by CSM and reachable by the dsh command.
• The rfwscan command is not supported on JS20 blade servers. Use the Blade Center management module web interface to view firmware levels for JS20 blade servers.
• When running commands that run rconsole such as getadapters , netboot , and installnode for an IVM-managed LPAR, other open consoles to that LPAR are forced closed. This is due to a limitation in the IVM firmware.
• reventlog -a or reventlog -e will hang when retrieving large event logs of 65K or greater. The event log size required to reproduce this problem is a log with approximately 800 entries; although, this number is dependent on the length of each entry since the real limiting factor is retrieving 65K or greater worth of data.
  As a workaround to running reventlog -a , run reventlog -e <#> , where <#> is some number (for example 500) that will not exceed the 65K limit. Since the log is returned in LIFO order, the last (most current) 500 entries will be returned.

CSM 1.7.1.11 is a service update level package for Release 1.7.1 Systems Management software for Linux on multiplatform. This package contains a full image for CSM software to support Linux on multiplatform hardware.

See the CSM for AIX and Linux documentation for further information.

RPMS

Software requisites (included in the package)

Problems fixed in CSM 1.7.1.11 [December 3,2010]

• Dsh fails if file descriptor set to unlimited with non-English environment.
• Dsh with -N & "-" doesn't handle noderange correctly.
• This update addresses the following APAR: IZ86620 IZ87774

Problems fixed in CSM 1.7.1.10 [September 9, 2010]

• Ignore invalid RTAS entries
• This update addresses the following APAR: IZ81389

Problems fixed in CSM 1.7.1.9 [August 2, 2010]

• Remove duplicate IP entries from ctrmc.mcptbl
• This update addresses the following APAR: IZ77443

Problems fixed in CSM 1.7.1.8 [June 10, 2010]

• OpenCIMOM is required by csm.server ptf update on AIX
• Copycds doesn't output error message when failed for disk full
• Change DR script to support post hybernation
• This update addresses the following APAR: IZ75845

Problems fixed in CSM 1.7.1.7 [April 29, 2010]

• lppchk error for csm.deploy inside wpar.
• rfwflash hangs for JS blade.
• rpower status stuck with HMC V7R7.
• This update addresses the following APARs: IZ72980 IZ73089

Problems fixed in CSM 1.7.1.6 [March 15, 2010]

• CRHS problem starting hdwr_svr with openssl installp package.
• This update addresses the following APARs: IZ66739 IZ69943

Problems fixed in CSM 1.7.1.5 [January 21, 2010]

• rpower query CEC status fail to work because of CIM event error.
• dsh returns errors when running some commands to Qlogic IB switches.
• cfmupdatenode -F option does not always work.
• This update addresses the following APARs: IZ67540 IZ58284

Problems fixed in CSM 1.7.1.4 [October 26, 2009]

• IBM.CSMAgentRM reports 2610-602 A session could not be established.
• IBM.HWCTRLRM socket connections remain in a CLOSE_WAIT state.
• This update addresses the following APARs: IZ55597 IZ57962 IZ58359

Problems fixed in CSM 1.7.1.3 [August 13, 2009]

• IBM.CSMAgentRM has disabled polling when running on a WPAR.
• Installing RedHat 5.3 from a POWER4 Install Server failing with an LED E143.
• This update addresses the following APARs: IZ54837 IZ54838 IZ54839

Problems fixed in CSM 1.7.1.2 [June 25, 2009]

• cfmupdatenode is not recognizing the "MinManaged-Installing" status
• This update addresses the following APARs: IZ50520 IZ52840

Problems fixed in CSM 1.7.1.1 [May 18, 2009]

• CSM Try-and-Buy license key is not allowed.
• healthCheck does not show unknown speed info on JS blade.
• HWSVRRMD core due to unreserved is being called.
• This update addresses the following APARs: IZ48411 IZ49810

Problems fixed in CSM 1.7.0.19 [April 16, 2009]

• checkpoint of WPAR is failing.
• csm.server prereq issue in multibos.
• This update addresses the following APARs: IZ42536 IZ47932 IZ47935

Problems fixed in CSM 1.7.0.18 [March 5, 2009]

• nodegrp issue when removing nodes.
• cfmupdatenode failing for filename containing ":"
• ibAdapterConfig updated to configure ml0.
• This update addresses the following APARs: IZ41004 IZ42902 IZ43362 IZ43614

Problems fixed in CSM 1.7.0.17 [January 26, 2009]

• dsh fails in non English locale.
• Performance enhancements for CSMAgentRM.
• csmsnap enhancements.
• cfmupdatenode coexistence update.
• This update addresses the following APARs: IZ38648 IZ39065 IZ39066 IZ39067

Problems fixed in CSM 1.7.0.16 [November 13, 2008]

• POWER6 FSP default IP addresses cause Version Mismatch issue in CRHS environment.
• getadapters with -D flag on POWER6 9117-MMA fails with "no adapters found".
• rpower reports wrong status when IBM.HWCTRLRM loses its connection to an HMC.
• dsh -v performance issue on large clusters.
• FSP Proxy Provider connect failures to POWER6 CECs.
• CSMAgentRM not setting certain IBM.ManagementServer attributes.
• This update addresses the following APARs: IZ31725 IZ33415 IZ34163 IZ35702 IZ34290

Problems fixed in CSM 1.7.0.15 [October 7, 2008]

• DLPAR function is unavailable in Power4 environment
• This update addresses the following APARs: IZ29205 IZ33416

Problems fixed in CSM 1.7.0.14 [September 19, 2008]

• Fix for netboot of CSP nodes.
• Update for Hardware Control Java daemon issue on large clusters
• Corrected a dsh issue where the hostname was appearing at the end of some lines.
• This update addresses the following APARs: IZ28845 IZ29741 IZ29195 IZ29199

Problems fixed in CSM 1.7.0.13 [July 24, 2008]

• Update to cfmupdatenode to correctly substitute meta variables.
• Update to cfmupdatenode to prevent files from being copied to incorrect nodes.
• Corrected a dsh issue where the hostname was appearing at the end of some lines.
• Fix for dsh -v reporting the node as not responding when LC_ALL is not C.
• SFP events monitoring updates for POWER5 and POWER6.
• This update addresses the following APARs: IZ20906 IZ21571 IZ23343 IZ23836 IZ23934 IZ26101 IZ26895

Problems fixed in CSM 1.7.0.12 [May 29, 2008]

• Update to dsh for noderanges.
• Fix for dlpar on POWER4 HMCs.
• IBM.HWSVRRM will now process updates to Element_Frame_ID and Element_BPA_MTMS in one request.
• Cluster-Ready Hardware Server updates.
• This update addresses the following APARs: IZ21571 IZ20709 IZ22352

Problems fixed in CSM 1.7.0.11 [May 2, 2008]

• Update IBM Tivoli System Automation for Multiplatforms (TSA) package to 2.3 FP3 to make the HA MS work properly.
• This update addresses the following APARs: IZ16405 IZ16865 IZ18109 IZ18204 IZ18791 IZ18792 IZ19460

Problems fixed in CSM 1.7.0.4 [February 7, 2008]

• Update to prevent hung child processes in dsh.
• RAS enhancement for cfmupdatenode.
• Correction to cfmupdatenode to maintain correct ownership of files.
• Change to certain predefined conditions to make the monitoring of the conditions more efficient.
• Fix for hwsdagent core dump.
• This update addresses the following APARs: IZ11547 IZ11548 IZ11549 IZ12233 IZ12748 IZ14050 IZ14370 IZ14374

Problems fixed in CSM 1.7.0.3 [December 6, 2007]

• Enhanced support for communication between the CSM MS and the 7.0 HMC using SSL.
• Update to predefined conditions that are shipped with CSM for more efficient monitoring.
• Corrected a condition where the ManagedNode Status attribute remains 127.
• This update addresses the following APARs: IZ08386 IZ09468 IZ10063

Problems fixed in CSM 1.7.0.1 [November 12, 2007]

• Support RHEL 5.1 GA.
• Improve updatenode command's performance.
• syslog monitoring performance enhancement.