From a2209046543ccaae5cd391fe69346d4a47ee557f Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Sun, 2 Jun 2024 18:07:19 -0700
Subject: [PATCH 1/8] Added some more test cases

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 498 +++++++++++++++++++++
 1 file changed, 498 insertions(+)
 create mode 100644 docs/testplan/SmartSwitch-PMON-testplan.md

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
new file mode 100644
index 0000000000..e8ddba6355
--- /dev/null
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -0,0 +1,498 @@
+# SmartSwitch PMON Test Plan
+
+- [Introduction](#introduction)
+- [Scope](#scope)
+- [Definitions and Abbreviations](#definitions-and-abbreviations)
+- [Test Cases](#test-cases)
+    - [1.1 Check SmartSwitch specific ChassisClass APIs](#11-check-smartswitch-chassis-apis)
+    - [1.2 Check modified ChassisClass APIs](#12-check-modified-chassis-apis)
+    - [1.3 Check DpuModule APIs for SmartSwitch](#13-check-dpu-module-apis)
+    - [1.4 Check modified ModuleClass APIs](#14-check-modified-module-apis)
+    - [1.5 Check SwitchModule APIs for SmartSwitch](#15-check-switch-module-apis)
+    - [1.6 Check the show reboot-cause CLI on the DPU](#16-check-dpu-reboot-cause-cli)
+    - [1.7 Check the show reboot-cause history CLI on the DPU](#17-check-dpu-reboot-cause-history-cli)
+    - [1.8 Check the show reboot-cause CLI on the SWITCH](#18-check-switch-reboot-cause-cli)
+    - [1.9 Check the show reboot-cause history CLI on the SWITCH](#19-check-switch-reboot-cause-history-cli)
+    - [1.10 Check the show system-health summary CLI on the SWITCH](#110-check-switch-system-health-summary-cli)
+    - [1.11 Check the show system-health monitor-list CLI on the SWITCH](#111-check-switch-system-health-monitorlist-cli)
+    - [1.12 Check the show system-health detail CLI on the SWITCH](#112-check-switch-system-health-detail-cli)
+    - [1.13 Check the show system-health dpu DPUx CLI on the SWITCH](#112-check-dpu-state-cli)
+
+## Introduction
+
+The purpose is to test the SONiC PMON functionality of SmartSwitch platform.
+
+## Scope
+
+The primary goal is to cover SmartSwitch specific PMON APIs. The corresponding CLIs and remaining SmartSwitch life cycle management related functions are covered in the "DPU-test-plan.md"
+
+## Definitions and Abbreviations
+
+| **Term**   | **Meaning**                              |
+| ---------- | ---------------------------------------- |
+| DPU       | Data Processing Unit       |
+| NPU       | Network Processing Unit       |
+| SWITCH    | Refers to NPU and the anything other than DPUs    |
+| SS        | SmartSwitch       |
+
+
+## Objectives of Test Cases
+
+|    | **Test Case**   | **Intention**                              |
+| ---------- | ---------- | ---------------------------------------- |
+| 1.1 | Check SmartSwitch specific ChassisClass APIs      | To verify the newly implemented SmartSwitch specific ChassisClass APIs |
+| 1.2 | Check modified ChassisClass APIs for SmartSwitch       |  To verify the existing ChassisClass APIs that undergo minor changes with the addition of SmartSwitch|
+| 1.3 | Check DpuModule APIs for SmartSwitch       |  To Verify the newly implemented  DpuModule APIs for SmartSwitch|
+| 1.4 | Check modified ModuleClass APIs for SmartSwitch       |  To verify the existing ModuleClass APIs that undergo minor changes with the addition of SmartSwitch|
+| 1.5 | Check SwitchModule APIs for SmartSwitch       |  To Verify the newly implemented  SwitchModule APIs for SmartSwitch|
+
+## Test Cases
+
+
+### 1.1 Check SmartSwitch specific ChassisClass APIs
+
+#### Steps
+ * Execute the following CLIs on SmartSwitch
+ * get_dpu_id(self, name):
+    * Provide DPU0-DPU7
+    * This API should return 1-8 for DPU0-DPU7
+ * is_smartswitch(self):
+    * This API should return True
+ * get_module_dpu_data_port(self, index):
+    * For index: 1 will return the dup0 port association which is "Ethernet224: Ethernet0" where the string left of ":" (Ethernet224) is the NPU port and the string right of ":" (Ethernet0) is the DPU port.
+ 
+
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch:
+    get_dpu_id(self, DPU3)
+    Output: 4
+
+    is_smartswitch(self):
+    Output: True
+
+    get_module_dpu_data_port(self, DPU0):
+    Output: "Ethernet224: Ethernet0"
+
+```
+#### Pass/Fail Criteria
+ *  The test result is a pass if the return value matches the expected value as shown in the "steps" and "Sample Output".
+
+
+### 1.2 Check modified ChassisClass APIs for SmartSwitch
+
+#### Steps
+ * is_modular_chassis(self):
+    * Should return False
+ * get_num_modules(self):
+    * Should return number of DPUs + 1 switch
+ * get_module(self, index):
+    * Make sure for each index this API returns an object and has some content and not None
+ * get_all_modules(self):
+    * This should return a list of items
+ * get_module_index(self, module_name):
+    * Given the module name say “DPU0” should return the index of it “1”
+ 
+
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch:
+    is_modular_chassis(self):
+    Output: False
+
+    get_num_modules(self):
+    Output: number of DPUs + 1
+
+    get_module(self, DPU0):
+    Output: DPU0 object
+
+    get_all_modules(self):
+    Output: list of objects (one per DPU + 1 switch object)
+
+    get_module_index(self, DPU0):
+    Output: could be any value from 0 to modules count -1
+```
+#### Pass/Fail Criteria
+ * The test result is a pass if the return value matches the expected value as shown in the "steps" and "Sample Output"
+
+### 1.3 Check DpuModule APIs for SmartSwitch
+
+#### Steps
+ * get_dpu_id(self):
+    * Should return ID of the DpuModule Ex: 1 on DPU0
+ * get_reboot_cause(self):
+    * Reboot the module and then execute the "show reboot-cause ..." CLIs
+    * Verify the output string shows the correct Time and Cause
+    * Limit the testing to software reboot
+ * get_state_info(self):
+    * This should return an object
+    * Stop one of the DPU containers on this DPU
+    * Execute the CLI and check the dpu-controlplane value should be down
+ * get_health_info(self):
+    * This should return an object
+    * Stop one of the DPU containers on this DPU
+    * Execute the CLI and check if the health shows the stopped container
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch:
+    get_dpu_id(self):
+    Output: When on module DPUx should return x+1
+
+    get_reboot_cause(self):
+    Output: {"Device": "DPU0", "Name": 2024_05_31_00_33_30, "Cause":  "reboot", "Time": "Fri 31 May 2024 12:29:34 AM UTC", "User": "NA", "Comment": "NA"}
+
+    get_state_info(self):
+    Output: dpu state info object
+
+    get_health_info(self):
+    Output: dpu health info object
+
+```
+#### Pass/Fail Criteria
+ * Verify that all the APIs mentioned return the expected output
+
+### 1.4 Check modified ModuleClass APIs
+
+#### Steps
+ * get_base_mac(self):
+    * Should return the base mac address of this DPU
+    * Read all DPUs mac and verify if they are unique and not None
+ * get_system_eeprom_info(self):
+    * Verify the returned dictionary key:value
+ * get_name(self):
+    * Verify if this API returns “DPU0” to “DPU7” on each of them
+ * get_description(self):
+    * Should return a string
+ * get_type(self):
+    * Should return “DPU” which is “MODULE_TYPE_DPU”
+ * get_oper_status(self):
+    * Should return the operational status of the DPU
+    * Stop one ore more containers
+    * Execute the CLI and see if it is down
+ * reboot(self, reboot_type):
+    * Issue this CLI with input “MODULE_REBOOT_DEFAULT”
+    * verify if the module reboots
+ * get_midplane_ip(self):
+    * should return the midplane IP
+
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch:
+    get_base_mac(self):
+    Output: BA:CE:AD:D0:D0:01
+
+    get_system_eeprom_info(self):
+    Output: eeprom info object
+
+    get_name(self):
+    Output: DPU2
+
+    get_description(self):
+    Output "Pensando DSC"
+
+    get_type(self):
+    Output: DPU
+
+    get_oper_status(self):
+    Output: Online
+
+    reboot(self, reboot_type):
+    Result: the DPU should reboot
+
+    get_midplane_ip(self):
+    Output: 169.254.200.1
+
+```
+#### Pass/Fail Criteria
+ *  The test result is a pass if the return value matches the expected value as shown in the "steps" and "Sample Output".
+
+### 1.5 Check SwitchModule APIs for SmartSwitch
+* This includes the appropriate new and modified ChassisClass and ModuleClass APIs 
+
+#### Steps
+ * get_dpu_id(self, name):
+    * Provide “SWITCH”
+    * Should return 0
+ * is_smartswitch(self):
+    * This API should return True
+ * get_module_dpu_port(self, index):
+    * For index 0 should return None
+ * get_base_mac(self):
+    * Should return the base mac address of the switch
+ * get_system_eeprom_info(self):
+    * Verify the returned dictionary key:value
+ * get_name(self):
+    * Verify if this API returns “SWITCH”
+ * get_description(self):
+    * Should return a string
+ * get_type(self):
+    * Should return “SWITCH” which is “MODULE_TYPE_SWITCH”
+ * get_oper_status(self):
+    * Should return the operational status of the DPU
+    * Stop one ore more containers
+    * Execute the CLI and see if it is down
+ * reboot(self, reboot_type):
+    * Issue this CLI with input “MODULE_REBOOT_DEFAULT”
+    * verify if the chassis is rebooted
+ * get_midplane_ip(self):
+    * should return the midplane IP of the switch
+
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch:
+    get_dpu_id(self, SWITCH)
+    Output: 0
+
+    is_smartswitch(self):
+    Output: True
+
+    get_module_dpu_data_port(self, DPU0):
+    Output: None
+
+    get_base_mac(self):
+    Output: AA:CE:DD:D0:D0:78
+
+    get_system_eeprom_info(self):
+    Output: eeprom info object
+
+    get_name(self):
+    Output: SWITCH
+
+    get_description(self):
+    Output "Cisco 28x400G QSFPDD DPU-Enabled 2RU Smart Switch,Open SW"
+
+    get_type(self):
+    Output: SWITCH
+
+    get_oper_status(self):
+    Output: Online
+
+    reboot(self, reboot_type):
+    Result: the Chassis should reboot
+
+    get_midplane_ip(self):
+    Output: 169.254.200.254
+
+```
+#### Pass/Fail Criteria
+ *  The test result is a pass if the return value matches the expected value as shown in the "steps" and "Sample Output".
+ 
+ 
+### 1.6 Check the show reboot-cause CLI on the DPU
+
+#### Steps
+ * reboot the DPU
+ * issue the CLI “show reboot-cause” on the DPU
+ * verify the returned content’s time and cause
+ 
+#### Verify in
+ * DPU
+   
+#### Sample Output
+```
+On DPU: “show reboot-cause”
+Unknown
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error
+
+### 1.7 Check the show reboot-cause history CLI on the DPU
+
+#### Steps
+ * reboot the DPU a few times
+ * issue the CLI “show reboot-cause history” on the DPU
+ * verify the returned contents show all the reboot events time and cause
+ 
+#### Verify in
+ * DPU
+   
+#### Sample Output
+```
+On DPU: “show reboot-cause history”
+TBD: show the DPU output
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error as shown
+ 
+### 1.8 Check the show reboot-cause CLI on the SWITCH
+
+#### Steps
+ * reboot the SWITCH
+ * issue the CLI “show reboot-cause” on the SWITCH
+ * verify the returned content’s time and cause
+ * issue the cli extension for smartswitch which is “show reboot-cause all”
+ * verify the returned output has the DPU modules's reboot-cause as well
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show reboot-cause”
+Output: User issued 'reboot' command [User: cisco, Time: Fri 31 May 2024 12:29:34 AM UTC]
+
+On Switch: “show reboot-cause all”
+
+Device    Name                 Cause    Time                             User
+--------  -------------------  -------  -------------------------------  ------
+SWITCH    2024_05_31_00_33_30  reboot   Fri 31 May 2024 12:29:34 AM UTC  cisco
+
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error
+
+### 1.7 Check the show reboot-cause history CLI on the SWITCH
+
+#### Steps
+ * reboot the SWITCH a few times
+ * issue the CLI “show reboot-cause history” on the SWITCH
+ * verify the returned contents show all the reboot events time and cause
+ * issue the cli extension for smartswitch which is “show reboot-cause history all”
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show reboot-cause history”
+
+Name                 Cause       Time                             User    Comment
+-------------------  ----------  -------------------------------  ------  ---------
+2024_05_31_00_33_30  reboot      Fri 31 May 2024 12:29:34 AM UTC  cisco   N/A
+2024_05_30_05_09_36  reboot      Thu May 30 05:04:00 UTC 2024     cisco   N/A
+2024_05_24_19_50_39  reboot      Fri 24 May 2024 07:45:40 PM UTC  cisco   N/A
+2024_05_24_04_13_41  Power Loss  N/A                              N/A     Unknown
+2024_05_22_21_51_18  Power Loss  N/A                              N/A     Unknown
+2024_05_22_19_08_52  reboot      Wed 22 May 2024 07:03:16 PM UTC  cisco   N/A
+
+On Switch: “show reboot-cause history SWITCH”
+
+Device    Name                 Cause       Time                             User    Comment
+--------  -------------------  ----------  -------------------------------  ------  ---------
+SWITCH    2024_05_31_00_33_30  reboot      Fri 31 May 2024 12:29:34 AM UTC  cisco   N/A
+SWITCH    2024_05_30_05_09_36  reboot      Thu May 30 05:04:00 UTC 2024     cisco   N/A
+SWITCH    2024_05_24_21_13_52  reboot      Fri 24 May 2024 09:08:56 PM UTC  cisco   N/A
+SWITCH    2024_05_24_20_59_48  reboot      Fri 24 May 2024 08:54:50 PM UTC  cisco   N/A
+SWITCH    2024_05_24_19_50_39  reboot      Fri 24 May 2024 07:45:40 PM UTC  cisco   N/A
+SWITCH    2024_05_24_04_13_41  Power Loss  N/A                              N/A     Unknown
+
+On Switch: “show reboot-cause history all"
+Device    Name                 Cause       Time                             User    Comment
+--------  -------------------  ----------  -------------------------------  ------  ---------
+SWITCH    2024_05_31_00_33_30  reboot      Fri 31 May 2024 12:29:34 AM UTC  cisco   N/A
+SWITCH    2024_05_30_05_09_36  reboot      Thu May 30 05:04:00 UTC 2024     cisco   N/A
+SWITCH    2024_05_24_19_50_39  reboot      Fri 24 May 2024 07:45:40 PM UTC  cisco   N/A
+SWITCH    2024_05_24_04_13_41  Power Loss  N/A                              N/A     Unknown
+
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error as shown
+
+### 1.10 Check the show system-health summary CLI on the SWITCH
+
+#### Steps
+ * Issue this CLI “show system-health summary" on the switch
+ * Verify the health is reflected properly
+ * Test all, switch, DPU0 options by issuing “show system-health summary \<options\>”
+ * Verify the health is reflected properly for the given module
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show system-health summary"
+
+On Switch: “show system-health summary DPU0"
+
+On Switch: “show system-health summary SWITCH"
+
+On Switch: “show system-health summary all"
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error
+
+### 1.11 Check the show system-health monitor-list CLI on the SWITCH
+
+#### Steps
+ * Issue this CLI “show system-health monitor-list" on the switch
+ * Verify the health is reflected properly
+ * Test all, switch, DPU0 options by issuing “show system-health monitor-list \<options\>”
+ * Verify the health is reflected properly for the given module
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show system-health monitor-list"
+
+On Switch: “show system-health monitor-list DPU0"
+
+On Switch: “show system-health monitor-list SWITCH"
+
+On Switch: “show system-health monitor-list all"
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error
+
+### 1.12 Check the show system-health detail CLI on the SWITCH
+
+#### Steps
+ * Issue this CLI “show system-health detail" on the switch
+ * Verify the health is reflected properly
+ * Test all, switch, DPU0 options by issuing “show system-health detail \<options\>”
+ * Verify the health is reflected properly for the given module
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show system-health detail"
+
+On Switch: “show system-health detail DPU0"
+
+On Switch: “show system-health detail SWITCH"
+
+On Switch: “show system-health detail all"
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error
+
+### 1.13 Check the show system-health dpu DPUx CLI on the SWITCH
+
+#### Steps
+ * Issue this CLI “show system-health dpu DPU0" on the switch
+ * Verify the DPU0 state information
+ * Check the midplane state, control-plane state, data-plane state
+ * Alter the control-plane state, data-plane of the DPU by causing a container failure and pipeline failure respectively
+ * Verify the state changes get reflected
+ * TBD: midplane state
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show system-health dpu DPU0"
+
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error
\ No newline at end of file

From 1130b054f8e23cf7d1a4dd478c3aa79318184dd1 Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Mon, 3 Jun 2024 08:31:32 -0700
Subject: [PATCH 2/8] Initial draft

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 129 ++++++++++++++++++++-
 1 file changed, 124 insertions(+), 5 deletions(-)

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
index e8ddba6355..3e242c818d 100644
--- a/docs/testplan/SmartSwitch-PMON-testplan.md
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -1,7 +1,7 @@
 # SmartSwitch PMON Test Plan
 
 - [Introduction](#introduction)
-- [Scope](#scope)
+- [Scope](#scope)C
 - [Definitions and Abbreviations](#definitions-and-abbreviations)
 - [Test Cases](#test-cases)
     - [1.1 Check SmartSwitch specific ChassisClass APIs](#11-check-smartswitch-chassis-apis)
@@ -16,7 +16,11 @@
     - [1.10 Check the show system-health summary CLI on the SWITCH](#110-check-switch-system-health-summary-cli)
     - [1.11 Check the show system-health monitor-list CLI on the SWITCH](#111-check-switch-system-health-monitorlist-cli)
     - [1.12 Check the show system-health detail CLI on the SWITCH](#112-check-switch-system-health-detail-cli)
-    - [1.13 Check the show system-health dpu DPUx CLI on the SWITCH](#112-check-dpu-state-cli)
+    - [1.13 Check the show system-health dpu DPUx CLI on the SWITCH](#113-check-dpu-state-cli)
+    - [1.14 Check the cold startup of the DPUs and SWITCH](#114-check-startup-config)
+    - [1.15 Check the startup config CLI](#115-check-startup-config-cli)
+    - [1.16 Check the shutdown config CLI](#116-check-shutdown-config-cli)
+    - [1.17 Check the reboot config CLI](#117-check-reboot-config-cli)
 
 ## Introduction
 
@@ -42,9 +46,26 @@ The primary goal is to cover SmartSwitch specific PMON APIs. The corresponding C
 | ---------- | ---------- | ---------------------------------------- |
 | 1.1 | Check SmartSwitch specific ChassisClass APIs      | To verify the newly implemented SmartSwitch specific ChassisClass APIs |
 | 1.2 | Check modified ChassisClass APIs for SmartSwitch       |  To verify the existing ChassisClass APIs that undergo minor changes with the addition of SmartSwitch|
-| 1.3 | Check DpuModule APIs for SmartSwitch       |  To Verify the newly implemented  DpuModule APIs for SmartSwitch|
+| 1.3 | Check DpuModule APIs for SmartSwitch       |  To verify the newly implemented  DpuModule APIs for SmartSwitch|
 | 1.4 | Check modified ModuleClass APIs for SmartSwitch       |  To verify the existing ModuleClass APIs that undergo minor changes with the addition of SmartSwitch|
-| 1.5 | Check SwitchModule APIs for SmartSwitch       |  To Verify the newly implemented  SwitchModule APIs for SmartSwitch|
+| 1.5 | Check SwitchModule APIs for SmartSwitch       |  To verify the newly implemented  SwitchModule APIs for SmartSwitch|
+
+| 1.6 | Check the show reboot-cause CLI on the DPU       |  To verify the reboot-cause CLI on the DPU is unaffected |
+| 1.7 | Check the show reboot-cause history CLI on the DPU       |  To verify the reboot-cause history CLI on the DPU is unaffected|
+| 1.8 | Check the show reboot-cause CLI on the SWITCH       |  To verify the reboot-cause CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended|
+| 1.9 | Check the show reboot-cause history CLI on the SWITCH       |  To verify the reboot-cause history CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended|
+| 1.10 | Check the show system-health summary CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health summary" CLI work as expected |
+
+
+| 1.11 | Check the show system-health monitor-list CLI on the SWITCH        |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health monitor-list" CLI work as expected|
+| 1.12 | Check the show system-health detail CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health detail" CLI work as expected|
+| 1.13 | Check the show system-health dpu DPUx CLI on the SWITCH       |  To verify the newly implemented  show system-health dpu DPUx CLI for SmartSwitch reflects the midplane, control-plane, data-plane states of the DPU|
+| 1.14 | Check the cold startup of the DPUs and SWITCH       |  To verify the "chassisd", "chassis instance o database" are created and the admin state of the DPUs as defined in the config_db.json are applied properly |
+| 1.15 |  Check the startup config CLI       |  To verify the "config chassis modules startup DPUx" CLI does startup the DPU|
+
+
+| 1.16 | Check the shutdown config CLI        |   To verify the "config chassis modules shutdown DPUx" CLI does shutdown the DPU|
+| 1.17 | Check the reboot config CLI       |  To verify the "config chassis modules reboot SWITCH " CLI does reboot the SWITCH|
 
 ## Test Cases
 
@@ -418,6 +439,7 @@ SWITCH    2024_05_24_04_13_41  Power Loss  N/A                              N/A
 #### Sample Output
 ```
 On Switch: “show system-health summary"
+Output: TBD
 
 On Switch: “show system-health summary DPU0"
 
@@ -442,6 +464,7 @@ On Switch: “show system-health summary all"
 #### Sample Output
 ```
 On Switch: “show system-health monitor-list"
+Output: TBD
 
 On Switch: “show system-health monitor-list DPU0"
 
@@ -466,6 +489,7 @@ On Switch: “show system-health monitor-list all"
 #### Sample Output
 ```
 On Switch: “show system-health detail"
+Output: TBD
 
 On Switch: “show system-health detail DPU0"
 
@@ -492,7 +516,102 @@ On Switch: “show system-health detail all"
 #### Sample Output
 ```
 On Switch: “show system-health dpu DPU0"
+Output: TBD
+
+```
+#### Pass/Fail Criteria
+ *  A proper output should be delayed without any error
+
+### 1.14 Check the cold startup of the DPUs and SWITCH
+
+#### Steps
+ * Set the config_db.json such that some DPUs are powered down
+ * Cold start the system with the config
+ * Verify if the expected DPUs  are ON and the remaining are OFF and the  admin_status is set properly
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+Once the all the containers are up, (give enough time for the DPUs to boot up as well) and the system is stable
+On Switch: “show platform inventory"
+Output: TBD
+
+On Switch: "show chassis modules status"
+Output: TBD
+
+```
+#### Pass/Fail Criteria
+ * Verify if the expected DPUs are ON and the remaining are OFF and the  admin_status is set properly
+
+### 1.15 Check the startup config CLI
+
+#### Steps
+ * Boot the system
+ * Change config such that DPU3 which is OFF will be shutdown with the CLI “config chassis modules startup DPU3”
+ * Wait for the DPU to boot fully and the midplane IP is established
+ * Verify if the expected DPU "DPU3"  is ON and the  admin_status is set properly
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show platform inventory"
+Output: TBD
+
+On Switch: "show chassis modules status"
+Output: TBD
+
+```
+#### Pass/Fail Criteria
+ * Verify if the expected DPU "DPU3"  is ON and the  admin_status is set properly
+
+### 1.16 Check the shutdown config CLI
+
+#### Steps
+ * Boot the system
+ * Change config such that DPU1 which is ON will be shutdown with the CLI “config chassis modules shutdown DPU1”
+ * Wait for the DPU to shutdown fully and the midplane IP is detached
+ * Verify if the expected DPU "DPU1"  is OFF and the  admin_status is set properly
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+On Switch: “show platform inventory"
+Output: TBD
+
+On Switch: "show chassis modules status"
+Output: TBD
+
+```
+#### Pass/Fail Criteria
+ * Verify if the expected DPU "DPU1" is OFF and the  admin_status is set properly
+
+### 1.17 Check the reboot config CLI
+* TBD
+
+#### Steps
+ * Boot the system
+ * TBD: Change config such that "SWITCH" module is rebooted with the CLI “config chassis modules reboot SWITCH”
+ * Wait for the system to reboot fully
+ * Verify if the SWITCH and the DPUs that were ON rebooted properly
+ 
+#### Verify in
+ * Switch
+   
+#### Sample Output
+```
+Once the all the containers are up, (give enough time for the DPUs to boot up as well) and the system is stable
+On Switch: “show platform inventory"
+Output: TBD
+
+On Switch: "show chassis modules status"
+Output: TBD
 
 ```
 #### Pass/Fail Criteria
- *  A proper output should be delayed without any error
\ No newline at end of file
+ * Verify if the expected DPUs are ON and the remaining are OFF and the admin_status is set properly
\ No newline at end of file

From b1c1c5131f978da72afc2d508e9a96b461e0d445 Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Mon, 3 Jun 2024 09:15:48 -0700
Subject: [PATCH 3/8] Did some formatting

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
index 3e242c818d..2ff0dee45e 100644
--- a/docs/testplan/SmartSwitch-PMON-testplan.md
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -49,21 +49,16 @@ The primary goal is to cover SmartSwitch specific PMON APIs. The corresponding C
 | 1.3 | Check DpuModule APIs for SmartSwitch       |  To verify the newly implemented  DpuModule APIs for SmartSwitch|
 | 1.4 | Check modified ModuleClass APIs for SmartSwitch       |  To verify the existing ModuleClass APIs that undergo minor changes with the addition of SmartSwitch|
 | 1.5 | Check SwitchModule APIs for SmartSwitch       |  To verify the newly implemented  SwitchModule APIs for SmartSwitch|
-
 | 1.6 | Check the show reboot-cause CLI on the DPU       |  To verify the reboot-cause CLI on the DPU is unaffected |
 | 1.7 | Check the show reboot-cause history CLI on the DPU       |  To verify the reboot-cause history CLI on the DPU is unaffected|
 | 1.8 | Check the show reboot-cause CLI on the SWITCH       |  To verify the reboot-cause CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended|
 | 1.9 | Check the show reboot-cause history CLI on the SWITCH       |  To verify the reboot-cause history CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended|
 | 1.10 | Check the show system-health summary CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health summary" CLI work as expected |
-
-
 | 1.11 | Check the show system-health monitor-list CLI on the SWITCH        |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health monitor-list" CLI work as expected|
 | 1.12 | Check the show system-health detail CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health detail" CLI work as expected|
 | 1.13 | Check the show system-health dpu DPUx CLI on the SWITCH       |  To verify the newly implemented  show system-health dpu DPUx CLI for SmartSwitch reflects the midplane, control-plane, data-plane states of the DPU|
 | 1.14 | Check the cold startup of the DPUs and SWITCH       |  To verify the "chassisd", "chassis instance o database" are created and the admin state of the DPUs as defined in the config_db.json are applied properly |
 | 1.15 |  Check the startup config CLI       |  To verify the "config chassis modules startup DPUx" CLI does startup the DPU|
-
-
 | 1.16 | Check the shutdown config CLI        |   To verify the "config chassis modules shutdown DPUx" CLI does shutdown the DPU|
 | 1.17 | Check the reboot config CLI       |  To verify the "config chassis modules reboot SWITCH " CLI does reboot the SWITCH|
 

From f9ee11fddf44938630ccc98628dae3ef749b47e3 Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Tue, 4 Jun 2024 20:13:58 -0700
Subject: [PATCH 4/8] Initial draft for review

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 379 +++++++++++++++++++--
 1 file changed, 353 insertions(+), 26 deletions(-)

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
index 2ff0dee45e..57f97b56d2 100644
--- a/docs/testplan/SmartSwitch-PMON-testplan.md
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -341,7 +341,22 @@ Unknown
 #### Sample Output
 ```
 On DPU: “show reboot-cause history”
-TBD: show the DPU output
+
+Output:
+
+Name                 Cause    Time    User    Comment
+-------------------  -------  ------  ------  ---------
+2024_06_04_23_27_28  Unknown  N/A     N/A     N/A
+2024_05_29_21_28_22  Unknown  N/A     N/A     N/A
+2024_05_23_17_15_19  Unknown  N/A     N/A     N/A
+2024_05_23_17_15_15  Unknown  N/A     N/A     N/A
+2024_05_23_17_15_14  Unknown  N/A     N/A     N/A
+2024_05_23_17_15_00  Unknown  N/A     N/A     N/A
+2024_05_21_19_43_58  Unknown  N/A     N/A     N/A
+2024_05_21_19_42_07  Unknown  N/A     N/A     N/A
+2024_05_21_19_42_06  Unknown  N/A     N/A     N/A
+2024_05_21_19_42_05  Unknown  N/A     N/A     N/A
+
 ```
 #### Pass/Fail Criteria
  *  A proper output should be delayed without any error as shown
@@ -365,9 +380,10 @@ Output: User issued 'reboot' command [User: cisco, Time: Fri 31 May 2024 12:29:3
 
 On Switch: “show reboot-cause all”
 
-Device    Name                 Cause    Time                             User
---------  -------------------  -------  -------------------------------  ------
-SWITCH    2024_05_31_00_33_30  reboot   Fri 31 May 2024 12:29:34 AM UTC  cisco
+Device    Name                 Cause       Time    User
+--------  -------------------  ----------  ------  ------
+SWITCH    2024_06_04_23_27_25  Power Loss  N/A     N/A
+DPU0      2024_06_04_23_27_28  Unknown     N/A     N/A
 
 ```
 #### Pass/Fail Criteria
@@ -391,8 +407,6 @@ On Switch: “show reboot-cause history”
 Name                 Cause       Time                             User    Comment
 -------------------  ----------  -------------------------------  ------  ---------
 2024_05_31_00_33_30  reboot      Fri 31 May 2024 12:29:34 AM UTC  cisco   N/A
-2024_05_30_05_09_36  reboot      Thu May 30 05:04:00 UTC 2024     cisco   N/A
-2024_05_24_19_50_39  reboot      Fri 24 May 2024 07:45:40 PM UTC  cisco   N/A
 2024_05_24_04_13_41  Power Loss  N/A                              N/A     Unknown
 2024_05_22_21_51_18  Power Loss  N/A                              N/A     Unknown
 2024_05_22_19_08_52  reboot      Wed 22 May 2024 07:03:16 PM UTC  cisco   N/A
@@ -403,18 +417,22 @@ Device    Name                 Cause       Time                             User
 --------  -------------------  ----------  -------------------------------  ------  ---------
 SWITCH    2024_05_31_00_33_30  reboot      Fri 31 May 2024 12:29:34 AM UTC  cisco   N/A
 SWITCH    2024_05_30_05_09_36  reboot      Thu May 30 05:04:00 UTC 2024     cisco   N/A
-SWITCH    2024_05_24_21_13_52  reboot      Fri 24 May 2024 09:08:56 PM UTC  cisco   N/A
-SWITCH    2024_05_24_20_59_48  reboot      Fri 24 May 2024 08:54:50 PM UTC  cisco   N/A
 SWITCH    2024_05_24_19_50_39  reboot      Fri 24 May 2024 07:45:40 PM UTC  cisco   N/A
 SWITCH    2024_05_24_04_13_41  Power Loss  N/A                              N/A     Unknown
 
 On Switch: “show reboot-cause history all"
-Device    Name                 Cause       Time                             User    Comment
---------  -------------------  ----------  -------------------------------  ------  ---------
-SWITCH    2024_05_31_00_33_30  reboot      Fri 31 May 2024 12:29:34 AM UTC  cisco   N/A
-SWITCH    2024_05_30_05_09_36  reboot      Thu May 30 05:04:00 UTC 2024     cisco   N/A
-SWITCH    2024_05_24_19_50_39  reboot      Fri 24 May 2024 07:45:40 PM UTC  cisco   N/A
-SWITCH    2024_05_24_04_13_41  Power Loss  N/A                              N/A     Unknown
+Device    Name                      Cause       Time    User    Comment
+--------  ------------------------  ----------  ------  ------  --------------------------------------------------------------------------
+SWITCH    2024_06_04_23_27_25       Power Loss  N/A     N/A     Unknown (First boot of SONiC version detached.12061-dirty-20240601.152750)
+DPU0      2024_06_04_23_27_28       Unknown     N/A     N/A     N/A
+DPU0      2024_05_29_21_28_22|DPU0  Unknown     N/A     N/A     N/A
+
+show reboot-cause history DPU0
+Device    Name                      Cause    Time    User    Comment
+--------  ------------------------  -------  ------  ------  ---------
+DPU0      2024_06_04_23_27_28       Unknown  N/A     N/A     N/A
+DPU0      2024_05_29_21_28_22       Unknown  N/A     N/A     N/A
+DPU0      2024_05_23_17_15_19       Unknown  N/A     N/A     N/A
 
 ```
 #### Pass/Fail Criteria
@@ -434,13 +452,61 @@ SWITCH    2024_05_24_04_13_41  Power Loss  N/A                              N/A
 #### Sample Output
 ```
 On Switch: “show system-health summary"
-Output: TBD
+
+System status summary
+
+  System status LED  green
+  Services:
+    Status: Not OK
+    Not Running: container_checker, lldp:lldpmgrd
+  Hardware:
+    Status: OK
 
 On Switch: “show system-health summary DPU0"
 
+DPU0
+System status summary
+
+  System status LED  green
+  Services:
+    Status: Not OK
+    Not Running: container_checker, macsec, dhcp_relay, mux, snmp, lldp, mgmt-framework, gnmi, swss:vlanmgrd, swss:vxlanmgrd, teamd:teammgrd, teamd:teamsyncd
+  Hardware:
+    Status: OK
+
 On Switch: “show system-health summary SWITCH"
 
+SWITCH
+System status summary
+
+  System status LED  green
+  Services:
+    Status: Not OK
+    Not Running: container_checker, lldp:lldpmgrd
+  Hardware:
+    Status: OK
+
 On Switch: “show system-health summary all"
+
+SWITCH
+System status summary
+
+  System status LED  green
+  Services:
+    Status: Not OK
+    Not Running: container_checker, lldp:lldpmgrd
+  Hardware:
+    Status: OK
+
+DPU1
+System status summary
+
+  System status LED  green
+  Services:
+    Status: Not OK
+    Not Running: container_checker, mux, dhcp_relay, gnmi, lldp, mgmt-framework, macsec, snmp, swss:vlanmgrd, swss:vxlanmgrd, teamd:teammgrd, teamd:teamsyncd
+  Hardware:
+
 ```
 #### Pass/Fail Criteria
  *  A proper output should be delayed without any error
@@ -459,13 +525,161 @@ On Switch: “show system-health summary all"
 #### Sample Output
 ```
 On Switch: “show system-health monitor-list"
-Output: TBD
+
+System services and devices monitor list
+
+Name                   Status    Type
+---------------------  --------  ----------
+container_checker      Not OK    Program
+lldp:lldpmgrd          Not OK    Process
+sonic                  OK        System
+rsyslog                OK        Process
+root-overlay           OK        Filesystem
+var-log                OK        Filesystem
+routeCheck             OK        Program
+dualtorNeighborCheck   OK        Program
+bgp:fpmsyncd           OK        Process
+bgp:bgpcfgd            OK        Process
+PSU0.fan0              OK        Fan
+PSU1.fan0              OK        Fan
+fantray0.fan0          OK        Fan
+fantray1.fan0          OK        Fan
+fantray2.fan0          OK        Fan
+fantray3.fan0          OK        Fan
+PSU 1                  OK        PSU
+PSU 2                  OK        PSU
+root@sonic:/home/cisco# 
 
 On Switch: “show system-health monitor-list DPU0"
 
+DPU0
+
+System services and devices monitor list
+
+Name                      Status    Type
+------------------------  --------  ----------
+container_checker         Not OK    Program
+macsec                    Not OK    Service
+dhcp_relay                Not OK    Service
+mux                       Not OK    Service
+snmp                      Not OK    Service
+lldp                      Not OK    Service
+mgmt-framework            Not OK    Service
+gnmi                      Not OK    Service
+swss:vlanmgrd             Not OK    Process
+swss:vxlanmgrd            Not OK    Process
+teamd:teammgrd            Not OK    Process
+teamd:teamsyncd           Not OK    Process
+sonic                     OK        System
+rsyslog                   OK        Process
+root-overlay              OK        Filesystem
+var-log                   OK        Filesystem
+routeCheck                OK        Program
+dualtorNeighborCheck      OK        Program
+diskCheck                 OK        Program
+vnetRouteCheck            OK        Program
+memory_check              OK        Program
+swss:buffermgrd           OK        Process
+swss:vrfmgrd              OK        Process
+swss:nbrmgrd              OK        Process
+swss:coppmgrd             OK        Process
+teamd:tlm_teamd           OK        Process
+eventd:eventd             OK        Process
+dpu-pdsagent              OK        UserDefine
+dpu-pciemgrd              OK        UserDefine
+dpu-eth_Uplink1/1_status  OK        UserDefine
+dpu-pcie_link             OK        UserDefine
+
 On Switch: “show system-health monitor-list SWITCH"
+SWITCH
+
+System services and devices monitor list
+
+Name                   Status    Type
+---------------------  --------  ----------
+container_checker      Not OK    Program
+lldp:lldpmgrd          Not OK    Process
+sonic                  OK        System
+rsyslog                OK        Process
+root-overlay           OK        Filesystem
+var-log                OK        Filesystem
+routeCheck             OK        Program
+dualtorNeighborCheck   OK        Program
+bgp:fpmsyncd           OK        Process
+bgp:bgpcfgd            OK        Process
+PSU0.fan0              OK        Fan
+PSU1.fan0              OK        Fan
+fantray0.fan0          OK        Fan
+fantray1.fan0          OK        Fan
+fantray2.fan0          OK        Fan
+fantray3.fan0          OK        Fan
+PSU 1                  OK        PSU
+PSU 2                  OK        PSU
 
 On Switch: “show system-health monitor-list all"
+
+SWITCH
+
+System services and devices monitor list
+
+Name                   Status    Type
+---------------------  --------  ----------
+container_checker      Not OK    Program
+lldp:lldpmgrd          Not OK    Process
+sonic                  OK        System
+rsyslog                OK        Process
+root-overlay           OK        Filesystem
+var-log                OK        Filesystem
+routeCheck             OK        Program
+dualtorNeighborCheck   OK        Program
+bgp:fpmsyncd           OK        Process
+bgp:bgpcfgd            OK        Process
+PSU0.fan0              OK        Fan
+PSU1.fan0              OK        Fan
+fantray0.fan0          OK        Fan
+fantray1.fan0          OK        Fan
+fantray2.fan0          OK        Fan
+fantray3.fan0          OK        Fan
+PSU 1                  OK        PSU
+PSU 2                  OK        PSU
+
+DPU0
+
+System services and devices monitor list
+
+Name                      Status    Type
+------------------------  --------  ----------
+container_checker         Not OK    Program
+macsec                    Not OK    Service
+dhcp_relay                Not OK    Service
+mux                       Not OK    Service
+snmp                      Not OK    Service
+lldp                      Not OK    Service
+mgmt-framework            Not OK    Service
+gnmi                      Not OK    Service
+swss:vlanmgrd             Not OK    Process
+swss:vxlanmgrd            Not OK    Process
+teamd:teammgrd            Not OK    Process
+teamd:teamsyncd           Not OK    Process
+sonic                     OK        System
+rsyslog                   OK        Process
+root-overlay              OK        Filesystem
+var-log                   OK        Filesystem
+routeCheck                OK        Program
+dualtorNeighborCheck      OK        Program
+diskCheck                 OK        Program
+vnetRouteCheck            OK        Program
+memory_check              OK        Program
+swss:buffermgrd           OK        Process
+swss:vrfmgrd              OK        Process
+swss:nbrmgrd              OK        Process
+swss:coppmgrd             OK        Process
+teamd:tlm_teamd           OK        Process
+eventd:eventd             OK        Process
+dpu-pdsagent              OK        UserDefine
+dpu-pciemgrd              OK        UserDefine
+dpu-eth_Uplink1/1_status  OK        UserDefine
+dpu-pcie_link             OK        UserDefine
 ```
 #### Pass/Fail Criteria
  *  A proper output should be delayed without any error
@@ -484,13 +698,96 @@ On Switch: “show system-health monitor-list all"
 #### Sample Output
 ```
 On Switch: “show system-health detail"
-Output: TBD
+
+System status summary
+
+  System status LED  green
+  Services:
+    Status: Not OK
+    Not Running: container_checker, lldp:lldpmgrd
+  Hardware:
+    Status: OK
+
+System services and devices monitor list
+
+Name                   Status    Type
+---------------------  --------  ----------
+container_checker      Not OK    Program
+lldp:lldpmgrd          Not OK    Process
+sonic                  OK        System
+rsyslog                OK        Process
+root-overlay           OK        Filesystem
+var-log                OK        Filesystem
+routeCheck             OK        Program
+dualtorNeighborCheck   OK        Program
+diskCheck              OK        Program
+bgp:bgpd               OK        Process
+bgp:fpmsyncd           OK        Process
+bgp:bgpcfgd            OK        Process
+PSU0.fan0              OK        Fan
+PSU1.fan0              OK        Fan
+fantray0.fan0          OK        Fan
+fantray1.fan0          OK        Fan
+fantray2.fan0          OK        Fan
+fantray3.fan0          OK        Fan
+PSU 1                  OK        PSU
+PSU 2                  OK        PSU
+
+System services and devices ignore list
+
+Name    Status    Type
+------  --------  ------
 
 On Switch: “show system-health detail DPU0"
 
+DPU0
+System status summary
+
+  System status LED  green
+  Services:
+    Status: Not OK
+    Not Running: container_checker, macsec, dhcp_relay, mux, snmp, lldp, mgmt-framework, gnmi, swss:vlanmgrd, swss:vxlanmgrd, teamd:teammgrd, teamd:teamsyncd
+  Hardware:
+    Status: OK
+
+System services and devices monitor list
+
+Name                      Status    Type
+------------------------  --------  ----------
+container_checker         Not OK    Program
+macsec                    Not OK    Service
+dhcp_relay                Not OK    Service
+mux                       Not OK    Service
+snmp                      Not OK    Service
+lldp                      Not OK    Service
+mgmt-framework            Not OK    Service
+gnmi                      Not OK    Service
+swss:vlanmgrd             Not OK    Process
+teamd:teamsyncd           Not OK    Process
+sonic                     OK        System
+rsyslog                   OK        Process
+root-overlay              OK        Filesystem
+var-log                   OK        Filesystem
+routeCheck                OK        Program
+dualtorNeighborCheck      OK        Program
+container_memory_gnmi     OK        Program
+container_eventd          OK        Program
+database:redis            OK        Process
+bgp:zebra                 OK        Process
+bgp:staticd               OK        Process
+teamd:tlm_teamd           OK        Process
+eventd:eventd             OK        Process
+dpu-pdsagent              OK        UserDefine
+dpu-pciemgrd              OK        UserDefine
+dpu-eth_Uplink1/1_status  OK        UserDefine
+dpu-pcie_link             OK        UserDefine
+
 On Switch: “show system-health detail SWITCH"
+Output: Same as “show system-health detail"
 
 On Switch: “show system-health detail all"
+Output: Same as “show system-health detail SWITCH" plus the DPUs output
+
 ```
 #### Pass/Fail Criteria
  *  A proper output should be delayed without any error
@@ -511,7 +808,12 @@ On Switch: “show system-health detail all"
 #### Sample Output
 ```
 On Switch: “show system-health dpu DPU0"
-Output: TBD
+
+Name    ID    Oper-Status    State-Detail             State-Value    Time               Reason
+------  ----  -------------  -----------------------  -------------  -----------------  --------------------------------------------------------------------------------------------------------------------------
+DPU0    0     Online         dpu_midplane_link_state  UP             20240605 02:01:13  INTERNAL-MGMT : admin state - UP, oper_state - UP, status - OK, HOST-MGMT : admin state - UP, oper_state - UP, status - OK
+                             dpu_control_plane_state  UP             20240605 02:01:13  All containers are up and running, host-ethlink-status: Uplink1/1 is UP
+                             dpu_data_plane_state     UP             20240605 00:03:55  DPU container named polaris is running, pdsagent running : OK, pciemgrd running : OK
 
 ```
 #### Pass/Fail Criteria
@@ -531,10 +833,35 @@ Output: TBD
 ```
 Once the all the containers are up, (give enough time for the DPUs to boot up as well) and the system is stable
 On Switch: “show platform inventory"
-Output: TBD
+
+    Name                Product ID      Version              Serial Number   Description
+
+Chassis
+    CHASSIS             8102-28FH-DPU-O 0.10                 FLM274802F6     Cisco 28x400G QSFPDD DPU-Enabled 2RU Smart Switch,Open SW
+
+Route Processors
+    RP0                 8102-28FH-DPU-O 0.10                 FLM274802F6     Cisco 28x400G QSFPDD DPU-Enabled 2RU Smart Switch,Open SW
+
+Sled Cards
+    SLED0               8K-DPU400-2A    0.10                 FLM2750036R     Cisco 800 2xDPU Sled AMD Elba
+    SLED1               8K-DPU400-2A    0.10                 FLM2750037Z     Cisco 800 2xDPU Sled AMD Elba
+    SLED2               8K-DPU400-2A    0.10                 FLM2750036Q     Cisco 800 2xDPU Sled AMD Elba
+    SLED3               8K-DPU400-2A    0.10                 FLM2750037L     Cisco 800 2xDPU Sled AMD Elba
+
+Dpu Modules
+    DPU0                DSS-MTFUJI      6.1.0-11-2-arm64     225207731731968 Pensando DSC
+    DPU1                DSS-MTFUJI      6.1.0-11-2-arm64     225207731731984 Pensando DSC
+    DPU2 -- not present
+    DPU3                DSS-MTFUJI      6.1.0-11-2-arm64     225207731731952 Pensando DSC
+
 
 On Switch: "show chassis modules status"
-Output: TBD
+
+  Name    Description    Physical-Slot    Oper-Status    Admin-Status    Serial
+------  -------------  ---------------  -------------  --------------  --------
+  DPU0            N/A               -1         Online              up       N/A
+  DPU1            N/A               -1         Online              up       N/A
+  DPU2            N/A               -1        Offline            down       N/A
 
 ```
 #### Pass/Fail Criteria
@@ -554,10 +881,10 @@ Output: TBD
 #### Sample Output
 ```
 On Switch: “show platform inventory"
-Output: TBD
+Output: shown in 1.4
 
 On Switch: "show chassis modules status"
-Output: TBD
+Output: shown in 1.4
 
 ```
 #### Pass/Fail Criteria
@@ -577,10 +904,10 @@ Output: TBD
 #### Sample Output
 ```
 On Switch: “show platform inventory"
-Output: TBD
+Output: shown in 1.4
 
 On Switch: "show chassis modules status"
-Output: TBD
+Output: shown in 1.4
 
 ```
 #### Pass/Fail Criteria
@@ -602,10 +929,10 @@ Output: TBD
 ```
 Once the all the containers are up, (give enough time for the DPUs to boot up as well) and the system is stable
 On Switch: “show platform inventory"
-Output: TBD
+Output: shown in 1.4
 
 On Switch: "show chassis modules status"
-Output: TBD
+Output: shown in 1.4
 
 ```
 #### Pass/Fail Criteria

From ccd289e02fb2d883467b6b020641d4d326f25ced Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Tue, 9 Jul 2024 20:24:41 -0700
Subject: [PATCH 5/8] Addressed review comments

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 111 ++++-----------------
 1 file changed, 20 insertions(+), 91 deletions(-)

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
index 57f97b56d2..249599a8bd 100644
--- a/docs/testplan/SmartSwitch-PMON-testplan.md
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -48,7 +48,6 @@ The primary goal is to cover SmartSwitch specific PMON APIs. The corresponding C
 | 1.2 | Check modified ChassisClass APIs for SmartSwitch       |  To verify the existing ChassisClass APIs that undergo minor changes with the addition of SmartSwitch|
 | 1.3 | Check DpuModule APIs for SmartSwitch       |  To verify the newly implemented  DpuModule APIs for SmartSwitch|
 | 1.4 | Check modified ModuleClass APIs for SmartSwitch       |  To verify the existing ModuleClass APIs that undergo minor changes with the addition of SmartSwitch|
-| 1.5 | Check SwitchModule APIs for SmartSwitch       |  To verify the newly implemented  SwitchModule APIs for SmartSwitch|
 | 1.6 | Check the show reboot-cause CLI on the DPU       |  To verify the reboot-cause CLI on the DPU is unaffected |
 | 1.7 | Check the show reboot-cause history CLI on the DPU       |  To verify the reboot-cause history CLI on the DPU is unaffected|
 | 1.8 | Check the show reboot-cause CLI on the SWITCH       |  To verify the reboot-cause CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended|
@@ -68,14 +67,14 @@ The primary goal is to cover SmartSwitch specific PMON APIs. The corresponding C
 ### 1.1 Check SmartSwitch specific ChassisClass APIs
 
 #### Steps
- * Execute the following CLIs on SmartSwitch
+ * Execute the following APIs on SmartSwitch
  * get_dpu_id(self, name):
-    * Provide DPU0-DPU7
-    * This API should return 1-8 for DPU0-DPU7
+    * Provide name (Example: DPU0 - Get it from platform.json file)
+    * This API should return an integer from 1-8 (check it against platform.json)
  * is_smartswitch(self):
     * This API should return True
  * get_module_dpu_data_port(self, index):
-    * For index: 1 will return the dup0 port association which is "Ethernet224: Ethernet0" where the string left of ":" (Ethernet224) is the NPU port and the string right of ":" (Ethernet0) is the DPU port.
+    * For index: 1 will return the dpu0 port association which is "Ethernet224: Ethernet0" where the string left of ":" (Ethernet224) is the NPU port and the string right of ":" (Ethernet0) is the DPU port.
  
 
 #### Verify in
@@ -104,9 +103,10 @@ On Switch:
  * is_modular_chassis(self):
     * Should return False
  * get_num_modules(self):
-    * Should return number of DPUs + 1 switch
+    * Should return number of DPUs
  * get_module(self, index):
     * Make sure for each index this API returns an object and has some content and not None
+    * Check that the object's class is inherited from the ModuleBase class
  * get_all_modules(self):
     * This should return a list of items
  * get_module_index(self, module_name):
@@ -123,7 +123,7 @@ On Switch:
     Output: False
 
     get_num_modules(self):
-    Output: number of DPUs + 1
+    Output: number of DPUs
 
     get_module(self, DPU0):
     Output: DPU0 object
@@ -149,7 +149,8 @@ On Switch:
  * get_state_info(self):
     * This should return an object
     * Stop one of the DPU containers on this DPU
-    * Execute the CLI and check the dpu-controlplane value should be down
+    * Execute the CLI and check the dpu-control-plane value should be down
+    * Check the complete list of containers without which the control plane can be up.
  * get_health_info(self):
     * This should return an object
     * Stop one of the DPU containers on this DPU
@@ -195,9 +196,11 @@ On Switch:
     * Should return the operational status of the DPU
     * Stop one ore more containers
     * Execute the CLI and see if it is down
+    * Power down the dpu and check if the operational status is down.
  * reboot(self, reboot_type):
     * Issue this CLI with input “MODULE_REBOOT_DEFAULT”
     * verify if the module reboots
+    * The reboot type should be updated based on SmartSwitch reboot HLD sonic-net/SONiC#1699
  * get_midplane_ip(self):
     * should return the midplane IP
 
@@ -234,80 +237,6 @@ On Switch:
 ```
 #### Pass/Fail Criteria
  *  The test result is a pass if the return value matches the expected value as shown in the "steps" and "Sample Output".
-
-### 1.5 Check SwitchModule APIs for SmartSwitch
-* This includes the appropriate new and modified ChassisClass and ModuleClass APIs 
-
-#### Steps
- * get_dpu_id(self, name):
-    * Provide “SWITCH”
-    * Should return 0
- * is_smartswitch(self):
-    * This API should return True
- * get_module_dpu_port(self, index):
-    * For index 0 should return None
- * get_base_mac(self):
-    * Should return the base mac address of the switch
- * get_system_eeprom_info(self):
-    * Verify the returned dictionary key:value
- * get_name(self):
-    * Verify if this API returns “SWITCH”
- * get_description(self):
-    * Should return a string
- * get_type(self):
-    * Should return “SWITCH” which is “MODULE_TYPE_SWITCH”
- * get_oper_status(self):
-    * Should return the operational status of the DPU
-    * Stop one ore more containers
-    * Execute the CLI and see if it is down
- * reboot(self, reboot_type):
-    * Issue this CLI with input “MODULE_REBOOT_DEFAULT”
-    * verify if the chassis is rebooted
- * get_midplane_ip(self):
-    * should return the midplane IP of the switch
-
-#### Verify in
- * Switch
-   
-#### Sample Output
-```
-On Switch:
-    get_dpu_id(self, SWITCH)
-    Output: 0
-
-    is_smartswitch(self):
-    Output: True
-
-    get_module_dpu_data_port(self, DPU0):
-    Output: None
-
-    get_base_mac(self):
-    Output: AA:CE:DD:D0:D0:78
-
-    get_system_eeprom_info(self):
-    Output: eeprom info object
-
-    get_name(self):
-    Output: SWITCH
-
-    get_description(self):
-    Output "Cisco 28x400G QSFPDD DPU-Enabled 2RU Smart Switch,Open SW"
-
-    get_type(self):
-    Output: SWITCH
-
-    get_oper_status(self):
-    Output: Online
-
-    reboot(self, reboot_type):
-    Result: the Chassis should reboot
-
-    get_midplane_ip(self):
-    Output: 169.254.200.254
-
-```
-#### Pass/Fail Criteria
- *  The test result is a pass if the return value matches the expected value as shown in the "steps" and "Sample Output".
  
  
 ### 1.6 Check the show reboot-cause CLI on the DPU
@@ -455,7 +384,7 @@ On Switch: “show system-health summary"
 
 System status summary
 
-  System status LED  green
+  System status LED  red
   Services:
     Status: Not OK
     Not Running: container_checker, lldp:lldpmgrd
@@ -467,7 +396,7 @@ On Switch: “show system-health summary DPU0"
 DPU0
 System status summary
 
-  System status LED  green
+  System status LED  red
   Services:
     Status: Not OK
     Not Running: container_checker, macsec, dhcp_relay, mux, snmp, lldp, mgmt-framework, gnmi, swss:vlanmgrd, swss:vxlanmgrd, teamd:teammgrd, teamd:teamsyncd
@@ -479,7 +408,7 @@ On Switch: “show system-health summary SWITCH"
 SWITCH
 System status summary
 
-  System status LED  green
+  System status LED  red
   Services:
     Status: Not OK
     Not Running: container_checker, lldp:lldpmgrd
@@ -491,7 +420,7 @@ On Switch: “show system-health summary all"
 SWITCH
 System status summary
 
-  System status LED  green
+  System status LED  red
   Services:
     Status: Not OK
     Not Running: container_checker, lldp:lldpmgrd
@@ -501,7 +430,7 @@ System status summary
 DPU1
 System status summary
 
-  System status LED  green
+  System status LED red 
   Services:
     Status: Not OK
     Not Running: container_checker, mux, dhcp_relay, gnmi, lldp, mgmt-framework, macsec, snmp, swss:vlanmgrd, swss:vxlanmgrd, teamd:teammgrd, teamd:teamsyncd
@@ -701,7 +630,7 @@ On Switch: “show system-health detail"
 
 System status summary
 
-  System status LED  green
+  System status LED  red
   Services:
     Status: Not OK
     Not Running: container_checker, lldp:lldpmgrd
@@ -743,7 +672,7 @@ On Switch: “show system-health detail DPU0"
 DPU0
 System status summary
 
-  System status LED  green
+  System status LED  red
   Services:
     Status: Not OK
     Not Running: container_checker, macsec, dhcp_relay, mux, snmp, lldp, mgmt-framework, gnmi, swss:vlanmgrd, swss:vxlanmgrd, teamd:teammgrd, teamd:teamsyncd
@@ -859,8 +788,8 @@ On Switch: "show chassis modules status"
 
   Name    Description    Physical-Slot    Oper-Status    Admin-Status    Serial
 ------  -------------  ---------------  -------------  --------------  --------
-  DPU0            N/A               -1         Online              up       N/A
-  DPU1            N/A               -1         Online              up       N/A
+  DPU0   Pensando DSC               -1         Online              up       225207731731968
+  DPU1   Pensando DSC               -1         Online              up       225207731731984
   DPU2            N/A               -1        Offline            down       N/A
 
 ```

From 3b65e55d06f4e68cd34d251396009dfc1fad9054 Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Mon, 29 Jul 2024 13:16:11 -0700
Subject: [PATCH 6/8] Addressed review comments

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 59 +++++++++-------------
 1 file changed, 23 insertions(+), 36 deletions(-)

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
index 249599a8bd..b64ebc1208 100644
--- a/docs/testplan/SmartSwitch-PMON-testplan.md
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -1,7 +1,7 @@
 # SmartSwitch PMON Test Plan
 
 - [Introduction](#introduction)
-- [Scope](#scope)C
+- [Scope](#scope)
 - [Definitions and Abbreviations](#definitions-and-abbreviations)
 - [Test Cases](#test-cases)
     - [1.1 Check SmartSwitch specific ChassisClass APIs](#11-check-smartswitch-chassis-apis)
@@ -90,7 +90,9 @@ On Switch:
     Output: True
 
     get_module_dpu_data_port(self, DPU0):
-    Output: "Ethernet224: Ethernet0"
+    Output: {
+                "interface": {"Ethernet224": "Ethernet0"}
+            }
 
 ```
 #### Pass/Fail Criteria
@@ -151,6 +153,7 @@ On Switch:
     * Stop one of the DPU containers on this DPU
     * Execute the CLI and check the dpu-control-plane value should be down
     * Check the complete list of containers without which the control plane can be up.
+    * This test case can be extended to verify the DPU transition through all states.
  * get_health_info(self):
     * This should return an object
     * Stop one of the DPU containers on this DPU
@@ -187,7 +190,7 @@ On Switch:
  * get_system_eeprom_info(self):
     * Verify the returned dictionary key:value
  * get_name(self):
-    * Verify if this API returns “DPU0” to “DPU7” on each of them
+    * Verify if this API returns “DPUx" on each of them
  * get_description(self):
     * Should return a string
  * get_type(self):
@@ -240,7 +243,7 @@ On Switch:
  
  
 ### 1.6 Check the show reboot-cause CLI on the DPU
-
+This test case should be optional based on the platform capabilities listed on the platform.json file on the switch side
 #### Steps
  * reboot the DPU
  * issue the CLI “show reboot-cause” on the DPU
@@ -258,7 +261,7 @@ Unknown
  *  A proper output should be delayed without any error
 
 ### 1.7 Check the show reboot-cause history CLI on the DPU
-
+This test case should be optional based on the platform capabilities listed on the platform.json file on the switch side
 #### Steps
  * reboot the DPU a few times
  * issue the CLI “show reboot-cause history” on the DPU
@@ -273,19 +276,10 @@ On DPU: “show reboot-cause history”
 
 Output:
 
-Name                 Cause    Time    User    Comment
--------------------  -------  ------  ------  ---------
-2024_06_04_23_27_28  Unknown  N/A     N/A     N/A
-2024_05_29_21_28_22  Unknown  N/A     N/A     N/A
-2024_05_23_17_15_19  Unknown  N/A     N/A     N/A
-2024_05_23_17_15_15  Unknown  N/A     N/A     N/A
-2024_05_23_17_15_14  Unknown  N/A     N/A     N/A
-2024_05_23_17_15_00  Unknown  N/A     N/A     N/A
-2024_05_21_19_43_58  Unknown  N/A     N/A     N/A
-2024_05_21_19_42_07  Unknown  N/A     N/A     N/A
-2024_05_21_19_42_06  Unknown  N/A     N/A     N/A
-2024_05_21_19_42_05  Unknown  N/A     N/A     N/A
-
+Name                 Cause       Time                                User    Comment
+-------------------  -------     ------                              ------  ---------
+2024_06_26_21_08_27  Unknown     Wed Jun 26 09:04:43 PM UTC 2024     cisco    N/A
+2024_06_25_21_08_27  Unknown     Wed Jun 25 09:04:43 PM UTC 2024     cisco    N/A
 ```
 #### Pass/Fail Criteria
  *  A proper output should be delayed without any error as shown
@@ -309,10 +303,10 @@ Output: User issued 'reboot' command [User: cisco, Time: Fri 31 May 2024 12:29:3
 
 On Switch: “show reboot-cause all”
 
-Device    Name                 Cause       Time    User
---------  -------------------  ----------  ------  ------
-SWITCH    2024_06_04_23_27_25  Power Loss  N/A     N/A
-DPU0      2024_06_04_23_27_28  Unknown     N/A     N/A
+Device    Name                 Cause       Time                               User
+--------  -------------------  ----------  ------                             ------
+SWITCH    2024_06_26_21_08_27  reboot      Wed Jun 26 09:04:43 PM UTC 2024    cisco
+DPU0      2024_06_26_21_08_27  Unknown     Wed Jun 26 09:04:43 PM UTC 2024    cisco
 
 ```
 #### Pass/Fail Criteria
@@ -754,6 +748,8 @@ DPU0    0     Online         dpu_midplane_link_state  UP             20240605 02
  * Set the config_db.json such that some DPUs are powered down
  * Cold start the system with the config
  * Verify if the expected DPUs  are ON and the remaining are OFF and the  admin_status is set properly
+ * Tests don't need to check for version info.
+ * The test should check the fields only for the DPUs that are powered.
  
 #### Verify in
  * Switch
@@ -768,15 +764,6 @@ On Switch: “show platform inventory"
 Chassis
     CHASSIS             8102-28FH-DPU-O 0.10                 FLM274802F6     Cisco 28x400G QSFPDD DPU-Enabled 2RU Smart Switch,Open SW
 
-Route Processors
-    RP0                 8102-28FH-DPU-O 0.10                 FLM274802F6     Cisco 28x400G QSFPDD DPU-Enabled 2RU Smart Switch,Open SW
-
-Sled Cards
-    SLED0               8K-DPU400-2A    0.10                 FLM2750036R     Cisco 800 2xDPU Sled AMD Elba
-    SLED1               8K-DPU400-2A    0.10                 FLM2750037Z     Cisco 800 2xDPU Sled AMD Elba
-    SLED2               8K-DPU400-2A    0.10                 FLM2750036Q     Cisco 800 2xDPU Sled AMD Elba
-    SLED3               8K-DPU400-2A    0.10                 FLM2750037L     Cisco 800 2xDPU Sled AMD Elba
-
 Dpu Modules
     DPU0                DSS-MTFUJI      6.1.0-11-2-arm64     225207731731968 Pensando DSC
     DPU1                DSS-MTFUJI      6.1.0-11-2-arm64     225207731731984 Pensando DSC
@@ -786,11 +773,11 @@ Dpu Modules
 
 On Switch: "show chassis modules status"
 
-  Name    Description    Physical-Slot    Oper-Status    Admin-Status    Serial
-------  -------------  ---------------  -------------  --------------  --------
-  DPU0   Pensando DSC               -1         Online              up       225207731731968
-  DPU1   Pensando DSC               -1         Online              up       225207731731984
-  DPU2            N/A               -1        Offline            down       N/A
+  Name    Description    Physical-Slot    Oper-Status    Admin-Status            Serial
+------  -------------  ---------------  -------------  --------------          --------
+  DPU0   Pensando DSC              N/A         Online              up    225207731731968
+  DPU1   Pensando DSC              N/A         Online              up    225207731731984
+  DPU2            N/A              N/A        Offline            down                N/A
 
 ```
 #### Pass/Fail Criteria

From a82d7490c6fad0f8bb5b6848b2b5d4f2e7087e93 Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Mon, 29 Jul 2024 16:52:35 -0700
Subject: [PATCH 7/8] Chaning the output of get_module_dpu_data_port  to a dict

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
index b64ebc1208..1429810217 100644
--- a/docs/testplan/SmartSwitch-PMON-testplan.md
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -74,7 +74,7 @@ The primary goal is to cover SmartSwitch specific PMON APIs. The corresponding C
  * is_smartswitch(self):
     * This API should return True
  * get_module_dpu_data_port(self, index):
-    * For index: 1 will return the dpu0 port association which is "Ethernet224: Ethernet0" where the string left of ":" (Ethernet224) is the NPU port and the string right of ":" (Ethernet0) is the DPU port.
+    * It will return a dict as shown below.
  
 
 #### Verify in

From 3f8e6db9cd0f218c6e144578570c0ad9e9da869f Mon Sep 17 00:00:00 2001
From: Ramesh Raghupathy <ram@cisco.com>
Date: Mon, 29 Jul 2024 17:18:08 -0700
Subject: [PATCH 8/8] Added a comments column to the test table and moved
 system-health related tests to phase:2

---
 docs/testplan/SmartSwitch-PMON-testplan.md | 36 +++++++++++-----------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/docs/testplan/SmartSwitch-PMON-testplan.md b/docs/testplan/SmartSwitch-PMON-testplan.md
index 1429810217..70367b11e1 100644
--- a/docs/testplan/SmartSwitch-PMON-testplan.md
+++ b/docs/testplan/SmartSwitch-PMON-testplan.md
@@ -42,24 +42,24 @@ The primary goal is to cover SmartSwitch specific PMON APIs. The corresponding C
 
 ## Objectives of Test Cases
 
-|    | **Test Case**   | **Intention**                              |
-| ---------- | ---------- | ---------------------------------------- |
-| 1.1 | Check SmartSwitch specific ChassisClass APIs      | To verify the newly implemented SmartSwitch specific ChassisClass APIs |
-| 1.2 | Check modified ChassisClass APIs for SmartSwitch       |  To verify the existing ChassisClass APIs that undergo minor changes with the addition of SmartSwitch|
-| 1.3 | Check DpuModule APIs for SmartSwitch       |  To verify the newly implemented  DpuModule APIs for SmartSwitch|
-| 1.4 | Check modified ModuleClass APIs for SmartSwitch       |  To verify the existing ModuleClass APIs that undergo minor changes with the addition of SmartSwitch|
-| 1.6 | Check the show reboot-cause CLI on the DPU       |  To verify the reboot-cause CLI on the DPU is unaffected |
-| 1.7 | Check the show reboot-cause history CLI on the DPU       |  To verify the reboot-cause history CLI on the DPU is unaffected|
-| 1.8 | Check the show reboot-cause CLI on the SWITCH       |  To verify the reboot-cause CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended|
-| 1.9 | Check the show reboot-cause history CLI on the SWITCH       |  To verify the reboot-cause history CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended|
-| 1.10 | Check the show system-health summary CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health summary" CLI work as expected |
-| 1.11 | Check the show system-health monitor-list CLI on the SWITCH        |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health monitor-list" CLI work as expected|
-| 1.12 | Check the show system-health detail CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health detail" CLI work as expected|
-| 1.13 | Check the show system-health dpu DPUx CLI on the SWITCH       |  To verify the newly implemented  show system-health dpu DPUx CLI for SmartSwitch reflects the midplane, control-plane, data-plane states of the DPU|
-| 1.14 | Check the cold startup of the DPUs and SWITCH       |  To verify the "chassisd", "chassis instance o database" are created and the admin state of the DPUs as defined in the config_db.json are applied properly |
-| 1.15 |  Check the startup config CLI       |  To verify the "config chassis modules startup DPUx" CLI does startup the DPU|
-| 1.16 | Check the shutdown config CLI        |   To verify the "config chassis modules shutdown DPUx" CLI does shutdown the DPU|
-| 1.17 | Check the reboot config CLI       |  To verify the "config chassis modules reboot SWITCH " CLI does reboot the SWITCH|
+|    | **Test Case**   | **Intention**                              | **Comments** |
+| ---------- | ---------- | ---------------------------------------- | ---------- |
+| 1.1 | Check SmartSwitch specific ChassisClass APIs      | To verify the newly implemented SmartSwitch specific ChassisClass APIs | |
+| 1.2 | Check modified ChassisClass APIs for SmartSwitch       |  To verify the existing ChassisClass APIs that undergo minor changes with the addition of SmartSwitch| |
+| 1.3 | Check DpuModule APIs for SmartSwitch       |  To verify the newly implemented  DpuModule APIs for SmartSwitch| |
+| 1.4 | Check modified ModuleClass APIs for SmartSwitch       |  To verify the existing ModuleClass APIs that undergo minor changes with the addition of SmartSwitch| |
+| 1.6 | Check the show reboot-cause CLI on the DPU       |  To verify the reboot-cause CLI on the DPU is unaffected | |
+| 1.7 | Check the show reboot-cause history CLI on the DPU       |  To verify the reboot-cause history CLI on the DPU is unaffected| |
+| 1.8 | Check the show reboot-cause CLI on the SWITCH       |  To verify the reboot-cause CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended| |
+| 1.9 | Check the show reboot-cause history CLI on the SWITCH       |  To verify the reboot-cause history CLI on the SWITCH is unaffected and the new extensions of the CLI work as intended| |
+| 1.10 | Check the show system-health summary CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health summary" CLI work as expected | Phase:2 |
+| 1.11 | Check the show system-health monitor-list CLI on the SWITCH        |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health monitor-list" CLI work as expected| Phase:2 |
+| 1.12 | Check the show system-health detail CLI on the SWITCH       |  To verify the new extensions such as "all, SWITCH, DPUx" of the show system-health detail" CLI work as expected| Phase:2 |
+| 1.13 | Check the show system-health dpu DPUx CLI on the SWITCH       |  To verify the newly implemented  show system-health dpu DPUx CLI for SmartSwitch reflects the midplane, control-plane, data-plane states of the DPU| Phase:2 |
+| 1.14 | Check the cold startup of the DPUs and SWITCH       |  To verify the "chassisd", "chassis instance o database" are created and the admin state of the DPUs as defined in the config_db.json are applied properly | |
+| 1.15 |  Check the startup config CLI       |  To verify the "config chassis modules startup DPUx" CLI does startup the DPU| |
+| 1.16 | Check the shutdown config CLI        |   To verify the "config chassis modules shutdown DPUx" CLI does shutdown the DPU| |
+| 1.17 | Check the reboot config CLI       |  To verify the "config chassis modules reboot SWITCH " CLI does reboot the SWITCH| |
 
 ## Test Cases