JDS Uniphase T-BERD MTS 8000, T-BERD 6000A, T-BERD 5800 Getting Started Manual

21165803 rev 002

Remote Operation Getting Started Guide

This guide describes remote operation and control of a Transport Module, Multi-Service
Application Module (MSAM), or T-BERD/MTS 5800 using SCPI commands.

SCPI command syntax and format requirements are presente d alo ng w ith instr uction s on
how to establish a connection to a module and initiate example applications. A list of
commands and queries that apply to all applications concludes this section as a refere nce
for basic remote control applications.

Controlled modules may be a part of an MTS-8000 or MTS 6000A Test Platform. As these
platforms are physically diff erent, only those phys ical features that apply directly to remo te
operations will be discussed when necessary.

The sections contained in this chapter are as follows:
– “About the T-BERD/MTS 8000, 6000A, and 5800” on p age2

– “Remote control flow” on page 4
– “Command syntax and format requirements” on page 4
– “Getting the module port number” on page 6
– “Getting the remote control port number” on page 7
– “Working with applications” on page 11
– “Using setups, actions, and results” on page 14
– “Rebooting an instrument” on page 19
– “Example remote control procedur e s” on page 19
– “Demo Remote Control Scripts” on page25
– “SCPI command reference” on page 26

Transport Module, DMC, MSAM, and 5800 Remote Operation 1

Remote Operation Getting Started Guide

About the T-BERD/MTS 8000, 6000A, and 5800

About the T-BERD/MTS 8000, 6000A, and 5800

Before beginning a remote session, you should be familiar with the products and modules,
found in the T-BERD

Transport Module, and MSAM Getting Started Guide and T-BERD/MTS 5800 Getting
Started Manual.

The following terms have a specific meaning when referring to the T-BERD/MTS 8000 or
6000A:

– 10/100/1000 Ethernet — Used to represent 10/100/1000 Mbps Ethernet. The

connector panel also uses 10/100/1000M to identify the connector used for 10/100/
1000 Mbps Ethernet testing.

– 1GigE — Used to represent 1 Gigabit Ethernet. The Transport Module connector

panel also uses GigE to identify the optical connector used for 1 Gigabit Ethernet
testing.

– 10GigE — Used to represent 10 Gigabit Ethernet. The Transport Module connector

panel also uses 10GE and 10G to identify the optical connectors used for
10 Gigabit Ethernet LAN and WAN testing.

–Action — Refers to an item that triggers some change to the test interface, such as

inserting an alarm or enabling the laser. In the user interface, these are located in the
Actions toolbar at the bottom of the main results screen.

– Application module — Used to refer to the component that provides test functionality

to the assembled instrument. This manual supports two application modules: the
Transport Module, and the MSAM.

– Assembly — Used to refer to a complete set of components assembled as an instru-

ment and used for testing. This manual supports three assemblies: The Transport
Module assembly, consisting of an T-BERD ⁄ MTS 8000 base unit and T ransport
Module, the MSAM assembly, consisting of a MSAM, Physical Interface Modules
(PIMs), and a T-BERD ⁄ MTS 6000A base unit, and a DMC assembly, consisting of
up to two MSAMs, up to four PIMs, a Dual Module Carrier (DMC), and a
T-BERD ⁄ MTS 8000 base unit.

– Base unit — The unit which connects to the application module and power adapter,

providing the user interface and a variety of connectivity and work flow tools. If
optioned to do so, the base unit also allows you to measure emitted power, received
power, and optical link loss on fiber optic networks.

– Battery Module — The module connected to the back of the T-BERD / MTS 8000

base unit, which supplies power whenever it is not provided using the power adapter.

– Component— Used to refer to an individual hardware component which is connected

to the other components to build a test instrument (assembly). This manual supports
the following components: the Transport Module, the MSAM, and the DMC. The base
units are documented in separate manuals.

–DMC — Dual Module Carrier. The DMC is a two slot chassis which you ca n connect to

the T-BERD / MTS 8000 base unit to test using up to two MSAM application modules
and four Physical Interface Modules (PIMs).

– FC — Used to represent Fibre Channel on the Transport Module connector panel and

the Transport Mod ule and M SAM use r i nterfa c e to iden tify the optica l conn ectors used
for Fibre Channel testing.

⁄

MTS 8000 and T-BERD⁄MTS 6000A Dual Module Carrier,

2 Transport Module, DMC, MSAM, and 5800 Remote Operation

Remote Operation Getting Started Guide

About the T-BERD/MTS 8000, 6000A, and 5800

– JDSU Ethernet test set — A test set marketed by JDSU and designed to transmit an

Acterna Test Packet (ATP) payload. These packets carry a time stamp used to calcu­late a variety of test results. The FST-2802 TestPad, the SmartClass Ethernet tester,
the HST with an Ethernet SIM, the T-BERD/MTS 8000 Transport Module, and the
T-BERD/MTS 6000A MSAM can all be configured to transmit and analyze ATP
payloads, and can be used in end-to-end and loopback configurations during testing.

– MSAM Multiple Services Application Module — Referred to generically as “the

instrument” when inserted in the T-BERD / MTS 6000A base unit or the DMC with a

PIM. The MSAM provides testing functionality for the base unit.
– MTS 8000 and MTS 6000A — See T-BERD/MTS 8000 and T-BERT 6000A.
– OC-n — Used to refer to each of the optical SONET rates supported by the Transport

Module or MSAM (OC-3, OC-12, OC-48, and OC-192), where “n” represents the

user-selected line rate.
– OTN — Optical Transport Network.
– OTU1 — Optical Transport Unit 1. A 2.7G OTN sign al d esigned to ca rr y a SONET OC-

48 or SDH STM-16 client signal. OTU1 is used on the connector panel and the

Transport Module and MSAM user interfaces to identify the connectors and applica-

tions used for 2.7G OTN testing.
– OTU2 — Optical Transport Unit 2. A 10.7G, 11.05G, or 11.1G OTN signal designed to

carry SONET OC-192, SDH STM-64, or 10GigE Ethernet WAN and LAN client signals.

OTU2 is used on the <product name> connector panel and the Transport Module and

MSAM user interfaces to identify the connectors and applications used for 10.7G,

11.05G, or 11.1G OTN te sting.

– PIM — The physical interface module (PIM) inserted into one of up to two ports

provided on the MSAM chassis. PIMs supply the physical connectors (interfaces)

required to connect the MSAM to the circuit under test. A variety of cables, SFPs, and

XFPs are offered as options, and can used to connect the PIMs to the circuit.
–Result — Refers to a measurement made by the test ap plication. In the user interface,

these are displayed in the result windows and in the software LED panel on the main

Results screan.
– Setup — Refers to a setting of a test application that is usually changable by the user.

In the user interface, they are located on the Setup screen and on the main Result

screen in the horizontal toolbars.
– SFP — Small form-factor pluggable module. Used on the connector panel and

throughout this manual to represent pluggable optical modules.
–Slice — Used as a generic term for an applicaiton module or battery module. Typical

use is referring to the Transport Module, as the “BERT slice”. After assembling a T-

BERD/MTS 8000 base unit to a battery module and then to the Transport Module, the

instrument resembles a sandwich; thus, the indivicual components are slices.
– STM-n — Used to refer to each of the optical SDH rates supported by the Transport

Module or MSAM (STM-1, STM-4, STM-16, and STM-64), where “n” represents the

user-selected line rate.
– STS-1 — Used to refer to the electrical equivalent of OC-1 (51.84 Mbps) supported by

the Transport Module or MSAM.
– STM-1e — Used to refer to the electrical equivalent of STM-1 (155.52 Mbps)

supported by the Transport Module or MSAM.

Transport Module, DMC, MSAM, and 5800 Remote Operation 3

Remote Operation Getting Started Guide

Remote control flow

– T-BERD ⁄ MTS 8000 and T-BERD ⁄ MTS 6000A — The family of products, typically

a combination of a base unit, a battery module, and one or more application modules.
The Dual Module Carrier (DMC) can be used on the T-BERD / MTS 8000 platform to
test using two MSAMs.

The products are branded T-BERD in North American and branded MTS in Europe,
and are interchangeably referred to as the T-BERD 8000, MTS 8000, MTS-6000,
MTS5800 and Media Test Set 6000 throughout supporting documentation.

– Transport Module — Referred to generically as “the instrument” when connected to

the T-BERD / MTS 8000 base unit. The T ranspor t Module provides testin g functionality
for the base unit.

– XFP — 10 Gigabit Small Form Factor Pluggable optical transceiver. A variety of

optional XFPs are available for testing 10 Gigabit fibre circuits.

Remote control flow

When running a remote control session, the basic flow is as follows:

1 Obtain the remote control port number
2 Start remote control
3 Interacting with the applications

a query for running applications
b launching an application
c using setup, action, and results
d restarting a test

e configuring a timed test
4 Exiting the application(s)
5 Leaving remote control

Command syntax and format requirements

Before starting the remote session you sould become familiar with the syntax and format
requirements.

Command case-

sensitivity

SCPI command headers are not case sensitive , so both commands below are correct and
return the Signal Present test result.

:SENSE:DATA? CSTatus:PHYSical:SIGNal

:sense:data? CSTatus:PHYSical:SIGNal

Result names are not case sensitive, so both commands below return the Signal Present
test result.

:SENSE:DATA? CSTatus:PHYSical:SIGNal

4 Transport Module, DMC, MSAM, and 5800 Remote Operation

:SENSE:DATA? cstatus:physical:signal

Setup and action values are case-sensitive.

:SENSe:PAYLoad:BERT:PATTern ALL_ONESCorrect
:SENSe:PAYLoad:BERT:PATTern all_onesIncorrect

Remote Operation Getting Started Guide

Command syntax and format requirements

Sockets and

messages

Issuing multiple

commands

Serial command

processing

Short-form v. Long-

form commands

All remote control communications are socket-based TCP/IP. Any message passed via
remote control must be terminated with a newline character ("\n") as shown (or ENTER in
direct entry mode).

:INITiate\n

Without the following \n, a message may be interpreted incorrectly or cause an error condi­tion.

You can issue multiple commands on a single line by separating each of the commands
using a semicolon. The following examples show correct and incorrect presentation of the
multiple commands.

:INITiate; :SYSTem:ERRor:NEXT?\nCorrect
:INITiate :SYSTem:ERRor:NEXT?\nIncorrect

The remote control system processes commands sequentially in the order they are
received. It does not process multiple commands simultaneously. If a command is sent
while another command is still being processed, the second command will not be
processed until the first command has been fully executed.

Commands may be abbreviated using the short form (the capital lette rs in the comma nd).
Each word in the command may be either the long or short-form.

If long-form is used, the entire word must be specified; "partial" long -form is not recognized.
The following examples show the complete long-fo rm ver sio n fo llow ed by var iou s, sh or t-

form versions of the same command. The final example shows an exam ple of "partial" long­form that is not acceptable.

:SENSe:DATA? CSTatus:PHYSical:SIGNal Correct
:SENSe:DATA? CST:PHYS:SIGNCorrect
:SENS:DATA? CSTatus:PHYS:SIGNalCorrect
:SENS:DATA? CST:PHYS:SIGNCorrect
:SENS:DATA? CST:PHYS:SIGNaIncorrect

Transport Module, DMC, MSAM, and 5800 Remote Operation 5

Remote Operation Getting Started Guide

Getting the module port number

Getting the module port number

Starting remote

operation

Obtaining the module

port number

The first step is to start remote operation

1 Open a TCP/IP socket connection to the unit on port 8000.
2 Start remote operation.

*REM

IMPORTANT:

The *REM command must always be the first command sent after opening a
socket (to port 8000, the module port, or the RC port). On the ANT pla tforms
this was not necessary - they allowed you to connect, acce ss ap plic at ion s,
disconnect, then reconnect and continue without having to send *REM
again; on the MTS platforms, it is required.

Before issuing any SCPI commands, a socket connection to the module must be estab­lished.

Module identification and location

In order to establish a connection, the module must be identified and located.
Since multiple layers (slices) of transport modules (MTS-8000) and installation locations

(sides) for Multi-Service Application Modules (MSAM) are possible, the exact location of
the module to which a connection is being made must be verified.

There are two arguments that are required in the following commands and queries that
establish the exact physical location of the module being used in the test. These are indi­cated as <side>
value as follows:

<side>

–PWRS - Power Side - specify this location when connecting to an MSAM connected to

an MTS-6000A

OR

on the right side (viewed from front of base unit) of MTS-8000 dual carrier (same side

as power connector).
– OPPS - Opposite Side - specify this location when connecting to an MSAM connected

to the left side (viewed from front of base unit) of MTS-8000 dual carrier (far side from

power connector).
– BOTH - specify this location when connecting to full-width Transport Module (on MTS-

8000).

and <slice>. These are required arguments and must be filled with a

NOTE

The <side> parameter was added to the ":SYST:FUNC" commands in ver­sion 8.0 of the MTS-8000 BERT software and version 3.0 on the MTS-6000.
For previous versions, this parameter must be omitted.

6 Transport Module, DMC, MSAM, and 5800 Remote Operation

Remote Operation Getting Started Guide

Getting the remote control port number

<slice>

– SLIC1 - specify this location when connecting to an MTS-6000A MSAM

OR
to the transport module connected directly to the MTS-8000.

– SLIC2, SLIC3 - specify this location when connecting to the second or third transport

module (counting from the front) on an MTS-8000.

NOTE

For MTS-6000A, <side> will always be PWRS and <slice> will always be
SLIC1.

Verify the location of the module to which a connection is being made:

Example procedure

MOD:FUNC:LIST?

replacing <side> and <slice> as detailed in “Module identification and location” on

page 6.

If the module is located where queried, the system will respond with “BERT”.

1 Verify whether the module is powered.

MOD:FUNC:SEL? <side>,<slice>,"BERT"
example:
MOD:FUNC:SEL? PWRS,SLIC1,"BERT"
The module will return “OFF” or “ON”.

2 If the module state response was OFF, turn ON the module:

MOD:FUNC:SEL <side>,<slice>,"BERT",ON

3 Query the module’s port number.

MOD:FUNC:PORT? <side>,<slice>,"BERT"
The module will return its port number.If the module is in a ready state, the response to

the port query will be the port number, for example “8002”.
If the port is not in a ready state, the response will be -1 .
This port number will be needed in the next step.

<side>,<slice>

Getting the remote control port number

1 Open a TCP/IP socket to the module port obtained in “Module identification and loca-

tion” on page 6.

2 Enable remote operations on the module:

*REM

3 Verify the BERT module is ready

:SYST:FUNC:READY? <side>,<slice>,"BERT"

Returns 1 if the BERT module is in a ready state (i.e. po were d o n and finishe d b ooting
up), 0 otherwise.

Transport Module, DMC, MSAM, and 5800 Remote Operation 7

Remote Operation Getting Started Guide

Getting the remote control port number

4 Enable the remote control socket and return its port number

:SYST:FUNC:PORT? <side>,<slice>,"BERT"

Returns this module's remote control port number. If the module is not in a ready state,

the response will be -1.

Remote modes

Default Mode

GUI Mode

Remote operations are often conducted when the re is no physical access to th e base unit
where applications can be directly implemented using the Graphical User Interface (GUI).
Alternate situations can exist where remote operations need to be monitored by a techni­cian at the base unit or even supplemented with input from the base unit.

The default remote operational mode disables the Graphical User Interface (GUI) on the
base unit. This mode is activated by the implementation of the following command with no
optional values:

*REM

In this mode, the GUI is disabled and a message is displayed indicating the unit is under
remote control. At any time the GUI is enabled or disabled, all currently running applicaitons
will be shut down.

Alternatively, remote control may be used without deactivating the GUI. This mode can be
used to debug remote control tests and to verify that commands have the expected
behavior; the default mode is recommended for routine automated tasks. To activate GUI
mode, two optional parameters may be a dded to the *REM command on the remote con trol
port: <GUI-mode> and <access-mode>.

<GUI-mode> parameter

The <GUI-mode> parameter has three variables that can be defined:
– HIDDEN - when specified, the GUI is disabled (default if not specified).

– VISIBLE - when specified, the GUI is enabled.
– CURRENT - when specified, whatever is currently set will continue to be applied to the

new application or command.

<access-mode> parameter

The <access-mode> parameter has three variables that can be defined.
– READ_ONLY - when specified, a GUI user may navigate the UI but not change any

settings (default, if not specified).
– FULL - when specified, a GUI user may change settings.
– CURRENT - when specified, whatever is currently set will continue to be applied to the

new application or command.
These modes may be activated by the implementation of the REM command and speci-

fying the alternate parameters as follows:

*REM <GUI-mode> <access-mode>

8 Transport Module, DMC, MSAM, and 5800 Remote Operation