12.1 Monitoring the Terminal Bootup

To verify and test your Novell Linux Point of Service installation:

  1. Attach a Point of Service client to the Branch Server network.

  2. (Optional) Verify the LDAP structure on the Administration Server using a GUI-based LDAP browser, such as GQ, or an ldapsearch command.

    For example: 

    ldapsearch -x -h administration_server_name -b o=mycorp,c=us -s base -D cn=admin,o=mycorp,c=us -w password

  3. Verify the following LDAP object settings:

    • The scCashRegister object which matches the model type of the Point of Service client must exist in LDAP; for example, IBMSurePOS300Series.
    • There must be an scPosImage object for each image in the /tftpboot/image/ directory on the Branch Server. The scPosImageDn attribute within each object must correspond to an existing Point of Service image.

      IMPORTANT:You must create the scPosImage objects and set the scPosImageVersion attribute to Active before you boot the Point of Service terminals. The Point of Service terminals require an scPosImage object with an active scPosImageVersion attribute before they can download the corresponding physical image from the Branch Server at boot time. For more information on setting the scPosImageVersion attribute to Active, see Activating Images.

    For further information how to modify and add LDAP entries for your specific Novell Linux Point of Service system environment, refer to Using posAdmin to Manage the LDAP Directory in the Novell Linux Point of Service 9 Administration Guide.

  4. Verify that the Point of Service client images and their corresponding MD5 checksum files are available in /tftpboot/image/ directory on the Branch Server.

  5. Verify that the initrd.gz and linux images are available in the /tftpboot/boot/ directory on the Branch Server.

  6. Power on the Point of Service client.

    You can watch the Branch Server log messages using the following command:

    tail -f /var/log/messages

  7. While the Point of Service client is booting, check if there are tftpd entries.

    For example:

    • .. bs1 tftpd[31434]: Serving /boot/pxelinux.0 to 192.168.2.15:2070
    • .. bs1 tftpd[31435]: Serving /boot/pxelinux.cfg/C0A8020F to 192.168.2.15:57217
    • .. bs1 tftpd[31436]: Serving /boot/pxelinux.cfg/C0A8020 to 192.168.2.15:57090
    • .. bs1 tftpd[31437]: Serving /boot/pxelinux.cfg/C0A802 to 192.168.2.15:56963
    • .. bs1 tftpd[31438]: Serving /boot/pxelinux.cfg/C0A80 to 192.168.2.15:56836
    • .. bs1 tftpd[31439]: Serving /boot/pxelinux.cfg/C0A8 to 192.168.2.15:56709
    • .. bs1 tftpd[31440]: Serving /boot/pxelinux.cfg/C0A to 192.168.2.15:56582
    • .. bs1 tftpd[31441]: Serving /boot/pxelinux.cfg/C0 to 192.168.2.15:56455
    • .. bs1 tftpd[31442]: Serving /boot/pxelinux.cfg/C to 192.168.2.15:56328
    • .. bs1 tftpd[31443]: Serving /boot/pxelinux.cfg/default to 192.168.2.15:56201
    • .. bs1 tftpd[31444]: Serving /boot/linux to 192.168.2.15:56202
    • .. bs1 tftpd[31445]: Serving /boot/initrd.gz to 192.168.2.15:56203
    • .. bs1 dhcpd: DHCPDISCOVER from 00:06:29:e3:02:e6 via eth0
    • .. bs1 dhcpd: DHCPOFFER on 192.168.2.15 to 00:06:29:e3:02:e6 via eth0
    • .. bs1 dhcpd: DHCPREQUEST for 192.168.2.15 (192.168.2.1) from 00:06:29:e3:02:e6 via eth0
    • .. bs1 dhcpd: DHCPACK on 192.168.2.15 to 00:06:29:e3:02:e6 via eth0
    • .. bs1 tftpd[31454]: Serving CR/config.00:06:29:E3:02:E6 to 192.168.2.15:32768
    • .. bs1 tftpd[31455]: Fetching from 192.168.2.15 to upload/hwtype.00:06:29:E3:02:E6

    The Point of Service terminal performs a PXE boot to receive the Linux kernel and its first stage boot image, initrd.gz. For detailed information on the Point of Service boot process, see Section 11.4, Booting the Point of Service Terminal.

  8. Watch for the hwtype.MAC_address file below the /tftpboot/upload directory (for example, hwtype.00:06:29:E3:02:E6). This file contains the information required to create the terminal’s workstation object (scWorkstation) in LDAP and determine which image and configuration settings should be included in the terminal’s configuration file. For more information, see The hwtype.MAC_address File in the Novell Linux Point of Service 9 Administration Guide.

  9. Watch to see if the Point of Service client is able to boot the second stage image. This is the client image configured in LDAP (scPosImage) and downloaded from the /tftpboot/image/ directory on the Branch Server (for example, the browser-2.0.21 image).

  10. If everything proceeds normally, the Point of Service terminal boots and you will see the login prompt.

    If the boot is successful, the config.MAC_address for the terminal is written below the /tftpboot/CR/MAC_address/ directory on the Branch Server. For example, if a terminal’s MAC address is 00:06:29:E3:02:E6, the config.00:06:29:E3:02:E6 file will be located in the /tftpboot/CR/00:06:29:E3:02:E6 directory. Additionally, the scWorkstation object for the Point of Service terminal is created in the LDAP directory.