Keeping the MC in sync

[gbudgbud7]

What is the best way to ensure the MC database is in sync with the actual running config for a sensor? Currently I remove and re-add the sensor if the MC does not reflect the actual sensor config?

[nkhawaja]

there is a script as well that you can run to sync up the mc with sensor

Usage Ex.

In a browser window type:

https:///ids-config/GPS?class=com.cisco.nm.mdc.ids.common.ReImport.ImportServlet&import-all=true

server = name or ip address.

or

https:///ids-config/GPS?class=com.cisco.nm.mdc.ids.common.ReImport.ImportServlet&import-name=machine1,machine2

or

https:///ids-config/GPS?class=com.cisco.nm.mdc.ids.common.ReImport.ImportServlet&import-ip=10.10.10.1,10.10.10.2

btw why it goes off sync?

[gbudgbud7]

Thanks for your reply. I will try your sugestions.

To answer your question: sometimes our admins may modify a sensor by logging into its own web interface or on the CL

[gbudgbud7]

I have some type of permission error to get through.

I will keep trying

[gbudgbud7]

I have had time to try running the script from my workstation and I get the following error:

"You are not authenticated, and are not allowed to perform this function. You must either be logged into the desktop and then launch this URL, or youmust pass a 'user' and 'password' parameter to use for authentication purposes".

I tried running it from a terminal window using the rdep client and I got the same error.

Any ideas?

[nkhawaja]

try to first login to VMS and keep those windows open. then launch this from a new browser window

[gbudgbud7]

Still did not work. How can I verify if the url is correct for our installation?

[gbudgbud7]

nkhawaja

looks like user head space issue. I was running the script from the main cisco works window not the MC for IDS Sensors window.

The script is running now. Ill have to wait for the results