Question

A data center engineer is developing a RESTCONF client to manage interface descriptions on a Nexus 9000 switch running NX-OS. The client currently sends an HTTP PUT to the resource URI for a specific interface containing only the 'description' leaf. After the call, the engineer notices that other previously configured attributes on that same interface node (such as MTU and speed settings within the same YANG container) have been reset to their defaults. What is the most likely cause, and how should the request be changed to update only the description without affecting other attributes?

Accepted Answer

PUT replaces the entire target resource with the supplied content; use HTTP PATCH to merge only the specified leaf into the existing configuration.

Answer

PUT is read-only in RESTCONF; use HTTP POST to the interface URI to create a new merge operation for the description leaf.

Answer

The Accept header is set to XML instead of JSON; switching to application/yang-data+json will preserve the untouched leaves.

Answer

The candidate datastore was not locked before the write; issuing a GET with the lock parameter before PUT will prevent attribute loss.