Page 6 of 6

Re: Config error for Exchange server and Network Switch

Posted: Fri May 11, 2012 12:48 pm
by dmanem
Hi,

I set the values based on your suggestions. Now the write config command is not showing any errors. I have not run the monitoring wizard configuration yet as the hosts are still out of sync. I am guessing they take time to get in sync. Now I have so many hosts without a proper parent node defined. As I have 500+ hosts is there a easier way to configure them than to go to each node separately and do so.

After the hosts are in sync I will run the monitoring wizard and will update you on the result.

Thank you very much for your help. I appreciate it.

Re: Config error for Exchange server and Network Switch

Posted: Sat May 12, 2012 6:48 pm
by scottwilkerson
They will show synced once you successfully apply configuration.

Off the top of my head, I don't have any easy way to set the parents for all of these hosts.

Re: Config error for Exchange server and Network Switch

Posted: Mon May 14, 2012 10:05 am
by dmanem
Hi,

I am trying to configure my Stack Switch and I am having issues again. When I am configuring the switch, the steps do not include the "Check period" and "Notification period" and they are required when configuring services on the switch. Is that a reason the configuration is failing? I have around 900 services for this switch and I cannot change those settings individually. Attached is the config snapshot with the errors.

Thank you.

Re: Config error for Exchange server and Network Switch

Posted: Mon May 14, 2012 10:18 am
by scottwilkerson
We recently ran into a similar issue with a different client that contained Nagios illegal characters as this does.

I am attaching a new Switch/Router wizard. Upload it to your server through Admin -> Manage Config Wizards

You will need to remove these through Configure -> CCM then re-run the wizard.

The new wizard will strip out (){}[]

Re: Config error for Exchange server and Network Switch

Posted: Mon May 14, 2012 1:46 pm
by dmanem
Thank you. That worked better.