Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
On Behalf Of Andreas Döhler
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
-Fabric Element checks
-PSU
-Temperature Sensors
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)
Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)
Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
Hi Marco,
One rule you can look at is “disabled checks” and “disabled services”. This is the naming of the actual 1.5 and 1.6 version. I don’t know how the old naming in 1.2.6 is for this rules.
There it is possible that the check type is disabled for fiber channel interfaces.
Best regards
Andreas
Am Di., 24. Sept. 2019 um 06:51 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
- Created a test site on the same server and added the device (Agent type= SNMP (Networking device, Appliance) ). This device is queried using a public community string so I have not created any rules.
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
- A Lot of FiberChannel Port x.xx checks
-Fabric Element checks
-PSU
-Temperature Sensors
- On the prod site, the same device (Agent type= SNMP (Networking device, Appliance)) only shows 4 checks:
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
- I tried to dump configuration about the hosts on test and prod site:
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
Hi Andreas,
It’s the same name in 1.2.6p15.
I already checked these rule sets but nothing is there.
On Tue 24. Sep 2019 at 09:59, Andreas Döhler andreas.doehler@gmail.com wrote:
Hi Marco,
One rule you can look at is “disabled checks” and “disabled services”. This is the naming of the actual 1.5 and 1.6 version. I don’t know how the old naming in 1.2.6 is for this rules.
There it is possible that the check type is disabled for fiber channel interfaces.
Best regards
Andreas
Am Di., 24. Sept. 2019 um 06:51 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
- Created a test site on the same server and added the device (Agent type= SNMP (Networking device, Appliance) ). This device is queried using a public community string so I have not created any rules.
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
- A Lot of FiberChannel Port x.xx checks
-Fabric Element checks
-PSU
-Temperature Sensors
- On the prod site, the same device (Agent type= SNMP (Networking device, Appliance)) only shows 4 checks:
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
- I tried to dump configuration about the hosts on test and prod site:
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
Okay. I tried the
cmk --debug -v -v -II on the PROD and test sites.
While running the debug, I noticed that it ignores the OID and its subelements and does not do any walk on it.
( “.1.3.6.1.2.1.75.1”,[
OID_END, # Index of the Port
“2.1.1.3”, # fcFxPortOperMode
“2.2.1.1”, # fcFxPortPhysAdminStatus
“2.2.1.2”, # fcFxPortPhysOperStatus
“3.1.1.1”, # fcFxPortLinkFailures
“3.1.1.2”, # fcFxPortSyncLosses
“3.1.1.4”, # fcFxPortPrimSeqProtoErrors
“3.1.1.5”, # fcFxPortInvalidTxWords
“3.1.1.6”, # fcFxPortInvalidCrcs
“3.1.1.8”, # fcFxPortAddressIdErrors
“3.1.1.9”, # fcFxPortLinkResetIns
“3.1.1.10”, # fcFxPortLinkResetOuts
“3.1.1.11”, # fcFxPortOlsIns
“3.1.1.12”, # fcFxPortOlsOuts
“4.2.1.1”, # fcFxPortC2InFrames
“4.2.1.2”, # fcFxPortC2OutFrames
“4.2.1.3”, # fcFxPortC2InOctets
“4.2.1.4”, # fcFxPortC2OutOctets
But on the TEST site, it walks over the above OID tree and shows the FCport checks.
Now, this sounds to be some kind of rule that is telling checkmk to skip the oid or some manual configuration somewhere which I am overlooking.
Can you please advise ? What I could check more ?
On Tue, Sep 24, 2019 at 12:29 PM marco checl-mk marcocheckmk2005@gmail.com wrote:
Hi Andreas,
It’s the same name in 1.2.6p15.
I already checked these rule sets but nothing is there.
On Tue 24. Sep 2019 at 09:59, Andreas Döhler andreas.doehler@gmail.com wrote:
Hi Marco,
One rule you can look at is “disabled checks” and “disabled services”. This is the naming of the actual 1.5 and 1.6 version. I don’t know how the old naming in 1.2.6 is for this rules.
There it is possible that the check type is disabled for fiber channel interfaces.
Best regards
Andreas
Am Di., 24. Sept. 2019 um 06:51 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
- Created a test site on the same server and added the device (Agent type= SNMP (Networking device, Appliance) ). This device is queried using a public community string so I have not created any rules.
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
- A Lot of FiberChannel Port x.xx checks
-Fabric Element checks
-PSU
-Temperature Sensors
- On the prod site, the same device (Agent type= SNMP (Networking device, Appliance)) only shows 4 checks:
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
- I tried to dump configuration about the hosts on test and prod site:
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
Check your SAN switch. It may be configured to restrict access.
On Behalf Of marco checl-mk
Okay. I tried the
cmk --debug -v -v -II on the PROD and test sites.
While running the debug, I noticed that it ignores the OID and its subelements and does not do any walk on it.
( “.1.3.6.1.2.1.75.1”,[
OID_END, # Index of the Port
“2.1.1.3”, # fcFxPortOperMode
“2.2.1.1”, # fcFxPortPhysAdminStatus
“2.2.1.2”, # fcFxPortPhysOperStatus
“3.1.1.1”, # fcFxPortLinkFailures
“3.1.1.2”, # fcFxPortSyncLosses
“3.1.1.4”, # fcFxPortPrimSeqProtoErrors
“3.1.1.5”, # fcFxPortInvalidTxWords
“3.1.1.6”, # fcFxPortInvalidCrcs
“3.1.1.8”, # fcFxPortAddressIdErrors
“3.1.1.9”, # fcFxPortLinkResetIns
“3.1.1.10”, # fcFxPortLinkResetOuts
“3.1.1.11”, # fcFxPortOlsIns
“3.1.1.12”, # fcFxPortOlsOuts
“4.2.1.1”, # fcFxPortC2InFrames
“4.2.1.2”, # fcFxPortC2OutFrames
“4.2.1.3”, # fcFxPortC2InOctets
“4.2.1.4”, # fcFxPortC2OutOctets
But on the TEST site, it walks over the above OID tree and shows the FCport checks.
Now, this sounds to be some kind of rule that is telling checkmk to skip the oid or some manual configuration somewhere which I am overlooking.
Can you please advise ? What I could check more ?
On Tue, Sep 24, 2019 at 12:29 PM marco checl-mk marcocheckmk2005@gmail.com wrote:
Hi Andreas,
It’s the same name in 1.2.6p15.
I already checked these rule sets but nothing is there.
On Tue 24. Sep 2019 at 09:59, Andreas Döhler andreas.doehler@gmail.com wrote:
Hi Marco,
One rule you can look at is “disabled checks” and “disabled services”. This is the naming of the actual 1.5 and 1.6 version. I don’t know how the old naming in 1.2.6 is for this rules.
There it is possible that the check type is disabled for fiber channel interfaces.
Best regards
Andreas
Am Di., 24. Sept. 2019 um 06:51 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
- Created a test site on the same server and added the device (Agent type= SNMP (Networking device, Appliance) ). This device is queried using a public community string so I have not created any rules.
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
- A Lot of FiberChannel Port x.xx checks
-Fabric Element checks
-PSU
-Temperature Sensors
- On the prod site, the same device (Agent type= SNMP (Networking device, Appliance)) only shows 4 checks:
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
- I tried to dump configuration about the hosts on test and prod site:
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM
Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for
your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows
few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
Hi Matthew,
It works perfectly fine and returns data on the test site which I created on the monitoring server. For the Prod site on the same server, it does not work.
On Tue 24. Sep 2019 at 18:58, Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
Check your SAN switch. It may be configured to restrict access.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of marco checl-mk
Sent: Tuesday, September 24, 2019 9:54 AM
To: Andreas Döhler andreas.doehler@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Okay. I tried the
cmk --debug -v -v -II on the PROD and test sites.
While running the debug, I noticed that it ignores the OID and its subelements and does not do any walk on it.
( “.1.3.6.1.2.1.75.1”,[
OID_END, # Index of the Port
“2.1.1.3”, # fcFxPortOperMode
“2.2.1.1”, # fcFxPortPhysAdminStatus
“2.2.1.2”, # fcFxPortPhysOperStatus
“3.1.1.1”, # fcFxPortLinkFailures
“3.1.1.2”, # fcFxPortSyncLosses
“3.1.1.4”, # fcFxPortPrimSeqProtoErrors
“3.1.1.5”, # fcFxPortInvalidTxWords
“3.1.1.6”, # fcFxPortInvalidCrcs
“3.1.1.8”, # fcFxPortAddressIdErrors
“3.1.1.9”, # fcFxPortLinkResetIns
“3.1.1.10”, # fcFxPortLinkResetOuts
“3.1.1.11”, # fcFxPortOlsIns
“3.1.1.12”, # fcFxPortOlsOuts
“4.2.1.1”, # fcFxPortC2InFrames
“4.2.1.2”, # fcFxPortC2OutFrames
“4.2.1.3”, # fcFxPortC2InOctets
“4.2.1.4”, # fcFxPortC2OutOctets
But on the TEST site, it walks over the above OID tree and shows the FCport checks.
Now, this sounds to be some kind of rule that is telling checkmk to skip the oid or some manual configuration somewhere which I am overlooking.
Can you please advise ? What I could check more ?
On Tue, Sep 24, 2019 at 12:29 PM marco checl-mk marcocheckmk2005@gmail.com wrote:
Hi Andreas,
It’s the same name in 1.2.6p15.
I already checked these rule sets but nothing is there.
On Tue 24. Sep 2019 at 09:59, Andreas Döhler andreas.doehler@gmail.com wrote:
Hi Marco,
One rule you can look at is “disabled checks” and “disabled services”. This is the naming of the actual 1.5 and 1.6 version. I don’t know how the old naming in 1.2.6 is for this rules.
There it is possible that the check type is disabled for fiber channel interfaces.
Best regards
Andreas
Am Di., 24. Sept. 2019 um 06:51 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
- Created a test site on the same server and added the device (Agent type= SNMP (Networking device, Appliance) ). This device is queried using a public community string so I have not created any rules.
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
- A Lot of FiberChannel Port x.xx checks
-Fabric Element checks
-PSU
-Temperature Sensors
- On the prod site, the same device (Agent type= SNMP (Networking device, Appliance)) only shows 4 checks:
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
- I tried to dump configuration about the hosts on test and prod site:
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM > > > > Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for
your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows
few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
Can anyone suggest what else I can do to troubleshoot further?
On Tue 24. Sep 2019 at 19:00, marco checl-mk marcocheckmk2005@gmail.com wrote:
Hi Matthew,
It works perfectly fine and returns data on the test site which I created on the monitoring server. For the Prod site on the same server, it does not work.
On Tue 24. Sep 2019 at 18:58, Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
Check your SAN switch. It may be configured to restrict access.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of marco checl-mk
Sent: Tuesday, September 24, 2019 9:54 AM
To: Andreas Döhler andreas.doehler@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Okay. I tried the
cmk --debug -v -v -II on the PROD and test sites.
While running the debug, I noticed that it ignores the OID and its subelements and does not do any walk on it.
( “.1.3.6.1.2.1.75.1”,[
OID_END, # Index of the Port
“2.1.1.3”, # fcFxPortOperMode
“2.2.1.1”, # fcFxPortPhysAdminStatus
“2.2.1.2”, # fcFxPortPhysOperStatus
“3.1.1.1”, # fcFxPortLinkFailures
“3.1.1.2”, # fcFxPortSyncLosses
“3.1.1.4”, # fcFxPortPrimSeqProtoErrors
“3.1.1.5”, # fcFxPortInvalidTxWords
“3.1.1.6”, # fcFxPortInvalidCrcs
“3.1.1.8”, # fcFxPortAddressIdErrors
“3.1.1.9”, # fcFxPortLinkResetIns
“3.1.1.10”, # fcFxPortLinkResetOuts
“3.1.1.11”, # fcFxPortOlsIns
“3.1.1.12”, # fcFxPortOlsOuts
“4.2.1.1”, # fcFxPortC2InFrames
“4.2.1.2”, # fcFxPortC2OutFrames
“4.2.1.3”, # fcFxPortC2InOctets
“4.2.1.4”, # fcFxPortC2OutOctets
But on the TEST site, it walks over the above OID tree and shows the FCport checks.
Now, this sounds to be some kind of rule that is telling checkmk to skip the oid or some manual configuration somewhere which I am overlooking.
Can you please advise ? What I could check more ?
On Tue, Sep 24, 2019 at 12:29 PM marco checl-mk marcocheckmk2005@gmail.com wrote:
Hi Andreas,
It’s the same name in 1.2.6p15.
I already checked these rule sets but nothing is there.
On Tue 24. Sep 2019 at 09:59, Andreas Döhler andreas.doehler@gmail.com wrote:
Hi Marco,
One rule you can look at is “disabled checks” and “disabled services”. This is the naming of the actual 1.5 and 1.6 version. I don’t know how the old naming in 1.2.6 is for this rules.
There it is possible that the check type is disabled for fiber channel interfaces.
Best regards
Andreas
Am Di., 24. Sept. 2019 um 06:51 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
- Created a test site on the same server and added the device (Agent type= SNMP (Networking device, Appliance) ). This device is queried using a public community string so I have not created any rules.
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
- A Lot of FiberChannel Port x.xx checks
-Fabric Element checks
-PSU
-Temperature Sensors
- On the prod site, the same device (Agent type= SNMP (Networking device, Appliance)) only shows 4 checks:
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
- I tried to dump configuration about the hosts on test and prod site:
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM > > > > > Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for
your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows
few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en
It is important what you see with a “cmk --debug -vvI” on the command line.
There are information if a check is found or not.
I can only speak for version 1.5 and newer as I have no older systems available at the moment.
Inside the debug output you find the lines “SNMP scan found” and “SNMP filtered check plugin names”. If there are the expected plugins included the scan was working correctly.
After this lines you see the SNMP queries for the single checks found.
Best regards
Andreas
Am Mi., 25. Sept. 2019 um 09:02 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Can anyone suggest what else I can do to troubleshoot further?
On Tue 24. Sep 2019 at 19:00, marco checl-mk marcocheckmk2005@gmail.com wrote:
Hi Matthew,
It works perfectly fine and returns data on the test site which I created on the monitoring server. For the Prod site on the same server, it does not work.
On Tue 24. Sep 2019 at 18:58, Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
Check your SAN switch. It may be configured to restrict access.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of marco checl-mk
Sent: Tuesday, September 24, 2019 9:54 AM
To: Andreas Döhler andreas.doehler@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Okay. I tried the
cmk --debug -v -v -II on the PROD and test sites.
While running the debug, I noticed that it ignores the OID and its subelements and does not do any walk on it.
( “.1.3.6.1.2.1.75.1”,[
OID_END, # Index of the Port
“2.1.1.3”, # fcFxPortOperMode
“2.2.1.1”, # fcFxPortPhysAdminStatus
“2.2.1.2”, # fcFxPortPhysOperStatus
“3.1.1.1”, # fcFxPortLinkFailures
“3.1.1.2”, # fcFxPortSyncLosses
“3.1.1.4”, # fcFxPortPrimSeqProtoErrors
“3.1.1.5”, # fcFxPortInvalidTxWords
“3.1.1.6”, # fcFxPortInvalidCrcs
“3.1.1.8”, # fcFxPortAddressIdErrors
“3.1.1.9”, # fcFxPortLinkResetIns
“3.1.1.10”, # fcFxPortLinkResetOuts
“3.1.1.11”, # fcFxPortOlsIns
“3.1.1.12”, # fcFxPortOlsOuts
“4.2.1.1”, # fcFxPortC2InFrames
“4.2.1.2”, # fcFxPortC2OutFrames
“4.2.1.3”, # fcFxPortC2InOctets
“4.2.1.4”, # fcFxPortC2OutOctets
But on the TEST site, it walks over the above OID tree and shows the FCport checks.
Now, this sounds to be some kind of rule that is telling checkmk to skip the oid or some manual configuration somewhere which I am overlooking.
Can you please advise ? What I could check more ?
On Tue, Sep 24, 2019 at 12:29 PM marco checl-mk marcocheckmk2005@gmail.com wrote:
Hi Andreas,
It’s the same name in 1.2.6p15.
I already checked these rule sets but nothing is there.
On Tue 24. Sep 2019 at 09:59, Andreas Döhler andreas.doehler@gmail.com wrote:
Hi Marco,
One rule you can look at is “disabled checks” and “disabled services”. This is the naming of the actual 1.5 and 1.6 version. I don’t know how the old naming in 1.2.6 is for this rules.
There it is possible that the check type is disabled for fiber channel interfaces.
Best regards
Andreas
Am Di., 24. Sept. 2019 um 06:51 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Thank you, Andreas and Matthew, for your response.
So far, I have done the below:
- Created a test site on the same server and added the device (Agent type= SNMP (Networking device, Appliance) ). This device is queried using a public community string so I have not created any rules.
I am able to see the below checks now apart from the Interface eth, SNMP info, Uptime checks, etc:
- A Lot of FiberChannel Port x.xx checks
-Fabric Element checks
-PSU
-Temperature Sensors
- On the prod site, the same device (Agent type= SNMP (Networking device, Appliance)) only shows 4 checks:
-SNMP info
-Uptime
-Checkmk
-Interface eth
It looks like some kind of restriction/rule exists that is preventing the discovery of the other checks or something else.
On the Prod site >> Network and Switch Port discovery rule, I see a couple of rules there defined for some particular devices like different CISCO models and at the bottom, there is a generic rule defined like this:
Condition: Host has tag monitor via SNMP
Use description as service name for network interface checks: On
Network interface port types to discover: ethernetCsmacd(6), frameRelay(32), propVirtual(53), fibreChannel(56), fastEther(62), gigabitEthernet(117), ieee8023adLag(161)
- I tried to dump configuration about the hosts on test and prod site:
cmk -D
Test site:
Tags: site:test, snmp-only, prod, snmp, lan, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Prod site:
Tags: wan, site:prod, snmp, sl3, snmp-only, prod, wato, /wato/
Type of agent: SNMP (community: ‘public’, bulk walk: yes, port: default, inline: yes)Any pointers what else can be checked/looked into?
On Mon, Sep 23, 2019 at 9:44 PM > > > > > > Matthew.Stier@us.fujitsu.com Matthew.Stier@us.fujitsu.com wrote:
An issue I’ve run into, is that when the check scans for applicable MIB, it may not find the one for
your systems.
The qlogic_sanbox ships that check oid(“.1.3.6.1.2.1.1.2.0”) for “.1.3.6.1.4.1.3873.1.8” and “.1.3.6.1.4.1.3873.1.14”.
My 5802 starts with “.1.3.6.1.4.1.3873.1.9”
I copied the check to ~/local/share/check_mk/checks/ and add my MIB value, and the checks started working.
From: checkmk-en checkmk-en-bounces@lists.mathias-kettner.de
On Behalf Of Andreas Döhler
Sent: Monday, September 23, 2019 1:52 PM
To: marco checl-mk marcocheckmk2005@gmail.com
Cc: checkmk-en@lists.mathias-kettner.de checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] SNMP v2c issue on qlogic sanbox devices
Hi Marco,
this is a correct behavior. If there are no checks for your device available, then you will only see the general checks like interface and SNMP info.
What you should do first is. Use the actual CheckMK version and test if there are some more information available on your device.
For the fiber channel ports it is also possible to adjust the “Network and switch port discovery” rule. There you can define the interface type the system should discover.
But if this is are “normal” SAN switch then the fiber channel ports should be automatically found.
Best regards
Andreas
Am Mo., 23. Sept. 2019 um 18:10 Uhr schrieb marco checl-mk marcocheckmk2005@gmail.com:
Dear All,
We are trying to monitor qlogic sanbox devices via SNMP. If I do a manual snmpwalk or bulksnmpwalk , I can see a lot of information but when I configure it in check mk it only shows
few checks like:
interface
SNMP info
Check mk
It does not show any information about Fibre channel port , temperature sensors etc but I can manually get the OID’s value.
Has anybody else faced this problem?
We are using checkmk 1.2.6p15.
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
Manage your subscription or unsubscribe
https://lists.mathias-kettner.de/cgi-bin/mailman/listinfo/checkmk-en