Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
nagaraja_cs
Contributor

Unable to install QOS policy

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.

0 Kudos
9 Replies
Benedikt_Weissl
Advisor

Hi,

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

Best Regards,

0 Kudos
nagaraja_cs
Contributor

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.

 

0 Kudos
Benedikt_Weissl
Advisor

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

0 Kudos
nagaraja_cs
Contributor

Yes,it is performed but not working.

0 Kudos
G_W_Albrecht
Legend
Legend

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

CCSE CCTE SMB Specialist
0 Kudos
Tuatara
Explorer

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

0 Kudos
Steven_Sultana
Contributor

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.

0 Kudos
Sony_James
Participant

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.

0 Kudos
the_rock
Champion
Champion

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?

0 Kudos