Author: paul.deluca

How Do I add a Printer in AIX?

AIX Printer Setup

The easiest way to add a printer is to follow this video tutorial: http://screencast.com/t/ClPiIwe5E

Manual Steps are:

Login as root

Add hosts entry: echo "172.17.189.5 lp1" >> /etc/hosts

Add a print queue in smit: smit queue -> Add -> Remote -> Standard (or execute the command directly:

/usr/lib/lpd/pio/etc/piomisc_ext mkpq_remote_ext  -q 'lp1' -h 'lp1' -r 'lp1' -t 'aix' -T '999' -C 'FALSE'
echo "lp -dlp1" > /usr/spool/uv/lp1.dvr
chmod 777 /usr/spool/uv/lp1.dvr
su - uv
Spooler -> Device -> Maintain
Use ENTER to advance, selecting all defaults unless otherwise specified.
Name = LP1 (shows all caps)
Path = /dev/null
Driver = lp1.dvr (answer yes to prompt)
Lock File 1 = lock.lp1
ESC -> Q -> ENTER to exit
Apps Setup:

    
	
  1. su - eclipse
    2. 
	
  2. F2 -> F -> P -> A (Assign Printer)
    3. 
	
  3. Printer/Fax = new
    4. 
	
  4. Name = 1 (# from lp#)
    5. 
	
  5. Type = (press F10 to select)
    6. 
	
  6. ESC to apply and exit
    7. 
	
  7. L (Location Maintenance)
    8. 
	
  8. Location = NEW
    9. 
	
  9. Name = HERE
    10. 
	
  10. Ship Ticket Branch = (blank)
    11. 
	
  11. Physical Branch = (blank)
    12. 
	
  12. Printer = 1 (number of printer)
    13. 
	
  13. ESC to apply and exit
    14.

Do I need anti-virus software on my Linux server?

The Eclipse database server runs the Red Hat Enterprise Linux operating system, not Microsoft Windows, the common target of virus attacks. As explained in this Red Hat knowledge base article, Red Hat does not consider viruses a threat to their Linux operating system. Rather than installing anti-virus software, Red Hat suggests implementing standard UNIX security “best practices” to secure the server, which Eclipse implements when configuring your Linux server. We also encourage our customers to enforce strong user password policies and keep their servers behind a firewall.

If your company’s security policies mandate the presence of additional anti-virus software, even on a Linux server, we recommend installing the free, open-source ClamAV software. If you choose to install anti-virus software, our standard 3rd party software policy applies: you are welcome to install and operate 3rd party software on the Eclipse server, but Eclipse will not certify or provide technical support for any of these software products, so you must obtain technical support from the vendor or elsewhere.

Setting up a Local Printer (USB)

Setting Up a Local Printer

Local printing allows you to attach a printer to a users PC, install it on their PC and allow the user to print from Eclipse as well as windows. This is not a network printer.

1. Configure the Printer to Print from Windows. The Printer may be a Networked Windows Printer, or connected locally utilizing a USB Port or a Parallel Printer Port. Make the Printer your Default Windows Printer if using USB. For Parallel Port or Networked Windows Printers, the Printer need not be the Default Windows Printer (although we would RECOMMEND it be the Default Windows Printer.)

2. Login to Eclipse.

3. Select Terminal Setup from the F2-System/System Files… menu.

4. Locate your Terminal ID and place the cursor on that line. If there is not one you will need to setup a Terminal Id. This can be done by accessing the Terminal Setup screen in Eclipse. F2/F/T.

Once your ID is created, Highlight it and select ALT/S to get the Local Printer Menu

Figure 1 Local Printer Menu.

5. Under the Local Printer field hit the F10 key and select the ‘HPLJ’ or HPLJ-1TRAY’  for a Laser Printer or ‘Printronix’ for a Dot Matrix or Zebra Label Printer. Local Laser Printers support One Tray ONLY.

6. Under the Form Loaded field hit the F10 key and select the form you desire.

\*ANY* is the most common form loaded on a Local printer and means that

everything you print from Eclipse will print to your Local printer even if you select another Eclipse printer..

7. Press Esc to exit the Local Printer Assignment screen and save your settings.

8. Access your Eterm Configuration screen by selecting Configure and then Communications from the grey menu bar in Eterm.

Figure 2: Configure/Communications screen.

9. Move the cursor to the ID field and type in your Terminal ID.

Note: It is important to type your User ID exactly as it appears on the Terminal Setup screen, including capitalization where appropriate.

10. Click on OK to save your changes.

11. Access the Configure/Printing menu in eterm and check off ‘Default Printer’ if USB connected, ‘Selected Printer’ may be used if Network or Parallel Port is used. This will give you the option to select the installed printer from your computers installed printers. Once selected click on OK.

How do I upgrade the Fusion-io drivers?

This article was last updated April 2011.

Any time the kernel is upgraded, you’ll need to recompile and reinstall the drivers. As such, it is important to plan your kernel upgrades in advance and perform testing after the first boot using a new kernel.

If you are an IBM customer using IBM High IOPS adapters, please refer instead to the latest IBM documentation, drivers and firmware located at IBM Fix Central.

The 2.3.x driver builds and runs on a much wider range of kernels than the 1.2.x driver series. It accomplishes this using a new portability layer to abstract itself away from the operating system internals. By following the procedure below, you will obtain a working driver, built for the specific kernel running on your system.

Follow the instructions based on the version of your driver.

Building the Fusion-io Drivers From Source

To view a step-by-step screencast of this process, click here.

Before beginning, download the ioDrive driver source rpm for RHEL from the Dell Fusion-io support site to a temporary directory. At minimum, you’ll need the latest version of the following packages:

  • fio-common
  • fio-firmware
  • fio-sysvinit
  • fio-util
  • iomemory-vsl
  • libfio

Here’s a screenshot showing the packages that need to be downloaded.

Remove prior versions of the ioDrive driver rpm

yum remove iomemory* iomanager* iodrive* fio-* libfio*
rm -rf /usr/src/redhat/RPMS/x86_64/iomemory-vsl-*

For Red Hat Enterprise 5, install the gcc 4.x and kernel-devel packages for your current kernel. The kernel-headers package is also needed, but is typically installed as part of the base operating system.

yum -y install kernel-headers-`uname -r` kernel-devel-`uname -r` rpm-build gcc lm_sensors net-snmp

Change to the directory where you downloaded the ioDrive driver source RPM and begin the rebuild process.

rpmbuild --rebuild iomemory-vsl*.src.rpm

Install the newly-built drivers.

yum install --nogpgcheck fio-sysvinit* fio-common* fio-util* libfio* fio-firmware* iomemory-vsl-source* /usr/src/redhat/RPMS/x86_64/iomemory-vsl-*

Check the status of the ioDrive(s):

fio-status

Found 1 ioDrive in this system

fct0 Attached as 'fioa' (block device)
 Fusion-io ioDIMM3 160GB, Product Number:FS1-001-161-ES SN:6168
 Firmware v5.0.1, rev 42895
 161 GBytes block device size, 198 GBytes physical device size capacity.
 PCI:0c:00.0, Slot Number:6
 Internal temperature: avg 42.3 degC, max 44.3 degC
 Media status: Healthy; Reserves: 100.00%, warn at 10.00%

Upgrading the Fusion-io Firmware

In the previous section, you should have already downloaded and installed the latest firmware package. If not, you may download the fio-firmware package from the Fusion-io Support website to proceed. Once the firmware package is installed, it needs to be applied to the cards.

To upgrade the firmware:

fio-update-iodrive /usr/share/fio/firmware/iodrive_*.fff

Watch the output of the upgrade process and reboot when complete.

Update the Fusion-io Init Scripts

NOTE: this is the new recommended configuration for any customer using multiple Fusion-io ioDrives in a RAID array, as it ensures the cards are all initialized before bringing the RAID array and filesystems online. Reference: http://kb.fusionio.com/KB/a64/loading-the-driver-via-udev-or-init-script-for-md-and-lvm.aspx

Uncomment the blacklist line:

vim /etc/modprobe.d/iomemory-vsl.conf
# To keep ioDrive from auto loading at boot when using udev, uncomment below
blacklist iomemory-vsl

Backup /etc/fstab, and modify it to add “noauto 0 0” to the datavg filesystems:

cp /etc/fstab /etc/fstab.`date +%Y%m%d.%H%M%S`
vim /etc/fstab

Example:

/dev/datavg/u2          /u2                     ext3    defaults,noauto        0 0
/dev/datavg/eclipse     /u2/eclipse             ext3    defaults,noauto        0 0
/dev/datavg/edi         /u2/edi                 ext3    defaults,noauto        0 0
/dev/datavg/ereports    /u2/eclipse/ereports    ext3    defaults,noauto        0 0
/dev/datavg/pdw         /u2/pdw                 ext3    defaults,noauto        0 0
/dev/datavg/uvtmp       /u2/uvtmp               ext3    defaults,noauto        0 0
/dev/datavg/kourier     /u2/kourier             ext3    defaults,noauto        0 0
/dev/datavg/crashplan   /usr/local/crashplan    ext3    defaults,noauto        0 0

Uncomment “ENABLED=1” in /etc/sysconfig/iomemory-vsl to enable init script:

vim /etc/sysconfig/iomemory-vsl
# If ENABLED is not set (non-zero) then iomemory-vsl init script will not be
# used.
ENABLED=1

In the same /etc/sysconfig/iomemory-vsl file, add the RAID array(s) and mount points. For example:

MD_ARRAYS="/dev/md0"
LVM_VGS="/dev/datavg"
MOUNTS="/u2 /u2/edi /u2/eclipse /u2/eclipse/ereports /u2/pdw /u2/uvtmp /u2/kourier /usr/spool/crashplan"

Enable the init script:

chkconfig iomemory-vsl on
chkconfig --list iomemory-vsl

Resources