NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

rmftechnologies's avatar
Feb 08, 2017

RN316 - FW 6.6.1 - iSCSI CHAP Broken / Confusion

Hi All,

 

Ever since updating to 6.6.1, we've noticed that all our iSCSI drives, which use CHAP Authentication, keep dropping off / disconnecting.

 

On further investigation it seems that everytime we fix one on the ReadyNAS and go fix another, the previous one has changed, in the sense that the initiator configured on the previous drive, is now the new one configured on this drive. Yes, it sounds confusing, so here's a breakdown.

 

1) Configure an iSCSI CHAP Login for a specific initiator on iSCSI Drive A

2) Apply that change

3) Confirm that the connection works on the server requiring the iSCSI Drive

4) Configure an iSCSI CHAP Login for a specific initiator on iSCSI Drive B

5) Apply that change

6) Confirm that the connection works on the server requiring the iSCSI Drive B

7) Re-visit the configuration for iSCSI Drive A on the NAS

8) The initiator configured for Drive A now no longer exists, but the initiator for Drive B now exists on Drive A, albeit disabled.

9) Checking the configuration on Drive B exists as normal.

10) Repeat this process to fix Drive A, now Drive B is screwed and has Drive A's config.

 

HELP!!! This is doing my head in!!!

 

Can someone please advise a resolution to this or issue an urgent patch to fix?

 

Cheers,

Ray

16 Replies

Replies have been turned off for this discussion
  • The iSCSI configuration on ReadyNAS OS6 has always confused me.
    Like, by default, "Selected" is selected instead of "Any", resulting in the LUN to be unreachable with default setting (shares are reachable with default setting). Then if you add an initiator, its "allowed" option is unchecked, making it unsuitable by default too.
    Then you get two separate CHAP options, one at the top, one at the bottom. They're not the same, but the first one doesn't clearly say it's not the same as the bottom one.
    You really need to know what you're doing.

    It's the complete opposite of user friendly, imo. Practice help...
    • nxtgen's avatar
      nxtgen
      Apprentice

      Thought I'd keep you all updated...

       

      6.7 apparently doesnt work with the 10Gb NICs.  They are "grayed out" in the interface, and missing from ifconfig when I SSH to the box. 

       

      I swear Netgear's QA is a joke. 

       

      I think I might just install Windows Server 2016 on the RN4220 and call it a day.  I'm tired of wasting my time on this. 

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        nxtgen wrote:

        6.7 apparently doesnt work with the 10Gb NICs.  They are "grayed out" in the interface, and missing from ifconfig when I SSH to the box. 

         


        6.7 is working with the RN524 and RN526 10gb NICs, so this must be model-specific.

  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired

    aalexandrebeta you shouldn't assume that 6.7.0 is a "magic" fix for any and every issue.

     

    rmftechnologies based on your purchase date you should have lifetime online chat. You may wish to open a support case using that method.

     

    nxtgen it looks like you may be a Powershift reseller. Have you considered opening a support case?

     

    6.7.0 does have some updates relevant to iSCSI, however I don't think any of the changes I've seen have anything to do with CHAP.

     

    I'd suggest waiting for the next build after Beta 3 before considering installing it on your RN316. Do note the support implications of trying a beta.

    • nxtgen's avatar
      nxtgen
      Apprentice

      Does anyone have the older firmware and know how to downgrade?  

       

      I cant use this in a production environment this way.  

       

      The minute an unauthorized iSCSI Initiator hits the box, the iSCSI service on the ReadyNAS "hangs" and takes down all of my iSCSI LUNs and I have to hard reboot the box by shutting off the power.. if you try a restart from the admin interface, the box never comes back online.

       

      This is junk as it is. 

  • FYI All...

     

    A temporary workaround to keep the iSCSI drives connected is to allow "Any" initiator to connect to the drive.

     

    Extremely poor QA'ing by Netgear here, but out of desparation, this will allow operations to continue until a patch is released.

     

    Cheers,

    Ray

    • aalexandrebeta's avatar
      aalexandrebeta
      Master

      The 6.7.0 FW is expected to be released and solve those issues!

      Unfortunatly we have to deal with it!

      • nxtgen's avatar
        nxtgen
        Apprentice

        Is this why I've been fighting iSCSI issues connecting to a single target/LUN from two separate initiators for the last 4 hours???   because, unless something has changed... CHAP and authentication are required to connect from multiple hosts... 

         

        First host works; the second gives me an authentication error and/or "service unavailable"  

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More