Juniper TePM Agent Release note

Brand: Juniper

Model: TePM Agent

Type: Release note

This manual is also suitable for

TEPM AGENT - RELEASE NOTES 17-12-10

Juniper TePM Agent, part of the TePM Controller suite, empowers you to proactively monitor and troubleshoot your network's performance and quality. By simulating real-world traffic and analyzing various metrics, including VoIP quality, latency, and jitter, the TePM Agent provides actionable insights to optimize your network's performance and deliver a seamless user experience.

T e P M A g e n t

R e l e a s e N o t e s

17 Dec 2010

™

- ii -

Proprietary Notice

Information in this document is confidential and proprietary to Telchemy, Incorporated. Access to and use of this information is

limited strictly to licensees of Telchemy, Incorporated and is subject to the terms of a separate and appropriate written license

agreement between the Licensee and Telchemy. The information in this document may be protected by granted or pending patents.

In addition, the information in this document is subject to change without notice and does not represent a commitment on the part of

Telchemy, Incorporated. The software described in this document may be used only in accordance with the terms of the license

agreement. It is against the law to copy the software on any medium except as specifically allowed in the license or non-disclosure

agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical,

including photocopying, recording, or information storage and retrieval systems, for any purpose other than the licensee’s personal

use without express written permission of Telchemy, Incorporated.

All specifics of the product, its use and implementation contained in this document are provided in good faith. However, all

warranties, implied or expressed, including but not limited to implied warranties of merchantability or fitness for a particular purpose

are excluded.

This document is intended solely to assist the Licensee in the use of the Telchemy Licensed Software Product and for no other

purpose. Telchemy shall not be liable, in any way under any theory of law, for any loss or damage of any kind what so ever, arising

from the use of any of the information contained in this manual, or any error or omission in the information, or any incorrect use of

the Software Product.

Telchemy, DVQattest, VQmon, and the Telchemy logo are registered trademarks of Telchemy, Incorporated.

TePM and the VQmon Quality Assured logo are trademarks of Telchemy, Incorporated.

Juniper Networks and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries.

- iii -

Contents

ABOUT THIS DOCUMENT ........................................................................................................................................... 1

NEW FEATURES .......................................................................................................................................................... 1

CHANGES IN DEFAULT BEHAVIOR AND COMMAND SYNTAX ............................................................................... 1

ISSUES BY SUPPORTED JUNOS RELEASE.............................................................................................................. 2

JUNOS RELEASE 10.0R1 – 10.0R3 ............................................................................................................................... 2

General ................................................................................................................................................................................. 2

VoIP ....................................................................................................................................................................................... 2

Ping........................................................................................................................................................................................ 3

Path Diagnostics .................................................................................................................................................................. 3

Trace Route .......................................................................................................................................................................... 3

TWAMP ................................................................................................................................................................................. 3

DHCP .................................................................................................................................................................................... 4

HTTP ..................................................................................................................................................................................... 4

POP3 ..................................................................................................................................................................................... 4

SMTP .................................................................................................................................................................................... 5

ERRATA AND DOCUMENTATION UPDA TE S ............................................................................................................. 5

TePM Agent Release Notes 17 Dec 2010

- iv -

- 1 -

About this Document

This document contains release notes for the Telchemy TePM Agent Release 2.0 for the Juniper

M Series and MX Series Routers. The release notes are structured as follows:

• New Features in TePM Agent Release 2.0

• Changes in default behavior and syntax in TePM Agent Release 2.0

• Issues in TePM Agent Release 2.0 by supported Junos

Release

• Errata and Documentation Updates in TePM Agent Release 2.0

New Features

The TePM Agent Release 2.0 is the first release of the TePM Agent for Junos. The TePM Agent

includes the ability to schedule a variety of test types and analyze the results using both the

Junos command line interface (CLI) and the TePM Controller. The TePM Agent currently

supports the following types of tests that can be executed between two TePM Agents or between

a TePM Agent and a specified network device/server:

• VoIP (SIP signaling)

• Ping (ICMP Echo)

• Path diagnostics

• Trace route

• TWAMP (server/reflector only)

• DNS

• DHCP

• HTTP

• POP3

• SMTP

Changes in Default Behavior and Command

Syntax

The TePM Agent Release 2.0 is the first release of the TePM Agent for Junos. No changes in

default behavior or command system are present.

TePM Agent Release Notes 17 Dec 2010

- 2 -

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

Issues by Supported Junos Release

- 3 -

teardown messages. It is suggested that VoIP test calls typically be configured to 45

seconds or greater in duration in order to minimize the impact of call setup and teardown.

• VoIP/SIP tests initiated from the CLI unexpectedly attempt to place calls through an

outbound proxy and/or use the wrong transport protocol for the call SIP messages. This

is because the Controller can configure an interface-oriented SIP configuration that is

inherited by VoIP tests executed through the interface. As a result, if a test plan defined

in the CLI does not include a definition of the SIP registrar or outbound proxy, those

values are inherited from the Controller-specified SIP configuration.

• VoIP/SIP tests between twoTePM Agents attempt to use TCP as the transport protocol

because the SIP configuration for the associated interfaces is set to ‘Auto’ transport

selection. TCP transport is not working properly for peer-to-peer tests. In order to get

peer-to-peer tests to work properly, it is necessary to set up the SIP interface

configuration in the Controller to ‘UDP only’ for the SIP transport.

• On rare occasions, VoIP tests executed from the Junos CLI appear to ‘hang’ and never

report completion. Simply cancelling/stopping the test instance and re-running the test

corrects the problem when it occurs.

Ping

• Ping tests executed/scheduled from the Junos CLI do not adhere to the requested packet

interval. Ping tests executed/scheduled from the TePM Controller do send the packets at

the appropriate intervals.

• Ping tests do not indicate failure status when no response is received from the ping

target.

Path Diagnostics

• Because path diagnostic tests include transmission of packets to the local host as part of

the normal course of the test, running TePM path diagnostic tests will cause the Junos

Release 10.0 to crash due to a known defect in the Junos Release 10.0 kernel.

Trace Route

• Trace route tests may incorrectly indicate test failure status when the target is the remote

interface of a multi-homed network device.

T W A M P

• TWAMP client is unable to connect to the TWAMP server. The TWAMP server must be

configured with an interface to listen for TWAMP client control connections. In addition,

the TWAMP client IP address MUST be configured in the TWAMP server ‘client list’ filter.

• The TWAMP responder currently inserts the same timestamp for the receive and transmit

times of the reflected packets.

• Issuing the CLI command ‘show services tepm twamp-responder status…’

displays that the interface name for the interface where the TWAMP server is bound is

TePM Agent Release Notes 17 Dec 2010

- 4 -

different from what was configured. The interface name displayed is the interface from

the perspective of the router MS-PIC and not the routing engine.

• Issuing the CLI command ‘show services tepm twamp-responder status…’

displays the interface name ‘unknown’ when the TWAMP server is bound to an IP

address that is not the first IP address configured for the interface/unit.

• Deleting the TWAMP server configuration from the router configuration does not stop the

TWAMP server. The TePM service must either be restarted by taking the host MS-PIC

offline and bringing it back online followed by the CLI command ‘restart tepm-

service’, or rebooting the router.

• On rare occasions, the TWAMP server/responder does not automatically (re-)start after

TePM Agent installation/upgrade or router reboot. Entering ‘configure’ mode and

setting/committing the TWAMP responder interface will cause the TWAMP server to start.

• On rare occasions, the TWAMP server does not properly cleanup Control connections

and hence reports control connections are still active when they have actually been

closed.

• The TWAMP server/responder can only be configured to listen on one (1) interface and

that interface MUST be used for both Control and Test sessions.

DHCP

• DHCP tests MUST be configured to require a unicast response due to a design limitation

within the M and MX series routers that prevents broadcast packets from being sent to

the MS-PIC that is hosting the TePM Agent. DHCP servers that are known to support

generation of correct unicast responses are: MS Windows 2000 Server, MS Windows

2003 Server, MS Windows 2008 Server and most Unix-based DHCP servers.

• Because of the nature of DHCP, only the DHCP Inform method should be used for DHCP

tests initiated from the TePM Agent running in the Juniper M and MX series routers. The

other TePM-supported test method – DHCP Discover – requires addressing facilities not

available to the TePM Agent running on the multi-services PIC.

HTTP

• HTTP tests initiated from the Junos CLI may incorrectly report successful test completion

when the URL requested cannot be located. The TePM Agent classifies an HTTP test as

being successful as long as a TCP connection is established to the host specified in the

URL and a 3XX, 4XX or 5XX error is returned by the HTTP server.

POP3

• POP3 tests initiated from the Junos CLI may incorrectly report successful test completion

when incorrect authentication credentials (username or password) are supplied. The

TePM Agent classifies a POP3 test as being successful as long as a TCP connection is

established to the target server and the server progresses to the authentication stage of

the POP3 protocol.

• The TePM Agent does not support DIGEST-MD5 or CRAM-MD5 authentication (only

clear text authentication is supported) for POP3 tests.

Issues by Supported Junos Release

- 5 -

SMTP

• SMTP tests initiated from the Junos CLI may incorrectly report successful test completion

when the SMTP server generates relay errors. The TePM Agent classifies a SMTP test

as being successful as long as a TCP connection is established to the target server and it

is able to exchange SMTP command primitives with the server.

• SMTP tests initiated from the Junos CLI may incorrectly report successful test completion

when incorrect authentication credentials (username or password) are supplied. The

TePM Agent classifies a SMTP test as being successful as long as a TCP connection is

established to the target server and it is able to exchange SMTP command primitives

with the server.

• The TePM Agent does not support DIGEST-MD5 or CRAM-MD5 authentication (only

none and clear text authentication are supported) for SMTP tests.

Errata and Documentation Updates

There are no errata or documentation updates required for the TePM Agent Release 2.0.

Juniper TePM Agent Release note

Brand: Juniper

Model: TePM Agent

Type: Release note

This manual is also suitable for

TEPM AGENT - RELEASE NOTES 17-12-10

Download PDF

report

Juniper TePM Agent Release note

This manual is also suitable for

Juniper TePM Agent Release note

Related papers

Other documents