Looking for cisco templates

[techlive13]

Hi Guys,
I am a new bee to zabbix and having a hard time adding Cisco switches and routers to zabbix. I was able to add and monitor linux and windows hosts without any issues but i have been struggling in adding switches and routers. The generic templates on Zabbix are not working for me and i only see errors such "unable to parse OID" . It will be of great help if anyone can share templates for Cisco 3750/2960 switches and Cisco ASR routers. Any help or input will be deeply appreciated.
Many thanks in advance!

[tatapoum]

Hi,

Here are a few templates I use for Cisco 2960-S stacks, 3750s, 6K5s and Nexus 5K, 6K, to monitor :
- CDP
- HSRP
- hardware
- interfaces
- CPU + MEM
- stackwise
I use a few other ones for Nexus specific OIDs if needed.

You will have to create a few value mappings before importing these templates. Here is an SQL dump of our value mappings. You will need to create the ones related to Cisco :
+------------+---------------------------------------+
| valuemapid | name |
+------------+---------------------------------------+
| 4 | APC Battery Replacement Status |
| 5 | APC Battery Status |
| 18 | Brocade admStatus |
| 15 | Brocade Link State |
| 14 | Brocade Port OpStatus |
| 17 | Brocade Port Physical State |
| 16 | Brocade Port Speed |
| 12 | Brocade Sensor Status |
| 13 | Brocade Sensor Type |
| 20 | Checkpoint standard status |
| 59 | CIM Health Status |
| 60 | CIM Oper Status |
| 19 | Cisco AP OpState Table |
| 9 | Cisco Card State Table |
| 54 | Cisco cefc OperStatus |
| 55 | Cisco entSensorType |
| 10 | Cisco EnvMonState Table |
| 8 | Cisco Interface State Table |
| 52 | Cisco stack member state |
| 53 | Cisco Stack port state |
| 64 | Cisco Threshold Relation |
| 11 | Cisco Tunnel Table |
| 57 | Cisco UDLD Operational Mode |
| 58 | Cisco UDLD Operational Status |
| 56 | ciscoHsrpGrpStandbyState |
| 7 | Dell Open Manage System Status |
| 2 | Host status |
| 6 | HP Insight System Status |
| 23 | Server HP Fan |
| 24 | Server HP Health |
| 1 | Service state |
| 22 | SMX Status Code |
| 49 | SNMP device status (hrDeviceStatus) |
| 51 | SNMP interface status (ifAdminStatus) |
| 48 | SNMP interface status (ifOperStatus) |
| 62 | VMWare ESX Connection Status |
| 43 | VMware status |
| 42 | VMware VirtualMachinePowerState |
| 63 | VMWare VM Power State |
| 61 | VMWare VM Status |
| 3 | Windows service state |
| 21 | Zabbix agent ping status |
+------------+---------------------------------------+

+-----------+------------+-------+----------------------------+
| mappingid | valuemapid | value | newvalue |
+-----------+------------+-------+----------------------------+
| 1 | 1 | 0 | Down |
| 2 | 1 | 1 | Up |
| 3 | 2 | 0 | Up |
| 4 | 2 | 2 | Unreachable |
| 5 | 3 | 0 | Running |
| 6 | 3 | 1 | Paused |
| 7 | 3 | 3 | Pause pending |
| 8 | 3 | 4 | Continue pending |
| 9 | 3 | 5 | Stop pending |
| 10 | 3 | 6 | Stopped |
| 11 | 3 | 7 | Unknown |
| 12 | 3 | 255 | No such service |
| 13 | 8 | 1 | Up |
| 14 | 8 | 2 | Down |
| 15 | 8 | 3 | Testing |
| 16 | 8 | 4 | Unknown |
| 17 | 8 | 5 | Dormant |
| 18 | 8 | 6 | NotPresent |
| 19 | 8 | 7 | LowerLayerDown |
| 20 | 9 | 1 | not-specified |
| 21 | 9 | 2 | up |
| 22 | 9 | 3 | down |
| 23 | 9 | 4 | standby |
| 24 | 10 | 1 | normal |
| 25 | 10 | 2 | warning |
| 26 | 10 | 3 | critical |
| 27 | 10 | 4 | shutdown |
| 28 | 10 | 5 | notPresent |
| 29 | 10 | 6 | notFunctioning |
| 30 | 11 | 1 | active |
| 31 | 11 | 2 | destroy |
| 32 | 12 | 4 | nominal |
| 33 | 12 | 6 | absent |
| 34 | 13 | 1 | temperature |
| 35 | 13 | 2 | fan |
| 36 | 13 | 3 | power-supply |
| 37 | 12 | 1 | unknown |
| 38 | 12 | 2 | faulty |
| 39 | 12 | 3 | below-min |
| 40 | 12 | 5 | above-max |
| 41 | 14 | 0 | unknown |
| 42 | 14 | 1 | online |
| 43 | 14 | 2 | offline |
| 44 | 14 | 3 | testing |
| 45 | 14 | 4 | faulty |
| 46 | 15 | 1 | enabled |
| 47 | 15 | 2 | disabled |
| 48 | 15 | 3 | loopback |
| 49 | 16 | 1 | one-GB |
| 50 | 16 | 2 | two-GB |
| 51 | 16 | 3 | auto-Negotiate |
| 52 | 16 | 4 | four-GB |
| 53 | 16 | 5 | eight-GB |
| 54 | 16 | 6 | ten-GB |
| 55 | 16 | 7 | unknown |
| 56 | 17 | 1 | noCard |
| 57 | 17 | 2 | noTransceiver |
| 58 | 17 | 3 | laserFault |
| 59 | 17 | 4 | noLight |
| 60 | 17 | 5 | noSync |
| 61 | 17 | 6 | inSync |
| 62 | 17 | 7 | portFault |
| 63 | 17 | 8 | diagFault |
| 64 | 17 | 9 | lockRef |
| 65 | 17 | 10 | validating |
| 66 | 17 | 11 | invalidModule |
| 67 | 17 | 255 | unknown |
| 68 | 18 | 1 | online |
| 69 | 18 | 2 | offline |
| 70 | 18 | 3 | testing |
| 71 | 18 | 4 | faulty |
| 72 | 18 | 5 | reboot |
| 73 | 18 | 6 | fastboot |
| 74 | 19 | 1 | associated |
| 75 | 19 | 2 | disassociating |
| 76 | 19 | 3 | downloading |
| 77 | 20 | 0 | OK |
| 78 | 20 | 1 | Warning |
| 79 | 20 | 2 | Error |
| 80 | 21 | 0 | Down |
| 81 | 21 | 1 | Up |
| 82 | 22 | 2 | OK |
| 83 | 22 | 3 | Degraded |
| 84 | 22 | 6 | Error |
| 85 | 23 | 0 | NOK |
| 86 | 23 | 1 | OK |
| 87 | 24 | 0 | OK |
| 88 | 24 | 1 | Error |
| 149 | 49 | 1 | unknown |
| 150 | 49 | 2 | running |
| 151 | 49 | 3 | warning |
| 152 | 49 | 4 | testing |
| 153 | 49 | 5 | down |
| 161 | 48 | 1 | up |
| 162 | 48 | 2 | down |
| 163 | 48 | 3 | testing |
| 164 | 48 | 4 | unknown |
| 165 | 48 | 5 | dormant |
| 166 | 48 | 6 | notPresent |
| 167 | 48 | 7 | lowerLayerDown |
| 169 | 51 | 1 | up |
| 170 | 51 | 2 | down |
| 171 | 51 | 3 | testing |
| 172 | 42 | 0 | poweredOff |
| 173 | 42 | 1 | poweredOn |
| 174 | 42 | 2 | suspended |
| 175 | 43 | 0 | gray |
| 176 | 43 | 1 | green |
| 177 | 43 | 2 | yellow |
| 178 | 43 | 3 | red |
| 179 | 52 | 1 | waiting |
| 180 | 52 | 2 | progressing |
| 181 | 52 | 3 | added |
| 182 | 52 | 4 | ready |
| 183 | 52 | 5 | sdmMismatch |
| 184 | 52 | 6 | verMismatch |
| 185 | 52 | 7 | featureMismatch |
| 186 | 52 | 8 | newMasterInit |
| 187 | 52 | 9 | provisioned |
| 188 | 52 | 10 | invalid |
| 189 | 52 | 11 | removed |
| 190 | 53 | 1 | Up |
| 191 | 53 | 2 | Down |
| 192 | 53 | 3 | forcedDown |
| 193 | 54 | 1 | unknown |
| 194 | 54 | 2 | ok |
| 195 | 54 | 3 | disabled |
| 196 | 54 | 4 | okButDiagFailed |
| 197 | 54 | 5 | boot |
| 198 | 54 | 6 | selfTest |
| 199 | 54 | 7 | failed |
| 200 | 54 | 8 | missing |
| 201 | 54 | 9 | mismatchWithParent |
| 202 | 54 | 10 | mismatchConfig |
| 203 | 54 | 11 | diagFailed |
| 204 | 54 | 12 | dormant |
| 205 | 54 | 13 | outOfServiceAdmin |
| 206 | 54 | 14 | outOfServiceEnvTemp |
| 207 | 54 | 15 | poweredDown |
| 208 | 54 | 16 | poweredUp |
| 209 | 54 | 17 | powerDenied |
| 210 | 54 | 18 | powerCycled |
| 211 | 54 | 19 | okButPowerOverWarning |
| 212 | 54 | 20 | okButPowerOverCritical |
| 213 | 54 | 21 | syncInProgress |
| 214 | 54 | 22 | upgrading |
| 215 | 54 | 23 | okButAuthFailed |
| 216 | 54 | 24 | mdr |
| 217 | 54 | 25 | fwMismatchFound |
| 218 | 54 | 26 | fwDownloadSuccess |
| 219 | 54 | 27 | fwDownloadFailure |
| 220 | 55 | 1 | other |
| 221 | 55 | 2 | unknown |
| 222 | 55 | 3 | voltsAC |
| 223 | 55 | 4 | voltsDC |
| 224 | 55 | 5 | amperes |
| 225 | 55 | 6 | watts |
| 226 | 55 | 7 | hertz |
| 227 | 55 | 8 | celsius |
| 228 | 55 | 9 | percentRH |
| 229 | 55 | 10 | rpm |
| 230 | 55 | 11 | cmm |
| 231 | 55 | 12 | truthvalue |
| 232 | 55 | 13 | specialEnum |
| 233 | 55 | 14 | dBm |
| 234 | 56 | 1 | initial |
| 235 | 56 | 2 | learn |
| 236 | 56 | 3 | listen |
| 237 | 56 | 4 | speak |
| 238 | 56 | 5 | standby |
| 239 | 56 | 6 | active |
| 240 | 57 | 1 | enable |
| 241 | 57 | 2 | disable |
| 242 | 57 | 3 | aggressive |
| 243 | 58 | 1 | shutdown |
| 244 | 58 | 2 | indeterminant |
| 245 | 58 | 3 | biDirectional |
| 246 | 58 | 4 | notApplicable |
| 247 | 59 | 0 | Unknown |
| 248 | 59 | 5 | OK |
| 249 | 59 | 10 | Degraded |
| 250 | 59 | 15 | Minor |
| 251 | 59 | 20 | Major |
| 252 | 59 | 25 | Critical |
| 253 | 59 | 30 | Non-recoverable Error |
| 254 | 60 | 0 | Unknown |
| 255 | 60 | 1 | Other |
| 256 | 60 | 2 | OK |
| 257 | 60 | 3 | Degraded |
| 258 | 60 | 4 | Stressed |
| 259 | 60 | 5 | Predictive Failure |
| 260 | 60 | 6 | Error |
| 261 | 60 | 7 | Non-Recoverable Error |
| 262 | 60 | 8 | Starting |
| 263 | 60 | 9 | Stopping |
| 264 | 60 | 10 | Stopped |
| 265 | 60 | 11 | In Service |
| 266 | 60 | 12 | No Contact |
| 267 | 60 | 13 | Lost Communication |
| 268 | 60 | 14 | Aborted |
| 269 | 60 | 15 | Dormant |
| 270 | 60 | 16 | Supporting Entity in Error |
| 271 | 60 | 17 | Completed |
| 272 | 60 | 18 | Power Mode |
| 273 | 61 | 0 | Grey |
| 274 | 61 | 1 | Green |
| 275 | 61 | 2 | Yellow |
| 276 | 61 | 3 | Red |
| 277 | 62 | 0 | Connected |
| 278 | 62 | 1 | Disconnected |
| 279 | 62 | 2 | Other |
| 280 | 63 | 0 | poweredOff |
| 281 | 63 | 1 | poweredOn |
| 282 | 63 | 2 | suspended |
| 283 | 63 | 3 | unknown |
| 284 | 64 | 1 | LessThan |
| 285 | 64 | 2 | EqualOrLessThan |
| 286 | 64 | 3 | GreaterThan |
| 287 | 64 | 4 | EqualOrGreaterThan |
| 288 | 64 | 5 | Equal |
| 289 | 64 | 6 | NotEqual |
+-----------+------------+-------+----------------------------+

Last, if the {$TRIGGER_IF_DOWN} macro equals one, an interface status change will raise a trigger.

[tatapoum]

Value mappings are created like this :

https://www.zabbix.com/documentation/2.2/manual/config/items/mapping

[techlive13]

Thanks for your reply and templates.
I followed your instructions. Created value mappings first and added templates afterwards. Issue i am seeing over here now is i dont see any items in the host template. I only see discovery rules with prototype items. Am i missing something here?
I have attached snapshots of the host for a better view.

[tatapoum]

It's probably working as expected. These templates make extensive use of low-level discovery (https://www.zabbix.com/documentation...evel_discovery) to automatically discover the items to monitor (CPU, interfaces, sensors, etc). That means that the items will be created after they have been discovered by LLD. As the discovery interval is mostly set to 3600s in our templates, you'll have to wait a moment before the checked items appear.
If that doesn't work, have a look at the discovery status in the host properties :
http://imgbox.com/2BNXsUtQ

And I also forgot that the CDP template uses the advsnmpdiscovery script. You can find it here :

https://github.com/simonkowallik/Zabbix-Addons/tree/master/advsnmp.discovery

Put it into your external scripts directory and restart zabbix.

You also have to set the {$SNMP_COMMUNITY} macro for these templates to work.

[techlive13]

As you said it took a while due to update time setup to 3600.
Its working fine now on our Nexus 5k, 2960, 3750 & ASR. Many thanks for your help with this regard. Strongly appreciate this.

Thanks!

[tchjts1]

There are also some good Cisco templates here, among others...

https://github.com/jjmartres/Zabbix/tree/master/zbx-templates

[techlive13]

I have one question for you. Although most of the item which are working now. I do get this error on some half of the items.
e.g.
"snmp_parse_oid(): cannot parse OID "ifPromiscuousMode.437379072" for a lot of items.
"snmp_parse_oid(): cannot parse OID "ifHighSpeed.151192662".
and many.
Is there something i need to change in this? Do i need to manually change OID's?

[tatapoum]

The SNMP interfaces template is kind of generic and some items may not be supported by different models or IOS/NXOS versions. That's why some of them return an error. You can just disable them on the related hosts if you want. Or if you prefer the "opt-in" you can disable them globally on the template (in item prototypes) and enable them on every host that support them. Unsupported items will be checked at an interval specified here :

https://www.zabbix.com/documentation/2.0/manual/web_interface/frontend_sections/administration/general?&#other_parameters

Moreover, NXOS doesn't support the same OIDs as IOS for a few features. I am going to attach some Nexus specific templates.

Last, I think that a few items use text instead of numerical OIDs. So if they don't work, check that the corresponding MIB is installed on your server, or replace the name by the numerical OID.

[tatapoum]

Cisco Nexus specific templates.

[tatapoum]

Last, I think that a few items use text instead of numerical OIDs. So if they don't work, check that the corresponding MIB is installed on your server, or replace the name by the numerical OID.

For example, ifPromiscuousMode and ifHighSpeed are part of the IF-MIB. So, the IF-MIB must be installed in your server to translate these OIDs. You can find it here ftp://ftp.cisco.com/pub/mibs/v2/IF-MIB.my and put it in /usr/share/snmp/mibs (for RedHat/Centos). Then add "mibs +IF-MIB" in /etc/snmp/snmp.conf. You can check that it works with :
snmpwalk -v 2c -c COMMUNITY DEVICE ifPromiscuousMode

Or, you can just replace ifPromiscuousMode by 1.3.6.1.2.1.31.1.1.1.16 and ifHighSpeed by 1.3.6.1.2.1.31.1.1.1.15.

[houranit]

Hey,

I have tried those same templates and they all work great except for the Triggers on the CDP template.

I changed the trigger to use 2 independent LLD's instead of the advanced.snmp script, and I have created the triggers in both LLD's. The issue is that when I shutdown an interface and the CDP neighbor is lost, Zabbix will not throw a trigger. Instead it marks the items as unsupported.

Do you have this working? I cant figure how to throw the trigger instead of marking the item prototypes as an unsupported item

Any help would be greatly appreciated!

[tatapoum]

That's strange. I'm sure that I've tested the CDP trigger.

I'll have a look at this.

[houranit]

Really? How are you testing it? But shutting the interace connecting to the CDP neighbor?

Could you possibly send me screen shots of hwo you have the CDP LLD setup? Including items and triggers?

Thanks again!

[Husabuse]

Cisco Nexus specific templates.

Hi!

I'm trying to import your nexus scripts in my Zabbix server, and the memory one works fine, but the hw one drops an error.

History:	 Configuration of hosts » Configuration import » Configuration of hosts » Configuration of templates » Configuration import 
Details
	ERROR: Import failed

    Created: Application "Hardware" on "Template LLD Cisco Nexus Hardware".
    Created: Discovery rule "entPhysicalDescr.Fan" on "Template LLD Cisco Nexus Hardware".
    Created: Discovery rule "entPhysicalDescr.Module" on "Template LLD Cisco Nexus Hardware".
    Created: Discovery rule "entPhysicalDescr.PS" on "Template LLD Cisco Nexus Hardware".
    Created: Discovery rule "entPhysicalDescr.Serial" on "Template LLD Cisco Nexus Hardware".
    Created: Discovery rule "entSensor" on "Template LLD Cisco Nexus Hardware".
    Cannot find value map "Cisco cefc OperStatus" used for item prototype "Fan {#SNMPVALUE} State" of discovery rule "entPhysicalDescr.Fan" on "Template LLD Cisco Nexus Hardware".

...any ideas?

Rgds

/J