Newsgroup: it.comp.retrocomputing
Titolo: risc6000 e modems

moderatamente OT anche se il "pezzo" è abbastanza datato..
Ho recuperato una bella workstation ibm risc6000/320 e nonostante sia
già configurata tcp/ip non ha un modem.
Vorrei usarla in rete ma non avendo molta familiarità con l'AIX 4.2 e
simili ho qualche difficoltà.
Fra l'altro ho già Netscape installato, quindi si tratterebbe di fargli
vedere l'hardware e configurare la connessione (credo slip)
C'è qualcuno che ci capisce + di me?
Come si configura una connessione dial-up su questo s.o.?
Ciao
Fabio M.

 Come si configura una connessione dial-up su questo s.o.?
E anche... c'e' qualcuno che sa dove trovare informazioni *chiare* su
questo SO e sulle macchine RS6000????
Intendo qualcosa di analogo a quello che c'e' in rete per Sun, una
miniera, con moltissimi dettagli e di chiarezza esemplare.
Ciao
Sabino


Argh, AIX ergo *nix, allora "dovrebbe" essere PPP 
il demone che ti prenderà nella rete ;-)
Se il sistema é stato installato bene dovresti
trovare sia le pagine man che le doc varie.

 ha scritto nel messaggio
news:3AAFAA8B...@ien.it...

io in rete non ho trovato un granchè, c'è solo della doc sul sito ibm, quei
manuali che credo si chiamino "redbook" ma purtroppo non ho i link
un mio amico me li ha scaricati ma sono diverse centinaia di mega...
inoltre ho questi link, se possono essere utili, ma direi quasi solo sw
freeware
http://pdslib4aix.seas.ucla.edu/aixpdslib.html
http://www-frec.bull.com/docs/download.htm
ciao
luigi


Ciao,
se ha una scheda di rete configurata il mio consiglio e' di usare quella e
passare attraverso un router od un pc gia' conneso che faccia da proxy.
Altrimenti, come gia' consigliato da altri, PPP is the way to go. 
Ho sentito che alcuni ci sono riusciti, ma non so dirti molto di piu'.
news:comp.unix.aix e' un buon riferimento, oltre ai gia' citati IBM e Bull.
Su IBM, a cercarlo bene, trovi tutto un sottosito dedicato ai RS/6000 e AIX con
la documentazione completa dei comandi e anche di alcune procedure.
http://www.redbooks.ibm.com
 ha pure lui diversi riferimenti.
http://www.ibmlink.ibm.com/
http://www.rs6000.ibm.com/
-- 
 Alberto Varesio - Certified AIX V4.3 System Support  Phone: 
+39-011-415-8111
 EDIST Spa - Via Goito 51/A      Riding the world       Fax: +39-0270040-8636
 10195 Grugliasco (TO) ITALY     on a Honda CB500      Cell: 
+39-349-492-4769
 mailto:
alberto...@torinofacile.it
 
http://www.geocities.com/avaresio

 wrote in message 3AAF8FCC...@tin.it...

dunque... io ricordo maneggiai con una connessione slip su aix tipo 5 anni
fa :) ergo non mi ricordo una cippa.... sapevo solo di avere sull'hd un
filettino che parlava di slip di aix, non so se preso direttamente dal man
.... ergo lo posto qua... poi picchiatemi se e' stato troppo lungo e OT :)
                       SLIP (Serial Line Interface Protocol)
This document applies to AIX versions 3.2.3 and 3.2.5.
Important Notice: This document will no longer be
updated and remains available only for high severity situations.
For all other situations, we recommend that you order
"System Management: Communications and Networks", publication number
GC23-2487.
Planning SLIP Addresses
Probably one of the most important things to consider when planning your
SLIP connection is the addressing. You should
examine which address class you wish to use and then develop the actual
numerical values (see :hdref refid=slipnat. for
possible class types).
Please verify that your SLIP addresses DO NOT conflict with any existing
(network) addresses on your system. For
simplicity, these addresses are used in the following instructions:
   1.1.1.2   for local system  "A"
   1.1.1.1   for remote system "B"
Please note that this SLIP example starts SLIP from the command line. The
following instructions add a tty via SMIT and
then configure and start SLIP from the command line. It is good to first
configure from the command line, as in these
instructions, because command line options are easier to correct. After you
get SLIP working correctly from the command
line, bring it down, detach it (to start clean), and reconfigure it through
SMIT. Configuring it through SMIT will make the
configuration permanent and allow SLIP to start automatically at each system
reboot.
Setting Up SLIP
Step 1: Configure/Add a tty Port
Add a tty for serial port S2 on BOTH machines A and B. (* means user can
change the setting.)
        Login:   as root or "su" to root
        Enter:   smit tty
        Select:  Add a TTY
        Select:  tty rs232 Asynchronous Terminal
     *  Select:  sa1 Available 00-00-S2 Standard I/O Serial Port 2
        Press:   F4    (for PORT number)
     *  Select:  s2
        Change:  "Enable LOGIN" to "disable"
     *  Change:  "BAUD rate" to desired speed
        Change:  XON-XOFF to "no"
        Press:   <enter> key until tty is added or changed
Add ONE of the following lines to the /etc/uucp/Devices file on both the
server and the remote client. (If you are not sure
which line to use, try one and, if you get an error, try another.) Be sure
to change 9600 to the correct bps rate for your
modem.
   Direct tty1 - 9600 direct
   Direct tty1 - 9600 hayes
   ACU    tty1 - 9600 hayes
Step 2: Assign Addresses for SLIP
Configure SLIP lines for both systems A and B using selected addresses.
Here, 1.1.1.2 is the address for A and 1.1.1.1 is
the address for B. (Note: sl# should match the tty# being used; that is, if
tty1 is being used, sl# should be sl1.)
On system A, enter:
   ifconfig  sl#  1.1.1.2   1.1.1.1   up
On system B, enter:
   ifconfig  sl#  1.1.1.1   1.1.1.2   up
Step 3: Verify
Check status on BOTH machines with the following command line entry:
   ifconfig  sl0
Step 4: Make the SLIP Connection
On the remote system to be dialed into, enter:
   slattach  tty#
Use the following command line option to dial out of the local system.
(Replace "#" with your tty number.)
   slattach  tty#  9600  ' "" AT OK ATDT555-3346 CONNECT "" '
The above string is interpreted as ``Use tty# at 9600 baud, send ``AT'' and
I should get back an ``OK'', dial 555-3346 and I
should get a ``CONNECT'' back.''
Notes:
   1.The tty ports MUST be disabled for use with SLIP and not set for
"share" or "delay" (no getty).
   2.In the modems, you CANNOT use XON/XOFF, software flow-control. XON/XOFF
should also be set off in SMIT
     for tty. Use of XON/XOFF will not allow SLIP to work properly (SLIP
will be up but you won't be able to ping the
     other system).
   3.DTR should be set so that the modem tracks the status of DTR and hangs
up when an "on" to "off" transition occurs.
     slattach will bring DTR up.
 
4.CD
 should be set so the modem tracks the status of DTR (AT&C1).
   5.On a modem with Hayes-compatible AT commands, "AT&K0" sets
no-flow-control and "AT&K3" sets RTS/CTS
     on. DTR can be set with "AT&D2". See :hdref refid=sliprts. for
instructions on adding RTS to a port on the RISC
     System/6000.
Test the SLIP connection between system "A" and system "B" by using the ping
command. On system "A", enter:
   ping 1.1.1.1
System should display packets being sent and received from that address.
Bringing Down a SLIP Connection
   1.Enter "ps -ef | grep slatt" to search for processes associated with
SLIP.
   2.******** VERY IMPORTANT !! *************
     Kill these processes WITHOUT the -9 option. The proper way to kill a
slattach is with "kill <pid>". If SLIP has been
     defined via SMIT, severe problems could occur if you use "kill -9".
Problems can effect your system and may cause a
     crash with LED 888.
     Should system crash with the 888 LED, a reboot will NOT correct the
problem. You will need to use SMIT to
     remove the SLIP interface and associated tty. Use SMIT again to
reconfigure tty and SLIP.
     *****************************************
   3.On the command line, enter "ifconfig sl# down" where # is the number of
your SLIP interface (sl0, sl1, etc.).
   4.To completely remove the SLIP configuration from your system, enter:
        ifconfig  sl#  detach
   5.If SMIT was used to add the SLIP line, use SMIT again to remove it.
This does not, however, kill the slattach.
Other Notes on SLIP
     ** IMPORTANT NOTE: With AIX releases prior to 3.2.4, when configuring
multiple SLIP lines on a single RISC
     System/6000, make sure direct or leased-line interfaces are configured
first and are the lowest numbered interfaces.
     Example: If there are three interfaces, SL0, SL1, SL2, and one is over
leased-line, that one should be defined as SL0.
     Any interfaces defined to use modems (which take more time to setup by
system) should be configured or defined last
     as SL2 or SL3.
     Troubleshooting: If a leased-line SLIP interface is defined last or as
a higher number (sl1 as opposed to sl0) a problem
     might occur at boot time. The system may assign it to sl0 and the user
may not be aware of the change. SLIP will be
     up but a ping to one address may be crossed to another.
     A SLIP connection, when configured from the command line, will stay in
effect only until the system is reset or
     powered down. This is because nothing is permanently added to the
system's startup files or the ODM database.
     It is for this reason that we suggest experimenting with SLIP first on
the command line -- then, once the configuration is
     understood, add it through SMIT.
     On a SLIP direct connect, no "baud rate" or "dial string" is needed. A
direct connect is where a serial cable is run
     directly between two systems (no modems involved).
     On a SLIP connection over a LEASED-LINE, no "dial string" is needed.
Leased-line is where there is a dedicated
     phone line between two modems.
     Ports MUST be disabled for SLIP (not shared or delayed, so no getty is
running on the port).
     When slattach is used to link a tty to a SLIP interface, it will take
the FIRST available SLIP interface. If more than one
     exists, a problem might occur during bootup when links to ttys might
occur in the wrong order (right tty with wrong
     interface and vice-versa).
     The SLIP driver is the file "/etc/network/if_sl".
     If you cannot ping or access a remote machine, the most likely causes
would be:
          Incorrect modem or port settings
          Check that XON is not on either modem or port. Verify that DTR and
CD handling are set correctly in both
          modems.
          Bad cabling or phone lines
          Test connection with ATE or cu by dialing other system and being
able to login. This would be as a first test but
          does not eliminate the chance of port or modem problems. Use IBM
cabling or cable that has adequate
          shielding.
          Check modem profile. If the "Quiet Enable" (or "Q" value) is set
to "1", as with most Hayes compatibles, try
          changing it to "0" (for example, AT&Q0). If the TD and RD lights
flicker when you ping across SLIP, this might
          be your problem.
          Incorrect or conflicting network addresses
          Issue a "netstat -i" to examine.
          A port is not set to "disable".
#### Notes on Adding RTS Handshaking to a tty Port
For AIX levels 3.2.5 and greater, there is a field for RTS in the smit panel
for Adding a TTY Device. For these levels, use
smit to add RTS handshaking.
For AIX levels before 3.2.5, use one of the methods in this section to add
RTS handshaking.
Is an example of how to add RTS to a tty port on the 6000 using stty command
as followed :
If You Wish to Use stty
   1.Edit the "/etc/uucp/Devices" file to contain the following in the
leftmost column: "Direct tty# - Any direct".
     Note: Replace # with your tty number.
   2.Remove getty on the port with "pdisable tty#".
   3.Run the command "cu -ml tty#".
   4.On another terminal or session issue command:
        stty add rts < /dev/tty#
   5.Type "~." (that's a tilde and a period to end cu session).
     Note: If cu is not installed on your system, use any available
communication program to connect to the modem. This
     will keep "carrier" signal high and allow the stty command to complete.

 
http://www-frec.bull.com/docs/download.htm
Finalmente dei siti con software per AIX! Sembrano decisamente
interessanti!
E c'e' anche mc (il mio tool preferito...)
Ciao
Sabino
-- 
      +---------------------------------------------------+
      | Windows NT has detected that there were no errors |
      | for the past 10 minutes. The system will now try  |
      | to restart or crash. Click the OK button to       |
      | continue.                                         |
      |                       < Ok >                      |
      +---------------------------------------------------+
-----------------------------------------------------------------
Sabino Maggi                     !  tel: (+39) 011-3919-449 *NEW*
IEN "G. Ferraris"                !  fax: (+39) 011-3463-84
Strada delle Cacce, 91           !  e-mail: 
ma...@ien.it
I-10135 Torino, Italy            !  http:   
www.ien.it/~maggi
-----------------------------------------------------------------