Escolar Documentos
Profissional Documentos
Cultura Documentos
Release 3.65
Ixia and its licensors retain all ownership rights to the IXIA 100, 400 and 1600 hardware and software and its doc-
umentation. Use of Ixia hardware and software is governed by the license agreement accompanying your original
purchase. This manual, as well as the hardware and software described in it, is furnished under license and may
only be used or copied in accordance with the terms of such license. The information in this manual is furnished
for informational use only, is subject to change without notice, and should not be construed as a commitment by
Ixia. Ixia assumes no responsibility or liability for any errors or inaccuracies that may appear in this book.
Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or
transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written
permission of Ixia.
IXIA, the Ixia logo, ANVL, IxExplorer, IxServer, Ixia NetOps, IxCore, IxEdge, IxMapping, IxProfile, IxTraffic,
IxActivate, and Optixia are either trademarks or registered trademarks of Ixia in the United States and/or other
countries.
All other companies and product names and logos are trademarks or registered trademarks of their respective
holders.
Contacting Ixia
Website www.ixiacom.com
General info@ixiacom.com
Sales sales@ixiacom.com
Training training@ixiacom.com
Chapter 1 Introduction
Ixia Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Powering Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
File-Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Computer System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Test System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
General Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
IxClock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Electrical Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Mechanical Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
MDC/MDIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Ixia produces a number of Load Modules which provide data transmission and
reception capabilities for a variety of Ethernet and Packet Over Sonet (POS)
speeds and technologies. These Load Modules reside in an Ixia chassis, which
provide different numbers of Load Module slots and power. In addition, an
IxClock chassis provides a facility for accurate timing. This chapter introduces
the Ixia hardware components. The Ixia chassis and load modules are compared
and contrasted.
Ixia Chassis
Five Ixia chassis capable of holding Load Modules are available:
• IXIA 1600 Chassis–capable of holding up to 16 Ixia Load Modules.
• IXIA 1600T Chassis–capable of holding up to 16 Ixia Load Modules and
equipped with extra power and fans required for some high-powered load
modules.
• IXIA 400 Chassis–capable of holding up to 4 Ixia Load Modules. Revision C
or higher is required to handle the extra power and cooling required for some
of the high-powered load modules.
• IXIA 250 Chassis–a portable Field Service Unit (FSU) which includes a sin-
gle 10/100/1000 port and capable of holding two additional Ixia Load Mod-
ule. May optionally be equipped with a built-in GPS or CDMA receiver.
Appendix A contains the specification of the GPS hardware.
• Clocking - IXIA 100 and IxClock Modules–the IXIA 100 is capable of hold-
ing one Ixia Load Module and includes a built-in GPS or CDMA receiver.
Appendix A contains the specification of the GPS hardware.
• Optixia Chassis–capable of holding a combination of high-density Ixia Load
Modules with 24 or 48 ports and smaller Load Modules compatible with the
other chassis. It supports up to a total of 480 10/100Mbps ports or 240 Giga-
bit ports. It is equipped redundant power supplies and supports hot-swapping
of Load Modules. The Optixia chassis includes sufficient power and airflow
to support high-powered load modules.
All of the Ixia chassis have the ability to hold one or more standard Load Mod-
ules. Ixia Load Modules provide media dependent and independent ports to
Devices Under Test (DUTs). Any of the chassis may be daisy-chained and syn-
chronized within 10ns. The IXIA 100 chassis includes timing provisions based
on GPS which allows accurate worldwide synchronization without local inter-
chassis connections.
The basic characteristics of these chassis are compared in Table 1-1 on page 1-2.
Table 1-1. Ixia Chassis Comparison
1600 16 Desktop/ 0
Rack
IxClock Module
The IxClock module provides a means of maintaining accurate timing through a
variety of input signals, including GPS, CDMA, T1/E1 and 1PPS signals. The
IxClock module includes a battery so that a GPS signal can be obtained ‘outside’
and the unit then brought inside. It also includes a Rubidium oscillator that
retains the time lock for a period of time.
Refer to Clocking - IXIA 100 and IxClock Modules for a complete discussion of
this module.
Load modules that end with -3 or -M are limited in their functionality. In general,
-3 and -M modules do not have the following functions:
• Flows, except where Streams are not supported.
• Advanced Streams (included with OC48C-3, however)
• Packet Groups (included with OC48C-3, however)
• Latency (included with OC48C-3, however)
• Sequence Checking (included with OC48C-3, however)
• Data Integrity (included with OC48C-M, however)
• Multiple DLCIs on OC48c Cards
• Convert to streams in capture view
• Protocol Server for router testing
Each family of interfaces is discussed in full in its own chapter in this manual.
The load module names used within the IxExplorer software differ slightly from
the load module names used in Ixia marketing literature. Table 1-2 on page 1-4
describes the mapping from load module names to the names used in IxExplorer.
The reverse mapping, alphabetized, is shown in Table 1-3 on page 1-6.
Stream triggers Collect statistics of how often the stream filters were
triggered.
Receive Modes Packet groups Supports generation of packet group IDs in packets.
Flow image file When packet flows are used, allows the data to come
from a file.
Gap time units The inter-frame, -burst, and -stream gaps can be
programmed in discreet units of time as opposed to
indirectly through a percentage of maximums frame
rate.
Frequency offset The frequency for the card as a whole may be modified
a few percent from nominal.
User Defined Fields Odd offset UDFs are allowed to start at an odd offset.
(UDF)
Bit mask UDFs output data may be masked with an arbitrary bit
mask. Otherwise limitations on the number of changes
of bits applies.
Multiple DLCIs Supports the use of more than one DLCI in frame relay
testing.
Set pause The destination for pause control packets may be set.
destination
address
ARP rate control The rate at which multiple ARP packets are transmitted
may be controlled.
IGMP rate control The rate at which multiple IGMP packets are
transmitted may be controlled.
Sequence checking
Advanced PG Filter
ISL Encapsulation
Checksum errors
Seq Check/PGID
S&Fwd LB to FB
S&Fwd LB to FP
Small Packets
Data integrity
Data integrity
Tx Duration
Qos
10/100
10/100 X X X X X X X X X
10/100-3 X X X X X X
10/100 TXS8 X X X X X X X X X
10/100 MII X X X X X X X X X
10/100 Reduced X X X X X X X X X
MII
10/100/1000
10/100/1000 TXS4 X X X X X X X X X X X
Copper 10/100/ X X X X X X X X X X X X
1000
100Mbps
100Base FX X X X X X X X
MultiMode
100Base FX X X X X X X X
SingleMode
Gigabit
Gigabit X X X X X X X X X X X X
Gigabit-3 X X X X X X X
GBIC X X X X X X X X X X X X
Gigabit Single X X X X X X X X X X X X
Mode
1000 SFPS4 X X X X X X X X X X X
USB
Ethernet/USB X X X X X X X X
OC12c/OC3c
OC12c/OC3c POS X X X X X X X X X X X
OC48
OC48c POS X X X X X X X X X X
Sequence checking
Advanced PG Filter
ISL Encapsulation
Checksum errors
Seq Check/PGID
S&Fwd LB to FB
S&Fwd LB to FP
Small Packets
Data integrity
Data integrity
Tx Duration
Qos
OC48c POS-M X X X X X X X X X X
OC48c BERT
OC48c POS/BERT X X X X X X X X X X
Unframed Bert
Single-Rate
Unframed BERT
Multi-Rate
Unframed BERT
OC192
OC192c POS X X X X X X X X X
OC192c BERT
OC192c POS/ X X X X X X X X X
BERT
OC192c POS/ X X X X X X X X X X X
10GE WAN
OC192c POS/ X X X X X X X X X X X
BERT/10GE WAN
OC192c VSR POS X X X X X X X X X
OC192c VSR
BERT
OC192c VSR POS/ X X X X X X X X X
BERT
10GB
10GE WAN X X X X X X X X X X X
10GE BERT/WAN X X X X X X X X X X X
10GE LAN X X X X X X X X X X X
10GE LAN-M X X X X X X X X X X
10GE XAUI X X X X X X X X X X X
10GE XAUI/BERT X X X X X X X X X X X
10GE XENPAK-M
X
X
Stream trigger
Checksum errors
Stats
X
X
Data integrity
X
X
Tx Duration
X
Packet groups
TABLE 1-5. Card Features Summary - Part 1
X
X
S&Fwd LB to FB
X
X
S&Fwd LB to FP
Advanced PG Filter
Round trip flows
X
X
Data integrity
First time stamp
Receive Modes
X
X
Sequence checking
X
X
Seq Check/PGID
X
X
ISL Encapsulation
Small Packets
Ixia Load Module Properties
Introduction
1-13
Introduction
1 Ixia Load Module Properties
Hardware Checksum
Incr Frame Size by N
Modifiable Preamble
Forced Collisions
Frequency Offset
Tx Data Integrity
Incr DA/SA by N
Packet Streams
Odd Preamble
Packet Flows
Odd offset
Advanced
Incr By N
Bit Mask
Cascade
Overlap
UDF5
Echo
Split
10/100
10/100 X X X X X X X
10/100-3 X X X X X
10/100 TXS8 X X X X X X X X X X X X X
10/100 MII X X X X X X X
10/100 Reduced X X X X X X X
MII
10/100/1000
10/100/1000 TXS4 X X X X X X X X X X X X X X X X X
Copper 10/100/ X X X X X X X X
1000
100Mbps
100Base FX X X X X X X X
MultiMode
100Base FX X X X X X X X
SingleMode
Gigabit
Gigabit X X X X X X X
Gigabit-3 X X X X X
GBIC X X X X X X X
Gigabit Single X X X X X X X
Mode
1000 SFPS4 X X X X X X X X X X X X X X X X X
USB
Ethernet/USB X X X X X X X
OC12c/OC3c
OC12c/OC3c POS X X X X
Hardware Checksum
Advanced Scheduler
Frequency Offset
Tx Data Integrity
Incr DA/SA by N
Packet Streams
Odd Preamble
Packet Flows
Odd offset
Advanced
Incr By N
Cascade
Bit Mask
Overlap
UDF5
Echo
Split
OC12c POS 32MB X X X X
OC48
OC48c POS X X X X X X X X X
OC48c POS-M X X X X X X X X X
OC48c BERT
OC48c POS/BERT X X X X X X X X X
Unframed Bert
Single-Rate X
Unframed BERT
Multi-Rate X
Unframed BERT
OC192
OC192c POS X X X X X X X X X
OC192c BERT
OC192c POS/ X X X X X X X X X
BERT
OC192c POS/ X X X X X X X X X X X
10GE WAN
OC192c POS/ X X X X X X X X X X X
BERT/10GE WAN
OC192c VSR POS X X X X X X X X X
OC192c VSR
BERT
OC192c VSR POS/ X X X X X X X X X
BERT
10GB
10GE WAN X X X X X X X X X X
10GE BERT/WAN X X X X X X X X X X
1-16
10GE LAN
10GE XAUI
10GE LAN-M
10GE XENPAK
Introduction
Card Name
10GE XENPAK-M
10GE XAUI/BERT
10GE XAUI BERT
X
X
X
X
X
X
Packet Streams
Ixia Load Module Properties
Packet Flows
Flow image file
X
X
X
X
X
X
Advanced Scheduler
Forced Collisions
X
X
X
X
X
X Tx Data Integrity
Odd Preamble
TABLE 1-6. Card Feature Summary - Part 2
X
X
X
X
X
X
X
X
X
X
Modifiable Preamble
Forced Minimum Gap
Transmit Modes
X
X
X
X
X
X
Odd offset
X
X
X
X
X
X
Overlap
Cascade
Split
X
X
X
X
X
X
UDFs
Bit Mask
X
X
X
X
X
X
Incr By N
UDF5
IxWeb/IxRouter
Error insert list
Multiple DLCI
BERT err gen
Layer 2 VPN
Layer 3 VPN
Lane Skew
Local CPU
SRP Full
Routing
RIPng
BERT
PING
XAUI
WAN
DCC
POS
ARP
SRP
LAN
LDP
10/100
10/100 X X X X X
10/100-3 X X X X
10/100 TXS8 X X X X X X X X X X
10/100 MII X X X X X
10/100 Reduced X X X X X
MII
10/100/1000
10/100/1000 TXS4 X X X X X X X X X
Copper 10/100/ X X X X X
1000
100Mbps
100Base FX X X X X X
MultiMode
100Base FX X X X X X
SingleMode
Gigabit
Gigabit X X X X X
Gigabit-3 X X X X
GBIC X X X X X
Gigabit Single X X X X X
Mode
1000 SFPS4 X X X X X X X X
USB
Ethernet/USB X X X X X
OC12c/OC3c
OC12c/OC3c POS X X X X
IxWeb/IxRouter
Error insert list
Multiple DLCI
BERT err gen
Layer 2 VPN
Layer 3 VPN
Lane Skew
Local CPU
SRP Full
Routing
RIPng
BERT
PING
XAUI
WAN
DCC
POS
ARP
SRP
LAN
LDP
OC48
OC48c POS X X X X X X X
OC48c POS-M X X X X X X
OC48c BERT X X X X
OC48c POS/BERT X X X X X X X X X
Unframed Bert
Single-Rate X X X X
Unframed BERT
Multi-Rate X X X X
Unframed BERT
OC192
OC192c POS X X X X X X X X X
OC192c BERT X X X X
OC192c POS/ X X X X X X X X X X X X
BERT
OC192c POS/ X X X X X X X X X X X X X X X X
10GE WAN
OC192c POS/ X X X X X X X X X X X X X X X X X X X
BERT/10GE WAN
OC192c VSR POS X X X X X X X X X
OC192c VSR X X X X
BERT
OC192c VSR POS/ X X X X X X X X X X X X
BERT
10GB
10GE WAN X X X X X X X X X X
10GE BERT/WAN X X X X X X X X X X X X X
10GE LAN X X X X X X X X X X
10GE LAN-M X X X X X X X X X
IxWeb/IxRouter
Error insert list
Multiple DLCI
BERT err gen
Layer 2 VPN
Layer 3 VPN
Lane Skew
Local CPU
SRP Full
Routing
RIPng
BERT
PING
XAUI
WAN
DCC
POS
ARP
SRP
LAN
LDP
10GE XAUI X X X X X X X X X X X
10GE XAUI/BERT X X X X X X X X X X X X X X
10GE XENPAK X X X X X X X X X X X X
10GE XENPAK-M X X X X X X X X X X X
Card Properties
The load module chapters include the card characteristics described in Table 1-8
on page 1-19.
Table 1-8. Card Specifications
Specification Usage
Captured packet size The range of packet sizes that may be captured
on the card.
Specification Usage
To get the best idea of the memory available for packet capture, a set of simple
experiments can be run. For example, the following table indicates the measured
number of packets captured for different packet sizes. The type of card used was
an LM100TX, which has a 2MB capture buffer. The buffer slice was set to 8191.
Table 1-9. Measured Number of Packets for an LM100TX Card
IXIA 250 The IXIA 250 is a new, portable Ixia chassis with a built-in keyboard and screen.
It contains a single 10/100/1000 or 1000 port and has room to accommodate up
to two Ixia load modules. Refer to:
• Chapter 6, IXIA 250 Chassis
10GE Cards Additional cards have been added to the 10GE card family. Refer to:
• Chapter 18, IXIA 10Gigabit Ethernet Load Modules.
RMII Interface Additional details on the 10/100RMII interface have been added. Refer to:
• Appendix C, LM-RMII Interface Specification.
Configuration
This chapter discusses the installation and initial configuration for the Ixia
Hardware.
Ixia Hardware
Four Ixia Hardware chassis are available:
• IXIA 1600 Chassis–capable of holding up to 16 Ixia Load Modules.
• IXIA 1600T Chassis–capable of holding up to 16 Ixia Load Modules and
equipped with extra power and fans required for some high-powered load
modules.
• IXIA 400 Chassis–capable of holding up to 4 Ixia Load Modules. Revision C
or higher IXIA 400 chassis are required to handle the extra power and cooling
required for some of the high-powered load modules.
• Clocking - IXIA 100 and IxClock Modules–the IXIA 100 is capable of hold-
ing 1 Ixia Load Module and includes a built-in GPS or CDMA receiver.
Appendix A contains the specification of the GPS hardware.
Unpacking the Ixia Each chassis comes packed in its own box. Carefully remove all of the pieces
Chassis from the box and check that you have all of the components listed below:
❒ IXIA 100, 400, 1600, 1600T or Optixia chassis
❒ Power cord
❒ Right and left ear brackets and screws, for rack mounting
(IXIA 100 and 1600 only)
❒ Y splitter cable (IXIA 100 and 400 only)
❒ Chassis sync cable
❒ The following documentation items, possibly shipped
separately:
❒ Windows 2000 certificate of authenticity
❒ This Quickstart Guide
Notes and Warnings • Voltage. The Ixia chassis all utilize voltage from 100VAC to 240VAC at 50/
60Hz. Current is from 20A to 2.25A.
• Power cord. Use the power cord provided or a power cord approved by the
appropriate agency for use in the country where the unit is being used. The
power source should be properly grounded.
• Ventilation requirements. For the IXIA 1600 and Optixia, do not block the
bottom or the back. For the IXIA1600T, 400 and 100, do not block the back
or sides.
• Rack mounting. Two rack-mount ears are provided which are designed to fit a
generic 19” electronic rack, along with 6 black flat-head screws. First, attach
the ears to the unit, and then attach the unit by the ears to the rack by a
method appropriate for the rack.
• Maintenance instructions. The only user maintainable feature is changing the
fuse, if it blows. Only replace the fuse with one of the same size and rating as
what is installed. The fuse drawer, located near the power cord, pulls out with
a small flat-bladed screwdriver. Note that repeated fuse blowing may likely
indicate some internal problem; you should reporting the problem to Ixia
Technical Support. Clean intake grills periodically to permit good airflow
intake.
Initial Configuration
The Ixia Chassis comes pre-loaded with IxServer and IxExplorer software along
with Windows 2000. The chassis includes an internal industry-standard PC hard-
ware platform. In order to perform initial configuration, it is necessary for you to
obtain the components below and to attach them to the appropriate connectors on
the back of the chassis:
• SVGA monitor
• PS/2-style keyboard
• PS/2-style mouse
NOTE: Any of the Ixia chassis must always be operated with the chassis cover
closed and with all card face plates mounted.
The TCP/IP networking on the chassis must be configured first. In order to con-
figure TCP/IP, follow the steps below:
1. Attach the monitor, keyboard and mouse to the ports on the back of the 1600,
400 or 100 chassis or the front of the Optixia chassis as shown in the figures
below.
Mouse
Monitor
Keyboard
Figure 2-2. Rear View of IXIA 400 Chassis with Serial Mouse
Serial Mouse
Monitor
PS-2 Keyboard
Figure 2-3. Rear View of IXIA 400 Chassis with PS-2 Keyboard and Mouse
PS-2 Mouse
DIN Keyboard
Figure 2-4. Front View of Optixia Chassis with PS-2 Keyboard, Mouse and
Monitor
An additional ‘Y’ connector, shown in Figure 2-5 on page 2-5, is included with
the IXIA 400 chassis when a PS-2 keyboard and a PS-2 mouse are both required.
This is the lower pictured cable.
Similarly, the IXIA100 has two possible sets of cable connections, based on the
availability of a serial mouse. This is shown in the following two figures:
PS-2 Keyboard
PS-2 Mouse
PS-2 Keyboard
2. Attach the power cord to the chassis and then to the wall socket. Switch the
master power switch to ‘1’ (on).
3. Power on the chassis by depressing the power button on the front of the chas-
sis.
4. Verify that the monitor screen appears as shown below
Windows 95 Configuration
Windows 95 TCP/IP The network address of the chassis must now be set, even if the network will not
Configuration be used.
1. To do this right click on the Network Neighborhood icon and select Properties
with the left mouse button:
Right Click
Left Click
2. The Network Menu is then displayed and is shown below. Select the Identifi-
cation tab.:
3. The Identification tab is shown below. Note the value in the ‘Computer
Name’ field - we will refer to this as the Host ID at a later time when running
the IxExplorer. Press OK and go back to the Configuration tab.
4. Now double left click on the TCP/IP entry to get the TCP/IP dialog shown
below.
5. This setting reflects the default factory setup for your chassis. It is configured
to utilize DHCP in order to discover all network aspects for your chassis. If
you have a DHCP server on the network attached to the chassis, then this is
the appropriate configuration of your chassis; skip the remainder of this sec-
tion. If no DHCP server is found on the network, then your chassis will not be
accessible from your network. Again this might be appropriate for your net-
work.
6. If the chassis is to be attached to an existing network, then obtain the values
shown in the table of IP values from your network administrator and enter
them on the appropriate TCP/IP Properties sheet. Only a subset of all of the
parameters are shown here, your administrator might suggest other options.
The IP address is an important quantity that you will need; write it down for
later use. Plug your network cable into the RJ-45 plug pictured above. [Note:
the Ixia chassis will generate a great deal of network traffic when applying
input sequences and sensing results. It may not be wise to connect one or
more chassis to a widely used network without the aid of a network switch,
bridge or similar device.
The table of TCP/IP Networking Parameters is shown below:
Table 2-1. TCP/IP Networking Parameters
7. Click OK and Windows will ask you if you wish to reboot. Answer ‘YES’.
Windows 95 The Windows 95 initial configuration includes some features which make the
General chassis more robust and easier to use:
Configuration 1. The time zone of the computer has been set to GMT, with Daylight Saving
Time disabled. To change this, right-click on the time in the lower left corner
of the screen and then left-click on Adjust Date/Time, as shown in Figure 2-
14.
Left Click
Right Click
2. First select the Time Zone tab from the dialog and adjust the time zone and
daylight savings time settings as appropriate, as shown in Figure 2-16, then
return to the Date & Time tab to set the current time in your time zone.
Double Click
2. The Local Area Connection Status dialog will open, as shown below.
3. Click the Properties button, and the Local Area Connection Properties dialog
will open, as shown below:.
4. In the Local Area Connection Properties dialog, check the boxes for the fol-
lowing items:
• Internet Protocol (TCP/IP) - required
• Client for Microsoft Networks - if information on other networked systems
is to be accessed via Microsoft file sharing, this should be checked.
• File and printer sharing for Microsoft Networks - if information or printers
are to be shared via Microsoft file sharing, this should be checked.
5. Double click on the Internet Protocol TCP/IP entry or press the Properties
button to open the Internet Protocol (TCP/IP) Properties dialog shown below:
6. This setting reflects the default factory setup for your chassis. It is configured
to utilize DHCP in order to discover all network aspects for your chassis. If
you have a DHCP server on the network attached to the chassis, then this is
the appropriate configuration of your chassis; proceed to step 11. If no DHCP
server is found on the network, then Windows 2000 will automatically assign
a unique IP address in the 169.254.0.0–169.254.255.255 range. Again this
might be appropriate for your network. If you need to assign a particular IP
address to your chassis, then fill in the fields as shown below and explained in
the following table:
General Obtain an IP address If selected, the fields for IP address are disabled, and the
automatically button for Obtain DNS server address automatically is
selected.
Use the following IP If selected, the fields below become active for manual
address: configuration of the IP address information.
Obtain DNS server If selected, the IP address for the server providing Domain
address automatically Name Service for name resolution is obtained
automatically from the local DHCP server.
Use the following If selected, the fields below become active for manual
DNS server entry of the IP addresses for the DNS servers.
addresses
7. You will need to refer to the Host ID at a later time when running IxExplorer.
This name must be assigned in the My Computer > Identification Changes
Window. First right-click on the My Computer icon on the desktop to display
the popup menu, as shown below.
Right Click
Left Click
9. On the Network Identification tab, press the Properties button to display the
Identification Changes dialog shown below.
10. The Computer Name shown in Figure 2-25 is an example of the pre-config-
ured name assigned to each chassis. Each chassis’ name is of the form
<TYPE>-<SERIALNO>. <TYPE> is either 100, 400, 1600 or Optixia corre-
sponding to the type of chassis. <SERIALNO> is the chassis serial number
and is always six digits long. By default, each chassis is also a member of the
IXIA workgroup. This may be changed at this time to another workgroup or
as a member of a Windows NT/2000 domain. If any changes have been made,
Windows will ask you if you wish to reboot. Answer ‘YES’.
Windows 2000 The Windows 2000 initial configuration includes some features which make the
General chassis more robust:
Configuration 1. Windows 2000 Service Pack 1 has been applied. This Microsoft Certified
software increases the operating system security.
2. The time zone of the computer has been set to GMT, with Daylight Saving
Time disabled. To change this, right-click on the time in the lower left corner
of the screen and then select Adjust Date/Time.
Right Click
First select the Time Zone tab from the dialog and adjust the time zone and
daylight savings time settings as appropriate, as shown in Figure 2-28, then
return to the Date & Time tab to set the current time in your time zone.
Double Click
Windows 2000 This section includes some important notes on passwords and other security set-
Security Settings tings.
1. The password for the Administrator account is the word ixia (all lower case).
The Administrator account is responsible for system maintenance and may
perform any operation on the system. It is strongly suggested that this pass-
word be changed as soon as you receive your chassis. To perform this opera-
tion, select the Manage dialog from the My Computer icon, as shown in
Figure 2-30.
Right Click
Select
2. In the dialog (shown in Figure 2-31), select the Administrator entry, right-
click and select Set Password. In the form that pops up, set the new password
twice and press OK.
3. A user account has also been created for use during normal test operation. It is
named IXIA-<SERIALNO>, where <SERIALNO> is the serial number of the
chassis. This user is automatically logged in when the chassis is powered on.
This user account does not have a password associated with it. If you wish to
change the password for this account, you must do two things. First, change
the password as discussed in Step 2. Second, set the password into the system
entry used for the automatic login at boot time. This is accomplished through
the use of Tweak UI which can be accessed through the Start button as shown
in Figure 2-32.
Figure 2-33. Setting the Password Associated with the Default User
4. When accessing the chassis’ disk drive remotely via another computer’s Net-
work Neighborhood choice in a Windows Explorer window, a user account
and password must be given. Use the IXIA-<SERIALNO> account and pass-
word defined above (or empty if it has not been changed).
Local/Remote Operation
The IxExplorer software is the user’s primary tool for navigation, configuration,
and control of the Ixia hardware. You may use IxExplorer either from the monitor
attached directly to the chassis or from a system connected to the network
attached to the chassis. After initial configuration, the monitor, keyboard and
mouse need not remain attached to the chassis. If the IxExplorer software is to be
used from a remote system, the software must be installed there; this is covered
below.
Powering Up
To power up the chassis, press the power button on the front of the chassis. If a
monitor is connected to the chassis, then the initial screen should be as pictured
in Figure 2-9 on page 2-7.
The IxServer software is the agent that interfaces directly to the hardware of the
chassis. It is started automatically at power-up and the software’s viewable out-
put is primarily intended as a diagnostic tool for the Ixia hardware. IxExplorer
can now be started locally by double-clicking on the IxExplorer icon on the Win-
dows desktop, shown below:
NOTE: The chassis must be powered off before installing or removing load
modules.
Shutting Down
To shut down the chassis, if you are using the monitor attached to the chassis
itself, you can use any of the three following techniques:
• From IxExplorer, select the chassis in the tree view, click on “Tools” and
choose “Shutdown”
• Close IxExplorer, and shut down Windows normally by using the “Shut-
down” option from the Start menu
• Depress the power button on the front of the chassis
If you are using IxExplorer remotely, you can shut down the chassis by:
• From IxExplorer, select the chassis in the tree view, click on “Tools” and
choose “Shutdown”
All of these options will invoke a graceful shutdown of Windows, and turn off
the power supply in the chassis. When the chassis is powered off but still getting
AC power, the green “Standby” LED on the front of the chassis will be lit. Try to
avoid powering down the unit by removing AC power or turning off the power
switch at the AC power input module on the rear of the chassis, as this may cause
file system problems.
File-Sharing
Ixia chassis are shipped with File Sharing to its disk enabled, but set to Read-
Only mode. If the chassis is connected to a network, care should be taken to pro-
tect the contents of the disk as with any computer system. No non-essential soft-
ware should be installed, nor should the type of File Sharing be set to Read-Write
without restricting the scope of file sharing and/or establishing procedures to
ensure that the system is used properly and that it can be restored from a known-
good backup.
Chassis Chaining
Regardless of which Ixia chassis you have, up to 256 chassis may be linked
together into a chassis chain. In order to chain any two chassis together, use only
the Ixia supplied cables to connect the Sync Out from one chassis to the Sync In
of the next chassis in the chain, as shown below. The chassis whose Sync In is
not connected is the Master of the chain. The IxExplorer software automatically
determines the master in the chain and the chain order.
Sync Out
Sync In
NOTE: Chained chassis are sensitive to the order in which chassis are brought
up and to any disconnection of sync cables. Always bring up chained chassis in
the order in which they are chained. If a sync cable is disconnected, reconnect
the cable and shutdown all chassis and bring them up in the same order.
The Ixia 1600 chassis has 16 slots for Ixia Load Modules. It is shown in Figure
3-1.
Specifications
The chassis specifications are contained in Table 3-1.
Table 3-1. Ixia 1600 Chassis Specifications
Physical
Environmental
Temperature
Humidity
The IXIA 1600T chassis has 16 slots for Ixia Load Modules, but may also be
used to support the high-powered load modules, including all OC192 and 10GB
modules. The IXIA 1600T Chassis is specifically designed to accommodate up to
eight OC192 Load Modules. It has an enhanced power supply, providing more
than three times the power of the standard IXIA 1600. Additional cooling fans
have been added to the 1600T to meet the requirements of the OC192 modules.
The IXIA 1600T is shown in Figure 4-1.
Specifications
The chassis specifications are contained in Table 4-1.
Table 4-1. Ixia 1600T Chassis Specifications
Physical
Environmental
Temperature
Humidity
Insert one or more OC192 modules into the chassis as indicated by the Table 4-2
on page 4-4.
Table 4-2. Slot Preferences for Installing Multiple OC192 Load Modules
6th 1&2 (4) 1-slot (shift the 5th module to slots 3 & 4)
7th 7&8 (2) 1-slot (shift the 3rd module to slots 9 & 10)
8th 13 & 14 None (shift the 4th module to slots 15 & 16)
The filler panels are required when there are empty slots in the chassis. However,
any other Ixia load modules, such as 10/100, Gigabit, OC12/3c, and OC48c, can
be installed in the chassis, alongside the OC192c load modules. First, insert the
OC192c load modules into the respective slots, as described in the second col-
umn of the table above. Second, install any other load modules in any empty
slots. Last, fill the remaining slots with the filler panels.
The IXIA 400 chassis has 4 slots for Ixia Load Modules The IXIA 400 is shown
in Figure 5-1 on page 5-1. Revision C or higher is required to support high-pow-
ered load modules, including OC192, 10GB and 10/100TSX8 modules. Rev C or
higher will handle one, one-port card and Rev L or higher will support one two-
port card.
Specifications
The chassis specifications are contained in Table 5-1 on page 5-2.
Table 5-1. Ixia 400 Chassis Specifications
Physical
Environmental
Temperature
Humidity
The IXIA 250 is a Field Service Unit (FSU) chassis with a built-in 10/100/1000
port and an additional 2 slots for Ixia Load Modules The IXIA 250 is shown in
Figure 6-1.
Operation
Setup The IXIA 250 incorporates an adjustable support, shown collapsed in Figure 6-2
and extended in Figure 6-3.
The support is extended by placing your thumbs in the recesses at the top and
pushing down as shown in Figure 6-4. Make sure that the stand is stable in one of
its available locking positions.
The keyboard is released by pressing on the button at the top of the chassis, as
shown in Figure 6-5.
Power is applied to the unit by plugging it in and toggling the “1/0” switch as
shown in Figure 6-6.
This applies power to the chassis, but does not turn on the computer within. The
separate Standby switch must be pressed, as shown in Figure 6-7. This may also
be used to put the computer into standby mode at a later time. Should the IXIA
250 experience a power failure, it will not automatically boot the operating sys-
tem.
Computer The computer on the IXIA 250 is operated as with any other computer system
Operation running Windows 2000. The keyboard is used for all typed input. The touchpad
at the bottom of the keyboard, as shown in Figure 6-8, is used to position the cur-
sor and ‘click’ the left and right mouse buttons.
LCD Brightness
Right button
Touchpad
Left button
Right button
Just put your index finger on the touchpad and move it around, following the cur-
sor on the screen. Use the buttons under the touchpad as you would the left and
right mouse buttons on a mouse. Double tapping on the keyboard is equivalent to
a double-mouse click. Pressing in the shaded area at the top-right of the touchpad
is equivalent to a right mouse button click.
The intensity of the LCD screen is controlled by the slide switch at the top right
of the keyboard.
In addition to the use of the touchpad, an external mouse may be connected to the
Keyboard/Mouse port at the back of the chassis. Further, the LCD screen is touch
sensitive and may be used as an alternative to the touchpad or mouse. Touching
the screen is equivalent to pressing and holding the left mouse button at that point
and taking your finger off the screen is equivalent to releasing the mouse button.
Keyboard or
mouse connectors
The rear panel of the IXIA 250 contains additional connectors for external
devices. This is shown in Figure 6-11 and further explained in Table 6-1.
Table 6-1. IXIA 250 Computer Connections
Connector Usage
A floppy drive and access to the hard disk is provided on the left rear of the chas-
sis, as shown in Figure 6-10.
Hard Disk
Floppy
CDMA/GPS
Antenna
Input
Test Operation Device testing may be accomplished using the built-in port or by plugging in
additional Ixia load modules. Figure 6-11 shows two additional boards in an
IXIA 250 chassis.
Card #1
Card #3
Card #2
The IXIA 250 will accept any two single-wide or one double-wide load module.
See the remaining chapters of this manual for a discussion of available load mod-
ules. When using Ixia software to access the load modules, the cards are num-
bered as shown in Figure 6-11. That is, the built-in port is card number 1, the
lower card in the chassis is card number 2 and the card above that is card number
3.
When the IXIA 250 is ordered with the Gigabit-only option, then one of two
optional connectors may be attached to the Test Port. The connectors are either
copper (RJ-45) or fibre optic (LC). The module to which the connector is
attached is hot-swappable. Merely press the release button to the left of the con-
nector and pull out the connector.
Sync-in/Sync-out connectors are provided to daisy chain the IXIA 250 with other
chassis.
Specifications
Computer System The computer specifications are contained in Table 6-1.
Table 6-2. IXIA 250 Computer Specifications
Memory 256 MB
External keyboard Via external connector: PS/2 6-pin DIN with or without Y-
connector
External mouse Via external connector: PS/2 6-pin DIN with or without Y-
connector
LCD Integrated:
• 1024 x 768 resolution
• Touchscreen
• Adjustable brightness
Test System The test system specifications are contained in Table 6-3 on page 6-8.
Table 6-3. IXIA 250 Computer Specifications
General The general specifications are contained in Table 6-4 on page 6-8.
Specification Table 6-4. IXIA 250 Chassis Specifications
Physical
Environmental
Temperature
Humidity
Momentary power-on
The Optixia chassis has 10 slots for Ixia Load Modules. Each slot either accom-
modates one high-density card or up to two smaller cards on a special carrier.
Optixia may also be used to support the high-powered load modules, including
all OC192 and 10GB modules. For double-wide load modules such as the OC-
192, a double-wide carrier are provided. This allows the Optixia to accommodate
all existing load modules.
The Optixia uses four redundant power supplies, providing continuous long term
operation. It also supports hot-swapping of Load Modules, allowing dynamic re-
configuration. The Optixia is shown in Figure 7-1 on page 7-1.
Specifications
The chassis specifications are contained in Table 7-1 on page 7-2.
Table 7-1. Optixia Chassis Specifications
Physical
Environmental
Temperature
Humidity
Trigger In BNC
IxClock Modules
Ixia 100
The IXIA 100 chassis has 1 slot for Ixia Load Modules and includes either an
integral GPS unit (IXIA 100 GPS) or CDMA unit (IXIA 100 CDMA). The IXIA
100 is shown in Figure 8-1 on page 8-1.
The IXIA 100 with Integrated Global Positioning System (GPS) or Code-Divi-
sion Multiple Access (CDMA) technology is designed for distributed end-to-end
performance measurements of key metrics, including point-to-point latency and
jitter.
IxClock
The IxClock module provides the means for accurate world-wide timing using a
number of different reference inputs. It includes an integral GPS unit. The
IxClock module is shown in Figure 8-2 on page 8-1.
The IxClock module may be used in conjunction with any of the standard IXIA
chassis (100, 400, 1600 and 1600T). The IxClock module and the Ixia 100 chas-
sis have a number of characteristics in common and are discussed together in the
following section.
Background–Chassis
Synchronization
Measurement of unidirectional latency and jitter in the transmission of data from
a transmit port to a receive port requires that the relationship between the time at
the ports is known. This is not required for measuring roundtrip properties since
the same port sends and receives the data. This can be accomplished by providing
one of the following signals between chassis:
• Clock (frequency standard): this allows chassis to phase-lock their frequency
standards so that a cycle counter on any chassis will count the same number
of cycles during the same time interval. Each Ixia port maintains such a
counter from a common chassis-wide frequency standard.
• Reset: Phase-locking the frequency standards between chassis allows ports on
different chassis to count the same number of cycles during a given time
interval. However, this does not allow the transmission delay to be calculated.
A means of either discovering the fixed offset between their counters or
simultaneously setting the counters to a known value must exist. It is concep-
tually easy to think of this as the zero reset.
Ixia has provided facilities that allow for the synchronization of independent Ixia
chassis located anywhere in the world by replacing the existing inter-chassis sync
cables with a widely available frequency and time standard supplied from an
external source. Accurate timing can be used to obtain accurate latency and other
measurements in a live global network. When geographically dispersed chassis
are connected in this way, the combination is called a ‘virtual chassis chain’.
Worldwide Two or more Ixia 100 chassis and/or IxClock modules may be distributed world-
Synchronization wide forming a virtual chassis chain based on GPS and/or CDMA timing. One
possible configuration is shown in Figure 8-3 on page 8-3.
The ports on all of the chassis may be shared by one or more Ixia software users
located likewise anywhere in the world. Where GPS and CDMA sources are
used, all of the sources must have good quality time values in order to for the
trigger to be transmitted.
Once the timing features of the chassis is configured, operating a worldwide set
of Ixia chassis is the same as local operation. The Ixia hardware and software
programs the clocks such that they all send a master trigger pulse to all Ixia chas-
sis, within a tolerance of ±80 ns with GPS and ±100 us for CDMA.
Ixia chassis timing operates by setting a time-of-day from one source and then
maintaining the time accuracy through a potentially different means. Table 8-1
on page 8-3 describes the full set of options available and their approximate rela-
tive accuracies.
Table 8-1. Summary of Timing Options
Ixia 100, 400, 1600 Synchronous N/A Internal PC clock 1 microsecond / second
IxClock GPS (with T1/E1 150 nanoseconds T1/E1 or 1PPS Dependent on the
or 1PPS input) accuracy of the selected
frequency source
The specifications of the GPS unit are detailed in Appendix A, Time and
Frequency Module.
Independent Independent Ixia 400, 1600 or Optixia chassis may synchronize themselves with
Operation other chassis as shown in Figure 8-4 on page 8-4.The timing choices are
explained in Table 8-2 on page 8-4.
Internal Sync
Choice Usage
Ixia 100 If the two chassis are separated by any significant distance, a sync-out/sync-in
cable cannot be used to connect them. In this case, two Ixia 100 chassis with
built-in Global Positioning Satellite (GPS) or Code Division Multiple Access
(CDMA) are attached to each chassis through sync-out/sync-in cables, as shown
in Figure 8-5 on page 8-5. The Ixia 100s maintains an accuracy of less than 150
nanoseconds when attached to a GPS antenna or 100 microseconds when
attached to a CDMA receiver and provide chassis to chassis synchronization.
The Ixia 100 chassis contains one slot for an Ixia card module. The additional
timing features available with the Ixia 100 are shown in Table 8-3 on page 8-5.
Table 8-3. Ixia 100 Chassis Timing Choices
Choice Usage
The Sync-Out from the Ixia 100 is used to master a chassis chain at a specific
geographic location. Since the Ixia 100 chassis has all other functions provided
by the other Ixia chassis, it may also use independent timing when not used to
synchronize with other chassis at other locations.
IxClock The final choice involves the use of an IxClock chassis. This is shown in Figure
8-6 on page 8-6.
The IxClock module is a separate rack-mountable chassis for use in isolated envi-
ronments where GPS or CDMA antenna placement is not possible. The IxClock
includes provisions for multiple reference sources. At the heart of the IxClock
chassis is a GPS unit. This GPS unit, with its battery pack, may be taken outside
and attached to an included antenna in order to obtain an accurate time lock.
Once a time value is obtained, the IxClock unit may be brought inside where it
will maintain a better than 1 millisecond accuracy for up to 1-3 months depend-
ing on the IxClock version used. The clock accuracy is maintained by a 1 rubid-
ium oscillator. The IxClock may, of course, be permanently connected to the
antenna to maintain a 150 nanosecond accuracy. The functions of the IxClock
module are controlled via a serial link from the chassis chain master. The full set
of timing choices available are shown in Table 8-4 on page 8-6.
Table 8-4. IxClock Chassis Timing Choices
Choice Usage
E1/T1 Time of day is set by the GPS unit and the time base is
maintained by a E1/T1 signal connected to an IxClock connector.
1PPS Time of day is set by the GPS unit and the time is maintained by
a 1 pulse per second signal connected to the IxClock front serial
I/O connector.
GPS Antenna
Carrying Case
Rack Mount
Battery
IxClock Connectors The front and rear connectors on the IxClock module are shown in Figure 8-8 on
page 8-7.
FRONT
Connector Usage
on / off switch Controls AC power to the unit. This should be left on before
attaching the rack mount adapter.
Connector Usage
sync out The sync out connects to an Ixia chassis as the master in a
timing chain. The output goes to the front or rear connector
based on the position of the slide switch.
slide switch If the slide switch is in the up position, the sync out in the rear
of the chassis is enabled. If the slide switch is in the down
position, the sync out in the front of the chassis is enabled.
Rack Mounting If the IxClock module is to be rack mounted, then the rack mount adapter must be
attached to the back of IxClock as shown in Figure 8-9 on page 8-8. Four con-
nectors from the rack mount adapter must be attached to the back of the IxClock
chassis; each connector’s mate is clear and unambiguous. If AC power is to be
used, the on/off switch should be left on. Also, the position of the slide switch
should be determined at this time based on rack installation and expected usage;
refer to Table 8-5 on page 8-7.
Figure 8-9. Connecting the IxClock Chassis to the Rack Mount Adapter
Rack Mount
Adapter
IxClock Chassis
The rack mount adapter is then attached to the IxClock chassis by tightening six
screws, as shown in Figure 8-10 on page 8-8.
Figure 8-10. Attaching the IxClock Chassis to the Rack Mount Adapter
Tighten
Screws
The IxClock, with the rack mount adapter is then slid into the rack mount (which
is presumed to be mounted in a rack) as shown in Figure 8-11 on page 8-9.
Rack Mount
Rack Mount Adapter
IxClock Chassis
The rear of the rack mount is shown in Figure 8-12 on page 8-9.
Making the IxClock When it is not possible to connect the GPS antenna to the IxClock permanently,
Chassis Portable the IxClock may be placed in its carrying case and taken outside in order to
obtain a GPS time lock. The unit may be operated up to 2 hours from a fully
charged battery. The location of the battery, battery charger and carrying case is
shown in Figure 8-13 on page 8-9.
Figure 8-13. Battery, Battery Charger and GPS Antenna Location in IxClock
Carrying Case
Battery Charger
The supplied GPS antenna should be mounted in the left, front pocket of the case
and the battery should go in the middle compartment. When the battery charger is
in use, the charger should be plugged into a wall socket and the longer cable con-
nected to the top of the battery unit. The battery’s rotary switch should be set to
the Charge position. A battery will reach full charge within 8 hours.
In order to prepare the unit for portable use, the power extension battery cable
should be connected to the battery as shown in Figure 8-14 on page 8-10.
Battery Cable
The battery cable should be connected to the battery with the case itself; there is a
cutout between the left and center compartments to accommodate the cable con-
nector. Both the battery cable and the GPS antenna cable should be threaded to
the rear compartment through a grommet located at the bottom of the left pocket
of the case, as shown from the rear in Figure 8-15 on page 8-10.
Grommet
Battery and
GPS cables
The battery and antenna cables are then attached to the front of the IxClock unit
as shown in Figure 8-16 on page 8-11. Note that if the rack mount adapter has
been attached to the IxClock chassis, it need not be removed in order to place it in
the case.
All zippers and velcro straps may now be closed. For best results, the case should
be taken to a place that has a clear view of the sky. The battery should be set to
the Discharge position and kept in that position until it is connected to a perma-
nent power source. When the battery is set to discharge, the Lock and Pwr lights
will be lit while the unit performs a self-test. The Lock light will then extinguish
until a GPS lock has occurred at which point, it will blink at a 1/2 hz rate. The
first time a lock is obtained, it may require up to 30 minutes. Subsequent locks
may be obtained within 15 minutes, if the unit has been moved less than 1/4 mile.
The time to obtain a lock can be reduced by choosing a location with an unob-
structed view of the sky.
The unit should then be moved to its permanent position and AC or DC power
applied to one of the rear connectors, either on the IxClock unit itself or to the
rack-mount, if appropriate. The GPS antenna may be detached at any point in this
process, but the front 48VDC connector should not be removed until a rear power
source is attached.
Ixia Chassis To complete the connections, the Sync Out port on the front or rear (depending
Connections on the slide switch - see Table 8-5 on page 8-7) and a 9-pin RS-232 cable from
the front or rear to the first Ixia chassis which will hold load modules. A null-
modem cable is required. The rear control connector is normally used for rack-
mount applications. The front connector may be used instead or in addition to
supply the 1PPS input. The pin-out for the front control connector is shown in
Table 8-6 on page 8-11.
Table 8-6. IxClock Front Control Connector Pin-Out
Pin Usage
4 12VDC GND. Short this pin to pin 5 if the RS-232 signals are to be
used from the front connector.
Pin Usage
8 +1PPS Signal
9 -1PPS Signal
Thus, if the front control connector is to be used for connection to an Ixia chassis,
a null modem cable which shorts pins 4 and 5 should be used. A 1PPS timing
source may be connected through the use of pins 8 and 9 on the connector.
A number of LEDs are available on the IXIA 100’s front panel, as described in
Table 8-7 on page 8-12.
Table 8-7. IXIA 100 Front Panel LEDs
LED Usage
Time Stamp The number of LEDs lit indicates the time quality available from
the GPS unit. Three LEDs lit indicates best quality.
Physical
Environmental
Temperature
Humidity
IxClock Specifications
The module specifications are contained in Table 8-9 on page 8-13.
Table 8-9. IxClock Specifications
General Rack-mounted
Physical
Environmental
Temperature
Humidity
Modules
The 10/100 family of load modules implements Ethernet interfaces that may run
at 10Mbps or 100Mbps. Different numbers of ports and interfaces are available
for the different board types. The features available for these load modules are
included in three tables starting with Table 1-5 on page 1-11.
One of the family’s modules (the LM100TXS8) is shown in Figure 9-1 on page
9-1. The face plate for the same module (populated with 4 ports) is shown in
Figure 9-2 on page 9-1.
Specifications
The load module specifications are contained in Table 9-1 on page 9-2. Note that
the -3 modules are not included in the table; their limitations versus the non-3
version are discussed in Ixia Load Modules on page 1-3.
Table 9-1. 10/100 Load Module Specifications
# ports 8 4 (LM100TX) 2 4
2 (LM100TX2)
-3 Card Available? N Y N N
Data Rate 10 / 100 Mbps 10 / 100 Mbps 10 / 100 Mbps 10 / 100 Mbps
Captured packet size 12-13k bytes 12-64k bytes 12-64k bytes 12-64k bytes
Preamble size: min- 2-255 bytes 2-255 bytes 2-255 bytes 2-255 bytes
max
Frame size: min-max 12-64k bytes 12-64k bytes 12-64k bytes 12-64k bytes
Inter-frame gap: 10Mbps: 800ns- 10Mbps: 800ns- 10Mbps: 800ns- 10Mbps: 800ns-
min-max 17sec in 400ns 17sec in 400ns 17sec in 400ns 17sec in 400ns
steps steps steps steps
100Mbps: 80ns- 100Mbps: 80ns- 100Mbps: 80ns- 100Mbps: 80ns-
170sec in 40ns 170sec in 40ns 170sec in 40ns 170sec in 40ns
steps steps steps steps
Inter-burst gap: min- 10Mbps: 800ns- 10Mbps: 800ns- 10Mbps: 800ns- 10Mbps: 800ns-
max 17sec in 400ns 17sec in 400ns 17sec in 400ns 17sec in 400ns
steps steps steps steps
100Mbps: 80ns- 100Mbps: 80ns- 100Mbps: 80ns- 100Mbps: 80ns-
170sec in 40ns 170sec in 40ns 170sec in 40ns 170sec in 40ns
steps steps steps steps
Inter-stream gap: 10Mbps: 800ns- 10Mbps: 800ns- 10Mbps: 800ns- 10Mbps: 800ns-
min-max 17sec in 400ns 17sec in 400ns 17sec in 400ns 17sec in 400ns
steps steps steps steps
100Mbps: 80ns- 100Mbps: 80ns- 100Mbps: 80ns- 100Mbps: 80ns-
170sec in 40ns 170sec in 40ns 170sec in 40ns 170sec in 40ns
steps steps steps steps
Port LEDs
Each LM100TXS8 port incorporates a set of 2 LEDs, as described in Table 9-3
on page 9-3.
Table 9-2. LM100TXS8 Port LEDs
Green Transmitting
Yellow Link
Green Receiving
All other 10/100 ports incorporate a set of 6 LEDs, as described in Table 9-3 on
page 9-3.
Table 9-3. 10/100 Port LEDs
Link Green if link established. For Mii and RMii boards, Red if no
transceiver is detected.
Trig Follows the state of the Trigger Out pin, which is programmed
via User Defined Statistic 1.
Pin Signal
1 Port 1 – 40 ns high pulse for each packet matching User Defined Statistic 1
2 Port 2 – 40 ns high pulse for each packet matching User Defined Statistic 1
3 Port 3 – 40 ns high pulse for each packet matching User Defined Statistic 1
4 Port 4 – 40 ns high pulse for each packet matching User Defined Statistic 1
Statistics
Statistics for 10/100 cards, for various modes of operation may be found in Table
E-8 on page E-28.
Modules
The 10/100/1000 family of load modules implements Ethernet interfaces that run
at 10Mbps, 100Mbps or Gigabit (1000 Mbps) speeds. Different numbers of ports
and interfaces are available for the different board types. The features available
for these load modules are included in three tables starting with Table 1-5 on
page 1-11.
One of the modules in this family, the LM1000TXS4, is shown in Figure 10-1 on
page 10-1.
Specifications
The load module specifications are contained in Table 10-2 on page 10-3. Note
that the -3 modules are not included in the table; their limitations versus the non-
3 version are discussed in Ixia Load Modules on page 1-3.
Table 10-1. 10/100/1000 Load Module Specifications
LM1000T-5 LM1000TXS4
# ports 2 4
-3 Card Available N N
LM1000T-5 LM1000TXS4
Port LEDs
Each LM1000T-5 port incorporates a set of 8 LEDs, as described in Table 10-2
on page 10-3.
Table 10-2. 10/100/1000 Port LEDs
Trigger Follows the state of the Trigger Out pin, which is programmed via
User Defined Statistic 1.
Link Green for 1000 Mbps link, alternating green and orange for 100
Mbps link, orange for 10 Mbps link and off for no link.
Rx/Err Green during error free reception and red if errors are received.
Trigger Follows the state of the Trigger Out pin, which is programmed via
User Defined Statistic 1.
Pin Signal
1 Port 1 – 10 ns high pulse for each packet matching User Defined Statistic 1
2 Port 2 – 10 ns high pulse for each packet matching User Defined Statistic 1
The LM1000TXS4 sends a 660ns negative pulse when user defined statistic 1 is
true.
Statistics
Statistics for 10/100/1000 cards, under various modes of operation may be found
in Table E-8 on page E-28, Table E-9 on page E-30 and Table E-12 on page E-
40.
The 100 family of load modules implements Ethernet interfaces that may run at
100Mbps. Different numbers of ports and interfaces are available for the differ-
ent board types. The features available for these load modules are included in
three tables starting with Table 1-5 on page 1-11.
One of the modules in this family (the LM100FX) is shown in Figure 11-1 on
page 11-1. The face plate for the same module is shown in Figure 11-2 on page
11-1.
Specifications
The load module specifications are contained in Table 11-2 on page 11-2. Note
that the -3 modules are not included in the table; their limitations versus the non-
3 version are discussed in Ixia Load Modules on page 1-3.
Table 11-1. 100 Load Module Specifications
LM100FX LM100FXSM
# ports 4 4
-3 Card Available N N
Port LEDs
Each 100 port incorporates a set of 6 LEDs, as described in Table 11-2 on page
11-2.
Table 11-2. 100 Port LEDs
Link Green if link established. For Mii and RMii boards, Red if no
transceiver is detected.
Trig Follows the state of the Trigger Out pin, which is programmed via
User Defined Statistic 1.
Pin Signal
1 Port 1 – 40 ns high pulse for each packet matching User Defined Statistic 1
2 Port 2 – 40 ns high pulse for each packet matching User Defined Statistic 1
3 Port 3 – 40 ns high pulse for each packet matching User Defined Statistic 1
4 Port 4 – 40 ns high pulse for each packet matching User Defined Statistic 1
Statistics
Statistics for 100Mbps cards, under various modes of operation may be found in
Table E-8 on page E-28.
Modules
The Gigabit family of load modules implements copper and fiber Ethernet inter-
faces that may run at 1000Mbps. Different numbers of ports and interfaces are
available for the different board types. The features available for these modules
are included in three tables starting with Table 1-5 on page 1-11.
One of the modules in this family, the LM1000SX, is shown in Figure 12-1 on
page 12-1. The face plate for the same module is shown in Figure 12-2 on page
12-1.
Specifications
The load module specifications are contained in Table 12-2 on page 12-3. Note
that the -3 modules are not included in the table; their limitations versus the non-
3 version are discussed in Ixia Load Modules on page 1-3. A special capability of
Gigabit modules is the ability to echo all received packets back out to the net-
work. This feature should never be used in a live network, as it will likely crash
the network.
Table 12-1. Gigabit Load Module Specifications
# ports 2 2 1 4
(LM1000GBIC-
P1)
2 (LM1000
GBIC)
-3 Card Available Y Y N N
Data Rate 1000 Mbps 1000 Mbps 1000 Mbps 1000 Mbps
Frame size: min-max 40-64k 40-64k 40-64k bytes 24-124 bytes (10/100)
bytes bytes
Port LEDs
Each Gigabit port incorporates a set of 8 LEDs, as described in Table 12-2 on
page 12-3.
Table 12-2. Gigabit Port LEDs
Trig Follows the state of the Trigger Out pin, which is programmed via
User Defined Statistic 1.
Pin Signal
1 Port 1 – 10 ns high pulse for each packet matching User Defined Statistic 1
2 Port 2 – 10 ns high pulse for each packet matching User Defined Statistic 1
Statistics
Statistics for Gigabit cards, under various modes of operation may be found in
Table E-12 on page E-40 and Table E-9 on page E-30.
Load Modules
The Ethernet/USB load module implements USB and Ethernet interfaces that
may run at USB speeds (12Mbps) or 10Mbps. The features available for this load
modules is shown in three tables starting with Table 1-5 on page 1-11.
The LMUSB2 is shown in Figure 13-1 on page 13-1. The face plate for the same
module is shown in Figure 13-2 on page 13-1.
Specifications
The load module specifications are contained in Table 13-2 on page 13-2. Note
that the -3 modules are not included in the table; their limitations versus the non-
3 version are discussed in Ixia Load Modules on page 1-3.
Table 13-1. USB Load Module Specifications
# ports 4 4
-3 Card Available N N
Port LEDs
Each USB port incorporates a set of 4 or 6 LEDs, as described in Table 13-2 on
page 13-2 and Table 13-3 on page 13-3.
Table 13-2. USB Port LEDs – USB Mode
LED Usage
Label
Trig Follows the state of the Trigger Out pin, which is programmed via
User Defined Statistic 1.
Pin Signal
1 Port 1 – 40 ns high pulse for each packet matching User Defined Statistic 1
2 Port 2 – 40 ns high pulse for each packet matching User Defined Statistic 1
3 Port 3 – 40 ns high pulse for each packet matching User Defined Statistic 1
4 Port 4 – 40 ns high pulse for each packet matching User Defined Statistic 1
Statistics
Statistics for USB cards, under various modes of operation may be found in
Table E-8 on page E-28 and Table E-11 on page E-36.
Load Modules
One of the modules in this family, the LMOC12c, is shown in Figure 14-1 on
page 14-1. The face plate for the same module is shown in Figure 14-2 on page
14-1.
Specifications
The load module specifications are contained in Table 14-4 on page 14-3.
Table 14-1. OC12c/OC3c Load Module Specifications
LMOC12c / LMOC12cSM
# ports 2
-3 Card Available N
1. Captured Packet Size Note: at 100% line rate. Smaller values are possible at
lower line rates.
2. Requires that packets be larger than 70 bytes when operating at full line rate.
3. Correct data rates can only be maintained with a minimum number of packet,
depending on packet size. For OC12 operation, the numbers of packets are
required for the indicated ranges of packet sizes:
Table 14-2. OC12 Minimum Number of Packets
45 or less 30
46 - 47 8
48 - 54 7
55 - 63 6
64 - 84 5
85 - 129 4
130 - 199 3
200 - 499 2
500+ 0
For OC3 operation, the numbers of packets are required for the indicated
ranges of packet sizes:
Table 14-3. OC3 Minimum Number of Packets
34 or less 4
35 - 64 3
65 - 274 2
275+ 0
Port LEDs
Each OC12c/OC3c port incorporates a set of 4 or 6 LEDs, as described in Table
14-4 on page 14-3.
Table 14-4. LMOC12c Port LEDs
Pin Signal
1 Port 1 – 10 ns high pulse for each packet matching User Defined Statistic 1
2 Port 2 – 10 ns high pulse for each packet matching User Defined Statistic 1
Pin Signal
Optical Specifications
The optical characteristics for the OC12c/OC3c cards are described in Table 14-6
on page 14-4.
Table 14-6. LMOC12c Optical Specifications
Average Output Power– Min/Max -19 dBM / -14 dBM -15 dBM / -8 dBM
Statistics
Statistics for OC12c cards, under various modes of operation may be found in
Table E-13 on page E-43.
Modules
The OC48c family of load modules implements Optical Carrier interfaces that
runs at OC48 speeds. The interface operates in concatenated mode, as opposed to
channelized mode. Different numbers of ports and interfaces are available for the
different board types. Cards are available that perform Packet Over Sonet testing,
Bit Error Rate Testing or both. A POS card with variable timing support is also
available. The features available for these load modules are included in three
tables starting with Table 1-5 on page 1-11.
One of the modules in this family, the LMOC48cBert, is shown in Figure 15-1
on page 15-1. The face plate for the same module is shown in Figure 15-2 on
page 15-1.
The currently available part numbers are shown in Table 15-1 on page 15-2.
Table 15-1. Currently Available OC48 modules
Specifications
The load module specifications are contained in Table 15-3 on page 15-4. Note
that the -3 modules are not included in the table; their limitations versus the non-
3 version are discussed in Ixia Load Modules on page 1-3.
Table 15-2. OC48 Load Module Specifications
# ports 1 1 1 1
Frequency The OC48 VAR allows a variation of +/- 100 parts per million (ppm) from the
Adjustment clock source’s nominal frequency, via a DC voltage input into the BNC jack
marked “DC IN” on the front panel. The variation is from the lowest frequency
when DC IN is 0 V, to highest frequency when DC IN is 3.3 V. The input voltage
should be used only within this range, although the DC IN circuitry is designed to
withstand +/- 30 V in the case of accidental overdrive from a function generator.
The input has a single-pole low pass at 16 Hz to keep injected noise from causing
a violation of OC48 jitter specifications. As a result, the system should be given
50 to 100 milliseconds to settle after a voltage step at DC IN.
Frequency The frequency may be monitored via the BNC marked “Freq Monitor.” This out-
Monitoring put provides the OC48 line clock divided by 16. The center frequency is 155.52
MHz. The voltage is 70 mV peak-to-peak into 50 ohms, suitable for direct con-
nection into a frequency counter (such as an HP53181A) via 50 ohm coaxial
cable. The frequency counter should be set for 50 ohm termination in a suitably
sensitive mode
Port LEDs
Each OC48c port incorporates a set of LEDs, as described in Table 15-3 on page
15-4.
Table 15-3. LMOC48c Port LEDs
Trig Follows the state of the Trigger Out pin, which is programmed via
User Defined Statistic 1.
Pin Signal
Optical Specifications
The optical characteristics for the OC48c cards are described in Table 15-5 on
page 15-4.
Table 15-5. LMOC48c Optical Specifications
Manufacturer Sumitomo
Statistics
Statistics for OC48 cards, under various modes of operation may be found in
Table E-14 on page E-48.
Load Modules
The unframed BERT family of load modules implements Optical Carrier inter-
faces that runs at multiple rates. Rates vary from OC-3 to OC-48, including Fibre
Channel and Gigabit Ethernet. A single-rate version that supports OC-3/OC-12
only is also available.
Transmit port
Receive port
Receive port
Transmit port
Note that the connectors for odd versus even port numbers are reversed with
respect to each other. For odd numbered ports, the transmit port is on the top. For
even numbered ports, the transmit port is on the bottom. The labels on the face
plate relate to the Tx, Rx and LOS LEDs which are next to the connectors, not to
the connectors themselves.
The currently available part numbers are shown in Table 16-1 on page 16-2.
Table 16-1. Currently Available OC48 modules
Specifications
The load module specifications are contained in Table 16-2 on page 16-3.
Table 16-2. Unframed BERT Load Module Specifications
# ports 8 8 8
LEDs
The lower portion of the card displays a set of LEDs, as seen in Table 16-3 on
page 16-2 and described in Table 16-4 on page 16-4.
Table 16-4. Unframed Bert Card-Level LEDs
Int (Clock) Off if the external clock is selected. Blinks green to indicate the
clock speed selected:
• SONET: 1 time then pauses
• SONET FEC: 2 times then pauses
• Fibre Channel: 3 times then pauses
• Gigabit Ethernet: 4 times then pauses
Ext (Clock) Green when the External Clock is selected, and off otherwise.
Each unframed Bert port incorporates a set of LEDs, as described in Table 16-5
on page 16-5.
Table 16-5. Unframed Bert Per-Port LEDs
Optical Specifications
The optical characteristics for the unframed Bert cards are described in Table 16-
6 on page 16-5.
Table 16-6. Unframed Bert Optical Specifications
Statistics
Statistics for unframed Bert cards may be found in Table E-14 on page E-48.
Modules
The OC192c family of load modules implements Optical Carrier interfaces that
run at OC192 speeds. The interface operates in concatenated mode, as opposed to
channelized mode. Different numbers of ports and interfaces are available for the
different board types. Cards are available that perform Packet Over Sonet testing,
Bit Error Rate Testing or both. The features available for these load modules are
included in are included in three tables starting with Table 1-5 on page 1-11.
The Ixia VSR modules, which were developed in accordance with the OIF
Implementation Agreement VSR-1, use twelve parallel multi-mode fiber optic
lines operating at 1.25Gbps per channel, instead of existing 1310nm or 1550nm
serial optics. VSR optics are designed to drive signals over distances less than
300 meters, which is sufficient for interconnecting devices within a service pro-
vider's Point-of-Presence (POP). Over these short distances, VSR optics offer a
significant cost savings compared to intermediate and long-reach serial lasers.
One of the modules in this family (the LMOC192cPOS) is shown in Figure 17-1
on page 17-1. The face plate for the same module is shown in Figure 17-2 on
page 17-2.
where H is the hundreds designator, T is the tens designator, O is the ones desig-
nator and S is the suffix.
LMF boards have no fiber optic interface. It allows for quick validation of serial-
izer and deserializer designs for WAN Packet over Sonet/SDH products operat-
ing at the STS-192c/STM-64 level. The LMF interface is a 300 pin MegaArray
BERG connector, which is an industry standard MSA interface and is compliant
per OIF1999.102.8, SFI-4 specification. A reference clock can be supplied
through this interface ranging in frequency from 25MhHz to 622 MHz. The spec-
ification of this interface may be found in Appendix B, OC192c Emulator Board
(LMF) Interface Specification.
The currently available part numbers are shown in Table 17-1 on page 17-2.
Table 17-1. Currently Available OC192 modules
Specifications
The load module specifications are contained in Table 17-3 on page 17-4. Note
that the -M modules are not included in the table; their limitations versus the non-
M version are discussed in Ixia Load Modules on page 1-3.
Table 17-2. OC192 Load Module Specifications
# ports 1 or 2 1 or 2
-M Card Available Y N
Port LEDs
Each OC192c port incorporates a set of 10 LEDs, as described in Table 17-3 on
page 17-4.
Table 17-3. LMOC192cPOS Port LEDs
Trigger Follows the state of the Trigger Out pin, which is programmed via
User Defined Statistic 1.
Pin Signal
Optical Specifications
The optical characteristics for the OC192c cards are described in Table 17-5 on
page 17-6.
Table 17-5. LMOC192c Optical Specifications
Average Output Power–Min/Max -4 dBM / 0 dBM -4 dBM / 0 dBM -10 dBM / -4 dBM
Receive Sensitive–Min/Max -16 dBM / 0 dBM -15 dBM / 0 dBM -16 dBM / 0 dBM
Statistics
Statistics for OC192 cards, under various modes of operation may be found in
Table E-15 on page E-52.
Load Modules
The 10 Gigabit Ethernet (10GE) family of load modules implements five of the
seven IEEE 8.2.3ae compliant interfaces that run at 10Gbit/second. Cards are
available which offer the following interfaces:
• 10GBASE-R (LAN): 10GBASE-SR, 10GBASE-LR, 10GBASE-ER
• 10GBASE-W(WAN): 10GBASE-LW and 10GBASE-EW
• XAUI
• XENPAK
Figure 18-1 on page 18-2 is a picture of four of the load module in the family.
The currently available part numbers are shown in Table 18-1 on page 18-2.
Refer to Table 17-1 on page 17-2 as well for a listing of OC192c / 10GBASE
combination modules.
Table 18-1. Currently Available 10GE modules
The following additional XAUI accessories are also available. These items are
discussed in Appendix D, XAUI Connector Specifications
Table 18-2. 10GE XAUI Accessories
Specifications
The load module specifications are contained in Table 18-4 on page 18-5.
Table 18-3. 10GB Load Module Specifications
# ports 1 1 1 1 1 1
-M Card Available N N Y N N Y
Inter-frame gap: 3/4ns - 43sec N/A 3.2ns - 42sec 3.2ns - 42sec N/A 3.2ns - 42sec
min-max in 3.4ns in 3.2ns in 3.2ns in 3.2ns
steps steps steps steps
Inter-burst gap: min- 3/4ns - 43sec N/A 3.2ns - 42sec 3.2ns - 42sec N/A 3.2ns - 42sec
max in 3.4ns in 3.2ns in 3.2ns in 3.2ns
steps steps steps steps
Inter-stream gap: 3/4ns - 43sec N/A 3.2ns - 42sec 3.2ns - 42sec N/A 3.2ns - 42sec
min-max in 3.4ns in 3.2ns in 3.2ns in 3.2ns
steps steps steps steps
The LAN and XAUI manufacturing mode boards include a set of features
expanded from other manufacturing mode boards. The LAN-M, XAUI-M boards
includes all of the features of the LAN/XAUI board with the following excep-
tions:
• No support for routing protocols
• No real-time latency, but timestamps are included
• 32 streams in packet stream mode
• 16 streams in advanced scheduler mode
Port LEDs
Each 10GB port incorporates a set of LEDs, as described in the following tables.
Table 18-4. WAN Port LEDs
Link Green if Ethernet link has been established, red otherwise. Link
may be down due to no signal or no PCS lock.
Tx/Pause Green while data is transmitted. Red while flow control frames
are received. Off if no traffic is passing in either direction.
Rx/Error Green while data is received. Red on any Ethernet error. Off if
no frames are received.
Optical Specifications
The optical characteristics for the 10GE cards are described in Table 18-6 on
page 18-6.
Table 18-6. 10GE Optical Specifications
Tx Power (dBm) -5 to -1 -6 to 2 -4 to 0 -4 to 0 -4 to 0
Safety Class 1 Laser Class 1 Laser Class 1 Laser Class 1 Laser Class 1 Laser
XAUI Connectors
The following connectors and adapters are available for the XAUI Load Modules
and are discussed in Appendix D, XAUI Connector Specifications.
• Standard Connector Specifications–the signals carried on the Load Module’s
XAUI connector.
• Front Panel Loopback Connector–a connector used to loopback XAUI sig-
nals at the external connector.
• Standard Cable Specification–the CAB10GE500S1 (20”) and
CAB10GE500S2 (40”) cables.
• SMA Break-Out Box–the BOB10GE500 SMA break-out box.
• XAUI Fujitsu to XENPAK Adapter–an adapter used with Ixia XENPAK load
modules to create a XAUI interface.
• XAUI Tyco Interoperability Backplane HM-Zd Adapter–an adapter used to
connect to the Tyco Interoperability Backplane.
MDIO A Management Data Input/Output (MDIO) interface is provided to the user. The
Ixia Load Module acts as the Station Management entity (STA), and can control
one or more MDIO Manageable Devices (MMD) in the users system. Multiple
MMDs can be attached to the interface. The user can set/read the MDIO control/
status registers inside a MMD via a graphical user interface.
The connector used for the MDIO interface is a 15-pin female D-sub and pro-
vides the user with the ability to add up to two external Mii interfaces compliant
to either 802.3 clause 22 or 802.3ae clause 45. The connector pin assignments,
Mii Interface, signal names, and functional descriptions are listed in Table 18-7
on page 18-7.
Table 18-7. MDC/MDIO Connector Pin Assignments
WARNING: The MDIO on the Ixia XAUI Load Module is 3.3V while the Ixia
XENPAK Load Module, when used with the adapter for XAUI, is 1.2V. The
reason for the difference is that the XENPAK MSA requires 1.2V for MDIO
whereas most XAUI SerDes chips require 3.3V (LVTTL). Therefore, when using
the XAUI Load Module to test a XENPAK transceiver or SerDes, which require
1.2V, a level shifter is needed to convert 3.3V to 1.2V.
The MDIO/MDC interface has a clock line (MDC) and bi-directional data line
(MDIO) as defined in IEEE 802.3ae. In addition to these, a +5Vdc supply, and
data direction control line (DIR) are provided to make interfacing easier for the
user. The +5Vdc output is intended to power buffers and/or optocouplers at the
user-end of the cable. This supply can be turned ON or OFF under software con-
trol through the GUI.
The +5Vdc supply is OFF when the chassis is initially powered-up, or following
a reset.
Reference Clock In/ The XAUI load module provides coaxial connectors for clock input and clock
Out output to allow the DUT to phase-lock with the XAUI interface. When running
off an external clock, the clock input signal must meet the requirements listed in
Table 18-8 on page 18-8 in order to ensure proper performance of the load mod-
ule.
Table 18-8. XAUI Reference Clock Input Requirements
Parameter Characteristic
The clock in/out electrical interface parameters are defined in Table 18-9.
Parameter Characteristic
The load module contains a phase-locked loop (PLL) that reduces the jitter of the
input clock, either from the internal or external clock source. The output of this
PLL is driven out on the REF CLK OUT connector. The bandwidth of the PLL is
approximately 1kHz. The user can modulate the REF CLK IN frequency up to
1kHz, but it is not recommended, as some degradation of the load module’s per-
formance may result.
Trigger Out Values The Load Module provides two outputs that can be used to trigger to external
equipment for the purpose of capturing events. The Trigger-A and Trigger-B
events are independent, TTL pulse and user-defined through IxExplorer or TCL
API.
.XENPAK Connectors
Clock In/Out Two coaxial connectors provide clock input and clock output to allow the user to
phase-lock the XAUI interface with the DUT.
Power Sequencing The Xenpak 2.1 MSA does not specify any particular power sequencing for the
Specification various Xenpak power supply rails (3.3V, 5V, and APS).
Reset Hardware asserts a Reset by bringing Xenpak connector pin 10 low whenever
either of the following conditions is true:
• The Xenpak module is not inserted into the load module; i.e. Xenpak pin 14
is high.
• Xenpak power is turned off.
The hardware continues to assert Reset until both of these items are false. Once
Xenpak Power is asserted, or if a Xenpak is hot-plugged, the system waits 5 sec-
onds for Xenpak initialization (per MSA 2.1). Reset is then de-asserted, and the
system waits an additional 500 ms for any vendor-based reset management to
complete initialization. After this final 500 ms delay, the load module assumes
the Xenpak module is ready for MII access or to transmit and receive.
Pin Signal
Pin Signal
Statistics
Statistics for 10GB cards, under various modes of operation may be found in
Table E-16 on page E-57.
Module
The purpose of the TFM is to provide accurate time, frequency and position as
derived from Coarse Acquisition (C/A) Link 1 (L1) signals transmitted by the
NAVSTAR Global Positioning System (GPS) satellites. The TFM is usable on a
world-wide basis under any weather conditions.
The TFM is completely automatic in satellite acquisition and time and frequency
synchronization.
The TFM receiver will operate when the satellites are 10 degrees above the hori-
zon and their signals are not obstructed. Whenever entered position information
is less accurate than 10 m, the TFM will first have to accurately ascertain its
antenna position by tracking four or more satellites and performing a long term
(24 hours) average of position fixes in order to maintain time and frequency
accuracy and stability within specification. From that point on, the TFM will
require only one satellite (above 10 degrees) to maintain valid time and fre-
quency. However, operation to specified stability requires four or more satellites.
When no satellites are in view, the TFM will continue to output its signals using
the internal disciplined oscillator.
The Time and Frequency Module (TFM) consists of a receiver, antenna unit and
cable. Since the on-board oscillator is a Temperature Compensated Crystal Oscil-
lator (TCXO), it is essential that it be isolated from rapid fluctuations in air tem-
perature. For this reason, operation of the TFM mounted in an enclosure is
required in order to obtain specified stability performance levels.
Specifications
Table A-11. Time and Frequency Module Specifications
TFM
Standard Antenna
Down Converter Antenna Size: 4.4 in dia. x 2.1 in (11.17 cm dia. x 6.85
cm)
Down Converter Antenna Weight: 0.60 lb. (0.272 kg) (including mounting
mast)
Type: RG-59
Attenuation at 1.575 G should be no more
than 10.5 dB per 100 ft. (Belden 9104 or
equivalent)
Type: RG-58
Environmental
Specifications Table A-12. Environmental Specifications
Operating Temperature
Storage Temperature
Humidity
Timing/Frequency All performance specifications are valid when the antenna’s geodetic position is
Performance known within 10 m in WGS-84 and four or more satellites are being tracked. In
Specifications addition, in order to achieve the stated accuracy, the receiver must be mounted
in an enclosure that will eliminate exposure of the internal oscillator to rapid
temperature fluctuations due to air currents.
TFM Specifications
Procedure The TFM antenna unit should have an unobstructed view of the sky. Connect the
cable between the Antenna unit and TFM antenna input connector. If satellites
are visible and the TFM has an accurate position, lock should be achieved within
two minutes.
Satellite Acquisition Time to first satellite acquisition is dependent upon many factors. The following
paragraphs describe some of the possible events which affect satellite acquisition
times. Note that satellite visibility at the receiver site will affect acquisition
times.
If the Time and Frequency receiver was tracking satellites immediately prior to a
momentary power interruption, satellite re-acquisition will be almost immediate
with valid UTC time available within two minutes.
If the current position is unknown or in error by more than 100 km, acquisition
typically requires from 3 to 15 additional minutes to locate current antenna posi-
tion, reacquire satellite almanac and ephemeris data, and deliver UTC time.
If internal almanac data is lost, the time to first satellite acquisition will depend
upon which satellites are visible at the time of power-on. The TFM will attempt
to acquire satellites not knowing which satellites are visible. The satellite search
will be expanded until a satellite is acquired. After first satellite acquisition, time
will be acquired from the satellite and the receiver will return to normal opera-
tion. This procedure may take as little as three minutes to as long as 15 minutes
depending upon current satellite visibility.
Specifications
The specifications given below are the requirements of a fiber optic transponder,
which is normally installed in the 300 pin Berg location. Keeping to these speci-
fications will insure proper operation.
Electrical
Performance
Table B-1. Power Supply Characteristics
Mechanical
Dimensions Table B-5. Electrical Interface
FR_PICLK P TX_PICLK P
TX_PICLK [P/N]
FR_PICLK N TX_PICLK N
REFCLK
SYS_REFCLKIN+
TX_PCLKP
SYS_REFCLKIN[+/-] FOM_PCLK [P/N] TX_PCLKN
SYS_REFCLKIN-
RX_DATAP
RXDATA P[15:0]
TX_REFCLK P
TX_REFCLK N
RXMCLKP
RXMCLKN
RXREFCLKP
RXREFCLKN
K J H G F E D C B A
1 +5V Analog TBD Frame GND RxDout12P TBD RxDout8P Digital GND RxDout4P Digital GND RxDout0P
2 +5V Analog TBD Frame GND RxDout12N TBD RxDout8N Digital GND RxDout4N Digital GND RxDout0N
3 Reserved FFU Reserved FFU TBD Digital GND RxLOPMON Digital GND TBD Digital GND TBD Digital GND
4 +3.3V Analog TBD Frame GND RxDout13P +3.3V Digital RxDout9P Digital GND RxDout5P Digital GND RxDout1P
5 +3.3V Analog TBD Frame GND RxDout13N +3.3V Digital RxDout9N Digital GND RxDout5N Digital GND RxDout1N
6 RxReset Reserved FFU TBD Digital GND Reserved FFU Digital GND TBD Digital GND TBD Digital GND
7 TBD TBD Analog GND RxDout14P +3.3V Digital RxDout10P Digital GND RxDout6P Digital GND RxDout2P
8 TBD TBD Analog GND RxDout14N +3.3V Digital RxDout10N Digital GND RxDout6N Digital GND RxDout2N
9 Reserved FFU Reserved FFU TBD Digital GND Reserved FFU Digital GND Reserved FFU Digital GND RxLCKREF Digital GND
10 -5.2V Analog TBD Analog GND RxDout15P +3.3V Digital RxDout11P Digital GND RxDout7P Digital GND RxDout3P
11 -5.2V Analog TBD Analog GND RxDout15N +3.3V Digital RxDout11N Digital GND RxDout7N Digital GND RxDout3N
12 Reserved FFU Reserved FFU TBD Digital GND Reserved FFU Digital GND Reserved FFU Digital GND Reserved FFU Digital GND
13 -5.2V Analog TBD Analog GND TBD -5.2V Digital RxPOCLKP Digital GND Reserved FFU Digital GND RxREFCLKP
14 -5.2V Analog TBD Analog GND TBD -5.2V Digital RxPOCLKN Digital GND Reserved FFU Digital GND RxREFCLKN
15 Reserved FFU Reserved FFU TBD Digital GND Reserved FFU Digital GND Reserved FFU Digital GND RxLCKREF Digital GND
16 -5V Analog TBD Analog GND TxDin12P TBD TxDin8P Digital GND TxDin4P Digital GND TxDin0P
17 -5V Analog TBD Analog GND TxDin12N TBD TxDin8N Digital GND TxDin4N Digital GND TxDin0N
18 Reserved FFU Reserved FFU Reserved FFU Digital GND LsBIASMON Digital GND LsPOWMON Digital GND Reserved FFU Digital GND
19 +3.3V Analog TBD Analog GND TxDin13P TBD TxDin9P Digital GND TxDin5P Digital GND TxDin1P
20 +3.3V Analog TBD Analog GND TxDin13N TBD TxDin9N Digital GND TxDin5N Digital GND TxDin1N
21 Reserved FFU Reserved FFU Reserved FFU Digital GND LsENABLE Digital GND Reserved FFU Digital GND Reserved FFU Digital GND
22 +3.3V Analog TBD Analog GND TxDin14P +3.3V Digital TxDin10P Digital GND TxDin6P Digital GND TxDin2P
23 +3.3V Analog TBD Analog GND TxDin14N +3.3V Digital TxDin10N Digital GND TxDin6N Digital GND TxDin2N
24 TxRESET Reserved FFU Reserved FFU Digital GND LsBIASALM Digital GND Reserved FFU Digital GND Reserved FFU Digital GND
25 -5.2V Analog TBD Frame GND TxDin15P -5.2V Digital TxDin11P Digital GND TxDin7P Digital GND TxDin3P
26 -5.2V Analog TBD Frame GND TxDin15N -5.2V Digital TxDin11N Digital GND TxDin7N Digital GND TxDin3N
27 Reserved FFU Reserved FFU TBD Digital GND LsTEMPALM Digital GND Reserved FFU Digital GND Reserved FFU Digital GND
28 -5.2V Analog TBD Frame GND TxPICLKP -5.2V Digital TxPCLKP Digital GND Reserved FFU Digital GND TxREFCLKP
29 -5.2V Analog TBD Frame GND TxPICLKN -5.2V Digital TxPCLKN Digital GND Reserved FFU Digital GND TxREFCLKN
30 Reserved FFU Reserved FFU TxLINESEL Digital GND TxREFSEL0 Digital GND Reserved FFU Digital GND TxLOCKERR Digital GND
Specification
Description
The IXIA RMII Test Board can interface with up to 4 RMII channels within one
or more RMII PHYs running on the same reference clock. The connector type is
from the AMP AMPLIMITE family and is the same type used in the regular MII
interface, but with 68 contacts. Except for the reference clock all signals are TTL
compatible with safe levels for 3.3V only inputs on the target board under test.
The reference clock is an LVDS type, described in more detail below. Except for
the reference clock all of the signals use a serial resistor of 51 ohm for termina-
tion. No parallel termination is provided for input signals, since it is expected that
they should also be driven using serial resistors.
MDC/MDIO
The MDC/MDIO signals operate in the same manner as in a conventional MII
PHY. The user designates the PHY addresses present which will be used to com-
municate with each of the PHYs. Note that all 4 ports controlled by a single IXIA
RMII Test Board must have the same upper 3 PHY address bits, i.e. within a
group of 4 PHYs controlled by an IXIA RMII Test Board, the PHY entities are
selected with the least significant 2 bits of the PHY address.
The IXIA RMII Test Board recognizes that a transceiver module is attached by a
pull up/pull down scheme similar to that specified for the conventional MII. The
Test Board has a 24K pull down on the MDIO line and the device under test must
have a 1K pull up on that line.
Once a transceiver module is detected, the IXIA RMII Test Board will scan the
present PHYs. The PHYs can then be loaded with the desired configuration for
that channel. The PHYs will also be continuously polled for link. When link is
found, the respective channel transmit section can then be enabled for RMII
transmission. The receive channel is always enabled.
Connector
IXIA RMII Test Board connector part number (female): AMP 787170-7
AMPLIMITE,.050 Series, 68 pin Mating Connector (male, PCB Mount, Right
Angle): AMP 2-174341-5 (Use this only if you plan to plug the target directly
into the IXIA RMII Test Board without a cable)
There are three ways to connect the evaluation board to the IXIA RMII Test
Board:
1. Using the male connector mentioned above, and plugging the evaluation
board directly to the IXIA RMII Test Board without a cable.
2. Using the same female connector used on the IXIA RMII Test Board (or a
vertical version of it), with a 1’ male to male cable. This cable is a standard
SCSI-3 cable that is available from AMP, part number: 319285-4 (product
description: 68 pos. Amplimite .050”, 1’). Figure 1a illustrates the signal
positions on this connector.
3. Using the Ixia RMII Adapter Cable that translates the 68 pin Amplimite con-
nector to a 38 pin Mictor connector via a very flexible 50 ohm controlled
impedance flat cable. The Mictor connector on the cable is of the plug type,
thus the board under test must have the Mictor receptacle type. Figure 1b
illustrates the signal positions on this connector.
Notes:
1. There is no standard male to female cable and therefore extending a board
(with a cable) that uses option 1 (male connector) is not easily possible.
2. Good signals have been received from CMOS devices driving the 1’ cable
directly via 33 ohm resistors. These devices were specified to drive only 5ma
max DC. However, their dynamic drive capability is unknown to us. We
mention this to help our customers decide whether or not to use buffers to
drive the cable.
Figure C-1 illustrates the signal positions on the IXIA RMII Test Board connec-
tor (the 68 pin Amplimite type). The 4 channels are suffixed 0 through 3 on the
RMII signals described in the specification of the RMII consortium.
A board under test can use a 38 pin Receptacle Mictor Connector with this pin
assignment.
Expansion
The IXIA RMII Test Boards can be expanded to support up to 32 PHY’s in a sin-
gle evaluation board. This may be done by using several connectors on the evalu-
ation board, and connecting them via cables to several adjacent IXIA RMII Test
Boards. Via the IxExplorer GUI or TCL API, the PHY addresses for each RMII
Test Board may be entered. If the reference clock is to originate from the test
equipment, then a single IXIA RMII Test Board designated as board_1 must be
configured via jumpers as the reference clock source, whereas the other boards
must be configured to receive the reference clock. The evaluation board should
assign one connector as connector_1, whose function is to receive the clock from
board_1 via an LVDS receiver. The output of this LVDS receiver becomes the
reference 50MHz clock of the evaluation board. The rest of the connectors must
repeat the reference clock via LVDS transmitters using one device per connector.
If the reference clock is to originate from the evaluation board, then each of the
RMII connectors must be assigned an LVDS driver to deliver the clock to the
respective IXIA RMII Test Board. All the IXIA RMII Test Boards must be con-
figured to receive the reference clock.
The MDC signal must originate from only one IXIA RMII Test Board. The sig-
nal must not be driven toward other IXIA RMII Test Boards because all the
MDC signals in a single IXIA chassis are identical. The MDIO signal should be
bussed across all connectors.
Power
Four pins on the connector are tied to MII_PWR, which can supply up to 1 amp
of current to the unit under test. The voltage is selectable between 3.3V or 5V by
a jumper JP3 as indicated in Table C-1. The front panel LEDs will confirm the
selection.
Table C-1. Voltage Selection Jumper Configuration
Reference Clock
The 50 MHz reference clock can sourced from either the IXIA RMII Test Board
or the DUT. The clock is driven (or received) differentially using an LVDS
driver/receiver chip. The recommended part is the National Semiconductor
DS92LV010A with a termination resistor of 100 ohm. The same part can either
drive or receive. Jumpers JP2 and JP1 control the direction as depicted in Table
C-2.
Table C-2. Selection of Reference Clock Source
Timing Considerations
Figure C-3 shows the timing for outgoing data under typical delay conditions.
The diagram assumes that the IXIA RMII Test Board clocks data on the falling
edge of the clock, which can be selected via the IxExplorer GUI or TCL API. As
the diagram indicates, a setup of 8ns and a hold time of 12ns is provided under
these typical circumstances. If these delays are grossly different in a particular
system, the edge which clocks outgoing data may be changed.
A very similar scenario occurs with the receive data clocked out of the PHY
board. If the user suspects that there may be a setup/hold violation on the RMII
Test Board, the user may change the other clock edge to clock incoming data.
In summary, the IXIA Explorer GUI will allow the user to alter the clock edge
for incoming and outgoing data independently, so that any clock and data delay
combinations can be made to work.
The timing diagram shows outgoing data with respect to clock. It is assumed the
outgoing data in the RMII Test Board is clocked on the falling edge of the clock
as can be selected via the GUI. The 50MHz_PHY clock is shown 180 degrees out
of phase because it is assumed that it undergoes a typical delay of 10ns via the
transmit and receive LVDS devices as well as the cable.
Specifications
Description
The following cable and accessories for the 10GE XAUI cards are described in
this appendix. These include:
• Standard Connector Specifications–the signals carried on the Load Module’s
XAUI connector.
• Front Panel Loopback Connector–a connector used to loopback XAUI sig-
nals at the external connector.
• Standard Cable Specification–the CAB10GE500S1 (20”) and
CAB10GE500S2 (40”) cables.
• SMA Break-Out Box–the BOB10GE500 SMA break-out box.
• XAUI Fujitsu to XENPAK Adapter–an adapter used with Ixia XENPAK load
modules to create a XAUI interface.
• XAUI Tyco Interoperability Backplane HM-Zd Adapter–an adapter used to
connect to the Tyco Interoperability Backplane.
Standard Connector
Specifications
The Ixia XAUI Load Module’s front panel connector is the Fujitsu MicroGiGa.
This connector can be mounted on the Device Under Test (DUT), eliminating the
need for SMA cables. This part is also available directly from Fujitsu as part
number FCN-268D008-G/1D-/2D.The connector is shown in Figure D-1.The
signal names, functional description and connector pin assignments are as shown
in Table D-1.
Figure D-2 shows how the pins are physically arranged within the connector. The
connector is specifically designed for high-speed differential signals on 100 ohm
twisted pairs. Also shown is a cross section of the cable.
Figure D-2. XAUI Connector Contact Details and Cable Cross Section
NOTE: The 50cm max. length suggested in the XAUI section of 802.3ae is a
rough guideline for keeping the losses on PCB traces under 7.5dB. Well
designed cables will usually have much lower losses per meter than PCB
traces, so cables can be much longer than 50cm.
If the DUT uses coaxial connectors for the XAUI interface, a special break-out
box (BOB10GE500) is required in addition to the XAUI cable, as shown in
Figure D-6. The user must provide the sixteen 50-ohm coaxial cables with a male
SMA connector on the end that mates to the BOB. The actual break-out box is
shown in Figure D-6.
Ixia Load
Module
XAUI/SMA
Break-out box
P
N } TX Lane-A
N}
P
RX Lane-A
N}
P
TX Lane-B
N}
P
RX Lane-B
XAUI 20" Cable
N}
P
XAUI Port TX Lane-C
N}
P
RX Lane-C
N}
P
TX Lane-D
N}
P
RX Lane-D
When using coaxial cables for the XAUI interface, extreme care should be taken
to match the electrical lengths of the two cables in each pair. The pairs can be of
different lengths, since the XAUI SerDes should automatically correct for skew
between lanes. Skew between the “P” and “N” lines within a pair, however, can
introduce bit errors. The XAUI edge-rates can be as short as 60ps. Therefore, the
total in-pair skew should be kept below 30ps to avoid bit-errors. Some of this in-
pair skew must be budgeted to the Load Module, Ixia XAUI cable, BOB, and the
DUT. Allocating 10ps of in-pair skew to the coax cables would require length
matching them to within about 0.08” (for RG-174). The propagation velocity of
coax can vary slightly between manufacturers, lots, and as it is bent or stretched.
Therefore, it is recommended that coax cables be kept as short as possible.
Table D-2. XAUI Electrical Interface Performance
Parameter Characteristic
This enables a XENPAK Load Module to act as a XAUI Load Module. How-
ever, the XENPAK Load Module can only run in Ethernet mode and transmit and
verify layer 2 or 3 traffic. Further, there is no D-sub connector for MDIO on the
front panel of the XENPAK Load Module. Both the MDIO and power are avail-
able through pins on the adapter and serve the same function as the D-sub con-
nector on the XAUI Load Module.
Fujitsu Connector
This appendix covers the available statistics for the different card types:
• Statistics for 10/100 Cards and Ethernet/USB Cards in Ethernet Mode. These
cards include:
• 10/100
• 10/100 MII
• 10/100 Reduced MII
• 100 Base FX MultiMode
• 100 Base FX SingleMode
• Ethernet/USB operating in Ethernet mode
• Copper 10/100/1000 running at 10/100 Mbps
• Statistics for 10/100 TXS Modules. These cards include:
• 10/100 TXS8
• Statistics for 10/100/1000 TXS and 1000 SFPS4 Cards. These cards include:
• 10/100/1000 TXS4
• 1000 SFPS4
• Statistics for Ethernet/USB cards in USB Mode. These cards include:
• Ethernet/USB
• Statistics for Gigabit Modules. These cards include:
• 1000 Base SX MultiMode
• 1000 Base LX MultiMode
• 1000 Base SX SingleMode
• GBIC
• Statistics for OC12c/OC3c Modules. These cards include:
• OC12c/OC3c
• Statistics for OC48c Modules with Bert. These cards include:
• OC48c POS
• OC48 POS VAR
• OC48c BERT
• OC48c BERT Rx
• OC48c POS/BERT
• Statistics for OC192c Modules with Bert. These cards include:
• OC192c with optional BERT and 10 Gigabit Ethernet.
• OC192c VSR. Note that all VSR cards have available all of the VSR statis-
tics listed in the VSR section of Table E-6 on page E-8.
• Statistics for 10GE Modules with BERT. These cards include:
• 10 Gigabit Ethernet with optional BERT.
• Statistics for Protocol Server. These statistics are common to all cards which
support the Protocol Server.
Table Organization
Each of the following tables details the statistics available for that set of cards.
Available statistics are controlled by three sets of controls:
From the Explorer tree, select a port and select Filter, Statistics, Receive Mode
from the right-hand panel. Select the tab at the top labelled Statistics. This is
shown below for a Gigabit module with the statistics modes highlighted in a solid
box. The choices here are mutually exclusive. In most cases, when one is selected
new statistics are available at the expense of others.
Figure E-1. Statistics Mode Selection
Statistics Mode
Additional statistics are selected through a set of checkboxes located on the same
Statistics tab, as highlighted in a dashed line. These statistics are always in addi-
tion to those in the Statistics Mode box.
Receive Mode
From the Explorer tree, select a port and select Filter, Statistics, Receive Mode
from the right-hand panel. Select the tab at the top labelled Receive Mode. This is
shown below for a Gigabit module. Not all of the receive modes necessarily
result in additional statistics. For example, in the figure below First Time Stamp
and ISL Encapsulation do not affect statistics. Otherwise, the checkboxes gener-
ally result in additional statistics.
Figure E-2. Receive Mode Selection
Key To Tables
Table E-1 lists the headings that appear in the tables in this appendix and their
correspondence to IxExplorer dialogs and selections.
Table E-1.Key for Statistics Table
Heading Item IxExplorer Dialog IxExplorer Label
Statistics Mode
Extra Statistics
Checkboxes
Receive Mode
The statistics mode is controlled by the use of the stat mode command. Figure
E-1 on page E-3 lists the available choices and their correspondence to
IxExplorer choices and the labels used in the tables in this appendix.
Table E-2.Tcl stat mode Options
Option IxExplorer Choice
Access to Statistics
Most statistics are accessed through the use of stat command. VSR statistics are
access through the use of the vsrStat command.
Receive Mode
The receive mode is controlled through the use of the port receiveMode option.
The choices available are or’d together. list the bits available to control the
receive mode.
Table E-3.Tcl port receive Options
Option IxExplorer Choice
The statistics mode is controlled by the use of the stat.mode member. Table E-1
on page E-3 lists the available choices and their correspondence to IxExplorer
choices and the labels used in the tables in this appendix.
Table E-4.C++ stat Members
Member Value IxExplorer Choice
Access to Statistics
Most statistics are accessed through the use of TCLStatistics class. VSR statis-
tics are access through the use of the TCLvsrStat class.
Receive Mode
The receive mode is controlled through the use of the port.receiveMode mem-
ber. The choices available are or’d together. list the bits available to control the
receive mode.
Table E-5.Tcl port receive Options
Member Value IxExplorer Choice
Description of Statistics
Table E-6 on page E-8 lists all of the available statistics, along with an explanation of those statistics.The following three col-
umns are used:
• Counter – the name of the statistics as it appears in IxExplorer. These are organized by general category, as used in the
remaining tables in this appendix.
• Interpretation – the description of the statistics.
• Internal Baseame – the internal basename used to describe the statistics in the TCL and C++ API. The base name is used to
form other names:
• TCL stat command options – the basename is the name of the option.
• TCL stat command get sub-command counterType argument – the counterType name needed to fetch a particular sta-
tistic is formed by prepending the letters stat to the basename, while capitalizing the first letter of the statistic. For exam-
ple, for basename alignmentErrors, the counterType name is statAlignmentErrors.
Description of Statistics
• C++ stat class members – the basename is the name of the member.
• C++ stat command get method counterType argument – the counterType name needed to fetch a particular statistic is
formed by prepending the letters stat to the basename, while capitalizing the first letter of the statistic. For example, for
basename alignmentErrors, the counterType name is statAlignmentErrors.
.
E-7
E
Table E-6.Statistics Counters
E-8
Description of Statistics
User Configurable
User Defined Stats 1 and 2 & Rate Counters that increment each time the statistics conditions are met. The user- userDefinedStat1
defined statistics conditions are set up in the Capture Filter window. userDefinedStat2
Capture Trigger (UDS3) & Rate A counter that increments each time the capture trigger conditions are met, as captureTrigger
defined in the Capture Filter window.
Capture Filter (UDS4) & Rate A counter that increments each time the capture filter conditions are met, as captureFilter
defined in the Capture Filter window.
User Defined Stats 5 and 6 & Rate Counters that increment each time the statistics conditions are met. The user- streamTrigger1
defined statistics conditions are set up in the Capture Filter window. (N/A to OC192 streamTrigger2
modules.)
States
Link State “Up” when a link is established with another device, “Loopback” when the port has link
loopback enabled, “Down” when there is no connection to another device. (See
note 2 in Notes)
Line Speed “10”, “100”, or “1000” (denoting Mbps) and OC-12, OC-3 or OC-48 for POS lineSpeed
modules. (See note 6 in Notes)
Duplex Mode “Half” or “Full”. Half duplex only applies to 10/100 Load Modules. (See note 7 in duplexMode
Notes)
Transmit State Not shown in IxExplorer. The current transmit state of the port. See the stat transmitState
command in the Tcl Development Guide and C++ Development Guide.
Capture State Not shown in IxExplorer. The current capture state of the port. See the stat captureState
command in the Tcl Development Guide and C++ Development Guide.
Ixia Hardware Guide
Pause State Not shown in IxExplorer. The current pause state of the port. See the stat pauseState
command in the Tcl Development Guide and C++ Development Guide.
Common
Frames Sent & Rate A counter that increments only when a frame is successfully transmitted - this framesSent
counter does not count collision attempts.
Ixia Hardware Guide
Valid Frames Received & Rate The valid frame size is from 64 bytes to 1518 bytes inclusive of FCS, exclusive of framesReceived
preamble and SFD and must be an integer number of octets. This 32 bit counter
only counts frames with good FCS. VLAN tagged frames that are greater than
1518 but less than 1522 bytes in size will also be counted by this counter.
Bytes Sent & Rate A counter that counts the total number of bytes transmitted. bytesSent
Bytes Received & Rate A counter that counts the total number of bytes received. bytesReceived
Transmit Duration
Quality of Service
Quality of Service 0 - 7 & Rate Counters which increment each time a frame with that particular QoS setting is qualityOfService0
received. qualityOfService1
(N/A to OC192-3) ...
Framer Stats
Framer CRC Errors CRC errors detected by the POS framer. framerFCSErrors
Framer Min Length & Rate POS frames received with less than the minimum length. framerMinLength
Framer Max Length & Rate POS frames received with more than the maximum length. framerMaxLength
Description of Statistics
Framer Frames Sent Reserved for future use. framerFramesTx
Checksum Stats
Description of Statistics
TCP Packets Received The number of TCP packets received. tcpPackets
UDP Checksum Errors The number of UDP checksum errors detected. udpChecksumErrors
TCP Checksum Errors The number of TCP checksum errors detected. tcpChecksumErrors
Data Integrity
Data Integrity Frames The number of data integrity frames received. dataIntegrityFrames
Data Integrity Errors The number of data integrity errors detected. dataIntegrityErrors
Sequence Checking
Small Sequence Errors The number of times when the current sequence number minus the previous smallSequenceErrors
sequence number is less than or equal to the error threshold and not negative, or
when the current sequence number is equal to the previous sequence number.
Big Sequence Errors The number of times when the current sequence number minus the previous bigSequenceErrors
sequence number is greater than the error threshold.
Reverse Sequence Errors The number of times when the current sequence number is less than the previous reverseSequenceErrors
sequence number.
Total Sequence Errors The sum of the small, bug and reverse sequence errors. totalSequenceErrors
General
Transmit Ping Reply Number of Ping replies generated. (N/A to OC192-3) txPingReply
Transmit Ping Request Number of Ping requests received. (N/A to OC192-3) txPingRequest
Receive Ping Reply Number of Ping replies received. (N/A to OC192-3) rxPingReply
Receive Ping Request Number of Ping requests generated. (N/A to OC192-3) rxPingRequest
VLAN Dropped Frames The number of VLAN frames dropped by the Protocol Server. protocolServerVlanDropped
Frames
Asynchronous Frames Sent The number of frames sent as a result of user request asynchronousFramesSent
Scheduled Frames Sent The number of frames origination from the stream engine. scheduledFramesSent
Port CPU Frames Sent The number of frames originating from the port’s CPU as opposed to the stream portCPUFramesSent
engine.
BGP
BGP Sessions Configured The number of BGP4 sessions that were configured. bgpTotalSessions
BGP Sessions Established The number of configured BGP4 sessions that established adjacencies. bgpTotalSessionsEstablished
ISIS
Description of Statistics
ISIS L1 Sessions Configured The total number of level 1 configured sessions. isisSessionsConfiguredL1
ISIS L2 Sessions Configured The total number of level 2 configured sessions. isisSessionsConfiguredL2
ISIS L1 Sessions Up The total number of level 1 configured sessions that are fully up. isisSessionsUpL1
ISIS L2 Sessions Up The total number of level 2 configured sessions that are fully up. isisSessionsUpL2
E-11
E
Table E-6.Statistics Counters
E-12
Description of Statistics
OSPF
OSPF Total Sessions The number of OSPF sessions that were configured. ospfTotalSessions
OSPF Neighbors in Full State The number of OSPF neighbors that are fully up. ospfFullNeighbors
RSVP
RSVP Ingress LSPs Configured The number of ingress LSPs configured. rsvpIngressLSPsConfigured
RSVP Ingress LSPs Up The number of ingress LSPs configured and running rsvpIngressLSPsUp
RSVP Egress LSPs Up The number of egress LSPs configured and running rsvpEgressLSPsUp
LDP
LDP Sessions Configured The number of LDP sessions configured for targeted peers ldpSessionsConfigured
LDP Sessions Up The number of LDP sessions configured and running with targeted peers ldpSessionsUp
LDP Basic Sessions Up The number of LDP sessions up for broadcast peers ldpBasicSessionsUp
Ethernet
Fragments & Rate A counter that counts the number of frames less than 64 bytes in size with a bad fragments
FCS.
Undersize & Rate A counter that counts the number of frames less than 64 bytes in size with a good undersize
FCS.
Oversize & Rate A counter that counts the number of frames greater than 1518 bytes in size. The oversize
following modules count oversize packets with both good and bad FCSs: 10/100
TX, 10/100 MII, 10/100 RMII and Ethernet/USB. All other modules include oversize
packets with a good FCSs only.
Ixia Hardware Guide
CRC Errors & Rate A counter that counts all valid size frames that have CRC errors. fcsErrors
Vlan Tagged Frames & Rate A counter that counts the number of VLAN tagged frames. vlanTaggedFramesReceived
Line Errors & Rate A counter that counts the number of 4B/5B (100Mbps) or 8B/10B (Gigabit) symbol symbolErrors
errors.
Ixia Hardware Guide
Flow Control Frames & Rate A counter that counts the number of PAUSE frames received. This counter only flowControlFrames
increments when Flow Control is enabled for that port (using the port properties
dialog).
10/100
Alignment Errors & Rate A counter that counts all valid size frames that are not an even multiple of 8 bits alignmentErrors
and have an invalid FCS. The frame is truncated to the nearest octet and then the
FCS is validated. If the FCS is bad, then this frame is counted as an alignment
error.
Dribble Errors & Rate A counter that counts all valid size frames that are not an even multiple of 8 bits dribbleErrors
and have a valid FCS. The frame is truncated to the nearest octet and then the
FCS is validated. If the FCS is good, then this frame is counted as a dribble bit
error.
Collisions & Rate A counter that counts all occurrences (only one count per frame or fragment) of the collisions
Collision Detect signal from the physical layer controller.
Late Collisions & Rate A counter that counts all collisions that occur after the 512th bit time (preamble lateCollisions
included) or after the 56th byte.
Collision Frames & Rate A counter that counts the number of frames received that were retransmitted due collisionFrames
to one or more collisions.
Excessive Collision Frames & Rate A counter that counts the number of frames that were attempted to be sent but had excessiveCollisionFrames
16 or more consecutive collisions.
Gigabit
Description of Statistics
Oversize and CRC Errors & Rate A counter that counts the number of frames greater than 1518 bytes in size with a oversizeAndCrcErrors
bad FCS.
Line Error Frames & Rate A counter that counts the number of frames received that contain symbol errors. symbolErrorFrames
Byte Alignment Error & Rate A counter that counts the number of times that a comma character is detected to synchErrorFrames
be out of alignment.
E-13
POS
E
Table E-6.Statistics Counters
E-14
Description of Statistics
Section LOS “OK” or “ALARM” during loss of signal. (See note 3 in Notes) sectionLossOfSignal
Section LOF “OK” or “ALARM” during loss of frame. (See note 3 in Notes) sectionLossOfFrame
Section BIP(B1) & Rate The number of section bit interleaved parity errors. sectionBip
Line AIS “OK” or “ALARM” during a line alarm indication signal condition. (See note 3 in lineAis
Notes)
Line RDI “OK” or “ALARM” during a remote defect indication. (See note 3 in Notes) lineRdi
Line REI(FEBE) & Rate A count of the number of remote error indicate conditions. lineRei
Line BIP(B2) & Rate The number of line bit interleaved parity errors. lineBip
Path AIS “OK” or “ALARM” during a path alarm indication signal condition. (See note 3 in pathAis
Notes)
Path RDI “OK” or “ALARM” during a path remote defect indication. (See note 3 in Notes) pathRdi
Path REI(FEBE) & Rate A count of the number of path remote error indicate conditions pathRei
Path BIP(B3) & Rate The number of path bit interleaved parity errors. pathBip
Path LOP “OK” or “ALARM” during a loss of pointer condition. (See note 3 in Notes) pathLossOfPointer
Path PLM(C2) Either “OK” or “ALARM” along with the current received path signal label byte. pathPlm
“ALARM” will occur when a path signal label mismatch occurs. (See note 5 in
Notes)
Section BIP Errored Seconds A count of the number of seconds during which (at any point during the second) at sectionBipErroredSecs
least one section layer BIP was detected.
Section BIP Severely Errored Seconds A count of the number of seconds during which K or more Section layer BIP errors sectionBipSeverlyErroredSec
Ixia Hardware Guide
Section LOS Seconds A count of the number of seconds during which (at any point during the second) at sectionLossOfSignalSecs
least one section layer LOS defect was present.
Line BIP Errored Seconds A count of the seconds during which (at any point during the second) at least one lineBipErroredSecs
Line layer BIP was detected.
Ixia Hardware Guide
Line REI Errored Seconds A count of the seconds during which at least one line BIP error was reported by the lineReiErroredSecs
far end.
Line AIS Alarmed Seconds A count of the seconds during which (at any point during the second) at least one lineAisAlarmSecs
Line layer AIS defect was present.
Line RDI Unavailable Seconds A count of the seconds during which the line is considered unavailable at the far lineRdiUnavailableSec
end.
Path BIP Errored Seconds A count of the seconds during which (at any point during the second) at least one pathBipErroredSecs
Path BIP error was detected.
Path REI Errored Seconds A count of the seconds during which (at any point during the second) at least one pathReiErroredSecs
STS Path error was reported by the far end.
Path AIS Alarmed Seconds A count of the seconds during which (at any point during the second) an AIS defect pathAisAlarmSec
was present)
Path AIS Unavailable Seconds A count of the seconds during which the STS path was considered unavailable. pathAisUnavailableSecs
Path RDI Unavailable Seconds A count of the seconds during which the STS path was considered unavailable at pathRdiUnavailableSec
the far end.
Input Signal Strength (dB) (OC-192) This stat monitors the receive optical input power. (See note 8 in Notes) inputSignalStrength
SRP
Description of Statistics
SRP Data Frames Received The number of data frames received. IPv4 frames fall in this category. srpDataFramesReceived
SRP Discovery Frames Received The number of discovery type frames received. srpDiscoveryFramesReceived
SRP IPS Frames Received The number of IPS type frames received. srpIpsFramesReceived
SRP Header Parity Errors The number of SRP frames received with SRP header parity error. This includes all srpParityErrors
frame types.
E-15
E
Table E-6.Statistics Counters
E-16
Description of Statistics
SRP Usage Frames Received The umber of usage frames received with good CRC, good header parity and only srpUsageFramesReceived
those that match the MAC address set for the SRP’s port. Bad CRC frames,
frames with header errors or those with other MAC addresses are received but not
counted.
SRP Usage Frames Sent The number of usage frames sent.These are sent periodically to keep the link srpUsageFramesSent
alive.
SRP Usage Status If the number of consecutive timeouts exceeds the Keep Alive threshold, this srpUsageStatus
status changes to FAIL. Otherwise shows OK.
SRP Usage Timeouts The number of times a usage frame was not received within the time period. srpUsageTimeouts
BERT
Status For BERT - The status of the connection. “Locked” when the receiving interface bertStatus
locks onto the data pattern. (See note 1 in Notes)
Bits Sent For BERT - the total number of bits sent. bertBitsSent
Bits Received For BERT - the total number of bits received. bertBitsReceived
Bit Errors Sent For BERT - the total number of bit errors sent. bertBitErrorsSent
Bit Errors Received For BERT - the total number of bit errors received. bertBitErrorsReceived
Bit Error Ratio For BERT - (BER) the ratio of the number of errored bits compared to the total bertBitErrorRatio
number of bits transmitted.
Errored Blocks For BERT- (EB) Number of blocks containing at least one errored second. bertErroredBlocks
Errored Seconds For BERT - (ES) Number of seconds containing at least one errored block or a bertErroredSeconds
defect.
Ixia Hardware Guide
Errored Second Ratio For BERT - (ESR) the ratio of Errored Seconds (ES) to the total seconds. bertErroredSecondRatio
Severely Errored Seconds For BERT - (SES) Number of seconds with 30% or more of the errored blocks or a bertSeverelyErroredSeconds
defect.
Severely Errored Second Ratio For BERT - (SESR) the ratio of Severely Errored Seconds (SESs) to the total bertSeverelyErroredSeconds
seconds in available time. Ratio
Ixia Hardware Guide
Error Free Seconds For BERT - (EFS) Number of seconds with no errored blocks or defects. bertErrorFreeSeconds
Available Seconds For BERT - (AS) Number of seconds which have occurred during Available bertAvailableSeconds
Periods.
Unavailable Seconds For BERT - (UAS) Number of seconds which have occurred during Unavailable bertUnavailableSeconds
Periods.
Block Error State For BERT - Available Period or Unavailable Period, determined according to the bertBlockErrorState
running count and calculation of seconds in various error conditions. A min. of 10
non-SESs must pass for the state to change from Unavailable to Available. A min.
of 10 SESs must pass for the state to change from Available to Unavailable. (See
note 4 in Notes)
Background Block Errors For BERT - (BBE) The number of errored blocks not occurring as part of a bertBackgroundBlockErrors
Severely Errored Second.
Background Block Error Ratio For BERT - (BBER) the ratio of Background Block Errors (BBEs) to the total bertBackgroundBlockError
number of blocks in available time. Ratio
Elapsed Test Time For BERT - the elapsed test time, expressed in seconds. bertElapsedTestTime
Number Mismatched Zeros The number of expected zeroes received as ones. bertNumberMismatchedZeros
Mismatched Zeros Ratio The ratio of the number of expected zeroes received as ones to all bits. bertismatchedZerosRatio
Number Mismatched Ones The number of expected ones received as zeroes. bertNumberMismatchedOnes
Mismatched Ones Ratio The ratio of the number of expected ones received as zeroes to all bits. bertMismatchedOnesRatio
Description of Statistics
Unframed Bert Detected Line Rate. For unframed BERT - the detected line rate, in bps. bertUnframedDetectedLine
Rate
Unframed Bert Output Signal Strength For unframed BERT - the output signal strength, in db.
Service Disruption A service disruption is the period of time during which the service is unavailable
while switching rings. The SONET spec calls for this to be less than 50 ms.
Last Service Disruption Time (ms) The length of the last service disruption that occurred, expressed in milliseconds. bertLastServiceDisruption
E-17
Time
E
Table E-6.Statistics Counters
E-18
Description of Statistics
Min Service Disruption Time (ms) The shortest service disruption that occurred, expressed in milliseconds. bertMinServiceDisruption
Time
Max Service Disruption Time (ms) The longest service disruption that occurred, expressed in milliseconds. bertMaxServiceDisruption
Time
Cumulative Service Disruption Time The total service disruption time encountered, expressed in milliseconds. bertServiceDisruption
(ms) Cumulative
DCC
DCC CRC Receive Errors The number of DCC CRC errors received. dccCrcErrorsReceived
DCC Framing Errors Received The number of DCC framing errors received. dccFramingErrorsReceived
OC192
Temperature
DMA Chip Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature of the DMA chip. dMATemperature
Capture Chip Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature of the Capture chip. captureTemperature
Latency Chip Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature of the Latency chip. latencyTemperature
Background Chip Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature of the Background chip. backgroundTemperature
Ixia Hardware Guide
Overlay Chip Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature of the Overlay chip. overlayTemperature
Front End Chip Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature of the Front End Chip. frontEndTemperature
Scheduler Chip Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature of the Scheduler Chip. scheduleTemperature
Ixia Hardware Guide
Plm Internal Chip Temperature 1 (C) (OC-192 - Temperature Sensors Stats) Internal temperature of temperature plmDevice1Internal
measuring device #1. Temperature
Plm Internal Chip Temperature 2 (C) (OC-192 - Temperature Sensors Stats) Internal temperature of temperature plmDevice2Internal
measuring device #2. Temperature
Plm Internal Chip Temperature 3(C) (OC-192 - Temperature Sensors Stats) Internal temperature of temperature plmDevice3Internal
measuring device #3. Temperature
Fom Port Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature for one of the sensors on the fobPort1FpgaTemperature
Fiber optic module (Fom). fobPort2FpgaTemperature
Fom Board Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature for one of the sensors on the fobBoardTemperature
Fiber optic module (Fom).
Fom Internal Temperature (C) (OC-192 - Temperature Sensors Stats) Temperature for one of the sensors on the fobDevice1Internal
Fiber optic module (Fom). Temperature
VSR The statistics in this sub-section relate to all VSR channels. See VSR per Channel
statistics below for further per-channel statistics.
Rx Channel Protection Disabled The status of the channel protection on the receiving interface. rxChannelProtection
Disabled8
Rx Channel Skew Error The status of the channel skew error detection on the receiving interface. rxChannelSkewError8
RX Channel Skew First The channel number of the earliest channel to arrive on the receiving interface. If rxChannelSkewFirst8
more than one channel arrives at the same time, Channel #1 has the highest
priority and so on.
Description of Statistics
Rx Channel Skew Last The channel number of the latest channel to arrive on the receiving interface. If rxChannelSkewLast8
more than one channel arrives at the same time, Channel #1 has the highest
priority, and so on.
Rx Channel Skew Max This counter increments every time the channel skew is equal to or greater than rxChannelSkewMax8
the maximum channel skew.
Description of Statistics
Rx Code Word Violation Error Indicates one or more 8b/10b code word violation errors. rxCodeWordViolationError8
Rx CRC Corrected Errors The number of corrected CRC block errors accumulated on the receiving interface. rxCrcCorrectedErrorCounter8
Rx CRC Correction Disabled Indicates the status of the CRC correction on the receiving interface. rxCrcCorrectionDisabled8
Rx CRC Uncorrected Errors The number of uncorrected CRC block errors accumulated on the receiving rxCrcUnCorrectedError
interface. Counter8
Rx Hardware Error The number of hardware errors detected on the receive side. rxHardwareError8
Rx Loss Of Synchronization Counter Indicates the number of times that a protection channels was in the loss of rxLossOfSynchronization
synchronization state. Counter8
Rx Multi-loss Of Synchronization Indicates the number of times that two or more data or protection channels were in rxMultiLossOfSynchronization
Counter the Loss of Synchronization state. Counter8
Rx Multi-loss Of Synchronization Status Indicates that two or more data or protection channels are in the Loss of rxMultiLossOfSynchronization
Synchronization state. Status8
Rx Out of Frame Counter Indicates the number of frame errors for the receiving interface. rxOutOfFrameCounter8
Rx Out of Frame Status Indicates one or more out of frame errors for the receiving interface. rxOutOfFrameStatus8
Rx Section BIP Error Counter The number of Section BIP errors detected on the receiving interface. rxSectionBipErrorCounter8
Tx Hardware Error Counter The number of hardware errors detected on the transmit side. txHardwareError8
Ixia Hardware Guide
Tx Out Of Frame Counter The number of out of frame errors detected on the transmit side. txOutOfFrameCounter8
Tx Out of Frame Status Indicates one or more out of frame errors for the transmit interface txOutOfFrameStatus8
Tx Section BIP Error Counter The number of Section Bit Interleaved Parity (BIP) errors which have been txSectionBipErrorCounter8
detected on the transmit interface.
VSR per Channel The statistics in this sub-section relate to a specific VSR channel.
Ixia Hardware Guide
Rx Code Word Violation Counter This per-channel statistic indicates the number of codeword violations detected on rxCodeWordViolation
the receiving channel interface. Codeword violations include running disparity Counter9
errors, undefined codewords, and any control characters besides K28.5.
Rx CRC Error Counter This per-channel statistic indicates the number of corrected and uncorrected errors rxCrcErrorCounter9
on the receive interface.
Rx Loss Of Synchronization Status This per-channel statistic indicates the loss of synchronization status of the rxLossOfSynchronization9
receiving interface.
Rx OUt of Frame Status This per-channel statistic indicates the out of frame status of the receiving interface rxOutOfFrame9
for a particular channel.
USB
Transmit NO Error (For USB Extended Stats) Data packets sent with no errors. usbTxNoError
Receive NO Error (For USB Extended Stats) Data packets received with no errors. usbRxNoError
Receive CRC Error (For USB Extended Stats) The last data packet received contained a CRC error. usbRxCRCError
Receive Bit Stuffing (For USB Extended Stats) The last data packet received contained a bit stuffing usbRxBitStuffing
violation.
Receive Data Toggle Mismatch (For USB Extended Stats) The data toggle PID for the last data packet received did usbRxToggleMismatch
not match the expected value.
Transmit Stall (For USB Extended Stats) Transmitted a Stall PID. usbTxStall
Receive Stall (For USB Extended Stats) Received a Stall PID. usbRxStall
Description of Statistics
Transmit Device Not Responding (For USB Extended Stats) The transmit device did not provide a handshake to the usbTxDeviceNotResponding
receive device.
Receive Device Not Responding (For USB Extended Stats) The receive device did not respond to a token sent by usbRxDeviceNotResponding
the transmit device.
Transmit PID Check Failure (For USB Extended Stats) Check bits in the PID from the endpoint failed on usbTxPIDCheckFail
handshake.
E-21
E
Table E-6.Statistics Counters
E-22
Description of Statistics
Receive PID Check Failure (For USB Extended Stats) Check bits in the PID from the endpoint failed on data usbRxPIDCheckFail
PID.
Transmit Unexpected PID (For USB Extended Stats) Transmitted an invalid PID or undefined PID value. usbTxUnexpectedPID
Receive Unexpected PID (For USB Extended Stats) Received an invalid PID or undefined PID value. usbRxUnexpectedPID
Receive Data Overrun (For USB Extended Stats) The amount of data returned exceeded the size of: usbRxDataOverrun
• maximum data packet allowed, or
• remaining amount of memory in the buffer
Receive Data Underrun (For USB Extended Stats) The endpoint sent less than maximum packet size, so usbRxdataUnderrun
the specified buffer is not filled.
Receive Buffer Overrun (For USB Extended Stats) Receiving port receives data faster than it can be written usbRxbufferOverrun
to system memory.
Transmit Buffer Underrun (For USB Extended Stats) During transmission, cannot retrieve data from system usbTxBufferUnderrun
memory and send out fast enough to keep up with the USB data rate.
Transmit Not Accessed (For USB Extended Stats) This code is set by software before the RUT is placed in usbTxNotAccessed
a queue for processing.
Receive Not Accessed (For USB Extended Stats) This code is set by software before the RUT is placed in usbRxNotAccessed
a queue for processing.
10 Gig
Pause Frame
Pause Acknowledge The number of clocks for which transmit has been paused. pauseAcknowledge
Pause End Frames The number of pause frames received with a quanta of 0. pauseEndFrames
Ixia Hardware Guide
Pause Overwrite The number of pause frames received while transmit was paused with a quanta not pauseOverwrite
equal to 0
Temperature
Ixia Hardware Guide
Lan Transmit FPGA Temperature For the 10Gig LAN board, the temperature at the transmit FPGA. 10GigLanTxFpga
Temperature
Lan Receive FPGA Temperature For the 10Gig LAN board, the temperature at the receive FPGA. 10GigLanRxFpga
Temperature
Description of Statistics
E-23
E
Notes
E-24
Description of Statistics
Note Choices displayed for Statistic
Not Locked
2 Demo Mode
Ixia Hardware Guide
Link Up
Link Down
Loopback
WriteMii
Ixia Hardware Guide
Restart AutoNegotiate
End RestartAutoNegotiate
AutoNegotiate
WriteMii Failed
No Transceiver
Read LinkPartner
No LinkPartner
No GBIC Module
Fifo Reset
PPP Off
PPP Up
PPP Down
PPP Init
Description of Statistics
PPP WaitForOpen
PPP AutoNegotiate
PPP Close
PPP Connect
Loss of Frame
E-25
E
Table E-7.Notes for Statistics Counters
E-26
Description of Statistics
Loss of Signal
StateMachine Failure
PPP RestartNegotiation
LP Boot Failed
Ignore Link
Temperature Alarm
PPP Closing
PPP Authenticate
3 OK
Alarm
Ixia Hardware Guide
“-”
Defect
4 Unavailable Period
Available Period
Ixia Hardware Guide
5 OK
OK (%)
Alarm (%)
“-”
6 OC-3c
OC-12c
OC-48c
OC-192c
10GE WAN
10 Mbps
100 Mbps
1000 Mbps
7 Full
Half
8 Loss of Signal
[-] %d.%d
Description of Statistics
8 The statistics in this section must be accessed using the vsrStat
command in TCL and the TCLvsrStat class in C++.
Table E-8.Statistics for 10/100 Cards and Ethernet/USB Cards in Ethernet Mode
Description of Statistics
Normal Qos Stream Trigger
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
PacketGroup
PacketGroup
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X
UserDefinedStat2 X X X X X X X X
CaptureTrigger X X X X
CaptureFilter X X X X
StreamTrigger1 X
StreamTrigger2 X
Type: States
Link X X X X X X X X X
LineSpeed X X X X X X X X X
DuplexMode X X X X X X X X X
TransmitState X X X X X X X X X
CaptureState X X X X X X X X X
PauseState X X X X X X X X X
Type: Common
FramesSent X X X X X X X X X
FramesReceived X X X X X X X X X
Ixia Hardware Guide
BytesSent X X X X X X X X X
BytesReceived X X X X X X X X
FcsErrors X X X X X X X X X
Type: Transmit Duration
TransmitDuration X X X X X X X
Ixia Hardware Guide
Table E-8.Statistics for 10/100 Cards and Ethernet/USB Cards in Ethernet Mode
Normal Qos Stream Trigger
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
PacketGroup
PacketGroup
Capture
Capture
Capture
Type: Quality of Service
QualityOfService0 X
Type: Ethernet
Fragments X X X X X X X X X
Undersize X X X X X X X X X
Oversize X X X X X X X X X
VlanTaggedFramesRx X X X
FlowControlFrames X X X X X X X X X
Type: 10/100
AlignmentErrors X X X X X X X X X
DribbleErrors X X X X X X X X
Collisions X X X X X X X X X
LateCollisions X X X X X X X X X
CollisionFrames X X X X X X X X X
ExcessiveCollisionFrames X X X X X X X X X
Type: 10/100 + Gigabit
Description of Statistics
SymbolErrors X
OversizeAndCrcErrors
E-29
E
E-30
Description of Statistics
Normal Qos Stream Trigger Mode
DataIntegrity
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X X
CaptureTrigger X X X X X X X X
CaptureFilter X X X X X X X X
StreamTrigger1 X X
StreamTrigger2 X X
Type: States
Link X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X
CaptureState X X X X X X X X X X X X X X X X X X
PauseState X X X X X X X X X X X X X X X X X X
Type: Common
Ixia Hardware Guide
FramesSent X X X X X X X X X X X X X X X X X X
FramesReceived X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X
BytesReceived X X X X X X X X X X X X X X X X
FcsErrors X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Type: Transmit Duration
TransmitDuration X X
Type: Quality of Service
QualityOfService0 X X
Type: Data Integrity
DataIntegrityFrames X X X
DataIntegrityErrors X X X
Type: Sequence
Checking
SequenceFrames X
SequenceErrors X
Type: Ethernet
Fragments X X X X X X X X X X X X X X X X X X
Undersize X X X X X X X X X X X X X X X X X X
Description of Statistics
Oversize X X X X X X X X X X X X X X X X X X
VlanTaggedFramesRx X X X X X X X X
FlowControlFrames X X X X X X X X X X X X X X
Type: 10/100
AlignmentErrors X X X X
DribbleErrors X X X X X X X X X X X X X X X X X X
Collisions X X X X X X X X X X X X X X X X X X
E-31
LateCollisions X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide E-32
SymbolErrors
CollisionFrames
OversizeAndCrcErrors
Type: 10/100 + Gigabit
ExcessiveCollisionFrames
X
X
X
Capture
X
X
X
PacketGroup
X
X
RxTcpRoundTrip
X
X
X
RxDataIntegrity
Normal
Table E-9.Statistics for 10/100 TXS Modules
X
X
RxFirstTimeStamp
X
X
X
RxSequenceChecking
X
X
X
Capture
Qos
X
X
X
PacketGroup
X
X
X
Capture
X
X
X
PacketGroup
X
X
RxTcpRoundTrip
X
X
X
RxDataIntegrity
X
Stream Trigger
RxFirstTimeStamp
X
X
X
RxSequenceChecking
X
X
X
Capture
X
X
X
PacketGroup
X
X
X
RxDataIntegrity
Mode
DataIntegrity
X
X
X
RxSequenceChecking
Description of Statistics E
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X X
CaptureTrigger X X X X X X X X
CaptureFilter X X X X X X X X
StreamTrigger1 X X X X
StreamTrigger2 X X X X
Type: States
Link X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X
CaptureState X X X X X X X X X X X X X X X X X X
Description of Statistics
PauseState X X X X X X X X X X X X X X X X X X
Type: Common
FramesSent X X X X X X X X X X X X X X X X X X
FramesReceived X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X
BytesReceived X X X X X X X X X X X X X X X X
E-33
FcsErrors X X X X X X X X X X X X X X X X X X
E
Table E-10.Statistics for 10/100/1000 TXS and 1000 SFPS4 Cards
E-34
Description of Statistics
Integrity
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Type: Transmit Duration
TransmitDuration X X X X X X X X X X X X X X X X
Type: Quality of Service
QualityOfService0 X X
Type: Data Integrity
DataIntegrityFrames X
DataIntegrityErrors X
Type: Sequence
Checking
SequenceFrames X
SequenceErrors X
Type: Ethernet
Fragments X X X X X X X X X X X X X X X X X X
Undersize X X X X X X X X X X X X X X X X X X
Oversize X X X X X X X X X X X X X X X X X X
VlanTaggedFramesRx X X X X X X
Ixia Hardware Guide
FlowControlFrames X X X X X X X X X X X X X X
Type: 10/100
AlignmentErrors X X X X
DribbleErrors X X X X X X X X X X X X X X X X X X
Collisions X X X X X X X X X X X X X X X X X X
LateCollisions X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
CollisionFrames X X X X X X X X X X X X X X X X X X
ExcessiveCollisionFrames X X X X X X X X X X X X X X X X X X
Type: 10/100 + Gigabit
SymbolErrors
OversizeAndCrcErrors X X X X X X X X X X X X X X
Description of Statistics
E-35
E
E-36
Description of Statistics
Normal Qos Stream Trigger Mode Checksum Mode Data Integrity Additional
Errors Modes
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
UsbExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X X X X X X X
CaptureTrigger X X X X X X X X X X X X
CaptureFilter X X X X X X X X X X X X
StreamTrigger1 X
StreamTrigger2 X
Type: States
Link X X X X X X X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X X X X X X X
CaptureState X X X X X X X X X X X X X X X X X X X X X X X X
PauseState X X X X X X X X X X X X X X X X X X X X X X X X
Type: Common
Ixia Hardware Guide
FramesSent X X X X X X X X X X X X X X X X X X X X X X X X
FramesReceived X X X X X X X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X X X X X X X
BytesReceived X X X X X X X X X X X X X X X X X X X X X X
FcsErrors X X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
UsbExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
Type: Transmit Duration
TransmitDuration X X X X X X X X X X X X X X X X X X X X X X
Type: Quality of Service
QualityOfService0 X X
Type: Checksum Stats
IpPackets X
UdpPackets X
TcpPackets X
IpChecksumErrors X
UdpChecksumErrors X
TcpChecksumErrors X
Type: Data Integrity
DataIntegrityFrames X X X X
DataIntegrityErrors X X X X
Description of Statistics
Type: Sequence Checking
SequenceFrames X X X X
SequenceErrors X X X X
Type: Ethernet
Fragments X X X X X X X X X X X X X X X X X X X
Undersize X X X X X X X X X X X X X X X X X X X
Oversize X X X X X X X X X X X X X X X X X X X
E-37
E
Table E-11.Statistics for Ethernet/USB cards in USB Mode
E-38
Normal Qos Stream Trigger Mode Checksum Mode Data Integrity Additional
Description of Statistics
Errors Modes
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
UsbExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
VlanTaggedFramesRx X X X X X X X X X
FlowControlFrames X X X X X X X X X X
Type: 10/100
AlignmentErrors X X
DribbleErrors X X X
Collisions X X X
LateCollisions X X X
CollisionFrames X X X
ExcessiveCollisionFrames X X X
Type: Gigabit
SymbolErrorFrames X X X X X X X X X X X X X X X
SynchErrorFrames X X X X X X X
Type: 10/100 + Gigabit
SymbolErrors X X X X X X X
OversizeAndCrcErrors X X X X X X X X X X X X X X X X X
Type: USB
Ixia Hardware Guide
UsbTxNoError X
UsbRxNoError X
UsbRxCRCError X
UsbRxBitStuffing X
UsbRxToggleMismatch X
UsbTxStall X
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
UsbExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
UsbRxStall X
UsbTxDeviceNotResponding X
UsbRxDeviceNotResponding X
UsbTxPIDCheckFail X
UsbRxPIDCheckFail X
UsbTxUnexpectedPID X
UsbRxUnexpectedPID X
UsbRxDataOverrun X
UsbRxdataUnderrun X
UsbRxBufferOverrun X
UsbTxBufferUnderrun X
UsbTxNotAccessed X
UsbRxNotAccessed X
Description of Statistics
E-39
E
E-40
Description of Statistics
Normal Qos Stream Trigger ModeChecksumErrors Mode Data Integrity
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X X X X X X X
CaptureTrigger X X X X X X X X X X X X
CaptureFilter X X X X X X X X X X X X
StreamTrigger1 X
StreamTrigger2 X
Type: States
Link X X X X X X X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X X X X X X X
CaptureState X X X X X X X X X X X X X X X X X X X X X X X X
PauseState X X X X X X X X X X X X X X X X X X X X X X X X
Type: Common
FramesSent X X X X X X X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
FramesReceived X X X X X X X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X X X X X X X
BytesReceived X X X X X X X X X X X X X X X X X X X X X X
FcsErrors X X X X X X X X X X X X X X X X X X X X X X X X
Type: Transmit Duration
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
TransmitDuration X X X X X X X X X X X X X X X X X X X X X X
Type: Quality of Service
QualityOfService0 X X
Type: Checksum Stats
IpPackets X
UdpPackets X
TcpPackets X
IpChecksumErrors X
UdpChecksumErrors X
TcpChecksumErrors X
Type: Data Integrity
DataIntegrityFrames X X X X
DataIntegrityErrors X X X X
Type: Sequence
Checking
Description of Statistics
SequenceFrames X X X X
SequenceErrors X X X X
Type: Ethernet
Fragments X X X X X X X X X X X X X X X X X X X X X X X X
Undersize X X X X X X X X X X X X X X X X X X X X X X X X
Oversize X X X X X X X X X X X X X X X X X X X X X X X X
VlanTaggedFramesRx X X X X X X X X X X X X
E-41
E
Table E-12.Statistics for Gigabit Modules
E-42
Description of Statistics
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
FlowControlFrames X X X X X X X X X X X X X X X
Type: 10/100
AlignmentErrors X X
DribbleErrors X X X
Collisions X X X
LateCollisions X X X
CollisionFrames X X X
ExcessiveCollisionFrames X X X
Type: Gigabit
SymbolErrorFrames X X X X X X X X X X X X X X X X X X X
SynchErrorFrames X X X X X X X X X X X X
Type: 10/100 + Gigabit
SymbolErrors X X X X X X X X X X
OversizeAndCrcErrors X X X X X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X X X X X X X
CaptureTrigger X X X X X X
CaptureFilter X X X X X X
StreamTrigger1 X X
StreamTrigger2 X X
Type: States
Link X X X X X X X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X X X X X X X
CaptureState X X X X X X X X X X X X X X X X X X X X X X X X
Description of Statistics
PauseState X X X X X X X X X X X X X X X X X X X X X X X X
Type: Common
FramesSent X X X X X X X X X X X X X X X X X X X X X X X X
FramesReceived X X X X X X X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X X X X X X X
BytesReceived X X X X X X X X X X X X X X X X X X X X X X
E-43
FcsErrors X X X X X X X X X X X X X X X X X X X X X X X X
E
Table E-13.Statistics for OC12c/OC3c Modules
E-44
Normal Qos Stream Trigger Mode Checksum Mode Data Integrity Add’l
Description of Statistics
Errors Modes
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
Type: Transmit Duration
TransmitDuration X X X X X X X X X X X X X X X X X X X X X X
Type: Quality of Service
QualityOfService0 X X
Type: Framer
FramerFCSErrors
FramerAbort X
FramerMinLength X
FramerMaxLength X
Type: Checksum Stats
IpPackets X
UdpPackets X
TcpPackets X
IpChecksumErrors X
UdpChecksumErrors X
TcpChecksumErrors X
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
Type: Ethernet
Fragments X X X X X X
Undersize X X X X X X
Oversize X X X X X X
VlanTaggedFramesRx X X X X X X
FlowControlFrames X X X X X X
Type: 10/100
AlignmentErrors X X
DribbleErrors X X
Collisions X X
LateCollisions X X
CollisionFrames X X
ExcessiveCollisionFrames X X
Type: Gigabit
Description of Statistics
SymbolErrorFrames X X X X
SynchErrorFrames X X X X
Type: 10/100 + Gigabit
SymbolErrors X X X X
OversizeAndCrcErrors X X X X
Type: POS
SectionLossOfSignal X
E-45
E
Table E-13.Statistics for OC12c/OC3c Modules
E-46
Normal Qos Stream Trigger Mode Checksum Mode Data Integrity Add’l
Description of Statistics
Errors Modes
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
Capture
Capture
Capture
Capture
Capture
SectionLossOfFrame X
SectionBip X
LineAis X
LineRdi X
LineRei X
LineBip X
PathAis X
PathRdi X
PathRei X
PathBip X
PathLossOfPointer X
PathPlm X
SectionBipErroredSecs
SectionBipSeverlyErroredSecs
SectionLossOfSignalSecs
LineBipErroredSecs
Ixia Hardware Guide
LineReiErroredSecs
LineAisAlarmSecs
LineRdiUnavailableSecs
PathBipErroredSecs
PathReiErroredSecs
PathAisAlarmSecs
E-47 Ixia Hardware Guide
PosK2Byte
PosK1Byte
InputSignalStrength
PathAisUnavailableSecs
PathRdiUnavailableSecs
Capture
PacketGroup
RxTcpRoundTrip
RxDataIntegrity
Normal
Table E-13.Statistics for OC12c/OC3c Modules
RxFirstTimeStamp
RxSequenceChecking
Capture
Qos
PacketGroup
Capture
PacketGroup
RxTcpRoundTrip
RxDataIntegrity
RxFirstTimeStamp
Stream Trigger
RxSequenceChecking
Capture
PacketGroup
Errors
RxDataIntegrity
RxFirstTimeStamp
Mode Checksum
RxSequenceChecking
Capture
PacketGroup
RxDataIntegrity
RxFirstTimeStamp
RxSequenceChecking
Mode Data Integrity
PosExtendedStats
Add’l
Modes
Description of Statistics
E
E-48
Description of Statistics
Normal Qos StreamTrigger ModeDataIntegrity Add’l
Modes
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X
CaptureTrigger X X X
CaptureFilter X X X
StreamTrigger1 X X X X
StreamTrigger2 X X X X
Type: States
Link X X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X X
CaptureState X X X X X X X X X X X X X X X X X X X
PauseState X X X X X X X X X X X X X X X X X X X
Type: Common
Ixia Hardware Guide
FramesSent X X X X X X X X X X X X X X X X X X X
FramesReceived X X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X X
BytesReceived X X X X X X X X X X X X X X X
FcsErrors X X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Type: Transmit Duration
TransmitDuration X X X X X X X X X X X X X X X X X X X
Type: Quality of Service
QualityOfService0 X X X X
Type: Data Integrity
DataIntegrityFrames X X X
DataIntegrityErrors X X X
Type:Sequence Checking
SequenceFrames X X X X
SequenceErrors X X X X
Type: POS
SectionLossOfSignal X
SectionLossOfFrame X
SectionBip X
Description of Statistics
LineAis X
LineRdi X
LineRei X
LineBip X
PathAis X
PathRdi X
PathRei X
E-49
E
Table E-14.Statistics for OC48c Modules with Bert
E-50
Description of Statistics
Modes
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
PathBip X
PathLossOfPointer X
PathPlm X
SectionBipErroredSecs X X X X X X X X X X X X X X X X X X X
SectionBipSeverlyErrored X X X X X X X X X X X X X X X X X X X
Secs
SectionLossOfSignalSecs X X X X X X X X X X X X X X X X X X X
LineBipErroredSecs X X X X X X X X X X X X X X X X X X X
LineReiErroredSecs X X X X X X X X X X X X X X X X X X X
LineAisAlarmSecs X X X X X X X X X X X X X X X X X X X
LineRdiUnavailableSecs X X X X X X X X X X X X X X X X X X X
PathBipErroredSecs X X X X X X X X X X X X X X X X X X X
PathReiErroredSecs X X X X X X X X X X X X X X X X X X X
PathAisAlarmSecs X X X X X X X X X X X X X X X X X X X
PathAisUnavailableSecs X X X X X X X X X X X X X X X X X X X
PathRdiUnavailableSecs X X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
InputSignalStrength
PosK1Byte
PosK2Byte
SrpDataFramesReceived X X X X X X X X X X X X X X X X X X X
SrpDiscoveryFrames X X X X X X X X X X X X X X X X X X X
Received
Ixia Hardware Guide
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
SrpIpsFramesReceived X X X X X X X X X X X X X X X X X X X
SrpParityErrors X X X X X X X X X X X X X X X X X X X
SrpUsageFramesReceived X X X X X X X X X X X X X X X X X X X
SrpUsageStatus X X X X X X X X X X X X X X X X X X X
SrpUsageTimeouts X X X X X X X X X X X X X X X X X X X
Description of Statistics
E-51
E
E-52
Description of Statistics
Normal Qos StreamTrigger ModeDataIntegrity Add’l
Modes
TemperatureSensorsStats
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X
CaptureTrigger X X X
CaptureFilter X X X
StreamTrigger1 X X X X
StreamTrigger2 X X X X
Type: States
Link X X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X X
CaptureState X X X X X X X X X X X X X X X X X X X
PauseState X X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
Type: Common
FramesSent X X X X X X X X X X X X X X X X X X X
FramesReceived X X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X X
BytesReceived X X X X X X X X X X X X X X X
Ixia Hardware Guide
TemperatureSensorsStats
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
FcsErrors X X X X X X X X X X X X X X X X X X X
Type: Transmit Duration
TransmitDuration X X X X X X X X X X X X X X X X X X X
Type: Quality of Service
QualityOfService0 X X X X
Type: Data Integrity
DataIntegrityFrames X X X
DataIntegrityErrors X X X
Type:Sequence Checking
SequenceFrames X X X X
SequenceErrors X X X X
Type: Ethernet
Fragments X X X X X X X X X X X X X X X X X X X
Description of Statistics
Undersize X X X X X X X X X X X X X X X X X X X
Oversize X X X X X X X X X X X X X X X X X X X
VlanTaggedFramesRx X X X X X X X X X X X X X X X X X X X
FlowControlFrames X X X X X X X X X X X X X X X X X X X
Type: 10/100 + Gigabit
SymbolErrors
E-53
OversizeAndCrcErrors X X X X X X X X X X X X X X X X X X X
E
Table E-15.Statistics for OC192c Modules with Bert
E-54
Description of Statistics
Modes
TemperatureSensorsStats
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Type: POS
SectionLossOfSignal X
SectionLossOfFrame X
SectionBip X
LineAis X
LineRdi X
LineRei X
LineBip X
PathAis X
PathRdi X
PathRei X
PathBip X
PathLossOfPointer X
PathPlm X
SectionBipErroredSecs
Ixia Hardware Guide
SectionBipSeverlyErrored
Secs
SectionLossOfSignalSecs
LineBipErroredSecs
LineReiErroredSecs
LineAisAlarmSecs
Ixia Hardware Guide
TemperatureSensorsStats
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
LineRdiUnavailableSecs
PathBipErroredSecs
PathReiErroredSecs
PathAisAlarmSecs
PathAisUnavailableSecs
PathRdiUnavailableSecs
InputSignalStrength X X X X X X X X X X X X X X X X X X X
PosK1Byte
PosK2Byte
SrpDataFramesReceived X X X X X X X X X X X X X X X X X X X
SrpDiscoveryFrames X X X X X X X X X X X X X X X X X X X
Received
SrpIpsFramesReceived X X X X X X X X X X X X X X X X X X X
Description of Statistics
SrpParityErrors X X X X X X X X X X X X X X X X X X X
SrpUsageFramesReceived X X X X X X X X X X X X X X X X X X X
SrpUsageStatus X X X X X X X X X X X X X X X X X X X
SrpUsageTimeouts X X X X X X X X X X X X X X X X X X X
Type: OC192 -
Temperature
DMATemperature X
E-55
CaptureTemperature X
E
Table E-15.Statistics for OC192c Modules with Bert
E-56
Description of Statistics
Modes
TemperatureSensorsStats
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
PosExtendedStats
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
LatencyTemperature X
BackgroundTemperature X
OverlayTemperature X
FrontEndTemperature X
SchedulerTemperature X
PlmDevice1Internal X
Temperature
PlmDevice2Internal X
Temperature
PlmDevice3Internal X
Temperature
FobPort1FpgaTemperature X
FobPort2FpgaTemperature
FobBoardTemperature X
FobDevice1InternalTemper X
ature
Ixia Hardware Guide
TemperatureSensorsStats
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Capture
Type: User Configurable
UserDefinedStat1 X X X X X X X X X X X X X X X X X X X X X X X X X X X X
UserDefinedStat2 X X X X X X X X X X X X X X X X X X X X X X X X X X X
CaptureTrigger X X X X X X
CaptureFilter X X X X X X
StreamTrigger1 X X X X X
StreamTrigger2 X X X X X
Type: States
Link X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
LineSpeed X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
DuplexMode X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
TransmitState X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Description of Statistics
CaptureState X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
PauseState X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Type: Common
FramesSent X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
FramesReceived X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
BytesSent X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
E-57
BytesReceived X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Ixia Hardware Guide
TemperatureSensorsStats
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Capture
FcsErrors X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Type: Transmit Duration
TransmitDuration X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Type: Quality of Service
QualityOfService0 X X X X X
Type: Checksum Stats
IpPackets X
UdpPackets X
TcpPackets X
IpChecksumErrors X
UdpChecksumErrors X
TcpChecksumErrors X
Type: Data Integrity
Description of Statistics
DataIntegrityFrames X X X X
DataIntegrityErrors X X X X
Type: Sequence Checking
SequenceFrames X X X X X
SequenceErrors X X X X X
Type: Ethernet
E-58
Fragments X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
E
Table E-16.Statistics for 10GE Modules with BERT
E-59
Description of Statistics
umErrors Modes
TemperatureSensorsStats
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Capture
Undersize X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Oversize X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
VlanTaggedFramesRx X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
FlowControlFrames X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Type: 10/100
AlignmentErrors X X
DribbleErrors X X
Collisions X X
LateCollisions X X
CollisionFrames X X
ExcessiveCollisionFrames X X
Type: Gigabit
SymbolErrorFrames X X X X
SynchErrorFrames X X X X
Type: 10/100 + Gigabit
Ixia Hardware Guide
SymbolErrors X X X X
OversizeAndCrcErrors X X X X X X X X X X X X X X X X X X X X X X X X X X X
Type: POS
SectionLossOfSignal X
SectionLossOfFrame X
E-60 Ixia Hardware Guide
LineAis
LineBip
LineRei
LineRdi
PathAis
PathBip
PathRei
PathRdi
PathPlm
SectionBip
LineAisAlarmSecs
PathLossOfPointer
LineBipErroredSecs
LineReiErroredSecs
PathBipErroredSecs
PathReiErroredSecs
SectionBipErroredSecs
LineRdiUnavailableSecs
SectionLossOfSignalSecs
SectionBipSeverlyErroredSecs
Capture
PacketGroup
RxTcpRoundTrip
RxDataIntegrity
RxFirstTimeStamp
Normal
RxSequenceChecking
Table E-16.Statistics for 10GE Modules with BERT
RxModeBert
RxModeBertChannelized
Capture
PacketGroup
RxSequenceChecking
Qos
RxModeBert
RxModeBertChannelized
Capture
PacketGroup
RxTcpRoundTrip
RxDataIntegrity
RxFirstTimeStamp
RxSequenceChecking
StreamTrigger
RxModeBert
RxModeBertChannelized
Capture
PacketGroup
RxDataIntegrity
RxFirstTimeStamp
umErrors
ModeChecks
RxSequenceChecking
Capture
PacketGroup
RxDataIntegrity
RxFirstTimeStamp
RxSequenceChecking
RxModeBert
ModeDataIntegrity
RxModeBertChannelized
X
X
X
X
X
X
X
X
X
X
X
PosExtendedStats
TemperatureSensorsStats
Add’l
Modes
Description of Statistics
Ixia Hardware Guide
TemperatureSensorsStats
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxModeBertChannelized
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxSequenceChecking
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
RxFirstTimeStamp
PosExtendedStats
RxTcpRoundTrip
RxTcpRoundTrip
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
RxDataIntegrity
PacketGroup
PacketGroup
PacketGroup
PacketGroup
PacketGroup
RxModeBert
RxModeBert
RxModeBert
RxModeBert
Capture
Capture
Capture
Capture
Capture
PathAisAlarmSecs
PathAisUnavailableSecs
PathRdiUnavailableSecs
InputSignalStrength X X X X X X X X X X X X X X X X X X X X X X X
PosK1Byte
PosK2Byte
Type: OC192 - Temperature
DMATemperature X
CaptureTemperature X
LatencyTemperature X
BackgroundTemperature X
OverlayTemperature X
FrontEndTemperature X
Description of Statistics
SchedulerTemperature X
PlmDevice1InternalTemperature X
PlmDevice2InternalTemperature X
PlmDevice3InternalTemperature X
FobPort1FpgaTemperature X
FobPort2FpgaTemperature
E-61
FobBoardTemperature X
Ixia Hardware Guide E-62
PauseOverwrite
PauseEndFrames
PauseAcknowledge
Type: 10 Gig - Pause Frame
FobDevice1InternalTemperature Capture
X X
X X
X X
PacketGroup
RxTcpRoundTrip
X
X
X
RxDataIntegrity
RxFirstTimeStamp
Normal
RxSequenceChecking
Table E-16.Statistics for 10GE Modules with BERT
RxModeBert
RxModeBertChannelized
Capture
PacketGroup
RxSequenceChecking
Qos
RxModeBert
RxModeBertChannelized
Capture
X X X X X X X X X X
X X X X X X X X X X
X X X X X X X X X X
PacketGroup
RxTcpRoundTrip
X
X
X
RxDataIntegrity
RxFirstTimeStamp
RxSequenceChecking
StreamTrigger
RxModeBert
X X X
X X X
X X X
RxModeBertChannelized
Capture
PacketGroup
RxDataIntegrity
RxFirstTimeStamp
umErrors
ModeChecks
RxSequenceChecking
Capture
PacketGroup
X X X
X X X
X X X
RxDataIntegrity
RxFirstTimeStamp
RxSequenceChecking
RxModeBert
ModeDataIntegrity
X X X
X X X
X X X
RxModeBertChannelized
PosExtendedStats
X
TemperatureSensorsStats
Add’l
Modes
Description of Statistics E
Ixia Hardware Guide
ProtocolServerStats
PosExtendedStats
RsvpStats
IcmpStats
OspfStats
BgpStats
LdpStats
ArpStats
IsisStats
Type: Protocol Server - General
ProtocolServerTx X
ProtocolServerRx X
TxArpReply X
TxArpRequest X
TxPingReply X
TxPingRequest X
RxArpReply X
RxArpRequest X
RxPingReply X
RxPingRequest X
ProtocolServerVlanDroppedFrames X
ScheduledFramesSent
AsynchronousFramesSent
PortCPUFramesSent
Description of Statistics
Type: Protocol Server - BGP
BGPTotalSessions X
BGPTotalSessionsEstablished X
Type: Protocol Server - ISIS
ISISSessionsConfiguredL1 X
ISISSessionsUpL1 X
ISISSessionsConfiguredL2 X
E-63
ISISSessionsUpL2 X
E
Table E-17.Statistics for Protocol Server
E-64
ProtocolServerStats
Description of Statistics
PosExtendedStats
RsvpStats
IcmpStats
OspfStats
BgpStats
LdpStats
ArpStats
IsisStats
Type: Protocol Server - OSPF
OspfTotalSessions X
OSPFFullNeighbors X
Type: Protocol Server - RSVP
RSVPIngressLSPsConfigured X
RSVPIngressLSPsUp X
RSVPEgressLSPsUp X
Type: Protocol Server - LDP
LdpSessionsConfigured X
LdpSessionsUp X
LdpBasicSessionsUp X
Ixia Hardware Guide
Description of Statistics
Ixia Hardware Guide E-65
E Description of Statistics
E-66 Ixia Hardware Guide
Index
Numerics Chassis Chaining 2-21
10GE BERT 18-1 Sync-in 2-21
Sync-out 2-21
10GE LAN 18-1
Cumulative Service Disruption Time E-18
10GE Load Modules 18-1
10GE WAN 18-1 D
10Gigabit 18-1 Data Integrity Errors E-10
Data Integrity Frames E-10
A
DCC Bytes Received E-18
Antenna A-2, A-3
DCC Bytes Sent E-18
Asynchronous Frames Sent E-11
DCC CRC Receive Errors E-18
Available Seconds E-17
DCC Frames Received E-18
B DCC Frames Sent E-18
Background Block Error Ratio E-17 DCC Framing Errors Received E-18
Background Block Errors E-17 DMA Chip Temperature E-18
Background Chip Temperature E-18
E
BGP Sessions Configured E-11
Elapsed Test Time E-17
BGP Sessions Established E-11
Error Free Seconds E-17
Bit Error Ratio E-16
Errored Blocks E-16
Bit Errors Received E-16
Errored Second Ratio E-16
Bit Errors Sent E-16
Errored Seconds E-16
Bits Received E-16
Bits Sent E-16 F
Block Error State E-17 File-Sharing 2-7
Bytes Received Rate E-9 Fom Board Temperature E-19
Bytes Sent Rate E-9 Fom Internal Temperature E-19
Fom Port Temperature E-19
C
Framer Abort E-9
Capture Chip Temperature E-18
Framer CRC Errors E-9
Capture State E-8
Framer Frames Received E-9
Chassis A-2, A-3
Framer Frames Sent E-9
Framer Max Length & Rate E-9 Number Mismatched Zeros E-17
Framer Min Length & Rate E-9
O
Frames Sent Rate E-8
Optional Down Converter A-2
Front End Chip Temperature E-18
OSPF Neighbors in Full State E-12
G OSPF Total Sessions E-12
Global Positioning System A-1 Overlay Chip Temperature E-18
GPS 8-4, A-1 Oversize E-12
H P
Humidity A-3 Path AIS E-14
Path AIS Alarmed Seconds E-15
I
Path AIS Unavailable Seconds E-15
Initial Configuration 2-2
Path BIP Errored Seconds E-15
Input Signal Strength E-15
Path BIP(B3) E-14
Introduction 1-1
Path LOP E-14
IP Checksum Errors E-10
Path PLM(C2) E-14
IP Packets Received E-9 Path RDI E-14
ISIS L1 Sessions Configured E-11
Path RDI Unavailable Seconds E-15
ISIS L1 Sessions Up E-11
Path REI E-14
ISIS L2 Sessions Configured E-11 Path REI Errored Seconds E-15
ISIS L2 Sessions Up E-11
Pause Acknowledge E-22
L Pause End Frames E-22
Last Service Disruption Time E-17 Pause Overwrite E-22
Latency Chip Temperature E-18 Pause State E-8
LDP Basic Sessions Up E-12 Plm Internal Chip Temperature E-19
LDP Sessions Configured E-12 Plm Internal Chip Temperature 1 E-19
LDP Sessions Up E-12 Plm Internal Chip Temperature 2 E-19
Line AIS E-14 Port CPU Frames Sent E-11
Line AIS Alarmed Seconds E-15 POS K1 Byte E-15
Line BIP Errored Seconds E-14 POS K2 Byte E-15
Line BIP(B2) E-14 Powering Up 2-21
Line RDI E-14 Protocol Server Receive E-10
Line RDI Unavailable Seconds E-15 Protocol Server Transmit E-10
Line REI Errored Seconds E-15 Q
Line REI(FEBE) E-14 Quality of Service E-9
M R
Master Chassis Chain 2-21 Receive Arp Reply E-11
Max Service Disruption Time E-18
Receive Arp Request E-11
Min Service Disruption Time E-18
Receive Bit Stuffing E-21
Mismatched Ones Ratio E-17 Receive Buffer Overrun E-22
Mismatched Zeros Ratio E-17 Receive CRC Error E-21
N Receive Data Overrun E-22
Number Mismatched Ones E-17 Receive Data Toggle Mismatch E-21
T
TCP Checksum Errors E-10
TCP Packets Received E-10
TCXO A-1
Temperature A-3
Temperature Compensated Crystal Oscillator A-1
Time and Frequency Module A-1, B-1, C-1, D-1
Transmit Arp Reply E-10
Transmit Arp Request E-11
Transmit Buffer Underrun E-22
Transmit Device Not Responding E-21
Transmit Duration E-9