Skip to content

Conversation

@Chr1st0ph3rTurn3r
Copy link
Contributor

No description provided.


### 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not in the headline, but here we need to quantify what "large-scale system" means.
Is there a certain amount of interfaces and memory combination that runs into this problem?

The workaround suggests that this issue arrises when a certain number of interfaces are configured. That needs to be explained in the problem section.

<details>
Juniper may provide a method to temporarily circumvent a problem; workarounds do not exist for all issues.
</details>
Reduce the number of configured SSR interfaces. No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which interfaces should be removed? How many?

@Chr1st0ph3rTurn3r Chr1st0ph3rTurn3r merged commit e551729 into master Jun 13, 2024
@Chr1st0ph3rTurn3r Chr1st0ph3rTurn3r deleted the caveat-for-6.2.x branch June 13, 2024 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants