STMS V8.2 User Guide-đã chuyển đổi

STMS
Version 8.2
User Guide
STMS User Guide
V8.2
Catalog No: X92373
Drawing No: 497006-2412-083-A00
August 2017
Rev01
ECI's NPT-1800, NPT-1200, NPT-1050, NPT-1021, and NPT-1010 are CE2.0 certified.
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.
ECI's management applications run on VMWare virtualization hypervisors.
© Copyright by ECI, 2012-2017. All rights reserved worldwide.

This is a legal agreement between you, the end user, and ECI Ltd. (“ECI”). BY OPENING THE DOCUMENTATION AND/OR DISK PACKAGE,
YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY
RETURN THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND
BINDERS OR OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU OBTAINED THEM.
All documentation and/or disk and all information and/or data contained in the documentation and/or disk ["ECI's Proprietary"] is ECI's proprietary
and is subject to all copyright, patent, and other laws protecting intellectual property, and any international treaty provisions, as well as any specific
agreement protecting ECI's rights in the aforesaid information. Any use of ECI's Proprietary for any purposes [included but not limited: published,
reproduced, or disclosed to third parties, in whole or in part] other than those for which it was disclosed, without the express prior written
permission of ECI, is strictly forbidden.
ECI's Proprietary is provided "AS IS" and may contain flaws, omissions, or typesetting errors. No responsibility and or liability whatsoever are
assumed by ECI for you or any other party, for the use thereof, nor for the rights of third parties, nor for any loss or damage whatsoever or
howsoever caused, arising directly or indirectly in connection with ECI's Proprietary, which may be affected in any way by the use and/or
dissemination thereof. ECI reserves the right, without prior notice or liability, to make changes in equipment design or specifications including any
change in and to the ECI's Proprietary.
Any representation(s) in ECI's Proprietary concerning performance of ECI's product(s) are for informational purposes only and are not warranties of
product performance or otherwise, either express or implied. No warranty is granted nor liability assumed in relation thereto, unless specifically
undertaken in ECI's sales contract or order confirmation. ECI's Proprietary is periodically updated, and changes will be incorporated in subsequent
editions. All graphics included in this document are for illustrative purposes only and might not correspond with your specific product version.
The documentation and/or disk and all information contained therein is owned by ECI and is protected by all relevant copyright, patent, and other
applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation and disk as any
other copyrighted material (for example, a book or musical recording).
Other Restrictions. You may not rent, lease, sell, or otherwise dispose of ECI's Proprietary, as applicable.
YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY
PROVIDED IN THIS LICENSE. ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI.
All trademarks mentioned herein are the property of their respective holders.
Notwithstanding the generality of the aforementioned, you expressly waive any claim and/or demand regarding liability for indirect, special,
incidental, or consequential loss or damage which may arise in respect of ECI's Proprietary contained therein, howsoever caused, even if advised of
the possibility of such damages.
The end user hereby undertakes and acknowledges that they read the "Before You Start/Safety Guidelines" instructions (when provided by ECI) and
that such instructions were understood by them. ECI shall not be liable to you or to any other party for any loss or damage whatsoever or
howsoever caused, arising directly or indirectly in connection with you fulfilling and/or failure to fulfill in whole or in part the "Before You
Start/Safety Guidelines" instructions.
Contents
Useful information.................................................................................................xii
Related documents.............................................................................................................................xii
Contact information............................................................................................................................xii
Revision history...................................................................................................................................xii
1 Network setup..............................................................................................1-1
1.1 Group configuration..............................................................................................................1-1
1.1.1 Create a group..........................................................................................................................1-1
1.1.2 Move a group............................................................................................................................1-2
1.1.3 Delete a Group..........................................................................................................................1-2
1.2 NE discovery..........................................................................................................................1-2
1.2.1 NE discovery via the STMS client..............................................................................................1-3
1.2.2 NE discovery via the STMS discovery utility.............................................................................1-5
1.2.3 Define the NE ID.....................................................................................................................1-10
1.3 Define STMS server data.....................................................................................................1-10
1.4 View STMS Domain properties............................................................................................1-11
1.5 View SNMP settings............................................................................................................1-12
1.6 Define the NE configuration files directory.........................................................................1-13
1.7 Define STMS performance parameters...............................................................................1-13
1.8 Maintain historical alarms...................................................................................................1-14
2 NE management...........................................................................................2-1
2.1 NE implicit configuration.......................................................................................................2-1
2.1.1 Equipment implicit configuration.............................................................................................2-1
2.1.2 Controller cards implicit configuration.....................................................................................2-2
2.1.3 Severity profiles implicit configuration....................................................................................2-2
2.1.4 PM threshold profiles implicit configuration...........................................................................2-2
2.1.5 Cross connection implicit configuration...................................................................................2-2
2.1.6 Protection group implicit configuration...................................................................................2-3
2.1.7 Transport entities implicit configuration..................................................................................2-3
2.2 Configure an NE using Plug and Play.....................................................................................2-3
2.3 View NE properties................................................................................................................2-7
2.4 View NE operational status.................................................................................................2-10
2.5 Connect to an NE using Telnet............................................................................................2-11
ECI Telecom Ltd. Proprietary iii

2.6 Connect to an NE using SSH................................................................................................2-11
2.7 Check network connectivity................................................................................................2-12

2.8 Delete an NE........................................................................................................................2-12
2.9 Move an NE.........................................................................................................................2-12
2.10 Halt an NE...........................................................................................................................2-13
2.11 Restart an NE.......................................................................................................................2-13
2.12 Reboot an NE......................................................................................................................2-13
2.13 Flash LEDs on an NE............................................................................................................2-14
2.14 Refresh an NE......................................................................................................................2-14
2.15 Refresh alarm information..................................................................................................2-14
2.16 Unmanage an NE.................................................................................................................2-15
2.17 Reconnect an NE.................................................................................................................2-15
2.18 Define logging for an NE......................................................................................................2-16
2.19 View NE temperature statistics...........................................................................................2-17
2.20 Viewing NE power control areas.........................................................................................2-18
2.21 View NE capacity data.........................................................................................................2-19
2.22 Define LCT access to an NE..................................................................................................2-21
2.23 NTP configuration...............................................................................................................2-22
2.23.1 Configure NTP on an NE.........................................................................................................2-23
2.23.2 Add an NTP bootstrap server.................................................................................................2-24
2.23.3 Remove an NTP bootstrap server...........................................................................................2-24
2.23.4 Add an NTP authentication key..............................................................................................2-24
2.23.5 Remove an NTP authentication key.......................................................................................2-25
2.23.6 Define NTP symmetric mode..................................................................................................2-25
2.23.7 Remove an NTP peer..............................................................................................................2-25
2.23.8 Define NTP client mode..........................................................................................................2-26
2.23.9 Remove an NTP server...........................................................................................................2-26
2.23.10 Define NTP broadcast mode...................................................................................................2-26
2.23.11 Define NTP broadcast client mode.........................................................................................2-27
2.23.12 Set the device date and time..................................................................................................2-27
2.23.13 Remove the NTP configuration from an NE...........................................................................2-28
2.23.14 View NTP properties...............................................................................................................2-28
2.24 Security certificate management........................................................................................2-29
2.24.1 Create a new STMS Certificate...............................................................................................2-30
2.24.2 Update new STMS public key for all NEs................................................................................2-31
2.24.3 Manually activate a new STMS certificate.............................................................................2-31
ECI Telecom Ltd. Proprietary iv

2.24.4 Load an NE public key to the STMS server.............................................................................2-32
2.24.5 Create a new NE certificate....................................................................................................2-33

2.24.6 Manually activate a new NE certificate..................................................................................2-33
2.24.7 View the Peer IPs table...........................................................................................................2-33
2.25 Commissioning tool.............................................................................................................2-34
2.25.1 Access the Commissioning tool..............................................................................................2-35
2.25.2 Select NEs for commissioning.................................................................................................2-35
2.25.3 Routing protocol configuration (commissioning)...................................................................2-36
2.25.4 General router settings (commissioning)...............................................................................2-38
2.26 NE Credentials tool..............................................................................................................2-38
2.26.1 Access the NE Credentials tool...............................................................................................2-39
2.26.2 Create an NE profile................................................................................................................2-39
2.26.3 Edit an NE profile....................................................................................................................2-39
2.26.4 Delete an NE profile................................................................................................................2-40
2.26.5 Map an NE profile...................................................................................................................2-40
2.26.6 Apply the NE profile mapping................................................................................................2-40
2.26.7 Remove an NE profile mapping..............................................................................................2-41
2.26.8 Send bootstrap configuration to 9200 devices......................................................................2-42
2.27 NE configuration backup and restore..................................................................................2-42
2.27.1 Define the backup file directory.............................................................................................2-42
2.27.2 Perform an immediate network configuration backup..........................................................2-43
2.27.3 Schedule a network configuration backup.............................................................................2-44
2.27.4 View all network configuration backups................................................................................2-45
2.27.5 View a network configuration backup...................................................................................2-45
2.27.6 View the network configuration backup log..........................................................................2-45
2.27.7 Suspend a scheduled network configuration backup............................................................2-45
2.27.8 Resume a scheduled network configuration backup.............................................................2-46
2.27.9 Monitor the network configuration backups.........................................................................2-46
2.27.10 Edit a network configuration backup.....................................................................................2-46
2.27.11 Delete a network configuration backup schedule.................................................................2-47
2.27.12 Sort the network configuration backups................................................................................2-47
2.27.13 Verify a network configuration backup..................................................................................2-47
2.27.14 Delete a network configuration backup.................................................................................2-48
2.27.15 Compare network configuration backups..............................................................................2-48
2.27.16 Save a network configuration backup to a file.......................................................................2-48
2.27.17 Restore an NE configuration backup......................................................................................2-49
2.27.18 Restore a selected configuration............................................................................................2-49
ECI Telecom Ltd. Proprietary v

2.28 NE event logs.......................................................................................................................2-50
2.28.1 View NE event logs.................................................................................................................2-50

2.28.2 Filter the NE event logs list.....................................................................................................2-51
2.28.3 Define the number of logs per page.......................................................................................2-51
2.28.4 Purge NE event logs................................................................................................................2-52
2.28.5 Export NE event logs to an XML file.......................................................................................2-52
2.29 ASON/WSON configuration.................................................................................................2-53
2.29.1 View ASON/WSON Control Plane attributes..........................................................................2-53
2.29.2 View ASON/WSON Control Plane protocol attributes...........................................................2-54
2.29.3 View ASON/WSON port parameters......................................................................................2-56
2.29.4 View the ASON/WSON Trails list............................................................................................2-57
2.29.5 View the GMPLS Control Channels list...................................................................................2-59
2.29.6 View XC resource ownership..................................................................................................2-60
2.29.7 Define auto-discovered ASON data links................................................................................2-61
2.30 Synchronize the standby RCP configuration........................................................................2-62
2.31 Define utilization thresholds...............................................................................................2-62
2.32 Configure a subtending shelf...............................................................................................2-63
2.33 View the Maintenance List..................................................................................................2-63
3 Cards and modules.......................................................................................3-1

3.1 OPT99xx cards and modules.................................................................................................3-1
3.1.1 HIO10_20..................................................................................................................................3-1
3.1.2 HIO100_2..................................................................................................................................3-2
3.1.3 TIOMR_32.................................................................................................................................3-3
3.1.4 OPT99xx common cards and modules.....................................................................................3-4
3.2 OPT9904X cards and modules...............................................................................................3-5
3.2.1 MIO200.....................................................................................................................................3-5
3.2.2 OPT99xx common cards and modules.....................................................................................3-6
3.2.3 Supported passive and photonic cards....................................................................................3-7
3.3 OPT96xx layer 1 service cards...............................................................................................3-7
3.3.1 TR10_4......................................................................................................................................3-8
3.3.2 TR10_4EN.................................................................................................................................3-8
3.3.3 TR10_12....................................................................................................................................3-9
3.3.4 TR10_12ULL............................................................................................................................3-10
3.3.5 TR100/TR100L.........................................................................................................................3-10
3.3.6 TM100.....................................................................................................................................3-11
3.3.7 TM200EN................................................................................................................................3-12
ECI Telecom Ltd. Proprietary vi

3.3.8 TM100_2EN............................................................................................................................3-13
3.3.9 TM400.....................................................................................................................................3-14
3.3.10 AoC10/AoC10B.......................................................................................................................3-15
3.3.11 AoC25/AoC25B.......................................................................................................................3-16
3.3.12 CMR40B..................................................................................................................................3-17
3.3.13 CMR100/CMR100L.................................................................................................................3-18
3.3.14 CMR100M...............................................................................................................................3-19
3.4 OPT96xx layer 1 fabric interface cards................................................................................3-20
3.4.1 FIO10_5/FIO10_5B.................................................................................................................3-20
3.4.2 FIOMR_16/FIOMR_16B..........................................................................................................3-21
3.4.3 FIO100.....................................................................................................................................3-22
3.4.4 FIO100M.................................................................................................................................3-22
3.5 OPT96xx layer 2 cards.........................................................................................................3-23
3.5.1 AoC10_L2................................................................................................................................3-23
3.5.2 AoC10_L2 port configuration.................................................................................................3-23
3.5.3 AoC10_L2 switch configuration..............................................................................................3-30
3.6 Optical components............................................................................................................3-48
3.6.1 Multidegree ROADM cards.....................................................................................................3-48
3.6.2 Mux/DeMux cards..................................................................................................................3-50
3.6.3 OADM cards............................................................................................................................3-52
3.6.4 Optical filters, splitters, and couplers.....................................................................................3-53
3.6.5 Optical amplifiers....................................................................................................................3-55
3.6.6 OTDR.......................................................................................................................................3-58
3.6.7 OTDR_8...................................................................................................................................3-58
3.6.8 DCF..........................................................................................................................................3-59
3.6.9 OMSP......................................................................................................................................3-60
3.6.10 OLP_S2....................................................................................................................................3-60
3.7 Pluggable transceiver modules...........................................................................................3-60
3.8 Assign cards.........................................................................................................................3-61
3.9 Replace cards......................................................................................................................3-62
3.10 Unassign a card...................................................................................................................3-63
3.11 View the card description...................................................................................................3-63
3.12 View card properties...........................................................................................................3-63
3.12.1 Optical card properties...........................................................................................................3-63
3.12.2 xRCP/RCP card properties......................................................................................................3-64
3.12.3 CTM card properties...............................................................................................................3-65

i
3.13 View card performance statistics........................................................................................3-65
4 Ports and interfaces......................................................................................4-1

4.1 Supported ports and interfaces.............................................................................................4-1
4.2 Terminology..........................................................................................................................4-2
4.3 Supported interfaces.............................................................................................................4-3
4.3.1 OTN interfaces..........................................................................................................................4-3
4.3.2 FC interfaces.............................................................................................................................4-4
4.3.3 Video interfaces........................................................................................................................4-4
4.3.4 Management interfaces...........................................................................................................4-4
4.3.5 Physical Optical interfaces........................................................................................................4-4
4.3.6 SDH interfaces..........................................................................................................................4-4
4.3.7 SONET interfaces......................................................................................................................4-5
4.3.8 Channelized interfaces.............................................................................................................4-6
4.3.9 Concatenated interfaces..........................................................................................................4-7
4.3.10 1 GbE/10 GbE interfaces...........................................................................................................4-7
4.3.11 10/100/1000Mbps Ethernet interfaces....................................................................................4-7
4.3.12 Logical interfaces......................................................................................................................4-8
4.4 Interface name......................................................................................................................4-8
4.5 Logical interface numbering..................................................................................................4-9
4.6 Router ID and primary address.............................................................................................4-9
4.7 Primary interface.................................................................................................................4-10
4.8 IP addresses and interfaces.................................................................................................4-10
4.9 View port properties...........................................................................................................4-10
4.10 Enable or disable a port......................................................................................................4-11
4.11 Configure ports...................................................................................................................4-11
4.11.1 Configure TM200EN/TM100_2EN card ports........................................................................4-13
4.12 Loopback interfaces............................................................................................................4-14
4.12.1 Enable/disable a loopback interface (lo0)..............................................................................4-15
4.12.2 Create a logical loopback interface........................................................................................4-15
4.12.3 Enable/disable a logical loopback interface...........................................................................4-15
4.12.4 Enter a description for a logical loopback interface...............................................................4-16
4.12.5 Delete a logical loopback interface........................................................................................4-16
4.12.6 View the interfaces in a Loopback Interface folder...............................................................4-17
4.12.7 View logical loopback interface properties............................................................................4-18
4.13 Define TR10_4EN encryption settings.................................................................................4-20
4.14 Define TM200EN/TM100_2EN encryption settings.............................................................4-21

ii
4.15 OTDR management.............................................................................................................4-21
4.15.1 Start OTDR Calibration............................................................................................................4-22

4.15.2 Start OTDR Test......................................................................................................................4-23
4.16 Run OTDR_8 tests...............................................................................................................4-24
4.17 Upload SOR files from an NE...............................................................................................4-25
4.18 View ONCP data..................................................................................................................4-26
4.19 Configure LOS threshold.....................................................................................................4-27
4.20 Define performance margin threshold................................................................................4-27
4.21 View configured VPPs..........................................................................................................4-28
4.22 Port maintenance................................................................................................................4-28
4.22.1 Run an Optical Loopback command.......................................................................................4-29
4.22.2 Run a Send BDI command......................................................................................................4-29
4.22.3 Run a Send CSF command......................................................................................................4-30
4.22.4 Set Test mode.........................................................................................................................4-30
4.22.5 Run a Delay Measurement operation....................................................................................4-30
5 L1-XCs...........................................................................................................5-1
5.1 L1-XC compatibility guidelines..............................................................................................5-1
5.2 L1-XC modes..........................................................................................................................5-2
5.3 L1-XC leg directionality..........................................................................................................5-3
5.4 ODU-XC fabric support..........................................................................................................5-3
5.5 L1-XC protection....................................................................................................................5-4
5.5.1 Unprotected configurations.....................................................................................................5-5
5.5.2 Protected configurations..........................................................................................................5-5
5.5.3 Define Y-Protection..................................................................................................................5-7
5.6 Managing L1-XCs...................................................................................................................5-8
5.6.1 View L1-XCs...............................................................................................................................5-8
5.6.2 Create L1-XCs............................................................................................................................5-9
5.6.3 Modify an L1-XC......................................................................................................................5-12
5.6.4 Deletion of L1-XCs...................................................................................................................5-14
5.7 L1-XC connection tables......................................................................................................5-15
6 Packet configuration.....................................................................................6-1
6.1 Configure L2 port parameters...............................................................................................6-2
6.2 Configure Link OAM..............................................................................................................6-3
6.3 View Link OAM events and statistics.....................................................................................6-4
ECI Telecom Ltd. Proprietary ix

6.4 Configure Link OAM thresholds............................................................................................6-4
6.5 Switch configuration.............................................................................................................6-5
6.5.1 Configure switch properties.....................................................................................................6-6

6.5.2 Configure a VLAN ID Range profile...........................................................................................6-7
6.5.3 Configure a Port TPID profile....................................................................................................6-7
6.5.4 Configure a CoS Group Profile..................................................................................................6-9
6.5.5 Configure a QoS profile..........................................................................................................6-10
6.5.6 Configure a Policer profile......................................................................................................6-17
6.5.7 Configure a WRED profile.......................................................................................................6-18
6.5.8 Configure a Slow Path Policer profile.....................................................................................6-19
6.5.9 Configure a LAG......................................................................................................................6-21
6.5.10 Configure Slow Path...............................................................................................................6-23
6.5.11 View configured VSIs..............................................................................................................6-25
6.5.12 View VSI properties................................................................................................................6-25
6.5.13 View VSI statistics...................................................................................................................6-26
7 Protection.....................................................................................................7-1
7.1 Equipment protection...........................................................................................................7-1
7.1.1 FM protection...........................................................................................................................7-1
7.1.2 Fast IOP protection...................................................................................................................7-2
7.2 Port protection......................................................................................................................7-4
7.2.1 Port association guidelines.......................................................................................................7-5
7.2.2 IOP protection for L1 ports.......................................................................................................7-6
7.2.3 IOP protection for physical packet ports..................................................................................7-9
7.3 Traffic protection.................................................................................................................7-13
7.3.1 Modify a traffic protection group of L1-XCs (OPT99xx).........................................................7-13
7.3.2 Modify a traffic protection group of L1-XCs (OPT96xx).........................................................7-15
7.4 Protection maintenance......................................................................................................7-16
7.4.1 Perform protection maintenance...........................................................................................7-18
7.5 View protection alarms.......................................................................................................7-18
7.6 FM fabric status...................................................................................................................7-19
8 Fiber connectivity.........................................................................................8-1
8.1 Fiber connectivity prerequisites and guidelines....................................................................8-2
8.2 Define fiber connectivity.......................................................................................................8-2
8.3 Define fiber connectivity for non-Shadetree equipment......................................................8-4
8.4 View fiber connectivity for an NE..........................................................................................8-5
ECI Telecom Ltd. Proprietary x

8.5 Fiber/port connectivity rules.................................................................................................8-6
9 Customer management................................................................................9-1
9.1 Create a customer.................................................................................................................9-1
9.2 Modify customer information...............................................................................................9-2
9.3 Customer import and export.................................................................................................9-2
9.3.1 Import customer information...................................................................................................9-2
9.3.2 Export customer information...................................................................................................9-2
9.4 Customer reports..................................................................................................................9-3
9.4.1 Generate a Customer Report...................................................................................................9-3
9.4.2 Generate an Interface Utilization Report.................................................................................9-4
9.5 Delete a customer.................................................................................................................9-4
9.6 View customer information..................................................................................................9-5
ECI Telecom Ltd. Proprietary xi

Useful information
This document describes how to configure and manage network elements (NEs) in your network using the
ShadeTree® Management System (STMS).
This document is intended for network administrators and technical personnel responsible for configuring
and managing NEs.
Related documents
 STMS What's New Guide
 STMS Getting Started and Administration Guide
 STMS Performance Management Guide
 LCT-STMS Getting Started and Administration Guide
 Apollo Reference Manual
Contact information
Telephone Email
ECI Documentation Group +972-3-9268145 techdoc.feedback@ecitele.com
ECI Customer Support +972-3-9266000 on.support@ecitele.com
Revision history
Revision Section Description
1 N/A New
ECI Telecom Ltd. Proprietary xii

1 Network setup
The Network Explorer provides a hierarchical view of the network. The root domain, called the STMS
Domain, is created during STMS installation. If your network has a small number of NEs, this one domain
may be sufficient. However, it is recommended that you set up groups (or subdomains) for your NEs under
the STMS Domain. See Group configuration.
You can then perform NE discovery using either the STMS client or the STMS discovery utility. See NE
discovery.
1.1 Group configuration

Groups enable you to organize NEs logically, according to a common attribute such as geographical
location. This type of hierarchical structure provides a logical organized view of the network.
Figure 1-1: Network hierarchy
The above illustration shows an example of a network hierarchical structure. Three groups - East, Midwest,
and West - appear below the root STMS Domain. These groups represent geographical regions of the U.S.
Two subgroups - New York and Pittsburgh - appear below the East group. These subgroups represent cities
in the East.
1.1.1 Create a group

Groups are a convenient tool for organizing your network. You can create as many groups and subgroups as
are necessary to accurately depict your network. The groups that you create are added below the root
STMS Domain; subgroups are added below their respective groups.
To create a group:
1. In the Network Explorer tab, do one of the following:
 To create a group, right-click STMS Domain and click Create Group.
 To create a subgroup, right-click the relevant group and click Create Group.
The Create Group window opens.
2. Type the name of the group.
The name must be unique and contain 1 to 30 alphanumeric characters in length, including spaces
and special characters (e.g., * . - _ $).
ECI Telecom Ltd. Proprietary 1-1

STMS User Guide Network setup
3. Click OK.
The group is created.
1.1.2 Move a group

You can move a group or subgroup within your network:
 from the STMS Domain to another group or subgroup, or vice versa
 from group to group
 from subgroup to subgroup
To move a group:
 In the Network Explorer tab, drag the group or subgroup to the relevant location in the tree.
The group/subgroup is moved.
1.1.3 Delete a Group

You can delete groups or subgroups as required. Groups that contain subgroups or NEs cannot be deleted.
You must first delete the relevant subgroups and NEs (see Deleting an NE).
To delete a group:
 In the Network Explorer tab, right-click the group or subgroup you want to delete, and click Delete.
The group/subgroup is deleted.
1.2 NE discovery
Instead of configuring STMS server information on NEs, you can use the STMS to discover them. You can
discover NEs using either the STMS client or the STMS discovery utility. See:
 NE discovery via the STMS client
 NE discovery via the STMS discovery utility
NOTE: The number of NEs that can be managed by an STMS is on a cost basis. Verify that the
purchased license is current and has not exceeded its token limits. (For more information, see
Manage licenses in the Getting Started and Administration Guide.)

1.2.1 NE discovery via the STMS client
You can discover NEs using the STMS client.
1.2.1.1 Verify STMS server data

To verify STMS server data on an NE:
1. Log in to the NE using the CLI.
2. At the prompt, type show system stms-servers and press ENTER.
The system displays output similar to the following:
root@netmgmt2> show system stms-servers
LPS IP addr LPS Port Enabled Status
10.0.4.130 6336 true CONTACTING

10.0.4.151 6336 true CONTACTING
10.0.4.227 6336 true CONTACTED
172.23.0.112 6336 true SUBSCRIBED
1.2.1.2 Discover NEs

Using the STMS Client, you can discover NEs within the STMS Domain or within groups and subgroups. You
can discover an NE for a single IP address or you can specify a range to discover all NEs with IP addresses in
that range.
NOTE: During NE discovery, the STMS needs to identify the public key of each discovered NE
in order to communicate with it. If an NE's public key is different from the Default value, the
STMS must also know its Current value. In this case, you must copy the NE's public key file to a
predefined folder on the STMS server before performing NE discovery.
The filename format of the public key file must be: <NE IP address>_PublicKey.pem
where underscores appear instead of periods in the IP address.
For example: 153_34_77_201_PublicKey.pem
To discover NEs:
1. In the Network Explorer tab, right-click STMS Domain or a group/subgroup and click Discover
Network Element.
The Discover Network Element window opens.
2. In the Name/IP Address field, type the host name or IP address of the management interface for the
NE, or type in a range of IP addresses (any IP address range followed by a netmask). Ranges may be
specified as "a-b" where "a" represents the start of the range and "b" represents the end of the
range. The netmask is an integer from 1 to 32.
For example, 10.0.232.20-24/27 specifies a range of IP addresses that includes 10.0.232.20,
10.0.232.21, 10.0.232.22, 10.0.232.23, and 10.0.232.24.
When discovering a range of IP addresses, the STMS should not have a new key during the process.
3. From the Type dropdown list, select the type of product series for the NE you wish to discover.
4. Click OK.
5. Repeat this procedure for each NE you want to discover.
NOTE: The progress during discovery is displayed beside the NE icon in the Network Explorer
tab, as shown:
1.2.1.3 Discover NEs using an IP range from file

To discover NEs using an IP address list specified in a file:
1. In the Network Explorer tab, right-click STMS Domain (to discover NEs within the STMS Domain) or
the group for which you want to discover the NEs, and click Discover IP Range From File. The Open
window opens.
2. Select the directory and file name of the file which contains the IP address list.
3. Click Open.
File Syntax
Each line of the file has this syntax:
[typeName]:(ip address|ip address range):[groupName].
 typeName - an optional typeName. If not specified, the type defaults to the SR9700.
 ip address - any valid IP address with or without netmask.
 ip address range - any IP address range with a netmask. Range may be specified in any hostpart of ip
address. An IP address can be in the form x.x.x.x and a range is specified in any host part octet as "a-
b", where "a" represents the start of the range and "b" represents the end of the range inclusive, for
example, 192.168.1.2-100/24. The network part of the address must be specified by a valid netmask -
the ip address followed by a /XX, where XX is any number from 1 to 32 for ipv4 address.
 groupName - an optional STMS groupname may be specified (the group must already exist in the
STMS).
The following is an example of the contents of this file:
AS9215:10.0.228.189:
AS9215:10.0.246.199:
AS9216:10.0.228.190:
AS9216:10.0.251.46:
DM9225E:10.0.228.186:
DM9225:10.0.228.188:
DM9234:10.0.228.187:
DM9234:10.0.251.44-45/24
1.2.2 NE discovery via the STMS discovery utility

You can discover NEs using the STMS discovery utility. This utility (also referred to as the discover
command) enables you to discover NEs and create STMS groups (or subdomains). This enables you to
discover several NEs at a time.
To use the STMS discovery utility:

1. Log in to a system in which the STMS server has been installed.
2. Open a shell prompt.
3. Change the working directory to the directory in which you installed the STMS software.
4. At the prompt, type:
./bin/discover option argument
where:
 option is a valid command option (or set of options).
 argument is a valid argument (or arguments) associated with the command option.
For a complete list of command options and arguments, see STMS discovery utility commands.
5. Press ENTER.
1.2.2.1 Perform ranged discovery using the STMS discovery utility
You can use the STMS discovery utility for ranged discovery, that is, discovery driven by a list of IP
addresses or ranges. This is useful for discovering a larger number of NEs.
Before initiating ranged discovery, ensure you have a logical organization around your elements. Create
STMS groups to hold, for example, numbers of elements based on geographical locations or administrative
partitioning, and decide which elements (based on address, host name, location, etc.) you wish to put into
the respective groups.
You need to obtain a list of elements by address and device type in CSV format. Common locations for such
lists include inventory systems and spreadsheets. Ensure that each element in the list has an additional
column for the group to which they will be assigned. Without a group listing, all NEs are assigned to a
default group and the list becomes unwieldy when managing a large number of elements. Put the list on
the STMS server so you can call it during discovery.
Use the range option command to discover elements of a particular type. This allows you to discover any
number of elements in a given IP address range. You must run this command for each type of element you
want to discover; it cannot be used to discover a mix of elements.
To use the STMS discovery utility for range discovery via a CSV list:
1. Log in to a system on which the STMS server has been installed.
./bin/discover -t type -f file -o filename
where:
 type is the type of device to discover (default is SR9710).
 file is name of the CSV file that contains a listing of elements by address and device type.
 filename is the name of the file where the discovery results are written.
For example, if you enter a file containing the following information:
SR9200:10.0.242.208
SR9200:10.0.242.209
SR9200:10.0.242.210
SR9200:10.0.242.212
SR9200:10.0.242.213
SR9200:10.0.242.214
you get the results shown in Step 5.
5. Press ENTER.
The output displays the progress of the discovery:
Discovering 10.0.242.208
10.0.242.211::DISCOVERY_FAILED
10.0.242.210::DISCOVERY_COMPLETE
10.0.242.208::NOT_PRESENT
Writing results to: result ... done.
6. (Optional) To see the discovery results, type:
7. more filename (where filename is the name of the file to which the discovery results are written)
and press ENTER.
10.0.242.208:S92XX::NOT_PRESENT: Request = RequestId = 3147
Status = Timeout Occurred. Timeout/MaxTries/NumTries =
15000/3/3 PrevPolled = Wed Jun 10 13:14 :00 EDT 2009 /
RemainingTime(millis)
= -1 UserCreated. SnmpCmd = SnmpGet RequestOptions = 7 Error
status = reqTimeout Error index = 0
10.0.242.209:AS9205::DISCOVERY_COMPLETE
10.0.242.210:DM9234::DISCOVERY_COMPLETE
10.0.242.211:S92XX::NOT_PRESENT:com.lni.lps.client.exceptions
.LPSVersionNotSupported: Version not supported on NE at IP
address /10.0.242.211: version = NeCh assisType(SNMP),
supported versions = DM9225E,DM9225,DM9234,AS9205,AS9215,AS9216
To use the STMS discovery utility for range discovery via an IP address
range:
1. Log in to a system in which the STMS server has been installed.
./bin/discover -t type ip address range -o filename
where:
 type is the type of device to discover (default SR9710).
 ip address range is the range of addresses to be discovered.
 filename is the name of the file where the discovery results are written.
For example, entering ./bin/discover -t SR9200 10.0.242.208-212/24 -o filename gives you the
results shown in Step 5.
5. Press ENTER.
The output displays the progress of the discovery:
10.0.242.211::DISCOVERY_FAILED
Writing results to: result ... done.
6. (Optional) To see the discovery results, type more filename (where filename is the name of the file to
which the discovery results are written) and press ENTER.
10.0.242.209:AS9205::DISCOVERY_COMPLETE
10.0.242.210:DM9234::DISCOVERY_COMPLETE
10.0.242.211:S92XX::NOT_PRESENT:com.lni.lps.client.exceptions
.LPSVersionNotSupported: Version not supported on NE at IP
address /
10.0.242.211: version = NeCh assisType(SNMP), supported
versions
= DM9225E,DM9225,DM9234,AS9205,AS9215,AS9216
The batch size command can be used in combination with the other commands to limit the number of
elements discovered at one time. For example, ./discover -t type -b 3 -f file -o filename limits discovery to
three elements at a time. The server waits for each batch to complete before moving on to the next.
1.2.2.2 STMS discovery utility commands
The following table describes the valid command options and arguments for the STMS discovery utility (or
discover command).
Table 1-1: Command options and arguments

Options/Arguments Description
-h host Connects to the STMS server specified by the host argument in order to issue
commands for that server (host is the host name or IP address of the STMS server).
Note: If you are running the STMS server on a system other than your local system,
you must use the -h option and host argument to issue any STMS Discovery Utility
commands for the remote server.
-b batchsize Completes discovery in batches; waits for each batch to complete before moving
on to the next (default batch size 10).
-o filename Name of file where discovery results must be written.
-t type Specifies the type of device to discover. The correct type is reflected in the output
file if the -o option is specified (type defaults to SR9700).
-f file Specifies a file containing a list of NEs to discover. Each line of the file can contain a
host name, the IP address of an NE's management interface, or a range of IP
addresses. You can also specify a group for each entry by using the :group
argument, as described later in this table.
 ip address — any valid IP address with or without /32 netmask.
 ip address range — any IP address range with a netmask. Ranges may be
specified in any hostpart of IP address. An IP address can be in the form x.x.x.x
and a range is specified in any host part octet as "a-b", where "a" represents
the start of the range and "b" represents the end of the range inclusive, for
example, 192.168.1.2-100/24. The network part of the address must be
specified by a valid netmask - the IP address followed by /XX, where XX is any
number from 1 to 32 for IPv4 address.
host [:group] Where the host argument specifies the host name or IP address of the
management interface for the NE to be discovered. You can also specify a range of
IP addresses by using the last octet to indicate the range. For example, the range
specified by 192.168.1.2-100 includes all IP addresses from 192.168.1.2 to
192.168.1.100.
Additionally, you can use the optional :group argument to specify the name of a
group in the STMS Domain under which you want to discover an NE (the group
must currently exist). For example,
192.168.1.2-100:WEST specifies the group named WEST for all NEs with IP
addresses from 192.168.1.2 to 192.168.1.100
1.2.3 Define the NE ID
Each NE has a unique and persistent ID which is used to identify it in the STMS when uploading information
to the NMS. If the NE ID is not defined on the NE or if there is a mismatch in the NE ID configured on the NE
and STMS, the NE goes to DISCOVERY_FAILED state in the STMS. You can define the NE ID manually via the
CLI.
To define the NE ID on the NE:

 At the CLI prompt, type the following command:
set network-element opt96xx ne-id <ne ID number>
1.3 Define STMS server data

When you define STMS server data on an NE, the NE automatically contacts the STMS server, which then
collects information about the NE's configuration. If the specified STMS server is unavailable, the NE
continues to ping the STMS server until communication is established.
NOTE: Assigning an NE to multiple STMS server instances is not supported.
You can configure STMS server data on an NE using the CLI. To access the CLI, you must log in to the NE.
You can log in to the NE either by logging on at a console or by telneting to the NE.
NOTE: For more information about using the CLI (including logging in to the NE), see the
ShadeTree User Guide.
To define STMS server information on an NE:

1. Log in to the NE via the CLI.
2. At the prompt, type configure and press ENTER.
The CLI enters into configuration mode, as indicated by [edit] and the prompt hash (#).
3. At the prompt, type set system services management stms server ip-address (where ip-address is
the IP address of the STMS server, in the form A.B.C.D.), and then press ENTER.
4. Type commit and press ENTER.
5. Type exit and press ENTER.
The CLI returns to operation mode.
NOTE: You have to perform these steps for each NE on which you want to configure the STMS
server data.
1.4 View STMS Domain properties
The root domain, called the STMS Domain, is created during STMS installation.
To view STMS Domain properties:

 In the Network Explorer tab, right-click STMS Domain and select Properties.
The STMS Domain properties appear in the right pane.
Table 1-2: STMS domain properties

Field Description
STMS P4 Version Build version information for the STMS software.
STMS Server Install Directory Directory in which the STMS server software is installed.
IDL Version Map Interface Definition Language (IDL) version mapping information; specifies
the different versions of the IDL interface supported by the STMS software
to an NE. STMS supports up to three different versions of ShadeTree NE
software and each version may have a different IDL interface. The IDL
versions are specified in the following format:
<IDL 1>:<IDL 2>:<IDL 3>
where each of <IDL 1>, <IDL 2>, and <IDL 3> have the following format:
<release date>-<build line>:<IDL version>
RDR Role If RDR is configured, RDR Role indicates whether the selected STMS is
defined as the Primary or Mirror STMS. The Primary STMS is the functioning
STMS, and the Mirror STMS starts functioning only if the Primary STMS
fails.
STMS Listener Port Port on which the STMS server listens for pings from NEs.
Network Element Bootstrap Port an NE uses to communicate with the STMS server.
Port
# of Discovery Retries Number of times the STMS attempts to initially discover an NE.
# of Worker Threads Number of threads the STMS uses to process data.
Network Element Ping Number of seconds between pings of an NE by the STMS server.
Interval
Event Queue Size Maximum number of events to queue for processing.
Config Change Limit Number of configuration change elements the STMS processes per
transaction.
LI Limit/Transaction Number of logical interfaces on an NE the STMS processes per transaction.
Alarm Queue Size Size (in number of alarms) of the queue for alarms to be written to the
STMS DB.
Max. Period to Persist Alarms Maximum period the alarm will be persisted in the database. Default value
is 60 minutes.
Max. Period to Persist Events Maximum period the event will be persisted in the database once it has
reached the STMS. Default value is 5 days.
Field Description
Min. # of Persistent Alarms Minimum number of alarms always persisted in the database, even if the
Max. Period to Persist Alarms is exceeded.
STMS Server Free Memory Amount of free memory available to the Java Virtual Machine (JVM) used
by the STMS server.
STMS Server Total Memory Total amount of memory allocated to the JVM used by the STMS server.
Maintain historical alarms Whether the STMS maintains historical alarm information.
Email SMTP Host Host name of the mail server the STMS server can use to send emails such
as notification of alarms.
Email Domain Name Domain name to append to unqualified email addresses when sending
email.
Default File Server Host Host name of the server to use for remote storage of files.
Network Element Files Path to the directory for NE system configuration files.
Directory
Reports Directory Path to the directory for report files.
1.5 View SNMP settings

To view SNMP settings for the STMS Domain:
1. In the Network Explorer tab, right-click STMS Domain and select Properties.
The STMS Domain properties appear.
2. Select the SNMP tab.
The SNMP settings appear.
Table 1-3: SNMP settings

Field Description
Alarm Age (seconds) Time in seconds an alarm based on an SNMP trap received by the STMS stays in
the STMS cache and related to that, in the GUI (default 3600 sec). The age is
checked every Max. Period.
Trap Destination Port Port the STMS uses to listen for incoming SNMP traps (default 1620).
1.6 Define the NE configuration files directory
The configuration files directory is used to store system configuration files for NEs. The default
configuration files directory is the /deviceConfig directory in the STMS root directory.
To define the configuration files directory:

2. In the Properties tab, in the Network Element Files Directory field, type the path to the directory you
want to use.
3. Click Apply.
1.7 Define STMS performance parameters

The STMS software is configured during installation to provide optimal performance and reliability.
However, depending on the complexity of your network or changes to your network following the
installation of the STMS software, you may need to adjust particular STMS performance parameters.
NOTE: It is highly recommended that you only change STMS configuration settings described
in this section if directed by an appropriate network/system administrator or technical
support representative.
NOTE: The parameters described in this section are stored in the STMS database. If you use
dbutil to revert the STMS to a prior state, changes you made to these settings may be lost.
To define STMS performance parameters:

2. In the Properties tab, define the performance attributes and click Apply.
The following table describes the STMS performance attributes.
Table 1-4: STMS performance parameters

Parameter Description
# of Discovery Retries Number of times the STMS attempts to discover an NE initially (default 6).
# of Worker Threads Number of threads the STMS uses to process data (default 10).
Network Element Ping Number of seconds between pings of an NE by the STMS server (default 120).
Interval
Event Queue Size Max. number of events to queue for processing (default 50,000).
Config Change Limit Number of configuration change elements the STMS processes per transaction
(default 100).
LI Limit/Transaction Number of logical interfaces on an NE the STMS processes per transaction
(default 100).
Alarm Queue Size Size (in number of alarms) of the queue for alarms that are to be written to the
STMS DB (default 10,000).
Max. period to Persist Max. number of minutes to persist alarms (default 60).
Alarms (minutes)
1.8 Maintain historical alarms

By default, the STMS does not maintain historical alarm information within its database. If you want to
maintain this information, you must enable this feature.
To maintain historical alarms:

2. In the Properties tab, select the Maintain historical alarms checkbox.
3. Click Apply.
2 NE management
You can perform various management and configuration tasks on NEs in the network via the STMS.
2.1 NE implicit configuration

Implicit configuration is the ability to configure equipment and/or supported entities by the NE, without
operator intervention, to their default values as a trigger of another operation.
Implicit configuration is applied in the following cases:
 Equipment configuration: Includes system minimal configuration and discovered equipment whose
location is determined and unique (e.g. a second RCP card, fabric card). Such equipment entities are
implicitly configured to their default configuration values including supported entities. The operator is
required to set equipment type to slots having cards other than common cards.
 Card with unique configuration of supported entities: Includes cards having a unique configuration
of supported entities. Examples are all cards belonging to passive optics cards (e.g. DCF,
splitter/coupler), amplifiers, some ports in ADD ROADMs and service cards having non-FRU
transceivers. In these cases, as part of card assignment, its supported entities, such as its ports, sub-
interfaces or cross-connections, are implicitly configured to default values. When there is a multiple
configuration in the supported entities the operator must explicitly configures these entities.
 Port with unique configuration of its supported entities: The operator is required to specify the port
type and its supported entities are implicitly configured. Service cards, data cards and ROADMS
belong to this category.
In some cases upon explicit configuration of the port, its supported entities and cross connections are
implicitly configured. For example: AOC10 card where its line port is configured to be compatible to
Apollo mode.
In case there are several channelization options within sub-interfaces (e.g. ODU0 within ODU2 and
ODU1 within ODU2), it is required to specify the mapping type in order to configure the additional
sub-interfaces.
Ports participating in ODU cross connections can aggregate a mixture of sub-interfaces (e.g. ODU2 can
have a mixture of 2 x ODU0 and 3x ODU1). Therefore it is required to provide information on the sub-
interfaces in order to configure the cross-connection.
2.1.1 Equipment implicit configuration

Equipment implicit configuration is applied on the following equipment:
 System minimal configuration (i.e. main shelf, RCP, FANs and PFMs) as a result of installation
operation
 Controller cards
 Common cards are implicitly configured by the NE
For cards other than common cards, the operator is required to set the equipment type and the card is
configured to its default configuration.
Cards that require a fabric card are not configured when a fabric card is not yet configured.

STMS User Guide NE management
Cards having unique configuration of supported entities are implicitly configured to their default
configuration values.
A port having unique configuration of its supported entities is implicitly configured to its default
configuration values following its configuration.
2.1.2 Controller cards implicit configuration

Controller cards have the following implicit configuration rules:
 The first discovered controller card is implicitly configured as a simplex (i.e. having no redundancy).
 If two controller cards are simultaneously discovered they are implicitly configured to their default
configuration.
The operator must explicitly configure auto-switchover and high availability in order to have redundancy
behavior. Without redundancy configured, configuration changes are not synchronized to the standby.
The main shelf implicitly configures a controller card discovered in a passive shelf.
2.1.3 Severity profiles implicit configuration

Severity profiles contain alarm and event lists per each managed entity type. NE implicitly creates all
default profiles per each managed entity types.
You can also manually create a severity profile from the STMS. See Creating a Severity Profile in the STMS
Performance Management Guide.
2.1.4 PM threshold profiles implicit configuration

PM threshold profiles contain counters threshold lists per each managed entity type. NE implicitly creates
all default PM profiles per each managed entity.
You can also manually create a PM profile from the STMS. See Creating a PM Profile in the STMS
2.1.5 Cross connection implicit configuration

Cross connection implicit configuration is as follows:
 Fixed cross connections are implicitly configured following assignment of card having unique
connectivity.
 A card deletion implicitly deletes its fixed cross connections.
 Fixed cross connections are implicitly configured following configuration of a port having unique
connectivity (e.g. a client port in CMB40 implicitly configures a fixed cross connection).
 Port deletion implicitly deletes its fixed cross connections.
 Modification changes in fixed cross connection attributes are allowed only on non-traffic affecting
attributes.

2.1.6 Protection group implicit configuration
Entities that participate in protection implicitly configure their protection group entity, as follows:
 A protected fixed cross connection implicitly configures its protection group (e.g. protection group in
splitter coupler cards).
 Configuration of an unprotected cross connection to be protected implicitly configures its protection
group.
 Configuration of a protected cross connection to be unprotected implicitly deletes its protection
group.
 Upon configuration of fabric protection the associated protection group is implicitly configured.
 Upon deletion of fabric protection the associated protection group is implicitly deleted.
 Modification changes on protection group attributes are allowed.
A protection group is explicitly created and deleted in the case of port protection.
2.1.7 Transport entities implicit configuration

Transport entities (ports and sub-interfaces) have the following implicit configuration rules:
 Cards with unique configuration, following card configuration, all ports and their supported entities
are implicitly configured to their default values. In addition the NE implicitly configures all cross
connections on this card (e.g. passive optics cards (DCF, splitter/coupler), and amplifiers).
 High order sub-interfaces are implicitly configured following its supporting port configuration (e.g.
upon configuration of port type OTU2, NE implicitly configures its ODU2 sub-interface).
 High order sub- interfaces are implicitly deleted due to deletion of its supporting port.
 A port with unique configuration of its sub-interface, following configuration of port type and/or port
mapping, its sub-interfaces is implicitly configured to the default values (e.g. FC10G port with port
mapping ODU2 implicitly configures a sub- interface ODU2).
 For OTS ports in OADM and MUX/DEMUX and some ports in ROADM cards, each OTS port and all its
OCH sub-interfaces are implicitly configured. The number of OCH sub- interfaces are determined
according to port spacing attribute (44 channels for 100 GHz and 88 channels for 50 GHz).
 Modification requests on implicitly configured transport entities are allowed unless they require
deletion of the entities.
2.2 Configure an NE using Plug and Play

The Plug and Play tool uses the LightPLAN OM/SM output file to install and configure equipment on
managed NEs (locally or remotely) through automatically-generated CLI commands. Plug and Play
functionality simplifies the configuration of the NE and its component shelves, cards, and ports, as well as
the associated fiber link configuration.
You can configure an NE that is already installed using the Plug and Play tool.
To configure an NE using the Plug and Play tool:

1. From the Tools menu, select Plug & Play.
The Select and Configure NE(s) window opens.
2. Click Select and browse for the XML file.

The NEs in the XML file are listed in the Network Elements section.
The NEs that exist in the Network and are found and are listed as Ping Succeeded and Installed.
3. To view each NEs configuration in the XML file, right-click on the NE and select XML Hierarchy.
A window opens showing the NEs configuration in an XML tree view. If the XML code was configured
properly, then the shelf, cards and ports are shown in green and marked as success
If the XML code was not configured correctly then the NE is displayed in red with an explanation in
the Error Details section.
4. Select the NEs that you want to update with the configuration and click Configure.
If an NE is not discovered by the STMS, you will receive a warning.
5. Click Yes to configure the NE anyway, and click No to cancel.

When finished, each NE's configuration status is listed in the Network Elements area.
2.3 View NE properties
To view NE properties:
 In the Network Explorer tab, right-click the NE and select Properties.
The Properties tab appears in the right pane.
The following fields appear in the NE Properties tab.
Table 2-1: NE Properties

Field Description
General
Hostname (read-only) Host name of the NE or the IP address of the NE's management interface.
NE ID Unique number assigned to the NEs managed by the STMS. (Read Only)
Group Name (read-only) Name of the group to which the NE belongs.
IP Address (read-only) IP address of the NE's management interface.
Model (read-only) Model information for the NE.
Router ID Primary IP address of the NE.
ST Software Version Version of ShadeTree software running on the NE.
(read-only)
Active RCP Software Version Software version of the active RCP card. The initial part of the version
(read-only) number indicates the NE version number (e.g. 7.3).
Field Description
Standby RCP Software Software version of the standby RCP card. The initial part of the version
Version (read-only) number indicates the NE version number (e.g. 7.3).
NE Uptime (read-only) Length of time (in hours, minutes, and seconds) that the system process
daemon has been running on the corresponding RCP.
State (read-only) Current state of the NE:
 reachable: NE has successfully been contacted by the STMS.
 not reachable: NE cannot be contacted by the STMS.
 discovery in progress: NE is currently being discovered by the STMS.
 discovery complete: NE has successfully been discovered by the STMS.
 discovery failed: NE was not successfully discovered by the STMS. Must
be refreshed or deleted manually.
 rediscovery scheduled: NE will be rediscovered prior to being managed
by the STMS.
 rediscovery in progress: NE is currently being rediscovered by the
STMS.
 squelched: Management of the NE has been suspended by the STMS
temporarily. After a period of time the STMS will attempt to rediscover
the NE.
 orphaned by user: Per user request, NE is no longer being managed by
the STMS.
 delete in progress: NE is currently being deleted by the STMS (will no
longer be managed by the STMS).
 unsupported version: NE is running a version of the routing software
not currently supported by the STMS.
 unknown: NE state unknown.
Description Description of the shelf.
Audible Alarm
Enable or Disable the NE's audible alarm indications.
Severity Profile The severity profile that has been assigned to the NE.
Domain Name Domain name of NE.
DNS Servers DNS servers resolve host names to IP addresses. You must have a DNS
server address configured in order for the switch router to resolve IP
addresses to host names.
Linux Hostname (read-only)
Host name used by the Linux OS. It is defined during NE installation and can
include only a limited number of characters.
Shelf
Mode (for OPT96xx only) Current operating mode of the shelf.
Configured Type Type of shelf configured.
Actual Type Type of shelf that is physically present.
Time
Field Description
Date & Time Date and time set on the NE. Click Refresh to update.
Click Set Date and Time to manually set the NE date and time or to select an
NTP server to set the NE date and time. (To use this option, NTP must be
configured with an NTP server.)
Time Zone Time zone configured on the NE; can be modified by the user. Default time
zone is Universal Time Coordinated (UTC), the international time standard
(formerly Greenwich Mean Time (GMT)).
Location
System Location Free-text attribute used for indicating the chassis location (255 character
limit).
Longitude NE's distance east or west (in degrees and minutes), relative to the Prime
Meridian (0° longitude).
Latitude NE's distance north or south (in degrees and minutes), relative to the
Equator line (0° latitude).
Rack Number Rack number on which shelf is located.
Position in Rack The number within the rack that indicates the shelf position.
IP
IP Policing – Exclude Layer-2 Configures the switch router to ignore the Layer 2 header when policing and
Encap shaping IP traffic.
(for OPT96xx only) By default, when the switch router polices or shapes IP traffic on the ingress,
it includes the bits in the Layer 2 header when it determines the rate of the
packet flow.
You can configure the switch router to exclude these bits as part of the flow.
This leads to a less aggressive policing and shaping scheme and potentially
fewer dropped packets since the packet size is smaller.
IPv6 Classification – Include Sets the IPv6 classification mode to include traffic classification.
Traffic Class
(for OPT96xx only)
Firewall
Pre-Filter Name of a firewall filter to apply globally before all configured interface
firewall filters.
When global filters are configured and there is no interface filter for the
destined interface, and if no match conditions are met in any of the filters,
the packet is accepted.
When global filters are configured and there is an interface filter for the
destined interface, if no match conditions are met in any of the filters, the
packet is discarded.
Field Description
Post-Filter Name of a firewall filter to apply globally after all configured interface
firewall filters.
When global filters are configured and there is no interface filter for the
destined interface, and if no match conditions are met in any of the filters,
the packet is accepted.
When global filters are configured and there is an interface filter for the
destined interface, if no match conditions are met in any of the filters, the
packet is discarded.
Utilization Thresholds
CPU Percentage of CPU resources that can be used before a CPU utilization alarm
is generated, range from 1 to 100 percent (default 90).
Memory Percentage of memory resources that can be used before a memory
utilization alarm is generate, range from 1 to 100 percent (default 90).
File system Percentage of file system resources that can be used before a file system
utilization alarm is generated, range from 1 to 100 percent (default 90).
PM
Protocol Protocol used for PM data collection.
User ID User ID to connect to the NE for PM data collection.
Password Password for the User ID to connect to the NE for PM data collection.
2.4 View NE operational status

To view the operational status for an NE:
1. In the Network Explorer tab, right-click on the NE and select Properties.
The NE properties appear.
2. Click the Operational Status tab.
The NE operational details appear. The details vary for different types of NEs:
 For all OPT99xx NEs and for OPT96xx NEs (when enabled), DC power consumption information
appears.
 For OPT99xx NEs, the Fan Spin appears for the three Fan cards.
 Temperature statistics appear for all NEs.
2.5 Connect to an NE using Telnet
The STMS server enables you to connect to an NE using the Telnet client provided with your OS.
NOTE: On Linux and Solaris systems, the path /usr/bin must be added to your system's PATH
environment variable to use the Telnet command.
To open a Telnet session to an NE:

1. In the Network Explorer tab, right-click the NE to which you want to connect and select Connect >
telnet.
A Telnet session to the NE opens in a new window.
2. At the login prompt, enter a valid user name and press Enter.
3. At the password prompt, enter the password and press Enter.
A Telnet session is established with the NE.
2.6 Connect to an NE using SSH

The STMS server enables you to connect to the NE using the SSH client provided with the STMS software.
NOTE: On Solaris systems, SUNWCuser metacluster or above must be installed to use the SSH
command.
NOTE: Windows does not come with a built-in SSH command, so it is necessary to install a
third-party SSH application. The suggested application is PuTTY (which can be obtained at
http://www.putty.org/).
The default installation location for PuTTY is C:\Program Files\PuTTY, so that the path is
assumed here. If you installed PuTTY with another path, or if you are using a different SSH
program, adjust these instructions accordingly.
After installing PuTTY in Windows, follow these steps:
 Add ";C:\Program Files\PuTTY" to your windows Path environment variable.
 To get the update to the path to take effect, restart your web browser and then restart
your client from the "Download the Client via WebStart" link.
In the directory "C:\Program Files\PuTTY", copy the binary file "putty.exe" to a file called
"ssh.exe."
To open an SSH session to an NE:
1. In the Network Explorer tab, right-click the NE to which you want to connect and select Connect >
ssh.
The Login Name window opens.
2. Enter a valid user name and click OK.
An SSH session to the NE opens in a new window.
3. At the password prompt, enter the password and press Enter.
An SSH session is established with the NE.
2.7 Check network connectivity

You can use ping to determine if a remote host is reachable. Ping sends Internet Control Message Protocol
(ICMP) echo request packets to a specific host, and then displays an ICMP echo reply packet from the host.
You can check the reachability of a host through network interfaces or though the management interface.
Ping can also be used to help determine if the management network has been configured correctly.
To ping an NE:
 In the Network Explorer tab, right-click the NE for which you want to check the network connectivity
and select Actions > Ping IP Address.
The Ping IP Address window opens.
The result of the ping is displayed in the Ping Result field.
2.8 Delete an NE
Deleting an NE clears the NE from display in the STMS server and removes the associated STMS server
configuration information from the NE.
To display an NE in the STMS Client after it has been deleted, you must discover the NE again using the
procedures described in NE Discovery.
To delete an NE:
 In the Network Explorer tab, right-click the NE that you want to delete and select Delete.
2.9 Move an NE
You can move NEs within the STMS hierarchical structure in one of the following ways:
 From the STMS Domain to a group or subgroup, or vice versa
 From group to group
 From subgroup to subgroup
To move an NE:
 Drag the NE to the desired location in the Network Explorer tree.
2.10 Halt an NE
You must halt an NE prior to powering it off. Halting an NE stops all system processes on it. To restart an NE
after a system halt, you must power off the NE and then power it on.
NOTE: In a dual RCP system, halting an NE stops the system processes on both the active and
the standby RCPs. For information about halting an individual RCP, see Halting an RCP.
To halt an NE:
1. In the Network Explorer tab, right-click the NE you want to halt, point to Actions, and then click Halt.
A confirmation popup opens.
2. Click Yes. The NE is halted.
2.11 Restart an NE
You can restart the system software on an NE, instead of performing a system-wide reboot of the NE.
NOTE: In a dual RCP system, restarting an NE restarts the system software on both the active
and standby RCPs. For information about restarting an individual RCP, see Restarting an RCP.
To restart an NE:
1. In the Network Explorer tab, right-click the NE you want to restart and select Actions > Restart.
A confirmation message appears.
2. Click Yes.
The system software on the NE is restarted.
2.12 Reboot an NE
Rebooting the NE performs a system-wide reboot of the NE.
NOTE: In a dual RCP system, rebooting an NE reboots both the active and the standby RCPs.
See Rebooting an RCP.
To reboot an NE:
1. In the Network Explorer tab, right-click the NE that you want to reboot, and point to Actions. Then,
click either:
 Reboot To Defaults: reboots the device using the factory default settings.
 Reboot Save: saves the current configuration as the starting configuration, and then reboots.
A confirmation popup opens.
2. Click Yes. The NE is rebooted.
2.13 Flash LEDs on an NE

You can flash the LEDs on all of the component cards for an NE. This option is useful for physically locating a
particular NE in an equipment room.
To flash the LEDs on all of the NE's component cards:

 In the Network Explorer tab, right-click the NE for which you want to flash LEDs and select Flash LEDs
> Start.
The LEDs start flashing.
To stop flashing the LEDs, right-click the NE and select Flash LEDs > Stop.
2.14 Refresh an NE
While the STMS server strives to maintain and display complete and accurate information for each NE,
there may be instances when the configuration and alarm information displayed in the STMS server may
not fully reflect the information for an NE that is stored in the STMS DB. Under these circumstances, you
can perform an update (or "refresh") of the configuration and alarm information for a particular NE.
NOTE: It is recommended that you perform a refresh only when necessary. Refreshing alarm
information for an NE can unnecessarily consume processing and networking resources and so
degrade the overall performance of the STMS.
NOTE: To perform a refresh for only an NE's alarm information, see Refreshing Alarm
Information.
2.15 Refresh alarm information

While the STMS strives to maintain and display completely accurate information about the alarms for each
NE, there may be instances when the alarm information displayed in the STMS server may not fully reflect
the current state of alarms for an NE. Under these circumstances, you can request that the STMS perform
an update (or "refresh") of the alarm information for a particular NE.
NOTE: It is recommended that you perform a refresh only when necessary. Refreshing alarm
information for an NE can unnecessarily consume processing and networking resources, so
degrading the overall performance of the STMS.
To perform a refresh for both NE configuration and alarm information, see Refresh an NE.
To refresh alarm information for an NE:

 In the Network Explorer tab, right-click on the NE for which you want to refresh alarm information
and select Actions > Refresh Alarms.
2.16 Unmanage an NE
You can temporarily suspend the ability to manage an NE through the STMS server, without deleting it.
When you unmanage an NE, it remains discovered by the STMS and is displayed in the Network Explorer
tab, but you can't issue commands to manage or provision it (or the component cards and interfaces
associated with it).
In addition, alarm and log information of an unmanaged NE is not displayed in the STMS server. You can
only continue to view its properties.
To start managing the NE again, you must reconnect the NE.
NOTE: It is recommended that you unmanage an NE only under special circumstances (such
as an NE generating an unusual number of alarms or unnecessarily consuming STMS
processing and networking resources).
NOTE: Reconnecting an NE causes the STMS to refresh its configuration information and can
unnecessarily consume processing and networking resources, which can degrade the overall
performance of the STMS.
To unmanage an NE:
 In the Network Explorer tab, right-click the NE you want to unmanage and select Unmanage.
2.17 Reconnect an NE
To reconnect an unmanaged NE:
 In the Network Explorer tab, right-click the NE you want to reconnect and click Reconnect.

2.18 Define logging for an NE

Logging is enabled for an NE record of system-wide events, such as:
 Users logging in and out of the router
 Interfaces coming up or going down
 Changes to the configuration
 Authorization attempts
For more information on log management, see the STMS Performance Management Guide.
To define logging for an NE:

1. In the Network Explorer tab, right-click the NE for which you want to set logging, and click Logging.
The Logging Levels window opens.
2. In the Logging Level list, select a level:
 Emergency: panic conditions that make the system unusable
 Alert: conditions that must be corrected immediately
 Critical: critical conditions
 Error: error conditions
 Warning: warning messages
 Notice: conditions that need special handling
 Info: informational messages
 Disable: logging
3. Click OK.
NOTE: Logging levels are defined in a hierarchical structure. Messages are displayed for the
level you specify and all those below that logging level. For example, if you set the logging
level to alert, messages for the emergency level are displayed in addition to messages for the
alert level. If you set the logging level to critical, messages for both the emergency and alert
levels are displayed in addition to messages for the critical level.
NOTE: By default, if you set logging for multiple NEs, messages for all of the NEs are displayed
in the Network Element Logging tab in the Alarm/Log panel. However, you can change the
STMS server view preference to display the logging messages for each NE in separate tabs in
the Alarm/Log panel.

2.19 View NE temperature statistics
To view temperature statistics for an NE:
1. In the Network Explorer tab, right-click on the NE and select Properties.
2. Click the Operational Status tab.
The temperature statistics for the NE's installed cards appear in a table.
3. To view a graph of the statistics, select the checkboxes for the relevant cards (four maximum) in the
View Graph column and click View Graph.
A window opens, displaying a graph of the temperature statistics for the selected cards.
2.20 Viewing NE power control areas
OPT99xx features a distributed fully-redundant power feed subsystem. The power distribution is divided
into separate areas, where each xPFM pair provides power to one area.
To view power control areas for an NE:

 Do one of the following:
 From the Network Explorer tab, right-click the NE and select Show Power Control Areas.
The Power Control Areas View window opens, displaying the OPT99xx chassis power
distribution structure. The color of the xPFM pair corresponds to the color of the cards/slots it is
feeding.
 From NE Chassis view, click on an xPFM.
The xPFM pair and the cards/slots it is feeding are highlighted.
2.21 View NE capacity data

You can view port usage and card capacity data for an OPT99xx NE.
To view NE capacity data:

1. From the Network Explorer tab, right-click the NE and select Show Capacity.
The Show Capacity window opens, displaying the chassis.
The Capacity area shows the maximum capacity of the NE, the assigned cards capacity, and the
available capacity.
In the View area, the Port Usage view is selected by default. In this view, the number of
assigned/available ports appears at the top of each card in the chassis. Different colors within the
cards indicate the number of unused, provisioned, or blocked ports (see the legend).
2. To view card capacity data, select the Card Capacity view.
The percentage of used capacity appears at the top of each card in the chassis. Different colors within
the cards indicate the amount of free, provisioned, and blocked capacity (see the legend).
3. To export the capacity data to a CSV file, click Export.
2.22 Define LCT access to an NE

You can manage the secure access level of each NE by defining its LCT Security Mode. This parameter
controls all LCT user privileges when connecting to the NE.
NOTE: Only users belonging to the Admin or Security user groups can define LCT access to an
NE.
The security modes available are:

 No Access: Disconnected.
 No Access with RO Option: Disconnected but the LCT user has the option to ask for Read Only access.
 RO Access: Read Only access.
 RO Access with RW Option (default): Read Only access is allowed, and the LCT user has the option to
ask for Read Only access.
 RW Access: Read and Write access.
To define LCT access to an NE:
1. Right-click on the NE and select Properties.
The NE Properties view appears.
2. Click the LCT Security tab.
The LCT Security Mode field appears.
Figure 2-1: LCT Security Tab
3. Select the security mode from the LCT Security Mode dropdown list and click Apply.
NOTE: Only users belonging to the Admin or Security user groups can define this setting.
Other users have read-only permissions.
2.23 NTP configuration

Network Time Protocol (NTP) is used to synchronize the clocks in computers, routers, and other network
devices. There are many stratum-1 and stratum-2 time servers on the internet that are synchronized to UTC
via radio, satellite, or modem. Stratum-1 servers are synchronized to a reference clock, while stratum-2
servers are synchronized to stratum-1 servers.
You can configure the switch router to be an NTP client, an NTP server, or both. However, NTP servers are
only trusted (time-wise) if the server is synchronized to another server. This means that every NTP server is
synchronized to at least one other device upstream. This progression of NTP servers terminates at a high-
precision clock. When a synchronization attempt occurs and the switch router’s time differs from
the NTP server time by less than 128 seconds (approximately two minutes), the clock is slowly
synchronized. However, if the switch router’s clock differs from the NTP server by more than 128
seconds, the clock is not synchronized. You must set the clock on the switch router to deviate from the
correct time less than 128 seconds.
When the switch router first boots and connects to a network, it contacts its NTP boot server for the
correct time and date. You must configure an NTP boot server to ensure that the switch router’s date and
time are set within 128 seconds of the current time so that the switch router can synchronize to an NTP
server. You can add more than one boot server for NTP. Additional servers make NTP synchronization more
precise and reliable.
The switch router can operate in the following NTP modes:
 Symmetric: An NTP host operating in this mode is synchronized by its peers and synchronizes its
peers. This mode is intended for root servers with moderate to large subnets where rapid response is
required.
 Client: An NTP host operating in this mode is synchronized by a peer. However, it does not
synchronize its peers.
 Broadcast: An NTP host operating in this mode broadcasts to a multicast or broadcast address, which
allows it to synchronize all of its peers. However, it cannot be synchronized by any of its peers. This
mode is intended for operation on high-speed LANs with numerous workstations and where the
highest accuracies are not required.
 Broadcast Client: A switch router operating in this mode enables reception of broadcast server
messages.
In order to avoid accidental or malicious disruption in the Client mode, both the server and client should
operate using symmetric-key or public-key authentication.
2.23.1 Configure NTP on an NE

To configure NTP on an NE:
1. In the Network Explorer tab, right-click the NE and select NTP > Configure.
The NTP Configuration Mode window opens.
2. Select the relevant NTP Mode checkbox (Symmetric, Client, Broadcast Server, or Broadcast Client).
You can select more than one mode.
3. To configure NTP authentication, select the Enable Authentication checkbox.
4. Click Next.
The NTP Configuration window opens.
5. You can perform the following procedures:
 Add an NTP bootstrap server
 Add an NTP authentication key
 Define NTP symmetric mode
 Define NTP client mode
 Define NTP broadcast mode
 Define NTP broadcast client mode
6. Click Save. to save the configuration.
Once NTP is configured, the NE attempts to start using NTP to synchronize its time. However, if the
time difference between the NE and the NTP server is too large, the NE's time is not adjusted. See
Setting the Device Time to Work with NTP.
2.23.2 Add an NTP bootstrap server
To add an NTP bootstrap server for the NE:
1. In the NTP Configuration window, under the Bootstrap Servers list, click Add.
The Bootstrap Server Hostname window opens.
2. Enter the hostname or IP address of the NTP boot server, and click OK.
The hostname/IP address is added to the Bootstrap Servers list.
NOTE: You can add more than one boot server for NTP. More servers make NTP
synchronization more precise and reliable.
2.23.3 Remove an NTP bootstrap server

To remove an NTP bootstrap server for the NE:
 In the NTP Configuration window, from the Bootstrap Servers list, select the bootstrap server you
want to remove and click Remove.
The bootstrap server is removed.
2.23.4 Add an NTP authentication key

To add an NTP authentication key:
1. In the NTP Configuration window, click Add.
The Add Authentication Key window opens.
2. Define the following parameters for NTP authentication.
Authentication Key A number for the authentication key, from 1-4,294,967,295.

Type Authentication type - MD5. Must be the same between NTP peers.
Value Enter the password for authentication. If the password includes special
characters, enclose the password in quotes (").
Trusted Select this checkbox to configure the authentication keys that connecting NTP
peers can use when they connect to the switch router.
3. To add the authentication key to the Authentication Keys list, click Finish.
NOTE: Other NTP hosts can synchronize to the switch router without authentication.
However, if NTP authentication is configured, remote hosts must authenticate before they are
used to synchronize the time on the local switch router.
2.23.5 Remove an NTP authentication key
To remove an NTP authentication key:
 In the NTP Configuration window, from the Authentication Keys list, select the key you want to
remove and click Remove.
2.23.6 Define NTP symmetric mode

To define an NE as an NTP host in symmetric mode:
1. To add a peer, click Add. The Add NTP Peer window opens.
2. Configure the following properties.
Hostname Hostname or IP address of the remote NTP peer.

Prefer Select this checkbox if this peer is preferred over all other configured peers.
Version Version of NTP packets you want the NE to send, from 1 to 3.
Min Poll Minimum polling interval, in the range 4-14. These values represent a power 2, so the
polling interval can be set from 16 (24) to 16,384 (214) seconds. Min. polling interval
must be less than the max. polling interval. Default is 6 (i.e., 64 seconds).
Max Poll Maximum polling interval, in the range 4-14. These values represent a power 2, so the
polling interval can be set from 16 (24) to 16,384 (214) seconds. Max. polling interval
must be greater than the min. polling interval. Default is 10 (i.e., 1024 seconds).
Key If authentication is required, select an authentication key number from the dropdown
list.
3. To add the peer to the list of NTP peers for this NE, click Finish.
2.23.7 Remove an NTP peer

To remove an NTP peer from the list of peers:
 In the NTP Configuration window, from the Peers list, select the peer you want to remove and click
Remove.
The peer is removed from the list.
2.23.8 Define NTP client mode
To define an NE as an NTP host in client mode:
1. To add a server, click Add.
The Add NTP Server window opens.
2. Configure the following properties.
Hostname Hostname or IP address of the remote NTP server.

Prefer Select this checkbox if this server is preferred over all other configured servers.
Version Select the version of NTP packets you want the NE to receive, from 1 to 3.
Min Poll Enter the minimum polling interval, in the range 4-14. These values represent a power
2, so the polling interval can be set from 16 (24) to 16,384 (214) seconds. The min. polling
interval must be less than the max. polling interval. Default is 6 (i.e., 64 seconds).
Max Poll Enter the maximum polling interval, in the range 4-14. These values represent a power
2, so the polling interval can be set from 16 (24) to 16,384 (214) seconds. The max. polling
interval must be greater than the min. polling interval. Default is 10 (i.e., 1024 seconds).
Key If authentication is required, select an authentication key number from the dropdown
list.
3. To add the server to the list of NTP servers for this NE, click Finish.
2.23.9 Remove an NTP server

To remove an NTP server from the list of servers:
 In the NTP Configuration window, From the Servers list, select the server you want to remove and
click Remove.
The server is removed from the list.
2.23.10 Define NTP broadcast mode

To define an NE as an NTP host in broadcast mode:
 In the Broadcast Servers group, define the following parameters.
Broadcast Address IP multicast address to which to send NTP messages.

Version Version of NTP packets you want the NE to receive, from 1 to 3.
Key If authentication is required, select an authentication key number from the
dropdown list.
TTL Enter the time-to-live (TTL) value for the NTP packets the switch router sends,
from 1 to 7 (default 1).
2.23.11 Define NTP broadcast client mode
To define an NE to listen for broadcast NTP messages:
 In the Broadcast Client group, define the following parameters.
Broadcast Client Select this checkbox to enable the NE to listen for broadcast NTP messages.
Multicast Address Multicast IP address from which to listen for messages.
2.23.12 Set the device date and time

The date and time can be set manually or you can configure an NTP server to synchronize the date and
time.
When NTP is configured, a synchronization attempt occurs. If the switch router’s time differs from
the NTP server’s time by less than 128 seconds, the clock is slowly synchronized. However, if the
switch router’s clock differs from the NTP server by more than 128 seconds, the clock cannot be
synchronized, and you must manually change the clock on the switch router (to be less than 128 seconds
off the NTP time).
You can manually change the router clock by either logging in to the router and changing it in LSH, or by
removing the NTP configuration and manually changing the clock via the STMS GUI.
You can use the Set Device Date and Time window to set the device’s time.
NOTE: If NTP is configured, setting the date and time manually is disabled. If NTP is not
configured, you can only set the date and time manually.
To set the device date and time from an NTP server:

1. In the Network Explorer tab, right-click the NE and select Properties.
2. Click Set Date & Time.
The Set Device Date and Time window opens.
Figure 2-2: Set Device Date and Time
3. Do one of the following:
 To set the date and time from the NTP server, select the NTP Server option and select an NTP
server from the dropdown list.
 To manually set the date and time, select the Set Date & Time Manually option and enter a new
time. In the first field, enter the date in MM/DD/YYYY format. In the second field, enter the
time in HH:MM:SS format (HH in 24-hour format).
4. Click Finish.
2.23.13 Remove the NTP configuration from an NE

To remove NTP configuration from an NE:
 In the Network Explorer tab, right-click the NE from which you want to remove NTP and select NTP >
Remove.
The NTP configuration is removed from the NE.
NOTE: The configuration can be changed within the modes already selected. For example, if
Client mode is selected, peers can be added, removed, or modified.
2.23.14 View NTP properties

To view NTP properties:
1. In the Network Explorer tab, right-click the NE whose properties you want to view, and select
Properties.
2. Click the NTP tab. (If the NTP tab is not visible on the tab bar, click the right arrow on the row of tabs
until the tab becomes visible.)
In the Operational tab, you can see the following operational properties of NTP peer associations:
 remote: Name of the remote NTP server.
 refid: Where each server is getting its time right now, either a server hostname or something
like .GPS., indicating a Global Positioning System source.
 st: Stratum - a number from 1 to 16, indicating the remote server precision. 1 is the most
accurate, 16 means 'server unreachable'. Your stratum is equal to the accurate remote server
plus 1.
 poll: Polling interval (in seconds) between time requests. The value ranges between the min.
and max. allowed polling values. Initially the value is smaller to allow synchronization to occur
quickly. After the clocks are 'in sync', the polling value increases to reduce network traffic and
load on popular time servers.
 reach: Octal representation of an array of eight bits, representing the last eight times the local
machine tried to reach the server. The bit is set if the remote server was reached.
 delay: Length of time (sec) needed to receive a response for a "what time is it" request.
 offset: The most important value; the difference of time between the local and remote server.
In the course of synchronization, the offset time drops more, indicating that the local machine
time is getting more accurate.
 jitter: Dispersion, also called jitter, is a measure of the statistical variance of the offset across
several successive request/response pairs. Lower dispersion values are preferred over higher
dispersion values as they allow more accurate time synchronization.
3. Click the Configuration tab to view the NTP configuration properties. These include:
 List of Bootstrap servers
 List of Authentication Keys
 List of Peers for symmetric mode
 List of servers for client mode
 Broadcast server configuration
 Broadcast client configuration
2.24 Security certificate management

The STMS and NEs use security certificates for SSL communication. Each certificate (key-pair) is composed
of a private key and a public key.
The STMS stores three security certificate values for itself:
 Default: the default value, defined during installation
 Current: the currently used value
 New: a new value pending activation
When a new STMS certificate is created, it is defined as New. When the new certificate starts being used, it
is copied to Current.
You can create a new STMS certificate by either loading it from an existing file or by instructing the STMS to
generate a new file (see Creating a New STMS Certificate). You can then choose whether to enable the
STMS to distribute the new STMS public key to the NEs (with V6.1 or higher) automatically, or to load it to
each NE manually yourself (via disk-on-key/Telnet). You must load the public key manually to NEs with V5.1
or lower.
If the automatic distribution of the public key is selected, after the STMS receives at least one acknowledge
message for the new setting from an NE, it sends a command to all the NEs instructing them to start using
the new certificate. After this command is acknowledged by at least one NE, the STMS copies the value of
the new certificate from New to Current.
The STMS also stores the public keys of all NEs, including their Default, Current, and New values. If you
change the NE public key manually, you can either select to distribute it to STMS automatically by
communication channel, or to manually load it to the STMS server (see Loading an NE Public Key to the
STMS Server).
You can also send a command from the STMS to instruct an NE to create a new certificate for itself (see
Creating a New NE Certificate). After the NE creates its new certificate, the STMS instructs the NE to start
using the certificate (copy it to Current) in order to begin SSL communication.
For data encryption, NEs have to authenticate themselves when sending messages to other NEs. Each NE
stores a list of peer IPs containing the public key of each NE from which it can receive encrypted messages
(see Accessing the Peer IPs Table).
2.24.1 Create a new STMS Certificate

You can create a new STMS certificate (key-pair), which is composed of a private key and a public key.
To create a new STMS certificate:

1. From the Security menu, select STMS Certificate Settings.
The STMS Certificate Setting window opens.
2. In the STMS Certificate Setting pane, select one of the following:

 Load File: to load an external certificate file (the file must be saved in
<INSTALL_DIR>/data/security/certs). Click Select to select the file from a list of files.
 Generate: to generate a new certificate file.
3. In the Certificate Exchange pane, select one of the following:
 Automatic: to enable the STMS to automatically distribute the new STMS public key to all NEs in
the network (with V6.1 or higher). After receiving at least one acknowledge message for the
new setting from each NE, the STMS will send a command to the NEs instructing them to start
using the new certificate. After this command is acknowledged by at least one NE, the STMS will
copy the value of the new certificate from New to Current.
 Manual: to load the public key to each NE manually. You must copy the new public key to a disk-
on-key and load it to each NE separately via Telnet over SSH (or other direct methods).
NOTE: For NEs with V5.1 or lower, you must select Manual and load the public key to each NE
manually.
4. Click Set.
The STMS creates the new STMS certificate according to the selected settings.
 If you selected Automatic for the Certificate Exchange, one of the following occurs:
 If the operation of setting the new STMS public key succeeded for all NEs, the STMS sends a
command to the NEs instructing them to start using the new certificate. After this
command is acknowledged by at least one NE, the STMS copies the value of the new
certificate from New to Current and starts a new SSL session with the NEs.
A success message appears.
 If the operation of setting the new STMS public key succeeded for only some of the NEs, a
message appears enabling you to access a list of NEs for which the operation failed. You
will need to load the public key to each of these NEs manually via Telnet over SSH (or
other direct methods).
The STMS will then send a command to the NEs that acknowledged the new setting,
instructing them to start using the new certificate. After the NEs acknowledge this
command, the STMS copies the value of the new certificate from New to Current and
starts a new SSL session with the NEs.
 If the operation failed for all NEs (none of the NEs acknowledged the new public key
setting), a failure message appears. In this case, you can run the operation again (see
Updating New STMS Public Key for all NEs).
 If you selected Manual for the Certificate Exchange, you are prompted to enable the STMS to
start using the new certificate.
 If you select Now, the STMS will copy the value of the new certificate from New to Current.
 If you select Later, you will need to activate the certificate manually at a later time (see
Manually Activating a New STMS Certificate).
2.24.2 Update new STMS public key for all NEs

During the creation/loading of a new STMS certificate, if you selected Automatic for the Certificate
Exchange setting, and the operation failed for all NEs, you can run the operation again to update the new
public key for all NEs.
To update the new STMS public key for all NEs:

1. From the Security menu, select Set New STMS Public Key to all NEs.
2. Click OK to run the operation.
The STMS distributes the new STMS public key to all NEs in the network (with V6.1 or higher). After
receiving at least one acknowledge message for the new setting from each NE, the STMS will send a
command to the NEs instructing them to start using the new certificate. After this command is
acknowledged by at least one NE, the STMS will copy the value of the new certificate from New to
Current.
2.24.3 Manually activate a new STMS certificate

During the creation/loading of a new STMS certificate, if you selected Manual for the Certificate Exchange
setting and then selected Later when prompted to activate the new STMS certificate, you must activate the
certificate manually.
You should only perform this procedure if you finished loading the new public key to each NE manually.
To manually activate a new STMS Certificate:

 From the Security menu, select Start Using STMS New Key-Pair.
The STMS copies the value of the new STMS certificate from New to Current.
2.24.4 Load an NE public key to the STMS server
Before NE discovery or when an NE certificate is changed manually, you must load the NE public key to the
STMS server. In both cases, a root user must first load the file to the relevant folder on the STMS server.
For NE discovery, the NE discovery operation will automatically load the NE public key to the STMS server.
However, when an NE is already discovered and its certificate is changed, you must perform this operation
so that the STMS will load the new NE public key to its server.
To load the NE public key to the STMS server:

1. Copy the NE public key file from a disk-on-key to the STMS server. The NE public key file must be
saved to <INSTALL_DIR>/data/security/certs, in the following file name format:
<NE IP address>_PublicKey.pem
For example: 172_18_212_189_PublicKey.pem
2. Select Security > Load NE Public Key.
The Load NE Public Key window opens.
3. Click Select.
The Certificate List window opens.
4. Select the NE public key file and click OK.

The file name appears in the File Name field of the Load NE Public Key window. If you selected more
than one file, Multiple appears for the file name.
5. Click OK.
The NE public key is loaded to the STMS server.
2.24.5 Create a new NE certificate
You can send a command from the STMS to instruct an NE to create and activate a new certificate for itself.
To create a new certificate for an NE:

 In the Network Explorer tab, right-click the NE and select Security > Create Key-Pair.
The Create Key-Pair command is sent from the STMS to the NE. The NE creates a new certificate for
itself.
The STMS then sends a command to the NE instructing it to start using the new certificate. After the
NE acknowledges the command, the value is copied from New to Current (by both the NE and STMS)
and starts being used by the STMS for SSL communication with the NE.
2.24.6 Manually activate a new NE certificate

In rare cases where a new NE certificate is created, but the NE does not start using the new certificate
automatically (Start Using New Key-Pair command from STMS failed or other reason), you can manually
send the command from the STMS.
To instruct an NE to start using its new certificate:

 Right-click the NE and select Security > Start Using New Key-Pair.
The STMS sends a command to the NE to start using its new certificate and the new STMS public key
(if exists).
2.24.7 View the Peer IPs table

For data encryption, NEs have to authenticate themselves when sending messages to other NEs. Each NE
stores a list of peer IPs containing the public key of each NE from which it can receive encrypted messages.
The Peer IPs table contains entries created and updated by the STMS for the NE automatically. The table
shows whether each peer IP is in use, and whether the peer public key is consistent with the value of NE
public key stored by the STMS (for the peer IP). If the public key is inconsistent, you can fix this
inconsistency via the Resolve option.
To view the Peer IPs table:

 In the Network Explorer tab, right-click the NE and select Security > Peer IPs Table.
The Peer IPs Table window opens.
 To delete entries from the table, select the relevant entries and click Delete.
 If the peer public key is inconsistent with the value of the NE public key stored by the STMS for
the peer IP (No appears in the Peer Public Key Consistency column), click Resolve to fix the
inconsistency.
2.25 Commissioning tool

The Commissioning tool enables the STMS to configure NEs. It can configure newly discovered elements or
elements that are already configured.
The Commissioning tool performs the following functions:
 Configures routing and signaling protocols
 Configures OSPF areas
 Configures IS-IS area
 Configures Router IDs and loopback addresses
 Creates LAGs
 Assigns NNI ports
 Creates LSP pairs
NOTE: IS-IS configuration and monitoring is supported for the SR9700 and is presently not
available for the SR9600.
When the Commissioning tool is launched, a persistent commissioning session is created. All transient
information that is captured using the tool is saved while navigating to the next window. A persistent
session enables you to start where you left off. If a previously created session exists, you can decide
whether to delete it and create a new session or to continue with the previous session.
2.25.1 Access the Commissioning tool
To access the Commissioning tool:
 On the STMS menu bar, select Tools and then Commissioning Tool.
 If no commissioning session is in progress, the Select Network Elements For Commissioning
window opens.
 If a commissioning session is already in progress, the following window opens.
You have the option to delete the old session and create a new session, or continue with the
previous session.
NOTE: When typing data in the following windows, remember to end each input by pressing
TAB or ENTER. Otherwise, the input may be ignored.
2.25.2 Select NEs for commissioning

All discovered devices are listed in this window. Global Routing and Signaling protocols are selected. The
option to create LAGs is also available.
The Status column indicates the device configuration status and can be one of the following:
 READY: NE does not have any configuration. This NE can be configured using the CT.
 CONFIGURED: NE is already configured. This NE can be reconfigured using the CT.
 UNAVAILABLE: Cannot be configured using the CT.
 UNKNOWN: Cannot be configured using the CT.
To commission NEs:
1. Click the Select checkbox alongside each NE you want to commission in this session.
2. Select either OSPF or IS-IS as the Global Routing Protocol.
3. (Optional) Select either RSVP or LDP, or both, as the Global Signaling Protocol.
4. If you want to create LAGs, select the Create Link Aggregates checkbox.
5. Click Next.
 If you chose OSPF in Step 2, the OSPF Area Configuration window opens.
 If you chose IS-IS, the IS-IS Configuration window opens.
NOTE: If you selected a routing protocol (OSPF or IS-IS) and entered some data in CT before
completing the commissioning session, reselecting a different routing protocol in this window
causes the following:
 A message popup warns you that any previous inputs for this session will be lost.
 Once the warning is confirmed, STMS drops the old commissioning session and creates a
new one.
This ensures that the NNI is NOT configured for both routing protocols in the same
commissioning session.
2.25.3 Routing protocol configuration (commissioning)

OSPF Area Configuration
The following window opens if you selected OSPF as the global routing protocol. This window allows you to
create, configure, or remove OSPF areas for commissioning.
Existing areas belonging to configured NEs are automatically displayed in this window. New areas can be
added or removed by clicking the New or Remove buttons. At least one area must exist.
The following items can be configured:
 Area Types: NORMAL, BACKBONE, STUB, and NSSA. Area 0.0.0.0 can only be a backbone.
 Authentication types: NONE, SIMPLE, or MD5. Simple and MD5 require an authentication key which
can be up to 16 characters wide.
 BFD and Strict flags can be checked as appropriate. (Note: If you select BFD and BFD is not configured
on an NE, it is configured with defaults of Minimum Receive Value = 50, Minimum Transmit Interval =
50, and Multiplier = 3.)
 Check the Preferred checkbox to select an area as the default area.
NOTE: You must select one and only one preferred area. The preferred area becomes the
default area assigned to all ports.
Click Next to continue. The General Router Settings window opens.

IS-IS Area Configuration

The following window opens if you selected IS-IS as the global routing protocol. Use this window to create,
configure or remove IS-IS configurations for commissioning.
The Authority and Format Indicator (AFI) and Area ID columns are populated from all the existing ISO
addresses on loopback interfaces on configured NEs.
New AFIs and areas can be added or removed by clicking the New or Remove buttons.
The following items can be configured in this window:
 Authentication types can be set to MD5, SIMPLE, or NONE.
 Authentication Key: required if Authentication type is specified as MD5 or SIMPLE and automatically
removed if the Authentication type is specified as NONE.
NOTE: The Authentication Type and Authentication Key defined here configure the
Authentication Type and Authentication Key for the IS-IS Global level and the IS-IS Level 1 and
Level 2. Authentication for the IS-IS Interface and IS-IS Interface Level can be defined during
the NNI Port Configuration. See NNI Port Configuration (Commissioning).
 Preferred: Check to select an IS-IS area as the default Area Prefix for address.
 BFD and Strict flags can be checked as needed. (Note: If you select BFD and BFD is not configured on
an NE, it is configured with defaults of Minimum Receive Value = 50, Minimum Transmit Interval = 50,
and Multiplier = 3.)
NOTE: You must select one and only one preferred address, which then becomes the default
assigned to all ports.
Click Next to continue. The General Router Settings window opens.

2.25.4 General router settings (commissioning)
The General Routing Settings window has one row for each NE being commissioned.
To commission an NE in the General Routing Settings window (OSPF

global routing protocol):
1. Enter a Router ID for each row. The Router ID becomes the default Loopback Address.
2. Enter a Loopback Address if different from the default.
3. Enter a subnet mask, an integer between 1 and 32.
4. Select an OSPF area for this router.
NOTE: One of the OSPF areas contains the prefix Pref. When selected, the preferred area is
always assigned to the router, even if the preferred area changes.
To commission an NE in the General Routing Settings window (IS-IS

global routing protocol):
1. Enter a Router ID for each row.
2. Enter a Loopback Address if different from the default.
3. Enter a subnet mask, an integer between 1 and 32.
4. Select an Area Prefix from the dropdown list. This is a combination of the AFI (1 byte) and Area ID (2
bytes) columns of the previous window. The preferred area prefix is selected by default.
5. Enter a System ID (6 to 10 bytes in format: xxxx.xxxx.xxxx.xxxx.xxxx).
6. Enter a Selector (2 bytes).
7. Loopback ISO Address is a read-only cell that is automatically populated from Area Prefix, System ID,
and Selector. The ISO address values are validated upon leaving this wizard window.
8. Select a Level setting (1, 2, or both) from the dropdown list. IS-IS is configured only on the level(s)
specified.
9. Click Next to continue. If you chose to create LAGs in this commissioning session, the Link
Aggregation window opens. Else the NNI Port Configuration window opens.
2.26 NE Credentials tool

The NE Credentials tool can be used to send basic bootstrap configuration to 9200 devices, allowing STMS
to establish CLI communication with them.
The tool allows you to create different profiles and to map the profiles to a range of IP addresses. This
enables you to send a profile to many devices simultaneously.
2.26.1 Access the NE Credentials tool
To access the NE Credentials tool:
 From the STMS menu bar, select Tools > NE Credentials.
The NE Credentials window opens.
2.26.2 Create an NE profile
NOTE: The STMS_DEFAULT profile is created automatically. It can't be deleted. It can only be
modified.
To create an NE profile:
1. From the STMS menu bar, select Tools > NE Credentials.
2. Click the Add button.
The Create NE profile window opens.
3. Define the parameters as required. For example, if the profile is intended for slower devices, set
SNMP timeout or SNMP Retries to higher values.
4. Click Create.
The NE profile is created.
NOTE: When creating new profiles, you need the Name and Password for a CLI user on the
device. You may also need the Privileged Mode password. For the default passwords, contact
the Customer Support team.
2.26.3 Edit an NE profile

To edit an NE profile:
2. Select the profile row and click Edit.
3. Change the parameters as required.
4. Click Update.
5. If this profile is currently mapped, you are prompted to apply the changes to the mapped devices.
2.26.4 Delete an NE profile
To delete an NE profile:
2. Select the profile row and click Delete.
The NE profile is deleted.
2.26.5 Map an NE profile

From the middle section of the NE Credentials window, you can map NE profiles to an IP address or to an IP
address range.
The IP address range can be any followed by a netmask. Ranges may be specified as "a-b", where "a"
represents the start of the range and "b" represents the end. The netmask is an integer from 1-32.
For example, 10.0.232.20-24/27 specifies a range of addresses that includes 10.0.232.20, 10.0.232.21,
10.0.232.22, 10.0.232.23, and 10.0.232.24.
To map a profile to an address or address range:

2. In the NE Profile Mappings area, click Manage.
The Manage Profile Mappings window opens.
3. Click Add.
The Create NE Profile Mapping window opens.
4. In the IP Address Range field, enter an IP Address or IP Address range.
5. Click Create.
6. In the Manage Profile Mappings window, click OK. You are prompted to choose whether to apply the
profiles to NEs that were affected by the new profile mappings.
NOTE: One profile can have many different mappings. However, the mappings cannot have
overlapping IP addresses.
2.26.6 Apply the NE profile mapping

To apply the profile to the mapped devices:
1. In the NE Profile Mappings table in the NE Credentials window, select the checkbox in the row that
you want to apply.
2. Click the Apply button. The Apply Selected Profiles to Devices window opens.
3. Select one of three options:
 Apply selected profiles to ALL IP addresses within the ranges.
 Apply selected profiles to DISCOVERED IP addresses within the ranges.
 Apply selected profiles to UNKNOWN IP addresses within the ranges.
4. Click OK.
You can also apply profiles to mapped ranges by using the NE Profiles list at the top of the NE Credentials
window.
5. Right-click the profile row you want to apply.
6. Click Apply Profile to mapped devices to apply the profile to all devices that it is presently mapped to.
OR
Click Apply Mapped Profile to IP Address or Range. The Apply Mapped Profile to IP Address window
opens.
 Enter the IP Address or range.
 Click OK. The profile is applied to the device(s) matching the IP Address or in the IP Address
range.
NOTE: If you enter an address or address range that is not currently mapped to this profile,
the STMS_DEFAULT profile is sent to those addresses.
2.26.7 Remove an NE profile mapping

To remove a profile mapping:
2. In the NE Profile Mappings area, click Manage.
The Manage Profile Mappings window opens.
3. Select the checkbox in the row of the mapping that you want to remove, and click Remove.
4. Click OK to save changes.
2.26.8 Send bootstrap configuration to 9200 devices
To send bootstrap configuration to 9200 devices:
1. Create NE profiles. (Perform this step only if you need a configuration that is different from the
default.)
2. Map the NE profiles to an address or address range.
3. Apply the NE profiles to the devices.
2.27 NE configuration backup and restore

You can create backups of one or more NE's configuration information. Backups are stored in the STMS
database.
Using the Configuration Manager, you can:
 Schedule recurring backups to start at any time hourly, daily, or weekly, schedule a one-time backup,
or start an immediate backup.
 View the details of an existing backup.
 Suspend a scheduled backup, resolve schedule conflicts automatically, and audit backup and restore
events.
 Compare the details of two backups of the same NE (or two NEs of the same type) and view the
differences between them.
NOTES:
 For the OPT96xx: This feature requires that a Secure Shell/Secure Copy (SSH/SCP) or File
Transfer Protocol (FTP) service be running on the computer that is hosting the STMS
server, and that the host's firewall allows connections to that service.
 For the 9200 series: This feature requires that Trivial File Transfer Protocol (TFTP) be
running on the computer hosting the STMS server.
 The user name and password to use for accessing this service must also be configured as
STMS Domain properties. See View STMS Domain properties.
2.27.1 Define the backup file directory

The default directory for the network configuration backups on the STMS server is:
/opt/STMS/data/deviceConfig
You can change the directory as required.
To define the backup file directory:
1. From the Edit menu, select Server Preferences.
2. In the General tab, delete the file directory defined in the Network Element File Directory field, and
enter the new directory.
3. Click Apply.
The new file directory is defined.
2.27.2 Perform an immediate network configuration backup

To perform an immediate backup of the network configuration (1):
1. From the main menu, select Tools and then select Configuration Manager.
The Configuration Manager window opens.
2. In the Backup Scheduler tab, click the Create button. The Create Schedule window opens.
a. Select the Start Immediately checkbox.
b. Enter a label to identify this backup.
OR
3. In the Backup Manager tab, click the Create button. The Create System Configuration Backup
window opens.
(Optional) Enter a label to identify this backup.
4. In the Select the NEs to backup pane, select the checkbox corresponding to the NE(s) you wish to
back up.
5. Click OK.
6. Click Yes.
The backup begins immediately.
7. To view the results of the backup, check the bottom of the Configuration Manager window or the NE
Event Logs.
See Viewing a Network Configuration Backup.
To perform an immediate backup of the network configuration (2):
1. Right-click the NE you wish to back up, and select Actions.
2. Select Backup Configuration Now.
The STMS automatically backs up the configuration of the NE you have selected.
2.27.3 Schedule a network configuration backup

To schedule a backup of the network configuration:
1. From the main menu, select Tools, and then select Configuration Manager.
The Configuration Manager opens.
2. Select the Backup Scheduler tab, and then click the Create button. The Create Schedule window
opens.
OR
Right-click the NE you wish to back up:
a. Select Actions.
b. Select Schedule Configuration Backup. The Create Schedule window opens.
3. From the Start Time dropdown lists, enter the month, day, year, and time the backup must first be
run.
4. From the Interval list, select the desired time interval.
5. Enter a label to identify this backup.
NOTE: If the label you specify is a duplicate of another active schedule's label, an error
message appears.
6. In the Select the NEs to Backup pane, select the checkbox corresponding to the NE(s) you want to
back up.
7. Click OK.
8. Click Yes.
The backup begins at the scheduled time.
To view the results of the backup, check the bottom of the Configuration Manager window or the NE Event
Logs.
See View a network configuration backup.
2.27.4 View all network configuration backups
To view network configuration backups:
2. Click the Backup Manager tab.
2.27.5 View a network configuration backup

To view a specific network configuration backup:
3. Click one of the NE backups listed. The configuration information appears in the View Configuration
window.
2.27.6 View the network configuration backup log

To view the network configuration backup log entries:
2. Click the NE Event Logs tab.
3. Click the Filter button. The NE Event Log Filter window opens.
4. Check the Type checkbox.
5. From the corresponding dropdown list, select configuration archive to view configuration backup
logs. Or select scheduled archive to view scheduled backup logs.
6. Click Apply.
2.27.7 Suspend a scheduled network configuration backup

You can temporarily defer a scheduled backup. A suspended scheduled backup is not performed until it is
resumed. See Resume a scheduled network configuration backup.
To suspend a network configuration backup:

2. Click the Backup Scheduler tab if it is not already active.
3. Right-click the backup schedule you want to suspend from the list, and select Suspend from the
shortcut menu.
NOTE: If the backup is set for "once", it cannot be suspended.
4. Click Yes to confirm. The backup schedule is suspended. You can confirm the suspension by viewing
the log. See View a network configuration backup.
2.27.8 Resume a scheduled network configuration backup

You can resume a scheduled backup that was suspended. The scheduled backup is performed at its next
scheduled time.
To resume a network configuration backup:

3. Right-click the backup schedule you wish to resume from the list, and select Unsuspend from the
menu. The backup schedule is resumed. You can confirm the resumption by viewing the log. See View
a network configuration backup.
2.27.9 Monitor the network configuration backups

You can monitor the status of a network configuration backup in real time by observing the network
configuration backup log entries. See View the network configuration backup log.
2.27.10 Edit a network configuration backup

You can edit an existing backup. A scheduled backup is not processed while it is being edited.
To edit a scheduled backup of the network configuration:

3. Right-click the backup schedule you wish to edit, and select Edit from the menu. The Edit Schedule
window opens.
4. (Optional) Using the Start Time dropdown lists, change the month, day, year, and time the backup
should be run.
NOTE: If the backup is set for "once", you cannot edit its interval.
5. (Optional) In the Select the NEs to Backup pane, select the checkbox corresponding to the NE(s) you
wish to back up.

6. Click OK.
7. Click Yes.
The backup begins at the scheduled time.
8. To view the results of the backup, check the bottom of the Configuration Manager window or the NE
Event Logs.
2.27.11 Delete a network configuration backup schedule

To delete a network configuration backup schedule:
1. From the main menu, select Tools and then select Configuration Manager.
3. Right-click the backup schedule(s) you wish to delete from the list, and select Delete from the menu.
4. Click Yes to delete the backup schedule(s).
2.27.12 Sort the network configuration backups

You can sort the list of scheduled backups. You can sort the list by any of the headers shown in the list of
backup schedules.
To sort the scheduled network configuration backups:

3. Click any of the list headers to sort.
2.27.13 Verify a network configuration backup

You can verify that a network configuration backup was processed by viewing the NE Event Logs. See View
the network configuration backup log.

2.27.14 Delete a network configuration backup
To delete a network configuration backup:
2. Click the Backup Explorer tab.
3. Right-click the NE backup you wish to delete, and from the menu select Delete.
4. Click Yes to confirm.
The backup is deleted.
2.27.15 Compare network configuration backups

You can compare the details of two backups of the same NE and view the differences between them.
To compare the contents of two network configuration backups:

3. Right-click an NE backup you wish to compare, and select Diff... The Configuration Diff window opens.
4. From the dropdown list, select another configuration backup to compare.
5. Click OK. The configuration differences are displayed.
2.27.16 Save a network configuration backup to a file

To save the contents of a network configuration backup to a text file:
3. Right-click the NE backup you wish to save to a text file, and select Export from the menu.
The Save window opens.
4. Select the directory where you want to save the file, and enter a file name.
5. Click Save.
The backup is saved to a text file.
2.27.17 Restore an NE configuration backup
A network configuration backup can be restored to the NE. It can only be restored to the NE from which it
originated.
To restore the contents of a network configuration backup to the

originating NE:
3. Right-click the NE backup you wish to restore, and select Restore from the
menu. A confirmation message appears.
4. If you want to reboot the NE after configuration is restored, select the Reboot upon completion
checkbox.
5. Click Yes to confirm.
The backup is restored to the originating NE.
To automatically restore the contents of a network configuration backup

to the originating NE:
 Right-click the NE on which you wish to restore the backup configuration, and from the menu, select
Actions and then Restore Last Configuration.
The STMS automatically restores the latest backup for the NE you have selected.
2.27.18 Restore a selected configuration

If you have multiple configurations, you can choose which configuration to restore on an NE.
To restore a selected configuration on an NE:

1. Right-click the NE on which you want to restore configuration.
2. Select Actions and then Restore Selected Configuration.
The Restore Selected Configuration window opens.
3. Select the NE backup from the list you wish to restore, and click OK.
2.28 NE event logs
The NE event logs contain a list of transactions recording changes to the NEs.
A log is entered in the event logs when one of the following occurs:
 Discovery of an NE - Success or Failure
 Changes to an NE - Reachable or Unreachable
 Results of NE Profile apply operations - Success or Failure
 Results of software apply operations
 Results of Backup operations - Success or Failure
 Results of Backup schedule - Started, Completed, or Failed
 Results of Backup restoration - Success or Failure
2.28.1 View NE event logs

To view the NE event logs:
The list of NE event logs appears in the Live tab. This shows a list of NE event logs with the following
properties:
 The list automatically updates whenever a new NE event occurs.
 The list is always sorted by time in descending order. You cannot sort this list any other way.
 The list includes NE Event Logs since STMS was installed or since the last purge command,
whichever was later.
 The list contains a maximum of 1000 records. Records are maintained in a First In First Out
(FIFO) method. So if the number of records exceeds 1000, the oldest records are discarded.
 Severities are highlighted in color as follows:
 Red - CRITICAL or WARNING
 Orange - MAJOR
 Yellow - MINOR
3. Right-click the row and click View Details to show event details which are too lengthy to display in a
column.
2.28.2 Filter the NE event logs list
To filter the NE event logs list:
3. In the Query tab, click Filter.
The NE Event Log Filter window opens.
This window contains eight different filters, one for each column. The following conditions apply:
 You must select the checkbox next to each filter before it can be applied.
 If more than one filter is selected, the selected filters are applied in an "AND" operation.
For example, in the window above, the Type and IP Address filters are selected. Therefore, the
list contains only Event Logs that have a type of "ne discovery" and have an IP Address in the
range of 10.0.232.20-24/27.
 To remove the filter, clear all the checkboxes and click Apply. This returns the full list of NE
Event Logs.
2.28.3 Define the number of logs per page

You can define the number of logs that appear in the NE event logs list.
To define the number of logs per page:

3. In the Query tab, click Filter.
The NE Event Log Filter window opens.
4. In the Paging Size field, enter the new number of logs.

5. Click Apply.
2.28.4 Purge NE event logs

To purge NE events logs:
3. In the Query tab, click the Purge button.
The Purge window opens.
4. Select a date and time, and then click OK.
All logs from before than the selected date/time are purged. Purged logs are exported to an XML file
on the server. Upon completion, a message with the path to this file appears.
2.28.5 Export NE event logs to an XML file

To export event logs to an XML file:
3. In the Query tab, click Export.
4. Save the XML file to the relevant directory.
2.29 ASON/WSON configuration
OPTIONAL FEATURE: Automatic Switched Optical Network (ASON) and Wavelength Switched
Optical Network (WSON) protection are available in the STMS on a cost basis. To ensure
ASON/WSON restoration is supported, verify that the purchased license is current and has not
exceeded its token limits (see Manage licenses in the STMS Getting Started and
Administration Guide).
The Apollo platform supports the implementation of ASON and WSON protection. ASON- and WSON-
protected trails are created in LightSOFT and managed via the GMPLS Control Plane. The Control Plane is
capable of establishing LSPs comprising ODUk XCs or OCH XCx and can create, delete, manage, and protect
the LSPs.
The STMS manages the ASON/WSON trail on the NE-level only, and mainly provides support for LightSOFT
management of the ASON/WSON trails.
The STMS receives and handles notifications about the creation, deletion, and modification of ASON
attributes on OTUk ports and WSON attributes on OTS ports.
2.29.1 View ASON/WSON Control Plane attributes

Where ASON/WSON support is employed on the network, XCs and their sub-interfaces can be owned by
the Control Plane or by the management plane (LightSOFT, STMS, or ShadeTree CLI). Resources controlled
by the Control Plane can only be managed (created, deleted, or modified) by the Control Plane.
To view ASON/WSON Control Plane attributes:

2. Select the CP Attrs tab.
The Control Plane attributes appear. See the table below for a description of the attributes.
Table 2-2: Control Plane attributes

Attribute Description
GMPLS Mode Defines whether ASON or WSON is enabled for the NE.
Inhibit GMPLS If set to Yes, it prevents ASON/WSON protection from switching to
this restoration path. Only relevant if GMPLS Mode is set to ASON or
WSON.
CP Router IP Address (read-only) IP address of the Control Plane DCN
2.29.2 View ASON/WSON Control Plane protocol attributes

To view ASON/WSON Control Plane protocol attributes:
2. Select the CP Protocols Attrs tab.
NOTE: The CP Protocols Attrs tab only appears if GMPLS Mode is set to ASON or WSON.
The Control Plane protocol attributes appear. See the table below for a description of the attributes.
All of the attributes, except Signaling Recovery Time, are read-only.
Table 2-3: Control Plane protocol attributes

RSVP-TE Signaling
Hello Interval The time interval (in seconds) between RSVP-TE signaling hello
messages.
Signaling Refresh Interval The time interval (in seconds) between RSVP-TE refresh
messages sent to upstream or downstream next hop (in
seconds).
Clear-out Multiplier The Signaling Refresh Interval is multiplied by the Clear-out
Multiplier to define the time period in which refresh messages
can be received for the LSP. If no refresh message is received
for the LSP during this time period, the CP controller tears
down the LSP.
Signaling Recovery Time The time period during which the restarted device can get
recovery information from its neighbors.
No. of Retry Restoration Intervals The number of intervals that the NE attempts to restore the
trail.
No. of Restoration Attempts in One Retry The number of times that the NE attempts to restore the trail
within one interval.
Retry Restoration Time Interval The time period (in seconds) between restoration attempts.
Data Link WTR N/A
OSPF-TE
Hello Interval The time interval (in seconds) between OSPF-TE hello
messages.
Link State Advertisement Refresh Time The time interval (in seconds) between OSPF-TE refresh
messages.
Minimum Link State Advertisement The minimal time interval (in seconds) between two LSA
Interval messages about the same TE-link.
TE Metric The type used as TE metric. Must be the same for the entire
network.
 For ASON: Hop Count, Cost, or Length
 For WSON: Hop Count, Cost, Length, or OSNR
2.29.3 View ASON/WSON port parameters

ASON/WSON port parameters are defined in LightSOFT and inherited by the STMS. From the STMS, you can
only view these parameters (which are read-only).
To view ASON/WSON port parameters:

1. In the Network Explorer tab (or in Chassis view), right-click the relevant port (OTUk port for ASON or
OTS port for WSON) and select Properties.
The port properties appear.
2. Select the GMPLS Parameters tab.
The ASON/WSON port parameters appear. See the tables below for the parameter descriptions.
Table 2-4: ASON port parameters

Network Interface Type Network interface type. Possible values: NNI, UNI, None.
Only NNI ports can be the endpoints of ASON data link. All other ASON fields
only contain meaningful data when the network interface type is NNI.
Remote NE ID NE ID of the remote NE.
Remote Port ID Port ID for the ASON port on the remote NE.
Data Link EndPoint If the port is a TE-Link endpoint (i.e. the TE-Link exists in the NE) and there is
no mismatch between peer IDs on both ends of the TE-Link, the value should
be Yes. In all other instances, the value should be No.
Data Link Operational State Operational state value of the TE-Link entity with an endpoint on this port (Up
or Down).
Tributary Slot Type Bandwidth of each tributary slot.
SRLGs List of strings corresponding to the SRLG values of the ASON Data Link
connected to the port.
Auto Discovery State Indicates whether discovery has been performed on the NE.
Auto Discovery Indicates whether NE remote NE discovery is enabled/disabled.
Data Link Cost Value of cost metric.
Data Link Length Value of link length.
ASON XC Defined Indicates whether an ASON XC has been created on the port.
Supported ODU Types ODU rates supported for the selected port.
Table 2-5: WSON port parameters

Network Interface Type Network interface type. Possible values: NNI, UNI, None.
Only NNI ports can be the endpoints of WSON data link. All other WSON fields
only contain meaningful data when the network interface type is NNI.
Remote NE ID NE ID of the remote NE.
Data Link EndPoint If the port is a TE-Link endpoint (i.e. the TE-Link exists in the NE) and there is
no mismatch between peer IDs on both ends of the TE-Link, the value should
be Yes. In all other instances, the value should be No.
Remote Port ID Port ID for the WSON port on the remote NE.
SRLGs List of strings corresponding to the SRLG values of the WSON Data Link
connected to the port
Data Link OSNR OSNR WSON data link.
Data Link Cost Value of cost metric.
Associated OSC ID(s) List of up to two OSC ports associated with the OTS port.
Data Link Operational Operational state value of the TE-Link entity with an endpoint on this port (Up
State or Down).
2.29.4 View the ASON/WSON Trails list

If there is at least one ASON/WSON trail with a head-end residing in the Control Plane of the NE, the ASON
Trails or WSON Trails folder appears in the Network Explorer tab, below the cards. ASON/WSON trails are
created and managed in LightSOFT. From the STMS, you can only view the trails and their parameters
(which are read-only).
To view the ASON/WSON Trails list:
 In the Network Explorer tab, click the ASON Trails or WSON Trails folder for the relevant NE.
The ASON/WSON Trails list appears in the right pane, showing the ASON/WSON trails and their
parameters.
See the table below for the parameter descriptions.
Table 2-6: NE ASON/WSON trail parameters

Trail Name Name of the ASON/WSON trail
Alarm Status Indicates the number of critical, major, and minor alarms on the trail
Trail ID ID of the ASON/WSON trail
NMS Trail ID ID of the NMS trail associated with the ASON/WSON trail, as defined in
LightSOFT
Trail Rate (ASON only) Rate of SNC of the trail (ODUk)
Bandwidth (WSON only) Bandwidth of the trail (10G, 40G, 100G), based on the XC rate
Wavelength (WSON only) Frequency in which the trail is created
Alarm Severity Profile Alarm severity profile of the trail
2.29.5 View the GMPLS Control Channels list
To view the GMPLS Control Channels list:
 In the Network Explorer tab, click the GMPLS Control Channels folder below the relevant NE.
NOTE: The GMPLS Control Channels folder only appears if the GMPLS Mode attribute is set
to ASON or WSON.
The GMPLS Control Channels list appears in the right pane. See the table below for the parameter
descriptions.
Table 2-7: GMPLS Control Channel parameters

Remote CP IP Address IP Address of the remote CP Routing Instance. Specifies the other end of
ASON/WSON data Link.
Operational State ASON or WSON data link state.
Alarm Status Indicates the number of critical, major, and minor alarms on the control
channel.
Alarm Master Mask Indicates whether the alarm master mask is enabled/disabled. It is disabled
by default.
Note: To enable the alarm master mask, you must create a custom severity
profile for the protection group, and set the reporting to False for the
alarms that you do not want to view.
Alarm Severity Profile Alarm severity profile of the control channel.
2.29.6 View XC resource ownership
XC resources are owned by the Control Plane (CP), or by the Data Management Plane (Mgmt) except in the
following circumstances, where they are co-owned:
 When LightSOFT migrates a trail from non-ASON to ASON, or from ASON to non-ASON. During
migration the resources are co-owned. However, when the migration process is complete, the
resources remain with a single owner (Control Plane or Management, as applicable).
 When LightSOFT migrates a trail from non-WSON to WSON, or from WSON to non-WSON. During
migration the resources are co-owned. However, when the migration process is complete, the
resources remain with a single owner (Control Plane or Management, as applicable).
 When STMS must release a resource that is owned by the Control Plane, and there is no other way to
release the resource (e.g., the Control Plane controller is not reachable), the STMS 'takes over' the
resource by adding the Management as a resource owner, and then removing the Control Plan as co-
owner. The resource can then be modified or deleted.
To view XC resource ownership details:

1. Right click the NE icon in the Network Explorer tab and select Show XCs.
The XC Manager window opens, showing the XCs defined for the NE.
2. In the Results area, the XC Owners field shows the owner per resource. Values are either:
 Mgmt: XCs owned by the Data Plane only
 CP: XCs owned by the Control Plane only
 Mgmt & CP: XCs owned by both the Management and Control Planes
2.29.7 Define auto-discovered ASON data links
You can define ASON data links that can be auto-discovered in LightSOFT.
To define auto-discovered ASON data links:

1. Create bidirectional, external fiber connectivity for the relevant OTU ports (see Define fiber
connectivity).
2. In the Properties > GMPLS Parameters tab of each OTU port, select NNI for the Network Interface
Type, and click Apply.
NNI configuration is enabled for the OTU ports.
3. In the Properties > GMPLS Parameters tab of each OTU port, select Enable for the Auto Discovery
field.
Auto-discovery is enabled. The Received Remote NE ID and Received Remote Port ID appear.
These attributes are sent to LightSOFT. If successful, the auto-discovered data link can be created
from LightSOFT (see the LightSOFT User Guide).
NOTE: Auto-discovery must be enabled in LightSOFT. See the LightSOFT User Guide.
2.30 Synchronize the standby RCP configuration
In a dual RCP system, you can manually synchronize the configuration file on the active RCP with the
configuration files on the standby RCP.
NOTE: If you enable automatic RCP switchover, you can also enable automatic configuration
synchronization (automatically synchronizing the configuration files on the active and standby
RCPs). See Configuring RCP Redundancy.
To manually synchronize the configuration files on the active and

standby RCPs:
1. In the Network Explorer tab, right-click the NE for which you want to synchronize the configuration
files and select Actions > Synchronize Standby RCP Configuration.
The Synchronize Configuration window opens.
2. Click Yes.
2.31 Define utilization thresholds

You can define several utilization thresholds for an NE. If the NE exceeds the percentage specified by a
threshold, an alarm is generated.
The following table describes each of the utilization thresholds.
Table 2-8: Utilization thresholds

Threshold Description
CPU Percentage of CPU resources that can be used before a CPU utilization alarm
is generated, range from 1 to 100 percent (default 90).
Memory Percentage of memory resources that can be used before a memory
utilization alarm is generate, range from 1 to 100 percent (default 90).
File system Percentage of file system resources that can be used before a file system
utilization alarm is generated, range from 1 to 100 percent (default 90).
To define the utilization thresholds for an NE:

1. In the Network Explorer tab, right-click the NE for which you want to change the control protocols
service profile, and then select Properties. The property sheet for the NE opens.
2. In the Properties tab, in the corresponding fields, type valid values for the utilization thresholds.
3. Click Apply.
2.32 Configure a subtending shelf
NOTE: Adding a subtending shelf is not traffic-affecting.
To configure a subtending shelf:

1. In the Network Explorer tab, right-click the NE on which you want to add a subtending shelf, and
select Assign shelf.
The Assign shelf window opens.
2. Select the subtending shelf ID, Artemis shelf type, and the shelf mode.
3. Enter a description of the shelf (optional).
4. Enter a rack number and the position in the rack.
5. Click Finish to save.
NOTE: All XCs and associated trails must be deleted prior to the deletion of a subtending
shelf.
NOTE: Removing a subtending shelf does not cause a service interruption to other shelves
within the same multi-shelf NE.
2.33 View the Maintenance List

You can view a list of the maintenance operations currently running on network objects (NEs, cards, ports).
The Maintenance List is only available for objects currently undergoing maintenance operations.
These objects appear with the maintenance icon in the Network Explorer pane.
To view the maintenance list for an object:
 Right-click on the object and select:
 NE Maintenance List - for an NE
 Maintenance List - for a card or port
NOTE: From Chassis view, you can select NE Maintenance List from the Maintenance menu.
This option is only available for NEs undergoing maintenance operations.
The Maintenance List window opens.

Figure 2-3: Maintenance List Dialog Box
3 Cards and modules
The STMS enables you to manage the configuration of the following Apollo cards and modules:
 Optical Components
 Layer 1 Service Cards
 Layer 1 Fabric Interface Cards
 Layer 2 Cards
 Pluggable Transceiver Modules
3.1 OPT99xx cards and modules

OPT99xx supports the following service cards:
 HIO10_20
 HIO100_2
 TIOMR_32
Additional cards and modules provide common functionality for OPT99xx. See OPT99xx Common Cards and
Modules.
For detailed descriptions of the supported OPT99xx cards and modules, see the Apollo Reference Manual.
3.1.1 HIO10_20
The HIO10_20 is a 10G multi-service interface card for the OPT99xx platforms that supports up to 20 client
interfaces, SFP+ based transceivers. Each port can be configured to OTU2, OTU2e, STM-64, OC-192, FC1200,
FC800, 40GbE, or 10GbE. Client-side signals are mapped to G.709 ODU-k and cross connected through the
central universal fabric to the egress side. Two additional client interfaces can be configured to 40 GbE.
These are QSFP+ based ports and the configuration of such interface is at the expense of four SFP+ ports.
The HIO10_20 provides a multi-service, cost-effective solution to customers for grooming 10G services over
OTN DWDM networks.
For more information about the HIO10_20 card, see the Apollo Reference Manual.

STMS User Guide Cards and modules
Table 3-1: HIO10_20 - Port Configuration Rules

Number of Port Label Port Number Port Role Port Type Sub-IF Type
Ports
22 0,1 0,1 Client/Line ETY40G ODU3
2-21 2-21 Client/Line  STM64  ODU2
 OC192  ODU2
 FC800  ODUflex-FC800
 FC1200  ODU2e
 ETY10GOC  ODU2e
 OTU2  ODU2 (PT21)
 OTU2e  ODU2e
 GE10  N/A
 GE10-OTU2e  N/A
IMPORTANT: The following exceptions apply when configuring HIO10_20 ports:

 If any port between 2-5 is configured, port 0 must be disabled.
 If port 0 is configured, ports 2-5 must be disabled.
 If any port between 6-9 is configured, port 1 must be disabled.
 If port 1 is configured, ports 6-9 must be disabled.
 GE10-OTU2e ports can only be configured as ports 12-21.
NOTE: To define the port configuration for a HIO10_20 card, see Configure ports.
3.1.2 HIO100_2
HIO100_2 provides an OTU4 uplink for the OPT99xx platforms. HIO100_2 also supports up to two 100G
ports in a single slot card with CFP pluggable optics. The client-side signals are mapped to G.709 ODU-k and
cross connected through the central universal fabric to the egress side.
The HIO100_2 provides a multi-service, cost-effective solution to customers for Metro, Regional, and Long
haul applications over OTN DWDM networks.
For more information about the HIO100_2 card, see the Apollo Reference Manual.

Ports
2 0 0 Client/Line  ETY100G  ODU4 - for ETY100G
 OTU4  ODU4 (PT21) - for
 GE100 OTU4
 GE-100-OTU4  N/A
 N/A
1 1 Client/Line  ETY100G  ODU4 - for ETY100G
 OTU4  ODU4 (PT21) - for
 GE100 OTU4
 GE-100-OTU4  N/A
 N/A
An LO sub-interface can be created under HO ODU4 of OTU4, and supports PT21: ODUF-GFP. It has mode =
L1 or L2.
ODUF-GFP L2 is created together with its associated VPP. If this VPP is the master, the LAG is also created at
the same time. If the VPP is the slave, it will be associated to an existing LAG.
Note: To define the port configuration for a HIO100_2 card, see Configure ports.
3.1.3 TIOMR_32
The TIOMR_32 is a multi-rate interface card for the OPT99xx platforms that supports up to 32 low-rate
client interfaces using SFP transceivers. Each port can be configured to STM-1, STM-4, STM-16,
FC100/FC200/FC400, or GbE. Client-side signals are mapped to G.709 ODU-k and cross connected through
the central universal fabric to the egress side.
The TIOMR_32 provides a multi-service, cost-effective solution to customers for grooming low-rate (< 10G)
services over OTN DWDM networks.
For more information about the TIOMR_32 card, see the Apollo Reference Manual.
Table 3-3: TIOMR_32 - Port Configuration Rules
Ports
32 0-31 0-31 Client  ETY1G  ODU0
 ETY1Ge  ODU1
 FC200
 FC400
 OC3
 OC3e
 OC12
 OC48
 STM1
 STM1e
 STM4
 STM16
IMPORTANT: The following exceptions apply when configuring TIOMR_32 ports:

 FC400 can only be configured for even ports (0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24,
26, 28, 30).
 The port following an FC400 port is not configurable. For example, if FC400 is configured
for port 2, you can't configure port 3.
 If an odd port is already configured, you can't configure FC400 for the port preceding it.
For example, if ETY1G is configured for port 7, you can't configure FC400 for port 6.
NOTE: To define the port configuration for a TIOMR_32 card, see Configure ports.
3.1.4 OPT99xx common cards and modules

The following cards and modules provide common functionality for OPT99xx:
 xRCP: the central control component in the OPT99xx platforms, providing the main system processor
responsible for essential system management, timing, and control. The card supports timing
functionality for a wide range of synchronization standards by the Central Timing Module (xCTM)
residing on it. In addition, xRCP cards include a Fabric Element (FE) used as part of the OPT99xx
system fabric.
 xFM: part of the universal fabric in OPT99xx platforms together with FEs residing on the xRCP cards.
 xMIM: the connection unit between the OPT99xx family and external management.
 xTAM: the timing and alarms connection unit between the OPT99xx platforms and the external world.
It provides interfaces for timing and alarms.
 xPFM: serves as an input power filter for the DC voltage connected to the OPT99xx.
 xFCM: has two types of fan trays that provide cooling air to the platform: xFCMV and xFCMH. The two
types have identical electronic design and cooling and control functionality, and differ only in physical
structure and number of fan units.
For more information about the OPT99xx common cards and modules, see the Apollo Reference Manual.
3.2 OPT9904X cards and modules

OPT9904X supports the MIO200 card, common cards and modules, and passive and photonic cards.
For detailed descriptions of the supported OPT9904x cards and modules, see the Apollo Reference Manual.
3.2.1 MIO200
MIO200 is a multipurpose ODU-XC base card with 100G CFP based uplink interface and up to 12 x SFP/SFP+
based client ports. The card is hardware ready for packet switching over OTN and 200G bandwidth.
The card throughput is 200 Gbps, and four cards together comprise a 800G mesh cross-connect, without
the need for a central matrix. MIO200 is a multi-rate IO card and supports 100G, 10G, and 1G clients.
NOTE: MIO200 is supported in the OPT9904X platform only.
The OPT9904X equipped with MIO200 cards provides a Multi-Service, low cost, minimal size sub 1T ODU-XC
solution to customers for grooming 10G and sub 10G services over the OTN DWDM networks.
For more information about the MIO200 card, see the Apollo Reference Manual.
Ports
1 0 0 Client/Line ETY100G ODU4
OTU4 ODU4 (P21)
12 P1-P12 1,…,12 Client/Line  ETY1G  ODU0
 ETY1Ge  ODU0
 FC100  ODU0
 FC200  ODU1
 FC400  ODUF-FC400
 FC1200  ODU2e
 FC1600  ODUF-FC1600
 OC3  ODU0
 OC3e  ODU0
 OC12  ODU0
 OC48  ODU1
 OC192  ODU2
 M-OTDR  N/A
 OTU2  ODU2
 OTU2e  ODU2
 STM1  ODU0
 STM1e  ODU0
 STM4  ODU0
 STM16  ODU1
 STM64  ODU2
NOTE: To define the port configuration for an MIO200 card, see Configure ports.
3.2.2 OPT99xx common cards and modules

The following cards and modules provide common functionality for OPT9904x:
 RCP04x: The central control component in the OPT9904X platform, providing the main system
processor responsible for essential system management, timing, and control. The card supports
timing functionality for a wide range of synchronization standards by the Central Timing Module
(xCTM) residing on it.
 PFM04x: An input power filter for the DC voltage connected to the OPT9904X and also protects the
equipment from external abnormal voltage connectivity. Each platform has two PFM04X units for
redundancy purposes.
 FCM04x: Positioned at the right side of the OPT9904X platform and provides cooling air to the system
from four separate fans. Air is drawn in by the fans from the right side of the chassis and pumped out
through the horizontally-mounted cards and modules through the left side of the chassis. FCM04X
includes a controller that controls the operation of the fans.
 TAMIM04x: The timing, alarms, and management connection unit between the OPT9904X platform
and the external world. It provides interfaces for timing, alarms and the external management. The
TAMIM04X is installed at the upper part of the OPT9904X.
For more information about the OPT9904x common cards and modules, see the Apollo Reference Manual.
3.2.3 Supported passive and photonic cards

Passive cards for the OPT9904X are supported only via an Artemis shelf.
Several OPT96xx photonic cards are supported in the OPT9904X platform, including:
 OA_LF
 OA_DLF
 OA_DLHF
 OLP_S2
 OMSP
 OTDR_8
3.3 OPT96xx layer 1 service cards

OPT96xx supports the following Layer 1 service cards:
 TR10_4
 TR10_4EN
 TR10_12
 TR10_12ULL
 TR100/TR100L
 TM100
 TM200EN
 TM100_2EN
 TM400
 AoC10/AoC10B
 AoC25/AoC25B
 CMR40B
 CMR100/CMR100L
 CMR100M
NOTE: For detailed descriptions of the supported Layer 1 service cards, see the Apollo
Reference Manual.
3.3.1 TR10_4
The TR10_4 is a 10 Gbps transponder card that maps the client signal according to G.709 and transmits a
colored signal towards the network.
The card includes two transponders (client and line) providing full functionality in a space saving form
factor and operating in an East/West configuration. Each one can be configured independently for
transponder or regenerator applications.
For more information about the TR10_4 card, see the Apollo Reference Manual.
Table 3-5: TR10_4 Card - Port Configuration Rules

Ports
2 C1, C2 0,2 Client  STM64  ODU2
 OC192  ODU2
 FC800  ODU2
 FC1200  ODU2f
 ETY10G  ODU2
 OTU2  ODU2
 OTU2e  ODU2e
2 L1, L2 1,3 Line OTU2/2e/2f ODU2/2e/2f
NOTE: To define the port configuration for a TR10_4 card, see Configure ports.
3.3.2 TR10_4EN
The TR10_4EN is a 10 Gbps transponder card with encryption capabilities. The card maps the client signal
according to G.709 to OTU2/ODU2e/ODU2f. The encryption is performed at the optical ODU2/2e layer,
using an encryption system and sends it to the line. The encryption system encodes the data with AES-GCM
256 algorithm to ensure a high security level. In addition to its main role as a transponder, the TR10_4EN
provides encryption on the optical (ODU2/e) layer.
The TR10_4EN provides the following encryption capabilities:
 AES256-GCM encryption with initialization vector and message integrity check
 Diffie-Hellman group 5 key exchange
 Encryption can be applied to any of its client-line interface mappings: 10G LAN to OTU2/2e, 10G WAN
STM-64 to OTU2/2e, FC8 to OTU2, and FC10 to OTU2f

For more information about the TR10_4EN card and its encryption capabilities, see the Apollo Reference
Manual. To define encryption settings for a TR10_4EN port, see Define encryption settings for TR10_4EN.
Table 3-6: TR10_4EN Card - Port Configuration Rules

Ports
2 C1, C2 0,2 Client  STM64  ODU2
 OC192  ODU2
 FC800  ODU2
 FC1200  ODU2f
 OTU2  ODU2
 OTU2e  ODU2e
2 L1, L2 1,3 Line OTU2/2e/2f ODU2/2e/2f
NOTE: To define the port configuration for a TR10_4EN card, see Configure ports.
3.3.3 TR10_12
The TR10_12 is a 10 Gbps transponder card that maps the client signals according to G.709 and transmits a
colored signal towards the network.
The card includes six transponders (client and line) providing full functionality in a space saving form factor
and operating in an East/West configuration. They can also be configured as six regenerators between the
line ports.
For more information about the TR10_12 card, see the Apollo Reference Manual.
Table 3-7: TR10_12 Card - Port Configuration Rules

Ports
6 C1-C6 0,2,4,6,8,10 Client  STM64/OC192  ODU2
6 L1-L6 1,3,5,7,9,11 Line OTU2/2e OTU2/2e
12 P0-P11 0,…,11 Client/Line  OTU2  ODU2
 OTU2e  ODU2e
 STM64/OC192  ODU2
 FC1200  ODU2e
NOTE: To define the port configuration for a TR10_12 card, see Configure ports.

3.3.4 TR10_12ULL
The TR10_12ULL is a 10 Gbps transponder card that maps the client signals according to G.709 and
transmits a colored signal towards the network. The card has 12 ports - four dedicated for ULL (Ultra Low
Latency) transponder channels with very low latency for FC16, FC12, and ETY10GOC clients. The other eight
ports can be configured as four independent transponders.
For more information about the TR10_12ULL card, see the Apollo Reference Manual.
Table 3-8: TR10_12ULL Card - Port Configuration Rules

Ports
12 P0-P11 0,…,11 Client/Line  OTU2  ODU2
 OTU2e  ODU2e
 FC1200  ODU2e
 ULL_FC1200  ULL-FC1200
 ULL_FC1600  ULL-FC1600
 ULL_ETY10GOC  ULL-ETY10GOC
NOTE: To define the port configuration for a TR10_12ULL card, see Configure ports.
3.3.5 TR100/TR100L
The TR100/TR100L transponder maps a 100 GbE client signal into a 100 Gbps colored line signal for WDM
network transport, according to the G.709 standard. It occupies a double slot in Apollo platforms.
The TR100/TR100L uses DP-QPSK modulation, a coherent receiver, DSP processing, and soft decision
forward error correction, for superior noise tolerance, and an exceptional ability to mitigate CD and PMD
impairments.
The TR100 is optimized for Ultra Long Haul networking applications, and the TR100L supports regional
applications. While the TR100L does not support single fiber bi-directional WDM operation, in terms of all
other capabilities, the cards are identical and they are interoperable with each other.
The TR100/TR100L can be used in regenerator applications when installed adjacent to another
TR100/TR100L card, or in add/drop mode with an IOP protection option. For regenerator applications the
TR100/TR100L is supported only in 9600 and only in slots 0, 2, 4, 6, 12, 14, 16, 18, 20, 22. Slots 8 and 10 are
not supported for regenerator applications.
For more information about the TR100/TR100L card, see the Apollo Reference Manual.
Card assignment of a TR100/TR100L card requires defining an additional mandatory attribute, Operation
Mode (see Card Assignment).
Table 3-9: TR100/TR100L Card - Port Configuration Rules

Ports
1 Client 1 Line ETY100G ODU4
1 Line 0 Client OTU4 ODU4
NOTE: To define the port configuration for a TR100/TR100L card, see Configure ports.
3.3.6 TM100
The TM100 is a 100G coherent transponder and muxponder card optimized for metro applications (up to
1200 km without regeneration). When assigned as a transponder (TR100M) the TM100 maps a 100 GbE
client signal into a 100 Gbps colored line signal for WDM network transport, according to the G.709
standard. In addition it can be configured as a muxponder in two modes: to multiplex 10 x 10 GbE clients
(MXP100E10) or to multiplex 2 x 40 GbE clients (MXP100E40).
During card assignment of the TM100 card, you must select one of the operation modes for the Card Type
(TR100M, MXP100E10, or MXP100E40).
For more information about the TM100 card, see the Apollo Reference Manual.
Table 3-10: TM100 Card - Port Configuration Rules

Operation Number of Port Label Port Number Port Role Port Type Sub-IF Type
Mode Ports
TR100M 1 Client 1 Client ETY100G ODU4
1 Line 0 Line OTU4 ODU4
MXP100E10 10 Client 1,,,,,10 Client ETY10GOC ODU2e
MXP100E40 2 Client 1,2 Client ETY40G ODU3
NOTE: To define the port configuration for a TM100 card, see Configure ports.
3.3.7 TM200EN
The TM200EN is a 200G Multi-Service, low cost, minimal size encrypted solution to customers for DWDM
networks that can be configured to operate with or without encryption. The card applications are used in
small regional or metro access networks requiring flexible grooming of 10G to OTU2 and 10G\100G
OTU4\OTUC2, encrypted or non-encrypted.
The TM200EN card can be configured to operate in two modes (expected types):
 TM200EN: for muxponder applications of N x 10G/16G/32G/100G to 100G or 200G user selectable
 TR10_12EN: for six 10G transponders application
For more information, see the Apollo Reference Manual. To define encryption settings, see Define
TM200EN/TM100_2EN encryption settings.
Table 3-11: TM200EN Card - Port Configuration Rules

Ports
1 Line 0 Line  OTU4  ODU4
 OTUC2  ODUC2 (PT22) +
2*ODU4(PT21)
20 C1-C20 1,…,20 Client  OTU4  ODU4
 ETY100G  ODU4
 ETY40G  ODU3
 STM64  ODU2
 OC192  ODU2
 FC1200  ODU2e
 FC1600  ODUF-FC1600
 FC3200  ODUF-FC3200
 OTU2  ODU2
 OTU2e  ODU2e
Table 3-12: TR10_12EN Card - Port Configuration Rules

Ports
12 C9-C12 9,…,12  ETY10GOC  ODU2e
Client
 ETY10G  ODU2
P13-P14 13,14 Client/Line  STM64  ODU2
L15-L20 15,…,20 Line  OC192  ODU2
 FC1200  ODU2e
 OTU2  ODU2
 OTU2e  ODU2e
NOTE: To define the port configuration for a TM200EN/TR10_12EN card, see Configure ports.
3.3.8 TM100_2EN
TM100_2EN is a 2 x 100G Multi-Service, low cost, minimal size encrypted solution to customers for DWDM
networks that can be configured to operate with or without encryption. The card applications is used in
small regional or metro access networks requiring flexible grooming of 10G to OTU2 and 10G\100G OTU4,
encrypted or non-encrypted.
The card is very similar to the TM200EN in all client port aspects. The main difference is in the line ports;
TM200EN has a single CFP2-based line port, while the TM100_2EN has two QSFP28-based line ports that
can be configured to OTU4.
TM100_2EN is a double slot long card that provides similar main functions as the TM200EN.
For more information, see the Apollo Reference Manual. To define encryption settings, see Define
TM200EN/TM100_2EN encryption settings.
Table 3-13: TM100_2EN Card - Port Configuration Rules

Ports
22 Line 0, Line 0,21 Line OTU4 ODU4
21
C1-C20 1,…,20 Client  OTU4  ODU4
 ETY100G  ODU4
 ETY40G  ODU3
 STM64  ODU2
 OC192  ODU2
 FC1200  ODU2e
 FC1600  ODUF-FC1600
 FC3200  ODUF-FC3200
 OTU2  ODU2
 OTU2e  ODU2e
NOTE: To define the port configuration for a TM100_2EN card, see Configure ports.

3.3.9 TM400
The TM400 is a Flex-grid and Flex-rate transponder/muxponder card designed for ultra-long haul, metro-
long haul, and metro-regional network configurations. It has four client ports and two line ports supporting
line rates of 2 x 200 Gbps, or 2 x 100 Gbps. The card occupies a double (long) slot in the Apollo supported
platforms. The card can be configured to operate in one of two modes: transponder or muxponder.
TM400 provides a multi-service, cost-effective solution with 100G/200G wavelengths.
For more information about the TM400 card, see the Apollo Reference Manual.
Since the TM400 occupies a double slot, you can only assign it to a free even-numbered IO slot, where the
following odd-numbered slot is free as well. In the STMS, when you assign the TM400 card to an even-
numbered slot, the following slot is automatically disabled for assignment.
Table 3-14: TM400 Card - Port Configuration Rules

Ports
40 CLIENT-<n+10> ; n=2…41 2,12,22,32 Client ETY100G ODU4
CLIENT-<n+10> ; n=2…41 2,12,22,32 Client OTU4 ODU4
CLIENT-<n> ; n=2…41 2-41 Client ETY10GOC ODU2e
2 LINE 0, LINE 1 0, 1 Line OTU4 ODU4
or or
OTUC2 ODUC2 (PT22) +
2*ODU4(PT21) +
10*ODU2e (for
each ODU4)
or ODUC2 (PT22) +
2*ODU4(PT21)
You can configure up to 40 client ports, depending on Line Port Type and Client Port Type selected per
Client Port Group.
Under ODUC2, another Sub-IF level exists - ODU4. Each ODU4 works with the regular PT21 rules.
You can only configure a second line port if you purchased the license for it. See the STMS Getting Started
and Administration Guide.
NOTE: To define the port configuration for a TM400 card, see Configure ports.

3.3.9.1 TM400-REG100
The TM400 can be configured as a regenerator by assigning it as TM400_REG100. The two LINE ports are
used to implement the regenerator configuration, while the Client ports are not used.
The functions of the regenerator are to clean up and amplify the optical signals transmitted through the
optical line (3R regeneration). Any attempt to assign the Client ports in the TM400_REG100 mode will be
rejected by the software.
When the TM400 is assigned as regenerator (TM400_REG100), the software implicitly configures both line
ports to operate as independent OTU4 ports. It also configures the cross-connect between the lines for the
regenerator application. The user only has to configure the SD-FEC modes, including:
 SD-FEC15 (regularly marked SD-FEC (legacy))
 SD-FEC25
For more information about the TM400-REG100 card, see the Apollo Reference Manual.
Table 3-15: TM400-REG100 Card - Port Configuration Rules

Ports
2 L0, L1 Line OTU4 ODU4
0, 1
NOTE: To define the port configuration for a TM400-REG100 card, see Configuring Ports.
3.3.10 AoC10/AoC10B
The AoC10/AoC10B provides 10 Gbps ADM service on a card. It supports up to 16 client interfaces, which
are multiplexed into the G.709 multiplexing structure and sent via two OTU2 line interfaces.
Any of the client interfaces can be configured to accept an STM-1, STM-4, GbE, FC/FC2/FC4, OTU-1, STM-
16, DVB-ASI, SDI, or HD-SDI signal. The card has integrated cross-connect capabilities, providing more
efficient utilization of the lambda. Any of the signals can be added or dropped at each site, while the rest of
the traffic continues on to the next site. Broadcast TV services can be dropped and continued (duplicated),
eliminating the need for external equipment to provide this functionality.
For more information about the AoC10/AoC10B card, see the Apollo Reference Manual.
Table 3-16: AoC10/AoC10B Card - Port Configuration Rules
Card Number Port Label Port Number Port Role Port Type Sub-IF Type
of Ports
16 C0 - C15 0,…,15 Client  STM1/OC3  ODUslot
AoC10
 STM1e/OC3e  ODUslot
 STM4/OC12  ODUslot
 FC100  ODUslot
 ETY1G  ODUslot
 ETY1Ge  ODUslot
 VIDEO270  ODUslot
 FC200  ODU1
 HDSDI1485  ODU1
 OTU1  ODU1
 FC400  2*ODU1
2 L1, L2 16,17 Line OTU2 ODU2 + 4 * ODU1
16 C0 - C15 0,…,15 Client  STM1/OC3  ODU0
AoC10B
 STM1e/OC3e  ODU0
 FC100  ODU0
 ETY1G  ODU0
 ETY1Ge  ODU0
 FC200  ODU1
 OTU1  ODU1
 FC400  2*ODU1
2 L1, L2 16,17 Line OTU2 ODU2(PT21)
NOTE: To define the port configuration for an AoC10/AoC10B card, see Configure ports.
3.3.11 AoC25/AoC25B
The AoC10 can be assigned as an AoC25 operating in 2.5 Gbps mode, and enabling the user high flexibility
in implementation of more applications with the same hardware. When assigned as an AoC25 the card can
work as a Multi-service OTU1 muxponder and/or transponder.
The two Line ports (port 16 and 17) are disabled in this mode, and only the 16 client ports are used. The
first eight ports (Port 0 to Port 7) are configured as Client ports, and the last eight (Port 8 to Port 15), as
Line ports.
For more information about the AoC25/AoC25B card, see the Apollo Reference Manual.
Table 3-17: AoC25/AoC25B Card - Port Configuration Rules
of Ports
8 C0 - C7 0,…,7 Client  STM1/OC3  ODUslot
AoC25
 ETY1G  ODUSlot
 ETY1Ge  ODUSlot
 FC200  ODU1
8 C8 - C15 8,…,15 Client OTU1 ODU1
8 C0 - C7 0,…,7 Client  STM1/OC3  ODU0
AoC25B
 FC100  ODU0
 ETY1G  ODU0
 ETY1Ge  ODU0
 VIDEO270  ODU0
 FC200  ODU1
8 C8 - C15 8,…,15 Client OTU1 ODU1(PT20)
NOTE: To define the port configuration for an AoC25/AoC25B card, see Configure ports.
3.3.12 CMR40B
The CMR40B is a multiservice combiner card that supports 4 x 10G LAN/STM-64/OC-192/OTU2/OTU2e
aggregation to OTU-3e. It enjoys enhanced noise tolerance with improved chromatic dispersion tolerance,
and offers good bandwidth efficiency. It reduces the number of wavelengths, increases capacity, and
simplifies management, and can be used in both metro/core and long-haul networks.
The CMR40B uses a coherent receiver and DP-DQPSK modulation format. The client side utilizes XFPs for
10G interfaces.
For more information about the CMR40B card, see the Apollo Reference Manual.
Table 3-18: CMR40B Card - Port Configuration Rules
Ports
4 C1 - C4 0,1,2,3 Client  STM64  ODU2
 OC192  ODU2
 FC800  ODU2 or ODUF-FC800
 FC1200  ODU2e
 OTU2  ODU2
 OTU2e  ODU2e
1 Line 4 Line OTU3e ODU3e(PT21) + 4 *
ODU2/ODU2e/ODUF-FC800
NOTE: To define the port configuration for a CMR40B card, see Configure ports.
3.3.13 CMR100/CMR100L
The CMR100/CMR100L combiner (muxponder) interfaces to any combination of ten of the following client
signals through XFPs, and maps them into a 100 Gbps colored line signal for WDM network transport,
according to the G.709 standard: 10GbE/STM64/OC192/FC8/FC10/OTU2/OTU2e. It occupies a double slot
in Apollo platforms.
The CMR100/CMR100L uses DP-QPSK modulation, a coherent receiver, DSP processing, and soft decision
forward error correction, for superior noise tolerance, and an exceptional ability to mitigate CD and PMD
impairments.
The CMR100 is optimized for Ultra Long Haul networking applications, and the CMR100L supports regional
applications. While the TR100L does not support single fiber bi-directional WDM operation, in terms of all
other capabilities, the cards are identical and they are interoperable with each other. The client side utilizes
XFPs for 10G interfaces.
For more information about the CMR100/CMR100L card, see the Apollo Reference Manual.
Table 3-19: CMR100/CMR100L Card - Port Configuration Rules

Ports
10 C1 - C10 1,2,3,…,10 Client  STM64  ODU2
 OC192  ODU2
 FC1200  ODU2e
 OTU2  ODU2
 OTU2e  ODU2e
1 Line 0 Line OTU4 ODU4 (PT21) +
10 * ODU2/ODU2e
NOTE: To define the port configuration for a CMR100/CMR100L card, see Configure ports.
3.3.14 CMR100M
The CMR100M is a combiner card that interfaces to any combination of ten of the following client signals
through SFP+, and maps them into a 100 Gbps colored line signal for WDM network transport, according to
the G.709 standard: 10GbE/STM64/40GbE. It occupies a double slot in the Apollo platforms.
The CMR100M is optimized for metro applications (up to 1200 km without regeneration). The client side
utilizes SFP+ transceivers for 10G interfaces.
The CMR100M uses a CFP based on DP-QPSK modulation, a coherent receiver, DSP processing, and soft
decision forward error correction, for superior noise tolerance, and an exceptional ability to mitigate CD
and PMD impairments.
In addition, the CMR100M line can be deployed with non-colored CFP (instead the coherent CFP) for simple
point to point over dark fiber or any other application. The card supports SR10 or LR4 100G line
transmission.
For more information about the CMR100M card, see the Apollo Reference Manual.
Table 3-20: CMR100M Card - Port Configuration Rules

Ports
12 C1-C12 1,2,3,…,12 Client  STM64  ODU2
 OC192  ODU2
 FC1200  ODU2e
 OTU2  ODU2
 OTU2e  ODU2e
 ETY40G  ODU3
1 Line 0 Line OTU4 ODU4 (PT21) +
10*
ODU2/ODU2e/ODUF_FC800
NOTE: To define the port configuration for a CMR100M card, see Configure ports.
3.4 OPT96xx layer 1 fabric interface cards
OPT96xx supports the following fabric interface cards:
 FIO10_5/FIO10_5B
 FIOMR_16/FIOMR_16B
 FIO100
 FIO100M
NOTE: For detailed descriptions of the supported fabric interface cards, see the Apollo
Reference Manual.
3.4.1 FIO10_5/FIO10_5B
The FIO10_5/FIO10_5B is a fabric interface I/O card that supports up to five 10G interfaces using fixed or
tunable pluggable XFP transceivers. Each port can be configured to serve as either client or line interface
port. Client interface ports accept 10G LAN, STM-64, FC8, OTU-2, or OTU-2e signals. Client signals are
mapped to ODU-2 or ODU-2e (G.709) and cross connected through the central universal fabric to the line
side.
The FIO10_5B card does not support FC ports (e.g. FC800, FC1200).
For more information about the FIO10_5/FIO10_5B card, see the Apollo Reference Manual.
Table 3-21: FIO10_5/FIO10_5B Card - Port Configuration Rules

of Ports
5 P0 - P4 0,…,4 Client/Line  STM64  ODU2
FIO10_5
 OC192  ODU2
 FC800  ODU2
 FC1200 (day2)  ODU2e
 ETY10G  ODU2
 OTU2  ODU2
 OTU2e  ODU2e
5 P0 - P4 0,…,4 Client/Line  STM64  ODU2
FIO10_5B
 OC192  ODU2
 ETY10G  ODU2
 OTU2  ODU2(PT21)
 OTU2e  ODU2e
NOTE: To define the port configuration for an FIO10_5 card, see Configure ports.
3.4.2 FIOMR_16/FIOMR_16B
The FIOMR_16/FIOMR_16B card is a fabric interface I/O card that supports up to 16 low-rate client
interfaces using SFP transceivers. Each port can be configured to STM-1, STM-4, GbE, FC1/FC2/FC4, OTU-1,
STM-16, DVB-ASI, SDI, and HD-SDI signals. Client-side signals are mapped to G.709 ODU-k and cross
connected through the central universal fabric to the egress side.
The FIOMR_16B card does not support FC ports (e.g. FC100, FC200) or Video ports (e.g.
VIDEO270). For more information about the FIOMR_16/FIOMR_16B card, see the Apollo Reference
Manual.
Table 3-22: FIOMR_16/FIOMR_16B Card - Port Configuration Rules

of Ports
16 P0,…,P15 0,…,15 Client/Line  STM1/OC3  ODUslot
FIOMR_16
 ETY1G  ODUslot
 ETY1Ge  ODUslot
 FC200  ODU1
 OTU1  ODU1
 FC400  2*ODU1
16 P0,…,P15 0,…,15 Client/Line  STM1/OC3  ODU0
FIOMR_16B
 ETY1G  ODU0
 ETY1Ge  ODU0
 OTU1  ODU1(PT20)
NOTE: To define the port configuration for an FIOMR_16 card, see Configure ports.
3.4.3 FIO100
The FIO100 card is an OTU4v uplink for the 1 Tbps universal fabric of the 9600 platform. The 100G OTU-4 is
terminated to its tributary signals (ODUk) and cross connected through the fabric to the egress side.
For more information about the FIO100, see the Apollo Reference Manual.
Table 3-23: FIO100 Card - Port Configuration Rules

Ports
1 Line 0 Line OTU4 ODU4 (PT21)
NOTE: To define the port configuration for an FIO100 card, see Configure ports.
3.4.4 FIO100M
The FIO100M card is an OTU4 uplink for the 1 Tbps universal fabric of the 9600 platform. The 100G OTU-4
is terminated to its tributary signals (ODUk) and cross connected through the fabric to the egress side.
NOTE: The FIO100M is supported only in the 9600 Apollo platform when the FM1000 1 Tbps
universal fabric is also installed.
For more information about the FIO100, see the Apollo Reference Manual.
Table 3-24: FIO100 Card - Port Configuration Rules

Ports
1 Line 0 Line OTU4 ODU4 (PT21)
NOTE: To define the port configuration for an FIO100 card, see Configure ports.
3.5 OPT96xx layer 2 cards
Layer 2 cards in Apollo support both black and white and colored (C/DWDM) line/clients, with optional
bidirectional functionality. Services on these cards can be configured independently to work with no
protection or full equipment protection. The cards support GFEC, EFEC (I.4), and no FEC modes towards the
line. The service cards interface smoothly with alien client transceivers as well.
Apollo service cards comply with ITU-T standards for 50 GHz and 100 GHz multichannel spacing (DWDM)
using fixed or tunable XFP transceivers. They support PM and GCC in-band management, with Ethernet and
MPLS-TP PM.
Apollo currently supports the AoC10_L2 layer 2 card.
3.5.1 AoC10_L2
The AoC10_L2 is an MPLS service card that supports an advanced Ethernet-based metro-core layer,
enabling NG Ethernet applications such as triple play, VPLS business connectivity, 3G Ethernet-based
aggregation, and CoC bandwidth applications. The AoC10_L2 cards provides complete PB (QinQ) and MPLS
switching functionality, offering scalability and smooth interoperability with IP/MPLS core routers.
The AoC10_L2 supports full interoperability with data cards in the NPT, XDM, and BroadGate platforms, as
well as seamless interfacing with external third-party hardware.
You can configure Fast IOP protection for AoC10_L2 cards. See Fast IOP protection (L2 ports).
For more information about the AoC10_L2 card, see the Apollo Reference Manual.
3.5.2 AoC10_L2 port configuration

Table 3-25: AoC10_L2 card - port configuration rules
Number of Ports Port Label Port Number Port Type
16 P0,…,P15 0,…,15 GE
4 P16,…,P19 16,…,19  GE10
 GE10-OTU2E
2 P20,P21 20,21 GE10
During port configuration of an AoC10_L2 card, you must define the Port Mode for each port to one of the
following:
 UNI (default)
 I-NNI
 E-NNI
 MoE
 I-MOE
 Mirror
The Port Mode for ports 20 and 21 can only be set to I-MOE.
NOTE: To define the port configuration for an AoC10_L2 card, see Configuring Ports.
3.5.2.1 Configure L2 port parameters (AoC10_L2)

To configure L2 parameters for a port:
1. In the Network Explorer tab, right-click the relevant port and select Properties.
The port properties appear in the right pane.
2. In the Properties tab, select the L2 Parameters tab.
The L2 parameters appear.
3. Define the parameters as required and click Apply.

The parameters displayed depend on the Port Mode defined for the port. See the following table.
Table 3-26: L2 Parameters

Parameter Description Port Mode
Ethernet Attributes
LLCF Trigger Enables the port to be an LLCF trigger UNI, E-NNI
LLCF Client Enables the port to be an LLCF client UNI, E-NNI
Max Packet Length The maximum packet length allowed for the All modes
port

Parameter Description Port Mode

MAC Filter Defines whether the reserved MAC address is UNI, E-NNI, MIRROR
filtered or not
Scheduling Mode For future versions UNI, E-NNI, MIRROR
UNI Attributes
Untagged Frame Handling The method used for frame handling: Priority UNI
Tagged, Forward, PVID, Block, and None
PVID The C-VLAN ID assigned to untagged frames UNI
received on this port (PVID translation)
Default CD Priority The default priority for untagged or UNI
priority-tagged frames
Ingress Policer Attributes
Ingress Policer State The Ingress policer state: Blocked, Policing, or UNI, E-NNI
NRL (No Rate Limit)
Ingress Policer Profile The Ingress policer profile UNI, E-NNI
Egress Policer Attributes
Egress Policer State The Egress policer state: Blocked, Policing, or UNI, E-NNI
NRL (No Rate Limit)
Egress Policer Profile The Egress policer profile UNI, E-NNI
3.5.2.2 Configure MPLS port parameters (AoC10_L2)

You can define MPLS parameters for MOE and iMOE ports.
To configure MPLS parameters for a port:

2. In the Properties tab, select one of the following:
 MPLS tab - to define MPLS parameters.

 MPLS Status tab - to view MPLS status parameters (read-only).
3. In the MPLS tab, define the parameters as required and click Apply. See the following table.
Table 3-27: MPLS Port Parameters

Tunnel Capacity Mode The tunnel capacity mode: Normal mode or Extended mode.
Next Hop MAC Address The destination port's MAC address
Severity Profile The severity profile assigned to the port protection group (if port
protection is defined). The default value is default.
Alarm Master Mask Enables or disables the alarm master mask. Enabling it causes all alarms
for the port protection group to be masked. Disabled by default.
DiffServ Block Read-only. Shows DiffServ block attributes for an MOE port (for tunnels
on which DiffServ is enabled).
MoE Attributes
In Exp Mapping Read-only. Shows the mapping of EXP bits from incoming MPLS packets.
Each incoming EXP bit is mapped to a specific CoS and color.
Out Exp Mapping Read-only. Shows the mapping of EXP bits from outgoing MPLS packets.
A specific CoS and color is mapped to each outgoing EXP bit.
3.5.2.3 Configure Link OAM for a port (AoC10_L2)

Configuring Link Operation, Administration, and Maintenance (OAM) enables you to monitor a link for
critical events. You can also set the remote device to Loopback mode in order to perform testing on the
link.
To configure Link OAM for a port:

2. In the Properties tab, select the Link OAM Configuration tab.
The Link OAM parameters appear.
3. Select the Enable OAM checkbox.

4. Define the Local Mode and Remote Mode.
5. To set the remote device to Loopback mode, select the Loopback checkbox.
3.5.2.4 Configure a LAG (AoC10_L2)
Two or more links can be aggregated together to form a Link Aggregation Group (LAG). A LAG is treated by
MAC clients as a single link.
To configure a LAG:
1. In the Network Explorer tab, right-click the AoC10_L2 card and select Show LAG.
The LAG window opens.
2. Select and transfer two ports or more (with the same type and port mode) from the Individual Port
List to the right pane.
3. Define the LAG parameters. See the table below.

4. Click Apply.
The LAG is created.
5. To view the LAG details, select it from the Aggregation Group dropdown list and click Get.
NOTES:
 To create a new LAG port from this view, click New. The details of the selected LAG port
are cleared.
 To delete a LAG, click Delete.
Table 3-28: LAG parameters

Master Port Defines the master port.
Distribution Enables/disables distribution for the port.
Protection Type Currently only Load Sharing is available. (Read-only)
LACP Enable Enables/disables LACP for the port.
 If LACP is Disabled, LACPDU will not be sent/received.
 If LACP is Enabled, LACPDU will be sent/received based on LACP Mode.
LACP Mode Defines the LACP mode for the port as one of the following:
 Active: LACPDU will be sent/received.
 Passive: LACPDU will be sent/received only if the partner’s LACP
Mode is Active (the partner sends LACPDUs).
Actor Port Priority Defines the port priority (higher value= lower priority).
LACPDU Timeout Defines the LACPDU time interval:
 Short = 1 second
 Long = 30 seconds
LAG Link Down Threshold Defines how many failed LAG member ports (including the master and slaves)
are considered Link Down.
Alarm Master Mask The alarm master mask.
PM Monitor Enables/disables PM monitoring for the LAG.
Mac Address The MAC address automatically associated with the LAG. (Read-only)
Severity Profile The severity profile.
3.5.3 AoC10_L2 switch configuration
The following AoC10_L2 switch configuration operations are available:
 Configure general switch parameters
 Configure RSTP
 Manage switch policer profiles
 Configure link OAM thresholds
 Configure port mirroring
 View host budget information
 View VSI configuration
 View CE-VLAN and COS translation for a UNI port
 Configure Egress COS policing
 View PW redundancy for a VSI
 View VSI alarms
 View VSI PM counters
 View switch PM counters
 View CFM configuration
 View BD tunnel configuration
 View tunnel XC configuration
3.5.3.1 Configure general switch parameters (AoC10_L2)
To configure general switch parameters for the AoC10_L2 card:
1. In the Network Explorer tab, right-click the switch element below the AoC10_L2 card and select
Properties.
The switch properties appear in the right pane.
2. In the General tab, set the Switching Mode parameter to PB (default) or MPLS-PE and click Apply.
3. Configure the switch parameters and click Apply.
Different parameters must be defined for each switching mode. See the following table.
Table 3-29: AoC10_L2 General Switch Parameters

Ethernet (PB) Network ID PB network ID.
MPLS Network ID MPLS network ID.
PE ID Switch ID.
Ethernet MAC Address Ethernet MAC address defined for the network (read-only).
Scheduling Mode Set to Auto by default. (read-only).
FIB
Aging Time Timeout period in seconds for aging out dynamically learned forwarding
information.
Switch Quota Exceeded Action performed if the switch quota is exceeded: Forward (default) or Drop.
Action
PM Monitor Enables or disables performance monitoring.
CFM Domain
CFM Local MEP ID MEP ID of local MEP for all MEGs with configured MEP in which switch
participates.
CFM LTM Flooding  Disable (default): LTM is not forwarded unless the target MAC address
has been learned.
 Enable: LTM is flooded when the target MAC address has not been
learned.
PM
PM Profile PM profile, which contains object thresholds for triggering alarms and events.
PM Monitor Enables or disables performance monitoring.
CoS Defines the priority levels of COS profiles used for data traffic. You can
transfer COS profiles between the High Priority List and Low Priority List.
CAC Configuration Defines the overbooking factors for each COS. Enables defining each COS as
best-effort.
CCN
CCN Enable Enables the switch to accept CCN messages.
CCN Forwarding Enables the switch to forward CCN messages.
LACP System Priority Defines the system priority for LACP (higher value = lower priority).
If both systems have the same System Priority, the system with the lowest
LAG MAC address is preferred.
3.5.3.2 Configure RSTP (AoC10_L2)

AoC10_L2 supports RSTP protection mechanisms. RSTP functionality is configured at both the card and port
levels.
To configure RSTP:
Properties.
2. Select the RSTP tab.
The RSTP tab displays two tabs:
 Switch RSTP: Displays the RSTP configuration settings for the card.
 RSTP Ports: Displays the list of ports with RSTP defined for the card. Ports without RSTP do not
appear (MOE and I-MOE).
3. In the Switch RSTP tab, you can define the following RSTP parameters, as required:
 Bridge Priority: The RSTP Bridge Priority, which is used with the Bridge's MAC Address. Default:
8192.
 Fwd Delay: The time that the bridge stays in each of the Listening and Learning states that
precede the Forwarding State. Default: 15 sec.
When a topology change is underway and has been detected, this parameter is also used to age
all dynamic entries in the Forwarding database.
 Max Age: The time that learned Spanning Tree information is kept before being discarded.
Default: 20 sec.
 Hello Time: The time interval between the generation of Configuration BPDUs by the Root.
Default: 2 sec.
 Notification Enable: Enables or disables RSTP notifications. Enabled by default.
 BPDU Frame Format: Type of BPDU frame format. Default: Standard-BPDU-B.
 Tx Hold Count: Time interval in which no more than two configuration BPDU frames are
transmitted.
The rest of the parameters are read-only.
4. In the RSTP Ports tab, you can define the following RSTP port parameters, as required:
 RSTP Enabled: Defines whether RSTP is enabled for the port
 BPDU PA: BPDU MAC DA used by RSTP
 Port Priority: Priority of RSTP port
 Admin Edge: Defines the initial port state when the port is enabled
The rest of the parameters are read-only.
5. Click Apply to save your changes.
3.5.3.3 Manage switch policer profiles (AoC10_L2)

To manage switch policer profiles defined for the AoC10_L2 card:
Properties.
2. Select the Policer Profiles tab.
The list of Policer Profiles appears.
3. To create a Policer Profile, click Create.

The Create Policer Profile window opens.
4. Type the Policer Profile name and define the following fields:
 CIR: Committed Information Rate
 CBS: Committed Burst Size
 EIR: Excess Information Rate
 EBS: Excess Burst Size
 CM: Coupling Flag
5. Click Create.
The new policer profile is created and appears in the list of policer profiles.
3.5.3.4 Configure link OAM thresholds (AoC10_L2)
To define link OAM thresholds:
Properties.
2. Select the Link OAM Threshold tab.
The ports and their default thresholds appear.
3. Modify the thresholds as required and click Apply.
3.5.3.5 Configure port mirroring (AoC10_L2)

Port mirroring is a method of monitoring network traffic. A copy of each incoming and outgoing packet
from one port of a network switch is forwarded to another port, from where the packet can be studied.
Port mirroring can be used for diagnostics or debugging.
You can configure port mirroring by defining a source port from which to copy all packets, and a destination
(mirror) port to which those packets are sent. The Port Mode for the destination port must be defined as
MIRROR during port configuration.
There can only be one source port and two mirror ports (Ingress & Egress) per switch. The mirror port can
also be a single port, configured as both Ingress and Egress mirror ports.
To configure port mirroring:
Properties.
2. Select the Port Mirror tab.
The Port Mirroring parameters appear.
3. For Source Port, select the source port from the dropdown list.
4. For Mirror Ingress traffic to, select the mirror port to which Ingress traffic will be copied.
5. For Mirror Eggress traffic to, select the mirror port to which Egress traffic will be copied.
6. Click Configure.
Port mirroring is configured.
3.5.3.6 View host budget information (AoC10_L2)
On the AoC10-L2 card, the host CPU is responsible for receiving and transmitting control packets, as well as
for handling state machines for all the configured control protocol instances. Host budget management is
required to ensure that the host CPU can perform these processes.
To view host budget information:

Properties.
2. Select the Host Budget tab.
The host budget information appears.
The host budget information includes the following:

 Utilized control packet budget: The amount of utilized managed resources in the managed
resources pool
 Available control packet budget: The amount of available managed resources in the managed
resources pool
 BFD current session number: The current BFD session Number
 BFD maximum session number: The maximum BFD Session Number
3.5.3.7 View VSI configuration (AoC10_L2)
To view the configuration of a VSI:
Services.
The list of defined VSIs appears in the VSI List tab. You can filter the list using the Filter options.
2. Right-click the relevant VSI in the list and select VSI Properties View.
The VSI window opens, displaying the configuration details. The information that appears in this
window changes according to the VSI type and configuration. See the table below for a description of
the available tabs.
Most of the parameters in the VSI window are configured from LightSOFT and are read-only. For more
information about them, see the LightSOFT User Guide.
Table 3-30: Tabs in the VSI window

Tab Description
VSI Definitions Displays the VSI definitions. It also enables you to view Egress CE-VLAN and COS
translation for UNI ports on the VSI, as well as configure Egress COS policing. See
Viewing CE-VLAN and COS Translation for a UNI Port and Configuring Egress COS
Policing.
PW Redundancy Displays the Pseudowire (PW) redundancy configuration for the VSI. See Viewing PW
Redundancy for a VSI.
Alarms Displays alarms for the VSI. See Viewing VSI Alarms.
PM Counters Displays PM counters for the VSI. See Viewing VSI PM Counters.
3.5.3.8 View CE-VLAN and COS translation for a UNI port (AoC10_L2)
To view CE-VLAN and COS translation for a UNI port on a VSI:
Services.
The list of defined VSIs appears in the VSI List tab.
The VSI window opens.
3. In the VSI Definitions tab, click next to the relevant UNI port row in the table.
The row expands to display the CE-VLAN and COS translation details for the port.
3.5.3.9 Configure Egress COS policing (AoC10_L2)

To configure Egress COS policing:
Services.
3. In the VSI Definitions tab, click next to the relevant UNI port row in the table.
The row expands to display the CE-VLAN and COS translation details for the port.
4. Scroll down to view the Egress Cos Policer pane.
 Define the policing settings for the COSs by selecting the checkbox in the relevant COS columns
and selecting the State and Profile settings.
 Define the same policing setting for all COSs by selecting Policing All CoSs and selecting the state
from the dropdown list.
6. Click Apply to save the settings.
3.5.3.10 View PW redundancy for a VSI (AoC10_L2)

To view the PW redundancy configuration for a VSI:
Services.
3. Select the PW Redundancy tab.
The PW Redundancy List displays PW redundancy objects defined for the VSI.
4. Select the relevant PW redundancy object.
The PW redundancy object details appear in the Properties tab (below the PW Redundancy List).
5. To view PM counters for the object, select the PM Counters tab and define the settings for the
counters to be displayed.
6. To view which maintenance commands are running on the object, select the Commands tab.
3.5.3.11 View VSI alarms (AoC10_L2)
To view alarms for a VSI:
Services.
3. Select the Alarms tab.
The current alarms appear in the Current Alarms tab.
4. To view non-reported alarms, select the Non Reported Alarms tab.
3.5.3.12 View VSI PM counters (AoC10_L2)

To view PM counters for a VSI:
Services.
3. Select the PM Counters tab.
The current PM counters appear.
You can select the time interval (Duration) of the counters to be displayed, as well as the time period
in which the list is refreshed (Refresh in).
4. To view historical PM counters:
a. Select Historic Counters.
b. Define the time period
c. Click Apply.
The historical PM counters from the defined time period appear.
5. To view policer PM counters:
a. Select the Policer PM Counters tab.
b. Select the port and policer from the dropdown lists.
c. Click Get PM Counters.
The policer PM counters appear.
3.5.3.13 View switch PM counters (AoC10_L2)
To view the PM counters for the switch:
Properties.
2. Select the PM Counters tab.
3. Select the Bridge PM Counters or FDB PM Counters tab.

4. For Duration, select the time interval of the counters to be displayed.
5. For PM Counters, select Current Counters or Historic Counters.
 For current counters, you can define the Refresh in setting as required.
 For historic counters, define the time period for the counters and click Apply.
The counters appear in the list.
3.5.3.14 View CFM configuration (AoC10_L2)

To view the CFM configuration for a VSI:
Services.
The list of defined VSIs appears in the VSI List tab. You can filter the list using the Filter options.
2. Right-click the relevant VSI in the list and select CFM MA List.
The CFM MA List window opens, displaying the CFM configuration details. All parameters in this
window are read-only.
NOTES:
 To view the DM and SLM configuration of the CFM, select the DM and SLM tabs in the MA
Parameters tab.
 To view the DM and SLM configuration of the Remote MEP, select the DM and SLM tabs in
the Remote MEP tab.
3.5.3.15 View BD tunnel configuration (AoC10_L2)
To view the configuration of a BD tunnel:
Services.
2. Select the BD Tunnel List tab.
The list of defined BD tunnels appears. You can filter the list using the Filter options.
3. Right-click the relevant BD tunnel in the list and select BD Tunnel Properties.
The BD Tunnel window opens, displaying the configuration details. All parameters in this window are
read-only.
3.5.3.16 View tunnel XC configuration (AoC10_L2)
To view the configuration of a tunnel XC:
Services.
2. Select the Tunnel XC List tab.
The list of defined tunnel XCs appears. You can filter the list using the Filter options.
3. Right-click the relevant tunnel XC in the list and select View Tunnel XC.
A window opens, displaying the tunnel XC configuration details. All parameters in this window are
read-only.
3.6 Optical components
Apollo platforms support a wide range of passive optical cards, including C/DWDM Mux/DeMuxes, OADMs,
splitters/couplers, filters, and Dispersion Compensating Fibers (DCFs). These platforms can be deployed
together with Artemis passive optical platforms (that also include a wide range of similar optical cards),
offering a low cost, high modularity, and very high density solution. This leaves the photonic slots in the
Apollo platforms available for active cards, such as optical amplifiers, ROADMs, service cards, and fabric.
Apollo supports the following optical components:
 Multi-degree ROADM Cards
 Mux/DeMux Cards
 OADM Cards
 Optical Filters, Splitters, and Couplers
 Optical Amplifiers
 DCF
 OLP_S2
NOTE: For detailed descriptions of the supported optical components, see the Apollo
Reference Manual.
3.6.1 Multidegree ROADM cards

A comprehensive suite of third-generation WSS ROADM solutions are available, to suit different operator
needs. WSS advanced technology is available for full inter-ring connectivity between access rings and the
metro backbone while providing advanced protection and restoration capabilities. In the current release of
Apollo platforms, ROADM cards are implemented with WSS on the add side.
Apollo supports the following ROADM cards:
 ROADM_2A: A 2-degree double slot ROADM card that supports 44 channels with 100 GHz spacing in
the C band.
 ROADM_2A50: A 2-degree wide double-slot ROADM card that supports 88 channels with 50 GHz
spacing in the C band.
 ROADM_4A: A 4-degree double slot ROADM card that supports 44 channels with 100 GHz spacing in
the C band.
 ROADM_4A50: A 4-degree double-slot ROADM card that supports 88 channels with 50 GHz spacing in
the C band.
 ROADM_4F: A 4-degree double-slot ROADM card that supports 88 channels with 50 GHz spacing in
the C band.
 ROADM_9A: A 9-degree double-wide slot ROADM card that supports 44 channels with 100 GHz
 ROADM_9A50: A 9-degree double-wide slot ROADM card that supports 88 channels with 50 GHz
 ROADM_9F: A 9-degree double-slot ROADM card that supports 88 channels with 50 GHz spacing in
the C band.
 ROADM_20CF: A long double-slot card that has 20 ports with duplex LC connectors, marked 1 to 20. It
can be configured to operate as a ROADM with a variable number of Degree and Client ports,
applicable in three modes: 4x16, 6x14, 8x12.
 ROADM_20TF: A long double-slot card. In the current release, this card operates as a Fix-Grid ROADM
that supports 88 channels with 50 GHz spacing.
 TFA_8: A Tunable Filter Array card that provides the colorless functionality for the ROADM cards,
which enables the operator to control the color of the drop ports.
For detailed descriptions of the supported ROADM cards, see the Apollo Reference Manual.
Table 3-31: ROADM Cards - Port Configuration Rules

Card Number Port Label Port Port Role Port Type Sub-IF Type
of Ports Number
ROADM_2A 1 Line 0 Line OTS OMS + 44 * OCH
1 Local 1 Local
1 Express 2 Express
ROADM_2A50 1 Line 0 Line OTS OMS + 88 * OCH
1 Local 1 Local
1 Express 2 Express
1 Local/Deg1 1 Local
3 Deg2 - Deg4 2,…,4 Degree
ROADM_4F 1 Line 0 Line OTS OMS + 88 * OCH
1 Local/Deg1 1 Local OTS OMS + 88 * OCH
3 Deg2 - Deg4 2,…,4 Degree OTS or For OTS: OMS +
OCHP 88 * OCH
For OCHP: OCH
ROADM_9F 1 Line 0 Line OTS OMS + 88 * OCH
of Ports Number
OCHP 88 * OCH
For OCHP: OCH
ROADM_20CF_4x16 4 Deg1 - Deg4 1,…,4 Degree OTS OMS + 88 * OCH
16 C5 - C20 5,…,20 Client OTS or For OTS: OMS +
OCHP 88 * OCH
For OCHP: OCH
ROADM_20CF_6x14 6 Deg1 - Deg6 1,…6 Degree OTS OMS + 88 * OCH
14 C7 - C20 7,…20 Client OTS or For OTS: OMS +
OCHP 88 * OCH
For OCHP: OCH
ROADM_20CF_8x12 8 Deg1 - Deg8 1,…8 Degree OTS OMS + 88 * OCH
12 C9 - C20 9,…20 Client OTS or For OTS: OMS +
OCHP 88 * OCH
For OCHP: OCH
ROADM_20TF 1 Line 0 Line OTS OMS + 88 * OCH
OCHP 88 * OCH
For OCHP: OCH
TFA_8 1 Line 0 Line OTS OMS + 88 * OCH
8 P1, P2…, P8 1,…,8 Add/Drop OCHP OCH
NOTE: To define the port configuration for a ROADM card, see Configuring Ports.
3.6.2 Mux/DeMux cards

A range of passive Mux/DeMux cards are available for Apollo platforms. The DWDM Mux/DeMux cards are
based on flat-top technology, enabling back-to-back connectivity with lower attenuation compared to other
technologies. With this configuration, minimal (if any) regeneration is required for the back-to-back
Mux/DeMux connectivity. Mux/DeMux cards are available for DWDM with 8, 16, 44, 48, 88, or 96 channels.
Apollo supports the following Mux/DeMux cards:
 MXD8: A DWDM Mux/DeMux card for 8 channels in the C band (Ch. 21-Ch. 28) with 100 GHz spacing
and E/W configuration.
 MXD16: A DWDM Mux/DeMux card for 16 channels in the C band (Ch. 21-Ch. 36) with 100 GHz
spacing and E/W configuration.
 MXD44/MXD44_P: A DWDM Mux/DeMux card for 44 channels in the C band (Ch. 17-Ch. 60) with 100
GHz spacing and E/W configuration.
 MXD44E: Provides a cost-effective solution to support 88-channel networks. The solution is based on
two 44-Channel Mux/DeMux cards with 100 GHz spacing with channels shifted 50 GHz, relatively to
each other.
 MXD48_P: A DWDM Mux/DeMux shelf for 48 channels in the Extended-C band (Ch. 14-Ch. 61) with
100 GHz spacing and E/W configuration.
 MXD88/MXD88_P: A DWDM Mux/DeMux card for 88 channels in the C band (Ch. 17-Ch. 60) with 50
GHz spacing and E/W configuration.
 MXD96_P: A DWDM Mux/DeMux shelf for 96 channels in the Extended-C band (Ch. 13.5-Ch. 61) with
50 GHz spacing and E/W configuration.
 CMXD8: A CWDM Mux/DeMux with 8 channels (20 nm spacing).
 D_MD_40: A DWDM Mux/DeMux card for 40 channels with 100GHz spacing.
 MXD4_B: A Band Mux/DeMux for up to four bands into a transmission fiber. It has 4 Band ports and a
single line port. Each of its four Band ports enables the multiplexing/DeMultiplexing of the 100 Gbps
Band transceivers (OTR100_ER10DR_Bx and OTR100_ZR10DR_Bx).
For detailed descriptions of the supported Mux/DeMux cards, see the Apollo Reference Manual.
The Mux/DeMux card ports are automatically configured upon card assignment. You can view the port
configuration for a Mux/DeMux card from Chassis view (via the Configuration > Artemis Chassis View
menu options).
Table 3-32: Mux/DeMux Cards - Port Configuration Rules

of Ports Number
MXD8 1 Line 0 Line OTS OMS + 8 * OCH
8 Ch-21,…,Ch-28 1,…,8 Add/Drop OCHP OCH
MXD16 1 Line 0 Line OTS OMS + 16 * OCH
MXD44/MXD44_P 1 Line 0 Line OTS OMS + 44 * OCH
MXD44E 1 Line 0 Line OTS OMS + 88 * OCH
MXD48_P 1 Line 0 Line OTS OMS + 44 * OCH
MXD88/MXD88_P 1 Line 0 Line OTS OMS + 88 * OCH
88 Ch-17,…,Ch-60.5 1,…,88 Add/Drop OCHP OCH
MXD96_P 1 Line 0 Line OTS OMS + 88 * OCH
88 Ch-17,…,Ch-60.5 8,…,95 Add/Drop OCHP OCH
CMXD8 1 Line 0 Line OTS OMS + 8 * OCH
8 Ch-47 - Ch-61 1,2,…,8 Add/Drop OCHP OCH
1 OSC1310 9 OSC OSChannel N/A
D_MD_40 1 Line 0 Line OTS OMS + 40 * OCH
of Ports Number
MXD4_B 1 Line 0 Line OTS OMS + 4 * OCH
4 Band 1,…,4 Add/Drop OCHP OCH
3.6.3 OADM cards

The passive Optical ADM (OADM) cards perform the channel add-and-drop function.
Apollo supports the following OADM cards:
 FOADM2_xx: Fixed OADM with two add/drop channels, for 100 GHz spacing networks.
 FOADM4_xx: Fixed OADM with four add/drop channels, for 100 GHz spacing networks.
 FOADM850_xx: Fixed OADM with eight add/drop channels, for 50 GHz spacing networks.
 COADM4_x: Fixed OADM with four add/drop channels for CWDM networks.
 OADMC4_xx: Passive OADM with four flexible (colorless) add/drop channels, for 100 GHz spacing
networks.
 OADMC8_xx: Passive OADM with eight flexible (colorless) add/drop channels, for 100 GHz spacing
networks.
For detailed descriptions of the supported OADM cards, see the Apollo Reference Manual.
OADM card assignment requires defining an additional mandatory attribute, First Channel (see Card
Assignment).
The OADM card ports are automatically configured upon card assignment. You can view the port
configuration for an OADM card from Chassis view (via the Configuration > Artemis Chassis View menu
options).
Table 3-33: OADM Cards - Port Configuration Rules

of Ports Number
FOADM2_xx 1 Line 0 Line OTS OMS + 44 * OCH
1 Exp 1 Express OTS OMS + 44 * OCH
2 Ch-xx - Ch-xx+1 2,…,3 Add/Drop OCHP OCH
4 Ch-xx - Ch-xx+3 2,…,5 Add/Drop OCHP OCH
7 Ch-xx, Ch-xx+0.5, 2,…,8 Add/Drop OCHP OCH
Ch-xx+1, … CH-xx+3
COADM4_x 1 Line 0 Line OTS OMS + 4 * OCH
of Ports Number
4 Ch-xx, Ch-yy, Ch-zz, 2,3,4,5 Add/Drop OCHP OCH
Ch-tt
OADMC4_xx 1 Line 0 Line OTS OMS + 44 * OCH
4 Ch-xx, Ch-xx+1, ..., 1,…,4 Add/Drop OCHP OCH
Ch-xx+3
OADMC8_xx 1 Line 0 Line OTS OMS + 44 * OCH
8 Ch-xx, Ch-xx+1, ..., 1,…,8 Add/Drop OCHP OCH
Ch-xx+7
3.6.4 Optical filters, splitters, and couplers

Apollo supports the following optical filters, splitters, and couplers:
 CT_1310_2: An optical card that includes two separate CT filters with a 1310 nm OSC port each.
 CT_1510_2: An optical card that includes two separate CT filters with a 1510 nm OSC port each.
 CT_OTDR_2: An optical card that includes two separate CT and OTDR filters with a 1510 nm OSC port
each. The card Muxes/DeMuxes the OTDR signal, C-Band, and OSC signals.
 C_OTDR_2: An optical card that includes two separate CT and OTDR filters each. The card
Muxes/DeMuxes the OTDR signal with the combined C-Band and OSC signals.
 SP_SM_4: A quad splitter/coupler for single mode (SM) fibers with 50% ratio card that includes four
identical splitter/coupler units.
 SP_MM_4: A quad splitter/coupler for multi-mode (MM) fibers with 50% ratio card that includes four
identical splitter/coupler units.
 SP_CE4_2: A double splitter/coupler card for four services with 25% ratio.
 SP_CE8_1: A 1 x 8 splitter/coupler card, used for CDC reception of coherent channels in a mixed
network (network that contains both coherent and non-coherent channels).
 SP_CE32_1: Includes two independent splitter/coupler sections: a 1 x 32 bidirectional splitter/coupler
unit and a 1 x 2 bidirectional splitter/coupler unit. It is used for CDC reception in coherent networks.
 R/B_2: A Red/Blue filter card for use in single-fiber bidirectional network applications.
 CLT_1510/1590: A CLT filter card for use in bidirectional network applications.
For detailed descriptions of the supported optical filters, splitters, and couplers, see the Apollo Reference
Manual.
The ports of the optical filters, splitters, and couplers are automatically configured upon card assignment.
Table 3-34: Optical Filters, Splitters, and Couplers - Port Configuration Rules
Component Number of Port Label Port Port Role Port Type Sub-IF Type
Ports Number
CT_1310_2 4 Line-x, C-band-x 0,1 3,4 Line OTS OMS
2 1310-x 25 OSC OSChannel N/A
CT_1510_2 4 Line-x, C-band-x 0,1 3,4 Line OTS OMS
2 1510-x 25 OSC OSChannel N/A
CT_OTDR_2 4 Line-x, C-band-x 0,1 5,6 Line OTS OMS
2 OSC1510-x 27 OSC OSChannel N/A
4 OTDR 1610 3, 4 8, 9 OTDR Tap OTDR Tap N/A
C_OTDR_2 2 Line-x 04 Line OTS OMS
2 C-band+OSC-x 15 Line OTS N/A
4 OTDR 1610 2,3 6,7 OTDR Tap OTDR Tap N/A
SP_SM_4/ 12 Userx 0 User PO OS
SP_MM_4 Serv-Ax, Serv-Bx 1,2 Service
3
4,5
6
7,8
9
10,11
SP_CE4_2 10 Line-x, 0 Line OTS OMS + 88 * OCH
P1-x, P2-x, P3-x, P4-x 1,2,3,4 Add/Drop
5
6,7,8,9
SP_CE8_1 1 Line 0 Line OTS OMS + 88 * OCH
SP_CE32_1 1 Line 33 Line OTS OMS + 88 * OCH
2 P1, P2 34, 35 Add/Drop OTS OMS + 88 * OCH
1 Line 0 Line OTS OMS + 88 * OCH
R/B_2 6 Line-x 03 Line OTS OMS
Red-In-1 Blue-Out-1 1,2 4,5 Add/Drop OTS OMS
Red-Out-1 Blue-In-1
CLT_1510 4 Line-x, C-band-x 0,1 3,4 Line OTS OMS
2 OSC-1510 25 OSC OSChannel N/A
CLT_1590 4 Line-x, C-band-x 0,1 3,4 Line OTS OMS
2 OSC-1590 25 OSC OSChannel N/A
3.6.5 Optical amplifiers
Apollo supports dynamic variable and fixed gain amplifiers. The variable gain EDFAs are typically used in
regional and long-haul networks. Using dynamic EDFA technology, these amplifiers automatically adjust
themselves to the attenuation of the fiber span for which they are compensating, providing optimized
amplification over the entire spectral band.
Fixed gain amplifiers are offered as a low-cost alternative for specific configuration requirements, such as a
booster after ROADM nodes.
Apollo supports the following optical amplifiers:
 OA_PA: A fixed gain EDFA-based amplifier optimized as a preamplifier for metro applications.
 OA_FB: A fixed gain EDFA-based amplifier optimized as a power booster for terminal and ROADM
sites with up to 44 DWDM channels.
 OA_FB-R: A new hardware version of the OA_FB optical amplifier that can operate in the ACC
(Automatic Current Control) mode. It is optimized to work in OSC signal amplifier application for the
OA_HRSF. The card occupies one slot in the Apollo platforms.
 OA_ML: A variable gain EDFA-based amplifier with-mid stage access (MSA), optimized for low gain
spans before In-Line and ROADM sites in Regional/LH applications, supporting up to 44/88 DWDM
channels.
 OA_M: A variable gain EDFA-based amplifier with MSA, optimized for high gain spans before In-Line
and ROADM sites in Regional/LH applications, supporting up to 44/88 DWDM channels.
 OA_L: A variable gain single-stage EDFA optimized for medium gain spans in coherent networks
applications, supporting up to 44/88 DWDM channels.
 OA_LF: A variable gain single-stage EDFA optimized as an ILA for coherent networks with short span
applications, supporting up to 96 DWDM channels.
 OA_HF: A variable gain single-stage EDFA optimized as an ILA for coherent networks with long span
applications, supporting up to 96 DWDM channels.
 OA_DLF: A dual EDFA card that includes two independent EDFA amplifiers in a single package. The
two EDFAs are defined as pre-amp and Booster amplifiers. The pre-amp EDFA amplifies the optical
signal received from the line, and the Booster amplifies the light transmitted to the line. The pre-amp
EDFA in the OA_DLF is optimized as an ILA for coherent networks with short-span applications.
 OA_DLHF: A dual EDFA card that includes two independent EDFA amplifiers in a single package. The
two EDFAs are defined as pre-amp and Booster amplifiers. The pre-amp EDFA amplifies the optical
signal received from the line, and the Booster amplifies the light transmitted to the line. The pre-amp
EDFA in the OA_DLHF is optimized as an ILA for coherent networks with long-span applications.
 OA_FHBS: A high power fixed gain EDFA-based amplifier optimized for terminal and ROADM sites in
E/W configuration, supporting up to 88 DWDM channels.
 OA_MHS: A high-power variable gain EDFA-based amplifier with MSA, optimized for in-line sites in
regional/LH applications, E/W configuration, supporting up to 88 DWDM channels.
 OA_HRS: A Raman optical amplifier especially optimized for long-haul multispan and undersea
applications. OA_HRS is intended for use in conjunction with EDFA amplifiers over G.652, G.654, and
G.655 fibers.
 OA_HRSF: A Raman optical amplifier card that provides low-noise amplification for Apollo networks.
It provides a mean to improve the system OSNR, but specifically employed on ultra-long links (>40dB
loss). It also enables the generation and termination of the optical supervision channel (OSC). This
card includes an OTDR Tap port that will be able to connect to an OTDR port of the OTDR_8 card
(from V8.0).
 OA_EHRS: A Hybrid Raman-EDFA optical amplifier specially optimized for DCF-less coherent networks.
It combines a distributed low-noise Raman amplification and a lumped high-Gain, high-power EDFA
amplification in a single module. This card includes an OTDR Tap port that will be able to connect to
an OTDR port of the OTDR_8 card (from V8.0).
 OA_EHRSF: A Hybrid Raman-EDFA optical amplifier specially optimized for DCF-less coherent
networks. It also supports operation in Flex-Grid. It combines a distributed low-noise Raman
amplification and a lumped high-Gain, high-power EDFA amplification in a single module.
 rid Raman-EDFA optical amplifier specially optimized for DCF-less coherent networks. It combines a
distributed low-noise Raman amplification and a lumped high-Gain, high-power EDFA amplification in
a single module.
 OA_USPBF: A high-gain power booster amplifier with an output power of 26 dBm. It can be used in
dispersion-managed 10G networks, cascaded to MSA ILA, or in DCF-less coherent networks, cascaded
to non-MSA ILA. It supports multichannel applications and is capable of amplifying the Extended-C-
band.
 OA_DPR: A low-cost Red Band, dual EDFA card that includes two independent EDFA amplifiers in a
single package. The two EDFAs are defined as pre-amp and Booster amplifiers. The OA_DPR can
operate only in the Red Band (ITU-T Ch. 21 to Ch. 36) and support 16 (100 GHz spacing), or 32
channels (50 GHz spacing). For safety reasons the OA_DPR is designed to operate in E/W
configurations and includes built-in C/T filters. The card occupies one slot in the OPT96xx platforms,
and includes an 1510nm OSC filter and a pluggable 100 Mbps 1510nm OSC SFP.
For detailed descriptions of the supported optical amplifiers, see the Apollo Reference Manual.
Depending on the amplifier type, you might need to define additional mandatory attributes during card
assignment (see Card Assignment).
Table 3-35: Optical Amplifiers - Port Configuration Rules

Amplifier Number Port Label Port Port Role Port Type Sub-IF
of Ports Number Type
OA_PA 2 Amp-In, Amp-Out 1, 2 Line OTS OMS
1 OSC100M 0 OSC OSC100M N/A
OA_FB 2 Amp-In, Amp-Out 1, 2 Line OTS OMS
OA_FB-R 2 Amp-In, Amp-Out 1, 2 Line OTS OMS
1 OSC100M 0 OSC OSC100M OSC100M
OA_ML 4 Amp-In, Amp-Out, 1,2 Line OTS OMS
Mid-stage-Out, Mid-stage-In 3,4
OA_M 4 Amp-In, Amp-Out, 1,2 Line OTS OMS
OA_L 2 Amp-In, Amp-Out 1, 2 Line OTS OMS
OA_LF 2 Amp-In, Amp-Out 1, 2 Line OTS OMS
OA_HF 2 Amp-In, Amp-Out 1, 2 Line OTS OMS
OA_DLF 2 Node, Line 1, 2 Line OTS OMS
OA_DLHF 2 Node, Line 1, 2 Line OTS OMS
OA_FHBS 3 Amp-In, Exp-Out, Line 1,3,2 Line OTS OMS
OSC1510 4 OSChannel
OA_MHS 5 Amp-In, Exp-Out, Line, 1,5,2 Line OTS OMS
OSC1510 6 OSChannel
OA_HRS 2 Node, Line 1,2 Line OTS OMS
OSC1510 3 OSChannel
OA_HRSF 2 Node, Line 1,2 Line OTS OMS
2 OSC2M 0,3 OSC OSC2M N/A
OSC1528 OSChannel
1 OTDR1610 4 OTDR Tap OTDR Tap N/A
OA_EHRS 3 Line, Amp-Out, Exp-In 1,2,3 Line OTS OMS
OSC1528 4 OSChannel
OA_EHRSF 3 Line, Amp-Out, Exp-In 1,2,3 Line OTS OMS
OSC1528 4 OSChannel
1 OTDR1610 5 OTDR Tap OTDR Tap N/A
OA_LEHRS 3 Line, Amp-Out, Exp-In 1,2,3 Line OTS OMS
OSC1528 4 OSChannel
OA_USPBF 3 Amp-In, Exp-Out, Line 1,3,2 Line OTS OMS
OA_DPR 2 Node, Line 1, 2 Line OTS OMS
NOTE: To define the port configuration for an optical amplifier, see Configuring Ports.
3.6.6 OTDR
The Optical Time Domain Reflectometer (OTDR) is an optoelectronic device used to test the characteristic
of an optical fiber. The OTDR injects a series of optical pulses into the tested fiber and examines the light
scattered or reflected back from the end of the fiber. The strength of the return pulses is measured and
integrated as a function of time.
OTDR functionality is supported in any Apollo amplifier that supports 100 Mbps OSC with an SFP, by simply
replacing the regular OSC SFP with the OTDR1_L5 transceiver.
The OTDR is implemented in the Apollo platforms by an OSC SFP that has also the capability to operate as
an OTDR. This application provides a low-cost and compact OTDR device, specifically designed to determine
the location of a fiber cut. The SFP used for the OTDR application is OTDR1_L5, which is a 1510 nm, 100
Mbps OSC SFP with OTDR capabilities.
The OTDR1_L5 provides the following main functions:
 Operates normally as a 100 Mbps OSC SFP
 OTDR functionality triggered by management commands (see OTDR Management)
For more information about the OTDR card, see the Apollo Reference Manual.
3.6.7 OTDR_8
An Optical Time-Domain Reflectometer (OTDR) is an optoelectronic device used to characterize an optical
fiber. It injects a series of optical pulses into the fiber under test and extracts, from the same end of the
fiber, light that is scattered or reflected back from points along the fiber. The scattered or reflected light
that is gathered back is used to analyze the optical fiber characteristics.
The purpose of an OTDR is to detect, locate, and measure elements at any location on a fiber optical link.
The OTDR_8 test results are processed and enable to display a graphical representation of the entire fiber
optic link (see Run OTDR_8 tests). The OTDR provides the user a trace (graphic representation) of the fiber's
attenuation as a function of distance from the OTDR connection point.
The OTDR_8 is a low-cost dedicated OTDR test card for the Apollo OPT96xx family that occupies a double
(long) slot in the supported platforms. It can monitor up to 8 fibers (one at a time) and provide a maximum
reach on 40 dB fibers. The OTDR_8 operates at 1610 nm (outside the range of the C-band), which enables it
to perform in-service tests.
For more information about the OTDR_8 card, see the Apollo Reference Manual.
Table 3-36: OTDR_8 Card - Port Configuration Rules

Ports
8 P1, P2, …P8 1, …, 8 OTDR OTDR N/A
3.6.8 DCF
Apollo supports the following Dispersion Compensation Fiber (DCF) cards:
 DCF652_xx: A DCF card suitable for G. 652 compliant fibers. The card is available for compensation for
various distances (5, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, or 120 km).
 DCF655_xx: A double-wide slot DCF card that is suitable for G. 655 compliant fibers. The card is
available for compensation for various distances (40 km, 80 km, or 120 km).
The marking xx in the card name indicates the compensated distance in km.
NOTE: For detailed descriptions of the supported DCF cards, see the Apollo Reference
Manual.
DCF cards are passive modules that can be installed in any service slot or in Artemis cages. DCF card
assignment requires defining an additional mandatory attribute, Length (see Card Assignment).
DCF card ports are automatically configured upon card assignment.
Table 3-37: DCF Cards - Port Configuration Rules

of Ports Number
DCF652_xx 2 OUT, IN 0,1 Line OTS OMS
DCF655_xx 2 OUT, IN 0,1 Line OTS OMS
3.6.9 OMSP
The OMSP card provides Optical Multiplexer Section Protection (OMSP). The OMSP modules switch the
traffic to the protection path when a failure occurs on the main path, and vice versa.
For more information about the OMSP card, see the Apollo Reference Manual.
Table 3-38: OMSP Card - Port Configuration Rules

Number of Port Label Port Port Role Port Type Sub-IF Type
Ports Number
3 Common 0 Common OMS
OTS
Path-A, Path-B 1,2 Path
3.6.10 OLP_S2
The OLP_S2 is an Optical Line Protection (OLP) card that provides protection for two services of Apollo
DWDM networks, while increasing the networks reliability and availability in a cost-effective manner. The
card enables protection against fiber cuts and card failures at the DWDM layer and saves duplicating the
network infrastructure.
The card was designed as an integrated solution for Apollo platforms that saves the use of high-cost
external OEM protection units. It protects Apollo service cards such as transponders, combiners, AoC, and
FIO cards. The card occupies one slot in the Apollo platforms. The OLP_S2 is intended to work with SM
(Single Mode) fibers.
For more information about the OLP_S2 card, see the Apollo Reference Manual.
Table 3-39: OLP_S2 Card - Port Configuration Rules

Number of Port Label Port Port Role Port Type Sub-IF Type
Ports Number
6 Common x 03 Common OCHP, OTS or PO OCH, OMS or OS
Path-Ax, Path-Bx 1,2, 4,5 Path
3.7 Pluggable transceiver modules

Apollo supports pluggable optical transceivers (SFP, SFP+, XFP, QSFP, QSFP28, CFP, and CFP2) for all
services, in both colored and noncolored interfaces. Transceiver modules are used for the entire spectrum
of interfaces, including intra-office, short range, and long range. The standardized modular design of the
transceiver components facilitates network maintenance and upgrades since interchangeable transceiver
components are utilized throughout the product line. Instead of replacing an entire circuit board, a single
module can be removed or replaced, for a considerable cost savings.
SFP+ and XFP transceivers are available in colored and noncolored, tunable, and fixed versions. The tunable
SFP+/XFP transceivers support 50 GHz spacing and are available for long-haul network configurations. QSFP
transceivers support 40GbE, QSFP28 transceivers support 100GbE, CFP transceivers are used for client side
(100GbE) or line coherent interfaces, and CFP2 transceivers are used for 100 GbE client or fan-out (10GbE
or 40GbE) applications.
NOTE: For detailed descriptions of the supported pluggable transceiver modules, see the
Apollo Reference Manual.
3.8 Assign cards

To assign cards:
1. From the Network Explorer tab, right-click the NE and select Assign/Replace Card.
The Assign/Replace Card window opens.
2. For each new card, select the slot and card type to assign to the slot.
3. To view slots in which the assigned card is different from the actual card, click Display mismatch of
Assigned vs Actual.
4. To copy the actual cards to the assigned cards, select the slots of the relevant cards and click Copy
Actual to Assigned.
5. Click Apply.
The cards are assigned.

IMPORTANT: When you assign a new card, most of the mandatory attributes are defined
automatically for the card. For some card types, you must define additional mandatory
attributes as follows:
 OADM Cards: The First Channel attribute must also be defined.
 Amplifiers: Additional attributes must also be defined, depending on the amplifier type.
 DCF Cards: The Length attribute must also be defined.
 TR100/TR100L: The Operation Mode attribute must also be defined.
If the mandatory attributes are not defined for the card, card assignment will fail.
3.9 Replace cards

To replace assigned cards:
1. To replace one card:
a. From the Network Explorer tab, right-click on the card to replace and select Replace Card.
The Replace Card window opens.
)
b. Select the new card and click Set.

The card is replaced.
2. To replace one or more cards for the same NE:
a. From the Network Explorer tab, right-click the NE and select Assign/Replace Card.
The Assign/Replace Card window opens.
b. Change the cards as required and click Apply. For more assignment options, see Assigning cards.
The cards are replaced.
3.10 Unassign a card

NOTE: To unassign an HIO10_20 or HIO100_2 card, you must first delete all of its GE ports.
To unassign a card:
1. From the Network Explorer tab, right-click the card and select Unassign Card.
2. Click Yes.
The card is removed from the slot.
3.11 View the card description

This procedure describes how to view a detailed, textual description of a component card.
To view the card description:

 In the Network Explorer tab (or in Chassis view), right-click on the card and select Description.
A description of the card appears.
3.12 View card properties

To view the card properties:
 In the Network Explorer tab (or in Chassis view), right-click the component card and select
Properties.
The card properties appear. The tabs available depend on the type of card.
3.12.1 Optical card properties

The following configuration and status information about Optical cards is displayed in its Properties tab.
The specific properties depend on the actual card type.
Table 3-40: Optical Card Properties

Field Description
Chassis (read only) Host name of the NE or the IP address of the NE's management
interface.
Boot Firmware Revision (read only) Boot firmware revision of the component card.
Slot Number (read only) Card slot location.
Configured Card Type Type of component card.
Actual Card Type (read only) Actual type of component card that is plugged in the shelf.

Field Description
Operation Status (read only) Operational status of the card.
Severity Profile Select the profile to be assigned to the card.
Alarm Master Mask Set the value to true to enable Alarm Master Mask mode.
3.12.2 xRCP/RCP card properties

The following configuration and status information about the RCP card is displayed in its Properties tab.
Table 3-41: xRCP/RCP Card Properties

Field Description
Name (read only) Name of the component card.
interface.
Card Type (read only) Specific card type: xRCP or RCP.
Status (read only) Status of the component card, for example, Active.
Last State Change (read only) Date and time of the last state change.
State Change Reason (read only) Reason for the last state change, for example, Boot.
Primary RCP Defines the primary RCP card: RCP A or RCP B.
Enable High Availability (for In OPT96xx platforms, high availability is disabled for RCP cards by
OPT96xx only) default. Selecting this option, enables high availability for RCP cards.
See Configuring High Availability (OPT96xx).
Number of seconds to wait after detecting a failure of the active RCP
Timeout before standby takeover
before the standby RCP switches to active.
(Active RCP card)
Serial Number (read only) Serial number of the component card.
Board Revision (read only) Board revision level of the component card.
Architecture Revision (read only) Architecture revision level of the component card.
Hardware Configuration (read Hardware configuration version of the component card.
only)
Boot Firmware Revision (read N/A
only)
Hardware Option (read only) N/A
Card Role (read only) Type of component card, for example, Route Control Processor.
Slot Number (read only) Card slot location.
DC Power Consumption (read DC power consumption of the xRCP/RCP.
only) Note: This field will appear for OPT96xx only if it is configured during
STMS installation to appear.
Power Source (read only)
List of xPFM/PFMs that feed the xRCP/RCP card.
(for OPT99xx only)
3.12.3 CTM card properties
The following configuration and status information about CTM cards (where applicable) is displayed in its
Properties tab.
NOTE: The CTM resides on the RCP card and is installed only when node synchronization is
required. It is not shown in the Chassis view.
Table 3-42: CTM Card Properties

Field Description
Name (read only) Name of the component card.
Chassis (read only) Host name of the NE or the IP address of the NE's management interface.
Serial Number (read only) Serial number of the component card.
Board Revision (read Board revision level of the component card.
only)
Architecture Revision Architecture revision level of the component card.
(read only)
Hardware Configuration Hardware configuration version of the component card.
(read only)
Card Type (read only) Type of component card, displayed as Control Timing Module.
Slot Number (read only) Card slot location, CTM_A or CTM_B.
CTM Card Type (read Type of CTM displayed, for example, CTM.
only)
CTM Card Operational Operational state of CTM displayed, for example, Active.
state (read only)
Last Switchover (read Date and time of the last switchover from active to Standby or Never.
only)
Auto Enable Select if auto enable is required.
Locked Out Select if the clock synchronization is to be locked out.
Primary CTM Select the primary CTM card, CTM A or CTM B.
Timeout Enter the amount of time for timeout.
3.13 View card performance statistics

In addition to a variety of real-time counter tabs, the property sheet for a component card may display a
number of related performance statistics tabs.
NOTE: For information about viewing real-time and historical counter data, see the STMS
The following table describes each of the performance statistics tabs and indicates the types of component
cards for which the tabs are displayed.
Table 3-43: Performance statistics information

Tab Card types Description
File System RCP Displays graphs of file system usage data.
Stats
Temperature NPB, RCP Displays graphs of temperature sensor data.
Stats
Counters
CPU Usage NPB, RCP Displays the following CPU usage data:
 User Time
 System Time
 Idle Time
Memory Usage NPB, RCP Displays the following memory usage data:
 Total Memory Available
 Used Memory
 Total Swap Available
 Used Swap
OS Processes NPB, RCP Displays the following OS processes data:
 Total Processes, Running Processes,
 Sleeping Processes, Stopped Processes,
 Zombie Processes
NOTE: Performance statistics for NPBs are displayed per slice.

To view performance statistics for a component card:
1. In the Network Explorer tab (or in Chassis view), right-click the component card and then Properties.
2. Click the relevant performance statistics tab.
4 Ports and interfaces
STMS enables you to manage ports and interfaces. Interfaces are implemented through ports on the
supported service cards.
4.1 Supported ports and interfaces

The following types of ports and interfaces are supported:
Table 4-1: Supported Ports and Interfaces

Interface category Port type abbreviation
Ethernet/GbE ety (ety1g | ety1ge | ety10g | ety10goc)
gbe (ge | ge10)
For example, the interface name ge-u2/2.3 corresponds to a GbE interface located on
port 2 of an NPB card in slot u2 that has a logical unit number of 3.
Fibre Channel fc (fc1200 | fc800 | fc400 | fc200 | fc100 | fc1600 | fc3200)
Logical gre0
For example, the interface name gre0.53 corresponds to a GRE interface that has a
logical unit number of 53.
lo0
For example, the interface name lo0.0 corresponds to the primary logical loopback
interface on the device.
ml
For example, the interface name ml-bundle_1.0 corresponds to a multilink interface
using the multilink bundle named bundle_1, with a unit number of 0.
t
For example, the interface name t-ge-u7/11.0 corresponds to a tunnel interface on
port 11 of the 20-port GbE card in slot u7, with a unit number of 0.
Management osc (osc100 | osc2m | oschannel)
OTN and other ochp
photonic interfaces
odu (odu-slot | odu1 | odu2 | odu2e | odu2f | odu3 | odu3e)
oms (cwdm | dwdm | non-colored)
ots
otu (otu1 | otu2 | otu2e | otu2f | otu3 | otu3e | otu4)
otuc2
po
spo
SDH stm (stm64 | stm16 | stm4 | stm1 | stm1e)
e1
For example, the interface name e1-u6/2:3-3:7-2.0 corresponds to an interface located
on port 2 of an MSM card in slot u6 that has been channelized to E-1, starting at
channel 3, TUG-3 group 3, TUG-2 group 7, TU-12 2. This interface has a logical unit
number of 0.

STMS User Guide Ports and interfaces
SONET oc (oc192 | oc48 | oc12 | oc3 | oc3e)

ds (ds | ds1)
For example, the interface name ds1-u7/1:1:5-4.0 corresponds to an interface located
on port 1 of an MSM card in slot u7 that has been channelized to a VT group, starting
at channel 1, VT group of 5, and a tributary of 4 within the group. The interface has a
logical unit number of 0.
A second example illustrates a DS-1 channel group interface. The interface name
ds-u5/2:2:7-4:3.0 corresponds to an interface located on port 2 of an MSM card in slot
u5 that has been channelized to a DS-1channel group, starting at DS-3 channel 2, VT
Group 7, and a tributary of 4 within that group, with the first DS-0 starting at 3. The
interface has a logical unit number of 0.
Video video270
sdi360m
hdsdi1485g
Packet
ge10
ge10-otu2e
ge100
ge100-otu4
4.2 Terminology
The following terms are used when describing interfaces:
 Logical interface: Virtual interface on a physical interface or sub-interface. One interface or sub-
interface can support multiple logical interfaces. Multiple logical interfaces are supported by applying
tagging, such as VLAN-IDs, to packets arriving from or sent to different destinations.
 Concatenated interface: SDH/SONET interface where all of the time-slots are used together. For
instance, a concatenated OC-12 interface cannot be channelized to smaller data streams.
 Channelized interface: Single SDH/SONET interface can support multiple SDH/SONET sub-interfaces
or channels. The time-slots are divided into channelized interfaces, creating multiple interfaces on
one physical interface. Channelized interfaces are also called sub-interfaces.
 Gigabit Ethernet interface: Correspond to Gigabit Ethernet ports. Support multiple logical interfaces
per physical interface and can support multiple VLANs.
 10 Gigabit Ethernet interface: Correspond to 10 Gigabit Ethernet ports. Support multiple logical
interfaces per physical interface and can support multiple VLANs.
 10 Mbps Ethernet interface: Correspond to 10/100/1000BaseT Ethernet ports. 10 Mbps Ethernet is
carried over a twisted pair copper cable.
 100 Mbps Ethernet (FE) interface: Correspond to 10/100/1000BaseT Ethernet ports. 100 Mbps
Ethernet is carried over a twisted pair copper cable.
 1000 Mbps Ethernet interface: Correspond to 10/100/1000BaseT Ethernet ports. 1000 Mbps
Ethernet is carried over four CAT5 shielded twisted pair copper cables.

4.3 Supported interfaces
Interfaces are implemented through ports on the various types of service cards. This section describes the
interfaces supported through ports on service cards installed in the chassis slots.
4.3.1 OTN interfaces

Optical Transport Network (OTN) technology offers a range of rates up to 200Gbps. 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 ODU1 to ODU4. Used, for example, in OTU2 ports in TR10_4 cards, or for ODU
interfaces multiplexed to an OTUk port in an AoC10 or FIO10_5 card. Also used for ODUSlot interface
for ports with interface rates under 2.5G.
 OTUC2 port with a rate of 200Gbps for ODUC2 interfaces. It provides PT22 multiplexing via the HO
ODO (ODUC2) interface, which is divided into two ODU4 interfaces (marked as TPN1 and TPN2), each
with 100G.
PT21 ODU multiplexing is supported. It provides the following benefits:
 Support of lower granularity ODU0 - 1.25Gbps (PT21).
 Flat ODU hierarchy means that ODUk can sit directly on an ODU4 trail.
 High order ODU trails can include ODUk trails of various rates. Rates do not need to be of a single,
uniform type.
 New ODU interfaces provide greater efficiency of resource usage.
Table 4-2: Cards and Sub-interfaces Supporting PT21 Granularity

Card Port Type PT21 Sub-interface Rate Supported
FIO10_5B OTU2 ODU2 (client/line)
AOC10B OTU2 ODU1 (client), ODU2 (line)
FIO100 OTU4 ODU4 (line)
PT22 multiplexing is supported via the OTUC2 port.
Table 4-3: Cards and Sub-interfaces Supporting PT22 Granularity

Card Port Type PT22 High Order (HO) PT22 Lower hierarchy PT21 Sub-interfaces
Sub-interface Rate Supported sub-interface
TM400 OTUC2 ODUC2 (line) 2 x ODU4 For each ODU4 (as in
other cards)
4.3.2 FC interfaces
Fibre Channel (FC) technology, supported by the OPT96xx platforms, offers a range of rates up to FC10G. FC
interfaces are supported through the following types of ports:
 FC-1G ports using ODU0 and ODUSlot interfaces
 FC-2G ports using ODU1 interfaces
 FC-4G ports using 2xODU1 interfaces
 FC-8G ports using ODU2 interfaces
 FC10G ports using ODU2f interfaces
 FC16G ports using ODU Flex FC1600 interfaces
 FC32G ports using ODU Flex FC3200 interfaces
4.3.3 Video interfaces

Constant Bit Rate (CBR) technology is supported through the following types of ports:
 VIDEO270 ports with a rate of 270 Mbps, using ODU0 and ODUSlot interfaces.
 HDSDI1485 ports with a rate of 1.485 Gbps, using ODU1 interfaces (future).
4.3.4 Management interfaces

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.
4.3.5 Physical Optical interfaces

Physical Optical (PO) technology is supported for splitter/coupler ports using Optical Section (OS)
interfaces.
4.3.6 SDH interfaces

SDH/SONET technologies are supported for the following port types:
 STM1/OC3, STM1e/OC3e, and STM4/OC12 ports using ODU0 and ODUSlot interfaces.
 STM16/OC48 ports using ODU1 interfaces.
 STM64/OC192 ports using ODU2 or ODU2e interfaces. Used, for example, in TR10_4 or CMR40 cards.
SDH interfaces correspond to SDH ports. SDH interfaces can correspond either to the bandwidth of an
entire SDH port or a channelized portion of the physical SDH port. By default, SONET/SDH PHY cards ports
use SDH framing.
The following figure illustrates the SDH mappings supported by different PHY cards and the channelization
paths taken by those cards.
Figure 4-1: SDH Mappings
For SDH ports, you can configure E-1 interface type.

TUG-3 channels
One STM-1 interface can be channelized into three Tributary Unit Groups, level 3 (TUG-3) channels, each
supporting a Tributary Unit, level 3 (TU-3) channel.
NOTE: The TUG-3 channel follows the Administrative Unit, level 4 (AU-4) path. AU-4 channels
are equivalent to STM-1 channels. There is no direct way to configure a TUG-3 or TU-3
interface on the device.
TU-3 interfaces have a rate of 49.536 Mbps and carry DS-3 frames.
TUG-2 channels
Tributary Unit Group, level 2 channels can be channelized from TUG-3 channels. One STM-1 contains 21
TUG-2 channels. Each TUG-2 supports three Tributary Unit, level 12 channels. The rate for TU-12 channels is
2.304 Mbps. TU-12s carry E-1 frames.
E-1 interfaces
TU-2 interfaces can be channelized into 3 DS-1 interfaces (63 per STM-1). E-1 interfaces have a rate of 2.048
Mbps.
4.3.7 SONET interfaces

SDH/SONET technologies are supported for the following port types:
 STM1/OC3, STM1e/OC3e, and STM4/OC12 ports using ODU0 and ODUSlot interfaces.
 STM16/OC48 ports using ODU1 interfaces.
 STM64/OC192 ports using ODU2 or ODU2e interfaces. Used, for example, in TR10_4 or CMR40 cards.
SONET interfaces correspond to SONET ports. SONET interfaces can correspond either to the bandwidth of
an entire SONET port or a channelized portion of the physical SONET port. By default, SONET/SDH PHY
cards ports use SDH framing.
The following figure illustrates the SONET mappings and the channelization paths those cards take.
Figure 4-2: SONET Mappings
For SONET ports, you can configure the following interface types:
 DS-1
 VT-Group
DS-1 interfaces
DS-3 interfaces can be channelized into 28 DS-1 interfaces. DS-1 interfaces are equivalent to T1 interfaces
or 1.544 Mbps.
Virtual Tributary group channel
Virtual Tributary (VT) groups provide an alternative method for channelizing an STS-1 channel. There are
seven VT groups per STS-1 channel, and each can be channelized further.
However, the amount of tributaries per group varies depending on the type of VT group. Currently, the
device supports the VT1.5 type, which has four tributaries per VT group. Each tributary is equivalent to a
DS-1 interface or 1.544 Mbps.
DS-1 Channel Group Interfaces
DS-1 channel groups are DS-1 interfaces that contain a bundle of selected DS-0 time slots. DS-1 interfaces
contain 24 DS-0 time slots. Each DS-1 can support multiple channel groups of non-overlapping bundles of
DS-0 time slots.
4.3.8 Channelized interfaces

A single SDH/SONET interface can support multiple SDH/SONET sub-interfaces or channels. The time-slots
are divided up into channelized interfaces, creating multiple interfaces on one physical interface.
Channelized interfaces are also called sub-interfaces.
4.3.9 Concatenated interfaces
A concatenated interface is an SDH/SONET interface in which all of the time-slots are used together. By
definition, a concatenated interface cannot be channelized - they are two contradictory uses of the
interface. For instance, a concatenated OC12 interface cannot be channelized to smaller data streams.
4.3.10 1 GbE/10 GbE interfaces

Gigabit Ethernet (GbE) interfaces work with corresponding (appropriate capacity) GbE ports. A range of
interface options are supported, including 1GbE, 10GbE, 40GbE, and 100GbE. GbE interfaces support
multiple logical interfaces per physical interface and can support multiple VLANs. Supported port types
include:
 ETY1G/ETY1Ge Layer 1 GbE ports, using ODU0 and ODUSlot interfaces.
 ETY10G Layer 1 10GbE ports, using ODU2 or ODU2e interfaces.
 ETY10Goc Layer 1 10GbE overclocking ports, using ODU2e interfaces.
Multilink Bundles
Multilink bundles allow you to group interfaces into a larger bundle. This feature is available for GbE
interfaces, but not for 10GbE interfaces. For GbE interfaces, you can group together physical interfaces to
create larger Ethernet links. Ethernet bundling is based on the 802.3ad standard.
Generating MAC addresses for GbE interfaces
The device generates MAC addresses for GbE interfaces by using the physical card slot number, the NPB
card slice, the port number, a special value designated for our equipment, and an additional unique
number stored on the device’s chassis.
4.3.11 10/100/1000Mbps Ethernet interfaces

 10 Mbps Ethernet interfaces correspond to 10/100/1000Base-T Ethernet ports. 10 Mbps Ethernet is
carried over a twisted pair copper cable.
 100 Mbps Ethernet (FE or Fast Ethernet) interfaces correspond to 10/100/1000Base-T Ethernet ports.
100 Mbps Ethernet is carried over a twisted pair copper cable.
 1000 Mbps Ethernet interfaces correspond to 10/100/1000Base-T Ethernet ports. 1000 Mbps
Ethernet is carried over four CAT5 shielded twisted pair copper cables.
4.3.12 Logical interfaces
A logical interface is a virtual interface on a physical interface or sub-interface. One interface or sub-
interface can support multiple logical interfaces. Multiple logical interfaces are supported by applying
tagging, such as VLAN-IDs, to packets arriving from or sent to different destinations. The logical interface
number corresponds to the logical unit number which can be any number from 0 through 999,999.
 GRE Interfaces: Generic Routing Encapsulation (GRE) interfaces are software-only interfaces. Logical
GRE interfaces are dependent on the GRE routing protocol and are used to create endpoints for GRE
routing tunnels.
 Logical Loopback Interfaces: Logical loopback interfaces are software-only interfaces that are internal
to the device. Logical loopback interfaces are virtual interfaces that are never down and allow for
routing protocol adjacencies to remain up, even if the outbound interface is down. For example, you
can use a logical loopback interface as a neighbor address for a BGP session.
 Tunnel Interfaces: Tunnel interfaces are a type of virtual interface but they are associated with a
physical port on an NPB card that has a loopback enabled. Tunnel interfaces are used to terminate
L2TPv2 tunnels onto the device.
4.4 Interface name

Each type of interface has a naming scheme, and there are common name elements between interface
types.
The interface naming scheme is as follows:
type-slot/port:channel:(<2channel | group-unit>:channel-group).logical
where:
 type is the type of interface.
 slot is the chassis slot into which the NPB or MSM card is inserted.
 port is the port number on the NPB or MSM card.
 channel is the channel.
 2channel is the DS-1/E-1 channel number, if needed.
 group-unit is the group and unit number.
 channel-group is the channel of the first DS-0 channel in the channel group interface.
 logical is the logical interface number.
NOTE: For multilink bundles, the interface name is in the form ml-bundlename where
bundlename is the user-defined name of the bundle. For tunnel interfaces, a t- is prepended
to the interface name
4.5 Logical interface numbering
The logical interface number corresponds to the logical unit number, which can be any number from 0
through 999,999. An interface can have any number of logical interfaces.
The following section illustrates interface numbering conventions.
 Gigabit Ethernet interface: Corresponds to a Gigabit Ethernet interface port 2 on an NPB card in slot
NPB2 that has a logical unit number of 3, for example, ge-u2/2.3.
 DS-1 Interfaces: Correspond to an interface located on port 1 of an MSM card in slot U7 that has been
channelized to a VT group, starting at channel 1, a VT group of 5, and a tributary of 4 within that
group. The interface has a logical unit number of 0, for example, ds1-u7/1:1:5-4.3.
NOTE: There can only be one logical interface which is used for CES.
 E-1 Interface: Corresponds to an interface located on port 2 of an MSM card in slot U6 that has been
channelized to E-1, starting at channel 3, TUG-3 group 3, TUG-2 Group 7, TU-12 2. This interface has a
logical unit number of 0, for example, e1-u6/2:3-3:7-2.10.
NOTE: There can only be one logical interface which is used for CES.
 DS-1 Channel Group Interface: There are a number of names for DS-1 and E-1 channel group
interfaces, all beginning with ds. The DS-1 channel group via VT-Group corresponds to an interface
located on port 2 of an MSM card in slot U5 that has been channelized to a DS-1 channel group,
starting at DS-3 channel 2, VT Group 7, and a tributary of 4 within that group, with the first DS-0
starting at 3. The interface has a logical unit number of 14. For example, ds-u5/2:2:7-4:3.14.
 GRE Interface: Corresponds to a GRE interface that has a logical unit number of 53, for example,
gre0.53.
 Loopback Interface: Corresponds to the primary logical loopback interface on the device, for
example, lo0.0.
 Tunnel Interface: Corresponds to a tunnel interface on port 11 of the 20-Port Gigabit Ethernet card in
slot NPB7. The unit number is 0. For example, t-ge-u7/11.0.
 Multilink Bundle Interface: Corresponds to a multilink interface that uses the multilink bundle named
bundle_1. The unit number is 0. For example, ml-bundle_1.0.
4.6 Router ID and primary address

The router ID is the primary IP address of the router. The router uses the primary address as the source
address for traffic originating at unaddressed interfaces. BGP and OSPF also use the primary address to
form adjacencies with remote peers.
If a router ID is not configured, the address of the primary loopback (lo0.0) becomes the router ID.
NOTE: For detailed information about router ID selection and configuration, see the
ShadeTree User Guide.
4.7 Primary interface

The primary interface of a router is the interface the router uses to send packets when a specific interface
is not specified and the destination address does not imply a specific interface.
The default primary interface is the lowest addressed interface that is multicast-capable. If no such
interface exists, the default interface is the point-to-point (P2P) interface with the lowest address.
NOTE: See the ShadeTree User Guide.
4.8 IP addresses and interfaces

Follow these rules when assigning IP addresses to interfaces:
 Only one IP address can be assigned to a logical interface.
 IP addresses assigned to broadcast interfaces, such as Ethernet interfaces, cannot have a subnetwork
mask of 32.
 IP addresses assigned to logical loopback interfaces can only have a subnetwork mask of 32.
 Reserved IP addresses cannot be assigned to interfaces.
 Broadcast and network IP addresses cannot have all 1s in the host position
(e.g., 1.1.1.255/24 or 1.1.1.0/24).
 One IP address cannot be assigned to multiple interfaces.
4.9 View port properties

This section explains how to view port configuration details.
To view the properties for a port:

 In the Network Explorer tab (or in Chassis view), right-click the port and select Properties.
The port properties appear in the right pane. The tabs that appear depend on the type of port. For
example, when viewing an optical port with a transceiver, a Transceiver tab is available under the
Properties tab.

4.10 Enable or disable a port

To enable/disable a port:
1. In the Network Explorer tab (or in Chassis view), right-click the port you want to enable/disable.
2. (Optional) If a given port has not yet been configured (or if the port configuration has been deleted
via lsh), right-click the port and select Configure from the shortcut menu.
3. Select Actions > Enable or Disable.
4.11 Configure ports

This procedure provides the general guidelines for configuring ports. For more specific details, as relevant
to each card, see Cards and Modules.
For TM200EN /TM100_2EN card ports, see Configure TM200EN/TM100_2EN card ports.

To configure ports:
1. From Chassis view, right-click the card and select Configure Port.
The Port Configuration window opens.
2. In the Select column, select the checkboxes of the ports you want to define.
3. In the New Type column, select the port interface type for each port.
NOTE: You can view the port configuration rules for the TM200EN/TM100_2EN card by
clicking Configure Port Rules.
4. For the AoC10_L2 card only, select the Port Mode for each port.
5. For GE ports on HIO10_20 /HIO100_2 cards, select the Interface Type (VLAN-Tagged or I-NNI).
6. In the Configured Transceiver column, the options vary according to the port type defined:
 For ports with pluggable transceivers, you can select the transceiver type (for example: all client
ports, OTU2/2e/2f/1, OSC).
 For ports with built-in transceivers, the transceiver type is set and cannot be changed (for
example: OTU4).
 For ports without transceivers, the transceiver type is empty (for example: OTS, OCHP).
7. The Actual Transceiver Type column shows the actual transceiver installed. For newly assigned ports,
you can copy the actual transceivers to the configured transceivers by selecting the relevant ports and
clicking Copy Actual Transceiver to Configured.
8. Define wavelengths for the following types of transceivers:
 DWDM transceivers
 CWDM transceivers
 OCHP ports in SP_CE32_1, SP_CE8_1 and OLP_S2 cards (when configured with OCHP port-types)
a. In the Wavelength column, click select.
The Wavelength Selection window opens.
b. Click a wavelength in the relevant tab and click Select.
9. (Optional) Select a Severity Profile or PM Profile for the port (see Severity Profiles and PM Profiles).
4.11.1 Configure TM200EN/TM100_2EN card ports

To configure TM200EN/TM100_2EN card ports:
1. From Chassis view, right-click the card and select Configure Port.
The Port Configuration window opens.
2. In the Select column, select the checkboxes of the ports you want to define.
3. In the New Type column, select the port interface type for each port.
NOTE: You can view the port configuration rules by clicking Configure Port Rules.
4. The number of ODU4-1 TSs and ODU4-2 TSs for each port you define are updated according to the
port type selected. To view the number of ODU4 TSs used per port type, click ODU4 TSs.
The ODU4TSs window opens.
5. Check the Sum information for the ODU4-1 TSs/ODU4-2 TSs to verify that they do not exceed the
maximum capacity.
6. (Optional) Select a Severity Profile or PM Profile for the port (see Severity Profiles and PM Profiles).
4.12 Loopback interfaces

You can configure one or more logical loopback interfaces on the loopback interface (lo0) of an NE. You can
also configure protocol families for the logical loopback interfaces.
The loopback interface for an NE is displayed under the primary RCP card in the Network Explorer tab. Any
loopback logical interfaces that are configured (e.g., lo0.0, lo0.1, lo0.2) are contained in the Loopback
Interfaces folder.

NOTES:
 The logical loopback interface lo0.0 is referred to as the primary logical loopback
interface.
 This feature is not currently available on 9200 series NEs.
4.12.1 Enable/disable a loopback interface (lo0)

To enable/disable a loopback interface (lo0):
 In the Network Explorer tab, right-click the loopback interface (lo0) and select Actions > Enable or
Disable.
4.12.2 Create a logical loopback interface

To create a logical loopback interface:
1. In the Network Explorer tab, right-click the corresponding Loopback Interfaces folder and select
Create Loopback Interface.
The Input window opens.
2. Enter the unit number for the loopback interface and press ENTER.
A new logical loopback interface is created.
4.12.3 Enable/disable a logical loopback interface

To enable/disable a logical loopback interface:
1. In the Network Explorer tab, click the Loopback Interfaces folder.
2. In the Admin column, select/clear the checkbox that corresponds to the logical loopback interface
you want to enable/disable.
3. In the list, right-click the logical loopback interface you want to enable/disable and select Properties.
The properties of the logical loopback interface appear.
4. In the Logical Interface tab, in the Administrative Status list, select Enabled or Disabled.
5. Click Apply.
4.12.4 Enter a description for a logical loopback interface

You can specify a text description for a logical loopback interface. Typically, this description defines the
usage of the interface.
To enter a description for a logical loopback interface:

2. In the Description column, double-click the cell that corresponds to the logical loopback interface for
which you want to enter a description.
3. In the cell, enter a description of the interface and press ENTER.
OR
The logical loopback interfaces contained in the folder are listed in the View panel.
5. In the list, right-click the logical loopback interface for which you want to specify a description and
select Properties.
6. In the Logical Interface tab, in the Description field, enter a description of the interface.
7. Click Apply.
4.12.5 Delete a logical loopback interface

To delete a logical loopback interface:
The logical loopback interfaces contained in the folder are listed in the View panel.
2. In the list, right-click the logical loopback interface that you want to delete and click Delete.
The logical loopback interface is deleted.

4.12.6 View the interfaces in a Loopback Interface folder
The logical loopback interfaces contained in a particular Loopback Interfaces folder in the Network
Explorer tab are listed in an Interfaces table.
To view the interfaces in a Loopback Interface folder:

 In the Network Explorer tab, click the corresponding Loopback Interfaces folder.
The logical loopback interfaces contained in the folder appear in the View panel.
The Loopback Interfaces table contains the following columns.
Table 4-4: Loopback Interfaces table

Field Description
Name (read only) Name of the logical loopback interface.
Admin Administrative status of the logical loopback interface:
 Enabled
 Disabled
Oper (read only) Operational status of the logical loopback interface:
 Up: Operational.
 Down: Not operational.
 Blank: Not known.
IP Addr IP address (including IP mask) for an INET protocol family.
ISO Addr ISO address for an ISO protocol family.
Description Description of the logical loopback interface.
4.12.6.1 Loopback Interfaces Table

The Loopback Interfaces table contains the following columns.
Table 4-5: Loopback Interfaces table

Field Description
Admin Administrative status of the logical loopback interface:
 Enabled
 Disabled
Field Description
Oper (read only) Operational status of the logical loopback interface:
 Blank: Not known.
IP Addr IP address (including IP mask) for an INET protocol family.
ISO Addr ISO address for an ISO protocol family.
4.12.7 View logical loopback interface properties

To view the properties for a logical loopback interface:
1. In the Network Explorer tab, click the corresponding Loopback Interfaces folder.
The logical loopback interfaces contained in the folder appear in the View panel.
2. In the list, right-click the logical loopback interface for which you want to view the properties and
select Properties.
Table 4-6: Logical loopback interface properties

Field Description
interface.
Operational Status (read only) Operational status of the logical interface:
 Unknown: Not known.
Interface Type The type of logical interface, displayed as Loopback (loopback
(read only) interface).
Interface Index (read only) SNMP ifIndex number.
Time since state change (read only) Time since the last change in operational status.
Layer2 Protocol Name of Layer 2 protocol.
Encapsulation Logical interface encapsulation, displayed as None.
Cross Connected (read only) Whether the logical loopback interface is cross-connected.
Customer Customer assigned to the loopback interface.
Administrative Status Administrative status of the logical loopback interface:
 Enabled
 Disabled
4.12.7.1 Description of Logical Loopback Interface Properties
The following configuration and status information about a logical loopback interface is displayed in the
Properties tab.
NOTE: For information about the MTU for a protocol family (which is displayed on the
property sheet for the associated logical interface), see Changing the Maximum Transmission
Unit for a Protocol Family.
Table 4-7: Logical loopback interface properties

Field Description
interface.
Operational Status (read only) Operational status of the logical interface:
 Unknown: Not known.
Interface Type The type of logical interface, displayed as Loopback (loopback
(read only) interface).
Interface Index (read only) SNMP ifIndex number.
Time since state change (read only) Time since the last change in operational status.
Layer2 Protocol Name of Layer 2 protocol.
Encapsulation Logical interface encapsulation, displayed as None.
Cross Connected (read only) Whether the logical loopback interface is cross-connected.
Customer Customer assigned to the loopback interface.
Administrative Status Administrative status of the logical loopback interface:
 Enabled
 Disabled
4.13 Define TR10_4EN encryption settings
Traffic data entering or exiting the ODU2 sub-interface of the OTU2 line of TR10_4EN/TR10_12EN cards is
encrypted. You can define the encryption settings for each OTU2 line port of a TR10_4EN card.
To define encryption settings for an OTU2 line port:

1. In the Network Explorer tab, click L1 Interfaces below the relevant OTU2 line port of the
TR10_4EN/TR10_12EN card.
The LI Interfaces List appears.
2. Right-click the relevant ODU2 interface and select Properties.

The ODU2 properties window opens.
3. In the Properties tab, select the ODU Attributes tab.
4. In the Encryption Data pane, define the Peer IP and GCM Mode attributes and click Close.
NOTE: If the peer IP was already defined via NMS (during the creation of an LP/ODU trail), the
Peer IP attribute will be read-only.
The encryption settings for the OTU2 line port are saved.
4.14 Define TM200EN/TM100_2EN
encryption settings
You can define encryption settings for the TM200EN/TM100_2EN cards if an XC is created between the line
and client ports of the card.
There are various guidelines you must follow when configuring TM200EN/TM100_2EN ports. See Configure
ports.
To define encryption settings for a TM200EN/TM100_2EN card:

1. In the Network Explorer tab, right-click the relevant card and select Ports Encryption.
The Ports Encryption window opens.
2. Define the following settings for client ODUs that have XCs:
 Encryption: Select Enable to enable encryption.
 GCM Mode: Select Monitor or Standard mode.
 Peer IP: Select the NE peer IP for secure communication with the NE.
3. (optional) To define the same NE peer IP for the client ODUs cross-connected to the same line port,
select the Select Peer IP radio button in the row with the defined peer IP, and click Set selected Peer
IP to all Enable ODUs of same line.
The peer IP is updated for the relevant client ODUs.
4. Click Apply.
The encryption settings are saved.
4.15 OTDR management

OTDR is an optoelectronic device used to test the characteristic of an optical fiber. The OTDR injects a series
of optical pulses into the tested fiber and examines the light scattered or reflected back from the end of the
fiber. The strength of the return pulses is measured and integrated as a function of time.
OTDR functionality is supported in any Apollo amplifier that supports 100 Mbps OSC with an SFP, by simply
replacing the regular OSC SFP with the OTDR1_L5 transceiver. For more information, see OTDR.
You can manage OTDR using two commands:
 Start OTDR Calibration: You must run this command after installing a new fiber span and after the
fiber span is modified or repaired. This command activates the OTDR testing of the fiber span
connected to the SFP output. At the end of the calibration test, the OTDR creates a list of numbers
that represent the location of points with high reflection. This Reference list is stored by the RCP and
used to evaluate the fiber characteristics in a real test.
 Start OTDR Test: This command activates the OTDR test, which locates fiber cuts by comparing the
farthest reported point with the points in the Reference list (created by the calibration test). The test
results indicate the distance to fiber cut in kilometers.
For more information, see the Apollo Reference Manual.
4.15.1 Start OTDR Calibration

The Start OTDR Calibration command activates the OTDR testing of the fiber span connected to the SFP
output. You must run this command after installing a new fiber span and after the fiber span is modified or
repaired.
To run the Start OTDR Calibration command:

1. In the Network Explorer tab (or in Chassis view), right-click the relevant OSC port and select
Properties.
2. In the Main tab, select OTDR1_L5 from the Configured Transceiver Type dropdown list and click
Apply.
The transceiver type is updated and the OTDR buttons are enabled.
3. Click Start OTDR Calibration.

The Start OTDR Calibration command runs.
A Reference list containing the location of points with high reflection is created.
A confirmation message appears upon completion.
4.15.2 Start OTDR Test
The Start OTDR Test command activates the OTDR test, which locates fiber cuts by comparing the farthest
reported point with the points in the Reference list (created by the calibration test).
To run the Start OTDR Test command:

1. In the Network Explorer tab (or in Chassis view), right-click the relevant OSC port and select
Properties.
2. In the Main tab, select OTDR1_L5 from the Configured Transceiver Type dropdown list and click
Apply.
The transceiver type is updated and the OTDR buttons are enabled.
3. Click Start OTDR.

The Start OTDR command runs.
 If the farthest reported point is different from any of the points in the Reference list by at least
+/-25 m, it is considered a fiber cut. A message appears indicating the distance to fiber cut (in
km).
 If the farthest reported point is equal to one of the reference points +/-25 m, the farthest point
is reported as a fiber cut with a warning message stating that the results are inconclusive, and
that the fiber cut is indicated as a reference point.
 If no reflection is detected, a message appears, stating there is no information.
 If the Reference list does not exist (for example, because the OTDR calibration test was not
performed), the farthest point is reported with a warning message stating that the results are
inconclusive and that the OTDR calibration test was not performed.
 In case of time-out or any other hardware failure, a message appears, stating that the OTDR test
failed.
4.16 Run OTDR_8 tests
The OTDR_8 card is an OTDR card that can monitor up to 8 fibers (one at a time). It enables running tests to
detect, locate, and measure elements at any location on a fiber optical link.
For more information about the OTDR_8 card, see OTDR_8.
To run OTDR_8 tests:

1. If it isn't already defined, create fiber connectivity between the OTDR_8 port and the OTDRTAP port
of either an OTDR filter card or a Raman amplifier card (with an OTDRTAP port).
2. Right-click the NE on which the OTDR_8 card is assigned and select Properties.
3. In the Main tab, for OTDR File Transfer, define the Protocol and enter the STMS User ID and
Password.
NOTE: The STMS receives OTDR_8 test results in an SOR file from the NE. These settings
enable the SOR file transfer between the NE and the STMS.
4. Right-click the OTDR_8 port and select Properties.

The OTDR_8 port properties appear.
5. Open the OTDR tab.
6. If this is the first time you are running an OTDR test on this port, define the OTDR attributes. If not,
just check that they are defined correctly.
For a description of the attributes, see the table below.
7. Click the relevant test button:
 Reference Test: Runs the Reference test, which serves as a baseline for comparing future tests
on the port. Usually performed during initial setup or after changes to test conditions or
configurations.
 Regular Test: Runs the regular OTDR test. Results are compared with the Reference test.
 RAMAN Pre-Installation Test: Used for pre-installation qualifying of Raman spans.
NOTE: You can view the Reference test results and last test results by clicking the Reference
Test Results and Last Test Results buttons.
A confirmation prompt appears.

Upon confirmation, the test starts to run. The test results appear in a new window.
Table 4-8: OTDR attributes

Span Length Expected OTDR Span that will be used by the NE to calculate the Target
Dynamic Range for OTDR tests (except for the Raman Pre-Installation test that
always zooms in on the first 10km)
Peer OTDR Tap Card Type of card linked to the OTDR port. Raman for a Raman amplifier card or
Other for any OTDR filter card.
Fiber Attenuation Expected value that will be used by the NE to calculate the Target Dynamic
Coefficient Range for OTDR tests.
High Reflection Fiber Default is No. When Yes is selected, it enables operating the OTDR with
non-default test parameters, in order to achieve higher dynamic range (only
used for problematic links, for which the default settings do not provide the
expected results).
Alarm Sensitivity Default is High. When false alarms are received repeatedly for a specific
port/link, you can change the alarm sensitivity to Medium or Low. This will
change the thresholds that trigger the alarms, in order to minimize the trigger
of false alarms.
CAUTION: This can result in the masking of REAL alarm cases.
4.17 Upload SOR files from an NE

OTDR_8 test results are stored in SOR files on the NE. When you discover an NE that has SOR files, you can
upload the last SOR files from the NE.
To upload SOR files from an NE:

 In the Network Explorer tab, right-click the NE and select Actions > Upload all OTDR last SOR files.
The SOR files are uploaded.
4.18 View ONCP data
You can view ONCP data if it exists for an optical port, in table or graph format.
To view ONCP data:

1. In the Network Explorer tab (or in Chassis view), right-click the port and select Properties.
2. Select the Optical Parameters tab.
The ONCP data appears in table format in the ONCP Data/Info for Input Channels and ONCP
Data/Info for Output Channels areas.
3. To view the ONCP data in graph format, click Input Graph or Output Graph respectively.
Table 4-9:
NOTE: The Input Graph or Output Graph buttons are only enabled if ONCP data exists for the
input/output channels.
A window opens, displaying the ONCP data in graph format.

4.19 Configure LOS threshold
You can configure LOS threshold for an OTS port.
To configure LOS threshold:

1. In the Network Explorer tab (or in Chassis view), right-click the OTS port and select Properties.
2. Select the Ots Attributes tab.
3. In the Los threshold field, enter a value between -24 dBm and -40 dBm.
4. Click Apply.
4.20 Define performance margin threshold

The performance margin estimation is based on the equivalence between Bit-error-rate (BER) and system
performance (expressed as Q-value).
The known pre-FEC BER value that leads to FEC breach is expressed as Q0(dB), the Q-value that
corresponds to FEC breach.
A specific performance margin, XdB, means a Q-value of Q0+XdB. This Q-value is then translated into its
equivalent pre-FEC BER value (pre-FEC BER threshold).
An alarm is raised when the actual pre-FEC BER crosses the defined pre-FEC BER threshold.
For example, assume a transceiver with FEC breach of 1.50E-2, which is equivalent to Q-value 6.73dB, i.e.
Q0 = 6.73dB. A 3dB performance margin means Q0 = 9.73dB, which is equivalent to 1.08E-3.
In this case, an alarm is raised when the measured pre-FEC BER is worse than 1.08E-3.
You can define the performance margin threshold for the following ports:
 OTU4 port with FEC-Mode FEC/SD-FEC/SD-FEC15/SD-FEC25
 OTUCn port with FEC-Mode SD-FEC15/SD-FEC25
 OTU2/2e/3e2 port with FEC-Mode FEC/EFEC7
To define the performance margin threshold for a port:

1. In the Network Explorer tab, right-click the relevant OTU port and select Properties.
2. In the OTU Attributes tab, define the following attributes in the High Pre-FEC BER section:
 Monitor: Enables/disables High Pre-FEC BER.
 Performance Margin: Automatically defines the Set threshold and Clear threshold.
The rest of the attributes are read-only.
3. Click Apply.
The performance margin threshold is set.
4.21 View configured VPPs
Virtual packet ports (VPPs) are automatically created in the STMS when an ODU Flex trail is created from
LightSOFT. You can only view the configured VPPs from the STMS.
To view configured VPPS:

1. In the Network Explorer tab, right-click the VPP folder under the relevant OTU4 port and select Show
List.
The list of VPPs appears.
2. To view a specific VPP's configuration, right click the VPP in the list and select Properties.
The VPP Configuration window opens, displaying the VPP's configuration settings.
4.22 Port maintenance

You can run the following maintenance operations on ports:
 Running an Optical Loopback Command
 Running a Send BDI Command
 Running a Send CSF Command
 Setting Test Mode
4.22.1 Run an Optical Loopback command
NOTES:
 For ROADM_9F/ROADM_20F/ROADM_20CF cards, an Optical Loopback command can
only run on one channel at a time.
 Before running the Optical Loopback command for ROADM_9F/ROADM_20TF cards , you
must activate Tx-Rx-Loop on one of the degree ports of the card by right-clicking the
relevant port and selecting Maintenance Actions > Tx-Rx-Loop. Then physically connect
the fiber of this degree port to itself.
To run an Optical Loopback maintenance command on a port:

1. In the Network Explorer tab (or in Chassis view), right-click the relevant port and select Maintenance
Actions > Loopback.
NOTES:
 For ROADM_9F/ROADM_20TF cards, you must select the CH in the line port in order to
run the loopback command, as the optical loop runs on the OCH sub-interface of the OTS
port.
 For ROADM_20CF cards, you must select the CH in the client port order to run the
loopback command, as the optical loop runs on the OCH sub-interface of the OTS or OCHP
port.
The Loopback command starts to run. The maintenance icon appears next to the port.
4.22.2 Run a Send BDI command

To run a Send BDI command on a port:
 In the Network Explorer tab (or in Chassis view), right-click the relevant port and select Maintenance
Actions > Send BDI > Enable.
NOTE: If the Send BDI command is not available for the selected port, it will not appear in the
Maintenance Actions menu.
The Send BDI command starts to run. The maintenance icon appears next to the port.
4.22.3 Run a Send CSF command
To run a Send CSF command on a port:
Actions > Send CSF > Enable.
NOTE: If the Send CSF command is not available for the selected port, it will not appear in the
The Send CSF command starts to run. The maintenance icon appears next to the port.
4.22.4 Set Test mode

To set Test mode for a port:
Actions > Test Mode > Test.
NOTE: If Test mode is not available for the selected port, it will not appear in the
Test mode is set for the port. The maintenance icon appears next to the port.
4.22.5 Run a Delay Measurement operation

You can activate the Delay Measurement operation from LightSOFT or from the STMS. You can run a Delay
Measurement operation for ODUk ports only.
To run a Delay Measurement operation from the STMS:

1. In the Network Explorer tab, right-click the ODUk port that will be the Source port (start of the trail),
and select Properties.
2. In the Maintenance Actions section (of the Main tab), set the Delay Measurement Role attribute to
Source and click Apply.
3. In the Network Explorer tab, right-click the ODUk port that will be the Loop port (end of the trail), and
select Properties.
4. In the Maintenance Actions section (of the Main tab), set the Delay Measurement Role attribute to
Loop and click Apply.
The Delay Measurement operation starts running. The maintenance icon appears next to the
ports.
5. To view the Delay Measurement result, open the Properties of the Source port.
In the Main tab, the delay measurement appears in the Round Trip Delay Measurement field. If it
doesn't, click Refresh.
6. To stop the Delay Measurement operation, set the Delay Measurement Role attribute for both ODUk
ports to None.
5 L1-XCs
L1-XCs provide connections between transport entities (signals from tributaries or interfaces). Incoming
signals or tributaries are connected to outgoing signals or tributaries of compatible bandwidth. For
example, you can configure L1-XCs between two OTU2 ports (using ODU2 as the L1-XC endpoints), or
between an OTU2 port and up to four different OTU1 ports (using ODU1 as the L1-XC endpoints). (Detailed
connectivity rules and guidelines are provided later in this section.)
L1-XC connectivity can be configured between:
 Endpoints residing on one or more service cards with Fabric Interface Control (FIC). Cross connections
between cards run through the ODU-XC fabric, via the backplane. For example:
 Between endpoints on FIOMR_16 and FIO10_5 cards
 Between endpoints on FIOMR_16 and FIO40 cards
 Tributaries on a single service card without FIC. For example:
 ODUk L1-XCs on L1 service cards (transponders or AoC cards)
 OCH L1-XC on a Mux/DeMux card
To configure an L1-XC on a device, the physical port properties must first be configured, including slots,
cards, and supporting ports. The assumption in this chapter is that the equipment and the L1 interfaces
have already been configured.
You can create and configure L1-XCs for equipment that is already installed or for equipment that is not yet
installed. When you add the pre-configured equipment to the system (by inserting the appropriate card),
the software detects the L1-XCs and applies the configuration. You can also retrieve and modify certain L1-
XC configuration settings under certain circumstances, as described later in this section. Configurable L1-
XCs can be deleted as long as they are not in use by a trail.
5.1 L1-XC compatibility guidelines

L1-XCs can be configured between matching endpoints supporting the signal rates described in the
following table. Note that the two endpoints must be compatible in terms of rates and payloads, where
relevant.
Table 5-1: Supported signal rates for L1-XC endpoints

Endpoint Card type Connection guidelines
OMS Photonic cards Between two OTS ports
Passive optics cards
OCH Photonic cards Between two OTS or OCHP ports (any combination)
Passive optics cards Input and output wavelengths between
two OCH endpoints must be identical.

STMS User Guide L1-XCs
ODUk, L1 service cards with ODUk cross connections can be configured between ports on the same
including: FIC card, for cards without FIC, or between ports residing on the same or
ODU1 L1 service cards different cards, for cards with FIC. Cards must reside within the same
ODU2 without FIC NE, on the main platform.
ODU2e Incoming signals or tributaries are connected to outgoing signals or
tributaries of compatible bandwidth. Multiplexing signals is supported
ODU2f
for greater bandwidth efficiency. For example, up to four different
ODU3e
ODU1s can be multiplexed to an ODU2.
ODUSlot L1 service cards with Proprietary rate developed for lower-rate ports supporting less than
FIC 1.25 Gbps bandwidth, such as STM1 and ETY1G.
L1 service cards Up to two adjacent ODUSlot endpoints based in the low-rate ports on
without FIC the client side can be connected to two ODUSlot endpoints contained
within a single ODU1interface at the network side.
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.
ODUFlex L1 service cards - ODUflex (CBR) supports any possible client bit rate as a service in
AOC10B, AOC25B, circuit transport networks. CBR clients use a bit-sync mapping into
FIOMR_16B, ODUflex (239/238xthe client rate).
CMR100M XC-leg endpoints should use the same ODUFlex type (e.g. ODUF-FC400,
ODUF-FC800).
Changes in ODUFlex (CBR) XC rate are the same as in fixed ODUk.
ODUF-BBE is defined per ODUF type (e.g. ODUF-FC400-BBE,
ODUF-FC800-BBE).
OS Splitter/coupler cards Relevant for OS interfaces between passive optics ports only. When a
used for port splitter/coupler card is assigned, the NE implicitly configures the card
protection ports and interfaces and creates the appropriate number of L1-XCs
necessary to provide protection for that card. Each L1-XC is configured
with two unidirectional legs.
5.2 L1-XC modes

L1-XCs are automatically configured in one of the following modes:
 Configurable: L1-XCs that are explicitly created, edited, and deleted by users working through the
management plane. (In V2.0, configurable L1-XCs will also be created by the Control Plane.) Not all
attributes can be edited at any time. Some modifications are traffic-affecting, while others are not.
 Fixed: L1-XCs that are created automatically by the NE without operator intervention. Fixed-mode L1-
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 L1-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 L1-XC to prevent inadvertent deletion of a cross connection
in use.

5.3 L1-XC leg directionality
L1-XCs are actually containers that can hold multiple cross connect legs, where each leg represents a single
connection configured between two endpoints. A protected L1-XC can include up to four legs. An
unprotected L1-XC can include an unlimited number of legs. L1-XC legs are defined with directionality:
 Unidirectional, with up to two independent L1-XC legs configured, one in each direction, between two
endpoints. The direction is indicated by identifying the two endpoints as the starting (from-tp) and
destination (to-tp) endpoints. Note that L1-XCs configured in fixed mode always have unidirectional
legs.
 Bidirectional, with a single two-way L1-XC leg configured between the two endpoints. While the two
endpoints in a bidirectional leg are also identified as the from-tp and to-tp endpoints, these names
are not significant in the classic sense, since this is a bidirectional leg on which traffic is running back
and forth in both directions between the two endpoints. The to-tp 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.
Note that L1-XC leg directionality depends on the underlying hardware capabilities. Ports that do not
support bidirectionality cannot be configured with bidirectional L1-XC legs.
Directionality of the L1-XC leg is not dependent upon or affected by the direction of the fiber connectivity
configured for the same ports.
Directionality of the L1-XC leg is not dependent upon or affected by the direction of the trails configured for
the same ports, with one exception: a unidirectional trail must be configured over a unidirectional L1-XC.
5.4 ODU-XC fabric support

ODU-XCs are configured using fabric cards (such as FM1000 cards) to create connections between L1
service cards with FIC (such as FIO10_5, FIO40, and FIOMR_16). The ODUk cross connections are created
over an ODU-XC fabric, via the backplane. Cards must reside within the same NE on the main platform. The
following figure illustrates a typical ODU-XC configuration.
Figure 5-1: ODU-XC cross connect configuration
Incoming signals or tributaries are connected to outgoing signals or tributaries of compatible bandwidth.
For example, the following cross connections are currently supported:
 ODU1<->ODU1
 ODU2<->ODU2
 ODU2e<->ODU2e
 ODUSlot<->ODUSlot
ODUSlot is a proprietary rate developed 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.
 ODUi<->ODUktrib[m] (where i<k)
For example, the following figure illustrates a cross connection where i=2, k=3, and the ODU2 endpoint is a
tributary [0] of an OTU3 port.
Figure 5-2: ODUi <--> ODUktrib[m] cross connect configuration
 ODUitrib[n]<->ODUitrib[m]
For example, the following figure illustrates a cross connection between two tributaries of two OTU2 ports.
Figure 5-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.
5.5 L1-XC protection

L1-XCs can support a range of connectivity protection options, both unprotected and protected. During L1-
XC configuration, the NE determines whether any of the protected configurations would be applicable for
the new L1-XC. If so, the NE automatically creates an appropriate protection group object that includes the
relevant L1-XC legs.
If an L1-XC is configured with protection (and is therefore a member of a protection group), all
maintenance actions applied to that L1-XC are automatically applied to both the main cross connection and
the protection group entity. Some maintenance operations may also be applied directly to the protection
group by the user.
5.5.1 Unprotected configurations
 1-way unprotected P2P: This is the simplest type of connection. A single L1-XC leg is configured as a
unidirectional P2P connection from an input endpoint port to a compatible output endpoint port of
equal bandwidth. There is no protection built into this connection, and the corresponding L1-XC leg
running in the opposite direction can be used for a completely different service.
Figure 5-4: 1-way unprotected P2P L1-XC leg
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 5-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 5-6: 2-way unprotected P2P L1-XC leg
Note that a bidirectional cross connection may also consist of two unidirectional cross connections
managed together.
5.5.2 Protected configurations

When the L1-XC structure would support a protection configuration, the NE automatically creates the
appropriate protection group entity.
 1-way protected P2P: Two unidirectional L1-XC legs that both end at the same endpoint (to-tp). Each
protected L1-XC is associated with a single protection group.
Figure 5-7: 1-way protected P2P L1-XC leg
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 5-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 5-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 5-10: 2-way fully protected L1-XC
5.5.3 Define Y-Protection
You can define Y-protection for an LP service running between two cards.
The following example shows a high-level overview of the stages in creating a new Y-protected service.
Figure 5-11: Y-protection for service running between NE-1 and NE-2
This example illustrates creating a Y-protected LP service running between two TR10_12 cards, installed on
two different NEs, one at each end of the service. With Y-protection, three ports on each card participate in
the service configuration; one as a client port and two as line ports. Any available port on the TR10_12 card
can be used for any of the participating port roles, client or line.
Y-protection between two NEs includes two distinct paths running between the two pairs of line ports on
the NE endpoints. The signal is transmitted and received on both lines. Only one of the signals received by
the card is processed and forwarded to the client side. The choice of which signal to process is based on PM
parameters for the signal.
To define Y-protection:
1. Assign the first card to the appropriate slot in the NE.
2. Configure a client port and two line ports on the card.
3. Assign the second card, installed on the second NE endpoint.
4. Configure a client port and two line ports on the second card.
5. Perform the following procedures from LightSOFT (see the LightSOFT User Guide):
a. Create LEs for both cards installed, one on each endpoint NE.
b. Create a fiber connectivity topology link between one set of line ports.
c. Create a fiber connectivity topology link between the second set of line ports.
d. Provision an underlying trail between the first set of line ports.
e. Provision an underlying trail between the second set of line ports.
f. Provision an LP trail for the new service.
5.6 Managing L1-XCs
The L1-XC is a container that can hold one or more L1-XC legs, with any combination of directionalities,
within a single L1-XC container. Each leg is identified by a unique index number, endpoints, and direction.
The leg endpoints identify the origination and destination points for the L1-XC leg. The directionality
identifies whether this leg is unidirectional, running in one direction only, or bidirectional, running in both
directions between the two endpoints.
You can view, create, edit, and delete L1-XCs, subject to certain guidelines and rules.
5.6.1 View L1-XCs

You can view the XCs that exist for all NEs managed by the STMS. Alternatively, use the filter parameters to
filter the results to display only the XCs for a specific card or rate.
To view L1-XCs:
The XC Manager window opens, listing in detail all the XCs defined for the NE.
2. If you want to filter the results, select your criteria in the Filter Parameters area, and click Apply.
The relevant XCs are displayed in the Results area.
For ASON/WSON trails, the XC Owners parameter indicates whether the XC is managed by the Control
Plane or STMS. For information about XC owners, see Viewing XC Resource Ownership.
5.6.2 Create L1-XCs
To configure an L1-XC on a device, the physical port properties must first be configured. You can then
configure the underlying equipment, including chassis, cards, and supporting ports. The procedure varies
slightly depending on whether the cards support PT20 or PT21 granularity. PT21 granularity is available on
newer cards, and enables you to select various types of interfaces (see OTN).
To create L1-XCs:
1. From the main menu, select Tools > XC Manager.
The XC Manager window opens.
2. At the bottom of the Results area, click Create.
The Optic XC Configuration window opens.
3. In the XC Parameters area, enter the following information:

 In the NE field, select the NE from the dropdown list.
 In the Name field, enter a name for the XC.
 In the XC Rate field, select the rate that you require for the XC.
 For the Wavelength field, click Select and select the DWDM or CWDM wavelength.
 In the Type field, select the XC type (e.g. P2P Unidirectional, P2MP).
 In the Leg Directionality field, select the XC directionality (Unidirectional or Bidirectional).
 Enter information for all other fields as required (see L1-XC attributes).
4. In the tree:
a. (PT21 only) If any of the endpoints display [PT21] label next to the HO-ODU, right-click the sub-
interface and select Add LO-ODU rate (where LO-ODU rate is the rate defined in XC Rate field of
the XC Parameters area).
A new sub-interface appears in the tree of the selected rate.
b. (PT20 and PT20) Select the From tp sub-interface and To tp sub-interface and then click Add
Leg. In the XC Details area the XC Leg Info tab shows XC leg details and the Endpoints Info tab
shows details of the From tp and To tp sub-interfaces.
5. (PT21 only) In Endpoints Info tab, select From tp entry and then to select the timeslot(s) you want to
use:
a. Click Edit TS.
A window opens, showing the available timeslots and their availability. It also specifies the
number of timeslots that you should select.
b. Select the timeslot(s) that you want to use and click Finish.
6. Click Activate.
The XCs are activated and available for use.
5.6.2.1 L1-XC attributes
You can define the following additional attributes for L1-XCs.
Table 5-2: L1-XC attributes

Attribute/Keyword Options Usage guidelines
NE  Select the name of the NE
Name <string> Unique value for each L1-XC, identifying the cross
connection entity.
 Set by the user when the user creates a
configurable L1-XC.
 Assigned automatically by the NE when the NE
creates a fixed L1-XC.
Trail ID  <numeric>  Identifies the trail using this cross connection, when
 NULL in use.
(default)  Null if not in use by any trail.
 This value can be edited.
Connection Mode  configurable  All L1-XCs created explicitly by the user are
(default for configurable.
user-created L1-XCs)  All L1-XCs created automatically by the NE are fixed.
 fixed  This value cannot be edited once the L1-XC has
(default for been created.
NE-created L1-XCs)
Table 5-3: L1-XC leg attributes

Index <numeric> Unique value for each L1-XC leg. Assigned automatically
by the NE.
From Tp <string> Unique string identifying the origination point for this
L1-XC leg. Identifies the endpoint location, using the
format:
endpoint-slot/port/interface-index.
To Tp <string> Unique string identifying the destination point for this
L1-XC leg. Identifies the endpoint location, using the
format:
endpoint-slot/port/interface-index.
Directionality unidirectional This attribute identifies whether this leg is
bidirectional unidirectional, running in one direction only, or
bidirectional, running in both directions between the
two endpoints.
Note that each L1-XC can include multiple legs, where:
 A mixture of directionalities can be configured for
the various legs.
 Only one leg can be bidirectional.
 Two disjoint bidirectional legs can be included
within the same L1-XC.
 Multiple legs can be unidirectional.
This attribute is only assigned when the L1-XC container
includes multiple legs with different directionalities.
Note that when this attribute is assigned for each leg,
the directionality attribute of the L1-XC container is left
empty.
5.6.2.2 L1-XC protection groups

Protection groups are entities created to protect various types of objects, such as equipment or ports. If an
L1-XC is configured with the relevant legs, the NE automatically creates the appropriate protection group of
type traffic.
All maintenance operations completed for the L1-XC are automatically applied to the protection group.
Some maintenance operations for the protection group are applied explicitly by the user.
To modify an L1-XC protection group, see Modify a traffic protection group.
5.6.3 Modify an L1-XC

You cannot edit attributes of L1-XCs created in fixed mode. Operators are allowed to edit many of the
attributes of L1-XCs created in configurable mode. Some of these editing actions are traffic-affecting, and
some are not. If a modification to an L1-XC would be traffic-affecting, a warning message is displayed.
The following modifications do NOT affect traffic:
 Connection labels: Assigning a different user label to the L1-XC.
 Trail ID: Associating this L1-XC to a specific trail, or removing the association by resetting the value to
null. Note that modifications to one L1-XC within a trail are non-traffic-affecting for any other L1-XCs
assigned to the same trail.
 Adding a leg: Adding an additional leg to a P2MP L1-XC container is non-traffic-affecting for any other
legs in the same L1-XC. Similarly, changing a unidirectional P2P L1-XC leg to a leg in a P2MP L1-XC by
adding legs is non-traffic-affecting for the original leg.
 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.
Changes to the endpoints and direction of a cross connection are often traffic-affecting. The following
modifications affect traffic:
 Switching origin and destination endpoints: Replacing the from-tp endpoint with the to-tp endpoint
in a unidirectional L1-XC leg (and vice versa) is traffic-affecting. For example, if traffic used to run from
PointA to PointB, switching the configuration so that the traffic now runs from PointB to PointA.
 Changing a bidirectional leg to unidirectional: Reconfiguring an L1-XC leg that was originally
bidirectional so that it now carries traffic in one direction only is traffic-affecting. For example, if traffic
used to run back and forth between PointA and Point B, switching the configuration so that the traffic
now only runs from PointA to PointB.
 Changing a subset of the cross connection endpoints: Changing some (but not all) of the endpoints of
a cross connection is traffic-affecting. For example, if traffic used to run from PointA to PointB,
switching the configuration so that the traffic now runs from PointA to PointC.
 Deleting the active leg in a protected L1-XC: If an L1-XC has been configured for protection, deleting
the active leg and moving the traffic to one of the protection legs is traffic-affecting.
NOTE: If a modification to an L1-XC would be traffic-affecting, a warning message is displayed.
5.6.3.1 Non-Traffic-Affecting Modifications

The following are modifications that do not affect traffic.
 Connection labels: Assigning a different user label to the L1-XC.
 Trail ID: Associating this L1-XC to a specific trail, or removing the association by resetting the value to
null. Note that modifications to one L1-XC within a trail are non-traffic-affecting for any other L1-XCs
assigned to the same trail.
 Adding a leg: Adding an additional leg to a P2MP L1-XC container is non-traffic-affecting for any other
legs in the same L1-XC. Similarly, changing a unidirectional P2P L1-XC leg to a leg in a P2MP L1-XC by
adding legs is non-traffic-affecting for the original leg.
 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.
5.6.3.2 Traffic-Affecting Modifications
Changes to the endpoints and direction of a cross connection are often traffic-affecting. Note that if a
modification to an L1-XC would be traffic-affecting, a warning message is displayed.
 Switching origin and destination endpoints: Replacing the from-tp endpoint with the to-tp endpoint in
a unidirectional L1-XC leg (and vice versa) is traffic-affecting. For example, if traffic used to run from
PointA to PointB, switching the configuration so that the traffic now runs from PointB to PointA.
 Changing a bidirectional leg to unidirectional: Reconfiguring an L1-XC leg that was originally
bidirectional so that it now carries traffic in one direction only is traffic-affecting. For example, if traffic
used to run back and forth between PointA and Point B, switching the configuration so that the traffic
now only runs from PointA to PointB.
 Changing a subset of the cross connection endpoints: Changing some (but not all) of the endpoints of
a cross connection is traffic-affecting. For example, if traffic used to run from PointA to PointB,
switching the configuration so that the traffic now runs from PointA to PointC.
 Deleting the active leg in a protected L1-XC: If an L1-XC has been configured for protection, deleting
the active leg and moving the traffic to one of the protection legs is traffic-affecting.
5.6.4 Deletion of L1-XCs

You can only delete configurable L1-XCs that are not currently associated with and in use by a trail. You
cannot delete L1-XCs created in configurable mode if they are currently in use by a trail (i.e., trail-id is not
null). You cannot delete L1-XCs created in fixed mode. These cross connections are created and deleted
automatically by the NE.
To change the wavelength of an OCH L1-XC, or to change the payload of an ODUk L1-XC, you must delete
the original L1-XC and recreate it with the new attribute values.
STMS User Guide L1-XCs
5.7 L1-XC connection tables

The following tables list in detail the L1-XC options available for each type of port and interface.
Table 5-4: ODUk L1-XC options for OTU ports

OTU1 OTU2 OTU2e OTU2f OTU3 (future) OTU3e OTU4
OTU1 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC ODU1-XC
OTU2 ODU1-XC ODU2-XC N/A N/A ODU2-XC ODU2-XC ODU2-XC

ODU1-XC ODU1-XC ODU1-XC ODU1-XC
ODU0-XC ODU0-XC ODU0-XC ODU0-XC
OTU2e N/A N/A ODU2e-XC N/A ODU2e-XC ODU2e-XC ODU2e-XC
OTU2f N/A N/A N/A ODU2f-XC N/A N/A N/A
OTU3 ODU1-XC ODU3-XC N/A N/A ODU3-XC N/A ODU3-XC

ODU2-XC ODU2-XC ODU2-XC

OTU1 OTU2 OTU2e OTU2f OTU3 (future) OTU3e OTU4
OTU3e ODU1-XC ODU2-XC ODU2e-XC N/A N/A ODU3-XC ODU2-XC

ODU0-XC
OTU4 ODU1-XC ODU2-XC ODU2e-XC N/A ODU3-XC N/A ODU4-XC

ODU0-XC ODU1-XC
ODU0-XC
ODUF-GFP
Table 5-5: ODUk L1-XC options for Ethernet ports

OTU3
OTU1 OTU2 OTU2e OTU2f OTU3e OTU4 ETY1Gx ETY1Ge ETY1G ETY10G ETY10GOC ETY40G ETY100G
(future)
ETY 1Gx ODUSlot-XC ODUSlot-XC N/A N/A N/A N/A N/A ODUSlot-XC N/A N/A N/A N/A N/A N/A
ETY 1Ge ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC N/A ODU0-XC N/A N/A N/A N/A N/A
ETY 1G ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC N/A N/A ODU0-XC N/A N/A N/A N/A
ETY 10G N/A ODU2-XC N/A N/A ODU2-XC ODU2-XC ODU2-XC N/A N/A N/A ODU2-XC N/A N/A N/A
ETY 10GOC N/A N/A ODU2e-XC N/A ODU2e-XC ODU2e-XC ODU2e-XC N/A N/A N/A N/A ODU2e-XC N/A N/A
ETY 40G N/A N/A N/A N/A ODU3-XC N/A N/A N/A N/A N/A N/A N/A ODU3-XC N/A
ETY 100G N/A N/A N/A N/A N/A N/A ODU4-XC N/A N/A N/A N/A N/A N/A ODU4-XC
Table 5-6: ODUk L1-XC options for SDH ports
OTU1 OTU2 OTU2e OTU2f OTU3 OTU3e OTU4 STM1 STM1e STM4 STM16 STM64
STM1 ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC ODU0-XC N/A N/A N/A N/A
STM1e ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC N/A ODU0-XC N/A N/A N/A
STM4 ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC N/A ODU0-XC ODU0-XC N/A N/A
STM16 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC ODU1-XC N/A N/A N/A ODU1-XC N/A
STM64 N/A ODU2-XC N/A N/A ODU2-XC ODU2-XC ODU2-XC N/A N/A N/A N/A ODU2-XC
Table 5-7: ODUk L1-XC options for SONET ports

OTU1 OTU2 OTU2e OTU2f OTU3 (future) OTU3e OTU4 OC3 OC3e OC12 OC48 OC192
OC3 ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC ODU0-XC N/A N/A N/A N/A
OC3e ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC N/A ODU0-XC N/A N/A N/A
OC12 ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC N/A N/A ODU0-XC N/A N/A
OC48 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC ODU1-XC N/A N/A N/A ODU1-XC N/A
OC192 N/A ODU2-XC N/A N/A ODU2-XC ODU2e-XC ODU2e-XC N/A N/A N/A N/A ODU2-XC
Table 5-8: ODUk L1-XC options for FC ports

OTU1 OTU2 OTU2e OTU2f OTU3 (future) OTU3e OTU4 FC100 FC200 FC400 FC800 FC1200 FC1600 FC3200
FC100 ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC ODU0-XC N/A N/A N/A N/A N/A N/A
FC200 ODU1-XC ODU1-XC N/A N/A ODU1-XC ODU1-XC ODU1-XC ODU1-XC N/A ODU1-XC N/A N/A N/A N/A
FC400 N/A ODUF-FC400 N/A N/A ODUF-FC400 ODUF-FC400 ODUF-FC400 N/A N/A ODUF-FC400 N/A N/A N/A N/A
FC800 N/A ODUF-FC800 N/A N/A ODU2-XC ODUF-FC800 ODUF-FC800 N/A N/A N/A ODUF-FC800 N/A N/A N/A
OTU1 OTU2 OTU2e OTU2f OTU3 (future) OTU3e OTU4 FC100 FC200 FC400 FC800 FC1200 FC1600 FC3200
FC1200 N/A N/A ODU2e-XC ODU2f-XC ODU2e-XC ODU2e-XC ODU2e-XC N/A N/A N/A N/A ODU2e-XC N/A N/A
FC1600 N/A N/A N/A N/A ODUF-FC1600 ODUF-FC1600 ODUF-FC1600 N/A N/A N/A N/A N/A ODUF- N/A
FC1600
FC3200 N/A N/A N/A N/A ODUF-FC3200 ODUF-FC3200 ODUF-FC3200 N/A N/A N/A N/A N/A N/A ODUF-
FC3200
Table 5-9: ODUk L1-XC options for CBR ports

OTU1 OTU2 OTU2e OTU2f OTU3 OTU3e OTU4 VIDEO270 HDSDI1485 HDSDI3G
VIDEO270 ODU0-XC ODU0-XC N/A N/A ODU0-XC ODU0-XC ODU0-XC ODU0-XC N/A N/A
HDSDI1485 ODU1-XC ODU1-XC N/A N/A ODU1-XC 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 ODUF-SDI3G-XC N/A N/A ODUF-SDI3G-XC
6 Packet configuration
OPT99xx supports packet-switching via the HIO10_20 and HIO100_2 cards.
The following packet ports are supported:
 GE10
 GE10-OTU2E
 GE100
 GE100-OTU4
After you assign the data cards and configure the packet ports, you can perform the following configuration
operations:
 Configure L2 parameters for a packet port
 Configure Link OAM for a packet port
 View Link OAM events and statistics
 Configure the Link OAM thresholds
In addition, the OPT99xx uses a central switch. You can configure various switch settings, as described in
Switch configuration.

STMS User Guide Packet configuration
6.1 Configure L2 port parameters

To configure L2 parameters for a packet port:
1. In the Network Explorer tab, right-click the relevant packet port and select Properties.
2. In the Properties tab, select the L2 Parameters tab.
The L2 parameters appear.
3. Define the parameters as required and click Apply.

See the following table. The parameters displayed vary according to the configured port type.
Table 6-1: L2 Parameters

Type (read-only) The port mode, which can be either VLAN-Tagged or I-NNI.
Description Description of the PIF.
Ethernet Attributes
Max Packet Length The maximum packet size that can be received or transmitted on
the port.
Strict Scheduling Mode
Enables/disables strict scheduling on the PIF.
MAC Filter Defines whether the reserved MAC address is filtered or not.
TPID Profile Name The TPID profile associated to PIF.
VLAN-Tagged Attributes
Untagged Frame Handling The method used for untagged frame handling: Forward or Block.
Priority Tagged Frame The method used for priority tagged frame handling: Forward or
Block.

All to One Handling Enables/disables the all-to-one-handle-bundling on the PIF.
PVID The C-VLAN ID assigned to untagged frames received on this port
(PVID translation).
Untagged Default CoS The untagged default CoS, which ranges from 0-7.
I-NNI Attributes
Tx DEI Marking Enables/disables Tx DEI marking.
PIR
PIR Defines whether rate limit exists on the PIF. If exists, the rate limit is
defined in MBps.
Statistics
Statistics-Enable Enables/disables the collection of PM counters on the PIF.
6.2 Configure Link OAM

Configuring Link Operation, Administration, and Maintenance (OAM) enables you to monitor a link for
critical events. You can also set the remote device to Loopback mode in order to perform testing on the
link.
To configure Link OAM for a packet port:

2. In the Properties tab, select the Link OAM Configuration tab.
The Link OAM parameters appear.
3. Select the Enable OAM checkbox.

4. Define the Local Mode and Remote Mode.
5. To set the remote device to Loopback mode, select the Loopback checkbox.
6.3 View Link OAM events and statistics
To view Link OAM events and statistics:
2. In the Properties tab, select the Link OAM Events and Statistics Panel tab.
The Link OAM local and remote events and statistics appear.
6.4 Configure Link OAM thresholds

You can configure the Link OAM thresholds for the packet ports configured on the HIO10_20 and HIO100_2
cards.
To configure the Link OAM thresholds:

1. In the Network Explorer tab, select the relevant card.
The card properties appear in the right pane.
2. Select the Link OAM Threshold tab.
The default Link OAM thresholds appear for the ports configured on the card.
3. Change the thresholds as required and click Apply.
The Link OAM thresholds are saved.
6.5 Switch configuration

You can perform the following operations on the L2 switch:
 Configure switch properties
 Configure a VLAN ID Range profile
 Configure a Port TPID profile
 Configure a CoS Group Profile
 Configure a QoS profile
 Configure a Policer profile
 Configure a WRED profile
 Configure a Slow Path Policer profile
 Configure a LAG
 Configure Slow Path
 View configured VSIs
 View VSI properties
 View VSI statistics
6.5.1 Configure switch properties
To configure switch properties:
1. In the Network Explorer tab, right-click the switch for the relevant NE and select Properties.
The switch properties appear in the right pane. The Switching Mode is set to PB by default.
2. Define the switch parameters and click Apply. See the following table.
Table 6-2: Switch properties

Switching Mode PB by default.
Ethernet (PB) Network ID PB network ID.
LACP System Priority Defines the system priority for LACP (higher value = lower priority).
If both systems have the same System Priority, the system with the lowest
LAG MAC address is preferred.
CoS Defines the priority levels of COS profiles used for data traffic. You can
transfer COS profiles between the High Priority List and Low Priority List.
WRED Latency Defines the delay of WRED auto profiles per CoS.
Statistics Enable Enables/disables the collection of PM counters on the switch.
6.5.2 Configure a VLAN ID Range profile
You can configure up to 28 VLAN ID Range profiles on a switch.
To configure a VLAN ID Range profile:

2. Select the Profiles tab.
The configured profiles appear by type. The VLAN ID Range Profile is selected in the tree by default.
3. Click Create .
The Create Profile window opens.
4. Enter the profile name and define the range settings.

5. Click Apply.
The profile is created.
NOTES:
 To edit a profile, click Edit and modify the profile details.
 To delete a profile, select the profile in the list and click Delete .
6.5.3 Configure a Port TPID profile

You can configure up to 2 Port TPID profiles on a switch.
To configure a Port TPID profile:

The configured profiles appear by type.
3. Select the Port TPID Profile type in the tree.

The Port TPID profiles appear.
4. Click Create .
5. Enter the profile name and define the profile settings.

6. Click Apply.
NOTES:
 To edit a profile, select the profile in the list, click Edit , and modify the profile
details.
6.5.4 Configure a CoS Group Profile
You can configure up to 8 CoS Group profiles on a switch.
To configure a CoS Group profile:

3. Select the CoS Group Profile type in the tree.

The CoS Group profiles appear.
4. Click Create .
5. Enter the profile name and select the checkboxes for the CoSs to include in the profile.
6. Click Apply.
NOTES:
details.
6.5.5 Configure a QoS profile

The QoS profile is composed of the following profiles:
 Priority to CoS profile
 CoS to Priority profile
 DSCP to CoS profile
A default set of profiles is configured. Up to 11 QoS Group profiles can be configured on a switch.
To configure a QoS profile:

3. Select the QoS Profile type in the tree.

The QoS profiles appear.
4. Create the profiles to include in the QoS profiles as required:

 Create a Priority to CoS profile
 Create a CoS to Priority profile
 Create a DSCP to CoS profile

5. Click Create .
6. Enter the profile name, and enable DSCP classification and/or DEI Bit remarking as required.
7. Select the profiles to include in the QoS profile.
8. Click Apply.
NOTES:
details.
 You can't edit or delete the default profile.
6.5.5.1 Create a Priority to CoS profile

You can configure up to 11 Priority to CoS profiles on a switch.
To configure a Priority to CoS profile:


3. Expand the QoS Profile type in the tree.
4. Select the Priority to CoS Profile type.

The Priority to CoS profiles appear.
5. Click Create .
6. Enter the profile name and select the CoS for each priority level.
7. Click Apply.
NOTES:
details.
6.5.5.2 Create a CoS to Priority profile
You can configure up to 11 CoS to Priority profiles on a switch.
To configure a CoS to Priority profile:

4. Select the CoS to Priority Profile type.

The CoS to Priority profiles appear.
5. Click Create .
6. Enter the profile name and select the priority level for each CoS.
7. Click Apply.
NOTES:
details.
6.5.5.3 Create a DSCP to CoS profile

You can configure up to 11 DSCP to CoS profiles on a switch.
To configure a DSCP to CoS profile:

4. Select the DSCP to CoS Profile type.

The DSCP to CoS profiles appear.
5. Click Create .
6. Enter the profile name and define the DSCP to CoS mapping.
7. Click Apply.
NOTES:
details.
6.5.6 Configure a Policer profile
You can configure up to 894 Policer profiles on a switch.
To configure a Policer profile:

3. Select the Policer Profile type in the tree.

The Policer profiles appear.
4. Click Create .

6. Click Apply.
NOTES:
details.
6.5.7 Configure a WRED profile

You can configure up to 11 WRED profiles on a switch.
To configure a WRED profile:

3. Select the WRED Profile type in the tree.

The WRED profiles appear.

4. Click Create .

6. Click Apply.
NOTES:
details.
6.5.8 Configure a Slow Path Policer profile

You can configure up to 15 Slow Path profile on a switch.
To configure a Slow Path Policer profile:


3. Select the Slow Path Policer Profile type in the tree.

The Slow Path Policer profiles appear.
4. Click Create .

6. Click Apply.
NOTES:
details.
 You can't edit or delete the default profiles.
6.5.9 Configure a LAG
Two or more links can be aggregated together to form a Link Aggregation Group (LAG). A LAG is treated by
MAC clients as a single link.
A LAG can be configured for GE10, GE100, GE10-OTU2E, and GE100-OTU4 ports, with VLAN_Tagged or I-
NNI interfaces.
A single LAG can include a maximum of 8 ports.
To configure a LAG:
2. Select the LAG tab.
The list of configured LAGs appears.
3. Click Create .
The Create LAG window opens.
4. In the Aggregation Group field, enter the LAG name.

5. Select the Port Type and Interface Type.
The cards appear in the Individual Port List. To view the relevant ports, expand the cards.
6. Select and transfer two ports or more from the Individual Port List to the LAG Details list. You can
select ports from the same card or different cards.
7. Define the LAG parameters in the LAG Details list and at the bottom of the window. See the table
below.
8. Click Apply.
The LAG is created.
Table 6-3: LAG parameters

Master Port Defines the master port.
Port Name (read-only) The port name.
Distribution Enable Enables/disables distribution for the port.
LACP Enable Enables/disables LACP for the port.
 If LACP is Disabled, LACPDU will not be sent/received.
 If LACP is Enabled, LACPDU will be sent/received based on LACP Mode.
LACP Mode Defines the LACP mode for the port as one of the following:
 Active: LACPDU will be sent/received.
 Passive: LACPDU will be sent/received only if the partner’s LACP
Mode is Active (the partner sends LACPDUs).
Actor Port Priority Defines the port priority (higher value= lower priority).
LACPDU Timeout Defines the LACPDU time interval:
 Short = 1 second
 Long = 30 seconds
Min Active Links Defines the minimum number of active links in a LAG. If the number of active
links is below this value, an alarm is triggered.
Max Active Links Defines the maximum number of active links in a LAG. If the number of active
links is above this value, the low-priority port goes into standby status to
support 1:1 protection.
Actor Key Defines the unique identifier of the LAG within the PE. It must be unique per
switch.
Mac Address The MAC address automatically associated with the LAG. (Read-only)
Alarm Master Mask The alarm master mask.
Severity Profile The severity profile.
PM Monitor Enables/disables PM monitoring for the LAG.
Statistics Enable Enables/disables the collection of PM counters on the LAG.
Notes:
 To edit a LAG, select the LAG in the list, click Edit , and modify the LAG settings.
 To delete a LAG, select the LAG in the list and click Delete .
 You can't delete VPP LAGs if they exist. You can edit VPP LAG properties, but you can't add
or remove a slave.
6.5.10 Configure Slow Path

To configure Slow Path:
2. Select the Slow Path tab.
3. If Slow Path is not already configured, click Create . Only one Slow Path instance can be
configured.
The Create Slow Path window opens.
4. Define the parameters and click Apply.

The Slow Path configuration appears in the Configuration tab.
NOTES:
 To edit the Slow Path configuration, select the Slow Path entry in the list, click Edit ,
and modify the details.
 To delete the Slow Path configuration, select the Slow Path entry in the list and click
Delete .
5. To view queue priority settings for the Slow Path, select the State tab and expand the queue priority
rows.
6. To view Slow Path statistics, select the Statistics tab, and select the relevant slot.
6.5.11 View configured VSIs
To view configured VSIs:
 In the Network Explorer tab, right-click the switch for the relevant NE and select Services.
The configured VSIs appear in the VSI List tab. Up to 250 VSIs can be configured on a switch.
You can filter the list using the Filter options.
6.5.12 View VSI properties

To view VSI properties:
1. In the Network Explorer tab, right-click the switch for the relevant NE and select Services.
The configured VSIs appear in the VSI List tab.

The VSI window opens, displaying the VSI properties.
3. To view alarms for the VSI, select the Alarms tab.

The VSI alarms appear. You can select to view either current alarms or non-reported alarms by
selecting the relevant tab.
4. To view PM counters for the VSI, select the Statistics tab. See View VSI PM counters.
6.5.13 View VSI statistics

To view VSI PM counters:
1. In the Network Explorer tab, right-click the switch for the relevant NE and select Services.
The configured VSIs appear in the VSI List tab.

The VSI window opens, displaying the VSI properties.
3. Select the Statistics tab.

The statistics configuration information appears in the Configuration tab.
You can enable or disable statistics or extended statistics collection for the relevant ports in the
Statistics-Enable and Extended-Statistics-Enable columns.
4. Select the Statistics Table tab.
5. From the Display dropdown list, select the port for which you want to view PM counters.
The PM counters for the selected port appear.
7 Protection
Each Apollo platform can support one or more of the following protection types:
 Equipment protection: Protection of fabric modules and the AoC10_L2 card.
 Port protection: Protection of one or more physical ports, by the corresponding port of an adjacent
card (OPT96xx) or any card (OPT99xx).
 Traffic protection: L1 cross-connection (L1-XC) protection (e.g., ODU).
 Network traffic protection: configured at the NMS or EMS-level.
 Dual Node Interconnection (DNI) protection: configured at the NMS or EMS-level.
7.1 Equipment protection

Equipment protection is used to protect equipment such as cards. You can configure the following types of
equipment protection:
 FM protection
 Fast IOP protection for AoC10_L2 cards only
7.1.1 FM protection
FM protection provides protection for the following fabric modules:
 FM1000 in OPT9624
 xFM in OPT99xx
On shelves with fabric modules, a protection group is automatically created with N:1 protection scheme.
For example, in OPT9624, the protection scheme is 3:1, where there are three active FM1000 cards and
one standby FM1000.
When there are four active FMs, in case one FM has a failure, the standby FM becomes one member of the
active group. If there are less than three active 3 FMs, there is no protection and no service.
FM protection is non-revertive. FM protection switching is minimally traffic-affecting (<10msec).

STMS User Guide Protection
7.1.2 Fast IOP protection

You can configure Fast IOP protection for AoC10_L2 cards. Fast IOP is a protection mechanism that
performs automatic switchover in case of card failure or partial failure/malfunction. You can also perform
the switchover manually as required.
To configure IOP protection, you must assign two AoC10_L2 cards, then define one card as the protected
(Main) card and the other card as the protecting (Standby) card. The Main card is initially active, so it
receives and transmits traffic from/to CPEs (connected over LAN ports). The Standby card is initially
inactive, so it only receives traffic from CPEs.
Fast IOP is activated automatically by a trigger such as active card failure, or manually by the user. Upon the
trigger, if the current active card has a higher severity fault than the current inactive card, then a
switchover occurs, and the roles of the cards are switched. For example, if the Main card is active and the
Standby card is inactive, and BIT Failed is detected on the Main card, a switchover is performed. The
Standby card becomes the active card, and it will automatically begin to receive and transmit traffic from/to
CPEs.
Fast IOP is non-revertive. Also, Fast IOP can't be configured if I-MoE is configured (and vice versa).
After configuring Fast IOP for the AoC_L2 cards, you can define fiber connectivity for the cards (optional). If
you define fiber connectivity, you must define it for both cards.
7.1.2.1 Create a protection group of AoC10_L2 cards

To configure Fast IOP protection for AoC10_L2, you must create a protection group of the cards. The
AoC10_L2 cards must be assigned to slots 0 and 1 on an OPT9603 NE.
To create a protection group of AoC10_L2 cards:

1. In the Network Explorer tab, right-click on the AoC10_L2 card and select Show/Configure Protection.
The Protection Group Properties window opens.
2. The selected card is defined as the Main card by default. You can change the Main card by selecting
the relevant radio button in the Main Unit column.

3. Define the following parameters as required:
 Hold-Off Time: The amount of time the system should wait after a signal failure is generated
before performing protection switching. Protection switching is only activated if a signal failure
is still present at the end of the hold-off time. The hold-off time value can be set between 0-10
seconds, and can be defined in 100ms intervals. The default value is 0.
 Alarm Mask Master: Enabling the alarm mask master causes all alarms for the specified
protection group to be masked. Masked alarms do not appear in the show chassis alarms
command, or in the relevant STMS/NMS. The alarm mask master is disabled by default.
 Severity Profile: The name of the severity profile assigned to the protection group. The value is
a string of up to 255 characters. The default value is default.
4. Click Apply.
Fast IOP is configured for the AoC10_L2 cards. In the Network Explorer tab, appears next to the
Main card and appears next to the Standby (protecting) card.
5. Define fiber connectivity (optional). If you define fiber connectivity, you must define it for both the
Main card and the Standby card.
IMPORTANT: When defining fiber connectivity for the Standby card, make sure that the
Report to LightSOFT option is deselected.
Note: See Performing Protection Maintenance and Viewing Protection Alarms for additional
related actions.
7.1.2.2 Delete Fast IOP protection for AoC10_L2 cards
You can delete the Fast IOP protection configured for AoC10_L2 cards (see Create a protection group of
AoC10_L2 cards).
To delete Fast IOP protection for AoC10_L2 cards:

1. In the Network Explorer tab, right-click on the AoC10_L2 card and select Show/Configure Protection.
2. Select the Lockout Unit checkbox (for either card) and click Apply.
The Main card becomes the active card.
Note: The Lockout Unit operation switches the active role to the Main card regardless of the
Main card's presence. This operation is traffic-affecting, so you must verify that the Main card
is present and alarm-free before running it.
3. Verify that the Main card is functioning.

4. Click Delete Protection.
Fast IOP protection is deleted for the cards. The Standby card's configuration is automatically deleted,
and the Switching Mode is set to PB.
7.2 Port protection

NE port protection is used to protect against card or module failures. It enables service continuation in the
event of failure or extraction of the service source/sink card or module/transceiver.
Port protection is supported on the following ports:
 L1 Service ports in OPT96xx and OPT99xx. See IOP protection for L1 ports.
 Physical packet ports in OPT99xx. See IOP protection for physical packet ports.
On a single protection card pair, you can choose to protect selected service ports or all service ports, using
protection groups. A protection group defines a protection switching relationship between the ports,
where one or more standby (backup) ports provide protection for one or more active ports.
For each protection group, the two client ports (preferably one on each card) are connected to the cli ent’s
equipment via an external splitter/coupler, and send traffic to both lines via the splitter. The main port
laser is set to ON, and the protecting port laser remains OFF. In the event of a failure, a protection switch is
achieved by changing the laser state on both ports, so that the new active port laser is set to ON.
You must explicitly configure a port protection group, associating the two ports. Configuration is performed
on the main port, and the relevant configuration parameters are copied to the protecting port.
7.2.1 Port association guidelines

To associate client ports for protection, use the following guidelines:
 The ports use only optical transceivers.
 The ports must be configured with the same port type.
 The port on the left/top card is automatically configured as the main port, and the configuration is
copied to the protecting port on the right/bottom card. Any subsequent configuration changes are
performed on the main port, and then copied to the protecting port.
 Once a protection group is created, the role of protection group members can't be changed.
Additional guidelines for OPT99xx:
 Port protection can be configured on the same card or on two different cards (do not have to be
adjacent).
Additional guidelines for OPT96xx:
 Ports in a protected pair must have the same port number.
 The relevant cards must be located in adjacent slots, as follows:
Table 7-1: OPT96xx adjacent slots

Platform Type Slot numbers
OPT9608 Single
0:2, 1:3, 4:6, 5:7
Wide
Card pairs are a subgroup of the regular cards: 0:2, 4:6
Double
2:3, 6:7
Quad
2:6
OPT9624 Single 0:2, 1:3, 4:6, 5:7, 12:14...21:23
Wide Card pairs are a subgroup of the regular cards 0:4, 12:16...1:5
Double 0:1, 4:5...20:21
Quad 0:4
OPT9603 Single 1:2

7.2.2 IOP protection for L1 ports
In IOP protection configuration, for each client traffic protection group in transmit (ingress) direction the
trail is split into two independent routes (bridging) and the service is sent to two client ports on two
different cards. On the egress side a selection is made between the two incoming routes, according to the
incoming signal and BIT quality.
When supporting both traffic protection and IOP, switching criteria vary according to the XC objects and/or
equipment failure. For example, ODU failures in case of OTN, or BIT failures in case of IOP.
7.2.2.1 Create a protection group of L1 ports (OPT99xx)

You can define IOP protection for L1 ports in OPT99xx by creating a protection group.
Note: When port protection is configured, you can only create a protected XC. Creation of P2P
XCs is disabled.
To create a port protection group:

1. Right-click on the relevant port and select Show/Configure Protection.
Note: The Show/Configure Protection option is only available for ports that support
protection.
2. In the Unit column, select the associated port for protection. The port can have a different number,
and can be on the same or on a different card.
3. In the Main Unit column, select the unit that will function as the Main unit.
Note: By default, the first port you select is defined as the master port as well as the main port
(unit). You can change the associated port to the main port, but the first port will remain the
master port.
The master port is the configurable port, and its data is copied by the NE to the slave port
(where the data can't be modified). The name of the protection group is the name of the
master port (appears in the window title).
The main port is the active port. If revertive protection is enabled, it is the port to which the
NE returns after failure and recovery.
Note: Changing the main unit is not traffic-affecting. However, in some circumstances, it may
cause a protection switch event (traffic affecting <50msec).

 Revertive: Define protection as either revertive or non-revertive. (The default value is No for
non-revertive.)
 Revertive: The main path has priority over the protection path. In the event of a failure,
when the main path is restored, the protected path reverts to the main path.
 Non-revertive: The main and protection paths have equal precedence. Therefore, there is
no need to return to the main path after recovery.
 WTR Period: The Wait to Restore (WTR) period is the number of minutes a failed unit should be
without fault before it can be used again as the active unit. WTR is used to prevent frequent
protection switching due to an intermittent fault. The WTR value can be between 0-12 minutes.
The default value is 5 minutes.
5. Click Apply.
The protection group is created.
7.2.2.2 Create a protection group of L1 ports (OPT96xx)
You can define IOP protection for L1 ports in OPT96xx by creating a protection group.

The Protection Group Properties window opens, displaying the two associated ports.
The main unit is defined by the following system defaults:

 In OPT9608, the left port is defined as the main unit by default.
 In OPT9624, the upper port is defined as the main unit by default.
 In OPT9603, u1 is defined as the main unit by default.
NOTE: Changing the main unit is not traffic-affecting. However, in some circumstances, it may
cause a protection switch event (traffic affecting <50msec).

non-revertive.)
 Revertive: The main path has priority over the protection path. If the main path has equal
or better signal than the protection path, it is used. In the event of a failure, when the
main path is restored, the protected path reverts to the main path.
 Non-revertive: The main and protection paths have equal precedence. Switching between
paths only occurs if the active path’s signal quality is lower than the non-active path.
3. Click Apply.
7.2.3 IOP protection for physical packet ports

IOP protection provides an alternative resiliency mechanism for connectivity between the customer
equipment and packet-switching Apollo shelf (OPT99xx). The solution is relevant for Ethernet ports using
optical transceivers only.
The following diagram shows the IOP protection solution.
Figure 7-1: IOP protection for physical packet ports
The active port (A) represents the actual port that is active, and can be either the main/protected port or
the standby/protecting port in the protection group.
Only the active port (A) receives and transmits packets, whereas the packets received by the inactive port
(IA) are discarded, and Tx laser is turned off.
The ports connected to the splitter coupler can reside on different cards or on the same card (e.g. for
shelves that don’t have redundant IO cards).
When a failure is detected on the active port, the inactive port becomes active.
The following cards and ports support IOP protection:
 OPT99xx cards: HIO10_20, HIO100_2
 Physical packet port types: GE10, GE10-OTU2e, GE100, GE100-OTU4
To configure IOP protection for physical packet ports:
1. Configure two ports using the following guidelines:
 The ports must have the same port type and interface type.
 The ports are on the same IO card or different IO cards.
2. Define fiber connectivity between the ports and splitter coupler.
3. Create a protection group consisting of the main/protected port and the standby/protecting port
using the following guidelines:
 Both ports do not have any services on them.
 The ports are not LAG members.
 TX laser is ON for the active port, and OFF for the inactive port.
7.2.3.1 Create a protection group of physical packet ports

Configure IOP protection for physical packet ports in OPT99xx by creating a port protection group.

Note: The Show/Configure Protection option is only available for ports that support
protection.
3. In the Main Unit column, select the unit that will function as the Main unit.
Note: By default, the first port you select is defined as the master port as well as the main port
(unit). You can change the associated port to the main port, but the first port will remain the
master port.
The master port is the configurable port, and its data is copied by the NE to the slave port
(where the data can't be modified). The name of the protection group is the name of the
master port (appears in the window title).
The main port is the active port. If revertive protection is enabled, it is the port to which the
NE returns after failure and recovery.

non-revertive.)
 Revertive: The main path has priority over the protection path. In the event of a failure,
when the main path is restored, the protected path reverts to the main path.
 Non-revertive: The main and protection paths have equal precedence. Therefore, there is
no need to return to the main path after recovery.
5. Click Apply.
7.2.3.2 Modify a protection group of physical packet ports

You can change the protecting port in a protection group of physical packet ports at any time.
To modify a port protection group:

3. Click Apply.
The protection group is updated.
7.3 Traffic protection
Traffic protection, also called SNCP protection, is a bridge or switch point within a trail. A traffic protection
group is created automatically by the NE, and can only be modified by the user.
In the transmit direction, the trail is split into two independent routes (bridging), and the service is sent to
two client ports on the egress side of the NE. On the receive (egress) side, a selection is made between
these two incoming routes (switching), according to protection switching criteria that are based on
incoming signal quality and module (e.g. SFP, XFP) extraction.
SNCP protection is supported on:
 ODU-XC endpoints in OPT99xx and OPT96xx
 OCH-XC endpoints in OPT96xx only
L1-XCs can support a range of connectivity protection options, both unprotected and protected. During L1-
XC configuration, the NE determines whether any of the protected configurations would be applicable for
the new L1-XC. If the possibility of protection exists within the L1-XC configuration, the NE automatically
creates an appropriate traffic protection group object that includes the relevant L1-XC legs. In v12.1 and
higher, a traffic protection group is created automatically for all applicable protected configurations. The
XCs can be created implicitly during the assignment process or explicitly by the user.
Traffic protection can be configured as revertive or non-revertive.
7.3.1 Modify a traffic protection group of L1-XCs (OPT99xx)

If an L1-XC is configured with the relevant legs, the NE automatically creates a traffic protection group. You
can modify a traffic protection group as required.
To modify a traffic protection group:

The XC Manager window opens, listing the XCs defined for the NE.
2. Select the relevant XC and select the Protection Group tab (in the bottom pane).
The list of defined traffic protection groups appears.
3. Select the protection group you want to modify and click Edit.
The Edit Protection Group window opens, displaying the two associated L1-XCs.
4. You can change the XC defined as the main unit by selecting the relevant radio button in the Main
Unit column.
NOTES:
 The L1-XC leg with the lowest index is defined as the main unit by default.
 Changing the main unit is traffic-affecting.
5. You can change the value in the Hold-Off Time column for each XC separately. The hold-off time is the
amount of time the system should wait after a signal failure is generated before performing
protection switching. Protection switching is only activated if a signal failure is still present at the end
of the hold-off time. Its value can be set between 0-10 seconds, and can be defined in 100ms
intervals. The default value is 0.
If each XC has a different value, a "Mixed" value appears for the Hold-Off Time in the Protection
Group tab of the XC Manager window.
6. Modify the following parameters as required:
non-revertive.)
7. Click Apply.
The protection group settings are updated.
7.3.2 Modify a traffic protection group of L1-XCs (OPT96xx)

If an L1-XC is configured with the relevant legs, the NE automatically creates a traffic protection group. You
can modify a traffic protection group as required.
To modify a traffic protection group:

The XC Manager window opens, listing the XCs defined for the NE.
2. Select the relevant XC and select the Protection Group tab (in the bottom pane).
The list of defined traffic protection groups appears.
3. Select the protection group you want to modify and click Edit.
The Edit Protection Group window opens, displaying the two associated L1-XCs.
4. You can change the XC defined as the main unit by selecting the relevant radio button in the Main
Unit column.
NOTES:
 The L1-XC leg with the lowest index is defined as the main unit by default.
 Changing the main unit is traffic-affecting.
5. Modify the following parameters as required:

non-revertive.)
6. Click Apply.
The protection group settings are updated.
7.4 Protection maintenance

You can use maintenance commands to force switching between main or protection units, when required.
Maintenance commands are executed based on priority. If the maintenance command has a higher priority
than the current command, the current command is cleared, and then the maintenance command is
activated. If a command with a higher priority than the maintenance command exists, the maintenance
command is not executed, and a rejection message is displayed.
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.

The following protection maintenance operations are available:

 Protection Lockout: A protection lockout command prevents protection switching from main to the
specified protecting unit, regardless of the state of the main unit. (For fabric cards, this command
prevents the system from using the card as part of an active FM set.)
Lockout clears all externally initiated switch commands and WTR at the protected unit to which the
command was addressed. If any service traffic is using the protecting unit at the time that the
command is applied, service traffic is switched back to the main unit, regardless of its condition.
NOTE: Lockout can only be applied to a one unit in a protection group at any given time.
Lockout is persistent and has the highest priority of any FM switchover criteria.
 Forced Switch: A forced switch to protection command forces a switch from main to protection units.
It takes priority over any service failure (SF) or service degraded (SD) alarm. Switching occurs,
regardless of the status of the protecting unit.
A manual switch cannot be performed if a lockout command or forced switch command has already
been applied.
NOTE: The manual switch over command can be overridden by any service failure (SF), or
service degraded (SD) alarm, or a command of higher priority.
 Manual Switch: Manual switch enables you to switch from the currently active unit to the other unit,
unless a higher priority request has been received. This command has a lower priority than Signal
Failure or Signal Degraded errors, and a higher priority than WTR. A manual switch cannot be
performed if a lockout command is already applied. A message is displayed if the command cannot be
executed.
NOTE: The manual switch over command can be overridden by an error or a command of
higher priority.
The following manual operations can also trigger a switchover, if required:

 Resetting a module: For equipment protection, if a module is reset, the other three modules are
automatically switched to active.
 Powering off a module: For equipment protection, if a module is powered off, the other three
modules are automatically switched to active.

7.4.1 Perform protection maintenance
To perform protection maintenance:
 For equipment protection, right-click on the relevant card and select Show/Configure
Protection.
 For port protection, right-click on the relevant port and select Show/Configure Protection.
 For traffic protection, in the XC Manager, select a protection group (from the Protection Group
tab) and click Edit.
The Edit Protection Group window opens.
2. Perform one of the following maintenance operations:
 To run a Protection Lockout command for a unit, select the checkbox in the Lockout Unit
column for the relevant unit and click Apply.
 To run a Forced Switch to Protection command, select the checkbox in the Force Switch Unit
column for the relevant unit and click Apply.
 To perform a manual switch, change the unit that is not defined as the main unit to be the main
unit and click Manual Switch.
7.5 View protection alarms

To view protection alarms:
2. Select the Alarms tab.
The protection alarms appear.
7.6 FM fabric status
You can view the status of the FM fabric modules. You can also view a more detailed status, that includes
details about the FM cards that are currently working. The detailed FM fabric status can aid
troubleshooting, and it also enables you to view the connectivity between the fabric card and the I/O
module. In the event that there is a loss of connectivity between a fabric card and the I/O module, all errors
related to the fabric module are displayed in the detailed status, including link failure alarms.
The status includes the following information:
Table 7-2: FM fabric status information

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.
8 Fiber connectivity
Fiber connectivity defines the characteristics of the connectivity between ports connected via physical
fibers. Defining fiber connectivity provides the following benefits:
 Power equalization: fiber connectivity is essential for ports participating in power equalization to pass
power control parameters to one another (e.g., ports residing in passive optics cards, optics cards and
WDM ports on L1 service cards). With the exception of passive optics cards, these ports cannot
transmit traffic if fiber connectivity configuration is missing. For all other cards, fiber connectivity is
optional.
 Diagnostic information: provided via ONCP (Optics Network Control Parameters).
 Top Down Trail application: Links and trails can be created in the NMS and their configuration sent to
STMS. The STMS can then send the configuration to the NE.
Fibers can be connected in one of the following ways:
 Intra-fiber connectivity (internal): fibers are connected with an NE. For example connectivity between
cards residing in the same chassis, or between an Apollo card and an Artemis (passive) optical card.
Fiber connectivity parameters defined on one port are automatically copied to the peer port.
 Inter-fiber connectivity (external): Fiber connectivity between two different NEs. Fiber connectivity
parameters must be defined on the NEs at both endpoints of the fiber.
The following figure illustrates the two types of fiber connectivity.
Figure 8-1: Fiber Connectivity
Fiber connectivity must be defined on the following ports:

 OTUk
 OTS
 OCHP
NOTE: OTUk, OTS, and OCHP ports cannot transmit traffic, and power equalization is not
possible unless fiber connectivity is defined.

STMS User Guide Fiber connectivity
8.1 Fiber connectivity prerequisites

and guidelines
The following prerequisites and guidelines should be adhered to when configuring fiber connectivity.
 Before configuring fiber connectivity, configure the relevant ports.
 For a bidirectional port, up to two unidirectional fibers can be defined per port. For a unidirectional
port, only a single fiber of the applicable direction can be applied.
 When configuring intra-fiber connectivity, it is not necessary to explicitly configure both peer ports.
Configure fiber connectivity parameters on one peer port and the NE automatically configures fiber
connectivity parameters on the other port.
 It is possible to define fiber connectivity without specifying a wavelength value. For inter-connectivity,
if the wavelength value is defined at one end, the NE automatically configures the wavelength value
in the corresponding peer port during configuration.
 Apollo ports are bidirectional, and XDM ports are unidirectional. When creating fiber connectivity
between Apollo and XDM NEs, it is important to create the topology link in LightSOFT so that the fiber
connectivity in the Apollo NE is automatically created as unidirectional.
If you create fiber connectivity between Apollo and XDM NEs in the STMS before they are created in
LightSOFT, you must define two unidirectional fiber connectivity links. Otherwise, the topology link
creation over the port in LightSOFT will fail.
8.2 Define fiber connectivity

Fiber connectivity configuration is part of the chassis configuration.
To define fiber connectivity:

1. From the NE Chassis view, right click on the port for which fiber connectivity needs to be defined, and
select Create Fiber Connectivity.
2. Select the fiber directionality (Unidirectional In, Unidirectional Out, or Bidirectional) and connectivity
type (Internal or External).

The Create Fiber Connectivity window opens.
The connectivity type and directionality can be changed from this window if needed.
3. Select the fiber rate from the Rate dropdown list.
4. Define the A>Z (input) and Z>A (output) wavelengths:
a. Click Select.
The Wavelength Selection window opens.
b. In the DWDM or CWDM tab, select the wavelength and click Finish.
5. Define a Label (optional).
6. If the operation needs to be reported to LightSOFT, select Report to LightSOFT.
7. Define the parameters in the Power Equalization Parameters area:
 Fiber type: g652, g653, g654, g655-leaf, g655-tw-rs, g655-tw-reach, or multimode
 A>Z (input) and Z>A (output) fiber loss: default value = 0; possible values = 0-100; resolution =
0.1
 Fiber length: intra-fiber connectivity values 0-500; resolution = 0.1
 Allowed fiber loss margin: the margin of fiber loss allowed before an alarm is raised (in dB).
Default: intra-fiber connectivity = 0.1; inter-fiber connectivity = 3, and resolution = 0.1. Possible
intra-fiber connectivity values = 0-7.
 PMD (Polarized Mode Dispersion): 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.)
8. From the graphical network tree, select the Z-end (peer) NE, slot, and port.
9. Click Apply.
The fiber connectivity is defined.
NOTES:
 When deleting fiber connectivity, configuration must be deleted on both peers.
 Modifying fiber connectivity does not affect xc connectivity.
8.3 Define fiber connectivity for non-ShadeTree

equipment
You can define fiber connectivity for NEs that are not managed by ShadeTree, such as the XDM platform, or
for third party equipment.
NOTE: Apollo ports are bidirectional, and XDM ports are unidirectional. When creating fiber
connectivity between Apollo and XDM NEs, it is important to create the topology link in
LightSOFT so that the fiber connectivity in the Apollo NE is automatically created as
unidirectional.
If you create fiber connectivity between Apollo and XDM NEs in the STMS before they are
created in LightSOFT, you must define two unidirectional fiber connectivity links. Otherwise,
the topology link creation over the port in LightSOFT will fail.
Alien lambdas are third party WDM transceivers that are connected directly to the Apollo equipment, but
are not managed by the Apollo NMS. The NE can monitor all types of lambdas. Lambdas that are not used
by the Apollo equipment can be blocked. The following figure shows an example of alien lambdas.
NOTE: Configuring alien lambda ports is a fully integrated add-on capability that is available
on a cost basis. The feature and related menus are available if a license has been purchased,
the license is current and has not exceeded its limits. (For more information, see Manage
licenses in the STMS Getting Started and Administration Guide.)
Alien lambdas are included in the power equalization mechanism.

To define fiber connectivity for non-ShadeTree equipment:
1. In the Create Fiber Connectivity window (see Defining fiber connectivity), select External for the
Connectivity type.
2. For Directionality, select Unidirectional or Bidirectional.
3. For the Z-End, select Unmanaged.
4. For the Peer NE, select Unspecified.
NOTE: All other attributes should be defined as null and cannot be modified.
To enable monitoring of alien lambdas:

1. In the Create Fiber Connectivity window (see Define fiber connectivity), select the Advanced tab.
2. Select the WDM type: CWDM, DWDM, or Non-colored.
3. Select the Spacing: 20 nm (for CWDM) or 50/100 GHz (for DWDM).
4. For Alien Lambda, select yes or no to define whether to monitor alien lambdas.
8.4 View fiber connectivity for an NE

To view fiber connectivity settings for an NE:
 Right click on the NE in the Network Explorer tab and select Show Fiber Connectivity.
The Fiber Connectivity Manager window opens, showing the fiber connectivity settings defined for
the NE.
Figure 8-2: Fiber Connectivity Manager window
8.5 Fiber/port connectivity rules

The following table describes the fiber connectivity rules for OTN technology.
Table 8-1: Fiber connectivity rules for OTN technology

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 N N N N N
PO Y Y Y Y Y Y Y Y N N N N N
OSC100M N N Y N N N N N N N N N Y
OSC2M N N N Y N N N N N N N N Y
OSChannel N N N N N N N N N N Y Y N
Table 8-2: Fiber connectivity rules for OTUCn ports
OTUC2 OTS OCHP PO OSC100M OSC2M OSC1G OSChannel
OTUC2 Y N Y Y N N N N
OTS N Y N Y N N N N
OCHP Y N Y Y N N N N
PO Y Y Y Y N N N N
OSC100M N N N N N N N Y
OSC2M N N N N N N N Y
OSC1G N N N N N N N Y
OSChannel N N N N Y Y Y N
The following table shows the fiber connectivity rules for SDH technology.
Table 8-3: Fiber connectivity rules for STM technology

STM1 STM1e STM4 STM16 STM64 PO
STM1 Y N N N N Y
STM1e N Y N N N Y
STM4 N N Y N N Y
STM16 N N N Y N Y
STM64 N N N N Y Y
PO Y Y Y Y Y N
The following table shows the fiber connectivity rules for SONET technology
Table 8-4: Fiber connectivity rules for SONET technology

OC3 OC3e OC12 OC48 OC192 PO
OC3 Y N N N N Y
OC3e N Y N N N Y
OC12 N N Y N N Y
OC48 N N N Y N Y
OC192 N N N N Y Y
PO Y Y Y Y Y N
The following table shows the fiber connectivity rules for FC technology.
Table 8-5: Fiber connectivity rules for FC technology

FC100 FC200 FC400 FC800 FC1200 FC1600 FC3200 PO
FC100 Y N N N N N N Y
FC200 N Y N N N N N Y
FC400 N N Y N N N N Y
FC800 N N N Y N N N Y
FC1200 N N N N Y N N Y
FC1600 N N N N N Y N Y
FC3200 N N N N N N Y Y
The following table shows the fiber connectivity rules for Ethernet technology.
Table 8-6: Fiber connectivity rules for Ethernet technology

GE GE10 GE10-OTU2e GE100 GE100-OTU4 ETY1G ETY1Ge ETY10G ETY10GOC OCHP PO
GE Y N N N N Y Y(note) N N N Y
GE10 N Y N N N N N Y Y Y Y
GE10-OTU2e N N Y N N N N N N Y Y
GE100 N N N Y N N N N N Y Y
GE100-OTU4 N N N N Y N N N N Y Y
ETY1G Y N N N N Y N N N N Y
ETY1Ge Y(note) N N N N N Y N N N Y
ETY10G N Y N N N N N Y N N Y
ETY10GOC N Y N N N N N N Y N Y
PO Y Y Y Y Y Y Y Y Y Y Y
Fiber connectivity can also be defined between GE10-OTU2e and OTU2e ports, and between GE100-OTU4
and OTU4 ports.
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 this port
The following table shows the fiber connectivity rules for CBR technology.
Table 8-7: Fiber connectivity rules for CBR technology

VIDEO270 HDSD1485 PO
VIDEO270 Y N Y
HDSD1485 N Y Y
PO Y Y N
9 Customer management
You can perform the following customer management operations using the STMS:
 Create a customer
 View customer information
 Modify customer information
 Import customer information
 Export customer information
 Delete a customer
 Generate customer reports
9.1 Create a customer

To create a customer:
1. In the Customer Explorer tab, right-click the Customers folder, and click Create Customer.
The Create Customer window opens.
2. In Company Name field, type a name for the customer.

3. (Optional) In the corresponding fields, type additional customer information.
4. Click Finish.

STMS User Guide Customer management
9.2 Modify customer information

To modify the information for a customer:
1. In the Customer Explorer tab, right-click the corresponding customer folder, and select Properties.
The property sheet for that customer opens.
2. In the corresponding fields, type the customer information, or leave the information unchanged.
3. Click Apply.
9.3 Customer import and export

Customer information can be imported from, or exported to, XML files in the reports directory on the STMS
server. The default directory for customer XML files is the /reports directory in the STMS root directory.
9.3.1 Import customer information

You can import customer information from XML files in the reports directory on the STMS server. The
default directory for customer XML files is the /reports directory in the STMS root directory.
To import customer information:

1. In the Customer Explorer tab, right-click the Customers folder, and click Import Customers.
The Customer Import window opens.
2. Enter the file name of the XML file from which you want to import customer information.
3. Click OK.
The customer information contained in the specified file is added to the Customers folder in the
Customer Explorer tab.
9.3.2 Export customer information

You can export customer information to XML files in the reports directory on the STMS server. The default
directory for customer XML files is the /reports directory in the STMS root directory.
To export customer information:

1. In the Customer Explorer tab, right-click the Customers folder, and click Export Customers.
The Customer Export window opens.
2. Enter the file name of the XML file to which you want to export customer information.

3. Click OK.
Information for all customers in the Customers folder is saved to the specified XML file.
9.4 Customer reports

The STMS provides a variety of reporting options, including detailed customer reports. You can generate
the following types of customer reports:
 Customer Report: Displays pertinent information about the logical interfaces and E-Line services
assigned to customers. It can be generated for all customers in the Customers folder or a single
customer. See Generate a Customer Report.
 Interface Utilization: Displays utilization information about the interfaces assigned to a customer for a
specified interval. It can be generated for a single customer. See Generate an Interface Utilization
Report.
All of the generated customer reports are saved in HTML format to the reports directory on the STMS
server. The default reports directory is the /reports directory in the STMS root directory.
NOTE: For information about STMS reporting options, see the STMS Performance
Management Guide.
9.4.1 Generate a Customer Report

To generate a Customer Report:
 To save a report for all customers, in the Customer Explorer tab, right-click the Customers
folder and click Customer Report.
 To save a report for a single customer, in the Customer Explorer tab, right-click the
corresponding customer folder, point to Reports, and then click Customer Report.
The Generate Report window opens.
2. Type a file name for the report.
3. Click Save.
9.4.2 Generate an Interface Utilization Report
To generate an Interface Utilization Report:
1. In the Customer Explorer tab, right-click the corresponding customer folder, point to Reports, and
click Interface Utilization.
The Generate Report window opens.
2. Type a file name for the report.
3. Click OK.
The Report Interval window opens.
4. In the Start date field, type a start date (in the form MM/DD/YYYY) or click the Calendar button ( )
and select a start date.
5. From the corresponding Time list, select a start time.
6. In the End date field, type an end date (in the form MM/DD/YYYY) or click the Calendar button ( )
and select an end date.
7. From the corresponding Time list, select an end time.
8. Click OK.
9.5 Delete a customer

To delete a customer:
 In the Customer Explorer tab, right-click the corresponding customer you want to delete, and click
Delete.
When you delete a customer, the interface and services that were assigned to that customer are
moved to the Carrier Resources folder.
9.6 View customer information
To view customer information:
 In the Customer Explorer tab, right-click the customer folder and select Properties.
The customer information appears.
Table 9-1: Customer information

Field Description
Customer Name Name of customer
Street 1 Street address
Street 2 Additional address information
City City name
State State or province name
Field Description
Zip Zip or postal code
Country Country name
Name Name of customer contact
Email E-mail address
Phone Telephone number
Fax Fax number
URL Web address

STMS V8.2 User Guide-đã chuyển đổi

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

STMS V8.2 User Guide-đã chuyển đổi

Uploaded by

Copyright:

Available Formats

STMS

ECI's management applications run on VMWare virtualization hypervisors.

© Copyright by ECI, 2012-2017. All rights reserved worldwide.

ECI Telecom Ltd. Proprietary iii

2.7 Check network connectivity................................................................................................2-12

ECI Telecom Ltd. Proprietary iv

2.24.5 Create a new NE certificate....................................................................................................2-33

ECI Telecom Ltd. Proprietary v

2.28.1 View NE event logs.................................................................................................................2-50

3 Cards and modules.......................................................................................3-1

ECI Telecom Ltd. Proprietary vi

ECI Telecom Ltd. Proprietary vi

4 Ports and interfaces......................................................................................4-1

ECI Telecom Ltd. Proprietary vi

4.15.1 Start OTDR Calibration............................................................................................................4-22

ECI Telecom Ltd. Proprietary ix

6.5.1 Configure switch properties.....................................................................................................6-6

ECI Telecom Ltd. Proprietary x

ECI Telecom Ltd. Proprietary xi

ECI Telecom Ltd. Proprietary xii

1.1 Group configuration

1.1.1 Create a group

ECI Telecom Ltd. Proprietary 1-1

1.1.2 Move a group

1.1.3 Delete a Group

ECI Telecom Ltd. Proprietary 1-2

1.2.1.1 Verify STMS server data

10.0.4.130 6336 true CONTACTING

1.2.1.2 Discover NEs

1.2.1.3 Discover NEs using an IP range from file

1.2.2 NE discovery via the STMS discovery utility

To use the STMS discovery utility:

Table 1-1: Command options and arguments

To define the NE ID on the NE:

1.3 Define STMS server data

NOTE: Assigning an NE to multiple STMS server instances is not supported.

To define STMS server information on an NE:

To view STMS Domain properties:

Table 1-2: STMS domain properties

1.5 View SNMP settings

Table 1-3: SNMP settings

To define the configuration files directory:

1.7 Define STMS performance parameters

To define STMS performance parameters:

Table 1-4: STMS performance parameters

1.8 Maintain historical alarms

To maintain historical alarms:

2.1 NE implicit configuration

2.1.1 Equipment implicit configuration

ECI Telecom Ltd. Proprietary 2-1

2.1.2 Controller cards implicit configuration

2.1.3 Severity profiles implicit configuration

2.1.4 PM threshold profiles implicit configuration

2.1.5 Cross connection implicit configuration

ECI Telecom Ltd. Proprietary 2-2

2.1.7 Transport entities implicit configuration

2.2 Configure an NE using Plug and Play

To configure an NE using the Plug and Play tool:

2. Click Select and browse for the XML file.

5. Click Yes to configure the NE anyway, and click No to cancel.

The following fields appear in the NE Properties tab.

Table 2-1: NE Properties

2.4 View NE operational status

To open a Telnet session to an NE: