Unable to install QOS policy

[nagaraja_cs]

Hi Team,

We have upgraded the appliance and changed the management interface.

R80.20 cluster with Jumbo hotfix TAKE_103.

Everything works fine except QOS.

When we install QOS policy ,we are getting error  "A network interface name does not match the name assigned to the interface by the operating system"

There is no change in the interface name,we have verified it.

We have followed sk147593 but still it is same.

Disbled QOS blade and re-enabled the same but no luck.

We have a hospital  environment so it is required to assign minimum  bandwidth for one the critical machine.

Immediate help is appreciated.

[Benedikt_Weissl]

Hi,

have you checked for whitespaces after the interface name? Can you post the output of "fgate stat"?

Best Regards,

[nagaraja_cs]

After upgrading the appliance,we are unable to install policy at all(Not for a single time).Access control and Threat Prevention policies are installed.

There is no white space in the interface names.

Will the gateway shows the output for "fgate stat" if the QOS policy is not installed.

[Benedikt_Weissl]

Maybe its sk147593, can you try to delete the cache?

[nagaraja_cs]

Yes,it is performed but not working.

[G_W_Albrecht]

Please involve TAC - this is a serious issue...

[Tuatara]

Hello, have you solve the problem yet? I have the same issue on R80.40

[Steven_Sultana]

Sharing my experience. This happened to me after changing the topology and disabling an interface which was previously defined.

The disabled interface is not seen at all by the OS (eg. Missing from ifconfig), and this was causing the policy to fail (it seems the policy installation goes through the previously known interfaces as part of the procees).  cpd debugs on the gateway were helpful to discover this.

[Sony_James]

Had same issue today on R80.10, tried everything listed here, nothing worked. Restarted both cluster members 1 by 1 and that resolved the issue.

[the_rock]

I agree with all responses...I know this is an older post, but sounds like a pretty serious issue. Have you been able to fix it?