2 Replies Latest reply: Apr 5, 2011 9:40 AM by 841725 RSS

    es-cli Error getting the alarms with getAlarms

    841725
      Hi All,

      We are using Sun Management Center Server Version 4.0 Build: 15,H491 and I am haveing a problem seeing alarms for all clients. We would really appreciate any help.

      This is what I am doing and the results:
      $ /opt/SUNWsymon/sbin/es-cli
      Copyright (c) 2007 Sun Microsystems, Inc. All rights reserved.
      Use is subject to license terms.
      login
      Host: hostname
      Password: ********
      Login is successful.
      getLoadedModules a=rdfnur01
      The command is currently running in the background.

      >
      The command has ended its operation.
      print
      == getLoadedModules: Results 1/3 ===============================================
      Module Name=Common Config Reader
      Module Key=Config-Readerelp
      Description=Common Config Reader Module
      Agent Name=rdfnur01
      Agent Port=1161
      Version=1.0
      == getLoadedModules: Results 2/3 ===============================================
      Module Name=Kernel Reader
      Module Key=kernel-reader
      Description=Kernel Reader
      Agent Name=rdfnur01
      Agent Port=1161
      Version=2.0
      == getLoadedModules: Results 3/3 ===============================================
      Module Name=File Scanning [var/adm/messages Log]
      Module Key=fscan+syslog
      Description=File Scanning
      Agent Name=rdfnur01
      Agent Port=1161
      Version=2.0
      ================================================================================
      getAlarms -l
      Using the last output as the input to the current command...
      The command is currently running in the background.

      >
      The command has ended its operation.
      print
      == getAlarms: Results 1/1 ======================================================
      Domain=IMS Core Nodes
      Agent Name=rdfnur01
      Agent Port=1161
      State=Fail
      Message=Error getting the alarms.
      ================================================================================
      getAlarms a=rdfnur01
      The command is currently running in the background.

      >
      The command has ended its operation.
      print
      == getAlarms: Results 1/1 ======================================================
      Domain=IMS Core Nodes
      Agent Name=rdfnur01
      Agent Port=1161
      State=Fail
      Message=Error getting the alarms.
      ================================================================================
      getAlarms a=rdfnur01
      The command is currently running in the background.

      >
      The command has ended its operation.
      print
      == getAlarms: Results 1/1 ======================================================
      Domain=IMS Core Nodes
      Agent Name=rdfnur01
      Agent Port=1161
      State=Fail
      Message=Error getting the alarms.
      ================================================================================
      >
        • 1. Re: es-cli Error getting the alarms with getAlarms
          Mike Kirk
          Hello user13499843,

          If you click on the "Alarms" tab for that Agent (rdfnur01) in the Java Console, do you see alarms there either? Do you see alarms in the Alarms tab for any of your Agents? If not... have you applied patches 143323-04 (SPARC) or 143324-05 (x86) on your SunMC Server? Those patches break the Alarms tab in SunMC (a regression) and would also break es-cli in the way that you posted.

          Solution: downgrade to 143323-03/143324-04 ... once your Alarms tab works in the Java Console es-cli should work for you as well. You may also want to check the versions of your other SunMC patches (http://forums.halcyoninc.com/showthread.php?t=104)

          Regards,

          Mike.Kirk@HalcyonInc.com
          • 2. Re: es-cli Error getting the alarms with getAlarms
            841725
            Hi Mike,

            Thanks for the quick response.
            We currently have no alarms from that agent, but the alarm tab works fine. We occasionally have alarms and can see them on the alarm tab of the gui, but not in the cli. In the cli we receive the same error as described in my original post.

            Thanks!