Cloud Managed Networks

Issue with this solution, is that Clearpass information is overwritten.
I have tried this earlier, but had to remove it, because that systems like raspberry pi where recognized in Central as linux computers, not raspberry pi. And therefore the rule in Central got corrupted, and the systems where sent to different network. As of many other systems as well.

Had it only added the Device insight rule, it would have been a lot better, but when it screws up the database in central, then its useless. :(

I had so much hope for this, and still have, but I cannot have central rewriting Clearpass with other categories/family that is more general than Clearpass' database.

Anyone that have found an solution to this?

with New Central, the device gets profiled a lot better. Like in this case of RPi, the vendor for it is "Raspberry Pi". See the screenshot below.

Issue with this solution, is that Clearpass information is overwritten.
I have tried this earlier, but had to remove it, because that systems like raspberry pi where recognized in Central as linux computers, not raspberry pi. And therefore the rule in Central got corrupted, and the systems where sent to different network. As of many other systems as well.

Had it only added the Device insight rule, it would have been a lot better, but when it screws up the database in central, then its useless. :(

I had so much hope for this, and still have, but I cannot have central rewriting Clearpass with other categories/family that is more general than Clearpass' database.

Anyone that have found an solution to this?

Check out Evoko Naso booking plates.

Clearpass has the ability to map those to Evoko Family.

Central - Not so much.

If I now enable this integration between Central and Clearpass, then classification will be overwritten as Unclassified or set to something quite different, like Generic or Smartdevice or something else.

with New Central, the device gets profiled a lot better. Like in this case of RPi, the vendor for it is "Raspberry Pi". See the screenshot below.

Issue with this solution, is that Clearpass information is overwritten.
I have tried this earlier, but had to remove it, because that systems like raspberry pi where recognized in Central as linux computers, not raspberry pi. And therefore the rule in Central got corrupted, and the systems where sent to different network. As of many other systems as well.

Had it only added the Device insight rule, it would have been a lot better, but when it screws up the database in central, then its useless. :(

I had so much hope for this, and still have, but I cannot have central rewriting Clearpass with other categories/family that is more general than Clearpass' database.

Anyone that have found an solution to this?

Check out Evoko Naso booking plates.

Clearpass has the ability to map those to Evoko Family.

Central - Not so much.

If I now enable this integration between Central and Clearpass, then classification will be overwritten as Unclassified or set to something quite different, like Generic or Smartdevice or something else.

with New Central, the device gets profiled a lot better. Like in this case of RPi, the vendor for it is "Raspberry Pi". See the screenshot below.

Issue with this solution, is that Clearpass information is overwritten.
I have tried this earlier, but had to remove it, because that systems like raspberry pi where recognized in Central as linux computers, not raspberry pi. And therefore the rule in Central got corrupted, and the systems where sent to different network. As of many other systems as well.

Had it only added the Device insight rule, it would have been a lot better, but when it screws up the database in central, then its useless. :(

I had so much hope for this, and still have, but I cannot have central rewriting Clearpass with other categories/family that is more general than Clearpass' database.

Anyone that have found an solution to this?

In the context of Customers migrating from AOS8 overtime how does this integration effect DHCP Fingerprinting of both AP's and Clients on AOS8 where DHCP Relay is used to relay the Fingerprint  info to ClearPass.  It is not clear if ClearPass then stops listening to these requests once this integration with Central is done?

Check out Evoko Naso booking plates.

Clearpass has the ability to map those to Evoko Family.

Central - Not so much.

If I now enable this integration between Central and Clearpass, then classification will be overwritten as Unclassified or set to something quite different, like Generic or Smartdevice or something else.

with New Central, the device gets profiled a lot better. Like in this case of RPi, the vendor for it is "Raspberry Pi". See the screenshot below.

Issue with this solution, is that Clearpass information is overwritten.
I have tried this earlier, but had to remove it, because that systems like raspberry pi where recognized in Central as linux computers, not raspberry pi. And therefore the rule in Central got corrupted, and the systems where sent to different network. As of many other systems as well.

Had it only added the Device insight rule, it would have been a lot better, but when it screws up the database in central, then its useless. :(

I had so much hope for this, and still have, but I cannot have central rewriting Clearpass with other categories/family that is more general than Clearpass' database.

Anyone that have found an solution to this?

Thanks for this!

One remark though. You mention in your 2.1 Things You Need "ClearPass Policy Manager 6.11.x", and later in 3.2 ClearPass Integration to SSH to the CPPM and enter the "configure central-communication 1" command through SSH. This command has only been added to ClearPass since 6.11.10 (https://arubanetworking.hpe.com/techdocs/ClearPass/6.11/PolicyManager/Content/cmds/con-central-comm.htm). Don't ask me how I found out, please. :D

Steven

Thanks Steven, I'll update the technote, BTW how did you find it :-)

Thanks for this!

One remark though. You mention in your 2.1 Things You Need "ClearPass Policy Manager 6.11.x", and later in 3.2 ClearPass Integration to SSH to the CPPM and enter the "configure central-communication 1" command through SSH. This command has only been added to ClearPass since 6.11.10 (https://arubanetworking.hpe.com/techdocs/ClearPass/6.11/PolicyManager/Content/cmds/con-central-comm.htm). Don't ask me how I found out, please. :D

Steven

Can I use AOS-S switches as data collectors or does it have to be a CX switch? our environment is maybe 90% AOS-S and 10% CX

Thanks Steven, I'll update the technote, BTW how did you find it :-)

Thanks for this!

One remark though. You mention in your 2.1 Things You Need "ClearPass Policy Manager 6.11.x", and later in 3.2 ClearPass Integration to SSH to the CPPM and enter the "configure central-communication 1" command through SSH. This command has only been added to ClearPass since 6.11.10 (https://arubanetworking.hpe.com/techdocs/ClearPass/6.11/PolicyManager/Content/cmds/con-central-comm.htm). Don't ask me how I found out, please. :D

Steven