White Paper

ManualsBrandsHP ManualsSoftwareHP MFP Digital Sending Software 5.0

Page 1 of 7 white paper



Introduction

DSS keeps addresses in the DSS database in logical address books. These addresses can be

accessed by devices that are bound to DSS for addressing with email or FAX jobs. In DSS 5

FutureSmart devices access DSS address information differently than pre-FutureSmart devices, and

differently than FutureSmart devices do in the 4.25 version of DSS. This paper will describe the

addressing architecture and also give troubleshooting tips for common problems.

Architecture

FutureSmart devices directly access addressing information from the DSS database. Pre-FutureSmart

devices request addresses from the DSS service, and the DSS service in turn gets the addresses

from the database and passes them back to the requesting device.

Default and External DSS Databases

The DSS database can be the default database which is installed when DSS is installed. This

database is installed on the DSS server and is accessed by FutureSmart devices using TCP port

5213. Port 5213 must be open bi-directionally on the DSS server for FutureSmart addressing to

work.

The DSS database can also be an SQL Server database that is not installed when DSS is installed.

DSS can be configured to use an external database either during DSS installation, or after

installation using a utility provided for this purpose. When a database other than the default DSS

database is used it is referred to as an “external” database. An external database can exist on the

DSS server itself, but is most commonly a database on a separate server. An external database can

be configured by the DSS admin to use whatever port they choose. Also, the database server can

be specified using either an IP address or a host name. For FutureSmart addressing to work when

an external database is in use the database server must allow bi-directional access on the

configured port to the FS devices. Also, the networking configuration on each FutureSmart device

must be properly configured such that the device can find the database server. The usually involves

making sure the DNS servers and suffixes are properly configured.

When a FutureSmart device is added to DSS the database connection string is pushed from DSS to

the device for use when getting address information.

White Paper

DSS 5 – FutureSmart Device

Addressing Architecture and

Troubleshooting

Date Written:

5/14/2014

Summary of content (7 pages)

PAGE 1
White Paper DSS 5 – FutureSmart Device Addressing Architecture and Troubleshooting  Date Written: 5/14/2014  Introduction DSS keeps addresses in the DSS database in logical address books. These addresses can be accessed by devices that are bound to DSS for addressing with email or FAX jobs. In DSS 5 FutureSmart devices access DSS address information differently than pre-FutureSmart devices, and differently than FutureSmart devices do in the 4.25 version of DSS.
PAGE 2
DSS Server Port 5213 Default DSS Database Port 1783 DSS Service FutureSmart Printer Pre-FutureSmart Printer Figure 1: Device Access of DSS address books - Default DSS database DSS Server DSS Service Admin Configured Port External DSS Database Admin configured port Port 1783 Database Server Pre-FutureSmart Printer FutureSmart Printer Figure 2: Device Access of DSS address books - External DSS database Page 2 of 7 white paper
PAGE 3
Address Books and Database Structure Addresses are kept in the DSS database in logical address books. See the admin guide for a complete description of the address books. Most of the address books, excluding the LDAP replicated address book, are visible and editable from the DSS Address Book Manager (ABM). The ABM is accessed by pressing the Address Book Manager button at the bottom of the Addressing tab in the DSS Configuration Utility.
PAGE 4
DSS instead of getting them directly from the LDAP database. To provide this functionality DSS has the ability to replicate addresses from an LDAP database into the DSS database. This can help reduce the load on a busy LDAP server which can result from many devices directly accessing it for address information during busy times. By replicating the addresses from the LDAP database into the DSS database the devices can then get these addresses from DSS rather than from the LDAP server.
PAGE 5
Figure 5 – View of the External Database Configuration Tool 2- The FutureSmart device does not get replicated LDAP addresses, but does get other addresses. In this case it may be that the LDAP replication is not working and there are no LDAP addresses in the database. a. The first step is to make sure the LDAP replication is working from the test that can be run from the UI. The test is found on the Addressing tab of the Configuration Utility, and it is step 4 in the process of configuring LDAP replication.
PAGE 6
b. Be sure a synch has been done. Look at the UI for step 5 of the configuration to see when the last replication was done. If there is no time given for the last replication then hit the “Sync Now” button. Even if a replication had been previously done it is possible the “Clear LDAP Cache” button may have been hit by mistake so “Synch Now” should still be run. c. Even when the test for LDAP retrieval passes, there can occasionally be problems when a full replication is done.
PAGE 7
Page 7 of 7 white paper