Re: JINETD and Other NICs
- From: "Johnson, Tracy" <Tracy.Johnson@xxxxxxxxxxxxx>
- Date: Tue, 23 Sep 2008 09:19:38 -0400
Woohoo!
(I did have to add the NIC cards, so I did a reboot this Sunday anyway.)
In effect I connected two HP3000s with a crossover cable on the extra
NICs.
And it is working fine with the Netbase Shadowing product.
Tracy Johnson
Business Analyst
Measurement Specialties, Inc.
1000 Lucas Way
Hampton, VA 23666
Office 1-757-766-4318
tracy.johnson@xxxxxxxxxxxxx
www.meas-spec.com
-----Original Message-----
From: HP-3000 Systems Discussion
[mailto:HP3000-L@xxxxxxxxxxxxx] On Behalf Of James Hofmeister
Sent: Monday, September 22, 2008 5:13 PM
To: HP3000-L@xxxxxxxxxxxxx
Subject: Re: [HP3000-L] JINETD and Other NICs
Hello Tracy,
The service daemon's INETD and DSDAD should not need to be
restarted, nor
should the network or system (unless the hardware card is not already
installed).
Adding a networking configuration for an existing network card and
":netcontrol start;net=<NIC>" will create the NIC driver data
structures,
establish a "new" buffer pool if necessary and create the TCP
& IP data
structures.
Once this is complete the NIC driver will perform a DMA write
of a received
frame to the network buffer pool and the driver will pass the
buffer pointer
(based on the value in the Ethernet frame type field) to IP
who will pass
the buffer pointer (based on the value in the IP datagram
protocol field) to
TCP who will pass the buffer pointer a service daemon who has
a select on
the port (based on the value in the TCP packet destination
port field). The
service daemon will then fork (or o.s. dependant createproc)
or internally
provide the requested service. It is at this point that the
forked/created
service copies the data from the network buffer pointer to
the user stack
via a "receive" command and the buffer pointer is returned to
the driver for
re-use.
The only reason I would see to restart the service daemon
INETD would be if
changes were necessary because allow/deny <network> was specified in
inetdsec.net.sys. I did not find in the documentation if it
was necessary
to stop/restart inetd for this case or not.
Regards,
James Hofmeister
-----Original Message-----
From: HP-3000 Systems Discussion
[mailto:HP3000-L@xxxxxxxxxxxxx] On Behalf
Of Johnson, Tracy
Sent: Friday, September 19, 2008 10:34 AM
To: HP3000-L@xxxxxxxxxxxxx
Subject: [HP3000-L] JINETD and Other NICs
When one configures other network cards in NMMGR and tie them to other
LAN names and IP addresses, does one have to tell the INETD
configuration anything or does it just "know" by itself?
Tracy Johnson
Business Analyst
Measurement Specialties, Inc.
1000 Lucas Way
Hampton, VA 23666
Office 1-757-766-4318
tracy.johnson@xxxxxxxxxxxxx
www.meas-spec.com
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
.
- Follow-Ups:
- Re: JINETD and Other NICs
- From: James Hofmeister
- Re: JINETD and Other NICs
- References:
- JINETD and Other NICs
- From: Johnson, Tracy
- Re: JINETD and Other NICs
- From: James Hofmeister
- JINETD and Other NICs
- Prev by Date: Re: DTC on A500?
- Next by Date: Contract opportunity in Sacramento COBOL Powerhouse
- Previous by thread: Re: JINETD and Other NICs
- Next by thread: Re: JINETD and Other NICs
- Index(es):
Relevant Pages
|