Getting Started With Spirent TestCenter
Getting Started With Spirent TestCenter
TM
Spirent TestCenter
Hardware, Software, License Set Up,
and Upgrades
March 2020
Copyright
© 2020 Spirent Communications, Inc. All Rights Reserved.
All of the company names and/or brand names and/or product names referred to in this document, in particular, the
name “Spirent” and its logo device, are either registered trademarks or trademarks of Spirent plc and its subsidiaries,
pending registration in accordance with relevant national laws. All other registered trademarks or trademarks are the
property of their respective owners. The information contained in this document is subject to change without notice
and does not represent a commitment on the part of Spirent Communications. The information in this document is
believed to be accurate and reliable, however, Spirent Communications assumes no responsibility or liability for any
errors or inaccuracies that may appear in the document.
Limited Warranty
Spirent Communications, Inc. (“Spirent”) warrants that its Products will conform to the description on the face of
order, that it will convey good title thereto, and that the Product will be delivered free from any lawful security interest
or other lien or encumbrance.
Spirent further warrants to Customer that hardware which it supplies and the tangible media on which it supplies
software will be free from significant defects in materials and workmanship for a period of twelve (12) months, except
as otherwise noted, from the date of delivery (the “Hardware Warranty Period”), under normal use and conditions.
To the extent the Product is or contains software (“Software”), Spirent also warrants that, if properly used by Customer
in accordance with the Software License Agreement, the Software which it supplies will operate in material
conformity with the specifications supplied by Spirent for such Software for a period of ninety (90) days from the date
of delivery (the “Software Warranty Period”). The “Product Warranty Period” shall mean the Hardware Warranty
Period or the Software Warranty Period, as applicable. Spirent does not warrant that the functions contained in the
Software will meet a specific requirement or that the operation will be uninterrupted or error free. Spirent shall have no
warranty obligations whatsoever with respect to any Software which has been modified in any manner by Customer or
any third party.
Defective Products and Software under warranty shall be, at Spirent's discretion, repaired or replaced or a credit issued
to Customer's account for an amount equal to the price paid for such Product provided that: (a) such Product is
returned to Spirent after first obtaining a return authorization number and shipping instructions, freight prepaid, to
Spirent's location in the United States; (b) Customer provides a written explanation of the defect or Software failure
claimed by Customer; and (c) the claimed defect actually exists and was not caused by neglect, accident, misuse,
improper installation, improper repair, fire, flood, lightning, power surges, earthquake, or alteration. Spirent will ship
repaired Products to Customer, freight prepaid, based on reasonable best efforts after the receipt of defective Products.
Except as otherwise stated, any claim on account of defective materials or for any other cause whatsoever will
conclusively be deemed waived by Customer unless written notice thereof is given to Spirent within the Warranty
Period. Spirent reserves the right to change the warranty and service policy set forth above at any time, after
reasonable notice and without liability to Customer.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, ALL IMPLIED WARRANTIES, INCLUDING BUT
NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS
FOR A PARTICULAR PURPOSE, ARE HEREBY EXCLUDED, AND THE LIABILITY OF SPIRENT, IF ANY,
FOR DAMAGE RELATING TO ANY ALLEGEDLY DEFECTIVE PRODUCT SHALL BE LIMITED TO THE
ACTUAL PRICE PAID BY THE CUSTOMER FOR SUCH PRODUCT. THE PROVISIONS SET FORTH ABOVE
STATE SPIRENT'S ENTIRE RESPONSIBILITY AND CUSTOMER'S SOLE AND EXCLUSIVE REMEDY WITH
RESPECT TO ANY BREACH OF ANY WARRANTY.
Contents
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
User Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Hardware Handling/Cleaning Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
How to Contact Us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About Chassis Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
To Identify Chassis Controller Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About the Virtual Spirent LabServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Summary of Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Procedure 1: Check System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Procedure 2: Verify Contents of Shipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Checking a Chassis Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Checking a Spirent C50 Appliance Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Procedure 3: Install Spirent TestCenter Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing Spirent TestCenter [Microsoft Windows] . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing Spirent TestCenter [Linux] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Procedure 4: Chassis and Appliance Firmware Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Procedure 5: Perform Cable Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Procedure 6: Install the Ferrite Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Procedure 7: Connect Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
AC Power Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
DC Power Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Procedure 8: Set the Chassis IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Setting the IP Address using the SPT-N4U or SPT-N11U Front Panel Touchscreen . . . 44
Setting the IP Address using the SPT-N4U, SPT-N11U, or SPT-N12U Direct Console Con-
nection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Setting the IP Address using SSH (all chassis). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Setting the IP Address using Web Client (SPT-N4U, SPT-N11U, or SPT-N12U) . . . . . 47
Setting the SPT-C50 Addressing mode, IP Address, Netmask and Gateway . . . . . . . . . 48
Setting the Netmask and Gateway Values (all chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Procedure 9: Confirm the Ethernet Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Procedure 10: Using the Authenticate Mode (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Procedure 11: Obtain Your License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Procedure 12: Connect to a DUT/SUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Procedure 13: Configure and Run Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
• User Documentation . . . . 6
• How to Contact Us . . . . 9
Introduction
Getting Started with Spirent TestCenter provides hardware set up, software installation,
firmware support, licensing, and software upgrade and downgrade instructions.
New Spirent chassis and modules are shipped with current firmware. Firmware upgrade or
downgrade instructions for installed equipment are described in Appendix B, “Upgrade/
Downgrade Procedures.”
User Documentation
Documentation is available in PDF format and as online Help files:
• Documents delivered in PDF format support product installation, provide important
system reference information, and support Spirent TestCenter Automation users.
These manuals are available in the Documentation installer (.exe) for each release, on
the Downloads page of the Customer Service Center (https://support.spirent.com).
They are also included on the Spirent TestCenter Application DVD and in the
Knowledge Base on the Customer Service Center site (CSC). The “DOC” ID numbers
are provided below with each document title.
• Help files, included within Spirent TestCenter applications, provide reference and
context sensitive user support. Launch a Help file by pressing F1 in an open
application or by clicking the Help button in the menu bar or a dialog box.
Tip: For your convenience, the current Help file is also available as part of the CSC
Knowledge Base (DOC10335). This stand-alone Help file is fully functional. Use the
Table of Contents to navigate through the file, or click the Search tab and enter a
search string to find the information you need.
Release Notes
Release notes are available as a Related Resource on the Customer Service Center site on
the Downloads page with each software download. You can also refer to the Spirent
TestCenter Release Notes Index on the Knowledge Base - search on DOC10921.
Environmental Considerations
This label is on all Spirent-provided electrical and electronic products that are sold and
shipped (see Figure 1).
This label indicates that the product contains material that presents an environmental
concern. Spirent encourages users of Spirent-provided electrical and electronic equipment
to not dispose of the labeled products in waste collection units where the waste is destined
for landfills. Electrical and electronic equipment should be collected separately and
recycled, reused, and processed for recovery and waste treatment in accordance with your
local, regional, and federal laws. If you have any questions regarding this labeling, please
contact your Spirent Communications representative.
How to Contact Us
To obtain technical support for any Spirent Communications product, please contact our
Customer Service Center (CSC) using any of the following methods:
Americas
E-mail: [email protected]
Web: https://support.spirent.com
Toll Free: +1 800-SPIRENT (+1 800-774-7368) (North America)
Phone: +1 818-676-2616
Hours: Monday through Friday, 05:00 to 17:00, Pacific Time
Asia Pacific
E-mail: [email protected]
Web: https://support.spirent.com
Phone: +86 (400) 810-9529 (toll-free mainland China only)
Phone: +86 (10) 8233 0033 (China)
Hours: Monday through Friday, 09:00 to 18:00, Beijing Time
Information about Spirent Communications and its products and services can be found on
the main company website at https://www.spirent.com.
Company Address
Spirent Communications, Inc.
27349 Agoura Road
Calabasas, CA 91301
USA
Warning: You must use the power cord included with your chassis.
Note: Your Spirent chassis, modules, and appliances are shipped with current operating
system firmware.
Tip: Additional system requirements may be included in the release notes provided for
the extended applications that run on Spirent TestCenter.
Note: For packaging, installation, and setup information about the SPT-C1 or the
PX3/DX3-QSFP-DD-8 appliances, refer to the installation documentation that is
included in your shipment. See “Quick Start Guides and Installation Instructions” on
page 6.
• One Cable Kit, which includes:
• One (1) or two (2) power cords with the SPT-N4U, and up to seven (7) with the
SPT-N11U/SPT-N12U chassis, either domestic or international.
(see “Power supply connector” on page 32).
• One white 10 ft. (3.048 m.), crossover Ethernet LAN cable (RJ-45); used to
connect the Spirent chassis directly to a PC.
• One blue 10 ft. (3.048 m.), straight-through Ethernet LAN cable (RJ-45); used to
connect the Spirent chassis to a hub or LAN.
• One purple 3 ft. (.9144 m.), straight-through Ethernet LAN cable (RJ-45); used to
connect one Spirent chassis to another Spirent chassis.
• One Ferrite block; connects onto the Ethernet cable that attaches the Spirent
chassis to your network or a hub. The ferrite block reduces potential EMI
interference.
• DVD containing Spirent TestCenter application software (with online Help files),
documentation files in PDF format, and Spirent TestCenter License Entitlement ID
Certificate (shipped with Spirent TestCenter orders).
Notes: • A 32-bit and 64-bit Spirent TestCenter application of the same version cannot
coexist. Running a 32-bit (Windows) installer when the same version of a
64-bit (Windows) Spirent TestCenter application is installed on the host PC,
will result in an error message similar to this:
• The 32-bit and 64-bit applications share the same user data path. As is
typical, the installer does not delete the files in user data path.
• Spirent TestCenter 32-bit and 64-bit applications of different versions can run
on the same machine.
Navigate to operating system-specific installation instructions using these links:
• All customers: “Installing Spirent TestCenter [Microsoft Windows]” on page 18
• Linux customers: “Installing Spirent TestCenter [Linux]” on page 20
Tip: Some extended applications require steps not included in this document. Check the
relevant release notes for additional installation information.
1 Load the DVD and then click Spirent TestCenter for Windows to launch the instal-
lation wizard.
2 Follow the wizard instructions until you reach the Setup Type screen, and then choose
an installation option:
• Follow on-screen prompts to run the recommended Complete installation.
• Use Custom to change the Tcl installer option:
a Click Custom and then Next.
b Deselect the Tcl [x.x.x] (configured for Spirent TestCenter Automation)
installer.
c Select the Update/Configure existing Tcl for Spirent TestCenter
Automation installer.
Note: Automation customers: If you do not use the Tcl [x.x.xx] installer, (configured
for Spirent TestCenter Automation) you must manually configure your automation
environment. Setup instructions for each environment are in readme format, located
in the <Spirent_Install_Dir>/API folder with sub-directories matching the language
name.
For example:
/home/user/Spirent_TestCenter_[x.xx]/Spirent_TestCenter_Application_Linux/API/
Tcl
3 Click Next to complete your installation.
4 Click Finish, when installation is complete, to return to the main DVD menu.
Tip: Click the relevant links on the DVD Contents screen to download and install
extended Spirent TestCenter applications.
When you have finished installing applications, you are ready to download Spirent
TestCenter firmware files.
To disable Telemetry, add this text to the end of the command above:
/DISABLE_TELEMETRY
You can repeat this process to select and download extended Spirent TestCenter
applications.
3 Use the standard procedure (for your workstation) to copy the installer appropriate for
your system and the documentation tarball to your workstation.
4 Run the shell-based installer as root. For example, use the following for 64-bit OS:
./install_Spirent_TestCenter_Auto_Linux64_[x.xx].sh
Note: To perform a silent install, these are the options that can be set:
Follow these instructions to use commands to copy and install Spirent TestCenter files on
your workstation.
./install_Spirent_TestCenter_Auto_Linux64_[x.xx].sh
Note: To perform a silent install, these are the options that can be set:
6 Use tar to extract the documentation from the tarball. For example, use the following
command for a Linux file:
tar -xzvf Spirent_TestCenter_Docs_Linux_Unix[x.xx].tar.gz
7 Set up Tcl [x.x.xx], or other automation environment, for use with Spirent TestCenter.
Setup instructions for each environment are in readme format, located in the
<Spirent_Install_Dir>/API folder with sub-directories matching the language name.
For example:
/home/user/Spirent_TestCenter_[x.xx]/Spirent_TestCenter_Application_Linux/API/
Tcl
Note: Refer to the Spirent TestCenter Extreme Automation™ Toolkit Release Notes for
detailed installation instructions. Go to the Customer Service Center (CSC), and search
using the document title or DOC10751.
./install_Spirent_TestCenter_Auto_Linux64_[x.xx].sh
Note: To perform a silent install, these are the options that can be set:
11 Use tar to extract the documentation from the tarball. For example, use the following
command for a Linux file:
tar -xzvf Spirent_TestCenter_Docs_Linux_Unix[x.xx].tar.gz
12 Log off the website.
13 Set up Tcl [x.x.xx], or other automation environment, for use with Spirent TestCenter.
Setup instructions for each environment are in readme format, located in the
<Spirent_Install_Dir>/API folder with sub-directories matching the language name.
For example:
/home/user/Spirent_TestCenter_[x.xx] Spirent_TestCenter_Application_Linux/API/
Tcl
To see the available Spirent TestCenter versions using the command line interface:
1 SSH to the device using the admin username. Refer to page 46 for login instructions.
2 Use the applicable command
• Type version to identify the active Spirent TestCenter version.
• Type standby_version to see the standby version. This shows an example.
To switch between two installed versions using the command line interface:
1 SSH to the device using the admin username. Refer to page 46 for login instructions.
2 Type help to view the list of options.
3 Select switch_version with yes as an option to switch to the standby version.
Note: A reboot is required to switch versions. Select yes if you want to reboot and use the
standby version. If you select no, the switch to the standby version will take effect with
the next reboot.
To see the available Spirent TestCenter versions using the command line interface:
1 SSH to the device using the admin username. Refer to page 46 for login instructions.
2 Use the applicable command
• Type version to identify the active Spirent TestCenter version.
• Type standby_version to see the standby version. This shows an example.
To switch between two installed versions using the command line interface:
1 SSH to the device using the admin username. Refer to page 46 for login instructions.
2 Type help to view the list of options.
3 Select switch_version with yes as an option to switch to the standby version.
Note: A reboot is required to switch versions. Select yes if you want to reboot and use the
standby version. If you select no, the switch to the standby version will take effect with
the next reboot.
The AutoFallBack behavior is true for a reboot initiated from the Equipment View.
Notifications will display in Log window and a warning message will display in the lower
right pane as shown in the screen capture.
The admin prompt shows Active Version as shown in the screen capture below.
Refer to the Spirent C1 Installation Instructions for complete install, set up, and usage
information for the SPT-C1.
To see the available Spirent TestCenter versions using the command line interface:
Notes: • For complete installation and setup information for the SPT-C1 or the PX3/
DX3-QSFP-DD-8 appliances, refer to the installation documentation that is
included in your appliance shipment.
• Refer to FAQ18073 for information about External Time Reference (ETR)
methods you can use to sync multiple remote chassis. Go to the Customer
Service Center (CSC) (https://support.spirent.com) and type FAQ18073 in
the Search box. Press Enter.
Removable
Hard Drive
DVI-I Connector External Time Reference Tray
Connectors
Back Panel USB Ports LEDs for
Chassis
Connection
Status
Ethernet Multiple
Admin Chassis
Port Connection
Ports
Power Cord
Connectors
Figure 1-6. SPT-C50-S2-RX Front Panel Connectors for Hardware Rev 80-002535
Note: The hardware “Rev” number for your SPT-C50 model is on the label on the bottom
of the appliance. See Figure 1-7 on page 32.
SPT-C50 Label for Hardware Rev 80-002394 SPT-C50 Label for Hardware Rev 80-002311
Table 1-1 describes the chassis back-panel connectors, their functions, and the cable used
for each connector.
Power supply connector Power outlet Power cord(s). On the SPT-N4U, SPT-
N11U, or SPT-N12U chassis, each power
supply must be connected to a 15A circuit
that is not shared with other equipment.
WARNING: You must use the power
cords provided with your chassis. Each
power cord must be plugged into wall
outlets that are controlled by separate 15A
circuit breakers.
ETHERNET INTERFACE (RJ-45)—To Your hub or LAN Blue 10 ft. (3.048 m.), straight-through
connect a chassis to a network. Ethernet LAN cable (RJ-45)
EXTERNAL TIME REFERENCE 10MHZ External time External time reference cable
(BNC) reference hardware
EXTERNAL TIME REFERENCE 1 PPS External time External time reference cable
(BNC) reference hardware
EXTERNAL TIME REFERENCE SERIAL External time External time reference cable
DCE (DB9) reference hardware
SPT SYNC OUT and SPT SYNC IN The SPT SYNC IN Purple 3 ft. (.9144 m.), straight-through
(RJ-45) or SPT SYNC OUT Ethernet LAN cable (RJ-45)
(RJ-45) port of Note: If you are connecting multiple
another Spirent chassis, attach the SPT SYNC OUT
chassis. connector to the SPT SYNC IN
connection on the next slave chassis.
DVI Connectors Video monitor DVI cable (not provided), or serial cable
(SPT-N4U, SPT-N11U, SPT-N12U only) via DVI to serial Adapter (provided)
Important: • The serial port on the Spirent chassis is RS-232 DCE and has default
settings of 9600 baud with 8 data bits, 1 start bit, 1 stop bit, no parity, and
no flow control. The PC used for the serial port connection should be
configured with these same settings.
Table 1-2 describes the SPT-C50 appliance connectors, their functions, and the cable used
for each connector.
USB Ports USB keyboard, mouse, or other User supplied USB keyboard, mouse,
peripherals or other peripheral cable
Ethernet Admin Port Your hub or LAN Blue 10 ft. (3.048 m.), straight-
through Ethernet LAN cable (RJ-45)
EXTERNAL TIME External time reference hardware External time reference cable
REFERENCE 10MHZ (BNC)
EXTERNAL TIME External time reference hardware External time reference cable
REFERENCE 1 PPS (BNC)
EXTERNAL TIME External time reference hardware External time reference cable
REFERENCE SERIAL DCE
(DB9)
SPT SYNC OUT and SPT The SPT SYNC IN or SPT SYNC Purple 3ft. (.9144 m), straight-
SYNC IN (RJ-45) OUT (RJ-45) port of another Spirent through Ethernet LAN cable (RJ-45)
chassis/appliance
Note: If you are connecting multiple
chassis/appliance, attach the SPT
SYNC OUT connector to the SPT
SYNC IN connection on the next
slave chassis/appliance.
Warning: Before you begin using your chassis, make sure that you have attached the
ferrite block to the Ethernet cable using the procedure below.
1 Remove the ferrite block and the Ethernet cable from the Cable Kit package.
2 Release the built-in clip on the side of the ferrite block and open it so that the center of
the ferrite block faces up. Place the Ethernet cable in the open ferrite block
(see Figure 1-9 on page 36, #1).
3 Clamp the ferrite block around the Ethernet cable within a few inches of the end of the
connector, making sure that the built-in clip snaps together (see Figure 1-9 on
page 36, #2).
4 Connect the Ethernet cable to the chassis (see Figure 1-9 on page 36, #3).
1 2
Note:
In this example, the ferrite block is placed near the end
of the Ethernet cable that connects to the chassis.
Important: On the SPT-N4U, SPT-N11U, SPT-N12U, and SPT-C50, each power supply
must be connected to a 15A circuit that is not shared with other equipment.
AC Power Operation
The SPT-N4U, SPT-N11U, SPT-N12U, and SPT-C50 do not have an AC master power
switch. Remove or attach the power cord to control AC power.
Warning: To power down the unit, use the (DC) POWER button on the front of the
chassis. Under normal circumstances, do not remove the AC power cords for this purpose.
Doing so may lead to equipment failure.
The (DC) POWER button on the front of the chassis performs an orderly (firmware-
controlled) shutdown of the chassis systems. The removal the AC power cords should
only be used if all power needs to be removed from the chassis (e.g., during maintenance).
In such situations, the AC power cords should only be removed after DC power has been
disabled by using the (DC) POWER button. The DC power is disabled when the main
cooling fans are off, and the Power LED on the front of the chassis is off. This shut down
requires approximately 45 seconds.
DC Power Operation
The DC power button (labeled POWER) is located on the front panel of the chassis or
appliance (refer to the appropriate figures in this section). The POWER button controls the
DC power from the unit’s internal AC/DC power supply. Information about how the
button operates begins on page 42.
Figure 1-13. Power Connector and Fans on the SPT-C50 C50-S2-RX Rev 80-002535
(DC)
POWER
Button
DC Power Button
Warning: The status of the POWER LED does not necessarily mean that AC power to
the chassis is on or off. For this reason, be sure to check the status of AC and DC power
before performing maintenance on the chassis. Remove or attach the power cord to control
AC power. Refer to the warning on page 37 under AC Power Operation.
Refer to Hot Swap in the Spirent Hardware Reference for information about hot swapping
test modules with the chassis AC and DC power turned on. See “Spirent Hardware
Reference (DOC10031)” on page 7.
You can also use this connection to configure the chassis netmask and gateway values.
Refer to “Setting the Netmask and Gateway Values (all chassis)” on page 49.
SPT-C50
For the SPT-C50, set a unique IP address by using either of these methods:
• Attach a USB keyboard and VGA monitor to the appliance
• Use a communication program to SSH (secure shell) over the Ethernet administration
port to the SPT-C50 default IP address
See “Setting the SPT-C50 Addressing mode, IP Address, Netmask and Gateway”.
Setting the IP Address using the SPT-N4U or SPT-N11U Front Panel Touchscreen
The built-in touch screen interface allows reconfiguring of the chassis IP address settings.
1 Use your finger to press the Configure button on the Welcome screen.
2 Press on the IP Address text box to bring up a keyboard for entering the address.
3 Enter the address and press Go.
4 Repeat Step 2 to enter the IP Gateway Address and IP Netmask, if necessary.
5 Press the Submit button.
The settings will be applied and the controller will automatically reboot.
Setting the IP Address using the SPT-N4U, SPT-N11U, or SPT-N12U Direct Console
Connection
To set the IP address using the SPT-N4U, SPT-N11U, or SPT-N12U direct console
connection:
1 Connect a video monitor and USB keyboard and mouse to the chassis.
The chassis prompt appears:
login:
Password:
2 Access the chassis by logging in. Log in as admin to change chassis parameters (IP
address, gateway, netmask, etc.).
a Type admin <enter>.
b Type spt_admin <enter>
3 Enter a chassis command.
• To view the chassis IP address, type the command ipaddress <no parameter>
• To set the chassis IP address, type the command ipaddress <new ip address>
When log in is complete, you will see the command prompt admin>
Note: At this time, you should change the netmask and default gateway if your controller
PC and chassis will be on different subnets. Refer to “Setting the Netmask and Gateway
Values (all chassis)” on page 49.
4 Apply and save the settings.
Enter the Spirent TestCenter command activate.
The settings will be applied and the controller will automatically reboot.
Note: It may take up to several minutes for the new IP address to take effect after the
activate command is issued.
Note: At this time you should change the netmask and default gateway if your controller
PC and chassis will be on different subnets. Refer to “Setting the Netmask and Gateway
Values (all chassis)” on page 49.
Note: It may take up to several minutes for the new IP address to take effect after the
activate command is issued.
1 Open a web client on the controller PC and enter the default IP address in the address
bar (http://192.168.0.100) and press Enter on the keyboard.
This launches the Welcome screen.
2 Click on the link titled Reconfigure the Chassis.
This launches the Chassis Configuration screen.
3 Click the Configure button.
4 Click in the IP Address text box to enter the address and then press Enter.
5 Repeat Step 4 for the IP Gateway Address and IP Netmask, if necessary.
6 Click the Submit button.
The settings will be applied and the controller will automatically reboot.
Note: It may take up to several minutes for the new IP address to take effect.
Tip: Refer to the Chassis Commands section in the Spirent Hardware Reference for
information about Spirent chassis commands. This resource is available on the Spirent
Customer Service website. See “Spirent Hardware Reference (DOC10031)” on page 7.
You can now use the following commands to set the addressing mode and/or set the IP
address, netmask and gateway. When you have made your changes, you must activate the
new settings and reboot the appliance:
Note: You must manually set the IP address, netmask, and gateway if you use the static
setting.
Note: If you are connected using SSH, you will lose connectivity when you use the
activate command. You must log back in to the appliance using the new IP address.
When the SPT-C50 appliance restores after the power cycle, it is ready for use with the
Spirent TestCenter GUI, or an automation script (if supported in your current release).
Command Description
Note: This feature is available on the SPT-N12U, SPT-N11U, SPT-N4U, SPT-C1, SPT-
C50, SPT-C50-S2-RX, and the PX3/DX3-QSFP-DD-8 appliances.
• Refer to the Spirent C1 Installation Instructions for complete install, set up, and usage
information for the SPT-C1.
• Refer to the Spirent PX3/DX3-QSFP-DD-8 Installation Guide or complete install, set
up, and usage information for these appliances.
Note: The Black Bold text is user input; Blue Bold text is console output.
1 Connect to chassis via console (keyboard and display connected)
2 Login as user admin (password: spt_admin)
admin>
To turn authenticate mode on
admin> authenticate on
authenticate mode is currently disabled
Note: Each activation screen in the process provides detailed step-by-step instructions.
The instructions in this section are an overview of the license activation process that you
will follow from the Customer Service Center home page.
4 Enter your License Entitlement ID (this field is case-sensitive). Include any hyphens.
5 Click Login.
The STEP 1 window opens. This includes two options:
• Activate licenses
• Manage licenses
6 Select the license(s) you wish to activate for a specific Host ID and click Activate.
9 Follow the instructions in the STEP 4 window to specify the method by which you
want your license file to be delivered to your computer.
• Click Save to File to browse the directory structure on your PC. After selecting a
location, rename the file according to your preference, using an .lic extension.
• Click Email to send the license key text to your email address. You can then copy
this text into a license file on a directory on your PC.
Note: You can rename the license file using Microsoft file naming parameters. The
file name should contain the chassis controller serial number for easy identification.
This provides an easy way to manage licenses and to inventory the components of
your system.
10 Click Complete.
11 On the License Fulfillment page, Click Manage Licenses to see the parameters of the
license that you generated.
12 If there are multiple licenses, follow the steps on the screen to consolidate them.
You can load your license key file onto your Spirent chassis controller. This will enable
you to use your new Spirent hardware and test applications.
Tip: If you try to run a test before you disconnect and reconnect, Spirent TestCenter will
generate an error log message.
1 Connect to the chassis with test module on which you want to install the license.
2 Select Tools > Licensing Management in the main window menu.
The Licensing Management window opens.
3 Go to the Test Module tab and make sure View By: Speed is selected.
4 Select the Test Module on which you want to install the license.
5 Click Install to display the Install License File dialog box.
6 Browse to the folder that contains the license file (*.json) you want to install.
7 Select the license file and click the Open button.
This initiates license installation.
8 Disconnect from the chassis, and then reconnect to the chassis.
This action is required to reload the license into the Spirent TestCenter application
cache on your computer.
To connect your Spirent chassis either to your PC or to the network to which your PC is
connected, use the chassis’ Ethernet port labeled ETHERNET INTERFACE (RJ-45)
located on the chassis’ back panel.
Connect the chassis to the desired device(s) or network to be tested via either of the
methods shown in Figure 1-18 or Figure 1-19.
Connect to the Ethernet
port on the chassis back
DUT/SUT
Figure 1-18. Connecting the PC Directly to the Chassis and to the DUT/SUT
WAN/LAN
DUT/SUT
Figure 1-19. Connecting the PC via a WAN/LAN to the Chassis and to the DUT/SUT
Important: You must position and install the provided ferrite block onto the Ethernet
cable (at the chassis end) that attaches the chassis to your network. The ferrite block
reduces potential EMI interference. Refer to “Procedure 6: Install the Ferrite Block” on
page 35 for details on connecting the ferrite block.
Spirent test modules connect to a DUT/SUT via the connectors on each unit. To connect a
test module to a DUT/SUT, you must determine the type of ports (connectors) on your test
module and on the DUT/SUT.
1 Determine the type of connectors used on your DUT/SUT, and then refer to Connec-
tors and Cables in the online Spirent Hardware Reference for pin-out information on
cables used to connect the test module to the DUT. See “Spirent Hardware Reference
(DOC10031)” on page 7.
2 Match the pin-outs of the cables described in the Spirent Hardware Reference with the
requirements of the connectors on your DUT/SUT and select the correct cable.
Note: Most test setups require a minimum of two port connections to the DUT/SUT:
one port to transmit traffic, and one port to receive traffic. Many tests are also set up
as partial or full mesh, uni-directional or bi-directional, full or half duplex, single-to-
many ports, or many-to-many ports. For sample test scenarios, refer to the online Help
for each test application.
3 Connect the test module to the DUT/SUT, and ensure that the chassis and DUT/SUT
are on a stable surface and that proper ESD guidelines are followed.
Your equipment is ready to use for testing.
Important: • All customers: Before you begin testing, check your environment and
make sure that you follow the EMI guidelines as described in
Appendix C, “ESD Requirements.” When the testing environment is
properly prepared, you can use the appropriate software for the tests you
want to perform. Failure to comply with these guidelines may produce
invalid test results.
• vLS customers: Proceed to Appendix A, “Install and Configure Spirent
Virtual LabServer.” Complete the vLS installation and configuration
tasks before you set up and run tests.
Note: Spirent TestCenter automation user documentation is available in PDF and HTML
formats on the installation DVD and on the Downloads page of the Spirent Customer
Service Center (CSC) website.
Refer to “User Documentation” on page 6.
This appendix provides installation and configuration instructions for the Spirent Virtual
LabServer (vLS).
• Configure System . . . . 70
• Shell Access . . . . 72
Note: The file names provided in this section are examples of the file formats. The release
version number may be different in your product.
You can choose either the OVA or QCOW2 VM image file to create the vLS, depending
on the hypervisor in your virtualization environment. Users with older hypervisors may
use the OVA image with the -SHA1 name, if the system does not support an SHA256
checksum. The two OVA files are otherwise identical.
Users with older QEMU hypervisors should use the QCOW2 image with the -compat file
name; this file can be read by any QEMU version since 0.10. The QCOW2 image without
the -compat file name contains image format extensions that can only be understood by
QEMU version 1.1 and newer. The two QCOW2 files are otherwise identical.
Choose the Docker container image if you want to run Virtual LabServer natively on a
bare metal Linux server without a hypervisor. Checksum files (<filename>.sha256 or
<filename>.sha1) are available for the container and VM images to verify the integrity of
the downloaded files.
When using either of the VM images, the vLS virtual machine should be configured to use
bridged networking, so it will be connected directly to the physical network and have its
own external IP address, reachable from outside the host. Figure A-1 on page 63 shows
the vLS in a bridged network.
When connecting to the Virtual LabServer in the Spirent TestCenter Session Manager, the
Server Name to select in the Choose Server popup depends on how the Virtual LabServer
is deployed (VM or container):
• Use the VM host IP address or hostname, if you are running either of the VM images.
• Use the Linux server host IP address or hostname, if you are running the Docker
container image on a bare metal Linux server.
Prior to starting the VM, set the configuration settings to the number of CPUs, amount of
memory, and hard disk capacity to the values listed in the recommended system
requirements (page 62), as well as configuring for bridged networking.
Timing for the VM should be provided by the Network Time Protocol (NTP), not the
VMware clock synchronization software. The latter is turned off by disabling time sync
under VMware Tools features. The Synchronize guest time with host box should be
unchecked as shown in Figure A-3.
Before starting the VM, increase the size of the VM image file system to 100 GB, so that
the recommended 100 GB of disk space will be accessible. Execute the following
command to increase the file system by 90 GB (added to the initial size of 10 GB):
sudo qemu-img resize <file path of qcow2 image> +90G
On the hypervisor, launch the VM with the QCOW2 image and the recommended 32 GB
of memory (-m 32768) by executing the following:
sudo kvm -k en-us -m 32768M -drive file=<file path of qcow2
image>,cache=none,if=virtio,discard=unmap -serial telnet:<host
IP>:<available port>,server,nowait -monitor
telnet:127.0.0.1:<available port> -net
nic,vlan=1,model=virtio,name=admin0,macaddr=<VM eth0 mac
address>,netdev=nic-0 -netdev tap,id=nic-0,ifname=<tap
name>,script=no,downscript=no,vhost=on -cpu host -smp 4 -
nographic &
Upon startup, a script in the VM will automatically perform the remaining steps to
configure the virtual machine so that it will have access to 100 GB of disk space.
When Docker is installed, use these steps to start the Virtual LabServer container:
Note: The execution of Docker commands can only be done by user root or by a user
who is a member of the docker group.
2 Perform the following command to reserve the ports Virtual LabServer uses to com-
municate with Spirent TestCenter sessions:
sudo sh -c 'echo "40000-46000" >
/proc/sys/net/ipv4/ip_local_reserved_ports'
To completely remove the container and/or the Virtual LabServer image from the
host:
Note: All admin configuration can be performed from the admin console or telnet
port. Optionally, SSH can be used; however, it is disabled by default. To enable SSH,
select [1] Configure System followed by [7] SSH. At the Enable SSH prompt, enter
“y”, then select Save changes [10].
The IP address should be displayed at the login prompt (Note: If the telnet session
only responds with “Escape character is ‘^]”, press Enter one or more times). If the
address is displayed, use the escape sequence, and then quit out of telnet.
telnet <host IP> <telnet port>
Trying 10.28.226.20...
Connected to 10.28.226.20.
Escape character is '^]'.
Started labserver
IP Addr: 10.28.239.108
MAC Addr: 00:a1:f5:3b:03:00
rune-00a1f53b0300 login:
If the IP is not displayed, proceed with the login at the prompt with user ID admin
and password spirent. When presented with the admin menu, select [6] Shell Access,
and then execute the ifconfig command to get the IP address of the eth0 interface.
rune-00a1f53b0300 login: admin
Password:
Linux rune-00a1f53b0300 3.16.0-4-amd64 #1 SMP Debian
3.16.39-1+deb8u1 (2017-02-22) x86_64
sudo /bin/bash
ifconfig eth0
2 To configure the license server host, select [2] Configure Container, followed by [4]
Set License Server. At the Enter license server host: prompt, enter the license
server host name, followed by [6] Apply change and start new container.
Note: The license server is only required if you are using a virtual chassis. It is
optional for physical chassis.
Configure System
Navigate to the first item of the top-level menu, Configure System, to see the following:
>>>>> System configuration <<<<<
[1] Networking
[2] Hostname
[3] Admin Password
[4] DNS
[5] NTP
[6] Proxy
[7] SSH
[8] SSL
[9] Exit without saving
If any configuration changes are made, an additional option Save changes will appear on
this menu. The changes must be saved, or they will be lost upon exiting the shell.
• To enable/disable DHCP, select [1] Networking and enter “y” or “n” at the Use
DHCP (y/n): prompt. If disabling, follow the subsequent prompts to set the IP
address, netmask, gateway, and any optional static routes, to configure a static IP for
the VM.
• To set the VM hostname, select [2] Hostname and enter the new name at the Current
hostname: prompt.
Note: The container must be restarted for the LabServer to display the new name in
the Host field of the Session Manager.
From the top level of the administration menu, select [2] Configure Container, [3]
Reset container, and [6] Apply change and start new container. After the restart,
newly created sessions will reflect the new hostname.
• To change the admin user’s password, select [3] Admin Password and enter the new
password at the Password: prompt.
• To configure DNS, select [4] DNS and enter nameserver IP addresses and search
domains, as necessary.
• To enable/disable NTP, select [5] NTP and enter “y” or “n” at the Enable NTP?
prompt. If enabling, follow the subsequent prompts to add the NTP server(s).
• To enable/disable HTTP/HTTPS proxy, select [6] Proxy and enter “y” or “n” at the
Enable HTTP/HTTPS Proxy? Prompt, and enter the HTTP Proxy and HTTPS
Proxy addresses.
• To enable/disable SSH, select [7] SSH and enter “y” or “n” at the Enable SSH?
prompt.
• To configure SSL, select [8] SSL. If your webapp.key and webapp.crt files have been
uploaded to /etc/ssl/private, enter “y” at the Have you uploaded the private-key and
certificate? prompt. If the files have not been uploaded, enter “n” and select [9] Exit
without saving; upload the files, and execute the SSL menu item again.
For changes to any of the settings in the menu to take effect, you must select [10] Save
changes before exiting. The latter item will be added to the menu selections, if any
changes are made while running the admin shell.
Configure Container
Navigate to the second item on the top menu, Configure Container, to see the following:
[1] Load image from registry is used to start the container with an image from a Docker
registry.
[2] Load image from file is used to start the container with an image copied to the /tmp
directory on the VM.
[3] Reset container stops and removes the current running container and starts a new
container instance.
[4] Set environment variables is used to add or update environment variables inside the
running container.
[5] Set License Server sets an environment variable that tells the LabServer the address
of license server.
If any changes are made in items 1 through 5, then item [7] Apply change and start new
container will appear. You must select this item for the changes to take effect.
Other than [5] Set License Server, under normal circumstances, the items at this level will
rarely be used.
Shell Access
The main menu also provides the [6] Shell Access option that allows the admin user to
access a bash shell on the VM. Privileged (root) access is available via the sudo command,
if needed. This allows administrators to perform any necessary operations that are not
available from the admin menu.
Once in the bash shell, you can gain access into the LabServer container itself by
executing the following:
docker exec -ti $(docker ps -q -f ancestor=$(docker images -q
registry.oriontest.net/labserver)) /bin/bash
Other Options
The other options available from the main, System Information, System Status, and View
Journal allow the admin user to inspect various types of information describing the VM
and its current state.
In this appendix...
• Introduction . . . . 74
Introduction
This appendix introduces Spirent TestCenter software installation procedures. An
installation may be either an upgrade or a downgrade.
Spirent TestCenter installation files can be downloaded from the installation DVD
(included with chassis shipments), or from the Spirent Communications support website.
If you do not already have Spirent hardware, software, and firmware installed refer to
“Getting Started” on page 11.
Note: For Spirent TestCenter Extreme Automation™ Toolkit customers: Use the
installation instructions in this document to install the Windows and Linux versions of the
Spirent TestCenter Application.
Refer to the Spirent TestCenter Extreme Automation™ Toolkit Release Notes for
additional Toolkit installation and setup instructions. Go to the Customer Service Center
(CSC), and search using the document title or DOC10751.
If you are upgrading from a Spirent TestCenter DVD or from the Spirent Customer
Service Center (CSC):
1 Log in to your Spirent CSC account at https://support.spirent.com.
2 On the home page, click the Downloads icon on the left panel.
3 On the Downloads page, under Release Type, select General Release from the drop-
down menu.
4 Under Product Line, select Spirent TestCenter.
5 At the top of the page, use the Filter by release drop-down list to choose the Spirent
TestCenter upgrade release you want to install.
6 On the filtered results page, select the Spirent TestCenter Application option for
your operating system.
The release date for the application is shown to the left of the title.
• Valid:
SUPPORT_ENTITLEMENT Version = or > Release Date (month, year only).
Proceed with the Spirent TestCenter upgrade.
• Expired:
SUPPORT_ENTITLEMENT Version < Release Date (month, year only).
Tip: If your Support Entitlement has expired, you do not have a Support Entitlement,
or you have any questions about Spirent TestCenter licensing, contact
[email protected] for assistance.
7 Repeat these steps as needed to look up the Support Entitlement date associated with
each chassis.
8 Proceed to file download and installation instructions when all Support Entitlements
have been verified.
Note: For Spirent TestCenter Automation customers. Customers have the choice of
downloading “Tcl configured for Spirent TestCenter” from the Spirent Customer Service
website (https://support.spirent.com), updating/configuring an existing Tcl installation, or
manually setting up an existing Tcl installation to work with Spirent TestCenter.
To Install Software
Follow these instructions to run installers for Spirent TestCenter applications,
documentation, and Tcl options.
1 Verify that your Support Entitlement is valid (see “Upgrade steps for the Windows
platform” on page 76).
2 Load the DVD and then click Spirent TestCenter for Windows to launch the instal-
lation wizard.
3 Follow the wizard instructions until you reach the Setup Type screen.
4 Do one of the following:
• Follow on-screen prompts to run the recommended Complete installation.
• Use Custom to change the Tcl installer option:
a Click Custom and then Next.
b De-select the Tcl [x.x.x] (configured for Spirent TestCenter Automation)
installer.
c Select the Update/Configure existing Tcl for Spirent TestCenter Automa-
tion installer.
Note: Automation customers: If you do not use the Tcl [x.x.xx] (configured for Spirent
TestCenter Automation) installer, you must manually configure your automation
environment. Setup instructions for each environment are in readme format, located in the
<Spirent_Install_Dir>/API folder with sub-directories matching the language name.
For example:
/home/user/Spirent_TestCenter_[x.xx]/Spirent_TestCenter_Application_Linux/API/Tcl
Tip: Click the relevant links on the DVD Contents screen to download and install
extended Spirent TestCenter applications.
When you have finished installing applications, you are ready to download Spirent
TestCenter firmware files.
1 Create, or verify that there already is, a Firmware folder in the appropriate Spirent
TestCenter directory on your computer.
2 Click Browse this DVD to view the DVD folder tree.
3 Open the Spirent TestCenter Firmware folder.
4 Copy the appropriate firmware volume (Controller 2 or Controller 3) to the Firmware
folder on your computer.
When the application software is installed, and the appropriate firmware files have been
copied to your computer, you are ready to upgrade chassis and test module firmware.
Refer to the online Help file in the Spirent TestCenter Application or the Spirent
TestCenter Conformance Application for firmware installation instructions.
1 Verify that your Support Entitlement is valid (see “Upgrade steps for the Windows
platform” on page 76).
2 Navigate to https://support.spirent.com and log in.
First time website users, register for a login user ID and password.
3 Click the Downloads icon in the left panel menu.
4 From the Filter options, select General Release as the Release Type, and select
Spirent TestCenter from the Product Line list.
5 In the Filter by Release drop-down list, select the version to download.
6 Click the Windows Spirent TestCenter Application link associated with the version
you want to install.
Note: Automation customers: If you do not use the Tcl [x.x.xx] (configured for Spirent
TestCenter Automation) installer, you must manually configure your automation
environment. Setup instructions for each environment are in readme format, located in the
<Spirent_Install_Dir>/API folder with sub-directories matching the language name.
For example:
/home/user/Spirent_TestCenter_[x.xx]/Spirent_TestCenter_Application_Linux/API/Tcl
1 Create, or verify that there already is, a Firmware folder in the appropriate Spirent
TestCenter directory on your computer.
2 Locate and click on the Spirent TestCenter Firmware link for the version you need.
The download page opens.
3 Click the Download button.
The File Download dialog opens.
4 Save and then Extract the appropriate files to the Firmware folder in your Spirent
TestCenter directory.
Click Yes when you are prompted to overwrite the .map and .pdf files
5 Repeat these steps, if there is more than one firmware volume file for the Spirent
TestCenter version you need.
When the application software is installed, and the appropriate firmware files have been
extracted, you are ready to upgrade chassis and test module firmware.
Refer to the online Help file in the Spirent TestCenter Application or the Spirent
TestCenter Conformance Application for firmware installation instructions.
Note: The Spirent TestCenter Application Windows version is required for chassis and
test module firmware management. Linux customers must install the Spirent TestCenter
Application on a computer running a supported version of Windows, and then install the
appropriate Linux version of the application on a workstation.
Note: For Spirent TestCenter Automation customers. Customers have the choice of
downloading “Tcl configured for Spirent TestCenter” from the Spirent Customer Service
website (https://support.spirent.com), updating/configuring an existing Tcl installation, or
manually setting up an existing Tcl installation to work with Spirent TestCenter.
Appropriate licensing is required to use any Spirent TestCenter application for testing. If
you have questions about Spirent TestCenter licenses or about Support Entitlement,
contact [email protected]. To find out how to verify Support Entitlement status, see
“To Verify Support Entitlement” on page 75.
Note: Automation customers: If you do not use the Tcl [x.x.xx] (configured for
Spirent TestCenter Automation) installer, you must manually configure your
7 Set up Tcl [x.x.xx], Perl, C++, Java, Ruby, Python, C#, or REST for use with Spirent
TestCenter.
Note: Automation customers: If you do not use the Tcl [x.x.xx] (configured for
Spirent TestCenter Automation) installer, you must manually configure your
automation environment. Setup instructions for each environment are in readme
format, located in the <Spirent_Install_Dir>/API folder with sub-directories matching
the language name.
For example:
/home/user/Spirent_TestCenter_[x.xx]/Spirent_TestCenter_Application_Linux/API/
Tcl
Tip: Spirent TestCenter Extreme Automation Toolkit users: Refer to the Spirent
TestCenter Extreme Automation Toolkit Release Notes for installation instructions. Go to
the Spirent Knowledge Base and search using the document title or DOC10751.
Note: If you do not use the Tcl [x.x.xx] (configured for Spirent TestCenter Automation)
installer, you must manually configure your automation environment. Setup instructions
for each environment are in readme format, located in the <Spirent_Install_Dir>/API
folder with sub-directories matching the language name. For example:
/home/user/Spirent_TestCenter_[x.xx]/Spirent_TestCenter_Application_Linux/API/Tcl
Note: The vLS server upgrade file must be stored in the STC Server file in your Spirent
TestCenter Application [X.xx] directory.
Spirent Communications manufactures and sells products that require industry standard
precautions to protect against damage from electrostatic discharge (ESD). This document
explains the proper process for handling and storing electrostatic discharge sensitive
(ESDS) devices, assemblies, and equipment.
The requirements presented in this document comply with the EIA Standard, ANSI/ESD
S20.20-1999: Development of an Electrostatic Discharge Control Program, and apply to
anyone who handles equipment that is sensitive to electrostatic discharge. Such equipment
includes, but it not limited to:
• All electronic assemblies manufactured by Spirent Communications
• Discrete and integrated circuit semiconductors
• Hybrid microcircuits
• Thin film passive devices
• Memory modules
Caution: Failure to comply with the requirements explained in this document poses risks
! to the performance of ESDS devices, as well as to your investment in the equipment.
• Any racks or carts used for the temporary storage or transport of ESDS equipment
must be grounded either by drag chains or through direct connection to earth ground.
Loose parts that are not protected by ESD-safe packaging must not be transported on
carts.
Workstation Preparation
The ideal setup for working with ESDS equipment is a workstation designed specifically
for that purpose. Figure C-1 illustrates an ESD protected workstation. Please follow the
requirements listed below to prepare a proper ESD protected workstation.
• The ESD Ground must be the equipment earth ground. Equipment earth ground is the
electrical ground (green) wire at the receptacles.
• An ESD protected workstation consists of a table or workbench with a static
dissipative surface or mat that is connected to earth ground. A resistor in the
grounding wire is optional, providing that surface resistance to ground is ≥ 105 to
≤ 109 Ω.
• The workstation must provide for the connection of a wrist strap. The wrist strap must
contain a current limiting resistor with a value from ≥ 250K Ω to ≤ 10M Ω.
• ESD protective flooring or floor mats are required when floor-grounding devices (foot
straps/footwear) are used or when it is necessary to move in between ESD protected
workstations when handling ESDS equipment.
ESD protective
Optional resistor surface or mat
Wrist strap
ESD protective
floor mat (optional)
Note: The equipment needed for proper grounding is available in ESD service kits from
various suppliers. Refer to the Buyer’s Guide on the ESDA website (http://www.esda.org).
Spirent Communications manufactures and sells products that contain fiber optic
components, including fiber optic transmitters and receivers. These components are
extremely susceptible to contamination by particles of dirt or dust, which can obstruct the
optic path and cause performance degradation. To ensure optimum product performance,
it is important that all optics and connector ferrules are kept clean.
This document provides guidelines for maintaining clean fiber optic components. Spirent
Communications recommends that these guidelines be followed closely.
Caution: • Failure to comply with the guidelines explained in this document poses
! risks to the performance of fiber optic-based devices, as well as to your
investment in the equipment.
• Whenever you handle a piece of equipment that contains fiber optic
components, you must be properly grounded to avoid harming the
equipment. Refer to Appendix C, “ESD Requirements,” for more details
on electrostatic discharge (ESD).
Cleaning Guidelines
To ensure the cleanliness of fiber optic components, follow these guidelines:
• Use fiber patch cords (or connectors if you terminate your own fiber) only from a
reputable supplier. Low-quality components can cause many hard-to-diagnose
problems during an installation.
• Dust caps are typically installed on fiber optic components to ensure factory-clean
optical devices. These protective caps should not be removed until the moment of
connecting the fiber cable to the device. Ensure that the fiber is properly terminated,
polished, and free of any dust or dirt. Also make sure that the location of installation is
as free of dust and dirt as possible.
• If you must disconnect the fiber device, reinstall the protective dust caps.
• If you suspect that the optics have been contaminated, alternate between blasting with
clean, dry, compressed air and flushing with methanol to remove particles of dirt.