Xserver+XRaid+SMB+DHCP = failure

I have basic services running on my xserver (DHCP/SMB). I have basic permisssions set up. but everyone has full access to the entire share. Some of my Windows XP users are getting errors when trying to access files on the shares. Random, but it happens at least once a day for different users.
Can anyone expierance this? Any reccomendations?

My bad - they do still offer the fiber channel cards.
http://store.apple.com/us/product/MB842G/A
It comes with the cables you need (as long as you're not mounting the RAID a long way from the server.

Similar Messages

Since update to 10.5.6 can't write to XServe/XRaid

Since updating several Mac Pro workstations to 10.5.6 from 10.5.2 We can't write to our XServe/XRaid running 10.4.10. We can read files off the server but any attempt to write to the server results in the file copying 4 to 44kb of data then hanging. Other machines running 10.5.2 have no issues.
I have checked permissions on the XRaid, repaired permissions on the workstation, created new users on the workstation, created new users and folders on the XServe/XRaid and nothing changes.
As soon as the file starts to copy onto the server the user connection changes to asleep/disabled.
I would like to roll back a 10.5.6 machine to 10.5.2 to test if the update has buggered something up but am unsure what the best method is for doing this. Any assistance would be appreciated.

There are two methods you can use: Archive and Install or Migration Assistant.
http://support.apple.com/kb/HT1710
Migration assistant requires access to a bootable clone of the workstation you wish to roll back or a
Time Machine Backup of the workstation that you wish to roll back, for migration to take place and
successfully transfer your original apps and settings to a fresh OS X install version of your choosing.
If any of the other workstations are similar (same apps and settings), you also have the choice to
migrate apps and settings from one of those machines via firewire or network.
Kj

SMB Authorization Failure

I'm seeing lots of SMB Authorization Failure events being reported to MARS from IPS signature 5606/0. I strongly suspect that these events are false but I don't know a lot about SMB. The Event Type Details in MARS states "This signature detects when three or more consecutive failed Windows NT (or Samba) user authentication within a single SMB session..." However, the Event Count parameter of 5606/0 is set to the default of 1. Should this be bumped up to 3 or am I smoking dope? Should I be looking at other areas of the signature definition?
Any help would be appreciated.
-Frank

Frank,
The documenation wasn't updated when we updated the SMB engine, so its not working on the "three strikes" principal. The current functionality is to alarm on the first instance and then go into summary mode. You can have it alarm after 3 instances by bumping the event count to 3. You can cut down some of the noise by adjusting that value.
Additionally, the event tracking key is currently AaBb, which means that it will track the events on a full Quad (Src IP/port & Dst IP/port). In this case the Dst IP/port are always the same (your server), so if an attacker uses a tool that uses the same port over and over, you'll only get the one alarm then summaries later. If its parallel in its operation and uses multiple ports, you'll get an alarm per SrcIP/port. Generally I'd keep the summarization key in step with the event key for this signature. I'm not suggesting that it needs to change or anything, just letting you know what it does.
Generally this alarm will fire every time someone fat fingers their window's password or attempts to access a protected share that they don't have permissions on. I will recommend this signature to the signature team for a review of its settings in a future update.

Recommended annual maintenance for xserve/xraid

hello everyone,
i'm coming up on the one year mark for our company's xserve/xraid which serves as a file server and publishing database (mei/k4) for the campus newspaper at NU. really it's been working splendidly, but just recently having come over from os9 (it's publishing people!) i'm ignorant of what annual maintenance is appropriate for the xserve/xraid/osx server in terms of running disk warrior/repair permissions/etc OR should i just let everything be? i'm used to performing a major tune-up every quarter!
osx 10.4.11, server HDs are mirrored and the Xraid is raid 5.
thanks for the advice!
ez chris

Completely agree with the concept, unless the security updates are relevant to your services and your servers are facing the Internet (like web/email/ssh, etc.).
That's for sure - although relevant security updates certainly falls in the 'broke' category and worth a reboot unless you can work around it another way. In my case, though, most of my servers are running custom Java applications and Java updates are the ones that I'm most interested in.
Camelot. Not to hijack the thread to ask something unrelated, but in an old thread you mentioned having some Xserve G5 hw raid cards available. Is that still the case? Am very interested...
Sure. email me - camelot at mac.com

Xserve + XRaid +MacPro

Hi guys!
Here is my setup.. I have a Xserve, a Xraid and a macpro. The xserve has a quad-channel fiber channel card. I want to connect 2 of the channels to the XRaid and the other 2 channels to the MacPro (to share the Xraid via Xserve). The remaining computers on the network will connect to the Xseve (and xraid) via gigabit ethernet. Is this setup possible? Thanks in advance!

This is not possible. The four ports on the XServe's fiber channel card are not a fiber channel switch. At best the MacPro would see nothing, at worst it would break the entire fiber channel setup and neither machine would see anything.
Unless the MacPro is directly connected to the RAID via its own fiber channel card or a fiber channel switch it'll have to connect through the XServe's network.
Note that even if you do get a fiber channel switch you can't connect both hosts to the same RAID volume at the same time without implementing something like XSAN. On its own fiber channel doesn't allow for this. You're OK if you want the XServe to see one volume and the MacPro to see the other, but if you want them to see the same volume then you're out of luck there, too.

Really Need Help Please! Xserve XRAID Volume Keeps Unmounting

I recently had a 14 Drive Apple RAID drop a drive and I immediately replaced the bad drive with a new drive so it could rebuild. Drives 1-7 are RAID5 handled by Upper Controller and Drives 8-14 are RAID5 handled by the lower controller. The Xserve is running Leopard Server 10.5.8.
I noticed the next day before the rebuild was almost done that the Volume had unmounted and didn't think much of it until the RAID rebuilt successfully and I rebooted everything to sync everything back. I thought all was good until the Volume on drives 1-7 started to unmount by itself. It will not stay up for more than 15 minutes. If I reboot the RAID or Xserve it always comes back.
I tried different cables, different ports on the Fibre controller, swaped different RAID Controller cards and even moved all the 7 drives into a different RAID chassis and the problem always follows the 7 drives in question, which is drives 1-7. I've just finished a parity rebuild, which did not help. I'm running another parity rebuild right now.
I would copy the data off onto the RAID which is identical but the Volume that the data is on won't stay mounted long enough to start and substantial copying of data.
I've looked at the console logs and RAID Admin logs, which didn't help much. I'm really at wits end and do not know what to do at this point. I believe the issues is not card, cable or chassis related but part of the 7 drives but don't know how to fix this issue. This problem only started after one of the drives had failed in drives 1-7.
Any help would be greatly appreciated.
Thank you!

Hi,
Couple of quick questions for you.
1) What drives do you have in the Xserve RAID?
2) What error does RAID Admin pop up? Is it Controller 1 Communications Failure?
3) If you look at the Console does if have an error in there Flushing FS disk buffer returned 0x5?
All the best
Beatle

Xserve/XRAID to HP Tape with Retrospect. Problems?

We have a quad core xeon xserve connected via fibre to an XRAID with ~2TB of data. If the data is lost we're in trouble. We have a used HP StorageWorks 1/8 Ultrium 960 Tape Autoloader we can use for tape backups. I found that EMC Retrospect can work with this particular model, but we'll need to purchase a SCSI card to connect it to the Xserve.
My question is; What problems, if any, should I anticipate having with this configuration? I've heard SCSI can be a nightmare, but is it ok under Leopard Server? Is Retrospect the best/easiest option here? Anything else you can add with regards to this would be very helpful. Thanks

Ultra 320 SCSI? I tried to install the card, but I misunderstood the manual which led me to believe I had a PCI-X and PCI-E riser card in the server. Apparently since we got it from Apple with the fibre card it came with two PCI-E risers. So, we now have to order the PCI-X riser in order to install it.
The card came with no real documentation beyond the pages from the server manual showing how to install the card and that to configure a SCSI card you would need to use Disk Utility. At any rate the tape autoloader has a terminator on its second port. Would that normally be enough or would I need another one on the expansion card's second connector too?
And a terminator isn't brand specific is it? I would imagine we have some laying around from HP hardware we use. Would that be usable?
Thanks

Xserve RAID using DHCP - DNS field = 127.0.0.1

I have four Xserves all getting a static IP address from a 10.4.11 OS X Server.
They get the IP address, subnet mask as well as gateway address correctly from the DHCP server BUT the DNS server address is NOT populated - it displays 127.0.0.1
All the other clients on the LAN DO get the DNS server address.
NB All RAIDs are updated to latest firmware (1.5.1 IIRC)

Hi,
Ping localhost is a loopback process to verify the TCP/IP is configured correctly on the local computer. So, the TCP/IP configuration or stack contains a corruption, first, I would suggest you check you check you TCP/IP settings, reset the
TCP/IP stack by using NetShell
http://support.microsoft.com/kb/299357
Since the Ping is timeout via ipv4 but Ok via Ipv6, so it's also recommended to just reset the ipv4 setting via the following command and check the result
netsh interface ipv4 reset
Yolanda Zhu
TechNet Community Support

Netctl: Retry connection on DHCP failure

So I'm in the following situation:
Our university wireless network often has DHCP issues and it takes thousands of millions of retries until you finally get an address. The problem is, netctl-auto doesn't retry to connect to the network on a failure. It just stops doing anything.
Is there a way to get netctl to retry a profile until it's working when there are no other networks in range configured?
Wolle

Anyone looking at this should check this thread: https://bbs.archlinux.org/viewtopic.php?id=190141
Basically, it boils down to adding "-b" switch to dhcpcd.

Xserve RAID - Multiple drive failure.

Morning all,
An Xserve RAID I have been called to take a look at is behaving rather erratically! Here's the chain of events over the last 3 days:
(4 x 180GB - RAID 5)
- 2 folders (the largest in size) suddenly appear empty. The capacity and available space do not change.
- Some remaining files and folders appear corrupted / incomplete e.g. Quickbooks company file.
- Data Rescue appear to recover all data, missing files are recoverd as "orphaned" files.
- DRIVE 1 FAILS showing red light and disappearing from RAID admin.
- RAID set shows "degraded" but still accessible due to RAID 5 config.
- Replace drive 1 with 750GB Apple supplied drive.
- RAID 5 set rebuilds automatically showing green and "online"
- missing files in the 2 large folders still appears missing.
- DRIVE 2 FAILS
I believe the chances of 2 drives failing in such short succession are extremely small and I now thing that drive 1 is probably ok and that something else is at fault here.
Xserve RAID is on the latest FW 1.5.1 and no other errors are present.
Can anyone shed any light on this, could it possibly be the controller ?

The act of the rebuild could have been enough to push the second drive over the edge.
I would say... if the Xserve RAID has been running 24x7 since you purchased it, you may want to consider replacing it. The 180 GB drives were discontinued almost 5 years ago from what I recall... 5 years of constant use is really a long, long time for had drives. It's more typical in data center usage to replace drives after about 3 years of use (even if their MTBF is 500,000+ hours, those numbers are rather meaningless). Hard drives fail on a "bathtub curve," where once you get to the far end of it the odds of failure are great, and lots will fail around the same time. You can't rely on the Xserve RAID to run 24x7 for 10 years, or you'll definitely have problems. There is no RAID on the planet you can expect to run for 10 years without issues with the drives... even if you're using $1500 apiece fiber or SAS drives.

Windows XP SP 2 DHCP failure connecting to OS X Tiger Server

Hello,
Standard setup for DHCP Server on OS X Tiger Server... latest version. Mac's acquire 192.168.7.x just fine from OS X Server. When XP SP2 client attempts, shows self-assigned ip and subnet. Looking at the DHCP log in Server Admin, the server sees the xp client discover message, offers a response to the xp client, but that is it... no request for DHCP configuration information or acknowledge. If I go wireless, 10.0.0.x with XP, does fine as does the mac clients. What am I missing. Turned off the firewall, same scenario for DHCP through OS X Server. If I plug in the XP client directly into the cable modem, works fine for DHCP also. I've done some searching on the net for some info, unable to find any info that helps. Any help on this would be greatly appreciated.

Add some setup info. en0 is the static ip address for the server to the cable modem... 10 static. Using en1 as the DHCP server 192.168.7.1. Network consists of 10/100 switches. Standard DHCP settings in SA. IP range from 192.168.7.2 thru 127 using en1. DNS is set to 192.168.7.1. LDAP is configured and works fine with Open Directory on. I do have WINS set to our en0 static ip address for the server, but Windows services in SA are off. That is the DHCP settings in SA. Any info and help would be greatly appreciated.

Recovering from DHCP failure

Hi
I am on Windows 2008. Just wondering what kind of problems I can get into if my DHCP server fails. We are backing up the DHCP DB once a day and the lease period for some odd reason has been set to 1 day.
For the sake of discussion I want you to assume that I backed up my DB yesterday at 6 PM and my DHCP crashed today at 4 PM.
I can restore from my backup. But the entries in the backup could be stale.
There could be some IP Address that was allocated by the DHCP server today at 2 PM but is see as available in yesterday's backup. Post restoration, the server could try to lease out that IP Address to some other system. (I assume that the system that got
the address at 2 PM would not contact the DHCP server again until 2 AM in the morning (50% of its least period)
There could be some IP Address that was assigned to some system at 3 PM (just before the crash) or not assigned at all but the backup taken yesterday could show the IP Address against a different system with active lease. In this case, if I try to use the
DHCP log to identify a system on the network then I am likely to reach the incorrect system.
Is there some kind of reconciliation option where the DHCP could force all the clients to renew leases to get to some consistent state of the network?
Thanks
-GW

Hi,
Windows Server 2008 DHCP has both server-side and client-side conflict detection to prevent duplicate IP addresses on your network.
Client conflict detection
Client computers running Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, Windows 2000, Windows NT 4.0, Windows Millennium Edition, and Windows 98 automatically check to
determine if an IP address is already in use before using it.
After the DHCP client receives a lease from the DHCP server, the client sends an Address Resolution Protocol (ARP) request to the address that it has been assigned. If a reply to the ARP request
is received, the client has detected a conflict and sends a DHCPDecline message to the DHCP server. The DHCP server attaches a BAD_ADDRESS value to the IP address in the scope for the length of
the lease. The client then begins the lease process again, and is offered the next available address in the scope.
Server conflict detection
If your network includes older DHCP clients that do not perform conflict detection themselves, you can enable conflict detection on the DHCP server. By default, the Windows Server 2008 DHCP Server
service does not perform any conflict detection.
To detect conflicts, the DHCP server pings (sends an ICMP Echo message to) an IP address before offering that address to clients in a new lease. The DHCP server only pings addresses that have not
been successfully and previously leased. If a client requests a lease on an IP address that it already had or is requesting a renewal, the DHCP server does not ping the IP address.
If conflict detection is enabled, an administrator-defined number of pings are sent. The server waits 1 second for a reply. Because the time required for a client to obtain a lease is equal to the
number of pings used, choose this value carefully because it directly impacts the overall performance of the server. In general, one ping is sufficient.
If a response to the ping is received, a conflict is registered and that address is not offered to clients requesting a lease from the server. The DHCP server then attaches a BAD_ADDRESS value to
that IP address in the scope. The DHCP server then tries to lease the next available address. If the duplicate address is removed from the network, the BAD_ADDRESS value attached to the IP address
can be deleted from the scope’s list of active leases, and then the address returns to the pool. Addresses are marked as BAD_ADDRESS for the length of the lease for which the scope is configured.
If the BAD_ADDRESS entry is not manually removed, it will automatically be removed after a period of time equal to the lease time for the scope.
Note: In general, using server conflict detection only as a troubleshooting aid when you suspect that duplicate IP addresses are in use on your network. Each additional conflict detection attempt
adds to the time required to negotiate leases for DHCP clients.
Hope this helps.
Steven Lee
TechNet Community Support

Linux Debian 6 (Squeeze) DHCP failure

I have a Cisco/Linksys E2500 router. I connected to it through one of the Ethernet ports with a Microsoft Windows XP Pro machine and installed and ran the setup software. Windows was able to connect to the router and to the internet through the Siemens Gigaset 4300 DSL modem to my internet provider, Windstream.
I cannot get my Dell GX620 which is running Linux Debian 6 (Squeeze) to connect to the router through the Ethernet ports.
It appears that I receive no reply to the DHCP requests made by Linux.
I am open to any suggestions. I have only one monitor, keyboard and mouse and no KVM switch to run both the machines at once. I do have Windows XP Pro running in a VirtualBox virtual machine on the Debian machine if that might be of help.
I can configure Debian to a static IP if I knew all of the IP configuration that the E2500 would assign. I would also need to know what reconfiguration the router requires if I use a static IP.
Thanks in advance for any assistance.

If the router’s IP is 192.168.x.1, you can use any IP from 192.168.x.2 to 49. It would not create an IP conflict since the DHCP range of the router is from 192.168.x.100 to 149. As for the DNS servers, you can copy the same DNS that your Windows PC is getting from the router.

Wrt310n packet loss and dhcp failure?

I purchased a wrt310n to replace a netgear POS (which was a temp after my wrt54g died) and I'm having issues. The netgear is slow and temporarily freezes every once in a while. I put the wrt310n in and it worked flawlessly... for about a week. Now I'm getting packet loss between 10% and 20%. Also, after leaving the router running for a couple days (upside down, because it seemed to be freezing when it got hot) it would work for 5-10 minutes and then freeze. Power cycle the thing and... repeat.
I'm only using WEP, the machines have 802.11g cards, I've changed the network to 10.4.2.x (only the private side) and left almost everything else stock. The other things that have been changed are the admin password and logging has been enabled. My ISP is comcast cable. Suggestions? More info required? Anyone know how long 'til DD-WRT will work on these things?
ps-just so my skillset is known, i'm a sysadmin for a very large tech company and have been doing this type of role for over 8 years... that puts me slightly above the average home user... i think...
pps-mixed network of Linux and Windows machines
Message Edited by junk on 01-23-2008 06:47 PM

Nothing yet. I've switched back to my Netgear, for the time being. I'm hoping Linksys actually reads these forums and has a firmware update coming out soon. The Netgear works great until you hit something with a lot of jpgs (like myspace) and then it chokes for a couple minutes. I can deal with that until the first firmware update shows. Hopefully it's soon, since I hate having to box things up and send them back. I've read a few other posts about people having problems and they suggest doing a factory reset. I always change my network over to a 10.x.x.x subnet because I like to avoid common RFC1918 address spaces (geek/hacker issues). Perhaps it doesn't like dealing with class A address space...

IPad Wi-Fi DHCP failure

My iPad's WiFi connection has just stopped working since a couple of days ago. It can connect to WiFi access point. However, it fails to correctly obtain its IP address and other related information such as mask, DNS, and others. So, it shows full bars on the top of screen, but cannot connect to Internet at all. I had used the Internet connection and hasn't changed any network related option at all. It just stopped working. I've even tried to connect to several different wireless access points, but its symptom is same. So, I do not think that it's a specific wireless router problem.
I've reset its network setting; furthermore, I've done with "Restore". Even in the original factory setting, it shows me the same symptom. Is it a hardware problem?

JimHdk wrote:
Those other discussions aren't really relevant and millions of users are using 3.2.2 without WiFi problems. (3.2.2 didn't contain any WiFi changes vs 3.2.1)
It's not true. It IS RELEVANT. A few guys actually complained the same problem as mine. They had used their iPad with a WiFi connection without any problem for a while, but suddenly got a problem. Furthermore, "millions of users are using 3.2.2 without WiFi problems." doesn't necessarily mean that the OS doesn't has any bug related to WiFi in it. It might not be specific to 3.2.2 only, though. If millions of users using 3.2.2 had a problem with WiFi, this bug would be pretty easy one to catch. Apple must already fix it.
In the linked forum, one of guys said that changing brightness setting is related to some WiFi connection problems. Last night, I tried to change the setting several times; then, the WiFi connection in my iPad suddenly worked. However, when I reset the iPad to make it sure, it didn't work again. I desperately tried lots of different trials, so I couldn't repeat what I did with the brightness setting. So, now it still doesn't work.
I cannot rule out the possibility of hardware fault in my case. However, based on my little experiment which I mentioned, it seems to be more like some bug in the OS.
Message was edited by: Youngsang

Xserver+XRaid+SMB+DHCP = failure

Similar Messages

Maybe you are looking for