|
In the v-cluster environment for NP7 units in v7.2.11 if the traffic stops passing through the LAG interface and resolves after removing the LAG interface members or using physical interface between cluster instead of LAG interface which is a logical interface it can be a match of known issue 1164092 that is included in the Known issues of v7.2.11.
Here is an example setup of the V-Cluster in CLI :
config system ha
set mode a-p
set vcluster-status enable
config cluster
edit 1
set monitor "Lag-Test"
set vdom "root" "vdom-2"
next
end
end
To check the issue, it is required to check with the following command:
fnsysctl cat /proc/net/np7/lag
name oid tid macid mtu mac_addr trbase abin nr_mbr nr_active member(oid, state)
Lag-Ext 179 1 43 1500 00:09:0f:09:7b:a6 2096 1 2 2 [(162,1),(163,1)]
Lag-Test 181 3 45 1500 00:09:0f:09:7b:9c 2144 0 2 2 [(152,1),(153,1)]
Total Entry: 2
Once the LAG interface OID is found for the TX issue, it is required to be set in the following CLI command:
diagnose npu np7 readtbl 0 cdb_tpact_tbl 0 181
[181]_SW: [82ee7fff,000000bb,00b40000,0000fffc,00000000]
[181]_HW: [82ee7fff,000000bb,00b40000,0000fffc,00000000]
...
trunk_vld (43:43) = 00000000
trunk_num (51:44) = 00000000
t2p_base (64:52) = 00000000
...
After checking if trunk_vld, trunk_num, and t2p_base are found NULL value or all zero, it is supposed to be a match of the known issue. To verify and confirm it, open a ticket with the Fortinet Technical Support Team. Otherwise, FortiGate can be upgraded to v7.2.12 or 7.4.8 GA versions, where the fix is implemented.
Related article:
Troubleshooting Tip: NP7 FortiGates on v7.2.11 may stop sending traffic out on certain interfaces
|
