Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Bruno_Petronio
Contributor

CPD_amon traffic TCP/18192 still to old IP after changing Mgmt IP of the Gw cluster

Jump to solution

Hello all,

 

After changing in the IP Address and interface in one cluster of firewalls, i realize that our Management Smarts are  still trying to reach the old IP for TCP/18192.

As there is no communication established for the old IP the SmartConsole states the firewall cluster is Down, which is not true.

I can still install policy  through the new defined IP, which leaves me to the question that something is "hardcoded" in both MDS regarding the TCP/18192.

 

I reseted the SIC for one cluster member and the symptom is the same.

Went in the GUIEditDB and i dont find this old IPs anywhere ...

 

Running R80.30 T200 + JHF 215.

Any troubleshooting suggestion ?

 

Thanks in advance !

0 Kudos
1 Solution

Accepted Solutions
John_Fleming
Advisor

restart CPD process on mgmt server. 

View solution in original post

6 Replies
John_Fleming
Advisor

restart CPD process on mgmt server. 

View solution in original post

Wolfgang
Leader
Leader

And too I suggest an „install database“ on the management.

Wolfgang

0 Kudos
Bruno_Petronio
Contributor

It was done before. 

No difference.

0 Kudos
Bruno_Petronio
Contributor

Not the way i was expecting but mdsstop solved the issue.

 

Tks.

0 Kudos
Erik_perez
Participant

Hello,

When changing the IP in the firewalls using the webui or cli, you have to update the object that represents the Firewall in the smart console to update the topologies and update the routing tables. Have you already done this step?

regards

0 Kudos
Bruno_Petronio
Contributor

Firewall object in Smart was updated with the new IPs and new interfaces were created before that as well.

All comunication from MDS (primary and secondary) are made trough the new IPs with the exception of CPD_admon TCP/18192.

0 Kudos