User guide

Note: Alcatel-Lucent 5620 SAM-O is an open interface on the
Alcatel-Lucent 5620 SAM. An OSS client application can access information
through the Alcatel-Lucent 5620 SAM-O.
Figure 1 shows that in the event-driven inventory, DataStage processes JMS
create, delete, and update messages.
DataStage resynchronizes the element names that are based on IP address
and subchannel affiliations from the Tivoli Netcool Performance Manager
database on startup. For newly encountered elements, a hash of the
element name IP address is used to assign it to a subchannel. It is not
necessary for DataStage to write the element to the Tivoli Netcool
Performance Manager database. The UBAs generate the elements and other
inventory. By default, the hash function is used and applied to the entire
set of accounting or metric subchannels.
However, it is possible through configuration to restrict the assigned
subchannels to a subset of the accounting or metric subchannels. This is
provided in the event one subchannel starts to approach capacity. In
addition, the user might explicitly override the subchannel affiliation for
individual IP addresses. Intended to all for the case that a network has a
handful of large devices that they want to ensure are evenly distributed
across the available subchannels. Metrics and inventory are merged
together and appended to a file destined for a subchannel with the IP
address that determines the destination subchannel. After the data for a
period is complete, the file is cut and staged atomically for UBA
acquisition.
When the DataStage is started, it establishes the SAM metric data by using
the new LogToFile feature. Availability of metric file is notified to the
DataStage through JMS connection. DataStage then retrieves the file.
DataStage uses SFTP connections for multiple downloads rather than
establish new connections for every download.
DataStage also establishes a JMS connection with SAM to receive inventory
updates, file available messages and control messages. The JMS process is
running continuously. The Monitor stage in job periodically checks and
restarts the JMS daemon if the daemon is not running. JMS daemon buffers
messages and passes the messages to DataStage.
DataStage also processes the full inventory dump by using the existing
FindToFile SOAP requests. Full dump on inventory is run on need basis.
There is no automated full dump on startup. Warnings can be found in the
logs that show missed JMS messages. These warnings can be monitored to
initiate a full dump if required.
Finally, DataStage requires that all inventory update messages have
information to help determine the IP address. DataStage requires the IP
address to determine to which subchannel an inventory update must be
routed.
4 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack Installation and User Guide