I think I can produce cumulative patch for that ('old' will be 087e+PA). Anybody interested?toe_cutter wrote:But what i meant was that on the 1225 bug there is like 7 patches, further down links to 4 more bugs, at least 2 of them have more patches and more links to other bugs and so forth, its hard keeping track of what i need
The first patch i tried from 1225 also failed on the dry-run :/
Cisco SFP (with DOM) Optical value plugin v0.2.3 + 0.2.4b
Moderators: Developers, Moderators
-
- Cacti User
- Posts: 168
- Joined: Fri Sep 12, 2008 2:41 am
- Location: Sweden
Try this patch. It should cover all pathes in 1225 and related.toe_cutter wrote:I am!BorisL wrote:I think I can produce cumulative patch for that ('old' will be 087e+PA). Anybody interested?
Pure SNMP is always preferable!
- Attachments
-
- issue1225.full.patch
- issue1225 cummulative patch
- (12.67 KiB) Downloaded 428 times
-
- Cacti User
- Posts: 168
- Joined: Fri Sep 12, 2008 2:41 am
- Location: Sweden
Thanks a lot!BorisL wrote:Try this patch. It should cover all pathes in 1225 and related.
However a chunk of the data_query patch failed, attached is the reject. I did manage to patch it manually, im not sure what failed really...
Something i noted with the graph template, the |query_entSensorScale| variable-name is displayed in the graphs when there is no value to display. I suppose this is a feature for 0.8.8 tho.
Other than this, it works great, thanks
- Attachments
-
- data_query.php.rej.txt
- (10.81 KiB) Downloaded 308 times
It seems you have patched 087e, aroundtoe_cutter wrote:However a chunk of the data_query patch failed, attached is the reject. I did manage to patch it manually, im not sure what failed really...
Code: Select all
- /* correct bogus index value */
- /* found in some devices such as an EMC Cellera */
- if ($snmp_index == 0) {
- $snmp_index = 1;
- }
Nope, that is not a feature of 088. Can you show situation when entSensorScale is not set? It seems it should be for every sensor.toe_cutter wrote:Something i noted with the graph template, the |query_entSensorScale| variable-name is displayed in the graphs when there is no value to display. I suppose this is a feature for 0.8.8 tho.
-
- Cacti User
- Posts: 168
- Joined: Fri Sep 12, 2008 2:41 am
- Location: Sweden
Afaik i only have the latest 087e patches, and pia2.5.BorisL wrote:It seems you have patched 087e, aroundtoe_cutter wrote:However a chunk of the data_query patch failed, attached is the reject. I did manage to patch it manually, im not sure what failed really...Code: Select all
- /* correct bogus index value */ - /* found in some devices such as an EMC Cellera */ - if ($snmp_index == 0) { - $snmp_index = 1; - }
But cacti seems fully functional anyway, so...
Nvm about this, i had a broken line in your cisco-sensors.xml after copy-paste, right at the 9th exponent unit, removed the linebreak and added the missing space between the quotation marks. Its working now.BorisL wrote:Nope, that is not a feature of 088. Can you show situation when entSensorScale is not set? It seems it should be for every sensor.toe_cutter wrote:Something i noted with the graph template, the |query_entSensorScale| variable-name is displayed in the graphs when there is no value to display. I suppose this is a feature for 0.8.8 tho.
Thanks again for the patch and snmp-templates
Hi BorisL,BorisL wrote:This version is affected for sure, I have a couple of themFirstLast wrote:Hi Boris,
do you know which firmware versions are affected with it ?
I run : s72033-adventerprisek9_wan-mz.122-33.SXI2.bin
which is one of very recent versions.
I was unable to recreate this problem the way you described it meaning that I can read DOM using sub-slot syntax after re-insert or reboot.
Regarding SNMP reading, Cisco told me it is expected behavior and suggested to search for Power Sensor :
The ES+ line cards use the ‘show interface trans’ command while the SIP cards use the ‘show hw-module subslot’ command.
The example I have is the following search power outputs:
Router#sh hw-module sub 8/0 transc 0 s
The Transceiver in slot 8 subslot 0 port 0 is enabled.
Module temperature = +40.148 C
Transceiver Tx supply voltage = 3252.3 uVolts
Transceiver Tx bias current = 14152 uAmps
Transceiver Tx power = -11 dBm <-------
Transceiver Rx optical power = -14 dBm <-------
Router#
!search for Power sensor
bash-2.05b$ snmpwalk -v2c -c public 1.88.13.3 47.1.1.1.1.2 | grep 'subslot 8/0' | grep Power
47.1.1.1.1.2.3097 = "subslot 8/0 transceiver 0 Tx Power Sensor"
47.1.1.1.1.2.3098 = "subslot 8/0 transceiver 0 Rx Power Sensor"
!retrieve value
bash-2.05b$ snmpwalk -v2c -c public 1.88.13.3 enterprises.9.9.91.1.1.1.1.4 | grep 3097
enterprises.9.9.91.1.1.1.1.4.3097 = -11
bash-2.05b$ snmpwalk -v2c -c public 1.88.13.3 enterprises.9.9.91.1.1.1.1.4 | grep 3098
enterprises.9.9.91.1.1.1.1.4.3098 = -14
Would anybody know how to modify that SNMP Walk which is parsing and expects to return 14 if dBm found to also parse sub-slots and look for Power Sensor, then get their values as described above ?
Regards
My SNMP query grabs every sensor available and only then tries to lookup for it's name in inventory MIB. So it should be usable for you.FirstLast wrote:Would anybody know how to modify that SNMP Walk which is parsing and expects to return 14 if dBm found to also parse sub-slots and look for Power Sensor, then get their values as described above ?
Patch in windows
Hi
How can I do to patch in windows__
Regards,
How can I do to patch in windows__
Regards,
Hi BorisL,
nice work !
I have a problem though.
After applying the issue1225.full.patch successfully I still receive :
Any thoughts ?
nice work !
I have a problem though.
After applying the issue1225.full.patch successfully I still receive :
Code: Select all
+ Running data query [22].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/var/www/html/resource/snmp_queries/cisco_sensors.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.9.9.91.1.1.1.1.1'
+ No SNMP data returned
+ Found data query XML file at '/var/www/html/resource/snmp_queries/cisco_sensors.xml'
+ Found data query XML file at '/var/www/html/resource/snmp_queries/cisco_sensors.xml'
+ Found data query XML file at '/var/www/html/resource/snmp_queries/cisco_sensors.xml'
Cacti user
I figured it out - SNMP Timeout has to be increased about 6000-10000 ms.
In spite of that I have another problem:
When I graph a sensor, there is no graph showing at all (No such file or directory) and after investigation I found in data sources :
Do you have any ideas ?
In spite of that I have another problem:
When I graph a sensor, there is no graph showing at all (No such file or directory) and after investigation I found in data sources :
Code: Select all
Index Type Data query data sources must be created through New Graphs.
Index Value
Output Type ID Data query data sources must be created through New Graphs.
Cacti user
Re: Cisco SFP (with DOM) Optical value plugin v0.2.3 + 0.2.4
I've modified the script to allow graphing of interfaces other than the TenGigabitEthernet ports on the Supervisor cards.
I have a number of interfaces Ten and GigEthernet on SPAs which were showing up as "subslot", so I applied the following changes to get this working:
This is what it looks like when you add the graphs in Cacti:
Here are the files:
I have a number of interfaces Ten and GigEthernet on SPAs which were showing up as "subslot", so I applied the following changes to get this working:
- Changed for example 'subslot 3/0 transceiver 8 Rx Power Sensor' to be '3/0/8'
- Checked that an interface called either TenGigabitEthernet3/0/8 or GigabitEthernet3/0/8 exists in Cacti host_snmp_cache and select
- Replaced colons ":" in the ifAlias because the script server explodes these as returned variables
- Introduced a "divisor" to work around the Cisco oddness of returning the dBM for the SUP card's interface e.g. Ten7/1 in 1/10ths and the values for say Gig2/0/1 as a rounded-to-a-whole number.
This is what it looks like when you add the graphs in Cacti:
Here are the files:
Re: Cisco SFP (with DOM) Optical value plugin v0.2.3 + 0.2.4
Thanks for you help (and also thank you for sharing)ahouston wrote:I've modified the script to allow graphing of interfaces other than the TenGigabitEthernet ports on the Supervisor cards.
...
All the problems of the world could be settled if people were only willing to think...
-
- Cacti User
- Posts: 168
- Joined: Fri Sep 12, 2008 2:41 am
- Location: Sweden
Re: Cisco SFP (with DOM) Optical value plugin v0.2.3 + 0.2.4
Awesome! We got a ton of interfaces that show as "subslot" aswell, but i hadnt gotten around to editing the script (not sure how i would apply it either)ahouston wrote:I've modified the script to allow graphing of interfaces other than the TenGigabitEthernet ports on the Supervisor cards.
I have a number of interfaces Ten and GigEthernet on SPAs which were showing up as "subslot", so I applied the following changes to get this working:
Thanks for sharing!
Who is online
Users browsing this forum: No registered users and 2 guests