Hi thanks for the reply.
I'm not talking about HP Procurve switches, I'm talking about Hp rebadged H3C switches running comware 5 or comware 7. The procurve switches do run CoA on 3799. The comware 5 & comware 7 switches do different things.
If you have their virtual switch VSR ( running comware 7.1), then you can enable CoA and change the port it listens on through specific radius commands from the cli.
If you have a comware 7 router then the same commands appear
If you have a comware 5 or comware 7 switch ( e.g. 5500HI or 5130 EI) then it appears that CoA is supported as an extension of the radius server and you pump commands into port 1812. Theres no enable/disable functionality, no ability to change the port it listens on and no <expletive> documentation other than a 1 liner in the switch description glossy saying it supports RFC.... - CoA
The issue I had was that having configured our Aruba Controller to support CoA, when I select a clearpass "session" associated with a wireless user, I can see a change status option and can select an Aruba Terminate Session option... so everything does what is expected.
However this doesn't seem to be the case with the comware stuff. Even though I've defined an HP 5500/5130 switch as supporting CoA on port 1812 within clearpass, when I look at the session, you can't even select CoA under change status.
Quesiton is why? Whats going on in the background that makes clearpass think you can perform a CoA on an Aruba bit of kit but not on an HP one. Is there some form of dialogue between clearpass and the end switch that is missing on the comware side of things?
Rgds
Alex