Many systems administrators will recognize Vixel SAN InSite from its former incarnation as the configuration software for Vixel switches and hubs. With this latest release, Vixel has broadened the scope of SAN InSite to include the physical management of other systems. However, the product doesn't cover quite as much ground as SANavigator does. For instance, there are no planning features available for SAN InSite.
On the other hand, though SAN InSite's visualization features are not as slick as those in SANavigator, its navigation interface is laid out a bit better for those using it in large SAN installations. For example, SAN InSite has a detachable tree view that we feel would make navigating a large SAN network easier with the Vixel product than with SANavigator. The flexibility of the visual interface on SAN InSite will be a boon in large SANs.
To begin our testing, we dropped the SAN InSite CD into one of our test servers, and the autostart began the install. We noticed we could either install SAN InSite or install something called HBA Proxy. We installed SAN InSite and ran the "server" portion of the software.
This all went well, so we ran the client and logged into the SAN InSite server. After looking around for a while, we found that we could not manage the HBA. Checking through the online help, we found documentation indicating that the HBA Proxy is needed on any system where you want to manage the HBA as well.
No problem: We popped the SAN InSite CD back into the drive. It autostarted and began the install sequence. Then it stopped and told us that SAN InSite was already installed. That was it: no option to install the HBA Proxy. No options were offered, in fact, except Exit.
Puzzled, we consulted the documentation, which said the HBA Proxy should have loaded with SAN InSite. The reality of the situation is that if you want to run the HBA Proxy server so as to enable the management of supported HBA devices, you need to do a custom install on the initial install screen. If you load either SAN InSite or the HBA Proxy by itself, you will be unable to load the other package. A small, easily solved yet irritating problem.
We called Vixel, which said that the company generally does not expect the HBA Proxy and SAN InSite to be installed on the same machine. The expected use is that SAN InSite would be installed on a central management station that isn't necessarily directly on the SAN, with the HBA Proxy installed only where needed. This is a design decision based on the product's highly client/server-centric configuration. Fair enough, but this was not immediately apparent to us when we installed the package.
While using SAN InSite to investigate our SAN, we found the interface good but ultimately lacking in polish and some functionality. One nice feature: SAN InSite is upgradable on the fly with the use of modules that will let it discover and manage new devices. You can download these modules from Vixel's Web site as they are released. SAN InSite also supports a historical traffic monitor with little graphs that provide some data on the amount of traffic going on each switch port.
One thing that we definitely did not like is the technical support provided (or not provided, as the case may be) by Vixel. If you are not an integrator, OEM or similar type of customer, you don't get technical support. You are required to go to your local VAR or reseller and get technical support through that channel. To be frank, that sucks.
SAN systems are too complex and their relative importance to the company too high for admins to be calling local resellers in the hope they will have a clue on how to use SAN InSite. While a local VAR can call and get technical support, all the customer's support needs have to be filtered through the VAR. This causes an exponential increase in the amount of time taken and confusion caused.
Vixel needs to pony up its experienced people and make them available to the end user in times of need. The company's online presence also could be beefed up. The only information available on SAN InSite, other than sales notes, are some "tech tips" that seem to be mostly installation notes.
The list of supported devices for SAN InSite is much smaller than that of SANavigator. That is to be expected, however, because Vixel has only recently said that SAN InSite will be used for more than just its own platform. We expect that the supported hardware list will grow as work on the software progresses.
With respect to launching native tools to manage a device that it does not support, SAN InSite will launch the tool if aware of that tool, launch your default browser at the device's IP address or allow you to configure an application for managing the device. This functionality is a bit basic in SAN InSite. With a device for which it had no information, such as the Chaparral Network Storage Fiber Channel interface on our Overland Data tape array, SAN InSite offered us nothing: No menus, no HTTP launch and no way to configure a tool to use with it.
While we like SAN InSite -- especially its significant cost savings over SANavigator -- we feel that, as with all products in this category, the software has room for improvement. Still, it's a promising beginning.
SAN InSite Professional 3.5, $7,995 for up to 32 ports to $44,995 for up to 512 ports; for more than 512 ports, contact Vixel; total cost on our test SAN: $7,995. Vixel Corp., (425) 806-5509; fax (425) 806-4050. www.vixel.com
Steven J. Schuchart Jr. covers storage and servers for Network Computing. Previously he worked as a network architect for a general retail firm, a PC and electronics technician, a computer retail store manager, and a freelance disc jockey. Send your comments on this article to him at sschuchart@nwc.com.
REPORTS
ANALYTICS
Follow 
