NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

ONTAP Hardware

[Question] The difference between "bye, bye -g" and "boot_ontap" in NetApp ONTAP.

hojun
3,449 Views
Hello, everyone.
 
I am curious about the differences between the commands "bye", "bye -g", and "boot_ontap" in the LOADER state.
For example, after replacing an NVDIMM on an AFF-A700s, we execute boot_ontap, but after replacing an NVDIMM on an AFF-A700, we use bye. I would like to understand the reason behind this difference.
Additionally, I would appreciate your advice on the differences between bye and bye -g.
 
Finally, a 1TB disk is installed in the Flash Cache Card Slot on the AFF-A700.
However, it is identified as a core dump device rather than serving as a Flash Cache.
Is the disk installed in this slot used exclusively for core dump purposes?
 
::> sysconfig -a output
slot 6-1: NVMe Coredump Device
Additional Info:    0X917011900207B0SAM00PM17330001T00015000
Serial Number:      S5MTNA0T300108
Firmware Version:   NA00
Capacity:           894 GB
Sector Size:        512B/sect
 
Thank you!
have a good day.
1 ACCEPTED SOLUTION

andris
3,387 Views

boot_ontap boots the ONTAP operating system from the LOADER.  You use this any time you want to bring up the system from LOADER.

 

bye performs a warm reset of the controller (CPU complex). You use "bye" any time you have any hardware (additions, removals, replacements) or system firmware (BIOS/LOADER) changes in the system.

 

bye -g performs a global reset of the controller (including CPU complex and internal CPU firmware, such as the management engine). It's somewhat vestigial, in that the "bye" command will automatically invoke "bye -g" in situations where it is necessary.


In your NVDIMM example, it doesn't really matter if you use boot_ontap or bye, since the controller was pulled out for the NVDIMM replacement. So, you have already "power-cycled" the PCM/controller post-replacement, in effect.

 

In platforms such as the AFF-A700 where I/O and NVRAM modules can be independently added/removed/replaced while the PCM/motherboard is still sitting at the LOADER prompt, bye is required to re-enumerate all of the PCIe devices now in the system.

 

X9170A "Core Dump Device":
See: How to configure A700 systems with X9170A core dump device

View solution in original post

2 REPLIES 2

andris
3,388 Views

boot_ontap boots the ONTAP operating system from the LOADER.  You use this any time you want to bring up the system from LOADER.

 

bye performs a warm reset of the controller (CPU complex). You use "bye" any time you have any hardware (additions, removals, replacements) or system firmware (BIOS/LOADER) changes in the system.

 

bye -g performs a global reset of the controller (including CPU complex and internal CPU firmware, such as the management engine). It's somewhat vestigial, in that the "bye" command will automatically invoke "bye -g" in situations where it is necessary.


In your NVDIMM example, it doesn't really matter if you use boot_ontap or bye, since the controller was pulled out for the NVDIMM replacement. So, you have already "power-cycled" the PCM/controller post-replacement, in effect.

 

In platforms such as the AFF-A700 where I/O and NVRAM modules can be independently added/removed/replaced while the PCM/motherboard is still sitting at the LOADER prompt, bye is required to re-enumerate all of the PCIe devices now in the system.

 

X9170A "Core Dump Device":
See: How to configure A700 systems with X9170A core dump device

hojun
3,362 Views

You explained it in detail, so I was able to understand it.
Thank you very much.

Public