Flex System Manager activities

Lenovo Integration Pack adds Lenovo PureFlex activities to Orchestrator Runbook Designer. The topics in this section describe how to use each of the Flex System Manager activities.

Input parameters

The following table lists the conventions for using the input parameters in the Flex System Manager activities.

Table 1. Conventions for input parameters

Input parameter	Indication
x	Parameter x is required.
[x]	Parameter x is optional.
(x)	Parameter x will be shown according to another parameter's value.
{ x | y | z }	Required alternative keywords are grouped in braces and separated by vertical bars.
[ x | y | z ]	Optional alternative keywords are grouped in brackets and separated by vertical bars.

Object types

The following table lists the object types for the input parameters and published data in the Flex System Manager activities.

Table 2. Object types for input parameters and published data

Object type	Indication
[Array]	[Array] indicates that the published data is an array.
Boolean	Boolean type
Enum	Enumeration type
Filter	Filter indicates that the published data can be used as an activity filter.
ManagedSystem	ManagedSystem information using the format: name, type, id
String	String type

System types for PureFlex systems

The following table lists the PureFlex system types for the input parameters and published data in the Flex System Manager activities.

Table 3. PureFlex system types

System type	Definition
Chassis	The physical resources that enclose other resources and provide definable functionality, such as a desktop, processing node, UPS, disk or tape storage, or a combination of these resources.
Cluster	A computer system that is made up of two or more computer systems that operate together to increase performance, reliability, availability, and serviceability.
ComputerSystem	A single or multiple computing entity that contains an operating system or firmware.
Farm	A group of systems that share a common goal, such as maintaining High Availability or streamlining processes.
GenericNetworkDevice	This class represents a computer system that has been discovered on a network for which the device type is not known.
HardwareManagementConsole	A computer system that controls managed systems, including logical partitions and the use of Capacity on Demand.
HybridSystem	A system that contains, in the case of zEnterprise, both CECs and BladeCenter.
OperatingSystem	Software responsible for forming an execution environment and allocating resources on a computing entity.
PassThroughModule	A computer system that is dedicated to managing pass-through network traffic rather than performing switching.
PowerUnit	A computing resource that is responsible for distributing or controlling power.
Server	A single node computer system such as a desktop, mobile device, or multipurpose server.
Storage Enclosure
StorageSubsystem	A computer system dedicated to acting as a storage server or array.
Switch	A computer system dedicated to acting as a switch for network traffic.
SystemChassis	A computer system that represents a modular enclosure containing blades.
SystemPool	A pool of networked systems with integrated virtualization and management software that manages the physical platform, the virtualization layer, and the virtual images that run within that set of systems.

• SM-Discover
  The FSM-Discover activity searches for and discovers resources on networks that are connected to the FSM server. The result of the search is stored in the FSM database. Use the FSM-Get-SystemList activity to obtain results from the database.
• FSM-Get-SystemList
  The FSM-Get-SystemList activity gets the managed system list according to the system type.
• FSM-Get-SystemInfo
  The FSM-Get-SystemInfo activity gets system information.
• FSM-Get-SystemAccessState
  The FSM-Get-SystemAccessState activity gets the system access state, which indicates whether FSM can communicate or access the target system.
• FSM-Access-System
  The FSM-Access-System activity grants FSM system access.
• FSM-Get-SystemPatterns
  The FSM-Get-SystemPatterns activity gets existing system patterns (Configuration Patterns).
• FSM-Get-SystemProfiles
  The FSM-Get-SystemProfiles activity gets the existing system profiles.
• FSM-Deploy-SystemPattern
  FSM uses patterns to create profiles and then deploys the profiles to systems. The FSM-Deploy-SystemPattern activity deploys and applies the system pattern to a system.
• FSM-Unassign-SystemProfile
  The FSM-Unassign-SystemProfile activity unassigns the profile from the system it is currently assigned to.
• FSM-Monitor-Event
  The FSM-Monitor-Event activity monitors system events.
• FSM-Monitor-Status
  The FSM-Monitor-Status activity monitors system status.
• FSM-Get-ActiveStatus
  The FSM-Get-ActiveStatus activity gets the active status of the target system.
• FSM-Collect-Inventory
  The FSM-Collect-Inventory activity collects the system inventory, which can then be retrieved by the FSM-Get-Inventory activity.
• FSM-Get-Inventory
  The FSM-Get-Inventory activity gets the system inventory that is collected by the FSM-Collect-Inventory activity. The inventory result can be viewed in either plain text or in html format.
• FSM-List-Chassis
  The FSM-List-Chassis activity lists all of the known chassis.
• FSM-Restart-CMM
  The FSM-Restart-CMM activity can either restart or initiate a failover of one or both of the CMMs of a Flex System Chassis.
• FSM-Run-Task
  The FSM-Run-Task activity executes noninteractive tasks that are available to the target system.
• FSM-Run-SMCLI
  The FSM-Run-SMCLI activity can run any smcli command on FSM. Manually enter the smcli command and its parameters.
• FSM-Upload-File
  The FSM-Upload-File activity uploads a local file (or folder) to the FSM server using the scp command. The file or folder is uploaded to the \home\userid\ path on the FSM. This activity fails if a the file with the same name already exists on the FSM.