Cannot remove a service check

[JohnFLi]

I have XI version 2014R2.7

I have a check that checks bandwidth on one of our fiber switches.
One of the ports is no longer being used (fc1/27) and was set to off on the switch. Naturally Nagios is reporting it as being down.
And I want to disable the check for that.

As it stands now, Nagios reports:

Code: Select all

DC-N5K-S2  fc1/27 Status  CRITICAL	08-20-2015 11:30:24	16d 9h 25m 0s	5/5	CRITICAL - Interface fc1/27 (index 16883712) is down 

But I am not able to disable it in XI using CCM /services.:

Code: Select all

DC-N5K-S2	fc1/26 Bandwidth	Yes	Applied	2360
	DC-N5K-S2	fc1/26 Status	Yes	Applied		2361
	DC-N5K-S2	fc1/28 Bandwidth	Yes	Applied	2364
	DC-N5K-S2	fc1/28 Status	Yes	Applied	2365

As you can see, fc1/27 isn't there.

When I go to Nagios core / system/configuration, it is:

Code: Select all

DC-N5K-S2	fc1/27 Bandwidth	0	5	0h 5m 0s	0h 1m 0s	check_xi_service_mrtgtraf!dc-n5k-s2_16883712.rrd!2,2!3,3!G	xi_timeperiod_24x7	Yes	No	Yes	Yes	Yes	No	Auto-determined value	Dave Harmon, Dave Harmon_txt	Yes	0h 30m 0s	0h 0m 0s	Unknown, Warning, Critical, Recovery, Flapping, Downtime	xi_timeperiod_24x7	 	Yes	None	Yes	Program-wide value	Program-wide value	Ok, Warning, Unknown, Critical	Yes	 	 	 	 	 	Status Information, Non-Status Information

DC-N5K-S2	fc1/27 Status	0	5	0h 5m 0s	0h 1m 0s	check_xi_service_ifoperstatusnag!16883712!-v3 -u sanswitchmonitor.svc -A k%pLk304UZ-J -a MD5 -l authNoPriv	xi_timeperiod_24x7	Yes	No	Yes	Yes	Yes	No	Auto-determined value	Dave Harmon, Dave Harmon_txt	Yes	0h 30m 0s	0h 0m 0s	Unknown, Warning, Critical, Recovery, Flapping, Downtime	xi_timeperiod_24x7	 	Yes	None	Yes	Program-wide value	Program-wide value	Ok, Warning, Unknown, Critical	Yes	 	 	 	 	 	Status Information, Non-Status Information

Any ideas on how to fix?

[ssax]

Please go to Configure > Core Config Manager > Tools > Write Config Files
- Click Delete (don't worry, it's safe, they get re-written)
- Click Write
- Now apply configuration

Let us know if that resolves the issue.

[JohnFLi]

Awesome....

Doing that took care of that issue....

You can close this