it’s not “broken” in the sense that CSCO officially considers multicontext snmp the “by-design” method (and I have the TAC cases to prove it).
remember, snmp *works* which means it’s for grouchy old [grey|neck]beards.
netconf & shiny-api-disaster-of-the-week are supposed to rule the new agile! world! of! devops! ( *gag* )
not just ASRs … for instance, it’s the same thing (multicontext snmp hell) with VRFs on n7k’s.
so, it’s a “feature” not a “bug”
smh
R.
On Jan 13, 2016, at 07:00, observium-request@observium.org wrote:
Because the MIB is broken and doesn?t have any concept of VRF awareness.
The workaround that I used on my ASR9Ks was to create a different context for the VRF in question.
This config example basically treats the vrf Inetv4 as the default vrf when polling with community blahpoo. It only applies to that community. I have non-contextual communities to catch my default stuff, i.e. my MP-BGP underpinnings.
It?s not ideal because you need to create two of the same device in Observium; one for each community (vrf and non-vrf), but it sucks less than the alternative, which is to not have this functionality at all.
! snmp-server vrf Inetv4 context BGPVRF ! snmp-server context BGPVRF snmp-server community-map blahpoo context BGPVRF snmp-server community blahpoo RO MANAGEMENT !
http://postman.memetic.org/pipermail/observium/2015-June/010467.html http://postman.memetic.org/pipermail/observium/2015-June/010467.html
My question wasn't Cisco specific, seeing the same on HP (h3c) gear
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> on behalf of Rob VanHooren <rob_vanhooren@mac.commailto:rob_vanhooren@mac.com> Reply-To: "observium@observium.orgmailto:observium@observium.org" <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, 13 January 2016 at 12:26 To: "observium@observium.orgmailto:observium@observium.org" <observium@observium.orgmailto:observium@observium.org> Subject: [Observium] itsafeaturenotabug (was re: routing tab)
it's not "broken" in the sense that CSCO officially considers multicontext snmp the "by-design" method (and I have the TAC cases to prove it).
remember, snmp *works* which means it's for grouchy old [grey|neck]beards.
netconf & shiny-api-disaster-of-the-week are supposed to rule the new agile! world! of! devops! ( *gag* )
not just ASRs ... for instance, it's the same thing (multicontext snmp hell) with VRFs on n7k's.
so, it's a "feature" not a "bug"
smh
R.
On Jan 13, 2016, at 07:00, observium-request@observium.orgmailto:observium-request@observium.org wrote:
Because the MIB is broken and doesn?t have any concept of VRF awareness.
The workaround that I used on my ASR9Ks was to create a different context for the VRF in question.
This config example basically treats the vrf Inetv4 as the default vrf when polling with community blahpoo. It only applies to that community. I have non-contextual communities to catch my default stuff, i.e. my MP-BGP underpinnings.
It?s not ideal because you need to create two of the same device in Observium; one for each community (vrf and non-vrf), but it sucks less than the alternative, which is to not have this functionality at all.
! snmp-server vrf Inetv4 context BGPVRF ! snmp-server context BGPVRF snmp-server community-map blahpoo context BGPVRF snmp-server community blahpoo RO MANAGEMENT !
http://postman.memetic.org/pipermail/observium/2015-June/010467.html
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL.
Kelway (UK) Ltd is a Company registered in England and Wales. This email is sent for and on behalf of Kelway Holdings Limited. Kelway Holdings Limited is the UK holding company for Kelway (UK) Limited trading as Kelway. The registered office for Kelway Holdings Limited (Company Number 05872067) and its UK group undertakings is 10 Fleet Place, London, EC4M 7RB. VAT Registration 902 1949 39. Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than Kelway or the sender of its existence.
For more information about Kelway please visit www.kelway.co.uk
Same thing, if the H3C gear speaks BGP4-MIB, your VRF sessions won't be in it (else they'd be displayed in Observium)...
On 2016-01-13 13:40, Serghei Golipad wrote:
My question wasn’t Cisco specific, seeing the same on HP (h3c) gear
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> on behalf of Rob VanHooren <rob_vanhooren@mac.com mailto:rob_vanhooren@mac.com> Reply-To: "observium@observium.org mailto:observium@observium.org" <observium@observium.org mailto:observium@observium.org> Date: Wednesday, 13 January 2016 at 12:26 To: "observium@observium.org mailto:observium@observium.org" <observium@observium.org mailto:observium@observium.org> Subject: [Observium] itsafeaturenotabug (was re: routing tab)
it’s not “broken” in the sense that CSCO officially considers multicontext snmp the “by-design” method (and I have the TAC cases to prove it).
remember, snmp *works* which means it’s for grouchy old [grey|neck]beards.
netconf & shiny-api-disaster-of-the-week are supposed to rule the new agile! world! of! devops! ( *gag* )
not just ASRs … for instance, it’s the same thing (multicontext snmp hell) with VRFs on n7k’s.
so, it’s a “feature” not a “bug”
smh
R.
On Jan 13, 2016, at 07:00, observium-request@observium.org mailto:observium-request@observium.org wrote:
Because the MIB is broken and doesn?t have any concept of VRF awareness.
The workaround that I used on my ASR9Ks was to create a different context for the VRF in question.
This config example basically treats the vrf Inetv4 as the default vrf when polling with community blahpoo. It only applies to that community. I have non-contextual communities to catch my default stuff, i.e. my MP-BGP underpinnings.
It?s not ideal because you need to create two of the same device in Observium; one for each community (vrf and non-vrf), but it sucks less than the alternative, which is to not have this functionality at all.
! snmp-server vrf Inetv4 context BGPVRF ! snmp-server context BGPVRF snmp-server community-map blahpoo context BGPVRF snmp-server community blahpoo RO MANAGEMENT !
http://postman.memetic.org/pipermail/observium/2015-June/010467.html
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL.
Kelway Ltd is a Company registered in England and Wales. This email is sent for and on behalf of Kelway Holdings Limited. Kelway Holdings Limited is the UK holding company for Kelway Limited trading as Kelway. The registered office for Kelway Holdings Limited (Company Number 05872067) and its UK group undertakings is 10 Fleet Place, London, EC4M 7RB. VAT Registration 902 1949 39. Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than Kelway or the sender of its existence.
For more information about Kelway please visit www.kelway.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Rob VanHooren -
Serghei Golipad -
Tom Laermans