• NET-APP-SUP-250 Alpha license question

    From Richard Jordan@21:1/5 to All on Fri Aug 9 15:47:51 2024
    Can anyone confirm if the VAX or Alpha NET-APP-SUP-250 licensing VAX- or VMSCluster support is for the full cluster support, or the client one
    that does not let the system it is on provide a vote towards quorum?

    The info I've found so far is generic and doesn't state it clearly
    (shows the same working for cluster support for -250, -300, and -400).

    Looking at waking up a long dormant box (assuming it works) to act as a vote-only node in a 3 node LAVC that is likely to lose its old an cranky
    shared storage.

    Thanks

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volker Halle@21:1/5 to All on Sat Aug 10 09:21:56 2024
    Am 09.08.2024 um 22:47 schrieb Richard Jordan:
    Can anyone confirm if the VAX or Alpha NET-APP-SUP-250 licensing VAX- or VMSCluster support is for the full cluster support, or the client one
    that does not let the system it is on provide a vote towards quorum?

    Richard,

    you can easily answer this question by looking at SYS$UPDATE:VMSINSTAL_LMFGROUPS.COM

    The NET-APP-SUP-250 license includes VMSCLUSTER.

    Only the NET-APP-SUP-150 license includes VMSCLUSTER-CLIENT

    Volker.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stephen Hoffman@21:1/5 to Richard Jordan on Mon Aug 12 17:45:12 2024
    On 2024-08-09 20:47:51 +0000, Richard Jordan said:

    Can anyone confirm if the VAX or Alpha NET-APP-SUP-250 licensing VAX-
    or VMSCluster support is for the full cluster support, or the client
    one that does not let the system it is on provide a vote towards quorum?

    The info I've found so far is generic and doesn't state it clearly
    (shows the same working for cluster support for -250, -300, and -400).

    Looking at waking up a long dormant box (assuming it works) to act as a vote-only node in a 3 node LAVC that is likely to lose its old an
    cranky shared storage.


    NAS client 150 was cluster client, while NAS client 250 was full clustering.

    Here are old VAX-era docs:

    http://odl.sysworks.biz/disk$axpdocjun043/database/nas83b/nasinstall/nas_vax_over1.html


    Here are "recent" Compaq / HP-era SPDs for NAS Client 250 on OpenVMS Alpha:

    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/MasterIndex/spd/spd_00581ab0.txt

    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/masterindex/spd/spd_00e417cc.txt


    For comparision, here's a NAS Client 150 SPD:

    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/MasterIndex/spd/spd_0135a5ec.txt


    Coincidentally (or entirely unsurprisingly?), you were in a thread
    about this NAS mess some twenty years ago, too:

    https://groups.google.com/g/comp.os.vms/c/39GoF1ao-gs/m/1R03B9UR_yUJ

    The LMF group table stuff was the easiest way to see what included
    what, though the contents of the SPDs officially overrode the group
    table.

    Off the top, I don't remember the full filename LMF$*something-or-other
    for the LMF group data, but it should be easy enough to find.




    --
    Pure Personal Opinion | HoffmanLabs LLC

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Jordan@21:1/5 to Stephen Hoffman on Tue Aug 13 09:32:04 2024
    On 8/12/24 4:45 PM, Stephen Hoffman wrote:
    On 2024-08-09 20:47:51 +0000, Richard Jordan said:

    Can anyone confirm if the VAX or Alpha NET-APP-SUP-250 licensing VAX-
    or VMSCluster support is for the full cluster support, or the client
    one that does not let the system it is on provide a vote towards quorum?

    The info I've found so far is generic and doesn't state it clearly
    (shows the same working for cluster support for -250, -300, and -400).

    Looking at waking up a long dormant box (assuming it works) to act as
    a vote-only node in a 3 node LAVC that is likely to lose its old an
    cranky   shared storage.


    NAS client 150 was cluster client, while NAS client 250 was full
    clustering.

    Here are old VAX-era docs:

    http://odl.sysworks.biz/disk$axpdocjun043/database/nas83b/nasinstall/nas_vax_over1.html

    Here are "recent" Compaq / HP-era SPDs for NAS Client 250 on OpenVMS Alpha:

    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/MasterIndex/spd/spd_00581ab0.txt
    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/masterindex/spd/spd_00e417cc.txt

    For comparision, here's a NAS Client 150 SPD:

    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/MasterIndex/spd/spd_0135a5ec.txt

    Coincidentally (or entirely unsurprisingly?), you were in a thread about
    this NAS mess some twenty years ago, too:

    https://groups.google.com/g/comp.os.vms/c/39GoF1ao-gs/m/1R03B9UR_yUJ

    The LMF group table stuff was the easiest way to see what included what, though the contents of the SPDs officially overrode the group table.

    Off the top, I don't remember the full filename LMF$*something-or-other
    for the LMF group data, but it should be easy enough to find.




    I had found the reference to the LMF file and looked it up on the
    customer's current production system (which doesn't have any NAS license installed; it has discrete DECnet and UCX licenses). The -250 license
    entries in that file didn't even include any cluster entries. The
    actual machine it originally came with is offline on a shelf so I can't
    check that for now.

    Thanks for replying, and for the answer!

    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Jordan@21:1/5 to Stephen Hoffman on Tue Aug 13 09:40:53 2024
    On 8/12/24 4:45 PM, Stephen Hoffman wrote:
    On 2024-08-09 20:47:51 +0000, Richard Jordan said:

    Can anyone confirm if the VAX or Alpha NET-APP-SUP-250 licensing VAX-
    or VMSCluster support is for the full cluster support, or the client
    one that does not let the system it is on provide a vote towards quorum?

    The info I've found so far is generic and doesn't state it clearly
    (shows the same working for cluster support for -250, -300, and -400).

    Looking at waking up a long dormant box (assuming it works) to act as
    a vote-only node in a 3 node LAVC that is likely to lose its old an
    cranky   shared storage.


    NAS client 150 was cluster client, while NAS client 250 was full
    clustering.

    Here are old VAX-era docs:

    http://odl.sysworks.biz/disk$axpdocjun043/database/nas83b/nasinstall/nas_vax_over1.html

    Here are "recent" Compaq / HP-era SPDs for NAS Client 250 on OpenVMS Alpha:

    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/MasterIndex/spd/spd_00581ab0.txt
    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/masterindex/spd/spd_00e417cc.txt

    For comparision, here's a NAS Client 150 SPD:

    https://www.zx.net.nz/mirror/h30266.www3.hpe.com/MasterIndex/spd/spd_0135a5ec.txt

    Coincidentally (or entirely unsurprisingly?), you were in a thread about
    this NAS mess some twenty years ago, too:

    https://groups.google.com/g/comp.os.vms/c/39GoF1ao-gs/m/1R03B9UR_yUJ

    The LMF group table stuff was the easiest way to see what included what, though the contents of the SPDs officially overrode the group table.

    Off the top, I don't remember the full filename LMF$*something-or-other
    for the LMF group data, but it should be easy enough to find.





    I had found that reference and looked it up on the customer's current production system (which doesn't have any NAS license installed; it has discrete DECnet and UCX licenses). The -250 license entries in that
    file didn't even include any cluster entries. The actual machine it
    originally came with is offline on a shelf so I can't check that for now.

    Thanks for replying, and for the answer!

    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)