NagiosXI 5 upgrade issue (partial failed)

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
absarcompass
Posts: 182
Joined: Thu May 14, 2015 9:57 pm

Re: NagiosXI 5 upgrade issue (partial failed)

Post by absarcompass »

Hi Guys,
after upgrade I have noticed that my Network Devices which were added by the WIZARD in nagiosXI have started generating warning alarms for 'Admin Down' ports
I have checked the plugin its default value for admin down is 'warning'
Though i have changed the command at my end but i think default value for Admin down should not be warning because a port is put in administratively down mode for a known reason and for some time its been put for long, for good.

Wizard uses this "check_ifoperstatus"
from --help
-D (--admin-down =i|w|c) same for administratively down interfaces (default warning)
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: NagiosXI 5 upgrade issue (partial failed)

Post by rkennedy »

From the Core Config Manager, click the service in question for the port that is down, and uncheck the 'Active' box. This will stop all checks for the port that you expect to be down.
Former Nagios Employee
absarcompass
Posts: 182
Joined: Thu May 14, 2015 9:57 pm

Re: NagiosXI 5 upgrade issue (partial failed)

Post by absarcompass »

That is one of the solution if i have few ports to work on. In an environment where 700 hosts are mostly network devices, disabling single service for each port is not scale-able.
As i mentioned I have tweaked my checks for the Admin down status
command
usr/local/nagios/libexec/check_ifoperstatus -H x.x.x.x -C somecommunity -k 2 -v 2 -D i
will not generate alarms for Admin Down ports.
I was saying that it shouldn't be generating warning alarms for Admin Down ports at first place by default.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: NagiosXI 5 upgrade issue (partial failed)

Post by rkennedy »

Ah - I understand where you're getting now. Did you modify your service, or command?

The functionality built into the wizard gives you the option to deselect a port when you initially set it up, and would then not setup a service to monitor it. This should handle the scaling you're looking for.
Former Nagios Employee
absarcompass
Posts: 182
Joined: Thu May 14, 2015 9:57 pm

Re: NagiosXI 5 upgrade issue (partial failed)

Post by absarcompass »

Did you modify your service, or command?
I tweaked the command.

Yup! I know about the deselect of port:) I was trying to create services for all ports and let the admin down port be there without generating alarm on default because its a change in network ports on almost daily basis. And then I will have to keep track of left out ports and will have to run wizard quite a few times.
absarcompass
Posts: 182
Joined: Thu May 14, 2015 9:57 pm

Re: NagiosXI 5 upgrade issue (partial failed)

Post by absarcompass »

Hi Guys,
Just updated nagios xi 5 to version 2.2.3 and it again starts with a concern
have not tested all the fixes though but got this [img]
upgrade-result-web.png
[/img]
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
looks OK but i think this should have been fixed for the web interface update.


Note: Now will test the bulk modification tools :D
You do not have the required permissions to view the files attached to this post.
Locked