CCf825_INST_OPS R1[1].2.pdf

Optical Networking

TM

Fiber Service Platform 150CCf-825 (FSP 150CCf-825)

FSP 150CCf-825 Release 1.2

Installation and Operations Manual840-00028-02 Rev 1.0 November 2007

Copyright © 2001-2007 ADVA AG Optical Networking. All rights reserved.

All rights reserved. Hardware and software mentioned in this document includes software developed by ADVA AG Optical Networking ("ADVA"), the Apache Software Foundation (http://www.apache.org), Te-odor Danciu (http://jasperreports.sourceforge.net), and/or other open source software. Some software was created using ORBacus for Java by Object-Oriented Concepts, Inc.

Trademarks

The terms ADVA, FSP, Etherjack and the Etherjack logo are trademarks or registered trademarks of ADVA 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 or their respective owner.

Patents

The content described in this document may be covered by patents or pending patent applications of ADVA. The furnishing of this document does not give you 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. Any references in this document to non-ADVA publications and/or non-ADVA 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 In-ternet sites are not part of the materials for any ADVA 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 MER-CHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ADVA, ITS AFFILIATES, EMPLOYEES, OFFICERS OR ITS SUPPLIERS BE LIA-BLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUEN-TIAL 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 OR THE APPLICABLE PRODUCT LIABILITY LAW EXPRESSLY STATES OTHERWISE.

ADVA AG Optical Networking Headquarters Campus Martinsried Fraunhoferstr. 9 A 82152 Martinsried/Muenchen Germany

Phone+49(0)89-890665-848 Fax +49(0)89-890665-22848 www.advaoptical.com

Optical Networking

TM

Table of Contents

Chapter 1 Installing the FSP 150CCf-825 - - - - - - - - - - - - - - - - - - 1-1

1.1 Document Overview- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1Chapter Contents- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-3Release Levels Supported in This Document - - - - - - - - - - - - - - - - - - - 1-3Audience - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-3Related Documentation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-3Documentation Feedback - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-3

1.2 Trouble Clearing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-4Obtaining Technical Assistance- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-5

1.3 Product Features Supported in This Release - - - - - - - - - - - - - - - - - - - 1-61.4 Overview of the FSP 150CCf-825 - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-16

eVision Web Browser Management Tool - - - - - - - - - - - - - - - - - - - - - 1-17Command Line Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-17Simple Network Management Protocol (SNMP) - - - - - - - - - - - - - - - - 1-17

1.4.1 Service Applications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-18Connection-Oriented Services - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-18Connection-Less Services - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-19

1.4.2 ADVA’s Etherjack® Technology- - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-20Etherjack® Performance Monitoring - - - - - - - - - - - - - - - - - - - - - - - - 1-22Etherjack® Diagnostics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-23Cable Length Benchmark- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-24Port, VLAN and EFM-OAM Loopback - - - - - - - - - - - - - - - - - - - - - - - - 1-25Etherjack® Connection Performance Analyzer- - - - - - - - - - - - - - - - - 1-29

840-00028-02 Rev 1.0 Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL Page i

Installation and Operations Manual FSP 150CCf-825Table of ContentsRelease 1.2, November 2007 Optical Networking

TM

ECPA Operation- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-31Scheduled Ping - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-32Etherjack® Service Assurance- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-33Fault Propagation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-34EFM-OAM Dying Gasp - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-36SNMP Dying Gasp - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-36EFM-OAM Dying Gasp and SNMP Dying Gasp Inter-Operation- - - - - 1-38Ethernet Connectivity Fault Management- - - - - - - - - - - - - - - - - - - - - 1-39

1.5 Upgrading an Existing FSP 150CCf-825 - - - - - - - - - - - - - - - - - - - - - - 1-451.6 Initial Turn Up of an FSP 150CCf-825 - - - - - - - - - - - - - - - - - - - - - - - - 1-45

Recommended Sequence of Steps for Initial Turn Up of an FSP 150CCf-825 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-45

1.6.1 Connectors and LED Descriptions - - - - - - - - - - - - - - - - - - - - - - - - - - 1-46Rear Panel Connector Descriptions - - - - - - - - - - - - - - - - - - - - - - - - - 1-46Front Panel Connector Descriptions - - - - - - - - - - - - - - - - - - - - - - - - 1-47System LEDs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-49Local Management Port LEDs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-49Network and Client Ethernet Electrical Facility LEDs - - - - - - - - - - - - 1-50Network Optical Ethernet Port LEDs - - - - - - - - - - - - - - - - - - - - - - - - 1-51

1.6.2 Physical Installation- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-52FSP 150CCf-825 Package Contents - - - - - - - - - - - - - - - - - - - - - - - - - 1-52Mounting/Placement Procedures - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-54Placing the FSP 150CCf-825 on a Desk-top or in a Communications Clos-et - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-54Mounting the FSP 150CCf-825 to a Wall - - - - - - - - - - - - - - - - - - - - - - 1-54Mounting the FSP 150CCf-825 in a 19” or 23” Rack - - - - - - - - - - - - - 1-57

1.6.3 Power Options and Wiring - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-59Power Requirements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-59AC Supply - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-59DC Supply - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-59External AC to 12 VDC Power Converter - - - - - - - - - - - - - - - - - - - - - 1-60Connect Cables and Apply Power - - - - - - - - - - - - - - - - - - - - - - - - - - 1-60

1.6.4 Establish Communications Via Serial Console Port - - - - - - - - - - - - - 1-661.6.5 Provision Communications - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-67

Page ii Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL 840-00028-02 Rev 1.0

Installation and Operations Manual FSP 150CCf-825Table of Contents

Release 1.2, November 2007Optical Networking

TM

1.6.6 Download Latest Software Version - - - - - - - - - - - - - - - - - - - - - - - - - 1-681.6.7 Provision System Level Options - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-681.6.8 Create Users - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-691.6.9 Provision Access Security Options - - - - - - - - - - - - - - - - - - - - - - - - - 1-691.6.10 Provision the WAN Interface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-691.6.11 Provision LAN Interface(s) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-701.6.12 Provision Alarm Attributes and Scheduled Ping- - - - - - - - - - - - - - - - 1-701.6.13 Provision Performance Monitoring- - - - - - - - - - - - - - - - - - - - - - - - - - 1-701.6.14 Provision Cable Length Benchmarks and Perform Etherjack Diagnostic

Test - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-711.6.15 Provision and Perform ECPA Test - - - - - - - - - - - - - - - - - - - - - - - - - - 1-711.6.16 Provision and Perform ESA - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-711.6.17 Provision Connectivity Fault Management - - - - - - - - - - - - - - - - - - - - 1-711.6.18 Clear All Alarms- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-721.6.19 Create a Database Backup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-72

Chapter 2 Etherjack Service Assurance - - - - - - - - - - - - - - - - - - - 2-1

2.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-1Network Performance - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-1End-to-End Performance Monitoring - - - - - - - - - - - - - - - - - - - - - - - - - 2-4ESA Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-4

2.2 ESA Operation Using eVision- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8Create a Probe - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8Create a Reflector - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-14Scheduled ESA - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-15

Chapter 3 Web Browser Management Tool - - - - - - - - - - - - - - - - - 3-1

3.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-1Minimum System Requirements- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-4

3.2 Logging Onto the FSP 150CCf-825 - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-43.3 User Session Timeout - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-73.4 Getting Familiar with eVision Web Browser Management Tool- - - - - 3-83.5 About the Workspace- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-9

Title Bar - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-9

840-00028-02 Rev 1.0 Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL Page iii


TM

Menu Bar - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-9Tool Bar - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-10Menu Tree - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-11View Area- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-12Alarms Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-14Status Bar - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-14Applications Menu - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-14

3.6 Configuration View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-15Viewing Entities in Configuration View- - - - - - - - - - - - - - - - - - - - - - - 3-16Provisioning Entities in Configuration View - - - - - - - - - - - - - - - - - - - 3-17

3.6.1 Provisioning LAN Interface(s) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-17Provisioning a LAN to Transparent EVC Mode - - - - - - - - - - - - - - - - - 3-17Provisioning a LAN to Connection-oriented Flow VLAN EVC Mode - 3-22Provisioning a LAN to Connection-less Flow VLAN EVC Mode - - - - 3-31

3.7 Maintenance View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-37Viewing LAN, WAN and PSU Entities in Maintenance View- - - - - - - - 3-38

3.7.1 Editing Alarm Attributes- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-403.7.2 Loopback- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-413.7.3 Etherjack® Diagnostics - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-423.7.4 Cable Length Benchmark- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-45

Entering Cable Length Benchmarks Using Etherjack Test Measurements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-46Manually Entering / Editing Cable Length Benchmarks - - - - - - - - - - 3-49

3.7.5 Etherjack® Connection Performance Analyzer- - - - - - - - - - - - - - - - - 3-52Run Untagged ECPA Test on a LAN Facility- - - - - - - - - - - - - - - - - - - 3-57Run VLAN ECPA Test on a LAN Facility - - - - - - - - - - - - - - - - - - - - - - 3-60

3.8 Performance Monitoring - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-633.8.1 Selecting and Viewing PM Counts - - - - - - - - - - - - - - - - - - - - - - - - - - 3-64

Selecting and Viewing WAN and LAN Port PM Counts - - - - - - - - - - - 3-64Selecting and Viewing Queue PM Counts (VLAN)- - - - - - - - - - - - - - - 3-65Selecting and Viewing Flow PM Counts - - - - - - - - - - - - - - - - - - - - - - 3-65

3.8.2 Editing PM Thresholds- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-68Editing WAN and LAN Port PM Thresholds - - - - - - - - - - - - - - - - - - - 3-68Editing Queue PM Thresholds (VLAN) - - - - - - - - - - - - - - - - - - - - - - - 3-68

Page iv Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL 840-00028-02 Rev 1.0



TM

Editing Flow PM Thresholds - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-693.8.3 Initializing PM Registers- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-703.9 Scheduled Ping - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-723.10 Etherjack® Service Assurance- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-733.11 Connectivity Fault Management - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-74

Connectivity Fault Management Provisioning and Operation - - - - - - 3-743.12 Users and Security- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-81

User Access Security Levels - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-81GUI Login Time-out - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-81Viewing All Users- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-82Viewing Single User Details - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-82Creating a New User - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-83Editing a User - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-84Editing a User ID and Password- - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-84Editing Your Own Password - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-85Deleting a User - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-86

3.13 Provisioning Remote Authentication - - - - - - - - - - - - - - - - - - - - - - - - 3-863.14 Software Upgrade - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-893.15 Configuration Database Management - - - - - - - - - - - - - - - - - - - - - - 3-107

Determining Database Configuration Status - - - - - - - - - - - - - - - - - 3-107Save Changes - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-108Restore Factory Defaults - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-109Validation Timer- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-110Database Backup- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-113Database Restore- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-115

3.16 Rescue Image - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-119

Chapter 4 Communications Provisioning - - - - - - - - - - - - - - - - - - 4-1

4.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-14.2 Communications Provisioning for Various IP Configurations- - - - - - - 4-1

Scenario 1: Remote eVision Workstation Communications to SNE - - 4-4Scenario 2: GNE and SNE FSP 150CCs on Different Subnets - - - - - - 4-11Scenario 3: Stand Alone FSP 150CC Over a Layer 2 Cloud- - - - - - - - 4-15Scenario 4: eVision Workstation and GNE on Same Subnet, SNE on a Dif-

840-00028-02 Rev 1.0 Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL Page v


TM

ferent Subnet, FSP 150CCs Over a Layer 2 Cloud - - - - - - - - - - - - - - 4-184.3 Set Up Management LAN Port Using the Serial Console Port - - - - - - 4-234.4 Set Up Management Tunnel Using eVision- - - - - - - - - - - - - - - - - - - - 4-334.5 Set Up DHCP Using eVision - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-394.6 Provision ACL Using eVision - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-47

Chapter 5 Configuration Settings and Technical Data- - - - - - - - - 5-1

5.1 Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-15.2 System Default Parameters and Maximum Bandwidth - - - - - - - - - - - - 5-25.3 System Configuration Options and Rules - - - - - - - - - - - - - - - - - - - - 5-85.4 WAN Configuration Options and Rules - - - - - - - - - - - - - - - - - - - - - - 5-18

WAN Management Tunnel Configuration Options and Rules - - - - - - 5-205.5 LAN Configuration Options and Rules - - - - - - - - - - - - - - - - - - - - - - - 5-215.5.1 Transparent LAN Service Provisioning - - - - - - - - - - - - - - - - - - - - - - 5-215.5.2 Connection-oriented Flow VLAN Service Provisioning- - - - - - - - - - - 5-26

Default Priority Mapping Tables - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-345.5.3 Connection-less Flow VLAN Service Provisioning - - - - - - - - - - - - - - 5-355.5.4 LAN Management Tunnel Configuration Options and Rules- - - - - - - 5-415.6 CPD Configuration Options and Rules - - - - - - - - - - - - - - - - - - - - - - - 5-425.7 Loopback Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-465.8 Alarm Attributes, Probable Cause and Trouble Clearing - - - - - - - - - 5-495.9 Performance Monitoring Settings- - - - - - - - - - - - - - - - - - - - - - - - - - - 5-58

WAN Threshold Crossing Alerts - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-58LAN Port Threshold Crossing Alerts - - - - - - - - - - - - - - - - - - - - - - - - 5-63Flow Related Threshold Crossing Alerts - - - - - - - - - - - - - - - - - - - - - 5-69Flow QOS Threshold Crossing Alerts- - - - - - - - - - - - - - - - - - - - - - - - 5-69Flow Policer Threshold Crossing Alerts - - - - - - - - - - - - - - - - - - - - - - 5-70ESA Threshold Crossing Alerts - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-70

5.10 ESA Options and Rules - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-725.11 Scheduled Ping and ESA Activity Settings- - - - - - - - - - - - - - - - - - - - 5-76

Scheduled Ping - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-76Scheduled ESA - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-77

5.12 CFM Options and Rules - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-78Configure CFM System Level Parameters - - - - - - - - - - - - - - - - - - - - 5-78

Page vi Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL 840-00028-02 Rev 1.0



TM

Configure Default MD Parameters - - - - - - - - - - - - - - - - - - - - - - - - - - 5-79Configure CFM VLAN Table - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-79Configure Maintenance Domain - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-80Configure Maintenance Association- - - - - - - - - - - - - - - - - - - - - - - - - 5-81Configure Maintenance End Point - - - - - - - - - - - - - - - - - - - - - - - - - - 5-83Initiate Loop Back Message - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-84Initiate Link Trace Message - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-85

5.13 Technical Data - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-865.13.1 Connector Pin Assignments - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-865.13.2 Power - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-885.13.3 Environmental - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-89

Air Flow Requirements- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-895.13.4 Safety, Immunity, Emissions and Compliance - - - - - - - - - - - - - - - - - 5-905.13.5 Technical Specifications List by Functional Area- - - - - - - - - - - - - - - 5-91

840-00028-02 Rev 1.0 Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL Page vii


TM

This Page is Intentionally Left Blank

5.13.6Optical Specifications for FSP 150CC SFPs 5-96

Page viii Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL 840-00028-02 Rev 1.0

Optical Networking

TM

List of Tables

Table 1-1 FSP 150CCf-825 Rear Panel Power Connector - - - - - - - - - - - - - - - - 1-46Table 1-2 FSP 150CCf-825 Front Panel Connectors (Left to Right) - - - - - - - - - 1-48Table 1-3 150CCf-825 -48 VDC Power Supply Unit Connectors - - - - - - - - - - - - 1-48Table 1-4 System LEDs - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-49Table 1-5 Local Management LAN Port LEDs - - - - - - - - - - - - - - - - - - - - - - - - - 1-49Table 1-6 Network and Client Ethernet Facility LEDs - - - - - - - - - - - - - - - - - - - 1-50Table 1-7 Network and Client Electrical RJ-45 Connector LED Definitions - - - 1-50Table 1-8 Network Optical Ethernet Lk/Rate LEDs - - - - - - - - - - - - - - - - - - - - - 1-51Table 1-9 Power and Mounting Ordering Options - - - - - - - - - - - - - - - - - - - - - - 1-52Table 1-10 Air Flow Requirements for the FSP 150CCf-825 - - - - - - - - - - - - - - - - 1-57Table 1-11 Minimum and Maximum Operating Voltages - - - - - - - - - - - - - - - - - - 1-59Table 1-12 COM Port Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-66Table 1-13 Minimum WAN Interface Provisioning via CLI Commands - - - - - - - - 1-67Table 2-1 ESA Counts By Protocol Type and Report Group - - - - - - - - - - - - - - 2-17Table 3-1 COM Port Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-119Table 4-1 COM Port Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-24Table 5-1 System Default Configuration Settings - - - - - - - - - - - - - - - - - - - - - - - 5-2Table 5-2 Maximum WAN/LAN Bandwidth - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-7Table 5-3 System Configuration Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-8Table 5-4 Time Zone Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-16Table 5-5 WAN Configuration Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-18Table 5-6 WAN Management Tunnel Configuration Settings - - - - - - - - - - - - - - 5-20Table 5-7 Configuration Settings for Transparent LAN Service - - - - - - - - - - - - 5-22Table 5-8 Configuration Settings for Connection-oriented Flow VLAN Service 5-26


Installation and Operations Manual FSP 150CCf-825List of TablesRelease 1.2, November 2007 Optical Networking

TM

Table 5-9 8021P Default Priority Mapping Table - - - - - - - - - - - - - - - - - - - - - - - 5-34Table 5-10 TOS Default Priority Mapping Table - - - - - - - - - - - - - - - - - - - - - - - - 5-34Table 5-11 DSCP Default Priority Mapping Table - - - - - - - - - - - - - - - - - - - - - - - 5-34Table 5-12 Configuration Settings for Connection-less Flow VLAN Service - - - 5-35Table 5-13 LAN Management Tunnel Configuration Settings - - - - - - - - - - - - - - 5-41Table 5-14 Control Data Protocol Configuration Options and Rules - - - - - - - - - 5-42Table 5-15 Layer 2 Control Protocol Summary - - - - - - - - - - - - - - - - - - - - - - - - - 5-44Table 5-16 WAN Loopback Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-46Table 5-17 LAN Loopback Settings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-47Table 5-18 System Alarms - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-49Table 5-19 LAN and WAN Alarms - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-51Table 5-20 MEP Alarms - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-55Table 5-21 WAN Monitored Types and Default TCA Settings - - - - - - - - - - - - - - 5-58Table 5-22 LAN Port Monitored Types and Default TCA Settings - - - - - - - - - - - 5-63Table 5-23 Flow Monitored Types and Default TCA Settings - - - - - - - - - - - - - - - 5-69Table 5-24 Flow QOS Monitored Types and Default TCA Settings - - - - - - - - - - 5-69Table 5-25 Flow Policer Monitored Types and Default TCA Settings - - - - - - - - - 5-70Table 5-26 ESA Monitored Types and Default TCA Settings - - - - - - - - - - - - - - - 5-70Table 5-27 ESA Reflector Configuration Settings - - - - - - - - - - - - - - - - - - - - - - - 5-72Table 5-28 ESA Probe Configuration Settings - - - - - - - - - - - - - - - - - - - - - - - - - 5-72Table 5-29 Scheduled Ping Configuration Settings - - - - - - - - - - - - - - - - - - - - - - 5-76Table 5-30 Scheduled ESA Configuration Settings - - - - - - - - - - - - - - - - - - - - - - 5-77Table 5-31 Configure CFM System Level Parameters Settings - - - - - - - - - - - - - 5-78Table 5-32 Configure Default MD Parameters Settings - - - - - - - - - - - - - - - - - - - 5-79Table 5-33 CFM VLAN Table Configuration Settings - - - - - - - - - - - - - - - - - - - - - 5-79Table 5-34 Maintenance Domain Configuration Settings - - - - - - - - - - - - - - - - - 5-80Table 5-35 Maintenance Association Configuration Settings - - - - - - - - - - - - - - 5-81Table 5-36 Maintenance End Point Configuration Settings - - - - - - - - - - - - - - - - 5-83Table 5-37 Inititate Loop Back Message Settings - - - - - - - - - - - - - - - - - - - - - - - 5-84Table 5-38 Inititate Loop Back Message Settings - - - - - - - - - - - - - - - - - - - - - - - 5-85Table 5-39 10/100 Base-T LAN Port (RJ-45 Connector) - - - - - - - - - - - - - - - - - - - 5-86Table 5-40 1000 Base-T LAN Port (RJ-45 Connector) - - - - - - - - - - - - - - - - - - - - 5-87Table 5-41 RJ-45 (RS-232 Serial Console Port) and DB9 Adapter Pin Assignments

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-87


Installation and Operations Manual FSP 150CCf-825List of Tables


TM

Table 5-42 Power Ordering Options - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-88Table 5-43 Air Flow Requirements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-89Table 5-44 FSP 150CC Technical Specifications - - - - - - - - - - - - - - - - - - - - - - - - 5-91


Installation and Operations Manual FSP 150CCf-825List of TablesRelease 1.2, November 2007 Optical Networking

TM


Table 5-45Optical Specifications for FSP 150CC SFPs 5-96


Optical Networking

TM

List of Figures

Figure 1-1 FSP 150CCf-825 Front Panel - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-1Figure 1-3 Point-to-Point Application - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-16Figure 1-2 CO Aggregation Application - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-16Figure 1-4 Connection-Oriented UNI-EVC Mapping (Static Mapping) - - - - - - - - 1-18Figure 1-5 Connection-less UNI-EVC Mapping (Dynamic MAC-Based Mapping) 1-19Figure 1-6 Demarcation for Traditional T1 Services - - - - - - - - - - - - - - - - - - - - - 1-20Figure 1-7 Etherjack Demarcation for Ethernet Services - - - - - - - - - - - - - - - - - 1-21Figure 1-8 Performance Monitoring View with Counts in Chart Format - - - - - - 1-22Figure 1-9 Etherjack® Diagnostic Results Using eVision - - - - - - - - - - - - - - - - - 1-23Figure 1-10 Faulty Segment Identified Using Cable Length Benchmark - - - - - - - 1-24Figure 1-11 CO Based Testing Using Ethernet Loopback - - - - - - - - - - - - - - - - - - 1-25Figure 1-13 Facility Loopback (without Swap SA/DA) - - - - - - - - - - - - - - - - - - - - 1-26Figure 1-12 Terminal Loopback (without Swap SA/DA) - - - - - - - - - - - - - - - - - - - 1-26Figure 1-15 LAN Terminal Loopback (with Swap SA/DA) - - - - - - - - - - - - - - - - - - 1-27Figure 1-14 LAN Terminal Loopback (without Swap SA/DA) - - - - - - - - - - - - - - - 1-27Figure 1-16 LAN Terminal VLAN Loopback - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-28Figure 1-17 EFM-OAM Loopback - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-28Figure 1-18 End-to-End EVC Circuit Testing Using ECPA - - - - - - - - - - - - - - - - - 1-29Figure 1-19 ECPA Block Diagram - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-30Figure 1-20 ECPA Point to Point EVC Example - - - - - - - - - - - - - - - - - - - - - - - - - 1-30Figure 1-21 ECPA Test Results Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-32Figure 1-22 ESA Test Results in Chart Format - - - - - - - - - - - - - - - - - - - - - - - - - - 1-33Figure 1-23 Fault Propagation with RLD Notification Using Remote Link ID - - - - 1-34Figure 1-24 WAN Fault Propagation Disabling LANs (Detection of RFI) - - - - - - - 1-35


Installation and Operations Manual FSP 150CCf-825List of FiguresRelease 1.2, November 2007 Optical Networking

TM

Figure 1-25 EFM-OAM Dying Gasp - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-36Figure 1-26 SNMP Dying Gasp - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-37Figure 1-27 Provider-Subscriber Relationship - - - - - - - - - - - - - - - - - - - - - - - - - - 1-39Figure 1-28 Maintenance Domain Hierarchy - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-40Figure 1-29 Maintenance Points Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-41Figure 1-30 CCM Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-42Figure 1-31 Link Trace Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-43Figure 1-32 Loopback Message Example - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-44Figure 1-33 FSP 150CCf-825 Rear Panel Power Connector - - - - - - - - - - - - - - - - 1-46Figure 1-34 FSP 150CCf-825 Front Panel Connectors and LEDs - - - - - - - - - - - - 1-47Figure 1-35 FSP 150CCf-825 -48 VDC Power Supply Unit Connectors - - - - - - - - 1-48Figure 1-36 Install Wall Mounting Brackets - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-55Figure 1-37 Mount the FSP 150 to the Wall - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-56Figure 1-38 Attach Mounting Ears - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-58Figure 1-39 Mounting the FSP 150CCf-825 in a 19” or 23” Rack - - - - - - - - - - - - - 1-58Figure 2-1 ESA Test Results in Chart Format - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-2Figure 2-2 End-to-End SLA Verification - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-4Figure 2-3 ESA Probes and Reflectors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-5Figure 2-4 ESA One-Way Measurements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-6Figure 2-6 ESA Probe - Monitor Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-7Figure 2-5 ESA Probe - Injector Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-7Figure 2-7 ESA Reflector Operation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-8Figure 2-8 Create Probe View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-10Figure 2-9 Viewing a Probe Config Tab - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-11Figure 2-10 Viewing a Probe DistStats Tab (Summary History) - - - - - - - - - - - - - 2-12Figure 2-11 Viewing a Probe Thresholds Tab - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-12Figure 2-12 Create Reflectors View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-14Figure 2-13 Reflector View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-15Figure 2-14 Create New Groups View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-16Figure 2-15 ESA Test Results in Tabular Format - - - - - - - - - - - - - - - - - - - - - - - - 2-19Figure 2-16 ESA Late Packets Statistics Results in Chart Format - - - - - - - - - - - 2-20Figure 2-17 ESA Round Trip Delay Distributed Statistics Results in Chart Format

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-21Figure 2-18 ESA One Way Probe to Reflector Distributed Statistics Results in Chart


Installation and Operations Manual FSP 150CCf-825List of Figures


TM

Format - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-22Figure 3-1 eVision Web Browser Management Tool - - - - - - - - - - - - - - - - - - - - - - 3-1Figure 3-2 Authentication Failed Screen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-7Figure 3-3 eVision Web Browser Management Tool Components - - - - - - - - - - - 3-8Figure 3-4 Menu Tree with Menu Selected - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-11Figure 3-5 Tab Selections in the View Area - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-12Figure 3-6 Edit Transparent LAN Facility View - - - - - - - - - - - - - - - - - - - - - - - - - 3-13Figure 3-7 Alarms Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-14Figure 3-8 Configuration View (Transparent LAN Facility View) - - - - - - - - - - - - 3-16Figure 3-9 Edit Transparent LAN Facility View - - - - - - - - - - - - - - - - - - - - - - - - - 3-19Figure 3-10 Edit Connection-oriented Flow VLAN Facility View - - - - - - - - - - - - - 3-23Figure 3-11 Create Connection-oriented Flow View - - - - - - - - - - - - - - - - - - - - - - 3-26Figure 3-12 Options Available When Multi COS is Enabled - - - - - - - - - - - - - - - - 3-28Figure 3-13 Edit Connection-less Flow VLAN Facility View - - - - - - - - - - - - - - - - 3-32Figure 3-14 Create Connection-less Flow View - - - - - - - - - - - - - - - - - - - - - - - - - 3-34Figure 3-15 Maintenance View of LAN Facility (Operations Tab) - - - - - - - - - - - - 3-38Figure 3-16 Maintenance View of LAN Facility (Alarm Attributes Tab) - - - - - - - - 3-39Figure 3-17 Edit Alarm Attributes Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-40Figure 3-18 Loopback View (WAN) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-41Figure 3-19 Etherjack® Diagnostic Status - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-42Figure 3-20 Etherjack® Diagnostic Results - All Tests Passed - - - - - - - - - - - - - - 3-43Figure 3-21 Etherjack® Diagnostic Results - Failure Detected - - - - - - - - - - - - - - 3-44Figure 3-22 Cable Length Benchmark Using Etherjack® Diagnostics - - - - - - - - - 3-45Figure 3-23 Edit Cable Length Benchmark Information Screen - - - - - - - - - - - - - 3-49Figure 3-24 Edit ECPA Test Streams Window - - - - - - - - - - - - - - - - - - - - - - - - - - 3-52Figure 3-25 ECPA Test Setup Window (Flow VLAN) - - - - - - - - - - - - - - - - - - - - - - 3-53Figure 3-26 ECPA Test Results Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-54Figure 3-27 ECPA First Frame from ECPA Results Window - - - - - - - - - - - - - - - - 3-55Figure 3-28 ECPA First Frame Window from Menu Tree - - - - - - - - - - - - - - - - - - - 3-56Figure 3-29 Viewing RADIUS Counts in Performance Monitoring View - - - - - - - 3-63Figure 3-30 Selecting Port Counts in Performance Monitoring View - - - - - - - - - 3-66Figure 3-31 Performance Monitoring View with Port Counts in Tabular Format - 3-67Figure 3-32 Performance Monitoring View with Port Counts in Chart Format - - - 3-67Figure 3-33 Edit Port PM Threshold Window - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-69


Installation and Operations Manual FSP 150CCf-825List of FiguresRelease 1.2, November 2007 Optical Networking

TM

Figure 3-34 Initialize PM Registers Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-71Figure 3-35 Edit Scheduled Ping Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-72Figure 3-36 Scheduled Ping Status Window - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-73Figure 3-37 Create Maintenance Association Window - - - - - - - - - - - - - - - - - - - - 3-77Figure 3-38 Maintenance End Point Status Window - - - - - - - - - - - - - - - - - - - - - - 3-80Figure 3-39 Users View Showing All Users - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-82Figure 3-40 Default Database Configuration - - - - - - - - - - - - - - - - - - - - - - - - - - 3-108Figure 3-41 Validation Timer Window - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-110Figure 3-42 Commit/Exit Validation Timer Screen - - - - - - - - - - - - - - - - - - - - - - 3-112Figure 4-1 eVision Workstation on LAN Segment A and FSP 150CCs on LAN Seg-

ment B - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-4Figure 4-2 GNE and SNE FSP 150CCs on Different Subnets - - - - - - - - - - - - - - - 4-11Figure 4-3 Standalone FSP 150CC Over a Layer 2 Cloud - - - - - - - - - - - - - - - - - 4-15Figure 4-4 Workstation / GNE on Same Subnet, SNE on Different Subnet, FSP

150CCs Over a Layer 2 Cloud - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-18Figure 4-5 Management Tunnel View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-34


Optical Networking

TM

7

Chapter 1 Installing the FSP 150CCf-825

1.1 Document OverviewThis manual is provided to help you install, configure and operate the FSP 150CCf-825 Network Interface Device (NID) (see Figure 1-1 for a front panel view of the FSP 150CCf-825). The FSP 150CCf-825 provides 1 Gb Ethernet WAN interface media conversion to four 10/100 Base-T LANs and one 1 Gb Ethernet LAN.

In addition to providing media conversion, ADVA’s Etherjack technology provides carriers with an intelligent Ethernet demarcation device that is aligned with emerging Ethernet OAM standards for transport, connectivity and services from IEEE, MEF and ITU standards bodies.

Although this document focuses primarily on using the eVision web browser for configuring and monitoring the FSP 150CCf-825, equivalent CLI or SNMP commands may be used. For more information regarding the CLI command structure, refer to the FSP 150CCf-825 Etherjack OS (EOS) Command Line Interface Handbook. For more information regarding the SNMP command structure, refer to the FSP 150CCf-825 SNMP User Guide.

Before installing and provisioning the FSP 150CCf-825, familiarize yourself with the FSP 150CCf-825 equipment, its functions and requirements. The following chapters support the installation and operation of the FSP 150CCf-825:

Chapter 1, Installing the FSP 150CCf-825 contains FSP 150CCf-825 feature descriptions and a step by step walk through of the installation process. It is organized in a recommended work flow sequence for new installations and provides support for software upgrades.

Figure 1-1 FSP 150CCf-825 Front Panel

5

PSU1

Status

100 -240V AC

PSU2

Status Critical

Major

Minor

Status

Etherjack TM

Management

RS -232

LAN

4321

2 4 Access

Lk Rate Lk Rate Lk Rate

21

Active

Network FSP150CCf

211 3

840-00028-02 Rev 1.0 Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL Page 1-1

Installation and Operations Manual FSP 150CCf-825Chapter 1 - Installing the FSP 150CCf-825Release 1.2, November 2007 Optical Networking

TM

Chapter 2, Etherjack Service Assurance contains a a detailed description of ESA operation.

Chapter 3, Web Browser Management Tool contains detailed descriptions and procedures for the operation of the eVision web browser management tool, including the following OAMP functions:

• Logging Onto the FSP 150CCf-825, on Page 3-4

• Provisioning Entities in Configuration View, on Page 3-17

• Provisioning LAN Interface(s), on Page 3-17

• Editing Alarm Attributes, on Page 3-40

• Loopback, on Page 3-41

• Etherjack® Diagnostics, on Page 3-42

• Cable Length Benchmark, on Page 3-45

• Etherjack® Connection Performance Analyzer, on Page 3-52

• Editing PM Thresholds, on Page 3-68

• Initializing PM Registers, on Page 3-70

• Scheduled Ping, on Page 3-72

• Users and Security, on Page 3-81

• Software Upgrade, on Page 3-89

• Configuration Database Management, on Page 3-107

• Rescue Image, on Page 3-119

Chapter 4, Communications Provisioning contains procedures to set up the communications management configuration for your site. It provides a summary of supported management configurations and example procedures for various configuration scenarios.

Chapter 5, Configuration Settings and Technical Data contains configuration option setting information to be used as a guide to plan, operate, configure and maintain the FSP 150CCf-825. It contains FSP 150CCf-825 technical specifications, system default settings, configuration options and provisioning rules using the eVision web browser management tool. High level descriptions and provisioning rules are provided for each eVision configuration option. Additional information for each option description can be found in the Application Notes for specific features. For CLI option settings and rules, refer to the Etherjack OS (EOS) Command Line Interface Handbook.

Page 1-2 Copyright © 2007 ADVA Optical Networking - CONFIDENTIAL 840-00028-02 Rev 1.0

Installation and Operations Manual FSP 150CCf-825Chapter 1 - Installing the FSP 150CCf-825


TM

Chapter ContentsThis chapter provides the following information supporting FSP 150CCf-825 installation and provisioning:

Section 1.4 Overview of the FSP 150CCf-825, on Page 1-16 contains major feature descriptions.

Recommended Sequence of Steps for Initial Turn Up of an FSP 150CCf-825, on Page 1-45 provides an overview of the commissioning process and detailed sections to support each step in the commissioning process.

Release Levels Supported in This DocumentThis version of the FSP 150CCf-825 Installation and Operations Manual is applicable to the FSP 150CCf-825 software release 1.2. This version of FSP 150CCf-825 is compatible with the nVision Network Management System software release 9.0 or greater.

AudienceThe reader must have sufficient knowledge of the following when using this document:

• IP addressing

• WAN facility provisioning requirements

• LAN EVC provisioning requirements

• Fiber handling and cleaning procedures (if connecting fiber cables)

• Power handling and connection procedures (if connecting DC power)

Related DocumentationRefer to the following documents for additional information about the FSP 150CCf-825:

• FSP 150CCf-825 Etherjack OS (EOS) Command Line Interface Handbook

• FSP 150CCf-825 Quick Start Guide

• FSP 150CCf-825 Product Description

• FSP 150CCf-825 SNMP User Guide

Documentation FeedbackWe want our manuals to be as helpful as possible. Feedback regarding the manuals are therefore always welcome. You can e-mail your comments/suggestions to:

[email protected]



TM

To submit your comments/suggestions by mail, use the following address:

ADVA AG Optical Networking Technical Documentation Märzenquelle 1-3 98617 Meiningen-Dreissigacker Germany

We appreciate and value your comments/suggestions to improve the quality of our manuals.

1.2 Trouble ClearingIn the event that alarms are raised after commissioning the FSP 150CCf-825, this procedure is provided to assist maintenance personnel in identifying the probable cause and clearing the alarm.

The following procedure lists the steps to identify, isolate, and correct conditions that cause alarms reported in eVision Alarm Window.

Procedure

Step 1 Ensure that an interface device, such as a craft interface, is connected to the network and is operating correctly before continuing.

Step 2 Establish a communication connection to the NID(s) and log on. See Section 3.2 Logging Onto the FSP 150CCf-825, on Page 3-4.

Step 3 Observe the Alarms Window to view all current alarms, and record the alarm severity. See Figure 3-3, on Page 3-8 for an overview of the eVision web browser management tool components and the location of the Alarm Window.

Step 4 Determine which current alarm has the greatest service effect, and record the alarm. Service-affecting (SA) critical alarms should be cleared first, followed by Major SA alarms, and then Minor SA alarms. Then any remaining non-service-affecting (NSA) major alarms should be cleared, followed by any minor alarms.

Step 5 Locate the appropriate alarm indication description and suggested troubleshooting techniques for the specific problem.

Refer to Section 5.8 Alarm Attributes, Probable Cause and Trouble Clearing, on Page 5-49 for identifying, interpreting, and troubleshooting alarms.

Refer to Section 1.6.1 Connectors and LED Descriptions, on Page 1-46 for descriptions of connectors and front-panel LED indications.




TM

Step 6 After performing suggested trouble clearing actions, did the alarm or status condition clear?

If YES:

Record the time the alarm was cleared, and continue with the next step.

If NO:

Obtain ADVA technical assistance (see below).

Step 7 Repeat Step 5 and Step 6 for all alarms.

Step 8 Observe the Alarms Window to view all current alarms. Have all alarm conditions been cleared?

If YES:

Go to the next step.

If NO:

Obtain ADVA technical assistance (see below).

Step 9 Log off all NIDs when finished.

End of Procedure

Obtaining Technical AssistanceProduct Maintenance Agreements and other customer assistance agreements are available for ADVA Optical Networking AG products through your ADVA distribution channel. Technical support is available to warranty or maintenance contract customers who need technical assistance with an ADVA product that is under warranty or covered by a maintenance contract.

To display ADVA’s Technical Support web site that includes all contact information, go to ADVA’s home page at http://www.advaoptical.com and select the “Support” button.

ADVA’s service options include:

• 24 X 7 telephone support

• Web-based support tools

• On-site support

• Technical training, both on-site and at ADVA facilities in Germany and the USA

• Expedited repair service

• Extended hardware warranty service



TM

Partner Login

ADVA’s partner login provides a suite of interactive, networking services that provide immediate access to ADVA information and resources at any time, from anywhere in the world. This highly integrated internet application is a powerful, easy-to-use tool for doing business with ADVA.

The partner login’s broad range of features and services help customers and partners to streamline business processes and improve productivity. Through your partner login, you will find information tailored especially for you, including networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order ADVA training materials.

Access your partner login via the ADVA home page at http://www.advaoptical.com

1.3 Product Features Supported in This Release The FSP 150CCf-825 supports the following new features in software release 1.2:

• A second WAN port may be provisioned with a Link Aggregation Group, providing a 1:1 protection mechanism for the WAN uplink. If one of the physical links fail, traffic still flows through the remaining link.

• 802.1ag Loopback and Link Trace added to the Connectivity Fault Management (CFM) feature.

• Extended Security Banner allows up to 1000 characters, and is configurable from any interface.

• SNMPv3 is extended to support encryption capabilities for increased security.

• Rate shaping at the egress WAN enables oversubscription of client services without exceeding a specified WAN bandwidth. This allows a carrier to force a virtual maximum bandwidth on a WAN port and allows LAN services (EIR) to compete for bandwidth allocation.

The FSP 150CCf-825 also supports the following existing features:

System / Interfaces

• Delivers Ethernet services with support for network termination, traffic management and OAM.

• The Network 1 Gigabit Ethernet interface is presented in both electrical and optical media form. Either media form supports operation at both 100 Mbps and 1000 Mbps rates. The Network interface in copper mode uses an RJ-45 connector (auto-negotiation, auto MDI/MDIX). The Network interface in fiber mode uses an SFP optical transceiver which present the Network Ethernet interfaces as LC connectors. Single fiber transceivers are supported. Both 100 Mbps and 1000 Mbps optical SFPs are supported, and can be configured as dual fiber (1000 BaseLX10 or 1000 BaseLH) or single fiber (1000 Base BX10).




TM

• 4 Client 10/100 Base-T Ethernet copper interfaces via RJ-45 connectors (auto-negotiation, auto MDI/MDIX). The Client 10/100BT Ethernet interfaces support 10 BaseT and 100 BaseTX operation. The Client Fast Ethernet ports are supplied via 4 female RJ-45 connectors located on the front of the unit.

• A Client 1 Gigabit Ethernet interface is presented in both electrical and optical media form, supports auto-negotiation, is capable of operating at 10 Mbps, 100 Mbps and 1000 Mbps line rates in fiber mode, and 100 Mbps and 1000 Mbps rates in optical mode. The Client interface in copper mode uses an RJ-45 connector (auto-negotiation, auto MDI/MDIX). The Client interface in fiber mode uses an SFP optical transceiver which present the Client Ethernet interfaces as LC connectors. Single fiber transceivers are supported. Both 100 Mbps and 1000 Mbps optical SFPs are supported.

• Layer 2 traffic classification: Classification of services based on layer 2 protocol information (i.e., MAC header and VLAN tags) and layer 3 information (TOS, DSCP fields).

• SNMP trap destination and community configuration from GUI allows for easy provisioning of SNMP interfaces.

• Simple Network Time Protocol (SNTP) provides network based timing

• Power: The system is powered by dual AC and/or DC Power Supply Units (PSUs). PSUs can be of similar type or mixed, and are hot swapable.

• Enclosure: The FSP 150CCf-825 is located in a 1U enclosure that provides physical, EMC and safety protection, and supports free-standing, rack mounting and wall mounting installations.

• Supports back-to-back and third party termination applications.

Frame Sizes

• Jumbo Ethernet frames up to 9250 bytes are supported on Network and Client 1 Gigabit Ethernet interfaces.

• The support of Jumbo frames can be enabled or disabled at the system level via configuration setting. When disabled, the maximum frame size accepted at the traffic-bearing Ethernet ports is 2000 bytes.

• The system limits the maximum frame size of management tunnel frames to 1400 bytes to ensure inter operability across networks which employ multiple stacked tags.

Untagged Service Flows at the Client Port

• Client Ethernet ports may be operated in a VLAN aware or VLAN unaware mode. A customer port operating in “Transparent” mode is VLAN unaware; when operating in “Flow-VLAN” mode, a customer port is made VLAN aware.

• A system configuration parameter is associated with each Client Ethernet port that defines the forwarding mode for both tagged and untagged frames. The “Tagged Frame Filter” parameter defines whether to forward (default) or discard tagged frames arriving at the Client port. The “Untagged Frame Filter” defines whether to forward (default) or



TM

discard untagged frames arriving at the Client port. Priority tagged frames are treated as untagged frames for the purpose of filtering. The Tagged Frame Filter and Untagged Frame Filter parameters can be set when a Client port is operating in either Transparent or Flow-VLAN mode.

Single Tagged Flows at the Client Port

• When a Client port is operated in a VLAN aware (Flow-VLAN) mode; untagged and tagged ingress frames are treated differently.

• The CoS priority of a single tagged VLAN flow is identified by the VLAN priority of the outer tag.

• The VLAN ID identifies the switching path; the VLAN priority identifies the CoS priority.

Client Ethernet Virtual Circuit Connection

• A Client Ethernet virtual circuit connection is identified by a unique X-tag at a Client Ethernet port. In the upstream direction, the system can translate this X-TAG value into any S and C tag combination at the network interface. In the downstream direction, the system can translates the S and C tag combination into an X-TAG value.

Network Ethernet Virtual Circuit Connection

• A network Ethernet virtual circuit connection is identified by a unique S and C tag combination at the network Ethernet port. Both the outer and inner VLAN IDs can be any valid value. The CoS priority of frames within a double tagged VLAN flow is identified by the VLAN priority of the outer tag.

Egress Port Rate Limiting

• The system supports per-port rate limiting at the egress of each Client Ethernet port. The system can distinguish up to 8 CoS associated with egress port rate limiting. Up to 8 queues can be assigned to a customer port to perform egress rate limiting using CoS differentiation.

Flow Control

• The system supports flow control using PAUSE frames per IEEE 802.3x on all Ethernet ports. Flow control can be enabled and disabled independently on each port. Separate controls are provided for Receive and Transmit directions to allow individual control over generating and responding to PAUSE frames.

Ingress Policing

• The system supports policing in the ingress path of customer Ethernet ports. Policing flows can be defined by any combination of port VLAN ID(s) and VLAN priority parameters. The system supports up to 472 upstream ingress QoS queues which can be scheduled independently. The system supports up to 40 downstream egress queues which can be scheduled independently. This allows for CoS scheduling at the customer ports.




TM

• The system supports Committed Information Rate (CIR), Excess Information Rate (EIR), Committed Burst Size (CBS) and Excess Burst Size (EBS) service parameters for each service flow.

• Packets marked red are discarded immediately at the policer.

• Packets which are marked green are forwarded unmodified.

• Counts of Red, Green and Yellow frames for each port are maintained by the system.

Policing and Traffic Buffering

• A policing function which utilizes a token refresh concept is employed to police traffic at Client Ethernet port ingress.

• Frames are tail-dropped if there is no room for a frame in the destination QoS queue.

Traffic Shaping and Scheduling

• The system provides the option for per-QoS flow shaping and per-QoS flow CoS queuing at the network Ethernet port.

• The system provides per-class scheduling at the Client Ethernet ports. Up to 8 CoS values can exist per port.

MAC Bridging

• The system supports a proprietary form of MAC bridging known as MAC to TAG translation which switches MAC frames between customer Ethernet ports and network EVCs on the network Ethernet ports.

Layer 2 Control Protocol Transparency

• Metro Ethernet Forum compliance for Layer 2 Control Protocol Disposition (CPD)

Local Management Ethernet Port

• Management interface via RJ-45 10/100 Base-T LAN port or RJ-45 RS-232 Serial Console port with Auto MDIX capability.

• The system supports DHCP on the management LAN to obtain its IP address from a central server.

• The local management LAN port can be disabled via configuration setting over any of the management interfaces supported on the system to prevent access into the carrier’s management network or launching denial of service attacks toward the local host processor. The port can be enabled and disabled via remote management access.

Communications and Management Connectivity

• Management tunnel connectivity may be established on both Network and Client Ethernet interfaces as a VLAN or Ethernet MAC-based channel.

• In IP over Ethernet mode, management tunnels support ARP. A maximum of 20 ARP entries are supported. The Aging process is applied on ARP cache entries (default 5



TM

minute aging).

• In IP over Ethernet mode, management tunnels support Proxy ARP. The system allows user to retrieve the ARP cache.

• The system maintains one IP address associated with the local management LAN port. When routing is enabled, the system maintains an IP address per interface (management LANs on Network and Client interfaces).

• The IP/ETH management tunnel supports a Default Gateway setting.

• RIPv2 is supported on management tunnels and local management LAN port.

• Security features include: user access security levels, Secure Sockets Layer (SSL) support for security of Secure Hypertext Transfer Protocol (HTTPS) and Secure Shell (SSH) management protocols. Telnet and HTTP protocols may be disabled to ensure secure access.

• The system provides an HTML-based GUI interface for all controls, administration, monitoring and operations. This is accessible via HTTPS on any of the Ethernet management interfaces (local and remote).

• Scheduled Ping provides a current state of management link connectivity. A list of IP addresses are pinged periodically and the results are analyzed. The ping rate and alarm activity are provisionable. All Scheduled Ping attributes are stored in non-volatile memory. Any enabled Scheduled Ping will resume after an FSP 150CCf-825 warm or cold restart.

Management and Management Protocols

• The system supports SSH (secure shell) for ASCII-based CLI access.

• The system supports HTTPS for the GUI interface.

• Web interface can be disabled via configuration parameters.

• SNMP v1, v2c and v3 support.

• The product supports an enterprise MIB for proprietary technology (such as Etherjack diagnostics, Etherjack CPA and Etherjack Service Assurance).

• The product supports a proprietary enterprise MIB for port/service configuration and for communications management.

Software Load Management

• The system software image is stored in non-volatile memory. Two software versions may be stored in the system at one time - a primary or active image and a backup or standby image.

• Software image versions are visible via all management interfaces and software image integrity is maintained via checksum.




TM

• The system supports a Software Upgrade capability accessed and controlled via the management LAN port as well as management tunnels.

• FTP and HTTP(S) protocols are used to transfer software loads from a remote server to RAM. If the file transfer is successful, the system then writes the new software image to the NV-memory.

• The software copy and upgrade actions are separate events. A software copy can take place without an automatic software upgrade. The software upgrade may be performed at a later time.

Database Management

• All configuration settings can be stored in non-volatile memory.

• The system supports remote database back up and restore. The database may be copied to a remote server (using FTP or HTTP file copy) for secure storage and later restored to the system. Each system software release provides the means to convert and utilize the configuration database from the prior 2 older releases. Only forward compatibility of configuration databases is required.

Configuration Management

• CLI “show running-config” command provides the ability to capture a current FSP 150CCf-825 configuration which may be edited and re-played to other FSP 150CCf-825s. The output consists of a sequence of input commands required to duplicate the configuration (starting from the default configuration).

Configuration Change Protection

• Validation Timer is a “Safe Mode” transaction mechanism to allow a remote operator to make changes to system configuration without the fear of permanent loss of communication. This safe mode transaction can be enabled prior to making a configuration change. In the event that the configuration change results in loss of communication to the device, the device will reset itself after a configurable timeout to the previous configuration settings, restoring communications.

• The system maintains a database checksum record which is automatically recalculated after each configuration database change. This checksum is accessible via an SNMP MIB variable.

System and SFP Inventory

• Inventory information is programmed in the factory and may be retrieved through management interfaces. Factory programmed information includes the following data: hardware part number, hardware revision, serial number, date of manufacture, and MAC address information of all Ethernet ports (management, Network and Client).

• The system can read the inventory of optical SFP units inserted and can display the following information: manufacturer, manufacturer part number, serial number, and date of manufacture



TM

Alarms and Performance Monitoring

• WAN and LAN facility alarm monitoring, and near end/far end performance monitoring.

• GR-253/GR-820 style PM parameters and features.

• The system maintains current bins for both 15 min and 1 day interval for all the counters.

• The system maintains 32 history bins for 15 min interval for all the counters and 1 history bin for 1 day interval for all the counters.

• A real time clock applies time stamps to all alarms, PMs, and system log events.

• Event log browser: A graphical interface to view all log history.

• Autonomous Output (AO) messages, including alarms and PM threshold crossings, are stored in non-volatile memory. The AO buffer contains a circular buffer that maintains up to 250 entries.

EFM Link Layer OAM

• The following Ethernet OAM features are supported: provisionable activation of the OAM sublayer, operation in active mode only, OAM Discovery, Remote Failure Indication, OAM Remote Loopback, and Dying Gasp Critical Link Event.

• Provisionable on/off Dying Gasp message via SNMP on a per port basis (when disabled, no dying gasp messages are generated on the port). When enabled, SNMP dying gasp trap messages are sent on EFM-enabled interfaces. Provisionable on/off “Dying Gasp” message is available to be transmitted on both the LAN and WAN interfaces on detection of power loss.

• A node receiving an EFM-OAM message, such as the dying gasp message, raises an alarm on the interface on which it was received. The alarm is cleared when a valid signal is subsequently detected on the interface or when a manual action is taken to remove the alarm. If EFM-OAM is disabled on a port, the port will not generate any EFM-OAM related alarms.

Service Layer OAM

• Service layer Ethernet OAM using IEEE 802.1ag Connectivity Fault Management (CFM) mechanisms as defined in Section 9.3.2.

• A Maintenance Association End Point (MEP) is supported on a single service provider Maintenance Association (MA) level at each Client port. The system supports service layer OAM for network EVC connections in both connectionless and connection- oriented services.

• A MEP can be configured to transmit Continuity Check Messages (CCMs) at a configurable rate and to process received CC messages. A MEP can be associated with one or more service identifiers. When a MEP transmits a CC message, it includes the service identifiers in the CC message. When a MEP receives a CC message, it checks that the service identifier(s) in the message match its list of valid service identifiers. If




TM

there is a mismatch, the MEP raises a fault indication.

• Link Trace Message (LTM) is used for path discovery and fault isolation. LTM messages are multicast frames that a MEP transmits, at user request, to track the path (hop-by-hop) to destination MEP. At each MIP along the path to the target, the LTM is forwarded to the next hop and a Link Trace Response message (LTR) is sent back to the originating MEP. This process is repeated until the LTM reaches the intended target, or the LTM can no longer be forwarded. Based on the information in the LTRs received, the originating MEP can determine the path to the target if the Link Trace was successful, or the location of the fault in the event of a failure.

• Loopback Messages (LBMs) are unicast messages that a MEP transmits, at user request, to verify connectivity to a particular maintenance point. LBMs may also contain additional data in the payload to measure performance characteristics of the service. At the destination maintenance point, a Loopback Reply Message (LBR) is transmitted back to the originating MEP. A reply to a loopback message indicates whether a destination is reachable but does not contain hop-by-hop discovery of the path.

User and System Security

• Up to 10 user accounts are supported. Four user security levels are available as: Superuser, Provisioning, Maintenance and Retrieve.

• GUI login time-out security feature provides a provisionable login time-out for each user ID.

• RADIUS authentication.

• Configurable encryption private keys for SNMPv3, and SNMPv3 is updated to support authentication and privilege functions.

• SNMP has been enhanced to support the DES encryption scheme.

• Terminal Access Controller Access Control System Plus (TACACS+) user authentication. TACACS+ protocol is TCP-based for enhanced security. It allows greater levels of control over user actions and can be used to create separate administrative groups that are based on user functionality/authentication levels. TACACS+ version 0xc0 will be supported along with minor versions of 0x0 and 0x1.

• All autonomous events, alarms and messages generated by the system are written to the syslog. The system supports 250 entries in the syslog in a circular buffer. The syslog can be written to FLASH memory in order to ensure survival of all restarts and power failures. A user settable option controls whether the syslog is written to FLASH memory.

• Security banner. This feature allows an operator to define a custom security banner which is displayed whenever a user logs onto the system. This banner is displayed on CLI and web browser logins. The system is shipped with a default security banner.

Security and Network Protection

The system implements the following mechanisms to safe-guard itself against Denial of



TM

Service (DOS attacks), slow protocol frames and spoofing:

• For connection oriented services, customer broadcast frames are switched within the statically configured service flows, which prevents broadcast storms from affecting other services and/or the network.

• For connectionless (MAC bridging) services, the broadcast domain is limited to the NTE, which is dedicated to a single customer. Beyond the NTE, broadcast frames are statically switched through the network in an EVC.

• When the MAC to TAG MAC Learning and forwarding features is not enabled on a customer E/FE port then no MAC learning is performed and there is no susceptibility to a MAC learning DOS attack.

• When the MAC to TAG MAC Learning and forwarding features is enabled on a customer port configured for transparent operation, then MAC learning is performed on ingress traffic from the network port.

• The system limits the processing of slow protocol frames to a defined number per second in order to prevent the Ethernet NTE from collapsing when subject to a excessive number of customer originated slow protocol frames. A default number shall be used that prevents the Ethernet NTE from collapsing under the load. It shall be possible to modify this number from the Element Management system.

• The system maintains an optional Access Control List (ACL) to implement security on management tunnels and local management ports. The ACL allows the operator to add sub-networks or individual IP addresses and allocate them to management tunnels and/or local management interfaces. When the ACL is active, management of the system is restricted only to those valid IP addresses contained in the ACL.

Etherjack® Diagnostics and Loopback

• Ethernet ports support port diagnostic using an internal port loopback

• The Client Fast Ethernet and Gigabit electrical Ethernet ports support virtual cable test using TDR diagnostics (Etherjack diagnostics).

• Advanced Etherjack Connection Performance Analyzer (ECPA) capability simplifies test and turn-up.

• WAN port VLAN loopback for both ingress and egress.

• WAN and LAN physical port level loopback.

• LAN facility loopback (port and VLAN). This allows the port or VLAN to be looped back towards the facility (line).

• Timed Loopback. This option allows the NOC to configure a port into loopback with a preset time, at the expiration of which the loopback is released.

• Cable length benchmark feature provides a means to save and recall up to 5 cable segment lengths during the installation process. When subsequent cable length tests are executed, they can be compared to the original installation. With the original cable




TM

length(s) captured, the test operator can quickly determine if a cable open connection is located at a particular patch panel, possibly preventing the need to dispatch maintenance personnel to the remote site.

• Etherjack Service Assurance (ESA) feature provides Service Level Agreement (SLA) Monitoring for Ethernet services. ESA reports Frame Delay Performance, Frame Delay Variation Performance and Frame Loss Ratio Performance, as defined by standards that are currently in progress.

• Scheduled ESA.

Fault Propagation

• Provisionable WAN and LAN Facility Fault Propagation (WFFP and LFFP) notifies upstream equipment and CPE equipment of a failure on the WAN or LAN facility. An “EFM - Remote Link Down (RLD)” option is provisionable, where an RLD message received on the WAN port may result in fault propagation to the LAN port.

• Fault propagation hold-off feature provides a programmable delay before fault propagation is enacted between LAN and WAN ports. This provides filtering of short duration faults and prevents the network from over-reacting to customer network changes.



TM

1.4 Overview of the FSP 150CCf-825The FSP 150CCf-825 provides WAN interface media conversion to up to 4 client 10/100 Base-T LANs and/or one client 1 GbE LAN. The FSP 150CCf-825 can be terminated on third party ADMs in the telco to provide access to service provider data networks (see Figure 1-2), or two FSP 150CCf-825 units can be used back-to-back to extend Ethernet private lines over leased optical facilities (see Figure 1-3).

The FSP 150CCf-825 is configured with default factory settings, however, you may wish to modify these settings (refer to Section 5.2 System Default Parameters and Maximum Bandwidth, on Page 5-2 for FSP 150CCf-825 default settings).

Figure 1-2 CO Aggregation Application

Figure 1-3 Point-to-Point Application

Up to 4 x 10/100BTUp to 4 x 10/100BT

Up to 4 x 10/100BTUp to 4 x 10/100BTCentral Office orCo-location space

CC-nVision

FSP 150CC

Ethernet loopbacks enable CO-based testing

VLAN mgmnt tunnel

FSP 150CC

VLAN mgmnt tunnel Ethernet or EoTDM

Ethernet orEoTDM

ADM 10/100/1000BTor GbE

10/100/1000BTor GbE

10/100/1000BTor GbE

10/100/1000BTor GbE

Up to 4 x 10/100BT

10/100/1000BTor GbE

Up to 4 x 10/100BTUp to 4 x 10/100BT

10/100/1000BTor GbE

10/100/1000BTor GbE

VLAN mgmnttunnel

Central Office

CC-nVision

FSP 150CC

Ethernet loopbacks enable CO-based testing

FSP 150CC10/100/1000BTor fiber GbEthernet

Ethernet or EoTDM




TM

The FSP 150CCf-825 is designed for use in a desktop or communications closet environment. Wall-mount and rack-mount options are also available. The chassis is 1.75 inches high, 17.2 inches wide and approximately 8.6 inches deep. The FSP 150CCf-825 is convection cooled (no fans or filters). A heat deflector should be installed between a group of four FSP 150CCf-825s and heat generating equipment or heat sensitive equipment (refer to Section 5.13.5 Technical Specifications List by Functional Area, on Page 5-91 for details). Its operating temperature is 0 to +50 C, and a relative humidity range of 5% to 95% non-condensing. The system is powered by dual AC and/or DC Power Supply Units (PSUs), and optionally, an external AC to 12 VDC power converter.

eVision Web Browser Management ToolEach device supports an eVision web browser management tool to provide a GUI-based interface for Operation, Administration and Maintenance (OA&M) functions. For more information on eVision web browser management tool operation, see Chapter 3, Web Browser Management Tool.

Command Line InterfaceAlthough this document focuses on using the eVision web browser for configuring and monitoring the FSP 150CCf-825, equivalent CLI commands may be used. The FSP 150CCf-825 CLI command structure provides a text-based system for local configuration and management of FSP 150CCf-825 functions. CLI access may be attained via RS-232 Serial Console Port direct connection, or telnet / ssh session. For more information regarding the CLI command structure, refer to the Etherjack OS (EOS) Command Line Interface Handbook.

Simple Network Management Protocol (SNMP)Although this document focuses on using the eVision web browser for configuring and monitoring the FSP 150CCf-825, equivalent SNMPcommands may be used. The FSP 150CCf-825 SNMP MIB provides a system for remote configuration and management of FSP 150CCf-825 functions. For more information regarding the SNMP command structure, refer to the SNMP Users Guide.



TM

1.4.1 Service ApplicationsIn general, the FSP 150CCf-825 implements E-LINE service types as defined by the Metro Ethernet Forum (MEF). The MEF defines an Ethernet Virtual Connection (EVC) as an association between two or more User Network Interface (UNI) points in a network, where the UNI is a standard Ethernet interface that is the demarcation point between the customer and the service provider. A UNI represents a client Ethernet port on the FSP 150CCf-825.

An E-LINE service type is based on a Point-to-Point Ethernet Virtual Connection (EVC). The service types supported by E-LINE include Ethernet Private Line (EPL) and Ethernet Virtual Private Line (EVPL), as defined by the MEF. The FSP 150CCf-825 also supports Ethernet Private LAN and Ethernet Virtual Private LAN services when used in conjunction with metro edge and metro core devices that implement multi-point bridged services. (For more details regarding service applications, refer to the FSP 150CCf-825 Product Description.) In the FSP 150CCf-825, UNIs operate in one of two modes: Connection-oriented or Connection-less.

Connection-Oriented ServicesIn Connection-oriented mode, client Ethernet frames from a UNI are statically mapped to a network EVC based on the client port, client VLAN, frame priority, or some combination thereof. Connection-oriented mode supports E-LINE service types providing EPL and EVPL service offerings. An example is shown in Figure 1-4.

A Connection-oriented UNI which maps all client frames to a single EVC is said to operate in “Transparent” mode, as is the case for UNI-1 in Figure 1-4. UNI-2 maps some frames to one EVC and other frames to another EVC. In the example, UNI-2 uses a single VLAN tag to determine which EVC to address. Such a service is referred to as a single-tagged multiple-service offering. UNI-3, in contrast, maps frames with a single VLAN 404 to an EVC. This type of offering is referred to as single-tagged single-service.

Figure 1-4 Connection-Oriented UNI-EVC Mapping (Static Mapping)

UNI-1

UNI-2

UNI-3

Network Port

Network EVCsUNI <–> EVC

MappingUNI-1 All frames

UNI-1 VLAN 404

UNI-2 VLAN 56

UNI-2 VLAN 405

UNI-1

UNI-2

UNI-3

Network Port


MappingUNI-1 All frames

UNI-1 VLAN 404

UNI-2 VLAN 56

UNI-2 VLAN 405




TM

Connection-Less ServicesThe system supports MAC bridging between customer UNIs and network EVCs that are configured as bridge ports, as illustrated in Figure 1-5. A proprietary form of MAC bridging is supported for ingress packets received on customer UNIs. This proprietary form of MAC bridging is known as MAC to TAG.

The system supports up to 5 instances of the MAC BRIDGE to enable partitioning between multiple customers. A MAC bridge instance attaches at most one customer Ethernet port but may connect to multiple network EVCs.

In Connection-less mode, client frames from a UNI are dynamically mapped to one or more network EVCs based on the frame’s destination MAC address. This mechanism enables support of point to multipoint network topologies. In Connection-less mode, the system performs MAC learning on frames to determine on which EVC to forward the frame. If the system does not know where to forward the frame, it replicates and broadcasts the frame on all EVCs associated with the service.

The system maintains a mapping between MAC Bridge, network EVC port and customer UNIs. A customer UNI may be associated with multiple network EVCs.

In the upstream direction, an S-tag and optionally a C-tag are added to all frames that are forwarded to a network EVC. In the downstream direction S-tag and C-tags are stripped from all frames received at the network EVC.

Customer VLAN tags can be optionally switched through the bridge transparently, i.e., the port can be operating in VLAN unaware mode while in Bridged mode.

Figure 1-5 Connection-less UNI-EVC Mapping (Dynamic MAC-Based Mapping)

UNI-1

UNI-2

UNI-3

Network Port


Mapping

MACTable

MACTable

MAC bridging instance

UNI-1

UNI-2

UNI-3

Network Port


Mapping

MACTableMACTable

MACTableMACTable

MAC bridging instance



TM

1.4.2 ADVA’s Etherjack® TechnologyMost carriers are delivering or will soon be delivering Ethernet based services to their small to medium business customers. Ethernet has been the physical medium of choice for decades in the enterprise environment, and forward looking carriers are offering Ethernet services as a way to simplify their customer’s networking challenges.

Unfortunately, Ethernet was designed as a local area network (LAN) solution and is not well suited for carrier’s wide area network (WAN) environment. While traditional data services such as frame relay and private line T1/T3s offer many levels of performance monitoring and fault isolation, Ethernet has a limited set of parameters for these tasks. In addition, traditional carrier services have a well-defined hand-off specifications and demarcation points which do not exist in the Ethernet world. ADVA’s FSP 150CCf-825 adds Ethernet capability to first generation transport systems and can also add Virtual LAN (VLAN) support to second generation systems.

In addition to providing media conversion, ADVA’s Etherjack® technology provides carriers with an intelligent Ethernet demarcation device that is aligned with emerging Ethernet OAM standards for transport, connectivity and services from IEEE, MEF and ITU standards bodies.

ADVA's patented Etherjack® technology allows carriers to deploy profitable Ethernet services by providing carrier grade remote monitoring and diagnosis for Ethernet based services. This capability is analogous to the Smartjack™ capability used as a demarcation point for traditional T1 services (see Figure 1-6).

While early data services were delivered blind, without demarcation capability, carriers quickly determined that remote management was critical to providing value-added services to their customers while reducing truck rolls and the expense of diagnosing an Ethernet service problem.

ADVA’s Etherjack® technology includes performance monitoring, remote failure indications (e.g., dying gasp), remote loopbacks, cable integrity testing and Etherjack Connection Performance Analyzer (ECPA) to provide diagnostics through the carrier network and on both sides of the demarcation point (see Figure 1-7).

Figure 1-6 Demarcation for Traditional T1 Services

Smartjack orCSU/DSU

V.35

Carrier Network

Switch/Router

Customer Network

T1ADM orModem




TM

Using Etherjack® technology, the FSP 150CCf-825 monitors the performance of Ethernet services and provides carriers with advance visibility of performance degradation (RMON Etherstats) before an outage occurs. The Ethernet performance data is presented in 15 minute bins just like traditional T1 performance data, and can provide indication of whether a fault is a one time event, or an on-going problem.

When a fault occurs, the FSP 150CCf-825 provides fault isolation and diagnosis of both the carrier network as well as the final Cat5 connection to the customer premise equipment (CPE). It enables a carrier to diagnose Ethernet cable faults to determine if the customer's Cat5 cable is open-circuit, short-circuit or properly terminated.

When Etherjack® locates a cable fault; it will provide the distance from a FSP 150CCf-825 Ethernet port to the cable fault to the nearest meter. In addition, the FSP 150CCf-825 can detect if an Ethernet cross-over cable has been improperly installed on the LAN port, and re-configure its port to compensate for the improper wiring. These unique isolation and diagnosis capabilities can dramatically reduce the quantity and duration of truck rolls necessary to maintain Ethernet services.

Figure 1-7 Etherjack Demarcation for Ethernet Services

ADM,Modem or

Media converter

Carrier Network

Switch/Router

Customer Network

Ethernet or EoTDM 10/100/1000BTor GbE

FSP 150CCADM,Modem or

Media converter

Carrier Network

Switch/Router

Customer Network

Ethernet or EoTDM 10/100/1000BTor GbE

FSP 150CCFSP 150CC



TM

Etherjack® Performance Monitoring

Etherjack® Performance Monitoring allows carriers to detect and react to potential failures prior to a customer outage. In addition to providing traditional SNMP MIB Etherstats, Etherjack provides GR-253/GR-820 style PM parameters and features similar to those found on traditional SONET and T1 services. This allows Ethernet service assurance to be integrated into a carrier’s existing Service Assurance infrastructure. Etherjack Performance Monitoring supports threshold setting and automatic TCA message/trap generation. Current and history PM bins provide a continuous record of service performance, allowing for accurate SLA conformance statements. PM counts can be displayed in either tabular or chart format. See Figure 1-8 for an example of PM counts displayed in chart format in ADVA’s on-board eVision Web Browser Management Tool.

For additional information on Etherjack® Performance Monitoring using eVision, see Section 3.8 Performance Monitoring, on Page 3-63. For information on the PMs available and default settings, see Section 5.9 Performance Monitoring Settings, on Page 5-58.

Figure 1-8 Performance Monitoring View with Counts in Chart Format




TM

Etherjack® Diagnostics

Etherjack® diagnostics provide a suite of tests to isolate faults between carrier equipment, customer equipment and Ethernet cables:

• Ethernet port loopbacks to verify driver and receiver issues

• Ethernet LAN cable diagnostics to detect open-circuit, short-circuit conditions

• Manual restart of Ethernet auto-negotiation sequences (to detect one-way failures and MDIX conditions)

The FSP 150CCf-825 can monitor the status of a physical Ethernet link to determine whether the link is properly terminated, improperly terminated, open-circuit or short-circuit. See Figure 1-9 for an example of Etherjack diagnostics results using the eVision Web Browser Management Tool. For additional information on Etherjack Diagnostics using eVision, see Etherjack® Diagnostics, on Page 3-42.

Figure 1-9 Etherjack® Diagnostic Results Using eVision



TM

Cable Length Benchmark

An addition to Etherjack® diagnostics results is the cable length benchmark feature. This feature provides a means to store up to 5 cable segment lengths during the installation process. Each cable segment can be named with a text string to describe the physical location of each segment. If a subsequent Etherjack diagnostic detects an open circuit at one of the stored segments, eVision will highlight the location name of the faulty segment, and the test operator can quickly determine if the fault is located at a particular patch panel, possibly preventing the need to dispatch repair personnel.

See Figure 1-10 for an example of Etherjack diagnostics results highlighting the open segment location. For additional information on Cable Length Benchmark using eVision, see Cable Length Benchmark, on Page 3-45.

Figure 1-10 Faulty Segment Identified Using Cable Length Benchmark




TM

Port, VLAN and EFM-OAM LoopbackTo assist with Ethernet service fault isolation and to support Service Level Agreement (SLA) conformance verification, ADVA’s family of FSP 150CCs support port, VLAN and EFM-OAM message loopback modes on all LAN and WAN ports (see Note). This feature allows the operator to set up an Ethernet test-set at a central location to inject traffic into the network (see Figure 1-11).

As shown in the example in Figure 1-11, traffic is looped back into the network and back to the test-set. The test-set can look for any anomalies such as frame loss or out-of-sequence frames. The loopback eliminates the need to connect a test-set in the field or at the customer premise to verify round-trip service.

Three basic types of loopback are available: Port, VLAN and EFM-OAM. The following loopback functions are available:

• Terminal Loopback

• Terminal Timed Loopback

• Facility Loopback

• Facility Timed Loopback

• Terminal VLAN Loopback

• Facility VLAN Loopback

• Remote EFM-OAM Loopback

Note: For WAN interfaces when LAG is present, only a WAN-1 or WAN-2 loopback may be applied at a time. They cannot be applied simultaneously on WAN-1 and WAN-2.

Figure 1-11 CO Based Testing Using Ethernet Loopback

CO Based Test Head

Test Pattern 1Test Pattern 2

Central Office

LoopbackLoopback

FSP 150CC FSP 150CC

Customer Premise Customer Premise

CO Based Test Head

Test Pattern 1Test Pattern 2

Central Office

LoopbackLoopback

FSP 150CC FSP 150CC

Customer PremiseCustomer Premise Customer PremiseCustomer Premise



TM

Port LoopbackPort loopbacks consist of Terminal and Facility loopbacks, which may be applied in a constant or timed manner. A terminal loopback connects all traffic frames about to be transmitted from the port to the associated, incoming receiver (see Figure 1-12). This operation also enables testing of internal receivers and transmitters. Placing a port in facility loopback mode connects all traffic frames received from the port to the associated transmitter (see Figure 1-13).

Both terminal and facility loopbacks will loop back all traffic frames (including EFM-OAM messages), resulting in a disruption of service. Selecting the timed loopback option can minimize the amount of time service is disrupted while allowing a specified duration of testing.

Figure 1-12 Terminal Loopback (without Swap SA/DA)

LAN WANTX

RX TX

RX

LAN Terminal Loopback

FSP 150CC

Figure 1-13 Facility Loopback (without Swap SA/DA)

LAN WANTX

RX TX

RX

LAN Facility Loopback

FSP 150CC

All traffic is looped back, including EFM-OAM messages

All traffic is looped back, including EFM-OAM messages

LAN WAN

RX

TX RX

TX

WAN Terminal Loopback

FSP 150CC

LAN WAN

RX

TX RX

TX

WAN Facility Loopback

FSP 150CC




TM

A simple terminal or facility loopback is sufficient for back-to-back FSP 150CCf-825 configurations with no Layer 2 cloud between them. However, if a Layer 2 cloud does exist between each FSP 150CCf-825, traffic will not reach its intended destination (see Figure 1-14). Within each Ethernet frame is a MAC address from which the frames are sent (Source Address) and the MAC address of the intended recipient of those frames (Destination Address). A Layer 2 cloud looks at the Destination Address to determine where to send the frames, and if the Destination Address is the same address from where the frames are received, the Layer 2 cloud will discard the frames.

Selecting the Swap SA/DA [Swapping the Source Address (SA) with the Destination Address (DA)] option during the loopback will direct the FSP 150CCf-825 to look up the MAC address of frames being received and swap out the Source Address with the Destination Address, allowing the Layer 2 cloud to forward the frames (see Figure 1-15). This function is performed by the Media Controller Converter (MCC). Only one Swap SA/DA loopback may be performed per system. Once a Swap SA/DA loopback has been operated, a second Swap SA/DA loopback may not be performed on another entity.

Although the following examples show LAN loopbacks, the same applies to WAN loopbacks.

Figure 1-14 LAN Terminal Loopback (without Swap SA/DA)

LAN WAN

TX

RX TX

RX

FSP 150CC

LANWAN

TX

RXTX

RX

FSP 150CC

Layer 2 Cloud

(MAC Address: 00:0B:90:00:08:32)(MAC Address: 00:0B:90:02:8A:31)

SA MAC: 00:0B:90:02:8A:31

SA MAC: 00:0B:90:00:08:32

Media Converter Controller:

DA MAC: 00:0B:90:00:08:32

FRAMES:

FRAMES:

DA MAC: 00:0B:90:02:8A:31Swap SA/DA

Figure 1-15 LAN Terminal Loopback (with Swap SA/DA)

LAN WAN

TX

RX TX

RX

FSP 150CC

LANWAN

TX

RXTX

RX

FSP 150CC

Layer 2 Cloud

(MAC Address: 00:0B:90:00:08:32)(MAC Address: 00:0B:90:02:8A:31)

SA MAC: 00:0B:90:00:08:32

Media Converter Controller

FRAMES:

DA MAC: 00:0B:90:02:8A:31

SA MAC: 00:0B:90:00:08:32FRAMES:

DA MAC: 00:0B:90:02:8A:31

X



TM

VLAN LoopbackBoth terminal and facility loopbacks send all traffic frames, and therefore result in an out-of-service disruption of service for the time the loopback is applied. The VLAN loopback function can select egress frames with a specific VLAN ID to be looped back without disrupting normal EVC traffic. During a VLAN loopback, only the specified VLAN traffic is looped back. All other traffic is forwarded, preventing any disruption of service. See Figure 1-16. This function is performed by the Media Controller Converter (MCC). Only one VLAN loopback may be performed per system. Once a VLAN loopback has been operated, a second VLAN loopback may not be performed on another entity. For WAN, selection and entry of Inner Tag and/or Outer Tag VLAN IDs are possible.

EFM-OAM LoopbackIEEE compliance requires EFM-OAM frame integrity when a loopback is in place. The EFM-OAM loopback (which is similar to a facility loopback) performs this function by processing all EFM-OAM frames while looping back all other traffic. The EFM-OAM loopback function is performed by the Media Controller Converter (MCC). See Figure 1-17. Note that the Remote EFM-OAM loopback includes management traffic, therefore management traffic is dropped while the Remote EFM-OAM loopback is active. Since all EFM-OAM frames are still processed, when the loopback is released, management connectivity will also be restored.

Figure 1-16 LAN Terminal VLAN Loopback

Figure 1-17 EFM-OAM Loopback

LAN WAN

TX

RX TX

RX

FSP 150CC

LANWAN

TX

RXTX

RX

FSP 150CC


Selected VLAN(s) are looped back,all other frames are forwarded

VLAN ID = 4094-0

All Other Traffic

LAN WAN

TX

RX TX

RX

FSP 150CC

LANWAN

TX

RXTX

RX

FSP 150CC


EFM-OAM messages are processed,all other frames are looped back

All Other Traffic

All EFM-OAM EFM-OAM CPD set to PeerMessages Processed

Remote EFM-OAM Loopback command sent from this FSP 150CC




TM

Etherjack® Connection Performance AnalyzerWhile port and VLAN loopback functions provide a means to manually test end-to-end EVC circuits, multiple test suites are required, and the result of the tests performed will estimate end-to-end throughput, latency, jitter, etc. ADVA’s Etherjack Connection Performance Analyzer (ECPA) provides a means to test end-to-end EVC circuits, and provides a measurement of actual customer throughput, latency, jitter, etc. (see Figure 1-18).

The Etherjack® Connection Performance Analyzer (ECPA) provides a subset of Ethernet test equipment functions embedded directly into the port cards so that each individual Ethernet port can act as its own “test equipment.” This provides a means to test EVC connectivity and verify service conformance from a remote location without the need for external test equipment.

The ECPA feature can be controlled remotely from a Network Management terminal anywhere in the network. Together with port and VLAN loopback functions on each ECPA port, ECPA allows in-service end-to-end EVC traffic testing.

Etherjack™ Connection Performance Analyzer:

• Provides a subset of Ethernet test equipment functions embedded directly into the Provider Equipment so that each individual Ethernet port can act as its own test equipment.

• Provides a management feature which allows the FSP 150CCf-825 to be controlled remotely from a Network Management terminal anywhere in the network.

• Allows service verification for new point-to-point EVCs on a multipoint Ethernet port without disrupting other “live” connections on the same port.

• Provides a port loopback on each Ethernet port which loops egress traffic back to the ingress path. This allows end-to-end traffic testing.

• Provides a VLAN loopback capability to allow only selected VLANs (up to 3) to be looped back at a port

Figure 1-18 End-to-End EVC Circuit Testing Using ECPA

Test Pattern

Central Office

Loopback

FSP 150CC FSP 150CC

Customer Premise Customer Premise

ECPATest Pattern

Central Office

Loopback

FSP 150CC FSP 150CC

Customer PremiseCustomer Premise Customer PremiseCustomer Premise

ECPA



TM

ECPA functionality is implemented by a combination of hardware and software components. The hardware component is used to insert Ethernet test frames into an EVC connection and to monitor test frames received from an EVC connection.

The FrameInjector and FrameMonitor blocks lie in the data-path on each service card. The Input of the FrameMonitor can be connected to the ingress or egress data path on the card so that frames can be monitored in either direction. The output of the FrameInjector can be connected to either ingress or egress data path. In addition, a VLAN loopback function can select egress frames with a specific VLAN ID to be looped back into the ingress traffic path. This allows for in-service testing of connections without disrupting normal EVC traffic.

A port loopback can also be selected which loops all traffic from the egress direction back to the ingress data path. This is an out-of-service disruptive loopback.

Refer to Figure 1-19 for a block diagram of the data path of a service interface card which contains the FrameInjector and FrameMonitor blocks.

By injecting test traffic into an EVC connection, then looping the test traffic at the far end of the EVC, and monitoring the “echoed” traffic, ECPA can verify network connectivity along with several performance parameters. An example of this is shown in Figure 1-20.

Figure 1-19 ECPA Block Diagram

Figure 1-20 ECPA Point to Point EVC Example

CLIENTETHERNET

PORT

ME

DIA

INTE

RFA

CE

FRAMEINJECT

EGRESSFRAME

PROCESSING

INGRESSFRAME

PROCESSING

WA

NIN

TER

FAC

E

PORT LOOPBACK(All frames)

VLAN LOOPBACK

(Only selected EVC frames)

FRAMEMONITOR

WANETHERNET

PORT

CLIENTETHERNET

PORT

ME

DIA

INTE

RFA

CE

FRAMEINJECT

EGRESSFRAME

PROCESSING

INGRESSFRAME

PROCESSING

WA

NIN

TER

FAC

E

PORT LOOPBACK(All frames)

VLAN LOOPBACK

(Only selected EVC frames)

FRAMEMONITOR

WANETHERNET

PORT

ME

DIA

INTE

RFA

CE

FRAMEINJECT

EGRESSFRAME

PROCESSING

INGRESSFRAME

PROCESSING

WAN

INTER

FACE

FRAMEMONITOR

ME

DIA

INTE

RFA

CE

FRAMEINJECT

EGRESSFRAME

PROCESSING

INGRESSFRAME

PROCESSING

WAN

INTER

FACE

FRAMEMONITOR

ME

DIA

INTE

RFA

CE

FRAMEINJECT

INGRESSFRAME

PROCESSING

EGRESSFRAME

PROCESSING

FRAMEMONITOR W

ANIN

TER

FAC

E

ME

DIA

INTE

RFA

CE

FRAMEINJECT

INGRESSFRAME

PROCESSING

EGRESSFRAME

PROCESSING

FRAMEMONITOR W

ANIN

TER

FAC

E

NETWORK

ME

DIA

INTE

RFA

CE

FRAMEINJECT

EGRESSFRAME

PROCESSING

INGRESSFRAME

PROCESSING

WAN

INTER

FACE

FRAMEMONITOR

ME

DIA

INTE

RFA

CE

FRAMEINJECT

EGRESSFRAME

PROCESSING

INGRESSFRAME

PROCESSING

WAN

INTER

FACE

FRAMEMONITOR

ME

DIA

INTE

RFA

CE

FRAMEINJECT

INGRESSFRAME

PROCESSING

EGRESSFRAME

PROCESSING

FRAMEMONITOR W

ANIN

TER

FAC

E

ME

DIA

INTE

RFA

CE

FRAMEINJECT

INGRESSFRAME

PROCESSING

EGRESSFRAME

PROCESSING

FRAMEMONITOR W

ANIN

TER

FAC

E

NETWORK




TM

ECPA OperationUnder normal circumstances, the FrameInjector allows traffic from the MAC block to pass-thru to the Ingress Frame Processing block. Similarly, the FrameMonitor, in normal operation, passes frames transparently in the egress direction from the egress frame processing block to the MAC block.

When placed in test mode, the FrameInjector can inject test traffic in the ingress or egress data path. This test traffic emulates the flow of traffic from a UNI or EVC and allows various characteristics of the traffic to be simulated to ensure that the EVC connection performs correctly all the way through the network.

The FrameMonitor, when enabled, sniffs the ingress or egress traffic path for EVC test frames and traps them. The FrameMonitor can perform various performance calculations on the test traffic to analyze the EVC operation.

The FrameMonitor and FrameInjector also implement a flow loopback path which allows egress traffic frames trapped in the FrameMonitor to be “looped” back to the FrameInjector for transmission back into the network. This flow loopback enables a single EVC test traffic flow to be looped back without affecting normal EVC traffic. This capability is critical to performing multi-service port testing.

Each FrameInjector block is capable of sourcing three independent traffic flows, each with a different set of characteristics. Thus, it is possible to test EVC performance for multiple classes of traffic (for instance, with different priority levels) to ensure that different traffic classes receive correct QoS treatment. Similarly, each FrameMonitor is capable of monitoring and analyzing three independent data flows.

An ECPA test setup window via eVision walks you though the steps for selecting ECPA setup and execution options, and performing ECPA diagnostics. You can place a facility in the maintenance state, select the desired tests to perform, execute diagnostics, view test results, and restore the facility from this window. Refer to Figure 1-21 for an example of an ECPA test in progress using eVison.

For more information on the ECPA operation, see Etherjack® Connection Performance Analyzer, on Page 3-52.



TM

Scheduled PingThe Scheduled Activity icon provides a Scheduled Ping feature. The Scheduled Ping feature provides a current state of management link connectivity. Up to four IP addresses may be scheduled at a provisioned rate (1 minute to 1440 minutes) and should a failure occur, a provisionable alarm is raised against the IP address. A response threshold (1 to 4) is provisionable, indicating the number of consecutive time-outs that must occur before the alarm is raised. The alarm severity is provisionable for the group of IP addresses (Critical, Major, Minor, Not Reported or Not Alarmed). For more information on Scheduled Activity, see Section 3.9 Scheduled Ping, on Page 3-72.

Figure 1-21 ECPA Test Results Window




TM

Etherjack® Service AssuranceThe Etherjack Service Assurance (ESA) feature is a real-time monitoring tool to allow Ethernet services to be subjectively measured for the basis of Service Level Agreements (SLA). ESA implements standards-based approaches that are currently in progress.

SLA monitoring is a key success factor for carriers offering premium Ethernet services. Sophisticated enterprise customers demand SLA guarantees in their service contracts. Carriers must monitor the performance of a connection to determine if the agreement is being satisfied.

The FSP 150CCf-825 offers built-in SLA monitoring via the ESA feature set. The ESA feature provides Ethernet service providers with the ability to monitor individual customer SLAs without the need to install any extra monitoring and reporting equipment. ESA test results are displayed in tabular or chart format using the eVision Web Browser Management Tool. See Figure 1-22 for an example of ESA test results in chart form (for more information regarding ESA operation using eVision, see Chapter 2, Etherjack Service Assurance).

Figure 1-22 ESA Test Results in Chart Format



TM

Fault PropagationThe system supports both network to client and client to network Facility Fault Propagation (FFP). This feature is designed to help notify downstream / upstream equipment about failures occurring on the WAN / LAN interface.

LAN FFP is designed to notify the network (upstream) of failures on the LAN port. LAN FFP can be configured to perform one of the following actions when a LAN port is down:

• Do nothing (None) (default)

• Disable WAN port. This will result in Loss of Signal at the upstream node in the network and will cause a Link Deactivated condition to be raised against the WAN port.

• Send EFM RLD (Remote Link Down) message

WAN FFP is designed to notify the customer (downstream) of failures on the WAN connection by (optionally) turning off the LAN port(s). WAN FFP can be configured to perform one of the following actions when the WAN connection fails:

• Do nothing (None) (default)

• Disable LAN. This will shut down all LAN ports, which will result in Link Down at the customer device(s) and will cause a Link Deactivated condition to be raised against the LAN port.

Example Send EFM RLD OperationRefer to Figure 1-23 for the following EFM RLD example operation. Site A LAN-2 FFP is set to Send EFM RLD with Fault Propagation Delay set to 0 and Local Link ID is set to 2. When a Link Down failure is detected on LAN-2 (Local Link ID=2) at Site A, the defined Fault Propagation Delay is applied (in this case it is set to 0 seconds), then Site A transmits an EFM RLD message associated with Link ID-2 over the WAN to Site B.

Figure 1-23 Fault Propagation with RLD Notification Using Remote Link ID

RLD msg (LID-2)

FSP 150CC

WFFP=Disable LAN

LAN-1 LLID=1XLAN-2 LLID=2

LAN-1 RLID=1LAN-2 RLID=2

LAN-3 LLID=3LAN-4 LLID=4

LAN-3 RLID=2LAN-4 RLID=3

XWAN

Site A Site B

XFSP 150CC

LAN-5 LLID=5 LAN-5 RLID=4




TM

Site B WAN FFP is set to Disable LAN with Fault Propagation Delay set to 2 (seconds) and LAN-2 and LAN-3 Remote Link IDs are set to 2. Site B detects the EFM RLD message and identifies LAN-2 and LAN-3 as the RLID-2 members of the Remote Link ID list. Site B implements the defined Fault Propagation Delay (in this case it is set to 2 seconds) and then disables LAN-2 and LAN-3 at Site B.

When the fault on LAN-2 at Site A clears, the defined Fault Propogation Delay is applied (in this case it is set to 0 seconds),then the EFM RLD message is cleared for LAN-2 (RLID-2). Site B senses the EFM RLD message has cleared for LID-2, waits the defined Fault Propogation Delay (in this case it is set to 2 seconds) and then re-activates LAN-2 and LAN-3.

WAN FFP OperationWhen an RFI is detected on the WAN and the WAN FFP is set to Disable LAN, the behavior is controlled by the RFI alarm indication. The defined Fault Propagation Delay is applied, then the LAN(s) is disabled. In this case, all LAN ports will be deactivated at Site B (see Figure 1-24).

Note: If the WAN RFI alarm notification code is set to Not Reported or Not Alarmed, then the Fault Propagation feature will not activate for that alarm attribute.

Figure 1-24 WAN Fault Propagation Disabling LANs (Detection of RFI)

FSP 150CC

RFI

FSP 150CC

WAN FFP=Disable LAN

LAN-1LAN-2

LAN-1LAN-2

LAN-3LAN-4

LAN-3LAN-4

XWANX X

X

XSite A Site B

LAN-5 LAN-5X



TM

EFM-OAM Dying GaspThe FSP 150CCf-825 transmits a single EFM-OAM Dying Gasp message out of each EFM-OAM enabled port when a power failure occurs. This message is specified in the IEEE standard 802.3ah - Annex 43B. A receiving peer entity capable of processing this message will raise an alarm when the Dying Gasp is detected (see Figure 1-25). If EFM-OAM Dying Gasp and SNMP Dying Gasp are both enabled, and an SNMP Trap Dying Gasp Interface is resolved, then SNMP Dying Gasp will take priority on that interface.

SNMP Dying GaspUnfortunately, not all peers attached to the FSP 150CCf-825 can process EFM-OAM Dying Gasp messages. The SNMP Dying Gasp feature may be used as an alternative to EFM-OAM Dying Gasp to enable these peers to receive power failure notification as an SNMP trap. When SNMP Dying Gasp is enabled, Ethernet frame particulars such as VLAN and source MAC address will be obtained from each interface’s provisioned MAC- or VLAN-based management tunnel, and a Dying Gasp message will be prepared for transmission to the first reachable SNMP target address, should a power failure occur. See Figure 1-26.

The SNMP Dying Gasp feature is best utilized when connected to a device that is not EFM-OAM compliant. Note that SNMP Dying Gasp, which is intended to supplant EFM-OAM Dying Gasp, only functons on traffic carrying ports (i.e. not the MGMT LAN port) and will not work with PPP- or DLCI-based management tunnels (which are only employed in back-to-back systems).

Figure 1-25 EFM-OAM Dying Gasp

LAN WAN

TX

RX TX

RX

FSP 150CC

LANWAN

TX

RXTX

RX

FSP 150CC


EFM-OAM CPD set to Peer

EFM-OAM Dying Gasp sentto all EFM-OAM enabled interfaces





TM

To set up the SNMP Dying Gasp feature, first create the appropriate Ethernet encapsulated MAC- or VLAN-based management tunnel (the SNMP Dying Gasp feature only applies to LAN and WAN interfaces and are not applicable to the Management LAN or Serial Port). Then configure SNMP Target addresses on the FSP 150CCf-825. Then enable SNMP Dying Gasp at the system level. Once an SNMP target address has been configured and resolved, the SNMP Trap Dying Gasp Interface will display, indicating that the SNMP Dying Gasp feature is operational.

Resolving Target AddressesThe list of SNMP target addresses, as displayed, will be polled every 5 minutes to resolve target addresses and verify reachability. It may take up to 10 minutes for a target address to be resolved. Upon reboot, a resolved SNMP target address is not displayed until a second 5 minute cycle has completed. Outside of a reboot, changes are reflected after each 5 minute poll cycle.

Resolving target addresses entails using traceroute to determine the appropriate interface. It does not guarantee that the target address can be reached over that interface. Reachability uses ping (ICMP Echo) in an attempt to reach the target address. If the Ping fails, an “SNMP Dying Gasp Trap Host Unreachable Via Ping” alarm is raised. Note that reaching the IP address does not equate to an SNMP trap receiver running at that IP address. It is also possible that the ping could fail (e.g., be filtered by the network even though an SNMP trap would get through).

If an SNMP target address is unresolved, the SNMP Dying Gasp trap cannot be transmitted for that SNMP target address. Each interface may have one target address resolved for it. This means that a device that has two management tunnels, with a resolved target address on each tunnel, will send out two SNMP Dying Gasp traps - one for each interface.

The first target address per interface that is resolved is considered as the “resolved” one for that interface. Other target addresses that would be reachable on that same interface will be listed as unresolved.

Figure 1-26 SNMP Dying Gasp

LAN WAN

TX

RX TX

RX

Third Party System

LANWAN

TX

RXTX

FSP 150CC

SNMP Dying Gasp sentto resolved SNMP Target Address

RX



TM

EFM-OAM Dying Gasp and SNMP Dying Gasp Inter-OperationIf EFM-OAM Dying Gasp and SNMP Dying Gasp are both enabled, and an SNMP Trap Dying Gasp Interface is resolved, then SNMP Dying Gasp will take priority on that interface. (Note that it may take up to 10 minutes for a target address to be resolved on an interface once it is added. During that time period, the EFM-OAM Dying Gasp message will be sent if the system loses power.)




TM

Ethernet Connectivity Fault ManagementThe expansion of Ethernet technology into the domain of service providers provides an additional challenge to maintaining link uptime, where timeliness in isolating and responding to failures is crucial to daily operation.

Customers contract with service providers for end-to-end Ethernet service, and service providers may sub-contract with operators to provide equipment and networks (see Figure 1-27). These constituent networks belong to distinct organizations or departments, which are substantially larger, are more complex, and have a wider user base compared to enterprise networks.

Ethernet Connectivity Fault Management (CFM) is an emerging standard aimed at enhancing Ethernet Service Operation, Administration and Management (OAM) capabilities by providing proactive end-to-end connectivity monitoring, fault verification and fault isolation for large Ethernet MANs and WANs.

The CFM features included in this release of the FSP 150CCf-825 are:

• Configure Maintenance Domains (MD)

• Configure Maintenance Associations (MA)

• Configure and manage Maintenance End Points (MEP)

• Configure and manage Maintenance Intermediate Points (MIP)

• Transmit and receive Continuity Check Messages

• Initiate transmission of and receive responses for Link Trace and Loopback Messages

• Detect and raise CFM-related alarms

Figure 1-27 Provider-Subscriber Relationship

MEPMEPMIPMIP

Service Provider Domain

Customer Domain

Operator DomainOperator DomainOperator Domain



TM

CFM OverviewThe managed network in the context of CFM consists of Maintenance Domains (MDs), Maintenance Domain levels, and Maintenance Associations (MAs). An MA consists of a set of Maintenance End Points (MEPs) and Maintenance Intermediate Points (MIPs) that have the same MA ID and MD level.

CFM exchanges messages and performs operations on a per-domain basis. A Maintenance Domain is a bridged network (or network of bridged networks) maintained by an operator. Multiple domains at different levels create a hierarchy of Maintenance Domains. Each maintenance domain is assigned a Maintenance Domain level between 0 and 7. Suggested Maintenance Domain level allocation is: Customer Domain (5-7), Service Provider Domain (3-4), Operator Domain (0-2). An example of a Maintenance Domain hierarchy is shown in Figure 1-28.

A Maintenance Domain at a higher level is a subscriber of the services of a lower level domain. As shown in Figure 1-28, the MD at level 5 (Customer Domain) uses the service provided by the MD at level 3 (Service Provider Domain). Similarly, the Service Provider Domain at MD level 3 uses the services of Operators A and B at MD level 2.

Maintenance Domain level restricts visibility upward and downward in the hierarchy. The network topology of the Service Provider is not visible to the Customer Domain. Similarly, the Service Provider cannot see the Operator Domain’s topology. A higher level domain can only see what the lower level domain allows it to see.

Figure 1-28 Maintenance Domain Hierarchy

CPE Operator A Provider Bridges Operator B Provider Bridges CPE

Customer DomainMD Level = 5


MD Level = 3

MD Level = 2

Operator DomainOperator Domain

Up MEP Down MEP MIP MA




TM

A Maintenance Association represents the service instance being monitored and consists of MEPs which define the edge or boundary of the Maintenance Association. Even though only one MEP is created on each bridge for a Maintenance Domain, the MEP IDs of all MEPs in the MA must be configured at each bridge.

Maintenance PointsA maintenance point is a demarcation point on an interface that participates in CFM within a Maintenance Domain. Maintenance points can be associated with a port, an EVC, or a VLAN ID and can be created as an end point (MEP) or an intermediate point (MIP). MEPs define the boundary of a maintenance association. A MEP can be configured as an up MEP or a down MEP. Up MEPs transmit and receive CFM messages in the direction of the bridge relay. Down MEPs are just the opposite - CFM messages are transmitted/ received in the direction facing away from the bridge relay. Currently, down MEPs are not supported on LAN ports. Maintenance Intermediate Points (MIPs) are intermediate hops on the path between MEPs and are useful in fault isolation applications. MIPs are often MEPs for maintenance domains at a lower MD level. See Figure 1-28.

Figure 1-29 illustrates the possible locations of the maintenance end points. Port based MEPs are associated with the entire physical port. These are typically down MEPs created to monitor the link between the local port and the far end port.

VLAN based MEPs are associated with specific VIDs. These are typically up or down MEPs monitoring an X or Y tag. EVC based MEPs monitor the service instance over the network interface. These MEPs are usually associated with C and S tags.

Figure 1-29 Maintenance Points Example

Ingress Egress Client/LAN Ports (UNIs)

Port Mapped EVC

EVC w/Multi VLAN IDs

Network/WAN Port

Up/Down MEP

Flow Mapped EVCs

VLAN based MEPs

Port based MEPs EVC based MEPs



TM

Continuity Check MessageFundamentally, the CFM standard defines a set of CFM messages, along with supporting protocols and procedures, used for monitoring and managing the connectivity between the maintenance points that comprise a Maintenance Association.

Continuity Check Messages are periodic multicast messages used for detecting loss of continuity between maintenance end points within a maintenance association. Each MEP transmits CCMs to all other MEPs in the maintenance association at a specified interval. This message maintains a heartbeat between the MEPs. If the heartbeat from any one MEP is not detected for 3 consecutive intervals, a loss of continuity defect is declared. The loss of continuity defect must persist for 3 consecutive seconds for the “Some Remote MEP CCM” alarm to be declared. Since all MEPs in the same maintenance association must transmit at the same interval, the CCM interval is also used as the receive interval for loss of continuity detection. See Figure 1-30.

CCMs can also be used to detect misconfigurations. These defects include:• Unexpected MD Level• MA ID Mismatch/Service cross-connect• Missing or Unexpected MEP ID• CCM Interval Mismatch• Duplicate MEP ID• Duplicate Sequence Number

Figure 1-30 CCM Example

MEPMEPMIPMIPCCMCCM


Operator A Operator B

A

B

C

D

CCM Multicast from MEP A forwarded to MEP B, C and D




TM

The CCM carries information about the sender such as the source MAC address, maintenance association ID, source MEP ID, MD Level, etc. Each MEP receiving a CCM from a peer MEP must catalog this information into a local CCM MEP database. An entry should be created in the database for each MEP in the MA. The CCM interval ranges from 3.3 ms to 10 minutes. The 3.3 ms CCM interval is intended for protection applications. An interval of 1 second is recommended for fault detection.

Link Trace MessageLink Trace Message (LTM) is used for path discovery and fault isolation. LTM messages are multicast frames that a MEP transmits, at user request, to track the path (hop-by-hop) to destination MEP. At each MIP along the path to the target, the LTM is forwarded to the next hop and a Link Trace Response message (LTR) is sent back to the originating MEP. This process is repeated until the LTM reaches the intended target, or the LTM can no longer be forwarded. Based on the information in the LTRs received, the originating MEP can determine the path to the target if the Link Trace was successful, or the location of the fault in the event of a failure. See Figure 1-31.

Figure 1-31 Link Trace Example

MEPMEPMIPMIP

LTMLTM

LTR



A

B

C

D

LTM Ignored

LTM from MEP A forwarded to MEP B, C and D



TM

Loopback MessageLoopback Messages (LBMs) are unicast messages that a MEP transmits, at user request, to verify connectivity to a particular maintenance point. LBMs may also contain additional data in the payload to measure performance characteristics of the service. At the destination maintenance point, a Loopback Reply Message (LBR) is transmitted back to the originating MEP. A reply to a loopback message indicates whether a destination is reachable but does not contain hop-by-hop discovery of the path. See Figure 1-32.

Figure 1-32 Loopback Message Example

MEPMEP

MIPMIP

LBMLBM

LBR



A

B

C

D

LBM from MEP A forwarded to MEP B, LBR from MEB B forwarded to MEP A




TM

1.5 Upgrading an Existing FSP 150CCf-825If your FSP 150CCf-825 has already been commissioned and you are performing a software upgrade, perform the upgrade procedure in Section 3.14 Software Upgrade, on Page 3-89.

1.6 Initial Turn Up of an FSP 150CCf-825When performing an initial turn up of an FSP 150CCf-825, refer to the following sequence of steps and supporting technical information.

Recommended Sequence of Steps for Initial Turn Up of an FSP 150CCf-825The following sections in this chapter provide supporting information and procedures for physically installing and provisioning the FSP 150CCf-825:

• Section 1.6.1 Connectors and LED Descriptions

• Section 1.6.2 Physical Installation contains procedures for placing the FSP 150CCf-825 on a desk or communications cabinet, mounting the FSP 150CCf-825 onto a wall, into a 19” rack or a 23” rack.

• Section 1.6.3 Power Options and Wiring

• Section 1.6.4 Establish Communications Via Serial Console Port

• Section 1.6.5 Provision Communications

• Section 1.6.6 Download Latest Software Version

• Section 1.6.7 Provision System Level Options

• Section 1.6.8 Create Users

• Section 1.6.9 Provision Access Security Options

• Section 1.6.10 Provision the WAN Interface

• Section 1.6.11 Provision LAN Interface(s)

• Section 1.6.12 Provision Alarm Attributes and Scheduled Ping

• Section 1.6.13 Provision Performance Monitoring

• Section 1.6.14 Provision Cable Length Benchmarks and Perform Etherjack Diagnostic Test

• Section 1.6.15 Provision and Perform ECPA Test

• Section 1.6.16 Provision and Perform ESA

• Section 1.6.17 Provision Connectivity Fault Management



TM

• Section 1.6.18 Clear All Alarms

• Section 1.6.19 Create a Database Backup

It is recommended that you commission the FSP 150CCf-825 in the above order. Refer to Chapter 3, Web Browser Management Tool to become familiar with the eVision web browser management tool and refer to Chapter 5, Configuration Settings and Technical Data for system defaults, provisioning options and rules to provision the FSP 150CCf-825.

1.6.1 Connectors and LED DescriptionsRefer to the following for FSP 150CCf-825 connectors and LED descriptions when performing the following procedures. They may be used as supporting technical information for troubleshooting faults as well as connector and LED location/identification.

Refer to Section 5.8 Alarm Attributes, Probable Cause and Trouble Clearing, on Page 5-49 for a description of the alarm condition, probable cause, and suggested trouble clearing procedure. To clear alarm conditions, it is suggested that you start by using the trouble clearing procedure in Section 1.2 Trouble Clearing, on Page 1-4, using the associated eVision alarm condition.

Rear Panel Connector DescriptionsThe rear panel of the FSP 150CCf-825 provides a third option for power input. AC power adapters may be ordered separately to provide a third option for power input.

Figure 1-33 FSP 150CCf-825 Rear Panel Power Connector

Table 1-1 FSP 150CCf-825 Rear Panel Power ConnectorConnector Description

PWR AC to 12V DC power converters are available for both 120 VAC and 240 VAC, 15 A

12V DC




TM

Front Panel Connector DescriptionsAll interface connections except the power connectors are located at the FSP 150CCf-825 front panel. The front panel of the FSP 150CCf-825 is shown in Figure 1-34.

The following connectors are provided on the front panel of the FSP 150CCf-825:

• Network 1GbE optical WAN port. The WAN interface in fiber mode uses an SFP optical transceiver (SMF or MMF) that supports 1000 Base SX/LX/ZX.

• Network 100/1000 Base-T copper WAN port (RJ45)

• LAN 1 - 4: Client 10/100 Base-T copper LAN ports (RJ45)

• LAN 5: Client 1GbE optical LAN port. The LAN interface in fiber mode uses an SFP optical transceiver (SMF or MMF) that supports (1000 BaseLX10 or 1000 BaseLH) or single fiber (1000 Base BX10).

• LAN 5: Client 10/100/1000 Base-T copper LAN port (RJ45)

• 10/100 Base-T Management LAN port (RJ45)

• RS-232 Serial Console (maintenance) port (RJ45)

Figure 1-34 FSP 150CCf-825 Front Panel Connectors and LEDs

PSU1

Status

100 -240V AC

PSU2

Status Critical

Major

MinorStatus

Etherjack TM

Management

RS -232

LAN

5

4321

2 4 Access


21

Active

Network FSP150CCf

21

5

PSU1

Status

100 -240V AC

PSU2

Status Critical

Major

Minor

Status

Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3

1 3

- Gnd+



TM

Table 1-2 FSP 150CCf-825 Front Panel Connectors (Left to Right)Section Connectors Description

PSU 1 and PSU2

AC power AC power connector on AC power supply unit

DC power -48 VDC power connector on DC power supply unit

Management

RS-232 RJ-45 RS-232 Serial Console (maintenance) port

LAN RJ-45 10/100 Base-T Management LAN port supports auto-MDIX capabilities

Access

LAN 1 - 4 RJ-45 Client 10/100/1000 Base-T Copper LAN port

LAN 5 SFP optics LAN port or RJ-45 10/100/1000 Base-T Copper LAN port

Network (1 and 2)

Optical port SFP optics WAN port

Copper port RJ-45 10/100/1000 Base-T Copper WAN port

Figure 1-35 FSP 150CCf-825 -48 VDC Power Supply Unit Connectors

Table 1-3 150CCf-825 -48 VDC Power Supply Unit ConnectorsPin # Connector Description

1 -48 VDC, 5 A Battery (Red wire)

2 Frame Ground (Green wire)

3 Return (Black wire) for battery source

Position Connector Release Tabat top of power connector

Status

1 2 3

- Gnd+

- Gnd +




TM

System LEDsThe names and functions of each general system LED are described in Table 1-4.

Local Management Port LEDsThe names and functions of each local management LAN port LED are described in Table 1-5.

Table 1-4 System LEDsLED Name Color Definition

PSU-n Status

Off No input power detected

Green Input power present and PSU operating with normal limits

Red PSU fail or input power out of spec

CROff No critical alarms

Red At least one critical alarm present on the system

MJOff No major alarms

Red At least one major alarm present on the system

MNOff No minor alarms

Amber At least one minor alarm present on the system

Status

Off No Power detected

Green Power OK and system operational

Red

Power OK, but system fault detected, or

Power OK, system booting, or

Input power good, internal power bad

Table 1-5 Local Management LAN Port LEDsConnector LED Color Definition

RJ-45 (LAN) Link

Off No signal detected on receive

Green Good signal

Activity

Off No traffic activity

Flashing-Green Traffic being transmitted on portActivity

Link



TM

Network and Client Ethernet Electrical Facility LEDsAssociated with each Client Ethernet port is a facility LED (labeled 1 through 5) and associated with each Network electrical Ethernet port is a facility LED (labeled 1 and 2) which are defined in Table 1-6. (For software release 1.0, only one Network port is available for use. The second port will be available for use in a future release.)

Each Network and Client RJ-45 electrical Ethernet port has two LEDs associated with the connector. The definitions of the LEDs are shown in Table 1-7.

Table 1-6 Network and Client Ethernet Facility LEDsLED Name Color Definitions

Client Facility

(Labeled 1 through 5)

Network Facility

(Labeled 1 and 2)

Off Unassigned (for Network Facility - only applies to port “B”)

Green Assigned and no defects

Amber

RFI

LCP Fail

Duplex Mismatch

EFM RLS (Remote Link Status)

EFM RCE (Remote Critical Event)

EFM Fail (EFM Discovery Fail)

Red

Link Down (Unisolated, Cable Removed, Cable Fault, Auto Negotiation Fault)

Link Deactivated

Receive Jabber

Dying Gasp

SFP Removed (only applies to Client optical Ethernet Port 5)

Table 1-7 Network and Client Electrical RJ-45 Connector LED Definitions Connector LED Color Definitions

RJ-45

Activity

Off

Unassigned (for Client - applies to all ports, for Network - only applies to Port “B”)

No Traffic

Port in optical (Fiber) mode (only applies to Client optical Ethernet Port 5 and Network Port “B”)

Flashing Green Traffic (TX or RX)

Activity

Link




TM

Network Optical Ethernet Port LEDsAssociated with each Network optical Ethernet port are two LEDs (Lk and Rate) defined in Table 1-8.

(see above) Link Off

Unassigned (for Client - applies to all ports, for Network - only applies to Port “B”)

Link Down

Port in optical (Fiber) mode (only applies to Client optical Ethernet Port 5 and Network Port “B”)

Green Link Detected

Table 1-8 Network Optical Ethernet Lk/Rate LEDsConnector LED Name Color Definition

SFP Rate

OffUnassigned (only applies to Port “B”)

Port in electrical (Copper) mode

Amber 100M Operation

Green 1000M Operation

Lk (Link)Off

Unassigned (only applies to Port “B”)

SFP not present

Port in electrical (Copper) mode

Link Down

Green Working (Link detected)

Flashing Green Traffic (TX or RX)

Table 1-7 Network and Client Electrical RJ-45 Connector LED Definitions (Continued)Connector LED Color Definitions

Lk Rate



TM

1.6.2 Physical InstallationInstallation of the FSP 150CCf-825 requires that you establish WAN facility connection(s) between your local and remote sites, or between your local site and the telco. After your end-to-end connection has been installed, you are ready to install the FSP 150CCf-825.

The FSP 150CCf-825 is designed for deployment in both customer premises and CO locations. Wall mount and rack mount brackets may be ordered separately.

FSP 150CCf-825 Package ContentsUpon receipt of your product, please check the FSP 150CCf-825 package contents carefully. The FSP 150CCf-825 package should contain the FSP 150CCf-825 as well as the following components:

• 2 blank PSU panels

• One 16 gauge stranded wire grounding cable, with #8 spade lug, 10 feet

• One DB-9 to RJ-45 console converter adapter

The following power and mounting components may be ordered separately:

Table 1-9 Power and Mounting Ordering Options Description Use Part Number

Power Supply Unit (plugs into front of chassis), 120/240 VAC

Universal 0040904010

IEC AC Power Cord (for use with a single PSU module, part number 0040904010)

Central Europe 0036904021


United Kingdom 0036904022


North America 0036904023

Power Supply Unit (plugs into front of chassis), 48 VDC


Power Adapter, 120/240 VAC (for use with 12 VDC rear panel power connector)


AC Power Cable for external power adapter (Power Adapter part number 0040904040)

Argentina 0036904019


Australia 0036904017




India 0036904018




TM


Japan 0036904020



FSP 150 Rack/Wall Mounting Kit, containing:

• two 19-inch standard ears

• two 19-inch extended ears

• two ETSI standard ears

• two ETSI extended ears

• two 23-inch standard ears

• two wall mount brackets

• 10 mounting screws


Table 1-9 Power and Mounting Ordering Options (Continued)Description Use Part Number



TM

Mounting/Placement ProceduresIf the FSP 150CCf-825 is to be placed on a desk or in a communications cabinet, refer to Placing the FSP 150CCf-825 on a Desk-top or in a Communications Closet.

If the FSP 150CCf-825 is to be mounted on a wall or in a rack, perform one of the following procedures:

• Mounting the FSP 150CCf-825 to a Wall, on Page 1-54• Mounting the FSP 150CCf-825 in a 19” or 23” Rack, on Page 1-57

Placing the FSP 150CCf-825 on a Desk-top or in a Communications ClosetThe system can be deployed on a desk-top environment and provides suitable protection of desk-top surfaces via non-skid, non-marking rubber feet. The FSP 150CCf-825 is cooled by radiating heat from the chassis and does not require any fans to operate correctly in the defined environment.

Physically place the FSP 150CCf-825 on the desktop or in the communications cabinet. Then proceed to Section 1.6.3 Power Options and Wiring, on Page 1-59.

Mounting the FSP 150CCf-825 to a WallPrior to mounting the FSP 150CCf-825, please check the package contents carefully. The Wall Mounting Kit (ordered separately) should contain the following components:

• Two wall mounting brackets

• 10 mounting screws (only eight are required)

• Two wall mounting screws (not included)

Procedure: Mounting the FSP 150CCf-825 to a Wall

Step 1 Select a suitable location to install the FSP 150. The wall material and mounting screws should be of sufficient strength to bear the load of the FSP 150 (approx. 9 lbs).

Step 2 Secure the FSP 150 wall mounting brackets to the center screw holes on the unit using four screws each. See Figure 1-36.




TM

WARNING — To avoid overheating and the risk of fire, do no block airflow through the FSP 150. Leave at least 3 inches (7 cm) of space above and below the unit to provide sufficient air flow.

Step 3 Use the wall mounting brackets as a template for marking holes. Drill mounting holes and insert wall anchors, as required.

Step 4 Attach the FSP 150C mounting bracket to the wall using wall anchors and screws. See Figure 1-37.

Step 5 Connect a ground wire to one of the screws and connect the other end to a suitable building (earth) ground.

Figure 1-36 Install Wall Mounting Brackets

5

PSU1

Status

100 -240V AC

PSU2

Status Critical

MajorMinor

Status

Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3



TM

End of Procedure

Figure 1-37 Mount the FSP 150 to the Wall

5

PSU

1

Stat

us

100

-24

0V A

C

PSU

2

Stat

usC

ritic

alM

ajor

Min

orSt

atus

Eth

erja

ck T

M

Man

agem

ent RS

-23

2

LAN

4 3 2 1

24

Acc

ess

LkR

ate

LkR

ate

LkR

ate

2 1

Act

ive

Net

wor

kFS

P150

CC

f

21

13

Wall




TM

Mounting the FSP 150CCf-825 in a 19” or 23” RackPrior to mounting the FSP 150CCf-825, please check the mounting package contents carefully. The Rack Mounting Kit (ordered separately) is a universal rack mounting kit for mounting an FSP 150CCf-825 into a 19” or 23” rack.

The following components will be used in this procedure:

• Two 19-inch standard ears

• Two 19-inch extended ears

• Two ETSI standard ears

• Two ETSI extended ears

• Two 23-inch standard ears

• Ten mounting screws (only eight are required)

• Four rack mounting screws (not included)

Procedure: Mounting the FSP 150CCf-825 in a 19” or 23” Rack

Step 1 Determine the required mounting configuration for the rack installation.

Step 2 Secure the appropriate two ears to the FSP 150CCf-825 using four screws each, by attaching them to either the front or center screw holes. See Figure 1-38.

Step 3 Mount the FSP 150CCf-825 to the rack with four #10-32 x 3/8 screws. See Figure 1-39.

Note: If additional FSP 150CCf-825s are to be stacked above each other, are installed above heat producing components, or are installed below heat sensitive components, heat deflector(s) must be installed. Install air deflector(s) as described in Table 1-10.

Table 1-10 Air Flow Requirements for the FSP 150CCf-825

Air Flow Requirements

Multiple units may be stacked up to 5 rows high in an environmentally controlled environment, such as a Central Office. A heat deflector should be installed between every 5 rows of FSP 150CC NIDs and other equipment.

If it is necessary to install 5 rows of NIDs above other heat producing components, it is recommended that a heat deflector is installed below the NIDs. If it is necessary to install heat sensitive equipment above 5 rows of NIDs, it is recommended that a heat deflector is installed above the NIDs.



TM

End of Procedure

Figure 1-38 Attach Mounting Ears

Figure 1-39 Mounting the FSP 150CCf-825 in a 19” or 23” Rack

5

PSU1

Status

100 -240V AC

PSU2

Status CriticalMajor

Minor

Status

Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3

5

PSU1

Status

100 -240V AC

PSU2

Status Critical

MajorMinor

Status

Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3




TM

1.6.3 Power Options and WiringThe following provides power supply requirements as well as instructions for installing the power and cabling for the FSP 150CCf-825. Refer to Table 1-9, on Page 1-52 and the following information for determining PSU and/or power adapter cabling requirements for your site.

Power RequirementsThe system is powered by dual AC and/or DC Power Supply Units (PSUs). PSUs can be of similar type or mixed, and are hot swapable. It can be equipped with two AC modules, two DC modules, or one of each. They are physically accessed at the front of the unit and source connections are located on the front of each PSU module.

Optionally, a third possible power source, an external AC to 12 VDC power converter, may be used. The 12 VDC power converter may be used alone, or mixed with AC and/or DC power supply modules. It is physically connected at the rear of the unit. AC power converters may be ordered separately for North American and international location.

If an external AC power converter and/or one PSU module fails - or its input source fails, the remaining module continues to power the system without interruption to system function.

Note: The power supplies are not designed to operate in load-sharing mode.

AC SupplyThe system operates with an AC source fused at 15A, with the voltage range specified in ANSI specification C84.1-1989, Voltage Ratings (60 Hz) for Electric Power Systems Equipment, Range B. The FSP 150CCf-825 can tolerate any frequency within the range of 60 (+/-3) Hz for North American applications, and the range of 50 (+/-3) Hz for European applications. The maximum power consumption from the 230 VAC supply is 40W.

DC SupplyThe DC power connector is a 3-pin socket (Battery, Return, Frame Ground) which includes a mated connector, providing protection against improper (reversed polarity) connection at the NID. The maximum power consumption from the -48 VDC supply is 40W. External fuse rating is 5A.

The FSP 150CCf-825 operates properly when supplied with minimum and maximum operating voltages for North American and International applications, as shown in Table 1-11.

Table 1-11 Minimum and Maximum Operating Voltages Nominal Voltage Minimum

Operating VoltageMaximum

Operating VoltageMinimum

Abnormal VoltageMaximum

Abnormal Voltage

-48 -40.5 -57.0 0 -60.0

-60 -50 -72 0 -75



TM

External AC to 12 VDC Power ConverterThe system also provides an optional AC to 12 VDC converter input on the rear panel, externally fused at 15A. North American and International versions are available (see Table 1-9, on Page 1-52).

Connect Cables and Apply PowerFor all FSP 150CCf-825 installations, you will need the proper PSU, power cables and/or power adapter for your site, and cabling related tools and supplies, as required by local practices. For DC powered FSP 150CCf-825 power supply units, you will need the following items for this procedure:

• Screwdriver

• Wire wrap tool

• Wire cutters

• Wire strippers

• Volt meter

• Fuse panel

• Other power related tools and supplies as required by local practices

For optical cabling installation, you will need the following items for this procedure:

• Optical Power Meter

• Fiber Cleaner

• Small Form-factor Plug-ables (SFPs), as required

Refer to Section 1.6.1 Connectors and LED Descriptions, on Page 1-46 and Section 5.13.1 Connector Pin Assignments, on Page 5-86 for supporting information when performing the following procedure.

Procedure

Insert SFPs, Run and Connect Power Cables

Step 1 Connect the ground cable, as required.

Step 2 If using optical WAN/LAN interfaces: Obtain the proper SFP (Small Form-factor Plug-able), and insert it/them into the optical port(s).




TM

Step 3 Determine the next step.

DANGER — Avoid the risk of electrical shock. Follow local procedures for working with electrical power. High voltage may be present in the following tasks. Shut off the power from the power source or turn off the circuit breakers before proceeding. Use properly insulated tools when working with power connections. Do not allow any metal objects to connect across power terminals.

Step 4 Verify that the office DC power supply is set up to deliver the correct operating voltage to the FSP 150CCf-825 (between -40.5 and -72 VDC). Verify that the correct fuse or breaker (5 A rating) is installed at the power supply source and that power is turned off. Repeat for a second DC power supply source, if present.

Step 5 Using a volt meter, measure the voltages at the source power supply terminals. Verify that no voltage is present. Repeat for a second DC power supply source, if present.

Step 6 Run the DC power cables (shipped with the power supply unit) from the FSP 150CCf-825 to the office battery terminals. Dress the power cables. Repeat for a second DC power supply unit, if present.

Step 7 Remove the blank PSU front panel, then insert the DC power supply unit into the front panel. Repeat for a second DC power supply unit, if present. If the second PSU slot is unused, ensure that a blank PSU card is inserted into the slot. Tighten the thumb screws on both PSU slots.

Step 8 Connect the green Frame Ground wires to the Frame Ground terminal. Repeat for a second DC power supply unit, if present.

Step 9 Connect the black Office Return wires to the RTN DC power supply terminals. Repeat for a second DC power supply unit, if present.

Step 10 Connect the red Office Battery wires to the BATT DC power supply terminals. Repeat for a second DC power supply unit, if present.

Step 11 Verify that all power terminal connections are tight and that no strands of wire are shorting terminals together. Repeat for a second DC power supply unit, if present.

Step 12 Reconnect the office power source (reinstall fuses, reset breakers or turn on supply). Repeat for a second DC power supply unit, if present.

Current Status Then

Does/will the FSP 150CCf-825 include a DC power supply unit?

Continue with the next step.

Does/will the FSP 150CCf-825 NOT include a DC power supply unit?

Go to Step 16.



TM

Step 13 Use a volt meter to verify the A side power and ground at the power terminals. Ensure that the voltage between BATT and RTN terminals measures between -40.5 and -72 VDC. Repeat for a second DC power supply unit, if present.

Step 14 Using a volt meter, measure the voltage between RTN and Frame GND terminals. Verify that 2 VDC or less is present. Repeat for a second DC power supply unit, if present.

Step 15 Connect the power cables to FSP 150CCf-825 front connectors (red wire / connector release tab oriented at the bottom). Repeat for a second DC power supply unit, if present. The power supply Status LED should illuminate green. During the power cycle, the front panel Status LED will illuminate red for approximately 1 minute, then will change to solid green.


Step 17 Run the AC power cable (shipped with the FSP 150CCf-825 power supply unit) from the FSP 150CCf-825 to the AC power outlet, externally fused at 15A. Dress the power cables. Repeat for a second AC power supply unit, if present.

Step 18 Remove the blank PSU front panel, then insert the AC power supply unit into the front panel. Repeat for a second AC power supply unit, if present. If the second PSU slot is unused, ensure that a blank PSU card is inserted into the slot. Tighten the thumb screws on both PSU slots.

Step 19 Insert the power cable into the PSU front connector. Then insert the power cable into the AC power outlet. Repeat for a second AC power supply unit, if present. The power supply Status LED should illuminate green. If AC power is the only power source: During the power cycle, the front panel Status LED will illuminate red for approximately 1 minute, then will change to solid green.

Current Status Then

Does/will the FSP 150CCf-825 include an AC power supply unit at the front panel?


Does/will the FSP 150CCf-825 NOT include an AC power supply unit at the front panel, but a 12 VDC rear connector power adapter will be used?

Go to Step 21.

Only DC power will be used in this installation? Go to Step 22.




TM


Step 21 Connect the power adaptor cable to the power connector (PWR) located at the rear panel, connect the power cord into the power adapter, then plug the AC adaptor to an AC (120V or 240V) wall outlet, externally fused at 15A. If this is the only power source: During the power cycle, the front panel Status LED will illuminate red for approximately 1 minute, then will change to solid green.

Step 22 Tie-off and secure all power cabling.

Run and Connect Metallic Cables

Step 23 Run the MGMT LAN port cable and metallic LAN port cables to the FSP 150CCf-825, as required. Temporarily secure the cables.

Step 24 Connect a LAN Cable to the MGMT LAN port and connect the other end of the cable to your networking gear (PC, hub, switch, or router). From the factory, the default IP address of the FSP 150CCf-825 is: 192.168.0.2/24.


Step 26 For metallic WAN interface(s): Connect the WAN cable(s) to the designated WAN port(s) using a Cat 5 LAN cable (RJ-45 connector). Otherwise, go to the next step.

Step 27 For metallic LAN interface(s): Connect the client Ethernet communications equipment (PC, hub, switch, or router) to the first designated client LAN port using a Cat 5 LAN cable (RJ-45 connector). Repeat for each additional client LAN port, as required. Otherwise, go to the next step.

Step 28 Tie-off and secure all metallic cabling.

Current Status Then

Will a rear accessible 12 VDC power adapter be used?


No rear accessible 12 VDC power adapter will be used?

Go to Step 22.

Current Status Then

Are you only installing fiber optic WAN and LAN cables, and no metallic cables are to be installed?

Go to Step 35.

Are metallic WAN or LAN cable terminations required for this FSP 150CCf-825?




TM


Run and Connect Fiber Optic Cables

The following precautions should be applied when handling fiber optic cables:

DANGER — Follow local safety procedures regarding fiber optic cables. Never look at the end of a fiber optic cable. Permanent eye damage or blindness can occur. All optical connectors are shipped with protective caps. Ensure that protective caps are firmly in place before running any fiber optic cables.

DANGER — Never handle exposed fiber optic cables with bare hands or touch it to your body. A fiber fragment could enter the skin and be very difficult to detect and remove.

CAUTION — Optical power performance is affected by dust. Clean all connectors before performing measurements. Keep the ends of the fiber optic cables covered when the cables are not in use. The need for cleaning can be minimized if covers are always used when fibers are not used. Refer to local practices for fiber handling and cleaning procedures. Clean all connectors before performing measurements.

WARNING — Prevent damage to fiber optic cables. Do not bend fiber optic cables to a radius less than 50 mm.

WARNING — To avoid damage to optical receivers, do not connect any fibers until instructed to do so. Always check optical levels before connecting fiber optic cables.

Step 30 Run the optical fiber cables to the FSP 150CCf-825. Do not connect the cable(s) to the FSP 150CCf-825 connectors at this time. They will be connected later.

Step 31 Dress all fiber optic cables. Use local practices for protecting all cables and connectors.

Current Status Then

Are only metallic cable terminations required for this FSP 150CCf-825 and cabling is complete?

Go to Step 35.

Are you installing any fiber optic cables? Continue with the next step.




TM

Step 32 Test the optical cables according to local practices.

Step 33 Measure the transmit and receive levels of the fiber optic cables and record them for future reference.

Step 34 Connect the optical interface cables to the appropriate WAN and/or LAN SFP connectors on the front panel.

Verify WAN and LAN LED Indicators

Step 35 Observe the client LAN LED(s) and refer to Section 1.6.1 Connectors and LED Descriptions for FSP 150CCf-825 LED descriptions. If the LAN LED(s) indicate anything other than the appropriate response for the current state, troubleshoot as necessary.

Step 36 Observe the WAN (Network) LED and refer to Section 1.6.1 Connectors and LED Descriptions or FSP 150CCf-825 LED descriptions. If the WAN LED(s) indicate anything other than the appropriate response for the current state, troubleshoot as necessary.

End of Procedure



TM

1.6.4 Establish Communications Via Serial Console PortPerform the following procedure to establish communications via the Serial Console Port.

You will need the following items for this procedure:

• PC with a serial communications port (e.g., COM1 or COM2)

• Category 5 LAN Cable (with RJ-45 connectors)

• DB-9 to RJ-45 converter

• A communications program, like HyperTerminal (a standard Windows communications utility)

• Internet Explorer 5.0 or greater

Procedure

Step 1 Connect the console cable between the FSP 150CCf-825 RS-232 Serial Console Port and a PC using the RJ-45 cable and the DB-9 converter. See Section 1.6.1 Connectors and LED Descriptions, on Page 1-46 for the RS-232 Serial Console Port connector location.

Step 2 From the PC, start a communications utility application (such as TeraTerm Pro Web or HyperTerminal) with the following COM port settings:

Note: The Serial Console Port supports only 9600 baud. Do not use Autobaud.

Step 3 Hit the “Enter” key and you will be prompted to enter a login and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively. A warning banner and continue query displays. Enter “y” to the query and the serial console CLI prompt (-->) will then be displayed.

End of Procedure

Table 1-12 COM Port Settings PARAMETER SETTING

Baud Rate 9600 baud

Data 8 bits

Stop Bits 1

Parity None

Flow Control None




TM

1.6.5 Provision CommunicationsUse the following procedure for provisioning FSP 150CCf-825 communications. If you are provisioning the FSP 150CCf-825 locally using the Serial Console port or Management LAN port, WAN interface provisioning is not required in order to communicate to the FSP 150CCf-825. If you are planning to provision the FSP 150CCf-825 via the WAN port (for example, from a remote location), then a minimal amount of WAN interface provisioning is required prior to provisioning WAN communications. This may be performed using CLI commands (refer to the FSP 150CCf-825 Etherjack OS (EOS) Command Line Interface Handbook for CLI command details). The following procedure supports both provisioning scenarios.

Procedure

Step 1 If you will be commissioning the FSP 150CCf-825 using the Serial Console port or Management LAN port, go to Step 6. If you will be commissioning a FSP 150CCf-825 via the WAN port (for example, from a remote location), determine the WAN interface provisioning requirements, then continue with the next step to set up the WAN port via CLI commands.

Step 2 Connect your PC to the FSP 150CCf-825 RS-232 Serial Console Port as described in Section 1.6.4 Establish Communications Via Serial Console Port.

Step 3 Use the following CLI commands (as applicable) to provision the WAN interface via CLI commands (refer to the FSP 150CCf-825 Etherjack OS (EOS) Command Line Interface Handbook for CLI command details):

Note: The following are a list of the minimal WAN interface provisioning commands required prior to setting up WAN port communications.

Step 4 Verify the changes by using the show interface e1000-wan-1 or show this command followed by a carriage return.

Table 1-13 Minimum WAN Interface Provisioning via CLI Commands Command Description

WAN Port

adminstate Defines the WAN facility administrative state.

media Defines the WAN interface media type.

speed Defines the line rate of the Ethernet port and whether it is in half duplex or full duplex mode.



TM

Step 5 Enter the database save command followed by a carriage return. The system will display a warning message and when complete, the CLI prompt will appear, as shown in the following example:

Step 6 Refer to Chapter 4, Communications Provisioning for communications provisioning information and provisioning details. It contains example management configuration procedures to set up FSP 150CCf-825 management configurations for your site. Upon completion, you should be logged onto the FSP 150CCf-825 via the eVision web browser management tool prior to continuing with the installation process.

End of Procedure

1.6.6 Download Latest Software VersionThe latest FSP 150CCf-825 software load is provided on the CD-ROM that was packaged with your FSP 150CCf-825 or shipped separately for a software revision upgrade if a licence was purchased with the unit.

CAUTION — For GNE/SNE configurations, perform the software upgrade on the SNE first, and perform the upgrade on the GNE last. This will prevent loss of communication during the upgrade process. Both FSP 150CCf-825s in a GNE/SNE configuration must be set to the same software version in order for some features to work correctly, e.g., LCP to work in BCP encapsulation mode.

The Software Upgrade procedure is accomplished by using the eVision Web Browser Management Tool. Prior to performing the following procedure, it is recommended that you become familiar with the Web Browser Management Tool (see Chapter 3, Web Browser Management Tool). To download the latest software version, go to Section 3.14 Software Upgrade, on Page 3-89.

1.6.7 Provision System Level OptionsRefer to Section 5.3 System Configuration Options and Rules, on Page 5-8 and use eVision to provision system options as required for your site. Refer to Chapter 3, Web Browser Management Tool for additional information regarding system provisioning using eVision.

config:if(e1000)--> database save

Saving configuration. Do not power down the system.

config:if(e1000)-->




TM

Upon completion, save the configuration in eVision by selecting File and then Save Changes from the menu bar.

1.6.8 Create UsersCreate a new System Administrator user, delete the default System Administrator user (Covaro1) and create new users, as required. Refer to Section 5.3 System Configuration Options and Rules, on Page 5-8 for user option settings and defaults. Refer to Section 3.12 Users and Security, on Page 3-81 for information on how to use eVision to provision users.


1.6.9 Provision Access Security OptionsThe FSP 150CCf-825 support Remote Authentication, using either RADIUS or TACACS+. Refer to Section 5.3 System Configuration Options and Rules, on Page 5-8 for option settings and defaults. To provision Remote Authentication using eVision, refer to Section 3.13 Provisioning Remote Authentication, on Page 3-86.

The FSP 150CCf-825 also provides the option of Access Control List (ACL). Refer to Section 5.3 System Configuration Options and Rules, on Page 5-8 for option settings and defaults. To provision ACL using eVision, refer to Section 4.6 Provision ACL Using eVision, on Page 4-47.


1.6.10 Provision the WAN InterfaceRefer to Section 5.2 System Default Parameters and Maximum Bandwidth, on Page 5-2 for WAN interface default values and Section 5.4 WAN Configuration Options and Rules, on Page 5-18 for WAN interface configuration options and rules. Provision the WAN interface by selecting configuration view, entering a right click on the WAN entity in the eVision menu tree and selecting Edit Facility.


CAUTION — Provision the FSP 150CCf-825 in the sequence described in this document to prevent loss of provisioning data.



TM

1.6.11 Provision LAN Interface(s)Refer to Section 5.5 LAN Configuration Options and Rules, on Page 5-21 for LAN interface configuration options and rules and Section 3.6.1 Provisioning LAN Interface(s), on Page 3-17 for information on how to use eVision for creating and editing LAN interfaces. Three procedures are provided for provisioning LAN interfaces:

• Provisioning a LAN to Transparent EVC Mode, on Page 3-17

• Provisioning a LAN to Connection-oriented Flow VLAN EVC Mode, on Page 3-22

• Provisioning a LAN to Connection-less Flow VLAN EVC Mode, on Page 3-31


1.6.12 Provision Alarm Attributes and Scheduled PingProvision Alarm Attributes, as required. Refer to Section 5.8 Alarm Attributes, Probable Cause and Trouble Clearing, on Page 5-49 for Alarm Attribute default values and Section 3.7.1 Editing Alarm Attributes, on Page 3-40 for information on how to use eVision to provision Alarm Attributes.

Provision Scheduled Ping, as required. Refer to Section 5.11 Scheduled Ping and ESA Activity Settings, on Page 5-76 for Scheduled Ping options and rules, and refer to Section 3.9 Scheduled Ping, on Page 3-72 for a description on how to use eVision to provision Scheduled Ping as required for your site.


1.6.13 Provision Performance MonitoringView the current PM counts and edit any PM threshold levels, as required. When all PM thresholds are set as desired, then initialize all PM registers.

Refer to Section 5.9 Performance Monitoring Settings, on Page 5-58 for WAN, LAN and FID Threshold Crossing Alert (TCA) option settings and defaults and refer to Section 3.8 Performance Monitoring, on Page 3-63 for information on how to use eVision to view PM counts, edit PM threshold levels and initialize PM thresholds as required for your site.





TM

1.6.14 Provision Cable Length Benchmarks and Perform Etherjack Diagnostic Test

Enter cable length benchmarks (up to 5 per LAN) so that when future Etherjack diagnostics are performed on the LAN, the test operator can quickly determine if the fault is located at a particular patch panel. Refer to Section 3.7.4 Cable Length Benchmark, on Page 3-45 for information on how to use eVision to store cable length benchmarks and perform an Etherjack diagnostic for each provisioned LAN.


1.6.15 Provision and Perform ECPA TestProvision and perform an Etherjack Performance Analyzer (ECPA) test on each LAN to test EVC connectivity and to verify end-to-end service conformance. Refer to Section 3.7.5 Etherjack® Connection Performance Analyzer, on Page 3-52 for information on how to use eVision to perform an ECPA test for each provisioned LAN.


1.6.16 Provision and Perform ESAProvision and perform an Etherjack Service Assurance (ESA) test, as required. Refer to Section 5.10 ESA Options and Rules, on Page 5-72 for ESA option settings and rules, and refer to Scheduled ESA, on Page 5-77 for scheduled ESA options. Refer to Chapter 2, Etherjack Service Assurance for information on how to use eVision to provision and perform an ESA test.


1.6.17 Provision Connectivity Fault ManagementProvision Connectivity Fault Management (CFM) for the node, as required. Refer to Section 5.12 CFM Options and Rules, on Page 5-78 for CFM option settings and defaults and refer to Section 3.11 Connectivity Fault Management, on Page 3-74 for information on how to use eVision to provision CFM.




TM

1.6.18 Clear All AlarmsObserve all current alarms and clear any problems. Perform the alarm clearing procedure in Section 1.2 Trouble Clearing, on Page 1-4.

1.6.19 Create a Database BackupPerform a database backup to back up the FSP 150CCf-825 provisioning settings. Refer to Section 3.15 Configuration Database Management, on Page 3-107 for information on how to use eVision to create a database backup.


Optical Networking

TM

Chapter 2 Etherjack Service Assurance

2.1 OverviewThe Etherjack Service Assurance (ESA) feature is a real-time monitoring tool to allow Ethernet services to be subjectively measured for the basis of Service Level Agreements (SLA). ESA implements standards-based approaches that are currently in progress.

SLA monitoring is a key success factor for carriers offering premium Ethernet services. Sophisticated enterprise customers demand SLA guarantees in their service contracts. Carriers must monitor the performance of a connection to determine if the agreement is being satisfied.

The ADVA FSP 150CCf-825 offers built-in SLA monitoring via the ESA feature set. The ESA feature provides Ethernet service providers with the ability to monitor individual customer SLAs without the need to install any extra monitoring and reporting equipment. ESA test results are displayed in tabular or chart format using the eVision Web Browser Management Tool. See Figure 2-1 for an example of ESA test results in chart form.

Network PerformanceNetwork performance is measured and reported in terms of the experience a packet encounters as it traverses a network. This performance is typically expressed in terms of the following four parameters:

• delay

• delay variation

• packet loss

• network availability

A Service Level Agreement for a service hosted on a network defines the performance expectations of the network in terms of these four parameters.


Installation and Operations Manual FSP 150CCf-825Chapter 2 - Etherjack Service AssuranceRelease 1.2, November 2007 Optical Networking

TM

DelayDelay, often referred to as latency, is the time delay experienced by a packet in traversing the network from the source to the destination.

Controlling congestion points is just one means of ensuring consistent network throughput and predictable network delay. Delay can cause significant QoS issues for sensitive services such as voice and video. Voice and video over IP can compensate for minor delays across a network, but once a threshold is exceeded, the quality of the service degrades exponentially. Network delays are typically caused by queueing points in the network. The more queues which a packet encounters, the greater is the potential for delay. The key to low latency QoS is to minimize the amount of queueing which a packet encounters when transiting the network.

Figure 2-1 ESA Test Results in Chart Format


Installation and Operations Manual FSP 150CCf-825Chapter 2 - Etherjack Service Assurance


TM

Delay VariationJitter is the variation in the delay of transmission of packets from source to destination. Some applications are more sensitive to jitter than others. Voice and video applications, for instance, cannot tolerate excessive jitter. The same techniques and mechanisms employed to manage delay are employed to bound the jitter across a network. With small queue sizes and committed bandwidths, the maximum amount of jitter which a service will experience can be computed and bounded. With appropriate tuning, a network can easily be engineered to meet the strict jitter tolerances of jitter-sensitive traffic.

Packet LossPacket loss refers to the number of packets of a particular class which are received by the network but are never delivered to the intended destination. Traffic loss is often expressed as a ratio of: (#packets not delivered at destination) / (total #packets received at source).

Packet loss can occur due to physical errors on network links, hardware faults in network equipment, and network congestion. Traffic loss can also be experienced if a service transmits more bandwidth into the network than its SLA contract specifies. Rate limiting discards packets which exceed the guaranteed bandwidth or burst size for a service. Congestion management mechanisms, such as Random Early Discard (RED), can be employed to reduce congestion within a network. Such algorithms randomly discard packets once the network nears congestion. This practice effectively limits the size of traffic bursts presented to the network.

An application’s response to packet loss is dependent on the application type. Certain applications respond by ignoring lost packets. VoIP and video applications, for instance, recover from a single lost packet by re-using the last packet received. Other applications, such as E-mail, file transfer and web applications are intolerant to packet loss. Such applications often rely on transport layer protocols, such as TCP/IP, to retransmit lost packets. Application layer protocols may also guard against packet loss using retry methods.

Network AvailabilityNetwork availability refers to the percentage of time that a network is capable of transporting packets between a source port and destination port. While a network may be capable of physically transporting packets presented to it, it may not always meet the QoS specifications for all traffic classes. Thus, we extend the definition of network availability as the percentage of time that a network is able to transport packets while meeting the QoS requirements for each traffic class supported by the network.

Failures which completely inhibit the transmission of packets are easy to detect and quantify with simple metrics, but partial failures or service degrades which impact different traffic types in different ways require QoS specific network probes and metrics.



TM

End-to-End Performance MonitoringESA enables true end-to-end performance monitoring (see Figure 2-2). In contrast, some Ethernet service providers monitor the performance of the core network only and use those results to prepare customer reports and to monitor SLAs.

By deploying the FSP 150CCf-825 at the customer premise, true end-to-end service monitoring is enabled. This capability is particularly critical if the last mile links to the customer premise are sub-Ethernet rate, such as DS3 (43 Mbps). End-to-end monitoring provides the most accurate monitoring of Ethernet connection performance.

ESA OperationThe Etherjack Service Assurance (ESA) feature provides real-time monitoring of the four major network performance metrics (delay, delay variation, packet loss and network availability) for an Ethernet circuit.

ESA operates by injecting test traffic into a live Ethernet connection and monitoring the delay, jitter and loss of the test traffic as it transits the connection. Network availability is then computed from the measured parameters.

ESA uses a special Probe object to inject test traffic into an Ethernet connection. This test traffic is targeted to another object called a Reflector. See Figure 2-3. There are two types of Reflectors. The first Reflector type is a simple Reflector which simply “echoes” the test traffic back to the Probe. The Probe object then calculates round-trip delay, jitter and loss. The second type of Reflector recognizes the injected test traffic and inserts timestamps into the test traffic before reflecting it back to the Probe. This allows the Probe to compute one-way delay and jitter.

Figure 2-2 End-to-End SLA Verification

10/100BT

IP Network10/100BT

CustomerPremise

CustomerPremise

DemarcationDevice

DemarcationDevice

Etherjack Service AssuranceEnd to End SLA Verification

Trunk LinkLink

10/100BT

IP Network10/100BT

CustomerPremise

CustomerPremise

DemarcationDevice

DemarcationDevice

Etherjack Service AssuranceEnd to End SLA Verification

Trunk LinkLink




TM

A Probe can support up to 10 active monitoring sessions each. A Reflector can terminate up to 30 sessions. ESA utilizes IP layer frames to conduct performance monitoring. Probes and Reflectors are assigned individual IP addresses to enable service monitoring across layer 2 and 3 networks.

Standard and Enhanced ReportingBoth UDP Echo and ICMP Echo packets are employed to measure connection performance. Because of this standard IP layer implementation, a Reflector can in fact be any network device that has an IP address and supports UDP echo. UDP echo provides support for standard reporting. The following round-trip measurements are available with Standard Reporting:

• Round trip delay

• Round trip jitter

• Round trip packet loss

The ICMP echo packet enables enhanced reporting which includes one-way measurements. The UDP echo packet allows for a custom packet payload. By placing timestamp data in the packet payload, an ADVA Probe / Reflector pair can determine one-way performance. In addition to standard reporting measurements, Enhanced Reporting also includes the following parameters:

• One way delay• One way jitter• One way packet loss

To perform the one-way measurement, the Probe inserts a timestamp into the ICMP echo packet as it sends the packet. When the Reflector receives the packet, it places a second timestamp in the packet indicating when the packet was received. When the Reflector sends the packet back toward the Probe, it inserts a third timestamp indicating time of transmission. When the Probe receives the original packet, it again timestamps the packet as it is received. The Probe then uses the four timestamps to calculate the one-way transmission time in both directions (Probe to Reflector and Reflector to Probe). This operation is shown in Figure 2-4.

Figure 2-3 ESA Probes and Reflectors



TM

A critical aspect of one-way measurements requires that the system clocks of the Reflector and the Probe units be synchronized to a common source. The FSP 150CCf-825 utilizes the Simple Network Time Protocol (SNTP) to synchronize the clocks of Probes and Reflectors. NTP/SNTP timing distribution protocols provide timing accuracy of about 1 msec. More accurate timing distribution mechanisms are also being investigated.

ESA Probe - Injector OperationThe ESA Packet Generator builds the ESA frame based on user configurable information such as: packet size, destination IP, VLAN tag. Prior to injecting the frame into the service flow, it inserts a timestamp. From the system perspective, the frame will appear to be coming from the customer service port, hence ESA frames will receive the same frame processing as customer frames. This ensures true end-to-end monitoring of performance and yields the most accurate results. This operation is shown in Figure 2-5.

Figure 2-4 ESA One-Way Measurements




TM

ESA Probe - Monitor OperationThe ESA packets will follow the same traffic path through the device as the customer traffic. Just prior to being sent out the customer port, the ESA filter will determine if the packet belongs to one of the active ESA sessions and diverts the packet to the Network Processor queue. Once received by the ESA Packet Processor, the receive timestamp will be inserted. The ESA Packet Processor will then process the packet and update the appropriate metrics based on the information in the packet. This operation is shown in Figure 2-6.

Reflector OperationThe ESA packets follow the same traffic path through the device as customer traffic. Just prior to being sent to the customer port, if the packet matches the ESA Filter criteria, it is diverted to the ESA Packet Processor. At the ESA Packet Processor, if the packet is an ICMP timestamp request, the Receive timestamp is inserted. The echo/timestamp request packet is then processed into an echo/timestamp reply. Just prior to leaving the ESA Packet Processor, the Send Timestamp is inserted. This operation is shown in Figure 2-7.

Figure 2-5 ESA Probe - Injector Operation

FrameProcessor

FrameProcessor

VLAN lookup, Push, Swap

FPGA

RateLimiting,

CoS,Burstableservices

AFP, Priority

processing

Classifier

Queue MgrScheduler

ESA Packet Generator

Network Processor

Probe - Injector

Uplink

Figure 2-6 ESA Probe - Monitor Operation



TM

ESA Test ConfigurationAn operator can choose to continuously monitor an Ethernet connection by scheduling ESA tests to run automatically at fixed intervals. Test results are then collected in monitoring bins and can be retrieved asynchronously. Additionally, an operator can configure the system to autonomously report ESA performance violations in “real time” through the use of performance thresholds.

2.2 ESA Operation Using eVision

Etherjack Service Assurance (ESA) provisioning and reporting is invoked by selecting the ESA icon on the Tool Bar or selecting ESA from the Applications menu and expanding the system folder in the Menu Tree.

Creating Reflectors and Probes are performed by expanding the Reflectors and Probes entities, entering a right click on one of the LAN entities and selecting Create. Up to 30 Reflectors and 10 Probes are supported. Once a Probe / Reflector Pair have been created, an ESA Scheduled Activity may be initiated to control the activity (see Scheduled ESA, on Page 2-15).

Create a ProbeThe first step in creating an ESA test is to establish a probe at one FSP 150CCf-825. See Figure 2-8 for an example of a Create Probes view. The parameters associated with a probe are:

Port – the client port on which the probe is created.

Probe Identifier – a text identifier (up to 32 characters, no spaces) for the probe.

Figure 2-7 ESA Reflector Operation

FPGAFrame

Processor

ESA Packet Processor

Network Processor

Reflector

ESA Filter Queue MgrScheduler

Queue MgrScheduler Mgmt

Frame FilterMgmt

Frame Filter

ClassifierClassifier FrameProcessor

FrameProcessor

Queue MgrScheduler

Queue MgrScheduler

Uplink




TM

Probe IP Address and Mask – the IP address and subnet mask of the probe to which echo replies will be sent.

Note 1: The IP address must not overlap with any non-ESA related subnet provisioned within the FSP 150CCf-825.

Note 2: If more than one Probe IP address resides on the same subnet, they must all be created on the same EVC.

Reflector IP Address and Mask – the IP address and subnet mask of the reflector to which echo replies (and optionally, timestamp) will be reflected back.

Protocol – the type of protocol to use (UDP Echo or ICMP Echo for General and Round Trip Delay count reporting, or ICMP Timestamp for General, Round Trip Delay, One-Way Delay and Jitter count reporting).

VLAN ID and Priority – the VLAN ID and Priority to be used for test traffic frames. To test a specific FID on an existing Flow VLAN service, the VLAN ID and Priority entry should be a member of that FID.

Service Type – specifies whether the service is VLAN Tagged or Untagged. To test a specific FID on an existing Flow VLAN service, the VLAN ID and Priority entry should be set to VLAN Tagged.

Priority Map Mode and Priority – identifies the priority classification mechanism for ESA traffic. To test a specific FID on an existing Flow VLAN service, the Priority Map Mode should match the actual service.

Packet Size – the number of bytes for each test frame.

Packets Per Sample – the number of test packets to send in a sample burst.

Packet Interval – the interval between packets in a sample burst.

Dead Interval – the settling time to wait after a sample burst is complete before starting the next sample.

Response Timeout – wait time for a response. Packets received after this time-out are considered lost.

History Bins – the number of bins of history results to keep.

History Interval – the number of minutes in a single interval.

Distribution History Bins – the number of distribution history bins to keep.

Distribution History Interval – the number of minutes in a distribution history bin.



TM

Once a Probe has been created, the Probe will appear under its corresponding LAN entity in the menu tree. You can view Probe details by expanding the LAN entity that the Probe has been created on and selecting the specific Probe entity. See the menu tree in Figure 2-9.

Selecting a specific Probe entity in the Menu Tree will display the Probe status, configuration details, count details and ESA reporting results. See Figure 2-9.

Figure 2-8 Create Probe View




TM

A Probe view provides five tabs for viewing configuration details and ESA results:

• Config tab for viewing Probe configuration and scheduling information details (see Figure 2-9).

• StatsConfig tab for viewing statistics configuration.

• Stats tab for viewing ESA counts as provisioned by entering a right click on the Probe entity and selecting Retrieve Counts (see Selecting and Viewing PM Counts, on Page 3-64 for a procedure on selecting ESA counts).

• DistStats for viewing distributed statistics results (see Figure 2-10). A Summary-Curr. tab displays the current bin, the Summary-Hist. tab displays all history bins, and the rtDelay tab displays a graph of all binned Round Trip Delays.

• Thresholds for viewing current provisioned thresholds (see Figure 2-11).

Figure 2-9 Viewing a Probe Config Tab



TM

Figure 2-10 Viewing a Probe DistStats Tab (Summary History)

Figure 2-11 Viewing a Probe Thresholds Tab




TM

Entering a right click on an existing Probe entity will provide menu selections for the specific Probe.

Menu selections available for Probe entities are: • Edit - To edit Service Parameters, Traffic Settings or Statistics and Distribution

parameters. (A Probe that is assigned to an active schedule cannot be edited.)• Delete - To delete the Probe. (A Probe cannot be deleted if it is associated with a

Scheduled ESA Activity. To delete a Probe that is associated with a Scheduled ESA Activity, the Scheduled ESA Activity must first be deleted.)

• Retrieve Counts - To select the desired PM Counts to display in the Stats tab (see Selecting and Viewing PM Counts, on Page 3-64).

• Retrieve Stats - To retrieve Distribution Statistics for a specific period.• Edit Thresholds - To edit ESA performance monitoring thresholds.• Init. PM Registers - To initialize PM registers (see Initializing PM Registers, on Page

3-70).• Init. Dist. Registers - To initialize Distribution registers (see Initializing PM Registers,

on Page 3-70).

The following thresholds may be viewed and edited by entering a right click on the Probe entity in the menu tree and selecting Edit Thresholds:

• Probe to Reflector Packets

• Reflector to Probe Packets

• Probe to Reflector Errored Packets

• Reflector to Probe Errored Packets

• Lost Packets

• Late Packets

• Number of Gaps in Sequence Numbers

• Out of Sequence Errors

• Minimum Round Trip Delay

• Maximum Round Trip Delay

• Average Round Trip Delay

• Sum of Round Trip Delays

• Sum of Square of Round Trip Delays



TM

Create a ReflectorTo create a reflector, the user specifies the following information:

Reflector ID – the Reflector identifier (up to 32 characters, no spaces)

Port – the port on which the reflector operates

Reflector IP Address, Mask – the IP address and subnet mask of the reflector. (The IP address must not overlap with any non-ESA related subnet provisioned within the FSP 150CCf-825.)

Note: Although it is possible for an FSP 150CCf-825 to contain both Reflectors and Probes, it is not possible for a Probe-Reflector pair to be on the same FSP 150CCf-825. This is determined by the subnet of the Probe and Reflector IP Address.

Once a Reflector has been created, the Reflector will appear under its corresponding LAN entities in the menu tree. You can view Reflector details by expanding the LAN entity that the Reflector has been created on and then selecting the specific Reflector entity. See the menu tree in Figure 2-13.

Entering a right click on an existing Reflector or Probe entity will provide menu selections for the specific Reflector. Menu selections available for Reflector entities are:

• Delete

• Suspend

• Resume

Figure 2-12 Create Reflectors View




TM

Scheduled ESAA scheduled ESA is invoked by selecting the ESA icon on the Tool Bar or selecting ESA from the Applications menu, expanding the system folder in the Menu Tree, entering a right click on SchGroups and selecting Create New Group. See Figure 2-14 for an example of a Create New Groups view.

The first step in creating an ESA test is to establish a probe at one FSP 150CCf-825. After one or more Probes have been created, a Scheduled ESA may be provisioned as a:

• one-shot or periodic execution• immediate or scheduled execution• continuous or fixed duration

One or more Probes may be scheduled using the same Activity ID, and multiple Scheduled ESA activities may be created. Refer to Section 5.11 Scheduled Ping and ESA Activity Settings, on Page 5-76 for detailed information on Scheduled ESA configuration options and rules.

Once a Scheduled ESA has been created, options available when entering a right click on the Activity ID in the Menu Tree are: Delete, Suspend and Resume. To delete an activity, you must first Suspend the activity.

Figure 2-13 Reflector View



TM

Once a scheduled ESA has been activated, status results may be displayed. To display PM counts, enter a right click on the appropriate Probe entity, select Retrieve Counts from the menu selection, select the desired report Group, select the desired counts to display and select OK. Then select the Stats tab to view the results. Results may be refreshed by selecting the Stats tab.

Counts available are dependant upon which Protocol type has been entered when creating the Probe and which report Group has been selected from the Groups selection list (see Table 2-1).

Figure 2-14 Create New Groups View




TM

Table 2-1 ESA Counts By Protocol Type and Report Group Probe Protocol Type Report Group Count

UDP Echo,

ICMP Echo,

ICMP Timestamp

General

Probe to Reflector Packets

Reflector to Probe Packets

Probe to Reflector Errored Packets

Reflector to Probe Errored Packets

Lost Packets

Late Packets

Number of Gaps in Sequence Numbers

Out of Sequence Errors

Probe to Reflector Lost Packets

Reflector to Probe Lost Packets

Probe to Reflector Sync Errors

Reflector to Probe Sync Errors

Round Trip Delay

Minimum Round Trip Delay

Maximum Round Trip Delay

Average Round Trip Delay

Sum of Round Trip Delays

Sum of Square of Round Trip Delays



TM

ICMP Timestamp

One Way Delay

Probe to Reflector Minimum One Way Delay

Probe to Reflector Maximum One Way Delay

Probe to Reflector Average One Way Delay

Probe to Reflector Sum of One Way Delay

Probe to Reflector Sum of Square of One Way Delays

Reflector to Probe Minimum One Way Delay

Reflector to Probe Maximum One Way Delay

Reflector to Probe Average One Way Delay

Reflector to Probe Sum of One Way Delay

Reflector to Probe Sum of Square of One Way Delays

Jitter

Probe to Reflector Minimum Positive Jitters

Probe to Reflector Maximum Positive Jitters

Probe to Reflector Number of Positive Jitters

Probe to Reflector Sum of Positive Jitters

Probe to Reflector Sum of Square of Positive Jitters

Probe to Reflector Minimum Negative Jitters

Probe to Reflector Maximum Negative Jitters

Probe to Reflector Number of Negative Jitters

Probe to Reflector Sum of Negative Jitters

Probe to Reflector Sum of Square of Negative Jitters

Reflector to Probe Minimum Positive Jitters

Reflector to Probe Maximum Positive Jitters

Reflector to Probe Number of Positive Jitters

Reflector to Probe Sum of Positive Jitters

Reflector to Probe Sum of Square of Positive Jitters

Reflector to Probe Minimum Negative Jitters

Reflector to Probe Maximum Negative Jitters

Reflector to Probe Number of Negative Jitters

Reflector to Probe Sum of Negative Jitters

Reflector to Probe Sum of Square of Negative Jitters

Table 2-1 ESA Counts By Protocol Type and Report Group (Continued)Probe Protocol Type Report Group Count




TM

ESA counts may be displayed in tabular format or chart format. Chart format may be selected within the Retrieve Counts window by selecting Show Charts. See Figure 2-15 for an example of ESA counts displayed in tabular format and see Figure 2-16, Figure 2-17 and Figure 2-18 for examples of ESA counts displayed in chart format.

Figure 2-15 ESA Test Results in Tabular Format



TM

Figure 2-16 ESA Late Packets Statistics Results in Chart Format




TM

Figure 2-17 ESA Round Trip Delay Distributed Statistics Results in Chart Format



TM

Figure 2-18 ESA One Way Probe to Reflector Distributed Statistics Results in Chart Format


Optical Networking

TM

Chapter 3 Web Browser Management Tool

3.1 OverviewThe eVision web browser management tool provides a GUI interface for Operation, Administration and Maintenance (OA&M) functions. eVision provides comprehensive support for fault, configuration, performance and security functions from a web browser (Internet Explorer version 4 or later) on a computer connected on the LAN port. See Figure 3-1.

Figure 3-1 eVision Web Browser Management Tool


Installation and Operations Manual FSP 150CCf-825Chapter 3 - Web BrowserRelease 1.2, November 2007 Optical Networking

TM

eVision simplifies the provisioning of the FSP 150CCf-825 by providing an intuitive GUI. The GUI application is resident on the FSP 150CCf-825 and can be accessed via a web browser. To access the eVision Web Browser Management Tool, the FSP 150CCf-825 must first be configured with an IP address and subnet mask. If this has not already been done, refer to Section 1.6.5 Provision Communications, on Page 1-67.

Users are provided access to all of the following functions in a single logon session. Navigation links between the applications allow you to improve productivity, e.g., retrieve configuration information while troubleshooting an alarm condition. The Web Browser Management Tool provides comprehensive FSP 150CCf-825 management, consisting of the following major applications and tools:

Alarms WindowThe Alarms window provides quick visibility and access to current alarms. Alarms are color-coded based on its severity. The Alarms window is always displayed no matter what application is currently selected, thereby providing continuous alarm monitoring. For more information, see Alarms Window, on Page 3-14 and Section 5.8 Alarm Attributes, Probable Cause and Trouble Clearing, on Page 5-49.

Configuration ViewConfiguration view provides capability to view the current status and provision the FSP 150CCf-825. All the entities of the FSP 150CCf-825, such as system settings, SNMP, SNTP, syslog, equipment, facilities, communications and user management are laid out in hierarchical order to make it easy to browse and configure. For more information, see Section 3.6 Configuration View, on Page 3-15.

Maintenance ViewMaintenance view provides a single view for all the maintenance related operations such as software upgrade, database backup and restore, operate/release loopback or protection switching, retrieve/edit alarm attributes for a given entity, and inhibit/allow messages.

In addition to standard maintenance operations, you can initiate an Etherjack® diagnostic operation, enter/edit cable benchmark information, or perform Etherjack Connection Performance Analyzer (ECPA) tests. For more information, see Section 3.7 Maintenance View, on Page 3-37.

Performance Monitoring ViewPerformance Monitoring view helps you to periodically receive the Performance Monitoring (PM) reports and chart them in an easy to read graphical form. You can retrieve the PM counts for a given entity, and its monitored parameter for a given interval (current or historical). This application also allows you to view and configure threshold values. For more information, see Section 3.8 Performance Monitoring, on Page 3-63.


Installation and Operations Manual FSP 150CCf-825Chapter 3 - Web Browser


TM

Schedule ActivitiesActivities may be provisioned using this selection for monitoring performance. Scheduled Ping is provided which provides scheduled monitoring of up to four IP addresses. Scheduled ESA provides scheduled monitoring of up to 30 Reflectors and 10 Probes (see below).

In future releases, other scheduled activities will become available, such as Scheduled ECPA. For more information, see Section 3.9 Scheduled Ping, on Page 3-72.

Etherjack® Service AssuranceThe Etherjack Service Assurance (ESA) feature is a real-time monitoring tool to allow Ethernet services to be subjectively measured for the basis of service level agreements. ESA may be implemented when FSP 150CCf-825 equipment is at both ends for round-trip reporting via Probe and Reflector, or may be implemented with only one FSP 150CCf-825 for one-way trip reporting via Probe only. Up to 30 Reflectors and 10 Probes are supported.

Standard reporting includes Round Trip Delay and Round Trip Packet Loss. Enhanced reporting includes round trip and one-way packet delay, one-way packet loss, out-of-sequence and late arrival packets, and inter-packet delay variation. In addition to performing an ESA measurement on demand, ESAs may be scheduled for periodic monitoring. For more information, see Chapter 2, Etherjack Service Assurance.

Connectivity Fault ManagementThe Connectivity Fault Management (CFM) feature provides the ability to detect, verify, isolate and report connectivity faults on a service instant. For more information, see Section 3.11 Connectivity Fault Management, on Page 3-74.

Users and SecurityUsers and associated security levels can be viewed, entered and modified by the Superuser. Other users can view and modify their own user accounts. For more information, see Section 3.12 Users and Security, on Page 3-81.

Software UpgradeSoftware may be easily updated to the current release level using the Browser Management Tool provided by the GUI interface. For more information, see Section 3.14 Software Upgrade, on Page 3-89.

Database Configuration ManagementOperations available for managing configuration data are: determining database configuration status, restore factory defaults, validation timer, backup database and restore database. For more information, see Section 3.15 Configuration Database Management, on Page 3-107.

Rescue ImageIf data transfer fails during the software upgrade, a “Rescue Image” provides a means to communicate with the FSP 150CCf-825 and allow you to complete the software upgrade. For more information, see Section 3.16 Rescue Image, on Page 3-119.



TM

Minimum System RequirementsPrior to running the web browser, verify that your PC meets the following minimum system requirements:

• 200Mhz processor

• Supported OS versions: Windows 98/2000/XP


• 128 MB of RAM

• Adobe Acrobat Reader 5.0 or greater (Reader 6.0 is included)

• Recommended display: 1024 x 768 with 16+ color bits

3.2 Logging Onto the FSP 150CCf-825Use the following procedure to log onto the FSP 150CCf-825 using a web browser.

Procedure

Step 1 Activate a web browser by double clicking on the shortcut icon.

Step 2 Enter the FSP 150CCf-825’s Management LAN port IP address in the web browser address field and enter return. A security alert window will appear

Note: The security alert window may not appear, depending on browser security settings.




TM

Step 3 Select Yes to proceed. The FSP 150CC login window appears

Step 4 Enter User ID (default is covaro1) and Password (default is covaro#1).

Step 5 Select Login. The security banner displays (the default setting is shown in the following example)

Note: If a login error appears, re-enter the user ID and password. Up to 3 login attempts will be processed. On a failed third attempt the web browser will redirect to a 401 error page (Unauthorized error). The login process must be re-started by going back to the web browser home page and re-entering the FSP 150CCf-825 IP address (at Step 2).



TM

Step 6 Select Continue. The eVision Web Browser Management Tool will display

End of Procedure




TM

3.3 User Session TimeoutEach user is provisioned with a GUI timeout of 0 (to disable logout) to 99 (minutes). Default is 30 (minutes). Only a Superuser may edit a user GUI login timeout value. When a user session is inactive for the amount of time provisioned in the GUI timeout, the user session is automatically logged off to ensure system security. Once the user timeout has occurred and the user attempts to operate or view the eVision GUI, an Authentication Failed screen is displayed as shown in Figure 3-2.

When this occurs, simply select here from the Authentication Failed screen to go to the FSP 150CC login screen, and continue with the logon sequence (see Step 3, on Page 3-5).

Figure 3-2 Authentication Failed Screen



TM

3.4 Getting Familiar with eVision Web Browser Management ToolThe eVision Web Browser Management Tool workspace is arranged to allow you to focus on the task you wish to perform. The Menu Bar, Tool Bar and Menu Tree provide easy access to the desired workflow, e.g., provisioning an entity or performing maintenance functions.

The View Area provides a different set of viewing and editing options, depending on the application selected. The Alarms window provides continuous alarm monitoring no matter what application is currently selected.

Configuration view displays when you first open eVision. The FSP 150CCf-825 system view (located in the View area) provides a physical representation of the FSP 150CCf-825, its current provisioning configuration and alarm status. Alarm details are displayed in the Alarms Window. Refer to Figure 3-3 for an example of a system entity selected in Configuration view and each component of the web browser window.

Figure 3-3 eVision Web Browser Management Tool Components

Title Bar

Menu Bar

Tool Bar

Menu Tree

Alarms WindowStatus Bar

View Tabs

Login Name

EntityView Area

SystemName

Secure Session Indicator




TM

3.5 About the WorkspaceThe workspace consists of the following components:

• Title Bar

• Menu Bar

• Tool Bar

• Menu Tree

• View Area

• Alarms Window

• Status Bar

Title BarThe Title Bar indicates which application is currently selected. The view mode is dependant upon what Tool Bar icon is selected, or which Application is selected from the Menu Bar. The Title Bar also allows you to minimize, maximize, restore down or close the eVision Web Browser Management Tool window.

Menu BarThe Menu Bar contains menus for performing tasks. The Menu Bar topics are:

Menu Description

File Provides options for: saving changes, rebooting the FSP 150CCf-825, restoring to factory defaults, validation timer and logging out.

Applications Allows selection of eVision applications (Configuration, Maintenance, Performance Monitoring, Etherjack Service Assurance and scheduling activities.



TM

Tool BarThe Tool Bar provides a selection of applications (views) for managing tasks. The tool options provided on the Tool Bar are:

Tool Bar Icon Application Description

Configuration

Allows you to perform provisioning functions, such as editing system, equipment, facilities or users. Various views are provided when Configuration view is selected, depending upon what folder or entity is selected in the Menu Tree. When entering a right click on a folder or entity from the Menu Tree, provisioning options become available in menu form. Options available to the user are dependent upon the user access permission level.

Maintenance

Allows you to perform maintenance functions, such as loopbacks and diagnostics. When entering a right click on a folder or entity from the Menu Tree, maintenance options become available in menu form. Various views are provided, depending upon what folder or entity is selected in the Menu Tree. Options available to the user are dependent upon the user access permission level.

Performance Monitoring

Allows you to retrieve performance monitoring counts in columnar or chart format. Performance monitoring thresholds can be edited or displayed, and registers can be initialized (depending on the user access permission level).

Schedule Activities

Allows you to perform a scheduled ping, providing a current state of management link connectivity. A list of IP addresses can be provisioned to automatically ping periodically, and raise an alarm in result of a communications failure.

Save Configuration Allows you to save configuration changes.

Validation Timer

Allows you to make configuration changes to the current database without saving to non-volatile memory. If a change causes a loss of the communications link, after a specified amount of time, the safe mode timer will expire and automatically revert back to the old database. If communications is successful following the configuration change, you can manually commit the transaction to non-volatile memory by exiting safe mode.

ESA

Allows you to perform a manual or scheduled Etherjack Service Assurance (ESA). The ESA feature is a real-time monitoring tool to allow Ethernet services to be subjectively measured for the basis of service level agreements.

CFMConnectivity Fault Management (CFM) provides the ability to detect, verify, isolate and report connectivity faults on a service instance.




TM

Menu TreeThe Menu Tree (located on the left of the screen) provides the ability to quickly view current status of an entity and provides menu selectable options for an entity. A hierarchical tree of entities are displayed in the Menu Tree when the Configuration, Maintenance or Performance Monitoring, Schedule Activity or Etherjack Service Assurance application is selected from the Tool Bar or is selected via the Applications menu on the Menu Bar.

Each Menu Tree entity is representative of a specific equipment, facility, path, etc. Entities are arranged in hierarchical order, e.g., to gain access to a management tunnel, the communications menu must first be opened. Menu tree nested items are opened or closed by clicking on the + or - symbol next to the entity, respectively. Once nested items are opened, the entity item is expanded, displaying nested items.

A “pointing hand” curser (displayed when hovering the cursor over an entity within the menu tree) indicates there are menu selectable items available for that entity, and if a right mouse click is entered on that entity, applicable menu selectable items will appear. See Figure 3-4 for an example of a Menu Tree with menu selected. Menu selectable items are bold and non-selectable items are grey. If an I-beam cursor is displayed, it indicates there are no menu selectable items for that entity within the currently selected application.

When an entity is selected within the Menu Tree, the corresponding entity status is displayed in the View Area. The status displayed in the view area is dependent upon which application is currently selected. For example, if Configuration view is selected, and a LAN facility is selected in the Menu Tree, facility status information such as assigned state, operational state and EVC mode status will be displayed. If the same LAN facility is selected in the Menu Tree while in Maintenance view, the view area will display Etherjack diagnostics results and alarm attributes.

Figure 3-4 Menu Tree with Menu Selected



TM

View AreaViews displayed are dependent upon which application is selected from the Tool Bar or Applications Menu. Many views provide tabs to select categories of information regarding the entity. See Figure 3-5 for an example of tab selections in the View Area.

In addition to viewing entity status, the View Area also provides edit or operate functions once an applicable menu item is selected from the Menu Tree. See Figure 3-6 for an example of an edit Transparent LAN facility window. A LAN facility may be edited within the View Area by selecting menu items, entering data and selecting buttons. Valid options are displayed in white while unselectable options are grey.

View Area menu selections may be made by either selecting an option via the menu, or by selecting the menu field and using the up/down arrows to change the menu option. You can move from field to field by either clicking within the desired field or by using the tab key.

Once an option selection is made, only valid options for related parameters become available for selection or data entry. Using the example shown in Figure 3-6, if Port/EVC Mode is changed from Transparent to Flow VLAN, options such as Ingress CIR, Ingress PIR, Ingress

Figure 3-5 Tab Selections in the View Area

Tabs




TM

Rate Limiting and C-Tag/S-Tag Control will become unavailable for selection or data entry at the Port level, and options such as Acceptable Frame Policy and Priority Map Mode become selectable.

Figure 3-6 Edit Transparent LAN Facility View



TM

Alarms WindowThe Alarms window provides easy access to current alarms. See Figure 3-7.

All alarms are color-coded by severity: red (Critical), orange (Major) and yellow (Minor). Each alarm and its interface type, notification code, a brief description, and time stamp are listed as a separate line item.

Status BarThe Status Bar, located at the bottom of the web browser window (see Figure 3-3, on Page 3-8) displays FSP 150CCf-825 operations status when menu selected items are in progress.

Applications MenuThe following Application Menu selections are provided for managing tasks:

• Configuration View

• Maintenance View

• Performance Monitoring

• Scheduled Ping

Figure 3-7 Alarms Window




TM

3.6 Configuration ViewConfiguration view allows you to perform provisioning functions, and view provisioning attributes of the entity that is selected in the Menu Tree or the entity View Area. Alarm status is displayed in the Alarms Window located at the bottom of the screen, providing constant visibility and access to current alarms. Options available to you are dependent upon your user access permission level and the current entity status.

The following configuration changes can be applied and current status can be viewed within Configuration View (refer to Chapter 5, Configuration Settings and Technical Data for provisioning options, default values and provisioning rules for each entity):

• System - System level settings can be viewed by selecting the system name in the menu tree (default is the FSP 150CC variant name) and selecting either the Identification, SNTP, Syslog, CPD (Control Protocol Disposition) Filters, ACL (Access Control List) or Banner tab. You can edit system, SNTP, Syslog, Security Banner or Access Control List settings by entering a right click on the system name and selecting the desired menu option.

• Facility (LAN and WAN) - By entering a right click on the facility in the menu tree and selecting menu options, you can change the Administration State, view or modify specific facility operating parameters, edit the LAN or WAN Control Protocol Disposition (CPD), and in the case of a Flow VLAN facility, you can create flows and edit the priority map. Refer to Section 3.6.1 Provisioning LAN Interface(s), on Page 3-17 for LAN provisioning procedures.

• PSUs - By right clicking on a PSU entity in the menu tree, you can assign/unassign and edit the Administrative State.

• Protection Groups - A Link Aggregation Group (LAG) may be created, edited or deleted by expanding the Protection Groups entity and LAG entity (if present), by entering a right click on the entity and selecting the desired menu option.

• Communication - By entering a right click on the Communication entity in the menu tree, you can create or delete a static route, add or delete an ARP entry on the local management port, LAN or WAN. By expanding the Communication folder and entering a right click on the desired communication entity, you can change the Administration State or edit specific facility parameters for the local management port, LAN management tunnel or WAN management tunnel.

• SNMP - Simple Network Management Protocol communities, target addresses and V3 users can be provisioned by entering a right click on SNMP in the menu tree and selecting either Add Community, Add Target Address or Add V3 User. To delete a Community/Target Address, select SNMP in the menu tree and the Community or Target Address tab, enter a right click on the desired entity and select Delete Entry. A V3 User may be edited or deleted by selecting SNMP in the menu tree and the V3 User Info tab, entering a right click on the desired V3 User and selecting either Delete Entry, Edit Entry or Change Password.



TM

• Users - By expanding the Administration folder and entering a right click on Users in the menu tree, the Superuser can view all users and create a new user. By expanding the Users folder and entering a right click on a specific user ID and selecting either Edit User, Edit Password or Delete User, the Superuser can edit the user privilege level and comment, change the User ID and password, or delete a user. See Section 3.12 Users and Security, on Page 3-81 for procedures for creating, deleting and editing users information.

• Remote Authentication- RADIUS and TACACS+ properties can be edited by expanding the Administration folder, entering a right click on Remote Authentication in the menu tree and selecting Edit.

Viewing Entities in Configuration ViewVarious views are provided when Configuration view is selected, depending upon what entity is selected in the Menu Tree. Entity views provide current provisioning and alarm attributes, and a means to provision the entity by entering a right click on the entity in the Menu Tree. Refer to Figure 3-8 for an example of a Transparent LAN facility in Configuration view.

Figure 3-8 Configuration View (Transparent LAN Facility View)




TM

Provisioning Entities in Configuration ViewWhen entering a right click on an entity folder or file from the Menu Tree and selecting Edit <entity>, provisioning options become available in menu form. Options available to you are dependent upon your user access permission level, and the current entity and option status. Refer to Figure 3-9, on Page 3-19 and Figure 3-11, on Page 3-26 for an example of edit Transparent LAN facility and create Flow provisioning options available in Configuration view, respectively.

3.6.1 Provisioning LAN Interface(s)Refer to the following procedures for creating and editing LAN interfaces. There are three procedures for provisioning LAN interfaces:

• Provisioning a LAN to Transparent EVC Mode, on Page 3-17

• Provisioning a LAN to Connection-oriented Flow VLAN EVC Mode, on Page 3-22

• Provisioning a LAN to Connection-less Flow VLAN EVC Mode, on Page 3-31

Provisioning a LAN to Transparent EVC ModeThis procedure can be used for provisioning one or more LAN in Transparent EVC mode using the eVision web browser. It is recommended that you pre-determine the provisioning details and ensure that they meet the FSP 150CCf-825’s provisioning rules prior to making changes to a LAN or placing an additional LAN into service. Ensure that CIR, EIR and C-Tag/S-Tag VLAN ID-Priority values will not conflict with another LAN/Flow that is in the Assigned state.

Refer to Transparent LAN Service Provisioning, on Page 5-21 to determine the default values, value ranges and rules for each option in the following procedure. For Control Data Protocol provisioning, see Section 5.6 CPD Configuration Options and Rules, on Page 5-42.

Procedure

Step 1 Observe the current LAN Port Mode and EVC Mode. The status will be used in the following steps.

eVision

Select Configuration view

Expand the System Name entity in the Menu Tree

Select the LAN facility in the Menu Tree The LAN facility status window is displayed



TM

WARNING — Changing EVC Mode on a facility will drop all traffic on the port, including Management Tunnel connectivity and Maintenance End Points.


Step 3 Enter a right click on the LAN facility and select CO Mode (Connection-oriented Mode). A warning screen appears, indicating selection of this option will cause a loss of all traffic

Step 4 Select OK. The EVC Mode changes to Transparent

Step 5 Go to Step 8.

Step 6 Enter a right click on the LAN facility and select CO Transparent (Connection-oriented Transparent mode). A warning screen appears, indicating selection of this option will cause a loss of all traffic


Current Status Then

Is the current EVC Mode set to Transparent? Go to Step 8.

Is the Port Mode set to Connection-oriented and EVC Mode set to Flow VLAN?

Go to Step 6.

Is the Port Mode set to Connection-less and EVC Mode set to Flow VLAN?





TM

Step 8 Right click on the LAN facility in the Menu Tree and select Edit Facility. An edit Transparent LAN facility window appears

Figure 3-9 Edit Transparent LAN Facility View



TM

Step 9 Enter the LAN facility changes.

Note: See Transparent LAN Service Provisioning, on Page 5-21 for default values, value ranges and provisioning rules for each option in the above table.

Step 10 Verify the changes.

Step 11 Observe the current LAN facility Assigned/Unassigned State: (The LAN facility should still be selected in the menu tree.)


eVision

Enter a Circuit Name, as required

Set the Administration State to Enabled

For LAN-5: Select the desired Media Type

Enter the desired Interface Speed

Enter the Ingress CIR, EIR, CBS, EBS and Buffer Size values

Enable or disable Egress Rate Limiting

If Egress Rate Limiting is set to enabled: Egress setting options are displayed. Enter the desired Egress CIR, EIR, CBS, EBS and Buffer Size

Select the desired C-Tag Control

If C-Tag Control is set to Push: Enter the appropriate C-Tag VLAN ID and C-Tag VLAN Priority

Select the desired S-Tag Control

If S-Tag Control is set to Push: Enter the appropriate S-Tag VLAN ID and S-Tag VLAN Priority

Enable or disable Tagged Frames and Untagged Frames

Select/enter other options, as required

Select OK The LAN facility status window appears

Current Status Then

Is the current Assigned/Unassigned State set to Enabled?

Go to Step 14.

Is the current Assigned/Unassigned State set to Disabled?





TM

Step 13 Place the LAN facility to the Assigned state.

Note: If you receive an error message indicating the CIR and/or EIR values exceed the maximum allowed, and/or the C-Tag/S-Tag VLAN ID-Priority values conflict with existing ones, then one or more LAN values must be changed in order to co-exist. These changes must be made by editing the LAN(s) prior to placing this LAN to the Assigned state.

Step 14 Save the configuration in eVision by selecting File and then Save Changes from the menu bar.

End of Procedure

eVision

Enter a right click on the LAN facility in the menu tree and select Assign A confirmation window appears

Select OK The LAN facility status window appears and the LAN Assigned/Unassigned State is Enabled



TM

Provisioning a LAN to Connection-oriented Flow VLAN EVC ModeThis procedure can be used for provisioning one or more LAN in Flow VLAN EVC mode using the eVision web browser. It is recommended that you pre-determine the provisioning details and ensure that they meet the FSP 150CCf-825’s provisioning rules prior to making changes to a LAN/Flow or placing an additional LAN/Flow into service. Ensure that the Flow’s CIR, EIR and C-Tag/S-Tag VLAN ID-Priority values will not conflict with another LAN/Flow that is in the Assigned state. Refer to Section 5.5.2 Connection-oriented Flow VLAN Service Provisioning, on Page 5-26 to determine the default values, value ranges and rules for each option in the following procedure. For Control Data Protocol provisioning, see Section 5.6 CPD Configuration Options and Rules, on Page 5-42.

Procedure




eVision




Desired Changes Assigned/ Unassigned

State

Then

Change the Port/EVC Mode from Transparent to Connection-oriented Flow VLAN?

Don’t care Continue with the next step.

Change the Port/EVC Mode from Connection-less Flow VLAN to Connection-oriented Flow VLAN?

Don’t care Go to Step 6.

Edit the LAN facility? Don’t care Go to Step 9.

Edit an existing FID? (Flow Type and Multi COS cannot be edited)


Create a new FID?

Enabled Go to Step 19.

Disabled Go to Step 14.




TM

Step 3 Enter a right click on the LAN facility and select CO Flow VLAN Mode (Connection-oriented Flow VLAN mode). A warning screen appears, indicating selection of this option will cause a loss of all traffic

Step 4 Select OK. The Port/EVC Modes changes to Connection-oriented Flow VLAN


Step 6 Enter a right click on the LAN facility and select CO Mode (Connection-oriented Services mode). A warning screen appears, indicating this option will cause a loss of all traffic

Step 7 Select OK. The Port/EVC Mode changes to Connection-oriented Transparent


Step 9 Right click on the LAN facility in the Menu Tree and select Edit Facility. An edit Connection-oriented Flow VLAN facility window appears

Figure 3-10 Edit Connection-oriented Flow VLAN Facility View



TM

Step 10 Enter the Connection-oriented Flow VLAN facility changes.

Note: See Section 5.5.2 Connection-oriented Flow VLAN Service Provisioning, on Page 5-26 for default values, value ranges and provisioning rules for each option in the above table.




eVision





Select the desired Acceptable Frame Policy

If Acceptable Frame Policy is set to All: Enter the Port VLAN ID (See Note 1)

Enable or disable Egress VLAN Trunking, Ingress PUSH Port VLAN ID and Egress POP Port VLAN ID options

Select the desired Priority Map Mode

If Acceptable Frame Policy is set to All: Enter the Priority VLAN ID (See Note 2)

Enable or disable Untagged Frames



Current Status Then


Go to Step 15.






TM


Step 15 If Priority Map Mode is set to anything other than Off, and if required, edit the Priority Mapping Table for the first Index. Otherwise, go to Step 18.

Note: If multiple indexes are selected, they will all be changed to the same PRIOCTL, Priority and Policer COS options when they are selected.

Step 16 Select the Priority Map tab to verify the changes.

Step 17 Repeat Step 15 and Step 16 for each additional Index to be changed or to edit the changes made.


eVision

Enter a right click on the LAN facility in the menu tree and select Assign


eVision

Right click on the LAN facility and select Edit Priority A priority map index window appears

Select the first Index to be changed. If other Indexes will be changed to the same Priority Control, Priority and Latency options, select additional Indexes by using Control+Click. To select a contiguous set of Indexes, select the first desired Index, then enter a Shift+click on the last desired Index in the range of Indexes. (See Note)

Select OK A Priority map settings window opens

Select the desired X-Tag PRIOCTL option

If X-Tag PRIOCTL is set to Swap: Select the desired X-Tag Priority

Select the desired Policer COS

Select OK

Current Status Then

Are all LAN changes completed and you want to create a Flow?


Are all LAN changes completed and no Flows need to be created?

Go to Step 26.



TM

Step 19 Right click on the LAN facility and select Create Flow. A create flow window appears

Figure 3-11 Create Connection-oriented Flow View




TM

Step 20 Enter the desired Flow options.


eVision

Select the desired Flow ID


Select the flow Type

Enable or Disable Untagged Frames Supported option

Select the desired C-Tag Control option If C-Tag Control is set to anything other than None: Enter the appropriate C-Tag VLAN ID (and C-Tag VLAN Priority, if allowed)

Select the desired S-Tag Control option If S-Tag Control is set to Push: Enter the appropriate S-Tag VLAN ID and S-Tag VLAN Priority

Enable or disable Multi COS


If Multi COS is set to Enabled: Ingress Policer options are displayed (see Figure 3-12). Select the desired Ingress Policer(s) and enter the desired Policer option settings

If Multi COS is set to Enabled and Egress Rate Limiting is set to Enabled: Egress Policer options are displayed. Select the desired Egress Policer(s) and enter the desired Policer option settings

If Multi COS is set to Disabled: Enter the Ingress CIR, EIR, CBS, EBS and Buffer Size values

If Multi COS is set to Disabled and Egress Rate Limiting is set to Enabled: Egress setting options are displayed. Enter the desired Egress CIR, EIR, CBS, EBS and Buffer Size values

If flow Type is Regular: Scroll down to the VLAN Members section. Enter the first VLAN Member and select Add. Enter additional VLAN Members and select Add, as required. To delete a VLAN Member, select the VLAN Member to be removed, and then select Remove.

Select OK The LAN status window appears



TM


Figure 3-12 Options Available When Multi COS is Enabled

eVision

Expand the LAN entity in the Menu Tree The new FID entity is present

Select the new FID in the Menu Tree The current options settings are displayed in the FID status window




TM


Step 23 Edit the existing Flow (Flow Type and Multi COS cannot be edited).

Current Status Then

Are changes required to a Flow Identifier (FID)? Continue with the next step.

Are all FID options correct and you want to create another FID on the LAN?

Go to Step 19 to create the FID.

Are all FID options correct and no other changes are required for the LAN?

Go to Step 26.

eVision

Expand the LAN facility in the Menu Tree

Enter a right click on the Flow to be edited and select Edit Flow An edit flow window appears


Enable or Disable Untagged Frames Supported option

Select the desired C-Tag Control option If C-Tag Control is set to anything other than None: Enter the appropriate C-Tag VLAN ID and C-Tag VLAN Priority

Select the desired S-Tag Control option If S-Tag Control is set to Push: Enter the appropriate S-Tag VLAN ID and S-Tag VLAN Priority


If Multi COS is set to Enabled: Ingress Policer options are displayed (see Figure 3-12). Select the desired Ingress Policer(s) and enter the desired Policer option settings

If Multi COS is set to Enabled and Egress Rate Limiting is set to Enabled: Egress Policer options are displayed. Select the desired Egress Policer(s) and enter the desired Policer option settings

If Multi COS is set to Disabled: Enter the Ingress CIR, EIR, CBS, EBS and Buffer Size values

If Multi COS is set to Disabled and Egress Rate Limiting is set to Enabled: Egress setting options are displayed. Enter the desired Egress CIR, EIR, CBS, EBS and Buffer Size values

If flow Type is Regular: To add a VLAN Member, enter additional VLAN Members and select Add, as required. To delete a VLAN Member, select the VLAN Member to be removed, and then select Remove.

Select OK The FID status window appears



TM





End of Procedure




TM

Provisioning a LAN to Connection-less Flow VLAN EVC ModeThis procedure can be used for provisioning one or more LAN in Flow VLAN EVC mode using the eVision web browser. It is recommended that you pre-determine the provisioning details and ensure that they meet the FSP 150CCf-825’s provisioning rules prior to making changes to a LAN/Flow or placing an additional LAN/Flow into service. Ensure that the Flow’s CIR, EIR and C-Tag/S-Tag VLAN ID-Priority values will not conflict with another LAN/Flow that is in the Assigned state. Refer to Section 5.5.3 Connection-less Flow VLAN Service Provisioning, on Page 5-35 to determine the default values, value ranges and rules for each option in the following procedure. For Control Data Protocol provisioning, see Section 5.6 CPD Configuration Options and Rules, on Page 5-42.

Procedure




eVision




Desired Changes Assigned/ Unassigned

State

Then

Change the Port/EVC Mode from Transparent to Connection-less Flow VLAN?


Change the Port/EVC Mode from Connection- oriented Flow VLAN to Connection-less Flow VLAN?

Don’t care Continue with the next step.

Edit the LAN facility? Don’t care Go to Step 8.

Edit an existing FID? Don’t care Go to Step 18.

Create a new FID? Enabled Go to Step 14.

Create a new FID? Disabled Go to Step 12.



TM

Step 3 Enter a right click on the LAN facility and select CO Transparent (Connection-oriented Transparent mode). A warning screen appears, indicating selection of this option will cause a loss of all traffic


Step 5 Enter a right click on the LAN facility and select CL Mode (Connection-less Flow VLAN mode). A warning screen appears, indicating this option will cause a loss of all traffic

Step 6 Select OK. The Port/EVC Mode changes to Connection-oriented Flow VLAN

Step 7 Right click on the LAN facility in the Menu Tree and select Edit Facility. An edit Connection-oriented Flow VLAN facility window appears

Figure 3-13 Edit Connection-less Flow VLAN Facility View




TM

Step 8 Enter the Connection-less Flow VLAN facility changes.





eVision



Enter the desired Bridge Age Time and MAC Table Size

Select the desired MAC Table Full option





Current Status Then


Go to Step 13.



eVision

Enter a right click on the LAN facility in the menu tree and select Assign




TM


Step 14 Right click on the LAN facility and select Create Flow. A create flow window appears

Current Status Then

Are all LAN changes completed and you want to create a Flow?


Are all LAN changes completed and no Flows need to be created?

Go to Step 21.

Figure 3-14 Create Connection-less Flow View




TM

Step 15 Enter the desired Flow options.

Note: See Section 5.5.3 Connection-less Flow VLAN Service Provisioning, on Page 5-35 for default values, value ranges and provisioning rules for each option in the above table.



eVision

Select the desired Flow ID


Enter the appropriate C-Tag VLAN ID and C-Tag VLAN Priority

Enter the appropriate S-Tag VLAN ID and S-Tag VLAN Priority



If Egress Rate Limiting is set to Enabled: Egress setting options are displayed. Enter the desired Egress CIR, EIR, CBS and EBS values

Select OK The LAN status window appears

eVision

Expand the LAN entity in the Menu Tree The new FID entity is present

Select the new FID in the Menu Tree The current options settings are displayed in the FID status window

Current Status Then

Are changes required to a Flow Identifier (FID)? Continue with the next step.

Are all FID options correct and you want to create another FID on the LAN?

Go to Step 14 to create the FID.

Are all FID options correct and no other changes are required for the LAN?

Go to Step 21.



TM

Step 18 Edit the existing Flow.

Note: See Section 5.5.3 Connection-less Flow VLAN Service Provisioning, on Page 5-35 for default values, value ranges and provisioning rules for each option in the above table.




End of Procedure

eVision

Expand the LAN facility in the Menu Tree

Enter a right click on the Flow to be edited and select Edit Flow An edit flow window appears


Enter the appropriate C-Tag VLAN ID and C-Tag VLAN Priority

Enter the appropriate S-Tag VLAN ID and S-Tag VLAN Priority



If Egress Rate Limiting is set to Enabled: Enter the desired Egress CIR, EIR, CBS and EBS values.

Select OK The FID status window appears




TM

3.7 Maintenance ViewMaintenance View allows you to perform maintenance functions, such as performing diagnostics, activating loopbacks, setting and retrieving alarm attributes, upgrading software, and database backup and restore.

When entering a right click on an entity in the Menu Tree, maintenance options become available in menu form. Options available to you are dependent upon your user access permission level and current entity status. Alarm status is displayed in the Alarms Window located at the bottom of the screen, providing constant visibility and access to current alarms. Options available to you are dependent upon your user access permission level.

The following current status can be viewed and maintenance operations can be performed within Maintenance View:

• LAN Facility - Options available are: Diagnose, Edit Alarm Attributes, Loopback, Edit Etherjack Connection Performance Analyzer (ECPA) Streams and Analyze ECPA. By entering a right click on the LAN facility entity in the menu tree and selecting menu options, you can perform a diagnostic, operate or release a Terminal or VLAN loopback, enter/edit cable benchmark information, edit ECPA streams, perform an ECPA test or edit alarm attributes for the LAN facility.

• WAN Port/Facility - Options available are: Edit Alarm Attributes and Loopback. By entering a right click on the WAN entity in the menu tree and selecting menu options, you can operate or release a loopback, perform a protection switch operation, or edit alarm attributes.

• Communication - Selecting the Communication entity will display the Routing Table, ARP Table, PARP Table and operation status. By entering a right click on the Communication entity, menu options available are: Ping, Trace Route, Flush ARP Cache and Flush PARP Cache.

• Administration - By expanding the Administration folder, software upgrade, and database backup and restore functions are available from the Software and Database entities. Options available are: Software Upgrade, Backup Database, Copy to Server, Copy from Server and Restore Database. A procedure for performing a software update is provided in Section 3.14 Software Upgrade, on Page 3-89 and more details for managing the configuration database are provided in Section 3.15 Configuration Database Management, on Page 3-107.



TM

Viewing LAN, WAN and PSU Entities in Maintenance ViewWhen selecting a LAN facility, WAN facility or PSU entity in Maintenance View, Operations and Alarm Attributes views are available by selecting the associated tab in the view area. When selecting a LAN facility Operations Tab in Maintenance View, the LAN status and an Etherjack Summary is initially displayed (see Figure 3-15).

The Etherjack Summary shows a graphical view of the results of the last Etherjack diagnostic test, the type of test that was run, and the date and time the test was performed. Selecting the Details tab will display the detailed results of the last Etherjack diagnostic test.

Selecting the Alarm Attributes Tab displays the current Notification Code assigned to each Alarm Attribute/Condition Type (see Figure 3-16).

Figure 3-15 Maintenance View of LAN Facility (Operations Tab)




TM

Figure 3-16 Maintenance View of LAN Facility (Alarm Attributes Tab)



TM

3.7.1 Editing Alarm AttributesAn Edit Alarm Attributes window is accessed in Maintenance view by entering a right click on a LAN facility, WAN facility or PSU and selecting Edit Alarm Attributes (see Figure 3-17). For Connectivity Fault Management (CFM), alarm attributes may be edited by entering a right click on the MEP ID entity and selecting Edit Alarm Attributes.

Notification Codes can be edited for a given Condition Type by selecting the desired Notification Code in the drop down menu, then selecting OK.

Notification Codes available for selection are:• Critical• Major• Minor• Not Alarmed• Not Reported

Figure 3-17 Edit Alarm Attributes Window




TM

3.7.2 LoopbackEntering a right click on the WAN or LAN and selecting Loopback will provide a Loopback view. From this view, the LAN or WAN facility can be placed in the Testing state and a loopback or timed loopback can be performed at the terminal or facility. If performing a terminal or facility VLAN loopback, up to three VLAN loopbacks may be created per entity.

Selecting the Swap SA/DA [Swapping the Source Address (SA) with the Destination Address (DA)] option during the loopback will direct the FSP 150CCf-825 to look up the MAC address of frames being received and swap out the Source Address with the Destination Address, allowing the Layer 2 cloud to forward the frames.

VLAN and Swap SA/DA functions are performed by the Media Controller Converter (MCC). Only one VLAN and/or Swap SA/DA loopback may be performed per system. Once a VLAN and/or Swap SA/DA loopback has been operated, a second Swap SA/DA loopback may not be performed on another entity.

Another option available is performing a Remote EFM-OAM loopback. See Figure 3-18 for an example of a loopback view.

Figure 3-18 Loopback View (WAN)



TM

3.7.3 Etherjack® Diagnostics

An Etherjack® diagnostics can be performed by entering a right click on the LAN in the menu tree and selecting Diagnose. The current maintenance status is displayed (see Figure 3-19). From this view you can place the LAN facility in the maintenance state (Administrative State: Testing), select the desired test to be run, view test results and place the LAN facility back to the In Service state (Administrative State: Enabled). Next and Back buttons are provided to navigate back to the previous screen and forward to the next step in the diagnostic process.

Upon completion of an Etherjack diagnostics test, a diagnostic result screen is displayed, showing a diagnostic result summary, diagnostic details and a cable benchmark summary. Refer to Figure 3-20 for an example of completed Etherjack diagnostics results where all tests have passed.

Figure 3-19 Etherjack® Diagnostic Status




TM

Within the Diagnostic Summary section, a graphic identifies whether tests have passed at the FSP 150CCf-825, cable and customer. If the test(s) pass a green check mark will be displayed. If a test failure is detected, a red “X” will appear at the location of the failure (FSP 150CCf-825, cable or customer location). In the example diagnostic summary graphic shown in Figure 3-21, a failure was detected in the cable. If a portion of a test was not run (i.e. an open cable prevents the capability of performing an auto-negotiation test) a yellow warning sign will be displayed, as shown in Figure 3-21.

The Diagnostic Summary also identifies the test that was run and the date and time the test was performed.

Figure 3-20 Etherjack® Diagnostic Results - All Tests Passed



TM

The Diagnostic Details section shows the test result details, including the location of a cable fault, if present, as shown in Figure 3-21.

The Cable Benchmark Summary will identify the physical cable length of each cable segment lengths (up to 5) from the FSP 150CCf-825 to the customer equipment and identify a detected faulty segment. The Cable Benchmark Summary will only display this information if each cable segment has been stored during the installation process. For more details on the Cable Benchmark feature, continue to the next page.

Figure 3-21 Etherjack® Diagnostic Results - Failure Detected




TM

3.7.4 Cable Length BenchmarkThis feature provides a means to store up to 5 cable segment lengths during the installation process, and in conjunction with the Etherjack Diagnostic test, will identify a specific faulty cable segment. Each cable segment can be named with a text string to describe the physical location of each segment. Cable segment lengths can be manually entered or saved after performing an Etherjack diagnostic.

If a subsequent Etherjack diagnostic results in an open circuit at one of the stored segments, eVision will highlight the location name of the faulty segment, and the test operator can quickly determine if the fault is located at a particular patch panel. See Figure 3-22 for an example of Etherjack diagnostics results highlighting a detected open segment location.

Figure 3-22 Cable Length Benchmark Using Etherjack® Diagnostics



TM

Refer to the following procedures to enter/edit cable length benchmarks:

• Entering Cable Length Benchmarks Using Etherjack Test Measurements

• Manually Entering / Editing Cable Length Benchmarks

Entering Cable Length Benchmarks Using Etherjack Test MeasurementsUse the following procedure to enter cable length benchmarks (up to 5 per LAN) by using Etherjack test measurements to enter cable length data.

Procedure

Step 1 Go to the end of the first cable segment location from the FSP 150CCf-825 and open the cable termination point toward the next segment

Step 2 Perform an Etherjack Diagnostic and enter the cable benchmark for the first cable length segment.

Note: The Capture option is only applicable if an open circuit has been detected.

eVision

Select Maintenance view

Right click on the LAN in the menu tree

Select Diagnose

Select Remove from the LAN Status screen The LAN Administrative State changes to the Testing state

Select Next

Select either All Ethernet Tests or Ethernet Cable test from the test type drop down menu

Select Diagnose After a few moments the test result screen will display

Select Capture (See Note) A Cable Benchmark Information entry screen displays

Enter a description name for the cable segment (up to 24 characters) in the information field

Select Apply




TM

Step 3 Select Diagnose to verify the FSP 150CCf-825 identifies the first cable segment is open. The first segment location should be highlighted in the Cable Benchmark Summary

Step 4 Reconnect the cable termination point toward the second cable segment, as required. Go to the end of the second cable segment location from the FSP 150CCf-825 and open the cable termination point.

Step 5 Perform an Etherjack Diagnostic and enter the cable benchmark for the second cable length segment.

Note: The Capture option is only applicable if an open circuit has been detected.

Step 6 Select Diagnose to verify the FSP 150CCf-825 identifies the second segment location is open. The second segment location should be highlighted in the Cable Benchmark Summary

Step 7 Repeat Step 4 through Step 6 for each additional segment (a total of 5), as required, up to the customer premise.

Step 8 Reconnect the last segment to the customer premise equipment and perform an Etherjack diagnostic to verify connectivity is restored to the customer equipment.

eVision

Select Back

Select either All Ethernet Tests or Ethernet Cable test from the test type drop down menu


Select Capture (See Note) A Cable Benchmark Information entry screen displays


Select Apply

eVision

Select Back

Select All Ethernet Tests from the test type drop down menu




TM

Step 9 Restore the LAN facility.

End of Procedure

eVision

Select Next

Select Restore

Verify the restoration of the LAN facility The Administrative State changes to Enabled

Select Finish The LAN maintenance status window appears




TM

Manually Entering / Editing Cable Length Benchmarks Cable length benchmarks can be manually entered or existing cable length benchmarks may be edited as shown in Figure 3-23. Use the following procedure to edit existing cable length benchmarks or manually entering cable length benchmarks. Up to 5 cable length benchmarks can be saved per LAN.

Figure 3-23 Edit Cable Length Benchmark Information Screen



TM

Procedure

Step 1 Enter or edit the cable benchmarks for the desired LAN.

Note: To delete a cable point, deselect the desired Cable Point number selection box. If a Cable Point selection box is not selected, it will be deleted from the list.

Step 2 If desired, open one of the cable segments at its termination point and perform an Etherjack diagnostic to verify a cable benchmark entry.

eVision


Right click on the LAN in the menu tree

Select Diagnose

Select Remove from the LAN Status screen The LAN Administrative State changes to the Testing state

Select Next

Select Cable Benchmark from the test type drop down menu

Select Edit The Cable Benchmark entry screen appears (see Figure 3-23)

Ensure that all desired Cable Points to be kept are selected, and deselect any Cable Points you with to delete (See Note)

Enter the desired cable length(s) in meters (decimal is allowed)


Select Apply

eVision

Select Back The Diagnostic Test selection screen appears

Select All Ethernet Tests or Ethernet Cable from the test type drop down menu

Select Diagnose After a few moments the test result screen will display. The segment location should be highlighted in the Cable Benchmark Summary.




TM


End of Procedure

eVision

Select Next

Select Restore





TM

3.7.5 Etherjack® Connection Performance AnalyzerThe Etherjack® Connection Performance Analyzer (ECPA) provides a subset of Ethernet test equipment functions embedded directly into the port cards so that each individual LAN port can act as its own “test equipment”. This provides a means to test EVC connectivity and verify service conformance from a remote location without the need for external test equipment.

Refer to the following procedures to initiate an Etherjack® Connection Performance Analyzer (ECPA) routine on a LAN facility:

• Run Untagged ECPA Test on a LAN Facility

• Run VLAN ECPA Test on a LAN Facility

Entering a right click on the System Name in the menu tree and selecting Edit ECPA Streams allows you to edit ECPA test stream details prior to advancing through the ECPA test process. See Figure 3-24.

Figure 3-24 Edit ECPA Test Streams Window




TM

ECPA setup and execution options are available by entering a right click on the System Name and selecting Analyze ECPA. An ECPA test setup window walks you though the steps for selecting ECPA setup and execution options, and performing ECPA diagnostics. You can place a facility in the testing state, select the desired tests to perform, execute diagnostics, view test results, and restore the facility from this window. See Figure 3-25 for the ECPA test setup window provided after the facility has been placed in the testing state.

The desired ECPA stream, Injector direction, Monitor direction and test length are also selected and edited from this window.

Figure 3-25 ECPA Test Setup Window (Flow VLAN)



TM

The next step in the ECPA Test Process is running the test, which is invoked by selecting the Run button from the ECPA test setup window. The ECPA test results window will appear, displaying the current ECPA test status and results. If multiple test streams are run, scroll down to review each ECPA test stream. The screen will refresh itself every few seconds if the Auto Refresh box is selected. If the Auto Refresh box is deselected, an update of the test results can be displayed by selecting the Refresh button located at the bottom of the screen. (Scrolling down may be required.) The test can be cancelled by selecting the Cancel button, also located at the bottom of the screen.

The first ECPA test frame can be viewed by selecting the ECPA First Frame button located at the top of the ECPA view. See Figure 3-26 for the location of the ECPA First Frame button. See Figure 3-27 for an example of ECPA First Frame results.

Figure 3-26 ECPA Test Results Window




TM

The ECPA First Frame window provides first frame result details, including frame header, packet details and raw frame content for each ECPA test stream. If more than one ECPA test stream was run, use the tabs to view the ECPA First Frame for the desired ECPA test stream. To toggle back to the ECPA Test Results window, select the ECPA Results button located at the top of the ECPA First Frame results view. See Figure 3-27.

Figure 3-27 ECPA First Frame from ECPA Results Window



TM

The first ECPA test frame can also be viewed by selecting the LAN facility in the Menu Tree and then selecting the ECPA First Frame tab. As in the previous window, if more than one ECPA test stream was run, tabs are provided for each ECPA First Frame. See Figure 3-28.

Figure 3-28 ECPA First Frame Window from Menu Tree




TM

Run Untagged ECPA Test on a LAN Facility

WARNING — Running an Untagged ECPA test on a LAN facility is a Service Affecting procedure. If customer traffic is present, ensure that the following procedure is performed during a scheduled Maintenance Window. Creating a VLAN loopback and running a VLAN ECPA test is not Service Affecting, as long as the test rate does not exceed the available bandwidth for customer traffic, and as long as the customer is not using the same VLAN.

Procedure

Step 1 Create a remote loopback at the far end of the facility to be tested or create a local loopback if internal testing is desired.

Step 2 Edit the ECPA stream.

eVision


Right click on the System Name in the menu tree

Select Edit ECPA Streams An Edit Streams window appears

Select ECPA Stream-1

Select Yes for Include in Test

Enter the desired Rate

Select the desired bit rate entry desired for Rate (in bps, kbps, Mbps, etc.)

Select the desired IP version

If required, enter the Destination MAC address

Select the desired Payload Type

Enter the desired Frame Size

Select the Frame Type UNTAGGED

Enter the desired Priority value

Select OK The E100 maintenance status window appears

Select the ECPA Streams tab to verify ECPA Stream entry



TM

Step 3 Remove the LAN facility on the FSP 150CCf-825.

Step 4 Perform the ECPA test.


eVision


Select Analyze ECPA An ECPA Status window appears

Select the desired Port ID to test and select Next

Select Remove

Verify the Administrative State of the LAN facility is in the Testing state The LAN Administrative State changes to the Testing state

eVision

Select Next An ECPA Tests window appears

Select the desired Injector and Monitor points

Select a test duration type, and if using Frames or Seconds, Enter a Test Length

Select Run ECPA Test Status window is displayed

Observe the test status.

Select Stop when desired, or wait until the test has completed

View completed ECPA test results

Select Next

eVision

Select Restore






TM

Step 6 Review the ECPA test results.

Step 7 If desired, retrieve the first frame received.

Step 8 Remove the local or remote loopback.

End of Procedure

eVision

Select the ECPA Test tab The ECPA test data is displayed

eVision

Select the ECPA First Frame tab The ECPA first frame received data is displayed



TM

Run VLAN ECPA Test on a LAN Facility

Procedure

Step 1 Create a remote loopback at the far end of the facility to be tested or create a local loopback if internal testing is desired.

Step 2 For Flow VLAN facility, create the appropriate VLAN member(s) that will be used when creating ECPA test streams in the next step. (Defaults are: ECPA Stream 1 is 4094-0 [Include in Test=Yes], ECPA Stream 2 is 4094-1 [Include in Test=No] and ECPA Stream 3 is 4094-2 [Include in Test=No].)

Step 3 Edit an ECPA stream. Repeat for each stream, as required.

Note 1: For Transparent LAN facility, only one ECPA stream is allowed.

eVision



Select Edit ECPA Streams An Edit Streams window appears

Select the desired ECPA Stream (See Note 1)

Select to include in test or not

Select the desired bit rate entry desired for Rate (in bps, kbps, Mbps, etc.) and enter the desired Rate (See Note 2)

Select the desired IP version

If required, enter the Destination MAC address (See Note 3)

Select the desired Payload Type

Enter the desired Frame Size

Select Frame Type VLAN

Enter the VLAN ID and select the desired Priority Map Mode

Enter the desired VLAN Priority and Priority values

Select Apply

Repeat for each desired stream

Select OK The LAN maintenance status window appears

Select the ECPA Streams tab to verify ECPA Stream entry




TM

Note 2: The rate should not exceed the facility/path rate, including overhead bytes.

Note 3: The destination MAC address needs to be specified if the packets may be traversing a network that has many switches, or if the configuration uses a MAC-enabled management tunnel. In order to ensure that the packet reaches the proper destination, the destination MAC address must be supplied here, and destination/source address swapping must be requested as part of the loopback at the other end.

Step 4 Remove the LAN facility.

Step 5 Perform the ECPA test.

eVision


Select Analyze ECPA An ECPA Status window appears

Select the desired Port ID to test and select Next

Select Remove

Verify the Administrative State of the LAN facility is in the Testing state The LAN Administrative State changes to the Testing state

eVision

Select Next An ECPA Tests window appears

Select the desired ECPA Stream(s): select Yes or No for each available ECPA Stream

Select the desired Injector and Monitor points

Select a test duration type, and if using Frames or Seconds, Enter a Test Length

Select Run ECPA Test Status window is displayed

Observe the test status.

Select Stop when desired, or wait until the test has completed

View completed ECPA test results

Select Next



TM


Step 7 Review the ECPA test results.

Step 8 If desired, retrieve the first frame received.

Step 9 Remove the local or remote loopback.

End of Procedure

eVision

Select Restore



eVision

Select the ECPA Test tab The ECPA test data is displayed

eVision

Select the ECPA First Frame tab The ECPA first frame received data is displayed




TM

3.8 Performance MonitoringPerformance Monitoring (PM) view allows you to view performance monitoring counts in tabular or chart format. Performance monitoring thresholds can be edited or displayed, and registers can be initialized (for users with proper user access permission level).

Performance Monitoring OptionsWhen entering a right click on an entity folder or file from the Menu Tree, Performance Monitoring options become available in menu form. The following functions are available from the Menu Tree menu:

• Selecting and Viewing PM Counts

• Editing PM Thresholds

• Initializing PM Registers

PM Counts can be viewed for RADIUS Servers as well as WAN, LAN and flow entities. To view RADIUS Server counts, expand the Administration entity in the Menu Tree and select the RADIUS entity (see Figure 3-29). Refer to the following procedure (on the next page) to view PM counts for WAN, LAN and flow entities. RADIUS PM registers may also be initialized.

Note: RADIUS PM counts are only applicable where Remote Authentication Protocol is set to RADIUS.

Figure 3-29 Viewing RADIUS Counts in Performance Monitoring View



TM

3.8.1 Selecting and Viewing PM CountsRefer to the following procedures for viewing the following PM Counts:

• Selecting and Viewing WAN and LAN Port PM Counts

• Selecting and Viewing Queue PM Counts (VLAN)

• Selecting and Viewing Flow PM Counts

Selecting and Viewing WAN and LAN Port PM Counts

Procedure

Step 1 Select the Performance Monitoring icon or select Performance from the Applications menu, then expand the menu tree.

Step 2 Enter a right click on the WAN or Transparent LAN entity, select Retrieve Counts (WAN) or Retrieve Port-Counts (LAN). An Retrieve PM Counts window appears in the view area (see Figure 3-30)

Step 3 Select the Charts box if charts are desired, and select the desired PM Period, where applicable.

Step 4 Select the desired count group box(es) that the desired counts reside. Individual counts are displayed in the picker window

Step 5 Select the desired counts by selecting the first desired count and then entering a Control+click to select other counts. To select a contiguous set of counts, select the first desired count, then enter a Shift+click on the last desired count in the range of counts. To deselect a specific count, enter a Control+click on the count to remove it from the list.

Step 6 Select OK. The selected counts will be displayed in the view area (see Figure 3-31 for an example in tabular format and see Figure 3-32 for an example in chart format)

Step 7 Select the Counts tab (WAN) or P-Counts tab (Transparent LAN) and then the Summary tab. If required, use the scroll bars to view the summary counts. If Chart report type was selected, a tab will be present for each count in chart form. Select the desired count tab to view its count in chart form.

Note: Counts can be refreshed by selecting the tab associated with the count you are viewing (either the Summary tab, or individual count tab when viewing charts).

End of Procedure




TM

Selecting and Viewing Queue PM Counts (VLAN)

Procedure


Step 2 Enter a right click on the VLAN Port entity, select Retrieve Q-Counts. A Retrieve PM Counts window appears in the view area

Step 3 Select the desired period.

Step 4 Select the desired counts by selecting the first desired count and then entering a Control+click to select other counts. To select a contiguous set of counts, select the first desired count, then enter a Shift+click on the last desired count in the range of counts. To deselect a specific count, enter a Control+click on the count to remove it from the list.

Step 5 Select OK. The selected counts will be displayed in the view area (see example in Figure 3-31)

Step 6 Select the Counts tab and the desired Egress Q tab. If required, use the scroll bars to view the counts.

Note: Counts can be refreshed by selecting the Egress Q tab associated with the count you are viewing.

End of Procedure

Selecting and Viewing Flow PM Counts

Procedure


Step 2 Enter a right click on the Flow entity, select Retrieve P/Q Counts. A Retrieve PM Counts window appears in the view area

Step 3 Select the desired period.



TM

Step 4 Select the desired Ingress Policer counts by selecting the first desired count and then entering a Control+click to select other counts. To select a contiguous set of counts, select the first desired count, then enter a Shift+click on the last desired count in the range of counts. To deselect a specific count, enter a Control+click on the count to remove it from the list.

Step 5 Select the desired Ingress Policer(s).

Step 6 Repeat Step 4 and Step 5 for the desired Egress Policer counts, as required.

Step 7 Select OK. The selected count tabs will be displayed in the view area

Step 8 Select the Counts tab and the desired PM tab. If required, use the scroll bars to view the counts.

Note: Counts can be refreshed by selecting the PM tab associated with the count you are viewing.

End of Procedure

Figure 3-30 Selecting Port Counts in Performance Monitoring View




TM

Figure 3-31 Performance Monitoring View with Port Counts in Tabular Format

Figure 3-32 Performance Monitoring View with Port Counts in Chart Format



TM

3.8.2 Editing PM ThresholdsRefer to the following procedures for editing the following PM Thresholds:

• Editing WAN and LAN Port PM Thresholds• Editing Queue PM Thresholds (VLAN)• Editing Flow PM Thresholds

Editing WAN and LAN Port PM Thresholds

Procedure


Step 2 Enter a right click on the WAN or Transparent LAN entity, select Edit Thresholds (WAN) or Edit Port-Thresholds (LAN). An Edit Threshold window appears in the view area (see Figure 3-30)

Step 3 Select the desired count group box(es) that the desired count(s) reside. Individual counts are displayed in the picker window

Step 4 Select the desired count in the picker window and the desired PM Period. The current Threshold level displays

Step 5 Enter the desired threshold level, and then select OK.

End of Procedure

Editing Queue PM Thresholds (VLAN)

Procedure


Step 2 Enter a right click on the VLAN Port entity, select Edit Q-Thresholds. An Edit Threshold window appears in the view area

Step 3 Select the desired Queue Number, Monitor Name, and PM Period. The current Threshold level displays


End of Procedure




TM

Editing Flow PM Thresholds

Procedure


Step 2 Enter a right click on the Flow entity and select Edit Thresholds. An Edit Threshold window appears in the view area

Step 3 Select the desired PM Type and Policer/Queue, if applicable, then select Next.

Step 4 Select the desired monitor name, and PM Period. The current Threshold level displays


End of Procedure

Figure 3-33 Edit Port PM Threshold Window



TM

3.8.3 Initializing PM RegistersFor WAN, LAN, flow and ESA Probe entities, PM data is maintained in individual monitored parameter bins for each interval. The system maintains bins for the following time periods:

• Current 15-minute bin

• Current 24-hour (1-day) bin

For WAN, LAN and flow PM registers, current intervals are indicated by index=0, and older periods are assigned sequentially higher numbers The index allows a user to identify the current (INDEX=0), previous (INDEX=1) or one of the historical bins (INDEX = 2 to 32), with 32 being the oldest bin.

For ESA Probe registers, each bin is indicated by a 24-hour clock time (e.g., 15:30). For RADIUS registers, only a total count is stored for each PM register.

PM registers can be initialized by entering a right click on the entity in the Menu Tree and selecting the available/desired Initialize Registers option. An Initialize PM Registers selection window appears in the view area (refer to Figure 3-34).

To initialize WAN, LAN Port, ESA Probe PM registers: Enter a right click on the entity in the Menu Tree and select Init Port-Registers (LAN Port) or Initialize Registers (WAN). Select the desired Period and Bin, and then select OK.

To initialize Queue PM registers (VLAN): Enter a right click on the entity in the Menu Tree and select Init Q-Registers. Select the desired Period, Queue Number and Bin, and then select OK.

To initialize flow PM registers: Select the desired register Type and Policer / Queue, where applicable, and then select Next. Select the desired Period and Bin, and then select OK.

To initialize RADIUS Server PM registers: Select the desired RADIUS Server, and then select OK. Only one register selection may be initialized at a time (ALL or an individual register).




TM

Figure 3-34 Initialize PM Registers Window



TM

3.9 Scheduled PingSchedule Activities view allows you to perform a scheduled ping. The scheduled ping feature provides a current state of management link connectivity (for users with proper user access permission level).

Scheduled Ping is invoked by selecting the Schedule Activities icon on the Tool Bar or selecting Schedule Activities from the Applications menu, expanding the system folder in the Menu Tree, entering a right click on Scheduled Ping and selecting Edit Settings. Up to four IP addresses can be provisioned to automatically ping periodically. If a communications failure is detected, an alarm (Scheduled Ping Failed alarm) may be raised against the IP address.

Scheduled ping can be enabled or disabled for each provisioned IP address, as well as the frequency of the ping, the alarm severity level raised if there is no response, and a response threshold. The response threshold indicates the number of consecutive attempts to make on a failed response before an alarm may be raised against that IP address. Refer to Figure 3-35 for an example of an edit Scheduled Ping window. For provisioning details regarding Scheduled Ping, see Section 5.11 Scheduled Ping and ESA Activity Settings, on Page 5-76.

Figure 3-35 Edit Scheduled Ping Window




TM

Once the scheduled ping has been provisioned, the Scheduled Ping status window will display the current status of each IP address scheduled ping attempt. The Scheduled Ping status window may be accessed at any time by selecting the Schedule Activities icon on the Tool Bar or selecting Schedule Activities from the Applications menu, expanding the system folder in the Menu Tree, and then selecting Scheduled Ping. Refer to Figure 3-36 for an example of a Scheduled Ping status window.

3.10 Etherjack® Service Assurance The Etherjack Service Assurance (ESA) feature is a real-time monitoring tool to allow Ethernet services to be subjectively measured for the basis of Service Level Agreements (SLA). (For a detailed description of ESA operation, see Chapter 2, Etherjack Service Assurance.)

Figure 3-36 Scheduled Ping Status Window



TM

3.11 Connectivity Fault ManagementConnectivity Fault Management (CFM) is an emerging standard aimed at enhancing Ethernet Service OAM capabilities. The main features provided by CFM include the ability to detect, verify, isolate and report connectivity faults on a service instance. CFM features include the ability to:

• Configure Maintenance Domains (MDs)

• Configure Maintenance Associations (MAs)

• Configure and manage Maintenance End Points (MEPs)

• Transmit and receive Continuity Check Messages (CCMs)

• Initiate Loop Back Messages or Link Trace Messages

• Detect and raise CFM-related alarms

Connectivity Fault Management Provisioning and OperationThe following procedure describes the CFM feature provisioning and operation process for each node.

Procedure

Step 1 Determine the CFM node locations to be provisioned, including their MAC addresses and other associated options. Common elements for each end point include Primary VLAN IDs, Maintenance End Point IDs and Continuity Check Message interval.

Step 2 Edit the CFM System Level Parameters.

eVision

Select CFM from the Applications menu

Expand the System and Administration entities in the menu tree

Right click on the System entity in the menu tree

Select Edit CFM An Edit CFM System Level Parameters screen appears

Enter the desired Ethertype and Multicast MAC Address

Enter the desired CFM Service and WAN-1 / WAN-2 CFM Port CIR, EIR, Buffer Size, CBS and EBS parameters

Select OK




TM

Step 3 Create a Maintenance Domain (MD).

Note: If Format Type String or DNS Name is selected, allowed characters are: a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not allowed. If Format Type MAC-Integer is selected, the entry must be Hexadecimal characters.

Step 4 Expand the Maintenance Domain entity in the menu tree. The new Maintenance Domain ID is present in the menu tree

Step 5 Select the new Maintenance Domain ID and verify the entry.


eVision

Right click on the Maintenance Domain entity in the menu tree

Select Create A Maintenance Domain creation screen displays

Select the desired MD ID and name Format Type

If String, MAC Integer or DNS Name was selected for Format Type: Enter the MD Name contents (See Note)

Select the desired Level

Select the desired MIP Creation Control

Select OK

Current Status Then

Are MIP Creation Control changes required to the MD?

Enter a right click on the MD ID and select Edit. Enter the desired changes and select OK.

Are changes other than MIP Creation Control required to the MD?

Enter a right click on the MD ID and select Delete and then select OK. Then go to Step 3 and re-enter the appropriate MD ID options.



TM

Step 7 Create a Maintenance Association (MA).

Note: If Format Type String or DNS Name is selected, allowed characters are: a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not allowed. If Format Type MAC-Integer is selected, the entry must be Hexadecimal characters.

eVision

Right click on a Maintenance Domain ID in the menu tree

Select Create MA A Maintenance Association creation screen displays (see Figure 3-37)

Select the desired MA ID

Select the desired name Format Type

Enter the MA Name contents (See Note)

Select the desired CCM Interval

Select the desired MIP Creation Control type

Enter the Primary VID (VLAN Identifier)

Enter the Maintenance Association MEP list by entering the first ID number and select Add. Enter additional ID members and select Add, as required. To delete an ID member, select the ID member to be removed, and then select Remove. (The last VID member cannot be removed.)

Select OK




TM

Step 8 Expand the Maintenance Domain ID in the menu tree. The new Maintenance Association ID is present in the menu tree

Step 9 Select the new Maintenance Association ID and verify the entry.


Figure 3-37 Create Maintenance Association Window

Current Status Then

Are changes to the CCM Interval, MIP Creation Control or MEP List required to the MA?

Enter a right click on the MA ID and select Edit. Enter the desired changes and select OK.

Are MA ID, Format Type, Name or Primary VID changes required to the MA?

Enter a right click on the MA ID and select Delete and then select OK. Then go to Step 7 and re-enter the appropriate MA ID options.



TM

Step 11 If additional MA IDs are required for the same Maintenance Domain ID, repeat Step 7 through Step 10.

Step 12 Create the Maintenance End Point (MEP) for a Maintenance Association.

Note: For LAN ports, only the Up direction is supported.

Step 13 Expand the associated Maintenance End Point entity interface in the menu tree. The new MEP is present in the menu tree

Step 14 Select the new MEP and verify the entry.


Note: For LAN ports, only the Up direction is supported.

Step 16 If additional MEPs are required for another Maintenance Association ID, repeat Step 12 through Step 15.

Step 17 If additional Maintenance Domains, and their associated MD IDs and MEPs are required, repeat Step 2 through Step 16.

Step 18 Select one of the MEP IDs and select the Alarm Attributes tab. Determine if Notification Code changes are required. If Alarm notification code changes are required, enter a right click on a MEP ID and select Edit Alarm Attributes, select the desired Notification Code(s) and then select OK. Repeat for each MEP. Otherwise,

eVision

Expand the Maintenance End Point entity in the menu tree

Right click on the associated MEP interface in the menu tree

Select Create A Maintenance End Point Identification creation screen displays

Select the desired MA ID and then MEP ID

Select the desired MEP Direction (See Note)

Select the desired State and Continuity Check Message (CCM) options

Select the desired Fault Alarm Priority

Select the desired Primary VID (Primary VLAN ID)

Select OK

Current Status Then

Are changes other than MEP Direction required to the MEP?

Enter a right click on the MEP and select Edit. Select the desired changes and select OK.

Are MEP Direction changes required to the MEP? (See Note)

Enter a right click on the MEP and select Delete and then select OK. Then go to Step 12 and re-enter the appropriate MA ID options.




TM

continue to the next step.

Step 19 Repeat Step 2 through Step 18 for each node to be set up for Connectivity Fault Management.


Step 21 Initiate a Loop Back Message (LBM) or Link Trace Message (LTM).

Step 22 Select the MEP Configuration tab at the first node and verify the status (see Figure 3-38). For LTM, enter a right click on the MEP ID and select View LTR DB to view the Link Trace Reply database. Troubleshoot and edit any issues, as required.

End of Procedure

Current Status Then

Do you wish to initiate a Loop Back Message (LBM) or Link Trace Message (LBM)?


Is no further action required at this time? End of Procedure

eVision

Expand the Maintenance End Point entity in the menu tree

Right click on the associated MEP interface in the menu tree

Select Initiate LBM or Initiate LTM An Initiate Loop Back Message or Link Trace Message screen displays

Select the desired Destination Type and select/enter the desired Destination ID

Select/enter other options as desired

Select OK



TM

Figure 3-38 Maintenance End Point Status Window




TM

3.12 Users and Security

User Access Security LevelsA hierarchy of security levels provide user accessibility to the functions and features appropriate to their job function. Selecting a given security level will allow specific operations necessary to accomplish the user’s task, and will restrict access to specific commands and menu selections outside of their job function. The Superuser assigns security levels for each user and each FSP 150CCf-825. The security levels are:

If a user attempts to access functions that are not allowed at the current security access level, the error message “Access Denied. Your privilege level does not allow you access to this page!” will display.

GUI Login Time-outEach user is assigned a GUI login time-out that will automatically logout the user after a defined set of time. Valid entries are 0 to 99 (minutes), where 0 disables GUI login time-out. Default setting is 30 (minutes). When a user GUI login time-out expires the user is logged out and is directed to the Authentication Failed screen. Selecting here will direct the user to the initial login screen (see Logging Onto the FSP 150CCf-825, on Page 3-4).

User Access Security Level

Name Allowed Operations

1 Retrieve All retrieve commands

2 Maintenance Retrieve and control commands, such as diagnostics, protection switching, loopbacks and initializing registers

3 Provisioning Retrieve, control and provisioning commands

4 Super User All above security level operations, and manage users



TM

Viewing All UsersWhen selecting the Configuration View and opening the Users folder, the Users view displays all users, their current status and parameter settings. Refer to Figure 3-39 for an example of a Users view when logged in as a Superuser. (When logged in as a security level other than a Superuser, only self can be viewed and only self password can be modified.) All users can be viewed by selecting Configuration view, expanding the Administration tree, and selecting Users.

Viewing Single User DetailsIndividual user details can be viewed by selecting Configuration view, expanding the Administration tree, expanding the Users tree, and selecting the desired User ID.

Figure 3-39 Users View Showing All Users




TM

Creating a New UserThis procedure describes how to create a new User ID. Security level required: Superuser.

Procedure

Step 1 Select Configuration view and expand the Administration tree.

Step 2 Right click on Users and select Create New User. A Create New User window displays in the view area

Step 3 Complete the following fields:

• User ID - The User ID (UID) is a unique, non confidential name to identify each authorized NE user. Enter a new user name, which contains 6 to 10 alphanumeric characters. Special characters * # % are allowed. Spaces are not allowed.

• Password - Enter the user Password ID (PID), which contains between 6 and 10 characters. The PID must contain at least two non-alpha characters and one special character. Special characters include *, # and %. Spaces are not allowed.

• Confirm Password - Re-enter the Password ID.

• Privilege - Select the desired user access security level. Default is Retrieve.

• GUI Login Timeout Value - Enter a time-out value of 0 (to disable logout) to 99 (minutes). Default is 30 (minutes).

• Comment - Enter a comment, if desired.

Step 4 Select OK. The new User information is displayed in the Users view

Step 5 Expand the Users tree. The new user is listed

Step 6 Select the new User name and view the new user information to verify new user entry. (The new user password is not displayed for security reasons. The new user will need to attempt a login in order to verify the password entry.)

End of Procedure



TM

Editing a UserThis procedure describes how to edit a user GUI time-out value, privilege level or comment field. Security level required: Superuser.

Procedure


Step 2 Expand the Users tree.

Step 3 Right click on the User to be edited and select Edit User. An Edit User Profile window displays in the view area

Step 4 Enter the new user time-out value of 0 (to disable logout) to 99 (minutes), if desired. Default is 30 (minutes).

Step 5 Select the desired privilege level and enter a comment, if desired.

Step 6 Select OK. The User Profile window displays the changes made

End of Procedure

Editing a User ID and PasswordThis procedure describes how to modify a user ID and password. Security level required: Superuser.

Procedure



Step 3 Right click on the User name be edited and select Edit Password. An Edit Password window displays in the view area

Step 4 Enter the User ID changes, if required. The user name must contain 6 to 10 alphanumeric characters. Special characters * # % are allowed. Spaces are not allowed.




TM

Step 5 Enter the current password.

Step 6 Enter the new password and confirm the new password. The password must range between 6 and 10 characters. The password must contain at least two non-alpha characters and one special character. Special characters include *, # and %. Spaces are not allowed.

Step 7 Select OK.

Step 8 Verify the new password by logging in as that user.

End of Procedure

Editing Your Own PasswordThis procedure describes how to modify your own password. All security levels have the ability of changing their own password.

Procedure



Step 3 Right click on your User name and select Edit Password. An Edit Password window displays in the view area

Step 4 Enter your current password.

Step 5 Enter your new password and confirm the new password. The password must range between 6 and 10 characters. The password must contain at least two non-alpha characters and one special character. Special characters include *, # and %. Spaces are not allowed.

Step 6 Select OK. A new Login window appears

Step 7 Enter your user name and new password to log onto the system.

End of Procedure



TM

Deleting a UserThis procedure describes how to delete a user. Security level required: Superuser.

Procedure



Step 3 Right click on the User to be deleted and select Delete User.

Step 4 Select Delete. The user ID should no longer be present

End of Procedure

3.13 Provisioning Remote AuthenticationThe FSP 150CC supports remote authentication using either RADIUS or TACACS+. The following procedure uses eVision to provision the NID for either authentication system. It is assumed that if provisioning for remote authentication is desired that the user is familiar with the authentication system used and the settings required. The FSP 150CC automatically sets the port number, time out, retries and priority settings specified in the standards. The user can edit these for non-standard applications and the user must input IP addresses, select the authentication protocol (PAP or CHAP), secrets, and enable each server access.

Note 1: TACACS+ is a proprietary enhancement to the original TACACS protocol and is not backward compatible to TACACS.

Note 2: The FSP 150CC must always have at least one superuser locally defined. The NID will always use the local database of defined users before accessing remote authentication.

Procedure

Step 1 Logon to the FSP 150CC using Section 3.2 Logging Onto the FSP 150CCf-825, on Page 3-4 and using a UID/PID with provisioning level access.

Step 2 Click on the Configuration icon.




TM

Step 3 In the tree view, expand the display.

Step 4 Expand the Administration tree.

Step 5 Right click on Remote Authentication and select Edit Remote Authentication.The Edit Remote Authentication window appears

Step 6 Select the desired Authentication Protocol; either RADIUS or TACACS+.

Step 7 Select the desired Authentication Type; either PAP (Password Authentication Protocol) or CHAP (Challenge Handshake Authentication Protocol).


Current Status Then

Is the selected protocol TACACS+? Go to Step 10.

Is the selected protocol RADIUS? Continue with the next step.



TM

Step 9 Enter the Network Access Server (NAS) IP Address.

Step 10 Check the following entries for each Remote Authentication Server (1 through 3), and change whatever does not use the default values in your application.

Note: The Priority setting defaults to First for Server 1, Second for Server 2 and Third for Server 3. You may change the priority for any server, but should never have more than one first priority server.

Step 11 For each Remote Authentication Server (1, 2 and 3), select which ones to enable by clicking on the Enable box for that server.

Step 12 For each Remote Authentication Server (1, 2 and 3), enter an IP Address for the server(s) that are enabled.

Step 13 For each Remote Authentication Server (1, 2 and 3), enter a Secret for the server(s) that are enabled.

Step 14 Click on OK to enter the Remote Authentication information.

Note: To test the Remote Authentication settings, logout of the FSP 150CC and then attempt to log in using a UID/Password combination that is registered on the Remote Authentication system, but is not a local UID/Password on the FSP 150CC. Additionally, the user can verify that each Remote Authentication Server is functional by disabling all but one, testing the remote logon facility, then changing the enabled server until each has been verified to work. If problems are encountered with Remote Authentication, first verify that all the settings on the FSP 150CC are correct. Edit any information found to be in error, and retest. If the data on the NID is correct and problems still exist, contact the administrator of the Remote Authentication system.

End of Procedure

Server Item RADIUS

Default Value

TACACS+

Default Value

Port 1812 49

Timeout 3 NA

Retries 3 3

Priority (1, 2, 3) First, Second, Third First, Second, Third




TM

3.14 Software UpgradeThe FSP 150CCf-825 Web Browser Management Tool provides an application to update software to the current release level. The latest FSP 150CCf-825 software load is originally provided on a CD-ROM, although your company may choose to store the current software on a remote server. The software upgrade process may be performed via eVision Web Browser by transferring the update file via Web Browser or FTP.

CAUTION — If a database (configuration) file other than the current active database on the unit is desired or specified as part of an upgrade, it should be loaded to the standby partition prior to beginning the software upgrade using the Database Restore procedure. (Database Restore, on Page 3-115)

Minimum System Requirements for Software UpgradeThe software upgrade procedure is accomplished by using the FSP 150CCf-825 web browser. Prior to running the web browser, verify that your PC meets the following minimum system requirements:

• 200Mhz processor

• Supported OS versions: Windows 98/2000/XP


• 128 MB of RAM

• Adobe Acrobat Reader 5.0 or greater (Reader 6.0 is included)

• Recommended display: 1024 x 768 with 16+ color bits

CAUTION — For GNE/SNE configurations, perform the upgrade on the SNE first, and perform the upgrade on the GNE last. This will prevent loss of communication during the upgrade process. Both FSP 150CCf-825s in a GNE/SNE configuration must be set to the same software version in order for some features to work correctly.

Procedure

Step 1 Copy the latest FSP 150CCf-825 software version from the CD-ROM onto your PC desktop or obtain the path to the file location on an FTP server. The file name will be of type “ccxxx_nnnnn.img”, where xxx is the FSP 150CC variant type and nnnnn is the software release number.

Step 2 Select Applications then Maintenance from the menu bar.



TM

Step 3 Expand nested items in the System Name and Administration entities in the menu tree by selecting the “+” next to each entity, and select Software. The Software Status window appears

Step 4 Observe the current Active and Standby Partition software versions and current partition in use.

Step 5 Right-click on the Software entity and select Software Copy. The Software Copy window appears




TM


Step 7 Select File Transfer Method of Web Browser.

Step 8 Enter the path to the “ccxxx_nnnnn.img” file (from the PC root directory) into the New Software Image entry window, or browse to the file location.


Step 10 Select File Transfer Method of FTP.

Step 11 Enter the server IP address.

Step 12 Enter a valid user ID and password.

Step 13 Enter the path to the “ccxxx_nnnnn.img” file (from the server root directory).

Step 14 Select OK. After a few seconds the Writing to Flash status screen appears The software will copy to the FSP 150CCf-825. Do not interrupt the software file transfer while it is in progress. After a few seconds a progress graph will appear, indicating the software file transfer is in progress. It may take several minutes to complete the file transfer.

Current Status Then

Do you wish to perform the software upgrade via FTP?

Go to Step 10.

Do you wish to perform the software upgrade via web browser?




TM

Step 15 When the software copy is completed, a message will appear, indicating the software has successfully been written to the standby partition:

Step 16 Select OK. Current status indicates the Standby Partition contains the new software version




TM

Step 17 Right-click on the Software entity in the menu tree and select Software Upgrade. The Software Upgrade window appears

Step 18 Select the desired Schedule Reboot option of Now or Time. If Time is selected, enter the desired date and time to schedule the reboot.

Step 19 Select the desired Validation Timer option of Enabled or Disabled. If Enabled is selected, enter the appropriate time (in hours and minutes) that will allow enough time to validate the software upgrade, and to cancel the validation timer (revert back to the previous software version), if required.

Step 20 Select the desired Preserve Standby Database option (Yes or No). No is the default and should be used except in special circumstances. This option means that the current active database configuration will be used with the new software load and after the upgrade is complete, the same database configuration will be on both the active and standby partitions. Yes means that the database file on the standby partition will be used by the new software build. This should not be done unless a custom or special database file was provided or specified for use with the new software load and has already been loaded to the standby partition using the Database Restore procedure (Database Restore, on Page 3-115).

WARNING — A reboot will cause the FSP 150CCf-825 to drop all traffic. Adhere to local practices when performing a reboot. Local practices may require you to ensure that the reboot will be performed during a scheduled maintenance window.

WARNING — Do not remove power while performing the next steps. Removing power while the operation is in progress will corrupt the software update operation.



TM


Step 22 Click OK. If a Scheduled Reboot time was entered, the Scheduled Upgrade Reboot Time will display at the top of the screen


Current Status Then

Was the Scheduled Reboot option Now selected? Go to Step 30.

Was a Scheduled Reboot time entered? Continue with the next step.

Current Status Then

Do you wish to continue the scheduled reboot? Go to Step 29.

Do you wish to cancel the scheduled reboot or reboot now?


Scheduled RebootTime Indicator




TM

Step 24 Right-click on the Software entity and select Software Upgrade. The Software Upgrade window appears


Step 26 Select Reboot Now. If Reboot Now was selected, a status window appears, indicating the system is restarting

Note: If the software upgrade process fails due to data corruption or power loss, “Rescue Image” will be booted, providing a means to communicate with the FSP 150CCf-825 even when the software data has been corrupted, and therefore, will allow you to restart the software upgrade or revert back to a previous software release. See Rescue Image, on Page 3-119.

Current Status Then

Do you wish to cancel the scheduled reboot? Go to Step 28.

Do you wish to reboot now? Continue with the next step.



TM

Step 27 Wait until the reboot completes. Communications will be lost while the reboot is in progress. Wait a few minutes, refresh the web browser, then go to Step 31.

Step 28 Select Cancel Reboot. The Software Upgrade Reboot Timer indicator (at the top of the screen) clears

End of Procedure

Step 29 Wait until the Scheduled Upgrade Reboot Timer has expired. Communications will be lost while the reboot is in progress. Wait a few minutes, refresh the web browser, then go to Step 31.

Step 30 Click OK. If a Scheduled Reboot of Now was selected, a status window appears, indicating the system is restarting

Note: If the software upgrade process fails due to data corruption or power loss, “Rescue Image” will be booted, providing a means to communicate with the FSP 150CCf-825 even when the software data has been corrupted, and therefore, will allow you to restart the software upgrade or revert back to a previous software release. See Rescue Image, on Page 3-119.




TM

Step 31 Upon reboot completion, an authentication failure screen appears (due to user logoff during the reboot process):

Step 32 Select here to continue. The FSP 150CC login window appears




TM



Step 36 Select Continue. The eVision Web Browser Management Tool will display

Note: If the authentication failure screen re-appears and you have entered the correct user name and password, the web browser cache may need to be cleared. This is accomplished by deleting cookies and temporary internet files from the web browser application, closing the web browser, opening a new web browser window and then logging back onto the FSP 150CCf-825.


Step 38 Expand nested items in the System Name and Administration entities in the menu tree by selecting the “+” next to each entity.

Current Status Then

Was the Software Validation Timer Enabled? Go to Step 40.

Was the Software Validation Timer Disabled? Continue with the next step.




TM

Step 39 Select the Software entity. If Software Validation Timer was Disabled, the Software Status Window indicates the Active Partition (containing the software update) is currently in use

End of Procedure

Step 40 Select Continue. The eVision Web Browser Management Tool will display. If the Software Validation Timer was enabled, the amount of time remaining before time-out will display at the top of the screen

ValidationTimerIndicator



TM

Note: If the authentication failure screen re-appears and you have entered the correct user name and password, the web browser cache may need to be cleared. This is accomplished by deleting cookies and temporary internet files from the web browser application, closing the web browser, opening a new web browser window and then logging back onto the FSP 150CCf-825.



Step 43 Select the Software entity. If Software Validation Timer was Enabled, the Software Status Window indicates the Standby Partition (containing the software update) is currently in use and the software has not been validated

Step 44 Validate the software load prior to the validation timer expiration time.


Current Status Then

Do you wish to commit the software update? Go to Step 57.

Do you wish to revert back to the original software load?





TM


Step 47 If communications is lost or you wish to revert back to the previous software update when the Software Validation Timer expires, then do nothing. Wait until the Software Validation Timer has expired. When the time-out period expires, the system will evert back to the previous software version and a system reboot will occur. Communications will be lost while the reboot is in progress. Wait a few minutes, refresh the web browser, then log back onto the system.



Step 50 Select the Software entity. The Software Status Window indicates the Active Partition (containing the original software load) is currently active

End of Procedure

Current Status Then

Has communications been lost, and/or you wish to revert back to the original software load when the Software Validation Timer expires?


Is communications possible and you wish to revert back to the original software load prior to expiration of the Software Validation Timer?

Go to Step 51.



TM

Step 51 Read the following warning before proceeding to the next step.

WARNING — A reboot will cause the FSP 150CCf-825 to drop all traffic. Adhere to local practices when performing a reboot. Local practices may require you to ensure that the reboot will be performed during a scheduled maintenance window.

Step 52 If communications is not lost, and you wish to revert back to the previous version prior to when the Software Validation Timer expires, then select File and then Reboot.

Step 53 Wait until the reboot has competed. Communications will be lost while the reboot is in progress. Wait a few minutes, refresh the web browser, then log onto the system.



Step 56 Select the Software entity. The Software Status Window indicates the Software Validation Timer is no longer active and the Active Partition (containing the original load) is currently active

Note: At this point, the Standby Partition contains the new software load. If the system is kept in this status, it is still possible to activate the new software load at a later date by performing a Software Upgrade. However, if for any reason the Active flash partition fails, the system will attempt to use the Standby Partition, which contains the new load. Once you are absolutely sure that you want to discard to the new software load, you have the option to also overwrite the Standby Partition with the old load (by performing a Software Mirror) in order to provide redundancy.




TM

End of Procedure

Step 57 Right-click on the Software entity and select Software Validate to commit to the new load. The Software Validation window appears


Step 59 To continue the validation timer, select Cancel.


Current Status Then

Do you wish to commit the software update? Go to Step 61.

Do you wish to cancel and continue the Software Validation Timer?




TM

Step 61 To commit the software update, select OK. The Software Status Window indicates the Active Partition (containing the software update) is currently active

Note: At this point, the Standby Partition still contains the original software load. If the system is kept in this status, it is still possible to revert back to the original software load at a later date by performing a Software Upgrade. However, if for any reason the Active flash partition fails, the system will attempt to use the Standby Partition, which contains the old load. Once you are absolutely sure that you want to commit to the new software load, you have the option to also overwrite the Standby Partition with the new load in order to provide redundancy.


Step 63 Optional - If redundancy for the New Load is desired: Right-click on Software and select Software Mirror to copy the software image and database from the active partition (which contains the new software load) to the standby partition (which currently contains the old software load). The Software Mirror window appears

Current Status Then

Do you wish to continue to have the ability to revert back to the old software load?

End of Procedure

Do you wish to overwrite the Standby Partition with the new software load to ensure redundancy?





TM

Step 64 Select OK. A Software Mirror progress window appears The FSP 150CCf-825 will copy the software image and database from the active partition to the standby partition. Do not interrupt the software mirror while it is in progress. A progress window will appear, indicating the software mirror is in progress. It may take several minutes to complete the process.

Step 65 When complete, a successful completion message appears:



TM

Step 66 Select OK. The Software Status Window indicates both the Standby Partition and Active Partition contain the new software load

End of Procedure




TM

3.15 Configuration Database ManagementThe FSP 150CCf-825 eVision Web Browser Management Tool provides an easy means to manage the following configuration database management functions via the eVision Web Browser:

• Determining Database Configuration Status

• Save Changes

• Restore Factory Defaults

• Validation Timer

• Database Backup

• Database Restore

Determining Database Configuration StatusWhen an unsaved configuration change has been made to the FSP 150CCf-825, an “Unsaved Configuration Data” alarm is raised, alerting personnel that configuration changes have been made that have not been stored in non-volatile memory. If a power loss / system reboot should occur, all unsaved configuration data will be lost. Invoking Save Changes will save the current configuration database to non-volatile memory as well as store a CRC32 checksum of the saved configuration (see Save Changes).

This database configuration checksum is updated when changes have been made to the configuration data and a save configuration operation is performed. This checksum is retrievable via the eVision web browser management tool, CLI or SNMP. It can be used to compare the current database configuration with a back up master configuration. If no database files have been saved, or if the database has been set to factory default, the configuration database checksum is set to zero.

To view the configuration database checksum in eVision, select Maintenance view, expand the Administration entity, and then select the Database entity (see Figure 3-40 for an example of a default database configuration).



TM

Save ChangesIf any unsaved configuration database changes are present, an “Unsaved Configuration Data” alarm is raised. Should a power loss / system reboot occur without first saving configuration changes, the FSP 150CCf-825 will revert to the previously saved configuration database and any subsequent changes made will be lost. Invoking Save Changes will save the current configuration database to non-volatile memory and create a CRC32 checksum of the saved configuration (see Determining Database Configuration Status).

Procedure

WARNING — Do not power down the system while saving configuration data. Any power disruption during the save configuration process may cause adverse affects to system operations.

Step 1 Select File from the Menu Bar and then select Save Changes. A warning screen appears

Figure 3-40 Default Database Configuration




TM

Step 2 Select OK. A caution screen appears. It will take a few seconds to save the changes. When the operation is complete a completion message appears.

Step 3 Select OK.


Step 5 Expand nested items in the System Name and Administration entities by selecting the “+” next to each entity.

Step 6 Right-click on Database and select software. The software status screen indicates the saved configuration and its associated checksum are placed in the Active Partition, and the Active Partition is currently in use

End of Procedure

Restore Factory DefaultsRestoring the FSP 150CCf-825 to factory defaults will revert the FSP 150CCf-825 back to its original factory configuration settings. If any configuration changes have been made, whether they have been saved to non-volatile memory or not, will be purged, and the configuration database checksum will be set to zero. The factory default settings, as shown in Section 5.2 System Default Parameters and Maximum Bandwidth, on Page 5-2, will replace any configuration changes made.

WARNING — Restoring to Factory Defaults will revert the FSP 150CCf-825 to its original factory configuration settings. Any configuration changes that have been made will be purged, including all communications settings, and communications will be dropped. Once Factory Defaults have been restored, any desired configuration settings will need to be re-entered (or a Database Restore may be performed - if a Database Backup on a known good database has previously been created).

To restore factory defaults, select File from the Menu Bar and then select Restore Factory Defaults.



TM

Validation TimerValidation Timer is a “Safe Mode” feature that allows you to make configuration changes to the current database without saving to non-volatile memory. This allows the operator time to validate the changes made in a “Safe Mode” before committing the changes. For example, if a configuration change causes a loss of the communications link, after a specified amount of time, the “Safe Mode” timer will expire, the FSP 150CCf-825 will reboot, and the configuration data will automatically revert back to the old database. If communications is successful following the configuration change, or the verification process is successful, you can manually commit the transaction to non-volatile memory by exiting “Safe Mode.”

Procedure

Step 1 Observe the alarms window before making any configuration database changes. If an “Unsaved Configuration Data” alarm exists, verify that the current configuration database is valid, then save the changes by performing the procedure in Save Changes, on Page 3-108.

Step 2 If a configuration database backup has not been created, create a database backup before proceeding. This will ensure that the database can be restored if a power failure or communication failure occurs during the software upgrade. Refer to Database Backup, on Page 3-113 to perform the database backup.

Step 3 Select File and then Validation Timer. The Validation Timer window appears

Figure 3-41 Validation Timer Window




TM

Step 4 Enter a safety time-out period (1 to 10 minutes) that will provide enough time to enter the configuration changes, validate the changes made, and to cancel the validation timer, if it is required.

Step 5 Select OK. The amount of time remaining before timing out will display at the top of the screen

Step 6 Make the desired configuration changes and validate the changes prior to the validation timer expiration time.


WARNING — Allowing the Validation Timer to expire will cause the FSP 150CCf-825to reboot, and therefore, drop traffic. If communication to the FSP 150CCf-825 is possible, to prevent loss of traffic, use the Exit without Saving option in the following step prior to the Validation Timer expiration.

Current Status Then

Do you wish to commit the configuration changes? Go to Step 9.

Do you wish to revert back to the previous database? Continue with the next step.

ValidationTimerIndicator



TM

Step 8 If communications is lost, then do nothing. When the safety time-out period expires, the FSP 150CCf-825 will reboot, and therefore, revert back to the previous configuration database. If communications is not lost, select File and Validation Timer, then select Exit without Saving (see Figure 3-42). Then undo any unwanted database changes.

End of Procedure

Step 9 Read the following warning before proceeding to the next step.

WARNING — Do not power down the system while saving configuration data. Any power disruption during the save configuration process may cause adverse affects to system operations.

Step 10 To keep the changes and save to non-volatile memory, select File and Validation Timer, then select Exit and Save (see Figure 3-42). It will take a few seconds to save the changes. If the screen doesn’t refresh, manually refresh from the web browser.

End of Procedure

Figure 3-42 Commit/Exit Validation Timer Screen




TM

Database BackupWhenever configuration database changes are entered and verified, it is highly recommended that you create a database backup to a remote server location. Database backup is performed in a two step process. First, a database file is created to temporary storage. Then the configuration database file may be copied to a PC or server via web browser or FTP.

Procedure



Step 3 Right-click on Database and select Backup Database. The Backup Database window appears

Step 4 Select either Backup Database Only or Save Any Changes and Backup Database. Then select OK. A Backup Information screen appears, indicating the database has been backed up

Step 5 Select OK.



TM

Step 6 Right-click on Database and select Copy to Server. The Copy Backup Database to Remote Server window appears



Step 9 Click on “here” to go to the next screen to transfer the file. A confirmation screen appears, asking you if you want to save this file

Step 10 Select Save. A Save As window appears

Current Status Then

Do you wish to perform the backup via FTP? Go to Step 15.

Do you wish to perform the backup via web browser? Continue with the next step.




TM

Step 11 Browse to the desired location to store the backup database file.

Step 12 If desired, change the file name, leaving the .icf extension. Ensure that Save As type .icf Document is selected.

Step 13 Select Save. A Download Complete window appears

Step 14 Select Close.

End of Procedure


Step 16 Enter the FTP server IP address.


Step 18 Enter the path and file name to copy the configuration database backup file (enter the path from the server root directory).

Step 19 Select OK. A status screen appears indicating the file has been successfully transferred

Step 20 Select OK.

End of Procedure

Database RestoreOnce a configuration database has been backed up to a PC or server, the FSP 150CCf-825 configuration database may be restored by using the Database restore function. Database restore is performed in a three step process. First, the backup configuration file is copied from a PC or server via web browser or FTP to temporary storage. Then the database file is restored from the backup copy. Then a system restart must be performed before the changes will take affect.

Under special circumstances, it may be desirable or necessary to perform a combination software upgrade and database restoral. For instance, if a unit is being installed and turned up for a new service and a customized database file has been created to speed the process of building the user’s configuration from the default values in the original database file, the custom database file can be restored to the standby partition and then a software upgrade is performed with the option selected to preserve the standby database. This will then allow the implementation of the latest software release and activate the customized database at the same time.



TM

Procedure



Step 3 Right-click on Database and select Copy from Server. The Copy Database from Remote Server window appears



Step 6 Enter the path and filename to the database backup file (enter the path from the PC root directory) into the Select Database File entry window, or browse to the file location.

Step 7 Select OK. A status screen appears indicating the file has been successfully uploaded

Current Status Then

Do you wish to perform the database restore via FTP?

Go to Step 10.

Do you wish to perform the database restore via web browser?





TM

Step 8 Select OK.



Step 11 Enter the FTP server IP address.


Step 13 Enter the path and filename to the configuration database backup file (enter the path from the server root directory).

Step 14 Select OK. A status screen appears indicating the file has been successfully transferred

Step 15 Select OK.

Step 16 Right-click on Database and select Restore Database. A confirmation window appears

Step 17 Select Active or Standby. Active is used for all normal restorals. Standby is used when a combination software upgrade and database restoral is required.


Current Status Then

Did you select Active? Go to Step 20.

Did you select Standby? Continue with the next step.



TM

Step 19 Select OK. When the transfer completes, eVision will notify you. To activate the database in the standby partition, you must perform a software update procedure with the “preserve standby database” option selected. See Section 3.14 Software Upgrade, on Page 3-89.

End of Procedure

Step 20 Select OK. When the transfer completes, eVision will prompt you to reboot the system in order to implement the changes (the system must be rebooted in order for the changes to take affect)

Step 21 Click OK to restart the system. The main menu screen will be displayed once the restart completes.

Note: If the web browser does not seem to update automatically, you may need to refresh the web browser.

End of Procedure




TM

3.16 Rescue ImageAlthough designed to protect against data corruption, especially while performing software upgrades and database transfers or restoration operations, the FSP 150CCf-825 also has a fail-safe mode called “Rescue Image”, providing a means to communicate with the FSP 150CCf-825 and allow you to complete a software upgrade if the data transfer process fails due to data corruption, power loss or loss of communication.

Verification that the Rescue Image is running requires connecting your PC to the management console (RS 232) port and verifying that the Rescue Image indication is present. The Rescue Image allows you to communicate with the FSP 150CCf-825 via eVision using the default IP address (192.168.0.2/24) on the Management LAN Port (the FSP 150CCf-825 reverts back to its default database). When the software upgrade is completed, a configuration database restore needs to be performed. (See Database Restore, on Page 3-115.)

You will need the following items to access the serial console port and verify that the Rescue Image is running:


• Two Category 5 LAN Cables (with RJ-45 connectors)


• A communications program, like TeraTerm Pro Web (a free software terminal emulator [communication program] for MS-Windows) or HyperTerminal (a standard Windows communications utility)

Note: If normal reboot procedures are ineffective, the NID can be forced to Rescue Image mode by cycling power while holding the “Space” key down on the terminal interface.

Procedure

Step 1 Install the console cable between the FSP 150CCf-825 RS 232 Port and a PC using the RJ-45 cable and the DB-9 converter. See Section 1.6.1 Connectors and LED Descriptions, on Page 1-46 for the RS 232 Port connector location.


Note: The serial console port supports only 9600 baud. Do not use Autobaud.


Rate 9600 baud

Data Bits 8



TM

Step 3 Reboot the FSP 150CCf-825 while holding the “Space” key down on the terminal interface.

Step 4 The following information should display on the terminal interface screen. At the “]” prompt, type in “rescue” and press the “Enter” key.

Stop Bits 1

Parity No

Flow Control None

Table 3-1 COM Port Settings (Continued)PARAMETER SETTING




TM

Step 5 To verify that the Rescue Image is running, hit the “Enter” key and the following screen displays, indicating that a Rescue Image is running. Do not Login.

Note: If the Rescue Image does not appear, attempt to log onto the FSP 150CCf-825 to determine if the CLI prompt appears. If the normal login prompt is present, a communication or other problem exists; and if so, troubleshoot the problem. If neither the Rescue Image indication nor the normal login prompt appear, troubleshoot accordingly.

Step 6 Change your PC IP address to allow successful access of the FSP 150CCf-825 default Management LAN port IP address of 192.168.0.2 (at this point, the FSP 150CCf-825 configuration is at factory default).

Step 7 Remove the Management LAN cable if present, and connect your PC to the FSP 150CCf-825 Management LAN port using an Ethernet cable.

Rescue Image Indicator



TM

Step 8 Activate an Internet Explorer web browser by double clicking on the shortcut icon.

Step 9 Enter the FSP 150CCf-825’s default Management LAN port IP address (192.168.0.2) in the web browser address field and enter return. The Software Recovery screen will display

Step 10 Enter the location of the “ccxxxnnnnn.img” file, or browse to the file location (file name and location are case sensitive).

WARNING — Do not remove power while performing the next steps. Removing power while the operation in progress will corrupt the file transfer operation.

Step 11 Select OK. The software upgrade file will download to the FSP 150CCf-825. Do not interrupt the file download while it is in progress. A progress graph will appear, indicating the software update is in progress.




TM

Step 12 It may take several minutes to complete this file transfer. When the update is completed, a message will appear, indicating the software update was completed successfully. When the software download completes, eVision presents a confirmation screen:

Step 13 Click Reboot to restart the system. A security alert window will appear once the restart has completed

Step 14 Log onto the FSP 150CCf-825 using default user name (covaro1) and password (covaro#1).

Step 15 Select the system name in the menu tree and verify the software version.

Step 16 Perform a database restore (see Database Restore, on Page 3-115) or re-provision the configuration database. (If the backup configuration database is not located on your PC, configure communications as required to permit access to the remote configuration database file location, or copy the remote configuration database file onto your PC prior to performing the database restore operation.)

Step 17 Reset your PC to the original IP address settings and remove the LAN cable to the FSP 150CCf-825.

Step 18 Reconnect the Management LAN cable to the FSP 150CCf-825 Management LAN port.

Step 19 Log onto the FSP 150CCf-825 to verify connectivity and the configuration database.

End of Procedure



TM



Optical Networking

TM

Chapter 4 Communications Provisioning

4.1 OverviewThis Chapter contains communications provisioning examples that can be used to provision the FSP 150CCs for your specific network configuration. Four scenarios are presented along with provisioning details for each scenario. This Chapter also contains the following supporting communications procedures:

• Set Up Management LAN Port Using the Serial Console Port, on Page 4-23

• Set Up Management Tunnel Using eVision, on Page 4-33

• Set Up DHCP Using eVision, on Page 4-39

• Provision ACL Using eVision, on Page 4-47

4.2 Communications Provisioning for Various IP ConfigurationsThe FSP 150CC supports several management configurations and options. This section provides typical deployment scenarios showing FSP 150CCs in common IP network configurations. (This section does not provide a comprehensive explanation of IP networking concepts.)

The FSP 150CC can be connected in many different ways within an IP environment:

• They can be connected to a LAN through direct connections, a router, or an Ethernet switch.

• Different IP functions and protocols can be used to achieve specific network goals. For example, proxy Address Resolution Protocol (ARP) enables one LAN-connected FSP 150CC to serve as a gateway for another FSP 150CC that is not connected to the LAN.

• Static routes can be created to enable connections between a workstation (PC, SUN, etc.) and a FSP 150CC.

• FSP 150CCs can be connected to RIP networks so the FSP 150CC network information is automatically communicated across multiple LANs and WANs.


Installation and Operations Manual FSP 150CCf-825Chapter 4 - Communications ProvisioningRelease 1.2, November 2007 Optical Networking

TM

Prior to performing one of the following procedures, it is recommended that you become familiar with the Web Browser Management Tool. See Chapter 3, Web Browser Management Tool.

The following scenarios illustrate how to set up an FSP 150CC in an Internet Protocol (IP) network.

Scenario #1: Remote eVision Workstation Communications to SNE. A scenario managing FSP 150CCs in back-to-back configuration on the same subnet, where the SNE is on a logical extension of the subnet. One eVision workstation resides on the same LAN segment, and a remote eVision workstation is on a different LAN segment. A management tunnel is required. See Scenario 1: Remote eVision Workstation Communications to SNE, on Page 4-4.

Scenario #2: GNE and SNE on Different Subnets. A scenario managing FSP 150CCs in back-to-back configuration where the GNE and SNE reside on different subnets. A management tunnel is required. See Scenario 2: GNE and SNE FSP 150CCs on Different Subnets, on Page 4-11.

WAN

LAN Segment B

LAN Segment A

X

RIP Enabled

GNEFSP 150CC #1

SNEFSP 150CC #2

Management Tunnel

5

PSU1

Status

100 -240V AC

PSU2

Status CriticalMajorMinorStatus

Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3 5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3

WAN

LAN Segment A

SNE on Different Subnet as GNE

GNEFSP 150CC #1

SNEFSP 150CC #2

RIP EnabledManagement Tunnel

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3 5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3


Installation and Operations Manual FSP 150CCf-825Chapter 4 - Communications Provisioning


TM

Scenario #3: Stand Alone FSP 150CC Over a Layer 2 Cloud. A scenario managing a stand alone FSP 150CC over a Layer 2 Cloud. A management tunnel is required. See Scenario 3: Stand Alone FSP 150CC Over a Layer 2 Cloud, on Page 4-15.

Scenario #4: eVision Workstation and GNE on the Same Subnet, SNE on a Different Subnet, WAN Connectivity Through Layer 2 Cloud. A scenario managing FSP 150CC configuration where the eVision workstation and the Gateway NE (GNE) are on the same subnet and the Subtending NE (SNE) is on a different subnet, and WAN connectivity is over a Layer 2 cloud. In this configuration, one FSP 150CC is located on LAN Segment A via the Management LAN port, as shown below. A management tunnel is required. See Scenario 4: eVision Workstation and GNE on Same Subnet, SNE on a Different Subnet, FSP 150CCs Over a Layer 2 Cloud, on Page 4-18.

LAN Segment A

FSP 150CC

Layer 2 Cloud

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3

WAN

LAN Segment A

Management Tunnel

GNEFSP 150CC #1

SNEFSP 150CC #2

SNE on Different Subnet as GNE

WAN

Management Tunnel

Layer 2 Cloud5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3



TM

Scenario 1: Remote eVision Workstation Communications to SNEFigure 4-1 shows an example of an FSP 150CC Management LAN port configuration where FSP 150CC #1 and FSP 150CC #2 reside on the same subnet, and the SNE is located on a logical extension of the same subnet. One eVision workstation resides on the same subnet as the FSP 150CCs and a remote eVision workstation resides on a different subnet. A RIP enabled management tunnel is required.

Figure 4-1 eVision Workstation on LAN Segment A and FSP 150CCs on LAN Segment B

eVision Workstation 2IP Address = 10.10.0.24Subnet Mask = 255.255.255.0Default Gateway = 10.10.0.1

WAN

MGMT LAN Port IP Address = 192.168.2.2Subnet Mask = 255.255.255.0 Default Router =192.168.2.1 Static Route Not Required

GNEFSP 150CC #1

MGMT LAN Port IP Address = 192.168.2.3Subnet Mask = 255.255.255.0Default Router = None Static Route Not Required

LAN Segment B

Note: If a DHCP server is available on LAN Segment B, then enable DHCP on the Management LAN port of FSP 150CC #1. If DHCP is enabled, then the IP Address, Subnet Mask and Default Router will be assigned by the DHCP server.

LAN Segment A

IP Address = 192.168.2.4Subnet Mask = 255.255.255.0Default Gateway = 192.168.2.1

IP Address = 10.10.0.4Subnet Mask = 255.255.255.0Default Gateway = 10.10.0.1

X

eVision Workstation 1IP Address = 192.168.2.5Subnet Mask = 255.255.255.0Default Gateway = 192.168.2.1

Static RouteInterface = WANIP Address = 0.0.0.0 Subnet Mask = 0.0.0.0

Management TunnelVLAN Based, VLAN ID = 100 Layer 2 Protocol = PPP DHCP = disabled RIP V2 Packets = enabled

SNEFSP 150CC #2

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 35

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3




TM

Note 1: For management tunnels where RIP is enabled, under a Denial of Service attack scenario, RIP PDUs will likely be discarded, resulting in all RIP learned routes being withdrawn from the routing table. On the GNE, this will have the affect of losing the route to the SNE.

Note 2: When this procedure is completed, you will not be able to communicate directly to FSP 150CC #2’s Management LAN port. You will need to use the Serial Console port to communicate to FSP 150CC #2 because its Management LAN port will be disabled.

Procedure

Perform the following steps at FSP 150CC #2:

Step 1 At FSP 150CC #2, perform the procedures Section 1.6.3 Power Options and Wiring, on Page 1-59 and Section 4.3 Set Up Management LAN Port Using the Serial Console Port, on Page 4-23.

Note: According to the example in Figure 4-1, on Page 4-4, FSP 150CC #2’s Management LAN port DHCP setting should be disabled, the IP address should now be set to 192.168.2.3 with a Subnet Mask of 255.255.255.0 and No Default Router, and you should currently be logged onto the FSP 150CC using the eVision Web Browser Management Tool. In this example, a commissioning PC IP address of 192.168.2.4/24 will successfully access the FSP 150CC.

Step 2 Provision the WAN management tunnel. Perform the procedure in Section 4.4 Set Up Management Tunnel Using eVision, on Page 4-33. According to the example in Figure 4-1, on Page 4-4, the FSP 150CC #2 WAN management tunnel is provisioned as VLAN Based with a VLAN ID of 100, PPP Layer 2 Protocol, DHCP is set to disabled, and RIP V2 Packets Enabled is set to enabled.

Step 3 Select the System Name to view the current Proxy ARP setting (in the example in Figure 4-1, on Page 4-4, Proxy ARP should be Disabled for FSP 150CC #2).

CAUTION — Ensure that the Proxy ARP option is set correctly for the FSP 150CC. If two or more ADVA NEs or FSP 150CCs are connected via SDCC or Management Tunnel as well as connected to the same LAN, then only one of the them should have the Proxy ARP option enabled. Otherwise, there will be multiple ARP responses for a single ARP request for a remote reachable IP address from each NE/FSP 150CC in the same LAN that has Proxy ARP enabled.

Step 4 If the current Proxy ARP setting is set to disabled, go to Step 9. If the Proxy ARP setting needs to be changed, continue with the next step.



TM

Step 5 Right-click on the System Name and select Edit Settings. The edit system settings screen appears

Step 6 Set the Proxy ARP to the appropriate setting (disabled).

Step 7 Observe the current date and time setting. If changes are required, enter the changes.

Step 8 Select OK.

Step 9 Right click on the Communications entity in the menu tree and select Create Static Route. The create static route screen appears

Step 10 For Route Type, select Interface, and for Interface, select Wan.

Step 11 For IP Address, enter 0.0.0.0.

Step 12 For IP Mask, enter 0.0.0.0.

Step 13 If desired, select the Advertise Route check box.

Step 14 Select OK. The Static Route entry displays in the Static Routes tab

Step 15 Right click on the Local Management Port and select Edit Facility. The edit Local Management Port screen appears

Step 16 Set the Administration State to Disabled.




TM

Step 17 Select OK (communications will be dropped and the configuration will need to be saved using CLI, as described in the following steps).

Note: The browser will appear to stay busy after OK is selected because it is attempting to reach the IP address of the FSP 150CC who’s Local Management Port has just been disabled.

Step 18 Install the console cable between the FSP 150CC RS-232 Port and a PC using the RJ-45 cable and the DB-9 converter. See Section 1.6.1 Connectors and LED Descriptions, on Page 1-46 for the RS-232 Serial Console Port connector location.

Step 19 From the PC, start a communications utility application, such as HyperTerminal with the following COM port settings:


Step 20 Hit the “Enter” key and you will be prompted to enter a login and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively. The serial console CLI prompt (-->) will then be displayed.

Step 21 Enter show interface mgmt-lan followed by a carriage return. The DHCP setting will display, as shown below. Verify that the Administration State is set to Disabled.

COMM Port Parameter

COMM Port Setting

Baud Rate 9600 baud

Data 8 bits

Stop Bits 1

Parity No

Flow Control None

--> show interface mgmt-lan

Management Interface: mgmt-lan

Administrative State: Disabled

Operational State: Enabled

MAC Address: 00:0B:90:00:47:80

MTU: 1500

Interface Speed: Auto

Negotiated Speed: 100 Mb Full Duplex

DHCP: Disabled

RIPv2: Disabled

ACL Inbound Filtering: Disabled



TM

WARNING — Do not remove power while performing the next step. Removing power while the operation in progress may corrupt the database.

Step 22 Enter database save followed by a carriage return. The system will display a warning message and when complete, the CLI prompt will appear, as shown below:

Step 23 Enter logout followed by a carriage return. The login prompt will appear

Step 24 Remove any commissioning cables (Ethernet cable and/or console cable) from the FSP 150CC front panel connectors, as required.

Step 25 Connect the WAN cable to the FSP 150CC front panel connector.

Perform the following at FSP 150CC #1:


Note: According to the example in Figure 4-1, on Page 4-4, FSP 150CC #1’s DHCP option should be set appropriately (the IP address should now be set to 192.168.2.2 with a Subnet Mask of 255.255.255.0 and Default Router of 192.168.2.1), and you should currently be logged onto the FSP 150CC using the eVision Web Browser Management Tool. In this example, your PC IP address should still be set to 192.168.2.4/24 to successfully access the FSP 150CC.

Step 27 Provision the WAN management tunnel. Perform the procedure in Section 4.4 Set Up Management Tunnel Using eVision, on Page 4-33. According to the example in Figure 4-1, on Page 4-4, the FSP 150CC #1 WAN management tunnel is provisioned as VLAN Based, PPP Layer 2 Protocol, DHCP is set to disabled, and RIP V2 Packets Enabled is set to enabled.

Step 28 Select the System Name to view the current Proxy ARP setting (in the example in Figure 4-1, on Page 4-4, Proxy ARP should be Enabled for FSP 150CC #1).

--> database save


-->




TM


Step 29 If the current Proxy ARP setting is correct, go to Step 34. If the Proxy ARP setting needs to be changed, continue with Step 30.


Step 31 Set the Proxy ARP to the appropriate setting.

Step 32 Observe the current date and time setting. If changes are required, enter the changes.

Step 33 Select OK.

Step 34 Select File and then Save Changes from the menu bar.


Step 35 Select OK.


Step 37 Connect the WAN cable to the FSP 150CC front panel connector.

Step 38 Observe the WAN LED on the front panel. It should be lit green. If the WAN LED is not lit green, then troubleshoot the WAN connections between FSP 150CC #1 and FSP 150CC #2.

Step 39 Verify that the Management LAN cable is connected to the FSP 150CC.

Step 40 Verify connectivity to FSP 150CC #1 and FSP 150CC #2 from eVision Workstation 1. Set the PC’s Default Gateway to the router’s IP address (according to the example in Figure 4-1, on Page 4-4, use a Default Gateway of 192.168.2.1). (Open a web browser window and enter the IP address of FSP 150CC #1 to access the FSP 150CC eVision Web Browser Management Tool. Logon using a valid user name and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively. Repeat for FSP 150CC #2.)



TM

Step 41 Verify connectivity to FSP 150CC #1 and FSP 150CC #2 from eVision Workstation 2. Set the PC’s Default Gateway to the router’s IP address (according to the example in Figure 4-1, on Page 4-4, use a Default Gateway of 10.10.10.1). (Open a web browser window and enter the IP address of FSP 150CC #1 to access the FSP 150CC eVision Web Browser Management Tool. Logon using a valid user name and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively. Repeat for FSP 150CC #2.)

End of Procedure




TM

Scenario 2: GNE and SNE FSP 150CCs on Different SubnetsFigure 4-2 shows an example of back-to-back FSP 150CCs where the GNE and SNE FSP 150CCs are on different subnets. FSP 150CC #2 has no LAN connection, and FSP 150CC #2 has a WAN management tunnel connection to FSP 150CC #1. A management tunnel is required.

Note: For management tunnels where RIP is enabled, under a Denial of Service attack scenario, RIP PDUs will likely be discarded, resulting in all RIP learned routes being withdrawn from the routing table. On the GNE, this will have the affect of losing the route to the SNE.

Procedure



Figure 4-2 GNE and SNE FSP 150CCs on Different Subnets

WAN

MGMT LAN Port IP Address = 192.168.2.2Subnet Mask = 255.255.255.0 Default Router =192.168.2.1 Static Route Not Required

MGMT LAN Port IP Address = 192.168.3.1Subnet Mask = 255.255.255.0Default Router = None Static Route Not Required

LAN Segment A

Note 1: If a DHCP server is available on LAN Segment A, then enable DHCP on the Management LAN port of each FSP 150CC. If DHCP is enabled, then the IP Address, Subnet Mask and Default Router will be assigned by the DHCP server.

Note 2: The eVision Workstation must have a default gateway set to the GNE’s IP address or a static route must be created at the PC to the GNE’s IP address.

GNEFSP 150CC #1

SNE FSP 150CC #2

Management TunnelVLAN Based, VLAN ID = 100 Layer 2 Protocol = PPP DHCP = disabled RIP V2 Packets = enabled

eVision WorkstationIP Address = 10.10.0.5Subnet Mask = 255.255.255.0Default Gateway = 10.10.0.1

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 35

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3



TM

Note: According to the example in Figure 4-2, FSP 150CC #2’s DHCP setting should be disabled, the IP address should be set to 192.168.3.1 with a Subnet Mask of 255.255.255.0 and no Default Router, and you should currently be logged onto the FSP 150CC using the eVision Web Browser Management Tool. In this example, a commissioning PC IP address of 192.168.3.4/24 will successfully access the FSP 150CC.







Step 7 Observe the current date and time setting. If the current setting is incorrect, enter the changes.

Step 8 Select OK.



Step 10 Select OK.





TM

Step 12 Connect the WAN cables to the FSP 150CC front panel connectors.



Note: According to the example in Figure 4-2, on Page 4-11, FSP 150CC #1’s DHCP option should be set appropriately (the IP address should now be 192.168.2.2 with a Subnet Mask of 255.255.255.0 and Default Router of 192.168.2.1), and you should currently be logged onto the FSP 150CC using the eVision Web Browser Management Tool. In this example, a commissioning PC IP address of 192.168.2.4 with a Subnet Mask of 255.255.255.0 will successfully access the FSP 150CC.








Step 20 Select OK.




TM


Step 22 Select OK.




Step 26 Depending on your configuration, either set the eVision workstation default gateway to point to the GNE FSP 150CC’s Management LAN port IP address, or create a static route on the PC to the GNE FSP 150CC’s Management LAN port IP address. This will allow you to connect to the SNE since it’s IP address is on a different subnet.

Step 27 Verify connectivity to FSP 150CC #1 and FSP 150CC #2 from the eVision Workstation. (Open a web browser window and enter the IP address of FSP 150CC #1 to access the FSP 150CC eVision Web Browser Management Tool. Logon using a valid user name and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively. Repeat for FSP 150CC #2.)

End of Procedure




TM

Scenario 3: Stand Alone FSP 150CC Over a Layer 2 CloudFigure 4-3 shows an example of a basic stand alone FSP 150CC configuration. The FSP 150CC and Workstation reside on the same subnet with the FSP 150CC connected to the LAN segment via a third party Layer 2/Layer 3 device, such as an Ethernet switch.

Figure 4-3 Standalone FSP 150CC Over a Layer 2 Cloud

eVision WorkstationIP Address = 10.10.34.5Subnet Mask = 255.255.255.0

WAN

MGMT LAN Port IP Address = 192.168.0.2 (default)Subnet Mask = 255.255.255.0Default Router = None Static Route Not Required DHCP = disabled

Note: If a DHCP server is available on the WAN, then enable DHCP on the WAN Port of the FSP 150CC. If DHCP is enabled on the WAN, then the IP Address, Subnet Mask and Default Router will be assigned by the DHCP server.

LAN Segment A

FSP 150CC

Management TunnelVLAN Based, VLAN ID = 100 Layer 2 Protocol = Ethernet DHCP = enabled IP Address = 10.10.34.228 Subnet Mask = 255.255.255.0 RIP V2 Packets = disabled

Layer 2 Cloud

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3



TM

Procedure

Step 1 Determine what type of management tunnel to use:

• MAC Based with Layer 2 Protocol = Ethernet, or

• VLAN Based with Layer 2 Protocol = Ethernet

Step 2 At the FSP 150CC, perform the procedures Section 1.6.3 Power Options and Wiring, on Page 1-59 and Section 4.3 Set Up Management LAN Port Using the Serial Console Port, on Page 4-23.

Note: According to the example in Figure 4-3, on Page 4-15, the FSP 150CC’s Management LAN port DHCP setting should be disabled, the IP address should be set to default (192.168.0.2) with a Subnet Mask set to default (255.255.255.0) and no Default Router, and you should currently be logged onto the FSP 150CC Management LAN port using the eVision Web Browser Management Tool. In this example, a commissioning PC IP address of 192.168.0.4/24 will successfully access the FSP 150CC.

Step 3 Provision the WAN management tunnel. Perform the procedure in Section 4.4 Set Up Management Tunnel Using eVision, on Page 4-33. According to the example in Figure 4-3, on Page 4-15, the FSP 150CC WAN management tunnel DHCP option should be set appropriately (the WAN IP address should now be set to 10.10.34.228 with a Subnet Mask of 255.255.255.0), the Layer 2 Protocol should be set to Ethernet, the VLAN ID should be set to 100, and RIP V2 Packets Enabled should be set to disabled.

Step 4 Change your PC Default Gateway setting to successfully access the FSP 150CC’s WAN IP address to verify the WAN port. (Your PC should still be connected to the Management LAN port. Set the PC’s Default Gateway to the FSP 150CC #’s Management LAN port IP address [192.168.0.2 in this example].)


Step 6 Enter the FSP 150CC’s WAN IP address (10.10.34.228 in this example) in the web browser address field and enter return. The Login Screen appears

Step 7 Enter User Name (default is covaro1) and Password (default is covaro#1).

Step 8 Select OK. The eVision Web Browser Management Tool will display

Step 9 Select the System Name to view the current Proxy ARP setting (in the example in Figure 4-3, on Page 4-15, Proxy ARP should be Disabled for the FSP 150CC).




TM






Step 14 Select OK.



Step 16 Select OK.



Step 19 Observe the WAN LED on the front panel. It should be lit green. If the WAN LED is not lit green, then troubleshoot the WAN connections between the FSP 150CC and the Layer 2 device.

Step 20 Verify connectivity to the FSP 150CC from the eVision Workstation (IP address 10.10.34.5 with a subnet mask of 255.255.255.0 according to the example in Figure 4-3, on Page 4-15). (Open a web browser window and enter the WAN IP address [10.10.34.228 in this example] of the FSP 150CC to access the FSP 150CC eVision Web Browser Management Tool. Logon using a valid user name and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively.)

End of Procedure



TM

Scenario 4: eVision Workstation and GNE on Same Subnet, SNE on a Different Subnet, FSP 150CCs Over a Layer 2 CloudFigure 4-4 shows an example of back-to-back FSP 150CCs where the eVision workstation and Gateway NE (GNE) are on the same subnet, the Subtending NE (SNE) is on a different subnet, and WAN connectivity between FSP 150CCs is through a Layer 2 cloud. FSP 150CC #1 and the Workstation reside on LAN Segment A. FSP 150CC #2 has no LAN connection, and FSP 150CC #2 has a WAN management tunnel connection to FSP 150CC #1.

Figure 4-4 Workstation / GNE on Same Subnet, SNE on Different Subnet, FSP 150CCs Over a Layer 2 Cloud

eVision WorkstationIP Address = 192.168.2.4Subnet Mask = 255.255.255.0Default Gateway = 192.168.2.2

WAN

MGMT LAN Port IP Address = 192.168.2.2Subnet Mask = 255.255.255.0 Default Router = 192.168.2.1 Static Route Not Required DHCP = enabled Proxy ARP = enabled

GNEFSP 150CC #1

SNE FSP 150CC #2

MGMT LAN Port IP Address = 192.168.0.2 (default)Subnet Mask = 255.255.255.0Default Router = N/A Static Route Not Required DHCP = false

LAN Segment A

Note 1: If a DHCP server is available on LAN Segment A and/or the Layer 2 device, then enable DHCP on the WAN Port of FSP 150CC #1 and/or FSP 150CC #2. If DHCP is enabled, then the IP Address, Subnet Mask and Default Router will be assigned by the DHCP server. Note 2: Must create a static route on the eVision Workstation PC to reach the SNE OR set the PC’s Default Gateway to the GNE’s IP Address.

WAN

Management TunnelVLAN Based, VLAN ID = 100 Layer 2 Protocol = Ethernet DHCP = disabled RIP V2 Packets = enabled IP Address = 10.10.10.4 Subnet Mask = 255.255.255.0

Management TunnelVLAN Based, VLAN ID = 100 Layer 2 Protocol = Ethernet DHCP = disabled RIP V2 Packets = enabled IP Address = 10.10.10.5 Subnet Mask = 255.255.255.0

Layer 2 Cloud

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3

5

PSU1

Status

100 -240V AC

PSU2


Etherjack TM

Management

RS -232

LAN

4321

2 4 Access


21

Active

Network FSP150CCf

211 3




TM


Procedure

Step 1 Determine what type of management tunnel to use:

• MAC Based with Layer 2 Protocol = Ethernet, or

• VLAN Based with Layer 2 Protocol = Ethernet



Note: According to the example in Figure 4-4, on Page 4-18, FSP 150CC #2’s Management LAN port DHCP setting should be disabled, the IP address should be set to default (192.168.0.2) with a Subnet Mask set to default (255.255.255.0) and no Default Router, and you should currently be logged onto the FSP 150CC’s Management LAN port using the eVision Web Browser Management Tool. In this example, a commissioning PC IP address of 192.168.0.4/24 will successfully access the FSP 150CC.

Step 3 Provision the WAN management tunnel. Perform the procedure in Section 4.4 Set Up Management Tunnel Using eVision, on Page 4-33. According to the example in Figure 4-4, on Page 4-18, the FSP 150CC #2’s WAN management tunnel should be set to Ethernet Layer 2 Protocol, the DHCP option should be set appropriately (the IP address should be set to 10.10.10.5 with a Subnet Mask of 255.255.255.0), the VLAN ID should be set to 100, and RIP V2 Packets Enabled should be set to enabled.

Step 4 Change your PC Default Gateway setting to successfully access the FSP 150CC’s WAN IP address to verify the WAN port. (Your PC should still be connected to the Management LAN port. Set the PC’s Default Gateway to FSP 150CC #2’s Management LAN port IP address [192.168.0.2 in this example].)


Step 6 Enter the FSP 150CC’s WAN IP address (10.10.10.5 in this example) in the web browser address field and enter return. The Login Screen appears

Step 7 Enter User Name (default is covaro1) and Password (default is covaro#1).



TM

Step 8 Select OK. The eVision Web Browser Management Tool will display







Step 14 Select OK.



Step 16 Select OK.








TM

Note: According to the example in Figure 4-4, on Page 4-18, FSP 150CC #1’s Management LAN port DHCP option should be set appropriately (the IP address should now be 192.168.2.2 with a Subnet Mask of 255.255.255.0 and Default Router of 192.168.2.1), and you should currently be logged onto the FSP 150CC Management LAN port using the eVision Web Browser Management Tool. In this example, a commissioning PC IP address of 192.168.2.4/24 will successfully access the FSP 150CC.

Step 20 Provision the WAN management tunnel. Perform the procedure in Section 4.4 Set Up Management Tunnel Using eVision, on Page 4-33. According to the example in Figure 4-4, on Page 4-18, the FSP 150CC #1’s WAN management tunnel DHCP option should be set appropriately (the IP address should be set to 10.10.10.4 with a Subnet Mask of 255.255.255.0), the Ethernet Layer 2 Protocol should be set to Ethernet, the VLAN ID should be set to 100, and RIP V2 Packets Enabled should be set to enabled.







Step 26 Select OK.



Step 28 Select OK.



TM




Step 32 Depending on your configuration, either set the eVision workstation default gateway to point to the GNE FSP 150CC’s Management LAN port IP address, or create a static route on the PC to communicate to the SNE (e.g., from Windows command prompt, enter route add 192.168.0.2 mask 255.255.255.255 192.168.2.2 according to the example in Figure 4-4, on Page 4-18). This will allow you to connect to the SNE since it’s IP address is on a different subnet.

Step 33 Verify connectivity to FSP 150CC #1 and FSP 150CC #2 from the eVision Workstation. (Open a web browser window and enter the IP address of FSP 150CC #1 to access the FSP 150CC eVision Web Browser Management Tool. Logon using a valid user name and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively. Repeat for FSP 150CC #2.)

End of Procedure




TM

4.3 Set Up Management LAN Port Using the Serial Console PortPerform the following procedure to set up the Local Management LAN port (MGMT LAN) using the RS-232 Serial Console Port CLI command structure. (For more information on the CLI command structure, see the Etherjack OS (EOS) Command Line Interface Handbook.)

You will need the following items for this procedure:


• Category 5 LAN Cable (with RJ-45 connectors)


• A communications program, like TeraTerm Pro Web (a free software terminal emulator [communication program] for MS-Windows) or HyperTerminal (a standard Windows communications utility)


This procedure is intended to be used during the commissioning process or used as a stand-alone procedure. For existing sites you may wish to use the provisioning options available through the eVision Web Browser Management Tool. See Chapter 3, Web Browser Management Tool for more information on eVision provisioning options.

The default DHCP setting for the Management LAN port is disabled. Therefore, it is possible to access the FSP 150CC during commissioning via the eVision Web Browser Management Tool by connecting your PC to the Management LAN port and using the default IP address (192.168.0.2/24) to log onto the FSP 150CC. The default DHCP setting for the WAN port is enabled.

This procedure is offered as the best way to set up the FSP 150CC IP address using the CLI command structure by connecting a LAN cable to the RS-232 Serial Console Port and your PC. If a DHCP server is not available for the Management LAN port, then DHCP must be disabled. If DHCP is disabled on the Management LAN port, the default IP address is 192.168.0.2/24. Note that DHCP settings are available for LAN, WAN and the Management LAN port interfaces, but DHCP may only be enabled on one of the FSP 150CC’s interfaces.

The IP addresses, Subnet Masks and Default Router entries shown in these procedures are for example purposes only. The information you will enter should be determined from local sources.

Procedure

Step 1 Connect the console cable between the FSP 150CC RS-232 Serial Console Port and a PC using the RJ-45 cable and the DB-9 converter. See Section 1.6.1 Connectors and LED Descriptions, on Page 1-46 for the RS-232 Serial Console Port connector location.



TM



Step 3 Hit the “Enter” key and you will be prompted to enter a login and password. The default login and password are ‘covaro1’ and ‘covaro#1,’ respectively. The serial console CLI prompt (-->) will then be displayed.

Step 4 Use the show mgmttnl e1000-wan-1 command followed by a carriage return to view the current WAN DHCP setting. See the following example:


Baud Rate 9600 baud

Data 8 bits

Stop Bits 1

Parity No

Flow Control None

--> show mgmttnl e1000-wan-1

Management Tunnel: e1000-wan-1

Tunnel Mode: None

Encapsulation: Ethernet

Tunnel VLAN ID: 4095

Tunnel S-Tag: Disabled

Tunnel S-Tag VLAN ID: 4095

IP Address: 0.0.0.0

Subnet Mask: 255.255.255.0

MAC Address: 00:0B:90:00:47:81

DHCP: Enabled

RIPv2: Disabled





TM


Step 6 Use the configure mgmttnl e1000-wan-1 command followed by a carriage return. A next level prompt will appear. Then enter dhcp enable or dhcp disable followed by a carriage return to set the desired DHCP state. For example:

Step 7 Use the show mgmttnl e1000-wan-1 command followed by a carriage return to verify the changes.


Note: DHCP may only be enabled on one interface.

Current Status Then

Is the WAN port DHCP status set to the desired state of Disabled?

Go to Step 9.

Is the WAN port DHCP status set to the desired state of Enabled?

Go to Step 23.

Does the WAN port DHCP setting need to be changed?


--> configure mgmttnl e1000-wan-1

config:mgmttnl(e1000)--> dhcp disable

config:mgmttnl(e1000)-->

Current Status Then

Did the command complete without any error message?

Proceed to the next step.

Did you receive a failure message indicating DHCP is already set on another interface?

Disable DHCP on the other management tunnel interface by entering the exit command to go back one level, enter the configure mgmttnl <ifname> command (where ifname is the interface name indicated in the failure message), then enter the dhcp disable command, OR disable DHCP on the Management LAN port by entering the exit command to go back one level, enter the configure interface mgmt-lan command, then enter the dhcp disable command. Upon completion, go to Step 6 to select the desired WAN port DHCP setting.



TM

Step 9 Enter show interface mgmt-lan followed by a carriage return to view the current Management LAN port DHCP setting:


Step 11 Enter exit followed by a carriage return to go back one level, if required. Then enter configure interface mgmt-lan followed by a carriage return. A next level prompt will appear. Then enter dhcp enable or dhcp disable followed by a carriage return to set the desired DHCP state.

Step 12 Enter show interface mgmt-lan followed by a carriage return to view the verify the changes.

--> show interface mgmt-lan

Management Interface: mgmt-lan

Administrative State: Enabled

Operational State: Enabled

MAC Address: 00:0B:90:00:47:80

MTU: 1500


Negotiated Speed: 100 Mb Full Duplex

DHCP: Disabled

RIPv2: Disabled


Current Status Then

Is the Management LAN port DHCP status set to the desired state?

Go to Step 14.

Does the Management LAN port DHCP setting need to be changed?


--> configure interface mgmt-lan

config:if(mgmt)--> dhcp disable

config:if(mgmt)-->




TM




Step 15 Ensure that the local LAN cable is connected to the Management LAN port.

WARNING — Do not remove power while performing the next step. Removing power while the operation in progress will cause the FSP 150CC to lose its configuration.


Current Status Then

Did the command complete without any error message?


Did you receive a failure message indicating DHCP is already set on another interface?

Disable DHCP on the other interface by entering the exit command to go back one level, then entering the configure mgmttnl <ifname> command (where ifname is the interface name indicated in the failure message), then enter the dhcp disable command. Upon completion, go to Step 9 to select the desired Management LAN port DHCP setting.

Current Status Then

Is the Management LAN port DHCP set to enabled? Proceed to the next step.

Is the Management LAN port DHCP set to disabled? Go to Step 23.

--> database save


-->



TM

Step 17 Enter show ip followed by a carriage return. The Management LAN port IP information displays:



Verify the local Management LAN port communication settings by accessing the FSP 150CC’s eVision Web Browser Management Tool. Perform the following steps:

Step 20 Change your PC IP address to successfully access the FSP 150CC’s Management LAN port IP address from the local LAN port.

Step 21 Connect your PC to the local LAN port.


Step 23 Enter show ip followed by a carriage return. The Management LAN port IP information displays:

--> show ip

System IP Information:

IP Address:

Subnet Mask:

Default Gateway:

10.10.36.163

255.255.240.0

10.10.32.1

Current Status Then

Is the IP address correct? Proceed to the next step.

Is the correct IP address not shown and IP connectivity should be available?

Wait a few minutes, then retry Step 17. If after several attempts, the IP address still does not appear, contact your System Administrator. When the correct IP address is present, proceed to the next step.

--> show ip


IP Address:

Subnet Mask:

Default Gateway:

10.10.36.163

255.255.240.0

10.10.32.1




TM


Step 25 If required, enter the IP address and subnet mask, by entering configure system followed by a carriage return. A next level prompt will appear. Then enter ip-address <address> <subnet mask>.

Step 26 If required, enter a new Default Gateway, by entering ip-gateway nexthop <gateway> or ip-gateway interface <ifname> followed by a carriage return.

Step 27 Verify the changes by entering show ip followed by a carriage return. The Management LAN port IP information displays:

WARNING — Do not remove power while performing the next step. Removing power while the operation in progress will cause the FSP 150CC to lose its configuration.



Current Status Then

Do the IP address, Subnet Mask and/or Default Router require changes?


Are the IP address, Subnet Mask and Default Router are all correct?

Go to Step 28.

--> show ip


IP Address:

Subnet Mask:

Default Gateway:

10.10.36.163

255.255.240.0

10.10.32.1

--> database save


-->



TM

Verify the local Management LAN port communication settings by accessing the FSP 150CC’s eVision Web Browser Management Tool. Perform the following steps:

Step 30 Change your PC IP address to successfully access the FSP 150CC’s Management LAN port IP address (default is 192.168.0.2 if DHCP is disabled).

Note: If commissioning multiple FSP 150CCs, try to use an IP address that can be used to access each FSP 150CC you plan to commission. This will help reduce the amount of times you will need to reconfigure your PC’s IP address when commissioning. Do not use the same IP address as any Static Route when commissioning the FSP 150CC or communications will be dropped during provisioning, and you will need to change the IP address of your PC to complete commissioning the FSP 150CC.

Step 31 Use an Ethernet cable to connect your PC to the FSP 150CC Management LAN port.


Step 33 Enter the FSP 150CC’s Management LAN port IP address in the web browser address field and enter return. A security alert window will appear




TM

Step 34 Verify that the security certificate is valid. Select Yes to proceed. The FSP 150CC login window appears





TM

Step 37 Select Continue. The eVision Web Browser Management Tool will display, as shown in the following example

End of Procedure




TM

4.4 Set Up Management Tunnel Using eVisionPerform the following procedure to set up the WAN or LAN Management Tunnel using the eVision Web Browser Management Tool. (For more information on the eVision Web Browser Management Tool, see Chapter 3, Web Browser Management Tool.)

Procedure

Step 1 Use an Ethernet cable to connect your PC to the FSP 150CC Management LAN port and log onto the FSP 150CC via the eVision web browser.


To set up a MAC Based Management Tunnel

To set up a MAC Based Management Tunnel, perform the following steps:

Step 3 Select Applications \__ Configuration from the menu bar.

Step 4 Open the System Name and Communication menus by selecting the “+” next to each entity.

Desired Management Tunnel Then

Is MAC Based Management Tunnel desired? Go to Step 3.

Is VLAN Based Management Tunnel with Ethernet encapsulation desired?

Go to Step 15.

Is VLAN Based Management Tunnel with PPP encapsulation desired?

Go to Step 29.



TM

Step 5 Right-click on MGMT Tunnel (WAN or LAN-x) and select Edit Mgmt Tunnel. The Management Tunnel view will appear

Step 6 Set Tunnel Mode to MAC Based. Layer 2 Protocol is set to Ethernet

Step 7 Select the appropriate DHCP setting. (If a DHCP server exists for the interface, then set DCHP to Enabled. Otherwise, set DHCP to Disabled.)


Step 8 If DHCP is set to disabled, enter the IP Address and Subnet Mask.

Step 9 Set the desired RIP setting.Note: For management tunnels where RIP is enabled, under a Denial of Service

attack scenario, RIP PDUs will likely be discarded, resulting in all RIP learned routes being withdrawn from the routing table. On the GNE, this will have the affect of losing the route to the SNE.

Step 10 Select OK.

Figure 4-5 Management Tunnel View




TM



Step 13 Ensure that that WAN or LAN cable is connected to the appropriate FSP 150CC connector.

Step 14 Refresh the web browser and observe the WAN or LAN IP address.

To set up a VLAN Based Management Tunnel with Ethernet Encapsulation

To set up a VLAN Based Management Tunnel with Ethernet encapsulation, perform the following steps:



Step 17 Right-click on MGMT Tunnel (WAN or LAN-x) and select Edit Mgmt Tunnel. The Management Tunnel view will appear as shown in Figure 4-5, on Page 4-34

Current Status Then

Did the settings complete without an error message?

Proceed to Step 12.

Did you receive an error message indicating DHCP is already enabled on another interface?

Go to Section 4.5 Set Up DHCP Using eVision, on Page 4-39 to disable DHCP on the other interface. Upon completion, go to Step 5 to set up the management tunnel.

Current Status Then

Did you set DHCP to enabled? Proceed to Step 13.

Did you set DHCP to disabled? Go to Step 38.

Current Status Then

Is the IP address correct? Go to Step 38.


Wait a few minutes and refresh the web browser again. If after several attempts, the IP address still does not appear, contact your System Administrator. When the correct IP address is present, go to Step 38.



TM

Step 18 Set Tunnel Mode to VLAN Based.

Step 19 Set Layer 2 Protocol to Ethernet.

Step 20 For LAN Management Tunnel: Enter the VLAN ID. For WAN Management Tunnel: Enter the VLAN ID. If an S-Tag VLAN ID is desired, select the S-Tag VLAN ID check box, then enter the S-Tag VLAN ID.

Note: Default VLAN ID is 4095. The same VLAN ID number(s) must be used for both FSP 150CCs.

Step 21 Select the appropriate DHCP setting. (If a DHCP server exists for the interface, then set DCHP to Enabled. Otherwise, set DHCP to Disabled.)


Step 22 If DHCP is set to disabled, enter the IP Address and Subnet Mask.

Step 23 Set the desired RIP setting.


Step 24 Select OK.



Step 27 Ensure that that WAN or LAN cable is connected to the appropriate FSP 150CC connector.

Current Status Then

Did the settings complete without an error message?

Proceed to Step 26.

Did you receive an error message indicating DHCP is already enabled on another interface?

Go to Section 4.5 Set Up DHCP Using eVision, on Page 4-39 to disable DHCP on the other interface. Upon completion, go to Step 17 to set up the management tunnel.

Current Status Then

Did you set DHCP to enabled? Proceed to Step 27.

Did you set DHCP to disabled? Go to Step 38.




TM

Step 28 Refresh the web browser and observe the WAN or LAN IP address.

To set up a VLAN Based Management Tunnel with PPP Encapsulation

To set up a VLAN Based Management Tunnel with PPP encapsulation, perform the following steps:



Step 31 Right-click on MGMT Tunnel (WAN or LAN-x) and select Edit Mgmt Tunnel. The Management Tunnel view will appear as shown in Figure 4-5, on Page 4-34

Step 32 Set Tunnel Mode to VLAN Based.

Step 33 Set Layer 2 Protocol to PPP.

Step 34 For LAN Management Tunnel: Enter the VLAN ID. For WAN Management Tunnel: Enter the VLAN ID. If an S-Tag VLAN ID is desired, select the S-Tag VLAN ID check box, then enter the S-Tag VLAN ID.

Note: Default VLAN ID is 4095. The same VLAN ID number(s) must be used for both FSP 150CCs.

Step 35 Set the DHCP setting to Disabled.

Step 36 Set the desired RIP setting.


Step 37 Select OK.

Step 38 For management tunnels where ACL is desired: Perform the procedure Section 4.6 Provision ACL Using eVision, on Page 4-47.

Current Status Then

Is the IP address correct? Go to Step 38.


Wait a few minutes and refresh the web browser again. If after several attempts, the IP address still does not appear, contact your System Administrator. When the correct IP address is present, go to Step 38.



TM

Step 39 Verify the WAN management tunnel settings.



Step 41 Select OK.

End of Procedure




TM

4.5 Set Up DHCP Using eVisionPerform the following procedure to enable or disable Dynamic Host Configuration Protocol (DHCP) using the eVision Web Browser Management Tool. (For more information on the eVision Web Browser Management Tool, see Chapter 3, Web Browser Management Tool.)

DHCP can only be enabled on one interface. Because of this, before enabling DHCP on a chosen interface, the user should first ensure it is disabled on all other interfaces. This procedure provides the steps to successfully accomplish this.

If DHCP is disabled on the Management LAN port (labeled MGMT LAN on the rear panel), the Management LAN port default IP address is 192.168.0.2/24.

When a management tunnel is set to a Tunnel Mode of VLAN Based and the Layer 2 Protocol is set to PPP, then DHCP should only be set to the Disabled state.

Procedure

Step 1 If required, use an Ethernet cable to connect your PC to the FSP 150CC Management LAN port and log onto the FSP 150CC via the eVision web browser.



Current Status Then

Are you enabling DHCP on an interface and have not attempted to enable it yet?

Go to Step 3.

Did you receive an error message indicating DCHP is already enabled on another interface?

Proceed to Step 4.

Interface Desired DHCP Setting Then

Management LAN port

Disable DHCP? Go to Step 5.

Enable DHCP? Go to Step 13.

WAN Port



LAN Port





TM


To Disable DHCP on the Management LAN port:



Step 7 Select Local Management Port. The Local Management Port view will appear

Step 8 Observe the current DHCP setting.

Step 9 Enter a right click on Local Management Port and select Edit Facility. The Local Management Port edit view will appear

Step 10 Select the DHCP setting of Disabled.

Step 11 If required, enter the appropriate IP Address and Subnet Mask.

Step 12 Select OK.

End of Procedure

Desired Management Tunnel Then

Did you attempt to enable DHCP on the Management LAN port and you received an error message indicating DHCP is already enabled on another port?

Proceed to Step 19.

Did you attempt to enable DHCP on the WAN Port and you received an error message indicating DHCP is already enabled on another port?

Go to Step 42.

Did you attempt to enable DHCP on a LAN Port and you received an error message indicating DHCP is already enabled on another port?

Go to Step 65.

Current Status Then

Is DHCP set to disabled? End of ProcedureIs DHCP set to enabled? Proceed to Step 9.




TM

To Enable DHCP on the Management LAN port:






Step 18 Select the DHCP setting of Enabled then select OK.


Step 20 Enter a right click on Management Tunnel (WAN) and select Edit Management Tunnel. The WAN Management Tunnel edit view will appear

Step 21 Select the DHCP setting of Disabled then select OK.



End of Procedure

Current Status Then

Is DHCP set to enabled? End of ProcedureIs DHCP set to disabled? Proceed to Step 17.

Current Status Then

Did the change complete? End of ProcedureDid you receive an error message indicating that DHCP is already enabled on the WAN port?

Proceed to Step 20.

Did you receive an error message indicating that DHCP is already enabled on a LAN port?

Go to Step 24.



TM

Step 24 Enter a right click on the Management Tunnel (LAN-x) port in the menu tree as indicated in the error message, and select Edit Management Tunnel. The LAN Management Tunnel edit view will appear




End of Procedure

To Disable DHCP on the WAN Port:



Step 30 Select Management Tunnel (WAN). The WAN Management Tunnel view will appear


Step 32 Enter a right click on Management Tunnel (WAN) and select Edit Facility. The WAN Management Tunnel edit view will appear



Step 35 Select OK.

End of Procedure

Current Status Then





TM

To Enable DHCP on the WAN Port:





Step 40 Enter a right click on Management Tunnel (WAN) and select Edit Facility. The WAN Management Tunnel edit view will appear







End of Procedure

Current Status Then


Current Status Then

Did the change complete? End of ProcedureDid you receive an error message indicating that DHCP is already enabled on the Management LAN port?

Proceed to Step 43.

Did you receive an error message indicating that DHCP is already enabled on a LAN port?

Go to Step 47.



TM

Step 47 Enter a right click on the Management Tunnel (LAN-x) port in the menu tree as indicated in the error message, and select Edit Management Tunnel. The LAN Management Tunnel edit view will appear




End of Procedure

To Disable DHCP on a LAN Port:



Step 53 Select the desired Management Tunnel (LAN-x) port in the menu tree. The LAN Management Tunnel view will appear.


Step 55 Enter a right click on the desired Management Tunnel (LAN-x) port in the menu tree and select Edit Facility. The LAN Management Tunnel edit view will appear.



Step 58 Select OK.

End of Procedure

Current Status Then





TM

To Enable DHCP on a LAN Port:



Step 61 Select the desired Management Tunnel (LAN-x) port in the menu tree. The LAN Management Tunnel view will appear.


Step 63 Enter a right click on the desired Management Tunnel (LAN-x) port in the menu tree and select Edit Facility. The LAN Management Tunnel edit view will appear





Step 68 Enter a right click on the desired Management Tunnel (LAN-x) port in the menu tree and select Edit Management Tunnel. The LAN Management Tunnel edit view will appear.


End of Procedure

Current Status Then


Current Status Then

Did the change complete? End of ProcedureDid you receive an error message indicating that DHCP is already enabled on the Management LAN port?

Proceed to Step 66.

Did you receive an error message indicating that DHCP is already enabled on the WAN port?

Go to Step 70.

Did you receive an error message indicating that DHCP is already enabled on another LAN port?

Go to Step 74.



TM





End of Procedure

Step 74 Enter a right click on the Management Tunnel (LAN-x) port in the menu tree as indicated in the error message, and select Edit Management Tunnel. The LAN Management Tunnel edit view will appear.




End of Procedure




TM

4.6 Provision ACL Using eVisionPerform the following procedure to establish, edit, enable or disable Access Control List (ACL) using the eVision Web Browser Management Tool. (For more information on the eVision Web Browser Management Tool, see Chapter 3, Web Browser Management Tool.)

ACL is a method of providing additional network security. This is accomplished by having a list of up to 10 IP addresses and network masks at the system level that can be individually activated or deactivated. The user can add, delete or edit the IP address and network mask entries, and activate or deactivate each address at any time. The list of active subnetworks can then be enabled or disabled on each communications port on the NID. The system defaults are no entries or active subnetworks in the ACL list, and ACL is disabled on all communication ports.

Note: If ACL is being activated for the first time, and will be applied to the communications port the user is using to access the NID, be sure the subnet used to access the NID is included in the ACL list and activated. Otherwise, at the time ACL is enabled on the communications interface, the user will lose connectivity to the NID.

Procedure

Step 1 If required, connect your PC to the FSP 150CC Management LAN port and log onto the FSP 150CC via the eVision web browser.


Step 3 Right click on the System Name entity (top item in the tree) in the menu tree and select Edit ACL. The Edit ACL screen appears



TM

Step 4 For each Entry ID, enter or edit the desired IP/Network Address and Network Mask.

Step 5 For each Entry ID, use the drop down arrow to select Entry Active: Yes or No.

Step 6 Select OK.

Step 7 To display the data just entered, select the ACL tab in the System Display. The ACL entries are displayed in the ACL table


Interface Desired ACL Setting Then

Management LAN port

Disable ACL? Go to Step 9.

Enable ACL? Go to Step 15.

WAN Port



LAN Port



All Interfaces Set as desired? End of Procedure




TM

To Disable ACL on the Management LAN port:



Step 11 Observe the current ACL setting.


Step 13 Select the ACL Inbound Filtering setting of Disabled and select OK.


To Enable ACL on the Management LAN port:





Step 19 Select the ACL Inbound Filtering setting of Enabled then select OK.


Current Status Then

Is ACL set to disabled? Go to Step 8.

Is ACL set to enabled? Proceed to the next step.

Current Status Then

Is ACL set to enabled? Go to Step 8.

Is ACL set to disabled? Proceed to the next step.



TM

To Disable ACL on the WAN Port:




Step 24 Enter a right click on Management Tunnel (WAN) and select Edit Mgmt Tunnel. The WAN Management Tunnel edit view will appear


Step 26 Go to Step 8

To Enable ACL on the WAN Port:




Step 30 Enter a right click on Management Tunnel (WAN) and select Edit Mgmt Tunnel. The WAN Management Tunnel edit view will appear


Step 32 Go to Step 8

Current Status Then



Current Status Then






TM

To Disable ACL on a LAN Port:


Step 34 Select the desired Management Tunnel (LAN-x) port in the menu tree. The LAN Management Tunnel view will appear


Step 36 Enter a right click on the desired Management Tunnel (LAN-x) port in the menu tree and select Edit Mgmt Tunnel. The LAN Management Tunnel edit view will appear



To Enable ACL on a LAN Port:


Step 40 Select the desired Management Tunnel (LAN-x) port in the menu tree. The LAN Management Tunnel view will appear


Step 42 Enter a right click on the desired Management Tunnel (LAN-x) port in the menu tree and select Edit Mgmt Tunnel. The LAN Management Tunnel edit view will appear



End of Procedure

Current Status Then



Current Status Then





TM



Optical Networking

TM

Chapter 5 Configuration Settings and Technical Data

5.1 OverviewThis chapter provides a summary of system default settings, configuration options, provisioning rules and detailed technical specifications.

The following configuration options and rules tables provide high level option descriptions and valid entries using the eVision web browser management tool. The high level option descriptions provided here assume a good working knowledge of the use of each option, and are intended to be used as a guide to operate, configure and maintain the system. Additional information for each option description can be found in the FSP 150CCf-825 Etherjack OS (EOS) Command Line Interface Handbook and Application Notes for specific features. For more information regarding navigating and using the eVision, see Chapter 3, Web Browser Management Tool.

This chapter provides the following configuration settings information:

• System Default Parameters and Maximum Bandwidth, on Page 5-2

• System Configuration Options and Rules, on Page 5-8

• WAN Configuration Options and Rules, on Page 5-18

• LAN Configuration Options and Rules, on Page 5-21

• CPD Configuration Options and Rules, on Page 5-42

• Loopback Settings, on Page 5-46

• Alarm Attributes, Probable Cause and Trouble Clearing, on Page 5-49

• Performance Monitoring Settings, on Page 5-58

• ESA Options and Rules, on Page 5-72

• Scheduled Ping and ESA Activity Settings, on Page 5-76

• CFM Options and Rules, on Page 5-78


Installation and Operations Manual FSP 150CCf-825Chapter 5 - Configuration Settings and Technical DataRelease 1.2, November 2007 Optical Networking

TM

This chapter also provides the following supporting technical data:

• Connector Pin Assignments, on Page 5-86

• Power, on Page 5-88

• Environmental, on Page 5-89

• Safety, Immunity, Emissions and Compliance, on Page 5-90

• Technical Specifications List by Functional Area, on Page 5-91

• Optical Specifications for FSP 150CC SFPs, on Page 5-96

5.2 System Default Parameters and Maximum BandwidthRefer to Table 5-1 for system default configuration settings. Each functional area and default configuration settings are shown in order, as seen when using the eVision web browser management tool. Refer to Table 5-2, on Page 5-7 for WAN maximum bandwidth per product variant WAN type and encapsulation type, and LAN maximum bandwidth and default LAN CIR/PIR values per product variant. For default TCA settings, refer to Section 5.9 Performance Monitoring Settings, on Page 5-58.

Table 5-1 System Default Configuration Settings

Functional Area

Parameter Default Setting

System

System Name FSP150CCf-825

System Location blank

System Contact blank

Local Management LAN IP Address 192.168.0.2

Local Management LAN Subnet Mask 255.255.255.0

Local Management Default Router None

Proxy ARP Disabled

Time Zone Universal (Coordinated)

Serial Port Enabled

Telnet Enabled

Web Interface Enabled

SNMP Trap Dying Gasp Disabled

Jumbo Frames Enabled

SNTP SNTP Mode Disable

Syslog Host 0.0.0.0


Installation and Operations Manual FSP 150CCf-825Chapter 5 - Configuration Settings and Technical Data


TM

Security Banner

Security Banner

This is a private system. Unauthorized access or use may lead to prosecution.

Ethernet LAN Facility (LAN-1 through LAN-5)

Assigned/Unassigned State All LANs - Disabled

Administrative State Enabled

Port Mode Connection-oriented

EVC Mode Transparent

Circuit Name (Associated LAN number)

Media Type (LAN-5) See Note 1

MTU Size See Note 2

Interface Speed

Auto (LAN 1-4)

Auto 1000 Mb Full Duplex (LAN-5)

Fault Propagation None

Remote Link IDs None Selected

802.3 PAUSE TX Control Disabled

802.3 PAUSE RX Control Disabled

Loopback Configuration None

Ingress CIR 1,024,000 bps

Ingress EIR 0 bps

Ingress CBS 1 bps

Ingress EBS 0 bps

Ingress Buffer Size 128 KB

Egress Rate Limiting Disabled

C-Tag Control Push

C-Tag VLAN ID (Associated LAN number)

C-Tag VLAN Priority 0

C-Tag Match Rx Priority Enabled

S-Tag Control None

Outer Tag EtherType 8100 (hex)

Tagged Frames Enabled

Untagged Frames Enabled

Control Protocol Disposition EFM-OAM Discard

Table 5-1 System Default Configuration Settings (Continued)

Functional Area




TM

E1000 WAN Facility (WAN-1 and WAN-2)

Assigned/Unassigned State WAN-1 Enabled

WAN-2 Disabled


Media Type See Note 1

MTU Size See Note 2

Interface Speed Auto 1000 Mb Full Duplex

Port Shaping Disabled

Port Speed 1000000000

WAN Fault Propagation None

C-Tag EtherType 8100 (hex)

S-Tag EtherType 88a8 (hex)

Loopback Configuration None

Control Protocol Disposition EFM-OAM Peer

PSU-1/PSU-2

Assigned/Unassigned State Enabled


Local Management Port


Interface Speed Auto

DHCP Disabled

ACL Inbound Filtering Disabled

RIP V2 Packets Enabled Disable

LAN Management Tunnel (LAN 1-5)

Management Tunnel Mode None

VLAN ID N/A

Management Tunnel IP Address 0.0.0.0

Management Tunnel Subnet Mask 255.255.255.0

Layer 2 Protocol Ethernet

DHCP Disabled


RIP V2 Packets Enabled Disabled


Functional Area





TM

WAN-1 Management Tunnel

Management Tunnel Mode MAC Based

Management VLAN ID N/A

Management Tunnel IP Address 0.0.0.0

Management Tunnel Subnet Mask 255.255.255.0

Layer 2 Protocol Ethernet

DHCP Enabled


RIP V2 Packets Enabled Disabled

SNMP

Community Names public, sysadmin, private

Access Type read-only (public)read-write (sysadmin,

private)

SNMP User v3RO

User Name v3RO

Authentication Type No authentication

Password N/A

Privacy Type No Privacy

Access Level v3ReadAllGroup

SNMP User v3RW

User Name v3RW


Password N/A


Access Level v3WriteAllGroup

SNMP User super

User Name super


Password N/A


Access Level v3WriteAllGroup

SNMP User nVision

User Name nVision



Functional Area




TM

Note 1: For E1000 WAN and E1000 LAN-5, the default Media Type is set based on whether or not an SFP is present upon power-up. If an SFP is present upon power-up, the Media Type defaults to Fiber; otherwise, it defaults to Copper.

Note 2: For E1000 WAN and E1000 LAN-5, MTU Size is determined by the selection made for Jumbo Frames (at System level). If Jumbo Frames is Enabled, then MTU Size is 9250. If Jumbo Frames is Disabled, then MTU Size is 2000. For LAN 1 through LAN 4, MTU Size is fixed at 2000.

SNMP (Continued)

Password N/A


Access Level nVisionTarget

SNMP User v3super

User Name v3super

Authentication Type MD5

Password v3userpwd


Access Level v3supergroup

SNMP User v3desuser

User Name v3desuser

Authentication Type MD5

Password v3desuserpwd

Privacy Type DES Privacy

Access Level v3desgroup

Users and Security

Login covaro1

Password covaro#1

Privilege Super User

GUI Login Timeout Value 30

Comment Default admin user

Remote Authentication

Authentication Protocol None

Authorization Type PAP

Remote Authentication Servers 1-3 Disabled


Functional Area





TM

Note: All maximum values shown in this table are indicative of a port without a management tunnel, which utilizes 200 Kbps of bandwidth. As default, the W AN is provisioned with a management tunnel and all LANs are provisioned without a management tunnel.

Table 5-2 Maximum WAN/LAN Bandwidth

WAN Type

Max. WAN Bandwidth

Maximum LAN CIR/EIR

E1000 1 Gbps LAN 1-4: 110 Mbps LAN 5: 1 Gbps



TM

5.3 System Configuration Options and RulesRefer to Table 5-3 for System configuration settings and associated rules when using the eVision web browser. Default settings are identified in bold. The following edittable system settings are shown in order, as seen when using the eVision web browser management tool in Configuration mode.

System configuration options and rules consist of the following entities:

• System Name

• Power Supply Units

• Protection Groups

• Communication

• SNMP

• Administration

Table 5-3 System Configuration Settings

Parameter Description / Applicable Rules

Option Settings / Defaults

System Name

System (Edit System)

System Name

This is a text string containing a meaningful description of the FSP 150CC. The System Name must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphens. Maximum length is 64 characters. Upper and lower case characters are allowed.

FSP150CCf-825

System Location

This is a text string entry that should specify where the system is located with enough detail so that operations personnel can easily locate the device. Maximum length is 24 characters.

blank

System Contact

This is a text string entry that should specify the name and contact information of the individual responsible for the administration of the system. Maximum length is 24 characters.

blank

IP Address

Local Management LAN IP Address

Note: If RIP is enabled on an interface and you are changing the IP address, it may take several minutes for RIP to advertise the new IP address. If RIP is enabled on an interface, it is recommended that you perform a reboot after changing the IP address. This will force RIP to advertise the address immediately. Note that this operation should be performed locally, or a static route must be created to the remote in order to make the changes remotely.

192.168.0.2

Subnet Mask The network mask to be used in conjunction with the IP address. 255.255.255.0

Default Router The default router gateway to the internal LAN. blank




TM

Proxy ARP

This option defines if the proxy ARP functionality should be enabled. If two or more ADVA FSP 150CCs are connected via SDCC or Management Tunnel as well as connected to the same LAN, then only one of the NIDs should have the PROXYARP option enabled. Otherwise, there will be multiple ARP responses for a single ARP request for a remote reachable IP Address.

Enabled

Disabled

Date/Time

The date in format: yyyy-mm-dd and the time in format: hh:mm:ss. If Anycast or Unicast is selected for SNTP Mode and an SNTP server has been linked, changing the date and time will have no affect and the SNTP server will override any entry. If a date/time is entered that exceeds the provisioned user GUI timeout value in respect to the current system time, then the user session will time out.

yyyy-mm-dd

hh:mm:ss

Timezone Time zone for the FSP 150CC. See Table 5-4 for available time zone options.

Universal (Coordinated)

Serial Port

Enables or disables RS-232 serial port access to the system.

Enabled

Disabled

Telnet

Enables or disables Telnet (TCP port 23) access to the system.

Enabled

Disabled

Web Interface

Enables or disables web interface (eVision) access to the system.

Enabled

Disabled

SNMP Trap Dying Gasp

Enables or disables dying gasp message via SNMP. When enabled, OAM dying gasp messages are sent on EFM-enabled interfaces.

Enabled

Disabled

Jumbo Frames

Enables or disables Jumbo Frames.

Enabled

Disabled

SNTP (Edit SNTP)

SNTP Mode

Enables or disables SNTP Mode for Simple Network Time Protocol, which is used to synchronize computer clocks in the global Internet.

Selecting Unicast (point-to-point) will send a request to a server IP address and expects a reply indicating the time. Up to two IP addresses can be provisioned when in Unicast mode.

Selecting Anycast (multipoint-to-point) will send a broadcast message to a designated local broadcast group address or multicast group address and expects a reply with their individual unicast IP address. The FSP 150CC will link up with the first reply received.

If Anycast is selected and IP addresses for Unicast operation have been entered, changing the mode to Anycast will override any IP addresses that have been entered.

Anycast

Unicast

Disable

Table 5-3 System Configuration Settings (Continued)Parameter Description /

Applicable RulesOption Settings /

Defaults



TM

Server IP Address

Option to add or delete a Server IP Address.

Add

Delete

IP Address of the SNTP Server. blank

Syslog (Edit Syslog)

Host IP Address of the Syslog Host. Entering an IP address will enable transmission of alarm information to a Syslog Host.

0.0.0.0

Flush AO Buffer? If selected, will clear the Autonomous Output (AO) buffer. The AO buffer is a circular buffer that maintains up to 100 entries.

Deselected

Security Banner (Edit Security Banner)

Security Banner

Defines a custom security banner (a text string of up to 1024 characters in length) which is displayed when a user logs onto the system. This banner is displayed on CLI and web browser logins.

This is a private system.

Unauthorized access or use may lead to prosecution.

Access Control List (Edit ACL for Entry ID 1 through 10)

IP / Network Address

IP Address of the user/subnet allowed to access the NID. Up to 10 user/subnetwork IP addresses can be entered (Entry ID 1-10).

0.0.0.0

Network Mask

Network Mask for the user/subnet IP address allowed to access the NID. Up to 10 user/subnetwork IP address and Network Mask combinations can be entered (Entry ID 1-10).

255.255.255.255

Entry Active?

Each IP Address/Network Mask combination can be active or inactive. The default is No.

YES

NO

Power Supply Units

Power Supply Unit (Edit PSU) (see Note)

Administrative State

Enables or disables PSU-1 and PSU-2.

Enabled

Disabled

Note: PSUs may be placed in the Assigned or Unassigned state by entering a right click on the PSU and selecting Assign or Unassign.

Protection Groups

Link Aggregation Groups (Create or Edit LAG) (see Note)

LAG ID (Create only)

Sets the Link Aggregation Group (LAG) identifier. The only valid option is LAG-1.

LAG-1

LAG Name Text string containing a locally significant name for the Aggregator. Valid entry must be up to 255 characters long and consist of a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not allowed.

LAG-1



Defaults




TM

Administrative State Enables or disables LAG, or places the LAG group in the testing state.

Enabled

Disabled

Testing

LACP Control

Detemines whether or not the Link Aggregation Control Protocol (LACP) is enabled or disabled for the LAG. When disabled, the LAG will ignore LACP frames for the purpose of selecting the “active” link, and will select its “active” link solely upon the status of the two WAN links.

Enabled

Disabled

Primary Member (Create only)

Selects the Primary Member of the LAG (Create LAG only). The only valid selection is E1000[WAN-1]

E1000[WAN-1]

Secondary Member (Create only)

Selects the Secondary Member of the LAG (Create LAG only). The only valid selection is E1000[WAN-2]

E1000[WAN-2]

Actor System Priority

The Actor System Priority value is used to determine which of two Aggregators participating in a LAG assumes the “primary” role. A lower value implies higher priority.

0 to 65,535

32,768

Collector Max Delay

Collector Max Delay (in tens of microseconds) which will be sent to the LAG partner via LACP.

0 to 65,535

50

Link UP/Down Trap

Enables or disables link status notification.

Enabled

Disabled

Note: Only a single WAN LAG can be created. Creating a LAG will automatically provision WAN-2 to the Assigned state. If the creation of a WAN LAG is attempted while one already exists, the creation attempt will be denied. If either WAN port has an active loopback, the WAN LAG creation attempt will be denied. To delete an existing LAG, enter a right click on the LAG entity and select Delete LAG.

LAG-n (Edit Primary/Secondary)

Actor System Priority

The Actor System Priority is used to determine which of two Aggregators participating in a LAG assumes the “primary” role. A lower value implies higher priority.

0 to 65,535

32,768

Actor Port Priority

Actor Port Priority is used to determine which of the ports participating in the LAG has higher priority. A lower value implies higher priority. Default for WAN-1 is 1 and default for WAN-2 is 2.

0-65,535

Actor Port LACP Control

Enables or disables the port from participating as an “Active” port in the LAG.

Enabled

Disabled

Actor LACP Activity

Sets Actor LACP control value to the acrive or passive state. Active

Passive

Actor LACP Timeout

Sets Actor LAG port Actor LACP Timeout control value. Short

Long



Defaults



TM

Partner Administration System ID

Defines the MAC address that uniquely identifies the partner system for the LAG. This information fills automatically when the partner interface is configured and connected.

00:00:00:00:00:00

Partner Administration System Priority

Identifies the Partner Administration System Priority value. An entry of 0 indicates that there is no partner member.

0 to 65,535

32,768

Partner Administration System Key

Defines the LAG port partner’s administration key. 0 to 65,535

1,000

Partner Administration Port Number

Defines the LAG port partner administration port number. Default for WAN-1 is 1 and default for WAN-2 is 2. 0 to 65,535

Partner Administration Port Priority

Defines the priority value of the LAG port partner. Default for WAN-1 is 1 and default for WAN-2 is 2. 0 to 65,535

Partner LACP Activity

Sets Partner LACP control value to the active or passive state. Active

Passive

Partner LACP Timeout

Sets Partner LAG port Actor LACP Timeout control value. Short

Long

Communication

Static Route (Create Static Route) (see Note)

Route Type

Defines whether an interface is used for the static route or if a next hop is to be entered. Select Gateway if a next hop is required, otherwise, select Interface.

Gateway

Interface

Interface

Defines the interface to create a static route. This option is only selectable if Route Type is set to Interface.

local

Wan

Lan-1 to Lan-5

IP Address

Defines the IP address of the destination. The valid values are the IPv4 addresses. The IP address of 0.0.0.0 is reserved for default routes. You can only enter the static default route of 0.0.0.0 if the system default router is 0.0.0.0.

blank

Subnet Mask

Defines the subnet mask for the destination. The valid values are IPv4 mask. If you set the IP address to 0.0.0.0, the only available choice for subnet mask is 0.0.0.0.

blank

Next Hop

Defines the IP address of the next hop for remote destinations. For the routes reachable directly from the specified interface, this value should be 0.0.0.0. This option is only valid if the Route Type is set to Gateway. 0.0.0.0

Metric Metric of the route. This defines the subnet mask for the destination. 0 to 65,5351



Defaults




TM

Advertise Route

Defines whether the static route is to be advertised or not. When selected, the static route will be advertised on every other interface that has RIP enabled.

Deselected

Note: To delete an existing Static Route, select the Communication entity in the Menu Tree and the Static Routes tab, then enter a right click on the desired Static Route and select Delete Static Route.

ARP Entry (Add an ARP Entry) (see Note)

IP Address IP Address to be added to the Address Resolution Protocol entry. blank

MAC Address Media Access Control Address to be added to the ARP entry. blank

Interface Defines the interface to create the ARP entry.

local

Wan

Lan-1 to Lan-5

Note: To delete an existing Static ARP Entry, select the Communication entity in the Menu Tree and the Static ARP Entries tab, then enter a right click on the desired Static ARP Entry and select Delete ARP Entry.

Local Management Port (Edit Facility)


Defines the local management port administrative state.

Enabled

Disabled

Interface Speed

Defines the line rate of the port and whether it is in half duplex or full duplex mode.

Auto

10 MB Full Duplex

100 MB Full Duplex

10 MB Half Duplex

100 MB Half Duplex

DHCP

Defines whether Dynamic Host Configuration Protocol is enabled or disabled. Only one interface may have DHCP enabled. If it is desired to set DHCP for this interface to enabled, then the DHCP setting for all other interfaces must first be set to disabled.

Enabled

Disabled

ACL Inbound Filtering

Allows enabling/disabling of the system level Access Control List (ACL) on this management interface. When enabled, only the permitted IP address(es) provisioned in the system ACL list will be allowed access on this interface.

Enabled

Disabled

RIP V2 Packets Enabled

Allows setting/disabling of Routing Information Protocol V2 packets.

Enable

Disable

LAN and WAN Management Tunnels (Edit Mgmt Tunnel)

See LAN Management Tunnel Configuration Options and Rules, on Page 5-41 and WAN Management Tunnel Configuration Options and Rules, on Page 5-20.



Defaults



TM

SNMP

Add Community (see Note)

Community Name

Entry for the valid Community Name.

publicsysadmin

private

Access Type

Defines the access type.

read-only (public)

read-write (sysdmin)

Note: To delete an existing Community Name, select the SNMP entity in the Menu Tree and the Communities tab, then enter a right click on the desired Community Name and select Delete Entry.

Add Target Address (see Note)

Security Model

Defines the Simple Network Management Protocol (SNMP) security model to be used.

snmpV1

snmpV2c

snmpV3

Credentials

Defines the security credentials for the target IP address. The community name must be entered (see SNMP Add Community) before a credential will appear as a selection in the drop down menu.

public

sysadmin

private

IP Address: Port IP address and port of the SNMP trap receiver. blank:162

Note: Up to 10 Target addresses are supported. To delete an existing Target Address, select the SNMP entity in the Menu Tree and the Target Addresses tab, then enter a right click on the desired Target Address and select Delete Entry.

Add V3 User (see Note)

User Name Entry for a valid user name. Valid entry is 1 to 32 characters. blank

Access Level

Defines the SNMP access level for the new V3 user. The default access level for V3super is super.

super

v3desgroup

v3supergroup

nVisionTarget

v3ReadAllGroup

v3WriteAllGroup

Authentication Defines whether MD5 authentication is used.

No Authentication

MD5 Authentication

Auth. Password

Entry for a valid SNMP password. Valid entry is 6 to 32 characters, no spaces. This option is only applicable if MD5 Authentication is selected. blank

Confirm Auth. Password

Reenter the password entered in the Auth. Password box to confirm the password

blank



Defaults




TM

Privacy Defines whether DES Encryption is used.

No Encryption

DES Encryption

Priv. Password

Entry for a valid DES privacy password. Valid entry is 6 to 32 characters, no spaces. This option is only applicable if DES Encryption is selected. blank

Confirm Priv. Password

Reenter the password entered in the Priv. Password box to confirm the password

blank

Note: To delete an existing V3 user, edit an existing V3 user or edit an existing V3 user password, select the SNMP entity in the Menu Tree and the V3 User Info tab, then enter a right click on the desired V3 User and select Delete Entry, Edit Entry or Change Password, respectively.

Administration

Users (Create New User, Edit User or Edit Password)

User ID

User Identifier (log-in name). The new login name for the user account. Must be at least 6 alphanumeric characters long and no more than 10 alphanumeric characters. The following special characters * # % are allowed. Spaces are not allowed. The default Superuser privilege User-ID Login is covaro1. Only a Superuser may create or delete a user ID. This option is available when selecting Create New User or Edit Password.

blank

Password / New Password / Confirm Password

User login password. A password must be a minimum of 6 characters and a maximum of 10 characters in length. The password must consist of at least 2 non-alpha characters and at least one of the following special characters: * # %. Spaces are not allowed. The default covaro1 user ID password is covaro#1. Only a Superuser may create a password associated with a new User ID. A Superuser may edit any existing password. Any user may edit their own password. This option is available when selecting Create New User or Edit Password.

blank

Privilege

User Security Level. The Superuser assigns security levels for each user and each FSP 150CC. Refer to Section 3.12 Users and Security, on Page 3-81 for more details. Only a Superuser may edit a user privilege level. This option is available when selecting Create New User or Edit User. The default covaro1 user ID privilege level is Super User.

Super User

Maintenance

Provisioning

Retrieve

GUI Login Timeout Value

eVision GUI login timeout for the user ID. Only a Superuser may edit a user GUI login timeout value. This option is available when selecting Create New User or Edit User.

0 (no logout timer) to

99 (minutes)

30 (minutes)

Comment

User comment text string (maximum 64 characters in length). Only a Superuser may edit a user comment. This option is available when selecting Create New User or Edit User.

blank

Remote Authentication (Edit Remote Authentication)

Authentication Protocol Sets the Remote Authentication Protocol type.

None

RADIUS

TACACS+



Defaults



TM

Authentication Type

Remote authentication type. Options available are: Password Authentication Protocol (PAP) or Challenge- Handshake Authentication Protocol (CHAP).

PAP

CHAP

NAS IP Address

The IP address of the Network Access Security server. This option is only applicable if Authentication Protocol is set to RADIUS.

0.0.0.0

Remote Authentication Server (1 to 3) Enable Checkbox

Enables the specific server for operation. Unselected

Remote Authentication Server (1 to 3) Priority

Defines the priority of the server in servicing requests. Multiple servers may have the same priority value. Random ordering will be chosen for those servers with equal priority values.

First

Second

Third

Remote Authentication Server (1 to 3) IP Address

The IP address of the specified Remote Authentication Server. 0.0.0.0

Remote Authentication Server (1 to 3) Port

Defines the UDP port to use when communicating with the Remote Authentication server. Default is 1812 if Authentication Protocol is set to RADIUS or None, default is 49 if Authentication Protocol is set to TACACS+.

0 to 65535

1812 (RADIUS)

49 (TACACS+)

Remote Authentication Server (1 to 3) Timeout

Defines the timeout in seconds after which communication with this server fails. This option is only applicable if Authentication Protocol is set to RADIUS.

1 to 99

3

Remote Authentication Server (1 to 3) Retries

The maximum number of tries that will be attempted with this server. 1 to 99

3

Remote Authentication Server (1 to 3) Secret

Defines the shared secret used for authenticating the FSP 150CC with the Remote Authentication server. Valid entry is a string of up to 64 characters. Blank

Table 5-4 Time Zone Options Alaska Standard International Date Line East Russian Ural

Atlantic Daylight International Date Line West Russian West-Siberian

Atlantic Standard Israeli Daylight Russian Yenisei

Azores Israeli Standard Swedish Summer



Defaults




TM

Baghdad Iran Swedish Winter

Brazil Standard Japan Standard US Central Daylight

British Summer Java US Central Standard

Central Australian Daylight Korean Daylight US Eastern Daylight

Central Australian Standard Korean Standard US Eastern Standard

Central European Middle European US Mountain Daylight

China Coast Middle European Summer US Mountain Standard

Eastern Australian Daylight Middle European Winter US Pacific Daylight

Eastern Australian Standard Newfoundland Daylight US Pacific Standard

Eastern Europe, Russia Zone 1 Newfoundland Standard Universal (Coordinated)

French Summer Newfoundland West Africa

French Winter Nome West Australian Daylight

Greenwich Mean North Sumatra West Australian Standard

Guam Standard New Zealand Daylight Western European

Hawaii Standard New Zealand Standard Yukon Daylight

Indian Standard Russian Volga Yukon Standard

Table 5-4 Time Zone Options (Continued)



TM

5.4 WAN Configuration Options and RulesRefer to Table 5-5 for WAN configuration settings. Also see the following associated options and rules: Section 5.6 CPD Configuration Options and Rules, on Page 5-42 and WAN Management Tunnel Configuration Options and Rules, on Page 5-20. Default settings are identified in bold. The following edittable WAN settings are shown in order, as seen when using the eVision web browser management tool in Configuration mode.

Table 5-5 WAN Configuration Settings Parameter Description /

Applicable RulesOption Settings

WAN Port (Edit Facility)


Defines the WAN facility administrative state. The administrative state controls the generation of alarms and event reports. When an entity is in the administratively enabled state, it is fully operational.

The Administrative State must be set to Testing prior to initiating a loopback or an Etherjack Diagnostic. The setting cannot be changed from the Testing state if the facility is in loopback state. The loopback must be released before changing from the Testing state.

Enabled

Disabled

Testing

Media Type

Defines the WAN interface media type. The default Media Type is set based on whether or not an SFP is present upon power-up. If an SFP is present upon power-up, the Media Type defaults to Fiber; otherwise, it defaults to Copper.

Fiber

Copper

Interface Speed (Copper)

Defines the line rate of the port.

Auto 1000 Mb Full Duplex


100 Mb Full Duplex


10 Mb Full Duplex

Interface Speed (Fiber)

Defines the line rate of the port.


100 Mb Full Duplex

Port Shaping

Port rate shaping at the egress WAN enables oversubscription of client services without exceeding a specified WAN bandwidth.

Enabled

Disabled

Port Speed

Defines the maximum bandwidth on the WAN port. This allows a carrier to force a virtual maximum bandwidth on a WAN port and allows LAN services (EIR) to compete for bandwidth allocation. Setting can not be lower than the cumulative CIR setting for all LAN ports.

0 to 1000000000 1000000000




TM

Note: If the WAN AIS, LOS or RFI alarm notification code is set to Not Reported or Not Alarmed, then the Fault Propagation feature will not activate for that alarm attribute.

Fault Propagation

Defines the LAN Facility Fault Propagation (LFFP) to notify the network (upstream) of LAN port failures. If set to Disable LAN, it will disable all LAN ports when it receives either an RFI, AIS or LOS on the WAN. See Note.

Disable LAN

None

Fault Propagation Delay

Defines the delay before fault propagation is enacted between LAN and WAN ports. This option is only available if Fault Propagation is set to Disable LAN. See Note.

0 to 3600 (sec.)

C-Tag EtherType

Set the C-Tag Ethertype. 8100 (hex.)

S-Tag EtherType

Set the S-Tag Ethertype. 88a8 (hex.)

Table 5-5 WAN Configuration Settings (Continued)Parameter Description /




TM

WAN Management Tunnel Configuration Options and RulesRefer to Table 5-6 for WAN management tunnel configuration settings and associated rules. Default settings are identified in bold. The following edittable WAN management tunnel settings are shown in order, as seen when using the eVision web browser management tool in Configuration mode. Management tunnel is only supported for WAN-1. (See Note 1 through Note 4.)

Note 1: The sum of all management tunnels plus all Control Protocol Disposition (CPD) filters cannot exceed 16.

Note 2: If RIP is enabled on an interface and you are changing the IP address, it may take minutes for RIP to advertise the new IP address. If RIP is enabled on an interface, it is recommended that you perform a system reboot after changing the IP address. This will force RIP to advertise the address immediately. Note that this operation should be performed locally, or a static route must be created to the remote in order to make the changes remotely.

Table 5-6 WAN Management Tunnel Configuration Settings Parameter Description /


(Edit Mgmt Tunnel)

Tunnel Mode

Defines the WAN management tunnel mode. Default for WAN-1 is MAC Based.

None

MAC Based

VLAN Based

VLAN ID Defines the Management VLAN ID. It is used to identify management traffic on the WAN port. This option is only available when Tunnel Mode is set to VLAN Based

1 to 4095

4095

S-Tag VLAN ID

Defines the S-Tag Management VLAN ID. It is used to identify management traffic on the WAN port. This option is only available when Tunnel Mode is set to VLAN Based and the S-Tag VLAN ID checkbox is selected.

1 to 4095

4095

IP Address Defines the IP address for the WAN management tunnel. See Note 2. 0.0.0.0

Subnet Mask Defines the IP subnet mask for the WAN management tunnel. 255.255.255.0

Layer 2 Protocol

Defines the management tunnel encapsulation mode. This option is only available if a Tunnel Mode of None or VLAN Based is selected.

Ethernet

PPP

DHCP


Enabled

Disabled


Allows enabling/disabling of the system level Access Control List (ACL) on this management interface. When enabled, only the permitted IP address(es) provisioned in the system ACL list will be allowed access on this interface.

Enabled

Disabled


Allows setting/disabling of Routing Information Protocol (RIP) V2 packets.

Enable

Disabled




TM

Note 3: A management tunnel utilizes 256 Kbps of bandwidth. As default, the WAN is provisioned with a MAC based management tunnel with DHCP enabled.

Note 4: If LAG is created, a management tunnel can only be created/edited/deleted on WAN-1.

5.5 LAN Configuration Options and RulesRefer to one of the following for LAN service configuration options and rules:

• Section 5.5.1 Transparent LAN Service Provisioning for Transparent LAN configuration settings and associated rules.

• Section 5.5.2 Connection-oriented Flow VLAN Service Provisioning, on Page 5-26

• Section 5.5.3 Connection-less Flow VLAN Service Provisioning, on Page 5-35

Also see the following associated options and rules: Section 5.6 CPD Configuration Options and Rules, on Page 5-42 and LAN Management Tunnel Configuration Options and Rules, on Page 5-41.

5.5.1 Transparent LAN Service ProvisioningRefer to the following for provisioning a port in Transparent LAN EVC Mode. It is recommended that you review the following configuration options and rules and pre-determine the desired provisioning details prior to making any provisioning changes to a LAN port. Ports may be placed in the Assigned or Unassigned state by entering a right click on the LAN port and selecting Assign or Unassign. Default settings are identified in bold.

If the Port is currently configured in Connection-oriented Flow VLAN mode: the LAN port may be converted to Transparent LAN Service by entering a right click on the LAN port and selecting CO Transparent (Connection-oriented Transparent).

If the Port is currently configured in Connection-less Flow VLAN mode: the LAN port may be converted to Transparent LAN Service by entering a right click on the LAN port and selecting CO Mode (Connection-oriented Mode).

WARNING — Changing EVC Mode on a port will drop all traffic on the port, including Management Tunnel connectivity and Maintenance End Points.



TM

Table 5-7 Configuration Settings for Transparent LAN Service Parameter Description /


(Edit Facility)

Circuit Name

Assigns a circuit name to the port. Up to 64 characters are allowed. Allowed characters include: a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not allowed.

LAN-1 through LAN-5


Defines the LAN facility administrative state. The administrative state controls the generation of alarms and event reports. When an entity is in the disabled state, alarms are squelched. When an entity is in the administratively enabled state, it is fully operational.


Enabled

Disabled

Testing

Media Type (LAN 5)

Define the physical interface operating mode for an Ethernet LAN interface. The default Media Type is set based on whether or not an SFP is present upon power-up. If an SFP is present upon power-up, the Media Type defaults to Fiber; otherwise, it defaults to Copper.

Copper

Fiber

Interface Speed LAN 1 to 5 (Copper)

Defines the line rate of the port and whether it is in half duplex or full duplex mode. When Media Type is set to Copper, all of the options to the right are available and the default setting is Auto.

Auto (Copper)


Auto 100 Mb Half Duplex

100 Mb Full Duplex

100 Mb Half Duplex



10 Mb Full Duplex

10 Mb Half Duplex

Interface Speed LAN 5 (Copper)

(See above.) Auto 1000 Mb Full Duplex

Interface Speed LAN 5 (Fiber)

(See above.)

When Media Type is set to Fiber, options available are Auto 1000 Mb Full Duplex (default) and Auto 100 Mb Full Duplex only.

When Media Type is set to Fiber, Interface Speed can only be changed if the port Assigned/Unassigned State is set to Disabled.

If changing Media Type from Copper to Fiber and setting the Interface Speed to 100 Mb Full Duplex, the changes can only be made if the port Assigned/Unassigned State is set to Disabled.

Auto 1000 Mb Full Duplex (Fiber)





TM

Fault Propagation

Defines the LAN Facility Fault Propagation (LFFP) to notify the network (upstream) of LAN port failures. All LAN ports must be set consistently, otherwise individual LAN port(s) may be set to None.

None

Disable WAN Port

Send EFM RLD Msg


Defines the delay before fault propagation is enacted between LAN and WAN ports. This option is only available if Fault Propagation is set to anything other than None.

0 to 3600 (sec.)

Local Link ID

Defines the Local Link ID for the LAN port to indicate which port is faulted. Local Link ID is only provisionable if Fault Propagation is set to Send EFM RLD Msg.

1 to 5

N/A

Remote Link IDs

Allows selection of the Remote Link ID(s) to be used for matching against the Link ID in the EFM RLD (Remote Link Down) message. The same Remote Link ID number may be set for multiple LANs, if desired.

1 to 5

N/A

802.3 PAUSE TX Control

Defines the transmit flow control for the facility.

Enabled

Disabled

802.3 PAUSE RX Control

Defines the receive flow control for the facility. Enabled

Disabled

Ingress CIR

Defines the Ingress Committed Information Rate (CIR) for this port, in bps. Entry of commas are allowed.

If LAN port speed < WAN port speed, then an Ingress CIR value of 0 to 1.10 times the speed of the LAN may be entered (this value is designated as LPS* below). Ingress CIR may not exceed the speed of the WAN port.

Where Ingress CIR + Ingress EIR = Ingress PIR (Peak Information Rate): Ingress PIR must be <= LPS* or the WAN port speed, whichever is less.

The combined Ingress CIR of all transparent service/flows plus the size of the WAN management tunnel (if present) and/or WAN EFM-OAM (if enabled) cannot exceed the speed of the WAN. (WAN management tunnel utilizes 256 Kbps. WAN EFM-OAM, if enabled, utilizes 64 Kbps. If both a WAN management tunnel is provisioned and WAN EFM-OAM is enabled, 256 Kbps is utilized.)

0 to 110 Mbps(LAN 1 to 4)

1,024,000 bps

0 to 1 Gbps(LAN 5)

1,024,000 bps

Ingress EIR

Defines the Ingress Excess Information Rate (EIR) for this port, in bps. Entry of commas are allowed.

If Ingress CIR is set to 0, then an Ingress EIR value of 64 Kbps or greater must be entered (if a value of 1 bps through a value less than 64 Kbps is entered, then the value will automatically be rounded up to 64 Kbps).

(See above definition of LPS* and PIR): Ingress PIR must be <= LPS* or the WAN port speed, whichever is less.


0 bps

0 to 1 Gbps(LAN 5)

0 bps

Ingress CBS Defines the Ingress Committed Burst Size (CBS) for this port, in Kilobytes. Entry of comma is allowed.

1 to 1,000 (KB)

Ingress EBS Defines the Ingress Excess Burst Size (EBS) for this port, in Kilobytes. Entry of comma is allowed.

0 to 1,000 (KB)

Table 5-7 Configuration Settings for Transparent LAN Service (Continued)Parameter Description /




TM

Ingress Buffer Size

Defines the Ingress buffer size for the normal latency queues, in Kilobytes. Entry of comma is allowed.

64 to 33,480 (KB)

128 (KB)

Egress Rate Limiting

Enables or disables Egress Rate Limiting. Egress limiting allows control over the bandwidth of egress traffic toward the customer LAN port, and is set independently from Ingress Rate Limiting. If set to the Enabled state, Egress CIR, EIR, CBS, EBS and Buffer Size entries are allowed.

Disabled

Enabled

Egress CIR

Defines the Egress Committed Information Rate (CIR) for this port, in bps. Entry of commas are allowed. This option is only available if Egress Rate Limiting is set to the Enabled state.

Egress CIR must not exceed the speed of the LAN.


0 to 1 Gbps(LAN 5)

Egress EIR

Defines the Egress Excess Information Rate (EIR) for this port, in bps. Entries of commas are allowed. This option is only available if Egress Rate Limiting is set to the Enabled state.

If Egress CIR is set to 0, then an Egress EIR value of 64 Kbps or greater must be entered (if a value of 1 bps through a value less than 64 Kbps is entered, then the value will automatically be rounded up to 64 Kbps).

Where Egress CIR + Egress EIR = Egress PIR (Peak Information Rate): Egress PIR must not exceed the speed of the LAN.


0 to 1 Gbps(LAN 5)

Egress CBS

Defines the Egress Committed Burst Size (CBS) for this port, in Kilobytes. Entry of comma is allowed. This option is only available if Egress Rate Limiting is set to the Enabled state.

1 to 1,000 (KB)

Egress EBS

Defines the Egress Excess Burst Size (EBS) for this port, in Kilobytes. Entry of comma isallowed. This option is only available if Egress Rate Limiting is set to the Enabled state.

0 to 1,000 (KB)

Egress Buffer Size

Defines the Egress buffer size for the normal latency queues, in Kilobytes. Entry of comma is allowed. This option is only available if Egress Rate Limiting is set to the Enabled state.

64 to 33,480 (KB)

C-Tag Control

Defines whether the C (Customer) Tag VLAN ID / VLAN Priority should be PUSHed or no action taken.

If more than one LAN port is to be used in the system, Push must be selected. If C-Tag Control is set to None, only one LAN port may be used in the system.

If C-Tag Control is set to None, then C-Tag VLAN ID and C-Tag VLAN Priority cannot be entered.

Push

None






TM

C-Tag VLAN ID

Defines the C-Tag VLAN ID that will be PUSHed. This option is only available if C- Tag Control is set to Push.

All C-Tag and S-Tag VLAN ID-Priority values must not conflict on the WAN port. (For example: A service with C-Tag PUSH 100-0, S-Tag PUSH 100-0 will conflict with another service with the same C-Tag and S-Tag. A service with C-Tag PUSH 100-0, S-Tag None will conflict with another service with C-Tag None, S-Tag PUSH 100-0. A TLS service with C-Tag PUSH 100-0, S-Tag NONE will conflict with a Flow with VLAN Member 100-0, C-Tag NONE and S-Tag NONE.)

1 to 4095

LAN-1 default is 1

LAN-2 default is 2

LAN-3 default is 3

LAN-4 default is 4

LAN-5 default is 5

C-Tag VLAN Priority

Defines the C-Tag VLAN Priority that will be PUSHed. This option is only allowed if C-Tag Control is set to Push.

All C-Tag and S-Tag VLAN ID-Priority values must not conflict on the WAN port (see C-Tag VLAN ID).

0 to 7

C-Tag Match Rx Priority

Enable or disable matching of C-Tag priority to Receive priority. It specifies whether the C-Tag priority will be used or ignored for traffic in the egress direction. This option is only allowed if C-Tag Control is set to Push.

Enabled

Disabled

S-Tag Control

Defines whether the S (Service) Tag VLAN ID / VLAN Priority should be PUSHed or no action taken.

If S-Tag Control is set to None, S-Tag VLAN ID and C-Tag VLAN Priority cannot be entered.

Push

None

S-Tag VLAN ID

Defines the S-Tag VLAN ID that will be PUSHed. This option is only applicable if S-Tag Control is set to Push.


1 to 4095

LAN-1 default is 1

LAN-2 default is 2

LAN-3 default is 3

LAN-4 default is 4

LAN-5 default is 5

S-Tag VLAN Priority

Defines the S-Tag VLAN Priority that will be PUSHed. This option is only applicable if S-Tag Control is set to Push.

All C-Tag and S-Tag VLAN ID-Priority values must not conflict on the WAN port (see S-Tag VLAN ID).

0 to 7

Outer Tag EtherType

Defines the Stacked Ethertype to be used to inter-operate with Queue-in-Queue frames with other vendors.

8100 (hex)

Tagged Frames

Enable or disable Tagged Frames.

Enabled

Disabled

Untagged Frames

Enable or disable Untagged Frames.

Enabled

Disabled





TM

5.5.2 Connection-oriented Flow VLAN Service ProvisioningRefer to the following for provisioning a Connection-oriented Flow-VLAN service. It is recommended that you review the following configuration options and rules and pre-determine the desired provisioning details prior to making any provisioning changes. Ports may be placed in the Assigned or Unassigned state by entering a right click on the LAN port and selecting Assign or Unassign. Default settings are identified in bold.

If the Port is currently configured in Transparent LAN EVC mode: the LAN port may be converted to Connection-oriented Flow-VLAN service by entering a right click on the LAN port and selecting CO Flow VLAN (Connection-oriented Flow VLAN).

If the Port is currently configured in Connection-less Flow VLAN mode: the LAN port may be converted to Connection-oriented Flow-VLAN service by entering a right click on the LAN port and selecting CO Mode (Connection-oriented Mode), then entering a right click on the LAN port and selecting CO Flow VLAN (Connection-oriented Flow VLAN).


Table 5-8 Configuration Settings for Connection-oriented Flow VLAN Service Parameter Description /


E100 LAN Port (Edit Facility)

Circuit Name


LAN-1 through LAN-5




Enabled

Disabled

Testing

Media Type (LAN 5)

Define the physical interface operating mode for an Ethernet LAN interface. The default Media Type is set based on whether or not an SFP is present upon power-up. If an SFP is present upon power-up, the Media Type defaults to Fiber; otherwise, it defaults to Copper.

Copper

Fiber




TM

Interface Speed

LAN 1 to 5 (Copper)


Auto (Copper)



100 Mb Full Duplex

100 Mb Half Duplex



10 Mb Full Duplex

10 Mb Half Duplex

Interface Speed

LAN 5 (Copper)

(See above.)


Interface Speed

LAN 5 (Fiber)

(See above.)





(Fiber)


Fault Propagation


None

Disable WAN Port

Send EFM RLD Msg



0 to 3600 (sec.)

Local Link ID


1 to 5

N/A

Remote Link IDs


1 to 5

N/A

Table 5-8 Configuration Settings for Connection-oriented Flow VLAN Service (Continued)Parameter Description /




TM

Outer Tag EtherType


8100 (hex)

Acceptable Frame Policy

Defines the ingress behavior at the port.

All

VLAN

Port VLAN ID

Defines the Port VLAN ID. The format is VID-PRIO. The valid values for VID are 1 to 4095 and valid values for PRIO are 0 to 7. The default value is 1-0. If only the VID portion is entered, PRIO will default to 0. If the VID portion is not entered, PRIO also cannot be specified. This option is only valid when Acceptable Frame Policy is set to All.

[1 to 4095]-[0 to 7]

1-0

Egress VLAN Trunking

Defines the egress behavior for the port. Setting this option to Enabled delivers VLAN tagged frames to the CPE. Setting this option to Disabled delivers untagged frames to the CPE.

Enabled

Disabled

Ingress PUSH Port VLAN ID

Sets Push port VLAN ID on Ingress.When Enabled, the Port VLAN ID is PUSHed onto the frame. When Disabled, no tags are PUSHEed onto the frame (i.e., it stays untagged).

Enabled

Disabled

Egress POP Port VLAN ID

Sets Pop port VLAN ID on egress frames. If Ingress PUSH Port VLAN ID is Enabled, it may be desired that the PVID may be POPed.

Enabled

Disabled

Priority Map Mode

Defines the Priority Map Mode. It identifies the lookup criteria for the priority mapping table. This table is used to perform priority based lookup (to determine low and normal latency) and/or to change the priority value.

Priority Map Mode must be set to anything other than Off in order to enable multi-COS on this LAN. If Priority Map Mode is set to anything other than OFF, a Priority Mapping Table is created. See Default Priority Mapping Tables, on Page 5-34 for default Priority Map settings.

Off

TOS

DSCP

802.1P

Priority VLAN ID

Defines the Priority VLAN ID. This is the VLAN ID used to replace the NULL VLAN ID of the priority tagged frames. If the value is not specified by the user, the default will be the VID part of the Port VLAN ID attribute. This option is only valid when Acceptable Frame Policy is set to VLAN.

0 to 4095

1

Untagged Frames


Enabled

Disabled

Priority Map (Edit Priority)

Note: Selecting Edit Priority option is only selectable (by entering a right click on the LAN entity) if a Priority Map Mode selection other than Off is made for the LAN facility, and a Priority Map Index Selection is made.

Priority Map Index Selection

The following ranges of Indexes are: 0...7 if Priority Map Mode is set to 802.1P or TOS, 0...63 if Priority Map Mode is set to DSCP.

Multiple Indexes can be selected by selecting the first desired Index and then entering Control+Click for each additional Index. To select a contiguous set of Indexes, select the first desired Index, then enter a Shift+click on the last desired Index in the range of Indexes. If multiple indexes are selected, they will all be changed to the same PRIOCTL, Priority and Latency options when they are selected.

0 to 7 (802.1P or TOS)

0 to 63 (DSCP)






TM

X-Tag PRIOCTL

X-Tag Priority Control. This parameter controls the behavior of the Priority portion of the frame. If NONE is selected, the incoming priority bits are left unchanged. If SWAP is selected, the incoming priority bits are changed by the value specified in the X-Tag Priority parameter.

None

Swap

X-Tag Priority This parameter defines the new priority bits to be used. Valid only if X-Tag PRIOCTL is set to Swap.

0 to 7

Policer COS Class Of Service (COS) Policer. Allows the incoming traffic to be steered to the appropriate EVC Ingress Policer.

0 to 7

Egress QoS Queue 0 to 7 Settings (Edit Egress Queue)

Buffer Size

Defines the buffer size for the Egress QoS queues, in Kilobytes. 64 to 1024 (KB)

128 (KB)

Flow (Create Flow or Edit Flow)

Note: Create Flow is only applicable if the Port is in the Assigned state.

Flow ID (Create Flow only)

Defines the Flow Identifier (FID) for this flow. Up to 400 flows can be created for the system. Each of the four 10/100 Ethernet Client interfaces can support a maximum of 100 flows. The LAN-5 1 Gb Ethernet Client interface can support a maximum of 400 flows.

Note: Every assigned LAN port reduces the maximum number of available flows by 1.

FID-1 to FID-400

Circuit Name Assigns a circuit name to the flow. Blank

Type (Create Flow only)

Defines the flow type. If Default is selected, no VLAN Member value is supplied, and this FID becomes the Default FID for the port, i.e., all the VLAN IDs that don’t belong to any other FID on the port belongs to this FID. If Default is selected and Transport Tag Control is set to None, no other FIDs can be added to this port. If Regular is selected, then individual VLAN Members can be added.

Flow Type cannot be edited. To change the Flow Type, the FID must be deleted and then re-created with the new Flow Type.

Default

Regular

Untagged Frames Supported


Enabled

Disabled

C-Tag Control

Defines whether the C (Customer) Tag VLAN ID / VLAN Priority should be PUSHed, Swapped or no action taken. If Swap VID is selected, only the VLAN ID (12 bits) are swapped with the specified C-Tag VLAN ID. If Swap Tag is selected, both the VLAN ID and Priority (15 bits) are swapped. If Push VID is selected, only the VLAN ID (12 bits) is PUSHed - the Priority is copied from the incoming tag’s Priority.

If flow Type is set to Default and C-Tag Control is set to None, no other FIDs can be added to this port. If C-Tag Control is set to None, then C-Tag VLAN ID cannot be entered. If C-Tag Control is set to None, Swap VID or Push VID, C-Tag VLAN Priority cannot be entered.

Push

Swap VID

Swap Tag

Push VID

None





TM

C-Tag VLAN ID

Defines the C-Tag VLAN ID. If C-Tag Control is set to None, then C-Tag VLAN ID cannot be entered.


1 to 4095

C-Tag VLAN Priority

Defines the C-Tag VLAN Priority. If C-Tag Control is set to None, Swap VID or Push VID, C-Tag VLAN Priority cannot be entered.


0 to 7



Enabled

Disabled

S-Tag Control

Defines whether the S (Service) Tag VLAN ID / VLAN Priority should be PUSHed or no action taken. If S-Tag Control is set to None, S-Tag VLAN ID and S-Tag VLAN Priority cannot be entered.

Push

None

S-Tag VLAN ID

Defines the Transport VLAN ID. If S-Tag Control is set to None, S-Tag VLAN ID cannot be entered.


1 to 4095

S-Tag VLAN Priority

Defines the S-Tag VLAN Priority. If S-Tag Control is set to None, S-Tag VLAN Priority cannot be entered.


0 to 7


Enables or disables Egress Rate Limiting. Egress limiting allows control over the bandwidth of egress traffic toward the customer LAN port, and is set independently from Ingress Rate Limiting. If set to the Enabled state, Egress CIR, EIR, CBS and EBS entries are allowed.

Disabled

Enabled

Multi COS

(Create Flow only)

Enables or Disables Multi Class Of Service (COS). If set to the Disabled, one Ingress Policer and one Egress Policer are provisionable. If set to the Enabled state, up to 8 Ingress Policers and 8 Egress Policers may be provisioned. Multi COS can only be set to the Enabled state if Priority Map Mode is set to anything other than OFF for the facility. This option is only available during Flow creation and cannot be edited. If it is desired to edit an existing Flow, the Flow must be deleted and then recreated with the Multi COS change.

Enabled

Disabled






TM

Ingress (and Egress) Policer 0 to 7

If Multi COS is set to the Enabled state, then up to 8 Ingress Policers and 8 Egress Policers are allowed. To activate Policer entry, select the desired Policer (0 to 7). A maximum of 100 policing flows may be created per 10/100 Ethernet LAN port (LAN-1 to LAN-4). A maximum of 400 policing flows may be created for the 1 G Ethernet LAN port (LAN-5). A maximum of 400 policing flows may be created per system.

0 to 7

Ingress CIR

Defines the Ingress Committed Information Rate (CIR) for this flow, in bps. Entry of commas are allowed. If Multi COS is set to the Disabled state, one Ingress CIR setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Ingress CIR Policer Settings are allowed.

Defines the Ingress Committed Information Rate (CIR) for this port, in bps. Entry of commas are allowed.

If LAN port speed < WAN port speed, then the sum of all Ingress CIRs on the LAN port may be <= to 1.10 times the speed of the LAN (this value is designated as LPS below). The sum of all Ingress CIRs on the LAN port may not exceed the speed of the WAN port.

Where the sum of all Ingress CIRs on the LAN port + the sum of all Ingress EIRs on the LAN port = Ingress PIR (Peak Information Rate) for the LAN port: Ingress PIR must be <= LPS or the WAN port speed, whichever is less. The sum of Ingress PIRs of all ports/flows/policers must not exceed the speed of the WAN.



1,024,000 bps

0 to 1 Gbps(LAN 5)

1,024,000 bps

Ingress EIR

Defines the Ingress Excess Information Rate (EIR) for this port, in bps. Entry of commas are allowed. If Ingress CIR is set to 0, then an Ingress EIR value of 64 Kbps or greater must be entered (if a value of 1 bps through a value less than 64 Kbps is entered, then the value will automatically be rounded up to 64 Kbps).

If Multi COS is set to the Disabled state, one Ingress EIR setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Ingress EIR Policer Settings are allowed.

(See above definition of LPS and Ingress PIR): Ingress PIR must be <= LPS or the WAN port speed, whichever is less. The sum of Ingress PIRs of all ports/flows/policers must not exceed the speed of the WAN.


0 bps

0 to 1 Gbps(LAN 5)

0 bps

Ingress CBS

Defines the Ingress Committed Burst Size (CBS) for this flow, in Kilobytes. Entry of comma is allowed. If Multi COS is set to the Disabled state, one Ingress CBS setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Ingress CBS Policer Settings are allowed. CBS cannot be less than CIR in bytes/millisecond.

1 to 1,000 (KB)





TM

Ingress EBS

Defines the Ingress Excess Burst Size (EBS) for this flow, in Kilobytes. Entry of comma is allowed. If Multi COS is set to the Disabled state, one Ingress EBS setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Ingress EBS Policer Settings are allowed. EBS cannot be less than CIR in bytes/millisecond. EBS cannot be less than EIR in bytes/millisecond.

0 to 1,000 (KB)

QoS Queue

Defines the Quality of Service (QoS) Queue associated with the selected Policer. This option is not available if Multi COS is set to the Disabled state. If Multi COS is set to the Enabled state, then a specific QoS Queue may be associated with each selected Policer. The same Queue may be associated with more than one Policer. up to 8 Queues may be provisioned per port.

Queue 0 to 7

Associated Policer number

Ingress Buffer Size

Defines the Ingress buffer size for the normal latency queues, in Kilobytes. This resource is allocated in 64 K Byte segments. User input is allocated in 64 K Byte increments - rounded up to the next closest segment. Buffer Size cannot be less than CBS. Entry of comma is allowed. This option is only available if Multi COS is set to the Disabled state.

64 to 33,480 (KB)

128 (KB)

QoS Queue Ingress Buffer Size

Defines the Ingress buffer size for the selected Policer QoS queues, in Kilobytes. This resource is allocated in 64 K Byte segments. User input is allocated in 64 K Byte increments - rounded up to the next closest segment. Buffer Size cannot be less than CBS. Entry of comma is allowed. If Multi COS is set to the Enabled state, then up to 8 QoS Queue settings are allowed per port.

64 to 33,480 (KB)

128 (KB)

Egress CIR

Defines the Egress Committed Information Rate (CIR) for this flow, in bps. Entry of decimal is allowed. Entry of commas are not allowed. If Multi COS is set to the Disabled state, one Egress CIR setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Egress CIR Policer Settings are allowed.

The combined CIR of all transparent service/flows/policers plus the size of the WAN management tunnel (256 Kbps, if present) cannot exceed the maximum speed of the WAN.


0 to 1 Gbps(LAN 5)

Egress EIR

Defines the Egress Excess Information Rate (EIR) for this flow, in bps. Entry of commas are allowed. If Multi COS is set to the Disabled state, one Egress EIR setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Egress EIR Policer Settings are allowed.

Where Egress CIR + Egress EIR = Egress PIR (Peak Information Rate) for the Port: Egress PIR must not exceed the speed of the LAN Port. If Multi COS is set to the Enabled state for any flow on the LAN port, then only the maximum EIR of all the provisioned Policers on a given FID is used for this calculation.


0 to 1 Gbps(LAN 5)

Egress CBS

Defines the Egress Committed Burst Size (CBS) for this flow, in Kilobytes. Entry of comma is allowed. If Multi COS is set to the Disabled state, one Egress CBS setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Egress CBS Policer Settings are allowed. CBS cannot be less than CIR in bytes/millisecond.

1 to 1,000 (KB)






TM

Egress EBS

Defines the Egress Excess Burst Size (EBS) for this flow, in Kilobytes. Entry of comma is allowed. If Multi COS is set to the Disabled state, one Egress EBS setting is allowed for the FID. If Multi COS is set to the Enabled state, then up to 8 Egress EBS Policer Settings are allowed. EBS cannot be less than CIR in bytes/millisecond. EBS cannot be less than EIR in bytes/millisecond.

0 to 1,000 (KB)

VLAN Members

Defines the frames that belong to the flow. Frames are classified based on the VLAN tag and the membership is specified as a list of VLAN IDs. The VLAN member format is VLAN ID-Priority. The valid values for VLAN ID are 0 to 4095. Valid values for Priority are “null” or 0 to 7.

If the Priority value is not specified, all the priority values for that VLAN ID belongs to the FID. A maximum of 64 members can be defined for a given FID. A maximum of 4,000 VLAN members can be created per system. If no value is supplied, this FID becomes the default FID for the port, i.e., all the VLAN IDs that don’t belong to any other FID on the port belongs to this FID.

To add a VLAN member, enter the valid VLAN ID-Priority number and select Add. To delete a VLAN member, select the VLAN ID-Priority number and select Remove.

If Type is set to Default, no VLANMEMBER value can be supplied, and this FID becomes the Default FID for the port, i.e., all the VLAN IDs that don’t belong to any other FID on the port belongs to this FID. If Type is set to Regular, then individual VLANMEMBERs can be entered.

VLAN ID portion of

VLAN ID-Priority:

0 to 4095

N/A

Priority portion of VLAN ID-Priority:

0 to 7

N/A





TM

Default Priority Mapping TablesThe Table 5-9, Table 5-10 and Table 5-11 identify the default Priority Mapping Tables for 802.1P, TOS and DSCP.

Table 5-9 8021P Default Priority Mapping TableIndex PRIO Control New Priority

BitsLatency

0 None N/A NRML

1 None N/A NRML

2 None N/A NRML

3 None N/A NRML

4 None N/A NRML

5 None N/A LO

6 None N/A LO

7 None N/A LO

Table 5-10 TOS Default Priority Mapping Table Index PRIO Control New Priority

BitsLatency

0 None N/A NRML

1 None N/A NRML

2 None N/A NRML

3 None N/A NRML

4 None N/A NRML

5 None N/A LO

6 None N/A LO

7 None N/A LO

Table 5-11 DSCP Default Priority Mapping TableIndex PRIO Control New Priority

BitsLatency

0 to 31 None N/A NRML

32 to 63 None N/A LO




TM

5.5.3 Connection-less Flow VLAN Service ProvisioningRefer to the following for provisioning a Connection-less Flow-VLAN service. It is recommended that you review the following configuration options and rules and pre-determine the desired provisioning details prior to making any provisioning changes. Ports may be placed in the Assigned or Unassigned state by entering a right click on the LAN port and selecting Assign or Unassign. Default settings are identified in bold.

If the Port is currently configured in Transparent LAN EVC mode: the LAN port may be converted to Connection-less Flow-VLAN service by entering a right click on the LAN port and selecting CL Mode (Connection-less Flow VLAN).

If the Port is currently configured in Connection-oriented Flow VLAN mode: the LAN port may be converted to Connection-less Flow-VLAN service by entering a right click on the LAN port and selecting CO Transparent (Connection-oriented Transparent), then entering a right click on the LAN port and selecting CL Mode (Connection-less Flow VLAN).


Once a Connection-less service has been created, an option to Flush MAC Entry is available flush the MAC bridge table learned entries.

Table 5-12 Configuration Settings for Connection-less Flow VLAN Service Parameter Description /


E100 LAN Port (Edit Facility)

Circuit Name


LAN-1 through LAN-5




Enabled

Disabled

Testing

Age Time

Forwarding entry will be removed from the forwarding table after an inactivity time represented by this entry.

10 to 1000000 sec.

300 sec.

MAC Table Size

MAC forwarding table size. 1 to 4095



TM

MAC Table Full

Indicates the behavior of the bridge once the forwarding table is full.

Block

Flood

Media Type (LAN 5)

Defines the physical interface operating mode for an Ethernet LAN interface. The default Media Type is set based on whether or not an SFP is present upon power-up. If an SFP is present upon power-up, the Media Type defaults to Fiber; otherwise, it defaults to Copper.

Copper

Fiber

Interface Speed

LAN 1 to 5 (Copper)


Auto (Copper)



100 Mb Full Duplex

100 Mb Half Duplex



10 Mb Full Duplex

10 Mb Half Duplex

Interface Speed

LAN 5 (Copper)

(See above.) Auto 1000 Mb Full

Duplex

Interface Speed

LAN 5 (Fiber)

(See above.)





(Fiber)


Fault Propagation


None

Disable WAN Port

Send EFM RLD Msg



0 to 3600 (sec.)

Table 5-12 Configuration Settings for Connection-less Flow VLAN Service (Continued)Parameter Description /





TM

Local Link ID


1 to 5

N/A

Remote Link IDs


1 to 5

N/A

Outer Tag EtherType


8100 (hex)

Egress QoS Queue 0 to 7 Settings (Edit Egress Queue)

Buffer Size

Defines the buffer size for the Egress QoS queues, in Kilobytes.

64 to 1024 (KB)

128 (KB)

Flow (Create Flow or Edit Flow)

Note: Create Flow is only applicable if the Port is in the Assigned state.

Flow ID (Create Flow only)

Defines the Flow Identifier (FID) for this flow. Up to 400 flows can be created for the system. Each of the four 10/100 Ethernet Client interfaces can support a maximum of 100 flows. The LAN-5 1 Gb Ethernet Client interface can support a maximum of 400 flows.

Note: Every assigned LAN port reduces the maximum number of available flows by 1.

FID-1 to FID-400

Circuit Name Assigns a circuit name to the flow. Default circuit name is the Flow ID. Blank

C-Tag Control

Defines whether the C (Customer) Tag VLAN ID / VLAN Priority should be PUSHed, Swapped or no action taken. If Swap VID is selected, only the VLAN ID (12 bits) are swapped with the specified C-Tag VLAN ID. If Swap Tag is selected, both the VLAN ID and Priority (15 bits) are swapped. If Push VID is selected, only the VLAN ID (12 bits) is PUSHed - the Priority is copied from the incoming tag’s Priority.

If flow Type is set to Default and C-Tag Control is set to None, no other FIDs can be added to this port. If C-Tag Control is set to None, then C-Tag VLAN ID cannot be entered. If C-Tag Control is set to None, Swap VID or Push VID, C-Tag VLAN Priority cannot be entered.

Push

Swap VID

Swap Tag

Push VID

None

C-Tag VLAN ID

Defines the C-Tag VLAN ID. If C-Tag Control is set to None, then C-Tag VLAN ID cannot be entered.


1 to 4095





TM

C-Tag VLAN Priority

Defines the C-Tag VLAN Priority. If C-Tag Control is set to None, Swap VID or Push VID, C-Tag VLAN Priority cannot be entered.


0 to 7



Enabled

Disabled

S-Tag Control

Defines the behavior of the S-Tag VLAN ID specified. If S-Tag Control is set to None, S-Tag VLAN ID and S-Tag VLAN Priority cannot be entered.

Push

None

S-Tag VLAN ID

Defines whether the S (Service) Tag VLAN ID / VLAN Priority should be PUSHed or no action taken. If S-Tag Control is set to None, S-Tag VLAN ID cannot be entered.


1 to 4095

S-Tag VLAN Priority

Defines the S-Tag VLAN Priority. If S-Tag Control is set to None, C-Tag VLAN Priority cannot be entered.


0 to 7


Enables or disables Egress Rate Limiting. Egress limiting allows control over the bandwidth of egress traffic toward the customer LAN port, and is set independently from Ingress Rate Limiting. If set to the Enabled state, Egress CIR, EIR, CBS and EBS entries are allowed.

Disabled

Enabled






TM

Ingress CIR

Defines the Ingress Committed Information Rate (CIR) for this port, in bps. Entries of commas are allowed.

If LAN port speed < WAN port speed, then the sum of all Ingress CIRs on the LAN port may be <= to 1.10 times the speed of the LAN (this value is designated as LPS below). The sum of all Ingress CIRs on the LAN port may not exceed the speed of the WAN port.

Where the sum of all Ingress CIRs on the LAN port + the sum of all Ingress EIRs on the LAN port = Ingress PIR (Peak Information Rate) for the LAN port: Ingress PIR must be <= LPS or the WAN port speed, whichever is less. The sum of Ingress PIRs of all ports/flows/policers must not exceed the speed of the WAN.



1,024,000 bps

0 to 1 Gbps(LAN 5)

1,024,000 bps

Ingress EIR

Defines the Ingress Excess Information Rate (EIR) for this port, in bps. Entries of commas are allowed. If Ingress CIR is set to 0, then an Ingress EIR value of 64 Kbps or greater must be entered (if a value of 1 bps through a value less than 64 Kbps is entered, then the value will automatically be rounded up to 64 Kbps).

(See above definition of LPS and Ingress PIR): Ingress PIR must be <= LPS or the WAN port speed, whichever is less. The sum of Ingress PIRs of all ports/flows/policers must not exceed the speed of the WAN.


0 bps

0 to 1 Gbps(LAN 5)

0 bps

Ingress CBS

Defines the Ingress Committed Burst Size (CBS) for this flow, in Kilobytes. Entry of commas are allowed. CBS cannot be less than CIR in bytes/millisecond.

1 to 1,000 (KB)

Ingress EBS

Defines the Ingress Excess Burst Size (EBS) for this flow, in Kilobytes. Entry of commas are allowed. EBS cannot be less than CIR in bytes/ millisecond. EBS cannot be less than EIR in bytes/millisecond.

0 to 1,000 (KB)

Ingress Buffer Size

Defines the Ingress buffer size for the normal latency queues, in Kilobytes. This resource is allocated in 64 K Byte segments. User input is allocated in 64 K Byte increments - rounded up to the next closest segment. Buffer Size cannot be less than CBS. Entry of comma is allowed.

64 to 33,480 (KB)

128 (KB)

Egress CIR

Defines the Egress Committed Information Rate (CIR) for this flow, in bps. Entry of decimal is allowed. Entries of commas are not allowed.

The combined CIR of all transparent service/flows/policers plus the size of the WAN management tunnel (256 Kbps, if present) cannot exceed the maximum speed of the WAN.


0 to 1 Gbps(LAN 5)

Egress EIR

Defines the Egress Excess Information Rate (EIR) for this flow, in bps. Entry of commas are allowed.

Where Egress CIR + Egress EIR = Egress PIR (Peak Information Rate) for the Port: Egress PIR must not exceed the speed of the LAN Port.


0 to 1 Gbps(LAN 5)





TM

Egress CBS

Defines the Egress Committed Burst Size (CBS) for this flow, in Kilobytes. Entry of commas are allowed. CBS cannot be less than CIR in bytes/millisecond.

1 to 1,000 (KB)

Egress EBS

Defines the Egress Excess Burst Size (EBS) for this flow, in Kilobytes. Entry of commas are allowed. EBS cannot be less than CIR in bytes/ millisecond. EBS cannot be less than EIR in bytes/millisecond.

0 to 1,000 (KB)






TM

5.5.4 LAN Management Tunnel Configuration Options and RulesRefer to Table 5-13 for LAN management tunnel configuration settings and associated rules. A maximum of 16 management tunnels plus Control Protocol Disposition (CPD) filters may be created. Default settings are identified in bold. (See Note 1 through Note 3.)

Note 1: The sum of all management tunnels plus all Control Protocol Disposition (CPD) filters cannot exceed 16.

Note 2: If RIP is enabled on an interface and you are changing the IP address, it may take minutes for RIP to advertise the new IP address. If RIP is enabled on an interface, it is recommended that you perform a FSP 150CC reboot after changing the IP address. This will force RIP to advertise the address immediately. Note that this operation should be performed locally, or a static route must be created to the remote in order to make the changes remotely.

Note 3: A management tunnel utilizes 256 Kbps of bandwidth. As default, each LAN is provisioned without a management tunnel.

Table 5-13 LAN Management Tunnel Configuration Settings Parameter Description /


Tunnel Mode

Defines the LAN management tunnel mode.A management tunnel cannot be created on a LAN provisioned as Connection-oriented Transparent service.

VLAN Based

None

MAC Based

VLAN ID

Defines the Management VLAN ID. It is used to identify management traffic on the LAN port. This option is only applicable if Tunnel Mode is set to VLAN Based.

1 to 4095

N/A

IP Address

(See Note 2)

Defines the IP address for the LAN management tunnel.

0.0.0.0

Subnet Mask Defines the IP subnet mask for the LAN management tunnel. 255.0.0.0

Layer 2 Protocol

Defines the management tunnel encapsulation mode.

Ethernet

PPP

DHCP


Enabled

Disabled


Allows enabling/disabling of the system level Access Control List (ACL) on this management tunnel interface. When enabled, only the permitted IP address(es) provisioned in the system ACL list will be allowed access on this interface.

Enabled

Disabled


Allows setting/disabling of Routing Information Protocol (RIP) V2 packets.

Enable

Disable



TM

5.6 CPD Configuration Options and RulesThe following configuration options and rules apply to WAN, LAN and FID Control Protocol Disposition (CPD) settings by entering a right click on the entity and selecting Edit CPD (see Table 5-14). Default settings are identified in bold.

Table 5-15 summarizes the list of relevant Layer 2 control protocols and Cisco proprietary protocols that are the subject of this feature.

Table 5-14 Control Data Protocol Configuration Options and Rules Parameter Description /


Control Protocol Disposition (Edit CPD) (See Note)

EFM Disposition

EFM-OAM is the default Control Protocol Disposition. It defines the Ethernet First Mile - Operations, Administration and Maintenance protocol setting.

When set to Peer, the CPD frames are counted in Etherjack PM parameters and forwarded. When set to Discard, the CPD frames are discarded and counted in Etherjack PM parameters. When set to Pass, the CPD frames are transported transparently through the system.

If the WAN EFM-OAM is not set to Peer, LAN Facility Fault Propagation cannot be set to Send EFM RLD Msg. The option of Peer is not available for a flow. In order to set a flow to discard, the corresponding port must be set to peer for that protocol type.

Peer (Port default)

(ports only)

Discard (FID default)

(ports and flows)

Pass

(ports and flows)

Add CPD Filter

Selects a Control Protocol Disposition filter to add to the selectable list of CPDs. Selecting a CPD filter from the Add CPD Filter list, then selecting a Disposition, then selecting OK or Apply will create a new selectable CPD within the Control Protocol Disposition area.

If Custom Filter is selected, the Edit Custom Filter data may be entered.

The sum of all management tunnels plus all Control Protocol Disposition (CPD) filters cannot exceed 16.

See Table 5-15 for CPD filter details.

Default has WAN EFM-OAM set to Peer and all LAN interfaces have EFM-OAM set to Discard.

None Selected

Bridge Group

-BPDU

-EFM OAM

-LACP

-LACP Marker

-Port Based

Cisco Group

Custom Filter

GARP Group

-GMRP

-GVRP

LAN Bridge

Disposition for selected CPD Filter

When set to Peer, the selected CPD frames are counted and forwarded. When set to Discard, the selected CPD frames are discarded and counted. When a CPD filter is selected, Inactive is not a valid option.

Inactive

Peer

Discard




TM

Note: To delete a CPD filter, edit all interface CPD dispositions to Pass for the CPD filter to be removed.

MAC Address Match

Set the custom CPD filter MAC address match (in hexadecimal). This option is only applicable when Custom Filter is selected. An active custom filter cannot be edited.

00:00:00:00:00:00

MAC Address Mask

Set the custom CPD filter MAC address and mask (in hexadecimal). This option is only applicable when Custom Filter is selected. An active custom filter cannot be edited.

00:00:00:00:00:00

Ethertype

Set the custom CPD filter Ethertype (in hexadecimal). This option is only applicable when Custom Filter is selected. An active custom filter cannot be edited.

0000

Ethertype Mask

Set the custom CPD filter Ethertype mask (in hexadecimal). This option is only applicable when Custom Filter is selected. An active custom filter cannot be edited.

0000

Subtype

Set the custom CPD filter Subtype (in hexadecimal). This option is only applicable when Custom Filter is selected. An active custom filter cannot be edited.

00

Subtype Mask

Set the custom CPD filter Subtype mask (in hexadecimal). This option is only applicable when Custom Filter is selected. An active custom filter cannot be edited.

00

Table 5-14 Control Data Protocol Configuration Options and Rules (Continued)Parameter Description /




TM

Table 5-15 Layer 2 Control Protocol Summary Protocol Group

Protocol Description MAC Address Ethertype(Subtype)

Notes

Cisco Group

ISL Inter Switch Link (ISL)

01-00-0C-00-00-00 N/A By totally encapsulating the original frame in a two-level tagging scheme, ISL is effectively a tunneling protocol and has the additional benefit of carrying non-Ethernet frames. It adds a 26-byte header and 4-byte Frame Check Sequence (FCS) to the standard Ethernet frame - the larger Ethernet frames are expected and handled by ports configured to be trunks. ISL supports 1024 VLANs.

PAgP Port Aggregation Protocol (PAgP)

01-00-0C-CC-CC-CC 0x0104 PAgP is a management protocol that will check for parameter consistency at either end of the link and assist the channel in adapting to link failure or addition. IEEE 802.3ad Link Aggregation Control Protocol (LACP) will likely supersede PAgP in the long term.

UDLD Unidirectional Link Detection (UDLD)

01-00-0C-CC-CC-CC 0x0111 UDLD monitors physical cabling, shutting down miswired ports, protecting against uni-directional links.

CDP Cisco Discovery Protocol

01-00-0C-CC-CC-CC 0x2000 Proprietary Discovery Protocol

VTP VLAN Trunking (VTP)

01-00-0C-CC-CC-CC 0x2003 The VTP protocol communicates between switches using an Ethernet destination multicast MAC address (01-00-0c-cc-cc-cc) and SNAP HDLC protocol type Ox2003. It does not work over non-trunk ports (VTP is a payload of ISL or 802.1Q), so messages cannot be sent until DTP has brought the trunk online.

DTP Dynamic Trunking (DTP)

01-00-0C-CC-CC-CC 0x2004 DTP negotiates configuration parameters between a switch port and its neighbor. Trunks extend VLANs between devices by temporarily identifying and tagging (link-local) the original Ethernet frames, thus enabling them to be multiplexed over a single link. This also ensures the separate VLAN broadcast and security domains are maintained between switches.

PVSTP+ Spanning Tree PVSTP+

01-00-0C-CC-CC-CD 0x010b In order to support the IEEE 802.1q standard, Cisco's existing STP implementation was extended to become PVST+ by adding support for tunneling across an IEEE 802.1q mono Spanning Tree region. PVST+ is therefore compatible with both IEEE 802.1q's MST and Cisco PVST protocols without requiring extra commands or configuration. In addition, PVST+ adds verification mechanisms to ensure that there is no configuration inconsistency of port trunking and VLAN IDs across switches.

UplinkFast STP UplinkFast 01-00-0C-CD-CD-CD 0x200a UplinkFast provides fast STP convergence after a direct link failure in the network access layer. It operates without modifying STP, and its purpose is to speed up convergence time in a specific circumstance to less than three seconds.




TM

Cisco Group (Cont.)

VLAN Bridge

VLAN Bridge 01-00-0C-CD-CD-CE 0x010c If there is a need to bridge non-routable or legacy protocols between VLANs without interfering with the IEEE Spanning Tree instance(s) running on those VLANs

L2PT Layer 2 Protocol Tunnelling (L2PT)

01-00-0C-CD-CD-D0 N/A Layer 2 protocol tunneling allows Layer 2 protocol data units (PDUs) (CDP, STP, and VTP) to be tunneled through a network using a Cisco proprietary multicast address.

Bridge Group

802.1d (BPDU)

IEEE Spanning Tree 802.1d

01-80-C2-00-00-00 N/A N/A - DSAP 42 SSAP 42

802.1s (BPDU)

Multiple STP 01-80-C2-00-00-00 N/A

802.1w (BPDU)

Rapid Reconfiguration of Spanning Tree (RSTP)

01-80-C2-00-00-00 N/A

802.3ad (LACP)

Link Aggregation Control Protocol

01-80-C2-00-00-02 0x8809

(01)

Link Aggregation Control protocol

802.3ad (LACP Marker)

Marker Protocol 01-80-C2-00-00-02 0x8809

(02)

LACP Marker protocol

802.3ah (EFM OAM)

EFM OAM 01-80-C2-00-00-02 0x8809

(03)

EFM OAM Slow protocol

802.1x (Port Based)

Port Based Network Access Control

01-80-C2-00-00-03 0x888E Port Authentication Protocol

Reserved (Bridge Reserved)

Bridge Reserved 01-80-C2-00-00-04

through

01-80-C2-00-00-0F

N/A Reserved for use by 802.1. IEEE-802.1D states that a bridge will never forward a frame with one of these addresses.

All Bridges

802.1d (LAN Bridge)

LAN Bridge Management

01-80-C2-00-00-10 N/A All LANs Bridge Management

GARP Group

GMRP GARP Multicast Registration Protocol

01-80-C2-00-00-20 N/A Multicast Registration Protocol

GVRP GARP VLAN Registration Protocol

01-80-C2-00-00-21 N/A VLAN Registration Protocol

Reserved (GARP Reserved)

GARP 01-80-C2-00-00-22

through

01-80-C2-00-00-2F

N/A

Table 5-15 Layer 2 Control Protocol Summary (Continued)Protocol Group

Protocol Description MAC Address Ethertype(Subtype)

Notes



TM

5.7 Loopback SettingsRefer to Table 5-16 for WAN and Table 5-17 for LAN loopback option settings. To set loopback options, select Maintenance view, enter a right click on the desired entity in the Menu Tree and select Loopback. For WAN interfaces when LAG is present, only a WAN-1 or WAN-2 loopback may be applied at a time. They cannot be applied simultaneously on WAN-1 and WAN-2. Loopback may be selected from either the WAN Interface or Protection Groups lists. Default settings are identified in bold.

Table 5-16 WAN Loopback Settings Parameter Description /



Defines the LAN or WAN facility administrative state. The Administrative State must be set to Testing prior to initiating a loopback or Etherjack Diagnostic. The setting can only be changed from the Testing state when in Maintenance View if the facility is in loopback.

Enabled

Disabled

Testing

Loopback

Allows you to set the Loopback State for a WAN or LAN port. Allows constant or timed loopback of terminal or up to three individual VLAN flows. The interface must be in the assigned state and the Administrative State must be set to Testing prior to initiating a loopback.

To activate a VLAN loopback, at least one VLAN ID must be selected in order to activate the VLAN loopback.

When activating a Remote EFM-OAM loopback, the loopback includes management traffic, therefore management traffic is dropped while the EFM-OAM loopback is active. Since all EFM-OAM frames are still processed, when the Remote EFM-OAM loopback is released, management connectivity will also be restored.

None

Terminal

Facility

Terminal VLAN

Facility VLAN

Terminal Timed

Facility Timed

Remote EFM-OAM

Timer

Specifies the amount of time the loopback is to be applied to Terminal Timed and Facility Timed loopback. The loopback is released when the preset time has expired.

2 to 300 (seconds)60

Inner and Outer VLAN ID 1

First of three Virtual LAN Identifiers available for loopback. The format is VLAN ID-Priority. Up to three Inner and Outer VLAN loopbacks may be created per entity.

Only selectable if Terminal or Facility VLAN is selected. To activate the VLAN ID, the check box must be selected. At least one Inner and Outer VLAN ID must be selected in order to activate the VLAN loopback.

Default VLAN ID is the same as the last VLAN ID used for the entity. Only one VLAN loopback may be performed per system. Once a VLAN loopback has been operated, a second VLAN loopback may not be performed on another entity.

(0 to 4095)-(0 to 7)

(4094-0 if Terminal or Facility VLAN is

selected)




TM


(See above.)

Second of three Inner and Outer Virtual LAN Identifiers available for loopback.

(0 to 4095)-(0 to 7)


selected)


(See above.)

Last of three Virtual LAN Identifiers available for loopback.

(0 to 4095)-(0 to 7)


selected)

Swap SA and DA at loopback

Allows enabling/disabling of swapping the source and destination addresses for loopback testing. This option is available when in Maintenance View by selecting Loopback.

Only one Swap SA/DA loopback may be performed per system. Once a Swap SA/DA loopback has been operated, a second Swap SA/DA loopback may not be performed on another entity.

Selected (Enabled)

Not Selected (Disabled)

Table 5-17 LAN Loopback Settings Parameter Description /



Defines the LAN or WAN facility administrative state. The Administrative State must be set to Testing prior to initiating a loopback or Etherjack Diagnostic. The setting can only be changed from the Testing state when in Maintenance View if the facility is in loopback.

Enabled

Disabled

Testing

Loopback

Allows you to set the Loopback State for a WAN or LAN port. Allows constant or timed loopback of terminal or up to three individual VLAN flows. The interface must be in the assigned state and the Administrative State must be set to Testing prior to initiating a loopback.

To activate a VLAN loopback, at least one VLAN ID must be selected in order to activate the VLAN loopback.

None

Terminal

Facility

Terminal VLAN

Facility VLAN

Terminal Timed

Facility Timed

Timer

Specifies the amount of time the loopback is to be applied to Terminal Timed and Facility Timed loopback. The loopback is released when the preset time has expired.

2 to 300 (seconds)60

Table 5-16 WAN Loopback Settings (Continued)Parameter Description /




TM

VLAN ID 1

First of three Virtual LAN Identifiers available for loopback. The format is VID-PRIO. Up to three VLAN loopbacks may be created per entity.

Only selectable if Terminal or Facility VLAN is selected. To activate the VLAN ID, the check box must be selected. At least one Inner and Outer VLAN ID must be selected in order to activate the VLAN loopback.

Default VLAN ID is the same as the last VLAN ID used for the entity. Only one VLAN loopback may be performed per system. Once a VLAN loopback has been operated, a second VLAN loopback may not be performed on another entity.

(0 to 4095)-(0 to 7)


selected)

VLAN ID 2

(See above.)

Second of three Virtual LAN Identifiers available for loopback.

(0 to 4095)-(0 to 7)


selected)

VLAN ID 3

(See above.)

Last of three Virtual LAN Identifiers available for loopback.

(0 to 4095)-(0 to 7)


selected)

Swap SA and DA at loopback

Allows enabling/disabling of swapping the source and destination addresses for loopback testing. This option is available when in Maintenance View by selecting Loopback.

Only one Swap SA/DA loopback may be performed per system. Once a Swap SA/DA loopback has been operated, a second Swap SA/DA loopback may not be performed on another entity.

Selected (Enabled)

Not Selected (Disabled)

Table 5-17 LAN Loopback Settings (Continued)Parameter Description /





TM

5.8 Alarm Attributes, Probable Cause and Trouble ClearingAll problems causing an alarm event are soaked for 2.5 seconds before the alarm indication is raised. The problem causing the alarm event must clear for 10 seconds before the alarm indication is cleared. All FSP 150CCf-825 System alarms and default notification codes are shown in Table 5-18. For all FSP 150CCf-825 LAN and WAN alarms, see Table 5-19. For Maintenance End Point (MEP) alarms, see Table 5-20. Each of the following tables contain a description of the alarm condition, probable cause and suggested trouble clearing procedure. To clear alarm conditions, it is suggested that you start by using the trouble clearing procedure in Section 1.2 Trouble Clearing, on Page 1-4.

To modify alarm notification codes for a given alarm condition type using eVision, select Maintenance view, right click on the desired entity in the Menu Tree and select Edit Alarm Attributes. The options available for notification codes are: Critical, Major, Minor, Not Alarmed or Not Reported. For LED locations associated with an alarm condition, refer to Section 1.6.1 Connectors and LED Descriptions, on Page 1-46.

Table 5-18 System Alarms Condition Type

(See Note 1)Description /

Probable CauseService Affect

Default Notification

Trouble Clearing Procedure

PSU Power Failure Power Supply Unit power failure. Non-Affecting

Critical Replace power supply unit.

PSU Unequipped Power Supply Unit is unequipped. Non-Affecting

Critical Insert power supply unit.

Scheduled Ping Failed

A scheduled Ping failed to complete.

See Note 2.

Non-Affecting Minor

1) Verify that the IP address can be reached (respond to pings) by performing both a ping and a trace route from the management tunnel’s IP address.

2) Verify management communication configuration.

a) Target IP address connectivity or routing problem.

a) Repair IP address connectivity or routing problem.

b) Ping is turned off at target equipment.

b) Ensure that ping response is not disabled at the target equipment.

c) Alarm or condition on interface. c) Repair using appropriate alarm reference in this manual.

d) Incorrect IP address entered. d) Edit target IP address.



TM

Note 1: Except for the PSUs, the alarm attributes for system alarms are settable via CLI and SNMP, but not via eVision.

Note 2: When using Ethernet encapsulated management tunnels, the source IP address of the ping used to validate reachability of the trap host is the IP address assigned to the management tunnel, and not the system IP address.

SNMP Dying Gasp Trap Host Unreachable Via Ping

Test to reach Dying Gasp Host failed. Cannot reach target address over designated interface.

See Note 2.

Non-Affecting

Minor

Ensure that the trap host can be reached (respond to pings) by performing both a ping and a trace route from the management tunnel’s IP address.

SNTP Server Not Found

Attempt to connect to the SNTP Server failed.

See Note 2.

Non-Affecting

Minor

1) Verify that the IP address can be reached (respond to pings) by performing both a ping and a trace route from the management tunnel’s IP address.

2) Verify management communication configuration.

a) Target IP address connectivity or routing problem.

a) Repair IP address connectivity or routing problem.

b) No SNTP server / SNTP server down.

b) Repair SNTP server.

Unsaved Configuration Data

Configuration changes have been made but not saved.

This alarm is generated any time the existing (saved) configuration is modified by a user. It is sent as a way to log user activity and also remind the user that configuration changes must be saved to non-volatile memory prior to logging off the unit.

Non-Affecting

Minor Verify configuration changes and then save configuration.

Table 5-18 System Alarms (Continued) (Continued)Condition Type

(See Note 1)Description /







TM

Table 5-19 LAN and WAN Alarms Condition Type Description /



LEDColor


Auto Negotiation Duplex Unknown

Duplex mode of the connected equipment is unknown. The unit determined it cannot conclude negotiation with remote end on the Ethernet port. Although auto negotiation failure is a minor alarm, it is usually followed by a critical alarm due to link down.

Affecting Minor Amber

Determine the expected port speed setting and ensure that both ends are configured to reflect that setting.

Dying Gasp Received an EFM OAM Dying Gasp message.

Affecting Critical Red Restore or repair connected equipment.

EFM Discovery Fail

EFM OAM protocol discovery failure. This notification is sent by the interface unit when it is unable to establish EMF based peering with a remote unit (per 802.3ah standard).


Verify that the IP address can be reached and verify far end equipment EFM provisioning.

a) Far end does not support EFM-OAM (IEEE 802.3ah).

a) Set interface CPD to discard EFM-OAM.

b) Communications problem.

b) Repair communications problem.

c) EFM turned off (not set to Peer) at far end.

c) Provision far end equipment.

LCP Fail

This alarm is generated as a result of a loss of tunneling capability between the two units.

Link Control Protocol, which is run on PPP encapsulated management tunnels, has encountered a problem.

Equipment throughout the network may not be configured correctly.

Affecting Critical Amber

Verify the management tunnel definition at the far end device is consistent with the definition of the management tunnel on this port.

If the tunnel definitions are the same, ensure equipment in between this device and the far end device is configured to properly transport the VLAN defined for the management tunnel.



TM

Link Deactivated

The fault propagation feature is enabled and has been activated, resulting in the deactivation of this LAN port.

Such alarm indicates that the port is down due to fault propagation on a corresponding remote port. The link deactivated message is useful in that it ensures that the proper failed unit will be addressed.

Affecting Critical Red

Verify WAN alarms at the far end.

a) Clear the WAN condition that caused the fault propagation feature to activate.

b) Disable fault propagation.

Link Down

(See Note 2)

Link Down, is generated when a physical connection is lost on a good link on the Ethernet interface port (LAN or WAN), due to one of the following:

Affecting Critical Red

Verify interface configuration and cable connections at both ends.

a) Auto negotiation fault. Far end is not advertising its auto negotiation rate.

a) Test and repair far end equipment.

b) Unisolated. Upon the loss of connection on a given port, this is the first notification being sent, before any specific cause is determined (such as cable fault or cable removed).

b) Wait a few moments for the system to isolate the trouble and observe another Link Down condition on this interface. Troubleshoot according to the new condition.

c) Cable removed. A Cable Removed notification is sent when it is determined that the link is down due to a cable being locally removed from its RJ-45 port connection.

c) Insert or repair cable.

d) Cable fault. A Cable Fault notification is sent when it is determined that the link is down due to a cable fault on a copper (RJ-45) port.

d) Perform an Etherjack Diagnostic test. Repair the cable using test results.

Table 5-19 LAN and WAN Alarms (Continued)Condition Type Description /



LEDColor





TM

MAC Table Full

MAC learning table is full. Applicable to LAN Connection-less services only.

Affecting Minor N/A

Observe the MAC table entries. No action may be required in some cases and this is simply an indicator. Continue if action is required:

a) Increase the MAC Table Size.

b) Decrease the Aging time.

c) Flush the MAC table.

Remote Critical Event

Received an EFM OAM Critical Event indication. This alarm is sent when a NID receives an OAM- PDU from the remote end indicating a critical event has occurred.


Clear critical condition at that far end.

Remote Link Down

(WAN only)

The fault propagation feature is enabled and has been activated, and a Remote Link Down (RLD) EFM message has been received for a specific interface.

This message is sent by the far end when a LAN problem is detected. The alarm specifies the far end LAN port(s) that is experiencing a problem.


At the far end, clear the fault on the LAN port(s) that is causing the transmission of the RLD message.

Alternatively, the fault propagation feature can be disabled at the near or far end.

Remote Link Status Indication

Received an EFM OAM Remote Link Status Indication

Affecting Minor AmberClear fault (Link Down or SFP) condition at the far end.

RFI

Remote Failure Indication received from remote equipment. Remote end has lost the signal originating from the local NID (see Note 1).


Verify the signal leaving the local NID, through any inter-mediate equipment, and at the far end.

Repair faulty equipment or cable.




LEDColor




TM

Rx Jabber

The total number of packets received were longer than the MTU size (see below), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error), or a bad FCS with a non-integral number of octets (Alignment Error).

Note that the MTU is interface specific and can vary, based on the system attribute indicating whether jumbo frames are supported: LAN-1 to LAN-4: 2000 octets (always), LAN-5: 2000 or 9250 octet, WAN: 2004 or 9250 octets.

Probable Cause: Network problem, or possibly a bad cable.

Affecting Major Red

Verify the signal leaving the far end NID, through any inter-mediate equipment, and at the near end.

Repair faulty equipment or cable.

SFP Mismatch (Fiber only)

Small Form-factor Plug-able optics module mismatch. The installed SFP module does not match the provisioned module type for the interface.

The system expects the SFP to conform to the MSA specification for inventory contents and and alarm will be raised if the SFP’s inventory data does not reflect that the device supports the configured speed.

Affecting Critical AmberRemove SFP module and replace with an ADVA-approved module for that interface type.

SFP Removed (Fiber only)

Small Form-factor Plug-able optics module is removed.

Affecting Critical Red Install SFP module.

SFP Tx Fault (Fiber only)

Small Form-factor Plug-able optics module failure.

Affecting Critical Red Replace SFP module.




LEDColor





TM

Note 1: If the WAN RFI alarm notification code is set to Not Reported or Not Alarmed, then the Fault Propagation feature will not activate for that alarm attribute.

Note 2: LAG Link Down alarm has both Service Affecting and Non-Service Affecting alarm profiles. The alarm is Service Affecting when LAG Aggregator LACP Control is Enabled and is Non-Service Affecting when LAG Aggregator LACP Control is Disabled. The alarm is raised whenever the LAG has been created, but neither WAN (e1000-wan-1 nor e1000-wan-2) is Collecting and Distributing. If either WAN port is Collecting and Distributing (should ever only be one at a time), the alarm is cleared (or never raised). The LAG Link Down alarm has a 2.5 +/- 0.5 second onset and 10.5 +/- 0.5 second offset.

Table 5-20 MEP Alarms Condition Type Description /




Crossconnect CCM

Crossconnect Continuity Check Message (CCM) defect is raised when one cross-connected CCM is received. It is cleared when a cross-connected CCM is not received for 3.5 times the provisioned CCM transmission interval of the last cross-connected CCM.

A CCM is considered cross- connected if MAID (48 byte entity consisting of MD name, MA name and MEP ID) does not match with the MAID of the receiving MEP, or if MD Level is less than the receiving MEP’s MD Level.

Probable causes are:

Affecting Minor

1) Verify MA and VLAN configuration at each end point throughout the network.

2) Verify configuration of MA VLANs in the network.

a) Erroneous configuration of MA at the different end points of the MA. For example, if a different MA name is configured at different end points.

a) Reconfigure MA configuration at appropriate node(s).

b) MD Level is less than the receiv-ing MEP’s MD Level

d) Reconfigure MD Level configuration at appropriate node(s).

c) Some other MA’s CCM can be received due to mis-configuration of VLANs in the network.

c) Change MA and/or VLAN configuration at appropriate node(s).



TM

Erroneous CCM

Erroneous Continuity Check Message (CCM) defect is raised when one invalid CCM is received. It is cleared when an invalid CCM is not received for 3.5 times the provisioned CCM transmission interval of the last invalid CCM. A CCM is invalid if:

1. MEP ID in the received CCM is not configured in the receiving MEP’s MA.

2. MEP ID in the received CCM matches the receiving MEP’s MEP ID.

3. CCM interval does not match the interval configured for the receiving MEP’s MA.

Probable Causes are:

Affecting Minor

Verify MEP ID and CCM transmission interval configuration at each end point throughout the network.

a) Mis-configuration of MA, where the MEP list is not consistent at all the end points.

a) Reconfigure MEP list at appropriate node(s).

b) Mis-configuration of MA, where the MA CCM transmission interval is different at one or more end points of the MA.

b) Reconfigure MA CCM transmission interval at appropriate node(s).

c) Mis-configuration of MEP, where MEPs with same MEP ID is created at two or more end points of the MA.

c) Reconfigure MEP ID at appropriate node(s).

Some Remote MEP CCM

A Remote Maintenance End Point (MEP) Continuity Check Message (CCM) defect indicates that a CCM is not received from a Remote MEP for 3 consecutive provisioned CCM transmission intervals.

Probable causes are:Affecting Minor

1) Observe if an Erroneous CCM or Cross-connect CCM condition exists on the remote MEP.

2) Verify cable connections and configuration at network equipment / intermediate nodes.

a) If MEPs in an MA are mis-configured, and as a result there are Erroneous CCM or Crossconnect CCM conditions, this alarm could be raised as a side-effect.

a) If an Erroneous CCM or Cross-connect CCM condition exists, refer to the appropriate steps to clear the Erroneous CCM or Cross-connect CCM condition.

b) A problem exists causing the CCM to be dropped before it reaches the end point, such as a physical problem with the network or mis-configuration of the equipment in the network.

b) Troubleshoot and repair the physical network or reconfigure network equipment / intermediate nodes.

Table 5-20 MEP Alarms (Continued)Condition Type Description /







TM

Note: MEP alarm attributes are editable in CFM mode (by selecting Applications and then CFM or selecting the CFM icon).

Some MAC Status

Some MAC Status defect exists on a MEP if:

1) At least one remote MEP’s interface is unavailable.

2) All MEPs on the same interface are reporting that the port is blocked (i.e., all remote MEPs’ Bridge Ports are not forwarding data).

The problem lies at the starting point of the service instance (the Remote MEP) and probably not anywhere in the network used by the MA.

Note: In Release 1.1 CCMs generated do not have Port Status or Interface Status TLVs, but the TLVs are handled if CCMs are received containing them.

Affecting Minor

Verify the Remote MEP LAN interface connection and configuration.

Troubleshoot and repair the Remote MEP interface connection or reconfigure the interface.

Some RDI

At least one of the Remote MEPs is sending CCMs with Remote Defect Indication (RDI) set.

RDI is present in the CCMs transmitted when any of the other MEP alarm conditions (above) exist for a Remote MEP.

Affecting Minor

Observe MEP alarm conditions at the remote node.

Perform appropriate steps in this table to clear the condition at the far end.

Table 5-20 MEP Alarms (Continued)Condition Type Description /






TM

5.9 Performance Monitoring SettingsRefer to the following tables for Performance Monitoring (PM) Threshold Crossing Alert (TCA) monitored types and associated default settings for WAN, LAN Port, Flows, QOS, Policer, ESA and RADIUS:

• WAN Threshold Crossing Alerts

• LAN Port Threshold Crossing Alerts

• Flow Related Threshold Crossing Alerts

• Flow QOS Threshold Crossing Alerts

• Flow Policer Threshold Crossing Alerts

• ESA Threshold Crossing Alerts

For RADIUS, PM counters may be displayed and registers may be initialized.

Note: RADIUS PM counts are only applicable where Remote Authentication Protocol is set to RADIUS.

Refer to Performance Monitoring, on Page 3-63 for procedures on viewing, editing and initializing PMs using eVision.

WAN Threshold Crossing AlertsRefer to the following table for WAN port Threshold Crossing Alerts (TCAs).

Table 5-21 WAN Monitored Types and Default TCA Settings Performance

ParameterDefinition Number /

15 MinutesNumber /

DayLocation Direction

ABR-RX Average Bit Rate Received. The average bit rate received over the specific interval in the ingress direction. If there is link down during the interval, the bin is not accessible. This counter is based on RMON etherStatsOctets.

0 0 NEND RCV

ABR-TX Average Bit Rate Transmitted. The average bit rate transmitted over a specific interval in the egress direction, based on Bytes Sent. If there is link down during the interval, the bin is not accessible.

0 0 NEND TRMT

ESBF EtherStats Broadcast Frames. The Broadcast Frames Sent in the egress direction If there is link down during the interval, the bin is not accessible.

0 0 NEND TRMT




TM

ESBP EtherStats Broadcast Packets Received. The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.

0 0 NEND RCV

ESBS EtherStats Bytes Sent. The Bytes Sent in the egress direction If there is link down during the interval, the bin is not accessible.

0 0 NEND TRMT

ESC EtherStats Collisions. The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously.

0 0 NEND RCV

ESCAE EtherStats CRC (Cyclic Redundancy Check) Aligned Errors. The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).

37055 3557280 NEND RCV

ESDE EtherStats Drop Events. The total number of events in which packets were dropped due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.

37055 3557280 NEND RCV

Table 5-21 WAN Monitored Types and Default TCA Settings (Continued)Performance


15 MinutesNumber /




TM

ESF EtherStats Fragments. The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).

Note that it is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.

37055 3557280 NEND RCV

ESFS EtherStats Frames Sent. The Frames Sent in the egress direction If there is link down during the interval, the bin is not accessible.

0 0 NEND TRMT

ESJ EtherStats Jabbers. The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).

Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.

0 0 NEND RCV

ESMF EtherStats Multicast Frames. The Multicast Frames Sent in the egress direction If there is link down during the interval, the bin is not accessible.

0 0 NEND TRMT

ESMP EtherStats Multicast Packets Received. EtherStats Multicast Packets Received. The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.

0 0 NEND RCV

ESO EtherStats Octets Received. The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).

0 0 NEND RCV



15 MinutesNumber /





TM

ESOP EtherStats Oversize Packets. The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.

37055 3557280 NEND RCV

ESP EtherStats Packets Received. EtherStats Packets Received. The total number of packets (including bad packets, broadcast packets, and multicast packets) received.

0 0 NEND RCV

ESP64 EtherStats Packets - 0 to 64 Octets Frames. The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).

0 0 NEND RCV

ESP65 EtherStats Packets - 65 to 127 Octets Frames. The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).

0 0 NEND RCV


0 0 NEND RCV

ESP256 EtherStats Packets - 256 to 511 Octet Packets. The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).

0 0 NEND RCV


0 0 NEND RCV


0 0 NEND RCV



15 MinutesNumber /




TM

a. Media Type = Fiber only.


0 0 NEND RCV

ESUF EtherStats Unicast Frames. The Unicast Frames Sent in the egress direction If there is link down during the interval, the bin is not accessible.

0 0 NEND TRMT

ESUP EtherStats Undersize Packets. The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were therwise well formed.

37055 3557280 NEND RCV

L2CPFD Layer 2 Control Protocol Frames Discarded. Number of Layer 2 Control Protocol Frames discarded on the interface.

0 0 NEND RCV

L2CPFP Layer 2 Control Protocol Frames Processed. Number of Layer 2 Control Protocol Frames processed on the interface.

0 0 NEND RCV

LBC a Laser Bias Current retrieved from the SFP. Applicable only if the media type is Fiber.

50 50 NEND RCV

LOOKUPFAILS Lookup Fail Counts. Number of frames received on the WAN Port that failed the lookup for steering to the right LAN port and were dropped.

0 0 NEND RCV

OPR a Optical Power Receive. Received Optical Power (in dBm) retrieved from the SFP. Applicable only if the media type is Fiber.

-80 -80 NEND RCV

OPT a Optical Power Transmit. Transmit Optical Power (in dBm) retrieved from the SFP. Applicable only if the media type is Fiber.

-80 -80 NEND RCV



15 MinutesNumber /





TM

LAN Port Threshold Crossing Alerts Refer to the following table for LAN port level Threshold Crossing Alerts (TCAs).

Table 5-22 LAN Port Monitored Types and Default TCA Settings Performance


15 MinutesNumber /


ABRRLRX Average Bit Rate Limited Received. The average over the specific interval based on Bytes Received. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND RCV

ABRRLTX Average Bit Rate Limited Transmitted. The average bit rate transmitted over a specific interval in the egress direction, based on Bytes Sent. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND TRMT

ABR-RX Average Bit Rate Received. The average bit rate received over the specific interval in the ingress direction. If there is link down during the interval, the bin is not accessible. This counter is valid for all modes of the ethernet interface. In case of transparent ethernet service, this counter is based on RMON etherStatsOctets.

0 0 NEND RCV

ABR-TX Average Bit Rate Transmitted. The average bit rate transmitted over a specific interval in the egress direction, based on Bytes Sent. If there is link down during the interval, the bin is not accessible.

0 0 NEND TRMT

APFD a AFP (Acceptable Frame Policy) Priority Tagged Frames Discarded (APFD) in the ingress direction. Only applicable when Port is in Connection-oriented, TVLS mode.

0 0 NEND RCV

AUFD b AFP (Acceptable Frame Policy) Untagged Frames Discarded (AUFD) in the ingress direction. Only applicable when Port is in Connection-oriented, TVLS mode.

0 0 NEND RCV

BT-RX Bytes Transmitted (BT) - Receive. Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND RCV

BTD-RX Bytes Tail Dropped (BTD) by RX Policer, Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND RCV

BTD-TX Bytes Tail Dropped (BTD) by TX Policer. Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND TRMT



TM

ESBF EtherStats Broadcast Frames sent in the egress direction.

0 0 NEND TRMT

ESBP EtherStats Broadcast Packets Received. EtherStats Broadcast Packets Received. The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.

0 0 NEND RCV

ESBS EtherStats Bytes Sent. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND TRMT

ESC EtherStats Collisions. The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously.

0 0 NEND RCV

ESCAE EtherStats CRC (Cyclic Redundancy Check) Aligned Errors. The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).

37055 3557280 NEND RCV

ESDE EtherStats Drop Events. The total number of events in which packets were dropped due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.

37055 3557280 NEND RCV

Table 5-22 LAN Port Monitored Types and Default TCA Settings (Continued)Performance


15 MinutesNumber /





TM

ESF EtherStats Fragments. The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).

Note that it is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.

37055 3557280 NEND RCV

ESFS EtherStats Frames Sent. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND TRMT

ESJ EtherStats Jabbers. The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).

Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.

0 0 NEND RCV

ESMF EtherStats Multicast Frames sent in the egress direction.

0 0 NEND TRMT

ESMP EtherStats Multicast Packets Received. The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.

0 0 NEND RCV

ESO EtherStats Octets Received. The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).

0 0 NEND RCV



15 MinutesNumber /




TM

ESOP EtherStats Oversize Packets. The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.

37055 3557280 NEND RCV

ESP EtherStats Packets Received. The total number of packets (including bad packets, broadcast packets, and multicast packets) received.

0 0 NEND RCV

ESP64 EtherStats Packets - 0 to 64 Octets Frames. The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).

0 0 NEND RCV


0 0 NEND RCV


0 0 NEND RCV

ESP256 EtherStats Packets - 256 to 511 Octet Packets. The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).

0 0 NEND RCV


0 0 NEND RCV


0 0 NEND RCV



15 MinutesNumber /





TM


0 0 NEND RCV

ESUF EtherStats Unicast Frames sent in the egress direction.

0 0 NEND TRMT

ESUP EtherStats Undersize Packets. The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were therwise well formed.

37055 3557280 NEND RCV

FD-RX Frames Dequeued (FD) - Receive. Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND RCV

FD-TX a Frames Dequeued (FD) - Transmit. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND TRMT

FFD-RX Frames Filtered by MAC Bridge - Receive. Only applicable when Port is in Connection- less mode.

0 0 NEND RCV

FMG-RX Frames Marked as Green by RX Policer in the ingress direction. Only applicable when Port is in Connection-oriented, TLS mode.

37055 3557280 NEND RCV

FMG-TX Frames Marked as Green by TX Policer. Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND TRMT

FMRD-RX Frames Marked as Red Dropped by RX Policer in the ingress direction. Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND RCV

FMRD-TX Frames Marked as Red Dropped by TX Policer. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND TRMT

FMY-RX Frames Marked as Yellow by RX Policer in the ingress direction. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND RCV

FMY-TX Frames Marked as Yellow by TX Policer. Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND TRMT

FMYD-RX Frames Marked as Yellow Dropped by RX Policer. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND RCV



15 MinutesNumber /




TM

FMYD-TX Frames Marked as Yellow Dropped by TX Policer. Only applicable when Port is in Connection-oriented, TLS mode.

0 0 NEND TRMT

FTD-RX Frames Tail Dropped (FTD) - Receive. Only applicable when Port is in Connection- oriented, TLS mode.

0 0 NEND RCV

FTD-TX a Frames Tail Dropped (FTD) - Transmit. Only applicable when Port is in Connection- oriented, TLS mode.

37055 3557280 NEND TRMT

L2CPFD Layer 2 Control Protocol Frames Discarded. Number of Layer 2 Control Protocol Frames discarded on the interface.

0 0 NEND RCV

L2CPFP Layer 2 Control Protocol Frames Processed. Number of Layer 2 Control Protocol Frames processed on the interface.

0 0 NEND RCV

LBC b Laser Bias Current retrieved from the SFP. Applicable only if the media type is Fiber.

50 50 NEND RCV

OPR b Optical Power Receive. Received Optical Power (in dBm) retrieved from the SFP. Applicable only if the media type is Fiber.

-80 -80 NEND RCV

OPT b Optical Power Transmit. Transmit Optical Power (in dBm) retrieved from the SFP. Applicable only if the media type is Fiber.

-80 -80 NEND RCV

a. Flow VLAN service only.b. Media Type= Fiber only.



15 MinutesNumber /





TM

Flow Related Threshold Crossing AlertsRefer to the following table for Flow related Threshold Crossing Alerts (TCAs).

Flow QOS Threshold Crossing Alerts Refer to the following table for Flow QOS Threshold Crossing Alerts (TCAs).

Table 5-23 Flow Monitored Types and Default TCA Settings Performance


15 MinutesNumber /


ABRRL-RX Average Bit Rate Limited - Receive 0 0 NEND RCV

ABRRL-TX Average Bit Rate Limited - Transmit 0 0 NEND TRMT

ABR-RX Average Bit Rate - Receive. 0 0 NEND RCV

ABR-TX Average Bit Rate - Transmit 0 0 NEND TRMT

FMRD-RX Frames Marked as Red Dropped - Receive. 0 0 NEND RCV

FMRD-TX Frames Marked as Red Dropped - Transmit 0 0 NEND TRMT

FMYD-RX Frames Marked as Yellow Dropped - Receive 0 0 NEND RCV

FMYD-TX Frames Marked as Yellow Dropped - Transmit 0 0 NEND TRMT

FMYP-RX Frames Marked as Yellow Passed - Receive 0 0 NEND RCV

FMYP-TX Frames Marked as Yellow Passed - Transmit 0 0 NEND TRMT

FTD-RX Frames Tail Dropped - Receive 37055 3557280 NEND RCV

FTD-TX Frames Tail Dropped - Transmit 37055 3557280 NEND TRMT

L2CPFD Layer 2 Control Protocol Frames Discarded 0 0 NEND RCV

Table 5-24 Flow QOS Monitored Types and Default TCA Settings Performance


15 Min.Number /


ABR-RL Average Bit Rate Limited 0 0 NEND RCV

BT Bytes Transmitted 0 0 NEND RCV

BTD Bytes Tail Dropped 0 0 NEND RCV

FD Frames Dequeued 0 0 NEND RCV

FTD Frames Tail Dropped 0 0 NEND RCV



TM

Flow Policer Threshold Crossing Alerts Refer to the following table for Flow Policer Threshold Crossing Alerts (TCAs).

ESA Threshold Crossing AlertsESA PM thresholds are viewed using eVision by selecting the ESA icon or selecting ESA from the Applications menu, expanding the menu tree, selecting the Probe entity and then selecting the Thresholds tab. To edit PM thresholds, enter a right click on the Probe entity and select Edit Thresholds. See Table 5-26 for ESA monitored types and default TCA settings.

Table 5-25 Flow Policer Monitored Types and Default TCA Settings Performance


15 Min.Number /


ABR Average Bit Rate 0 0 NEND RCV

FMG Frames Marked Green 0 0 NEND RCV

FMRD Frames Marked Red and Dropped 0 0 NEND RCV

FMY Frames Marked Yellow 0 0 NEND RCV

FMYD Frames Marked Yellow and Dropped 0 0 NEND RCV

Table 5-26 ESA Monitored Types and Default TCA Settings Performance

ParameterDefinition Default

Threshold

P2R-PKT Probe to Reflector Packets. The total number of Transmitted Packets in the current interval.

0

R2P-PKT Reflector to Probe Packets. The total number of Received Packets in the current interval.

0

P2R-ERR-PKT Probe to Reflector Errored Packets. The total number of Packets in the current interval, for which there was a problem in transmission.

0

R2P-ERR-PKT Reflector to Probe Errored Packets. The total number of Received Packets in the current interval, which had protocol errors, timestamp synchronization problems.

0

LOST-PKT Lost Packets. The total number of Lost Packets in the current interval.

0

LATE-PKT Late Packets. The total number of Late Arrival Packets in the current interval.

0

SEQ-GAPS Sequence Gaps. The total number of sequence gaps across all packets received in the current interval.

0




TM

OUTOFSEQ-ERR Out of Sequence Errors. The total number of out of sequence errors across all packets received in the current interval.

0

MIN-RTDELAY Minimum Round Trip Delay. The minimum round-trip delay (in milliseconds) across all packets received in the current interval.

0

MAX-RTDELAY Maximum Round Trip Delay . The maximum round-trip delay (in milliseconds) across all packets received in the current interval.

0

AVG-RTDELAY Average Round Trip Delay. The average round-trip delay (in milliseconds) across all packets received in the current interval.

0

SUM-RTDELAY Sum of Round Trip Delays. The total sum of round trip delay (in milliseconds) in the current interval.

0

SUM-SQ-RTDELAY Sum of Square of Round Trip Delays. The sum of square of round trip delays in the current interval.

0

Table 5-26 ESA Monitored Types and Default TCA Settings (Continued)Performance

ParameterDefinition Default

Threshold



TM

5.10 ESA Options and RulesEtherjack Service Assurance (ESA) provisioning and reporting is invoked by selecting the ESA icon on the Tool Bar or selecting ESA from the Applications menu and expanding the system folder in the Menu Tree.

Creating Reflectors and Probes are performed by expanding the Reflectors and Probes entities, entering a right click on one of the LAN entities and selecting Create. See Table 5-27 and Table 5-28 for ESA Reflector and Probe configuration settings, respectively. Default settings are identified in bold.

Note: When the first Probe is created, a virtual interface is created and the first Probe is attached to it. Each additional Probe created will be attached to this same virtual interface. Therefore, the first created Probe cannot be deleted until all other Probes are deleted first. If an attempt is made to delete the first Probe created prior to deleting all other Probes, eVision will display the following error: “webserver:Interface has 1 attached virtual interfaces.”

Note: If the IP address assigned to the Reflector collides with an IP address used by the customer traffic, all packets destined for that IP address will be routed up to the Network Processor.

Table 5-27 ESA Reflector Configuration Settings Parameter Description /


Reflector Id

Reflector identifier (1 to 32 characters - no spaces). This is a user specified unique identifier associated with a Reflector. blank

Reflector IP Address

Reflector IP address. This is a user specified IP address, uniquely associated with an ESA Reflector instance. The IP address must not overlap with any non-ESA related subnets provisioned within the FSP 150CC. (See Note.)

blank

Reflector Subnet Mask

Reflector Subnet mask. 255.255.255.0

Table 5-28 ESA Probe Configuration Settings Parameter Description /


Probe Identification

Probe Id (Create only)

Probe identifier (1 to 32 characters - no spaces). This is a user specified unique identifier associated with a Probe.

blank




TM

Service End Points

Probe IP Address (Create only)

Source (Probe) IP address. This is a user specified IP address, uniquely associated with an ESA Probe instance. This is the IP address to be used in UDP Echo, ICMP Echo or ICMP Timestamp request. The IP address must not overlap with any non-ESA related subnet provisioned within the FSP 150CC. (See Note 1.)

blank

Probe Subnet Mask (Create only)

Probe Subnet mask. 255.255.255.0

Reflector IP Address (Create only)

Destination (Reflector) IP address. This is a user specified IP address, which is the ESA Reflector’s IP address. This is the IP address to be used in UDP Echo, ICMP Echo or ICMP Timestamp request.

blank

Reflector Subnet Mask (Create only)

Reflector Subnet mask. 255.255.255.0

Service Parameters

Protocol (Create only)

Protocol. UDP Echo and ICMP Echo measure the round-trip delay. ICMP Timestamp measures the round-trip delay and one-way delay as well as one-way jitter.

UDP Echo

ICMP Echo

ICMP Timestamp

Service Type

Specifies whether the service is VLAN Tagged or Untagged. (See Note 2.)

Untagged

VLAN Tagged

VLAN ID

Virtual LAN identifier. Provides the ability to monitor a specific service. This option is only applicable when Service Type is set to VLAN Tagged. (See Note 2.)

0 to 4095

N/A

VLAN Priority

Defines the VLAN Priority. This option is only applicable when Service Type is set to VLAN Tagged. (See Note 2.)

0 to 7

N/A

Priority Map Mode Identifies the priority classification mechanism for ESA traffic.

Off

TOS

DSCP

Priority

Specifies the ESA service priority bits. (See Note 2.)

0 to 63 (DSCP)or

0 to 7 (TOS)

Traffic Settings

Packet Size

Set the packet size (in bytes) of the Service Assurance Packets. (See Note 2.)

64-1500

100

Packets per Sample

Set the number of packets per sample. (See Note 2.) 1- 99999

500

Table 5-28 ESA Probe Configuration Settings (Continued)Parameter Description /




TM

Packet Interval

Interval between packets (in milliseconds). (See Note 2.) 1-99999

100

Dead Interval

Setting time (in seconds) after all packets within a sample are sent. (See Note 2.)

1-99999

10

Response Timeout

Set the amount of time to wait for a response (in seconds). Packets received after this timeout are considered lost. (See Note 2.).

1-99999

5

History Configuration

History Bins (Create only)

Number of History Bins (up to a maximum of 32 bins). This is the amount of time between history bins.

1 to 32

16

History Interval (Create only)

History Interval (in minutes). 5 to 60

15

Distribution History Bins (Create only)

Number of Distribution History Bins (up to a maximum of 32 bins). 1 to 32

16

Distribution History Interval (Create only)

Distribution History Interval (in minutes). This is the amount of time between distribution history bins.

5 to 60

15

Statistics and Distribution (Edit Only)

Min.

Round Trip Delay, Oneway Tx Delay, Oneway Rx Delay, Oneway Tx Jitter, or Oneway Rx Jitter

(Edit only)

Minimum delay threshold (in milliseconds). The entry must be less than the entry for Max. Round Trip Delay. (See Note 2.)

-2147483647 to 2147483647

0

Max.


(Edit only)

Maximum delay threshold (in milliseconds). The entry must be greater than the entry for Min. Round Trip Delay. (See Note 2.) -2147483647 to

2147483647

100






TM

Note 1: If the IP address assigned to the Probe collides with an IP address used by the customer traffic, all packets destined for that IP address will be routed up to the Network Processor.

Note 2: Oneway options are only available if ICMP timestamp is set for protocol type. A Probe that is assigned to an active schedule cannot be edited.

Bins


(Edit only)

Number of bins. (See Note 2.) 1-10





TM

5.11 Scheduled Ping and ESA Activity SettingsThe following section describes scheduled activities option settings. Scheduled activities include Scheduled Ping and Scheduled ESA.

Scheduled PingThe Scheduled Ping feature provides a current state of management link connectivity. Up to four IP addresses may be scheduled at a provisioned rate, and should a failure occur, a provisionable alarm (Scheduled Ping Failed) is raised against the IP address.

Scheduled Ping is invoked by selecting the Schedule Activities icon on the Tool Bar or selecting Schedule Activities from the Applications menu, expanding the system folder in the Menu Tree, entering a right click on Scheduled Ping and selecting Edit Settings. See Table 5-29 for Scheduled Ping configuration settings. Default settings are identified in bold.

Note: To remove an IP address, first set the IP address to the Disabled state and select Apply. Then enter 0.0.0.0 into the address field and select OK.

Table 5-29 Scheduled Ping Configuration SettingsParameter Description /


Frequency Time interval between each ping attempt. 1 to 1440 (minutes)

Alarm Severity Alarm severity level raised if the number of attempts indicated in Response Threshold have all failed.

Critical

Major

Minor

Not Reported

Not Alarmed

Response Threshold

Indicates the number of consecutive attempts to make on a failed response before an alarm may be raised against that IP address.

1 to 4

IP Address Up to four IP addresses can be provisioned to automatically ping periodically.

0.0.0.0

Enabled

Enables or disables scheduled ping for that IP address.

Enabled

Disabled




TM

Scheduled ESAA scheduled ESA is invoked by selecting the ESA icon on the Tool Bar or selecting ESA from the Applications menu, expanding the system folder in the Menu Tree, entering a right click on SchGroups and selecting Create New Group. See Table 5-30 for Scheduled Ping configuration settings. Default settings are identified in bold. Up to 10 Scheduled ESA groups may be created.

Once a Scheduled ESA has been created, options available when entering a right click on the Activity ID in the Menu Tree are: Delete, Suspend and Resume. To delete an activity, you must first Suspend the activity.

Table 5-30 Scheduled ESA Configuration SettingsParameter Description /


Activity ID Activity identifier (1 to 32 characters - no spaces). Empty

Schedule Type

Define schedule type as a one time or periodic execution.

One Shot

Periodic

Start Time Buttons

Activate either an immediate ESA or future (scheduled) ESA.

Now

Future

Start Time Entry Windows

The date in format: yyyy-mm-dd and the time in format: hh:mm:ss (24-hour clock time entry). Entry must be greater than the current time. This option is only applicable if Future start time is selected.

yyyy-mm-dd

hh:mm:ss

Duration Buttons

Define the duration as continuous or a fixed time (in seconds).

Forever

Fixed

Duration secs. Entry Window

Define the duration in seconds. Valid entries are 0 (continuous) through 9999 (seconds) if Schedule Type of One Shot is selected, and valid entries are 60 through 9999 (seconds) if Schedule Type of Periodic is selected. This option is only valid if Fixed duration is selected.

N/A

0 to 9999 (One Shot)

60 to 9999 (Periodic)

Periodic Interval

Specifies the interval between subsequent runs (in seconds). This option is only available if Schedule Type of Periodic is selected.

N/A

Range 1 to 99999

Schedule Probes

Selects the Probes that belong to this ESA group. To add a Probe, select a Probe from the Available Probes list and select the Right arrow. To remove a Probe from the Selected Probes list, select the desired Probe and select the Left arrow.

To select multiple Probes, either select the first Probe, then select additional individual Probes by entering a Control+click on each one, or select a contiguous set of Probes by selecting the first Probe, then entering a Shift+click on the last desired Probe in the list.

Only previously created Probes that are not used for another Scheduled Activity are available for selection.

Any available probes will be displayed in the Available Probes list



TM

5.12 CFM Options and RulesThe following section describes Connectivity Fault Management (CFM) option settings. CFM configuration options are created in the following order:

• Configure CFM System Level Parameters

• Configure Default MD Parameters

• Configure CFM VLAN Table

• Configure Maintenance Domain

• Configure Maintenance Association

• Configure Maintenance End Point

• Initiate Loop Back Message

• Initiate Link Trace Message

In addition to configuring CFM options, alarm attributes are editable when the CFM application is selected (see Table 5-20, on Page 5-55).

Configure CFM System Level ParametersCFM system level parameters may be edited by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system folder in the Menu Tree, expanding the Administration entity, entering a right click on the System entity and selecting Edit CFM.

Table 5-31 Configure CFM System Level Parameters Settings Parameter Description /


EtherType CFM System EtherType, in hexadecimal. 0x88b7

Multicast MAC Address

CFM System Multicast MAC Address. 01:80:C2:00:00:0X

Queue Parameters (CFM Service and WAN-1 / WAN-2 CFM Ports)

CIR Defines the Ingress Committed Information Rate (CIR), in bps. Entry of commas are allowed.

320,000

EIR Defines the Ingress Excess Information Rate (EIR), in bps. Entry of commas are allowed.

0

Buffer Size Defines the buffer size for the normal latency queues, in Kilobytes. Entry of comma is allowed.

1

CBS Defines the Ingress Committed Burst Size (CBS), in Kilobytes. Entry of comma is allowed.

1

EBS Defines the Ingress Excess Burst Size (EBS), in Kilobytes. Entry of comma is allowed.

0




TM

Configure Default MD ParametersSystem Level Default Maintenance Domain (MD) level parameters may be created by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system folder in the Menu Tree, entering a right click on the Default Maintenance Domain entity and selecting Edit. The Default MD may be edited by entering a right click on the desired Default MD entity and selecting Edit.

Configure CFM VLAN TableThe CFM VLAN List may be edited by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system folder in the Menu Tree, entering a right click on CFM VLAN Table entity and selecting Create Entry.

To edit or delete an existing CFM VLAN Table entry, select the CFM VLAN Table entity in the menu tree and enter a right click on the desired Primary VID or VID List in the CFM VLAN Table view and select Edit Entry to edit the VID List or Delete Entry to delete the Primary VID and asssociated VID List.

See Table 5-33 for Maintenance Domain configuration settings.

Table 5-32 Configure Default MD Parameters Settings System Level

ParameterDefault MD Parameter

Description / Applicable Rules

Option Settings

System Default MD Level

Level System or specified Maintenance Domain default MD level.

0 to 7

Suystem MIP Creation Control

MIP Creation Control

MIP Creation Control. If Default is selected, the parameters set in the Default Maintenance Domain will be used for MD Level, MIP Creation Control and Default Sender ID Control.

None

Default

Explicit

Table 5-33 CFM VLAN Table Configuration Settings Parameter Description /


Primary VID Primary VLAN Identifier. 1 to 4095

VID List

CFM Virtual Identifier (VID) list. To add a VID member, enter the valid VID number in the VID Entry window and select Add. To delete a VID member, select the VID number in the VID List window and select Remove. The last VID member cannot be removed.

1 to 4095



TM

Configure Maintenance DomainA Maintenance Domain (MD) may be created by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system folder in the Menu Tree, entering a right click on the Maintenance Domain entity and selecting Create. Once an MD is created, only MIP Creation Control may be edited. To edit an MD, expand the Maintenance Domain entity, enter a right click on the desired MD and select Edit. To remove an MD, expand the Maintenance Domain entity, enter a right click on the desired MD and select Delete. Then select OK.

Note: In order to delete an MD, all subordinate entities (MAs and MEPs) must first be deleted.

See Table 5-34 for Maintenance Domain configuration settings. Default settings are identified in bold.

Table 5-34 Maintenance Domain Configuration Settings Parameter Description /


MD ID Maintenance Domain identifier. MD-1 to MD-100

Format Type Selectable Name Entry type.

String

MAC-Integer

DNS Name

No Name

Name

Maintenance Domain name identified by string (if Format Type String is selected) or by DNS Name (if Format Type DNS Name is selected) or by MAC address (if Format Type MAC-Integer is selected).

If Format Type String or DNS Name is selected, allowed characters are: a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not allowed. If Format Type MAC-Integer is selected, the entry must be Hexadecimal characters.

Blank

Level Maintenance Domain level. 0 to 7



None

Default

Explicit




TM

Configure Maintenance AssociationA Maintenance Association (MA) may be created by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system and Maintenance Domain folders in the Menu Tree, entering a right click on the desired Maintenance Domain entity and selecting Create MA.

To edit a Maintenance Association, expand the Maintenance Domain entity, expand the Maintenance Domain ID, enter a right click on the desired MA and select Edit. The following parameters cannot be edited: MA ID, Format Type, Name, Sender ID Control or Primary VID. To edit these parameters, the MA must be deleted and then re-entered with the new desired parameters.

To remove a Maintenance Association, expand the Maintenance Domain entity, expand the Maintenance Domain ID, enter a right click on the desired MA and select Delete. Then select OK.

Note: In order to delete an MA, all subordinate entities (MEPs) must first be deleted.

See Table 5-35 for Maintenance Association configuration settings. Default settings are identified in bold.

Table 5-35 Maintenance Association Configuration Settings Parameter Description /


MA ID Maintenance Association identifier. The MA ID must be unique per system.

MA-mdid-1 to MA-mdid-100

Format Type Selectable Name Entry type.

Integer

Primary VID

String

VPN ID

Name

A Maintenance Association name identified by integer, in Hexadecimal (if Format Type Integer is selected) or by Primary VLAN Identifier (if Format Type Primary VID is selected) or by character string (if Format Type String is selected) or by VPN identifier (if Format Type VPN ID is selected).

If Format Type String is selected, allowed characters are: a-z, A-Z, 0-9, and _@#$%^*-+=:;.?(){}[]|? Spaces are not allowed.

The MA Name must be unique per associated MD.

Blank



TM

CCM Interval

Continuity Check Message (CCM) interval. The same interval must be selected for all MEPs associated with the MA.

3.3 Milli Seconds

10 Milli Seconds

100 Milli Seconds

1 Second

10 Seconds

1 Minute

10 Minutes



None

Default

Explicit

Defer

Primary VID Primary VLAN Identifier. 1 to 4095

MEP List

Maintenance End Point (MEP) list. To add a MEP member, enter the valid MEP ID number in the MEP ID Entry window and select Add. To delete a MEP member, select the MEP number in the MEP ID List window and select Remove. The last VID member cannot be removed. This list must not contain the Primary VID.

1 to 4095

Table 5-35 Maintenance Association Configuration Settings (Continued)Parameter Description /





TM

Configure Maintenance End PointA Maintenance End Point (MEP) may be created by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system and Maintenance End Point folders in the Menu Tree, entering a right click on the desired LAN or WAN entity, and selecting Create.

To remove a Maintenance End Point, expand the Maintenance End Point and LAN interface entities, enter a right click on the desired MEP and select Delete. Then select OK.

To edit a Maintenance End Point, expand the Maintenance End Point and LAN interface entities, enter a right click on the desired MEP and select Edit.

See Table 5-36 for Maintenance Association configuration settings. Default settings are identified in bold.

Table 5-36 Maintenance End Point Configuration Settings Parameter Description /


MEP ID

Maintenance End Point (MEP) identifier. MEP IDs are created when provisioning a MEP list during MA creation/edit. Existing MEP IDs are listed in numerical order according to the selected MA ID. The appropriate MA ID must be selected prior to selecting the MEP ID.

1 to 8191

MA ID Maintenance Association identifier associated with this MEP. The MA must first be created prior to selecting this MA ID.

MA-mdid-1 to MA-mdid-100

Direction Selects the MEP direction. For MEPs associated with a LAN port, only Up is supported.

Up

Down

State

Enable or disable MEP state.

Disabled

Enabled

CCM Generation

Enable or disable Continuity Check Message (CCM) generation.

Disabled

Enabled

Fault Alarm Priority

Selectable fault alarm priority type.

RDI

MAC Status

Remote CCM

Error CCM

XCON CCM

No Defects

VLAN Priority VLAN priority. 0 to 7

Primary VID

Primary VLAN Identifier. Options available are determined by the selected MA’s Primary VID(s) created.

1 to 4095

MA Primary VID



TM

Initiate Loop Back MessageLoop Back Message (LBM) may be initiated by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system, and Maintenance End Point and associated LAN or WAN entity folders in the Menu Tree, entering a right click on the desired MEP entity, and selecting Initiate LBM.

See Table 5-37 for Inititate Loop Back Message configuration settings. Default settings are identified in bold.

Note: The MEP must be set to the Enabled State for the Loop Back Message to be initiated.

Table 5-37 Inititate Loop Back Message Settings Parameter Description /


LBM Destination Type

Selects the LBM destination type. MAC Address

Remote MEP

LBM Destination ID

Allows entry of the destination MAC address or selection of the desired Remote MEP ID.

00:00:00:00:00:00

Number of LBMs to be transmitted

Allows entry of the number of LBMs to be transmitted. 1 to 50

Number of padding bytes in the Data TLV

Allows entry of the number of padding bytes in the Data TLV. 0 to 1461

LBM Data Pattern

Selects the LBM Data Pattern to be sent. All Zeros

All Ones

Alternate

LBM Vlan Priority Selects the LBM VLAN priority. 0 to 7

LBM Vlan Drop Enable

Selects whether LBM VLAN drop is enabled or not. true

false




TM

Initiate Link Trace MessageLink Trace Message (LTM) may be initiated by selecting the CFM icon on the Tool Bar or selecting CFM from the Applications menu, expanding the system, and Maintenance End Point and associated LAN or WAN entity folders in the Menu Tree, entering a right click on the desired MEP entity, and selecting Initiate LTM.

See Table 5-38 for Inititate Link Trace Message configuration settings. Default settings are identified in bold.

Note: The MEP must be set to the Enabled State for the Link Trace Message to be initiated.

Table 5-38 Inititate Loop Back Message Settings Parameter Description /


LTM Destination Type

Selects the LTM destination type. MAC Address

Remote MEP

LTM Destination ID

Allows entry of the destination MAC address or selection of the desired Remote MEP ID.

00:00:00:00:00:00

LTM TTL 1 to 255

LTM Transmit Flags

Selects whether LTM transmit flags are enabled or not. true

false

LTM Egress ID Allows entry of the LTM egress ID. 00:00:00:0B:90:00:40:4B



TM

5.13 Technical DataRefer to the following technical data for site planning and supporting technical information. This section provides the following technical information:

• Connector Pin Assignments

• Power

• Environmental

• Safety, Immunity, Emissions and Compliance

• Technical Specifications List by Functional Area

• Optical Specifications for FSP 150CC SFPs

5.13.1 Connector Pin AssignmentsThe following connector pin assignments are provided:

• RJ-45 10/100 Base-T and 1000 Base-T LAN port connector

• RJ-45 (RS-232 Serial Console port) connector to DB9 adapter connector pin assignments

Refer to Table 5-39 for the RJ-45 10/100 Base-T connector pin assignments and refer to Table 5-40 for 1000 Base-T LAN port connector pin assignments.

Table 5-39 10/100 Base-T LAN Port (RJ-45 Connector)MDI MDI-X 10/100 Base-T

Signal

1 3 TX+

2 6 TX-

3 1 RX+

4 7 -

5 8 -

6 2 RX-

7 4 -

8 5 -




TM

Refer to Table 5-41 for the RJ-45 (RS-232 Serial Console port) connector pin assignments, which follows the EIA/TIA-232-F standard. The FSP 150CC only uses pins 4, 5 and 6. The installation kit also provides an RJ-45 to DB9 conversion adapter (pin assignments are shown in the following table).

Table 5-40 1000 Base-T LAN Port (RJ-45 Connector)MDI MDI-X 1000 Base-T

Signal Name

1 3 BI D1+

2 6 BI D1-

3 1 BI D2+

4 7 BI D3+

5 8 BI D3-

6 2 BI D2-

7 4 BI D4+

8 5 BI D4-

BI D= Bi-directional Data

Table 5-41 RJ-45 (RS-232 Serial Console Port) and DB9 Adapter Pin AssignmentsFSP 150CC

SignalDescription RJ-45 DB9

- Not used 1 -

- Not used 2 -

- Not used 3 -

GND Ground 4 5

TX Transmit Data 5 2

RX Receive Data 6 3

- Not used 7 -

- Not used 8 -



TM

5.13.2 PowerThe FSP 150CCf-825 operates on AC or DC power. AC power converters are available for both 120 VAC and 240 VAC; externally fused at 15A. The system is capable of operating with an AC source with the voltage range specified in ANSI specification C84.1-1989, Voltage Ratings (60 Hz) for Electric Power Systems Equipment, Range B. The equipment shall tolerate any frequency within the range of 60 (+/-3) Hz (or 50 +/- 3 HZ for European applications).

The FSP 150CCf-825 also operates on redundant -48 VDC office battery sources, external fuse rating of 5A. The FSP 150CCf-825 is capable of operating at a voltage range of -36 to -72 VDC with a maximum transient voltage of -75.0 VDC. Power dissipation: 20-24 Watts typical, 30 Watts fully loaded.

The following power components may be ordered separately:

Table 5-42 Power Ordering Options Description Use Part Number

Power Supply Unit (plugs into front of chassis), 120/240 VAC


IEC AC Power Cord (for use with PSU module, part number 0040904010)





North America 0036000158


Switzerland 0036000521

Power Supply Unit (plugs into front of chassis), 48 VDC


Power Adapter, 120/240 VAC (for use with 12 VDC rear panel power connector)



Argentina 0036904019


Australia 0036904017




India 0036904018


Japan 0036904020






TM

5.13.3 EnvironmentalThe FSP 150CCf-825 is targeted for use within office controlled environments. In some instances it might be deployed in uncontrolled environments. The FSP 150CCf-825 operates in the following environmental conditions:

• The system will operate properly in any ambient conditions that are within a temperature range of 0 to +50°C and relative humidity levels up to 95% non-condensing (with a maximum absolute humidity condition of 0.024 kg of water/kg of dry air).

• A single FSP 150CCf-825 shall meet the above operating temperature range requirements without the use of fans or assisted air-flow.

• The system will operate at altitudes within the range of -200ft to 16,500ft (-60m to 5,000m)

• The system supports storage in the temperature range of -40°C to +70°C without any impact on the functionality.

Air Flow RequirementsRefer to Table 5-43 for air flow requirements.

Table 5-43 Air Flow RequirementsAir Flow Requirements

Rack Mounting: Multiple units may be stacked up to 5 rows high in an environmentally controlled environment, such as a Central Office. A heat deflector should be installed between every 5 rows of FSP 150CC NIDs and other equipment.

If it is necessary to install 5 rows of NIDs above other heat producing components, it is recommended that a heat deflector is installed below the NIDs. If it is necessary to install heat sensitive equipment above 5 rows of NIDs, it is recommended that a heat deflector is installed above the NIDs.



TM

5.13.4 Safety, Immunity, Emissions and ComplianceThe system complies with the following product safety standards:

• UL 60950• EN60950• CSA 22.2 No. 60950 Standard for Information Technology Equipment, Including

Electrical Business Equipment• CE Marking safety• TUV EN60950• K.41 Overvoltage Protection

The system complies with the following standards for Electro-Magnetic Compatibility (EMC) and Immunity (EMI):

• FCC Part 15, Class B• IC ES-003, Class B• CISPR 22 (2003), EN55022, Class B, Emissions• CISPR 24 (2002), EN55024, Immunity• EMC Directive (89/336/EEC) (CE Mark)• AS/NZS 3548 (C-Tick Mark)• VCCI, Class B

The system complies with GR-1089-CORE (intra-building voltages) for the following aspects:• ESD• EMI• Lightning• AC Power Fault• Steady State Power• DC Potential Difference• Bonding and Grounding

The system complies with the standards established by the Administrative Council for Terminal Attachments standards (FCC Part 68).

The system complies with GR-63-CORE, NEBS LEVEL 3 requirements for safety for the following aspects:

• Fire Resistance• Office Vibration• Transportation Vibration




TM

5.13.5 Technical Specifications List by Functional AreaRefer to Table 5-44 for technical specifications for all FSP 150CC variants listed by functional area.

Table 5-44 FSP 150CC Technical Specifications Functional Area

Feature / Component

Specifications

Bandwidth

Data Plane Capacity

Up to 1 Gbps Ethernet frame processing

Encapsulation Mode

Ethernet Ethernet

Interfaces

WAN2 - SFP (100FX/1000SX/LX/ZX/BX) optical interfaces, or 10/100/1000 Base-T Ethernet copper interfaces. (For software release 1.1, only one Network port is available for use. The second port will be available for use in a future release.)

Service4 (LAN 1-4): 10/100 Base-T Ethernet copper interfaces

LAN 5: 1 - 100FX/1000 Base X optical interface or 10/100/1000 Base-T Ethernet copper interface

System Hardware

Processor Nitrogen-500 processor, 64 MB Flash, 64 MB SDRAM, 8 MB Boot Memory, 10/100 Base-T LAN Port, RS232 Serial Craft Port

Software Upgrade

Image File Application

Web Interface

FTP (via Web Interface, CLI or SNMP)

Database Backup

Primary Non-volatile memory

Secondary Remote database backup

Copy ApplicationWeb Interface

FTP (via Web Interface, CLI or SNMP)

System Configuration

Terminal

Protection

1+1 Link aggregation on Network ports (For software release 1.1, only one Network port is available for use. The second port will be available for use in a future release.)

Network Interface - WAN

Ports 1 x 100/1000 Base-T or 100FX/1000 Base X. For software release 1.0, only one Network port is available for use. The second port will be available for use in a future release.



TM

Reach

100BaseT: 100 meters

1000BaseT: 100 meters

100FX/1000SX/LX/ZX/BX optical: SFP dependant

Duplex Full, Auto

Line Rate10/100/1000 Base-T: 10/100 Mbps, Full or Auto, 1000 Mbps Auto

100FX/1000SX/LX/ZX/BX: 100 Mbps Full, 1000 Mbps Auto

MTU Size 2004 bytes if Jumbo Frames are Disabled, 9250 bytes if Jumbo Frames are Enabled

VLANs 4095

Service Parameters

802.1Q & 802.1QQ, Tag Stacking, Tag Swapping/Translation

Flow Control CIR, EIR, CBS, EBS, burstsize (on port, VLAN or priority basis)

Rate LimitingOptional 802.1Q flow control.

Ingress and Egress rate limiting up to line rate with 64 Kb resolution for port and VLAN

Burst Size Up to 8 MB with 64 KB resolution

Priority 802.1p/TOS/DSCP

Diagnostics

Terminal or Facility Loopback (constant or timed)

Connection Performance Analyzer for Ethernet test pattern generation

Automatic Cable removal detection


Etherstats - RMON RFC-2819 plus proprietary data rate counters

Etherjack® Counters

Current and history bins (per GR-820)

Threshold settings and TCA Events are supported for all (relevant) Ethernet stats

Connectors LC on SFP (fiber), RJ45 (copper)

Ethernet Services - LAN

PortsLAN 1 to 4: 10/100 Base-T, MDI/MDI-X copper interfaces

LAN 5: 1 x 10/100/1000 Base-T, MDI/MDI-X for copper interface, or 1 x 1GbE optical interface (SMF/MMF)

ReachLAN 1 to 4: 10BaseT: 150 meters, 100BaseT: 100 meters

LAN 5: 1000BaseT: 100 meters, 100FX or 1GbE optical: SFP dependant

Duplex Full, Half, Auto

Line RateLAN 1 to 4: 10 Mbps, 100 Mbps, Auto.

LAN 5: 10/100 Mbps, Full, Half, Auto, 1000 Mbps, Full, Auto.

Table 5-44 FSP 150CC Technical Specifications (Continued)Functional Area

Feature / Component

Specifications




TM

MTU Size LAN 5: MTU Size is determined by the selection made for Jumbo Frames. If Jumbo Frames is Enabled, then MTU Size is 9250. If Jumbo Frames is Disabled, then MTU Size is 2000. LAN 1 to 4: MTU Size is fixed at 2000.

VLAN s 4095 per system

Service Parameters

802.1Q & 802.1QQ, Tag Stacking, Tag Swapping/Translation

Flow Control CIR, EIR, CBS, EBS, burstsize (on port, VLAN or priority basis)

Rate LimitingOptional 802.1Q flow control.

Ingress and Egress rate limiting up to line rate with 64 Kb resolution for port and VLAN

Burst Size Up to 8 MB with 64 KB resolution

Priority 802.1p/TOS/DSCP

Diagnostics

Terminal or Facility Loopback (constant or timed)

Terminal or Facility VLAN Loopback (up to three VLANs)

Etherjack® Physical Layer Diagnostics

Connection Performance Analyzer for Ethernet test pattern generation

Automatic Cable removal detection

RFC-2544 (when using nVision Network Management System)


Etherstats - RMON RFC-2819 plus proprietary data rate counters

Etherjack® Counters

Current and history bins (per GR-820)

Threshold settings and TCA Events are supported for all (relevant) Ethernet stats

ConnectorsLAN 1 to 4: RJ45 (copper)

LAN 5: 1 x RJ45 (copper), or 1 x LC on SFP (fiber)

System Time

System Date/Time Mode

Manual

SNTP

Communications

Management LAN Port

10/100 Base-T, RJ-45 on front panel

MTU size: 1500


Auto-MDIX capability


Feature / Component

Specifications



TM

Craft TerminalRJ-48 RS-232 serial port on front panel, 9600 baud (N-8-1)

Auto negotiation supported (operational range 4800 to 57600 baud)

Management Tunnel

VLAN in Ethernet payload on LAN and WAN interfaces

MAC based Management Tunnels on LAN and WAN interfaces

The system supports simultaneous management tunnels on all interfaces

Network Protocol TCP/IP (IPv4)

Routing Protocol RIP V2, static routing

OAMP Telnet/SSH CLI interface, HTTPS based GUI interface, SNMP v1, v2c, and v3

User Authentication

RADIUS

TACACS+

Access Control Lists

Up to 10 Access Control Entries

Port Authentication 802.1x

Mechanical and Power

Power

One or two pluggable AC or DC power supplies, and rear accessible 12 VDC input DIN connector.

Power Dissipation: 20-24W typical, 30W fully loaded

External AC power fuse rating: 15A

AC power converter (for rear power connector) may be ordered separately for North American and international locations.

AC Power Unit

Operating Voltage Range: 120 or 240 VAC

Frequency Range: 60 +/- 3 Hz or 50 +/- 3 Hz (European)

Maximum power consumption: 40W

External AC power fuse rating: 15A

The AC power connector is a 3 prong male socket accepting a North American standard AC power cord.

DC Power Unit

Operating Voltage Range: -36 to -72 VDC

Maximum power consumption: 40W

External power fuse rating: 5A

The DC power connector is a 3-pin socket (Battery, Return, Ground) which provides a mated connector providing protection against improper (reversed polarity) installation.

Over-voltage and reverse polarity protection

Dimensions: 1.75 inches (H), 17.2 inches (W) and 8.6 inches (D)


Feature / Component

Specifications




TM

Weight: Approx.9 lbs.

Emissions / Immunity

NEBS Level 3, UL 60950, CSA22.2-60950, 21-CFR-1040, GR-1089

SafetyCFR 14 - Part 68, Part 15 (FCC), CS-03 (Industry Canada)

NEBS level 3, GR-1089

Mounting

Wall mount, 19” rack mount or 23” rack mounting options are available.

Multiple units may be stacked up to 5 rows high in an environmentally controlled environment, such as a Central Office. A heat deflector should be installed between every 5 rows of FSP 150CC NIDs and other equipment. If it is necessary to install 5 rows of NIDs above other heat producing components, it is recommended that a heat deflector is installed below the NIDs. If it is necessary to install heat sensitive equipment above 5 rows of NIDs, it is recommended that a heat deflector is installed above the NIDs.

Front Connectors

MGMT LAN (RJ-45) - Management LAN interface

RS-232 (RJ-45) - Serial management interface

WAN Optical Connector Type LC 1 GbE / 100 FX port

WAN (RJ-45) - LAN 10/100/1000Base T interface

4 x LAN (RJ-45) - LAN 10/100Base T interfaces

LAN Optical Connector Type LC 1 GbE port

LAN (RJ-45) - LAN 10/100/1000Base T interface

Rear Connector AC Power - lockable 2 prong for 120/240 VAC to 12 VDC converter

Optical

Optical See Table 5-45, on Page 5-96.

Environmental

Temperature (operating)

0ºC to +50ºC

No fans required

Temperature (storage)

-40ºC to +70ºC

Humidity 5% to 95%, non-condensing

Safety and Compliance

NEBS NEBS Level 3, GR-63

Electrical GR-1089-CORE

Safety 60950, CE Marking

EMC / EMIFCC Part 15 Class B, IC CS-003 Class B, CISPR 22 (2003) EN55022 Class B Emissions, CISPR 24 (2002) EN55024 Immunity, EMC Directive (89/336/EEC) (CE Mark), AS/NZS 3548 (C-Tick Mark), VCCI Class A


Feature / Component

Specifications


840-00028-02 Rev 1.0

Copyright ©

2007 AD

VA O

ptical Netw

orking - CO

NFID

ENTIA

LPage 5-96

Installation and Operations M

anual FSP 150CC

f-825C

hapter 5 - Configuration Settings and Technical D

ataR

elease 1.2, Novem

ber 2007O

ptic

alN

etw

ork

ing

TM

Reach Temp. Range

Mode Wavelength

50um 62.5um

10m 10m

0 0 0 to +70 SMF 1310 TX, 1550 RX

0 0 0 to +70 SMF 1550 TX, 1310 RX

0 0 -40 to +85 SMF 1310

0 0 -40 to +85 SMF 1550

0 0 0 to +70 SMF 1310

0 200 0 to +70 MMF 1310

0 0 -40 to +85 SMF 1310 TX, 1490 RX

0 0 -40 to +85 SMF 1490 TX, 1310 RX

55 55 -40 to +85 SMF/MMF

1310

0 0 0 to +70 SMF 1310

0 0 0 to +70 SMF 1310 TX, 1490 RX

0 0 0 to +70 SMF 1490 TX, 1310 RX

50 30 -20 to +85 MMF 850

30 15 0 to +70 MMF 850

0 0 0 to +70 SMF 1470

0 0 0 to +70 SMF 1490

0 0 0 to +70 SMF 1510

0 0 0 to +70 SMF 1530

0 0 0 to +70 SMF 1550

5.13.6 Optical Specifications for FSP 150CC SFPsRefer to Table 5-45 for FSP 150CC SFP optical specifications.

Table 5-45 Optical Specifications for FSP 150CC SFPs ADVA Part

Number

DescriptionTXCVR OPTIC SFP

Manufac-turer

Manufacturer Part Number

Opti-cal

PM?

RX Sensitivity RX Max

(Error)

RX Dam-age

TX Out

LOS Max 9um

Min Max Min Typ Max 1km

61004002 100BX/OC3, T-1310, R-1550, SMF, 20KM, IR-1, C-TEMP

Formerica BIDI-1315-0161-001 Y -45 -32 -32 0 N/S -14 -8 20

61004003 100BX/OC3, T-1550, R-1310, SMF, 20KM, IR-1, C-TEMP

Formerica BIDI-1513-0161-001 Y -45 -32 -32 0 N/S -14 -8 20

61004004 100FX/OC3, 1310NM, SMF, 40KM, LR-1, I-TEMP

Sumitomo SCP6811-GL-ZWE Y -45 -34.5 -34 -10 3 -5 0 40

61004005 100FX/OC3, 1550NM, SMF, 80KM, LR-2, I-TEMP

Sumitomo SCP6861-GL-ZWE Y -45 -34.5 -34 -10 3 -5 0 80

61004017 100FX/OC3, 1310NM, SMF, 15KM, IR-1, C-TEMP

Fiberxon FTM-3101C-L15G Y -45 -37 -34 -8 N/S -5 0 15

61004006 100FX, 1310NM, MMF, 2KM, C-TEMP Stratos Lightwave

SPLC-20-1-4-B N -45 -29 -29 N/S N/S -22 -14 0

61004010 1000BX, T-1310, R-1490, SMF, 10KM, C-TEMP

Sumitomo SBP6H44-GL-NB-31

Y -30 -21 -20 -3 3 -9 -6 -3 10

61004011 1000BX, T-1490, R-1310, SMF, 10KM, C-TEMP

Sumitomo SBP6H44-GL-NB-49

Y -30 -21 -20 -3 3 -9 -6 -3 10

61004009 1000LX, 1310NM, SMF/MMF, 10KM/550M, I-TEMP

Sumitomo SCP6844-GL-ZWE Y -30 -21 -20.5 -3 3 -9.5 -6 -3 10

61004012 1000LX, 1310NM, SMF, 40KM, C-TEMP Sumitomo SCP6814-GL-ZNE Y -30 -23 -22.5 0 3 -4.5 0 40

61003018 1000LX, T-1310, R-1490, SMF, 40KM, C-TEMP

ADVA 61003018 Y -45 -23 -22 -3 N/S -5 2 40

61003019 1000LX, T-1490, R-1310, SMF, 40KM, C-TEMP

ADVA 61003019 Y -45 -23 -22 -3 N/S -5 2 40

61004008 1000SX, 850NM, MMF, 700M, C-TEMP Finisar FTLF8519P2BNL Y -30 -20 -20 0 N/S -9 -3 0

Fiberxon FTM-8120C-L Y -30 -18 -20 0 N/S -9.5 -6 -1.5 0

61003020 1000XD, 1470NM, SMF, C-TEMP ADVA 61003020 Y -36 -24 -24 -3 N/S -3 2 50





840-00028-02 Rev 1.0

Copyright ©

2007 AD

VA O

ptical Netw

orking - CO

NFID

ENTIA

LPage 5-97

Installation and Operations M

anual FSP 150CC

f-825C

hapter 5 - Configuration Settings and Technical D

ataR

elease 1.2, Novem

ber 2007O

ptic

alN

etw

ork

ing

TM

0 0 0 to +70 SMF 1570

0 0 0 to +70 SMF 1590

0 0 0 to +70 SMF 1610

0 0 -40 to +85 SMF 1550

0 0 0 to +70 SMF 1550

ed)Reach Temp.

RangeMode Wavelength

50um 62.5um

10m 10m




61004014 1000ZX, 1550NM, SMF, 80KM, I-TEMP Sumitomo SCP6874-GL-ZWE Y -30 -24.5 -24 -3 3 -2 3 80

61003011 1000ZX, 1550NM, SMF, 100KM, C-TEMP ADVA 61003011 Y -43 -32 -32 -9 N/S 0 5 100

Table 5-45 Optical Specifications for FSP 150CC SFPs (ContinuADVA Part

Number

DescriptionTXCVR OPTIC SFP

Manufac-turer

Manufacturer Part Number

Opti-cal

PM?

RX Sensitivity RX Max

(Error)

RX Dam-age

TX Out

LOS Max 9um

Min Max Min Typ Max 1km


TM



CCf825_INST_OPS R1[1].2.pdf

Documents

Transcript of CCf825_INST_OPS R1[1].2.pdf