Diagnostic Interface (Legacy)

For new devices using 7.2 and later, you cannot use the legacy Diagnostic interface. Only the merged Management interface is available.

If you upgraded to 7.2 or later, and you did not have any configuration for the Diagnostic interface, then the interfaces will merge automatically.

If you upgraded to 7.2 or later, and you have configuration for the Diagnostic interface, then you have the choice to merge the interfaces manually, or you can continue to use the separate Diagnostic interface. Note that support for the Diagnostic interface will be removed in a later release, so you should plan to merge the interfaces as soon as possible. To manually merge the Management and Diagnostic interfaces, see Merge the Management and Diagnostic Interfaces. Configurations that prevent an automatic merge include the following:

• A data interface named "management"—This name is reserved for use with the merged Management interface.

• IP Address on Diagnostic

• DNS enabled on Diagnostic

• Syslog, SNMP, RADIUS or AD (for remote access VPN) source interface is Diagnostic

• RADIUS or AD (for remote access VPN) with no source interface specified, and there is at least one interface configured as management-only (including Diagnostic)—The default route lookup for these services has changed from the management-only routing table to the data routing table, with no fallback to management. Therefore, you cannot use a management-only interface other than Management.

• Static routes on Diagnostic

• Dynamic routing on Diagnostic

• HTTP server on Diagnostic

• ICMP on Diagnostic

• DDNS for Diagnostic

• FlexConfig using Diagnostic

For more information about how the legacy Diagnostic interface operates, see the 7.1 version of this guide.