Beta Release: IPv6 Monitoring Support
We’re excited to announce our beta release of IPv6 monitoring this past week. With ARIN recently anouncing the depletion of all remaining IPv4 addresses, we’ve received a large volume of requests from customers running servers and devices on IPv6 capable networks. Fundamentally, our IPv6 features are no different than existing IPv4 monitoring.
IPv6, which is 20+ years in the making, has a number of novel improvements over IPv4
- A substantially larger address pool relative to IPv4 thanks to its larger address size (128-bit vs. 32-bit).
- The removed dependency on NAT, thanks to the aforementioned address pool
- More efficiency for routers, as the larger header size of IPv6 packet reduces the work required from routers
How IPv6 monitoring fits in at Panopta
Panopta currently has the ability monitor 39 different network services, ranging from simple ICMP ping checks to more complex synthetic application checks. Our IPv6 support covers 38 of the existing network service checks, the one exception being OWA, which we’re still working on.
Users have two options for configuring IPv6 checks:
Option 1 – Hostname: When creating/editing a server, provide a FQDN which has IPv6 records attached to it. When configuring a network service check, select the FQDN annotated with [v6] – we’ll autodiscover these you for. When we perform the check on this FQDN, our check will resolve to an IPv6 address.
Option 2 – IP Address: When creating/editing a server, provide an IPv6 address much like you would an IPv4 address. You’ll then be able to create network service checks utilizing this address.
We’re rolling out our IPv6 support in two phases:
Phase 1: Beta users (email us to join!) can add IPv6 FQDN’s/addresses to any existing server (see guide below).
Phase 2: Users can add IPv6 FQDN’s/addresses via the new server wizard or to any existing server. As well, users can add IPv6 checks via our API.
Each of the features you currently enjoy are fully IPv6 enabled as well – dashboard, reporting, notifications, and more.
You can also expect to see automated tagging for quicker segmenting of IPv6 vs. IPv4 devices in reporting, dashboards, etc. in the not too distant future.
1. Select the Edit Server button
2. If you’re monitoring the server via FQDN, just hit save. We’ll automatically detect the available IPv6 addresses associated with the FQDN and add them to the server.
3. If you’re monitoring the server via IP, you can add IPv6 addresses in the “Additional IP addresses or..” input.
4. After you’ve completed step 2 or 3, your IPv6 address will now be present in your server details module. You’ll notice we also add an IPv6 FQDN as well if we’re able to detect one.
5. To add a Network Service check using the address, you will create it as you normally; be sure that you select the newly added address from the Server FQDN dropdown.
6. Select a monitoring location that is IPv6 compliant. They’re the only ones that are selectable.
7. You are now monitoring IPv6 resources!
Our transition to IPv6
In an upcoming post, our head of DevOps Cory Pulm will detail Panopta’s internal journey to supporting IPv6. Stay tuned!