bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Restructured Documentation
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 8s
Details

Browse Source
This commit is contained in:
Nicole Rappe
2026-09-05 14:08:43 -06:00
parent c4bd235eba
commit 289769a601
281 changed files with 5403 additions and 3563 deletions
Download Patch File Download Diff File Expand all files Collapse all files
reference/Lab Map/Hardware/Cluster Node 01 Disk Layout.md
+20
View File
@@ -0,0 +1,20 @@
---
tags:
- Disk Arrays
- Storage
- Hardware
---
## Purpose
This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
!!! note "Disk Order Structure"
Disks are represented in 4 columns, with the drive positions / topology mirroring the table seen below.
| **Column 01** | **Column 02** | **Column 03** | **Column 04** |
| :--- | :--- | :--- | :--- |
| 240GB<br>`SN: 50026B77850B2DA9` | 240GB<br>`SN: 50026B7784D34038` | 240GB<br>`SN: 50026B7784E8A771` | 240GB<br>`SN: 50026B7784E8CB49` |
| 240GB<br>`SN: 50026B7784D3620D` | 240GB<br>`SN: 50026B7784D45C34` | 240GB<br>`SN: 50026B7784E8AC95` | 240GB<br>`SN: 50026B7784E8A983` |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Hardware/Cluster Node 02 Disk Layout.md
+26
View File
@@ -0,0 +1,26 @@
---
tags:
- Disk Arrays
- Storage
- Hardware
---
## Purpose
This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
!!! note "Disk Order Structure"
Disks are represented in 3 columns, with the top-down view representing left-to-right.
| **Column 01** | **Column 02** | **Column 03** |
| :--- | :--- | :--- |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR31DHQ` |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR4fHA0` |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR31DJL` |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR33GBT` |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR31D8L` |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR33F2W` |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 600GB<br>`SN: 6XR32TFE` |
| EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Hardware/Cluster Node 03 Disk Layout.md
+21
View File
@@ -0,0 +1,21 @@
---
tags:
- Disk Arrays
- Storage
- Hardware
---
## Purpose
This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
!!! note "Disk Order Structure"
Disks are represented in 4 columns, with the drive positions / topology mirroring the table seen below.
| **Column 01** | **Column 02** | **Column 03** | **Column 04** |
| :--- | :--- | :--- | :--- |
| 8TB<br>`SN: X1P0A01NFDWF` | 8TB<br>`SN: WWZ1TJT2` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` |
| 8TB<br>`SN: VRK6M6MK` | 8TB<br>`SN: Y1L0A0QQFDWF` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` |
| 8TB<br>`SN: VRK6XEMK` | EMPTY<br>`SN: N/A` | EMPTY<br>`SN: N/A` | 1TB<br>`SN: 2417E8A9A7C1` |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Hardware/Storage Node 01 TrueNAS Core Disk Layout.md
+27
View File
@@ -0,0 +1,27 @@
---
tags:
- TrueNAS
- Disk Arrays
- Storage
- Hardware
---
## Purpose
This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
!!! note "Disk Order Structure"
Disks are represented in 4 columns, with the drive positions / topology mirroring the table seen below.
!!! note "Boot Drive"
Boot drive is an external Samsung PSSD T7 portable SSD. Serial Number: `S6U5NS0RC09159R`
| **Column 01** | **Column 02** | **Column 03** | **Column 04** | **Column 05** |
| :--- | :--- | :--- | :--- | :--- |
| 960GB<br>`SN: 50026B778526FF9F` | 960GB<br>`SN: 50026B778527104D` | 960GB<br>`SN: 50026B778526FFAD` | 960GB<br>`SN: 50026B7785270727` | 960GB<br>`SN: 50026B778526FCD2` |
| 960GB<br>`SN: 50026B7785270194` | 960GB<br>`SN: 50026B77853B0F4C` | 960GB<br>`SN: 50026B7785270EB4` | 960G<br>`SN: 50026B76870D497D` | 960GB<br>`SN: 50026B778526FCC8` |
| 960GB<br>`SN: 50026B778526F8F2` | 960GB<br>`SN: 50026B778526F8EB` | 960GB<br>`SN: 50026B778526FCFC` | 960GB<br>`SN: 50026B76870D47DF` | 960GB<br>`SN: 50026B778526F8EC` |
| 960GB<br>`SN: 50026B7785270E2A` | 960GB<br>`SN: 50026B7785270653` | 960GB<br>`SN: 50026B778526FF67` | 960GB<br>`SN: 50026B7384228B63` | 960GB<br>`SN: 50026B778526FF4A` |
| 960GB<br>`SN: 50026B778526FFAA` | 960GB<br>`SN: 50026B778526FFC7` | 960GB<br>`SN: 50026B778526FF49` | 1TB<br>`SN: SI04T000311404D40` | EMPTY<br>`SN: N/A` |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Hardware/Storage Node 02 TrueNAS Scale Disk Layout.md
+20
View File
@@ -0,0 +1,20 @@
---
tags:
- TrueNAS
- Disk Arrays
- Storage
- Hardware
---
## Purpose
This document is meant to help keep track disks and their associated serial numbers for replacement and recordkeeping purposes.
!!! note "Disk Order Structure"
Disks are represented in 1 column, with the drive positions / topology mirroring the table seen below.
| **Slot 01** | **Slot 02** | **Slot 03** | **Slot 04** | **Slot 05** |
| :--- | :--- | :--- | :--- | :--- |
| 4TB<br>`SN: Z305ZNZM` | 4TB<br>`SN: Z305SPL8` | 4TB<br>`SN: Z3051AF8` | 4TB<br>`SN: Z305ZNM1` | 4TB<br>`SN: Z305S03R` |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Hardware/iLO License Reference.md
+27
View File
@@ -0,0 +1,27 @@
---
tags:
- iLO
- Hardware
- Licensing
---
## Purpose
Preserve the recorded iLO license reference and its existing usage limitations for lab hardware.
!!! info "Assumptions of Usage"
It should go without saying, using one of these keys does not entitle you to support by Hewlett-Packard Enterprise. These are meant for homelab environments where licensing / auditing does not matter.
| **iLO Version** | **License Key** |
| :--- | :--- |
| iLO Standard Trial | `34T6L-4C9PX-X8D9C-GYD26-8SQWM` |
| iLO 1 Advanced | `247RH-ZPJ8S-7B17D-FCE55-DDD17` |
| iLO 2 / 3 / 4 Advanced | `35DPH-SVSXJ-HGBJN-C7N5R-2SS4W` |
| iLO 2 / 3 / 4 / 5 Advanced | `35SCR-RYLML-CBK7N-TD3B9-GGBW2` |
!!! warning "Do not Use in Production Work Environments"
In (rare) cases, these keys can be used as a temporary solution when working in a work environment, then promptly removed after the work is performed. Leaving them installed on a server could lead to legal consequences if Hewlett-Packard Enterprise asked for it while providing support, and it was using one of these keys, it could fail a software licensing audit.
`REMOVE THE KEY AFTER USAGE`
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Homelab Server Inventory.md
+254
View File
@@ -0,0 +1,254 @@
---
tags:
- iptables
- Networking
- Docker
---
## Purpose
Use this reference for homelab server inventory and the environment-specific values recorded below.
!!! info "Inventory Reconciliation"
This reference preserves the recorded host and group assignments. Some deployment examples use different hostnames or addresses; reconcile those differences with the running environment before changing inventory or applying a procedure.
## Overview
All servers (physical and virtual) are documented within this specific page. They are written in a specific annotated manner in order to make them copy/paste ready for the Ansible AWX Operator server that interacts with devices in the homelab over `SSH` and `WinRM` protocols. This allows me to automate functions such as updates across the entire homelab declaratively versus individually.
**Note**: This list does not include Docker/Kubernetes-based workloads/servers. Those can be found within the [Container Network IP Table](<Network Address Plans/192.168.5.0 Container Network.md>) document. Given that Ansible does not interact with containers in my homelab (*yet*), these devices are not listed within this document.
## Updating Ansible Inventory
Whenever changes are made here, they need to be replicated to the production Ansible AWX Inventory File. This ensures that Ansible AWX is always up-to-date. Simply copy/paste the codeblock below into the linked inventory file, and commit the change with a comment explaining what was added/removed from the inventory list.
[:material-ansible: Edit Ansible AWX Inventory File](https://git.bunny-lab.io/GitOps/awx.bunny-lab.io/_edit/main/inventories/homelab.ini){ .md-button }
```ini title="https://git.bunny-lab.io/GitOps/awx.bunny-lab.io/src/branch/main/inventories/homelab.ini"
# ----------------------------------------------------------------- #
# Servers (Physical and Virtual) - Hosts Mapped to IPs / FQDNs #
# ----------------------------------------------------------------- #
# Deep Nodes
deep-node ansible_host=10.0.0.20
lab-pfsense-01 ansible_host=192.168.3.1 # (1)
lab-mini-pc ansible_host=192.168.3.2 # (2)
lab-storage-01 ansible_host=192.168.3.3 # (3)
cluster-node-01 ansible_host=192.168.3.4 # (4)
cluster-node-02 ansible_host=192.168.3.5 # (5)
lab-games-04 ansible_host=lab-games-04.bunny-lab.io # (6)
lab-photos-01 ansible_host=lab-photos-01.bunny-lab.io # (7)
kb-bunny-lab-io ansible_host=kb.bunny-lab.io # (8)
lab-fog-01 ansible_host=192.168.3.9 # (9)
lab-ansible-01 ansible_host=lab-ansible-01.bunny-lab.io # (10)
lab-games-02 ansible_host=lab-games-02.bunny-lab.io # (11)
lab-dhcp-01 ansible_host=lab-dhcp-01.bunny-lab.io # (12)
lab-dhcp-02 ansible_host=lab-dhcp-02.bunny-lab.io # (13)
lab-games-03 ansible_host=lab-games-03.bunny-lab.io # (14)
lab-mail-gw-01 ansible_host=192.168.3.15 # (15)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (16)
lab-traefik-01 ansible_host=traefik.bunny-lab.io # (17)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (18)
#container-node-01 ansible_host=container-node-01.bunny-lab.io # (19)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (20)
lab-puppet-01 ansible_host=lab-puppet-01.bunny-lab.io # (21)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (22)
usagi-cluster ansible_host=usagi-cluster.bunny-lab.io # (23)
lab-pool-01 ansible_host=lab-pool-01.bunny-lab.io # (24)
lab-dc-01 ansible_host=lab-dc-01.bunny-lab.io # (25)
lab-dc-03 ansible_host=lab-dc-03.bunny-lab.io # (26)
lab-camera-01 ansible_host=lab-camera-01.bunny-lab.io # (27)
lab-games-01 ansible_host=lab-games-01.bunny-lab.io # (28)
lab-cloud-01 ansible_host=lab-cloud-01.bunny-lab.io # (29)
deeplab-win11 ansible_host=deeplab-win11.dev-testing.lab # (30)
lab-dt-02 ansible_host=lab-dt-02.bunny-lab.io # (31)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (32)
cluster-node-03 ansible_host=192.168.3.33 # (33)
lab-draas-01-ilo ansible_host=192.168.3.34 # (34)
deeplab-dc ansible_host=deeplab-dc-01.dev-testing.lab # (35)
deeplab-win10 ansible_host=deeplab-win10.dev-testing.lab # (36)
# NOT-IN-USE ansible_host=192.168.3.37 # (37)
# NOT-IN-USE ansible_host=192.168.3.38 # (38)
# NOT-IN-USE ansible_host=192.168.3.39 # (39)
# NOT-IN-USE ansible_host=192.168.3.40 # (40)
# NOT-IN-USE ansible_host=192.168.3.41 # (41)
# NOT-IN-USE ansible_host=192.168.3.42 # (42)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (43)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (44)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (45)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (46)
# NOT-IN-USE ansible_host=NOT-IN-USE.bunny-lab.io # (47)
lab-docker-02 ansible_host=192.168.3.48 # (48)
lab-fps-01 ansible_host=192.168.3.49 # (49)
# NOT-IN-USE ansible_host=192.168.3.50 # (50)
# NOT-IN-USE ansible_host=192.168.3.51 # (51)
# NOT-IN-USE ansible_host=192.168.3.52 # (52)
# NOT-IN-USE ansible_host=192.168.3.53 # (53)
veeam-draas-01 ansible_host=192.168.3.54 # (54)
# NOT-IN-USE ansible_host=192.168.3.55 # (55)
# NOT-IN-USE ansible_host=192.168.3.56 # (56)
# NOT-IN-USE ansible_host=192.168.3.57 # (57)
lab-photos-02 ansible_host=192.168.3.58 # (58)
lab-ca-01 ansible_host=192.168.3.59 # (59)
lab-ca-02 ansible_host=192.168.3.60 # (60)
lab-mail-02 ansible_host=192.168.3.61 # (61)
# NOT-IN-USE ansible_host=192.168.3.62 # (62)
# NOT-IN-USE ansible_host=192.168.3.63 # (63)
lab-iso-01 ansible_host=192.168.3.64 # (64)
# NOT-IN-USE ansible_host=192.168.3.65 # (65)
# NOT-IN-USE ansible_host=192.168.3.66 # (66)
lab-fps-02 ansible_host=192.168.3.67 # (67)
lab-pbs-01 ansible_host=192.168.3.68 # (68)
cluster-laptop-node-01 ansible_host=192.168.3.69 # (69)
cluster-laptop-node-02 ansible_host=192.168.3.70 # (70)
cluster-laptop-node-03 ansible_host=192.168.3.71 # (71)
cluster-laptop-node-01 ansible_host=192.168.3.72 # (72)
cluster-laptop-node-05 ansible_host=192.168.3.73 # (73)
# NOT-IN-USE ansible_host=192.168.3.74 # (74)
# NOT-IN-USE ansible_host=192.168.3.75 # (75)
borealis-engine-02 ansible_host=192.168.3.251 # (251)
borealis-engine-01 ansible_host=192.168.3.252 # (252)
deeplab-node-02 ansible_host=192.168.3.253 # (253)
core-switch-01 ansible_host=192.168.3.254 # (254)
# ----------------------------------------------------------------- #
# Host Groups - Various Logical Groupings of Devices #
# ----------------------------------------------------------------- #
[domainControllers]
lab-dc-01
lab-dc-03
[windowsDomainServers]
lab-games-04
lab-games-02
lab-games-03
lab-games-05
lab-dc-01
lab-dc-03
lab-camera-01
lab-games-01
lab-ca-01
lab-ca-02
lab-mail-02
[windowsStandaloneServers]
#lab-dt-02
[linuxServers]
lab-photos-01
lab-photos-02
lab-puppet-01
lab-cloud-01
lab-docker-02
lab-iso-01
[workstations]
lab-operator-01
# ----------------------------------------------------------------- #
# Host Group Variables - Defining Specific Requirements of Groups #
# ----------------------------------------------------------------- #
[domainControllers:vars]
ansible_connection=winrm
ansible_port=5986
ansible_winrm_transport=kerberos
ansible_winrm_scheme=https
ansible_winrm_server_cert_validation=ignore
[windowsDomainServers:vars]
ansible_connection=winrm
ansible_port=5986
ansible_winrm_transport=kerberos
ansible_winrm_scheme=https
ansible_winrm_server_cert_validation=ignore
[windowsStandaloneServers:vars]
ansible_connection=winrm
ansible_winrm_kerberos_delegation=false
ansible_port=5986
ansible_winrm_transport=ntlm
ansible_winrm_server_cert_validation=ignore
[linuxServers:vars]
ansible_connection=ssh
```
1. pfSense Firewall @ `192.168.3.1` | [Documentation](https://www.pfsense.org/getting-started/)
2. 3.7GHz High-Performance Mini-PC @ `192.168.3.2`
3. TrueNAS Core Server @ `192.168.3.3` | [Documentation](https://www.truenas.com/truenas-core/)
4. ProxmoxVE Virtualization Node @ `192.168.3.4`
5. ProxmoxVE Virtualization Node @ `192.168.3.5`
6. Satisfactory Dedicated Server @ `192.168.3.6` | [Documentation](https://satisfactory.wiki.gg/wiki/Dedicated_servers)
7. Immich Server @ `192.168.3.7` | [Documentation](https://immich.app/docs/install/docker-compose/)
8. Zensical Documentation Server @ `192.168.3.8` | [Documentation](https://hub.docker.com/r/zensical/zensical)
9. FOG Project @ `192.168.3.9` | [Documentation](https://fogproject.org/)
10. Ansible AWX @ `192.168.3.10` | [Documentation](<../../deployments/automation/AWX/AWX Operator.md>)
11. Minecraft - All The Mods 9 @ `192.168.3.11` | [Documentation](https://www.curseforge.com/minecraft/modpacks/all-the-mods-9)
12. Windows DHCPS Server @ `192.168.3.12`
13. Windows DHCPS Server @ `192.168.3.13`
14. Minecraft - All The Mods 10 @ `192.168.3.14` | [Documentation](https://www.curseforge.com/minecraft/modpacks/all-the-mods-10)
15. Proxmox Mail Gateway @ `192.168.3.15` | [Documentation](https://example.com)
16. Not Currently In-Use @ `192.168.3.16` | [Documentation](https://example.com)
17. Traefik Reverse Proxy @ `192.168.3.17` | [Documentation](https://example.com)
18. Keycloak Server @ `192.168.3.18` | [Documentation](<../../deployments/Identity and Certificates/Keycloak/Deploy Keycloak.md>)
19. Docker Container Environment (Portainer) @ `192.168.3.19` | [Documentation](<../../deployments/Containers/Docker/Deploy Portainer.md>)
20. PrivacyIDEA @ `192.168.3.20` | [Documentation](<../../deployments/Identity and Certificates/Privacyidea.md>)
21. Puppet Server @ `192.168.3.21` | [Documentation](<../../deployments/automation/Puppet/Puppet.md>)
22. Not Currently In-Use @ `192.168.3.22` | [Documentation](https://example.com)
23. Hyper-V Failover Cluster @ `192.168.3.23` | [Documentation](<../../deployments/Virtualization and Storage/Hyper-V/Failover Cluster/Deploy Failover Cluster Node.md>)
24. TrueNAS SCALE @ `192.168.3.24` | [Documentation](https://www.truenas.com/truenas-scale/)
25. Primary Domain Controller @ `192.168.3.25` | [Documentation](https://example.com)
26. Secondary Domain Controller @ `192.168.3.26` | [Documentation](https://example.com)
27. Blue Iris Surveillance @ `192.168.3.27` | [Documentation](https://blueirissoftware.com/)
28. ARK: Survival Ascended Server @ `192.168.3.28` | [Documentation](<../../deployments/Applications/Gaming and Media/Ark Survival Ascended.md>)
29. Nextcloud AIO @ `192.168.3.29` | [Documentation](<../../deployments/Applications/Files and Collaboration/Nextcloud AIO.md>)
30. Dev-Testing Win11 Lab Environment @ `192.168.3.35` | [Documentation](https://example.com)
31. Windows 11 Work VM @ `192.168.3.31` | [Documentation](https://example.com)
32. Matrix Synapse HomeServer @ `192.168.3.32` | [Documentation](https://github.com/matrix-org/synapse)
33. ProxmoxVE Virtualization Node @ `192.168.3.33`
34. LAB-DRAAS-01 iLO IPMI Access Interface @ `192.168.3.34` | [Documentation](https://example.com)
35. Dev-Testing DC Lab Environment @ `192.168.3.35` | [Documentation](https://example.com)
36. Dev-Testing Win10 Lab Environment @ `192.168.3.35` | [Documentation](https://example.com)
37. Security Onion @ `192.168.3.37` | [Documentation](https://docs.securityonion.net/en/2.4/installation.html)
38. Wazuh SIEM Security VM @ `192.168.3.38` | [Documentation](https://documentation.wazuh.com/current/quickstart.html)
39. Rancher Harvester Hyper-Converged Infrastructure
40. Rancher Harvester Hyper-Converged Infrastructure - VIP Management Interface
41. Pterodactyl Dedicated Game Server Hosting Dashboard
42. NGINX Server Package Caching Server
43. NOT IN USE @ `192.168.3.43`
44. NOT IN USE @ `192.168.3.44`
45. NOT IN USE @ `192.168.3.45`
46. NOT IN USE @ `192.168.3.46`
47. NOT IN USE @ `192.168.3.47`
48. Portainer Docker Node
49. Windows File Server
50. Flyff VM 01
51. Semaphore UI Automation Server
52. Headless Laptop Server 01
53. Headless Laptop Server 02
54. Veeam Backup & Replication Server
55. Veeam Backup Worker
56. Veeam Backup Worker
57. Veeam Backup Worker
58. Immich Server @ `192.168.3.58` | [Documentation](https://immich.app/docs/install/docker-compose/)
59. Active Directory Root Certificate Services VM
60. Active Directory Intermediary Certificate Services VM
61. Mailcow Email Server
62. NOT IN USE @ `192.168.3.62`
63. Proxmox Datacenter Manager
64. H5ai File Sharing Server
65. Netbird VPN Server
66. Kasm Workspaces VM
67. Windows File Server
68. Proxmox Backup Server
69. ProxmoxVE Headless Laptop Virtualization Node
70. ProxmoxVE Headless Laptop Virtualization Node
71. ProxmoxVE Headless Laptop Virtualization Node
72. ProxmoxVE Headless Laptop Virtualization Node
73. ProxmoxVE Headless Laptop Virtualization Node
74. Rancher Harvester Node
75. Rancher Harvester Cluster VIP
251. Borealis Engine Node 02
252. Borealis Engine Node 01
253. Fedora Workstation 42 VM
254. Core Infrastructure Switch 01 (Zyxel GS1920-48)
## Related Documentation
- [Related Lab Map Documentation](<index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Network Address Plans/172.16.16.0 Sophos Network.md
+23
View File
@@ -0,0 +1,23 @@
---
tags:
- Sophos
- iptables
- Networking
---
## Purpose
Use this reference for 172.16.16.0 sophos network and the environment-specific values recorded below.
### IP Addresses
Documented IP addresses of Hyper-V Failover Cluster VMs that exist behind the Sophos XG Firewall VM. All of these machines are funneled through the Sophos XG Firewall VM before they are allowed to communicate on the physical network with other devices.
## 172.16.16.0/24 Network
| **IP Address** | **FQDN** | **Additional Notes** |
| :--- | :--- | :--- |
| 172.16.16.1 | LAB-SOPHOS-01.bunny-lab.io | Sophos XG Firewall |
| 172.16.16.2 | LAB-IRIS-01 | Blue Iris Surveillance |
| 172.16.16.3 | `NOT IN USE` | `NOT IN USE` |
| 172.16.16.4 | `NOT IN USE` | `NOT IN USE` |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Network Address Plans/192.168.5.0 Container Network.md
+77
View File
@@ -0,0 +1,77 @@
---
tags:
- Containers
- iptables
- Networking
---
## Purpose
Use this reference for 192.168.5.0 container network and the environment-specific values recorded below.
!!! info "Address Ownership"
Entries marked undocumented or unknown remain unresolved. Deployment examples elsewhere describe some of the same addresses, but they do not establish current ownership. Confirm the running service before updating this plan.
### IP Addresses
Documented IP addresses of containers.
## 192.168.5.0/24 Network
| **IP Address** | **Hostname** | **Additional Notes** |
| :--- | :--- | :--- |
| 192.168.5.1 | PFSENSE | pfSense Firewall |
| 192.168.5.2 | AUTH.bunny-lab.io | Keycloak Server |
| 192.168.5.3 | AUTH.bunny-lab.io | Keycloak PostgreSQL DB Server |
| 192.168.5.4 | ALPINE-WORK-01.bunny-lab.io | Firefox Containerized Environment |
| 192.168.5.5 | ACTUAL.bunny-lab.io | Actual Finance Server |
| 192.168.5.6 | Monica | Server |
| 192.168.5.7 | Monica | Database |
| 192.168.5.8 | Gatus | Server |
| 192.168.5.9 | Gatus | Database |
| 192.168.5.10 | `UNDOCUMENTED - Active` | |
| 192.168.5.11 | NOTES.bunny-lab.io | Trillium Notes |
| 192.168.5.12 | `UNDOCUMENTED - Active` | |
| 192.168.5.13 | LAB-CLOUD-02 | Docker Proxy |
| 192.168.5.14 | `UNDOCUMENTED - Active` | |
| 192.168.5.15 | `UNDOCUMENTED - Active` | |
| 192.168.5.16 | `UNDOCUMENTED - Active` | |
| 192.168.5.17 | `UNDOCUMENTED - Active` | |
| 192.168.5.18 | `UNDOCUMENTED - Active` | |
| 192.168.5.19 | Immich | Server |
| 192.168.5.20 | Immich | Microservices |
| 192.168.5.21 | Immich | Machine Learning |
| 192.168.5.22 | Immich | Redis DB |
| 192.168.5.23 | Immich | PostgreSQL DB |
| 192.168.5.24 | Sanctuary | Content Database Server |
| 192.168.5.25 | Homebox | Inventory Management System |
| 192.168.5.26 | Material MkDocs | Voice Training Documentation |
| 192.168.5.27 | MM.bunny-lab.io | Mattermost PostgreSQL DB |
| 192.168.5.28 | MM.bunny-lab.io | Mattermost Server |
| 192.168.5.29 | `UNDOCUMENTED - Active` | |
| 192.168.5.30 | Pyload | Python-Based Download Manager |
| 192.168.5.31 | FLATNOTES.bunny-lab.io | Note-Taking Server |
| 192.168.5.32 | SEMAPHORE.bunny-lab.io | Ansible Semaphore |
| 192.168.5.33 | SEMAPHORE.bunny-lab.io | Ansible Semaphore PostgreSQL Database |
| 192.168.5.34 | CONTACT.bunny-lab.io | Linkstack |
| 192.168.5.35 | BIFROST.bunny-lab.io | Rustdesk HBBS |
| 192.168.5.36 | FLYFF.bunny-lab.io | Material MKDocs |
| 192.168.5.37 | traggo.bunny-lab.io | Traggo Time-Management Server |
| 192.168.5.38 | speedtest.bunny-lab.io | Speedtest Tracker |
| 192.168.5.39 | speedtest.bunny-lab.io | Speedtest Tracker Database |
| 192.168.5.40 | apprise.bunny-lab.io | Apprise Notification Relaying Service |
| 192.168.5.41 | joplin.bunny-lab.io | Joplin Documentation |
| 192.168.5.42 | todo.bunny-lab.io | Tududi Server |
| 192.168.5.43 | `UNDOCUMENTED - Active` | |
| 192.168.5.44 | `UNDOCUMENTED - Active` | |
| 192.168.5.45 | `UNDOCUMENTED - Active` | |
| 192.168.5.46 | kb.bunny-lab.io | Zensical Documentation Server |
| 192.168.5.47 | help.bunny-lab.io | Rustdesk Info Page |
| 192.168.5.48 | borealis.bunny-lab.io | NGINX Webserver |
| 192.168.5.49 | `UNDOCUMENTED - Active` | |
| 192.168.5.50 | Pathfinder Server | |
| 192.168.5.51 | Pathfinder MariaDB | |
| 192.168.5.52 | Pathfinder Redis | |
| 192.168.5.53 | Kavita Server | |
| 192.168.3.54 | `UNDOCUMENTED - Active` | |
| 192.168.3.55 | Linkding Server | |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Power/APC Battery Cell Wiring.md
+51
View File
@@ -0,0 +1,51 @@
---
tags:
- UPS
- APC
- Power
---
## Purpose
When an APC battery backup's battery dies, you can manually replace the cells and 'refurbish' the battery. The following diagram is how you rewire the cells.
!!! warning "Work in Progress"
This document is still being written
## Wiring Diagram
```mermaid
graph TB
%% Define cells and connections
Cell1["Cell 1<br>Black (Negative) to Black (Negative)"] -.-> AndersonNeg["Anderson Connector Negative<br>(Black)"]
Cell1 -->|"Red (Positive) to Black (Negative)"| Cell2["Cell 2<br>Red (Positive) to Black (Negative)"]
Cell2 -->|"Red (Positive) to Black (Negative)"| Cell3["Cell 3<br>Red (Positive) to Black (Negative)"]
Cell3 -->|"Red (Positive) to Fuse"| Fuse["30A Fuse"]
Fuse -->|"Red (Positive) to Black (Negative)"| Cell4["Cell 4<br>Red (Positive) to Black (Negative)"]
Cell4 -->|"Red (Positive) to Anderson Connector Positive"| AndersonPos["Anderson Connector Positive<br>(Red)"]
%% Define styles
classDef battery fill:#f2f2f2,stroke:#000,stroke-width:2px;
class Cell1,Cell2,Cell3,Cell4 battery;
classDef fuse fill:#ffcc00,stroke:#000,stroke-width:2px;
class Fuse fuse;
classDef anderson fill:#00ccff,stroke:#000,stroke-width:2px;
class AndersonPos,AndersonNeg anderson;
classDef positive fill:#ff0000,stroke:#000,stroke-width:2px;
class AndersonPos positive;
classDef negative fill:#000000,stroke:#fff,stroke-width:2px;
class AndersonNeg negative;
%% Define line colors for clarity
linkStyle 0 stroke:#000,stroke-width:2px;
linkStyle 1 stroke:#ff0000,stroke-width:2px;
linkStyle 2 stroke:#ff0000,stroke-width:2px;
linkStyle 3 stroke:#ff0000,stroke-width:2px;
linkStyle 4 stroke:#ff0000,stroke-width:2px;
linkStyle 5 stroke:#ff0000,stroke-width:2px;
```
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/Power/UPS Power Distribution.md
+19
View File
@@ -0,0 +1,19 @@
---
tags:
- UPS
- Backup
- Power
---
## Purpose
Record the devices connected to each lab UPS, their estimated runtime, and their shutdown thresholds. Use this reference when planning maintenance or checking power dependencies.
| **Battery Backup** | **Status** | **Connected Device(s)** | **Estimated Runtime** | **Shutdown Threshold** | **UPS Web Management** |
| :--- | :--- | :--- | :--- | :--- | :---: |
| Outer-Left `#1` | ![](https://status.bunny-lab.io/api/v1/endpoints/battery-backups_outer-left-1-(virt-node-01--10-port-10gbe-network-switch--pfsense-firewall)/uptimes/7d/badge.svg) | - VIRT-NODE-01<br>- 10-Port 10GbE Network Switch<br>- pfSense Firewall | 10 Minutes | 3 Minutes Remaining | [:fontawesome-solid-car-battery: Manage](http://192.168.3.4:3052){ .md-button } |
| Inner-Left `#2` | ![](https://status.bunny-lab.io/api/v1/endpoints/battery-backups_inner-left-2-(bunny-node-02--24-port-1gbe-network-switch)/uptimes/7d/badge.svg) | - BUNNY-NODE-02<br>- 24-Port 1GbE Network Switch | 12 Minutes | 3 Minutes Remaining | [:fontawesome-solid-car-battery: Manage](http://192.168.3.5:3052){ .md-button } |
| Inner-Right `#3` | ![](https://status.bunny-lab.io/api/v1/endpoints/battery-backups_inner-right-3-(moon-storage-01--wireless-ap)/uptimes/7d/badge.svg) | - MOON-STORAGE-01<br>- Wireless AP | 16 Minutes | 3 Minutes Remaining | [:fontawesome-solid-car-battery: Manage](http://192.168.3.3:3052){ .md-button } |
| Outer-Right `#4` | ![](https://status.bunny-lab.io/api/v1/endpoints/battery-backups_outer-right-4-(lab-draas-01--lab-pool-01--8-port-1gbe-network-switch--internet-modem--poe-surveillance-cameras)/uptimes/7d/badge.svg) | - LAB-DRAAS-01<br>- LAB-POOL-01<br>- 8-Port 1GbE Network Switch<br>- Internet Modem<br>- PoE Surveillance Cameras | 13 Minutes | 3 Minutes Remaining | [:fontawesome-solid-car-battery: Manage](http://192.168.3.33:3052){ .md-button } |
## Related Documentation
- [Related Lab Map Documentation](<../index.md>) — Find the connected deployments, procedures, and references for this subject.
reference/Lab Map/index.md
+23
View File
@@ -0,0 +1,23 @@
---
tags:
- Lab Map
- Reference
- Documentation
---
# Lab Map
## Purpose
Identify where a workload runs, which address plan describes it, and which hardware or power reference applies before following a deployment or repair procedure.
## Includes
- Find recorded host addresses, inventory groups, and service roles.
- Match container addresses to the services recorded for that subnet.
- Check the separate Sophos network before using its VPN procedures.
## Find the Right Document
- [Server Inventory](<Homelab Server Inventory.md>) — Find recorded host addresses, inventory groups, and service roles.
- [Container Address Plan](<Network Address Plans/192.168.5.0 Container Network.md>) — Match container addresses to the services recorded for that subnet.
- [Sophos Address Plan](<Network Address Plans/172.16.16.0 Sophos Network.md>) — Check the separate Sophos network before using its VPN procedures.
- [UPS Power Distribution](<Power/UPS Power Distribution.md>) — Identify the recorded devices, runtimes, and shutdown thresholds for each UPS.
- [Storage Node 01 Disk Layout](<Hardware/Storage Node 01 TrueNAS Core Disk Layout.md>) — Identify the physical drive before following the drive-replacement workflow.
- [Replace a TrueNAS Drive](<../../workflows/Virtualization and Storage/TrueNAS/Replace a Drive in Storage Node 01.md>) — Use the physical disk inventory during replacement and update it afterward.