Table of Contents
Advertisement
TePM Agent Release Notes
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.
- 4 -
17 Dec 2010
Advertisement
Table of Contents
