Skip to main content
Cisco Meraki

IPv6 Support on MX Security & SD-WAN Platforms - Monitoring and Reporting

Monitoring and Reporting 

IPv6 Prefix tab

Is a single place to simply view all of the IPv6 Prefixes on an MX.  This tab will provide you information regarding Manually configured prefixes (If any), Delegated prefixes from your IPv6 enabled ISPs and which prefixes are assigned to which IPv6 enabled VLANs.

It also provides additional information such as how many prefixes are assigned and available from larger prefix blocks and prefix expiration status.

You can access this tab from the Security & SD-WAN > Appliance status page

Ping

The MX can perform pings to both IPv4 and IPv6 addresses. The type of ping will be determined based on the address given. If a hostname is given, the MX will default to an IPv4 ping unless the hostname resolves to an IPv6 address only.

Example of an IPv4 hostname resolution

Example of an IPv6 hostname resolution

In addition, the source of a ping can be specified using the Source IP Address dropdown menu. This menu auto-populates based on the available interfaces, and will often include “Default”, “Internet” or “Internet 1/2”, and “VLAN 0” or “VLAN 1/2/3…”. The selected source will not change whether a ping is IPv4 or IPv6, as the actual source IP gets set based on the interface and the IP type of the destination. 

Example of populated Source IP Address menu

Traceroute

The MX supports IPv4 and IPv6 trace routes for troubleshooting purposes.  You may use an IPv4, IPv6 or a domain name to perform trace routes.  If the DNS record for the domain name contains both IPv4 and IPv6 records a trace route is initiated for both.  If it only contains IPv4 or IPv6 records, then the appropriate one will be performed and the other will not yield any results.

Example of a Dual Stack name Record

Example where the name record only contains IPv4

DNS Lookup

The DNS lookup tool makes use of the drill utility on an MX. If IPv6 is enabled in the network, the MX will perform a drill lookup for both A and AAAA records, then display them together. The tool is used this way regardless of the destination (IPv4, IPv6, or hostname) or the DNS server address type. 

Example of a Dual Stack Record

Example of IPv4 only Record

Route Table

There are several options for configuring IPv6 Prefixes supported by the MX.  In this section, we will cover the different options available, how to configure them, and how to view available prefixes.

Note:

  • Currently only IPv6 Local VLANs and Static routes are visible on the table.

  • Currently IPv6 AutoVPN routes are missing, but will be added in the future.

AutoVPN Participants table

The VPN Participants table was a view only table located in the Site-to-site VPN page; which contained all of the VPN configured Peer and Subnet/Prefix information.  This table is being deprecated and a new table has been added in the VPN Status page.

You can now Filter, Sort and Search the table allowing you to quickly and easily locate the information you need.

Client Tracking

To view statistics for a particular client, Navigate to Network-wide > Monitor > Clients. Click on the client to open the Client Details page. This page features information about the applications, ports, and content viewed by a particular client. When Hostname Visibility has been enabled, you can view the specific destinations visited by clients. This is shown in the image below. You can see statistics about the specific applications used, transport protocol information, destination hostname or IP address, usage data, amount of traffic sent and received, and number of flows:

Event Log

Duplicate Address Detection (DAD)

DAD events help recognize duplicate address alerts and can be filtered with the following event type:

Addressing/VLAN updates

Prefix starvation

  • Was this article helpful?