MeshDB Status Values
Node Status
| Value | Description |
| Planned | An assignment of a network number to one or more install numbers that has not yet been brought online. This happens commonly when planning for new large hubs, but can apply to smaller installs also |
| Active | A nominally routable network number on the mesh |
| Inactive | A node which was active but is no longer connected to the mesh due to disassembly, abandonment, etc. If a node drops offline for a few days, it does not need to be marked Inactive, but if it is offline for a month or more, or is known to have been taken down, it should be marked Inactive |
Install Status
| Value | Description |
| Request Received | Default status when an install is created. It indicates that the join form has been submitted for the specified unit, but not much more |
| Pending | This install has LOS and an install has been scheduled, or is in the process of getting scheduled. We expect to connect this install in the near future. Installs should not remain in this status longer than 6 months |
| Blocked | We have received some kind of confirmation that the install identified by this row is 1) interested in getting connected and 2) is unable to actually go through with an install. Usually due to a landlord not cooperating |
| Active | A nominally connected unit, with active service |
| Inactive | This is a physically connected unit, with equipment in place but the equipment is not communicating with the mesh. This may be due to a power, cable, or software issue. Installs in this status are expected to reactivate at some point the future. If the install has been physically taken down or completely abandoned, it should be marked as Closed instead If an install drops offline for a few days, it does not need to be marked Inactive, but if it is offline for a month or more, this status is likely appropriate Installs should not remain in this status longer than 2 years |
| Closed | This install request is no longer something we are interested in tracking. This could be because the person communicated disinterest, asked to unsubscribe, gave invalid information in the join form. This status is also used for installs that have been abandoned, or physically taken down, and are not expected to be reactivated This could also be a duplicate of another install request |
| NN Reassigned | A special status for low-numbered installs indicating that this install number has been re-used as a network number for another node and is not safe to use as a network number for this install, should the unit associated with this install seek to get connected |
Link Status
| Value | Description |
| Planned | A future link that might be added to the mesh, if the specified devices are deployed. Does not need to be actively scheduled, but should have some chance at feasibly being completed (don't enter planned links that clearly have no LOS for example) |
| Active | A nominally online link that is able to pass traffic between its specified devices. That does not necessarily mean it is a primary path for any internet traffic (e.g. WDS backup links) |
| Inactive | A link which was active but is no longer able to pass traffic due to disassembly, abandonment, loss of LOS, etc. If a link drops offline for a few days, it does not need to be marked Inactive, but if it is offline for a month or more, or is known to have been taken down, it should be marked Inactive |
Device Status
| Value | Description |
| Planned | A future device that might be added to the mesh. Does not need to be actively scheduled, but should have some chance at feasibly being completed |
| Active | A nominally online device that is reachable on the mesh |
| Inactive | A device which was active but is no longer online due to disassembly, abandonment, power issue, etc. If a device drops offline for a few days, it does not need to be marked Inactive, but if it is offline for a month or more, or is known to have been taken down, it should be marked Inactive |