jon@jonlab.UUCP (Jon H. LaBadie) (10/04/89)
We're new to AIX (not to UNIX) and babes in the woods where networking
is concerned. We could use some serious hand-holding in setting up
the TCP/IP network on our systems. It will be a VERY simple network!
We have 2 systems, model 125's running AIX 2.2.1. The baseband adapters
and transceivers are installed and now it is time to proceed to network
administration. Our goals include file and mail transfer; remote backup
of one system (only one has a tape drive); remote printing (yup, one
printer); and eventually, external communications via one system with
modems.
If someone has a blow by blow description of getting started, that would
be ideal. Otherwise, perhaps a few clarifications would allow progress.
1. TCP/IP vs. Distributed Services
I'm not sure how these tie together. Seems that each has its own set
of administrative requirements.
2. Addressing
Node name - set via "uname -S", used only by uucp??
Node id number - printed by "uname -a" and listed as the local
"nickname" when entering "ndtable". What is its use and how
(or should) it be set.
Internet address - big HUH? Seems to be required at many points.
But I have no plans to get onto any external Internet. Is it
still required? How is it chosed/set?
Domain name - same HUH? as Internet address.
Hostname - seems to be set with "hostname". Should this be the
same as Node name?
3. Sendmail.cf and associated needs
I think I have a minimum config established, but some assurances
would be welcome.
4. NFS/YP software
This has not been obtained. Is it needed, would it be nice, for
our basic requirements?
5. Cabling
We have appropriate coax to connect the two systems. It would
mean routing the cable through the dropped ceiling between offices.
An alternative (attractive physically and visually) is to use the
already installed coax for our synchronous terminals. Each office
has a number of these going to a patch panel in the computer room.
It would be simple to run coax to the wall plate, and jumper the
two connections at the patch panel. Is this a no-no because of
the different types of coax cable?
I would appreciate any input you might have; posted or mailed. I would
prefer mailings however as the propogation delay on new articles is
about 3 days to my site. Mail is nearly immediate.
Thanks in advance,
Jon LaBadie,
many-backbones!princeton
\
bcr !jonlab!jon
/
AT&T-sites!att
--
Jon LaBadie
{att, princeton, bcr}!jonlab!jon
{att, attmail, bcr}!auxnj!jondrake@ibmarc.uucp (Sam Drake) (10/06/89)
In article <809@jonlab.UUCP> jon@jonlab.UUCP (Jon H. LaBadie) writes: >1. TCP/IP vs. Distributed Services > I'm not sure how these tie together. Seems that each has its own set > of administrative requirements. Distributed Services allows RTs to share filesystems over the network. Files on one RT can be accessed from the other. DS uses SNA, not TCP/IP, as its lowest level transport mechanism, and so there is no overlap... they do indeed require separate administration. DS does roughly the same thing as NFS does, but in a different manner... arguably superior in many ways. You can / should choose ONE of them to satisfy your remote file access requirements. If all you have are RTs, DS is probably the way to go; if you need to interoperate with other vendors' equipment then use NFS. NFS uses TCP/IP. >2. Addressing > Node name - set via "uname -S", used only by uucp?? True. > Node id number - printed by "uname -a" and listed as the local > "nickname" when entering "ndtable". What is its use and how > (or should) it be set. > Internet address - big HUH? Seems to be required at many points. > But I have no plans to get onto any external Internet. Is it > still required? How is it chosed/set? > Domain name - same HUH? as Internet address. > Hostname - seems to be set with "hostname". Should this be the > same as Node name? Internet addresses must be assigned for each machine, each machine must have a hostname/nodename, and you must have a domain name. If you really truly will never hook up to any other network you could make up the internet address (use a class C address, see the TCP/IP for AIX manual), and you could make up a domain name. Since I doubt it's possible to say that you'll never want to hook up, it might be worth the exercise to get formally assigned domain names and IP addresses. An example: My machine's node name is "sd2", my site's domain name is "almaden.ibm.com". Therefore my "hostname" in /etc/rc.tcpip is "sd2.almaden.ibm.com". So is my nodename in /etc/master. >3. Sendmail.cf and associated needs > I think I have a minimum config established, but some assurances > would be welcome. The supplied /usr/adm/sendmail/sendmail.cf needs to be modified to include the machine's node name in the indicated place, then run "sendmail -bz". That's it. >4. NFS/YP software > This has not been obtained. Is it needed, would it be nice, for > our basic requirements? See above. >5. Cabling > We have appropriate coax to connect the two systems. It would > mean routing the cable through the dropped ceiling between offices. > An alternative (attractive physically and visually) is to use the > already installed coax for our synchronous terminals. Each office > has a number of these going to a patch panel in the computer room. > It would be simple to run coax to the wall plate, and jumper the > two connections at the patch panel. Is this a no-no because of > the different types of coax cable? Doesn't sound promising. You might look at "Lattisnet" (sp?) equipment, they sell boxes that let you run Ethernet over existing phone wiring ... might be easier to set up and install than traditional Ethernet cabling. I have no connection with this company, and I'm certainly not speaking for IBM in any way. >I would appreciate any input you might have; posted or mailed. I would >prefer mailings however as the propogation delay on new articles is >about 3 days to my site. Mail is nearly immediate. Oops. Sam Drake / IBM Almaden Research Center
schwartz@psuvax1.cs.psu.edu (Scott Schwartz) (10/07/89)
In article <1122@ks.UUCP> Sam Drake writes: | NFS uses TCP/IP. Actually, NFS uses UDP/IP. -- Scott Schwartz <schwartz@shire.cs.psu.edu> Now back to our regularly scheduled programming....
jfh@rpp386.cactus.org (John F. Haugh II) (10/07/89)
>In article <809@jonlab.UUCP> jon@jonlab.UUCP (Jon H. LaBadie) writes: >> Node id number - printed by "uname -a" and listed as the local >> "nickname" when entering "ndtable". What is its use and how >> (or should) it be set. This one got missed - that is the CPU serial number. It is unique over the universe of RTs. -- John F. Haugh II +-Things you didn't want to know:------ VoiceNet: (512) 832-8832 Data: -8835 | The real meaning of MACH is ... InterNet: jfh@rpp386.cactus.org | ... Messages Are Crufty Hacks. UUCPNet: {texbell|bigtex}!rpp386!jfh +--------------------------------------