OCP Custom Config

The SANBlaze OCP api allows users to override certain behaviors by setting values in the ocp.conf file.

Note

The ocp.conf is located on the vlun at /virtualun/python_usr/ocp.conf

Any flags that are set will be logged in script as follows:

<< EXAMPLE HERE>>

StopOnFirstError

This flag allows users to continue testing even when the first error is found.

Enable = True (Default behavior)

  • Stops the test when the first error is found.

Enable = False

  • Continue the test even the errors are encountered.

[StopOnFirstError]
Enable=True

Certification Mode

This flag allows users to modify the behavior of ADP file verification.

Enable = True (Default behavior)

  • If the current running firmware is incorrect per ADP file, the test will stop.

  • If the ADP file encounters an incorrect format or an unknown parameter, the test will stop immediately and skip the test.

Enable = False

  • Allow checking the current running firmware to be skipped.

  • If the ADP file encounters an incorrect format or an unknown parameter, a warning message will be logged and the test will continue.

[Certification Mode]
Enable=True

ADP Override

Beginning with OCP 2.6 users will have an option to begin testing without a full ADP file to let them focus on debug. This is intended for testing and means the drive run is not valid for certification with Microsoft.

How it works:

  1. Enable the feature

[ADP Override]
enable = true

  1. Define the critical information for a test to run for each firmware version

[ADP Override]
enable = true

[FWV123]
CUR_FW_FN = FWV123.file
PREV_FW_FN = FWV122.file

3) Anywhere in the scripts that a value is obtained from the drive, instead of checking the drives reported value with the matching value in the parameters file, there will be a skip message log indicating that a adaptation parameters check is being skipped.

Using multiple firmware versions

When using multiple firmware versions, just add sections for each fimware version defining the required information

[ADP Override]
enable = true

[FWV123]
CUR_FW_FN = FWV123.file
PREV_FW_FN = FWV122.file

[FWV124]
CUR_FW_FN = FWV124.file
PREV_FW_FN = FWV123.file

Required parameters

Note

Some parameters are required to be specified by the user before running certain tests, such as those related to firmware. A list of these required parameters is listed below. The examples shown are just for reference. Put in the correct values for each parameter.

FORM_FACTOR = E3.S

PREV_FW_REV = 1.0.0 CUR_FW_REV = 1.0.0 UNSEC_FWRV1 = 1.00 UNSEC_FWRV2 = 1.00

SEC_FWRV1_PK1_SV1 = 1.00 SEC_FWRV1_PK1_SV2_FN = FwFilename.bin SEC_FWRV1_PK2_SV2_FN = FwFilename.bin

SEC_FWRV2_PK1_SV1 = 1.00 SEC_FWRV2_PK1_SV1_FN = FwFilename.bin SEC_FWRV2_PK1_SV2_FN = FwFilename.bin

OLD_FW_REV = 1.00 NEW_FW_REV = 1.00

Factory

Warning

Factory mode is primarily for script debug and development and not intended for customer use. For most instances,

the Certification Mode will provide more useful test runs.

Factory mode

  • Skips preconditioning

  • Does not verify firmware version with adp file

  • Does not enforce namespace size