396 lines
14 KiB
HTML
396 lines
14 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE>Linux Netstation HOWTO: Misc Stuff</TITLE>
|
|
<LINK HREF="NC-HOWTO-7.html" REL=next>
|
|
<LINK HREF="NC-HOWTO-5.html" REL=previous>
|
|
<LINK HREF="NC-HOWTO.html#toc6" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="NC-HOWTO-7.html">Next</A>
|
|
<A HREF="NC-HOWTO-5.html">Previous</A>
|
|
<A HREF="NC-HOWTO.html#toc6">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s6">6. Misc Stuff</A></H2>
|
|
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss6.1">6.1 Experiences (NC100)</A>
|
|
</H2>
|
|
|
|
<P>Using the NC as a plain terminal with multiple consoles.
|
|
The Built-in Motif extensions are a lot easier to use than the
|
|
default setup ;-)
|
|
Pressing the Pause/Break key will pop up the NC Menu at any time.
|
|
<P>
|
|
<H2><A NAME="ss6.2">6.2 Connecting through a network into the NC (NC100)</A>
|
|
</H2>
|
|
|
|
<P>
|
|
<P>The network station allows configuration access via telnet sessions on
|
|
several ports. The ones I know are by default configured like this:
|
|
<P>
|
|
<UL>
|
|
<LI>port 87, service SerialSD, (raw - serial daemon)</LI>
|
|
<LI>port 5964, service ParallelD, (raw - parallel daemon)</LI>
|
|
<LI>port 5976, service FILED, (raw - file manager)</LI>
|
|
<LI>port 5977, service PREFD, (raw - user preferences)</LI>
|
|
<LI>port 5978, service DIAG, (raw - diagnostics)</LI>
|
|
<LI>port 5979, service CONFIGD, (raw - configuration)</LI>
|
|
<LI>port 5996, service FILED, (telnet - file manager)</LI>
|
|
<LI>port 5997, service PREFD, (telnet - user preferences)</LI>
|
|
<LI>port 5998, service DIAG, (telnet - diagnostics)</LI>
|
|
<LI>port 5999, service CONFIGD, (telnet - configuration)</LI>
|
|
</UL>
|
|
<P>You can easliy access the TCP ports by using a telnet session
|
|
telnet NC-IPaddr port.
|
|
Be careful whether there is a password check enabled.
|
|
The passphrase 'public' (without quotes) worked for me.
|
|
<P>
|
|
<H3>Port 5978</H3>
|
|
|
|
<P>Remote Logging
|
|
It's the same as the messages console in your CLE.
|
|
<P>The format of each entry stretches over 2 lines.
|
|
<P>+ DD:HH:MM:SS
|
|
NSKxxxx: ...
|
|
<P>The first line covers date using the string that counts days, hours,
|
|
minutes and
|
|
seconds since boot time. The second line starts with an message identifier
|
|
and the
|
|
english plain text message after a separating colon, e.g.:
|
|
<P>
|
|
<PRE>
|
|
[...]
|
|
+ 25:17:31:43
|
|
NSK5641: unable to get current time from 10.10.90.149
|
|
+ 26:03:29:10
|
|
NSK4708: automatic powerdown to Suspend state after 40 minutes idle time
|
|
+ 26:03:49:10
|
|
NSK4708: automatic powerdown to Powerdown state after 60 minutes idle time
|
|
+ 26:07:22:38
|
|
NSK8001: accepting DIAGD connection from 10.10.90.150
|
|
[...]
|
|
</PRE>
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<H3>Port 5999 CONFIGD</H3>
|
|
|
|
<P>
|
|
<P>Use this port to do remote configuration for the NC by an telnet session
|
|
(telnet
|
|
NC-IPaddr 5999).
|
|
<P>
|
|
<P>
|
|
<P>Here are some first commands and hints that seemed to me to be useful.
|
|
You can apparently configure the NC remotely - online. The configuration
|
|
files use the same format, but do allow only an offline configuration.
|
|
As an alternative you may use the the setup
|
|
function
|
|
from the NC menu window.
|
|
<P> First of all you will need to login if you defined a password.
|
|
Logging into the NC should show you a sequence like:
|
|
<PRE>
|
|
*** NCD X Terminal Configuration ***
|
|
Password:
|
|
Invalid Password
|
|
Password: public
|
|
</PRE>
|
|
<P>
|
|
<P> Being logged in, you can start configurating.
|
|
The configuration syntax is identical to
|
|
/usr/netstation/configs/ the setup files.
|
|
Be aware that the behaviour within this command line interface is
|
|
the same as using the gui, i.e. when you set
|
|
(you may omit this keyword)
|
|
some parameter you need to apply it.
|
|
Otherwise you will not see any effect.
|
|
There is a /usr/netstation/configs/configd.doc
|
|
documentation file (- more precisely I would call it a
|
|
reference script -) delivered with the netstation software.
|
|
(The links are configured for the RS/6000 installation.)
|
|
<P>
|
|
<P> You probably want to start straight into the matter.
|
|
So for learning it the hard way, I recommend some commands to start with:.
|
|
<P>
|
|
<UL>
|
|
<LI>help - shows you all possible commands with some really short
|
|
explanation. Some commands concerning locking should be used with care.</LI>
|
|
<LI>get groups - tells you which groups of configuration options
|
|
are available. These are the subjects in the setup browser of the NC
|
|
menu. You may think of them as section headers. These group names are
|
|
also the first token in the name of the
|
|
configurable items within it. </LI>
|
|
<LI>get boot ... slow in answering and shows you how the boot
|
|
parameters of the NC are currently set.</LI>
|
|
<LI>get tftp - again some basic boot parameters. On my NC
|
|
all are read only statistics</LI>
|
|
<LI>get tcpip - most useful for reading some TCP statistics, less
|
|
useful for changing the IP setup, i.e. name servers, local DNS cache, ARP
|
|
configuration.</LI>
|
|
<LI>get file - again slow response. A long list of parameters.
|
|
Most of them are again self explaining. Be careful when changing the port
|
|
parameters, since you might have problems to find them later on. Also some
|
|
important boot parameters can be
|
|
found here.</LI>
|
|
<LI>get nfs - shows NFS configuration. You most likely will only
|
|
need it, if you use a memory PCMCIA card. Otherwise you will have little
|
|
to import or export.</LI>
|
|
<LI>info - shows you NAME, ACCESS, and PROTECTION of a
|
|
given or all variables. Helpful, if you work with protect</LI>
|
|
</UL>
|
|
<P>
|
|
<H2><A NAME="ss6.3">6.3 Port 161/udp - SNMP Access</A>
|
|
</H2>
|
|
|
|
<P>
|
|
You need some network management software to work with it.
|
|
Among the most famous commercial ones are (Tivoli) NetView and HP
|
|
OpenView.
|
|
They provide an easy-to-use user interfaces. For linux you usually use
|
|
cmu-snmp for command line and TCL/TK-based scotty
|
|
for visual frontend. (I like command line and that's what I am going to
|
|
explain)
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<H3>Some general statement </H3>
|
|
|
|
<P>The network station is completely configurable as already noted.
|
|
In allows examinations and alterations while being used.
|
|
The changes take effect either immediately, at session startup,
|
|
or at boot time (see configd.doc).
|
|
All reads from the network station do not unveal the users display
|
|
contents, and therefore the users' privacy is respected
|
|
(if the application itself respects it as well).
|
|
Only the configuration may be retrieved,
|
|
but not the window contents (at least not this way).
|
|
<H3>How to configure network management ? </H3>
|
|
|
|
<P>There is a file in ASN.1 called snmpmib.txt in the
|
|
installation directory of the recent releases that allows your
|
|
network management console resolve the mib symbols.
|
|
Otherwise you see dot-separated sequences of numbers only.
|
|
So best is to append this file (comments start with double
|
|
minus "--") to the mib.txt file of your SNMP software.
|
|
You can use snmpwalk, snmpget, snmpset to browse and modify the symbols
|
|
you have retrieved.
|
|
<P>
|
|
<H3>How to start managing? </H3>
|
|
|
|
<P>Simplest way to start managing is to execute the commands
|
|
<P>
|
|
<PRE>
|
|
snmpwalk NC-IPaddr public system
|
|
snmpget NC-IPaddr public system.sysDescr.0
|
|
snmpset NC-IPaddr public system.sysContact.0 s"MailTo:Kris.Buytaert@advalvas.b$
|
|
snmpwalk NC-IPaddr public system
|
|
</PRE>
|
|
<P>Sit back and think a little bit about it. It is easy to work with.
|
|
<P>If you never had experience with SNMP commands you should read some
|
|
SNMP
|
|
documentation, take reference to configd.doc.
|
|
For more details refer to SNMP-HowTos.
|
|
<H3>What do you manage? </H3>
|
|
|
|
<P>
|
|
<P>
|
|
<P>It works nearly the same way as the telnet session to the configuration
|
|
port,
|
|
except that each command is transferred separately to the NC using UDP.
|
|
The advantage is that you do not have to work interactively, you work with
|
|
UDP
|
|
instead of TCP, which avoids retries to network stations that are down.
|
|
you must have the privileges for being successful - 'public' is a good
|
|
community for reading...
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss6.4">6.4 IBM Software Releases</A>
|
|
</H2>
|
|
|
|
<P>IBM Has a special program for upgrades and documentation about the IBM
|
|
Netststation releases. It includes CDs and printed documentation
|
|
<P>It can be ordered freely from IBM from the following url
|
|
<A HREF="http://service.boulder.ibm.com/nc/pcserver/cd_order.shtml">service.boulder.ibm.com/nc/pcserver/cd_order.shtml</A>.
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<P>(Thnx to Herman Bos (
|
|
<A HREF="mailto:hermanb@xs4all.nl">hermanb@xs4allnl</A>) for this info)
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss6.5">6.5 NetworkStation Manager</A>
|
|
</H2>
|
|
|
|
<P>
|
|
<P>The NetworkStation Manager is a piece of software running on the boot
|
|
server. It has a web interface and allows you to administrate all your
|
|
NetworkStations from a single point.
|
|
You can define users and groups and provide a customised desktop for each
|
|
of them.
|
|
<P>This is required if you don't use a windowmanager provided by Linux.
|
|
It basically works by parsing and writing the configuration files. However, Linux is not a supported plattform of this software. So as a workaround you have to change the configuration files by hand or have an
|
|
OS/390, an AIX or a Windows NT do the job for you. Please be aware, that
|
|
for the personalisation in users and groups of your NetworkStation
|
|
Desktop, you need the login daemon running on your boot server. This
|
|
daemon is not available on Linux. So personalisation has to be done by
|
|
naming the configuration files according to the user sitting
|
|
at the Station.
|
|
<P>
|
|
<P>There is an actual Redbook about the Network Station,
|
|
<P>
|
|
<A HREF="http://www.redbooks.ibm.com/redpieces/abstracts/sg245844.html">Network Station Manager V2R1</A><P>, IBM PubNumber SG24-5844-00.
|
|
For the use with Linux it may be helpful for you to read
|
|
<A HREF="http://www.redbooks.ibm.com/abstracts/sg242016.html"> IBM Network Station - RS/6000 Notebook</A>,
|
|
IBM PubNumber SG24-2016-01.
|
|
It explains the use with the RS/600 AIX System (an interesting flavour of
|
|
Unix).
|
|
<H2><A NAME="ss6.6">6.6 Configuration file statements</A>
|
|
</H2>
|
|
|
|
<P>Here are some configuration file statements that I found useful:
|
|
<P>set boot-prom-force-update = true
|
|
With this setting, the Network Station will check for a new boot PROM (aka
|
|
Firmware) and download it if available.
|
|
<P>set xserver-access-control-enabled = false
|
|
Will allow all XClients to connect to the XServer running on that Network
|
|
Station.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss6.7">6.7 Printing</A>
|
|
</H2>
|
|
|
|
<P>
|
|
<P>(contributed by Bram Piket)
|
|
<P>To get printing work you have do two configuration steps.
|
|
One on the Netstation and one on the printsystem of the server.
|
|
<P>On the Netstation :
|
|
<P>
|
|
<P>Pop up the IBM Network Station User Services window (standard with
|
|
Alt-Shift-Home) or reboot the Netstation terminal.
|
|
<P>As stated on page 184 of the named IBM Redbook:
|
|
<P>In Setup -> Changes Setup Parameters, choose Print:
|
|
<P>Add in Lpr-Servers:
|
|
Server: localhost
|
|
Queue Name: PARALLEL1
|
|
Datastream type: ps (postscript)
|
|
<P>
|
|
<P>Save with Apply and as a file.
|
|
Add this file to:
|
|
/netstation/prodbase/configs/defaults.dft
|
|
<P>On the printer side
|
|
<P>Assumed is a cups printsystem.
|
|
You have to be root to administrate cups.
|
|
Within a webbrowser open the cups-setup (localhost:631).
|
|
In Administration -> Add Printer
|
|
Name your printer and give the device URI:
|
|
<P>
|
|
<P>lpd://ppp.qqq.rrr.sss/PARALLEL1,
|
|
<P>
|
|
<P>where ppp.qqq.rrr.sss = IP-adress of the Netstation.
|
|
<P> There is a Redbook about printing, 'IBM Network Station Printing Guide',
|
|
IBM
|
|
PubNumber SG24-5212-00. Redbooks can be found at
|
|
http://www.redbooks.ibm.com/
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss6.8">6.8 PCMCIA Memory Cards </A>
|
|
</H2>
|
|
|
|
<P>
|
|
<A HREF="mailto:ANeuper@antaris.de">ANeuper@antaris.de</A> the author of this paraphrase.
|
|
<P>
|
|
<P>I have tested memory cards manufactured by Centennial (IBM
|
|
gives you a more complete list of memory cards that work with the NC).
|
|
I recommend a minimum capacity of 20 MB.
|
|
If you have less you will have less functionality on the card.
|
|
Even 20MB is hardly sufficient. Once a NC is installed
|
|
with a memory card it can serve as peer booting host for other NCs
|
|
in its network vicinity.
|
|
<P>You need to connect to the file manager port 5996.
|
|
Keep a eye on your access protections in your configuration files.
|
|
If you use the memory card with the network station for the first
|
|
time, you need to format it. You should mount it and export it.
|
|
once you have exported it (<CODE>showmount -e NC-IPaddr</CODE>) you
|
|
can mount it to your boot server (<CODE>mount NC-IPaddr:/local /mnt</CODE>)
|
|
and transfer the setup directory(<CODE> cp -r /usr/netstation/* /mnt</CODE>).
|
|
Be careful not to forget some necessary files, particularily some
|
|
X11 files are needed. The full directory will not fit on the card.
|
|
Avoid erasing on the chip card, claiming the freed space isn't easy
|
|
and wastes space.
|
|
<P>For more detailed information you have place an PRPQ at IBM
|
|
(whatever this means), contact some IBM representative or contact
|
|
<P>
|
|
<H2><A NAME="ss6.9">6.9 Setup</A>
|
|
</H2>
|
|
|
|
<P>It seems the "user preferences" are stored in NVRAM, while "quick
|
|
setup" and "setup parameters" are read from the boot server (in NFS,
|
|
/netstation/prodbase/configs/standard.nsm).
|
|
<H2><A NAME="ss6.10">6.10 Images</A>
|
|
</H2>
|
|
|
|
<P>The screensaver and background reads XBM images, Linux/BSD/*nix users can
|
|
use XV to export to this format. The screensaver image shown will be
|
|
inverted.
|
|
<H2><A NAME="ss6.11">6.11 Time Sync</A>
|
|
</H2>
|
|
|
|
<P>The units don't use NTP, instead inetd's built-in unix time
|
|
(37/udp) support, I'd personally recommend using xinetd.
|
|
<H2><A NAME="ss6.12">6.12 Test Network</A>
|
|
</H2>
|
|
|
|
<P>This is User Sevices Console version of ping.
|
|
<H2><A NAME="ss6.13">6.13 BIOS</A>
|
|
</H2>
|
|
|
|
<P>Setting a global password will password-protect the "BIOS" setup.
|
|
According to Matthew Poertner
|
|
<P>You can reset the NVRAM on the netstations (tested on 110 and 300 types) using the
|
|
following commands:
|
|
<PRE>
|
|
>From Setup Utility:
|
|
-CTRL+ALT+SHIFT+F1
|
|
-NV
|
|
-R
|
|
-L
|
|
-S
|
|
Are you Sure? Yes
|
|
-Q
|
|
Reboot and Reconfig
|
|
</PRE>
|
|
<P>
|
|
<P>However if this doesn't work yet, you can always try to ...
|
|
<PRE>
|
|
1. Power Off
|
|
2. open it, everything attached
|
|
3. above the pcmcia slot, right hand there are two blank metal spots,
|
|
about 1 mm square, connect them (e.g. with a screwdriver) and power on the
|
|
netstation
|
|
4. watch the boot sequence, some when it should say sth. like "NVRAM
|
|
cleared or so"
|
|
5. Power Off, close it, and everything should be wonderful!
|
|
</PRE>
|
|
<P>If that still doesn't work I don't have a clue ;(
|
|
<H2><A NAME="ss6.14">6.14 Features</A>
|
|
</H2>
|
|
|
|
<P>Most units (8361-110 for sure) features not only support for X (as an
|
|
Xterminal) and NC (Windows NT Terminal Server) usage, it's built-in
|
|
console also has
|
|
support for serial (locally attached and dial-up using PPP/SLIP, also
|
|
telnet connections.
|
|
<HR>
|
|
<A HREF="NC-HOWTO-7.html">Next</A>
|
|
<A HREF="NC-HOWTO-5.html">Previous</A>
|
|
<A HREF="NC-HOWTO.html#toc6">Contents</A>
|
|
</BODY>
|
|
</HTML>
|