7090-01 CE Ethernet SFP NID User Manual 76.01FP33/2-A

7090-01 CE Ethernet SFP NID User Manual
76.01FP33/2-A
Revision A, 5/17
Copyright © 2017 Coriant Operations, Inc. All rights reserved.
Federal Communications Commission (FCC) Rules require that you be notified of the
following:
This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference
in which case the user will be required to correct the interference at his own expense.
Changes or modifications not expressly approved by Coriant Operations, Inc., in
writing can void the user’s authority to operate the equipment.
Industry Canada interference-causing equipment regulations require that you be

notified of the following:
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Voluntary Control
Council for Interference
(VCCI)
Corporate References Tellabs and Coriant are joining forces. You may see references to Coriant or Tellabs
when doing business with us. Contact information is available at
http://www.coriant.com.
Copyright Statement This manual is protected by U.S. and international copyright laws, conventions, and
treaties. Your right to use this manual is subject to limitations and restrictions imposed
by applicable licenses and copyright laws. Unauthorized reproduction, modification,
distribution, display or other use of this manual may result in criminal and civil
penalties.
Trademark Notice The following trademarks and service marks are owned by Coriant Operations, Inc.,
or its affiliates in the United States and/or other countries: BROADLEAF®, CABLESPAN®,
CORIANT™, CORIANT DYNAMIC OPTICAL CLOUD™, CORIANT TRANSCEND™, DXX®,
®
, DYNAMIC SIGNAL TRANSFER™, FOCUS™, MARTIS®, ®
,
MARTISDXX , ® ®
, METROCARE , METROWATCH , MTERA™, Nano™,
SM ®
Pico™, SILVX®, SILVX INSIGHT®, SILVXMANAGER®, SILVXOSS®, SILVXSOURCE®, SMARTCORE®,

SOLAR®, SYCAMORE NETWORKS®, TECHNOLOGY THAT TRANSFORMS THE WAY THE WORLD
COMMUNICATES™, ®
, TELLABS®, ®
, TELLABS PROPARTNER™, TELLABS. THE
FUTURE OF YOUR BUSINESS. STARTING NOW , THE WORLD COMMUNICATES THROUGH
™
TELLABS™, TITAN®, YOUR NETWORKING PARTNER®, XIEON NETWORKS™
Any other company or product names may be trademarks of their respective

companies.
76.01FP33/2-A Page 2 5/17

Table of Contents
1.0 Overview............................................................................................................................6
1.1 General Description.............................................................................................................. 6
1.2 Definition of Terms................................................................................................................ 6
1.2.1 Carrier Ethernet Terms............................................................................................................................. 6
1.2.1.1 Ethernet Virtual Connection (EVC)........................................................................................... 6
1.2.1.2 Network to Network Interface (NNI).......................................................................................... 6
1.2.1.3 User to Network Interface (UNI)................................................................................................ 6
1.2.1.4 Ethertype................................................................................................................................... 6
1.2.1.5 Class of Service........................................................................................................................ 7
1.2.2 IEEE 802.1ag Service Operation, Administration and Maintenance (OAM)............................................. 7
1.2.2.1 Maintenance Domain (MD)....................................................................................................... 7
1.2.2.2 Maintenance Association (MA)................................................................................................. 7
1.2.2.3 Maintenance Points ................................................................................................................. 7
1.2.2.4 Maintenance End Point (MEP).................................................................................................. 8
1.2.2.5 Maintenance Intermediate Point (MIP)..................................................................................... 8
1.2.3 IEEE 802.1ag Tools.................................................................................................................................. 8
1.2.3.1 Continuity Check ...................................................................................................................... 8
1.2.3.2 Loopback ................................................................................................................................. 8
1.2.3.3 Linktrace .................................................................................................................................. 8
1.2.4 ITU-T Y.1731 Performance Monitoring..................................................................................................... 9
1.2.4.1 2-Way Delay and Delay Variation............................................................................................. 9
1.2.4.2 1-Way Delay Variation............................................................................................................... 9
1.2.4.3 Loss and Availability.................................................................................................................. 9
1.2.5 RFC 2544 Service Activation Testing........................................................................................................ 9
1.2.5.1 Frame Loss Measurement........................................................................................................ 9
1.2.5.2 Latency Measurement.............................................................................................................. 9
1.2.5.3 Throughput Measurement......................................................................................................... 9
1.2.5.4 Back-to-Back Measurement.................................................................................................... 10
1.2.6 ITU-T Y.1564 Service Activation Testing................................................................................................. 10
1.2.7 RFC-5357 Two-Way Active Measurement Protocol (TWAMP)............................................................... 11
2.0 Installation, Verification and Configuration......................................................................12

2.1 Installing the 7090-01......................................................................................................... 12
2.2 Verifying the 7090-01.......................................................................................................... 12
2.3 Configuring the 7090-01..................................................................................................... 12
3.0 Network Application Example..........................................................................................14

3.1 7090-01 Requirements....................................................................................................... 16
3.1.1.1 IP Address Configuration........................................................................................................ 16
3.1.1.2 EVC Configuration.................................................................................................................. 16
3.1.2 IEEE 802.1ag Connectivity Fault Management...................................................................................... 17
3.1.2.1 IEEE 802.1ag Service OAM Configuration............................................................................. 17
3.1.3 7090-01 Configuration File..................................................................................................................... 19
3.1.3.1 Create the Configuration File.................................................................................................. 19
3.1.3.2 Load the Configuration File..................................................................................................... 19
3.1.3.3 Execute the Configuration File................................................................................................ 21
3.1.4 Fault Management.................................................................................................................................. 22
3.1.4.1 Continuity Check..................................................................................................................... 22
3.1.4.2 Loopback................................................................................................................................ 23
3.1.4.3 Linktrace................................................................................................................................. 24
3.1.5 ITU-T Y.1731 Performance Monitoring Configuration............................................................................. 25
3.1.5.1 Global Probe Configurations................................................................................................... 25
3.1.5.2 2-way Delay/Delay Variation (DMM/DMR) Probe................................................................... 26
3.1.5.3 Single Ended Loss/Availability (LMM/LMR) Probe................................................................. 28
76.01FP33/2-A Page 3 5/17

3.1.6 RFC 2544............................................................................................................................................... 30

3.1.6.1 Test Responder....................................................................................................................... 30
3.1.6.2 Test Initiator............................................................................................................................. 31
4.0 Hardware Overview.........................................................................................................33

4.1. Accessing The Command Line Interface............................................................................ 33
5.0 Command Line Interface.................................................................................................34

5.1 CLI Commands................................................................................................................... 36
5.1.1 Access Control List (ACL)....................................................................................................................... 36
5.1.2 Bandwidth Profile (BWP)........................................................................................................................ 38
5.1.3 Connectivity Fault Management (CFM).................................................................................................. 40
5.1.4 Class of Service (CoS)........................................................................................................................... 41
5.1.5 File Directory (DIR)................................................................................................................................. 43
5.1.6 Ethertype (ETHERTYPE)....................................................................................................................... 44
5.1.7 Ethernet Virtual Connection (EVC)......................................................................................................... 45
5.1.8 Create a Script File (FILE)...................................................................................................................... 47
5.1.9 Activate FPGA Code (FPGAUPD).......................................................................................................... 49
5.1.10 Interface (INTERFACE).......................................................................................................................... 50
5.1.11 IP Configuration Parameters (IP)............................................................................................................ 52
5.1.12 Layer 2 Control Protocol (L2CP)............................................................................................................ 53
5.1.13 IEEE 802.1ag Loopback (LBM).............................................................................................................. 56
5.1.14 IEEE 802.3ah Link OAM (LINKOAM)..................................................................................................... 58
5.1.15 Link Layer Discovery Protocol (LLDP).................................................................................................... 62
5.1.16 IEEE 802.1ag Linktrace (LTM)................................................................................................................ 64
5.1.17 Maintenance Association (MA)............................................................................................................... 67
5.1.18 Maintenance Domain (MD)..................................................................................................................... 70
5.1.19 Default Maintenance Domain (MDE)...................................................................................................... 73
5.1.20 Maintenance Points................................................................................................................................ 75
5.1.20.1 Maintenance End Point (MEP)................................................................................................ 75
5.1.20.2 Maintenance Intermediate Point (MIP)................................................................................... 78
5.1.21 Global Settings (MODULE)..................................................................................................................... 80
5.1.22 Ping (PING)............................................................................................................................................ 82
5.1.23 Port Attributes (PORT)............................................................................................................................ 83
5.1.24 Port Statistics (PORTSTAT).................................................................................................................... 84
5.1.25 ITU-T Y.1731 Performance Monitoring................................................................................................... 86
5.1.25.1 Probe (PROBE)...................................................................................................................... 86
5.1.25.2 Type 1: 2-way Delay/Variation (DMM/DMR) Probe Example.................................................. 93
5.1.25.3 Type 2: 1-way Delay/Variation (1DM) Probe Example............................................................ 96
5.1.25.4 Type 3: Single-Ended Loss/Availability (LMM/LMR) Probe Example..................................... 97
5.1.26 Protocol Configuration (PROTOCOL)..................................................................................................... 98
5.1.27 Restart (RESTART)................................................................................................................................ 99
5.1.28 Restore to Factory Defaults (RESTORE)............................................................................................. 100
5.1.29 IEEE 802.1ag Continuity Check Messages (RMEP)............................................................................ 101
5.1.30 Run a Script File (RUN)........................................................................................................................ 102
5.1.31 Save Configuration Changes (SAVE)................................................................................................... 104
5.1.32 SFP Port Information (SFP).................................................................................................................. 105
5.1.33 Display the Common Configuration Parameters (SHOWCONFIG)...................................................... 107
5.1.34 Simple Network Management Protocol (SNMP).................................................................................. 108
5.1.35 Simple Network Time Protocol (SNTP)..................................................................................................111
5.1.36 Ethernet Service Testing....................................................................................................................... 112
5.1.36.1 Overview............................................................................................................................... 112
5.1.36.2 Third-Party Test Equipment.................................................................................................. 112
5.1.36.3 Built-in Test Initiator (TESTINIT)........................................................................................... 112
5.1.36.4 Test Responder (TESTRESP).............................................................................................. 118
5.1.37 Set/Display Time of Day (TIME)........................................................................................................... 124
5.1.38 SNMP Trap Host (TRAPHOST)............................................................................................................ 125
5.1.39 SNMP Traps (TRAPS).......................................................................................................................... 126
5.1.40 Firmware Version (VER)....................................................................................................................... 130
5.1.41 Time Zone (ZONE)............................................................................................................................... 131
76.01FP33/2-A Page 4 5/17

6.0 Specifications................................................................................................................132
7.0 Appendix A: Network Topology Configurations Commands.........................................133

7.1 7090-01 - Location A......................................................................................................... 133
7.2 7090-01 - Location B........................................................................................................ 135
8.0 Appendix B: Firmware and FPGA Code Update .........................................................136

8.1 Overview........................................................................................................................... 136
8.2 Save Current Settings....................................................................................................... 136
8.3 Copy the Files to Your Hard Drive.................................................................................... 136
8.4 Recovering the 7090-01................................................................................................... 136
8.5 Update the 7090-01.......................................................................................................... 136
8.5.1 Updating the Firmware and FPGA Code Using FTP............................................................................ 136
8.5.1.1 Update the FPGA Code........................................................................................................ 137
8.5.1.2 Update the Firmware............................................................................................................ 139
9.0 Replacement and After-Sale Technical Support............................................................140
76.01FP33/2-A Page 5 5/17

1.0 OVERVIEW
This document describes the installation and configuration of the 7090-01 CE Ethernet SFP NID.
1.1 GENERAL DESCRIPTION
The 7090-01 is a 1310nm, 1000BASE-X Gigabit Ethernet Small Form Pluggable (SFP) Transceiver with
digital diagnostic monitoring and provides Fault Monitoring (FM) and Performance Monitoring (PM). It
can be installed directly into a demarcation, aggregation or any other network location adding advanced
FM and PM capabilities to non-Carrier Ethernet equipment; preserving investments in non-CE or legacy
switches and routers.
7090-01 CE Ethernet SFP NID

The 7090-01 supports Carrier Ethernet Service OAM standards. IEEE 802.1ag Connectivity Fault
Management (CFM) proactively monitors service availability and provides tools for rapid fault isolation.
ITU-T Y.1731 PM monitors key SLA parameters including frame delay, frame delay variation, and frame
loss. IEEE 802.3ah Link OAM monitors the individual network links for physical failures and provides
proactive fault detection and rapid isolation of potential service problems, enabling SLA assurance while
reducing Operational costs (OPEX).
For Ethernet Service Activation Testing, the 7090-01 supports ITU-T Y.1564 and IETF RFC 2544. These
standards allow Service Providers to rapidly verify the configuration and performance of Ethernet services
prior to customer hand off. The 7090-01 can also be configured to respond to RFC 2544, Y.1564 test
measurements from a Test Initiator or 3rd party test equipment (JDSU, Sunrise and VeEX). It can also be
configured to initiate or respond to TWAMP protocol.
1.2 DEFINITION OF TERMS
1.2.1 Carrier Ethernet Terms
1.2.1.1 Ethernet Virtual Connection (EVC)
An end-to-end Ethernet service is assigned an EVC which connects two physical interfaces creating a
virtual private connection between the interfaces. The interfaces can be a User Network Interface (UNI)
or a Network to Network Interface (NNI).
1.2.1.2 Network to Network Interface (NNI)
The NNI is an interface which specifies signaling and management functions between two networks.
1.2.1.3 User to Network Interface (UNI)
The UNI is a demarcation point between the responsibility of the service provider and the responsibility of
the subscriber. The UNI resides at the end user location and provides Ethernet service access.
1.2.1.4 Ethertype
Ethertype is a two-octet field in an Ethernet frame indicating which protocol is used to encapsulate VLAN
information in the frame data. UNI interfaces commonly use Ethertype 8100 to define the frame as a
802.1Q tagged VLAN. NNI interfaces commonly use Ethertype 88a8 to define the frame as a 802.1ad
Service Provider tagged EVC.
76.01FP33/2-A Page 6 5/17

1.2.1.5 Class of Service

Class of Service (CoS) provides the means for identifying traffic in a network by grouping similar types of
traffic (voice and video high priority, data low priority) into a service class and treating each class with its
own level of service priority (profiles). Traffic is classified based on the Priority Code Point (PCP). PCP
uses the three bits in the layer 2 packet header to specify priority.
1.2.2 IEEE 802.1ag Service Operation, Administration and Maintenance (OAM)
IEEE 802.1ag Service OAM Connectivity Fault Management provides the capability to detect, verify, and
isolate connectivity failures. 802.1ag Service OAM uses frames called OAM Protocol Data Units (PDU)
to send/receive messages to detect loss of service connectivity and perform loopback/linktrace tests to
verify and isolate faults along an end-to-end Ethernet connection.
To create an end-to-end Ethernet service path, 802.1ag uses the concepts of Maintenance Domains,
Maintenance Associations and Maintenance End Points.
1.2.2.1 Maintenance Domain (MD)
A Maintenance Domain defines a boundary of responsibility. There can be multiple carriers providing
an Ethernet service to a customer. Each carrier defines their boundary of responsibility, or domain level.
These levels make it easy to delineate the responsibilities and make it easy to manage and detect faults
along an Ethernet service. The figure below illustrates nested domains, where the Operator and Service
Provider Domains are nested under the Customer Domain.
The Service Provider delivers the service to the customer and monitors the performance of the service
to ensure the contracted Service Level Agreements are met. The Operator is typically a regional Local
Exchange Carrier (LEC) which often leases the network segments to a Service Provider who inturn provide
an end-to-end Ethernet service. This out-of-franchise application illustrates an end-to-end service path
between two customer locations spanning two or more Operator networks.
1.2.2.2 Maintenance Association (MA)

A Maintenance Association is a group of maintenance points that defines the physical end-to-end service path.
When a Maintenance Association is created, it is associated with a specific Maintenance Domain, VLAN
ID (EVC) and port number.
1.2.2.3 Maintenance Points
Any port on a network may be configured as a maintenance point. A maintenance point is classified as a
Maintenance Association End Point (MEP) or Maintenance Domain Intermediate Point (MIP). The table
below describes the function of each type of maintenance point.
76.01FP33/2-A Page 7 5/17

Maintenance Maintenance
Function End Point Intermediate Point
Initiates CFM OAMPDU messages Yes No
Responds to loopback and linktrace OAMPDU messages Yes Yes
Keeps track of continuity check OAMPDU messages received Yes Yes
Forwards CFM OAMPDU messages No Yes
1.2.2.4 Maintenance End Point (MEP)

Maintenance End Points reside at the edge of a Maintenance Domain and generate and terminate OAM
PDU messages. When a Maintenance End Point is created, it is associated with a specific Maintenance
Domain, Maintenance Association, VLAN ID (EVC) and port number.
A Maintenance End Point can be defined as UP or DOWN MEP. The figure below illustrates an UP and
DOWN MEP.
An UP MEP monitors the forwarding path internal to the node, while a DOWN MEP only monitors the
forwarding path external to the node. An UP MEP is configured on the ingress port, while the DOWN
MEP is configured on the egress port.
1.2.2.5 Maintenance Intermediate Point (MIP)
Maintenance Intermediate Points are internal to the domain. Maintenance Intermediate Points will forward
OAM PDUs. Maintenance Intermediate Points will forward and respond to loopback and linktrace OAM
PDUs. If the loopback message is intended for the Maintenance Intermediate Point, the loopback message
will not be forwarded.
1.2.3 IEEE 802.1ag Tools
The 802.1ag tools provide proactive and on-demand fault detection and fault isolation.
1.2.3.1 Continuity Check
Maintenance End Points automatically issue Continuity Check “heartbeat” messages (OAM PDUs) to detect
loss of service connectivity between end points. Maintenance End Points will detect a loss of connectivity
when three consecutive Continuity Check messages are not received. A Remote Detect Indicator (RDI)
message will be initiated on a loss of connectivity. Once an RDI is received, a service fault alarm is generated.
1.2.3.2 Loopback
A loopback command can be initiated by a network administrator to verify/isolate an issue with an end-to-end
service path. Loopback is initiated from a Maintenance End Point. Loopback indicates whether the
destination is reachable. It is similar to ICMP Echo Request/Reply (PING).
1.2.3.3 Linktrace
A linktrace command can be initiated by a network administrator to verify/isolate an issue with an end-to-end
service path. Linktrace is initiated from a Maintenance End Point. Maintenance End Points send linktrace
request messages to each Maintenance Point along the service path. Each Maintenance Point replies and
forwards the message along the service path. Each reply indicates the path is a reachable Maintenance
Point. Linktrace is similar to IP Traceroute.
76.01FP33/2-A Page 8 5/17

1.2.4 ITU-T Y.1731 Performance Monitoring

ITU-T Y.1731 Performance Monitoring tools provide statistics for delay, delay variation, loss and availability
between MEPs. There are three types of measurements that can be created between MEPs. Y.1731 uses
OAM PDU to send/receive messages to measure the different performance parameters. When enabled,
the OAM PDUs run continuously until disabled. Each performance measurement uses a different OAM
PDU message. They are:
1.2.4.1 2-Way Delay and Delay Variation
Delay Measurement Message (DMM): 2-way delay/variation OAM PDU message
Delay Measurement Reply (DMR): 2-way delay/variation OAM PDU reply
1.2.4.2 1-Way Delay Variation
One-way Delay Measurement (1DM): 1-way delay variation OAM PDU message
1.2.4.3 Loss and Availability
Loss Measurement Message (LMM): Single-ended loss/availability OAM PDU message
Loss Measurement Reply (LMR): Single-ended loss/availability OAM PDU reply
1.2.5 RFC 2544 Service Activation Testing

Ethernet connections must be tested to ensure that they are operating correctly and performing to the required
levels. RFC 2544 specifies certain test criteria that allow Ethernet connections to validate operation and
service level agreements. RFC 2544 performs specific tests using standard frame sizes (64, 128, 256, 512,
1024, 1280 and 1518 bytes).
1.2.5.1 Frame Loss Measurement
Frame loss is the number of frames that were transmitted from the source but were never received at the
destination. Frames can be lost or dropped.
1.2.5.2 Latency Measurement
Latency is the total round trip time for a frame to travel from source to destination and back. The time is
the sum of the processing delays in the network and the propagation delay along the transmission path.
1.2.5.3 Throughput Measurement
Data throughput is the maximum amount of data that can be transported from source to destination. The
maximum throughput for various frame sizes is shown:
1000 Mbps:
Frame Down MEP Down MEP Down MEP
Size Throughput Overhead Frames/sec
64 byte 761.90 Mbps 238.10 Mbps 1,488,095
128 byte 864.86 Mbps 135.14 Mbps 844,594
256 byte 927.54 Mbps 72.46 Mbps 452,898
512 byte 962.40 Mbps 37.59 Mbps 234,962
1024 byte 980.84 Mbps 19.16 Mbps 119,731
1280 byte 984.61 Mbps 15.38 Mbps 96,153
1518 byte 986.99 Mbps 13.00 Mbps 81,274
76.01FP33/2-A Page 9 5/17

Frame Up MEP Up MEP Up MEP

Size Throughput Overhead Frames/sec
64 byte 727.27 Mbps 272.73 Mbps 1,420,454
128 byte 842.11 Mbps 157.89 Mbps 822,368
256 byte 914.28 Mbps 85.72 Mbps 446,428
512 byte 955.22 Mbps 44.78 Mbps 233,208
1024 byte 977.09 Mbps 22.91 Mbps 119,274
1280 byte 981.59 Mbps 18.41 Mbps 95,858
1518 byte 984.43 Mbps 15.57 Mbps 81,063
Ethernet devices must allow a minimum idle period between transmission of Ethernet frames known as
the Inter-Frame Gap (IFG) or Inter-Packet Gap (IPG). The minimum inter-frame gap period is 96 bits or
12 bytes + 7 bytes of preamble and 1 byte of delimiter (20 bytes of overhead). An additional 4 bytes are
added for UP MEP interface to include one VLAN tag (24 bytes of overhead).
Down MEP Calculation (1000Mbps interface rate):
Frames/sec = 1 second / ((frame size + 20) x 8ns)
Throughput (Mbps) = frames/sec x frame size x 8
Up MEP Calculation (1000Mbps interface rate):
Frames/sec = 1 second / ((frame size + 24) x 8ns)
Throughput (Mbps) = frames/sec x frame size x 8
1.2.5.4 Back-to-Back Measurement
The back-to-back measurement sends a burst of frames with minimum inter-frame gaps to the responder
module. The frames are returned and counted by the initiator module. If the count of transmitted frames
is equal to the number of frames returned the length of the burst is increased and the test is rerun. The
back-to-back value is the number of frames with the longest burst that the responder module can handle
without any loss of frames.
NOTE: For RFC 2544 back-to-back measurements on UP MEP interfaces, the -bits or -rp command
must be used to alter the number of bits or rate for each frame size based on the table above.
For a 64 byte frame, the -bits value will be 727000000 or the -rp value will be 72.7 (assuming 1000Mbps
interface rate).
1.2.6 ITU-T Y.1564 Service Activation Testing
ITU-T Y.1564 is a Carrier Ethernet service activation test methodology for turning up, installing and
troubleshooting Ethernet-based services. The test methodology allows for complete validation of Ethernet
Service Level Agreements (SLAs) in a single test.
ITU-T Y.1564 defines test streams with specific attributes identified by different classifiers such as 802.1Q
VLAN, 802.1ad and class of service (CoS) profiles. These services are defined at the UNI level with
different frame and bandwidth profile such as frame size, committed information rate (CIR), and excess
information rate (EIR).
76.01FP33/2-A Page 10 5/17

1.2.7 RFC-5357 Two-Way Active Measurement Protocol (TWAMP)

The Two-Way Active Measurement Protocol (TWAMP) is a Layer 3 protocol for measuring network
performance between two devices supporting the TWAMP protocol. The TWAMP protocol includes
TWAMP-Control and TWAMP-Test. The TWAMP-Control protocol performs handshaking between
initiator and reflector to set up the measurement session. The TWAMP-Test protocol is used to send and
receive performance measurement data.
The initiator and reflector exchange test packets according to the TWAMP-Test protocol for each active
session. On receiving a TWAMP-Test packet, the session reflector only reflects a measurement packet and
does not collect packet statistics in TWAMP.
76.01FP33/2-A Page 11 5/17

2.0 INSTALLATION, VERIFICATION AND CONFIGURATION

2.1 INSTALLING THE 7090-01
Caution: Use proper ESD protection to reduce the risk of damage to your equipment.
a. Insert the 7090-01 into the SFP receptacle on the host device.
NOTE: The release latch of the SFP transceiver must be in the closed (up) position before
insertion.
b. Connect the appropriate single-mode fiber cable to the 7090-01. When using dual fiber, it is
important to ensure that the transmit (TX) is attached to the receive side of the device at the other
end and the receive (RX) is attached to the transmit side.
2.2 VERIFYING THE 7090-01
Once the 7090-01 is installed and the fiber cable is plugged into the 7090-01, verify the operational status
of the fiber port by viewing the status of the LED indicators of the host device. The fiber LED on the host
device will illuminate when the 7090-01 is receiving a signal from the device at the other end of the fiber
cable.
Verify connectivity by pinging the IP address of the 7090-01. Once connectivity has been verified, initiate
a Telnet session to configure the 7090-01.
2.3 CONFIGURING THE 7090-01

The 7090-01 can be configured through the fiber interface (P1) on the 7090-01 or through the electrical
interface (P2) on the 7090-01 via the host device. This provides the capability to remotely or locally
configure the 7090-01.
To minimize configuration and installation costs, the 7090-01 can be pre-configured at a host location than
deployed at the CPE location with minimal support. Once service has been provisioned and activated
between the CPE and Service Provider, the Service Provider can remotely manage and test the service
across the network.
The 7090-01 has the capability of having a configuration file downloaded via FTP and executed using
the Command Line Interface (CLI); run command. This allows service provisioning to be centralized
providing a simple and cost effective method to configure and deploy the 7090-01. See Section 5.0 on for
more information on using the CLI.
Once the 7090-01 is installed in the host device, open a Telnet session using the default IP address of the
7090-01. The default IP address is 10.0.0.1 and the default Telnet password is public. The 7090-01 supports
Telnet, SNMPv1, v2c and v3.
76.01FP33/2-A Page 12 5/17

When a Telnet session is initiated, the Password Entry screen will be displayed. Type the Telnet password
and press <ENTER>.
The CLI configuration screen prompt will be displayed.
Coriant 7090-01 CE FP3.3

Copyright 2017 Password Entry
-----------------------------------------------------------------------------
Coriant Technical Assistance Center(TAC)
1415 West Diehl Road On the web at:
Naperville, IL 60563 http://www.coriant.com/services_support
-----------------------------------------------------------------------------
IP address 10.0.0.1
MAC xx-xx-xx-xx-xx-xx
Serial number xxxxxx
Please enter the password >

>
76.01FP33/2-A Page 13 5/17

3.0 NETWORK APPLICATION EXAMPLE

This section provides a step-by-step example on how to configure key features on the 7090-01. For a detailed
explanation of the commands used in this example, refer to the specific sections for more information.
In this network application example, the customer initially purchased a “best effort” Ethernet circuit between
their two locations from the Service Provider.
The customer has upgraded their network and now requires guaranteed services between their locations.
The Service Provider upgrades the Access Links and provides an End-to-End Service between the customer
locations by installing an 7090-01 into the CPE equipment. The 7090-01 provides Service Activation, Fault
Management and Performance Monitoring of the Access Links and End-to-End Service.
NOTE: The Packet Transport Platform is shown as the aggregation device installed at the edge of
the CE 2.0 Service Provider Network. However, any CE compliant aggregation device can be used.
The Service Provider will create a single Ethernet Virtual Connection (EVC) for all customer data traffic.
Another EVC will be created for management. Management will be accessible over the Service Provider’s
network.
76.01FP33/2-A Page 14 5/17

In this example, only the Access Link and End-to-End Service paths will be shown. The same concepts
and features can be implemented across the Operator Network path.
Ethernet Service OAM (SOAM) is configured for fault management (IEEE 802.1ag) and performance
monitoring (ITU-T Y.1731). Fault management provides proactive and on-demand fault detection and
isolation. Performance monitoring will verify Service Level Agreements (SLAs) established by the Service
Provider.
76.01FP33/2-A Page 15 5/17

3.1 7090-01 REQUIREMENTS

The Service Provider will configure the 7090-01 to provide one EVC for customer data and one EVC for
management. Service OAM will be configured across the customer EVC to provide fault management
and performance monitoring. Service Activation Testing will be used to certify the customer EVC before
the service is handed off to the customer.
A configuration file with the requirements outlined above will be downloaded to each 7090-01 before the
equipment is deployed at the customer locations.
The configuration commands for each 7090-01 are shown in the following sections.
3.1.1 IP and EVC Configuration
3.1.1.1 IP Address Configuration
Each 7090-01 will be configured with a unique IP address.
7090-01 - Location A
CLI Command Description
> ip -addr 10.0.0.230 IP address configuration
7090-01 - Location B
> ip -addr 10.0.0.231 IP address configuration
See Section 5.1.11 for additional information on the ip command.

3.1.1.2 EVC Configuration
The 7090-01 will be configured with one EVC for customer data and one EVC for management. The
management EVC will be configured to allow the Service Provider NOC access to the 7090-01 over the
network.
A unique service name will be defined for each EVC.
Customer VLAN ID Ethertype EVC Service Name
100 Data
8100
- Mgt
NOTE: In this example, the customer traffic is tagged with VLAN 100.
Each EVC will be associated with one or more ports on the 7090-01. Port definitions for the 7090-01 are
illustrated below.
76.01FP33/2-A Page 16 5/17

The associations between the EVCs and ports define the path for each service on the 7090-01.
Customer EVC Internal 7090-01
Ethertype
VLAN ID Service Name VLAN ID Port Number
100 Data 1000 1,2
8100
- Mgt 2000 1,mgt1
7090-01 - Location A and B

> evc -dis Disable EVCs and delete
> evc -dall EVCs
> evc -a -e Data -p 1,2 -v 1000

Define EVCs
> evc -a -e Mgt -p 1,mgt1 -v 2000
> interface -a -p 1 -t uni -e Data:100 -e Mgt:* Associate EVC to the port,

> interface -a -p 2 -t uni -e Data:100 configure port VLAN ID and
> interface -a -p mgt1 -t uni -e Mgt:* configure port type
> evc -ena Enable EVCs
The following is an explanation of the commands used above:

EVC Name (-e) Data Mgt
Ports (-p) 1,2 1,mgt1
Internal Tag (-v) 1000 2000
Interface Type (-t) uni uni
VLAN ID (-e:) 100 Untagged (*)
See Section 5.1.7 and 5.1.10 for more information on the evc and interface commands.
3.1.2 IEEE 802.1ag Connectivity Fault Management

IEEE 802.1ag is used to detect and isolate connectivity failures on the Access Link and End-to-End Service
paths. The Service Provider will configure a Service OAM (SOAM) instance across the Access Link and
the End-to-End Service to verify service connectivity across the Data EVC.
In this example, only the End-to-End Service path will be configured. The same concepts and features can
be implemented across the Access Link.
3.1.2.1 IEEE 802.1ag Service OAM Configuration
IEEE 802.1ag Service OAM Connectivity Fault Management (CFM) provides capability to detect, verify
and isolate connectivity failures. Using 802.1ag CFM, loopback/linktrace tests can be performed to verify
and isolate faults along the End-to-End Service path. A SOAM instance called “End-to-End Service SOAM”
will be configured using a Maintenance Domain, Maintenance Association and Maintenance End Points.
End-to-End Service SOAM
7090-01 - Location A 7090-01 - Location B
Description Name Description Name
Maintenance Domain MD4 Maintenance Domain MD4
Maintenance Association MA4 Maintenance Association MA4
Maintenance End Point 230 Maintenance End Point 231
76.01FP33/2-A Page 17 5/17

> md -a -n MD4 -l 4
> ma -a -n MD4 -o MA4 -e Data -p 2
Create a MD, MA and MEP
> mep -a -n MD4 -o MA4 -e Data -p 2 -m 230 -up
> rmep -a -n MD4 -o MA4 -m 231
> cfm -ena all Enable CFM on all ports
The following is an explanation of the commands used above:

MD Name (-n) MD4 Maintenance Domain Name
MD Level (-l) 4 Maintenance Domain Level
MA Name (-o) MA4 Maintenance Association Name
EVC Name (-e) Data
Port # (-p) 2
MEP Name (-m) 230 Local Maintenance End Point Name
RMEP Name (-m) 231 Remote Maintenance End Point Name
Up MEP (-up) Maintenance End Point Direction
Enable 802.1ag (cfm) ena all
> md -a -n MD4 -l 4
Create a MD, MA and MEP
> cfm -ena all Enable CFM on all ports
See Section 5.1.18, 5.1.17, 5.1.20 and 5.1.29 for more information on the md, ma, mep and rmep commands.
76.01FP33/2-A Page 18 5/17

3.1.3 7090-01 Configuration File

The configuration parameters for each 7090-01 has been outlined in the previous sections. A configuration
file can now be created, downloaded and executed. This provides a simple and cost-effective method for
centralized provisioning of the 7090-01.
3.1.3.1 Create the Configuration File
Create a configuration file (text file) for each 7090-01 based on the information below. The file extension
must be a <filename>.osf.
7090-01 - Location A 7090-01 - Location B
ip -addr 10.0.0.230 ip -addr 10.0.0.231
evc -dis evc -dis
evc -dall evc -dall
evc -a -e Data -p 1,2 -v 1000 evc -a -e Data -p 1,2 -v 1000
evc -a -e Mgt -p 1,mgt1 -v 2000 evc -a -e Mgt -p 1,mgt1 -v 2000
interface -a -p 1 -t uni -e Data:100 -e Mgt:* interface -a -p 1 -t uni -e Data:100 -e Mgt:*
interface -a -p 2 -t uni -e Data:100 interface -a -p 2 -t uni -e Data:100
interface -a -p mgt1 -t uni -e Mgt:* interface -a -p mgt1 -t uni -e Mgt:*
evc -ena evc -ena
md -a -n MD4 -l 4 md -a -n MD4 -l 4
ma -a -n MD4 -o MA4 -e Data -p 2 ma -a -n MD4 -o MA4 -e Data -p 2
mep -a -n MD4 -o MA4 -e Data -p 2 -m 230 -up mep -a -n MD4 -o MA4 -e Data -p 2 -m 231 -up
rmep -a -n MD4 -o MA4 -m 231 rmep -a -n MD4 -o MA4 -m 230
cfm -ena all cfm -ena all
save save
3.1.3.2 Load the Configuration File

To load a configuration file on the 7090-01, FTP must be enabled and a FTP password configured. By
default, FTP is disabled and a default password is assigned.
Open a Telnet session to the default IP address of the 7090-01 (see Section 2.3 for more information).
To enable FTP and assign a FTP password, use the following command:
> protocol -ftp ena -ftppw *****
NOTE: Substitute a text password for the ***** in the command line above.
See Section 5.1.26 for more information on the protocol command.
76.01FP33/2-A Page 19 5/17

Open a DOS command window and enter the following commands. Bold lettering indicates information
to be entered.
> ftp 10.0.0.1 (default IP address)
Connected to 10.0.0.1
220 FTP server ready
User (10.0.0.1:(none)): admin (default login name)
331 Password required
Password: <enter ftp password> (enter ftp password previously assigned)
230 User logged in
ftp> quote tfs on
200 TFS Enabled
ftp> put <location and filename of the config file> (filename.osf)
200 OK
150 ready to take file
226 transfer complete
226 Saving file to flash... closing session
ftp: 2488 bytes sent in 0.89Seconds 1109.62Kbytes/sec.
ftp>quit (exit FTP session)
The configuration file has been transferred to the 7090-01.
Using the previously opened Telnet session, display the available files on the 7090-01 by using the run -l
command.
7090> run -l
Name Size
=================================
modelscfg.ini 11554
ag24hr.dat 2
snmp.key 1170
ag7day.dat 2528
FPGA.dat 2818080
Location_A.osf 2488
Total: 6 items listed (2835822 bytes)
7090>
Perform this operation for both 7090-01s.
76.01FP33/2-A Page 20 5/17

3.1.3.3 Execute the Configuration File

To execute the configuration file located on the 7090-01, use the run -f <filename> command.
7090> run -f Location_A.osf
Running script file :Location_A.osf

Executing cmd: ip -addr 10.0.0.230
Executing cmd: evc -dis
Executing cmd: evc -dall
Executing cmd: evc -a -e Data -p 1,2 -v 1000
Executing cmd: evc -a -e Mgt -p 1,2,mgt1 -v 2000
Executing cmd: interface -a -p 1 -t uni -e Data:100 -e Mgt:*
Executing cmd: interface -a -p 2 -t uni -e Data:100
Executing cmd: interface -a -p mgt1 -t uni -e Mgt:*
Executing cmd: evc -ena
Executing cmd: md -a -n MD4 -l 4
Executing cmd: ma -a -n MD4 -o MA4 -e Data -p 2
Executing cmd: mep -a -n MD4 -o MA4 -e Data -p 2 -m 230 -up
Executing cmd: rmep -a -n MD4 -o MA4 -m 231
Executing cmd: cfm -ena all
Executing cmd: save
7090>
Perform this operation for both 7090-01s.

After the configuration file has been executed, verify connectivity to the 7090-01 by pinging the new IP
address for each 7090-01 through the fiber port (P1). Once connectivity has been verified, the 7090-01s
are ready to be deployed to the customer’s locations.
76.01FP33/2-A Page 21 5/17

3.1.4 Fault Management

IEEE 802.1ag provides tools for proactive and on-demand fault detection and fault isolation. The available
tools are Continuity Check, Loopback and Linktrace.
Once the circuit between the customer and Service Provider has been provisioned, the Service Provider can
remotely manage the 7090-01 across the network. From the Service Provider NOC, open a Telnet session
using the IP address of the 7090-01 at Location A.
3.1.4.1 Continuity Check

Fault detection uses the Continuity Check protocol to detect connectivity failures and unintended connectivity
between Maintenance End Points within a Maintenance Association. Each MEP automatically transmits
Continuity Check Messages (CCM). Maintenance End Points will generate a SNMP loss of connectivity
trap when three consecutive Continuity Check messages are not received.
The rmep -s command displays the status of the connection between Maintenance End Points. If configured
correctly, the Status/Defect column will indicate OK/None or OK/RDI. This indicates Continuity Check
Messages are received by the MEPs. See Section 5.1.29 for more information on the rmep command.
CLI Command
> rmep -s
Auto learning is disabled
Local Remote MD MA MD Port Vlan Status/ MAC Domain Name/

MEPID MEPID Idx Idx Lvl Num Id Defect Addr Maint Assoc
================================================================================
230 231 1 1 4 2 100 OK/None 00-06-87-01-da-84 MD4/MA4
76.01FP33/2-A Page 22 5/17

3.1.4.2 Loopback
Loopback verifies bidirectional connectivity with a remote MEP. Loopback can be initiated from either the
local or remote MEP. The initiating MEP sends Loopback Messages (LBM) to verify service connectivity
to remote MEP. The remote MEP will respond with a Loopback Response (LBR). See Section 5.1.13 for
more information on the lbm command.
To initiate a loopback test from MEP 230 on the 7090-01 Location A to MEP 231 on the 7090-01 Location
B, use the following command:
> lbm -p 2 -n MD4 -m 231 -v 100 -r 5 -sz 100 Configures loopback
The following is an explanation of the commands used in this section:

Port # (-p) 2
MD Name (-n) MD4
Destination MEP ID (-m) 231
Primary VLAN ID (-v) 100
# of LBMs to send (-r) 5
Data size (-sz) 100 bytes
CLI Command
> lbm -p 2 -n MD4 -m 231 -v 100 -r 5 -sz 100
Loopback request to 00-06-87-01-da-84 with 100 bytes of data:

Reply 1 from 00-06-87-01-da-84 bytes 100 time=1 ms
Loopback statistics for 00-06-87-01-da-84:

Packets: Sent = 5, Received successfully = 5, Lost = 0 (0 % loss)
Late = 0, Data comparison fail = 0
Min delay = 1 ms, Max delay = 1 ms, Average = 1 ms
Frame variation = 0 ms, Std deviation = 0 ms
Successful loopback will indicate the same number of packets sent as received.
76.01FP33/2-A Page 23 5/17

3.1.4.3 Linktrace
Linktrace is used to isolate faults within a Maintenance Domain. Linktrace can be initiated from either the
local or remote MEP. The initiating MEP sends Linktrace Messages (LTM) to track the path to a destination
MEP. Each Maintenance Point (MEP or MIP) along the path will respond with a Linktrace Response (LTR).
See Section 5.1.16 for more information on the ltm command.
To initiate a linktrace test from MEP 230 on the 7090-01 Location A to MEP 231 on the 7090-01 Location
B, use the following command:
> ltm -p 2 -n MD4 -m 231 -v 100 Configures linktrace

Port # (-p) 2
MD Name (-n) MD4
VLAN ID (-v) 100
CLI Command
> ltm -p 2 -n MD4 -m 231 -v 100
MD index=1 MA Index=1 MEP ID=230 Transaction id 5. TTL 64.

Linktrace sent from Chassis 1, Slot 1, Port 2 00-06-87-02-17-5a
Tracing the route to 00-06-87-01-da-84 on Domain Level 4, vlan 100
Hit any key to terminate.
Last Egress ID Ingress MAC Relay Ingress Ingress Port

Hop Next Egress ID Egress MAC Reply Egress Egress Port
================================================================================
1 00-00:00-06-87-02-17-5a --:--:--:--:--:-- RlyHit ----- ------
00-00:00-06-87-01-da-84 00-06-87-01-da-84 Term MEP EgrOK Port 2
>
Successful linktrace will indicate Term MEP in the Relay Reply column. See Section 5.1.16 for more
information on other Relay Reply messages.
76.01FP33/2-A Page 24 5/17

3.1.5 ITU-T Y.1731 Performance Monitoring Configuration

ITU-T Y.1731 Performance Monitoring is used to ensure the Ethernet service is meeting the contracted
requirements purchased by the customer. Y.1731 Performance Monitoring tools provide statistics for
delay, delay variation, loss and availability between MEPs. Type 1 and Type 3 probes will be configured
and verified.
Type 1 Frame Delay: 2-way delay/delay variation (DMM/DMR)
Type 3 Frame Loss: Single ended loss/availability (LMM/LMR)
3.1.5.1 Global Probe Configurations
Performance monitoring data is collected during a predetermined measurement time interval. The time
interval is referred to as the measurement interval or bucket time. During the measurement interval, the
performance monitoring data is grouped into time interval bins. Each bin has a minimum and maximum
time limit and the performance monitoring data is counted by the bin that corresponds to the performance
monitoring data value.
Performance monitoring data packets are transmitted every 1 sec by default. The transmission rate can be
modified using the -i command. The number of performance monitoring data packets counted during a bucket
time is equal to the transmission time interval multiplied by the bucket time in seconds. (Example: transmission
time interval = 1 sec, bucket time = 5 minutes or 60 seconds and number of performance monitoring
packets = 1 packet/sec x 60 seconds = 60 packets).
See Section 5.1.25 for more information on the probe command.
Global probe settings need to be configured on both 7090-01s. From the Service Provider NOC, open a
another Telnet session using the IP address of the 7090-01 at Location B.
7090-01 - Location A and B
Configure bucket time = 5 minute and
> probe -g -bt 5 -bin 1,2,3,4,10 bins = 0 to 1ms, 1 to 2ms, 2 to 3ms,
3 to 4ms, 4 to 10ms and >10ms
> probe -ena Enable probes

Measurement Interval (-bt) 5 minutes
BINs (-bin) 1, 2, 3, 4, 10
Y.1731 Compatibility Mode (-ena) Enable
76.01FP33/2-A Page 25 5/17

3.1.5.2 2-way Delay/Delay Variation (DMM/DMR) Probe

Type 1 (DMM/DMR) probe measures frame delay and frame delay variation. A Type 1 probe can be initiated
from either the local or remote MEP. The initiating MEP transmits a Delay Measurement Message (DMM)
data packet every second by default to the remote MEP. The remote MEP replies with a Delay Measurement
Reply (DMR) data packet. The messages are collected during the measurement interval (bucket time). The
messages are then classified in specific frame delay time interval bins for that bucket time.
To configure a Type 1, 2-way delay/delay variation (DMM/DMR) probe from MEP 230 on the 7090-01
Location A to MEP 231 on the 7090-01 Location B, use the following command:
> probe -a -p 2 -ty 1 -n MD4 -o MA4 -m 231 Configures type 1 probe

Probe Type (-ty) 1
MD Name (-n) MD4
MA Name (-o) MA4
76.01FP33/2-A Page 26 5/17

CLI Command
> probe -a -p 2 -ty 1 -n MD4 -o MA4 -m 231
> probe -s
Probes enabled
Measurement Interval (Bucket size) = 1 min
Frame Delay Bins: Frame Delay Variation Bins:
Bin #1 Frame delay >= 0 and < 1 Bin #1 Delay variation >= 0 and < 5
Bin #2 Frame delay >= 1 and < 2 Bin #2 Delay variation >= 5
Bin #3 Frame delay >= 2 and < 3
Bin #6 Frame delay >= 10
--- Probe #1 -------------------------------------------------------------

Name:
Port 2 Type = 2-way delay/variation, DMR synchronization, 1 sec
Destination 00-06-87-01-da-84 (Domain Level = 4 ; VLAN = 100 ; Priority = 0)
Acceptance Criteria: FD < 1000.0ms, IFDV < 1000.0ms
2-way Frame Delay Frame Variation Total Frames

Min Max Ave Min Max Ave Tx Rx
========================== ========================== ============
10s: 0.004 0.006 0.006 0.000 0.002 0.000 10 10
1 min: 0.004 0.006 0.006 0.000 0.002 0.001 60 60
5 min: 0.004 0.006 0.006 0.000 0.002 0.000 300 300
15 min: 0.004 0.006 0.006 0.000 0.002 0.000 900 900
1-way Forward FD Frame Variation Total Frames

========================== ========================== ============
10s: 0.002 0.003 0.003 0.000 0.001 0.000 10 10
1 min: 0.002 0.003 0.003 0.000 0.001 0.000 60 60
5 min: 0.002 0.003 0.003 0.000 0.001 0.000 300 300
15 min: 0.002 0.003 0.003 0.000 0.001 0.000 900 900
1-way Backward FD Frame Variation Total Frames

========================== ========================== ============
10s: 0.002 0.003 0.003 0.000 0.001 0.000 10 10
1 min: 0.002 0.003 0.003 0.000 0.001 0.000 60 60
5 min: 0.002 0.003 0.003 0.000 0.001 0.000 300 300
15 min: 0.002 0.003 0.003 0.000 0.001 0.000 900 900
NOTE: Y.1731 probes are configured with a pbit priority (-pri) of 0 by default. Probes can be
configured to verify performance measurements at different priority levels by changing the pbit
value (-pri) when configuring a probe.
76.01FP33/2-A Page 27 5/17

3.1.5.3 Single Ended Loss/Availability (LMM/LMR) Probe

Type 3 (LMM/LMR) probes measure frame loss and availability. A Type 3 probe can be initiated from
either the local or remote MEP. The initiating MEP transmits a Loss Measurement Message (LMM) data
packet every second by default to the remote MEP. The remote MEP replies with a Loss Measurement
Reply (LMR) data packet. The messages are collected during a predefined measurement time interval.
The messages are then classified in specific frame loss time interval bins for that bucket time.
To configure a Type 3, Single ended loss/availability (LMM/LMR) probe from MEP 230 on the 7090-01
Location A to MEP 231 on the 7090-01 Location B, use the following command:
> probe -a -p 2 -ty 3 -n MD4 -o MA4 -m 231 Configures type 3 probe

Probe Type (-ty) 3
MD Name (-n) MD4
MA Name (-o) MA4
76.01FP33/2-A Page 28 5/17

CLI Command
> probe -s
Probes enabled
--- Probe #1 -------------------------------------------------------------

Name:
Port 2 Type = frame loss and availability v2, single ended, EVC based, 1 sec
Destination 00-06-87-01-da-84 (Domain Level = 4 ; VLAN = 100 ; Priority = 0)
Acceptance Criteria: FLR < 50.0%, Availability > 50%
LMM Far-End (Forward)

Tx Sent Received Loss Avail
===== ========================================
10s: 10 20 20 0.0% 100.0%
1 min: 60 641 641 0.0% 100.0%
5 min: 300 1127 1127 0.0% 100.0%
15 min: 900 2355 2355 0.0% 100.0%
LMR Near-End (Backward)

Rx Sent Received Loss Avail
===== ========================================
10s: 10 20 20 0.0% 100.0%
1 min: 60 125 125 0.0% 100.0%
5 min: 300 606 606 0.0% 100.0%
15 min: 900 1828 1828 0.0% 100.0%
value (-pri) when configuring a probe.
76.01FP33/2-A Page 29 5/17

3.1.6 RFC 2544

RFC 2544 performs specific test measurements using standard frame sizes (64, 128, 256, 512, 1024, 1280
and 1518 bytes).
The 7090-01 has a built-in RFC 2544 test head providing frame loss, latency, throughput and back-to-back
measurements between an initiator and responder. 7090-01 Location A will be configured as the initiator
(test head) and the 7090-01 Location B will be configured as the responder.
The initiator will generate frames based on the user-defined configuration. The responder receives the
frames and loops the traffic back to the initiator.
The initiator will be configured to run a throughput test to verify the Data EVC. See Section 5.1.36 for
more information on the testinit and testresp commands.
NOTE: Always configure the Test Responder before configuring the Test Initiator.
3.1.6.1 Test Responder

Configure 7090-01 Location B as a test responder using the following command:
CLI Command
> testresp -a -p 2 -pe 1 -v 100 -e Data -pn Test

Port # (-p) 2
Egress Port # (-pe) 1
VLAN ID (-v) 100
EVC Name (-e) Data
Test Name (-pn) Test
Relay Action MAC swap (default option)
76.01FP33/2-A Page 30 5/17

To view the responder, use the testresp -s command.

CLI Command
> testresp -s
Product: 7090-01 CE (7301A)

Firmware version: v1.0.xx, serial number: 00713589, FPGA: v0.xx
Date & Time: 01/01/2000 18:23 (sysUpTime: 6622841)
Globals: Test Generator enabled, Test Monitor enabled
--- Test Responder Instance #1 -------------------------------------------

Test Name: Test, Responding Port 2, Destination Port 1
Test Responder enabled, Test Monitor enabled, Multicast Replacement disabled
Standard response disabled, Out-of-Service enabled
Reply Type: MAC Swap (Remote protocol: None)
Test Association: EVC (ethertype 9001)
EVC name “Data” (VID 100)
Local MAC Match disabled
Received frame counts: 0

Transmitted frame counts: 0
3.1.6.2 Test Initiator

Configure the 7090-01 Location A as a test initiator using the following command:
CLI Command
> testinit -a -p 2 -pe 1 -v 100 -e Data -pn Test -typ throughput -fst

Port # (-p) 2
Egress Port # (-pe) 1
VLAN ID (-v) 100
EVC Name (-e) Data
Initiator Name (-pn) Test
Test Type (-typ) Throughput
Frame Size (-fst) 64, 128, 256, 512, 1024, 1280, 1518
76.01FP33/2-A Page 31 5/17

Once the commands are entered, the test is automatically initiated. To view the results, use the testinit -s
command.
CLI Command
> testinit -s
Product: 7090-01 CE (7301A)

--- Test Initiator Instance #1 -----------------------------------------------

Test Name: Test, Source Port 2, Destination Port 1
Test Generator enabled, Test Monitor enabled, Out-of-Service
Test Status: Test iteration active for 7s
Test Type: 2544 Throughput
Frame sizes: 64, 128, 256, 512, 1024, 1280, 1518 (standard)
Acceptable frame loss: 10 frames/trial, fixed search (10%)
Number of trials: 1; test duration: 10s
Data payload: zeros
Test Association: EVC
EVC name “Data” (VID 100), PCP value 0, use policer:on
Test Partner: MAC 00-00-00-00-00-01
Remote Protocol: None
Initial Line Rate: 1,000,000,000 bits/sec (L1 rate calculation type)
Trial/ Frame -----Configured----- Transmit Receive Frame Frames Test

Iter Size (fps) (mbps) % Count Count Loss % Lost Status
*******************************************************************************
1/1 64 1488095 1000.0 100 14880950 14880950 0.000 0 PASS
1/2 128 844594 1000.0 100 8445940 8445940 0.000 0 PASS
1/3 256 452898 1000.0 100 4528980 4528980 0.000 0 PASS
1/4 512 234962 1000.0 100 2349620 2349620 0.000 0 PASS
1/5 1024 119731 1000.0 100 1197310 1197310 0.000 0 PASS
1/6 1280 96153 1000.0 100 961530 961530 0.000 0 PASS
1/7 1518 81274 1000.0 100 812740 812740 0.000 0 PASS
76.01FP33/2-A Page 32 5/17

4.0 HARDWARE OVERVIEW

The 7090-01 is a hot-pluggable 1310nm, 1000BASE-X Gigabit Ethernet SFP transceiver with digital
diagnostic monitoring. The fiber interface is Port 1 (P1) and the electrical interface is Port 2 (P2). The
electrical interface is accessible via the host device.
4.1. ACCESSING THE COMMAND LINE INTERFACE

The 7090-01 can be accessed using the default IP address. It supports Telnet, SNMPv1, v2c and v3. Access
is available through the fiber port or the electrical port via the host device
When a Telnet session is initiated, the Password Entry screen will be displayed. Type the Telnet password
and press <ENTER>, the CLI configuration screen prompt is displayed.
Coriant 7090-01 CE FP3.3

Copyright 2017 Password Entry
-----------------------------------------------------------------------------
Coriant Technical Assistance Center(TAC)
1415 West Diehl Road On the web at:
Naperville, IL 60563 http://www.coriant.com/services_support
-----------------------------------------------------------------------------
IP address 10.0.0.1
MAC xx-xx-xx-xx-xx-xx
Serial number xxxxxx
Please enter the password >

>
76.01FP33/2-A Page 33 5/17

5.0 COMMAND LINE INTERFACE

Each 7090-01 is configured with the following defaults:
IP
IP Address 10.0.0.1
IP Subnet Mask 255.255.255.0
IP Gateway 10.0.0.254
Protocols
IP Enabled
TELNET Enabled
FTP Disabled
DHCP Client Disabled
Passwords
FTP public
TELNET public
SNMPv1/v2c Communities
READ public
WRITE public
SNMPv1/v2c agent enabled
SNMPv3 Parameters
SNMPv3 agent enabled
User 1 Type read-only User 2 Type admin
User 1 Name guest User 2 Name admin
User 1 security level noAuthNoPriv User 2 security level noAuthNoPriv
User 1 privacy password publicguest User 2 privacy password privateadmin
User 1 authentication password publicguest User 2 authentication password privateadmin
User 3 Type deny User 4 Type deny
User 3 Name guest1 User 4 Name guest2
User 3 security level noAuthNoPriv User 4 security level noAuthNoPriv
User 3 privacy password publicguest User 4 privacy password publicgues
User 3 authentication password publicguest User 4 authentication password publicguest
General SNMP Parameters
SNMP trap type SNMPv2c
Other Networking Parameters
Keep Alive Trap Disabled
Keep Alive Trap interval 10 seconds
Link OAM Tunneled
LLDP Tunneled
The 7090-01 supports passwords for the Telnet, FTP, SNMPv1 and v3. It is highly recommended that the
passwords be changed in order to prevent unauthorized access to the 7090-01.
NOTE: FTP must be enabled to perform firmware or FPGA upgrades.
76.01FP33/2-A Page 34 5/17
At the module prompt (>), enter ?, help or h to view the command options.
7090> ?
CLI Command summary
For more help on a specific command, type the <command> -h
Command Description
acl Access Control List for management access
bwp Bandwidth profile command
cfm CFM global configuration command
cos Class of service configuration
dir List the existing files
ethertype Module Ethertype selection for customer and network ports
evc Module Ethernet Virtual Connection configuration
file File open and close command
fpgaupd Updates the FPGA firmware
h Display the CLI command summary (same as help command)
help Display the CLI command summary
interface Module port interface configuration
ip IP Configuration for network 1
l2cp Layer 2 Control Protocol configuration
lbm CFM loopback message configuration
linkoam Link OAM (802.3ah) configuration
lldp Link Layer Discovery Protocol configuration
ltm CFM Linktrace configuration
ma CFM maintenance association configuration
md CFM maintenance domain configuration
mde CFM default maintenance domain setup
mep CFM maintenance end point configuration
mip CFM maintenance intermediate point configuration
module Displays module global information
ping Generates a ping to a remote device
port Port attribute configuration
portstat Displays current stats for each port
probe CFM performance metric probe
protocol Protocol configuration
restart Restarts the module
restore Restore local or factory defaults
rmep CFM remote MEP configuration
run Execute script file
save Stores configuration changes into permanent memory
sfp Display SFP port information
showconfig Shows basic configuration information
snmp SNMP configuration
sntp Simple Network Time Protocol configuration
testinit Test Initiator
testresp Test Responder
time Displays the module time of day
traphost SNMP Trap Host configuration
traps Module trap setup
ver Displays the firmware version
x Log user out
zone Time zone help
? Display the CLI command summary (same as help command)
7090>
To exit the Telnet session, type exit or x at the CLI prompt.

NOTE: The commands in the CLI take effect immediately, but the save command must be used to
ensure the information is retained when the power is removed from the 7090-01. If the save command
is not used, the configuration changes will be lost.
76.01FP33/2-A Page 35 5/17
5.1 CLI COMMANDS

The commands are presented in alphabetical order and should not be used as configuration guide. Each
command has an explanation and configuration example.
5.1.1 Access Control List (ACL)
The module provides basic traffic filtering capabilities with Access Control Lists (ACL). Access Control
Lists can prevent certain traffic from entering or exiting the management port. ACLs can be configured
for ARP, ICMP, IP, TCP and UDP protocols. These protocols can be configured to be permitted or denied
access. Two hundred individual ACLs can be configured at one time.
The acl command provides the ability to configure ACL traffic filtering. To configure ACL, use the acl
option from the CLI prompt. A list of options is displayed when the acl -h command is entered.
7090> acl -h
Description: Access Control List for management access

Format: acl [-a [idx]|-d idx|-dall|-h|-m idx|-s] [-ena|dis]
[-ipsrc ipAddr[,ipAddrEnd] [-ty {deny|permit}] [-dst port] [-src port]
[-dflt {deny|permit}] [-ver]
Switches:
-a add selected ACL, index [idx]: {1..199}
-d delete selected ACL index [idx]: {1..199}
-dall delete all ACLs
-dflt default for items not found in ACL list: {deny|permit}, default permit
-dis disable ACL processing, default
-dst TCP/UDP destination port [port]: {-1..65535}
-ena enable ACL processing
-h display help information
-ipsrc source IP address
[ipAddr] IP address (individual or starting address)
[ipAddrEnd] ending IP address if present
-m modify selected ACL
-proto protocol: {arp,icmp,ip,tcp,udp}, default ip
-s show current configuration
-src TCP or UDP source port number [port]: {-1..65535}
-ty set the ACL access type -aty: {deny|permit}
-ver verbose help
7090>
The options available using the acl command are shown below.
The -a switch adds a new ACL filter.
The -d switch deletes an existing ACL filter by index number.
The -dall switch deletes all configured ACL filters.
The -dflt switch selects a default behavior for items not found in the ACL list. The default is permit.
The -dis switch disables ACL processing.
The -dst switch selects a TCP or UDP destination port number for an ACL filter. A value of -1 does not
select a specific TCP or UDP port.
The -ena switch enables ACL processing. If the ACL table is empty, the default behavior (-dflt) is applied
to all Ethernet frames that enter the module.
The -h switch displays the help screen presented above. It is static and provides help information for the
specific command.
76.01FP33/2-A Page 36 5/17

The -ipsrc switch selects the IP source address for an ACL filter. The source IP address for ARP is the
“Send IP Address”.
The -m switch modifies an existing ACL filter.
The -proto switch selects the protocol:
arp selects the ARP protocol.
icmp selects the ICMP protocol.
ip selects the IP protocol.
tcp selects the TCP protocol.
udp selects the UDP protocol.
The -s switch displays the configured ACL filters.
The -src switch selects a TCP or IP source port number for an ACL filter. A value of -1 does not select a
specific TCP or UDP port .
The -ty switch selects the ACL access type; permit or deny.
The -ver switch displays the extended help.
To display the configuration, use the acl -s command.
7090> acl -s
ACL processing is Disabled

Default ACL behavior is ‘permit’
7090>
To allow access to a device, the module must be configured to allow (permit) ARP and IP. Since ICMP
is part of the IP protocol, it must be explicitly excluded. ACL filters are processed in the order displayed.
7090> acl -ena

7090> acl -dall
7090> acl -a -ipsrc 172.16.9.1,172.16.9.5 -proto icmp -ty deny
7090> acl -a -ipsrc 172.16.9.1,172.16.9.5 -proto ip -ty permit
7090> acl -a -ipsrc 172.16.9.5,172.16.9.5 -proto arp -ty permit
7090> acl -s
ACL processing is Enabled

Default ACL behavior is ‘permit’
# ACL Details
1 172.16.9.1..172.16.9.5 ICMP via mgt1: deny
2 172.16.9.1..172.16.9.5 IP via mgt1: permit
3 172.16.9.5..172.16.9.5 ARP via mgt1: permit
7090>
76.01FP33/2-A Page 37 5/17

5.1.2 Bandwidth Profile (BWP)

The bwp command provides the ability to create a bandwidth profiles used as test criteria for ITU-T Y.1564.
NOTE: The bandwidth profiles do not rate limit the traffic on the port or EVC. It is only used by
the Y.1564 Test Initiator to determine test parameters.
Bandwidth profiles specifies the average rate of committed and excess Ethernet frames allowed. Bandwidth
profiles consist of the following parameters:
Committed Information Rate (CIR)
CIR specifies the average rate Ethernet frames are delivered per service performance objectives. These
frames are referred to as being in-profile (green). CIR is an average rate because all frames are sent at
the interface speed (e.g.,10M, 100M, 1G).
Committed Burst Size (CBS)
CBS is the maximum number of bytes allowed for incoming Ethernet frames maintaining in-profile. The
value of CBS will depend on the type of application or traffic being supported. Bursty data applications
will require a larger CBS than more constant rate applications. The default value is 150 KB.
Excess Information Rate (EIR)
EIR specifies the average excess service frames (>CIR) transmitted into the provider network. EIR
frames are out of profile (yellow) and may be discarded.
Excessive Burst Size (EBS)
EBS is the maximum number of bytes allowed for incoming Ethernet frames to be EIR-conformant.
The default value is 150 KB.
Coupling Flag (CF)
When the Coupling Flag is enabled, CIR and EIR rates are combined and the traffic is marked as yellow.
Coupling Flag is always disabled.
76.01FP33/2-A Page 38 5/17

To create a bandwidth profile to be used by the ITU-T Y.1564 Test Initiator, use the bwp command from
the CLI prompt. A list of options is displayed when the bwp -h command is entered.
7090> bwp -h
Description: Bandwidth profile configuration

Format: bwp [-a|-d|-dall|-h [-ver]|-m|-s] [-p portNum] [-n profileName]
[-cir cirRate] [-eir eirRate] [-uni|-e evcName] [-cn cName] [-dis|-ena]
[-pol poltype]
Switches:
-a add profile
-cir committed ingress information rate [cirRate] in kb/sec: {0...1000000},
default=0
-cn class of service identifier name [cName], 1-45 ASCII characters
-d delete profile
-dall deletes all the configured ingress and egress bandwidth profiles
-dis disable bandwidth profile
-e bandwidth profile associated with [evcName], 1-45 ASCII characters
-eir excess information rate [eirRate] in kb/sec: {0...1000000}, default=0
-ena enable bandwidth profile (default)
-m modifies profile
-n defines [profileName], 1-45 ASCII characters
-p [portNum] selected: {1,2}
-pol [poltype] port policing count type: {L1,L2,L3}, default is L2
-s shows bandwidth profile configuration
-uni bandwidth profile associated with uni (port)
-ver verbose help
7090>
The options available using the bwp command are shown below.
The -a switch adds a bandwidth profile to a port.
The -cir switch sets the Committed Information Rate of the ingress frame.
The -cn switch defines the name of the Class of Service profile.
The -d switch deletes the bandwidth profile.
The -dall switch deletes all configured bandwidth profiles.
The -dis switch disables all defined bandwidth profiles.
The -e switch defines the EVC associated with the bandwidth profile.
The -eir switch defines the average Excess Information Rate of the ingress frame.
The -ena switch enables all defined bandwidth profiles.
specific command.
The -m switch modifies a defined bandwidth profile.
The -n switch defines the name of the bandwidth profile.
The -p switch defines the port associated with the bandwidth profile.
The -pol switch defines the policing count as layer 1, layer 2 or layer 3 frame types on a per port basis.
The -s switch displays the current bandwidth profiles.
The -uni switch associates a bandwidth profile with a UNI port.
The -ver switch displays extend help screen.
76.01FP33/2-A Page 39 5/17

To create a bandwidth profile with a CIR of 100,000 kb/sec and a EIR of 100,000 kb/sec for Port 1, use
the following commands.
7090> bwp -a -cir 1000000 -eir 1000000 -p 1 -n bwp
In profile traffic (CIR) is marked Green. Out of profile traffic (EIR) is marked Yellow.
To display the bandwidth profiles, use the bwp -s command.
7090> bwp -s
Port 1
Profile “bwp1” : cir=100000 cbs=150 eir=100000 ebs=150; UNI based ; enabled; cf disabled
Port 2
No ingress bandwidth profile defined, port is operating at full speed
Unassigned Profiles:
7090>
5.1.3 Connectivity Fault Management (CFM)

The cfm command provides the ability to globally enable or disable Connectivity Fault Management function
on the 7090-01. If CFM is disabled, CFM frames will be processed as normal Ethernet Service traffic. If
CFM is enabled, CFM frames will be processed according to the 802.1ag specification.
To enable or disable CFM, use the cfm command from the CLI prompt. A list of options is displayed when
the cfm -h command is entered.
7090> cfm -h
Description: Update global CFM settings

Format: cfm [-dall|-h [-ver]|-s] [{-ena|-dis} portnum]
Switches:
-dall restore factory defaults
-dis disable cfm protocol on the selected [portnum]: {1,2,all}
-ena enable cfm protocol on the selected [portnum]: {1,2,all}
-s shows the cfm global configuration
-ver verbose help
7090>
The options available using the cfm command are shown below.
The -dall restores the CFM settings to factory default.
The -dis and -ena switches disable or enable the CFM protocol on a configured port.
specific command.
The -s switch displays the CFM configuration.
76.01FP33/2-A Page 40 5/17

To enable CFM on all ports, using the -ena command.
7090> cfm -s
Port 1: CFM is disabled

Port 2: CFM is disabled
7090> cfm -ena all

7090> cfm -s
Port 1: CFM is enabled

Port 2: CFM is enabled
7090>
5.1.4 Class of Service (CoS)

The cos command provides the ability to configure and display Class of Service profiles associated with
each port. CoS profiles are assigned to bandwidth profiles and used as test criteria for ITU-T Y.1564 testing.
To configure class of service, use the cos option from the CLI prompt. A list of options is displayed when
the cos -h command is entered.
7090> cos -h
Description: Class of Service configuration

Format: cos [-a|-d|-dall|-h [-ver]|-m|-s] [-cn cName] [-g gPri] [-y yPri]
[-pcp pbits]
Switches:
-a add CoS profile
-d delete CoS profile
-dall delete all CoS configured profiles
-g sets the green traffic priority (gPri) and class of service (gClass)
When the traffic is classified as “green” the following applies:
green priority [gPri]: {0...7}, default 7
used for S-TAG Cos (PCP bits) when provider tag added to the frame
-m modifies CoS profile
-pcp bandwidth profile associated with tag priority [pbits]: {0..7,0..7}
-s shows CoS configuration
-ver verbose help
-y sets the yellow traffic priority (yPri)
When the traffic is classified as “yellow” the following applies:
yellow priority [yPri]: {0...7}, default 1
used for S-TAG Cos (PCP bits) when provider tag added to the frame
7090>
The options available using the cos command are shown below.
The -a switch adds a class of service profile.
The -cn switch defines the name of the class of service profile.
The -d switch deletes a class of service profile.
The -dall switch deletes all configured CoS profiles.
The -g switch sets the PCP bits for green traffic priority (for egress frames within the defined CIR) in the
provider tag and the green class of service (used for egress queuing).
specific command.
76.01FP33/2-A Page 41 5/17

The -m switch modifies a defined class of service profile.

The -pcp switch defines the profile based on the PCP bit of the ingress frame.
The -s switch displays the current class of service profiles.
The -y switch sets the PCP bits for yellow traffic priority (for egress frames exceeding the defined CIR) in
the provider tag and the yellow class of service (used for egress queuing).
Class of Service profiles provides the means for identifying traffic in a network by grouping similar types
of traffic into a service class and treating each class with it own level of service priority.
Class of Service profiles uses the PCP fields to assign priority to ingress frames. Priority Code Point (PCP)
profiles are associated with the tagged priority bits (pbits). Values are 0 - 7.
In the example below four class of service profiles are created. Each profile is assigned a name (-cn), a
priority and class based on the PCP value of the ingress frame.
7090> cos -a -cn bronze -g 1,1 -pcp 0..1

7090> cos -a -cn silver -g 3,2 -pcp 2..3
7090> cos -a -cn gold -g 6,3 -pcp 4..6
7090> cos -a -cn platinum -g 7,4 -pcp 7
To display the configuration, use the cos -s command.
7090> cos -s
Class of Service “bronze”: PCP 0..1

green priority 1 class 1
yellow priority 1 class 1
Class of Service “silver”: PCP 2..3
Class of Service “gold”: PCP 4..6
Class of Service “platinum”: PCP 7
7090>
76.01FP33/2-A Page 42 5/17

5.1.5 File Directory (DIR)

The dir command provides the ability to view/delete files stored on the 7090-01.
To view/delete the files stored on the 7090-01, use the dir command from the CLI prompt. A list of options
is displayed when the dir -h command is entered.
7090> dir -h
Description: List the existing files

Format: dir [-d filename]|[-h [-ver]]|[-s]
Switches:
-d delete specified file, [filename]
-s list available files
-ver verbose help
7090>
The options available using the dir command are shown below.
The -d switch is used to delete a specific file on the 7090-01.
specific command.
The -s switch displays the files stored on the 7090-01.
To display the files stored on the 7090-01, use the dir -s command.
7090> dir -s
Size Name
==============================
64905 modelscfg.ini
2 ag24hr.dat
1170 snmp.key
64533 modelscfgold.ini
3145760 SFPNID_FPGA_V00xx.dat
116 ag7day.dat
7090>
76.01FP33/2-A Page 43 5/17

5.1.6 Ethertype (ETHERTYPE)

The ethertype command provides the ability to configure the protocol used to encapsulate a VLAN tagged
frame. Ethertype is a two-octet field in an Ethernet frame indicating which protocol is used to encapsulate
tag information in the frame data.
To configure the Ethertype, use the ethertype command from the CLI prompt. A list of options is displayed
when the ethertype -h command is entered.
7090> ethertype -h
Description: Ethertype selection for tag identification

Format: ethertype [-h [-ver]|-s] [{-uni|-nni} ethertypeVal]
Switches:
-nni selects provider network [ethertypeVal]
[ethertypeVal] selects the Ethertype that is used for the selected
network type, value is entered in hex, typical selection for
customer networks is 8100, for provider networks 88a8
default for customer/provider networks is 8100
-s show port configuration
-uni selects customer network [ethertypeVal]
[ethertypeVal] selects the Ethertype that is used for the selected
network type, value is entered in hex, typical selection for
customer networks is 8100, for provider networks 88a8
default for customer/provider networks is 8100
-ver verbose help
7090>
The options available using the ethertype command are shown below.
specific command.
The -nni and -uni switches allow configuration of the Ethertype for provider and customer tagged frames.
The -s switch displays the Ethertype configuration of the 7090-01.
Use the following commands to configure the NNI port for a Ethertype value of 88a8 (S-Tag) and the UNI
port for a Ethertype of 8100 (C-Tag).
7090> ethertype -nni 88a8
7090> ethertype -uni 8100
Network to Network Interface (NNI) is an interface which specifies signaling and management functions
between two networks.
User Network Interface (UNI) is a demarcation point between the responsibility of the service provider
and the responsibility of the subscriber.
To display the Ethertype configuration, use the ethertype -s command.
7090> ethertype -s
Customer (UNI) Ethertype value is 8100
Provider (NNI) Ethertype value is 88a8
7090>
76.01FP33/2-A Page 44 5/17

5.1.7 Ethernet Virtual Connection (EVC)

The evc command provides the ability to configure and display EVCs on the 7090-01. An EVC provides
a logical connection between two end points creating a point-to-point Ethernet connection.
To configure EVCs, use the evc command from the CLI prompt. A list of options is displayed when the
evc -h command is entered.
7090> evc -h
Description: Ethernet Virtual Connection (EVC) configuration

Format: evc [-a|-d|-dall|-h [-ver]|-s] [-e evcName] [-v evcVid]
[-p ports] [-pri pbits] [-ena|-dis] [-enaevc evcName] [-disevc evcName]
Switches:
-a add selected EVC on specified port
-d delete selected EVC
-dall deletes all the configured EVCs
-dis disable global EVC processing
-disevc disable specific evc: [evcName], 1-45 ASCII characters
-e [evcName] associated with the primary vlan id, 1-45 ASCII characters
-ena enable global EVC processing
-enaevc enable specific evc: [evcName], 1-45 ASCII characters
-p [portNum] selected: {1,2,mgt1,all}
-pri provider vlan priority bits, [pbits], for PDU if sent tagged;
-s show EVC configuration for specified port
-v [evcVid] associated with provider tag: {0...4095}
-ver verbose help
7090>
The options available using the evc command are shown below.
The -a switch allows an EVC to be added and configured. The add command must have an EVC name
and the port association specified.
The -d switch deletes a previously defined EVC for all ports.
The -dall switch deletes all configured EVCs.
The -dis switch globally disables all EVCs.
The -disevc switch disables a specific EVC.
The -e switch defines the name of the new EVC or the name of an EVC to be deleted. EVCs are defined
and selected by its name.
The -ena switch globally enables all EVCs. For an EVC to be enabled, the EVC must be globally and
individually enabled.
The -enaevc switch enables a specific EVC. When an EVC is created it is locally enabled.
specific command.
The -p switch defines one or more ports on the 7090-01 to be used when an EVC is added or deleted. All
user available ports can be assigned to one or more EVCs. The management ports (mgt1) can be assigned
to none or one EVC.
The -pri switch allows modification of the priority bits in the providers VLAN ID.
The -s switch displays the current EVC configurations for the 7090-01.
76.01FP33/2-A Page 45 5/17

The -v switch defines the S-TAG (provider tag) associated with the EVC. It can be the same value for two
different EVCs.
An EVC allows customer Ethernet frames to be exchanged between UNIs that are connected via the same
EVC. Customer frames may be VLAN tagged or untagged. A provider may also add an additional VLAN
tag to the Ethernet frame to isolate the customer VLAN tag. To distinguish the customer VLAN tag from
the provider tag, the customer VLAN is referred to as CE-VLAN (Customer Edge VLAN ID).
The CE-VLAN tag contains the 802.1p field defining the Class of Service priority for the frame. The CoS
field is referred to as CE-VLAN CoS.
Ethernet Frame with 802.1Q Tag
Ethernet Frame with Q-in-Q Tag

The 7090-01 has factory configured EVCs. To display the EVCs configured on the 7090-01, use the evc -s
command.
7090> evc -s
EVC processing is globally disabled
“mgt” associated with provider tag 999 on ports All; EVC enabled
“default” associated with provider tag 1 on ports 1,2; EVC enabled
7090>
When configuring a factory default 7090-01, make sure to disable EVCs and delete the management and
default EVCs before configuring the new EVCs.
7090> evc -dis

7090> evc -dall
76.01FP33/2-A Page 46 5/17

The example below configures an EVC called “mgt” with a VLAN ID of 2000 on Ports 1, 2 and mgt1.
7090> evc -a -e mgt -p 1,2,mgt1 -v 2000
The example below configures an EVC called “Data” with a VLAN ID of 1000 on Ports 1 and 2.
7090> evc -a -e Data -p 1,2 -v 1000
To display the configured EVCs, use the evc -s command.
7090> evc -s
EVC processing is globally disabled
“Data” associated with provider tag 1000 on ports 1,2; EVC enabled
“mgt” associated with provider tag 2000 on ports 1,2,Mgt1; EVC enabled
7090>
To globally disable EVCs, use the -dis command.
7090> evc -dis
To globally enable EVCs, use the -ena command.
7090> evc -ena
5.1.8 Create a Script File (FILE)

The file command provides the ability to create and save a configuration file to the module. After a file
has been opened, all typed CLI commands are written to the file. None of the commands typed will be
executed, only written to the open file. After the file is closed, the run command can be used to execute
the saved CLI commands.
To create a file on the 7090-01, use the file command from the CLI prompt. A list of options is displayed
when the file -h command is entered.
7090> file -h
Description: file open and close

Format: file [-h [-ver]|-s|-open filename|-close]
Switches:
-close close the currently open file
-open creates a file [filename]
-s shows the file open status
-ver verbose help
7090>
The options available using the file command are shown below.
The -close switch stops the capture of all typed commands and saves the file.
specific command.
76.01FP33/2-A Page 47 5/17

The -open switch starts the capture of all typed commands.

The -s switch displays the open file status.
To create a file, use the -open command. The filename must have the .osf extension.
7090> file -open MetroConfig.osf
All CLI commands typed after the file has been opened is automatically saved in the file. Once complete
with the configuration, close the file using the -close command.
7090> file -close
To execute the file, use the run -f <filename.osf> command.
7090> run -f MetroConfig.osf

Running script file :MetroConfig.osf
Executing cmd:....
To verify the file has been saved, use the run -l command.
7090> run -l
Name Size
=================================
MetroConfig.osf 34
modelscfg.ini 11554
ag24hr.dat 2
snmp.key 1170
ag7day.dat 2528
SFPNID_FPGA_V00xx.dat 2818080
7090>
76.01FP33/2-A Page 48 5/17

5.1.9 Activate FPGA Code (FPGAUPD)

The fpgaupd command provides the ability to activate the FPGA on the 7090-01 after the code has been
transferred (FTP) to the module. See Appendix B for more information on how to upgrade the FPGA code.
To activate the FPGA code stored on the 7090-01, use the fpgaupd command from the CLI prompt. A list
of options is displayed when the fpgaupd -h command is entered.
7090> fpgaupd -h
Description: FPGA firmware update

Format: fpgaupd [-h [-ver]|-s|-w fileName] [-act]
Switches:
-act activate the FPGA firmware
-s shows the FPGA firmware version information
-ver verbose help
-w writes to the FPGA, [fileName], 1-23 ASCII characters
7090>
The options available using the fpgaupd command are shown below.
The -act switch will activate the newly loaded FPGA code.
specific command.
The -s switch displays the current FPGA information.
The -w switch writes the new FPGA code into memory.
NOTE: When upgrading the 7090-01 firmware and FPGA code, always upgrade the FPGA first,
before the 7090-01 firmware is upgraded.
To update the FPGA, use the -w and -act commands.
7090> fpgaupd -w <filename> -act
FPGA programming process started...

FPGA programming 2097152 bytes to device.......................
FPGA programming successful
Verifying 2097152 bytes from device...
FPGA verification successful
FPGA programming process complete.
FPGA restarted
7090>
To verify the update, use the fpgaupd -s command.
7090> fpgaupd -s
FPGA revision:
v0.xx 09/02/2016 12:02:00
7090>
76.01FP33/2-A Page 49 5/17

5.1.10 Interface (INTERFACE)

The interface command provides the ability to associate EVCs to specific ports (P1 and/or P2) on the
7090-01. The port type (NNI or UNI) can also be configured using the interface command.
To configure the ports on the 7090-01, use the interface command from the CLI prompt. A list of options
is displayed when the interface -h command is entered.
7090> interface -h
Description: Interface configuration

Format: interface [-a|-d|-h [-ver]|-s] [-p port] [-e evcName[:vidrange]]
[-pt evcName:primaryVID] [-t type]
Switches:
-a add an EVC association on a specific port
-d delete an EVC association on a specific port
-e selects the [vidrange] for the specified [evcName]
[evcName] is the name of the EVC as defined by the evc command
[vidrange] for a UNI port are the CE-VLANs: { *, 0..4095 | all | rest}
Note: The asterisk indicates untagged data.
-pt select for the specific UNI [evcName] the [primaryVID]: {0...4095}
If this option is not present the [primaryVID] defaults to smallest
vid in the [vidrange]
-s shows the interface configuration
-t selects port [type] for the specified port: {uni|nni}
-ver verbose help
7090>
The options available using the interface command are shown below.
The -a switch allows an EVC association and configuration to be added to a port.
The -d switch deletes an EVC association on the selected port.
The -e switch defines the EVC association that is being added or deleted on a port.
specific command.
The -p switch defines one or more ports on the 7090-01 to be used when an EVC is added or deleted, or
when a port type is changed or defined.
The -pt switch overrides the MEF definition of the primary VID being the smallest VID number in a
range and allows support of the generic CFM implementation. If the -pt switch is not defined on an EVC
association, it defaults to the smallest VID in the range. It is used with the -e switch.
The -s switch displays the current EVC associations and configurations for all the ports on the 7090-01.
The -t switch defines the specified port as an UNI or NNI port type.
76.01FP33/2-A Page 50 5/17

CE-VLAN ID on UNI ports can be configured with several vidrange options including:
VLAN 200..300 Indicates range of VLAN ID from 200 to 300.
all Indicates VLAN 1 - 4095.
rest Indicates all VLAN not specifically defined.
* Indicates untagged traffic.
The * can be combined with the other parameters to include untagged traffic (all*, rest*, 200...300*).
Configuring a CE-VLAN for 0 is the same as using the * for untagged traffic.
The example below configures Port 1 and 2 to be associated with a “Data” EVC, with a customer VLAN
ID 100.
7090> interface -a -p 1 -t uni -e Data:100

7090> interface -a -p 2 -t uni -e Data:100
The example below configures the management port and Port 1 to be associated with a “mgt” EVC and
accept untagged traffic.
7090> interface -a -p mgt1 -t uni -e mgt:*

7090> interface -a -p 1 -t uni -e mgt:*
Once an EVC range has been configured, it must be deleted before the range can be changed or swapped.
To display the configuration of the interface, use the interface -s command.
7090> interface -s
Port 1 (Comp ID 1) is type UNI [MAC 00-06-87-02-17-59]

EVC “mgt”; CE-VLAN Map *
EVC “Data” (primary VID 100); CE-VLAN Map 100
Port 2 (Comp ID 1) is type UNI [MAC 00-06-87-02-17-5a]
EVC “Data” (primary VID 100); CE-VLAN Map 100
Mgt1 (Comp ID 1) is type UNI [MAC 00-06-87-02-17-58]
EVC “mgt”; CE-VLAN Map *
7090>
76.01FP33/2-A Page 51 5/17

5.1.11 IP Configuration Parameters (IP)

The ip command provides the ability to configure the IP address, subnet mask and gateway of the 7090-01.
It also allows DHCP to be disabled or enabled.
To configure IP, use the ip command from the CLI prompt. A list of options is displayed when the ip -h
command is entered.
7090> ip -h
Description: IP Configuration
Format: ip [-h [-ver]|-s] [-addr ipAddr] [-net subNet] [-gw gateway]
[{-dis|ena} dhcp]
Switches:
-addr sets manual IP address [ipAddr]
-dis disable function: {dhcp}, default
-ena enable function: {dhcp}
[dhcp] DHCP protocol enable/disable
-gw set gateway address [gateway]
-net set subnet mask [subNet]
-s shows current IP settings
-ver verbose help
7090>
The options available using the ip command are shown below.

The -addr switch configures the IP address of the 7090-01.
The -dis switch disables DHCP client.
The -ena switch enables DHCP client.
The -gw switch configures the gateway IP address of the 7090-01.
specific command.
The -net switch configures the subnet mask of the 7090-01.
The -s switch displays the current IP configuration.
Use the -s command to view the IP configuration of the 7090-01.
7090> ip -s
MAC address: 00-06-87-02-17-58
IP 1
IP address: 10.0.0.1
Subnet mask: 255.255.255.0
Gateway address: 10.0.0.254
DHCP Disabled
7090>
To configure the IP address of the 7090-01, use the -addr command.
7090> ip -addr 10.0.0.100
76.01FP33/2-A Page 52 5/17

5.1.12 Layer 2 Control Protocol (L2CP)

The l2cp command provides the ability to configure and display L2CP frame control on each port. To keep
Service Provider and Customer networks separate, each port can be independently configured to tunnel,
forward, discard or peer L2CP frames. This prevents unauthorized interaction between the Service Provider
and Customer networks.
To configure Layer 2 Control Protocols, use the l2cp command from the CLI prompt. A list of options is
displayed when the l2cp -h command is entered.
7090> l2cp -h
Description: Layer 2 Control Protocol (Reserved Address) configuration

Format: l2cp [-a|-h [-ver]|-s] [-mac macAddress | -msh sMacAddr | -n l2Name]
[-p portNum] [-c l2cpControl]
Switches:
-a add or change selection
-c type of [l2cpControl]: {discard,tunnel,forward,peer}, default “tunnel”
-mac destination MAC Address, [macAddr]: {xx-xx-xx-xx-xx-xx}
-msh short destination MAC Address, [sMacAddr]: {xx}
Where resultant MAC address is 01-80-c2-00-00-xx
Slow protocol configuration is via mnemonics lacp, marker, and linkoam
-n specifies destination MAC address based upon name:
{rstp, lacp, marker, linkoam, 802.1x, macp, elmi, pbridge, gvrp,
lldp, garp, undef}
-p [portNum] selected: {1,2,all}
-s shows l2cp configuration
-ver verbose help
Where:
rstp Rapid Spanning Tree, DA=01-80-c2-00-00-00
lacp Link aggregation control protocol, DA=01-80-c2-00-00-02, subtype=1
marker Marker protocol, DA=01-80-c2-00-00-02, subtype=2
linkoam Link OAM 802.3ah protocol, DA=01-80-c2-00-00-02, subtype=3
802.1x Port Authentication protocol, DA=01-80-c2-00-00-03
macp IEEE MAC specific protocols, DA=01-80-c2-00-00-04
elmi Ethernet Local Management Interface, DA=01-80-c2-00-00-07
pbridge Provider Bridge Group Address, DA=01-80-c2-00-00-08
gvrp Provider Bridge GVRP Address, DA=01-80-c2-00-00-0D
lldp Link Layer Discovery Protocol (Nearest Bridge), DA=01-80-c2-00-00-0E
garp Generic Address Registration Protocol, DA=01-80-c2-00-00-2X
undef Undefined addresses block, DA=01-80-c2-00-00-xx,
where xx is 05, 06, 09, 0A, 0B, 0C, 0F, and undefined subtypes of 02
7090>
The options available using the l2cp command are shown below.
The -a switch allows L2CP protocol to be added or changed.
The -c switch defines the way the protocol is handled by the port (discard, tunnel, forward or peer).
specific command.
The -mac switch defines the MAC address of the L2CP protocol to be added or changed.
The -msh switch allows the MAC address to be shortened to the least significant octet.
The -n switch defines the name of the L2CP protocol is be added or changed.
The -p switch defines the port associated with L2CP protocol.
76.01FP33/2-A Page 53 5/17

The -s switch displays the current L2CP protocol configuration.

L2CP frames have specific destination MAC addresses that belongs to reserved multicast MAC addresses.
The range of L2CP destination MAC addresses are 01-80-C2-00-00-00 through 01-80-C2-00-00-0F and
01-80-C2-00-00-20 through 01-80-C2-00-00-2F. Several L2CP frames share the same destination MAC
address.
Generally, all L2CP frames are untagged. If the L2CP frame is tagged, the frame will be treated as normal
Ethernet traffic and the L2CP controls (Discard, Forward, Tunnel and Peer) will be ignored.
The definition of the L2CP controls are:
Discard
The ingress frame will be dropped and no reply is generated. No L2CP frame will egress a port
configured as Discard.
Forward
The ingress frame will not be altered. All EVC rules will be ignored as the frame egress the port
(unmodified). The frame only egresses ports that are configured as Forwarding ports.
Tunnel
The ingress frame will be treated as normal Ethernet service data. When the frame egresses the port,
it will follow the EVC rules configured on the 7090-01.
When customer LAN segments are interconnected across a Service Provider network, tunneling enables
Layer 2 Control Protocols to be transported across a Service Provide network without any interaction.
This provides a L2CP connection between the customer LAN segment end-points.
76.01FP33/2-A Page 54 5/17

Peer
When configured as Peer, the port will participate in the specific Layer 2 Control Protocol. The frame
will be processed according to the specification of the protocol.
Generally, all L2CP frames are either discarded, forwarded or tunneled. However, certain Layer 2
Control Protocols may be peered at the ingress port. LACP and E-LMI are examples of two Layer 2
Control Protocols that may require peering.
To display the configuration of the L2CP Protocols, use the l2cp -s command.
7090> l2cp -s
Destination Address Port 1 Port 2

01-80-c2-00-00-00 (RSTP) tunnel tunnel
01-80-c2-00-00-01 (Pause) discard discard
01-80-c2-00-00-02 (LACP) tunnel tunnel
01-80-c2-00-00-02 (Marker) tunnel tunnel
01-80-c2-00-00-02 (Link OAM) tunnel tunnel
01-80-c2-00-00-02 () tunnel tunnel
01-80-c2-00-00-03 (802.1x) tunnel tunnel
01-80-c2-00-00-04 (IEEE MAC) tunnel tunnel
01-80-c2-00-00-05 () tunnel tunnel
01-80-c2-00-00-06 () tunnel tunnel
01-80-c2-00-00-07 (E-LMI) tunnel tunnel
01-80-c2-00-00-08 (Pr Bridge) tunnel tunnel
01-80-c2-00-00-09 () tunnel tunnel
01-80-c2-00-00-0a () tunnel tunnel
01-80-c2-00-00-0b () tunnel tunnel
01-80-c2-00-00-0c () tunnel tunnel
01-80-c2-00-00-0d (GVRP) tunnel tunnel
01-80-c2-00-00-0e (LLDP) tunnel tunnel
01-80-c2-00-00-0f () tunnel tunnel
01-80-c2-00-00-2X (GARP) tunnel tunnel
7090>
To configure Port 2 on the 7090-01 to forward LLDP, use the -n lldp command.
7090> l2cp -a -p 2 -n lldp -c forward
76.01FP33/2-A Page 55 5/17

5.1.13 IEEE 802.1ag Loopback (LBM)

The loopback command provides the ability to initiate and display the result of a loopback test between two
MEPs on the same Maintenance Association and Maintenance Domain. MEPs are able to send loopback
messages (LBM) to verify service connectivity to a particular maintenance point. Loopback indicates
whether the destination is reachable. The MEP will respond with Loopback Responses (LBR).
To enable loopback testing, use the lbm option from the CLI prompt. A list of options is displayed when
the lbm -h command is entered.
7090> lbm -h
Description: CFM loopback message configuration

Format: lbm [-c|-h|-s] [-p portNum] [-n domainName | -l domainLevel |
-ni dindex] [-o maName | -oi mindex] [-mac macAddr] [-m mepid]
[-v primaryVid | -e evcName] [-r cnt] [-t testData] [-ver]
[-sz size | -fsz frameSize] [-f freq] [-pri pbits] [-to timeoutVal]
Switches:
-c clear current loopback statistics of the MEP/MIP
-f frequency (in ms) to send PDUs, default is 1s: {0,100...60000}
-fsz specifies Ethernet [frameSize], uses data TLV to adjust length
-l maintenance [domainLevel]: {0...7}
-m destination mep ID, [mepid], unique within a MA: {1...8191}
-n defines [domainName], 1-43 ASCII characters
-ni domain name index, [dindex], for the md table
-o short maintenance association name,[maName], 1-45 ASCII characters
-oi short maintenance name index,[mindex], for the ma table
-p [portNum] selected: {1|2}
-pri vlan priority bits, [pbits], for PDU sent if tagged; default value is 0
-r repeat count, [rcnt], number of LBMs to be transmitted
0 = continuous transmission until stopped; Default = 3 for unicast LBM
-s show the current loopback statistics kept in this MEP/MIP
-sz TLV packet [size]; filled with testData or random if not defined
-t [testData], pattern of data in ASCII hex bytes: {0-9,A-F}, 1...16 bytes
-to sets the PDU [timeoutVal] in seconds: {1...10}, default 5 sec
-v [primaryVid] associated with the MA: {0...4095}
-ver extended help or display of loopback full statistics
7090>
The options available using the lbm command are shown below.
The -c switch clears the loopback statistics for a specified MEP/MIP.
The -e switch associates the loopback test with a specific EVC.
The -f switch defines the time interval between LBM PDU messages.
The -fsz switch defines the frame size of the loopback data.
specific command.
The -l, -n, and -ni switches indicate a specific level, domain name and index.
The -m switch defines the destination MEP.
The -mac switch defines the destination MAC address.
The -o and -oi switches indicate a specific maintenance association name and index.
The -p switch associates a specific port for loopback.
76.01FP33/2-A Page 56 5/17

The -pri switch defines the specific VLAN priority bits for the LBM PDU.
The -r switch defines the number of times the loopback test will be run.
The -s switch displays the current loopback statistics.
The -sz switch defines the size of the data pattern used during the loopback test.
The -t switch defines the data pattern used.
The -to switch set the timeout value.
The -v switch associates a specific VID.
The -ver switch displays extended help or loopback statistics.
The example below performs a loopback test on Maintenance Domain “MD4” with remote Maintenance
End Point 231 on VLAN ID 100. Other options include setting the size of the test pattern (-sz) and the
number of attempts (-r).
7090> lbm -p 2 -n MD4 -m 231 -v 100 -r 5 -sz 100
Loopback request to 00-06-87-01-74-ee with 100 bytes of data:

Reply 1 from 00-06-87-01-74-ee bytes 100 time=1 ms
Loopback statistics for 00-06-87-01-74-ee:

Packets: Sent = 5, Received successfully = 5, Lost = 0 (0 % loss)
Late = 0, Data comparison fail = 0
Min delay = 1 ms, Max delay = 1 ms, Average = 1 ms
Frame variation = 0 ms, Std deviation = 0 ms
7090>
To display the loopback statistics, use the lbm -s command.
7090> lbm -s
Loopback statistics for MEP ID 231 initiated by MD4 level 4 MA4 Port 2
Total messages LBM sent = 5
Total in order valid messages received = 5
Total out of order valid messages received = 0
Total data compare failures = 0
Total number of LBRs transmitted = 0
7090>
76.01FP33/2-A Page 57 5/17

5.1.14 IEEE 802.3ah Link OAM (LINKOAM)

The linkoam command provides the ability to configure and monitor IEEE 802.3ah connectivity. By default
802.3ah is disabled.
To configure/monitor IEEE 802.3ah, use the linkoam option from the CLI prompt. A list of options is
displayed when the linkoam -h command is entered.
7090> linkoam -h
Description: Link OAM (802.3ah) configuration

Format: linkoam [-h [-ver]|-s] [-p portNum] [-m oamMode] [-lb {on|off}]
[-to timeout] [{-dis|-ena} oamFunction] [-e type,window,threshold]
[-cri criticalSelect] [-txrate tvalue] [-clr]
Switches:
-clr clear event counters
-cri configure critical event
[criticalSelect]: {0,1..n,1..n}, based upon [traps] command number
0 clears the list
-dis disable selected oamFunction: {lb,eve,cri}
-ena enable selected oamFunction: {lb,eve,cri}
[lb] Link OAM loopback, default enabled
[eve] Link OAM event generation, default enabled
[cri] Link OAM critical event generation, default disabled
-e set event [type] [window] time to [threshold] for the specified port,
[type]: {symbol-period | frame | frame-period | frame-sec}
[window] is size of the event window in seconds
[threshold] is number of errors before event is triggered
-lb remote loopback mode state: {on|off}
-m configure oamMode: {active,passive]
-p [portNum] selected: {1|2|all}
-s shows the Link OAM configuration
-to loopback timeout: {0...300} in seconds, where 0 disables timeout
-txrate OAM PDU transmission rate (tvalue): {5...100} in frames/sec, default 10
-ver verbose help
7090>
The options available using the linkoam command are shown below.
The -clr switch clears the event counters.
The -cri switch configures the traps associated with critical alarm notification.
The -dis switch disables Link OAM loopback (lb), Link OAM unidirectional mode (uni), Link OAM event
generation (eve) and Link OAM critical event generation (cri).
The -ena switch enables Link OAM loopback (lb), Link OAM unidirectional mode (uni), Link OAM event
generation (eve) and Link OAM critical event generation (cri).
The -e switch configures the event type (type), the event window (window) and the event threshold
(threshold) parameters.
specific command.
The -lb switch enables/disables remote loopback. The default is disabled.
The -m switch configures the OAM mode (active or passive). The default OAM mode is passive.
The -p switch associates a specific port for Link OAM configuration.
The -s switch displays the Link OAM configuration and event statistics.
76.01FP33/2-A Page 58 5/17

The -to switch configures the loopback timeout parameter. A 0 value disables the timeout.
The -txrate switch configures the OAM PDU transmission rate. The default is 10 seconds.
To display the Link OAM configuration, use the linkoam -s command.
7090> linkoam -s
Modes Port 1 Port 2

802.3ah OAM State Disabled Disabled
OAM Mode Passive Passive
Critical events Disabled Disabled
Loopback Mode Disabled Disabled
Loopback Timeout 30 sec 30 sec
OAM Transmission Rate 10 fps 10 fps
Local Status
Discovery State Disabled Disabled
Multiplexer State Forward Forward
Parser Action Forward Forward
Critical Event No No
Link Fault No No
Supports Unknown Unknown
Remote Status
Discovery State Disabled Disabled
Multiplexer State Unknown Unknown
Parser Action Unknown Unknown
Critical Event No No
Link Fault No No
Mode Unknown Unknown
Supports Unknown Unknown
OUI: Unknown Unknown
Link Events - Windows (sec)
Symbol Period 1 1
Frame 1 1
Frame Period 1 1
Frame Sec 1 1
Link Events - Thresholds
Symbol Period 1 1
Frame 1 1
Frame Period 1 1
Frame Sec 1 1
Link Events Running Totals
Symbol Period 0 0
Frame 0 0
Frame Period 0 0
Frame Sec 0 0
Link Errors Running Totals
Symbol Period 0 0
Frame 0 0
Frame Period 0 0
Frame Sec 0 0
7090>
NOTE: To enable Link OAM, use the L2CP commands.
76.01FP33/2-A Page 59 5/17

Event windows and error thresholds for each 802.3ah event type are displayed. There are four event types:
Link Events - Windows
• Symbol Period
Sets the Symbol Period window size in 1 second intervals. The window specifies the number of symbols
in the defined period (time interval). For 10G, 1 sec is 1,250,000,000 symbols.
• Frame
Sets the Frame window size in 1 second intervals. The window specifies the number of frames in the
defined period (time interval).
• Frame Period
Sets the Frame Period window size in 1 seconds intervals. The window specifies the number of frames
in the defined period (time interval). For 10G, 1 sec is 14,880,000 frames.
• Frame Seconds
Sets the Frame Seconds window size in 1 second intervals. The window specifies the time interval for
counting errored frames (1-second intervals with at least one frame error).
Link Events - Threshold
• Symbol Period (error symbols per second)
Sets the threshold for the number of errored symbols for the defined Symbol Period window before a
alarm is generated.
• Frame (error frames per second)
Sets the threshold for the number of errors allowed for the defined Frame window before a alarm is
generated.
• Frame Period (error frames per x frames)
Sets the threshold for the number of errors allowed for the defined Frame Period window before a
alarm is generated.
• Frame Seconds (error seconds per x seconds)
Sets the threshold for the number of errors allowed for the defined Frame Second window before a
alarm is generated.
Link Events - Running Totals
• Symbol Period
Indicates the number of errored Symbol Period events alarms that have been generated.
• Frame Window
Indicates the number of errored Frame event alarms that have been generated.
• Frame Period
Indicates the number of errored Frame Period event alarms that have been generated.
• Frame Seconds
Indicates the number of errored Frame Seconds event alarms that have been generated.
Link Errors - Running Totals
• Symbol Period
Indicates the sum of Symbol errors that have been detected.
76.01FP33/2-A Page 60 5/17

• Frame Window
Indicates the sum of Frame errors that have been detected.
• Frame Period
Indicates the sum of Frame Period errors that have been detected.
• Frame Seconds
Indicates the sum of Frame Second errors that have been detected.
These events/errors are defined on a per port basis. A non-zero window value enables the event. All windows
entries are in seconds. Threshold values are based on the number of symbol/frame errors allowed during
the specified window period before an alarm is generated. When the threshold is exceeded, a SNMP trap
is initiated.
The conversion factor for symbols/frames depends on the speed of the port.
To change the OAM mode on Port 1, use the -m command.
7090> linkoam -m active -p 1
The 802.3ah OAM Mode sets the selected port to Passive or Active configuration mode. In Passive mode,
the port cannot initiate Discovery or initiate Loopback Mode. It can observe and report only the port status
of its 802.3ah enabled remote partner. An Active port can initiate Discovery and initiate loopback mode.
To initiate an 802.3ah loopback on Port 1, use the -ena lb command.
7090> linkoam -ena lb -p 1
The Loopback Mode enables or disables the loopback operation. When Loopback Mode is set to Disable,
the port of the 802.3ah enabled local device will not initiate Loopback operations. It can respond to loopback
commands from its 802.3ah enabled remote partner if set to Passive or Active OAM Mode. When Loopback
Mode is set to Enable, the port of the 802.3ah enabled local device will initiate Loopback operations and
set the 802.3ah enabled remote partner into loopback. In this mode, the 802.3ah enabled local device will
not respond to any other configuration changes until its port is set to Disable or the Loopback timer expires.
To change the 802.3ah loopback timeout for Port 1, use the -t command.
7090> linkoam -t 100 -p 1
The Loopback Mode Timeout field controls the length of time that the port will stay in Loopback mode
when loopback is initiated. Loopback can be set between 0 and 300 seconds. The 0 setting disables the
timer and the 7090-01 will stay in loopback until stopped by the user.
76.01FP33/2-A Page 61 5/17

5.1.15 Link Layer Discovery Protocol (LLDP)

The IEEE 802.1ab Link Layer Discovery Protocol defines a standard way for Ethernet devices to advertise
information about themselves to their neighbors and store information they discover from other device.
Each device configured with an active LLDP agent will send and receive messages on all physical interfaces
enabled for LLDP transmission.
The lldp command provides the ability to configure the LLDP agent on the 7090-01.
To configure LLDP, use the lldp option from the CLI prompt. A list of options is displayed when the lldp -h
command is entered.
7090> lldp -h
Description: Configure Link Layer Discovery Protocol (LLDP)

Format: lldp [-dall|-h|-s] [-reinit tdly] [-txfnum tnum] [-txfint tsec]
[-txhold tvalue] [-txnum tnum] [-txrate tsec] [-p portNum] [-mode
{none|rxOnly|rxTx|txOnly}] [-tlvena {mgt,pdes,sysname,sysdes,syscap}]
Switches:
-dall delete all LLDP configuration settings and restore defaults
-mode defines the lldp mode on a per port basis
[none] neither lldp transmitter or receiver is enabled
[rxOnly] lldp receiver is enabled
[rxTx] both lldp transmitter and receiver enabled, default
[txOnly] lldp transmitter is enabled
-reinit delay from port disable until reinitialization, tdly: {1...10} in sec
-s shows the lldp status
-tlvena defines optional TLVs to send: {mgt,pdes,sysname,sysdes,syscap}:
[mgt] Management address
[pdes] Port description, same as Port Name
[sysname] System name, same as sysName object
[sysdes] System description, same as sysDescr object
[syscap] System capabilities
-txfnum number of lldp messages made during fast tx, tnum: {1..8}, default 4
-txfint fast message transmission interval, tsec: {1...3600} in seconds
-txhold multiplier of txrate for TTL value in PDU: {2..10}, default 4
-txnum number of consecutive lldp PDUs, tnum: {1...10}, default 5
-txrate lldp normal message transmission interval, tsec: {5...32768} in sec
-ver verbose help
7090>
The options available using the lldp command are shown below.
The -dall switch deletes all LLDP configuration settings and restores LLDP defaults.
specific command.
The -mode switch configures the port to receive, transmit, or transmit/receive LLDP PDUs.
The -p switch associates the port with the LLDP port instance.
The -reinit switch configures the delay period from the time a port becomes disabled until it’s re-initialized.
The -s switch displays the current LLDP status.
The -tlvena switch selects which optional TLVs to be included in the transmit LLDP PDUs
Management address (mgt)
Port description, same as Port Name (pdes)
76.01FP33/2-A Page 62 5/17

System name, same as sysName object (sysname)

System description, same as sysDescr object (sysdes)
System capabilities (syscap)
The -txfnum switch configures the number of successive LLDP PDUs transmitted for one complete fast-
start interval.
The -txfint switch selects the transmission interval between fast LLDP PDUs.
The -txhold switch configures the multiplier used with the advertised interval (txrate). The result is the
Time-To-Live (TTL) value for the information that is advertised.
The -txnum switch configures the number of successive LLDP PDUs transmitted.
The -txrate switch configures the interval at which LLDP PDUs are transmitted.
Use the lldp -s command to display the LLDP status.
7090> lldp -s
Normal transmission interval: 30s

TTL value multiplier: 4
Fast LLDP transmission interval: 1s
Number of fast LLDP messages: 4
Maximum Number of LLDP messages: 5
Reinitialization delay: 2 sec
Capabilities supported: Bridge, CVLAN, SVLAN
Capabilities enabled: Bridge, CVLAN, SVLAN
Last change time: 0
Number of times table data inserted: 0
Number of times table data deleted: 0
Number of times table data dropped: 0
Number of times table data aged out: 0
Port 1 Info:
LLDP Protocol: Tunnel
Port 2 Info:
LLDP Protocol: Tunnel
7090>
NOTE: To enable LLDP Protocol, use the L2CP commands.
76.01FP33/2-A Page 63 5/17

5.1.16 IEEE 802.1ag Linktrace (LTM)

The linktrace command provides the ability to initiate and display the result of a linktrace test between two
MEPs on the same Maintenance Association and Maintenance Domain. Linktrace is used to isolate faults
within a Maintenance Domain. MEPs send Linktrace Messages (LTM) to track the path to a destination
MEP. Each Maintenance Point (MEP or MIP) along the path will respond with a Linktrace Response (LTR).
To enable linktrace testing, use the ltm option from the CLI prompt. A list of options is displayed when
the ltm -h command is entered.
7090> ltm -h
Description: CFM Linktrace operation

Format: ltm [-h [-ver]|-s] [-mac macAddr] [-m mepid] [-p portNum]
[-n domainName|-l domainLevel|-ni dindex] [-o maName|-oi mindex|
-v primaryVid|-e evcName] [-ttl ttlData] [-to timeoutVal]
Switches:
-s show the last linktrace results
-to sets the PDU [timeoutVal] in seconds: {1...10}, default 5 sec
-ttl time to live field, [ttlData]
-ver verbose help
7090>
The options available using the ltm command are shown below.
The -e switch associates the linktrace test with a specific EVC.
specific command.
The -l, -n and -ni switches indicate a specific level, domain name and index.
The -p switch associates a specific port for linktrace.
The -s switch displays the current linktrace statistics.
The -to switch sets the timeout value.
The -ttl switch sets the time to live value.
The -v switch associates a specific VID.
76.01FP33/2-A Page 64 5/17

The example below performs a linktrace test on Maintenance Domain “MD4”, Port 2, remote Maintenance
End Point 231 and VLAN ID 100.
7090> ltm -p 2 -n Domain1 -m 101 -v 1000
MD index=1 MA Index=1 MEP ID=230 Transaction id 5. TTL 64.

Linktrace sent from Chassis 1, Slot 1, Port 2 00-06-87-02-17-5a
Tracing the route to 00-06-87-01-74-ee on Domain Level 4, vlan 100
Hit any key to terminate.
Last Egress ID Ingress MAC Relay Ingress Ingress Port

Hop Next Egress ID Egress MAC Reply Egress Egress Port
================================================================================
1 00-00:00-06-87-02-17-5a --:--:--:--:--:-- RlyHit ----- ------
00-00:00-06-87-01-74-ee 00-06-87-01-74-ee Term MEP EgrOK Port 2
7090>
Definitions:
Last Egress ID
Identifies the MEP Initiator that originated, or the Responder that forwarded, the Linktrace Message.
Next Egress ID
Identifies the Responder that transmitted the Linktrace Response, and can forward the Linktrace Message
to the next hop.
Ingress MAC
MAC address of the ingress port.
Egress MAC
MAC address of the egress port.
Relay Reply
RlyHit
The Linktrace Message reached the MEP with the same MAC address or MEP ID as the configured
destination MAC or destination MEP ID.
RlyFDB
The Egress Port was determined by consulting the Filtering Database.
RlyMPDB
The Egress Port was determined by consulting the MIP CCM Database.
Forward
Indicates a Linktrace Message was forwarded by the responding maintenance point.
Term MEP
The forwarded Linktrace Message reached the terminating MEP.
Ingress/Egress
egrNoTlv
Indicates that no Reply Egress TLV was returned in the Linktrace Message.
egrOK
The message was forwarded.
76.01FP33/2-A Page 65 5/17

egrDown
The port’s operational parameters are indicating a down MEP.
egrBlocked
The Egress Port can be identified, but the data frame would not pass through the Egress Port because
the port is not in the forwarding state.
egrVid
The Egress Port can be identified, but the port is not in the member set of the Linktrace Message
VID.
ingNoTlv
Indicates that no Reply Ingress TLV was returned in the Linktrace Message.
ingOK
The message was forwarded.
ingDown
The port’s operational parameters are indicating a down MEP.
ingBlocked
The message will not be forwarded if received on this port due to active topology enforcement.
ingVid
The ingress port is not in the member set of the Linktrace Message VID.
Ingress/Egress Port:
Port number of the ingress and egress port.
76.01FP33/2-A Page 66 5/17

5.1.17 Maintenance Association (MA)

A Maintenance Association is a group of maintenance points that belong to the same administrative domain.
When a Maintenance Association is created, it is associated with a specific Maintenance Domain, VLAN
ID (EVC) and port number. Names should be descriptive and unique. Maintenance Association names
can be between 1 and 45 characters (combination of letters and numbers with no spaces).
To create a Maintenance Association for a Maintenance Domain, use the ma option from the CLI prompt.
A list of options is displayed when the ma -h command is entered.
7090> ma -h
Description: CFM maintenance association configuration

Format: ma [-a|-d|-h|-m|-s] [-ver] [-n domainName|-l domainLevel|-ni dindex]]
[-o maName|-oi mindex] [-v primaryVid|-e evcName] [-i interval]
[-c compID|-p portNum] [-to timeoutVal] [-id idSelect][-mhf mhfSelect]
[-nm maNameType] [-noccmseq] [-noporttlv] [-nostatustlv]
Switches:
-a add maintenance association
-c component id, [compID]
1 = s-component (NNI port)
2 = c-component (first UNI port)
3-n = c-component when provider edge bridge (2nd-nth UNI port if
NNI port exists)
-d delete maintenance association
-i ccm interval, [interval] value, where: 1 is 3.3ms, 2 is 10ms,
3 is 100ms, 4 (default) is 1s, 5 is 10s, 6 is 1min, 7 is 10min
-id sender ID TLV info,[idSelect]: {1 (SendIdNone), 2 (SendIdChassis),
3 (SendIdManage), 4 (SendIdChassisManage), 5 (SendIdDefer)}, default is 5
-m modify configuration of an existing maintenance association
-mhf MHF creation, [mhfSelect]: {1 (defMHFnone), 2 (defMHFdefault),
3 (defMHFexplicit), 4 (defMHFdefer)}, default is 4
-nm select [maNameType] for maintenance association name, default is 2:
{1 (primary VLAN ID), 2 (charString), 3 (UnsignedInt16), 4 (vpn ID)}
where vpn ID format: [aa:bb:cc,ddd], where aa:bb:cc is VPN OUI
and ddd is VPN index, 32 (Y1731 MEG ID format) (1-13 ASCII characters)}
-noccmseq turns off incrementing the ccm sequence count and keeps it at zero
-noporttlv turns off Port Status TLV on the CCM
-nostatustlv turns off Interface Status TLV on the CCM
if [portNum] is a NNI, then compID=1
if [portNum] is a UNI, then compID=2 for lowest numbered UNI port,
compID=3-n for (2nd-nth UNI port if NNI port exists)
-s show existing maintenance associations
-to sets the CCM [timeoutVal] in ms: {10...2100000}, default 3.5x interval,
Min value is ccm rate set by -i command; max value is 10x ccm rate
-ver verbose extended show or help
7090>
76.01FP33/2-A Page 67 5/17

The options available using the ma command are shown below.

The -a switch defines a Maintenance Association (MA).
The -c switch defines the component ID.
The component ID relates to the type of component (C-component or S-component) defined on the
7090-01. UNI ports are C-components and NNI ports are S-components. If both ports are UNI or NNI
the component ID for both ports is “1”.
The -d switch deletes a defined MA using the configured name (-o) or index number (-oi).
The -e switch associates a specific EVC to a MA.
specific command.
The -i switch defines the time interval at which CCM messages are transmitted.
The -id switch defines the Sender ID TLV type transmitted in CCM, LBM, LTM and LTR messages. The
default value is: sendIdNone (Sender ID TLV is not transmitted).
The -l switch defines the MD level.
The -m switch modifies a defined MA.
The -mhf switch indicates whether the management entity can create MHFs (MIP Half Function) on this
Maintenance Association.
The -n switch defines the name for the MD.
The -ni switch uses the defined index number as shown in the MD table as a short attribute command to
delete or modify a MD.
The -nm switch defines the format for the MA name.
The -noccmseq switch turns off incrementing the CCM sequence count and keeps it at zero.
The -noporttlv switch turns off the Port Status TLV field in the CCM PDU.
The -nostatustlv switch turns off Interface Status TLV field on the CCM PDU.
The -o switch defines the name for the MA.
The -oi switch is the defined index number as shown in the MA table as a short attribute command to delete
or modify a MA.
The -p switch associates a specific port to the MA.
The -s switch displays the configuration of the defined MAs on the 7090-01.
The -to switch defines the timeout value for CCM messages. This indicates the time period before a CCM
message is counted as lost.
The -v switch associates a specific VID to a MA.
The -ver switch displays the extended help and show.
76.01FP33/2-A Page 68 5/17

The example below creates a Maintenance Association “MA4” for the Maintenance Domain “MD4” for
EVC “Data” assigned to Port 2.
7090> ma -a -n MD4 -o MA4 -e Data -p 2
To display created Maintenance Associations, use the ma -s command.
7090> ma -s
MA MD Comp Pri MD CCM Time MHF Id Name Domain Name/

Idx Idx ID VLAN Level INTVL Out(ms) Create Perm Type MA Name/Evc Name
================================================================================
1 1 1 100 4 1sec 3500 Defr Defr 2 MD4/MA4/Data
7090>
The example below modifies the name of Maintenance Association “MA4” to “MA04”. The command ni
relates to the MD Index and command oi relates to the MA Index number displayed in the Maintenance
Association list (ma -s).
7090> ma -m -ni 1 -oi 1 -o MA04

7090> ma -s

================================================================================
1 1 1 100 4 1sec 3500 Defr Defr 2 MD4/MA04/Data
7090>
To delete a Maintenance Association, use the ma -d command.
7090> ma -d -ni 1 -oi 1

7090> ma -s

================================================================================
7090>
76.01FP33/2-A Page 69 5/17

5.1.18 Maintenance Domain (MD)

A Maintenance Domain is an administrative domain for the purpose of managing and administering
a network. A domain is assigned a unique maintenance level (0 - 7) by the administrator, defining the
hierarchical relationship of domains. Maintenance domains may nest or touch, but cannot overlap. If two
domains nest, the outer domain must have a higher maintenance level than the inner domain. The figure
below illustrates nested domains, where the Operator and Provider Domains are nested under the Customer
Domain. The Customer Domain would have the highest maintenance level.
To configure the Maintenance Domain, a MD name and level must be defined. Names should be descriptive
and unique. Maintenance Domain names can be between 1 and 43 characters (a combination of letters and
numbers with no spaces). When more then one Maintenance Domain is created, the outer domain must
have the higher maintenance level.
Metro Ethernet Forum specifications 17 and 30.1 define the suggested type and level for each domain.
Domain Suggested Usage
Subscriber Subscriber monitoring of an Ethernet Service
Test Service Provider isolation of subscriber reported problem
EVC Service Provider monitoring of provided service
Service Provider Service Provider Monitoring of Service Provider network
Operator Operator monitoring of the portion of a network
UNI Service Provider monitoring of a UNI
ENNI Network Operators’ monitoring of an ENNI
Domain Default Level

Subscriber 6
Test 5
EVC 4
Service Provider 3
Operator 2
UNI 1
ENNI 1
76.01FP33/2-A Page 70 5/17

To create a Maintenance Domain, use the md option from the CLI prompt. A list of options is displayed
when the md -h command is entered.
7090> md -h
Description: CFM maintenance domain configuration

Format: md [-a|-d|-dall|-h [-ver]|-m|-s] [-n domainName|-ni dindex]
[-l domainLevel] [-id idSelect] [-mhf mhfSelect][-nd mdNameType]
Switches:
-a add maintenance domain
-d delete maintenance domain
-dall deletes all maintenance domains and restore mde defaults
3 (SendIdManage), 4 (SendIdChassisManage)}, default 1
-m modify configuration of an existing domain
3 (defMHFexplicit), default is 1
-nd select [mdNameType] for domain name, default is 4:
{1 (none), 2 (dnsLikeName), 3 (macAddrAndUint), 4 (charString)}
Where macAddrAndUint format: [xx-xx-xx-xx-xx-xx,ggg] where the MAC
Address is xx-xx-xx-xx-xx-xx and ggg is a two octet decimal integer
-s show existing maintenance domains
-ver verbose help
7090>
The options available using the md command are shown below.

The -a switch defines a Maintenance Domain (MD).
The -d switch deletes a defined MD using the configured name (-n) or index number (-ni).
The -dall switch deletes all configured maintenance domains.
specific command.
The -id switch defines the Sender ID TLV type transmitted in CCMs, LBMs, LTMs and LTRs messages.
The default value is: sendIdNone (Sender ID TLV is not transmitted).
The -l switch defines the maintenance level associated with the domain.
The -m switch modifies a defined MD.
The -mhf switch indicates whether the management entity can create MHFs (MIP Half Function) on this
Maintenance Domain.
The -n switch defines the name for the MD.
The -nd switch defines the format for the MD name.
The -ni switch uses the defined index number as shown in the MD table as a short attribute command to
delete or modify a MD.
The -s switch displays the configuration of the defined MDs on the 7090-01.
The -ver switch displays extended help.
76.01FP33/2-A Page 71 5/17

The example below creates a Maintenance Domain called “MD4” with a maintenance level of 4.
7090> md -a -n MD4 -l 4
To display created Maintenance Domains, use the md -s command.
7090> md -s
Domain Domain Service Name MHF Id Domain

Index Level (MA Idx) Type Create Perm Name
================================================================================
1 4 1 4 None None MD4
7090>
The example below modifies the name of Maintenance Domain “MD4” to “MD04”. The command ni
relates to the Domain Index number displayed in the Maintenance Domain list (md -s).
7090> md -m -ni 1 -n MD04

7090> md -s

================================================================================
1 4 1 4 None None MD04
7090>
To delete a Maintenance Domain, use the md -d command.
7090> md -d -ni 1
7090> md -s

================================================================================
7090>
76.01FP33/2-A Page 72 5/17

5.1.19 Default Maintenance Domain (MDE)

The mde command provides the ability to configure and display MIP Half Function (MHF) on a Maintenance
Domain and EVC. Default Maintenance Domain provides the ability to create MIPs on MAs or EVCs on
ports that are not configured.
To configure the MIP Half Function (MHF) on a single Maintenance Domain and EVC, use the mde
command from the CLI prompt. A list of options is displayed when the mde -h command is entered.
7090> mde -h
Description: CFM Default Maintenance Domain configuration

Format: mde [-a|-h [-ver]|-s] [-p portNum|-c compID] [-v primaryVid|-e evcName]
[-l domainLevel] [-mhf mhfSelect] [-id idSelect]
Switches:
-a modify existing default setup
-c component id, [compID]
1 = s-component (NNI port)
2 = c-component (first UNI port)
3-n = c-component when provider edge bridge (2nd-nth UNI port if
NNI port exists)
3 (SendIdManage), 4 (SendIdChassisManage), 5 (SendIdDefer)}, default 5
-l maintenance [domainLevel]: {0...7}, default 0
3 (defMHFexplicit), 4 (defMHFdefer)}, default 4
-p [portNum] selected: {1,2}
-s show the current default MD settings
-ver verbose help
7090>
The options available using the mde command are shown below.
The -a switch modifies an existing default setup.
The -c switch defines the component ID.
The component ID relates to the type of component (C-component or S-component) defined on the
module. UNI ports are C-components and NNI ports are S-components. If both ports are UNI or NNI
the component ID for all ports is “1”.
The -e switch associates a specific EVC.
specific command.
The -id switch determines the Sender ID TLV type transmitted in CCM, LBM, LTM and LTR messages.
The default value is: sendIdNone (Sender ID TLV is not transmitted).
The -l switch defines the MD level.
The -mhf switch indicates whether the management entity can create MHFs (MIP Half Function).
The -p switch associates a specific port.
The -s switch displays the current VLAN ID table.
The -v switch associates a specific VID to a MA.
76.01FP33/2-A Page 73 5/17

MIP Half Function (MHF) is a CFM entity, associated with a single Maintenance Domain, and a single
MD Level and a set of VIDs, that can generate CFM PDUs in response to received CFM PDUs.
To display the default maintenance domain, use the mde -s command from the CLI prompt.
7090> mde -s
Default domain level = 0

Default MHF creation = defMHFnone(1)
Default Sender ID TLV info = SendIdNone(1)
VLAN MD MHF Sender ID

ID Cid Status Level Ability TLV Info Evc
===============================================================================
0 1 Active -1 Defr(4) Defr(5) mgt
100 1 Active -1 Defr(4) Defr(5) Data
7090>
76.01FP33/2-A Page 74 5/17

5.1.20 Maintenance Points

Maintenance points can be configured on any port on the network. Depending on the location of the port,
the maintenance point will be classified as a Maintenance End Point (MEP) or Maintenance Intermediate
Point (MIP).
5.1.20.1 Maintenance End Point (MEP)
Maintenance End Points are located at the edge of the Maintenance Domain and generate and terminate
CFM packets. Maintenance End Points are associated with a specific Maintenance Domain, Maintenance
Association, VLAN ID (EVC) and port number. Identifiers should be descriptive and unique. Maintenance
End Point identifiers can be between 1 and 45 characters (combination of letters and numbers with no spaces).
To create a Maintenance End Point, use the mep option from the CLI prompt. A list of options is displayed
when the mep -h command is entered.
7090> mep -h
Description: CFM maintenance end point configuration

Format: mep [-a|-c|-d|-h|-s|[-ena|-dis {ccm | mepactive}]]
[-n domainName|-l domainLevel|-ni dindex] [-o maName|-oi mindex]
[-m mepid] [-p portNum] [-v primaryVid|-e evcName] [-up|-dn] [-scomp]
[-pri pbits] [-pr pval] [-alarmon time] [-alarmoff time] [-ver]
[-ctagvid cvid]
Switches:
-a add maintenance end point
-alarmoff [time] defect absent before resetting alarm: {250...1000} in 0.01s
-alarmon [time] defect present before fault alarm: {250...1000} in 0.01s
-c change (modify) config of an existing maintenance association end point
-ctagvid C-TAG VID associated with the PDUs for the MEP that
originates on an NNI port
-d delete maintenance end point
-dis disable MEP option: {ccm|mepactive}
[ccm] disable ccm function
[mepactive] disable mep function
-dn mep down direction (towards the LAN entity)
-ena enable MEP option: {ccm|mepactive}; default is enabled for both
[ccm] enable ccm function
[mepactive] enable mep function
-m mep ID, [mepid], unique within a MA: {1...8191}
-pr lowest priority to trigger Fault Alarm [pval]: {1...6}, default 2
-s show existing maintenance end points
-scomp places a mep on a UNI port to be a part of the S-component
-up mep up direction (facing towards the relay entity)(default)
-ver extended show or help
7090>
76.01FP33/2-A Page 75 5/17

The options available using the mep command are shown below.
The -a switch adds a MEP to a defined MD/MA.
The -alarmoff switch defines the amount of time in 1/100 of a second that fault alarm is removed after
correction of the defect.
The -alarmon switch defines the amount of time in 1/100 of a second that a defect must be present before
it is generates a fault alarm.
The -c switch modifies a defined MEP.
The -ctagvid switch associates a C-Tag VID to the OAM PDUs on a NNI port or a scomp UNI.
The -d switch deletes a defined MEP on a MD/MA.
The -dis and -ena switches disable or enable specific functions of a MEP: CCM and MEP active.
The -dn switch defines the MEP as a down MEP.
The -e switch associates a specific EVC to a MEP.
specific command.
The -l, -n, and -ni switches indicate a specific level, domain name and index for the MEP.
The -m switch defines MEP ID for the selected MD/MA.
The -o and -oi switches indicate a specific maintenance association of the MEP.
The -p switch associates a specific port to a MEP.
The -pr switch defines the lowest defect that will trigger a fault alarm. The following fault alarms are set
as the default value: DefMACstatus, DefRemoteCCM, DefErrorCCM and DefXconCCM.
-pr value Defects Reported
All defects
1
DefRDICCM, DefMACstatus, DefRemoteCCM, DefErrorCCM, andDefXconCCM
2 (default) DefMACstatus, DefRemoteCCM, DefErrorCCM, and DefXconCCM
3 DefRemoteCCM, DefErrorCCM, and DefXconCCM
4 DefErrorCCM, and DefXconCCM
5 DefXconCCM
6 None
DefRDICCM
A remote MEP is reported the RDI bit in its last CCM.
DefMACstatus
A remote MEP is reporting its Port Status as not up (linkup).
DefRemoteCCM
The MEP is not receiving valid CCMs from at least one of the remote MEPs.
DefErrorCCM
The MEP has received at least one invalid CCM whose CCM Interval has not yet timed out.
DefXconCCM
The MEP has received at least one CCM from either another MAID or a lower MD Level whose CCM
Interval has not yet timed out.
The mep -s -ver command will display the fault alarm value.
The -pri switch indicates the specific VLAN priority bits for the MEP.
The -s switch the displays the configured MEPs and the running status.
76.01FP33/2-A Page 76 5/17

The -scomp switch associates a MEP on a UNI port to a S-TAG.

The -up switch defines a MEP as a up MEP.
The -v switch associates a specific VLAN ID with a MEP.
The -ver switch displays extended help or show status.
The example below creates Maintenance End Point 230 associated with Maintenance Association “MA4”
and Maintenance Domain “MD4”.
7090> mep -a -n MD4 -o MA4 -e Data -p 2 -m 230
To display created Maintenance End Points, use the mep -s command.
7090> mep -s
MEP MD P Prim CCM MEP MAC Domain Name/

ID Lvl # VLAN Status Status Int Dir Address MA Name/Evc Name
===================================================================================
230 4 2 100 enabled active 1sec Up 00-06-87-02-17-5a MD4/MA4/Data
7090>
To obtain more information on configured Maintenance End Points and default values, use the mep -s -ver
command.
7090> mep -s -ver
MEP MD P Prim CCM MEP MAC Domain Name/

ID Lvl # VLAN Status Status Int Dir Address MA Name/Evc Name
===================================================================================
230 4 2 100 enabled active 1sec Up 00-06-87-02-17-5a MD4/MA4/Data
pri=0, alarmon=250, alarmoff=1000, pr=Def_MAC_REM_ERR_XCON(2)

defect state=Defect Reported Highest Pri Defect=RemoteCCM(3) Defects=Rem
CCM Tx=2336 CCM Sequence Err=0; RDI Tx; Probe responder=EVC, v2
7090>
To delete a Maintenance End Point, use the mep -d command.
7090> mep -d -n MD4 -o MA4 -m 230
76.01FP33/2-A Page 77 5/17

5.1.20.2 Maintenance Intermediate Point (MIP)

Maintenance Intermediate Points are internal to the Maintenance Domain. Maintenance Intermediate
Points will forward CFM packets.
To create a Maintenance Intermediate Point for a Maintenance Domain, use the mip option from the CLI
prompt. A list of options is displayed when the mip -h command is entered.
7090> mip -h
Description: CFM maintenance intermediate point configuration

Format: mip [-a|-d|-h [-ver]|-s] [-n domainName|-l domainLevel|-ni dindex]
[-o maName|-oi mindex] [-p portNum] [-scomp]
Switches:
-a add explicit maintenance intermediate point
-d delete explicit maintenance intermediate point
-s show existing maintenance intermediate points
-scomp places a mip on a UNI port to be a part of the S-component
-ver verbose help
7090>
The options available using the mip command are shown below.
The -a switch adds a MIP to a defined MD/MA.
The -d switch deletes a defined MIP on a MD/MA.
specific command.
The -l, -n, and -ni switches indicate a specific level, domain name and index for the MIP.
The -o and -oi switches indicate a specific maintenance association of the MIP.
The -p switch associates a specific port to a MIP.
The -s switch the displays the configured MIPs.
The -scomp switch associates a MIP on a UNI port to a S-TAG.
76.01FP33/2-A Page 78 5/17

There are several ways to create a MIP. The following are the valid combinations of the MIP Half Function
(MHF) Creation:
Dflt(I)
Implicit creation of a MIP on an existing MA when MA’s MHF Creation = defMHFdefault
or MA MHF Creation = defMHFdefer and MD MHF Create = defMHFdefault.
Expl(I)
Implicit creation of a MIP on an existing MA when MA MHF Creation = defMHFexplicit
or MA MHF Creation = defMHFdefer and MD MHF Creation = defMHFexplicit.
Dflt(D)
Implicit creation of a MIP via default MD table when default MD table MHF Creation = defMHFdefault.
Expl(D)
Implicit creation of a MIP via default MD table when default MD table MHF Creation = defMHFexplicit.
Dflt(E)
Explicit creation of a MIP on an MA by user.
Dflt(IE)
Implicit creation of a MIP on an existing MA when MA MHF Creation = defMHFdefault and explicit
creation of a MIP on an MA by user.
Expl(IE)
Implicit creation of a MIP on an existing MA when MA MHF Creation = defMHFexplicit and explicit
creation of a MIP on an MA by user.
MIP Half Function (MHF) is a CFM entity, associated with a single Maintenance Domain, and a single
MD Level and a set of VIDs, that can generate CFM PDUs in response to received CFM PDUs.
The example below creates a Maintenance Intermediate Point associated with Maintenance Association
“MA4” and Maintenance Domain “MD4”.
7090> mip -a -p 1 -n MD4 -l 7 -o MA4
To display created Maintenance Intermediate Points, use the mip -s command.
7090> mip –s
MD MA MIP MD Prim MHF Domain Name/

Idx Idx Idx Lvl Port Vlan Create MA Name/Evc Name
=========================================================================
1 2 1 4 1 1000 Dflt MD4/MA4/Data
7090>
76.01FP33/2-A Page 79 5/17

5.1.21 Global Settings (MODULE)

The module command provides the ability to configure and display specific 7090-01 settings. The chassis
number and name, 7090-01 identifier and system location can be configured using the module command.
7090-01 specific parameters can also be displayed using the module command.
To configure the global setting, use the module command from the CLI prompt. A list of options is displayed
when the module -h command is entered.
7090> module -h
Description: Displays module global information

Format: module [-dall|-h [-ver]] [-s showType] [-con sysContact]
[-loc sysLoc] [-id modId] [-nm chassisName] [-cn chassiNumber]
Switches:
-cn set chassis number: {1...19}, default 1
-con sets system contact [sysContact], 1-64 ASCII characters
-dall restore factory defaults
-id sets module identification, 1-64 ASCII characters
-loc set system location [sysLoc], 1-64 ASCII characters
-nm sets chassis name,[chassisName], 1-64 ASCII characters
-s shows the module global information [showType]: {env|mfg|mod|}
-ver verbose help
7090>
The options available using the module command are shown below.
The -cn switch configures the chassis number. The default chassis number is 1.
The -con switch configures the system contact. The system contact name can be any 1-32 alphanumeric
character string.
The -dall switch restores the factory defaults of all global setting.
specific command.
The -id switch configures the 7090-01 identifier. The 7090-01 identifier can be any 1-32 alphanumeric
character string.
The -loc switch configures the system location. The system location name can be any 1-32 alphanumeric
character string.
The -nm switch configures the chassis name. The chassis name can be any 1-32 alphanumeric character
string.
The -s switch displays the 7090-01 global configuration. Specific parameter can be displayed using the
led, env, mfg or mod command.
env displays the voltage and temperature parameters.
mfg displays the manufacturing information.
mod displays the 7090-01 specific information.
76.01FP33/2-A Page 80 5/17

To configure the system contact and location, use the following commands.
7090> module -con JSmith -loc Dallas

7090> module -s mod
Module Type: 7090-01 CE (817301A)

Module Identification:
SysContact: JSmith
SystemLoc: Dallas
Chassis Name: 7090-01 CE
Chassis Number: 1
Slot Number: 1
7090>
To display the manufacturing information, use the module -s mfg command.
7090> module -s mfg
Model Number = 81.73S-7301A-R6

Serial Number = 00713570
Manufacturing Date = 20160401
Product Revision = 10
Software Revision = x.x.x
7090>
To display the environmental information, use the module -s env command.
7090> module -s env
Voltage: 3.3V
Temperature: 42.6C
CPU Utilization: 29%
RAM Utilization: 26.7MB out of 128MB (19.9%)
Flash Utilization: 17.2MB out of 32MB (51.2%)
7090>
76.01FP33/2-A Page 81 5/17

5.1.22 Ping (PING)

The ping command provides the ability to ping network devices connected to the 7090-01. This provides
a convenient way to verify connectivity through the CLI interface.
To configure ping, use the ping command from the CLI prompt. A list of options is displayed when the
ping -h command is entered.
7090> ping -h
Description: Generates a ping to a remote device

Format: ping [-t ipaddress] [-h [-ver]] [-n count] [-l size]
Switches:
-l send buffer [size], default is 32 bytes, maximum is 1472 bytes
-n number of ping requests [count] to send: {0..65536}, default is 3
-t ping the specified [ipaddress]
-ver verbose help
7090>
The options available using the ping command are shown below.
specific command.
The -l switch defines the size of the ping frame.
The -n switch defines the number of pings frames sent. A value of 0 sends pings until interrupted.
The -t switch defines the destination IP address.
To ping an IP address, use the ping -t command.
7090> ping -t 10.0.0.100 -l 256
Pinging 192.168.1.221 with 256 bytes of data sourced from IP1 (10.0.0.1):
Reply from 10.0.0.100: bytes=256 time=1ms

Ping statistics for 10.0.0.100:

Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1
7090>
The command pings IP address 10.0.0.100 (-t) using a frame size of 256 bytes (-l).
76.01FP33/2-A Page 82 5/17

5.1.23 Port Attributes (PORT)

The port command provides the ability to configure each port with specific parameters.
To configure the attributes of a port, use the port command from the CLI prompt. A list of options is
displayed when the port -h command is entered.
7090> port -h
Description: Changes port attribute configuration

Format: port [-h|-s] [-ver] [-p port] [-n portName]
[-looptimeout time] [{-dis|-ena} {loop|port}] [-tv tvval]
Switches:
-dis disable function: {loop|port}
-ena enable function: {loop|port}
[loop] local loopback for the selected port, default disable
[port] port output, default enable
-looptimeout loopback timeout [time]: {1...3600}, default 30 seconds
-n defines the [portName] identifier, 1-45 ASCII characters
-s shows the port attribute configuration
-tv defines utilization threshold violation percentage value [tvval]:
{0.000...100.000}, default 100.000
-ver extended help
7090>
The options available using the port command are shown below.
The -dis and -ena switches disable or enable the configuration of specific attributes on each port. These
include port output and local loopback.
specific command.
The -looptimeout switch configures the amount of time the port will stay in loopback when loopback is
enabled on a port.
The -n switch defines the name for the selected port.
The -p switch defines the port on the 7090-01 to be used when configuring the attributes.
The -s switch displays the attributes associated with each port on the 7090-01.
The -tv switch configures the port utilization threshold violation value. When the value is violated, an
SNMP trap is generated.
The example below disables Port 1.
7090> port -p 1 -dis port
To set Port 1 into local loopback, use the -ena loop command.
7090> port -p 1 -ena loop
76.01FP33/2-A Page 83 5/17

The example below configures the ports with a name or an identifier.
7090> port -p 1 -n Port1

7090> port -p 2 -n Port2
To display the port attributes, use the port -s command.
7090> port -s
Port 1 is named “Port 1” is type UNI [MAC 00-06-87-02-35-49]

Port is Fiber 1000, AN, FDX (No link)
Laser output is enabled
Port loopback is disabled, port loopback timeout is 30 seconds
Threshold violation: Not configured (100.000%)
Port 2 is named “Port 2” is type UNI [MAC 00-06-87-02-35-4a]
Port is UTP 1000, AN, FDX (Linked: 1000,FDX)
Port loopback is disabled, port loopback timeout is 30 seconds
Threshold violation: Not configured (100.000%)
Management port 1 is named “Mgt1” is type UNI [MAC 00-06-87-02-35-48]
7090>
5.1.24 Port Statistics (PORTSTAT)

The portstat command provides the ability to display the port statistics on the 7090-01.
To display the port statistics, use the portstat command from the CLI prompt. A list of options is displayed
when the portstat -h command is entered.
7090> portstat -h
Description: Displays and clears the port statistic counters

Format: portstat [-h [-ver]|-s] [-p portNum] [-clr]
Switches:
-clr clear current port statistics
-p [portNum] selected: {1|2|mgt1}
-s shows the port statistics
-ver verbose help
7090>
The options available using the portstat command are shown below.
The -clr switch clears the current port statistics.
specific command.
The -p switch selects which port statistic will be displayed.
The -s switch displays the selected port statistics.
76.01FP33/2-A Page 84 5/17

To display the port statistics for Port 1, use the portstat -s -p 1 command.
7090> portstat -s -p 1
Transmission Counters Receive Counters Receive Packets by Size

Packets 42551 64 Octets 19286
Total Octets 11823742 Total Octets 9564366 65-127 7707
Good Pkts 40761 Good Pkts 42551 128-255 1788
Pause Pkts 0 Pause Pkts 0 256-511 6119
Unicast Pkts 40761 Unicast Pkts 2 512-1023 6121
Multicast Pkts 39775 Multicast Pkts 42549 1024-10240 1530
Broadcast Pkts 985 Broadcast Pkts 0
Errored Pkts 0 Errored Pkts 0
Dropped Pkts 0 Dropped Pkts 0
Bad Events 0 FCS Errors 0
Deferred 0 Symbol Errors 0
Collisions: CRC/Alignment 0
Total 0 Undersized 0
Single 0 Oversized 0
Multiple 0 Fragments 0
Late 0 Jabber 0
Excessive 0 Alignment 0
Tx Throughput 0.000 Mbps Rx Throughput 0.003 Mbps

Tx Utilization 0.000% Rx Utilization 0.000%
7090>
76.01FP33/2-A Page 85 5/17

5.1.25 ITU-T Y.1731 Performance Monitoring

ITU-T Y.1731 Performance Monitoring tools provide statistics for delay, delay variation, loss and availability
between MEPs. There are three types of measurements that can be created between MEPs. Y.1731 uses
OAM PDUs to send/receive messages to measure the different performance parameters. When created,
the OAM PDUs run continuously until disabled. Each performance measurement uses different OAM
PDUs messages.
Y.1731 utilizes the same configuration parameters used by 802.1ag Connectivity Fault Management, defining
Maintenance Domains, Maintenance Associations and Maintenance Points.
5.1.25.1 Probe (PROBE)
There are three performance measurement types available:
Type 1: 2-way delay/variation (DMM/DMR)
Type 2: 1-way delay variation (1DM)
Type 3: Single ended loss/availability (LMM/LMR)
Before a probe can be configured, global parameters must be defined. The global parameters include
bucket size and bins.
Performance monitoring data is collected during a predetermined time frame. The time frame is referred to
as the measurement interval or bucket size. During the measurement interval, the performance monitoring
data is grouped into bins inside each bucket. The default bucket size is 15 minutes. A bin counts the number
of data samples falling within the limits of the bin. Each bin has a minimum and a maximum value. If
one of the bins has a minimum value of 1ms and a maximum value of 2ms, then all the data that is greater
than or equal to 1ms, but less than 2ms is stored in that bin. The default bin times are: 5 (0 to 5msec), 10
(5 to 10msec) and greater than 10ms.
Y.1731 must be globally enabled on the initiator and responder for a performance measurement to run.
Use the probe -ena command to enable Y.1731 performance monitoring.
The probe command provides the ability to configure and display the three types of Y.1731 probes on the
7090-01. Probes are used to provide performance monitoring data to help validate Service Level Agreements.
value when configuring a probe.
76.01FP33/2-A Page 86 5/17

To configure performance monitoring, use the probe option from the CLI prompt. A list of options is
displayed when the probe -h command is entered.
7090> probe -h
Description: Performance Metric Probe Configuration

Format: probe [-a|-clear|-d|-dall|-dis|-ena|-g|-h|-resp|-s] [-p portNum]
[-ty probeType] [-n domainName | -l domainLevel | -ni dindex]
[-o maName | -oi mindex] [-v primaryVid | -e evcName] [-mac macAddr |
-m mepid] [-pri pbits] [-i probeInterval] [-fr flvalue]
[-sz size | -fsz frameSize] [-bt bucketTime] [-bin bval1,...,bvaln]
[-bu] [-cpp|-cpe|-cpo|-cph] [-pi pindex|all]
[-rt] [-tx] [-rx] [-vbin bval1,bval2,...,bvaln] [-ver] [-pn pName]
[-nosync] [-du dselect] [-fd ftime] [-fdv ftime]
[-dat {ones|zeros}] [-avail aavail] [-v1|-v2]
Switches:
-a add performance metric probe
-avail acceptable availability percent, [aavail]: {0.0...100.0}, default 50.0
-bin delay bin sizes in ms, 1-15 values
-bt bucket size, [bucketTime], in minutes: {1...60}
-bu bucket show results
-clear clears specific probe history data
-cpe enables probe on a per EVC basis
-cph enables probe on a per hopping priority basis
-cpo disables responder
-cpp enables probe on a per fixed priority basis
-d delete performance metric probe
-dall delete all probe instances
-dat selects data payload value: {ones|zeros}
[ones] selects a payload that is filled with ones
[zeros] selects a payload that is filled with zeros, default
-dis disable Y.1731 compatibility mode
-du configures delay units, [dselect]: {ms|us|ns}, default ms
-ena enable Y.1731 compatibility mode
-fd acceptable frame delay, [ftime]: {1...10000} ms, default 1000
-fdv acceptable frame delay variation, [ftime]: {1...10000} ms, default 1000
-fr acceptable frame loss percentage, for a time period to be listed as
Available, 0.1% resolution; default is 500 (50.0%)
-fsz specifies Ethernet [frameSize], uses data TLV to adjust length
-g probe metric global setup
-i [probeInterval] value: {3 is 100ms, 4 (default) is 1s, 5 is 10s,
6 is 1min, 7 is 10min}
-nosync disables using peer partner time of day (master clock)
-pi probe index value
-pn defines probe name [pName], 1-45 ASCII characters, default blank
-resp probe responder setup
-rt realtime show results
-rx enable receive for the 1DM (1 way delay/variation)
-s show performance metric probe results
-sz TLV packet [size]; filled with testData or random if not defined
76.01FP33/2-A Page 87 5/17

-ty [probeType]: {1|2|3}

1 = 2-way delay/variation (DMM/DMR)
2 = 1-way delay/variation (1DM)
3 = single-ended loss/availability (LMM/LMR)
-tx enables transmit for the 1DM (1 way delay/variation)
-vbin delay variation bin sizes in ms, 1-15 values
-v1 enable Y.1731 v1 LMM/CCM counting
-v2 enable Y.1731 v2 LMM/CCM counting, default
7090>
The options available using the probe command are shown below.
The -a switch adds a probe.
The -avail switch configures the acceptable available in % allowed before a SNMP trap is generated. 50%
is the default value. Valid for type 3 (LMM/LMR) probe only.
The -bin switch defines the sizes of the bin.
The -bt switch defines the size of the bucket.
The -bu switch displays the bucket results when used with the -s switch.
The -clear switch clears the history data for a specific probe.
The -cpe, -cph, and -cpp switches define the type of frames counted during the probe measurement interval.
-cpe counts frames per EVC. -cph counts frames on a hopping priority. -cpp counts frames with a fixed
priority.
The -cpo switch disables the responder 7090-01 from counting frames.
The -d switch deletes a specific probe.
The -dall switch deletes all probe instances.
The -dat switch configure the value of payload data used by the probe (all ones or all zeros).
The -dis switch globally disables Y.1731.
The -du switch configures the delay units for the test results metrics.
The -e switch associates a EVC with a probe.
The -ena switch globally enables Y.1731.
The -fd switch configures the maximum frame delay allowed before a SNMP trap is generated. 1000msec
is the default value. Valid for type 1 (DMM/DMR) probes only.
The -fdv switch configures the maximum frame delay variation allowed before a SNMP trap is generated.
1000msec is the default value. Valid for type 1 (DMM/DMR) probes only.
The -fr switch defines the acceptable frame loss percentage. An SNMP trap will be generated if the measured
frame loss percentage is greater than the acceptable frame loss percentage. The -fr switch is not valid for
type 1 (DMM/DMR) probes.
The -fsz switch defines the frame size used in the performance testing.
The -g switch is used to setup the bins and bucket times.
specific command.
The -i switch configure the time interval between probe OAM PDUs. Valid options are 100ms, 1 sec, 10
sec, 1 min and 10 min. The default value is 1 sec.
76.01FP33/2-A Page 88 5/17

The -l, -n, and -ni switches indicate a specific level, domain name and index.
The -nosync switch disables the use of the peer partner’s time of day indicator.
The -p switch associates a specific port to a probe.
The -pi switch using the defined index number as shown in the probe table as a short attribute command
to delete a probe.
The -pn switch defines the name of the probe.
The -pri switch defines the VLAN priority bits for the probe PDU.
The -resp switch configures the responder 7090-01 for fixed priority and priority hooping configurations.
The -rt switch displays the real time results when used with the -s switch.
The -rx switch enables the port to receive 1 way delay/variation probe PDU.
The -s switch displays the probe results.
The -sz switch defines the frame size of the probe PDU.
The -ty switch defines the probe type. Three probe types are available: DMM/DMR, 1DM or LMM/LMR.
The -tx switch enables the port to transmit 1 way delay/variation probe PDU.
The -v switch associates a specific VID to the probe setup.
The -vbin switch defines the delay variation of the bin sizes.
The -ver switch displays extended help or show results.
The -v1 switch configures Y.1731 LMM/LMR v1 counting (CCM not counted at same MD level).
For LMM/LMR probe type all OAM frames higher than the MEP’s domain level are counted with the
Service Frames.
OAM frames transmitted at the MEP’s domain level or lower are NOT counted.
The -v2 switch configures Y.1731 LMM/LMR v2 counting (CCM counted at same MD level).
For LMM/LMR probe, all OAM frames higher than the MEP’s domain level are counted with the
Service Frames.
For LMM/LMR probe, all OAM frames lower than the MEP’s domain level are NOT counted.
For LMM/LMR probe, OAM frames at the MEP’s same domain level of type CCM, APS, and CSF are
counted.
For LMM/LMR probe, OAM frames at the MEP’s same domain level of type LBM/LBR and LTM/
LTR frames are NOT counted.
76.01FP33/2-A Page 89 5/17

Probes can be configured on an EVC (-cpe), priority hopping (-cph) or fixed priority (-cpp) basis. EVC
base priority is the default setting.
When configured for EVC (-cpe), loss measurement probes count all the frames in the configured EVC.
When configured for priority hopping (-cph), loss measurement probes count frames based on a priority
hopping algorithm. The initiator 7090-01 will be configured for priority hopping with a defined pbit priority
and the responder 7090-01 will be configured for priority hopping with no pbit priority defined.
For example, if the incoming priority of the LMM probe is 1 and there is no corresponding probe responder
of any priority, a new probe responder “session” is created and starts the frame count on priority 1. If the
incoming LMM priority changes to 2, the session is “hopped” to start the frame count on priority 2.
When LMM with a new priority is received, it is considered as a “counter reset” and a new session is
created and all counters are reset.
When configured for fixed priority (-cpp), the loss measurement probes count all frames with the configured
priority. The initiator will be configured for fixed priority with a defined pbit priority and the responder
will be configured for fixed priority with the same defined pbit priority. Both the initiator and responder
must be configured using the -cpp command.
When the -cpo command is used, the framing counting algorithms are disabled and no replies are generated
by the responder.
The example below configures a bucket time of 5 minutes with four bins.
7090> probe -g -bt 5 -bin 1,2,5,10
Each bin has the following range: 1 (0 to 1msec), 2 (1 to 2msec), 5 (2 to 5msec), 10 (5 to 10msec) and
greater than 10msec.
A maximum of sixteen bins can be defined.
To display the global settings, use the probe -s command.
7090> probe -s
Probes disabled
No probes defined
7090>
NOTE: Probes can be created before Y.1731 has been globally enabled on the 7090-01. If a probe
is created before Y.1731 is enabled, the probe will not run. Use the probe -ena command to enable
Y.1731 on the 7090-01.
76.01FP33/2-A Page 90 5/17

The example below configures a Type 3 probe to count frames on a EVC basis on Port 2, Maintenance
Domain “MD4”, Maintenance Association “MA4” and remote Maintenance End Point 231.
7090> probe -a -p 2 -ty 3 -n MD4 -o MA4 -m 231 -cpe
The example below configures a Type 3 probe on Port 2 with a Maintenance Domain Level 2, VLAN ID
100, pbit priority 3, for remote Maintenance End Point 100.
7090> probe -a -p 2 -ty 3 -l 2 -v 100 -pri 3 -m 100 -cpp
To change the pbit priority of a created probe, the probe must be deleted and recreated with the new value.
Use the probe -d command to delete the probe.
For fixed priority configurations, the remote (responding) 7090-01 must be configured. Use the -cpp
command to configure the remote 7090-01.
7090> probe -resp -p 2 -ty 3 -l 2 -cpp
For priority hopping configurations, the remote (responding) 7090-01 must be configured. Use the -cph
command to configure the remote 7090-01.
7090> probe -resp -p 2 -ty 3 -l 2 -cph
Once a probe has been created, the probe will continue to run until it is deleted. Use the probe -d command
to delete a probe.
7090> probe -d -pi 1
When probes are created, they are given a probe number. The probe number is displayed when the probe -s
command is entered. -pi 1 command indicates probe #1 will be deleted.
To enable 1731 testing, use the probe -ena command.
7090> probe -ena
The configuration used for the examples in this section is shown below. The configuration assumes a
factory default 7090-01.
76.01FP33/2-A Page 91 5/17

7090-01 #1
CLI Command
> evc -dis
> evc -dall
> cfm -dis all
> evc -a -e Data -p 1,2 -v 1000
> evc -a -e mgt -p 1,2,mgt1 -v 2000
> interface -a -p 1 -t uni -e Data:100 -e mgt:*
> interface -a -p mgt1 -t uni -e mgt:*
> evc -ena
> md -a -n MD4 -l 4
> cfm -ena all
> probe -g -bt 1 -bin 1,2,5,10 -du us
> probe -ena
> probe -a -p 2 -ty 2 -n MD4 -o MA4 -m 231 -rx
Packet Transport Platform

CLI Command
> evc -dis
> evc -dall
> cfm -dis all
> evc -a -e Data -p 1,2,7 -v 1000
> evc -a -e mgt -p 1,2,7,mgt1 -v 2000
> interface -a -p 1,2 -t nni
> evc -ena
> md -a -n MD4 -l 4
> mep -a -n MD4 -o MA4 -e Data -p 7 -m 231 -dn
> cfm -ena all
> probe -g -bt 1 -bin 1,2,5,10 -du us
> probe -ena
76.01FP33/2-A Page 92 5/17

5.1.25.2 Type 1: 2-way Delay/Variation (DMM/DMR) Probe Example

Type 1 probe provides 1 and 2-way frame delay and frame delay variation measurements.
The example below configures a Type 1 probe for Port 1 with a Maintenance Domain “Domain1”,
Maintenance Association “MA01” and Maintenance Endpoint 101 on the local 7090-01.
7090> probe -a -p 2 -ty 1 -n MD4 -o MA4 -m 231
To display the results, use the probe -s command.
7090> probe -s
Probes enabled
--- Probe #1 -------------------------------------------------------------

Name:
Destination 00-06-87-01-74-ee (Domain Level = 4 ; VLAN = 100 ; Priority = 0)

========================== ========================== ============
10s: 0.006 0.006 0.006 0.000 0.000 0.000 10 10
1 min: 0.004 0.006 0.006 0.000 0.002 0.000 60 60
5 min: 0.004 0.006 0.006 0.000 0.002 0.000 300 300
15 min: 0.004 0.006 0.006 0.000 0.002 0.000 900 900
1-way Forward FD Frame Variation Total Frames

========================== ========================== ============
10s: 0.003 0.003 0.003 0.000 0.000 0.000 10 10
1 min: 0.002 0.003 0.003 0.000 0.001 0.000 60 60
5 min: 0.002 0.003 0.003 0.000 0.001 0.000 300 300
15 min: 0.002 0.003 0.003 0.000 0.001 0.000 900 900
1-way Backward FD Frame Variation Total Frames

========================== ========================== ============
10s: 0.002 0.003 0.003 0.000 0.001 0.000 10 10
1 min: 0.002 0.003 0.003 0.000 0.001 0.000 60 60
5 min: 0.002 0.003 0.003 0.000 0.001 0.000 300 300
15 min: 0.002 0.003 0.003 0.000 0.001 0.000 900 900
7090>
Valid switch options for DMM/DMR:

probe -a -p [portNum] -ty 1 [-pn pName] [-n domainName|-l domainLevel|-ni dindex]
[-o maName|-oi mindex] [-mac macAddr|-m mepid]
[-v primaryVid|-e evcName] [-pri pbits] [-i probeInterval]
[-sz size] [-dat {ones|zeros}]
[-nosync] [-fd ftime] [-fdv ftime]
76.01FP33/2-A Page 93 5/17

To display the real time results, use the probe -s -rt command.
7090> probe -s -rt
Probes enabled
--- Probe #1 -------------------------------------------------------------

Name:
# Time TxTimeStampf RxTimeStampf TxTimeStampb RxTimeStampb

1 22:38:08.8733 22:38:08.8733 22:38:08.8733 22:38:08.8733 22:38:08.8733
2 22:38:07.8734 22:38:07.8734 22:38:07.8734 22:38:07.8734 22:38:07.8734
3 22:38:06.8734 22:38:06.8734 22:38:06.8734 22:38:06.8734 22:38:06.8734
4 22:38:05.8735 22:38:05.8735 22:38:05.8735 22:38:05.8735 22:38:05.8735
5 22:38:04.8736 22:38:04.8736 22:38:04.8736 22:38:04.8736 22:38:04.8736
6 22:38:03.8736 22:38:03.8736 22:38:03.8736 22:38:03.8736 22:38:03.8736
7 22:38:02.8737 22:38:02.8737 22:38:02.8737 22:38:02.8737 22:38:02.8737
8 22:38:01.8737 22:38:01.8737 22:38:01.8737 22:38:01.8737 22:38:01.8737
9 22:38:00.8738 22:38:00.8738 22:38:00.8738 22:38:00.8738 22:38:00.8738
10 22:37:59.8739 22:37:59.8739 22:37:59.8739 22:37:59.8739 22:37:59.8739
11 22:37:58.8739 22:37:58.8739 22:37:58.8739 22:37:58.8739 22:37:58.8739
12 22:37:57.8740 22:37:57.8740 22:37:57.8740 22:37:57.8740 22:37:57.8740
13 22:37:56.8741 22:37:56.8740 22:37:56.8740 22:37:56.8741 22:37:56.8741
14 22:37:55.8741 22:37:55.8741 22:37:55.8741 22:37:55.8741 22:37:55.8741
15 22:37:54.8742 22:37:54.8742 22:37:54.8742 22:37:54.8742 22:37:54.8742
16 22:37:53.8742 22:37:53.8742 22:37:53.8742 22:37:53.8742 22:37:53.8742
17 22:37:52.8743 22:37:52.8743 22:37:52.8743 22:37:52.8743 22:37:52.8743
18 22:37:51.8744 22:37:51.8744 22:37:51.8744 22:37:51.8744 22:37:51.8744
19 22:37:50.8744 22:37:50.8744 22:37:50.8744 22:37:50.8744 22:37:50.8744
20 22:37:49.8745 22:37:49.8745 22:37:49.8745 22:37:49.8745 22:37:49.8745
76.01FP33/2-A Page 94 5/17

To display the bucket time results, use the probe -s -bu command.
7090> probe -s -bu
Probes enabled
--- Probe #1 -------------------------------------------------------------

Name:
Type Min Max Ave Bin#1 Bin#2 Bin#3 Bin#4 Bin#5

1/1/2000 05:28:07.2799; Suspect=No; Initiated 60; Completed 60
FD 2-way 0.004 0.006 0.006 60 0 0 0 0
FD Fwd 0.002 0.003 0.003 60 0 0 0 0
FD Back 0.002 0.003 0.003 60 0 0 0 0
FDV 2-way 0.000 0.002 0.000 60 0
FDV Fwd 0.000 0.001 0.000 60 0
FDV Back 0.000 0.001 0.000 60 0
FD 2-way 0.004 0.006 0.006 60 0 0 0 0
FD Fwd 0.002 0.003 0.003 60 0 0 0 0
FD Back 0.002 0.003 0.003 60 0 0 0 0
FDV 2-way 0.000 0.002 0.000 60 0
FDV Fwd 0.000 0.001 0.000 60 0
FDV Back 0.000 0.001 0.000 60 0
FD 2-way 0.004 0.006 0.006 60 0 0 0 0
FD Fwd 0.002 0.003 0.003 60 0 0 0 0
FD Back 0.002 0.003 0.003 60 0 0 0 0
FDV 2-way 0.000 0.002 0.000 60 0
FDV Fwd 0.000 0.001 0.000 60 0
FDV Back 0.000 0.001 0.000 60 0
FD 2-way 0.004 0.006 0.006 60 0 0 0 0
FD Fwd 0.002 0.003 0.003 60 0 0 0 0
FD Back 0.002 0.003 0.003 60 0 0 0 0
FDV 2-way 0.000 0.002 0.000 60 0
FDV Fwd 0.000 0.001 0.000 60 0
FDV Back 0.000 0.001 0.000 60 0
FD 2-way 0.004 0.006 0.006 60 0 0 0 0
FD Fwd 0.002 0.003 0.003 60 0 0 0 0
FD Back 0.002 0.003 0.003 60 0 0 0 0
FDV 2-way 0.000 0.002 0.000 60 0
FDV Fwd 0.000 0.001 0.000 60 0
FDV Back 0.000 0.001 0.000 60 0
76.01FP33/2-A Page 95 5/17

5.1.25.3 Type 2: 1-way Delay/Variation (1DM) Probe Example

Type 2 probes provide 1-way frame delay and frame delay variation measurements.
For Type 2 probes, each 7090-01 must be configured; one for transmit and the other for receive.
The example below configures a Type 2 probe for receive on Port 2 Maintenance Domain “MA4”,
Maintenance Association “MA4” with a Maintenance Endpoint of 231.
7090> probe -a -p 2 -ty 2 -n MD4 -o MA4 -m 231 -rx
The other 7090-01 is configured for transmit on Port 4 Maintenance Domain “MD4”, Maintenance
Association “MA4” with a Maintenance Endpoint of 230.
7090> probe -a -p 11 -ty 2 -n MD4 -o MA4 -m 230 -tx
To display the results, use the probe -s command on the receive 7090-01.
7090> probe -s
Probes enabled
--- Probe #1 -------------------------------------------------------------

Name:
Port 2 Type = 1-way delay/variation receive enabled, 1 sec

========================== ========================== ============
10s: >2s >2s >2s 0.000 0.000 0.000 n/a 10
1 min: >2s >2s >2s 0.000 0.000 0.000 n/a 60
5 min: >2s >2s >2s 0.000 0.000 0.000 n/a 300
15 min: >2s >2s >2s 0.000 0.000 0.000 n/a 900
7090>
NOTE: Type 2 performance monitoring probe requires clock synchronization between 7090-01s to
return accurate test results. The 7090-01s should be synchronized to the same Network Time Protocol
server.
Valid switch options for 1DM:
[-pri pbits] [-i probeInterval]
[-tx] [-rx] [-sz size] [-dat {ones|zeros}]
[-fd ftime] [-fdv ftime]
76.01FP33/2-A Page 96 5/17

5.1.25.4 Type 3: Single-Ended Loss/Availability (LMM/LMR) Probe Example

Type 3 probes provide single-ended frame loss and availability measurements.
The example below configures a Type 3 probe on Port 2 with a Maintenance Domain “MD4”, Maintenance
Association “MA4” and Maintenance Endpoint 231.
7090> probe -a -p 2 -ty 3 -n MD4 -o MA4 -m 231
Start a continuous ping to generate traffic across the connection.

To display the results, use the probe -s command.
7090> probe -s
Probes enabled
--- Probe #1 -------------------------------------------------------------

Name:
Port 2 Type = frame loss and availability v2, single ended, EVC based, 1 sec
Acceptance Criteria: FLR < 50.0%, Availability > 50%
LMM Far-End (Forward)

Tx Sent Received Loss Avail
===== ========================================
10s: 10 10 10 0.0% 100.0%
1 min: 60 60 60 0.0% 100.0%
5 min: 300 300 300 0.0% 100.0%
15 min: 900 900 900 0.0% 100.0%
LMR Near-End (Backward)

RxSentReceived Loss Avail
===== ========================================
10s: 10 10 20 0.0% 100.0%
1 min: 60 60 120 0.0% 100.0%
5 min: 300 300 600 0.0% 100.0%
15 min: 900 900 1800 0.0% 100.0%
7090>
Valid switch options for LMM/LMR:

[-v primaryVid|-e evcName] [-pri pbits] [-i probeInterval]
[-fr flvalue] [-cpe|-cph] [-avail aavail] [-v1|-v2]
76.01FP33/2-A Page 97 5/17

5.1.26 Protocol Configuration (PROTOCOL)

The protocol command provides the ability to configure specific protocols available on the 7090-01. Telnet,
FTP and SNMP parameters can be configured using the protocol command.
To configure the protocols, use the protocol option from the CLI prompt. A list of options is displayed
when the protocol -h command is entered.
7090> protocol -h
Description: Protocol Configuration

Format: protocol [-h [-ver]|-s] [-snmpv1 prEn] [-snmpv3 prEn]
[-telnet prEn] [-telnetpw pw|-notelpw] [-ftp prEn] [-ftppw pw|-noftppw]
[-keepalive kpEn] [-keeptime kpTime]
Switches:
-ftp set FTP protocol [prEn]: {ena|dis}, default disabled
-ftppw set FTP protocol password [pw], 1-32 ASCII characters
-keepalive set keep alive trap [kpEn]: {ena|dis}, default disabled
-keeptime sets keep alive trap interval [kpTime]: {10...300}, default 10
-noftppw removes FTP password
-notelpw removes Telnet password
-s shows current protocol settings
-snmpv1 set SNMPv1/v2c agent [prEn]: {ena|dis}, default enabled
-snmpv3 set SNMPv3 agent [prEn]: {ena|dis}, default enabled
-telnet set Telnet protocol [prEn]: {ena|dis}, default enabled
-telnetpw set Telnet protocol password [pw], 1-32 ASCII characters
-ver verbose help
7090>
The options available using the protocol command are shown below.
The -ftp switch enables or disables the FTP protocol. The default setting is disabled.
The -ftppw switch configures the FTP password. No password is configured by default.
specific command.
The -keepalive switch enables or disable the keepalive trap. The default setting is disabled.
The -keeptime switch configures the keepalive timer. The keepalive trap interval can be configured to send
the a trap in intervals of 10 to 600 seconds. The default setting is 10 seconds.
The -noftppw switch removes the FTP password.
The -notelpw switch removes the Telnet password.
The -s switch displays the protocol configuration.
The -snmpv1 switch enables or disables the SNMPv1 agent. The default setting is enabled.
The -snmpv3 switch enables or disables the SNMPv3 agent. The default setting is enabled.
The -telnet switch enables or disables Telnet. The default setting is enabled.
The -telnetpw switch configures the Telnet password. The default password is public.
To enable FTP, use the following command.
7090> protocol -ftp ena
76.01FP33/2-A Page 98 5/17

To display the configuration of the protocols, use the protocol -s command.
7090> protocol -s
Telnet protocol: enabled (active, IP = 10.0.0.110, mgt1)

Telnet password: *****
FTP protocol: disabled
FTP password: *****
SNMPv1/v2c agent: enabled
SNMPv3 agent: enabled
Keep alive: disabled, interval=10s
7090>
5.1.27 Restart (RESTART)

The restart command provides the ability to restart (warm boot) the 7090-01 and enable/disable restart
after application and/or FPGA coded is upgraded.
Use the restart option from the CLI prompt to configure or restart the 7090-01. A list of options is displayed
when the restart -h command is entered.
7090> restart -h
Description: Restarts the module

Format: restart [-h [-ver]|-s] [-boot] [{-ena|-dis} {fw|fpga}]
Switches:
-boot perform a warm boot of the module
-dis restart functions: {fw|fpga}
-ena restart functions: {fw|fpga}
[fw] auto restart after firmware upgrade, default
[fpga] auto restart of FPGA after load of new image, default
-s shows restart status
-ver verbose help
7090>
The options available using the restart command are shown below.
The -boot switch will perform a warm boot on the 7090-01.
The -dis and -ena switches disables or enables the restart function when application and/or FPGA code is
upgraded.
specific command.
The -s switch the displays the restart status.
To restart the 7090-01, use the restart -boot command.
7090> restart -boot
76.01FP33/2-A Page 99 5/17

5.1.28 Restore to Factory Defaults (RESTORE)

The restore command provides the ability to restore the 7090-01 to factory default settings or to a
configuration file stored on the 7090-01.
Use the restore option from the CLI prompt to restore factory defaults. A list of options is displayed when
the restore -h command is entered.
7090> restore -h
Description: Restores defaults

Format: restore [-h [-ver]|-a|-d|-s] [-r rType] [-keepip]
Switches:
-a add a new local default settings file based upon current settings
-d deletes current local default settings file
-keepip restore all but IP based settings: IP address, subnet, gateway
-r restore to default [rType]: {factory|local|previous}
-s shows restore status
-ver verbose help
7090>
The options available using the restore command are shown below.
The -a switch creates a new local configuration file.
The -d switch deletes the current local configuration file.
specific command.
The -keepip switch will maintain the current IP setting after the 7090-01 has been restored to factory defaults.
The -r switch restores the 7090-01 to factory defaults or to a configuration file stored on the 7090-01.
The -s switch the displays the restore status.
To create a local configuration file based on the current 7090-01 configuration, use the restore -a command.
7090> restore -a
To display the restore status, use the restore -s command.
7090> restore -s
Factory default file name: modelscfg.ini

Local definition file name: localdefs.ini
7090>
To restore the 7090-01 to factory default settings, use the restore -r factory command.
7090> restore -r factory
The 7090-01 will be rebooted and the factory default settings will be restored.
76.01FP33/2-A Page 100 5/17

5.1.29 IEEE 802.1ag Continuity Check Messages (RMEP)

MEPs exchange Continuity Check Message (CCM) packets with one or more remotely connected end
points. Remote MEP (RMEP) is used to connect a set of MEPs to be used for continuity check.
Use the rmep option from the CLI prompt to configure the remote MEP association. A list of options is
displayed when the rmep -h command is entered.
7090> rmep -h
Description: CFM remote MEP list configuration

Format: rmep [-a|-d|-h|-s|-auto {on|off}] [-n domainName | -l domainLevel] |
-ni dindex] [-o maName | -oi mindex] [-m mepid] [-ver] [-lmep mepid]
[-p portNum]
Switches:
-a add remote maintenance end point
-auto automatic learning of remote MEPs
-d delete remote maintenance end point
-lmep selects the local MEP [mepid] associated with the remote MEP: {1..8191}
-m mep ID, [mepid], unique within a MA: {1...8191}
-s show existing maintenance end point crosschecks
7090>
The options available using the rmep command are shown below.
The -a switch adds a remote MEP to a defined MD/MA/MEP.
The -auto switch automatically learns the remote MEP.
The -d switch deletes a defined remote MEP on a MD/MA/MEP.
specific command.
The -l, -n, and -ni switches indicate a specific level, domain name and index for the remote MEP.
The -lmep switch defines the local MEP that is associated with the remote MEP ID.
The -m switch defines remote MEP ID.
The -o and -oi switches indicate a specific maintenance association of the remote MEP.
The -p switch associates a specific port to a remote MEP.
The -s switch the displays the configured remote MEPs and the running status.
The rmep command only allows the pairing of one local MEP within the same MA. If more than one MEP
is configured locally within the same MA, only the first MEP will be paired with the remote MEP.
The example below creates a remote MEP for Maintenance Domain “MD4” and Maintenance Association
“MA4” Maintenance End Point 231.
7090> rmep -a -n MD4 -o MA4 -m 231
76.01FP33/2-A Page 101 5/17

To display created remote MEPs, use the rmep -s command.
7090> rmep -s
Auto learning is disabled
Local Remote MD MA MD Port Vlan Status/ MAC Domain Name/

MEPID MEPID Idx Idx Lvl Num Id Defect Addr Maint Assoc
================================================================================
230 231 1 1 4 2 100 OK/None 00-06-87-01-74-ee MD4/MA4
7090>
The Status column indicates the condition of the connection.

Failed:
Continuity Check Messages (CCM) are not being received between end points.
RDI:
Remote end point is sending a Remote Defect Indication (RDI). This indicates a failure condition at
the far end (possibly a link down condition on the port).
OK:
CCMs have been received from the far end. Everything is OK.
5.1.30 Run a Script File (RUN)
The run command provides the ability to run a script file located on the 7090-01. The script file is a text
file with the .osf extension. Use FTP to send the script file to the 7090-01. Once the file resides on the
module, use the run command to load the file.
To run a configuration file located on the module, use the run command from the CLI prompt. A list of
options is displayed when the run -h command is entered.
7090> run -h
Description: Executes stored script file

Format: run [-h [-ver]]|[-l]|[-d scriptname]|[-f scriptname]
Switches:
-d delete script file, [scriptname]
-f CLI script file name, [scriptname]
-l list available files
-ver verbose help
7090>
The options available using the run command are shown below.
The -d switch deletes a specific configuration file.
The -f switch defines the file name of the configuration file.
specific command.
The -l switch displays the available files on the 7090-01.
76.01FP33/2-A Page 102 5/17

To store a configuration file on the 7090-01, open a DOS command window and enter the following
commands. Bold lettering indicates information to be entered.
> ftp -w:12288 10.0.0.1 (7090-01 IP address)
Password: <enter ftp password> (from the IP and Control Preferences screen )
230 User logged in
ftp> quote tfs on
200 TFS Enabled
ftp> put <location and filename of the config file> (filename.osf)
200 OK
226 Saving file to flash... closing session
The configuration file has been transferred to the 7090-01.
To display the available files on the module, use the run -l command.
7090> run -l
Name Size
=================================
modelscfg.ini 11554
ag24hr.dat 2
snmp.key 1170
ag7day.dat 2528
FPGA.dat 2818080
7090>
To run a configuration file located on the 7090-01, use the run -f <filename> command.
NOTE: The run command will only execute .osf files.
76.01FP33/2-A Page 103 5/17

5.1.31 Save Configuration Changes (SAVE)

To save the changes when using the CLI, use the save command from the CLI prompt. A list of options is
displayed when the save -h command is entered.
7090> save -h
Description: Save configuration changes into permanent memory

Format: save [-h [-ver]|-s]
Switches:
-s show save status
-ver verbose help
7090>
The options available using the save command are shown below.
specific command.
The -s switch displays the current state of the changes made to the 7090-01.
Use the save -s command to see if the recent changes have been made.
7090> save -s
Save status: some parameters have been changed and have not been stored into Permanent
memory
7090>
To save the changes, use the save command.
7090> save
7090> save -s
Save status: all parameters have been stored into Permanent memory
7090>
NOTE: If power is removed before the save command is initiated, the changes made with the CLI
will be lost.
76.01FP33/2-A Page 104 5/17

5.1.32 SFP Port Information (SFP)

The sfp command displays the digital diagnostic information on the 7090-01.
To display the digital diagnostic information, use the sfp command from the CLI prompt. A list of options
is displayed when the sfp -h command is entered.
7090> sfp -h
Description: Displays SFP port information

Format: sfp [-h [-ver]|-s]
Switches:
-s shows the SFP information
-ver verbose help
7090>
The options available using the sfp command are shown below.
specific command.
The -s switch displays the current state of the changes made to the 7090-01.
76.01FP33/2-A Page 105 5/17

To display the SFP information, use the sfp -s command.
7090> sfp -s
Address A0 Page Contents

===================================================
00: 03 04 07 00 00 00 02 12 00 01 01 01 0D 00 0C 78 ...............x
10: 00 00 00 00 4F 6D 6E 69 74 72 6F 6E 20 53 79 73 ....Omnitron Sys
20: 74 65 6D 73 00 00 06 87 37 32 30 37 4E 2D 31 00 tems....7207N-1.
30: 20 20 20 20 20 20 20 20 30 31 30 30 05 1E 00 31 0100...1
40: 00 1A 00 00 30 30 37 31 33 35 37 30 20 20 20 20 ....00713570
50: 20 20 20 20 31 35 34 00 30 31 20 20 68 B0 01 E2 154.01 h...
60: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
70: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 55 ...............U
Address A2 Page Contents

===================================================
00: 7F FF 80 00 7F FF 80 00 FF FF 00 00 FF FF 00 00 ................
10: FF FF 00 00 FF FF 00 00 FF FF 00 00 FF FF 00 00 ................
20: FF FF 00 00 FF FF 00 00 00 00 00 00 00 00 00 00 ................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
60: 3B 90 80 98 1A 38 1B D0 0A 68 00 00 00 00 00 F8 ;....8...h......
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Bit rate: 1300 Mbps

Vendor Name: Omnitron Systems
Vendor Part Number: 7207N-1
Vendor Serial Number: 00715447
Date Code: 10/20/2015
Temperature: 57.5C
Vcc: 3.0v
Bias current: 20.0ma
Tx power: -7.0 dBm
Rx power: -7.9 dBm
7090>
Specific data has been decoded and displayed. All other data is displayed using hexadecimal values per
specification SFF-8472.
76.01FP33/2-A Page 106 5/17

5.1.33 Display the Common Configuration Parameters (SHOWCONFIG)

The showconfig command display the commonly configured parameters on the module. The parameters
that are displayed are: ver, ip, port, protocol, traphost, time, module, ethertype, evc, interface, cos and bwp.
To display the parameters, use the showconfig command from the CLI prompt. A list of options is displayed
when the showconfig -h command is entered.
7090> showconfig -h
Description: Shows basic configuration information

Format: showconfig [-h [-ver]]|[-s]
Switches:
-s shows the standard configuration information
-ver verbose help
7090>
The options available using the showconfig command are shown below.
specific command.
The -s switch displays the current state of the changes made to the module.
Use the showconfig -s command to display the configuration of the module.
76.01FP33/2-A Page 107 5/17

5.1.34 Simple Network Management Protocol (SNMP)

The snmp command provides the ability to configure the SNMP parameters on the 7090-01.
To configure the 7090-01 to support Simple Network Management Protocol (SNMP), use the snmp command
from the CLI prompt. A list of options is displayed when the snmp -h command is entered.
7090> snmp -h
Description: SNMP Configuration

Format: snmp [-h [-ver]|-s] [-rdcomm pw] [-wrcomm pw] [-wr wrEn]
[-u1type uTyp] [-u1name uName] [-u1auth uPw] [-u1priv uPw] [-u1sec uSec]
Switches:
-rdcomm set SNMPv1/2c read community name [pw], 1-32 ASCII characters
-s shows current SNMP settings
-u1auth set SNMPv3 user 1 authent password [uPw], 1-16 ASCII characters
-u1name set SNMPv3 user 1 name [uPw], 1-16 ASCII characters
-u1priv set SNMPv3 user 1 privacy password [uPw], 1-16 ASCII characters
-u1sec set SNMPv3 user 1 security level [uSec]:
{noAuthNoPriv, authNoPriv, authPriv}
-u1type set SNMPv3 user 1 type [uTyp]: admin, deny, readonly, readwrite
-ver verbose help
-wr set SNMP write enable [wren]: {ena|dis}, default enabled
-wrcomm set SNMPv1/2c write community name [pw], 1-32 ASCII characters
7090>
The options available using the snmp command are shown below.
specific command.
The -rdcomm switch configures the SNMPv1/V2c read community name. The SNMP Read Community
Name is necessary for reading (get) data from the 7090-01. The name can be any 1-32 alphanumeric
character string. The default setting is public.
The -s switch displays the SNMP configuration parameters.
The -u1auth switch configures the SNMPv3 authentication password for User 1. Authentication password
can be any 1-16 alphanumeric character string. The default setting is publicguest.
76.01FP33/2-A Page 108 5/17
The -u1name switch configures the SNMPv3 user name for User 1. The username can be any 1-32
alphanumeric character string. The default setting is guest.
The -u1priv switch configures the SNMPv3 privacy password for User 1. Privacy password can be any
1-16 alphanumeric character string. The default setting is publicguest.
The -u1sec switch configures the SNMPv3 security level for User 1. The 7090-01 supports the three security
levels: noAuthNoPriv, authNoPriv and authPriv. noAuthNoPriv allows access without authentication and
without privacy. authNoPriv allows access with authentication, but without privacy. authPriv allows access
with authentication and with privacy. Authentication and privacy uses different algorithms for encrypting
and decrypting SNMPv3 packets. The default setting is noAuthNoPriv.
The -u1type switch configures the SNMPv3 user type for User 1. Each user name can be configured as:
admin, read-write, read-only or deny. An admin user has full read/write privileges including user name
and password changes. A read-write user has full read/write privileges with the exception of user name
and password operations. A read-only user can only view the configuration of the 7090-01 and will not be
allowed to make any changes. A deny user does not have any access to the 7090-01. The default setting
is read-only.
The -u2auth switch configures the SNMPv3 authentication password for User 2. Authentication password
can be any 1-16 alphanumeric character string. The default setting is privateadmin.
alphanumeric character string. The default setting is admin.
1-16 alphanumeric character string. The default setting is privateadmin.
levels: noAuthNoPriv, authNoPriv and authPriv. The default setting is noAuthNoPriv.
admin, read-write, read-only or deny. The default setting is admin.
The -u3auth switch configures the SNMPv3 authentication password for User3 . Authentication password
alphanumeric character string. The default setting is guest1.
admin, read-write, read-only or deny. The default setting is deny.
he -u4auth switch configures the SNMPv3 authentication password for User 4. Authentication password
alphanumeric character string. The default setting is guest2.
76.01FP33/2-A Page 109 5/17

admin, read-write, read-only or deny. The default setting is deny.
The -wr switch enables/disables the ability to respond to SNMP write (set) commands. SNMP Writes is
enabled by default.
The -wrcomm switch configures the SNMPv1/V2c write community name. The SNMP Write Community
Name is necessary for writing (set) data to the 7090-01. The name can be any 1-32 alphanumeric character
string. The default setting is public.
To configure SNMPv3 User 1 login credentials, use the following commands.
7090> snmp -u1auth 12345 -u1name JSmith -u1priv 67890 -u1sec authNoPriv -u1type admin
To display the SNMP parameters, use the snmp -s command.
7090> snmp -s
Read Community Name *****

Write Community Name *****
User 1 type admin
User 1 name JSmith
User 1 Security level authNoPriv
User 1 Privacy password *****
User 1 Authentication password *****
User 2 type admin

User 2 name admin
User 2 Security level noAuthNoPriv
User 3 type deny

User 3 name guest1
User 4 type deny

User 4 name guest2
7090>
76.01FP33/2-A Page 110 5/17

5.1.35 Simple Network Time Protocol (SNTP)

The sntp command provides the ability to configure the 7090-01 to request the time and day from a SNTP
server.
To configure the 7090-01 to support Simple Network Time Protocol (SNTP), use the sntp command from
the CLI prompt. A list of options is displayed when the sntp -h command is entered.
7090> sntp -h
Description: SNTP protocol configuration

Format: sntp [-h [-ver]|-s] [-ena|-dis] [-i interval] [-z zoneVal]
[-ip1 serverNumIP] [-ip2 serverNumIP]
Switches:
-dis disable SNTP on the module
-ena enable SNTP on the module
-i time server requested every [interval] minutes: {1...60}
-ip1 time server IP address 1, [serverNumIP]
-ip2 time server IP address 2, [serverNumIP]
-s show SNTP configuration
-ver verbose help
-z set the time [zoneVal]
To get help screen on time zone values type “zone -h”
7090>
The options available using the sntp command are shown below.
The -dis and -ena switches disable or enable SNTP on the 7090-01.
specific command.
The -i switch defines the time interval between SNTP requests.
The -ip1 and -ip2 switches define the IP addresses of the SNTP servers.
The -s switch displays the SNTP configuration.
The -z switch defines the time zone.
To enable SNTP services and assign the SNTP server IP address, use the -ena and -ip1 commands.
7090> sntp -ena -ip1 10.0.0.200
To display the SNTP configuration, use the sntp -s command.
7090> sntp -s
SNTP service is enabled, query interval is 5 minutes
time zone PDT (Pacific Daylight Time)
SNTP server 1 IP is 10.0.0.200
SNTP server 2 IP is 255.255.255.255 (not configured)
SNTP server request sent (sourced) from IP 1
7090>
76.01FP33/2-A Page 111 5/17

5.1.36 Ethernet Service Testing

5.1.36.1 Overview
Ethernet connections must be tested to ensure that they are operating correctly and performing to the required
levels. RFC 2544 specifies certain test criteria that allows Ethernet connections to validate operation and
service level agreements. RFC 2544 performs specific tests using standard frame sizes (64, 128, 256, 512,
1024, 1280 and 1518 bytes).
ITU-T Y.1564 is a Carrier Ethernet service activation test methodology for turning up, installing and
troubleshooting Ethernet-based services. The test methodology allows for complete validation of Ethernet
Service Level Agreements (SLAs) in a single test.
ITU-T Y.1564 defines test streams with specific attributes identified by different classifiers such as 802.1Q
VLAN, 802.1ad and Class of Service (CoS) profiles.
5.1.36.2 Third-Party Test Equipment
The module can be configured to respond to inband loop-up and loop-down commands from third party
test equipment, such as JDSU, Sunrise and VeEX. Configure the remote module using the testresp -remote
command. See Section 5.1.36.4 for configuration examples.
5.1.36.3 Built-in Test Initiator (TESTINIT)
The testinit command configures the built-in test-head to generate RFC 2544, Y.1564 and/or TWAMP test
measurements traffic to a Test Responder module. The built-in test-head or Test Initiator will generate
frames based on the user-defined configuration. The Responder module receives the frames and loops the
traffic back to the Test Initiator.
RFC 2544 Test Initiator uses the -typ throughput/latency/loss/back commands to configure the built-in
test-head.. The Y.1564 Test Initiator uses the -typ service command to configure the built-in test-head.
NOTE: During a power cycle or reboot, testinit and testresp commands will need to be re-entered.
The testinit and testresp commands are not saved.
76.01FP33/2-A Page 112 5/17

To configure the 7090-01 as a test initiator, use the testinit option from the CLI prompt. A list of options
is displayed when the testinit -h command is entered.
7090> testinit -h
Description: Configures and displays the results of the Test Initiator

Format: testinit [-a|-d|-dall|-h [-ver]|-s] [-p portNum] [-pn profileName]
[-pi pindex|all] [-ena|-dis {inservice|monitor|test}] [-clr]
[-po|-e evcName {-cn cName}|{-bn bname}|{-n dName|-l dLevel|-ni dindex }
{-o maName|-oi mindex}] [-pri pbit] [-v evcVid] {-mac macAddr|-mep mepid}
[-pdu ptype] [-typ ttype] [-r fcnt|-t tsec] [-frt frate|-bit brate|
-rp prate] [-fsz fsizemin[,fsizemaxm,fincr]|-fst|-fmx
fsize1,..fsize8] [-trial tnum] {-flr fratio|-flc nframes}
[-pe portNum] [-decr dval] [-restart] [-btype btypesel]
[-ipdst ipAddr] [-ipsrc ipAddr] [-fd ftime] [-remote rpro]
[-fty fixed|binary] [-fdv ftime] [-cir100]
[-perf] [-dists] [-dat {ones|prbs|zeros}[,crc]] [-avail aavail]
[-etype eval]
Switches:
-a add test instance
-avail acceptable availability percent, [aavail]: {0.0...100.0}, default 50.0
-bit number of bits per seconds, [brate]: {25000...1000000000}, default=max
-bn bandwidth profile identifier name [bName], 1-45 ASCII characters
-btype bit rate selection type, [btypesel}: {L1,L2,L3}, default L1
-cir100 run the A.1 test. The default is to run the A.2 test
-clr clears specific test instance data
-d deletes test instance
-dall deletes all configured test instances
-dat selects data payload value: {ones|prbs|zeros}[,crc]
[ones] selects a payload that is filled with ones
[prbs] selects PRBS 2^-31 data pattern
[zeros] selects a payload that is filled with zeros, default
[crc] selects whether the last four bytes of the payload includes a CRC
-decr failure decrement step size [dval]: {1-100}, default 10
-dis disable function: {monitor|test}
-dists turns off insertion of timestamp into Test/Data TLV
-ena enable function: {monitor|test}
[monitor] selects test monitor function, default enabled
[test] test instance, default enabled
-etype selects the data ethertype, [eval], default 0x9001
-fd acceptable frame delay, [ftime]: {1..1000000} us, default 100000
-fdv acceptable frame delay variation, [ftime]: {1..1000000} us, default 100000
-flc acceptable frame loss count, [nframes]: {0...65535}, default 10
-flr acceptable frame loss ratio percent, [fratio]: {0.000...100.000}
-fmx selects a mixed list of 1-8 frame sizes: {fsize1,..,fsize8}
-frt number of frames per second, [frate]: {10...1488095}
-fst selects standard frame sizes of 64, 128, 256, 512, 1024, 1280, 1518
-fsz selects test instance frame size range
[fsizemin] starting frame size: {64...10240}, default 64
[fsizemax] maximum frame size: {64...10240, must be >= fsizemin
if no ending size is selected only a single size is tested
[fincr] frame size increment value, multiple of 4, default is 4
-fty selects failure mechanism decrement type: {fixed|binary}
-ipdst selects the IP destination address, [ipAddr]
-ipsrc selects the IP source address, [ipAddr]
-l maintenance domain level, [dLevel]: {0...7}
default 00-00-00-00-00-01
76.01FP33/2-A Page 113 5/17

-mep destination mep ID, [mepid], unique within a MA: {1...8191}

-n defines domain name, [dName], 1-43 ASCII characters
-p source [portNum] selected: {1|2}
-pdu test instance pdu type, [ptype]: {L2|L3|lbm|tst}
[L2] indicates standard layer 2 frame type, default
[L3] indicates standard layer 3 frame type
[lbm] indicates standard CFM frame type, needs md/ma/mep defined
[tst] indicates standard Y.1731 frame type, needs md/ma/mep defined
-pe egress [portNum]: {1|2}, default same as source port
-perf selects the service performance test. Default is the service config test
-pi test instance profile index [pindex]: {1..16} or [all] profiles
-pn defines [profileName], 1-45 ASCII characters
-po test instance associated with port
-pri selects frame priority bit, [pbit], default is 0
-r number of frames, [fcnt], to send: {0...2^32-1}, 0=no end
-remote remote protocol, [rpro]: {jdsu|sunrise|twamp|veex}
[jdsu] indicates proprietary JDSU protocol
[sunrise] indicates proprietary Sunrise Telecom protocol
[twamp]indicates standard TWAMP protocol
[veex] indicates proprietary VeEX protocol
-restart restarts the indicated test instance
-rp rate in percentage of interface speed, [prate}: {0.001...100.000}
-t time in seconds [tsec] to run: {0...2^32-1}, 0=no end, 10=default
-trial number of trials, [tnum], for a particular test instance: {1..65535}
-typ test instance type, [ttype]:
[throughput] RFC 2544 throughput test
[latency] RFC 2544 latency test
[loss] RFC 2544 loss test, default
[back] RFC 2544 back-to-back test
[service] ITU-T Y.1564 service activation test
-useeir uses the EIR when running the CIR test
-v [evcVid] associated with the test instance: {0...4095}
-ver verbose help
7090>
The options available using the testinit command are shown below.
The -a switch adds a test instance to the port, EVC, EVC+CoS, or MEP.
The -avail switch configures the acceptable availability for 1564 test.
The -bit switch defines the frequency the test PDUs are generated. -bit switch defines the bit rate.
The -bn switch indicates the specific test instance is associated with a bandwidth profile. -bn identifies the
bandwidth profile name.
The -btype switch defines how the bit rate will be determined: Layer 1, Layer 2 or Layer 3.
The -cir100 switch runs the 1564 A.1 test only. If not specified, the 1564 A.2 test is ran.
The -clr switch clears the test results.
The -cn switch associates the test instance with a class of service profile, defined using the cos command.
The -d switch deletes a test instance.
The -dall switch deletes all test instances.
The -dat switch selects the payload type: all zeros (default), all ones, or PRBS, all with or without a CRC.
76.01FP33/2-A Page 114 5/17

The -decr switch indicates the change in percentage on the amount of traffic sent during a test. During
a test, the amount of traffic sent is increased or decreased by the percentage value to find the maximum
throughput the 7090-01 can pass (increasing or decreasing the percentage value is based on passing or
failing the present percentage value). The entered value is in percent of the initial rate.
The -dis and -ena switches disable or enable specific functions or test instances.
The -dists switch turns off insertion of the timestamp for Data/Test TLVs. This is needed for one-way
measurements.
The -e switch associates the test instance with an EVC.
The -etype switch configures the ethertype for the test instance. The default is 0x9001.
The -fd switch defines the acceptable frame delay.
The -fdv switch defines the acceptable frame delay variation.
The -flr and -flc switches define the number of errors before a failure condition is declared during a test.
-flr switch displays the errors in percentages, and the -flc switch displays the errors in number of frames.
The -frt switch defines the frame rate.
The -fsz , -fst and -fmx switches define the PDU frame sizes for the test instance. -fsz switch defines a range
of frame sizes, the -fst switch selects the standard seven frame sizes of 64, 128, 256, 512, 1024, 1280, and
1518, and -fmx switch allows the selection of up to 8 individual frame sizes.
The -fty switch indicates how the test will increment or decrement the throughput traffic levels to find the
maximum amount of traffic the 7090-01 can pass (increasing or decreasing the percentage value is based on
passing or failing the present percentage value). A failure condition is defined by the -flr or -flc switches.
fixed indicates the increment or decrement value will be defined by the -decr switch.
binary indicates the percentage value is decreased or increased by 50% of the previous value but will
not continue if the percentage change is less then the -decr switch when the test fails.
specific command.
The -ipdst switch defines the virtual destination IP address used when a L3 test is selected.
The -ipsrc switch defines the virtual source IP address used when a L3 test is selected.
The -l, -n, and -ni switches associate a specific test instance with a maintenance domain.
The -mac switch associates the test instance with a specific unicast destination address and frames received
from the destination MAC address are ignored.
The -mep switch associates the test instance with a specific MEP ID.
The -o and -oi switches associate a specific test instance with a maintenance association.
The -p switch defines the initiating port. The combination of -p and -pe switches defines the logical starting
point of the test frames (-p) and the egress point of the test frame (-pe). This allows a test instance to be
defined on a UNI port and able to egress a NNI port double tagged.
The -pdu switch defines the type of test frame PDU.
The -pe switch defines the egress port where the test PDUs are generated. The initiating port is set via the
-p switch.
The -perf switch indicates the service performance test will be initiated. Without this switch the service
configuration test will be initiated.
The -pi or -pn switches are used to identify or name a specific test profile.
The -po switch associates the test instance with a port.
76.01FP33/2-A Page 115 5/17

The -pri switch associates the selected VLAN priority bits with a specific test instance.
The -r switch defines the number of frames to send in a test; 0=unlimited.
The -remote switch indicates the communication protocol used with the remote partner.
jdsu indicates the JDSU proprietary loop up/down protocol will be used.
sunrise indicates the Sunrise Telecom proprietary loop up/down protocol will be used.
twamp indicates the TWAMP protocol will be used.
veex indicates the VeEX proprietary loop up/down protocol will be used.
The -restart switch will restart the selected tests by first clearing the current completed history information
and then starting the configured and selected tests.
The -rp switch defines the rate of the interface speed as a percentage.
The -s switch the displays the current tests and results.
The -t switch defines the amount of time to run a test in seconds, 0=forever.
The -trial switch selects the number of trials to run for a particular test, size, rate and time.
The -typ switch configures the type of test: throughput, latency, loss, back to back and Y.1564.
The -useeir switch indicates the 1564 A.1/A.2 test will be initiated with EIR if CIR=0.
The -v switch associates a test instance with a specific VLAN ID specified by an EVC (-e switch).
The -ver switch displays the extended help and show results.
A test instance can be added to a port, EVC or Maintenance End Point (MEP). If a test instance is defined
on a port, a second test instance using an EVC or MEP will not be allowed. If a test instance is defined on
a EVC, a second test instance using port only will not be allowed.
The example below creates a frame loss test instance on Port 1.
7090> testinit -a -p 1 -pn test -mac 00-06-87-00-cf-f9 -e E2
The command creates an initiator instance on Port 1 to a destination MAC address of 00:06:87:00:cf:f9
using test as the instance name. The default measurement type is: frame loss with a frame size of 64 bytes.
76.01FP33/2-A Page 116 5/17

Verify the test results by using the testinit -s command.
7090> testinit -s
Product: 7090-01 CE (7301A)

--- Test Initiator Instance #1 -----------------------------------------------

Test Name: test, Source Port 1, Destination Port 1
Test Generator enabled, Test Monitor enabled, Out-of-Service
Test Status: Completed
Test Type: 2544 Frame Loss
Frame sizes: 64
Acceptable frame loss: 10 frames/trial, fixed search (10%)
Number of trials: 1; test duration: 10s
Data payload: zeros
EVC name “E2” (VID 1000), PCP value 0,
Test Partner: MAC 00-06-87-00-cf-f9
Remote Protocol: None
Initial Line Rate: 1,000,000,000 bits/sec (L1 rate calculation type)
Trial/ Frame -----Configured----- Transmit Receive Frame Frames Test
Iter Size (fps) (mbps) % Count Count Loss % Lost Status
*******************************************************************************
1/1 64 1488095 1000.0 100 14880950 14880950 0.000 0 PASS
Delete the test instance by using the testinit -d command.
7090> testinit -d -pn test1
The example below creates a frame loss test instance on Port 1 using the standard frame sizes.
7090> testinit -a -p 1 -pn test1 -mac 00-06-87-00-cf-f9 -e E2 -fst
The example below creates a latency test instance on Port 1.
7090> testinit -a -p 1 -pn test1 -mac 00-06-87-00-cf-f9 -e E2 -typ latency
The example below creates a throughput test instance on Port 1.
7090> testinit -a -p 1 -pn test1 -mac 00-06-87-00-cf-f9 -e E2 -typ throughput
The example below creates a back-to-back test instance on Port 1.
7090> testinit -a -p 1 -pn test1 -mac 00-06-87-00-cf-f9 -e E2 -typ back
The example below creates a frame loss measurement to remote MEP 332.
7090> testinit -a -p 1 -pn test1 -e EVC1 -l 3 -pdu lbm -mep 332
76.01FP33/2-A Page 117 5/17

The example below creates a Y.1731 ETH-Test latency measurement to remote MEP 200.
7090> testinit -a -p 1 -pn test1 -n Domain -o MA00 -pdu tst -typ latency -mep 332
The example below creates a TWAMP test initiator.
7090> testinit -a -p 1 -pn test1 -e E1 -remote twamp -ipdst 10.2.2.2 -ipsrc 10.2.2.1
NOTE: The minimum frame size supported by TWAMP is 91 bytes.

The example below restarts the test instance called test1.
7090> testinit -restart -pn test1
5.1.36.4 Test Responder (TESTRESP)

The testresp command configures the 7090-01 to respond to RFC 2544, Y.1564 test measurements from the
Test Initiator or 3rd party test equipment (JDSU, Sunrise and VeEX). It can also be configured to respond
to TWAMP protocol.
The Test Initiator will generate frames based on the user-defined configuration. The Responder receives
the frames and loops the traffic back to the Test Initiator.
The 3rd party test equipment will issue inband loop up and loop down commands that will be received by
the Responder. When a loop up command is received, the port or EVC will loop all traffic back to the test
equipment. When a loop down command is received, the port or EVC will return to normal operation.
NOTE: During a power cycle or reboot, testinit and testresp commands will need to be re-entered.
The testinit and testresp commands are not saved.
76.01FP33/2-A Page 118 5/17

To configure the 7090-01 as a test responder, use the testresp option from the CLI prompt. A list of options
is displayed when the testresp -h command is entered.
7090> testresp -h
Description: Configures and displays the results of the Test Responder

Format: testresp [-a|-d|-dall|-h [-ver]|-s] [-p portNum] [-pn profileName]
[-pi pindex|all] [-clr] [-ena|-dis {inservice|mcast|monitor|reflect}]
[-po | -e evcName [-cn cName] | {-n dName | -l dLevel | -ni dindex }
{-o maName | -oi mindex} ] [-mac macAddr | -mep mepid] [-rty rtype]
[-pe portNum] {-v evcVid} [-remote rpro] [-lmac] [-ipsrc ipAddr]
[-ipdest ipAddr] [-etype eval]
Switches:
-a add test instance
-clr clears specific test instance data
-d deletes test instance
-dall delete all test instances settings and restore defaults
-dis disable function: {mcast|monitor|reflect}
-ena enable function: {mcast|monitor|reflect}
[mcast] sets source MAC substitution for multicast, default disabled
[monitor] selects test monitor function, default enabled
[reflect] selects test reflector function, default enabled
-etype selects the data ethertype, [eval], default 0x9001
-ipdst selects the IP destination address, [ipAddr]
-ipsrc selects the IP source address, [ipAddr]
-l maintenance domain level, [dLevel]: {0...7}
-lmac frames received must match local module’s MAC address
-mac source MAC Address, [macAddr]: {xx-xx-xx-xx-xx-xx}
-mep source mep ID, [mepid], unique within a MA: {1...8191}
-n defines domain name, [dName], 1-43 ASCII characters
-p responding [portNum] selected: {1|2}
-pe egress [portNum]: {1|2}, default same as responding port
-pi test instance profile index [pindex]: {1..16} or [all] profiles
-pn defines [profileName], 1-45 ASCII characters
-po test instance associated with port
-remote remote protocol, [rpro]: {jdsu|sunrise|veex}
[jdsu] indicates proprietary JDSU protocol
[sunrise] indicates proprietary Sunrise Telecom protocol
[twamp] indicates standard TWAMP protocol
[veex] indicates proprietary VeEX protocol
-rty reply type, [rtype]: {lbr|loop|macswap|tst}
[lbr] indicates an LBR is sent in response to a LBM
[loop] indicates egress is equal to ingress (L1)
[L3] indicates Layer 3 (IP) reply type, includes MAC/IP swap
[macswap] swaps the DA/SA of the frame, default (L2)
[tst] indicates standard Y.1731 ETH-Test
-v [evcVid] associated with the test instance: {0...4095}
7090>
The options available using the testresp command are shown below.
The -a switch adds a test instance to the port, EVC, EVC+CoS, or MEP.
The -clr switch clears the test results.
76.01FP33/2-A Page 119 5/17
The -d switch deletes a test instance.

The -dall switch deletes all test instances.
The -dis and -ena switches disable or enable specific functions or test instances.
The -e switch associates the test instance with an EVC.
The -etype switch configures the ethertype for the test instance. The default is 0x9001.
specific command.
The -ipdst switch defines the virtual destination IP address of the responder used when a L3 test is selected.
The -ipsrc switch defines the virtual source IP address used when a L3 test is selected.
The -l, -n, and -ni switches associate a specific test instance with a maintenance domain.
The -lmac switch defines the local 7090-01’s MAC address of the received frames.
The -mac switch associates the test instance with a specific unicast destination address and frames received
from the destination MAC address are ignored.
The -mep switch associates the test instance with a specific MEP ID.
The -o and -oi switches associate a specific test instance with a maintenance association.
The -p switch associates a port to a specific test instance.
The -pe switch defines the egress port where the test PDUs are generated. The responding port is set via
the -p switch.
The -pn or -pi switches are used to name or identify a specific test profile.
The -po switch associates the test instance with a port.
The -remote switch indicates the communication protocol used with the remote partner.
jdsu indicates the JDSU proprietary loop up/down protocol will be used.
sunrise indicates the Sunrise Telecom proprietary loop up/down protocol will be used.
twamp indicates the TWAMP protocol will be used.
veex indicates the VeEX proprietary loop up/down protocol will be used.
The -rty switch defines the type of reply by the responder unit.
The -s switch the displays the current test configuration and status.
The -v switch associates the test instance with a specific VLAN ID.
The -ver switch displays the extended help and show results.
The example below configures Port 1 on the 7090-01 as a responder for test instance test1.
7090> testresp -a -p 1 -pn test1 -e E2
The example below configures EVC Data to respond to inband commands from a JDSU tester.
7090> testresp -a -p 1 -pn jdsu -e Data -remote jdsu
The example below configures EVC Data to respond to inband commands from a Sunrise tester.
7090> testresp -a -p 1 -pn sunrise -e Data -remote sunrise
76.01FP33/2-A Page 120 5/17

The example below configures EVC E1 to respond to inband commands using the TWAMP protocol.
7090> testresp -a -p 1 -pn twamp -e E1 -remote twamp -ipdst 10.2.2.2 -ipsrc 10.2.2.1
NOTE: The TWAMP responder module will not be activated until a TWAMP loopup commands is
received.
Verify the 7090-01 has been configured by using the testresp -s command.
7090> testresp -s
Product: 7090-01 CE (7301A)

--- Test Responder Instance #1 -------------------------------------------

Test Name: Test, Responding Port 2, Destination Port 1
Test Responder enabled, Test Monitor enabled, Multicast Replacement disabled
Standard response disabled, Out-of-Service enabled
Reply Type: MAC Swap (Remote protocol: None)
EVC name “Data” (VID 100)
Local MAC Match disabled
Received frame counts: 29761900

Transmitted frame counts: 29761900
7090>
The examples below show how to configure the test initiator and test responder for different test instances.
The diagram below illustrates the network configuration used for the test examples.
76.01FP33/2-A Page 121 5/17

The following configuration will be used in the test examples.

Test Responder Setup
Packet Transport Platform
CLI Command
> evc -dis
> evc -dall
> cfm -dis all
> evc -a -e Data -p 1,2,7 -v 1000
> evc -a -e mgt -p 1,2,7,mgt1 -v 2000
> interface -a -p 1,2 -t nni
> evc -ena
> md -a -n MD4 -l 4
> mep -a -n MD4 -o MA4 -e Data -p 7 -m 231 -dn
> cfm -ena all
> testresp -a -p 7 -v 100 -e Data -pn Test
Test Initiator Setup

7090-01
CLI Command
> evc -dis
> evc -dall
> cfm -dis all
> evc -a -e Data -p 1,2 -v 1000
> evc -a -e mgt -p 1,2,mgt1 -v 2000
> evc -ena
> md -a -n MD4 -l 4
> cfm -ena all
> testinit -a -p 2 -pe 1 -v 100 -e Data -pn Test -typ throughput -fst
76.01FP33/2-A Page 122 5/17

Below are example of different Test Responder/Test Initiator configurations:

Frame Loss - EVC
The example below creates a frame loss test instance across the Data EVC using the standard frame sizes.
Test Responder
CLI Command
> testresp -a -p 11 -v 100 -pn loss -e Data
Test Initiator
CLI Command
> testinit -a -p 2 -pn loss -mac 00:06:87:00:cf:f9 -e Data -fst
Frame Loss - MEP

The example below creates a frame loss LBM test instance to remote MEP 231.
Test Responder
CLI Command
> testresp -a -p 11 -pn loss -e Data -l 4 -rty lbr -mep 230
Test Initiator
CLI Command
> testinit -a -p 2 -pn loss -e Data -l 4 -pdu lbm -mep 231
Frame Loss - ETH-Test

The example below creates a frame loss ETH-Test test instance to remote MEP 231 using the standard
frame sizes.
Test Responder
CLI Command
> testresp -a -p 11 -pn loss -n MD4 -o MA4 -rty tst
Test Initiator
CLI Command
> testinit -a -p 2 -pn loss -n MD4 -o MA4 -pdu tst -typ loss -mep 231 -fst
76.01FP33/2-A Page 123 5/17

5.1.37 Set/Display Time of Day (TIME)

The time command provides the ability to set or display the time of day on the 7090-01. The system uptime
will also be displayed.
To configure the time on the 7090-01, use the time command from the CLI prompt. A list of options is
displayed when the time -h command is entered.
7090> time -h
Description: Displays the time of day

Format: time [-h [ver]|-s] [-a timeOfDay] [-z zoneVal]
Switches:
-a sets the time of day, [timeOfDay]: month/day/year 24hr:min:sec
-s show current time of day
-ver verbose help
-z set the time [zoneVal]
7090>
The options available using the time command are shown below.
The -a switch is used to set the time of day.
specific command.
The -s switch displays the current time of day.
The -z switch defines the time zone.
The example below sets the time of day.
7090> time -a “1/24/2017 07:55:00”
To display the time of day, use the time -s command.
7090> time -s
Time of day: 1/24/2017 07:55:03 AM Pacific Standard Time

sysUpTime: 40738676 (4 days 17 hours 9 minutes 46 secs)
7090>
76.01FP33/2-A Page 124 5/17

5.1.38 SNMP Trap Host (TRAPHOST)

SNMP traps report events that occur during the operation of a network, and may require the attention of
the network administrator. The 7090-01 is capable of sending SNMP traps to eight different SNMP Trap
Hosts (IP addresses).
The traphost command provides the ability to configure the IP addresses of the SNMP Trap Hosts.
To configure the Trap Hosts, use the traphost command from the CLI prompt. A list of options is displayed
when the traphost -h command is entered.
7090> traphost -h
Description: SNMP Trap Host Configuration

Format: traphost [-dall|-h [-ver]|-s] [-ip ipAddr] [-host hNum]
Switches:
-dall delete all SNMP trap hosts and set back to 255.255.255.255
-host select traphost number [hNum]: {1...8}
-ip selects the IP trap host address, [ipAddr]
-s shows current SNMP settings
-ver verbose help
7090>
The options available using the traphost command are shown below.
The -dall switch deletes are configured trap hosts and resets the setting to factory default. The default
setting is 255.255.255.255.
specific command.
The -host switch selects the Trap Host number to be configured. Eight different Traps Hosts can be
configured.
The -ip switch configures the IP address for the selected Trap Host.
The -s switch displays the SNMP Trap Host settings.
To configure the IP address for Trap Host 1, use the following command.
7090> traphost -host 1 -ip 10.0.0.100
To display the Trap Host configuration, use the traphost -s command.
7090> traphost -s
SNMP Trap Host #1 IP address = 10.0.0.100 (pending, Save required)

SNMP Trap Host #2 IP address = 255.255.255.255 (not configured)
7090>
76.01FP33/2-A Page 125 5/17

5.1.39 SNMP Traps (TRAPS)

The traps command provides the ability to enable/disable specific 7090-01 traps. By default, all traps are
enabled.
To enable traps, use the traps option from the CLI prompt. A list of options is displayed when the traps -h
command is entered.
7090> traps -h
Description: Trap configuration

Format: traps [-dall|-h|-log|-s] [{-ena|-dis} tnum|-disall|-enaall]
[-tbl ttype] [-portnum portnumber] [-clear] [-gen tnum]
[-type {snmpv1|snmpv2c|snmpv3}]
Switches:
-clear clears trap log
-dall restores trap defaults
-dis disable selected [tnum]
-disall disable generation of all traps
-ena enable selected [tnum]
-enaall enable generation of all traps
-gen generates the [tnum] trap number
-log shows last 100 trap entries
-portnum SNMP trap [portnumber], default 162
-s show the current trap configuration
-tbl selects the trap table type, [ttype]:
{cfm|ent|lldp|mef}
[cfm] selects 802.1ag trap number
[ent] select enterprise specific trap number, default
[lldp] selects LLDP trap number
[mef] selects MEF trap number
-type selects SNMP trap generation type: {snmpv1|snmpv2c|snmpv3}
-ver verbose help
7090>
The options available using the traps command are shown below.
The -clear switch clears the current trap log entries.
The -dall switch restores all traps to default.
The -dis switch defines which trap types will be disabled.
The -disall switch disables all traps.
The -ena switch defines which trap types will be enabled.
The -enaall switch enables all traps.
The -gen switch generates a specific trap number. Traphost must be configured to receive the generated trap.
specific command.
The -log switch displays the last 100 trap entries.
The -portnum switch defines the SNMP UDP trap port number.
The -s switch displays the current trap configuration.
The -tbl switch selects the trap type to be displayed.
The -type switch selects the generation type of the trap (snmpv1, snmpv2c, snmpv3).
76.01FP33/2-A Page 126 5/17

The example below enables all traps.
7090> traps -ena all
Individual traps can be enabled or disabled by entering the name of the traps after the ena/dis command.
The example below disables linktrace traps.
7090> traps -dis linktrace
To display the traps, use the traps -s command.
7090> traps -s
SNMP trap type: SNMPv2c
Trap Type Status

==================================================
1 module inserted Enabled
2 module restarted Enabled
3 module link down Enabled
4 module link up Enabled
5 switch change Enabled
6 software configuration change Enabled
7 module over temperature Enabled
8 module voltage out of range Enabled
9 power removed Enabled
10 power applied Enabled
11 authentication failure Enabled
13 chassis inserted Enabled
14 chassis removed Enabled
16 module removed Enabled
17 primary link up Enabled
18 primary link down Enabled
19 secondary link up Enabled
20 secondary link down Enabled
21 TELNET session started Enabled
22 TELNET session stopped Enabled
23 FTP session started Enabled
24 FTP session stopped Enabled
25 standby link up Enabled
26 standby link down Enabled
27 password count exceeded Enabled
28 ROM checksum error Enabled
29 ROM file type incorrect Enabled
30 ROM program failure Enabled
31 ROM file checksum error Enabled
32 module programming completed Enabled
33 dying gasp Enabled
34 keep alive Enabled
35 VLAN parameter change Enabled
36 AIS detected Enabled
37 PRBS detected Enabled
39 chassis mastership acquired Enabled
40 secure mode change Enabled
41 chassis mastership lost Enabled
42 SFP device inserted Enabled
43 SFP device removed Enabled
44 ah event notification gen Enabled
45 ah event notification rcv Enabled
76.01FP33/2-A Page 127 5/17

46 contact closure status change Enabled

47 ah link fault received Enabled
48 ah critical event gen Enabled
49 ah remote critical event rcvd Enabled
50 Remote dying gasp Enabled
51 Table Full Enabled
52 Loopback Reply Received Enabled
53 Loopback Reply Lost Enabled
55 CFM Loopback Complete Enabled
56 CFM Link Trace Complete Enabled
57 CFM MEP Up Enabled
58 CFM MEP Down Enabled
59 CFM Cross Connect Enabled
60 CFM Loop Enabled
61 CFM Configuration Error Enabled
62 CFM All MEPs Up Enabled
64 CFM Unknown MEP Enabled
73 SFP/XFP Tx Low Threshold Enabled
74 SFP/XFP Tx High Threshold Enabled
75 SFP/XFP Bias Low Threshold Enabled
76 SFP/XFP Bias High Threshold Enabled
77 SFP/XFP 3.3V Low Threshold Enabled
78 SFP/XFP 3.3V High Threshold Enabled
79 SFP/XFP Temp Low Threshold Enabled
80 SFP/XFP Temp High Threshold Enabled
81 XFP Aux 2 Low Threshold Enabled
82 XFP Aux 2 High Threshold Enabled
83 XFP Aux 1 Low Threshold Enabled
84 XFP Aux 1 High Threshold Enabled
85 SFP/XFP Rx Low Threshold Enabled
86 SFP/XFP Rx High Threshold Enabled
87 XFP 1.8V Low Threshold Enabled
88 XFP 1.8V High Threshold Enabled
89 XFP 5V Low Threshold Enabled
90 XFP 5V High Threshold Enabled
91 TDM Line Status Change Enabled
92 Configuration Change Enabled
93 Loopback Activation Enabled
94 Loopback Deactivation Enabled
95 Timing Error or Clock Slip Enabled
96 Data Framing Overrun Enabled
97 Data Framing Under run Enabled
98 Remote Unit Found Enabled
99 Module Hardware Failure Enabled
100 Remote Unit Lost Enabled
101 Remote Unit Error Detected Enabled
102 Remote Unit Good Detected Enabled
103 External Clock Source Lost Enabled
104 Serial Session Started Enabled
105 Serial Session Stopped Enabled
106 SFP is consuming too much power Enabled
107 Remote Test Activation Enabled
108 Remote Test Deactivation Enabled
109 Local Test Activation Enabled
110 Local Test Deactivation Enabled
111 SSH Authentication Failure Enabled
112 SSH Session Started Enabled
113 SSH Session Stopped Enabled
114 File Corruption Enabled
115 Protection Switch Enabled
76.01FP33/2-A Page 128 5/17

116 Protection Config Mismatch Enabled

117 Fan Rotation Not Detected Enabled
118 Fan Rotation High Threshold Enabled
119 FPGA Failure Enabled
120 Fan Rotation Normal Enabled
121 Unknown trap Enabled
130 AIS State Change detected Enabled
131 LCK State Change detected Enabled
132 Performance Threshold Crossing Enabled
134 TDM Clock Status Change Enabled
135 TDM Incorrect Ethernet frame count Enabled
136 XFP RX CDR Loss of Lock Enabled
137 XFP TX CDR Loss of Lock Enabled
138 DPOE warning Enabled
139 DPOE failure Enabled
140 XFP RX CDR Gained Lock Enabled
141 XFP TX CDR Gained Lock Enabled
142 Module Normal Temperature Enabled
143 Module Normal Voltage Range Enabled
144 Module Normal Data Detected Enabled
145 802.3AH Remote Link Normal Enabled
146 802.3AH Local Link Normal Enabled
147 XFP/SFP Normal Enabled
148 PoE PD Status Change Enabled
149 Y.1731 probe priority change Enabled
150 FTP Authentication Fail Enabled
151 ACL Access Denied Enabled
152 Link OAM Discovery Complete Enabled
153 Link OAM Discovery Lost Enabled
154 Service Activation Test Initiated Enabled
155 Service Activation Test Completed Enabled
156 Utilization Threshold Violation Enabled
157 Utilization Threshold Normal Enabled
SNMP UDP Trap Port Number = 162
7090>
76.01FP33/2-A Page 129 5/17

To view the trap log, use the traps -log command.
7090> traps -log

Chass/Slot Code Date/Time Trap Type / Module Identifier
================================================================================
01/01 0 01/01/2000 06:51:36 AM 21: TELNET session started
01/01 0 01/01/2000 06:06:09 AM 22: TELNET session stopped
01/01 2 01/01/2000 05:46:00 AM 132: Performance Threshold Crossing
7090>
To clear the trap log, use the traps -log -clear command.
5.1.40 Firmware Version (VER)
The ver command provides the ability to display the firmware version currently running on the 7090-01.
A list of options is displayed when the ver -h command is entered.
7090> ver -h
Description: Displays the firmware version

Format: ver [-h | -s] [-ver]
Switches:
-s display version information
-ver verbose help
7090>
The options available using the ver command are shown below.
specific command.
The -s switch displays the firmware version on the 7090-01.
To display the firmware version on the 7090-01, use the ver -s command.
7090> ver -s
Model Number: 81.73S-7301A-R6

Firmware: v1.0.xx January 24 2017, 14:11:43 caps(0x0 mtype 147)
(ER-7) prodRev(10) hwRev(10)
FPGA: v0.xx 01/24/2017 12:02:00
7090>
76.01FP33/2-A Page 130 5/17

5.1.41 Time Zone (ZONE)

The zone command displays the list of time zone values.
To display the time zone values, use the zone -h command from the CLI prompt.
7090> zone -h
Zone Full name Location Time Adjustment
===============================================================================
GMT Greenwich Mean Time Europe UTC
UTC Coordinated Universal Time Europe UTC
WET Western European Time Europe UTC
Z Zulu Time Zone Military UTC
N November Time Zone Military UTC - 01 hour
O Oscar Time Zone Military UTC - 02 hours
HAT Heure Avancée de Terre-Neuve N America UTC - 02:30 hours
NDT Newfoundland Daylight Time N America UTC - 02:30 hours
ADT Atlantic Daylight Time N America UTC - 03 hours
HAA Heure Avancée de l’Atlantique N America UTC - 03 hours
P Papa Time Zone Military UTC - 03 hours
HNT Heure Normale de Terre-Neuve N America UTC - 03:30 hours
NST Newfoundland Standard Time N America UTC - 03:30 hours
AST Atlantic Standard Time N America UTC - 04 hours
EDT Eastern Daylight Time N America UTC - 04 hours
HAE Heure Avancée de l’Est N America UTC - 04 hours
HNA Heure Normale de l’Atlantique N America UTC - 04 hours
Q Quebec Time Zone Military UTC - 04 hours
EST Eastern Standard Time N America UTC - 05 hours
CDT Central Daylight Time N America UTC - 05 hours
HAC Heure Avancée du Centre N America UTC - 05 hours
HNE Heure Normale de l’Est N America UTC - 05 hours
R Romeo Time Zone Military UTC - 05 hours
MDT Mountain Daylight Time N America UTC - 06 hours
CST Central Standard Time N America UTC - 06 hours
HAR Heure Avancée des Rocheuses N America UTC - 06 hours
HNC Heure Normale du Centre N America UTC - 06 hours
S Sierra Time Zone Military UTC - 06 hours
PDT Pacific Daylight Time N America UTC - 07 hours
HAP Heure Avancée du Pacifique N America UTC - 07 hours
HNR Heure Normale des Rocheuses N America UTC - 07 hours
MST Mountain Standard Time N America UTC - 07 hours
T Tango Time Zone Military UTC - 07 hours
PST Pacific Standard Time N America UTC - 08 hours
AKDT Alaska Daylight Time N America UTC - 08 hours
HAY Heure Avancée du Yukon N America UTC - 08 hours
HNP Heure Normale du Pacifique N America UTC - 08 hours
U Uniform Time Zone Military UTC - 08 hours
Only a partial list is shown.
76.01FP33/2-A Page 131 5/17

6.0 SPECIFICATIONS
Coriant 7090-01 CE
Description
1000BASE-X Network Interface Device
MSA SFF-8472
IEEE 802.1ag
Standard Compliances ITU-T Y.1564, 1731
RFC 2544, 5357
MEF 21, 30, 31
Regulatory Compliances* UL, cUL, FCC Class A, NEBS 3, RoHS2, REACH, WEEE
Management Telnet, SNMPv1, SNMPv2c, SNMPv3
Frame Size 10,240 bytes
1000BASE-LX (LC)
Port Type FIber:
1000BASE-EX (LC)
Cable Type Fiber: Single-mode: 9/125um
DC Input: < 1.5watts @ 3.3VDC (81.73S-7301A-R6)
DC Power Requirements
(SFP Receptacle) < 1.6watts @ 3.3VDC (81.73S-7301B-R6)
Operating Case
-40 to 85° C
Temperature
Storage
-40 to 85° C
Temperature
W: 0.53” x D: 2.69” x H: 0.33”
Dimensions
L: 13.46mm x B: 68.33mm x H: 8.38mm
Weight 0.736 oz. (21g)
Humidity 5% to 95% (non-condensing)
Altitude -100m to 4,000m (operational)
* Pending
Spec. Min Max Min Max Link

Model Fiber Wavelength Attenuation
Distance Tx Power Tx Power Rx Power Rx Power Budget
Number Type (nm) (dB)
(km) (dBm) (dBm) (dBm) (dBm) (dB)
81.73S-7301A-R6 SM/DF 10 1310 -9.5 -3.0 -21.0 -3.0 0 11.5
81.73S-7301B-R6 SM/DF 34 1310 -5.0 0 -24 -3.0 3 19
76.01FP33/2-A Page 132 5/17

7.0 APPENDIX A: NETWORK TOPOLOGY CONFIGURATIONS COMMANDS

7.1 7090-01 - LOCATION A
The following are the configurations used in this user manual.
## =======================================================================
## == 7090-01 - Location A 10.0.0.230
## =======================================================================
##
evc -dis
evc -dall
##
evc -a -e Data -p 1,2 -v 1000
evc -a -e Mgt -p 1,2,mgt1 -v 2000
##
interface -a -p 1 -t uni -e Data:100 -e Mgt:*
interface -a -p 2 -t uni -e Data:100
interface -a -p mgt1 -t uni -e Mgt:*
##
evc -ena
##
cfm -dis all
##
mde -a -l 7
md -a -n MD4 -l 4
ma -a -n MD4 -o MA4 -e Data -p 2
mep -a -n MD4 -o MA4 -e Data -p 2 -m 230 -up
rmep -a -n MD4 -o MA4 -m 231
##
cfm -ena all
##
save
76.01FP33/2-A Page 133 5/17

## =======================================================================
## == 7090-01 - Location A 10.0.0.230
## =======================================================================
##
## 1731 Configuration
##
probe -g -bt 5 -bin 1,2,3,4,10
probe -ena
##
## DMM/DMR probe
##
probe -a -p 2 -ty 1 -n MD4 -o MA4 -m 231
##
## LMM/LMR probe
##
probe -a -p 2 -ty 3 -n MD4 -o MA4 -m 231
save
##
## =======================================================================
## == 7090-01 - Location A 10.0.0.230
## =======================================================================
##
## RFC 2544 Throughput
##
testinit -a -p 2 -pe 1 -v 100 -e Data -pn Test -typ throughput -fst
##
##
##
76.01FP33/2-A Page 134 5/17

7.2 7090-01 - LOCATION B

## =======================================================================
## == 7090-01 - Location B 10.0.0.231
## =======================================================================
##
evc -dis
evc -dall
##
evc -a -e Data -p 1,2 -v 1000
evc -a -e Mgt -p 1,2,mgt1 -v 2000
##
interface -a -p 1 -t uni -e Data:100 -e Mgt:*
interface -a -p 2 -t uni -e Data:100
interface -a -p mgt1 -t uni -e Mgt:*
##
evc -ena
##
cfm -dis all
##
mde -a -l 7
md -a -n MD4 -l 4
ma -a -n MD4 -o MA4 -e Data -p 2
mep -a -n MD4 -o MA4 -e Data -p 2 -m 231 -up
rmep -a -n MD4 -o MA4 -m 230
##
cfm -ena all
##
save
##
## =======================================================================
## == 7090-01 - Location B 10.0.0.231
## =======================================================================
##
## 1731 Configuration
##
probe -g -bt 5 -bin 1,2,3,4,10
probe -ena
save
##
##
## =======================================================================
## == 7090-01 - Location B 110.0.0.231
## =======================================================================
##
## RFC 2544 Throughput
##
testresp -a -p 2 -pe 1 -v 100 -e Data -pn Test
##
76.01FP33/2-A Page 135 5/17

8.0 APPENDIX B: FIRMWARE AND FPGA CODE UPDATE

8.1 OVERVIEW
Appendix B describes the procedure for updating the firmware and FPGA code on the 7090-01.
8.2 SAVE CURRENT SETTINGS
Under normal circumstances the current configuration of the 7090-01 will carry forward to the new version
during the update, however, extreme events such as a power outage can lead to settings being lost. Prior to
upgrading the 7090-01, it is recommended that the settings be recorded. The settings can be viewed using
the Command Line Interface (CLI) over Telnet.
8.3 COPY THE FILES TO YOUR HARD DRIVE
The files should be copied to a convenient location on the hard drive of the workstation. The name
of the firmware file is similar to sfp-app-vx.x.x.bin. The name of the FPGA code file is similar to
YYYYMMDDxxxx-xx.dat. The ‘x’s represent the release revision of the firmware.
Depending on the operating system of the workstation and/or FTP installation, the name of the files
may need to be renamed to the “DOS 8.3 Format”. Rename the sfp-app-vx.x.x.bin to sfp.bin and
YYYYMMDDxxxx-xx.dat to fpga.dat and store the files in the root or c:\ directory.
Renaming the files to sfp.bin and fpga.dat will allow the new files to overwrite the old files, saving memory
allocation space on the module.
8.4 RECOVERING THE 7090-01
In the event the IP address of the 7090-01 is unknown or management access has been locked out due to an
incorrect configuration, the 7090-01 will revert to its factory default IP address for 60 seconds after a power
cycle. Using the factory default IP address, Telnet to the 7090-01. Login with the current username and
password. Once logged in, restore the 7090-01 to factory defaults using the restore -r factory command.
8.5 UPDATE THE 7090-01
The files can be updated using FTP. When updating both the firmware and FPGA code, always upgrade
the FPGA first, then activate the FPGA code, then upgrade the firmware.
8.5.1 Updating the Firmware and FPGA Code Using FTP
FTP can be used to update the firmware and FPGA code over a network. Verify the following parameters:
• IP Protocol is turned On and the module has a valid IP Address
• FTP Protocol turned On and a password has been configured
Verify the 7090-01 can be accessed via Telnet using the known IP address.
7090> ip -s
MAC address: 00-06-87-02-17-58
IP 1
IP address: 10.0.0.1
Subnet mask: 255.255.255.0
Gateway address: 10.0.0.254
DHCP Disabled
7090>
76.01FP33/2-A Page 136 5/17

To enable FTP and configure a password, use the protocol command.
7090> protocol -ftp ena -ftppw <pw>

7090> protocol -s
Telnet protocol: enabled (active, IP = 10.0.0.100, mgt1)

Telnet password: *****
FTP protocol: enabled
FTP password: *****
SNMPv1/v2c agent: enabled
SNMPv3 agent: enabled
Keep alive: disabled, interval=10s
7090>
8.5.1.1 Update the FPGA Code

To update the FPGA, open a DOS command window and enter the following commands. Bold lettering
indicates information to be entered.
> ftp 10.0.0.1 (Enter the module’s IP address)
331 User admin OK. Password required
Password: <enter ftp password> (from the protocol command configuration )
230 User logged in
ftp> quote tfs on
200 TFS Enabled
ftp> dir
200 OK.
150 Opening ASCII mode data connection for file list.
-r--r--r-- 1 user group 11926 01/01/2000 modelscfg.ini
-r--r--r-- 1 user group 2 01/01/2000 ag24hr.dat
-r--r--r-- 1 user group 1170 01/01/2000 snmp.key
-r--r--r-- 1 user group 11926 01/01/2000 modelscfgold.ini
-r--r--r-- 1 user group 2818080 01/01/2000 fpga.dat
-rw-rw-rw- 1 user group 1768 01/01/2000 traplog.txt
226 Transfer Complete.
ftp: 402 bytes received in 0.01Seconds 26.80Kbytes/sec.
ftp> del fpga.dat (delete old files)
226 Delete command successful
76.01FP33/2-A Page 137 5/17

ftp> put <location and filename of the FPGA code> fpga.dat

200 OK
150 Ready to take file
226 Saving file to flash...closing session
221 Goodbye
The FPGA code has been transferred to flash memory.
NOTE: Even though the file has been transferred via FTP, the file needs to be saved to flash. This
process could take up to 1 minute to complete, so the FTP process may appear to be inoperable until
the file has been saved. The file transfer process is completed when the 221 Goodbye message has
been received.
Do not remove power during the upgrade procedure until the FTP process has terminated.
After the FPGA code has been transferred via FTP, the FPGA code will need to be activated. Open a Telnet
session and use the dir -s command to verify the FPGA code has been transferred to flash.
7090> dir -s
Size Name
==============================
65506 modelscfg.ini
2 ag24hr.dat
1170 snmp.key
2883616 FPGA.dat
2496 ag7day.dat
7090>
Once the FPGA code has been transferred, use the fpgaupd command to finish the update process.
The filename of the FPGA code when using the fpgaupd command must be the same as the filename used
during the FTP process. Once the FPGA has been restarted, the Telnet session will be dropped.
7090> fpgaupd -w fpga.dat -act

Don’t remove power until programming is completed.
FPGA programming process started...

FPGA programming 2818048 bytes to device..............
FPGA programming successful
Verifying 2818048 bytes from device
FPGA programming process complete.
FPGA restarting
NOTE: Do not remove power during the upgrade procedure until the module has completed the
activation sequence and the FPGA has restarted.
76.01FP33/2-A Page 138 5/17

Use the ver command to verify the upgrade.
7090> ver -s

Firmware: v1.0.xx Dec 19 2016, 14:27:51 caps(0x0 mtype 147)
prodRev(10) hwRev(2) appAP(2)
FPGA: v0.xx 01/24/2017 11:27:00
7090>
8.5.1.2 Update the Firmware

FTP the application firmware to the 7090-01.
> ftp 10.0.0.1 (Enter the module’s IP address)
Password: <enter ftp password>
230 User logged in
ftp> put <location and filename of the application firmware> sfp.bin
200 OK
226 Management module firmware update in process.....closing session
Connection closed by remote host
When the file transfer is complete, the 7090-01 verifies the file, programs the flash memory and automatically
restarts with the newly loaded firmware.
NOTE: Do not remove power during the upgrade procedure until the 7090-01 has completed the
activation sequence and has restarted. Verify the 7090-01 has restarted by pinging the IP address
of the 7090-01. When the 7090-01 starts responding to the pings, the upgrade procedure has been
completed.
After the firmware has been transferred via FTP, verify the upgrade. Open a Telnet session and use the ver
command to verify the upgrade.
7090> ver -s

Firmware: v1.0.xx Dec 19 2016, 14:27:51 caps(0x0 mtype 147)
prodRev(10) hwRev(2) appAP(2)
FPGA: v0.xx 01/24/2017 11:27:00
7090>
76.01FP33/2-A Page 139 5/17

9.0 REPLACEMENT AND AFTER-SALE TECHNICAL SUPPORT

9.1 For information about Coriant services and to contact the Technical Assistance Center (TAC), refer to the
Coriant website at http://www.coriant.com/services_support.
9.2 If equipment is suspected of being defective, complete any applicable troubleshooting procedures to
troubleshoot the suspected equipment. Refer to **REFERENCE 7090 DOCUMENT** to replace faulted or
non-faulted equipment.
• If substitute equipment operates correctly, the original equipment should be considered defective and
returned to Coriant.
• If normal troubleshooting procedures do not solve the problem, contact Coriant Technical Assistance
Center.
9.3 Coriant will repair or replace Coriant products provided that the need for this repair or replacement arises from
the ordinary use of the products as intended by the manufacturer or otherwise stated in Coriant literature.
9.4 For more information about in-warranty and out-of-warranty repairs and returns, contact Coriant Customer
Service at http://www.coriant.com/services_support.
9.5 Contact the Coriant Technical Assistance Center to return a product for repair or replacement. When you
ship the product, you must use a Return Material Authorization (RMA) number for tracking purposes.
9.6 Coriant strongly recommends that no internal (component-level) testing or repairs be attempted on the
equipment. Unauthorized testing or repairs may void the warranty. Also, if the equipment is part of a
registered system, unauthorized repairs result in noncompliance with Parts 15 and/or 68 of the FCC Rules
and Regulations.
9.7 Although repair service always includes an attempt to remove any permanent markings made by customers
on Coriant products, the success of such attempts cannot be guaranteed. Therefore, if equipment must be
marked defective or bad, Coriant recommends that it be done with non-permanent materials and, where
appropriate, in a manner consistent with the correct handling of electrostatically sensitive devices.
76.01FP33/2-A Page 140 5/17

7090-01 CE Ethernet SFP NID User Manual 76.01FP33/2-A

Uploaded by

Copyright:

Available Formats

You might also like

7090-01 CE Ethernet SFP NID User Manual 76.01FP33/2-A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7090-01 CE Ethernet SFP NID User Manual 76.01FP33/2-A

Uploaded by

Copyright:

Available Formats

7090-01 CE Ethernet SFP NID User Manual

Industry Canada interference-causing equipment regulations require that you be

Pico™, SILVX®, SILVX INSIGHT®, SILVXMANAGER®, SILVXOSS®, SILVXSOURCE®, SMARTCORE®,

TELLABS™, TITAN®, YOUR NETWORKING PARTNER®, XIEON NETWORKS™

Any other company or product names may be trademarks of their respective

76.01FP33/2-A Page 2 5/17

2.0 Installation, Verification and Configuration......................................................................12

3.0 Network Application Example..........................................................................................14

76.01FP33/2-A Page 3 5/17

3.1.6 RFC 2544............................................................................................................................................... 30

4.0 Hardware Overview.........................................................................................................33

5.0 Command Line Interface.................................................................................................34

76.01FP33/2-A Page 4 5/17

7.0 Appendix A: Network Topology Configurations Commands.........................................133

8.0 Appendix B: Firmware and FPGA Code Update .........................................................136

9.0 Replacement and After-Sale Technical Support............................................................140

76.01FP33/2-A Page 5 5/17

7090-01 CE Ethernet SFP NID

76.01FP33/2-A Page 6 5/17

1.2.1.5 Class of Service

1.2.2.2 Maintenance Association (MA)

76.01FP33/2-A Page 7 5/17

1.2.2.4 Maintenance End Point (MEP)

76.01FP33/2-A Page 8 5/17

1.2.4 ITU-T Y.1731 Performance Monitoring

1.2.5 RFC 2544 Service Activation Testing

76.01FP33/2-A Page 9 5/17

Frame Up MEP Up MEP Up MEP

76.01FP33/2-A Page 10 5/17

1.2.7 RFC-5357 Two-Way Active Measurement Protocol (TWAMP)

76.01FP33/2-A Page 11 5/17

2.0 INSTALLATION, VERIFICATION AND CONFIGURATION

2.3 CONFIGURING THE 7090-01

76.01FP33/2-A Page 12 5/17

Coriant 7090-01 CE FP3.3

Please enter the password >

76.01FP33/2-A Page 13 5/17

3.0 NETWORK APPLICATION EXAMPLE

76.01FP33/2-A Page 14 5/17

76.01FP33/2-A Page 15 5/17

3.1 7090-01 REQUIREMENTS

CLI Command Description

> ip -addr 10.0.0.231 IP address configuration

See Section 5.1.11 for additional information on the ip command.

76.01FP33/2-A Page 16 5/17

7090-01 - Location A and B

> evc -a -e Data -p 1,2 -v 1000

> interface -a -p 1 -t uni -e Data:100 -e Mgt:* Associate EVC to the port,

The following is an explanation of the commands used above:

3.1.2 IEEE 802.1ag Connectivity Fault Management

76.01FP33/2-A Page 17 5/17

The following is an explanation of the commands used above:

76.01FP33/2-A Page 18 5/17

3.1.3 7090-01 Configuration File

3.1.3.2 Load the Configuration File

> protocol -ftp ena -ftppw *****

76.01FP33/2-A Page 19 5/17

Total: 6 items listed (2835822 bytes)