Storage: Retrieve Information that does not Require a Session Handle (MTU, Timeout Values, Write Erase Limit)

Intel AMT Features > Storage Administration and Operations > Use Cases > Storage: Retrieve Information that does not Require a Session Handle (MTU, Timeout Values, Write Erase Limit)

Storage: Retrieve Information that does not Require a Session Handle (MTU, Timeout Values, Write Erase Limit)

The following parameters, relevant to storage operations, can be retrieved without first registering an application:

• MTU – When reading or writing data from or to a block of storage, there is a limit on how many bytes can be transferred at once. This is the Maximum Transmission Unit (MTU). Management applications should request the MTU from Intel AMT and restrict the size of their transfers to be no more than the amount returned.

• Timeout Values – Intel AMT uses timeouts for two storage operations: idle sessions and block locks. A management application can retrieve these values.

• Write Erase Limit – The write erase limit indicates how many more write operations may be performed on the NVM. Intel AMT makes this information available as well.

The following steps summarize how to retrieve these values.

1. Retrieve the instance of AMT_ThirdPartyDataStorageAdministrationService, where the “Name” key equals “Intel(r) AMT Third Party Data Storage Administration Service”.

2. Perform one or more of the following operations:

a. To retrieve the MTU, invoke AMT_ThirdPartyDataStorageService.GetMTU. The value is returned as an output parameter.

Click here for a snippet demonstrating this step

You can execute this snippet by inserting it into the execution template found here.

$thirdPartyDataStorageServiceRef =$wsmanConnectionObject.NewReference("SELECT * FROM AMT_ThirdPartyDataStorageService WHERE Name='Intel(r) AMT Third Party Data Storage Service'")

$inputObject =$thirdPartyDataStorageServiceRef.CreateMethodInput("GetMTU")

$outputObject =$thirdPartyDataStorageServiceRef.InvokeMethod($inputObject)

$returnValue =$outputObject.GetProperty("ReturnValue")

if($returnValue -like "0")

{

$mtu =$outputObject.GetProperty("Mtu")

}

b. To retrieve the timeout values associated with the session and with block locks, invoke AMT_ThirdPartyDataStorageService.GetTimeoutValues. The method returns the idle session timeout value and idle block lock timeout value as output parameters.

Click here for a snippet demonstrating this step

You can execute this snippet by inserting it into the execution template found here.

$thirdPartyDataStorageServiceRef =$wsmanConnectionObject.NewReference("SELECT * FROM AMT_ThirdPartyDataStorageService WHERE Name='Intel(r) AMT Third Party Data Storage Service'")

$inputObject =$thirdPartyDataStorageServiceRef.CreateMethodInput("GetTimeoutValues")

$outputObject =$thirdPartyDataStorageServiceRef.InvokeMethod($inputObject)

$returnValue =$outputObject.GetProperty("ReturnValue")

if($returnValue -like "0")

{

$registrationTimeout =$outputObject.GetProperty("RegistrationTimeout")

$lockTimeout =$outputObject.GetProperty("LockTimeout")

}

c. To retrieve the write erase limit for the NVM, invoke AMT_ThirdPartyDataStorage.GetWriteEraseLimit. The limit value is returned as an output parameter.

Click here for a snippet demonstrating this step

You can execute this snippet by inserting it into the execution template found here.

$thirdPartyDataStorageServiceRef =$wsmanConnectionObject.NewReference("SELECT * FROM AMT_ThirdPartyDataStorageService WHERE Name='Intel(r) AMT Third Party Data Storage Service'")

$inputObject =$thirdPartyDataStorageServiceRef.CreateMethodInput("GetWriteEraseLimit")

$outputObject =$thirdPartyDataStorageServiceRef.InvokeMethod($inputObject)

$returnValue =$outputObject.GetProperty("ReturnValue")

if($returnValue -like "0")

{

$writeEraseLimit =$outputObject.GetProperty("WriteEraseLimit")

}

Instance Diagram

Not applicable

Classes Used in This Flow

• AMT_ThirdPartyDataStorageService

SDK Sample

If there is a sample demonstrating this flow, it is included in the SDK installation file. See SDK Installation Layout for details.