350-601 · Question #141
A network engineer repeatedly saves a configuration on Catalyst switches to NVRAM using the write memory command. What action should be taken to implement the same action on Nexus switches?
The correct answer is B. Use the alias command to use the write memory command. On Cisco Nexus switches running NX-OS, the 'write memory' command from IOS/Catalyst does not natively exist in the same form. The correct method to save the running configuration to NVRAM (startup-config) on NX-OS is 'copy running-config startup-config'. To allow engineers…
Question
A network engineer repeatedly saves a configuration on Catalyst switches to NVRAM using the write memory command. What action should be taken to implement the same action on Nexus switches?
Options
- AUse the write memory command to save the configuration.
- BUse the alias command to use the write memory command.
- CUse the exit command to leave the configuration mode and save the configuration automatically.
- DUse the wri command to use the copy running-config startup-config command.
How the community answered
(44 responses)- A2% (1)
- B89% (39)
- C2% (1)
- D7% (3)
Explanation
On Cisco Nexus switches running NX-OS, the 'write memory' command from IOS/Catalyst does not natively exist in the same form. The correct method to save the running configuration to NVRAM (startup-config) on NX-OS is 'copy running-config startup-config'. To allow engineers familiar with Catalyst/IOS to use the familiar 'write memory' syntax, option B is correct: use the CLI alias feature ('cli alias name wr copy running-config startup-config' or 'cli alias name write memory copy running-config startup-config'). Option A is incorrect because 'write memory' is not a default valid command on NX-OS without an alias. Option C is incorrect - NX-OS does not auto-save on exit. Option D references 'wri' which is also an alias abbreviation, not the underlying mechanism.
Topics
Community Discussion
No community discussion yet for this question.