Closed wdiane1 closed 2 years ago
@wdiane1 Thank you for your feedback! I'll follow up on this issue and get back to you as soon as possible.
@wdiane1 Step 16 on Install and boot node3 the page explains why the setenv kmip.init.maxwait off variable is set to "off": "If NetApp Storage Encryption (NSE) is in use on this configuration, the "setenv bootarg.storageencryption.support" command must be set to true, and the "kmip.init.maxwait" variable needs to be set to off to avoid a boot loop after the node1 configuration is loaded" Closing this comment. Thanks again!
Turning maxwait off will cause a permanent lockout of the NSE drives if the NSE drives are power-cycled.
From: Paula Carrigan @.> Sent: Wednesday, May 25, 2022 11:37 AM To: NetAppDocs/ontap-systems-upgrade @.> Cc: Williford, Diane @.>; Mention @.> Subject: Re: [NetAppDocs/ontap-systems-upgrade] Why is the setenv kmip.init.maxwait off being set? (Issue #31)
NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@wdiane1https://github.com/wdiane1 Step 16 on page: Install and boot node3https://docs.netapp.com/us-en/ontap-systems-upgrade/upgrade-arl-auto-app/install_boot_node3.html explains why the setenv kmip.init.maxwait off variable is set to "off": "If NetApp Storage Encryption (NSE) is in use on this configuration, the "setenv bootarg.storageencryption.support" command must be set to true, and the "kmip.init.maxwait" variable needs to be set to off to avoid a boot loop after the node1 configuration is loaded" Closing this comment. Thanks again!
- Reply to this email directly, view it on GitHubhttps://github.com/NetAppDocs/ontap-systems-upgrade/issues/31#issuecomment-1137448601, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AORTZV2PJM2HCEJ73WGIIWLVLZCIDANCNFSM5VWN75KA. You are receiving this because you were mentioned.Message ID: @.**@.>>
Page: Install and boot node3