RE item 1: Just do the lock and then unlock without the reboot in between. The unlock will reboot the host. Re item 3: Intent of Lock/Unlock is to recreate the host manifest and run it on the reboot recovery that occurs on the unlock. -----Original Message----- From: Pratik M. <pvmpublic@gmail.com> Sent: Wednesday, July 15, 2020 6:55 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Method to reboot controller-0 and oam-modify Hello everyone, Three questions from a newbie: 1. What is the recommended method to reboot a singleton controller-0. I do a "system host-lock" followed by a "system host-reboot". But when the controller comes back up it's status is locked. If I do an unlock, it reboots again. Can I rather just do a "sudo reboot" 2. How do I modify the OAM address in an AIO-DX setting? I did a "system oam-modify" but it does not take effect in Linux. Do I need to do a lock/unlock? Or a swact to controller-1 and back? 3. What is the intent of lock/unlock? Thanks in advance _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss