Man 2563XX 07

TM
Optical Networking
Fiber Service Platform 150 Multiplexer/Hub Node

(FSP 150Mx/CX)
Product Release 2.5.1
2563XA07_TitlePage.fm - 30. October 2007
User Guide
Version 7 (October 2007)
Copyright 2007 ADVA Optical Networking

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without prior written permission of ADVA Optical Networking. Hardware and software mentioned in this document includes software developed by ADVA Optical Networking.
Trademarks
The terms ADVA and FSP are trademarks or registered trademarks of ADVA Optical Networking in the United States, Germany and/or other countries. All other company, product, or service 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 any license to these patents.
Disclaimers
The content of this document could 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 non-ADVA Optical Networking publications and/or non-ADVA Optical Networking Internet sites 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 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.
Tel: Fax: Website:
+49 (0)89 89 06 65 0 +49 (0)89 89 06 65 699 www.advaoptical.com
ii
FSP 150Mx/CX User Guide
2563XA07_TitlePage.fm - 30. October 2007
ADVA AG Optical Networking Headquarters Fraunhoferstrae 9a 82152 Martinsried/Munich Germany
TM
Optical Networking
Preliminaries
The Preliminaries provide general information for the effective use of the Fiber Service Platform 150 Multiplexer/Hub Node (FSP 150Mx/CX) User Guide.
Purpose and Scope

The purpose of the FSP 150Mx/CX User Guide is to provide the following: an overview of the FSP 150 family and the network architectures that the product range can support a description of the traffic services supported a description of the FSP 150Mx/CX components a summary of available management options a description of the management interfaces instructions for configuring the FSP 150Mx/CX and connected devices instructions on how to perform system tests instructions on monitoring the performance of the FSP 150Mx/CX instructions on maintaining the FSP 150Mx/CX instructions on handling FSP 150 Mx/CX faults.
Audience
This guide is intended for use by any one who is involved in the configuration, management and maintenance of the FSP 150Mx/CX. In particular: Service Engineers; and Network Managers.
Prerequisites
Personnel should be familiar with the following:
2563XB07_Prelims.fm - 30. October 2007
Hardware installation and configuration Linux commands and environments Network Ethernet protocols Laser technology.
iii
Preliminaries
Document Revision History

Document Version No. 1 2 Issue Date January 2005 July 2005 Details of Issue Initial Issue. Addition of traffic management features and web-based interface. Addition of integration of the FSP 150CX, ring/chain support, and access control lists. Addition of traffic test and reboot from Craft and Web Interfaces. Addition of Configuration File Management, Audit Logging and Inband IP Management. Addition of Egress Multicast feature for the FSP 150MG. Also addition of enhancements to the remote loopback feature and auto negotiation configuration on an FSP 150CP. Addition of the Command Line Interface (CLI) Topology Presentation feature. Product Releases covered FSP 150Mx 1.0 FSP 150Mx 2.0
April 2006
FSP 150Mx/CX 2.1
July 2006
FSP 150Mx/CX 2.2
March 2007
FSP 150Mx/CX 2.3
August 2007
FSP 150Mx/CX 2.5
October 2007
FSP 150Mx/CX 2.5.1
Associated Documentation
This user guide is part of the FSP 150 Mx/CX document set which includes: The FSP 150 Safety Guide The FSP 150 Installation Guide The FSP 150Mx/CX User Guide (this guide) The FSP 150 Glossary.
Document Outline
This user guide consists of the parts listed in the table below:
Part/Chapter Preliminaries Description The Preliminaries (this part) provide general information for the effective use of the user guide, including the target audience, guide structure and the conventions used. They also provide important ADVA Optical Networking contact details. Provides an introduction to the network architectures that can be achieved using the FSP 150 family and how these networks operate.
Chapter 1, FSP 150 Network Architecture Overview
iv
TM
Optical Networking
Part/Chapter Chapter 2, Features Chapter 3, Components Chapter 4, Management Overview Chapter 5, Management Interfaces Chapter 6, Configuration Chapter 7, Test Procedures Chapter 8, Performance Management Chapter 9, Maintenance
Description Provides information on the traffic features provided by the FSP 150 Mx/CX. Provides information on the components of the FSP 150Mx/CX. Provides information on the management options available for the FSP 150Mx/CX. Provides information on the interface options available for managing the FSP 150Mx/CX. Provides details of how to configure the FSP 150Mx/CX to enable its management over a network. Provides a description of how to perform system tests. Provides details of monitoring counters and statistics. Provides details of how to inspect, back up configuration settings, clean and replace devices, and upgrade firmware and software. Provides details of how to view alarms, and detect and resolve faults. Provides a list of items delivered in the FSP 150Mx/CX package.
Chapter 10, Fault Management Chapter 11, System Data
Document Conventions
Typographic
This user guide uses the following conventions:
Convention Boldface Italic Description Indicates keywords and emphasized words. All warnings are in boldface. Indicates a reference to a chapter, section, figure, table or related documentation when appearing in main text areas. All notes are in italic. Boldface italic Monospace All cautions are in boldface italic font. Indicates a software application menu option or a command button that can be selected by the user or text that is to be input by the user. Indicates a software application main menu bar title, a pulldown menu title, a dialog box title or a window title. Indicates that additional information is available.
Bold monospace ->

Preliminaries
Symbols
This document contains the following safety and operational alert symbols:
This symbol accompanies any statement that draws attention to a risk of personnel injury or death. Warning
This symbol accompanies any statement that draws attention to a laser hazard. Warning
This symbol accompanies any statement that draws attention to the risk of damage to the FSP 150Mx/CX. Caution
This symbol accompanies any statement that draws attention to the possibility of equipment damage due to Electro-Static Discharge. Caution
This symbol accompanies any statement that the user should make a note of.
Documentation
Obtaining Documentation
World Wide Web
The most current ADVA Optical Networking documentation is available on the World Wide Web via your Partner Login at: http://www.advaoptical.com
Documentation CD-ROM
ADVA Optical Networking documentation and additional literature is available on the CD-ROM, which is supplied with the FSP 150 products.
vi
TM
Optical Networking
Documentation Feedback
Feedback on the FSP 150 documentation is always appreciated. Comments may be emailed to: techdocu@advaoptical.com Alternatively, submit comments by mail, to the following address: ADVA Optical Networking Ltd. Technical Documentation Clifton Technology Centre Clifton Moor York YO30 4GU United Kingdom
Technical Assistance
Product maintenance agreements and other customer assistance agreements are available for ADVA Optical Networking products through the ADVA distribution channels. ADVA Optical Networking service options include: 24 x 7 telephone support Web-based support tools On-site support Technical training, both on-site and at ADVA Optical Networking facilities in Germany and the USA Expeditious repair service Extended hardware warranty service.
Partner Login
ADVA Optical Networkings Partner Login provides a suite of interactive, networked services that provide immediate access to ADVA Optical Networking information and resources at any time, from anywhere in the world. Through the Partner Login, information tailored especially for each customer can be found, including networking solutions, services, and programs. In addition, technical issues can be resolved with online support services, software packages can be downloaded and tested, and ADVA Optical Networking training materials can be ordered.
The Partner Login can be accessed via the ADVA Optical Networking homepage at: http://www.advaoptical.com Queries about the Partner Login can be emailed to: Support@ADVAOptical.com
vii
Preliminaries
Technical Support
Technical assistance is available for any product, supplied by ADVA Optical Networking, which is under warranty or covered by a maintenance contract. A Technical Support web page is available on the ADVA Optical Networking website, which provides all contact information for technical support. To access this page go to the ADVA Optical Networking homepage at: http://www.advaoptical.com and select Support. Alternatively, to contact by email, use one of the following: Europe: North America: Asia: Support@ADVAOptical.com Support-usa@ADVAOptical.com Support-asia@ADVAOptical.com
Equipment Return and Repair

For assistance in returning a faulty FSP 150 for manufacturer repair, contact ADVA Optical Networking Technical Support. See Technical Support above for contact details.
Contacting ADVA
ADVA AG Optical Networking Headquarters Campus Martinsried Fraunhoferstrae 9a 82152 Martinsried/Munich Germany ADVA AG Optical Networking Groer Kolonnenweg 18D 30163 Hannover Germany ADVA Optical Networking Inc. One International Blvd, Suite 705 Mahwah, NJ 07495 USA ADVA Optical Networking Ltd. Clifton Technology Centre Clifton Moor York, YO30 4GU United Kingdom Tel: +49 (0)89 89 06 65 0 Fax: +49 (0)89 89 0665 22848 info@advaoptical.com
Tel: +49 (0)511 3365 070 Fax: +49 (0)511 3365 0755 info@advaoptical.com Tel: +1 201 258 8300 Fax: +1 201 684 9200 info@advaoptical.com Tel: +44 (0)1904 692 700 Fax: +44 (0)1904 692 097 info@advaoptical.com
viii
TM
Optical Networking
ADVA Optical Networking Corp. Ibasen Bldg. 7F Nihonbashi-kobunacho 4-1 Chuo-ku, Tokyo 103-0024 Japan ADVA Optical Networking S.A.R.L. Btiment Mont Royal Z.A de Courtaboeuf 21 Avenue du Quebec 91140 Villebon Sur Yvette France ADVA Optical Networking Lerchenfelder Grtel 43 Top 2/2 1160 Vienna Austria
Tel: +81 (0)3 6667 5830 Fax: +81 (0)3 6667 5839 info-asiapacific@advaoptical.com
Tel: +33 (0)1 60 13 59 53 Fax: +33 (0)1 60 13 12 10 info@advaoptical.com
Tel: +43 1 4090 801 info@advaoptical.com
ix
Preliminaries
THIS PAGE INTENTIONALLY LEFT BLANK
TM
Optical Networking
Contents
Chapter 1 Network Architecture Overview
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Ethernet Market Overview/Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.3 FSP 150 Ethernet Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.4 FSP 150Mx/CX Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.4.1 FSP 150Mx Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.4.1.1 Dedicated Transport Solutions (Dark Fiber between Devices) . . . . . . . . . . . . . . . . . 3 1.4.1.1.1 Point-to-Point Fiber Relief Topology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.4.1.2 Shared Transport Solutions (Active Network between Devices). . . . . . . . . . . . . . . . 4 1.4.1.2.1 Tree and Branch Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4.1.2.2 Ring or Chain Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.4.4 FSP 150CX Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.5 FSP 150 Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.5.1 Ethernet Line (E-Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.5.1.1 Unprotected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.5.1.2 Protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 1.5.2 Ethernet-LAN (E-LAN) Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 1.5.3 Throttled Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 1.5.4 Core Network Feeder for Managed Services (Internet Access) . . . . . . . . . . . . . . . . . . . . . .12 1.6 FSP 150 Network Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.6.1 Traffic Routing and Delivery (FSP 150Mx only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 1.6.2 Traffic Forwarding in a Tree or Point-to-Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 1.6.3 Traffic Forwarding in a Ring/Chain Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 1.6.4 Tag Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 1.6.5 Priority Bit Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 1.6.6 TAG Protocol Identifier Field Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 1.6.7 Protection and Restoration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 1.6.7.1 Redundant Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 1.6.7.2 Recovery from Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 1.6.7.3 Redundancy and Restoration using Tandem Nodes. . . . . . . . . . . . . . . . . . . . . . . .20 1.6.7.4 Network Port Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Chapter 2 Features
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.2 Introducing the FSP 150Mx/CX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.2.1 Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 2.3 Traffic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.3.1 Data Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 2.3.2 Frame Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 2.3.3 Hot Standby Routing Protocol/Virtual Routing Redundancy Protocol Forwarding (HSRP/VRRP)26 2.3.4 Auto-negotiation Advertising . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 2.3.4.1 Auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 2.3.4.2 Link Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 2.3.4.3 Duplex Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 2.4 Traffic Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2.4.1 FSP 150Mx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 2.4.2 FSP 150CX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
2563XC07_Contents.fm - 30. October 2007
xi
Contents
2.5 Traffic Service Protection (FSP 150Mx only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 Network Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.2 Network Port Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.3 Tandem Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Egress Multicast Support (FSP 150MG only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.1 Egress Multicast Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.1.1 Egress Multicast Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.1.2 Multicast Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.1.3 Ingress IGMP Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.2 Egress Multicast Configuration and Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27 27 27 28 29 29 29 30 30 30
Chapter 3 Components
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 FSP 150Mx/CX Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 FSP 150Mx Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.1 FSP 150MO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.2 FSP 150ME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1.3 FSP 150MG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 FSP 150CX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Component Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2 Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2.1 Fan Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3 Power Supply Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3.1 PSU Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4 Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.1 Network Element Management Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.2 Management Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.2.1 Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.2.2 MG DCN Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4.3 Management Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5 Access and Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.1 Connector Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.2 Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.1.1 Electrical Access Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.1.2 Electrical Network Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.1.3 Optical Access Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5.1.4 Optical Network Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.6 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.6.1 Optical Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.6.2 Electrical Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.7 SFP Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 33 33 33 34 34 34 35 35 35 36 36 37 37 37 38 38 38 38 39 39 39 39 39 40 40 40 40 40 41
Chapter 4 Management Overview

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 EFM OAM Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1 EFM in Dedicated Transport Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1.1 Local Ended Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1.2 Dual Ended Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 EFM in Shared Transport Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.1 Integration with Existing Network Management Systems . . . . . . . . . . . . . . . . . .
43 43 44 44 44 45 45 45
xii
TM
Optical Networking
4.3.3 IEEE 802.3ah EFM OAM Vendor Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 4.4 SNMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 4.4.1 Integration with SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 4.4.2 The FSP 150 MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 4.4.2.1 Supported Variables (RFC Conformance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 4.4.2.2 FSP 150 Enterprise MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 4.5 Network Element Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4.6 Management Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4.6.1 IP Inband Management (FSP 150Mx Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 4.6.2 Configuration Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 4.6.3 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 4.6.4 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 4.6.5 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 4.6.5.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 4.6.5.2 Audit Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Chapter 5 Management Interfaces

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.2 NEMI Access - User Account and Default Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.3 Craft/Web Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.3.1 Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 5.3.1.1 Craft Interface Access Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 5.3.1.2 Accessing the Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 5.3.1.3 Exiting the Craft Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 5.3.1.4 Automatic Logout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 5.3.1.5 Craft Interface User Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 5.3.2 Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 5.3.2.1 Web Interface Access Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 5.3.2.2 Accessing the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 5.3.2.3 Exiting the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 5.3.2.4 Automatic Logout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 5.3.2.5 Web Interface User Interaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 5.3.3 Craft/Web Interface Menu Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 5.4 Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 5.4.1 Command Line Interface Access Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 5.4.2 Accessing the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 5.4.3 Exiting the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 5.4.4 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 5.4.4.1 Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 5.4.4.2 Navigating Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 5.4.5 Node Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 5.4.5.1 FSP 150Mx/CX Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 5.4.5.2 FSP 150CP Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 5.4.5.3 Node Topology Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 5.4.6 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 5.4.6.1 Command Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 5.4.6.2 Command Abbreviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 5.4.6.3 Context Sensitive Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 5.4.7 Copyright Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 5.4.8 Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 5.4.9 Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 5.4.9.1 mgr (Manager Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 5.4.9.1.1 mgr configure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
xiii
Contents
5.4.9.1.2 mgr show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.1.3 mgr upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.1.4 mgr reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.1.5 mgr network-ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.1.6 mgr aux-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.1.7 mgr dcn-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.1.8 mgr cfg-mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.2 ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3 node (Node Mode). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.1 Connecting to a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.2 node port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.3 node unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.4 node chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.5 node upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.6 node show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.7 node cfg-mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.3.8 Connecting to a FSP 150CP Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.4 file-mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9.5 craft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
74 74 74 75 75 75 76 76 76 76 76 78 81 81 82 82 82 84 84
Chapter 6 Configuration
6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 6.2 Initial Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 6.3 Configuring IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 6.3.1 Configuring Ethernet IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 6.3.2 Configuring a Connection to a Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.3.3 Configuring Inband IP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 6.3.4 Configuring the Host Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 6.3.5 Configuring the Domain Name System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 6.3.5.1 Domain Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 6.3.5.2 DNS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 6.4 Configuring Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 6.5 Configuring Secure Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 6.5.1 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 6.5.1.1 Enabling/Disabling SNMP Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 6.5.1.2 Configuring a Contact and Location Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 6.5.1.3 Configuring SNMP Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 6.5.1.4 Configuring Trap Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 6.5.2 Configuring Secure External Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 6.5.2.1 Enabling/Disabling External Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 6.5.2.2 Configuring RADIUS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 6.5.2.3 Enabling/Disabling Security Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 6.5.2.4 Configuring Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 6.5.2.5 Attaching an Access Control List to an External Access Service . . . . . . . . . . . . . . . 98 6.5.3 Configuring Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 6.5.3.1 Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 6.5.3.2 Changing Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 6.5.3.3 Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 6.5.3.4 Locking/Unlocking a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 6.6 Configuring Active/Passive NEMI Mode (Mx only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 6.7 Configuring Chassis User Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
xiv
TM
Optical Networking
6.8 Configuring Traffic Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.8.1 Enabling/Disabling Ring/Chain Support (Mx only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.8.2 Configuring a Ring ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.8.3 Configuring Arrival/Departure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 6.8.4 Enabling/Disabling Jumbo Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 6.8.5 Configuring Port Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 6.8.5.1 Enabling/Disabling a Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 6.8.5.2 Enabling/Disabling Full Duplex (AUX and DCN ports only) . . . . . . . . . . . . . . . . . . 107 6.8.5.3 Enabling/Disabling Auto Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 6.8.5.4 Configuring the Port Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 6.8.5.5 Configuring Traffic Forwarding on an Access Port . . . . . . . . . . . . . . . . . . . . . . . . 109 6.8.5.6 Configuring Tag Mode on an Access Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 6.8.5.7 Configuring the Port User String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 6.8.6 Configuring Link Loss Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 6.8.6.1 Enabling/Disabling Link Loss Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 6.8.6.2 Enabling/Disabling Link Loss Forwarding on a Specific Port . . . . . . . . . . . . . . . . . 111 6.8.7 Configuring PID Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6.8.7.1 Enabling/Disabling PID Translation on a Network Port . . . . . . . . . . . . . . . . . . . . 112 6.8.7.2 Configuring PID Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6.8.7.3 Configuring PID Translation Entry View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 6.9 Configuring OAM and EFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 6.9.1 Configuring Unit OAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 6.9.2 Enabling/Disabling Access or Network Port OAM and EFM Information . . . . . . . . . . . . . . . 114 6.10 Configuring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 6.10.1 Configuring Tandem Mode (Mx only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 6.10.2 Configuring Protection on the Network Port (Mx only) . . . . . . . . . . . . . . . . . . . . . . . . 115 6.10.3 Enabling/Disabling HSRP/VRRP Forwarding (Mx only) . . . . . . . . . . . . . . . . . . . . . . . . . 117 6.11 Configuring Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 6.11.1 Enabling/Disabling Traffic Management Classification. . . . . . . . . . . . . . . . . . . . . . . . . 117 6.11.2 Configuring Network Port Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 6.11.3 Configuring Access Port Regulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 6.11.4 Configuring Access Port Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 6.12 Configuring Egress Multicast (FSP 150MG only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 6.12.1 Adding/Removing an Access Port to/from the Egress Multicast . . . . . . . . . . . . . . . . . . 120 6.12.2 Configuring the Multicast IGMP VLAN Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 6.12.3 Configuring Egress Multicast Regulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 6.12.4 Configuring Multicast Protection on the Network Port. . . . . . . . . . . . . . . . . . . . . . . . . 122 6.13 Configuring Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.13.1 Enabling/Disabling Alarm Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.13.1.1 Port Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.13.1.2 PSU and Fan Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.13.1.3 Individual Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.13.2 Configuring Alarm Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.13.3 Configuring Alarm Types and Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 6.13.3.1 Alarm Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 6.13.3.2 Severity Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 6.13.3.3 Modifying Alarm Types and Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 6.14 Configuring Audit Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 6.14.1 Enabling/Disabling Audit Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 6.14.2 Configuring Audit Log Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 6.14.2.1 Externally Stored Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 6.14.2.2 Locally Stored Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 6.15 Backing Up Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
xv
Contents
Chapter 7 Test Procedures

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.2 Connection Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.2.1 To Test the Ethernet Connection from a NMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 7.2.2 To Test the Ethernet Connection from the NEMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 7.3 Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.3.1 Performing loopbacks via the FSP 150Mx/CX NEMI Craft Interface . . . . . . . . . . . . . . . . . .136 7.3.1.1 Port Loopbacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 7.3.1.2 Remote Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 7.4 Onboard Traffic Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 7.4.1 Traffic Generators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 7.4.2 Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 7.4.3 Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 7.4.4 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 7.4.4.1 Arrival Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 7.4.4.2 Departure Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 7.4.5 Frame Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 7.4.6 Loopback Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 7.4.7 Tag Protocol ID (TPID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 7.4.8 VLAN IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 7.4.9 MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 7.4.10 Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 7.4.10.1 Point-to-Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 7.4.10.2 Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142 7.4.10.3 Chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 7.4.11 Running the Onboard Traffic Tests via the Craft Interface . . . . . . . . . . . . . . . . . . . . . .144 7.4.11.1 Configuring the Generator and Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 7.4.11.2 Viewing Generator Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 7.4.11.3 Clearing Current Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 7.4.11.4 Enabling Loopback Functionality at the End of the Test Path . . . . . . . . . . . . . .149 7.4.11.5 Starting the Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 7.4.11.6 Stopping the Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 7.4.11.7 Disabling Loopback Functionality at the End of the Test Path . . . . . . . . . . . . .150 7.4.11.8 Viewing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 7.4.11.9 Auto Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Chapter 8 Performance Management

8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 8.2 Viewing Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 8.2.1 Viewing Unit Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153 8.2.2 Viewing Port Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 8.2.3 Clearing Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 8.3 Viewing Network Port OAM Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 8.3.1 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157 8.3 Viewing PID Translation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Chapter 9 Maintenance
9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 9.2 Technical Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 9.3 Viewing Inventories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 9.3.1 Viewing the NEMI Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 9.3.2 Viewing the Chassis Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
xvi
TM
Optical Networking
9.3.3 Viewing a Port Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 9.4 Rebooting and Resetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 9.4.1 Rebooting the NEMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 9.4.2 Resetting the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 9.4.2.1 Reset via the NEMI Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 9.4.2.2 System Power Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 9.4.3 Enabling/Disabling Traffic during NEMI Reboot/Chassis Reset . . . . . . . . . . . . . . . . . . . . 166 9.5 Upgrading Firmware/Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 9.5.1 Node Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 9.5.2 NEMI Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 9.6 Backing Up and Restoring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 9.6.1 Configuration File Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 9.6.2 Backing Up and Restoring Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 9.6.2.1 Saving the Running Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 9.6.2.2 Backing Up the Active Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 9.6.2.3 Transferring Backup File from NEMI to PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 9.6.2.4 Transferring Backup File from PC to NEMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 9.6.2.5 Cloning Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 9.6.2.6 Restoring Backup File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 9.6.2.7 Deleting Files on the NEMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 9.6.3 Restoring Factory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 9.7 Hardware Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 9.7.1 Maintaining the FSP 150Mx/CX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 9.7.1.1 FSP 150Mx/CX Handling Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 9.7.1.2 Inspecting the FSP 150Mx/CX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 9.7.1.3 Cleaning the FSP 150Mx/CX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 9.7.2 Maintaining Fiber-Optic Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 9.7.2.1 SFP Transceiver Handling Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 9.7.2.2 Fiber-Optic Cable Handling Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 9.7.2.3 Inspecting Fiber-Optic Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 9.7.2.4 Cleaning Fiber-Optic Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 9.7.3 Equipment Disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Chapter 10 Fault Management

10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 10.2 Built in Tests (Except FSP 150MG). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 10.3 Fault Finding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 10.3.1 Evaluating Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 10.3.1.1 Viewing Current Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 10.3.1.2 Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 10.3.2 Evaluating the Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 10.3.2.1 Viewing the Logfile directly on Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 10.3.2.2 Viewing and Downloading the CSV File in the Web Interface . . . . . . . . . . . . . 195 10.3.2.2.1 Viewing the CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 10.3.2.2.2 Downloading the CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 10.3.3 Evaluating Component Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 10.3.3.1 Viewing Chassis Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 10.3.3.2 Viewing Unit Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 10.3.3.3 Viewing Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 10.3.4 Evaluating Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 10.4 Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 10.4.1 Resolving Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 10.4.1.1 Resolving Connection Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
xvii
Contents
10.4.1.2 Rebooting Management Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 10.4.1.3 Updating Management Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 10.4.2 Resolving Hardware Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 10.4.2.1 Resolving PSU Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 10.4.2.2 Resolving Fan Failure Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 10.4.2.3 Resolving Access Interface Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 10.4.2.4 Resolving Network Interface Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 10.4.2.5 Performing Onboard Traffic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 10.4.2.6 Performing Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 10.4.2.7 Performing Optical Power Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . .204 10.4.3 Resolving Incorrect Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 10.4.4 Hardware Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 10.4.5 Further Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 10.4.6 Replacing Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 10.4.6.1 Preparing for Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 10.4.6.2 Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 10.4.6.3 NEMI Battery Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 10.4.6.4 Fuse Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 10.4.6.5 Chassis Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 10.4.6.6 SFP Transceiver Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208 10.4.6.7 Equipment Return and Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Chapter 11 System Data

11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 11.2 FSP 150Mx/CX System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 11.2.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211 11.2.2 Base Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211 11.2.3 Equipment Accessory Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Figures
1-1: Point-to-Point Topology - Fiber Relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1-2: Unprotected Tree and Branch Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1-3: Protected Tree and Branch Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1-4: Closed Ring/Chain Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1-5: Hub and Spoke Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1-6: Unprotected E-line based on a FSP 150 Family Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1-7: Protected E-line Service based on a FSP 150 Family Network . . . . . . . . . . . . . . . . . . . . . . . . . 10 1-8: E-LAN Service based on a FSP 150 Family Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1-9: FSP 150 Core Feeder Service Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1-10: Identification of IEEE 802Q VLAN Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1-11: Simple Tree Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 1-12: FSP 150Mx Tree and Branch Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1-13: FSP 150Mx Tandem Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2-1: FSP 150Mx Tandem Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 3-1: FSP 150MO Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2: FSP 150ME Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3: FSP 150MG Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4: FSP 150CX Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 34 34 34
xviii
TM
Optical Networking
3-5: Chassis Ventilation Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 3-6: Typical SFP Transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 4-1: FSP 150Mx/CX Management; Local Ended Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 4-2: FSP 150Mx/CX Management; Dual Ended Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 4-3: SNMP/EFM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 4-4: FSP 150 Enterprise MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 5-1: Craft/Web Interface Menu Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 5-2: Command Line Interface Mode Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 5-3: CLI Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 7-1: Remote Loopback on the Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Tables
3-1: Chassis Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 3-2: FSP 150Mx/CX Alarm Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 3-3: Electrical Access Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 3-4: Electrical Network Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 3-5: Optical Access Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 3-6: Optical Network Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 5-1: Keyboard Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 5-2: Keyboard Navigation for Status Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 8-1: Unit Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 8-2: Port Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 9-1: Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 10-1: Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 10-2: Management Interface Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 10-3: Resolving PSU Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 10-4: Resolving Fan Failure Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 10-5: Resolving Access Interface Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 10-6: Resolving Network Interface Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
xix
Contents
xx
TM
Optical Networking
Chapter
1.1 Introduction
1
the Ethernet service types. an introduction to the use of the FSP 150 family to provide carrier class aggregation and demarcation in an Ethernet access network from the CP to a metro core. an introduction to the network topologies the FSP 150 family can be used in and an illustration of some of the deployment scenarios that it can be used for. an introduction to the services that can overlay the physical topologies outlined in Section 1.3 FSP 150 Mx/CX Topologies. the mechanisms employed to route traffic and to protect and restore traffic. in a FSP 150 network.
FSP 150 Network Architecture Overview

This chapter provides an introduction to the Fiber Service Platform 150 (FSP 150) family and the network architectures that can be achieved to deliver Ethernet services from backbone Switches and/or Routers to Customer Premises (CPs). The following information is provided:
1.2
Ethernet Market Overview/Requirements

The metro access portion of a carrier network infrastructure currently reduces the delivery of high capacity bandwidth to business customers. Although metro core technology has been developed extensively, access networks to this core are based on low speed legacy solutions for last mile connectivity. This means high operational overheads in the access network. In addition, as enterprise networks are usually based on Ethernet backbones, an additional cost is associated with adapting an incompatible service to Ethernet, resulting in a costly service presentation at the CPs. In an attempt to consolidate the access network, many carriers are now focusing on native Ethernet as the primary solution for the access network infrastructure to provide shared Ethernet services. The carrier can then use the shared infrastructure to deliver a variety of Ethernet service types, such as: Ethernet-Line (E-Line) Ethernet-Local Area Network (E-LAN) Throttled Ethernet (sub full rate Gigabit Ethernet (GbE) or Fast Ethernet) Core Network Feeder for Managed Access.
2563XD07_Ch1_NAO.fm - 16. October 2007
New technologies have subsequently emerged providing cheaper access links based on intelligent Layer 2 switching. These Layer 2 switches now solve many of the problems associated with Ethernet networks and can monitor Quality of Service using Technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.1Q/p (Virtual LAN (VLAN) tagging). Under these conditions the shared infrastructure becomes a much more balanced transport for Ethernet service delivery.
1.3
FSP 150 Ethernet Solutions

The current generation of Layer 2 switches are based on existing switch technology, which is flexible when used in a private enterprise, but not optimized for deployment in a carrier access network. The FSP 150, therefore, provides a family of low cost Ethernet access aggregation and demarcation units, which: are targeted at the fiber based access Ethernet market enables carrier class aggregation and demarcation in the access network and: eliminates enterprise switches and media converters simplifies commissioning and service deployment enables mass deployment reduces operation expenditure in the access network.
reduces power and space requirements in the Central Office (CO)/Point of Presence (POP), thereby reducing equipment expenditure.
Each unit within the FSP 150 family has been specifically designed to fulfill a function within a carrier class Ethernet access network and the units are: FSP 150 Customer Premise (FSP 150CP), which is a CP unit to perform the role of a customer demarcation device within an Ethernet access network. Its function is to provide a clear delineation between the edge of the customer network and the start of the provider network. FSP 150 Multiplexer (FSP 150Mx), which is an aggregation device, essentially a packet multiplexer, capable of aggregating multiple Ethernet streams into a single transport link. FSP 150 Hub Node (FSP 150CX), which is a multi port media converter that can be used as a secure Ethernet transport device for multi-service termination requirements.
The key subject of this User Manual is that of the FSP 150Mx/CX. The FSP 150CP is discussed, only, where necessary to illustrate the use of the FSP 150Mx/CX and its interconnection with the FSP 150CP to create an Ethernet access infrastructure. If further details are required about the FSP 150CP, refer to the FSP 150CP User Guide.
FSP 150MxCX User Guide
When used together the FSP 150 family can be used to build out a carrier class shared Ethernet access infrastructure and a number of interconnections and deployment scenarios are possible as discussed in Section 1.4 FSP 150 Mx/CX Topologies and Section 1.5 FSP 150 Service Types.
TM
Optical Networking
1.4
1.4.1
FSP 150 Mx/CX Topologies

FSP 150 Mx Topologies
The FSP 150 family is extremely versatile and can be used in many deployment scenarios to deliver Ethernet services to the CP. Network solutions can be as simple as point-to-point over dedicated fiber or can be complex access feeder networks connected to Ethernet/Synchronous Digital Hierarchy (SDH)/Dense Wavelength Division Multiplexer (DWDM) core infrastructures. It is also possible to build the access infrastructure using the FSP 150Mx in tree, ring or chain topologies. The basic topologies supported by the FSP 150 family can be broadly grouped into 2 categories, as follows: Dedicated Transport on Dark Fiber. This category defines solutions where there is only a passive fiber infrastructure between interconnected end devices. For further details see Section 1.4.1.1 Dedicated Transport Solutions (Dark Fiber between Devices). Shared Transport through an Active Transport Network. This category defines solutions which traverse an active (metro and/or core) network where some form of traffic segregation is applied by an independent control plane mechanism. For further details see Section 1.4.1.2 Shared Transport Solutions (Active Network between Devices).
1.4.1.1
Dedicated Transport Solutions (Dark Fiber between Devices)

Dedicated topologies are classed as such, since the fibre between the end devices is unique to the customer.
1.4.1.1.1 Point-to-Point Fiber Relief Topology

It is possible to deploy a FSP 150Mx in a point-to-point dedicated manner. Up to ten FSP 150CP units can then be linked to each FSP 150Mx. This will allow multiple optical or electrical 10/100/1000Mbit/s services to be transported between two end points. See Figure1-1.
10:1 Client Aggregation
Active Path FSP 150Mx
10:1 Client Aggregation 10:1 Client Aggregation
Optional Protection Path
Figure 1-1: Point-to-Point Topology - Fiber Relief
It is also possible to use FSP 150Mx and FSP 150CP units to form a tree and branch topology (as described in Section 1.4.1.2.1 Tree and Branch Topology) which can then be attached to a head node FSP 150Mx unit at either end of the point to point configuration. Each individual client traffic stream from a FSP 150Mx/CP is transported securely across a Gigabit aggregate and presented at the remote end on the equivalent port. This topology can be used to link two Multi Tenant Units (i.e. locations with multiple customers in a single office building) together. There is inherent security between traffic streams due to unique hardware based VLAN enforcement. (See Section 1.6.1 Traffic Routing and Delivery (FSP 150Mx only) for details on VLAN tagging.) The provider can guarantee that the customer traffic is private between two locations, even though it is carried on a common aggregate channel. The service can be protected using a standby protection path by routing a second redundant Network path between each FSP 150Mx unit. For further details on the FSP 150CP, refer to the FSP 150CP User Guide.
1.4.1.2
Shared Transport Solutions (Active Network between Devices)

A shared transport solution can be implemented by using a core active network. As a physical path is established between the provider and the customer locations via a core network, the provider can offer more varied services, giving the customer access to a richer variety of service types, not available on a dedicated infrastructure. See Section 1.5 FSP 150 Service Types for further details. The core active network can be: a layer 2, switched network a Multi Protocol Label Switching (MPLS), switched network a layer 3, routed network.
1.4.1.2.1 Tree and Branch Topology Unprotected

Deployed in an access feeder to an aggregated network, the FSP 150CP is located at the CPs and provides the demarcation point between the customer network and the service providers network. Aggregation points provided by the FSP 150Mx are used to aggregate both traffic and management data onto physical router ports. FSP 150Mx aggregation devices are capable of aggregating multiple Ethernet streams into a single transport link. When used with the FSP 150CP, a number of interconnections are possible. The Access Interface ports of the FSP 150Mx can be interconnected with the Network Interface port of a downstream FSP 150Mx or FSP 150CP. This allows multiple levels of aggregation to be built into a FSP 150 access network.
TM
Optical Networking
The FSP 150 family can be used to build a tree and branch access topology (see Figure 1-2), where up to three levels of FSP 150Mx devices are supported, allowing for an aggregation ratio of 1000:1 and distances of up to 500km.
Aggregation Tier 1 (10:1 Ratio)
FSP 150Mx Root Node
FSP 150Mx
x 10
FSP 150Mx
Demarcation
x 10
x 10
FSP 150CP
Figure 1-2: Unprotected Tree and Branch Topology

The FSP 150 uses VLAN Tagging to accurately route traffic from FSP 150CP to FSP 150Mx/CX User Ports (e.g. Port 1 is VLAN 1), see Section 1.6.1 Traffic Routing and Delivery (FSP 150Mx only). The FSP 150Mx root node shown at the top of the tree is responsible for the hand-off to the metro edge switch/router and will typically be co-located with the switch or router in the providers CO.
Protected
A protected port may be used on each Network uplink to act as a standby path up the tree. Traffic is automatically switched to the protected path in the event of a failure in the primary route. The general concept is to ensure that the customer has diverse paths available through the access network and that where possible, there is no single point of failure. Figure 1-3 shows how a service can be protected within a tree and branch structure. Each FSP 150CP is shown dual homed to different parts of the access tree to provide network resilience.
Metro Core Metro Core
Metro Edge Switch/Router
Access Aggregation Layer Tandem Node Link
FSP 150Mx
Protected Uplink
Access Demarcation Layer
FSP 150CP
Figure 1-3: Protected Tree and Branch Topology The tandem node is the key element in providing protection within a FSP 150 infrastructure. This node duplicates customer links and provides for complete equipment and path failure. The tandem nodes do not have to be physically co-located and can exist at any location in the tree architecture. As the tandem node behaves logically in an identical way to a standard FSP 150Mx root node, all management functions are consistent with those described for the unprotected tree and branch topology. For more details on protection and tandem nodes, see Section 1.6.7 Protection and Restoration.
TM
Optical Networking
1.4.1.2.2 Ring or Chain Topologies

It is possible to connect the Network Interface ports of a FSP 150Mx directly to the Network Interface port of an adjoining unit to form a chain of devices. The underlying forwarding technology in the FSP 150Mx manages the addressing of the units and supports up to 12 devices connected in a single physical chain. By ensuring that the chain is backhauled to the originating CO, it is also possible to terminate the chain and effectively close the topology into a ring (see Figure 1-4).
Metro Core Metro Core
Metro Edge Switch/Router
Access Aggregation Layer FSP 150Mx Access Ring Tandem Node Link
Access Demarcation Layer
FSP 150CP
Figure 1-4: Closed Ring/Chain Topology The ring is protected by means of the tandem root node providing the Network uplinks. In the event of a ring failure, the tandem node ensures that traffic received on the secondary path is forwarded unaffected to the metro edge device. For more details on protection and tandem nodes, see Section 1.6.7 Protection and Restoration.
1.4.2
FSP 150 CX Topology

The typical deployment of the FSP 150CX is as a multi port media converter located at a hub site. The Network Ports of the FSP 150CX are used to connect to remote customer sites (spoke sites) and the Access Ports are connected to a switch unit at the Hub site. The switch provides interconnection between the remote sites. When the FSP 150CX is deployed in a Hub and Spoke configuration, both ends of the link are located at the CPs and provide the demarcation point between the customer network and the service providers network. See Figure 1-2. In this topology FSP 150CP units, are located at remote CP feeding a single FSP CX located at the central Hub.
Metro Edge Switch/Router x10
FSP 150CX
FSP 150CP
Figure 1-5: Hub and Spoke Topology
1.5
FSP 150 Service Types

Section 1.4 FSP 150 Mx/CX Topologies details the physical topologies that can be built using the FSP 150 family. This section discusses the services that can overlay them. It is assumed that a service will be transported across a metro core network and terminated within a separate access infrastructure at a remote location.
TM
Optical Networking
1.5.1
Ethernet Line (E-Line)

The FSP 150 supports two E-line services, unprotected and protected, as described below.
1.5.1.1
Unprotected
An unprotected E-line service provides a transparent fixed bandwidth pseudo wire between customer locations. A bandwidth should be guaranteed or a set of service constraints may be enforced by traffic management within core and access network devices (see Figure 1-6).
Metro Core
L2/MPLS/IP Mapping Across Metro Core
POP#1
POP#2
FSP 150Mx
Access Infrastructure
FSP 150Mx
FSP 150CP
FSP 150CP
Customer A Logical Path Customer B Logical Path
Figure 1-6: Unprotected E-line based on a FSP 150 Family Network In Figure 1-6, two customers sharing the same access infrastructure are allocated virtual lines. The logical path is secured by the VLAN forwarding function in the FSP 150Mx and by the traffic segregation function in the metro device.
The E-line service functions at layer 2, and therefore, the provider network should agree to transport all customer traffic transparently between end locations. All frames must be delivered unaltered at the destination.
1.5.1.2
Protected
Adding protection to an E-line service is achieved by provisioning the second Network Interface port on the FSP 150CP. An FSP 150Mx Tandem node must also be present within the access tree and the working and protection paths from the customer must terminate on the appropriate ports of the tandem node. See Figure 1-7.
Metro Core
L2/MPLS/IP Mapping Across Metro Core
POP#1 Primary Path Backup Path
POP#2 Primary Path
FSP 150Mx Tandem Node
FSP 150CP
FSP 150CP
Figure 1-7: Protected E-line Service based on a FSP 150 Family Network As with the unprotected service, a path across the metro core must also be provisioned. Given that the core will typically have multiple physical paths available and will utilize a technology such as MPLS to route around failed nodes, it is not necessary to provision two independent paths across the core. Instead both the primary and backup paths from the access network can be mapped to a single core transport resource and the inherent fault tolerance of the core can be relied upon to bypass failed links. If required, two paths can be provisioned independently. While a layer 2 E-line service type is described above, the service topology also holds true for layer 3 E-line service type. The core network mapping is provisioned in the same way as described above. The FSP 150 family is based on layer 2 capabilities and does not perform any layer 3 routing function. It is assumed, therefore, that the layer 3 E-line is provisioned in the metro edge router and the access network is layer 2 only.
10
TM
Optical Networking
1.5.2
Ethernet-LAN (E-LAN) Service

The E-LAN service is a special case of the E-line service (see Section 1.5.1 Ethernet Line (E-Line)). However, the metro edge device will not provision a single transport link access the core. Instead, it maps the appropriate access trunks into a transport VLAN with the core network. See Figure 1-8. The E-LAN service can be protected in the same manner as described for the Eline service (see Section 1.5.1 Ethernet Line (E-Line). Once again, while an E-line or E-LAN service is traditionally based on MPLS technology in the core, it is also possible to build this service using a layer 3 Internet Protocol (IP) transport network in the core. The technology at the metro edge only needs to support a mapping function between VLAN on the access infrastructure and the appropriate IP network in the core.
FSP 150CP FSP 150CP
FSP 150Mx FSP 150Mx
Access Infrastructure POP#3 Metro Core or Provider Backbone Backbon POP#1 POP#4 VLAN/MPLS Mapping In Metro Edge Device POP#2
Access Infrastructure
FSP 150Mx FSP 150Mx
FSP 150CP
FSP 150CP
Figure 1-8: E- LAN Service based on a FSP 150 Family Network

1.5.3
Throttled Ethernet
Where business conditions do not require full use of GbE, rates can be throttled to lower rates.
11
1.5.4
Core Network Feeder for Managed Services (Internet Access)

Core network feeder applications assume that the destination resource is owned or managed within the provider network core. Figure 1-9 illustrates an Internet Access Service, however, this architecture could be used to provide managed data centre or application services.
The Internet
Internet Peering Location Provider Backbone
POP#1
POP#2
FSP 150Mx Access Infrastructure
FSP 150Mx
FSP 150CP Customer A Logical Path Customer B Logical Path Customer C Logical Path Customer D Logical Path
FSP 150CP
Figure 1-9: FSP 150 Core Feeder Service Application The access infrastructure is deployed in the same way as for the other service applications described in this section. The service mapping at the metro edge network determines the destination resource and therefore permits the provider to reduce the commissioning required and the operational cost of service.
12
TM
Optical Networking
1.6
1.6.1
FSP 150 Network Operation

Traffic Routing and Delivery (FSP 150Mx only)
The FSP 150Mx does not require Medium Access Control (MAC) address learning in order to forward packets. In the upstream direction, the FSP 150Mx always forwards traffic directly from the Access port to the Network port (and a VLAN tag is attached to the incoming packet in order to identify the ingress access port). This tag is modified as the packet traverses the access network to ensure that a complete source path exists once the packet exits the access network. In the downstream direction, the FSP 150Mx forwards packets based on information contained within the VLAN tag of the incoming packet. The downstream VLAN tag is generated at the top of the access tree and contains a source route path based on the port identifiers of the downstream FSP 150Mx devices. This VLAN tag is removed at the closest FSP 150Mx to the customer equipment. All tag processing is performed automatically in the FSP 150Mx hardware and requires no provisioning by the service provider. The traffic routing within a FSP 150 access network is achieved by a unique utilization of the IEEE 802.1q VLAN tag within the Ethernet frame. Traffic arriving at a FSP 150Mx root node from a FSP 150CP Network Interface port is tagged with an 802.1 VLAN ID (VID).
DA
SA
VLAN
TYPE
PAYLOAD
FCS
TPID 0x8100
P (3 Bits)
C Bit
VID (12 Bits)
T3
T2
T1
Figure 1-10: Identification of IEEE 802Q VLAN Tag Figure 1-10 shows the VLAN Tag in an Ethernet frame. The VLAN Tag is 4 bytes long and is further broken down into a number of fields, as follows:
TPID, which is the Frame Identifier. This occupies 2 bytes and is set to 810016 to identify it as an 802.1q frame. Priority (P), which occupies 3 bits. Canonical Bit (C Bit), which occupies one bit and is always set to zero. VID, which occupies the last 12 bits. ADVA Optical Networking split the VID into 3 sets of 4 bits to allow the numbers 0 to 15 (0x000 to 0x00F). These numbers can map directly to the Access Interface ports of the FSP 150Mx, e.g. if traffic arrives on port 1 of the root FSP 150Mx, the Ethernet frame should be tagged on receipt as VID=0x001, if port 10, then VID=0x00A.
13
VIDs 0x000 and 0x00B to 0x00F are reserved for system use and do not correspond to any of the FSP 150Mx ports.
FSP 150MO
FSP 150CP
FSP 150CP
Customer A
Customer B
Figure 1-11: Simple Tree Structure Referring to Figure 1-11, Customer A is connected to FSP 150Mx Port 2 and so is on VLAN 2. The router is configured to deliver traffic addressed to Customer A to VLAN 2 and the FSP 150Mx will tag inbound traffic for VLAN 2. Likewise, Customer B is connected to FSP 150Mx Port 10 and so is on VLAN 10. Alternatively, if a frame progresses through an FSP 150Mx access tree, the VID field is filled according to the port it is received on. E.g. if a customer is connected to port 5 of a tier 2 FSP 150Mx and the tier 2 FSP 150Mx is connected to port 2 of the FSP 150Mx root node, the VID would read 0x025. (1) This tagging exists only in the local FSP 150 domain and a packet, tagged by the network, will be untagged as it leaves the FSP 150 domain to the customer location. Any customer tags will remain intact. (2) The FSP 150Mx does not interfere with any existing customer VLAN tags. Stacked VLAN tags (similar to 802.1Q in 802.1Q (Q in Q) tagging) will be transported, subject to the network being able to transport the larger Maximum Transmission Unit (MTU) size.
1.6.2
Traffic Forwarding in a Tree or Point-to-Point

Logically the 12 bit VID field is split into three independent 4 bit fields (a 4 bit field is also known as a nibble). These fields are used for storing source routing information within the FSP 150Mx access network. This results in up to three levels of aggregation per IEEE802.1Q header.
14
TM
Optical Networking
FSP 150Mx Root Node
FSP 150Mx
x 10
FSP 150Mx
Demarcation FSP 150CP FSP 150CP
Figure 1-12: FSP 150Mx Tree and Branch Architecture Each nibble (4 bit sequence) is used for addressing within one level of an FSP 150Mx tree topology. When addressing in a tree topology, the first non zero nibble (starting with Nibble 3) indicates the Port ID (PID) address for the first unit the packet arrives at. The next nibble, if any, indicates the PID address for the next unit in the hierarchy. When the unit uses tree addressing the address format is as described below.
Address 0x0 0x1 to 0xA oxB to 0xD 0xE 0xF Untagged Description This level not addressed Address for ports 1-10 Reserved Address for AUX port Address for ring topology detection & local OAM Address for OAM in unit
The table below defines rules for valid addressing when the unit is in tree or point-to-point mode.
Nibble Nibble 3 Nibble 2 Nibble 1 Valid Values 0x0 to 0xA, non-zero only if Nibble 2 is non-zero 0x0 to 0xA, non-zero only if Nibble 1 is non-zero ox1 to 0xA, 0XE, 0xF
As the frame progresses upstream through an FSP 150Mx access tree, the VID field is filled in according to the port it was received on. Within an FSP 150Mx access network, the VID field is known as the PID.
FSP 150Mx/CX User Guide 15
This traffic forwarding behavior guarantees that customer traffic is private (even when customers are connected on the same aggregation unit). It also guarantees that a routing loop must use the spanning tree protocol, in order to operate. All tag processing is performed automatically in the FSP 150 Mx hardware and requires no provisioning by the service provider, thus ensuring a low operational overhead. This upstream tagging mechanism creates the unique logical link which allows downstream packets to be directed to a specific physical port despite a point to multipoint access network topology.
1.6.3
Traffic Forwarding in a Ring/Chain Topology

When operating in ring or chain mode, the traffic forwarding in the FSP 150Mx operates in a slightly different way. Standard IEEE802.1Q VLAN tags are used to differentiate the traffic as before. However, the VID portion of the tag is built in a different way in order to reflect the difference in topology. For chain operation, two nibbles of the VLAN tag are used to address one level of the chain. The first nibble is used for node number addressing and the second nibble is used for addressing ports within the node. This leaves one nibble that can be used for addressing in one additional tree level as previously described. When the unit is operating in chain mode addressing is according to the table below.
Address 0x0 0x1 to 0xA 0xB to 0xC 0xD 0xE 0xF Untagged First Nibble (Nibble 3 or 2) This level is not addressed. Chain Node 1 to 10 Chain Node 11 to 12 Reserved Reserved Reserved Reserved Second Nibble (Nibble 2 or 1) This level is not addressed. Port 1 to 10 Reserved Reserved Address for AUX port Address for ring/chain topology and OAM Address for OAM in unit.
The table below defines rules for valid addressing when the unit is in chain mode. Port 0xF is used for internal topology detection.
Nibble Nibble 3 Nibble 2 Nibble 1 Valid Values 0x0 to 0xC, non-zero only if Nibble 2 is non-zero 0x0 to 0xA, 0xB or 0xC only if this field is in chain node number. ox1 to 0xA, 0XE, 0xF
The ring topology is a special case of the chain topology and is obtained by ensuring that the head and the tail of the chain are terminated on a Tandem Node. For Ring operation, all the three nibbles of the VLAN Tag are used for addressing. The Nibble 3 is used to identify which port of the Tandem Node the chain is terminated to; the two remaining nibbles are used for node number addressing and for addressing the port number within a node.
16
TM
Optical Networking
The table below defines rules for valid addressing when the unit is in chain mode. Port 0xF is used for internal topology detection.
Nibble Nibble 3 Nibble 2 Nibble 1 Valid Values 0x0 to 0xA, non-zero only if Nibble 2 is non-zero 0x0 to 0xC (ring node number) ox1 to 0xA, 0XE, 0xF
1.6.4
Tag Translation
This mechanism of static tag generation is extremely beneficial for reduction of OPEX costs (i.e. the units can be deployed in a plug and go manner with no configuration needed), however, in some instances it may be necessary to control the tag value as it is sent into the core of the network. For this reason the FSP 150Mx also supports the ability to perform tag translation. The tag translation technology (also known as PID translation) resides in the FSP 150Mx device (typically at the root of a tree or ring) and simply maps PID values (as generated automatically during transit of the access network) into user defined VID values before forwarding the packet into the provider core network (note that the PID and VID field are exactly the same fields within the tag and therefore this is simply a translation on the VID field). The mechanism works in reverse for packets arriving from the provider core for forwarding via the access network to the customer. The whole VID range supported by the IEEE802.1Q standard (i.e. 4096 values) can be mapped. A single PID to VLAN translator located at the root node can support mapping for a complete access network (up to 1111 nodes). Note that the relationship between PID and VLAN is always 1:1. Thus only a single PID can be mapped into any single VLAN and vice versa. In addition to allowing the PID to VLAN translation to be performed, other fields within the tag can also be mapped or converted using the same process.
1.6.5
Priority Bit Mapping

The priority (P) bits within the Q tag can be controlled either by mapping priority bits from an incoming customer tag into the new provider tag or by imposing priority values as defined by the operator. This allows operators to build differentiated services within the access and core network. While the P bits are part of the 8021.Q tag, they are processed within the FSP 150Mx architecture at an earlier point than the other translation functions. The reason for early processing of the P bits is so that priority of buffering can be maintained before the traffic is processed across the FSP 150Mx transmission buses.
17
1.6.6
TAG Protocol Identifier Field Translation

0x8100 is used as the standard TAG Protocol Identifier (TPID) for IEEE802.1Q VLAN tags. However, some vendors also support the use of the TPID 0x9100. Extreme Networks uses this value to identify frames supporting the Extreme vMAN architecture. The FSP 150Mx PID to VLAN translator can be used to map incoming packets with one TPID to an alternate value. The translation on TPID is performed globally for all packets on the interface and is controlled via the Management Interface. For example if an FSP 150Mx were attached to an Extreme networks core device operating the vMAN architecture, the FSP 150Mx could be used to translate the TPID for all packets received from the core into an industry standard 802.1Q TPID (i.e. for packets received from the core Extreme switch, the TPID would be translated from 0x9100 to 0x8100). The reverse would be true for packets received from the customer destined for the core network. This feature allows multi vendor interoperable access networks to be constructed while still permitting the use of value added proprietary features within the network core. Note that all the conversions described above are only applied to the outer tag generated by the FSP 150Mx or the provider edge switch or router. They do not apply to any customer generated tags. Customer tags are always transported unchanged although information (such as priority bits) can be mapped from the customer tag to the provider outer tag. The FSP 150Mx does not interfere with any existing customer VLAN tags and thus will transport stacked VLAN Tags, subject to the network being able to transport the larger MTU size.
1.6.7
1.6.7.1
Protection and Restoration

Redundant Resources
The basic requirement for any restoration mechanism is the presence of redundant resources. A common model of redundancy is to use one resource as a primary and to protect it by providing a back-up (or stand-by) resource of the same type. In this way, one resource can be used as the back-up for a number of primary resources.
In Access Networks
Within an FSP 150 access infrastructure, the resource types that can be duplicated are:
Links, with duplication links following physically diverse communication paths in order to give a high degree of redundancy. Nodes, where FSP 150Mx units are duplicated to protect against node failures and to provide a mechanism to perform upgrades without disturbing the service delivery. See Section 1.6.7.3 Redundancy and Restoration using Tandem Nodes for further information.
18
TM
Optical Networking
In Core Networks
To protect against failures of the attachment units of the core network, the attachment point (router or switch) needs to be duplicated.If the core network is an IP network, router duplication provides the capability of protecting against router failure as well as the failure of the attachment links to the access network. Router duplication also allows maintenance and upgrades without disturbing the service delivery. Restoration in case of router failures can be provided by: manually switching from the failed router to a backup automatically switching to the backup using: dynamic routing protocols such as BGP/Open Shortest Path First (OSPF) other mechanisms such as Virtual Router Redundancy Protocol (VRRP)/ Hot Standby Router Protocol (HSRP).
If the core network is a pure layer 2 switched Ethernet core, redundant attachment nodes (Ethernet switches) provide the same type of protection as do the redundant routers above. In a layer 2 Ethernet system, the switch over from a failed primary switch to a backup secondary is performed automatically within the core layer 2 network.
1.6.7.2
Recovery from Failure

In order to recover from traffic service failure in a FSP 150 access network, three mechanisms must be in place: Failure detection, which is achieved by monitoring the resources on the network either actively or passively. A FSP 150 unit can recognize when a failure has occurred, for e.g.: on a node, by using a watchdog timer to monitor that the node is alive on a link, by monitoring the number of Cyclic Redundancy Check (CRC) errors that occur.
A Protection Policy, which will provide decisions on what actions should be taken when a particular failure occurs. Restoration, which will implement the decision taken.
Recovery may be initiated by two mechanisms, as follows:

Restoration by manual reconfiguration. When using this method the FSP 150Mx access system detects link and node failures, propagates information about these to a unit with topology knowledge that in turn propagates information about the failure, and possibly also proposed actions, to the Network Management Centre (NMC) where an operator should take some action in order to restore the service. This mechanism is typically slow and does not allow the network to restore service in <50ms (the target restoration time for most carrier networks).
19
Automatic restoration via Tandem Node. See Section 1.6.7.3 Redundancy and Restoration using Tandem Nodes.
1.6.7.3
Redundancy and Restoration using Tandem Nodes

The Tandem node provides a high degree of redundancy. The network ports are duplicated (as is the case in any FSP 150Mx unit), the node itself is duplicated, the access ports are duplicated, and switchover between nodes is automated. A Tandem node mechanism can be used in Tree and Branch Topologies, as well as Ring or Chain topologies. This is were two FSP 150Mx units may be connected in Tandem (as shown in Figure 1-13) up to 100km apart.
Backbone Provider Backbone
Provider
N1
N2
N2
N1
A1
A2
A3
B1 B2
B3
Figure 1-13: FSP 150Mx Tandem Nodes When two FSP 150Mx units are connected in Tandem the second network interface ports of each unit (N2 in Figure 1-13) are connected together. Access link protection is then applied by routing redundant fibers between the two units. The access interface ports are grouped in pairs across both nodes, such that access interface ports belong to the same group (e.g. A1 and B1 in Figure 1-13 belong to Group 1). As the index of the group is the same as the ports, a VLAN tag forwarding mechanism is preserved.
A protected access network is constructed by connecting units with dual network ports to the Tandem nodes such that both network ports of the units are connected to the two ports of the same port group of the Tandem node. Any system can be connected to the access side of a Tandem node and be protected as long as it accepts data from both ports and transmits all data to both ports.
20
TM
Optical Networking
A FSP 150MX Access Network built with Tandem Nodes will provide protection against the following type of failure: Failure of links internal to the Access Network. See the headings Internal Link Failures and Tandem Link Failures below. Failure of Tandem Node units. See the heading Node Failures below. The Tandem Node does not provide protection against failures on links that are used to connect the Access Network to the Core Network and it does not provide protection against router failures. However, the Tandem Node will work with other redundancy mechanisms, such as VRRP, HSRP and OSPF, to provide protection against these types of failures. See the headings Uplink Failures and Router Failure below.
1.6.7.4
Network Port Protection

To provide protection also against failures of the network link a network port protection mechanism has been implemented. Four different versions of network port protection can be configured on a FSP150Mx unit: Layer 3 protection. This mode should be used when connecting the FSP150Mx to a layer 3 (IP) metro core. In this mode the unit will accept traffic from both network ports and transmit all traffic received via the access ports via both network ports. Layer 2 protection. This mode should be used when connecting the FSP150Mx to a layer 2 (Ethernet) metro core. In this mode one of the network ports will be selected as active and the other one will be passive. The unit will receive and transmit data via the active port only. If the active port fails the unit will automatically switch the formerly passive network ports to active state. Point-to-point protection. This mode should be used when connecting two FSP150Mx units in a point-to-point configuration. In this mode the unit will transmit all data via both of the network ports and will select one of the network ports to receive from (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state. Link aggregation protection. In this mode the unit will receive data via both of the network ports and will select one of the network ports to transmit via (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state.
Network port protection can be configured both on a stand alone FSP 150Mx unit and on a Tandem Node. When configured on a Tandem Node the network port protection relates to the network ports of the Tandem Node.
21
22
TM
Optical Networking
Chapter
Features
2.1 Introduction
This chapter describes:
2
an introduction to the Fiber Service Platform 150 Multiplexer/Hub Node (FSP 150Mx/CX) the traffic services provided by the FSP 150Mx/CX traffic forwarding traffic protection in the FSP 150Mx/CX Operation, Administration and Maintenance (OAM) of the FSP 150Mx/CX.
2.2
Introducing the FSP 150Mx/CX

The FSP 150Mx, as part of the FSP 150 family, is primarily an aggregation device, essentially a packet multiplexer, capable of aggregating multiple Ethernet streams into a single transport link. When used together with FSP 150 Customer Premise (FSP 150CP), FSP 150Mx units can be used to build a carrier class shared Ethernet access infrastructure, were Ethernet services are delivered from backbone Switches and Routers to Customer Premises. Two types of FSP 150Mx aggregation unit are available, with: Optical Access Interfaces, the FSP 150M Optical (FSP 150MO) Electrical Access Interface, the FSP 150M Electrical (FSP 150ME). The FSP 150CX, as part of the FSP 150 family, is a multi port media converter that can be used as a secure Ethernet transport device for multi-service termination requirements. The operation (and management protocol) of the FSP 150Mx/CX is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.3ah Ethernet First Mile (EFM) standard and will inter-operate with other 802.3ah equipment directly.
2563XE07_Ch2_Features.fm - 16 October 2007
The FSP 150Mx/CX is supplied with an integrated Network Element Management Interface (NEMI). The NEMI allows Internet Protocol (IP)/Simple Network Management Protocol (SNMP) management capabilities to be added to the unit in addition to the EFM management function.
23
Features
2.2.1
Key Features
The key features of the FSP 150Mx/CX are: Two FSP 150Mx base variants are available, to provide: Optical Access Interfaces Electrical Access Interfaces. 19 Chassis, European Telecommunication Standardization Institute (ETSI) rack mounting compliant with: optional rack mounting brackets available optional wall mounting available. Factory installable dual Power Supply Unit (PSU) options available: Alternating Current (AC); and Direct Current (DC). Management capabilities: based on the IEEE 802.3ah EFM standard and the Operations, Administration and Maintenance (OAM) protocol. It will interact with other 802.3ah equipment. a remote unit will take configuration from a main unit the remote unit will be managed via the units Network Interface link. Factory installable NEMI option available, to add full SNMP manageability to unit. In field software upgradable. See Chapter 4 Management Overview for further details of FSP 150Mx management. Access Interfaces, which are electrical on the FSP 150ME, where 10 x 10/ 100baseT ports are provided. The FSP 150MO, however, offers optical options using Small Form Factor Pluggable (SFP) Transceivers and 10 x 100FX ports are provided. Network Interface, which is electrical as standard on both units, where 2 x 100/1000baseT ports are provided. Gigabit Ethernet (GbE) optical options are available using SFP Transceivers. Fiber protection (2 ports) on the Network Interface link. CE approved. designed to meet Network Equipment Building Systems (NEBS) standard, Level 3.
2563XE07_Ch2_Features.fm - 16. October 2007
24
TM
Optical Networking
2.3
Traffic Services
FSP 150Mx/CX supports the following traffic services: Tree, Ring and Chain support Dual fiber or single fiber bi-directional SFP transceiver support Auto MDI/MDIX on copper interfaces 2000 byte Maximum Transmission Unit (MTU) for Fast Ethernet 9250 byte Jumbo frame support Institute for Electrical and Electronics Engineers (IEEE) 802.1Q tag addition and Virtual Local Area Network (VLAN) Tag Support Auto-negotiation Advertising Port ID (PID) to VLAN translation Hot Standby Routing Protocol (HSRP)/Virtual Router Redundancy Protocol (VRRP) forwarding Link Loss Forwarding Remote Authentication Dial In User Service (RADIUS) authentication support Traffic Management.
2.3.1
Data Rates
The following data rates are supported:
Unit MO ME MG CX Access Port 10/100 BaseX 10/100 BaseT 1000 BaseX 10/100 BaseT Network Port 100/1000 BaseX 100/1000 BaseT 100/1000 BaseX 100/1000 BaseT 1000 BaseX 100/1000 BaseT 10/100 BaseX
Note: For 1000 BaseX operations, autonegotiation advertising is mandatory.
2.3.2
Frame Sizes
The FSP 150Mx units can be configured to support jumbo frames (9250 bytes). The FSP 150CX supports frame sizes up to 2000 bytes. This allows for the maximum size Ethernet packets (i.e. 2000 bytes) plus support for VLAN tagging and proprietary protocols such as Cisco ISL which requires a MTU size of 1548 bytes. Any frames received that are larger than the MTU will be recorded as an oversize frame received event.
25
Features
2.3.3
Hot Standby Routing Protocol/Virtual Routing Redundancy Protocol Forwarding (HSRP/VRRP)

In layer 3 protection mode only, HSRP/VRRP packets are bridged between the two network ports, that is, all HSRP and VRRP packets received via network port 1 are transmitted via network port 2 and vice versa.
2.3.4
Auto-Negotiation Advertising
Auto-negotiation advertising allows the FSP 150 Mx/CX and another device to determine the link speed and duplex mode automatically.
2.3.4.1
Auto-negotiation
Auto-negotiation is supported on all ports and must always be enabled to guarantee the correct protection and communication mechanisms between two FSP 150 units. It is enabled by default.
2.3.4.2
Link Speed
The link speeds supported are shown below.
Electrical Access 10/100 1000 10/100 Optical Access 100 Electrical Network 100/1000 100/1000 100/1000 Optical Network 100/1000 100/1000 1000 10/100
Variant MO ME MG CX
Management 10/100 10/100 10/100 10/100
2.3.4.3
Duplex Mode
Duplex mode is supported on all ports. Half-duplex is supported only on the FSP 150Mx management ports.
2.4
2.4.1
Traffic Forwarding
FSP 150Mx
The traffic forwarding scheme used by the FSP 150Mx is consistent across the whole aggregation range with all interfaces IEEE standards compliant. This standards compliance ensures that core and customer networks based on Ethernet technology supplied by any vendor will interoperate with an FSP 150 access network. Traffic is forwarded within an FSP 150Mx access network using IEEE802.1Q VLAN tags within the frame header. In an upstream direction (i.e. customer demarcation to provider core), a VLAN tag is appended to the frame by the first FSP 150Mx. In the downstream direction (i.e. provider core to customer demarcation) a VLAN tag must be generated on the provider edge switch or router prior to forwarding into the FSP 150Mx access network.
26
TM
Optical Networking
The information within the VLAN Identifier (VID) field of the tag is used for routing frames within the access network. In the upstream direction the VID information is built on a hop by hop basis similar to source routing. In the downstream direction, the full source route path must be created within the VID field by the provider edge switch or router. Any customer IEEE802.1Q tags will be preserved as an inner tag and embedded in the frame by the FSP 150Mx.
2.4.2
FSP 150CX
In the FSP 150CX traffic is point-to-point so no complex forwarding mechanism is involved.
2.5
2.5.1
Traffic Service Protection (FSP 150Mx only)

Network Path Protection
Having two network ports, The FSP 150Mx employs an optional line protection scheme. To provide network interface fiber line protection the FSP 150Mx may be populated with a second SFP transceiver and link to provide a secondary fiber path. This will provide fiber path protection and dual homing. A switch over from the active path to the secondary path is performed if one or more of the switching criteria is detected on the active path and none are detected on the secondary path. The protection path is monitored for proper connectivity and the Loss of Signal (LOS) alarm and will not be used unless it is performing properly. Protection switching is based on loss of service monitoring on the primary (working) path. If a LOS failure is detected on the primary and not on the secondary path, a switch to the secondary path will occur. Automated and forced protection switching is supported with the working path and protection path being selected automatically. In addition, the primary path used, can be forced (from path A to B from path B to A) manually by the user, which disables protection switching.
2.5.2
Network Port Protection

Several types of network port protection can be configured on a FSP 150Mx unit: Layer 2 protection without spanning tree. This mode should be used when connecting the FSP150Mx to a layer 2 (Ethernet) metro core. When configured for layer 2 protection one of the network ports will be selected as active and the other one will be passive. The unit will receive and transmit data via the active port only. If the active port fails the unit will automatically switch the formerly passive network ports to active state. Layer 3 protection. This mode should be used when connecting the FSP150Mx to a layer 3 IP) metro core. When configured for layer 3 port protection the unit will accept traffic from both network ports and transmit all traffic received via the access ports via both network ports.
27
Features
Point-to-point protection. This mode should be used when connecting two FSP150Mx units in a point-to-point configuration. When configured for point-to-point protection the unit will transmit all data via both of the network ports and will select one of the network ports to receive from (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state. Force Network 1. This will disable network port protection and force Network port 1 to be used for both transmit and receive. Network port 2 is disabled in this mode. Force Network 2. This will disable network port protection and force Network port 2 to be used for both transmit and receive. Network port 1 is disabled in this mode. Link aggregation protection. When configured for link aggregation protection the unit will receive data via any of the network ports and will select one of the network ports to transmit via (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state.
Network port protection can be configured both on a stand alone FSP150Mx unit and on a Tandem node.
2.5.3
Tandem Mode
Two FSP 150Mx units may be connected in Tandem to provide redundancy. When connected in Tandem the two nodes of the two FSP 150Mx units are connected together at network ports, and the access ports are grouped in pairs such that access ports, here shown as i (where i = 1 to 10), of the two units belong to the same group. The index of the port group is the same as the index of the ports.
N1
N2
N2
N1
1 2
10
1 2
10
Figure 2-1: FSP 150Mx Tandem Mode
28
10
TM
Optical Networking
2.6
Egress Multicast Support (FSP 150MG only)

The Egress Multicast feature provides an efficient Layer 2 multicast and has been designed to be used in Tree, Ring and Chain topologies. The FSP 150MG provides the following Egress Multicast features: Egress Multicast forwarding. See Section 2.6.1.1 Egress Multicast Forwarding. Multicast protection. See Section 2.6.1.2 Multicast Protection. Ingress IGMP identification. See Section 2.6.1.3 Ingress IGMP Identification. Egress Multicast configuration and statistics. See Section 2.6.2 Egress Multicast Configuration and Statistics.
2.6.1
2.6.1.1
Egress Multicast Features

Egress Multicast Forwarding
Egress Multicast traffic uses separate queues to those used for Unicast traffic. A specific VLAN tag is used internally within the FSP 150 network to identify and define Egress Multicast traffic. Only one Egress Multicast queue and one Multicast VLAN tag (i.e. 0xF00) is supported. Multicast fowarding has the following features: Normal FSP 150Mx/CX VLAN translation is also applied to Multicast VLAN tags. Frames tagged with Multicast VLAN tags are distributed to multiple Access ports and are not modified during distribution. Access ports need to be configured to belong to a Multicast VLAN in order to forward Multicast traffic. Multicast VLAN tags are removed when frames reach ports configured to Leaf Mode. Frames with a Multicast VLAN tag, received on an Access port configured to Branch Mode, are dropped. Jumbo frames are supported for Multicast traffic.
If Traffic Management is: enabled, Multicast traffic will have: lower priority than high priority queues higher priority than medium and low priority queues.
not enabled, Multicast traffic will have equal priority to Unicast traffic and Round Robin scheduling will occur between Unicast and Multicast queues.
29
Features
2.6.1.2
Multicast Protection
The existing protection mechanisms used for FSP 150Mx/CX traffic protection is also supported for Egress Multicast traffic: Tandem Protection. This protection is offered for tree and ring topologies and is always enabled for Multicast traffic as it is for Unicast traffic. Network Port Protection. By default, the protection for Multicast traffic will be that configured on the port. However, there is the opportunity to configure another protection mode specifically for multicast traffic.
A Preferred Port setting is also possible for Multicast protection.
2.6.1.3
Ingress IGMP Identification

Ingress IGMP frames are optionally identified and tagged with the Multicast VLAN tag before leaving an FSP 150 network. IGMP frames received on Access ports can be sent on Network ports: with an unmodified VLAN tag with the Multicast tag added as two frames, one frame with the unmodified VLAN tag and the other frame with the Multicast tag.
Typically the Multicast VLAN tag is only configured to be sent on the Network ports on the top node in a FSP 150 network. Normal VLAN translation applies to IGMP frames.
2.6.2
Egress Multicast Configuration and Statistics

The following configuration options are available for setting up Egress Multicast: Egress Multicast can be enabled or disabled on each Access port of the FSP 150MG. An IGMP VLAN tag can be configured. IGMP traffic received at an Access port and belonging to a Multicast VLAN group, may be set to be transmitted via the Network ports: with an unmodified VLAN tag with the VLAN tag replaced with the Multicast tag as two frames, one frame with the unmodified VLAN tag and the other frame with the Multicast tag.
Traffic can be policed by configuring dedicated Multicast regulators, measuring Committed Information rate (CIR) and Committed Burst Size (CBS). Multicast protection can be provided by configuring a Multicast protection type.
30
TM
Optical Networking
See Chapter 6, Section 6.12 Configuring Egress Multicast (FSP 150MG only) for details on the configuration options available. Statistical counters are provided to monitor Multicast traffic and provide the number of: Policed Multicast Frames Multicast frames received on a Network port Multicast frames transmitted on a Network port Multicast octets received on a Network port Multicast octets transmitted on a Network port Multicast frames transmitted on an Access port Multicast octets transmitted on an Access port. See Chapter 8, Section 8.2 Viewing Counters for further details.
31
Features
32
TM
Optical Networking
Chapter
Components
3.1 Introduction
3
The products: FSP 150Mx, and its variants, Optical (MO), Electrical (ME) and Gigabit (MG) FSP 150CX. The components: Chassis Fans Power Supply Units (PSUs) Interfaces Cabling Small Form Factor Pluggable (SFP) Transceivers.
This chapter describes the products and components of the Fiber Service Platform Multiplexer/Hub Node (FSP 150Mx/CX). These comprise:
3.2
3.2.1
3.2.1.1
FSP 150Mx/CX Products

FSP 150Mx Variants
FSP 150MO
The optical variant of the FSP 150Mx, the FSP 150MO, is shown in Figure 3-1.
2563XF07_Ch3_Components.fm - 16. October 2007
Figure 3-1: FSP 150MO Unit The FSP 150MO supports up to 10 x 100BaseX optical access connections using optical fiber.
33
Components
3.2.1.2
FSP 150ME
The electrical variant of the FSP 150Mx, the FSP 150ME, is shown in Figure 3-2.
Figure 3-2: FSP 150ME Unit The FSP 150ME supports up to 10 x 10/100BaseT access connections using electrical cabling.
3.2.1.3
FSP 150MG
The gigabit variant of the FSP 150Mx, the FSP 150MG, is shown in Figure 3-3.
Figure 3-3: FSP 150MG Unit The FSP 150MG supports up to 6 x 1000BaseX access connections over optical fiber.
3.2.2
FSP 150CX
A FSP 150CX unit is shown in Figure 3-4.
Figure 3-4: FSP 150CX Unit The FSP 150CX supports 10 x 10/100BaseT electrical access ports and 10 x 100BaseX optical network ports (SFP).
34
TM
Optical Networking
3.3
3.3.1
Component Descriptions
Chassis
The FSP 150Mx/CX chassis are alloy steel cases which house the entire system. The dimensions of the chassis are: Table 3-1:
Dimensions Height Width
1
Chassis Dimensions
Mx(mm) 44 439 270 CX(mm) 88 439 270
Depth 2
1 2
With mounting brackets
Without International Electrotechnical Commission (IEC) optical connectors;
The depth allows the chassis to fit into a 300mm deep European Telecommunication Standardization Institute (ETSI) cabinet. The chassis may be positioned as a standalone unit or it may be rack or wall mounted. Adaptation to rack or wall mounting is possible by using mounting brackets and separate removable mounting brackets are available for: 19 rack mounting 23 ETSI rack mounting Recessed rack mounting brackets are also available for 19 and 23 ETSI racks in order to ensure that optical fibre bend radius is maintained when installed in some cabinets with doors wall mounting. All brackets are designed to be screwed to the sides of the chassis and the screws supplied have metric threads.
3.3.2
Fans
The chassis is cooled by fans (two in the FSP 150Mx and four in the FSP 150CX), which draw air side to side through the chassis ventilation slots, in line with ETSI requirements. The air is drawn in through the ventilation slots located on the right side panel of the chassis and exhausted via the ventilation slots located on the left side panel.
35
Components
FSP 150Mx
FSP 150CX Figure 3-5: Chassis Ventilation Slots The fans are factory-fitted and not exchangeable. In the event of a single fan failure, sufficient airflow is available from the remaining working fan to keep the unit running. Each fan provides a signal indicating that it is operating normally. An alarm is generated if the fan is not operating normally, if it malfunctions, or its speed falls below a pre-set limit.
3.3.2.1
Fan Indicator
The fans support the standard indicator marked Fan. When illuminated Green, correct operation of the fans is indicated. When illuminated Red, a failure is indicated (see Section 3.3.4.3 Management Indicators).
3.3.3
Power Supply Units

The FSP 150Mx/CX provides dual PSUs located at the far left hand side of the chassis. Factory fitted dual supply options are available and two variants are offered, as follows: Alternating Current (AC), autoranging 90 to 264V, over voltage, over current protected, with input to the chassis via IEC 320 input connectors. Direct Current (DC), autoranging 36 to 72V, over voltage, over current protected, with input to the chassis via block barrier type connectors with 5 screw terminals (including 1 earthing screw). A plastic protective cover, covers the input connector.
36
TM
Optical Networking
Both operate in Hot Standby. Under normal operating conditions the two units share demand for power. In the case of failure of one supply, the remaining supply is capable of powering a FSP 150Mx/CX on an ongoing basis. Each PSU provides a signal indicating that it is operating normally. An alarm is generated if the PSU malfunctions.
3.3.3.1
PSU Indicators
The PSUs support the standard indicators marked PSU 1 and PSU 2. When illuminated Green, correct operation of the PSUs is indicated. When illuminated Red, a malfunction is indicated (see Section 3.3.4.3 Management Indicators).
3.3.4
Management Interface
The FSP 150Mx/CX is capable of retrieving information from a partner node by using the Ethernet First Mile (EFM) Institute for Electrical and Electronics Engineers (IEEE) 802.3ah standard and the Operation, Administration and Maintenance (OAM) protocol. Each FSP 150Mx/CX has a small on-board micro controller responsible for handling the EFM protocol requests and overall management takes place from the carrier end of the link with embedded EFM frames being delivered by the Network Interface fiber connection. A factory fitted Network Element Management Interface (NEMI) provides extended management control of all traffic and management features. See Section 3.3.4.1 Network Element Management Interface.
3.3.4.1
Network Element Management Interface

The FSP 150Mx NEMI is based on a X86 processor with 64MB Random Access Memory (RAM). It contains the Operating System (OS) OpenBSD. Externally, the NEMI adds a 10/100BaseT RJ45 connection from an internal switch. Functionally, the NEMI brings with it a command driven Command Line Interface (CLI) and a menu driven Craft/Web Interface for full configuration of the unit. The OS runs a full Internet Protocol (IP) stack along with a File Transfer Protocol (FTP) Client/Server, Secure Shell (SSH) Server and Simple Network Management Protocol (SNMP) agent, allowing remote management and integration into management systems. All elements of the FSP 150Mx can be controlled and monitored via the NEMI. The elements monitored include the PSUs, Fans and all Access and Network connections. The NEMI communicates with each element in the Chassis via an internal system bus. Each element is polled in turn for status information. If the response is not correct, the NEMI interrogates in greater detail for the exact fault. This allows the NEMI to determine whether any of the conditions have changed since the last time it was polled. The FSP 150Mx NEMI also enables SNMP management via a connected SNMP Network Management System (NMS). The NEMI allows the NMS to interrogate the FSP 150Mx using SNMP to establish the state of the Chassis.
37
Components
The NEMI maintains an Enterprise Management Information Base (MIB) for the managed objects within the FSP 150Mx. This MIB can be accessed via an SNMP agent running via the RJ45 Ethernet connector. The NEMI provides the following features: SNMP agent Abstract Syntax Notation 1 (ASN1) coded private MIB IP stack SSH agent FTP or HTTP for download of new code CLI (VT100 console) Craft Interface (VT100 console) Web Interface.
3.3.4.2
Management Connections 3.3.4.2.1 Ethernet Port

The FSP 150Mx NEMI has one management RJ45 Ethernet connector on the front panel labelled Management (the management port of the FSP 150MG is labelled AUX). This provides full support for 10/100 Mbit/s Carrier Sense Multiple Access/Collision Detect (CSMA/CD) Ethernet applications and is fully compliant with the Institute of Electrical and Electronics Engineers (IEEE) 802.3:1998 Ethernet standard.
3.3.4.2.2 MG DCN Port

In addition to the management Ethernet port (AUX), an extra ethernet port is provided on the FSP 150MG, labelled DCN. This enables connection to the management interface via a Data Communication Network (DCN).
3.3.4.3
Management Indicators
For the FSP 150Mx/CX the following alarm indicators are provided. Table 3-2:
Indicator PSU 1/2 PSU 1/2 Fan Fan Alarm
FSP 150Mx/CX Alarm Indicators

Color Green Red Green Red Red Indication when illuminated: The PSU is working normally. There is a PSU fault The fan is working normally. There is a fan fault. A major fault condition has occurred.
38
TM
Optical Networking
3.3.5
3.3.5.1
Access and Network Interfaces

Connector Types
The FSP 150Mx/CX supports two types of connector: Electrical interface, a copper IEEE 802.3 Ethernet port with Auto MDI/ MDIX enabled, allowing both cross-over and straight-through cables to be connected. Optical interface, supporting optical SFP Transceivers designed to the SFP Multi Source Agreement (MSA), fully qualified, tested and hot swappable (see Section 3.3.7 SFP Transceivers).
3.3.5.2
Indicators 3.3.5.2.1 Electrical Access Indicators

The electrical access connectors have the following indicators: Table 3-3:
Indicator Green
Electrical Access Indicators

Marking on Chassis Lk Indication when illuminated: Green. The integrity of the electrical access (RJ45) link is good. Off. The electrical network link has failed. Blinking. The integrity of the electrical access link is good and data activity has been detected. Amber. 100 Mbit/s Off. 10 Mbit/s.
Amber
Rate
3.3.5.2.2 Electrical Network Indicators

The electrical network connectors have the following indicators: Table 3-4:
Indicator Link
Electrical Network Indicators

Marking on Chassis Lk Indication when illuminated: Green. The integrity of the electrical network (RJ45) link is good. Off. The electrical network link has failed. Blinking. The integrity of the electrical network link is good and data activity has been detected. Green. 1000 Mbit/s Amber. 100 Mbit/s.
Rate
Rate
39
Components
3.3.5.2.3 Optical Access Indicators

The optical access connectors have the following indicators: Table 3-5:
Indicator Link
Optical Access Indicators

Marking on Chassis Lk Indication when illuminated: Green. The integrity of the Access optical link is good. Off. The Access optical link has failed. Blinking.The integrity of the optical access link is good and data activity has been detected. Red. An error condition is present (e.g. the SFP Transceiver is not recognized, and has not been approved by ADVA Optical Networking).
State
State
3.3.5.2.4 Optical Network Indicators

The optical network connectors have the following indicators: Table 3-6:
Indicator Rate N1/ Rate N2
Optical Network Indicators

Marking On Chassis Rate Indication when illuminated: Green. 1000Mbit/s Amber. 100Mbit/s. Red. The SFP Transceiver is not recognized, and has not been approved by ADVA Optical Networking. Green. The integrity of the Network Interface link is good. Off. The Network interface link has failed. Blinking. Data activity has been detected on the link.
Link N1/ Link N2
Lk
3.3.6
3.3.6.1
Cabling
Optical Cables
When cabling SFP Transceivers, use fiber-optic cables that will support distances up to the maximum drive distance. Both single mode (9/125m) and multimode (50/125m and 62.5/125m) are supported.
3.3.6.2
Electrical Cables
A Category 5E Unshielded Twisted Pair (UTP) cable terminated with RJ45 connectors should be used to connect to customer equipment and management devices. The cable should be no longer than 100m and should be compliant with the Institute of Electrical and Electronics Engineers (IEEE) 802.3:1998 Ethernet standard.
40
TM
Optical Networking
3.3.7
SFP Transceivers
SFP Transceivers are self contained optics with a built-in transmit and receive function which may be fitted into optical access or network interface slots of the FSP 150Mx/CX. A choice of fully qualified and tested optical SFP Transceivers are available from ADVA Optical Networking All SFP Transceivers provided by ADVA Optical Networking are designed to comply with the standard dimensions defined by the SFP MSA made between the main manufacturers in the Transceiver market. A list of supported SFP Transceivers is given in Chapter 11, System Data. Figure 3-6 shows an example of a SFP Transceiver.
Electrical Connector (not visible) Label Latching Mechanism
LC Connectors
Protective Plug
Figure 3-6: Typical SFP Transceiver The connectors of the SFP Transceiver may be single SC or duplex LC. Upon delivery, the optical connector is equipped with a protective dust plug to prevent contamination of the connector and the internal components. A latching mechanism is provided on the Transceiver to assist in fitting and removal. The latching mechanism may differ between SFP Transceivers supplied by ADVA Optical Networking. All SFP Transceivers are hot swappable and when fitted are recessed in the front panel to allow effective fiber handling and bend radius provision.
An SFP Transceiver receives optical signals from the access or network interfaces at the wavelength specific for the Transceiver, performs optical to electrical conversion and transfers the electrical signals to the FSP 150Mx/CX assembly for further processing and transmission. Conversely, the SFP Transceiver receives electrical signals from the FSP 150Mx/CX assembly and then converts the signals into optical signals via a laser and laser driver.
41
Components
The SFP contains a software key that is checked by the FSP 150Mx/CX base unit prior to initialization. This check is performed to ensure that only ADVA Optical Networking approved SFP units are used within the FSP 150Mx/CX. SFP units are individually qualified by ADVA Optical Networking to ensure the quality of the optical output and conformance to the MSA. If a non-approved SFP is inserted into any of the units, the optic will not be initialized, the port will not function and an alarm condition will be generated. In addition, the SFP Transceiver has an integrated area of Electrical Erasable Programmable Read Only Memory (EEPROM) which stores information such as the serial number of the Transceiver and laser type, supported link length, revision level and part code. This information is accessed via the management interface.
42
TM
Optical Networking
Chapter
Management Overview
4.1 Introduction
4
management options Ethernet First Mile (EFM) Operation, Administration and Maintenance (OAM) support Simple Network Management Protocol (SNMP) support management topology vendor extensions.
This chapter introduces the concept of Fiber Service Platform 150 Multiplexer/ Hub Node (FSP 150Mx/CX) management and provides details on the management available when a Network Element Management Interface (NEMI) card is fitted. On the FSP 150CX a NEMI is always fitted. For the FSP 150Mx the NEMI is optional. This chapter describes:
4.2
Management Options
A FSP 150Mx/CX fitted with a NEMI is always managed. A NEMI fitted in an FSP150Mx/CX will manage the node itself and nodes connected to the FSP 150Mx/CX downstream (access) ports. In addition, a FSP 150Mx/CX that has a NEMI fitted, but has its NEMI mode set to Passive can be managed by a FSP 150Mx/CX upstream via EFM OAM. This enables a FSP 150Mx/CX with a NEMI to be positioned anywhere in an Access Tree, Point-to-Point Link or Tandem Node. (See Chapter 6 Configuration for details of active or passive NEMI modes). When a FSP 150Mx is not fitted with a NEMI, and not connected to an upstream node, the FSP 150Mx is unmanaged. The ADVA vendor extensions to the Institute for Electrical and Electronics Engineers (IEEE) 802.3ah standard include specific managed objects within the following broad categories: Access/Network Interface Short Form Factor Pluggable (SFP) Transceiver inventory information Access/Network Interface Performance Metrics (PMs) including error counts Access/Network Interface optical power levels Remote firmware download capability Unit system status information.
2563XG07_Ch4_Mgt_Over.fm - 16. October 2007
43
Management Overview
Where EFM is not supported, a NEMI is required in at least one FSP 150Mx/CX located at the top of the tree. A NEMI adds: Internet Protocol (IP) capability SNMP agent and a Management Information Base (MIB) Secure Shell (SSH)/telnet/browser for ethernet connection Command Line Interface (CLI) for Personal Computer (PC) VT100/220 terminal emulation File Transfer Protocol (FTP) sand Hypertext Transfer Protocol (HTTP) support for firmware/software upgrades.
4.3
EFM OAM Support

The key network management capability of the FSP 150 family is that offered by the IEEE 802.3ah EFM OAM protocol. By default, all units within the FSP 150 family in a provider infrastructure can be managed using the EFM protocol in band. IEEE 802.3ah EFM OAM Protocol is a lightweight, low overhead protocol that allows remote Network Elements (NEs) to perform management functions in band with user data across the provider infrastructure consuming very little bandwidth. The FSP 150Mx/CX is capable of retrieving information from a partner node using the EFM IEEE 802.3ah standard and the OAM protocol. Overall management takes place from the carrier end of the link with embedded EFM frames being delivered by the network interface A managed FSP 150Mx/CX will perform EFM/OAM discovery on all data ports, i.e. access ports and network ports. Additionally, the network ports will honor EFM OAM standard loopback control. All other EFM management is conforming to the standard, but implemented using vendor extensions. Management using EFM OAM frames may be done over any network interface (fiber or electrical). Unmanaged nodes (nodes in a topology without a NEMI and not connected to an above NEMI) may also be managed using EFM OAM frames over the AUX (local management interface) port. The network ports of the FSP 150CX are contained within the chassis, it is, therefore, not possible to manage the node using the network ports.
4.3.1
EFM in Dedicated Transport Solutions

If the FSP 150Mx/CX is deployed in a point-to-point topology, where there is no connectivity via a shared provider network, management is typically provisioned using an external management network connected at one or both ends of the link. This can be achieved via a Ethernet/IP connection into the local management port of the FSP 150Mx/CX.
4.3.1.1
Local Ended Management

In this deployment, one FSP 150Mx/CX is configured to support network management functions with the service providers OAM system. This is referred to as the local unit. The local unit will collect data from the remote unit via a management channel conforming to the IEEE 802.3ah standard.
44
TM
Optical Networking
Network Management System
Local Unit
Remote Unit
Figure 4-1: FSP 150Mx/CX Management; Local Ended Management

If a NEMI is fitted in the local unit, management could take place over a Data Communication Network (DCN) such as an Ethernet Local Area Network (LAN) connection via the local management interface of the FSP 150Mx/CX. Also, If a NEMI is present, the SNMP protocol can also be utilized.
4.3.1.2
Dual Ended Management

When deployed in a leased line point-to-point configuration it is possible to configure both local and remote units to communicate independently with the service providers OAM system. If a NEMI is fitted in both the local and remote units it is possible to manage each FSP 150Mx/CX independently, by connecting to the management interface and accessing a local CLI at each end. Both units are therefore connected to a Network Management System (NMS).
Local Unit
Remote Unit
Figure 4-2: FSP 150Mx/CX Management; Dual Ended Management.
4.3.2
4.3.2.1
EFM in Shared Transport Solutions

Integration with Existing Network Management Systems
In a shared transport network EFM can be used for managing objects defined under IEEE802.ah. A FSP 150Mx/CX can be integrated into remote network management facilities, which are designed to manage and monitor all corporate networks. The facilities should be set up as a NMS that links to NEs via a DCN or LAN designed to carry management traffic. When the NMS links into a DCN or LAN it will provide a graphical representation of the network, the NEs present on the network and each NEs current operational state. A common application used for network management is Hewlett-Packard OpenView (HPOV), Network Node Manager (NNM). However, the NMS used will be specific to the organization.
45
Management Overview
It is out of the scope of this document to describe the use of any specific NMS. If further details are required on the use of a particular NMS, please refer to the documentation supplied to support it.
4.3.3
IEEE 802.3ah EFM OAM Vendor Extensions

In order to extend the management capability of the FSP 150Mx/CX, ADVA Optical Networking Vendor Extensions have been developed to provide additional management not covered by the IEEE 802.3ah EFM OAM protocol. IEEE 802.3ah EFM standard products allow read capability on the provider port only. The ADVA Optical Networking extensions to this standard allow for reading and writing parameters associated with any port or sub-system of the unit. Software upgrading via EFM is also supported. The vendor extensions include specific managed objects within the following categories: Access/Network interface configuration. Unit configuration. Access/Network interface SFP Transceiver inventory information. Access/Network interface Performance Metrics PM including error counts. Access/Network interface optical power levels. Remote firmware download capability. Unit status information.
Vendor Extensions are intended for use by partner organizations to implement a EFM scheme compatible with the FSP 150Mx/CX. For further information on the FSP 150Mx/CX Vendor Extensions, contact ADVA Optical Networking (see Preliminaries, Contact ADVA).
4.4
SNMP Support
Support for SNMP is provided by the NEMI. This is located in the root Mx/CX with an SNMP agent controlling all units, using EFM OAM as far as the next SNMP domain. If a lower Mx/CX has a NEMI another SNMP domain begins. The FSP 150CX is not intended to be used as a root node in a tree, even though it would be possible, as the tree nodes are connected to the electrical port.
4.4.1
Integration with SNMP

The FSP 150Mx/CX provides seamless integration between SNMP and EFM environments to ensure seamless network level views via the FSP 150 enterprise MIB.
46
TM
Optical Networking
Network Management System Management DCN SNMP Management Domain (red) FSP 150 Mx/CX Root Node NEMI
EFM Management Domain (blue)
FSP 150CP
FSP 150CP
FSP 150CP
Figure 4-3: SNMP/EFM Integration

A NEMI running within an FSP 150Mx/CX will present an IP/SNMP object to a NMS and will use EFM to communicate downstream to attached units The downstream units respond with EFM OAM Protocol Data Unit (OAMPDU) and the resulting information is used to populate the MIB. The NMS will extrapolate and present the downstream devices as independent units within an access tree.
4.4.2
The FSP 150 MIB

When the FSP 150Mx/CX is configured, SNMP can handle and log events (i.e specified changes in the FSP 150Mx/CX, also referred to as traps) and enable the user to view the current state of the system. In order to do this, the NMS is supplied with FSP 150Mx/CX structural information in a MIB. This describes the logical structure of the FSP 150Mx/CX and the events and states that are to be supported. The SNMP agents return information in the form of variables (also called Object Identifiers (OIDs)) coded in Abstract Syntax Notation 1 (ASN1). An example of an ASN1 coded variable is 1.3.6.1.2.1.1.1.0, which is the system description identifier (according to Request for Comments (RFC) 1213, the variable translates into iso.org.dod.internet.mgmt.mib-2.system.sysDescr.0). A MIB constitutes a text file to define the hierarchical structure of the variables and to assign textual names to the variables, so that they are easier to understand by the user.
The FSP 150Mx/CX uses standard variables which are provided in a number of MIBs defined by RFCs. However, FSP 150Mx/CX uses additional non-standard variables which are defined in a private Enterprise MIB (see Section 4.4.2.1 Supported Variables (RFC Conformance) and Section 4.4.2.2 FSP 150 Enterprise MIB Structure below). Enterprise MIB files are provided on the FSP 150Mx/CX CD-ROM. The MIB files should be downloaded to the NMS, before SNMP can be used effectively. The files may be copied from the CD-ROM using standard operating system commands.
47
Management Overview
4.4.2.1
Supported Variables (RFC Conformance)

The FSP 150Mx/CX uses standard variables which are provided in the MIBs defined by the following RFCs:
RFC 1157 RFC 1213
This defines generic SNMP v1 traps. This defines a standard MIB (i.e. MIB-II) and should be supported by all manageable NEs. The FSP 150Mx/CX supports the system variables and parts of the interfaces and SNMP variables that are defined in MIB-II. This defines a Physical Entity MIB (Version 2) and contains the following: An entPhysicalTable, which should provide a list of all physical entities that make up an assigned and/or equipped FSP 150Mx/CX and also all containment relationships. It also includes information on connected and/ or assigned remote FSP 150Mx/CX systems. An entPhysicalContainsTable, which should provide a list of what all the physical entities are made up of and also all containment relationships.
RFC 2737
RFC 2863
This defines an Interface Group MIB and an ifTable which should list all the interfaces defined for a FSP 150Mx/CX. The FSP 150Mx/CX supports most of the variables that are defined in the ifTable. FSP 150Mx/CX also supports variables which are specific to the ADVA Optical Networking and the product. These are defined in the Enterprise MIB, which is structured as a MIB tree (see Section 4.4.2.2 FSP 150 Enterprise MIB Structure). This is a hierarchical information base that is divided into the following parts: topologyMIB alarmMIB configAndStatusMIB performanceMIB trapMIB vendorTypesMIB PidTranslationMIB TrafficTestMIB.
Enterprise MIB
Under these main headings, the general and specific information on the system and its components can be read using an SNMP management application or MIB browser. The community string used to read the values is public. The MIB contains tables which provide static configurational information, as well as current status information. SNMP alarms are described in the branch of the tree labelled trapMIB.
4.4.2.2
FSP 150 Enterprise MIB Structure

The FSP 150 Enterprise MIB is organized as illustrated below. The areas highlighted in grey belong to the FSP 150 specific branch.
48
TM
Optical Networking
enterprises
2544
adva
products
fsp150 products 1
10
fsp150
1 fsp150 cp
2 2 fsp150 Mx/CX
1 topologyMIB 1 alarmFilters
2 alarmMIB 2 currentAlarms
3 configAndStatusMIB
4 performanceMIB
5 trapMIB
6 vendorTypesMIB
7 pidTranslationMIB
8 trafficTestMIB
Figure 4-4: FSP 150 Enterprise MIB Structure

Under the FSP 150 root, the MIB tree is divided into two branches: The fsp150Products node, which provides a standard way of defining an OID for the different variants of the FSP 150 product. These OIDs are used for the sysObjectID value in RFC 1213, to uniquely identify the NE containing this MIB. The fsp150Mx/CX MIB node is further divided into the following branches: topologyMIB, which contains MIB tables with local and remote chassis and information on how they are connected and by whom they are managed. alarmMIB, which contains the fault management part of the MIB and divides into alarmFilters and currentAlarms. configAndStatusMIB, which contains the configuration and status management part of the MIB. It contains tables that extend the ifTable in RFC 2863 and the entPhysicalTable in RFC 2737. performanceMIB, which contains the performance management part of the MIB and contains tables to provide information on interface performance and OAM statistics. trapMIB, which contains all the enterprise specific traps that can be sent by this NE, i.e state change traps, attribute value change traps and alarm traps. vendorTypesMIB, which defines OIDs used as entPhysicalVendorType in RFC 2737.
49
Management Overview
pidTranslationMIB, which contains the Port ID (PID) Translation tables. trafficTestMIB, which contains MIB tables for Ingress/Egress Generator and Filter configuration and status information.
4.5
Network Element Management Interface

The FSP 150Mx NEMI provides full system management facilities. This supports: Configuration management Performance management via counters Online Firmware/Software upgrades via FTP or HTTP Access control Alarm reporting using SNMP v1 Traps.
In the FSP 150Mx the NEMI is a factory-fitted option.
In addition, most providers already have sophisticated management topologies based on SNMP within the metro core network and the presence of a NEMI makes it possible for these to be utilized. For this, all FSP 150Mx/CX NEMIs support connection of a NMS. A NMS application may be connected directly to the NEMI management port or indirectly via an external DCN and a router. The NEMI is accessible via several interfaces which are described in Chapter 5, Management Interfaces.
4.6
4.6.1
Management Features
IP Inband Management (FSP 150Mx Only)
Management is extended with the capability of managing a unit with a NEMI using inband IPv4 communication via the Network Ports. This feature is always enabled on the FSP 150Mx if an IP address is assigned to the network ports. The presence of IP inband management has no relationship with management via EFM, i.e. the two management mechanisms can run concurrently with EFM managing the physical link, and the unit management being via IP. The user is able to: Enable/disable Virtual LAN (VLAN) tagging of inband IP traffic
Configure a management VLAN identifier (VID), to be shared between the two network interfaces.
A specific Medium Access Control (MAC) address is allocated to the NEMI for its communication over the network ports. The FSP 150Mx accepts management frames according to the following rules: All traffic within a management VLAN are forwarded exclusively to the NEMI regardless of the destination address of the Ethernet frame.
50
TM
Optical Networking
All user traffic received via the access port and tagged with the VID of the management VLAN is dropped.
The NEMI participates in IP protocol and sends management packets to an appropriate network port via the motherboard. VLAN-tagged inband management is disabled by default and enabled through the NEMI Management interface.
4.6.2
Configuration Management
The FSP 150Mx/CX is fully configurable with configuration data being stored persistently for restoration. The following features are user configurable: IP Connectivity, to enable communication between a NMS and the FSP 150Mx/CX so that management information can be obtained. Date and Time, to enable the synchronization of all NEMI system clocks to ensure consistent error reporting across multiple units. Secure Access, to control access to the FSP 150Mx/CX by the use of the following: SNMP access User authentication Security enhancements Optional Access Control Lists (ACLs).
Active/Passive NEMI Mode (Mx only), to set a unit NEMI to active or passive. Traffic Services, to configure the services provided and the operation of the service interfaces. Network Port OAM, to enable management to be performed via the EFM OAM protocol. Protection, to configure the tandem and line protection modes for the Network Interface. Traffic Management, to enable effective management of traffic across service interfaces. Fault Management, to configure the settings that will enable fault management, see Section 4.6.5 Fault Management. Audit Logging, to enable changes caused by user interaction to be logged, see Section 4.6.5.2 Audit Logging.
Procedures for configuring the FSP 150Mx/CX are provided in the Chapter 6 Configuration.
51
Management Overview
4.6.3
Performance Management
Performance management comprises the checking of: Port counters Network Port OAM statistics PID Translation status.
Procedures for monitoring the FSP 150Mx/CX are provided in the Chapter 8 Performance Management.
4.6.4
Maintenance
Maintenance of the FSP 150Mx/CX comprises: Viewing chassis and port inventories Rebooting and resetting the FSP 150Mx/CX Backing up and restoring settings Upgrading firmware/software Periodic inspection and cleaning of FSP 150Mx/CX equipment.
Procedures for maintaining the FSP 150Mx/CX are provided in the Chapter 9 Maintenance.
4.6.5
Fault Management
Fault management of the FSP 150Mx/CX comprises: Fault finding by: evaluating alarms evaluating the audit log evaluating component status evaluating status indicators.
Fault clearance by: resolving management issues resolving hardware issues resolving incorrect cabling performing a hardware reset replacing hardware components.
Procedures for managing faults in the FSP 150Mx/CX are provided in the Chapter 10 Fault Management.
To enable full management and control of the FSP 150Mx/CX, the system is designed to report defects that could lead to service interruption as alarms. All current alarms are registered and can be viewed via the FSP 150Mx/CX Management tool in use.
52
4.6.5.1
Alarms
TM
Optical Networking
All alarms are assigned to a specific FSP 150Mx/CX component or interface, as follows: Chassis Power Supply Unit Fan Port or Interface.
Alarm Reporting
Alarm reporting can be enabled and disabled by the user. When alarm reporting is off, SNMP traps will not be sent for alarms occurring on the chassis or on chassis components. Defects are detected by monitoring a variety of parameters and in the case of Voltage and Temperature the monitored parameters are compared to the following upper and lower limit thresholds held and set by the user in management: Low Voltage Threshold High Voltage Threshold High Temp Threshold.
Alarm Thresholds
Alarm Severities
Decisions on which alarm types should be visible to the NMS and what severity level should be assigned to each alarm type, may be made by the user and recorded in the Alarm Severity Table. The severity level provides an indication of how the capability of the managed object may be affected by the defect. Alarms result from the filtering of detected defects and when a defect is detected, the following filtering takes place: The defect is filtered to determine the cause of the failure. Failures that are related to a port interface are filtered against the interfaces Administration Status: If the Administration Status is Up, the FSP 150Mx/CX Indicators (Light Emitting Diodes (LEDs) will reflect the failure, as appropriate. If the Administration Status is Testing, the failure is recorded in the current alarm table but no notifications are sent. If the Administration Status is Down, the failure is not processed further and it is not reported at all. Failures are checked against the current alarm reporting settings that have been set by the user via the management interface; and: when Alarm Reporting is On an alarm notification is sent from the FSP 150Mx/CX.
Alarm Filtering
when Alarm Reporting is Off an alarm notification is not sent from the FSP 150Mx/CX. Alarms received are checked against individual alarm reporting settings that have been set by the user via the management interface; and: if an individual alarm is set to be notReported, the alarm is not reported.
53
Management Overview
If the alarm has a severity set, the alarm is reported and the severity of the alarm is indicated, both in management and via the Alarm indicator on the front panel of the local chassis.
4.6.5.2
Audit Logging
An audit log allows the logging of events which can be relayed to a remote server and analyzed for any irregular behavior. The following events are logged: all configuration changes authentication related information NEMI boot and reboots initiated via the user interfaces CLI, Craft, Web and SNMP).
Each event records the following attributes: Event Number. The sequence number of the logged event. Begins at 1 after each reboot. Time stamp. The date and time that the event occurred. Application. The textual name of the application used to apply the change (e.g. Craft, CLI, SNMP). User. The user name of the person making the change. Remote Host. The IP address of the remote server from which the change was performed. Chassis Ser Num. Details of the node affected by the change. Change Type. The type of change made. Parameter. The parameter that has been changed. Value. The value that has been set. Entity. The component on which the event or change occurred
54
TM
Optical Networking
Chapter
Management Interfaces
5.1 Introduction
5
the Craft Interface the Web Interface the Command Line Interface (CLI).
The management interfaces of the Network Element Management Interface (NEMI) enable access to configuration data allowing the user to activate/ deactivate functionality or change parameter values. Three interface types are supported:
These are described in detail in the following sections.
5.2
NEMI Access - User Accounts and Default Password

The NEMI management interfaces are accessible via the three default user accounts: root, which is assigned the security type superuser and provides full access to the management facilities. netadmin, which is assigned the security type admin and provides full access to the management facilities, apart from adding or deleting a user. user, which is assigned the security type monitor and provides readonly access rights to Network Element (NE) information.
The default password for the all accounts is ChgMeNOW. It is recommended that the password is personalized as soon as possible to minimize possible exposure, restrict access to the NEMI and thereby increase system security. Instructions on how to change a password are given in Chapter 6 Configuration.
5.3
2563XH07_Ch5_Interfaces.fm - 30. October 2007
Craft/Web Interfaces
Craft Interface
The Craft Interface is a menu driven interface, resident as software on the Fiber Service Platform 150 Multiplexer/Hub Node (FSP 150Mx/CX) NEMI.
5.3.1
55
5.3.1.1
Craft Interface Access Requirements

Access to the FSP 150Mx/CX NEMI can be obtained via the protocol Secure Shell (SSH) or Telnet application via an Ethernet connection. See the FSP 150 Installation Guide for connection details.
5.3.1.2
Accessing the Craft Interface

The FSP 150 Installation Guide provides detailed information on connecting to the FSP 150Mx/CX NEMI and accessing the Craft Interface.
To access the Craft Interface perform the following steps:
Step 1 Step 2
Ensure that a connection from a local Personal Computer (PC), laptop or VT100 terminal to the FSP 150Mx/CX NEMI has been established, as required. Start a SSH program or Telnet session towards the Internet Protocol (IP) address of the NEMI and login for access initially to the CLI. The Top Mode prompt (top>) will be displayed as described in Section 5.4.4 Modes of Operation.
Step 3
Type craft and press Return to display the Craft Interface Main Menu as shown below.
Details of the options provided by the Craft Interface Main Menu can be found in Section 5.3.3 Craft/Web Interface Menu Structure. Details on how to interact with the Craft Interface can be found in Section 5.3.1.5 Craft Interface User Interaction.
5.3.1.3
Exiting the Craft Interface

To exit the Craft Interface perform the following steps:
Step 1 Step 2
Select 4 Logout from the Main Menu. The Craft Interface will be closed. Close the terminal emulation program, as appropriate.
56
TM
Optical Networking
5.3.1.4
Automatic Logout
If the user has enabled security enhancements, the Craft Interface will enforce a timeout limit of fifteen minutes. If there is no keyboard activity during this time, the user will be automatically logged out. (1) Refer to Chapter 6 Configuration for details on enabling/disabling security enhancements. (2) Changes that have not been applied (via OK or Apply) prior to the automatic logout will be lost.
5.3.1.5
Craft Interface User Interaction Menus

The Craft Interface provides menu options for selection by the user. Options are available from a main menu and in some instances a main menu item may have a sub-menu available within it. This is indicated by a plus sign (+) to the left of the main menu item. Two methods of selecting menu options exist: key selection numeric selection.
Key Selection
To select an option from the Craft Interface menu, navigate to the appropriate option using the arrow keys or the tab key (see the heading Navigation) and press the Return key. The window or the sub-menu associated with that option will open. To select an option from the Craft Interface menu, select the number that appears to the left of that option. The window or the sub-menu associated with that option will open. Zero (0) will close a previously opened window or sub-menu and will function as the Cancel command button (see the heading Command Buttons, below).
Numeric Selection
Status Windows
A status window will appear upon selection of an option from a Craft Interface menu. The information on a status window is displayed using a series of fields. The fields provided will enable the user to gain information on the operation of the FSP 150 Mx and to input and/or select data that is required for operation (see the heading Field Types below for further information).
Actions are selected via command buttons that are available at the bottom of the status window (see the heading Command Buttons below for further information).
Field Types
The field types that may appear on a status window are: Display only fields, which are provided to display status information. These fields cannot be selected or changed.
57
Selection fields, which are surrounded by square brackets (i.e. []) and are used to indicate to the user: a command button (e.g. [ OK ], [ Cancel ])
a field that can be edited by: direct data input selection of field contents by scrolling through a drop down list of options a field that can be selected by: direct selection of that field selection of a checkbox or toggle button (i.e. [+]).
For details on how to navigate around and select status window fields, refer to the heading Navigation, below.
Command Buttons
The common Command Buttons that may become available on a status window are: OK, which will accept the information in a status window and close the window. Cancel, which will cancel any changes that have been made to the information in the status window and close the window. Refresh, which will read and display the latest values of the fields in the status window. Apply, which will apply any changes that have been made to the information in the status window, without closing the window.
Keyboard Navigation
A number of keys on the PC keyboard can be used to navigate around the Craft Interface menus before option selection and around status windows for field selection and input. The function of the keys available to navigate the Craft Interface menus are outlined below: Table 5-1
Key Return Up arrow Down arrow Tab Right arrow
Keyboard Navigation
Function Select. This key enables the user to select a highlighted menu option and open the appropriate window. Move. These keys enable the user to move up and down (scroll) through Craft Interface menu options to highlight the option required. Expand. This key enables the user to view a sub-menu. If a submenu is available to a main menu item it is indicated by a plus sign (+) to the left of that item. The main menu item must be highlighted before attempting to view its sub-menu. Collapse. This key enables the user to close a sub-menu. A minus sign (-) to the left of a main menu item indicates that the items sub-menu is open. The main menu item must be highlighted before attempting to close the sub-menu.
Left arrow
58
TM
Optical Networking
The same keys are used to navigate around status windows, however, as outlined below, the right and left arrow keys perform a move operation: Table 5-2
Key Return
Keyboard Navigation for Status Windows

Function Select. This key enables the user to select a highlighted field for information input, a highlighted option from an options list or a highlighted command button. Move. These keys enable the user to navigate around the editable fields or command buttons of a status window in order to highlight the field required.
Up arrow Down arrow Right arrow Left arrow Tab
5.3.2
Web Interface
The Web Interface is a menu driven interface, resident as software on the FSP 150Mx/CX NEMI. The interface can be accessed via an internet browser when connected to the FSP 150Mx/CX via an Ethernet connection. Internet Browsers supported by the Web Interface include: Internet Explorer 6.0 or later Netscape Version 6.0 or later Mozilla Firefox 0.9.1 or later. Before using the Web Interface refer Section 5.3.2.1 Web Interface Access Requirements.
5.3.2.1
Web Interface Access Requirements

Access to the web must first be enabled via the NEMI management interface prior to using the Web Interface (see Chapter 6 Configuration, Section 6.5.2.1 Enabling/Disabling External Access for further details). Commands from the internet browser are authenticated by a per-session cookie (i.e. a cookie that is not stored permanently). Ensure that the internet browser is configured to accept such cookies, as follows: In MS Internet Explorer, select Tools and then Internet Options.... On the Internet Options window, ensure that the tab Privacy is selected and then select the command button Advanced.... Select Override automatic cookie handling and then the tick box Always allow session cookies. In Netscape, select Edit and then Preferences.... Then select the command button Advanced....
In addition, ensure that scripting is enabled. In MS Internet Explorer, select Tools and then Internet Options.... On the Internet Options window, ensure that the tab Security is selected and then select the command button Custom Level.... Scroll down to Scripting, Active scripting and then select Enable.
59
5.3.2.2
Accessing the Web Interface

The FSP 150 Installation Guide provides detailed information on connecting to the FSP 150CMx/CX NEMI and accessing the Web Interface. To access the Web Interface perform the following steps:
Step 1 Step 2
Ensure that a connection from a local PC or laptop to the near end FSP 150Mx/ CX NEMI has been established, as required. Open up the appropriate Internet Browser and enter the following: http://xxx.xxx.xxx.xxx were xxx.xxx.xxx.xxx is the IP address of the NEMI that is being connected to. The Web Interface will open and the Login Screen will be displayed, as shown below:
Step 3
Login as appropriate and select OK. The following message will be displayed.
The FSP 150Mx/CX Main Menu will be displayed to the left of the screen. Details of the options provided by the Web Interface Main Menu can be found in Section 5.3.3 Craft/Web Interface Menu Structure. Details on how to interact with the Web Interface can be found in Section 5.3.2.5 Web Interface User Interaction.
5.3.2.3
Exiting the Web Interface

To exit the Web Interface perform the following steps:
Step 1 Step 2
Logout of the Web Interface by selecting Logout from the FSP 150Mx/CX Main Menu. Close the Internet Browser, as normal.
60
TM
Optical Networking
5.3.2.4
Automatic Logout
If the user has enabled security enhancements, the Web Interface will enforce a timeout limit of fifteen minutes. If there is no server activity during this time, the user will be automatically logged out. (1) Refer to Chapter 6 Configuration for details on enabling/disabling security enhancements. (2) Changes that have not been applied (via OK or Apply) prior to the automatic logout will be lost.
5.3.2.5
Web Interface User Interaction

The user may manage the FSP 150Mx/CX in a simple and intuitive way via the point and click Graphical User Interface (GUI).
Menus
The Web Interface provides menu options for selection by the user. Options are available from a main menu and in some instances a main menu item may have a sub-menu available within it. This is indicated by a red arrow sign (>) to the left of the main menu item. Menu options are selected by pointing and clicking with the mouse. When a menu option is selected, the appropriate status window will appear in the main window to the right.
Status Windows
A status window will appear upon selection of an option from the menu. The information on a status window is displayed using a series of fields. The fields provided will enable the user to gain information on the operation of the FSP 150Mx/CX and to input and/or select data that is required for operation (see the heading Field Types below for further information). Actions are selected via command buttons that are available at the bottom of the status window (see the heading Command Buttons below for further information).
Field Types
The field types that may appear on a status window are: Display only fields, which are provided to display status information. These fields cannot be selected or changed. Editable fields, that can be edited by: direct data input selection of field contents by scrolling through a drop down list of options
Selection fields, that can be selected by: selection of a tickbox (i.e. ) ).
selection of a toggle button (i.e.
61
To navigate around and select status window fields, point and click with the Mouse as normal.
Command Buttons
The common Command Buttons that may become available on a status window are: OK, which will accept the information in a status window and close the window. Cancel, which will cancel any changes that have been made to the information in the status window and close the window. Refresh, which will read and display the latest values of the fields in the status window. Apply, which will apply any changes that have been made to the information in the status window, without closing the window.
To select Command Buttons, point and click with the Mouse as normal.
5.3.3
Craft/Web Interface Menu Structure

The structure of both the Craft and Web Interface menu system is shown in Figure 5-1.
62
TM
Optical Networking
Manager configuration
IPv4 configuration
Addresses Routing Inband VLAN
Hostname DNS configuration Domain Servers Date and time SNMP settings General Communities Trap Recipients Alarm severity settings External access Users NEMI Mode Inventory Config Mgmt Logging Configuration View Logfile Node configuration Current alarms Chassis configuration Config Status Inventory Node Running Unit configuration OAM Reboot Protection Multicast (FSP 150MG only) Status Counters General RADIUS configuration Security Enhancements IP Filter
PID Translation PSUs and Fans
Configuration Status
Traffic Test Upgrade node firmware Config Mgmt
Ingress Egress
Generator Filter Statistics
Auto
Config Ingress Statistics
Ports
Egress Statistics General Counters (Network and Access Ports only) Inventory (Network and Access Ports only) Config Statistics (Network Ports only) Remote Loopback
aux
Status General Configuration
dcn
access-n
OAM
network-n
Manager actions
Upgrade NEMI software File Mgmt Run CLI (Craft Interface only) Reboot NEMI
Ring
Config Running Table Saved Table
Traffic Mgmt
Regulators (Access Ports only) Priority (Access Ports only)
Logout
Figure 5-1: Craft/Web Interface Menu Structure
63
5.4
Command Line Interface

The CLI is a command-driven interface, resident as software on the FSP 150Mx/ CX NEMI. It can be accessed using the protocols Telnet or SSH via an Ethernet connection.
5.4.1
Command Line Interface Access Requirements

Access to the FSP 150Mx/CX NEMI can be obtained via the protocol SSH or Telnet application via an Ethernet connection. See the FSP 150 Installation Guide for connection details.
5.4.2
Accessing the Command Line Interface

The FSP 150 Installation Guide provides detailed information on connecting to the FSP 150Mx NEMI and accessing the CLI. To enter the CLI perform the following steps:
Step 1 Step 1
Ensure that a connection from a local PC, laptop or VT100 terminal to the FSP 150Mx NEMI has been established, as required. Start the Telnet or SSH program and log in for access to the CLI. The Top Mode prompt (top>) will be displayed as shown below and as described in Section 5.4.4 Modes of Operation.
5.4.3
Exiting the Command Line Interface

To exit the CLI at any mode type quit and then press <Enter>. The CLI will be closed along with the terminal emulation window.
64
TM
Optical Networking
5.4.4
5.4.4.1
Modes of Operation
Command Modes
A number of operation modes are provided by the CLI which are accessed via a hierarchical route from the Top Mode prompt (i.e. top>). When the user is operating in a specific mode, only commands appropriate to that mode are available for use. Figure 5-2 illustrates the mode hierarchy and the headings that follow provide a brief description of each main mode.
Login Mode (login>)
Top Mode (top>)
Manager Mode (mgr>)
Node Mode (node>)
Figure 5-2: Command Line Interface Mode Hierarchy Login Mode

The login mode is the point of entry to the CLI. In this mode the user is prompted for a user account name and password and correct login details will grant unrestricted access to the CLI.
Top Mode
When the user has logged in successfully, the Top Mode will be entered and the following prompt will be displayed: top> This mode is the highest in the hierarchy and all sub-modes are reached from here. In the Top Mode the user may:
move to manager mode move to node mode move to file management mode ping a Network Management System (NMS) to ensure correct connection start the Craft Interface
65
Manager Mode
The Manager Mode is reached via the Top Mode by typing mgr and then pressing <Enter> at the top> prompt. When it is entered the following prompt will be displayed: mgr> The operation of the NEMI and its configuration is controlled in Manager Mode. In this mode the user may perform the following: configure/view general settings, access control, traffic services, protection and traffic management. perform IP configuration for correct connection between the NEMI and a NMS via the Management ports configure management via SNMP set the NEMI time and date reboot the NEMI save management configuration settings upgrade NEMI software.
Node Mode
The Node Mode is reached via the Top Mode by typing node and then pressing <Enter> at the top> prompt, and when it is entered the following prompt will be displayed: node> All nodes managed by the NEMI may be reached from here by inputting the serial number of the node required. Typing node ? at the top> prompt will display the serial numbers and user strings of all the nodes managed. The operation of a specific node and its configuration is controlled in Node Mode. In this mode the user may configure and view parameters on the operation of the following: the Chassis, where the user may: configure chassis thresholds reset the chassis
view chassis operating status, e.g. current temperature and rail voltages view chassis product information, e.g part number and serial number.
each Port/Interface, where the user may: configure required port operation and loopbacks view current port operation view port statistics.
66
TM
Optical Networking
the Unit (i.e. the FSP 150Mx as a logical entity), where the user may: configure unit operation perform a traffic test view current unit operation view unit statistics.
a FSP 150 Customer Premise (FSP 150CP) that is attached to the FSP 150Mx/ CX via any one of the Access ports. In this instance the user may: configure chassis, port and system parameters view chassis, port and system operation save management configuration settings on the FSP 150CP upgrade FSP 150CP NEMI firmware.
In addition, the user may: save node configuration settings upgrade node firmware.
5.4.4.2
Navigating Modes Entering and Exiting Modes

To enter a particular mode, type the name of the mode and then press <Enter>. The prompt will change to reflect the mode entered, e.g.: top> node <Enter> node> To exit a mode press Ctrl D, e.g.: mgr configure access> <Ctrl D> top> or type exit followed by <Enter> e.g.: mgr configure access> exit top>
Implicit Mode Entry

When entering commands in the Top Mode, the user may type an entire command which includes access to another mode, e.g.: top> mgr configure access ssh init top> mgr configure access ssh on top>
Alternatively, the user may enter a mode, equivalent to a common part of each command line entered. This enables the user to enter a sequence of similar commands faster, e.g.: top> mgr configure access mgr configure access> ssh init mgr configure access> ssh on mgr configure access> exit top>
67
5.4.5
5.4.5.1
Node Connection
FSP 150Mx/CX Nodes
It is possible to connect to and manage local and remote FSP 150Mx/CX nodes (without a NEMI) in the same CLI session and from the same NEMI by connecting to the nodes using the node command in Top Mode. It is possible to connect: to a local FSP 150Mx/CX node to another remote FSP 150Mx/CX node: in a FSP 150 tree in a FSP 150 ring or chain
within a FSP 150CX to the Upper Board.
Typing node ? at the top> prompt will display details of all accessible nodes (see Section 5.4.5.3 Node Topology Display). At the Top Mode prompt (i.e. top>), connect to a node by entering the following command: node <serial number> where <serial number> is the serial number of the FSP 150Mx/CX node. When a connection has been made to a node, that node may be managed by the NEMI using the commands available to the Node Mode (see Section 5.4.4.1 Command Modes).
5.4.5.2
FSP 150CP Nodes

It is possible to manage FSP 150CP units further down a FSP 150 tree in the same CLI session and from the same NEMI by connecting to the FSP 150CP nodes using the node command in Top Mode. Typing node ? at the top> prompt will display details of all accessible nodes (see Section 5.4.5.3 Node Topology Display). At the Top Mode prompt (i.e. top>), connect to a FSP 150CP node by entering the following command: node <serial number> where <serial number> is the serial number of the FSP 150CP node. When a connection has been made to a FSP 150CP node, that node may be managed by the FSP 150Mx/CX NEMI using the commands available to the Node Mode (see Section 5.4.4.1 Command Modes).
68
TM
Optical Networking
5.4.5.3
Node Topology Display

A facility is provided which will display topology information on how nodes are connected. The following details are given for all accessible nodes connected to the top node: Node serial number Management path Product type Chassis user string. At the Top Mode prompt (i.e. top>) enter the following command: node ? Information for all accessible nodes connected to the top node will be displayed, for e.g.: EN00000 top FSP150MG topMG1 EN01111 top.accl FSP150ME nodeME1 EN02222 top.up.acc2.ringNode2 FSP150ME nodeME2 FA111102222 top.acc2.ringNode3.acc2 FSP150CP nodeCP1 EN04444 top.acc3.acc2 FSP150MO nodeMO2
5.4.6
Help
Facilities are provided for help in entering and completing CLI commands as outlined in the following sections. The commands given in the following sections are provided for illustration purposes only and are not available to the CLI.
5.4.6.1
Command Completion
Completion of a command can be invoked by pressing the <tab> key, as the following examples illustrate: With the following commands available: mgr configure mgr show mgr save If the user enters: mgr c<tab> and, as in this case, there is only one command that matches, the result of the completion would be: mgr configure
69
If the user enters: mgr s<tab> and there are more than one command that matches, all the possible commands in the context will be displayed: mgr show mgr save
5.4.6.2
Command Abbreviation
It is possible to abbreviate a command or mode, as long as there is no ambiguity. For example, given the following commands: configure syslog server add <server> configure syslog server delete <server> configure syslog severity <severity> The following sequence would represent an unambiguous command as only one command starts with sev: config sys sev However, the following sequence would result in ambiguity, as two commands start with serv: config sys serv
5.4.6.3
Context Sensitive Help

It is possible to display the commands that are applicable to a particular context. For example, given the following mode: node FA70052802040> Press <tab> and all the possible commands in the node context will be displayed across the screen: port save unit show chassis upgrade
A question mark (?) will provide the same functionality as pressing <tab>, however, a short help text is written alongside each command printed: port unit chassis upgrade save show Port specific configuration Unit specification configuration Chassis specific configuration Upgrade node firmware Save running configuration Show node information
5.4.7
Copyright Statements
A command is provided in the CLI to obtain the relevant NEMI software copyright statements.
70
TM
Optical Networking
Show the copyright statements, by entering the following command at the Top Mode prompt (i.e. top>): mgr show copyright
5.4.8
Command Structure
Figure 5-5 below illustrates the command structure of the CLI.
mgr ping Tests a connection to a remote unit node <serial number> of local or remote node craft Launches local craft management interface show forwardmode linkloss-forwarding loopback remote loopback media mode oam neighbor priority regulators ring sfp shapers statistics tagmode translation userstring multicast IGMP-VLAN-tag multicast file-mgmt
configure
access dns ipv4 ip-filter nemi-mode nodename radius security-enhancements snmp terminal time user logging
port
configure forwardmode linkloss-forwarding loopback media mode oam priority regulators remote ring shapers tagmode translation userstring statistics multicast IGMP-VLAN-tag multicast
clone delete upload download show
show
access copyright dns ip-filter ipv4 nemi-mode nodename product radius security-enhancements snmp terminal time users version logging logfile
unit
configure egress-arrivalmode hsrp-forwarding ingress-departuremode jumboframe linkloss-forwarding ringid oam protection reboot-traffic tagid tandemmode traffic-mgmt translation vrrp-forwarding traffic-test statistics multicast
show controller forwarding hsrp-forwarding jumboframe linkloss-forwarding traffic-test oam protection reboot-traffic statistics tagid tandemmode traffic-mgmt translation uptime vrrp-forwarding ringid multicast
upgrade
software cancel now status
reboot
networkports
configure show
ipv4 inband-vlan
aux-port
configure show
ipv4
dcn-port
configure show
ipv4
chassis
configure threshold userstring
reset
show product railvoltage serialnumber status temperature threshold userstring
cfg-mgmt
save backup activate factory-default show
users interfaces system status backup active running
upgrade
firmware
show
version save backup activate factory-default show status backup active running
cfg-mgmt
Figure 5-3: CLI Command Structure

FSP 150Mx/CX User Guide 71
5.4.9
Command Summary
The following sections provide a brief summary of the commands that are available for use in the CLI via the Top Mode. (1) All commands are lower case sensitive. (2) The command exit is available at every stage, but is not described here. Refer to Section 5.4.4.2 Navigating Modes, Entering and Exiting Modes for details of this command. (3) Help is available at every stage, but is not described here. Refer to Section 5.4.6 Help for details. (4) The command quit is available at every stage, but is not described here. Refer to Section 5.4.3 Exiting the Command Line Interface for details of this command.
5.4.9.1
mgr (Manager Mode) 5.4.9.1.1 mgr configure

This command has the following parameters:
access>
ssh>
Enable/Disable and initialize SSH. init on/off Initialize SSH encryption keys. Turn on/off SSH. Turn on/off telnet. Turn on web access. Set domain name. <ipv4address>
telnet> www> dns>
on/off on/off
Set DNS configuration for the NEMI. domain> server> <domainname> Add or delete a DNS server. add/delete
ipv4>
Set IPv4 Router configuration for the NEMI. route> add/delete> <ipv4address>/<prefix> default> <gateway>
ip-filter>
create/delete>
create/Delete an access list. list>
<access-list-name> allow ipv4/disallow ipv4.
list>
Add/Delete IP subnet to/from access list. <name>
attach/detach service> nemi-mode> nodename> radius> active/passive <nodename>
Attach/Detach a service to/from an access list. sss/www/snmp/telnet Sets the node as the active/passive node. Set Node Name for the NEMI. Configures an alternative RADIUS server with port, secret and server as described below. <attempts> Configure the number of authentication attempts.
Enables/Disables RADIUS support and sets RADIUS configuration.
alternative> attempts> on/off

port>
Enables/Disables use of an alternative RADIUS server. <port> Sets the port number for communicating with the RADIUS server.
72
TM
Optical Networking
secret> server> timeout> securityenhancements> snmp> on/off
<secret> <server> <seconds>
Specifies the shared secret used between the FSP 150Mx and the RADIUS server. Sets the IPv4 address of the alternative RADIUS server. Configures how long an attempt will last before timeout.
Enable/disable security enhancements.
Enables the user to set the Read/Write Communities and the Trap Recipient Address(es). getcommunity> on/off restart setcommunity> syscontact> syslocation> trapsink> <getcommunity> Turn snmp on/off. Restarts the SNMP agent. <setcommunity> <syscontact> <syslocation> add/delete> Specifies the community allowed to perform Set commands. Set the system contact. Set the system location. Add/Delete trap sink address. <trapsink> trapsource> <trapsource> Set the trap source address. Where <rows> is the number of rows displayed at any one time. Set the emulated terminal type. Where <type> can be set to: dumb, vt100, vt220 and xterm. Configure the terminal emulation. rows type <rows> <type> Specifies the community allowed to perform Get commands.
terminal>
time user>
<YYYYMMDDhhmmss> Manage user accounts create/remove> lock/unlock> password> Configure audit logging on/off> syslog>
Enables the user to set the time the time of a NEMI so that external events can be analyzed more easily. <username> <username> <username> Create/removes an account. Locks/unlocks a users account. Sets an account password.
logging>
Enable/Disable audit logging. Add/Remove an external server to which log entries are to be sent. add <ip4address> remove <ip4address>
Add a syslog server. Remove a syslog server.

Enable/disable logging to flash memory.
logfile>
on/off maxentries
<number>
Set the maximum number of log entries that are to be logged to flash memory.
73
5.4.9.1.2 mgr show

access copyright dns ip-filter ipv4 nemi-mode nodename product radius security-enhancements snmp terminal time users version logging logfile> <entries> all Show current access configuration and verify the identity of the FSP 150Mx unit. Show NEMI copyright statements. Show current DNS configuration. Show access control ranges. Show current ipv4 router configuration. Show current mode. Show node name configuration. Show NEMI product information. Show the current RADIUS configuration. Show security enhancement setting. Show snmp configuration. Show terminal configuration. Show date and time. Shows all user accounts. Show NEMI management software version. Show the current audit logging configuration. Show logfile entries Show the number of entries to be shown as specified by the user. The last entry will be shown first Show all logfile entries with the last entry shown first.
5.4.9.1.3 mgr upgrade

This command enables you to upgrade the NEMI management software for the node. The syntax is: upgrade software <URL:software image> where: URL is the path to the software file software image is the name of the software file.
5.4.9.1.4 mgr reboot

<time out> cancel now status Set the NEMI to reboot after the specified timeout period.
Cancel a scheduled reboot. Reboot the NEMI. Show when the next NEMI reboot is scheduled.
74
TM
Optical Networking
5.4.9.1.5 mgr network-ports

configure> ipv4 address> Add or delete an IP address for the network ports. add delete inband-vlan> <ipv4address/prefix> <ipv4address>
Configure optional VLAN for inband IP management. on/off Enable/disable VLANtagged inband IP management. <vid> Configure Inband IP VID.
vid show> ipv4> inband-vlan
Show the IP address set for the network ports. Show the VLAN inband IP management configuration.
5.4.9.1.6 mgr aux-port

This command enables IPv4 settings for the aux port to be configured and viewed and has the following parameters:
configure> ipv4 address> Add or delete an IP address for the aux port. add> delete> show> ipv4 <ipv4address/prefix> <ipv4address>
Show the IP Address set for the aux port.
5.4.9.1.7 mgr dcn-port

configure> ipv4 address> Add or delete an IP address for the dcn port. add> delete> show> ipv4 <ipv4address/prefix> <ipv4address>
Show the IP address set for the dcn port.
75
5.4.9.1.8 mgr cfg-mgmt

This command enables NEMI management configuration files to be backed up and restored and has the following parameters:
save> backup> activate> factory-default> users Save / backup / activate / set back to factory defaults the NEMI-Users configuration settings. Save / backup / activate / set back to factory defaults the NEMI-Interfaces configuration settings. Save / backup / activate / set back to factory defaults the NEMI-System configuration settings. Show the current status of the NEMI configuration. Show the backed up / active / running configuration settings.
interfaces
system
show>
status backup active running
5.4.9.2
ping
This command allows you to ping a NMS from the NEMI to test for a connection. The syntax is: ping> <ipv4_addr> where <ipv4_addr> is the IP address of the NEMI.
5.4.9.3
node (Node Mode) 5.4.9.3.1 Connecting to a Node

At the Top Mode prompt (i.e. top>), connect to a node by entering the following command: node <serial number> where <serial number> is the serial number of the node to be connected to.
Typing node ? at the top> prompt will display details of all accessible nodes (see Section 5.4.5.3 Node Topology Display).
This command configures/monitors node ports, and has the following syntax: node <serial number> port <portname> where: <serial number> is the serial number of the node connected to. <portname> can be access-01 to access-10, network-1, network-2 and aux.
76
5.4.9.3.2 node port
TM
Optical Networking
The command has configure and show parameters as described below.:

configure> forwardmode> <mode> (Access Ports only.) Set Access Port Forward Mode. Where <mode> can be set to: network-1, network-2 (Access Ports only.) Set link loss forwarding on the Access Port on or off. (Access and Network Ports only.) Set loopback on or off. (All ports.) Set port Media Mode to a data rate or to auto-negotiation. Where <mode> can be set to: 1000Mbit, 100Mbit, 10Mbit, auto (All ports.) Set port Link Mode where <mode> can be set to: down, up, linkdown, test.
linkloss-forwarding> loopback> media>
on/off on/off <mode>
mode> oam>
<mode>
(Access and Network Ports only.) Enable or disable OAM. info> on/off statistics> on/off Enable/Disable OAM information.
Enable/Disables OAM. clear (Network Ports only.) Clear all performance counters.
priority>
(Access ports only.) Set the Access Port priority. default copy force value Leave the priority value unchanged. Copy the priority value. Overwrite the priority value. Set the priority to a value 0 to 7.
regulators>
(Access ports only.) Set Access Port regulators. cbs Committed burst size. <ingress/egress> <high/medium/low> <size in kB> Committed information rate. <ingress/egress> <high/medium/low> <rate in kbps> Turn remote loopback on/off.
cir
remote>
(Access and Network Ports only.) Set remote loopbacks. loopback> tree on/off (Access ports only.) Configures a remote node to tree node. (Access and Network Ports only.) Start/Stop a ring controller. <rate in kbps> <size in kB> (Access ports only.) Set Access Port Tag Mode to: branch or leaf (Network ports only.) Enables/Disables ID to VLAN translation. (All ports.) Set a userstring for the port. (Access and Network Ports only.) Clear all performance counters.
ring> shapers>
on/off
(Network ports only). Set shaper configuration. ac abs
tagmode> translation> userstring> statistics>
<mode> on/off <user string> clear
77
multicast IGMP-VLAN-tag>
(FSP 150MG Network ports only.) Set the Multicast IGMP VLAN tag mode. unmodified multicast-VLAN both Use an unmodified VLAN tag according to the FSP 150Mx/CX tagging scheme. Use a multicast VLAN tag. Use an unmodified VLAN tag and a multicast VLAN tag in two separate frames. (FSP 150MG Access ports only.) Add/Remove an Access port to/from Egress Multicast.
multicast> show> forwardmode linkloss-forwarding loopback remote loopback media mode oam>
on/off
(Access ports only.) Show forwardmode setting. (Access ports only.) Show linkloss-forwarding setting. (Access and Network ports only.) Show loopback setting. (Access and Network ports only.) Show remote loopback status (All ports.) Show current port Media Mode (Operational speed). Show FSP 150Mx/CX port Media Mode setting (Configured speed). (All ports.) Show current port Link Mode (Operation). Show FSP 150Mx/CX port Link Mode setting (Configuration). statistics status (Network Ports only.) Show OAM statistics. (Access and Network Ports only.) Show OAM status.
neighbor priority regulators ring sfp shapers statistics tagmode translation userstring multicast IGMP-VLAN-tag multicast
(Access and Network ports only.) Shows any connected nodes. (Access ports only.) Shows priority value/settings for that port. (Access ports only.) Shows the traffic regulator settings for that port. (Access and Network ports only.) Shows controller, running-table and saved-table settings. (Access and Network ports only.) Show SFP information. (Network Ports only.) Shows the shaper settings for that port. (Access and Network ports only.) Shows current port statistics. Show FSP 150Mx/ CX port statistics. (Access ports only.) Access ports only. Show tag mode. (Network ports only.) Show translation settings. (All ports.) Shows the userstring set for the selected FSP 150Mx/CX port. (FSP 150MG Network ports only.) Show the Multicast IGMP VLAN tag mode configuration. (FSP 150MG Access ports only.) Show whether Egress Multicast has been activated or not.
5.4.9.3.3 node unit

This command has the following syntax: node <serial number> unit
where <serial number> is the serial number of the node connected to. This command has the following parameters:
configure> egressarrivalmode> hsrpforwarding> ingressdeparturemode> both/network-1/ network-2 on/off both/single Set Egress Arrival Mode. Set HSRP forwarding on or off. Set Ingress Departure Mode.
78
TM
Optical Networking
jumboframe> linklossforwarding>
on/off Sets linkloss-forwarding. on/off point-to-point
Set Jumbo Frames on or off.
Sets linkloss forwarding on or off. Sets the unit to point-to-point mode. On a ring/chain network, configures the ring ID of the unit. <interval> <retries> <pps>
ringid <0-12> oam>
<ringid> Set OAM Parameters. eventretransmit interval eventretransmit tries maxpps
protection>
Sets Network Port protection. type> To Set the protection type to one of the following: none, forceN1, forceN2, layer2, layer3, pointto-point, link-aggregation preferrednetwork> To set the preferred network to one of the following: network-1, network-2 Specifies whether or not to allow traffic during a reboot. Sets the Tag protocol ID. Default=0x8100. Enables/disables tandem mode. Enables/disables traffic management. <pid> Set VRRP forwarding. generator-1> Configures, starts and stops the onboard traffic test. cbs> cir> c-vlan/ s-vlan> <size in kB> Add or delete a port id.
reboot-traffic> tagid> tandemmode> traffic-mgmt> translation>
on/off <tagid> on/off on/off
Sets translation configuration. add/delete> clear Clear all port id translation configurations.
vrrpforwarding> traffic-test>
on/off ingress/egress>
16-4095
<rate in kbps>
0-1048512 Push a customer/ service-VLAN as the first VLAN tag in each test frame.
vid. 0-4094. priority on/off
framecount> framesize> payload>
Set the number of test frames. 0-4294967295. Set the size of each test frame. 64-9250. Set the remaining part of the test frame to one of the following: all-0, all-1, increment, random
79
port>
Assign the component to a port: network-1, network-2 Signature specified in hex or ascii. Start/stop the generator running. Assign the component to a port: access-01 to access-10 Signature specified in hex or ascii. Set the filter action to: drop, pass Set the filter statistics or Clear all counters. Enable/disable the filter.
signature> start/stop filter-1> port>
signature> action> statistics on/off auto-1>
Set the automatic test using one generator and two filters. start/stop statistics port> Start/stop the generator running. Set the filter statistics or Clear all counters. Assign the component to a port: network-1, network-2, access-1 to access-10
statistics> multicast regulators>
clear
Clear all performance counters.
(FSP 150MG only) Set Egress Multicast regulators. cir cbs <rate in kbps> <size in kB> Set Committed Information Rate for Egress Multicast traffic. Set Committed Burst Size for Egress Multicast traffic.
multicast protection> show> controller forwarding hsrp-forwarding jumboframe linklossforwarding traffic-test oam protection reboot-traffic statistics tagid tandemmode traffic-mgmt translation
(FSP 150MG only.) Set multicast protection type to one of the following: same-as-unicast, layer2, layer3, point-to-point, forceN1, forceN2, link-aggregation. Show micro controller status information. Show forwarding status information. Show HSRP forwarding setting. Show Jumbo Frame setting. Show Link Loss Forwarding setting. Show traffic test settings.
Show OAM parameter settings. Show protection settings. Show reboot settings. Show Unit statistics. Show Tag Protocol ID configuration. Show tandemmode. Show configuration of traffic management classification. Show translation settings.
80
TM
Optical Networking
uptime vrrp-forwarding ringid multicast regulators> multicast protection>
Show time since unit boot. Show VRRP forwarding setting. Show the ringid. (FSP 150MG only) Shows Egress Multicast regulators. (FSP 150MG only) shows the configured Egress Multicast protection type and the active network used for multicast traffic.
5.4.9.3.4 node chassis

This command has the following syntax: node <serial number> chassis where <serial number> is the serial number of the node connected to. This command has the following parameters:
configure> Set Chassis rail voltage and temperature thresholds and userstring. threshold> railvoltage> max> min> temperature> userstring reset show> <String> Resets the FSP 150Mx/CX Chassis. Shows the current settings for the chassis. product railvoltage serialnumber status temperature threshold> Show Chassis product information. Show current PSU rail voltages. Show Chassis serial number. Show Chassis operating status. Show Chassis temperature. Show Chassis rail voltage and temperature thresholds. railvoltage temperature> userstring Show Chassis userstring. max> <millivolt> <millivolt> <temperature>
A string to identify the chassis.
5.4.9.3.5 node upgrade

This command enables the firmware for the node to be upgraded. The syntax is: node <serial number> upgrade firmware <URL:firmware image> where:
<serial number> is the serial number of the node connected to URL is the path to the firmware file firmware image is the name of the firmware file.
81
5.4.9.3.6 node show

This command will show the Node firmware version number. The syntax is: node <serial number> show version where <serial number> is the serial number of the node connected to.
5.4.9.3.7 node cfg-mgmt

This command enables Node configuration files to be backed up and restored. The syntax is: node <serial number> cfg-mgmt where <serial number> is the serial number of the node connected to. The command has the following parameters:
save> backup> activate> factory-default> show> Save / backup / activate / set back to factory defaults the running Node configuration settings.
Show the current status of the Node configuration. Show the backed up / active / running configuration settings.
5.4.9.3.8 Connecting to a FSP 150CP Node

This command configures/monitors a FSP 150CP connected to a FSP 150Mx access port, and has the following syntax: node <serial number> where <serial number> is the serial number of the FSP 150CP to be connected to.
Refer to the FSP 150CP User Guide for further details on configuring and monitoring the FSP 150CP. The following command parameters are available when connected to a FSP 150CP:
chassis> configure> Set rail voltage and temperature thresholds on the FSP 150CP Chassis. threshold> railvoltage> max> <millivolt> min> <millivolt> temperature> max> <temperature> userstring> <user defined string> show> product status thresholds Show FSP 150CP Product information. Show FSP 150CP operating status. Show FSP 150CP rail voltage and temperature thresholds.
82
TM
Optical Networking
userstring version port <portname>> configure>
Show the userstring set for the FSP 150CP chassis. Show FSP 150CP hardware and firmware revision.
Where <portname> can be copper-access, fibre-access, network-A or network-B. media> <mode> Set port Media Mode on the FSP 150CP to a data rate or to auto-negotiation. Where <mode> can be set to: 10mbit, 100mbit, 1000mbit, 10mbit halfduplex, 100mbit halfduplex, auto, auto 10mbit, auto 100mbit, auto 1000mbit, auto 10mbit halfduplex, auto 100mbit halfduplex. mode> <mode> Set port Link Mode on the FSP 150CP. Where <mode> can be set to: down, up oam> (Network Ports only.) Enable or disable OAM on the FSP 150CP Network ports. on Enable OAM. off Disable OAM. linkloss-forwarding> (Access Ports only.) Enable or disable linkloss forwarding on the FSP 150CP Access ports. on Enable linkloss forwarding. off Disable linkloss forwarding. userstring <userstring> Set a userstring for the FSP 150CP port. Show FSP 150CP port Media Mode setting (Configured speed). Show current port Media Mode (Operational speed). mode Show FSP 150CP port Link Mode setting (Configuration). Show current port Link Mode (Operation). oam statistics linkloss-forwarding loopback userstring (Network Ports only.) Show OAM setting. Show FSP 150CP port statistics. (Access Ports only.) Show linkloss forwarding setting. (Network Ports only.) Show loopback setting. Show the userstring set for the FSP 150CP port.
show>
media
cfg-mgmt
save> backup> activate> show>
Save / backup / activate / the running Node configuration settings.
Show the current status of the Node configuration. Show the backed up / active / running configuration settings.
show>
running saved
Show the currently running Node configuration settings. Show the saved Node configuration settings.
83
unit>
configure>
Set OAM Parameters on the FSP 150CP. protection> Sets FSP 150CP Network Port protection. type> To Set the protection type to one of the following: automatic, layer2, layer3, point-topoint, forceNA, forceNB vrrp-forwarding> hsrp-forwarding> linkloss-forwarding> on/off on/off point-to-point> Set VRRP forwarding. Set HSRP forwarding. on/off Set Link Loss Forwarding.
show>
forwarding protection>
Show forwarding status information on the FSP 150CP. Show FSP 150CP Network Port protection. type active network Show FSP 150CP Network Port protection setting. Show current active network.
vrrp-forwarding hsrp-forwarding linkloss-forwarding upgrade> Upgrade the firmware of a remote unit. <URL:firmware image>
Show the VRRP forwarding setting. Show the HSRP forwarding setting. Show the Link Loss Forwarding setting.
5.4.9.4
file-mgmt
This command allows configuration backup files to be transferred to and from another system running a FTP or HTTP server and has the following parameters:
clone> delete> upload> download> show>
from <idx> to <idx> <idx> <URL:remote storage file><idx> <URL:remote storage file> status
Clone the Node configuration.

Delete a NEMI or Node configuration with the specified index.
Upload a NEMI or Node configuration, specifying the URL of the remote storage file and the index. Download a NEMI and/or Node configuration, specifying the URL of the remote storage file.
Show the current status of the configuration files.
5.4.9.5
craft
This command launches the Craft Interface and has the following syntax: craft
84
TM
Optical Networking
Chapter
Configuration
6.1 Introduction
6
details on how to access the FSP 150Mx/CX Management Interface. details on how to configure the following: Internet Protocol (IP) date and time secure access Network Element Management Interface (NEMI) mode chassis user strings traffic services Operation, Administration, Maintenance (OAM) and Ethernet First Mile (EFM) protection traffic management fault management.
This chapter provides step by step instructions for configuring the Fiber Service Platform 150 Multiplexer/Hub Node (FSP 150Mx/CX) for traffic services and management purposes. The following information is provided:
details on how to back up configuration settings.
(1) Prior to performing the configuration tasks outlined in this chapter, it is assumed that connection to the NEMI has been made and that the Craft Interface has been entered successfully. If details on connecting to the Craft Interface and logging out are required, refer to Chapter 5 Management Interfaces. (2) This section assumes that the Craft Interface is used to perform FSP 150Mx/ CX configuration, However, the Web Interface or the Command Line Interface (CLI) may be used instead, if preferred. Details on the Web Interface and the CLI are given in Chapter 5 Management Interfaces.
6.2
2563XI07_Ch6_Cfg.fm - 30. October 2007
Initial Access
When no NEMI is present there is no local Management Interface present. All management of an FSP150Mx/CX without NEMI must be done remotely from another FSP 150Mx/CX fitted with NEMI. When the FSP 150Mx/CX is fitted with a NEMI, local management is possible over Ethernet/Internet Protocol v4 (IPv4) via the AUX port. Initially, the AUX port is configured with the link local IPv4 address: IPv4 address: 169.254.0.1 subnetmask: 255.255.255.252.
85
Configuration
This IPv4address is configured at boot time, in addition to any IPv4 address configured via the Management Interface. An unconfigured FSP150Mx/CX can be managed via the AUX port by the Secure Shell (SSH) or Telnet protocol. To manage a local FSP 150Mx/CX:
Step 1 Step 2 Step 3
Configure an Ethernet interface of the management station to IPv4 address 169.254.0.2 with netmask 255.255.255.252. Start a Telnet or SSH application and connect to IPv4 address 169.254.0.1. Login with the default username and password: Username:root Password:ChgMeNOW
Step 4
From the Management Interface IPv4 addresses can be configured for the network ports, the Data Communication Network (DCN) port (MG only), or the AUX port see Section 6.3.1 Configuring Ethernet IP Addresses. To be able to access the FSP 150Mx/CX via any other method than the default AUX port SSH/Telnet, that method must be enabled in the Management Interface.
6.3
Configuring IP Connectivity
The IP connectivity settings influence how the Network Element (NE) is reached so that management can be performed.
6.3.1
Configuring Ethernet IP Addresses

A connection can be made between a Network Management System (NMS) and the NEMI on an Ethernet link via: aux ports, for a direct connection. network ports, for a connection via the Network Interface. dcn ports, for a connection via a DCN. To ensure a reliable connection to the NEMI, the IP address of the management port to be used for communication should first be configured to a unique address compatible with the network it is to be present on.
Step 1
Navigate to the Manager configuration, IPv4 configuration, Addresses.
86
TM
Optical Networking
Step 2
Select Add....
Step 3
Type in an IP address for the Ethernet Management Interface. The IP address should be valid and unique for the network that the FSP 150Mx/CX is connected to. The IP address must be in the format: nnn.nnn.nnn.nnn where nnn is a number 0 to 255. (1) IP addresses are usually assigned by a Network Administrator. (2) Ensure that no two systems are using the same IP address.
Step 4 Step 5
Select a Netmask address from the drop-down list, to be used for the network to which this system is connected. Select an Interface from the list of, network 1 and 2, aux or dcn. Select OK or Apply.
Step 6
6.3.2
Configuring a Connection to a Router

If the NMS is on a different network to that of the FSP 150Mx/CX, the connecting router needs to be known to the NEMI.
87
Configuration
Step 1
Navigate to Manager Routing.
configuration, IPv4
configuration,
Step 2
Select Add...
Check the Default route box to make this route the default route. In parameter Network, if this parameter is not the default route, type in the IP network subnet to be reachable through this route, for example 192.168.10.0. In parameter Netmask, if this parameter is not the default route, select the IP netmask for the subnet to be reachable through this route, for example 255.255.255.0. Select from a dropdown list. In parameter Destination, type in the routers IP address. Select OK or Apply.
Step 6 Step 7
6.3.3
Configuring Inband IP Management

This facility will enable or disable IP access to the NEMI via the FSP 150Mx Network Ports (i.e. inband).
Step 1
Navigate to Manager Inband VLAN.
configuration, IPv4
configuration,
88
TM
Optical Networking
Step 2 Step 3
Enable/disable the VLAN-tagged inband facility at the Enable Inband tick box. Select VID and specify a VLAN identifier (i.e. a number from 1 to 4095) to be used for VLAN-tagged inband IP management. (1) Using a certain VLAN for inband IP will block any user traffic that would otherwise use this VLAN. (2) If a VLAN ID (VID) is used as a Default VID or in a Port ID (PID) Translation (see Section 6.8.7 Configuring PID Translation) the software will prevent it from being used for inband IP and vice versa.
Step 4
Select OK or Apply.
6.3.4
Configuring the Host Name

This facility will set the host (or node) name of the FSP 150Mx chassis.
Step 1
Navigate to Manager configuration, Hostname.
Step 2
Type in a name for the FSP 150Mx/CX. A text string of up to 63 alpha-numeric characters (except spaces and dots) can be input. If a name service is being run, individual host names should be kept consistent with the name server. If not, choose any name. Select OK or Apply.
Step 3
89
Configuration
6.3.5
Configuring the Domain Name System

The Domain Name System (DNS) is the system used in the Internet for translating the names of network nodes into addresses. This configuration will set the domain to which the chassis is to belong and add the DNS to be used.
6.3.5.1
Domain Name
Configure the name of the domain to which the chassis belongs, as follows:
Step 1
Navigate to Manager configuration, DNS configuration, Domain.
Step 2 Step 3 6.3.5.2 DNS Server
Type in the name of the domain to which the chassis belongs. Input a text string of up to 64 alphanumeric characters. Select OK or Apply.
Configure the DNS server to be used in the Internet for translating network node names into addresses.
Step 1
Navigate to Servers.
Manager
configuration,
DNS
configuration,
Step 2 Step 3
Select Add... and add a DNS server as required. Select OK and OK.
90
TM
Optical Networking
6.4
Configuring Date and Time

It is common practice in enterprise networks to synchronize system clocks and in the case of FSP 150Mx/CX, external events can be analyzed more easily, when the clocks of all NEMIs are synchronized to ensure consistent error reporting across multiple units. For the FSP 150Mx/CX to operate more effectively the correct date, time and timezone should be set on each NEMI. To set the date and time perform the following:
Step 1
Navigate to Manager configuration, Date and time.
Type in the local date in the format dd/mm/yyyy. Type in the current local time in the format hh:mm:ss (on a 24h clock). Select OK or Apply.
6.5
Configuring Secure Access

Unauthorized access to the NE is avoided by using security mechanisms at several levels. This includes authentication of data origin, operators, access privileges and standard protocols for secure communication and file transfer.
6.5.1
Configuring SNMP
Simple Network Management Protocol (SNMP) management applications use the SNMP protocol to communicate with the NE. This protocol must use a specified community to authenticate itself and gain access to the NE. This facility will enable or disable the SNMP agent. If using the SNMP agent at least one trap recipient must be defined before SNMP traps can be sent across a management network. In addition, community strings must be configured so that the SNMP Get (Read) and Set (Write) messages can be authenticated.
91
Configuration
6.5.1.1
Enabling/Disabling SNMP Agent

This facility will enable or disable the SNMP agent.
Step 1
Navigate to Manager configuration, SNMP settings, General.
Step 2 Step 3
In the parameter Enable SNMP agent, enable or disable as required. In the parameter Trap source IP Address, type in the IP address that will appear as the source IP address in the SNMP traps emitted by the SNMP agent. Select OK or Apply.
Step 4 6.5.1.2
Configuring a Contact and Location Name

The FSP 150Mx/CX provides parameters to provide a contact and location name. These are reported as sysContact and sysLocation in the System Management Information Base (MIB) (RFC 1213).
Step 1
Navigate to Manager configuration, SNMP settings, General.
Step 2
Type in a System Contact name, up to 128 alpha-numeric characters long. This will identify the contact person for the system, together with information on how to contact them. Type in a System Location name, up to 128 alphanumeric characters long. This will provide the location of the FSP 150Mx/CX.
Step 3
92
TM
Optical Networking
Step 4 6.5.1.3
Select OK or Apply.
Configuring SNMP Communities

This facility enables the user to set the Read/Write (or Get/Set) or the Read-Only (get) Communities used for authentication.
Step 1
Navigate to Manager Communities.
configuration,
SNMP
settings,
Step 2 Step 3 Step 4 6.5.1.4
In the parameter Get Community, type in the name of the community, up to 64 alpha-numeric characters. This will allow SNMP Read Only requests. In the parameter Set Community, type in the name of the community, up to 64 alpha-numeric characters. This will allow SNMP Write requests. Select OK or Apply.
Configuring Trap Recipients Step 1

Navigate to Manager Recipients. configuration, SNMP settings, Trap
Step 2
Select Add....
93
Configuration
Step 3 Step 4 Step 5 Step 6
In the parameter Host, type in the IP address of the NMS device that is to receive SNMP traps. In the parameter Trap Community, specify a name for the SNMP Community, up to 17 alphanumeric characters, which appears in the traps. Select OK or Apply. Reboot the NEMI. Refer to Chapter 9, Section 9.4.1 Rebooting the NEMI.
6.5.2
6.5.2.1
Configuring Secure External Access

Enabling/Disabling External Access
The FSP 150Mx/CX supports secure communication via the SSH protocol and the less secure protocols Hypertext Transfer Protocol (HTTP) and Telnet. This facility enables the required protocol to be enabled/disabled. The use of the Remote Authentication Dial In User Service (RADIUS, as specified in RFC 2865) may be enabled/disabled. This enables usernames and passwords to be verified using the RADIUS to authenticate users with a server. Here user details are sent to a server for verification and the server will then send a reply indicating whether the user should have access to the system or not. If no reply is received, a Local Password File is used. The servers used for verification can be configured as outlined in Section 6.5.2.2 Configuring RADIUS Servers. During NEMI access via the SSH, encryption keys are used to provide secure encrypted communication and avoid unauthorized access to the FSP 150Mx/CX unit. Each FSP 150Mx/CX has a unique set of keys which are automatically created. SSH Fingerprints act as checksums which are used to compare the public keys of the FSP 150Mx/CX and thereby, verify the identity of the FSP 150Mx/CX unit.
Step 1
Navigate to Manager configuration, External Access, General.
Step 2 Step 3
Enable or Disable the required SSH, Web, Telnet authentication service, as required. Select OK or Apply.
or RADIUS
94
TM
Optical Networking
6.5.2.2
Configuring RADIUS Servers

In order to use RADIUS authentication (see Section 6.5.2.1 Enabling/Disabling External Access), RADIUS servers must be available and the FSP 150Mx/CX must be configured to use them.
Step 1
Navigate to Manager configuration, External access, RADIUS configuration.
Step 2 Step 3
In the parameter IP address, type in the IP address of the RADIUS server. In the parameter Port, type in the User Datagram Protocol (UDP) port number used to communicate with the RADIUS server. The officially assigned port number for RADIUS is 1812. In the parameter Shared secret, type in a string to serve as the shared secret. This is a string of up to 64 alpha-numeric characters and is configured and known to both systems. It is then used to compute and verify message checksums to encrypt the passwords contained in a message before being sent over the network. If an additional server is required, check the parameter Enable alternative server, and type in the IP address, port and shared secret for the alternative server. In the parameter Number of authentication attempts, type in a number for the number of attempts to be performed before a request is terminated. The default is 2. In the parameter Authentication timeout (seconds), type in the number of seconds a request will be allowed to continue without a response. Select OK or Apply.
Step 4
Step 5
Step 6
Step 7 Step 8 6.5.2.3

Enabling/Disabling Security Enhancements

When security enhancements are enabled a timeout limit of fifteen minutes will be enforced. If there is no activity during this time, the user will be automatically logged out.
95
Configuration
Changes that have not been applied (via OK or Apply) prior to the automatic logout will be lost. In addition, the number of failed login attempts and the last successful login time will be displayed after login has been completed.
Step 1
Navigate to Manager configuration, External access, Security Enhancements.
Step 2 Step 3
Enabled/Disable security enhancements, as required. Select OK or Apply. For the security enhancements configuration to fully take effect, the user must logout, close all connections and login again. For the configuration to take effect on remotely connected units, a reboot is required.
6.5.2.4
Configuring Access Control Lists

The Access Control List (ACL) feature allows incoming IPv4 packets to be filtered. The filtering is based on the service (i.e. the destination UDP or Transmission Control Protocol (TCP) port) and the source IP address. The filtering applies regardless of the IP interface through which a packet is received. ACL will allow Internet Control Message Protocol (ICMP) Echo Request and Reply (ping) messages to be sent, but will block all other ICMP messages. Each UDP/TCP service is assigned a filter list, which is a list of IP subnets. The service then can only be accessed from IP addresses within one of the subnets in the list. All other services and IPv4 protocols are blocked. ACLs are based on mappings between the following external access services and IP subnets: SSH SNMP Web (or HTTP) Telnet.
96
TM
Optical Networking
Each service has an associated control list. The following control lists are supported: allow-all, a predefined list which allows all connections irrespective of their source address block-all, a predefined list which denies all connections irrespective of their source address User-configurable lists. A user-configured list will have one or more IP address ranges, and only a request from an IP address within a defined range is allowed access. (See the heading Adding User-Configurable Access Control Lists for details on creating a ACL.)
See the heading Attaching an Access Control List to an External Access Service for details on how to map attached services to an ACL.
Adding User-Configurable Access Control Lists

To add and define an ACL perform the following:
Step 1
Navigate to Manager Filter
configuration, External
access, IP
Step 2
Select Add filter list...
Step 3 Step 4
In the parameter List Name, type in an identifiable name for the filter. Use only alphabetical characters a to z (in any case). Spaces are not allowed. Select OK. This will add the new filter list to the table. Select the new filter list and press Return.
Step 5
97
Configuration
Step 6
Select Add network....
In the parameter IP, type in the IP address that is to be filtered on. In the parameter Netmask, select the required subnet for the range. Select OK. The range is now added to the list. Repeat for other ranges as required. To delete a filter list select the list from the ACL window and select the command button Delete List and then OK.
6.5.2.5
Attaching an Access Control List to an External Access Service

To attach an ACL to a service perform the following:
Step 1
Navigate to Manager Filter.
configuration, External
access, IP
Step 2 Step 3
Navigate to the required Attached Service and select the required ACL (or filter list) from the drop-down list. Map other services as required.
98
TM
Optical Networking
Step 4
Select Apply and OK.
6.5.3
Configuring Users
In order to avoid unauthorized access, the user must log on to the FSP 150Mx/ CX management interface. Each user has a unique name for identification and a password for authentication. Each user is also assigned to a specific security level, defining the users rights. The following security levels are provided: superuser, which has access rights to the entire functionality of the management interface. Upon initial logon, this is the security level for the default user. admin, which has the same rights as the superuser, with the exception of adding or deleting a user. monitor, which provides read-only access rights to NE information.
6.5.3.1
Adding Users Step 1

Navigate to Manager configuration, Users.
Step 2
Select Add....
99
Configuration
Step 3
In the parameter User name, type in a name unique to the user pool. The following rules apply: a minimum of 8 characters a mix of upper and lower case alphanumeric characters or an underscore (i.e, a to z, A to X, 0 to 9 and _ )
Step 4
In the parameter User type select a user type from the drop-down list of superuser, admin or monitor. These provide the following security levels: superuser, has access rights to the entire functionality of the management interface. This is the security level for the root user. admin, has the same rights as the superuser, with the exception of adding or deleting a user. monitor, provides read-only access rights to NE information.
Step 5 Step 6
Select OK. From the Users list, select the user name that has been created, input a password as required and select OK. When creating a password, the following rules apply: all passwords must be 8 to 32 characters long and contain a mix of upper and lower case alphanumeric characters. At least one numeric character must be present. the password cannot be the same as the username. the password must not be "password" (irrespective of case). the password must not be passw0rd" (irrespective of case). no more than 2 letters or digits must be repeated in consecutive character positions. a sequence of adjacent letters or numbers is not allowed at the start or end of the password (e.g. 12345A, 1ABCDE).
6.5.3.2
Changing Passwords Step 1

100
TM
Optical Networking
Step 2
From the Users list, select the user name required.
Step 3
Input a password as required and select OK. When creating a password, the following rules apply: all passwords must be 8 to 32 characters long and contain a mix of upper and lower case alphanumeric characters. At least one numeric character must be present. the password cannot be the same as the username. the password must not be "password" (irrespective of case). the password must not be passw0rd" (irrespective of case). no more than 2 letters or digits must be repeated in consecutive character positions. a sequence of adjacent letters or numbers is not allowed at the start or end of the password (e.g. 12345A, 1ABCDE).
6.5.3.3
Deleting Users Step 1

Step 2
101
Configuration
Step 3 6.5.3.4
Select Delete user.
Locking/Unlocking a User Account Step 1

Step 2
Step 3
Select Lock account/Unlock account as required.
102
TM
Optical Networking
6.6
Configuring Active/Passive NEMI Mode (Mx only)

Step 1
Navigate to Manager configuration, NEMI Mode.
Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8
Select Passive. Select OK or Apply. Save the node configuration. Refer to Section 6.15 Backing Up Configuration Settings. Set the node intended to be the active node to Active. Save the node configuration. Refer to Section 6.15 Backing Up Configuration Settings. Reboot the passive node. Refer to Chapter 9, Section 9.4 Rebooting and Resetting. Reboot the active node. Two nodes should now be in tandem, one as active, the other as passive.
6.7
Configuring Chassis User Strings

The FSP 150Mx/CX provides a chassis user string of up to 40 alpha-numeric characters to provide information for management purposes. They are not interpreted or used by the NEMI.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Chassis configuration, Config.
103
Configuration
Step 3 Step 4
In the parameter User String 1 (Alias) type in the required text. Select OK or Apply.
6.8
6.8.1
Configuring Traffic Services

Enabling/Disabling Ring or Chain Support (Mx only)
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Ports and select the required access or network port and select Ring, Config.
Step 3 Step 4
In the parameter Ring, select either On or Off. Select OK or Apply. If a ring controller is to be started on a network port, a Ring ID must first be added to the local node (i.e. the node with NEMI) on which the ring controller shall start. Configure a Ring ID on the Unit Configuration, Running window (see Section 6.8.2 Configuring a Ring ID).
6.8.2
Configuring a Ring ID
Step 1 Step 2
Navigate to Node configuration and select the required node. Select Unit Configuration, Running.
104
TM
Optical Networking
Step 3 Step 4
In the parameter Ring ID, select the ID required Select OK or Apply.
6.8.3
Configuring Arrival/Departure Mode

This facility configures the way each unit receives and transmits traffic from/to the Network Interfaces.
Step 1 Step 2
Step 3
The parameter Egress-Arrival Mode defines how traffic is received from the Network ports into the unit. Select one of the following: Both, traffic to be received from both Network ports. network-1, traffic to be received from Network port A only. network-2, traffic to be received from Network port B only. If protection is to be enabled this parameter must be set to Both.
Step 4
The parameter Ingress-Departure Mode defines how traffic is transmitted to the Network ports from the unit. Select one of the following: Both, traffic to be transmitted to both Network ports. Single, traffic to be transmitted to a single Network port. If protection is to be enabled this must be set to Both. The network port to use is configured on a per access port basis. E.g. when configured to single access ports, ports 1 to 5 can be configured to transmit user data via network-1 and ports 6 to 10 can be configured to transmit data via network-2.
Note
Step 5
Select OK or Apply.
6.8.4
Enabling/Disabling Jumbo Frames

Jumbo Frames are frames of a maximum 9250 bytes. This facility is used to enable or disable support for Jumbo Frames.
Step 1
Navigate to Node configuration and select the required node.
105
Configuration
Step 2
Navigate to Unit configuration, Running.
Step 3 Step 4
In the parameter Jumbo frames select either On or Off. Select OK or Apply.
6.8.5
6.8.5.1
Configuring Port Services

Enabling/Disabling a Port
This will enable the link mode of a particular port to be configured to indicate whether the port interface is ready for data traffic or not. There are four possible states: 1 2 3 4 Up, the port is active and available to send or receive traffic Down, the port will not forward any traffic except EFM-OAM packages. Link down, forces the physical link down. Testing, reported when the port currently is being used for loopback testing.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Ports and select the required port. Select General Configuration. The screen below shows the access port as an example.
106
TM
Optical Networking
Step 3 Step 4 6.8.5.2
In the parameter Admin Status (Administrative Status), select the required option. Select OK or Apply.
Enabling/Disabling Full Duplex (AUX and DCN ports only)

The AUX and DCN ports support both half duplex and full duplex. Half duplex is a feature for communicating with systems that only run at half-duplex.
Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports, navigate to the required port and select General Configuration.
Step 3 Step 4 6.8.5.3
Enable or disable the Full Duplex parameter. Select OK or Apply.
Enabling/Disabling Auto Negotiation

When auto negotiation is enabled, the port will auto negotiate duplex mode and data rate with other devices for optimum common performance. If auto negotiation is not used, the user should select a data rate (see Section 6.8.5.4 Configuring the Port Data Rate).
Step 1 Step 2
107
Configuration
Step 3 Step 4 6.8.5.4
Select or de-select the Auto Negotiation parameter to enable or disable the service. Select OK or Apply.
Configuring the Port Data Rate

If Auto Negotiation is disabled (see Section 6.8.5.3 Enabling/Disabling Auto Negotiation), the port should be set to operate at a particular data rate.
Step 1 Step 2
Step 3
In the parameter Data Rate, select the required rate (in Mbit/s) from the drop-down list provided. The following values are possible:
Unit MO ME MG CX Access Port 100 BaseX 10/100 BaseT 1000 BaseX 10/100 BaseT Network Port 100/1000 BaseX 100/1000 BaseX 100/1000 BaseX 10/100 BaseX
Note: For 1000 Base X operations, auto negotiation advertising is mandatory. In this case, the network port value becomes auto.
108
TM
Optical Networking
Step 4 6.8.5.5
Select OK or Apply.
Configuring Traffic Forwarding on an Access Port Step 1 Step 2

Navigate to Node configuration and select the required node. Navigate to Ports and select the required access port. Select General Configuration.
Step 3 Step 4 6.8.5.6
For the parameter Forwarding mode, select the required network port. Select OK or Apply.
Configuring Tag Mode on an Access Port

In a tree topology, the FSP 150 Mx/CX access ports may be connected to another FSP 150Mx/CX or another device. When connected to another FSP 150Mx/CX, the VLAN tag needs to be modified for routing requirements. When connected to another device a VLAN tag is added. Parameters Branch and Leaf are used to specify how the FSP 150MX will handle the VLAN tag decision. When an access port of an FSP 150Mx/CX is connected to a network port of another FSP 150Mx/CX the outer most VLAN tag is modified to reflect the arriving access port. This behavior is referred to as Branch mode. When an access port of an FSP 150Mx/CX is connected to any other type of NE, a VLAN tag is added to reflect the arriving access port. This is referred to as Leaf mode. When an FSP 150Mx/CX is attached to an access port, the port will be automatically configured to Branch mode. However, when the port is detached, it will revert to its former state. An unconfigured access port is in Leaf mode. To configure the tag mode, perform the following steps:
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Ports and select the required access port. Select General Configuration.
109
Configuration
Step 3 Step 4 6.8.5.7
For the parameter Tag mode, select either Branch if the access port connects to another FSP 150Mx/CX or Leaf. Select OK or Apply.
Configuring the Port User String

A user string is provided for each port into which the user can enter a description of up to 40 alpha-numeric characters for what the port is used for or connected to. This is also reported as entPhysicalAlias in the Entity MIB (RFC 2737). User strings can be assigned, as required for management purposes. They are not interpreted or used by the NEMI.
Step 1 Step 2
Step 3 Step 4
In the parameter User String (Alias) type in the required text string.
Select OK or Apply.
110
TM
Optical Networking
6.8.6
6.8.6.1
Configuring Link Loss Forwarding

Enabling/Disabling Link Loss Forwarding
Link loss forwarding forwards notification of link down from one or more ports to one or more other ports.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Unit configuration, Running.
Step 3 Step 4 Step 5 6.8.6.2
In the parameter Link Loss Forwarding select On or Off. In the parameter Link Loss Forwarding - Point-to-Point select On or Off. Select OK or Apply.
Enabling/Disabling Link Loss Forwarding on a Specific Port

Link loss forwarding can be enabled or disabled on individual ports as required.
Step 1 Step 2
Step 3
Select or de-select Link Loss Forwarding to enable or disable the service.
111
Configuration
Step 4
Select OK or Apply.
6.8.7
Configuring PID Translation

PID translation enables mapping between a PID and a VID. Configuring PID translation is described in the sections below.
6.8.7.1
Enabling/Disabling PID Translation on a Network Port

PID translation is enabled or disabled on each network port.
Step 1 Step 2
Step 3 Step 4
In the parameter Translation select On or Off. Select OK or Apply. If PID translation needs configuring refer to Section 6.8.7.2 Configuring PID Translation.
6.8.7.2
Configuring PID Translation Step 1 Step 2

Navigate to Node configuration and select the required node. Select PID Translation, Configuration.
112
TM
Optical Networking
In the parameter Translation select one of Add S-VID, Del S-VID or Clear configuration. In the parameter Port ID (PID) type in the PID. In the parameter Service-VLAN ID (S-VID) type in the Service VID. Select OK or Apply. If PID translation needs enabling refer to Section 6.8.7.1 Enabling/Disabling PID Translation on a Network Port.
6.8.7.3
Configuring PID Translation Entry View Step 1 Step 2

Navigate to Node configuration and select the required node. Navigate to PID Translation, Status.
This will show which frames will be dropped on the PID Filters on Egress or Ingress by selecting either Egress or Ingress and then Apply.
6.9
6.9.1
Configuring OAM and EFM

Configuring Unit OAM
OAM Parameters define how EFM OAM Protocol Data Units (OAMPDUs) are transmitted to the Network Ports.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Unit configuration, OAM.
113
Configuration
Step 3
In the parameter Maximum packets / second, specify the maximum number of EFM OAMPDUs to be sent per second. The default is 10 PDUs per second (pps). In the parameter Event Retransmission Interval, specify the number of seconds between each retransmission of an EFM event OAMPDU. In the parameter Event Retransmission Tries, specify the number of times the EFM event OAMPDU will be retransmitted. Select OK or Apply.
6.9.2
Enabling/Disabling Access or Network Port OAM and EFM Information

Facilities are provided via the NEMI interfaces to enable or disable OAM management and EFM information on the Access and Network Interface ports, as required.
Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports, navigate to the required access or network port and select OAM, Config.
Select or deselect the parameter OAM Enabled to enable or disable the service. Select or deselect the parameter Info Enabled, to enable or disable the service. Select OK or Apply.
6.10
6.10.1
Configuring Protection
Configuring Tandem Mode (Mx only)
Step 2
Select Unit configuration, Running.
Step 1
114
TM
Optical Networking
Step 3 Step 4
Turn the parameter Tandem mode either On or Off. Select OK or Apply.
6.10.2
Configuring Protection on the Network Port (Mx only)

Protection on the network ports applies only to the FSP 150Mx only.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Unit configuration, Protection.
Step 3
In parameter Protection Type select the required option from the dropdown list.
115
Configuration
The FSP 150Mx/CX supports the following protection types: Layer 2 without Spanning Tree. This mode should be used when connecting the FSP150Mx to a layer 2 (Ethernet) metro core. When configured for layer 2 protection one of the network ports will be selected as active and the other one will be passive. The unit will receive and transmit data via the active port only. If the active port fails the unit will automatically switch the formerly passive network ports to active state. Layer 3. This mode should be used when connecting the FSP150Mx to a layer 3 IP metro core. When configured for layer 3 port protection the unit will accept traffic from both network ports and transmit all traffic received via the access ports via both network ports. Point-to-point. This mode should be used when connecting two FSP150Mx units in a point-to-point configuration. When configured for point-topoint protection the unit will transmit all data via both of the network ports and will select one of the network ports to receive from (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state. Force Network 1, which will disable network port protection and force Network port 1 to be used for both transmit and receive. Network port 2 is disabled in this mode. Force Network 2, which will which will disable network port protection and force Network port 2 to be used for both transmit and receive. Network port 1 is disabled in this mode. Link aggregate. When configured for link aggregation protection the unit will receive data via any of the network ports and will select one of the network ports to transmit via (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state.
When setting a protection type, it is possible to set a Preferred Network. However, for the protection types Layer 3, Force Network 1 and Force Network 2, this is not necessary.
Step 4
Select OK or Apply.
116
TM
Optical Networking
6.10.3
Enabling/Disabling HSRP/VRRP Forwarding (Mx only)

Hot Standby Router Protocol (HSRP) or Virtual Router Redundancy Protocol (VRRP) enables a virtual Router to be configured across two physical routes to protect against Router failure in the core network. This facility is used to enable or disable the bridging of HSRP/VRRP data packets across the Network ports.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Unit configuration, Protection.
Turn Forward HSRP On or Off. Turn Forward VRRP On or Off. Select OK or Apply.
6.11
6.11.1
Configuring Traffic Management

Enabling/Disabling Traffic Management Classification
Step 1 Step 2
Step 3 Step 4
Switch Traffic Mgmt classification, On or Off. Select OK or Apply.
117
Configuration
6.11.2
Configuring Network Port Shaping

Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports and navigate to the required network port. Select Traffic Mgmt.
Step 3
In the parameter AC [kbps], (Allocated Capacity) specify the mean capacity with which the ports are allowed to transmit. If no shaping is required set the value to 1048512. In the parameter ABS [kB], (Allocated Burst Size) specify the largest burst the network ports are allowed to send. If no shaping is required set the value to 4095. Select OK or Apply.
Step 4
Step 5
6.11.3
Configuring Access Port Regulators

Access port regulation is configured at access port level as described in this section. However, regulation is enabled or disabled by turning Traffic Management Classification on or off. The Traffic Mgmt classification parameter can be found by navigating to Node configuration, selecting the required node, Unit configuration, Running. To configure access port regulators:
Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports and navigate to the required access port. Select Traffic Mgmt, Regulators.
118
TM
Optical Networking
Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14 Step 15
In the parameter Ingress high priority CIR [kbps], specify the Ingress high priority Committed Information Rate (CIR). The default is 0. In the parameter Ingress high priority CBS [kB], specify the Ingress high priority Committed Burst Size (CBS). The default is 4095. In the parameter Ingress medium priority CIR [kbps], specify the Ingress medium priority CIR. The default is 0. In the parameter Ingress medium priority CBS [kB], specify the Ingress medium priority CBS. The default is 4095. In the parameter Ingress low priority CIR [kbps], specify the Ingress low priority CIR. The default is 1048512. In the parameter Ingress low priority CBS [kB], specify the Ingress low priority CBS. The default is 4095. In the parameter Egress high priority CIR [kbps], specify the Egress high priority CIR. The default is 0. In the parameter Egress high priority CBS [kB], specify the Egress high priority CBS. The default is 4095. In parameter Egress medium priority CIR [kbps], specify the Egress medium priority CIR. The default is 0. In the parameter Egress medium priority CBS [kB], specify the Egress medium priority CBS. The default is 4095. In the parameter Egress low priority CIR [kbps], specify the Egress low priority CIR. The default is 1048512. In the parameter Egress low priority CBS [kB], specify the Egress low priority CBS. The default is 4095. Select OK or Apply.
6.11.4
Configuring Access Port Priorities

Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports and then the required access port. Select Traffic Mgmt, Priority.
119
Configuration
Step 3
In the parameter Priority, select one of: default - no change of tagged traffic, and untagged traffic is assigned a default value.) force - forced to a specified priority (specified in Priority) copy - copied from an existing VLAN tag. If no VLAN tag exists the default value is used.
Step 4 Step 5
In the parameter Value, specify the priority value for Priority. The value may be 0 to 7. The default is 0. Select OK or Apply.
6.12
Configuring Egress Multicast (FSP 150MG only)

Configuring Egress Multicast consists of: Including an Access port in the Egress Multicast. See Section 6.12.1 Adding/Removing an Access Port to/from the Egress Multicast. Configuring IGMP VLAN tag mode on the Network ports. See Section 6.12.2 Configuring the Multicast IGMP VLAN Tag. Configuring CIR and CBS regulators for Egress Multicast. See Section 6.12.3 Configuring Egress Multicast Regulators. Configuring the Network port multicast protection type. See Section 6.12.4 Configuring Multicast Protection on the Network Port.
6.12.1
Adding/Removing an Access Port to/from the Egress Multicast

Step 1 Step 2
Select Ports, navigate to the required Access port and select General Configuration.
120
TM
Optical Networking
Step 3 Step 4.
At the parameter Multicast select On or Off. Select OK or Apply To view Multicast Access port statistics see Chapter 8, Section 8.2.2 Viewing Port Counters.
6.12.2
Configuring the Multicast IGMP VLAN Tag

Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports, navigate to the required Network port and select General Configuration.
Step 3
In the parameter Multicast IGMP-VLAN-tag select: unmodified multicast-VLAN both.
Step 4
Select OK or Apply. To view Multicast Network port statistics see Chapter 8, Section 8.2.2 Viewing Port Counters.
121
Configuration
6.12.3
Configuring Egress Multicast Regulators

Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Unit configuration, Multicast.
In parameter Egress Multicast regulator CIR [kbps] specify the Egress CIR. The default is 1048512. In Parameter Egress Multicast regulator CBS [kB] specify the Egress CBS. The default is 4095 Select OK or Apply. To view Egress Multicast regulator overflow status see Chapter 8, Section 8.2.1 Viewing Unit Counters.
6.12.4
Configuring Multicast Protection on the Network Port

Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Unit configuration, Multicast.
Step 3
In parameter Multicast Protection Type select the required option from the drop-down list.
122
TM
Optical Networking
The FSP 150MG supports the following protection types: Same as unicast, which will configure the protection mode for Multicast traffic so that it is the same as that configured for Unicast traffic. Layer 2 without Spanning Tree. This mode should be used when connecting the FSP150MG to a layer 2 (Ethernet) metro core. When configured for layer 2 protection one of the network ports will be selected as active and the other one will be passive. The unit will receive and transmit data via the active port only. If the active port fails the unit will automatically switch the formerly passive network ports to active state. Layer 3. This mode should be used when connecting the FSP150MG to a layer 3 IP metro core. When configured for layer 3 port protection the unit will accept traffic from both network ports and transmit all traffic received via the access ports via both network ports. Point-to-point. This mode should be used when connecting two FSP150MG units in a point-to-point configuration. When configured for point-to-point protection the unit will transmit all data via both of the network ports and will select one of the network ports to receive from (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state. Force Network 1, which will disable network port protection and force Network port 1 to be used for both transmit and receive. Network port 2 is disabled in this mode. Force Network 2, which will disable network port protection and force Network port 2 to be used for both transmit and receive. Network port 1 is disabled in this mode. Link Aggregate. When configured for link aggregation protection the unit will receive data via any of the network ports and will select one of the network ports to transmit via (the active network port). If the active port fails the unit will automatically switch the formerly passive network ports to active state.
Step 4
Select OK or Apply. To view Egress Multicast protection status see Chapter 10, Section 10.3.3.2 Viewing Unit Status.
123
Configuration
6.13
6.13.1
6.13.1.1
Configuring Fault Management

Enabling/Disabling Alarm Reporting
Port Alarms
Alarm reporting can be activated and deactivated by the user to switch the sending of Interface alarms On or Off. When alarm reporting is off, SNMP traps will not be sent for alarms occurring on the selected port. (1) If Off is selected, current alarms can be viewed in the Current Alarm facility, but the severity of each is given as notReported. Notes (2) If the Admin Status of the port is set to Down or Testing all alarms and traps are suppressed. (3) To suppress the sending of a specific individual alarm, set its severity to notReported in the Alarm Severity Table (see Section 6.13.3 Configuring Alarm Types and Severities).
Step 1 Step 2
Step 3 Step 4. 6.13.1.2
At the parameter Alarm Reporting select On or Off. Select OK or Apply
PSU and Fan Alarms

Facilities are provided via the NEMI Interfaces to enable alarm reporting for individual Power Supply Units (PSUs) and Fans.
To configure PSU and Fan alarm reporting perform the following steps:
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to PSU and Fans.
124
TM
Optical Networking
Step 3
For each component select On or Off. Enabling one will disable the other. Enabling an alarm will set its severity to the default value in the Alarm Severity Table (see Section 6.13.3 Configuring Alarm Types and Severities). Disabling an alarm will set its severity to notReported. Select OK or Apply.
Step 4 6.13.1.3
Individual Alarms
Alarms may be enabled on an individual basis by setting its severity level in the Alarm Severity Table. Alternatively, an individual alarm may be disabled by setting its severity to notReported. See Section 6.13.3 Configuring Alarm Types and Severities for further details.
6.13.2
Configuring Alarm Thresholds

Alarms may have been enabled to be raised when the Chassis temperature and/ or the PSU voltages have crossed a configured threshold. These thresholds may be configured.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Chassis configuration, Config.
Step 3
In the parameter Low Voltage Threshold [mV], specify a value between 11000 and 13000mV. This will be the minimum rail voltage threshold, below which a rail voltage failure alarm is raised. The default value is 11000mV.
125
Configuration
Step 4
In the parameter High Voltage Threshold [mV], specify a value between 11000 and 13000mV. This will be the maximum rail voltage threshold, above which a Rail Voltage Failure alarm is raised. The default value is 13000mV. In the parameter High Temp Threshold [C], specify a value between 30 and 75oC. This will be the maximum temperature threshold for the chassis, above which a Temperature Failure alarm will be raised. The default field value is 55oC. Select OK or Apply.
Step 5
Step 6
6.13.3
Configuring Alarm Types and Severities

Decisions on which alarm types should be visible to the NMS and what severity level should be assigned to each alarm type, should be made and recorded in the Alarm Severity Table.
6.13.3.1
Alarm Types
The alarm types that can be configured to be sent are: Voltage Too Low, when the voltage detected on the PSU is below the configured Low Voltage Threshold or the default value of 11000mV. Voltage Too High, when the voltage detected on the PSU is above the configured High Voltage Threshold or the default value of 13000mV. Temp Too High, when an internal temperature is detected to be above the configured High Temp Threshold or above the default value of +55oC.
The threshold values for Voltage Too Low, Voltage Too High and Temp Too High may be configured by the user. See Section 6.13.2 Configuring Alarm Thresholds PSU Failure, when a failure is detected on a PSU or the mains cable is not connected. Fan Failure, when a failure is detected on a fan unit. Local Chassis Missing, when the local chassis configuration has been saved, but a chassis is not physically present or accessible (e.g. during a firmware update). Local Chassis Mismatch, occurs after reboot (until communication between the NEMI and the microcontroller has been established) and during firmware download. Config Failed, when the saved configuration of the chassis, cannot be loaded on to the system.
Loss Of Signal, when an interface has no input signal. The cable may not be plugged in or the transmitter at the other end may be switched off. Low Rx Power, when the receive power (or Optical Input Power (OIP)) for an interface is below the Low Rx Power Threshold.
126
TM
Optical Networking
Tx Failure, when an interface is reporting a transmit failure. This could be caused by a broken laser or a faulty Small Form Factor Pluggable (SFP) Transceiver. Loss Of Link, when a loss of signal is detected on an electrical Ethernet port (i.e. the interface is not receiving link pulses). The cable used could be of the wrong type or there may not be a system connected to the other end.
The Loss Of Link alarm can be suppressed by setting the port Admin Status to Link down. See Section 6.8.5.1 Enabling/Disabling a Port. Eq Mismatch, when a SFP Transceiver module has been fitted and is of the wrong type (i.e. operates at the wrong data rate) or has not been approved by ADVA Optical Networking. Loopback, which is set when a loopback is in operation. SFP Missing, which is set when a Network or optical Access port does not operate because an SFP Transceiver is not fitted or has been fitted incorrectly.
6.13.3.2
Severity Values
Each severity indicates how the capability of the managed object has been affected, when the alarm is raised, as follows: Critical. A service affecting condition has occurred and immediate corrective action is required. Such severity can be reported, for example, when a managed object becomes out of service and its capability must be restored. Major. A service affecting condition has developed and urgent corrective action is required. Such a severity can be reported, for example, when there is a severe degradation in the capability of the managed object and its full capability must be restored. Minor. This is a non-service affecting fault condition and corrective action should be taken in order to prevent a more serious (e.g. service affecting) fault. Such severity can be reported, for example, when the detected alarm condition is not currently degrading the capacity of the managed object. Warning. A potential or impending service affecting fault may be indicated, before any significant effects have been felt. Action should be taken to further diagnose and correct the problem in order to prevent it from becoming a more serious service affecting fault. notReported. This suppresses a particular alarm. This value can also be set by disabling alarm reporting for ports and PSUs and fans (see Section 6.13.1.1 Port Alarms, Section 6.13.1.2 PSU and Fan Alarms and Section 6.13.1.3 Individual Alarms).
127
Configuration
All FSP 150Mx/CX NEMIs are delivered with all Working alarm types set to be reported and with their severity levels set to a default value. The default values are shown below:
Alarm Voltage Too Low Voltage Too High Temp Too High PSU Failure Fan Failure Local Chassis Missing Local Chassis Mismatch Config Failed Configuring Loss Of Signal Low Rx Power Tx Failure Loss Of Link Eq Mismatch Loopback SFP Missing Default Severity Value major major critical major major critical critical critical warning critical minor critical critical critical warning critical
The default factory settings may be changed. Each alarm type may be set to be notReported or a different severity level can be assigned, in accordance with system performance requirements.
6.13.3.3
Modifying Alarm Types and Severities

To modify the alarm types and severities:
Step 1
Navigate to Manager configuration, Alarm severity settings.
Step 2
Select the specific alarm and press Return to display the edit screen.
128
TM
Optical Networking
Step 3
Select the severity required (or notReported) from the drop-down list.
Step 4
Select OK.
6.14
Configuring Audit Logging

The FSP 150Mx/CX can, if enabled, log changes caused by user interaction (e.g. configuration changes), together with information about the user who made the changes. This facility may be used to trace (and therefore prevent) tampering with the set-up of a NMS.
6.14.1
Enabling/Disabling Audit Logging

To enable/disable audit logging:
Step 1
Navigate to Manager Configuration.
configuration
and
select
Logging,
129
Configuration
Enable or disable the parameter Audit Logging by selecting either On or Off. Ensure that the log entries are to be stored as required (see Section 6.14.2 Configuring Audit Log Storage). Select OK or Apply.
6.14.2
6.14.2.1
Configuring Audit Log Storage

Externally Stored Log Entries
Log entries can be sent to external servers whenever a system change is made by the user. The facility uses the syslog protocol according to RFC 3164 and up to eight servers can be configured.
Step 1 Step 2
Navigate to Manager Configuration. Select Add....
configuration
and
select
Logging,
Step 3 Step 4 6.14.2.2
In parameter SysLog Receiver enter the IP address of the server required and select OK. Select OK or Apply.
Locally Stored Log Entries

To store log entries on the local system flash memory:
Step 1
Navigate to Manager Configuration.
configuration
and
select
Logging,
130
TM
Optical Networking
Step 2
Select Log to File and enter the number of entries required in the parameter Number of log entries. During logging, when the number of log entries is reached, old log entries are overwritten with new ones. The maximum number of log entries that may be configured is 10 000. Select OK or Apply.
Step 3
6.15
Backing Up Configuration Settings

Once configuration of the FSP 150MX/CX has been performed, it is recommended that the configuration settings are saved to the NEMI and then copied from the NEMI and backed up somewhere safe. If the FSP 150Mx/CX is replaced in the future or the system requires re-configuration, the backed-up settings, can be restored easily so that existing system operation can be re-established. For full details on backing up configuration settings, refer to Chapter 9, Section 9.6 Backing Up and Restoring Settings. To backup configuration settings, perform the following steps:
Step 1
Select: Manager configuration, Config Mgmt, or Node configuration, the node required and then Config Mgmt.
Step 2
Select the configuration settings that are to be backed up from the Config Column and then select BACKUP. This will backup an entry from the Active Area and create a copy of the selected part of the configuration in a Backup Area. An existing backup file will be overwritten.
Step 3
Select OK.
131
Configuration
132
TM
Optical Networking
Chapter
Test Procedures
7.1 Introduction
This chapter describes how to perform tests for:
7
connectivity between Fiber Service Platform Multiplexer/Hub Node (FSP 150 Mx/CX) units identifying possible faulty connections traffic throughput.
7.2
7.2.1
Connection Tests
To Test the Ethernet Connection from a NMS
To test the success of the Network Element Management Interface (NEMI) Management Interface Internet Protocol (IP) configuration on an Ethernet network, connect the NEMI to an external network and ping the NEMI from a Network Management System (NMS) device on that network. For example, from a Windows Operating System (OS), open a Microsoft (MS) DOS command prompt window and issue the following command: ping xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the IP address entered during the configuration of the Management Interface. This command will send an Internet Control Message Protocol (ICMP) echo request to the NEMI. The NEMI should answer with an echo reply. If a reply is received this will be displayed on the screen along with the response time. If a response is not received a timed out message will be displayed, similar to that given below: Request timed out The timed out message from ping will vary depending upon the version of ping software in use. Request timed out is a typical message from MS DOS.
2563XJ07_Ch7_Test.fm - 16. October 2007
If a timed out message is received, this indicates that either the NEMI Management Interface IP configuration is incorrect or that there is a hardware problem.
133
Test Procedures
7.2.2
To Test the Ethernet Connection from the NEMI

To test the success of the NEMI Management Interface IP configuration on an Ethernet network, connect the NEMI to an external network and ping a NMS on that network from the NEMI.
Step 1 Step 2
Connect to the NEMI (see Chapter 5, Section 5.4.2 Accessing the Command Line Interface) and log in using the root account. Type: ping xx.xx.xx.xx where xx.xx.xx.xx is the IP address of the NMS on the external network. This command will send an ICMP echo request to the NMS. The NMS should answer with an echo reply. If a reply is received this will be displayed on the screen. If a response is not received, nothing will be displayed, indicating that either the NEMI IP configuration is incorrect or that there is a hardware problem.
7.3
Loopback Test
Loopbacks are a useful tool for tracking down and eliminating elements in an optical signal path. These may be implemented physically by, for example, plugging the output of an interface straight back into the input. However, an internal loopback may also be set via the FSP 150Mx/CX NEMI. When using the NEMI Loopback Test facility, a port may be tested for correct operation and/or correct fiber connections. This enables the FSP 150Mx/CX to be tested for an indication of where faults may be. Loopback testing would normally be performed during the commissioning of a complete FSP 150Mx/CX, directly after installation and/or during a service window. Laser radiation may be emitted from a fiber-optic transmitter, an optical time domain reflectometer (OTDR), or other optical test equipment. Laser infrared radiation is not visible to the naked eye. It is normal for connection to be made to the Rx and Tx ports of customer equipment during loopback. However, if customer equipment and service data is not yet available, connection can be made to a service test set instead. A remote loopback on the Network Interface, for example, will test the correct operation of and the correct flow of data through the near end FSP 150Mx/CX, across the network link to the far end Network Interface and back. This is illustrated in Figure 7-1.
Warning
134
TM
Optical Networking
Near End FSP 150Mx

Access Interface Network Interface
Far End FSP 150Mx

Network Interface Access Interface
Test Set
Figure 7-1: Remote Loopback on the Network Interface

The loopback will indicate if customer or test data is: Received correctly at the near end FSP 150Mx/CX by the Access Interface Transmitted correctly from the near end FSP 150Mx/CX by the Network Interface across the fiber link. Received at the far end FSP 150Mx/CX by the Network Interface. Transmitted correctly from the far end back across the Network fiber link. Received correctly at the near end FSP 150Mx/CX by the Network Interface. Transmitted correctly back to the Customer Equipment or Test Set by the Access Interface. The loopback serves to test, primarily, that the far end Network Interface is operating correctly. In so doing, an indication that customer data is being passed successfully across the Network Interface link between near and far end FSP 150Mxs is tested also. The FSP 150Mx/CX supports two loopback modes, as follows: Operation, Administration and Maintenance (OAM) loopback on Network Interfaces. Here, network ports will loopback all traffic except Ethernet First Mile (EFM) OAM Protocol Data Units (OAMPDUs). Incoming EFM OAMPDUs will be received and processed as normal and outgoing EFM OAMPDUs may be generated and mixed with the looped back traffic. Ethernet PHY loopback on Access Interfaces. Here, all traffic coming from the network ports will be looped back out from the network ports and all traffic arriving on the access port itself will be dropped. No traffic will ever be sent on the access port.
The consequence of configuring an access port in loopback mode is that communication with any nodes managed via that access port is lost. This may result in the Tag Mode of that access port being re-set to the default value of Leaf.
135
Test Procedures
7.3.1
Performing Loopbacks via the FSP 150Mx/CX NEMI Craft Interface

(1) Prior to running loopback tests, it is assumed that connection to the NEMI has been made and that the Craft Interface has been entered successfully. If details on connecting to the Craft Interface and logging out are required, refer to Chapter 5 Management Interfaces. (2) This section assumes that the Craft Interface is used to perform loopback tests. However, the Web Interface or the Command Line Interface (CLI) may be used instead, if preferred. Details on the Web Interface and the CLI are given in Chapter 5 Management Interfaces. There are two ways to enable/disable a loopback on a FSP 150Mx/CX port, as follows: by enabling/disabling a Port Loopback directly on the required node. See Section 7.3.1.1 Port Loopbacks. by starting/stopping a Remote Loopback from a connected node. See Section 7.3.1.2 Remote Loopbacks.
7.3.1.1
Port Loopbacks
To enable/disable a Port Loopback directly on a FSP 150Mx/CX node network or access port perform the following steps:
Step 1
Select Node configuration and then the required node. Select Ports and the port required and select General Configuration.
Step 2 Step 3
Enable/Disable the checkbox Port Loopback. Select OK or Apply. Loopback status can be checked by navigating to Node configuration, node required, Ports, port required, Status, General. The Loopback status parameter will show whether a loopback has been enabled/disabled on that port.
136
TM
Optical Networking
7.3.1.2
Remote Loopbacks
A Remote Loopback may be started/stopped from a connected node. I.e. a node may issue a remote loopback request to the node at the far end of a link. The far end node will then implement the loopback as requested. (1) A remote loopback request is only supported from an access port. (2) The Remote Loopback feature can be used to set a loopback on the network port of an attached downstream FSP 150 Customer Premise (FSP 150CP). To start and stop a remote loopback on an attached FSP 150Mx/CX or FSP 150CP perform the following steps:
Step 1
From the main menu select Node configuration and then the required node. Select Ports and the access or network port required and then select OAM, Remote Loopback.
Step 2
Select Start Rem Loopback/Stop Rem Loopback. If Start/Stop Rem Loopback is not performed successfully a message window will be displayed providing the remote loopback status.
Step 3
Select OK. Remote loopback status can be viewed on the Remote Loopback window. The Rem Loopback Status parameter will show whether the port is in Loopback, if there is No loopback or if the status is Unknown.
7.4
Onboard Traffic Test

The FSP150Mx/CX has a traffic test facility to test connectivity, throughput and frame loss over one or more links between a FSP 150Mx/CX and a locally connected FSP 150CP, and between a remotely connected FSP 150Mx/CX and its connected FSP 150CP. The test operates in point-to-point, tree and chain topologies. The tests can be run from the CLI or the Craft/Web Interface.
137
Test Procedures
7.4.1
Traffic Generators
The test components are shown below.
Network Port Network Port
Ingress Filter Action Drop
Egress Generator
Ingress Filter Departure Statistics
Egress Filter Arrival Statistics
Packet Processing and Buffering
Ingress Filter Arrival Statistics
Egress Filter Departure Statistics
Ingress Generator
Egress Filter Action Drop Access Port
Access Port
Both egress and ingress tests are supported, each with a suite of tests which can be run individually or collectively. The ingress generator injects frames close to the access ports in the ingress direction. The egress generator injects frames close to the network ports in the egress direction. In an Egress path, frames arrive at a network port and are forwarded on to an access port. In an Ingress path, frames arrive at an access port and are forwarded on to a network port. Only one generator per node can run at one time, which means that one generator can run on node A and another generator can, at the same time, run on node B, but not two tests on the same node at the same time. A filter feature is used to specify whether a port should pass or drop frames and counters are used to count the frames. In addition, arrival and departure statistics are available on screen.
7.4.2
Filters
Each node has been designed with one ingress filter and one egress filter.The ingress filter detects and counts frames that pass through the node from one access port to the network ports. The egress filter detects and counts frames that pass through the node from the network port to the access port. The ingress filter can be configured to detect and count frames of one type while the egress filter can be configured to detect and count frames of the same type as the ingress filter or of another type. To prevent packets being delivered externally, for each test, the ports filters must be set to opposing actions, one to pass and one to drop.
138
TM
Optical Networking
7.4.3
Tests
The following tests are provided within the commissioning test: Generate frames with a certain 8byte signature, which can be configured in hex or ASCII. Generate frames with a certain frame size in the interval from 64bytes to 9250bytes. Generate a certain number of frames in the interval from 1 to 2^{32}-1 (4294967265) frames or to generate frames in continuous mode. Generate frames at a certain bit rate, from 0 to 16383 x 64 kbps. The value entered will be automatically rounded up to the nearest 64kbps step.
Although the bit rate can be set to 1 gigabit per second not all access ports can provide such a high bandwidth. Therefore, the maximum bit rate that can be generated will be the maximum bit rate of the port that the generator is associated with. Generate frames with a certain burst between 16 to 4095 kbyte. The remaining part of an ADVA specific frame can be configured to different patterns such as random bytes, incremental bytes, all ones or all zeros. Random bytes are continuous random test patterns. (Optional) Generate frames with a customer Virtual Local Area Network (VLAN) tag which may be inserted with a specified VLAN ID (VID) and priority. A customer VLAN tag must be used when the ingress generator injects frames for a certain virtual interface. For the egress generator, a service VLAN tag must be inserted with a specific VID and priority. The VID will then dictate by which access port the frames will be routed through the node. A service VLAN tag should also be configured when the ingress generator injects frames for a certain virtual interface. Optionally a customer VLAN tag may be inserted with a specific VID and priority. A collective test comprising all of the above with or without a customer VLAN tag.
7.4.4
7.4.4.1
Statistics
Arrival Statistics
Arrival statistics are collected for both the access ports and network ports. The statistics are listed separately below.
Access Port
The access port arrival statistics are as follows: frames received from the assigned access port of the ingress filter bytes received from the assigned access port of the ingress filter frames received from all access ports bytes received from all access ports.
139
Test Procedures
Network Port
The network port arrival statistics are as follows: frames received from network-1 bytes received from network-1 frames received from network-2 bytes received from network-2.
7.4.4.2
Departure Statistics
Departure statistics are collected for both the access ports and network ports. The statistics are listed separately below.
Access Port
The access port departure statistics are as follows: frames sent on the assigned access port of the egress filter bytes sent on the assigned access port of the egress filter frames sent on any access port bytes sent on any access port frames dropped due to filter action frames dropped due to a regulator overflow frames dropped due to a buffer overflow frames dropped for any other reason.
Network Port
The network port departure statistics are as follows: frames sent on network-1 bytes sent on network-1 frames sent on network-2 bytes sent on network-2 frames dropped due to filter action frames dropped due to a regulator overflow frames dropped due to a buffer overflow frames dropped for any other reason.
7.4.5
Frame Formats
Only pre-defined ADVA-specific, layer-2 frame format is supported.
7.4.6
Loopback Requirement
In normal (bidirectional) traffic test circumstances, one port of a node (access or network) in the test path should be configured in loopback. Unidirectional testing is possible. Here a test path can be set up in one direction from one node to another and test frames can be dropped at the end of the path. In this case a loopback is not required.
For the FSP 150Mx/CX, access ports can be configured in PHY loopback and network ports can be configured in OAM loopback. For the FSP 150CP, OAM loopback on the network ports is supported. For further details refer to the FSP 150CP User Guide. For further details on loopbacks set via the FSP 150Mx/CX, refer to Section 7.3 Loopback Test.
140
TM
Optical Networking
7.4.7
Tag Protocol ID (TPID)

The TPID of VLAN tags added to the test frame is always set to 0x8100, which identifies the frame as a tagged frame. Test frames are inserted before TPID translation, so if the TPID translation feature is then enabled, ingress test frames will get their TPID changed from 0x8100 to the value of the TPID translation.
7.4.8
VLAN IDs
The first nibble of the VID must be greater than zero. Otherwise, the VLAN tag will be treated as invalid and therefore removed.
7.4.9
MAC Addresses
The source Medium Access Control (MAC) address will always be set to the MAC address of the node and the destination MAC address will be set to the invalid MAC address of 0.0.0.0.0.0.
7.4.10
7.4.10.1
Topologies
Point-to-Point
The illustration shows the traffic test paths in a point-to-point topology.
A1 Ingress filter - 'Pass' Egress filter - 'Drop' Ingress Generator N1
FSP 150Mx
FSP 150Mx
A1
Ingress filter - 'Pass' Egress filter - 'Pass' N1
Loopback
141
Test Procedures
7.4.10.2
Tree
The illustration below an example of the traffic test paths in a tree topology.
A5
Ingress filter - 'Drop' Egress filter - 'Pass'
FSP 150Mx
N1
Egress Generator
FSP 150Mx
A2
Ingress filter - 'Pass' Egress filter - 'Pass'
Loopback
FSP 150CP
Loopback
Note: A Remote Loopback could also be configured on the FSP 150CP Network Port A, in order to test the path down from the FSP 150Mx to the FSP 150CP.
142
TM
Optical Networking
7.4.10.3
Chain
The illustration shows the traffic test paths in a chain topology.
FSP 150Mx
A5
Ingress filter - 'Drop' Egress filter - 'Pass'
N1
Egress Generator
FSP 150Mx N1 N2
FSP 150Mx
A2
Ingress filter - 'Pass' Egress filter - 'Pass'
N1
FSP 150CP NA
Loopback
143
Test Procedures
7.4.11
Running the Onboard Traffic Tests via the Craft Interface

(1) Prior to running onboard traffic tests, it is assumed that connection to the NEMI has been made and that the Craft Interface has been entered successfully. If details on connecting to the Craft Interface and logging out are required, refer to Chapter 5 Management Interfaces. (2) This section assumes that the Craft Interface is used to perform onboard traffic tests. However, the Web Interface or the CLI may be used instead, if preferred. Details on the Web Interface and the CLI are given in Chapter 5 Management Interfaces. The menu structure of the onboard traffic test via the Craft (and Web) Interface(s) is shown below.
Traffic Test Generator Port Frame Size Frame Count Signature Payload CIR CBS Service VLAN Tag Customer VLAN Tag View View View State Rate Frames VID Priority VID Priority All-0/All-1/Incr/Random
Ingress/Egress
Start/Stop/Refresh/OK/Cancel/Apply
Filter
Port Enable Filter Signature Action Pass/Drop On/Off
OK/Cancel/Apply
Statistics
OK/Clear/Refresh
Auto
Config
Port Service VLAN Tag View View View
VID Priority Running/Not Running
State Rate Frames
Ingress Statistics
OK/Clear/Refresh
Egress Statistics
OK/Clear/Refresh
144
Start/Stop/Refresh/OK/Cancel/Apply
TM
Optical Networking
Running of the onboard traffic tests comprises the following actions: Login to CLI, Craft or Web Interface. Configure generator and filters. Clear current statistics. Enable loopback functionality at the end of the network link path. Start the generator. Stop generator or wait for test to finish. Disable loopback functionality at the end of the network link path. View the statistics. Enable loopback functionality at the end of the access link path. Start the generator. Stop generator or wait for test to finish. Disable loopback functionality at the end of the access link path. View the statistics. Verify result in statistics.
Login in to CLI/Craft/Web Interface
Configure generator and filters
Clear current statistics
Enable loopback functionality at the end of the test path
Start generator
Stop Generator or wait for the test to finish
Disable loopback functionality at the end of the test path
View statistics
7.4.11.1
Configuring the Generator and Filters Step 1 Step 2

From the main menu navigate to Node configuration and select the required node. Navigate to Traffic Test, Ingress or Egress, Generator.
145
Test Procedures
Step 3
Configure the parameters referring to the table below.

Parameter Assigned to port Frame size Frame count Description The port to be used in the test path. Specifies the length of an Ethernet network frame. The value can be 64 to 9250. The default is 128. Specifies the number of Ethernet network frames to be generated by the generator. The value can be 0 to 4294967295. The default is 500000. Specifies an identifier of 8 bytes that is inserted in each Ethernet network frame and used to identify a test frame. The value can be up to 17 alphanumeric characters. The default is blank. The default is advatest. Specifies the essential data that is being carried within an Ethernet network frame. The payload does not include the "overhead" data required to get the packet to its destination. Select one of the following: CIR [kbps] All-0 All-1 Incr Random
Signature
Payload
The default is Random. (Committed Information Rate). This is a bandwidth profile parameter that specifies the average speed at which the Ethernet network frames will be transferred. The value can be 0-1048512. The default is 10048. (Committed Burst Rate). This is a bandwidth profile parameter that limits the maximum number of bytes available for a burst of Ethernet network frames sent at the UNI (User Network Interface) speed. The value can be 16 to 4095. The default is 16. Enables and specifies a service VLAN tag ID from 0 to 4094 and specifies a priority for 0 to 7. Enables and specifies a customer VLAN tag ID from 0 to 4094 and specifies a priority from 0 to 7.
CBS [kB]
Service VLAN tag Customer VLAN tag
Step 4
Select Apply, OK.
146
TM
Optical Networking
Step 5
Navigate to the Filter tab.
Step 6
Configure the parameters referring to the table below.

Parameter Enable Filter Assigned to port Signature Description Enable or disable the filter. Select the required port. Specify an identifier of 8 bytes that this filter searches for in each Ethernet network frame and used to identify a test frame Pass counts the matching frames; Drop counts the matching frames and then discards them.
Action
Step 7 Step 8
Select Apply, OK. Navigate to the units corresponding ingress or egress filter; for example, if you have just configured the ingress filter, navigate to the egress filter and then perform the following: enable the filter assign the filter to the required port specify the signature In the parameter Action select Drop.
Step 9
Select Apply, OK.
147
Test Procedures
7.4.11.2
Viewing Generator Status Step 1 Step 2

From the main menu navigate to Node configuration and select the required node. Navigate to Traffic-test, Ingress or Egress, Generator.
Step 3
View the following parameters: State, which will have a value of either Idle or Running. Rate [kbps], which is the rate at which the generator, if running, is currently transmitting. Frames, which will show the number of frames generated.
View the latest status be selecting Refresh.
7.4.11.3
Clearing Current Statistics Step 1 Step 2

From the main menu navigate to Node configuration and select the required node. Navigate to Traffic-test, Ingress or Egress, Statistics.
Step 3 Step 4
Select Clear. Select OK.
148
TM
Optical Networking
7.4.11.4
Enabling Loopback Functionality at the End of the Test Path

To enable loopback functionality at the end of the test path follow the instructions given in Section 7.3.1 Performing Loopbacks via the FSP 150Mx/CX NEMI Craft Interface.
7.4.11.5
Starting the Generator

To start the traffic test:
Step 1 Step 2
Step 3 7.4.11.6
Select Start.
Stopping the Generator

To stop the traffic test:
Step 1 Step 2
Step 3
Select Stop.
149
Test Procedures
7.4.11.7
Disabling Loopback Functionality at the End of the Test Path

To disable loopback functionality at the end of the test path follow the instructions given in Section 7.3.1 Performing Loopbacks via the FSP 150Mx/CX NEMI Craft Interface.
7.4.11.8
Viewing Statistics
To view the statistics from a test:
Step 1 Step 2
From the main menu navigate to Node configuration and select the required node. Navigate to Traffic-test, Ingress or Egress, Statistics.
This displays statistics relevant for the test. See Section 7.4.4 Statistics, for a list of possible statistics.
7.4.11.9
Auto Test
An automatic version of the traffic test may be used. This auto test has the following default values pre-configured: Frame size: 500 Frame count: 22500000 Signature: advatest CIR [kbps]: 96064 CBS [kB]: 16
Running the Auto Test

To run the auto test:
Step 1 Step 2
Navigate to Traffic-test, Auto, Config.
150
From the main menu navigate to Node configuration and select the required node.
TM
Optical Networking
Step 3
Select the required port in the Assigned to port parameter. Selecting a network port will define an Egress auto test and selecting an access port will define an ingress auto test. For an egress test (assigned to one of the network ports), configure a VLAN tag ID and associated priority. For an ingress test (assigned to one of the access ports) this is optional. Select Start.
Step 4
Step 5
Viewing Auto Generator Status

To view the status of the automatic test packet generator:
Step 1 Step 2
From the main menu navigate to Node configuration and select the required node. Navigate to Traffic-test, Auto, Config.
Step 3
View the following parameters: State, which will have a value of either Idle or Running. Rate [kbps], which will show the data rate of the test, derived from the parameters. Frames, which will show the number of frames generated.
View the latest status be selecting Refresh.
151
Test Procedures
Viewing Auto Test Statistics

To view the statistics generated by the auto test:
Step 1 Step 2
From the main menu navigate to Node configuration and select the required node. Navigate to Traffic-test, Auto, Ingress or Egress Statistics.
Step 3
This will display all statistics relevant to the test. See Section 7.4.4 Statistics, for a list of possible statistics.
152
TM
Optical Networking
Chapter
8.1 Introduction
8
counters Operation, Administration and Maintenance (OAM) statistics on the network OAM interfaces. Port ID (PID) translation status.
This chapter describes how to monitor component counters to provide information on how the Fiber Service Platform Multiplexer/Hub Node (FSP 150Mx/CX) is performing. It describes how to view:
(1) Prior to performing the performance management tasks, it is assumed that connection to the Network Element Management Interface (NEMI) has been made and that the Craft Interface has been entered successfully. If details on connecting to the Craft Interface and logging out are required, refer to Chapter 5 Management Interfaces. (2) This section assumes that the Craft Interface is used to perform performance management. However, the Web Interface or the Command Line Interface (CLI) may be used instead, if preferred. Details on the Web Interface and the CLI are given in Chapter 5 Management Interfaces.
8.2
8.2.1
Viewing Counters
Viewing Unit Counters
Facilities are provided to view the number of frames that have been dropped during transmission to the Network ports from the unit.
Step 1 Step 2
2563XK07_Ch8_Performance.fm - 16. October 2007
Navigate to Node configuration and select the required node. Navigate to Unit configuration, Counters.
153
The counters are outlined in Table 8-1. Table 8-1 Unit Counters
Counter Egress Arrival Path changes Description The number of times the unit switches from receiving traffic via one of the network ports to receiving traffic via the other. The number of high priority frames dropped due to ingress buffer overflow. The number of medium priority frames dropped due to ingress buffer overflow. The number of low priority frames dropped due to ingress buffer overflow. The number of high priority frames dropped due to egress buffer overflow. The number of medium priority frames dropped due to egress buffer overflow. The number of low priority frames dropped due to egress buffer overflow. (FSP 150MG only.) The number of frames dropped due to Multicast buffer overflow.
Ingress Buffer Overflow high Ingress Buffer Overflow med Ingress Buffer Overflow low Egress Buffer Overflow high Egress Buffer Overflow med Egress Regulator Overflow low Multicast Regulator Overflow
The Running column provides values reported from system start. The Cleared column provides values reported since the counters were last cleared (see Section 8.2.3 Clearing Counters).
Step 3 Step 4
To update the counters select Refresh. When viewing of the unit counters is complete, select OK.
8.2.2
Viewing Port Counters

Facilities are provided to view the port counters on any connected port interface. The information that can be obtained is a summary of the Ethernet frames that have been transmitted and received on all interfaces.
Step 1
154
TM
Optical Networking
Step 2
Navigate to Ports, select the required port and then select Status, Counters.
The port counters are outlined in Table 8-2. Table 8-2 Port Counters
Counter Frames transmitted OK Frames received OK Frame too long errors Octets transmitted Octets received FCS Errors Pid Errors Description The number of Ethernet frames transmitted without errors. The number of Ethernet frames received without errors. The number of oversized frames received. The number of octets transmitted successfully. The number of octets received without errors. The Frame Check Sequence (FCS) errors i.e. the checksum errors in a received frame. The number of frames dropped due to illegal pids (i.e. Virtual Local Area Network (VLAN) Tag frame identifiers. (Access Ports only.) The number of high priority frames dropped due to ingress regulator overflow. (Access Ports only.) The number of medium priority frames dropped due to ingress regulator overflow. (Access Ports only.) The number of low priority frames dropped due to ingress regulator overflow. (Access Ports only.) The number of high priority frames dropped due to egress regulator overflow. (Access Ports only.) The number of medium priority frames dropped due to egress regulator overflow. (Access Ports only.) The number of low priority frames dropped due to egress regulator overflow.
Ingress Regulator Overflow high
Ingress Regulator Overflow med
Ingress Regulator Overflow low
Egress Regulator Overflow high
Egress Regulator Overflow med
Egress Regulator Overflow low
155
Table 8-2 Port Counters

Counter Frames transmitted to ring Description (Network Ports only.) The number of frames transmitted in a ring or chain network. (Network Ports only.) The number of frames received in a ring or chain network. (FSP 150MG Network Ports only.) The number of Multicast frames received without errors. (FSP 150MG Access and Network Ports only.) The number of Multicast frames transmitted without errors. (FSP 150MG Network Ports only.) The number of Multicast octets received without errors. (FSP 150MG Access and Network Ports only.) The number of Multicast octets transmitted without errors.
Frames received from ring
Multicast frames received
Multicast frames transmitted
Multicast octets received
Multicast octets transmitted
The Running column provides values reported from system start. The Cleared column provides values reported since the counters were last cleared (see Section 8.2.3 Clearing Counters).
Step 3 Step 4
To update the counters select Refresh. When viewing is complete select OK.
8.2.3
Clearing Counters
Each Counters facility has a Clear Command Button which will clear all resettable counters, i.e. set each counter back to 0.
8.3
Viewing Network Port OAM Statistics

Facilities are provided via the NEMI Management Interfaces to view the statistics available on the number of OAM Protocol Data Units (OAMPDUs) that have been transmitted and received on the uplink Network ports. To view the OAM statistics perform the following steps:
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Ports, select the required network port and then select OAM, Statistics.
156
TM
Optical Networking
The parameters that are shown are: OAM PDUs transmitted, the number of OAM PDUs passed for transmission. OAM PDUs received, the number of OAM PDUs received.
The Running column provides values reported from system start. The Cleared column provides values reported since the counters were last cleared (see Section 8.3.1 Clearing Statistics).
Step 3 Step 4
To update the statistics select Refresh. When viewing of the OAM statistics is complete, select OK.
8.3.1
Clearing Statistics
The Statistics facility has a Clear Command Button which will clear all resettable counters, i.e. set each counter back to 0.
8.4
Viewing PID Translation Status

Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to PID Translation, Status.
This shows which frames (tagged with S-VID or PID) will be dropped.
157
Step 3 Step 4
To update the status information select Refresh. When viewing is complete, select OK.
158
TM
Optical Networking
Chapter
Maintenance
9.1 Introduction
9
Technical Assistance and how technical assistance can be obtained from ADVA Optical Networking, if required during maintenance operations. Viewing Inventories and how to obtain information about the product needed when requesting support. Rebooting and Resetting and how to reboot the Network Element Management Interface (NEMI) and how to reset the chassis by performing a system power down. Upgrading Firmware/Software and how to upgrade node firmware and NEMI software. Hardware Maintenance and how to inspect and clean FSP 150Mx/CX equipment and replace hardware components.
This chapter provides the information required to successfully maintain and monitor the Fiber Service Platform 150 Multiplexer/Hub Node (FSP 150Mx/CX) hardware so that faults can be prevented and the unit can continue to operate successfully. The following information is provided:
Warnings
INVISIBLE LASER RADIATION (1) The FSP 150Mx/CX is a class 1 laser product when SFP Transceivers, approved by Adva Optical Networking, are fitted. (2) Do NOT stare into the beam of any SFP Transceiver or view directly with optical instruments. (3) There are no serviceable parts within the FSP 150Mx/CX unit. Casing should only be removed by trained service personnel.
2563XL07_Ch9_Maint.fm - 19. October 2007
159
Maintenance
(1) Small Form Factor Pluggable (SFP) Transceivers contain laser emitters on the front of the unit operating at a wavelength of 850/1310/1550nm, Class 1 AEL. (2) Unless labeled otherwise, when the FSP 150Mx/CX has SFP Transceivers fitted that are approved by ADVA Optical Networking, the whole unit meets specifications for a Class 1 laser product, (even if a laser diode is forced on during servicing operation) (21 CFR 1040.10, IEC 60825-1 and 60825-2 compliant). (3) Prior to performing some of the maintenance tasks outlined in this chapter, it is assumed that connection to the NEMI has been made and that the required management interface has been entered successfully. If details on connecting to the management interfaces and logging out are required, refer to Chapter 5 Management Interfaces. (4) Unless otherwise stated, it is assumed that the Craft Interface is used as the NEMI management interface. However, the Web Interface or the Command Line Interface (CLI) may be used instead, if preferred. Details on the Web Interface and the CLI are given in Chapter 5 Management Interfaces. (5) Only suitably qualified personnel may maintain FSP 150Mx/CX equipment. It is recommended that Personnel maintaining the FSP 150Mx/CX be trained and authorized by ADVA Optical Networking. The training necessary to, operate and service the FSP 150Mx/CX includes the following as a minimum: background information on optical fiber communication systems safety information concerning the laser classification system and the hazard levels of the FSP 150Mx/CX guidance on the safe use of the FSP 150Mx/CX.
9.2
Technical Assistance
Assistance may be required during the maintenance of the FSP 150Mx/CX. ADVA Optical Networking offers a comprehensive technical support service to customers. For further information, refer to the Preliminaries, Obtaining Technical Assistance.
9.3
Viewing Inventories
Inventories provide details on components in the chassis and on the ports. They are described below.
9.3.1
Viewing the NEMI Software Version

Facilities are provided to view the Management software version currently loaded.
Step 1
Navigate to Manager configuration, Inventory.
160
TM
Optical Networking
Step 2 Step 3
The NEMI software version will be shown, including the revision number. When viewing is complete select OK.
9.3.2
Viewing the Chassis Inventory

Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Chassis configuration, Inventory.
The information shown is:

Parameter Product Type Hardware Rev Firmware Rev Serial Number Part Number MAC Address NEMI fitted Description One of: MO/MX/MG/CX. The hardware revision number of the chassis. The revision number of the firmware currently resident in the chassis. The serial number of the chassis. This is factory set. The part number of the chassis.This is factory set. The Media Access Control (MAC) address of the chassis FSP 150MX/CX.This is factory set. This shows whether or not the chassis NEMI card fitted.
161
Maintenance
Step 3
When viewing is complete select OK.
9.3.3
Viewing a Port Inventory

Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports, the port required and then Status, Inventory.
The information shown is:

Parameter Hardware Rev Serial Number Part Code Wavelength [nm] Description The hardware revision number of the selected port. The serial number of the selected port. This is factory set. The part code of the selected port. The wavelength that the selected optical port will operate at. For bi-directional operations the Transmit wavelength is displayed.
Step 3
9.4
9.4.1
Rebooting and Resetting

Rebooting the NEMI
A reboot will reset the NEMI, and is generally performed after upgrading management software. See Section 9.5 Upgrading Firmware/Software. To perform a reboot navigate to Manager actions, Reboot NEMI.
162
TM
Optical Networking
Two types of reboot are available to the user: 1. Scheduled, which will perform an orderly shutdown and restart of the NEMI Operating System (OS) after a pre-defined timeout period. This will not affect the electrical and optical functions of the FSP 150Mx and the user may define the timeout period. See the heading Scheduled Reboot below for further details. Immediate, which will perform an orderly shutdown and restart of the NEMI OS immediately when requested by the user. Again, this will not affect the electrical and optical functions of the FSP 150Mx. See the heading Immediate Reboot below for further details.
2.
(1) A reboot will reset the NEMI, but lose any configuration that has not been saved (Refer to Chapter 6 Configuration, Section 6.14 Backing Up Configuration Settings for details on saving configuration settings). (2) The user can specify whether or not a NEMI should enable traffic forwarding after the NEMI reboot. See Section 9.4.3 Enabling/Disabling Traffic during NEMI Reboot/Chassis Reset.
Scheduled Reboot Setting a Scheduled Reboot Step 1

To perform a scheduled reboot: Enter the time out period required in the field: Reboot timeout (in seconds) and select OK.
A message similar to that shown below will be displayed: Time until reboot 00:02:41
Step 2 Step 3
To check the time remaining until reboot select the command button Refresh. After the timeout period has elapsed the NEMI will take approximately one minute to reboot.
163
Maintenance
Step 4 Cancelling a Scheduled Reboot
When the NEMI has rebooted successfully, reconnect to the management interface and/or login as required. To cancel the next scheduled reboot select the command button Cancel reboot.
Immediate Reboot
To reboot the NEMI immediately:
Step 1 Step 2
Select the command button Reboot Now!. The NEMI will take less than a minute to reboot. When the NEMI has rebooted successfully, reconnect to the management interface and/or login as required.
9.4.2
Resetting the Chassis

A reset will reset the whole FSP 150Mx/CX unit and is generally performed after upgrading node firmware. See Section 9.5 Upgrading Firmware/Software. Two methods of resetting the chassis are available to the user: 1. via the NEMI Management Interface, which will perform an orderly shutdown and restart of the chassis when requested by the user. See Section 9.4.2.1 Reset via the NEMI Management Interface for further details. System Power Down, which will completely power down the chassis and restart it and the NEMI when it is powered back up. See Section 9.4.2.2 System Power Down for further details.
2.
(1) A reset will reset the chassis, but lose any configuration that has not been saved (Refer to Chapter 6 Configuration, Section 6.14 Backing Up Configuration Settings for details on saving configuration settings). (2) The user can specify whether or not a NEMI should enable traffic forwarding after the chassis reset. See Section 9.4.3 Enabling/Disabling Traffic during NEMI Reboot/Chassis Reset.
9.4.2.1
Reset via the NEMI Management Interface

A chassis reset will result in an orderly shutdown and a restart of the chassis. A chassis reset will result in a complete loss of electrical and optical functions for the duration of the resetting procedure.
To reset the chassis follow the steps below:
Step 1
Navigate to Node configuration and select the node required. Select Upgrade node firmware.
164
TM
Optical Networking
Step 2 Step 3
Select the command button Reset Chassis. The FSP 150Mx/CX chassis will take less than a minute to reboot, during which time: the checksum of flash memory will be verified to ensure an undamaged firmware image. all unit indicators will be flashed once. The sequence is very fast as the unit will become operational in approximately 100ms.
Step 4
When the FSP 150Mx/CX has rebooted successfully, reconnect to the management interface and/or login as required.
9.4.2.2
System Power Down

During a System Power Down, the FSP 150Mx/CX chassis will be completely powered down and restarted. A System Power Down will result in a complete loss of electrical and optical functions for the duration of the power cycling procedure. To perform a System Power Down, follow the steps below:
Switch off the power to the FSP 150Mx/CX Chassis by disconnecting the power to each Power Supply Unit (PSU). Wait ten seconds and reconnect power. The FSP 150Mx/CX will take less than a minute to reboot, during which time: the checksum of flash memory will be verified to ensure an undamaged firmware image. all unit indicators will be flashed once. The sequence is very fast as the unit will become operational in approximately 100ms.
Step 4
When the FSP 150Mx/CX has rebooted successfully, reconnect to the management interface and/or login as required.
165
Maintenance
9.4.3
Enabling/Disabling Traffic during NEMI Reboot/Chassis Reset

The user may specify whether or not a node should enable traffic forwarding following a NEMI reboot or a chassis reset. To enable/disable traffic perform the following steps:
Step 1
Navigate to Node configuration and select the node required. Select Unit configuration, Reboot.
Step 2 Step 3
Turn Traffic forwarding before configuration, On or Off. Select OK or Apply.
9.5
Upgrading Firmware/Software
New FSP 150Mx/CX management software and node firmware upgrades may be provided from time to time by ADVA Optical Networking. This facility enables those upgrades to be downloaded and installed whenever they become available. However, there are several notes to take into account. This facility requires root privileges Services may be affected
Please refer to the Release Notes issued with the software/firmware release to confirm whether it is service affecting. The upgrade file must be resident on machine running a File Transfer Protocol (FTP) or Hypertext Transfer Protocol (HTTP) server which must be accessible by the FSP 150Mx/CX. Loss of power during the upgrade may cause corruption to the software/ firmware image and the procedure may have to be repeated. All software is checked during activation. If a power failure or a reset has occurred, which has resulted in software corruption, the download procedure will need to be repeated. For this reason, DO NOT reboot or power down during an upgrade.
Instructions for upgrading node firmware and NEMI software are given in the following sections.
166
TM
Optical Networking
9.5.1
Node Firmware Upgrade

Step 1 Step 2
Navigate to Node Configuration and select the required node. Select Upgrade node firmware.
Step 3
In parameter URL, type in the URL or Internet Protocol (IP) address and path of the upgrade file, for example, ftp://172.23.292.24/FSP150Mx_m3-fw_R2_0.bin
Step 4 Step 5
Select Upgrade to install the new firmware/software. Select Reset Chassis. The image will be downloaded, verified and activated. If a corrupt image has been downloaded, it will not be activated. If the unit is power cycled, the previous image will be loaded.
9.5.2
NEMI Software Upgrade

Rebooting or performing a power down during a software download will result in all software files resident on Random Access Memory (RAM) being lost.
Step 1
Navigate to Manager actions, Upgrade NEMI software.
167
Maintenance
Step 2
In parameter URL, type in the URL or IP address and path of the upgrade file, for example, ftp://172.23.292.24/FSP150Mx_m3-sw_R2_0.bin
When downloading from a web server use HTTP instead of FTP.
Step 3 Step 4
Select Upgrade to install the new software. Reboot the NEMI (see Section 9.4.1 Rebooting the NEMI). The image will be downloaded, verified and activated. If a corrupt image has been downloaded, it will not be activated. If the unit is power cycled, the previous image will be loaded.
9.6
9.6.1
Backing Up and Restoring Settings

Configuration File Management Overview
Backing up and restoring settings is performed using the facilities available via: Manager configuration, Config Mgmt. This enables NEMI management configuration files to be backed up and restored.
Node configuration, Node, Config Mgmt. This enables node configuration files to be backed up and restored.
168
TM
Optical Networking
Manager actions, File Mgmt. This allows configuration backup files to be transferred to and from another system running a FTP or HTTP server.
The information provided by these facilities is given in the following columns: Config, which lists the configuration settings that may be backed up and restored. All settings are grouped into four parts which can be individually backed up and restored, as follows: NEMI-Users, which comprises the user passwords for all user accounts and the times that they were last changed. NEMI-Interfaces, which comprises IP configuration settings and Secure Shell (SSH) encryption keys. NEMI-System, which comprises all other NEMI configuration settings (i.e. Date and Time, Simple Network Management Protocol (SNMP), Remote Authentication Dial In User Service (RADIUS) and Access Control List (ACL) settings) as well as the Alarm Severity Table. nodes, which comprises the configuration settings set for the selected node in the Node configuration submenu.
169
Maintenance
Area, which indicates the area that the configuration settings occupy: ACT, Active. The configuration is current and may be copied to a file in the Backup Area (see below). BAK, Backup. The settings are backup settings and may be activated to restore a certain configuration. Files in the Backup Area may also be transferred to and from a server system in order to store them safely.
State, which compares the Active configuration with the running configuration and the Backup configuration with the Active configuration and indicates whether the configurations are: UTD, Up To Date. The Active and Backup configurations are equal, i.e. the Active configuration is equal to the running configuration and the Backup configuration is equal to the Active configuration. Not UTD, Not Up To Date. At least one of the configurations has changed, i.e. the Active configuration is not equal to the running configuration and the Backup configuration is not equal to the Active configuration. N/A, Not Applicable. MIBs, XML schemas and generic node configuration files are always set to N/A.
Size, which indicates the size of the backup file (in bytes). Mod Date, which indicates the date and time that a file was created or last modified.
9.6.2
Backing Up and Restoring Configuration Settings

Current configuration settings can be saved to compact flash on the NEMI and copied from the NEMI and saved on a Personal Computer (PC) on the management network. If the system configuration needs to be replaced at any time, the saved configuration settings can be restored by reloading the back-up file. The configuration settings saved and/or restored are those settings that have been made during configuration. See Chapter 6, Configuration for further details on the configuration settings.
9.6.2.1
Saving the Running Configuration

To save the Running Configuration settings, perform the following steps:
Step 1
Select:
Manager configuration, Config Mgmt, or Node configuration, the node required and then Config Mgmt.
Step 2 Step 3
Select the configuration settings that are to be saved and then select SAVE. This will save the entry as the Active Configuration. Select OK.
170
TM
Optical Networking
9.6.2.2
Backing Up the Active Configuration

To backup the Active Configuration settings, perform the following steps:
Step 1
Step 2
Select the configuration settings that are to be backed up and then select BACKUP. This will backup an entry from the Active Area and create a copy of the selected part of the configuration in the Backup Area. An existing backup file will be overwritten.
Step 3 9.6.2.3
Select OK.
Transferring Backup File from NEMI to PC

A backup file that has previously been saved to the NEMI can be transferred to a PC on the management network using a FTP server, by performing the following steps: This process uses the NEMIs FTP/HTTP client and a FTP/HTTP server on the PC.
Select Manager actions, File Mgmt. Select UPLOAD and then select the configuration file(s) to be uploaded in the Sel column. Specify the URL required, using the following format: ftp://<name>:<password>@xxx.xxx.xxx.xxx/<filename> where: <name> is the user name of the system. <password> is the password for the user on the system running the FTP server. xxx.xxx.xxx.xxx is the IP address of the system running the FTP server. <filename> is the name of the file to be transferred.
Step 4
Select Apply. The selected files will be combined into one and transferred to the given URL. The process may take a few seconds.
Step 5
Select Refresh to update the status given in the Status field.
171
Maintenance
9.6.2.4
Transferring Backup File from PC to NEMI

A backup file that has previously been saved to a PC on the management network can be transferred back to the NEMI using a FTP or HTTP server, by performing the following steps: (1) This process uses the NEMIs FTP/HTTP client and FTP/HTTP server on the PC from which the files are to be transferred. (2) Ensure that the backup file has been downloaded to the appropriate server on the network connected to the NEMI and that the directory path to the file is known.
Step 1 Step 2
Select Manager actions, File Mgmt. Select DOWNLOAD and then specify the URL required, using the following format: ftp://<name>:<password>@xxx.xxx.xxx.xxx/<filename> where: <name> is the user name of the system. <password> is the password for the user on the system running the FTP server. xxx.xxx.xxx.xxx is the IP address of the system running the FTP server. <filename> is the name of the file to be transferred.
Step 3
Select Apply. The file specified by the URL will be downloaded and split into the following four parts: NEMI-Users NEMI-Interfaces NEMI-System nodes. See Section 9.6.1 Configuration File Management Overview for a definition of these parts. Existing backup files for parts contained in the file will be overwritten. The process may take a few seconds.
Step 4 Step 5

In order to restore the configuration in the backup file, the file must be activated (see Section 9.6.2.6 Restoring Backup File).
172
TM
Optical Networking
9.6.2.5
Cloning Configurations
A configuration in the Active or the Backup Area of one node may be cloned and used for another node of the same product type in its Active or Backup Area. This means that a configuration can be cloned: from the Active Area of one node to the Active or Backup Area of another node from the Backup Area of one node to the Active or Backup Area of another node.
This process uses the NEMIs FTP/HTTP client and a FTP/HTTP server on the PC.
Select Manager actions, File Mgmt. Select CLONE and then select the configuration file(s) to be copied in the Sel column. Specify the URL required, using the following format: ftp://<name>:<password>@xxx.xxx.xxx.xxx/<filename> where: <name> is the host name of the system. <password> is the password required to access the NEMI. xxx.xxx.xxx.xxx is the IP address of the NEMI from which the backup file will be transferred or the default IP address of 169.254.0.1, if IP configuration has not been performed. <filename> is the name of the file to be transferred.
Step 4
Select Apply. The selected files will be combined into one and transferred to the given URL. The process may take a few seconds.
Step 5 9.6.2.6
Restoring Backup File

A backup file of configuration settings that has previously been transferred to the Backup Area on the NEMI can be restored as the Active settings by performing the following steps:
Step 1
Step 2
Select the backed up configuration settings that are to be activated from the Config Column and then select ACTIVATE. This will activate a file from the Backup Area and after the next reboot the selected part of the configuration will be restored.
173
Maintenance
Step 3
Select OK. When restoring NEMI Interface settings, the IP Address of the Management Interface will be restored. If currently connected to the NEMI via its IP Address, connection may be lost if the address restored differs. If this occurs re-connect using the default IP Address, 169.254.0.1 and reconfigure the IP Address to the address required.
9.6.2.7
Deleting Files on the NEMI

To delete files that have been saved on the NEMI:
Select Manager actions, File Mgmt. Select DELETE and then select the files to be deleted, from the Sel column. Select Apply/OK and the file will be deleted.
9.6.3
Restoring Factory Settings

If problems are encountered during the FSP 150Mx/CX configuration process, the NEMI settings can be restored. The procedure will force a NEMI reboot and restore the NEMI settings back to the original factory defaults. Following a factory setting restoration, FSP 150Mx/CX configuration must be performed again.
(1) A restoration to factory settings may interrupt traffic until service settings are re-allocated. In addition, specific IP and SNMP configurations are lost, until re-configured. (2) When restoring NEMI Interface settings, the IP Address of the Management Interface will be restored. If currently connected to the NEMI via its IP Address, connection may be lost if the address restored differs. If this occurs re-connect using the default IP Address, 169.254.0.1 and reconfigure the IP Address to the address required. To reset a NEMI to its default factory settings, perform the following steps:
Step 1
Step 2
Select the configuration settings that are to be restored.

Step 3
Select FACTORY.
174
TM
Optical Networking
The settings restored are those settings that have generally been made during configuration and during the restore all settings will be emptied, apart from those outlined in the table below which will be reset to the factory defaults given. Table 9-1Factory Defaults
Settings NEMI_Users Password NEMI_Interfaces Host Name IP Address (Available on the Management and Aux ports only.) Inband Access VLAN Enable VLAN VID SSH HTTP Telnet NEMI_System Access Control Lists NEMI mode Security Enhancements List Network Address Services SNMP Agent Audit Logging Logging Log to File No. of File Entries Alarm Severities Voltage Too Low Voltage Too High Temp Too High PSU Failure Fan Failure Local Chassis Missing Local Chassis Mismatch Config Failed Configuring
Factory Defaults root netadmin user ChgMeNOW Blank 169.254.0.1/30
Off 15 Off Off Off Active Off allow-all 0.0.0.0 HTTP/SSH/SNMP/Telnet Off Disabled Disabled 1000 major, NSA major, NSA critical, NSA major, NSA major, NSA critical, SA critical, SA critical, SA warning, NSA critical, SA minor, NSA critical, SA critical*, SA critical, SA warning, SA critical, SA
Loss Of Signal Low Rx Power Tx Failure Loss Of Link Eq Mismatch Loopback SFP Missing
175
Maintenance
Table 9-1Factory Defaults

Settings Notes: SA - Service Affecting NSA - Not Service Affecting nodes Unit Egress Arrival Mode Event Retransmission Interval Event Transmission Count Ingress Departure Mode Jumbo Frames Link Loss Forwarding Link Loss Forwarding Point-to Point Network Port Protection Mode Network Port Protection Preferred Mode OAM Maximum Transmitted (pps) OAM Reporting Interval Router Redundancy Mode Tandem Traffic Forwarding Traffic Management VLAN Tag Protocol Id Chassis Rail Voltage Threshold Maximum Rail Voltage Threshold Minimum Temperature Threshold Alarm Reporting Ports aux Admin Status Data Rate Alarm Reporting Access Admin State Data Rate Forwarding Mode Link Loss Forwarding Loopback OAM OAM Information Tag Mode Traffic Management Egress Burst High Traffic Management Egress Burst Low Traffic Management Egress Burst Med Traffic Management Egress Capacity High Traffic Management Egress Capacity Low Up auto On Up auto Network 1 Off Off Enabled On Leaf 4095 4095 4095 0 1048512
Factory Defaults
Both 10 3 Both Off Off Off None None 10 Standard Disabled Off On Off 33024 (0x8100) 13000 11000 328K (55oC) On
176
TM
Optical Networking
Table 9-1Factory Defaults

Settings Traffic Management Egress Capacity Med Traffic Management Ingress Burst High Traffic Management Ingress Burst Low Traffic Management Ingress Burst Med Traffic Management Ingress Capacity High Traffic Management Ingress Capacity Low Traffic Management Ingress Capacity Med VLAN Priority VLAN Priority Mode Alarm Reporting Network Admin State Data Rate Loopback OAM OAM Information Traffic Management Transmit Burst Traffic Management Transmit Capacity Vid Translation Alarm Reporting PSUs and Fans Alarm Reporting Factory Defaults 0 4095 4095 4095 0 1048512 0 0 Default On Up auto Off Enabled On 4095 1048512 Disabled On On
Step 4
Select OK. A dialog box will appear asking: Are you sure you want to restore to factory settings?
Step 5 Step 6
Select OK to reboot the NEMI. The NEMI will take less than a minute to reboot. When the NEMI has rebooted successfully, reconnect to the Management Interface and/or login as required.
9.7
Hardware Maintenance
This section provides details of the precautions that can be taken and the general maintenance that can be applied to the FSP 150Mx/CX. Details on hardware and fiber-optic equipment handling, inspection and cleaning are provided.
177
Maintenance
9.7.1
9.7.1.1
Maintaining the FSP 150Mx/CX

FSP 150Mx/CX Handling Precautions
This product contains electro-static discharge devices. Caution Appropriate anti-static handling precautions should be followed. (i.e. IEC 61340-5-1:1998). An electro-static discharge device (ESD) can be damaged or destroyed by a discharge that may go unnoticed by a Technician. The FSP 150Mx/CX contains ESD-sensitive devices. When handling the FSP 150Mx/CX the following precautions should be taken to reduce electro-static discharges: Wear a grounded anti-static wrist or heel strap when handling the FSP 150Mx/CX.
Heel straps are effective, only while standing on conductive or static-dissipative surfaces. Store the FSP 150Mx/CX in an anti-static bag and keep it in its anti-static bag until it is to be installed. Do not handle the FSP 150Mx/CX unnecessarily. Do not use brushes with synthetic bristles or acid brushes to clean the FSP 150Mx/CX. Handle a defective FSP 150Mx/CX with the same precautions.
9.7.1.2
Inspecting the FSP 150Mx/CX

Observe the following notices when inspecting FSP 150Mx/CX equipment: (1) Output ports of the SFP Transceivers emit laser radiation which is invisible to the naked eye. The equipment uses laser diodes as fiber-optic transmitter sources, which are inherently safe unless mishandled. Mishandling and misuse can result in severe eye injury. (2) Do NOT inspect fiber-optic connectors with the FSP 150Mx/CX powered on.
Warnings
The FSP 150Mx/CX should be inspected visually for any signs that the unit is not operating adequately and/or as a means to prevent potential problems. Particularly look for: damage dirt and debris
178
Refer to Section 9.7.1.1 FSP 150Mx/CX Handling Precautions, for details on the precautions to be taken when handling the FSP 150Mx/CX.
TM
Optical Networking
correct cable connection correct Indicator display.
Tighten any cables and SFP Transceivers that may have worked loose. If status indicators are indicating incorrect operation, investigate the cause fully. Refer to Chapter 10, Fault Management, Section 10.3.4 Evaluating Status Indicators, for tips on how to do this. If a build up of dust and debris has occurred on the FSP 150Mx/CX, clean it by following the procedures given in Section 9.7.1.3 Cleaning the FSP 150Mx/CX.
9.7.1.3
Cleaning the FSP 150Mx/CX

Observe the following notices when cleaning FSP 150Mx/CX equipment: (1) Keep power inlet terminals free from dust to avoid risk of fire. (2) To avoid eye injury from debris, always wear safety glasses when working with canned compressed air.
Warnings
Refer to Section 9.7.1.1 FSP 150Mx/CX Handling Precautions, for details on the precautions to be taken when handling the FSP 150Mx/CX. The cleaning of the FSP 150Mx/CX is restricted to using canned compressed air to blow off any dust and debris evident from the inspection of the unit. Whilst cleaning unit components: do not use wet cleaning tissues do not use harsh or abrasive cleaning agents do not use brushes with synthetic bristles or acid brushes.
9.7.2
Maintaining Fiber-Optic Equipment

(1) Dirty fiber-optic connectors are a common source of light loss, especially for 9 m core singlemode fibers. As a general rule, whenever there is a significant, unexplained loss of light, inspect the connector plugs and sockets for dirt and dust (see Section 9.7.2.3 Inspecting Fiber-Optic Equipment). (2) To avoid fingerprints or other contamination, handle fiber-optic connector plugs and sockets carefully. (3) To prevent contamination, ensure that the optical ports of all active devices are fitted with protective caps when not in use.
Fiber-optic connectors differ from electrical connectors. In a fiber-optic system, light is transmitted through an extremely small fiber core. Since fiber cores are often 62.5 microns or less in diameter and dust particles range from a tenth of a micron to several microns in diameter, dust and any contamination at the end of the fiber core can degrade the performance of the connector interface where the two cores meet. Performance degradation can result in Connector Loss and/ or Return Loss (refer to the FSP 150 Glossary on your CD-ROM for a definition of these conditions).
179
Maintenance
In a communication system, proper fiber-optic connections become a critical factor. The fiber-optic connection quality depends on three factors: 1. 2. 3. the type of connector used the cleanliness of the connector the connection techniques employed.
Connectors must be precisely aligned and the connector interfaces must be completely free of foreign material. Fiber-optic cable connectors can be damaged by improper cleaning and connection procedures and dirty or damaged fiber-optic connectors can result in inaccurate communication. Unless equipment is installed in a hermetic environment, dust particles will eventually collect within the fiber-optic connections. This may, over time, cause signal degradation. For this reason, fiber-optic cable connectors need periodic care and maintenance.
9.7.2.1
SFP Transceiver Handling Precautions

SFP Transceivers contains electro-static discharge devices. Caution Appropriate anti-static handling precautions should be followed. (i.e. IEC 61340-5-1:1998). An ESD device can be damaged or destroyed by a discharge that may go unnoticed by a Technician. SFP Transceivers contains ESD-sensitive devices. When handling a SFP Transceiver take the following precautions to reduce electro-static charges: Wear a grounded anti-static wrist or heel strap when handling a SFP Transceiver.
Heel straps are effective, only while standing on conductive or static-dissipative surfaces. Store a SFP Transceiver in an anti-static bag or other anti-static enclosure until it is to be installed. Do not handle SFP Transceivers unnecessarily and handle them by the faceplate only. Do not touch the electronic components or any exposed printed circuitry. Do not use brushes with synthetic bristles or acid brushes to clean the SFP Transceivers. Handle defective SFP Transceivers with the same precautions.
180
TM
Optical Networking
9.7.2.2
Fiber-Optic Cable Handling Precautions

Fiber-optic cables can be damaged if they are handled or routed improperly. To avoid damaging fiber-optic cables, it is strongly recommended that the following is noted: Never bend fiber-optic cables at sharp angles. Do not bend fiber-optic cables to less than 30mm (1.2 in) radius. Do not knot or extremely flex fiber-optic cables. Do not tie fiber-optic cables together with a cable clamp or tie strap. Do not stand on fiber-optic cables. Keep cables off the floor. Avoid mechanical stress by routing unsupported fiber-optic cables over short distances only. Frequent mechanical stress can cause progressive degeneration of fiber-optic cables. Avoid tightening or pressuring fiber-optic cables. Avoid twisting or crossing one fiber-optic cable over another. Avoid excess cable length. Use a spiral wrap. Store unused fiber-optic cables in a cabinet or on a cable rack. Never use tools when connecting or disconnecting fiber-optic cables. Excessive force can damage or mis-align the connection system.
Caution
The most vulnerable areas of a fiber-optic cable are its connector plugs.
Do not pull fiber-optic cables too hard. When connecting or disconnecting a fiber-optic connector, hold the knob of the (plastic) movable part of the plug casing. Use extreme care when removing or installing fiber-optic connector plugs to avoid damaging the connector housing or scratching the end-face surface of the fiber. Put protective caps on fiber-optic connector plugs, when not in use. Remove protective caps from immediately before connection. fiber-optic connector plugs, only

Inspect fiber-optic connector plugs, periodically, as described in Section 9.7.2.3 Inspecting Fiber-Optic Equipment. Clean fiber-optic connector plugs as described in Section 9.7.2.4 Cleaning Fiber-Optic Equipment.
181
Maintenance
9.7.2.3
Inspecting Fiber-Optic Equipment

INVISIBLE LASER RADIATION. (1) SFP Transceivers, approved by ADVA optical networking are class 1 laser devices, when fitted into the FSP 150Mx/CX. (2) Do NOT stare into the beam of any SFP Transceiver or view directly with optical instruments. (3) Output ports of the SFP Transceivers emit laser radiation which is invisible to the naked eye. The equipment uses laser diodes as fiber-optic transmitter sources, which are inherently safe unless mishandled. Mishandling and misuse can result in severe eye injury. (4) Do NOT look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber. (5) Do NOT inspect fiber-optic connectors with the FSP 150Mx/CX powered on.
Warnings
(1) The FSP 150Mx/CX contains laser emitters on the front of the unit operating at a wavelength of 850/1310/1550nm, Class 1 AEL. (2) Unless labeled otherwise, when the FSP 150Mx/CX has SFP Transceivers fitted that are approved by ADVA Optical Networking, the whole unit meets specifications for a Class 1 laser product, (even if a laser diode is forced on during servicing operation) (21 CFR 1040.10, IEC 60825-1 and 60825-2 compliant). (3) Only suitably qualified personnel must inspect FSP 150Mx/CX Fiber-Optic Equipment. To inspect SFP Transceiver connectors, perform the following steps:
Step 1 Step 2
Power off the FSP 150Mx/CX equipment (see Section 9.4.2.2 System Power Down). Disconnect the optical connection. If the connection to be inspected is not currently established, remove the protective caps from the connector plug and socket, as appropriate.
Step 3
Inspect the connector plug, as follows: Do NOT look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber. Inspect the connector plug, with a magnifying glass, for dirt, obstruction and any possible damage. If the connector plug is damaged, replace the fiber-optic cable. If the connector plug is dirty, clean the plug as described in Section 9.7.2.4 Cleaning Fiber-Optic Equipment.
Warning
182
TM
Optical Networking
Step 4
Inspect the connector socket, as follows: Do NOT look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber. Inspect the connector socket, with a magnifying glass, for dirt, obstruction and any possible damage.
Warning
Caution
Attempts to repair a damaged SFP Transceiver connector socket may result in damage to the equipment. If a connector socket is damaged consult ADVA Optical Networking. If the connector socket is damaged, contact ADVA Optical Networking. If the connector socket is dirty, clean the socket as described in Section 9.7.2.4 Cleaning Fiber-Optic Equipment.
Step 5
Re-connect the connector plug and socket, if appropriate. If the inspected connection is not to be re-established, fit both the connector plug and socket with protective caps.
Step 6 Step 7 9.7.2.4
Repeat steps 2 to 5 until all necessary connectors have been inspected. Power on the FSP 150Mx/CX (see Section 9.4.2.2 System Power Down).
Cleaning Fiber-Optic Equipment

Observe the following notices when cleaning fiber-optic equipment INVISIBLE LASER RADIATION. (1) SFP Transceivers, approved by ADVA optical networking are class 1 laser devices, when fitted into the FSP 150Mx/CX. (2) Do NOT stare into the beam of any SFP Transceiver or view directly with optical instruments. (3) Output ports of the SFP Transceivers emit laser radiation which is invisible to the naked eye. If the equipment uses laser diodes as fiberoptic transmitter sources, which are inherently safe unless mishandled. Mishandling and misuse can result in severe eye injury. (4) Do NOT look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber. (5) Do NOT inspect fiber-optic connectors with the FSP 150Mx/CX powered on.
Warnings
Warning
To avoid eye injury from debris, always wear safety glasses when working with canned compressed air.
183
Maintenance
Caution
Commercial compressed air may cause oil contamination during cleaning. ALWAYS use canned, dry and oil-free compressed air when cleaning fiberoptic equipment.
(1) The FSP 150Mx/CX contains laser emitters on the front of the unit operating at a wavelength of 850/1310/1550nm, Class 1 AEL. (2) Unless labeled otherwise, when the FSP 150Mx/CX has SFP Transceivers fitted that are approved by ADVA Optical Networking, the whole unit meets specifications for a Class 1 laser product, (even if a laser diode is forced on during servicing operation) (21 CFR 1040.10, IEC 60825-1 and 60825-2 compliant). (3) Only suitably qualified personnel must clean FSP 150Mx/CX Fiber-Optic Equipment. The following materials are recommended for cleaning Fiber-Optic Equipment: Lint-free, nonabrasive, nonadhesive swabs for cleaning optical sockets (Microswabs by Texwipe are recommended). Lint-free, nonabrasive wipe or pads for cleaning optical plugs (Texwipe pads are recommended).
Moist cleaning using alcohol or other agents may leave a residue of industrial paper rag or other dirt on the ferrule end of connectors. Canned, dry oil-free compressed air, for removing dust or debris.
To clean SFP Transceiver connectors, perform the following steps:
Step 1 Step 2
Power off the FSP 150Mx/CX (see Section 9.4.2.2 System Power Down). Disconnect the optical connection. If the connection to be cleaned is not currently established, remove the protective caps from the connector plug and socket, as appropriate.
Step 3
Clean the connector plug, as follows: Blow off any accumulated dust and loose debris from the connector plug with canned, dry oil-free compressed air.
Gently clean the end-face surface of the connector plug with a lint free, nonabrasive wipe or pad.
Do not touch the connector plug end-surface after cleaning.
184
TM
Optical Networking
Warning
Do NOT look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber. Inspect the connector plug for dust and debris with a magnifying glass or as described in Section 9.7.2.3 Inspecting Fiber-Optic Equipment.
If the connector plug remains dirty after repeated cleaning, replace the fiberoptic cable. If the connector plug is still contaminated, repeat this step.
Step 4
Clean the connector socket, as follows: (1) It is not anticipated that connector sockets should require regular routine cleaning. (2) The sockets in the SFP Transceivers are cleaned thoroughly by the Manufacturer prior to shipment and provided that clean connector plugs are provided on the application side, the operation of the FSP 150Mx/CX should be error free. (3) Do not clean connector sockets if it is not necessary. Carefully insert the extension tube of the dry oil-free compressed air can into the socket and blow air into the socket to remove any dust or debris. Do NOT look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber. Inspect the connector socket for dust and debris with a magnifying glass or as described in Section 9.7.2.3 Inspecting Fiber-Optic Equipment. If the connector socket is still contaminated, repeat this step.
Warning
Step 5
Re-connect the connector plug and socket, if appropriate. If the cleaned connection is not to be immediately operational, fit both the connector plug and socket with protective caps.
Step 6
Check the connection for correct performance. If the performance is not adequate, repeat steps 3 to 5. If the performance is not adequate after repeated cleaning, replace the SFP Transceiver.
Step 7
Repeat steps 2 to 7 until all the necessary connectors have been cleaned.
185
Maintenance
9.7.3
Equipment Disposal
The FSP 150Mx/CX contains a small replaceable lithium battery. Do NOT use a fire to dispose of a NEMI battery, a NEMI or a FSP 150Mx/CX that has a NEMI fitted. When the FSP 150Mx/CX has reached its end of life, disposal of all components should be carried out in accordance with the following: relevant waste disposal legislation the companies own procedures for the disposal of waste products.
Warning
186
TM
Optical Networking
Chapter
Fault Management
10.1 Introduction
10
which tests are automatically performed by the unit. Fault Finding and how to identify a fault. Fault Clearance and how to clear a fault.
This chapter provides a guide to troubleshooting the Fiber Service Platform 150 Multiplexer/Hub Node (FSP 150Mx/CX). While it cannot cover every possible error or problem, it is intended that enough information is provided to help the user identify the source of a FSP 150Mx/CX fault and resolve a problem, so that correct operation of the FSP 150Mx/CX can be resumed. The following information is provided:
It is recommended that personnel troubleshooting the FSP 150Mx/CX be trained and authorized by ADVA Optical Networking. The training necessary to troubleshoot the FSP 150Mx/CX includes the following as a minimum: background information on optical fiber communication systems safety information concerning the laser classification system and the hazard levels of the FSP 150Mx/CX guidance on the safe use of the FSP 150Mx/CX.
Warnings
INVISIBLE LASER RADIATION. (1) The FSP 150Mx/CX is a class 1 laser product when Small Form Factor Pluggable (SFP) Transceivers, approved by Adva Optical Networking, are fitted. (2) Do NOT stare into the beam of any SFP Transceiver or view directly with optical instruments. (3) There are no serviceable parts within the FSP 150Mx/CX unit. Casing should only be removed by trained service personnel.
2563XM07_Ch10_Faults.fm - 19. October 2007
187
Fault Management
(1) SFP Transceivers contain laser emitters on the front of the unit operating at a wavelength of 850/1310/1550m, Class 1 AEL. (2) Unless labeled otherwise, when the FSP 150Mx/CX has SFP Transceivers fitted that are approved by ADVA Optical Networking, the whole unit meets specifications for a Class 1 laser product, (even if a laser diode is forced on during servicing operation) (21 CFR 1040.10, IEC 60825-1 and 60825-2 compliant). (3) Only suitably qualified personnel may install FSP 150Mx/CX equipment. (4) Prior to performing some of the fault management tasks outlined in this chapter, it is assumed that connection to the Network Element Management Interface (NEMI) has been made and that the Craft Interface has been entered successfully. If details on connecting to the Craft Interface and logging out are required, refer to Chapter 5 Management Interfaces. (5) This section assumes that the Craft Interface is used to perform some of the checks in fault management, However, the Web Interface or the Command Line Interface (CLI) may be used instead, if preferred. Details on the Web Interface and the CLI are given in Chapter 5 Management Interfaces.
10.2
Built in Tests (Except FSP 150MG)

During Power up or a unit reset: the checksum of flash memory will be verified to ensure an undamaged firmware image all unit Indicators will be flashed once. The sequence is very fast as the unit will become operational in less than a second.
10.3
Fault Finding
The flowchart below provides a sequence of activities to detect and resolve any faults.
188
TM
Optical Networking
Start
Connect to a Management Interface
Is a Management fault indicated?
Y
Follow the appropriate solutions given in Section 10.4.1 Resolving Management Issues
Has the fault cleared?
Y
View Current Alarms (See Section 10.3.1.1 Viewing Current Alarms)
View the Status Indicators (See Section 10.3.4 Evaluating Status Indicators)
Has an Alarm occurred?
Is a fault indicated on LED's?
Y
Find Alarm and follow solution given in the Alarm Table (See Table 10-1)
Y
Follow the appropriate solutions given in Section 10.4.2 Resolving Hardware Issues)
Check for correct cabling (See Section 10.4.3 Resolving Incorrect Cabling)
N
Check the Audit Log to trace any configuration changes that should be reset. (See Section 10.3.2 Evaluating the Audit Log)
Y Y
Perform a Hardware Reset (See Section 10.4.4 Hardware Reset) Contact Technical Support for Assistance (See Section 10.4.5 Further Assistance) Replace faulty components (See Section 10.4.6 Replacing Hardware Components)
Y Y
N
Check Management Interface for further information (See Section 10.3.3 Evaluating Component Status)
Y
End
189
Fault Management
A number of tools can be used for fault finding depending on the configuration of the FSP 150Mx/CX, as follows: for a basic FSP 150Mx/CX:
the Institute of Electrical and Electronics Engineers (IEEE) 802.3ah

Ethernet First Mile (EFM) standard and the Operations, Administration and Maintenance (OAM) protocol A FSP 150Mx/CX with a NEMI can be used to manage a FSP 150Mx/CX without a NEMI Indicator diagnostics for a managed FSP 150Mx/CX, with a Simple Network Management Protocol (SNMP) NEMI fitted: the IEEE 802.3ah EFM standard and the OAM protocol SNMP via an external Network Management System (NMS) local NEMI Management Interface Indicator diagnostics.
10.3.1
Evaluating Alarms
Alarms currently present on the FSP 150Mx/CX unit are listed in the NEMI Management Interface. To view current alarms refer toSection 10.3.1.1 Viewing Current Alarms. By referring to the Alarm Table given in Section 10.3.1.2 Alarm Table, identify the alarm that has occurred and initiate the appropriate solution. If the alarm is still present, refer to Section 10.4 Fault Clearance.
10.3.1.1
Viewing Current Alarms

Any alarms that exist on the FSP 150Mx/CX system can be viewed in the current Alarm Table. The information that the table contains is continually updated and lists all the traps stored locally on the NEMI. To view the current alarms perform the following steps:
Step 1 Step 2
Navigate to Node configuration and select the required node. Select Current alarms.
190
TM
Optical Networking
The information shown is: Location, which displays which component the alarm originates from. Alarm, which gives the names of the alarms that currently exist at the location given. Reported, which displays Reported or notReported. Reported indicates that a SNMP trap will be sent and that the indicators on the front panel of the local chassis will reflect the alarm condition.
(1) Only those alarms that have been chosen to be reported during Alarm Configuration will be displayed. See Chapter 6, Section 6.12.1.3 Individual Alarms. (2) For a description of each alarm type, refer to Section 10.3.1.2 Alarm Table.
Step 3 10.3.1.2
Alarm Table
By referring to Table 10-1, identify the alarm that has occurred and initiate the appropriate solution. If the alarm is still present, refer to Section 10.4 Fault Clearance.
Table 10-1:
Alarm
Alarm Table
Probable Cause The power supply has failed and/or the voltage has fallen below the threshold value. Solution 1. Confirm that the threshold value is at least 11000mV. If not, and a NEMI is fitted to the unit set the threshold value to 11000mV. 2. Contact ADVA Optical Networking Technical Support. 1. Confirm that the threshold value is less than or equal to 13000mV. If not and a NEMI is fitted to the unit set the threshold value to 13000mV. 2. Contact ADVA Optical Networking Technical Support. 1. Confirm that the threshold value is set appropriately. A suitable value is 55oC. If not and a NEMI is fitted to the unit set the threshold value appropriately. 2. Check that all fans are running and that the ventilation slots are unobstructed. 3. Contact ADVA Optical Networking Technical Support. 1. Check the mains cable for correct connection to the power supply. 2. Contact ADVA Optical Networking Technical Support.
Voltage Too Low
Voltage Too High
The power supply has failed and/or the voltage has risen higher than the threshold value.
Temp Too High
The temperature has risen higher than the threshold value.
PSU Failure
A fault is present on a Power Supply Unit (PSU).
191
Fault Management
Table 10-1:
Alarm Table
A fault is present on a fan unit. 1. Check that all fans are running and ensure that there are no obstructions. 2. Contact ADVA Optical Networking Technical Support. 1. Connect a local chassis. 2. Contact ADVA Optical Networking Technical Support. 1. Accept the configuration of the new system for storage in the NEMI Configuration database. 2. Contact ADVA Optical Networking Technical Support.
Fan Failure
Local Missing*
Chassis
A local chassis configuration has been assigned to the NEMI Configuration database, but a chassis is not present. Occurs after reboot (until communication between the NEMI and the microcontroller has been established) and during firmware download (when the serial link between NEMI and microcontroller is used to load the new firmware). It should go away afterwards. The saved configuration of the chassis, cannot be loaded on to the system.
Local Chassis Mismatch*
Config Failed*
1. Replace the system and try again. 2. Accept the configuration of the new system for storage in the NEMI Configuration database. 3. Contact ADVA Optical Networking Technical Support. 1. Ensure that the cable is connected correctly. 2. Ensure that the cable is of the correct type. 3. Ensure that the remote end is switched on/operating correctly. 4. Contact ADVA Optical Networking Technical Support. 1. Ensure that the SFP Transceiver is operating correctly. 2. Replace the SFP Transceiver. 3. Ensure that the fiber is not kinked. 4. Check the remote unit optical power output (see Section 10.4.2.7 Performing Optical Power Measurements). 5. Ensure that the SFP Transceiver in the remote unit has a suitable power output to meet the power budget. 6. Contact ADVA Optical Networking Technical Support. 1. Ensure that the SFP Transceiver is operating correctly. 2. Replace the SFP Transceiver. 3. Contact ADVA Optical Networking Technical Support.
Loss Of Signal
The interface has no input signal.
Low Rx Power
The Low Rx Power Threshold has fallen below the threshold value. The interface is contaminated or the power budget is exceeded.
Tx Failure
The interface is not transmitting.
192
TM
Optical Networking
Table 10-1:
Alarm Table
The electrical Ethernet interface is not receiving link pulses. 1. Ensure that the cable is connected correctly. 2. Ensure that the cable is of the correct type. 3. Ensure that the remote end is switched on/operating correctly. 4. Contact ADVA Optical Networking Technical Support. 1. Replace the SFP Transceiver with one of the correct type and approved by ADVA Optical Networking. 2. Contact ADVA Optical Networking Technical Support. 1. Refit the SFP Transceiver. 2. Contact ADVA Optical Networking Technical Support.
Loss Of Link
Eq Mismatch
A SFP Transceiver of the wrong type and/ or not approved by ADVA Optical Networking has been fitted.
SFP Missing
An SFP Transceiver is not fitted or has been fitted incorrectly.
* Alarms shown via the NEMI Management Interface only.
10.3.2
Evaluating the Audit Log

The FSP 150Mx/CX will, if enabled, log changes caused by user interaction (e.g. configuration changes), together with information about the user who made the changes. This facility may be used to trace a configuration change or action, which may be causing problems in the correct or desired operation of the FSP 150Mx/CX.
10.3.2.1
Viewing the Logfile directly on Screen

If audit logging has been configured to store log entries locally (see Chapter 6, Section 6.13.2.2 Locally Stored Log Entries) up to the latest 100 entries can be viewed directly on screen. To view the audit logfile:
Step 1
Navigate to Manager configuration and select Logging, View Logfile.
193
Fault Management
The following parameters are presented on screen:

Fields No Timestamp Chassis Parameter Entity Description The event number. The number starts at 1 following initial boot up and will go back to 1 following a reboot. The date and time that the event or change occurred. The serial number of the chassis on which the event or change occurred. The parameter that has been changed. The component on which the event or change occurred.
Step 2
Select an entry to show more details in the LOG Event.
The following parameters are presented on screen:

Fields Event Number Timestamp Application User Remote Host Chassis Ser Num Change Type Parameter Value Entity Description The event number. The number starts at 1 following initial boot up and will go back to 1 following a reboot. The date and time that the event or change occurred. Textual name of the application used to apply the change (e.g. Craft, SNMP). The user name of the person making the change. The Internet Protocol (IP) address of the remote server from which the change was performed. The serial number of the chassis on which the event or change occurred. The type of change made. The parameter that has been changed. The value that has been set.
The component on which the event or change occurred.
Step 3 10.3.2.2
When viewing is complete, select OK.
Viewing and Downloading the CSV File in the Web Interface

If using the Web Interface all the entries made to the logfile may be viewed and downloaded as a Comma-Separated Values (CSV) file.
194
TM
Optical Networking
10.3.2.2.1 Viewing the CSV File

To view the CSV logfile:
Step 1 Step 2
Navigate to Manager configuration and select Logging, View Logfile. To view the logfile using the default application for CSV (e.g. Microsoft Excel), select View Log File and respond to any alert dialog boxes as appropriate.
Step 3
When viewing is complete, close the CSV file as appropriate and select OK.
10.3.2.2.2 Downloading the CSV File

To download the CSV logfile:
Navigate to Manager configuration and select Logging, View Logfile. Right-click on View Log File, select Save Target As... and save the file as appropriate. When the file has been saved select OK.
10.3.3
Evaluating Component Status

Check the status of the chassis, unit and ports as described in this section. If a fault is indicated, refer to Section 10.4 Fault Clearance.
10.3.3.1
Viewing Chassis Status

Facilities are provided to view and monitor the current environmental and/or operating status of the chassis, in particular the current rail voltages of each PSU, the operating status and the operating temperature of the chassis.
Step 1
195
Fault Management
Step 2
Navigate to Chassis configuration, Status.
The parameters are:

Parameter Current Rail Voltage on PSU1 [mV] Current Rail Voltage on PSU2 [mV] Current Temperature [C] PSU 1 Status PSU 2 Status Description The current rail voltage on PSU 1 and 2 in milliVolts. In non-redundant PSU chassis types, this can be used to monitor the state of the power supply and should always be between 11000 and 13000mV. The temperature within the FSP 150Mx/CX chassis in Celsius. Acceptable values are below 40 celsius. The current status of PSU 1 and PSU 2. The following may be displayed: OK, which indicates that a PSU is operating correctly. Failed, which indicates that a failure is detected on a PSU or that the mains cable is not connected.
Fan 1 Status Fan 2 Status
The current status of Fan 1 and Fan 2. The following may be displayed: OK, which indicates that a fan is operating correctly. Failed, which indicates that a fan is running slow or has failed.
Chassis LED Status
The current alarm status of the Light Emitting Diodes (LEDs) on the front panel of the FSP 150Mx/CX chassis.
Step 3 10.3.3.2
When viewing of the chassis status is complete, select OK.
Viewing Unit Status

Facilities are provided to view and monitor the status of the unit and how it is currently receiving and transmitting traffic from/to the Network Interfaces. Information on the operation of the micro-controller and the forwarding status is also provided.
Step 1 Step 2
Navigate to Node configuration and select the required node. Navigate to Unit configuration, Status.
196
TM
Optical Networking
The parameters are:

Parameter Protection Type Active Network Multicast Protection Type Multicast Active Network Forward HRRP Forward VRRP Ring ID Unit Controller Watchdog timeout Controller address Controller mode The number of seconds until the node considers itself as unmanaged. The address of the NEMI controlling this node. The location of the unit controller (i.e. the NEMI). One of the following may be displayed: none, above, external (via AUX port) or internal. Whether the FSP 150Mx/CX is a master or slave. Description The protection type currently in use. The Network Interface currently in operation. (FSP 150MG only.) The Multicast protection type currently in use. (FSP 150MG only.) The Network Interface currently in operation. Whether forwarding of Hot Standby Router Protocol (HSRP) is enabled or disabled. Whether forwarding of Virtual Router Redundancy Protocol (VRRP) is enabled or disabled. The identifier of the FSP 150Mx/CX in a ring or chain network.
NEMI Mode
Step 3 10.3.3.3
When viewing of the unit status is complete, select OK.
Viewing Port Status

Facilities are provided via the NEMI Management Interface to view and monitor the condition of optical fiber links and electrical links. To view the condition of the links perform the following steps:
Step 1 Step 2
Navigate to Node configuration and select the required node. Select Ports and navigate to the port required. Select Status, General.
197
Fault Management
The port shown here is an Access Port but the parameters shown apply to all ports as follows:
Parameter Oper Status Description (Operational Status), a display only field which can have the following values: Up Down Link Down Testing Auto Negotiation Tx Mode Data Rate Loopback status Link Loss Forwarding Config Laser Bias [uA] the port is active and available for traffic. the port will not forward any traffic except EFM-OAM packages. the link has been forced down. the port is currently being used for loopback testing.
Shows whether auto negotiation is enabled or disabled. Displays the mode (half or full duplex) that the port is operating at. Displays the data rate that the port is operating at. Displays whether a loopback is enabled or disabled on the port. The current configuration of Link Loss forwarding. (Network and optical ports only.) A display-only field that results from monitoring the drive current required to maintain the correct output power of the optical lasers. (Network and optical ports only.) Displays the Tx Power in dBm as programmed onto the optical port at manufacture. As the value is displayed above the Rx power (see below), rudimentary calculations can be made to check the system link budget. (Network and optical ports only.) Displays the actual measured Rx Power in dBm. This enables a check to be made as to whether or not there is sufficient signal for the link to operate correctly.
Tx Power [dBm]
Rx Power [dBm]
Laser Temp [C]
(Network and optical ports only.) Displays the temperature of the optical port laser in oC.
Step 3
When viewing of the port status is complete, select OK.
198
TM
Optical Networking
10.3.4
Evaluating Status Indicators

Ensure that the status indicators are illuminated/extinguished to indicate correct operation of the FSP 150Mx/CX. Refer to Chapter 3, Components for the correct indications. If the status indicators indicate a problem, refer to Section 10.4 Fault Clearance.
10.4
Fault Clearance
Before replacing any hardware component, that is suspected of being faulty, first attempt to get the FSP 150Mx/CX operating correctly by following the procedures set out in: Section 10.4.1 Resolving Management Issues. Section 10.4.2 Resolving Hardware Issues. Section 10.4.3 Resolving Incorrect Cabling. Section 10.4.4 Hardware Reset. Section 10.4.5 Further Assistance. Section 10.4.6 Replacing Hardware Components.
10.4.1
10.4.1.1
Table 10-2:
Problem 1 2
Resolving Management Issues

Resolving Connection Issues
Management Interface Issues
Probable Cause Web access not enabled. The Ethernet cable is faulty. Solution Enable web access. Ensure that the cable is connected correctly and/or replace the cable. Ensure that the Ethernet connection is enabled on the attached device. Ensure that IP Configuration has been performed correctly.
Cannot access the Web Interface. Cannot connect to the NEMI via the Ethernet port.
A link fault. (Is the Link Indicator illuminated?) If the NEMI and the NMS PC are on different networks and there is no routing configured on the NEMI or a missing route on the PC configuration.
Note: To test the success of IP Configuration on an Ethernet network, perform the connections tests outlined in Chapter 7 Test Procedures. 3 4
Cannot login to a Management Interface. Cannot access the Web Interface, the login page is always redisplayed. (Other web sites can be accessed.)
The wrong username and/or password is being used. The internet browser cannot accept per-session cookies.
Enter the correct username and password. Ensure that the internet browser is configured to accept persession cookies. See Chapter 5, Section 5.3.2.1 Web Interface Access Requirements.
199
Fault Management
Table 10-2:
Management Interface Issues

Proxy may be configured. Do not use proxy and/or bypass proxy for local addresses. In MS Internet Explorer, select Tools, Internet Options... and ensure that the tab Connections is selected. Select the command button LAN Settings... and select the appropriate options in the Proxy server section. Re-configure the internet browser. In MS Internet Explorer, select Tools, Internet Options... and ensure that the tab General is selected. From the section Temporary Internet files select the command button Settings... and then select to Check for newer versions of stored pages, Automatically. In Netscape select, Edit, Preferences... and Advanced....
The internet browser does not refresh the pages of the Web Interface correctly.
The internet browser is using cached pages and is not checking for new page versions.
10.4.1.2
Rebooting Management Software

Software processes running in an undefined way may cause even a fault free device to indicate a fault status. Reboot the FSP 150Mx/CX software as described in Chapter 9, Section 9.4 Rebooting and Resetting.
10.4.1.3
Updating Management Software

Sometimes management problems are caused by software bugs and it is important to ensure that the latest software version is in use. New FSP 150Mx/ CX software updates may be provided from time to time by ADVA Optical Networking and facilities are provided to enable those updates to be downloaded. See Chapter 9, Section 9.5 Upgrading Firmware/Software.
200
TM
Optical Networking
10.4.2
Resolving Hardware Issues

INVISIBLE LASER RADIATION (1) SFP Transceivers, approved by adva optical networking are class 1 laser devices, when fitted into the FSP 150Mx/CX. (2) Do not stare into the beam of any SFP Transceiver or view directly with optical instruments. (3) Output ports of the SFP Transceivers emit laser radiation which is invisible to the naked eye. The equipment uses laser diodes as fiber-optic transmitter sources, which are inherently safe unless mishandled. Mishandling and misuse can result in severe eye injury. (4) NEVER look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber.
Warnings
Warnings
(1) ALWAYS remove power from supply leads when connecting or disconnecting DC power cables and always ensure that the protective earth terminal is grounded otherwise there is a risk of severe electrical shock and personal injury. (2) ALWAYS connect the accessory 3-pin power cord to a 3-pin grounded power outlet when supplying AC power to the FSP 150Mx/CX. If power is supplied without the protective earth grounded, there is a risk of severe electrical shock and personal injury. (3) The DC powered FSP 150Mx/CX units are designed for use with a telecommunications 48V DC (nominal) supply. As such, this should only be installed in a restricted access location by trained personnel. (4) When connecting to a 240V AC supply, the unit should be connected using a double pole branch circuit breaker of 3a. (5) NEVER insert metal objects, such as a screwdriver or a finger with jewelry, into open SFP Transceiver slots when the FSP 150Mx/CX is powered on.
Caution
This product contains Electro-Static Discharge-sensitive Devices. Appropriate anti-static handling precautions should be followed (i.e. IEC 61340-5-1:1998).
Caution
Fiber-optic cables can be damaged if they are handled or routed improperly. Observe the handling precautions provided in Chapter 9 Maintenance.
201
Fault Management
10.4.2.1
Table 10-3:
Problem
Resolving PSU Issues

PSU Issues
Probable Cause Mains lead not inserted. PSU internal failure. Solution Insert mains lead. Contact ADVA Optical Networking Technical Support. Insert mains lead. Contact ADVA Optical Networking Technical Support.
1. PSU 1/2 indicators extinguished.
PSU 1/2 Indicator illumination = Red.
Mains lead not inserted. PSU internal failure.
10.4.2.2
Table 10-4:
Problem
Resolving Fan Failure Issues

Fan Issues
Probable Cause A problem exists with the power supplies. Internal failure. Solution See Section 10.4.2.1 Resolving PSU Issues. Contact ADVA Optical Networking Technical Support. See Section 10.4.2.1 Resolving PSU Issues. Remove the obstruction. Contact ADVA Optical Networking Technical Support. Contact ADVA Optical Networking Technical Support.
1. Fan indicator extinguished.
Fans not operating.
A problem exists with the power supply. Fan obstruction. A fan has failed or is broken.
3. Fan indicator illumination = Red.
A problem exists with the fans.
10.4.2.3
Table 10-5:
Problem
Resolving Access Interface Issues

Access Interface Issues
Probable Cause No access port connections. A problem exists with the power supplies. Internal failure. Remote end fault. Solution Check all required access ports are connected. See Section 10.4.2.1 Resolving PSU Issues. Contact ADVA Optical Networking Technical Support. Check far end device(s) for faults.
1. All indicators extinguished.
Electrical Interface Rate indicator is extinguished, with cable inserted.
The indicator has failed.
Contact ADVA Optical Networking Technical Support. Contact ADVA Optical Networking Technical Support.
Internal failure.
202
TM
Optical Networking
Table 10-5:
3
Access Interface Issues

The Access Electrical link has failed. 1. Confirm correct cabling. 2. Confirm that the Auto negotiation, speed and duplex settings of the FSP 150Mx/CX match the connecting equipment. Remove the cable and check the connectors to ensure that none of the pins are distorted. Reinsert and ensure that the connectors are fully engaged. Replace the cable. Contact ADVA Optical Networking Technical Support. Confirm data transmission.
Electrical Interface Link indicator is extinguished, with cable inserted.
Cable is not inserted correctly.
The cable is damaged. Internal failure. 4 Electrical Interface Link indicator is not flashing. Data is not being transmitted.
Note: A green flashing Link indicator shows the normal operation of the Electrical Interface. 5 Optical Interface Data indicator is red. The SFP Transceiver is not approved by ADVA Optical Networking. Replace the SFP Transceiver with a new one approved by ADVA Optical Networking.
10.4.2.4
Table 10-6:
Problem
Resolving Network Interface Issues

Network Interface Issues
Probable Cause Invalid SFP Transceiver. Solution Fit an ADVA-approved SFP Transceiver.
1. Data indicator (Rate) is red.
10.4.2.5
Performing Onboard Traffic Tests

The FSP150Mx/CX has a traffic test facility to test connectivity, throughput and frame loss over one or more links between a FSP 150Mx/CX and a locally connected FSP 150 Customer Premise (FSP 150CP), and between a remotely connected FSP 150Mx/CX and its connected FSP 150CP. The test operates in point-to-point, tree and chain topologies. The tests can be run from the CLI or the Craft/Web Interface. Onboard traffic testing would normally be performed during the commissioning of a complete FSP 150Mx/CX, directly after installation and/or during a service window. However, a traffic test may be performed at any other time to enable the FSP 150Mx/CX to be tested for an indication of where faults may be. See Chapter 7, Test Procedures for details on performing Onboard Traffic Tests.
203
Fault Management
10.4.2.6
Performing Loopbacks
Loopbacks are a useful tool for tracking down and eliminating elements in an optical signal path. These may be implemented physically by, for example, plugging the output of an interface straight back into the input. An internal loopback is also possible via the FSP 150Mx/CX management interface. When using the Loopback Test facility, a network interface may be tested for the correct operation of a port and/or the correct fiber connections. Loopback testing would normally be performed during the commissioning of a complete FSP 150Mx/CX, directly after installation and/or during a service window. However, a loopback may be performed at any other time to enable the FSP 150Mx/CX to be tested for an indication of where faults may be. See Chapter 7, Test Procedures for details on performing loopbacks.
10.4.2.7
Performing Optical Power Measurements

Measuring light levels on the FSP 150Mx/CX optical interfaces is fundamental and should be undertaken when problems are encountered with data transmission. Optical measurements at the optical Rx and Tx ports should be obtained from: the appropriate Port Status screen in the Management Interface. by using an optical power meter calibrated for the appropriate wavelength.
The measurements should then be compared to the interfaces specification (given in the FSP 150 System Specification). The following should be attempted, for any optical interface whose measurements are outside the documented limits: Clean the SFP Transceiver optical interfaces. Clean the fibers used to couple the optical power meter to the FSP 150Mx/ CX optical interface. Confirm that the SFP Transceiver used is of the correct type. Check the SFP Transceiver for any obvious signs of damage and/or check the Management Interface for any alarm indications. Confirm that the fiber type used is appropriate for the SFP Transceiver (i.e. Multimode or Singlemode). In case of an SFP Transceiver fault, replace the SFP Transceiver with a new one of the same specification and repeat the test.
10.4.3
Resolving Incorrect Cabling

Check that the correct cables are in use. Check electrical connectors to ensure that they are fully engaged and that none of the pins are distorted. Check the fiber-optic cables and optical connectors according to the instructions given in Chapter 9 Maintenance.
204
TM
Optical Networking
10.4.4
Hardware Reset
Hardware processes running in an undefined way may cause even a fault free device to indicate a fault status. Try a Hardware Reset by resetting the chassis or performing a System Power Down (see Chapter 9, Section 9.4.2 Resetting the Chassis).
10.4.5
Further Assistance
The fault may be based on a particular hardware or software problem which is already known to ADVA Optical Networking and Technical Support may be able to provide some further assistance in clearing the fault. Refer to the Preliminaries, Technical Assistance for details on how to obtain further technical assistance.
10.4.6
Replacing Hardware Components

If a hardware defect has been identified, that cannot be resolved, a hardware component may need to be replaced as advised by ADVA Optical Networking and as outlined in this section. It is possible to replace the FSP 150Mx/CX chassis and SFP Transceivers. If a fault is suspected on the FSP 150Mx/CX chassis it is recommended that the chassis is replaced and the faulty chassis returned for Manufacturer repair. Likewise, if a fault is suspected on a SFP Transceiver, it is recommended that the Transceiver is replaced.
10.4.6.1
Preparing for Replacement

Replacement of a defective FSP 150Mx/CX component will result in a temporary interruption to a number of data channels. Minimize these interruptions by: Carefully planning the replacement operation, by being familiar with the procedures set for both removal and installation Establishing an optimum time for the replacement operation Ensuring that the new component to be replaced is readily available and of the correct type Ensuring that all the necessary tools, accessories and information is readily to hand.
10.4.6.2
Tools Required
A No.1 Pozi screwdriver may be required during replacement of the chassis for detaching Direct Current (DC) power cables. A No.2 Pozi screwdriver may be required during replacement of the chassis for detaching chassis rack mounting brackets. As the FSP 150Mx/CX contains Electro-Static Sensitive Devices (ESDs), a grounded anti-static wrist or heel strap is required when handling the unit to reduce electro-static discharges.
205
Fault Management
10.4.6.3
NEMI Battery Replacement

The FSP 150Mx/CX NEMI contains a small lithium battery. There is a risk of explosion if the battery is replaced by one of an incorrect type. There are NO user serviceable parts within the FSP 150Mx/CX unit. The Chassis case should only be removed and the NEMI battery be replaced by trained personnel, following advice from ADVA Optical Networking Technical Support. See Preliminaries, Equipment Return and Repair for contact details. Dispose of used batteries in accordance with the instructions given in the Chapter 9 Maintenance.
Warning
10.4.6.4
Fuse Replacement
There are NO user-serviceable parts within the FSP 150Mx/CX unit. The chassis case should only be removed and fuses be replaced by trained service personnel. A FSP 150Mx/CX has three fuses: PSUs marked ECM60US12 contain fuses, marked F1 and F2. A fuse for the NEMI on the main board.
All fuses should be replaced with a 3.15A, 250V fuse.
10.4.6.5
Chassis Replacement
This section covers the replacement of the FSP 150Mx/CX chassis. Before replacing the FSP 150Mx/CX chassis, refer to Section 10.4.6.1 Preparing for Replacement. The chassis contains electro-static discharge-sensitive devices. Appropriate anti-static handling precautions should be followed (i.e. IEC 61340-5-1:1998).
Caution
Caution
Keep all ports and connectors free from dust. When not in use, fit both connector plugs and sockets with protective caps.
Observe the handling precautions provided in Chapter 9 Maintenance.

The procedure for replacing a chassis includes the removal and re-installation of the FSP 150Mx/CX chassis. These procedures are outlined below.
206
TM
Optical Networking
Removal
The steps for removing a FSP 150Mx/CX chassis are as follows:
Step 1
Power Off Power off the FSP 150Mx/CX chassis.
Step 2
Remove all Cables Remove all cables from the connectors on the front panel. Install dust covers on the fiber cables connector plugs and insert a connector cover into the SFP Transceiver socket/s.
Step 3
Remove the Chassis Remove a standalone chassis from the surface on which it is placed. Remove a rack mounted chassis by carrying out the following: Release each mounting bracket from the rack and remove the FSP 150Mx/ CX chassis from the rack. Remove the two mounting brackets from the chassis, by removing the Pozihead Screws with a No.2 Pozi Screwdriver. Place the mounting brackets in a container suitable for storage.
Remove a wall mounted chassis from the two wall mounting brackets, by removing the Pozihead Screws on the side panels of the chassis with a No.2 Pozi Screwdriver and lifting the chassis away from the wall bracket. Only remove the wall bracket, if required. Place the chassis in a container suitable for storage and/or shipping. If returning equipment to ADVA Optical Networking for repair, use the original packaging material for optimum equipment protection.
Caution
Installation
For the installation of a replacement FSP 150Mx/CX chassis follow the procedure for installing a FSP 150Mx/CX given in the FSP 150 Installation Guide.
207
Fault Management
10.4.6.6
SFP Transceiver Replacement

INVISIBLE LASER RADIATION. (1) SFP Transceivers, approved by Adva Optical Networking are class 1 laser devices, when fitted into the FSP 150Mx/CX. (2) Do NOT stare into the beam of any SFP Transceiver or view directly with optical instruments. (3) Output ports of the SFP Transceivers emit laser radiation which is invisible to the naked eye. The equipment uses laser diodes as fiber-optic transmitter sources, which are inherently safe unless mishandled. Mishandling and misuse can result in severe eye injury. (4) NEVER look directly into an optical fiber connector or an unterminated receptacle with a magnifier, unless it is absolutely certain that no laser radiation is being emitted from the receptacle or the fiber.
Warnings
Warning
NEVER insert metal objects, such as a screwdriver or a finger with jewelry, into open SFP Transceiver slots when the FSP 150Mx/CX is powered on.
Caution
SFP Transceivers contain electro-static discharge-sensitive devices. Appropriate anti-static handling precautions should be followed (i.e. IEC 61340-5-1:1998).
Cautions
(1) When handling SFP Transceivers DO NOT touch any connections inside the device. (2) Keep all ports and connectors free from dust. When not in use, fit both connector plugs and sockets with protective caps.
(1) Observe the handling precautions provided in Chapter 9 Maintenance. (2) SFP Transceivers are hot-swappable, enabling them to be replaced when the FSP 150Mx/CX is powered on. The procedure for replacing a SFP Transceiver includes the removal and reinstallation of a Transceiver. These procedures are outlined below.
Removal
The steps for removing a SFP Transceiver are as follows:
Step 1
Remove Cables If fiber-optic cables are connected to the SFP Transceiver, disconnect them and install dust covers on the fiber cables connector plugs.
208
TM
Optical Networking
Step 2
Remove the SFP Transceiver Although the removal procedures for all SFP Transceiver types are basically the same, latch mechanisms may differ. Some SFP Transceivers may require the use of a small, flat screwdriver to assist in unlatching. Remove a SFP Transceiver by carrying out the following: Pull the latch forwards and down from the top of the Transceiver
Caution
Remove SFP Transceivers gently. If force is required, stop immediately. Ensure that the device is correctly unlatched and try again. Grasp the latch with thumb and finger and gently pull the SFP Transceiver forwards and out of the port. Holding the sides of the SFP Transceiver with thumb and finger, pull the latch upwards and back to its correct position. The figure below illustrates these actions with one SFP Transceiver type available.
Insert a connector cover into the SFP Transceiver sockets and place the Transceiver in a container suitable for storage and/or shipping. If returning equipment to ADVA Optical Networking for repair, use the original packaging material for optimum equipment protection. Insert a dust cover into the empty port casing of the chassis.
Caution
Installation
For the installation of a replacement SFP Transceiver follow the procedures given in the FSP 150 Installation Guide.
209
Fault Management
10.4.6.7
Equipment Return and Repair

When returning equipment to ADVA Optical Networking for repair, use the original packaging material for optimum equipment protection. If an FSP 150Mx/CX fault cannot be repaired on site, it may be recommended by ADVA Optical Networking Technical Support that the faulty component be returned for manufacturer repair. For assistance regarding the return of a faulty FSP 150Mx/CX for Manufacturer repair, contact ADVA Optical Networking Technical Support. See Preliminaries, Equipment Return and Repair for contact details.
Caution
210
TM
Optical Networking
Chapter
System Data
11.1 Introduction
11
Technical Definition An aggregation device, essentially a packet multiplexer capable of aggregating multiple Ethernet streams into a single transport link. A multi-port media converter that can be used as a secure Ethernet transport device for multi-service termination requirements.
This chapter provides a list of items which comprise the Fiber Service Platform 150 Multiplexer/Hub Node (FSP 150 Mx/CX) packages and accessories.
11.2
11.2.1
Name
FSP 150Mx/CX System Data

Description
Fiber Service Platform150 Multiplexer (FSP 150 Mx) Fiber Service Platform 150 Hub Node (FSP 150 CX)
11.2.2
Variant
Base Units
Part Number AC, No NEMI AC, inc. NEMI DC, No NEMI DC, inc. NEMI 0078903009 0078903010 0078903011 0078903012 0078903013 0078903014 0078903015 0078903016 0078903017 0078903018 0078903019 0078903020 0078903023 0078903024 0078993024 -
Optical Aggregation Unit (MO) 10x100BaseFX
Electrical Aggregation Unit (ME) 10x10/100BaseT
AC, No NEMI AC, inc. NEMI DC, No NEMI DC, inc. NEMI
Gigabit Ethernet Optical Aggregation Unit (MG) 6x1000BaseX

2563XN07_Ch11_Data.fm - 19. October 2007
AC, No NEMI AC, inc. NEMI DC, No NEMI DC, inc. NEMI
Multiport Multimedia Converter Unit (CX) 10x100Mbit/s 4 x Rubber Feet 1 x FSP 150 Mx/CX User Documentation CD-ROM
AC, inc NEMI DC, inc NEMI
211
System Data
11.2.3
Equipment Accessory Packs
Accessory Pack Name Optical SFP Transceiver Options (quantity as ordered)
Variant 100Mbit/s, 1310nm, SM, LC (10km) 100Mbit/s, 1310nm, SM, LC (40km) 100Mbit/s, 1550nm, SM, LC (70km) 1000Mbit/s, 850nm, MM, LC (220m) GigE, Electrical RJ45 (100m) GigE, 1310nm, SM, LC (10km) GigE, 1310nm, SM, LC (40km) GigE, 1550nm, SM, LC (80km) GigE, 1550 APD, SM, LC ((100km) GigE CWDM, 1470nm, SM, LC, (20db min optical budget) GigE CWDM, 1490nm, SM, LC, (20db min optical budget) GigE CWDM, 1510nm, SM, LC, (20db min optical budget) GigE CWDM, 1530nm, SM, LC, (20db min optical budget) GigE CWDM, 1550nm, SM, LC, (20db min optical budget) GigE CWDM, 1570nm, SM, LC, (20db min optical budget) GigE CWDM, 1590nm, SM, LC, (20db min optical budget) GigE CWDM, 1610nm, SM, LC, (20db min optical budget) 100Mbit/s (BX10), 1310nm/1550nm, SM, SC (10km) (pair) 100Mbit/s, BiDi 1310nm/1550nm, SM, SC (40km) (pair) GigE (BX10), BiDi 1310nm/1490nm, SM, SC (10km) (pair) GigE (BX10), BiDi 1310nm/1490nm, SM, SC (40km) (pair)
Part Number 0061003002 0061003003 0061003004 0061003006 0061000187 0061003008 0061003009 0061003010 0061003011 0061003020 0061003021 0061003022 0061003023 0061003024 0061003025 0061003026 0061003027 0061003012/13 0061003016/17 0061003014/15 0061003018/19 0036000156 0036000157 0036000158 0013903001
Power Supply Unit AC Power Lead (one of) Rack/Wall Mounting Kit
Central European UK US
1 x Right angled connection 2 x 19 Standard Brackets 2 x 19 Extended Brackets 2 x ETSI Standard Brackets 2 x ETSI Extended Brackets 2 x 23 Standard Brackets 2 x Wall Mount Brackets 10 x Screw (M4)
2563XN07_Ch11_Data.fm - 19. October 2007
8 x Screw (Countersunk Pozi)
212

Man 2563XX 07

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Man 2563XX 07

Încărcat de

Drepturi de autor:

Formate disponibile

TM

Fiber Service Platform 150 Multiplexer/Hub Node

Copyright 2007 ADVA Optical Networking

Tel: Fax: Website:

+49 (0)89 89 06 65 0 +49 (0)89 89 06 65 699 www.advaoptical.com

FSP 150Mx/CX User Guide

2563XA07_TitlePage.fm - 30. October 2007

ADVA AG Optical Networking Headquarters Fraunhoferstrae 9a 82152 Martinsried/Munich Germany

Purpose and Scope

FSP 150Mx/CX User Guide

Document Revision History

FSP 150Mx/CX 2.1

FSP 150Mx/CX 2.2

FSP 150Mx/CX 2.3

FSP 150Mx/CX 2.5

FSP 150Mx/CX 2.5.1

Chapter 1, FSP 150 Network Architecture Overview

FSP 150Mx/CX User Guide

2563XB07_Prelims.fm - 30. October 2007

Chapter 10, Fault Management Chapter 11, System Data

Bold monospace ->

FSP 150Mx/CX User Guide

FSP 150Mx/CX User Guide

FSP 150Mx/CX User Guide

Equipment Return and Repair

FSP 150Mx/CX User Guide

2563XB07_Prelims.fm - 30. October 2007

Tel: +33 (0)1 60 13 59 53 Fax: +33 (0)1 60 13 12 10 info@advaoptical.com

Tel: +43 1 4090 801 info@advaoptical.com

2563XB07_Prelims.fm - 30. October 2007

FSP 150Mx/CX User Guide

THIS PAGE INTENTIONALLY LEFT BLANK

FSP 150Mx/CX User Guide

2563XB07_Prelims.fm - 30. October 2007

2563XC07_Contents.fm - 30. October 2007

FSP 150Mx/CX User Guide

Chapter 4 Management Overview

FSP 150Mx/CX User Guide

Chapter 5 Management Interfaces

2563XC07_Contents.fm - 30. October 2007

FSP 150Mx/CX User Guide

FSP 150Mx/CX User Guide

2563XC07_Contents.fm - 30. October 2007

2563XC07_Contents.fm - 30. October 2007

FSP 150Mx/CX User Guide

Chapter 7 Test Procedures

Chapter 8 Performance Management

FSP 150Mx/CX User Guide

2563XC07_Contents.fm - 30. October 2007

Chapter 10 Fault Management

2563XC07_Contents.fm - 30. October 2007

FSP 150Mx/CX User Guide

Chapter 11 System Data

FSP 150Mx/CX User Guide

2563XC07_Contents.fm - 30. October 2007

2563XC07_Contents.fm - 30. October 2007

FSP 150Mx/CX User Guide

THIS PAGE INTENTIONALLY LEFT BLANK

FSP 150Mx/CX User Guide

2563XC07_Contents.fm - 30. October 2007

FSP 150 Network Architecture Overview

Ethernet Market Overview/Requirements