I've created a template for monitoring Cisco ASA firewalls. This one has been tested on a 5505 running ASA Version 8.0(2) and a 5510 running 7.2 firmware. It contains OIDs and some graphs for connections, IKE/IPSEC sessions/users/throughput, 1min CPU load and memory usage, plus the standard 24 ethernet interfaces. There are no triggers currently defined. Some of the OIDs also work for Cisco ISRs [877, 1841, etc].
Ad Widget
Collapse
Cisco edge device templates
Collapse
X
-
Cisco router + DSL stat templates
Attached is a Cisco router template with the usual interfaces, Cisco CPU usage and global IPSEC/IKE throughput. Also attached is a Zip file containing 24 templates for DSL interfaces stats and DSL up/down sync speeds, plus one unzipped so you can see it without downloading the zip. The reason for the 24 separate templates is that the index number of a DSL interface varies from one router to the next.
If you walk the CISCO-IPSEC-FLOW-MONITOR-MIB of your Cisco device, you'll be able to see the indices of the individual IPSEC tunnels, so if you're interested in throughput on a specific tunnel [rather than global IPSEC throughput] then you can monitor the cipSecTunHcIn/OutOctets.n values, where 'n' is the index of that particular tunnel.
Instructions- Upload the Template_Cisco_Router.xml
- Create a device and link it to Template_Cisco_Router
- Navigate to Monitoring > Latest Data, scroll down to find an interface called ATM0-asdl or similar on the device you've just created and look at the index number. On the 877 for example, it might be ifDescr11 has a value of ATM0-adsl, thus the index number for that interface is '11'.
- From the zip file, upload the corresponding template, in this case Template_Cisco_DSL_int.11.xml
- Link this template to your device. Your new device will now have two templates linked to it.
- Sit back and watch the DSL line stats roll in. Eventually, you will see a graph like this:
-
I've noticed on a few routers that the DSL stats go a bit haywire when the line drops, specifically I've seen the downstream noise margin figure can go up to 320,000 tenths of a dB. I suppose the only positive side effect of this is that you can see on your graphs when the line has dropped!Comment
-
I tried to use this template and it doesn't seem to work. Do you have an updated template that works with an ASA Version 8.2(1)?I've created a template for monitoring Cisco ASA firewalls. This one has been tested on a 5505 running ASA Version 8.0(2) and a 5510 running 7.2 firmware. It contains OIDs and some graphs for connections, IKE/IPSEC sessions/users/throughput, 1min CPU load and memory usage, plus the standard 24 ethernet interfaces. There are no triggers currently defined. Some of the OIDs also work for Cisco ISRs [877, 1841, etc].
thanks
-mattComment
-
I don't have anything with 8.2 to test with I'm afraid, and to be honest I don't use this template any more as using one of the template generators is easier. I do still use the DSL interface stats templates.
What items don't work with 8.2? If the answer is 'all of them', then I suspect something more fundamental is at play.Comment
-
i have a question , maybe the template has a problem about bankwidth , i'm running zabbix 1.8.3 ,import this template for a cisco asa 5510 ,then create a host named 5110,but every interface show bandwidth is not right , example if interface.9 bandwidth is 800K,but the graphs is 100K ,the right value is the zabbix get value * 8 . it seems somewhere has a calcution error.Comment
-
I tried to import on zabbix 1.8.5. seems doesn't work on that version.I've created a template for monitoring Cisco ASA firewalls. This one has been tested on a 5505 running ASA Version 8.0(2) and a 5510 running 7.2 firmware. It contains OIDs and some graphs for connections, IKE/IPSEC sessions/users/throughput, 1min CPU load and memory usage, plus the standard 24 ethernet interfaces. There are no triggers currently defined. Some of the OIDs also work for Cisco ISRs [877, 1841, etc].
is there any update for that database?
Cheers
ArashComment
-
I had the same problem...
I suspect that this is one of those templates that was exported with special characters that could not be re-imported. #fail
I noticed that colons ( : ) are special characters in the Zabbix key notation - so I removed the double colon ( :: ) from the key name and VoilĂ the Cisco ASA template was successfully imported into Zabbix FrontEnd v1.8.10!
I have attached the cleansed version for your convenience!
^_^
Cheers,
-D.Attached FilesComment
-
Fine basis template for asa, but I am looking for one with more features like:
- triggers
- in and output errors on interfaces
- drop packet count
- more vpn statistic
(- LLD for zabbix ver. 2.x?)
... more
Anyone who would like to upload their extended cisco asa template?
(... else I will have to make it my self
)
BR
ErikLast edited by eskytthe; 28-05-2013, 16:13.Comment
-
have you made one already?Fine basis template for asa, but I am looking for one with more features like:
- triggers
- in and output errors on interfaces
- drop packet count
- more vpn statistic
(- LLD for zabbix ver. 2.x?)
... more
Anyone who would like to upload their extended cisco asa template?
(... else I will have to make it my self
)
BR
Erik
or did you find any?
can you please shareComment
Comment