Accessing VLC Console through NI - DEC

This is a discussion on Accessing VLC Console through NI - DEC ; According to the VLC service information manual here: http://vt100.net/mirror/mds-199909/cd1/vax/v48vbsv1.pdf I can access the console through the NI if I set TRIGGER and MOP to 1. What type of client do I use to connect to the console this way?...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Accessing VLC Console through NI

  1. Accessing VLC Console through NI

    According to the VLC service information manual here:
    http://vt100.net/mirror/mds-199909/cd1/vax/v48vbsv1.pdf I can access the
    console through the NI if I set TRIGGER and MOP to 1. What type of client do
    I use to connect to the console this way?



  2. Re: Accessing VLC Console through NI

    Robert Jarratt wrote:
    >
    > According to the VLC service information manual here:
    > http://vt100.net/mirror/mds-199909/cd1/vax/v48vbsv1.pdf I can access the
    > console through the NI if I set TRIGGER and MOP to 1. What type of client do
    > I use to connect to the console this way?


    Just looked at that (SEARCH in Acrobat Reader is kewl!). First guess time, you'd
    need another VMS machine up and running. In NCP, the command would look like
    this:

    $ MC NCP
    NCP> CONNECT VIA circuit-name PHYSICAL ADDRESS aa-bb-cc-dd-ee-ff

    From the Exmaples in NCP's HELP:

    CONNECT

    VIA

    Examples


    NCP>CONNECT VIA UNA-0 PHYSICAL ADDRESS AA-00-04-00-38-00

    This command connects the host node to the console interface
    on the target node by specifying the circuit over which the
    connection is to be made and the physical address of the
    target node.

    You'd need to know the VLC's MAC address, obviously, and the DECnet circuit
    name.

    Using LANCP, it looks like this:

    $ MC LANCP
    LANCP> CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0

    ...., again from the example in HELP (for LANCP this time).

    I've never done either of those. T'would have been great if that worked on
    Alphas, eh?

    Now, dunno what happens if you (can) tell it to boot up...

    --
    David J Dachtera
    dba DJE Systems
    http://www.djesys.com/

    Unofficial OpenVMS Marketing Home Page
    http://www.djesys.com/vms/market/

    Unofficial Affordable OpenVMS Home Page:
    http://www.djesys.com/vms/soho/

    Unofficial OpenVMS-IA32 Home Page:
    http://www.djesys.com/vms/ia32/

    Unofficial OpenVMS Hobbyist Support Page:
    http://www.djesys.com/vms/support/

  3. Re: Accessing VLC Console through NI

    In article <6OAKi.34972$ka7.8051@newsfe4-gui.ntli.net>, "Robert Jarratt" writes:
    >According to the VLC service information manual here:
    >http://vt100.net/mirror/mds-199909/cd1/vax/v48vbsv1.pdf I can access the
    >console through the NI if I set TRIGGER and MOP to 1. What type of client do
    >I use to connect to the console this way?


    The full MOP functionality (like a DECserver has) is not present in VAXes.


    The DECnet commands for MOP are these (and then there are LANCP commands):

    DN4: DN5:

    NCP> CONNECT NODE ... SET HOST/MOP
    NCP> LOAD NODE ... NCL> LOAD MOP CLIENT clientname ...
    NCP> TRIGGER NODE ... NCL> BOOT MOP CLIENT clientname ...

    I think, only the last command (TRIGGER/BOOT) will work with SRM (if SRM
    has it enabled like you described above).

    --
    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

  4. Re: Accessing VLC Console through NI

    David J Dachtera wrote:
    > Robert Jarratt wrote:
    >> According to the VLC service information manual here:
    >> http://vt100.net/mirror/mds-199909/cd1/vax/v48vbsv1.pdf I can access the
    >> console through the NI if I set TRIGGER and MOP to 1. What type of client do
    >> I use to connect to the console this way?

    >
    > Just looked at that (SEARCH in Acrobat Reader is kewl!). First guess time, you'd
    > need another VMS machine up and running. In NCP, the command would look like
    > this:
    >
    > $ MC NCP
    > NCP> CONNECT VIA circuit-name PHYSICAL ADDRESS aa-bb-cc-dd-ee-ff
    >
    > From the Exmaples in NCP's HELP:
    >
    > CONNECT
    >
    > VIA
    >
    > Examples
    >
    >
    > NCP>CONNECT VIA UNA-0 PHYSICAL ADDRESS AA-00-04-00-38-00
    >
    > This command connects the host node to the console interface
    > on the target node by specifying the circuit over which the
    > connection is to be made and the physical address of the
    > target node.
    >
    > You'd need to know the VLC's MAC address, obviously, and the DECnet circuit
    > name.
    >
    > Using LANCP, it looks like this:
    >
    > $ MC LANCP
    > LANCP> CONNECT NODE 08-00-2B-11-22-33/DEVICE=EWA0
    >
    > ..., again from the example in HELP (for LANCP this time).
    >
    > I've never done either of those. T'would have been great if that worked on
    > Alphas, eh?
    >
    > Now, dunno what happens if you (can) tell it to boot up...
    >


    You can also use the MOP RC (Remote Console) feature from Tru64
    (=DigitalUnix=OSF/1) or even Ultrix. The utility called ccr is used in
    Tru64. I'm not sure about how it is done in Ultrix, because it is almost
    10 years since I've used an Ultrix machine.
    You can connect to the console and use almost all the usual console
    commands on the VAX and on the DEC3000 series Alphas.

    I think there has been two main reasons for the feature on VAX and
    Alphas. First you can do troubleshooting and second you can remotely
    boot e.g. diskless workstations.

    Also the DECserver series terminal servers can be remotely administered
    using MOP RC. The Terminal Server Manager (TSM) program uses MOP RC to
    communicate with DECservers, AFAIK.




+ Reply to Thread