I am using zabbix 2.4 version and added 'Template Cisco WLC Discovery'. Cisco 2960 not receiving dhcp from the router. The help desk software for IT. Create the Required Groups For this model, all of the Discovered routers are Cisco. Create a Host Group named 'Cisco Routers.' Configuring Zabbix Value Mappings Value Mappings interpret the Values returned by an SNMP query. The installed SNMP MIB defines a Value List for each relevant OID. The image below illustrates an snmpwalk for the OSPF MIB's OSPF Area Status OIDs. Notice the Value List in the lower left. These values -- and those for other OIDs -- must be mapped in Zabbix prior to importing Template_SNMP_Router_OSPF. The illustrations below depicts the various Value Mappings that must be configured prior to the OSPF Template import. This template is generic and will primarily query the IF-MIB tree to develop Interface Item, Trigger and Graph Prototypes. The Template is valid for any SNMP-compliant networking device -- Layer 1 Hubs, Layer Two and Three Switches and Layer Three Routers. This article adds Discovery functionality using other Templates and the same may be done for other vendor's equipment. Cisco SNMP Router Template This Template will query OIDs under proprietary Cisco MIBs. Ndrive keygen map. This may be problematical for routers running older versions of the Cisco IOS because the SNMP implementations have changed over time. The Template queries CPU and Memory utilization for recent IOS versions. It is assumed the Zabbix Server has stock MIBs installed (for instance, the snmp-mibs-downloader MIBs available under Debian Wheezy), but since the Cisco MIBs are proprietary and require additional Zabbix Server SMP configuration, they are queried by numerical OID and not by human-readable text. OSPF SNMP Router Template This template is generic and will primarily query the OSPF-MIB tree to develop Item, Trigger and Graph Prototypes. The Template is valid for any SNMP-compliant OSPF implementation. Items Items are single-instance OIDs unique to each device. Discovery is a dynamic and variable process. Essentially, the Discovery Item queries a single part of the MIB tree using the snmpwalk command. This query returns a series of Indexes and Values for the MIB tree. Assign the Name Cisco Routers. IP Range Assign as many subnets as necessary to include device IP addresses. You may subnet these values to search only a portion of the desired subnet. For instance, if there is a network subnet 10.64.0.0/24 that can accommodate 254 hosts, you may define the Zabbix Discovery IP address range as (for example) 10.64.0.0/28 to only search the lower portion of the subnet's available IP addresses. Checks The Checks are used primarily to define device uniqueness (SNMPv2-MIB::sysName.0 as described above) and for passing information to Actions (SNMPv2-MIB::sysDescr.0 as descibed above); Actions are described below. Device Uniqueness For a given Discovery Rule, a device -- particularly switches and routers -- may have several interfaces that will show up in Discovery. Uniqueness definitions assure they will only be added once and that each device has all interfaces encountered by the Discovery Rule included. Define Conditions that filter Discovered devices. Keep in mind interfaces other than Networking Devices may be discovered; we don't want to monitoring these as Cisco Routers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |