HP3000-L Archives

September 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Fri, 24 Sep 1999 01:59:29 -0400
Content-Type:
text/plain
Parts/Attachments:
Re: (138 lines)
Hello Friends @ 3000-l,

Re: Re: Oracle on the HP3000

Michel Gauthier writes:
+----------------------------------------------------------------------+
I have always thought NS/3000 was the subsystem on which all
communication services were dependent, including all IP protocol
services (TCP, FTP, TELNET, etc.).  Can anybody lighten us and get us out
from darkness?
+----------------------------------------------------------------------+

Larry Simonsen writes:
+----------------------------------------------------------------------+
There is a difference between the network (netcontrol) and ns.  On my
machines I do not start the ns service only the netcontrol.  Then I have
the jinetd job running which provides ftp, telnet and other arpa network
services.
+----------------------------------------------------------------------+


James say's it might be easiest to think about all of this from the ISO
7-Layer lasagna perspective... and I will use a :NMMAINT to get us back
to a 3000 reality...

Layer       Functionality
-----       -------------
 7          Application
 6          Presentation
 5          Session
 4          Transport
 3          Network
 2          Data Link
 1          Physical Hardware


7. Application

Your applications.

5. Session & 6. Presentation

NS3000/XL SERVICES - Inbound VT, RPM (FOS)
NS3000/XL SERVICES - Outbound VT, DSCOPY, RFA, RDBA (purchase)
FTP/XL (FOS)
TELNET/iX (FOS)
Internet Services (FOS)

3. Network & 4. Transport (this is TCP/IP):

NS3000/XL Transport (FOS)
NS3000/XL Transport - NETIPC Sockets (FOS)
NS3000/XL Transport - BSD Sockets (FOS)

2.  Data Link (these are drivers and card downloads):

HP LAN / Console Driver - ETHERNET/802.3 (FOS)
WAN SDLC DRIVER (purchase)
WAN LAPB DRIVER (purchase)
Token Ring LAN Driver (purchase)
FDDI LAN Driver (purchase)
100VG-AnyLAN driver (purchase)
100Base-T Fast Ethernet driver (purchase)

1.  Physical Links (these are all hardware cards):

LANIC (1 with every system)
PSI (purchase)
Token Ring (purchase)
FDDI (purchase)
100VG-AnyLAN (purchase)
100Base-T (purchase)


OK, now the answer to your questions...

Q1: I have always thought NS/3000 was the subsystem on which all
communication services were dependent, including all IP protocol
services (TCP, FTP, TELNET, etc.).  Can anybody lighten us and get
us out from darkness?

a1: NO.  The NS/3000 is a Level 5/6 Service.  NS3000/XL SERVICES
(Outbound VT "DSLINE", NFT "DSCOPY", RFA, RDBA, etc.) runs on top of
Level 3/4 NS3000/XL Transport and on top of your favorite Level 1/2
Physical Link and Driver/Downloads.

a2: FTP on 6.0 (under inetd) runs independently of NS3000/XL SERVICES,
FTP on 5.5 (under ftpmon) requires the NS3000/XL SERVICE RPM. If we
use FTP on 6.0 as an example, FTP Level 5/6 Service runs on top of
Level 3/4 NS3000/XL Transport and on top of your favorite Level 1/2
Physical Link and Driver/Downloads. On MPE/iX 6.0 you do not have to
perform a ":nscontrol start" to get FTP/iX to work.

a3: TELNET client and TELNET server runs independently of NS3000/XL
SERVICES.  If we use FTP Client or Server as an example, FTP Level 5/6
Service runs on top of Level 3/4 NS3000/XL Transport and on top of your
favorite Level 1/2 Physical Link and Driver/Downloads. On MPE/iX 5.5
and 6.0 you do not have to perform a ":nscontrol start" to get TELNET/iX
to work.



Q2: There is a difference between the network (netcontrol) and ns.  On my
machines I do not start the ns service only the netcontrol.  Then I have
the jinetd job running which provides ftp, telnet and other arpa network
services.

a1: Yes.  The ":NETCONTROL START;NET=<your Network Interface>" starts the
Level 1/2 Physical Link and Driver/Downloads (if not already started) and
it starts the Level 3/4 NS3000/XL Transport.

a2. The ":NSCONTROL START" starts only the above identified Level 5/6
Services NS3000/XL SERVICES.

A3. Yes. You don't need to start the NS3000/XL SERVICES for operation of
FTP (6.0) and TELNET/iX (5.5 and 6.0). P.S. On MPE/iX 5.5 you may not be
aware you are starting the NS3000/XL SERVICES RPM for FTP/iX since FTPMON
job does this for you.


Q3: And the final question is where does Oracle on the HP3000 fit into all
of this ???   I personally don't know of the design of Oracle, but an
educated guess is:  I suspect this product would fit in as a  Layer 7.
Application, 6. Presentation and 5. Session and that it would interface to
the Layer 3 & 4 TCP/IP stack with BSD Socket calls.  I would not expect
this product to require any NS3000/XL SERVICES to run.   If someone else
knows otherwise, please enlighten us.


I hope this helps.

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

ATOM RSS1 RSS2