1MRTG-IPV6(1)                         mrtg                         MRTG-IPV6(1)
2
3
4

NAME

6       mrtg-ipv6 - IPv6 support in MRTG
7

OVERVIEW

9       MRTG and cfgmaker support SNMP over IPv6. IPv6 targets can be specified
10       by hostname or IPv6 address, and if the required libraries are present
11       (see below), queries will use IPv6.
12

USAGE

14   Enabling IPv6
15       IPv6 is currently disabled by default and must be explicitly enabled.
16       In MRTG this is done by turning on the EnableIPv6 global option in the
17       configuration file. In cfgmaker, it is enabled with the --enable-ipv6
18       command-line option.
19
20       If IPv6 is disabled, MRTG and cfgmaker should behave in exactly the
21       same way as previous versions. So the addition of IPv6 support should
22       have no effect on existing MRTG setups unless IPv6 is enabled.
23
24       IPv6 support requires the Socket6 and INET6 libraries (see below). If
25       MRTG can't find them, IPv6 is disabled.
26
27   Specifying IPv6 targets
28       IPv6 targets may be specified by name or IPv6 address. Numeric IPv6
29       addresses may be used with both cfgmaker and MRTG, but they must be
30       enclosed in square brackets.
31
32       For example, a target could be specified as:
33
34        public@[2001:760:4::]:161
35
36       Hostnames work as expected: first an IPv6 name lookup is tried, then an
37       IPv4 lookup.
38
39   Targets that do not support SNMP over IPv6
40       Many targets (this currently includes all Cisco routers) do not yet
41       support SNMP over IPv6 and must be monitored over IPv4. This can cause
42       problems if you specify a target through its DNS name and the name maps
43       to both the IPv6 address and the IPv4 address of the target: MRTG will
44       only try IPv6, and will fail.
45
46       To query these targets, use the IPv4Only per-target option, which tells
47       MRTG not to use SNMP over IPv6 for the target.
48
49       MRTG does not fall back to IPv4 for performance and correctness
50       reasons. If there are many routers to query, a timeout for every router
51       would make MRTG take too long to query them all. And if, for some
52       reason, IPv6 connectivity to the target is lost, MRTG's error messages
53       can help figure out what is wrong.
54
55       cfgmaker does fall back from IPv6 to IPv4. If IPv6 is enabled and
56       cfgmaker is given a hostname that resolves to both an IPv6 and an IPv4
57       address, it first tries to query the target over IPv6. If it receives
58       no answer, it tries again using IPv4. If the target answers, cfgmaker
59       sets the IPv4Only option in the generated config file.
60

IPv6 LIBRARIES

62   Libraries required
63       IPv6 support requires the Socket6 and INET6 Perl modules. Both can be
64       downloaded from CPAN:
65
66       http://search.cpan.org/author/UMEMOTO/Socket6/
67
68       http://search.cpan.org/author/MONDEJAR/INET6/
69
70       If you use Debian, you will need the packages libsocket6-perl and
71       libio-socket-inet6-perl, which are (or should soon be) in unstable.
72
73       So far, IPv6 support has been tested on Linux only, and only with
74       Socket6 version 0.12. Also note that IPv6 won't work at all if you
75       don't have INET6.pm version 2.00 or newer.
76
77   Installing the libraries
78       Building and installing Socket6 and INET6 is very simple. For each
79       module, just unpack the archive and then do:
80
81        perl Makefile.PL
82        make
83
84       and then:
85
86        su
87        make install
88
89       If you have installed the libraries successfully, cfgmaker and mrtg
90       should automatically detect them and allow IPv6 support to be enabled.
91

AUTHOR

93       Lorenzo Colitti <lorenzo location colitti.com>
94
95
96
972.16.4                            2010-05-17                      MRTG-IPV6(1)
Impressum