Policy wise, we have shied from scripting CLI commands as in many cases
human factors concerns can cause changes that break parsers (see struggles
in xCAT 1.x with different Cisco CatOS firmware levels changing layout of
various commands).  The SNMP interfaces of these same systems are largely
immune to this sort of concern.  I'm not aware of BladeCenter experiencing
a CLI change, but I also haven't been looking too hard.

Conversely, since xCAT is not the only consumer of the SNMP interface,
improving the AMM behavior is the correct course anyway.  Given that we are
endeavoring to correct the slowness, a blade plugin rewrite would likely
complete after the SNMP interface is hopefully working better again and the
effort would be largely moot.



From:   Arif Ali <[email protected]>
To:     [email protected],
Date:   11/03/2011 05:47 AM
Subject:        Re: [xcat-user] Bladecenter rbeacon issue



Hi Jarrod,

Why not use something like

led -loc on -T blade[1]

or will that cause too many ssh connections?
Arif Ali

catch me on freenode IRC, username: arif-ali

On 02/11/11 11:56, Jarrod B Johnson wrote:


      I just checked in a change to increase the timeouts on the rbeacon
      and rvitals commands. Regrettably, SNMP commands involving LED
      requests can take up to 5 minutes to be fulfilled by the AMM, during
      which the AMM will not respond to other SNMP requests. This is under
      investigation. Non-snmp interfaces are not impacted by this behavior.

      Arif Ali ---11/01/2011 06:46:51 PM---Hi all, not sure if anyone is
      aware of this. It seems that the rbeacon on the

      From: Arif Ali <[email protected]>
      To: "Mailing list, xCAT" <[email protected]>,
      Date: 11/01/2011 06:46 PM
      Subject: [xcat-user] Bladecenter rbeacon issue





      Hi all,

      not sure if anyone is aware of this. It seems that the rbeacon on the
      bladecenter causes the bladecenter AMM to become unresponsive for
      about 5-10 seconds. rpower group stat works every single time, but
      rbeacon group on, would hang on the initial nodes and work ok on the
      rest. But cause timeout issues on it

      Is there anything I need to be aware of in this situation wrt to snmp
      or ssh to the AMM
      --
      Arif Ali

      catch me on freenode IRC, username: arif-ali
      
------------------------------------------------------------------------------

      RSA&#174; Conference 2012
      Save $700 by Nov 18
      Register now&#33;
      http://p.sf.net/sfu/rsa-sfdev2dev1
      _______________________________________________
      xCAT-user mailing list
      [email protected]
      https://lists.sourceforge.net/lists/listinfo/xcat-user



      This body part will be downloaded on demand.


      This body part will be downloaded on demand.[attachment "mail.vcf"
      deleted by Jarrod B Johnson/Raleigh/IBM] [attachment "smime.p7s"
      deleted by Jarrod B Johnson/Raleigh/IBM]
      
------------------------------------------------------------------------------

      RSA(R) Conference 2012
      Save $700 by Nov 18
      Register now
      http://p.sf.net/sfu/rsa-sfdev2dev1
      _______________________________________________
      xCAT-user mailing list
      [email protected]
      https://lists.sourceforge.net/lists/listinfo/xcat-user

<<inline: graycol.gif>>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to