decnet startup failing - VMS

This is a discussion on decnet startup failing - VMS ; We have an old Vax system (4300) that is clustered with an Alpha (2100 4/200) yes, I know, also old as dirt. However, users can't log on to the Vax directly, only by logging on the the Alpha and doing ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 23

Thread: decnet startup failing

  1. decnet startup failing

    We have an old Vax system (4300) that is clustered with an Alpha (2100
    4/200) yes, I know, also old as dirt. However, users can't log on to
    the Vax directly, only by logging on the the Alpha and doing a 'set
    host xxx' can they log onto the Vax. So I'm assuming it's not attached
    tothe network.
    If I do a show net:

    $ show net
    %NETWRK-E-NOAVAILABLE, network service information is unavailable at
    this time

    What I've discovered, is that the startnet.com file has some errors.
    The first one is:
    $ RUN SYS$SYSTEM:NETACP -
    /NOACCOUNTING-
    /NOAUTHORIZE-
    /TRUSTED-
    /AST_LIMIT=100-
    /BUFFER_LIMIT=262144-
    /EXTENT=1500-
    /FILE_LIMIT=128-
    /IO_BUFFERED=32767-
    /IO_DIRECT=32767-
    /QUEUE_LIMIT=16-
    /ENQUEUE_LIMIT=255-
    /MAXIMUM_WORKING_SET=350-
    /PAGE_FILE=20480-
    /PRIORITY=8-
    /PRIVILEGES=CMKRNL-
    /PROCESS_NAME=NETACP-
    /UIC=[1,3]
    %RUN-F-CREPRC, process creation failed
    -SYSTEM-F-DUPLNAM, duplicate name

    With show process, I see that it already exists with devices attached,
    privileges, etc. Can I assume that this is ok? If not, do I kill it
    (and how) and re-run startnet.com?
    Then further down I get:

    NCP
    SET MODULE CONFIGURATOR KNOWN CIRCUITS ALL
    %NCP-I-NOINFO, No information in database

    So i assume this either related, or another problem. Is there a
    config com file or something I can run to automatically / manually
    create whatever database this is?

    Then later on, I get:
    Run sys$system:remacp -
    /noaccounting -
    /noauthorize -
    /
    privileges=(NOSAME,CMKRNL,LOG_IO,NETMBX,TMPMBX,SYS NAM) -
    /uic=[1,3] -
    /priority=8 -
    /page_file=600053 -
    /ast_limit=511 -
    /buffer_limit=85304 -
    /file_limit=256 -
    /io_buffered=511 -
    /process_name=remacp
    %RUN-F-CREPRC, process creation failed
    -SYSTEM-F-DUPLNAM, duplicate name
    Again, I can see that this process already exists as well.

    Again, should I kill these processes and execute startnet again (or
    does the aforementioned database have to be populated first)? Would
    there be a backup (on disk) of this database?

    Any assistance would be greatly appreciated. I am a relative newbie.
    As such, I can follow the clues, but not always find the answers (at
    least not quickly).

    Thanks again!


  2. Re: decnet startup failing


    "jhjr4381" wrote in message
    news:1185469441.346923.215710@x40g2000prg.googlegr oups.com...

    > What I've discovered, is that the startnet.com file has some errors.


    You appear to be running it twice; although that's not useful, it
    may not be relevant. I would start by looking at what:

    show known lines
    show known lines count
    show known circ
    show exec

    say. If you want you can try stopping with "set exec state shut"
    and restarting but I doubt it will help.



  3. Re: decnet startup failing

    On Jul 26, 1:26 pm, "Richard Brodie" wrote:
    > "jhjr4381" wrote in message
    >
    > news:1185469441.346923.215710@x40g2000prg.googlegr oups.com...
    >
    > > What I've discovered, is that the startnet.com file has some errors.

    >
    > You appear to be running it twice; although that's not useful, it
    > may not be relevant. I would start by looking at what:
    >
    > show known lines
    > show known lines count
    > show known circ
    > show exec
    >
    > say. If you want you can try stopping with "set exec state shut"
    > and restarting but I doubt it will help.


    After stopping with NCP> SET EXEC STAT SHUT, restart by running SYS
    $MANAGER:STARTNET.COM from SYSTEM or other sutiably privileged
    account.

    AEF



  4. Re: decnet startup failing

    On Jul 26, 1:26 pm, "Richard Brodie" wrote:
    > "jhjr4381" wrote in message
    >
    > news:1185469441.346923.215710@x40g2000prg.googlegr oups.com...
    >
    > > What I've discovered, is that the startnet.com file has some errors.

    >
    > You appear to be running it twice; although that's not useful, it
    > may not be relevant. I would start by looking at what:
    >
    > show known lines
    > show known lines count
    > show known circ
    > show exec
    >
    > say. If you want you can try stopping with "set exec state shut"
    > and restarting but I doubt it will help.

    NCP>show known lines


    Known Line Volatile Summary as of 26-JUL-2007 11:47:00

    Line State

    ISA-0 on
    NCP>show known lines count


    Known Line Counters as of 26-JUL-2007 11:47:07

    Line = ISA-0

    >65534 Seconds since last zeroed

    9817691 Data blocks received
    4361598 Multicast blocks received
    0 Receive failure
    1171342390 Bytes received
    482395316 Multicast bytes received
    0 Data overrun
    9420553 Data blocks sent
    4452191 Multicast blocks sent
    23609 Blocks sent, multiple collisions
    35575 Blocks sent, single collision
    102620 Blocks sent, initially deferred
    1016779541 Bytes sent
    459956452 Multicast bytes sent
    3341 Send failure, including:
    Excessive collisions
    0 Collision detect check failure
    0 Unrecognized frame destination
    0 System buffer unavailable
    0 User buffer unavailable


    NCP>show known circuits


    Known Circuit Volatile Summary as of 26-JUL-2007 11:47:31

    Circuit State Loopback Adjacent
    Name Routing Node

    ISA-0 on
    NCP>show exec


    Node Volatile Summary as of 26-JUL-2007 11:47:35

    Executor node = 12.116 (ASKNT2)

    State = on
    Identification = DECnet for OpenVMS VAX V6.1

    OK, it looks like I have structure there, not sure what it tells me
    though.


  5. Re: decnet startup failing

    In article <1185469441.346923.215710@x40g2000prg.googlegroups. com>, jhjr4381 writes:
    > We have an old Vax system (4300) that is clustered with an Alpha (2100
    > 4/200) yes, I know, also old as dirt. However, users can't log on to
    > the Vax directly, only by logging on the the Alpha and doing a 'set
    > host xxx' can they log onto the Vax. So I'm assuming it's not attached
    > tothe network.


    If users can log onto the VAX using "set host", then it is attached
    to the network and probably running DECnet (there are variations
    of "set host" for LAT and TCP/IP, but it doesn't look like your
    users are using them). Also to be in the cluster these models
    almost certainly are on an ethernet network since thats the most
    likely way to get the cluster protocol between them.

    What protocol are the user's using? TCP/IP? Maybe TCP/IP isn't
    installed or running on the VAX.

    > If I do a show net:
    >
    > $ show net
    > %NETWRK-E-NOAVAILABLE, network service information is unavailable at
    > this time


    That could be a trivial configuration problem that has only to
    do with the information provided to the "show net" display.
    Many of us are sad that this is no longer dynamically fetched from
    the network protocols' data, but there was reason for changing that.

    > What I've discovered, is that the startnet.com file has some errors.
    > The first one is:
    > $ RUN SYS$SYSTEM:NETACP -
    > /NOACCOUNTING-
    > /NOAUTHORIZE-
    > /TRUSTED-
    > /AST_LIMIT=100-
    > /BUFFER_LIMIT=262144-
    > /EXTENT=1500-
    > /FILE_LIMIT=128-
    > /IO_BUFFERED=32767-
    > /IO_DIRECT=32767-
    > /QUEUE_LIMIT=16-
    > /ENQUEUE_LIMIT=255-
    > /MAXIMUM_WORKING_SET=350-
    > /PAGE_FILE=20480-
    > /PRIORITY=8-
    > /PRIVILEGES=CMKRNL-
    > /PROCESS_NAME=NETACP-
    > /UIC=[1,3]
    > %RUN-F-CREPRC, process creation failed
    > -SYSTEM-F-DUPLNAM, duplicate name


    That is not an error "in" startnet.com, it's an error when you ran
    startnet.com that demonstrates that DECnet is already running.

    > With show process, I see that it already exists with devices attached,
    > privileges, etc. Can I assume that this is ok? If not, do I kill it
    > (and how) and re-run startnet.com?


    It depends on the Phase of DECnet. I think you should start from the
    VMS FAQ and find out what you do have so you can let us know.

    OBTW, if you succeed in killing NETACP (which has safeguards to make
    it non-trivial even for privileged users), you will crash the system.

    I think you need to know a lot more before you mess any further with
    your system. Please read the FAQ, and learn about at least DECnet
    and TCP/IP protocols, then come back here and ask more questions.


  6. Re: decnet startup failing

    On Jul 26, 1:26 pm, "Richard Brodie" wrote:
    > "jhjr4381" wrote in message
    >
    > news:1185469441.346923.215710@x40g2000prg.googlegr oups.com...
    >
    > > What I've discovered, is that the startnet.com file has some errors.

    >
    > You appear to be running it twice; although that's not useful, it
    > may not be relevant. I would start by looking at what:
    >
    > show known lines
    > show known lines count
    > show known circ
    > show exec
    >
    > say. If you want you can try stopping with "set exec state shut"
    > and restarting but I doubt it will help.


    I did run this solo, after the system has booted. I forgot to mention
    that, sorry. Is there another service that should be started then?


  7. Re: decnet startup failing

    On Jul 26, 12:04 pm, jhjr4381 wrote:
    > We have an old Vax system (4300) that is clustered with an Alpha (2100
    > 4/200) yes, I know, also old as dirt. However, users can't log on to
    > the Vax directly, only by logging on the the Alpha and doing a 'set
    > host xxx' can they log onto the Vax. So I'm assuming it's not attached
    > tothe network.
    > If I do a show net:
    >
    > $ show net
    > %NETWRK-E-NOAVAILABLE, network service information is unavailable at
    > this time
    >
    > What I've discovered, is that the startnet.com file has some errors.
    > The first one is:
    > $ RUN SYS$SYSTEM:NETACP -
    > /NOACCOUNTING-
    > /NOAUTHORIZE-
    > /TRUSTED-
    > /AST_LIMIT=100-
    > /BUFFER_LIMIT=262144-
    > /EXTENT=1500-
    > /FILE_LIMIT=128-
    > /IO_BUFFERED=32767-
    > /IO_DIRECT=32767-
    > /QUEUE_LIMIT=16-
    > /ENQUEUE_LIMIT=255-
    > /MAXIMUM_WORKING_SET=350-
    > /PAGE_FILE=20480-
    > /PRIORITY=8-
    > /PRIVILEGES=CMKRNL-
    > /PROCESS_NAME=NETACP-
    > /UIC=[1,3]
    > %RUN-F-CREPRC, process creation failed
    > -SYSTEM-F-DUPLNAM, duplicate name
    >
    > With show process, I see that it already exists with devices attached,
    > privileges, etc. Can I assume that this is ok? If not, do I kill it
    > (and how) and re-run startnet.com?
    > Then further down I get:
    >
    > NCP
    > SET MODULE CONFIGURATOR KNOWN CIRCUITS ALL
    > %NCP-I-NOINFO, No information in database
    >
    > So i assume this either related, or another problem. Is there a
    > config com file or something I can run to automatically / manually
    > create whatever database this is?
    >
    > Then later on, I get:
    > Run sys$system:remacp -
    > /noaccounting -
    > /noauthorize -
    > /
    > privileges=(NOSAME,CMKRNL,LOG_IO,NETMBX,TMPMBX,SYS NAM) -
    > /uic=[1,3] -
    > /priority=8 -
    > /page_file=600053 -
    > /ast_limit=511 -
    > /buffer_limit=85304 -
    > /file_limit=256 -
    > /io_buffered=511 -
    > /process_name=remacp
    > %RUN-F-CREPRC, process creation failed
    > -SYSTEM-F-DUPLNAM, duplicate name
    > Again, I can see that this process already exists as well.
    >
    > Again, should I kill these processes and execute startnet again (or
    > does the aforementioned database have to be populated first)? Would
    > there be a backup (on disk) of this database?
    >
    > Any assistance would be greatly appreciated. I am a relative newbie.
    > As such, I can follow the clues, but not always find the answers (at
    > least not quickly).
    >
    > Thanks again!


    Daniel,

    It can be a challenge fixing networking problems without adequate
    information.

    Obviously, DECnet is up (otherwise the SET HOST command would not
    work).

    How are users expecting to connect to the VAX? Perhaps your problem is
    not DECnet but LAT?

    More information is needed.

    - Bob Gezelter, http://www.rlgsc.com


  8. Re: decnet startup failing

    Couple of things to try:

    SHOW LICENSE DVNETEND on all nodes. The same licence can't be used on
    multiple nodes (unless its units permit it) because the locks taken out
    by the licence database is cluster-wide. An invalid licence will allow
    DECNET to start but not to activate any circuits.


    SHOW NETWORK DECNET should tell you if it thinks decnet is up or down.

    SET HOST 0 tells you if decnet is running and at least able to connect
    to itself.

    MC NCP SHOW KNOWN NODES tells you which nodes DECNET knows about. To
    connect to another node, make sure the other node also knows about the
    originating node,

  9. Re: decnet startup failing

    Another thing: make sure DECNET is started early in the boot, prior to
    TCPIP services and LAT. DECNET changes the ethernet address of the
    interface.

  10. Re: decnet startup failing


    "jhjr4381" wrote in message
    news:1185469441.346923.215710@x40g2000prg.googlegr oups.com...

    > We have an old Vax system (4300) that is clustered with an Alpha (2100
    > 4/200) yes, I know, also old as dirt. However, users can't log on to
    > the Vax directly, only by logging on the the Alpha and doing a 'set
    > host xxx' can they log onto the Vax.


    Reading this again, Bob is obviously correct. If you can currently use
    'set host', then your Decnet must be OK.



  11. Re: decnet startup failing

    In article <3134f$46a95e90$cef8887a$27578@TEKSAVVY.COM>, JF Mezei writes:
    >Another thing: make sure DECNET is started early in the boot, prior to
    >TCPIP services and LAT. DECNET changes the ethernet address of the
    >interface.


    No problem with LAT here. LATCP>CREATE LINK has /DECNET as default

    And DECnet Phase5 aka DECnet-OSI aka DECnet-Plus has also no problem
    starting after TCPIP, only DECnet-Phase4

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  12. Re: decnet startup failing

    jhjr4381 wrote:
    > We have an old Vax system (4300) that is clustered with an Alpha (2100
    > 4/200) yes, I know, also old as dirt. However, users can't log on to
    > the Vax directly, only by logging on the the Alpha and doing a 'set
    > host xxx' can they log onto the Vax. So I'm assuming it's not attached
    > tothe network.


    So, reading this correctly, users CAN login to the vax with decnet, so decnet
    is working. What is NOT working? Do you expect that the users can login
    to the vax via tcpip? If true then the issue is with tcpip on the vax....
    There does not appear to be any decnet issue.

    Jur.

    jhjr4381 wrote:
    > We have an old Vax system (4300) that is clustered with an Alpha (2100
    > 4/200) yes, I know, also old as dirt. However, users can't log on to
    > the Vax directly, only by logging on the the Alpha and doing a 'set
    > host xxx' can they log onto the Vax. So I'm assuming it's not attached
    > tothe network.
    > If I do a show net:
    >
    > $ show net
    > %NETWRK-E-NOAVAILABLE, network service information is unavailable at
    > this time
    >
    > What I've discovered, is that the startnet.com file has some errors.
    > The first one is:
    > $ RUN SYS$SYSTEM:NETACP -
    > /NOACCOUNTING-
    > /NOAUTHORIZE-
    > /TRUSTED-
    > /AST_LIMIT=100-
    > /BUFFER_LIMIT=262144-
    > /EXTENT=1500-
    > /FILE_LIMIT=128-
    > /IO_BUFFERED=32767-
    > /IO_DIRECT=32767-
    > /QUEUE_LIMIT=16-
    > /ENQUEUE_LIMIT=255-
    > /MAXIMUM_WORKING_SET=350-
    > /PAGE_FILE=20480-
    > /PRIORITY=8-
    > /PRIVILEGES=CMKRNL-
    > /PROCESS_NAME=NETACP-
    > /UIC=[1,3]
    > %RUN-F-CREPRC, process creation failed
    > -SYSTEM-F-DUPLNAM, duplicate name
    >
    > With show process, I see that it already exists with devices attached,
    > privileges, etc. Can I assume that this is ok? If not, do I kill it
    > (and how) and re-run startnet.com?
    > Then further down I get:
    >
    > NCP
    > SET MODULE CONFIGURATOR KNOWN CIRCUITS ALL
    > %NCP-I-NOINFO, No information in database
    >
    > So i assume this either related, or another problem. Is there a
    > config com file or something I can run to automatically / manually
    > create whatever database this is?
    >
    > Then later on, I get:
    > Run sys$system:remacp -
    > /noaccounting -
    > /noauthorize -
    > /
    > privileges=(NOSAME,CMKRNL,LOG_IO,NETMBX,TMPMBX,SYS NAM) -
    > /uic=[1,3] -
    > /priority=8 -
    > /page_file=600053 -
    > /ast_limit=511 -
    > /buffer_limit=85304 -
    > /file_limit=256 -
    > /io_buffered=511 -
    > /process_name=remacp
    > %RUN-F-CREPRC, process creation failed
    > -SYSTEM-F-DUPLNAM, duplicate name
    > Again, I can see that this process already exists as well.
    >
    > Again, should I kill these processes and execute startnet again (or
    > does the aforementioned database have to be populated first)? Would
    > there be a backup (on disk) of this database?
    >
    > Any assistance would be greatly appreciated. I am a relative newbie.
    > As such, I can follow the clues, but not always find the answers (at
    > least not quickly).
    >
    > Thanks again!
    >


  13. Re: decnet startup failing

    On Jul 26, 10:53 pm, JF Mezei wrote:
    > Another thing: make sure DECNET is started early in the boot, prior to
    > TCPIP services and LAT. DECNET changes the ethernet address of the
    > interface.


    Upon further review.....here are the answers to questions asked:

    Users log on through network using Reflections
    Reflections 1st choice is telnet



    $ show license dvnetend

    Active licenses on node ASKNT2:

    ------- Product ID -------- ---- Rating ----- -- Version --
    Product Producer Units Avail Activ Version Release
    Termination
    DVNETEND DEC 0 0 100 0.0 (none) 30-
    APR-2008
    $ show network decnet
    %NETWRK-E-NOAVAILABLE, network service information is unavailable at
    this time
    $ mc ncp show known nodes


    Known Node Volatile Summary as of 27-JUL-2007 07:23:46

    Executor node = 12.116 (ASKNT2)

    State = on
    Identification = DECnet for OpenVMS VAX V6.1


    Node State Active Delay Circuit Next node
    Links



    12.117 (ALPHA3) 1 3 ISA-0 0

    Now, having looked at a gazillion FAQ's and then some, I started
    asking the users of this system questions. It
    appears it's been a couple of years or so that this has been going on.
    Sorry, I inherited this, and was unaware.
    Looking at systartup_vms (on node A - VAX), LAT$STARTUP.COM is
    commented out. TCPIP is not started at all either. the only thing I
    see is an MC LATCP SET NODE/CONN=BOTH. On the other node in the
    cluster (node B - Alpha), in systartup_vms we do execute STARTNET,
    then LAT$STARTUP as well. LAT$SYSTARTUP executes, with all defaults,
    and (lcp set node, lcp create service, and lcp set node /stae=on)
    without p1-p5 set, and no TCPIP.com files executed here as well. Oh,
    there is in systartup_vms.com on node B, "DEFE DECW$IGNORE_DECNET
    TRUE",
    Obviously, this is deliberate, but can someone explain the reason? Is
    it indicative of somthing particulary (sane or insane)? Oh, there is
    in systartup_vms.com on node B, "DEFE DECW$IGNORE_DECNET TRUE". It
    seems this applies to DECWindows, or Motif that correct (not
    applicable here)?
    If I execute the lat$startup in systartup_vms.com on both nodes will
    it allow users to log directly on to that system (A)?

    The learning curve looks quite steep here. It doesn't help the ego
    when one looks at the HP Docs and sees 18 manuals to peruse for
    starters!

    Thanks all for the help / suggestions.
    Dan


  14. Re: decnet startup failing

    jhjr4381 wrote:
    > DVNETEND DEC 0 0 100 0.0 (none) 30-


    OK, it appears the licence is OK.



    > $ show network decnet
    > %NETWRK-E-NOAVAILABLE, network service information is unavailable at
    > this time


    Decnet is down or definitely a sick puppy. Does this happen on both nodes ?

    > $ mc ncp show known nodes
    > Executor node = 12.116 (ASKNT2)


    > 12.117 (ALPHA3) 1 3 ISA-0 0


    You should make sure that MC NCP SHOW KNOWN NODES when executed on
    ALPHA3, would show 12.116 (ASKNT2) . AKA: the alpha knows about the vax,
    and the vax knows about the alpha.


    What you could do is
    $ MC NCP SET EXECUTOR STATE SHUT
    $ @SYS$MANAGER:NETCONFIG

    And just rebuild your decnet config from scratch. It is fairly quick and
    painless.


    After it is done:
    $MC NCP DEFINE NODE 12.117 NAME ALPHA3

    AND THEN @SYS$MANAGER:STARTNET





    > Looking at systartup_vms (on node A - VAX), LAT$STARTUP.COM is
    > commented out. TCPIP is not started at all either. the only thing I
    > see is an MC LATCP SET NODE/CONN=BOTH.


    If you don't call LAT$STARTUP.COM , it is likely that the LATCP command
    is just changing a configuration without having an effect. Not starting
    LAT means that people cannot SET HOST/LAT to that machine, and people
    cannot SET HOST/LAT from that machine to another.


    If TCPIP is also not started, then people cannot telnet in or out of
    that machine.

    However, you may also wish to look at:

    $MC SYSMAN STARTUP SHOW FILE

    This was some not-too-succesful attempts at moving stuff from
    systartup_VMS.com to some database to make it look "cool", but it never
    really caught on in a big way, but unfortunatly, some products gets
    started from that and it makes managing a system harder because there
    are now 2 places where stuff gets executed during system startup.

    >e as well. Oh,
    > there is in systartup_vms.com on node B, "DEFE DECW$IGNORE_DECNET
    > TRUE",


    This is benign. It pertains to decwindows transports. If that node runs
    decwindows server software (eg: the X terminal), that will cause it to
    not listen to DECNET for incoming calls.


    > If I execute the lat$startup in systartup_vms.com on both nodes will
    > it allow users to log directly on to that system (A)?


    Example:

    $@sys$startup:lat$startup NODE1 -
    "/IDENTIFICATION=""""NODE1 of the BANANA cluster"""""


    You then need to go and edit LAT$SYSTARTUP.COM in sys$manager to
    uncomment the portions you want. (that file is fairly well documented).

    > Thanks all for the help / suggestions.


    $ help /suggestions
    %DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and
    placement
    \SUGGESTIONS\


  15. Re: decnet startup failing

    On Jul 27, 1:47 pm, JF Mezei wrote:
    > jhjr4381 wrote:
    > > DVNETEND DEC 0 0 100 0.0 (none) 30-

    >
    > OK, it appears the licence is OK.
    >
    > > $ show network decnet
    > > %NETWRK-E-NOAVAILABLE, network service information is unavailable at
    > > this time

    >
    > Decnet is down or definitely a sick puppy. Does this happen on both nodes ?
    > Only happens on ASKNT2 (node a)

    Node B gives me:
    Product: DECNET Node: ALPHA3 Address(es):
    12.117

    > > $ mc ncp show known nodes
    > > Executor node = 12.116 (ASKNT2)
    > > 12.117 (ALPHA3) 1 3 ISA-0 0

    >
    > You should make sure that MC NCP SHOW KNOWN NODES when executed on
    > ALPHA3, would show 12.116 (ASKNT2) . AKA: the alpha knows about the vax,
    > and the vax knows about the alpha.
    >

    MC NCP SHOW KNOWN NODES:

    node a - asknt2
    Executor node = 12.116 (ASKNT2)
    12.117 (ALPHA3) 2 2 ISA-0 0

    node b - Alpha3
    Executor node = 12.117 (ALPHA3)
    12.116 (ASKNT2) 1 1 SVA-0 0

    looks OK

    > What you could do is
    > $ MC NCP SET EXECUTOR STATE SHUT
    > $ @SYS$MANAGER:NETCONFIG
    >
    > And just rebuild your decnet config from scratch. It is fairly quick and
    > painless.
    >
    > After it is done:
    > $MC NCP DEFINE NODE 12.117 NAME ALPHA3
    >
    > AND THEN @SYS$MANAGER:STARTNET



    Did the above and got the following when STARTNET executed:
    MC NCP DEFINE NODE 12.117 NAME ALPHA3
    $ @SYS$MANAGER:STARTNET
    %SYSGEN-E-NOUNLOAD, driver is not unloadable
    %SYSGEN-F-DEVACTIVE, device is active
    %RUN-F-CREPRC, process creation failed
    -SYSTEM-F-DUPLNAM, duplicate name
    %DCL-I-SUPERSEDE, previous value of MOM$SYSTEM has been superseded
    %DCL-I-SUPERSEDE, previous value of MOM$SYSTEM_NOSOFTID has been
    superseded
    %DCL-I-SUPERSEDE, previous value of MOM$SYSTEM_SOFTID has been
    superseded
    %NCP-I-NOINFO, No information in database
    %RUN-F-CREPRC, process creation failed
    -SYSTEM-F-DUPLNAM, duplicate name

    Which device is active?

    $ mc ncp show known nodesExecutor node = 12.116 (ASKNT2)

    State = on
    Identification = DECnet for OpenVMS VAX V6.1


    Node State Active Delay Circuit Next node
    Links

    1.41 (CONDOR) ISA-0 0
    4.316 (USILED) ISA-0 0
    4.317 (ASKRD) ISA-0 0
    4.319 (RDAXP) ISA-0 0
    4.320 (ALPHA2) ISA-0 0
    12.111 (WRCMAN) ISA-0 0
    12.112 (ASKNT1) ISA-0 0
    12.115 (ALPHA1) ISA-0 0
    12.117 (ALPHA3) 1 1 ISA-0 0
    12.118 (BILBO) ISA-0 0
    40.101 (VUKPM) ISA-0 0
    55.100 (USWWVM) ISA-0 0

    most of these nodes don't exist, I'll delete them as well






    >
    > > Looking at systartup_vms (on node A - VAX), LAT$STARTUP.COM is
    > > commented out. TCPIP is not started at all either. the only thing I
    > > see is an MC LATCP SET NODE/CONN=BOTH.

    >
    > If you don't call LAT$STARTUP.COM , it is likely that the LATCP command
    > is just changing a configuration without having an effect. Not starting
    > LAT means that people cannot SET HOST/LAT to that machine, and people
    > cannot SET HOST/LAT from that machine to another.
    >
    > If TCPIP is also not started, then people cannot telnet in or out of
    > that machine.
    >
    > However, you may also wish to look at:
    >
    > $MC SYSMAN STARTUP SHOW FILE
    >
    > This was some not-too-succesful attempts at moving stuff from
    > systartup_VMS.com to some database to make it look "cool", but it never
    > really caught on in a big way, but unfortunatly, some products gets
    > started from that and it makes managing a system harder because there
    > are now 2 places where stuff gets executed during system startup.
    >

    $ MC SYSMAN STARTUP SHOW FILE
    %SYSMAN-I-COMFIL, contents of component database on node ASKNT2
    Phase Mode File
    ------------ ------ ---------------------------------
    LPMAIN DIRECT EASY$STARTUP.COM
    $
    Looks like it's just a shell .com file - nothing is changed
    EASY$STARTUP.COM;1

    show log easy*
    (EASY$LOGICAL_NAMES)

    "EASY$COMMAND" = "SYS$COMMON:[EASYMGR.IMAGE]"
    "EASY$LESSONS" = "SYS$COMMON:[EASYMGR.]"
    "EASY$MANAGER" = "SYS$COMMON:[EASYMGR.MANAGER]"
    "EASY$PROGRAM" = "SYS$COMMON:[EASYMGR.IMAGE]"
    "EASY$VERSION" = "02.0"
    Checked node B, got:
    -sysman-i-noderror error returned from ALPHA3
    startup-e-comfilemty, Startup component file is empty
    yet we can telnet to ALPHA3, though no TCPIP$ startup com files in
    systartup_vms.com exists


    > >e as well. Oh,

    >
    > > there is in systartup_vms.com on node B, "DEFE DECW$IGNORE_DECNET
    > > TRUE",

    >
    > This is benign. It pertains to decwindows transports. If that node runs
    > decwindows server software (eg: the X terminal), that will cause it to
    > not listen to DECNET for incoming calls.
    >
    > > If I execute the lat$startup in systartup_vms.com on both nodes will
    > > it allow users to log directly on to that system (A)?

    >
    > Example:
    >
    > $@sys$startup:lat$startup NODE1 -
    > "/IDENTIFICATION=""""NODE1 of the BANANA cluster"""""
    >
    > You then need to go and edit LAT$SYSTARTUP.COM in sys$manager to
    > uncomment the portions you want. (that file is fairly well documented).
    >


    yes, looked at that file, seems pretty straight forward.


    > > Thanks all for the help / suggestions.

    >
    > $ help /suggestions
    > %DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and
    > placement
    > \SUGGESTIONS\




  16. Re: decnet startup failing

    jhjr4381 wrote:
    > Did the above and got the following when STARTNET executed:
    > MC NCP DEFINE NODE 12.117 NAME ALPHA3
    > $ @SYS$MANAGER:STARTNET
    > %SYSGEN-E-NOUNLOAD, driver is not unloadable
    > %SYSGEN-F-DEVACTIVE, device is active
    > %RUN-F-CREPRC, process creation failed
    > -SYSTEM-F-DUPLNAM, duplicate name



    First message is normal. Second message indicates there is already a
    process using the decnet name. SHOW SYS would give you NETACP and/or
    REMACP. IF MC NCP SET EXECUTOR STATE SHUT doesn't kill that process,
    you may need to use bigger hammers (you can try STOP/ID but that often
    fails for ACP type of processes who refuse to be killed.

    > $ mc ncp show known nodesExecutor node = 12.116 (ASKNT2)
    >
    > State = on
    > Identification = DECnet for OpenVMS VAX V6.1
    >
    >
    > Node State Active Delay Circuit Next node
    > Links
    >
    > 1.41 (CONDOR) ISA-0 0
    > 4.316 (USILED) ISA-0 0
    > 4.317 (ASKRD) ISA-0 0
    > 4.319 (RDAXP) ISA-0 0
    > 4.320 (ALPHA2) ISA-0 0


    When you use NETCONFIG, it will normally flush the known nodes list
    fromm it.

    MC NCP LIST KNOWN NODES should reveal an empty list. If not, then your
    NETCONFIG did not work properly.

    (with NCP: LIST -> permanent database, SHOW -> dynamic/running database. )

  17. Re: decnet startup failing

    JF Mezei writes:

    >jhjr4381 wrote:
    >> Did the above and got the following when STARTNET executed:
    >> MC NCP DEFINE NODE 12.117 NAME ALPHA3
    >> $ @SYS$MANAGER:STARTNET
    >> %SYSGEN-E-NOUNLOAD, driver is not unloadable
    >> %SYSGEN-F-DEVACTIVE, device is active
    >> %RUN-F-CREPRC, process creation failed
    >> -SYSTEM-F-DUPLNAM, duplicate name



    >REMACP. IF MC NCP SET EXECUTOR STATE SHUT doesn't kill that process,
    >you may need to use bigger hammers (you can try STOP/ID but that often
    >fails for ACP type of processes who refuse to be killed.


    NCP SET EXECUTOR STATE SHUT is a "gentle" shutdown of the network. Any
    links active at the time remain active, but no new links can be created.
    The NETACP process (and the net itself) remain active until the last net
    user quits using the net. You want MC NCP SET EXECUTOR STATE OFF
    to be sure net users (and the NETACP process) are gone.


  18. Re: decnet startup failing

    In article <1185557088.850076.325540@e16g2000pri.googlegroups. com>, jhjr4381 writes:

    > LAT$STARTUP.COM is
    > commented out. TCPIP is not started at all either. the only thing I
    > see is an MC LATCP SET NODE/CONN=BOTH.


    OK, that does the most essential part of LAT$STARTUP. But LAT is
    still another protocol, not DECnet and not TCP/IP, and OBTW not
    routeable. So if there's a router along the way having LAT running
    doesn't help. And doesn't solve the original issue of having
    Reflection want TCP/IP.

    > "DEFE DECW$IGNORE_DECNET TRUE",


    Boy, theze systems have been "managed" as a real hack job. That
    statement prevents X11 windows on the system from using DECnet as
    a transport.

    > If I execute the lat$startup in systartup_vms.com on both nodes will
    > it allow users to log directly on to that system (A)?


    No. Your users need you to have TCP/IP running on the system, or
    set Reflection to use something that is running.


  19. Re: decnet startup failing

    On Jul 27, 12:24 pm, jhjr4381 wrote:
    > On Jul 26, 10:53 pm, JF Mezei wrote:
    >
    > > Another thing: make sure DECNET is started early in the boot, prior to
    > > TCPIP services and LAT. DECNET changes the ethernet address of the
    > > interface.

    >
    > Upon further review.....here are the answers to questions asked:
    >
    > Users log on through network using Reflections
    > Reflections 1st choice is telnet
    >


    You also say TCP/IP is *not* started on the VAX. So, why are you
    worrying about DECnet?? Exactly how do you want the clients to
    connect? If by TELNET, then start TCP/IP and TELNET on the VAX.

    DECnet has nothing to do with TCP/IP. If the VAX doesn't have a TCP/IP
    stack and you can't get one, your other option is to install DECnet
    and/or LAT on the client(s) --- and that takes a separate license.


  20. Re: decnet startup failing

    "Peter 'EPLAN' LANGSTOeGER"

    > And DECnet Phase5 aka DECnet-OSI aka DECnet-Plus has also no problem
    > starting after TCPIP


    Unless when running with phase-IV-compatible addresses enabled.

    Greetings, Ferry
    --



    > --
    > Peter "EPLAN" LANGSTOEGER
    > Network and OpenVMS system specialist
    > E-mail peter@langstoeger.at
    > A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist




+ Reply to Thread
Page 1 of 2 1 2 LastLast