Rose Electronics UltraMatrix Remote 2 - Manual (Page 29)

ULTRAMATRIX REMOTE 2 INSTALLATION AND OPERATIONS MANUAL 23
Logging and Status
The logging and status screen provides various details about the user activity on the UltraMatrix Remote 2
Note: The log has a maximum capacity of 1000 event lines. After 1000 entries, the oldest entries are overwritten. If log
data are important to your installation, ensure a regular backup procedure or use the Syslog Server IP Address option
to send log information automatically to another system.
The first three (3) columns show the date the event
occurred.
The next column is the time the event occurred.
The last column describes the type of event with the
users name and the access method.
The “Clear log” tab will clear all entries in the log
The “Refresh” tab will refresh the log list
The “Syslog Server IP Address field is an optional
field where you can enter an IP address to send the
status log.
The “Save” tab will save the log file
The “Cancel” tab will exit the log menu and return to
the main menu
Figure 18. Logging and Status
To copy and paste the log
You can copy the information listed within the log and paste it into another application. While viewing the log screen,
press Ctrl and C, to copy the data into the clipboard. Start a text application (i.e. Word, WordPad, Notepad) press Ctrl
and V, or right mouse click and ‘Paste’.
LDAP Configuration
The LDAP configuration should be performed by the administrator and / or the network administrator. Inputs will vary
depending on the network configuration, LDAP server IP address, port number, and other parameters.
To implement the use of LDAP authentication, check the box “Use LDAP”. This enables the input fields.
Host address The IP address of the LDAP
server to contact for authentication
Host Port The port number that the LDAP
server uses for authentication
Base DN The name to bind against the LDAP
server (Example – “dc=rose,
dc=com”
User Field The LDAP database entry field to
match usernames against. This
field will vary depending on the
specific LDAP database being
used.
Typical values are ‘uid’ or ‘cn’.
Anonymous
bind If checked, bind requests are
anonymous (suitable for Linux
LDAP implementations. If
unchecked, the bind requests are
sent with the user name and
password (suitable for active
directory)
Figure 19. LDAP Configuration