ONTAP Hardware

Node reboot

not_a_Lone_wolf

Hi. I want to understand the difference between below reboot procedures:

1>Takeover /Giveback -cluster prompt

2> System node reboot-system prompt

3> Halt and power on the node -cluster prompt

4> boot_ontap from loader prompt

1 ACCEPTED SOLUTION

aladd

1. Takeover and giveback have multiple options available, however we'll focus on the basic.

this option performs a graceful takeover of the target nodes storage, starting with the SFO (data) aggregates, and then the CFO (root) aggregate. The target node then reboots and will go into waiting for giveback (WFG) state.

 

2. system node reboot, is still from the cluster prompt but uses a command subset of "system" instead of "storage failover" as in a takeover/giveback operation. This performs a reboot of the target node, which will boot into WFG as well. This as well has multiple options available to it, such as preventing a takeover by the partner node (default is to allow the partner to takeover).

 

3. Halting a node (system node halt) will halt the target node at the loader prompt. there are options here as well to prevent a takeover by the partner node.

 

4. boot_ontap from loader simply boots the node into ONTAP or into a WFG state depending on previous status and state of the partner.

 

 

Hope this helps!

View solution in original post

2 REPLIES 2

aladd

1. Takeover and giveback have multiple options available, however we'll focus on the basic.

this option performs a graceful takeover of the target nodes storage, starting with the SFO (data) aggregates, and then the CFO (root) aggregate. The target node then reboots and will go into waiting for giveback (WFG) state.

 

2. system node reboot, is still from the cluster prompt but uses a command subset of "system" instead of "storage failover" as in a takeover/giveback operation. This performs a reboot of the target node, which will boot into WFG as well. This as well has multiple options available to it, such as preventing a takeover by the partner node (default is to allow the partner to takeover).

 

3. Halting a node (system node halt) will halt the target node at the loader prompt. there are options here as well to prevent a takeover by the partner node.

 

4. boot_ontap from loader simply boots the node into ONTAP or into a WFG state depending on previous status and state of the partner.

 

 

Hope this helps!

View solution in original post

not_a_Lone_wolf

Thanks a lot  

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public