Aruba has a multitiered platform, with a GUI that is driven by a Java-enabled browser. The middle-tier report server is made up of several databases that define groups, authenticate users and summarize data to generate on-the-fly reports. The final tier comprises the raw data gathered from data collectors or polling agents. The data resides in an Oracle database.

Because Aruba doesn't go beyond OSI Layer 2 monitoring, it can't monitor or analyze TCP/IP traffic. Also, it lacks application-monitoring capabilities. But it does a good job of presenting a network's operational overview.

In my test of Aruba, I found the installation to be straightforward. But I discovered that you must do your homework regarding how you want to distribute Aruba's remote server and central Oracle database. Unfortunately, Aruba does not have autodiscovery tools to add nodes automatically. You can use a third-party autodiscovery tool and save the data in "host file" format and then add it to Aruba. As your network grows and the number of devices monitored by Aruba increases, you have to maintain a device directory as you would with any other directory. Keep in mind, however, that modifications to your directory won't be recognized by Aruba.

It was a snap to add a few key devices on the network, including the Cisco Systems Catalyst 8510 and Cisco Catalyst 2916 backbone switches; a frame relay-configured router, the Cisco 2501; and a handful of switches and routers that process heavy traffic. After I entered the IP addresses of the devices, Aruba was able to get detailed information about each.

Devices in Aruba can be classified in groups arranged in a tree hierarchy. Any single device can be a part of multiple groups. I created groups by locations and by organizations.

I established several and defined their top-level groups. (A top-level group is the highest point in the tree a user can access.) A user can access all the components in the tree hierarchy below the top-level group. The level assigned affects which reports a user can view. For example, assigning a specific level in the hierarchy to your user would let him or her create groupings from that point in the tree, and assign other users and rights below that branch. You can share devices in as many groups as you prefer, but you can't give different levels of access to the shared device. All users would be able to see similar data and all ports on the device with the same granularity.

Aruba Reports

To access Aruba, you can use a Web browser to point at the report server or use Aruba Console, a downloadable program that lets you create and modify users, groups, devices, thresholds, queries and various other policies.

After defining a query in Aruba Console, I was able to view reports in various chart formats. I also exported the results from the query in a text file.

Using the Web browser, you can access reports, make predefined and customized queries, download Aruba Console, access limited administrative controls, forward reports as e-mail attachments, and access help. However, the Web interface is primarily used to access reports. The report page has predefined quick links that let you view reports on a daily, weekly, monthly and quarterly basis.

A report menu lets you see reports in various paradigms, such as by summary or service quality, and a pull-down menu gives access to groups for which you have permission. I was able to run the query I defined in the Aruba Console. I wasn't satisfied with the query interface, however, as I had to enter the name of the device instead of selecting from a list. Valencia says it will improve the interface in Aruba's next release.

Reports generated from different categories differ from each other, depending on the devices and kind of report used. For example, a frame relay report tells you about DLCI failures, and a LAN report tells you about interface failure. Both types of reports can provide information on the total bytes, average availability, utilization, round-trip delay, marginal and critical exception, and peak utilization on each port.

In the exception reports, I detected ports on some of my switches that were generating many errors and being overused. The reports described any violation of the thresholds that I defined using Aruba Console.

Asad Irshad is a freelance writer based in Syracuse, N.Y. Send your comments on this article to him at airshad@syr.edu.