Jump to content
SNS Users' Forums
  • Announcements

    • Eric Newbauer

      Forum closed   06/30/2018

      PLEASE NOTE: This forum is closed and no longer moderated. Please visit https://www.studionetworksolutions.com/support/ for assistance with your SNS products. Follow Studio Network Solutions on Twitter. Thank you!

Joseph Behrens

KB Moderators
  • Content count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Joseph Behrens

  • Rank
    Member

Profile Information

  • Gender
    Male
  1. The latest version the lab has tested is 17A306f. Using that release along with the latest public releases of globalSAN (registered) & SANmp (available at http://www.snsftp.com/), we ran an upgrade to PB3 (17A315i). Leaving iSCSI error-checking enabled, and with "Allow Unconverted SAN Volumes (AUSV)" off, there did not seem to be a problem. We also tried with AUSV on without trouble. Given "High Sierra" is still early in beta, we have not done a great deal of deep testing (such as upgrading from one beta to another). Make sure you are on the latest version of globalSAN. If you still have trouble, please open a ticket as HAL suggested. We will likely prompt you for some log files. It would also be useful for us to know what Mac you are using (eg: MacPro6,1 Late 2013), what iSCSI target you are using, SAN software in use, iSCSI LUN partition type and format, topology to the target, and if you are running OSX on HFS or APFS. Regards, Joseph
  2. Andy, I just noticed Hal had been discussing this with you on the support line. Please look for updates there. -Joseph
  3. Connect to the VLAN first, then add the iSCSI portal. Operation of globalSAN is then as it would be on a local network. Once you have added the portal, the list on the left should populate with available LUNs. Select one of the LUNs, and the list on the right side should show the available paths. select which path(s) you would like to use and hit connect. For the record, using iSCSI over a wireless connection or over an internet connection is not recommended.
  4. You should also keep in mind that the CLI and GUI will act as two different clients. You can not log in from one while connected to another. That behavior can be overridden, but we do not suggest it.
  5. You could just make a BASH script that runs at startup. Those instructions are meant for the CLI, but they can be worked into an Apple script by calling a shell command. Given the following: User=dennis Password=123ABC Volume = PAV018DR5 Your BASH script may look something like this: #!/bin/bash /opt/local/bin/SANmpClient login dennis 123ABC sleep 1 /opt/local/bin/SANmpClient mount volume "PAV018DR5" RW exit You would also want to add a script for logout. #!/bin/bash echo y | /opt/local/bin/SANmpClient logout exit (the "echo y" is to automate the verification of the logout)
  6. Hello Todd, Sorry for the late reply here. We have some questions: What OSX version are you using? What version of globalSAN are you running? --If you are running a version previous to 5.1.0.336, please get the update from snsftp.com. Please be sure to uninstall the old version first. Are you directly connected to the Synology, or are you running through a switch? --If you are running through a switch you may want to bypass it as a test. If this does not get you moving, please feel free to open a support case by emailing us at support@studionetworksolutions.com. Thanks, Joseph
  7. Lost Share Drive, how to get it back

    As an update to anyone with this problem: We had to force off the EVO, and remove / replace the mapping from the EVO UI once it was back up. The system had been up for 11 months without a reboot, and we have not yet determined why the share stopped working. If anyone is having the same problem, make sure all users are logged off, and initiate a reboot from the Web UI. If it is unresponsive, make sure all users are logged off, and force-off the system with a long-press of the power button. Once the system is rebooted, check on the status of the shares from the Web UI. On the 'iSCSI Target' page, select checkbox of the problematic volume, then click "Remove Selected Targets" below the list of targets. Afterward you will remap the target by selecting it from the "Volume for iSCSI target:" drop-down menu (modifying the name if needed) and clicking 'Create iSCSI Target'. After a few moments you will receive a message stating the volume was mapped. Once this is done, you will likely need to remove the troublesome target and re-establish the link to the portal IP on connected workstations. As always, please contact us at http://support.studionetworksolutions.com if you are having trouble.
  8. Intelligent bandwidth control

    This is a duplicate topic, please see http://www.snsforums.com/index.php?showtopic=579.
  9. The easiest way to remove the software is to use the original installer to uninstall. Do you know what version you were running? you may want to check http://www.snsftp.com. -Joseph
  10. WTB- SNS Ellipse 2Gb PCI-X HBA

    We may have a couple left here. We will have Brad contact you on Monday.
  11. SanMP on Lion

    Version 4 is for Lion, please check the product announcements at http://www.snsforums.com/index.php?showforum=3. If you are wanting to test some new software, why don't you try 4.1 on Mountain Lion:)
  12. WTB- SNS Ellipse 2Gb PCI-X HBA

    Armando, forgive me, what is it you are asking?
  13. SanMP with Drobo b800i?

    Here is what I came up with when working with another user. The Drobo Dashboard must be used to mount the volume. If the GlobalSAN or other iSCSI initiators are used, this is expected behavior. The Dashboard needs to communicate with the Drobo in order to update the available filespace accordingly. The bad part about this is that you can only have the Drobo Dashboard mount a drive on one system. If you use one system to mount the drive, you should be still able to then mount the drive on other systems with GlobalSAN. Using the Drobo Dashboard to mount the volume while SANmp is installed: You will first need to run this from a terminal: sudo rm -r /System/Library/Extensions/SANmpDiskStimulator* (there must be a password set for the user account. If there is not, this command will silently fail) You will then need to reboot the workstation. After the reboot, you should be able to mount the volume from the Drobo Dashboard. Using SANmp admin, convert the drive, set permissions, and log out of SANmpAdmin. For the monitoring to work, the volume must then be mounted in SANmp Client (read only is fine) with that system. If this system unmounts the drive while other systems are connected, you will not be able to mount the volume with the Drobo Dashboard until they disconnect. We hope this helps, Joseph
  14. SanMP with Drobo b800i?

    Lamp, I can send you a procedure that will update the Drobo, but you will need the dashboard running on one system. Is there a reason the dashboard can not be used on one system?
  15. Best NTFS for OSX software?

    We are hoping to address this in a future release of SANmp. The limitation is there to prevent an issue that makes the volume unmountable by Windows. -Joseph
×