| Location | Project | Environment | Tier | VM Name | IP | OS | Cluster | vCPU | Mem (GiB) | VM HA | Cluster HA | Actions |
|---|
| Project | Detail (application / database) | Owner | VM Count | Actions |
|---|
Firewalls, switches, routers, load balancers… A branch is a
Location. Type a location by name or code — the same name always maps to the
same location. To add many at once, use bulk-add-network.sh with a CSV.
| Name | Management IP | Data IP | Type | Environment | HA Status | HA Name | Location | Actions |
|---|
Pick which applications show inside the Nutanix Cluster box (none ticked = show all). Nutanix clusters are detected from the VM data — add any extra cluster for a site here. Admin only.
Each Nutanix node is 1U. Nodes fill upward from the start rack unit and overflow to the next rack when the rack is full (42U).
Format: VM-NAME[=IP[=CLUSTER]] —
e.g. RT-P-GIS-APP-03=10.10.5.13=RT-TPVT-C02.
Location, environment, project and tier are decoded from the name.
For old VMs whose names don't follow the
LOC-ENV-PROJECT-TIER-NUM standard: enter the name as-is
and fill in the details manually. The VM joins HA evaluation like any other.
VMs submitted by Prism Central or manual add that are missing a required detail (project not in Settings, missing/duplicate IP, unknown cluster, etc.). Fill in the missing fields, then Promote. They stay here until every requirement is met.
| VM Name | IP | OS | Cluster | vCPU | Mem | Project | Loc | Env | Tier | Source | Issues | Actions |
|---|
| Username | Role | Created | Actions |
|---|
Code + default name. A project can override the name below (so the same code can differ per project).
Owner, description, purpose and notes shown in the popup when a VM is clicked.
Per project + tier: the tier's full name (can differ per project) and the shared HA endpoints common to the tier's VMs. DB tier → Windows FC IP + SQL Listener IP; App tier → F5 VIP + DNS.
Build the traffic flow for a project: connect tiers in order (LB/VIP → FE → BE → APP → DB). VIP/DNS + listener come from the tier's HA values above. Cross-project links can start from any project (use a middle project as a shared broker), and any tier can face the Internet. Multiple flows = separate diagrams.
Middle project: to route proj1→proj2 through a shared broker in proj3, add two links — proj1 tier → proj3 tier and proj3 tier → proj2 tier.
Pick a project to load its application flow segments (WEB→APP, APP→DB…). For each segment, insert the network devices it passes through (shown by HA name), and add users / internet at the edges. Users appear on the right; DMZ devices show red, DC purple. View in Executive → a project → the Network tab.
One global map of how the network devices are physically wired — e.g. Perimeter FW → DMZ Switch, F5 → Internet, Local Users → Core Switch. Devices are listed by HA name (an HA pair / stack appears once). Add the link IP address if that connection has one. Internet and users are available as endpoints.
Upload the official vendor icon (SVG/PNG) and give a keyword
that appears in the device Type — e.g. keyword palo matches
"Palo Alto Perimeter Firewall". Matching devices then show that vendor's own artwork
in the Infrastructure view. Max 96 KB per icon.
1. F5 path — the ordered device chain F5 traffic traverses, from the F5 in the DMZ back to the DC. Set it once. 2. Per project — pick a project, then tick the tiers that have F5 connectivity. Those tiers auto-route through the path above in that project's Executive → Network view.
How each branch reaches HQ — e.g. Riyadh → Tabuk over VPN, with the branch firewall public IP and the Riyadh firewall public IP. Shown on the Infrastructure view and in the branch drill-down.
HA set to Yes/No/NA is a manual override; "Auto" recomputes it from the VM name.