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!

SNS Hal

Members
  • Content count

    182
  • Joined

  • Last visited

Everything posted by SNS Hal

  1. It sounds like the storage is not presenting the iSCSI LUN - check that you have a LUN0 designated and that it is allowing incoming connections. If you have CHAP enabled, try disabling it for troubleshooting purposes. Try toggling the settings for "iSCSI Options..." in the globalSAN initiator. If you've connected using "Portal/Group" try using "Target" and manually entering the iqn for the target instead. If you still have trouble, please open a support case by emailing support@studionetworksolutions.com.
  2. It sounds like the storage is not presenting the iSCSI LUN - check that you have a LUN0 designated and that it is allowing incoming connections. If you have CHAP enabled, try disabling it for troubleshooting purposes. Try toggling the settings for "iSCSI Options..." in the globalSAN initiator. If you've connected using "Portal/Group" try using "Target" and manually entering the iqn for the target instead. If you still have trouble, please open a support case by emailing support@studionetworksolutions.com.
  3. Even though you do not have a previous version installed, it does sound as if there are remnants of an older, incompatible version conflicting with this one. We'd like to gather some information about your workstation. Please open a support case so we can more personally assist with this.
  4. Hi Charles, It sounds like your target disk may be sleeping when not in use; some storage systems have sleep enabled by default. Check that disk sleep is disabled for both the storage and the workstation. An iSCSI connection makes network storage appear local to your machine; however Spotlight is not designed for SAN storage, disks which may be much larger than your typical OS drive or which may be unmounted. You may find a third-party indexing utility will perform better in this environment.
  5. Hi Frank, Ensure you're using the latest version of the initiator and that no older versions are installed. Check that your setup matches that described in this video - If you still have trouble, fee free to open a support case.
  6. Not sure why a support case wasn't generated, but for reference you can open a support ticket by emailing support@studionetworksolutions.com anytime. Has globalSAN been installed on this machine in the past? If the install was migrated or restored from an image it will not work - you'll need to reinstall to generate the Product key. Ensure that you're entering the Activation key in the globalSAN tab rather than Xtarget tab. Also verify the key that the site displays is the same as the one in the top box in globalSAN, and then copy and paste the second key the site generates in the bottom box. If you still have trouble, open a case so we may investigate further.
  7. The newest QNAP firmware seems to require that targets be added differently. Rather than using "Portal/Group" as before, use "Target" when adding the target in globalSAN, and then manually enter the iqn for the QNAP LUN in the "Target Name" field.
  8. Sheekamoo, I just enabled CHAP for our own storage solution, as well as a Synology for good measure (I don't have a Solaris set up), and connected globalSAN 5.1.1.423 without trouble. Only the first field (User Authentication) was required for each target. Some systems do require a 12-character password. Perhaps there's more in the Oracle documentation. It could also be that a reboot or reconnection is required after changes are made - it isn't a requirement for the targets I tried but just in case, try restarting the server and workstation and re-adding the portal after enabling CHAP on the target.
  9. Some targets require different CHAP authentication methods; to ensure compatibility we have both mutual and target-only. Have you tried the authentication for both? You may need to enable both iSCSI options as well, and check that you're connected using Portal instead of Target.
  10. It sounds as if some SAN management is trying to protect your storage by preventing two devices from having simultaneous write access.
  11. If you'd like to open a support ticket we can take a look at some workstation diagnostics.
  12. We recommend disabling sleep for all components of the SAN. Additionally, mixing versions of SANmp is not supported.
  13. We recommend disabling sleep for all components of the SAN. Additionally, mixing versions of SANmp is not supported.
  14. What version of globalSAN and OSX are you using? Do you have jumbo frames set for the workstation and the target? Feel free to open a support case as well.
  15. Alexey, please open a support case so we may troubleshoot further.
  16. Alexey, One of the requirements for globalSAN is gigabit ethernet - wireless is not recommended. Even though you connected in Windows, starting at the beginning... Confirm that you can ping the target IP address. Try removing the portal in globalSAN and then re-adding it (Also check the iSCSI name and that you are connecting using Portal, not Target). Some targets require the Auth Method and/or Session Type settings be toggled in globalSAN. Confirm you have a LUN0. Also, feel free to open a support case if you still have trouble.
  17. Try the settings in the initiator under "iSCSI Options..." Check that the Error Detection settings match for the target and initiator (try turning it off for testing) You may need to manually enter the .iqn-formatted name rather than the .naa Also, feel free to open a case for support.
  18. You can also follow our Product Announcements page to be notified immediately of a new release.
  19. At this time globalSAN is not compatible with Windows Server 2012. It is however compatible with Windows Server 2008 R2.
  20. TG-Admin, see my previous reply as well as the threads you linked.
  21. The 0xe00002d9 code is a generic error, so it's harder to pin that down without more details. Please do an uninstall (removing preferences), then re-install and try to connect again. If that doesn't help, you may (depending on your target) have to change your initiator name from naa to an IQN format, and perhaps try using the "iSCSI Options" preferences. Documentation can be found in the /Applications/globalSAN folder and there's a demo video here that might help, too. Feel free to open a support case if you still have trouble.
  22. Are you trying to use CHAP? If so, please try disabling it and see if you can connect. Also, try toggling the 'Always send "SessionType" when connecting' and 'Always send "AuthMethod" when connecting' options available in the iSCSI options menu. Let us know how it goes.
  23. What is the target you are connecting? Feel free to open a case so we may gather more information.
×