Recent Comments

  • Reply to: Notes on Xsan4   5 days 19 hours ago

    Thanks for the reply. Unfortunately, our test san has only one volume and 2 mdc units. Was hoping someone had run across this. Will have to dig further. Thanks again.
    Glenn

  • Reply to: adding client machine into xsan 3.1   1 week 2 days ago

    ahh no wonder! appreciate your response

  • Reply to: Notes on Xsan4   1 week 2 days ago

    I don't know the answer to this question. Have you tested an upgrade of multisan to see what happens?

  • Reply to: adding client machine into xsan 3.1   1 week 2 days ago

    That would be the right assumption as it was the case with previous versions too. In summary, the metadata network needs to be on the same vlan so that the backend protocols between MDC and Client stations work properly, if you have different vlans for that then there is no way to guarantee that the messages will go across vlans. Even if the ip looks really close, the vlans are similar to islans isolated to each other so the machines can't really see each other.

  • Reply to: Notes on Xsan4   1 week 3 days ago

    We too have a large multisan with 13 volumes hosted on 5 mdc pairs. With the new Yosemite version, I don't see any way of creating a multisan setup. It appears that all volumes will be hosted by all mdc. Has anyone found a way to specify which volumes are hosted on a given mdc pair?

    Thanks,
    Glenn

  • Reply to: Notes on Xsan4   1 week 3 days ago

    abstractrude wrote:

    With the new Xsan 4 admin model, you don't need static addresses on the public network.

    /quote

    Thank you for the information! That's what I assumed since it pulls rather than the server pushing the configuration, but I just wanted to make sure.

  • Reply to: Notes on Xsan4   1 week 3 days ago

    With the new Xsan 4 admin model, you don't need static addresses on the public network.

  • Reply to: Notes on Xsan4   1 week 3 days ago

    Quick question on Xsan 4. Under Xsan 3 it was my understanding that it was the best practice (or necessary) to set static IPs for the client machines under Xsan Admin. I have my current machines all on static IPs for the metadata network and the primary network and everything is running successfully under Xsan 4. However, I'm looking to add four more devices to my SAN and am wondering, with the new profile method, whether static IPs are necessary on the primary network. I have no problem setting statics on the metadata network, but the IT department at this location is always reluctant to give out additional static IPs so if it's not necessary I would prefer to just let the new clients use DHCP on the primary network. Thanks for the help, there's just so little documentation on Xsan 4 I'm a little more in the dark than I was with previous versions.

  • Reply to: Notes on Xsan4   1 week 4 days ago

    For moving a volume configuration around? Have you thought about setting the mounts via the fibre channel system preference pane, then copying it around to the clients...

  • Reply to: XSAN: No visible Luns   1 week 4 days ago

    Good to hear. Happy xsaning.

  • Reply to: adding client machine into xsan 3.1   1 week 5 days ago

    error message:

    network configuration required
    the computer XXXXXX requires manual network configuration to be added to the SAN. You need to assigin it an address on the metadata network (10.244.128.0/24)

    does this mean that client and Xsan needs to be on same network vlan? basically on 10.244.128.XXX and not two different vlan 10.244.128.xxx and 10.244.40.xxx?

  • Reply to: XSAN: No visible Luns   1 week 6 days ago

    Hello Trevor,

    it worked. After I run the cvlabel command pointing to the file with the correct labels, the two volumes immediately showed up. I rebooted and then turn on all the other computers in the xsan and the volumes mounted on all of them.

    Thank you Trevor for your help. You are great. It is very difficult to get support arround here and we can only count on people like you in difficult situations like that.

    Again thank you for your time, efforts and paintiense.

    Kind regards

  • Reply to: Notes on Xsan4   2 weeks 1 day ago

    Thanks for the quick response.

    I'm very interested to know when will be available to use Yosemite Clients under our Stornext SAN Metadata enviroinment.

    When you say that Yosemite is running on 4.3.2 are you meaning over a metadata controlers in that version?? So in fact I only need to upgrade my Stornext system to that version?? And finally this will works with the preview Xsan Clients (2, 2.2, 3,...)

    Thanks a lot.

  • Reply to: Notes on Xsan4   2 weeks 2 days ago

    This would be unsupported but earlier clients are not locked out of the FSM. So things should work no problem. Of course the software on the client has to support the volume featureset.

    Yosemite is running 4.3.2 though, let me ask someone for a better answer.

  • Reply to: XSAN: No visible Luns   2 weeks 2 days ago

    We built a new label file
    XsanLUN2 /dev/rdisk3 # host 1 lun 0 sectors 30701535 sector_size 512 inquiry [easyRAIDERP16R-8FR3 0001] serial 2465000612666464
    XsanLUN4 /dev/rdisk5 # host 1 lun 0 sectors 19507167 sector_size 512 inquiry [G-TECH G-SPEED -VOL#00 R001] serial 001B4D280000E37A
    XsanLUN1 /dev/rdisk4 # host 1 lun 1 sectors 54662619103 sector_size 512 inquiry [easyRAIDERP16R-8FR3 0001] serial 2264000612336438
    XsanLUN3 /dev/rdisk6 # host 1 lun 1 sectors 27324196831 sector_size 512 inquiry [G-TECH G-SPEED -VOL#01 R001] serial 001B4D280100E37A

    cvlabel filename