Reset Search
 

 

Article

Rate limit pushed from Policy Manager after changes made via the GUI of the wireless controller will fail

« Go Back

Information

 
TitleRate limit pushed from Policy Manager after changes made via the GUI of the wireless controller will fail
Symptoms
  • Enforcing a rate limit from Policy Manager after changing said limits via the GUI of the controller will fail, be incorrect
Environment
  • IdentiFi Wireless
  • ExtremeWireless
  • Policy Manager
  • ExtremeManagement
Cause
The Policy Manager rate limit names on Netsight are not pushed to the controller. The controllers snmpagent will auto generate a name for each rate limit. Netsight will push the index only to the controller. That is why the controllers GUI shows something like "snmp.out.1x" "snmp.in.1" If the rate limit applies to out and in Policy Manager will create 2 rate limit indexes,one for in,one for out. Snmpagent will create 2 rate profiles in the controller with same rate. Snmpagent might use the already defined profile name and change the rate only. Also note that things can get bad if there are more than one import from the controller to PM. During the initial connection PM imports the controllers configuration and after that it is supposed to only push the changes back to the controller. If PM imports the controller config a second time things will be messed up and should not be done. 
Resolution
The bottom line here is you need to create the rate limit in Policy Manager and push it do not create it on the controller and import it and expect policy to be able to manage it. This is another case of do it in Policy Manager or via the GUI but not both. 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255