ISE 2.2p4 using 172.27.0.0 /16 for the NAD, ISE is not finding the NAD

[Richard Wakefield]

ISE 2.2p4 using 172.27.0.0 /16 for the NAD, ISE is not finding the NAD.

If I put in a specific address, 172.27.0.254/32 it works fine.

If I put in a subnet, 172.27.0.0/16, ISE log shows "unknown network device"

I think I am hitting this: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvg56391

I tried to pen a TAC case and 2 days later I have not heard anything from them, even after a re-queue. Seems lie an easy question. Is doing /16 or something like that supported? If I'm hitting this bug, is there a hotfix for it?

I get this:

I see the entry 172.27.0.0  /16 here:

So, I created a one-off rule for 172.27.0.254/32 and that worked fine.

In doing some research, they are suggesting that ISE will only allow up to a /24 in the format 172.26.0.1-255/32, I can’t confirm that.

https://communities.cisco.com/message/254809

I tried the above “172.26.0.1-255/32”, and it did work. I left it like that for now until I can get a firm answer on why 172.27.0.0/16 is not working (if it is supported) and if there is a hotfix.

[Jason Kunst]

Ok thank you, if you already escalated through the TAC to the BU and reached out to our product management through the sales team then I have no further ability to help.