Submitted by beau@318 on Wed, 01/14/2009 - 5:38pm
Of all the command line tools available to assist you in the management of an Xsan volume, cvadmin serves as the primary command line tool to interface with, troubleshoot, and ultimately administer your Xsan. It provides for capabilities beyond what is available through Apple-provided GUI tools, which can be extremely useful for resolving the more complex problems that can crop up. Given the reported issues with Xsan Admin occasionally misreporting information, cvadmin is one of the tools that can help to make your experience administering an Xsan much less frustrating.
Read more below...
Submitted by aaron on Thu, 09/21/2006 - 4:15am
The general rule with Xsan, since version 1.1 or so, is this: DNS isn't necessary, but if you have some you had better make sure it is perfect. A few of us are beginning to suspect that DNS is, in fact, required, although in a very obscure way. It will take me several paragraphs to explain why, but let me get to the bottom line first:
Your DNS servers should include a zone for reverse lookups of your metadata (private) IP range. Ask your DNS administrator to create a reverse zone for this range, with SOA and NS records. PTR records aren't needed.
Read more to find out why.
Submitted by aaron on Mon, 03/13/2006 - 4:41am
The most mystifying component of our SANs has got to be the fibre channel network. With heavy black boxes, bright orange cables, even lasers, it sends our PKE meter off the scale. Even the management software manages to either look like a Windows program or require -- ack -- Internet Explorer!
This article may help shed just a little light on your fabric. The idea is to set up zones -- lots of zones -- to make your SAN behave more predictably. It can be a lot of work at the beginning, but you get several important benefits.
- Broadcast traffic is isolated between clients, minimizing client-to-client conflicts
- New devices are effectively invisible until deliberately added to a zone