11.01.2013 Views

Workshop

Workshop

Workshop

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The Outsiders<br />

Previous Table of Contents Next<br />

Two types of vendors who don’t have to get into your building to wreak havoc on your network are ISPs<br />

(Internet service providers) , who you rely on to surf the Web and send email, and, of course, telephone<br />

companies, who may connect your sites to each other via leased lines. Of these two, the telephone<br />

company is the much more mature vendor. Although the various phone companies take a lot of abuse,<br />

they’ve been doing this stuff for decades, and they tend to have good change-management policies in<br />

place. Consider that ISPs have only been around in their current form for less than a decade, and it’s easy<br />

to see why they still have growing pains and therefore a bum rap.<br />

Mondays can be tough. ISPs and phone companies tend to make changes over the weekend when<br />

utilization is low. If something that worked on Friday doesn’t work on Monday, it’s time to pick up the<br />

phone and call the appropriate provider and ask what’s been changed? The answer will likely be<br />

“nothing,” but if you can verify that nothing has broken over the weekend at your end and hang in there,<br />

the problem may mysteriously vanish around lunch time.<br />

For longer-term problems, you may have to convince them that there’s nothing wrong with your<br />

computer equipment (or figure out that there is something wrong and apologize for having doubted<br />

them). One way of doing this is to set up a test network; if two sites can’t talk, you might as well bring<br />

the equipment to the same site and connect them directly. Once you do this and see that it works, you<br />

have pretty compelling evidence for the outside provider that nothing has changed with your equipment<br />

and that something has changed between the two sites.<br />

The Risk/Benefit Ratio<br />

New programs are cool. They offer features not offered in older versions, and it’s fun to be the first one<br />

on your block to have them. Unfortunately, experience shows that for every new feature introduced, there<br />

are probably two new bugs in a product. The breakneck speed of Internet time means that software<br />

developers have unbearable pressure on them to be first to market. This usually translates into quick<br />

product testing, which means that the programs are released with at least a few bugs. Check out any<br />

software vendor’s Web site—you’ll see fixes posted for products that have been out for at least six<br />

months.<br />

Because you have better things to do with your day than report these bugs to the software vendor, it’s a<br />

good idea to not be the first one on your block to put a new application or operating system on your<br />

network. Unless you desperately need the new features of a new product, you should wait six months<br />

after product release to start rolling it out. If you need to do it sooner than that, consider what surgeons

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

Saved successfully!

Ooh no, something went wrong!