11.01.2013 Views

Workshop

Workshop

Workshop

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Previous Table of Contents Next<br />

Here are some examples of service monitoring packages, listed from the primitive to the sublime:<br />

• Sitter (ftp://feldman.org/pub/sitter) A primitive Linux bash script that checks ports using the<br />

Telnet trick and complains to the console when problems are found. This definitely must be<br />

manually reconfigured for your site.<br />

• Netoscope (http://www.basta.com) A Windows utility for checking socket availability of certain<br />

servers. Issues audible alerts or runs a program (such as email) when problems occur.<br />

• IPSentry (http://www.ipsentry.com) A socket-monitoring package that runs under Windows. It<br />

tries whichever IP addresses and sockets you want, as often as you like. It can also page you when<br />

a problem occurs.<br />

• WhatsUp and WhatsUp Gold (http://www.ipswitch.com) This is a graphical network polling<br />

package with paging features. WhatsUp Gold has Web access, SNMP features, and IPX<br />

monitoring, as well. WhatsUp Gold also has the dubious distinction of being quite expensive for a<br />

polling package (close to $1,000 at this writing).<br />

So when do you use “pollsters” rather than SNMP managers? It depends on what you need. In my<br />

experience, only larger shops tend to use the SNMP managers; they tend to be expensive, resource<br />

intensive, and complex to install and maintain.<br />

Of course, SNMP managers also provide you with lots of information. In particular, the SNMP managers<br />

will provide you service-level information—that is, not only will they tell you whether the resource is<br />

“up” but also how fast it responds, how many bytes of resources are left, and so on. This makes SNMP<br />

managers very valuable if you’re looking to optimize your network. SNMP managers are excellent for<br />

keeping long-term track (baselining) of how your network and resources look on a normal day. As you’ll<br />

see in Hour 23, baselining is a very important part of problem determination when, as they say, “The<br />

network is slow!” After all, if you don’t have a sense of how things typically are, how can you tell when<br />

something is out of range? Long-term service-level record keeping is also a way to know—and a way to<br />

show your boss—that everything is operating efficiently and is working properly.<br />

Still, simple network polling packages can be extraordinarily effective, even for large shops, but<br />

particularly for smaller shops. They’re typically inexpensive compared to the costs of deploying even a<br />

modest SNMP installation, and they’re very easy to configure and use. Although most network polling<br />

packages don’t address service-level issues, look for more of them to do so in the future. Of course,<br />

you’ll never have the rich level of information that SNMP provides, but you might not need it. In short, a<br />

polling package is a one-stop application where you can monitor many services easily. Figure 22.3 shows<br />

one of them.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!