Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

The Survivor's Guide to 2004: Network and Systems Management: Page 3 of 12

• Packet shaping: Packet-shaping vendors, including Allot Communications and Packeteer, also are seeking to stem the data overrun. On wide-area links--and especially at the Internet border--their products' ability to explicitly allow traffic based on application can conserve bandwidth while knocking out performance bottlenecks and security threats. For example, packet monitoring at the application layer can catch worms and other nastiness trying to cross the appliance into your network.

This is a rare inclusion of security management into the FCAPS model, one we'd like to see more of. Here's another example of how the twain can meet: The basic functionality of conventional fault-management tools closely resembles that of SIM (security-information management) tools. Products from Arbor Networks and other vendors that characterize traffic for intrusion detection also characterize route flow, a network-management function.

Unfortunately, 2004 will not see a bridging of the crevasse between security-management and network-management functions. Even though FCAPS management nirvana would integrate the distinct groups of people administering networks and security, the reality is that IT management likes keeping access and privacy control in the hands of a few, and security vendors exacerbate this division. We hope vendors will start to merge these two, improving both in the process. A push from the enterprise asking for focused fault correlation could drive this union.

The SNMPv3 and SNMPconf standards were refined during 2003, and adoption seems likely for 2004. SNMPv3 is poised to implement Diff-Hillman key exchange, making it possible to have a private, secure management channel. And SNMPconf, now a standard, has the Diff-Serv MIB poised to become a draft specifying the first multivendor standard to configure network QoS applications.

The IEEE isn't sitting on its hands, either. It's busy chiseling out a Layer 2 topology standard, 802.1ab, that will regulate the way in which network and systems management products attempt to piece together networks. Not only will this improve network documentation a hundredfold, it offers real hope that root-cause analysis will improve in network and systems management systems.

On the old-friend product front, both Aprisma and Hewlett-Packard are bringing out new versions of their veteran network-management applications, Spectrum and Network Node Manager, respectively. These stalwarts have been around more than 10 years but continue to innovate.