Nagios and IPv6 made easy with the mknagconf configuration generator
This article describes how to install Nagios3 and my mknagconf tool and how to use them. It should take about 30 minutes to install nagios3 and mknagconf and set it up to monitor a few hosts. The following has been tested with Ubuntu 10.04, 10.10 and 11.04 on an amd64 platform.Nagios3 is an excellent monitoring engine, but the stock Nagios has some limitations in regard to dual-stack hosts. In the Nagios universe, one host is one ip address, and a secondary ipv6 address would require an extra host definition.
The Nagios packages which you are about to install have been patched to support this concept "one host = 1 ipv4 address + 1 optional ipv6 address". The mknagconf script makes it easier to maintain your Nagios installation. mknagconf takes small short, and simple definition files, parses them and generate the configuration files for Nagios. This will be explained after installing the required software.
Step 1: Install all dependencies
apt-get install apache2-mpm-prefork apache2-utils apache2.2-binStep 2: obtain PGP key, configure apt Continue reading
apache2.2-common bsd-mailx libapache2-mod-php5 libapr1
libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
libgd2-noxpm libjpeg62 libperl5.10 nagios-plugins-basic
php5-common postfix ssl-cert nagios-plugins-standard
nagios-plugins-extra git-core make
Common Services VRF MPLS and BGP
One of the most common MPLS VPN topologies is the Common Services simply put, it provides the most control of Branch traffic and filtering. MPLS VPNs are among one of today’s favorite and for good...[[ Summary content only, you can read everything now, just visit the site for full story ]]
3 weeks to go
I know it is a little slow here in this blog. ... The marathon is 3 weeks from now, so in the past few months I was very busy training. I have lots of ideas for new mini labs and some other stuff.The OSPFv2 Network Summary LSA Type-3
Well, what is the Network Summary LSA? It’s an LSA flooded throughout the backbone area, which describes networks in other areas. Originated only by ABRs (Area Border Routers) and not flooded...[[ Summary content only, you can read everything now, just visit the site for full story ]]
Booting Solaris After a Motherboard Upgrade
As part of the recent hardware upgrade to my ZFS file server I replaced the motherboard. I'd never replaced the motherboard on an active Solaris system before and was curious whether it would be at the easy end of the spectrum (like OpenBSD is) or at the impossible end (like any recent version of Windows). This is what I learned.
ZFS File Server Hardware Refresh
I recently decided to indulge my inner geek by doing a hardware refresh on my home ZFS file server. The system had served me well since moving to ZFS from my previous system but there was room for improvement.
Hitting the PF state table limit
I recently had an issue with an OpenBSD firewall where the number of state table entries was hitting the default limit of 10,000. When this limit is reached, no new state entries can be created. If you're using “keep state”, “modulate state” or “synproxy state” on your rules or if you're running OpenBSD 4.1 or newer (where “keep state” is the default on all rules) this could mean that:
- You cannot make new connections through the firewall
- You cannot make new connections to the firewall
- You cannot make new connections from the firewall
So…. if you hit the state table limit it's kinda bad, mmmkay?
ZFS File Server
Specifications Total storage raw: 10TB Total storage usable: 5TB Case Norco RPC-4220 - 20 hot-swap bay, 4RU chassis PSU Corsair HX 750W Motherboard Supermicro X8STE - single socket 1366; 2x Intel 82574L GigE NIC; Matrox G200 GPU CPU Intel Xeon E5620 Westmere 2.4GHz Quad Core RAM 24GB (6x4GB) Kingston 240-pin DDR SDRAM ECC Unbuffered Controller Cards Intel SASWT4I (LSI SAS1064E chipset) PCIe x4 4-port SAS HBA LSI 9201-16i 6GB/s PCIe 2.Website Redesign
If you've visited this site before then it's obvious to you the site has undergone a major face lift. All of the content that was on the old site is still here, it's just at a different URL. Some of the more popular pages on the site are now here: Juniper Networks Olive Monitoring BIND9 Monitoring Postfix NetPacket PERL modules for IPv6 and OpenBSD packet filter OpenBSD SNMP MIBs As these pages are updated or when I add new tools or scripts, I plan on posting a blog entry to that affect.Troubleshooting OSPFv2 Neighbors (Part2)
This will seem very similar to t he last post, again going on simple. Things that can be overlooked if one is not careful, doesn’t look at everything with a magnifying glass, and becomes over...[[ Summary content only, you can read everything now, just visit the site for full story ]]
Contact
Joel Knight Calgary, Alberta, Canada @knight_joel Github Profile LinkedIn Profile PGP key A962 E7D1 B274 ABDE 3993 50FC 026A 7711 BAAA 8FEFIPv6 Tutorial: IPv6 Addressing #1
I am back again with the second post in this series, in the first post we had an overview of IPv6 and the need for it in the near future. In this post we will start breaking the technical ice of IPv6; I am going to discuss basic IPv6 addressing. This will need more than [...] No related posts. Related posts brought to you by Yet Another Related Posts Plugin.Ticket #17
Ticket #17 is published under the CCIE Flyer. Click here for direct link. Enjoy!IPv6 Tutorial: The overview
I will start from the beginning; two weeks ago I wrote a post claiming that IPv4 is depleting and IPv6 is coming soon; and since we are considering deploying IPv6 soon in our network, I thought it might be useful to write about IPv6 migration and transition strategies. Although, this is important but I think [...] No related posts. Related posts brought to you by Yet Another Related Posts Plugin.vPC and VSS features and Comparison
Seems like other than IPv6 allot of the talk lately (in the Datacenter anyways) is about MEC, or multi-chassis etherchannel. Using something like this in the aggregation part of the Datacenter not...[[ Summary content only, you can read everything now, just visit the site for full story ]]
How Network Operators can cooperate: the NLNOG RING
In December 2010 I started a project with a few friends to make life for network engineers in the Netherlands better.I noticed that there are a lot of friendly 'shell access' exchange deals between dutch network operators. This makes it easier for parties to debug network issues and troubleshoot from the outside. A point of view outside your network is absolutely essential, seeing what others see is a useful thing for a variety of network problems. Well known examples are "it works for even numbered ip address, but not for odd numbered ip address via this and this route".
The NLNOG RING tries to do this in a more organized way, basically the deal is "donate 1 machine, and gain access to all other machines in the ring". So far already 10 organisations are participating.
How useful is the ring exactly? A very nice example is executing a traceroute from ten different autonomous systems: nlnog ring example.
More information about the NLNOG RING can be found on the website we've launched today: ring.nlnog.net.