Product Release Note

Tellabs 6325 Edge NodeFeature Pack 1.2 SP2

Tellabs Denmark A/S Lautrupvang 3C DK-2750 Ballerup Denmark Tel: +45.44.73.30.00 Fax: +45.44.73.30.01 www.tellabs.com

Introduction This Product Release Note launches Tellabs 6325 Edge Node, FP 1.2 SP2.

Feature Pack 1.2 introduces features: Performance monitoring of E1 signals, E3/DS3 interfaces and WDM multiplex capabilities including transponders and muxponders.

Service Pack 2 corrects a number of problems identified in the Embedded software for the node.

Feature Pack 1.2 Tellabs6325EdgeNode,FP1.2launchesthefollowingnewhardware:

SDH and PDH Interface Module with PDH monitoring (SPIMXm) The new SPIMXm module makes it possible to monitor performance (Near End and Far End performance monitoring) for E1 signals according to ITU-T Recommendation G.704. Performance can be monitored for all E1s in the node independently of whether these interfaces are located on a PIM1 module or a SPIMXm module.

SDH and PDH Interface Module with STM-16 (SPIMX16m) The new SPIMX16m is identical to the above module, but with an additional option for STM-16 interface. One SDH SFP slot supports STM-1, STM-4 and STM-16 SFP transceivers, whereas the other one supports STM-1 and STM-4 SFP transceivers.

PDH Interface Module with E3/DS3 (PIM3P) The PIM3 module contains six E3/DS3 interfaces. The interfaces are individually configurable from the management system meaning that the can be set to either E3 (34 Mbit/s) or DS3 (45 Mbit/s). Using two of these modules the node also offers equipment protection of the interfaces.

Wavelength Division Multiplexers (OM-C, OM-D, OAD1-C and OAD1-D) Two eight channel WDM multiplexer modules are part of this release: One supporting CWDM (OM-C) and another supporting DWDM (OM-D). Furthermore, two single-channel Optical Add/Drop (OAD) WDM multiplexer modules are provided: The OAD1-C (CWDM) and OAD1-D (DWDM).

Transponder / Repeater module (TR4) The TR4 module provides four transponder functions each of which may convert a standard non-coloured STM-4, STM-16, Gigabit Ethernet or Fibre Channel FC-100 or FC-200 interface signal to a CWDM / DWDM wavelength. Using SFP pluggable transceivers each of the four transponder functions can also be used as a repeater function if a wavelength has to pass longer distances than one single CWDM / DWDM transceiver is able to reach.

The following trademarks and service marks are owned by Tellabs Operations, Inc., or its affiliates in the United States and/or other countries: TELLABS, Tellabs and T symbol, and T symbol. Any other company or product names may be trademarks of their respective companies.

One Tellabs Center 1415 West Diehl Road Tellabs reserves the right to change the above specifications without notice. Naperville, IL, 60563, USA +1.630.378.8800 Fax: +1.630.852.7346 2009, Tellabs. All rights reserved. 6325_rn017_1

6325_rn017_1 Page: 2 of 5

Feature Pack 1.2, continued

Muxponder (MP4) The MP4 module can be used as transponder and repeater in the same way as the TP4 module. In addition to that the module includes two muxponder functions that each multiplex two (client) signals into a single 2.5Gbit/s signal. The client signals can be Gigabit Ethernet and FC-100.

CWDM transceivers for Gigabit Ethernet The transceivers are available in eight wavelengths from 1471nm to 1611nm. The transceivers have an attenuation range so they can reach up to 120km.

DWDM transceivers for STM-16, STM-4 and STM-1 The transceivers are available in more than 40 wavelengths in the range from 1528nm to 1566nm. The transceivers have an attenuation range so they can reach up to 80km. The transceivers can reach up to 120km. without external dispersion compensation.

Fibre Channel Fibre Channel transceivers are also qualified as part of this Feature Pack. SFP Transceivers supporting FC-100, FC-200 and FC-400 are supported and are available in 850nm, 1310nm and as CWDM and DWDM transceivers. The Fibre Channel transceivers can be used together with the TP4 and MP4 modules.

Management via GFP-F DCC As an additional option for the EMAP module it is now possible to multiplex a DCC channel into the GFP-F data stream when mapping Ethernet into SDH or PDH.

Management via IP DCN It is possible to manage the Network Element using TCP/IP protocol instead of OSI TP4 protocol. This makes it possible to use routers without OSI routing capability in the DCN network. The Network Element still uses OSI CLNS and OSI IS-IS protocol on the DCC channels. The IP protocol is automatically tunnelled over OSI on the DCC channels to other Tellabs Network Elements. Please note that if third party Network Elements are part of the network those Network Elements must be OSI CLNS and IS-IS compatible.

New Hardware Items Item Number Description

CM3574A SPIMXMMDL,2XSTM1/4,21XE1,MONXC

CM3575 SPIMX16MSTM1/4/1621XE1XC

CM3579 PIM3PMODULE,6XE3/DS3

CM3580C OMCCWDMMUX8XCHANNELS

CM3580D OMDDWDMMUX8XCHANNELS

CM3581Cxxx OAD1CCWDM1XCHANNEL1xxxNM

CM3581Dxxx OAD1DDWDM1XCHANNEL19x.xxTHZ

CM3582 TR4TRANSP/REPEAT4XCHANNELS

CM3585 MP4MUXPONDER4XCHANNELS

TR0018xxx FOSTM16DWDM19x.xxTHZ

TR0024xxx FOGBECWDM1xxxNM

TR0027 FO10/100BASET

6325_rn017_1 Page: 3 of 5

ItemNumber Description

TR0029 FOFIBRECHANNEL850NM

TR0030 FOFIBRECHANNEL1310NM

TR0031xxx FOFIBRECHANNELCWDM1xxxNM

TR0032xxx FOFIBRECHANNELDWDM19x.xxTHZ

Order Number Description Embedded software identification

SW6325-0012M200 ESW FP1.2, CD-ROM

Subrack File name Identification of Software FP 1.2 SP2

ESW Tellabs 6325 node 6325_fp1.02_107.zip

Subrack File name Identification of Bootprom

Boot-SW Tellabs 6325 node 6325_boot_051.zip

Module name File name Identification of Firmware

EMAP, MP4, TR4, SPIMXm and SPIMX16m 6325_fpga_087.zip

Module name File name

ETEX10S l2sm-r2.3-2.27.img

Identification of ESW for ETEX

This is the version of ETEX SW this Service Pack has been tested with. Please note that ETEX software is not included on Tellabs 6325 ESW CD, but has to be ordered separately on item number: SW-ETEX-M200. For latest ETEX ESW please check the latest ETEX Release Notes.

Item number Release Management System

NM63-CA03.00.05 Feature Pack 3.0 SP5 Tellabs 6300 Craft Terminal

Management Software Requirements

NM63-CB03.00.05 Feature Pack 3.0 SP5 Tellabs 6300 Extended Craft Terminal

NM63-RA03.00.05 Feature Pack 3.0 SP5 Tellabs 6300 Network Manager

6325_rn017_1 Page: 4 of 5

Related Manuals Item no. Description

MA365 Rev. C Tellabs 6325 Edge Node, Hardware Installation Manual

MA368 Rev. E Tellabs 6300 Network Manager, Managing Tellabs 6325 Edge Node

MA336 Rev. K Tellabs 6300 Network Manager, Using the Craft Terminal

MA345 Rev. G Tellabs 6300 Network Manager, Managing ETEX

MA359 Rev. A Tellabs 6300 Network Manager, DCN Planning Guide

MA351 Rev. F Tellabs 6300 Network Manager, Managing the DCN for ETEX

EPR No. / CMS no. Problem description Solved irregularities in FP1.2 SP2, BV107 compared to FP1.2 SP1, BV099

8791 / After more than 2000 zip-operation, e.g. backups, the pre-allocated memory for zip operations is consumed and an LMIP error is raised.

8794 / 114522 In some nodes it is seen that it hasnt been possible to open Equipment View/Traffic Management dialogs from the manager.

9372 / 139922 When synchronization of a Tellabs 6325 node is in free-running mode it is seen that bit errors may occur in a multiplexed GbE signal on an MP4 module.

9273 / 141833 In modules with E1s a LOS alarm will clear when only one of the pins in the balanced E1 Rx signal is connected. It should only clear when there is signal on both Rx pins.

9275 / 138542 With a GbE signal mapped into STM-16 signal in an MP4 module the VC-4 alarms occurring if the external STM-16 signal is disrupted are not always as specified. Furthermore they can be instable.

9635 / 151485 With a PIM3P module connected to a Cisco Router over an E3 signal, and the payload of the E3 from the Router is ATM, CRC errors caused by the PIM3P module are generated.

EPR No. / CMS no. Problem description Work around Known irregularities in FP1.2 SP2, BV107

None

6325_rn017_1 Page: 5 of 5

Upgrade paths To upgrade to FP1.2 SP2 from FP1.1 the following steps are recommended:

First of all make a backup of the existing node configuration. It is important the Boot prom is updated before updating the ESW. It is furthermore recommended to upgrade ESW before upgrading the FPGA code on

the EMAP module. If the FPGA is upgraded first a critical alarm (GFP_UPI mismatch) will occur and an additional reset of EMAP module is needed). The alarm is not traffic affecting except for the 2 seconds it takes to reset the EMAP module again.

To upgrade to FP1.2 SP2 from FP1.2 SP1 the following steps are recommended:

First of all make a backup of the existing node configuration. It is furthermore recommended to upgrade ESW before upgrading the FPGA code on

the EMAP module. If the FPGA is upgraded first a critical alarm (GFP_UPI mismatch) will occur and an additional reset of EMAP module is needed). The alarm is not traffic affecting except for the 2 seconds it takes to reset the EMAP module again.

To upgrade to FP1.2 SP2 the following upgrade paths are recommended:

Tellabs 6325 FP1.2 SP1 (BV099) Tellabs 6325 FP1.2 SP2 (BV107) Tellabs 6325 FP1.1 SP4 (BV112) Tellabs 6325 FP1.2 SP2 (BV107)

No other combinations are tested. Hence if other releases or build vectors are currently running, it is recommended to update to one of above Build Vectors before upgrade.

Roll back procedure To downgrade the SDH node to original Feature Pack (FP) and Build Vector (BV) the procedure is described in the Tellabs 6300 manual MA368.