Our setup looks as follows: We have some servers which are running Xen
dom0 and one for measuring the traffic of all the servers and the domUs,
which are running on them. On each one Debian respectively Ubuntu is
running.
= Xen Servers: =
On these servers it is necessary to install the snmpd package and to set
the vifname for each vif in domu configuration file.
== snmpd ==
For snmpd there are two configuration files (the second one is Debian
specific) to be configured:
=== /etc/snmp/snmpd.conf ===
com2sec local 127.0.0.1/32 mysecretcommunity
com2sec local 192.168.1.40/32 mysecretcommunity
group MyROGroup v1 local
group MyROGroup v2c local
group MyROGroup usm local
view all included .1 80
access MyROGroup "" any noauth exact all none none
syslocation "My location"
syscontact nospam@xxxxxxxxxxx
=== /etc/default/snmpd.conf ===
# replace the default of 127.0.0.1 with your IP address you want the
snmpd listening on.
[...]
SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid
127.0.0.1'
[...]
== domU ==
=== domu.cfg ===
# add the directive vifname to each vif to make the interface unique and
the measurements reliable
[...]
vif = [ 'bridge=br-vlan2000, mac=00:16:3e:00:dd:56, vifname=srv1-eth0',
'bridge=br-vlan2001, mac=00:16:3e:00:dd:57, vifname=srv1-eth1' ]
[...]
= server with routers2.cgi =
On this server we have installed mrtg, rrdtool and the routers2.cgi. The
main part is done by routers2.cgi. So let's have a look at its
configuration file.
== srv1.example.com.cfg: ==
Usually mrtg is using only numbers to refer to the interfaces. But these
numbers are changing under Linux, after rebooting, changing network
configuration, etc. To avoid this problem, we are using the interface
names to refer to the interfaces. This is the reason why we had to set
the vifname in domu.cfg.
If you are using GBit interfaces it also necessary to use SNMP v2. This
is done by adding ":::::2" at the end of the ip address in the first
row. On this way mrtg uses 64Bit counters instead of 32Bit.
[...]
Target[192.168.1.1_srv1-eth0]:
#srv1-eth0:mysecretcommunity@xxxxxxxxxxx:::::2
SetEnv[192.168.1.1_srv1-eth0]: MRTG_INT_IP="" MRTG_INT_DESCR="srv1-eth0"
MaxBytes[192.168.1.1_srv-eth0]: 125000000
Title[192.168.1.1_srv1-eth0]: Traffic Analysis for srv1-eth0 -- srv1
PageTop[192.168.1.1_srv1-eth0]: <H1>Traffic Analysis for srv1-eth0 --
srv1</H1>
<TABLE>
<TR><TD>System:</TD> <TD>dom0 in My Location</TD></TR>
<TR><TD>Maintainer:</TD> <TD>nospam@xxxxxxxxxxx</TD></TR>
<TR><TD>Description:</TD><TD>srv1-eth0 </TD></TR>
<TR><TD>ifType:</TD> <TD>ethernetCsmacd (6)</TD></TR>
<TR><TD>ifName:</TD> <TD>srv1-eth0</TD></TR>
<TR><TD>Max Speed:</TD> <TD>1 GBit/s</TD></TR>
</TABLE>
[...]
== Troubleshooting ==
After some testing it became obvious that there was a big spread between
the measuring of the switch and of the dom0 itself. I solved this issue
by adding the following line to the config.
LoadMIBs: /usr/share/snmp/mibs/IF-MIB.txt
Regards,
Jan
Stephen Liu schrieb:
Hi Jan
Apprecited if you could post the info in detail in re their setup and
use. Pointers would be appreciated as well. TIA
B.R.
Stephen L
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
| 
Home