Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[server::dell::idrac::snmp:plugin] Networkinterface up/down status and filter on instance #3294

Closed
Hbitvof opened this issue Dec 3, 2021 · 27 comments
Labels

Comments

@Hbitvof
Copy link

Hbitvof commented Dec 3, 2021

Hi,

Is it possible to check the networkinterfaces of Dell servers for up/down status?

At the moment the plugin is only checking for status, two of below interfaces are down:

network 'Intel(R) Gigabit 4P X710/I350 rNDC - 24:6E:96:AB:3F:A3' status is 'ok' [instance = 1.1]
network 'Intel(R) Ethernet 10G X710 rNDC - 24:6E:96:AB:3F:84' status is 'ok' [instance = 1.2]
network 'Intel(R) Ethernet 10G 4P X710/I350 rNDC - 24:6E:96:AB:3F:82' status is 'ok' [instance = 1.3]
network 'Intel(R) Gigabit 4P X710/I350 rNDC - 24:6E:96:AB:3F:A2' status is 'ok' [instance = 1.4]

These are down:

#1 ConnectionStatus = Down, FQDD = NIC.Integrated.1-4-1, ProductName = Intel(R) Gigabit 4P X710/I350 rNDC - 24:6E:96:AB:3F:A3
#2 ConnectionStatus = Down, FQDD = NIC.Integrated.1-3-1, ProductName = Intel(R) Gigabit 4P X710/I350 rNDC - 24:6E:96:AB:3F:A2

So in this example I want to know if instance 1.1 and 1.2 have status up and instance 1.3 and instance 1.4 should be ignored

Is this possible to add?

@garnier-quentin
Copy link
Contributor

garnier-quentin commented Dec 3, 2021

You cannot check directly in the operating system ?

@Hbitvof
Copy link
Author

Hbitvof commented Dec 3, 2021

You cannot check directly in the operating system ?

No, these are ESX servers and we don't have an agent or something on these nodes that can talk to our monitoring solution.

@garnier-quentin
Copy link
Contributor

You can use the vmware connector: https://github.com/centreon/centreon-vmware

@Hbitvof
Copy link
Author

Hbitvof commented Dec 3, 2021

You can use the vmware connector: https://github.com/centreon/centreon-vmware

That's not working for me. I get this error:

Can't locate ZMQ/LibZMQ4.pm in @inc

And the instructions to get this working seems outdated.

@garnier-quentin
Copy link
Contributor

Pease use rpm package for the connector vmware.

yum install centreon-plugin-Virtualization-VMWare-daemon

@Hbitvof
Copy link
Author

Hbitvof commented Dec 3, 2021

Pease use rpm package for the connector vmware.

yum install centreon-plugin-Virtualization-VMWare-daemon

That's not working:

No package centreon-plugin-Virtualization-VMWare-daemon available.

@garnier-quentin
Copy link
Contributor

Do you use centreon ? You can add centreon repository to install the connector vmware (it won't install centreon)

@Hbitvof
Copy link
Author

Hbitvof commented Dec 3, 2021

Do you use centreon ? You can add centreon repository to install the connector vmware (it won't install centreon)

No, we use Nagios XI on top of CentOS.

@garnier-quentin
Copy link
Contributor

You can install the repository:
yum install https://yum.centreon.com/standard/21.10/el7/stable/noarch/RPMS/centreon-release-21.10-4.el7.centos.noarch.rpm

And install the vmware connector (plugins also if you want) and disable/remove the repository

@garnier-quentin
Copy link
Contributor

Have you succeeded ? :)

@Hbitvof
Copy link
Author

Hbitvof commented Dec 9, 2021

Have you succeeded ? :)

Hi, Apologies for the late response.

Using the vmware connector is not an option for us because we need to roll out multiple VMWare connectors because we have different VCenters and we have bad experience with those connectors (when a connector give problems we see many messages in our monitoring that's only related to this connector).

This said, we prefer to connect directly to the ESX server.

@garnier-quentin
Copy link
Contributor

You can connect directly to the ESX with the connector.

@Hbitvof
Copy link
Author

Hbitvof commented Dec 9, 2021

You can connect directly to the ESX with the connector.

Ah ok. I thought I had to connect everytime to vCenter. So I can use the following command?:

--plugin=apps::vmware::connector::plugin --mode=net-host --connector-hostname=serverx.x --vsphere-username=username --vsphere-password=password

When I do this I get a timeout.

@garnier-quentin
Copy link
Contributor

The plugin connect the vmware connector:
plugin ----> vmware connector --> esx

@Hbitvof
Copy link
Author

Hbitvof commented Dec 9, 2021

The plugin connect the vmware connector: plugin ----> vmware connector --> esx

What's in this case the vmware connector?

@garnier-quentin
Copy link
Contributor

vmware connector is for performance improvement.

@Hbitvof
Copy link
Author

Hbitvof commented Dec 9, 2021

vmware connector is for performance improvement.

But what do I need to fill in there?

@garnier-quentin
Copy link
Contributor

You have a onlive mode with vmware connector (don't need to add it in centreon_vmware.pm file). Have you read the documentation ?

@Hbitvof
Copy link
Author

Hbitvof commented Dec 9, 2021

You have a onlive mode with vmware connector (don't need to add it in centreon_vmware.pm file). Have you read the documentation ?

Now I understand this is related to something else. Guess I need to use the option. Now I tried with:

centreon_plugins.pl --plugin=apps::vmware::wsman::plugin --mode=hardware --hostname=ESXserver --wsman-username=username --wsman-password=password

But I get a timeout:

UNKNOWN: Could not enumerate instances: Timeout was reached

Do I need to configure anything on the ESX host side?

@garnier-quentin
Copy link
Contributor

The wsman plugin is only for hardware stuff. You won't have the information about vmnic connection status.

@garnier-quentin
Copy link
Contributor

To get that information, you need to use the connector: https://github.com/centreon/centreon-vmware/blob/master/doc/en/exploitation/index.rst

@garnier-quentin
Copy link
Contributor

You should use the vmware connector. Otherwise, you can use the snmp (apps::protocols::snmp) collection mode to check it. If you provide snmpwalk of the good OID i could provide the config for the mode collection.

@garnier-quentin
Copy link
Contributor

Could you provide the snmpwalk ? if you want to use snmp

@Hbitvof
Copy link
Author

Hbitvof commented Aug 1, 2022

Could you provide the snmpwalk ? if you want to use snmp

You can close this one. I solved this by another solution from Dell.

@garnier-quentin
Copy link
Contributor

Ok. what is the solution ? for information

@Hbitvof
Copy link
Author

Hbitvof commented Aug 1, 2022

Ok. what is the solution ? for information

We solved it with Dell EMC OpenManage Plug-in Version 3.2.0 For Nagios XI. In this version of this plugin the check is added on my request: (https://www.dell.com/support/manuals/nl-nl/openmanage-plugin-nagios-xi/nagios_xi_3.2.0_rn/new-features?guid=guid-f8ee7116-4440-4123-ae98-c290a8ace6df&lang=en-us)

@garnier-quentin
Copy link
Contributor

Thanks for the feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants