What can I help you with?
NMX Manager (NMX-M) Documentation v85.1.1000

Known Issues

Internal Reference Number

Issue

4369284

Description: The Loki pods responsible for handling log data in the NMX-M environment may run out of storage, leading to crashes. This can disrupt log aggregation and prevent users from viewing logs. The issue occurs when the assigned storage capacity is exceeded.

Workaround: To mitigate this issue, run the following commands:

  • Delete Loki PVC:

    kubectl -n infra delete pvc storage-loki-0 --wait=false

  • Delete Loki pod to trigger re-creation:

    kubectl -n infra delete pod loki-0

Keywords: Loki pods; log aggregation; storage

Discovered in Version: 85.1.1000

4355456

Description: The registration of services (NMX-T & NMX-C) is only available when all three nodes of NMX-M are up and running.

Workaround: N/A

Keywords: NMX-T; NMX-C

Discovered in Version: 85.1.1000

4367335

Description: The following PUT requests execute successfully despite potentially returning an HTTP 500 Internal Server Error:

  • http://localhost:8084/nmx/v1/compute-nodes

  • http://localhost:8084/nmx/v1/switch-nodes/

  • http://localhost:8084/nmx/v1/gpus/

  • http://localhost:8084/nmx/v1/switches/

  • http://localhost:8084/nmx/v1/chassis/

Workaround: N/A

Keywords: PUT; HTTP 500 Error

Discovered in Version: 85.1.1000

4363356

Description: After installation, NMX services take up to 10 minutes to start and stabilize.

Workaround: N/A

Keywords: Installation

Discovered in Version: 85.1.1000

© Copyright 2025, NVIDIA. Last updated on Mar 24, 2025.