ISO8859-1>A X; : ; L MS Q G @ F M  s9 FNC/9>?7~QGFPNQo8\2o`U`: H!':"=b#T$T%J&'iW()lN*+lH,-O>.=/x0WE1{2Z3{t4Z5K6}7N89y: ; < = >%!U!5 "G","t"`"I"#9 ]#L ^# $ s$ q$%f% %t%%%A%%%&'&&>S&F.&'n'(H(P (!5(")0#+)5$)a%)q& *H'@*R(*)l** ++]+,+s-+.+/+0+1 +2+3+4"+5,6=,+7 ,i8,u9,:#,;[,<}-&=->x-? .1@.>A.SBG.gC.D6.E .F.G/H/I 0J0K0Lr0M1QNS1oO1P1Q 1R1S 2T 2 U2A;2V30C3I33\3E44J Y4] Z4 5 o5( q56 b66u66686666&7 73J7;%78n89+93 9!I9":#":0$:S%:c& ;1'c;;( ;)Y;*N<+ 7?8?&9 @B:@N; A8A C bCCCsCqDD cD D 8E EG .EYE>EEFF.F.F]Fq F F F=FGG"G?.GPGG G!G" G##G$ G%;H&HD'=Ha(H)H*H+#H, I-#I. IA/*IO0Iz12I2I3I4J5#J6 J67!JD8Jf'7JKLKL$L5eL>NLL bM cMi M xM qN\NkNOBOXO]OpVOyOOO4PPHgPP2PQnQRjRr S!WS!"Sy#LS~$S%4S& T'bT"T~U@NUZUU_UqV(V .V V V W W%WE+WYW=WW,WXX(X>XGXd<Xt%XXX,XY,Y; YW!Yk"YY ZDZPqZYZfZ[:[P [U [h [q 0[y \n\])]1]<]^T^^j2613-000 The attribute %1$s is read-only and cannot be modified. 2613-001 The class action specified by ID %1$d is invalid. 2613-002 The class action requires structured data input. 2613-003 The structured data input requires %1$d elements. 2613-004 The structured data input element data type is incorrect for %1$s. 2613-005 PKE could not start a session with %1$s. The %2$s function returned %3$d. 2613-006 When invoking the %1$s action on %2$s, the %3$s function returned %4$d. 2613-007 PKE did not receive the expected response for %1$s from %2$s. 2613-008 PKE received an error response for %1$s from %2$s: %3$d %4$s 2613-009 The structured data input element data value is not valid for %1$s. 2613-010 Encryption error. 2613-011 The chrmcacl command terminated with status %1$d. See /var/ct/IW/run/mc/IBM.MgmtDomainRM/chrmcacl.stderr. 2613-012 The chrmcacl command terminated abnormally with status %1$d. 2613-013 Error detected when attempting to update the THL for %1$s using %2$s 2613-014 Error number %1$d was detected while evaluating the select string "%2$s". RH = "0x%3$04x 0x%4$04x 0x%5$08x 0x%6$08x 0x%7$08x 0x%8$08x". 2613-015 The attribute %1$s must be specified. 2613-016 PKE timed out with the node at IP address %1$s. 2613-017 The attribute %1$s cannot specify the local Node ID. 2613-018 Cannot fetch RTAS data, error number is %1$d. 2613-019 When invoking the %1$s action on %2$s, the %3$s function returned %4$d. 2613-020 MDC did not receive the expected response for %1$s from %2$s. 2613-021 MDC received an error response for %1$s from %2$s: %3$d %4$s 2613-022 The invalid IP address %1$s has been found in RTAS slot number %2$d. 2613-023 The data in RTAS slot number %1$d is invalid. The error number is %2$d. 2613-024 MDC could not start a session with %1$s, from RTAS slot number %2$d. The %3$s function returned %4$d. 2613-025 MDC could not obtain a local IP address for the session with %1$s, from RTAS slot number %2$d. The %3$s function returned %4$d. 2613-026 MDC could not establish a session with the HMC specified in RTAS slot number %1$d. 2613-027 MDC detected a protocol error with the HMC specified in RTAS slot number %1$d due to prior error %2$s 2613-028 MDC could not obtain local system information. Error type is %1$d. Error code is %2$d. 2613-029 The Management Console does not support IPv6 addresses. IP address is %1$s. 2613-030 A host name cannot be found for IP address %1$s. 2613-031 An invalid key length has been found in RTAS slot number %1$d. 2613-032 Cannot create message digest. 2613-033 MDC protocol contains an invalid message signature. 2613-034 Error number %1$d was returned when attempting to define an %2$s resource. 2613-035 Error number %1$d was returned when attempting to remove an %2$s resource. 2613-036 When attempting to change the attribute of an %1$s resource, error number %2$d was returned. The attribute name is %3$s. 2613-037 MDC could not configure a new resource for the Mangement Console with the name "%1$s" and address %2$s due to prior error %3$s. 2613-038 MDC configured a new resource for the Management Console with the name "%1$s" and address %2$s. 2613-039 MDC could not update an existing resource for the Mangement Console with the name "%1$s" and address %2$s due to prior error %3$s. 2613-040 MDC updated an existing resource for the Management Console with the name "%1$s" and address %2$s. 2613-041 MDC could not remove an existing resource for the Mangement Console with the name "%1$s" and address %2$s due to prior error %3$s. 2613-042 MDC removed an existing resource for the Management Console with the name "%1$s" and address %2$s. 2613-043 Expected values are missing for the attributes in the list %1$s. RH = "0x%2$04x 0x%3$04x 0x%4$08x 0x%5$08x 0x%6$08x 0x%7$08x". 2613-044 Error detected when attempting to generate a key for %1$s using %2$s. 2613-045 Error %1$d returned when calling the function %2$s. 2613-046 MDC could not configure a new resource for the LPAR with name "%1$s" and address %2$s due to prior error %3$s. 2613-047 MDC configured a new resource for the LPAR with name "%1$s" and address %2$s. 2613-048 MDC could not update an existing resource for the LPAR with name "%1$s" and address %2$s due to prior error %3$s. 2613-049 MDC updated an existing resource for the LPAR with name "%1$s" and address %2$s. 2613-050 MDC could not remove an existing resource for the LPAR with name "%1$s" and address %2$s due to prior error %3$s. 2613-051 MDC removed an existing resource for the LPAR with name "%1$s" and address %2$s. 2613-052 The Management Console could not accept the request to be managed from an LPAR due to its unsupported protocol number %1$d 2613-053 The Management Console could not accept the request to be managed from an LPAR due to a missing key for CEC ID %1$s 2613-054 The Management Console could not accept the request to be managed from an LPAR due to an error updating the THL file for input element ID %1$d 2613-055 The Management Console could not accept the request to be managed from an LPAR due to an error while trying to fetch the local hostname 2613-056 The Management Console could not accept the request to be managed from an LPAR due to an error while trying to fetch the local network interfaces 2613-057 The Management Console could not accept the request to be managed from an LPAR due to an error while trying to convert its hostname to a set of IPs 2613-058 RMC Disconnect error. 2613-059 RMC Response error. 2613-060 MCP Undefine error. 2613-061 MDRM Command timeout error. The IBM.MngNode resource class, along with the IBM.MCP resource class, is used to define a Management Domain. Each IBM.MngNode resource created on the Management Control Point defines another managed node in the Management Domain.Managed NodeWhenever an IBM.MngNode resource is defined this attribute is asserted.Resource DefinedInternalThe example event expression generates an event whenever a new IBM.MngNode resource is created.Whenever an IBM.MngNode resource is undefined this attribute is asserted.Resource UndefinedThe example event expression generates an event whenever an IBM.MngNode resource is removed.Whenever an IBM.MngNode resource is defined, undefined or changed this attribute is asserted.Configuration ChangedThe example event expression generates an event whenever an IBM.MngNode resource is defined, undefined or changed.Identifies the specific defined class attributes and actions that apply to this variation of the resource class.VarietyWhenever the persistent attributes of an IBM.MngNode resource are changed this attribute is asserted.Configuration ChangedNoneAttributes changedInternalThis attribute reflects the heartbeat status of the managed node.StatusThe node is down.The node is up.The node's heartbeat status is unknown.GeneralThe example event expression generates an event whenever a managed node is not up.A globally unique handle that identifies the managed node. Every resource is assigned a resource handle, which is used internally for identifying and locating each resource. The resource handle is fixed in size and avoids the problems of name space collisions across different types of resources.Resource HandleIdentifies the specific defined resource attributes and actions that apply to this variation of the resource.VarietyIdentifies the location of the resource that represents the managed node. While this attribute is an array data type, it only ever contains one entry.Node IdentifiersIdentifies the primary host name of the managed node.NameIdentifies the Node ID of the managed node.Node IdentifierSpecifies the Host Identity that is used to look up the public key of the managed node in the Trusted Host List on the MCP. This value is typically the fully qualified host name or IP address of the managed node.Key TokenSpecifies one or more additional host names of the managed node.AliasesSpecifies a list of IP addresses assigned to the managed node. Each address should be on a separate subnet.IP AddressesThe example event expression generates an event whenever an IBM.MngNode resource is changed.Hardware Type.HWTypeHardware model number.HWModelHardware serial number.HWSerialNumLogical Partition Identifier.LParIDStorage facility image identifier.StorageFacilityImageIDThis attribute reflects the power status of the managed node.PowerStatusThe node's power is off.The node's power is on.The node's power status is unknown.The example event expression generates an event whenever a managed node's power is not on.This action is a request to the resource manager to update the power status of the managed node represented by the resource.Update Power StatusThe new power status value for the resource. A value of 0 indicates power is off. A value of 1 indicates power is on.Power StatusSet Power Status offSet Power Status onThis action is a request to the resource manager to add a new partitionAdd LPARThe name of the new LPAR as LParID*HWModel*HWSerialNumLPAR NameThis resource action can be used to affect heartbeat status between lpar (Managed Node) and HMC (Management Control Point) of represented by the resource.Update Heatbeat StatusThe new suspend state value for the resource. A value of 0 will trigger suspension of heartbeat between managed node (lpar) and management control point. A value of 1 will resume heartbeat between managed node (lpar) and management control point.Suspend StateSet Suspend State OnSet Suspend State OffThe value (in no. of seconds) is the total time for resource manager to wait to change the desired suspend state.Number of Seconds for timeoutThis resource action can be used to query node status of local node at remote node.Get Node StateThe state of local node.Local State.The state of remote node.Remote State.The suspend state of local node.Local Suspend State.The IBM.MCP resource class, along with the IBM.MngNode resource class, is used to define a Management Domain. Each IBM.MCP resource created on a managed node defines a Management Control Point for that managed node.Management Control PointWhenever an IBM.MCP resource is defined this attribute is asserted.Resource DefinedInternalThe example event expression generates an event whenever a new IBM.MCP resource is created.Whenever an IBM.MCP resource is undefined this attribute is asserted.Resource UndefinedThe example event expression generates an event whenever an IBM.MCP resource is removed.Whenever an IBM.MCP resource is defined, undefined or changed this attribute is asserted.Configuration ChangedThe example event expression generates an event whenever an IBM.MCP resource is defined, undefined or changed.Identifies the specific defined class attributes and actions that apply to this variation of the resource class.VarietyWhenever the persistent attributes of an IBM.MCP resource are changed this attribute is asserted.Configuration ChangedNoneAttributes changedInternalThis attribute reflects the heartbeat status of the MCP.StatusThe MCP is down.The MCP is up.The MCP's heartbeat status is unknown.GeneralThe example event expression generates an event whenever a MCP is not up.A globally unique handle that identifies the MCP. Every resource is assigned a resource handle, which is used internally for identifying and locating each resource. The resource handle is fixed in size and avoids the problems of name space collisions across different types of resources.Resource HandleIdentifies the specific defined resource attributes and actions that apply to this variation of the resource.VarietyIdentifies the location of the resource that represents the MCP. While this attribute is an array data type, it only ever contains one entry.Node IdentifiersIdentifies the primary host name of the managed node as known to the MCP.Managed Node NameIdentifies the Node ID of the MCP.Node IdentifierSpecifies the Host Identity that is used to look up the public key of the MCP in the Trusted Host List on the managed node. This value is typically the fully qualified host name or IP address of the MCP.Key TokenSpecifies a list of IP addresses assigned to the MCP. Each address should be on a separate subnet.IP AddressesThe example event expression generates an event whenever an IBM.MCP resource is changed.Names which the Management Control Point can use to connect back to this node.ConnectivityNamesThe value of the 'HscName' field found in the RTASHMCNameThe value of the 'HscIPAddr' field found in the RTASHMCIPAddrThe value of the 'HscAddIPs' field found in the RTASHMCAddIPsThe value of the 'HMCAddIPv6s' field found in the RTASHMCAddIPv6sThis action is a request to the resource manager to harvest RTAS information and update the Management Domain configuration if appropriate.Harvest RTAS InformationSpecification of RTAS slots to be examined for change. A value of 0 indicates to examine all slots. Otherwise, it is a bit encoded value where Bit 0 is slot 0, Bit 1 is slot 1, through Bit 15 is slot 0xF. A bit value of 1 indicates to examine the corresponding slot.Slot SpecifierStatus of RTAS slots after examination. A value of 0 indicates no error. Otherwise, it is a bit encoded value where Bit 0 is slot 0, Bit 1 is slot 1, through Bit 15 is slot 0xF. A bit value of 1 indicates the action must be invoked again for the corresponding slot sometime later.Slot StatusThis action reports RTAS entries and their detailed status. The action output will return the same information provided in the IBM.MCP DetailStatus attribute along with slot and HMC identification.QueryRTASThe IBM.PublicKeyExchange resource class is used by the IBM.MgmtDomainRM to exchange the public keys of each MCP and managed node pair in a Management Domain. This exchange is done automatically as IBM.MCP resources are created on each managed node. Note that the IBM.MngNode resource must be created first on the MCP before the IBM.MCP resource is created on the managed node. Public key exchange can also be initiated by executing the command "refrsrc IBM.MCP" on the managed node.Public Key ExchangeWhenever a successful Public Key Exchange protocol has been performed this attribute is asserted.Configuration ChangedInternalThe example event expression generates an event whenever a Public Key Exchange protocol is successfully performed.Identifies the specific defined class attributes and actions that apply to this variation of the resource class.VarietyThis class action is used to determine the version of the Public Key Exchange protocol to be used.Negotiate Protocol VersionsList of protocol versions supported by the Managed node.Protocol VersionsHighest protocol version supported by the MCP.Maximum Supported VersionThis action is Phase Zero of the Public Key Exchange protocol.Phase Zero Public Key ExchangeThe protocol version in use.Protocol VersionUnique identifier of protocol being performed.Protocol IdentifierPublic key of managed node.Public KeyIP addresses of the managed nodeIP AddressesThis action is Phase One of the Public Key Exchange protocol.Phase One Public Key ExchangeThe protocol version in use.Protocol VersionUnique identifier of protocol being performed.Protocol IdentifierPublic key of MCP.Public KeyIP addresses of the MCPIP AddressesChallenge from MCP to managed node.Challenge OneProtocol identifier of protocol originated by managed node.Returned Protocol IdentifierThis action is Phase Two of the Public Key Exchange protocol.Phase Two Public Key ExchangeThe protocol version in use.Protocol VersionChallenge from MCP to managed node.Challenge OneChallenge from managed node to MCP.Challenge TwoEncrypted node identifier of managed node.Encrypted Node IdentifierProtocol identifier of protocol originated by MCP.Returned Protocol IdentifierThe protocol version in use.Protocol VersionChallenge from managed node to MCP.Challenge TwoEncrypted node identifier of MCP.Encrypted Node IdentifierResources of the IBM.MngNodeNetIF resource class are automatically created as resources of the IBM.MngNode resource class are created, one per IP address configured to a managed node. As IP addresses are added or removed to or from managed nodes, IBM.MngNodeNetIF resources are added or removed accordingly.Managed Node Network InterfaceWhenever an IBM.MngNodeNetIF resource is defined this attribute is asserted.Resource DefinedInternalThe example event expression generates an event whenever a new IBM.MngNodeNetIF resource is created.Whenever an IBM.MngNodeNetIF resource is undefined this attribute is asserted.Resource UndefinedThe example event expression generates an event whenever an IBM.MngNodeNetIF resource is removed.Whenever an IBM.MngNodeNetIF resource is defined, undefined or changed this attribute is asserted.Configuration ChangedThe example event expression generates an event whenever an IBM.MngNodeNetIF resource is defined, undefined or changed.Identifies the specific defined class attributes and actions that apply to this variation of the resource class.VarietyWhenever the persistent attributes of an IBM.MngNodeNetIF resource are changed this attribute is asserted.Configuration ChangedNoneAttributes changedInternalThis attribute reflects the heartbeat status of the managed node's network interface.StatusThe network interface is down.The network interface is up.The network interface's heartbeat status is unknown.GeneralThe example event expression generates an event whenever a managed node's network interface is not up.A globally unique handle that identifies the network interface. Every resource is assigned a resource handle, which is used internally for identifying and locating each resource. The resource handle is fixed in size and avoids the problems of name space collisions across different types of resources.Resource HandleIdentifies the specific defined resource attributes and actions that apply to this variation of the resource.VarietyIdentifies the location of the resource that represents the network interface. While this attribute is an array data type, it only ever contains one entry.Node IdentifiersIdentifies the primary host name of the managed node containing the network interface.NameIdentifies the Node ID of the managed node containing the network interface.Node IdentifierSpecifies the IP addresses of the network interface.IP AddressThe example event expression generates an event whenever an IBM.MngNodeNetIF resource is changed.The IBM.MngNodeAuthenticate resource class is used by the IBM.MgmtDomainRM to allow unauthenticated nodes to be able to invoke its two actions. Its two actions may allow a node to be managed.Managed Node AuthenticateWhenever a successful protocol has been performed this attribute is asserted.Configuration ChangedInternalThe example event expression generates an event whenever a protocol is successfully performed.Identifies the specific defined class attributes and actions that apply to this variation of the resource class.VarietyAction to get the list of supported protocols.Get Supported ProtocolsProtocols supported by the node.Supported Client ProtocolsProtocols supported by the MCP.Supported ProtocolsAction to request the MCP to manage a node.Request Node ManagementThis argument is used to identify the version of the request.Paramter VersionMessage digest used to validate the request.Message DigestHostname of the node.HostnameNode identifier of the node.Node IdentifierString containing the machine type, model and serial number.Machine Type, Model and Serial NumberPublic Key of the node.Node Public KeyMessage digest used to validate the request.Message DigestNode identifier of the MCP.MCP Node IdentifierPublic key of the MCP.Management Server Public KeyThe IBM.RMCCtrl resource class implicitly defines a single resource. Attributes of this resource are used to specify configuration parameters for the RMC subsystem.RMC ControlInternalIdentifies the specific defined class attributes and actions that apply to this variation of the resource class.VarietyWhenever the persistent attributes of an IBM.RMCCtrl resource are changed this attribute is asserted.Configuration ChangedNoneAttributes changedInternalGeneralA globally unique handle that identifies the IBM.RMCCtrl resource. Every resource is assigned a resource handle, which is used internally for identifying and locating each resource. The resource handle is fixed in size and avoids the problems of name space collisions across different types of resources.Resource HandleIdentifies the specific defined resource attributes and actions that apply to this variation of the resource.VarietyIdentifies the location of the IBM.RMCCtrl resource. While this attribute is an array data type, it only ever contains one entry.Node IdentifiersNumber of seconds between heartbeat messages sent to a node.Heartbeat FrequencyNumber of missed heartbeat messages sent to a node to declare that node unreachable.Heartbeat Sensitivity