[rhcw]

One might build off site if the client wanted to see the SAN running off site for acceptance tests.

[rhcw]

I have not actually upgraded any XSRs in an XSAN to 1.5 myself, although I am tucking into one today, but there was a chap in Germany who was suffering terribly with RSCN on an XSAN when clients were shut down or rebooted. He contacted me as I had posted similar issues in the summer (solved by turning off device scan using XSR 1.3 firmware). His problem turned out to be settings on the XSR settings – I think it was the host cache flushing and you are right the settings changed every time the XSR was rebooted.

[rhcw]

Don’t forget that as well as setting the streamguard and device scan correctly on all the switch ports you need to also be careful how you set the XSERVE RAID cache settings etc. This only became an issue with 1.5 FW and Admin. If you get this wrong then you will see RSCN behaviour when you shut down clients and reboot clients.

[rhcw]

[QUOTE BY= maccanada] IP addressing – yes there are several files living in /Libray/Filesystems/Xsan/config with IP addresses in them. Changeip was never designed for an Xsen environment so changing IPs can get messy. Like you say, best to make sure the initial IP is a permanent one.
~Ian[/QUOTE]

Are we saying that changeip will work but will do you no good if it is an MDC on which you are changing the IP after the fact?

On a related subject, lets say you set the IP to 10.0.0.2 and use a DNS that is good for the off-site location where you are pre-building. What bad things happen when you finally install on site and leave the IP alone but have to change the DNS to the one that is correct for the new network?

[Author]

Posts