Hello guys,
I'm a new Zabbix user and this is my first post!
I'm having some trouble trying to discover SAPs on a 7750, and I didn't find anything in the forum, so I'm here asking for your help.
I loaded the certified Zabbix template for these devices, and I'm now able to discover a subset of the interfaces that are configured into the them.
The subset I'm referring to is made of those interfaces in the global-routing-table where you typically run OSPF/ISIS. But I use to have a lot of VRFs on the box ("vprn" in 7750 language), and none of their logical-interfaces gets discovered.
Those interfaces use SAPs, that are entities to map the interfaces themselves to a given port/vlan, e.g.:
In order to graph that interface counters, I have to poll the ifindex associated to its sap, which is not discovered by the standard IF::MIB.
The MIB to use should be "1.3.6.1.4.1.6527.3.1.2.4.3.2.1.5" instead, that gives you both the sap-index and the sap-description. Here is how the output looks like:
As you can see the sap-index is made up of three dot-separated numbers "100536.1342177283.86573058", and if I append this index to other 7750 sap-specific mibs I can get back the desired counters.
So I tried to create a discovery-rule based on SNMPv2, using a custom hey "net.sap.interfaces" and this SNMP-OID value:
I was expecting this rule to discover all the device's saps' indexes and their description, mappped to #SNMPINDEX and #SAPDESCR respectively, thus I created some item prototypes referring to those macros in order to have automatically created items:
Name: Key:
SAP {#SAPDESCR}: Bits received InProf net.sap.in.inProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.12.{#SNMPINDEX}]
SAP {#SAPDESCR}: Bits received OutProf net.sap.in.OutProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.14.{#SNMPINDEX}]
SAP {#SAPDESCR}: Bits sent InProf net.sap.out.inProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.20.{#SNMPINDEX}]
SAP {#SAPDESCR}: Bits sent OutProf net.sap.out.OutProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.22.{#SNMPINDEX}]
But it didn't work, no items are created by the rule.
Is Zabbix expecting a single number as the index? Maybe that's the reason why no items are gettimg created by my rule. Can someone confirm the index must be a single number only?
Or may it be because of the time needed to complete the discovery? It can take up to 2 mins to have all the list back via snmpwalk..
Where should I start troubleshooting this? I'm using 4.4 with proxy.
I also tried using a custom "User-Paramether" Zabbix-agent, but this doesn't work either because the script I wrote takes too long to retrieve all the indexes.
I understand the custom User-Parameter should be used to get the metric for something you cannot poll via SNMP, not to discover all the idexes (for some device I need up to 2 minutes to get them all...)
Any hint?
I'm a new Zabbix user and this is my first post!
I'm having some trouble trying to discover SAPs on a 7750, and I didn't find anything in the forum, so I'm here asking for your help.
I loaded the certified Zabbix template for these devices, and I'm now able to discover a subset of the interfaces that are configured into the them.
The subset I'm referring to is made of those interfaces in the global-routing-table where you typically run OSPF/ISIS. But I use to have a lot of VRFs on the box ("vprn" in 7750 language), and none of their logical-interfaces gets discovered.
Those interfaces use SAPs, that are entities to map the interfaces themselves to a given port/vlan, e.g.:
A:devicename# configure service vprn 100536 interface "MY-LOGICAL-INTF_1"
A:devicename>config>service>vprn>if# info
----------------------------------------------
description "MY CUSTOMER"
address x.x.x.x/30
ip-mtu 1500
sap lag-3:2.1321 create
description "vprn 100536 lag-3:2.1321"
exit
-------------------------------------------
A:devicename>config>service>vprn>if# info
----------------------------------------------
description "MY CUSTOMER"
address x.x.x.x/30
ip-mtu 1500
sap lag-3:2.1321 create
description "vprn 100536 lag-3:2.1321"
exit
-------------------------------------------
In order to graph that interface counters, I have to poll the ifindex associated to its sap, which is not discovered by the standard IF::MIB.
The MIB to use should be "1.3.6.1.4.1.6527.3.1.2.4.3.2.1.5" instead, that gives you both the sap-index and the sap-description. Here is how the output looks like:
SNMPv2-SMI::enterprises.6527.3.1.2.4.3.2.1.5.100536.13421 77283.86573058 = "vprn 100536 lag-3:2.1321"
As you can see the sap-index is made up of three dot-separated numbers "100536.1342177283.86573058", and if I append this index to other 7750 sap-specific mibs I can get back the desired counters.
So I tried to create a discovery-rule based on SNMPv2, using a custom hey "net.sap.interfaces" and this SNMP-OID value:
discovery[{#SAPDESCR},1.3.6.1.4.1.6527.3.1.2.4.3.2.1.5]
I was expecting this rule to discover all the device's saps' indexes and their description, mappped to #SNMPINDEX and #SAPDESCR respectively, thus I created some item prototypes referring to those macros in order to have automatically created items:
Name: Key:
SAP {#SAPDESCR}: Bits received InProf net.sap.in.inProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.12.{#SNMPINDEX}]
SAP {#SAPDESCR}: Bits received OutProf net.sap.in.OutProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.14.{#SNMPINDEX}]
SAP {#SAPDESCR}: Bits sent InProf net.sap.out.inProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.20.{#SNMPINDEX}]
SAP {#SAPDESCR}: Bits sent OutProf net.sap.out.OutProfile[1.3.6.1.4.1.6527.3.1.2.4.3.6.1.22.{#SNMPINDEX}]
But it didn't work, no items are created by the rule.
Is Zabbix expecting a single number as the index? Maybe that's the reason why no items are gettimg created by my rule. Can someone confirm the index must be a single number only?
Or may it be because of the time needed to complete the discovery? It can take up to 2 mins to have all the list back via snmpwalk..
Where should I start troubleshooting this? I'm using 4.4 with proxy.
I also tried using a custom "User-Paramether" Zabbix-agent, but this doesn't work either because the script I wrote takes too long to retrieve all the indexes.
I understand the custom User-Parameter should be used to get the metric for something you cannot poll via SNMP, not to discover all the idexes (for some device I need up to 2 minutes to get them all...)
Any hint?
Comment