GestioIP

Search for GestioIP in the Marketplace, select the SecureAnyCloud publisher, and select Create. Choose Standard_B2s or larger. Configure the NSG to allow TCP 80 for the web UI from your administrative networks (or from the internet, if you intend the IPAM console to be broadly reachable) and TCP 22 for administration. MariaDB stays on loopback and is never exposed.

RG="gestioip-prod"; LOCATION="eastus"; VM_NAME="gestioip-01" IMAGE_URN="sac1647283583153:gestioip:default:latest" SSH_KEY="$(cat ~/.ssh/id_rsa.pub)" az group create --name "$RG" --location "$LOCATION" az network vnet create -g "$RG" --name gestioip-vnet --address-prefix 10.92.0.0/16 --subnet-name gestioip-subnet --subnet-prefix 10.92.1.0/24 az network nsg create -g "$RG" --name gestioip-nsg az network nsg rule create -g "$RG" --nsg-name gestioip-nsg --name allow-ssh --priority 100 \
  --source-address-prefixes "<your-mgmt-cidr>" --destination-port-ranges 22 --access Allow --protocol Tcp az network nsg rule create -g "$RG" --nsg-name gestioip-nsg --name allow-http --priority 110 \
  --source-address-prefixes "<your-mgmt-cidr>" --destination-port-ranges 80 --access Allow --protocol Tcp
# Accept the Marketplace terms once per subscription (required before the first CLI deploy)
az vm image terms accept --urn sac1647283583153:gestioip:default:latest
az vm create -g "$RG" --name "$VM_NAME" --image "$IMAGE_URN" \
  --size Standard_B2s --storage-sku StandardSSD_LRS \
  --admin-username azureuser --ssh-key-values "$SSH_KEY" \
  --vnet-name gestioip-vnet --subnet gestioip-subnet --nsg gestioip-nsg --public-ip-sku Standard

On first boot, the image builds the GestioIP database schema, generates this VM's database password and administrator password, rotates both into place, permanently removes the installation wizard, opens the bootstrap gate and starts Apache. It then verifies that the new administrator password works and that common defaults are rejected. This completes within well under a minute. Connect over SSH as azureuser and read the details:

sudo cat /root/gestioip-credentials.txt

The file is mode 0600 and owned by root, so only a privileged user can read it. It contains the site URL, the administrator username and password, and the database name, user and password.

Both services should report active. ss confirms the site is on port 80 while MariaDB is bound to loopback only, and the GPL-3.0 licence text ships in the image.

systemctl is-active apache2.service mariadb.service ss -tln 2>/dev/null | grep -E ':(80|3306) ' head -3 /usr/share/doc/gestioip/LICENCE

You can verify the same login from the command line. The following command performs a real login through the form with the per-VM password, confirms that the authenticated network overview renders, and then confirms that every common default credential is rejected through the same flow:

sudo /usr/local/sbin/gestioip-roundtrip.sh

Browse to http://<your-vm-public-ip>/gestioip/ to see the GestioIP sign-in page.

Sign in with the username gipadmin and the password from the credentials file. Once signed in you land on the network overview. A fresh instance shows no networks until you add or discover your first one.

Select new in the top navigation to open the "create new networks" form. Enter the network address and prefix length, a description, and choose a Site and category (both required). A fresh instance ships with the seeded values Default Site and LAN from setup. You can rename or extend them later undermanage >sites and categories.

Select add. The network is now stored in the inventory and appears immediately in the authenticated network overview. This is the core of what GestioIP does: it turns a form submission into a live, searchable IP address record.

You can confirm the same thing from the command line by counting the rows GestioIP's own schema now holds:

mysql -N -B -e "SELECT red, BM, descr FROM gestioip.net"

GestioIP's signature feature is building your inventory automatically from your real network devices via SNMP, rather than typing every subnet in by hand. Open import/export >import networks via SNMP query to configure a discovery run.

Enter the IP address of a router or switch that has SNMP enabled and reachable from this VM, and its SNMP community string (SNMPv1/v2c) or SNMPv3 credentials, then start the query. GestioIP walks the device's routing/ARP tables and offers the networks and hosts it finds for import into your inventory. Repeat against your core routers to build a complete picture of your network, and use Jobs in the navigation to schedule discovery to run automatically so the inventory stays current without manual re-entry.

Under manage >sites and categories you can add locations beyond the seeded "Default Site" and categories beyond "LAN". This is useful once you organise networks by physical site, device role, or client. manage >Users lets you review the internal GestioIP user/role model (distinct from the single Apache-level login this guide covers) if you want finer-grained access control for a team. manage >manage GestioIP holds the global application settings, including enabling authentication features and DNS/dynamic-update integration.

The entire inventory lives in the gestioip MariaDB database. Take a logical backup with mysqldump on a schedule appropriate for your change rate:

sudo mysqldump gestioip > "gestioip-backup-$(date +%Y%m%d).sql"

Store the dump off the VM (Azure Blob Storage, another host, or your existing backup pipeline). To restore, recreate an empty gestioip database and mysql gestioip < gestioip-backup-<date>.sql.

The image ships HTTP only. If you point a domain at this VM, add TLS with your own certificate (or Let's Encrypt via certbot --apache) and update GestioIP's Apache virtual host to redirect HTTP to HTTPS. Keep the existing AuthUserFile, AuthGroupFile and SessionCryptoPassphrase directives in /etc/apache2/conf-enabled/gestioip.conf unchanged when you edit the vhost. They are what the per-VM login depends on.

From the GestioIP UI, open manage >manage GestioIP to review application-level settings, or rotate the Apache-level login password directly:

sudo htpasswd /usr/share/gestioip/etc/apache/users-gestioip gipadmin

You will be prompted for a new password interactively. The change takes effect immediately. No service restart is required, because the AuthUserFile is read per request.