Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    Self-check setup with DHCP

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    Can Self-check work with DHCP in such a way that the IP address can change from one time to another?

    The only place I see IP numbers for the self-check server is in tab_attr_sub_library. Since the self-check server does not use the GUI client, I don't know of any way in which to add it with a Station ID. We were using a static IP, but our networking group would rather we use DHCP which would boot into a specified range. Can tab_attr_sub_library take a wild card similar to the way in which server_ip_allowed for X services can, or does it have to be a specific IP number?

    Or, are we missing somewhere else where the IP for the server is set? tab_attr_sub_library was the only place I saw when reviewing tables.

    Network changes have already been made, and one server is down. Our others will stop if/when rebooted. Hence the High priority of this request.

    Thanks,
    Tom [ <Tom Hanstra > ]
    [ <Alan Manifold > ]
    [ <Jerry Specht > ]
    [ <Jerry Specht > ]

    Resolution:
    As described in the tab_attr_sub_library header, it can have URLs with wildcards and/or station ID's. The distributed usm50 tab_attr_sub_library contains examples of both.

    KB 6677 describes a case where the self-check machine was not in tab_attr_sub_library; it got the message "Apply to Circulation Desk - Unable to loan/renew item".

    [From site:]

    Closing this. Unknown to me, the port was mistakenly changed on the self-check server. Once we got the port set back to the right number, things started working.

    • Article last edited: 10/8/2013