-
Notifications
You must be signed in to change notification settings - Fork 53
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
Juniper BGP monitoring #252
Comments
Hi @SnDsound , first of all, thanks for your detailed explanation! When you define an We will try to study the case and find a possible solution! To be sure if I understand your issue and to summarise it:
In your example:
The attached metrics will use the IDX1 indexes to get the values, as you attached on your logs, it is trying to query
And your desired behaviour is
|
Hi @sbengo, Thanks for prompt response. Yes, I wan't to use IndexOID vaule, as index for next queries. In this case:
This is for this case. Your explanation is ok, and BaseOID + VAL1 will cover this topic.
I had similar topic when I wanted to monitor resources on Cisco 9006 device (IOS-XR). Please look at this topic: https://supportforums.cisco.com/document/73251/monitoring-cpu-utilization-ios-xr-based-platforms-using-snmp-tools, especially at Fabrice Ducomble post. After you get the index for each card:
You need to take index, put in in the middle, and at the end define numeric type. In this case 1 will represent other type of memory, 2 will be for processorMemory, 6 for multibusMemory, etc.
1:other
Regards, |
The @SnDsound most requested feature would also greatly fix some of my problems. All of the above comes down generally to have an option to use $VAL1 from IndexOID as index for queries. Any chance of implementing that? |
Are there any chances to implement this? |
Hi @pavleec, rigth now, he have no time enough, but we have plans to implement ASAP. |
+1 |
Hi @toni-moreno, Any news about implementation? |
Hello guys, First of all, sorry for the delayed response! We detected 2 needs on this issue: $VAL1 as indexAs you described quite well, @SnDsound , the first implementation would be set up the $VAL1 as the real index. Index suffix (single and mapped)Both cases, the BGP and the Cisco Enhanced seems to have a suffix on the metric query: This suffix breaks the way that SNMPCollector maps the metric query result with the indexed ones: it is expected that both walks have the same index, the measurement and metric ones. Example:
Implementing this would produce several changes on code (without breaking the existent one), so we have no foresight to implement it! Thanks, |
I think this is similar issue, but I have QoS RED drops for best-effort I would like to capture, but there is an interface index in the middle. In example below is interface index 593. how snmp mib walk jnxCosIfqTotalRedDropPkts ascii | grep 593 Anyway I could get that if you implement this feature? |
Hi @sbengo / @toni-moreno Do you have plans to implement mentioned functionalities?
Regards, |
Hello @SnDsound , We have recently updated wth 2 new measurement types:
Feel free to test if you can now query data as you need. |
Hi,
I'm trying to create measurement for BGP prefixes for Juniper products, but I stuck.
Maybe I don't know how to create this kind of measurements, or it's not possible to do this right now.
Base OID which should be used as index is regarding to Juniper documentation is: .1.3.6.1.4.1.2636.5.1.1.2.1.1.1.14
Output for this is:
So we have after .14:
10.1 - I don't know what it is
172.18.3.25 - Source IP
1 - I don't know what it is
172.18.3.26 - Destination IP
As value for particular index we have 4 or 5, which is a Juniper "index value" used for other things.
Then for example I would like to have number of received prefixes.
I should use value from jnxBgpM2PeerIndex, to get number of prefixes:
So I've created 2 SNMP Metrics:
jnxBgpM2PeerIndex - .1.3.6.1.4.1.2636.5.1.1.2.1.1.1.14
jnxBgpM2PrefixInPrefixes - .1.3.6.1.4.1.2636.5.1.1.2.6.2.1.7
Then Influx Measurements, where I'm getting Destination IP as TAG:
![juniper bgp](https://user-images.githubusercontent.com/12694268/29038644-bcb2a70e-7ba8-11e7-98fd-7b3e42a871f7.png)
But my table is not working as I expected. I have BGP peer IP, jnxBgpM2PeerIndex from SNMP, but there is no match for number of prefixes.
SNMP Collector is always forwarding index from jnxBgpM2PeerIndex to jnxBgpM2PrefixInPrefixes
I've tried to use direct / indirect TAG, change IndexAsValue to true/false, but result is always the same.
How can I build this kind of measurement?
Best regards,
Peter
The text was updated successfully, but these errors were encountered: