Cisco ISE VM-AWS 3.4 - no Radius Live log and Blank Dashboard

[Agung1007]

Hi All,

Greetings.

we have an issue with Our Customer ISE 3.4 running on AWS (installed from AWS Marketplace) ==> BLANK Live log & Dashboard

after we restore config from Existing ISE.

Chronology:

Before we installed the ISE 3.4 on AWS,

we "try" to backup and restore from Our customer Existing ISE running 2.7 Patch 7, but with additional step. 

the detailed of procedure are :

1. Backup Config and Ops from Cisco ISE 2.7 patch 7

2. Installed VM-Temp Cisco ISE 3.2

3. Restored the Config & Ops from Cisco ISE 2.7 patch7, into ISE 3.2 VM-Temp

4. Installed Patch 7, for ISE 3.2 VM-Temp

5. Backup Config & Ops from ISE 3.2 patch 7

6. Installed ISE 3.4 on AWS --> target ISE

7. Restore Config & Ops from ISE 3.2 Patch 7 VM-Temp, into ISE AWS 3.4

8. Installed Patch 3 for ISE AWS 3.4 

- All process backup and restore works well.

- but when we try to migrate service (Radius/TACACS) to New ISE AWS 3.4,

- the client can connect and running well, but No Live Log & Dashboard blank

For tshoot we already try :

- Purge Operational Data

- Reset MnT Database

but still the same. the Live Log and Dashboard Still Blank/No Value

what causing it and how we solve the issue?

Kindly need your all insight and enlightment.

Thanks!
Best Regards.

[Mark Elsen]

   - @Agung1007              Check if this could be related to browser caching effects:
                                        Connected to ISE for instance with Chrome in incognito mode, refuse cookies.
                                                                Does it then still happen ?

 M.

[Agung1007]

Hi Mark,

Thanks for the reply.

Already try and check, but still the same (still blank).

[Marcelo Morais]

@Agung1007 ,

1st ... about your Chronology

Items 7 and 8 ... IMHO, I prefer to install the Patch first (to solve any bugs) before restoring the Config & Oper Bkp, I hope this makes sense to you and that you find it useful !

2nd ... two questions to better understand your issue:

• The Live Logs data is in MnT, are you also having issues with the Context Visibility (where the data is in PAN) ?
• Are your PAN and MnT in different Nodes ?

Hope this helps !

[Agung1007]

Hi @Marcelo Morais 

thanks for the reply,

with the running configuration,

can we "uninstall" the patch then install the patch?
Do we have known bug in the ISE 3.4 regarding this issue (blank live log) ?

the PAN and MnT in same Note (Standalone mode).

in the context visibility only showing device that already been connected before : 

 

[Marcelo Morais]

@Agung1007 and @SatriaAdidaya40508 ,

 since it's a Standalone Deployment, it makes sense to me that Context Visibility and Live Logs are having issues.

 Please check if your ISE Indexing Engine is running, it provides data for ISE Dashboard and ISE Context Visibility.

ise/admin# show application status ise
 ISE PROCESS NAME     STATE     PROCESS ID 
 -----------------------------------------
 ...
 ISE Indexing Engine  running   7360 
 ...

About your question: " ... Can we "uninstall" the patch then install the patch ? ... ", yes, with the following command:

ise/admin# patch remove ise 3
 Continue with application patch uninstall? [y/n] y
 % Warning: Patch will be removed only from this node. Remove patch using Primary Administration node GUI to remove from all nodes in deployment. Continue? (yes/no) [yes] ? yes
 Patch successfully uninstalled

 % This application Install or Upgrade requires reboot, rebooting now...

Note: if you don't mind, before uninstalling the patch, let's try 1st to debug the issue a little more.

[SatriaAdidaya40508]

Hi @Marcelo Morais , ISE is standalone mode