Table of Contents
Advertisement
TePM Agent Release Notes
Issues by Supported Junos Release
The current TePM Agent software bundle is 2.0.103. The TePM Agent currently supports the
following Junos Releases:
•
Junos Release 10.0R1-10.0R3.
Junos Release 10.0R1 – 10.0R3
General
•
The TePM Agent requires a multiservices PIC (MS-100, MS-400, or MS-DPC) in order to
be installed and perform tests.
•
When the TePM Agent bundle is installed, the 'no-validate' option should be included
in the installation request, such as:
router> request system software add telchemy-tepm-bundle... no-validate
If the 'no-validate' option is not included, the installation will fail on routers with
redundant routing engine hardware configured for graceful failover.
•
The TePM Agent requires the TePM Controller assign a valid license before any tests
can be executed from the CLI or Controller.
•
Running TePM tests that have the same origination and target interface on a single
router (i.e. loopback tests) causes the Junos Release 10.0 kernel to crash due to a
known defect in the Junos Release 10.0 kernel. TePM tests must only be executed
between two different TePM agent instances.
•
The CLI command 'restart tepm-service' does not restart the entire TePM Agent.
In order to restart the TePM Agent, first bring the MS-PIC hosting TePM offline and wait
10 seconds. Then, bring the MS-PIC back online and issue the CLI command 'restart
tepm-service'. The TePM Agent will be back online after 2-5 minutes.
•
Test start times are delayed by up to 2 minutes from their scheduled start time. When a
DNS server is configured for the router or a specific test plan/instance specifies a DNS
server to use for the test and that DNS server cannot be contacted, the test start time
reported is after the DNS lookups timeout. As a result, the reported test start times may
be up to 2 minutes after the test started to perform the DNS request(s).
•
Any test that requires DNS name resolution of the test target must use a DNS server that
can be contacted from the multi-services PIC (e.g. the DNS cannot only be connected to
the OOB management network interface of the router).
VoIP
•
The TePM Agent is limited to managing a maximum of 400 simultaneous VoIP sessions
when running on the MS-DPC and 200 simultaneous VoIP sessions when running on the
MS-100 multiservices PIC.
•
When the TePM Agent starts/ends more than 10 simultaneous call sessions coincident
with each other (around the same time), the call quality reports may reflect jitter levels
greater than 10ms as a result of the MS-PIC being busy processing the call setup and
- 2 -
17 Dec 2010
Advertisement
Table of Contents
