PS/2 - TCP/IP, NFS

• 3Com Hardware Installation
• Test
• Protocol Configuration

3Com Hardware Installation

• Install the 3Com board - and connect it to the network (BNC / Tranciever)
• Continue with System configuration (386 - reference diskette, 486 - doesn't need it)
• Keyboard menu appears - Press ENTER
• Configuration error 00165: Automatically configure the system Y/N? - enter N
• Main menu is displayed: Select Set Configuration (2) to change your configuration
• The internal hardware config is displayed: The address range can be modified to avoid conflicts of addresses.
• Check your network connection (BNC/AUI) and set the card accordingly.
• Save the configuration and exit. Reboot the system.

Test

• Test the system with the PING command to your own IP-Address and afterwards to another IP-Address.
  A good result of the PING command should include 0% packet loss. A failure of a PING command is usually a hardware problem. Check your connections to the network.
  
• After defining the remote host machine, mount and test a file transfer.

Protocol Configuration

PS/2 VERSION 3.8 - NFS

• If the hostname of the station is aixps2, and there is another PS2 with the same name, add alias name to the station, in sciutil -> communication -> TCP/IP -> host configuration.
• Define the stanza from "sciutil"
• The stanza is defined by the sciutil application like:

/u/aux/jobs/nripro.j/Raid 1. p:

• Change the stanza manually to be:

/u/dO/jobs/raid1.j:

• Add in the files/etc/rc.nfs and /etc/.rc.nfs, at the end the command:
  /etc/mount -vt nfs_mount
• For each stanza create the relevant job directory under D0 from the application. In this case create the directory "raid1", (the .j is created automatically by the application).
• Reboot the PS2 in order to mount the NFS devices.

CONNECT THE PS/2 TO THE INDIGO

NOTE: Changes must be made to both systems. Make arrangements for an INDIGO engineer to be on site.

NOTE: If the site has a Ripro Server, verify zone routing and publishing.

1. The version of the PS/2 should be version 4.BS10 and up.
2. The version of the Indigo should be 2.1 and up.

• The Indigo Eprint1000 is a product based on Sun Platform.
• CreoScitex transfers CHS and LHS files from the PS/2 to the Indigo, to directory /usr/eprint/pic0/scitex.
  Indigo runs a script which recognize the scitex's files, moves it to directory /usr/eprint/pic0/lan and expose it.
• The NFS definition in the PS2 for the Indigo, is in the same way as any other remote NFS server (such as RiproServer, Savanna, or Contex).
• Parameters to be configured in the PS2 version4 (from Sciutil):

under the NFS definition:

Logical name:	any name.
Mount Level:	~FL (to copy files like CT, LW)
Application Mount:	Yes or NO (as requested by the user, NO is recommended).
path:	/usr/eprint/pic0/scitex (this directory must defined and exported in the indigo machine).

Important: since version 4 may create NLW as a result of the Rip and not LW, there is need to define the PS Defaults with the option :Create CT = YES (AVR), and convert all the spot colors to proccess colors. In this way, the Rip will create LW only and not NLW.

PS/2 VERSION 4 - NFS STANZA

NOTE: The Sciutil configures the PS/2. DO NOT manually make any changes. The results of the Sciutil configuration are shown below.

1. Job - Level definition ( the pages created by the clients, MAC, PS2 .... ).

/u/nfs/jobs/arch1.2.1.j:

2. File - Level definition ( the pages created automatically by the PS/2 application .... ).

/u/nfs/jobs/indigo.j/page. p: