Skip to main content
Sakakura
New Member
December 11, 2025
Question

Questions About FortiADC 7.6.4 CLI Commands

  • December 11, 2025
  • 5 replies
  • 672 views

Hi everyone,
I’m working with FortiADC 7.6.4 and would like to ask about a couple of CLI commands. If anyone has information, I’d appreciate your help.

 

1. Checking interface link status
    Is there a CLI command that shows the actual link status of an interface?
    According to the documentation, the command
    "get system interface"
    only provides the enabled/disabled status, so I understand it does not show the real-time link state.

 

    I also looked at the following command:

    "diagnose hardware get deviceinfo nic-detail"
    which appears to offer detailed NIC information, but it does not show the link status for aggregated (LAG) interfaces.

 

2. Deleting backup configuration files
    I know that configuration backups can be created using:
    "execute restore config disk <name>"
    However, I haven’t been able to find a CLI command that deletes configuration backup files stored on disk.
    Is there a way to remove these backup files through the CLI?

 

Thanks in advance for your support!

5 replies

AEK
SuperUser
SuperUser
December 11, 2025

Hi Sakakura

 

1. Does this command help?

diagnose netlink interface list agg1

 

2. Command not found :(

AEK
Sakakura
SakakuraAuthor
New Member
December 11, 2025

AEK, thanks for your reply.


For some reason, the command you suggested only returns a blank line with no output.


The output looks something like this:

FortiADC #  FortiADC # diagnose netlink interface list lag01   FortiADC #  FortiADC #  FortiADC # diagnose netlink interface list port1   FortiADC #

 

funkylicious
SuperUser
SuperUser
December 12, 2025

https://docs.fortinet.com/document/fortiadc/7.6.4/cli-reference/188513

try doing a ? after interface in order for the system to give you all the options and then select one. according to the link it should work/display the state/flag.

"jack of all trades, master of none"
AEK
SuperUser
SuperUser
December 13, 2025

Probably you discovered a new issue, since there is no known issue on 7.6.4 so far.

https://docs.fortinet.com/document/fortiadc/7.6.4/release-notes/454516/known-issues

AEK
AEK
SuperUser
SuperUser
December 13, 2025

I tested on a FAD 7.6.4 VM (on KVM).

The command seem to work as expected.

Here I have agg1 made of port2 (up) and port3 (down).

We can see the status is displayed correctly as "run" (in blue) when the interface is plugged.

fad01 # diagnose netlink interface list port2
if=port2 family=00 type=1 index=5 mtu=1500 link=0 master=13
flags=up broadcast run slave multicast
Qdisc=pfifo_fast hw_addr=52:54:00:3f:b3:fb: broadcast_addr=ff:ff:ff:ff:ff:ff:
stat: rxp=99 txp=24 rxb=7730 txb=2424 rxe=0 txe=0 rxd=0 txd=0 mc=0 collision=0
re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0
te: txa=0 txc=0 txfi=0 txh=0 txw=0


fad01 # diagnose netlink interface list port3
if=port3 family=00 type=1 index=6 mtu=1500 link=0 master=13
flags=up broadcast slave multicast
Qdisc=pfifo_fast hw_addr=52:54:00:3f:b3:fb: broadcast_addr=ff:ff:ff:ff:ff:ff:
stat: rxp=0 txp=0 rxb=0 txb=0 rxe=0 txe=0 rxd=0 txd=0 mc=0 collision=0
re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0
te: txa=0 txc=0 txfi=0 txh=0 txw=0


fad01 # diagnose netlink interface list agg1
if=agg1 family=00 type=1 index=13 mtu=1500 link=0 master=0
flags=up broadcast run master multicast vlan_id=4 vlan_flag=
Qdisc=noqueue hw_addr=52:54:00:3f:b3:fb: broadcast_addr=ff:ff:ff:ff:ff:ff:
stat: rxp=68 txp=22 rxb=3874 txb=2298 rxe=0 txe=0 rxd=0 txd=0 mc=0 collision=0
re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0
te: txa=0 txc=0 txfi=0 txh=0 txw=0

As it works fine on the VM then probably the bug is related to the hardware appliance.

Try open a ticked.

 
AEK
New Member
June 10, 2026

Thanks for raising these questions. The interface link status for LAG interfaces can definitely be tricky to verify through CLI alone

New Member
June 10, 2026

Interesting discussion. I've also seen limitations when checking real-time link status on aggregated interfaces. 69live apk Hopefully someone from the Fortinet community can clarify the best approach for both link-state verification and backup file deletion.