Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
scruboy01 wrote:I'm getting an "ERROR: Empty result" message using the files from 65xx_sfp.zip.
[...]
I can manually run the script and I will get the correct result.
at which user is the script run when it succeeds ? and and as which user is it run by cacti?
if you look at the poller cache look things oke?
when you run things in verbose mode in devices look things oke?
my 2 cents
All the problems of the world could be settled if people were only willing to think...
Hi,
thank you for sharing this plugin. This is very important for the network I support. Unfortunately I have the following issues:
1) The levels for GigabitEthernet interfaces are not visible and I got "nan" on the graphs, although via cli there are values in the output
2) For ES+ modules on cisco 7609 routers the Tengigabitethernet interfaces are fine, but for ES modules, the values are multiplied by 10(if the optic level is 3.4, the value on the graph is depicted as 34). I know this is due to the way cisco devices reply to snmp queries for this type of modules. This is not a great problem, but it is present anyway.
Hi,
thank you for your answer. The CDEF is an option and it's not a big deal to make it work.
The more serious problem I can't understand right now is related to the GigabitEthernet interfaces, for which I don't see any values (both Es and ES+ modules)
I wasn't quite correct in my previous post. Please take into consideration the following statements:
1)With SNMPwalk with the same OIDs for both Es and ES+ card, for both TenGigabit and Gigabit interfaces, the values are visible and correct.
2)At the same time with the php script I can see values only for TenGigabitEthernet interfaces
Output from CLOG:
10/25/2011 01:50:07 PM - SPINE: Poller[0] Host[8] Description[router1] TH[1] DS[40] Graphs['router1 SFP GigabitEthernet9/3 - router1_Gi9/3-router2_Gi1/48'] SS[0] SERVER: /var/www/cacti/scripts/ss_65xx_sfp.php ss_sfp x.x.x.x 8 2:161:500:1:40:xxxxxxxxxxxxxx:::::: get tx GigabitEthernet9/3, output: U
If you have any explanation, it will be great, because I don't see a difference in the OIDs and at first glance a restriction int the script only for TenGigabit interfaces. The Gigabit interfaces are discovered, but after creating the graph, you see no results(just nan). Has the script been tested with GigabitEthernet interfaces before?
regards,
georgi
Last edited by bakkapo on Fri Oct 28, 2011 12:14 pm, edited 1 time in total.
If you have any explanation, it will be great, because I don't see a difference in the OIDs and at first glance a restriction int the script only for TenGigabit interfaces. The Gigabit interfaces are discovered, but after creating the graph, you see no results(just nan). Has the script been tested with GigabitEthernet interfaces before?
Have you done the steps by hand to see if the Cisco is willing to answer (and have you check that you do not have too restricted views on the Cisco)?
Sodium
All the problems of the world could be settled if people were only willing to think...
Do you get values from the cisco cli from these gigabit interfaces?
The SFP (and the interface i think) has to support the DOM feature to get any values.
from CLI there is no problem
show int Gix/x/x tra
is working as charm. snmpwalk to the same interface (as I wrote above) is also fine. The only issue is when I try to use the cacti script (via cli or via GUI). Maybe I am missing something, but that's the effect I observe. If you have tested it with Gigabith interface as well, probably I should verify everything again and spend some more time testing and troubleshooting.
bakkapo wrote:
from CLI there is no problem
show int Gix/x/x tra
is working as charm. snmpwalk to the same interface (as I wrote above) is also fine. The only issue is when I try to use the cacti script (via cli or via GUI). Maybe I am missing something, but that's the effect I observe. If you have tested it with Gigabith interface as well, probably I should verify everything again and spend some more time testing and troubleshooting.
on what OID's are you reading the output of the SFP's?
In the script you see I first get the index -> then witht the index I read the specific OID needed to get the values (it'sno rocket science)
All the problems of the world could be settled if people were only willing to think...
sodium wrote:on what OID's are you reading the output of the SFP's?
In the script you see I first get the index -> then witht the index I read the specific OID needed to get the values (it'sno rocket science)
Maybe its a different output type, because of the difference in power metered on his ES modules and the gi-interfaces?
That could explain why he would get -20dBm instead of -2.0dBm? Since in the last script i posted (with the improved timings) before i print the result of a get i actually divide the result by 10.
I am using the same OIDs as those in the script and those I had found before trying to use cacti for monitoring of the optic levels. I don't have any GLS SFPs, so all of them have DOM. This is not the case.
Georgi
Last edited by bakkapo on Fri Oct 28, 2011 12:13 pm, edited 1 time in total.
bakkapo wrote:I am using the same OIDs as those in the script and those I had found before trying to use cacti for monitoring of the optic levels. I don't have any GLS SFPs, so all of them have DOM. This is not the case.
Georgi
Thanks for the output.
In the script, for debug purposes (im abroad without access to anything currently), below the last preg_match on line 179 but before the if-statement; Could you add these two lines:
If your using the script in cacti already, dont add these as it will break the graphs. Easier to copy the script and rename it if so.
subslot 1/0 transceiver 0 Tx Power Sensorsubslot 1/0 transceiver 0 Rx Power Sensorsubslot 1/0 transceiver 1 Tx Power Sensorsubslot 1/0 transceiver 1 Rx Power SensorTenGigabitEthernet2/1 Transmit Power SensorTenGigabitEthernet2/1 Receive Power SensorTenGigabitEthernet2/2 Transmit Power SensorTenGigabitEthernet2/2 Receive Power SensorGigabitEthernet5/1 Transmit Power SensorGigabitEthernet5/1 Receive Power SensorGigabitEthernet7/1 Transmit Power SensorGigabitEthernet7/1 Receive Power SensorGigabitEthernet7/2 Transmit Power SensorGigabitEthernet7/2 Receive Power SensorGigabitEthernet7/3 Transmit Power SensorGigabitEthernet7/3 Receive Power SensorGigabitEthernet8/1 Transmit Power SensorGigabitEthernet8/1 Receive Power SensorGigabitEthernet8/2 Transmit Power SensorGigabitEthernet8/2 Receive Power SensorGigabitEthernet8/3 Transmit Power SensorGigabitEthernet8/3 Receive Power SensorGigabitEthernet8/4 Transmit Power SensorGigabitEthernet8/4 Receive Power SensorGigabitEthernet8/5 Transmit Power SensorGigabitEthernet8/5 Receive Power SensorGigabitEthernet8/8 Transmit Power SensorGigabitEthernet8/8 Receive Power SensorGigabitEthernet8/9 Transmit Power SensorGigabitEthernet8/9 Receive Power SensorGigabitEthernet8/10 Transmit Power SensorGigabitEthernet8/10 Receive Power SensorGigabitEthernet8/11 Transmit Power SensorGigabitEthernet8/11 Receive Power SensorGigabitEthernet8/12 Transmit Power SensorGigabitEthernet8/12 Receive Power SensorGigabitEthernet8/13 Transmit Power SensorGigabitEthernet8/13 Receive Power SensorGigabitEthernet8/14 Transmit Power SensorGigabitEthernet8/14 Receive Power SensorGigabitEthernet8/15 Transmit Power SensorGigabitEthernet8/15 Receive Power SensorGigabitEthernet8/16 Transmit Power SensorGigabitEthernet8/16 Receive Power SensorGigabitEthernet8/17 Transmit Power SensorGigabitEthernet8/17 Receive Power SensorGigabitEthernet8/18 Transmit Power SensorGigabitEthernet8/18 Receive Power SensorGigabitEthernet8/19 Transmit Power SensorGigabitEthernet8/19 Receive Power SensorGigabitEthernet8/20 Transmit Power SensorGigabitEthernet8/20 Receive Power Sensorsubslot 9/0 transceiver 0 Tx Power Sensorsubslot 9/0 transceiver 0 Rx Power Sensorsubslot 9/0 transceiver 2 Tx Power Sensorsubslot 9/0 transceiver 2 Rx Power Sensorsubslot 9/0 transceiver 3 Tx Power Sensorsubslot 9/0 transceiver 3 Rx Power Sensorsubslot 9/0 transceiver 4 Tx Power Sensorsubslot 9/0 transceiver 4 Rx Power Sensorsubslot 9/0 transceiver 5 Tx Power Sensorsubslot 9/0 transceiver 5 Rx Power Sensorsubslot 9/0 transceiver 6 Tx Power Sensorsubslot 9/0 transceiver 6 Rx Power Sensorsubslot 9/0 transceiver 7 Tx Power Sensorsubslot 9/0 transceiver 7 Rx Power Sensorsubslot 9/0 transceiver 8 Tx Power Sensorsubslot 9/0 transceiver 8 Rx Power Sensorsubslot 9/0 transceiver 9 Tx Power Sensorsubslot 9/0 transceiver 9 Rx Power Sensorsubslot 9/0 transceiver 10 Tx Power Sensorsubslot 9/0 transceiver 10 Rx Power Sensorsubslot 9/0 transceiver 11 Tx Power Sensorsubslot 9/0 transceiver 11 Rx Power Sensorsubslot 9/0 transceiver 12 Tx Power Sensorsubslot 9/0 transceiver 12 Rx Power Sensorsubslot 9/0 transceiver 13 Tx Power Sensorsubslot 9/0 transceiver 13 Rx Power Sensorsubslot 9/0 transceiver 14 Tx Power Sensorsubslot 9/0 transceiver 14 Rx Power Sensorsubslot 9/0 transceiver 15 Tx Power Sensorsubslot 9/0 transceiver 15 Rx Power Sensorsubslot 9/0 transceiver 17 Tx Power Sensorsubslot 9/0 transceiver 17 Rx Power Sensorsubslot 9/0 transceiver 18 Tx Power Sensorsubslot 9/0 transceiver 18 Rx Power Sensorsubslot 9/0 transceiver 19 Tx Power Sensorsubslot 9/0 transceiver 19 Rx Power SensorTenGigabitEthernet3/21 Transmit Power SensorTenGigabitEthernet3/21 Receive Power SensorTenGigabitEthernet3/22 Transmit Power SensorTenGigabitEthernet3/22 Receive Power Sensor
I think it matches all types of interfaces:
ES+ modules :GigabitEthernet8/11 Transmit Power Sensor
ES+ modules: TenGigabitEthernet3/21 Receive Power Sensor
ES module: subslot 9/0 transceiver 9 Tx Power Sensor /GigabitEthernet interface
ES module: subslot 1/0 transceiver 1 Tx Power Sensor /TenGigabitEthernet interface