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 ....

Similar Messages

Using Xsan Admin with StorNext MDCs

This is an area I'm a little shaky on... anyone know if, when using a Stornext MDC, if I can install Xsan Admin on Clients, be able to connect to the SAN and look at Graphs (IP Network Traffic, CPU Usage, Fibre Network) for the clients? I'm guessing probably not, but I wanted to throw out the question anyway...
Thanks,
Sapridyne

Unfortunately you can not. The other way around does not work either, you never see the traffic that a StorNext client makes.
jotjot

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 ?

Problem when try to use ACSE+ Windows AD to authenticate two kind of WLAN c

I met a problem when try to use ACSE+ Windows AD to authenticate two kind of WLAN clients:
1. Background:
We have two WLAN: staff and student, both of them will use PEAP-MSCHAPv2, ACSE will be the Radius server, it will use Windows AD's user database. In AD, they create two groups: staff and student. The testing account for staff is staff1, the testing account for student is student1.
2. Problem:
If student1 try to associate to staff WLAN, since both staff and student WLAN using the same authentication method, the auth request will be send to AD user database, since student1 is a valid user account in AD, then it will pass the authentication, then it will join the staff WLAN. How to prevent this happen?
3. Potential solution and its limitation:
1) Use group mapping in ACSE(Dynamic VLAN Assignment with WLCs based on ACS to Active Directory Group Mapping), but ACS can only support group mapping for those groups that have no more than 500 users. But the student group will definitely exceed 500 users, how to solve it?
2) Use methods like âRestrict WLAN Access based on SSID with WLC and Cisco Secure ACSâ: Configure DNIS with ssid name in NAR of ACSE, but since DNIS/NAR is only configurable in ACSE, don't know if AD support it or not, is there any options in AD like DNIS/NAR in ACSE?
Thanks for any suggestions!

I think the documentation for ACS states:
ACS can only support group mapping for users who belong to 500 or fewer Windows groups
I read that as, If a user belongs to >500 Windows Group, ACS can't map it. The group can have over 500 users, its just those users can't belong to more than 500 groups.

Problem when try to use 2 computers

Hello there.
I'm now facing a problem when try to use 2 computers. Specifically, I downloaded my ebook (pdf form) in my laptop and open it without problems. But when I tried to reopen the same book (from human kinetics site) to my pc, the known message revealed ("E_LIC_ALREADY" etc etc).
As I realised, in my laptop, the ADE wasn't authorized (in fact, "is authorized without an ID"). I tried but didn't achieve to authorize it (it's not accepting my username and password, saying that the specific ID is already used, obviously when I made the similar procedure on my pc, a year ago), whereas I'm also not able to re-open the book in my pc (I made copy-paste to the appropriate folder of my pc, by the way...). What's the solution in this case? I mean, it's very annoying for me and I desperately want to solve it...
Thank you in advance,
Nikolas

Answer 1 : Really not quite sure about this ....
Answer 2 : turn the card upside down and check the model number .. the model number would be WPC54G and if there v2/v3/v4 after it it means that the card is version 1 ....
Answer 3: As you windows xp , go to start >> programs >> uninstall wireless notebook adapter.... insert the CD for the adapter ...take the card out and insert it back again.... follow the instructions on the found new hardware wizard ... this will install the drivers for the adapter and then you can use the windows wireless configuration utility to connect to the wireless network ....

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.

Newbie XSan question - authenticating a computer from XSan Admin

Hello - I have a very newbie XSan question!
I have 2 computers that connect to an XSan. 1 I am having no problems with. The other I am unable to connect with.
When I look in XSan Admin the 2nd computer (the one that is not working) is not authenticated.
So I click on it and choose Authenticate. I enter what I know is an Admin username and password for the computer I am attempting to connect. The dot next to the computers IP turns green with 3 dots in it and then it turns gray again. It just does not connect.
What is the problem?
Is it licensing?
Thanks
Taj

You need a different license ID for each machine, plus the admin machine. Do you have that?

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?

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.

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.

How to edit the Authorisation DB (authenticate-admin, the authenticate-admin-30 or the authenticate-session-owner-or-admin)

Hi,
Since i updated to os 10.9, i had to change my script which helps me to create a powerusers group, which has more rights than a normal user. It was no problem to change in the most rules the group key from admin to powerusers. I did this with the help of the security authorizationdb and the plistbuddy command. What I do not understand is why i can't change anything in the authenticate-admin, the authenticate-admin-30 or the authenticate-session-owner-or-admin rule. Anyone has an idea? I used the following command:
security authorizationdb read authenticate-admin > /tmp/test.plist
/usr/libexec/PlistBuddy -c "Set :group powerusers" /tmp/test.plist
security authorizationdb write authenticate-admin < /tmp/test.plist
The first two lines work ok but it won't write it back into the auth DB. The same command even won't work if i leave away the second line and change nothing in the plist file. Does anyone has tips or ideas how to resolve this? or inputs why it doesn't work?
Thanks for your help!!

Thanks for the link. I used it for my script and was able to change the group in a lot of rules from admin to powerusers. For example:
security authorizationdb read system.preferences > $mod
/usr/libexec/PlistBuddy -c "Set :group powerusers" $mod
security authorizationdb write system.preferences < $mod
This works fine. I could change 25 rules with it. But the rules authenticate-admin, authenticate-admin-30 or authenticate-session-owner-or-admin can't be written back into the authorisation file and I don't know why. I used exactly the same code that I used for the other rules.

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

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.

[SCCM 2012 R2] - IBCM - Authenticate computers on TMG from another forest

Hi All,
There is no article on TechNet that describe client certificate requirements for computers in another forest.
Scenario:
We have Domain A [aaa.bbb.ccc] and Domain B [111.222.333] and those domains are in different forest. There is "Forest" trust between forests.
TMG and IBCM site server are in Domain A and computers authenticate successfully from Internet to TMG using SSL client authentication. Problem are computers from Domain B that cannot authenticate to TMG.
We used old documentation
https://technet.microsoft.com/en-us/library/cc707697.aspx#AppendixA for SCCM 2007 and ISA without success. I created certificate for computers in Domain B with custom
SAN:upn=<hostname>$@<domain.tld> and TMG still cannot authenticate computers from Domain B.
Please help.
Thank you in advance.
Regards,

There's no difference -- ConfigMgr does *not* care about forests, domain, or trusts for client authentication and neither does certificate based authentication.
The certs in use, both the client auth and server auth certs, must of course be trusted by the site systems and the clients and in this case the TMG server -- that's simply how certs work though and has nothing to do with ConfigMgr. Additionally, the CRLs
for the certs in use must be accessible to the clients and servers via an accessible CRL DP but that is also simply how certs work.
For what you've described above, does TMG trust the certs issued to the clients? In other words, does it trust the CA that issued those certs and can it access a CRL for that CA?
Jason | http://blog.configmgrftw.com | @jasonsandys

Can not connect using Server Admin - server running.

Hi there, can anyone help me?
I am running OSX Server Tiger on a Mac Pro G5. It has worked perfectly for several years.
Suddenly I cannot connect to the server using Server Admin either locally or remotely - the machine continues to function perfectly. The only problem is that I can not make any changes and I am nervous! I would prefer not to reformat and reinstall.
I did have some network problems a while ago which meant that I changed some IP numbers manually, and I installed and de-installed an ADSL modem.
I am hoping that deleting a library here or there will solve the problem. Any ideas?
Thanks, Drew

Last time this happened to me I deleted the server from Server Admin and re-added it

Problem in authenticate computers using XSAN admin

Similar Messages

Maybe you are looking for