From 0660ee984429e6e1271c00998be64bf02295b5e6 Mon Sep 17 00:00:00 2001 From: Chris Date: Tue, 11 Jun 2024 14:38:31 -0400 Subject: [PATCH 1/2] splitting the Jira for 54838 into 2, adding kb for 57085, which is the original issue. --- ...5-I95-54838.md => 2024-04-25-I95-57085.md} | 2 +- kb/2024-06-11-I95-54838.md | 46 +++++++++++++++++++ 2 files changed, 47 insertions(+), 1 deletion(-) rename kb/{2024-04-25-I95-54838.md => 2024-04-25-I95-57085.md} (99%) create mode 100644 kb/2024-06-11-I95-54838.md diff --git a/kb/2024-04-25-I95-54838.md b/kb/2024-04-25-I95-57085.md similarity index 99% rename from kb/2024-04-25-I95-54838.md rename to kb/2024-04-25-I95-57085.md index d98dd8b645..2a1fc5a42f 100644 --- a/kb/2024-04-25-I95-54838.md +++ b/kb/2024-04-25-I95-57085.md @@ -9,7 +9,7 @@ Existing device to PCI mappings are not persistent across software upgrades. -**Issue ID:** I95-54838 +**Issue ID:** I95-57085 **Last Updated:** 2024-04-25 **Introduced in SSR Version:** 6.2.3 diff --git a/kb/2024-06-11-I95-54838.md b/kb/2024-06-11-I95-54838.md new file mode 100644 index 0000000000..ee725a57cd --- /dev/null +++ b/kb/2024-06-11-I95-54838.md @@ -0,0 +1,46 @@ +--- +title: Issues with memory sizing algorithm on large systems +date: 2024-6-11 +tags: ['6.2', '6.2.3-r2'] +hide_table_of_contents: false +--- + +Large-scale systems with many interfaces are not able to activate all interfaces + + + +**Issue ID:** I95-54838 +**Last Updated:** 2024-06-11 +**Introduced in SSR Version:** 6.2.3 + +### Problem + +Large systems with multiple numa locations and many interfaces configured may not initialize the configured interfaces. This results in a `MemoryAllocationException` in the `Device Disabled Error Reason` section of the `show device-interface detail` command output. Currently known systems exhibiting this issue are the **Dell 7515** and **AWS c5.18xlarge** deployed on AMD CPU’s. This issue is under investigation and will be resolved in a future release. + +### Release Notes + +### Severity +
+The potential impact of a software defect if encountered. Severity levels are: +* Critical: Could severely affect service, capacity/traffic, and maintenance capabilities. May have a prolonged impact to the entire system. +* Major: Could seriously affect system operation, maintenance, administration and related tasks. +* Minor: Would not significantly impair the functioning or affect service. +
+Minor + +### Status +Open + +### Resolved In + +### Product +SSR + +### Functional Area +Memory Sizing + +### Workaround +
+Juniper may provide a method to temporarily circumvent a problem; workarounds do not exist for all issues. +
+Reduce the number of configured SSR interfaces. \ No newline at end of file From c9295577212656cab349c95935dd31ba46ceb890 Mon Sep 17 00:00:00 2001 From: Chris Date: Thu, 13 Jun 2024 09:09:31 -0400 Subject: [PATCH 2/2] removing KB article for 54838 for now --- kb/2024-06-11-I95-54838.md | 46 -------------------------------------- 1 file changed, 46 deletions(-) delete mode 100644 kb/2024-06-11-I95-54838.md diff --git a/kb/2024-06-11-I95-54838.md b/kb/2024-06-11-I95-54838.md deleted file mode 100644 index ee725a57cd..0000000000 --- a/kb/2024-06-11-I95-54838.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Issues with memory sizing algorithm on large systems -date: 2024-6-11 -tags: ['6.2', '6.2.3-r2'] -hide_table_of_contents: false ---- - -Large-scale systems with many interfaces are not able to activate all interfaces - - - -**Issue ID:** I95-54838 -**Last Updated:** 2024-06-11 -**Introduced in SSR Version:** 6.2.3 - -### Problem - -Large systems with multiple numa locations and many interfaces configured may not initialize the configured interfaces. This results in a `MemoryAllocationException` in the `Device Disabled Error Reason` section of the `show device-interface detail` command output. Currently known systems exhibiting this issue are the **Dell 7515** and **AWS c5.18xlarge** deployed on AMD CPU’s. This issue is under investigation and will be resolved in a future release. - -### Release Notes - -### Severity -
-The potential impact of a software defect if encountered. Severity levels are: -* Critical: Could severely affect service, capacity/traffic, and maintenance capabilities. May have a prolonged impact to the entire system. -* Major: Could seriously affect system operation, maintenance, administration and related tasks. -* Minor: Would not significantly impair the functioning or affect service. -
-Minor - -### Status -Open - -### Resolved In - -### Product -SSR - -### Functional Area -Memory Sizing - -### Workaround -
-Juniper may provide a method to temporarily circumvent a problem; workarounds do not exist for all issues. -
-Reduce the number of configured SSR interfaces. \ No newline at end of file