If you manage hot or cold redundant clusters within PulseNET, and one of the devices paired in the cluster fails, and must be replaced, the entire cluster must first be decommissioned.
If the device is swapped out without first decommissioning the cluster, the new device will not properly bind to the cluster.
Process to safely swap out a device in a cluster is as follows:
- Note the number of remote devices off of the cluster, and their Unit IDs if possible.
- Drill into the cluster via the Summary menu, then open the gear icon in the top right of the main cluster menu.
- Decommission the cluster from the top-level cluster menu, confirming that it will remove associated remotes as well.
- Perform the swap, replacing the bad radio with a new radio configured the same as the previous, and possessing the same IP address.
- Perform discovery on the active side of the cluster, and authorize it.
- Fail over to the inactive side, then discover this side of the cluster. Once returned, it should have recognized the device as possessing the same IP as the first side, and ask if you would like to create a cluster with the two devices.
- Confirm that serial number listed matches the new device, and not the previously discovered device, then authorize the cluster.
By default, the configuration settings should allow for auto-discovery to pull in the previously associated remotes as it polls passively. You will merely need to navigate to Auto-Discovery through the Administration menu (Standard) or the Summary gear icon (Enterprise) to authorize the devices once found. Alternatively, an active discovery can be attempted using the Unit IDs you previously recorded, or a full Unit ID range can be left to discover overnight or similar.