TePM Controller Release Notes
17 Dec 2010
- 2 -
Outstanding Issues
The current TePM Controller software is 1.3.024. The TePM Controller requires Sun/Oracle Java
Runtime Edition 1.6 update 5 or later (32-bit version only). The TePM Controller may only be
installed on the following operating systems with the Sun/Oracle JRE installed:
•
RedHat Enterprise Linux v5/CentOS 5.x
•
Microsoft Windows XP/Vista
•
Mac OS X Leopard (10.5)/Snow Leopard (10.6)
All Operating Systems
Java Virtual Machine
•
The TePM Controller may periodically generate heap space or random exceptions in the
tepmDebug.log. If these errors start to occur, increase the JVM heap memory
configuration by adding the
-Xms256m -Xmx512m
options to the command line used to
start the TePM Controller.
•
The TePM Controller does not execute correctly on a 64-bit version of the Sun/Oracle
JRE.
SQL Database
•
The TePM Controller should be configured to use Oracle 10g and PostgreSQL 8.x as the
DBMS supporting the Controller as opposed to the in-system HSQL DB. Using the in-
system HSQL DB will cause the host system performance to dramatically degrade after
receipt of about 8,000 to 10,000 call records.
•
If the connection to the SQL database is lost while the Controller is running and a user is
actively logged in, the Controller will ‘hang’ (become unresponsive to mouse movements/
button clicks and keyboard key presses) until connectivity to the database is
reestablished.
TePM Agent/Test Point Management
•
The TePM Controller displays the uptime of the multiservices PIC hosting the TePM
Agent in a Juniper M Series or MX series router as opposed to the router uptime.
VoIP Test Configuration
•
The status of the interface-oriented SIP registration is not displayed in the Controller user
interface. As a result, it is unclear whether the SIP configuration information specified in
the Controller is valid for the interface.
•
The SIP interface-oriented configuration disappears (is reset) after the TePM Agent is
restarted. The SIP configuration specified by the Controller for a TePM Agent is not