XSAN Admin playing up!

Two similar problems...
First:
Some clients do not appear at all in XSAN Admin, yet they are working happily with mounted, fully functioning volumes. All well and good, but we can't mount or unmount volumes.
Second:
Within XSAN Admin, some clients appear in the Setup/Computers list with a green blob, yet they do not appear at volume level. So whilst at some level the system is aware of the client, again they cannot mount or unmount volumes.
Refreshing the list doesn't help. Nor does completely removing the SAN from the list and re-adding it. Running XSAN Admin from the MDC or any client gives the same result.
Is there a lower level way of forcing a refresh that might re-acquaint the system with what actually connected to it?
Any ideas gratefully received!
Message was edited by: VTmaint
Oh, and rebooting an invisible or partially visible client doesn't make any difference either!

I was just in contact with Apple support about this issue. Turns out it's a bug. The workaround is log in as an admin on the client system and issue this command from Terminal:
sudo killall servermgrd
<password>
The next refresh in XSA the client should appear.

Similar Messages

Client not being recognized on Xsan Admin

I am not able to see both my client computers on the Xsan admin page, and there are some strange things happening.
-My setup consists of two G5 computers (Clients), one Xserve G5 (Metadata Controller), a fiber channel switch, and an Xserve RAID (with 5 drives on the first controller partitioned RAID 0 for a total of 1.8 TB of storage space, and 2 drives on the second controller partitioned RAID 1 for a total of 370 GB to be the controller data).
-For the sake of testing I disabled their internal network controller (connected to a DHCP server), and have them all talking to each other with a second ethernet card. They are all on the same subnet and they can all see each other. They each have a manually assigned IP and are not on an external network
-When I access Xsan admin from the Xserve (using Remote Desktop) I can connect to the Xsan Xserve.local (IP 10.10.1.10). There, under setup, I see the Xserve (which is bold) stating that it is the controller. I also see Client 1 (client). Both have a green light next to them and are reporting no problems with the serial number (note that I am accessing the Xserve using Remote desktop on CLIENT 2). Client 2 is not seen on the computers section of the setup.
-Now when I access Xsan Admin from the Client 2 machine, I get different results. First, when I try to add a SAN, Client's 2 local address is the default. I change it to Xserve.local with the proper name and password, and I get to monitor the Xsan just like I was doing before from the Xserve machine.
-Now if I leave the default address, another Xsan will appear on the left pane (SAN Components). Here is the were it confuses me. Under this new San, I see all 3 machines on the computers list, but the one in bold is the Client 2 machine (the one from which a I am accessing Xsan admin, also the one that was missing from the previous list). If I try to setup the SAN from there, naming the san or continuing the setup it will not allow me (note that all three machines have a green light next to them). It tells me that "Some configuration is invalid; The computer you are connect to must be a controller." The catch here is that it will only let me configure if I am connected to a controller but Client 2 will only appear if I am connect to it. Needless to say that I want client 2 to be a client, not a controller.
I know this may sound a little confusing, but I can feel I am very close in getting this to work. Any help would be much appreciated.
Best,
Marcello

For anyone who has read this, thank you.
I finally managed to get all the clients to work together.
I was having a firewall issue, where my customized firewall settings were preventing communication on one of the critical ports that Xsan uses to talk to the components. All I had to do was flush the firewall and all was back to normal.

Problem in authenticate computers using XSAN admin

hi, i have XSAN 2.2 and i want to destroy it and create a new one , i have 2 xserve and 3 mac PC and all of them can ping on each other ....
when i connect to xserve 1 and open XSAN admin i choose connect to existing XSAN , then from the overview i choose destroy XSAN but i gives me error message that all computers must be connected to xsan to can destroy it so, i go to computers tab and select then i found the 3- computers , i select all of them and press continue i wrote username and password (use same authentication information for all added computers) then i wrote the username and password (which is the same for an admin on all computers) but it gave me error message
"Authentication Failures occurred... not all clients were successfully authenticated .you can individually authenticate to the other clients or you can attempt to bilk authenticate to the remaining clients using a different username and password "
i do not know why the authentication failed although all the computers have the same admin name and password??!!!
can anyone help me please ....

hi, i have XSAN 2.2 and i want to destroy it and create a new one , i have 2 xserve and 3 mac PC and all of them can ping on each other ....
when i connect to xserve 1 and open XSAN admin i choose connect to existing XSAN , then from the overview i choose destroy XSAN but i gives me error message that all computers must be connected to xsan to can destroy it so, i go to computers tab and select then i found the 3- computers , i select all of them and press continue i wrote username and password (use same authentication information for all added computers) then i wrote the username and password (which is the same for an admin on all computers) but it gave me error message
"Authentication Failures occurred... not all clients were successfully authenticated .you can individually authenticate to the other clients or you can attempt to bilk authenticate to the remaining clients using a different username and password "
i do not know why the authentication failed although all the computers have the same admin name and password??!!!
can anyone help me please ....

Problem with Xsan Admin

Hello
I have a big problem with my Xsan Admin.
Yesterday by mistake my configuration of xsan admin from Application
Support are gone.
Only config files from /Library/Filesystems/Xsan/config survive, but
without one client in config.plist
Now i cant mount any clients or controllers from Xsan Admin, even when
i set to connect to existing san.
From terminal i run two volumes locally on MDC.
I also try to add i client in Xsan Admin and its work, but not full
fuctionally. Only thing i can do now, i can mount on client volumes
using terminal and command:
sudo mkdir /Volumes/volumename
sudo mount_acfs volumename /Volumes/volumename
But its still dont work, because on some cleints i receive info
"Cannot mount. License authorization failure"

Have you allowed email to be sent/relayed from your local LAN / subnet ?

Xsan Admin reporting wrong volume size

I have an Xsan with 12T in a volume.
Xsan admin report only 4T free. In a Volume folder really it have used 4.5T (information obtain by the command du -h -d 1)but when I have Get Info in Volume, it show me 8T occupied.
Two weeks ago I had a cleanup of the system with cvfsck and the problem was corrected, but in this moment i have the same problem again.
Can you help me?

Did you first see the problem after you upgraded to Xsan 2.2?
Are you running Mac OS X Server 10.5.8 or 10.6.4?

Computer Listed in Bold in Setup of Xsan Admin

I have an Xsan (v1.4.2) with four (4) computers. One of these computers is the original MDC, and is named Thirty-Six. Another computer is named Xsan-PMDC, and is now the primary MDC (via cvadmin's fail <Volume_Name>). Even though Xsan-PMDC is now the MDC, the computer that used to be the MDC (Thirty-Six) is listed in bold in Xsan Admin-->Creative (name of SAN component)--> Setup-->Computers. I have been told that the computer listed in bold is the controller I am connecting to.
On the computer that is the active MDC at the moment, I have a window with this prompt.
"You have connected to a Xsan client computer. 'Thirty-Six.local' sees 4 disks (LUNs) that appear to be managed by the controllers listed below. To administer the corresponding SAN, select a controller and click Reconnect." The lone computer I can select from the Existing controllers menu is the active metadata controller (not Thirty-Six.local). If I select the active metadata controller and click Reconnect, will bad things happen? Will the data on the Xsan volumes be lost? Will service be interrupted?
My goal is for the active metadata controller to be the one that is listed in bold in Xsan Admin, but I don't want to lose the data on the Xsan volumes or create an otherwise bad situation. If anyone can offer me guidance on this, it would be appreciated.
Thanks for reading!
-Jonathan

I am sure you have figured it out by now, but in case you haven't try connecting to the Xsan controller in charge to run Xsan admin directly, or else try different Xsan clients.

No LUNs in Xsan admin

I'm using Xsan 1.1 on OSX 10.4.7 and I added an new Xserve RAID into the mix. But the trouble is that the LUNs are not showing up in Xsan Admin (v.1.3).
`cvlabel -l` shows the two LUNs, labeled "unknown". so does `diskutil list`.
All Xserve RAIDs have the same firmware, no LUN masking is on, and all the ports on the fibre switches are in the same zone.
Disk Utility.app can see the LUNs and will let me make a software RAID combo of them , but that's what I want. What I would like is to expand two of my data-only storage pools, if they'd show up in Xsan admin.
I've looked the manuals,man pages, discussions and so forth.
Any ideas?
Thx.

I reveiwed the following documentation for adding LUNs to storage pools:
http://docs.info.apple.com/article.html?artnum=303571
http://docs.info.apple.com/article.html?artnum=303570
http://docs.info.apple.com/article.html?artnum=301911
And it worked. Sort of.
I shutdown all the clients, except 2 or 3 (mdc, md backup and my admin Mac). Then I unmounted the volume from last remaining clients, and I stopped the volume. Then I proceeded to backup the cfg, check the volume, and add the luns to an existing storage pool. All went well, until it failed to update the volume with the new cfg. I reverted to the old cfg and added the LUNs to a new storage pool. That worked.
Thanks for everyone's thoughts on this one. I took more time to do it this time, then I did a month of so ago. Careful planning and backups (cfg and data) are helpful to peace of mind.
-x

The XSAN Admin Authentication mistery

We have an interesting problem with our xsan and cannot figure out the answer. Perhaps someone can help?
We have 2 Intel Xserve MDCs and 2 G5 Xserve ODs, running 10.5.1 server and xsan 1.4.2
Our clients are a mix of G5s running 10.4.11 and Intels running 10.5.1, also with xsan 1.4.2
We have a public IP range of 10.160.16.x to 10.160.20.255 and a private metadata IP range of 10.160.21.x
All xsan clients (including the OD servers) have a public and a private ethernet connection, with the private at the top.
The 2 MDCs have only a private metadata connection. Our problem is this...
when we view clients in xsan admin, the Leopard client's public IP address is listed with a red ball next to it.
We cannot authenticate this client as the MDC has no public IP connection. How is this IP address being seen by the MDC? Other Leopard clients authenticate without a problem, the only difference being that their public IP address is 10.160.20.x. The clients that show up as red are 10.160.19.x and 10.160.16.x ranges.
Removing the public IP connection from this Leopard client will cure the problem and we can then authenticate, obviously over the private ethernet connection, however as soon as the client is booted with the public connected again, the same thing happens.
From the information given above, can anybody spot anything that is being done incorrectly?
Thanks.

Hi Bob, thanks for the reply.
Answers to your questions as follows.
1. Public IP ranges between 10.160.16.x through to 10.160.20.254
2. We have the metadata (Private) on top, not public, as per Apples guide.
3. It seems to be any Leopard client that is not on the 10.160.20.x range of public IP address. (The MDCs were on 10.160.20.x addresses before we removed them). Leopard clients are currently okay if they are on the 10.160.20.x range of public IP addresses.
4. We have tried running xsan admin from other machines and the problem still exists.
5. Both IP addresses of the MDCs are 10.160.21.48 and 10.160.21.49
Thanks
Richard

Clients don't appear in xsan admin

I have had my SAN working for a while now, and when I did the initial set up of clients, I made sure each had only one ethernet port active- the one that attaches the machine to the SAN. Once the clients were configured, and the Volume mounted, I re-enabled a second ethernet port so the users could access the internet, etc.
Now none of those clients show up in XSAN admin, although one does appear with it's IP address of the other subnet (not the metadata subnet).
The Volume is still mounted on these clients, though.
How can I 'bring them back' so I can keep track of things from the one machine I have XSAN admin installed on?

You want to see the Public IPs of your clients in XSAN admin. XSAN admin uses DNS over the public network to "find" the clients. Inproperly configured DNS is usually the culprit when XSAN admin takes a long time to bring up list of clients
Hope this helps.

After upgrade of hard drives in RAID, XSAN Admin sees wrong lun sizes?

So I purchased new 750GB drives for our XS RAIDS and I upgraded firmware to 1.5.1 C on RAIDS, but XSAN Admin sees wrong lun sizes. I have tried running XSAN 1.4.2 and even uninstalled on MDC and reinstalled back to 1.4.1 still no luck. Weird thing is that when I uninstall XSAN and then reinstall XSAN the lun names are still there in XSAN Admin, it is like they are stored in a file that does not get uninstalled when I uninstall XSAN.
I even upgraded the Firmware on the RAIDS again after the install of the new drives, the only drives that did not get upgraded were the 2 x 250GB set for Metadata Info on the first Raid Controller. I am running this on XSERVE non intel with OS X Server 10.4.11. I did not uninstall XSAN off any of the clients only the backup MDC.
I hope this info helps cause I could really use some tips from all you masters.
Thanks in advance
Jesse

Ok so I am a dumb *. All I had to do to fix my issue was delete the actual names of the Luns in XSAN Admin and hit enter and it updated the Lun sizes. Thanks everyone.

Xserve Xsan Client shows up mulitple times in Xsan Admin

I am seeing one of my clients showing up multiple times in my Xsan Admin under the Computers tab. Also under the Licenses tab I see that this Client's license is being used Multiple times.
So information of interest:
The Client is an Xserve (Early 2009) that has a Quad Fibre Channel Card installed in it. Though only two of its connections go to my Fibre Channel switch. Also, I have installed Xsan Admin on all of my MDC's, and they differ with how many times this server comes up. What I mean by this is on one instance of Xsan Admin, it will show up in the Computers tab 15 times, while on another instance it will show up three times.
Any help would be most appreciated.

I found that if you quit XSAN by closing the app and disconnecting from SAN and reconnecting next time you launch XSAN Admin, it refreshes these lists and clears the redundant entries. If you choose "quit xsan" from menu bar and don't disconnect, the multiple entries appear.

XSAN 2.2 Don't Show a Volume but Show a LUNs and When I click mount, XSAN Admin will Quit any time ?

Hi all
I'm a new staff for XSAN 2.2 , I have a ptoblem is XSAN Admin not show a Volume but Show a LUNs. and then I click Mount it will Quit a Window.
I test Import old Config file . It has a same thing.
please answer thx alot
^ ^

thank for solutions , I can't to see any Volumes when I click on "Volumes" on the left column of Xsan admin.
and last queston, Why a Xsan admin quit when I click a Mount on the left column?
^ ^

Xsan Admin misreporting free disk space

Is this common?
the 100GB volume has only 4GB in it yet Xsan Admin reports that there is only 14GB remaining.
Any comments?

Out of curiousity, why do have a 100 GB volume?
Sapridyne

Had to replace Xserve RAID controller and now I get Xsan Admin: duplicate LUN label RAID1-Left1

after we replace the controller volumes are mounting. Any advice on what to do with the duplicates?

Try reconnecting to the Xsan by closing the window in Xsan Admin, clicking "disconnect", then File -> New -> Connect to existing SAN. If you still see the duplicate LUNs after reconnecting, try shutting everything down and starting back up again in the order provided in this article: http://support.apple.com/kb/HT4027.

Had to replace Xserve RAID controller and now I get Xsan Admin: ERROR: duplicate LUN label RAID1-Left1

I need some help, I had one of my five Xserve RAID boxes fail. The upper controller card needed to be replaced and so we replaced it. But now only one of my volumes is loading and I am seeing the following error in my Console.
7/18/12 9:23:18.550 AM Xsan Admin: ERROR: duplicate LUN label RAID1-Left1
This raid box holds three LUNs. the left is split into two with one being the metadata / Journal for the main volume and the 2nd being the same for my secondary volume. The right side of this box is the second volume while the remaining 4 RAID boxes are my main volume. Here is the rub, the main volume is using the left1 LUN and the secondary is left2. The left2 is the one that is not working and when I go into the LUN info the WWN number does not match the actual id on the raid box.
HELP!!!!
Thanks,
Kevin Rosenthal

Did you try turning it off and on again? I mean, the full SAN shutdown/startup: http://support.apple.com/kb/HT4027
You're probably seeing "duplicate LUN labels" because the MDC has seen two LUNs with the same label but different serial numbers since it has been online. The serial number (which I think is based off the WWN) would have changed when the RAID controller changed. A reboot should fix that specific error message.
If the volume still doesn't start after rebooting, then you would want to check the cvlog for that volume.

XSAN Admin playing up!

Similar Messages

Maybe you are looking for