Slime: Nagios monitor single NIC dual IP

This article starts in the Slime row world.

The company's business has several servers stored in the IDC room, said to be a double line. But I see the configuration of the network card is a single NIC dual IP form. As follows:

650) this.width=650; "title=" clip_image001 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image001 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981352gw1r.png "width=" 557 "height="/>

650) this.width=650; "title=" clip_image002 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image002 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981353kevb.png "width=" 411 "height=" 481 "/>

And the company side of the line is Unicom's IP, as follows:

650) this.width=650; "title=" clip_image003 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image003 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981353yvjq.png "width=" 723 "height=" 317 "/>

Nagios monitoring is built within the company due to the problem of North-South line connectivity. The server on the company side of the Nagios monitoring IDC engine room frequently false alarms. Especially a big night, sister's, false alarm information more people are headache. As follows:

650) this.width=650; "title=" clip_image004 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image004 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981354spwl.png "width=" 808 "height=" 162 "/>

At first the suspicion was caused by the instability of the company's routers. But after a few reboots, this is still a problem. As follows:

650) this.width=650; "title=" clip_image005 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image005 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981355hkjf.png "width=" 644 "height=" 195 "/>

View Nagios monitors one of the servers with the IP address for the telco IP. As follows:

650) this.width=650; "title=" clip_image006 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image006 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 14119813556888.png "width=" 379 "height="/>

Ping the IP address within the company during the day, everything is OK. But I was embarrassed when the bag was badly dropped at night.

It was later assumed that the problem was due to the fact that Nagios had a certain monitoring cycle. If data is not available for a period of time, Nagios sends an email notification.

Make sure that Nagios monitors the IP address of the server as a Unicom IP, as follows:

650) this.width=650; "title=" clip_image007 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image007 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981356cqzr.png "width=" 407 "height=" "/>

After the modification, restart the Nagiso to monitor, as follows:

/etc/init.d/nagios restart

650) this.width=650; "title=" clip_image008 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image008 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981356q8jz.png "width=" 553 "height=" 107 "/>

After observing a period of time, it is still impossible to find, and it will be false alarm information.

This guest is a headache, ping that Unicom's IP is also through. As follows:

650) this.width=650; "title=" clip_image009 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image009 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981356a5s7.png "width=" 480 "height=" 158 "/>

Later, carefully observe the IP address configuration on the server as follows:

650) this.width=650; "title=" clip_image010 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image010 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981357ovav.png "width=" 394 "height=" 384 "/>

Found in the default gateway only the IP of telecommunications, and not the IP of the Unicom. Guess is not because of this cause, decisive add in. As follows:

650) this.width=650; "title=" clip_image011 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image011 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981358nrkx.png "width=" 412 "height=" 486 "/>

Once added, restart Nagios and monitor again. Found or false alarm, this time the pit father. If you don't know where the problem is, just click on it. Suddenly found in the network card display IP out with the network card configuration of the IP has a certain discrepancy, as follows:

650) this.width=650; "title=" clip_image012 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image012 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 14119813584oud.png "width=" 697 "height=" 508 "/>

Note the marked part of the figure.

You can see that the Unicom IP address you just added earlier as the gateway does not work.

What's going on here? Check the relevant information or have no clue.

Test the original telecommunications IP gateway deleted, add the Unicom IP, re-add the telecommunications IP, but found to be normal monitoring. As follows:

650) this.width=650; "title=" clip_image013 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; margin:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image013 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981359tfjg.png "width=" 825 "height=" 555 "/>

View the routing table for this server, as follows:

Route print

650) this.width=650; "title=" clip_image014 "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" clip_image014 "src=" http://img1.51cto.com/attachment/201409/29/526870_ 1411981359hwru.png "width=" 684 "height=" 435 "/>

Now I suspect that the original use of the telco IP as the default gateway. This causes Nagios to receive data that is causing network instability. This results in Nagios's false positives.

The false positives to this nagios have been greatly reduced ...

Slime: Nagios monitor single NIC dual IP