Secondary Node not joining to deployment after patch installation

[Jithishkk1514]

Hello Guys,

We have 2 ISE Nodes with 3.0 and we have installed Patch 4 in the ISE deployment due to a bug behavior. 

Patch installation was successful , but secondary node not joining to the deployment. Not sync is the error.

We have done the deregistered the node and reset the config and tried to join back to the deployment, still the sync is getting failed.

Can you guys help to let us know where is the issue and how to identify it.

[marce1000]

        - Could you post the exact error as it appears ?

 M.

[Arne Bier]

it smells like a communications issue between the Primary and the Secondary node. Is there a firewall in-between? 

If 100% no firewall between, and if you have gone as far as de-registering and resetting the node, then the next step I would recommend is to deploy a fresh VM (if you're using VMs of course) and try again.

Failing that, call TAC

[Marcelo Morais · Accepted solution]

Hi @Jithishkk1514 ,

 try to install the Secondary Node with 3.0 P4 and register to the Primary Node, during the sync process use the following command to check for errors:

ise/admin# show logging system ade/ADE.log tail

Note: please take a look at ISE 3.0 Installation Guide for ISE Ports Reference.

Hope this helps !!!

[thomas]

If you ISE deployment is not functioning, call TAC!

Dont wait for responses from the community.