Professional Documents
Culture Documents
Version 6.1
ECI's qualification lab is accredited by A2LA for competence in electrical testing according to
the International Standard ISO IEC 17025-2005 General Requirements for the Competence of
Testing and Calibration Laboratories.
8.14.4 Changing Priority Bit to CoS Mapping for E-NNI Ports .......................................................... 8-58
8.14.5 Changing CoS to P-Bit Mapping for E-NNI Ports.................................................................... 8-59
8.14.6 Changing DSCP CoS Mapping for UNI Ports .......................................................................... 8-59
8.14.7 Changing DSCP CoS Mapping for E-NNI Ports ....................................................................... 8-60
8.14.8 Complete CLI Configuration Example .................................................................................... 8-61
8.15 Configuring ERP Options...................................................................................................8-62
8.15.1 Configuring VSIs for ERP Protection ...................................................................................... 8-64
8.15.2 Configuring VSIs for ERP Protection on Non-Aggregation Access Ring Nodes ...................... 8-64
8.16 Configuring Ethernet and Packet Handling Port Options ...................................................8-65
8.17 Configuring EXP Mapping Options ....................................................................................8-69
8.17.1 Configuring EXP Mapping on an MPLS Interface................................................................... 8-71
8.17.2 Configuring EXP Mapping under a Routing Instance............................................................. 8-73
8.17.3 Deleting a Specific EXP Mapping ........................................................................................... 8-76
8.17.4 Deleting a Complete EXP Mapping Set.................................................................................. 8-76
8.18 Configuring Fault Management Options ...........................................................................8-77
8.18.1 Default Severity Profile at the Card Level.............................................................................. 8-78
8.18.2 Editing a Severity Profile ....................................................................................................... 8-78
8.18.3 Deleting a User-Defined Severity Profile ............................................................................... 8-79
8.18.4 Modifying a Severity Profile Configuration ........................................................................... 8-79
8.18.5 Displaying Alarms (Two Methods)......................................................................................... 8-80
8.19 Configuring FDB Card Parameters.....................................................................................8-81
8.20 Configuring LAG Options ..................................................................................................8-81
8.20.1 Typical LAG Configuration Work Flow ................................................................................... 8-83
8.20.2 Configuring the LAG Master .................................................................................................. 8-84
8.20.3 Configuring LAG Slaves .......................................................................................................... 8-85
8.20.4 Deleting a LAG Slave .............................................................................................................. 8-85
8.20.5 Deleting a LAG Master........................................................................................................... 8-86
8.20.6 Configuring the LAG Link Down Threshold............................................................................ 8-86
8.20.7 Deleting the LAG Link Down Threshold ................................................................................. 8-87
8.20.8 Enabling/Disabling LAG Distribution ..................................................................................... 8-87
8.20.9 Retrieving LAG Group Information for a Specific Slot ........................................................... 8-88
8.20.10 Retrieving LAG Group Information for a Specific Slot and Port ............................................ 8-89
8.21 Configuring Layer 2 Ethernet Options ...............................................................................8-89
8.22 Configuring Link OAM Options .........................................................................................8-91
8.23 Configuring LLCF Options .................................................................................................8-93
8.24 Configuring IGMP Options ................................................................................................8-93
8.25 Configuring MPLS Options ................................................................................................8-93
9 ONCP............................................................................................................... 9-1
9.1 ONCP Data Values ..............................................................................................................9-3
9.2 Displaying ONCP Data Values .............................................................................................9-4
NOTE: The CLI commands and parameters provided in this book are part of a comprehensive
system implementation developed for a wide range of platforms and devices. Some of the
specific commands and parameters that are included in these code fragments are not
supported in the current version of ShadeTree. In addition, not every user has full privileges to
perform commands in the CLI. Therefore, you might not be able to run some of the commands
described in this manual, with the specific syntax and parameters listed.
ASON Trail Restoration. Describes how to work with ASON trail protection and restoration
parameters.
Configuring Protection Mechanisms. Outlines the configuration required for cards and ports to
support these protection schemes; the commands that can be used to modify protection temporarily
during maintenance operations; and the commands that can be used to view and troubleshoot
protected entities.
Upgrading the Software. Describes how to view and upgrade the NE software version.
WARNING: failure to follow directions could result in bodily harm or loss of life.
LASER WARNING: how to avoid personal injury. All personnel involved in equipment
installation, operation, and maintenance must be aware that laser radiation is invisible.
Therefore, although protective devices generally prevent direct exposure to the beam,
personnel must strictly observe the applicable safety precautions and, in particular, must
avoid staring into optical connectors, either directly or using optical instruments.
ESD: information on how to avoid discharge of static electricity and subsequent damage to
the unit.
TIP: helpful information and handy hints that can make your task easier.
NOTE: In the CLI, slot names begin with the letter u followed by the slot number.
For example, the location that houses Slot 0 is called u0 in the CLI. The ports on the sNPB
(located on the RCP card) are considered to be in slots ua (RCP-A) or ub (RCP-B).
Card slots are organized for use with the following card combinations:
24 universal I/O slots, with slot allocation optimized per application:
Up to 4 slots that can be used for either fabric cards or service and photonic cards, identified as
slots u8, u9, u10, and u11. In the preceding figure, these slots are identified as slot#/FM_#,
indicating that they can be used for standard service cards or fabric cards, depending on the
platform configuration.
An additional 20 slots for service and photonic cards, referred to as slots u0-u7 and u12-u23.
Two slots for redundant Routing Control Processor (RCP_24T) cards that may include optional sNPB
modules. These slots are identified as slots ua and ub.
The OPT9624 can be configured with different fabric matrix cards, or without fabric at all, to support
various applications. Depending on the fabric installation, there are three main configurations:
High capacity 1 Tbps fabric, suitable for mixed OTN and data applications.
Medium capacity 100 Gbps fabric, suitable mainly for metro applications, supporting data, OTN, and
optic cards.
No fabric, suitable for pure WDM applications.
The following figures depict the layout of the three OPT9624 configurations:
Figure 2-2: OPT9624 with four FM1000 cards
For a more detailed description of the various card types available, refer to the Reference Manual of the specific device.
Where:
type is the type of port interface, such as ge for a GbE interface or lo0 for a loopback interface.
slot is chassis slot in which the card is inserted, such as u0 for the first slot in a 9600 chassis or sa-u0
for the first slot in a subtending Artemis shelf. For more information about subtending shelves, see
Multi-Shelf Configuration.
port is the number of the card port.
channel is the channel number.
2channel is the DS-1/E-1 channel number, if relevant.
group-unit is the group and unit number, if relevant.
channel-group is the channel of the first DS-0 channel in the channel group interface, if relevant.
logical is the logical interface number, if relevant.
The numbering on ROADM cards refers to degree ports, but a similar principle applies. For example, on a
ROADM_9A50 card, the ports in a single row are numbered from left to right, with the port on the far left
for local use or for Degree 1, the second for Degree 2, and so on, until you reach the port on the far right
side, used for Degree 9.
Figure 2-11: ROADM_9A50 card - OPT9600 series
The port numbering on REG40 regenerator cards follows the same left-to-right pattern when looking at the
card standing vertically.
Figure 2-12: REG40 card - OPT9600 series
If the ports are arranged on multiple rows, then in most cards the port on the upper left-hand side of the
card when the card is inserted horizontally into the chassis is Port 0. The port numbering increments from
left to right for the ports along the top row, then continues from left to right for the ports on the bottom
row.
For example, this is the port numbering scheme on the 12-port SP_MM_4 and SP_SM_4 splitter cards,
running from Port 0 to Port 5 along the top row, and from Port 6 to Port 11 along the bottom row. The
10-port SP_CE_2 splitter card follows the same pattern with 5 ports on each row, numbered from Port 0 to
Port 4 along the top row and from Port 5 to Port 9 along the bottom row.
In the CMXD8, OADMC8_21, and FOADM850_21 cards, the port numbering refers to channels, but a similar
principle applies. The first group of ports runs from left to right along the upper row, and the second group
runs from left to right along the bottom row. Similarly in the MXD44, ports are numbered left to right from
Port 1 to Port 22 along the upper row, and Port 23 to Port 44 along the bottom row. In the MXD88, the
ports are arranged in four rows of 22 ports each, similarly numbered from left to right, with the numbering
again beginning with the left side port in the top row. The following figure illustrates the port numbering on
a 10-port GbE NPB card.
Figure 2-13: OPT9600 series 88-port MXD88 card
Ports on AoC10 and FIOMR_16 cards are numbered slightly differently. Both cards provide 16 SFP-based
client ports arranged in three groups, as follows. When the card is inserted horizontally into the chassis, the
port on the lower left-hand side of the card is Port 0. The port numbering increments from left to right for
six ports along the bottom left side (Port 0 - Port 5). Port numbering then continues from left to right for six
ports along the top left side (Port 6 - Port 11). The last group of four SFP ports increment from left to right
for four ports along the bottom right side (Port 12 - Port 15). The AoC10 card also provides two XFP-based
OTU-2 line ports are located on the upper right side (Port 16 and Port 17). The following figure illustrates
the port numbering on an 18-port AoC10 card.
Figure 2-14: OPT9600 series 18-port AoC10 card
2.5.1 OTN
Optical Transport Network (OTN) technology, supported by the OPT9600 platforms, offers a range of rates
up to 100Gbps. OTN interfaces are supported through the following types of ports:
Optical Transmission Section (OTS) ports for equipment with more than one wavelength, supporting
OMS and xOCH interfaces. Used, for example, in amplifiers or DCF cards, or in OADM or Mux/DeMux
cards for channelization purposes.
Optical Channel Ports (OCHP), for single-wavelength OCH interfaces.
Optical Transport Unit (OTU) ports, for port rates ranging from OTU1 to OTU4, for comparable ODUk
interfaces ranging from ODU0 to ODU4. Used, for example, in OTU2 ports in TR10_4 cards, or for ODU
interfaces multiplexed to an OTUk port in an AoC10B or FIO10_5B card. Also used for ECI’s proprietary
ODUSlot interface for ports with interface rates under 2.5G on cards that predate V5.1.
Note that when you configure an OTU port, the software automatically creates the comparable high
order (HO) interfaces. If you wish to configure that OTU port for multiplexing, you must explicitly
define the low order (LO) ODUs to be multiplexed for that port.
NOTE: ODU0 and the set of ODUflex interfaces, working with payload type 21 (PT21), are
supported by cards from V5.1 and later. ODUSlot interfaces, working with PT20 and PT82, are
supported by cards that predate V5.1.
In the following table, all LO interfaces are implemented on cards from V5.1 and later using
PT21 unless otherwise noted.
The following table clarifies the correspondence between OTN ports and interfaces. These ports and
interfaces are identified in the CLI using the abbreviations listed in this table.
2.5.2 FC
Fibre Channel (FC) technology, supported by the OPT9600 platforms, offers a range of rates up to FC10G.
The following table clarifies the correspondence between FC ports and interfaces. These ports and
interfaces are identified in the CLI using the abbreviations listed in this table.
2.5.3 Video
Constant Bit Rate (CBR) technology is supported by the OPT9600 platforms. The following table clarifies
the correspondence between video ports and interfaces. These ports and interfaces are identified in the CLI
using the abbreviations listed in this table.
2.5.4 Management
Optical Supervisory Channel (OSC) technology is supported for an industry-standard range of management
channel ports:
1510 nm OSC port for DWDM applications.
1310 nm OSC port for CWDM applications.
100 Mbps (FE) OSC port.
2 Mbps OSC port.
Management ports are identified in the CLI using the abbreviations listed in the following table.
Port Types
oscchannel
osc100m
osc2m
osc-8
2.5.6 SDH/SONET
SDH/SONET technologies are supported for STM/OC ports using ODU interfaces. The following table
clarifies the correspondence between SDH/SONET ports and interfaces. These ports and interfaces are
identified in the CLI using the abbreviations listed in this table.
Layer 2 ports on the AoC10_L2 card have their own set of attributes and configuration options. The
following table introduces the attributes and options supported for Layer 2 ports.
Interface Types
dcu0
lo0
gre0
NOTE: The CLI examples provided in this section are for illustrative purposes only, to clarify
the style or syntax of a type of command. Some of the specific commands and parameters
used in these examples are not supported in the current version of ShadeTree. In addition, not
every user has full privileges to perform commands in the CLI. Therefore, you might not be
able to run some of the commands described in this manual, with the specific syntax and
parameters listed.
Where:
npb identifies the NPB card slot location:
rcpa-np and rcpb-np are the sNPB modules on the RCP cards in slots ua and ub.
Where:
slot is the chassis slot in which the card is located:
ca, cb - Slots RCPA and RCPB (9600 CTM module)
u0, u2, ..., uN-1, uN – Slots NPB0 through NPBN, where N depends on the number of slots in
that specific chassis
ua, ub – Slot RCPA and RCPB (9600 sNPB module)
sa-u1, sa-u2... sa-u6, sa-u7 - Slots in subtending shelf A, where used
sb-u1, sb-u2... sb-u6, sb-u7 - Slots in subtending shelf B, where used
sc-u1, ..., sl-u7 - Slots in subtending shelves C through L, where used
For more information about subtending shelves, see Multi-Shelf Configuration.
NOTE: For more information about slot numbering, see Chassis Slot Layout.
card-name is the name of the card, such as aoc10b or fio100. For a complete list of the cards and
their naming abbreviations, see Card Types.
mode is the running mode, pb (default) or mpls-pe, relevant for aoc10-l2 only.
port is the number of the port being configured.
port-type is the type of interface being configured for this port.
HO-interface and LO-interface information is optional, depending on the card configuration
and use. Interface configuration is explained in the following section.
The following figure provides a graphic illustration of the relationship between ODUs and the
corresponding TPN and tributary slot values when working with PT21. Note that the system supports single
stage multiplexing with different LO-ODU, ODUk, and/or ODU-Flex (CBR) such as ODUf-fc400 at the same
level.
Figure 2-15: Relationship between ODU interfaces and their component TPN and tributary slot
combinations
V5.1 supports ODUk both P20 and P21 multiplexing schemes. PT20 is supported on service cards released
prior to V5.1, such as AOC10 and FIOMR_16. PT21 is supported on service cards released as of V5.1 and
later, such as FIO100, FIOMR_16B, and AOC10B.
While the PT21 multiplexing scheme is flexible, with PT20 the tributary slot allocation is fixed. The LO-ODUs
in PT20 are only ODUk, with ODU0 supported only under ODU1. The following figure illustrates the fixed
multiplexing structure used for PT20. To distinguish between the different ODUs, each LO-ODUk occupies a
pre-defined TPN, and the corresponding list of TSs cannot be edited. In this figure, four ODU2s are
multiplexed into an ODU3e. The tributary slots for each TPN are identified by color. For example, TPN 1
uses tributary slots 1, 5, 9, and 13, colored purple in the following figure.
Figure 2-16: PT20 multiplexing structure
Multiplexing information is stored in a Multiplex Structure Identifier (MSI) structure that includes the TPN
and ODTU type information, as illustrated in the following figure.
Figure 2-17: MSI structure
The following table lists the corresponding ODU rates, multiplexing schemes, ODU types, and TPN values.
The following command configures port 0 of an FIO100 card located in slot u6. The HO interface is an
ODU with a rate of ODU4, the LO interface is an ODU2, the Tributary Port Number (TPN) is 2, and the
operator is selecting 8 specific tributary slots to be assigned to this port.
set chassis slot u6 fio100 port 0 odu 1 odu odu2-TPN2 tributary-slots
2,12,22,32,42,52,62,72;
After entering the preceding set chassis command, entering a show chassis command would
typically list the following port parameter values. (Note that most of these values are default settings
or automatically detected by the system. Parameter values that were set through the preceding
command line are highlighted in the following listing.)
...
tpn 2;
msi-expected-tpn 2;
tributary-slots 2,12,22,32,42,52,62,72;
tim-monitor disable;
tti-expected-sapi "Apollo Port";
tti-sent-sapi "Apollo Port";
tti-expected-dapi 0000000000000000;
tti-sent-dapi 0000000000000000;
tti-sent-operator 00000000000000000000000000000000;
payload-type-expected unknown;
payload-type-sent unknown;
plm-monitor disabled;
deg 10e-9;
force-ais disabled;
send-ais disabled;
send-bdi disabled;
send-csf disabled;
pattern-type-tx off;
pattern-type-rx off;
severity-profile default;
pm-profile default;
alarm-master-mask enable;
plm-consequent-action disabled;
tim-oci-lck-consequent-action disabled;
pm-monitor enabled;
Tributary port number (TPN) provides the port number to be used as part of the ODUk multiplexing
scheme. Values defined based on ODU type. For example, a typical port configuration listing may
display:
port 1 {
interface-type otu2;
otu3-options {
...
}
odu {
type odu2;
...
...
expected-payload-type 5;
sent-payload-type 5;
deg 10E9;
odu oduf-fc400-TPN1 {
tributary-slots 1,3,5,7;
...
}
odu oduf-fc400-TPN2 {
tributary-slots 2,4,6,8;
...
}
odu odu1-TPN3 {
...
}
odu odu1-TPN4 {
...
}
...
}
}
interfaces {
odu2-u1/1:1;
oduf-fc400-u1/1:1:TPN1;
oduf-fc400-u1/1:1:TPN2;
odu1-u1/1:1:TPN3;
odu1-u1/1:1:TPN4;
Port 12
port-u18/12 N/A Up Not Present
Port 13
port-u18/13 N/A Up Not Present
Port 14
port-u18/14 N/A Up Not Present
Port 15
port-u18/15 N/A Up Not Present
Port 16
port-u18/16 N/A Up Not Present
OTU otu2-u18/16 N/A Up Not Present
Port 17 port-u18/17 N/A Up Not Present
Slot u19 fio10-5 N/A Up Up
Port 0 port-u19/0 N/A Up Down
OTU otu2-u19/0 N/A Up Down
Port 1 port-u19/1 N/A Up Not Present
Port 2 port-u19/2 N/A Up Not Present
Port 3 port-u19/3 N/A Up Not Present
Port 4 port-u19/4 N/A Up Not Present
OTU otu2-u19/4 N/A Up Not Present
Slot u22 fio100 N/A Up Not Present
Port 0 port-u22/0 N/A Up Not Present
OTU otu3e-u22/0 N/A Up Not Present
Slot ua snpb1-2i N/A Up Not Present
(*) - No usable configuration available for the indicated slot.
(#) - Swap in failed for the indicated port.
The command displays installed service cards and all currently configured interfaces and subinterface. It
also lists the encapsulation type and the state of the interfaces.
NOTE: For more information about the show chassis configuration command, see the
Command Reference Manual.
The command displays the currently configured interfaces, whether the link is up, the protocol family
currently configured on that interface, and the address of the interface.
NOTE: For more information about the show interfaces command, see the Command
Reference Manual.
NE configuration is persistent and can be detached from the NE and saved to another location on the
network.
In the event that one or more subtending shelves are out of service, as long as the main controller card is
operational within the main shelf, it is still possible to access PM history, logs, and status of all (functioning)
shelves, and to perform configuration operations. It is also possible to view a partial status of a faulty or
disconnected subtending shelf. Partial configuration and retrieval of PM history, and logs may also be
possible.
If the main shelf malfunctions, and/or its controller card is removed, management of the main shelf, and/or
any of the subtending shelves is suspended, until such time as recovery of the main controller card is
complete.
In addition, the following parameters should also be configured explicitly at the NE-level:
External input alarm configuration: to operate the external input dry contacts.
External output alarm configuration: to operate the external output dry contacts.
For details of how to configure these parameters see the System Overview and Configuration User Guide.
Example
set network-element opt96xx shelf s0 opt9624h fm1000
Example
set network-element opt96xx shelf sg artemis4a with-controller-card
Example
set chassis slot sb-u0 mxd16
See also Specifying a Chassis Slot, Card Name, Port, and Interface Configuration.
Once your card has been configured, configure ports, interfaces, Layer 1 cross connections, and fiber
connectivity as explained in the following sections. Be careful to specify the subtending slot name correctly,
using the shelf-slot syntax described here.
Configure the physical properties of the port at the [edit port] hierarchy level, as described in Port
Configuration.
When working with SDH/SONET service cards, configure interfaces at the [edit interfaces]
hierarchy level, as described in Interface Configuration.
When working with photonic, optical, or data cards, configure cross connections at the [edit cross
connections] hierarchy level, as described in Cross Connection Configuration.
Configure fiber connectivity at the [edit port] hierarchy level, as described in Fiber Connectivity.
NOTE: Removing a subtending shelf does not cause a service interruption to shelves within
the same multi-shelf NE.
a. For each XC that participates in a trail, delete the trail ID, type commit and then delete all XCs
again. To delete a XC trail ID, at the root level, type:
delete cross connects <XC name> trail-id
2. To delete all cards residing on the shelf, at the root level, type:
user@root# delete chassis slot <slot>
3. To delete the subtending shelf, at the root level, type:
user@root# shelf shelf shelftype
Example
Deleting all XCs:
user@root# delete cross-connects
Deleting a specific trail ID:
user@root# delete cross-connects odu1-xc trail-id
Deleting all cards:
user@root# delete chassis slot sa-u0 mxd16
Deleting the subtending shelf:
user@root# delete network-element opt96xx shelf sa artemis2p
NOTES:
CLI commands can be used to configure a wide range of features, as explained in this
section. Not all features are relevant for all types of cards. This section begins with an
explanation of the minimal requirements for port configuration, including the basic
command syntax (Minimum Port Configuration). Other features and attribute
configuration settings are then listed in alphabetical order.
RCP cards contain management and auxiliary interface ports. This section does not discuss
the management or auxiliary interfaces. For information about configuring these
interfaces, see the System Overview and Configuration User Guide.
Interface configuration is described in Interface Configuration.
Cross connection configuration is described in Cross Connection Configuration.
Fiber connectivity configuration is described in Fiber Connectivity.
Layer2 Ethernet port configuration is described in Configuring Layer2 Ethernet Ports.
The CLI examples provided in this section are for illustrative purposes only, to clarify the
style or syntax of a type of command. Some of the specific commands and parameters
used in these examples are not supported in the current version of ShadeTree. In addition,
not every user has full privileges to perform commands in the CLI. Therefore, you might
not be able to run some of the commands described in this manual, with the specific
syntax and parameters listed.
Example
The following example configures port 1 and port 2 on a 10-port GbE NPB card located in slot u0 on an
OPT9600 device. The ports are disabled by default.
chassis {
slot u0 npb1-10ad {
port 1;
port 2;
}
}
NOTE: Because different types of cards have a varying number of ports, the CLI allows you to
enter up to 40 ports for any type of card. However, if you try to configure a non-existent port
on a card, you will be unable to commit the configuration.
If the port is located on a card that resides on a subtending shelf of a multi-shelf NE, include
the subtending shelf name with the slot number (for example, sa-u0). For more information
about subtending shelves, see Multi-Shelf Configuration.
Example
The following example configures port 1 and port 5 on a 20 port GbE NPB card located in slot u3 on a
device. The ports are disabled by default.
chassis {
slot u3 phyc-20p-ge {
port 1;
port 5;
}
}
NOTE: To disable a port after it has been enabled, delete the enable statement and commit
the configuration.
TIP: Very often the user does not have to explicitly set the port attribute values because the
system automatically configures the most appropriate settings for the specific port being
configured; see the System Overview and Configuration User Guide.
cbr-options {
csf-tsf-action (lol | none | lf | ndc | nos | v-char | pn-11);
gfp-consequent-action (enable | disable);
send-csf (enable | disable);
see Configuring CBR Options
}
ety-options {
csf-tsf-action (lol | none | lf | ndc | nos | v-char | pn-11);
max-frame-size <max-frame-size>;
lf-rf-mode (local | transparent);
send-csf (enable | disable);
test-mode (normal | test);
tx-pattern (none | pseudorandom | prbs31 | idles | off);
rx-pattern (none | pseudorandom | prbs31 | idles | off);
gfp-consequent-action (enable | disable);
gfp-upi-values (standard | xdm);
see Configuring ETY Options
}
fc-options {
csf-tsf-action (lol | none | lf | ndc | nos | v-char | pn-11)
gfp-consequent-action (enable | disable);
send-csf (enable | disable);
see Configuring FC Options
}
osc100-options {
wavelength (non-colored);
}
osc2m-options {
wavelength (non-colored);
}
see Configuring OSC Options
odu odu {
type (none | odu-slot | odu1 | odu2 | odu3 | odu2e | odu3e |
odu2f | odu4 | odu0 | oduf-sdi3g | oduf-fc400 | oduf-fc800 |
och | oms | os | spo | oc | ull-ety10goc | ull-fc800 |
ull-fc1200 | ull-fc1600);
odu-attributes-list;
see Configuring ODU Options
}
oms {
oms-attributes-list;
see Configuring OMS Options
}
och {
och-attributes-list;
see Configuring OCH Options
}
spo spo {
spo-attributes-list;
see Configuring SPO Options
}
os;
ull;
encapsulation (frame-relay | ppp | atm | cisco-hdlc | dix);
encapsulation (dix | multilink-ethernet);
ethernet-options {
(auto-negotiation | no-auto-negotiation);
(flow-control | no-flow-control);
link-mode (full-duplex | half-duplex);
ifg-optimization (enabled | disabled);
speed (10g | 1g | 100m | 10m);
pma-mode (master | slave);
port-mode (uni | e-nni | i-nni | moe | i-moe | mirror);
stpId <stpId>;
llcf-options {
llcf-ingress-enable (enabled | disabled);
llcf-egress-enable (enabled | disabled);
}
pause-options {
force-pause (enabled | disabled);
pause-type (rx-only | disable);
pause-advertisement (no-pause | sym-pause |
asym-pause | sym-asym-pause);
}
rstp-options {
port-enable (enabled | disabled);
priority <priority>;
path-cost <path-cost>;
hold-off-time <hold-off-time>;
port-change-detect (enabled | disabled);
dynamic-port-cost-update (enabled | disabled);
admin-edge (enabled | disabled);
auto-cost-config (enabled | disabled);
bpdu-mac-address (bridge-group | provider-bridge-group);
}
}
dcn;
force_ms (ais | rdi);
hold-time-up hold-time-up;
queue-block qname;
scheduler scheduler-name;
policer-block pbname;
remote-fault-disable;
cac-pirmax-algorithm (flat | hierarchical);
cac-failure-action (syslog | userlog | reject);
cac-syslog-level (debug | event | audit | warn);
scheduling-mode (access | trunk);
scheduling-model scheduling-model;
loopback (remote | local);
oschannel-options {
wavelength (non-colored);
}
sdh-options {
section-trace section_trace;
ber-sf (10e-5 | 10e-4 | 10e-3);
ber-sd (10e-9 | 10e-8 | 10e-7 | 10e-6 | 10e-5);
tx-clock (loop | local | system);
}
vlan-tagging;
} // end port configuration
enable;
ains (enable | disable);
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
oa-options {
edfa-mode (none | automatic | constant | semiautomatic);
initial-gain <initial-gain>;
tilt <tilt>;
max-number-channels <max-number-channels>;
amplifier-state (on | off);
output-pwr-per-channel <output-pwr-per-channel>;
exp-raman-gain <exp-raman-gain>;
tilt-offset <tilt-offset>;
response-to-los
(immediate-shut-down | delay-50-msec-shut-down);
}
passive-oadm-options <first-channel>;
roadm-options (roadm | terminal | dge | directionless | collector);
total-channels-options <total-channels>;
dcf-fiber-length-options <dcf-fiber-length>;
tr100-options (transponder | regenerator);
layer2-ethernet-options {
mode (pb | mpls-pe);
ethernet-network-id <ethernet-network-id>;
bridge-options {
pm-monitor (enable | disable);
pm-profile <pm-profile>;
rstp-options {
rstp-notifications (enabled | disabled);
bridge-priority <priority>;
max-age <max-age>;
hello-time <hello-time>;
forward-delay <forward-delay>;
bpdu-frame-format (standard | standard-b);
tx-hold-count <tx-hold-count>;
}
cfm-options {
ltm-flooding (enabled | disabled);
local-mep-id <local-mep-id>;
}
ccn-options {
ccn (enabled | disabled);
ccn-forwarding (enabled | disabled);
}
port-mirroring-options {
source-port <source-port>;
ingress-dest-port <ingress-dest-port>;
egress-dest-port <egress-dest-port>;
}
}
fdb-options {
age-time <age-time>;
over-quota-action (forward | drop);
pm-monitor (enable | disable);
}
mpls-pe-options {
pe-id <pe-id>;
mpls-id <mpls-id>;
}
tm-options {
high-priority-cos-delimiter
<high-priority-cos-delimiter>;
per-cos-tm {
cos <cos> {
best-effort-cos (enabled | disabled);
over-booking-factor <over-booking-factor>;
}
}
}
}
}
Where customer is the name of a customer. If the name includes special characters, enclose the customer
name in quotes (").
If the port is located on a card that resides on a subtending shelf of a multi-shelf NE, include the subtending
shelf name with the slot number (for example, sa-u0). For more information about subtending shelves, see
Multi-Shelf Configuration.
Number of Port Label Port Number Port Role Port Type Sub-IF Type
Ports
2 C1, C2 0,2 Client STM64 ODU2
OC192 ODU2
FC800 ODU2
FC1200 ODU2f
ETY10GOC ODU2e
OTU2 ODU2
OTU2e ODU2e
2 L1, L2 1,3 Line OTU2/2e/2f ODU2/2e/2f
To configure the TR10_4EN encryption capabilities, the network operator must define the relevant security
certificate and peer IP address, using the following two CLI commands.
For example:
odu odu {
type (none | odu-slot | odu1 | odu2 | odu3 | odu2e | odu3e | odu2f | odu4 | odu0
| oduf-sdi3g | oduf-fc400 | oduf-fc800 | och | oms | os | spo | oc | ull-ety10goc
| ull-fc800 | ull-fc1200 | ull-fc1600);
tpn tpn;
tributary-slot tributary-slot;
tim-monitor (sapi | dapi | both | disable);
tti-expected-sapi tti-expected-sapi;
tti-sent-sapi tti-sent-sapi;
tti-expected-dapi tti-expected-dapi;
tti-sent-dapi tti-sent-dapi;
tti-sent-operator tti-sent-operator;
spo spo {
tim-monitor (enabled | disabled);
expected-tti expected-tti;
sent-tti <sent-tti>;
expected-signal-label (unequipped | tug-structure | gfp-mapping);
sent-signal-label (unequipped | tug-structure | gfp-mapping);
plm-monitor (enabled | disabled);
deg (10e-6 | 10e-7 | 10e-8 | 10e-9);
exc (10e-3 | 10e-4 | 10e-5);
severity-profile severity-profile;
pm-profile pm-profile;
alarm-master-mask (enable | disable);
pm-monitor (enabled | disabled);
tim-consequent-action (enabled | disabled);
plm-consequent-action (enabled | disabled);
}
gcm-mode (standard | monitor);
}
Note that ODU port interfaces include support for hierarchical attribute configuration nesting to multiple
levels. This means that a higher-capacity OTU port can support a single corresponding high-order ODU
interface or a multiplexed group of low-order ODU interfaces. Attributes configuring the multiplexed
L1 interfaces can be nested up to three levels deep. ODU port interfaces can also be configured to work
with a single level of nesting for SPO sub-interfaces where configured for XDM-AoC functionality. SPO
attributes are listed in Configuring SPO Options.
oms {
wdm-type (na | cwdm | dwdm | non-colored);
first-wavelength (non-colored);
last-wavelength (non-colored);
space space;
och och {
power-offset power-offset;
rx-wavelength (non-colored);
tx-wavelength (non-colored);
severity-profile severity-profile;
alarm-master-mask (enable | disable);
}
}
Note that OMS ports include support for a single level of nesting for OCH sub-interfaces. OCH attributes are
listed in Configuring OCH Options.
port port {
...
os;
...
osc100-options {
wavelength (non-colored);
}
osc2m-options {
wavelength (non-colored);
}
oschannel-options {
wavelength (non-colored);
}
ots-options {
als-state (enabled | disabled);
los-threshold <los-threshold>;
osc-channel-peer osc-channel-peer;
}
otu-options {
tim-monitor (sapi | dapi | both | disable);
tim-ca (enabled | disabled);
fec-mode (fec | efec4 | efec7 | efec7-10 | efec7-13 | sd-fec);
fec-ignore (enabled | disabled);
send-bdi (enabled | disabled);
gcc-termination (disable | 0 | 1 | 2);
gcc-mode (standard);
tti-expected-sapi tti-expected-sapi;
tti-expected-dapi tti-expected-dapi;
tti-sent-sapi tti-sent-sapi;
tti-sent-dapi tti-sent-dapi;
tti-sent-operator tti-sent-operator;
deg (10e-9 | 10e-10 | 10e-11 | 10e-12);
odu-ais-to-lol (enabled | disabled);
gmpls-options (uni | nni) {
remote-node <remote-node>;
remote-interface <remote-interface>;
remote-flat-port <remote-flat-port>;
remote-mpls-if-index <remote-mpls-if-index>;
auto-discovery (enabled | disabled);
auto-discovery-state (none | not-done | succeeded |
failed);
link-length <link-length>;
link-cost <link-cost>;
trib-slot-for-restoration (u0 | u1 | u2 | u3 | u4 | u5 | u6 | u7 | u8 | u9 |
u10 | u11 | u12 | u13 | u14 | u15 | u16 | u17 | u18 | u19 | u20 | u21 | u22 | u23
| ua | ub | ca | cb | sa-u0 | sa-u1 | sa-u2 | sa-u3 | sa-u4 | sa-u5 | sa-u6 | sa-u7
| sb-u0 | sb-u1 | sb-u2 | sb-u3 | sb-u4 | sb-u5 | sb-u6 | sb-u7 | sc-u0 | sc-u1 |
sc-u2 | sc-u3 | sc-u4 | sc-u5 | sc-u6 | sc-u7 | sd-u0 | sd-u1 | sd-u2 | sd-u3 | sd-u4
| sd-u5 | sd-u6 | sd-u7 | se-u0 | se-u1 | se-u2 | se-u3 | se-u4 | se-u5 | se-u6 |
se-u7 | sf-u0 | sf-u1 | sf-u2 | sf-u3 | sf-u4 | sf-u5 | sf-u6 | sf-u7 | sg-u0 | sg-u1
| sg-u2 | sg-u3 | sg-u4 | sg-u5 | sg-u6 | sg-u7 | sh-u0 | sh-u1 | sh-u2 | sh-u3 |
sh-u4 | sh-u5 | sh-u6 | sh-u7 | si-u0 | si-u1 | si-u2 | si-u3 | si-u4 | si-u5 | si-u6
| si-u7 | sj-u0 | sj-u1 | sj-u2 | sj-u3 | sj-u4 | sj-u5 | sj-u6 | sj-u7 | sk-u0 |
sk-u1 | sk-u2 | sk-u3 | sk-u4 | sk-u5 | sk-u6 | sk-u7 | sl-u0 | sl-u1 | sl-u2 | sl-u3
| sl-u4 | sl-u5 | sl-u6 | sl-u7);
port port {
...
passive-oadm-options first-channel;
...
}
port port {
...
po-options;
...
}
port port {
...
port-behavior (uni-in | uni-out | bidirectional | uni-in-out);
...
}
port port {
...
direction (uni-in | uni-out | bidirectional | uni-in-out);
...
}
port port {
...
loopback (local | remote);
...
}
port port {
...
port-mapping port-mapping;
...
}
Port and interface options are described in Port and Interface Types.
port port {
...
roadm-options (roadm | terminal | dge | directionless | collector);
...
}
port port {
...
tr100-options (transponder | regenerator);
...
}
transceiver-options {
exp-transceiver-type (none | etgbe | etr1 | etsdi | otc10-alxx |
otc10-psxx | otc25-alxx | otc25-psxx | otgbe-ex | otgbe-l3bd |
otgbe-l5bd | otgbe-lx | otgbe-s3bd | otgbe-s5bd | otgbe-sx |
otgbe-zx | otr1-l3 | otr1-l5 | otr1-s3 | otr1-v5 | otr1-vl5 |
otr1-x3 | otr1-x5 | otr10-alxx | otr10-asxx | otr100-lr4 |
otr100-lr10 | otr100-sr10 | otr100-lr4dr | otr100-sr10dr |
otr100pt-c1200 | otr100ptf-c1200 | otr100p2-lr4 | otr100p2-lr10 |
otr100p2-sr10 | otr103-er | otr103-lr | otr103-sr |
otr103-zr | otr10t-al | otr10t-nb-al | otr16-i3 | otr16-l3 |
otr16-l3bd | otr16-l5 | otr16-l5bd | otr16-mm | otr16-s3 |
otr16-s3bd | otr16-s5bd | otr25-abxx | otr25-avxx | otr2m-ulh |
otr4-l3 | otr4-l5 | otr4-s3 | otr4-v5 | otr64-al5 | otr64-pi3 |
otr64-ps5 | otfc4-mm | otfc4-s3 | otfc8-mm | otfc8-pi3 |
rz-dqpsk | dp-dqpsk | dp-dqpsk-40 | otr1-vl62 | otr1-vl59 |
otp40-lr4 | otp40-sr4 | otp10-sr | otp10-lrm | otp10-lr |
otp10-er | otp10-zr | otp10-s27bd | otp10-s33bd | otp10-l27bd |
otp10-l33bd | otp10d-alxx | otp10d-allmxx | otp10t-allm |
otp10t-alln | otp10c-psxx | otp10c-allmxx | otpmr-pi3 |
otpmr-ps5 | otpmr-allm5 | otpmrc-psxx | otpmrc-allmxx | otp8-mm |
otp8-pi3 | otp16-mm | otp16-pi3 | otp16d-allmxx | otp16d-asxx |
otp16d-psxx | otp8d-allmxx | alien-sfp | alien-xfp);
rx-wavelength (non-colored);
tx-wavelength (non-colored);
tx-enable (enable | disable);
tx-power <tx-power>;
als-state (enable | disable);
coherent (true | false);
config-chromatic-dispersion config-chrom-disp;
last-known-chromatic-disp last-known-chrom-disp;
}
To automatically configure the complete set of ULL options with settings optimized for the installed
equipment, include the following statement at the
[edit chassis slot slot card-name port port] hierarchy level:
port port {
...
ull;
...
The following show configuration and show interfaces statements illustrates the port configuration
settings for a ull-fc1600 port type.
enable;
port-mapping ull-fc1600;
port-type ull-fc1600;
port-behavior bidirectional;
direction bidirectional;
transceiver-options {
exp-transceiver-type otp16-pi3;
rx-wavelength non-colored;
tx-wavelength non-colored;
tx-enable enable;
als-state disable;
coherent false;
}
severity-profile default;
pm-profile default;
alarm-master-mask disable;
description none;
label P1;
pm-monitor enable;
ull;
NOTE: Not all attributes are relevant for all types of ports. Even when an attribute is relevant
for a specific type of port, not all the attribute values may be relevant for that port type. For
specific usage examples, see the relevant command line explanations provided previously in
this section.
TIP: Many of these attributes are preconfigured with default values appropriate for the
specific type of port being configured. To simplify port configuration, begin with the default
settings and change the attribute settings only as needed.
Attribute/
Options Usage guidelines
Keyword
ains enabled The system should (enabled) or should not (disabled)
disabled utilize automatic in-service functionality, by default
disabled.
alarm-master-mask enabled The system should (enabled) or should not (disabled)
disabled mask reporting of selected classes of alarms.
alien-lambda enabled The system should (enabled) or should not (disabled)
disabled interconnectivity with third party WDM transceivers
that are connected directly to ECI equipment, but are
not managed by ECI’s NMS.
alien-lambda-rx-options <attribute set> See Defining Fiber Connectivity for Alien Lambdas.
alien-lambda-tx-options
Attribute/
Options Usage guidelines
Keyword
allowed-fiber-loss-margin <numeric> The margin of fiber loss allowed before an alarm is
raised (dB). (Default: intra-fiber connectivity=0.1;
inter-fiber connectivity=3, and resolution=0.1.
Possible intra-fiber connectivity values=0-7.)
als-state enabled The system should (enabled) or should not (disabled)
disabled automatically implement an automatic laser
shutdown (ALS) for this transceiver port in case of Rx
loss error. Default setting depends on the port type.
amplifier-state off Current state of this amplifier module.
on
config-chromatic-dispersion config-chrom-di Sets the chromatic dispersion value for this
sp transceiver port. Range of -360 to +1200 ps/nm,
configurable in steps of 5 ps/nm.
connection-mode configurable All L1-XCs created explicitly by the user are
(default for configurable.
user-created All L1-XCs created automatically by the NE are
L1-XCs) fixed.
fixed This value cannot be edited once the L1-XC has
(default for been created.
NE-created
L1-XCs)
csf-tsf-action none In the case of csf (Client Signal Failure) or tsf (Trail
lol Signal Failure), the system should stop transmission
lf (lol - Loss of Light) or send a sequence (e.g., lf (Local
Fault) or ndc - Neutral Disparity Code) to the remote
ndc
client.
nos
v-char
pn-11
dcf-fiber-length-options <value> Length of the transmission fiber for whose dispersion
the DCF module is compensating.
deg 10e-6 Bit error rate threshold that triggers a degraded signal
10e-7 error condition. Depends on port rate for the installed
10e-8 hardware.
10e-9
10e-10
10e-11
10e-12
edfa-mode automatic EDFA mode configured for this amplifier.
constant
semiautomatic
Attribute/
Options Usage guidelines
Keyword
exc 10e-3 Bit error rate (BER) threshold that triggers an
10e-4 excessive BER condition. Usually applicable within an
10e-5 SPO context.
exp-raman-gain <value> Expected gain value configured for this RAMAN-type
amplifier.
exp-transceiver-type <expected- The type of transceiver module inserted into the port,
transceiver selected from a list of choices.
type>
Refer to the following list, subject to change:
none | etgbe | etr1 | etsdi | otc10-alxx | otc10-psxx | otc25-alxx |
otc25-psxx | otgbe-ex | otgbe-l3bd | otgbe-l5bd | otgbe-lx | otgbe-s3bd |
otgbe-s5bd | otgbe-sx | otgbe-zx | otr1-l3 | otr1-l5 | otr1-s3 | otr1-v5 |
otr1-vl5 | otr1-x3 | otr1-x5 | otr10-alxx | otr10-asxx | otr100-lr4 |
otr100-lr10 | otr100-sr10 | otr100-lr4dr | otr100-sr10dr | otr100pt-c1200 |
otr100ptf-c1200 | otr100p2-lr4 | otr100p2-lr10 | otr100p2-sr10 | otr103-er
| otr103-lr | otr103-sr | otr103-zr | otr10t-al | otr10t-nb-al | otr16-i3 |
otr16-l3 | otr16-l3bd | otr16-l5 | otr16-l5bd | otr16-mm | otr16-s3 |
otr16-s3bd | otr16-s5bd | otr25-abxx | otr25-avxx | otr2m-ulh | otr4-l3 |
otr4-l5 | otr4-s3 | otr4-v5 | otr64-al5 | otr64-pi3 | otr64-ps5 | otfc4-mm |
otfc4-s3 | otfc8-mm | otfc8-pi3 | rz-dqpsk | dp-dqpsk | dp-dqpsk-40 |
otr1-vl62 | otr1-vl59 | otp40-lr4 | otp40-sr4 | otp10-sr | otp10-lrm |
otp10-lr | otp10-er | otp10-zr | otp10-s27bd | otp10-s33bd | otp10-l27bd |
otp10-l33bd | otp10d-alxx | otp10d-allmxx | otp10t-allm | otp10t-alln |
otp10c-psxx | otp10c-allmxx | otpmr-pi3 | otpmr-ps5 | otpmr-allm5 |
otpmrc-psxx | otpmrc-allmxx | otp8-mm | otp8-pi3 | otp16-mm | otp16-pi3
| otp16d-allmxx | otp16d-asxx | otp16d-psxx | otp8d-allmxx | alien-sfp |
alien-xfp
expected-signal-label unequipped Type of signals expected. Usually applicable within an
tug-structure SPO context.
gfp-mapping
expected-tti <expected-tti> The TTI (Trail Trace ID) string expected by the system;
verified when working with TIM monitoring.
Attributes can be set explicitly for DAPI, Operator,
SDH/SONET, and SAPI contexts.
fec-ignore enabled The system should (enabled) or should not (disabled)
disabled ignore FEC (Forward Error Correction) alarms.
Attribute/
Options Usage guidelines
Keyword
fiber-connectivity uni-in Set this attribute to configure how the peer-port fiber
uni-out is connected (one-way in, one-way out, running in
bidirectional both directions, or two separate unidirectional trails).
uni-in-out
fiber-length <numeric> The length of the fiber (km).
(Intra-fiber connectivity values 0-500; resolution=0.1).
Attribute/
Options Usage guidelines
Keyword
gfp-consequent-action enabled The system should (enabled) or should not (disabled)
disabled implement the predefined "consequent actions" or
responses that have been configured for this port in
case of a GFP error.
gmpls-options Full set of values, GMPLS options are utilized for ASON protection and
usually set restoration, described in ASON Trail Restoration.
automatically by the Most of the attribute values are set automatically by
embedded system. the embedded system. The use can assign values to
some of the attributes, for example, to identify the
port as either UNI or NNI and set the port’s
"link-cost". Link-cost and link-length are ranking
values used to optimize segment selection for
ASON-protected trails.
index-for-io <value> Index value used for I/O actions.
initial-gain <value> Initial gain setting for the amplifier.
input-fiber-loss <value> The configured input fiber loss (dB). (Default value=0;
possible values 0-100; resolution=0.1)
is-connected false Boolean values indicates whether this interface is
true connected.
last-known-chromatic- last-known- Saves the last known chromatic dispersion value for
dispersion chrom-disp this transceiver port. Range of -360 to +1200 ps/nm.
last-wavelength <wavelength> Upper bound of supported wavelength range for this
port, when working with tunable transceivers.
Specific value depends on hardware capabilities.
Options include:
DWDM (17-60.5)
CWDM (1471-1611)
non-colored
lf-rf-mode local System reactions to certain types of fault conditions
transparent should be implemented either locally (local) or
network-wide (transparent).
los-threshold <value> Loss of Signal threshold that triggers an alarm.
management-buffer-b64 <value> Read-only, set at the NMS level.
Attribute/
Options Usage guidelines
Keyword
multi-wavelength true Indicates whether the module is configured to work
false with multiple wavelengths simultaneously.
multiplexing-scheme none Identifies the multiplexing scheme (if any) used by
transparent this port. Read-only, automatically detected.
pt-20
pt-21
pt-82
(ODU) type <odu-types> Type of ODU interface for which the port is being
configured.
Refer to the following list, subject to change:
odu-slot, odu1, odu2, odu3, odu2e, odu3e, odu2f, odu4, odu0, oduf-sdi3g,
oduf-fc400, oduf-fc800, och, oms, os, spo, oc, ull-ety10goc, ull-fc800,
ull-fc1200, ull-fc1600
odu-ais-to-lol enabled The ODU port should (enabled) or should not
disabled (disabled) shut down the laser if an Alarm Indication
Signals (AIS) alarm is triggered.
os --- Configure this port for OS (splitter/coupler)
functionality using preconfigured optimized settings.
osc-channel-peer <string> The channel of the corresponding (peer) osc channel.
Attribute/
Options Usage guidelines
Keyword
Refer to the following list, subject to change:
none | experimental | asyncronous | bit-syncronous | atm-mapping |
gfp-mapping | vcat-signal | transparent-ety | 1000basex-into-odu0 |
fc1200-into-odu2e | gfp-into-opu2 | stm1-gmp | stm4-gmp |
stm1-into-odu0 | odu-slot-proprietary | bitstr-with-octet |
bitstr-without-octet | odu-multiplex-jk | odu-multiplex-k-ts | na-55 | na-66
| null-test-signal | prbs-test-signal | gbe10-oc | fc-10g | fc-8g-gfp-mapping |
fc200-into-odu1 | cbr-mapping | fc100-gmp | fc400-flex | fc800-flex |
video270-gmp | hdsdi1485-gmp | hdsdi-3g-flex | na-ff | unknown
peer-ne unspecified The IP address of the peer router. Configured
<ip-address> explicitly for inter-fiber connectivity only.
peer-port <numeric> The number of the peer port number.
peer-slot <string> The shelf and slot name of the peer slot.
plm-consequent-action allow The system should (allow/enabled) or should not
disabled (disabled/inhibit) implement the predefined
enabled "consequent actions" or responses that have been
configured for this port in case of a PLM (payload
inhibit
mismatch) error.
plm-monitor enabled The system should (enabled) or should not (disabled)
disabled utilize PLM (payload mismatch) monitoring to check
for mismatches between expected and actually-sent
payload types.
pm-monitor enabled The system should (enabled) or should not (disabled)
disabled utilize performance monitoring (PM). Performance
monitoring can be configured at various hierarchical
levels for a wide range of system entities (see
Performance Monitoring in the System Overview and
Configuration User Guide).
pm-profile <pm-profile Specifies a user-defined PM profile to be applied.
name> Profiles are used to store sets of user-defined PM
thresholds. Traffic performance can be monitored
using either the default system settings or some
combination of user-defined settings (see
Performance Monitoring in the System Overview and
Configuration User Guide).
pmd <numeric> Polarized Mode Dispersion (PMD)
For intra-fiber connectivity, default=0.
For inter-fiber connectivity, PMD range=0-40,
resolution=0.1. Default PMD varies according to
fiber length: <10km=0; >10km=0.7sqrt.
po-options --- Configure this port for PO functionality using
preconfigured optimized settings.
Attribute/
Options Usage guidelines
Keyword
port-behavior uni-in By default, bidirectional ports are configured for
uni-out bidirectional cross-connection traffic flow. Set this
bidirectional attribute to configure bidirectional ports to support
unidirectional cross connections, and to identify the
uni-in-out
direction of the cross connection (one-way in,
one-way out, running in both directions, or two
separate unidirectional trails).
port-description <string> User comments providing information regarding
essential port characteristics.
port-direction uni-in Set this attribute to configure the direction of the
uni-out physical traffic flow for the port, (one-way in,
bidirectional one-way out, running in both directions, or two
separate unidirectional trails).
uni-in-out
port-mapping <port-mapping> Defines how to map various types of ports and/or
interfaces to a specific (sub)interface choice when
multiple interface options are available.
User chooses from the list of available options
provided by the CLI, including OCH, OMS, OS, and
various ODU types, as appropriate.
port-type <port type Type of port being configured, dependent on installed
value> hardware capabilities. Cannot be changed once the
port has been configured. To change the port type,
delete the current port and configure a new one.
power-offset <power-offset Specific the power offset, with the possible values
value> determined by the hardware capabilities. (N/A for
TFA cards.)
response-to-los immediate- Defines how this module should respond to a loss of
shut-down signal event; immediate shutdown or shut down after
delay-50-msec- a 50msec delay.
shut-down
roadm-options roadm Identifies the configuration of this ROADM module.
terminal
dge
directionless
collector
rx-pattern none When the system is running in test-mode, defines
idles what (if any) testing pattern should be used for signal
off transmission and reception.
pseudorandom
Attribute/
Options Usage guidelines
Keyword
rx-wavelength <wavelength> Input wavelength for this port. Specific value depends
on hardware capabilities. Must match expected
tx-wavelength. Options include:
DWDM (17-60.5)
CWDM (1471-1611)
non-colored
send-ais enabled The system should (enabled) or should not (disabled)
disabled send AIS signals.
send-bdi enabled The system should (enabled) or should not (disabled)
disabled transmit Backward Defect Indication (BDI) signals.
send-csf enabled The system should (enabled) or should not (disabled)
disabled send CSF (Client Signal Fail) signals.
sent-signal-label unequipped Type of signals actually sent. Usually applicable within
tug-structure an SPO context.
gfp-mapping
sent-tti <sent-tti> The TTI (Trail Trace ID) string actually sent by the
system; verified when working with TIM monitoring.
Attributes can be set explicitly for DAPI, Operator,
SDH/SONET, and SAPI contexts.
severity-profile <severity-profil Specifies a user-defined severity profile to be applied.
e name> Severity profiles are used to store sets of user-defined
alarm severity settings. Alarms are triggered using
either the default system settings or some
combination of user-defined settings. For more
information, see the System Overview and
Configuration User Guide.
signal-type <value> Type of signal being transmitted.
Refer to the following list, subject to change:
ochp | ots | otu1 | otu2 | otu2e | otu2f | otu2x | otu3 | otu3e | otu4
|stm64 | stm16 | stm4 | stm1 | stm1e | oc192 | oc48 | oc12 | oc3 | oc3e |
ety1g | ety1ge | ety1gx |ety1gxe | ety10g | ety10goc | ety40g | ety100 |
ety100g | fc1600 | fc1200 | fc800 | fc400 | fc200 | fc100 | video270 |
sdi360m | hdsdi1485g | ge | ge10 | ge10-otu2e | osc100 | osc2m |
oschannel | po | ull-ety10goc | ull-fc800 | ull-fc1200 | ull-fc1600
space DWDM: 50GHz Specify the wavelength channel spacing.
spacing or 100GHz
CWDM: 20nm
<empty> where
not relevant
(for amplifiers,
OLP, OMSP)
Attribute/
Options Usage guidelines
Keyword
spo --- Used to configure AoC cards working in XDM mode
using SPO subinterfaces for ETY ports. Implements
preconfigured optimized settings.
test-mode normal The system should run and handle network traffic
test normally (normal) or should run in test mode and not
handle live traffic (test).
tilt <value> Tilt setting for this amplifier.
tilt-offset <value> Tilt offset setting for this amplifier.
tim-ca allow The system should (allow/enabled) or should not
tim-consequent-action disabled (disabled/inhibit) implement the predefined
enabled "consequent actions" or responses that have been
configured for this port in case of a Trace Identifier
inhibit
Mismatch (TIM).
tim-monitor Enable or disable TIM (Trace Identifier Mismatch)
monitoring.
SDH/SONET mode: When working with SDH/SONET options, this
disabled attribute can only be enabled or disabled
(default).
enabled
When working with optical or photonic options,
this attribute specifies the TIM monitoring mode
Optical/Photonic to be used:
mode:
---SAPI (Secure Access Point Identifier, usually
sapi used for P2P or P2MP topologies)
dapi ---DAPI (Destination Access Point Identifier,
both usually used for MP2P topologies)
disabled ---Both
---Disabled
tim-oci-lck- enabled The system should (enabled) or should not (disabled)
consequent-action disabled implement the predefined "consequent actions" or
responses that have been configured for this port in
case of an instance of one of these types of error
conditions: Trace Identifier Mismatch (TIM), Open
Connection Indication (OCI), or Locked upstream
connection (LCK).
tributary-slot <value> Defines the smallest possible subdivision for an ODU
subinterface. The slot size depends on the payload
type (PT). For example, PT21 provides a granularity of
1.25G. These means, for example, that an ODU2 port
can be divided into eight PT21 tributary slots.
total-channels-options 16 Defines the total number of channels configured for
44 this ROADM-9a module.
Attribute/
Options Usage guidelines
Keyword
tpn <value> Tributary port number (TPN) provides the port
number to be used as part of the ODUk multiplexing
scheme. Values defined based on ODU type (see
Understanding Interface and Tributary Slot
Configuration).
tr100-options transponder Defines how this TR100 module is being configured
regenerator and used; as a transponder or as a regenerator.
tti-expected <tti-expected> The TTI (Trail Trace ID) strings expected by the
tti-expected-dapi system; verified when working with TIM monitoring.
tti-expected-operator Configured as appropriate for DAPI, Operator, SAPI,
tti-expected-sapi or SDH/SONET modes.
tti-sent <tti-sent> The TTI strings actually sent by the system; verified
tti-sent-dapi when working with TIM monitoring.
tti-sent-operator Configured as appropriate for DAPI, Operator, SAPI,
tti-sent-sapi or SDH/SONET modes.
tx-enable enabled Defines the laser state, indicating whether
disabled transmission should be enabled (default) or disabled
from this transceiver port.
tx-pattern none When the system is running in test-mode, defines
idles what (if any) testing pattern should be used for signal
off transmission.
pseudorandom
tx-power <tx power> Transmission power level.
tx-wavelength <wavelength> Output wavelength for this port. Specific value
depends on hardware capabilities. Options include:
DWDM (17-60.5)
CWDM (1471-1611)
non-colored
ull Optimize configuration settings for ultra low latency
transceivers.
wavelength <wavelength> Wavelength for this port, usually configured when
working with fixed transceivers. Specific value
depends on hardware capabilities. Options include:
DWDM (17-60.5)
CWDM (1471-1611)
non-colored
wdm-type na WDM type, preconfigured setting based on the type
cwdm of equipment.
dwdm
non-colored
NOTE: The CLI examples provided in this section are for illustrative purposes only, to clarify
the style or syntax of a type of command. Some of the specific commands and parameters
used in these examples are not supported in the current version of ShadeTree. In addition, not
every user has full privileges to perform commands in the CLI. Therefore, you might not be
able to run some of the commands described in this manual, with the specific syntax and
parameters listed.
NOTE: For detailed information about configuring GRE, see the GRE User Guide.
If you are using GRE to create tunnels across an IP network, you can create a tunnel for a GRE interface. To
create a GRE tunnel, you configure:
Source IP address of the tunnel
Destination IP addresses of the tunnel
An optional description of the tunnel
NOTE: The name of a GRE interface is always gre0. You may configure multiple GRE logical
interfaces under the [interfaces gre0 unit unit] hierarchy.
To configure a GRE tunnel, include the following statements at the [edit interfaces gre0 unit unit]
hierarchy level:
tunnel {
disable;
description description;
source source;
destination destination;
mtu mtu;
(rebalance | no-rebalance);
keepalive-interval keepalive-interval;
keepalive-limit keepalive-limit;
}
Where:
disable disables the tunnel.
source is the IP address to use as the source of this tunnel.
description is a text description of the tunnel. If the description contains spaces or special characters,
enclose the text in quotes (").
destination is the IP address to use as the source of this tunnel.
mtu is the MTU for the tunnel, from 256 to 9,600 bytes.
rebalance allows the GRE tunnel to be rebalanced (default).
no-rebalance keeps the GRE tunnel from being rebalanced.
keepalive-interval is the length of time the device waits before sending the next GRE keepalive
packet, from 0 to 32,766 seconds. The default is zero seconds (i.e., disabled).
keepalive-limit is the maximum number of keepalives to send without hearing a response before
declaring the GRE protocol down on the interface, from 1 to 254 packets. The default is three packets.
NOTE: You can only create one GRE tunnel per logical interface. You cannot configure GRE
tunnels if high availability is enabled. For more information about high availability, see the
System Overview and Configuration User Guide.
Example
The following example configures a GRE tunnel called "Tunnel to 159" with a source IP address of
10.1.1.153 and a destination IP address of 10.1.1.159:
interfaces {
gre0 {
unit 0 {
tunnel {
description "Tunnel to 159";
source 10.1.1.153;
destination 10.1.1.159;
}
}
}
}
NOTE: The Apollo (OPT9600) Platforms include special performance monitoring features. For
example you can define threshold values in a profile and assign different profiles to different
entities (see Performance Monitoring in the System Overview and Configuration User Guide).
The monitor interface command allows you to monitor, in real-time, interface-specific counters for a
specific interface or all interfaces. There are two modes:
monitor interface interface-name: Allows you to monitor counters on a specific physical interface
(port or subinterface). Certain logical interfaces, such as lo0, can also be monitored. Displays
information in long mode.
monitor interface traffic: Allows you to monitor traffic counters for all interfaces. Displays
information in short mode.
monitor interface logical interface-name: Allows you to monitor counters on a specific logical
interface. Displays information in long mode.
NOTE: Once the monitor interface command is running, you can switch between modes.
Default display
By default, the monitor interface traffic command displays:
The rate of traffic, rather than the absolute value of the counters
Packets, rather than bytes
Information in short mode rather than long mode
By default, the monitor interface interface-name command displays information in long mode.
Real-time information about all of the interfaces on the device displays, as illustrated in the following
figure.
Figure 5-1: Example of monitor interface traffic display
The following table lists the keyboard commands you can use within the monitor interface traffic
command (short mode).
Command Description
b Displays traffic in bytes and displays the traffic rate in bytes per second.
c Clears the display and restarts the averaging interval for rate measurement.
d Displays the absolute counter increments for traffic, rather than the average rate.
f Temporarily freezes the display. Only the t (thaw) and q (quit) commands are operational.
Press t to unfreeze the display.
l Changes the display to long mode, that is, displays information about an interface. Usually,
information about the first interface in the traffic list displays. If you have previously
displayed an interface in long mode, that interface information displays. To change back to
short mode, press s.
p Displays traffic in packets and displays the traffic rate in packets per second (Default).
q Exits the monitor interface command and returns to the CLI.
r Displays the average rate of traffic, rather than the absolute counter increments (Default).
t Unfreezes the display. This option is only available when the display is frozen.
Ctrl-u Scrolls the display up.
Ctrl-d Scrolls the display down.
The following table lists the keyboard commands you can use within the monitor interface
interface-name command (long mode).
Command Description
c Clears the display and restarts the averaging interval for rate measurement.
f Temporarily freezes the display. Only the t (thaw) and q (quit) commands are
operational. Press t to unfreeze the display.
i Displays information about a specified interface. You are prompted to enter the
interface name.
n Displays information about the next interface.
s Changes the display to short mode, that is, displays traffic information for all interfaces.
To change back to long mode, press l.
q Exits the monitor interface command and returns to the CLI.
t Unfreezes the display. This option is only available when the display is frozen.
NOTE: You can also press Ctrl-c to exit the monitor interfaces command.
NOTES:
The Apollo platforms include special fault management features. For example you can
define alarm severity levels in a profile and assign different profiles to different entities
(see Fault Management in the System Overview and Configuration User Guide).
You can display additional information by issuing the show interfaces extensive
command.
There are alarms for Gigabit Ethernet interfaces. You can display interface alarm information by using the
show interfaces detail command from the operation mode.
6.1.3 XC Owners
Following introduction of GMPLS support for ODU-XCs, XCs may be "owned" or controlled by either the
management plane, or the control plane, or even both, depending on the network context.
Management plane ownership (via ShadeTree, STMS, and LightSoft) indicates that the object is
configured, setting card assignment, port configuration, and so on, through the management plane.
Control plane ownership, identified by the relevant LSP ID number, is relevant for XCs that are
participating in ASON protection and restoration configuration, which is handled by the control plane.
Typically, ODU-XCs for restoration purposes are implicitly created by the control plane and can be
implicitly deleted only by the control plane.
An object can be owned simultaneously by both the management and control planes when
performing maintenance operations on objects owned by the control plane or during transition states
from non-ASON to ASON and vice versa.
A XC may have multiple owners, depending on how that XC is being used and by what. For example, XCs
that migrate from non-ASON functionality to ASON protection, or vice versa, are considered "owned" by
both the management and the control planes. Multiple ownership also provides a safety net, since a XC
cannot be deleted unless it is owned by only a single owner and is not carrying any traffic, thereby ensuring
that a XC is not mistakenly deleted, leading to an unintentional impact on traffic.
Ownership is determined by the system, depending on the XC creation and usage context, and can be
checked through the owner CLI parameter.
6.1.4 XC Modes
XCs are automatically configured in one of the following modes:
Configurable: XCs that are explicitly created, edited, and deleted by users working through the
management or control plane. Note that not all attributes can be edited, and some attributes can
only be edited under certain conditions. Some modifications are traffic-affecting, while others are
not.
Fixed: XCs that are created automatically by the NE without operator intervention. Fixed-mode XCS
are used to connect two endpoints with a unidirectional connection at a single fixed connectivity rate.
Examples include cross connections in amplifiers or in passive optics cards such as DCFs or
Mux/DeMuxes.
Operators are not allowed to create or delete fixed-mode XCs. Operators are allowed to edit
non-traffic-affecting attributes such as trail ID and customer name. When these cross connections are
used by a trail, the relevant trail information is so noted by the XC to prevent inadvertent deletion of
a cross connection in use.
Fixed XC: Mgmt Fixed XC: Control Configurable: Mgmt Configurable: Control
XC Action
plane owner plane owner plane owner plane owner
Creation No user action, implicitly created by NE Explicit XC creation Created via control
only. only if XC created via plane only if XC
Mgmt plane. created as part of
GMPLS/WSON trail
configuration.
Modification Explicit editing Explicit editing Explicit editing only if Explicit editing for
only for enabled in future at least one of the traffic-affecting
non-traffic versions. owners is the Mgmt parameters only for a
affecting plane. single owner.
attributes such as Explicit editing for
trail ID. non-traffic-affecting
parameters allowed
for multiple owners.
Deletion No user action, implicitly deleted by NE Explicit deletion only if Explicit deletion only if
only. the last owner is the the last owner is the
Mgmt plane. Control plane.
Notifications Notifications sent for all creation, modification, and deletion actions in all modes.
User retrievable Yes in all modes.
Saved in
non-volatile Yes in all modes.
memory
Incoming signals or tributaries are connected to outgoing signals or tributaries of compatible bandwidth.
For example, the following cross connections are currently supported:
ODU0ODU0
ODU1ODU1
ODU2ODU2
ODU2eODU2e
ODU4ODU4
ODUFlex (CBR)ODUFlex (CBR)
ODUSlotODUSlot
ODUSlot is a proprietary rate developed by ECI for lower-rate ports supporting less than 1.25 Gbps
bandwidth, such as STM1 and ETY1G. Up to two adjacent ODUSlot endpoints based in the low-rate
ports on the client side can be connected to two ODUSlot endpoints contained within a single
ODU1interface at the network side. Note that throughout the network the ODUSlots are aggregated
into ODU1s. Only at the trail edges they are split into ODUSlot cross connections.
If one of the ODUSlot connections to an ODU1 interface has been configured as a protected type,
then the NE automatically configures the second ODUSlot connection to that ODU1 as the protection
connection. If the main ODUSlot connection is deleted, then the NE automatically deletes the
protection connection.
ODUitrib[n]ODUitrib[m]
For example, the following figure illustrates a cross connection between two tributaries of two OTU2
ports.
Figure 6-3: ODUi trib[n] <--> ODUitrib[m] cross connect configuration
Multiplexing is supported for greater bandwidth efficiency. For example, up to four different ODU1s can be
multiplexed to an ODU2. Detailed connectivity rules and guidelines are provided in L1-XC Connection
Tables.
This type of cross connection is used, for example, when connecting local tributaries on a board or
tributaries from client to line or from line to line.
1-way unprotected P2MP: Multiple L1-XC legs are configured as a group of unidirectional P2MP
connections that all originate at the same input port (from-tp), with each one terminating at a
different endpoint (to-tp).
Figure 6-5: 1-way unprotected P2MP L1-XC legs
This type of cross connection is used, for example, when connecting an input port to multiple output
ports for multicast or broadcast applications.
2-way unprotected P2P: A single L1-XC leg is configured as a bidirectional P2P connection between
two compatible endpoint ports of equal bandwidth.
Figure 6-6: 2-way unprotected P2P L1-XC leg
Note that a bidirectional cross connection may also consist of two unidirectional cross connections
managed together.
This type of cross connection is used, for example, when creating unidirectional connections between
two source tributaries and a single destination tributary.
2-way protected P2P: Two bidirectional L1-XC legs that both end at the same endpoint. Each
protected L1-XC is associated with a single protection group.
Figure 6-8: 2-way protected P2P L1-XC legs
This type of cross connection is used, for example, when creating bidirectional connections between
two source tributaries and a single destination tributary. Note that while the terms source and
destination are not meaningful in the classic sense for a bidirectional leg on which traffic is running
back and forth in both directions, the destination endpoint is significant in terms of protection
configurations, since that is the endpoint the NE uses as the basis when creating the associated
protection group.
1-way protected P2MP: Up to four unidirectional L1-XC legs can be configured to create a group of
connections that all originate at different endpoints (from-tp) but all end at the same endpoint
(to-tp). Each protected L1-XC is associated with a single protection group.
This type of cross connection is used, for example, for ROADM-Add applications with multiple drop
points.
2-way protected P2MP: Up to four bidirectional L1-XC legs can be configured to create a group of
connections that all originate at different endpoints (from-tp) but all end at the same endpoint
(to-tp). Each protected L1-XC is associated with a single protection group.
Figure 6-9: 2-way protected P2MP L1-XC legs
This type of cross connection is used, for example, for ROADM applications with multiple add/drop
points. Since there are multiple legs protecting the line port, the operator must specify which is the
main leg.
1-way fully protected XC: Four unidirectional L1-XC legs can be configured to create a group of
connections that all run between the same set of four endpoints, providing full traffic protection.
Each unidirectional L1-XC leg participates in two different protection group entities.
2-way fully protected XC: Four bidirectional L1-XC legs can be configured to create a group of
connections that all run between the same set of four endpoints, providing comprehensive traffic
protection. Each bidirectional L1-XC leg participates in two different protection group entities.
Figure 6-10: 2-way fully protected L1-XC
Protected XC
Usage Maximum XC legs
endpoint
ODU FIO cards 4 (V5.1)
2 (earlier versions)
Other L1 service cards 2
OCH Non-WSON ROADM cards 4
WSON ROADM cards 2 (future)
OLP 2
OMS Protection cards (OMSP, OLP, etc.) 2
OS Splitter/Coupler 2
For example:
set cross-connects odu2-xc leg 1 directionality bidirectional
from-tp odu2-u3/1:1 to-tp odu2-u3/2:1
The preceding code line illustrates a minimal L1-XC configuration command, creating an L1-XC named
odu2-xc with one bidirectional leg running between port 1 and port 2 on the card in slot 3. When
configuring L1-XCs for their system, operators would include a full set of relevant attribute specifications,
depending on their network configuration. A list of L1-XC attributes and their options is provided in Cross
Connection Attributes.
Deleting a leg: Deleting a leg from a multi-leg L1-XC, when that leg is not the active leg of a protected
L1-XC and at least one leg remains to carry traffic, is non-traffic-affecting.
Changing a unidirectional leg to bidirectional: Reconfiguring an L1-XC leg that was originally
unidirectional so that it now carries traffic in both directions, (or alternatively, adding a second
unidirectional leg so that traffic can be carried in both directions) is non-traffic-affecting. For example,
if traffic used to run from Point A to Point B, switching the configuration so that the traffic now only
runs in both directions between Point A and Point B.
For example:
delete cross-connects fio100_odu2
commit
In this example, the first leg runs between odu2-u3/1:1 and odu2-u3/2:1. The second leg runs between
odu2-u3/1:1 and odu2-u3/3:1. The two legs share the odu2-u3/1:1 endpoint. The system automatically
creates a corresponding protection group, identified by the type (traffic, indicating that it protects a L1-XC)
and by the identity of the shared endpoint (odu2-u3/1:1). The main traffic leg is the one running between
the shared endpoint and odu2-u3/2:1.
In this example, the user enters a series of set cross-connects commands to configure a cross connect,
and then enters a show cross-connects command and a show protection-group command to see
the structure of the new L1-XC entity and the protection group created automatically for this entity.
root@localhost# set cross-connects sample-xc trail-id 12
root@localhost# commit
OTU1 OTU2 OTU2e OTU2f OTU3e OTU4 ETY 1Gx ETY 1Ge ETY 1G ETY 10G ETY 10GOC
ETY 1Gx1 ODUSlot-XC ODUSlot-XC N/A N/A N/A N/A ODUSlot-XC N/A N/A N/A N/A
ETY 1Ge ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC N/A N/A ODUSlot-XC N/A N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC ODU0-XC
ETY 1G ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC N/A N/A N/A ODUSlot-XC N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC ODU0-XC
ETY 10G N/A ODU2-XC N/A N/A ODU2-XC N/A N/A N/A N/A ODU2e-XC N/A
ETY 10GOC N/A N/A ODU2e-XC N/A ODU2e-XC N/A N/A N/A N/A N/A ODU2e-XC
ETY100G N/A N/A N/A N/A N/A ODU4 N/A N/A N/A N/A N/A
OTU1 OTU2 OTU2e OTU2f OTU3e OTU4 STM1 STM1e STM4 STM16 STM64
STM1 ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC ODUSlot-XC N/A N/A N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
STM1e ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC N/A ODUSlot-XC N/A N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
STM4 ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC N/A ODUSlot-XC ODUSlot-XC N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC ODU0-XC
STM16 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC N/A N/A N/A ODU1-XC N/A
STM64 N/A ODU2-XC N/A N/A ODU2e-XC ODU2-XC N/A N/A N/A N/A ODU2-XC
OTU1 OTU2 OTU2e OTU2f OTU3e OTU4 OC3 OC3e OC12 OC48 OC192
OC3 ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC ODUSlot-XC N/A N/A N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
OC3e ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC N/A ODUSlot-XC N/A N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
OC12 ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC N/A N/A ODUSlot-XC N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
OC48 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC N/A N/A N/A ODU1-XC N/A
OC192 N/A ODU2-XC N/A N/A ODU2e-XC ODU2-XC N/A N/A N/A N/A ODU2-XC
OTU1 OTU2 OTU2e OTU2f OTU3e OTU4 FC100 FC200 FC400 FC800 FC1200
FC100 ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC ODUSlot-XC N/A N/A N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
FC200 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC ODU1-XC N/A ODU1-XC N/A N/A
FC400 N/A 2 x ODU1-XC N/A N/A 2 x ODU1-XC 2 x ODU1-XC N/A N/A 2 x ODU1-XC N/A N/A
ODUF-FC400 ODUF-FC400 ODUF-FC400 ODUF-FC400
FC800 N/A ODU2-XC N/A N/A ODU2-XC ODUF-FC800 N/A N/A N/A ODU2-XC N/A
ODUF-FC800 ODUF-FC800 ODUF-FC800
FC1200 N/A N/A ODU2e-XC ODU2f-XC ODU2e-XC ODU2e-XC N/A N/A N/A N/A ODU2f-XC
ODU2e-XC
VIDEO270 ODUSlot-XC ODUSlot-XC N/A N/A ODUSlot-XC ODU0-XC ODUSlot-XC N/A N/A
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
HDSDI1485 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC N/A ODU1-XC N/A
HDSDI3G N/A ODUF-SDI3G-XC N/A N/A ODUF-SDI3G-XC ODUF-SDI3G-XC N/A N/A ODUF-SDI3G-XC
packet-cross-connects {
<cross-connect> {
description <description>;
disable;
type (l2t | pw-stitching);
interface <interface_name>;
options {
pw-type (ethernet | ethernet-vlan);
pw-status-relay;
pw-stitching-tlv;
pwgroup-id <pwgroup-id>;
ethernet-attributes {
mtu <mtu>;
}
}
}
}
When fiber connectivity is defined, each port provides details of the fiber connectivity configuration of its
connected peer. The following figure is an example of a pre-amplifier, connected to a ROADM, and a
ROADM connected to a booster. The figure displays the fiber connectivity information of each peer port.
Figure 7-2: Example of fiber connectivity connected peer configuration
IMPORTANT: OTUk, OTS, and OCHP ports cannot transmit traffic if fiber connectivity
configuration is missing (unless the ports reside on passive cards). Power equalization is
possible where both external and internal fiber connectivity have an NE_PEER IP, (as long as
the NE_PEER IP is not unspecified).
Attribute/
Options Description
Keyword
Connectivity Type external Type of fiber connection.
internal
Direction uni-in How the peer-port fiber is connected (one-way in,
uni-out one-way out, running in both directions, or two
bidirectional separate unidirectional trails).
uni-in-out
Peer_NE unspecified The peer router IP address. Configured explicitly for
ip-address inter-fiber connectivity only.
Peer_Slot <string> The peer shelf and slot name (e.g., u4).
Peer_Port <numeric> The peer port number (e.g., 2).
input-fiber-loss <value> The configured input fiber loss (dB). (Default
value=0; possible values 0-100; resolution=0.1)
Attribute/
Options Description
Keyword
fiber-type g652 The type of fiber (default = G652).
g653
g654
g655-leaf
g655-tw-rs
g655-tw-reach
multimode
fiber-length <numeric> The length of the fiber (km).
(Intra-fiber connectivity values 0-500;
resolution=0.1).
allowed-fiber-loss-margin The margin of fiber loss allowed before an alarm is
<numeric>
raised (dB).
(Default: intra-fiber connectivity=0.1; inter-fiber
connectivity=3, and resolution=0.1. Possible
intra-fiber connectivity values=0-7).
pmd <numeric> Polarized Mode Dispersion (PMD)
For intra-fiber connectivity, default=0.
For inter-fiber connectivity, PMD range=0-40,
resolution=0.1. Default PMD varies according
to fiber length: <10km=0; >10km=0.7sqrt.
management-buffer-b64 <value> Read-only, set at the NMS level.
The following code chunks provide examples of intra-fiber connectivity with the peer_ne defined as the
loopback IP address:
uni-directional fiber connectivity
fiber-connectivity internal uni-in
peer-ne 127.0.0.1;
peer-slot u13;
peer-port 2;
input-fiber-loss 0;
fiber-length 0;
fiber-type g652;
allowed-fiber-loss-margin 1;
pmd 0;
}
fiber-connectivity internal uni-out
peer-ne 127.0.0.1;
peer-slot u12;
peer-port 1;
output-fiber-loss 0;
fiber-length 0;
fiber-type g652;
allowed-fiber-loss-margin 1;
pmd 0;
}
bidirectional fiber connectivity:
fiber-connectivity internal bidirectional
peer-ne 127.0.0.1;
peer-slot u4;
peer-port 2;
input-fiber-loss 0;
output-fiber-loss 0;
fiber-length 0;
fiber-type g652;
allowed-fiber-loss-margin 1;
pmd 0;
}
The following code chunks provide an example of inter-fiber connectivity, including definition of the peer
NE IP address.
fiber-connectivity external uni-in
peer-ne 10.4.4.30;
peer-slot u4;
peer-port 2;
input-fiber-loss 0;
fiber-length 0;
fiber-type g652;
allowed-fiber-loss-margin 1;
pmd 0;
}
fiber-connectivity external uni-out
peer-ne 10.4.4.30;
peer-slot u5;
peer-port 1;
output-fiber-loss 0;
fiber-length 0;
fiber-type g652;
allowed-fiber-loss-margin 1;
pmd 0;
}
NOTE: If the Peer NE is unspecified, all other attributes are automatically defined as null and
cannot be modified.
When deleting fiber connectivity configuration on one port, deletion of fiber connectivity on the peer port
varies as follows:
For external fiber connectivity: Fiber connectivity configuration must be deleted separately on each
peer port, unless the NE_PEER is unspecified.
For internal fiber connectivity: the NE automatically deletes the connected peer configuration.
The following table describes how to modify intra-fiber connectivity parameters and indicates which
modifications are traffic affecting.
The following table describes how to modify intra-fiber connectivity parameters and indicates which
modifications are traffic affecting.
peer_port For external connectivity, perform this procedure via STMS. Yes, for old peer
port
Physical attributes such Parameters can be modified. No
as: fiber_type, At the [set chassis] level, modify the existing
fiber_length parameter(s), as required.
IMPORTANT: Modifying port parameters can impact fiber connectivity, and some port
modifications can be traffic affecting.
The following table describes port modifications and their impact on fiber connectivity.
OTU1 OTU2 OTU2e OTU2f OTU3 OTU3e OTU4 OTS OCHP PO OSC100M OSC2M OSChannel
OTU1 Y N N N N N N N Y Y N N N
OTU2 N Y N N N N N N Y Y N N N
OTU2e N N Y N N N N N Y Y N N N
OTU2f N N N Y N N N N Y Y N N N
OTU3 N N N N Y N N N Y Y N N N
OTU3e N N N N N Y N N Y Y N N N
OTU4 N N N N N N Y N Y Y N N N
OTS N N N N N N N Y N Y N N N
OCHP Y Y Y Y Y Y Y N Y Y N N N
PO Y Y Y Y Y Y Y Y Y Y N N N
OSC100M N N Y N N N N N N N N N Y
OSC2M N N N N N N N N N N N N Y
OSChannel N N N N N N N N N N Y Y N
The following table shows the fiber connectivity rules for SDH technology.
The following table shows the fiber connectivity rules for SONET technology
The following table shows the fiber connectivity rules for FC technology.
The following table shows the fiber connectivity rules for Ethernet technology.
ULL-ETY10
GE 10GE ETY1G ETY1Ge ETY1GX ETY1GXe ETY10G ETY10GOC ETY40G ETY100G PO OCHP
GOC
GE Y N Y Y (see note) Y Y (see note) N N N N N Y Y
10GE N Y N N N N Y Y N N N Y Y
ETY1G Y N Y N Y N N N N N N Y Y
ETY1Ge Y (see N N Y N Y N N N N N Y N
note)
ETY1GX Y N Y N Y N N N N N N Y Y
Y (see N N Y N Y N N N N N Y N
ETY1GXe note)
ETY10G N Y N N N N Y N N N N Y Y
ETY10GOC N Y N N N N N Y N N N Y Y
ULL- N Y N N N N N Y Y N N Y Y
ETY10GOC
ETY40G N N N N N N N N N Y N Y Y
ETY100G N N N N N N N N N N Y Y Y
PO Y Y Y Y Y Y Y Y N N Y Y Y
OCHP Y Y Y N Y N Y Y N N Y Y Y
NOTE: Only GE ports that reside on NPB cards and have electrical connectors (i.e., the expected type has a suffix starting with e) can connect to the
ETY1Ge port.
The following table shows the fiber connectivity rules for CBR technology.
NOTES:
Ethernet ports on AoC10_L2 cards are automatically configured as Data Communication
Network (DCN) interfaces.
A single termination label has been reserved for use by all AoC10_L2 cards.
The CLI configuration commands assume consistency between the DCN interface
configuration (IMG, GCC and OSC) and configuration of DCN flows on AoC10_L2 Ethernet
ports.
Routing instances are created automatically as part of the card configuration process. Routing-instances are
linked to the specific card and identified by slot number. For example:
The routing instance is the container in which the relevant MPLS LSPs, tunnels, and PWs are configured. By
default the card is in PB mode. To switch the card to MPLS-PE mode, enabling LSP and PW functionality,
type:
There are no restrictions when changing the card from PB to MPLS mode. Changing the card from MPLS
mode to PB mode is only allowed if no MPLS services are configured on the card.
In addition to the automatic default settings, there are a number of optional card level parameters that you
can configure explicitly for the card. The details of these are covered in the previous subsections. These
include features such as RSTP, CFM, port mirroring, and so on, described later in this section.
Port Configuration
To provision a service, at least one pair of card ports must be configured in order to receive and transmit
signals. For example:
lsh> set chassis slot u0 aoc10-l2 port 0 enable ethernet-options port-mode uni
lsh> set chassis slot u0 aoc10-l2 port 17 enable ethernet-options port-mode i-nni
lsh> commit
In this example two ports are configured: Port 0, a 1G UNI port, and Port 17, a 10G I-NNI port. The
necessary underlying infrastructure and attribute setting are configured automatically. To change the port
mode, simply type in a new set chassis command with the new port setting.
Interface Configuration
Port configuration causes ShadeTree to automatically create the corresponding physical interfaces (PIF)
required to transmit traffic for that port. These interfaces can be seen using the show interfaces
command. As with other configuration commands, the necessary underlying setting are configured
automatically and most other interface layer parameters are optional. You can also explicitly configure
attribute values for each PIF through the interface configuration hierarchy. For example:
VSI Configuration
VSIs are configured within the context of a specific routing instance. For example:
After the preceding command is executed, an empty VSI is created with the attribute values defined in the
command line.
CD-VLAN-ID Range from 1 to 4094 Customer VLAN IDs, configured for each port
included in the VSI.
These commands automatically create the necessary subinterfaces and attribute values. In this example,
this means creation of two interfaces identified as ge-u0/0.10 and ge-u0/1.10, both included in the
routing-instance slot-u0-routing-instance.
TIP:
To display the port configuration within a CLI command hierarchy structure, type show
interfaces from configuration mode. For example:
lsh> show interfaces
ge-u0/1 {
ethernet-options {
max-frame-size 1604;
link-oam-options {
enable disabled;
local-mode active;
passive-peer-only any;
remote-loopback disabled;
err-frame-threshold 1;
err-frame-window 1;
err-frame-period-threshold 1;
err-frame-period-window 1;
err-frame-sec-sum-threshold 1;
err-frame-sec-sum-window 60;
}
}
}
To display the current port status, type run show interfaces. For example:
lsh> run show interfaces
Interface Admin Oper Family Address
fe-rcp Down Down
ge-u0/1 Up Up
ge-u0/1.1 Up Up mpls
ge-u0/11 Up Up
ge-u0/11.1 Up Up mpls
ge10-u0/16 Up Lower Down
ge10-u0/16.1 Up Lower Down mpls
ge-ua/0 Up Up
ge-ua/0.0 Down Down inet
dcn0 Down Down
gmpls0 Down Down
lo0 Down Down
routing-instances {
<ri-name> {
virtual-switching-instances {
<vsi-name> {
uni-ports {
<uni-port-name> {
cd-vlan-ids {
<vlan-id-list (10 | 11 | 12 | ...)>;
}
egress-tagged-vlan-action (nochange | translate |
priority-tagged | untagged);
egress-ptagged-vlan-action (nochange | translate |
priority-tagged | untagged);
ingress-untagged-ptagged-vlan (enabled | disabled);
ingress-wildcard-vlan (enabled | disabled);
}
} // end uni ports
}
} // end virtual switching instances
}
} // end routing instances
The following command lines illustrate a typical example of wildcard VLAN mapping.
lsh> set routing-instances slot-u1-routing-instance virtual-switching-instances
foo uni-ports ge-u1/0 cd-vlan-ids 10
lsh> set routing-instances slot-u1-routing-instance virtual-switching-instances
foo uni-ports ge-u1/0 ingress-wildcard-vlan enabled
lsh> set routing-instances slot-u1-routing-instance virtual-switching-instances
foo uni-ports ge-u1/0 ingress-untagged-ptagged-vlan enabled
lsh> commit
This set of commands automatically creates an interface included in the containing routing instance and
identified as ge10-u2/17.100.
uni-ports {
ge-u2/0 {
cd-vlans {
10;
} // cd-vlans
} // ge-u2/0
} // uni-ports
nni-ports {
s-vlan 100;
ge10-u2/17 {
} // ge10-u2/17
} // nni-ports
} // vsi_foo
} // virtual-switching-instances
} // slot-u2-routing-instance
lsh> commit
protocols mpls {
interface ge-u0/16.1; // Implicitly created when this port is set as MoE mode
static {
label-switched-paths tunnel_1;
}
}
virtual-switching-instances {
vsi_foo {
vsi-type P2P;
nms-service-identifier 1;
uni-port ge-u0/0 {
cd-vlans {
10;
}
}
pseudo-wires {
pw-A {
remote-pe-id 288-8;
split-horizon-group 1;
receive-pw-label 200;
transmit-pw-label 100;
transmit-tunnel tunnel_1;
} // pw-A
} // pseudo-wires
} // vsi_foo
} // virtual-switching-instances
} // slot-u0-routing-instance
lsh> set chassis slot u1 aoc10-l2 port 1 port-type ge ethernet-options port-mode moe
lsh> set chassis slot u1 aoc10-l2 port 2 port-type ge ethernet-options port-mode moe
lsh> set chassis slot u1 aoc10-l2 port 3 port-type ge ethernet-options port-mode moe
lsh> commit
egress-counting disabled;
vsi-type mp2mp;
max-fib-size 100;
nms-service-identifier 2;
pm-monitor disable;
state enabled;
pseudo-wires {
ge-u1/1.1 {
remote-pe-id 100:100;
split-horizon-group 1;
receive-pw-label 1024;
transmit-pw-label 32;
transmit-tunnel tun1;
}
ge-u1/2.1 {
remote-pe-id 101:101;
split-horizon-group spoke;
receive-pw-label 1026;
transmit-pw-label 64;
transmit-tunnel tun2;
}
}
severity-profile default;
alarm-master-mask disable;
Entity Routing instance Tunnel name LSP name Final entity name
MPLS static slot-u1-routing- HEAD-BDT N/A slot-u1-routing-instance-
tunnel instance HEAD-BDT
Out-Segment of slot-u1-routing- HEAD-BDT MAIN slot-u1-routing-instance-
Originating/ instance HEAD-BDT-MAIN
Terminating
Tunnels
Out-Segment of slot-u1-routing- XC-BDT MAIN slot-u1-routing-instance-
Transit Tunnel - instance XC-BDT-MAIN-Fwd
Forward
Out-Segment of slot-u1-routing- XC-BDT MAIN slot-u1-routing-instance-
Transit Tunnel - instance XC-BDT-MAIN-Bwd
Backward
Entity Routing instance VSI name Cos Role Final entity name
Slot u1 slot-u1
Port 0 of slot u1 port-u1/0
LAG master on port 0 of slot u1 ge-u1/0
For example, the following command chunk illustrates use of this command with a typical output listing.
For example, the following command chunk illustrates use of this command with a typical output listing.
PW Summary Data
To retrieve a complete data listing for all PWs configured for the VSIs defined for a slot, enter the following
command.
For example, the following command chunk illustrates use of this command with a typical output listing.
For example, the following command chunk illustrates use of this command with a typical output listing.
For example, the following command chunk illustrates use of this command with a typical output listing.
routing-instances {
slot-u0-routing-instance { // Routing Instance will be created implicitly for
each card.
interface ge-u0/0.100; // UNI LIF created implicitly
interface ge-u0/16.200; // NNI LIF created implicitly
virtual-switching-instances {
vsi_bar {
vsi-type P2P;
nms-service-identifier 1; // Mandatory field
uni-ports {
ge-u0/0 {
cd-vlan-ids{
100;
} // cd-vlan-ids
} // ge-u0/0
} // uni-ports
nni-ports {
svlan 200; // Mandatory field
ge-u0/16 {
} // ge-u0/0
} // nni-ports
} // virtual-switching-instance-name
} // virtual-switching-instances
} // routing-instance-name
} // routing-instances
interfaces {
interface ge-u0/0 {
unit 100 { // implicitly created
vlan-id 100;
}
}
interface ge-u0/16 {
unit 200 { // implicitly created
vlan-id 200;
}
}
} // interfaces
routing-instances {
slot-u0-routing-instance { // Routing Instance created implicitly for each card
interface ge-u0/0.100; // UNI LIF created implicitly
interface ge-u0/17.1; // MPLS LIF created when port configured in MoE mode
protocols {
mpls {
interface ge-u0/17.1; // implicitly created when port configured in
MoE mode
static {
label-switched-path orig-lsp-abc; // Represents a tunnel
} // static
} // mpls
} // protocols
virtual-switching-instances {
vsi_bar {
vsi-type P2P;
nms-service-identifier 1;
uni-ports {
ge-u0/0 {
cd-vlan-ids{
100;
} // cd-vlan-ids
} // ge-u0/0
} // uni-ports
pseudo-wires {
xyz {
remote-pe-id 255-8;
split-horizon-group 1;
receive-pw-label 1024;
transmit-pw-label 17;
transmit-tunnel orig-lsp-abc;
} // xyz
} // pseudo-wires
} // virtual-switching-instance-name
} // virtual-switching-instances
} // routing-instance-name
} // routing-instances
interfaces {
interface ge-u0/0 {
unit 100 { // implicitly created
vlan-id 100;
}
interface ge-u0/17 { // implicitly created when this Port is in MoE mode
unit 1 {
family mpls;
}
}
} // interfaces
routing-instances {
slot-u0-routing-instance { // Routing Instance created implicitly for each card.
interface ge-u0/0.100; // UNI LIF created implicitly
interface ge-u0/16.200; // NNI LIF created implicitly
interface ge-u0/17.1; // LIF created implicitly when port mode set to MoE
protocols {
mpls {
interface ge-u0/17.1; // implicitly created when port configured in
MoE mode
static {
label-switched-path orig-lsp-abc;
} // static
} // mpls
} // protocols
virtual-switching-instances {
vsi_bar {
vsi-type MP2MP;
nms-service-identifier 1;
vfib-quota 100;
uni-ports {
ge-u0/0 {
cd-vlan-ids{
100;
} // cd-vlan-ids
} // ge-u0/0
} // uni-ports
nni-ports {
svlan 200;
ge-u0/16 {
} // ge-u0/16
} // nni-ports
pw-segments {
xyz {
remote-pe-id 255-8;
split-horizon-group <0..15>;
receive-pw-label 1024;
transmit-pw-label 17;
transmit-tunnel orig-lsp-abc;
} // xyz
} // pw-segments
} // virtual-switching-instance-name
} // virtual-switching-instances
} // routing-instance-name
} // routing-instances
interfaces {
interface ge-u0/0 {
unit 100 { // implicitly created
vlan-id 100;
}
}
interface ge-u0/16 {
unit 200 { // implicitly created
vlan-id 200;
}
}
interface ge-u0/17 { // implicitly created for the Port in MoE mode
unit 1 {
family mpls;
}
}
} // interfaces
The following statement is used to configure unidirectional or bidirectional tunnels, working at the
[edit routing-instances routing-instance protocols mpls] hierarchy level.
static {
tunnel <tunnel> {
control-channel-cos <control-channel-cos>;
description <description>;
directionality (uni-directional | bi-directional);
originating-tunnel {
main-lsp <main-lsp> {
backward-path {
in-segment {
label <inlabel>;
interface <ifname>;
} //end in-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
} //end cos
} //end tm-options
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
} // end bfd
forward-path {
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end forward-path
pm-monitor (enable | disable);
} // end main lsp
protection-lsp <prot-lsp> {
backward-path {
in-segment {
label <inlabel>;
interface <ifname>;
}
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
} // end bfd
forward-path {
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end forward-path
pm-monitor (enable | disable);
} // end protection-lsp
} //end originating-tunnel
psc-protocol {
psc-max-refresh-interval <psc-max-refresh-interval>;
}
terminating-tunnel {
main-lsp <main-lsp> {
backward-path {
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
} // end bfd
forward-path {
in-segment {
label <inlabel>;
interface <ifname>;
protected;
} // end in-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end forward-path
pm-monitor (enable | disable);
} // end main-lsp
protection-lsp <protection-lsp> {
backward-path {
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
}
forward-path {
in-segment {
label <inlabel>;
interface <ifname>;
} // end in-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end forward-path
pm-monitor (enable | disable);
} // end protection-lsp
} // end terminating-tunnel
tpg-options {
hold-off-time-main <hold-off-time-main>;
hold-off-time-prot <hold-off-time-prot>;
pm-monitor (enabled | disabled);
psc-maint-cmd (release | lockout | force-switch |
manual-switch | manual-reversion);
revertive-mode (enabled | disabled);
wait-to-restore-time <wait-to-restore-time>;
}
transit-tunnel {
main-lsp <main-lsp> {
ais-ldi (enabled | disabled);
backward-path {
in-segment {
label <inlabel>;
interface <ifname>;
} // end in-segment
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end backward-path
bidir-lsp-num <bidir-lsp-num>;
forward-path {
in-segment {
label <inlabel>;
interface <ifname>;
protected;
} // end in-segment
out-segment {
label <outlabel>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end forward-path
pm-monitor (enable | disable);
} // end main-lsp
} // end transit-tunnel
revert-time <revert-time>;
nms-tunnel-identifier <nmsidentifier>;
to <dest-pe-id>;
type (terminating | originating | transit);
severity-profile <severity-profile>;
pm-monitor (enable | disable);
alarm-master-mask (enable | disable);
} // end tunnel
} // END STATIC
Examples of tunnel configuration statements are provided in the following sections. For more information,
see the STMS User Guide.
static {
tunnel <tunnel-name> { // label-switched-path
type originating;
to 10:20;
directionality bi-directional;
control-channel-cos 0; Range: <0-7>;
//tpg options configured only when protection-lsp enabled
tpg-options {
lockout;
revertive;
wait-to-restore-time <seconds>;
hold-off-time-main <seconds>;
hold-off-time-protection <seconds>;
pm-monitor enable;
}
psc-protocol {
psc-max-refresh-interval <seconds>;
}
originating-tunnel {
main-lsp <lsp-name> { // primary path
pm-monitor enable;
forward-path {
out-segment {
nexthop ge-u1/1.1;
label 100;
}
tm-options {
cos 0 {
bandwidth 1;
}
cos 1 {
bandwidth N/A;
}
cos 2 {
bandwidth N/A;
}
cos 3 {
bandwidth N/A;
}
cos 4 {
bandwidth N/A;
}
cos 5 {
bandwidth N/A;
}
cos 6 {
bandwidth N/A;
}
cos 7 {
bandwidth N/A;
}
} // end tm-options
} // end forward-path
backward-path {
in-segment {
interface ge-u1/2.1;
label 200;
}
tm-options {
cos 0 {
bandwidth 1;
}
cos 1 {
bandwidth N/A;
}
... <remaining cos (0-7) values, see previous section>
} // end tm-options
} // end backward-path
bfd {
disable;
minimum-receive-interval 100;
minimum-transmit-interval 100;
detection-multiplier 3;
} // end bfd
} // end main-lsp
minimum-receive-interval 100;
minimum-transmit-interval 100;
detection-multiplier 3;
}
} // pm-monitor
} // protection-lsp
} // end originating-tunnel
} // end tunnel
} // static
static {
tunnel <tunnel-name> { // label-switched-path
type transit;
directionality bi-directional;
control-channel-cos 0; Range: <0-7>;
transit-tunnel {
main-lsp <lsp-name> { // primary path
pm-monitor enable;
ais-ldi enable;
forward-path {
in-segment {
interface ge-u1/1.1;
label 100;
}
out-segment {
nexthop ge-u1/2.1;
label 200;
}
tm-options {
cos 0 {
bandwidth 1;
}
cos 1 {
bandwidth N/A;
}
... <remaining cos (0-7) values, see head-end example>
} // end tm-options
} // end forward-path
backward-path {
in-segment {
interface ge-u1/3.1;
label 300;
}
out-segment {
nexthop ge-u1/4.1;
label 400;
}
tm-options {
cos 0 {
bandwidth 1;
}
cos 1 {
bandwidth N/A;
}
... <remaining cos (0-7) values, see head-end example>
} // end tm-options
} // end backward-path
} // end main-lsp
} // end transit-tunnel
} // end tunnel
} // static
static {
tunnel <tunnel-name> { // label-switched-path
type terminating;
from 10:30;
directionality bi-directional;
control-channel-cos 0; Range: <0-7>;
//tpg options configured only when protection-lsp enabled
tpg-options {
lockout;
revertive;
wait-to-restore-time <seconds>;
hold-off-time-main <seconds>;
hold-off-time-protection <seconds>;
pm-monitor enable;
}
psc-protocol {
psc-max-refresh-interval <seconds>;
}
terminating-tunnel {
main-lsp <lsp-name> { // primary path
pm-monitor enable;
forward-path {
in-segment {
interface ge-u1/1.1;
label 100;
tm-options {
cos 0 {
bandwidth 1;
}
cos 1 {
bandwidth N/A;
}
... <remaining cos (0-7) values, see head-end example>
} // end tm-options
} // end forward-path
backward-path {
out-segment {
nexthop ge-u1/2.1;
label 200;
}
tm-options {
cos 0 {
bandwidth 1;
}
cos 1 {
bandwidth N/A;
}
... <remaining cos (0-7) values, see previous section>
} // end tm-options
} // end backward-path
bfd {
disable;
minimum-receive-interval 100;
minimum-transmit-interval 100;
detection-multiplier 3;
} // end bfd
} // end main-lsp
bandwidth N/A;
}
... <remaining cos (0-7) values, see previous section>
} // tm-options
} // forward-path
backward-path {
out-segment {
nexthop ge-u1/4.1;
label 400;
}
tm-options {
cos 0 {
bandwidth 1;
}
cos 1 {
bandwidth N/A;
}
... <remaining cos (0-7) values, see previous section>
} // tm-options
} // backward-path
bfd {
disable;
minimum-receive-interval 100;
minimum-transmit-interval 100;
detection-multiplier 3;
}
} // pm-monitor
} // protection-lsp
} // end terminating-tunnel
} // end tunnel
} // static
Ingress LSPs
RSVP LSPs
Total 0 RSVP LSP displayed, Up 0, Down 0
Static LSPs
Name: HEAD-BDT, State: Up, Uptime: 00:00:39
To: 1:200, From: 0.0.0.0
Type: BiDirectional
Active Lsp: MAIN
Egress LSPs
RSVP LSPs
Total 0 RSVP LSP displayed, Up 0, Down 0
Static LSPs
Name: TAIL-BDT, State: Up, Uptime: 00:00:38
To: 0.0.0.0, From: 1:400
Type: BiDirectional
Uptime: 00:00:38
Incoming Interface: ge-u1/5.1, Label In: 410, Protection: Disabled
Bwd Outgoing Interface: ge-u1/5.1, Label Out: 411
Transit LSPs
RSVP LSPs
Static LSPs
Name: XC-BDT, State: Up, Uptime: 00:00:39
To: [INVALID], From: [INVALID]
Type: BiDirectional
Ingress LSPs
RSVP LSPs
Total 0 RSVP LSP displayed, Up 0, Down 0
Static LSPs
Name: HEAD-BDT, State: Up, Uptime: 00:01:14
To: 1:200, From: 0.0.0.0
Type: BiDirectional
Active Lsp: MAIN
Egress LSPs
RSVP LSPs
Total 0 RSVP LSP displayed, Up 0, Down 0
Static LSPs
Name: TAIL-BDT, State: Up, Uptime: 00:01:24
To: 0.0.0.0, From: 1:400
Type: BiDirectional
Transit LSPs
RSVP LSPs
Static LSPs
Name: XC-BDT, State: Up, Uptime: 00:01:32
To: [INVALID], From: [INVALID]
Type: BiDirectional
Name: tunnel1
LSP info:
Main: MAIN State: Down
BFD info:
Local State: Down Remote State: Down
Uptime: 00:00:00
Negotiated Rx Interval: 1234 Negotiated Tx
Interval: 1234
Remote Session Detect: <>
Local Discriminator: 1234 Remote Discriminator: 1234
Local Diag: <> Remote Diag: <>
LDI AIS state: Down
TPG info:
PscState: Remote protection failure BdtOperState: Down
false
LocalMepId 1-8191 Contains the LocalMepId value, configured at the
[chassis layer-2-options bridge-options
cfm-options] hierarchy level.
LocalMipConf true Boolean, set to true if local MIP ID exists.
false
oam provider Identifies the relevant MD level.
operator
nested-operator
MaConfigured true Boolean, indicates whether to configure MA/MEG.
false
MaName <string> Unique name identifying MA under this VSI.
MdLevel 0-7 Identifies corresponding domain under the relevant MD
Level (provider, operator, or nested-operator).
MdName <string> Unique name identifying MD under this VSI.
MegAlarmsEnabled enable If disabled, no alarms will be raised and collected.
disable (default)
MegCcmEnabled enable If enabled, allows CCM messages to be sent and
disable (default) received.
MegCcmPeriod 100ms CCM transmission period.
1000ms (default)
10000ms
60000ms
600000ms
MegId <unsigned integer> MEG identification. Generated automatically by STMS
or RCP, based on MA and MD names.
MegLlcfEnabled enable If enabled, allows LLCF functionality.
disable (default)
PmCollectionEnable enable Enables performance monitoring counter collection.
disable (default)
PmEnable enable Enables performance monitoring.
disable (default)
cos 5 {
provider {
md-level 4;
md-name pr;
ma-name u1-vsi1-5;
meg-id 42pr0029vsi1-5000000000000000000000000000000000;
meg-alarms-enable disable;
meg-ccm-enable disable;
meg-ccm-period 1s;
meg-llcf-enable disable;
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
}
cfm-options {
ltm-flooding disabled;
local-mep-id 100;
}
cos 5 {
provider {
md-level 4;
md-name pr;
ma-name u1-vsi1-5;
meg-id 42pr0029vsi1-5000000000000000000000000000000000;
meg-alarms-enable enable;
meg-ccm-enable enable;
meg-ccm-period 100ms;
meg-llcf-enable enable;
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
}
cos 5 {
provider {
md-level 4;
md-name pr;
ma-name u1-vsi1-5;
meg-id 42pr0029vsi1-5000000000000000000000000000000000;
meg-alarms-enable disable;
meg-ccm-enable disable;
meg-ccm-period 1s;
meg-llcf-enable disable;
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
operator {
md-level 2;
md-name op;
ma-name u1-vsi1-5;
meg-id 42pr0029vsi1-5000000000000000000000000000000000;
meg-alarms-enable enable;
meg-ccm-enable enable;
meg-ccm-period 100ms;
meg-llcf-enable enable;
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
nested_operator {
md-level 1;
md-name nop;
ma-name u1-vsi1-5;
meg-id 42pr0029vsi1-5000000000000000000000000000000000;
meg-alarms-enable enable;
meg-ccm-enable enable;
meg-ccm-period 100ms;
meg-llcf-enable enable;
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
}
}
cos 1 {
provider {
md-level 3;
md-name pr;
ma-name u1-vsi1-1;
meg-id 42pr0026vsi1-1000000000000000000000000000000000;
meg-alarms-enable disable;
meg-ccm-enable disable;
meg-ccm-period 1s;
meg-llcf-enable disable;
remote-mep 10 {
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
remote-mep 11 {
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
pm-enable disable;
pm-collection-enable disable;
severity-profile default;
alarm-master-mask disable;
}
}
NMSID MEGID COS LVL MEP MIP ALARMS CCM CCMPRD RDI RMTDFECT RMEPCNT
1 0 1 2 N Y N N 1000 N N 0
lsh> run show cfm meg slot u1 vsi-name vsi1 cos 1 oam operator
Nms-Id: 1
Meg Id: 0
Cos: 1
Md Lvl: 2
Mep: N
Mip: Y
Alarms: N
Ccm: N
Ccm Period: 1000
SendingRDI: N
RmtDefect: N
SNo RMepId RMepOperState RMepRdi
Total number of Megs Configured: 1
For example:
lsh> run cfm loopback target-mac 00:20:8f:80:9e:00 instance
slot-u1-routing-instance vsi-name vsi1 cos 1 oam operator.
For example:
lsh> run cfm link-trace target-mac 00:20:8f:80:9e:00 instance
slot-u1-routing-instance vsi-name vsi1 cos 1 oam operator
Non-service-affecting alarms:
Severity Timestamp Alarm Name Type Element Name
-----------------------------------------------------------------------
major 2014-06-27,02:43:15 megCfmMismerge protocol u1-vsi1-0pr
major 2014-06-27,02:43:15 megUnexpectedMep protocol u1-vsi1-0pr
major 2014-06-27,02:43:15 megUnexpectedPeriod protocol u1-vsi1-0pr
Non-service-affecting alarms:
Severity Timestamp Alarm Name Type Element Name
--------------------------------------------------------------------------
major 2014-06-27,02:43:40 rmepSlmUnavailBackward protocol
u1-vsi1-0pr-10
major 2014-06-27,02:43:40 rmepSlmUnavailForward protocol
u1-vsi1-0pr-10
major 2014-06-27,02:43:40 dmIncomplemeteMeasurements15M protocol
u1-vsi1-0pr-10
major 2014-06-27,02:43:40 fD15M protocol
u1-vsi1-0pr-10
major 2014-06-27,02:43:40 fDVBackward15M protocol
u1-vsi1-0pr-10
Examples of this configuration statement are included in this section. For more information, see the STMS
User Guide.
TIP: VSIs are configured under routing instances, identified by the card's slot number
(slot-u1-routing-instance). Use the show routing-instances command to see this
option. To configure port mapping, no explicit configuration is required at the card level. The
necessary routing instance is created automatically as part of the card assignment stage for a
selected slot. For example:
lsh> set chassis slot u1 aoc10-l2
lsh> commit
lsh> show routing-instance
slot-u1-routing-instance {
instance-type forwarding;
}
p-bit 1 {
cos 1;
}
<default p-bit values>
}
egress-cos-pbit-mapping {
cos 0 {
p-bit 0;
}
cos 1 {
p-bit 1;
}
<default cos values>
}
ingress-dscp-cos-mapping{
state disable;
}
}
}
}
...
...
p-bit 0 {
cos 0;
}
p-bit 1 {
cos 0;
}
p-bit 2 {
cos 5;
}
p-bit 3 {
cos 0;
}
<default p-bit values>
}
...
p-bit 0 {
cos 0;
}
p-bit 1 {
cos 1;
}
p-bit 2 {
cos 5;
}
p-bit 3 {
cos 3;
}
<default p-bit values>
...
...
cos 0 {
p-bit 0;
}
cos 1 {
p-bit 1;
}
cos 2 {
p-bit 5;
}
cos 3 {
p-bit 3;
}
<default cos values>
...
ingress-dscp-cos-mapping {
state enable;
dscp cs0 {
cos 0;
}
dscp cs1 {
cos 0;
}
<default dscp csx values>
dscp af11 {
cos 5;
}
dscp af12 {
cos 0;
}
<default dscp afx values>
dscp af43 {
cos 0;
}
dscp ef-phb {
cos 0;
}
}
ingress-dscp-cos-mapping {
state enable;
dscp cs0 {
cos 0;
}
dscp cs1 {
cos 0;
}
<default dscp values>
dscp af11 {
cos 5;
}
routing-instances {
slot-u1-routing-instance {
// Routing Instance are created implicitly for each slot
virtual-switching-instances {
vsi_bar {
instance-type <MP2MP|P2P|ROOTED_MP|RSTP|ERP>;
uni-ports {
ingress-pbit-cos-mapping {
p-bit<0-7> {
<cos<0-7> | discard >;
} // end priority
} // end ingress-priority-cos-mapping
ingress-dscp-cos-mapping {
state <enable | disable>
dscp<codepoint-name> {
<cos<0-7> | discard >;
} // end dscp
} // end ingress-dscp-cos-mapping
} // end uni-ports
nni-ports {
ingress-pbit-cos-mapping {
p-bit<0-7> {
<cos<0-7> | discard >;
} // end priority
} // end ingress-priority-cos-mapping
egress-cos-pbit-mapping {
cos<0-7> {
p-bit<0-7>;
} // end cos
} // end egress-cos-priority-mapping
ingress-dscp-cos-mapping {
state <enable | disable>
dscp< codepoint-name > {
<cos<0-7> | discard >;
} // end dscp
} // end ingress-dscp-cos-mapping
} // end nni-ports
} // end virtual-switching-instance-name
} // end virtual-switching-instances
} // end routing-instance-name
} // end routing-instances
wait-to-restore Range from 1 to 12 minutes in A fixed period of time that must elapse
1 minute steps after a failure recovery before traffic
Default 5 minutes channel reverts to the original path.
Can be modified only when node-role is
RPL Owner.
Examples of this configuration statement are included in this section. For more information, see the STMS
User Guide.
lsh>commit
ethernet-options {
(auto-negotiation | no-auto-negotiation);
(flow-control | no-flow-control);
ifg-optimization (enabled | disabled);
speed (10g | 1g | 100m | 10m);
pma-mode (master | slave);
port-mode (uni | e-nni | i-nni | moe | i-moe | mirror);
stpId <stpId>;
llcf-options {
llcf-ingress-enable (enabled | disabled);
llcf-egress-enable (enabled | disabled);
} // end llcf-options
pause-options {
force-pause (enabled | disabled);
pause-type (rx-only | disable);
pause-advertisement (no-pause | sym-pause | asym-pause | sym-asym-pause);
} // end pause-options
rstp-options {
port-enable (enabled | disabled);
priority <priority>;
path-cost <path-cost>;
hold-off-time <hold-off-time>;
port-change-detect (enabled | disabled);
dynamic-port-cost-update (enabled | disabled);
admin-edge (enabled | disabled);
auto-cost-config (enabled | disabled);
bpdu-mac-address (bridge-group | provider-bridge-group);
} // end rstp-options
ethernet-options {
vlan-ethertype (0x8100 | 0x88a8 | 0x9100 | 0x9200);
outer-vlan-id <VlanId> {
vlan-ethertype (0x8100 | 0x88a8 | 0x9100 | 0x9200);
}
err-frame-period-threshold <err-frame-period-threshold>;
err-frame-period-window <err-frame-period-window>;
err-frame-sec-sum-threshold <err-frame-sec-sum-threshold>;
err-frame-sec-sum-window <err-frame-sec-sum-window>;
} // end link-oam-options
} // end ethernet-options
The following statement is used to configure EXP bit mapping, working at the
[edit routing-instances routing-instance protocols mpls interface] hierarchy level.
exp-map {
cos <cos> {
out-exp {
color-green <color-green>;
color-yellow <color-yellow>;
}
}
in-exp <in-exp> {
cos <cos>;
color (green | yellow);
}
}
The following table lists the parameters and options available when configuring EXP bit mapping. For more
information, see the STMS User Guide.
Attribute/
Options Description
Keyword
cos cos value ranging from 0 to 7 or Defines Class of Service value.
discard (default) Configured implicitly for outgoing
traffic.
color green Defines color to be mapped, together
yellow with CoS value, to EXP bit.
N/A (default) Configured implicitly for outgoing
traffic.
lsh# commit
lsh# commit
Port configuration automatically creates a physical interface (PIF) and an MPLS interface. These can
be configured with a show interfaces command.
slot-u0-routing-instance {
description "routing-instance for interfaces
belonging to card in slot u0";
instance-type forwarding;
interface ge-u0/0.1;
protocols {
mpls {
…
interface ge-u1/1.1 {
…
exp-map {
in-exp 0 {
cos discard;
color N/A;
}
// <continue with in-exp 1...in-exp 7>
in-exp 7 {
cos discard;
color N/A;
}
cos 0 {
color green {
out-exp N/A;
}
color yellow {
out-exp N/A;
}
}
// <continue with cos 1...cos 7>
} // end exp-map
} // end interface
} // end mpls
} // end protocols
slot-id u0;
} // end routing-instance
slot-u0-routing-instance {
description "routing-instance for interfaces
belonging to card in slot u0";
instance-type forwarding;
interface ge-u0/0.1;
protocols {
mpls {
…
interface ge-u1/1.1 {
…
exp-map {
in-exp 0 {
cos 0;
color green;
}
in-exp 1 {
cos 0;
color yellow;
}
in-exp 2 {
cos 1;
color green;
}
in-exp 3 {
cos 1;
color yellow;
}
in-exp 4 {
cos 2;
color green;
}
in-exp 5 {
cos 2;
color yellow;
}
in-exp 6 {
cos 6;
color green;
}
in-exp 7 {
cos 7;
color green;
}
cos 0 {
color green {
out-exp 0;
}
color yellow {
out-exp 0;
}
}
cos 1 {
color green {
out-exp 1;
}
color yellow {
out-exp 2;
}
}
cos 2 {
color green {
out-exp 3;
}
color yellow {
out-exp N/A;
}
}
cos 3 {
color green {
out-exp N/A;
}
color yellow {
out-exp N/A;
}
}
cos 4 {
color green {
out-exp N/A;
}
color yellow {
out-exp N/A;
}
}
cos 5 {
color green {
out-exp N/A;
}
color yellow {
out-exp 4;
}
}
cos 6 {
color green {
out-exp 5;
}
color yellow {
out-exp N/A;
}
}
cos 7 {
color green {
out-exp 7;
}
color yellow {
out-exp N/A;
}
}
} // end exp-map
} // end interface
} // end mpls
} // end protocols
slot-id u0;
} // end routing-instance
lsh# commit
lsh# commit
severity-profiles {
...
profile-name card default {
...
probable-cause hostBudgetExceeded {
severity minor;
report true;
}
probable-cause hostBudgetLowResources {
severity warning;
report true;
}
probable-cause bscDiscardSeconds15M {
severity warning;
report true;
}
probable-cause lowClassDiscardPrcntPkts15M {
severity warning;
report true;
}
probable-cause macMove15M {
severity major;
report true;
}
probable-cause fdbFullSec15M {
severity minor;
report true;
}
} // end profile-name
} // end severity-profiles
severity-profiles {
...
profile-name card default {
...
probable-cause fdbFullSec15M {
severity minor;
report true;
} // end configuration for fdbFullSec15M probable cause
} // end profile name
} // end severity-profiles
severity-profiles {
...
profile-name card default {
...
probable-cause fdbFullSec15M {
severity major;
report false;
} //
} //
} //
Non-service-affecting alarms:
Severity Timestamp Alarm Name Type
Element Name
---------------------------------------------------------------------
--------
minor 2014-04-02,17:58:39 rxPowerHigh l2-eth-port
port-u1/0
Service-affecting alarms:
Severity Timestamp Alarm Name Type Element
Name
---------------------------------------------------------------------
----
major 2014-04-02,17:58:39 equipmentOut l2-eth-port port-u1/0
major 2014-04-02,17:58:39 wavelengthMismatch l2-eth-port port-u1/0
Non-service-affecting alarms:
2. Configure ports.
# set chassis slot u1 aoc10-l2 port 1 port-type ge ethernet-options
port-mode uni
# set chassis slot u1 aoc10-l2 port 2 port-type ge ethernet-options
port-mode uni
# commit
Examples of various LAG configuration actions are included in the rest of this section. For more information,
see the STMS User Guide.
The following code line and resulting output listing illustrate typical command usage. Note that most of the
configuration settings are automatically configured and don't require explicit user intervention.
ge-u1/1 {
ethernet-options {
lag-master {
lag-link-down-threshold 8;
lag-protection-type load-sharing;
lag-distribution enable;
pm-monitor disable;
pm-profile default;
severity profile default;
}
}
… // Other information
}
The following code line and resulting output listing illustrate typical command usage. Note that most of the
configuration settings are automatically configured and don't require explicit user intervention.
ge-u1/2 {
ethernet-options {
lag-slave {
master-port ge-u1/1;
lag-distribution disable;
}
}
… // Other information
}
Where <if-name> is the name of the Slave port being deleted. For example:
NOTE: Deleting a LAG Master essentially means deleting the LAG Group, since without a
Master link there is no LAG Group. LAG Masters can only be deleted if there are no LAG Slaves
or services associated with that Master. Therefore, you must delete all participating LAG
Slaves before deleting the associated LAG Master.
To delete a LAG Master link from a LAG group, include the following statement at the
[edit interface] hierarchy level.
Where <if-name> is the name of the Master port being deleted. For example:
Where <if-name> is the name of the Master port and <threshold number> is the minimum value. For
example:
For example:
OR
For example:
The following lines illustrate the comparable command for a LAG slave.
Slot: u1
MasterPort: ge-u1/1
SlaveMembers:
ge-u1/2;
ge-u1/3;
MasterPort: ge-u1/4
SlaveMembers:
ge-u1/5;
To list detailed information about all LAG Groups configured for a specific slot, include the following
statement at the
[edit interface] hierarchy level.
Slot: u1
MasterPort: ge-u1/1
LinkDownThreshold ProtectionType LagDistributionStatus OperStatus
8 load-sharing enabled Up
SlaveMembers:
PortName LagDistributionStatus OperStatus
ge-u1/2 enabled Up
ge-u1/3 disabled Down
MasterPort: ge-u1/4
LinkDownThreshold ProtectionType LagDistributionStatus OperStatus
8 load-sharing enabled Up
SlaveMembers:
PortName LagDistributionStatus OperStatus
ge-u1/5 enabled Up
Slot: u1
MasterPort: ge-u1/1
SlaveMembers:
ge-u1/2;
ge-u1/3;
To list detailed information about all LAG Groups configured for a specific slot and port, include the
following statement at the
[edit interface] hierarchy level.
Slot: u1
MasterPort: ge-u1/1
LinkDownThreshold ProtectionType LagDistributionStatus OperStatus
8 load-sharing enabled Up
SlaveMembers:
PortName LagDistributionStatus OperStatus
ge-u1/2 enabled Up
ge-u1/3 disabled Down
Attribute/
Options Description
Keyword
llcf-egress-enable enabled Enables or disables LLCF on the egress
disabled (default) side.
llcf-ingress-enable enabled Enables or disables LLCF on the ingress
disabled (default) side.
Attribute/
Options Description
Keyword
igmp-multicast- 0-800 Configures the multicast address
address-limit Default 800 threshold.
mpls-pe-options {
pe-id <pe-id>;
mpls-id <mpls-id>;
}
mpls {
interface <ifname> {
exp-map {
cos <cos> {
out-exp {
color-green <color-green>;
color-yellow <color-yellow>;
}
}
in-exp <in-exp> {
cos <cos>;
color (green | yellow);
}
}
performance-monitoring (enabled | disabled);
tunnel-capacity-mode (normal | extended);
next-hop-mac-address <next-hop-mac-address>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
} // end interface
label-switched-path <lsp_name> {
adaptive;
admin-groups {
exclude-groups [ <group_name> ];
include-groups [ <group_name> ];
include-all-groups [ <group_name> ];
}
bandwidth <bps>;
bidirectional;
disable;
description <description>;
fast-reroute {
admin-groups {
exclude-groups [ <group_name> ];
include-groups [ <group_name> ];
include-all-groups [ <group_name> ];
}
bandwidth <bps>;
hop-limit <hop_limit>;
priority <setup_priority> <hold_priority>;
}
from <from>;
no-record;
hop-limit <hop_limit>;
(random | least-fill | most-fill);
record-label;
link-protection;
no-cspf;
no-decrement-ttl;
no-revert;
no-revert-from-bypass;
node-link-protection;
optimize-timer <optimize_timer>;
preference <preference>;
primary <path_name> {
adaptive;
admin-groups {
exclude-groups [ <group_name> ];
include-groups [ <group_name> ];
include-all-groups [ <group_name> ];
}
bandwidth <bps>;
disable;
fast-reroute {
admin-groups {
exclude-groups [ <group_name> ];
include-groups [ <group_name> ];
include-all-groups [ <group_name> ];
}
bandwidth <bps>;
hop-limit <hop_limit>;
priority <setup_priority> <hold_priority>;
}
hop-limit <hop_limit>;
ignore-retry-limit;
no-cspf;
no-record;
optimize-timer <optimize_timer>;
preference <preference>;
priority <setup_priority> <hold_priority>;
record;
} // end primary
fast-reroute {
admin-groups {
exclude-groups [ <group_name> ];
include-groups [ <group_name> ];
include-all-groups [ <group_name> ];
}
bandwidth <bps>;
hop-limit <hop_limit>;
priority <setup_priority> <hold_priority>;
}
hop-limit <hop_limit>;
no-cspf;
no-record;
optimize-timer <optimize_timer>;
preference <preference>;
priority <setup_priority> <hold_priority>;
record;
standby;
} // end secondary
to <destination>;
} // end label-switched-path
no-propagate-ttl;
path <path_name> {
<next_hop> {
(strict | loose);
interface-id <interfaceId>;
interface-name <interfaceName>;
downstream-Label <downStreamLabel>;
upstream-Label <upStreamLabel>;
}
} // end path
static {
tunnel <tunnel> {
bandwidth <bps>;
bypass;
control-channel-cos <control-channel-cos>;
subscription <subscription>;
description <description>;
destaddr <destaddr>;
disable;
directionality (uni-directional | bi-directional);
from <src-pe-id>;
no-revert-from-bypass;
originating-tunnel {
main-lsp <main-lsp> {
backward-path {
in-segment {
label <inlabel>;
interface <ifname>;
}
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
} // end bfd
disable;
forward-path {
out-segment {
bandwidth <bps>;
label <label>;
nexthop <nexthop>;
preference <preference>;
protected-by {
disable;
outgoing-bypass <bypasstunnel>;
merge-label <label>;
}
nms-tunnel-identifier <nmsidentifier>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end forward-path
pm-monitor (enable | disable);
}// end main-lsp
protection-lsp <prot-lsp> {
backward-path {
in-segment {
label <inlabel>;
interface <ifname>;
}
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
} // end bfd
disable;
forward-path {
out-segment {
bandwidth <bps>;
label <label>;
nexthop <nexthop>;
preference <preference>;
protected-by {
disable;
outgoing-bypass <bypasstunnel>;
merge-label <label>;
}
nms-tunnel-identifier <identifier>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end forward path
pm-monitor (enable | disable);
} // end protection-lsp
} // end originating-tunnel
psc-protocol {
psc-max-refresh-interval <psc-max-refresh-interval>;
}
terminating-tunnel {
main-lsp <main-lsp> {
backward-path {
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
} // end bfd
disable;
forward-path {
bandwidth <bps>;
in-segment {
label <inlabel>;
interface <ifname>;
protected;
} // end in-segment
nms-tunnel-identifier <nmsidentifier>;
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end forward-path
pm-monitor (enable | disable);
} // end main-lsp
protection-lsp <protection-lsp> {
backward-path {
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
} // end out-segment
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
} // end tm-options
} // end backward-path
bfd {
admin-state (enabled | disabled);
detection-multiplier <detection-multiplier>;
min-rx-interval <min-rx-interval>;
min-tx-interval <min-tx-interval>;
} // end bfd
disable;
forward-path {
in-segment {
label <inlabel>;
interface <ifname>;
}
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end forward-path
pm-monitor (enable | disable);
} // end protection-lsp
} // end terminating-tunnel
tpg-options {
hold-off-time-main <hold-off-time-main>;
hold-off-time-prot <hold-off-time-prot>;
pm-monitor (enabled | disabled);
psc-maint-cmd (release | lockout | force-switch | manual-switch |
manual-reversion);
revertive-mode (enabled | disabled);
wait-to-restore-time <wait-to-restore-time>;
}
transit-tunnel {
main-lsp <main-lsp> {
ais-ldi (enabled | disabled);
backward-path {
in-segment {
label <inlabel>;
interface <ifname>;
}
out-segment {
label <label>;
nexthop <nexthop>;
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
}
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end backward-path
disable;
bidir-lsp-num <bidir-lsp-num>;
forward-path {
bandwidth <bps>;
in-segment {
label <inlabel>;
interface <ifname>;
protected;
}
out-segment {
label <outlabel>;
nexthop <nexthop>;
protected-by {
disable;
merge-label <label>;
outgoing-bypass <bypass-name>;
}
severity-profile <severity-profile>;
alarm-master-mask (enable | disable);
pm-profile <pm-profile>;
}
nms-tunnel-identifier <nmsidentifier>;
tm-options {
cos <cos> {
bandwidth <bandwidth>;
}
}
} // end forward-path
pm-monitor (enable | disable);
} // end main-lsp
} // end transit-tunnel
preference <preference>;
revert-time <revert-time>;
nms-tunnel-identifier <nmsidentifier>;
to <dest-pe-id>;
type (terminating | originating | transit);
severity-profile <severity-profile>;
pm-monitor (enable | disable);
alarm-master-mask (enable | disable);
}
} // end static
traceoptions {
file {
<filename>;
files <files>;
no-stamp;
no-world-readable;
replace;
size <size>;
world-readable;
}
flag (all | cspf | cspf-link | cspf-node | error | state);
}
traffic-engineering (bgp | bgp-igp);
} // end mpls
Attribute/
Options Description
Keyword
Slot/Card attributes
[edit chassis slot slot card-name] hierarchy level
mpls-id 0-65535 MPLS network ID.
Default 1
pe-id 1-65535 PE ID.
Default 65535
Protocol/MPLS attributes
[routing-instances routing-instance protocols mpls] hierarchy level
next-hop-mac-address FF:FF:FF:FF:FF:FF (default) Relevant for MoE ports only.
Used as MAC-DA of MPLS frames
transmitted from MoE ports.
Default value must be changed to
Unicast/Broadcast MAC address
before the port can be enabled.
Changing the address while MoE
port is enabled may be traffic
affecting.
tunnelCapacityMode normal (default)
extended
hierarchical
Attribute/
Options Description
Keyword
force-pause enabled Enables or disables the force-pause
disabled (default) option. Valid for Ethernet ports only. Not
supported on 10GbE ports.
pause-advertisement noPause (default) Advertisement of the local device
SymPause regarding the FC capacity. Not supported
AsymPause on 10GbE ports.
SymAsymPause
pause-type autoNeg Local pause configuration, for Ethernet
disable ports only. Not supported on 10GbE
transmit ports.
receive (default)
transmit-receive
Attribute/
Options Description
Keyword
pm-monitor enabled (default) The system should (enabled) or should not
disabled (disabled) utilize performance monitoring
(PM). Performance monitoring can be
configured at various hierarchical levels for a
wide range of system entities.
pm-profile <pm-profile name> Specifies a user-defined PM profile to be
applied. Profiles are used to store sets of
user-defined PM thresholds. Traffic
performance can be monitored using either
the default system settings or some
combination of user-defined settings.
lsh> commit
lsh> commit
policer-state no-rate-limit
Defines the policing conditions.
blocked
If set to policing, a policer profile name
policing must also be supplied.
If set to blocked, all traffic on this port is
dropped. (Default for egress, UNI, and
E-NNI ports.)
If set to no-rate-limit, only internal
policing mechanisms are applied.
(Default for ingress and I-NNI ports.)
policing-info Container for subset of options configuring
policing conditions at the interface level.
profile-name <string> Identifies the policer profile in a routing
instance, should be unique within the routing
instance.
routing-instance-nam <string> Unique string that identifies this routing
e instance. With the following format:
slot-u<x>-routing-instance
vsi-name <string> Name of the VSI in which this port is
participating.
cd-vlans {
10;
}
policing-info {
ingress {
policer-state no-rate-limit;
policer-profile N/A;
per-cos-policers {
cos 0 {
policer-state policing;
policer-profile profile_1;
policer-group 0;
} // end cos0
cos 1 {
policer-state policing;
policer-profile profile_1;
policer-group 0;
} // end cos1
cos 2 {
policer-state policing;
policer-profile profile_1;
policer-group 0;
} // end cos2
cos 3 {
policer-state policing;
policer-profile profile_1;
policer-group 4;
} // end cos3
cos 4 {
policer-state policing;
policer-profile profile_1;
policer-group 4;
} // end cos4
cos 5 {
policer-state policing;
policer-profile profile_1;
policer-group 4;
} // end cos5
cos 6 {
policer-state no-rate-limit;
policer-profile N/A;
policer-group N/A;
} // end cos6
cos 7 {
policer-state blocked;
policer-profile N/A;
policer-group N/A;
} // end cos7
} // end per-cos policers
} // end ingress
egress {
policer-state blocked;
policer-profile N/A;
} // end egress
} // end policing info
} // end interface ge-u1/0
} // end uni ports
nni-ports {
s-vlan 100;
ge-u1/1 {
policing-info {
ingress {
policer-state blocked;
policer-profile N/A;
}
egress {
policer-state blocked;
policer-profile N/A;
}
}
}
} // end nni ports
} // end vsi instance
} // end vsi
} // end routing-instance
ge-u1/1 {
policing-info {
ingress {
policer-state no-rate-limit;
policer-profile N/A;
}
egress {
policer-state blocked;
policer-profile N/A;
}
}
unit 100 {
vlan 100;
}
}
Configurations in which the Source Port and the Destination Port are located on the same switch are
considered local. Remote port mirroring is not implemented in the current release.
Port mirroring configuration commands are located within the layer2-ethernet-options,
bridge-options, and interfaces containers, as illustrated in the following code samples.
layer2-ethernet-options {
...
bridge-options {
...
port-mirroring-options {
source-port port;
ingress-dest-port port;
egress-dest-port port;
}
...
}
...
}
The ingress and egress destination ports can be configured on same port. All destination mirror ports must
be configured in port-mode mirror. The source port can be in any port-mode other than mirror, and
the source port must be different from the destination ports. Port mode is also set to mirror as part of the
ethernet-options configuration within the [chassis slot port] level.
layer2-ethernet-options {
...
bridge-options {
...
port-mirroring-options {
source-port port-u1/0;
ingress-dest-port port-u1/1;
egress-dest-port port-u1/2;
}
...
}
...
}
layer2-ethernet-options {
...
bridge-options {
...
port-mirroring-options {
source-port port-u1/0;
ingress-dest-port port-u1/1;
egress-dest-port port-u1/4;
}
...
}
...
}
rstp-options {
rstp-notifications (enabled | disabled);
bridge-priority <priority>;
max-age <max-age>;
hello-time <hello-time>;
forward-delay <forward-delay>;
bpdu-frame-format (standard | standard-b);
tx-hold-count <tx-hold-count>;
}
rstp {
disable;
bpdu-dest-mac (bridge-group | provider-bridge-group);
bridge-priority <bridge-priority>;
forward-delay <forward-delay>;
force-version <force-version>;
hello-time <hello-time>;
interface <ifname> {
cost <cost>;
disable;
edge;
mode (point2point | shared);
priority <priority>;
}
max-age <max-age>;
traceoptions {
file {
<filename>;
files <files>;
no-stamp;
no-world-readable;
replace;
size <size>;
world-readable;
}
flag (all | error | general | normal | packets | rstp | mstp | stp-config
| stp-tc | policy | port-receive-statestate-machine | port-migration-state-machine
| bridge-detect-state-machine | port-transmit-state-machine |
port-information-state-machine | port-role-selection-state-machine |
port-role-transition-state-machine | port-state-transition-state-machine |
topology-change-state-machine | state | task | timer) detail disable hex-dump receive
send;
}
tx-hold-count <tx-hold-count>;
}
Card options
[edit chassis slot slot card-name] hierarchy level
bpdu- Standard-BPDU Specifies type of BPDU frame format.
frame-format Standard-BPDU-B
(default)
bridge priority 0-61440 Specifies the RSTP Bridge Priority to be used along with
Default 8192 the Bridge's MAC Address.
Steps of 4096
forward delay 4-30 seconds The time that the bridge stays in each of the Listening
Default 15 seconds and Learning states that precede the Forwarding State.
In addition, when a topology change is underway and
has been detected, this parameter is used to age all
dynamic entries in the Forwarding database.
hello time 1-10 seconds Specifies the time interval between the generation of
Default 2 seconds Configuration BPDUs by the Root. Set to 2 seconds for
802.1D-2004 compliant RSTP (no validations).
max age 6-40 seconds Specifies the time that learned Spanning Tree
Default 20 seconds information is kept before being discarded.
notifications enable (default) Enable or disable RSTP notifications.
disable
tx hold count 1-10 Time interval within which no more than two
Default 3 configuration BPDU frames is transmitted.
Port options
[edit chassis slot slot card-name port port ethernet-options] hierarchy level
admin-edge true Defines the initial port state value to use when the
false port is enabled.
For edge ports, default false.
auto-cost-config enabled Enables or disabled automatic cost configuration.
disabled Default enable.
bpdu-mac-address bridge-group Defines the BPDU MAC DA to be used by RSTP. Default
provider-bridge- values depend on the port type:
group ETY UNI: 01-80-C2-00-00-00
ETY NNI: 01-80-C2-00-00-08
RSTP VI: 01-80-C2-00-00-00
(not changeable)
dynamic-port-cost- enabled Enables or disables dynamic updating of port cost
update disabled values.
hold-off-time 0-10,000msec Amount of time to hold off and wait before beginning
Default 200msec fault management and error recovery.
The committed information rate (CIR) is divided by the overbooking factor to determine actual
bandwidth allocated for this customer's virtual circuit. For example, if 10Mb of bandwidth have been
allocated for CoS-0 and the overbooking factor is 2, then the actual bandwidth allocation for CoS-0 is
10/2=5Mb.
Note that the higher the overbooking factor, the more aggressive or higher the overbooking. For
example, with an overbooking value of 2 (allocating 50% of the actual BW configured in the link), a
customer requesting a T1 (1.5Kbps) line is allocated 0.75Kbps. By comparison, with an overbooking
value of 1.5 (allocating 66% of the actual BW configured in the link), the allocated bandwidth is 1Kbps
for the same request. The larger overbooking value of 2 is more aggressive, accepting more VCs per
trunks.
The overbooking factor is defined per CoS, with a higher priority CoS entitled to a higher overbooking
factor. The overbooking factor can be changed only while the CoS is not "in use", meaning no MPLS
XCs are configured for this CoS.
A scheduler enforces a minimum average bandwidth for a CoS by pulling packets to be forwarded
from that class’s queue at regular intervals. Scheduling may be either automatic or manual.
Scheduling in ShadeTree is currently available in automatic mode only.
Weighted Random Early Detection (WRED) is a method of avoiding congestion by discarding selected
packets. WRED allows packets within the same queue to have different minimum and maximum
discard thresholds. The packet's service precedence (part of the CoS) determines the discard
thresholds. WRED is particularly useful for preventing lower-priority traffic from consuming shared
buffers and starving higher-priority traffic. WRED may be configured either automatically or manually.
WRED in ShadeTree is currently available in automatic mode only.
Shaping is a mechanism for controlling the rate at which the switch router transmits traffic through
the network. Shaping buffers traffic so that the switch router can send the traffic through the network
in manageable amounts. Shaping the traffic limits congestion and ensures that traffic conforms to
established rates. Shaping may be configured either automatically or manually. Shaping in ShadeTree
is currently available in automatic mode only.
slot u2 aoc10-l2 {
enable;
severity-profile default;
alarm-master-mask disable;
layer2-ethernet-options { //implicitly created
mode mpls-pe;
ethernet-network-id 0;
bridge-options { //implicitly created
rstp-options { //implicitly created
}
cfm-options { //implicitly created
}
ccn-options { //implicitly created
}
}
tm-options { //Valid only when card mode is mpls-pe
and is implicitly created
high-priority-cos-delimiter <0-8>; // default is 6
sched-mode <auto>; // cannot be changed by user
per-cos-tm{
cos <0-7>{ //implicitly created
over-booking-factor <0.1-100.0>; // default is 1.0
best-effort-cos <enabled/disabled>; // default is disabled
}
}
}
fdb-options { //implicitly created
}
mpls-pe-options { //implicitly created
}
}
interfaces {
ge-u2/1 {
ethernet-options {
max-frame-size 1604;
tm-options{ //implicitly created
shaping-mode <auto>; // cannot be changed by user
per-cos-tm{
cos <0-7>{ //implicitly created
wred-mode <auto>; // cannot be changed by user
}
}
}
}
monitor-utilization {
severity-profile default;
}
unit 1 {
family mpls;
}
}
} //interfaces
bsc-policer-profile Default-BSC-Profile;
user-label 777;
egress-counting disabled;
vsi-type mp2mp;
max-fib-size 100;
nms-service-identifier 1231237294;
pm-monitor disable;
pm-profile default;
state enabled;
uni-ports {
ge10-u0/18 {
cd-vlan-ids {
777;
}
policing-info {
ingress {
cos 0 {
policer-state policing;
policer-profile CIR_1000_CBS_1_EIR_2000_EBS_2_CM_0_CF_0;
policer-group 0;
pm-monitor disable;
}
cos 1 {
policer-state policing;
policer-profile CIR_1000_CBS_1_EIR_2000_EBS_2_CM_0_CF_0;
policer-group 1;
pm-monitor disable;
}
}
egress {
cos 0 {
policer-state no-rate-limit;
policer-profile N/A;
policer-group 0;
pm-monitor disable;
}
cos 1 {
policer-state no-rate-limit;
policer-profile N/A;
policer-group 1;
pm-monitor disable;
}
}
}
ingress-untagged-ptagged-vlan disabled;
ingress-wildcard-vlan disabled;
}
ingress-pbit-cos-mapping {
p-bit 1 {
cos 1;
}
}
ingress-dscp-cos-mapping {
state disabled;
}
}
nni-ports {
s-vlan 777;
ge-u0/2;
}
pseudo-wires {
1037@1231237294 {
remote-pe-id 1:22222;
split-horizon-group 1;
receive-pw-label 4097;
transmit-pw-label 4097;
transmit-tunnel tunnel:6035@U0@70;
}
}
severity-profile default;
alarm-master-mask disable;
bsc-policer-profile Default-BSC-Profile;
user-label "XDM 1K-Nikhi_14-01-2015_12:44:57";
egress-counting disabled;
vsi-type mp2mp;
max-fib-size 100;
nms-service-identifier 1231237295;
pm-monitor disable;
pm-profile default;
state enabled;
uni-ports {
ge10-u0/18 {
cd-vlan-ids {
888;
}
policing-info {
ingress {
cos 0 {
policer-state policing;
policer-profile CIR_1000_CBS_1_EIR_2000_EBS_2_CM_0_CF_0;
policer-group 0;
pm-monitor disable;
}
cos 1 {
policer-state policing;
policer-profile CIR_1000_CBS_1_EIR_2000_EBS_2_CM_0_CF_0;
policer-group 1;
pm-monitor disable;
}
}
egress {
cos 0 {
policer-state no-rate-limit;
policer-profile N/A;
policer-group 0;
pm-monitor disable;
}
cos 1 {
policer-state no-rate-limit;
policer-profile N/A;
policer-group 1;
pm-monitor disable;
}
}
}
ingress-untagged-ptagged-vlan disabled;
ingress-wildcard-vlan disabled;
}
ingress-dscp-cos-mapping {
state enabled;
dscp cs0_other {
cos 0;
}
dscp cs1 {
cos 1;
}
dscp cs2 {
cos 0;
}
dscp cs3 {
cos 0;
}
dscp cs4 {
cos 0;
}
dscp cs5 {
cos 0;
}
dscp cs6 {
cos 0;
}
dscp cs7 {
cos 0;
}
dscp af11 {
cos 0;
}
dscp af12 {
cos 0;
}
dscp af13 {
cos 0;
}
dscp af21 {
cos 0;
}
dscp af22 {
cos 0;
}
dscp af23 {
cos 0;
}
dscp af31 {
cos 0;
}
dscp af32 {
cos 0;
}
dscp af33 {
cos 0;
}
dscp af41 {
cos 0;
}
dscp af42 {
cos 0;
}
dscp af43 {
cos 0;
}
dscp ef_phb {
cos 0;
}
}
}
pseudo-wires {
1037@1231237295 {
remote-pe-id 1:22222;
split-horizon-group 1;
receive-pw-label 4098;
transmit-pw-label 4098;
transmit-tunnel tunnel:6035@U0@70;
}
}
severity-profile default;
alarm-master-mask disable;
slot u2 aoc10-l2 {
enable;
severity-profile default;
alarm-master-mask disable;
layer2-ethernet-options {
mode mpls-pe;
ethernet-network-id 0;
bridge-options {
rstp-options {
}
cfm-options {
}
ccn-options {
}
} //end bridge options
tm-options {
high-priority-cos-delimiter 6;
sched-mode <auto>; //cannot be changed by user
per-cos-tm{
cos 0{
over-booking-factor 1.0;
best-effort-cos disabled;
}
cos 1{
over-booking-factor 1.0;
best-effort-cos disabled;
}
... <repeated for each cos value, 0 through 7>
} // end per-cos-tm
} // end tm-options
} // end layer2-ethernet-options
} // end slot options
lsh> commit
slot u2 aoc10-l2 {
enable;
severity-profile default;
alarm-master-mask disable;
layer2-ethernet-options {
mode mpls-pe;
ethernet-network-id 0;
bridge-options {
rstp-options {
}
cfm-options {
}
ccn-options {
}
}
tm-options {
high-priority-cos-delimiter 5;
sched-mode <auto>; //cannot be changed by user
per-cos-tm{
cos 0{
over-booking-factor 1.0;
best-effort-cos disabled;
}
cos 1{
over-booking-factor 1.0;
best-effort-cos disabled;
}
cos 2{
over-booking-factor 1.0;
best-effort-cos disabled;
}
cos 3{
over-booking-factor 0.2;
best-effort-cos enabled;
}
<default cos settings through cos 7>
} // end per-cos-tm
} // end tm-options
} // end slot
lsh> set chassis slot u2 aoc10-l2 port 0 port-type ge ethernet-options port-mode e-nni
lsh> set chassis slot u2 aoc10-l2 port 1 port-type ge ethernet-options port-mode moe
lsh> commit
interfaces {
ge-u2/0 {
ethernet-options {
tm-options{
shaping-mode <auto>;//cannot be changed by user
per-cos-tm{
cos 0{
wred-mode <auto>; //cannot be changed by user
}
cos 1{
wred-mode <auto>; //cannot be changed by user
}
... <repeated for each cos value, 0 through 7>
}
}
}
monitor-utilization {
severity-profile default;
}
}
ge-u2/1 {
ethernet-options {
max-frame-size 1604;
tm-options{
shaping-mode <auto>;//cannot be changed by user
per-cos-tm{
cos 0{
wred-mode <auto>; //cannot be changed by user
}
cos 1{
wred-mode <auto>; //cannot be changed by user
}
cos 2{
wred-mode <auto>; //cannot be changed by user
}
cos 3{
wred-mode <auto>; //cannot be changed by user
}
cos 4{
wred-mode <auto>; //cannot be changed by user
}
cos 5{
wred-mode <auto>; //cannot be changed by user
}
cos 6{
wred-mode <auto>; //cannot be changed by user
}
cos 7{
wred-mode <auto>; //cannot be changed by user
}
}
}
}
monitor-utilization {
severity-profile default;
}
unit 1 {
family mpls;
}
}
}
ethernet-options {
max-frame-size 1604;
tm-options{
shaping-mode <auto>;//cannot be changed by user
per-cos-tm{
cos 0{
wred-mode <auto>; //cannot be changed by user
}
cos 1{
wred-mode <auto>; //cannot be changed by user
}
cos 2{
wred-mode <auto>; //cannot be changed by user
}
cos 3{
wred-mode <auto>; //cannot be changed by user
}
<default cos values through cos 7>
} // end per-cos-tm
} // end tm-options
monitor-utilization {
severity-profile default;
}
unit 1 {
family mpls;
}
For example, the following figure illustrates one side of a symmetrical configuration of two NEs. The first NE
has an AoC10 transponder receiving a non-colored input signal and transmitting it as an OTS signal over
channels 21 and 22 to an FOADM, which aggregates and converts the OTS signals to DWDM transmitted
out over an OCH port to an adjacent ROADM. The ROADM transmits the signal out to the second NE
through an amplifier. The second NE is configured with a mirror image of the same series of optical
modules. Each optical element participates in the ONCP protocol. Each input and output port includes an
ONCP table that stores the relevant optical parameters for that port. The NE’s RCP receives the ONCP
parameter values and processes them according to the ONCP algorithm. The RCP then sends the
appropriate commands to the active elements (in our example, the amplifier), to update their optical
parameters accordingly.
Figure 9-1: ONCP transmission along the network
Note that ONCP data can be transferred between two ports residing on the same card, or between two
ports on two adjacent cards. The two cards may be within the same platform, on different platforms within
the same node, or even at different nodes.
Parameter Description
Per Port
Pr Total port power output (dBm)
Pavg Average power per channel at port output (dBm)
ASE Indicates presence/absence of ASE noise at port output (Boolean)
Nch Total number of transmitted channels
Passive hops Number of passive cards between two active cards
Fiber span: Accexp Accumulated expected span loss from last active port (dB)
Fiber span: Accmar Accumulated span loss margin from last active port (dB)
Fiber span: Acctilt Accumulated tilt (dB)
Ptar Required power per channel at previous EDFA output (dBm)
Posc OSC output power, relevant for OA_HR only (dBm)
Per Channel j
ITU ITU channel number
Existence Indicates presence or absence of a channel (Boolean)
Hop counter Indicates the number of WSS transmitted by the channel
BR Type of this channel (text)
D Accumulated dispersion for this channel (psec/nm)
Spreading Filtering tolerance of this channel (GHz)
P Power of this channel (dBm)
Noise ASE noise in this channel’s bandwidth (dBm/0.1nm)
OSNR Optical Sound to Noise Ratio (OSNR) for this channel (dBm/0.1nm)
PMD Polarized Mode Dispersion (PMD) for this channel (psec)
PDL Polarization Dependent Loss (PDL) for this channel (dB)
AccNLT Accumulated nonlinearity for this channel (dBm)
AccDis Accumulated traveled distance for this channel (km)
ONCP data is presented first for the selected port and then for the channels within that port, arranged with
input data first, followed by output data. For example, the following command output lists the most
frequently requested subset of ONCP data values for a port carrying traffic for two channels (17, 17.5).
Output is provided for two amplifier ports, one input and one output.
+ Number of channels: 2
|-------------------------------------------------------------------------|
| ITU IfType Disper. Power OSNR PMD PDL accNLT Dist. Spread. |
|-------------------------------------------------------------------------|
|-------------------------------------------------------------------------|
+ Number of channels: 2
|-------------------------------------------------------------------------|
| ITU IfType Disper. Power OSNR PMD PDL accNLT Dist. Spread. |
|-------------------------------------------------------------------------|
|-------------------------------------------------------------------------|
The next two command examples includes the detail option, requesting a listing of
the complete set of ONCP data values for the same two ports (input and output).
root> show chassis port oncp port-u2/1 input-only detail
+ ASE: 1
+ Number of channels: 2
+ Passive hops: 1
+ Acc. margin: 1 dB
+ Acc. tilt: 0 dB
|-------------------------------------------------------------------------------
---|
| ITU RodmHop IfType Disper. Spread. Power Noise OSNR PMD PDL accNLT
Dist.|
|-------------------------------------------------------------------------------
---|
|-------------------------------------------------------------------------------
---|
+ ASE: 1
+ Number of channels: 2
+ Passive hops: 0
+ Acc. margin: 0 dB
+ Acc. tilt: 0 dB
|-------------------------------------------------------------------------------
--|
| ITU RodmHop IfType Disper. Spread. Power Noise OSNR PMD PDL accNLT Dist.|
|-------------------------------------------------------------------------------
--|
|-------------------------------------------------------------------------------
--|
NOTE: In this document the terms "protection" and "restoration" refer to two different
recovery mechanisms:
Protection switches damaged traffic from one already-set path to another already-set path.
The switch does not involve any control plane operations. This switch can happen very quickly
(sub-50 milliseconds), but requires pre-allocation of extra resources in the network, up to
twice the amount necessary.
Restoration dynamically defines an alternative path (using available shared resources) when
the original path is damaged, and tears this path down (releasing shared resources for further
use) once the original damaged path has been repaired. Restoration requires control plane
operation for the set up and tear down of the additional path and is therefore relatively slow;
on the other hand, it facilitates reuse of shared resources.
Five combinations of trail protection and restoration are available, depending on the level of service
provided:
1+0: Unprotected trail, with only a main path configured, no protection path, and no ASON
restoration.
1+1: SNCP-protected trail, with main and protection paths configured, no ASON restoration.
1+R: Trail restoration provided, with main and main-restoration paths set up as needed, offering one
level of ASON restoration.
1+1+R: One-time SNCP trail protection together with multiple path restoration, with main, protection,
and main-restoration paths configured, offering a combination of protection and dynamic restoration.
1++: Trail is protected by both SNCP and restoration mechanisms, with main, protection,
main-restoration, and protection-restoration paths configured. If the main path goes down, traffic is
switched to the protection path and the restoration-main path is prepared. If then the protection
path also goes down, traffic is switched immediately to the restoration-main path and the
restoration-protection path is prepared. In the meantime the original main and protection paths are
restored. In this manner there are always 2 paths kept available for traffic transmission. With this
level of protection, sub-50msec recovery is guaranteed, since there is always an alternative path
immediately available in case of failure.
In the event of a failure, ASON-associated entities are controlled exclusively by the ASON control plane
during the time that traffic is restored, independent of the EMS and NMS management systems (STMS and
LightSoft).
During this time the following processes occur:
Restoration: If a failure occurs on any ASON link or node that the provisioned path traverses (for
example, a fiber cut), a new trail path is automatically found by the ASON control plane (rerouting).
When the trail is interrupted, its head-end node computes the best possible restoration path using
information from the traffic-engineering database (TED) combined with explicitly-defined constraints,
such as avoiding damaged TE links and avoiding all TE links in the same SRLG. When selecting the
optimal path, ASON searches for a data link that traverses a different TE link to the one on which the
failure occurred. If a different TE link is not available, then ASON will use a data link from the same
TE-link on which the failure occurs, if available. ASON then sends signaling to the downstream nodes
hop-by-hop, requesting that they reserve resources and set up a cross connection. When the message
reaches the tail-end, the tail-end node sends a signal upstream hop-by-hop to the head-end,
confirming the success of the LSP setup for trail restoration. The ASON control plane automatically
reroutes the traffic to the new trail path, which becomes visible in the NMS.
Revertion: After the failure is repaired, revertive rerouting enables the trail to automatically revert
back to the originally provisioned trail path, after the wait to restore (WTR) time has expired. The
rerouted path is released and its bandwidth is made available for use by other services on the
network.
A trail configured in LightSoft can include both ASON and non-ASON components. At the NE level, the ASON
trail is managed through STMS or ShadeTree. STMS and ShadeTree support creation of ODUk ASON trails
over ASON Data Links (DL). OTUk ports in Apollo equipment serve as endpoints for both ASON Data Links
and the underlying TE-Links. The OTUk port attributes determine the creation, deletion, and behavior of
Data Links and TE-Links in the NE.
The ASON implementation on the current NE automatically discovers the adjacent ASON player NEs and
sets up the channels needed to communicate (using GMPLS routing protocols) with these adjacent nodes.
In addition to the default automatic discovery mechanism, ASON offers a manual discovery/verification
option in which each ASON NNI port is configured with the identity of its peer ports across ASON data links.
Each ASON port also transmits its own identity to the adjacent peer ports. Thus each ASON player can verify
that the actual port adjacencies match the automatically configured adjacencies.
This discovery mechanism, repeated across all participating ASON nodes, allows ASON to build a database
of the complete network topology, including information about the bandwidth available on each
participating ASON player. This information enables ASON to define alternate routes as needed when a trail
goes down.
3. Verify that the FIO cards are installed and the relevant ports configured. These commands are
described in Chassis, Slot, Card, and Port Identification, Port Configuration, and Interface
Configuration. Note that ASON protection is supported by the V5.1 set of FIO cards, including the
FIOMR_16B, FIO10_5B, and FIO100 cards, through NNI ports configured on these cards.
For example:
commit
4. Data links are only visible and enabled by the control plane once the physical OCH trails are created
and the necessary NNI ports defined. Type a show MPLS interface command to see a listing of the
relevant interfaces. For example:
5. ASON functionality includes autodiscovery, in which the ASON NE automatically discovers and
identifies the addresses of adjacent ASON nodes. Alternatively, network operators can manually
identify the remote nodes that will serve as peer nodes at either end of a trail, and explicitly list those
node identification addresses when configuring an ASON trail.
For example, the show mpls interface detail command described in the preceding step lists the
local interface ID, the remote interface ID, and the peer address for each interface configured on the
local NE. These are the values needed to manually identify the remote ports used for ASON trails. For
example, the preceding show MPLS interface command included the following output line:
The remote interface ID and peer address information in this command output are used to identify
the remote nodes when configuring ASON ports with manual discovery, as follows:
When working with manual discovery, the network operator must go to each ASON node in turn and
list the MPLS interfaces on that NE to identify the local interface IDs and addresses. The operator then
goes to each ASON node in turn and enters the set chassis slot commands for all links that begin
on that NE. Note that NEs with parallel card and port configurations will also have similar interface ID
settings.
6. The specific paths used for ASON-protected trails are usually selected automatically. The empty path
name parameter tells the GMPLS control plane that it is free to choose the best possible path at the
time that path is being dynamically provisioned, rather than being required to traverse a specific set
of data links.
However, the network operator is also able to identify specific paths to use or avoid. While path
definition is not included within the scope of this section, the following command line illustrates how
a path would be defined. The path name highlighted in the following example identifies that path for
later use in the ASON trail configuration command.
7. ASON trail restoration is a dynamic process that provisions the best possible trail at the time that the
trail is needed, based on priorities and metrics defined by the network operator. The network
operator defines the appropriate "cost" for each data link, and configures the system to prioritize
data link selection during trail provisioning based on minimizing the total "cost" of that trail. For
example:
a. To tell the system to prioritize link selection based on minimizing the total "link cost" enter the
following command. Note that technically this command is not necessary; link-cost is the
default setting.
b. Link costs are set at the data link level, meaning that data links based on the selected port will
be assigned the specified gmpls link-cost. To define the link-cost of a data link, enter the
following set chassis command:
This assigns a link-cost of 40 to the data link on port 0 (configured as an NNI port), located on
the FIO100 card installed in slot u16.The following code chunk lists the results of a show
chassis command after setting the link-cost.
Note that the default value for link-cost and link-length is set to 100.
8. Once you have completed the equipment configuration, the next step is to create bidirectional
co-routed trails that will enjoy ASON protection. Trails are defined between any two client ports that
have the same rate, located on cards that supports ASON functionality. Trails run from the head-end
node to the tail-end node, with trail configuration commands entered at the head-end.
For example, you can define an ASON-protected trail on two GbE ports located on FIOMR_16B cards.
All you have to do is go to the NE that will serve as the head-end for the trail, and from that endpoint
specify the trail’s client endpoints. You don’t have to supply the IP address for the head-end, since
that is the location where are you defining the trail. You do have to supply the IP address for the
trail’s far end (egress) port.
The GMPLS control plane chooses the best route for the trail, selecting the best data links (and their
associated NNI ports) based on the criteria you specified in the preceding step. You also don’t have to
configure or specify the underlying XCs to be used for this trail - the GMPLS control plane manages
the necessary XCs automatically.
You do have to specify which protection and restoration tunnels (if any) should be provisioned for this
trail. The choice of protection and restoration tunnels determines the level of protection that will be
provided for this trail, as explained previously in this section. For each tunnel, you decide whether the
GMPLS control plane should choose the best data links available at the time of provisioning (empty
flag), based on the criteria specified previously, or whether the system should be required to use a
specific path route.
The complete set trails command syntax is included later in this section. In most cases parameter
values are set automatically by the system, and do not have to be included explicitly in the typical set
trails command.
The following command lines include the most basic set of parameters used for ASON trail
provisioning. For clarity, the command has been divided into multiple command lines, to highlight
each type of tunnel being provisioned for this trail.
commit
For example:
commit
commit
9. Type show trails to see what trails were created after entering a set of trail creation commands.
Note that most of the trail parameters do not have to be set explicitly by the user. In most cases
either the default values are correct, or the system detects the appropriate setting and configures it
accordingly. For example:
Trail_201_16 {
nms-trail-id 558;
trail-id 0.20.8f.60.0.38v95;
trail-rate odu1;
payload-type unknown;
directionality bidirectional;
egress-ne-id 172.30.130.21;
ingress-endpoint odu1-u4/12:1;
egress-endpoint odu1-u4/12:1;
fully-disjoint-protection disabled;
severity-profile default;
restoration-recovery {
recovery-type 1-plus-r;
automatic-reversion enabled;
wtr-period 5;
hold-off-time 0.0;
}
tunnels main {
lsp {
provisioned-path-name Trail_201_16_M;
actual-path-name Trail_201_16-0.20.8f.60.0.38v95-main;
lockout disabled;
}
}
tunnels restoration_main {
lsp {
provisioned-path-name empty;
lockout disabled;
}
}
}
10. The GMPLS control plane automatically creates the underlying XCs for these trails. Type show
cross-connects to see a listing of the relevant XCs. In the following examples, the trail numbers that
correspond to the preceding trail list are highlighted.
[edit]
root@AsonNE1xx# show cross-connects
Trail_201_16-0.20.8f.60.0.38v95 {
leg 1 {
from-tp odu1-u4/12:1;
to-tp odu1-u6/0:1:TPN1;
directionality bidirectional;
}
trail-id 558;
connection-mode configurable;
}
trail-id 2.2.e.ff.c1.1v661;
trail-rate odu2;
payload-type unknown;
directionality bidirectional;
egress-ne-id 90.90.90.201;
ingress-endpoint odu2-u13/3:1;
egress-endpoint odu2-u13/3:1;
fully-disjoint-protection disabled;
severity-profile default;
restoration-recovery {
recovery-type 1-plus-1-plus-r;
automatic-reversion enabled;
wtr-period 1;
hold-off-time 0.0;
}
tunnels main {
lsp {
provisioned-path-name empty;
lockout disabled;
}
}
tunnels protection {
lsp {
provisioned-path-name empty;
lockout disabled;
}
}
tunnels restoration_main {
lsp {
provisioned-path-name empty;
lockout disabled;
}
}
commit
commit
If the command is entered with the detail parameter, a more detailed summary of the MPLS
interface status is printed. For example:
run show mpls interface detail
If the command is entered with a specific MPLS interface name, a data listing is provided for
that interface only. If no name is provided, the system responds with a data listing for all MPLS
interfaces. For example:
2. The system will print out a list of GMPLS attributes for that port. For example:
remote-ne-id: 1.2.3.4
srlgs: srlg1,srlg2
metric: 20
operational state: up
admin state: up
agreed-tributary-slot-type: 1.25G
consistency-status consistent
configured-remote-port-id otu2-u5/3
tributary-slot-type 1.25G
supported-odu-types odu1,odu2
te-link-id 334
2. The system will print out the bandwidth available for each type of interface supported by that link.
For example:
commit
commit
commit
commit
commit
######## Configuring one link, using 100G NNI port configuration ###########
set chassis slot u16 fio100 port 0 port-type otu4 otu-options gmpls-options nni
remote-node 172.30.130.129 remote-mpls-if-index 2038759936
commit
######### Configuring four links, using 10G NNI port configuration ########
set chassis slot u5 fio10-5b port 0 port-type otu2 otu-options gmpls-options nni
set chassis slot u5 fio10-5b port 1 port-type otu2 otu-options gmpls-options nni
set chassis slot u5 fio10-5b port 2 port-type otu2 otu-options gmpls-options nni
set chassis slot u5 fio10-5b port 3 port-type otu2 otu-options gmpls-options nni
commit
### MPLS Path configuration - enables subsequent path specification by name ###
### This path configuration command includes remote interface identification ###
### information, found in the show mpls interface detail command ###
### Note that the path names configured here can be used in later trail ###
commit
1+0:
----
commit
1+1:
-----
commit
1+R:
-----
commit
1+1+R:
------
commit
1++:
-----
commit
Example
Equipment protection group configuration is performed automatically.
CAUTION: Modifying the main and protecting ports role without first deleting the protection
group may cause a traffic hit.
Table 11-1: Parameters automatically copied to the protecting port - per service type
FC port
All port STM/OC ETY100G ETY10GO ETY1G
OTU port ETY10G port and
types port port C port port
CBR ports
ALS state TIM FEC mode CSF/TSF TSFtoLOL TSFtoLOL CSF/TSF CSF/TSF
(enable/ monitor action action action
disable) type type / type
TSFtoLOL
Expected Expected TIM monitor Maximum Maximum GFP UPI GFP GFP
wavelength TTI frame size frame size values header header
(gfp- conseque conseque
compatibility- nt actions nt Actions
mode)
Port Expected TTI LF/RF mode Maximum
behavior (SAPI/DAPI) frame size
Severity DEG GFP header
profile consequent
(alarm actions
event
profile)
PM profile FEC_Ignore CSF_Ordered-
set_mode
Alarm mask GCC_Mode Maximum
master frame size
PM monitor GCC_Terminati
on
Admin TIM
status consequent
actions
Tx rnable Rx wavelength
Sent TTI
(SAPI/DAPI)
Sent TTI
operator string
ConfigChromDi
sp
LastKnown
ChromDisp
Example
The following example shows a port protection group, and an equipment protection group.
Examples:
user@root> show protection equipment
PG:fm1t Active Source(s): slot-u8, slot-u9, slot-u10 Alarm Status: clear
user@root> show protection port
PG:port-u0/0 Active Source(s): port-u0/0 Alarm Status: clear
Table 11-2: Triggers for port switch over events and their relative priorities
Example:
wtr-period 5;
is-revertive false;
severity-profile default;
}
NOTE: In the case of port protection, changing the main unit is not traffic affecting. However,
in some circumstances it may cause a protection switch event (traffic affecting <50msec). In
the case of traffic protection, changing the main unit is traffic affecting.
Example:
NOTE: Maintenance commands are executed according to priority level. When performing
maintenance commands via ShadeTree, enter the command and commit the change
separately for each action, to ensure the commands hierarchy is maintained.
NOTE: Lockout can only be applied to a single unit in a protection group at any given time.
Lockout is persistent and has the highest priority of any FM switch over criteria.
When viewing the details of the protection group, the relevant unit is listed as locked out:
NOTE: The manual switch command can be overridden by an error or command of higher
priority.
Resetting a module:
If a module is reset within an equipment protection group, the other three modules are automatically
switched to active.
To reset a module:
At the root level, type the following
user@root# reset <modulename>
Example
Parameter Description
Status The status of the fabric module (active/standby):
Condition The condition of the fabric module:
<none>: module is working.
Failing: there is currently an error on the module, and it is not working.
Failed: the module is working, but there was a problem on the module
in the past.
Alarm Status The status of the most severe alarm on the module.
Description The description of the module type.
The status and condition of the fabric modules is displayed, including the alarm with the highest severity, if
applicable. The status displays the module status for the FM modules only. The details of any known
failures are organized per module, as shown in the following examples.
Example A
Example of a detailed FM fabric status showing four working fabric cards.
Example B
Example of a detailed FM fabric status showing a combined card failure of pxfa1 and link failure
between pxfb2 and np13.
WARNING: ECI Telecom recommends that you do not remove a card, power down the
platform, or restart ShadeTree while an upgrade is in progress. Instead, wait until you are
certain that the upgrade has completed.
NOTE: This section is applicable to a chassis with either a single or dual RCP installed. If two
RCP cards are present on the NE, ensure they are synchronized before performing the
upgrade. To check the RCP status, use the show chassis command.
Before you install new RCS software, ECI recommends that you back up your current
configuration. For more information about backing up the system, see the System Overview
and Configuration User Guide.
You can perform a software upgrade on a single OPT96xx NE or multiple NEs simultaneously. Upgrading the
software involves the following steps:
1. Verify that SSH access has been enabled before running any installation or upgrade commands. If
necessary, run the following two commands:
Type set system services ssh root-login allow
Type set system services ssh enable-network
2. Run the software pre-installation test command on each NE in which you want to install the system
upgrade. The test script checks that the NE meets the installation requirements.
3. Run the installation command, which completes the following stages:
a. Download the upgrade software package to the machine that you want to upgrade.
b. Install the new software package.
4. Run the software pre-upgrade test command on each NE in which you want to upgrade the system.
The test script checks that the NE meets the upgrade requirements.
5. Run the upgrade command, which activates the new software. If you wish to schedule the upgrade
for a later date, use the relevant command. The upgrade is performed automatically in a single step
that does not require user intervention.
During the software upgrade, first the RCP cards are upgraded, then the OPB module(s) and FM cards are
upgraded. Traffic is not affected unless a specific component is traffic affecting.
Where RCP protection exists, the software is stored on both active and standby RCP cards. In the event that
an RCP card is added to an NE running a different software version, it is possible to upgrade only the
standby card.
ECI Telecom
SR9624 High Capacity
apollo
Branch: main-apollo-candidate
Active RCP Version:
Bundle: /var/home/software/opt96_V_CL.tar
Bundle: /var/staging/bundle/curr/opt96_V_CL.tar
Bundle: /var/staging/bundle/prev/opt96_V_CL.tar
End of bundles
File: /var/home/software/opt96_V_CL.tar
In progress: 0
Size: 6
Version: Model: -- / ST: -- / MOS: -- / UBoot: --
MD5: 0x8FEB211FEF744A43469CF07400094C70
WARNING: Downgrading the system software erases the configuration settings completely.
The whole system configuration must be redefined. Therefore, before completing this
command, save a backup of the system configuration settings to use with the new
downgraded version.
Extracting...
Staging...
Preparing... ############################################# [100%]
1:libpthread ############################# [ 12%]
2:libstdc++ ############################# [ 25%]
3:omniorb ############################# [ 37%]
4:st ############################# [ 50%]
5:st-domestic############################# [ 62%]
6:st-pkg ############################# [ 75%]
7:st- ################################ [ 87%]
Staged successfully.
WARNING: restart required for staged software to be installed and take effect
Software add succeeded
WARNING: Rolling back to a previous software version also restores the previous
configuration status and settings. Any new configuration that was performed with the newer
software is not saved.