DeveloperNet Professional Developer Avanti Product Banner PartnerNet Authorized ISV Partner
avanti's NodeMaster®
*** Conn List:   Licensed / Authenticated / N-L-I / Inactive?   User / NLM?   Which NLM? ***
*** File Info:   What Files Are Open?   By Which Connections?   User / NLM?   Which NLM? ***
*** Conn Info:   Status (DS / Authenticated / Bindery)?   NLM / User (Which NLM)?   Files In Use? ***
*** Logging:   Authenticate / Login / Logout (OK / Failed).   Allocate / Clear Conns.   Users & NLMs. ***
*** Management:   Clear Connections.   Close Open Files.   Message (NetWare SEND Messages) Users. ***
*** Security:   Opts Let Users View &/or Manage Connections.   Admin / Supervisor Equivalent Full Rights. ***
*** Support: Server -   NetWare v5.x / v6.x (incl. OES NetWare) / Client: Any Browser With JavaScript Support ***



Overview
NodeMaster® provides a quick and easy solution for monitoring / managing Connections and Open Files, as well as tracking and logging Connection activity, on a NetWare Server.
    Secure Help Desk Tool: Manage Connections & Open Files
    NodeMaster® provides a quick and easy solution for viewing and managing Connections and Open Files on a NetWare Server. It allows virtually any connection to view Connection and Open File information but restricts the actual management (i.e., clearing of connections or closing of open files) to Admin (and equivalent) users, plus specifically defined Users (up to 8) and/or Group members. This additional security option allows for providing select Users with sufficient rights to manage Connections and Open Files WITHOUT providing unneeded or excessive rights (i.e., Server Operator rights or access to the Server System Console or Server Console utilities). Merely loading the NodeMaster NLM on a Server provides Admin equivalent Users and specifically authorized Users the means to easily manage Connections and Open Files.
    The Secure Help Desk Tool For Managing Connections And Open Files On A NetWare Server!

    Connection Tracking: Login / Logout / Password Change / & More . . .
    NodeMaster can be configured to track and log activity associated with connection allocations, authentications, and user logins/logouts, including information on NLM connections and which NLM is using each connection. The activity can be logged in one or more formats (.TXT = Fixed Text, .CSV = Quote Enclosed Comma Delimited, and .DAT = Binary).
    Connection / User Access Tracking Without The Overhead Of Full Auditing On A NetWare Server!

    Simple Browser Interface: Customizable .HTML Templates
    NodeMaster information can be accessed using your favorite browser (JavaScript support required) simply by entering the IP address of the Server and the defined NLM Port. Once loaded, information on Connections, Open Files, and more is provided via JavaScript include files and displayed by .HTML templates which can be customized to your specific needs.
    User Customizable Browser Interface For Accessing Connection / Open File Information On A NetWare Server!

Operation
NodeMaster provides real-time Connection and Open File information to most any browser with JavaScript support enabled, merely by entering the Server IP address, NDS/eDirectory name, or URL and the appropriate defined Port. The type of information provided is dependent upon the use of keywords and options, or links within the pages, which specify how the request is processed.
    Client Browser Access
    http://{server_ip}:{port}/[.html][?_keyword_][&opt=x]
    http://{server_name}:{port}/[.html][?_keyword_][&opt=x]
    http://{server_url}:{port}/[.html][?_keyword_][&opt=x]

    Notes:

    • Items surrounded by braces {} are required while items surrounded by brackets [] are optional. A vertical bar | separates options within a required item.
    • The Server name or URL can be used in place of its IP address if defined in the workstation's ETC\HOSTS file or it can be resolved via DNS/NIS.
    • If [.html] is specified, it will be interpreted as a .HTML page to use in place of the default page associated with the [?_keyword_] which was included with the software. If a custom .HTML page is specified, it must reside in the same directory where the NodeMaster NLM resides. [.html] should be composed using Basic .HTML and JavaScript only. No special processing of CGI, PHP, Perl, SSI, etc. is supported.
    • Specific information can be retrieved by appending a supported [?_keyword_] to the IP address and Port (refer to examples). Some [?_keyword_] options also support additional parameters (refer to specific [?_keyword_]).
    • By default, ?_CONNLIST_ is assumed if no [?_keyword_] is specified.

    Security
    Any Server connection (and optionally, any workstation on the network) with a browser that supports JavaScript can view the Connection and Open File information on a NetWare Server (although Remote Access can be limited - see REMOTE_ACCESS option in the _CONFIG_ section). However, only workstations with a valid Admin (or equivalent) connection to the Server, or specifically authorized Users and/or Group members with a valid connection to the Server, can actually manage the connections (i.e., clearing connections or closing open files). And only workstations with a valid Admin (or equivalent) connection to the Server can modify the configuration parameters or define Users and/or Group members to grant additional rights.

    Client Browser Keyword Support
    The following are the supported keywords and the information provided.

      _CONFIG_   (sample screen link)
      Tries to locate/load CONFIG.HTM (unless some other [.html] page is specified) from the same directory where the NodeMaster NLM resides. If successful, also creates CONFIG.JS containing JavaScript defined variables which are used by CONFIG.HTM (or can be used by the [.html] specified page) to display information about the current configuration. The active configuration can be review, modified, and updated using this option when used with the included CONFIG.HTM page.

        Examples:

        http://192.168.1.1:8888/?_CONFIG_
        http://AVANTI_FS1:8765/?_CONFIG_
        http://www.avanti-fs1.com:8901/?_CONFIG_

        Attempt to access the NodeMaster NLM running on the Server

        1. assigned IP address 192.168.1.1 via Port 8888
        2. named AVANTI_FS1 via Port 8765
        3. associated with URL www.avanti-fs1.com via Port 8901
        to try to load CONFIG.HTM (supplied) and CONFIG.JS (generated) for purposes of managing NodeMaster NLM configuration.

        http://192.168.1.1:8888/myconfig.html?_CONFIG_
        Attempt to access the NodeMaster NLM running on the Server assigned IP address 192.168.1.1 via Port 8888 to try to load myconfig.html (instead of CONFIG.HTM) and then generate CONFIG.JS which can be used by myconfig.html.

        Note: The workstation accessing the Server via a browser must have a Logged In connection to the Server with Admin (or equivalent rights) to modify / update the configuration.

        Information / Options Provided By CONFIG.HTM:
        The CONFIG.HTM page provides the current settings for the supported configuration parameters with the option to modify and update them.

        Note: Options are stored in NODEMSTR.INI file which is read when the NLM loads and rewritten when updated. If the configuration file is manually edited while the NLM is loaded, the NLM must be reloaded before any changes take effect. For documentatoin purposes, the default values when installed are shown with the supported options in braces.

        AUTH_GROUP=   [group_name.context]
        Members of Group are granted operational rights to manage connections (same as Admin/Supervisor) but not to change configuration parameters. Leave blank to not authorize any Group.

        AUTH_USERS=   [user_name.context[,username.context[...]]]
        Specified users (maximum of 8, separated by commas) are granted operational rights to manage connections (same as Admin/Supervisor) but not to change configuration parameters. Leave blank to not authorize any User(s).

        BROWSER_PORT=8888   {1024 - 65535}
        Port to use when retrieving NodeMaster NLM information via browser interface.
        Note: NLM must be reloaded for any change to take effect.

        CONN_ALLOC=OFF   {OFF | ON}
        Monitor / log any new connection allocations.

        CONN_CLR=OFF   {OFF | ON}
        Monitor / log any connections which are cleared.

        CONN_LOGIN=ON   {OFF | ON}
        Monitor / log all connection login attempts (Bindery/NDS).

        CONN_LOGOUT=ON   {OFF | ON}
        Monitor / log all connection logouts (Bindery/NDS).

        DS_AUTH=ON   {OFF | ON}
        Monitor / log DS Authentication attempts (with OK or error result).

        DS_CHGPWD=ON   {OFF | ON}
        Monitor / log DS Change Password attempts (with OK or error result).

        DS_CHKPWD=ON   {OFF | ON}
        Monitor / log DS Check Password attempts (with OK or error result).

        DS_LOGIN=ON   {OFF | ON}
        Monitor / log DS Login attempts (with OK or error result).

        DS_LOGOUT=ON   {OFF | ON}
        Monitor / log DS Logout attempts (with OK or error result).

        EXCL_NLM_CONN_ALLOC=ON   {OFF | ON}
        Exclude connections allocated by NLMs on the Server.
        Note: Some NLMs allocate / clear connections as needed which can clutter the log with non-critical entries.

        EXCL_NLM_CONN_CLR=ON   {OFF | ON}
        Exclude NLM owned connections cleared on the Server.
        Note: Some NLMs allocate / clear connections as needed which can clutter the log with non-critical entries.

        EXCL_NLM_DS_AUTH=ON   {OFF | ON}
        Exclude NLM DS Authentication events on the Server.
        Note: Some NLMs Authenticate to DS as needed which can clutter the log with non-critical entries.

        LOG_CSV=OFF   {OFF | ON | DAILY | DAY | WEEK[LY] | MONTH[LY]}
        Log activity in quote ("") enclosed, comma delimited formatted file.
        Options:

        • OFF = no log
        • ON = continuous logging to NODEMSTR.CSV
        • DAILY | DAY = Archive daily @ 00:00 to NMLOGCSV.### (Julian day)
        • WEEK[LY] = Archive each Sunday @ 00:00 to NMLOGCSV.W## (week of year)
        • MONTH[LY] = Archive 1st of each month @ 00:00 to NMLOGCSV.M## (month ##)
        Note: See .CSV Log File section for format description.

        LOG_DAT=OFF   {OFF | ON | DAILY | DAY | WEEK[LY] | MONTH[LY]}
        Log activity in raw (binary) data formatted file.
        Options:

        • OFF = no log
        • ON = continuous logging to NODEMSTR.DAT
        • DAILY | DAY = Archive daily @ 00:00 to NMLOGDAT.### (Julian day)
        • WEEK[LY] = Archive each Sunday @ 00:00 to NMLOGDAT.W## (week of year)
        • MONTH[LY] = Archive 1st of each month @ 00:00 to NMLOGDAT.M## (month ##)
        Note: For future access via Avanti or End User custom utility.

        LOG_TXT=ON   {OFF | ON | DAILY | DAY | WEEK[LY] | MONTH[LY]}
        Log activity in fixed field / record length ASCII text formatted file.
        Options:

        • OFF = no log
        • ON = continuous logging to NODEMSTR.TXT
        • DAILY | DAY = Archive daily @ 00:00 to NMLOGTXT.### (Julian day)
        • WEEK[LY] = Archive each Sunday @ 00:00 to NMLOGTXT.W## (week of year)
        • MONTH[LY] = Archive 1st of each month @ 00:00 to NMLOGTXT.M## (month ##)

        NLM_NAME=ON   {OFF | ON}
        Display NLM name associated with NLM connections.
        Note: Requires SCREEN_ACTIVITY also be ON (display only option).

        QUEUE_BUFFERS=1000   {100 - 10000}
        Number of event entries which can be buffered to avoid loss.
        Note: NLM must be reloaded for any change to take effect.

        REMOTE_ACCESS=OFF   {OFF | ON}
        Allow remote access (i.e., OFF requires workstation running the browser to have an active Server connection).

        SCREEN_STATUS=ON   {OFF | ON}
        Display logged activity on NodeMaster Activity screen.

        ZERO_FILL_IP=OFF   {OFF | ON}
        Enable (192.168.001.001) / Disable (192.168.1.1) zero filled formatting of IP addresses.



      _CONNINFO_   (sample screen link)
      Tries to locate/load CONNINFO.HTM (unless some other [.html] page is specified) from the same directory where the NodeMaster NLM resides. If successful, also creates CONNINFO.JS containing JavaScript defined variables which are used by CONNINFO.HTM (or can be used by the [.html] specified page) to display information about a specific Server connection, including which files are open (in use) by the connection.

        Examples:

        http://192.168.1.1:8888/?_CONNINFO_
        http://AVANTI_FS1:8765/?_CONNINFO_&conn=1
        http://www.avanti-fs1.com:8901/?_CONNINFO_&conn=12

        Attempt to access the NodeMaster NLM running on the Server

        1. assigned IP address 192.168.1.1 via Port 8888
        2. named AVANTI_FS1 via Port 8765
        3. associated with URL www.avanti-fs1.com via Port 8901
        to try to load CONNINFO.HTM (supplied) and CONNINFO.JS (generated) for purposes of viewing
        1. the first active connection in the Server's connection table
        2. connection 1
        3. connection 12
        information, including any files open (in use) by the connection. NetWare SEND Messages can also be sent to the connection, if Logged In to the Server, when the supplied CONNINFO.HTM page is used.

        http://192.168.1.1:8888/myconninfo.html?_CONNINFO_
        Attempt to access the NodeMaster NLM running on the Server assigned IP address 192.168.1.1 via Port 8888 to try to load myconninfo.html (instead of CONNINFO.HTM) and then generate CONNINFO.JS which can be used by myconninfo.html.

        Notes: First active connection in the Server's connection table is assumed if no [&conn=#] is specified ( # is the connection number).

        Information (CONNINFO.HTM):
        The CONNINFO.HTM page provides information about a specific connection.

        Connection Information

          Conn - Connection number (slot)
          User - Name of the Licensed User (if logged in)
          NLM - NLM name (if NLM established the connection)
          Status - Connection state (Licensed / Authenticated / Bindery / etc.)
          Time - Connection time (when allocated)
          Type - Connection type (IP / IPX / NLM / etc.)
          Address - Connection address (IP / IPX)

        Open File Table

          Open File - File open (in use) on the Server by the connection
          Open Mode - File access in use / allowed by the connection
            S - File open in Shared mode
            L - File Locked (exclusive mode)
            R - File open for Read operations by connection
            W - File open for Write operations by connection
            r - Other connections can open file for Read operations
            w - Other connections can open file for Write operations

          Note: Left click on any information in an Open File row to link to the _FILEINFO_ (FILEINFO.HTM) page for that Open File.


        Buttons / Options (CONNINFO.HTM):
        The CONNINFO.HTM page provides buttons / options to access additional information or to manage the connection.

        Connection List - Link to _CONNLIST_ (CONNLIST.HTM)

        Open File Search - Link to _FILEINFO_ (FILEINFO.HTM)

        Prev - Previous lower active connection (1 is the lowest active connection)

        Next - Next higher active connection (up to maximum active connections)

        Refresh - Refresh (update) the connection information

        Send NetWare Message - Compose / Send message to this connection (if logged in)

        Terminate - Terminate (clear / kill) this connection

        Note: Any workstation attempting to Terminate a connection must have a Logged In connection to the Server as an Admin (or equivalent) user or as a specifically authorized User or Group member.



      _CONNLIST_   (sample screen link)
      Tries to locate/load CONNLIST.HTM (unless some other [.html] page is specified) from the same directory where the NodeMaster NLM resides. If successful, also creates CONNLIST.JS containing JavaScript defined variables which are used by CONNLIST.HTM (or can be used by the [.html] specified page) to display information about the active connections on the Server.

        Examples:

        http://192.168.1.1:8888
        http://AVANTI_FS1:8765/?_CONNLIST_
        http://www.avanti-fs1.com:8901/?_CONNLIST_

        Attempt to access the NodeMaster NLM running on the Server

        1. assigned IP address 192.168.1.1 via Port 8888
        2. named AVANTI_FS1 via Port 8765
        3. associated with URL www.avanti-fs1.com via Port 8901
        to try to load CONNLIST.HTM (supplied) and CONNLIST.JS (generated) for purposes of viewing active connections on the Server.

        http://192.168.1.1:8888/myconnlist.html?_CONNLIST_
        Attempt to access the NodeMaster NLM running on the Server assigned IP address 192.168.1.1 via Port 8888 to try to load myconnlist.html (instead of CONNLIST.HTM) and then generate CONNLIST.JS which can be used by myconnlist.html.

        Note: ?_CONNLIST_ is assumed if no [?_keyword_] is specified.

        Information (CONNLIST.HTM):
        The CONNLIST.HTM page provides information about all active connections.

        Connections

          Total - Number of allocated connection slots
          Licensed - Number of licensed connection slots
          Authenticated - Number of authenticated connection slots

        Connection List

          Conn - Connection number (slot)
          User - Name of the Licensed User associated with the connection (if logged in)
          NLM - Name of the NLM associated with the connection (if NLM established the connection)
          Status - Connection state (+ = Licensed / * = Authenticated / % = Authenticated)
          Time - Connection time (when allocated)
          Type - Connection type (IP / IPX / NLM / etc.)
          Address - Connection address (IP / IPX)

          Note: Left click any column heading to sort the connection list using that column's information. Left click the same column heading to reverse the sort order. Left click any information in a Connection row to link to the _CONNINFO_ (CONNINFO.HTM) page for that Connection.


        Buttons / Options (CONNLIST.HTM):
        The CONNLIST.HTM page provides buttons / options to access additional information or to manage the connections.

        Open File Search - Link to _FILEINFO_ (FILEINFO.HTM)

        Send NetWare Message - Compose / Send message to all logged in connections

        Refresh - Refresh (update) the connection information



      _FILEINFO_   (sample screen link)
      Tries to locate/load FILEINFO.HTM (unless some other [.html] page is specified) from the same directory where the NodeMaster NLM resides. If successful, also creates FILEINFO.JS containing JavaScript defined variables which are used by FILEINFO.HTM (or can be used by the [.html] specified page) to display information about which connections are accessing (have open or in use) file(s) matching a specific search pattern.

        Examples:

        http://192.168.1.1:8888/?_FILEINFO_
        http://AVANTI_FS1:8765/?_FILEINFO_&srch="DATA:/ACCT/FILE.TXT"
        http://www.avanti-fs1.com:8901/?_FILEINFO_&srch="SYS:SYSTEM/*.*"

        Attempt to access the NodeMaster NLM running on the Server

        1. assigned IP address 192.168.1.1 via Port 8888
        2. named AVANTI_FS1 via Port 8765
        3. associated with URL www.avanti-fs1.com via Port 8901
        to try to load FILEINFO.HTM (supplied) and FILEINFO.JS (generated) for purposes of
        1. entering a file search pattern.
        2. viewing which connections have DATA:/ACCT/FILE.TXT open (in use).
        3. viewing which connections have files matching SYS:/SYSTEM/*.* open (in use).

        http://192.168.1.1:8888/myfileinfo.html?_FILEINFO_
        Attempt to access the NodeMaster NLM running on the Server assigned IP address 192.168.1.1 via Port 8888 to try to load myfileinfo.html (instead of FILEINFO.HTM) and then generate FILEINFO.JS which can be used by myfileinfo.html.

        Note: Specification must be in Novell NetWare Server native format (i.e., {volume}:{path\}[filename.ext]). Wild cards are supported for the filename and ext portions of the &srch= specification. The workstation running the browser must have a Logged In connection to the Server with Admin / Supervisor (or equivalent rights) to close any of the open (in use) files.

        Information (FILEINFO.HTM):
        The FILEINFO.HTM page provides information on a Open Files which match the Search specificiation.

        Open File Table

          File - Name of the Open File (only shown if the Search is not specific to a single file)
          Conn - Connection Number associated with this instance of the Open File
          Task - Task Number associated with this instance of the Open File
          User - Name of the Licensed User associated with the connection (if logged in)
          NLM - Name of the NLM associated with the connection (if NLM established the connection)
          Mode - File access in use / allowed by the connection
            S - File open in Shared mode
            L - File Locked (exclusive mode)
            R - File open for Read operations by connection
            W - File open for Write operations by connection
            r - Other connections can open file for Read operations
            w - Other connections can open file for Write operations
          Close - Close the associated Open File WITHOUT terminating connection
          All - Close the listed Open File(s) WITHOUT terminating connection(s)

          Note: The workstation running the browser must have a Logged In connection to the Server with Admin / Supervisor (or equivalent rights) to close any of the open (in use) files.


        Buttons / Options (FILEINFO.HTM):
        The FILEINFO.HTM page provides buttons / options to access additional information or to manage the matching file(s).

        All - Close the listed Open File(s) WITHOUT terminating connection(s)

        Close - Close the associated Open File WITHOUT terminating connection

        Search - Search for Open Files matching specified pattern

        Refresh - Refresh (update) the Open File information for matching files



    Log Files
    NodeMaster can also be configured to collect and log activity associated with allocated / cleared connections, logins, logouts, and authentications (see _CONFIG_ section for more information). The supported log file formats are as follows:


      .CSV Log File
      "servername","date/time","event","result","connection","address",""user","nlm"

      Notes: "address" field is the IP / IPX address of the connection. "nlm" field only filled for NLM associated connection activity.

      .DAT Log File
      (Binary, not currently documented. For possible future use.)

      .TXT Log File
      servername
      yyyy/mm/dd
      hh:mm:ss
      event
      result
      connection
      address
      user
      nlm
      [left, 48 bytes]
      [8 bytes]
      [8 bytes]
      [left, 12 bytes]
      [left, 4 bytes - OK or error]
      [5 bytes]
      [left, 21 bytes]
      [left, 47 bytes]
      [left, 12 bytes]

      Notes: All fields are space filled to the specified fixed length (left = left justified within fixed length field). A single space separates each field. "address" field is the IP / IPX address of the connection. "nlm" field only filled for NLM associated connection activity.




Server Module (NLM)
The NodeMaster® Server Module (NLM) loads on the Server and includes customized WEB Server logic which generates JavaScript include files containing data in response to specific requests. The include files are then incorporated into .HTML pages with JavaScript incorporated that display the information and provide a means to perform selected actions based upon allowed requests.

The NLM can also be configured to track and log activity associated with connection allocations, authentications, logins, and logouts, including information on such activity by NLMs and which NLM. The activity can be logged in one or more formats (.TXT = Fixed Text, .CSV = Quote Enclosed Comma Delimited, and .DAT = Binary).

All in One Small NLM!



Client
The NodeMaster ® Client is merely a set of .HTML pages with JavaScript incorporated that display the information output into JavaScript include files by the NLM in response to specific requests and provide a means to perform selected actions based upon allowed requests. The actual Client interface is any JavaScript-enabled browser.



Supported Platforms
The following platforms are supported by the product:

    Server:
    Novell's NetWare v5.x / v6.x / OES (NetWare kernel)
    Protocols: IP
    Client: HTML / JavaScript Based
    Any IP-Based Workstation With A Browser Which Supports JavaScript



Release History
Information about the current release, including release notes and the latest update archive, can be found on the:

Technical Support Page



Revision History

09/17/2007 v1.01 Official Release
08/13/2007 v1.00d Pre-Release: Update (add support for AUTH_GROUP / AUTH_USERS)
07/13/2007 v1.00c Pre-Release: Update (fix connection tracking when logging disabled; enhance .HTM templates)
06/29/2007 v1.00b Pre-Release: Update (fix FILEINFO.HTM & create MANUAL.PDF)
06/11/2007 v1.00a Pre-Release: Initial



Ordering
Information about ordering any of avanti's products can be found on the:

Sales Information Page



Evaluation copy
Fully functional, thirty (30) day evaluation copies of our products can be downloaded from the:

Evaluation Software Page