| Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
| 5 | Operations |
| 6 | ========== |
| 7 | |
| 8 | Edge shutdown procedure |
| 9 | ----------------------- |
| 10 | |
| 11 | To gracefully shutdown an Aether Edge Pod, follow the following steps: |
| 12 | |
| 13 | 1. Shutdown the fabric switches using ``shutdown -h now`` |
| 14 | |
| 15 | 2. Shutdown the compute servers using ``shutdown -h now`` |
| 16 | |
| 17 | 3. Shutdown the management server using ``shutdown -h now`` |
| 18 | |
| 19 | 4. The management switch and eNB aren't capable of a graceful shutdown, so no |
| 20 | steps need to be taken for that hardware. |
| 21 | |
| 22 | 5. Remove power from the pod. |
| 23 | |
| 24 | .. note:: |
| 25 | |
| 26 | The shutdown steps can be automated with an :doc:`ad-hoc ansible command |
| 27 | <ansible:user_guide/intro_adhoc>` and you have an ansible inventory of all |
| 28 | the systems:: |
| 29 | |
| 30 | ansible -i inventory/sitename.ini -b -m shutdown -a "delay=60" all |
| 31 | |
| 32 | The ``delay=60`` arg is to allow hosts behind the management server to be |
| 33 | reached before the management server shuts down. |
| 34 | |
| 35 | Edge power up procedure |
| 36 | ----------------------- |
| 37 | |
| 38 | 1. Restore power to the pod equipment. The fabric and management switches will |
| 39 | power on automatically. |
| 40 | |
| 41 | 2. Turn on the management server using the front panel power button |
| 42 | |
| 43 | 3. Turn on the compute servers using the front panel power buttons |