BV110InstallConfigGuide PDF

BV-110™ VERIFIER INSTALLATION
AND CONFIGURATION GUIDE
Release Number: 8.1

August 2012
Copyright and Trademarks
Copyright © 2012 EXFO Service Assurance, Inc. All rights reserved. Information in this
document is subject to change without notice and does not represent a commitment on the
part of EXFO Service Assurance, Inc.
A Measure Above, Brix, Brix Networks, Brix 100, Brix 100M, Brix 1000, Brix 2500,
Brix 3000, Brix 3500T, Brix 4000, Brix 4100, Brix 4104, BV-4210, BV-4220, BV-4230,
BV-110, Brixnet, Brixnet.net, BrixWorx, BrixCare, BrixCall, BrixVision, BrixMobile, Built
with Brix, Helping the Internet Measure Up, The Trusted Authority, and the Brix Networks
logo are trademarks of EXFO Service Assurance, Inc.
This product may include software developed by the following people and organizations
with the following copyright notices:
• Apache web server. (http://www.apache.org/). Copyright (c) 2007. The Apache Software
Foundation. All rights reserved. This product includes software developed by The Apache
Software Foundation.
• FreeType (http://www.freetype.org). All rights reserved. This software is based in part on
the work of the FreeType Team.
• GNU glibc. Copyright (c) 2007 Free Software Foundation, Inc. (http://fsf.org/). All rights
reserved. Verifiers use GNU glibc under the LGPLv3 license.
• JPEG (http://www.ijg.org). All rights reserved. This software is based in part on the work of
the Independent JPEG Group.
• libapreq2. (http://www.apache.org/). Copyright (c) 2003–2006. The Apache Software
• libpcap. Copyright (c) 1998, Regents of the University of California. All rights reserved.
• OpenSSH. Copyright (c) 1998, Regents of the University of California. All rights reserved.
• OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/). Copyright (c)
1998-2003. The OpenSSL Project. All rights reserved.
• oSIP. Copyright (c) 1991, 1999 Free Software Foundation, Inc. (http://fsf.org/). All rights
reserved. Verifiers use oSIP under the LGPLv2.1 license.
• Perl. Copyright (c) 2000-2006, The Perl Foundation. (http://www.perlfoundation.org). All
rights reserved.
• regex. Copyright (c) 1986, 1993, 1995, the University of Toronto. Written by Henry
Spencer. Not derived from licensed software. All rights reserved.
• SNMP. Copyright (c) 1989, 1991, 1992 by Carnegie Mellon University Derivative Work -
1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California.
All rights reserved.
Copyright (c) 2001-2003, Networks Associates Technology, Inc All rights reserved.
Portions of this product’s code are copyright (c) 2001-2003, Cambridge Broadband Ltd. All
rights reserved.
Copyright © 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California
95054, U.S.A. All rights reserved.
Copyright (c) 2003-2004, Sparta, Inc. All rights reserved.
Copyright (c) 2004, Cisco, Inc and Information Network Center of Beijing University of
Posts and Telecommunications. (http://net-snmp.sourceforge.net/about/license.html) All
rights reserved.
• Xerces. (http://www.apache.org/). Copyright (c) 1999, 2000. The Apache Software
• PHP. Copyright (c) 1999 - 2010. The PHP Group. All rights reserved. This product includes
PHP software, freely available from http://www.php.net/software/.
• Open Source Initiative OSI - The MIT License. Copyright (c) 2005, 2006. Thomas Fuchs.
(http://script.aculo.us, http://mir.aculo.us). All rights reserved.
All other trademarks or service marks are the property of their respective owners.
Any third party software provided to you is distributed under the terms of the license agree-
ments associated with that third party software. Where applicable, copies of these terms are
included elsewhere in the documentation for this product.
The source code for some of these components is available upon request for three years
from the date of your receipt of the product. Please submit requests to:
EXFO Service Assurance
270 Billerica Road
Chelmsford, MA 01824
attn: Source Code Support
Please be sure to include your mailing address and a check for US $35 to cover the cost of
distribution.
Release Number: 8.1

Book Version: 1.0.0
Release Date: August 2012
CONTENTS
Chapter 1
Introducing the BV-110 Verifier..................................................1
Overview ..................................................................................................................2
Features ...............................................................................................................2
Physical Characteristics .......................................................................................3
Front Panel Description ......................................................................................3
Back Panel Description-AC Verifier ..................................................................4
Back Panel Description-DC Verifier ..................................................................4
LED Behavior Descriptions ................................................................................5
Reset Button ........................................................................................................5
Port Connections ................................................................................................6
Regulatory Compliance ........................................................................................8
Laser Safety Warnings .......................................................................................9
Federal Communications Commission (FCC) and Industry Canada (IC)
Information .............................................................................................................10
Declaration Of Conformity ................................................................................. 11
iv BV-110 Installation and Configuration Guide
Chapter 2
Preparing for Installation .................................................................13
Safety Recommendations .................................................................................14
Electrostatic Discharge Prevention .................................................................14
Recycling and Disposal (Applies to European Union Only) ........................14
General Site Requirements ...............................................................................15
Power Supply ....................................................................................................15
Rack Mounting Kit .............................................................................................16
Site Considerations ...........................................................................................17
General Specifications .....................................................................................17
Site Planning Checklist .....................................................................................18
Chapter 3
Installing the BV-110 Verifier......................................................19
Overview of the Installation Process ...............................................................20
Verifying the Package Contents .......................................................................21
Materials Inventory ............................................................................................21
Rack Mount Parts List ......................................................................................21
Installation and Operational Warnings ...........................................................22
Connecting the Power ........................................................................................23
Connecting the BV-110 to an AC Power Source .........................................24
Connecting the BV-110 to a DC Power Source ...........................................25
Connecting the Ports ...........................................................................................27
Connecting the Console Port ..........................................................................27
Connecting the Test Ports ...............................................................................28
Connecting the Wireless Modem (Optional) .................................................29
Chapter 4
Bench Configuring the BV-110 Verifier ...........................31
What is Bench Configuration? ..........................................................................32
Bench Configuration and the CLI ....................................................................33
The Bench Configuration Process ..................................................................35
How to Bench Configure the BV-110 Verifier ...............................................36
Contents v
Other Ways to Change a Verifier’s Configuration .........................................37

The Routing Table ................................................................................................38
Chapter 5
Configuring the BV-110 Verifier using the Operations
Center .................................................................................................................41
Adding a Verifier to BrixWorx ............................................................................42
Before You Begin ..............................................................................................43
How to Add a BV-110 Verifier .........................................................................43
The Verifier Information Page ...........................................................................46
Basic Configuration Section ............................................................................47
Details Section ..................................................................................................51
Working with Advanced Parameters ..............................................................52
Verifier Network Configuration .........................................................................54
Phone Directory ................................................................................................55
Test Interfaces ...................................................................................................56
Static Routes .....................................................................................................60
Additional Services ...........................................................................................61
Advanced Configuration ..................................................................................65
Verifier Health ....................................................................................................67
Verifier Management ........................................................................................70
Verifier Attributes ...............................................................................................71
Chapter 6
Choosing a BV-110 Verifier Time Source.....................75
Introduction ............................................................................................................76
Available Time Sources ......................................................................................77
NTP Servers ......................................................................................................77
Default Time ......................................................................................................77
Whether to Use NTP ...........................................................................................78
vi BV-110 Installation and Configuration Guide
Chapter 7
Troubleshooting .......................................................................................79
Resources ..............................................................................................................80
Useful Procedures ...............................................................................................82
LED Behavior Descriptions ..............................................................................82
Check the Connection to BrixWorx ................................................................83
Force Discovery ................................................................................................84
Reboot the Verifier ............................................................................................84
Clear the Verifier’s Flash Memory ...................................................................86
Check the Log Files ..........................................................................................86
Check Verifier Cables and Serial Port Configuration ....................................89
Stop and Restart BrixWorx ..............................................................................89
Verify that BrixWorx is Running .......................................................................90
How to Analyze and Correct Problems .........................................................92
Hardware Installation Problems ......................................................................92
Connectivity Problems .....................................................................................93
Operational Problems ......................................................................................95
Finding Errors Using the CLI ...........................................................................98
Appendix A
BV-110 CLI Commands...................................................................99
CLI Commands ..................................................................................................100
Appendix B
Replacing a Brix 100M with a BV-110 Verifier....... 111
Introduction ..........................................................................................................112
Adding and Configuring the BV-110 Verifier ...............................................113
Replacing the Brix 100M ..................................................................................114
PREFACE
Purpose
This document provides information about the hardware setup,
installation, and configuration of the BV-110 Verifier.
Audience
This guide is intended for qualified hardware installers, network
administrators, and network managers, with knowledge of Linux and
basic networking concepts, who are responsible for installing and
configuring the Brix System.
Other Brix Documentation

The following documentation is available for BrixWorx and related
products:
Book Title Description

Brix Verifier Quick Start guides Installation information for the Brix 100M,
Brix 1000, Brix 2500, Brix 3000,
Brix 3500T, Brix 4100, Brix 4104, BV-4210,
BV-4220, BV-4230, and BV-110 Verifiers.
Brix Verifier Installation and Installation, configuration, and
Configurations Guides troubleshooting information for the
Brix 3000, BV-42xx, and BV-110 Verifiers.
viii BV-110 Installation and Configuration Guide

Brix GPS Module Installation Installation, configuration, and usage
Guide information for the Brix GPS Module.
Brix CDMA Module Installation Installation, configuration, and usage
Guide information for the Brix CDMA Module.
BrixWorx Installation Guide Background and procedural information for
installing BrixWorx software.
BrixWorx Embedded Oracle Background and procedural information for
Installation Guide installing BrixWorx software with embedded
Oracle.
BrixWorx User Guide Conceptual and procedural information on
using the BrixWorx Operations Center to set
up and manage BrixWorx System Verifiers,
Guaranteed Services, and Customer SLAs.
Brix Test Suite Reference Guide General conceptual information and detailed
reference information for BrixWorx Active
and Passive tests, including tests for Cisco IP
SLA-enabled routers.
Brix Advanced Video Reference General conceptual information and detailed
Guide reference information for the Brix Advanced
Video tests.
BrixCall Advanced VoIP Reference General conceptual information and detailed
Guide reference information for BrixCall Advanced
VoIP tests.
Brix Reference Guide Conceptual and procedural information on
troubleshooting BrixWorx, remote bench
configuration, and using BrixWorx utilities.
Brix Command Line Interface Usage and reference information for the Brix
Reference Guide command line interface (CLI), which allows
you to perform Verifier configuration and
administration procedures.
BrixCall Administrator’s Guide Conceptual and procedural information on
BrixCall, a service assurance product for the
passive monitoring of VoIP and IMS systems
in real time.
BrixIMS Administrator’s Guide Conceptual and procedural information on
BrixIMS, a family of service assurance
products for the passive monitoring of IP
mobile subsystems in real time.
Preface ix

BrixCare Self-Service Conceptual and procedural information on
Administrator’s Guide BrixCare Self-Service, a two-component
layered product that provides VoIP service
providers with management features and a
Java-based applet for qualifying prospective
subscribers.
BrixVision Infrastructure Conceptual and procedural information on
Verification Administrator’s Guide the BrixVision Infrastructure Verification
package, one of a family of IPTV products
that provides passive monitoring of user
requested channels and content.
BrixVision Live Monitoring User Conceptual and procedural information on
Guide and related manuals the BrixVision Live Monitoring package, a
central management system for configuring
Brix Video Verifiers and monitoring the
quality and performance of IPTV and other
video.
BrixView Administrator’s Guide Conceptual and procedural information on
setting up and managing BrixView Advanced
Reporting, a reporting and analysis product
that presents families of reports designed for
particular technologies and particular users.
BrixView report package guides Each BrixView report package, such as the
Backbone VoIP or the Carrier Ethernet package,
has its own user guide that provides usage and
reference information about the reports, portlets,
and portal pages in that package.
Available formats Technical documentation for Brix products is available

• Portable Document Format (PDF)
• The Operations Center online help
Tip: You need Adobe Acrobat Reader to open a PDF file. This product is
available for free from Adobe at www.adobe.com.
x BV-110 Installation and Configuration Guide
Other Sources of Information

Following are some additional resources to consider if you need
information that is not part of the Brix technical documentation, or if you
have questions that are not related to a particular product.
General information To learn more about Brix and EXFO products, services, and company
news
Visit http://www.exfo.com
Call +1 978-367-5600
Fax +1 978-367-5700
Email brixinfo@exfo.com
Mail EXFO Service Assurance

270 Billerica Road
USA
Technical Support There are several ways to contact Brix Customer Support
Visit http://www.exfo.com
Call • In the US: 1 877-261-3279

• Outside the US: +1 978-367-5789
Fax +1 978-367-5700
Email brixsupport@exfo.com
Mail EXFO Service Assurance
270 Billerica Road
USA
C HAPTER 1
INTRODUCING THE BV-110

VERIFIER
This chapter describes the BV-110 Verifier and its features. It provides
information about the physical characteristics and the regulatory
requirements of the BV-110 Verifier.
In this chapter This chapter contains the following sections:
Section Page
Overview 2
Physical Characteristics 3
Regulatory Compliance 8
Federal Communications Commission (FCC) and Industry Canada
(IC) Information 10
Declaration Of Conformity 11
2 BV-110 Installation and Configuration Guide
Chapter 1, Introducing the BV-110 Verifier
Overview
The BV-110 Verifier supports service measurement, data collection, and
data delivery to the BrixWorx system and is designed as a successor to the
current Brix 100M platform.
By deploying the BV-110 at key locations in core and edge networks and
customer locations, an administrator can view a variety of data about
enterprise, access, and core networks.
As the BV-110 is a Linux Verifier and uses an IPv6-capable kernel, it can
support both IPv4 and IPv6 interface configurations.
Features
The BV-110 Verifier has the following features:
• Supports IPv4 for tests and management and IPv6 for tests
functionality.
• Provides active test functionality.
• Performs active tests against third party devices using industry-
standard protocols
• Is compatible for active testing with the following Verifiers: BV-10,
Brix 100M, Brix 1000, Brix 2500, Brix 3000, and BV-3100.
• Supports two copper or fiber 1 GigE interfaces for active testing.
• Offers worldwide time synchronization options.
• Offers AC or DC power connectivity.
Chapter 1, Introducing the BV-110 Verifier 3
Physical Characteristics
Physical Characteristics
This section provides a physical description of the BV-110 Verifier.
In this section This section contains the following topics:
Topic Page
Front Panel Description 3
Back Panel Description-AC Verifier 4
Back Panel Description-DC Verifier 4
LED Behavior Descriptions 5
Reset Button 5
Port Connections 6
Front Panel Description

The front panel of the BV-110 contains the power and status light-
emitting diode (LED) indicators.
Power Status LED

LED
Back Panel Description-AC Verifier

The back panel of the BV-110 AC Verifier provides a power LED, status
LED, an RJ-45 serial port (console port), two test ports, ground post, and
two USB 2.0 ports for wireless connectivity.
Test ports Console port USB ports Ground post
Laser LED Status LED Power LED Reset button Power

connector
Back Panel Description-DC Verifier

The back panel of the BV-110 DC Verifier provides a power LED, status
LED, an RJ-45 serial port (console port), two test ports, ground post (earth
symbol), DC power source connectors, and two USB 2.0 ports for
wireless connectivity.
USB DC power source
Test ports Console port ports connectors
Laser LED Status LED Power LED Reset button Ground post
LED Behavior Descriptions

The LED indicator descriptions and behavior for the BV-110 Verifier are
as follows:
LED State/Color Indicates

Status Off Powered off
Solid amber Powering up
Blinking green (1 second on, 1 IP acquisition
second off)
Blinking green (0.5 second on, BrixWorx discovery
0.5 second off)
Solid green Operational
Link/Act Solid Green Valid Ethernet link
Off No Ethernet activity
Duplex Solid Amber Valid Ethernet link at:
• 10M full duplex
• 100M full duplex
DC Power Solid green DC power
Off No DC power
Blown fuse
Reset Button
The reset button allows you to restart the BV-110 Verifier. To reset the
BV-110 Verifier, use a stylus, such as a paperclip to press the reset button.
5-second reset If you press the reset button longer than five seconds, the running
configuration, the Test Configuration File (TCF), and the locally stored
plug-ins are removed from the BV-110 Verifier.
The bench configuration, the modified passwords, and the ssh keys are not
removed.
Port Connections
The following table lists the port connections for the BV-110 Verifier.
Port Description
Management There is no dedicated Management port on the BV-110.
The BrixWorx management traffic uses one of the test
ports. If only one test interface is required for active
testing, you can configure the other test interface for
BrixWorx communication to be routed through this
interface as a management interface.
Test Each Test port consists of a 1Gbps optical interface
through an SFP connector and a 10/100/1000Mbps
electrical interface with RJ-45 connector. These interfaces
are mutually exclusive. After an SFP is inserted, you must
enable the optical port either through CLI command or
BrixWorx user interface. The switch between electrical
and optical ports is not automatic. You can also use the
Test ports to send and receive management packets.
For more information. See “Connecting the Test Ports”
on page 28 to learn more about the Test ports.
Console The BV-110 Verifier has a Console port with an RJ-45
connector to connect with devices, such as another PC or
serial terminal server.
For more information. See “Connecting the Console
Port” on page 27 to learn more about the Console port.
Wireless The BV-110 Verifier has two USB slots in the back panel
(Optional) of the Verifier. You can insert pluggable devices such as a
wireless USB modem or a data card directly into the USB
slots.
For more information. See “Connecting the Wireless
Modem (Optional)” on page 29 to learn more about the
Wireless ports.
Port Connections
Console port RJ-45 The BV-110 Verifier comes with an RJ-45 connector, which plugs into the
connector Verifier’s Console port.
Pinout information The following figure displays the Verifier Console port for the RJ-45
pinout:
Console port
The following table displays the Console pinout information:
Pin Number Direction Description

1 IN Clear To Send (CTS)
2 OUT Data Terminal Ready (DTR)
3 OUT Transmit Data (TxD)
4 Ground
5 Ground
6 IN Receive Data (RxD)
7 IN Data Set Ready (DSR)
8 OUT Request To Send (RTS)
Note: Use the supplied 6 feet DB-9 to RJ-45 cable to connect the BV-110
console to a PC terminal.
Regulatory Compliance
The following table summarizes product safety, laser, and EMC standards
for the BV-110 Verifier.
Category Approval Agency

Safety IEC/EN/CSA/UL 61010-1 Safety Requirements for
Electrical Equipment for Measurement, Control, and
Laboratory Use - Part 1: General Requirement
Laser CLASS 1 LASER PRODUCT
Complies with 21 CFR 1040.10 as per Laser Notice
No. 42, dated December 18, 1989 and with IEC/EN
60825-1
Electromagnetic EN-61326
Compatibility (EMC) Title 47 CFR; FCC Part 15, Subpart B
ICES-003
Certification Marks cCSAus, CE
Laser Safety Warnings
Laser Safety Warnings

The BV-110 Verifier complies with 21 CFR 1040.10 as per Laser Notice
No. 42, dated December 18, 1989 and with IEC/EN 60825-1.
Class 1 Laser Product.
CAUTION: Use of controls, adjustments, and procedures for operation and
maintenance other than those specified herein may result in hazardous
radiation exposure.
CAUTION: Use only EXFO-supplied or approved, Class 1 SFP optical
transceivers.
WARNING: Do not install or terminate fibers while a source is active.
Never look directly into a live fiber, and ensure that your eyes are
protected at all times.
WARNING: Use of optical instruments with this product will increase
eye hazard.
WARNING: When the LASER LED is on or flashing, the BV-110 is
transmitting an optical signal from the optical Test ports.
The Laser LED is located on the back panel for the AC and DC Verifier
between the two Test ports.
Always inspect the fiber-optic connectors before using them and clean
them if necessary.
Turning the laser off There are two ways to turn the laser off:
and on
• Turn the Verifier off completely by removing all power from the
BV-110 Verifier.
• Access the BrixWorx CLI in Global Configuration mode and enter the
acquisition none command. This command closes down the
interface and implicitly turns off the laser.
For more information. Refer to the Brix Command Line Interface
Reference Guide to learn more about using the CLI.
To turn the laser on:
• Reattach the power cords to the Verifier.
For more information. See “General Specifications” on page 17 to
learn more about AC and DC power information.
• Use the acquisition fixed CLI command.
Reference Guide to learn more about how to use the CLI.
Federal Communications Commission (FCC) and

Industry Canada (IC) Information
Electronic test and measurement equipment is exempt from FCC Part 15
compliance in the United States and from IC ICES 003 compliance in
Canada. However, EXFO Inc. (EXFO) makes reasonable efforts to ensure
compliance to the applicable standards.
The limits set by these standards are designed to provide reasonable
protection against harmful interference when the equipment is operated in
a commercial environment. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance
with the user guide, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely
to cause harmful interference in which case the user will be required to
correct the interference at his own expense.
Declaration Of Conformity
Declaration Of Conformity
DECLARATION OF CONFORMITY
Application of Council Directive(s): 2006/95/EC – The Low Voltage Directive

2004/108/EC – The EMC Directive
93/68/EEC – CE Marking
And their amendments
Manufacturer’s Name and Address: EXFO Inc. EXFO Europe

400 Godin Avenue Omega Enterprise Park, Electron Way
Quebec City, Quebec Chandlers Ford, Hampshire
G1M 2K2 CANADA SO53 4SE ENGLAND
Tel.: +1 418 683-0211 Tel.: +44 2380 246810
Equipment Type/Environment: Test & Measurement / Industrial

Trade Name/Model No.: BV-110 Verifier / BV-110-AC
Standard(s) to which Conformity is declared:
EN 61010-1:2001 Edition 2.0 Safety requirements for electrical equipment for measurement,
control, and laboratory use – Part 1: General requirements
EN 61326-1:2006 Electrical equipment for measurement, control and laboratory use –

EMC requirements – Part 1: General requirements
EN 61000-3-2: 2006 + A1: 2009 + A2: 2009 Electromagnetic Compatibility (EMC) – Part 3-2: Limits – Limits for
harmonic current emissions (equipment input current up to and
including 16 A per phase).
EN 61000-3-3: 2008 Electromagnetic Compatibility (EMC) – Part 3-3: Limits – Limitation

of voltage changes, voltage fluctuations and flicker in public low-
voltage supply systems, for equipment with rated current <=16A per
phase and not subject to conditional connection.
I, the undersigned, hereby declare that the equipment specified above conforms to the above Directive and Standards.
Manufacturer:
Stephen Bull, E. Eng

Vice-President Research and Development
400 Godin Avenue,

Quebec City, Quebec
G1M 2K2 CANADA
August 18, 2010
Page 1 of 1
C HAPTER 2
PREPARING FOR INSTALLATION
This chapter lists the site requirements for the BV-110 Verifier. It also
provides safety recommendations as well as a description of the contents
of the kit in which the Verifier is shipped and a list of the tools required to
perform the installation.
Section Page
Safety Recommendations 14
General Site Requirements 15
Chapter 2, Preparing for Installation
Safety Recommendations
Before you proceed with the installation and configuration of the BV-110
Verifier, review the safety recommendations in this section.
Topics Page
Electrostatic Discharge Prevention 14
Recycling and Disposal (Applies to European Union Only) 14
WARNING: Only a trained technician can perform Verifier installation
and configuration tasks. A trained technician is one who has appropriate
technical training and experience to be aware of the hazards to which a
person can be exposed to when performing the installation tasks.
This symbol on the Verifier refers to safety-related instructions in the
Verifier documentation. Do not proceed unless the required conditions are
met for installing a BV-110 Verifier.
If the equipment is not used as specified by the manufacturer, the
protection provided by the equipment can be damaged.
Additional The following additional equipment information is provided:
equipment
information
Equipment is not serviced on site.
Electrostatic Discharge Prevention

Electrostatic discharge (ESD) damage can cause complete or intermittent
equipment failures. EXFO recommends that you always use an ESD-
preventive wrist or ankle strap and ensure that it makes good skin contact.
Recycling and Disposal (Applies to European Union

Only)
For complete recycling/disposal information as per European Directive
WEEE 2002/96/EC, visit the EXFO Web site at www.exfo.com/recycle.
Chapter 2, Preparing for Installation 15
General Site Requirements
General Site Requirements

This section describes the general site requirements for installing and
running a BV-110 Verifier.
Topics Page
Power Supply 15
Rack Mounting Kit 16
Site Considerations 17
General Specifications 17
Site Planning Checklist 18
Power Supply
The BV-110 Verifier has three following power options:
• Direct wire +24 V DC.
• Direct wire –48 V DC.
• AC option that requires an EXFO supplied AC power supply.
The power supply in this product contains no user-serviceable parts.
Ensure that your power supply is properly grounded and use EXFO-
approved or supplied power supplies for the BV-110 Verifier.
For more information. See “Connecting the Power” on page 23 for more
information about connecting power to AC and DC units.
Power supply cord Do not modify or use the supplied AC power cord if it is not the exact type
as per requirement.
The temperature of the DC Power Source connectors may exceed 60o C
under normal conditions, when the units are operated at an extended
temperature (applicable only for the ETR versions).
Main power Permanently connected equipment must have a switch or circuit-breaker
disconnect for disconnection. If the switch is not part of the kit:
• Include a switch or circuit-breaker in the installation.
• The switch must be located easily.
• The switch must be specified as the disconnecting device for the
equipment.
If the equipment is connected to two different power sources, ensure that
both disconnect devices are turned off to remove power from the unit.
Rack Mounting Kit

You can purchase an optional kit for mounting a BV-110 Verifier in a rack.
Contact your EXFO representative for more information about purchasing
the rack-mount kits.
Two ways to mount The following mounting options are available for a BV-110 Verifier:
a BV-110 Verifier
• You can mount either one Verifier on the left or the right, or two
Verifiers side-by-side on the shelf.
The rack must provide sufficient horizontal clearance to insert the
BV-110 Verifier side-by-side.
The vents that discharge the cooling air for the BV-110, which are
located on the top of the Verifier must have a minimum clearance of 3
inches (8 centimeters) to prevent overheating.
For more information. Refer to the BV-110 Rack Mounting
Instructions that accompanies your rack-mount kit to learn more about
mounting the BV-110 Verifier on an equipment rack.
• You can mount the BV-110 Verifier on a table using rubber feet
attached at the bottom of the Verifier.
Chapter 2, Preparing for Installation 17
Site Considerations
Site Considerations
This product must be installed in a restricted access area, which applies to
the +24 V DC and –48 V DC version. Restricted access areas include
central offices, telecommunication centers, computer rooms, wiring
closet, and similar type locations in agreement with local codes.
Choose a site that is:
• Well-ventilated and away from sources of heat including direct
sunlight.
• No object covering the ventilation above the Verifier.
WARNING: Hot surface.
General Specifications
The BV-110 has the following general specifications for the standard
version:
Size (H x W x D) 31 mm x 202 mm x 180 mm (1.22 in x 7.95 in x

7.09 in)
Weight 1.36 kg (3 lb)
Operating Temperature 0o - 50o C (32o - 122o F)
Humidity 5 - 90 % non-condensing
Operating Altitude 13 000 feet (4 000 meters)
Pollution degree 2
The BV-110 has the following general specifications for the ETR version:
Size (H x W x D) 31 mm x 202 mm x 180 mm (1.22 in x 7.95 in x

7.09 in)
Operating Temperature –40o - 70o C (–104o - 158o F)
Humidity 5 - 95 % non-condensing
Operating Altitude 13 000 feet (4 000 meters)
Pollution degree 2
Site Planning Checklist

You require the following information and components before installing
the BV-110 Verifier:
Item Description Value

External power supply and
AC power cord
______________________
Console cable for Verifier • RS-232 Connector port cable with an
RJ-45 connector. ______________________
A computer • Terminal Emulation (PUTTY,
HyperTerminal, and so forth) - in case
a serial terminals server is not used
• Web browser (FireFox, Internet ______________________
Explorer)
Configuration information • DHCP Address ______________________
• Fixed IP Address
• IP Address ______________________
• Net Mask ______________________
• Gateway Address ______________________
• DNS Server ______________________
• BrixWorx Server Discovery
Information ______________________
• IP Address ______________________
• Fully Qualified Domain Name ______________________
(FQDN) ______________________
• Web Agent Comm port
Network/firewall • http ______________________
information for installation • https ______________________
network • port numbers ______________________
C HAPTER 3
INSTALLING THE BV-110

VERIFIER
This chapter provides the procedures for installing the BV-110 Verifier,
connecting ports, and power supplies.
Section Page
Overview of the Installation Process 20
Verifying the Package Contents 21
Installation and Operational Warnings 22
Connecting the Power 23
Connecting the Ports 27
Chapter 3, Installing the BV-110 Verifier
Overview of the Installation Process

The following steps provide an overview of the installation process for the
BV-110 Verifier:
Step Description See

1. Unpack the BV-110. “Verifying the Package
Contents” on page 21.
2. Optionally mount the BV-110 BV-110 Rack Mounting
in a rack. Instructions.
3. Make power connections. “Connecting the Power” on
page 23.
4. Power on the BV-110 Verifier. “Connecting the Power” on
page 23.
5. Make port connections. “Connecting the Ports” on
page 27.
6. Configure the BV-110 “How to Bench Configure the
Verifier. BV-110 Verifier” on page 36.
Refer to the Brix Reference Guide
for information about adding
Verifier keys and BrixWorx
licenses.
After installing the Verifier, you must establish communication with

BrixWorx. You have to establish communication in the following ways:
1 Use the CLI to bench configure the BV-110 Verifier. Bench
configuration is the process of manually providing a BV-110 Verifier
with user-defined settings.
For more information. See “The Bench Configuration Process” on
page 35 to learn more about the bench configuration process.
Note: You can bench configure the BV-110 Verifier before or after
you install it.
2 Use the BrixWorx Operations Center to add the new Verifier through
the user interface.
For more information. See “The Verifier Information Page” on
page 46 to learn more about adding a new Verifier.
Chapter 3, Installing the BV-110 Verifier 21
Verifying the Package Contents
Verifying the Package Contents

The BV-110 Verifier is packaged with the Verifier, cables, rack-mount kit,
and documentation.
Materials Inventory
The kit in which the BV-110 is shipped to you contains the following
items:
• A BV-110 Verifier.
• Rack-mount kit (optional)
• Console port cable for RS-232 connector with an RJ-45 serial cable.
• AC power cord (for AC units only).
• Power adapter (for AC units only).
• The BV-110 Quick Start Guide.
Check this list with the kit’s contents. If anything is missing or appears
damaged, retain the original custom packaging and contact EXFO Service
Assurance.
Optional contents You can purchase SFP optical modules from EXFO for fiber connectivity.
Rack Mount Parts List

The BV-110 Verifier rack mount kit lets you secure a BV-110 Verifier to
an equipment rack. The kit includes all items necessary for installation, as
well as the instructions for installation of the kit.
Tools
No special tools are required to install the BV-110 Verifier. If you are
rack-mounting the BV-110 Verifier using the supplied rack-mount kit, you
need a Phillips head screw driver.
Installation and Operational Warnings

This section explains the operational warnings regarding the BV-110
Verifier installation.
Operating ambient If the Verifier is installed in a closed or multi-unit rack assembly, the
temperature operating ambient temperature of the rack environment can be greater than
the ambient temperature of the room. The Verifier must be installed in an
environment compatible with the ambient temperature of 0 - 50o C for
standard version and –40 - 70o C for the ETR version.
Air flow Installation of the Verifier in a rack or cabinet must not compromise the
amount of airflow required for safe operation of the equipment.
Mechanical loading Mounting of the Verifier in a rack or cabinet must not be hazardous due to
uneven mechanical loading.
Circuit overloading The connection of the Verifier to the supply circuit must not overload the
circuits and result in an effect on the over-current protection and supply
wiring. The equipment nameplate ratings must also be considered.
Reliable earthing Reliable earthing of rack-mounted equipment must be maintained.
Particular attention should be given to supply connections other than direct
connections to the branch circuit (use of power strips, for example).
DC units For Verifiers equipped with DC power, follow these instructions before and
during installation:
1 Ensure that the power is off or disconnected at the source.
2 Before you connect the power supply or telecommunication lines,
install a protective earth (PE) or ground connection, using a wire gauge
in accordance with the local code. The ground or earthing connection
requires a ring or fork type terminal. The earthing stud or post is of 6 -
32 size.
3 Strip each power lead to 7 mm length.
4 Insert each power lead into the correct terminal of the plug and tighten
the screw (tightening torque: 0.5 - 0.6 Nm) to secure the lead.
5 After both terminals are completed, insert and tighten the entire plug
into the DC power connector (tightening torque: 0.5 - 0.6 Nm).
For more information. See “Connecting the Power” on page 23 to learn
more about connecting power supply.
Connecting the Power
Connecting the Power

The BV-110 has redundant +24 V or –48 V DC power supply that is
integrated in the unit. The BV-110 AC Verifier uses an external power
supply providing 12 V DC to the BV-110 Verifier. Ensure that the
connector used with the BV-110 is able to sustain a maximum peak
continuous current of 1 A for the BV-110-DC48/BV-110-DC48ETR
Verifier and 2 A for the BV-110-DC24ETR Verifier.
Mating connector Use the mating connector supplied by EXFO.
for BV-110 +24 V or
–48 V DC Verifier
The following mating connector specifications are required:
Technical Data
Tightening torque, minimum 0.5 Nm
Tightening torque, maximum 0.6 Nm
Stripping length 7 mm
Connection Data
Conductor cross section solid, maximum 2.5 mm²
Conductor cross section stranded, maximum 2.5 mm²
Conductor cross section stranded, with ferrule 2.5 mm²
without plastic sleeve, maximum
Conductor cross section stranded, with ferrule with 2.5 mm²
plastic sleeve, maximum
Conductor cross section AWG/kcmil, maximum 12
2 conductors with same cross section, solid, 1 mm²
maximum
2 conductors with same cross section, stranded, 1.5 mm²
maximum
2 conductors with same cross section, stranded, 1 mm²
ferrules without plastic sleeve, maximum
2 conductors with same cross section, stranded, 1.5 mm²
TWIN ferrules with plastic sleeve, maximum
BV-110 Verifier power ratings:
Power Input
Model Rating Input Voltage Range Temperature Humidity
BV-110-AC 12 V; 2.5 A 12 V; 2.5 A 0 - 50° C 5 - 90 %
uses external
approved AC/
DC adapter
BV-110- dual DC –48/– –40 V - –72 V 0 - 50° C 5 - 90 %
DC48 60 V; 0.75 A
BV-110- dual DC –48/– –40 V - –72 V –40 - 70° C 5 - 95 %
DC48ETR 60 V; 0.75 A
BV-110- dual 20 V - 32 V –40 - 70° C 5 - 95 %
DC24ETR +24 V; 1.5 A
As soon as the BV-110 is connected to a live power supply, the power

LED turns on. (If the power LED does not turn on, there is a power failure
at the source or the unit is damaged.) The status LED indicates whether or
not the unit is ready for use.
For more information. See BV-110 Installation and Configuration Guide
to learn more about the status LED.
Connecting the BV-110 to an AC Power Source

This section explains how to connect power to a BV-110 equipped with
AC power. The unit uses 12 V DC external power supply.
AC power connector
How to connect an Connect the supplied AC power cord and power adapter to the BV-110
AC unit and then plug the power cord into electrical outlets. Use only the EXFO-
supplied power adapter to ensure safety in operation and compliance to
specifications. Country specific AC power cord and power adapter are
shipped with the BV-110 Verifier.
Connecting the BV-110 to a DC Power Source
Connecting the BV-110 to a DC Power Source

This section explains how to connect power to a BV-110 equipped with
DC power. The unit is equipped with either +24 V or –48 V DC power.
DC power source
How to connect a For connecting the DC Verifier, you must adhere to the following
DC unit instructions before and during installation:
1 Ensure that the power is off or disconnected at the source.
2 Before you connect the power supply or telecommunication lines,
install a protective earth (PE) or ground connection, using a wire gauge
in accordance with the local code.
The ground or earthing connection requires a ring or fork type
terminal. The earthing stud or post is of 6 - 32 size.
3 Strip each power lead to 7 mm length.
4 Insert each power lead into the correct terminal of the plug and tighten
the screw (tightening torque: 0.5 - 0.6 Nm) to secure the lead.
• Connect the RTN lead to the RTN terminal on the left.
• Connect the –48 V DC or +24 V DC lead to the –48 V DC or
+24 V DC terminal on the left.
• Optionally, if available, connect the secondary RTN lead to the
RTN terminal on the right.
• Optionally, if available, connect the secondary –48 V DC or
+24 V DC lead to the –48 V DC or +24 V DC terminal on the right.
5 After both terminals are completed, insert and tighten the entire plug
into the DC power connector (tightening torque: 0.5 - 0.6 Nm).
For more information. See “Mating connector for BV-110 +24 V or –
48 V DC Verifier” on page 23 to learn more about the mating connector
specifications.
Fuse ratings The following table displays the fuse ratings for the BV-110 Verifier:
Version Voltage Range (V) Fuse Rating (A)

AC 12 V 3
DC48/DC48-ETR –40 V - –72 V 1
DC24-ETR 20 V - 32 V 2
Connecting the Ports
Connecting the Ports

This section describes how to connect the Console, Test, and Wireless
ports. All parts to connect the various ports of the BV-110 are provided
with the product.
In this section This section covers the following topics:
Topic Page
Connecting the Console Port 27
Connecting the Test Ports 28
Connecting the Wireless Modem (Optional) 29
Connecting the Console Port

Connect the Console port configured to 9600 baud; 8 data bits, no parity,
and 1 stop bit (8-N-1); no flow control using the supplied RJ-45 serial
cable shipped with the Verifier. Connect the Console port to your RS-232
device.
If you are connecting the BV-110 Verifier to a terminal server, you must
consult the terminal servers manufacturer to ensure proper connectivity.
For more information. See the “Pinout information” on page 7 to learn
more about Console pinout information.
Console port
To communicate with the BrixWorx server, you must enter the IP address
of the server through the Console port. The following sections provide
information about configuring the IP address for the BV-110 Verifier
using the bench configuration mode of the BV-110 Verifier.
For more information. See the “How to Bench Configure the BV-110
Verifier” on page 36to learn more about bench configuration.
Connecting the Test Ports

The BV-110 Verifier supports two Test ports. One of these Test ports also
has to be configured for management traffic. There is no dedicated
Management port on the BV-110.
Each Test port consists of a 1 Gbps optical (fiber) interface through an
SFP connector and an 10/100/1000 Mbps electrical (copper) interface
with an RJ-45 connector. These interfaces are mutually exclusive.
A Test port is used for active testing. The active tests can be configured on
any of the Test ports. One of the Test ports can also be dedicated for smart
loopback. If you configure a Test port for smart loopback, the configured
port cannot be used for active testing.
How to connect a To connect a Test port:
Test port
1 If you are using the optical interface, plug in the appropriate 1000Base-
SX/LX SFP optic into the desired SFP test port. Plug the fiber optic
cable into the SFP optic.
Note: The SFP network cable must be purchased separately.
2 Using BrixWorx, activate the desired fiber or copper port.
Note: You can activate only one type of connection per Test port at a
time, copper or fiber. By default, the copper test connection is activated
when the BV-110 Verifier is powered up if you have not saved any
configuration.
Test ports
For more information. See “BV-110 CLI Commands” on page 99 to

learn more about the CLI commands to activate the optical or electrical
interface loopback.
Connecting the Wireless Modem (Optional)
Connecting the Wireless Modem (Optional)

On the back panel of the BV-110 Verifier, insert the USB device directly
into one of the USB slots.
The USB device can be inserted before or after the BV-110 Verifier is
booted. If you insert the USB device after the system is booted, the
BV-110 Verifier automatically detects the device and loads the appropriate
kernel drivers.
USB ports
You can configure the USB device using the BrixWorx Operations Center
or the Brix CLI.
For more information. Refer to the BrixWorx User Guide to learn about
the Operations Center and the Brix Command Line Interface Reference
Guide to learn how to use the CLI.
C HAPTER 4
BENCH CONFIGURING THE

BV-110 VERIFIER
This chapter explains how to bench configure the BV-110 Verifier. It also
explains the routing table and how to reboot the Verifier.
Section Page
What is Bench Configuration? 32
Bench Configuration and the CLI 33
The Bench Configuration Process 35
How to Bench Configure the BV-110 Verifier 36
The Routing Table 38
Chapter 4, Bench Configuring the BV-110 Verifier
What is Bench Configuration?

Bench configuration is the process of manually providing a BV-110
Verifier with user-defined default settings. The Verifier requires this
information to communicate with BrixWorx.
The primary bench configuration settings are the IP addresses for the
BrixWorx servers (called registries) and the Communication Port
specified when BrixWorx is installed. In addition, you can specify other
settings, such as the IP address acquisition method and the IP addresses of
the Verifier’s active Test ports, during bench configuration.
You can bench configure a Verifier before or after you install it.
For more information. Refer to Chapter 3, Verifiers, in the BrixWorx
User Guide to learn more about the discovery process.
Chapter 4, Bench Configuring the BV-110 Verifier 33
Bench Configuration and the CLI
Bench Configuration and the CLI

You use Brix Command Line Interface (CLI) commands in bench
configuration mode to bench configure a Verifier. Your bench
configuration changes are written to the Verifier’s disk file system when
you save the changes.
Saving bench The changes that you make to a Verifier’s configuration using the CLI in
configuration the bench configuration mode are applied only after you write the bench
changes configuration changes into the Verifier’s running configuration. When you
exit the bench configuration mode, a message is displayed to save the
bench configuration changes, and if you want to write the bench
configuration changes into the running configuration. Type Y for both
messages.
The changes that you make to a Verifier’s configuration using the CLI in
other modes are written to a local copy of the VCF. The VCF is stored in
the Verifier’s file system and is applied immediately. These changes are
written to BrixWorx and merged with the copy of the VCF that resides in
BrixWorx. The revised VCF is written back to the Verifier the next time
the Verifier polls BrixWorx.
For more information. Refer to Chapter 1, Brix Command Line Interface
Reference Guide, to learn more about CLI modes and the commands you
can enter in each mode.
Bench To bench configure a Verifier, you need to specify information about the
configuration BrixWorx installation, with which the Verifier needs to communicate its
commands basic information. You can enter all other Verifier information using either
the CLI commands or the BrixWorx Operations Center.
The following table lists a set of CLI commands that you must enter in the
given order when you bench configure a Verifier.
For more information. See “The Bench Configuration Process” on
page 35 to learn more about the bench configuration process.
CLI Command Description

server discovery local Address of the Local Registry. IP
address of the BrixWorx server.
server discovery network Address of the Network Registry.
The IP address can be same as the
local registry.

Interface eth number commands: Configure the Verifier’s Test ports.
• acquisition The BV-110 has two Test Ports (eth0
and eth1).
• address
• default-gateway
(configurable only if
acquisition is fixed)
• vlan
[no] ip name-server Add or delete the IP address of a DNS
server from a list of DNS servers for
the Verifier.
[no] ip domain-name Creates or deletes the default domain
name used for any host that is
configured without a domain.
The following table lists additional CLI commands that you can use when
you bench configure a Verifier.

route Add or delete routes from the
Verifier’s routing table.
device-name Specifies the name of the Verifier.
server communications comm-port Comm port used for communication
between the Verifier and BrixWorx.
The default port is 80.
password Change the login or the enable
password.
preview changes Displays all the information that is
changed and not committed to the
Verifier’s running configuration
during the current CLI session.

Reference Guide for detailed information about each CLI command.
The Bench Configuration Process
The Bench Configuration Process

The BV-110 Verifier is bench configured locally. You must connect to the
BV-110 Verifier through a serial connection to configure the Verifier for
the first time. The serial connection also allows access to the BIOS and to
the Grand Unified Boot Loader (GRUB) boot menu as a primary boot
loader. A boot loader is the first software program that runs when a
computer starts, which loads and transfers control to the operating
system kernel software that is Linux. The kernel then initializes the
rest of the operating system.
Connecting to the To connect to the BV-110 Verifier:
BV-110 Verifier
1 Connect the serial cable to the BV-110 Verifier, using the RJ-45
connector.
a If the BV-110 Verifier serial port is connected to a PC, use the RJ-
45 serial cable shipped with the Verifier.
b If the BV-110 Verifier serial port is connected to a vendor-specific
terminal server, follow the instructions for the terminal server-
specific cables to connect to the BV-110 Verifier serial port.
2 Configure the serial terminal software to 9600 baud rate 8-N-1.
Supply power to the Before you begin bench configuration, ensure that power is supplied to the
BV-110 Verifier BV-110 Verifier.
For more information. See “Connecting the Power” on page 23 to learn
more about connecting power.
Once you supply power, the BV-110 Verifier boots up. While the BV-110
is booting up, the front panel status LED is amber.
Wait until the boot up is complete before you continue. The boot up is
complete when ‘System startup success’ is displayed at the serial
port and the login prompt appears.
How to Bench Configure the BV-110 Verifier

This section explains how to bench configure the BV-110 Verifier. It also
presents other ways to change a Verifier’s configuration.
Before you begin Before you enter the CLI commands for bench configuration, ensure that
the following information is available:
• Username and password if the defaults have been changed.
• Enable password if one has been created.
• IP address or host names for the following:
• Local Registry
• Network Registry (This can be same as the IP address for the local
registry.)
How to enter bench To enter CLI bench configuration commands:
configuration
1 Log on to the BV-110 and start a CLI session using either the default
commands
user name (admin) and the default password (admin) or a new user
name and password that is defined for the BV-110.
2 At the EXEC mode prompt ‘BV-110_name>, enter the enable command
to change to privileged EXEC mode.
3 If an enable password is created, enter the password at the prompt;
else, press Enter.
The prompt changes to BV-110_name#.
4 Enter the bench-cfg command to change to bench configuration
mode.
The prompt changes to BV-110_name(bc)#.
5 Enter the following commands to bench configure the BV-110:
Server discovery local
Server discovery network
6 Enter the preview changes command to view the bench configuration
information that is saved when you exit.
7 Enter the end or exit command to exit the bench configuration mode.
The following prompt appears:
Save bench configuration changes? [Y/N]
8 Type Y to write the bench configuration settings to the BV-110 file
system.
The following prompt appears:
Save bench configuration changes to running
configuration? [Y/N]
Other Ways to Change a Verifier’s Configuration
9 Type Y for the bench configuration changes to apply immediately.

You return to the privileged EXEC mode.
10 Enter the exit command twice to exit the CLI.
Note: The default server comm http port address for BrixWorx is x80.
You must change it if the comm port address is changed during the
BrixWorx setup.
Reboot the BV-110 The Verifier’s reset button is located adjacent to the Status LED on the AC
using the reset or DC Verifier’s back panel. Use a fine-point stylus, such as a paper clip,
button to reboot the Verifier.
To reboot a Verifier using the Verifier’s Reset button:
1. Locate the Verifier you want to reboot.
2. Press and release the Reset button.
WARNING: Ensure that you release the Reset button after you press it.
Holding the Reset button for 5 seconds or more clears the Verifier’s flash
memory.
Other Ways to Change a Verifier’s Configuration

When a Verifier is communicating with BrixWorx, you can change its
configuration information using the:
• BrixWorx Operations Center. Refer to Chapter 3, Verifiers, in the
BrixWorx User Guide.
Information about a Verifier configured using any of these methods is
written to the Verifier’s Verifier configuration file (VCF). The default
configuration file (DCF), which is a type of VCF is generated by the
Verifier and contains the default and bench configuration of a
Verifier.The settings in the VCF supersede, but do not permanently
replace, bench configured settings. The Verifier acquires its VCF the
next time it communicates with BrixWorx.
• Brix CLI. Refer to the Brix Command Line Interface Reference Guide.
When the configuration is changed on the Verifier using CLI, the
Verifier sends the current system configuration to the Local
Configuration File (LCF), which is also a type of the VCF. The LCF
includes the CLI changes, a combination of defaults, bench
configuration, and the existing VCF.
After the new LCF is created, BrixWorx requests the Verifier to upload
the LCF. Brixworx merges the LCF with its VCF to create a new VCF.
The new VCF is downloaded to the Verifier.
The Routing Table

The BV-110 Verifier has a routing table that lists the routes associated
with the Verifier’s interfaces and aliases.
An interface route can be defined manually using a fixed IP address or
automatically using DHCP or BOOTP. Aliases can also be defined either
from the CLI or from the BrixWorx Operations Center, refer to the
Verifiers chapter in the BrixWorx User Guide.
Interface names In the routing table, a Verifier’s Test interfaces are identified as eth0 and
eth1. Aliases for the Test interfaces are listed with a suffix composed of a
period and a number (for example, eth0.1).
The loopback interface, identified as lo0, is listed in the routing table and
cannot be changed.
How to display the To display a Verifier’s routing table, enter the show routes CLI command.
routing table
The following example displays the routes for an IPv4 configuration:
Routing table
Destination Gateway Subnet mask Metric Interface
127.0.0.1 127.0.0.1 255.255.255.255 1 lo0
192.168.2.0 192.168.2.170 255.255.255.0 10 eth0:2
192.168.1.0 192.168.1.170 255.255.255.0 10 eth0:1
192.168.4.0 192.168.4.170 255.255.255.0 10 eth0
0.0.0.0 192.168.4.15 0.0.0.0 1 eth0
Total of 5 routes.
When the Verifier is configured for IPv6, the show routes command also
displays IPv6 addresses.
Routing table A routing table displays the following information:
contents
• The destination network address of the packets using that route. For the
Test interface and aliases that you define, the destination network
address is based on the network portion of the IP address and subnet
mask you define for the interface or alias. The destination network
address for eth0:1 (192.168.1.0), for example, was derived by applying
the subnet mask 255.255.255.0 to the alias’s IP address
(192.168.1.170).
• The gateway IP address used. For directly connected routes, this is a
zero address. For indirectly connected routes, this is the next hop.
• The destination network’s subnet mask.
• A metric used by the routing algorithm to evaluate equivalent routes.
• The interface or alias associated with the route.
The Routing Table
How a routing table The routing table is modified when you define or modify an interface or
is modified an alias. You can also manually add and remove routes.
You can manage the routes using either the Static Routes section of the
Verifier Information page in the Operations Center or the CLI route
command.
Algorithm controls A Verifier uses a routing algorithm to evaluate routes, select an interface
the selection of or alias, and assign VLAN tags. The algorithm used for information is
routes transmitted through the interface or alias.
For more information. Refer to the Verifiers chapter in the BrixWorx
User Guide to learn more about the routing algorithm.
Determining which The default addresses for the test port and management port are the IP
route is used address, subnet mask, and gateway address you specify using the
interface commands in bench configuration mode. You can define other
routes using the route command.
If you specify multiple routes, the metric value you enter for a route
determines if it is selected. The lower the metric value, the higher its
priority when a route is selected for the Verifier’s traffic. For example, a
route with a metric of 1 is always selected before a route with a metric of
10. You can also enter the same metric for different routes.
C HAPTER 5
CONFIGURING THE BV-110

VERIFIER USING THE
OPERATIONS CENTER
This chapter provides procedures for configuring the BV-110 Verifier

using the BrixWorx Operations Center. This chapter also explains how to
add a Verifier to BrixWorx, with basic and advanced configuration
information.
Section Page
Adding a Verifier to BrixWorx 42
The Verifier Information Page 46
Working with Advanced Parameters 52
Chapter 5, Configuring the BV-110 Verifier using the Operations Center
Adding a Verifier to BrixWorx

A system administrator adds Verifiers to the BrixWorx system. Contact
your BrixWorx system administrator before proceeding.
This section describes how to add a Verifier to BrixWorx using the
BrixWorx Operations Center. It provides information on basic and
advanced configuration parameters. Basic configuration parameters
include Verifier name, alias, model and serial number, network link type,
and if the Verifier can be shared across multiple SLAs. The advanced
configuration parameters include settings for bandwidth, timeout, transfer
size, and transfer rates.
Adding a Verifier to BrixWorx is the process of creating an identity for the
Verifier. The information you provide about the Verifier while adding it to
BrixWorx is used to create the Verifier Configuration File (VCF) for that
Verifier. The VCF is written to the Verifier after it has successfully
discovered its Local Registry and polled the registry for information about
itself.
You can also add a Verifier to BrixWorx using the Command Line
Interface (CLI) and the verifier-util utility.
Reference Guide, the Brix Reference Guide, and see, Chapter 4, Bench
Configuring the BV-110 Verifier, on page 31 to learn more about the CLI
bench configuration process.
You can install a Verifier on your network before defining any information
about it using the BrixWorx Operations Center.
Topic Page
Before You Begin 43
How to Add a BV-110 Verifier 43
Chapter 5, Configuring the BV-110 Verifier using the Operations Center 43
Before You Begin
Before You Begin

Before you add a Verifier to BrixWorx, you must:
• Add the Verifier key to BrixWorx. The Verifier key contains the model,
serial number, and other information for the Verifier you have
purchased.
• Add BrixWorx licenses to BrixWorx.
Keys and licenses Verifier keys and BrixWorx licenses are shipped separately from your
shipped separately BrixWorx software and Brix Verifiers. Both keys and licenses come with
their own set of installation instructions. Installation information is
reproduced within the BrixWorx documentation set for your convenience.
For more information. Refer to the Brix Reference Guide for
information about adding Verifier keys and BrixWorx licenses.
How to Add a BV-110 Verifier

To add a BV-110 Verifier to BrixWorx:
1 Select Add a Verifier from the Verifier menu.
The Basic Configuration page of the Verifier appears.
2 Enter a name for the Verifier in the Name field.

3 Optionally, enter a Verifier alias name in the Alias field.
4 Select a model and serial number from the Model/SN drop-down list.
The Basic Configuration page expands to display other configuration
parameters for the Verifier.
5 Indicate if you want this Verifier to be shared by multiple SLAs by

selecting a radio button in the Shared field. By default, a Verifier can
be used by multiple SLAs.
6 Specify the type of network connection by selecting a value from the
Link Type drop-down list.
7 Click the save and continue button.
The Verifier Information page is refreshed. The page includes a
summary of the Verifier’s basic configuration information, as well as
tools that let you fine-tune the Verifier configuration.
8 If you want to deploy the Verifier using the current configuration, click
the save and continue button to add the Verifier to BrixWorx. This
creates the Verifier’s VCF, which is written to the Verifier the next time
the Verifier polls its BrixWorx server.
How to Add a BV-110 Verifier
Additional You can specify Verifier parameters beyond the basic parameters. These
parameters parameters are referred to as advanced parameters. You can use these
parameters to fine-tune your Verifier’s setup within BrixWorx. You can
specify advanced parameters at the same time you add the Verifier to
BrixWorx, or later, as required.
For more information. See “Working with Advanced Parameters” on
page 52 to learn more about advanced parameters.
Editing basic The Verifier Information page provides a summary of all the Verifiers
Verifier information associated with the BrixWorx system. Information displayed on this page
includes configuration status, model number, and IP address.
The Verifiers submenu allows you to add a Verifier to the system, view
Verifier locations, manage SLAs, and manage remote router hardware. To
change a Verifier’s basic configuration after adding it to BrixWorx, use the
Verifier Information page.
How to access the To access the Verifier Information page:
Verifier Information
1 Enter the URL for BrixWorx and enter the user name and password to
page
log on to the Operations Center.
2 From the Operations Center home page, click Verifiers.
The Verifiers page is displayed.
3 Select the Verifier for which you want to view detailed information.
The Verifier Information page is displayed.
The Verifier Information Page

The Verifier Information page provides access to the Verifier that you
want to add, modify, or delete. The following screen displays the Verifier
Information Page:
Categories of Advanced Parameters
The Verifier Information page contains the following sections:

• Basic Configuration: Lists the basic Verifier identification and
features. This information can be edited.
For more information. See “Basic Configuration Section” on page 47
to learn more about the basic configuration of the Verifier.
• Details: Lists the values of the configured Verifier.
For more information. See “Details Section” on page 51 to learn
more about the Verifier details.
• Advanced Parameters: This section describes the Advanced
parameters that are displayed on the Verifier Information page as a
series of collapsed categories.
For more information. See “Working with Advanced Parameters” on
page 52 to learn more about the advanced parameters.
Basic Configuration Section

This section describes how to configure your Verifier to establish a
connection with the BrixWorx server. You can name the Verifier, choose
the model and serial number, and so on.
In this section Fields on the Verifier Basic Configuration page include:
Fields Page
Naming your Verifier 47
Verifier aliases 47
Model and serial number 48
Sharing the Verifier 48
Network link type 49
Registry and collector lists 49
Monolith 50
Details Section 51
The fields are described in the following sections:
Naming your Verifier

You need to name the Verifiers you add to the BrixWorx system and
optionally add a Verifier alias. Verifier names, Verifier aliases, or both are
used to identify Verifiers in reports, alerts, SLA creation, and other places
throughout the BrixWorx Operations Center. Verifier names and Verifier
aliases must be unique across the BrixWorx system.
Verifier aliases
A Verifier alias is an optional alternate name for a Verifier. You can
specify an alias when you add a Verifier to BrixWorx. Each Verifier can
have a single Verifier alias and that Verifier alias must be unique across
the BrixWorx system.
Model and serial number

Each Verifier is assigned a model and serial number by the manufacturer.
These model and serial numbers are added to the BrixWorx database when
you install the Verifier.
You must provide a model and serial number for the Verifiers you want to
add to BrixWorx. BrixWorx uses the model and serial number when
issuing alerts for unknown Verifiers, and for other reporting situations that
require Verifier identification.
Note: If the Verifier is installed on the network but is not yet added to
BrixWorx, a Verifier is identified as unknown.
Model/SN field The Model/SN field displays a list of the Verifiers for which Verifier keys
shows available are installed.
Verifiers
If you do not know which Verifier you want to add to BrixWorx, you can
leave the value of the Model/SN field as Not Associated, but you must
provide this information before the Verifier can become operational.
For more information. Refer to the Brix Reference Guide to learn more
about installing Verifier keys.
Model/serial When you provide a model and serial number or identifier for the Verifier,
number provides the system displays the following basic configuration information:
other default values
• Network Registry list
• Collector list
• Monolith
For more information. See “Details Section” on page 51 to learn more
about the Verifier details.
Sharing the Verifier

You can share Verifiers across multiple SLAs by selecting the Multiple
radio button in the Shared field. By default, the Multiple radio button is
selected.
If you select the Single radio button, the Verifiers are associated with a
single SLA. When you associate the Verifier with the single SLA, that
Verifier cannot be used by any other SLA.
Network link type

You must specify the capacity of the network on which the Verifier is
running. This information is used by the preflight process to determine if
the Verifier’s network link has the capacity to run the tests associated with
the Verifier. Link types range from 56 Kbs to 1000 Mbs. By default, the
value in the Link Type field is 100 Mbs.
Tip: The Verifier’s Active Testing Bandwidth and Reporting Bandwidth
values specified as part of a Verifier’s advanced configuration parameters
represent percentages of the total bandwidth defined by the network link
type.
For more information. See “Advanced Configuration” on page 65 to
learn more about the Verifier parameters.
Registry and collector lists

Each Verifier must be associated with one or more BrixWorx hosts that
serve as local registry and collectors. The BrixWorx host often performs
both roles, but you can also assign multiple hosts to each role.
You can change local registry and collector information for a Verifier by
selecting the Verifier and using the arrow controls to move a host from the
Available to Active list boxes.
Tip: BrixWorx always tries to contact the hosts in the order they are listed,
starting at the top of the Active group boxes. You can use the up and down
arrows to change the hosts order.
Monolith
A Verifier’s monolith consists of its operating system, its user level
applications, and supporting libraries. A monolith is created when the
Verifier is manufactured; it is updated over time, when you upgrade
BrixWorx, for example.
Monolith version (also referred to as monolith image) information
displayed on the Verifier Information page displays the most current
monolith on the BrixWorx server. If the Verifier’s monolith version is out
of date with the monolith displayed here, the Verifier’s monolith is
updated the next time it receives a VCF.
Tip: The Modules/Monoliths page displays a list of the monolith images
that are installed on BrixWorx. These are the monolith images (versions)
that are used to create the Verifier configuration file.
To display this page, select Modules/Monoliths from the System menu.

Details Section
Details Section
The Details section of a BV-110 Verifier Information page displays the
values of the configured Verifier.
The Details section includes values for the following:
• Verifier Group, if any
• SLAs
• MAC Address (Test Interface 1)
• MAC Address (Test Interface 2)
• Current IP Address
• Current VCF
The following figure displays a sample Details section from the Verifier
Information page for a BV-110 Verifier:
Verifier details are not editable. However, the SLA field provides direct
links to the SLA Details page for each SLA that is configured to run on the
Verifier.
Working with Advanced Parameters

This section describes the advanced parameters that are displayed on the
Verifier Information page as a series of collapsed categories (Verifier
Network Configuration, Test Interface, and so on). Each category contains
a set of fields that becomes visible when you expand the category or click
the edit button.
Categories expand The Advanced Parameters have an auto-selection feature for some
and collapse parameters that allow the default settings on the Verifier to be used.
Advanced parameters are available on the Verifier Information page after
you add a Verifier to BrixWorx. To access the advanced parameter
categories, you must complete the following steps:
• Name the Verifier.
• Associate a serial number with the Verifier.
How to view the By default, the categories for advanced Verifier parameters are collapsed.
category content To view the category content, you can expand:
• All categories by clicking the expand all button ( ) at the top of the
page.
• Individual categories by clicking the expand button ( ) for that
category.
You can display the Verifier page by clicking on the name of the Verifier
whose information you want to display.
For more information. Refer to the Brix Reference Guide to learn more
about adding Verifier keys and BrixWorx licenses.
Editing a category To edit a category, click the edit button to display the fields for that
category. The categories are as follows:
Categories Description Reference

Verifier Network Lists the proxy host, the See “Verifier Network
Configuration proxy port, the default Configuration” on
domain, and the DNS servers. page 54.
Phone Directory Lists phone groups and phone See “Phone Directory”
directories on Verifiers that on page 55.
help to manage the resources
available in a mesh
environment.
Test Interface 1 Lists the Ethernet settings, the See “Test Interfaces” on
IPv4 or IPv6 settings, and the page 56.
IP alias settings.
Working with Advanced Parameters
Categories Description Reference

Test Interface 2 Lists the Ethernet settings, the See “Test Interfaces” on
IPv4 or IPv6 settings, and the page 56.
IP alias settings.
Static Routes Lists the Static routes See “Static Routes” on

configured for the Verifier. page 60.
Note: IPv4 static routes can
be configured from Brixworx
as well as from the Verifier
CLI. IPv6 routes can only be
configured from the Verifier
CLI.
Additional Services Lists the current settings of See “Additional
the additional services Services” on page 61.
parameters, for example,
status, tests, servers, and
services.
Advanced Lists the current settings of See “Advanced
Configuration the advanced configuration Configuration” on
parameters, for example, page 65.
bandwidth, timeout, transfer
size, and transfer rates.
Verifier Health Lists status information See “Verifier Health” on
specific to that Verifier page 67.
including the percentage of
the CPU the Verifier is using,
the amount of available
RAM, how many times the
Verifier is reset, even the
Verifier’s current operating
temperature. These fields
cannot be changed.
Verifier Lists management operations See “Verifier
Management such as, rebooting, shutting Management” on
down the Verifier, clearing page 70.
the flash memory, and forcing
the discovery of a collector.
Verifier Network Configuration

This section describes the fields in the Verifier Network Configuration
category of advanced Verifier parameters.
Parameter Description
Proxy Host The name of the host serving as an HTTP proxy for the
Verifier.
Proxy Port The port on which the proxy host accepts connections.
Default Domain The domain name to use as a suffix for DNS queries.
DNS Servers The IP addresses of DNS servers used for DNS queries.
Servers are used in the order specified.
How to specify a To specify a Verifier network configuration:

Verifier network
1 Click the edit button next to Verifier Network Configuration on the
configuration
2 Specify the:
• Proxy host
• Proxy port
• Default domain
3 In the DNS Servers field, type the name of the DNS server.
4 Click the Add button to add a server name to the list.
Note: To remove the servers, select the server name and click the Remove
button.
Phone Directory
Phone Directory
Using Phone Groups and Phone Directories on Verifiers helps to manage
the resources available in a mesh environment and also simplifies the
configuration of the PESQ Network Active test. Phone Directory entries
are stored in the Verifier’s Test Configuration File (TCF).
For more information. Refer to the BrixCall Advanced VoIP Reference

Guide for an example of a PESQ mesh environment that uses Phone
Groups.
EXFO Service Assurance recommends that you use Phone Groups when
configuring a mesh environment. The following steps must be taken to run
the PESQ Network Active test in a mesh environment while using Phone
Groups.
Step Task Where to Find More Information

1 Create a Phone Group. BrixWorx User Guide
2 Create a Phone Directory BrixWorx User Guide
entry and associate it with a
Phone Group.
3 Configure the PESQ BrixCall Advanced VoIP Reference Guide
Network Active test.
Test Interfaces
The BV-110 Verifier has two test interfaces that allow you to connect to
multiple networks. The Verifier Information page displays a separate
category for each test interface: Test Interface 1 and Test Interface 2.
Test Interfaces The Test Interface field descriptions are as follows:

fields
Parameters Description
Ethernet Speed Specifies the speed of the active Test port. On the
BV-110 Verifiers, the options are:
• 10M
• 100M
• 1000M
• auto
When you set the value to auto, the default setting on the
Verifier is used.
Test Interfaces
Ethernet Duplex Ethernet DuplexSpecifies the duplex mode of the Active
Test port. The options are:
• full duplex (available when Ethernet Speed is set to
10M, 100M, and 1000M)
• auto (available when Ethernet Speed is set to auto)
When you set the value to auto, the default setting on the
Verifier is used.
Maximum Specifies the Maximum Transmission Unit (MTU), in
Transmission Unit bytes, for the test interface. The default is 1500 bytes.
The MTU defines the maximum size of a packet that can
be transferred in one frame over a network. Optimizing
the MTU can improve network performance. For Linux
Verifiers, the MTU value can be from 68 to 9216. This
parameter is not available when the IPv4 Address
Method is set to one of the following:
• not set
• none
VLAN ID Specifies the VLAN ID associated with outgoing IPv4
test packets. This parameter is available when the IPv4
Address Method is set to:
• dhcp
• fixed
• no ip
VLAN Priority Specifies the VLAN priority associated with outgoing
IPv4 test packets. This parameter is available when the
IPv4 VLAN ID is specified.
Transceiver Specifies if the port is optical or electrical.
Each test port consists of a 1Gbps optical interface
through an SFP connector and an 10/100/1000Mbps
electrical interface with an RJ-45 connector.
IPv4 Address Specifies the method the Verifier uses to obtain the IP
Method address for its Management port:
• dhcp – The Verifier obtains its IP address using
Dynamic Host Configuration Protocol (DHCP).
• fixed – The Verifier uses the addresses specified for
the routing gateway, subnet mask, and DNS server
during bench configuration.
• no ip – The Verifier uses a fixed null address (0.0.0.0).
• none – Forces a configuration with no IP Address
Method setting.
IPv4 Address (CIDR) Specifies the IP address when the IPv4 Address Method
is set to fixed. The IPv4 address must be in CIDR
notation, for example, 192.168.0.0/16, appending a slash
character with the leading bits of the routing prefix.
IPv4 Gateway Identifies the default gateway to use to resolve Verifier
transmissions whose destinations are not on the Verifier’s
local network. This parameter is available when the IPv4
Address Method is set to fixed. The specified address
must be an IPv4 address that is in the same local subnet
as the specified IPv4 Address.
IPv4 Interface Associates the Verifier’s test interface with the selected
Category interface category. This parameter is available when
interface categories are defined and when the IPv4
Address Method is set to fixed, no ip, or dhcp. A specific
interface category can be used once per interface.
IPv4 Additional Allows you to specify one or more VLAN to be
VLANs associated with each IPv4 interface category selected.
The specified values are used to populate the VLAN test
parameters for tests provisioned on this Verifier and
configured to use the specified interface category. You
specify the VLAN ID and the VLAN priority for each
additional VLAN. This parameter is available if IPv4
interface categories are defined.
For more information. Refer to the BrixWorx User
Guide to learn more about associating VLAN with an
interface category.
IPv6 Address Specifies the address method used by IPv6-ready
Method Verifiers. This parameter is available if the IPv4 Address
Method is set to fixed, dhcp, or no ip. You can specify
one of the following IPv6 address methods:
• dhcp
• fixed
• none
IPv6 Address (CIDR) Specifies the IPv6 address when the IPv6 Address
Method is set to fixed. The IPv6 address must be in
CIDR notation, for example, 2001:db8::/32, appending a
slash character with the leading bits of the routing prefix.
IPv6 Gateway Identifies the default gateway to use to resolve Verifier
transmissions whose destinations are not on the Verifier’s
local network. This parameter is available when the IPv6
Address Method is set to fixed. The specified address
must be an IPv6 address that is in the same local subnet
as the specified IPv6 Address.
Test Interfaces
IPv6 Interface Associates the Verifier’s test interface with the selected
Category interface category. This parameter is available when
interface categories have been defined and when the IPv6
Address Method is set to fixed or dhcp. A specific
interface category can be used once per interface.
IPv6 Additional Allows you to specify one or more VLAN to be
VLANs associated with each IPv6 interface category selected.
The specified values are used to populate the VLAN test
parameters for tests provisioned on this Verifier and
configured to use the specified interface category. You
specify the VLAN ID and the VLAN priority for each
additional VLAN. This parameter is available if interface
categories are defined.
Guide to learn more about associating VLAN with an
interface category.
IP Alias Settings Enables you to configure multiple IP addresses for a
single network device. Each IP alias you create is
mapped to a fixed IP address that you configure in the IP
Address (CIDR) field. The maximum is 512 IP aliases
per Verifier. This parameter is available when the IPv4
Address Method is set to dhcp, fixed, or no ip and IPV6
Address Method is set to dhcp, fixed, or none.
Guide to learn more about creating IP alias.
Static Routes
This section describes the Static Routes category of the Verifier
Information Page. In this category, you can configure routes for the
Verifier’s IP interfaces and their IP aliases.
Only IPv4 static routes are configured in the BrixWorx Operations Center.
You can use the CLI to configure both IPv4 and IPv6 routes for Linux
Verifiers and view the routes in the Static Routes category of the Verifier
Information page. You cannot edit the routes.
Reference Guide to learn more about CLI.
How to specify a To specify a static route in the Static Routes category of the Verifier
static route Information page:
1 Click the edit button next to Static Routes on the Verifier Information
page.
2 In the Destination field, type the IP address or network address and
subnet mask (in CIDR format) for the Verifier route.
3 In the Gateway field, type the gateway IP address for the route.
4 In the Metric field, type the metric to be used by the routing algorithm
to evaluate equivalent routes.
5 Click the Add button.
The static route appears in the list box.
Additional Services
6 Repeat step 2 through step 5 for each additional static route you want
to configure.
Additional Services
This section describes the fields in the Additional Services category of
Note: Several parameters in the Additional Services category have Not

Specified as one of the options. The Not Specified option indicates that
the current setting on the Verifier is used. To check the actual settings of
the Additional Services parameters, you can expand the Additional
Services category.
Status Controls how often BrixWorx generates an automatic
report on the Verifier’s health. By default, the value is 1
minute.
For more information. See “Verifier Health” on
page 67 to learn more about Verifier health.
Ethernet Reflector Controls if the Verifier loads the Ethernet OAM
Test Reflector.
The Ethernet OAM Reflector passively listens for a
loopback, link trace, or frame delay message and returns
an appropriate message response.
NTP Service Allows you to specify one or more NTP (Network Time
Protocol) servers to use as a time source for the Verifier.
The following options are available:
• Not Specified
• Do not run
• Run with the following addresses
SNMP Service Allows network management stations to monitor
Verifiers using Simple Network Management Protocol
(SNMP).
• Not Specified
• Do not run
• Run with the following addresses
If you use this parameter, you can optionally specify a
community string used to authenticate the SNMP service
on the Verifier, as well as a system location and a system
contact for the SNMP Service.
SSH Service Allows you to enter Verifier (CLI) commands through
the Secure Shell (SSH) program. The SSH Service runs
on the Verifier.
• Not Specified
• Do not run
• Run
For more information, refer to the Brix Command Line
Interface Reference Guide to learn more about the SSH
service.
Additional Services
Telnet Service Allows you to enter Verifier (CLI) commands through
the telnet program. The Telnet Service runs on the
Verifier.
• Not Specified
• Do not run
• Run
For more information, refer to the Brix Command Line
Interface Reference Guide to learn more about the telnet
service.
Authentication Allows you to specify the way in which you want to
authenticate users trying to access the Verifier using the
Brix command line interface (CLI).
• Not Specified.
• Use the Verifier user list – The authentication defers
to the username/password list created for the Verifier
during bench configuration.
• Use RADIUS with these settings – RADIUS (Remote
Authentication Dial-In User Service) is an
authentication service used by many service
providers. You can enter the address, IP port, and
Shared Secret for the RADIUS server.
For more information see “Using RADIUS
authentication” on page 64.
How to specify an NTP server

To enter an address for the NTP server:
1 Select the Run with the following addresses radio button.
2 Type the DNS name or IP address of the NTP server.
3 Click the Add button to add a server name to the list.

Note: Servers can be removed by selecting the server name and clicking
the Remove button.
Using RADIUS authentication

To enable RADIUS authentication:
1 Click the Use RADIUS with these settings button.
2 Specify the:
• IP address of the RADIUS server.
• UDP port number to communicate with the RADIUS server.
• The shared secret between the client and the server (required for
authentication).
Note: The default username and password (admin/admin) override the
RADIUS username and shared secret. EXFO Service Assurance
recommends that you change these defaults when you enable RADIUS
authentication.
Advanced Configuration
Advanced Configuration
This section describes how to configure the advanced properties of the
BV-110 Verifier from the Verifier Information page.
Advanced This section describes the fields in the advanced configuration category of
configuration fields advanced Verifier parameters.
Active Testing The Active Testing Bandwidth parameter is used by the
Bandwidth SLA preflight process to check the load on the Verifier.
Available bandwidth is determined by the link type you
specified when adding the Verifier to BrixWorx.
For more information. Refer to the Brix Reference Guide to
learn more about adding Verifier keys, BrixWorx
licenses, and Verifier’s link type.
Reporting The percentage of available bandwidth allowed for
Bandwidth reporting test results to the collector.
Available bandwidth is determined by the link type you
specified when adding the Verifier to BrixWorx.
For more information. Refer to the Brix Reference Guide to
learn more about adding Verifier keys, BrixWorx
licenses, and Verifier’s link type.
Connection Timeout The amount of time in seconds over which the Verifier
attempts to contact BrixWorx before a timeout occurs.
Once a connection times out, the Verifier retries the
connection the number of times specified by the
Connection Retries value.
You do not have to specify s for seconds. You can enter
the number.
By default, the value is 60 seconds.
Connection Retries The number of times the Verifier attempts to connect to
BrixWorx after the connection has timed out. If the
Verifier exhausts the number of connection retries, the
system registers a connection failure on the Alerts page
of the BrixWorx Operations Center.
Polling Interval The amount of time in minutes (m) or seconds (s) the
Verifier waits before communicating with BrixWorx.
The default is 60 seconds.
The polling interval you set has an impact on how often
the following operations are performed:
• Results are reported.
• The Verifier checks for new Verifier Configuration
Files (VCFs), Test Configuration Files (TCFs), and
test modules.
Tip: You cannot mix units of time. Express the polling
interval in minutes or seconds, not both.
Max. Transfer Size The maximum number of bytes per packet for data sent
from the Verifier to the BrixWorx server.
By default, the value is 2048 bytes per packet.
Min. Transfer Size The minimum number of bytes per packet for data sent
from the Verifier to the BrixWorx server.
By default, the value is 2048 bytes per packet.
Max. Transfer Rate The average maximum transfer rate from the Verifier to
the BrixWorx server measured in bytes per second.
By default, the value is 10000000 bytes per second.
System Logging The level at which you want to log Verifier information.
Level The options are:
• Debug
• Minor
• Major
• Critical
• None
By default, the value is Minor.
Verifier Health
Verifier Health
This section describes the information you can display about a Verifier’s
current status by expanding the Verifier Health category on the Verifier
Information page. Every Verifier runs a test that provides status
information, including the percentage of its CPU it is using, the amount of
available RAM, how any times it has been reset, and its current operating
temperature. An example of a Verifier Health report is shown in the
following figure.
Name Description
CPU Usage The percent of the Verifier’s CPU currently in use.
Thread Info Active, idle, and maximum number of threads.
Total System Memory Size of RAM memory installed on the Verifier.
Memory Usage • System: Memory currently used by the kernel and by
all the application processes.
• Verifier: Memory currently used only by the Verifier
process.
Name Description
Swap File Usage • In use: Total amount of swap memory currently
used.
• Total: Total amount of swap memory installed.
Comm Bytes Sent/ Total number of COMM layer bytes sent and received.
Received
Comm Decryption The number of decryption errors that occurred
Errors decrypting HTTP in the COMM layer.
Comm Frames Total number of COMM layer frames received by the
Received Verifier.
Comm Frames Total number of COMM layer frames transmitted by
Transmitted the Verifier.
Monolith The identifier of the Verifier’s backup monolith.
TCF Version The version of the Verifier’s Test Configuration File
(TCF).
VCF Version The version of the Verifier’s Configuration File (VCF).
NTP Server Whether or not the Verifier is enabled as a Network
Time Protocol (NTP) server.
NTP Server Stratum The Verifier’s current stratum. This is always one more
than the stratum of the NTP server the Verifier’s using
as its reference. For example, if the Verifier’s using an
NTP stratum 2 server, the value shown in the NTP
Server Stratum field is 3.
An NTP time server’s stratum indicates the server’s
level of remove from a (theoretical) perfect time source
GPS receivers and atomic clocks, for example, are
stratum 0 devices. An NTP time server with one of
these devices attached to it is at stratum 1.
NTP Server List The list of NTP servers that the Verifier is configured
to use as a time source.
NTP Referring Server The NTP Server currently being used by the Verifier.
NTP Clock Drift The NTP clock drift of the Verifier.
Continuous Uptime How long the Verifier is running since it was first
brought online or since its last restart. Provided as both
a date/time and in elapsed time.
Number of Tests The number of tests currently loaded on the Verifier.
Loaded
System Temperature The Verifier’s temperature (in degrees Celsius and
degrees Fahrenheit).
Verifier Health
Name Description
FPGA Version The FPGA version number.
Current Time Source The time source currently in use:
• NTP
• Brix Time
Model Specific Health
Test Port 1 Details Details such as packets received and transmitted,
packets dropped in receiving and transmitting, errors in
receiving and transmitting, and port setting for test port
1.
Test Port 2 Details Details such as packets received and transmitted,
packets dropped in receiving and transmitting, errors in
receiving and transmitting, and port setting for test port
2.
Verifier Management
This section describes the Verifier Management page that allows you to
manage operations, such as, rebooting, shutting down, and forcing the
Verifier to discover a collector.
The description of the operations available from the Verifier

Management page is as follows:
Reboot The Verifier is rebooted. The Verifier initiates discovery;
if discovery is successful, the Verifier configuration
information is written to the Verifier.
Shutdown The Verifier is shut down and taken offline. It remains
offline until it is manually reset.
Clear Flash The Verifier’s flash memory is cleared. The Verifier
configuration information is written to the Verifier’s flash
memory the next time the Verifier polls its BrixWorx
server.
Discovery BrixWorx forces the Verifier to initiate the discovery
process. If discovery is successful, the Verifier
configuration information is written to the Verifier.
For more information. Refer to the BrixWorx User Guide to learn more
about Verifier management.
Verifier Attributes
Verifier Attributes
This section describes the Verifier Attributes. You can access this page
from the BrixWorx Operations Center menu after you have selected a
Verifier from the Verifier page. The Verifier Attributes page lists the
parameters for various tests that are available for the BV-110 Verifier.
The Verifier Attributes page allows you to specify the following

parameters:
Attribute Description
Geographic Latitude Specify the geographic latitude of this Verifier. The
value must be in decimal notation, for example, 43.00.
A Geographic Latitude value of 43.00 specifies a
location of 43 degrees north of the equator.
Geographic Longitude Specify the geographic longitude of this Verifier. The
value must be in decimal notation, for example, -76.30.
A Geographic Longitude value of -76.30 specifies a
location of 76 degrees 30 minutes west of the prime
meridian.
E-Mail Activity Tests
EMail to Address Specifies the mail address to which the mail delivery is
made. This must be of the form user@domain.
EMail from Address Specifies the mail address from which the mail
delivery has to be done. This must be in the form
user@domain.
IMAP Mailbox Specifies the mailbox from which the mail is retrieved.
IMAP Password Specifies the password for the mailbox from which the
mail is retrieved.
POP3 Mailbox Specifies the mailbox from which the mail is retrieved.
POP3 Password Specifies the password for the mailbox from which the
mail is retrieved.
Activity Tests for Management Port
Prefer Management If TRUE, use the Management port for peer-to-peer
Port for Peer-to-Peer control channel communications where possible. If the
Control Verifier does not have a management port then this
setting is not used. The defaults is Not Set.
H323 Activity Tests
H.323 Gatekeeper The IP address, DNS name, and (optionally) the UDP
Address RAS port number of the H.323 gatekeeper this Verifier
uses. The format used for Gatekeeper Address is IP
address or DNS name[:port]. The default port number
is 1720.
H.323 Gatekeeper If TRUE, the Gatekeeper Discovery procedure is
Discovery performed when attempting to connect to an H.323
Gatekeeper. If the H.323 Gatekeeper address is not
specified, auto-discovery is performed.
Local H.323 Source The local H.323 ID address used by this Verifier when
Address registering with an H.323 gatekeeper.
Local E.164 ID The local phone number used when registering with an
Address H.323 gatekeeper.
SIP Server Activity Tests
SIP User Name (For The SIP user name to use.
URL)
SIP Authentication The user name to use for SIP proxy authorization /
User Name authentication.
SIP Domain The DNS domain to use for a SIP test.
Verifier Attributes
SIP Password The password to use if the proxy server or registration
server requires authentication.
SIP Proxy Server The DNS or IP address (dotted decimal notation) of a
SIP proxy server used for outbound SIP messages. It
also includes a port number. The format of this
parameter is: hostname[:portNo] or
ipAddress[:portNo].
SIP Force Proxy If TRUE, SIP tests are forced to route all requests
associated with each call through the specified proxy
server. This causes the test to ignore any request route
or contact information contained in the final response
to the initial INVITE request.
SIP Enable If TRUE, SIP tests attempt to register themselves
Registration within the specified registrar domain through the
specified proxy server.
SIP Registrar Domain The name of the SIP client registration domain used
within registration requests.
SIP Registration Specifies the proxy registration refresh interval in
Interval seconds.
SIP Report Specifies if the SIP messages sent and received during
Transaction History a test are reported.
SIP Encrypt Audio Specifies if the audio RTP is encrypted prior to
transmission.
SIP Local URL A SIP URL used by this Verifier for the SIP Service
Tests.
MGCP/NCS Active Server tests
MGCP/NCS Call The IP address or DNS domain name of the MGCP/
Agent Address NCS Call Agent Server.
MGCP/NCS Test The first term to use for the name of local MGCP/NCS
Endpoint Name test endpoints.
MGCP/NCS Test The domain name to use for local MGCP/NCS test
Endpoint Domain endpoints.
Name
MGCP/NCS Test IP source CIDR address to use for the MGCP/NCS
Source IP Address packets for IP aliasing. The first IP address on the
Verifier that matches the CIDR is used as the Source IP
Address.
MGCP/NCS Diffserv Specifies the Type Of Service field for all MGCP/NCS
Codepoint message packets.
RTP Tests
RTP Passive Test Control Channel Port.
Control Channel Port
RTP Passive Test CIDR address of the host/net that is located on the
Local CIDR Network controller LAN whose connections will be measured.
RTP Passive Test Port Specifies the lower boundary of the destination RTP
Range Low Boundary port range to monitor on the controller Verifier
network.
RTP Passive Test Port Specifies the lower boundary of the destination RTP
Range High Boundary port range to monitor on the controller Verifier
network.
C HAPTER 6
CHOOSING A BV-110 VERIFIER

TIME SOURCE
This chapter describes how to choose a time source for the BV-110
Verifier, and how to set up a Verifier as an NTP client.
All Brix Verifiers have internal clocks used for timestamping packets.
This chapter also describes the available time sources, and provides
information about using an NTP time receiver to set a Verifier’s clock.
Section Page
Available Time Sources 77
Whether to Use NTP 78
Chapter 6, Choosing a BV-110 Verifier Time Source
Introduction
The time is set and maintained by two time sources:
• NTP Time
• Default Time (Brix Time)
The BV-110 Verifier uses the time source that has been configured. GPS
and CDMA time sources are not supported.
The time is read from the FPGA on the BV-110’s NIC time-stamping
module. Time is used by various tests in the system. The packets that are
received and transmitted from the Verifier are marked with a time stamp.
This time stamp is provided by the BV-110’s NIC time-stamping module.
This timestamp value is a 64-bit value in nanoseconds.
When the Verifier is first installed, it reads the initial time from the
battery-operated CMOS. The first time source to provide the Verifier with
a time is the time source that is used by the Verifier.
Three internal There are three internal clocks available on the BV-110 Verifier:
clocks
• Linux Kernel Clock:
This is the same as the system clock. Linux uses the system clock to
get the time.
• FPGA Time Stamp Clock:
This clock is also known as Synchronized Clock or Primary
Timestamp Clock (PTC). This clock uses Brix Time or NTP server
time source. This clock can be used for measurements that require
external time synchronization, for example, one-way latency testing.
• FPGA Free Running Clock:
This clock can be used for short duration measurements that do not
require external time synchronization. The free running clock or
Uptime Counter (UC) cannot be changed.
Chapter 6, Choosing a BV-110 Verifier Time Source 77
Available Time Sources
Available Time Sources

There are two types of time sources available for the BV-110 Verifier:
• Network Time Protocol (NTP)
• Default time (Brix Time)
NTP Servers
You can configure the BV-110 Verifier to use one or more NTP servers as
a time source. You can also configure a Verifier as an NTP server and
create other Verifiers in your system as NTP clients of that Verifier.
For more information. See “Whether to Use NTP” on page 78 to learn
more about using NTP.
Default Time
The default time is supplied by the Verifier’s Local Registry. Default time
is passed to the Verifier as part of the discovery process. It requires no user
configuration.
The BV-110 Verifier uses default time in the following conditions:
• When the Verifier is first installed and added to BrixWorx.
• When the Verifier’s Time Receiver configuration is set to None and
NTP is not enabled.
Chapter 6, Choosing a BV-110 Verifier Time Source
Whether to Use NTP

If each BV-110 Verifier is installed to monitor separate calls, BrixWorx
time can be sufficient as a time source.
To accurately correlate monitored calls across multiple Verifiers, NTP is
the recommended time source for the BV-110 Verifier.
For more information. Refer to the BrixWorx User Guide for
information on NTP and how the NTP clients work.
C HAPTER 7
TROUBLESHOOTING
This chapter describes possible solutions to problems with installation and

configuration of the BV-110 Verifier.
Section Page
Resources 80
Useful Procedures 82
How to Analyze and Correct Problems 92
Chapter 7, Troubleshooting
Resources
This section describes where to find information that can help you
diagnose and troubleshoot Verifier problems as well as corrective actions
that you can take.
LEDs You can use the Status LED indicators to discover the operational status
for the BV-110 Verifier as follows:
• Successful discovery
• Successful POST and BrixWorx server contact initiation
• Power-On-Self-Test (POST)
• POST failure
• Bench configuration
• Offline
• No power
For more information. See “LED Behavior Descriptions” on page 82 to
learn more about interpreting the LED indicators.
Log files You can trace the communication between the Verifier and BrixWorx
server using the Verifier server log, the discovery log, and the Web Agent
log.
For more information. See “Check the Log Files” on page 86 to learn
more about log files.
Verifiers page The Verifiers page of the BrixWorx Operations Center displays a
summary of status information for all the Verifiers in the BrixWorx
system.
For more information. See “Adding a Verifier to BrixWorx” on page 42
to learn more about Verifiers.
Operations center The Verifier Information page of the BrixWorx Operations Center
Verifier Information displays and lets you modify detailed information about a specific
page Verifier.
For more information. See “Verifier Information page” on page 97 to
learn more about Verifier page.
Brix CLI The Brix command line interface (CLI) has several commands that let you
identify Verifier problems.
For more information. See “Connectivity Problems” on page 93 to learn
more about connectivity problems with the Verifiers.
Chapter 7, Troubleshooting 81
Resources
System page The System page of the BrixWorx Operations Center displays status
information about the BrixWorx servers you have configured to perform
the roles of consolidator, collector, and discovery hosts. For more
information. refer to the BrixWorx User Guide to learn more about the
System page.
Utilities BrixWorx provides utilities that allow you to display current information
about a Verifier, including:
• verifier-util (operation show-verifier and operation
listverifierprobes)
• view-verifier-status
For more information. Refer to the Brix Reference Guide to learn about
the BrixWorx utilities.
Useful Procedures
This section describes useful procedures for troubleshooting Verifier
problems.
Topic Page
LED Behavior Descriptions 82
Check the Connection to BrixWorx 83
Force Discovery 84
Reboot the Verifier 84
Clear the Verifier’s Flash Memory 86
Check the Log Files 86
Check Verifier Cables and Serial Port Configuration 89
Stop and Restart BrixWorx 89
Verify that BrixWorx is Running 90

The LED indicator descriptions and behavior for the BV-110 Verifier are
as follows:

Status Off Powered off
Solid amber Powering up
Blinking green (1 second on, 1 IP acquisition
second off)
Blinking green (0.5 second on, BrixWorx discovery
0.5 second off)
Solid green Operational
Link/Act Solid Green Valid Ethernet link
Check the Connection to BrixWorx

Duplex Solid Amber Valid Ethernet link at:
• 10M full duplex
DC Power Solid green DC power
Off No DC power
Blown fuse
Check the Connection to BrixWorx

When power is supplied to the Verifier, it attempts to connect to the
BrixWorx server. The Status LEDs are active as the Verifier conducts a
self-diagnostic procedure and establishes communication with the
BrixWorx server. The Verifier is operational after discovery.
The Verifier typically communicates with the BrixWorx server through
HTTP using port 80.
Several network variables can affect these installation and communication
processes, for example:
Firewall settings The Verifier communicates with the BrixWorx server through HTTP. By
default, the port is configured to 80, but you can change it during
configuration. If there is no connectivity from the Verifier to the BrixWorx
server using HTTP, then the discovery process fails.
Route setting If you have configured invalid routes between the Verifier and the
BrixWorx server, the installation fails. Check your configured routes for
accuracy.
Web Agent failure If there is no Web Agent running at the IP address that the Verifier is
connecting to, the process fails. For more information. See “Stop and
Restart BrixWorx” on page 89 to learn more about starting and stopping
BrixWorx.
Force Discovery
If a Verifier is connected to BrixWorx, you can manually force a Verifier
to perform a discovery using the discovery operation. By using force
discovery you can check if the Verifier is communicating with BrixWorx.
You can also use it to ensure that your Verifier has the most up-to-date
information (for example, Verifier configuration, test configuration, and
monolith version).
The discovery operation is accessible from the Brix Management section
of the Verifier Information page in the BrixWorx Operations Center.
For more information. See “Verifier Information page” on page 97 to
check if the Verifier has re-established communication with the network.
Reboot the Verifier

Rebooting a Verifier is the process of restarting a Verifier if your Verifier
has lost communication with BrixWorx. The Verifier goes through the
discovery process. The Verifier configuration and test configuration in the
Verifier’s flash memory is updated.
To reboot a Verifier, use any of the following methods:
• The Reboot operation in the BrixWorx Management section of the
Verifier Information page. This operation requires that the Verifier is
connected to BrixWorx, in order to apply the changes.
• The CLI reboot command.
• The Reset button on the Verifier’s back panel. Press and release the
Reset button to reboot the Verifier.
For more information. See “Comm layer error codes” on page 94 to
check if the Verifier has re-established communication with BrixWorx.
If the Verifier is not communicating with BrixWorx, clear the Verifier’s
flash file system.
For more information. See “Clear the Verifier’s Flash Memory” on
page 86 to learn more about clearing the Verifier’s flash memory.
Booting into factory When you boot the Verifier to the factory settings, the default IP
default settings configuration is as follows:
1 DHCP configured for all interfaces.
2 DHCPv6 is disabled.
3 No fixed routes.
4 No fixed domain name is configured, no fixed DNS servers.
5 Telnet is disabled.
Reboot the Verifier
6 SSH is disabled.
7 New ssh keys to be generated on the first boot-up.
8 SNMP is disabled.
9 Radius is disabled.
10 Alert level and log level is set to informational.
11 NTP is disabled.
12 All levels have empty server discovery list – local, network, and
universal.
13 Server communications settings are as follows:
• comm-port: 80
• http-proxy host: none
• http-proxy port: 80
• max-rate: 10000000
• default size: 4096
• polling-interval: 60s
• retries: 5
• timeout: 60s
14 The following items are erased:
• The running configuration
• The TCF
• The locally stored plug-ins
• The bench configuration
• The modified passwords
• The ssh keys
Clear the Verifier’s Flash Memory

When you clear a Verifier’s flash memory, it loses all the information
stored in the Verifier configuration file (VCF) and test configuration file
(TCF), as well as individual test modules that are downloaded to the
Verifier. Current VCF, TCF, and test module information is written to the
Verifier the next time the Verifier polls the BrixWorx server.You can clear
the flash file system using any of the following techniques:
• The Clear Flash operation in the BrixWorx Management section of the
• The Reset button on the Verifier’s back panel. Press the Reset button
for five seconds and then release to reboot the Verifier. On a five
second reset operation, the BV-110 Verifier’s locally-cached files are
erased, including the TCF, the plug-ins, and the VCF. The factory
default settings are not restored because the bench configuration is not
erased.
For more information. See “Operational Problems” on page 95 to check
if the Verifier has re-established communication with the network.
If the Verifier is still not communicating with BrixWorx, check the
BrixWorx server.
For more information. See “Comm layer error codes” on page 94 to
learn more about comm error codes.
Check the Log Files

The following log files provide information about Verifier operations and
communications:
• The Verifier log file
• The Web Agent log file
Logging levels
The Verifier log file can record several levels of detail. You can increase
the logging level using the log-level <level> registry-agent/
communications command. The different levels are as follows:
• Info Level (default) – Logs discovery related messages, re-key
messages, online, and offline events.
• Debug Level – Logs information level data and also records each sent
or received comm segment.
• Trace Level – Logs the comm opcodes inside each segment along with
debug and info level messages.
The log level is persistent across Verifier reboots.
Check the Log Files
Verifier log
The Verifier log file contains information about discovery-related
messages, sent and received comm segments. The time displayed
represents the number of seconds since the Verifier was booted.
Access From the Verifier CLI, type show log at the root level.
Example The discovery section of the Verifier log (part of the information level)
displays the discovery related messages. For example:
03-15-2011 17:38:55 : INFO : Disc reply U KLNX.PALAB.TRINET.COM,10.17.11.10
03-15-2011 17:38:55 : INFO : Disc reply N KLNX.PALAB.TRINET.COM,10.17.11.10
03-15-2011 17:38:55 : INFO : Disc reply L KLNX.PALAB.TRINET.COM,10.17.11.10
03-15-2011 17:38:55 : INFO : Finish discovery -> KLNX.PALAB.TRINET.COM:2000
03-15-2011 17:38:55 : INFO : Lookup host 'KLNX.PALAB.TRINET.COM' ->
10.17.11.10
03-15-2011 17:38:55 : INFO : Transmit key
03-15-2011 17:38:55 : INFO : Receive key
03-15-2011 17:38:55 : INFO : Discovery success
03-15-2011 17:38:55 : INFO : Entered online state
03-15-2011 17:38:55 : INFO : Received chime, time delta -0.907960
03-15-2011 17:38:55 : INFO : Chime time delta -0.907960 - adjtimex status 5
(Success, 0) old offset 0.000000 usec
Web Agent log

Every Verifier’s discovery and boot sequence is logged in the Web Agent
log file. You can search for the serial number of the specific Verifier. The
file webagent.log is located in the $BX_ROOT/log directory on the
server.
Example The portion of a Web Agent log displays the discovery-related messages
and boot sequences.
[tri@elvis log] $ tail webagent.log
webagent : Wed Aug 22 11:54:48 2012 : DEBUG : 400A50008720: New incoming
server session
webagent : Wed Aug 22 11:54:48 2012 : INFORMATION : 400A50008720: Receive key
webagent : Wed Aug 22 11:54:48 2012 : INFORMATION : 400A50008720: Transmit key
webagent : Wed Aug 22 11:54:48 2012 : INFORMATION : 400A50008720: discovery
request
webagent : Wed Aug 22 11:54:48 2012 : INFORMATION : 400A50008720: L-registry
discovery
webagent : Wed Aug 22 11:54:49 2012 : DEBUG : Reading module
com.trinet.tcpechoserver.1.5720...
webagent : Wed Aug 22 11:54:49 2012 : DEBUG : Reading module

com.trinet.udpechoserver.1.5720...
webagent : Wed Aug 22 11:54:49 2012 : INFORMATION : 400A50008720: Discovery
returns data
webagent : Wed Aug 22 11:54:50 2012 : DEBUG : 400A50008720: Connection closed
by far end
webagent : Wed Aug 22 11:54:50 2012 : DEBUG : 400A50008720: New incoming
server session
webagent : Wed Aug 22 11:54:50 2012 : INFORMATION : 400A50008720: Receive key
webagent : Wed Aug 22 11:54:50 2012 : INFORMATION : 400A50008720: Transmit key
webagent : Wed Aug 22 11:54:51 2012 : DEBUG : 400A50008720: verifier poll
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: hardware config
handler
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: log event handler
webagent : Wed Aug 22 11:54:52 2012 : INFORMATION : 400A50008720: verifier log
event has an unreasonable timestamp 303391824000 - estimating event time
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: log event,
verifier = 1027 subsystem = bxinformational instance = null msg = 45 alarm = 2
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: ip interface
handler
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: Request LCF 'L2'
for VCF merge
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: sent chime
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: lcf response
handler
webagent : Wed Aug 22 11:54:52 2012 : DEBUG : 400A50008720: Request default
LCF for VCF merge
webagent : Wed Aug 22 11:54:53 2012 : DEBUG : 400A50008720: lcf response
handler
.
.
.
webagent : Wed Aug 22 11:59:45 2012 : DEBUG : 400A50008720: received 1
com.trinet.ntppassivetest.1.4880 report TS(Wed Aug 22 11:52:02 2012)
com.trinet.pingactivetest.10.3260 report TS(Wed Aug 22 11:52:29 2012)
com.trinet.ntppassivetest.1.4880 report TS(Wed Aug 22 11:52:33 2012)
Check Verifier Cables and Serial Port Configuration
Check Verifier Cables and Serial Port Configuration

If you have a problem powering up the Verifier, check all cable
connections and the serial port configuration.
For more information. See “Connecting the Ports” on page 27 to learn
more about connecting ports.
Stop and Restart BrixWorx

If no Verifier is communicating with the BrixWorx server, stop the
BrixWorx server and restart it.
Note: If you have configured a Web Agent to run on port 80 or to use the
IP SLA, you must stop the Web Agent before you stop the BrixWorx
Server. Restart the Web Agent after restarting BrixWorx.
Stopping the Web To stop the Web Agent:
Agent
1 Log on as the brix user.
2 Change to the directory in which you installed BrixWorx.
3 If necessary, set up your UNIX environment using one of the following
login scripts depending on your shell:
• ../bxlogin.sh, or
• source bxlogin.csh
4 Enter the following command:
bxworxroot.sh stop
Stopping the To stop the BrixWorx server:

BrixWorx server
3 If necessary, set up a UNIX environment using one of the following
bxworx.sh stop
Starting the To start or restart the BrixWorx Server, ensure that the parameters in
BrixWorx server sys.conf are configured correctly and perform the following steps:
For more information. refer to the Brix Reference Guide to learn more
about sys.conf parameters.
bxworx.sh start
Starting the Web To start the Web Agent:

Agent
bxworxroot.sh start
Verify that BrixWorx is Running

To verify that BrixWorx and its associated daemons are running properly,
check the System page in the Operations Center for a fail message to
identify the problem and the failing daemons.
For more information. See “Operational Problems” on page 95 to learn
more about operational problems.
If there are problems with the BrixWorx Server or its daemons, stop and
restart the BrixWorx server.
CLI commands You can check the following information using the command line:
• If all BrixWorx daemons are running
• If the Web server is running
• If the SNMP Master Agent is running
Verify that BrixWorx is Running
How to use the To run these checks from the command line:
command line
1 Log on as the user.
2 Change to the appropriate directory.
3 If required, set up a Unix environment using one of the following login
scripts depending on your shell:
ps -ef | grep argument
The argument varies based on what you want to check.
To Check This Use This Argument

daemons bx
Web server httpd
SNMP Master Agent snmp

How to Analyze and Correct Problems

This section describes how to analyze and solve problems related to
hardware, connectivity, and operational issues.
Topic Page
Hardware Installation Problems 92
Connectivity Problems 93
Operational Problems 95
Hardware Installation Problems

Some problems can occur during installation of the Verifier. The
following sections describe some of the problems and their solutions.
No BIOS messages displayed

The Verifier is powered on, and there are no BIOS messages displayed on
the serial terminal, you can do the following:
• Ensure that you have used the correct serial cable.
• Ensure that the serial cable is plugged into the Console port on the
back panel of the BV-110 Verifier.
• Ensure the serial port terminal is configured for 9600 baud rate 8-N-1.
If none of these situations apply, you can try the following operations:
• Power cycle the system and check the status LED on the front or back
panel of the BV-110. The status LED blinks green at a one second rate
until the Verifier acquires an IP address. The status LED blinks green
at a half second rate until the Verifier connects with the BrixWorx
registry. When the status LED is solid green, the Verifier is operational.
If the status LED is not green, the Verifier has failed. Contact EXFO
Service Assurance for assistance.
• If the BIOS messages are displayed on the serial terminal, and the
system does not boot at the login prompt, it is possible that the Verifier
is configured to point to a BrixWorx server that has downloaded a
corrupt monolith. Check the BrixWorx monolith version and
reconfigure a new monolith, if required. With the new monolith
configured on BrixWorx, reboot the Verifier. At the GRUB boot menu,
press Escape at the serial port. Select Brix Verifier Recovery to boot
the Verifier into the secondary partition to trigger a download of its
monolith.
Connectivity Problems
Console error
If the console displays an error when you try to start the BrixWorx server,
it is possible that you have not logged on properly or have not configured
the environment properly. Ensure that BrixWorx and its associated
daemons are running properly. If there are problems with the BrixWorx
server or its daemons, stop and restart the BrixWorx Server.
For more information. See “Stop and Restart BrixWorx” on page 89 to
learn more about starting and stopping BrixWorx.
Check the Status and Message columns of the System page on the
BrixWorx Operations Center. If the Status is Fail, the message identifies
the problem, including which daemons, if any, are failing.
Connectivity Problems
You can have connectivity problems with Ethernet and network
connections. The communication between the Verifier and the BrixWorx
server can be traced by using the Web Agent log file located on the server
that is running the Web Agent.
For more information. See “Check the Log Files” on page 86 to learn
more about log files.
Server discovery
When the Verifier boots up, it attempts to discover a BrixWorx server. The
Verifier maintains a list of servers and moves through the list until it
successfully discovers one of the servers on its list. The server list is
defined during the bench configuration process.
For more information. See “Force Discovery” on page 84 to learn more
about force discovery.
The server can redirect the Verifier to another server. The Verifier attempts
to connect to the new server. This process continues until the Verifier
successfully connects to a server.
Loss of connectivity Once the Verifier is connected to a server, it must stay permanently
connected to the server. The Verifier can lose connectivity to the server
due to the following reasons:
• The server’s Web Agent is stopped.
• Network connectivity is lost.
• The HTTP proxy failed.
• The server’s database is full and no more test results can be written to
the database.
• A transmit or receive timeout is triggered in the comm layer. For

example, the Verifier is downloading a large TCF file and is unable to
receive the next TCF segment within the expected timeout.
If the Verifier loses connectivity to the server, it attempts to reconnect
to the server. Some reasons for transmit and receive time-outs in the
comm layer are:
• Network packet loss requires TCP to retransmit packets, or requires
the TCP connection to be closed and reconnected.
• The HTTP proxy is very slow.
Comm layer error The comm layer can report numeric error codes in the Web Agent log or
codes on the Alerts page. The list of the error codes and their descriptions are as
follows:
Error code number Error code meaning

0 Success
1 No resources
2 Timeout
3 Invalid parameter
4 Invalid handle
5 Bad hostname
6 Network error
7 Close after connect if >= 4.0.0
8 Data handle open
9 Authentication failure
10 Unexpected error
11 Bad parameter
12 Transmit rate exceeded
13 Transmit queue full
14 Incompatible comm layer version
15 Verifier not connected
Operational Problems
There are several ways that the Verifier can indicate operational problems.
This section describes the indicators associated with certain problems and
some solutions.
Looking for indications

Following are some of the indicators for problems with a Verifier or
network communication:
• An increase in No Data status for the SLAs and services associated
with a Verifier.
• Warnings on the Alerts page, for example, Keep Alive and other
warnings that identify problems.
• The date and time of the last report is older than the test’s polling
interval permitted.
Tip: By default, the polling interval is one minute.
• The Verifier Health section of the Verifier page indicates problems
displayed in the following fields:
• The Continuous Uptime field shows how long the Verifier has been
running since it was online or since it was last reset.
• The Number of Resets field identifies the number of times the
Verifier is reset.
No data or old test results

If there is no recent activity data for the Verifier, it can be due to a network
failure or a Verifier being offline. It can also indicate that the BrixWorx
auditor is not active.
The auditor The BrixWorx auditor function (also called the Auditor) performs the task
of determining Verifier status. The auditor function is on the BrixWorx
server and acts as a consolidator.
For more information. Refer to the BrixWorx User Guide to learn more
about the auditor function.
Corrective actions
If the Verifier has stopped communicating with the network, perform the
tasks in the following order:
1 Force discovery.
For more information. See “Force Discovery” on page 84 to learn more
about force discovery.
2 Reboot the Verifier.
For more information. See “Reboot the Verifier” on page 84 to learn
more rebooting the Verifier.
3 Clear the Verifier’s flash file system.
For more information. See “Clear the Verifier’s Flash Memory” on
page 86 to learn more about clearing the Verifier memory.
LEDs troubleshooting summary

The following table summarizes some of the LED diagnostic and
corrective procedures available:
Possible
Symptom Problem Actions
Status LED is off. Power is not Ensure that the power cord is
supplied to the secure and the Verifier is
Verifier. receiving power.
If the Verifier is receiving power,
and the status LED is off, contact
EXFO Customer Support.
Status LED blinks The Verifier cannot Perform the following tasks:
green; never goes discover a registry. • Ensure that you have correctly
solid green. installed the Verifier keys on
BrixWorx, and the Verifier is
added to BrixWorx Verifier
page.
• Check the Alerts page for
relevant information.
• Ensure that the Verifier is
bench configured with the
correct BrixWorx server IP
address and port.
• Ensure that the Verifier test
interface is connected and that
the Ethernet link is up.
Verifiers page
The Verifiers page of the BrixWorx Operations Center displays summary
status information for all Verifiers in your BrixWorx system.
Last Report column The Last Report column can display no value or a value that, compared
with the current time of the day, is older than the Verifier’s polling
interval. This indicates that the Verifier has lost communication with
BrixWorx.
For more information. See “Check the Connection to BrixWorx” on
page 83 to learn more about BrixWorx connection.
Verifier Information page

The Verifier Information page of the BrixWorx Operations Center
displays and lets you modify information for a Verifier.
The Verifier Health The Verifier Health page provides status information about a Verifier’s
section attributes, and configuration. The status information is sent from the
Verifier to the server and is updated at a specified interval.
Finding Errors Using the CLI

The command line interface (CLI) has several commands that can help
you troubleshoot Verifier problems and provide diagnostic information:
• ping and traceroute – Attempts to reach the host you specify and
allows you to determine if a host is reachable.
• show system communications – Displays the Verifier’s current network
communication settings.
• show system log – Displays a log of activity on the Verifier. The log
starts when the Verifier discovers a registry.
• show interfaces – Displays the current settings and status of the
Verifier’s test ports.
• show running-config – Displays the system VCF configuration. For
example, it displays that DHCP is enabled but does not display the
acquired addresses.
• show bench-config – Displays the Verifier’s current bench
configuration settings.
• show statistics – Displays information about the Verifier’s current
physical condition including CPU usage and temperature.
Reference Guide to learn more about CLI commands.
A PPENDIX A
BV-110 CLI COMMANDS
This appendix lists the BV-110 CLI commands. Refer to the Brix
Command Line Interface Reference Guide for a complete description of
the Brix CLI commands.
In this appendix This appendix has the following section:
Section Page
CLI Commands 96
BV-110 CLI Commands
CLI Commands
The Brix command line interface (CLI) is a tool that lets you configure
and manage Brix Verifiers.
• On a console that is connected directly to the Verifier.
• From a telnet (all Verifiers) or Secure Shell (SSH) session.
With the CLI, you can change a Verifier’s default settings using a process
called bench configuration, or you can change the Verifier parameters in
the BrixWorx Operations Center.
CLI modes The CLI has four user modes:
• EXEC – The default user mode that lets you view Verifier information
and perform basic network commands, such as pinging a network
address.
• Privileged EXEC – This user mode has all the functions of EXEC
mode. In addition, privileged EXEC mode allows you to perform some
Verifier operations, such as starting and stopping the Verifier, taking
the Verifier offline, and clearing the Verifier’s flash memory.
• Global configuration – This user mode lets you change the Verifier’s
configuration – add users, change the Verifier’s IP acquisition method,
change the speed of the active test and management ports, and so on.
• Bench configuration – This mode lets you bench configure the Verifier
– specify the discovery list, the BrixWorx communications settings, IP
information, and static routes.
For more information. See the Brix Command Line Interface Reference
Guide for detailed information.
BV-110 CLI Commands 101
CLI Commands
BV-110 CLI The following table provides an alphabetical list of the BV-110 CLI
commands commands and the modes in which they are available:
Command Description Command Modes

? Displays context-sensitive help. You can type a Global
question mark (?) at the user prompt, at the end of a configuration
command or subcommand, or in the middle of a
command or subcommand.
acquisition Sets the type of IP address acquisition method to use for • Global
the port: dhcp, fixed, or none. This command is configuration
available from the interface global configuration and • Bench
bench configuration submodes. For example: configuration
> enable
# configure terminal
(config)# interface ethernet 0
(config-eht0)# acquisition fixed
address The IP address for the ethernet port and the associated • Global
subnet mask.The value must be in Classless Inter- configuration
Domain Routing (CIDR) notation in which the IP • Bench
address is entered in dotted-decimal notation followed configuration
by a slash (/) and the number of bits in the subnet mask.
This command is available from the interface global
configuration and bench configuration submodes. See
“acquisition” on page 101 for an example of the
menu path.
alert-level Specifies the alert level for filtering alerts. • Global
configuration
• Bench
configuration
bench-cfg Allows the user to access the bench configuration • Privileged EXEC
mode. You must be in the Privileged EXEC mode to
execute this command.
cancel changes Cancels any changes made to the current configuration • Privileged EXEC
that have not already been saved using the write • Global
command. configuration
• Bench
configuration
configure terminal Allows the user to access the global configuration • Privileged EXEC
mode. You must be in privileged EXEC mode to
execute this command.
device-name Changes the name of the Verifier. • Global
configuration
• Bench
configuration
disable Turns off the privileged EXEC mode commands. Privileged EXEC
BV-110 CLI Commands

duplex Sets the duplex mode for the ethernet port: auto, half, or • Global
full. This command is available from the interface configuration
global configuration submode. For example:
> enable
(config-eht0)# duplex full
enable Takes the user from the EXEC mode to the privileged EXEC
EXEC mode. Displays a prompt for a password
(password:) after the command is executed.
end Exits global configuration mode or bench configuration • Bench
mode and allows the user to access the privileged configuration
EXEC mode. • Global
Configuration
erase bench-cfg Clears the bench configuration settings in the Verifier’s Privileged EXEC
flash file system. The running configuration of the
Verifier is not changed until you clear the Verifier’s
flash file system, which resets the Verifier.
erase cache Reverts running configuration to bench configuration Privileged EXEC
and erases locally-cached test configurations and plug-
ins.
erase running-cfg Clears the Verifier’s running configuration and resets Privileged EXEC
the Verifier.
erase ssh-remote-keys Erases all known ssh remote host keys. Privileged EXEC
erase tcpdump- Erases tcpdump capture files. Privileged EXEC
capture-file
exit Exits the current mode and allows the user to access the All
previous mode. For example, from the global
configuration or bench configuration mode to
privileged EXEC mode, from privileged EXEC mode
to EXEC mode, and from EXEC mode, out of the CLI.
grep Searches for lines matching a pattern and prints them. • EXEC
The grep CLI command reads a list of files or standard • Privileged EXEC
input and searches for lines of text that match one or
many regular expressions and displays only the
matching lines.
help Displays general and context-sensitive help. All
interface Sets the interface configuration mode to: • Bench
• ethernet or configuration
• wireless • Global
Configuration
• Subcommand
CLI Commands

ip Enters the IP configuration subcommands. See “[no] ip • Bench
domain-name” on page 103 to learn more about IP. configuration
• Global
Configuration
ipv6 Enters IP version 6 configuration mode. You can Global
configure acquisition, alias, address, default gateway, Configuration
and so on.
less Displays the contents of a file. • EXEC
• Privileged EXEC
log-level Specifies the log level for filtering alerts. • Bench
configuration
• Global
Configuration
logout Logs the user out of the Verifier. All
mtu Sets the interface Maximum Transmission Unit (MTU). Global
The range for MTU is 68 - 9216. Configuration
[no] alias Configures an alias for the interface. It also allows you • Global
to set a default gateway or VLAN ID. This command is configuration
available from the interface global configuration • Bench
submode. For example: configuration
> enable
(config-eht0)# alias 10.10.20.30/35
[no] default-gateway Configures or negates the address of the IP gateway to • Global
use for the ethernet port. This command is available configuration
from the interface global configuration submode. For • Bench
example: configuration
> enable
(config-eht0)# default-gateway 10.10.20.30/35
[no] device-name Configures the name of the device or removes the • Global
specified device. configuration
• Bench
configuration
[no] ip domain-name Creates or deletes the default domain name used for any • Global
host that is configured without a domain. configuration
• Bench
configuration
[no] ip name-server Adds or deletes the IP address of a DNS server from a • Global
list of DNS servers for the Verifier. The DNS server list configuration
can contain a maximum of three entries. • Bench
configuration
BV-110 CLI Commands

[no] ntp server Adds or removes an NTP server from the Verifier. The • Global
NTP server can be specified using an IP address or configuration
DNS name. • Bench
configuration
[no] ntp service Enables or disables NTP for the Verifier. Global
configuration
[no] password Creates or deletes the enable password required by the Global
users to enter the privileged EXEC mode. There is one configuration
enable password for all users. If you delete the enable
password, the default enable password reverts to null.
[no] server The IP address or DNS name of the proxy server • Global
communications http- through which HTTP requests are routed. configuration
proxy host • Bench
configuration
[no] server The port on the HTTP proxy host to use for HTTP • Global
communications http- requests. configuration
proxy port • Bench
configuration
[no] server discovery The IP address or DNS name of the Verifier’s Local • Global
local Registry. configuration
• Bench
configuration
[no] server discovery The IP address or DNS name of the Verifier’s Network • Global
network Registry. configuration
• Bench
configuration
[no] server discovery Specifies a universal discovery host through its name or • Global
universal IP address. configuration
• Bench
configuration
[no] snmp community Sets or removes the SNMP community string. • Global
configuration
• Bench
configuration
[no] snmp manager Adds or removes the SNMP Manager Client. If you • Global
want the Verifier to send SNMP traps, you must configuration
configure one or more SNMP Managers to receive the • Bench
traps. configuration
[no] snmp service Enables or disables SNMP. • Global
configuration
• Bench
configuration
CLI Commands

[no] snmp system- Sets or removes the SNMP system contact using the • Global
contact contact information. configuration
• Bench
configuration
[no] snmp system- Sets or removes the SNMP server system location. • Global
location configuration
• Bench
configuration
[no] snmp trap-count Sets or removes the maximum number of traps to send • Global
within a trap interval. configuration
• Bench
configuration
[no] snmp trap- Sets or removes the trap interval time (in seconds). • Global
interval configuration
• Bench
configuration
[no] terminal Sets Verifier authentication to the Verifier’s user list or • Global
authentication RADIUS. configuration
• Bench
configuration
[no] terminal radius Configures the RADIUS server for Verifier • Global
authentication, which includes the following fields: configuration
port, server, and shared-secret. • Bench
configuration
[no] terminal ssh Enables or disables SSH access for the Verifier. You • Global
can enable or disable SSH on both ports (eth 0 or eth 1). configuration
If you do not specify a port, or if you use any argument, • Bench
SSH is enabled on both the Verifier’s ports. configuration
[no] terminal telnet Enables or disables telnet access. Global
configuration
[no] usb-device Disables or enables a USB device from the Wireless • Global
<device-name> Interface subcommand level. For example: configuration
> enable • Bench
# configure terminal configuration
(config)# interface wireless 0
(config-wireless0)# usb-device <device name>
[no] username Creates or deletes a user on the Verifier’s user list. Global
configuration
[no] vlan Configures a VLAN ID and an optional priority on an Global
interface. configuration
nslookup Sends a query for the IP address of a specified host. You • EXEC
can also use a specified DNS server. • Privileged EXEC
BV-110 CLI Commands

ntp NTP configuration subcommands. • Global
configuration
• Bench
configuration
ntpq ntpq is a command line tool for querying NTP servers • EXEC
about current state and can request changes in that state. • Privileged EXEC
ntpstat Displays current information about the time server. • EXEC
• Privileged EXEC
password Lets you change the password for the current shell All
mode.
ping Pings the host you specify, allowing you to determine if • EXEC
a host is reachable. Displays information about packets • Privileged EXEC
transmitted and received and round-trip time.
preview changes Privileged EXEC and global configuration modes • Privileged EXEC
display changes made in the current CLI session that • Global
are not saved using the write command. Bench configuration
configuration mode displays all the information that is • Bench
written to the Verifier’s flash file system, including any configuration
information that you change during the current CLI
session. (Bench configuration settings are saved when
you exit bench configuration mode and save the
configuration.)
reboot Restarts a Verifier that is currently online. Rebooting a Privileged EXEC
Verifier initiates start-up diagnostics and the discovery
process.
route Adds routes to or deletes routes from the Verifier’s • Global
routing table. configuration
• Bench
configuration
rtlookup Identifies the Verifier’s Test interfaces (primary or alias All
interfaces) that is used to transmit test packets.
scp Secure Copy (SCP) transfers files between hosts using • EXEC
the Secure Shell (SSH) protocol. • Privileged EXEC
server The port number to use for communication between the • Global
communications Verifier and BrixWorx. configuration
comm-port • Bench
configuration
server The maximum transfer rate in bytes per second from • Global
communications max- the Verifier to BrixWorx. configuration
rate • Bench
configuration
CLI Commands

server The maximum number of bytes per packet for data sent • Global
communications max- from the Verifier to BrixWorx. configuration
size • Bench
configuration
server The minimum number of bytes per packet for data sent • Global
communications min- from the Verifier to BrixWorx. configuration
size • Bench
configuration
server The time duration (in seconds) for which you want the • Global
communications Verifier to contact BrixWorx. configuration
polling-interval • Bench
configuration
server The number of times to retry establishing a connection • Global
communications to a BrixWorx registry before trying to establish a configuration
retries connection with another registry. • Bench
configuration
server The maximum time (in seconds) to wait before trying a • Global
communications connection attempt with a BrixWorx Registry. configuration
timeout • Bench
configuration
show alert-level Displays the system alert level. • All
show bench-cfg Displays the bench configuration settings stored in the Privileged EXEC
Verifier’s flash file system. If bench configuration has
been erased, the CLI displays a message that indicates
there is no bench configuration data.
show interfaces Displays the individual status of all test and wireless • EXEC
ports if specific interfaces are not specified. • Privileged EXEC
show ip Displays IP name server and domain name information • EXEC
for the Verifier. It also displays the DNS name servers • Privileged EXEC
that are dynamically acquired through the wireless
connection.
show log Displays a log of activity on the Verifier. The log is • EXEC
started when the Verifier discovers a registry. Time in • Privileged EXEC
the log is displayed as elapsed time in seconds from the
time of discovery
show log-level Displays the system log level. • EXEC
• Privileged EXEC
show ntp Displays the current status of NTP for the Verifier, • EXEC
including the IP address of the NTP server, the Verifier • Privileged EXEC
it is using, that server’s stratum, and the current date
and time.
show routes Displays the Verifier’s routing table. The display • EXEC
includes new routes to the remote wireless IP address. • Privileged EXEC
BV-110 CLI Commands

show running-config •
Displays the Verifier’s current configuration settings. EXEC
• Privileged EXEC
show server Displays the Verifier’s current network communication • EXEC
communications settings. • Privileged EXEC
show server discovery Displays information about the Verifier’s universal, • EXEC
network, and local registries. • Privileged EXEC
show snmp Displays the current status of accessibility for SNMP • EXEC
requests. • Privileged EXEC
show statistics Displays information about the Verifier’s current • EXEC
physical condition including CPU usage and • Privileged EXEC
temperature.
show terminal Displays the current status of CLI access and related • EXEC
Verifier settings. • Privileged EXEC
show time Displays the Verifier’s current time source, the date and • EXEC
time reported by that source, the timezone, and uptime • Privileged EXEC
statistics.
show usb Displays attached and supported USB devices. • EXEC
• Privileged EXEC
show usb all Displays all attached, supported and unsupported, USB • EXEC
devices. • Privileged EXEC
show usb <device- Displays the detailed status of the specified USB • EXEC
name> device. • Privileged EXEC
show version Displays the Verifier’s monolith version and hardware • EXEC
information. • Privileged EXEC
shutdown Shuts down the Verifier. Privileged EXEC
snmp community Sets the SNMP community string. Global
configuration
snmp system-contact Sets the SNMP.system contact. • Global
configuration
• Bench
configuration
snmp system-location Sets the SNMP.system location. • Global
configuration
• Bench
configuration
snmp trap-count Maximum number of traps allowed over the trap- Global
interval. configuration
snmp trap-interval Period of time for which you want to define a trap- Global
count limit. configuration
CLI Commands

speed The link speed of the ethernet port in Mbps. This Global
command is available from the interface global configuration
configuration submode.
ssh Secure Shell (ssh) client takes the name or IP address of • EXEC
a remote server and starts a login session while using • Privileged EXEC
encryption. SSH supports RSA authentication, which is
based on public-key cryptography.
tail Displays the contents at the end of a file. • EXEC
• Privileged EXEC
tcp-connect Verifies TCP connectivity between the Verifier port • EXEC
(Test or Management) and the destination you specify. • Privileged EXEC
You can optionally specify a timeout value to allow the
request to timeout if the destination does not reply.
By default, a timeout of 15 seconds is used if you do not
specify a timeout value.
tcpdump A command line tool for monitoring network traffic. It EXEC
captures and displays packet headers on a particular
network interface or on all interfaces.
telnet Establishes interactive communication with another • EXEC
computer over a network using the TELNET protocol. • Privileged EXEC
terminal Enables or disables access for telnet, ssh, or RADIUS • Global
server access. See “terminal telnet” on page 109 to configuration
learn more about terminal telnet. • Bench
configuration
terminal telnet Enables or disables telnet access for the Verifier. You • Global
can enable telnet on both ports (eth 0 or eth 1). If you do configuration
not specify a port, or if you use the any argument, telnet • Bench
is enabled on both the Verifier’s ports. configuration
time-receiver Selects the GPS, CDMA, or no time receiver. • Global
configuration
• Bench
configuration
traceroute Displays the network route traversed by packets to a • EXEC
specified destination. • Privileged EXEC
Transceiver Sets the ethernet transceiver type. This specifies the Global
physical connection type that is used. configuration
Transceiver electrical Sets the interface to use electrical transceiver type. This Global
is the RJ-45 connector, which indicates port number 1or configuration
port number 2.
Transceiver optical Sets the interface to use optical transceiver type. This is Global
the SPF connector, which indicates port number 1 or configuration
port number 2.
BV-110 CLI Commands

vlan Sets the VLAN configuration. The range for the VLAN Global
connection is 0 - 4095. If no VLAN connection is used, configuration
this parameter is deleted using [no] vlan CLI
command.
write Saves changes to the Verifier’s configuration made in • Privileged EXEC
the global configuration mode. The write command • Global
also checks for errors. If errors are discovered, the configuration
write command fails and none of the changes are • Bench
saved. configuration
A PPENDIX B
REPLACING A BRIX 100M WITH

A BV-110 VERIFIER
This appendix describes the steps that you need to follow to replace a
Brix 100M Verifier with a BV-110 Verifier.
In this appendix This appendix has the following section:
Section Page
Introduction 112
Adding and Configuring the BV-110 Verifier 113
Replacing the Brix 100M 114
Replacing a Brix 100M with a BV-110 Verifier
Introduction
When you replace a Brix 100M Verifier with a BV-110 Verifier, you need
to ensure that the transition is seamless by following this process:
1 Add and configure the BV-110 Verifier.
2 Replace the existing Brix 100M with the BV-110 Verifier.
The remaining sections in this appendix explain the details of the
replacement process.
An SLA that is configured to run on the Brix 100M Verifier is submitted
again to re-create test configurations for the new BV-110 hardware. If a
test is running on the Brix 100M and is not currently available for the
BV-110, the test is not configured on the BV-110.
Before the updated test configurations are sent to the BV-110 Verifier, the
system merges the Verifier configuration settings made using the CLI with
those made through the user interface. When the merge is complete, the
revised IP address acquisition and other configuration changes made using
the CLI are reflected in the user interface.
Replacing a Brix 100M with a BV-110 Verifier 113
Adding and Configuring the BV-110 Verifier
Adding and Configuring the BV-110 Verifier

You must first add and configure the BV-110 Verifier. Bench
configuration is recommended, but you must modify the running
configuration of the BV-110 Verifier to set the server discovery list and
comm port, to configure the IP address acquisition for port number 1 and
optionally for port number 2. You must also set network routes to ensure
that network traffic is sent to port number 1 if port number 2 is not to be
connected.
For more information. See “Adding a Verifier to BrixWorx” on page 42
to learn more about configuring a BV-110 Verifier.
Replacing the Brix 100M

After configuring the BV-110 Verifier, plug the BV-110 Verifier into the
network. You must connect port number 1 to the same network as the
Brix 100M. This is to ensure that the interface configuration information
for the Brix 100M network interface is applied to port number 1. You can
optionally configure port number 2.
Note: If you configure a BV-110 to have a fixed IP address that is the
same as a Brix 100M, you must unplug the Brix 100M from the network
before plugging the BV-110 into the network.
How to replace a To replace a Brix 100M with a BV-110 Verifier:
Brix 100M with a
1 From the Operations Center menu, select Verifiers.
BV-110 Verifier
The Verifiers page is displayed.
2 Click the name of the Brix 100M Verifier you want to replace.
The Verifier Information page is displayed.
3 Click the edit button at the top of the Basic Configuration section.
The Basic Configuration section is displayed.
4 In the Model/SN field, select the serial number of the BV-110 Verifier.
The Monolith field is updated to the BV-110 Verifier monolith.
6 Click the edit button corresponding to Test Interface 1.

The Test Interface 1 details are displayed.
a Select the Ethernet Speed setting.

b Select the Ethernet Duplex setting.
c Select the appropriate Transceiver radio button, optical or
electrical.
d Select appropriate IP address configuration settings.
Note: The address acquisition is updated after you save the configuration
to match the BV-110 configuration. You can retain the configuration for
Brix 100M.
e Click the save and continue button.
7 Click the edit button corresponding to Test Interface 2.

The Test Interface 2 details are displayed.
a Select the Ethernet Speed setting.

b Select the Ethernet Duplex setting.
c Select the appropriate Transceiver radio button, optical or
electrical.
d Select appropriate IP address configuration settings.
Note: The address acquisition is updated after you save the configuration
to match the BV-110 configuration. You can retain the configuration for
Brix 100M.
e Click the save and continue button.
8 Click the store this configuration button at the bottom of the Verifier
Information page.
The Verifier is ready for use.
Note: If you do not configure the test interfaces correctly, an error is
displayed indicating that the transceiver type and speed/duplex for an
interface are not compatible.
Index
A procedure 36
AC power required information 33
saving changes 33
BV-110 24
acquisition BIOS messages 92
CLI command 101 booting the Verifier 84
adding Brix 100M
Local Registry 104 replacing with a BV-110 111
Network Registry 104 BrixWorx
advanced configuration add Verifiers 43
Verifiers 45 Verifier settings
advanced parameters connection retries 66
timeout 66
Verifiers 52
alias BrixWorx licenses 43
Verifier 47 BV-110
attributes AC back panel 4
AC power 24
Verifiers 71
DC back panel 4
auditor function 95 DC mating connector 23
authentication DC power 25
RADIUS 64 features 2
fuse rating 26
B ports 6
power ratings 24
basic configuration
product safety certification 8
Verifiers 47
regulatory compliance 8
bench configuration replacing a Brix 100M 111
definition 32
Index
reset button 5 Verifiers 51

safety approval certification 8 DNS servers
Verifier network configuration 54
C domain-name 103
clear flash memory
Verifiers 86 E
CLI Command editing
acquisition 101 advanced Verifier configuration information 45
CLI command electrostatic discharge prevention 14
ip domain-name 103
ESD 14
comm layer
error codes 94
F
commands
erase bench-cfg 102
factory default settings
boot 84
erase running-cfg 102
preview changes 106 flash file system
rtlookup (ethernet) 106 writing changes to 33
Verifier interface commands force discovery
rtlookup (ethernet) 106 Verifiers 84
Verifier management commands fuse rating
preview changes 106 BV-110 26
write 110
write 110
I
community string
SNMP Service 62 information
Verifiers 46
compliance information 8
IP aliases
configuration specifying for a Verifier 59
serial port 89 Verifier test port configuration 59
console error 93 IP configuration 84
console port 6
L
D laser safety warnings 9
DC mating connector LEDs
BV-110 23 DC power A 5, 83
DC power status 5, 82
BV-110 25 Local Registry
DC power supply LEDs 5, 83 adding 104
default time displaying list of 108
Verifier time source 77 log files
description Verifiers 86
front panel 3
details
Index 121
M Verifier network configuration 54

manage
Verifiers 70 R
management port 6 rack mounting
model and serial numbers options 16
Verifiers 48 RADIUS authentication 64
monolith reboot
Verifiers 50 Verifiers 84
recycling and disposal 14
N registry and collectors
name Verifiers 49
Verifiers 47 regulatory compliance 8
naming regulatory information 8
Verifiers 47 replacing a Brix 100M with a BV-110 111
network configuration parameters 54 reports
network link type specifying Verifier bandwidth for 65
Verifiers 49 reset button
Network Registry factory defaults 84
adding 104 routing table
displaying list of 108 description 38
NTP server modifying 39
specify 63 rtlookup (ethernet) 106
P S
Phone Directories safety approval requirements 8
for PESQ mesh testing 55
SNMP
phone directory 55 enabling for Verifiers 62
Phone Groups specify
for PESQ mesh testing 55 NTP server 63
polling static routes 60
setting the polling interval 66 SSH
port connections 7 command 109
ports enabling for Verifiers 62
BV-110 6 static routes
power ratings compared to default routes 39
BV-110 24 specify 60
preview changes 106 status LEDs 5, 82
proxy front 5, 82
host system logging level 66
Verifier network configuration 52, 54
port
Index
T Verifiers 55
tail command 109 add to BrixWorx 43
adding a Local Registry 104
tcpdump command 109 adding a Network Registry 104
Telnet advanced configuration 65
enabling for Verifiers 63 advanced configuration parameters 45
telnet command 109 advanced parameters 52
test interface aliases 47
Verifiers 56 attributes 71
test modules basic configuration 47
effect of link type 49 changing name 101
choosing time sources 75
test port 6 clear flash memory 86
time source for Verifiers 77 clearing BV-110 running configuration 102
choosing 75 connection
types 77 retries 66
traceroute command 109 timeout 66
transfer size details 51
maximum 66 displaying registry information 108
minimum 66 enabling
SNMP 62
troubleshooting SSH 62
console error 93
Telnet 63
old test results 95
force discovery 84
starting BrixWorx 89
front panel 3
stopping BrixWorx 89
health and status 62
symptoms 95
how to
Web Agent log file 87
share across SLAs 44
information 46
U keys 43
Universal Registry licenses 43
displaying list of 108 link type 49
user modes log files 86
management 70
bench configuration 100
model 48
description 100
model and serial numbers 48
EXEC 100
monolith 50
global configuration 100
name 47
privileged EXEC 100
naming 47
users network configuration
CLI modes and 100 parameters 54
network link type 49
V phone directory 55
VCF (Verifier configuration file) 37 reboot 84
rebooting 106
Verifier alias 47
registry and collectors 49
Index 123
serial number 48
setting
the polling interval 66
sharing across SLAs 48
specifying
bandwidth for reporting 65
test interface 56
time sources 77
types of time sources 77
using
default time as a time source 77
Verifier configuration file (VCF) 37
ways to change Verifier configuration 37
W
Web Agent 87
WEEE directive 14
wireless port 6
write command 110

BV110InstallConfigGuide PDF

Uploaded by

Copyright:

Available Formats

BV110InstallConfigGuide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BV110InstallConfigGuide PDF

Uploaded by

Copyright:

Available Formats

BV-110™ VERIFIER INSTALLATION

AND CONFIGURATION GUIDE

Release Number: 8.1

Release Number: 8.1

Other Ways to Change a Verifier’s Configuration .........................................37

Other Brix Documentation

Book Title Description

Book Title Description

Book Title Description

Available formats Technical documentation for Brix products is available

Other Sources of Information

Mail EXFO Service Assurance

Call • In the US: 1 877-261-3279

INTRODUCING THE BV-110

Front Panel Description

Power Status LED

Back Panel Description-AC Verifier

Laser LED Status LED Power LED Reset button Power

Back Panel Description-DC Verifier

LED Behavior Descriptions

LED State/Color Indicates

The following table displays the Console pinout information:

Pin Number Direction Description

Category Approval Agency

Laser Safety Warnings

Federal Communications Commission (FCC) and

Application of Council Directive(s): 2006/95/EC – The Low Voltage Directive

Manufacturer’s Name and Address: EXFO Inc. EXFO Europe

Equipment Type/Environment: Test & Measurement / Industrial

Standard(s) to which Conformity is declared:

EN 61326-1:2006 Electrical equipment for measurement, control and laboratory use –

EN 61000-3-3: 2008 Electromagnetic Compatibility (EMC) – Part 3-3: Limits – Limitation

Stephen Bull, E. Eng

400 Godin Avenue,

PREPARING FOR INSTALLATION

Electrostatic Discharge Prevention

Recycling and Disposal (Applies to European Union

General Site Requirements

Rack Mounting Kit

WARNING: Hot surface.

Size (H x W x D) 31 mm x 202 mm x 180 mm (1.22 in x 7.95 in x

Size (H x W x D) 31 mm x 202 mm x 180 mm (1.22 in x 7.95 in x

Site Planning Checklist

Item Description Value

INSTALLING THE BV-110

Overview of the Installation Process

Step Description See

After installing the Verifier, you must establish communication with

Verifying the Package Contents

Rack Mount Parts List

Installation and Operational Warnings

Connecting the Power

BV-110 Verifier power ratings:

As soon as the BV-110 is connected to a live power supply, the power

Connecting the BV-110 to an AC Power Source

Connecting the BV-110 to a DC Power Source

Version Voltage Range (V) Fuse Rating (A)

Connecting the Ports

Connecting the Console Port