Merge pull request #934 from 128technology/move-docs-498-to-own-pr

Resolve I95-58622 and DOCS 498

Author: Chr1st0ph3rTurn3r

docs/concepts_ssr_idp.md

@@ -95,10 +95,19 @@ Starting with SSR 6.1.4-R2, users can customize an existing IDP policy, creating
 The SSR IDP engine requires a dedicated core. When the SSR is configured with `forwarding-core-mode` as automatic, the system automatically assigns cores based on the hardware type, as well as an additional core for IDP. 
 
 When the router is configured with `forwarding-core-mode` as manual, the administrator must account for the `forwarding-core-count` to include IDP core. For an HA router, each node follows the above scheme.
+
 :::note
 The system requires a reboot for the IDP core allocation; after upgrading to SSR 6.x for the first time, an additional reboot is required to enable the IDP engine.
 :::
 
+Software version 6.3.3-R2 introduces the support of multi-core capabilities for IDP for image-based routers. For customers running IDP on image-based firmware versions (6.3.0-R1 and under) on the SSR1300, SSR1400, and SSR1500, IDP multicore will be automatically enabled when upgrading to 6.3.3-R2. In some cases, after an upgrade the IDP engine can fail to start as it transitions from single-core to multi-core mode. When the IDP engine fails to start, the following alarm will be generated on the system: `IDP engine unable to start; reboot-required`. In this situation, it is required to reboot the system post-upgrade allocate system resources with IDP multi-core enabled. A reboot is required for any subsequent disable/enable actions.
+
+For legacy package-based routers, multi-core IDP capability is not supported, and those systems will continue to operate in the single-core mode.
+
+:::note 
+Multi-core IDP is not available on the following SSR devices: SSR120, SSR130, SSR1200, SSR400, and SSR440. 
+:::
+
 ## Limitations
 
 The following is a list of the current limitations of the IDP solution. 

docs/release_notes_128t_6.3.md

@@ -396,6 +396,11 @@ Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must b
 ### Caveats
 
 - **I95-58622 IDP Engine Intermittent Start-up:** 6.3.3-R2 introduces the support of multi-core capabilities for IDP for image-based routers. For legacy package-based routers, multi-core IDP capability is not supported, and those systems will continue to operate in the single-core mode. For customers running IDP on older image-based firmware versions (6.3.0-R1 and under) on the SSR1300, SSR1400, and SSR1500, IDP multicore will be automatically enabled when upgrading to 6.3.3-R2. In some cases, after an upgrade the IDP engine can fail to start as it transitions from single-core to multi-core mode. When the IDP engine fails to start, the following alarm will be generated on the system:  `IDP engine unable to start; reboot-required`. In this situation, it is recommended to reboot the system post-upgrade to ensure future reliable reboots with IDP multi-core enabled.
+
+:::note 
+Multi-core IDP is not available on the following SSR devices: SSR120, SSR130, SSR1200, SSR400, and SSR440. 
+:::
+
 ------
 - **I95-58782 `node.js` process may crash on SSR120, SSR130, and other branch router devices while generating Swagger documentation:** The `node.js` process may crash on SSR120, SSR130, and other branch router devices during SSR application startup while generating Swagger documentation. This is due to an internal error, and will generate a `node.js` coredump, but has **no impact** on the SSR. Swagger documentation is generated on a subsequent restart of the SSR. This is not service impacting.
 ------