by clicking on the page. A slider will appear, allowing you to adjust your zoom level. Return to the original size by clicking on the page again.
the page around when zoomed in by dragging it.
the zoom using the slider on the top right.
by clicking on the zoomed-in page.
by entering text in the search field and click on "In This Issue" or "All Issues" to search the current issue or the archive of back issues respectively.
by clicking on thumbnails to select pages, and then press the print button.
this publication and page.
displays a table of sections with thumbnails and descriptions.
displays thumbnails of every page in the issue. Click on a page to jump.
allows you to browse through every available issue.
GCN : March 2013
37 that IT shops already monitor to keep their networks humming, and the network administrator's job becomes more complicated than ever. "Network management is a multiheaded beast," says Jim Frey, managing research director for the consulting firm Enterprise Management Associates (EMA). Network management veterans say network administrators must adopt six factors if they hope to build a solid toolset and implementation strategy for monitoring and managing today's mission-critical networks. 1. Understand the Current Infrastructure Why are the latest IT initiatives so challenging for network- monitoring efforts? One reason is they make it difficult to nail down performance levels at a particular point in time. For example, traditional network-monitoring techniques, which only use probes to gather performance data, start to > CDWG.com | 800.808.4239 break down in virtualized and cloud environments. In those settings, IP addresses change constantly; an address used one week by an application may be assigned to a completely different app the next week. Another monitoring nuance created by cloud and virtualized computing is that administrators can no longer just focus on traffic going into and out of the data center. " ey have a lot more traffic that's just flowing between servers or even on the same server between virtual machines," says Lori MacVittie, senior technical marketing manager with F5 Networks. " at's not something that would naturally be detected by traditional monitoring solutions because they watch events out on the wire at a switch or router," she adds. "Suddenly, you have all of these variables, and you are trying to figure out where the traffic is coming from and how you can manage it. e first challenge is determining where the problems are and what is creating them." Before any problems arise, network administrators should establish a baseline for their network performance: how the pipes operate under normal conditions when bottlenecks and other types of breakdowns are not evident. Baselines should document bandwidth usage, the kind of traffic normally flowing over the communication links and the number of people who use the infrastructure. "You now have something that you can use to compare anomalies against," says Don Rumford, consulting systems engineer with Avaya. Baselines also make it possible to establish alert thresholds that warn administrators when network utilization rates, packet losses or other factors begin to rise significantly. 2. Know What to Measure What data points are most important to measure? Network administrators should track a mix of traditional metrics, such as utilization levels, netflow statistics