Académique Documents
Professionnel Documents
Culture Documents
OPERATION MANUAL
ETX-1
Ethernet Demarcation Switch
Version 1.2
ETX-1
Ethernet Demarcation Switch
Version 1.2
International Headquarters
RAD Data Communications Ltd.
Front Matter
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the ETX-1 to be delivered hereunder shall be
free of defects in material and workmanship under normal use and service for a period of twelve
(12) months following the date of shipment to DISTRIBUTOR.
If, during the warranty period, any component part of the equipment becomes defective by
reason of material or workmanship, and DISTRIBUTOR immediately notifies RAD of such defect,
RAD shall have the option to choose the appropriate corrective action: a) supply a replacement
part, or b) request return of equipment to its plant for repair, or c) perform necessary repair at
the equipment's location. In the event that RAD requests the return of equipment, each party
shall pay one-way shipping costs.
RAD shall be released from all obligations under its warranty in the event that the equipment has
been subjected to misuse, neglect, accident or improper installation, or if repairs or
modifications were made by persons other than RAD's own authorized service personnel, unless
such repairs by others were made with the written consent of RAD.
The above warranty is in lieu of all other warranties, expressed or implied. There are no
warranties which extend beyond the face hereof, including, but not limited to, warranties of
merchantability and fitness for a particular purpose, and in no event shall RAD be liable for
consequential damages.
RAD shall not be liable to any person for any special or indirect damages, including, but not
limited to, lost profits from any cause whatsoever arising from or in any way connected with the
manufacture, sale, handling, repair, maintenance or use of the ETX-1, and in no event shall
RAD's liability exceed the purchase price of the ETX-1.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to ETX-1 and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the ETX-1 are provided "as is" and without warranty of any kind. RAD
disclaims all warranties including the implied warranties of merchantability and fitness for a
particular purpose. RAD shall not be liable for any loss of use, interruption of business or
indirect, special, incidental or consequential damages of any kind. In spite of the above RAD
shall do its best to provide error-free software products and shall offer free Software updates
during the warranty period under this Agreement.
RAD's cumulative liability to you or any other party for any loss or damages resulting from any
claims, demands, or actions arising out of or relating to this Agreement and the ETX-1 shall not
exceed the sum paid to RAD for the purchase of the ETX-1. In no event shall RAD be liable for
any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if RAD
has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of
Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste
equipment in protecting the environment, the owner of this RAD product is
required to refrain from disposing of this product as unsorted municipal waste at
the end of its life cycle. Upon termination of the units use, customers should
provide for its collection for reuse, recycling or other form of environmentally
conscientious disposal.
ii
Front Matter
Safety Symbols
Warning
Danger of electric shock! Avoid any contact with the marked surface while
the product is energized or connected to outdoor telecommunication lines.
Warning
Some products may be equipped with a laser diode. In such cases, a label
with the laser class and other warnings as applicable will be attached near
the optical transmitter. The laser warning symbol may be also attached.
Please observe the following precautions:
Before turning on the equipment, make sure that the fiber optic cable is
intact and is connected to the transmitter.
The use of optical devices with the equipment will increase eye hazard.
iii
Front Matter
Connecting AC Mains
Make sure that the electrical installation complies with local codes.
Always connect the AC plug to a wall socket with a protective ground.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Always connect the power cord first to the equipment and then to the wall socket. If a power
switch is provided in the equipment, set it to the OFF position. If the power cord cannot be
readily disconnected in case of emergency, make sure that a readily accessible circuit breaker or
emergency switch is installed in the building installation.
In cases when the power distribution system is IT type, the switch must disconnect both poles
simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference
to the ground. Any single pole can be externally grounded.
Due to the high current capability of DC power systems, care should be taken when connecting
the DC supply to avoid short-circuits and fire hazards.
Make sure that the DC power supply is electrically isolated from any AC source and that the
installation complies with the local codes.
iv
Front Matter
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate
the circuit breaker of the panel board that services the equipment and switch it to the OFF
position. When connecting the DC supply wires, first connect the ground wire to the
corresponding terminal, then the positive pole and last the negative pole. Switch the circuit
breaker back to the ON position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated
in the building installation.
If the DC power supply is floating, the switch must disconnect both poles simultaneously.
Ports
Safety Status
SELV
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance
of a qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables.
Do not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
Front Matter
When using shielded or coaxial cables, verify that there is a good ground connection at both
ends. The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk,
there are restrictions on the diameter of wires in the telecom cables, between the equipment
and the mating connectors.
Caution
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication
line cords.
Attention
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In
such cases, a notice will be given in the installation instructions.
Do not attempt to tamper with any carrier-provided equipment or connection hardware.
vi
Front Matter
Avertissement
Achtung
vii
Front Matter
Franais
Symboles de scurit
Ce symbole peut apparaitre sur l'quipement ou dans le texte. Il indique des
risques potentiels de scurit pour l'oprateur ou le personnel de service,
quant l'opration du produit ou sa maintenance.
Avertissement
viii
Avertissement
Front Matter
Certains produits peuvent tre quips d'une diode laser. Dans de tels cas,
une tiquette indiquant la classe laser ainsi que d'autres avertissements, le
cas chant, sera jointe prs du transmetteur optique. Le symbole
d'avertissement laser peut aussi tre joint.
Veuillez observer les prcautions suivantes :
ix
Franais
Front Matter
Franais
Connexion d'alimentation CC
Sauf s'il en est autrement spcifi dans le manuel, l'entre CC de l'quipement est flottante par
rapport la mise la terre. Tout ple doit tre mis la terre en externe.
A cause de la capacit de courant des systmes alimentation CC, des prcautions devraient
tre prises lors de la connexion de l'alimentation CC pour viter des courts-circuits et des risques
d'incendie.
Assurez-vous que l'alimentation CC est isole de toute source de courant CA (secteur) et que
l'installation est conforme la rglementation locale.
La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de
court-circuit dpassant 35A (40A aux Etats-Unis et Canada).
Avant la connexion des cbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'quipement et fixez-le
en position OFF. Lors de la connexion de cbles d'alimentation CC, connectez d'abord le
conducteur de mise la terre la borne correspondante, puis le ple positif et en dernier, le
ple ngatif. Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapt et approuv devrait tre intgr l'installation du
btiment.
Le disjoncteur devrait dconnecter simultanment les deux ples si l'alimentation en courant CC
est flottante.
Glossary
Address
Agent
Front Matter
ANSI
APS (Automatic
protection switching)
AWG
Backhaul
Balanced
Bandwidth
Baud
Best Effort
Bipolar
Bit
Bridge
A device interconnecting local area networks at the OSI data link layer,
filtering and forwarding frames according to media access control
(MAC) addresses.
Buffer
Bus
Byte
Carrier
CESoPSN
Channel
CIR (Committed
xi
Front Matter
Information Rate)
Circuit Emulation
Service
New technology for offering circuit emulation services over packetswitched networks. The service offers traditional TDM trunking (at n x
64 kbps, fractional E1/T1, E1/T1 or E3/T3) over a range of transport
protocols, including Internet Protocol (IP), MPLS and Ethernet.
CLI
Clock
Congestion
Congestion Control
Data
Diagnostics
Digital
E1 Line
E3
Encapsulation
EIR
Ethernet
A local area network (LAN) technology which has extended into the
wide area networks. Ethernet operates at many speeds, including data
rates of 10 Mbps (Ethernet), 100 Mbps (Fast Ethernet), 1,000 Mbps
(Gigabit Ethernet), 10 Gbps, 40 Gbps, and 100 Gbps.
Ethernet OAM
xii
Front Matter
Ethertype
Flow
Flow Control
Frame
Framing
At the physical and data link layers of the OSI model, bits are fit into
units called frames. Frames contain source and destination
information, flags to designate the start and end of the frame, plus
information about the integrity of the frame. All other information,
such as network protocols and the actual payload of data, is
encapsulated in a packet, which is encapsulated in the frame.
Full Duplex
G.703
Gateway
Impedance
Interface
IP Address
J1
Jitter
L2CP
Laser
Latency
The time between initiating a request for data and the beginning of
the actual data transfer. Network latency is the delay introduced
xiii
Front Matter
Loading
Loopback
Manager
Mark
Master Clock
The source of timing signals (or the signals themselves) that all
network stations use for synchronization.
Modular
Multiplexer
Network
Node
NodeB
NTP
Packet
Parameters
Parameters are often called arguments, and the two words are used
interchangeably. However, some computer languages such as C define
argument to mean actual parameter (i.e., the value), and parameter
to mean formal parameter. In RAD CLI, parameter means formal
parameter, not value.
xiv
Front Matter
Physical Layer
Policing
A method for verifying that the incoming traffic complies with the
users service contract.
Polling
See Multidrop.
Port
Prioritization
Also called CoS (class of service), classifies traffic into categories such
as high, medium, and low. The lower the priority, the more drop
eligible is a packet. When the network gets busy, prioritization
ensures critical or high-rated traffic is passed first, and packets from
the lowest categories may be dropped.
Prompt
Protocol
Pseudowire
Queuing
Q-in-Q
See MAC-in-MAC.
RADIUS (Remote
Authentication Dial-In
User Service)
Router
Routing
The process of selecting the most efficient circuit path for a message.
Scalable
xv
Front Matter
SAToP
SONET (Synchronous
Optical Network)
Space
SVI
A logical port used for binding flows to bridge ports, router interfaces
or Layer-2 TDM pseudowires
Sync
Syslog
T1
T3
Telnet
Throughput
Timeslot
Traffic Management
xvi
Front Matter
Traffic Shaping
A method for smoothing the bursty traffic rate that might arrive on an
access virtual circuit so as to present a more uniform traffic rate on
the network.
Trunk
VLAN-Aware
A device that is doing the Layer 2 bridging according to the VLAN tag
in addition to the standard bridging parameters. A VLAN-aware device
will not strip or add any VLAN header.
VLAN Stacking
A technique that lets carriers offer multiple virtual LANs over a single
circuit. In essence, the carrier creates an Ethernet virtual private
network to tunnel customer VLANs across its WAN; this helps avoid
name conflicts among customers of service providers who connect to
the carrier. Stacking works by assigning two VLAN IDs to each frame
header. One is a "backbone" VLAN ID used by the service provider; the
other one has up to 4,096 unique 802.1Q VLAN tags.
Zero suppression
xvii
1.
Notes
purchased.
Lock the wire latch of each SFP module by lifting it up until it clicks into place.
Connecting to a Terminal
2.
Baud Rate:
9,600 bps
Data bits:
Parity:
None
Stop bits:
Flow control:
None.
3. If you are using HyperTerminal, set the terminal mode to 132-column mode
for optimal view of system menus (Properties> Settings> Terminal Setup>
132 column mode).
4. Power-up ETX-1.
5. ETX-1 boots up. When the startup process is completed, you are prompted to
press <ENTER> to receive the login prompt.
6. Press <ENTER> until you receive the login prompt.
7. To log in, enter your user name (su for full configuration and monitoring
access) and your password.
8. The device prompt appears:
ETX-1#
You can now type the necessary CLI commands.
Configuring SVI
SVI 1 must be administratively enabled in order to administratively enable the
corresponding flows and router interface.
configure flows
# Classifier-profile to allow untagged traffic
classifier-profile untagged match-any match untagged
# Classifier-profile to allow all traffic
classifier-profile all match-any match all
# Flow from management Ethernet port to SVI 1
flow mng_in
classifier untagged
no policer
ingress-port ethernet 101
egress-port svi 1 queue 1
no shutdown
exit
# Flow from SVI 1 to management Ethernet port
flow mng_out
classifier all
ingress-port svi 1
egress-port ethernet 101 queue 0 block 0/1
no shutdown
exit all
Configuring Router
The router must be configured with a router interface that is bound to the SVI
used for the management flows, and assigned an IP address. In addition, a static
route must be set up for the default gateway.
This section illustrates the following configuration:
Bound to SVI 1
Router interface 1:
configure router 1
interface 1
bind svi 1
# IP address 192.168.99.238 with mask 255.255.255.0
address 192.168.99.238/24
no shutdown
exit
# Default gateway 192.168.99.1
static-route 0.0.0.0/0 address 192.168.99.1
exit all
3.
Saving Configuration
Type save in any level to save your configuration in startup-config.
exit all
file copy startup-config user-default-config
Are you sure? [yes/no] _ yes
Contents
Introduction ............................................................................................................................ 1-1
1.1
1.2
1.3
1.4
1.5
2.6
2.7
2.8
3.4
3.5
Table of Contents
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
Table of Contents
6.2
7.2
7.3
iii
Table of Contents
8.2
8.3
8.4
8.5
iv
8.6
Table of Contents
Table of Contents
vi
Table of Contents
vii
Table of Contents
viii
Chapter 1
Introduction
1.1
Overview
ETX-1 is a carrier Ethernet demarcation device owned and operated by the service
provider and installed at the customer premises, which delivers SLA-based
Ethernet business services to the customer premises over native Ethernet access.
It serves as a clear demarcation point between the user and operator networks.
Incoming customer traffic is classified and mapped according to port-based
(all-to-one) bundling, or by user port and CE VLAN-ID, VLAN priority, DSCP, IP
precedence, MAC, IP address, and Ethertype. This offers operators the flexibility
to differentiate services using different kinds of classification methods, police the
traffic, and enforce SLA per service.
ETX-1 supports powerful bandwidth profiles such as CIR/CBS for differentiated
Ethernet services and includes comprehensive Ethernet OAM (Operation,
Administration, and Maintenance) functionality together with SLA monitoring.
The network ports support configurable static LAG link aggregation. At the
physical layer, ETX-1 supports auto-negotiation and fault propagation.
The unit can be managed via a local terminal port, or via a dedicated out-of-band
Ethernet port. Additionally, ETX-1 can be managed inband, via a user or network
port.
Product Options
The basic port type is Fast Ethernet, which can be optionally increased to Gigabit
Ethernet.
Applications
ETX-1 delivers Ethernet services as defined by the MEF standards.
ETX-1
Packet
Switched
Network
CPE
ETX-1
CPE
Overview
1-1
Chapter 1 Introduction
ETX-1
PSN
ETX-2
CPE
ETX-1
CPE
Features
Service Types
ETX-1 provides port-based and flow-based services.
Port-Based Service
In a typical port-based (all-to-one bundling) application ETX-1 receives different
services via different network ports (Figure 1-3). This method achieves clearer
service separation, it does not require any marking for CoS, and provides
straightforward SLA measurement.
Customer Premises
Provider Node
PE
Packet
Switched Network
(ETH, IP or MPLS)
Ethernet
Aggregator
GbE
ETX-1
FE
VoIP
FE
Premium
Data
FE
Best Effort
Data
Flow-Based Service
In a typical flow-based application different services are assigned to different
Ethernet flows received by the same network port (Figure 1-4). This provides a
cheaper, more scalable solution, with the possibility of mixing different types of
service.
1-2
Overview
Chapter 1 Introduction
Provider Node
PE
Customer Premises
Ethernet
Aggregator
Packet
Switched Network
(ETH, IP or MPLS)
VoIP
Premium
Data
Best Effort
Data
ETX-1
Flow Classification
The ingress user traffic is mapped to the Ethernet flows using the following list of
per-port classification criteria. In the classifications, VLAN refers to the service
provider (outer) VLAN, previously referred to as SP-VLAN, while inner VLAN refers
to the Customer Entity VLAN, previously referred to as CE-VLAN.
vlan
p-bit
ip-precedence
ip-dscp
src-mac/ dst-mac
src-ip/ dst-ip
ether-type
untagged
non-ip
all
vlan + inner-vlan
vlan + p-bit
vlan + ip-dscp
vlan + src-mac/dst-mac
vlan + src-ip/dst-ip
vlan + ether-type
vlan + non-ip
Overview
1-3
Chapter 1 Introduction
vlan + ip-precedence
Add (push) outer VLAN with a p-bit value. When you add a new VLAN, the
original outer VLAN becomes the inner VLAN.
Remove (pop) outer VLAN and p-bit. When you remove a VLAN, the inner
VLAN becomes the outer VLAN.
Only certain combinations of actions on the outer and inner VLAN are allowed.
Refer to Chapter 8 for details on the permitted combinations of actions.
Traffic Prioritization
Once traffic is classified to a flow, it can be mapped to Strict (Strict Priority)
queues or WRR (Weighted Round Robin):
1-4
Strict: Strict Priority strictly complies with the priority sequence from high to
low, and it sends packets in the high-priority queue first. When that queue is
empty, strict priority begins to send packets in lower priority queue. By
putting the key service packets in the high priority queues, you can ensure
that they can always be served first. At the same time, the common service
packets can be put in the low priority queues and transmitted when there are
no key service packets waiting for transmission.
Overview
Chapter 1 Introduction
Ethernet OAM
ETX-1 provides OAM to monitor and troubleshoot an Ethernet network and
quickly detect failures:
CFM OAM (End-to-end OAM) based on IEEE 802.1ag and Y.1731 for continuity
check, non-intrusive loopback, and Frame loss, frame delay and frame delay
variation measurement.
EFM OAM (Link OAM) according to IEEE 802.3-2005 (formerly IEEE 802.3ah)
for remote management and fault indication, including dying gasp, and MIB
parameter retrieval.
Link Aggregation
ETX-1 supports static link aggregation (LAG) without the LACP protocol according
to 802.3-2005.
Note
ETX-1 supports only one ring protection for network port 1 and 2.
L2CP Handling
ETX-1 can be configured to pass through Layer-2 control frames (including other
vendors L2CP frames) across the network, to peer-supported protocols
(IEEE 802.3-2005), or to discard L2CP frames.
Fault Propagation
The unit provides the following types of fault propagation:
Overview
1-5
Chapter 1 Introduction
Management
ETX-1 can be managed as follows:
Security
To ensure client-server communication privacy and correct user authentication,
ETX-1 supports the following security protocols:
SSH
SNMPv3
SFTP
Syslog
The syslog protocol is a client/server-type protocol, featuring a standard for
forwarding log messages in an IP network. It supports up to four syslog servers. A
syslog sender sends a small text message of less than 1024 bytes to the syslog
server. Syslog messages are sent via UDP in cleartext.
SFTP
SFTP (Secure File Transfer Protocol) is supported, to provide secure encrypted file
transfer using SSH.
Statistics Collection
ETX-1 collects performance statistics for the physical layers of the network/user
ports, and Radius.
1-6
Overview
Chapter 1 Introduction
Diagnostic Tools
ETX-1 offers several types of diagnostic procedures:
Trace route Quickly trace a route from ETX-1 to any other network device
Loopback tests:
1.2
Layer-1 loopback performed at the PHY of the physical ports. When the
loopback is active the data forwarded to a port is looped from the Tx
path to the Rx path, thereby disrupting the traffic. This loopback cannot
pass through Ethernet bridges.
1.3
Physical Description
Physical Description
1-7
Chapter 1 Introduction
ETX-1 OAM is compatible with other RAD products that support standard OAM
functionality.
ETX-1
1-8
Processing Stage
Description
Classiffier
Flow Engine
Flow Policer
Queue Manage
Egress Queue
Flow Editing
Functional Description
1.5
Network Interface
Chapter 1 Introduction
Technical Specifications
Number of Ports
Type
Electrical Operation
Mode
Number of Ports
Type
Electrical Operation
Mode
Standards
Compliance
IEEE
Ethernet Flows
Number of Flows
32
Management
Local
Inband
Out-of-band
External AC
Input: 100-240VAC
User Interface
Power
(Plastic Enclosure)
Power
Output: 12VDC
Power Consumption
6W max
Internal AC
Power Consumption
6W max
Height
42 mm (1.7 in)
Width
Depth
Weight
(Metal Enclosure)
Physical
(Plastic Enclosure)
Technical Specifications
1-9
Chapter 1 Introduction
Physical
Height
45 mm (1.8 in)
Width
Depth
Weight
Temperature
Humidity
Up to 90%, non-condensing
(Metal Enclosure)
Environment
1-10
Technical Specifications
Chapter 2
Installation and Setup
This chapter describes installation and setup procedures for the ETX-1 unit.
After installing the unit, refer to Chapter 3 for operating instructions and
Chapter 4 for management instructions.
If a problem is encountered, refer to Chapter 11 for test and diagnostic
instructions.
Internal settings, adjustment, maintenance, and repairs may be performed only
by a skilled technician who is aware of the hazards involved.
Warning
2.1
2.2
Package Contents
Package Contents
2-1
2.3
For rack mounting instructions, refer to the associated installation kit manual
For wall mounting instructions, refer to the drilling template at the end of
this manual.
Prerequisites.
2.4
Warning
Note
2-2
Caution Insert the SFP gently. Using force can damage the connecting pins.
4. Remove the protective rubber caps from the SFP modules.
Caution Do not remove the SFP while the fiber optic cables are still connected. This may
result in physical damage (such as a chipped SFP module clip or socket), or cause
malfunction (e.g., the network port redundancy switching may be interrupted)
2.5
Connect ETX-1 to the Ethernet equipment using a standard fiber optic cable
terminated with an LC connector.
2-3
2.6
2.7
Warning
Connecting to Power
2-4
Connecting to Power
Connecting to AC Power
AC power should be supplied via a 1.5 m (5 ft) standard power cable terminated
by a standard 3-prong socket. A cable is provided with the unit.
External AC Power:
AC power is supplied with the external AC power adapter provided with the unit.
To connect AC power:
1. Connect the power adapter output cable to the power connector on the
ETX-1 rear panel.
2. Connect the power adapter to the main outlet.
The unit turns on automatically upon connection to the mains.
Internal AC Power:
To connect AC power:
1. Connect the power cable to the power connector on the ETX-1 rear panel.
2. Connect the power cable to the main outlet.
The unit turns on automatically once connected to the mains.
2.8
To connect to an NMS:
Note
To provide protection against surges, use shielded cables when connecting to the
MNG-ETH port.
2-5
2-6
Chapter 3
Operation
This chapter provides the following information:
A detailed description of the front panel controls and indicators, and their
functions.
3.1
To turn on ETX-1:
3.2
Indicators
The unit's LEDs are located on the front panel (see Figure 3-1). Table 3-1 lists the
functions of the ETX-1 LED indicators.
ETX-1
Color
Function
PWR/TST/ALM
Green/red
ON (green) Power is ON
ON (red) There is at least one active alarm
Blinking Diagnostic loopback is active
Indicators
3-1
Chapter 3 Operation
Name
Color
NET 1
Green
Function
ON Corresponding Ethernet link is OK
Blinking Data is being transmitted or received on the corresponding
Ethernet link
NET/ USER 2
Green
USER
3,4,5,6
Green
MNG-ETH
Green
Note
The number of network and user ports and their corresponding LEDs depends on
the hardware configuration.
3.3 Startup
Configuration Files
The following files contain configuration settings:
Loading Sequence
At startup, the device attempts to load configuration files in the following
sequence until a valid one is found:
3-2
Startup
startup-config
rollback-config
user-default-config
factory-default-config.
Chapter 3 Operation
If an error is encountered while loading a file, the default is to ignore the error
and continue loading. You can use the on-configuration-error command to
change this behavior, either to stop loading the file and go to the next
configuration file, or to reject the file and reboot.
To display the parameter values after startup, use the command info
[detail].
Note
3.5
3-3
Chapter 3 Operation
3-4
Chapter 4
Management and Security
This chapter describes the following:
Management Flows
Management-related features.
4.1
Manager
Location
Transport Method
Management
Protocol
Application
CONTROL
Local
Out-of-band
RS-232
MNG-ETH
Local, remote
Out-of-band
Telnet, SSH
SNMP
Local, remote
Inband
Telnet, SSH
SNMP
4-1
Note
By default, the terminal, Telnet (SSH), and SNMP management access methods
are enabled. Refer to the section on Controlling Management Access for details
on enabling/disabling a particular method.
4.2
ETX-1 has a V.24/RS-232 control port based on mini-USB connector. The control
port continuously monitors the incoming data stream and immediately responds
to any input string received through this port. You can use any terminal
emulation program to manage ETX-1 via the control port; the following procedure
uses HyperTerminal.
4-2
4-3
7. Select a PC COM port to be used to communicate with ETX-1, and click <OK>.
The COM Properties dialog box is displayed.
Data bits: 8
Parity: None
Stop bits: 1
Note
4-4
4-5
Login
To prevent unauthorized modification of the operating parameters, ETX-1
supports two access levels:
Note
Superuser can perform all the activities supported by the ETX-1 management
facility, including defining new users.
User access rights (full control or read only) are defined by the superuser.
Users are not allowed to create new users.
4-6
Superuser allows you to configure all parameters of ETX-1 and to change the su
and user passwords.
To enter as user:
1. Enter user as user name and press <Enter>.
2. Enter 1234 as password and press <Enter>.
The base prompt ETX-1# appears.
Note
To use show commands without navigating, type show followed by the level
name(s) and the rest of the show command.
In the following example, the levels and command were typed together and
therefore no navigation was performed, so the prompt has not changed.
ETX-1#
ETX-1# configure port ethernet 1 loopback local
ETX-1# show configure port ethernet 1 loopback
Loopback : Local
Forever
ETX-1#
4-7
In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
ETX-1#
ETX-1# configure
ETX-1>config# port
ETX-1>config>port# ethernet 1
ETX-1>config>port>eth(1)# loopback local
ETX-1>config>port>eth(1)# show loopback
Loopback : Local
Forever
ETX-1>config>port>eth(1)#
ETX-1#
ETX-1# configure flows flow flow1
ETX-1>config>flows>flow(flow1)$ ingress-port ethernet 3
ETX-1>config>flows>flow(flow1)$ egress-port ethernet 1 queue 0 block 0/1
ETX-1>config>flows>flow(flow1)$ classifier Classifier1
ETX-1>config>flows>flow(flow1)$ no shutdown
ETX-1>config>flows>flow(flow1)$ exit
ETX-1>config>flows#
[]
<>
4-8
<Tab>
Command autocomplete
<Backspace>
Deletes character
<Ctrl-C>
<Ctrl-Z>
<Ctrl-E>
Exit CLI
Command Tree
At the CLI root, the following categories are available:
configure
file
admin
global-commands.
Description
configure
bridge
aging-time
clear-mac-table
filtering
port
accept-frame-type
clear-statistics
ingress-filtering
name
Port name
pvid
4-9
Command
Description
queue-mapping
show bind
spanning-tree
| admin-edge
| auto-edge
| cost
| mcheck
| priority
| shutdown
| show status
static-mac
vlan
name
VLAN name
tagged-egress
untagged-egress
vlan-aware
spanning-tree
forward-time
hello-time
max-age
mode
priority
tx-hold-count
show status
show mac-address-table
show vlans
chassis
show environment
temperature-threshold
4-10
Command
Description
fault
cfm
service
| frames-report
| shutdown
fault-propagation
action-on-group
trigger
wait-to-restore
flows
classifier-profile
flow
Configure flow
classifier
drop
egress-port
ingress-port
mark
inner-p-bit
inner-vlan
p-bit
vlan
policer
shutdown
vlan-tag
show summary
management
access
auth-policy
sftp
snmp
ssh
match
4-11
Command
Description
telnet
tftp
radius
clear-statistics
server
address
auth-port
key
retry
shutdown
timeout
show statistics
show status
snmp
access-group
context-match
notify-view
read-view
shutdown
write-view
community
name
sec-name
shutdown
Activate or deactivate
tag
notify
bind
shutdown
tag
notify-filter
mask
shutdown
4-12
type
notify-filter-profile
profile-name
shutdown
security-to-group
group-name
shutdown
snmp-engine-id
target
address
shutdown
tag-list
target-params
trap-sync-group
target-params
message-processing-model
security
shutdown
version
trap-sync-group
tag-list
target-params
user
authentication
privacy
shutdown
view
mask
shutdown
Activate or deactivate
type
4-13
Command
Description
show snmpv3
show trap-sync
tacacsplus
TACACS+ parameters
group
server
accounting-port
authentication-port
clear-statistics
group
key
retry
shutdown
timeout
show statistics
user
Create/delete user
show users
Display users
oam
cfm
maintenance-domain
maintenance-association
ccm-interval
classification
mep
ais
bind
ccm-initiate
ccm-priority
classification
client-md-level
4-14
accounting
dest-addr-type
dest-mac-addr
direction
Define direction
lbm
linktrace
queue
remote-mep
service
classification
clear-statistics
delay-threshold
delay-var-threshold
dest-ne
Configure destination NE
clear-statistics
delay
loss
pm-collection
Enable/disable PM collection
remote
show statistics
dmm-interval
lmm-interval
pm-collection
Enable/disable PM collection
shutdown
show statistics
shutdown
show lbm-results
show linktrace-results
show status
name
4-15
md-level
mip
bind
flow
shutdown
show status
name
mip-assign
show mips
show summary
efm
port
ethernet
auto-negotiation
clear-efm-statistics
clear-statistics
efm
loopback
Define loopback
snmp-tunneling
egress-mtu
flow-control
Flow control
l2cp
loopback
max-capability
name
pm-collection
Enable/disable PM collection
queue-group
shutdown
speed-duplex
4-16
descriptor
Command
Description
tag-ethernet-type
functional-mode
show loopback
show oam-efm
show oam-efm-statistics
show statistics
show status
l2cp-profile
lag
admin-key
bind
distribution-method
shutdown
show bind
show status
svi
name
shutdown
show summary
protection
erp
backward-compatibility
bridge
clear
clear-statistics
data-vlan
east-port
force-switch
manual-switch
port-type
mac
Configure LAG
4-17
Command
Description
r-aps
revertive
shutdown
timers
wait-to-restore
west-port
show statistics
show status
qos
cos-map-profile
policer-profile
bandwidth
compensation
queue-block-profile
queue
Define queue
depth
scheduling
shaper
queue-group-profile
queue-block
name
profile
shaper
queue-map-profile
shaper-profile
reporting
acknowledge
Acknowledge alarms
active-alarm-rebuild
alarm-input
4-18
map
map
bandwidth
Command
Description
alarm-source-attribute
alarm-source-type-attribute
clear-alarm-log
mask-minimum-severity
pm
pm-collection
show active-alarms
show active-alarms-details
show alarm-information
show alarm-input
show alarm-list
show alarm-log
show brief-alarm-log
show brief-log
show event-information
show event-list
show log
router
clear-arp-table
dhcp-client
host-name
vendor-class-id
interface
address
bind
dhcp
4-19
Command
Description
dhcp-client
management-access
mtu
name
shutdown
show status
name
static-route
show arp-table
show interface-table
show routing-table
system
clear-cpu-utilization
contact
date-and-time
date-format
date
sntp
broadcast
poll-interval
server
address
prefer
query-server
shutdown
udp
show status
time
zone
interval-duration
inventory
4-20
client-id
alias
Command
Description
asset-id
serial-number
show status
location
name
syslog
address
clear-statistics
facility
port
severity-level
shutdown
show statistics
show buffers
show cpu-utilization
show date-and-time
show device-information
show summary-inventory
terminal
baud-rate
length
4-21
Command
Description
timeout
Description
file
delete
dir
show configuration-files
show copy
show factory-default-config
show rollback-config
show startup-config
show sw-pack
show user-default-config
Description
admin
Administrative commands
factory-default-all
factory-default
reboot
software
install
software-confirm-required
undo-install
show status
startup-confirm-required
user-default
4-22
Description
global-commands
copy
echo
exec
exit
help
history
info
level-info
logout
ping
save
trace-route
tree
4.3
The Telnet host is typically a PC or Unix station with the appropriate suite of
TCP/IP protocols.
To enable the Telnet host to communicate with ETX-1, the ETX-1 IP address
settings must be configured (refer to Router section in Chapter 8 for details).
This is usually done via a terminal emulation program (see Working with
Terminal). After this preliminary configuration, you can use a Telnet host
connected directly or via a local area network.
4-23
4.4
4.5
4-24
Viewing device inventory and receiving traps (see Chapter 11 for trap list)
IANAifType-MIB
IEEE8023-LAG-MIB
MEF-R MIB
4.6
The ETX-1 management software allows you to assign a name and description to
the unit, specify its location to distinguish it from the other devices installed in
your system, and assign a contact person.
Task
Command
Comments
name <name-of-device>
4-25
Task
Command
Comments
Specifying location
contact
<contact-person>
Displaying device
information, MAC address,
and amount of time device
has been running
show device-information
[refresh [<sec>]]
Location floor-8
Contact Engineer-1.
:
:
:
:
:
:
4.7
Standards
The supported SNMP versions are based on the following standards:
4-26
RFC 1908, Coexistence between Version 1 and Version 2 of the Internetstandard Network Management Framework. SNMPv2 Working Group.
RFC 2272, message processing and dispatching for the Simple Network
Management Protocol (SNMP).
RFC 2274, User-Based Security Model (USM) for version 3 of the Simple
Network Management Protocol (SNMPv3).
RFC 2275, View-Based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP).
Benefits
The SNMP protocol allows you to remotely manage multiple units from a central
workstation using a network management system.
The SNMPv3 protocol allows data to be collected securely from SNMP devices.
Confidential information such as SNMP commands can thus be encrypted to
prevent unauthorized parties from accessing them.
Functional Description
In an SNMP configuration, one or more administrative computers manage a group
of hosts or devices. Each managed system continuously executes a software
component called agent, which sends reports via SNMP to the managing
workstations.
Factory Defaults
The following is the default configuration of the SNMP parameters (refer to
Setting SNMP Parameters for explanations of the parameters):
ETX-1 Ver. 1.2
4-27
4-28
User: initial
Write view =
Read view =
Write view =
Write view =
Read view =
Write view =
to configure SNMPv3:
1. Set SNMP engine ID if necessary
2. Add users, specifying authentication protocol and privacy protocol
3. Add groups, specifying security level, protocol and view
4. Connect users to groups
5. Add notification entries with assigned traps and tags
6. Configure target parameter sets to be used for targets
7. Configure targets (SNMPv3 network management stations to which ETX-1
should send trap notifications), specifying target parameter sets and
notification tags, and trap synchronization groups if applicable
4-29
Note
When you enter password parameters, they should contain at least eight
characters.
Task
Command
Level
Comments
Setting SNMP
engine ID, as MAC
address or IP
address or string
snmp
user <security-name>
[md5-auth [{des | aes128 | none}] ]
snmp
user <security-name>
[sha-auth [{des | aes128 | none}] ]
snmp>user
no authentication disables
authentication protocol.
snmp>user
Administratively
enabling user
no shutdown
snmp>user
Configuring group
4-30
snmp
no access-group <groupname>
{snmpv1|snmpv2c|usm} {noauth-no-priv| auth-nopriv|auth-priv} deletes the
group
Task
Command
Level
Comments
Defining how to
match the context
sent in frames by
the NMS
snmp>access-group
read-view <name>
snmp>access-group
write-view <name>
snmp> access-group
notify-view <name>
snmp> access-group
Administratively
enabling group
no shutdown
snmp> access-group
Configuring
community
community <community-index>
snmp
Configuring name
name <community-string>
snmp>community
Configuring security
name
sec-name <sec-name>
snmp>community
Configuring
transport tag
tag <transport-tag>
snmp>community
Administratively
enabling community
no shutdown
snmp>community
shutdown disables
community.
Configuring
notification
notify <notify-name>
snmp
no notify <notify-name>
cancels the notification
configuration.
Assigning trap to
notification
bind {trap-list}
snmp>notify
Assigning tag to
notification, to be
used to identify the
notification entry
when configuring
target
tag <argument>
snmp>notify
Administratively
enabling
notification
no shutdown
snmp>notify
4-31
Task
Command
Level
Comments
Configuring
notification filter to
define access to a
particular part of
the MIB hierarchy
for trap variables
snmp
mask [<mask>]
snmp>notify-filter
Defining whether
traps with trap
variables belonging
to the MIB subtree
are sent
snmp>notify-filter
Administratively
enabling
notification filter
no shutdown
snmp>notify-filter
Configuring
notification filter
profile
notify-filter-profile <params-name>
snmp
params-name Specifies
the target parameter set to
associate with the profile
Configuring
notification filter
profile name
profile-name <argument>
snmp>filter-profile
argument Specifies
notification filter to
associate with the profile
Administratively
enabling
notification filter
profile
no shutdown
snmp>filter-profile
Connecting security
name to group (e.g.
connecting user or
community to
group)
snmp
Specifying group to
which to connect
security name
group-name <group-name>
snmp>security-to-group
4-32
Task
Command
Level
Comments
Administratively
enabling
security-to-group
entity
no shutdown
snmp>security-to-group
Configuring set of
target parameters
target-params <name>
snmp
no target-params <name>
removes target parameters.
Specifying message
processing model
(SNMP version) to
be used when
generating SNMP
messages for the
set of target
parameters
message-processing-model
{snmpv1 | snmpv2c | snmpv3}
snmp>target-params
Specifying SNMP
version to be used
when generating
SNMP messages for
the set of target
parameters
snmp> target-params
Specifying user on
whose behalf SNMP
messages are to be
generated for the
set of target
parameters
snmp> target-params
Administratively
enabling target
parameters
no shutdown
snmp> target-params
Configuring target
target <name>
snmp
Specifying set of
target parameters
for target
target-params <params-name>
snmp>target
Assigning tag(s) to
target
tag-list <list>
snmp>target
Specifying target
address as IP
address or OAM
port
snmp>target
4-33
Task
Command
Level
Comments
Specifying trap
synchronization
group
snmp>target
Enter no trap-sync-group
to remove the manager
from the group. If the
manager was the last in
the group, the group is
deleted.
Administratively
enabling target
no shutdown
snmp>target
Configuring target
parameters and
tags for trap
synchronization
group
trap-sync-group <group-id>
snmp
tag-list <list>
snmp>trap-sync-group
Specifying set of
target parameters
target-params <params-name>
snmp>trap-sync-group
Defining access to a
particular part of
the MIB hierarchy
snmp
4-34
mask <mask>
snmp>view
Task
Command
Level
Comments
Defining whether
access to the MIB
subtree is allowed
snmp>view
Administratively
enabling view
no shutdown
snmp>view
Displaying trap
synchronization
groups and
members for
SNMPv3 manager
groups
snmp
Displaying SNMPv3
information, such
as the number of
times the SNMPv3
engine has booted,
and how long since
the last boot
snmp
Example
4-35
To create notifications:
4-36
Tag = Port
Tag = Power
version USM
User MD5_priv
Tag list =
IP address 192.5.4.3.
Port, Power
To create communities, target parameters, and target for devices in network that
are working with SNMPv2c :
Community read:
Name: public
4-37
4-38
Community write:
Name: private
Community trap:
Name: public
Version SNMPv2c
IP address 192.5.6.7.
4-39
4.8
You can enable or disable access to the ETX-1 management system via Telnet, SSH,
or SNMP applications. By disabling Telnet, SSH, or SNMP, you prevent unauthorized
access to the system when security of the ETX-1 IP address has been
compromised. When Telnet, SSH, and SNMP are disabled, ETX-1 can be managed
via an ASCII terminal only. Additionally, you can enable or disable access via
SFTP/TFTP.
Factory Defaults
By default, access is enabled for all the applications.
Task
Command
Comments
telnet
4-40
Task
Command
Comments
ssh
snmp
sftp
tftp
4.9
Factory Defaults
By default, authentication is via the locally stored database (1st-level local)
Task
Command
Comments
4-41
Task
Command
Comments
Devices using ERP and RSTP: management flow must be configured through
the bridge (bridge port 7)
Devices not using ERP and RSTP: management flow is configured through a
physical interface (ETH-1, ETH-2)
To configure management flows for ETX-1 not using ERP and RSTP:
1. Configure the Classifier Profiles:
4-42
Management Flows
Management Flows
4-43
flow mn_in
classifier v4
ingress-port bridge-port 7
egress-port svi 1 queue 5
vlan-tag pop vlan
no shutdown
exit
flow mn_out
classifier untagged
ingress-port svi 1
egress-port bridge-port 7
vlan-tag push vlan 4 p-bit fixed 7
no shutdown
exit all
4. Configure the router:
configure router 1 interface 1
bind svi 1
address 192.168.100.142/24
no shutdown
exit all
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS)
RFC 2618, RADIUS Authentication Client MIB
Benefits
The RADIUS protocol allows centralized authentication and access control,
eliminating the need to maintain a local user data base on each device on the
network.
Functional Description
When a login attempt occurs at ETX-1, it submits an authentication request to
the RADIUS server. The RADIUS server checks the database and replies with either
Access Rejected or Access Accepted.
4-44
Factory Defaults
By default, four RADIUS servers are defined, they are configured as shown below.
Description
Default Value
IP address of server
0.0.0.0
3 seconds
1812
Task
Command
Comments
address <ip-address>
retry <number-of-retries>
Range 010
timeout <seconds>
Range 15
auth-port <udp-port-number>
Range 165535
no shutdown
shutdown administratively
disables the server.
Displaying status
show status
Example
4-45
Key: RAD_server1.
4-46
Standards
RFC 1492, An Access Control Protocol, Sometimes Called TACACS
Benefits
The TACACS+ protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device on the
network. The TACACS+ server encrypts the entire body of the packet but leaves a
standard TACACS+ header.
Functional Description
When a login attempt occurs at ETX-1, it submits an authentication request to
the TACACS+ server, which checks the database and then grants or refuses
access.
Factory Defaults
By default, no TACACS+ servers are defined. When a TACACS+ server is first
defined, it is configured as shown below.
Description
Default Value
5 seconds
49
49
4-47
Description
Default Value
Administratively enabled
Disabled (shutdown)
Note
If you intend to use TACACS+ for authentication, verify that TACACS+ is selected
as level-1 authentication method (see Defining Access Policy).
To define TACACS+ servers:
1. At the config>mngmnt>tacacsplus# prompt, type server <ip-address> to
specify the server IP address.
The config>mngmnt>tacacsplus>server(<ip-address>)# prompt is
displayed.
2. Enter the necessary commands according to the tasks listed below.
Task
Command
Comments
accounting-port <port-number>
Range 165535
authentication-port <port-number>
Range 165535
group <group-name>
timeout <seconds>
Range 110
no shutdown
shutdown administratively
disables the server.
Clearing statistics
clear-statistics
Displaying statistics
show statistics
4-48
Key: TAC_server1.
To display statistics:
Note
You can enter any combination of shell, system, and commands, but you must
enter at least one of them.
3. Type exit to return to the TACACS+ level.
The config>mngmnt>tacacsplus# prompt is displayed.
4. Type server <ip-address> to select the TACACS+ server to which to bind the
group.
The config>mngmnt>tacacsplus>server(<ip-address>)# prompt is
displayed.
4-49
Factory Defaults
By default, data rate is set to 9,600 bps.
4-50
Task
Command
Comments
timeout forever
length <number-of-rows>
Notes
User passwords are stored in a database so that the system can perform
arbitrary block of data and returns a fixed-size bit string, the (cryptographic)
hash value, such that any change to the data changes the hash value.
Factory Defaults
By default, the following users exist, with default password 1234:
su
tech
user
oper
4-51
User password = hash of 4222 (user staff2 can log in with password 4222).
4-52
ETX-1>config>mngmnt# logout
exiting cli
ETX-1>config>mngmnt#
CLI session is closed
user>staff2
password>****
4-53
4-54
Chapter 5 Services
Chapter 5
Services
ETX-1 provides flow-based and port-based services. This section shows the
configuration steps for both.
Note
5.1
In Figure 5-1 the gray rectangles illustrate the data flow for Ethernet traffic. The
blue rounded rectangles indicate the functions that need to be configured,
numbered according to the sequence of configuration. Table 5-1 shows the
configuration steps in sequence.
Step
Commands
Comments
classifier-profile
match
2
Configuring Policer
Profiles
policer-profile
Configuring Flows
mark
bandwidth
vlan
inner-vlan
p-bit
inner-p-bit
5-1
Chapter 5 Services
Sequence
Step
Commands
Comments
queue-block-profile
scheduling
depth
Configuring Flows
classifier
ingress-port
egress-port
policer
mark
vlan-tag
shutdown
6
Configuring Shaper
Profiles
shaper-profile
Ethernet Ports
name
bandwidth
auto-negotiation
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
5.2
VLAN
membership
1) CoS mapping
3) VLAN
Queueing
level 0
4) Queue group
Egress
port
Shaping
5) Shaping
6) Ethernet port
2) Bridge port
Step
Commands
Comments
cos-map-profile
map
5-2
Chapter 5 Services
Sequence
Step
Commands
Comments
accept-frame-type
ingress-filtering
name
pvid
cos-mapping
3
name
tagged-egress
untagged-egress
4
queue-group-profile
queue-block
name
profile
shaper
5
Configuring Shaper
Profiles
shaper-profile
Ethernet Ports
name
bandwidth
auto-negotiation
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
5-3
Chapter 5 Services
5-4
Chapter 6
Ports
This chapter describes port-related features:
Ethernet Ports
6.1
Ethernet Ports
ETX-1 has up to two fiber optic or copper Fast Ethernet network ports and up to
four copper Fast Ethernet user ports.
The second network port can be configured as a user port. The following table
shows how to refer to the ports when configuring them with CLI commands.
Port in CLI
Net
Ethernet 1
Net/User
Ethernet 2
User
Ethernet 3
User
Ethernet 4
User
Ethernet 5
User
Ethernet 6
MNG-ETH
Ethernet 101
Port name
Auto-negotiation
Administrative status
Flow control
6-1
Chapter 6 Ports
Note
Link OAM EFM (IEEE 802.3-2005) Refer to OAM EFM (not relevant for
management Ethernet port)
ETX-1 supports SFP, but fiber optical interface needs to disable auto-negotiation
when using MiTop and MIRICI.
Task
Command
Comments
name <string>
Enabling autonegotiation
auto-negotiation
no auto-negotiation disables
autonegotiation
max-capability {10-full-duplex |
100-full-duplex | 1000-full-duplex}
speed-duplex {10-full-duplex |
100-full-duplex | 1000-full-duplex}
flow-control
tag-ethernet-type <ether-type>
6-2
Ethernet Ports
Chapter 6 Ports
Task
Command
Comments
queue-group profile
<queue -profile-name>
egress-mtu <size>
no shutdown
Note
When you change the functional mode, all flows related to the port are deleted.
The port must be administratively disabled before you can change the functional
mode.
Ethernet Ports
6-3
Chapter 6 Ports
To change the second network interface functional mode to user port, configure
the following:
Summary information showing the status and speed of all Ethernet ports
6-4
Ethernet Ports
Chapter 6 Ports
:
:
:
:
:
Up
Down
SFP In
Complete
00-20-D2-50-00-D6
SFP
----------------------------------------------------------------------------Connector Type
: LC
Manufacturer Name
: EOPTOLINK INC
Manufacturer part number
: EOLS131210DRAD
Typical Maximum Range (Meter) : 10000
Wave Length (nm)
: 1310 Laser
Fiber Type
: SM
RX Power (dBm)
TX Power (dBm)
: -36.9 dBm
: -5.0 dBm
Network
Interface
User
Interface
ETX-203A
ETX-36
Ethernet Ports
6-5
Chapter 6 Ports
Network
Interface
User
Interface
ETX-203A
ETX-1
6-6
Ethernet Ports
Chapter 6 Ports
Example
:
:
:
:
:
0
0
0
0
0
64 Octets
65-127 Octets
128-255 Octets
256-511 Octets
512-1023 Octets
1024-1518 Octets
1519-Max Octets
:
:
:
:
:
:
:
0
0
0
0
0
0
0
--0
0
0
0
0
0
0
0
SFP
----------------------------------------------------------------------------Minimum
Maximum
RX Power (dBm)
: -36.9 dBm
-36.9 dBm
TX Power (dBm)
: -5.1 dBm
-5.0 dBm
Laser Bias (mA)
: 5.7 mA
6.1 mA
Laser Temperature (Celsius) : 42.0 C
51.0 C
Power Supply (V)
: 3.2 V
3.2 V
ETX-1>config>port>eth(1)#
Description
Ethernet Ports
6-7
Chapter 6 Ports
Parameter
Description
Total Frames
Total Octets
Total Frames/Sec
Total Bits/Sec
Minimum Bits/Sec
Maximum Bits/Sec
Unicast Frames
Multicast Frames
Broadcast Frames
Error Frames
Dropped Frames
CRC Errors
CRC Errors/Sec
Number of frames per second received that are an integral number of octets
in length, but do not pass the Frame Check Sequence (FCS) check. This count
does not include frames received with Frame-Too-Long or Frame-Too-Short
error.
Oversize Frames
64 Octets
65127 Octets
128255 Octets
256511 Octets
5121023 Octets
10241518 Octets
1519Max Octets
Clearing Statistics
6-8
Ethernet Ports
6.2
Chapter 6 Ports
Note
ETX-1 can creates up to eight SVIs, but ETX-1 supports up to two valid
management interface (router interfaces).
Task
Command
Comments
name <string>
no name removes
the name
no shutdown
shutdown disables
the SVI
6-9
Chapter 6 Ports
6-10
Chapter 7
Resiliency
7.1
Link Aggregation
Link aggregation (LAG) can be enabled when the second port works in network
mode. The two network ports can form a LAG. After LAG was enabled, both ports
receive traffic at the same time and transmit. Both network ports must be
enabled and they must have the same configuration.
Benefits
ETX-1 can use the load balance to increase the bandwidth.
Functional Description
The two network Ethernet ports can be operated as a single logical interface,
using link aggregation in accordance with IEEE 802.3-2005. The two ports must
be connected to the same switch/router.
Factory Defaults
By default, no LAG is configured.
Configuring LAG
This section explains how to define a link aggregation group (LAG). ETX-1
supports one LAG.
Link Aggregation
7-1
Chapter 7 Resiliency
Task
Command
Comments
admin-key {fast-ethernet |
giga-ethernet}
distribution-method {src-mac | destmac | src-and-dest-mac | src-ip | destip | src-mac-and-ip | src-mac-and-dstip | dst-mac-and-src-ip | dst-mac-andip | src-and-dst-ip | src-dst-mac-andsrc-ip | src-dst-mac-and-dst-ip | srcmac-and-src-dst-ip | dst-mac-and-srcdst-ip| src-dest-mac-ip }
7-2
Link Aggregation
Chapter 7 Resiliency
according to their source and
destination MAC addresses and
source IP addresses
src-dst-mac-and-dst-ip
Packets are distrubuted
according to their source and
destination MAC addresses and
destination IP addresses
src-mac-and-src-dst-ip
Packets are distrubuted
according to their source MAC
addresses and source IP
addresses and destination IP
addresses
dst-mac-and-src-dst-ip
Packets are distrubuted
according to their destination
MAC addresses and source IP
addresses and destination IP
addresses
no shutdown
show bind
show status
Example
To define LAG 1:
ETX-1>config>port# lag 1
ETX-1>config>port>lag(1)$ bind ethernet 1
ETX-1>config>port>lag(1)$ bind ethernet 2
ETX-1>config>port>lag(1)$ no shutdown
ETX-1>config>port>lag(1)$
Link Aggregation
7-3
Chapter 7 Resiliency
7.2
Fault Propagation
Fault propagation enables you to specify which interfaces to shut down if link
failure occurs.
Standards
IEEE 802.1ag, ITU-T Y.1731
Benefits
You can ensure packets are being sent via links that have not failed. Failures are
propagated end-to-end via OAM CFM messages.
Functional Description
Network-to-user fault propagation mechanism on the port and OAM CFM levels:
When fault propagation is enabled, the user port shuts itself down or an OAM
CFM indication of failure is sent when a link failure is detected at the network
port or when an OAM CFM indication of failure is received.
User-to-network fault propagation mechanism on the port and OAM CFM levels:
When fault propagation is enabled, an OAM CFM indication of failure is sent to
Network port once a failure is detected on User port.
You can enable fault propagation to be triggered by failure detection on a
network/user interface, which causes a user-configurable action (such as
deactivation or OAM CFM failure message sent) to be performed on a
user/network interface. You can enable fault propagation in the network-to-user
direction, for a pair of interfaces such as Ethernet ports.
7-4
Fault Propagation
Chapter 7 Resiliency
You can define the following when you enable fault propagation for a pair of
interfaces:
Trigger:
Interface deactivation
Factory Defaults
By default, no fault propagation is configured. When you configure fault
propagation for a particular interface pair, the default configuration is as follows:
Wait-to-restore time = 0.
Specify the wait-to-restore time if you do not want the default value 0.
Fault Propagation
7-5
Chapter 7 Resiliency
To Interface
Command
MEP
Ethernet port
LAG port
Ethernet port
Ethernet port
MEP
LAG port
MEP
MEP
MEP
Ethernet port
Ethernet port
Task
Command
Comments
Specifying the
trigger(s)
7-6
Fault Propagation
Chapter 7 Resiliency
Task
Command
Comments
action-on-group {interface-deactivation |
oam-cfm-if-status-tlv | oam-cfm-ais}
Specifying the
wait-to-restore time
wait-to-restore <seconds>
Example
Trigger: LOS
Trigger: LOS
Fault Propagation
7-7
Chapter 7 Resiliency
7-8
Fault Propagation
Chapter 7 Resiliency
7.3
A G.8032 Layer-2 Ethernet ring is used by ETX-1 for traffic protection. This
technology builds a logical ring, defined as a set of IEEE 802.1-compliant bridges,
and protects against link and node failures. ETX-1 supports only one ring (major)
per shelf.
Standards
ITU-T G.8032-2010
Benefits
G.8032 revertive rings provide sub-50 ms protection for Ethernet traffic and
prevent loops at the Ethernet layer.
Functional Description
Ethernet Ring Protection technology provides scalable solution for low-cost traffic
protection and rapid service restoration, with SDH/SONET-type resilience. It is
built on traditional Ethernet MAC (IEEE 802.3) and bridging (IEEE 802.1) functions.
It is independent of any physical-layer technologies and can be utilized in any
carriers network.
In ERP there is one node designated as RPL, which periodically sends R-APS
messages, defining ring state and operation. When a link failure occurs, it is
detected via LOS. Upon failure, node forwarding information is recalculated to
ensure that data traffic reaches its destination, using alternative path.
Note
Ring Topology
ETX-1 supports single ring topology.
Ring node A
East Port
(RPL Owner)
West Port
(Neighbor)
Ring node D
Ring node B
Ring node C
7-9
Chapter 7 Resiliency
R-APS Messaging
Ethernet ring protection is achieved by means of a dedicated protocol,
Automated Protection Switching (APS). Every ring link is bound by two adjacent
nodes. At any time, traffic flows on all, but one of the ring links. This link is called
the ring protection link (RPL). Under normal conditions this link is blocked. RPL is
controlled by a single node called an RPL owner, which prevents traffic from using
the RPL. When a failure is detected, the RPL owner unblocks the RPL port,
allowing the RPL to be used for traffic. The other Ethernet Ring Node adjacent to
the RPL, the RPL Neighbor Node, may also participate in blocking or unblocking its
end of the RPL.
R-APS messages require a designated transmission channel (R-APS channel),
which is separated from the service traffic channel. An R-APS channel is
configured using a separate dedicated VLAN to enable the R-APS messages to
handled differently from the service traffic. An R-APS channel and service traffic
blocking is performed via VID filtering by the bridge.
Mechanism of Operation
Every failure along the ring triggers an R-APS (SF) (R-APS Signal Fail) message
along both directions from the nodes adjacent to the failed link. Before sending
the R-APS, these nodes block the ports facing the failed link. On receiving these
messages, the RPL owner unblocks the RPL port. An SF message is triggered even
if only one node adjacent to the failed link recognizes the failure.
During a recovery phase, when a failed link is restored and a node detects a Clear
SF continually it sends R-APS (No Request, NR) and keeps the failed port blocked.
When receiving the R-APS (NR), the RPL owner starts its Wait-To-Restore (WTR)
timer. When that timer expires it blocks the RPL port and sends RAPS (NR, RB) (RAPS no request, root blocked) messages along both direction of the ring. Nodes
receiving the R-APS (NR, RB) message flush their learning table, unblock their
blocked ports and return back to idle state.
Timers
The following timers are used to facilitate ERP operation:
Wait-to-Restore (WTR) Period of time used by RPL owner to verify that the
ring has stabilized before blocking the RPL after signal recovery.
Guard Period of time during which all received A-RPS messages are ignored
by the ERP mechanism. This prevents the ring nodes from receiving outdated
A-RPS messages circulating the network.
Hold-off Period of time during which the underlying Ethernet layer attempts
to filter out intermittent link faults before reporting them to the ERP
mechanism.
Administrative Commands
If there is a need to intervene into ERP operation for maintenance or any other
reason, the operator can issue forced or manual switch command.
7-10
Note
Chapter 7 Resiliency
Manual switch command manually blocks a particular ring port with manual
switch command. It can be overridden by SF condition or a force switch
command.
Clear command clear all existing force and manual switch command on the
ERP.
The manual and forced switch are temporary commands and they do not change
the location of the RPL permanently.
Factory Defaults
No Ethernet protection ring is configured in the system by default.
Configuring ERP
To configure ERP:
1. In the configure>protection# prompt, enter erp 1 and ring type (major).
An ERP instance with is created and the config>protection>erp(ringnumber)# prompt is displayed.
2. Configure the ERP as illustrated and explained below.
Note
Task
Command
Comments
backward-compatibility
bridge <1>
data-vlan <14094>
east-port <bridge_port_number>
west-port <bridge_port_number>
7-11
Chapter 7 Resiliency
Task
Command
Comments
revertive
no shutdown
7-12
Chapter 7 Resiliency
Task
Command
Comments
wait-to-restore <seconds>
clear
show status
show statistics
clear statistics
East Port
: 1
Local SF Source
Local SF Source
West Port
: 2
: OK
: OK
7-13
Chapter 7 Resiliency
Description
Example
Figure 7-1 (please refer to In ERP there is one node designated as RPL, which
periodically sends R-APS messages, defining ring state and operation. When a link
failure occurs, it is detected via LOS. Upon failure, node forwarding information is
7-14
Chapter 7 Resiliency
recalculated to ensure that data traffic reaches its destination, using alternative
path.
Note
VLAN 2
BP 1 and BP 2 ingress-filter
BP 1 East port
BP 2 West port
Data VLANs 2
#******************** Configuring_VLAN_Membership****************************
config bridge 1 vlan 2
tagged-egress 3..6
exit
port 1
ingress-filtering
exit
port 2
ingress-filtering
exit all
#************************ Configuring_the_Ring*******************************
config protection erp 1 major
port-type east rpl
port-type west node-port
bridge 1
east-port 1
west-port 2
r-aps vlan 1234 vlan-priority 1 mel 1
data-vlan 2
no shutdown
exit all
2. Ring node B configuration:
ETX-1 Ver. 1.2
7-15
Chapter 7 Resiliency
VLAN 2
BP 1 East port
BP 2 West port
Data VLANs 2
#******************** Configuring_VLAN_Membership****************************
config bridge 1 vlan 2
tagged-egress 3..6
exit
port 1
ingress-filtering
exit
port 2
ingress-filtering
exit all
#************************ Configuring_the_Ring*******************************
config protection erp 1 major
port-type west neighbor
port-type east node-port
bridge 1
east-port 1
west-port 2
r-aps vlan 1234 vlan-priority 1 mel 1
data-vlan 2
no shutdown
exit all
7-16
Chapter 8
Networking
8.1
ETX-1 can be configured to pass through Layer-2 Control frames (including other
vendors L2CP frames) across the network, to peer the supported protocol or to
discard the L2CP frames.
You can create profiles to define the handling of Layer-2 Control Protocol traffic.
You then assign the required profile to an Ethernet port (refer to Configuring
Standards
IEEE 802.3
Benefits
Layer 2 Control Protocol traffic can be passed or filtered to Ethernet virtual
connections.
Factory Defaults
ETX-1 provides a default L2CP profile named L2cpDefaultProfile, configured as
follows:
When a new L2CP profile is created, it has the same configuration as the
L2cpDefaultProfile. You can define up to 5 L2CP profiles in addition to the
L2cpDefaultProfile.
8-1
Chapter 8 Networking
Task
Command
Comments
mac <mac-addr-last-byte-value-list>
{discard | tunnel | peer}
8-2
Chapter 8 Networking
Example
To add L2CP profile named layer2ctrl1 with discard action for hex byte 0x01 and
0x03:
8-3
Chapter 8 Networking
8.2
Ethernet Bridge
Standards
The following standards are supported:
IEEE 802.1ad
IEEE 802.1Q.
IEEE 802.1w
Factory Defaults
The default configuration of the bridge is as follows:
VLAN-aware Enabled
Filtering Enabled
Accept-frame-type All
Spanning-tree
8-4
Path cost 0
Priority 128
Admin-edge false
Auto-edge true
Mcheck false
Spanning-tree
max-age 20
forward-time 15
hello-time 2
priority 32768
tx-hold-count 3
Ethernet Bridge
Chapter 8 Networking
Functional Description
An Ethernet bridge joins two or more LAN (Local Area Network) connections,
thus creating a larger LAN. It is a device that can modulate the traffic passing
between different local area networks.
ETX-1 supports RSTP which can be used to prevent loops in Layer 2 networks and
provides rapid convergence of the spanning tree.
Task
Command
Comments
aging-time <seconds>
filtering
Defining VLAN ID
vlan <vlan-id>
name <string>
tagged-egress <bridge-port-list>
untagged-egress <bridge-port-list>
port <port-number>
Ethernet Bridge
8-5
Chapter 8 Networking
clear-statistics
ingress-filtering
no ingress-tag
Defining the bridge port name
name <port-name>
queue-mapping <profile-name>
Note
To configure RSTP:
1. At the config>bridge(1)>spanning-tree# prompt, enter:
spanning-tree
The config>bridge(1)>spanning-tree# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Defining the
time duration in
listening and
learning states
that precede
the forwarding
state, in
seconds
forward-time <seconds>
8-6
Ethernet Bridge
Chapter 8 Networking
Task
Command
Comments
Defining the
time interval in
seconds
between BPDU
transmissions
hello-time <seconds>
Defining the
maximum age
of the
configuration
BPDU can be
maintained on a
device.
max-age <seconds>
Defining the
operation mode
for spanningtree
mode rstp
Assigning the
bridge priority
value
priority
{0|4096|8192|12288|16384|20480|24576|28672|32768|36864|40960|
Configure the
maximum
number of
BPDUs
transmitted
tx-hold-count
Displaying the
spanning-tree
status
show status
45056|49152|53248|57344|61440}
Task
Command
admin-edge {true|false}
auto-edge {true|false}
cost <number>
Comments
Ethernet Bridge
8-7
Chapter 8 Networking
Task
Command
Comments
mcheck {true|false}
Assigning the
priority value on the
port
priority
{0|16|32|48|64|80|96|112|128|144|160|176|192|208|224|240}
Administratively
enabling the
spanning-tree on
the port
no shutdown
Displaying the
spanning-tree
status on the port
show status
Management Host IP
192.168.100.144
D
ETH 1
ETH 2
ETH 4
Management Host IP
192.168.100.141
NMS
192.168.100.10
ETH 1
ETH 2
Management Host IP
192.168.100.143
ETH 5
C
ETH 2
ETH 1
ETH 6
ETH 2
ETH 1
B
Management Host IP
192.168.100.142
To configure RSTP:
1. Configure device A:
a. Configure the second port to be the user port:
8-8
Ethernet Bridge
Chapter 8 Networking
Ethernet Bridge
8-9
Chapter 8 Networking
configure bridge 1
port 1
spanning-tree
cost 8213818
priority 192
no shutdown
exit
exit
port 2
spanning-tree
cost 12345678
priority 224
no shutdown
exit all
1.
8-10
Ethernet Bridge
Chapter 8 Networking
configure flows
flow mn_in
classifier v4
ingress-port bridge-port 7
egress-port svi 1 queue 5
vlan-tag pop vlan
no shutdown
exit
flow mn_out
classifier untagged
ingress-port svi 1
egress-port bridge-port 7
vlan-tag push vlan 4 p-bit fixed 7
no shutdown
exit all
#******************** Configuring_router **********************************
configure router 1 interface 1
bind svi 1
address 192.168.100.142/24 (please configure the corresponding address for
device C and device D)
no shutdown
exit all
c.
Ethernet Bridge
8-11
Chapter 8 Networking
8-12
Ethernet Bridge
Chapter 8 Networking
priority 48
no shutdown
exit
exit
port 4
spanning-tree
cost 22
priority 0
no shutdown
exit all
Bridge port: 1
Ingress-filtering: Enabled
Accept-frame-type: vlan-only
name BridgePort1
ingress-filtering
accept-frame-type vlan-only
pvid 5 priority 5
exit
To define VLAN:
VLAN ID: 5
name: VLAN5
Ethernet Bridge
8-13
Chapter 8 Networking
name VLAN5
tagged-egress 2..3
untagged-egress 4
exit
VLAN ID : 5
Name
: VLAN5
Tagged Ports
: 2..3
Untagged Ports : 4
ETX-1>config>bridge(1)#
Total MAC Addresses
:
Static MAC Addresses :
Dynamic MAC Addresses :
Ethernet Bridge
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
00-20-D2-34-F0-A9
00-20-D2-35-1B-25
00-20-D2-36-9C-69
00-20-D2-50-17-56
00-24-1D-1D-7E-12
00-24-23-72-7F-0D
00-25-64-9A-C5-92
00-25-64-A3-25-D0
00-25-64-A7-54-91
00-25-64-B7-E8-99
00-25-64-C1-BB-08
00-25-64-C1-BB-EA
00-25-64-C2-34-10
00-25-64-C2-35-41
00-25-64-C2-3F-50
00-26-2D-F0-36-B5
00-30-18-A2-0D-87
00-50-56-E3-48-BB
02-50-56-C0-00-00
08-10-75-15-91-2B
0C-74-C2-ED-8D-97
40-16-9F-E1-CE-0E
44-2A-60-F5-46-EC
58-94-6B-84-C7-0C
5C-26-0A-47-B6-BF
5C-AC-4C-80-14-0F
78-A3-E4-73-D3-8E
7A-7A-C0-A8-D2-FE
8C-7B-9D-79-47-F6
BC-30-5B-AC-B4-AC
BC-30-5B-B6-C0-D9
BC-30-5B-B6-D1-51
BC-30-5B-B6-DC-21
BC-30-5B-B6-DD-C0
BC-30-5B-B6-DF-76
C8-3A-35-CC-F5-1F
C8-3A-35-D4-4A-D8
CC-08-E0-F6-7C-35
E0-05-C5-74-65-67
E0-05-C5-7B-E0-7B
F0-DE-F1-37-EB-EF
Chapter 8 Networking
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Ethernet Bridge
8-15
Chapter 8 Networking
8.3
The ETX-1 Quality of Service (QoS) parameters include the following profiles:
Bandwidth profiles
These profiles can be applied to the traffic flows to ensure the desired flow
prioritization.
Standards
The following standards are supported:
IEEE 802.1p
IEEE 802.1Q.
Benefits
QoS allows you to optimize bandwidth, eliminating the need to ensure the
necessary bandwidth for traffic with different speed and quality requirements.
Factory Defaults
Refer to the following sections for the specific defaults of each type of QoS.
Functional Description
To differentiate traffic, the IEEE 802.1p standard specifies eight classes of service
per user-defined queue map profile. These classes of service are associated with
priority values, from 0 to 7, using the 3-bit user priority field in an IEEE 802.1Q
header added to VLAN-tagged frames within an Ethernet frame header. The way
traffic is handled when assigned a specific priority value is only generally defined
and left to implementation. The general definitions are as follows:
8-16
User Priority
Traffic Type
Best effort
Background
Spare
Excellent effort
Controlled load
Chapter 8 Networking
User Priority
Traffic Type
Video
Voice
Network control
Note
The second port has 6 queues and uses net-profile regardless of being a
network port or a user port.
8-17
Chapter 8 Networking
Factory Defaults
By default, ETX-1 has two CoS mapping profiles, which are configured as follows:
8-18
Chapter 8 Networking
Note
ETX-1 supports only two CoS mapping profiles pbit-profile and dscp-profile.
These profiles cannot be removed, but can be modified.
Example
Bandwidth Profiles
ETX-1 supports the following bandwidth profiles:
You can control the bandwidth utilization by defining the committed information
rate (CIR) and committed burst size (CBS) in shaper and policer profiles.
CIR: Defines the Committed Information Rate for the current profile. The CIR
specifies a bandwidth with committed service guarantee.
CBS: Defines the Committed Burst Size for the current profile. The CBS specifies
the maximum guaranteed burst size.
Compensation: You can specify the amount of bytes that the policer can
compensate for the layer 1 overhead (preamble and IFG) and the overhead for
the added VLAN header in case of stacking.
Factory Defaults
ETX-1 provides default bandwidth profiles, as specified in the following table.
Profile Type
Shaper
Policer
Profile Name
Shaper1
Policer1
cir
1,000,000
1,000,000
cbs
524,288
524,288
compensation
8-19
Chapter 8 Networking
Task
Command
Comments
Example
CBS = 32kbytes
Note
8-20
Chapter 8 Networking
Command
Comments
Specifying the
compensation (bytes)
compensation <063>
Example
Compensation = 56
8-21
Chapter 8 Networking
56
ETX-1>config>qos>policer-profile(Policer4)$
Scheduling method:
In configurations with Strict and WRR queues, the WRR frames are transmitted
only after the transmission of frames associated with the Strict queues is
completed.
Note
If one of the internal queues is configured to WRR, queues with a higher queue ID
cannot be configured to Strict. Shaper per queue or per port cannot be set at the
same time.
Factory Defaults
ETX-1 provides a default queue block profile named DefaultQueue1, which
defines queues 05 as follows:
Depth: 8192
8-22
Chapter 8 Networking
Task
Command
Comments
depth <value>
Example
scheduling strict
depth 1024
exit
scheduling wrr 20
8-23
Chapter 8 Networking
Task
Command
name <block-name>
profile <queue-block-profile-name>
Note
Comments
Normally there is no need for you to enter the bind command. When you add a
queue block in level 0 to the profile, bind is done automatically.
Example
Note
8-24
This example uses the shaper profile and queue block profile created in the
examples in the preceding sections.
To create and configure a queue group profile named QGroupProf1:
Chapter 8 Networking
8.4
Flows
Note
Standards
IEEE 802.3x
Benefits
The user traffic can be classified into different Ethernet flows (EVC.CoS) to
provide services in a flexible manner.
Functional Description
Packets can be classified by means of their VLAN IDs and other criteria, as
specified in Table 8-3.
Flows
8-25
Chapter 8 Networking
Classifications that apply to the same port are allowed only one or one same
combination. NNI indicates ingress network port, UNI indicates ingress user port.
Range
NNI/UNI
vlan
04094
Both
p-bit
07
Both
ip-precedence
07
Both
ip-dscp
063
Both
src-mac
MAC address
Both
MAC address
Both
dst-mac
MAC address
Both
MAC address
Both
src-ip
IP address
Both
IP address
Both
dst-ip
IP address
Both
IP address
Both
ether-type
0x0000-0xffff
Both
untagged
Both
non-ip
Both
all
Both
vlan + inner-vlan
Both
vlan + p-bit
0-4094
Both
0-7
vlan + ip-dscp
0-4094
Both
0-63
vlan + src-mac
0-4094
Both
MAC address
vlan + dst-mac
0-4094
Both
MAC address
vlan + src-ip
0-4094
Both
IP address
8-26
Flows
Chapter 8 Networking
Classification
Range
NNI/UNI
vlan + dst-ip
0-4094
Both
IP address
vlan + ether-type
0-4094
Both
0x0000-0xffff
vlan + non-ip
0-4094
Both
0-4094
Both
IP address
vlan +dst-ip + to-dst-ip
0-4094
Both
IP address
vlan +src-mac + to-src-mac
0-4094
Both
MAC address
vlan +dst-mac + to-dst-mac
0-4094
Both
MAC address
vlan + inner-vlan + p-bit
Both
0-4094
Both
0-7
Flows
8-27
Chapter 8 Networking
Note
The VLAN may be a single value or a range for setting a classification or the same
combination classification. When setting the same combination classification with
VLAN and inner VLAN, the VLAN should be a single value.
The p-bit may be a single value or a range for setting a classification or the same
combination classification. When setting p-bit range, it should contain all values,
the following is valid: p-bit range: 0..7
The ip-precedence may be a single value or a range for setting a classification or
the same combination classification. When setting ip-precedence range, it should
contain all values, the following is valid: ip-precedence range: 0..7
The ip-dscp may be a single value or a range for setting a classification or the
same combination classification. When setting ip-dscp range, it should contain all
values, the following is valid: ip-dscp range: 0..63
If you apply the same combination classification with IP address range, the
following is valid:
1. For IP address range: the starting IP address is X.X.0.0, the end address is
X.X.255.255 or the starting IP address is X.X.X.0, the end address is X.X.X.255
2. The starting address and the end address must be in the same subnet.
For example:
IP address range: 10.10.10.0 10.10.10.255; If you apply the same combination
classification with MAC address range, the following is valid:
1. For MAC address range: the starting MAC address is XX-XX-XX-00-00-00, the
end address is XX-XX-XX-FF-FF-FF or the starting MAC address is XX-XX-XX-XX00-00, the end address is XX-XX-XX-XX-FF-FF or the starting MAC address is XXXX-XX-XX-XX-00, the end address is XX-XX-XX-XX-XX-FF
2. The prefix of the starting MACaddress and the end MACaddress must be same.
For example: IP address range: 66-66-66-66-66-00 66-66-66-66-66-FF
ETX-1 supports up to 32 Ethernet flows. Flows are unidirectional. One Ethernet
port can support one or same type classification combination. Two different flow
classification combinations are not allowed, except VLAN and untagged, IP and
non-IP.
When you configure the flow, if QinQ status is disabled (configure>bridge 1>port
(port-number)>no ingress-tag), please perform the VLAN action according to the
following rules:
Table 8-4, Table 8-5 and Table 8-6 show valid action combination rules on ingress
frame tags and the resulting egress frame tags and p-bits, according to whether
the ingress frame is untagged, contains one VLAN, or is double-tagged.
Note
8-28
Flows
Chapter 8 Networking
Innner VLAN
Untagged
One VLAN(X)
Double VLANS
(X and Y)
None
None
Untagged
X,Y
None
X,B
None
Pop
None
Untagged
Pop
Pop
B + p-bit D
Pop
Y + p-bit D
Pop
Pop
Untagged
Push Vlan A
None
Push Vlan A
None
Y + p-bit D
X
B + p-bit D
B (ingress
ports default
priority)
Push Vlan A
+ Inner-p-bit D
Push Vlan A
Push Inner-Vlan B
B+p-bit D
A
A,
Mark with
Vlan A
None
Mark with
Vlan A
Mark with
Vlan A
Mark with
Vlan A
A
B
A
Y+p-bit D
A
B+ p-bit D
+ Inner-p-bit D
Mark with
p-bit c
None
X+p-bit C
X+p-bit C
Y
Flows
8-29
Chapter 8 Networking
Mark with
p-bit c
Mark with
p-bit c
Mark with
p-bit c
Mark with
Vlan A
None
X+p-bit C
B
X+ p-bit C
Y+p-bit D
X+ p-bit C
+ Inner- p-bit D
B+p-bit D
A+p-bit C
A+p-bit C
Y
+ p-bit c
Mark with
Vlan A
A+p-bit C
B
+ p-bit c
Mark with Inner- p-bit
D
Mark with
Vlan A
A+p-bit C
Y+p-bit D
+ p-bit c
Mark with
Vlan A
A+ p-bit C
+ Inner- p-bit D
B+p-bit D
+ p-bit c
When you configure the flow, if QinQ status is enabled (configure>bridge 1>port
(port-number)>ingress-tag) and the flow direction is from net port to user port,
please perform the VLAN action according to the following rules:
Note
Outer VLAN
Untagged
One VLAN(X)
S
Double
VLANS
(S and C)
8-30
None
None
Untagged
Untagged
Pop
None
Untagged
None
None
C + p-bit D
None
B + p-bit D
B + p-bit D
Pop
Pop
C + p-bit D
Pop
Pop
Untagged
Pop
B + p-bit D
B + p-bit D
Flows
Chapter 8 Networking
Inner- p-bit D
When you configure the flow, if QinQ status is enabled (configure>bridge 1>port
(port-number)>ingress-tag) and the flow direction is from user port to net port,
please perform the VLAN action according to the following rules:
Note
Outer VLAN
Inner VLAN
Untagged
One VLAN
CE-VLAN(C)
None
None
PVID
PVID
C
None
PVID
B
None
PVID
C + p-bit D
Push Vlan A
None
A ,C
Push Vlan A
A,B
Push Vlan A
None
PVID
B + p-bit D
C + p-bit D
Push Vlan A
+ Inner-p-bit D
Push Vlan A
Push Inner-Vlan B
A
B+p-bit D
A,B
Factory Defaults
By default, no flows exist.
Flows
8-31
Chapter 8 Networking
To create classifier profile with criteria VLAN 20 and inner VLAN 30:
Configuring Flows
To configure flows:
1. Navigate to config>flows.
2. Enter flow <flow-name>.
8-32
Flows
Chapter 8 Networking
Command
classifier <classification-name>
Comments
Removing VLAN
no vlan-tag
Discarding traffic
transmitted via the flow
drop
Administratively enabling
the flow
no shutdown
The following marking actions can be performed in the mark level, at the
config>flows>flow(<flow-name>)>mark# prompt.
Flows
8-33
Chapter 8 Networking
Task
Command
Comments
vlan <vlan>
inner-vlan <inner-vlan>
p-bit <p-bit>
inner-p-bit <inner-p-bit>
8-34
Flows
Chapter 8 Networking
classifier v100_inner_v10
ingress-port ethernet 1
egress-port ethernet 3 queue 0 block 0/1
vlan-tag pop vlan
no shutdown
exit all
Flows
8-35
Chapter 8 Networking
:
:
:
:
:
f10_out
Up
Up
Off
v10
Name
Admin Status
Oper Status
Test
Classifier
:
:
:
:
:
f100_in
Up
Up
Off
v100_inner_v10
Slave flow from bridge port 1 to net port ETH 1, and bridge port 5 to user
port ETH 5:
Configure the same classifier profile v100
8-36
Flows
Chapter 8 Networking
2. Set up a flow using the previously defined classifier profile, with ingress at
ETH 3 and egress at bridge port 3:
ETX-1# configure flows
ETX-1>config>flows# flow master_flow
ETX-1>config>flows>flow(master_flow)$ classifier v100
ETX-1>config>flows>flow(master_flow)$ ingress-port ethernet 3
ETX-1>config>flows>flow(master_flow)$ egress-port bridge-port 3
ETX-1>config>flows>flow(f10_out)$ no shutdown
ETX-1>config>flows>flow(f10_out)$ exit all
ETX-1#
classifier v100
ingress-port bridge-port 1
egress-port ethernet 1 queue 1 block
no shutdown
exit all
2. Set up a flow using the previously defined classifier profile, with ingress at
bridge port 5 and egress at ETH 5:
ETX-1# configure flows
ETX-1>config>flows# flow slave_flow2
ETX-1>config>flows>flow(slave_flow2)$
ETX-1>config>flows>flow(slave_flow2)$
ETX-1>config>flows>flow(slave_flow2)$
0/1
ETX-1>config>flows>flow(slave_flow2)$
ETX-1>config>flows>flow(slave_flow2)$
ETX-1#
8.5
classifier v100
ingress-port bridge-port 5
egress-port ethernet 5 queue 1 block
no shutdown
exit all
Ethernet OAM
Ethernet OAM
8-37
Chapter 8 Networking
OAM CFM messages transparently, responding only to OAM link trace (LTM) and
unicast OAM loopback (LBM). MIPs can be configured automatically or manually.
Standards
IEEE 802.1ag, ITU-T Y.1731
Benefits
Ethernet service providers can monitor their services proactively and guarantee
that customers receive the contracted SLA. Fault monitoring and end-to-end
performance measurement provide tools for monitoring frame delay, frame delay
variation, and frame loss and availability.
Functional Description
OAM enables detection of network faults and measurement of network
performance, as well as distribution of fault-related information. OAM
functionality ensures that network operators comply with QoS guarantees, detect
anomalies before they escalate, and isolate and bypass network defects. As a
result, operators can offer binding service-level agreements.
In packet-switched networks, ETX-1 provides the following OAM (CFM) functions:
Note
Loss measurement
Delay measurement
OAM messages are always mapped to the queue with the lowest priority.
The device supports:
8-38
Ethernet OAM
Chapter 8 Networking
5. If ETX-1 is acting as a MIP, with manual MIP configuration, then configure the
necessary MIPs.
6. If ETX-1 is acting as a MEP:
a. Configure MA endpoints, referred as MEPs.
b. Configure MEP services.
c.
Factory Defaults
By default, there are no MDs, MAs, or MEPs.
The default MIP configuration mode is manual.
When a maintenance domain is created, it has the following default
configuration.
Parameter
Default
md-level
name
string "MD<mdid>"
Remarks
Default
Remarks
ccm-interval
1s
classification
vlan 0
mip-policy
no mip-policy
name
string "MA<maid>"
Default
classification
vlan 0
bind
no bind
client-md-level
queue
Remarks
Ethernet OAM
8-39
Chapter 8 Networking
Parameter
Default
Remarks
dest-addr-type
ccm-initiate
ccm-initiate
direction
down
ccm-priority
ais
no ais
shutdown
shutdown
Administratively disabled
Default
Remarks
delay-threshold
10
delay-var-threshold
10
classification
priority-bit 0
dmm-interval
1s
lmm-interval
1s
shutdown
shutdown
Administratively disabled
Default
remote
mac-address
00-00-00-00-00-00
delay
two-way data-tlv-length 0
loss
single-ended synthetic
Remarks
8-40
Ethernet OAM
Chapter 8 Networking
md/ma name
MD1/MA1
md slot/
lvl port
3
eth3
classifi admin
cation
status
100
enable
ok/total
r.meps
off 0/1
Ethernet OAM
8-41
Chapter 8 Networking
Task
Command
Comments
Configuring
maintenance
association for the
MD
maintenance-association
<maid>
Specifying the
maintenance domain
level
md-level <md-level>
name string
<md-name-string>
name mac-and-uint
<md-name-mac>
<md-name-uint>
no name
8-42
Ethernet OAM
Command
Chapter 8 Networking
Comments
mep <mepid>
mip-policy
{explicit | default | defer}
name string
<ma-name-string>
name primary-vid
<ma-name-vid>
Note
For every MEP, you must configure a flow with the same classification as the MEP.
Ethernet OAM
8-43
Chapter 8 Networking
Task
Command
Comments
Enabling initiation of
continuity check
messages (CCM)
ccm-initiate
ccm-priority <priority>
client-md-level <md-level>
8-44
Ethernet OAM
classification profile
<profile-name>
Chapter 8 Networking
Task
Command
Comments
dest-addr-type [ccm
{unicast|multicast}]
[pm {unicast|multicast}]
dest-mac-addr <mac-addr>
Defining direction
remote-mep <remote-mep-id>
service <serviceid>
show status
show remote-mep
<remote-mep-id> status
Administratively enabling
MEP
no shutdown
Services
To add a MIP:
Ethernet OAM
8-45
Chapter 8 Networking
To delete a MIP:
To configure a MIP:
1. Navigate to configure oam cfm maintenance-domain <mdid> mip <mip-id> to
select the MIP to configure.
The config>oam>cfm>md(<mdid>)>mip(<mip-id>)# prompt is displayed
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning unidirectional Rx
and Tx flows to the MIP
no shutdown
To configure a MIP:
Verify that you have flows configured between ETX-1 and the device(s)
acting as MEP(s) (refer to Flows for information on defining flows).
Examples
Configuring MD, MA, and MEP
MD ID 1
MA ID 1
8-46
Ethernet OAM
Chapter 8 Networking
MEP ID 1:
Bind Ethernet 1 (The bound Ethernet port must be the port that is used
by the flows)
Remote MEP ID 2
Ethernet OAM
8-47
Chapter 8 Networking
: MD1
: MA1
: OK
8-48
Ethernet OAM
Chapter 8 Networking
Task
Command
Comments
delay-threshold <delay-thresh>
8-49
Chapter 8 Networking
Task
Command
Comments
delay-var-threshold <delay-var-thresh>
dest-ne <dest-ne-index>
1255
no shutdown
no pm-collection disables PM
data collection.
Clearing statistics
clear-statistics
At the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)#,
enter:
dest-ne <dest-ne-index>
where <dest-ne-index> is 1255.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)>
dest-ne(<dest-ne-index>)$ is displayed.
8-50
Ethernet OAM
Chapter 8 Networking
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid
>)>dest-ne(<dest-ne-index>)# is displayed.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
delay two-way
[data-tlv-length <length-val>]
no pm-collection disables PM
data collection.
Clearing statistics
clear-statistics
Example
Service 1
Destination NE 3.
Ethernet OAM
8-51
Chapter 8 Networking
Far End Frame Loss Ratio Total number of OAM frames lost from local MEP
to remote MEP, divided by total number of transmitted OAM frames since the
service was activated
Near End Frame Loss Ratio Total number of OAM frames lost from remote
MEP to local MEP, divided by total number of transmitted OAM frames since
the service was activated
Far End Unavailability Ratio Total number of far end unavailable seconds
divided by elapsed time since service was activated
Near End Unavailability Ratio Total number of near end unavailable seconds
divided by elapsed time since service was activated.
For non ratio-based counters (Frames Above Delay and Frames Above Delay
Variation), you have to define a sampling interval in addition to the rising and
falling thresholds. The purpose of the interval is to define a timeline, in seconds,
in which the service OAM data is sampled and compared with the predefined
service thresholds. For the ratio-based counters, defining a sampling interval is
not required.
8-52
Ethernet OAM
Chapter 8 Networking
Description
Possible Values
event
rising-threshold
falling-threshold
For counters
near-end-unavailability-ratio or
far-end-unavailability-ratio:
11000
Notes:
8-53
Chapter 8 Networking
Example
Configure counters for the following service, as shown in the table below:
Maintenance domain 5
Maintenance association 8
MEP 3
Service 4.
The delay and delay variation (jitter) threshold for this service are set to 10 and
5 milliseconds respectively. The reporting counters for this service are set as
shown in the table below.
Counter
Event Type
Rising Threshold
Falling Threshold
Sampling
Interval
Log
10
30
Trap
1e-4
1e-8
1e-9
1e-10
Trap
40
20
Log
50
25
In this example, an SNMP trap and an event are generated as notification of the
rising threshold if during an 8-second sample interval, four DMM packets or more
exceed the 10-milliseconds delay threshold of this service. The alarm is cleared
(falling threshold) if ETX-1 detects an 8-second sample interval in which two or
fewer packets cross the thresholds.
A rising or falling threshold event is generated if a specific ratio is exceeded. For
example, an SNMP trap is sent if the far end Frame Loss Ratio (from ETX-1 to the
network) exceed 10^-4, i.e. more than one frame out of 10,000 LMMs sent for
this service are lost.
8-54
Ethernet OAM
Chapter 8 Networking
Ethernet OAM
8-55
Chapter 8 Networking
ETX-1>config>fault>cfm# info
service md 5 ma 8 mep
frames-report event
2 sampling-interval 8
no shutdown
exit
service md 5 ma 8 mep
frames-report event
sampling-interval 30
no shutdown
exit
service md 5 ma 8 mep
frames-report event
1e-8
no shutdown
exit
service md 5 ma 8 mep
frames-report event
falling-threshold 1e-10
no shutdown
exit
service md 5 ma 8 mep
frames-report event
no shutdown
exit
service md 5 ma 8 mep
frames-report event
no shutdown
exit
detail
3 service 4 above-delay
logandtrap rising-threshold
4 falling-threshold
3 service 4 above-delay-var
log rising-threshold 10 falling-threshold
3 service 4 far-end-loss-ratio
trap rising-threshold 1e-4 falling-threshold
3 service 4 near-end-loss-ratio
logandtrap rising-threshold 1e-9
3 service 4 far-end-unavailability-ratio
trap rising-threshold 40 falling-threshold
20
3 service 4 near-end-unavailability-ratio
log rising-threshold 50 falling-threshold 25
Interval OAM statistics for the current interval or a selected interval. You
can select an interval only if it has already ended since the corresponding
service was activated.
When a service is first activated, you can view statistics for only the current
interval. The statistics data is shown for the time elapsed since the beginning
of the interval. When the current interval ends, it becomes interval 1 and you
can select it for viewing interval statistics. After each interval ends, you can
select it for viewing interval statistics.
8-56
Ethernet OAM
Chapter 8 Networking
Note
The service for which you wish to view the statistics must be active. If the service
is not active, the commands to view statistics are not recognized.
Task
Command
Comments
Viewing running
statistics
show statistics
running
Ethernet OAM
8-57
Chapter 8 Networking
Task
Command
Comments
Viewing statistics
for the current
interval
show statistics
current
The statistics for the current interval are displayed as shown in Far
End TX Frames
: 161495
Far End RX Frames
: 161464
Far End Lost Frames
: 31
Far End Unavailable Seconds (Sec)
:0
Near End TX Frames
: 161464
Near End RX Frames
: 161462
Near End Lost Frames
:0
Near End Unavailable Seconds (Sec) : 0
Current Delay (mSec)
: 0.3
Current Delay Variation (mSec)
: 0.1
Frames Above Delay Threshold
:0
Frames Above Delay Variation Threshold : 0
Elapsed Time (sec)
: 80732
show statistics
interval
<interval-num>
Viewing running
statistics,
statistics for the
current interval,
statistics for all
intervals
Viewing statistics
for all intervals
Clearing the
statistics for the
service or
destination NE
clear-statistics
8-58
Statistics,
Ethernet OAM
Chapter 8 Networking
Description
Total number of frames lost from local service to remote service since
the service was activated (Far End Tx Frames - Far End Rx Frames)
Total number of frames received by local service since the service was
activated
Total number of frames lost from remote service to local service since
the service was activated (Near End Tx Frames - Near End Rx Frames)
Difference between the current delay value and the previous current
delay value
Description
Ethernet OAM
8-59
Chapter 8 Networking
Parameter
Description
Difference between the current delay value and the previous current
delay value
8-60
Ethernet OAM
Chapter 8 Networking
Description
Transmitted LMMs
Transmitted DMMs
Received LMRs
Received DMRs
Examples
Displaying Running Statistics
ETX-1>config>oam>cfm# ma 1 ma 1 mep 1 serv 1
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statistics running
Running Counters
----------------------------------------------------------------------------Far End TX Frames
: 160707
Far End RX Frames
: 160676
Far End Lost Frames
: 31
Near End TX Frames
Near End RX Frames
Near End Lost Frames
: 160676
: 160674
: 0
:
:
:
:
: 80338
0.3
0.0
0
0
Ethernet OAM
8-61
Chapter 8 Networking
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# dest-ne 3
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show
statistics running
Running Counters
----------------------------------------------------------------------------Far End TX Frames
: 161495
Far End RX Frames
: 161464
Far End Lost Frames
: 31
Far End Unavailable Seconds (Sec)
: 0
Near
Near
Near
Near
End
End
End
End
TX Frames
RX Frames
Lost Frames
Unavailable Seconds (Sec)
:
:
:
:
161464
161462
0
0
:
:
:
:
0.3
0.1
0
0
: 80732
8-62
Ethernet OAM
Chapter 8 Networking
End
End
End
End
Tx Frames
Rx Frames
Lost Frames
Frame Loss Ratio (%)
:
:
:
:
662
662
0
0.0000%
:
:
:
:
0.2
0.0
0
0
: 332
Ethernet OAM
8-63
Chapter 8 Networking
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# dest-ne 3
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show
statistics current
Current
----------------------------------------------------------------------------Far End Tx Frames
: 908
Far End Rx Frames
: 908
Far End Lost Frames
: 0
Far End Frame Loss Ratio (%)
: 0.0000%
Far End Unavailable Seconds (Sec)
: 0
Near
Near
Near
Near
Near
End
End
End
End
End
Tx Frames
Rx Frames
Lost Frames
Frame Loss Ratio (%)
Unavailable Seconds (Sec)
:
:
:
:
:
908
908
0
0.0000%
0
:
:
:
:
0.2
0.0
0
0
: 455
End
End
End
End
Tx Frames
Rx Frames
Lost Frames
Frame Loss Ratio (%)
:
:
:
:
1800
1800
0
0.0000%
8-64
Ethernet OAM
Chapter 8 Networking
End
End
End
End
End
Tx Frames
Rx Frames
Frames Loss
Frame Loss Ratio (%)
Unavailable Seconds (Sec)
End
End
End
End
End
Tx Frames
Rx Frames
Lost Frames
Frame Loss Ratio (%)
Unavailable Seconds (Sec)
:
:
:
:
:
1800
1800
0
0.0000%
0
:
:
:
:
:
1800
1800
0
0.0000%
0
: 0.2
: 0.0
Note
The option for remote MEP ID is available only if ETX-1 can resolve at least one
remote MEP MAC address.
To run an OAM loopback:
8-65
Chapter 8 Networking
Task
Command
Comments
Allowed range of
repeat-num is 150
show lbm-results
Note
The option to specify the destination MEP ID is available only if ETX-1 can resolve
at least one remote MEP MAC address.
To run an OAM link trace:
Task
Command
Comments
show linktrace-results
OAM EFM
This section describes the monitoring of the Ethernet links using OAM EFM (OAM
Ethernet at the First Mile)
ETX-1 can act as the active or passive side in an IEEE 802.3-2005 application.
When link OAM (EFM) is enabled for a port, you can view its status by displaying
the port status (show oam-efm). You can also display the OAM (EFM) parameters
and OAM (EFM) statistics.
Standards
IEEE 802.3ah
8-66
Ethernet OAM
Chapter 8 Networking
Benefits
Ethernet OAM (EFM) provides remote management and fault indication for the
Ethernet links. Remote link failure can be detected via OAM (EFM).
Functional Description
The OAM (EFM) discovery process allows a local data terminating entity (DTE) to
detect Ethernet OAM capabilities on a remote DTE. Once Ethernet OAM support is
detected, both ends of the link exchange state and configuration information,
such as mode, PDU size, and it can make a remote device perform loopback
function, if the remote device supports loopaback function. If both DTEs are
satisfied with the settings, OAM is enabled on the link. However, the loss of a link
or a failure to receive OAMPDUs for five seconds may cause the discovery process
to restart.
DTEs may either be in active or passive mode. DTEs in active mode initiate the
ETH-OAM (EFM) communications and can issue queries and commands to a
remote device. DTEs in passive mode generally wait for the peer device to initiate
OAM communications and respond to commands and queries, but do not initiate
them.
A flag in the OAMPDU allows an OAM entity to convey the failure condition Link
Fault to its peer. Link Fault refers to the loss of signal detected by the receiver; A
Link Fault report is sent once per second with the Information OAMPDU.
Factory Defaults
By default, OAM EFM is not enabled for the Ethernet.
Ethernet OAM
8-67
Chapter 8 Networking
Task
Command
Comments
no efm
show oam-efm
show oam-efm-statistics
loopback
snmp-tunneling
no snmp-tunneling disables
loopback
8-68
Ethernet OAM
Chapter 8 Networking
Example
To enable active link OAM (EFM) for Ethernet port 1 and display the status:
ETX-1# configure port l2cp-profile mac2peer
ETX-1>config>port>l2cp-profile(mac2peer)# mac 0x02 peer
ETX-1>config>port>l2cp-profile(mac2peer)# exit all
ETX-1# configure oam efm
ETX-1>config>oam>efm# descriptor 1 active
ETX-1>config>oam>efm# exit all
ETX-1# configure port ethernet 1
ETX-1>config>port>eth(1)# l2cp profile mac2peer
ETX-1>config>port>eth(1)# efm descriptor 1
ETX-1>config>port>eth(1)>efm# exit
ETX-1>config>port>eth(1)# show oam-efm
Administrative Status : Enabled
Operational Status
: Link Fault
Loopback Status
: Off
OAM EFM Information
----------------------------------------------------------------------------Local
Remote
MAC Address
: 00-20-D2-50-1A-13
-Mode
: Active
-Unidirectional : Not Supported
-Vars Retrieval : Supported
-Link Events
: Supported
-Loopback
: Not Supported
-PDU Size
: 1518
-Vendor OUI
: 0x0020D2
-ETX-1>config>port>eth(1)#
8.6
Router
Notes
Benefits
The router provides Layer-3 (IP) connectivity.
Factory Default
By default, the router is configured as shown in the following.
ETX-1 Ver. 1.2
Router
8-69
Chapter 8 Networking
Functional Description
Any management-related flow entering or exiting the device must be via an SVI
that is bound to a router interface. A router interface can be associated via
binding to only one SVI. If a flow is used for management purposes, the router
interface corresponding to the SVI must be enabled for management access.
Task
Command
clear-arp-table
name <string>
8-70
Router
Comments
Chapter 8 Networking
Task
Command
Comments
static-route
<IP-address/mask> address
<IP-address> [metric
<metric>]
show arp-table
show interface-table
show routing-table
dhcp-client
vendor-class-id name
<string>
vendor-class-id
ent-physical-name
Task
Command
address <ip-address/mask>
dhcp
management-access {allow-all
| allow-ping}
mtu <bytes>
name <string>
show status
Comments
Router
8-71
Chapter 8 Networking
Task
Command
Comments
no shutdown
dhcp-client
client-id id <string>
client-id mac
8-72
Router
Chapter 9
Timing and
Synchronization
9.1
This section explains how to receive the clock signal from NTP servers in the
network. ETX-1 can synchronize with up to ten servers, sending NTP requests to
the servers at user-defined intervals.
You can set one of the active SNTP servers as the preferred server, so that ETX1 sends NTP requests to the preferred server. If there is no preferred server or if
the preferred server does not answer, then ETX-1 sends NTP requests to any
enabled servers.
Factory Defaults
The default configuration of the SNTP parameters is:
Not preferred
Task
Command
Comments
broadcast
no broadcast disables
broadcast mode
poll-interval <minutes>
9-1
Task
Command
Comments
server <server-id>
Server Parameters
Displaying SNTP server status
show status
Task
Command
address <ip-address>
prefer
no shutdown
query-server
9-2
Comments
Example
Server ID = 1
IP address = 192.168.99.226
Preferred
Administratively enabled.
127.0.0.1
NTP Server
UDP Port Tstamp DateTime(UTC) Stratum Received
192.168.99.226 123
00-00-0000 00:00:00 0
-ETX-1>config>system>date-time>sntp#
9-3
9-4
Chapter 10
Administration
10.1 Clearing Device Statistics
You can clear the statistics for Ethernet ports.
Task
Command
date <date>
time <hh:mm[:ss]>
Comments
Format = mm-dd-yyyy
10-1
Chapter 10 Administration
Time = 3:32pm
Benefits
You can monitor the installed components and hardware/software revisions.
You can display additional information for each installed inventory component by
entering the inventory level using the corresponding inventory component index.
The index corresponds to the row in the output of show summary-inventory; it
therefore changes according to the specific components installed in the unit.
10-2
Chapter 10 Administration
Description
Description
Contained In
Index of the component that contains the component for which information is being
displayed. This is 0 for the chassis, as it is not contained in any component, and 1 for
all other components, as they are all contained in the chassis.
Physical Class
Class of component
Possible values: Chassis, CPU, Power Supply, Port
Relative Position
Contains the relative position of this component among other similar components
(with the exception of the relative positions for the chassis, management Ethernet
port).
Possible values for the various component types:
Chassis 4294967295
CPU 1
Power Supply 1
Network Port 1 or 2
User Port 3, 4, 5, 6
Management Ethernet 101
RS-232 Control Port 11
Name
Name of component
Possible values (according to component type):
<device-name> Chassis
CPU
Power Supply
Ethernet <n>
MNG Port
RS-232 Control Port
HW Rev
SW Rev
FW Rev
Serial Number
MFG Name
Model Name
Alias
Asset ID
FRU
Indicates whether the component is a field replaceable unit (can be replaced on-site).
For ETX-1 this is normally true only for the chassis.
10-3
Chapter 10 Administration
Task
Command
Comments
alias <string>
asset-id <id>
serial-number <string>
Example
10-4
Inventory table
Chassis
Power Supply
User Port 1.
Chapter 10 Administration
10-5
Chapter 10 Administration
ETX-1>config>system# inventory 6
ETX-1>config>system>inventor(6)# show status
Description
: ETX-1 Ethernet 3
Contained In
: 1
Physical Class
: Port
Relative Position : 3
Name
: Ethernet 3
HW Rev
:
SW Rev
:
FW Rev
:
Serial Number
:
MFG Name
:
Model Name
:
Alias
:
Asset ID
:
FRU
: False
ETX-1>config>system>inventor(6)# exit
ETX-1>config>system#
10-6
Displaying Environment
Chapter 10 Administration
2. Enter:
show environment
The information is displayed as shown in the example below.
The status of the power supply and fan indicates whether the unit is
present and functioning properly, or is absent (does not exist), or has
failed.
ETX-1# configure chassis
ETX-1>config>chassis# show environment
Power Supply
Type
Status
----------------------------------------------------------------------------1
AC-PFOK
FAN
Status
----------------------------------------------------------------------------Sensor
Value
Status
----------------------------------------------------------------------------ETX-1>config>chassis#
10-7
Chapter 10 Administration
ETX-1# file
ETX-1>file# show sw-pack
Name
Version
Creation Time
Actual
----------------------------------------------------------------------------sw-pack-1 1.2.0(0.15) 2013-05-09
08:35:15 previous active
sw-pack-2 1.2.0(0.16) 2013-05-09
08:35:15 active
Name
: 3444378
Version
Size
(Bytes)
----------------------------------------------------------------------------main
main.bin
1.2.0(0.15) 0.0
3444138
Name
H/W Ver
: 3444376
Version
H/W Ver
Size
(Bytes)
----------------------------------------------------------------------------main
main.bin
1.2.0(0.16) 0.0
3444136
ETX-1>file#
10-8
Chapter 10 Administration
0
0
0
0
0
Size
Purpose
VLAN
64
100
Huge
8192
100
Unused
Large
2048
1000
Medium
512
4000
Small
64
4000
Management traffic
Queue
16
8000
Display files
Delete files
Downloading/Uploading Files
You can download or upload files to the ETX-1 unit via SFTP/TFTP. Typically,
configuration files and software files are copied
The software files can also be downloaded to ETX-1 via the Boot Manager, using
XMODEM, FTP, or TFTP. For details on upgrading the device software, refer to
Chapter 12.
SFTP Application
The SFTP protocol provides secure file transfers via the devices Ethernet
interface. SFTP is a version of FTP that encrypts commands and data transfers,
keeping your data secure and your session private. For SFTP file transfers, an
SFTP server application must be installed on the local or remote computer.
File Operations
10-9
Chapter 10 Administration
Various third-party applications offer SFTP server software. For more information,
refer to the documentation of these applications.
ETX-1
ETX-1
10-10
File Operations
Chapter 10 Administration
Note
File Operations
10-11
Chapter 10 Administration
TFTP Application
TFTP protocol is typically used for remote IP-to-IP file transfers via the device's
Ethernet interface. It can also be used, however, for local file transfer, as the
transfer rate of the Ethernet interface is much faster than that of the RS-232
interface.
For TFTP file transfers, a TFTP server application must be installed on the local or
remote computer. The TFTP server waits for any TFTP file transfer request
originating from the device, and automatically performs the request.
Various third-party TFTP applications allow instant creation of a TFTP server on a
client computer. For more information, refer to the documentation of these
applications.
ETX-1
ETX-1
10-12
File Operations
Chapter 10 Administration
File Operations
10-13
Chapter 10 Administration
Note
10-14
File Operations
Chapter 10 Administration
TCP port 22
TCP port 22
File Operations
10-15
Chapter 10 Administration
Example
10-16
File Operations
Chapter 10 Administration
ETX-1# file
ETX-1>file# dir
Codes: C-Configuration
Name
S-Software
L-License
LO-Log
O-Other
B-Banner
db-config
LO
--
db-schema
LO
16780
mac-table
LO
--
pm-0
LO
18
sw-pack-1
3472304
sw-pack-2
3433902
startup-config
34
factory-default-config C
34
running-config
--
log
LO
310000
Free Bytes
2013-08-09
09:53:32
2013-08-09
09:53:32
2013-08-09
09:53:32
2013-08-09
09:53:33
2013-05-14
13:17:34
2013-05-09
16:24:28
2013-08-09
09:51:58
2013-08-09
09:53:32
2013-08-09
09:47:38
2013-05-06
14:58:32
File In Use
Read Only
Read Only
File In Use
File In Use
Read Only
File In Use
Read Only
: 5212160
ETX-1# file
ETX-1>file# show configuration-files
Configuration
Last Modified
Valid
----------------------------------------------------------------------------startup-config
1970.01.01 00:05:50 Yes
user-default-config
2015.05.19 01:00:34 Yes
factory-default-config1970.01.01 00:01:05 Yes
running-config
1970.01.01 00:00:08 Yes
Device loaded from : startup-config
running-config has been modified since last time it was equal to startup-config
show factory-default-config
show rollback-config
File Operations
10-17
Chapter 10 Administration
show startup-config
show user-default-config
The contents of the specified configuration file are displayed.
Deleting Files
You can delete the following files:
Note
sw-pack-<n>
restore-point-config
rollback-config
startup-config
user-default-config
zero-touch-config-xml
10-18
Saving Configuration
Chapter 10 Administration
10.9 Reset
ETX-1 supports the following types of reset:
Reset
10-19
Chapter 10 Administration
To restart ETX-1:
1. At the admin# prompt enter:
reboot.
A confirmation message is displayed:
Device will reboot. Are you sure? [yes/no]
2. Enter yes to confirm the reset.
The unit restarts.
10-20
Reset
Chapter 11
Monitoring and
Diagnostics
The following topics are covered in this chapter:
Detecting problems
Statistic Counters
Statistic counters provide information on possible abnormal behavior and failures.
You can collect statistics on the following:
Ethernet ports
RADIUS server
For further information, refer to the relevant sections in Chapter 6-10 and the
relevant sections in the troubleshooting chart.
11-1
Source An entity for which alarms and events can be generated. The source
consists of a source ID, source type (e.g., system, fan, Ethernet), and source
name.
Alarms and events can be masked per source type, source ID, or minimum
severity. When an alarm/event is masked, it is not written to the history log, and
any corresponding traps are not sent to management stations, regardless of
masking in the SNMP manager configuration. When an alarm/event is not masked,
any corresponding traps are sent only to management station for which the traps
are not masked in the SNMP manager configuration.
Task
Command
11-2
Comments
Task
Command
Comments
Configuring alarm/event
severity and masking per
source
alarm-source-attribute <source-name>
no alarm-source-attribute masks
[<source-id>] alarm <alarm-list> [severity alarms/events. The following apply:
{critical | major | minor}] [log] [snmp-trap] If a trap is masked according to
[led]
alarm/event attribute, it is not
sent to any management
alarm-source-attribute <source-name>
station, regardless of whether
[<source-id>] event <event-list> [log]
it is masked in the SNMP
[snmp-trap]
manager configuration
Configuring alarm/event
severity and masking per
source type
11-3
Command
show event-list
Task
Command
Acknowledging alarms
active-alarm-rebuild [send-traps]
show active-alarms
show active-alarms-details
show alarm-log
Comments
11-4
Task
Command
Comments
show brief-alarm-log
show brief-alarm-log {<source-type> [<source-id>] | all}
[minimum-severity {critical | major | minor | cleared}]
[order-ascending] [time-zone-utc] [acknowledged-included] [start
<yyyy-mm-dd> [<hh:mm[:ss]>]] [end <yyyy-mm-dd>
[<hh:mm[:ss]>]]
show brief-alarm-log {<source-type> [<source-id>] | all}
[minimum-severity {critical | major | minor | cleared}] [orderascending] [time-zone-utc] [acknowledged-included] [last-seconds
<seconds> | last-entries <entries>]
Description
A=Alarm ID
E=Event
Source
Trap
sw_install_start
1020001
system
systemSoftwareInstallStart
sw_install_end
1020002
system
systemSoftwareInstallEnd
download_end
End download
1020003
system
systemDownloadEnd
user_reset
1020004
system
systemUserReset
11-5
Description
Source
Trap
alternate_configuration_l {startup-config |
E
oaded
user-default-config |
factory-default-config
| rollback-config}
loaded as
running-config
1020005
system
systemAlternateConfigLoaded
1020006
system
systemConfigurationMigration
configuration_sanity
1020007
system
systemConfigurationSanity
Configuration sanity
in <configuration
file>: configuration
<loaded/rejected/
loaded till first error>
trap_hard_sync_start
Trap synchronization
hard sync process
started
1020008
system
systemTrapHardSyncStart
trap_hard_sync_end
Trap synchronization
hard sync process
ended
1020009
system
systemTrapHardSyncEnd
1020010
system
systemConfigurationChangeM
ask
1020011
system
systemConfigurationChangeU
nmask
dying_gasp
Dying gasp
1020012
system
systemDyingGasp
dying_gasp_recovery
1020013
system
systemDyingGaspRecovery
trace_msg_fatal_error
Fatal error
1020014
system
systemTraceMsgFatalError
trace_msg_exception
Exception
1020015
system
systemTraceMsgException
1020016
system
systemTraceMsgSwWatchdog
Reset
1020017
system
systemBackupConfigurationLo
aded
1020018
system
systemDeviceStartup
Successful login
1020022
device_startup
successful_login
11-6
coldStart
system
systemSuccessfulLogin
Name
Description
A=Alarm ID
E=Event
Source
Trap
failed_login
Failed login
1020023
system
systemFailedLogin
logout
Logout due to
inactivity
1020024
system
systemLogout
rfc2544_test_start
RFC2544 test ID
started
1020025
system
systemRfc2544TestStart
rfc2544_test_end
RFC2544 test ID
ended
1020026
system
systemRfc2544TestEnd
startup_config_unconfir
med
New startup-config
not confirmed
1020028
system
systemStartupConfigUnconfir
med
1020029
system
systemActiveSoftwareChange
d
running_config_saved
Running configuration E
saved to startup
configuration
1020030
system
systemRunningConfigSaved
sfp_opt_ora
Optical power
E
transmitted (OPT) out
of range
1050001
Ethernet sfpOptOra
sfp_opt_ora_off
Optical power
transmitted (OPT) in
permitted range
1050002
Ethernet sfpOptOraOff
sfp_lbc_ora
1050003
Ethernet sfpLbcOra
sfp_lbc_ora_off
1050004
Ethernet sfpLbcOraOff
bridge_new_root
1170001
Bridge
bridgeSpanningTreeNewRoot
bridge_top_change
Topology change is
detected
1170002
Bridge
bridgeSpanningTreeTopologyC
hange
sub_group_switchover
Switchover between
sub-groups of intercard LAG
1250001
LAG
lagSubGroupSwitchover
lag_failure
1250002
LAG
lagFailure
remote_loopback
Loopback started
1270101
oam-efm oamEfmRemoteLoopback
remote_loopback_off
Loopback ended
1270102
oam-efm oamEfmRemoteLoopbackOff
delay_tca
Delay threshold
crossing alert
1270401
oamcfmdest-ne
oamCfmDestNeDelayTca
11-7
Name
Description
A=Alarm ID
E=Event
Source
Trap
delay_tca_off
Delay in permitted
range
1270402
oamcfmdest-ne
oamCfmDestNeDelayTcaOff
delay_var_tca
Delay variance
threshold crossing
alert
1270403
oamcfmdest-ne
oamCfmDestNeDelayVarTca
delay_var_tca_off
Delay variance in
permitted range
1270404
oamcfmdest-ne
oamCfmDestNeDelayVarTcaOf
f
loss_ratio_tca
1270405
oamcfmdest-ne
oamCfmDestNeLossRatioTca
loss_ratio_tca_off
Loss ratio in
permitted range
1270406
oamcfmdest-ne
oamCfmDestNeLossRatioTcaO
ff
loss_ratio_tca_fe
1270407
oamcfmdest-ne
oamCfmDestNeLossRatioTcaF
e
loss_ratio_tca_fe_off
Loss ratio in
permitted range at
far-end
1270408
oamcfmdest-ne
oamCfmDestNeLossRatioTcaF
eOff
unavailable_ratio_tca
Unavailable ratio
threshold crossing
alert
1270409
oamcfmdest-ne
oamCfmDestNeUnavailRatioTc
a
1270410
oamcfmdest-ne
oamCfmDestNeUnavailRatioTc
aOff
unavailable_ratio_tca_fe
1270411
oamcfmdest-ne
oamCfmDestNeUnavailRatioTc
aFe
1270412
oamcfmdest-ne
oamCfmDestNeUnavailRatioTc
aFeOff
1291101
20002
system
systemDeviceTemperatureOra
configuration_mismatch Configuration
mismatch
20004
system
systemConfigurationMismatch
hardware_failure
20005
system
systemHardwareFailure
Unavailable ratio
threshold crossing
alert at far-end
11-8
Hardware failure
Name
Description
A=Alarm ID
E=Event
Source
Trap
interface_mismatch
20006
system
systemInterfaceMismatch
no_interface
20007
system
systemNoInterface
sw_pack_corrupted
20008
system
systemSwPackCorrupted
hardware_failure_fe
Hardware failure at
far-end
20012
system
systemFeHardwareFailure
configuration_mismatch_ Configuration
fe
mismatch at far-end
20013
system
systemFeConfigurationMismat
ch
interface_mismatch_fe
20014
system
systemFeInterfaceMismatch
no_interface_fe
20015
system
systemFeNoInterface
power_delivery_failure
20201
system
powerDeliveryFailure
power_in_ora
20202
power
supply
powerInOra
power_in_low
20203
power
supply
powerInLow
sfp_no_response
Loss of
communication with
SFP
50001
Ethernet sfpNoResponse
sfp_mismatch
SFP mismatch
50002
Ethernet sfpMismatch
los
50003
Ethernet linkUp/linkDown
ethLos
sfp_removed
50004
Ethernet sfpRemoved
sfp_temperature_ora
50005
Ethernet sfpTemperatureOra
sfp_opr_ora
Optical power
A
received (OPR) out of
range
50006
Ethernet sfpOprOra
fault_propagation
Fault propagation
50007
Ethernet faultPropagation
50008
Ethernet ethAutoNegotiationFailure
50009
Ethernet ethFeLos
auto_negotiation_failure Auto-negotiation
failed to synchronize
with remote device
los_fe
11-9
Name
Description
A=Alarm ID
E=Event
Source
fault_propagation_fe
Fault propagation at
far-end
50010
Ethernet feFaultPropagation
link_down
Link down
270101
oam-efm oamEfmLinkDown
link_fault_indication
270102
oam-efm oamEfmLinkFaultIndication
link_fault_indication_fe
270103
oam-efm oamEfmFeLinkFaultIndication
critical_link_indication
270104
oam-efm oamEfmCriticalLinkIndication
270105
oam-efm oamEfmFeCriticalLinkIndicatio
n
270106
oam-efm oamEfmDyingGaspIndication
270107
oam-efm oamEfmFeDyingGaspIndicatio
n
ais
270201
oamoamCfmMepAis
cfm-mep
lck
270202
oamoamCfmMepLck
cfm-mep
mismatch
Mismatch due to
A
<mismerge/
unexpected MEP/
unexpected MEG level/
unexpected period>
270203
oamoamCfmMepMismatch
cfm-mep
loc
Loss of continuity
(LOC) <mep name>
270601
oamoamCfmRmepLoc
cfm-mep
rdi
Remote defect
A
indication (RDI) <mep
name>
270602
oamoamCfmRmepRdi
cfm-mep
erp_state_protected
290301
ERP
dying_gasp_indication
Trap
erpStateProtected
Note
11-10
All traps are maskable, by masking the corresponding alarm/event via the
alarm-source-attribute / alarm-source-type-attribute commands, or by masking
the corresponding alarm per severity via the mask-minimum-severity command.
For details, refer to Configuring Alarm and Event Properties.
Trap OID
Alarm/Event Name
A=Alarm
E=Event
Alarm/
Event ID
Alarm/
Event
Source
coldStart
1.3.6.1.6.3.1.1.5.1
device_startup
1020018
system
systemSoftwareInstallSt 1.3.6.1.4.1.164.6.1.0.42
art
sw_install_start
1020001
system
systemSoftwareInstallEn 1.3.6.1.4.1.164.6.1.0.43
d
sw_install_end
1020002
system
systemDownloadEnd
1.3.6.1.4.1.164.6.2.12.18 download_end
.0.2
1020003
system
systemUserReset
1.3.6.1.4.1.164.6.1.0.82
user_reset
1020004
system
systemAlternateConfig
Loaded
1.3.6.1.4.1.164.6.1.0.45
alternate_configuratio E
n_loaded
1020005
system
systemConfiguration
Sanity
1.3.6.1.4.1.164.6.1.0.47
configuration_sanity
1020007
system
systemTrapHardSync
Start
1.3.6.1.4.1.164.6.1.0.77
trap_hard_sync_start
1020008
system
systemTrapHardSync
End
1.3.6.1.4.1.164.6.1.0.78
trap_hard_sync_end
1020009
system
systemDyingGasp
1.3.6.1.4.1.164.6.1.0.49
dying_gasp
1020012
system
systemTraceMsgFatalErr 1.3.6.1.4.1.164.6.1.0.51
or
trace_msg_fatal_error
1020014
system
systemTraceMsgExceptio 1.3.6.1.4.1.164.6.1.0.52
n
trace_msg_exception
1020015
system
systemDeviceStartup
1.3.6.1.4.1.164.6.1.0.55
device_startup
1020018
system
systemSuccessfulLogin
1.3.6.1.4.1.164.6.1.0.70
successful_login
1020022
system
systemFailedLogin
1.3.6.1.4.1.164.6.1.0.71
failed_login
1020023
system
systemLogout
1.3.6.1.4.1.164.6.1.0.72
logout
1020024
system
1020028
system
1020029
system
systemRunningConfigSa 1.3.6.1.4.1.164.6.1.0.84
ved
running_config_saved
1020030
system
bridgeSpanningTreeNew 1.3.6.1.4.1.164.4.0.1
Root
bridge_new_root
1170001
Bridge
bridgeSpanningTreeTopo 1.3.6.1.4.1.164.4.0.2
logyChange
bridge_top_change
1170002
Bridge
11-11
Trap OID
A=Alarm
E=Event
Alarm/
Event ID
Alarm/
Event
Source
1270101
oam-efm
1270102
oam-efm
1270401
oam-cfmdest-ne
1270402
oam-cfmdest-ne
1270403
oam-cfmdest-ne
1270404
oam-cfmdest-ne
1270405
oam-cfmdest-ne
1270406
oam-cfmdest-ne
1270407
oam-cfmdest-ne
1270408
oam-cfmdest-ne
1270409
oam-cfmdest-ne
1270410
oam-cfmdest-ne
1270411
oam-cfmdest-ne
1270412
oam-cfmdest-ne
erpPortStateChange
1291101
ERP port
1.3.6.1.4.1.164.3.1.6.1.0. erp_port_state_change E
5
systemDeviceTemperatu 1.3.6.1.4.1.164.6.1.0.41
reOra
device_temperature_or A
a
20002
system
systemSwPackCorrupted 1.3.6.1.4.1.164.6.1.0.61
sw_pack_corrupted
20008
system
powerDeliveryFailure
1.3.6.1.4.1.164.6.1.0.73
power_delivery_failure A
20201
power
supply
linkDown
1.3.6.1.6.3.1.1.5.4
los
50003
Ethernet
linkUp
1.3.6.1.6.3.1.1.5.3
los
50003
Ethernet
11-12
Trap OID
ethLos
sfpRemoved
A=Alarm
E=Event
Alarm/
Event ID
Alarm/
Event
Source
1.3.6.1.4.1.164.3.1.6.1.0. los
1
50003
Ethernet
1.3.6.1.4.1.164.40.3.4.0. sfp_removed
3
50004
Ethernet
270102
oam-efm
270103
oam-efm
270104
oam-efm
270105
oam-efm
270106
oam-efm
270107
oam-efm
oamCfmMepAis
1.3.6.1.4.1.164.3.1.6.1.3. ais
0.4
270201
oam-cfmmep
oamCfmMepLck
1.3.6.1.4.1.164.3.1.6.1.3. lck
0.5
270202
oam-cfmmep
oamCfmMepMismatch
1.3.6.1.4.1.164.3.1.6.1.3. mismatch
0.6
270203
oam-cfmmep
oamCfmRmepLoc
1.3.6.1.4.1.164.3.1.6.1.3. loc
0.7
270601
oam-cfmmep
oamCfmRmepRdi
1.3.6.1.4.1.164.3.1.6.1.3. rdi
0.8
270602
oam-cfmmep
erpStateProtected
1.3.6.1.4.1.164.3.1.6.1.0. erp_state_protected
4
290301
ERP
authenticationFailure
1.3.6.1.6.3.1.1.5.5
--
--
--
Not applicable
11-13
Task
Command
Comments
pm
11.3 Syslog
ETX-1 uses the Syslog protocol to generate and transport event notification
messages over IP networks to Syslog servers. The Syslog operation is compliant
with the RFC 3164 requirements.
Specify the UDP port that transmits syslog messages (allowed only if
syslog message transmitting is administratively disabled):
port <udp-port-number>
Allowed values: 165535
Default: 514
d. Specify the severity level. The log messages that contain severity level up
to the specified level are transmitted:
severity-level {emergency | alert | critical | error | warning | notice |
informational | debug}
e. Administratively enable the transmitting of syslog messages:
no shutdown
3. Define syslog server parameters:
a. Specify the syslog server to receive syslog messages, from 1 to 5:
syslog server <server-id>.
11-14
Syslog
Specify the UDP port on the server that receives syslog messages
(allowed only if the server is administratively disabled):
port <udp-port-number>
Allowed values: 165535
Parameter
Description
Total Tx Messages
Non-queued Dropped
Messages
Syslog
11-15
11.4 Troubleshooting
This section contains a general troubleshooting chart that lists possible failures
and provides workarounds.
Troubleshooting Chart
Use this chart to identify the cause of a problem that may arise during operation.
For detailed description of the LED indicators functions, refer to Chapter 3.
To correct the reported problem, perform the suggested corrective actions. If a
problem cannot be resolved by performing the suggested action, please contact
your RAD distributor.
Probable Cause
Corrective Action
No power
Blown fuse
Incorrect
management
settings
Management path
disconnected
11-16
Troubleshooting
Fault/Problem
Probable Cause
Corrective Action
Link may be
administratively
disabled.
Ethernet cable
problem
To ping an IP host:
1. In any level, start pinging the desired host specifying its IP address, optionally
the number of packets to send and the size of the payload in bytes:
ping <ip-address> [number-of-packets <packets>] [payload-size <bytes]
Allowed value: ip-address - 1.1.1.1255.255.255.255
packets 1-10000
bytes - 32-1450
To trace a route:
In any level, start the trace route and specify the IP address of the host to
which you intend to trace route:
trace-route <ipaddress>
Allowed value: ip-address - 1.1.1.1255.255.255.255
11-17
11-18
Technical Support
Chapter 12
Software Upgrade
This chapter explains how to upgrade ETX-1.
Software upgrade is required to fix product limitations, enable new features, or
to make the unit compatible with other devices that are already running the new
software version.
The device can store up to two software images, referred to as software packs
and named sw-pack-1 through sw-pack-2. You can designate any of the software
packs as active. The non-active software packs serve as backups that can be used
if the active software becomes corrupted.
Hardware 2.0
12.2 Impact
ETX-1 resets automatically after the software upgrade, resulting in up to
two minutes of downtime.
Upgrading to a new version does not affect any user settings after saving the
user settings.
12.3 Prerequisites
Before starting the upgrade, verify that you have the following:
Software image file stored on the PC. The image file (and exact name)
can be obtained from the local RAD business partner from whom the
device was purchased.
Prerequisites
12-1
Software image file stored on the PC. The image file (and exact name)
can be obtained from the local RAD business partner from whom the
device was purchased.
ETX-1
ETX-1
Note
Pinging the PC
Check the integrity of the communication link between ETX-1 and the PC by
pinging the PC from ETX-1.
12-2
Note
Choose an index that is not being used by the active software or by a software
pack that you do not want to overwrite.
The software download is performed. Refer to Installing Software for instructions
on installing the downloaded software as the active software.
12-3
Installing Software
After software is downloaded to ETX-1, it must be installed via the install
command as the active software. When you install software, ETX-1 by default
creates a restore point, so that you can perform a rollback to the previous
software pack if there is a problem with the new software pack.
Note
The file startup-config must exist before you can install software with creation of
a restore point.
You can request (using command software-confirm-required) that the next
installed software be confirmed after the next reboot. After you execute the
request, the next time ETX-1 reboots and loads the new software, you will need
to confirm the software (using command software-confirm) within the configured
timeout period. If the confirmation is not received before timeout, ETX-1
automatically falls back to its previous software.
Note
Note
If startup-config does not exist, you must install the software pack without
creating a restore point.
1. At the admin>software# prompt, enter:
install <filename> [no-restore-point]
The parameter <filename> can be any of the non-active software packs
(sw-pack-1 through sw-pack-2). If you specify no-restore-point, it will not be
possible to rollback to the previous software after the software is installed.
You are prompted to confirm the operation.
!Device will install file and reboot. Are you sure? [yes/no] _
2. Type yes to confirm.
If a restore point is being created, then startup-config is copied to
restore-point-config. ETX-1 designates the specified software pack as
active, and then reboots.
3. If a software confirmation request is active, ETX-1 starts a timer with the
specified timeout period.
Note
12-4
While the confirmation timer is running, ETX-1 does not allow any commands that
change its configuration.
Caution The Boot menu procedures are recommended for use only by authorized
personnel, because this menu has many additional options that are intended for
use only by technical support personnel.
The following software downloading options are available from the Boot menu:
ETX-1
12-5
Note
If you miss the timing, ETX-1 performs a regular reboot process (this process
starts with Loading and ends with the login screen).
System Boot
Copyright 1984-2008
CPU
:
OS version :
BSP version:
Boot-Manager
Freescale MPC8313E
VxWorks 6.7
1.17
version: 1.00.00 [14-May-12]
12-6
[boot]: ?
Commands:
?/help
p
c [param]
v
run
delete <FileName>
dir
show <index>
download <index> [,<FileName|x>]
by Xmodem)
set-active <index>
application
control-x/reset
Note
Choose an index that is not being used by the active software, or by a software
pack that you do not want to overwrite.
The process starts, and the following is displayed:
The terminal will become disabled !!!
Please send the file in XMODEM
3. Start the transfer in accordance with the program you are using. For example,
if you are using the Windows HyperTerminal utility:
Select Transfer in the HyperTerminal menu bar, and then select Send File
on the Transfer menu.
The Send File window is displayed:
Select the prescribed ETX-1 software file name (you may use the
Browse function to find it).
In the Protocol field, select Xmodem.
Note
ETX-1 Ver. 1.2
12-7
Using FTP
Use the following procedure to download new release to ETX-1 via FTP.
Note
Choose an index that is not being used by a software pack that you do not want
to overwrite.
If no errors are detected, the downloading process starts, and the file is
downloaded via FTP.
3. Refer to Activating Software for instructions on activating the downloaded
software.
Using TFTP
Use the following procedure to download new release to ETX-1 via TFTP.
Note
Choose an index that is not being used by a software pack that you do not want
to overwrite.
If no errors are detected, the downloading process starts, and the file is
downloaded via TFTP.
3. Refer to Activating Software for instructions on activating the downloaded
software.
12-8
Activating Software
To activate a software pack, you need to designate it as active and load it.
12-9
12-10
Chapter 13
Application Tutorial
13.1 Flow-Based Application
This section provides detailed instructions on configuring, and using a flow-based
point-to-point application. It provides instructions for enabling remote
connectivity to the management station, and running data traffic streams.
Site B
Site A
ETX-1
192.168.100.56
Untagged 3
ETX-1
192.168.100.57
VLAN 100
Data Flow
VLAN 100
IP
Network
Video Flow
Client PC
192.168.100.33
VLAN 4090
MNG Flow
Data Flow
Untagged 3
Video Flow
VLAN 4090
MNG Flow
Host
Client PC
192.168.100.36
Host
PC Server
192.168.100.99
Baud Rate:
9,600 bps
Data bits:
Parity:
None
Stop bits:
Flow control:
None.
3. Power-up ETX-1.
Flow-Based Application
13-1
4. ETX-1 boots up. When the startup process is completed, you are prompted to
press <ENTER> to receive the login prompt.
5. Enter the user name for Super User and the associated password. The default
user name is su and the default password is 1234.
6. The device prompt appears:
ETX-1#
You can now type the necessary CLI commands.
Configuring SVI
SVI 1 must be administratively enabled in order to administratively enable the
corresponding flows and router interface.
13-2
Flow-Based Application
Configuring Router
The router must be configured with the router interface 1 that is bound to the
SVI 1 used for the management flows, and assigned the IP address
192.168.100.57 with mask 255.255.255.0.
Enter the following commands:
configure router 1
interface 1
bind svi 1
address 192.168.100.57/24
no shutdown
exit all
Saving Configuration
Type save in any level to save your configuration.
Flow-Based Application
13-3
Saving Configuration
Type save in any level to save your configuration.
Baud Rate:
9,600 bps
Data bits:
Parity:
None
Stop bits:
Flow control:
None.
3. Power-up ETX-1.
4. ETX-1 boots up. When the startup process is completed, you are prompted to
press <ENTER> to receive the login prompt.
5. Enter the user name for Super User and the associated password. The default
user name is su and the default password is 1234.
6. The device prompt appears:
ETX-1#
You can now type the necessary CLI commands.
13-4
Flow-Based Application
Configuring SVI
SVI 1 must be administratively enabled in order to administratively enable the
corresponding flows and router interface.
Configuring Router
The router must be configured with the router interface 1 that is bound to the
SVI 1 used for the management flows, and assigned the IP address
192.168.100.56 with mask 255.255.255.0.
Flow-Based Application
13-5
Saving Configuration
Type save in any level to save your configuration.
Saving Configuration
Type save in any level to save your configuration.
13-6
Flow-Based Application
Management Host IP
192.168.100.3
ETX-1 (D)
Management Host IP
192.168.100.2
Ring Link
Ring Link
Management Host IP
192.168.100.4
IP
Network
ETX-1 (A)
RPL owner
RPL Port-GbE1
NMS
192.168.100.10
ETX-1 (C)
Ring Protection
Link (RPL)
User
Equipment
Ring Link
ETX-1 (B)
Management Host IP
192.168.100.5
GbE1-East Port
GbE2-West Port
User
Equipment
Equipment List
The following equipment is required to set up a typical ring application:
PC
13-7
Ring Link
2
ETX-1 (A)
(RPL owner RPL port: Net1)
1
ETX-1 (D)
ETX-1 (B)
Ring Link
2
1
Ring Link
Net1-East Port
Net2-West Port
ETX-1 (C)
Configuration Sequence
The following configuration steps are needed when deploying the ETX-1 units in a
ring topology:
1. Configuring the management flow
2. Configuring bridge port
3. Defining the VLAN
4. Configuring ERP parameters and enabling the ring functionality
Management Flow
Ring Traffic
ETX-1 (A)
Management IP:
192.168.100.2
VLAN ID: 4
Management IP:
192.168.100.3
VLAN ID: 4
Management IP:
192.168.100.4
VLAN ID: 4
Management IP:
192.168.100.5
VLAN ID: 4
ETX-1 (B)
ETX-1 (C)
ETX-1 (D)
13-8
Configuring VLAN
Create VLAN 4 for management flows and VLAN 12 for bridge traffic.
config bridge 1 vlan 12
tagged-egress 3..6
exit
vlan 4
exit all
13-9
13-10
Appendix A
Connector Wire Data
A.1
Ethernet Connectors
A.2
Pin
MDI
MDIX
A+
B+
A-
B-
B+
A+
C+
D+
C-
D-
B-
A-
D+
C+
D-
C-
MNG Connector
Pin
Designation
Function
RxD+
RxD
TxD+
4,5
Not connected
MNG Connector
A-1
Pin
Designation
Function
TxD-
7,8
Not connected
A.3
Control Connector
The control terminal interface terminates with a V.24/RS-232 cable based on the
mini-USB connector.
A-2
Control Connector
Appendix B
Test Plan
B.1
Introduction
This appendix describes basic verification tests for ETX-1. The aim is to perform a
series of short tests that check the following:
Basic functionality
OAM EFM
OAM CFM
B.2
Required Equipment
Product
HW Version
SW Version
DUT
ETX-1
2.0
1.2.0(0.30)
IXIA 400T
NA
HW Version
SW Version
ETX-1
2.0
1.2.0(0.30)
Test Equipment
Function
Requirements
Unit
PC
WireShark Ethereal
ETH Cable
Straight
Notes
Required Equipment
B-1
Function
Requirements
Terminal Configuration
Table
B.3
Unit
Notes
Supplied
1
2
3
4
3
4
5
6
IXIA
EFM
Active
3
1
LAG
Protection
ETX-1 (A)
Switch
4
ETX-1 (B) EFM
Active
ETX-1 (C)
3
5
6
7
8
EFM
Passive
1
IXIA
2
VID 51
OOB
ETX-1 (D)
NMS
Cable
Device Name
Switch
IXIA
Switch
ETX-1(B) port 3
ETX-1(C)
ETX-1(B) port 4
ETX-1(D)
ETX-1(B)
IXIA
ETX-1(B)
Switch
IXIA
Configuring Devices
This section explains how to configure test equipment and RAD devices. The
following table presents the configuration files for the ETX-1 devices, according
to test functionality and device type. You can open or save the configuration files
as follows:
B-2
Configuration File
ETX-1 (A)
ETX-1 (B)
ETX-1 (C)
ETX-1 (D)
B.4
The objective of the test is to verify the overall success of the setup
configuration.
Estimated Duration
The estimated duration of this test is 30 minutes.
Test Procedure
Table B-3 details procedure of the basic functionality test.
Table B-3. Test Procedure and Results
#
Action
Expected Result
Result
B-3
Action
Expected Result
Result
For example:
B-4
Action
Expected Result
10
11
B.5
Result
Testing OAM-EFM
The objective of this test is to verify the correct functionality of the OAM-EFM
discovery process.
Estimated Duration
The estimated duration of this test is 30 minutes.
Test Procedure
Table B-4 details the OAM-EFM test procedure.
Testing OAM-EFM
B-5
Action
Expected Result
Result
B.6
Testing OAM-CFM
The objective of this test is to verify the MEP and MIP status of ETX-1.
Estimated Duration
The estimated duration of this test is one hour.
B-6
Testing OAM-CFM
Test Procedure
Table B-5. OAM CFM Test Procedure
#
Action
Expected Result
Operational Status: OK
Result
Same as above
Testing OAM-CFM
B-7
Action
Expected Result
11
12
13
14
Result
On
Off
Operational status- Ok
B.7
Testing Diagnostics
Estimated Duration
The estimated duration of this test is 30 minutes.
Test Procedure
Table B-6 details the diagnostics test procedure.
B-8
Testing Diagnostics
Action
Expected Result
Result
Testing Diagnostics
B-9
Action
Expected Result
B.8
Result
Testing LAG
Estimated Duration
The estimated duration of this test is one hour.
Test Procedure
Table B-7 details the LAG test procedure.
Table B-7. LAG Test Procedure
#
Action
Expected Result
B-10
Testing LAG
Result
Action
Expected Result
Port 2 status is Up
Port 1 status is Up
Port 2 status is Up
Port 1 status is UP
Port 1 status is Up
Port 2 status is Up
Port 2 status is Up
Result
Testing LAG
B-11
Action
Expected Result
Port 1 status is Up
Port 2 status is Up
Port 1 status is Up
Port 2 status is Up
Port 2 status is Up
Port 2 status is Up
10
11
12
B-12
Testing LAG
Result
Action
Expected Result
Result
13
Port 2 status is Up
16
src-ip
B.9
Testing SNTP
Estimated Duration
The estimated duration of this test is 30 minutes.
Test Procedure
Table B-8 details the SNTP test procedure.
ETX-1 Ver. 1.20
Testing SNTP
B-13
Action
Expected Result
Result
Estimated Duration
The estimated duration of this test is 30 minutes.
Test Procedure
Table B-9 details the fault propagation test procedure.
Table B-9. Name of Table
#
Action
Expected Result
B-14
Result
Verify that user ports 3, 4, 5 and6 of ETX1(A) and ports 1 and 2 of ETX-1(C) change
their status to down
Action
Expected Result
Result
Estimated Duration
The estimated duration of this test is 15 minutes.
Test Procedure
Table B-10 details the traps and events test procedure.
Table B-10. Traps and Events Test Procedure
#
Action
Expected Result
Dying Gasp:
Power failure:
Result
B-15
Action
Expected Result
Soft Sync:
Result
Hard sync:
Estimated Duration
The estimated duration of this test is ten minutes.
Test Procedure
Table B-11 details the file transfer test procedure.
Table B-11. File Transfer Test Procedure
#
Action
Expected Result
B-16
Result
ETX-1 (D) 4
ETX-1 (A)
5
3
ETX-1 (C)
NMS
6
1
2
IXIA
ETX-1 (B)
Figure B-2. ETX-1 Test Plan Layout for ERP and RSTP
Cable
Device Name
ETX-1(A) port 1
ETX-1(B)
ETX-1(A) port 2
ETX-1(D)
ETX-1(A) port 5
NMS
ETX-1(B) port 1
ETX-1(C)
ETX-1(B) port 2
ETX-1(A)
ETX-1(C) port 1
ETX-1(D)
ETX-1(C) port 2
ETX-1(B)
ETX-1(D) port 1
ETX-1(A)
ETX-1(D) port 2
ETX-1(A)
ETX-1(D) port 2
ETX-1(C)
Configuring Devices
This section explains how to configure test equipment and RAD devices. Use the
configurations files listed below to configure each device.
B-17
Configuration File
ERP
RSTP
Estimated Duration
The estimated duration of this test is one hour.
Test Procedure
Table B-14 details the Ethernet ring protection test procedure.
Table B-14. Ethernet Ring Protection Test Procedure
#
Action
Expected Result
B-18
Testing ERP
Result
Action
Expected Result
Reboot ETX-1(C)
Result
Estimated Duration
The estimated duration of this test is one hour.
Test Procedure
Table B-15 details the rapid spanning tree protocol test procedure.
Testing RSTP
B-19
Action
Expected Result
Result
B-20
Testing RSTP
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
www.rad.com