ISE 2.7 Cannot create and edit authorization policy

[Sergey Bezpalov]

Hello,

Cisco ISE 2.7 cannot create and edit authorization policy, it is halted on conditions step.

Fetching data from server...

What the best way to fix this?

It is not possible now to open the case in TAC.

Thank you.

[marce1000]

          - Verify current health-status on the involved admin-node with : 

show application status ise

 If errors are listed , stop and re-start ise with application stop ise followed by application start ise Afterwards check the health-status of ISE again, with the initial command given.

 M. 

[Sergey Bezpalov]

Hi,

ISE 2.7 Services in Node

all app in stack working good and i already reboot/reload system.

( Cisco ISE 2.7.0.356 with patch 1, one and only node, small vm )

[marce1000]

 - Check your vm's resources  (CPU. memory, disk space!)  not only 'locally; (from the viewpoint of the vm), but also from the managerial hyper-visor environment.

 M.

[Sergey Bezpalov]

Hi,

 hypervisor resources (CPU, Memory and Storage) are good and no overloaded, its monitoring automatically and i check it especially for this case (manually).

Thank you.

[marce1000]

 - On ISE node issue show disk ; check if no partitions are full.

 M.

[Sergey Bezpalov]

Hi,

 "all internal filesystems have sufficient free space"

Thank you.

[sureshot]

If services running properly and all resources good, May be try using different browser (Chrome>/Firefox) in Private mode.

[marce1000]

 - Also if you would have some intranet fire-walling solution(s) in place between your browser (/terminal) and the ISE infrastructure then make sure some ISE-application traffic does not get blocked inadvertently.

 M.

[Sergey Bezpalov]

Hi,

after 12 hours authorization policy editor work good (without any actions), but system use old policy with new one.

Live Logs

"Wired" is old name of policy, "Wired ONE" new name. "Profiled Workstations" none existed (deleted) rule.

Thanks.

[Sergey Bezpalov · Accepted solution]

Hi,

backup

application reset-config ise

restore

And issue was fixed.

Thanks.