Munin.md
... ...
@@ -1,40 +0,0 @@
1
-## Graph your routes
2
-
3
-```
4
-#!/bin/bash
5
-if [ "$1" = "config" ];then
6
- echo graph_title Number of routes
7
- echo graph_vlabel num. routes
8
- echo graph_category network
9
- echo graph_scale no
10
- for AS in $(ip r|sed 's/.* dev //;s/ .*//'|sort|uniq -c|grep as|awk '{print $2}');do
11
- echo $AS.label $AS
12
- done
13
-else
14
- ip r|sed 's/.* dev //;s/ .*//'|sort|uniq -c|grep as|awk '{print $2".value "$1}'
15
-fi
16
-```
17
-
18
-## Graph routes and activity for every neighbour
19
-
20
-This munin-plugin makes it very easy to graph the announced routes and activity for each neighbour over time:
21
-https://github.com/luben/bird-multigraph-plugin
22
-
23
-It's also possible to get notified by Munin when a problem with the peering persists. You have to define a critical value in line 138:
24
-```
25
-imported.critical 1:
26
-```
27
-This will send execute the command (set in munin-node.conf) to alert you, if the imported route count falls under 1.
28
-
29
-You might also want to change line 125 from
30
-```
31
-graph_title $proto->{title} routes
32
-```
33
-to
34
-```
35
-graph_title $name routes
36
-```
37
- 
38
-
39
-Example installation:
40
-http://stats.tbspace.de/munin-cgi/munin-cgi-graph/tbspace.de/server.tbspace.de/dn42_crest_routes-day.png
howto/Munin.md
... ...
@@ -0,0 +1,40 @@
1
+## Graph your routes
2
+
3
+```
4
+#!/bin/bash
5
+if [ "$1" = "config" ];then
6
+ echo graph_title Number of routes
7
+ echo graph_vlabel num. routes
8
+ echo graph_category network
9
+ echo graph_scale no
10
+ for AS in $(ip r|sed 's/.* dev //;s/ .*//'|sort|uniq -c|grep as|awk '{print $2}');do
11
+ echo $AS.label $AS
12
+ done
13
+else
14
+ ip r|sed 's/.* dev //;s/ .*//'|sort|uniq -c|grep as|awk '{print $2".value "$1}'
15
+fi
16
+```
17
+
18
+## Graph routes and activity for every neighbour
19
+
20
+This munin-plugin makes it very easy to graph the announced routes and activity for each neighbour over time:
21
+https://github.com/luben/bird-multigraph-plugin
22
+
23
+It's also possible to get notified by Munin when a problem with the peering persists. You have to define a critical value in line 138:
24
+```
25
+imported.critical 1:
26
+```
27
+This will send execute the command (set in munin-node.conf) to alert you, if the imported route count falls under 1.
28
+
29
+You might also want to change line 125 from
30
+```
31
+graph_title $proto->{title} routes
32
+```
33
+to
34
+```
35
+graph_title $name routes
36
+```
37
+ 
38
+
39
+Example installation:
40
+http://stats.tbspace.de/munin-cgi/munin-cgi-graph/tbspace.de/server.tbspace.de/dn42_crest_routes-day.png