Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Infoserver 100 for Remote Boot
From: "Carl Nelson, Computer Operator I" <NELSON@MC.BITNET>
Date: 07 Jan 1993 15:23:00 -0700 (MST)
Content-transfer-encoding: 7BIT
Original_To:  JNET%"lanworks@miamiu"
Original_cc:  NELSON

Ralph:

  Gary is correct, an InfoServer cannot do an initial load of a DOS
system (at this time), you still need a VMS system to do that. The
virtual disk service can be on an InfoServer, but having the DEPCA_H.TSK
file on the InfoServer just takes up space.

  The reason why you can use the InfoServer for loading terminal
servers, but not DOS systems has to do with the MOP request packet
itself. If you break out your protocol analyzer (we all have those,
don't we? :-), and watch a terminal server's request for download via
MOP, you'll see that the MOP packet has the filename desired in the
packet itself. This makes it very simple for the InfoServer. In the
terminal server the file requested can be changed by changing the
terminal server's characteristics.

  A MOP packet from a DEC ethernet card, on the other hand, has no file
name imbedded. When a MOP packet like this is recieved by Decnet, it
scans the active NCP database, looking for the first record which
matches the ethernet address of the requesting packet. This is why you
will see the following:

NCP>show node 4r4201 char


Node Volatile Characteristics as of  7-JAN-1993 15:05:25

Remote node =   16.149 (4R4201)

Service circuit          = BNA-0
Hardware address         = 08-00-2B-11-C4-85
Load file                = SYS$COMMON:[PCSA.LOAD_FILE.V40]DEPCA_H.TSK

  This entry gets inserted when you create a remote workstation via
NETSETUP on the PC side, or via add workstation on the VMS side.

  There is currently no mechanism on the InfoServer to allow for a
NCP-like lookup, nor any way to synchronize the InfoServer with the NCP
database, nor (that I am aware of) are there any plans to modify the
ethernet cards to allow for an non-volitile area to store a file name.

  That isn't to say that something isn't in the works, though. (And THAT
isn't to say that something IS!)

--------------------------
: Carl Q. Nelson         :
: System Demigod         :
: Mesa Community College :
: Mesa, Azirona 85202    :
: (602) 461-7490         :
--------------------------

>
>We use InfoServers to assist with remote booting here, but your VMS systems
>are the ones which will service the MOP request.  We use the InfoServer to
>service the Remote Boot LAD itself (i.e. service name 08-00-2b-xx-xx-xx),
>but it is my understanding that VMS has to service the initial MOP request
>and TSK file load.  I would love it if I was wrong on this.
>
>Gary
>
>
>        +-------------------------------------------------------+
>        |   Gary. K Nalley         Network Specialist           |
>        |   Computer Services      nallegk@okra.millsaps.edu    |
>        |   Millsaps College       nalley@decus.org             |
>        |   1701 N. State St.      Fax:    601.974.1168         |
>        |   Jackson, MS 39210      Voice:  601.974.1140         |
>        +-------------------------------------------------------+


>>
>> Greetings All!  Hope you all had a good holiday...
>>
>> I need some help in making an Infoserver 100 service MOP requests to
>> PC's using PW4DOS.
>>
>> The point is that the Infoserver DOES receive the REQUEST for MOP service,
>> but there is no evidence that any further action is done by the Infoserver.
>>
>> I thought that I read here that several of these PW4DOS sites were
>> using the Infoserver for DEPCA_H.TSK files (i.e. the MOP service files for
>> DEPCA equipped PCs) on diskless remote boot machines....if any one that
>> might be able to help needs more data, let me know!
>>
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Ralph N. Yingling, Director       yingling@hcob.wmich.edu  (Internet)
>> College Computing Services
>> Haworth College of Business   --  Western Michigan University
>> Kalamazoo, MI 49008               (616) 387-5356
>>                                   YES, There really IS a Kalamazoo!
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Newsgroups: vmsnet.networks.desktop.pathworks