Data query for CMCIII_PDU : Index problem
Moderators: Developers, Moderators
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Data query for CMCIII_PDU : Index problem
Hi,
I'm experiencing a new issue with my network monitoring.
I'd like to graph my cmcIII PDU facilities.
For that, I have to create an XML file with the index and the OID's.
First, I've found the table (RITTAL-CMC-III-MIB::cmcIIIVarTable) as it appears in the attached file.
The first thing is that i don't find any index in the table.
I've found the MIB on the Internet (http://www.mibdepot.com/cgi-bin/getmib3 ... IIVarTable) and found this index: 1.3.6.1.4.1.2606.7.4.2.2.1
I use this Index in my XML file.
My query verbose works in Cacti. (cf attached)
But when I click on "create graph for...", i've got a list of value in the column "Index"...
Then, I try to add the table colums that i've choose (cmcIIIVarName and cmcIIIVarValueInt)
I had those 2 entries in the XML file but when turn on the verbose query, I don't see any change.
I guess there is a problem with the Index, table, etc but can't see where.
If someone have any clue, it's more than welcome !
thanks
I'm experiencing a new issue with my network monitoring.
I'd like to graph my cmcIII PDU facilities.
For that, I have to create an XML file with the index and the OID's.
First, I've found the table (RITTAL-CMC-III-MIB::cmcIIIVarTable) as it appears in the attached file.
The first thing is that i don't find any index in the table.
I've found the MIB on the Internet (http://www.mibdepot.com/cgi-bin/getmib3 ... IIVarTable) and found this index: 1.3.6.1.4.1.2606.7.4.2.2.1
I use this Index in my XML file.
My query verbose works in Cacti. (cf attached)
But when I click on "create graph for...", i've got a list of value in the column "Index"...
Then, I try to add the table colums that i've choose (cmcIIIVarName and cmcIIIVarValueInt)
I had those 2 entries in the XML file but when turn on the verbose query, I don't see any change.
I guess there is a problem with the Index, table, etc but can't see where.
If someone have any clue, it's more than welcome !
thanks
- Attachments
-
- query verbose
- Sélection_189.jpg (332.7 KiB) Viewed 2981 times
-
- snmp_table
- Sélection_187.jpg (218.93 KiB) Viewed 2981 times
-
- XML_file
- Sélection_188.jpg (39 KiB) Viewed 2981 times
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
Here is an update of my post.
A screenshot of the MIB table I've used.
A screenshot of the MIB table I've used.
- Attachments
-
- MIB_table
- Sélection_192.jpg (222.83 KiB) Viewed 2975 times
Re: Data query for CMCIII_PDU : Index problem
Looks like you didnt choose a correct index. Notice cacti stated there are 22K items? far too many for a normal device.
Try 1.3.6.1.4.1.2606.7.4.2.2.1.1 Actually, post an snmpwalk of 1.3.6.1.4.1.2606.7.4.2.2.1.1? Does it look like sane data?
Try 1.3.6.1.4.1.2606.7.4.2.2.1.1 Actually, post an snmpwalk of 1.3.6.1.4.1.2606.7.4.2.2.1.1? Does it look like sane data?
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
Hi,
Yeah, i guess that has something to do with a bad index.
I tried with the one you adviced me :
#snmpwalk -v 2c -c public DEVICE_IP 1.3.6.1.4.1.2606.7.4.2.2.1.1#
that returns me : "No Such Object available on this agent at this OID"
It works with 1.3.6.1.4.1.2606.7.4.2.2.1 but returns me thousand of informations.
thanks
(I've have some updates that I'll post as soon as I've sorted it out)
Yeah, i guess that has something to do with a bad index.
I tried with the one you adviced me :
#snmpwalk -v 2c -c public DEVICE_IP 1.3.6.1.4.1.2606.7.4.2.2.1.1#
that returns me : "No Such Object available on this agent at this OID"
It works with 1.3.6.1.4.1.2606.7.4.2.2.1 but returns me thousand of informations.
thanks
(I've have some updates that I'll post as soon as I've sorted it out)
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
So this is my update.
I'd evolved my XML file (see the attachement)
But when I choose the output direction for the OID cmcIIIVarValueInt, (the one I guess I need to graph) it desapears from the column of the "create graph" page. (cf attachement)
I've to say I'm a bit confused with this.
I've created a graph template (CMCIII_PDUVarTable) with 2 data sources (VarValueInt and VarValueStr)
Does it mean that I'll have to make a graph for each plug ???
I've to graph 20 PDU with 8 plugs each and that won't be easy at all !
But one thing at a time ; first try to resolve my index problem !
I'd evolved my XML file (see the attachement)
But when I choose the output direction for the OID cmcIIIVarValueInt, (the one I guess I need to graph) it desapears from the column of the "create graph" page. (cf attachement)
I've to say I'm a bit confused with this.
I've created a graph template (CMCIII_PDUVarTable) with 2 data sources (VarValueInt and VarValueStr)
Does it mean that I'll have to make a graph for each plug ???
I've to graph 20 PDU with 8 plugs each and that won't be easy at all !
But one thing at a time ; first try to resolve my index problem !
- Attachments
-
- XML file
- Sélection_171.jpg (147.09 KiB) Viewed 2949 times
-
- Create Graph
- Sélection_172.jpg (159.74 KiB) Viewed 2949 times
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
Hi,
another update.
When i do a #snmpwalk -v 1 -c public -On DEVICE_IP RITTAL-CMC-III-MIB::cmcIIIVarTable|less#
I get this : (just an extract...)
#.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.1 = STRING: Temperature.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.2 = STRING: Temperature.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.3 = STRING: Temperature.Offset
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.4 = STRING: Temperature.SetPtHighAlarm
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.5 = STRING: Temperature.SetPtHighWarning
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.6 = STRING: Temperature.SetPtLowWarning
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.7 = STRING: Temperature.SetPtLowAlarm
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.8 = STRING: Temperature.Hysteresis
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.9 = STRING: Temperature.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.10 = STRING: Temperature.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.11 = STRING: Access.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.12 = STRING: Access.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.13 = STRING: Access.Sensitivity
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.14 = STRING: Access.Delay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.15 = STRING: Access.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.16 = STRING: Access.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.17 = STRING: Input 1.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.18 = STRING: Input 1.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.19 = STRING: Input 1.Logic
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.20 = STRING: Input 1.Delay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.21 = STRING: Input 1.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.22 = STRING: Input 1.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.23 = STRING: Input 2.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.24 = STRING: Input 2.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.25 = STRING: Input 2.Logic
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.26 = STRING: Input 2.Delay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.27 = STRING: Input 2.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.28 = STRING: Input 2.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.29 = STRING: Output.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.30 = STRING: Output.Relay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.31 = STRING: Output.Logic
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.32 = STRING: Output.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.33 = STRING: Output.Category
#
This would mean that my index is .1.3.6.1.4.1.2606.7.4.2.2.1.3.1 and not .1.3.6.1.4.1.2606.7.4.2.2.1.2.1 right ?
But the MIB says that .1.3.6.1.4.1.2606.7.4.2.2.1.3.1 is cmcIIIVarName and that the index is 1.3.6.1.4.1.2606.7.4.2.2.1 (cmcIIIVarEntry)
...I'm loosing it, really.
I promise my eternal gratitude to the one(s) will help me to sort it out !
another update.
When i do a #snmpwalk -v 1 -c public -On DEVICE_IP RITTAL-CMC-III-MIB::cmcIIIVarTable|less#
I get this : (just an extract...)
#.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.1 = STRING: Temperature.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.2 = STRING: Temperature.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.3 = STRING: Temperature.Offset
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.4 = STRING: Temperature.SetPtHighAlarm
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.5 = STRING: Temperature.SetPtHighWarning
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.6 = STRING: Temperature.SetPtLowWarning
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.7 = STRING: Temperature.SetPtLowAlarm
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.8 = STRING: Temperature.Hysteresis
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.9 = STRING: Temperature.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.10 = STRING: Temperature.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.11 = STRING: Access.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.12 = STRING: Access.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.13 = STRING: Access.Sensitivity
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.14 = STRING: Access.Delay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.15 = STRING: Access.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.16 = STRING: Access.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.17 = STRING: Input 1.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.18 = STRING: Input 1.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.19 = STRING: Input 1.Logic
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.20 = STRING: Input 1.Delay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.21 = STRING: Input 1.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.22 = STRING: Input 1.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.23 = STRING: Input 2.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.24 = STRING: Input 2.Value
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.25 = STRING: Input 2.Logic
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.26 = STRING: Input 2.Delay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.27 = STRING: Input 2.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.28 = STRING: Input 2.Category
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.29 = STRING: Output.DescName
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.30 = STRING: Output.Relay
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.31 = STRING: Output.Logic
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.32 = STRING: Output.Status
.1.3.6.1.4.1.2606.7.4.2.2.1.3.1.33 = STRING: Output.Category
#
This would mean that my index is .1.3.6.1.4.1.2606.7.4.2.2.1.3.1 and not .1.3.6.1.4.1.2606.7.4.2.2.1.2.1 right ?
But the MIB says that .1.3.6.1.4.1.2606.7.4.2.2.1.3.1 is cmcIIIVarName and that the index is 1.3.6.1.4.1.2606.7.4.2.2.1 (cmcIIIVarEntry)
...I'm loosing it, really.
I promise my eternal gratitude to the one(s) will help me to sort it out !
Re: Data query for CMCIII_PDU : Index problem
hmm doesnt look like this device implements snmp in a standard manor Cacti likes. Given the output above, I'd expect if you snmpwalked .1.3.6.1.4.1.2606.7.4.2.2.1.3.1.2, you would get the current temp value. This does not happen, correct?
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
When I snmpwalk .1.3.6.1.4.1.2606.7.4.2.2.1.3.1.2, I get the string "Temperature.Value".
So you think that my device can't be graphed into cacti ?
I'll try to get in touch with my Rittal dealer to get more information about this issue
Thanks again for your help anyway.
So you think that my device can't be graphed into cacti ?
I'll try to get in touch with my Rittal dealer to get more information about this issue
Thanks again for your help anyway.
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
When I snmpwalk .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.2 , I get the temperature value "SNMPv2-SMI::enterprises.2606.7.4.2.2.1.11.1.2 = INTEGER: 2860"
Re: Data query for CMCIII_PDU : Index problem
ah-ha! nice. 1.3.6.1.4.1.2606.7.4.2.2.1.11 = cmcIIIVarValueInt Tree.
So now if you switch the index in the data query to .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.2, you'll get a better list for Cacti. Although, you're going to need to be mindful how you build the data query for the 5 fields.
So now if you switch the index in the data query to .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.2, you'll get a better list for Cacti. Although, you're going to need to be mindful how you build the data query for the 5 fields.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
Thanks BSOD2600 for your precious help !
So i switched index to .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.2 and I get just one value in the "data query" filed on the "create graph" page. (cf attachement1)
When I try with the Index .1.3.6.1.4.1.2606.7.4.2.2.1.11.1, I get all the values I need. (cf attachement2)
I'll try to deal with it but my question is how I can graph those values if they are the Index !!!!????
Do I have to use this OID again ( .1.3.6.1.4.1.2606.7.4.2.2.1.11.1) in my XML file with the output direction?
I'll try this today and let you know.
thanks again.
So i switched index to .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.2 and I get just one value in the "data query" filed on the "create graph" page. (cf attachement1)
When I try with the Index .1.3.6.1.4.1.2606.7.4.2.2.1.11.1, I get all the values I need. (cf attachement2)
I'll try to deal with it but my question is how I can graph those values if they are the Index !!!!????
Do I have to use this OID again ( .1.3.6.1.4.1.2606.7.4.2.2.1.11.1) in my XML file with the output direction?
I'll try this today and let you know.
thanks again.
- Attachments
-
- attachement1
- Sélection_173.jpg (26.62 KiB) Viewed 2899 times
-
- attachement2
- Sélection_174.jpg (22.3 KiB) Viewed 2899 times
Re: Data query for CMCIII_PDU : Index problem
When troubleshooting a new data query, its very helpful for discussion to post snmpwalks and Verbose Query outputs. Additionally, since you have the vendors MIB file, have snmpwalk load it so it'll parse the output correctly which will make understanding the output much easier (use the +m <mibname> option).
What do you have in the XML file currently?
Have you followed http://docs.cacti.net/manual:088:3a_adv ... alkthrough at all?
What do you have in the XML file currently?
Have you followed http://docs.cacti.net/manual:088:3a_adv ... alkthrough at all?
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
Yes, i've followed this link to the Cacti manual to create my data query after an XML file.
These are the troubleshooting information : the snmpwalk, the XML and the verbose.
I was thinking about something in my morning shower !
I should try to use these OID .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.2 , .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.3 , etc. in my XML file with the output direction for the graphs values.
I'll try this today and see if it does any good.
thanks anyway, looking forward your smart advices !
; )
These are the troubleshooting information : the snmpwalk, the XML and the verbose.
I was thinking about something in my morning shower !
I should try to use these OID .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.2 , .1.3.6.1.4.1.2606.7.4.2.2.1.11.1.3 , etc. in my XML file with the output direction for the graphs values.
I'll try this today and see if it does any good.
thanks anyway, looking forward your smart advices !
; )
- Attachments
-
- snmpwalk
- Sélection_176.jpg (152.59 KiB) Viewed 2881 times
-
- XML file
- Sélection_175.jpg (61.56 KiB) Viewed 2881 times
-
- Verbose query
- Sélection_177.jpg (202.22 KiB) Viewed 2881 times
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
UPDATE :
So I tried to use SNMPv2-SMI::enterprises.2606.7.4.2.2.1.11.1.2, SNMPv2-SMI::enterprises.2606.7.4.2.2.1.11.1.3 as OIDs to graph (cf attachment with my XML file)
I also put part of the verbose and the "create graph" page that doesn't show any good...
So I tried to use SNMPv2-SMI::enterprises.2606.7.4.2.2.1.11.1.2, SNMPv2-SMI::enterprises.2606.7.4.2.2.1.11.1.3 as OIDs to graph (cf attachment with my XML file)
I also put part of the verbose and the "create graph" page that doesn't show any good...
- Attachments
-
- XML file
- Sélection_178.jpg (76.57 KiB) Viewed 2881 times
-
- verbose part2
- Sélection_181.jpg (93.3 KiB) Viewed 2881 times
-
- verbose part1
- Sélection_180.jpg (111.02 KiB) Viewed 2881 times
-
- create graph
- Sélection_179.jpg (48.77 KiB) Viewed 2881 times
-
- Posts: 41
- Joined: Thu Jun 04, 2015 11:36 am
- Location: France
Re: Data query for CMCIII_PDU : Index problem
Maybe I should try with a REGEX ?
I really don't what it is or how it works but i'll investigate.
I've seen that is used when the SNMP index doesn't exist...
I really don't what it is or how it works but i'll investigate.
I've seen that is used when the SNMP index doesn't exist...
Who is online
Users browsing this forum: No registered users and 2 guests