Manualfsp 3000r7 Em

FSP 3000R7 Element Manager

User Manual

Product Release 10.3 Document Issue: B (July 2011)

Copyright © 2001-2011 ADVA Optical Networking All rights reserved. Hardware and software mentioned in this document includes software developed by ADVA Optical Networking ("ADVA Optical Networking"), the Apache Software Foundation (http://www.apache.org), Teodor Danciu (http://jasperreports.sourceforge.net), and/or other open source software. Some software was created using ORBacus for Java by Object-Oriented Concepts, Inc. Trademarks The terms “ADVA” and “FSP 3000” are trademarks or registered trademarks of ADVA Optical Networking in the United States, Germany and/or other countries. All other company products or services mentioned in this document may be trademarks or service marks of ADVA Optical Networking or their respective owner. Patents The content described in this document may be covered by patents or pending patent applications of ADVA Optical Networking. The furnishing of this document does not give you any license to these patents. Nothing in this document shall be construed as granting any license or rights with respect to its content or the patents and trademarks mentioned above. The content of this document may include technical inaccuracies or typographical errors, and is subject to change at any time without notice. Reliance on this content is at the relying party's sole risk and will not create any liability or obligation for ADVA Optical Networking. Any references in this document to publications and/or Internet sites that are not from ADVA Optical Networking are provided for convenience only and do not in any manner serve as an endorsement of those publications and/or Internet sites. The materials within those publications and/or Internet sites are not part of the materials for any ADVA Optical Networking information, product, or service, and use of those publications and/or Internet sites is at your own risk. THE CONTENT OF THIS DOCUMENT IS PROVIDED ''AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ADVA OPTICAL NETWORKING, ITS AFFILIATES, EMPLOYEES, OFFICERS OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND BASED ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE SAME APPLIES FOR ANY HARDWARE OR SOFTWARE COVERED BY THIS DOCUMENT, UNLESS A SIGNED AGREEMENT WITH ADVA OPTICAL NETWORKING OR THE APPLICABLE PRODUCT LIABILITY LAW EXPRESSLY STATES OTHERWISE. ADVA Optical Networking Fraunhoferstr. 9a 82152 Martinsried/Muenchen Germany Phone +49(0)89-890665-0 Fax +49(0)89-890665-199 http://www.advaoptical.com

2

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Disclaimers

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 List of Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Related Documents Overview. . . . . . . . . . . . . . . . . . . . 17

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Purpose and Scope . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . Document Revision History . . . . . . . . . . . . Organization . . . . . . . . . . . . . . . . . . . . . . Document Conventions . . . . . . . . . . . . . . . Typographic Conventions . . . . . . . . . . . Safety Symbol and Message Conventions Obtaining Documentation . . . . . . . . . . . . . Documentation Feedback. . . . . . . . . . . . . . Obtaining Technical Assistance . . . . . . . . . . Customer Portal . . . . . . . . . . . . . . . . . . Technical Support . . . . . . . . . . . . . . . . Contact ADVA Optical Networking . . . . . . . .

Chapter 1

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

21 21 21 22 24 24 26 27 27 27 28 28 29

Getting Started . . . . . . . . . . . . . . . . . . . . 31

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 . . . . . . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

46 51 52 53 55 56 56 57 57 58 59 59

Basics of the Element Manager. . . . . . . . 61

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Graphical User Interface . . . . . . . . . The Menu Bar . . . . . . . . . . . . . . . . . . . . . The Toolbar . . . . . . . . . . . . . . . . . . . . . . . The Network Element Pane . . . . . . . . . . . . The Information Pane . . . . . . . . . . . . . . . . The Entity Pane . . . . . . . . . . . . . . . . . . The Tree View . . . . . . . . . . . . . . . . The Racks View. . . . . . . . . . . . . . . . AID Names. . . . . . . . . . . . . . . . . . . Entity Position . . . . . . . . . . . . . . . . The Equipment Pane . . . . . . . . . . . . . . The Parameter Pane. . . . . . . . . . . . . . . Response Log . . . . . . . . . . . . . . . . . . . . . Status Bar . . . . . . . . . . . . . . . . . . . . . . . . Displaying Several NE Information Panes About Communicating with NEs . . . . . . . . . . . Getting Help. . . . . . . . . . . . . . . . . . . . . . . . . About Security . . . . . . . . . . . . . . . . . . . . . . . Security Levels . . . . . . . . . . . . . . . . . . . . Local Authentication . . . . . . . . . . . . . . . . . Centralized Authentication. . . . . . . . . . . . .

4

. . . . . . . . . . . .

............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ ............ Simultaneously . ............ ............ ............ ............ ............ ............

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

61 63 64 65 66 67 68 69 70 71 72 72 73 74 75 75 76 77 77 77 78 78

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Chapter 2

. . . . . . . . . . . .

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Chapter 3

Provisioning NEs . . . . . . . . . . . . . . . . . . . 81

About Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Equipment/Facilities Manually . . . . . . . . . . . . . . How to Create a Shelf . . . . . . . . . . . . . . . . . . . . . . . . How to Create an OTDR Shelf . . . . . . . . . . . . . . . . . . How to Create a Module . . . . . . . . . . . . . . . . . . . . . . How to Clone a Module . . . . . . . . . . . . . . . . . . . . . . . How to Create a Plug . . . . . . . . . . . . . . . . . . . . . . . . How to Create a Port . . . . . . . . . . . . . . . . . . . . . . . . How to Clone a Channel (Port). . . . . . . . . . . . . . . . . . How to Change a Service (Channel) . . . . . . . . . . . . . . How to Create a Virtual Channel . . . . . . . . . . . . . . . . How to Create an Ethernet Port (ETH) . . . . . . . . . . . . How to Create a Virtual Ethernet Port (VETH) . . . . . . . How to Create an EOC Channel . . . . . . . . . . . . . . . . . How to Create an SDH/SONET/OTN based ECC Channel How to Create an Ethernet based ECC Channel . . . . . . How to Create a PPP IP Interface . . . . . . . . . . . . . . . . How to Create a Supervisory Channel . . . . . . . . . . . . . How to Create an Optical Line . . . . . . . . . . . . . . . . . . How to Create Equipment/Facilities Automatically. . . . . . . Managing Encryption Modules . . . . . . . . . . . . . . . . . . . . Configuring Initial Settings . . . . . . . . . . . . . . . . . . . . How to Change the Crypto-Officer Password . . . . . . How to Specify the Module Authentication Password How to View the Key Exchange . . . . . . . . . . . . . . . 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 . . . Creating Protection Groups . . . . . . . . . . . . . . . . . . . . . . How to Create a Channel Protection Group . . . . . . . . . How to Create a Channel Card Protection Group . . . . .

User Manual

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . .

82 83 85 86 87 88 92 93 96 99 100 101 107 112 113 115 116 119 120 121 123 123 123 125 127 128 128 130 131 132 133 139 140 141 142 143 144 147

5

Chapter 4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

152 156 158 162 164 165 166 168 175 179 180 181 183 184 189 191 194 196 199 201 203 206 208 208 210 212 214 214 216 217

Configuring NEs . . . . . . . . . . . . . . . . . . 219

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

6

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

220 221 222 223 224 224 225

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Create a Client Channel Card Protection Group . . . . . . . How to Create a Virtual Channel Protection Group . . . . . . . . . . How to Create an Ethernet Linear Protection Group . . . . . . . . . How to Create a Versatile Protection Group . . . . . . . . . . . . . . . How to Delete a Protection Group . . . . . . . . . . . . . . . . . . . . . Creating ADM and ROADM Cross Connections . . . . . . . . . . . . . . . How to View ADM and ROADM Cross Connections . . . . . . . . . . How to Create an ADM or ROADM Cross Connection . . . . . . . . . How to Create a 1 Way ADM or ROADM Cross Connect Primitive How to Enable a ROADM Cross-connection . . . . . . . . . . . . . . . How to Delete a Bi-directional ADM or ROADM Cross Connection How to Delete 1 Way ADM or ROADM Cross Connect Primitives . Creating Flow Points, Bridges, and Cross Connections . . . . . . . . . . How to Create a Flow Point (FLW) . . . . . . . . . . . . . . . . . . . . . How to View Flow Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Create a Bridge (BRG) . . . . . . . . . . . . . . . . . . . . . . . . How to View Bridges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Create a Flow Cross Connection . . . . . . . . . . . . . . . . . How to Create a 1 Way Flow Cross Connect Primitive . . . . . . . . How to Delete a Bi-directional Flow Cross Connection . . . . . . . . How to Delete 1 Way Flow Cross Connect Primitives. . . . . . . . . How to View Flow Cross-connections . . . . . . . . . . . . . . . . . . . Creating DCN Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . How to Cross-connect PPP IP and EOC/ECC Interfaces . . . . . . . How to View ECC Channels . . . . . . . . . . . . . . . . . . . . . . . . . . How to Delete Equipment/Facilities Manually . . . . . . . . . . . . . . . . Handling Network Element User Accounts . . . . . . . . . . . . . . . . . . Adding a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying an User Account . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Configuring OSPF Areas . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring OSPF for the System Interface . . . . . . . . . . . . . Defining OSPF for Ethernet PPP IP/LAN IP Interfaces . . . . . . Assigning/Removing Static Routes . . . . . . . . . . . . . . . . . . . Assigning/Removing a Default Route . . . . . . . . . . . . . . . . . Assigning a Default Gateway via the IP Ethernet Interface . . Connecting the OSC and LAN IP Ethernet Interface . . . . . . . Configuring Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . Working with Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to view Single Protection Group Settings (Method A) . . . How to View Single Protection Group Settings (Method B). . . How to View All Protection Group Settings. . . . . . . . . . . . . . How to Make a Manual Protection Switch (Method A) . . . . . . How to Make a Manual Protection Switch (Method B) . . . . . . How to Make a Manual Ethernet Linear Protection Switch . . . How to Inhibit Protection Switch (Method A) . . . . . . . . . . . . How to Inhibit Protection Switch (Method B) . . . . . . . . . . . . How to Inhibit an Ethernet Linear Protection Switch . . . . . . . How to Configure APS Hold-Off Time (Method A) . . . . . . . . . How to Configure APS Hold-Off Time (Method B) . . . . . . . . . How to Change the Administrative State . . . . . . . . . . . . . . . . . Configuring the OTDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Node Channel Traces. . . . . . . . . . . . . . . . . . . . . . . . . Viewing Information About the NE . . . . . . . . . . . . . . . . . . . . . How to View System Information . . . . . . . . . . . . . . . . . . . . How to View Configured Parameters . . . . . . . . . . . . . . . . . . How to View Inventory for an Entity . . . . . . . . . . . . . . . . . . How to View Inventory for a NE . . . . . . . . . . . . . . . . . . . . . How to View Interface Information . . . . . . . . . . . . . . . . . . . How to View the Routing Table . . . . . . . . . . . . . . . . . . . . . How to View the OSPF Information. . . . . . . . . . . . . . . . . . . Configuring Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . How to Manually Set the Date, Time, and Time Zone . . . . Synchronizing NE time via NTP . . . . . . . . . . . . . . . . . . . How to Configure an NE for Client-Only or Relay Mode

User Manual

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

228 230 232 233 235 237 238 239 239 241 242 242 245 246 247 248 249 250 252 254 255 256 258 259 260 261 262 267 268 270 271 272 273 274 275 277 278 280 282

7

8

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

286 288 289 290 292 293 294 295 297 299 301 303 305 306 308 309 311 314 315 316 316 318 319 320 321 322 324 325 326 329 333 337 341 345 349 351 353 354 355

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Configure an NE for Server-Only Mode . . . . . . . . . . . . How to Check NE to Remote NTP Server Connectivity . . . . . . . How to Disable Time Synchronization with NTP. . . . . . . . . . . . Configuring Remote Syslog Servers . . . . . . . . . . . . . . . . . . . . . . . . . . How to Add a Remote Syslog Server . . . . . . . . . . . . . . . . . . . . . How to Edit a Remote Syslog Server . . . . . . . . . . . . . . . . . . . . . How to Delete a Remote Syslog Server . . . . . . . . . . . . . . . . . . . How To Configure Scheduled Equalization . . . . . . . . . . . . . . . . . . . . . . Configuring Span Equalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Provision Span Equalization in a New Network . . . . . . . . . How to Provision Span Equalization in an Existing Network . . . . . . How to Initiate Equalization . . . . . . . . . . . . . . . . . . . . . . . . . . . How to View the List of Qualified EDFAs . . . . . . . . . . . . . . . . . . . How to View Span Equalization Status, Alarms, and Configuration . How to Configure Span Equalization Options . . . . . . . . . . . . . . . . How to Change Qualified EDFA Set Point and PPC . . . . . . . . . . . . How to Change Qualified EDFA Gain. . . . . . . . . . . . . . . . . . . . . . How to Change Qualified EDFA Administrative State . . . . . . . . . . How to Enable/Disable Dynamic Equalization . . . . . . . . . . . . . . . Viewing and Configuring Trace Messages . . . . . . . . . . . . . . . . . . . . . . . How to View the Trace Messages . . . . . . . . . . . . . . . . . . . . . . . . . . How to Configure the Trace Messages. . . . . . . . . . . . . . . . . . . . . . . Configuring Settings for SDH/SONET Signals . . . . . . . . . . . . . . . Configuring Settings for OTN Signals . . . . . . . . . . . . . . . . . . . . . How to Configure TCA Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Configure Tandem Connection Monitoring . . . . . . . . . . . . . . . . . How to Store Optical Power Reference Values . . . . . . . . . . . . . . . . . . . Configuring Ethernet OAM/CFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Maintenance Domain (MD) . . . . . . . . . . . . . . . . . . . . Creating a Maintenance Association Network (MAnet) . . . . . . . . . Creating a Maintenance Association Component (MAcomp). . . . . . Creating a Maintenance End Point . . . . . . . . . . . . . . . . . . . . . . . Viewing and Modifying MAnet or MAcomp Configuration . . . . . . . . Viewing and Modifying MEP Configuration . . . . . . . . . . . . . . . . . . Deleting CFM Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Configure Loop-Backs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Cables in the Internal Database . . . . . . . . . . . . . . . . . . . . . . How to View Fibers in the Physical Connections Table . . . . . . . . . . . . How to Enter Fibers into the Physical Connections Table . . . . . . . . . .

Viewing Physical Termination Points . . . . . . . . . . How to Set the Automatic Laser Shutdown Mode . . . How to Force a Laser On . . . . . . . . . . . . . . . . . . . . How to Set the Forced-Laser Fallback/Release Timer. How to Allow Forced Deletion of Entities . . . . . . . . . Enabling Use of SCU Ring Interconnection . . . . . . . . How to Change Equipment Capabilities . . . . . . . . . . How to Configure TIF Contacts . . . . . . . . . . . . . . . .

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Chapter 5

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

357 358 360 362 363 363 364 365

Monitoring NEs . . . . . . . . . . . . . . . . . . . 369

Monitoring Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to View Current Conditions for a Single Entity or NE . . How to View Current Conditions for All Entities in an NE . . . How to View the Event Log . . . . . . . . . . . . . . . . . . . . . . . How to Manually Change an Individual Condition’s Severity. Changing Condition Severities with an Alarm Profile . . . . . . How to Modify the Alarm Profile. . . . . . . . . . . . . . . . . . How to Reset an Alarm Profile . . . . . . . . . . . . . . . . . . . How to Export an Alarm Profile . . . . . . . . . . . . . . . . . . How to Import a Alarm Profile . . . . . . . . . . . . . . . . . . . How to Set the Timer for the Fault Cause Persistency Filter . Monitoring Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . How to View Channel Performance per NE. . . . . . . . . . . . . How to View Single Channel Performance . . . . . . . . . . . . . How to View ROADM Performance . . . . . . . . . . . . . . . . . . How to View Reconfigurable Filter Performance . . . . . . . . . How to Reset Performance Records . . . . . . . . . . . . . . . . . How to Print Historic Performance Records . . . . . . . . . . . . How to Export Historic Performance Records . . . . . . . . . . . How to View Physical Layer Measurements . . . . . . . . . . . . How to View Optical Power Reference Values. . . . . . . . . . . How to View Thresholds for Threshold Crossing Alerts . . . . Monitoring States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to View States for an Entity . . . . . . . . . . . . . . . . . . . How to View States for an NE . . . . . . . . . . . . . . . . . . . . .

Chapter 6

. . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

369 370 372 374 375 377 377 380 381 383 386 388 389 390 392 395 398 399 400 400 401 402 403 403 404

Maintaining NEs . . . . . . . . . . . . . . . . . . 405

About Software and Database Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

User Manual

9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

406 408 409 409 411 411 413 415 419 421 423 425 428 429 432 434 435 435 436 437 441 448 448 453 458 458 459 459 460 461

Appendix A

Communication Port Overview . . . . . . . 463

Appendix B

Description of States . . . . . . . . . . . . . . 465

Administrative States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 Operational States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Secondary States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467

10

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The Software Package . . . . . . . . . . . . . . . . . . . . . . . . . Handling of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software and Database Compatibility . . . . . . . . . . . . . . . Software Downgrade and Switchback . . . . . . . . . . . . . . . NE Software Version versus File Names . . . . . . . . . . . . . Backing Up and Restoring the Database . . . . . . . . . . . . . . . How to Manually Back Up the Database . . . . . . . . . . . . . How to Set Up Scheduled Backup of the Database . . . . . . How to Restore the Database . . . . . . . . . . . . . . . . . . . . How to Enable Automatic Database Restoration . . . . . . . . Updating NE Software in a Network . . . . . . . . . . . . . . . . . . How to Install NE Software . . . . . . . . . . . . . . . . . . . . . . Activating the NE Software . . . . . . . . . . . . . . . . . . . . . . How to Schedule Activation of the NE Software . . . . . . How to Manually Activate the NE Software . . . . . . . . . Switching Back to Previous NE Software Version . . . . . . . Updating NE Software in a GNE-based Network . . . . . . . . . . Updating Firmware Packages in an NE. . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Update Firmware for a Single Module. . . . . . . . . . How to Update Firmware for Multiple Modules . . . . . . . . . Transferring Files To/From the NE. . . . . . . . . . . . . . . . . . . . How to Upload Files from the NE . . . . . . . . . . . . . . . . . . How to Download Files to the NE . . . . . . . . . . . . . . . . . . Rebooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rebooting the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-initiating a Module . . . . . . . . . . . . . . . . . . . . . . . . . . About FTP and SCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Move Files to an External Server . . . . . . . . . . . . . How to Move a Database Backup from an External Server.

Appendix C

RADIUS Authentication Setup . . . . . . . 471

Setting up RADIUS Authentication . . . . . . . . . . . . . . Defining RADIUS Servers. . . . . . . . . . . . . . . . . . . . . Enabling RADIUS Authentication . . . . . . . . . . . . . . . . Configuring SNMP Access Profiles . . . . . . . . . . . . . . . Adding a Default SNMP Access Profile . . . . . . . . . . Clearing a Default SNMP Access Profile . . . . . . . . . Adding an SNMP Access Profile for an IP Subnet . . Modifying an SNMP Access Profile for an IP Subnet. Removing an SNMP Access Profile for an IP Subnet Configuring IP Subnet Restrictions . . . . . . . . . . . . . . Adding a Restricted IP Subnet . . . . . . . . . . . . . . . Removing a Restricted IP Subnet . . . . . . . . . . . . . Enabling Restricted IP Subnets Access . . . . . . . . .

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Appendix D

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . .

472 472 475 476 476 478 479 482 484 486 486 488 489

Configuring a RADIUS Server . . . . . . . . 491

Installing and Starting a RADIUS Server . . . . Specifying Privilege Levels. . . . . . . . . . . . . . Modifying the Port for RADIUS Authentication Defining the Element Manager IP Addresses . Defining RADIUS User Accounts . . . . . . . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

492 493 494 495 495

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

User Manual

11

12

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

List of Figures Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure

1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31:

User Manual

Overview of SNMP Communication . . . . . . . . . . . . . . . . . . . Example of Element Manager Main Screen. . . . . . . . . . . . . . Context Sensitive Pop-up Menu . . . . . . . . . . . . . . . . . . . . . Overview of Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Network Element Pane Icons . . . . . . . . . . . . . . Example of the Information Pane, Default Layout . . . . . . . . . Example of the Information Pane, Alternative Layout . . . . . . Element Manager Entity Pane, Tree View. . . . . . . . . . . . . . . Entity Identification Examples . . . . . . . . . . . . . . . . . . . . . . Element Manager Entity Pane, Rack View . . . . . . . . . . . . . . Equipment Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of Parameter pane, Tab view . . . . . . . . . . . . . . . . . . Parameter Pane, List View . . . . . . . . . . . . . . . . . . . . . . . . . Response Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status Bar Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connections between NEs and Element Manager . . . . . . . . . User Accounts and Management Applications . . . . . . . . . . . . Routing Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Date and Time Window . . . . . . . . . . . . . . . . . . . . . . . . Span Equalization Linear Network Example: New Network. . . Span Equalization Linear Network Example: Existing Network Fiber Jumpers and Physical Termination Points . . . . . . . . . . Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Software and Database File Handling . . . . . . . . NE Software Update, First-time Activation . . . . . . . . . . . . . . Switchback to Previous NE Software and Database . . . . . . . . NE Software Activation Keeping Current Database . . . . . . . . NE Software Switchback With Auxiliary Database . . . . . . . . . GNE-based Network Example. . . . . . . . . . . . . . . . . . . . . . . FreeRadius Server Directory . . . . . . . . . . . . . . . . . . . . . . . Example of RADIUS Dictionary File . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

62 63 64 65 66 67 68 69 69 70 72 73 74 74 75 76 218 274 278 299 302 353 406 408 410 410 410 411 435 492 493

13

14

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

List of Tables Table Table Table Table Table Table Table Table Table Table Table Table

1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12:

User Manual

Entity AID Name Examples . . . . . . . . . . . . . . . . Example of AID addresses . . . . . . . . . . . . . . . . . Port Role/Port Mode versus IEEE Provider Bridge . Port Role/Port Mode versus IEEE Provider Bridge . Flow Point Parameters for all Port modes. . . . . . . Flow Point Parameters for Port mode CTAG . . . . . Flow Point Parameters for Port mode STAG . . . . . Bridge Parameters for all Port modes . . . . . . . . . Remote NTP Server Synchronization Status . . . . . Alarm Color Coding. . . . . . . . . . . . . . . . . . . . . . Communication Ports . . . . . . . . . . . . . . . . . . . . Element Manager versus RADIUS Privilege Levels

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. . . . . . . . . . . .

. 71 . 82 104 109 187 188 188 193 281 370 463 495

15

16

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

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.

18

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

•

TL-1 Maintenance and Troubleshooting Manual This document describes how to troubleshoot the FSP 3000R7 when managing it via TL-1.

•

OTDR Installation, Provisioning, and Operations Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This document covers installation, provisioning, operations, troubleshooting, and maintenance of the OTDR unit.

User Manual

19

20

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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

22

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Product Release

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.

Part Three

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

blue font

CAPITALIZED font courier [] | ^

24

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Typographic Conventions

Convention

Description

< >

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.

““ •

(bullet symbol)

1., 2., 3. ...or a., b., c. ... * or 1, 2 etc.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

->

User Manual

25

Document Conventions

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.

Note

26

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

CAUTION

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.

Documentation Feedback

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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]

28

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Technical Support

Contact ADVA Optical Networking ADVA Optical Networking Europe, Middle East and Africa Martinsried/Munich, Germany, +49 (0)89 89 06 65 0 [email protected] ADVA Optical Networking America Norcross, GA, USA, +1 687 728 8600 [email protected] ADVA Optical Networking Asia Shenzhen, China, +86 755 8621 7400 [email protected]

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

www.advaoptical.com

User Manual

29

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Contact ADVA Optical Networking

30

User Manual

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

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

32

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

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.

End of Procedure

34

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

b) Copy the files users.xml and em.lic to a safe location.

Chapter 1 Getting Started

Starting the Element Manager This instruction describes how to start the Element Manager in standalone mode.

Procedure Step 1

If you are starting the Element Manager in Windows: Select Start -> Programs -> FSP Element Manager 10_3_x -> FSP Element Manager.

Step 2

If you are starting the Element Manager in Unix: Type //runEm &

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Logon dialog appears.

Step 3

Enter a user name and a password. The default user account has administrator access rights, the user name ADMIN and the password CHGME.1.

User Manual

35

Starting the Element Manager

Step 4

Select Logon to continue. In response the Logon dialog displays information during the authentication period.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

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

User Manual

37

Initializing the Element Manager

management via the Managed Element pane. This allows you to keep a long list of NEs, without needing to connect to other ones than the ones you wish to manage at the moment. When the number of activated NEs is large, this results in a high memory consumption. Reducing the number of activated NEs reduces the memory consumption. When the memory consumption passes 90% of the memory allocated to the Element Manager, a warning window appears. The window will provide guidance on recovering from this situation. A warning message will also appear in the Response Log, and the Status bar memory indicator will turn red. There are two ways to add IP connections in the Element Manager. Either by adding a specific, known IP address or by letting the Element Manager discover all NEs in an address range. The latter is practical if you need to add several NEs. The NEs send traps using the NE’s system IP address as the trap sender identity. The Element Manager disregards traps with sender identities that do not match any of the NEs that it is connected to. Therefore, the Element Manager must connect to NEs using the NEs system IP addresses. The following topics are provided: “How to Add a Single IP Connection” on p. 39 “How to Discover all NEs in an IP Address Range” on p. 43 FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“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.

Procedure Step 1

From the Main Menu select File -> New.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

42

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Procedure Step 1

Select Configuration -> Managed Elements.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Managed Elements window opens.

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.

44

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Discovery window appears.

Chapter 1 Getting Started

Step 5

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-

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

covery window by clicking the

button.

Step 6

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

Exporting the list

Procedure Step 1

Select Configuration -> Managed Elements.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Managed Elements window opens.

46

User Manual

Chapter 1 Getting Started

Step 2

Select the

button, and the menu option Export.

In response, the Export Managed Elements window appears.

Step 3

Enter a new file name and file location into the relevant fields and select Save. Make a note of where you save the file so you can find it later.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

User Manual

47

Initializing the Element Manager

Importing the list

Procedure Step 1

Select Configuration -> Managed Elements.

Step 2

Select the

button, and the menu option Import.

In response, the Import Managed Elements wizard appears.

48

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Managed Elements window opens.

Chapter 1 Getting Started

Step 3

Select Browse to specify the location of the file you wish to import. In response the Import Managed Elements wizard content changes.

Step 4

Navigate to the file location and select the relevant file.

Step 5

Select Open.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Import Managed Elements wizard content changes.

User Manual

49

Initializing the Element Manager

Step 6

Select Next to continue. In response the Import Managed Elements wizard content changes.

Step 7

Specify which NEs you want to import by placing a check mark in the Import column.

Step 8

Select Finish to continue, or Cancel to cancel the import.

50

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

User Manual

Chapter 1 Getting Started

How to Modify IP Connections This instruction describes how to modify the connection settings for a managed NE.

Procedure Step 1

Select Configuration -> Managed Elements.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Managed Elements window opens.

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

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

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“The Delete Trap Recipient Window” on p. 56

User Manual

53

Initializing the Element Manager

Procedure Step 1

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.

54

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Trap Recipients window appears.

Chapter 1 Getting Started

Step 5

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

Select the Add button or Add button.

Step 2

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).

Step 2

Select Delete.

Step 3

Select Yes to delete or No to abort.

End of Procedure

56

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 3

Chapter 1 Getting Started

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the User Manager window appears.

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.

58

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 2

Chapter 1 Getting Started

Step 4

Select Close to finish.

End of Procedure

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Change Password window opens.

Step 2

Enter your present password to prove your identification, then enter your new password, and retype it.

Step 3

Select Change to apply the changes.

End of Procedure

User Manual

59

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Initializing the Element Manager

60

User Manual

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:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

62

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

NE 1

Chapter 2 Basics of the Element Manager

About the Graphical User Interface The Graphical User Interface (GUI) has various areas as shown in the illustration below.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 2: Managed

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.

64

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 3:

Chapter 2 Basics of the Element Manager

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

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

66

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 6:

Example of the Information Pane, Default Layout

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

68

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 7:

Chapter 2 Basics of the Element Manager

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.

click to expand FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

70

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 10:

Chapter 2 Basics of the Element Manager

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

Dependent Entity AID name

NE

SHELF FCU MOD FAN PL CH OM SC

SHELF MOD

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Entity AID Name Examples

PL CH

OM VCH

LINK

User Manual

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

72

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Source Description

74

Response Log

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Response Log

Chapter 2 Basics of the Element Manager

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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

76

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

NE 1

Chapter 2 Basics of the Element Manager

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.

About Security

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Centralized Authentication

Chapter 2 Basics of the Element Manager

•

one or more SNMP access profiles have been defined and installed on the Element Manager

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The administrator of the NE management should ensure these requirements are met for all users, see Appendix C: RADIUS Authentication Setup for instructions.

User Manual

79

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

About Security

80

User Manual

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

82

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Table 2:

Chapter 3 Provisioning NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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

84

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Chapter 3 Provisioning NEs

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:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

86

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

88

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

Chapter 3 Provisioning NEs

Step 3

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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. •

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 6

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--- 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.

92

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 1

Chapter 3 Provisioning NEs

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.

Step 8

Close the Provisioning Manager window by selecting Close.

End of Procedure

How to Create a Port This section describes how to create a port in the internal database, using the Provisioning Manager window. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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---- 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.

94

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 3

Chapter 3 Provisioning NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

User Manual

95

Creating Equipment/Facilities Manually

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.

96

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

Chapter 3 Provisioning NEs

Step 3

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 4

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.

End of Procedure

98

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Creating Equipment/Facilities Manually

Chapter 3 Provisioning NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Change Service wizard opens.

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---- 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

the parameters.

100

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 4

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----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

the parameters.

102

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Create port wizard starts.

Chapter 3 Provisioning NEs

Step 3

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Parameters Step 2 page appears.

User Manual

103

Creating Equipment/Facilities Manually

Step 4

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.

104

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Table 3:

Chapter 3 Provisioning NEs

Step 6

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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)

106

Go to Step 13.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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).

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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----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

the parameters.

108

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Table 4:

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

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.

110

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Select Next to continue.

Chapter 3 Provisioning NEs

Step 7

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

112

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements

Chapter 3 Provisioning NEs

Step 4

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

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.

114

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 3

Chapter 3 Provisioning NEs

Step 10

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

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.

116

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Chapter 3 Provisioning NEs

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 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).

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Creating Equipment/Facilities Manually

Chapter 3 Provisioning NEs

Step 5

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.

End of Procedure

How to Create a Supervisory Channel The supervisory channel (SC) entity supports the out of band optical supervisory (OSC) channel. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The Provisioning Manager window will display the Create Optical Line section on the right side.

Chapter 3 Provisioning NEs

Step 7

In the Entities pane, select the new OL entity. In response the Parameters pane displays the configuration information for the OL.

Step 8

Select Modify.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window opens.

Step 9

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.

End of Procedure

122

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

o

Note

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.

124

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

126

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Requirements FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

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.

128

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This section provides instructions for maintaining encryption modules. These subsections are covered:

Chapter 3 Provisioning NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 8

Enter the CO password in the Password field.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, all available information about the entitiy is displayed in the Parameter pane.

Chapter 3 Provisioning NEs

Step 9

Select OK to save your settings, or Cancel to cancel them.

End of Procedure

How to Reset the Key Exchange Fail Counter This instruction describes how to reset the counter of failed key exchanges. This is useful: •

When the key exchange process has failed three times and an attack can be excluded.

•

After self test.

Requirement Before resetting, ensure that no attacks caused the key exchange failure and that the module is operating correctly.

PS

You must not follow this instruction if an attack caused the encryption to stop.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Note

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).

131

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

From the Actions button, select Reset Key Exchange Fail Counter.

Step 7

Select Key Exchange Reset from the Key exchange fail reset 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

How to View the Key Exchange Fail Counter Follow this instruction to view the counter of failed key exchanges.

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.

132

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window appears.

Chapter 3 Provisioning NEs

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

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

How to Update the Encryption Module Firmware PS

Note

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the encryption related parameters of the module are displayed.

Chapter 3 Provisioning NEs

Step 10

From the Main Menu, select Configuration -> Software Control. In response, the Software Control start window is displayed.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 20

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.

End of Procedure

138

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 23

Chapter 3 Provisioning NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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. 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.

140

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window appears.

Chapter 3 Provisioning NEs

Step 4

Select the Monitoring tab.

Step 5

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements •

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.

Requirement Encryption is switched off.

142

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window appears.

Chapter 3 Provisioning NEs

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).

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

144

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements

Chapter 3 Provisioning NEs

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.

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Protection window appears.

Close the window by selecting Close. Step 14

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.

148

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

Chapter 3 Provisioning NEs

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 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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

150

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Protection window appears.

Close the window by selecting Close. Step 15

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.

Step 2

Select the relevant NE in the Entities pane.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements

Chapter 3 Provisioning NEs

Step 3

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Protection window appears.

Close the window by selecting Close. Step 15

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.

156

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 2

Select the relevant NE in the Entities pane.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 4

Select the Ethernet Linear Protection Groups tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

160

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 6

Chapter 3 Provisioning NEs

Step 7

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements

Chapter 3 Provisioning NEs

Step 5

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

User Manual

163

Creating Protection Groups

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.

Step 5

Close the Protection window by selecting Close.

End of Procedure

164

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Protection window appears.

Chapter 3 Provisioning NEs

Creating ADM and ROADM Cross Connections This section describes how to create Add-Drop Multiplexer (ADM) cross-connections and Re-configurable Optical Add-Drop Multiplexer (ROADM) cross-connections, and how to keep an overview of the cross connects on an individual NE. It assumes that the relevant modules are already correctly provisioned. ADM cross-connections are supported by the 4TCA-PC-4GU+4G-V channel module, while ROADM cross-connections are supported by the ROADM-C40/40/2-3HU-2DC shelf, the 8ROADM-C40/0/OPM module and the ROADM-C80/0/OPM module. 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. For example: One 1 way cross connect primitive from CH-1-20-C3 to VCH-1-20-NW3 and one 1 way cross connect primitive from VCH-1-20-NW3 to CH-1-20-C3 together form a bi-directional cross connection between CH-1-20-C3 and VCH-1-20-NW3. Each primitive must be created individually, and the Create Cross Connection wizard supports the user in doing this easily. The following topics are provided: FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“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.

Graphic symbol

Connection Direction Facility Type

166

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Cross Connections window appears.

Chapter 3 Provisioning NEs

Column Name

Description

Function

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.

State

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 2

Step 3

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.

Procedure Step 1

From the Configuration menu, select Cross Connections. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Cross Connections window appears.

168

User Manual

Chapter 3 Provisioning NEs

Step 2

Select the Create button. In response, the Create 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 CH or VCH facilities for.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

170

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response an informational window appears.

Step 8

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.

172

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Parameters Step 1 page appears.

Chapter 3 Provisioning NEs

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 17

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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

178

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 8

Select the Delete button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response a Warning window appears.

Step 9

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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----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.

Step 2

184

Select the Flow Point tab.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements

Chapter 3 Provisioning NEs

Step 3

Select Create. In response, the Create Flow Point window opens.

Step 4

Use the Equipment drop-down list to select which xPCA module to add a flow point to. Select Next to continue.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Parameters Step 1 page appears.

186

User Manual

Chapter 3 Provisioning NEs

Step 7

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.

CBS-RCV FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

CIR-TRMT

CBS-TRMT Shape Enablement Default EVC COS PM mode

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

User Manual

Step 1

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.

Connection State

CVIDs registered Port Role Alias

190

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 12

Select Close to finish viewing the flow points.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

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----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.

Step 2

Select the Bridges tab.

Step 3

Select Create.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Flow Connections window opens.

In response, the Create Bridge window opens.

192

User Manual

Chapter 3 Provisioning NEs

Step 4

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Parameters Step 1 page appears.

Step 6

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Complete page appears.

Chapter 3 Provisioning NEs

Step 5

In response the Flow Connections window is updated.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

196

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Flow Connections window appears.

Chapter 3 Provisioning NEs

Step 4

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 10

Close the Flow Connections window.

End of Procedure

198

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response an informational window appears.

Chapter 3 Provisioning NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Flow Connections window appears.

User Manual

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.

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.

200

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Requirement

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

202

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 2

Select the Flow Cross Connections tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Cross Connection Details window appears.

Chapter 3 Provisioning NEs

Step 13

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 16. Step 14

In the 1 WAY Cross Connection Primitives section, identify the 1 way cross connect primitive that you want to delete.

Step 15

Select the Delete button that belongs to the cross-connect primitive to delete.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, a warning window appears.

Step 16

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Flow Connections window appears.

Chapter 3 Provisioning NEs

Step 8

Go to Step 9.

Step 9

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Graphic symbol

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Chapter 3 Provisioning NEs

•

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.

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

210

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to View ECC Channels

Chapter 3 Provisioning NEs

Per NE

Procedure Step 1

Select any module in the NE in the Entities, Tree tab.

Step 2

From the Configuration menu, select ECC List. In response the ECC List window appears.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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,

212

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Chapter 3 Provisioning NEs

before deleting a non-ROADM cross-connection, ensure that the entities that are cross-connected do not have administrative state In Service.

Procedure Step 1

Select the relevant entity in the Entities pane.

Step 2

From the Main Menu, select Configuration -> Provisioning -> Delete. In response, the Delete window appears.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

214

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Handling Network Element User Accounts

Chapter 3 Provisioning NEs

Step 3

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 5

Select Close to close the User Manager window.

End of Procedure

218

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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

220

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“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.

Step 4

Select the Modify button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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. 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

224

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“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.

End of Procedure

How to Configure the System IP Address FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

If you selected Yes, a warning will be displayed.

Step 10

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.

Step 2

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

Step 6

Select Next.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

230

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Create OSPF Area window content changes.

Chapter 4 Configuring NEs

Procedure Step 1

Double-click the relevant NE in the Entities pane. In response, the Parameter pane displays.

Step 2

Select the OSPF tab in the Parameter pane.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

232

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This example shows the supervisory channel.

Chapter 4 Configuring NEs

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.

End of Procedure

Assigning/Removing Static Routes FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

234

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

Assigning a Default Gateway via the IP Ethernet Interface FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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).

Step 3

Select the Config tab in the Parameters pane.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Modify window displays.

Chapter 4 Configuring NEs

Step 4

Select Modify.

Step 5

Use the LAN-AID drop-down list to select the LAN IP Ethernet interface on the NCU to connect the OSC to. For example: LAN-1-A-1.

Step 6

Apply your setting by selecting OK or cancel them by selecting Cancel.

End of Procedure

Configuring Security

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

240

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 3

Chapter 4 Configuring NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Security Settings window appears.

Step 3

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.

242

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Security Settings window appears.

Chapter 4 Configuring NEs

Procedure Step 1

Select the relevant NE in the Entity pane.

Step 2

Select Configuration -> Security Settings from the main menu. In response the Security Settings window appears.

Step 3

Select the SSH Fingerprints tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

244

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

Working with Protection When channel, virtual channel, channel card or versatile protection has been provisioned, protection is active. You can view information about the current protection configuration at the entity level, or at the NE level. You can also operate the protection switch manually. The following topics are provided: “How to view Single Protection Group Settings (Method A)” on p. 246 “How to View Single Protection Group Settings (Method B)” on p. 247 “How to View All Protection Group Settings” on p. 248 “How to Make a Manual Protection Switch (Method A)” on p. 249 FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Protection window appears.

Chapter 4 Configuring NEs

Step 5

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.

Such channels are named: CH---N|NE|NW. Step 2

In the Parameter pane, select the Config tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

End of Procedure

248

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Protection Group window appears.

Chapter 4 Configuring NEs

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Protection window appears.

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.

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.

Such channels are named: CH---N|NE|NW.

250

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Chapter 4 Configuring NEs

Step 2

In the Parameter pane, select the Operation tab. In response, the commands that can be issued are displayed.

Select the Modify button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Modify Operation window appears.

Step 3

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.

252

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Flow Connection window appears.

Chapter 4 Configuring NEs

Step 3

If necessary use the Equipment, Port, SVID From and SVID To fields in the Filter section to filter the display of Ethernet linear protection groups.

Step 4

Right-click the correct Ethernet linear protection group in the table and select Details from the context sensitive menu that appears.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

254

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Protection window appears.

Chapter 4 Configuring NEs

Step 5

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.

Step 9

Close the Protection window by selecting Close.

End of Procedure

How to Inhibit Protection Switch (Method B) FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

256

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Inhibit an Ethernet Linear Protection Switch

Chapter 4 Configuring NEs

Step 2

Select the Ethernet Linear Protection Group tab. In response, the Flow Connection window content changes.

Step 3

If necessary use the Equipment, Port, SVID From and SVID To fields in the Filter section to filter the display of Ethernet linear protection groups.

Step 4

Right-click the correct Ethernet linear protection group in the table and select Details from the context sensitive menu that appears.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Protection window appears.

Chapter 4 Configuring NEs

Step 4

Select the Modify button in the top section. In response the Modify window appears.

Step 5

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 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 field APS Hold-Off to see whether the setting has been applied.

Step 9

Close the Protection window by selecting Close.

End of Procedure

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

in service out of service

IS AINS

out of service

MGT

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Change the Administrative State

Chapter 4 Configuring NEs

Option

Behavior

Abbreviation

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.

Procedure FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 1

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.

262

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response a browser opens, displaying the login window for the OTDR application.

Chapter 4 Configuring NEs

Procedure Step 1

From the main menu, select Node Channel Trace. In response, the Node Channel Trace window opens.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 2

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.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Node Channel Trace window table changes.

The following additional information is provided in the node channel

User Manual

265

Viewing Node Channel Traces

trace table:. Column Name

Description

Tx (a/ppc) [dBm]

This column shows the transmitted optical power measured at the trace’s source-point. The following values can be shown: •

/, where signifies the aggregate, or total, power at the transmission port and signifies the power per-channel, or optical power, for a particular service.

•

n/a, which indicates that an error has

occurred. Either the facility is provisioned but not equipped, or a Loss of Signal (LOS) alarm is raised against the port.

Rx (a/ppc) [dBm]

no value, which indicates that the port or OL does not support performance monitoring. This column shows the received optical power measured at the trace’s destination-point or optical line. The following values can be shown: •

/, where signifies the aggregate, or total power at the transmission port and signifies the power per-channel, or optical power, for a particular service.

•

n/a, which indicates that an error has

occurred. Either the facility is provisioned but not equipped, or a Loss of Signal (LOS) alarm is raised against the port. •

266

no value, which indicates that the port or OL does not support performance monitoring.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

Chapter 4 Configuring NEs

Step 6

To see a graphical view of the channel path, select the Graph tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Node Channel Trace window displays a graph instead of a table.

Step 7

To refresh the content of the table or graph, select Refresh.

Step 8

When you are finished, select Close to close the Node Channel Trace window.

End of Procedure

Viewing Information About the NE This section collects all instructions for viewing information about the entities in the NE. The following topics are provided: “How to View System Information” on p. 268 “How to View Configured Parameters” on p. 270 “How to View Inventory for an Entity” on p. 271 “How to View Inventory for a NE” on p. 272 “How to View Interface Information” on p. 273 “How to View the Routing Table” on p. 274 “How to View the OSPF Information” on p. 275

User Manual

267

Viewing Information About the NE

How to View System Information This instruction describes how to view system information for the NE.

Procedure Step 1

Double-click the relevant NE in the Managed Elements pane.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Parameter pane displays.

268

User Manual

Chapter 4 Configuring NEs

Step 2

Select the System tab in the Parameters pane. In response, all available information about the entity is displayed in the Parameters pane.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The following information is provided. Field Name

Description

NE SW Version

This shows the name of the SW package file that is currently running. This field is user configurable and shows the NE’s name. This field shows that the NE is WDM type equipment. This shows the product name of the NE. This field shows the manufacturer of the NE. This shows the grade of the NE. This field is user configurable, it shows what kind of configuration the node is defined to work in. For example, as a optical add drop multiplexer. The options are: o Optical terminal multiplexer node o Optical add drop multiplexer node o Optical converter node o In line amplification node o Hub node This field is user configurable and shows the size of the rack, in Height Units (HU). One HU is 44.45 mm. This field is a user-configurable system identification text for the NE. The default value is “FSP3000”. This field is user configurable and shows the location that the NE is installed at. This field is user configurable and shows the contact person that has been defined for the NE.

NE Name Network Element Type Model Manufacturer name Grade Traffic Config

Size of the Rack

System ID

System Location System Contact

User Manual

269

Viewing Information About the NE

Field Name

Description

Alarm Activation Time

The Fault Cause Persistency filter raises alarms only after being present for a configurable amount of time (Alarm Activation Time). The Fault Cause Persistency filter clears alarms after they are gone for the configured amount of time (Alarm Deactivation Time).

Alarm Deactivation Time

End of Procedure

How to View Configured Parameters This instruction describes how to view parameters that have been configured for the NE.

Procedure Step 1

Double-click the relevant NE in the Managed Elements pane.

Step 2

Select the entity to view parameters for it 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.

The parameters that are displayed in this tab depend on the entity you selected. See the document Management Data Guide for descriptions of all parameters that may be displayed for the selected module type and all its dependent entities.

End of Procedure

270

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Parameter pane displays.

Chapter 4 Configuring NEs

How to View Inventory for an Entity This instruction describes how to view the inventory information for a single piece of equipment.

Procedure Step 1

Select the relevant shelf, module or pluggable transceiver from the Entities pane hierarchical list.

Step 2

In the Parameter pane, select the Inventory tab. In response, the inventory information is displayed.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The following fields are used in the Inventory table: . Field Name CLEI Code FW Package Revision

Official Name Serial Number uCM Revision FPGA Revision Hardware Revision Part Number Vendor Code

Description. Shows the Common Language Equipment Identifier (CLEI) for this equipment. The revision number of the firmware package (FWP) that this equipment is using. The firmware package contains both software for the network element and equipment firmware for each module. The revision numbers for each of these can be found in the software and database control page of the management tools The name of the equipment. The equipment’s serial number. This field is not relevant for all modules. It shows the revision for the micro-controller software. This field is not relevant for all modules. It shows the revision for the FPGA. The revision of the equipment’s hardware. The ADVA part number for this equipment. This field is only relevant for SFP Transceivers. It shows the name of the vendor for the equipment.

End of Procedure

User Manual

271

Viewing Information About the NE

How to View Inventory for a NE This instruction describes how to view the inventory information for a whole NE.

Procedure Step 1

Select the relevant NE from the Entities pane hierarchical list.

Step 2

From the Main Menu, select Configuration -> Inventory List.

Each of the inventory items are described in “How to View Inventory for an Entity” on p. 271. Step 3

Use the Equipment Category drop-down list to filter the display of items in the Inventory List window.

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 list by selecting the Print button.

Step 6

Save the list to file by selecting the Save button.

Step 7

Close the Inventory List window by selecting the Close button.

End of Procedure

272

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Inventory List window appears.

Chapter 4 Configuring NEs

How to View Interface Information This instruction describes how to view information about channel module interfaces.

Procedure Step 1

Select the relevant module from the Entities pane hierarchical list.

Step 2

In the Parameter pane, select the Info tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, information about the interfaces on this module is displayed.

Step 3

This list is not updated automatically after it has been opened. To refresh the contents: Select the Refresh button.

End of Procedure

User Manual

273

Viewing Information About the NE

How to View the Routing Table This instruction describes how to view the routing table for the NE. The routing table can display both the currently active routes and the inactive routes. It is not possible to define or delete routes with the Element Manager. The routing table is shown in Figure 18. Figure 18:

Routing Table

Column Name

Description

Destination

This column shows the IP address for the destination of the route.For a network route, the Destination is the IP subnet ID and the Mask is the IP subnet mask. For a host route, the Destination is a single IP address, and the Mask is 255.255.255.255. The entry 0.0.0.0 is the default route. This column show the gateway that is used to reach the Destination IP address. This column shows the mask for the Destination IP address. This column shows the type of route. The possible types are Local, Static, or OSPF. The local route is the route the NE uses when reaching addresses in the same subnet as the NE itself. For a local route there is no gateway. Static and OSPF routes are set so the NE can reach addresses outside the NE’s subnet. Static routes are added manually, while OSPF routes are added by the OSPF protocol. This column shows the metric value for the route. The higher the metric value, the less priority this route has over other routes. This column shows which IP interface that the gateway is reachable over.

Gateway Mask Routing Type

Metric

Device

274

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The following information is provided.

Chapter 4 Configuring NEs

To open the routing table:

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.

Step 2

Select the Routing Table tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the active routes are displayed in the Routing pane.

Step 3

To display the inactive routes, expand the Inactive Routes section.

Step 4

Select the Refresh button to update the window contents.

End of Procedure

How to View the OSPF Information This instruction describes how to view the routing table for the NE. It is not possible to define routes with Element Manager.

Procedure Step 1

Double-click the relevant NE in the Managed Elements pane. In response, the Parameter pane displays.

User Manual

275

Viewing Information About the NE

Step 2

Select the OSPF tab in the Parameters pane.

The following information is provided. Field Name

Description

Area ID

This reduces the resources needed for the OSPF calculation by segmenting the routing domain into areas where routing information is exchanged (routing information exchange between areas is limited). This field shows how the routes shall be redistributed. The option Static means that static routes are redistributed using OSPF. The option None means that static routes will not be distributed using OSPF. This is the initial default value. This field shows whether the OSPF area is a normal area or a stub area. This field shows the OSPF cost for any stub areas.

Route Redistribution

Area Type Stub Default Route Cost Step 3

To view which interfaces use an OSPF area, select that OSPF area in the OSPF Areas list and toggle the Config button to display the information about that OSPF area.

Step 4

Select the Refresh button to update the window contents.

End of Procedure

276

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, all available information about the entity is displayed in the Parameters pane.

Chapter 4 Configuring NEs

Configuring Date and Time This section describes how to manually set the time, date and time zone of the NE, and to synchronize NE time using the Network Time Protocol (NTP).

PS

Note

Features such as scheduled equalization of ROADMs cannot take place unless NTP synchronization is configured and enabled for the NE.

Any action which changes the date and time will result in an entry in the event log. The entry will indicate whether the change was due to a manual change (including the user account that made the change), due to an NTP step correction, or due to a daylight saving time action. Changes to the date and time of the NE, either directly, via the time zone, or via changes to the NTP configuration, should preferably be done when commissioning the system.

PS

Any action which changes the date and time may affect the performance records in an already operating system.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Note

The intervals of the performance records that were being gathered when the time was changed, will be incomplete and therefore those performance records will be marked as invalid. Moreover, if the time is set back in an already operating system, you end up with multiple performance records with the same timestamp. To avoid confusion, it is best to retrieve already collected performance records from the NE prior to changing the time. For your convenience, multiple performance records with identical timestamps will still be listed chronologically, i.e. in the order they were gathered.

User Manual

277

Configuring Date and Time

All configuration for date, time, time zone, and NTP time synchronization is done in the Date and Time window. The Date and Time Window

The Time Settings section shows the current date, time, and time zone settings. The NTP Servers section shows the IP addresses for the remote NTP servers that are defined. The following procedures are provided: •

“How to Manually Set the Date, Time, and Time Zone” on p. 278.

•

“Synchronizing NE time via NTP” on p. 280.

How to Manually Set the Date, Time, and Time Zone This procedure describes how to manually set the time, date, and time zone of the NE.

PS

Note

When the NE is configured to operate as an NTP client (i.e. NTP Mode is set to Client-Only or Relay), then the time will be synchronized via NTP and it is not possible to set the time or date manually for this NE. However, the time zone can always be changed.

Requirements

278

•

Before making changes to the date, time, time zone, or NTP configuration in an already operating system, it is suggested that you retrieve your performance record history from the NE. Collect all performance records and store them in a safe place before following this procedure. Use the FSP 3000R7 Element Manager or the Network Manager to collect performance records.

•

You must be logged on with a user account which has ADMIN privileges.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 19:

Chapter 4 Configuring NEs

Procedure Step 1

Select the NE in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration->Date and Time. In response the Date and Time window appears.

Step 3

If the NTP Service Mode field is Client Only or Relay, do as follows: a) Change the field to NTP Disabled. One cannot set the date or time manually when time synchronization with a remote server using NTP is configured (the NTP service mode is Client Only or Relay). b) Select OK to apply the change, or Cancel to cancel it.

Step 4

To change the NE time, select Modify from the Time Settings section.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window appears.

Step 5

If relevant, enter the correct date in the Date field, using the syntax yyyy-mm-dd, or click the selection.

button to display a calendar for easy date

Step 6

If relevant, enter the correct time in the Time field, using the syntax hh:mm:ss and 24 hour time.

Step 7

Select a time zone from the Time Zone drop-down list. The time zone options are named after country names, city names, or simply “GMT+”, where offset is the desired offset from GMT. GMT+x represents a time zone west of Greenwich and GMT-x represents a time zone on the east side of Greenwich. Only some time-zone options contain info about Daylight Saving Time. This is indicated by the Daylight Savings Time field after applying the time zone.

Step 8

Select OK to apply the new settings.

Step 9

Ensure that your time zone settings are correct. If you entered a country or city, the resulting offset from GMT will be displayed in the Time Zone Offset field. Whether the time zone contains information about daylight saving time or not will be indicated in the Daylight Savings Time field. The Daylight Savings Time field does however not indicate whether Daylight Saving Time is currently in effect or not.

User Manual

279

Configuring Date and Time

Step 10

Select Close to close the Date and Time window.

End of Procedure

Synchronizing NE time via NTP The Network Time Protocol (NTP) is a standard protocol for distributing accurate time around a computer network. It operates hierarchically, where each level is termed a stratum and is assigned a number. The numbering starts with zero at the top (i.e. the lowest stratum). The most accurate servers have the lowest stratum numbers. Each system at a certain level obtains the time from its peers at the same or some lower stratum. This means that time can be distributed without overloading one single reference. It is common practice in carrier and enterprise networks to synchronize all the system clocks via NTP.

•

Client Only mode. The NE will operate as an NTP client and receive its timing information from some remote NTP server.

•

Relay mode. The NE will operate as an NTP client, receiving its timing information from some remote NTP server, and will simultaneously operate as an NTP server, distributing time to other NTP clients. NEs operating as NTP clients can therefore configure this NE as their remote NTP server. This mode is typically used for a gateway NE, receiving time information from a remote NTP server in the external network, and distributing it further to the NEs in the internal network.

•

Server Only mode. The NE will operate as an NTP server, distributing time to NTP clients. NEs operating as NTP clients can therefore configure this NE as their remote NTP server. In this mode, the NE receives its time information from the local hardware clock. Date, time, and time zone must therefore be set manually for this NE.

Because the local hardware clock of the NE is not very precise, only use Server Only mode if no other remote NTP servers (with a precise clock) are available, or use it as a back-up in case such more precise remote NTP servers fail. When used as a back-up, any other remote NTP server will be prioritized over an FSP 3000R7 NTP server, as the latter's stratum is set to the highest possible value.

PS

Note

280

If Server Only mode is used, maximally one NE in the network should be set to server-only mode, and all other nodes in the network should point to this node as their remote NTP server.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The following modes of operation are supported:

Chapter 4 Configuring NEs

When time synchronization via NTP is enabled, the NE listens on UDP port 123 (regardless of whether the NE is configured in Client Only, Server Only or Relay mode). When NTP is not enabled, the NE does not listen on UDP port 123.

PS

UDP port 123 will appear “open” to port scanning applications when use of NTP is enabled.

Note

The synchronization status for remote NTP servers is described in Table 9. Table 9:

Status Message

Description

No Data

This means that no contact whatsoever has been established with the remote peer. This will for example appear if the IP address of a host without NTP server capabilities was entered, or if the remote NTP server is not reachable via the DCN. This means that packets have been sent to the remote peer, and the time-out to receive packets in response has not been exceeded yet.. This means that the remote NTP server has been discarded as invalid by the sanity test algorithm (for example because the remote NTP server is sending packets with an invalid header or stratum). This means that the remote NTP server has not been retained by the Clock Select Algorithm as a truechimer. This means that the remote NTP server has been retained by the Clock Cluster Algorithm and its clock info is used by the Combine Algorithm to calculate corrections to the local clock. This means that the remote NTP server is selected as the system peer (there can be only 1 system peer at any given time). This means that in Relay mode the local NTP server will inherit system statistics from this remote NTP server to pass along to any dependent NTP client. This system peer selection takes place even if the local NE is operating in Client Only mode. It may be normal for this system peer selection to change over time, especially if multiple remote NTP servers are of similar quality.

In Progress

Discarded FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Remote NTP Server Synchronization Status

False Ticker1 Candidate

System Peer

1. A truechimer is a clock that maintains timekeeping accuracy to a previously published (and trusted) standard, while a falseticker is a clock that does not

User Manual

281

Configuring Date and Time

This section describes how to configure the use of NTP on an NE. The procedures apply to both first-time configuration and later changes. The following sections are provided: “How to Configure an NE for Client-Only or Relay Mode” on p. 282 “How to Configure an NE for Server-Only Mode” on p. 286 “How to Check NE to Remote NTP Server Connectivity” on p. 288 “How to Disable Time Synchronization with NTP” on p. 289

How to Configure an NE for Client-Only or Relay Mode This instruction describes the following aspects of NTP configuration: •

How to configure an NE to operate in Client-only mode or in Relay mode. This involves ensuring that at least one remote NTP server that is reachable for the NE is configured correctly and enabled.

•

How to check that the NE can reach the configured remote NTP server(s)

•

How to check the status of synchronization with a remote NTP server.

282

•

Before making changes to the date, time, time zone, or NTP configuration in an already operating system, it is suggested that you retrieve your performance record history from the NE. Collect all performance records and store them in a safe place before following this procedure. Use the FSP 3000R7 Element Manager or the Network Manager to collect performance records.

•

You must know the IP addresses of the remote NTP servers that shall be used. For an NE operating as an NTP client, another NE which is operating as an NTP server can be configured as (one of the) remote NTP servers.

•

You must be logged on with a user account which has ADMIN privileges.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements

Chapter 4 Configuring NEs

Procedure Step 1

Select the NE in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration->Date and Time.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Date and Time window appears.

Step 3

PS

Note

Check in the NTP Servers list whether the correct NTP servers have already been configured. Up to three remote NTP servers can be configured. The NTP protocol contains multiple mechanisms for an NTP client to automatically determine which NTP servers provide the best quality time information. Overruling this automatic prioritization is not supported on the Element Manager. Neither does the order in the list of configured remote NTP servers imply any such priority. For each listed remote NTP server the following information is displayed:

Field Name

Description

IP Address

This column lists the IP addresses of the configured remote NTP servers. This column shows which IP address the NE uses in the source field of the IP header when communicating with the remote NTP server. This column shows whether the remote NTP server is enabled (Admin State = IS) or not. This column shows the status of the last synchronization with the remote NTP server. The options are shown in Table 9.

Own IP

Admin State Synchronization State

User Manual

283

Configuring Date and Time

Step 4

If the required remote NTP servers are in the list, go to Step 8. If the required remote NTP server has not been configured, or has been configured but not enabled, take appropriate action.

To:

Then:

add a new remote NTP server delete an existing remote NTP server enable an existing remote NTP server

Go to Step 5 Go to Step 6 Go to Step 7

Step 5

If relevant, add another remote NTP server by selecting Add. It is not possible to add another remote NTP server if three servers already have been configured. You must then delete a remote NTP server from the list first (see Step 6).

a) Enter the IP address for the remote NTP server in the IP Address field. b) When the NE communicates with the NTP server, it identifies itself with its IP address. In a bi-directional IP communication the two IP hosts involved need to be able to reach each other. Because 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 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: • 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

284

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Enter the following settings for the new remote NTP server:

Chapter 4 Configuring NEs

c) The new remote NTP server is enabled for use by default. This can be seen by the entry In Service in the Admin State field. The remote NTP server will not be used for synchronization unless it is In Service. d) Select OK to apply your entries, or Cancel to cancel them. In response to OK, the new remote NTP server will be displayed in the NTP servers list in the Date and Time window. e) Check that the NE can reach this remote NTP server, see “How to Check NE to Remote NTP Server Connectivity” on p. 288. f) Step 6

Go to Step 8.

If relevant, delete an already configured remote NTP server. Do as follows: a) Select the remote NTP server in the NTP Servers list in the Date andTime window.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

b) Disable the remote NTP server by setting the administrative state to Disabled. This setting is available when you select the Modify button in the NTP Servers list.

c) Delete the remote NTP server with the Delete button in the Date and Time window. You will be requested to confirm the deletion. d) Check that the deleted remote NTP server no longer is displayed in the NTP servers list in the Date and Time window. e) Go to Step 4. Step 7

If relevant, enable an already configured remote NTP server. Do as follows: a) Select the remote NTP server in the NTP list in the Date and Time window. b) Enable the remote NTP server by setting the Admin State to In Service. This setting is available when you select the Modify button in the NTP Servers list.

c) Select Check NTP Server(s) to check that the NE can reach this remote NTP server (see also “How to Check NE to Remote NTP Server Connectivity” on p. 288).

User Manual

285

Configuring Date and Time

Step 8

If the NTP Service Mode field is not already set to Client Only or Relay, do as follows: a) Select Modify from the Time Settings section. In response the Modify window appears. b) Change the NTP Service Mode field to Client Only or Relay. c) Select OK to apply the change.

Step 9

Look in the NTP Servers list and ensure that the NTP synchronization status is satisfactory (this may take a while).

Step 10

Set the time zone for this NE as described in “How to Manually Set the Date, Time, and Time Zone” on p. 278.

Step 11

Close the Date and Time window.

End of Procedure

How to Configure an NE for Server-Only Mode

Requirements

286

•

Before making changes to the date, time, time zone, or NTP configuration in an already operating system, it is suggested that you retrieve your performance record history from the NE. Collect all performance records and store them in a safe place before following this procedure. Use the FSP 3000R7 Element Manager or the Network Manager to collect performance records.

•

You must be logged on with a user account which has ADMIN privileges.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This instruction describes how to configure an NE to operate in Server-only mode. In this mode the NE receives its time information from the local hardware clock. Date, time, and time zone must therefore be set manually for this NE.

Chapter 4 Configuring NEs

Procedure Step 1

Select the NE in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration->Date and Time.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Date and Time window appears.

Step 3

Set the NTP Service Mode field to NTP Disabled, do as follows: a) Select Modify from the Time Settings section. In response the Modify window appears.

b) Change the NTP Service Mode field to NTP Disabled. c) Select OK to apply the change,or Cancel to cancel it. Step 4

User Manual

Set the date, time, and time zone for this NE manually as described in “How to Manually Set the Date, Time, and Time Zone” on p. 278.

287

Configuring Date and Time

Step 5

Set the NTP Service Mode field to NTP Disabled, do as follows: a) Select Modify from the Time Settings section. In response the Modify window appears.

b) Change the NTP Service Mode field to Server Only. c) Select OK to apply the change,or Cancel to cancel it. Step 6

Close the Date and Time window.

End of Procedure

This instruction describes how to check that the NE can reach the remote NTP servers that have been configured. It also describes how to find information about the synchronization status for each configure remote NTP server.

Requirements •

You must be logged on with a user account which has ADMIN privileges.

Procedure Step 1

Select the NE in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration->Date and Time. In response the Date and Time window appears.

288

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Check NE to Remote NTP Server Connectivity

Chapter 4 Configuring NEs

Step 3

In the NTP Servers list, select the remote NTP servers that you want to check whether the NE can reach. You can select a single server or mulitple servers.

Step 4

Select Check NTP Server(s). In response the check begins.

Step 5 Step 6

The status of the ongoing checking process as well as the result of it is displayed in the Last Check Status column of the NTP Servers list. Read the result of the check in the Last Check Status column of the NTP Servers list.

This column shows the status of the last check of NE to remote NTP server connectivity. The possible values are: In Progress, Success, Failure, and Idle. Idle indicates that no check has been done since the last reboot of the NE. Step 7

Close the Date and Time window.

End of Procedure

How to Disable Time Synchronization with NTP This instruction describes how to disable time synchronization with NTP. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Features such as scheduled equalization of ROADMs can not take place unless NTP synchronization is configured and enabled for the NE.

Requirements

User Manual

•

Before making changes to the date, time, time zone, or NTP configuration in an already operating system, it is suggested that you retrieve your performance record history from the NE. Collect all performance records and store them in a safe place before following this procedure. Use the FSP 3000R7 Element Manager or the Network Manager to collect performance records.

•

You must be logged on with a user account which has ADMIN privileges.

289

Configuring Remote Syslog Servers

Procedure Step 1

Select the NE in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration->Date and Time.

Step 3

Select Modify from the Time Settings section. In response the Modify window appears.

Step 4

Change the NTP Service Mode field to NTP Disabled.

Step 5

Select OK to apply the change, or Cancel to cancel it.

Step 6

If relevant, adjust the current date, time, and time zone as described in “How to Manually Set the Date, Time, and Time Zone” on p. 278.

Step 7

Close the Date and Time window.

End of Procedure

Configuring Remote Syslog Servers Syslog is a protocol that allows one system to send event notification messages to another system that stores them. The system that stores them is known as a syslog server, or daemon. The following characterizes the support of syslog in the FSP3000R7:

290

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Date and Time window appears.

Chapter 4 Configuring NEs

•

Syslog messages are transported in UDP (User Datagram Protocol) segments encapsulated in IP (Internet Protocol) packets, and are received on UDP port 514 of the server. Syslog over TLS is not supported.

•

Up to three remote syslog servers (to which the NE will send syslog messages) can be configured.

•

All events listed in the Event Log will also be sent to remote syslog servers, if any are configured, with the exception of events with severity Not Reported. Optionally database change messages may be excepted as well, this is configurable per syslog server.

It is possible to add, delete, enable and disable remote syslog servers. It is also possible to enable or disable sending of database change messages to a remote syslog server. It is not possible to modify the IP address of a configured syslog server. Instead the syslog destination must be deleted and a new one added.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The syslog protocol features are located in Syslog tab of the NE information window.

This table provides the following information: Field Name

Description

IP Address

This column lists the IP addresses of the remote syslog server. This column shows whether sending of syslog messages to the remote syslog server is enabled or not This column shows whether database change messages will be sent to the remote syslog server or not.

Syslog

DB Change events

User Manual

291

Configuring Remote Syslog Servers

You must be logged in with an user account with ADMIN privilege rights (see “Handling Network Element User Accounts” on p. 214) to configure remote syslog servers. The following sections are provided: “How to Add a Remote Syslog Server” on p. 292 “How to Edit a Remote Syslog Server” on p. 293 “How to Delete a Remote Syslog Server” on p. 294

How to Add a Remote Syslog Server This procedure describes how to add a new syslog destination.

PS

A maximum of 3 remote syslog servers may be configured.

Note

Step 1

Select the relevant NE from the Entities pane hierarchical list.

Step 2

In the Parameter pane, select the Syslog tab. In response, the table of configured remote syslog servers is displayed.

Step 3

Select Add. In response, the Add Syslog entry window appears.

Step 4

Enter the IP address of the remote syslog server into the IP Address field. Ensure that you entered the correct IP address. You cannot modify the IP address after you have applied your entries.

292

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

Chapter 4 Configuring NEs

Step 5

When you add a new remote syslog destination, sending of syslog messages to it is enabled by default. This is indicated by the entry Enable in the Syslog field.

Step 6

Enable or disable whether logged database changes should also be sent to the remote syslog server by using the DB Change events drop-down list. Select Enable to send these messages.

Step 7

Select OK to save settings or Cancel to discard these changes. The new remote syslog server is displayed in the list.

End of Procedure

How to Edit a Remote Syslog Server It is only possible to edit the IP address of a remote syslog server by deleting the entry and creating a new one. This procedure describes how to enable or disable a remote syslog server and how to enable or disable sending of database change messages to a remote syslog server.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

Select the relevant NE from the Entities pane hierarchical list.

Step 2

In the Parameter pane, select the Syslog tab. In response, the table of configured remote syslog servers is displayed.

Step 3

Select the relevant remote syslog server to edit.

Step 4

Select Modify. In response, the Modify Syslog entry window appears.

Step 5

User Manual

Enable or disable this remote syslog server by using the Syslog drop-down list.

293

Configuring Remote Syslog Servers

Step 6

Enable or disable whether logged database changes should also be sent to the remote syslog server by using the DB Change events drop-down list. Select Enable to send these messages.

Step 7

Select OK to save any changes or Cancel to discard them.

Step 8

If the syslog table does not immediately display your changes, select Refresh to update it.

End of Procedure

How to Delete a Remote Syslog Server This procedure describes how to delete an existing remote syslog server from the Syslog Destination IP Table.

Procedure Step 1

Select the relevant NE from the Entities pane hierarchical list.

Step 2

In the Parameter pane, select the Syslog tab.

Step 3

Select the relevant remote syslog server to delete.

Step 4

Select Delete. In response, a warning window appears.

Step 5 Step 6

Select OK to confirm the deletion, or Cancel to stop it. If the syslog table does not immediately display your changes, select Refresh to update it.

End of Procedure

294

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the table of configured syslog server is displayed.

Chapter 4 Configuring NEs

How To Configure Scheduled Equalization The 8ROADM-C40/0/OPM, 8ROADM-C80/0/OPM, and ROADM-C80/0/OPM modules support scheduled equalization. Scheduled equalization is intended to correct slow, time-varying optical power changes in wavelengths that result from a number of conditions. Scheduled equalization attempts to keep channel power at the set point. The scheduled equalization process performs adjustments, as required, along the channel path, from the network input to the network output. Scheduled equalization ensures that the equalization is performed consistently, at the same moment in time, for all nodes in the network. Scheduled equalization adjusts channel optical power towards the set point when the power level is greater than or equal to the tolerance limit (0.3 dB) and less than or equal to the scheduled equalization limit (3.0 dB) from the set point, when hardware allows. Adjustments occur incrementally, in 0.3 dB steps, during each scheduled equalization interval. Multiple scheduled equalization intervals may be required to compensate for larger channel power changes.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Scheduled equalization is specified on a network basis, thus all NEs in the network must be scheduled for equalization at the same time, date, and interval. Scheduled equalization must be completed within 41 minutes. The designated scheduled equalization start time is based on coordinated universal time (UTC). Once a UTC time value is entered, the system displays the local NE time automatically. The date and time you define in the schedule are in the NE’s time zone, which can be different from the Element Manager’s time zone. PS

Note

If all nodes in the network are not in the same time zone, you must take this into consideration to schedule equalization at the same date and time.

Requirements Observe these rules when setting the parameters for a scheduled equalization:

User Manual

•

Network Time Protocol (NTP) must be enabled in server, client, or relay modes on all ROADM nodes in the network. At maximum, one node should be set to server-only mode, and all other nodes should point to this node as their remote NTP server. Alternatively, all nodes should use one or more third-party NTP servers as their common server. If NTP is not enabled on a ROADM node, the scheduled equalization process stops, and an alarm condition is raised. For more information about enabling NTP on a node, see “Synchronizing NE time via NTP” on p. 280.

•

If the NE is operating as an NTP client or relay, that NE must be synchronized with at least one remote NTP server. If it is not, the scheduled equalization process stops, and an alarm condition is raised. As soon as NTP synchronization is achieved, scheduled equalization restarts, and the alarm clears. For more information about operating NTP on a node in client or relay mode, see “How to Add a Remote Syslog Server” on p. 292.

•

Scheduled equalization start time and interval must be the same for all nodes in the network. All scheduled equalizations are based on UTC.

295

How To Configure Scheduled Equalization

Follow this instruction to setup and activate scheduled equalization on an NE with a ROADM module.

Procedure Step 1

Select the relevant NE in the Managed Elements pane.

Step 2

Select the Equalization tab in the Parameters pane.

Step 3

Select Modify.

Step 4

Enable use of scheduled equalization by setting the Schedule EQLZ Admin drop-down list to Enabled.

Setting the Schedule EQLZ Admin field to Disabled disables scheduled equalization for the whole network element and consequently also disables scheduled equalization for virtual channels that have Schedule EQLZ Admin set to Enabled. This setting does not take effect until you later apply the settings. Step 5

Specify the interval between each scheduled equalization, using the Schedule EQLZ Interval drop-down list. This setting must be equal for

all network elements in the network. The options are: • 5-MIN: Every 5 minutes (Not recommended.) • 2-HR: Every 2 hours • 4-HR: Every 4 hours • 12-HR: Every 12 hours • 1-DAY: Every 24 hours • 7-DAY: Every week

296

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window will appear.

Chapter 4 Configuring NEs

Step 6

Enter the start date for initiating equalization, using the EQLZ Start Date drop-down list. All NEs in the network must be scheduled to equalize at the same time. The date you enter must not be according to local time, but must be according to universal coordinated time (UTC). Use the format year, month and day (YY-MM-DD). By default, equalization is scheduled on all nodes to begin on the date of 08-01-01, at the time of 03-00-00.

Step 7

Enter the start time for the initiating equalization into the EQLZ Start Time field using the format hh:mm:ss. All NEs in the network must be scheduled to equalize at the same time. The time must be according to universal coordinated time (UTC). Use the format hours, minutes and seconds (HH:MM:SS).

Step 8

Select OK to apply your settings, or Cancel to discard them.

End of Procedure

Configuring Span Equalization

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Span equalization automates the gain provisioning of variable gain pre-amplifiers, boosters, and line-amplifiers between network elements, on a span basis. Span equalization and ROADM channel power equalization automatically perform overall network equalization and simplify the management of complex optical networks.

Automatic span equalization applies only to C-band amplifiers.

Note

In general terms, a span begins at the output of a booster amplifier at a node and ends at the output of the pre-amplifier or line-amplifier of the adjacent downstream node. Span equalization itself has three primary functions: •

Setting the gain of qualified EDFA amplifier modules automatically during initial network commissioning

•

Adjusting the gain of qualified EDFA amplifier modules automatically when a fiber is cut and re-spliced

•

Adjusting the gain of a replacement qualified EDFA amplifier module automatically

In addition to the three primary functions, dynamic span equalization adds the ability to constantly monitor the span loss in an operational network and dynamically compensate for span loss drift, by adjusting the gains of the appropriate amplifiers.

User Manual

297

Configuring Span Equalization

Span Equalization Requirements Span equalization requires these conditions to operate in a network: •

An optical supervisory channel (OSC) must be enabled on each span between every node.

•

All cable connections to the EDFA modules must be represented in each node database by valid PTP connections (fibermap representations) in the PTP & Physical Connections Table. For more information about entering cable connections into the database, see “Managing Cables in the Internal Database” on p. 353.

•

An EDFA module booster amplifier must be associated with every transmit network interface.

•

Span equalization does not set the gain of Raman amplifiers in a node. After a Raman amplifier has been installed and successfully provisioned, span equalization provisions the gain setting of qualified EDFA amplifier modules, accounting for the Raman amplifier gain.

•

In network spans containing Raman amplifier modules, the attenuation between the booster amplifier and the Raman amplifier could be altered when a fiber between a booster amplifier module and a Raman amplifier is replaced, or the booster amplifier module is replaced. In the event of such an attenuation change, perform an explicit equalization request to adjust the gain on the far-end pre-amplifier module at the end of the span. For instructions on how to perform an explicit equalization request, refer to the FSP 3000R7 Provisioning and Operations Manual.

•

Span equalization does not operate on nodes that contain more than one pre-amplifier on a span.

•

Span equalization does not support networks with VSM or RSM modules protecting the network interfaces.

Configuration Procedures This section describes how to turn-up span equalization for two example linear networks. In addition the section contains supporting procedures for the central sub-tasks required during this turn-up.

PS

Note

The procedures in this section support the use of the Element Manager to provision span equalization. These procedures are designed to complement the procedures described in the FSP 3000R7 Provisioning and Operations Manual. For a more detailed description of span equalization operational principles, functionality, and limitations, please refer to the

FSP 3000R7 Provisioning and Operations Manual. The following sections are provided:

298

•

“How to Provision Span Equalization in a New Network” on p. 299

•

“How to Provision Span Equalization in an Existing Network” on p. 301

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Span Equalization Limitations

Chapter 4 Configuring NEs

•

“How to Initiate Equalization” on p. 303

•

“How to View the List of Qualified EDFAs” on p. 305

•

“How to View Span Equalization Status, Alarms, and Configuration” on p. 306

•

“How to Configure Span Equalization Options” on p. 308

•

“How to Change Qualified EDFA Set Point and PPC” on p. 309

•

“How to Change Qualified EDFA Gain” on p. 311

•

“How to Change Qualified EDFA Administrative State” on p. 314

•

“How to Enable/Disable Dynamic Equalization” on p. 315

How to Provision Span Equalization in a New Network The first example demonstrates a greenfield, four-node linear network. Figure 20:

Span Equalization Linear Network Example: New Network

Terminal Node 1

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

1. ROADM 2. FOADM

Through Node 2 SetPoint

PPC

C1

D1

A2

Pre-amp

Booster

X P D R

Link 1-2

PPC /OPT

Line amp Node 3

PPC

SetPoint

PPC

B2

C2

D2

1. ROADM 2. FOADM

Terminal Node 4

PPC A3

Booster

PPC

B3

A4

Line-amp

Link 2-3

PPC/OPT

B4

Pre-amp

Link 3-4

1. ROADM 2. FOADM

X P D R

PPC/OPT

This example assumes these conditions: •

The network is a new, or greenfield, equipment installation in which all cables are properly connected.

•

All physical cable connections are represented in the database by valid PTP (fibermap) connections in the Physical Terminations window and in the Physical Connections List.

•

All EDFA amplifier modules are out of service without power applied.

•

An optical supervisory channel (OSC) service is active between nodes.

•

All FOADM or ROADM connections for service between Node 1 and Node 4 have been manually and correctly entered, but with no services established other than the OSC.

For this example, the goal is to establish a service from Node 1 to Node 4. For more information about how to provision amplifier gain settings, refer to the

FSP 3000R7 Provisioning and Operations Manual.

User Manual

299

Configuring Span Equalization

Procedure Step 1

For each node in Figure 20, trigger the EDFA module qualification process. Do as follows: a) Configure span equalization to Qualify Only as described in “How to Configure Span Equalization Options” on p. 308.

Step 2

For each node in Figure 20, enable the gain calculation process by configuring span equalization to mode Enable Calculate Gain as described in “How to Configure Span Equalization Options” on p. 308.

Step 3

If your network plan requires other settings than the default settings on the EDFAs for set point, output power per channel, and GainCal offset value gain settings, then change these as relevant for Nodes 1 through 4. See “How to Change Qualified EDFA Set Point and PPC” on p. 309 or “How to Change Qualified EDFA Gain” on p. 311 for guidance.

PS

Note

After a qualified EDFA module is placed in service, no further changes to the set point and PPC values are allowed. The gain can be changed while the EDFA module is in service, however a change to the GainCal offset parameter could disrupt the service. Changes to the gain should therefore be performed at this point, if required.

Step 4

On Node 1, set the administrative state of the network port of the channel module (marked XPDR in Figure 20) to In Service. See “How to Change the Administrative State” on p. 260 for guidance.

Step 5

On Node 1, set the administrative state of the qualified booster EDFA optical transmit port to In Service. See “How to Change Qualified EDFA Administrative State” on p. 314 for guidance. In response automatic span equalization sets the gain of the Node 1 booster amplifier and begins transmitting valid output power per channel (PPC) and optical power transmitted (OPT) values to Node 2 through the OSC.

Step 6

On Node 2, set the administrative state of the qualified pre-amplifier EDFA optical transmit port to In Service. See “How to Change Qualified EDFA Administrative State” on p. 314 for guidance. In response the optical power received (OPR) value at the Node 2 pre-amplifier is retrieved, and automatic span equalization calculates the gain setting for the Node 2 pre-amplifier based on validated PPC and OPT messages and OPR measurements. The gain is now set.

300

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

b) Check that the expected EDFA modules have been qualified, as described in “How to View the List of Qualified EDFAs” on p. 305.

Chapter 4 Configuring NEs

Step 7

On Node 2, set the administrative state of the qualified booster EDFA optical transmit port to In Service. See “How to Change Qualified EDFA Administrative State” on p. 314 for guidance. In response automatic span equalization sets the gain of the Node 2 booster amplifier module, and the booster amplifier begins to send valid PPC and OPT values to the Node 3 line-amplifier module through the OSC.

Step 8

On Node 3, set the administrative state of the qualified line-amplifier EDFA optical transmit port to In Service. See “How to Change Qualified EDFA Administrative State” on p. 314 for guidance. In response, OPR values at the Node 3 line-amplifier module are retrieved, and automatic span equalization calculates the Node 3 line-amplifier module gain value based on validated PPC and OPT messages and OPR measurements. The Node 3 line-amplifier module gain is now set, and the module begins to send valid PPC and OPT messages to Node 4 through the OSC.

Step 9

On Node 4, set the administrative state of the qualified pre-amplifier EDFA optical transmit port to In Service. See “How to Change Qualified EDFA Administrative State” on p. 314 for guidance.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, OPR values at the Node 4 pre-amplifier module are retrieved, and automatic span equalization calculates the gain setting for the Node 4 pre-amplifier module based on validated PPC and OPT messages and OPR measurements. The Node 4 pre-amplifier module gain is now set, and light is received by the Node 4 transponder input. Step 10

Place all qualified EDFA amplifier modules in the network in service.

End of Procedure

How to Provision Span Equalization in an Existing Network The second example demonstrates an existing, or brownfield, four-node linear network.

NOTICE

User Manual

Performing this procedure could cause service interruptions in your network. This procedure should only be performed during a maintenance window.

301

Configuring Span Equalization

Figure 21:

Span Equalization Linear Network Example: Existing Network

Terminal Node 1

1. ROADM 2. FOADM

Through Node 2 SetPoint

PPC

C1

D1

A2

Pre-amp

Booster

X P D R

Link 1-2

Line amp Node 3

PPC

SetPoint

PPC

B2

C2

D2

1. ROADM 2. FOADM

PPC A3

Booster

PPC

B3

A4

Line-amp

Link 2-3

PPC /OPT

Terminal Node 4

PPC/OPT

B4

Pre-amp

Link 3-4

1. ROADM 2. FOADM

X P D R

PPC/OPT

•

The network is an existing, or brownfield, equipment installation in which all cables are properly connected.

•

All physical cable connections are represented in the database by valid PTP (fibermap) connections in the Physical Terminations window and in the Physical Connections List.

•

All qualified EDFA amplifier modules are in service and not in LOS condition.

•

An optical supervisory channel (OSC) service is active between nodes.

•

All ROADM virtual channels (VCHs) are established.

For this example, the goal is to enable span equalization for all nodes in the existing network.

PS

Note

An EDFA amplifier module can be in service but not be in an LOS condition due to excessive amplified spontaneous emission (ASE) noise at the network input with node channels present. Before selecting the Enable Adopt Gain option, take precautions to ensure that all in service amplifier module gain settings have been set properly.

Procedure Step 1

For each node in Figure 21, trigger the EDFA amplifier module qualification process. Do as follows: a) Configure span equalization to Qualify Only as described in “How to Configure Span Equalization Options” on p. 308. b) Check that the expected EDFA modules have been qualified, as described in “How to View the List of Qualified EDFAs” on p. 305.

Step 2

302

For each node in Figure 21 enable span equalization as follows: • For a FOADM or line-amplifier node, do as described in Step 3 • For a ROADM node, do as described in Step 4

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This example assumes these conditions:

Chapter 4 Configuring NEs

Step 3

Enter manually the set point and PPC values for the FOADM node as follows: a) For each qualified booster-amplifier EDFA on the node, connect an optical spectrum analyzer (OSA) to the output tap ports to determine the average channel power levels. For more information about using OSAs to measure optical power levels, refer to the “Measuring and Leveling of the Network Line” section of the FSP 3000R7 Installation and Commissioning Man-

ual. b) For each qualified booster-amplifier EDFA on the node enter the measured average channel power level into the Power per channel field as described in “How to Change Qualified EDFA Set Point and PPC” on p. 309. The NCU software computes the set point value for each booster amplifier module. c) For each qualified pre-amplifier and line-amplifier EDFA on the node, connect an OSA to the output tap ports to determine the average channel power levels.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

d) For each qualified pre-amplifier and line-amplifier EDFA on the node, enter the measured average channel power level into the Power per channel field as described in “How to Change Qualified EDFA Set Point and PPC” on p. 309. e) Adopt existing gain settings for the qualified EDFAs by configuring span equalization to Enable Adopt Gain as described in “How to Configure Span Equalization Options” on p. 308. For more information about NCU software actions when using Enable Adopt Gain mode on a FOADM or line-amplifier node, refer to the FSP 3000R7 Provisioning and Operations Manual. Step 4

Adopt existing gain settings for the qualified EDFAs by configuring span equalization to Enable Adopt Gain as described in “How to Configure Span Equalization Options” on p. 308. For more information about NCU software actions when using Enable Adopt Gain mode on a ROADM node, refer to the FSP 3000R7 Provisioning and Operations Manual.

End of Procedure

How to Initiate Equalization For ROADM devices, the user can initiate equalization. A user-initiated equalization is never denied, as long as the requested ROADM device is equipped. However, the equalization operation only has a physical effect on the wavelengths (channels) that are currently supporting cross-connections, with the cross-connection Admin State set to In Service. There are several requirements before initiating equalization. This procedure only describes how to use the Element Manager to start the actual initiation.

User Manual

303

Configuring Span Equalization

For the full procedure, including requirements and restrictions, see the FSP 3000R7 Provisioning and Operations Manual.

PS

Note

An individual wavelength power equalization request on a 8ROADM-C40/0/OPM or 8ROADM-C80/0/OPM module results in global power level equalization for all virtual channels on the module network port.

Step 1

Identify the channel module that is cross-connected to the ROADM device as described in “How to View ADM and ROADM Cross Connections” on p. 166. • To equalize the ROADM shelf (ROADM-C40/40/OPM-3HU/2DC), view cross-connections for the SHELF X EROADM-DC. • To equalize ROADM modules (8ROADM-C40/0/OPM or ROADM-C80/0/OPM), view cross-connections for the the MOD-x-y [8]ROADM-C[40/80].

Step 2

Select this channel module that is cross-connected to the relevant ROADM device in the Entities pane.

Step 3

Ensure that light is present during equalization. Turning off ALS or setting the laser to “Forced on” ensures that light is present during equalization. Do as follows: • If the channel module supports turning off ALS, turn off ALS as described in “How to Set the Automatic Laser Shutdown Mode” on p. 358. • If the channel module supports forcing the laser on, force the laser on as described in “How to Force a Laser On” on p. 360.

Step 4

Select the relevant ROADM entity in the Entities pane. • For a global wavelength equalization, select an OM entity. For example, the OM-19-N OM entity for the ROADM-C40/40/OPM-3HU/2DC shelf, or the OM-1-6-N OM entity for the 8ROADM-C40/0/OPM or ROADM-C80/0/OPM module. • For an individual wavelength equalization: select a VCH entity. For example, the VCH-19-N3 OCH entity for the ROADM-C40/40/OPM-3HU/2DC shelf, or the VCH-1-6-N3 OCH entity for the 8ROADM-C40/0/OPM or ROADM-C80/0/OPM module.

Step 5

Select the Operation tab.

Step 6

Select Modify. In response, the Modify window appears.

Step 7

Select Operate from the Initiate Equalization drop-down list.

Step 8

Select OK to apply your change, or Cancel to reject it. In response, equalization is initialized.

304

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

Chapter 4 Configuring NEs

Step 9

If the network contains a ROADM-C40/40/2-3HU-2DC shelf: you may turn the ALS back on or remove the Forced On setting for the channel module lasers after the equalization is complete.

End of Procedure

How to View the List of Qualified EDFAs This section describes how to view the list of EDFA modules that have been qualified for span equalization at a NE.

Procedure Step 1

Right-click the NE in the Managed Elements pane, and select Span Equalization from the context-sensitive menu that appears.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Span Equalization window appears.

The following information is displayed for each qualified EDFA: Column Name

Description

AID OL-AID

Displays the AID of the qualified EDFA. Displays the AID of the optical line entity which is associated with the qualified EDFA. Displays the EDFA equipment type. Displays whether the qualified EDFA has been configured as Pre-Amp, Booster-Amp, or Line-Amp. Displays the input per-channel optical power to a booster amplifier.

Equipment Qualified

Setpoint

Step 2

User Manual

The number of qualified EDFA modules is displayed under the lower, right corner of the list. If the list of qualified EDFAmodules is long, you can use the yellow arrows to browse the list.

305

Configuring Span Equalization

Step 3

Select Close to close the Span Equalization window.

End of Procedure

How to View Span Equalization Status, Alarms, and Configuration When an EDFA module has been qualified for span equalization, the span equalization related properties for the EDFA module are displayed in the Span Equalization window, not in the Parameter pane like the rest of the EDFA module related information.

•

The State tab shows the administrative state and the operational state for the selected qualified EDFA.

•

The Fault tab only shows faults related to span equalization on the selected qualified EDFA.

•

The Config tab shows the following information o

o o o

o

306

Whether the qualified was found to be configured as a pre-amplifier, booster-amplifier, or line-amplifier. The current setting for the gain calibration offset for the qualified EDFA. The current setting for the optical set point for the qualified EDFA. The current setting for the output power per channel for the qualified EDFA. The current calculated gain for the qualified EDFA.

•

The Operation tab shows whether manually triggered gain calibration is ongoing or not.

•

The Info tab shows measurements for both the near-end qualified EDFA power (this EDFA) and far-end qualified EDFA power, as well as far-end qualified EDFA settings.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The span equalization related information is presented in the Parameters section of the Span Equalization window, and looks similar to the Parameter pane content. Standard tabs are provided for each information type.

Chapter 4 Configuring NEs

This instruction describes how to view all parameters which are related to span equalization for a qualified EDFA module.

Procedure Step 1

Right-click the NE in the Managed Elements pane, and select Span Equalization from the context-sensitive menu that appears.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Span Equalization window appears.

Step 2

Select the qualified EDFA in the list.

Step 3

Expand the Parameters section by clicking the + symbol. In response the Span Equalization window content is updated.

Step 4

User Manual

Select the relevant tab in the Parameters section in order to view the span equalization parameters for this qualified amplifier.

307

Configuring Span Equalization

Step 5

Select Close to close the Span Equalization window.

End of Procedure

How to Configure Span Equalization Options Enabling of span equalization options should only be done in conjunction with following the Provisioning and Operations Manual procedure to turn up span equalization for a network. These are the span equalization operational mode provisioning options and which effect they have: •

Disabled: Gain settings must be provisioned manually for all EDFA amplifier modules in the network.

PS

When in Disabled mode, all qualified EDFA amplifier module PPC and set point values are reset to default values.

Note

Qualify Only: The NCU software queries the node database PTP and Physi-

cal Connections list to determine which EDFA amplifier modules qualify for span equalization adoption. The NCU software makes no changes to the gain settings for these amplifier modules when operating in Qualify Only mode. The query action of the Qualify Only option is the first step towards enabling automatic span equalization, for either Enable Calculate Gain or Enable Gain Adopt modes. •

Enable Calculate Gain: By using a combination of parameters described in

detail in the FSP 3000R7 Provisioning and Operations Manual, span equalization automatically calculates and sets the initial gain values for all qualified EDFA amplifier modules at a node after an LOS condition clears. While operating in this mode, span equalization only re-calculates the gain of an EDFA pre-amplifier or line-amplifier module when an LOS transition is detected and has cleared, or upon an explicit request. Enable Calculate Gain is utilized primarily in new, or greenfield, networks. •

Enable Gain Adopt: Span equalization adopts the current gain settings for all

qualified EDFA amplifier modules at a node, calculates the values of the control parameters based on the gain settings of the qualified amplifier modules, and stores those values persistently in the NCU database. While operating in Enable Gain Adopt mode, span equalization only recalculates the gain of an EDFA pre-amplifier or line-amplifier module when an LOS transition is detected and has cleared, or upon an explicit request. Enable Gain Adopt mode is used primarily in existing, or brownfield, networks. This instruction describes how to use the Element Manager to enable span equalization options for an EDFA module.

Requirements See “Span Equalization Requirements” on p. 298

308

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

Chapter 4 Configuring NEs

Procedure Step 1

Right-click each node in the Managed Elements pane, and select Span Equalization from the context-sensitive menu that appears.

In response the Span Equalization window appears. Step 2

Select Modify.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window appears.

Step 3

Select one of the following options from the SPEQ Configuration field: • To trigger the process of qualifying EDFAs for span equalization in this node, select Qualify Only, • To trigger the automatic span equalization without adopting current gain values, select Enable Calculate Gain, • To trigger the automatic span equalization and adopt current gain values, select Enable Adopt Gain, • To disable automatic span equalization, select Disable,

Step 4

Select OK to apply your change, or Cancel to reject it.

Step 5

Select Close to close the Span Equalization window.

End of Procedure

How to Change Qualified EDFA Set Point and PPC This instruction describes how to change the set point or the output power per channel (PPC) for a qualified EDFA. The set point parameter is only relevant for booster-amplifier EDFAs. Changing the set point and PPC for a qualified EDFA should only be done in conjunction with following the Provisioning and Operations Manual procedure to turn-up span equalization for a network. The turn-up procedure takes into account restrictions as to when such a change is allowed, as well as gives guidance on selecting values.

Requirements The qualified EDFA must have administrative state Maintenance.

User Manual

309

Configuring Span Equalization

Procedure Step 1

Right-click the NE in the Managed Elements pane, and select Span Equalization from the context-sensitive menu that appears.

Step 2

Select the qualified EDFA to change set point or PPC for.

Step 3

Expand the Parameters section by clicking the + symbol. In response the Span Equalization window content is updated.

310

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Span Equalization window appears.

Chapter 4 Configuring NEs

Step 4

Select the Config tab in the Parameters section. In response the Span Equalization window content is updated.

Step 5

In the Config tab, select Modify.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window appears. Step 6

If relevant, enter the new value for the optical set point in the Optical Setpoint field.

Step 7

If relevant, enter the new value for the power per channel in the Power per channel field.

Step 8

Select OK to apply your change, or Cancel to reject it.

Step 9

Select Close to close the Span Equalization window.

End of Procedure

How to Change Qualified EDFA Gain This instruction describes how to change the gain of a qualified EDFA. This is relevant to do in order to fine tune the gain. Changing the gain is supported also after the EDFA has been put In Service, but such a change could affect service. It is recommended to change gain for a qualified EDFA only in conjunction with following the Provisioning and Operations Manual procedure to turn-up span equalization for a network. The turn-up procedure takes into account restrictions and recommendations as to when such a change is allowed.

User Manual

311

Configuring Span Equalization

Procedure Step 1

Right-click the NE in the Managed Elements pane, and select Span Equalization from the context-sensitive menu that appears.

Step 2

Select the qualified EDFA module in the list.

Step 3

Expand the Parameters section by clicking the + symbol. In response the Span Equalization window content is updated.

312

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Span Equalization window appears.

Chapter 4 Configuring NEs

Step 4

Select the Config tab in the Parameters section. In response the Span Equalization window content is updated.

Step 5

In the Config tab, select Modify.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window appears. Step 6

Enter the new value for the gain offset in the GainCal Offset field.

Step 7

Select OK to apply your change, or Cancel to reject it.

Step 8

Select Close to close the Span Equalization window.

End of Procedure

User Manual

313

Configuring Span Equalization

How to Change Qualified EDFA Administrative State This section describes how to change the administrative state of a qualified EDFA.

Procedure Step 1

Right-click the NE in the Managed Elements pane, and select Span Equalization from the context-sensitive menu that appears.

Step 2

Select the qualified EDFA in the list.

Step 3

Expand the Parameters section. In response the Span Equalization window content is updated.

314

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Span Equalization window appears.

Chapter 4 Configuring NEs

Step 4

Select the Modify button. In response the Modify window appears.

Step 5

Use the Admin State drop-down list to select the relevant administrative state, either In Service or Maintenance.

Step 6

Select OK to apply your change or Cancel to reject the change.

Step 7

Select Close to close the Span Equalization window.

End of Procedure

How to Enable/Disable Dynamic Equalization Dynamic span equalization can be enabled separately from the span equalization configuration mode, provided span equalization configuration is in either Enable Gain Calculate or Enable Gain Adopt modes.

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

When dynamic span equalization is enabled, the NCU dynamically computes a new gain value for pre-amplifier and line-amplifier modules every two seconds and makes automatic adjustments to those gain settings to compensate for span loss drift. These gain adjustments are made slowly, in small increments, so fast transitions in span loss requires several seconds to complete compensation.

When the gain setting of an EDFA that is in service is changed, this can disrupt traffic.

Note

This instruction describes how to enable dynamic span equalization for an NE.

Procedure Step 1

Right-click the NE in the Managed Elements pane, and select Span Equalization from the context-sensitive menu that appears. In response the Span Equalization window appears.

Step 2

Select Modify. In response the Modify window appears.

User Manual

315

Viewing and Configuring Trace Messages

Step 3

Use the SPEQ Dynamic Comp. drop-down list to select Enable or Disable field:

Step 4

Select OK to apply your change, or Cancel to reject it.

Step 5

Select Close to close the Span Equalization window.

End of Procedure

Viewing and Configuring Trace Messages Trace is a way to ensure connectivity within a network, by using the trace byte. The principle is that an expected trace message is defined for a connection. The transmitter enters this message in the trace overhead byte when sending. The receiver checks the message received in the trace byte against the expected message. A mismatch indicates that the sender and receiver that were supposed to be connected, may not be correctly connected. A Trace Identifier Mismatch (TIM) alarm can be raised upon detection of such a mismatch. Raising of the TIM alarm is configurable for each trace message.

The following topics are provided: “How to View the Trace Messages” on p. 316 “How to Configure the Trace Messages” on p. 318

How to View the Trace Messages This procedure explains how to view the current settings for Trace messages, TIM Mode etc.

Procedure Step 1

Select the relevant channel entity in the Entity pane.

Step 2

Select the Config tab in the Parameters pane.

Step 3

Expand the Trace section. In response the Trace pane appears. The values and information displayed may vary depending on which channel entity you have selected. The Trace pane content depends on whether the signals are SDH/ SONET or OTN, see “Trace Pane Content for SDH/SONET Signals” on p. 317 and “Trace Pane Content for OTN Signals” on p. 317.

End of Procedure

316

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

For more detailed information about Trace, see the FSP3000R7 User Documentation.

Chapter 4 Configuring NEs

Trace Pane Content for SDH/SONET Signals

For SDH and SONET signals, you see the fields described below. To modify any of the field values, you must select the Modify button. Field Name

Description

Layer

This drop down list is used to select which layer you want to measure on. The option Enabled_AISDisabled indicates that a TIM alarm will be raised if there is a mismatch between the received and expected trace message, but no AIS is raised as a consequent action. Shows the format (64 Byte, 16 Byte or 1 Byte). Radio buttons to let you select whether you want to view the trace messages in ASCII or hexadecimal format. Shows the trace message you expect to receive. Shows the trace message you sent.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

TIM Mode

Format ASCII and Hex

Expected Transmitted

Trace Pane Content for OTN Signals

User Manual

317

Viewing and Configuring Trace Messages

Field Name

Description

Layer

This drop down list is used to select which layer you want to measure on. If you select a sublayer, it will be easier to identify errors. The option Enabled_AISDisabled indicates that a TIM alarm will be raised if there is a mismatch between the received and expected trace message, but no AIS is raised as a consequent action. Radio buttons to let you select whether you want to view the trace messages in ASCII or hexadecimal format. Shows the trace message you expect to receive for SAPI (Source Access Point Identifier). The Trace compare process is only based on the SAPI, DAPI and OPSP are not used. Shows the SAPI trace message you sent. Shows the DAPI (Destination Access Point Identifier) trace message you sent. Shows the OPSP (Operator Specific) trace message you sent. Shows the SAPI trace message you received. Shows the DAPI trace message you received. Shows the OPSP trace message you received.

TIM Mode

ASCII and Hex

SAPI Expected

SAPI Tx DAPI Tx OPSP TX SAPI Rx DAPI Rx OPSP Rx

How to Configure the Trace Messages This procedure explains how to configure the settings for the trace messages.

Procedure Step 1

Select the relevant channel entity in the Entity pane.

Step 2

Select the Config tab in the Parameters pane.

Step 3

Expand the Trace section.

Step 4

Select the Modify button In response the Modify window appears. The fields and options available may vary depending on which channel entity you have selected. For SDH/SONET, go to “Configuring Settings for SDH/SONET Signals” on p. 319. For OTN, go to “Configuring Settings for OTN Signals” on p. 320. Remember to select layer before you select the Modify button.

End of Procedure

318

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

For OTN signals, you see the fields described below. To modify any of the field values, you must select the Modify button.

Chapter 4 Configuring NEs

Configuring Settings for SDH/SONET Signals This procedure explains how to configure the trace message settings for SDH/SONET signals and follows the procedure in “How to Configure the Trace Messages” on p. 318.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

In the TIM Mode field, specify whether the TIM Alarm shall be raised upon detection of a mismatch between Expected and Received trace message. If you select Enabled_AISDisabled, a TIM Alarm will be raised upon detection of a mismatch between Expected and Received message, but there will not be sent any Alarm Indication Signal. By default, TIM Mode is disabled.

Step 2

Select the message format in the Format field. The trace byte may contain a whole message, or successive bytes may be concatenated to contain a longer message. The supported message length depends on the mapping type. You can choose 1 Byte, 16 Byte or 64 Byte. See Step 4 for more information on these values.

Step 3

Select the code to enter the message in, ASCII, Hex (hexadecimal) or G.831.

Step 4

User Manual

In the Expected field, write the trace message you expect to receive back. • The 1 byte frame shall contain one of the codes 0-255 for Decimal format, or a hexadecimal code for the Hex format. • In the 16 byte frame, the first byte should consist of a CRC-7 calculation over the previous frame, and the following 15 bytes transport the Source Access Point Identifier (SAPI), expressed in T.50 characters. This gives you 15 characters to compose your message. • In the 64 byte frame the last two bytes are carriage return (0x0d) and a line feed (0x0a). This particular combination of values must not be used in other places in the message. The 64 byte format thus gives you 62 characters to compose your message.

319

Viewing and Configuring Trace Messages

Step 5

In the Transmitted field, write the trace message you want to send.

PS

The sender and receiver should agree upon the Transmitted and Expected trace messages before starting the Trace process.

Note

Step 6

Select OK to save your settings and close the Modify window.

End of Procedure

Configuring Settings for OTN Signals

Procedure

320

Step 1

In the TIM Mode field, specify whether the TIM Alarm shall be raised upon detection of a mismatch between Expected and Received trace message. If you select Enabled_AISDisabled, a TIM Alarm will be raised upon detection of a mismatch between Expected and Received message, but there will not be sent any Alarm Indication Signal. By default, TIM Mode is disabled.

Step 2

Select the code for to enter the trace message in: • Select ASCII to write your trace message in clear text. • Select G.709 to follow the G.709 standard where the SAPI and DAPI messages shall consist of a 3 byte country code and a 12 byte National Segment code. • Select Hex to write your trace message in hexadecimal code.

Step 3

In the SAPI Expected field, write the SAPI trace message you expect to receive back. Only SAPI is used for comparison of messages for the Trace functionality.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This procedure explains how to configure the trace message settings for OTN signals and follows the procedure in “How to Configure the Trace Messages” on p. 318.

Chapter 4 Configuring NEs

Step 4

In the SAPI Tx field, write the SAPI trace message you want to send.

Step 5

In the DAPI Tx field, you may write the DAPI trace message you want to send.

Step 6

In the OPSP Tx field, you may write the Operator Specific trace message you want to send.

PS

Note

Step 7

For OTN signals, you have 15 characters available for your message for the SAPI and DAPI and 32 characters available for OPSP. The length and format for the trace string is the same for all layers in OTN. Select OK to save your settings and close the Modify window.

End of Procedure

How to Configure TCA Thresholds

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This instruction describes how to configure the thresholds for Threshold Crossing Alerts. You can set these thresholds for performance measurement on the physical layer so that an alert is generated in case a performance measure crosses a threshold. The thresholds are described in the FSP3000R7 Provisioning and Operations Manual.

Procedure Step 1

Select the relevant NE in the Managed Elements pane hierarchical list.

Step 2

From the Main Menu, select Performance -> Performance Data. In response, the Performance Data window will appear.

Step 3

Select which channel to view performance data for, by using the Monitoring Point drop-down list. The drop-down list is populated from the provisioned channels. Channels are identified by their AID address.

Step 4

Select which type of performance data to configure thresholds for, by using the Monitoring Type drop-down list. The available options in this list depend on what is selected for Monitoring Point in Step 3. You need to select a monitoring type that monitors on the physical layer. In response, the performance records and thresholds for the selected monitoring point and type are displayed in the Performance Data window.

User Manual

321

How to Configure Tandem Connection Monitoring

Step 5

Select the Modify button. If the Modify button is inactive, you are not monitoring on the physical layer - select a correct monitoring type. In response the Modify window appears.

Step 6

Set the preferred threshold values in the fields for Low and High threshold.

End of Procedure

This procedure explains how to configure Tandem Connection Monitoring (TCM). TCM is an important feature of the OTN within different administrative domains. It enables the user to monitor the traffic quality that is transported between segments in the network, allowing errors and defects along the path to be traced to a particular segment. For more information about TCM, see the FSP3000R7 Provisioning and Operations Manual.

Procedure Step 1

Step 2

Select the Network Element in the Entities pane, and expand the module so you can see its dependent entities, plugs (PL) and/or channels (CH). • If you can see the CH entity, go to Step 2. • If the CH entity is not visible, you must create it first. See “How to Create a Port” on p. 93. • If the channel (CH) shows the state UAS, you must create it first. See “How to Create a Port” on p. 93. Select the channel (CH) in the Entities pane, and then select the Config tab.

322

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Configure Tandem Connection Monitoring

Chapter 4 Configuring NEs

Step 3

Select the Modify button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Modify window appears.

Step 4

User Manual

Choose which one of the three TCM monitoring segments (TCM-A, TCM-B or TCM-C) you want to activate. Activate one of the three TCMs by selecting the relevant TCMi in the drop-down list called TCM-A Activation, TCM-B Activation or TCM-C Activation. You can choose the following TCMis: TCM1, TCM2, TCM3, TCM4, TCM5, TCM6.

323

How to Store Optical Power Reference Values

Step 5

Specify settings for Signal Degrade (SD) for the TCM you activated. Do as follows: a) In the field for BBE Signal Degrade for the relevant TCM, enter a threshold for the BBE counter. The default value is 15% for TCM A, TCM B and TCM C. b) In the field for SD Integration Period for the relevant TCM, enter the integration period. The default is 7 seconds. A candidate second for an SD alarm is present when the BBE counter exceeds the threshold. If there are a specified number of consecutive candidate seconds (G.783), then the SD alarm is raised. This number of candidate seconds is the integration period.

PS

Note

Step 6

If you are pre-provisioning, the Modify window will look a bit different. To get to the settings for Signal Degrade, you must close the Modify window after you have activated the appropriate TCM, and then select the Modify button again. Select OK to save your settings and close the Modify window.

How to Store Optical Power Reference Values When storage of optical power related values is triggered, these values are saved persistently for each optical port and will survive both software upgrade/downgrade, firmware upgrade, and cold or warm restart of a module. Up to ten optical power reference values can be stored for each module. Thereafter, when measurement of optical power reference values is triggered again, the new values overwrite the oldest stored optical power reference values. This instruction describes how to store optical power reference values for the modules on the NE. Upon intiation and completion of the optical power reference value storage, the system generates transient conditions to indicate this.

Requirement

324

•

The Element Manager is set to manage the NE via SNMPv3, using an user account with ADMIN privileges.

•

You must logged in with an Element Manager user account that has ADMIN privileges.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Chapter 4 Configuring NEs

Procedure Step 1

Double-click the relevant NE in the Managed Elements pane. In response, the Parameters pane displays information about this NE.

Step 2

Select the Opt Pwr Ref tab in the Parameters pane. In response, the optical power reference options are displayed in the Parameters pane.

Step 3

Trigger storage of optical power reference values by selecting Store

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

reference values.

In response, storing of optical power reference values starts. Progress is indicated by the Status of storing field, using the following status messages: • • •

In Progress, which means that storing is in progress. Success, which means that storing has successfully completed. Error, which means that storing was interrupted.

End of Procedure

Configuring Ethernet OAM/CFM How to configure and use Ethernet connectivity fault management (CFM) for OAM purposes is described in the FSP 3000 Provisioning and Operations Manual, Chapter 4. This section supports the FSP 3000 Provisioning and Operations Manual by giving more detailed guidance on using the Craft or Web Console to create each individual CFM entity. The procedures in this section should only be followed for additional support in conjunction with the procedures for configuring CFM in the FSP 3000 Provisioning and Operations Manual. The following sections are provided: “Creating a Maintenance Domain (MD)” on p. 326 “Creating a Maintenance Association Network (MAnet)” on p. 329 “Creating a Maintenance Association Component (MAcomp)” on p. 333

User Manual

325

Configuring Ethernet OAM/CFM

“Creating a Maintenance End Point” on p. 337 “Viewing and Modifying MAnet or MAcomp Configuration” on p. 341 “Deleting CFM Entities” on p. 349

Creating a Maintenance Domain (MD) In a complex Ethernet network, a customer may relate to one or more providers, who again use one or more operators to deliver the service. Connectivity fault management can be done for different domains, allowing adaptation to the operator networking model in each case. The MD is a network scope entity. This section describes how to create a maintenance domain (MD) entity.

Requirements •

A CFM plan for the network must exist.

Procedure Step 1 Step 2

Select the relevant NE in the Managed Elements pane hierarchical list. From the Main Menu, select Configuration -> Ethernet Service In response the Ethernet Service OAM/CFM window appears.

326

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

OAM/CFM.

Chapter 4 Configuring NEs

Step 3

Select the item CFM at the top of the left hand pane. In response the Ethernet Service OAM/CFM window displays the maintenance domains defined for this NE.

Step 4

Select Add.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Create Maintenance Domain wizard starts.

Each page in the wizard has a title. and the final page has the title Confirm. This helps you keep track of how far you have come. Navi-

gate 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

the parameters.

User Manual

327

Configuring Ethernet OAM/CFM

Step 5

In the page Identifier enter the planned MD identifier for this MD in the MD Identifier field. Select Next to continue. In response, the Parameters page appears.

Step 6

In the page Parameters do as follows: a) Enter the planned domain level number in the Domain Level field. Ensure that you enter the correct value, it cannot be changed later.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

b) In the Format Type of Name drop-down list, select the planned format type for the maintenance domain name. Select Next to continue. In response, the Name page appears.

328

User Manual

Chapter 4 Configuring NEs

Step 7

In the page Name enter the maintenance domain name in the Name field. Select Next to continue. In response, the Confirm page appears.

Step 8

Select Finish. In response, the entity is displayed in the Ethernet Service OAM/CFM window if it was successfully created. Together with the MD identifier, the MAnet identifier is used to form the AID for the MAnet, and this is displayed in the AID column of the Maintenance Domains table

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 9

Select Close to close the Ethernet Service OAM/CFM window.

End of Procedure

Creating a Maintenance Association Network (MAnet) In each end the CFM maintenance flow is realized by defining a maintenance association (MA). This MA is represented by two entities: •

The maintenance association net (MAnet)

•

The maintenance association component (MAcomp).

The MAnet has network scope. It lists the end points of the CFM maintenance flow (in NE A and NE B) and the Maintenance Domain (MD) that the end points belong to. The MAcomp has local scope and owns the parameters that are specific to the local end point, such as the Ethernet port and the primary VID it belongs to. This section describes how to create one maintenance association network (MAnet).

Requirements

User Manual

•

A CFM plan for the network must exist.

•

The EVC/EVC flow segment that connectivity fault management shall be configured for, must already have been provisioned. It is not necessary that it is in service.

•

The MD that the MAnet belongs to must already have been provisioned.

329

Configuring Ethernet OAM/CFM

Procedure Step 1 Step 2

Select the relevant NE in the Managed Elements pane hierarchical list. From the Main Menu, select Configuration -> Ethernet Service OAM/CFM.

Step 3

Select the MD that the MAnet belongs to in the hierarchical list of CFM entities in the left hand pane. In response the content in the right hand pane changes.

All maintenance association networks defined for this MD will be displayed.

330

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Ethernet Service OAM/CFM window appears.

Chapter 4 Configuring NEs

Step 4

Select Add. In response the Create Maintenance Association wizard starts.

Each page in the wizard has a title. and the final page has the title Confirm. This helps you keep track of how far you have come. Navi-

gate 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

the parameters. Step 5

In the page Identifier do as follows:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

a) Ensure that the MD AID that is displayed in the MD field is correct. If not, cancel the wizard and start it again after selecting the correct MD in the left pane. b) Enter the planned MA identifier for this MAnet in the MA Identifier field. Select Next to continue. In response, the Parameters page appears.

User Manual

331

Configuring Ethernet OAM/CFM

Step 6

In the page Parameters do as follows: a) In the List of Attached MEPS field, enter the maintenance end-points (MEPs) that are associated with this MAnet. Separate the MEPs with commas.

PS

If the MEP identifiers are not entered, you will not be able to create these MEPs in the appropriate later step.

Note

b) Use the CCM Period drop-down list to select the planned CCM period for this CFM maintenance flow. The CCM period is how long time shall pass between each CCM frame transmission. CFM maintenance flows that are used for Ethernet linear protection shall use 3.3 ms. c) In the Format Type of Name drop-down list, select the planned format type for the maintenance association name. Select Next to continue.

Step 7

In the page Name enter the planned MAnet name in the Name field. Select Next to continue. In response, the Confirm page appears.

332

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Name page appears.

Chapter 4 Configuring NEs

Step 8

Select Finish. In response, the entity is displayed in the Ethernet Service OAM/CFM window if it was successfully created. Together with the MD identifier, the MAnet identifier is used to form the AID for the MAnet, and this is displayed in the AID column of the Maintenance Associations table.

Step 9

Select Close to close the Ethernet Service OAM/CFM window.

End of Procedure

Creating a Maintenance Association Component (MAcomp) In each end the CFM maintenance flow is realized by defining a maintenance association (MA). This MA is represented by two entities: •

The maintenance association net (MAnet)

•

The maintenance association component (MAcomp).

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The MAnet has network scope. It lists the end points of the CFM maintenance flow (in NE A and NE B) and the Maintenance Domain (MD) that the end points belong to. The MAcomp has local scope and owns the parameters that are specific to the local end point, such as the Ethernet port and the primary VID it belongs to. This section describes how to create one maintenance association component (MAcomp).

Requirements

User Manual

•

A CFM plan for the network must exist.

•

The EVC/EVC flow segment that connectivity fault management shall be configured for, must already have been provisioned. It is not necessary that it is in service.

•

The MD that the MAnet belongs to must already have been provisioned.

•

The MAnet that the MAcomp belongs to must already have been provisioned.

333

Configuring Ethernet OAM/CFM

Procedure Step 1 Step 2

Select the relevant NE in the Managed Elements pane hierarchical list. From the Main Menu, select Configuration -> Ethernet Service OAM/CFM.

Step 3

Select the MAnet that the this end of the CFM maintenance flow belongs to in the hierarchical list of CFM entities in the left hand pane. In response the content in the right hand pane changes.

Step 4

Select the MACOMP tab. All MA components that exist for this MAnet will be displayed in the MACOMP tab.

334

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Ethernet Service OAM/CFM window appears.

Chapter 4 Configuring NEs

Step 5

Select Add. In response the Create MACOMP wizard starts.

Each page in the wizard has a title. these titles and their sequence are: Identifier, Parameters, Name, 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

the parameters. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 6

In the page Identifier do as follows: a) Ensure that the MAnet AID that is displayed in the Maintenance Association field is correct. If not, cancel the wizard and start it again after selecting the correct MAnet in the left pane. b) Enter the planned MAcomp identifier in the Identifier field. Select Next to continue. In response, the Parameters page appears.

User Manual

335

Configuring Ethernet OAM/CFM

Step 7

In the page Parameters do as follows: a) Use the Port AID drop-down list to select the Ethernet port AID which this CFM maintenance flow is associated with. This must be the same ETH port entity that is used by the EVC or EVC flow segment that this CFM maintenance flow monitors.

PS

Ensure that you enter the correct ETH port entity. It is easy to make a mistake at this point.

P

Note

b) The VLAN Comp Type field content cannot be changed. No action is required. Select Next to continue.

Step 8

Enter the planned primary VID that the CFM maintenance flow shall use for the CFM frames in the Primary VID field. The primary VID shall be equal to the external VID that was defined for the EVC or EVC flow segment.

PS

Ensure that you enter the correct primary VID. It is easy to make a mistake at this point.

P

Note

Select Next to continue. In response, the Confirm page appears.

336

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Parameters page content changes.

Chapter 4 Configuring NEs

Step 9

Select Finish. In response, the entity is displayed in the Ethernet Service OAM/CFM window on the MACOMP tab if it was successfully created. Together with the MD identifier, the MAnet identifier and the MAcomp identifier are used to form the AID for the MAcomp, and this is displayed in the AID column of the table on the MACOMP tab.

Step 10

Select Close to close the Ethernet Service OAM/CFM window.

End of Procedure

Creating a Maintenance End Point A CFM maintenance flow is characterized by its end points. These maintenance end points (MEPs) can generate and terminate CFM messages, and they act as filters to confine CFM frames within the domain level, and the flow. End points discard CFM frames at lower domain levels while they are transparent for CFM frames at higher domain levels. Maintenance end points are per MD level and can be associated with a port, a VID (SVID) or an EVC. This section describes how to create one maintenance end point (MEP).

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements

User Manual

•

A CFM plan for the network must exist.

•

The EVC/EVC flow segment that connectivity fault management shall be configured for, must already have been provisioned. It is not necessary that it is in service.

•

The MAnet that the MAcomp belongs to must already have been provisioned.

•

The MAcomp that the MEP belongs to must already have been provisioned.

337

Configuring Ethernet OAM/CFM

Procedure Step 1 Step 2

Select the relevant NE in the Managed Elements pane hierarchical list. From the Main Menu, select Configuration -> Ethernet Service OAM/CFM.

Step 3

Select the MAnet that the this end of the CFM maintenance flow belongs to in the hierarchical list of CFM entities in the left hand pane. In response the content in the right hand pane changes.

Step 4

Select the Maintenance End Points tab. All MEPs defined for this MD will be displayed in the Maintenance End Points tab.

338

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Ethernet Service OAM/CFM window appears.

Chapter 4 Configuring NEs

Step 5

Select Add. In response the Create Maintenance End Point wizard starts.

Each page in the wizard has a title. these titles and their sequence are: Identifier, Parameters, Name, 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

the parameters. Step 6

In the page Identifier do as follows:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

a) Ensure that the MAnet AID that is displayed in the Maintenance Association field is correct. If not, cancel the wizard and start it again after selecting the correct MAnet in the left pane. b) Enter the planned MEP identifier in the Identifier field. Select Next to continue. In response, the Parameters page appears.

User Manual

339

Configuring Ethernet OAM/CFM

Step 7

In the page Parameters do as follows: a) The facility type for the MEP can only be Down MEP, so no action is required for the Facility Type field. b) The AID of the ETH port that this MEP is associated with is displayed in Port AID field. This entry has been deduced from the MAcomp that already is associated with the MAnet. Compare against your CFM plan and ensure that this is the same ETH port as used by the EVC or EVC flow segment to be monitored. c) Enter the priority that is planned for the transmitted ETH-CCM CFM frames, d) To enable CFM monitoring at the far end, generation of ETH-CCM frames must be started in the local end. This can be done now, by leaving the Start CCM generation field set to ENABLE. Otherwise set the field to DISABLE. You can also enable or disable ETH-CCM generation at a later time, using the Config tab of the MEP. Select Next to continue.

Step 8

Enter the planned primary VID that the CFM maintenance flow shall use for the CFM frames in the Primary VID field. The primary VID shall be equal to the external VID that is defined for the EVC or EVC flow segment. You should already have entered this VID when creating the MAcomp entity belonging to this end of the CFM maintenance flow. If the MAnet name that this MEP is associated with is of type “primary VID”, then the same primary VID must be entered in the Primary VID field.

PS

Ensure that you enter the correct primary VID. It is easy to make a mistake at this point.

P

Note

340

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Parameters page content changes.

Chapter 4 Configuring NEs

Step 9

Use the Admin State drop-down list to set the MEP’s administrative state in In Service. Select Next to continue. In response, the Confirm page appears.

Step 10

Select Finish.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the entity is displayed in the Ethernet Service OAM/CFM window on the Maintenance End Points tab if it was successfully created. Together with the MD identifier, the MAnet identifier and the MEP identifier are used to form the AID for the MEP, and this is displayed in the AID column of the table on the Maintenance End Points tab. Step 11

Select Close to close the Ethernet Service OAM/CFM window.

End of Procedure

Viewing and Modifying MAnet or MAcomp Configuration It is possible to modify the following parameters of the MAnet entities:

User Manual

•

CCM period

•

List of attached MEPs

341

Configuring Ethernet OAM/CFM

This section describes how to view how a MAnet or MAcomp entity is configured.

Procedure Step 1 Step 2

Select the relevant NE in the Managed Elements pane hierarchical list. From the Main Menu, select Configuration -> Ethernet Service OAM/CFM.

Step 3

Select the MAnet that the this end of the CFM maintenance flow belongs to in the hierarchical list of CFM entities in the left hand pane. In response the content in the right hand pane changes.

The current configuration of the MAnet parameters is displayed at the top of the right hand pane.

342

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Ethernet Service OAM/CFM window appears.

Chapter 4 Configuring NEs

Step 4

To change the CCM period, select Modify. In response the Modify window appears.

Step 5

Make changes to the CCM period as follows: a) Select the relevant CCM period from the CCM Period drop-down list. b) Select OK to apply your changes or Cancel to discard them.

Step 6

To change the list of MEPs associated with the MAnet, select Modify.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify List of Attached MEPs appears.

User Manual

343

Configuring Ethernet OAM/CFM

Step 7

Make changes to the MEP list as follows: a) Associate a new MEP with the MAnet by entering the MEP identifier(s) in the MEP IDs field and then selecting Add. If you enter more than one MEP identifier, separate them with commas. In response the new MEP identifier will appear in the List of Attached MEPs section. However, there will be no MEP AID entry together with it, as this MEP has not yet been created. b) Remove a MEP association with the MAnet by selecting the MEP identifier in the List of Attached MEPs section and then selecting Remove. Only MEP identifiers for which the actual MEP AID is not displayed can be removed from the list. To remove a MEP association for a MEP which already exists, you must delete the MEP before removing the MEP identifier from the List of Attached MEPs section.

d) You are required to confirm that you wish to discard the changes by selecting Yes. If you select No you will be returned to the Modify List of Attached MEPs window. Step 8

To view all information for MAcomp, select the Maintenance End Points tab. In response information about the MAcomp appears, no changes are possible.

344

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

c) Select OK to apply your changes or Cancel to discard them. If you select Cancel a warning window will appear.

Chapter 4 Configuring NEs

Step 9

Select Close to close the Ethernet Service OAM/CFM window.

End of Procedure

Viewing and Modifying MEP Configuration For each CFM entity it is possible to view how it is configured. For the MEP entity a standard information window is available, with the tabs State, Fault, Config, Info, FMEP. It is only possible to alter the Start CCM generation parameter of the MEP entity, and to change the Admin State of the MEP entity. This section describes how to view and modify a MEP configuration.

Procedure Step 1 Step 2

Select the relevant NE in the Managed Elements pane hierarchical list. From the Main Menu, select Configuration -> Ethernet Service OAM/CFM.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Ethernet Service OAM/CFM window appears.

User Manual

345

Configuring Ethernet OAM/CFM

Step 3

Select the MAnet that the this end of the CFM maintenance flow belongs to in the hierarchical list of CFM entities in the left hand pane.

Step 4

Select the MEP to view or modify in the Maintenance End Points tab and then select Config. In response the MEP Config window appears.

Step 5

To view states for the MEP entity, select the State tab. In response state information in is displayed.

Step 6

To change the administrative states for the MEP entity, select the State tab and then select Modify.

In response the Modify window appears. Step 7

Change the administrative state as follows: a) Use the Admin State drop-down list to select the relevant administrative state. b) Select OK to apply the change.

346

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the content in the right hand pane changes.

Chapter 4 Configuring NEs

Step 8

To view faults for the MEP entity, select the Fault tab. In response fault information for the MEP appears.

Step 9

To view the configured parameters for the MEP entity, select the Config tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the configured parameters for the MEP appear.

Step 10

To enable or disable generation of CCM frames for this MEP, select the Config tab and then select Modify. In response the Modify window appears.

Step 11

Enable/disable the CCM generation as follows: a) Use the Start CCM generation drop-down list to select the relevant setting, Enable or Disable. b) Select OK to apply the change.

Step 12

User Manual

To view the PDU Content for the MEP, select the Config tab and then select PDU Content.

347

Configuring Ethernet OAM/CFM

Step 13

To view information related to the MEP entity, select the Info tab. In response information related to the MEP appears.

Step 14

To view information about the far-end MEP entity of this MAnet, select the FMEP tab. This information is useful when troubleshooting CFM.

The displayed information is: • • • • • Step 15

The AID of the MEP in the far-end NE. The MAC address of the far-end MEP. The state of the far-end MEP. How long the far-end MEP has been up. Whether any RDI condition exists at the far-end MEP.

Select Close to return to the Ethernet Service OAM/CFM window.

End of Procedure

348

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response information related to the far-end MEP appears.

Chapter 4 Configuring NEs

Deleting CFM Entities This section describes how to delete the various CFM entities for an EVC or EVC segment. A CFM entity cannot be deleted unless its dependent entities already have been deleted. This procedure describes deletion of MEPs, MAcomps, MAnets and MDs, which is the required sequence of deletion to delete a MD. To delete any other CFM entity follow the procedure until you have deleted the entity in question, then stop the procedure.

Procedure Step 1 Step 2

Select the relevant NE in the Managed Elements pane hierarchical list. From the Main Menu, select Configuration -> Ethernet Service OAM/CFM.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Ethernet Service OAM/CFM window appears.

Step 3

To delete a MEP do as follows: a) In the right hand hierarchical list, select the MAnet for which you want to delete a MEP. b) Select the Maintenance End Point tab. c) In the displayed list of MEPs, select the MEP to delete. d) If that MEP’s administrative state is In Service, you must change the administrative state to any other state in order to be allowed to delete the MEP. See “Viewing and Modifying MEP Configuration” on p. 345 for guidance. e) Select Delete. A confirmation message appears.

f)

User Manual

Select OK to confirm the deletion, or cancel to stop it.

349

Configuring Ethernet OAM/CFM

Step 4

To delete a MAcomp entity do as follows: a) In the right hand hierarchical list, select the MAnet for which you want to delete the MAcomp. b) Select the MACOMP tab. c) In the displayed list of MAcomps, select the MAcomp to delete. d) If that MAcomp has a MEP entity entry in the MEP column, the MEP with which the MAnet and MAcomp are associated has not yet been deleted. You must delete this MEP in order to be allowed to delete the MAcomp. See Step 3 for guidance. e) Select Delete. A confirmation message appears.

f)

To delete a MAnet entity do as follows: a) In the left hand hierarchical list, select the MD to which the MAnet belongs. b) In the right hand pane, select the MAnet to delete from the displayed list of MAnets. c) If dependent MAcomps have not yet been deleted, the Delete button is not selectable. You must delete these MAcomps and MEPs in order to be allowed to delete the MAcomp. See Step 4 for guidance. d) Select Delete. e) A confirmation message appears.

f)

350

Select OK to confirm the deletion, or cancel to stop it.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 5

Select OK to confirm the deletion, or cancel to stop it.

Chapter 4 Configuring NEs

Step 6

To delete a MD entity do as follows: a) In the left hand hierarchical list, select the top item, CFM. b) In the right hand pane, select the MD to delete from the displayed list of MDs. c) If dependent MAnets have not yet been deleted, the Delete button is not selectable. You must delete these MAnets in order to be allowed to delete the MD. See Step 5 for guidance. d) Select Delete. e) A confirmation message appears.

f)

Select OK to confirm the deletion, or cancel to stop it.

Step 7

Select OK to return to the Ethernet Service OAM/CFM window.

Step 8

Select [Back] to return to the main menu.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

How to Configure Loop-Backs This instruction describes how to set an external or internal loop-back, and how to release either of the loop backs. External and internal loop-backs are described in the FSP3000R7 Detailed System Description.

Procedure Step 1

Select the client or network side channels that you wish to set a loop for. Use the Entities pane hierarchical entity list for this selection. Such channels are named: CH---C|C1.C8 or CH---N|NE|NW.

User Manual

351

How to Configure Loop-Backs

Step 2

In the Parameter pane, select the Operation tab. In response, the commands that can be issued are displayed.

The last issued loop-back command is displayed in the Loopback Extern/Facility field. Under normal conditions this will show RLS, which indicates that a loop has been released. Step 3

Select the Modify button.

Step 4

Use the Loopback Extern/Facility drop-down list to issue the relevant command. The options are: • External • Facility • RLS, which means to release any loops that currently are active.

Step 5

Select OK to apply the command, or Cancel to discard it.

End of Procedure

352

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Modify Operation window appears.

Chapter 4 Configuring NEs

Managing Cables in the Internal Database In the Element Manager, fiber jumpers interconnect various optical modules installed within a single network element. These jumpers are connected during network element installation and carry both client- and network-side signals from service termination points (such as transponders), through various active or passive optical modules, prior to entering or exiting the network element itself. In this way the jumpers form the internal optical signal path of the network element. Network management systems (NMS), as well as the control plane, require the fiber jumpers to be entered into the internal database. Some network management systems (NMS), as well as the control plane, require these fiber jumpers, as well as the network fiber endpoints to be entered into the internal database.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Physical termination point (PTP) entities are automatically created when port entities for a module are created. These PTPs represent each point in the NE to which a cable can be connected, including network internal cables. The access identifier of a physical termination point is derived from the AID of the port entity. For example: PTP-1-9-N is the physical termination point for the port CH-1-9-N. Network fiber endpoints are represented by Optical Line (OL) entities, and physical termination point (PTP) entities are automatically created for these as well. In this case an optical line can have access identifier OL-1, and the physical termination point is PTP-1A fiber jumper is represented in the database by an interconnection between the PTP entities of the two ports that it interconnects. Therefore, a connection is created in the database between the relevant PTP entities for each fiber jumper in the NE. A connected network fiber endpoint is modeled by an interconnection between the PTP of its OL entity and the PTP of the network port it is connected to. Figure 22:

User Manual

Fiber Jumpers and Physical Termination Points

353

Managing Cables in the Internal Database

This section contains the following topics: How to View Fibers in the Physical Connections Table How to Enter Fibers into the Physical Connections Table Viewing Physical Termination Points

How to View Fibers in the Physical Connections Table This procedure describes how to view all fibers that have been entered into the Physical Connections Table.

Procedure Step 1

Select the relevant NE from the Entity pane hierarchical list.

Step 2

From the Main Menu, select Configuration -> Physical Connections List.

The following information is presented in this window: Column Name

Description

From

This column shows the name of the module that the port/channel in the AID column belongs to. This column shows the name of the module to which port/channel the other end of the cable is connected. This column shows the equipment type of the module that the port/channel in the AID column belongs to.

To

Type

354

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Physical Connections List window appears.

Chapter 4 Configuring NEs

Column Name

Description

Conn

This column shows whether the connection is 2WAY, indicating that is carries both the transmit and receive direction, or whether it is 1WAY carrying one direction. This column shows the class a connection is.

Class

Step 3

•

The class standard indicates that the PTP AIDs do not incur any restriction in functionality. Standard connections are typically used to connect equipment.

•

The class Non Standard indicates that the PTP AIDs may limit the functionality of the NE in some way.

To filter which equipment to display physical connections for, use the Entity, Type and Class drop-down lists.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

For example set Entity to SHELF-1, Type to EDFA-DGCV and Class to Standard. The table will then display only standard physical connections to and from EDFA-DGCV modules in Shelf 1. 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 list by selecting the Print button.

Step 6

Save the list to file by selecting the Save button.

Step 7

Create a new connection by selecting the Create button, see “How to Enter Fibers into the Physical Connections Table” on p. 355.

Step 8

Delete a connection by selecting the connection and then selecting the Delete button.

Step 9

Close the Physical Connections List window by selecting the Close button.

End of Procedure

How to Enter Fibers into the Physical Connections Table This procedure describes how to fill in fiber jumpers or network fibers into the Physical Connections Table.

User Manual

355

Managing Cables in the Internal Database

Requirements •

A cabling plan mapping all internal fiber jumpers in the NE.

•

You will need a thorough understanding of how modules are interconnected in the NE.

Procedure Step 1 Step 2

Select the relevant NE from the Entity pane hierarchical list. From the Main Menu, select Configuration -> Physical Connections List.

In response, the Physical Connections List window appears. Step 3

Select the Create button.

Step 4

Use the Class drop-down list to define which class physical termination points (PTP) that shall be displayed in the To pane. • A PTP of class Standard does not incur any restriction in functionality. Class Standard connections are typically used to connect equipment. • A PTP of class Non Standard may limit the functionality of the NE in some way. • Setting the class to All results in all classes PTP being displayed.

Step 5

In the From and To panes: select the physical termination points (PTP) that represent the cable you want to enter. For a fiber jumper the PTPs represent two ports. For a network fiber there is an optical line PTP and a port PTP. The Create button remains inactive (greyed out) until you have selected a valid connection.

Step 6

Select the type of connection, bi-directional (2WAY) or uni-directional (1WAY), using the Type of Connection radio buttons. Uni-directional connections carry either the transmit or receive traffic and must be used for fiber jumpers attached to EDFAs or attached to modules used as regenerators. Bi-directional connections carry both transmit and receive traffic and represent two fiber jumpers.

356

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Create Physical Connections window appears.

Chapter 4 Configuring NEs

Step 7

Select the Create button to create the connection. If the NCU detects no equipment mismatches or other inconsistencies in the attempted connection, the system indicates that the connection has been created successfully in the database and these entities disappear from the list in the Create Connections window. They will appear in the Physical Connections List window after you have selected Refresh in that window, or automatically if you subscribe to Traps for the Network Element (see “Accessing Trap Recipients” on p. 53).

Step 8

Select Close to close the Create Physical Connections window when you are finished creating connections. You are returned to the Physical Connections List window.

Step 9

Select Close.

End of Procedure

Viewing Physical Termination Points This instruction describes how to view all PTPs in the NE, as well as display detailed information about each PTP. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure Step 1

Select the relevant NE from the Entity pane hierarchical list.

Step 2

From the Main Menu, select Configuration -> PTP Table. In response, the Physical Termination Points window appears.

This window displays the PTPs in the system, as well as whether they are currently part of a connection or not.

User Manual

357

How to Set the Automatic Laser Shutdown Mode

Step 3

Select a PTP in the list, and then select Details. In response the PTP Details window appears. The contents depend on the PTP you selected.

Step 4 Step 5

If there is more information that can be viewed about this PTP, use the Previous and Next buttons to display this. When you are finished, close the PTP Details window by selecting Close.

You will be returned to the Physical Termination Points window. When you are finished viewing PTPs, close the Physical Termination Points window by selecting the Close button.

End of Procedure

How to Set the Automatic Laser Shutdown Mode This instruction describes how to set the automatic laser shutdown mode (ALS) on a channel module. Refer to the Module and System Specification, Appendix A for an overview of the channel modules that support ALS, and an ALS switch-off. ALS is a method of providing eye safety for open fiber connections. When a fiber is detected to be open, the line side transmitter initiates a pulsing behavior to reduce the optical output power and thus provide eye safety. When the fibers are determined to be reconnected, by the end-to-end receivers detecting the pulses, the transmitters are enabled and the link is established again. In certain configurations, the default and normal working condition is to have ALS disabled. Laser safety is not affected by the disabled ALS in this case. An NE with a ROADM is an example of this.

Requirements You must be logged in to the Element Manager using an account with user account with OPERATOR privilege rights.

358

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 6

Chapter 4 Configuring NEs

Procedure Step 1

Select the Network Element in the Entities pane, and expand the relevant shelf and module so you can see the client and network channels.

Step 2

Select the relevant client or network channel where the ALS mode needs to be changed in the Entities pane. In response the Parameters pane displays the parameters for his channel.

Step 3

Select the State tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Parameters pane displays the State parameters.

Step 4

Set the administrative state for the channel to Management, using the Admin State drop-down list. Your choice here depends on the situation requiring the ALS mode change. Laser safety will not be affected.

User Manual

Step 5

Select the Config tab.

Step 6

Select the Modify button.

Step 7

To enable the ALS mechanism, select either ALS or SDH-ALS from the ALS Mode drop-down list. Use “SDH-ALS” if your channel carries SDH/SONET traffic (e.g. STM-16).

Step 8

To disable the ALS mechanism, select NONE from the ALS Mode drop-down list. As a result, the channel module transmitter will be on.

359

How to Force a Laser On

Step 9

Select OK to save your setting or Cancel to discard them.

Step 10

Select the State tab.

Step 11

Change the administrative state to the value it was before you set the ALS mode, or select Automatic in Service.

End of Procedure

How to Force a Laser On This section describes how to force a laser on. Once a laser has been forced on the laser release timer (see “How to Set the Forced-Laser Fallback/Release Timer” on p. 362) starts running. When the specified time is reached, the laser is released.

Requirements You must be logged in to the Element Manager with the ADMIN account

Step 1

Select the Network Element in the Entities pane, and expand the relevant shelf and module so you can see the client and network channels.

Step 2

Select the relevant client or network channel where the Laser shall be forced on or released, in the Entities pane. In response the Parameters pane displays the parameters for his channel.

Step 3

Select the State tab. In response the Parameters pane displays the State parameters.

Step 4

Set the administrative state for the channel to Maintenance, using the Admin State drop-down list.

360

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

Chapter 4 Configuring NEs

Step 5

Select the Operation tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Parameters pane displays the Operation parameters.

Step 6

Use the Laser Forced ON drop-down list to set the relevant laser operation: • Select OPR (operate), to force a laser on. This setting will override the ALS setting for the laser and should only be used for diagnostic purposes. • Select RLS (release), to release a forced-on laser. If the ALS mechanism is enabled, it will now switch on or off the laser appropriately.

Step 7

Select Apply to save your setting. In response the laser is forced on and the laser release timer starts running. The laser release timer can be observed on the Operation tab. If it does not show progress, use the Refresh button.

Step 8

Select the State tab.

Step 9

Use the Admin State drop-down list to set the administrative state to the state it was before you set the Laser Forced ON parameter, or select Automatic in Service.

End of Procedure

User Manual

361

How to Set the Forced-Laser Fallback/Release Timer

How to Set the Forced-Laser Fallback/Release Timer When a force-laser command is issued, a timer starts running. When a configurable amount of time has elapsed, the forced setting is autonomously released. Such a timer is commonly called a fallback or a release timer. It is normally not necessary to change factory default setting of this timer. This section contains the instruction to change this timer. The change is non-service affecting, and affects all modules in the NE within 60 seconds after the change is applied. The change of this parameter is recorded in the database change log. This makes it possible to reconstruct actions on system-wide parameters.

Procedure Step 1

Double-click the relevant Network Element in the NE Pane. In response, the Parameter pane displays the System page.

Step 2

Select the Database tab.

Step 3

Select the Modify button on the Database tab. In response, the Modify window appears.

Step 4

Enter the new value for the forced-laser fallback timer in the Laser RLS DEF Timer field.

The default value is 1440 minutes. The timer is configurable between 0 - 1440 minutes with 1 minute granularity. Step 5

Select OK to apply the change, or Cancel to discard the change.

End of Procedure

362

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Parameter pane displays the Database page. In this page parameters that affect the database are displayed.

Chapter 4 Configuring NEs

How to Allow Forced Deletion of Entities In order to delete an entity, its dependent entities must first have been deleted. In some situations it is cumbersome to delete each of the dependent entities manually. The FSP3000R7 can do this deletion of dependent entities automatically, if the Force Deletion feature has been enabled. This section contains the instruction to enable the Force Deletion feature. The change is non-service affecting, and affects all modules in the NE within 60 seconds after the change is applied. The change of this parameter is recorded in the database change log. This makes it possible to reconstruct actions on system-wide parameters.

Procedure Step 1

Double-click the relevant Network Element in the NE Pane. In response, the Parameter pane displays the System page.

Step 2

Select the Database tab. In response, the Parameter pane displays the Database page. In this page parameters that affect the database are displayed.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 3

Select the Modify button on the Database tab. In response, the Modify window appears.

Step 4

Use the Force Delete drop-down list and select Enable to enable the Force Delete feature. To disable it, select Disable.

Step 5

Select OK to apply the change, or Cancel to discard the change.

End of Procedure

Enabling Use of SCU Ring Interconnection Within a NE, the SCUs and ROADMs in each shelf can be interconnected in both a chain or ring topology. Using the ring topology requires that the SCUs and ROADMs have equipment software (firmware) version R8.2. Therefore use of the ring topology is disabled by default, and must be actively enabled by the

User Manual

363

How to Change Equipment Capabilities

operator. This supports software update without loosing connection to shelves without the correct SCU or ROADM equipment software version. This instruction describes how to enable SCU interconnection for a NE which previously did not support this.

Requirements •

All SCUs and ROADMs in the NE must be running Release 8.2 equipment software.

•

All shelves must have been registered in the database.

This instruction describes how to enable SCU interconnection for a NE which previously did not support this.

Procedure Step 1

Select the relevant NE in the Managed Elements pane. In response the Parameters pane displays all information about the NE.

Step 2

Select the Database tab. In response all information related to internal database is displayed. Select Modify. In response the Modify window appears.

Step 4

Use the SCU ring intercon. drop-down list to enable or disable use of Ring interconnection.

Step 5

Select OK to apply the change. If the SCUs and ROADMS are registered, running the correct equipment software and cabled correctly, they should all be manageable.

End of Procedure

How to Change Equipment Capabilities This section describes how to change the capability level of a module. The highest possible capability level contains all features the module can support. After

364

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 3

Chapter 4 Configuring NEs

updating the NE software, it is wise to check that the equipment capability is configured correctly in the case that expected features can not be found.

Procedure Step 1

Select the module to change capability for. Use the Entity pane hierarchical entity list for this selection.

Step 2

Select the Config tab in the Parameter pane.

Step 3

Note the current capability as displayed in the Prov. Capability level field.

Step 4

Select the Modify button.

Step 5

Use the Prov. Capability level drop-down list to select the correct capability level.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

For a 10TCC-PC-4GU module, the options could for example be: • • •

Level 0: Basic feature set. Level 1: FC400-C, TCA, PM-RST, RPS Level 2: STM64/OC192-N

The release notes of the currently running software version will contain information about the supported capabilities. Step 6

Select OK to apply the change, or Cancel to discard the change.

End of Procedure

How to Configure TIF Contacts This section describes how to configure the telemetry interface (TIF) contacts on the UTM module. There are 16 input and 4 output port contacts that can be used to manage alarms. You may configure whether the input ports (TIFI) use an open or closed contact to trigger an alarm. Alarm groups may be assigned to the output ports (TIFO), one group per port. There are three categories of alarms: NE alarms, FCU alarms, PSU alarms.

Procedure Step 1

Select the UTM module in the Entity pane hierarchical entity list. If it is not listed, you must first create the UTM module. In response the dependent telemetry input (TIFI) and output (TIFO) ports are displayed.

User Manual

365

How to Configure TIF Contacts

Step 2

Make a choice: • Configure each TIF input port that you will use, as described in Step 3 to Step 9. • Assign an alarm group to each TIF output port that you will use as described in Step 10 to Step 14

Step 3

Select the relevant input port under the UTM module in the hierarchical entity list.

Step 4

Select the Config tab in the Parameter pane.

Step 5

Select the Modify button. In response the Modify window displays.

Step 6

An alarm will be triggered either when the TIF input contact is closed, or when it is open. Use the Invert TIF input logic drop-down list to set this behavior for the TIF input.

Step 7

Enter the alarm message that shall be displayed when the alarm is raised. Use the TIF alarm message field. The alarm and configured alarm message are displayed in the Current Conditions window, and in the Event Log.

Step 8

Enter the severity for this TIF input alarm into the TIF alarm type field. Use the following abbreviations: CR=critical, MJ=major, MN=minor.

PS

If you do not enter a severity, this TIF input port will be automatically disabled.

Note

Step 9

366

Select OK to apply the change, or Cancel to discard the change.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This tab displays the current settings for this TIF input contact.

Chapter 4 Configuring NEs

Step 10

Select the relevant output port under the UTM module in the hierarchical entity list.

Step 11

Select the Config tab in the Parameter pane.

This tab displays the current settings for this TIF input contact. Step 12

Select the Modify button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify window displays.

Step 13

Use the TIF output provision drop-down list to select which alarm group that this TIF output shall indicate.

Step 14

Select OK to apply the change, or Cancel to discard the change.

End of Procedure

User Manual

367

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Configure TIF Contacts

368

User Manual

Chapter 5 Monitoring NEs This section describes how to monitor the equipment state, current conditions (for example, faults), events, performance and physical layer measurements.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The following topics are provided: Monitoring Faults, which gives a basic understanding of faults and current conditions, and how to view these. Monitoring Performance, which describes how to view physical monitoring measurements and performance monitoring records. Monitoring States, which gives a basic understanding of states and how to view them.

Monitoring Faults The Element Manager notifies the operator when faults, or conditions, occur. For quick overview purposes, the Element Manager indicates currently present conditions in the Managed Elements pane, by coloring the “ball” icon. In the Equipment pane, currently present conditions for the client and network interfaces and for the power supplies are indicated by a condition balloon symbol. The color and letter code inside the condition balloon symbol indicates the severity of the condition. Severity is indicated using standardized coding and the relationship between color, code and severity is shown in Table 10. When multiple conditions are present, the color and letter code of the most severe of these conditions is the one displayed. The number indicates the total number of condi-

User Manual

369

Monitoring Faults

tions present. The plus sign is displayed when there are conditions present with more than two different severities. Table 10:

Alarm Color Coding

Severity Level

Color

Letter Code

Cleared NotAlarmed Not Reported Minor Major Critical

Green Cyan Grey Yellow Orange Red

none N none m M C

Comment no alarms are present this alarm is not reported

You can find more information under the following topics: “How to View Current Conditions for a Single Entity or NE” on p. 370 explains how current conditions for the entities are viewed from the Fault tab. “How to View Current Conditions for All Entities in an NE” on p. 372 explains how current conditions for the entities are viewed from the Current Conditions window.

“How to Manually Change an Individual Condition’s Severity” on p. 375 provides information about setting severities manually. The severity of each condition for each entity can be user-defined. “Changing Condition Severities with an Alarm Profile” on p. 377 provides information about setting severities by using an alarm profile. Alarm profiles can be exported and imported to other NEs. “How to Set the Timer for the Fault Cause Persistency Filter” on p. 386 describes how to change the fault cause persistency filter timer. This is normally not necessary to change. In some situations it is desirable to disable reporting of one or more conditions from the NE in order to inhibit a specific alarm. For more details about Fault Management, see the FSP 3000R7 Detailed System Description.

How to View Current Conditions for a Single Entity or NE This instruction describes how to view current conditions for an entity or a network element.

Procedure Step 1

Double-click the relevant NE in the Managed Elements pane. In response, the Information pane displays.

370

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“How to Manually Change an Individual Condition’s Severity” on p. 375 explains how the Element Manager provides a history of events on a per NE basis.

Chapter 5 Monitoring NEs

Step 2

Select the entity or NE you want to view parameters for in the Entities pane. In response, all available information about the entity or NE is displayed in the Parameters pane.

Step 3

Select the Fault tab in the Parameters pane. In response all conditions for the selected entity or NE are displayed.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In the Current Conditions section the list of current conditions is displayed.

End of Procedure

User Manual

371

Monitoring Faults

How to View Current Conditions for All Entities in an NE This instruction describes how to view currents conditions for all entities in an NE. The data can be exported to both the XML and CSV format. Opening the exported 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.

Procedure Step 1

Select the relevant NE in the Managed Elements pane.

Step 2

From the Main Menu, select Fault -> Current Conditions.

The Counters section gives a summary of how many conditions there are, of each severity type. The total number of conditions is displayed under the table of conditions. The table of conditions are displayed, using the following columns: Column Name

Description

Severity

This column shows the condition severity. The severities are described in Table 10. This column shows the date and time that the event occurred on the NE. Note that the sequence that events occur in and the sequence that events are logged in may be different. This column shows the name of the condition. This column shows from which entity the event originates, using the AID address to identify it. This column shows whether the condition is service affecting or not.

Time

Condition Location Service Affecting

372

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Current Conditions window appears.

Chapter 5 Monitoring NEs

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 3

Customize which conditions to display in the Current Conditions table as follows: • Display only conditions of a specific severity by using the Severity drop-down list in the Filter section. • Display only conditions originating from a specific piece of equipment, for example a module. Use the Equipment drop-down list in the Filter section. • 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 Event Log. • Select Save to save the Event Log as a comma separated file. • Select Refresh to refresh the list an get the newest information.

Step 5

Select Close to finish viewing the Event Log.

End of Procedure

User Manual

373

Monitoring Faults

How to View the Event Log This instruction describes how to view the event log for an NE. The event log can be exported to both the XML and CSV format. Opening the exported 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.

Procedure Step 1

Select the relevant NE in the Managed Elements pane.

Step 2

From the Main Menu, select Fault -> Event Log

Column Name

Description

Id

This field shows the sequential number the NE assigns to each event when it is logged on the NE. This field shows the event severity. Events that are alarms use the severities described in Table 10. All other events have severity “Information”. This field shows the date and time that the event occurred on the NE. Note that the sequence that events occur in and the sequence that events are logged in may be different. This field shows from which entity the event originates, using the AID address to identify it. This field gives a description of the event.

Severity

Date/Time

Source Description Step 3

374

If appropriate you can: • Select Clear to erase the current Event Log and start afresh. • Select Print to print the Event Log. • Select Save to save the Event Log as a comma separated file. • Select Refresh to refresh the list an get the newest information.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Event Log window appears.

Chapter 5 Monitoring NEs

Step 4

Select Close to finish viewing the Event Log.

End of Procedure

How to Manually Change an Individual Condition’s Severity This instruction describes how to manually change the severity for a current condition on an entity or an NE.

Procedure Step 1

Double-click the relevant NE in the NE Pane. In response, the Information pane displays.

Step 2

Select the entity or NE to view parameters for in the Entity pane. In response, all available information about the entity or NE is displayed in the Parameters pane.

Step 3

Select the Fault tab in the Parameters pane.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response all conditions for the selected entity or NE are displayed.

In the Severities section, each condition that is relevant for this entity or NE is displayed in the Condition column. The belonging severity is displayed in the Severity column.

User Manual

375

Monitoring Faults

Step 4

Select the Modify button. In response, the Modify Severities window appears.

Step 5

For the condition you want to change severity for, click the condition in the Severity column. From the list that appears, select the new severity.

Step 6

Select OK to apply the new severity, or Cancel to discard it.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

376

User Manual

Chapter 5 Monitoring NEs

Changing Condition Severities with an Alarm Profile The default assigned severity for a condition type can be changed for all entities to which it is applicable, by applying an alarm profile. An alarm profile can be used in combination with changing the severity manually for a condition on an entity. The last applied change, either by alarm profile application or individual change, is the one that has effect. Initially the alarm profile contains all conditions, with severity set to Default. This setting indicates that the factory default severity setting shall be used. This alarm profile will have no effect on existing or future conditions if applied. Only severity settings with a value different from Default in the alarm profile will have effect on future and existing conditions. Thus, conditions which you wish to change severities for manually, should be left at the factory default values. Changing a condition’s setting in the alarm profile from a specific value back to Default effectively “removes” it from the alarm profile. The severity of an existing condition of this type will not be changed. Future conditions of this type will however have the factory default severity, unless a manual severity change has been made. This behavior secures that any manual severity change for this condition is not overwritten by the alarm profile. Thus the severities in the system are the default defined ones unless one has changed the severity for a condition manually, or applied an alarm profile. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The alarm profile resides together with the data base, and is backed-up together with the data base when a data-base backup is done. An alarm profile created on one NE, can be exported, stored, and imported to another NE, and applied to that NE. This section describes how to create, modify, reset, export and import an alarm profile. The following topics are provided: “How to Modify the Alarm Profile” on p. 377 “How to Reset an Alarm Profile” on p. 380 “How to Export an Alarm Profile” on p. 381 “How to Import a Alarm Profile” on p. 383

How to Modify the Alarm Profile Initially the alarm profile contains all conditions, with severity set to Default. This setting indicates that the factory default severity setting shall be used. This alarm profile will have no effect on existing or future conditions if applied. To create a meaningful alarm profile, you must select each condition type that you wish to change the severity for, and change the severity value from Default to the new value. There are a large amount of conditions in the system, and to make it easier to navigate to the relevant conditions, they are sorted according to which entity type they are relevant for. These entity types are classified by their access identifier (AID) alike mnemonics. For example: EQPT contains all conditions related to equipment, while CH contains all conditions related to channel entities. The content of the alarm profile has effect on all future conditions immediately after a condition is entered into the alarm profile (its severity is set different from

User Manual

377

Monitoring Faults

Default). The content of an alarm profile can also be applied to the existing conditions in the system, if relevant. If you wish to start from scratch with an empty alarm profile file instead of modifying an existing one, go to 6.1.5.2 “How to Reset an Alarm Profile”, p. 156. This instruction describes how to create an alarm profile on the NE.

Procedure Step 1

Double-click the relevant NE in the NE Pane.

Step 2

From the Main Menu, select Fault -> Alarm Profile.

Step 3

Use the AID Type drop-down list to select the relevant group of conditions to display in order to find the condition you wish to change severity for.

Step 4

Browse the list until you find the relevant condition, and select it.

Step 5

There are two ways of changing the condition’s severity: • To follow the quickest way of modifying the severity, go to Step 6 • To follow the standard way of modifying an item, go to Step 10

Step 6

Right-click the severity for this condition in the Severity column. In response a drop-down menu appears with the item Set Severity in it.

Step 7

Move the mouse pointer over the Set Severity item, and the available severities appear.

Step 8

Select the relevant severity by clicking it. In response the progress of the entry to the alarm profile is shown in the lower, left corner of the Alarm Profile window.

Step 9

378

Continue from Step 14.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Alarm Profile window appears, with the Active Profile tab active.

Chapter 5 Monitoring NEs

Step 10

Select Modify to change the severity. In response the Modify Alarm Profile Severities window appears.

Step 11

The condition you selected in Step 4 is already selected. If you happened to have made the wrong selection, you can select a different condition now.

Step 12

Click the displayed severity for the selected condition, and select a new severity from the drop-down list that appears.

Step 13

Select OK to apply the new severity value.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify Alarm Profile Severities window is closed, and the progress of the entry to the alarm profile is shown in the lower, left corner of the Alarm Profile window. Step 14

Ensure that your change is visible in the Alarm Profile window. If it is not visible: Select Refresh to update the content of the Alarm Profile window.

Step 15

Repeat Step 3 through Step 14 for each condition that you wish to change the severity for by using the alarm profile.

Step 16

If you wish to apply the alarm profile to all existing conditions in the NE: Select Severity Re-synch. You can check that the alarm profile had effect on existing conditions by looking at the list of current conditions for the NE, see “How to View Current Conditions for All Entities in an NE” on p. 372 for guidance.

End of Procedure

User Manual

379

Monitoring Faults

How to Reset an Alarm Profile Initially the alarm profile contains all conditions, with severity set to Default. This setting indicates that the factory default severity setting shall be used. This alarm profile will have no effect on existing or future conditions if applied. To create a meaningful alarm profile, you must select each condition type that you wish to change the severity for, and change the severity value from Default to the new value. If you wish to erase all changes you have made to the alarm profile, you can reset the alarm profile to its initial state. This means that the alarm profile no longer has any effect on the existing and future conditions. This instruction describes how to reset the alarm profile to its initial state.

Procedure Step 1

Double-click the relevant NE in the NE Pane.

Step 2

From the Main Menu, select Fault -> Alarm Profile.

380

Step 3

Consider whether it makes sense to backup the existing alarm profile before resetting it. See “How to Export an Alarm Profile” on p. 381 for guidance.

Step 4

Select the Manage Profiles tab.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Alarm Profile window appears, with the Active Profile tab active.

Chapter 5 Monitoring NEs

Step 5

Select Reset to Factory Default in the Active alarm profile section. In response a warning window appears.

Step 6

Every setting in the existing alarm profile will be erased. Select Yes to continue the reset, or No to stop it. In response: • •

The alarm profile file will be reset to factory defaults, that is, all severity entries are erased by setting them back to be Default. The activation date and time for the alarm profile will be updated, since this is equivalent to importing a new alarm profile. This can be seen by the activation date in the Active alarm profile section.

End of Procedure

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to Export an Alarm Profile An alarm profile can be exported from one NE, and imported to each other NE in the network. This allows you to apply the same severity changes to all NEs in a network. It is not necessary to export an alarm profile in order to back it up. Alarm profiles are part of the data base and are thus backed up when a data base back-up is done. This instruction describes how to export an alarm profile to an external storage place.

Procedure

User Manual

Step 1

Ensure that you have access to a remote file server that the NE can reach.

Step 2

Double-click the NE in the Managed Elements pane.

381

Monitoring Faults

Step 3

From the Main Menu, select Fault -> Alarm Profile. In response, the Alarm Profile window appears, with the Active Profile tab active.

Select the Manage Profiles tab. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 4

382

User Manual

Chapter 5 Monitoring NEs

Step 5

Select Backup to move a copy of the alarm profile file to the file download area of the NE. In response a warning window appears.

Step 6

Select Yes to start the backup. In response the progress of the copying is displayed in the lower, left corner of the Manage Profiles tab.

Step 7

Step 8

Select the alarm profile that now is in the NE File Area list. The file name has the extension ALP, and is built up by the following elements: F7, software package version number, date (yymmdd), time (hhmm), NE IP address. For example: F7008020_080905_1246_192_168_165_195.ALP Download the alarm profile file to a remote file server by selecting the Download button and entering the required information. See “How to

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Download Files to the NE” on p. 453 for guidance on using this window. Step 9

If required, move the alarm profile from the remote file server to a safe storage place, so you later can import it to other NEs.

End of Procedure

How to Import a Alarm Profile An alarm profile can be exported from one NE, and imported to each other NE in the network. This allows you to apply the same severity changes to all NEs in a network. This instruction describes how to import an alarm profile to an NE, and activate it.

Procedure

User Manual

Step 1

Move the file that you wish to import to a remote file server that the NE can reach.

Step 2

Double-click the NE in the Managed Elements pane.

383

Monitoring Faults

Step 3

From the Main Menu, select Fault -> Alarm Profile.

Step 4

Select the Manage Profiles tab.

Step 5

Select Download to move a copy of the alarm profile file from the remote file server to the file download area of the NE. See “How to Download Files to the NE” on p. 453 for guidance. When the download is complete, the alarm profile will appear in the NE File Area list.

384

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Alarm Profile window appears, with the Active Profile tab active.

Chapter 5 Monitoring NEs

Step 6

Select the correct alarm profile file in the NE File Area list. The file name has the extension ALP, and is built up by the following elements: F7, software package version number, date (yymmdd), time (hhmm), NE IP address. For example: F7008020_080905_1246_192_168_165_195.ALP The version number and creation date can in addition to the file name be used to identify the correct version.

Step 7

Transfer the alarm profile into the standby file area on the NE by selecting Install. In response a warning window appears.

Step 8

Select Yes to start the transfer. In response the progress of the transfer is displayed in the lower, left corner of the Manage Profiles tab.

Step 9

Ensure that the alarm profile now is present in the Standby alarm pro-

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

file section.

Step 10

Make the alarm profile in the standby area active in the active area by selecting Activate. Only alarm profiles that are in the Active area are active. In response a warning window appears.

Step 11

Select Yes to start the transfer.

Step 12

In response the progress of the transfer is displayed in the lower, left corner of the Manage Profiles tab.

Step 13

Ensure that the alarm profile now can be seen in the Active alarm profile section.

The alarm profile has now been imported and activated on the NE. Download the alarm profile file to a remote file server by selecting the Download button and entering the required information. See “How to

Download Files to the NE” on p. 453 for guidance on using this window.

User Manual

385

Monitoring Faults

Step 14

If required, move the alarm profile from the remote file server to a safe storage place, so you later can import it to other NEs.

End of Procedure

How to Set the Timer for the Fault Cause Persistency Filter This instruction describes how to configure the activation and deactivation times of the fault cause persistency filter (FCPF). However, normally it is not necessary to change the factory default values. The FCPF raises alarms only after being present for a configurable amount of time (Alarm Activation Time). It clears them only after they are gone for the configured amount of time (Alarm Deactivation Time). These configurable FCPF soak periods will take effect system wide, i.e. concerning all modules of that NE. It becomes effective for all modules within 60 seconds but is non-service affecting (NSA). To be able to reconstruct actions on system wide parameters, changes to these soak periods will be recorded in the database change log.

The frequency of a single alarm event shall not be higher than 1 second, i.e. the sum of activation and deactivation times shall always be > 1 second in order to prevent toggling alarms.

Procedure Step 1

Double-click the relevant NE in the Managed Elements pane. In response, the Information pane displays.

386

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Requirements:

Chapter 5 Monitoring NEs

Step 2

Select the System tab in the Parameters pane. In response, all available information about the system is displayed in the System pane.

Step 3

Select the Modify button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Modify Operation window appears.

Step 4

Enter the new alarm activation time in the Alarm Activation Time field. The alarm activation time is configurable between 0 - 10 seconds with granularity of 500 ms. The default value for the alarm activation time is 2.5 seconds.

Step 5

Enter the new alarm de-activation time in the Alarm Deactivation Time field. The alarm de-activation time is configurable between 0 - 10 seconds with granularity of 500 ms. The default value for the alarm activation time is 10 seconds.

User Manual

387

Monitoring Performance

Step 6

Select OK to apply the changes, or Cancel to discard them.

End of Procedure

Monitoring Performance

In addition, the FSP3000R7 provides instant measurements of some physical layer parameters that are not logged in records. They are thus only viewable as instantaneous measurements. A detailed description of performance management in the FSP3000R7 can be found in the FSP3000R7 Detailed System Description. This includes information about which performance parameters are monitored for each layer and each module, descriptions of each performance parameter and a detailed description of what information is logged in the records. Information about Threshold Crossing Alerts (TCAs) can also be found in the FSP3000R7 Detailed System Description. Performance monitoring is available for all active modules. However, the different types of performance monitoring are not available for all modules. The following topics are provided: “How to View Channel Performance per NE” on p. 389 “How to View Single Channel Performance” on p. 390 “How to View ROADM Performance” on p. 392 “How to View Reconfigurable Filter Performance” on p. 395 “How to Reset Performance Records” on p. 398 “How to Print Historic Performance Records” on p. 399 “How to Export Historic Performance Records” on p. 400 “How to View Physical Layer Measurements” on p. 400 “How to View Physical Layer Measurements” on p. 400 “How to View Thresholds for Threshold Crossing Alerts” on p. 402

388

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The FSP3000R7 supports monitoring of performance at the physical layer for modules and ports, and at the data layer for ports and services. The results of the monitoring are logged in records with recording intervals of 15 minutes, 24 hours or 1 week for physical layer monitoring and in intervals of 15 minutes and 24 hours for data layer monitoring. The Network Element stores the last ninety-six 15 minutes records, thirty-one 24 hours records and fifty-two 1 week records, representing a 1 day, 1 month and 1 year history respectively. Element Manager provides thresholds that can be set for physical layer performance measurements, so that an alert (Threshold Crossing Alert) is generated in the case a performance measurement crosses this threshold (see “How to Configure TCA Thresholds” on p. 321). This functionality is an aid for the person responsible for monitoring performance.

Chapter 5 Monitoring NEs

How to View Channel Performance per NE This instruction describes how to view instantaneous measurements and performance records for all channels in an NE.

Procedure Step 1

Select the relevant NE in the Managed Elements pane hierarchical list.

Step 2

From the Main Menu, select Performance -> Performance Data. In response, the Performance Data window will appear.

Step 3

Select which channel to view performance data for, by using the Monitoring Point drop-down list. The drop-down list is populated from the provisioned channels. Channels are identified by their AID address.

Step 4

Select which type of performance data to view, by using the Monitoring Type drop-down list. The available options in this list depend on what is selected for Monitoring Point.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the performance records for the selected monitoring point and type are displayed in the Performance Data window. The options and sections that appear in this window, depend on whether you are monitoring performance at the physical or data layer.

Step 5

User Manual

Select the relevant Intervals radio button to specify which interval you want to view records for. Depending on the selected Monitoring Type, this can be 15 minutes or 24 hours for data layer monitoring and 15 minutes, 24 hours or 1 week for physical layer monitoring.

389

Monitoring Performance

Step 6

Select from the following: • For data layer monitoring: expand the Current Record section to view the current records for this performance data type and expand the Threshold section to view thresholds for the counters. • For physical layer monitoring: expand the Current section to view the high and low threshold values and current value. The counters and thresholds are described in the

FSP 3000R7Detailed System Description. Step 7

To view the historic records for this performance data type, expand the History Record section.

Step 8

To view the historic records in a table, select the Table tab in the History Records section. This section then displays a table, where each row represents a record of performance counters. Each column contains a performance counter. In addition there is a column that indicates the validity of each record. The counters and thresholds are described in the

FSP 3000R7Detailed System Description. Step 9

To view the historic records in a chart, select the Chart tab in the HisThis section then displays a chart, with one colored line for each performance counter. A maximum of 16 records are shown in the chart view. The time and height of the records is indicated along the relevant axis. The counters and thresholds are described in the

FSP 3000R7Detailed System Description. Step 10

The information in the Performance Data window is not automatically updated. In order to update it: Select the Refresh button.

Step 11

To conclude viewing performance records, select Close.

End of Procedure

How to View Single Channel Performance This instruction describes how to view instantaneous measurements and performance records for one single channel.

Procedure Step 1

Select the relevant channel in the Entities pane. In response, all available information about the entity is displayed in the Parameters pane.

Step 2

Select the Monitoring tab in the Parameters pane. In response all monitored data is displayed.

390

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

tory Records section.

Chapter 5 Monitoring NEs

Step 3

Select which type of performance data to view, by using the Monitoring Type drop-down list. The available options in this list depend on which channel you selected in Step 1.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the performance records for the selected monitoring point and type are displayed. The options and sections that appear in this window, depend on whether you are monitoring performance at the physical or data layer.

Step 4

In the History section, select the relevant Intervals radio button to specify which interval you want to view records for. Depending on the selected Monitoring Type, this can be 15 minutes or 24 hours for data layer monitoring and 15 minutes, 24 hours or 1 week for physical layer monitoring.

Step 5

Make a decision: • For data layer monitoring: expand the Current Record section to view the current records for this performance data type and expand the Threshold section to view thresholds for the counters. • For physical layer monitoring: expand the Current section to view the high and low threshold values and current values. The counters and thresholds are described in the

FSP 3000R7Detailed System Description. Step 6

To view the historic records for this performance data type, expand the History Record section.

Step 7

To view the historic records in a table, select the Table tab in the History Records section. This section then displays a table, where each row represents a record of performance counters. Each column contains a performance counter. In addition there is a column that indicates the validity of each record. The performance counters are described in the FSP 3000R7Detailed

System Description.

User Manual

391

Monitoring Performance

Step 8

To view the historic records in a chart, select the Chart tab in the History Records section.

This section then displays a chart, with one colored line for each performance counter. A maximum of 16 records are shown in the chart view. The time and height of the records is indicated along the relevant axis. The performance counters are described in the FSP 3000R7Detailed

System Description Step 9

The information in the Monitoring tab is not automatically updated. In order to update it: Select the Refresh button.

Step 10

To conclude viewing performance records, select Close.

End of Procedure

How to View ROADM Performance

Procedure Step 1

Right-click the relevant NE in the Managed Elements pane and select ROADM Performance Data. In response the ROADM Performance Data window appears.

Step 2

392

Make a decision: • To view performance data for the ports of a ROADM module: Select the Port PMs tab, and continue from Step 3. • To view performance data for the network side channels (VCHs) of a ROADM module: Select the Channel PMs tab.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This instruction describes how to view instantaneous measurements of optical transmit and receive power for the ROADM network channels and associated VCHs. This provides the operator with an overview for monitoring channel power in the Network Element.

Chapter 5 Monitoring NEs

Step 3

Select which ROADM module to display by using the ROADM Module drop-down list. For example ROADM of type ROADM-C80 in shelf 1, slot 6, where this is ROADM number 1: MOD-1-6, ROADM-C70, #1.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The window displays the following information: Column Name

Description

AID

This column shows the AID of the port, the syntax is OM--- This field shows the admin state of the port. Only ports that are In Service may be used to create a cross-connection.severity. This field shows the item that is being measured. This field shows the measured value. The value is updated when you select Refresh.

Admin State

Monitoring Type Current

Step 4

Select which ROADM module to display by using the ROADM Module drop-down list. For example ROADM of type ROADM-C80 in shelf 1, slot 6, where this is ROADM number 1: MOD-1-6, ROADM-C70, #1.

Step 5

Select which channels to view measurements for by using the Channels drop-down list. The options are:

• •

User Manual

All, which results all channels being listed, regardless of whether they are used in a cross-connection or not. In Service, which results in only channels which are used in cross-connections that are enabled being listed. An enabled cross-connection has administrative state In Service.

393

Monitoring Performance

Step 6

Select the performance item that you wish to view measurements for by using the Monitoring Type drop-down list. In response, the specified items are displayed.

Column Name

Description

AID

This column shows the AID of the port, the syntax is OM--- This column shows the frequency of the channel. This field shows the admin state of the cross-connection that uses this channel. The value UAS indicates that no cross-connection using this channel exists. In Service indicates that the cross-connection is active, allowing traffic to flow through. This field shows the channel spacing that is used for each channel, either 50 GHz or 100 GHz spacing. This field shows the configured setpoint for this channel. This field shows the measured power level for the channel.

Frequency CRS Admin State

Channel Spacing

Setpoint Current

Step 7

The information in the window is not automatically updated. In order to update it: Select the Refresh button.

Step 8

To conclude viewing performance records, select Close.

End of Procedure

394

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The window displays the following information:

Chapter 5 Monitoring NEs

How to View Reconfigurable Filter Performance This instruction describes how to view optical power monitoring performance for the ports on the reconfigurable filters, and how to view information of which channels are provisioned on which ports.

Procedure Step 1

Select the relevant NE in the NE pane.

Step 2

Select Performance -> Reconfigurable Filters.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Reconfigurable Filters table appears.

Step 3

User Manual

Determine the port that a particular channel is provisioned on by selecting the Channel tab.

395

Monitoring Performance

Step 4

Use the Filter Group/ROADM Number drop-down list to select the relevant filter group to display channels for. This list contains all of the supported filter groups (“#1” – “#8”) with the number of CCM modules in the filter group in parenthesis. For example: “#1 (3 modules)”. In response the channel table fills up.

396

Column Name

Description

Frequency [THz] AID

This shows the frequency of the channel in Terahertz. This is the access identifier of the corresponding filter module port that carries the channel.

Step 5

Make a note of the AID for the relevant channel.

Step 6

Select the Port tab.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The following information is displayed for each channel.

Chapter 5 Monitoring NEs

Step 7

Based on the port AID you found in Step 5, use the Module drop-down list to select the corresponding filter module. In response, the Reconfigurable Filters table is updated with the power monitoring information of all the ports on this module.

The following information is displayed for each table entry: Column Name

Description

AID

This is the access identifier of the port entity used by the corresponding filter module. This shows the administrative state of the relevant port. This indicates whether the entry is transmit optical power (Tx) or receive optical power (Rx). This indicates the number of channels provisioned to carry traffic on the port but does not count channels provisioned on the disabled (DSBLD) client ports. This is the target optical transmit power of the channel and is set to achieve the desired launch power for the connected channel module. The optimal setpoint is determined by the corresponding channel module’s receive power range. This is the current optical power measurement for the port.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Admin State Monitoring Type Active Channels

Setpoint [dBm]

Current [dBm]

Step 8

Use the Refresh button to update the table.

Step 9

Select Close to return to the main menu.

End of Procedure

User Manual

397

Monitoring Performance

How to Reset Performance Records After provisioning an entity for which data-layer performance monitoring is performed, the data-layer performance records should be reset, so as not to include counting during the provisioning period. This instruction describes how to reset data-layer performance records.

Procedure Step 1

Select the relevant entity in the Entities pane. In response, all available information about the entity is displayed in the Parameters pane.

Step 2

Select the Monitoring tab in the Parameters pane. In response all monitored data is displayed.

Step 3

Select which type of data-layer performance records to view, by using the Monitoring Type drop-down list. The available options in this list depend on which entity you selected in Step 1.

Step 4

Select Reset. In response the Modify window appears.

Step 5

398

Use the Data-layer PM reset drop-down list to specify either: • A reset of only the current records for this entity, by selecting the Current only option. • A reset of both current and historic records for this entity, by selecting the Current + historic option.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the performance records for the selected monitoring point and type are displayed.

Chapter 5 Monitoring NEs

Step 6

Select OK to start the reset.

End of Procedure

How to Print Historic Performance Records This instruction describes how to print a performance record.

Procedure Step 1

Step 2

Display the relevant performance record, as described in “How to View Channel Performance per NE” on p. 389, or “How to View Single Channel Performance” on p. 390. If you wish to print a table of records: Select the Table tab in the History section.

Step 3

If you wish to print a chart of records: Select the Chart tab in the History section.

Step 4

Select the Print button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Print window appears.

Step 5

Specify the printer to use and configure the printer properties as appropriate, then print.

Step 6

Select Close to finish.

End of Procedure

User Manual

399

Monitoring Performance

How to Export Historic Performance Records This instruction describes how to export a performance record.

Procedure Step 1

Step 2

Display the relevant performance record, as described in “How to View Channel Performance per NE” on p. 389 or “How to View Single Channel Performance” on p. 390. If you wish to export a table of records: Select the Table tab in the History section.

Step 3

If you wish to export a chart of records: Select the Chart tab in the History section.

Step 4

Select the Save button. In response, the Save window appears.

Step 5

Specify a name for the file and a location, then export.

End of Procedure

This instruction describes how to view measurements at the physical layer for a single entity.

Procedure Step 1

Select the relevant module or pluggable transceiver in the Entities pane. In response, all available information about the entity is displayed in the Parameters pane.

Step 2

Select the Monitoring tab in the Parameters pane. In response all monitored data is displayed.

400

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

How to View Physical Layer Measurements

Chapter 5 Monitoring NEs

Step 3

To view the physical layer measurements, expand the Monitoring section. The displayed measurement types are described in the FSP3000R7 Provisioning and Operations Manual.

Step 4

The information in the Performance Data window is not automatically updated. In order to update it: Select the Refresh button.

End of Procedure

How to View Optical Power Reference Values This instruction describes how to view the stored optical power reference values for a port.

Procedure Step 1

Select the relevant port in the Entities pane. In response, all available information about the port is displayed in the Parameters pane.

Step 2

Select the Monitoring tab in the Parameters pane.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response all monitored data is displayed.

Step 3

Use the Monitoring Type drop-down list to select the optical power reference item to view the value for, For example, select Optical Power Rx.

Step 4

In the History Records section, select the Reference radio button from the Intervals area. In response, the stored reference values for this port are displayed in the table.

User Manual

401

Monitoring Performance

Step 5

The information in the window is not automatically updated. In order to update it: Select the Refresh button.

End of Procedure

How to View Thresholds for Threshold Crossing Alerts This instruction describes how to view the thresholds that are used to create Threshold Crossing Alerts (TCAs) for a single entity.

Procedure Step 1

Select the relevant module or pluggable transceiver in the Entities pane. In response, all available information about the entity is displayed in the Parameters pane.

Step 2

Select the Monitoring tab in the Parameters pane.

Step 3

To view the thresholds that are applied to the physical measurements to create threshold crossing alerts, expand the Thresholds section.

Step 4

The information in the Performance Data window is not automatically updated. In order to update it: Select the Refresh button.

End of Procedure

402

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response all monitored data is displayed.

Chapter 5 Monitoring NEs

Monitoring States Each entity has an administrative state, which shows whether the entity is prepared for traffic or not. The operational state shows the actual state of the entity. See “Description of States” on p. 465 for a full description of all the states for FSP3000R7. The following topics are provided: “How to View States for an Entity” on p. 403 “How to View States for an NE” on p. 404

How to View States for an Entity This instruction describes how to view states for a single entity.

Procedure Step 1

Select the relevant entity in the Entities pane. In response, all available information about the entity is displayed in the Parameters pane.

Step 2

Select the State tab in the Parameters pane.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the states for the entity is displayed.

Step 3

The information in this tab is not automatically updated. In order to update it: Select the Refresh button.

End of Procedure

User Manual

403

Monitoring States

How to View States for an NE This instruction describes how to view states for all entities in an NE.

Procedure Step 1

Select the relevant NE in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration -> State Summary.

In each row, the states for one entity are displayed. There is one column for each state and secondary state. The rows can be expanded and collapsed. Step 3

The information in this window is not automatically updated. In order to update it: Select the Refresh button.

Step 4

Select Close to finish viewing states.

End of Procedure

404

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the State Summary window appears.

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. The following topics are provided: FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

About Software and Database Files, which describes software and database files and how updating of these is handled on the Network Element. Backing Up and Restoring the Database, which contains the instructions for backing up and restoring the configuration database. Updating NE Software in a Network, which describes how to update application software and FWP for all NEs in a network. Updating NE Software in a GNE-based Network, which describes how to update application software and FWP for all NEs in a GNE based network. Updating Firmware Packages in an NE, which contains instructions for updating FWP on an NE. Transferring Files To/From the NE, which describes how to transfer software package files, database backup files or alarm profile files by downloading or uploading them. Rebooting, which describes how to reboot the NE and how to make a cold and warm start of a module. About FTP and SCP, which gives a brief overview of what the FTP protocol is, as well as an example, top-level instruction for moving the necessary files to and from an FTP server.

User Manual

405

About Software and Database Files

About Software and Database Files This section gives background information about how NE software packages and database files are handled on the network element. The following sections are provided: “The Software Package” on p. 406 “Handling of Files” on p. 408 “Software and Database Compatibility” on p. 409 “Software Downgrade and Switchback” on p. 409 “NE Software Version versus File Names” on p. 411

The Software Package

Figure 23:

Software Package

The NE software is a package containing the following files: •

The configuration file. This file is interpreted for the correct transferal of all required software. It is named F70XXYYZ.CON and contains the following information: o o

o

•

406

the names of the NE software files with their version number and size the names of all firmware package (FWP) files in the FWP set and the FWP version the type of NCU that each FWP is supported by.

The NCU software files. The NCU software is the part of the NE software that runs on the NCU. It includes the Linux operating system and environment and the FSP 3000R7 applications. Each NCU type supports a different

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The NE software is the complete software load for the NE. It is a software generic and contains all code that runs on an NE. The NE software version number is equal to the release number. The release number syntax is XX.YY.Z. The XX and YY represent numbers between 1 and 99, and are increased for major and minor releases, respectively. Z is increased for maintenance releases and can be a number from 1 to 9 or a letter from A to Z. It starts with 1 and continues into letters in alphabetical sequence, if necessary.

Chapter 6 Maintaining NEs

set of modules. To save space and to avoid overloading the NCUs, two software files are provided.The NCU software files are named as follows: o o

•

The firmware package (FWP) set files.The FWP set contains the individual FWPs for all modules that are supported by the NE software, except encryption modules. Each FWP is the software that runs on a particular module type. It contains code for all processors on the module as well as FPGA code. The user can select which FWP to activate on the individual modules. Each NCU type supports a different set of modules. To save space and to avoid overloading the NCUs, two FWP files are provided. The FWP set files are named as follows: o o

•

H70XXYYZ.PGM for the NCU-II O70XXYYZ.PGM for all other NCU types

S70XXYYZ.PGM for the NCU-II T70XXYYZ.PGM for all other NCU types

The firmware package (FWP) set files for encryption modules. These files are not included in the regular software package. These FWP files are made available through the Customer Portal at http://www.advaoptical.com/ and they are only retrievable for those customers who have ordered encryption hardware modules. The FWP set file is named as follows: C70XXYYZ.PGM

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

o

User Manual

407

About Software and Database Files

Handling of Files The NE software and database files are stored in two areas on the NCU: in the active and in the standby area. Overview of Software and Database File Handling

The NE software in the active or standby area consists of one NCU software file, the FWP files for each module type, and the configuration file. In addition, the active or standby area contains a database framework with default values. These files all originate from an NE software package. The database file in the active area contains the current configuration of the running system. The standby area originates from the default factory installation or from a restoration of a backed up database. The active area contains the files that are currently used by the NE. The standby area is used to prepare a change in software and/or database versions by installing the new file versions to the standby area. The NE starts using the new versions when the contents of the standby area are activated, which means that the standby area becomes the active area, and the active area becomes the standby area. Thus, the previously active version is contained in the standby area until a different file version is installed in the standby area. The standby software files and database files can be activated individually. The file area is an intermediate storage area located on a RAM disk (RDISK) on the NCU, and is cleared on reboot. It is used to download software and database files from external storage to the NE, and to upload backup database files to external storage.

408

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 24:

Chapter 6 Maintaining NEs

Downloading and uploading files may be done using File Transfer Protocol (FTP) or Secure Copy (SCP). SCP uses Secure Socket Layer (SSH). NEs with an NCU including a 1 GB CompactFlash (CF) installed have an FTP and SSH server on board. The NCU-II is an example of this. For all other NEs, an external FTP or SSH server is required to upload files to the NE. An external FTP server must support passive FTP mode. Database backup files can alternatively be stored in a file area on the SCU, and restored from this area on the SCU. This requires an SCU with hardware revision 2.01 or higher.

Software and Database Compatibility

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The NE software and database that shall be activated on an NE must have the same version. When a software update is performed, which is a valid update path, the version of the database is automatically updated to the version of the NE software. Otherwise, a situation in which functionality of the software is not supported by the database could arise, and vice versa. Services could be affected by this. In order to prevent a database from making service affecting (SA) changes to the installed modules, the NCU detects when it is inserted into a new network element, as well as when a new CompactFlash (CF) has been inserted. It then switches to an auxiliary database. This auxiliary database functions as a security mechanism, in which the settings of the equipment are not altered by it. It will therefore not have an impact on a running system. The auxiliary database uses the default IP address, and thus management contact with the NE will be lost. You will have to be on site, and reconnect to the NE via a serial connection, to restore contact. Refer to the FSP 3000R7 User Guide for help on fixing the problem.

Software Downgrade and Switchback Downgrade and switchback are subject to the following: •

Switchback to the former software is always possible after an update (Figure 26). By switching to the formerly active database as well, all previous settings can be reused. Thus the switchback can be done without losing connectivity or settings from the database.

•

Downgrade of software and using the database of a newer version is not allowed (Figure 28). An auxiliary database would be created, with factory default settings only.

•

Download and activation of an older software is possible, but the action is not supported. It would result in the creation of an auxiliary database and permanent loss of the database formerly located in the standby area. Please consult ADVA Optical Networking Technical Services if you are contemplating such an action.

During activation of a software update, the first step taken by the system is to preserve the former software database. This is done by copying the former database to the active area and migrating its format to the new software version in the process. The format update is necessary for the database to match the features of the new software version. In addition, the first time a software update

User Manual

409

About Software and Database Files

is activated, the former software database is copied to the standby area. Figure 25 illustrates this. Figure 25:

NE Software Update, First-time Activation

If you decide to use the former software after already using the new software, the former software including its database file is fully intact. In other words, after a software update you can switch back to the former software by activating it (activate STBY). Figure 26 illustrates this. Switchback to Previous NE Software and Database

However, when the software versions in the Active and Standby areas are switched, it is possible to keep the currently used database (in the Active area) for the new software while not touching the database in the Standby area. Figure 27 illustrates this. Figure 27:

410

NE Software Activation Keeping Current Database

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 26:

Chapter 6 Maintaining NEs

Downgrade of software and using the database of a newer version is not allowed. An auxiliary database would be created, with factory default settings only. Figure 28 illustrates this. Here no available compatible database can be found and thus an auxilary database must be used. Figure 28:

NE Software Switchback With Auxiliary Database

NE Software Version versus File Names

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

For all NE software files, the XXYYZ in the file name indicates the version of that file, and uses the same syntax as for the release number. The release number of the NE software package is updated when the version number of any of the other files in the NE software package is updated. Using R9.2 as an example, the release 9.2.1 NE software package consists of the following files: F7009021.CON, H7009021.PGM, O7009021.PGM, S7009021.PGM, and T7009021. After one maintenance NCU software update and two FWP set updates the release number would be 9.2.4.

Backing Up and Restoring the Database It is possible to back up the current database, and then at a later time restore the database to an NE. Backing up the database should be done regularly, and always as a precaution before you do any updates to software on the NE. The backup database file can be uploaded to a remote file server for safe storage there, or it can be stored on a file area on the SCU, if the SCU has hardware revision 2.01 or later. Since the backed up database file contains the settings for all the NE’s IP connections, storing it on the SCU is advantageous. If there is a problem with the current database, you may not be able to connect to the remote file server, but it is always possible for the NCU to reach the SCU. If you enable automatic database restore then the database backup file on the SCU will automatically be restored to the NCU if you need to replace it. It is possible to setup automatic database backup to the SCU or to a remote file server. A backup database file that was created and stored on the SCU while running software release 9.2 or later, will not be recognized after a downgrade to an

User Manual

411

Backing Up and Restoring the Database

older software release. The backup database file will still be present on the SCU, but the older software can not recognize it and therefore will not display it. It is possible to restore a database from a source NE to a target NE. This is outside the scope of this User Manual, for information see the FSP 3000R7 Maintenance and Troubleshooting Manual. This section contains instructions for backing up and restoring the database.The following topics are provided: “How to Manually Back Up the Database” on p. 413 “How to Set Up Scheduled Backup of the Database” on p. 415 “How to Restore the Database” on p. 419 “How to Enable Automatic Database Restoration” on p. 421 The above sections are supported by the following sections in Transferring Files To/From the NE: “How to Upload Files from the NE” on p. 448

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“How to Download Files to the NE” on p. 453

412

User Manual

Chapter 6 Maintaining NEs

How to Manually Back Up the Database This instruction describes how to manually back up the database, and store it either in an external storage place, or in the file area on the SCU. If you store the database backup file on an external storage place, you should make sure that it is part of a regular backup plan.

Requirements In order to store the database backup file on the SCU, the NE must have an SCU with hardware revision 2.01 or higher. This information can be found on the SCU’s Inventory tab in the Parameter pane.

Procedure Step 1

Select the NE to back up the database for, in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration -> Backup/Restore.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Backup/Restore window is displayed.

The Backup/Restore window is divided into three sections: •

•

•

User Manual

Active software database. This section displays the filename, ver-

sion number, size and creation date for the database file that is in the active area. In addition it displays any comment that exists for this database file. Standby software database. This section displays the filename, version number, size and creation date for the database file that is in the standby area. In addition it displays any comment that exists for this database file. NE File Area. This section displays the database files in the file area. This section displays the database files of either the file area on the NCU (RDISK) or on the SCU, in a tabular form. If you have an SCU with hardware revision older than 2.01, it does not support storage of a backup database file, and viewing the file

413

Backing Up and Restoring the Database

area on the SCU is not possible. For each backup database file that has been placed in the file area, either by download or by backup, this section displays the file name, the file size and the time the file was placed in the file area. If the backup database file was made and stored on the SCU while running software release 9.2 or later, and the software running now is an older release, the database file will not be visible in this section. The backup database file is however in place. Step 3

Optionally, add a comment to the database file in the Active software database section by selecting the Edit Comment button. This can be useful when keeping track of this database file through backup and restore at a later time.

Step 4

If you have an SCU installed with hardware revision 2.01 or newer, decide from the following: • To back up the database to the NE File Area (RDISK), select the Backup button in the Active Software database section. • To back up the database to the SCU, select the Backup to SCU button in the Active Software database section. Otherwise, if your SCU hardware is older than 2.0.1, select the Backup button in the Active Software database section.

Step 5

Confirm that you want to back up the database by selecting Yes. In response, the database file is copied either to the NCU’s file area or on the SCU. Progress is shown in the lower, left corner of the Backup/Restore window.

Step 6

Verify that the database backup file is now in the NE File Area table. If you have an SCU installed with hardware revision 2.01 or newer, you use the Location radio button to display either files in the RDISK area or on the SCU. The name of the backup file uniquely identifies the NE it belongs to. The syntax is: F7___.DBS The date and time is written in the format yymmdd_hhmm, and indicates the time the file was placed in the file area. If the database backup file is not visible, select Refresh to update the Backup/Restore window.

414

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, a Backup confirmation window matching your choice is displayed.

Chapter 6 Maintaining NEs

Step 7

Make a decision: • If you have backed up the database file to SCU, go to Step 12. • If you have backed up the database file to the NE’s file area, go to Step 8

Step 8

Everything in the file area on the NCU is deleted when the NE is rebooted, while files stored on the SCU are not. Decide where to upload the backup database file to, either an external storage location or on the SCU.

Step 9

Select the newly created database backup file in the NE File Area.

Step 10

Make a note of the database backup file name, which is displayed in the NE File Area table.

Step 11

Upload the database file from the file area to the storage place you decided on in Step 8. Follow the description in “How to Upload Files from the NE” on p. 448.

Step 12

Close the Backup/Restore window by selecting the Close button.

End of Procedure

How to Set Up Scheduled Backup of the Database FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This instruction describes how to set up scheduled backup of the database, with storage of the file in one of the following places: •

an external storage location

•

in the file area on the SCU

The file is named F70XXYYZ.DBS, where XXYYZ reflects the FSP3000R7 product release number. For example for product release R10.1.1 the file name is F701011.DBS. If you store the database backup file in an external storage location, you should make sure that it is part of a regular backup plan.

PS

The date and time you define in the schedule are in the NE’s time zone, which can be different from the Element Manager’s time zone.

Note

The schedule you set up must be enabled. This means that you may choose to set up the schedule, but postpone enabling it.

Requirements

User Manual

•

The NE must have access to an FTP or SSH server (depending on which method is chosen) for the backup to an external storage location.

•

In order to store the database backup file on the SCU, the NE must have an SCU with hardware revision 2.01 or higher. This information can be found on the SCU’s Inventory tab in the Parameter pane

415

Backing Up and Restoring the Database

Procedure Step 1

Select the NE to back up the database for, in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration -> Automatic Backup.

Step 3

Make a choice between setting up scheduled backup of the database to a remote file server or to the SCU.

Step 4

If you decided to set up backup to a remote server in Step 3: Enter the following parameters to enable the NE to connect to the remote server: a) Select Modify in the Remote File Server Settings section.

b) Select the file transfer protocol to use from the Protocol Copy drop-down list.

416

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Automatic Backup window is displayed.

Chapter 6 Maintaining NEs

c) 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: • 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. FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

d) Enter the IP address of the FTP or SSH remote server in the IP Address field. e) If the database backup file shall be stored in a sub-directory of the FTP or SSH server’s root directory, enter that sub-directory in the Path Name field. Otherwise leave this field empty. f)

Enter the user account name for accessing the FTP or SSH file server into the User Name field. It depends on the remote server whether the case of this entry as entered is taken into account before validation by the remote server.

g) Enter the password for the user account on the FTP or SSH server in the Password field. It depends on the remote server whether the case of this entry as entered is taken into account before validation by the remote server. h) Select OK to apply your entries, or Cancel to abort them. Step 5

Define the schedule for backup to the SCU or a remote file server. Do this by selecting the appropriate row in the Backup to column in the Schedule table.

• •

User Manual

If you decided on SCU in Step 3, select the row SCU. If you decided on remote file server in Step 3, select the row Remote File Server.

417

Backing Up and Restoring the Database

Step 6

Select Modify. In response the Schedule Remote File Server Backup or Schedule SCU Backup window appears. This example shows the Schedule Remote File Server Backup window.

Step 7

Define the backup schedule as follows:

b) Enter the date that the first backup shall take place in the DB Start Date field. The date you enter is in the NE’s time zone. Use the format year, month and day (YY-MM-DD). c) Enter the time that the first backup shall take place in the DB Start Time field. The time you enter is in the NE’s time zone. Use the format hours, minutes and seconds (HH:MM:SS). d) Specify whether the database backup file name shall embed a time stamp or not by using the File Name Timestamp drop-down list. • Select Add Timestamp to embed a time stamp in the file name. • Select Omit Timestamp to omit a time stamp in the file name. In addition to a timestamp, the NE’s IP address is embedded using the syntax __.DBS. For example, a backup file taken on Aug 19th 2010 at 12:15 for an R10.1 NE with IP address 192.168.154.220 gets the name F701011_100819_1215_192_168_165_220.DBS. e) Enable this schedule by selecting Yes in the Enable Schedulerfield. The schedules are by default set to No (disabled). This field is only available when you are setting up scheduled database backup to a remote file server. It is also only available when you have completed the remote file server specification in Step 4. f)

418

Select OK to apply your entries, or Cancel to abort them.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

a) Enter the interval between each backup in the Schedule DB Interval field. The interval options are one to six days, each week or every second week.

Chapter 6 Maintaining NEs

Step 8

You can check the date that the next backup will take place in the Next backup column of the table in the Schedule section. The content of this table is not automatically updated, select Refresh to update it if necessary.

Step 9

Close the Automatic Backup window by selecting the Close button.

End of Procedure

How to Restore the Database This instruction describes how to restore the database from its storage place. This involves placing the backup database file into the Standby Area, and then activating the Standby Area. When the Standby Area is activated by the database restore facility, only the database version in the Standby Area is activated, not the software version.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

User Manual

Step 1

Check your notes from How to Manually Back Up the Database, Step 8 to find out whether the database backup file is stored in an external storage place or on the SCU.

Step 2

If the database backup file is stored in an external storage place, download the database backup file as described in “How to Download Files to the NE” on p. 453.

Step 3

Select the NE you want to restore the database for, in the Managed Elements pane.

419

Backing Up and Restoring the Database

Step 4

From the Main Menu, select Configuration -> Backup/Restore.

Verify that the correct database backup file is present in the file area. Compare with the filename you made a note of in How to Manually Back Up the Database, Step 10. To locate the database backup file, select one of the following: • •

If the database backup file is located on the SCU: Select the SCU radio button in the NE File Area section. If the database backup file is located on an external server: Select the RDISK radio button in the NE File Area section.

If you need to remove old files, check the All files check box, select the relevant file and then select Delete.

PS

If you have an SCU with hardware revision older than 2.01, it does not support storage of a backup database file.

Note

Step 5

Select the correct database backup file in the NE File Area, and then select the Install button. In response, the Install dialog is displayed.

Step 6

Confirm that you want to install the database to the Standby Area, by selecting Yes. In response, the database file will be copied to the Standby Area.

420

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Backup/Restore window is displayed.

Chapter 6 Maintaining NEs

Step 7

Select Refresh to update the Backup/Restore window. In response, the database file should appear in the Standby software database section.

Step 8

Ensure that the correct database backup file now is present in the Standby software database section.

Step 9

If the database file that is now installed in the Standby Area is planned to be activated at a later time: Go to Step 13.

Step 10

If you wish to Activate the selected database and reboot the NE, select the Activate button.

Step 11

Select Yes to activate the standby database.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

If the database file in the standby area is not compatible with the currently installed NE software, a database mismatch alarm will be raised to indicate this. Step 12

Verify that the active and standby database versions have been updated. You can find this information in the Backup/Restore window.

Step 13

Select the Close button to close the Backup/Restore window.

End of Procedure

How to Enable Automatic Database Restoration When replacing an NCU, it is useful to allow the database back-up file on the SCU to be automatically restored to the replacement NCU when this NCU is inserted in the shelf. This feature must be enabled before backing up the old NCU’s database and removing the old NCU. The feature should be disabled after the new NCU is operational. See the FSP 3000R7 Maintenance and Troubleshooting Manual for a description of how to replace an NCU. This instruction describes how to enable automatic restoration of a database back-up file stored on the SCU. Automatic database restoration is disabled similarly.

User Manual

421

Backing Up and Restoring the Database

Procedure Step 1

Double-click the relevant Network Element in the NE Pane.

Step 2

Select the Database tab. In response the database related information is displayed in the Parameter pane.

Step 3

Select the Modify button.

Step 4

Use the Enable Auto Restore drop-down list and select Enable to enable the automatic database restoration. To disable it, select Disable.

Step 5

Select OK to apply the change, or Cancel to discard the change.

End of Procedure

422

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Modify window appears.

Chapter 6 Maintaining NEs

Updating NE Software in a Network This section describes how to update all software in a network, including firmware for the modules. For networks which use a Gateway Network Element (GNE), a different approach must be used. In this case, see “Updating NE Software in a GNE-based Network” on p. 435.

PS

Do not reseat the NCU during NE software installation.

Note

In the case that you have started an NE software update, but you for some reason are not able to finish the process, for example because the maintenance time slot is too small, you need a fall-back solution. “Switching Back to Previous NE Software Version” on p. 434 describes how to fall back to the previous NE software and database version.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

If any NE in the network is running NCU software version previous to 7.1.0, be aware that NCU software versions 7.1.x and later are able to handle optical input power thresholds according to the specification of the pluggable transceivers. This leads to two effects when updating an NCU software version Software Control.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Software Control start window is displayed.

The Active Software Package and Standby Software Package sections display an overview of the NE software, NCU software and FWP set file versions that are stored in the active and standby areas of the NE. The syntax used is: (, ). The date and time each the software packages where installed and activates are also displayed, as well as an optional descriptive comment.

PS

Note

User Manual

If the NE software package version you wish to update is listed in the STBY Program Versions (Standby) field, the NE software is already installed and you can stop this procedure.

425

Updating NE Software in a Network

Step 4

Select the Install Software Package radio button, and then select Next to continue.

Step 5

Install the new NE software files to the Standby Area by selecting the Install from External button. In response, the Download window appears.

This window remembers the entries which were used the last time a download was made to this NE.

426

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Install Software Package page appears.

Chapter 6 Maintaining NEs

Step 6

Specify which file transfer protocol to use when downloading the NE software to the target NE. Use the Protocol drop down list. 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 (see “How to Configure Known Hosts” on p. 242). If you are not familiar with FTP or SCP, see “About FTP and SCP” on p. 459 for a brief overview.

Step 7

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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: • • Step 8

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.

Specify which file to download as follows: a) Enter the IP address of the NE software package location into the Server field. b) If the NE software package is located in a sub-directory of the FTP or SSH server root directory, enter that sub-directory in the Path Name field. Otherwise leave this field empty. c) Enter the name of the NE software configuration file (F70XXYYZ.CON) into the File Name field.

User Manual

427

Updating NE Software in a Network

Step 9

In the Login and Password fields, enter the user account name and password to gain access to the server. Whether the case (lower/upper) of a user name or password as entered is taken into account depends on the remote server. If this remote server is running on an FSP 3000R7 NE (e.g. acting as a GNE), it will not take the case of the user name and password as entered into account. Instead, due to TL1 standards restrictions, the user names and passwords for accounts on an FSP 3000R7 NE are converted to all uppercase before they are saved or validated. For most other remote servers, account user names and passwords are case-sensitive. Please refer to the manual of the remote server in question.

Step 10

Select OK to start the installation, or Cancel to discard your entries and return to the Install Software Package page. In response to OK, the transfer and installation of the NE software files will start. The configuration file will be transferred and interpreted. After interpretation the correct NCU software file as well as the FWP set will be transferred and installed.

If there is little storage space left in the file area (RDISK), this can prevent a successful download. In that case, delete old files using Delete or Delete All, in combination with using the All files check box to see all file types. Step 11

When the installation is complete, verify that the standby area now contains the correct versions of the software package, software application and FWP set. The Install Software Package page, Installed File (Standby) section will display the versions of the software package, software application and FWP set.

Step 12

Optionally, add a comment to the NE software file in the Installed (Standby) section by selecting the Change Comment button and writing a comment in the Modify window that appears.

Step 13

Go back to the Software Control main page by selecting Back.

Step 14

Close the Software Control wizard by selecting Finish.

End of Procedure

Activating the NE Software The NE software that is stored in the Standby Area can be activated manually, or by scheduling the activation. The following sections are provided: How to Schedule Activation of the NE Software

428

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This may take up to 30 minutes, depending on your bandwidth. During the process, you will see progress messages in the bottom left corner of the Install Software Package page.

Chapter 6 Maintaining NEs

How to Manually Activate the NE Software

How to Schedule Activation of the NE Software This instruction describes how to schedule activation of the NE software that is stored in the Standby Area. It is possible to define a schedule, but postpone activation of the schedule to a later time.

PS

The date and time you define in the schedule are in the NE’s time zone, which can be different from the Element Manager’s time zone.

Note

Procedure Step 1

Select the NE to activate software for in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration -> Software Control.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Software Control start window is displayed. Step 3

The Active Software Package and Standby Software Package sections display an overview of the NE software, NCU software, and FWP set file versions that are stored in the active and standby areas of the NE. The syntax used is: (, ). The date and time of when each of the software packages were installed or activated are also displayed, as well as an optional descriptive comment.

Step 4

Ensure that the standby area contains the NE software version you need. Follow these steps: a) Check the version of the software package in the Standby Software Package section. This is the version of the software that will be installed if the standby area is activated. b) Check the comment attached to the software package in the field Comment. Unless edited, it repeats the software version and also contains the date when this version had been introduced. c) If it is not the correct version, return to “How to Install NE Software” on p. 425 and install the correct software package.

User Manual

429

Updating NE Software in a Network

Step 5

Select the Scheduled Activation of Standby Software Package radio button and select Next.

This window shows the default settings for when and how an activation will take place. The default date occurs in the past, so no activation will take place until these settings have been modified. Step 6

Step 7

Select Modify to specify when and how activation shall take place.

Enter the date the application software shall be activated in the Activation Date field.

The date you enter is in the NE’s time zone. Use the format year, month and day (YY-MM-DD). Step 8

Enter the time the application software shall be activated in the Activation Time field.

The time you enter is in the NE’s time zone. Use the format hours, minutes and seconds (HH:MM:SS).

430

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Activate Standby Software Package page is displayed.

Chapter 6 Maintaining NEs

Step 9

Specify what shall happen with the database when the application software is activated, by using the Scheduled DBRST drop-down list: • Select Keep Current Database if the configuration values in the currently active database shall be used together with the updated application software. This is the default setting, as this selection ensures that a NE software and database switchback is always possible. • Select Set Database to Factory Default if the currently active database shall be replaced by the factory default database. This is only relevant if you are switching back to the previous NE software version and you need to reset the database. As a result, the NE’s IP address will change. If the factory default IP address is not within the same IP network as the computer running the Element Manager, the Element Manager will lose contact with the NE. You will then have to be on site to re-connect to the NE again.

Step 10

The scheduled activation will not take place until it has been activated. Set the Scheduled Activation field to Yes to activate the schedule, or No to leave it un-activated.

Step 11

Select OK to apply your entries, or Cancel to cancel them. You are returned to the Software Control window, Scheduled Activation page.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 12

If you have activated the scheduled activation, select Finish to Close the Software Control wizard. At the specified date and time (in the NE’s time zone), the NE software will be activated and the NE rebooted.

PS

Note

Step 13

The activation and reboot process might take up to 5 minutes and the network connection will be lost. The connection is recovered again as soon as the NE is rebooted and ready for operation. When the NE is ready for operation again, check that the NE is now running the new NE software version. Follow the steps: a) Open the Software Control window again. b) Find the NE software version in the Active Software Package section.

End of Procedure

User Manual

431

Updating NE Software in a Network

How to Manually Activate the NE Software This instruction describes how to manually activate the NE software that is stored in the Standby Area.

Procedure Step 1

Select the NE to activate software for in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration -> Software Control. In response, the Software Control start window is displayed.

Step 3

Select the Activate Standby Software Package radio button and select Next.

The Active Software Package and Standby Software Package sections display an overview of the NE software, NCU software, and FWP set file versions that are stored in the active and standby areas of the NE. The syntax used is: (, ). The date and time of when each of the software packages were installed or activated are also displayed, as well as an optional descriptive comment.

432

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Activate Standby Software Package page is displayed.

Chapter 6 Maintaining NEs

Step 4

Ensure that the standby area contains the NE software version you need. Follow these steps: a) Check the version of the software package in the Standby Software Package section. This is the version of the software that will be installed if the standby area is activated. b) Check the comment attached to the software package in the field Comment. Unless edited, it repeats the software version and also contains the date when this version had been introduced.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

c) If it is not the correct version, return to “How to Install NE Software” on p. 425 and install the correct software package. Step 5

Specify what shall happen with the database when the application software is activated, by using the When this version is Activated drop-down list: • Select Keep Current Database if the configuration values in the currently active database shall be used together with the updated application software. This is the default setting, as this selection ensures that a NE software and database switchback is always possible. • Select Set Database to Factory Default if the currently active database shall be replaced by the factory default database. This is only relevant if you are switching back to the previous NE software version and you need to reset the database. As a result, the NE’s IP address will change. If the factory default IP address is not within the same IP network as the computer running the Element Manager, the Element Manager will lose contact with the NE. You will then have to be on site to re-connect to the NE again.

Step 6

Activate the selected software file, the specified database values, and reboot the NE, by selecting the Activate and Reboot button. Select Yes in the Confirmation window that appears.

PS

Note

Step 7

The activation and reboot process might take up to 5 minutes and the network connection will be lost. The connection is recovered again as soon as the NE is rebooted and ready for operation. When the NE is ready for operation again, check that the NE is now running the new NE software version. Follow the steps: a) Open the Software Control window again. b) Find the NE software version in the Active Software Package section.

Step 8

Close the Software Control wizard by selecting Finish.

End of Procedure

User Manual

433

Updating NE Software in a Network

Switching Back to Previous NE Software Version If you for some reason do not have time to complete an already started NE software update process, you may switch back to the former NE software. Even after already using the new software, the former software and the belonging database file is intact in the standby area. In other words, after a software update you can switch back to the former software by activating the standby area. Figure 26 illustrates this situation. If another NE software version has been installed to the standby area in the meantime, switch back will not be possible. This procedure describes how to switch back to the previous NE software and database.

Step 1

If you are not already logged in, log in to the relevant NE.

Step 2

Activate the NE software as described in “How to Manually Activate the NE Software” on p. 432, and in Step 5 select the option Use Standby Database. An activation of NE software always activates the NE software in the standby area. In this case the content of this area is the former NE software version. The option Use Standby Database secures that the database associated with the former NE software version is restored.

PS

Note

The activation and reboot process might take up to 5 minutes and the network connection will be lost. The connection is recovered again as soon as the NE is rebooted and ready for operation

Step 3

If necessary, downgrade the individual firmware packages for the relevant modules/module types, as described in “Updating Firmware Packages in an NE” on p. 435.

Step 4

Reboot the NE to complete the switch-back. Although the NE was rebooted as a consequence of the NE software activation, this final reboot is required.

End of Procedure

434

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Procedure

Chapter 6 Maintaining NEs

Updating NE Software in a GNE-based Network In a Gateway NE (GNE)-based network, an NE only has visibility of the GNE and the other NEs in this network. Only the GNE has visibility of an external file server. Therefore, in order to update the NE software on the NEs, the NE software must be downloaded to the GNE’s file area. Both the NEs and the GNE then install the NE software from the GNE’s file area. GNE-based Network Example

The Element Manager can only be used to perform software updates in this network example if it can reach the NEs. In that case follow the procedure described in “Updating NE Software in a Network” on p. 423. If this is not possible, the Element Manager cannot be used to update NE software in such a network configuration. Instead, use a Telnet or SSH session and the Craft Console. Please read the FSP 3000R7 Provisioning and Operations Manual for a full description.

Updating Firmware Packages in an NE The Element Manager lets you update firmware packages (FWPs) on a single module at a time, on all modules of a specific type at once or all modules in the NE at once. Downgrade to an older FWP is supported, but not to older versions than those valid for R9.1.

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 29:

FWP updates may be service affecting. FWP downgrades are always service effecting, except for legacy modules.

Note

User Manual

435

Updating Firmware Packages in an NE

The Element Manager allows you to conditionally update. You can, for example, specify that the FWP for a module shall be updated as long as this update does not affect any services on the module. This means you can allow a FWP update that will affect services, to be done only on the modules with services that are out of service. This allows you to quickly update FWPs on a number of modules and control whether this process will affect service or not, without having to check specifically the effects each new version update has on services. •

If an update of NE software or another FWP update is in progress, then FWP update is not possible.

•

Modules that have not been assigned to the database (administrative state UAS) and modules with a mismatch (secondary state MEA) will not be updated.

•

FWP update on multiple modules in a channel card protected or client path protected system is only performed on the inactive modules, if the update is service affecting. This is true even if the user specifies that effects on the service is accepted. The user must then perform a protection switch and another update in order to update all modules in the system. This is covered in “How to Update Firmware for Multiple Modules” on p. 441.

PS

Note

Do not remove hardware or power off during a FWP update. If you attempt this, you will corrupt the module firmware. Legacy modules with only one firmware image will then not be possible to restart without a special emergency recovery procedure.

The following sections describe how to update the FWP on each module, to a newer version: “Requirements” on p. 436 “How to Update Firmware for a Single Module” on p. 437 “How to Update Firmware for Multiple Modules” on p. 441

Requirements Before updating FWP, the following items are required: •

The NE software package, containing the relevant FWP versions, must already be in the active area (activated).

•

A working NCU, installed in slot A of shelf 1.

•

As an FWP update can be service affecting, take the necessary precautions for a service hit.

•

If the NE consists of multiple shelves, the following is required for a successful FWP update: o

o

•

436

Correctly cabled SCUs. In releases previous to Release 8.2, only chained connections of SCUs and ROADMs were supported. Starting from Release 8.2, ring connected SCUs and ROADMs are supported. The plugs on the SCUs must be provisioned.

A computer with an FTP or SCP server and a terminal program.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

The following restrictions apply:

Chapter 6 Maintaining NEs

•

Release notes

How to Update Firmware for a Single Module This instruction describes how to update the firmware package (FWP) on one single module.

PS

Note

An FWP update can be service affecting. Specify the correct Permitted Effect to avoid this. Take the necessary precautions for a service hit.

Procedure Step 1

Select the NE you want to update FWP for in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration -> Software Control.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Software Control start window is displayed.

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 3

Select the Update Equipment Firmware (FWP) radio button, and then select Next to continue. In response, the Install Equipment Firmware (FWP) page appears.

User Manual

437

Updating Firmware Packages in an NE

Step 4

Select the Single FWP Update radio button in the Update Mode section.

Each module is described by the following items: Column Name

Description

Equipment FWP Rev

This column shows the equipment in the system. This column contains the version of the FWP that is currently in use on the module This column contains the version of the FWP that is available and ready for installation on the module. This column contains information about whether making this update will affect service, or not. The following abbreviations are used:

NCU ACT FWP Rev

Update Effect

•

SA Activate, which means that service is

affected when the update is activated. •

SA Install, which means that service is affected

when the update is installed. •

NSA, which means that service is not affected.

•

Undefined, which means that the NE cannot

determine the effect of the update on the services.

438

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Install Equipment Firmware (FWP) page displays relevant information for updating the FWP for a single module at a time.

Chapter 6 Maintaining NEs

Column Name

Description

NCU STBY FWP Rev

This column shows the version of the FWP that was used prior to the currently active version. If anything goes wrong with the update and the new FWP version does not work as it should, the module will automatically revert to this version. This column contains information about whether making this update will affect service, or not. The following abbreviations are used:

STBY Update Effect

•

SA Activate, which means that service is

affected when the update is activated. •

SA Install, which means that service is affected

when the update is installed.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

State

User Manual

•

NSA, which means that service is not affected.

•

Undefined, which means that the NE cannot

determine the effect of the update on the services. This column shows the status of any firmware package upgrade, the options are •

Idle

•

Reject (rejection of a downgrade)

•

In progress

•

Complete

Step 5

Check whether the new FWP results in a changed set of performance monitoring counters for the module. This information can be found in the release notes. • If the set of performance counters for a port is changed by the FWP update: All historic records for all counters for that port will be deleted. Go to Step 6. • Otherwise go to Step 7.

Step 6

Preserve the historic records for all affected ports on the specific module by either: • Exporting the historic records to a CSV file, see “How to Export Historic Performance Records” on p. 400. This content can however not be presented via the Element Manager later. • Using the FSP NM to collect the records. The records can then later be displayed by the FSP NM.

439

Updating Firmware Packages in an NE

Step 7

Select a module to update FWP for. It is recommended that you update FWP for SCUs after you have updated FWP for all other modules. Do as follows: a) From the Select Equipment table, identify the module(s) to update FWP for. b) For each module identified, check whether the NCU ACT FWP Rev column contains the correct FWP version.

d) If the NCU ACT FWP Rev column displays the FWP version that you want to install: Select the module you want to update FWP for. Step 8

Select Next to continue. In response, the Update of equipment page appears.

440

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

c) If the NCU ACT FWP Rev column does not display the FWP version that you want to install, you must download it. Either download the FWP as described in “Transferring Files To/From the NE” on p. 448, or download the NE software that contains the correct FWP version as follows: • Select Back to get back to the Software Control page. • Install the NE software that has the relevant FWP set version, as described in “How to Install NE Software” on p. 425. • Select Back to get back to the Software Control page. • Return to the Update Equipment Firmware (FWP) by selecting the Update Equipment Firmware (FWP) radio button, and then selecting Next to continue. In response, the Update Equipment Firmware (FWP) page appears.

Chapter 6 Maintaining NEs

Step 9

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: • • • •

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.

Step 10

Select Finish to close the Software Control window.

Step 11

Resynchronize your system: a) Select the NE you want to reboot in the Managed Elements pane. b) Select Configuration -> Resynchronize on the Main Menu. c) Select Yes in the Confirmation window that appears.

End of Procedure

How to Update Firmware for Multiple Modules This instruction describes how to update firmware (FWP) for several modules at the same time. Either all modules in the NE, or all modules of one type.

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

•

Pending, which indicates that the process hasn’t started yet. Checking Status, which indicates that the Element Manager is

Note

User Manual

An FWP update can be service affecting. Specify the correct Permitted Effect to avoid this. Take the necessary precautions for a service hit.

441

Updating Firmware Packages in an NE

Procedure Step 1

Select the NE you want to update FWP for in the Managed Elements pane.

Step 2

From the Main Menu, select Configuration -> Software Control.

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.

442

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Software Control start window is displayed.

Chapter 6 Maintaining NEs

Step 3

Select the Update Equipment Firmware (FWP) radio button, and then select Next to continue.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Update Equipment Firmware (FWP) page appears.

Step 4

For each module type that you wish to update FWP for, check that the FWP version that is available is the correct version. Do as follows: a) For each module type, check whether the NCU ACT FWP Rev column contains the correct FWP version. b) If the NCU ACT FWP Rev column does not display the FWP version that you want to install, you must download it. Either download the FWP as described in “Transferring Files To/From the NE” on p. 448, or download the NE software that contains the correct FWP version as follows: • Select Back to get back to the Software Control page. • Install the NE software that has the relevant FWP set version, as described in “How to Install NE Software” on p. 425. • Select Back to get back to the Software Control page. • Return to the Update Equipment Firmware (FWP) by selecting the Update Equipment Firmware (FWP) radio button, and then selecting Next to continue. In response, the Update Equipment Firmware (FWP) page appears.

Step 5

User Manual

For each module type that you wish to update: Check whether the new FWP results in a changed set of performance monitoring counters for the module, This information can be found in the release notes. • If the set of performance counters for a port is changed by the FWP update: All historic records for all counters for that port will be deleted. Go to Step 6 • Otherwise go to Step 7

443

Updating Firmware Packages in an NE

Step 6

Preserve the historic records for all affected ports on the specific module by either: • Exporting the historic records to a CSV file, see “How to Export Historic Performance Records” on p. 400. This content can however not be presented via the Element Manager later. • Using the FSP NM to collect the records. The records can then later be displayed by the FSP NM.

Step 7

Select the Multiple FWP Update radio button in the Update Mode section.

Step 8

444

Select which module type to update FWP for. Use the Select all equipment of this type drop-down list. The options are: • All types, which means that FWP for all modules in the NE will be updated, if their current version differs from the version in the Standby Area. The SCUs will be updated last. • , for example VSM, which indicates that FWP for all modules of this type will be updated, if their current version differs from the version in the Standby Area. It is recommended that you update FWP for SCUs after you have updated FWP for other modules.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Install Equipment Firmware (FWP) page displays relevant information for updating FWP for multiple modules at a time.

Chapter 6 Maintaining NEs

Step 9

Select Next to continue. In response, the Update of equipment page displays the module type you selected as well as the revision of the FWP that will be installed and activated.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 10

User Manual

Restrict the update by using the Permitted Effect drop-down list. If you select: • NSA, and the update is service affecting for the selected modules or module types, then these modules will not be updated. • NSA, and the update is not service affecting for the selected modules or module types, then these modules will be updated. • SA, and the update is service affecting or non service affecting for the selected modules or module types, then these modules will be updated. The exception is for modules that are part of a channel card protection group. The modules in such a group that are inactive will be updated, while the modules that are active are not updated.

445

Updating Firmware Packages in an NE

Step 11

Select Start Update to start the update process, and select Yes in the Confirmation window that appears.

Field Name

Description

Number of equipment to update

This field shows the number of modules of the selected type that will be updated. The Permitted Effect restriction setting may result in this number being less than the total number of modules of this type in the NE. This field shows the installation progress for the FWP. This field does however not indicate whether the new FWP is in use yet. That information is found in the table below.

Installed

446

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Update of equipment page shows the progress.

Chapter 6 Maintaining NEs

Field Name

Description

Equipment

This column shows the Access Identifier (AID) for each module that is updated in this process. This column shows whether the new FWP has been successfully started. The following messages are used: o Pending, which indicates that the process hasn’t started yet. o Checking Status, which indicates that the Element Manager is waiting for access to the update process on the NE. o Updating which indicates that the process is ongoing. o Finished, which indicates that the Element Manager update process successfully finished. However, the reboot of the modules may not yet be completed. o Update Failed, which indicates that the process has failed and the FWP has not been updated. The module will in this case run the standby revision FWP.

Status

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 12

If the Update of equipment page status table shows that boot up has failed for one of more modules: a) Select back to return to the Update Equipment Firmware (FWP) page. b) Select the module type again. c) Start the FWP update of this module type again, as described in Step 5 through Step 9. d) If the module is part of a channel card protection group: A protection switch may have occurred during the update process. In that case, the process is halted. You must perform a single module FWP update (see “How to Update Firmware for a Single Module” on p. 437) on the module to complete the FWP update. e) If the reboot of the module still fails, contact Technical Support.

User Manual

Step 13

If the NE has channel card protected services: Only the inactive modules have been updated. Now you must update the active modules. Do as follows: • For each of the protection groups, perform a manual protection switch. Now the previously active modules are inactive, and can be updated by multiple equipment updating. • Start the FWP update of this module type again, as described in Step 5 through Step 9.

Step 14

Select Finish to close the Software Control window.

447

Transferring Files To/From the NE

Step 15

After updating the FWP you should re synchronize your system: a) Select the NE you want to reboot in the Managed Elements pane. b) Select Configuration -> Resynchronize on the Main Menu. c) Select Yes in the Confirmation window that appears.

End of Procedure

Transferring Files To/From the NE When making database backups or importing and exporting an alarm profile, it is necessary to transfer files to or from the NE. When transferring files to the NE, a download is done, while when transferring files from the NE, an upload is done. The principle is the same for all file types, but there are some differences. This section describes how to transfer NE software files, database backup files or alarm profile files to an NE, or from an NE. The following topics are provided: “How to Upload Files from the NE” on p. 448

How to Upload Files from the NE This instruction describes how to use the Upload window to upload files from the NE’s file area to another storage place. This storage place can be an external server, or the SCU.

PS

Do not reseat the NCU during the file transfer.

Note

448

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“How to Download Files to the NE” on p. 453

Chapter 6 Maintaining NEs

Procedure Step 1

Select the NE in the Managed Elements pane.

Step 2

If you wish to upload a database backup file: a) From the Main Menu, select Configuration -> Backup/Restore. In response, the Backup/Restore start window is displayed. b) In the NE File Area section, select the relevant Location radio button option to display the file you wish to upload. • Select RDISK to display the files stored on the NCU. • Select SCU to display the files stored on the SCU. If your NE does not have an SCU with hardware revision 2.01 or newer, the NE File Area section will not display Location radio buttons. This is because storage on the SCU is not supported in this case. The NE File Area will display the files stored on the NCU. c) Select the relevant database backup file to upload, in the NE File Area section.

Step 3

If you wish to upload an alarm profile file: a) From the Main Menu, select Fault -> Alarm Profile. In response, the Alarm Profile window is displayed.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

b) Select the Manage Profiles tab. c) Select the relevant alarm profile package file to upload, in the NE File Area section. Step 4

Open the Upload window by selecting the Upload button. In response, the Upload window appears.

User Manual

449

Step 5

The files that shall be uploaded from the NE can be destined to three different places, depending on the file type. Use the Destination drop-down list to specify this. • If the file is destined for an external FTP or SCP server: Select the option Remote File Server. This is relevant for a database backup file or an alarm profile file. • If the file is destined for an external FTP client: Select the option Use FTP Server on NE. This option is only available for database backup files, and only if the NE has an NCU with a 1 GB CompactfFash (CF) installed. In this case there is a local FTP server on board the NE, which can organize the transfer to the external FTP client. The NCU-II is an example of this. The FTP server on an NE is by default disabled, and must be enabled for this option to be available. • If the file is destined for the SCU: Select the option SCU. This option is only available for database backup files, and only if the NE has an SCU with hardware revision 2.01 or newer.

Step 6

Make a decision:

If

Then

If you selected Remote File Server in Step 5 If you selected Use FTP Server on NE in Step 5 If you selected SCU in Step 5

Continue from Step 7 Continue from Step 14 Continue from Step 19

Step 7

Select from the Protocol drop-down list which protocol to use when uploading. 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. If you are not familiar with FTP, see “About FTP and SCP” on p. 459 for a brief overview.

Step 8

450

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

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Transferring Files To/From the NE

Chapter 6 Maintaining NEs

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: • • Step 9

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.

Specify which file to upload as follows: a) Enter the IP address of the FTP or SSH server in the Server field.

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

b) If the file shall be placed in a sub-directory of the FTP or SSH server root directory, enter that relative path in the Path Name field. Otherwise leave this field empty.

Note

Step 10

If the relative path has already been defined in the external server configuration, do not enter anything in the Path Name field. Otherwise, the upload 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 11

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.

Step 12

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 13

User Manual

Go to Step 22.

451

Transferring Files To/From the NE

Step 14

Step 15

In response to your selection of Use FTP Server on NE in Step 5, the Upload window changes.

Enter the user account and password for the NE into the Login and Password fields.

The remote server running on the FSP 3000R7 NE (e.g. acting as a GNE), will not take the case of the user name and password as entered into account. Instead, due to TL1 standards restrictions, the user names and passwords for accounts on an FSP 3000R7 NE are converted to all uppercase before they are saved or validated. Step 16

Select OK to start the upload, or Cancel to discard your entries and return to the Install Software Package window. In response, the Upload window first displays the progress of initializing the FTP server, then the Save window appears.

452

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Whether a user name and password's case (lower/upper case) as entered is taken into account depends on the remote server.

Chapter 6 Maintaining NEs

Step 17

Browse to the location to which you wish to transfer the file and then select Save.

Step 18

Go to Step 22.

Step 19

In response to your selection of SCU as the destination for the upload in Step 5, the Upload window changes.

The Upload file section displays the file name of the backup database file. Check your notes in “How to Manually Back Up the Database” on p. 413, Step 10 to ensure that this is the correct file. Step 20

The backup file name will not be preserved when stored on the SCU, therefore you should write down that the SCU now will contain the backup file name displayed in Step 19, and store this information.

Step 21

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 22

The duration of an upload process to a remote file server depends on the bandwidth of the management connection. When the upload is complete, the Upload window closes.

End of Procedure

How to Download Files to the NE This instruction describes how to use the Download window to download files to the NE.

PS

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Progress is displayed in the lower, left corner of the Backup/Restore window.

Do not disconnect the NCU during the file transfer.

Note

User Manual

453

Transferring Files To/From the NE

Procedure Step 1

Select the NE in the Managed Elements pane.

Step 2

If you wish to download a database backup file: From the Main Menu, select Configuration -> Backup/Restore. In response, the Backup/Restore start window is displayed.

Step 3

If you wish to download an alarm profile file: Do as follows: a) From the Main Menu, select Fault -> Alarm Profile. In response, the Alarm Profile window is displayed. b) Select the Manage Profiles tab.

Step 4

Open the Download window by selecting the Download button.

Step 5

454

The files that shall be downloaded to the NE can be located in three different places, depending on the file type. Use the Source drop-down list to specify where the file is located. • If the file is located on an external FTP or SCP server: Select the option Remote File Server. This is relevant for a database backup file or an alarm profile file. • If the file is located on an internal FTP client: Select the option Use FTP Server on NE. This option is only available for and database backup files, and only if the NE has an NCU with a 1 GB CompactfFash (CF) installed. In this case there is a local FTP server on board the NE, which can organize the transfer from the external FTP client. The NCU-II is an example of this. The FTP server on an NE is by default disabled, and must be enabled for this option to be available. • If the file is located on the SCU: Select the option SCU. This option is only available for database backup files, and only if the NE has an SCU with hardware revision 2.01 or newer.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response, the Download window appears.

Chapter 6 Maintaining NEs

Step 6

Make a decision:

If

Then

If you selected Remote File Server in Step 5 If you selected Use FTP Server on NE in Step 5 If you selected SCU in Step 5

Continue from Step 7 Continue from Step 15 Continue from Step 20

Step 7

Select which protocol to use to transfer the file from its location. Use the Protocol drop down list. 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. If you are not familiar with FTP or SCP, see “About FTP and SCP” on p. 459 for a brief overview.

Step 8

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.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

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: • • Step 9

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.

Enter the IP address of the SCP or FTP server you use, into the Server field.

Ask IT personnel in your organization for this IP address if you do not know it. Step 10

PS

Note

User Manual

Specify the location of the update file 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.

455

Transferring Files To/From the NE

Step 11

Enter the name of the update file, into the File Name field.

Step 12

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 13

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.

Step 14

Select OK to start the upload, or Cancel to discard your entries and return to the Backup/Restore window.

Step 15

Go to Step 23.

Step 16

In response to your selection of Use FTP Server on NE in Step 6, the Download window changes.

Step 17

Enter the user account name and belonging password to gain access to the FTP/SCP server in the Login and Password fields. Whether a user name and password's case (lower/upper case) as entered is taken into account depends on the remote server. The remote server running on the FSP 3000R7 NE (e.g. acting as a GNE), will not take the case of the user name and password as entered into account. Instead, due to TL1 standards restrictions, the user names and passwords for accounts on an FSP 3000R7 NE are converted to all uppercase before they are saved or validated.

456

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Progress is displayed in the lower, left corner of the Backup/Restore window.

Chapter 6 Maintaining NEs

Step 18

Start the download by selecting OK. In response, the Download window first displays the progress of initializing the FTP or SSH server, then the Select window appears.

Step 19

Browse to the location where the file you wish to transfer to the NE is located, select the relevant file and then select Select.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Progress is displayed in the lower, left corner of the Backup/Restore window. Step 20

Go to Step 23.

Step 21

In response to your selection of SCU as the destination for the download, the Download window changes.

The Download file section displays the name of the database file that is present on the SCU. However, the original name of the database file was not preserved when it was stored on the SCU. Therefore the name always is shown as “SCU.DBS”. You must consult the notes you made in “How to Manually Back Up the Database” on p. 413, Step 10 to know which file this is.

User Manual

457

Rebooting

Step 22

Select OK to start the download, 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 23

The duration of the download process depends on the bandwidth of the management connection. For example, a software package file is typically around 50 MB, and downloading can take from a few minutes or up to 50 minutes on a slow connection. When the download is complete, the Download window closes.

End of Procedure

Rebooting It is possible to reboot the NE, as well as make a cold or warm start on individual modules. The following topics are provided: “Re-initiating a Module” on p. 459

Rebooting the NE This instruction describes how to reboot the NE.

Procedure Step 1

Select any equipment in the Entities pane.

Step 2

From the Main Menu, select Configuration->Reboot NCU. In response a warning window will appear.

Step 3

Start the reboot by selecting Yes or cancel by selecting No. In response the NE will be rebooted. The reboot takes approximately 5 minutes. If you are on site with the NE, you can observe that the reboot is complete and the NE ready for management access again. The NE indicates this by four consecutive beeps and the MOD LED of the NCU shining solid green.

End of Procedure

458

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

“Rebooting the NE” on p. 458

Chapter 6 Maintaining NEs

Re-initiating a Module This instruction describes how to re-initiate a module, by performing either a cold or a warm start.

Procedure Step 1

Double-click the relevant NE in the Managed Elements pane. In response, the Information pane displays.

Step 2

Select the module in the Entities pane. In response, all available information about the entity is displayed in the Parameters pane.

Step 3

Select the State tab in the Parameters pane. In response the current states for the module are displayed.

Step 4

Select the Reinit button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Reinit window appears.

Step 5

Use the Effect drop-down list to select a warm or cold start: • The option NSA is non-service affecting, and results in a warm start of the module. • The option SA is service affecting, and results in a cold start of the module.

Step 6

Select OK to continue. In response the Equipment Removed alarm is raised. This alarm is cleared when the restart is completed. Observe this from the Current Conditions table.

End of Procedure

About FTP and SCP These client/server protocols allow an user to transfer files to and from a remote network site. SCP is a more secure protocol than FTP. An FTP or SCP site is a computer that is running FTP or SCP server software.

User Manual

459

About FTP and SCP

An FTP or SCP client is the application on the user’s computer that allows the user to access the FTP or SCP server. Thus the user can get access to files stored on the FTP or SCP server. Most organizations have an FTP or SCP server already. A number of software packages for FTP or SCP clients/servers exist. Consult the IT personnel in your organization to learn whether you have an FTP or SCP server, and how to use it to move files. The following topics are provided: “How to Move Files to an External Server” on p. 460 “How to Move a Database Backup from an External Server” on p. 461

How to Move Files to an External Server The following instruction is general and provided solely to give an impression of the steps to follow when moving a file from a local computer to the FTP or SCP server. You should ask the IT personnel in your organization for the exact instructions for the software packages that your organization uses.

Procedure Connect to the FTP or SSH server. To do this you need the IP address of the server. Ask the IT personnel in your organization for this. You will need this IP address again when using the Element Manager to move the files to the NE. Step 2

Authenticate yourself to gain access to the files on the FTP or SCP server. To do this you need a user account name and the belonging password for the server. Ask the IT personnel in your organization for this. You will need this information again when using the Element Manager to move the files to the NE.

Step 3

Navigate around the folders and files on the server to identify the location you wish to place a NE Software Package or database backup file. Ask the IT personnel in your organization for the necessary commands to do this.

Step 4

Place the NE Software Package that you received from ADVA Optical Networking Optical Networking, or the database backup file you have stored locally, in the FTP or SSH server. Ask the IT personnel in your organization for the necessary commands to do this.

Step 5

460

Logout from the FTP or SSH server.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 1

Chapter 6 Maintaining NEs

Step 6

Disconnect from the FTP or SSH server. The Software Package files and/or database backup files are now ready for the Element Manager to fetch.

End of Procedure

How to Move a Database Backup from an External Server The following instruction is general and provided solely to give an impression of the steps to follow when moving a database backup file from the FTP or SCP server to a local computer. You should ask the IT personnel in your organization for the exact instructions for the software packages that your organization uses.

Procedure Step 1

Connect to the FTP or SSH server. To do this you need the IP address of the server. Ask the IT personnel in your organization for this.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 2

Authenticate yourself to gain access to the files on the FTP or SCP server. To do this you need a user account name and the belonging password for the server. Ask the IT personnel in your organization for this.

Step 3

Navigate around the folders and files on the server to identify the location you wish to place the database backup file. Ask the IT personnel in your organization for the necessary commands to do this.

Step 4

Move the database backup file in the FTP or SSH server to a location in your organization’s LAN, that is part of a regular backup plan. Ask the IT personnel in your organization for the necessary commands to do this.

Step 5

Logout from the FTP or SSH server.

Step 6

Disconnect from the FTP or SSH server.

End of Procedure

User Manual

461

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

About FTP and SCP

462

User Manual

Appendix A Communication Port Overview Ports used for communication between Element Manager and NEs:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Table 11:

Communication Ports

UDP Port

Description of use

161 162

SNMP requests SNMP traps

In the message log you can see the message Listening to UDP Port 162 when Element Manager has been started. If any other utility has been started and uses port 162, the message log will show the message Error binding to UDP Port 162. This indicates that port 162 is busy.

User Manual

463

464

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Appendix B Description of States This is a description of all states the network element can have. The following topics are provided:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Administrative States, which describes the administrative states for the network element and which implications these states have. Operational States, which describes the operational states for the network element and which implications these states have.

Administrative States The administrative state is user settable and controls configuration and operation of each entity. When the administrative state changes to any state other than “In Service”, an informative condition is raised, indicating that the administrative state has changed. These condition names all begin with “OOS”, indicating Out of Service.

In Service While in this administrative state (IS), normal surveillance can take place. You may not perform any operation or configuration that affects service. You can only set an entity’s administrative state to “In Service” if the entity that supports it is also “In Service”.

Automatic In Service When equipment is set to this administrative state (AINS), alarms are not reported. You may not perform any operation or configuration that affects service. Transition from this state to “In Service” takes place automatically, when all alarms on the module or any pluggable transceiver causing the “Outage” or “Supporting Entity Outage” operational states are cleared. You can only set a the administrative state of a piece of equipment to “Automatic In Service” if any equipment that supports it is also “Automatic In Service” or “In Service” and the entity that it supports is not “In Service”.

User Manual

465

Administrative States

When facilities are set to this administrative state (AINS), alarms are not reported and performance monitoring records are invalid. You may not perform any operation or configuration that affects service. Transition from this state to “In Service” takes place automatically, when all alarms 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 it supports is not “In Service”.

Management While in this administrative state (MGT), you may perform service affecting configurations. That is, it might lead to payload traffic loss in which alarms are not reported, and performance monitoring records are invalid. Therefore, consider the consequences when using this state. Contact your local technical support team if there is any uncertainty. You can only set an entity’s administrative state to “Management” if the entity that supports it is not “Disabled” and the entity that it supports is not “In Service” or not “Automatic In Service”.

While in this administrative state (MT), you may perform service affecting operations. That is, it might lead to payload traffic loss in which alarms are not reported, and performance monitoring records are invalid. Therefore, consider the consequences when using this state. Contact your local technical support team if there is any uncertainty. You can only set an entity’s administrative state to “Maintenance” if the entity that supports it is not “Disabled” and the entity that it supports is not “In Service” or not “Automatic In Service”.

Disabled While in this administrative state (DSBLD), all alarm notifications from the entity are stopped. Performance monitoring is disabled. If traffic on the entity is affected then this is shown by a corresponding "OOS Tx Disabled (OFF)" or "OOS Rx Disabled" condition. You may perform service affecting configurations. You can only set an entity’s administrative state to “Disabled” if the entity that it supports is “Disabled” or “Unassigned”.

Unassigned You enter this administrative state (UAS) automatically when an entity is installed, but not provisioned to the internal database. As a consequence, only inventory information is available for this entity. In the management tools, the administrative state is therefore displayed in parentheses behind the entity name in the list of entities.

466

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Maintenance

Appendix B Description of States

Operational States An entity’s operational state is influenced by the administrative state and current conditions.

Normal This operational state indicates that the entity is running normally.

Abnormal This operational state indicates that a signal degrade condition is present on the entity.

Outage This operational state indicates that service is affected on this entity. This state will be accompanied by a secondary state, and together with this and the current list of conditions, the cause for the outage can be found.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Unavailable This operational state indicates that the entity cannot pass traffic, but that this is not due to a defect. This operational state is entered when the entity’s administrative state is either “Disabled” or “Unassigned”, and there is no secondary state present. This operational state is entered when the entity’s administrative state is “Disabled”, and there is no secondary state present.

Secondary States Unequipped This autonomous state (UEQ) indicates that the equipment it is associated with is not present in the NE. In the management tools, the state is displayed in parenthesis behind the entity name in the Entity List. Provisioning is allowed according to the current administrative state for the entity. For the entity with the associated Unequipped state: all autonomous standing conditions except “Removed” are cleared and performance monitoring records are nulled and invalid. For supporting equipment, all autonomous standing conditions are cleared and performance monitoring records are nulled and invalid.

Mismatch This autonomous state (MEA) indicates that the equipment it is associated with does not match the equipment that was assigned during provisioning, or that this equipment is disallowed in this position. In the management tools, the state is displayed in parenthesis behind the entity name in the Entity List.Provisioning is allowed according to the current administrative state for the entity. For the entity with the associated Mismatch state: all autonomous standing conditions except MEA are cleared and performance monitoring records are nulled and invalid. For supporting equipment, all autonomous standing conditions are cleared and performance monitoring records are nulled and invalid.

User Manual

467

Operational States

Fault This state (FLT) indicates that the associated equipment has a fault. The equipment, and the equipment supported by this equipment, is unable to perform their provisioned tasks. The equipment supported by this equipment will have the SGEO state associated with it. The list of conditions for this equipment will detail the fault.

Supporting Entity Outage This autonomous state (SGEO) has a variety of root-causes, for example: •

The supporting equipment is unequipped.

•

The supporting equipment does not match the assigned supporting equipment.

•

The supporting equipment has a fault condition.

•

The entity has an outage of management communication

•

Port related secondary states:

Busy This state (BUSY) indicates that an ECC is provisioned, and cross-connected to a PPP/IP entity on the NCU module.

This state (IDLE) indicates that an ECC is provisioned, but not cross-connected to a PPP/IP entity on the NCU module.

Facility Failure This state (FAF) indicates that the associated facility has a failure, the list of conditions for this facility will detail the failure.

Auto Locked-Out This state (LKDO) indicates that the associated facility is autonomously suspended. This facility enters this state as a consequence of an event. This specific event can be found in the Current Conditions list, the condition name begins with “LKDO”. Protection related secondary states:

Active This state (ACT) indicates that the associated protection group is active.

Standby Hot This state (STBYH) indicates that the entity is part of a protection group, and is the hot standby entity.

PROTN Switch Inhibited When this state (PSI) is true, it indicates that switching from the working to the protection facility is inhibited. This state is associated with the working facility.

468

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Idle

Appendix B Description of States

WKG Switch Inhibited When this state (PRI) is true, it indicates that switching from the protection to the working facility is inhibited. Operation related secondary states:

Loopback This state (LPBK) indicates that a loopback is set on the associated facility. Forced On This state (FRCD) indicates that the laser transmitter of the entity is forced on.

Diagnostic

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This state (DGN) indicates that service affecting diagnostic activity is being performed on the port.

User Manual

469

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Operational States

470

User Manual

Appendix C RADIUS Authentication Setup This appendix is written for the administrator of an Element Manager managed network configuration, and where RADIUS shall be used as the authentication method.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

When RADIUS authentication is used to access the Element Manager, the Element Manager uses SNMP access profiles to access the SNMP agents on the managed NEs. This can only be done if the NEs support SNMPv3. The appendix describes how to enable use of RADIUS authentication, define the RADIUS servers and SNMP access profiles for an Element Manager installation, as well as any IP subnet restrictions for the Element Manager installation. In addition it describes how these settings can be distributed to other Element Manager installations. This appendix contains the following sections: “Setting up RADIUS Authentication” on p. 472 “Defining RADIUS Servers” on p. 472 “Enabling RADIUS Authentication” on p. 475 “Configuring SNMP Access Profiles” on p. 476 “Configuring IP Subnet Restrictions” on p. 486

User Manual

471

Setting up RADIUS Authentication

Setting up RADIUS Authentication This instruction describes how to setup and enable use of RADIUS authentication for the Element Manager.

Procedure Step 1

Ensure that RADIUS servers have been configured and are reachable for the Element Manager.

Step 2

Specify the RADIUS servers that the Element Manager shall contact for authentication. See “Defining RADIUS Servers” on p. 472.

Step 3

Configure the SNMP profiles that match the RADIUS privilege levels for the NEs. See “Configuring SNMP Access Profiles” on p. 476.

Step 4

If relevant, specify IP subnet restrictions for the Element Manager. See “Configuring IP Subnet Restrictions” on p. 486.

Step 5

Enable use of RADIUS authentication on the Element Manager. See “Enabling RADIUS Authentication” on p. 475.

End of Procedure

Defining RADIUS Servers This procedure describes how to define RADIUS servers that can be used for authentication, and how to add each of them to the list of RADIUS servers that will be used for authentication.

Requirements •

472

You must be logged in with an account with administrator privilege level.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Setting up RADIUS servers is outside the scope of this document, however an overview of how this can be done for one RADIUS server type is given in Appendix D “Configuring a RADIUS Server” on p. 491.

Appendix C RADIUS Authentication Setup

Procedure Step 1

Select Security->SNMPv3 via RADIUS.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMPv3 via RADIUS window appears.

Step 2

Make a choice: • To add a RADIUS server go to Step 3. • To modify a RADIUS server go to Step 11. • To remove a RADIUS server go to Step 19.

Step 3

To add a RADIUS server, select Add. In response the Add RADIUS Server window appears.

Step 4

Enter the IP address for the RADIUS server into the IP Address field. This IP address much be reachable for the Element Manager.

Step 5

Enter the port that the RADIUS server uses to communicate with the Element Manager with. The default value is 1812, and is normally suitable. This could however depend on the RADIUS server application that is used, please check the documentation for that application to confirm.

Step 6

User Manual

Enter into the Timeout field how long time the Element Manager shall try to connect to a RADIUS server before giving up.

473

Defining RADIUS Servers

Step 7

Enter the maximum number of times the Element Manager shall retry connecting to a RADIUS server, in the Retries field. The maximum number of retries is 5.

Step 8

Enter the shared secret the Element Manager shall use when connecting to the RADIUS server into the Shared Secret and Retype Shared Secret fields.

Step 9

Enable use of this RADIUS server by placing a check mark in the Enabled check box. This RADIUS server will not be used by the Element Manager until it has been enabled for use. It can be enabled at a later time as well.

Step 10

Select OK to apply your entries or Cancel to discard them.

Step 11

To modify an already defined RADIUS server, select Modify.

Step 12

Enter the port that the RADIUS server uses to communicate with the Element Manager with. The default value is 1812, and is normally suitable. This could however depend on the RADIUS server application that is used, please check the documentation for that application to confirm.

Step 13

Enter into the Timeout field how long time the Element Manager shall try to connect to a RADIUS server before giving up.

Step 14

Enter the maximum number of times the Element Manager shall retry connecting to a RADIUS server, in the Retries field. The maximum number of retries is 5.

Step 15

Enter the shared secret the Element Manager shall use when connecting to the RADIUS server into the Shared Secret and Retype Shared Secret fields.

Step 16

Enable use of this RADIUS server by placing a check mark in the Enabled check box. This RADIUS server will not be used by the Element Manager until it has been enabled for use. It can be enabled at a later time as well.

474

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify RADIUS Server window appears.

Appendix C RADIUS Authentication Setup

Step 17

If relevant, modify the shared secret the Element Manager shall use when communicating with the RADIUS server. Do as follows: a) Place a check mark in the Change Shared Secret field. In response the Shared Secret and Retype Shared Secret fields appear. b) Use the Shared Secret and Retype Shared Secret fields to change the shared secret.

Step 18

Select OK to apply your changes or Cancel to discard them.

Step 19

To remove a RADIUS server from the list, do as follows: a) Select it in the SNMPv3 via RADIUS window, RADIUS tab. b) Select Remove.

Step 20

Select OK to close the SNMPv3 via RADIUS window.

End of Procedure

Enabling RADIUS Authentication FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This procedure describes how to enable use of RADIUS authentication for the Element Manager installation.

Requirements •

You can be logged in with any privilege level.

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

User Manual

475

Configuring SNMP Access Profiles

Step 2

Enable RADIUS authentication by placing a check mark in the Use RADIUS for authentication check box.

When authenticating a user the Element Manager will connect to the RADIUS servers listed in this window. The Element Manager will only attempt to connect to enabled servers, and in the sequence that they are listed here. Step 3

Select OK to apply your changes or Cancel to discard them.

End of Procedure

Configuring SNMP Access Profiles

The Element Manager checks the IP address of the NE that a user connects to, and if this address is part of a IP subnet for which an SNMP access profile exists, it will use the SNMP access parameters defined in that SNMP access profile. If no such specific SNMP access profile is found, the Element Manager will use the default SNMP access profile. The Element Manager cannot manage NEs unless the default SNMP access profile has been configured. This section describes how to configure the two SNMP access profile types for the Element Manager. The following sections are provided: “Adding a Default SNMP Access Profile” on p. 476 “Clearing a Default SNMP Access Profile” on p. 478 “Adding an SNMP Access Profile for an IP Subnet” on p. 479 “Modifying an SNMP Access Profile for an IP Subnet” on p. 482 “Removing an SNMP Access Profile for an IP Subnet” on p. 484

Adding a Default SNMP Access Profile This procedure describes how to add the default SNMP profile.

Requirements •

You must be logged in with administrator privilege level.

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

476

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Two types of SNMP access profiles can be defined, a default one and multiple ones for specific IP subnets. This allows the administrator to set up different SNMP access parameters for different sub nets.

Appendix C RADIUS Authentication Setup

Step 2

Select the SNMP tab. In response the SNMPv3 via RADIUS window displays the SNMP tab.

Step 3

Select the Default SNMP Access profile radio button.

Step 4

Select Modify.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the Modify Default Profile window appears.

Step 5

Enter the user account name the Element Manager shall use when sending SNMP Get and Set requests to the NEs in the network configuration, in the User field. This user account name must exist on each NE that shall be accessed, before the Element Manager can actually access it. See “Handling Network Element User Accounts” on p. 214 for instructions on adding user accounts on NEs. Notice that you will have to log in to Element Manager using local authentication when following the procedure in this case.

Step 6

Enter the authentication password in the Authentication Password field. This password must be upper case and minimum 8 characters long. The security level and authentication type cannot be changed and are set to AuthPriv and MD5 respectively.

User Manual

477

Configuring SNMP Access Profiles

Step 7

Enter the privacy password in the Privacy Password field. This password must be upper case and minimum 8 characters long. The privacy type that will be used is AES 128.

Step 8

Select OK to apply your entries, or Cancel to cancel them. In response the SNMP tab content changes.

Select OK to close the SNMPv3 via RADIUS window.

End of Procedure

Clearing a Default SNMP Access Profile This procedure describes how to clear the default SNMP profile.

Requirements •

You must be logged in with an account with administrator privilege level.

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

478

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Step 9

Appendix C RADIUS Authentication Setup

Step 2

Select the SNMP tab. In response the SNMPv3 via RADIUS window displays the SNMP tab.

Step 3

Select the Default SNMP Access profile radio button.

Step 4

Select Clear.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMP tab content changes.

Step 5

Select OK to close the SNMPv3 via RADIUS window.

End of Procedure

Adding an SNMP Access Profile for an IP Subnet This procedure describes how to add an SNMP profile for an IP subnet.

Requirements •

User Manual

You must be logged in with an RADIUS account with administrator privilege level.

479

Configuring SNMP Access Profiles

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

Step 2

Select the SNMP tab.

Step 3

Select the SNMP Access profiles for IP subnets radio button. In response the SNMP tab content changes.

480

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMPv3 via RADIUS window displays the SNMP tab.

Appendix C RADIUS Authentication Setup

Step 4

Select Add. In response the Add Profile window appears.

Step 5

Enter the IP address for the IP subnet into the IP Address field.

Step 6

Enter the sub net mask for the IP subnet into the Subnet Mask field.

Step 7

Enter the user account name the Element Manager shall use when sending SNMP Get and Set requests to the NEs in the IP subnet, in the User field.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

This user account name must exist on each NE that shall be accessed, before the Element Manager can actually access it. See “Handling Network Element User Accounts” on p. 214 for instructions on adding user accounts on NEs. Notice that you will have to log in to Element Manager using local authentication when following the procedure in this case. Step 8

Enter the authentication password in the Authentication Password field. This password must be upper case and minimum 8 characters long. The security level and authentication type cannot be changed and are set to AuthPriv and MD5 respectively.

Step 9

Enter the privacy password in the Privacy Password field. This password must be upper case and minimum 8 characters long. The privacy type that will be used is AES 128.

User Manual

481

Configuring SNMP Access Profiles

Step 10

Select OK to apply your entries, or Cancel to cancel them. In response the SNMP tab content changes.

Step 11

Select OK to close the SNMPv3 via RADIUS window.

Modifying an SNMP Access Profile for an IP Subnet This procedure describes how to modify an SNMP profile for an IP subnet.

Requirements •

You must be logged in with an account with administrator privilege level.

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

482

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Appendix C RADIUS Authentication Setup

Step 2

Select the SNMP tab. In response the SNMPv3 via RADIUS window displays the SNMP tab.

Step 3

Select the SNMP Access profiles for IP Subnets radio button.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMP tab content changes.

Step 4

Select Modify. Modify Profile window appears.

User Manual

483

Configuring SNMP Access Profiles

Step 5

Modify the user account name the Element Manager shall use when sending SNMP Get and Set requests to the NEs in the IP subnet, in the User field. This user account name must exist on each NE that shall be accessed, before the Element Manager can actually access it. See “Handling Network Element User Accounts” on p. 214 for instructions on adding user accounts on NEs. Notice that you will have to log in to Element Manager using local authentication when following the procedure in this case.

Step 6

Enter the authentication password in the Authentication Password field. This password must be upper case and minimum 8 characters long. The security level and authentication type cannot be changed and are set to AuthPriv and MD5 respectively.

Step 7

Enter the privacy password in the Privacy Password field. This password must be upper case and minimum 8 characters long. The privacy type that will be used is AES 128.

Step 8

Select OK to apply your entries, or Cancel to cancel them.

Step 9

Select OK to close the SNMPv3 via RADIUS window.

End of Procedure

Removing an SNMP Access Profile for an IP Subnet This procedure describes how to remove an SNMP profile for an IP subnet.

Requirements •

484

You must be logged in with an account with administrator privilege level.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMP tab content changes.

Appendix C RADIUS Authentication Setup

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

Step 2

Select the SNMP tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMPv3 via RADIUS window displays the SNMP tab.

Step 3

Select the SNMP Access profiles for IP subnets radio button. In response the SNMP tab content changes.

Step 4

Select the IP sub net to remove SNMP access parameters for in the list.

Step 5

Select Remove. In response the IP sub net information is removed from the list.

User Manual

485

Configuring IP Subnet Restrictions

Step 6

Select OK to close the SNMPv3 via RADIUS window.

End of Procedure

Configuring IP Subnet Restrictions It is possible to restrict the users to only be able to manage NEs that are in one or more specific IP subnets. When an user defines an NE to manage or starts the Element Manager, the Element Manager checks whether any restricted IP subnets have been defined for this Element Manager. If a restricted subnet has been defined, the Element Manager checks whether the NE that is being defined for management is within the restricted subnet(s). If it is not, the user will be denied the possibility to manage this NE. Otherwise the NE can be managed. A restricted IP subnet can also require use of specific SNMP access parameters, in which case a matching SNMP profile must be created.

This section describes how to define restricted IP subnets for the Element Manager. The following sections are provided: “Adding a Restricted IP Subnet” on p. 486 “Removing a Restricted IP Subnet” on p. 488 “Enabling Restricted IP Subnets Access” on p. 489

Adding a Restricted IP Subnet One or more IP subnets can be added to the IP subnet restrictions list. Users will only be able to manage NEs that are in these IP subnets, when the list has been enabled. This procedure describes how to add an restricted IP subnet.

PS

If the IP subnet restriction feature already is enabled, addition of an IP subnet takes effect the next time the Element Manager is started.

Note

Requirements •

486

You must be logged in with an account with administrator privilege level.

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

A number of IP subnets can be added to the list, but if the use of restricted IP subnets has not been enabled, they will have no effect. Any change to the list of restricted IP subnets after this feature has been enabled, requires a re-start of the Element Manager to take effect.

Appendix C RADIUS Authentication Setup

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

Step 2

Select the IP Subnet Restrictions tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMPv3 via RADIUS window displays the IP Subnet Restrictions tab.

Step 3

Select Add. In response the Add IP Subnet Restriction window appears.

User Manual

Step 4

Enter the IP address for the IP subnet into the IP Address field.

Step 5

Enter the sub net mask for the IP subnet into the Subnet Mask field.

487

Configuring IP Subnet Restrictions

Step 6

Select OK to apply your entries, or Cancel to cancel them. In response the IP Subnet Restrictions tab content changes.

Step 7

Select OK to close the SNMPv3 via RADIUS window.

Removing a Restricted IP Subnet This procedure describes how to remove an already defined IP subnet from the list of IP subnet restrictions.

PS

If the IP subnet restriction feature already is enabled, removal of an IP subnet takes effect the next time the Element Manager is started.

Note

Requirements •

You must be logged in with an account with administrator privilege level.

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

488

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Appendix C RADIUS Authentication Setup

Step 2

Select the IP Subnet Restrictions tab.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMPv3 via RADIUS window displays the IP Subnet Restrictions tab.

Step 3

Select the relevant IP subnet in the list.

Step 4

Select Remove. In response the IP subnet is removed from the IP subnet restrictions list.

Step 5

Select OK to close the SNMPv3 via RADIUS window.

End of Procedure

Enabling Restricted IP Subnets Access This procedure describes how to enable use of restricted IP subnets. The Element Manager must be restarted afterwards for the change to take effect.

Requirements •

You must be logged in with an account with administrator privilege level.

Procedure Step 1

Select Security->SNMPv3 via RADIUS. In response the SNMPv3 via RADIUS window appears.

User Manual

489

Configuring IP Subnet Restrictions

Step 2

Select the IP Subnet Restrictions tab.

Step 3

Place a check mark in the Enable IP Subnet Restrictions check box.

Step 4

Select OK to apply your changes and close the SNMPv3 via RADIUS window.

Step 5

In response a warning window appears.

Step 6

Make a choice: • Select OK for your entry to be stored. It will take effect, the next time you start the Element Manager. • Select Cancel to cancel your entry and return to the SNMPv3 via RADIUS window for further configuration.

End of Procedure

490

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In response the SNMPv3 via RADIUS window displays the IP Subnet Restrictions tab.

Appendix D Configuring a RADIUS Server This appendix describes how to configure a RADIUS server that can be used for remote authentication of Element Managers. It also describes how to test that it works for authentication.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

In principle any RADIUS server application can be used, this appendix is based on using the FreeRADIUS server application for Windows. The FreeRADIUS server application is available from http://freeradius.org/. It is one of the most widely deployed RADIUS servers in the world. This procedure describes how to configure a RADIUS server so it can be used for authentication of users.

Procedure Step 1

Install and start a RADIUS server.

Step 2

In the RADIUS server, specify the privilege levels that are supported by the FSP 3000R7s (clients) that will use this RADIUS server.

Step 3

If necessary, modify the port that the RADIUS server uses to communicate with the Element Manager.

Step 4

Define the IP address for the Element Managers (clients) that will use this RADIUS server and the shared secret that the RADIUS server and Element managers (clients) will use.

Step 5

Define as many RADIUS user accounts as needed, including name, password and user level for each of them.

End of Procedure The following supporting sections are provided: “Installing and Starting a RADIUS Server” on p. 492 “Specifying Privilege Levels” on p. 493 “Modifying the Port for RADIUS Authentication” on p. 494 “Defining the Element Manager IP Addresses” on p. 495

User Manual

491

“Defining RADIUS User Accounts” on p. 495

Installing and Starting a RADIUS Server This procedure describes how to install and start a RADIUS server application.

PS

Note

You must stop and restart the server whenever changes are made to the RADIUS server’s configuration file. This is necessary because the daemon must build a memory table of all default attributes contained in the configuration files.

Procedure Step 1

Run the installer Setup Wizard on a computer that is reachable for the network elements.

Step 2

Start the RADIUS server application. An icon will appear in the system tray of your taskbar to show it is running. The default directory structure created by the installer looks like the following:

FreeRadius Server Directory FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Figure 30:

End of Procedure

492

User Manual

Appendix D Configuring a RADIUS Server

Specifying Privilege Levels The privilege levels, their attributes, and values for the FSP 3000R7 shall be defined in a dictionary file. The privilege levels for the FSP 3000R7 are the same as for the NEs, and therefore the dictionary file for the NE can be used. This dictionary file is located in the directory /usr/local/data/ on the NE. This dictionary file uses FreeRADIUS compatible syntax. Figure 31: #

Example of RADIUS Dictionary File

Dictionary for ADVA

#

Optical Networking

Fiber Service Platform

# #

http://www.advaoptical.com

# see http://www.iana.org/assignments/enterprise-numbers VENDOR

Adva

2544

#note this is the syntax for Freeradius, ATTRIBUTE

Adva-User-Level 100

integer

Adva

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

# #ATTRIBUTE

Adva

Adva-User-Level 100

integer

VALUE

Adva-User-Level

Super

5

VALUE

Adva-User-Level

Admin

4

VALUE

Adva-User-Level

Provision

3

VALUE

Adva-User-Level

Operate_Control 2

VALUE

Adva-User-Level

Reserved

1

VALUE

Adva-User-Level

Retrieve

0

ATTRIBUTE

Adva-UUM-User-Level

102

integer

Adva

# #ATTRIBUTE

Adva

Adva-UUM-User-Level

102

integer

VALUE

Adva-UUM-User-Level

Root

5

VALUE

Adva-UUM-User-Level

Admin

4

VALUE

Adva-UUM-User-Level

Provision

3

VALUE

Adva-UUM-User-Level

Operator

2

VALUE

Adva-UUM-User-Level

Reserved

1

VALUE

Adva-UUM-User-Level

Monitor

0

Note that only the text in bold is required for the FSP 3000R7 Element Manager; the other definitions are for the FSP 2000 Element Manager and can remain in this file. Lines starting with # are comments. The privilege levels Root, Provision and Monitor correspond to the Element Manager user account names Administrator, Provision and Monitor.

User Manual

493

This procedure describes how to provide the RADIUS server with the FSP 3000R7’s privilege levels.

Procedure Step 1

Download the dictionary file from a network element to your management computer, using SCP or FTP.

Step 2

If necessary, use Notepad (for example) to edit the dictionary file as necessary so its syntax conforms with that required by your RADIUS server.

Step 3

If using FreeRADIUS under Linux, add the following line to the dictionary file: $INCLUDE dictionary.adva.

Step 4

Copy the dictionary file to the RADIUS server. a) For FreeRADIUS on Windows, place the dictionary file in the location C:\FreeRADIUS.net\share\freeradius. b) For FreeRADIUS on Linux, place the dictionary file in the location /usr/share/freeradius.

Modifying the Port for RADIUS Authentication The RADIUS server uses the file radiusd.conf to define which port the network element will listen on. Use a text editor to open and modify the file as follows:

Procedure Step 1

Open the file located in C:\FreeRADIUS.net\etc\raddb\radiusd.conf.

Step 2

Modify the default entry port = 0 to port = 1812. If the NE is configured for any other port, change the number accordingly.

Step 3

Modify the “reject_delay” setting to “reject_delay = 0”. This means to send rejects immediately.

End of Procedure

494

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

Appendix D Configuring a RADIUS Server

Defining the Element Manager IP Addresses To define the IP address of the Element Managers that will use the RADIUS server, you must open the file that contains the list of clients that are allowed to make requests to the RADIUS server. For each client you must enter the network element (client) IP address along with the shared secret between the server and the client. Use a text editor to open and modify the file as follows:

Procedure Step 1

Open the file clients.conf located in C:\FreeRADIUS.net\etc\raddb\. This is an example of content:

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

client 172.18.0.0/16 secret = advasecret123 shortname = TS-LAB-Network Step 2

For each Element Manager client, add an entry in the same fashion, containing: • client IP-address/mask for the Element Manager client • the shared secret the Element Manager will use when communicating with the RADIUS server. • the shortname for the Element Manager is optional and used for logging purposes only.

Step 3

Save the edited file and close it.

End of Procedure

Defining RADIUS User Accounts This procedure describes how to define a RADIUS user account for an Element Manager user.

Procedure Step 1

Make a note of the following information for the account: • RADIUS user account name • RADIUS user account password • Element Manager privilege level for the RADIUS user account.

Step 2

Look up which RADIUS privilege level that corresponds to the Element Manager privilege level.

Table 12:

User Manual

Element Manager versus RADIUS Privilege Levels

EM Privilege Level

RADIUS Privilege Level

Administrator Provision Monitor

Super Admin Retrieve

495

Step 3

Use a text editor to open the file users.conf located in C:\FreeRADIUS.net\etc\raddb\.

Step 4

Define the Element Manager’s RADIUS user account by adding the following text: • Auth-Type := Local • User-Password == “RADIUS user account password>” • ADVA-UUM-User-Level = “” For example: David Auth-Type := Local User-Password == “David’s secret” ADVA-UUM-User-Level = “Root”

Step 5

Restart the “FreeRADIUS.net” service on the Windows PC to apply settings.

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

End of Procedure

496

User Manual

Index A

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

admin state 118 alarm history log 168, 191, 195, 208, 212, 373, 374 alarms 61, 76 color coding 370 disable reporting 370 inhibiting 370 severity 374 Area ID 118

C change password 59 comma separated file 168, 191, 195, 208, 212, 373, 374 community 54

E Entity pane 63 entity pane pane entity 63 equipment pane 63 events 76

F FSP Network Manager (FSP NM) 31 see also Network Management System

User Manual

497

G Graphical User Interface (GUI) 61

H help 77

I information pane 63 IP address 53, 118 NE 40, 76

L

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

Loopback 230

M maximum transmit rate 117 memory 75 modes integrated mode 31

N NE Pane 63 Network Management System (NMS) 31, 62, 76

O OSPF routing 118

P pane entity 63 equipment 63 information 63

498

User Manual

Index

NE 63 parameter 63 parameter pane 63 password 35 change 59 polling mechanism 40 proxy ARP 118

R response messages 76 routing metric 118 Routing Table 274

S

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential

security password 35 SNMP 61, 62 agent 76 community 41, 44 settings 51 traps 62 SNMP Provider 76 communication with 40 standalone 31 System Interface 230 System IP address 230

T TCA Thresholds 321 Trace 316 trap recipients 53 troubleshooting 40, 44, 66

U User Datagram Protocol (UDP) 54, 62 users 35

User Manual

499

500

User Manual

FSP 3000R7 R10.3 80000014705 Issue: B, © 2011 ADVA Optical Networking ADVA Confidential