A marine speed log fitted on ships for finding and indicating ship's speed through water. It is a mandatory SOLAS equipment for all ships above GT of 300
reparación motor YD22
EM EMAMI MCOM PART2 PROJECTFull description
Knife FightingFull description
RELATÓRIO CURRICULAR SUPERVISIONADO EM CONTROLE DE QUALIDADE EM MEDICAMENTOSFull description
Guia de palavras da língua italiana para ser utilizado durante viagens à Itália.Descrição completa
Intervenções baseadas em mindfulnessDescrição completa
Guia de palavras da língua italiana para ser utilizado durante viagens à Itália.
ColhedoraDescrição completa
Guia de palavras da língua italiana para ser utilizado durante viagens à Itália.
Validação da versão em portugues de um questionário para avaliaçãode autismo infantil (dissertação)Descrição completa
Descripción: Guia de palavras da língua italiana para ser utilizado durante viagens à Itália.
Descrição: RS prazer em conhecê-lo - Barbosa Lessa
Vivemos em tempos de crescente agitação. A informação, surgindo de todos os lados, ganha ares de avalanche. A violência, seja urbana ou rural, física, simbólica ou virtual, toma os espaços e espalha tristeza e medo, quando não terror.
Neste cenário
FSP 3000R7 Element Manager
User Manual
Product Release 10.3 Document Issue: B (July 2011)
Installing the Element Manager . . . . . . . . . . . . . . . . How to Install on a Windows Platform. . . . . . . . . . How to Install on a Solaris Platform . . . . . . . . . . . How to Uninstall. . . . . . . . . . . . . . . . . . . . . . . . . How to Upgrade on a Windows Platform . . . . . . . . Starting the Element Manager . . . . . . . . . . . . . . . . . Initializing the Element Manager. . . . . . . . . . . . . . . . Defining NEs to Manage . . . . . . . . . . . . . . . . . . . How to Add a Single IP Connection . . . . . . . . . How to Discover all NEs in an IP Address Range
User Manual
. . . . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
31 32 33 33 34 35 37 37 39 43
3
How to Export and Import the Managed Elements List How to Modify IP Connections . . . . . . . . . . . . . . . . . How to Delete IP Connections . . . . . . . . . . . . . . . . . Accessing Trap Recipients . . . . . . . . . . . . . . . . . . . . . . The Add Trap Recipient Window . . . . . . . . . . . . . . . The Modify Trap Recipient Window. . . . . . . . . . . . . . The Delete Trap Recipient Window. . . . . . . . . . . . . . Working with Element Manager User Accounts. . . . . . . . How to Add a User Name . . . . . . . . . . . . . . . . . . . . How to Delete a User Name . . . . . . . . . . . . . . . . . . How to Change Other Users’ Passwords . . . . . . . . . . How to Change Your Password . . . . . . . . . . . . . . . .
Configuring Parameters . . . . . . . . . . . . . . . How to Configure Parameters . . . . . . . . How to Configure System Parameters. . . How to Configure NE Mode . . . . . . . . . . Configuring DCN Features . . . . . . . . . . . . . How to Configure a LAN IP Address . . . . How to Configure the System IP Address
Related Documents Overview This section gives an overview of the complete suite of documents that is provided for the FSP 3000R7 system, and when to read each document. Refer to these documents when planning, installing, provisioning, operating, or troubleshooting FSP3000R7 network elements, and when using the built-in management tools.
Planning •
Product Description This document provides a basic product overview.
•
Detailed System Description This document is a look-up resource. It describes the solutions and principles behind major features such as transport protocols, protection, optical amplification, reconfigurable OADMs, DCN, Control Plane, and management related features.
•
Module and System Specification This document contains the technical specifications for the FSP 3000R7.
Deployment Rules This document contains the rules for deploying FSP 3000R7 optical amplifiers in an optical network.
Installing •
Critical Warnings This document lists the most important safety requirements as well as input power restrictions for channel modules and pluggable transceivers. Read this document before installing, provisioning, configuring or operating the FSP 3000R7.
•
Safety Guide This document describes important safety precautions that are to be read and observed before attempting to install, provision, configure or operate the FSP 3000R7. Therefore, read this document first.
•
Shipment Contents This document is used to check and verify the contents of each shipping box against the original purchase order.
•
Installation and Commissioning Manual This document describes how to install an FSP 3000R7 node. It covers everything from unpacking the shipment, rack-mounting the equipment, connecting optical fibers, and includes basic commissioning. This is a procedure-oriented document.
User Manual
17
•
Hardware Description This document describes physical details about each module such as front plate pictures and markings, signal path description with block diagram, allowed placement and labeling of the modules. For details related to the supported configurations of each module, parameter values, and other management related data, refer to the Management Data Guide.
•
OTDR Installation, Provisioning and Operations Manual This document covers installation, provisioning, operations, troubleshooting, and maintenance of the OTDR unit.
Provisioning and Operating •
Provisioning and Operations Manual This document covers provisioning, configuring, operating, and monitoring of the FSP 3000R7 system. This is a procedure-oriented document. Read this document in conjunction with the Management Data Guide in order to look-up configuration and management related details while following the procedures in the User Guide. For more detailed guidance about the mechanics of using a management tool to perform individual tasks, see the Element Manager User Manual or the Craft/Web Console User Manual. Management Data Guide This document contains all provisionable, configurable, and read-only parameters for each module, as well as performance counters and alarms. This is a useful look-up reference both when planning and engineering a network and while following the procedures in the User Guide.
•
OTDR Installation, Provisioning and Operations Manual This document covers installation, provisioning, operations, troubleshooting, and maintenance of the OTDR unit.
Working with Management Tools •
Craft/Web Console User Manual This document is useful if you need more guidance in using the Craft or Web Console than the User Guide offers. Notice however that it is the User Guide that guides you to operate the FSP 3000R7. The Craft/Web Console User Manual helps you with the mechanics of using the tool to perform individual tasks on the FSP 3000R7. This is a procedural document.
•
TL-1 User Manual This document describes the TL-1 commands available to provision, configure, operate and monitor the FSP 3000R7.
Troubleshooting •
Troubleshooting Guide This document describes how to troubleshoot the FSP 3000R7 hardware and software.
Preface The Preface gives general information for the effective use of the FSP 3000R7 Element Manager (Element Manager) User Manual. This publication is provided "as is" without express or implied warranty for accuracy and completeness.
Purpose and Scope The purpose of this user documentation is to describe how to install and use the FSP 3000R7 Element Manager. For instructions on provisioning, configuring, operating and monitoring FSP 3000R7 Network Elements, see the FSP 3000R7 Provisioning and Operations Manual. The FSP 3000R7 Element Manager User Manual is a detailed guide to using the FSP 3000R7 Element Manager to complete the tasks described in the FSP 3000R7 Provisioning and Operations Manual. From this point and on, the FSP 3000R7 Element Manager will be referred to as the Element Manager.
Audience This user documentation is written for personnel that, configure, operate, or troubleshoot FSP 3000R7 Network Elements using the Element Manager. It assumes that the personnel have a basic knowledge of the FSP 3000R7 product, and how it works.
Document Revision History For an overview of the content of any one product release, please refer to the Release Notes provided with your system. Product Release
Document Number
Document Version
Issue Date
8.3 9.1
80000003745 80000007377
Issue B Issue B
Mar 2009 Aug 2009
User Manual
Details of Issue Small adjustments. Updated description for Ethernet L2 facility creations and scheduled database backup.
21
Organization
Document Number
Document Version
Issue Date
9.2 9.3
80000008785 80000010471
Issue A Issue C
Nov 2009 Jul 2010
9.4 10.1 10.2 10.2
80000012372 80000011744 80000013989 80000013989
Issue A Issue A Issue A Issue B
Jun 2010 Sep 2010 Oct 2010 Dec 2010
10.2
80000013989
Issue C
Mar 2011
10.3 10.3
80000014705 80000014705
Issue A Issue B
June 2011 Aug 2011
Details of Issue Updated to cover new features in release. Updated with information about application file location. Updated to cover new features in release. Updated to cover new features in release. Updated to cover new features in release. Enhancements to descriptions of user name/password case-insensitivity for remote servers, use of IP header, and the administrative state. Updated to cover new features span equalization, Ethernet linear protection, and Ethernet OAM/CFM. Updated to cover new features in release. Enhancement to descriptions of viewing Ethernet OAM entities, OSPF configuration, and EM user account password rules.
Organization This user documentation is organized in three main parts.
Part One This part describes how the Element Manager works, and how to use the tools that it provides. This part consists of these sections: Chapter 1: Getting Started This section describes how to get started using the Element Manager. This includes installing the Element Manager and initializing it for management of the relevant Network Elements. Chapter 2: Basics of the Element Manager This section gives an introduction to the Element Manager, by providing a general description of it, the main features it offers, its architecture and how it operates.
Part Two This part describes how to use the Element Manager to carry out commands that are necessary when following the FSP 3000R7 ’s procedures for commissioning, configuring and monitoring FSP 3000R7 Network Elements. This part consists of these sections: Chapter 3: Provisioning NEs
This section gives an introduction to provisioning of the FSP 3000R7. It contains instructions for provisioning shelves, modules, pluggable transceivers, channels and virtual channels to the internal database, by using the Element Manager. Chapter 4: Configuring NEs This section contains instructions on how to view the parameters that have been configured for the equipment and facilities in an NE, and the instructions on how to configure editable parameters for the NE. Chapter 5: Monitoring NEs This section describes how to monitor the equipment state, current conditions (for example, faults), events, performance and physical layer measurements. Chapter 6: Maintaining NEs This section contains instructions on how to maintain software on Network Elements as well as how to back-up and restore the Network Element configurations in the internal database.
This part is the Appendix where you will find additional useful information about communication ports and different states for the network element. This part consists of the following sections: Chapter A: Communication Port Overview This section gives an overview over ports used for communication between the Element Manager and Network Elements. Chapter B: Description of States This section gives the description of all states the network elements can have. Chapter C: RADIUS Authentication Setup This section describes how to setup the Element Manager to use RADIUS authentication. Chapter D: Configuring a RADIUS Server This section describes how to configure a RADIUS server, for the free RADIUS server application FreeRADIUS.
Additional Supporting Documents Management Data Guide
User Manual
23
Document Conventions
All entities are characterized by a number of parameters, or attributes. The Management Data Guide lists all attributes that may be displayed on the Config, Info and Fault pages in the management tools Craft Console, Web Console and EM. Thus, the procedures in the Element Manager User Manual do not always explain the attributes you can select for the fields, instead you are referred to the Management Data Guide. The parameters in the Management Data Guide are organized per module type. For equipment and facilities there are tables containing parameters, faults and performance information. This document is available as a PDF, accessible via the Element Manager help menu, or on the World Wide Web via your partner login at: http://www.advaoptical.com/
Document Conventions This section lists the common typographical and symbol use for FSP 3000R7 documents.
The documentation follows these typographic conventions: Convention
Description
boldface font
Indicates keywords and emphasized words when appearing in main text areas. All warnings are in boldface font. Indicates a reference to a chapter, section, figure, table or related documentation when appearing in main text areas. Refers to the keys on your keyboard, e.g. ENTER marked Courier font is used to identify words that can be read from or typed into the command line interface. Elements in square brackets are optional. Alternative elements are separated by a vertical bar. The symbol ^ represents the key labeled Control for example, the key combination ^D means that you have to hold down the Control key while you press the D key.
References are enclosed in angle brackets, for example: The escape key, marked Esc The Enter key, marked This reference, including the angle brackets, is replaced by the appropriate user name. Nonprinting characters, such as passwords. Double inverted commas are used to enclose quoted text. Used in bulleted list of items where the sequence of items is not relevant. These numbering styles are used in lists of items where the sequence of items is relevant, e.g. the steps listed in a procedure Are used to point to table footnotes. The markers in the text are arranged as continuous superscript numbers. Footnote text (in smaller typeface) is placed at the bottom of a table and starts with a superscript number. Refers you to additional information.
Safety Symbol and Message Conventions The safety alert symbols with the appropriate signal words and the note signs below are used throughout this documentation to identify warnings, cautions and notes.
WARNING
This symbol accompanies any instruction that draws attention to the risks caused by electricity. These risks could result in death or serious injury if the instruction is ignored or not followed correctly.
This symbol accompanies any instruction that draws attention to a potentially hazardous situation/condition. This situation/condition, may result in minor or moderate injury, if the instruction is ignored or CAUTION not followed correctly.
This symbol accompanies any instruction that draws attention to the possibility of equipment damage due to electrostatic discharge (ESD). Damage can occur, if the ESD-prevention instructions are ignored or not followed correctly.
NOTICE
This symbol accompanies any instruction that draws attention to the risk of equipment damage, malfunction, process interruption or negative impacts on surroundings. These events can occur, if the instruction is ignored or not followed correctly.
A symbol that draws attention to the necessity and importance of carefully reading all instructions before any installation or operation takes place. Failure to do so may result in personal injury or damage to equipment. This symbol accompanies any instruction that draws attention to the proper disposal of waste electrical or electronic equipment and its components. Disregard of the instruction can threaten the environment.
PS
This symbol accompanies any statement supplemental information or helpful recommendation that should be observed.
This symbol accompanies any instruction that draws attention to the risk of possible laser radiation. This risk may result in serious eye injury, if the instruction is ignored or not followed correctly.
Obtaining Documentation World Wide Web You can access the most current ADVA Optical Networking documentation on the World Wide Web via the Customer Portal at: http://www.advaoptical.com/
Ordering Documentation ADVA Optical Networking customers can order the Element Manager documentation set and additional literature through a local ADVA Optical Networking sales representative. For more current product release information, please refer to ADVA Optical Networking’s home page, or contact ADVA Optical Networking’s Technical Services. See Obtaining Technical Assistance and Contact ADVA Optical Networking for contact details.
We want our Element Manager documentation to be as helpful as possible. Feedback regarding the guide is therefore always welcome. You can e-mail your comments/suggestions to: [email protected] To submit your comments/suggestions by mail, use the following address: ADVA AG Optical Networking Technical Documentation Märzenquelle 1-3 98617 Meiningen-Dreissigacker Germany We appreciate and value your comments/suggestions to improve the quality of the guide.
Obtaining Technical Assistance Product Maintenance Agreements and other customer assistance agreements are available for ADVA Optical Networking products through your ADVA Optical Networking distribution channel. Our service options include:
User Manual
•
24 x 7 telephone support
•
Web-based support tools
•
On-site support
•
Technical training, both on-site and at ADVA facilities in Germany and the USA
•
Expedited repair service
27
Obtaining Technical Assistance
•
Extended hardware warranty service
Customer Portal The ADVA Optical Networking Customer Portal provides a suite of interactive, networking services that provide immediate access to company information and resources at any time, from anywhere in the world. This highly integrated internet application is a powerful, easy-to-use tool for doing business with ADVA Optical Networking. The broad range of features and services provided by the portal help customers and partners to streamline business processes and improve productivity. Through the customer login, you will find information tailored especially for you, including networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order ADVA Optical Networking training materials. Access the Customer Portal via the ADVA Optical Networking home page at: http://www.advaoptical.com E-mail questions regarding the Customer Login to: [email protected]
Technical services are available to warranty or maintenance contract customers who need technical assistance with a product from ADVA Optical Networking that is under warranty or covered by a maintenance contract. To access ADVA Optical Networking Technical Services, including all contact information, go to the ADVA Optical Networking home page at: http://www.advaoptical.com and select the “Support” button. To contact ADVA Optical Networking by E-mail, use one of the following addresses: Europe, Middle East, Africa: [email protected] North America: [email protected] Asia: [email protected]
Chapter 1 Getting Started This section describes how to get started using the Element Manager. This includes installing the Element Manager and initializing it for management of the relevant Network Elements
The Element Manager can be started as a standalone application or as an integrated application. In integrated mode the Element Manager manages only one NE and is launched by the FSP Network Manager (FSP NM) or some other Network Management System. In standalone mode the Element Manager can manage multiple NEs. This section describes how to get started using Element Manager in standalone mode. The following topics are provided: Installing the Element Manager, which describes how to install the Element Manager on the management computer. Starting the Element Manager, which describes how to start the Element Manager. Initializing the Element Manager, which describes how to initialize the Element Manager so you are ready to manage Network Elements.
Installing the Element Manager This section describes how to install the Element Manager on your management computer. You can install the Element Manager under the following operating systems: •
MS Windows XP / MS Windows 7
•
Solaris 10
For both operating systems the system requirement are: •
User Manual
Screen resolution minimum: 800 * 600
31
Installing the Element Manager
•
Free HD capacity: 500 MB
•
2 GHz Pentium Processor
•
1 GB RAM
The following supporting topics are provided: “How to Install on a Windows Platform” on p. 32 “How to Install on a Solaris Platform” on p. 33 “How to Uninstall” on p. 33 “How to Upgrade on a Windows Platform” on p. 34
How to Install on a Windows Platform This instruction describes how to install the Element Manager on a Windows platform for the first time. A description of this can also be found in the release notes for the Element Manager.
The Element Manager stores application data as files on the file system. Up to version 9.3.2 the files were stored in the installation directory. From version 9.3.3 and onwards the files are stored in an application data area, in the %ALLUSERSPROFILE%\FSP 3000R7 Element Manager folder. The ALLUSERSPROFILE environment variable is: •
C:\Documents and Settings\All Users on Windows XP
•
C:\ProgramData on Windows 7
Requirements •
Ensure that you have administrator/power user rights for the computer you want to install Element Manager on.
•
No previous version of the Element Manager should be installed on the computer.
Procedure Step 1 Step 2
Ensure that the computer fulfils the system requirements. Start the installation program FSP_3000R7_Element_Manager_v10_3_x_for_Windows.exe
In response an installation wizard will open. Step 3
Follow the instructions from the installation wizard until it is completed.
Step 4
Start the Element Manager, as described in “Starting the Element Manager” on p. 35. In response, the License window will display.
If you wish to install an upgrade, read “How to Upgrade on a Windows Platform” on p. 34 instead.
Chapter 1 Getting Started
Step 5
Enter the license name and license key into the License window and select OK. You shall have received the license information together with the executable file and release notes.
Step 6
Ensure that the user(s) of the installed Element Manager have write permission to the application data folder %ALLUSERSPROFILE%\FSP 3000R7 Element Manager.
End of Procedure
How to Install on a Solaris Platform This instruction describes how to install the Element Manager on a Solaris platform. A description of this can also be found in the release notes for the Element Manager.
Ensure that you have administrator/power user rights for the computer you want to install Element Manager on.
Step 2
Ensure that the computer fulfils the system requirements.
Step 3
Uninstall any previous version of the FSP 3000R7 Element Manager
Step 4
Copy the installation tar file to a directory on your local hard drive.
Step 5
Become root, using the command su-
Step 6
Untar the archive, using the command tar xf
Step 7
Start the installation script, using the command ./install In response instructions will be displayed on the screen.
Step 8
Follow all the installation instructions displayed on the screen.
Step 9
Start the Element Manager in the background, as described in “Starting the Element Manager” on p. 35.
Step 10
Enter a valid license key. You shall have received the license information together with the executable file and release notes.
End of Procedure
How to Uninstall This section gives necessary information to uninstall the Element Manager on either system platform. •
User Manual
In order to uninstall Element Manager on a Windows platform, use Add/Remove Programs in the Control Panel.
33
Installing the Element Manager
•
In order to uninstall Element Manager on a Solaris platform, remove the installation directory with the rm -r command.
How to Upgrade on a Windows Platform This instruction describes how to upgrade an Element Manager installation on a Windows platform.
Procedure Step 1
If you are upgrading from an Element Manager version prior to R9.3.3 to R9.3.3 or higher, back up the files containing the user accounts and license. Do as follows: a) Use Windows Explorer or similar to navigate to sub-folder dat in the Element Manager installation folder. This is typically C:\Program Files\ADVA Optical Networking\FSP 3000R7 Element Manager.
Step 2
Un-install your current Element Manager version as described in “How to Uninstall” on p. 33.
Step 3
Install the new Element Manager version as described in “How to Install on a Windows Platform” on p. 32.
Step 4
Edit any existing personal shortcuts to the previously installed Element Manager version so they point to the newly installed Element Manager version. During the un-installation and installation in the previous steps any existing personal shortcuts were handled as follows: • •
The un-installation process did not remove them. The installation process did not update them.
If you do not edit such personal shortcuts, they may still work, but the Element Manager will be started with parameters from the previous installation. This means that the Element Manager may be started with wrong memory settings. Step 5
If you are upgrading from an Element Manager version prior to R9.3.3 to R9.3.3 or higher, copy the backed up files users.xml and em.lic to the %ALLUSERSPROFILE%\FSP 3000R7 Element Manager \dat folder. Say Yes to overwrite the existing files.
After authentication has completed successfully, the Element Manager opens, displaying information about the Element Manager version, the user that is logged in, the user’s privilege level and the authentication type that was used.
End of Procedure
36
User Manual
Chapter 1 Getting Started
Initializing the Element Manager This procedure describes what you must do in order to be ready to manage Network Elements with the Element Manager.
Define which NEs you shall manage. How to do this is described in “How to Add a Single IP Connection” on p. 39.
Step 2
Ensure that the NEs are set up to communicate with Element Manager. How to do this is described in “Accessing Trap Recipients” on p. 53.
Step 3
Change the default user account and password. How to do this is described in “How to Change Your Password” on p. 59.
Step 4
Define the users of the Element Manager. How to do this is described in “How to Add a User Name” on p. 57.
Step 5
Back-up the Element Manager user files users.xml, nodes.xml, and em.lic to a safe location. These are the files containing your Element Manager user accounts, your managed nodes and your Element Manager license. They will allow you to easily re-install the Element Manager in case of a computer crash. The files are typically located in one of these two locations: • •
Element Manager versions prior to R9.3.3: C:\Program Files\ADVA Optical Networking\FSP 3000R7 Element Manager Element Manager versions R9.3.3 or higher %ALLUSERSPROFILE%\FSP 3000R7 Element Manager \dat
End of Procedure The following supporting topics are provided: Defining NEs to Manage Accessing Trap Recipients Working with Element Manager User Accounts
Defining NEs to Manage This section describes how to define which NEs the Element Manager shall manage. It also describes how to enter parameters for the connection to these NEs, how to modify these parameters and how to delete a connection to an NE. You may add a number of NEs to the list of managed elements without activating them for management. Only the NEs that you activate are selectable for
“How to Export and Import the Managed Elements List” on p. 46 “How to Modify IP Connections” on p. 51 “How to Delete IP Connections” on p. 52
38
User Manual
Chapter 1 Getting Started
How to Add a Single IP Connection This instruction describes how to add a single Network Element to the Element Manager’s list of managed elements. It is also possible to add new IP connections by selecting the Add button in the Managed Elements window. To open the Managed Elements window, see “How to Modify IP Connections” on p. 51.
In response, the Add Managed Element window appears.
User Manual
39
Initializing the Element Manager
Step 2
Enter the relevant SNMP parameters for the new managed Network Element in the SNMP Parameters section. Do as follows: a) Enter the system IP address of the NE you want to connect to in the IP Address field. The system IP address is the loop-back IP address for the NE, and is used as the SNMP trap sender address, the OSPF router ID, and for ring group switching. Ensure that the IP address you enter is not a broadcast or subnet address. b) Enter the UDP port number that the NE Software (SNMP agent) occupies for communicating with the Element Manager, in the Port field. This is by default 161.
d) Enter the maximum number of times the Element Manager shall retry sending a message, in the Retry field. If no response is recevied after this number of retries, the network element concludes that the NE is not responding. Normally the default value for this item is adequate. However, in heavily loaded networks, the number of retries should be increased to ensure that contact with the NE is not lost. If you do increase the number of retries, you should also increase the polling interval value to reduce the total load on the network. e) Use the Polling Status drop-down list to specify whether Element Manager shall poll the NE or not. The Element Manager polling mechanism only checks whether the SNMP Agent responds to “Get” requests. f)
Step 3
40
Enter the number of seconds there shall be between subsequent polling requests, in the Polling Interval field. Normally the default value for this item is adequate. However, in heavily loaded networks, the polling interval value should be increased to reduce the total load on the network. This value must be larger than the timeout value.
Use the radio buttons in the SNMP Access section to specify how the Element Manager shall access the NE’s SNMP agent. • If you select SNMPv1, Element Manager will use SNMPv1 settings when accessing the NE. Go to Step 4 and configure these settings. • If you select SNMPv3, Element Manager will use SNMPv3 settings when accessing the NE. Go to Step 7 and configure these settings.
c) Enter the number of seconds the Element Manager shall wait for a response after sending a message to the NE, in the Timeout field. If no response is received after this number of seconds, the Element Manager sends the message again. This value must be less than the polling interval value.
Chapter 1 Getting Started
Step 4
If you previously specified use of SNMPv1: The SNMPv1 Access section will appear in the Add Managed Element window.
Step 5
Enter the relevant SNMP parameters for the new managed Network Element in the SNMPv1 Access section. Do as follows:
a) Enter the community string the Element Manager shall use when sending SNMP Get requests to the NE, in the Read Community field. b) Enter the community string the Element Manager shall use when sending SNMP Set requests to the NE, in the Write Community field.
User Manual
Step 6
Continue from Step 9.
Step 7
If you previously specified use of SNMPv3: The SNMPv3 Access section will appear in the Add Managed Element window.
41
Initializing the Element Manager
Step 8
Enter the relevant SNMP parameters for the new managed Network Element in the SNMPv3 Access section. Do as follows: a) Enter the user name the Element Manager shall use when sending SNMP Get and Set requests to the NE, in the User field. b) Select the security level, using the Security Level drop-down list. The following options are available: • No Auth No Priv, this means that authentication and encryption will not be performed. • Auth No Priv, this means that authentication will be performed, but no encryption. • Auth Priv, this means that authentication and encryption will be performed. c) If you selected Auth No Priv or Auth Priv, previously: The authentication type that will be used is MD5. Enter the authentication password in the Authentication Password field.
Step 9
Select OK to finish adding NEs or Cancel to abort.
Step 10
If you want to activate the new NE for management now: Do as follows: a) Select the NE from the list of NEs in the Managed Elements window. b) Select the Activate button. In response the NE’s activated state will be indicated by in the Managed Elements window and the NE will appear in the Managed Elements pane.
d) If you selected Auth Priv previously: The privacy type that will be used is AES 128. Enter the privacy password in the Privacy Password field.
Chapter 1 Getting Started
How to Discover all NEs in an IP Address Range This instruction describes how to discover all NEs in a specific IP address range and add selected NEs to the Element Manager’s list of managed elements. Only NEs running SNMPv1 are discovered, and only NEs communicating over SNMPv1 can be added this way. To add NEs running SNMPv3, see “How to Add a Single IP Connection” on p. 39.
The left pane lists any existing IP connections. The right pane displays SNMP settings and polling details (on separate tabs) for the selected NE IP address. Each IP connection is configured individually.
User Manual
43
Initializing the Element Manager
Step 2
Select the
button, and the menu option Discovery.
Step 3
In the Discovery Configuration section, specify the address range by entering information in the Start Address and End Address fields. The maximum range is 255 addresses.
Step 4
In the SNMP Configuration section, specify the parameters that Element Manager shall use when contacting the IP addresses specified above. Do as follows: a) Enter the NE port that Element Manager shall use when contacting potential NEs, in the Port field. b) The discovery process will only be able to contact NEs that actually use this port.Enter the number of seconds the Element Manager shall wait for a response after sending a message to the potential NE IP addresses, in the Timeout field. If no response is received, the Element Manager sends the message again. The maximum value accepted is 60 seconds. This parameter directly influences how long time the discovery process will take. c) Enter the maximum number of times the Element Manager shall retry sending a message to the potential NE IP addresses, in the Retries field. The maximum number of retries is 3. This parameter directly influences how long time the discovery process will take. d) Enter the community string the Element Manager shall use when sending SNMP Get requests to the potential NE IP addresses, in the Read Community field. The discovery process will only be able to contact NEs that also use this community string.
Start the discovery process, by selecting the Start button. In response, the Element Manager will search the specified address range for NEs. Progress is indicated by a percentage below the table. As soon as a NE is discovered, its IP address, name and description are displayed in the table in the lower part of the Discovery window. If you wish to terminate the discovery before it is finished, close the Dis-
From the table of discovered NEs, select the NE that you wish to monitor and configure via the Element Manager. It is possible to select several NEs by or clicking. You can perform this step before the discovery process is entirely completed.
Step 7
Select the Add Selected button.
Specify the SNMP parameters to use for the selected IP addresses. Each of these parameters are described in “How to Add a Single IP Connection” on p. 39. The Port and Read Community parameters have already been found to work during the discovery process. If you change these, Element Manager will not be able to contact the NE(s). Step 8 Step 9
Select OK to apply the settings or Cancel to abort addition of the selected IP addresses. The added IP addresses are now displayed in the table of the Managed Elements window.
End of Procedure
User Manual
45
Initializing the Element Manager
How to Export and Import the Managed Elements List This section describes how to export and import the list of managed elements. This allows one user to share his/her list of managed NEs with one or more other users. The following instructions are provided Exporting the list Importing the list
The left pane lists all existing IP connections. The right pane displays SNMP settings and polling details for each selected NE IP address. Each IP connection is configured individually. Step 2
Specify whether NEs supporting SNMPv1, SNMPv3 or both SNMPv1 and SNMPv3 shall be displayed in the left pane. Use the corresponding radio buttons above the left pane.
Step 3
Select an IP connection in the left pane. In response the SNMP settings and polling details for this NE are displayed in the right pane.
User Manual
51
Initializing the Element Manager
Step 4
Select Modify. In response, the Modify Settings window appears.
Step 5
Modify each field as necessary. The fields are described in “How to Add a Single IP Connection” on p. 39.
Step 6
Select OK to complete the modifications.
Step 7
Select Close to finish your work with IP connections.
How to Delete IP Connections This instruction describes how to stop managing a NE.
Procedure Step 1
Select the NE that you wish to delete the connection to.
Step 2
Select File -> Delete from the Main Menu
Step 3
Select OK to complete or Cancel to abort deletion.
End of Procedure
52
User Manual
Chapter 1 Getting Started
Accessing Trap Recipients This instruction describes how to enter the management computer, or another computer, into an NE’s trap recipients table. The NE will send traps to the IP addresses registered in the trap recipients table. However, the Element Manager discards received traps that do not have a sender identity that it can find in its Managed Elements table. The NE uses its system IP address as sender identification, so if an NE is not added to the Managed Elements table with its system IP address, then traps from that NE will not be registered by the Element Manager. The Element Manager polls the NE regularly and reads traps from it, so the Element Manager will be kept up to date, even if it does not receive the traps when they are sent. However, the poll interval could be long, for example in order to reduce network traffic. FSP 3000R7 allows a maximum of ten IP addresses to be entered into an NE trap recipients table. The following supporting topics are provided: “The Add Trap Recipient Window” on p. 55 “The Modify Trap Recipient Window” on p. 56
Select an NE and then select Configuration -> Trap Recipients from the Main Menu. Alternatively click the
button.
The title bar of the dialog window shows the name of the NE. The dialog window contains a table with three columns: Column Name
Description
Address
Displays the IP addresses of the computers that are already in the NE’s trap recipients table. Displays the UDP port number that the NE sends traps through. By default this is UDP port 162. This column has a different name depending on which SNMP version you have selected. For SNMPv1 this is called Community and displays the community string in the SNMP traps to this trap destination. For SNMPv3 this column is called User Name.
Port Community / User Name
Step 2
Activate use of either SNMP version 1 or version 3 traps, by selecting the SNMPv1 or SNMPv3 radio buttons.
Step 3
Enter the management computer running the Element Manager by selecting the Add button. See “The Add Trap Recipient Window” on p. 55.
Step 4
Enter any relevant IP address by using the command buttons Add, Modify and Delete as appropriate and as described in “The Modify Trap Recipient Window” on p. 56 and “The Delete Trap Recipient Window” on p. 56.
Select Refresh to update the information in the trap recipients table or select Close to finish working with the trap recipients table.
End of Procedure
The Add Trap Recipient Window This instruction describes how to enter information when adding an IP address to a NE’s trap recipients table. This instruction assumes that you have already opened the Trap Recipients window.
In the Address field, enter the IP address of the computer you wish to add to the trap recipient table.
Step 3
Suggested value for Port is displayed, modify this as needed.
Step 4
In the Version drop-down list, select SNMPv1 or SNMPv3. You should only choose SNMPv3 if SNMPv3 is used for the NE.
Step 5
The last field depends on which SNMP version you have selected. • For SNMPv1, set a value for Community. The community you enter here, has to be identical to the community that is used for the NE. • For SNMPv3, set a value for User Name. The user name you enter here, has to be identical to the user name that is used for the NE.
Step 6
Select OK to apply or Cancel to abort.
End of Procedure
User Manual
55
Initializing the Element Manager
The Modify Trap Recipient Window This instruction describes how to modify a NE’s trap table entry. This instruction assumes that you have already opened the Trap Recipients window.
Procedure Step 1
Select an entry in the trap recipients table.
Step 2
Select Modify.
You may now modify the community string settings. Select OK to apply or Cancel to abort.
End of Procedure
The Delete Trap Recipient Window This instruction describes how to delete an entry in an NE’s trap table. This instruction assumes that you have already opened the Trap Recipients window.
Procedure Step 1
Select the relevant IP address in the trap recipients table (you may delete any IP address).
Working with Element Manager User Accounts Here you will find information about administering User Accounts in the FSP 3000R7 Element Manager, with the following topics: “How to Change Your Password” on p. 59 “How to Change Other Users’ Passwords” on p. 59 “How to Add a User Name” on p. 57 “How to Delete a User Name” on p. 58
How to Add a User Name A user with Administrator level user may add or delete user names for the Element Manager.
Procedure Step 1
From the Main Menu select Security -> User Manager.
The Current user section displays information about the user who is currently logged in, and which authentication was used when logging in.
User Manual
57
Initializing the Element Manager
Select the Add button.
Field Name
Description
User Name
Enter the user’s identity in the Element Manager, the user name must have minimum 2 characters. Enter an initial password. This may be changed later by the actual user, upon his/her first logon. See “About Security” on p. 77 for information on requirements to the password. Retype the password to confirm spelling. Select the security level for the new user. This level can be Monitor, Operator or Administrator. By default Monitor is selected when you open this window. Upon initial logon to the Element Manager, Administrator is the security level for the first user.
Password
Retype Password Security Level
Step 3
Select OK to finish or Cancel to abort.
End of Procedure
How to Delete a User Name A user with Administrator level may delete user names for the Element Manager. This is sometimes necessary, e.g. when a user has forgotten his/her password. Any user who no longer is granted access to the Element Manager should also have his/her user name deleted.
Procedure Step 1
From the Main Menu select Security -> User Manager. In response, the User Manager window appears.
Step 2
Select the user name to delete.
Step 3
Select Delete. Select Yes in the Confirmation window.
How to Change Other Users’ Passwords It is not possible for a user with Administrator level to change passwords for other user names directly. Instead the administrator must delete the particular user name and add it again with a new password.
How to Change Your Password All users should periodically change his/her password to prevent unauthorized access to the Element Manager.
Procedure Step 1
Do one of the following: • From the Main Menu select Security -> Change Password, or • From the Main Menu select Security -> User Manager and then select Change Password.
Chapter 2 Basics of the Element Manager This section gives an introduction to the Element Manager, by providing a general description of it, the main features it offers, its architecture and how it operates. The following topics are provided:
Overview, which describes briefly how the Element Manager works, the features it offers and how it communicates with the NEs. About the Graphical User Interface, which describes the Element Manager’s graphical user interface (GUI) in detail. It describes each component of the GUI, which information it displays and how to customize the display. About Communicating with NEs, which describes how the Element Manager communicates with the NEs. Getting Help, which describes how you get help when working with the Element Manager. About Security, which describes the security features for the Element Manager.
Overview The Element Manager provides remote configuration and monitoring of one or more SNMP Network Elements (NEs). The operator may manage NEs in a simple and intuitive way using the Element Manager point-and-click graphical user interface. Graphical components representing NEs, ports, power and fan may be selected with the mouse. The appropriate management functions for a selected component are available in the Main Menu or the context sensitive popup menu. When alarms occur, the graphical view gives an overview over these by outlining the affected graphical component in color. This color reflects the most severe of all current alarms of any of the underlying components. The Element Manager can be used: •
User Manual
As a standalone application.
61
Overview
•
Integrated with the FSP Network Manager or other Network Management Systems (such as HP OpenView).
The Simple Network Management Protocol (SNMP) is used. SNMP defines how a network management system shall communicate with an NE. Figure 1:
Overview of SNMP Communication FSP Element Manager
UDP port Computer
Ethernet
NE 2
The Element Manager occupies a UDP (User Datagram Protocol) port for communication with NEs. All Element Manager views are updated immediately upon receiving SNMP traps (event information) from NEs.
Example of Element Manager Main Screen Information pane Parameter pane
Menu Bar
Status bar Entities pane
User Manual
Equipment pane
Response Log
63
About the Graphical User Interface
Each area is described in detail under the following topics: “The Menu Bar” on p. 64 “The Toolbar” on p. 65 “The Network Element Pane” on p. 66 “The Information Pane” on p. 67 “Response Log” on p. 74 “Status Bar” on p. 75
The Menu Bar The menu bar contains access to groups of related features via a submenu of executable commands. Each command is started on selection. A dimmed command indicates that the command does not apply to the present situation or that you need to make a selection or complete another action before choosing the command. In response to a command, a related window with necessary information and controls related to the command will appear. Context Sensitive Pop-up Menu
Context sensitive pop-up menus give quick access to frequently used commands. These menus pop up when you select an object and click the right mouse button. Which commands are available in the present situation depends on the object you have selected, e.g. a Network Element, shelf or a module. Select a command by left-clicking, just as you would do from the Main Menu. Unavailable commands are dimmed.
The Toolbar The Toolbar is a fixed area at the main window's top edge. It contains a set of tool buttons that give the operator quick access to commonly used commands. The Toolbar is displayed or removed by selecting View -> Toolbar from the Main Menu. By holding the mouse pointer over a button a ToolTip will appear with an description of the action the button represents. Figure 4:
Overview of Toolbar Icons
Displays the Equipment Window of the selected Network Element Displays the User Manager Change password for the present user Add or remove Managed Elements Updates stored management data of the selected NE Shows the inventory list for the whole NE Shows the list of current alarms of the selected NE or module Displays the Event Log
Displays the Cross Connections window Configure trap recipients Closes all open windows Displays the previous open window Displays the next open window Displays the About dialog
User Manual
65
About the Graphical User Interface
The Network Element Pane All NEs you have defined connections to are shown in this view, and are represented by symbols. Below each symbol one or more icons are displayed together with the NE name or IP address. Together these symbols and icons give information about the NE. This information in this view is continually updated. The following symbols and icons are used in Network Element View: Figure 5:
Overview of Network Element Pane Icons
This icon indicates that the NE operates normally. This icon indicates that the connected NE is unknown to the Element Manager. This may for example be the case if the agent software on the NE is not running. This icon indicates that the Element Manager does not get any response from the NE when it sends SNMP Get-Requests.
This icon indicates that no event messages are sent from the NE to the Element Manager. This occurs when the IP address of the computer running the Element Manager has not been entered in the NE trap table. To enter the NE trap table see “Accessing Trap Recipients” on p. 53. This icon indicates that lost traps are detected. The Element Manager has not been able to recover lost traps from the NE. This could be due to DCN problems or a heavily loaded NE. It is recommended to resynchronize the NE to make sure the management data is up to date. The icon is removed when the NE is resynchronized.
The NE name shown is the sysName (according to RFC 1213) of the NE. If the Element Manager cannot get the NE name information, it displays the IP address of the NE instead. To toggle between display of the NE name and the NE’s IP address, select View -> Name or View -> Address from the Main Menu. NEs in the Network Element View are selected by pointing and clicking. When an NE is selected, Element Manager indicates this by displaying an outline border on the NE symbol.
This icon is always present and the color indicates the highest severity of the present alarms on this NE. If no alarms are present, the icon is green. For information about the alarm color coding, see Table 10.
Chapter 2 Basics of the Element Manager
The Information Pane The Information pane consists of the Entities pane, the Parameter pane and the Equipment pane. To display information about an NE in the Information pane, double-click on the NE in Network Element View. Alternatively you select the NE in Network Element pane and then select View -> Equipment from the Main Menu. In response the Information pane will display all information about this NE on one page. You may display information for several NEs, each will have one dedicated page in the Information pane. Each page is selectable by a tab in the bottom of the Information pane. To close the Information pane for one NE, right-click on that NE’s tab in the Information pane and select Close. To close all presently open Information panes, right-click on any NE’s tab in the Information pane and select Close All.
Figure 6 shows the standard layout of the Information pane. This layout can be toggled in order to get a larger view of the Parameter pane, by sacrificing size of the Entities pane. Use the Toggle Layout field of the Entities pane to do this.
User Manual
67
About the Graphical User Interface
Example of the Information Pane, Alternative Layout
The Entities pane, the Parameter pane and the Equipment pane are each described under the following topics: “The Entity Pane” on p. 68 “The Equipment Pane” on p. 72 “The Parameter Pane” on p. 73
The Entity Pane The Entity pane consists of two tabs, the Tree tab and the Racks tab. Descriptions of these tabs and the information contained in them are described under the following topics: “The Tree View” on p. 69 “The Racks View” on p. 70 “AID Names” on p. 71 “Entity Position” on p. 72
The Tree View The Tree view of the Entities pane displays equipment and facilities in a hierarchical list. Figure shows an example of the Tree view. Figure 8:
Element Manager Entity Pane, Tree View click to toggle layout
click to collapse
indication of entity’s operational state or secondary state.
Use the list to select the entities that you wish to work with. In some cases, the configuration of a module may not allow provisioning of a pluggable transceiver for a port. If however a pluggable transceiver is physically in place, the Entities pane will display the equipped pluggable transceiver in this list. This does not indicate that it indeed can be provisioned. In front of each entity, a colored condition ball indicates the current condition with the highest severity that is present for that entity. The color code is described in “Monitoring Faults” on p. 369. Each entity is identified by its Access Identifier (AID) address and its type. Figure 9:
Entity Identification Examples
AID name
entity position
Entity type
alarm ball symbol for graphical identification of the entity.
The AID address consists of the entity’s AID name and the position of the entity in the system. AID names are described in Table 1 and entity positions in “Entity Position” on p. 72. The entity type can for example be NCU, OTU or LANIP. For an overview of AID names, see “AID Names” on p. 71, and for an overview of the positions entities can have see “Entity Position” on p. 72.
User Manual
69
About the Graphical User Interface
The Racks View The Racks view is a graphic representation of the shelves and racks of the Network Element. Element Manager Entity Pane, Rack View
The view shows the position of the shelves in the racks. You can select the shelves to see the related information in the Parameter and Equipment panes. When a shelf is selected, it is grey. The symbols indicate alarms for the entities. The color and letter inside the symbol indicate the severity of the alarm. The relationship between color, letter and severity is shown in Table 10 and also explained in “The Equipment Pane” on p. 72. The view only shows the shelves that are positioned in racks. The Unplaced shelfs drop down list contains shelves that are not yet positioned in the racks. You can position an unplaced shelf in the following way: 1
Select the shelf in the Unplaced shelfs drop down list.
2
Select the Config tab in the Parameter pane.
3
Select the Modify button.
4
Set the appropriate values in the Modify window that appears.
The Racks view shows the order of the shelves from the bottom and up and does not show any empty spaces between the shelves. The view is only used to navigate to the shelves and see their position relative to each other. If you want to change the position of the shelves in the racks, you must go to the Config tab in the Parameter pane and select the Modify button.
AID Names An overview of the main AID names that the system supports are listed in Table 1. This table also shows the dependencies between entities. A CH (channel) entity is dependent on a MOD (module) or PL (SFP Transceiver) entity. Thus, the MOD or PL entities support the CH entity. Table 1: Supporting Entity AID name
LINK CRS-DCN LAN SH IP TIFI TIFO CH SH VCH SDCC LDCC PDCC GCC0 GCC1 GCC2 FFP_CH FFP-OM STS1 VC4 VC3 CRS-DCN
Description Equipment. All shelves. Equipment. Fan control unit. Equipment. All modules. Equipment. Fan assembly. Equipment. SFP Transceiver (plug) Facility. Channel on the client or network port that carries the service(s). Facility. Optical multiplexed facility that carries the multiplexed signal. DCN Facility. Supervisory channel. For example of type E100Fx or LANIP. DCN facility. For example of type PPP IP, serial or USB interface. DCN Facility, DCN cross-connect between DCN facilities. DCN facility. Group of SC entities. For example of type LANIP. Facility. Internal communication between shelves. Facility. Broadcast IP Facility. External input. Facility. External output. Facility. Channel on the client or network port that carries the service(s). Facility. Internal communication between shelves. Facility. Virtual channel that models an intermediate mapping of facilities into a higher layer signal container DCN facility. SONET Section DCC. DCN facility. SONET Line DCC. DCN facility. SONET Path DCC. DCN facility. OTU GCC0. DCN facility. ODU GCC1. DCN facility. ODU GCC2. Facility. Protection group for channels. Facility. Protection group for optical multiplex signal. Facility sub-level. Higher layer signal container. Facility sub-level. Higher layer signal container. Facility sub-level. Higher layer signal container. DCN Facility, DCN cross-connect
71
About the Graphical User Interface
Entity Position The entity’s position in the Network Element is indicated by the shelf, slot, port and instance numbers. The syntax depends on the AID name. For MOD entities the syntax is - . For CH, SC, SDCC, LDCC, PDCC, GCC0, GCC1, GCC2 and EOC entities the syntax is - -. Ports can be N, NW and NE for network ports and C, C1.Cn for client side ports. NW indicates the West network port while NE indicates the east network port. For OM entities the syntax is - -. Ports can be: •
N, NW, NE, 1NW, 1NE, 2NW and 2NE for network ports.
•
C, C1..Cn for client side ports.
•
U, UW, UE for upgrade ports.
For SH entities the syntax is - -. Ports can be: •
U, D, and X for internal inter-shelf connections on the SCU card.
For VC4, VC3 AND STS1 entities the syntax is - -| - |.
For LAN entities the syntax is - -. Instance is always 1.
The Equipment Pane The Equipment pane is a graphical representation of the Network Element. Shelves, fans and modules are selectable, and the Parameter pane will display information for the selected entity here. Figure 11:
Equipment Pane
If there are any alarms/conditions present for any of the managed components, they are indicated by a symbol over the managed component. Clicking on the symbol leads to the Parameter pane displaying the State tab/list for that module. The color and a letter inside the symbol indicate the severity of the
For VCH entities the syntax is - - - . Instance can be 1..n, where there are n client ports to which they may be allocated.
Chapter 2 Basics of the Element Manager
alarm. The relationship between color, letter and severity is shown in Table 10. When several alarms/conditions are present: •
The number indicates how many alarms/conditions of the highest severity are present.
•
The color and letter of the most severe of these alarms/conditions are displayed.
•
When there are alarms/conditions present with different severities, this is indicated by the “+“ sign.
The Parameter Pane The Parameter pane is the main source of information in the Element Manager. Upon selection of an entity in the Entities pane, the relevant parameters and attributes describing this entity are displayed group-wise in the Entities pane. Figure 12 shows the Parameter pane with tab view active.
Figure 12: Example of Parameter pane, Tab view Tabs for selecting parameClick to toggle layout of ter group to display Parameter pane.
Click to modify editable parameters on the visible page.
The following parameter groups, are used: •
State
•
Fault
•
Config
•
Operation
•
Info
•
Monitoring
•
Inventory
However, the number of visible tabs varies according to the entity selected and whether or not equipment is installed. The parameter pane has two display options; a tab view and a list view. Each parameter group is then displayed either on a separate tab, or in a separate list.
User Manual
73
About the Graphical User Interface
You can toggle between these two options, by selecting the Toggle Layout text. The default Parameter pane view is the tab view. Figure 13:
Parameter Pane, List View Close Group
Click to display tab view
Open Group
This window presents information such as notifications related to user operations and occurring events on the connected NEs. The responses or results of user operations appear as log entries. These entries can either be error messages indicating that the operation failed, or positive acknowledgements of successful operations. The window is displayed or removed by selecting View -> Messages on the Main Menu. You can also remove the window by right-clicking the Response Log and selecting Hide. You clear the presently displayed messages by right-clicking in the Response Log and selecting Clear All. You can also clear all messages by selecting it in the Response Log, and then selecting View -> Clear Messages. To print, or save the response log, right-click in the Response Log and select Print or Save. The response log can be exported to both the XML and CSV format. Opening an exported response log file requires that the local regional settings for date and time on the computer you are using are the same as were used when the XML/CSV file was created. Otherwise the fault timestamps may be converted incorrectly. Date and time data is stored internally in the XML/CSV file in the following format: yyyy-mm-dd and hh:mm:ss:xxx, where xxx indicates three digits for milli-seconds. Figure 14:
Column Name
Description
Type Time
of log entry can be Information, Warning or Error. shows the date and time at which the entry was logged. indicates the location where the operation was performed or where the event took place. tells you what happened.
Status Bar The Status Bar is located at the bottom of the main window. It shows the most severe alarm registered in the FSP3000R7. Also, when you point to a command on a submenu, a short description of this command is displayed in the left end of the Status Bar. The same applies when pointing to a tool button. Upon start-up a certain amount of memory is allocated to the Element Manager. This amount is displayed in the right side of the Status bar along with the currently used amount of memory. When the memory consumption is too high, the Element Manager may freeze, or crash. Reducing the number of activated managed elements will help. The icons used on the Status Bar are: Figure 15:
Status Bar Icons
The color indicates the most severe present alarm present on the connected NEs using a standardized color scheme as described in Table 10. Indicates that UDP port 162, which the Element Manager listens to for SNMP traps, is occupied. This is also indicated in the Message Log.
Indicates the total memory allocated to Element Manager as well as how much memory is currently used. If more than 90% of the allocated memory is used, the bar will change color to red. No more managed elements can be activated in this situation. The command button for the Garbage collector.
In order to release memory, a Garbage Collector is provided. It runs automatically at regular intervals. You may also manually trigger the Garbage Collector, if relevant: •
Left-click the symbol on the Status Bar. The Status Bar is displayed or removed by selecting View -> Status Bar on the Main Menu.
When the Message Log shows “Error binding to Trap Port 162”, this is normally due to another Element Manager already running. Closing one instance of the Element Manager fixes the problem. See also Appendix A: Communication Ports. The following topics are provided: “Displaying Several NE Information Panes Simultaneously” on p. 75
Displaying Several NE Information Panes Simultaneously Sometimes it is advantageous to view equipment for two or more NEs at the same time. Element Manager allows you to “unplug” the Information panes from the Element Manager main window so that you can position them as you wish on your screen. Right-click on the NE tab in Information pane and select Unplug. When you are finished working with this Information pane, close it.
User Manual
75
About Communicating with NEs
About Communicating with NEs The Element Manager manages each NE via SNMP. This connection carries control, configuration and request messages from the management system to the NEs and alarms, event and response messages from the NEs back to the management system. Figure 16:
Connections between NEs and Element Manager FSP 3000 EM UDP port Computer
IP address
Ethernet
IP address
UDP port NE SW (SNMP Agent)
IP address
NE 2 UDP port NE SW (SNMP Agent)
Figure 16 illustrates necessary information for establishing IP connections between the Element Manager and NEs. To communicate with the NEs, you must enter their system IP addresses. When an IP connection to an NE is established, the Element Manager will automatically read management data from the NE and display an icon for it in the NE View. Likewise, the icon is removed when its corresponding IP connection is removed. The entered IP connections are stored in a file and this file is read at the next start-up of the Element Manager. Hence the IP addresses are available also after an upgrade of the Element Manager. NEs send information to the Element Manager in the form of SNMP traps, using their system IP address as the sender identity. In order for an Element Manager to continually receive SNMP traps from a NE, the NE must be entered into the Element Manager with its system IP address, and the IP address of the computer running the Element Manager must be entered in the NE’s trap recipients table. This table defines for the NE where to send traps to. If this IP address is not in the NE’s trap recipients table, the trap information displayed by the Element Manager reflects the state of the NE at connection time. In this case you can manually update this information. That may be satisfactory if you seldom connect to this NE. The other management functions available from Element Manager are not dependant on the trap recipients table entry and will hence function normally. The Element Manager checks its connections to NEs by polling. That is, the Element Manager periodically sends SNMP Get-requests to the NEs’ Software (SNMP agent). The connection is lost if the Ethernet cable between the Element Manager computer and the NE is removed, or if the NE Software does not respond. If the connection to an NE is lost, a red cross is displayed on top of the
associated icon in the NE View. The Element Manager will continue to poll the NE and will remove the red cross when the connection is re-established. Then the Element Manager re-synchronizes itself with the NE to update the management data stored in the NE.
Getting Help Open the Help window by selecting Help -> Help Topics from the Main Menu. The left pane in the Help window contains the table of contents in a tree-fashioned list. This list may be expanded and collapsed. Select a section from the list and the text will be displayed in the right pane. There are icons for setting up the page layout and for printing the displayed section. The page layout is valid for all sections.
In order to avoid unauthorized access to the NEs, you must log on to the Element Manager. Each Element Manager user has a unique name for identification and a password for authentication. Authentication will be done either against the local password file, or by centralized authentication using Remote Authentication Dial In User Service (RADIUS). If RADIUS authentication has been enabled for the Element Manager, this authentication method is tried first (first priority), the local password file is tried next. Each user is assigned to a specific security level, defining the user's rights. The following sections are provided: “Security Levels” on p. 77 “Local Authentication” on p. 78 “Centralized Authentication” on p. 78
Security Levels The following security levels are provided:
Administrator Users with this security level have access rights to the entire functionality of the Element Manager, including adding and deleting users from the Element Manager. Upon initial logon to the Element Manager this is the security level for the default user.
Operator Users with this security level have the same rights as the Administrator, with exception of the commands to add or delete a user.
User Manual
77
About Security
Monitor Users with this security level have the same rights as the Operator with exception of the commands to change settings on the NE.
Local Authentication Initially, one user account is defined on the Element Manager. This is the user name ADMIN with the password CHGME.1 and the security level Administrator. The Administrator user can manage user accounts from the User Manager window, see “Working with Element Manager User Accounts” on p. 57.
PS
For security reasons the default password should be changed after installation of the Element Manager.
Note
Password requirements: •
The password must have minimum 6 characters
•
The password is not case-sensitive.
The Element Manager supports the Remote Authentication Dial In User Service (RADIUS) protocol based on RFC2865 for centralized authentication. RADIUS allows authentication of users by communicating with a central server using the RADIUS protocol. The user profiles are maintained in a central database, and RADIUS automatically recognizes the properties that are assigned to each RADIUS user. Each user only needs one user name and one password for all network elements. This makes RADIUS authentication a flexible authentication method. In combination with RADIUS authentication, the Element Manager uses one or more SNMP access profiles when accessing the SNMP agents of the NEs that are managed by the Element Manager. Up to 3 RADIUS severs can be configured, and any RADIUS server application can be used. If RADIUS authentication has been enabled, the Element Manager will attempt to use the first listed RADIUS server for authentication. If this fails, it will attempt to use the second and then third RADIUS server, if any have been defined. It these too fail, the Element Manager will use the local password file. This sequence of priority is not user-configurable. In order to use RADIUS authentication and SNMP access profiles, the following requirements must be met:
78
•
at least one RADIUS server is configured to support the Element Manager
•
the RADIUS server is reachable for the Element Manager
•
RADIUS user accounts with belonging passwords have been defined on the RADIUS server
•
the Element Manager is enabled to use RADIUS authentication
The administrator of the NE management should ensure these requirements are met for all users, see Appendix C: RADIUS Authentication Setup for instructions.
Chapter 3 Provisioning NEs This section gives an introduction to provisioning of the FSP 3000R7. It contains instructions for provisioning shelves, modules, pluggable transceivers, channels and virtual channels to the internal database, by using the Element Manager.
This section should be read in conjunction with the FSP3000R7 Provisioning and Operations Manual, where the procedure for provisioning an FSP3000R7 Network Element is described. The following topics are provided: About Provisioning, which gives a basic understanding of the internal Network Element database and provisioning. Creating Equipment/Facilities Manually, which contains the instructions for manually creating entities and protection. How to Create Equipment/Facilities Automatically, which contains the instruction for enabling automatic provisioning for a Network Element. Managing Encryption Modules, which contains the instructions for provisioning encryption for the first time, and for adjusting and managing encryption. Creating Protection Groups, which contains the instructions for creating protection groups. Creating ADM and ROADM Cross Connections, which contains the instructions for creating Add-Drop cross connections. Creating Flow Points, Bridges, and Cross Connections, which contains the instructions for creating Ethernet L2 flow points and flow cross connections. Creating DCN Cross-Connections, which contains the instructions for creating DCN cross connections. How to Delete Equipment/Facilities Manually, which contains the instruction for manually deleting entities. Handling Network Element User Accounts, which contains the instructions for adding and deleting user accounts on the Network Element.
User Manual
81
About Provisioning
About Provisioning The basis for FSP3000R7 management, is the Network Element database. This database is a virtual representation of the actual equipment and the facilities that this equipment supports. Thus, this database reflects the actual equipment and facilities present in the NE, or the equipment and facilities that are planned for the NE. The generic term that is used for equipment and facilities is entity. The database recognizes each entity in an NE, by means of their Access Identifier (AID) address and their entity type. Table 2 shows a few examples of AID addresses. “The Equipment Pane” on p. 72 gives more details about AID addresses. Example of AID addresses
AID address syntax Module: MOD-- Plugs: PL--- Optical Channel: CH---
AID address example MOD-1-3 PL-1-3-NE CH-1-3-C1
Defining equipment and the facilities that they support, is called provisioning. You provision each entity by creating it in the internal database, specifying the relevant parameters for the entity in the process. You start by creating and configuring equipment: the shelf, the modules and any pluggable transceivers on the modules. Then you create ports and configure the channels on these ports. Thus the principle is to start at the bottom and then add entities that are supported by the existing entity. In the same manner, deletion must be done from the top. You must first delete a channel before you can delete the port of module that supports that channel. The parameters that are provisioned into the internal database are stored and can be used for future backup procedures. Any configuration after provisioning, operates on the internal database, which again transfers these settings to the actual equipment. Provisioning may be done manually or automatically. Regardless of provisioning method, the entity is set to a default administrative state when provisioning is finished. For manual provisioning the administrative state is Management. The exception is if the supporting entity has administrative state Disabled, then the provisioned entity is set to Disabled too. For automatic provisioning the administrative state is equal to that of the supporting entity. The exception is if the supporting entity is Maintenance, then the provisioned entity is set to Management. When automatic provisioning is used, the FSP3000R7 detects the equipment, and depending on the equipment, some of the entities. This equipment and these facilities are provisioned with default parameter values. The default administrative state is set equal to that of the supporting state. If required, the default administrative state can be overruled. Then the Automatic In Service administrative state is set, when the supporting entity state is In Service or Automatic In Service.
The document Management Data Guide lists all parameters that you my be required to enter during provisioning. This list gives the allowable range for parameter values, the default values and a brief description of each parameter. The FSP3000R7 Provisioning and Operations Manual describes the procedures for provisioning equipment and facilities (entities).
Creating Equipment/Facilities Manually This section contains the instruction for creating shelves, modules, pluggable transceivers and the necessary ports for the modules. Entities must be created from the bottom and up. That is, you must create the shelf before you can create a module that is in that shelf. Or, you must create a module before you can create the channel that the module shall carry. The Element Manager supports creation of entities via a wizard. During the creation, you will be required to specify a number of parameters. Which parameters you are requested to enter, depend on which entity type you are creating in the internal database.
The creation wizards can be started in several ways; using the Main Menu to open the Provisioning Manager window, or using context-sensitive menus by right-clicking an entity in the Entities pane hierarchical list. This section describes creation by using the Provisioning Manager window from the Main Menu. The Provisioning Manager window shows you which entities that the selected entity supports, and thus which entities that are available for creation at this point. This is useful for keeping the overview of what you are doing. The instructions in the following sub-sections all assume that you have opened the Provisioning Manager window. To open the Provisioning Manager window:
User Manual
83
Creating Equipment/Facilities Manually
Procedure Step 1
Select the relevant Network Element in the Managed Elements pane.
Step 2
From the Main Menu, select Configuration -> Provisioning ->. In response, the Provisioning Manager window appears.
This window can be used in parallel with the rest of the Element Manager. The following topics are provided: “How to Create a Shelf” on p. 85 “How to Create an OTDR Shelf” on p. 86 “How to Create a Module” on p. 87 “How to Clone a Module” on p. 88 “How to Create a Plug” on p. 92 “How to Create a Port” on p. 93 “How to Clone a Channel (Port)” on p. 96 “How to Change a Service (Channel)” on p. 99 “How to Create a Virtual Channel” on p. 100 “How to Create an Ethernet Port (ETH)” on p. 101 “How to Create a Virtual Ethernet Port (VETH)” on p. 107 “How to Create an SDH/SONET/OTN based ECC Channel” on p. 113 “How to Create an Ethernet based ECC Channel” on p. 115 “How to Create a PPP IP Interface” on p. 116 “How to Create a Supervisory Channel” on p. 119 “How to Create an Optical Line” on p. 120
How to Create a Shelf This section describes how to create a shelf in the internal database, using the Provisioning Manager window. After creation, the shelf is selectable from the SHELF- entity in the Entity pane.
Procedure Step 1
Select the NE that you wish to add a shelf to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection.
In response, the right side of the Provisioning Manager window displays the Create Shelf list. This is a list of AID addresses for the shelves that may be added. Step 2
Select the relevant shelf AID address from the list. In response the Create Shelf wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
Step 3
Enter the required parameters in the wizard pages as follows:
a) Use the drop-down lists and controls that the wizard provides, to select the relevant parameter values. See the supporting document Management Data Guide for descriptions of these parameters for this shelf type. b) Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters. Step 4
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete page appears, and the shelf is added to the Entities pane. By default, the NCU or SCU modules for the shelf are automatically created as well.
Step 5
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 6
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 7
User Manual
Close the Provisioning Manager window by selecting Close.
85
Creating Equipment/Facilities Manually
How to Create an OTDR Shelf This section describes how to create the OTDR shelf combination in the internal database, using the Provisioning Manager window. After creation, the shelf is selectable from the SHELF- entity in the Entity pane.
Requirements •
An NCU with two Ethernet ports must be provisioned in the NE.
•
The Ethernet port C2 (entity SC-1-A-C2) must be un-provisioned. This enables the OTDR provisioning process to provision the port according to its needs.
Procedure Step 1
Select the NE that you wish to add a shelf to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection.
Step 2
Select the item SHELF-OTDR from the list.
Step 3
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete page appears, and the shelf is added to the Entities pane.
Step 4
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 5
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 6
Close the Provisioning Manager window by selecting Close.
In response, the right side of the Provisioning Manager window displays the Create Shelf list. This is a list of AID addresses for the shelves that may be added.
Chapter 3 Provisioning NEs
How to Create a Module This section describes how to create a module in the internal database, using the Provisioning Manager window. After creation, the module is selectable from the MOD--- entity in the Entity pane.
Procedure Step 1
Select the shelf that you wish to add a module to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection. In response, the right side of the Provisioning Manager window displays the Create Module list. This is a list of AID addresses for the slots in the selected shelf that you may add modules to.
Step 2
Select the relevant slot AID address from the list. In response the Create Module wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
Step 3
In the Parameters Step 1 page, use the Equipment Type drop-down list to select the relevant module type.
The parameters you are required to enter in the next pages of the Create Module wizard, depend on your selection of the facility type. Step 4
Enter the required parameters in the wizard pages as follows: a) Use the drop-down lists and controls that the wizard provides, to select the relevant parameter values. See the document Management Data Guide for descriptions of these parameters for this module type. b) Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters.
Step 5
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete page appears.
Step 6
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 7
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
User Manual
87
Creating Equipment/Facilities Manually
Step 8
Close the Provisioning Manager window by selecting Close.
End of Procedure
How to Clone a Module This instruction describes how to clone an existing module, with the option of changing some parameters. This saves time when configuring several modules of the same type, with the same configurations. The cloning process starts with the module entity and leads you through provisioning all dependent entities which have been provisioned in the originating module, with the provisioning of the originating module as the parameter defaults. However, dependent entities that were not provisioned on the originating module are not offered for provisioning on the cloned module in the cloning process. They must be provisioned manually afterwards. ECC channels, belonging DCN cross-connects and protection groups are not copied in the cloning process.
Step 1
Select the relevant module to clone from the tree of entities in the Entity pane.
Step 2
From the Main Menu, select Configuration -> Provisioning -> Clone. Alternatively, right-click the relevant module to display the context sensitive menu, and select Clone. In response, the Clone Module wizard opens.
Specify which slot you wish to provision the clone module into by selecting a module AID from the tree list of entities in the Clone Module, Target Selection page. It is not possible to overwrite existing provisioning, therefore only unassigned slots are supported as targets for a module clone.
Select Next to continue to the Parameters Step 1 page.
User Manual
89
Creating Equipment/Facilities Manually
Step 4
The Parameters Step 1 page displays the parameters that were set on the originating module, with the same values as on the originating module. Adjust these parameters as required for the cloned module. To aid you in the adjustment, the right hand side of the page can display the progress of the cloning process, or the parameter values that have been set so far. •
Select the Progress radio button to display the list of dependent entities on the originating module, which you are in the process of cloning on the target module. Each entity that has had its values set, has a green check mark. The entity that you currently can adjust values for has an orange arrow. Select the Parameters radio button to display the values that have been selected for the entities that have been adjusted so far. This can be useful to remember what adjustments you wish to make on the rest of the entities.
90
User Manual
Chapter 3 Provisioning NEs
Step 5
Select Next to continue. In response you will be presented for as many new pages as are necessary in order to lead you through adjustment the parameter values for this entity. When all parameter values have been entered for this entity, Confirm page will be displayed.
Do one of the following: • If the values are incorrect, select Cancel. The cloning will be aborted, all cloned entities created thus far in this process will be deleted. • Confirm that the values are correct by selecting Next. If there are further entities to clone, you will be presented the necessary amount of parameter entry pages to adjust all parameter values. When all entities have been presented, and adjusted if relevant, the Result page. is displayed.
Step 7
User Manual
The Progress view shows all entities that were cloned. You can review the parameter values for all cloned entities by selecting the Parameters radio button.
91
Creating Equipment/Facilities Manually
Step 8
Select Finish to close the Clone Module wizard.
Step 9
If relevant, provision additional dependent entities on the cloned nodule.
Step 10
If relevant, provision a DCN cross-connect or protection group involving this new, cloned module.
End of Procedure
How to Create a Plug This section describes how to create a pluggable transceiver in the internal database, using the Provisioning Manager window. Follow this instruction only for modules that use pluggable transceivers. After creation, the module is selectable from the PL---<{C{1..x}|N|NE|NW}> entity in the Entity pane.
Procedure Select the module that you wish to add a pluggable transceivers to, using the hierarchical list of entities on the left of the Provisioning Manager window. In response, the right side of the Provisioning Manager window displays the Create Plug list. This is a list of AID addresses for the cages that you may add pluggable transceiver to on the selected module. Step 2
Select the relevant cage AID address from the list. In response the Create Plug wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
Step 3
In the Parameters Step 1 page, use the Equipment Type drop-down list to select the relevant pluggable transceiver type.
Step 4
In the next pages of the Create Plug wizard, you are required to enter the rate, WDM channel number, reach, usage of 3rd party plugs and the administrative state. Enter the required parameters in the wizard page as follows: a) Use the drop-down lists and controls that the wizard provides, to select the relevant parameter values. See the document Management Data Guide for descriptions of these parameters for this module type. b) Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters.
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete page appears.
Step 6
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 7
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 8
Close the Provisioning Manager window by selecting Close.
You use ports to create a connection that can carry traffic. For example:
User Manual
•
A connection that can carry traffic must have a client port and network port on the channel modules in both the near end and far end NE. After creation, the port (channel) is selectable from the CH---<{C{1..x}|N|NE|NW}>- entity in the Entity pane.
•
A connection that can carry traffic through an ROADM-C40/40/2-3HU-2DC shelf must have a client port (optical channel) and an network port (optical multiplex facility) on the shelf. After creation, the port (channel) is selectable from the CH----C{1..40} OCH or OM--OM in the Entity pane.
•
A connection that can carry traffic through an EDFA module must have a port. After creation, the port is selectable from the OM---1-EDFA or OM---2-EDFA-MID entities in the Entity pane.
•
A connection that can carry traffic through an VSM or RSM module must have a port. After creation, the port is selectable from the OM---{NE|NW}-SWITCH entity in the Entity pane.
93
Creating Equipment/Facilities Manually
Procedure Step 1
Select the module or shelf that you wish to add a port to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection. In response, the right side of the Provisioning Manager window displays the Create Port list. This is a list of AID addresses for the ports that you may add to the selected module, or to the selected module’s pluggable transceiver. In some cases the module’s configuration does not support use of one or more of the module’s plugs. In these cases the AID address for the port corresponding to the plug is not offered for selection in the list. This is also true even if the pluggable transceiver cage is equipped and thus displayed in the Entity pane.
Step 2
Select the relevant channel AID address from the list. In response the Create Port wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. In the Parameters Step 1 page, use the Facility Type drop-down list to select the relevant facility type for the channel. To configure a FICON service, select the facility type FC. To configure a 10G WAN service, select the facility type STM-64.
Step 4
For channel modules that support configuration of trace: • Select the Configure Trace radio button if you wish to configure trace. • Select the Use Defaults radio button if you wish to use the default settings for trace.
Step 5
The rest of the parameters you are required to enter in this first page, and the next pages of the Create wizard, depend on your selection of the facility type. Enter the required parameters in the wizard pages as follows: a) Use the drop-down lists and controls that the wizard provides, to select the relevant parameter values. See the document Management Data Guide for descriptions of these parameters, for this module/shelf type and use of the module/shelf type. b) Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters.
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete window appears.
Step 7
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 8
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 9
Close the Provisioning Manager window by selecting Close.
How to Clone a Channel (Port) This instruction describes how to clone an existing client or network channel (port) on a module, with the option of changing some of the parameters. This saves time when configuring several ports of the same type, with the same configurations. The cloning process starts with the channel entity and leads you through provisioning all dependent entities which have been provisioned in the originating channel, with the provisioning of the originating channel as the parameter defaults. However, dependent entities that were not provisioned on the originating module are not offered for provisioning on the cloned module in the cloning process. They must be provisioned manually afterwards. ECC channels, belonging DCN cross-connects and protection groups are not copied in the cloning process. All changes to the database are logged in the database change log.
Step 1
Select the relevant channel (port) to clone from the tree of entities in the Entities pane.
Step 2
From the Main Menu, select Configuration -> Provisioning -> Clone. Alternatively, right-click the relevant module to display the context sensitive menu, and select Clone. In response, the Clone Port wizard opens.
Specify which channel you wish to clone the provisioning of the originating channel into by selecting a channel AID from the tree list of entities in the Clone Port, Target Selection page. It is not possible to overwrite existing provisioning, therefore only unassigned channels are supported as targets for a channel clone. Select Next to continue to the Parameters Step 1 page.
The Parameters Step 1 page displays the parameters that were set on the originating channel, with the same values as on the originating channel. Adjust these parameters as required for the cloned channel. Select Next to continue. In response you will be presented for as many new pages as are necessary in order to lead you through adjustment the parameter values for this entity. When all parameter values have been entered for this entity, Confirm page will be displayed.
User Manual
97
Step 5
Do one of the following: • If the values are incorrect, select Cancel. The cloning will be aborted, all cloned entities created thus far in this process will be deleted. • Confirm that the values are correct by selecting Next. The Result page will be displayed.
Step 6
Select Finish to close the Clone Port wizard.
Step 7
If relevant, provision additional dependent entities on the cloned channel.
Step 8
If relevant provision a DCN cross connect or a protection group involving the cloned channel.
How to Change a Service (Channel) This instruction describes how to change a service. To do this manually, the channel must first be deleted, then re-provisioned. The Element Manager aids the operator in making changes to a a client or network channel. Changing a service is service-affecting.
Procedure Step 1
Select the client or network channel that you wish to make changes to.
Step 2
From the Main Menu, select Configuration -> Provisioning -> Change Service. Alternatively, right-click the relevant module to display the context sensitive menu, and select Change Service.
Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Change the required parameters. Enter the required parameters in the wizard pages as follows: a) Use the drop-down lists and controls that the wizard provides, to select the relevant parameter values. See the document Management Data Guide for descriptions of these parameters for this module/channel type if necessary. b) Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters.
User Manual
99
Creating Equipment/Facilities Manually
Step 3
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Result window appears.
End of Procedure
How to Create a Virtual Channel This section describes how to create a virtual channel in the internal database, using the Provisioning Manager window. Multiplexing channel modules and ROADM-C40/40/2-3HU-2DC shelves support virtual channels.
•
Each client service is carried by a virtual channel on the network port. After creation, the virtual channel is selectable from the VCH---<{C{1..x}|N|NE|NW}>- entity in the Entity pane.
•
Each client service in a ROADM-C40/40/2-3HU-2DC shelf is carried by a virtual channel on the network port optical multiplex facility. After creation, the port (channel) is selectable from the VCH---N{1..40} OCH in the Entity pane.
Procedure Step 1
Select the module or shelf that you wish to add a virtual channel to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection. In response, the right side of the Provisioning Manager window displays the Create Virtual Channel list. This is a list of AID addresses for the virtual channels that you may add to the selected shelf, the selected module, or to the selected module’s pluggable transceivers.
Step 2
Select the relevant channel AID address from the list. In response the Create Virtual Channel wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Navigate between the pages by selecting either: • •
Next to continue to the next wizard page. Back to return to the previous wizard page, and make changes to
You use virtual channels to carry the services that shall be multiplexed. For example:
Chapter 3 Provisioning NEs
Step 3
In the next pages of the Create Virtual Channel wizard, enter the required parameters in the wizard pages as follows: a) Use the drop-down lists and controls that the wizard provides, to select the relevant parameter values. See the document Management Data Guide for descriptions of these parameters for this module type. • For channel modules that support configuration of trace: • Select the Configure Trace radio button if you wish to configure trace. • Select the Use Defaults radio button if you wish to use the default settings for trace. • Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters. See the document Management Data Guide for descriptions of these parameters.
When the Confirm wizard page appears: • Check that the displayed settings are correct. • If the settings are incorrect: Select Back to go back and correct the settings. • If the settings are correct: Select Next to confirm. In response, the Complete page appears.
Step 5
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 6
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 7
Close the Provisioning Manager window by selecting Close.
End of Procedure
How to Create an Ethernet Port (ETH) This section describes how to create a Ethernet port (ETH entity) on an xPCA module in the internal database, using the Provisioning Manager window. The ETH port holds the Ethernet properties for the ports on an xPCA channel module. In the case that the ETH port shall be a member of a LAG group (VETH entity), the majority of the parameters for this ETH are derived from the LAG (VETH entity) they are members of. Therefore there are a limited number of parameters to enter for these ETHs. This section covers also this case of an ETH port creation. After creation, the ETH facility is selectable from the ETH---<{C{1..10}||NE|NW}>-entity in the Entity pane.
User Manual
101
Creating Equipment/Facilities Manually
Requirements •
The xPCA channel module has been provisioned and the administrative state is Automatic In Service or In Service. If the ETH port shall be part of a LAG group, the xPCA channel module must already be configured with the correct Link Aggregation System Priority (LAG Actor Sys Pri).
•
The pluggable transceiver (PL entity) on the interface has been provisioned correctly and the administrative state is Automatic In Service or In Service.
Procedure Step 1
Select the xPCA module that you wish to add a ETH port to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection. In response, the right side of the Provisioning Manager window displays the Create Port list. This is a list of AID addresses for the ETH facilities that you may add to the selected module.
Step 2
Select the relevant ETH AID address from the list.
Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Navigate between the pages by selecting either: • •
Next to continue to the next wizard page. Back to return to the previous wizard page, and make changes to
In the page Parameters Step 1, do as follows: a) If this is a client port, set Auto-Negotiation to either Enabled or Disabled. Autonegotiation is not supported for ports with XFP pluggable transceivers. b) If this is a 2PCA-PCN-10G module, specify whether the Ethernet port shall behave as a client port or a network port by using the Behavior field. This means that for example a client port can have network port behavior. If the port shall be used against your client’s equipment it should be set to behavior Client. The 10PCA-PCN+10G port behavior is directly linked to the port type, a client port has client behavior and a network port has network behavior. c) Do one of the following: • If the ETH port shall not be member of a LAG group, set Member of Virtual Port to NONE. • If the ETH port shall be member of a LAG group, go to Step 9. Select Next to continue.
In the page Parameters Step 2, do as follows: a) Set the Port Role as planned in the network design. It has effect on which modes the port can operate in: • Role UNI is used to interface user equipment. • Role NNI is used for handing over to the next network. • Role I-NNI is used to connect xPCA modules together in a ring, line or mesh topology. All ports can play the I-NNI role. The port’s role has effect on which modes the port can operate in. Port Role/Port Mode versus IEEE Provider Bridge
Port Role
Port Mode
IEEE Provider Bridge Port Name
UNI
Port based C-tagged S-tagged Port based C-tagged S-tagged Port based C-tagged S-tagged
Customer Network Port (CNP) Customer Edge Port (CEP) Customer Network Port (CNP) Not supported Not supported Provider Network Port (PNP) Not supported Not supported Provider Network Port (PNP)
NNI
I-NNI
In addition only ports with port role I-NNI can be members of an Ethernet linear protection group. b) Enter the default PCP priority the port shall use for untagged frames in the Port default PCP field. If the port is configured to accept untagged frames, a C-tag or an S-tag will be added to untagged frames at Rx. The Customer VLAN Identifier (CVID) or Service VLAN Identifier (SVID) will be equal to your entry in the Port VLAN ID field (see Step 8) and the PCP priority will be equal to your entry in the Port default PCP field. Select Next to continue. In response the Parameters Step 3 page appears.
Step 5
If selectable, set the Port Mode for the port. The port can operate in the modes PORT, CTAG or STAG, depending on the port’s role. Select Next to continue. In response the Parameters Step 3 page appears.
Your choice of port mode affects which parameters will be available for provisioning in the following. • If you selected PORT, go to Step 7. • If you selected CTAG or STAG, go to Step 8.
Step 7
In response to the selection of port mode PORT, the Parameters Step 4 page displays the relevant parameters. a) Set the administrative state (Admin State field) to Automatic in Service or In Service. b) Define which incoming frames to discard, based on their EtherType (Ether TAG Type). Incoming frames matching this EtherType will be discarded. To discard S-tagged frames enter the value 0x88a8 and to discard C-tagged frames enter the value 0x8100. The default is to discard S-tagged frames.
c) Define when incoming frames shall be discarded due to their size by entering the maximum acceptable frame size into the Max Frame Size field. This feature can be used to allow incoming SVLAN tagged frames to be transported and encapsulated with yet another SVLAN tag. The forwarded frame will use the Ether TAG Type field of the transmitting port. Discarding of frames larger than the maximum frame size is done at Rx. If tags are added between Rx and Tx, this means that the frame may be larger than the maximum frame size at Tx. On I-NNI ports one more tag is added to each frame as compared to UNI ports operating in CTAG and PORT modes. Therefore the max frame size should be 4 bytes longer on I-NNI ports. The default value takes this into consideration. If you enter a different value, remember to take this into consideration. d) Go to Step 13.
User Manual
105
Creating Equipment/Facilities Manually
Step 8
In response to the selection of port mode CTAG or STAG, the Parameters Step 4 page displays the relevant parameters. a) Set the administrative state (Admin State field) to Automatic in Service or In Service.
c) Define when incoming frames shall be discarded due to their size by entering the maximum acceptable frame size into the Max Frame Size field. Discarding of frames larger than the maximum frame size is done at Rx. If tags are added between Rx and Tx, this means that the frame may be larger than the maximum frame size at Tx. On I-NNI ports one more tag is added to each frame as compared to UNI ports operating in CTAG and PORT modes. Therefore the max frame size should be 4 bytes longer on I-NNI ports. The default value takes this into consideration. If you enter a different value, remember to take this into consideration. d) Enter the Port VLAN ID in the Port VLAN ID field. If the port is configured to accept untagged frames, a C-tag or an S-tag will be added to untagged frames at Rx. The CVID or SVID will be equal to your entry in the Port VLAN ID field and the PCP priority will be equal to your entry in the Port default PCP field (see Step 3). ID 4095 is reserved for EOC channels and shall not be used. Addition of a C-tag to untagged frames can also be configured at Tx. This is however configured on the FLW entity (the PUSH PVID Transmit and Prio PVID Transmit field). e) Select acceptance or rejection of untagged and priority-tagged frames using the Untagged frames drop-down list. f)
b) Enter the EtherType (Ether TAG Type). Detection of C- and S-tagged frames is done based on the EtherType field. Incoming frames matching this EtherType will be accepted. To accept S-tagged frames enter the value 0x88a8 and to accept C-tagged frames enter the value 0x8100. It is for example relevant to enter a different value when interfacing to older equipment that uses a non-standard Ether type. This feature can be used to allow incoming SVLAN tagged frames to be transported and encapsulated with yet another SVLAN tag. The forwarded frame will use the Ether TAG Type field of the transmitting port.
Chapter 3 Provisioning NEs
Step 9
Enter the LAG group (VETH entity) that the ETH port shall be member of, using the Member of Virtual Port drop-down list. Select Next to continue. In response the Parameters Step 2 page appears.
Step 10
Enter the actor port priority (Actor Port Pri field).
This is used to define which ETH port is the active port in a LAG. The port with the lowest number has the highest priority and is thus the active port. Step 11
Set the administrative state (Admin State field) to Automatic in Service or In Service.
Step 12
Go to Step 13.
Step 13
Select Next to continue. In response the Confirm wizard page appears.
Step 14
Check that the displayed settings are correct. • If the settings are incorrect: Select Back to go back and correct the settings. • If the settings are correct: Select Next to confirm. In response, the Complete page appears.
Step 15
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 16
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
End of Procedure
How to Create a Virtual Ethernet Port (VETH) This section describes how to create an Virtual Ethernet Port (VETH) on an xPCA module in the internal database, using the Provisioning Manager window. The VETH port is used when creating a Link Aggregation Group (LAG). The VETH holds the LAG-specific parameters and the packet handling layers for the member ports. The the Ethernet ports (ETH) that are members of the VETH hold the physical layer Ethernet properties for each member.
User Manual
107
Creating Equipment/Facilities Manually
After creation, the VETH facility is selectable from the VETH---<{V{1..n}>-entity in the Entity pane.
Requirements •
The xPCA channel module has been provisioned, the xPCA channel module must already be configured with the correct Link Aggregation System Priority (LAG Actor Sys Pri), and the administrative state is Automatic In Service or In Service.
•
The pluggable transceiver (PL entity) on the interface has been provisioned correctly and the administrative state is Automatic In Service or In Service.
•
No member ETH ports and belonging flow points (FLWs) are allowed to exist at VETH creation time.
Procedure Step 1
Select the xPCA module f that you wish to add a VETH facility to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection.
Step 2
Select the relevant VETH AID address from the list. In response the Create port wizard starts.
Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Navigate between the pages by selecting either: • •
Next to continue to the next wizard page. Back to return to the previous wizard page, and make changes to
In response, the right side of the Provisioning Manager window displays the Create Port list. This is a list of AID addresses for the VETH facilities that you may add to the selected module.
Chapter 3 Provisioning NEs
Step 3
In the page Parameters Step 1, enter the required parameters: a) Use the LACP MODE drop-down list to specify the Link Aggregation Control Protocol (LACP) mode for this LAG as either ACTIVE or PASSIVE. b) Enter the LACP Time Out, either long or short. c) Enter the number of active ports that will be members of this LAG, into the LAG Active ports field. In this release only one active port is supported. d) Use the LAG Port Type drop down list to select the port types of the ports that shall be members of the LAG, either 1GE or 10 GE. e) Set the Port Role as planned in the network design. It has effect on which modes the port can operate in: • Role UNI is used to interface user equipment. • Role NNI is used for handing over to the next network. • Role I-NNI is used to connect xPCA modules together in a ring, line or mesh topology. All ports can play the I-NNI role. The port’s role has effect on which modes the port can operate in.
Port based C-tagged S-tagged Port based C-tagged S-tagged Port based C-tagged S-tagged
Customer Network Port (CNP) Customer Edge Port (CEP) Customer Network Port (CNP) Not supported Not supported Provider Network Port (PNP) Not supported Not supported Provider Network Port (PNP)
NNI
I-NNI
f)
Enter the default PCP priority the port shall use for untagged frames in the Port default PCP field. If the port is configured to accept untagged frames, a C-tag or an S-tag will be added to untagged frames at Rx. The Customer VLAN Identifier (CVID) or Service VLAN Identifier (SVID) will be equal to your entry in the Port VLAN ID field (see Step 7) and the PCP priority will be equal to your entry in the Port default PCP field.
Select Next to continue. In response the Parameters Step 2 page appears.
User Manual
109
Creating Equipment/Facilities Manually
Step 4
Your choice of port role affects which parameters will be available in the Parameters Step 2 page. • If you selected UNI, you must set the Port Mode for the port.The port can operate in the modes PORT, CTAG or STAG.
Step 5
Your choice of port mode affects which parameters will be available for provisioning in the following. • If you selected PORT, go to Step 6. • If you selected CTAG or STAG, go to Step 7.
Step 6
In response to the selection of port mode PORT, the Parameters Step 3 page appears. Enter the required parameters. a) Define which incoming frames to discard, based on their EtherType (Ether TAG Type). Incoming frames matching this EtherType will be discarded. To discard S-tagged frames enter the value 0x88a8 and to discard C-tagged frames enter the value 0x8100. The default is to discard S-tagged frames. This feature can be used to allow incoming SVLAN tagged frames to be transported and encapsulated with yet another SVLAN tag. The forwarded frame will use the Ether TAG Type field of the transmitting port. b) Define when incoming frames shall be discarded due to their size by entering the maximum acceptable frame size into the Max Frame Size field. Discarding of frames larger than the maximum frame size is done at Rx. If tags are added between Rx and Tx, this means that the frame may be larger than the maximum frame size at Tx. On I-NNI ports one more tag is added to each frame as compared to UNI ports operating in CTAG and PORT modes. Therefore the max frame size should be 4 bytes longer on I-NNI ports. The default value takes this into consideration. If you enter a different value, remember to take this into consideration. c) Set the administrative state (Admin State field) to Automatic in Service or In Service. d) Go to Step 8.
In response to the selection of port role NNI or I-NNI, the Parameters Step 2 page appears. Enter the required parameters. a) Enter the EtherType (Ether TAG Type). Detection of C- and S-tagged frames is done based on the EtherType field. Incoming frames matching this EtherType will be accepted. To accept S-tagged frames enter the value 0x88a8 and to accept C-tagged frames enter the value 0x8100. It is for example relevant to enter a different value when interfacing to older equipment that uses a non-standard Ether type. This feature can be used to allow incoming SVLAN tagged frames to be transported and encapsulated with yet another SVLAN tag. The forwarded frame will use the Ether TAG Type field of the transmitting port.
b) Define when incoming frames shall be discarded due to their size by entering the maximum acceptable frame size into the Max Frame Size field. Discarding of frames larger than the maximum frame size is done at Rx. If tags are added between Rx and Tx, this means that the frame may be larger than the maximum frame size at Tx. On I-NNI ports one more tag is added to each frame as compared to UNI ports operating in CTAG and PORT modes. Therefore the max frame size should be 4 bytes longer on I-NNI ports. The default value takes this into consideration. If you enter a different value, remember to take this into consideration. c) Enter the port VLAN ID. If the port is configured to accept untagged frames, a C-tag or an S-tag will be added to untagged frames at Rx. The CVID or SVID will be equal to your entry in the Port VLAN ID field and the PCP priority will be equal to your entry in the Port default PCP field (see Step 3). ID 4095 is reserved for EOC channels and shall not be used. Addition of a C-tag to untagged frames can also be configured at Tx. This is however configured on the FLW entity (the PUSH PVID Transmit and Prio PVID Transmit field). d) Set acceptance or rejection of untagged and priority-tagged frames using the Untagged frames item. e) Set the administrative state (Admin State field) to Automatic in Service or In Service. f) Step 8
Go to Step 8.
Select Next to continue. In response the Confirm wizard page appears.
Step 9
Check that the displayed settings are correct. • If the settings are incorrect: Select Back to go back and correct the settings. • If the settings are correct: Select Next to confirm. In response, the Complete page appears.
User Manual
111
Creating Equipment/Facilities Manually
Step 10
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 11
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 12
Close the Provisioning Manager window by selecting Close.
End of Procedure
How to Create an EOC Channel This section describes how to create an EOC channel in the internal database, using the Provisioning Manager window.
•
A channel module that supports an EOC channel must already be provisioned. See “How to Create a Module” on p. 87.
•
The network port pluggable (if supported by the module) and channel must already be provisioned on the channel module. See “How to Create a Plug” on p. 92 and “How to Create a Port” on p. 93.
•
Ensure that there is enough un-used backplane bandwidth to support this backplane connection. This information can be found on the NE tab of the network element. See the Detailed System Description, “Deployment Restrictions” for information about backplane bandwidth restrictions and allocated backplane bandwidth per DCN entity.
Procedure Step 1
Select the module that you wish to add an EOC channel to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection.
Step 2
If the required entities have been provisioned already, the Provisioning Manager window will display the Create DCN Channel list section on the right side.
Step 3
Select the relevant EOC channel type in the list (for example EOC-2-9-NE). In response the Create DCN Channel wizard starts.
In the Parameters Step 1 page, set the administrative state for the EOC/ECC channel with the Admin State drop-down list.
Step 5
Select Next to continue. In response the Confirm wizard page appears.
Step 6
Check that the displayed settings are correct. a) If the settings are incorrect: Select Back to go back and correct the settings. b) If the settings are correct: Select Next to confirm. In response, the Complete window appears.
Step 7
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 8
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 9
Close the Provisioning Manager window by selecting Close.
How to Create an SDH/SONET/OTN based ECC Channel This section describes how to create an SDH/SONET/OTN based ECC channel in the internal database, using the Provisioning Manager window.
Requirements
User Manual
•
A channel module that supports SDH, SONET or OTN must already be provisioned. See “How to Create a Module” on p. 87.
•
A port must already be provisioned on the channel module. See “How to Create a Port” on p. 93.
•
Ensure that there is enough un-used backplane bandwidth to support this backplane connection. This information can be found on the NE tab of the network element. See the Detailed System Description, “Deployment Restrictions” for information about backplane bandwidth restrictions and allocated backplane bandwidth per DCN entity.
113
Creating Equipment/Facilities Manually
Procedure Step 1
Select the module that you wish to add an EOC/ECC channel to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection.
Step 2
If the required entities have been provisioned already, the Provisioning Manager window will display the Create DCN Channel list section on the right side.
Select the relevant EOC/ECC channel type in the list (for example SDCC-1-8-N). In response the Create DCN Channel wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
Step 4
In the Parameters Step 1 page, use the Facility Type drop-down list to select the relevant EOC/ECC type, for example SDCC.
Step 5
Set the administrative state for the EOC/ECC channel with the Admin State drop-down list.
Step 6
Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters.
Step 7
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete window appears.
Step 8
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 9
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Close the Provisioning Manager window by selecting Close.
End of Procedure
How to Create an Ethernet based ECC Channel This section describes how to create an Ethernet based ECC channel in the internal database, using the Provisioning Manager window.
Requirements •
A 10PCA-PCN+10G channel module must already be provisioned. See “How to Create a Module” on p. 87.
•
An Ethernet port (ETH) must already be provisioned on the client or network port. See “How to Create an Ethernet Port (ETH)” on p. 101.
•
Ensure that there is enough un-used backplane bandwidth to support this backplane connection. This information can be found on the NE tab of the network element. See the Detailed System Description, “Deployment Restrictions” for information about backplane bandwidth restrictions and allocated backplane bandwidth per DCN entity.
Select the 10PCA-PCN+10G module that you wish to add an ECC channel to. Use the hierarchical list of entities on the left of the Provisioning Manager window for this selection.
Step 2
If the required entities have been provisioned already, the Provisioning Manager window will display the Create DCN Channel section on the right side.
Step 3
Select the relevant ECC channel in the list (for example EOC-1-3-C1). In response the Create DCN Channel wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
User Manual
115
Creating Equipment/Facilities Manually
Step 4
In the Parameters Step 1 page, set the administrative state for the ECC channel with the Admin State drop-down list.
Step 5
Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page, and make changes to the parameters.
Step 6
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete window appears.
Step 7
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 8
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 9
Close the Provisioning Manager window by selecting Close.
How to Create a PPP IP Interface This instruction describes how to create a PPP IP interface on the NCU. PPP IP interfaces are part of the FSP3000R7 DCN. This DCN should be planned, please use the planned values when creating PPP IP interfaces.
Restrictions Ensure that there is enough un-used backplane bandwidth to support this backplane connection. This information can be found on the NE tab of the network element. See the Detailed System Description, “Deployment Restrictions” for information about backplane bandwidth restrictions and allocated backplane bandwidth per DCN entity.
Select the NCU. Use the left hand hierarchical entity list in the Provisioning Manager window for this selection. The Provisioning Manager window will display the Create PPP IP Interface list section on the right side.
Step 2
Select one of the NCU PPP IP links from the list (for example LINK-1A-3).
In response the Create PPP IP Interface wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Step 3
In the Parameters Step 1 and 2 page, you will be asked to specify: Max Tx Rate [Kbit/s] The maximum transmit rate that you specify here, must be lower than the absolute maximum that can be carried by the EOC/ECC that uses this PPP IP interface. Otherwise traffic may be lost and the connection will be slow. The default value is 100 kbit/s. Check
•
User Manual
117
• •
• •
•
•
•
Step 4
118
the maximum value for the relevant ECC entity in the Management Data Guide document, under the section for that channel module. The following lists the maximum value for some of the ECC types: • GCC0/GCC1/GCC2 on OTU3/ODU3: 1312 kbit/s (limited from 5248 kbit/s) • GCC0/GCC1/GCC2 on OTU2/ODU2: 1312 kbit/s • GCC0/GCC1/GCC2 on OTU1/ODU1: 326 kbit/s • SDCC/DCCr: 192 • LDCC/DCCm: 576 • EOC: 1000 (ADVA proprietary framing) OSPF Routing Select Enabled if OSPF is planned used for this interface. Routing Metric Enter the routing metric if OSFP is enabled. The default is 100, independently of the bandwidth of the IP interface. Enable Proxy ARP Select whether proxy ARP shall be used or not. Area ID Specify the area ID for the PPP IP interface. An OSPF network can be divided into sub-domains, called areas, and these areas are identified by an area ID. An area is a logical collection of OSPF networks, routers, and links that have the same area identification. Type of IP config Select whether this interface is numbered or unnumbered. For a numbered interface you must provision the IP address and mask. The system IP address and subnet mask are re-used for this unnumbered interface. All unnumbered interfaces share the same values. Only one logical LAN port or Ethernet port on the NCU can be unnumbered at any one time. Near End IP Address If you specified that this is a numbered interface, this field will appear. Use the planned IP address. Remember that if OSPF is planned for any IP interface in the NE, every IP address must be unique in the system. Admin State Set the relevant value for administrative state at this time. In order for the interface to become operational, you must select In Service or Automatic In Service.
Select either: • Next to continue to the next wizard page. • Back to return to the previous wizard page and make changes to the parameters.
When the Confirm wizard page appears: • Check that the displayed settings are correct. • If the settings are incorrect: Select Back to go back and correct the settings. • If the settings are correct: Select Next to confirm. In response, the Complete window appears.
Step 6
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 7
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 8
Close the Provisioning Manager window by selecting Close.
Create the network side supervisory channel on the OSCM, for example SC-3-17-N, and provision it as described in “How to Create a Port” on p. 93. This is the entity that supports the out of band OSC channel through the system.
Step 2
Create a client side supervisory channel on the OSCM port the NCU is connected to, for example SC-3-17-C1, and provision it as described in “How to Create a Port” on p. 93. Use the same parameter values that have been set for the NCU Ethernet port that the OSCM client port is connected to.
End of Procedure
User Manual
119
Creating Equipment/Facilities Manually
How to Create an Optical Line The optical line (OL) entity represents a network fiber endpoint, which is connected to the NE.
Procedure Step 1
Select the NE. Use the left hand hierarchical entity list in the Provisioning Manager window for this selection.
Step 2
Select one of the optical lines from the list (for example OL-1). In response the Create Optical Line wizard starts.
Step 3
Select either: • Next to create the optical line. • Cancel to abort the creation. In response, the Result window appears.
Step 4
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Result page.
Step 5
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 6
120
Close the Provisioning Manager window by selecting Close.
Enter the attenuation of the receive and transmit fiber into the Attenuation Rx Fiber and Attenuation Tx Fiber fields.
Step 10
Enter a text string identifying the NE in the at the other end point of the network fiber into the FEND field. For example: NE2 ROADM.
Step 11
Select OK.
Step 12
You are returned to the Parameters pane.
End of Procedure
How to Create Equipment/Facilities Automatically This section contains the instruction for setting provisioning preferences. This includes enabling automatic provisioning, enabling provisioning with Automatic In Service administrative state (both for manual and auto-provisioning) as well as preferred facility.
Procedure Step 1
Double-click the relevant Network Element in the Managed Elements pane. In response, the Parameter pane displays the System page.
User Manual
121
How to Create Equipment/Facilities Automatically
Step 2
Select the Database tab. In response, the Parameter pane displays the Database page. In this page the current setting of the Auto-Provisioning parameter and the related parameters is displayed.
Step 3
Select the Modify button on the Database tab. In response, the Modify window appears.
Step 4
If the Auto-Provisioning parameter is currently set to No: Change it to Yes as follows: b) In response, the Network Element will automatically provision all shelves, modules, pluggable transceivers and derivable facilities. Any new equipment that is added will also be automatically provisioned.
Step 5
Use the Preferred Facility Type drop-down list to select whether auto provisioned channel facilities shall be SDH or SONET.
Step 6
Use the AINS Enabled drop-down list to select whether provisioned entities shall be set to state Automatic In Service or not. When Automatic In Service state is used, the entity will automatically transition to administrative state In Service when all conditions causing the Outage or Supporting Entity Outage operational states have been cleared for a specific time period. You can only set an entity’s administrative state to Automatic In Service if the entity that supports it is also Automatic In Service or In Service and the entity that is supports is not In Service.
Step 7
If you set AINS Enabled to Yes: Use the AINS Default Timer field to specify the period of time that the operational state Outage or Supporting Entity Outage operational states must have been cleared before automatic transition to In Service shall take place.
Step 8
Select OK to apply the change, or Cancel to discard the change.
a) Use the Auto-Provisioning drop-down list to select Yes.
Chapter 3 Provisioning NEs
Managing Encryption Modules How to set-up and manage encryption modules is described in the FSP 3000 Provisioning and Operations Manual, “Provisioning Encryption Modules”. This section supports the FSP 3000 Provisioning and Operations Manual by giving more detailed guidance on using the Element Manager to perform each individual task involved. The instructions in this section should only be followed for additional support in conjunction with the procedures for managing encryption modules in the FSP 3000 Provisioning and Operations Manual.
General Requirements •
The network element (NE) that shall support encryption modules has to be equipped with an NCU-II module (second-generation NCU).
•
Both the far-end and near-end encryption module must provisioned completely the same way: o
both module entities are created and available all optical parameters are set
•
To successfully change or set any security-related parameters, authentication via the CO password is required.
•
The Element Manager is set to manage the NE via SNMPv3, using an user account with ADMIN privileges.
Follow the procedures in this sequence: Configuring Initial Settings, which are essential for the module operation Configuring Maintenance Settings, which can optionally be set as required
Configuring Initial Settings After provisioned to the network element (NE), encryption modules require two initial settings to fully encrypt data.
The Inventory tab and Crypto tab will be blocked for a couple of seconds, immediately after the module is created. During this period, the MOD LED blinks yellow. When the LED turns RED, the module is ready for operation.
Follow these procedures to get started with encryption modules: How to Change the Crypto-Officer Password How to Specify the Module Authentication Password How to View the Key Exchange
How to Change the Crypto-Officer Password This instruction describes how to change the Crypto-Officer (CO) password and thus acquire ownership of the encryption module.
User Manual
123
Managing Encryption Modules
The CO password has to be changed on both the near-end and far-end encryption module. CO passwords can be different for each encryption module.
Requirements •
The CO password has to be changed on both the near-end and far-end encryption module. CO passwords can be different for each encryption module.
•
Ensure that you are familiar with the requirements in “General Requirements” on p. 123.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the encryption module in the Entities pane.
Step 3
Set the administrative state (Admin State field) to Maintenance ( see “How to Change the Administrative State” on p. 260).
Step 4
Set the administrative state of all dependant entities to Maintenance. You can see the dependant entities by expanding the Dependent Entities field,
Step 5
Select the Crypto tab in the Parameter pane. In response the encryption related parameters of the module are displayed.
Step 6
From the Actions button, select Change Password. In response the Change Password window appears.
In response, all available information about the entity is displayed in the Parameter pane.
Chapter 3 Provisioning NEs
Step 7
Enter the currently used CO password in the Old Password field. If this is the first time you change the password, the currently used password is “CHANGEME.1”.
Step 8
Enter the new CO password in the New Password field, ensure it is different from the old password. The password must comply with the following requirements: • • •
consist of at least 10 and at most 32 characters consist of at least one lower [ a ..z] and one upper character [A..Z] plus a number [0..9] optionally contain special characters [!,@, #, $, %, ^, (, ), _, +, |, ~, {, }, [, ], -, .]
Step 9
Re-enter the new password in the Confirm New Password field.
Step 10
Select OK to save your settings, or Cancel to cancel them. In response the MOD LED of the module changes from red to green.
How to Specify the Module Authentication Password This instruction describes how to specify the authentication password that the encryption modules use for identification.
PS
Note
The authentication password has to be changed on both the near-end and far-end encryption modules within 15 minutes. Therefore you must be able to quickly access the far-end module.
When you have completed this instruction for the encryption modules in each end of the encryption link, a first key exchange will take place. If the key exchange is successful , encryption of the link will start. You can then verify the first key exchange, if required, as described in How to View the Key Exchange.
Requirements
User Manual
•
The authentication password has to be changed on both the near-end and far-end encryption module. Communicating encryption modules must have the same authentication password.
•
Ensure that you are familiar with the requirements in “General Requirements” on p. 123.
•
Ensure that you know the IP address of the far-end NE and the CO password of the far-end encryption module.
125
Managing Encryption Modules
Procedure Step 1
Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the encryption module in the Entities pane. In response, all available information about the entity is displayed in the Parameter pane.
Step 3
Select the module’s network channel (for example CH-1-17-N OTU2P).
In response, all available information about the entitiy is displayed in the Parameter pane. Step 4
Set the administrative state (Admin State field) to Maintenance ( see “How to Change the Administrative State” on p. 260).
Step 5
Select the Crypto tab in the Parameter pane.
Step 6
From the Actions button, select Change AuthKey. In response the Change Authenticaion key window appears.
In response the encryption related parameters of the module are displayed.
Chapter 3 Provisioning NEs
Step 7
Enter a new authentication password in the Authentication key field. The password must comply with the following requirements: • • •
consist of at least 10 and at most 32 characters consist of at least one lower [ a ..z] and one upper character [A..Z] plus a number [0..9] optionally contain special characters [!,@, #, $, %, ^, (, ), _, +, |, ~, {, }, [, ], -, .]
Step 8
Re-enter the new authentication password in the Retype key field.
Step 9
Enter the CO password in the Password field.
Step 10
Select OK to save your settings, or Cancel to cancel them.
End of Procedure
How to View the Key Exchange This instruction describes how to verify the key exchange by checking when the latest key exchange took place.
You must have successfully changed the CO password and specified the authentication password as described in How to Change the Crypto-Officer Password and How to Specify the Module Authentication Password.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the encryption module in the Entities pane. In response, all available information about the entity is displayed in the Parameter pane.
Step 3
Select the module’s network channel (for example CH-1-17-N OTU2P).
In response, all available information about the entitiy is displayed in the Parameter pane. Step 4
User Manual
Select the Monitoring tab.
127
Managing Encryption Modules
Step 5
Select Key exchange time from the Monitoring Type drop-down list. In response, the Parameter pane shows latest (Current) key exchange time.
End of Procedure
Configuring Maintenance Settings How to Change the Session-Key Lifetime How to Force a Key Exchange How to Reset the Key Exchange Fail Counter How to View the Key Exchange Fail Counter How to Update the Encryption Module Firmware How to Switch Off Encryption How to View the Encryption-Off Timer How to Switch On Encryption How to Configure a Network Interface Loopback
How to Change the Session-Key Lifetime Follow this instruction to change the session-key lifetime from its default value of “1-DAY”. The session-key lifetime indicates for how long a session key can still be used after an exchange of a newly generated session key has failed three times. This also includes the time that was required entering the wrong password three times before the key exchange failure.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
In response the encryption related parameters of the module are displayed.
Step 6
Select Modify. In response, the Modify window appears.
Step 7
Select the appropriate time from the Session key lifetime drop-down list.
Step 8
Enter the CO password in the Password field.
Step 9
Select OK to save your settings, or Cancel to cancel them.
End of Procedure
User Manual
129
Managing Encryption Modules
How to Force a Key Exchange This instruction describes how to manually initiate a key exchange to avoid a ten-minute timeout before a new session key is exchanged.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the encryption module in the Entities pane. In response, all available information about the entity is displayed in the Parameter pane.
Step 3
Select the module’s network channel (for example CH-1-17-N OTU2P).
Step 4
Set the administrative state (Admin State field) to Maintenance ( see “How to Change the Administrative State” on p. 260).
Step 5
Select the Crypto tab in the Parameter pane. In response the encryption related parameters of the module are displayed.
Step 6
From the Actions button, select Force Key Exchange. In response the Modify window appears.
130
Step 7
Select Key Exchange from the Force key exchange drop-down list.
Select the module’s network channel (for example CH-1-17-N OTU2P).
In response, all available information about the entitiy is displayed in the Parameter pane. Step 4
Select the Monitoring tab.
Step 5
Select Key exchange failed from the Monitoring Type drop-down list. In response, the Parameter pane shows how many times the key exchange has failed. The maximum value that can be observed is 3, because encryption stops after three failed key exchanges.
Updating the firmware of encryption modules is service affecting (SA). However, if this instruction is completed within 10 minutes, the module automatically reestablishes the encryption connection to the far-end module.
Firmware updates for encryption modules are distributed separately from NE software updates. They are made available through the Customer Portal at http://www.advaoptical.com/. Follow this instruction to update the firmware of an encryption module.
Requirement
User Manual
•
The network element (NE) on which the relevant encryption module resides has to run software release 10.3 or higher. If necessary, update the NE software as described in “Updating NE Software in a Network” on p. 423.
•
Changing security-related parameters on an encryption module always requires authentication by entering the CO password.
•
Ensure you are familiar with the requirements in “General Requirements” on p. 123.
133
Managing Encryption Modules
Procedure Step 1
Download the appropriate firmware package from the Customer Portal to a storage location that is addressable by the NE on which the relevant encryption module resides. This may be your management PC or an FTP/SCP server.
Step 2
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 3
Select the encryption module in the Entities pane. In response, all available information about the entity is displayed in the Parameter pane.
Step 4
Select the Crypto tab in the Parameter pane.
Step 5
Select the Modify button. In response the Modify window appears.
134
Step 6
Select Yes from the Allow FWP Update drop-down list.
Step 7
Enter the exact name of the firmware release (e.g. 1.9.3) to install in the Firmware Release field.
Step 8
Enter the CO password in the Password field.
Step 9
Select OK to save your settings, or Cancel to cancel them.
The Active Software Package and Standby Software Package sections displays which software package versions that are stored in the active and Standby Areas of the NE. Step 11
Select the Update Equipment Firmware (FWP) radio button, and then select Next to continue. In response, the Install Equipment Firmware (FWP) page appears.
Step 12
User Manual
Select Install Crypto FWP from External.
135
Managing Encryption Modules
Step 13
In response, the Install Crypto FWP from External window appears.
Step 14
Select which protocol to use when downloading the firmware to the target NE. Use the Protocol drop down list.
If you are not familiar with FTP or SCP, see “About FTP and SCP” on p. 459 for a brief overview. Step 15
During a file transfer, the NE's FTP or SCP client identifies itself with an IP address. In a bi-directional IP communication the two IP hosts involved need to be able to reach each other. Since both IP hosts identify each other by the IP addresses in the IP header of the IP packets, a successful IP communication relies on the availability of routes for these IP addresses in all the routers along the path between the IP hosts. Some network operators may configure their network in such a way that only the IP range in which the System IP addresses reside will be routed through their network. In this case it must be made sure that the FSP 3000R7 NE uses the System IP to identify itself as the source in the IP header of packets it is sending. If the network operator has configured his network to route the IP range in which the IP addresses of the physical IP interfaces reside, the default IP address as chosen by the IP stack can be used. Use the Own IP drop-down list to specify the IP address to use in the IP header as follows: • •
136
Select Default-IP if the IP address that the IP stack would choose by default should be used (this is the IP address of the interface through which the packet is sent). Select System IP if the system IP address should be used.
The options are FTP or SCP. SCP is a more secure protocol. If the SCP host is unknown, the transfer will fail. The user must therefore ensure that the known hosts table includes the SCP host.
Chapter 3 Provisioning NEs
Step 16
Enter the IP address of the SCP or FTP server where the firmware package is located, into the Server field. Ask IT personnel in your organization for this IP address if you do not know it.
Step 17
PS
Note
Step 18
Specify the location of the firmware pacakge on the external server by entering the relative path on the external server into the Path Name field. If the relative path has already been defined in the external server configuration, do not enter anything in the Path Name field. Otherwise, the download may fail. In the Login field, enter the user account name to gain access to the FTP/SCP server. It depends on the remote server whether the case of this entry as entered is taken into account before validation by the remote server.
Step 19
In the Password field, enter the password to gain access to the FTP/SCP server. It depends on the remote server whether the case of this entry as entered is taken into account before validation by the remote server.
Select OK to start the upload, or Cancel to discard your entries and return to the Backup/Restore window. Progress is displayed in the lower, left corner of the Backup/Restore window.
Step 21
Select the encryption module to update the firmware package for in the Select Equipment list. Ensure that the correct firmware revisions of the relevant encryption module are displayed: • •
User Manual
The FWP Rev. column displays the current module firmware revision. The NCU ACT FWP Rev. displays the revision that becomes active on the module when updated.
137
Managing Encryption Modules
Step 22
Select Next to continue. In response, the Update of equipment page appears.
Select Start Upgrade to start the update process, and select Yes in the confirmation window that appears.
PS
The update cannot be stopped.
Note
During the update, the Status field will display the status for each module. The following messages are used: • • • • • Step 24
Pending, which indicates that the process hasn’t started yet. Checking Status, which indicates that the Element Manager is
waiting for access to the update process on the NE. Updating which indicates that the Element Manager is checking if an NCU software update or FWP update is already ongoing. Finished, which indicates that the Element Manager update process successfully finished. However, the reboot of the modules may not yet be completed. Failed, which indicates that the process has failed and the FWP has not been updated.
Select Finish to close the Software Control window.
How to Switch Off Encryption This instruction describes how to switch off encryption for an encryption module. Switching off encryption involves enabling transparent mode for the module.
PS
Note
Switching off encryption is itself not service affecting (NSA). However, when encryption is switched on again, regardless of whether this is done manually or automatically after 30 minutes, the following generation and exchange of a new session key affects service (SA).
Only switch off encryption for: •
maintenance purposes, for example setting up network interface loopbacks
•
reconfiguring encryption modules
•
initially setting up an encryption link
If switched off, encryption will automatically be reestablished after 30 minutes, but you can manually restart it any time earlier.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane.
Select the encryption module in the Entities pane. In response, all available information about the entity is displayed in the Parameter pane.
Step 3
Select the module’s network channel (for example CH-1-17-N OTU2P).
In response, all available information about the entitiy is displayed in the Parameter pane. Step 4
Set the administrative state (Admin State field) to Maintenance ( see “How to Change the Administrative State” on p. 260).
Step 5
Select the Crypto tab in the Parameter pane. In response the encryption related parameters of the module are displayed.
User Manual
139
Managing Encryption Modules
Step 6
Select the Modify button. In response the Modify window appears.
Step 7
Select Yes from the Allow transparent mode drop-down list.
Step 8
Enter the CO password in the Password field.
Step 9
Select OK to save your settings, or Cancel to cancel them. In response, the Set transparent mode field becomes editable.
Step 10
Select the Modify button.
Step 11
Select Yes from the Set transparent mode drop-down list.
Step 12
Enter the CO password in the Password field.
Step 13
Select OK to save your settings, or Cancel to cancel them. If the Set transparent mode field displays Yes, encryption has successfully been switched off. Additionally, the N-port LED turns yellow indicating that traffic is not encrypted in transmission direction.
End of Procedure
How to View the Encryption-Off Timer This instruction describes how long time encryption has been switched off. When encryption is switched off, the module operates in transparent mode.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the encryption module in the Entities pane. In response, all available information about the entity is displayed in the Parameter pane.
Step 3
Select the module’s network channel (for example CH-1-17-N OTU2P).
In response, all available information about the entitiy is displayed in the Parameter pane.
Select Encryption off Time from the Monitoring Type drop-down list. In response, the Parameter pane shows the time in minutes that encryption has been switched off.
End of Procedure
How to Switch On Encryption This instruction describes how to manually encryption switch on. Switching off encryption involves disabling transparent mode for the module. This procedure is service affecting (SA): PS
Note
Having finished this procedure, it takes a few minutes until encryption has completely reestablished itself. This is because a new session key has to be generated. Traffic is interrupted during that time, as there is no transmission without key exchange.
Encryption was manually switched off (or transparent mode enabled) by the CO before.
•
Since encryption will be reestablished after 30 minutes, check how long encryption had been switched off already to ascertain whether it is necessary to follow this instruction (see “How to View the Encryption-Off Timer” on p. 140).
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the encryption module in the Entities pane. In response, all available information about the entity is displayed in the Parameter pane.
Step 3
Select the module’s network channel (for example CH-1-17-N OTU2P).
In response, all available information about the entitiy is displayed in the Parameter pane. Step 4
User Manual
Set the administrative state (Admin State field) to Maintenance ( see “How to Change the Administrative State” on p. 260).
141
Managing Encryption Modules
Step 5
Select the Crypto tab in the Parameter pane. In response the encryption related parameters of the module are displayed.
Step 6
Select the Modify button.
Step 7
Select No from the Set transparent mode drop-down list.
Step 8
Select No from the Allow transparent mode drop-down list.
Step 9
Enter the CO password in the Password field.
Step 10
Select OK to save your settings, or Cancel to cancel them.
Step 11
If relevant, verify the that the first key exchange has taken place as described in How to View the Key Exchange.
End of Procedure
How to Configure a Network Interface Loopback This instruction describes how to set facility or terminal loopbacks on the network interface for test purposes.
In response, all available information about the entitiy is displayed in the Parameter pane. Step 4
Set the administrative state (Admin State field) to Maintenance ( see “How to Change the Administrative State” on p. 260).
Step 5
Select the Operation tab.
Step 6
Select the Modify button.
Step 7
In reponse the Modify Operation window appears.
Step 8
Select the relevant loopback from the Loopback drop-down list: • ORP-FACILITY - A facility loopback is used to test the communication link between the near-end and far-end encryption module. That is, data received at the near-end network port is sent back to the far-end encryption module. • ORP-TERMINAL - A terminal loopback is to test the communication link between the near-end encryption module and the Customer Premises Equipment (CPE). That is, data multiplexed at the client ports is looped back at the network port. The laser of the network port is switched off. • RLS - To release a loopback.
Step 9
Select OK to save your settings, or Cancel to cancel them.
End of Procedure
Creating Protection Groups This section describes how to create protection groups. It assumes that the relevant channel modules and protection modules are already correctly provisioned. FSP 3000R7 supports three types of protection:
User Manual
•
channel protection
•
channel card protection
•
client channel card protection
•
virtual channel protection
•
versatile protection
143
Creating Protection Groups
In the following the procedures for configuring each of these protection groups are described. The following topics are provided: “How to Create a Channel Protection Group” on p. 144 “How to Create a Channel Card Protection Group” on p. 147 “How to Create a Client Channel Card Protection Group” on p. 152 “How to Create a Virtual Channel Protection Group” on p. 156 “How to Create an Ethernet Linear Protection Group” on p. 158 “How to Create a Versatile Protection Group” on p. 162 “How to Delete a Protection Group” on p. 164
How to Create a Channel Protection Group This section describes how to create a channel protection group or a channel card protection group in the internal database, using the Create window. Creating a protection group means associating two network side ports together in a group.
•
A channel module with two pluggable transceivers on the network side must already be provisioned using the correct transmission mode. It must be set to operate either in “Transponder HST” or “Multiplexer HST” mode. See “How to Create a Module” on p. 87.
•
The two network side pluggable transceivers must already be provisioned. The plugs may differ in provisioned channel, reach and rate, but they must both be provisioned to the same equipment type. See “How to Create a Plug” on p. 92.
•
Channels must already be provisioned on these two plugs. The facility type, ALS mode, error forwarding, and signal degrade threshold and hold-off period parameters must be provisioned alike on both channels. These parameters are not relevant for all facility types. See “How to Clone a Channel (Port)” on p. 96.
Procedure Step 1
If you are provisioning protection as a part of installation: a) Use the Service and Configuration documents in the Installation Plan to identify the location of the channel module that shall be used to realize protection of the channel. b) Make a note of the channel module type and its location.
If you are provisioning protection as a part of testing: a) If you are configuring a Network Element with equipment that is physically in place: • Identify the channel module type that can support this protection method. • Make a note of the location that contains such a channel module. b) If you are configuring a currently un-equipped Network Element: Make a note of the channel module type that can support the protection method.
Step 3
Select the relevant NE in the Entities pane.
Step 4
Verify that the channel module is provisioned in accordance with the requirements.
Step 5
If network side pluggables are supported: Verify that the two network side pluggable transceiver cages are already provisioned in accordance with the requirements.
Step 6
Verify that the two network side channels are already provisioned in accordance with the requirements.
Step 7
Select the channel module. Use the left hand hierarchical entity list in the Create window for this selection.
If the required entities have been provisioned already, the Create window will display the Create Protection Group list section on the right side. This is a list of AID addresses for the protection groups that can be created.
Step 8
Select the relevant protection group AID address from the list. The working path will be on the corresponding port/channel. In response the Create Protection Group wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
User Manual
145
Creating Protection Groups
Step 9
Enter parameters as follows, not all are applicable for all module types: a) Use the Working AID drop-down list to select which port/channel shall be used for the working path. b) Use the Protection AID drop-down list to select which port/channel shall be used for the protection path. c) The Protection Mechanism field displays protection mechanism for this protection group; Channel Protection.
e) Use the APS Hold-Off drop-down list to select the correct hold-off time to use. The hold-off is the period of time, in milliseconds, that initiation of an automatic protection switch will be delayed after a detected failure condition. The hold-off time coordinates timing of protection switches in cases with multiple layers or cascaded protection domains. f)
Use the Revertive drop-down list to specify whether the protection group shall be revertive or not. A revertive protection group will switch back to the working path once the condition that caused the protection switch has been cleared.
g) Use the Switch Trigger On SD drop-down list to enable or disable whether a signal degrade condition shall be regarded as a protection switching related failure. Your selection of protection level under Maintenance Switching decides which signal layer that signal degrade conditions are considered from. Step 10
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect and you used the Create Protection Group option: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response the Result window appears.
146
Step 11
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Result page.
Step 12
If you do not wish to continue provisioning: Select Finish.
d) Use the Maintenance Switching drop-down list to select the protection level. The options depend on the module type, the following are examples: • LINE/MSP: SDH/Sonet Multiplex Section/Line layer protection: • SNC-N-PM: Sub-network connection protection with non-intrusive monitoring (OTN) • PHYS: Physical layer protection • PCS: Physical Coding Sublayer protection • MUX: Proprietary multiplexed signal protection
Chapter 3 Provisioning NEs
Step 13
Check that the settings you made for the protection group are correct by right-clicking the channel module and selecting Protection from the context-sensitive menu that appears.
The protection group has been successfully created for the channels in this NE.
End of Procedure
How to Create a Channel Card Protection Group This section describes how to create a channel card protection group in the internal database, using the Create window. Creating a channel card protection group means associating two network side ports together in a group. Both manual creation of the channel group as well as assisted creation of the channel group is described. Assisted creation means that the Element Manager forcefully aligns the protection network channel with the working network channel at the same time as it creates the channel card protection group. The forceful alignment includes deletion of existing entities and creation of new ones. The extent of the forceful alignment is as follows: •
User Manual
All client entities provisioned on the working module will automatically be copied to the module defined as the protection module. If client entities exist on the protection module, and differ in protection relevant parameters from the ones of the working module, they will be aligned forcefully. Any already
147
Creating Protection Groups
provisioned client channel facility (e.g. ECC) on the protection module will not be aligned forcefully but will remain unaffected. •
All network entities provisioned on the working module will automatically be copied to the module defined as the protection module. If the network channel facilities require a forceful alignment and an already provisioned ECC would no longer be available, the ECC will be deleted.
Requirements Two channel modules in the same shelf, and of the same type, must already be provisioned. Channel card protection between normal and tunable variants is supported. For example between 10TCC10G-D and 10TCC10GT-D. The channel modules must be provisioned in accordance with: o
o
The channel module pair must have transmission modes Transponder, Transponder East, Transponder West, Multiplexer, Multiplexer East, or Multiplexer West. Deployment Scenario cannot be Back To Back or Client Layer Protection.
•
If the channel modules have a pluggable transceiver cage on the network side, these plugs must already be provisioned. The plugs may differ in provisioned channel, reach and rate, but they must both be provisioned to the same equipment type.
•
Network ports (channels) must already be provisioned on these two channel modules or plugs. They must be provisioned identically in order to support any APS mechanism and to support consistent switching triggers.
Procedure Step 1
Use the Service and Configuration documents in the Installation Plan to identify the location of the channel modules that shall be used to realize protection.
Step 2
Select the relevant NE in the Entities pane.
Step 3
Verify for the channel modules that they are provisioned in accordance with the requirements.
Step 4
If network side pluggables are supported: Verify that the network side pluggable transceiver cages on the two channel modules are already provisioned in accordance with the requirements. If you plan to use the option of creating a protection group where the protection path configuration is forcefully aligned with the working path, then you only need to ensure that the network plug of the working module is correctly configured.
Step 5
Verify that the two network side channels are already provisioned in accordance with the requirements. If you plan to use the option of creating a protection group where the protection path configuration is forcefully aligned with the working path, then you only need to ensure that the network channel of the working module is correctly configured.
Make a choice: • To create a protection group: Go to Step 7. This means that you must have manually aligned the parameters in Step 4 and Step 5. • To create a protection group and let the NE forcefully align the required parameters of the protection plug and protection network channel to those of the working plug and working network channel: Go to Step 9. During the process you will have the option of adjusting some parameters before the forced alignment.
Step 7
Select the working channel module. Use the left hand hierarchical entity list in the Provisioning Manager window for this selection.
If the required entities have been provisioned already, the Create window will display the Create Protection Group list section on the right side. This is a list of AID addresses for the protection groups that can be created.
Step 8
Select the relevant protection group AID address from the list. The working path will be on the corresponding port/channel. In response the Create Protection Group wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Continue from Step 10.
Step 9
Right-click the network channel that shall be the working path in the hierarchical list in the Entities pane, and select Force Protection Creation from the context sensitive menu that appears. In response the Force Protection Group wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
User Manual
149
Creating Protection Groups
Step 10
In the Parameters Step pages, enter values for the following parameters. Not all parameters are settable or supported by all channel module types. a) Use the Working AID drop-down list to select which port/channel shall be used for the working path. b) Use the Protection AID drop-down list to select which port/channel shall be used for the protection path. c) Use the Protection Mechanism drop-down list to select the relevant protection mechanism for the protection group. This parameter may not be settable for all channel module types.
e) Use the Revertive drop-down list to specify whether the protection group shall be revertive or not. Select Yes to set the revertive mode or select No to set the non-revertive mode. A revertive protection group will switch back to the working path once the condition that caused the protection switch has been cleared. f)
Use the Maintenance Switching drop-down list to select the protection level. The options depend on the module type, the following are examples: • LINE/MSP: SDH/Sonet Multiplex Section/Line layer protection • SNC-N-PM: Sub-network connection protection with non-intrusive monitoring (OTN) • PHYS: Physical layer protection • PCS: Physical Coding Sublayer protection • MUX: Proprietary multiplexed signal protection
g) Use the Switch Trigger On SD drop-down list to enable or disable whether a signal degrade condition shall be regarded as a protection switching related failure. Your selection of protection level under Maintenance Switching decides which signal layer that signal degrade conditions are considered from. h) Use the Directionally drop-down list to set the switching direction to uni- or bi-directional.
d) Use the APS Hold-Off drop-down list to select the correct hold-off time to use. The hold-off is the period of time, in milliseconds, that initiation of an automatic protection switch will be delayed after a detected failure condition. The hold-off time coordinates timing of protection switches in cases with multiple layers or cascaded protection domains.
Chapter 3 Provisioning NEs
Step 11
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. If you created the protection group using forced alignment: A warning window will appear to inform you that the forced alignment is service affecting and that all dependent entities will be removed. You must continue. Afterwards the Result window appears. Otherwise: The Result window appears.
Step 12
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Result page.
Step 13
If you do not wish to continue provisioning: Select Finish.
Step 14
Check that the settings you made for the protection group are correct by right-clicking the channel module and selecting Protection from the context-sensitive menu that appears.
The protection group has been successfully created for the channels in this NE.
End of Procedure
User Manual
151
Creating Protection Groups
How to Create a Client Channel Card Protection Group This section describes how to create a client channel card protection group in the internal database, using the Create window. Creating a client channel card protection group means associating two client side channels (same port number) together in a group. Both manual creation of the client channel group as well as assisted creation of the client channel group is described. Assisted creation means that the Element Manager forcefully aligns the protection client channel with the working client channel at the same time as it creates the channel card protection group. The forceful alignment includes deletion of existing entities and creation of new ones. The extent of the forceful alignment is as follows: •
The client entity on the working module will automatically be copied to the module defined as the protection module. If the same client entity on the protection module differs in protection relevant parameters from the ones of the working module, it will be aligned forcefully. Any other client entities will remain unaffected.
•
Two channel modules in the same shelf, and of the same type, must already be provisioned.The channel modules must be provisioned in accordance with: o
o o
The channel module pair must have the correct transmission modes, for example Multiplexer East and Multiplexer West. Hot standby modes are not allowed. Deployment Scenario cannot be Client Layer Protection. For some modules the correct module capability must be selected to allow client channel card protection. This is normally readable directly from the capability drop-down list. Otherwise the Compatibiltiy Matrix list the capabilities for each module.
•
If the channel modules have a pluggable transceiver cage on the client side: These plugs must already be provisioned, and provisioned alike since a protection switch is not allowed to change the signal in any way.
•
Client ports (channels) must already be provisioned on these two channel modules or plugs. They must be provisioned alike since a protection switch is not allowed to change the signal in any way.
•
Client channel protection can only be defined for alike ports, for example; between C1 and C1, or between C3 and C3.
Procedure
152
Step 1
Use the Service and Configuration documents in the Installation Plan to identify the location of the channel modules that shall be used to realize the client channel card protection group.
Verify that the channel modules are in place and provisioned in accordance with the requirements.:
Step 4
If client side pluggables are supported: Verify that the client side pluggable transceiver cages on the two channel modules are already provisioned according to the requirements. If you plan to use the option of creating a protection group where the protection path configuration is forcefully aligned with the working path, then you only need to ensure that the client plug of the working module is correctly configured and that the client plug on the protection module has been created on the correct port.
Step 5
Verify that the two client side channels are already provisioned according to the requirements.
If you to use the option of creating a protection group where the protection path configuration is forcefully aligned with the working path, then you only need to ensure that the client channel of the working module is correctly configured and that the client channel on the protection module has been created on the correct port. Step 6
Make a choice: To create a protection group: Go to Step 7.This means that you must have manually aligned the parameters in Step 4 and Step 5. • To create a protection group and let the NE forcefully align the required parameters of the protection client plug and protection channel to those of the working client plug and working channel: Go to Step 9. During the process you will have the option of adjusting some parameters before the forced alignment takes place.
Step 7
Select the working channel module. Use the left hand hierarchical entity list in the Provisioning Manager window (see “Creating Equipment/Facilities Manually” on p. 83) for this selection. If the required entities have been provisioned already, the Provisioning Manager window will display the Create Protection Group list section on the right side. This is a list of AID addresses for the protection groups that can be created.
User Manual
153
Creating Protection Groups
Step 8
Select the relevant protection group AID address from the list. The working path will be on the corresponding port/channel. In response the Create Protection Group wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Continue from Step 10.
Step 9
Right-click the client channel that shall be the working path in the hierarchical list in the Entities pane, and select Force Protection Creation from the context sensitive menu that appears. In response the Force Protection Group wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come.
Step 10
In the Parameters Step 1 page, enter the following values. Not all parameters are settable or supported for all channel module types: a) Use the Working AID drop-down list to select which port/channel shall be used for the working path.
c) The Protection Mechanism field shows the protection mechanism for this protection group, which is CLIENT CARD. d) The Maintenance Switching field shows the protection level, which is Multiplexer. This means that this is proprietary multiplexed signal protection. e) Use the APS Hold-Off drop-down list to select the correct hold-off time to use. The hold-off is the period of time, in milliseconds, that initiation of an automatic protection switch will be delayed after a detected failure condition. The hold-off time coordinates timing of protection switches in cases with multiple layers or cascaded protection domains. f)
154
Use the Revertive drop-down list to specify whether the protection group shall be revertive or not. A revertive protection group will switch back to the working path once the condition that caused the protection switch has been cleared.
b) Use the Protection AID drop-down list to select which port/channel shall be used for the protection path.
Chapter 3 Provisioning NEs
Step 11
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. If you created the protection group using forced alignment: A warning window will appear to inform you that the forced alignment is service affecting and that all dependent entities will be removed. You must continue. Afterwards the Result window appears. Otherwise: The Result window appears.
Step 12
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Result page.
Step 13
If you do not wish to continue provisioning: Select Finish.
Step 14
Check that the settings you made for the protection group are correct by right-clicking the channel module and selecting Protection from the context-sensitive menu that appears.
The protection group has been successfully created for this client channel, in this NE.
End of Procedure
User Manual
155
Creating Protection Groups
How to Create a Virtual Channel Protection Group This section describes how to create a virtual channel protection group in the internal database, using the Provisioning Manager window. Creating a virtual channel protection group means associating two network side virtual channels together, in a group.
•
A 4TCA-PCN-4GU+4G must already be provisioned to operate in ADM mode. See “How to Create a Module” on p. 87.
•
The two network side pluggable transceiver cages must already be provisioned. The plugs may differ in provisioned channel, reach and rate, but they must both be provisioned to the same equipment type. See “How to Create a Plug” on p. 92.
•
Network side ports (channels) must already be provisioned. The facility type, ALS mode, error forwarding, and signal degrade threshold and hold-off period parameters must be provisioned alike on both ports. See “How to Create a Port” on p. 93.
•
Virtual channels (VCHs) must already be provisioned on the two network ports. Both ports must be provisioned alike.
•
The client side pluggable transceiver cage must already be provisioned. See “How to Create a Plug” on p. 92.
•
A client side channel must already be provisioned on the client port. See “How to Create a Port” on p. 93.
•
Cross connects between the client channel and the east virtual channel, and between the client channel and the west virtual channel must already be provisioned. See “How to Create an ADM or ROADM Cross Connection” on p. 168.
Procedure Step 1
If you are provisioning protection as a part of installation: a) Use the Service and Configuration documents in the Installation Plan to identify the location of the channel module that shall be used to realize protection of the virtual channel. b) Make a note of the channel module type and its location.
Step 2
If you are provisioning protection as a part of testing: a) If you are configuring a Network Element with equipment that is physically in place: • Identify the channel module type that can support this protection method. • Make a note of the location that contains such a channel module. b) If you are configuring a currently un-equipped Network Element: Make a note of the channel module type that can support the protection method.
Requirements for creating a channel protection group
Chapter 3 Provisioning NEs
Step 3
Select the relevant NE in the Entities pane.
Step 4
Open the Provisioning Manager window, as described in “Creating Equipment/Facilities Manually” on p. 83.
Step 5
Select the channel module in the location you identified in step 1 or step 2. Use the left hand hierarchical entity list in the Provisioning Manager window for this selection. If the required entities have been provisioned already, the Provisioning Manager window will display the Create Protection Group list section on the right side. This is a list of AID addresses for the protection groups that can be created.
Step 6
Select the relevant protection group AID address from the list. The working path will be on the corresponding port/virtual channel.
In response the Create Protection Group wizard starts. Each page in the wizard has a title. The titles are: Parameters Step 1, Parameters Step 2, etc. The final page has the title Confirm. This helps you keep track of how far you have come. Step 7
In the Parameters Step 1 page, do as follows: a) Use the Protection Mechanism drop-down list to select path protection. b) Use the Working AID drop-down list to select which port/channel shall be used for the working path. c) Use the Protection AID drop-down list to select which port/channel shall be used for the protection path. d) Use the APS Hold-Off drop-down list to specify the hold off time before a protection switch takes place after the protection switching criteria are fulfilled.
Step 8
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete window appears.
Step 9
User Manual
Check that the protection group was successfully created See “How to view Single Protection Group Settings (Method A)” on p. 246.
157
Creating Protection Groups
Step 10
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 11
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 12
Close the Provisioning Manager window by selecting Close.
Step 13
If all other modules that are required to realize the channel that is protected are physically in place and provisioned: The channel is protected.
How to Create an Ethernet Linear Protection Group To configure Ethernet linear protection, follow the procedure describing this in the FSP 3000 Provisioning and Operations Manual.
Creating an Ethernet linear protection group means associating two flow points together in a group. This type of protection is only supported for the xPCA modules. This section describes how to create an Ethernet linear protection group in the internal database using the Flow Connections window.
Requirements for creating an Ethernet linear protection group •
The three Ethernet ports (ETHs) must already be configured, where the two ports holding the working and protection flow points must have role I-NNI. See “How to Create an Ethernet Port (ETH)” on p. 101.
•
The working and protection flow points must already be configured, and cross-connected to the flow point holding the service to protect. See “How to Create a Flow Point (FLW)” on p. 184 and “How to Create a Flow Cross Connection” on p. 196.
•
CFM maintenance flows for the working and protection paths must already be configured. See “Configuring Ethernet OAM/CFM” on p. 325.
Procedure
158
Step 1
Use the Service and Configuration documents in the Installation Plan to identify the location of the xPCA channel module that shall be used to realize protection of the Ethernet EVC. Make a note of the channel module type and its location.
This section supports the procedure in the FSP 3000 Provisioning and Operations Manual by giving more detailed guidance on using the Element Manager to create the Ethernet linear protection group. The procedure in this section should only be followed for additional support in conjunction with the procedure for configuring Ethernet linear protection in the FSP 3000 Provisioning and Operations Manual.
Chapter 3 Provisioning NEs
Step 3
Right-click the xPCA channel module in the location you identified in step 1, and select Flow Connections from the menu that appears. In response the Flow Connections window appears.
In response the Flow Connections window content changes.
User Manual
159
Creating Protection Groups
Step 5
Select Create to start the Create Ethernet Linear Protection wizard. In response the Create Protection Group wizard starts.
Each page in the wizard has a title. This helps you keep track of how far you have come. In the Ethernet Linear Protection entities to create page do as follows: a) Select the Ethernet linear protection group entity (FFP) that represents the working path. The Ethernet linear protection group entities that are possible to create are displayed using the syntax FFP_FLW_---F. Thus for the same SVID there are two possible protection group entities (FFPs), where the difference is the port. However, once you select one of them, the other cannot be created. b) Select Next to continue. In response the Working and Protection page appears.
In the Working and Protection page, do as follows: a) Ensure that the displayed working flow point AID is correct. b) Select Next to continue. In response the Parameters Step 1 page appears.
Step 8
In the Parameters Step 1 page, do as follows: a) The CFM maintenance flows which monitor the working and protection paths are associated with a Maintenance Domain. Use the Monitored Domain Level drop-down list to select the level that this Maintenance Domain has.
b) Select Next to continue. In response the Confirm page appears.
Step 9
In the Confirm page do as follows: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Result page appears.
User Manual
Step 10
Check that the protection group was successfully created See “How to view Single Protection Group Settings (Method A)” on p. 246.
Step 11
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Result page.
161
Creating Protection Groups
Step 12
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Flow Connections window.
Step 13
Close the Flow Connections window by selecting Close.
Step 14
If the working and protection flow points have been correctly cross-connected to the flow point to protect.: The Ethernet E-Line EVC is protected.
End of Procedure
How to Create a Versatile Protection Group This procedure describes how to create a versatile protection group for a channel group or a line.
•
A VSM and 2OSCM or OSCM-P module must already be provisioned. See “How to Create a Module” on p. 87.
•
Two network side ports (channels) must already be provisioned on this channel module. See “How to Create a Port” on p. 93.
Procedure Step 1
If you are provisioning protection as a part of installation: a) Use the Service and Configuration documents in the Installation Plan to identify the location of the VSM module that shall be used. b) Make a note of the module’s location.
162
Step 2
If you are provisioning protection as a part of testing: • If you are configuring a Network Element with equipment that is physically in place: Identify the VSM module and make a note of its location.
Step 3
Select the relevant NE in the Entities pane.
Step 4
Open the Provisioning Manager window, as described in “Creating Equipment/Facilities Manually” on p. 83.
Select the VCM in the location you identified in step 1 or step 2. Use the left hand hierarchical entity list in the Provisioning Manager window for this selection. If the required entities have been provisioned, the Provisioning Manager window will display the Create Protection Group list section on the right side.
Step 6
Provision the protection group as described in “How to Create a Channel Protection Group” on p. 144 or “How to Create a Channel Card Protection Group” on p. 147.
Step 7
If all other modules that are required to realize the protection are physically in place and provisioned: The protection is active.
How to Delete a Protection Group This instruction describes how to delete a protection group using the Protection window.
Procedure Step 1
Select the relevant channel module that is used in a protection group.
Step 2
Either right-click the module and select Protection from the context sensitive menu that appears, or select Configuration->Protection from the Main Menu.
Step 3
Select the correct protection group, using the Protection Group drop-down list. This list contains the FFP-CH entities, and there is one entity for each end channel in the protection group. For example, FFP-CH-1-18-NE1 and FFP-CH-1-18-NW1 can be defined to be in a protection group. You can select either of these two here, meaning that the information about that protection group can be viewed by selecting either of the two FFP entities.
Step 4
Select the Delete button. Both FFP-CH entities that are part of the protection group will be deleted.
“How to View ADM and ROADM Cross Connections” on p. 166 “How to Create an ADM or ROADM Cross Connection” on p. 168 “How to Create a 1 Way ADM or ROADM Cross Connect Primitive” on p. 175 “How to Enable a ROADM Cross-connection” on p. 179 “How to Delete a Bi-directional ADM or ROADM Cross Connection” on p. 180 “How to Delete 1 Way ADM or ROADM Cross Connect Primitives” on p. 181
User Manual
165
Creating ADM and ROADM Cross Connections
How to View ADM and ROADM Cross Connections This section describes how to view ADM and ROADM cross connections. This can be done only for the whole NE, not individually per module.
Procedure Step 1
From the Configuration menu, select Cross Connections.
The following information is provided in this window: Column Name
Description
From/To
These columns displays the AID for the channel (CH) or the virtual channel bundle (VCH) where the cross connect starts from, and ends. The double arrow indicates a bi-directional cross connection, while a single arrow indicates a unidirectional cross connection as well as the direction of it. When the symbol is red, this indicates that the cross connections’s state is Disabled, while green indicates that it is In Service. For the 4TCA-PC-4GU+4G-V, there is no state, and the color is always green. This column displays Bi to indicate that the cross connection is bi-directional. This column displays which facility type that uses this cross connections.
This column displays Add/Drop or Pass thru to indicate whether the cross connection is used for adding/dropping traffic, or for passing it through the NE. This column shows the joint administrative state of the from/to entities. If one or both of the entities is Disabled, this column displays Disabled. If both are In Service, In Service is shown here. The state column is not applicable to cross-connections on the 4TCA-PC-4GU+4G-V module.If both are Disabled, Disabled is shown here.
Customize the information that is displayed in the Cross Connections window: • Use the Equipment drop down list to specify which equipment to display cross-connections for in the window. • Sort the table based on a column, by clicking the column title. This toggles between ascending and descending display. •
Adjust the column widths to match the content by clicking the icon and selecting Pack All Columns or Pack Selected Column from the list that appears.
•
Turn off display of a column by clicking the icon and selecting the column name from the list that appears. A check mark indicates that the column will be displayed.
•
Turn on display of a horizontal scroll bar by clicking the icon and selecting Horizontal Scroll from the list that appears. A check mark indicates that the horizontal scroll bar will be displayed.
If the symbol is displayed when you expected the symbol: You have not created the return direction for the cross connect yet. Create it as follows: a) Double-click the entry. In response, the Cross Connection Details window appears. b) In the Cross Connection Details window, find the Create button. You can see which channel (CH) and Virtual channel bundle (VSH) that form the missing 1 way cross connect primitive. c) Select the Create button. In response, the Create Cross Connection wizard appears. d) Follow the instructions in the Create Cross Connection wizard to finish the creation of the missing 1 way cross connect primitive. Upon completion, you will be returned to the Cross Connection Details window. e) Select Close to return to the Cross Connections window.
User Manual
167
Creating ADM and ROADM Cross Connections
Step 4
If appropriate you can: • Select Print to print the Cross Connections list. • Select Save to save the Cross Connections list as a comma separated file. • Select Refresh to update the content of the window.
Step 5
Select Close to finish viewing the cross connections.
End of Procedure
How to Create an ADM or ROADM Cross Connection This section describes how to create an ADM or ROADM cross connection. A cross connection consists of one or two 1 way cross connect primitives, where a bi-directional cross-connection requires two 1 way cross-connect primitives. These primitives must be created individually, and the Create Cross Connection wizard supports the user in doing this easily.
In response the From Port list displays all channels (CHs) and virtual channel bundles (VCHs) on the module or on the NE that can be cross connected. Step 4
Identify the CH or VCH facilities that shall be used to form the 1 way cross connect primitive of the cross connection. If you cannot see the CH or VCH facility that you need: It has not been created yet, and you must create it before returning to this step again. See “How to Create a Port” on p. 93 or “How to Create a Virtual Channel” on p. 100 for guidance on creating CHs and VCHs.
User Manual
169
Creating ADM and ROADM Cross Connections
Step 5
Specify the1 way cross connect primitive of the cross connection. Do as follows: a) Select the CH or VCH facility from which the cross connection shall start. This will have impact on the direction of the 1 way cross connect primitive. b) Select Next to continue. In response, the To Port page appears.
d) Select Next to continue. In response, the Parameters Step 1 page appears.
e) Specify whether the cross connection shall be bi-directional or uni-directional by using the Direction drop-down list. f)
For a ROADM cross connection: Use the Path Node drop-down list to specify which number this node is in the sequence of nodes that the optical pathway (channel) traverses. The nodes are counted from client signal ingress to egress. This parameter is required to allow scheduled equalization on the channel. A service can be added in one node, passed through in the next and dropped in the third. This example involves three nodes.
g) For a ROADM cross connection: Use the Facility Type drop-down list to specify which facility type that will be transported through the optical pathway (channel) this cross-connection represents.
c) From the To Port, select the CH or VCH facility from which the cross connection shall start.
Chapter 3 Provisioning NEs
Step 6
Select Next to continue. In response, the Confirm page appears.
Step 7
Check the displayed information about the first 1 way cross connect primitive. If this does not look correct: Select Back to make corrections, or Cancel to close the Create Cross Connection wizard and return to the Cross Connections window. If this does look correct: Confirm by selecting Next.
If this is meant to be a bi-directional cross connection: Select OK and the wizard will create the reverse direction for you. Otherwise: Select Cancel. In both case the Result page appears.
Step 9
User Manual
Select Finish to return to the Cross Connections window.
171
Creating ADM and ROADM Cross Connections
Step 10
If relevant: Add an alias/comment to the 1 way cross connect primitive. Do as follows: a) In the Cross Connections window, select the cross connection you just created. b) Select the Details button. In response, the Cross Connection Details window appears.
d) Select Close to return to the Cross Connections window.
c) select the Modify button and enter an alias/comment.
Chapter 3 Provisioning NEs
Step 11
If this is a ROADM cross-connect primitive: Edit the settings for the cross-connections as relevant. Do as follows: a) Select the cross connection you just created.
b) Select the Details button. In response, the Cross Connection Details window appears.
c) For the 1 way cross connect primitive, select the Modify button. d) If the control plane is in use: The Tunnel AID field will show which tunnel that this cross-connection is associated with. Do not edit this field, the control plane controls this field when applicable. The Red Lined State indicates whether a cross-connection is allowed to be deleted or not. If required, change the Red Lined State setting. • Yes indicates that you are not allowed to delete the connection. This is typically the case if the control plane is in use, in which case the control plane deletes the connection as required. In this case: do not change this setting. You could also set the red lined state to Yes without the control plane being in use. This would help prevent accidentally deleting a cross-connection. • No indicates that you are allowed to delete the connection. e) If relevant: Modify the Path Node and Facility Type. f)
User Manual
If relevant at this time: enable the cross-connection so traffic can flow when applied. Set the Admin State to In Service. • If the network ports are not physically connected in a system with ROADM-C40/40/2-3HU-2DC shelves, traffic cannot flow through the pass-through cross connection. • To enable equalization to occur when 8ROADM-C40/0/OPM and ROADM-C80/0/OPM module cross-connections are enabled, two conditions must be met before placing the cross-connection in service. Pass-through channels must be
173
Creating ADM and ROADM Cross Connections
present at the receive network interface, and all devices between the network interface and the 8ROADM-C40/0/OPM or ROADM-C80/0/OPM module should be placed In Service and have the power levels adjusted. g) Select OK to apply the changes or Cancel to cancel them. h) Select Close to return to the Cross Connections window. Step 12
If the cross connection you just defined the 1 way cross connect primitive for is bi-directional: a) You can now complete the bi-directional cross connection creation, by creating the reverse direction 1 way cross connect primitive as described from Step 13. b) If you wish to create the second 1 way cross connect primitive of the cross connection, the reverse direction, at a later time: Go to Step 19.
Step 13
Create the second 1 way cross connect primitive of the cross connection by selecting the Create Reverse Direction link. This primitive is for the reverse direction.
Step 14
Since this is the second 1 way cross connect primitive of a bi-directional cross connection, the Direction drop-down list already is set to Bi. Select Next to continue. In response, the Confirm window appears.
Step 15
Check the displayed information about the second 1 way cross connect primitive, as described in Step 7. In response, the Result page appears.
Step 16
174
Close the Create Cross Connection wizard by selecting Finish.
If relevant: Add an alias/comment to the second 1 way cross connect primitive of the cross connection you created. Do as described in Step 10.
If this is a ROADM cross-connect primitive: Edit the settings for the cross-connections as described in Step 11. Step 18
Go to Step 20
Step 19
Select Finish to close the Create Cross Connection wizard and return to the Cross Connections window. A bi-directional cross connection will not be functional until both 1 way cross connect primitives have been created.
Step 20
Close the Cross Connections window.
End of Procedure
How to Create a 1 Way ADM or ROADM Cross Connect Primitive This instruction describes how to create a single 1 way ADM or ROADM cross connect primitive that forms the return path of a bi-directional cross connection. If you during the creation of the bi-directional cross connection chose to not immediately create the second 1 way cross connect primitive, follow this procedure to create the second 1 way cross connect primitive now.
Procedure Step 1
From the Configuration menu, select Cross Connections. In response the Cross Connections window appears.
User Manual
175
Creating ADM and ROADM Cross Connections
Step 2
From the cross connections list, select the bi-directional cross connection that consists of only 1 way cross connect primitive.
Step 3
Select Details.
Step 4
In the 1 WAY Cross Connection Primitives section, identify the 1 way cross connect primitive that needs to be created, and select the belonging Create button. In response, the Parameters Step 1 page appears.
Step 5
Since this is the second 1 way cross connect primitive of a bi-directional cross connection, the Direction drop-down list already is set to Bi. Select Next to continue. In response, the Confirm window appears.
Step 6
Check the displayed information about the new 1 way cross connect primitive. If this does not look correct: Select Back to make corrections, or Cancel to close the Create Cross Connection wizard and return to the Cross Connections window. If this does look correct: Confirm by selecting Next. In response, the Result page appears.
Step 7
176
Close the Create Cross Connection wizard by selecting Finish.
In response, the Cross Connection Details window appears.
Chapter 3 Provisioning NEs
Step 8
If relevant: Add an alias/comment to the 1 way cross connect primitive. Do as follows: a) Select the cross connection you just created. b) Select the Details button.
c) In response, the Cross Connection Details window appears.
d) For each 1 way cross connect primitive, select the Modify button and enter an alias/comment. e) Select Close to return to the Cross Connections window.
User Manual
177
Creating ADM and ROADM Cross Connections
Step 9
If this is a ROADM cross-connect primitive: Edit the settings for the cross-connections as relevant. Do as follows: a) Select the cross connection you just created. b) Select the Details button.
d) For the first 1 way cross connect primitive, select the Modify button. e) If relevant, enter an alias/comment. f)
If the control plane is in use: The Tunnel AID field will show which tunnel that this cross-connection is associated with. Do not edit this field, the control plane controls this field when applicable.
g) The Red Lined State indicates whether a cross-connection is allowed to be deleted or not. If required, change the Red Lined State setting. • Yes indicates that you are not allowed to delete the connection. This is typically the case if the control plane is in use, in which case the control plane deletes the connection as required. In this case: do not change this setting. You could also set the red lined state to Yes without the control plane being in use. This would help prevent accidentally deleting a cross-connection. • No indicates that you are allowed to delete the connection. h) If relevant at this time: enable the cross-connection so traffic can flow when applied. Set the Admin State to In Service. • If the network ports are not physically connected in a system with ROADM-C40/40/2-3HU-2DC shelves, traffic cannot flow through the pass-through cross connection. • To enable equalization to occur when 8ROADM-C40/0/OPM and ROADM-C80/0/OPM module cross-connections are enabled, two conditions must be met before placing the
c) In response, the Cross Connection Details window appears.
Chapter 3 Provisioning NEs
cross-connection in service. Pass-through channels must be present at the receive network interface, and all devices between the network interface and the 8ROADM-C40/0/OPM or ROADM-C80/0/OPM module should be placed In Service and have the power levels adjusted.
Step 10
i)
For the second 1 way cross connect primitive, select the Modify button and follow point Step e through Step h
j)
Select Close to return to the Cross Connections window.
Close the Cross Connections window.
End of Procedure
How to Enable a ROADM Cross-connection ROADM cross-connections must be enabled before the cross-connection will let traffic flow through it. This is done by setting the administrative state for the cross-connection to In Service. Disabling the cross-connection is achieved by setting the administrative state to anything but In Service.
If the network ports are not physically connected in a system with ROADM-C40/40/2-3HU-2DC shelves, traffic cannot flow through the pass-through cross connection. To enable equalization to occur when 8ROADM-C40/0/OPM and ROADM-C80/0/OPM module cross-connections are enabled, two conditions must be met before placing the cross-connection in service. Pass-through channels must be present at the receive network interface, and all devices between the network interface and the 8ROADM-C40/0/OPM or ROADM-C80/0/OPM module should be placed In Service and have the power levels adjusted.
Procedure Step 1
From the Configuration menu, select Cross Connections. In response the Cross Connections window appears.
Step 2
User Manual
From the cross connections list, select the cross connection to enable.
179
Creating ADM and ROADM Cross Connections
Step 3
Select Details.
Step 4
For the first 1 way cross connect primitive, select the Modify button.
Step 5
Set the Admin State to In Service.
Step 6
If there is a second 1 way cross connect primitive: Repeat Step 4 and Step 5 for the second 1 way cross connect primitive.
Step 7
Select Close to return to the Cross Connections window.
Step 8
Close the Cross Connections window.
End of Procedure
How to Delete a Bi-directional ADM or ROADM Cross Connection This instruction describes how to delete both 1 way cross connect primitives in a bi-directional ADM or ROADM cross connection at one time.
Requirements
180
•
ROADM cross-connect primitives can only be deleted if their Red Lined State is No, and their administrative state is not In Service.
•
All other cross-connections can be deleted at any time and deletion can thus interrupt traffic. Ensure that traffic is not running by checking that the entities that are being cross-connected do not have administrative state In Service.
In response, the Cross Connection Details window appears.
Chapter 3 Provisioning NEs
Procedure Step 1
From the Configuration menu, select Cross Connections. In response the Cross Connections window appears.
Step 2
From the cross connections list, select the cross connection to delete.
Step 3
Select from the following: • If this is a ADM cross-connection: Go to Step 8 • If this is a ROADM cross-connection: Go to Step 4
Step 4
Select Details. In response, the Cross Connection Details window appears.
Step 5
Ensure that the administrative state is not In Service. If it is necessary to change the administrative state, use the Modify button.
Step 6
Ensure that Red Lined State is set to No. The Red Lined State indicates whether a cross-connection is allowed to be deleted or not. Yes indicates that you are not allowed to delete the connection, while No indicates that you can delete the connection.
Step 7
Select Close to return to the Cross Connections window.
Select OK to proceed with the deletion. Progress is shown in the lower, left corner of the Cross Connections window.
End of Procedure
How to Delete 1 Way ADM or ROADM Cross Connect Primitives This instruction describes how to delete a single 1 way ADM or ROADM cross connect primitive. Deleting both 1 way cross connect primitives in a cross connection gives the same result as in “How to Delete a Bi-directional ADM or ROADM Cross Connection” on p. 180.
Requirements
User Manual
•
ROADM cross-connect primitives can only be deleted if their Red Lined State is No, and their administrative state is not In Service.
•
All other cross-connections can be deleted at any time and deletion can thus interrupt traffic. Ensure that traffic is not running by checking that the
181
Creating ADM and ROADM Cross Connections
entities that are being cross-connected do not have administrative state In Service.
Procedure Step 1
From the Configuration menu, select Cross Connections. In response the Cross Connections window appears.
Step 2
From the cross connections list, select the cross connection that consists of the 1 way cross connect primitive.
Step 3
Select Details.
Step 4
If you wish to delete one 1 way cross connect primitive: Go to Step 7.
Step 5
If you wish to delete two 1 way cross connect primitives: a) Select the Delete Both button. b) In response a warning window appears.
c) Confirm the deletion by selecting OK, or cancel it by selecting Cancel. d) Go to Step 10. Step 6
182
In the 1 WAY Cross Connection Primitives section, identify the 1 way cross connect primitive that you want to delete.
In response, the Cross Connection Details window appears.
Chapter 3 Provisioning NEs
Step 7
If this is a ROADM cross-connection: a) Ensure that the administrative state is not In Service. If it is necessary to change the administrative state, use the Modify button. b) Ensure that Red Lined State is set to No. c) The Red Lined State indicates whether a cross-connection is allowed to be deleted or not. Yes indicates that you are not allowed to delete the connection, while No indicates that you can delete the connection.
Step 8
Select the Delete button that belongs to the cross-connect primitive to delete. In response, a warning window appears.
Step 9
Confirm the deletion by selecting OK, or cancel it by selecting Cancel.
You are returned to the Cross Connection Details window. Step 10
If you want to delete, create or modify 1 way cross connect primitives in other cross connections: Use the Previous or Next buttons to reach the relevant cross connections and follow instructions in the relevant procedures in the “Creating DCN Cross-Connections” on p. 208.
Step 11
Close the Cross Connection Details window when you are finished.
End of Procedure
Creating Flow Points, Bridges, and Cross Connections This section describes how to create Ethernet layer 2 flow points, bridges, and flow cross-connections, and how to keep an overview of the flow points and flow cross-connections on an individual NE. It assumes that the relevant modules are already correctly provisioned. Flow points and flow cross-connections are supported by xPCA channel modules. Each cross connection is built up from one or two 1 way cross connect primitives. A bi-directional cross connection is built up from two 1 way cross connect primitives. Each primitive must be created individually, and the Create Flow Cross Connection wizard supports the user in doing this easily. The following topics are provided: “How to Create a Flow Point (FLW)” on p. 184 “How to View Flow Points” on p. 189
User Manual
183
Creating Flow Points, Bridges, and Cross Connections
“How to Create a Bridge (BRG)” on p. 191 “How to View Bridges” on p. 194 “How to Create a Flow Cross Connection” on p. 196 “How to Delete a Bi-directional Flow Cross Connection” on p. 201 “How to Delete 1 Way Flow Cross Connect Primitives” on p. 203 “How to View Flow Cross-connections” on p. 206
How to Create a Flow Point (FLW) This procedure describes how to create a flow-point on an xPCA Ethernet port (ETH entity) or an xPCA virtual Ethernet port (VETH entity), using the Provisioning Manager window. A flow point holds the shaping and policing properties for an Ethernet flow (EVC) on an xPCA channel module. After creation, the flow point is selectable as the AID FLW---<{C{1..10}||NE|NW}-{F{1..400}>-from the Flow Connections window.
The port’s ETH or VETH entity must already be provisioned correctly and the administrative state is Automatic In Service or In Service.
Procedure Step 1
From the Main Menu, select Configuration -> Flow Connections. In response, the Flow Connections window opens.
In response the Create Flow Point window content changes.
Step 5
Enter a Service VLAN Identifier (SVID) value to identify the flow point at the selected port. Avoid using SVID=4095 as this SVID value is normally used for ECC within ADVA Optical Networking networks. The SVID value is used later when cross-connecting ports.
User Manual
185
Creating Flow Points, Bridges, and Cross Connections
Step 6
Use the Port drop-down list to select the AID of the port you are defining a flow point for. • If you are creating a flow point on an Ethernet port, this is an ETH entity. • If you are creating a flow point on a virtual Ethernet port (LAG group), this is a VETH entity. If only one ETH or VETH entity exists, this will be auto-selected. Select Next to continue.
The contents of the next “pages” in the Create Flow Point window depend on which port mode the port was provisioned to operate in: • For all port modes, configure the parameters shown inTable 5. • For port mode CTAG, configure in addition the parameters shown inTable 6. • For port mode STAG, configure in addition the parameters shown inTable 7. Use Next to continue to each new page.
Table 5:
Flow Point Parameters for all Port modes
Parameter
Definition
CIR-RCV
Enter the Committed Information Rate used by the policer at Rx for this flow point1. If both CIR-RCV and CBS-RCV are set to zero, no traffic will be forwarded from the flow point. If the maximum frame length is configured to 0-15% less than the CBS-RCV value, the policer will become less accurate and let through 2-10% too high bit rate. To resolve this situation, configure CBS-RCV to the next higher value. Enter the Committed Burst Size used by the policer at Rx for this flow point Enter the Committed Information Rate used by the shaper at Rx for this flow point1. To stop forwarding of all traffic from the flow point, both CIR-TRMT and CBS-TRMT must be set to zero Enter the Committed Burst Size used by the shaper at Tx for this flow point.
Police Enablement Red Lined State3 Tunnel AID3 Admin State
Enable/disable the shaper2 at Tx for this flow point.. The default CoS used by this flow point. In this release only PCP=7 is supported. Enable/disable performance monitoring on this flow point. The system supports performance monitoring on up to 100 flow points, bridges, or a mix of flow points and bridges per xPCA module. Enable/disable policer at Rx for this flow point Do not change the value of the Red Lined State. It is used by the Control Plane, if the Control Plane has been enabled. Do not change the value of the Tunnel AID. It is used by the Control Plane, if the Control Plane has been enabled Enter the Admin State, typically Automatic In Service or In Service.
1. The measured rate can be up to 1.5% higher than the value you enter here. 2. xPCA modules do not support individually configurable shapers at Tx for E-LAN member ports. For E-LAN services shaping is defined by the bridge entity.Therefore the flow point creation wizard for E-LAN flow points do not offer configuration of a shaper.
User Manual
187
Creating Flow Points, Bridges, and Cross Connections
3. This parameter is only supported for flow points with facility type E-Line.
Table 6:
Flow Point Parameters for Port mode CTAG
Parameter
Definition
CVIDs registered
Enter the list of the CVID flows that shall be mapped into the SVID flow. If you have configured acceptance of untagged frames, any CVID you entered in the Port VLAN ID field must be included in the CVIDs registered list A C-tag can be added to untagged frames at Tx and/or at Rx. Configuration of C-tag addition at Rx is done on the ETH entity (the Port default PCP and Port VLAN ID field). Prio PVID Transmit Enter the PCP priority for the C-tag that is added to untagged frames at Rx. PUSH PVID Enter the CVID of the C-tag that is added to untagged frames at Rx Transmit1
1. This is in IEEE Provider Bridge known as PEP Port Default VID (PVID). Table 7:
Flow Point Parameters for Port mode STAG
Parameter
Definition
External VID
If the SVID to be used externally on this SVID flow is different than the entry in Step 5, then enter that external VID. This is applicable at both Tx and Rx. When these SVIDs are different an SVID translation will occur. Avoid using SVID=4095 as this SVID value is normally used for ECC within ADVA Optical Networking networks. External VID is in IEEE referred to as “local VID”.
Step 8
Select Next to continue. In response the Confirm wizard page appears.
Step 9
Check that the displayed settings are correct. • If the settings are incorrect: Select Back to go back and correct the settings. • If the settings are correct: Select Next to confirm. In response, the Complete page appears.
Step 10
188
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
The C-tag can be removed from frames at Tx and at Rx. POP CTAG receive Enter the CVID of the C-tag which shall be removed at Rx POP CTAG transmit Enter the CVID of the C-tag which shall be removed at Tx
Chapter 3 Provisioning NEs
Step 11
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 12
Close the Provisioning Manager window by selecting Close.
End of Procedure
How to View Flow Points This section describes how to view flow points. This can be done only for the whole NE, not individually per module.
From the Configuration menu, select Flow Connections.
Step 2
Select the Flow Points tab.
Step 3
Use the Equipment drop-down list to select which modules to display flow points for.
Step 4
Make a decision about how to filter your view: • To view flow points by port, go to Step 5. • To view flow points by SVID, go to Step 7.
Step 5
Display flow points per port by doing as follows: • Select Flow Points by Port in the View Mode drop-down list. • Use the Port drop-down list to select which ports to display flow points for. • Use the Port Role drop-down list to select which ports to display flow points for based on the port roles. • Use the Connections State drop-down list to select which flow points to display based on the connection’s (EVC’s) state.
Step 6
Go to Step 9.
Step 7
Display flow points per SVID by doing as follows: • Select Flow Points by SVID in the View Mode drop-down list. • Use the SVID From-To fields to enter the range of SVIDs to display. • Use the Connections State drop-down list to select which flow points to display based on the connection’s (EVC’s) state.
Step 8
Go to Step 9.
189
Creating Flow Points, Bridges, and Cross Connections
Step 9
In response the Flow Connections window is updated.
Column Name
Description
AID SVID EVC Type Admin State
This column displays the AID for the flow point. This column displays the SVID for the flow point. This column displays the service type of the EVC. This column displays the Admin State of the flow point. This column displays the state of the connection (EVC). The connection is in Idle state before it has been cross-connected. Busy indicates that it is used in a cross-connection. This column displays the CVIDs that have been registered to this EVC. This column displays which port role the port that the flow is defined on has. This column shows the flow point’s alias, if any has been entered.
The following information is provided in the table in this window:
Chapter 3 Provisioning NEs
Step 10
Customize the information that is displayed in the table: • Sort the table based on a column, by clicking the column title. This toggles between ascending and descending display. •
Adjust the column widths to match the content by clicking the icon and selecting Pack All Columns or Pack Selected Column from the list that appears.
•
Turn off display of a column by clicking the icon and selecting the column name from the list that appears. A check mark indicates that the column will be displayed.
•
Turn on display of a horizontal scroll bar by clicking the icon and selecting Horizontal Scroll from the list that appears. A check mark indicates that the horizontal scroll bar will be displayed.
Step 11
If appropriate you can: • Select Print to print the Flow Point list. • Select Save to save the Flow Point list as a comma separated file. • Select Refresh to update the content of the window.
How to Create a Bridge (BRG) This instruction describes how to create a bridge on an xPCA Ethernet module , using the Provisioning Manager window. A bridge contains the shaping properties for the EVC flow segment on an xPCA channel module. After creation, the bridge point is selectable as the AID BRG---<{C{1..10}||NE|NW}-{F{1..400}>-from the Flow Connections window.
User Manual
191
Creating Flow Points, Bridges, and Cross Connections
Requirements The xPCA channel module has been provisioned and the administrative state is Automatic In Service or In Service.
Procedure Step 1
From the Main Menu, select Configuration -> Flow Connections.
Use the Equipment drop-down list to select which xPCA module to add a bridge to. Select Next to continue. In response the Create Bridge window content changes.
Step 5
Enter the internal Service VLAN Identifier (SVID) value it shall be identical to the flow number of the bridge. Avoid using SVID=4095 as this SVID value is the default value for ECC. The SVID value is used later when cross-connecting ports. Select Next to continue.
Configure the parameters shown in Table 8. Use Next to continue to each new page as needed.
Table 8: Parameter
Definition
CIR-TRMT
Enter the Committed Information Rate used by the shaper at Rx for this port1. To stop forwarding of all traffic to all bridge ports, both CIR-TRMT and CBS-TRMT must be set to zero Enter the Committed Burst Size used by the shaper at Tx for this port.
CBS-TRMT
User Manual
Bridge Parameters for all Port modes
193
Creating Flow Points, Bridges, and Cross Connections
Table 8:
Bridge Parameters for all Port modes
Parameter
Definition
Facility Type
No entry is required. The field shows the facility type of the bridge. Shaping is enabled by default, no action is required. Enable/disable performance monitoring for the queue entity that belongs to the bridge. The system supports performance monitoring on up to 100 flow points, bridges, or a mix of flow points and bridges per xPCA module. Enter the Admin State, typically Automatic In Service or In Service.
Shape Enablement PM mode
Admin State
1. The measured rate can be up to 1.5% higher than the value you enter here.
Step 7
Select Next to continue. In response the Confirm wizard page appears.
Step 8
Check that the displayed settings are correct. • If the settings are incorrect: Select Back to go back and correct the settings. • If the settings are correct: Select Next to confirm.
Step 9
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 10
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 11
Close the Provisioning Manager window by selecting Close.
End of Procedure
How to View Bridges This section describes how to view bridges. This can be done only for the whole NE, not individually per module.
Procedure
194
Step 1
From the Configuration menu, select Flow Connections.
Step 2
Select the Bridges tab.
Step 3
Use the Equipment drop-down list to select which modules to display bridges for.
Step 4
Display bridges per SVID by using the SVID From-To fields to enter the range of SVIDs to display.
The following information is provided in the table in this window: Column Name
Description
AID SVID Admin State
This column displays the AID for the flow point. This column displays the SVID for the flow point. This column displays the Admin State of the flow point. This column shows the flow point’s alias, if any has been entered.
Alias
Step 6
Customize the information that is displayed in the table: • Sort the table based on a column, by clicking the column title. This toggles between ascending and descending display. •
Adjust the column widths to match the content by clicking the icon and selecting Pack All Columns or Pack Selected Column from the list that appears.
•
Turn off display of a column by clicking the icon and selecting the column name from the list that appears. A check mark indicates that the column will be displayed.
•
Turn on display of a horizontal scroll bar by clicking the icon and selecting Horizontal Scroll from the list that appears. A check mark indicates that the horizontal scroll bar will be displayed.
Step 7
If appropriate you can: • Select Print to print the list. • Select Save to save the list as a comma separated file. • Select Refresh to update the content of the window.
Step 8
Select Close to finish viewing the bridges.
End of Procedure
User Manual
195
Creating Flow Points, Bridges, and Cross Connections
How to Create a Flow Cross Connection This section describes how to create a flow cross connection. A flow cross connection consists of one or two 1 way cross connect primitives, where a bi-directional cross-connection requires two 1 way cross-connect primitives. These primitives must be created individually, and the Create Cross Connection wizard supports the user in doing this easily.
Procedure Step 1
From the Configuration menu, select Flow Connections.
Step 2
Select the Create button. In response, the Create Flow Cross Connection wizard appears.
Step 3
Use the Equipment drop-down list in the Filter section to select which module(s) you wish to display FLW facilities for. In response the From Port list displays all flow points (FLW) on the module or on the NE that can be cross connected.
Identify the FLW that shall be used to form the 1 way cross connect primitive of the cross connection. If you cannot see the FLW facility that you need: It has not been created yet, and you must create it before returning to this step again. See “How to Create a Flow Point (FLW)” on p. 184 for guidance on creating a FLW.
Step 5
Specify the1 way cross connect primitive of the cross connection. Do as follows: a) Select the FLW facility from which the cross connection shall start. This will have impact on the direction of the 1 way cross connect primitive.
b) Select Next to continue. In response, the To Port page appears.
c) From the To Port, select the FLW facility to which the cross connection shall end. d) Select Next to continue. In response, the Parameters Step 1 page appears.
e) Optionally enter an alias for this cross connection by using the Alias field.
User Manual
197
Creating Flow Points, Bridges, and Cross Connections
Step 6
Select Next to continue. In response, the Confirm page appears.
Step 7
Check the displayed information about the first 1 way cross connect primitive. If this does not look correct: Select Back to make corrections, or Cancel to close the Create Flow Cross Connection wizard and return to the Flow Connections window. If this does look correct: Confirm by selecting Next.
Step 8
Only bi-directional cross-connections are supported. Select OK and the wizard will create the reverse direction for you. The Result page appears.
Step 9
Select Finish to return to the Flow Connections window.
How to Create a 1 Way Flow Cross Connect Primitive This instruction describes how to create a single 1 way flow cross connect primitive that forms the return path of a bi-directional cross connection. If you during the creation of the bi-directional cross connection chose to not immediately create the second 1 way cross connect primitive, follow this procedure to create the second 1 way cross connect primitive now.
Procedure Step 1
From the Configuration menu, select Flow Connections.
Use the Equipment drop-down list to select which modules to display flow cross-connections for.
Step 4
Make a decision about how to filter your view: • To view flow cross-connections by port, go to Step 5. • To view flow cross-connections by SVID, go to Step 7.
Step 5
Display flow cross-connections per port by doing as follows: • Select Flow Cross Connections by Port in the View Mode drop-down list. • Use the Port drop-down list to select which ports to display flow points for. • Use the Port Role drop-down list to select which ports to display flow points for based on the port roles. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
Step 6
Go to Step 9.
Step 7
Display flow cross-connections per SVID by doing as follows: • Select Flow Points by SVID in the View Mode drop-down list. • Use the SVID From-To fields to enter the range of SVIDs to display. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
Step 8
Go to Step 9.
199
Creating Flow Points, Bridges, and Cross Connections
Step 9
In response the Flow Connections window is updated.
Step 10
From the flow cross connections list, select the bi-directional cross connection that consists of only 1 way cross connect primitive.
Step 11
Select Details.
Step 12
In the 1 WAY Cross Connection Primitives section, identify the 1 way cross connect primitive that needs to be created, and select the belonging Create button. In response, the Parameters Step 1 page appears.
Step 13
If relevant: Add an alias/comment to the 1 way cross connect primitive.
Step 14
Since this is the second 1 way cross connect primitive of a bi-directional cross connection, the direction is already is set to Bi. Select Next to continue. In response, the Confirm window appears.
In response, the Layer 2 Cross Connection Details window appears.
Chapter 3 Provisioning NEs
Step 15
Check the displayed information about the new 1 way cross connect primitive. If this does not look correct: Select Back to make corrections, or Cancel to close the Create Flow Cross Connection wizard and return to the Flow Connections window. If this does look correct: Confirm by selecting Next. In response, the Result page appears.
Step 16
Close the Create Flow Cross Connection wizard by selecting Finish.
Step 17
Close the Flow Connections window.
End of Procedure
How to Delete a Bi-directional Flow Cross Connection This instruction describes how to delete both 1 way cross connect primitives in a bi-directional flow cross connection at one time.
A flow cross-connection can be deleted at any time and can thus interrupt traffic. Ensure that traffic is not running by checking that the entities that are being cross-connected do not have administrative state In Service.
Procedure Step 1
From the Configuration menu, select Flow Connections. In response the Flow Connections window appears.
Step 2
Select the Flow Cross Connections tab. In response the Flow Connections window content changes.
User Manual
Step 3
Use the Equipment drop-down list to select which modules to display flow cross-connections for.
Step 4
Make a decision about how to filter your view: • To view flow cross-connections by port, go to Step 5. • To view flow cross-connections by SVID, go to Step 7.
Step 5
Display flow cross-connections per port by doing as follows: • Select Flow Cross Connections by Port in the View Mode drop-down list. • Use the Port drop-down list to select which ports to display flow points for. • Use the Port Role drop-down list to select which ports to display flow points for based on the port roles. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
Step 6
Go to Step 9.
201
Step 7
Display flow cross-connections per SVID by doing as follows: • Select Flow Points by SVID in the View Mode drop-down list. • Use the SVID From-To fields to enter the range of SVIDs to display. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
Step 8
Go to Step 9.
Step 9
In response the Flow Connections window is updated.
Step 10
Select Flow Cross Connections by Port or Flow Cross Connections by SVID in the View Mode drop-down list.
Step 11
From the cross connections table, select the cross connection to delete.
Step 12
Select the Delete button. In response a Warning window appears.
Step 13
Select OK to proceed with the deletion. Progress is shown in the lower, left corner of the Flow Connections window.
Creating Flow Points, Bridges, and Cross Connections
Chapter 3 Provisioning NEs
How to Delete 1 Way Flow Cross Connect Primitives This instruction describes how to delete a single 1 way cross connect primitive. Deleting both 1 way cross connect primitives in a flow cross connection gives the same result as in “How to Delete a Bi-directional Flow Cross Connection” on p. 201.
Requirement A flow cross-connection can be deleted at any time and can thus interrupt traffic. Ensure that traffic is not running by checking that the entities that are being cross-connected do not have administrative state In Service.
Procedure Step 1
From the Configuration menu, select Flow Connections. In response the Flow Connections window appears.
In response the Flow Connections window content changes.
User Manual
Step 3
Use the Equipment drop-down list to select which modules to display flow cross-connections for.
Step 4
Make a decision about how to filter your view: • To view flow cross-connections by port, go to Step 5. • To view flow cross-connections by SVID, go to Step 7.
Step 5
Display flow cross-connections per port by doing as follows: • Select Flow Cross Connections by Port in the View Mode drop-down list. • Use the Port drop-down list to select which ports to display flow points for. • Use the Port Role drop-down list to select which ports to display flow points for based on the port roles. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
Step 6
Go to Step 9.
Step 7
Display flow cross-connections per SVID by doing as follows: • Select Flow Points by SVID in the View Mode drop-down list. • Use the SVID From-To fields to enter the range of SVIDs to display. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
Step 8
Go to Step 9.
203
Creating Flow Points, Bridges, and Cross Connections
Step 9
In response the Flow Connections window is updated.
Step 10
From the cross connections table, select the cross connection that consists of the 1 way cross connect primitive.
Step 11
Select Details.
Step 12
204
If you wish to delete one 1 way cross connect primitive: Go to Step 14.
Confirm the deletion by selecting OK, or cancel it by selecting Cancel. You are returned to the Cross Connection Details window.
Step 17
If you want to delete, create or modify 1 way cross connect primitives in other flow cross connections: Use the Previous or Next buttons to reach the relevant flow cross connections.
Step 18
Close the Cross Connection Details window when you are finished.
End of Procedure
User Manual
205
Creating Flow Points, Bridges, and Cross Connections
How to View Flow Cross-connections This section describes how to view flow cross connections. This can be done only for the whole NE, not individually per module.
Procedure Step 1
From the Configuration menu, select Flow Connections.
206
Step 2
Select the Flow Cross Connections tab.
Step 3
Use the Equipment drop-down list to select which modules to display flow cross-connections for.
Step 4
Make a decision about how to filter your view: • To view flow cross-connections by port, go to Step 5. • To view flow cross-connections by SVID, go to Step 7.
Step 5
Display flow cross-connections per port by doing as follows: • Select Flow Cross Connections by Port in the View Mode drop-down list. • Use the Port drop-down list to select which ports to display flow points for. • Use the Port Role drop-down list to select which ports to display flow points for based on the port roles. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
Step 6
Go to Step 9.
Step 7
Display flow cross-connections per SVID by doing as follows: • Select Flow Points by SVID in the View Mode drop-down list. • Use the SVID From-To fields to enter the range of SVIDs to display. • Use the CRS Config drop-down list to select what type of flow cross connections to display. For example Add.
In response the Flow Connections window is updated.
The following information is provided in the table in this window: Column Name
Description
From/To
These columns displays the AIDs for the flow points that are cross-connected. The double arrow indicates a bi-directional cross connection, while a single arrow indicates a unidirectional cross connection as well as the direction of it. When the symbol is red, this indicates that the cross connections’s state is Disabled, while green indicates that it is In Service. This column displays the SVID for the flow points that are cross-connected. This column displays Bi to indicate that the cross connection is bi-directional. This column displays the service type of this cross connection. This column displays what type of cross connection this is.
SVID Connection Direction Facility Type CRS Config
Tunnel EVC
User Manual
•
Add/Drop: cross-connect between Client and Network ports
•
Pass Through: cross-connect between Network ports
• Hairpin: cross-connect between Client ports If the control plane is in use: This column shows which tunnel that this cross-connection is associated with. Do not edit this field, the control plane controls this field when applicable.
207
Creating DCN Cross-Connections
Step 10
Customize the information that is displayed in the table: • Sort the table based on a column, by clicking the column title. This toggles between ascending and descending display. •
Adjust the column widths to match the content by clicking the icon and selecting Pack All Columns or Pack Selected Column from the list that appears.
•
Turn off display of a column by clicking the icon and selecting the column name from the list that appears. A check mark indicates that the column will be displayed.
•
Turn on display of a horizontal scroll bar by clicking the icon and selecting Horizontal Scroll from the list that appears. A check mark indicates that the horizontal scroll bar will be displayed.
Step 11
If appropriate you can: • Select Print to print the Flow Cross Connections list. • Select Save to save the Flow Cross Connections list as a comma separated file. • Select Refresh to update the content of the window.
Step 12
Select Close to finish viewing the flow points.
Creating DCN Cross-Connections This section describes how to create DCN cross-connections. It assumes that the relevant channel modules as well as the NCU module, are already correctly provisioned. The following topics are provided: “How to Cross-connect PPP IP and EOC/ECC Interfaces” on p. 208 “How to View ECC Channels” on p. 210
How to Cross-connect PPP IP and EOC/ECC Interfaces This section describes how to cross-connect the EOC/ECC channel on the channel module with the PPP IP link on the NCU.
PS
Note
A DCN cross-connection can be deleted at any time and can thus interrupt DCN traffic. The cross-connect should not be deleted without ensuring that the PPP IP link and EOC/ECC channel entities that are being cross-connected do not have administrative state In Service.
Requirements •
208
A PPP IP link and an EOC/ECC channel must already have been created.
Ensure that there is enough un-used backplane bandwidth to support this backplane connection. This information can be found on the NE tab of the network element. See the Detailed System Description, “Deployment Restrictions” for information about backplane bandwidth restrictions and allocated backplane bandwidth per DCN entity.
Procedure Step 1
Select the NCU. Use the left hand hierarchical entity list in the Provisioning Manager window for this selection.
The Provisioning Manager window will display the Create ECC Connection list section on the right side.
Note
Step 2
The Create ECC Connection list section is only available when the maximum transmit rate for the PPP IP link (see “How to Create a PPP IP Interface” on p. 116) is lower than the absolute maximum that can be carried by the ECC/EOC entity. Select one of the NCU PPP IP links from the list (for example CRS_DCN-1-A-1). In response, the Create ECC Connection window displays the Parameters Step 1 page.
Step 3
Select which PPP IP link and EOC/ECC channel to interconnect as follows: a) Use the PPP IP AID drop-down list to select the relevant PPP IP link. b) Use the ECC AID drop-down list to select the relevant EOC/ECC channel. c) Select Next to continue. In response, the Create ECC Connection window displays the Parameters Step 2 page.
Step 4
User Manual
Specify whether communication over this DCN channel shall be two-way or not. Use the CRS Type drop-down list.
209
Creating DCN Cross-Connections
Step 5
When the Confirm wizard page appears: a) Check that the displayed settings are correct. b) If the settings are incorrect: Select Back to go back and correct the settings. c) If the settings are correct: Select Next to confirm. In response, the Complete window appears.
Step 6
If you wish to continue provisioning: Select the relevant entity type to provision from the Continue Provisioning? list on the right hand side of the Complete page.
Step 7
If you do not wish to continue provisioning: Select Finish. In response, you are returned to the Provisioning Manager window.
Step 8
Close the Provisioning Manager window by selecting Close.
End of Procedure
This section describes how to view cross-connections of EOC/ECC channels and PPP IP links for the NE. This can be done per cross-connection, or for the whole NE at once.
Per Interconnection
Procedure Step 1
Select the PPP IP link in the Entities, Tree tab.
Step 2
Select the Info tab in the Parameters pane to see which ECC/EOC channel the link is connected to.
Step 3
Select the Config tab to see: • The Committed Information Rate (CIR) for the PPP IP link in the Max Tx Rate field. • The far end IP address for the PPP IP link in the Far End IP Address field. • The near end IP address for the PPP IP link in the IP Address field.
Step 4
Select the ECC/EOC channel in the Entities, Tree tab.
Step 5
Select the Info tab in the Parameters pane to see: • The bit rate the ECC/EOC channel supports, in the Maximum ECC Bitrate field. • The PPP IP link that the ECC/EOC channel is connected to, in the PPPIP AID field.
The following information is provided in this window: Column Name
Description
PPP AID
This column displays the AID for each PPP IP link in the NE. This column displays the AID for each ECC channel in the NE. This column displays the IP address of the PPP IP link in this NE. This column displays the IP address of the PPP IP link in the far end NE. This column displays the maximum transmit rate that the PPP IP link supports. This column displays the maximum bit rate that the ECC channel supports. This column displays the channel number for the channel carrying the ECC.
ECC AID IP Address Far End IP Address Max Tx Rate Maximum ECC Bitrate Channel
User Manual
211
How to Delete Equipment/Facilities Manually
Step 3
Customize the information that is displayed in the ECC List window: • Sort the table based on a column, by clicking the column title. This toggles between ascending and descending display. •
Adjust the column widths to match the content by clicking the icon and selecting Pack All Columns or Pack Selected Column from the list that appears.
•
Turn off display of a column by clicking the icon and selecting the column name from the list that appears. A check mark indicates that the column will be displayed.
•
Turn on display of a horizontal scroll bar by clicking the icon and selecting Horizontal Scroll from the list that appears. A check mark indicates that the horizontal scroll bar will be displayed.
Step 4
If appropriate you can: • Select Print to print the ECC list. • Select Save to save the ECC list as a comma separated file. • Select Refresh to update the content of the window.
Step 5
Select Close to finish viewing the ECC list.
How to Delete Equipment/Facilities Manually This section contains the instruction for deleting an entity. An entity cannot be deleted before the entities that are dependent on it are deleted. For example, you cannot delete a port that is part of a cross-connection. The only exception is for modules, a forced deletion option is supported for these, allowing deletion of all dependent entities regardless of administrative state.
PS
Deleting a service from the internal database is service affecting. Be careful when deleting an EOC/ECC channel, this can affect the DCN.
Note
Requirement The system will allow deletion of all cross-connections except ROADM cross-connections, regardless of whether traffic is running or not. Therefore,
This window displays a hierarchical list of all entities that are supported by the entity you selected in Step 1. The window can be used in parallel with the rest of the Element Manager. Step 3
If you wish to delete a module: You can delete the module and all dependent entities all at once by selecting the Force Delete button.
Step 4
If the entity you wish to delete has dependent entities: a) Select each dependent entity and notice the administrative state in the Admin State column. b) If the Admin State is In Service: Change the administrative state as follows: • Select the Set Admin State button. • From the context sensitive menu that appears, select Management, Maintenance or Disabled. c) Select the Delete button. In response, that entity is removed from: • •
the Name column in the Delete window the Entities pane
If this deletion does not occur immediately, select the Refresh button. I
User Manual
213
Handling Network Element User Accounts
Step 5
Select the entity you wish to delete and do as follows: a) Notice the administrative state in the Admin State column. b) If the Admin State is In Service: Change the administrative state as follows: • Select the Set Admin State button. • From the context sensitive menu that appears, select Management, Maintenance or Disabled. c) Select the Delete button. d) In response, that entity is removed from: • the Name column in the Delete window • the Entities pane
If this deletion does not occur immediately, select the Refresh button. Step 6
Close the Delete window by selecting Close.
End of Procedure
This section describes how to add, modify, and delete user accounts on individual Network Elements. The Network Elements all are set up with four default user accounts, ADMIN, PROVISION, OPERATOR and MONITOR. You can print a list of the network element user accounts or save the list from the User Management window. When saving the file formats HTML, CSV, text and PDF are supported. The following sections are provided: Adding a User Account Modifying an User Account Deleting a User Account
Adding a User Account This section contains the procedure for adding a network element user account.
Requirements The Element Manager must manage the network element with SNMPv3 access using a user account with ADMIN privileges.
Procedure Step 1
Select the relevant network element in the Managed Elements pane.
Step 2
From the Main Menu, select Configuration -> User Management. In response the User Management window appears.
Select Create. In response the Create User Account window appears.
Step 4
Fill in the following fields:
Step 5
Enter the name of the new NE user account in the User Name field. The user account name must have 4-10 characters (for example your name) and is not case-sensitive.
Step 6
Use the Privilege drop-down list to select the privilege level that this new user account shall have.
The privilege levels are: ADMIN, PROVISION, OPERATOR AND MONITOR. Step 7
Use the Security Level drop-down list to select the SNMP security level for the new user account. This setting determines the permitted level of security. The options are: • NoAuthNoPriv -no authentication, no privacy • AuthNoPriv - authentication, no privacy • AuthPriv - authentication, privacy
Step 8
The fields UISTATE, TMOUTA and TMOUT pertain only to TL1 usage, which is not relevant here.
Step 9
Enter a password for the new user account into the Password field, and re-type the password in the Retype Password field. The password is not case-sensitive and must fulfil the following requirements: • • • • •
Be 6-10 characters long Include at least one alpha character [a..z, A..Z] Include at least one numeric character [0..9] Include at least one punctuation character [!,@, #, $, %, ^, (, ), _, +, |, ~, {, }, [, ], -, .] Not include an associated username string.
Step 10
Select OK to add the account.
Step 11
Select Close to close the User Manager window.
End of Procedure
User Manual
215
Handling Network Element User Accounts
Modifying an User Account This section contains the procedure for modifying a network element user account.
Requirements The Element Manager must manage the network element with SNMPv3 access using a user account with ADMIN privileges.
Procedure Step 1
Select the relevant network element in the Managed Elements pane.
Step 2
From the Main Menu, select Configuration -> User Management. In response the User Management window appears.
Step 3
Select Modify.
Step 4
If relevant: Modify the name of the NE user account in the User Name field. The user account name must have 4-10 characters (for example your name) and is not case-sensitive.
Step 5
If relevant: Use the Privilege drop-down list to change the privilege level that this user account shall have. The privilege levels are: ADMIN, PROVISION, OPERATOR AND MONITOR.
216
Step 6
If relevant: Use the Security Level drop-down list to change the SNMP security level for the user account. This setting determines the permitted level of security. The options are: • NoAuthNoPriv -no authentication, no privacy • AuthNoPriv - authentication, no privacy • AuthPriv - authentication, privacy
Step 7
The fields UISTATE, TMOUTA and TMOUT pertain only to TL1 usage, which is not relevant here.
In response the Modify User Account window appears.
Chapter 3 Provisioning NEs
Step 8
If relevant: Enter new password for the user account into the Password field, and re-type the password in the Retype Password field. The password is not case-sensitive and must fulfil the following requirements: • • • • •
Be 6-10 characters long Include at least one alpha character [a..z, A..Z] Include at least one numeric character [0..9] Include at least one punctuation character [!,@, #, $, %, ^, (, ), _, +, |, ~, {, }, [, ], -, .] Not include an associated username string.
Step 9
Select OK to apply the changes to the account.
Step 10
Select Close to close the User Manager window.
End of Procedure
Deleting a User Account This section contains the procedure for deleting a network element user account.
It is not advisable to delete user accounts which are in use.The network element considers a user account to be in use in the following situations: •
When a user has logged on to the network element with this user account. This includes connections using http (Web Console), Telnet (Craft Console), SSH (Craft Console), SCP, and FTP. The network element will deny deletion of a user account when a user has logged on with it.
•
When a management application (for example an NMS system) has a virtual SNMPv3 session with the network element, using this user account (see Figure 17). The network element considers a session to be active for 10 minutes after it was terminated. It is possible to delete this user account even though a virtual SNMPv3 session uses it, but the user will be warned that the account is used by an active SNMPv3 session. The user will also have the option to cancel the deletion.
Figure 17 shows the relationships between management applications, user accounts, and users.
User Manual
•
Connection-oriented management applications establish connections to the network element by allowing the user to log on. After a certain period of user inactivity, the network element will terminate the connection.
•
Management applications using SNMP to communicate with the network element are connectionless. They establish a virtual session with the network element by using polling. SNMPv1 based management applications do not use a network element user account to regulate access to the network element, they use SNMP community strings. SNMPv3 based management tools use a network element user account to regulate access to the network element.
217
Handling Network Element User Accounts
Figure 17:
User Accounts and Management Applications
Requirements The Element Manager must manage the network element with SNMPv3 access using a user account with ADMIN privileges.
Step 1
Select the relevant network element in the Managed Elements pane.
Step 2
From the Main Menu, select Configuration -> User Management. In response the User Management window appears.
Step 3
Select Delete. In response a confirmation window appears.
Step 4
Select Yes to delete the account, or Cancel to cancel the deletion.
Chapter 4 Configuring NEs In the FSP3000R7, most features are configured during provisioning. The parameters that define these features are not configurable afterwards. How to set these parameters is described in “Creating Equipment/Facilities Manually” on p. 83.
This section gives an introduction to provisioning of the FSP 3000R7. It contains instructions for provisioning shelves, modules, pluggable transceivers, channels and virtual channels to the internal database, by using the Element Manager. The following topics are provided: Configuring Parameters, which contains instructions for changing configurable parameters. Configuring DCN Features, which contains instructions for configuring the NE for use of OSC, and for configuring LAN IP on the NCU. Configuring Security, which contains instructions for enabling and disabling FTP server/client, SSH protocol and adding known hosts. Working with Protection, which contains instructions for viewing configuration information about the protection groups, and how to operate the protection switch. How to Change the Administrative State, which describes how to change the administrative state for equipment or facilities. Configuring the OTDR, which describes how to provision an OTDR shelf and open the OTDR application. How to configure OTDR measurements and operate the OTDR is described in the OTDR Installation, Provisioning, and Operations Manual. Viewing Node Channel Traces, which describes how to trace a wavelength channel or sub-channel through the NE. Viewing Information About the NE, which contains instructions for viewing configured information about the entities an NE. Configuring Date and Time, which contains instructions for setting the date and time, or NTP servers for the NE.
User Manual
219
Configuring Parameters
Configuring Remote Syslog Servers, which contains instructions for configuring remote syslog server destinations for the NE. How To Configure Scheduled Equalization, which contains instructions for setting up scheduled equalization for NEs containing 8ROADM devices. Configuring Span Equalization, which contains instructions for setting up span equalization in both ROADM and FOADM networks. Viewing and Configuring Trace Messages, which contains instructions for viewing and configuring messages for the Trace comparison process. How to Configure TCA Thresholds, which contains instructions for configuring the thresholds for Threshold Crossing Alerts. How to Configure Tandem Connection Monitoring, which contains instructions for configuring Tandem Connection Monitoring. Configuring Ethernet OAM/CFM, which contains instructions for configuring the Ethernet OAM/CFM entities. How to Configure Loop-Backs, which contains the instructions for setting and releasing a loop-back. “Managing Cables in the Internal Database” on p. 353, which contains the instructions for adding new connections to the Physical Connections List.
“How to Force a Laser On” on p. 360, which contains the instructions for forcing a laser on. “How to Set the Forced-Laser Fallback/Release Timer” on p. 362, which contains the instructions for changing the force-laser fallback timer. “How to Allow Forced Deletion of Entities” on p. 363, which contains the instructions for how to enable use of automatic deletion of dependent entities. “Enabling Use of SCU Ring Interconnection” on p. 363, which contains the instructions for how to enable or disable a NE for ring interconnection of the SCUs and ROADMs. “How to Change Equipment Capabilities” on p. 364, which describes how to increase the capabilities of a module. “How to Configure TIF Contacts” on p. 365, which describes how to configure telemetry input and output ports on the UTM module.
Configuring Parameters Most parameters in the NE can only be changed during provisioning. This means that to change the parameters for an entity, the entity must first be deleted, and then added again, with the new parameter value. For some entities, the parameters can be modified directly. This section gives descriptions of how to change these configurable parameters. The following topics are provided: “How to Configure Parameters” on p. 221
“How to Set the Automatic Laser Shutdown Mode” on p. 358, which contains the instructions for changing the ALS mode.
Chapter 4 Configuring NEs
“How to Configure System Parameters” on p. 222 “How to Configure NE Mode” on p. 223
How to Configure Parameters This section gives a general description on how to change configurable parameters.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the entity to view parameters for in the Entities pane. In response, all available information about the entity is displayed in the Parameters pane.
Step 3
Select the Config tab in the Parameters pane. In response all configured parameters for the selected entity are displayed.
In response, the Modify Configuration window appears. The parameters that are displayed here, depend on the entity that you selected previously. See the document Management Data Guide for descriptions of all parameters that may be displayed here.
Step 5
Use the provided drop-down lists to select a new value for the parameter. Value range and default values for the parameters are listed in the document Management Data Guide, per module type.
Step 6
Select OK to apply the change or Cancel to discard.
End of Procedure
User Manual
221
Configuring Parameters
How to Configure System Parameters This instruction describes how to change system parameters for the NE.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.
Step 2
Select the System tab in the Parameters pane. In response all configured parameters for the selected entity are displayed.
Step 3
Select the Modify button.
Step 4
Enter a text string to identify the NE in the System ID field. The system ID can be used to identify an NE instead of the NEs IP address. The system ID is required for proxy access via TL1 (acts as TL1 TID) or proxy access via http/https. The mapping between system ID and system IP address is stored on the NE (no DNS required). OSPF-enabled NEs exchange their known system ID to system IP mappings. The system ID can for example be used to address the NE via a GNE, using the GNE's http or TL1 proxy functionality. The default value is FSP3000. This value must be changed so that each NE in the network has a unique system ID. Your entry must conform to the following rules: • • • • • • •
Step 5
222
must begin with any one of the 52 alphabetic characters A through Z in upper case and a through z in lower case may contain [ A-Z, a-z, 0-9] may contain [ . ] as a domain separator must be minimum 1 character and maximum 20 characters, if the NE will be managed later using TL1 must be minimum 1 character and maximum 64 characters, if the NE will be managed later using the Craft Console, Web Console or Element Manager Must end with [A-Z, a-z, 0-9]
Enter the height of the rack, in Height Units (HUs), into the Size of the Rack field. One HU is 44.45 mm.
In response, the Modify Configuration window appears.
Chapter 4 Configuring NEs
Step 6 Step 7
Enter a name for the NE in the NE Name field. Enter information about where the NE is located into the System Location field.
Step 8
Enter information about a contact person for the NE into the System Contact field.
Step 9
Use the provided drop-down lists to select a new value for the parameter.
Step 10
Select OK to apply changes or Cancel to discard.
End of Procedure
How to Configure NE Mode This instruction describes how to configure which mode the NE shall work in. The NE mode must reflect the traffic configuration the NE shall handle, for example add-drop multiplexing.
Procedure Step 1
Double-click the relevant NE in the Managed Elements pane.
Select the System tab in the Parameters pane. In response all configured parameters for the selected entity are displayed.
Step 3
Select the Modify button. In response, the Modify Configuration window appears.
Step 4
User Manual
Use the Traffic Config drop-down list to select the relevant mode for this NE. The options are: • Optical terminal multiplexer node • Optical add drop multiplexer node • Optical converter node • In line amplification node • Hub node.
223
Configuring DCN Features
Step 5
Select OK to apply the change or Cancel to discard.
End of Procedure
Configuring DCN Features This section describes how to configure DCN features. It assumes that the relevant modules are already correctly provisioned. The following topics are provided: “How to Configure a LAN IP Address” on p. 224 “How to Configure the System IP Address” on p. 225 “Configuring OSPF for the System Interface” on p. 230 “Defining OSPF for Ethernet PPP IP/LAN IP Interfaces” on p. 232 “Assigning/Removing Static Routes” on p. 233 “Assigning/Removing a Default Route” on p. 235 “Assigning a Default Gateway via the IP Ethernet Interface” on p. 237
How to Configure a LAN IP Address This procedure describes how to configure the IP address of the LAN IP entity on the NCU.
PS
Note
The system IP address is used as the SNMP trap sender address, so this is the IP address that should be entered in the Element Manager, if the Element Manager shall be used for management of the NE.
Procedure Step 1
Select the SC LAN IP entity on the NCU in the Entities pane.
Step 2
Select the Config tab and the Modify button. In response, the Modify window appears.
Step 3
If relevant, enter an alias for this interface.
Step 4
If this interface shall be a numbered IP interface: Fill in the IP Address and the IP Mask in the relevant fields. Ensure that the planned IP addresses for the System, the Ethernet IP interfaces and the PPP IP interfaces are unique. Attempting to use non-unique addresses will be denied. In order to comply with the IP standards, using 255.255.255.254 as a subnet mask value is not allowed.1
“Connecting the OSC and LAN IP Ethernet Interface” on p. 238
Chapter 4 Configuring NEs
Step 5
If required, change the auto-negotiation setting for the Ethernet IP interface by selecting Enabled or Disabled in the Auto-Negotiation drop-down list.
Step 6
Select OK to apply the changes and close the Modify window.
Step 7
Select the State tab and the Modify button. Set the administrative state to the relevant value at this time. In order for the interface to become operational, you must set the administrative state to In Service or Automatic In Service.
Step 8
Reboot the NE for the new IP addresses to take effect. A reboot causes the management computer to momentarily lose connection to the NE. The NE's IP connectivity should be restored within a few minutes. The NE's management connectivity is restored at a later time, indicated by four consecutive beeps and the MOD LED shining green.
The system IP address is the loopback IP address for the NE, and is used as the SNMP trap sender address, the OSPF router ID, and for ring group switching. The Element Manager uses the System IP Address for connecting to the NE, so if you change this address, the Element Manager will lose contact with the NE. The system IP address is always OSPF enabled.
Additional considerations if the Control Plane is active If you change the System IP address, this will naturally change the mapping between the Target Identifier (TID) (System Identity) for the NE and the IP address to which that TID resolves. This has implications if Control Plane provisioning is active, and you have chosen to use TIDs to identify neighboring elements when configuring LIF_CP entities. A change to the mapping between IP address and TID is not automatically reflected on the LIF_CP configuration. In order to update any local LIF_CP entities affected by such a change to IP/TID mapping at a remote element, the LIF_CP will have to be removed and re-added. This can be avoided by choosing to enter LIF_CP configuration information using IP addresses rather than TIDs. This instruction describes how to configure the System IP address of the NE.
1. The value 255.255.255.255 is allowed, as it may be needed for special use cases. Please contact ADVA Optical Networking for more information if you want to use this value.
User Manual
225
Configuring DCN Features
Procedure Step 1
PS
Note
If the NE shall use OSPF: Ensure that the planned IP addresses for the system IP address, the Ethernet IP interfaces and the PPP IP interfaces are unique. If the IP addresses are not unique, the DCN will be non-functional because OSPF will not announce multiple IP interfaces with the same IP address. The default values for the system and Ethernet IP addresses are not unique, so they must be changed in this case. The system IP address is used as the SNMP trap sender address, so this is the IP address that should be entered in the Element Manager, if the Element Manager shall be used for management of the NE. If the NE shall not use OSPF: The system IP address and the Ethernet address may be the same. Likewise the PPP IP addresses may be the same.
Step 2
Right-click the relevant NE in the Managed Elements pane and select System IP Settings.
Step 3
Select the System IP tab. In response the current System IP address and mask is displayed.
Step 4
Select the Modify button. In response, the Modify Configuration window appears.
226
Step 5
Make a note of the existing address in the IP Address field.
Step 6
Enter the loop-back IP address in the IP Address field.
In response, the System IP Settings window displays.
Chapter 4 Configuring NEs
Step 7
Enter the mask for the loop-back IP address in the IP Mask field. The mask entered is only used for any existing unnumbered Ethernet interface in the NE; if no such interface exists, the subnet mask is simply ignored. In order to comply with the IP standards, using 255.255.255.254 as a subnet mask value is not allowed.1
Step 8
Select OK to apply the change or Cancel to discard. In response, a warning will be displayed.
Step 9
Confirm that you want to continue, or cancel the application of your entry.
It is necessary to reboot the NE for the new system IP address to take effect. However, you can choose to reboot later, do as follows: a) Stop the automatic reboot process by selecting Cancel. b) Make a note to remember to reboot at a later time. A reboot causes the management computer to momentarily lose connection to the NE. The NE is again ready for operation within approximately five minutes. Four consecutive beeps and the MOD LED shining green indicate that the NE has completed the reboot and can be accessed again.
Step 11
Remove the old IP address (see note you made in Step 5) that the Element Manager was connected to, see “How to Delete IP Connections” on p. 52 for guidance.
Step 12
Add the new system IP address to the Element Manager’s list of managed elements, see “How to Add a Single IP Connection” on p. 39 for guidance.
End of Procedure
1. The value 255.255.255.255 is allowed, as it may be needed for special use cases. Please contact ADVA Optical Networking for more information if you want to use this value.
User Manual
227
Configuring DCN Features
Configuring OSPF Areas In the OSPF routing protocol each router keeps track of the neighboring routers, exchanges the IP networks that are reachable through each router, calculates the shortest path to all the reachable IP destinations, and adds routes to its routing table accordingly. For OSPF to work, the IP addresses of numbered interfaces in the DCN must be unique. A DCN configuration with non-unique numbered interfaces will be rejected. OSPF is enabled per IP interface, and the System IP address will always be advertised. The System IP address is used as the OSPF Router ID. Depending on the size of the OSPF domain, a single or multiple areas may be configured. An NE having interfaces in multiple areas is called an Area Border Router (ABR) and must always have at least one interface configured in the backbone area (0.0.0.0). An area can also be configured to be a stub area. Please refer to the DCN chapter in the Detailed System Description for more information on stub areas. This instruction describes how to configure OSPF areas for the system.
Procedure Step 1
Double-click the relevant NE in the Entities pane.
In response, the Parameter pane displays. Select the OSPF tab in the Parameter pane. In response, all available OSPF information is displayed.
228
User Manual
Chapter 4 Configuring NEs
Step 3
Select the Add button. In response, the Create OSPF Area window appears.
Step 4
Enter the area ID for the System interface in the Area ID field. OSPF areas are identified by the 32-bit area ID, which is expressed in dotted decimal format. For example, area 0.0.1.15 is the same as area 271 in decimal format.
Step 5
Select the area type from the Area Type drop-down list, either Stub or Normal.
In response, the Create OSPF Area window content changes.
Step 7
Enter the Stub Default Route Cost for this stub area. This is a metric that is advertised for the default route into the stub area. It ranges from 0 to 65535. The lower the number, the more likely this area border router is used for external/default traffic.
User Manual
229
Configuring DCN Features
Step 8
Select Next. In response, the Create OSPF Area window content changes.
Step 9
Select Next.
Step 10
Select Finish to close the Create OSPF Area window.
Step 11
To view the settings of any OSPF area, select that area in the OSPF area list, then toggle the Config button.The OSPF area settings will be displayed below the OSPF area list.
Step 12
Ensure that all required OSPF areas for this NE have been created by checking the OSPF area list. Each OSPF area can be identified by its AID, which reflects its area ID.
End of Procedure
Configuring OSPF for the System Interface OSPF is always enabled for the System (Loopback) interface. The OSPF protocol uses the System IP address as the OSPF router ID. The System IP will only take effect as the OSPF Router ID, after the NE has been rebooted. This instruction describes how to configure the redistribution and area ID for the system interface.
In response, all available information about the entity is displayed in the OSPF pane.
Step 3
Select the Modify button to change any of these parameters. In response, the Modify window appears.
Step 4
Use the Area ID drop-down list to select the correct OSPF area.
Step 5
Use the Route Redistribution drop-down list to specify how the routes shall be redistributed. • Select Static to redistribute static routes using OSPF. • Select None if static routes will not be distributed using OSPF. This is the initial default value.
PS
Note
User Manual
Static routes shall not be redistributed into stub areas; similarly an NE which is internal to a stub area shall not redistribute static routes over OSPF.
231
Configuring DCN Features
Step 6
Select OK to apply your settings.
End of Procedure
Defining OSPF for Ethernet PPP IP/LAN IP Interfaces This instruction describes how to configure the redistribution and area ID for the system interface.
Procedure Step 1
Double-click the relevant Network Element in the NE Pane.
Step 2
Select from the NCU submenu either: • the supervisory channel (SC-1-A-C LANIP) • the PPP IP channel (LINK-1-A- PPP IP)
Step 3
Select the Config tab.
Step 4
To make changes to the current OSPF parameter values, select Modify.
Step 5
Set the OSPF routing properties for the interface as follows: a) Activate OSPF by setting OSPF Routing to the relevant option.
b) Enter the OSPF cost for this interface in the Routing Metric field. The default OSPF costis 100, which is independent of the IP interface's bandwidth. The higher the OSPF Cost, the less likely the OSPF routing protocol will enter routes to the attached network which go via this interface into the routing tables of the OSPF routers. c) Select the OSPF area ID for this interface. The area ID may be different for different IP interfaces on a network element. If multiple area ID's are configured, the NE operates as an area border router. An NE configured as an area border router must have at least one IP interface assigned to the backbone area ID 0.0.0.0. Step 6
Select OK to apply your changes or Cancel to cancel them.
This procedure describes how to add or delete a static route to the routing table. Static routes can be configured to be able to reach new destinations (destinations that are not immediately reachable through the configured IP interfaces). Static routes must point out the next hop or gateway to reach the new destination, as well as the IP interface over which the gateway can be reached. A gateway in a static route must therefore always be in the same IP subnet as the IP interface towards the gateway in that static route. For a static route using a PPP IP interface towards the gateway, the gateway IP address must be equal to the local/near-end IP address of that PPP IP interfaces. In the case of an unnumbered PPP IP interface, use the local System IP address as the default gateway. The DCN plan should give you the needed information to configure static routes: for each new destination the gateway and IP interface towards the gateway must be defined. A static route will become active immediately (i.e. no reboot is required), but only if its IP interface towards the gateway is operationally up. You can view both the active and the inactive routes. Viewing the inactive routes allows you to delete static route configurations that are not currently active. To define static routes, a user account of ADMIN level is required.
Procedure Step 1
Right-click the relevant NE in the Managed Elements pane and select System IP Settings. In response, the System IP Settings window displays.
User Manual
233
Configuring DCN Features
Step 2
Select the Routing Table tab.
Step 3
Select Add to open the Add Route window.
Step 4
Enter the destination IP address for this new route in the Destination field.
Step 5
Enter the subnet mask for the destination in the Mask field.
Step 6
Enter the IP address of the local interface gateway in the Gateway field.
Step 7
If required, change the default routing metric value displayed in the Metric field.
This value represents the weight for the OSPF interface in the OSPF calculation. The higher this number is, the more expensive a route becomes when using this link. In the case of multiple routes to the same destination, the route with the lower metric is preferred. Changing the routing metric will be taken into account immediately. Step 8 Step 9
In the Device field, use the drop-down list to select the IP interface that the gateway is reachable over. Apply your setting by selecting OK or cancel them by selecting Cancel.
Step 10 Step 11
Select Refresh in either the Active Routes or Inactive Routes section to update the list of routes after your change. You can now see the route you added in either the Active Routes or Inactive Routes section.
In response the current active routes in the system are displayed.
Chapter 4 Configuring NEs
Step 12
If you wish to remove either an active or inactive route, select the route in the Active Routes or Inactive Routes list, and select Delete. In response a warning window appears.
Step 13 Step 14
Select Yes to confirm the deletion or Cancel to cancel the deletion. When you are finished working with routes, select Close to close the System IP Settings window.
End of Procedure
Assigning/Removing a Default Route This procedure describes how to add or delete a default route to the routing table.
A default route is just a special case of a static route, namely for the destination "0.0.0.0". If no other, more specific static routes are present for the destination being looked up, the default route will always apply as a last resort. Configuring a default static route is the easiest way to perform static routing, and can still be useful in combination with dynamic routing, namely as a fall-back solution in case OSPF would fail. There is one special option for configuring a default route using an Ethernet interface: see “Assigning a Default Gateway via the IP Ethernet Interface” on p. 237. This method provides a very simple way of configuring a default route, and this configuration will be taken into account by the Linux system and be operational independently of the ADVA specific NE software. This default route will have metric 0, and thus have the highest priority. However, by design, this default route cannot be advertised by OSPF. Activating this configuration requires a reboot. Consider whether this option is relevant. To define static routes, a user account of ADMIN level is required.
Procedure Step 1
Right-click the relevant NE in the Managed Elements pane and select System IP Settings. In response, the System IP Settings window displays.
User Manual
235
Configuring DCN Features
Step 2
Select the Routing Table tab.
Step 3
Select Add to open the Add Route window.
Step 4
Enter the value 0.0.0.0 in the Destination field.
Step 5
Enter the 0.0.0.0 in the Mask field.
Step 6
Enter the IP address of the local interface that shall be the default route in the Gateway field. This IP address must be entered manually even if the local interface is unnumbered (=System IP address).
Step 7
If required, change the default routing metric value displayed in the Metric field.
This value represents the weight for the OSPF interface in the OSPF calculation. The higher this number is, the more expensive a route becomes when using this link. Changing the routing metric will be taken into account immediately. Step 8
Step 9
In the Device field, use the drop-down list to select the local IP interface for the default route. The options are: • LINK-1-A-x, if the PPP IP interface has been provisioned. Apply your setting by selecting OK or cancel them by selecting Cancel.
Step 10
236
Select Refresh in either the Active Routes or Inactive Routes section to update the list of routes after your change.
In response the current active routes in the system are displayed.
Chapter 4 Configuring NEs
Step 11
You can now see the route you added in either the Active Routes or Inactive Routes section.
Step 12
If you wish to remove the default route, select it in the Active Routes or Inactive Routes list, and select Delete. In response a warning window appears.
Step 13 Step 14
Select Yes to confirm the deletion or Cancel to cancel the deletion. When you are finished working with routes, select Close to close the System IP Settings window.
This section describes special option for configuring a default route using an Ethernet interface. This method provides a very simple way of configuring a default route, and this configuration will be taken into account by the Linux system and be operational even if the NE software is not running. This default route will have metric 0, and thus have the highest priority. However, by design, this default route cannot be advertised by OSPF. Activating this configuration requires a reboot. If dynamic routing using the OSPF protocol is used, this gateway will only be used if OSPF fails.
Procedure Step 1
Right-click the relevant NE in the Managed Elements pane and select System IP Settings. In response, the System IP Settings window displays.
User Manual
237
Configuring DCN Features
Step 2
Select the Default Gateway tab.
Step 3
Select the Modify tab.
Step 4 Step 5
Enter the IP address of the default gateway in the Default Gateway field. Apply your setting by selecting OK or cancel them by selecting Cancel.
Step 6
Select Close to close the System IP Settings window.
End of Procedure
Connecting the OSC and LAN IP Ethernet Interface This procedure describes how to connect the OSC and the Ethernet IP interface.
Procedure
238
Step 1
Double-click the relevant NE in the Managed Elements pane.
Step 2
Expand the list of equipment in the Entity pane and select the OSCM (MOD-x-y-OSCM).
This section contains instructions for configuring security related aspects of the NE. The following topics are provided: How to Enable/Disable the FTP Server How to Enable/Disable the FTP Client How to Enable/Disable Use of SSH How to Configure Known Hosts
How to Enable/Disable the FTP Server Software update files, database update files and alarm profile files can be imported and exported from the NE using an FTP client-server pair. The Element Manager has an FTP client on board. In order to upload files to the NE, a PC running an FTP server is required. NEs with a NCU with a 1 GB CompactFlash (CF) installed, also have an FTP server on board. The NCU-II is an example of this. In this case no external FTP server is necessary. The FTP server is disabled by default, thus after installation of a software update, the FTP server functionality will be disabled again. Thus, if use of the FTP server is required, the FTP server must be enabled after a software update. If use of FTP is considered a security threat, the FTP server should be disabled after the software update.
User Manual
239
Configuring Security
This section contains the instruction to enable the FTP server.
Procedure Step 1
Double-click the relevant Network Element in the NE Pane.
Step 2
From the Main Menu select Configuration -> Security Settings. In response the Security Settings window appears.
Select the Modify button. In response, the Modify window appears.
Step 4
Use the FTP Server drop-down list and select Enable to enable the FTP Server. To disable it, select Disable.
Step 5
Select OK to apply the change, or Cancel to discard the change.
How to Enable/Disable the FTP Client Software update files, database update files and alarm profile files can be imported and exported from the NE using an FTP client-server pair. The Element Manager has an FTP client on board. This section contains the instruction to enable or disable the FTP client that is built into the Element Manager.
Procedure Step 1
Double-click the relevant Network Element in the NE Pane.
Step 2
From the Main Menu select Configuration -> Security Settings.
Select the Modify button. In response, the Modify window appears.
Step 4
Use the FTP Client drop-down list and select Enable to enable the FTP client. To disable it, select Disable.
Step 5
Select OK to apply the change, or Cancel to discard the change.
End of Procedure
User Manual
241
Configuring Security
How to Enable/Disable Use of SSH This instruction describes how to enable or disable use of SSH for secure communication with the NE.
Procedure Step 1
Double-click the relevant Network Element in the NE Pane.
Step 2
From the Main Menu select Configuration -> Security Settings.
Step 3
Select the Modify button. In response, the Modify window appears.
Step 4
Use the SSH Server drop-down list and select Enable to enable the use of the SSH protocol. To disable it, select Disable.
Step 5
Select OK to apply the change, or Cancel to discard the change.
End of Procedure
How to Configure Known Hosts The secure shell protocol (SSH) allows data to be exchanged over secure channels. This involves use of private and public keys for exchanging the data with known hosts, and these items must be defined for each known host that may access the NE. This instruction describes how to define known hosts and their public keys.
In response the Security Settings window displays a list of the known hosts.
The following information is displayed: Column Name
Description
Known Host IP
This is the IP address of the remote host that shall de defined as a known host for the NE. This is the host's SSH public key encryption algorithm. RSA, RSA1 or DSA are supported. The SSH client, and the SSH server on the remote host will negotiate which one to use. This is a readable form of the remote host’s public key. By applying the cryptographic hash function MD5, SSH converts the public key of the remote host to this unique, more readable, form that you can use to exchange and compare with other key authentication data.
Type
Fingerprint
Step 4
User Manual
Select which action you wish to take: • To add a new known host to the list, go to Step 5. • To modify an the fingerprint for an existing known host, go to Step 11. • To delete a known host from the list, go to Step 15.
243
Configuring Security
Step 5
Select the Add button. In response, the Add Known Host dialog appears.
Step 6
Enter the IP address of the new known host in the Known Host IP field.
Step 7
Specify the host's SSH public key encryption algorithm by using the Type drop-down list. RSA, RSA1 or DSA are supported.
Step 8
Enter the fingerprint for the host’s public key in the Fingerprint field.
Step 9
Select OK to add the known host, or Cancel to discard your entries and return to the Known Hosts tab.
Step 10
Continue from Step 15.
Step 11
Select the Modify button.
Step 12
Modify the fingerprint for the host’s public key, in the Fingerprint field.
Step 13
Select OK to apply the new fingerprint, or Cancel to discard your entries and return to the Known Hosts tab.
Step 14
Continue from Step 15.
Step 15
Select the known host that you wish to delete from the known hosts list.
Step 16
Select the Delete button. In response, a confirmation window appears.
In response, the Modify Fingerprint dialog appears.
Chapter 4 Configuring NEs
Step 17
Select Yes to complete the deletion, or Cancel to abort the action. If you selected Yes, the list of known hosts is updated. If necessary, you can refresh the list of known hosts by selecting the Refresh button.
“How to Make a Manual Protection Switch (Method B)” on p. 250 “How to Make a Manual Ethernet Linear Protection Switch” on p. 252 “How to Inhibit Protection Switch (Method A)” on p. 254 “How to Inhibit Protection Switch (Method B)” on p. 255 “How to Inhibit an Ethernet Linear Protection Switch” on p. 256
User Manual
245
Working with Protection
How to view Single Protection Group Settings (Method A) This instruction describes how to view the protection settings for one single protection group.
Procedure Step 1
Select the relevant channel module that is used in a protection group.
Step 2
Either right-click the module and select Protection from the context sensitive menu that appears, or select Configuration->Protection from the Main Menu.
Step 3
Select which protection group to view, using the Protection Group drop-down list. This list contains the FFP-CH entities, and there is on entity for each end channel in the protection group. For example, FFP-CH-1-18-NE1 and FFP-CH-1-18-NW1 can be defined to be in a protection group. You can select either of these two here, meaning that the information about that protection group can be viewed by selecting either of the two FFP entities.
Step 4
246
To view all protection details that were entered during provisioning, read the top section of the Protection window. Note that the defined working AID is indicated here, while the status for each of the working and protection AIDs are shown in the Working AID and Protection AID sections.
Refresh the contents of this window when needed, using the Refresh button.
End of Procedure
How to View Single Protection Group Settings (Method B) This instruction describes how to view the protection settings for one single protection group. These settings are not editable from this window.
Procedure Step 1
Select one of the network side channels in a protection group from the Entities pane hierarchical list.
In response, the configured parameters for this channel are displayed.
The protection settings that were entered during provisioning are displayed in the Protection section. This section can be expanded or collapsed.
End of Procedure Each of the protection parameters are described in the FSP3000R7 Provisioning and Operations Manual.
User Manual
247
Working with Protection
How to View All Protection Group Settings This instruction describes how to view the protection settings for all protection groups in an NE at once.
Procedure Step 1
Select the NE from the Entities pane hierarchical list.
Step 2
From the Main Menu, select Configuration -> Protection Groups.
Step 3
Display the protection type that you wish to see protection groups for by selecting the relevant tab in the Protection Group window. The Protection Group window can display protection groups for the following protection types: • • •
channel protection channel group protection (versatile protection) Ethernet linear protection
The protection parameters are described in the FSP3000R7 Provisioning and Operations Manual. Step 4
This list is not updated automatically after it has been opened. To refresh the contents: Select the Refresh button.
Step 5
Print the protection groups list by selecting the Print button.
Step 6
Save the protection groups list to file by selecting the Save button.
Step 7
Close the Protection Groups window by selecting the Close button.
How to Make a Manual Protection Switch (Method A) This instruction describes how to issue manual protection switching commands using the Protection window. This instruction is not applicable for Ethernet linear protection.
PS
Note
For channel card protection: when ALS is enabled on the client port of the channel modules, the start time of the ALS will contribute to the protection switch time.
Procedure Step 1
Select the relevant channel module that is used in a protection group.
Step 2
Either right-click the module and select Protection from the context sensitive menu that appears, or select Configuration->Protection from the Main Menu.
Select the correct protection group, using the Protection Group drop-down list. If the Working AID or Protection AID has a selectable Modify button, this is the currently used AID.
User Manual
249
Working with Protection
Step 4
Select the Modify button of the currently used AID. In response the Modify window appears.
Step 5
Switch to the other AID by using the Protection Switch drop-down list and selecting the option Manual Switch.
Step 6
Apply the entry by selecting OK.
Step 7
Update the displayed information in the Protection window by selecting Refresh.
Step 8
Check the sections Working AID or Protection AID to see whether the switch took place.
Step 9
Close the Protection window by selecting Close.
How to Make a Manual Protection Switch (Method B) This instruction describes how to issue manual protection switching commands using the Operation tab. This instruction is not applicable for Ethernet linear protection.
PS
Note
For channel card protection: when ALS is enabled on the client port of the channel modules, the start time of the ALS will contribute to the protection switch time.
Procedure Step 1
Select one of the network side channels in a protection group from the Entities pane hierarchical list.
Use the Protection Switch drop-down list to issue the relevant command. • Manual Switch results in switching to the other path (working or protection). • Release Switch releases the manual setting.
Step 4
Select OK to apply the command, or Cancel to discard it.
End of Procedure
User Manual
251
Working with Protection
How to Make a Manual Ethernet Linear Protection Switch This instruction describes how to issue manual protection switching commands for Ethernet linear protection.
Procedure Step 1
Either right-click the NE where the protection module resides and select Flow Connections from the context sensitive menu that appears, or select Configuration->Flow Connections from the Main Menu.
Step 2
Select the Ethernet Linear Protection Group tab. In response, the Flow Connection window content changes.
In response the Ethernet Linear Protection Group Details window appears.
Step 5
Find out whether it is the working or protection path that is active by checking the Secondary States field In the Working AID or Protection AID section.
Step 6
Switch to the other AID by using the Protection Switch drop-down list in the active path’s section to select Manual Switch.
Step 7
Apply the entry by selecting Apply.
Step 8
Update the displayed information in the Protection window by selecting Refresh.
Step 9
Check the Secondary States fields in the sections Working AID or Protection AID to see whether the switch took place.
Step 10
Close the Ethernet Linear Protection window by selecting Close.
End of Procedure
User Manual
253
Working with Protection
How to Inhibit Protection Switch (Method A) This instruction describes how to inhibit a protection switch to the protection path using the Protection window.
Procedure Step 1
Select the relevant channel module that is used in a protection group.
Step 2
Either right-click the module and select Protection from the context sensitive menu that appears, or select Configuration->Protection from the Main Menu.
Step 3
Select the correct protection group, using the Protection Group drop-down list. If the Working AID or Protection AID has a selectable Modify button, this is the currently used AID.
Step 4
Select the Modify button of the currently used AID. In response the Modify window appears.
If you see the Inhibit Switch to PROTN drop-down list: Use the drop-down list to select: • Yes, which inhibits switching to the protection path. • No, which indicates normal protection operation If you see the Inhibit Switch to WKG drop-down list: Use the drop-down list to select: • •
Yes, which inhibits switching to the working path. No, which indicates normal working operation
Step 6
Select OK to apply the command, or Cancel to discard it.
Step 7
Update the displayed information in the Protection window by selecting Refresh.
Step 8
Check the sections Working AID or Protection AID to see whether the setting has been applied.
This instruction describes how to inhibit a protection switch to the protection path.
Procedure Step 1
Select one of the network side channels in a protection group from the Entities pane hierarchical list.
Such channels are named: CH---N|NE|NW. Step 2
In the Parameter pane, select the Operation tab. In response, the commands that can be issued are displayed.
User Manual
255
Working with Protection
Step 3
Select the Modify button. In response, the Modify Operation window appears.
Step 4
Use the Inhibit Switch to PROTN drop-down list to select: • Yes, which inhibits switching to the protection path. • No, which indicates normal protection operation
Step 5
Select OK to apply the command, or Cancel to discard it.
End of Procedure
This instruction describes how to inhibit a protection switch away from the currently active path for Ethernet linear protection.
Procedure Step 1
Either right-click the NE where the protection module resides and select Flow Connections from the context sensitive menu that appears, or select Configuration->Flow Connections from the Main Menu. In response, the Flow Connection window appears.
In response the Ethernet Linear Protection Group Details window appears.
Step 5
User Manual
Find out whether it is the working or protection path that is active by checking the Secondary States field In the Working AID or Protection AID section.
257
Working with Protection
Step 6
Inhibit protection switching to the other AID by using the Inhibit Switch to PROTN or Inhibit Switch to WKG drop-down list in the active path’s section to select Yes.
Step 7
Apply the entry by selecting Apply.
Step 8
Close the Ethernet Linear Protection window by selecting Close.
End of Procedure
How to Configure APS Hold-Off Time (Method A) This instruction describes how to configure the hold-off time between a protection switch trigger and the actual switching, using the Protection window.
Procedure Step 1
Select the relevant channel module that is used in a protection group.
Step 2
Either right-click the module and select Protection from the context sensitive menu that appears, or select Configuration->Protection from the Main Menu.
Step 3
258
Select the correct protection group, using the Protection Group drop-down list.
How to Configure APS Hold-Off Time (Method B) This instruction describes how to configure the hold-off time between a protection switch trigger and the actual switching, using the Config tab.
Procedure Step 1
Select one of the network side channels or virtual channels in a protection group from the Entities pane hierarchical list.
Step 2
In the Parameter pane, select the Config tab. In response, the configured parameters for this channel are displayed.
User Manual
259
How to Change the Administrative State
Step 3
Select the Modify button in the Protection section. In response the Modify window appears.
Step 4
Use the APS Hold-Off drop-down list to select the hold-off time. The option None means that no hold-off time will be used.
Step 5
Select OK to apply the command, or Cancel to discard it.
Step 6
Update the displayed information in the Protection section by selecting Refresh.
Step 7
Check the field APS Hold-Off to see whether the setting has been applied.
End of Procedure
This section describes how to change the administrative state for an entity.
Procedure Step 1
Select the NE in the Managed Elements pane.
Step 2
Select the relevant entity in the Entities pane.
Step 3
Select the State tab.
Step 4
Select Modify. In response the Modify window appears.
Step 5
260
Use the Admin State drop-down list to select the relevant administrative state option for the entity.
Option
Behavior
Abbreviation
In Service; alarms are reported Automatic In Service; alarms are not reported but service-affecting operations cannot be performed. Management; alarms are not reported, service affecting operations are allowed.
Maintenance; alarms are not reported, service affecting operations are allowed. Disabled; alarms are suppressed, service affecting operations are allowed.
out of service
MT
out of service
DSBLD
Step 6
Select OK to apply your change or Cancel to reject the changes.
End of Procedure
Configuring the OTDR The OTDR is configured using the separate OTDR application. For information about configuring the OTDR, please see the OTDR Installation, Provisioning, and Operations Manual. This section describes how to open the OTDR application.
Select the OTDR in the Entities pane. The OTDR is represented by the shelf entity SHELF-OTDR 8-OTDR3HU. In response the Equipment pane displays the OTDR.
User Manual
261
Viewing Node Channel Traces
Step 2
In the Equipment pane, select Open in browser.
Step 3
Consult the OTDR Installation, Provisioning, and Operations Manual for instructions on logging in to the OTDR application and using it.
End of Procedure
Viewing Node Channel Traces The FSP 3000R7 system supports NEs with multiple degrees, tunable lasers and filters, optical channel power control, channel switching, and directionless add/drop capabilities. Node channel trace determines the path that a service follows through a node, starting from a designated point. A service may be traced through the node at the wavelength level. Tracing a service through the node identifies the ports on modules that support that service, starting from the user-specified point to the other end-point. One or both of the service end points are Optical Lines (OL). The current performance monitoring (PM) values can also be displayed. Users can compare values to verify signal flow and to ensure that fibers are clean and properly connected. Service trace may be a single channel path for uni-directional channels or multiple channel paths for bi-directional, drop-and-continue, or multicast channels. This procedure describes how to view service traces in an NE.
If you wish to trace the channel path through an optical line, do as follows: • Select the Optical Line radio button. • Select the optical line that the channel passes through by using the Optical Line drop-down list. • Select the relevant channel carried on this optical line by using the Channel Number drop-down list. Continue from Step 4.
Step 3
User Manual
If you wish to trace the channel path from one port to another port, do as follows: • Select the Port radio button. • Select the port the channel originates from in the Port drop-down list.
263
Viewing Node Channel Traces
Step 4
In response the Node Channel Trace window displays the channel path in tabular form.
Column Name
Description
Id
Each uni-directional trace is represented by a different number, which is displayed in this field. This field shows the specific type of a channel path route. The following types are supported:
Route Type
From AID
•
Backplane
•
Cable
•
Equipment
•
Fiber
• Provisioned This field identifies the service trace’s source-point by its AID. •
If this is an optical line, also the channel number is displayed.
•
To AID
264
If this is a port, also the module equipment point displays. This field identifies the service trace’s source-point by its AID. •
If this is an optical line, also the channel number is displayed.
•
If this is a port, also the module equipment point displays.
The following information is provided in the node channel trace table.
Chapter 4 Configuring NEs
Step 5
If you want to view the measured optical power at the source and destination facilities of the channel, place a check mark in the Display Optical Power PM check box. This option is not selected by default because the retrieval of performance monitoring data can be a lengthy operation.
