diff --git a/docs/user-guide/shrink-expand.md b/docs/user-guide/shrink-expand.md index e69d120..d187b2f 100644 --- a/docs/user-guide/shrink-expand.md +++ b/docs/user-guide/shrink-expand.md @@ -22,22 +22,23 @@ connections may differ based on the `Switch` role given to the device. For more section](connections.md). !!! note - Switch devices should be booted in `ONIE` installation mode to install SONiC OS and configure the Fabric + Switch devices need to be booted in `ONIE` installation mode to install SONiC OS and configure the Fabric Agent. Ensure the management port of the switch is connected to fabric management network. ### Remove a switch from the existing fabric -Before you decommission a switch from the Hedgehog Fabric, several preparation steps are necessary. - -!!! warning - Currently the `Wiring` diagram used for initial deployment is saved in - `/var/lib/rancher/k3s/server/manifests/hh-wiring.yaml` on the `Control` node. Fabric will sustain objects within the - original wiring diagram. In order to remove any object, first remove the dedicated API objects from this file. It is - recommended to reapply `hh-wiring.yaml` after changing its internals. +Before you decommission a switch from the Hedgehog Fabric, several preliminary steps are necessary. * If the `Switch` is a `Leaf` switch (including `Mixed` and `Border` leaf configurations), remove all `VPCAttachments` bound to all switches `Connections`. * If the `Switch` was used for `ExternalPeering`, remove all `ExternalAttachment` objects that are bound to the `Connections` of the `Switch`. * Remove all connections of the `Switch`. * At last, remove the `Switch` and `Agent` objects. + +### Replace a switch from the existing fabric + +To replace a switch in the fabric, you do not need to remove and re-add it. Instead: + +* Edit the existing switch object to update the `MAC` address or `Serial` number of the new hardware. +* Reinstall the switch, following the boot `ONIE` process used when it was first added to the fabric.