6211_The Admins Guide to Server Infra - ebook

8/7/2019 6211_The Admins Guide to Server Infra - ebook

1/13

The Admins Guideto Server Infrastructure Tools

an Networking eBook


2/13

S

o you've done your research and purchasedyour servers and possibly signed a service

agreement. Now what? If you said, "walk awayand let 'em run," think again.

Life around servers is rarely that simple. A sys adminin a large server room, or rooms, will most likely needtools to help him or her keep the servers runningeffectively. This is where software to manage, monitor,and configure the server infra-structure comes in. Thus, thequestion is not whether youneed some of the tools, butwhich ones and from whom.

DefinitionWhen it comes to servers, whatdo we mean by infrastructure?Simply put, it's organized serversupport. Do all of your serverswork in isolation as standaloneunits? Probably not. There aregroups of them: different types,different functions, clusters for scalability, and so forth.You organize them to support them and enable themto work better together. Collectively, the way the

servers are organized and the tools are provided tosupport them constitutes the infrastructure. To makethe infrastructure work, you must set the servers up inthe right way, monitor their operation, and manage

their services. Not a simple task by any means.

Start with a rule of thumb: The greater the number ofservers, the greater the need for infrastructure tools.One server does not constitute an infrastructure. Onthe other hand, if you have a thousand servers, youcertainly need infrastructure tools. With that manyservers, you probably need infrastructure tools just tokeep them running. Then, there's the no small matter

of getting the most out of theservers, ultimately known asmaximizing ROI. Infrastructuretools are necessary for that aswell.

Tools to ConsiderThese "tools" are, of course,products. Sometimes theycome in suites, such as IBMTivoli or Computer AssociatesUnicenter. They are also sold invarious combinations or asindividual (even standalone)

products. Infrastructure tools cover a very large range,as this by no means inclusive list illustrates:

Application Deployment and Management (IT) Asset and Inventory Management Backup and Archiving Batch Processing

2 An Internet.com Networking eBook. 2009, Jupitermedia Corp.

The Admins Guide to Server Infrastructure Tools[ ]

The Admins Guide to ServerInfrastructure Tools

by Nelson King

Jupiterimages

To make the infrastructure work, you must set the servers up in the right way, monitor theiroperation, and manage their services. Not a simple task by any means.


3/13

Configuration and Change Management Cluster Management Data Management

Desktop Management Disaster Recovery Enterprise System Management File Transfer Management Job Automation and Scheduling License Management Network Management Performance (Load and Stress) Testing Patch and Update Management Print Management Security Management Storage Management

User Management Web Systems Management

There are many ways to slice and dice the territory ofserver infrastructure. With hundreds of products thathave considerable overlap, vendors, analysts, and jour-nalists can (and do) see infrastructure tools throughmany perspectives.

As numerous and confusing as the server infrastructureproducts can be, one needn't be a computer scientistto reach an understanding about what an organizationmust have to support its servers. Some basic informa-

tion is required: Where servers are located, what theyare doing (at least in general), and some details oftheir configuration (what hardware and software theyare running). From there, consider other areas of serv-er management (such as items on the above list) todetermine strengths and weaknesses. If there are gapsor problems managing the server infrastructure, startlooking at tools to cover them. Fundamentally, theprocess is the same for small and midsize businessesas it is for very large enterprises.



To best determinewhether someor your

entire server infrastructure is a good candi-

date for open source solutions, consider sev-

eral criteria.

Who is your audience? Does your server infra-

structure serve highly platform-dependent users?

For example, a Microsoft Exchange server han-

dling groupware messaging for a shop full of

MicrosoftOutlook clients is serving a highly spe-

cific audience.Unless your plans include migrat-ing clients to open source messaging solutions,

suchasGnome Evolution, the MSExchange serv-

er probablymakes the most sense in this scenario.

On the other hand, many "generic" network servic-

es, suchas file serving, POP3or IMAP4 e-mail,

Web serving, DNS, CUPS-based printing, andeven

somedatabases can be served neutrally by open

source packages. In a neutralnetwork, client con-

nectionsmay come in fromany platformwith sup-

port for these protocols. POP and IMAPe-mail is

supported by virtually every e-mail client available,

so running an open source e-mail server does not

precludewhich clients it can serve.

A third consideration is cost control and cost shift-

ing. Traditionally, commercial server solutions

require ongoing licensing fees be paid for the right

touse the software. These feesmay include a cer-

tain level of support, which can often be upgraded

with additional payment. Thismay also introduce

the need for in-house expertise tomaintain the

server infrastructure, thus raising costs.

Open source server solutions canoffermore finan-

cial options. Withmoney invested in in-house

expertise, outside support costs can be low tonone.

This sameexpertise cancustomize open source

software to a degree thatmay be costlyor unavail-

ablewithcommercial serverapplications. Third-

party vendors, likeNovell and Red Hat, offer sub-

scription-basedopensource solutions that function

similarly to commercial offerings, involving ongo-

ing costswith support andmaintenance contracts.

In this scenario, the costs may not differ all that

much from those of commercial applications.

Enterprises, however, may continue to benefit from

other flexible aspects of open source software.

Open Source Apps

for the Server RoomBy Aaron Weiss

As numerous and confusing as theserver infrastructure products can be,

one needn't be a computer scientist toreach an understanding about what an

organization must have to supportits servers.


4/13

People with experience will say, "It's not that easy."True. The process described in the previous paragraphleaves out some important complications, including

budget limitations, existing infrastructure elements,personal preferences (e.g., those of executives), andresistance to change. Nor is comparing server infra-structure products necessarily easy. Products may havemany common features, but their vendors maydescribe them differently. There are also overlaps infunctionality. Finally, not all vendors are equally skilledin marketing, which means sometimes a good product(or feature) is not effectively represented. More often,though, it means some products (or features) are over-sold.

Options and Trade-OffsAny research undertaken on infrastructure tools willprobably pay off regardless of the ultimate purchaseand implementation. Whether a vendor sells it to you,you buy it yourself, or ahosting service providesit, you'll see many of thesame products. Even ifyou're attracted to a par-ticular vendor (or alreadyhave a horse in the barn),it is useful to see what the

competition is doing. Later in this guide, we will pro-vide feature checklists for infrastructure tools - thosefocused on server management, server monitoring,and server configuration - that you can use to evalu-ate products.

The category of server infrastructure tools is one ofthe fastest growing areas of software. Thanks to theproliferation of small servers used in large groups(e.g., blades) the need for software to manage themhas grown exponentially. As a category of software,server infrastructure tools is extremely competitive.

Products are available from the biggest names in thebusiness as well as tiny, unknown start-ups. The goodnews is the resulting proliferation of options, alterna-tives, and comparative advantages. This is also, ofcourse, the bad news.

On top of wading through the forest of products,there are large issues to consider: Own or lease?Operate in-house or outsource? Single vendor or mul-tiple vendors? Given the wide functionality of server

tools, the many platforms, and the large number ofproducts, the trade-offs that must be weighed areinevitable.

When it comes to server infrastructure tools, thedefault decision factor has long been the server hard-ware vendor. If a company has IBM, HP, or Dellservers, for example the tendency is to stick with therespective vendor's server tools. This is usually con-venient and may mean the tools are optimized for theservers. Still, the functional coverage of vendor-sup-plied tools may not be complete, and they may becomparatively expensive. It's also true that organiza-tions often use servers from different vendors (runningdifferent operating systems). A grab bag of vendor

tools may not play together as well as third-partytools designed to run in a heterogeneous environ-ment. In addition, third-party products are oftenselected because they are considered best-of-breed

or offer cost advantages -not because of inertia.

If third-party products areselected, the assumptionis that each offering hasbest-in-class features;there is no guaranteethey will work together

properly (or at all). On the other hand, if you select anall-in-one (or suite) product from a single vendor, thecoordination problems may be gone, but cost andvendor lock-in may be a problem. In a different con-text, there are decisions to be made about whether acompany wants to own and operate the infrastructuretools, or outsource that operation to others. Trade-offsapply: Owning and operating your own managementtools provides greater security and control (usually),but using a host or another outsourcer can be lessexpensive and may provide better facilities or staff.

None of these trade-offs are a given, but it is impor-tant to be aware that in the category of server infra-structure tools, there are usually trade-offs. In general,the larger and more complex the infrastructure, themore it will exacerbate the trade-offs.

Management SoftwareIn the realm of infrastructure management, servermanagement tools have a wide row to hoe. In most



The category of server infrastructuretools is one of the fastest growing areas

of software.


5/13

cases, these tools are the center, or hub, of the serverinfrastructure. As a result, they provide unified admin-istrative services for a large number of servers, which

usually means combined or even comprehensive func-tionality covering major areas of server management.

In general, server management tools can be dividedinto two categories: suites and specialist products.The most conspicuous products are suites. These aregenerally the big one-stop shops for server adminis-tration. Some of these suites are so comprehensivethat it's legitimate to wonder, do suites cover every-thing?

The question is relevant only after a definition of

"everything" is provided. Certainly, some enterprise-level suites, such as IBM's Tivoli and HP's OpenView,

attempt to cover the principal areas of server manage-ment - storage, networking, security, server perform-ance, and software management. On the other hand,the scores of specialist products in these same areasdemonstrate that suites don't include all (or evenenough) of some important features and functionality,and there is indeed a market for other products.

Then there's the difference in "approach" to servermanagement. Most suites attempt to establish a uni-fied approach - a consistent user interface, multiplat-form support, overarching policy controls, a unifiedframework in code and structure to hold all the piecestogether, and of course, single-vendor support. Lesscomprehensive products may have some of these ele-ments, but they often distinguish themselves by

adhering to a particular kind of management philoso-phy (e.g., exception-based or business-process-orient-ed) or they may have unusual user interfaces (oftenmore graphical) or a unique configuration of features(grouping features in unorthodox ways).

It should be no surprise that management productsare divided primarily into single platform (for the mostpart Microsoft and partners) and multiplatform prod-ucts. For convenience, this is often sliced and diced as

Microsoft System Management Server and the BigFour suites: IBM Tivoli, Computer AssociatesUnicenter, BMC Software PATROL, and Hewlett

Packard OpenView. Although clear and convenient,this categorization is misleading because there areproducts that greatly enhance or even replaceMicrosoft products, and there are literally dozens ofproducts constantly challenging at least part of thehegemony of the big four suites. Still, the orientationremains: Many products are divided into those thatrun only on servers running a Microsoft OS, and thosefor multiplatform servers running Linux, Unix, or MacOS X. To a certain extent, this divide also reflectsproducts developed using Java, the ones in Javabeing non-Microsoft, but again, there are many

exceptions.

When Shopping AroundSo what should be expected from server managementsoftware? First and foremost, all server management

products consolidate, aggregate, or concentrate (pickthe word) the operation of many servers into a singlepoint of administration. The principle benefits areobvious: It takes fewer people to manage a largenumber of servers, and the power of managementsoftware can be brought to bear on many servers in auniform way. Of course, which servers, performingwhat functions, and how they are administered arecrucial issues.

Server management software can be specific to cer-tain hardware (e.g., IBM, Dell, and Apple), to certain

operating systems (e.g., Windows, Linux, Unix, andMac OS X), and certain types of servers (e.g., Web,database, and application). When researching prod-ucts, this is a starting point because the information isreadily available. Overall, most vendors are accuratein categorizing their software's functionality, but notalways. Teasing features into categories can some-times be arbitrary, and suite vendors will sometimesclaim full functionality when only providing a subset offeatures. Some products will also ride the overlapbetween functionality, for example monitoring net-



All server management products consolidate, aggregate, or concentrate (pick the word)the operation of many servers into a single point of administration.


6/13

work traffic and monitoring server security.

The most difficult choice is determining how the serv-

er will be managed - i.e., the approach. Some fea-tures, such as whether the software is GUI-oriented orWeb-based, are easily determined. However, themore subtle aspects of management often fall into therealm of marketing-speak, making it necessary in mostcases to run a trial or test the software to get a truefeel for how it works.

Before selecting products to trial, it helps to developa reasonably well-defined set of requirements con-cerning platforms, basic functionality, and desiredapproach. As is often the case in software, server

management tools bring trade-offs to consider. Forexample, for one organization the convenience ofhaving a single source of support for an all-in-onesuite may trump a higher price tag and less-than-com-plete components, but for another, pieced-togetherbest-of-breed software with support cobbled from

many vendors may be preferable.

To help with the evaluation of server management

tools, we've crafted a functionality checklist ideal forcomparing the coverage of suites and specialist tools.If an organization has identified the kind of servermanagement it needs, the checklist can help deter-mine whether a suite or a collection of specialist prod-ucts is most appropriate.

Note that no one product (or even suite) will cover allof the areas listed. There will be many overlaps infunctionality, and vendors will define what they do inoften-contradictory ways. In other words: These cate-gories are intended for use as guidelines and can be

modified to best suit your needs.

We also have not weighted the importance of any ofthese areas, as only you can determine what is of pri-mary importance for your organization.



Management Tools MatrixProduct 1 Product 2 Product 3

Application Deployment and Management(May include functions of an application server)

IT Asset Management(e.g., catalog, valuation, and life cycle)

Availability, Error, and Problem Management(Primarily monitoring system errors)

Backup and Archiving Services(e.g., security, federal compliance, anddata management)

Batch Processing

(e.g., scripting and large scale deployments)

Change Management(Primarily for applications and program updates)

Configuration Management(Initial software installation and configuration)

Cluster Management(Server farms and other clustered configurations)


7/13

Management Tools Matrix continued Product 1 Product 2 Product 3

Data Center Management

(Coordination of data managers andother data operations)

Desktop Management(e.g., user desktop software, licenses,and configuration)

Disaster Recovery(On-site, off-site, and other recovery schemes)

Enterprise Systems Management(Coordination of many or all facets ofserver management)

Event Automation(e.g., Using server events to generate e-mail)

File Transfer Management(FTP and other file transfer control)

Job Scheduling(Local and remote server jobs management)

Load, Stress, and Performance Management(Testing and monitoring of server activity)

License Management(Software and hardware license record keeping)

Network Management(Monitoring, analysis, and troubleshooting)

Patch and Update Management(For commercial software and hardware changes)

Printing Management(Control and monitoring of print-related services)

Security Management(e.g., firewall, spam and spyware, and anti-virus)

Storage Management(Management of many kinds of storage devices)

User Management(User registration, policy management, and monitoring)

Web Systems Management(Web server resources and other services)




8/13

Monitoring SoftwareMonitoring many servers - i.e., keeping an eye on theiroperation - is one step toward meeting two priorities:troubleshooting and optimizing.

Hardware may fail, and software may not perform wellenough. Servers may fail entirely, or worse, appear tobe operating while they are no longer performing vitalfunctions. The more servers a company is managing,the greater the likelihood of problems and the moredifficult it becomes to monitor them. Then there's thenot-so-small matter of getting bang for the buck. Arethe servers performing well enough? Can a group ofservers be considered reliable?

These and similar considerations are behind the needfor specialized software that falls under the category ofserver monitoring tools.

Getting the most fromserver monitoring tools ismore than a numbersgame of managing asmany servers as possiblewith the fewest number ofpeople. It's also a matterof what is monitored. In

most cases, this meansthree areas:

1. Monitoring server operation (the running status)2. Monitoring server traffic (both in and out)3. Monitoring the results of server use (keeping logs,

statistics, and analysis)

Within the three areas, the products that monitorservers also cover (albeit somewhat unevenly) a greatdeal of functionality, which can be broken down like this:

Physical: Monitoring the physical hardware includeskeeping an eye on the temperature, power supply, andthe functioning of components, such as disk drives.Many of these are critical elements, and failure means adead server. Software that monitors the hardware canbe very specific, for example, it works on IBM serversbut not Dell servers.

Server Performance: Monitoring the performance of aserver (e.g., CPU usage, available disk space, and mem-

ory availability), especially under a variety of conditions,helps with both troubleshooting and optimization.

Services: All servers run a number of services (e.g.,DNS, POP3, and TCP). Many of these are critical to serv-er operation. Again, if they fail, the server fails. Mostmonitoring software covers a wide range of services.

Network: An old and very large area of server moni-toring is associated with operating a network. This isoften considered a separate category of monitoringsoftware, although such functionality is often built intogeneral-purpose server monitoring tools.

In addition, many server-monitoring tools are designed

for a particular type of server (e.g., Web or databaseservers). We've provided a Functions Checklist for servermonitoring tools below. Although the matrix attemptsto cover features generally available, it barely scratchesthe surface of the more-specialized features for monitor-

ing Web servers or net-works.

In all, server-monitoringsoftware is very diverse,and literally hundreds ofproducts are on the mar-ket. Most offer "real-time"monitoring that displaysthe current condition of

servers along with historical monitoring, which is therecord of server performance over time. Server monitor-ing tools are also packaged in different ways: They arealways included in the big server management suites,such as IBM Tivoli or Computer Associates Unicenter.There are a large number of general server monitoringproducts, such as GFI Software Network Server Monitorand BMC Software Server Monitoring and Management.

Specialized products provide features for specific oper-

ating systems (Microsoft Windows being an obviousexample) and types of servers. To further complicatethe choices, server monitoring tools can be purchasedand operated by the user, hosted by a third-party com-pany but operated by the user, or fully outsourced (i.e.,hosted and operated by a third party). A cursory prod-uct search on the Internet will reveal scores of hostedand outsourced approaches.

The server monitoring tool selection process is often a



Getting the most from server monitoringtools is more than a numbers game ofmanaging as many servers as possiblewith the fewest number of people. It's

also a matter of what is monitored.


9/13

matter of matching several things: hardware, operatingsystem, functionality (e.g., Web or database,), and orga-nizational priorities (e.g., preferring software that pro-

vides a strong reporting and analytical capability). Someenterprises may opt to match their hardware vendorwith the monitoring software (e.g., an xSeries shop maychoose Tivoli); others may look for specific features orbest-of-breed characteristics in different kinds of servers(again, most commonly for Web and database servers).

And don't forget specific organizational needs. Whencomparing server monitoring products, it may beimportant to evaluate the options for alerting adminis-

trators, as support for specific methods, such as SMSand e-mail, can be crucial for some organizations.Alternatively, the ability to take remote corrective meas-

ures, such as server shutdown or script execution, canbe of great practical value.

The matrix below is designed to help in the comparisonof products by listing a range of features and placingthe servers side by side. Keep in mind, however, that tocreate a usable matrix, we had to limit the details forseveral monitoring functions. Hence, the blank cells atthe bottom of the table, which are there for you to fill inwith any requirements unique to your organization.



Server Monitoring Tools Matrix

Product 1 Product 2 Product 3Real-Time Monitoring Physical Status Temperature

Chassis IntegrityPower SupplyFan Speed

Server Performance Hard Disk Utilization- Files Open/Owner- File Existence Monitor- File Size Monitor(e.g. Log files)Memory UtilizationCPU Utilization

Processes (Count)Services Monitoring DNS

HTTP/HTTPSFTPTelnetNNTPSMTP, POP3, or IMAPCustom Port Monitoring

Server Types Supported WebDatabaseFileCommunications

Network Monitoring Network Throughput

Current LogonsFailover MonitoringOther NetworkMonitoring Points

Web Site Monitoring Hit RatePage ContentVerificationDatabase ConnectionVerificationCache Rate(s)

Security Intrusion Monitoring


10/13

Login Error MonitoringOther SecurityMonitoring Points

Administration Dashboard(or Other OverviewDisplay)Remote or InternetMonitoring

Administration Monitor Views DomainWorkgroupUser-Defined Group

Alert Modes E-MailPhone (Land Line orCell Phone)PagerNetwork AlertSMS

Escalating AlertLevels SupportAlert Multiple PeopleDesignate by Typeof AlertMonitoring IntervalUser ConfigurableMonitoring Intervals

Corrective ActionSupportMachine Shutdownor RebootService Shutdownor RestartProcess Shutdownor RestartRun Script, EXE, and Job

Testing Suite -Automatic TestingSupport

Historical Monitoring Logs

StatisticsReporting Online

PrintedCharts or Graphs

AnalysisOtherOtherOtherOther


The Admins Guide to Server Infrastructure Tools[ ]Server Monitoring Tools Matrix continued

Product 1 Product 2 Product 3


11/13

Configuration SoftwareIn a perfect world, every server in the enterprise wouldrun with optimum efficiency and could be reconfiguredto accommodate moves, adds, and changes at thedrop of hat. Needless to say, the world of servers does-n't work like that. Such efficiencies oftentimes are notpossible or can be the least attractive option.

The job of loading servers (and server-based software)and of tuning servers to run properly is the task ofremote server configuration software. This is a loose cat-egory, and products vary widely in functionality and fea-ture set. They cover tasks as diverse as software changemanagement, license management, inventory control,and performance monitoring. Moreover, this working

definition does not include remote client configuration(desktop or mobile), although this is sometimes part ofthe feature package for this type of software.

The job of configuring a large num-ber of servers can be daunting.There are three main steps:

1. Deployment and installation ofsoftware - be it new, an update,or a fix (occasionally, this step isnot part of the process)

2. The actual configuration of theserver - settings, rules, levels, andactions for events3. Testing of changes to ensurethey actually work

The obvious benefit of configuration management soft-ware derives from centralization and remote manage-ment. It rids an administrator (or small army of adminis-trators) of the need to physically visit each server thatrequires configuration. It also makes it possible to syn-chronize at levels difficult to achieve manually. An

important secondary benefit is the automatic logs thatrecord what was done, when, by whom, and to what.

Deployment, configuration, and testing on remoteequipment are rather tricky. Configuration processeshave more places where things can go awry than otherserver management areas. For example, a server maybe down or unplugged from the network, a piece ofsoftware that works on one server may not even starton another server, or a change that takes place on allservers from one manufacturer could fail to take place

on machines from another manufacturer. The condi-tions for failure in configuration management aregreater because it is 1) an active form of management

that is actually doing things to a server and its software,and 2) it usually involves making critical, simultaneous,and often sequential changes.

The moral of this story is that although configurationmanagement promises substantial and immediate bene-fits, such products are among the most difficult tochoose and implement. Perhaps because it is difficult todo everything well, products in this category are oftenvery targeted. There are configuration managers forspecific operating systems, specific types of applications(most commonly database), and for specific hardware.

As is always the case with server infrastructure software,suites (e.g., IBM Tivoli or Netopia netOctopus) ofteninclude server (and server-based software) configuration

tools. Although the suites are usual-ly more general in their approach,there is currently is no such thing asa universal configuration manager.Thus, when choosing this kind ofsoftware, there is often a trade-offbetween the range of possible con-figurations and the software need-ed fulfill the functionality.

To illustrate this, the FunctionalityMatrix for Configuration Tools pro-vided below is one where rather

than checking and comparing two or three productsthat compete across many of the features, enterpriseswill more likely be selecting from a grid of productsthat complement each other on the features provided.

An often-overlooked aspect of configuration manage-ment is that it must work with and sometimes aroundsystem security measures. The presence of firewalls,

port sniffers, spyware and antivirus software, and eventhings like unexpected password changes, can interruptor derail a multiserver configuration process. Therefore,features in configuration management software thathelp with security issues should be paramount.

Once a change is deployed and configured, it shouldbe part of the routine to ensure the changes are work-ing and delivering the expected improvements. Thisusually involves analyzing logs, event reports, and per-



An often-overlookedaspect of configurationmanagement is that it

must work with andsometimes around system

security measures.


12/13

Server Configuration Tools Matrix

Product 1 Product 2 Product 3

Server Architecture Cluster SupportUser-Defined Server GroupsOrchestration FeaturesHomogeneous Platform DeploymentMultiplatform Deployment

Configuration Types Supported Operating SystemApplicationsApplication Servers (Middleware)NetworksStorageOther

Deployment Installation Scripting- If Yes, Indicate Whether on

All Servers or Specified ServersFirewall ManagementLinks to Asset/Inventory ManagementMass Migration SupportDeployment Logs

Configuration SynchronizationPolicy ConfigurationEnterprise Directory SupportConfiguration Logs

Server Configuration Testing Testing SuiteLinks to Monitoring Software

Change Management Version Changes

PatchesLicense ControlAdministration Console

Web (Browser)Single Sign-OnAdministrative Session Logs

Other Other 1Other 2Other 3



formance tests. Some configuration management soft-ware includes testing capabilities, although the mini-

mum should be support for third-party testing and per-formance monitoring.

When done, it's crucial to set standards for a "success-ful" configuration and measure the results againstthose standards.

Coincidentally, note that "rollback" is not a commonfeature in this type of software. These products assumethat the organization unleashing a new configuration

on, for example, 1,000 servers, has tested thosechanges before doing so. To paraphrase an old adage,

the chain of configuration is no stronger than its weak-est link. I

This content was adapted from internet.com'sServerWatch Web site and written by Nelson King.

Copyright 2006 Jupitermedia Corp.


13/13



JupiterWeb eBooks bring together the best in technical information, ideas and coverage of important IT trends

that help technology professionals build their knowledge and shape the future of their IT organizations. For more

information and resources on networking, visit any of our category-leading sites:

www.enterprisenetworkingplanet.com

www.instantmessagingplanet.com

www.opticallynetworked.com

www.practicallynetworked.com

www.voipplanet.com

www.wi-fiplanet.com

www.opennetworkstoday.com

http://www.internet.com/networking

For the latest live and on-demand Webcasts on networking, visit: www.jupiterwebcasts.com/networking/

Documents

6211_The Admins Guide to Server Infra - ebook