Bug 1110804 - [Nagios] Network interface is shown as up even if it is disconnected
Summary: [Nagios] Network interface is shown as up even if it is disconnected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-nagios-addons
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHGS 3.0.4
Assignee: Timothy Asir
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks: 1182947
TreeView+ depends on / blocked
 
Reported: 2014-06-18 13:31 UTC by Shruti Sampat
Modified: 2015-05-13 17:53 UTC (History)
9 users (show)

Fixed In Version: gluster-nagios-addons-0.1.15-1.el6rhs
Doc Type: Bug Fix
Doc Text:
Previously, incorrect status was displayed for disconnected network interface. With this fix, the Nagios plug-in checks whether the interface is up and running and displays the correct status.
Clone Of:
Environment:
Last Closed: 2015-03-26 06:32:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0681 0 normal SHIPPED_LIVE Red Hat Storage Console 3.0 enhancement and bug fix update #4 2015-03-26 10:32:40 UTC

Description Shruti Sampat 2014-06-18 13:31:02 UTC
Description of problem:
-------------------------

For one of the nodes in my cluster, that was being monitored, a network interface was shown to be up even if it was actually disconnected.

See below -
----------------------------------------------------------------------------

# ifconfig eth5
eth5      Link encap:Ethernet  HWaddr 00:25:90:7C:2D:A5  
          inet addr:192.168.10.5  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Note: The IP address was assigned by running # ifconfig eth5 192.168.10.5

# ethtool eth5
Settings for eth5:
        Supported ports: [ TP ]
        Supported link modes:   100baseT/Full 
                                1000baseT/Full 
                                10000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  100baseT/Full 
                                1000baseT/Full 
                                10000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no


The status of the interface should have been shown as down in the Nagios UI, but was shown as up.

Version-Release number of selected component (if applicable):
gluster-nagios-addons-0.1.4-1.el6rhs.x86_64

How reproducible:
Saw it once.

Steps to Reproduce:
1. Assign an IP address to an interface, which is actually disconnected, using ifconfig command.
2. Run the network utilization service for that node.

Actual results:
The network utilization service shows the interface to be up.

Expected results:
The interface should be shown as down.

Additional info:

Comment 1 Timothy Asir 2014-06-19 06:59:32 UTC
Currently we are handling only UNKNOWN or OK status for the network interface and
the interface DOWN condition is not handled. However the plugin returns OK with out any perf data when the network is down. This will occurs only when the node has multiple interface.

Comment 2 Bala.FA 2014-06-19 07:32:30 UTC
upstream patch is under review at http://review.gluster.com/8111

Comment 4 Timothy Asir 2014-10-30 07:30:06 UTC
(In reply to Shruti Sampat from comment #0)
> Description of problem:
> -------------------------
> 
> For one of the nodes in my cluster, that was being monitored, a network
> interface was shown to be up even if it was actually disconnected.
> 
> See below -
> ----------------------------------------------------------------------------
> 
> # ifconfig eth5
> eth5      Link encap:Ethernet  HWaddr 00:25:90:7C:2D:A5  
>           inet addr:192.168.10.5  Bcast:192.168.10.255  Mask:255.255.255.0
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> 
> Note: The IP address was assigned by running # ifconfig eth5 192.168.10.5
> 
> # ethtool eth5
> Settings for eth5:
>         Supported ports: [ TP ]
>         Supported link modes:   100baseT/Full 
>                                 1000baseT/Full 
>                                 10000baseT/Full 
>         Supported pause frame use: No
>         Supports auto-negotiation: Yes
>         Advertised link modes:  100baseT/Full 
>                                 1000baseT/Full 
>                                 10000baseT/Full 
>         Advertised pause frame use: No
>         Advertised auto-negotiation: Yes
>         Speed: Unknown!
>         Duplex: Unknown! (255)
>         Port: Twisted Pair
>         PHYAD: 0
>         Transceiver: external
>         Auto-negotiation: on
>         MDI-X: Unknown
>         Supports Wake-on: d
>         Wake-on: d
>         Current message level: 0x00000007 (7)
>                                drv probe link
>         Link detected: no
> 
> 
> The status of the interface should have been shown as down in the Nagios UI,
> but was shown as up.
> 
> Version-Release number of selected component (if applicable):
> gluster-nagios-addons-0.1.4-1.el6rhs.x86_64
> 
> How reproducible:
> Saw it once.
> 
> Steps to Reproduce:
> 1. Assign an IP address to an interface, which is actually disconnected,
> using ifconfig command.
> 2. Run the network utilization service for that node.
> 
> Actual results:
> The network utilization service shows the interface to be up.
> 
> Expected results:
> The interface should be shown as down.
> 
> Additional info:


Currently the plugin check the interface status locally (in the server itself not thru remotly) and returns the status. If you assign any ip to an interface, you can also ping the ip locally. Please let me know whether you are able to ping the ip locally which you have assigned.

Comment 5 Shruti Sampat 2014-11-12 09:57:46 UTC
(In reply to Timothy Asir from comment #4)
> 
> 
> Currently the plugin check the interface status locally (in the server
> itself not thru remotly) and returns the status. If you assign any ip to an
> interface, you can also ping the ip locally. Please let me know whether you
> are able to ping the ip locally which you have assigned.

Timothy,

I am able to ping the IP address that I assigned locally to interface eth1. Let me know if you need more information.

Comment 11 Shruti Sampat 2015-02-18 09:14:51 UTC
Verified as fixed in gluster-nagios-addons-0.1.15-1.el6rhs.x86_64

Disconnected network interface is now shown as DOWN by Nagios.

Comment 12 Shalaka 2015-03-06 06:16:45 UTC
Please add doc text.

Comment 13 Shalaka 2015-03-13 07:09:25 UTC
Please review and sign-off edited doc text.

Comment 14 Timothy Asir 2015-03-13 09:28:12 UTC
It looks good to me!

Comment 16 errata-xmlrpc 2015-03-26 06:32:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0681.html


Note You need to log in before you can comment on or make changes to this bug.