I needed to monitor 3 NetApp filers with Nagios.
Since the filers are quite accesible through things like ssh, web interface and SNMP I didn’t think it would be hard. But, when doing a quick search I’ve found this excellent nagios plugin made by Sven Velt. It is available at http://people.teamix.net/~svelt/check_netappfiler/. It has saved me *lots* of time.
It even seems to be prepared to be used with pnp4nagios too. I haven’t tried this since I’m not using it.
One strange thing though… I can query all the filers with standard SNMP settings even with SNMP disabled on the filer(s). This has suprised me a bit. It might be a bug, but I’m not sure.
Dus..
Finaly I have my iPhone. So, here’s the first blog post written with it. I still have to get used to the thing.
For some time I’ve been wondering why none of my Debian/Ubuntu workstations would resolve something like ‘proxy.mycompany.local’. Simpy resolving ‘proxy’ would work.
I already knew that .local is not a correct tld, but since it was recomended by Microsoft to use this when installing Active Directory we used it. I never had any problems with it because most of the time I just use ip addresses when I need to access a server.
Now I installed a proxy server and a new mail relay server so I started using them as proxy.mycompany.local and relay.mycompany.local. The I found out that none of my Debian or Ubuntu workstations would resolve those addresses. At first I blamed the Microsoft DNS server for this. That’s the easiest and most logical thing to do 
. But Windows XP/Vista clients did resolve those addresses. Strange huh?
Then I started wireshark on my client. I did a query for proxy.mycompany.local and then there was…. an MDNS request instead of a normal DNS request?!?
This quickly gave me the conclusion that it was something avahi related because this does all the zeroconf stuff with Debian/Ubuntu. Avahi seems to be configured to pick up any request ending in .local and make MDNS requests for it. This must be a problem for more people because there must be loads of Microsoft networks out there ending in .local. I won’t say this is a fault from the avahi guys because it’s also completely wrong to use .local as tld.
My current solution is to just simply disable Avahi on my workstations. On Ubuntu I just do ‘System -> Administration -> Services’ and disable ‘Multicast DNS Service Discovery’ there. With Debian I just disable the startup of Avahi in /etc/default/avahi-daemon by settting ‘AVAHI_DAEMON_START=0′.
Van alle stroomleveranciers die er zijn in Nederland raad ik iedereen aan om *NOOIT* over te stappen naar de Nederlandse Energie Maatschappij. De mensen aldaar zijn te dom om te snappen dat als je niet over wil stappen dat je dat dan ook echt niet wil.
Ik ben nu welgeteld twaalf (ja dat is 12) keer gebeld met het verhaal dat de energie veeeeeel goedkoper kan. Verder leveren ze energie tegen inkoopsprijs. Maar als ik dan vraag hoe dat in godesnaam mogelijk is om iets in te kopen, te verkopen tegen diezelfde prijs en dan evengoed het loon van al je werknemers te betalen, dan weten de jongens en meisjes van het callcenter dit niet.
Een bedrijf dat zo aggressief met marketing bezig is en met zo’n lul verhaal komt kan gewoon geen goede leverancier zijn en is alleen maar uit op geld.
Na ook 12 keer gezegd te hebben dat ik niet meer gebeld wens te worden en hier geen gehoor aan te geven mogen de dames en heren van de Nederlandse Energie Maatschapij van mij nu allemaal doodvallen.
Dank u.
There’s another way to create vlan interfaces with Debian/Ubuntu. It’s even shorter than the previous example. Just add the following to /etc/network/interfaces:
auto eth0.10 iface eth0.10 inet static addres 10.0.0.2 netmask 255.255.255.0 gateway 10.0.0.1
Just make sure you dit ‘apt-get install vlan’ or something like that.
Comments(1)
