In ClusterXL, unused interfaces are marked as Monitored Interfaces.

[ChoiYunSoo]

Hi

Today I worked on adding a VLAN interface to a customer's firewall.

But due to other issues I had to restore the interface

But something strange happened

I deleted the interface in the CLI configuration, deleted the VLAN interface using 'Get' in the smart console topology, and installed the policy, but the ClusterXL Monitored interface still displays a VLAN interface.

In detail, it is as follows:

When you enter the 'cphaprob -a if' command in CLI, the VLAN interface is not displayed.

And when I typed 'cphaprob -l list' / 'cphaprob -e' as CLI commands, pnote shows all statuses as ok.

However, if you look at 'Device & License Information --> ClusterXL --> Interface table' in SmartConsole, you can see the 'eth1-01.131' VLAN interface and the interface is marked as Down.

Of course, if you look at the 'Problem Notification Table' on the same screen of SmartConsole, all statuses are displayed as ok here as well.

The customer's management server and firewall are both version R81.10, and the interface uses the 10Gbps i40e driver.
Has anyone experienced similar bug symptoms as me?

PS

The standby firewall solved the problem by restarting the daemon, but due to failover issues, FW_A is unable to restart the daemon and still displays the VLAN interface.

Thank you in advance for those who responded

[G_W_Albrecht]

Looks like a cosmetic issue in SmartConsole as CLI does not display it. Did you try a reboot already ?

[ChoiYunSoo]

Thank you for your reply

It's not a cosmetic problem

In fact, ClusterXL redundancy indicates Down status.

I uploaded a capture file to help you understand.

[G_W_Albrecht]

I would suggest to call TAC immediately to get this resolved asap !

[ChoiYunSoo]

I opened the case and the manufacturer is investigating the case.

Thanks for your reply

[emmap]

Interface monitoring oddness can sometimes require a reboot to clear up. I'd suggest setting the interface to 'state off' before rebooting to be sure.

[ChoiYunSoo]

Currently the FW_B firewall is cpstop; Confirmed normalization with cpstart

However, there are servers that require a restart when fail-over, so I posted a post on the community to see if there was a way to not fail-over.

Thank you for answer