tree 0cf22b262ed00c50f2a9a3c3331107c3cf68610a
parent 0f0bd53e1e7d09f589cf3f16169e5cdc94bc5e1e
author chithrag <chithrag@ami.com> 1647079960 +0000
committer chithrag <chithrag@ami.com> 1651735067 +0000

Added new script for inband SDR comands - Get SDR, Get Device SDR Info, Reserve Device SDR Repository and Get Device SDR IPMI commands

Testcases Added :
   - Verify Get SDR For Maximum Record Via IPMI
   - Verify Sensor And SDR Count In Get Device SDR Info Via Inband IPMI
   - Verify Timestamp In Get Device SDR Info Via Inband IPMI
   - Verify Get Device SDR Info For Invalid Data Request
   - Verify Device SDR Info Via IPMI Lanplus
   - Verify Reserve Device SDR Repository Via Inband IPMI
   - Verify Reserve Device SDR Repository For Invalid Data Request
   - Verify Reserve Device SDR Repository Info Via IPMI Lanplus
   - Verify Reserve Device SDR Repository For Partial Record
   - Verify Reserve Device SDR Repository For Partial Record After BMC Reboot
   - Verify Reserve Device SDR Repository Invalid Reservation ID For Partial Record
   - Verify Get Device SDR For Maximum Record Via IPMI
   - Verify Get Device SDR For Invalid Data Request Via IPMI

Request data for Device SDR present in data/ipmi_raw_cmd_table.py
Zfill Data keyword available in lib/utils.py - committed in - https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-test-automation/+/51641

For Get Device SDR Info, Sensor and sdr counts are compared with sensor list and sdr elist all respectively. Timestamps of both sensor and sdr data are validated.

Reserve Device SDR Repository and Get Device SDR Info should be accessible only via KCS interface and not via Lanplus interface.

Get SDR and Get Device SDR verifies maximum number Record IDs with their immediate next Record IDs.

Tested: Run robot ipmi/test_ipmi_inband_sdr.robot

Signed-off-by: chithrag <chithrag@ami.com>
Change-Id: Ia69fd02f44cb64f6341f95f987e159ee85f76a5b