Hey everyone!

I've been playing with IT for a long time, can't ever say I'm a professional of any sort but I do find myself enthusiastic about it. I started long ago with a cheap Google Search Appliance (Poweredge 2950) under my couch and just kept acquiring parts since then and eventually stuck it all into a rack.

XCP-NG has been a part of that journey for a long time and currently trying to practice diagram creation. I figured I'd started with a full summary reference diagram and break it down from there, but let me know how it looks! Either my diagram or the architecture itself!

This diagram includes 6 sections broken down into:

Home Logical Topology
Home Physical Topology (simple)
Colo (Virginia)
Hardware setup template
Home network equipment summary
Networking and VLANs

The diagrams cover my home architecture, and my off-site locations in a colo connected via S2S VPN.

Appreciate it everyone!

Appreciate the assistance on it all. This is only a homelab turned private cloud setup, but XCP-NG has been a pleasure to work with, thanks for all you and the team do!

So I'm not 100% but I've resolved the symptom.

I have 3 VLANS involved

DATA - Endpoints
PRIV - Reverse proxy manager exists here
MGMT - Where XOA exists.

Myself and users access XOA via the reverse proxy, which access the webserver in the MGMT vlan.

My hosts had their primary management access on the DATA vlan, a holdover setup from prior, and a secondary management access on the MGMT VLAN and a third for data migrations.

XOA was connected to the MGMT IPs of each host.

Watching packet capture I see packets moving from the originating endpoint in DATA, to the reverse proxy, from it to the XOA backend server. Then suddenly I see XOA in the MGMT VLAN try to access the hosts directly in the DATA VLAN which was blocked.

Problem is, it seemed to send packets meant to originate from the MGMT-VLAN as sourced from the DATA-VLAN.

The resolution was I just removed the secondary management IP and switched the primary management of each host to the MGMT-VLAN alongside XOA.

They're happier now at least.

@Greg_E Netbox does an amazing job and helps you make connections. I do have one setup but not listed here, however I don't have it fully operational at this moment. Been running some devs on a true one pane of glass solution such as Grafana or alternatives and how it feeds in. Haven't quite settled on anything though.

For the diagram above, generally I'll start off with the physical topology and I'll make a list of the hops it would take to get somewhere on the network until I reach an ending point, usually the longest route first. Then just create the basic flowchart, create my branches as necessary.

The format of the diagram is made up of the container shapes in either horizontal or vertical title, and I change the colors. I try to start with warmer or neutral colors at the background container and cooler colors in the foreground. Something I learned during early days of HTML/CSS.

The icon packs I used were Cisco, but had overlap from Rack, CAE and Citrix icon packs

@olivierlambert I appreciate that! You guys have been foundational in my learning experience with XCP-NG at the core. I'm essentially opensource style or BSD licensing in my setup and I've found everything you all do to be well documented and performance is outstanding from what I can push.

It helps to know this is a good representation! This was the hopeful start to creating more diagrams and trying to setup deep dives of each section; delving into abstraction layers and displaying on a personal website as a type of portfolio addition to a resume. Got caught up in layoffs recently, so as the search goes I've tried to improve and refine what I do have on hand.

It's not the most modern of hardware as It's really been a long process, but I've tried to eek out as much performance and variety as I could. Always learning, sometime brutally lol.

As I create more, I keep going back and updating this one.

@trobertson

Couldn't help myself, noticed a few errors and thought of a few items to throw in the diagram lol.

I appreciate that! I used draw.io to create this and although I've made quite a few diagrams as a prior teacher, I don't quite know any standards so I do my best to present it as built.

I've tried GLPI before and I did enjoy it, I also used Snipe-IT alongside a Dymo label printer to great success. I didn't quite keep up on that documentation sadly and most of my equipment details/warranty now fall under Grocy as I'm in that program more than others.

I tend to browse through the Awesome opensource Self-hosted list and see what I can put together and how I can improve. I do use a lot of this in my house, and contains my router now so I'm outta luck if it goes down lol.

Hey everyone!

I've been playing with IT for a long time, can't ever say I'm a professional of any sort but I do find myself enthusiastic about it. I started long ago with a cheap Google Search Appliance (Poweredge 2950) under my couch and just kept acquiring parts since then and eventually stuck it all into a rack.

XCP-NG has been a part of that journey for a long time and currently trying to practice diagram creation. I figured I'd started with a full summary reference diagram and break it down from there, but let me know how it looks! Either my diagram or the architecture itself!

This diagram includes 6 sections broken down into:

Home Logical Topology
Home Physical Topology (simple)
Colo (Virginia)
Hardware setup template
Home network equipment summary
Networking and VLANs

The diagrams cover my home architecture, and my off-site locations in a colo connected via S2S VPN.

Appreciate it everyone!

Appreciate the assistance on it all. This is only a homelab turned private cloud setup, but XCP-NG has been a pleasure to work with, thanks for all you and the team do!

So I'm not 100% but I've resolved the symptom.

I have 3 VLANS involved

DATA - Endpoints
PRIV - Reverse proxy manager exists here
MGMT - Where XOA exists.

Myself and users access XOA via the reverse proxy, which access the webserver in the MGMT vlan.

My hosts had their primary management access on the DATA vlan, a holdover setup from prior, and a secondary management access on the MGMT VLAN and a third for data migrations.

XOA was connected to the MGMT IPs of each host.

Watching packet capture I see packets moving from the originating endpoint in DATA, to the reverse proxy, from it to the XOA backend server. Then suddenly I see XOA in the MGMT VLAN try to access the hosts directly in the DATA VLAN which was blocked.

Problem is, it seemed to send packets meant to originate from the MGMT-VLAN as sourced from the DATA-VLAN.

The resolution was I just removed the secondary management IP and switched the primary management of each host to the MGMT-VLAN alongside XOA.

They're happier now at least.

Well that did help me to find something I did not notice before! An oddity in which I see the XO webserver traffic between itself and the host is routing oddly over my networking, will try to trace down as to why.

The short and sweet is I see the XO TCP calls come across the wrong interface in routing to the Host at 443, since the traffic isn't expected in this direction it has no stateful tracking and it's denied. This doesn't seem to impact anything else except the console streams and likely a misconfiguration in my host setup I'm assuming.

Appreciate the help!

Ah, I see now. I was adding it to the wrong location of the URL. I did load it up and it did freeze

Currently I have the same VM up in all 3 consoles (XO, XOv6, XO Lite)

XO and XOv6 both froze at differing times
XO lite is still going.

I've tried having XO and the host servers on the same VLAN, both tagged and untagged. I don't see any packet drops between them in monitoring.

Ah apologies, looking at other comments, I am built from Source without a license atm. I don't believe I get the preview