8000 inm sr6.0 service pack 3 bug notes

8000 Intelligent Network Manager SR6.0 ServicePack 3

Bug Notes

76.8060-70210D09.12.2014

Document Information

Revision History

Document No. Date Description of Changes

76.8060-70210D 09.12.2014 Bug Notes for 8000 Intelligent Network Manager SR6.0 servicepack 3 have been added.

76.8060-70210C 07.10.2014 Bug Notes for 8000 Intelligent Network Manager SR6.0 servicepack 2 have been added.

76.8060-70210B 11.07.2014 Bug Notes for 8000 Intelligent Network Manager SR6.0 servicepack 1 have been added.

© 2014 Coriant. All rights reserved.

This manual is protected by U.S. and international copyright laws, conventions and treaties. Your right to use this manual issubject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification,

distribution, display or other use of this manual may result in criminal and civil penalties.

The specifications and information regarding the products in this manual are subject to change without notice. All statements,information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,

express or implied. Users must take full responsibility for their application of any products.

Adobe® Reader® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

8000 Intelligent Network Manager SR6.0 Service Pack 3 76.8060-70210DBug Notes © 2014 Coriant.

2

Table of Contents

Table of Contents

About the Manual .............................................................................................................. 4

Objectives....................................................................................................................................................................... 4Audience......................................................................................................................................................................... 4Document Conventions .................................................................................................................................................. 4Product Name Rebranding ............................................................................................................................................. 4Documentation Feedback............................................................................................................................................... 5

1 Known Bugs ................................................................................................................ 6

1.1 5500 Node Management...................................................................................................................................... 61.2 6300 Node Management...................................................................................................................................... 61.3 7100 Element Support ......................................................................................................................................... 61.4 8600 Node Management...................................................................................................................................... 101.5 8800 Element Support ......................................................................................................................................... 111.6 Accounting Management..................................................................................................................................... 121.7 Dashboard............................................................................................................................................................ 121.8 Database............................................................................................................................................................... 121.9 Element Software Management........................................................................................................................... 131.10 Fault Management ............................................................................................................................................... 131.11 Macro Manager.................................................................................................................................................... 131.12 Management Server ............................................................................................................................................. 141.13 Network Editing Tools......................................................................................................................................... 141.14 Northbound Interface........................................................................................................................................... 161.15 Performance Management ................................................................................................................................... 171.16 Router .................................................................................................................................................................. 181.17 Security................................................................................................................................................................ 221.18 Tunnel Engineering ............................................................................................................................................. 221.19 VPN Provisioning................................................................................................................................................ 221.20 Web Reporter ....................................................................................................................................................... 24

76.8060-70210D 8000 Intelligent Network Manager SR6.0 Service Pack 3© 2014 Coriant. Bug Notes

3

About the Manual

About the Manual

Objectives

This manual lists the known bugs of 8000 Intelligent Network Manager.

Audience

This manual is intended for system installation and administration personnel, system specialists andoperators.

Document Conventions

Known bugs prior to SR3.0 can be found in the Tellabs® 8000 Intelligent Network Manager SR2.2Service Pack 2 Bug Notes document.

The following table defines the concepts that may be shown in the context of a particular bug.

Concept Description

Release published Specifies the first product release in which the bug has initially beenpublished in the Bug Notes document.

Product family Identifies the network element product family/families which the bugis related to.

PPN ID Specifies the Product Performance Notice identification numberassociated with the bug.

Workaround Describes the viable workaround procedure for the issue in the bug.

Product Name Rebranding

Product names are being rebranded and as a result the product name format consists of a numericalidentifier and a descriptive part.

Additionally, the previous Tellabs 7300 product family is renamed and the individual product namesare also changed. The table below lists previous and new product names. You may see instancesof both the previous and the new product names in the customer documents during the transitionperiod to the new naming system.

Previous Product Name New Product Name

Tellabs® 7300 metro Ethernet switching series 7090 Packet Transport Platform Series

Tellabs® 7305 7090-05 CE


4

About the Manual

Previous Product Name New Product Name

Tellabs® 7307 7090-07 CE

Tellabs® 7310 7310

Tellabs® 7325 7090-25 CE

Tellabs® 7345 7090-45 CE

Documentation Feedback

Please contact us to suggest improvements or to report errors in our documentation:

Email: [email protected]


5

1 Known Bugs

1 Known Bugs

1.1 5500 Node Managementt8000244079 In the 5500 Node Manager Microtopology view the discovery of the 5500

terminations fails.Release published: SR6.0-SP1Product family: 5500

1.2 6300 Node Managementt8000167499 The Unit Configuration pop-up menu is incorrectly offered for the 6300 ETEX

units by Node Editor as 6300 ETEX units do not have such a parameter andtherefore the offered configuration menu is incomplete (has empty menu items).If you still select any of the configurations, execution is terminated with thefollowing error: Error(600) The feature has not been implemented yet.Release published: SR3.0Product family: 6300

1.3 7100 Element Supportt8000258678 The Anyrate interface of the OSM-20 GOPT-ODU-O-7100 module has only the

ODUflex support and the 8000 INM support for ODU0 and ODU1 is missingfor this interface.Release published: SR6.0-SP3Product family: 7100

t8000257497 Optical circuits routed over the OTM-1 trunks between the 7100 and/or mTeranodes are not properly discovered if the OTM-1 trunks are in Planned state.Release published: SR6.0-SP3Product family: 7100, mTeraWorkaround: Raise the state of the OTM-1 trunks to In Use before runningthe optical circuit discovery.

t8000256547 After restarting Communication Server, the 7100 SNMP Adapter may operatewith a delay.Release published: SR6.0-SP2Product family: 7100

t8000256445 The 7100 SNMP Adapter fails to use the new 7100 NE SNMP username andpassword if they are changed after starting a server.Release published: SR6.0-SP2Product family: 7100Workaround: Restart Communication Server or the GSCOMM process.


6

1 Known Bugs

t8000255660 In 7100 Node Manager, the OTS Path (DWDM Link) report under Line SideFacilities does not include the number of supported channels or a managementsystem generated alarm when a mismatch of span channel limits occurs.Release published: SR6.0-SP3Product family: 7100

t8000253815 8000 INM does not support alien wavelength or direct connect using the 7100OTM-1 interfaces of the DXOADM unit.Release published: SR6.0-SP3Product family: 7100

t8000252494 After a Topology Link has been created using Network Builder, the assigneddefault name is incorrectly truncated in the Topology Link Properties dialog andin the queries.Release published: SR6.0-SP3Product family: 7100

t8000251416 In Router it is not possible to set up a Y-cable protected optical channel circuitwhere each subcircuit has one endpoint associated with the working Y-cableprotection interface and the other with the protecting Y-cable protection groupinterface. It is possible to create this connection in the hardware but the opticalcircuit discovery does not discover the circuit at all.Release published: SR6.0-SP2Product family: 7100

t8000250049 Optical circuits corresponding to the TGTM-E, FGTM, FGTM-E, HGTM andHDTG Y-Cable protected client interfaces are discovered by 7100 optical circuitdiscovery as one Y-cable protected circuit with two subcircuits. If discoveryfinds this type of a connection already represented in Router by two separateoptical circuits it erroneously shows "Internal processing error encountered" in thediscovery GUI. Additionally, a workstation trace.log shows the following: "Debuginfo: Circuit::IsSimilarTo, conflicting end point count".Release published: SR6.0-SP1Product family: 7100

t8000248165 In 7100 Node Manager, it is not possible to create a one-way cross connect withthe source and destination on the same STS/VC facility.Release published: SR6.0-SP1Product family: 7100Workaround: Use Craft Station or TL1 cut through to create such a cross connect.

t8000248161 In 7100 Node Manager, it is not possible to create a one-way cross connect withthe source and destination on the same ODU facility.Release published: SR6.0-SP1Product family: 7100Workaround: Use Craft Station or TL1 cut through to create such a cross connect.

t8000246808 In Node Editor, when creating interfaces in which the corresponding 7100 facilityhas the CBR Mapping parameter, the default value is erroneously used.Release published: SR6.0-SP1Product family: 7100Workaround: If needed, change the value using 7100 Node Manager, CraftStation or TL1.


7

1 Known Bugs

t8000245808 In 7100 Node Manager, alarms on FGTM-E are not displayed in the Alarm Historyin the Navigation right pane window.Release published: SR6.0-SP1Product family: 7100

t8000245664 7100 Node Manager Navigation Tree 'standby' symbols may sometimes indicateprotection when none exists on an entity.Release published: SR6.0-SP1Product family: 7100

t8000242802 When raising the state of a unit, module or interface in a 7100 port shelf subrack,and the main shelf or the SPM/SPMN/SPM-H unit of the main shelf is missing,there is a misleading and uninformative error "SPM/SPMN/SPM-H unit in slot0 of the main shelf subrack is in PLANNED state. Please update its state beforechanging unit state.".Release published: SR6.0Product family: 7100

t8000242657 It is not possible to create LAN 10G interfaces with Facility MappingFRAME_STD in the 7100 HDTG unit using Node Editor.Release published: SR6.0Product family: 7100

t8000239028 When a 7100 NE is under major maintenance, or when it is producing a largenumber of database change messages, 7100 Node Manager may report the networkelement to be out of sync with the message DB Change Pipe Overflow.Release published: SR6.0Product family: 7100Workaround: Right-click the NE in the 7100 Node Manager navigation treeand select Reconnect.

t8000238511 For a 7100 network element it is in some cases possible to change e.g. an OADMunit to another OADM unit of a different type without removing circuits, trunks,interfaces, modules or a unit. The change is made by replacing the modulephysically and by provisioning the change using 7100 Node Manager, 7191 CraftStation or TL1. However, the change cannot be made by the 7100 equipmentdiscovery, but it has to be done manually.Release published: SR6.0Product family: 7100Workaround: Change the unit type manually in the 8000 Intelligent NetworkManager database using the Change Unit type to menu option in Node Editor.

t8000235224 The discovery of 7100 Packet Subsystem (PSS) is not supported. The SMTM-P,TGIM-P and ESM20 packet units are discovered, but the modules and interfacesof the packet units are not discovered. Additionally, the PSS units, the relatedvirtual switches and LAG groups are not discovered.Release published: SR6.0Product family: 7100

t8000232803 The Logical VLAN Interface application may show an uninformative "Interfacewith VLAN ID %1 already exists" error when creating interfaces.Release published: SR5.1Product family: 7100


8

1 Known Bugs

t8000224811 It is not possible to use paired TGTM-E units with fibered connections forthe OEO regeneration of the optical circuits. Only backplane connections aresupported when paired units are used.Release published: SR5.1Product family: 7100

t8000224639 The client-side UPSR/SNCPRing protection is missing from the OC-3/12/48 andSTM-1/4/16 interfaces in the SSM-D and SSM-X units in Node Editor.Release published: SR5.0-SP1Product family: 7100

t8000223167 The Test tab in the 7100 Node Manager Microtopology view may have somemissing facilities for circuits involved with the DPRING integrated TGLANprotected circuit using HDTG or UPSR with STM4.Release published: SR5.1Product family: 7100Workaround: If the facilities are not presented in the Microtopology Test tab,perform the BER testing by right-clicking the corresponding objects in the NodeManager navigation tree.

t8000220985 The OTU interface faults are not mapped to the corresponding ODU trunk.Release published: SR5.0Product family: 7100

t8000220814 When an optical circuit has an end interface in a 7100 node and the node has adirectionless unit (RCMM-8D88-DX or DXOADM), the user can select to use DXby selecting the corresponding OTM-88 add-drop port (selecting None insteadmeans that DX is not used). The DX unit can only be used once for each channel,but Router allows to select the DX unit for several optical circuits using the samechannel. Connecting the first circuit is successful but connecting the other circuitsusing DX and the same channel fails.Release published: SR6.0Product family: 7100

t8000218755 Setting a non-default EVC/ETH/LAG in the SSM unit to the Planned state andback to the In Use state resets them to the default parameters.Release published: SR6.0Product family: 7100

t8000217303 In the 7100 system, hardware mismatch alarms (transceivers or modules) result inalarms on "slot" entities. These alarms are fully discovered and displayed in the7100 Node Manager alarm window as affecting entities such as "SLOT-2-1" or"SLOT-2-1-11". These alarms are also displayed in the Microtopology views forany affected circuit routes. However, the alarm colors erroneously do not appearin the tree view applied to the appropriate entities, e.g. the modules themselves.Release published: SR6.0Product family: 7100

t8000215399 If adding a protecting subcircuit to an ODU circuit while there already is aconnected route in the circuit, connecting the protecting subcircuit may fail withthe following error: "Error(12337) Operation failed: Network element deniedthe request".Release published: SR5.0Product family: 7100Workaround: Disconnect first the whole circuit and then connect the wholecircuit again.


9

1 Known Bugs

t8000213035 When operating a Node Manager with Scope set to All in the Network view, theleft side of the window contains a tree of all locations, nodes, node equipmentand provisioning. Whenever any object in that tree is selected, the right side ofthe window presents context-dependent information, normally including the listof children of that object; this list is meant to match the list of objects shownbelow that object in the tree when it is expanded. For example, when expanding alocation, the nodes and sub-locations within that location are shown in the tree,and that should match the list shown under children. A defect in the softwarecauses this list for a location to include additional nodes from other locations, butonly in the children view. The tree is correct in all known cases, and the childrenlist is correct in all other known cases.Release published: SR4.2-SP1Product family: 7100

t8000168294 The 7100 unit mode (non-switched/switched/pairing) is not allowed to mismatchin the 8000 Intelligent Network Manager database and the 7100 network element.The assumption is that the value set in the 7100 NE is the correct one. Thus, if aunit with an incorrect mode is raised to In Use, an error will be displayed.Release published: SR4.0-SP1Product family: 7100Workaround: Set the unit mode correctly in Node Editor and raise the state.

t8000168154 A 7100 DPRING protected circuit cannot be connected to CPM or AIM units.Release published: SR4.0Product family: 7100

t8000167469 Service monitoring faults are not seen in STS-1 point-to-point APS 1+1 protectingOC endpoint circuits.Release published: SR3.0Product family: 7100

t8000167035 Adding LAG group members to 7100 NEs may fail if the HW modules haveinconsistent configurations or data rates.Release published: SR3.0Product family: 7100

t8000167034 The 7100 NE does not support using SNCPRing and MSP1+1 concurrently whenthe units are in Pairing mode.Release published: SR3.0Product family: 7100

t8000120751 For a Control Plane Call that involves 2WAYPR VC4 or VC3 Cross Connection,not all entities involved in the call are displayed in the Circuit View.Release published: SR4.0-SP1Product family: 7100

1.4 8600 Node Managementt8000234302 In the IP Interface dialog it is not possible to automatically allocate multiple IP

addresses simultaneously, but only one IP address at a time.Release published: SR6.0Product family: 8600Workaround: Automatically allocate one IP address and click Update, thenrepeat this procedure for the following IP addresses.


10

1 Known Bugs

t8000168108 If the router ID is configured in the Node Parameters dialog before theautodiscovery for Tellabs 8605 FP1.3 or older and for Tellabs 8620, Tellabs 8630and Tellabs 8660 FP2.11A or older, it becomes empty in the database afterwards.This happens only if the router ID has not been configured in the network element(NE).Release published: SR4.0Product family: 8600Workaround: Configure the router ID in the network element before performingthe autodiscovery, or update the router ID in the Node Parameters dialog afterthe autodiscovery.

t8000167715 After updating Tellabs 8605 to FP1.5 or Tellabs 8620, Tellabs 8630 and Tellabs8660 to FP3.1 or FP4.0, Consistency Checker may show inconsistency for theLDP Router ID as a result of the changed internal router ID handling of thenetwork element in FP1.5 and FP3.1.Release published: SR3.0-SP1Product family: 8600Workaround: The inconsistency can be resolved from the network element todatabase with the resolve feature in Consistency Checker.

t8000167378 An 8600 node cannot be the endpoint for a 7100 SONET STS-1 point-to-pointcircuit or OC trunk.Release published: SR3.0Product family: 8600

1.5 8800 Element Supportt8000256213 8800 Node Manager displays the node state as normal even if there are critical

and major faults active in the hardware.Release published: SR6.0-SP3Product family: 8800

t8000168152 There is no default value (the first free value) for the bridging instance VC-ID.Release published: SR4.0Product family: 8800

t8000168148 When opening the System Clocking dialog from the 8800 Node Manager queries,the Synchronous Ethernet tab is missing. However, when opening the SystemClocking dialog from the Navigation view, the Synchronous Ethernet tab isavailable.Release published: SR4.0Product family: 8800

t8000168143 8800 Node Manager does not show the bridge port indication [B] on the fifth portin the ATM-CC card. For the other ports, the bridge port indication is showncorrectly.Release published: SR4.0Product family: 8800

t8000168142 In 8800 Node Manager the QoS Traffic Parameters properties dialog shows awrong value for the rule count.Release published: SR4.0Product family: 8800


11

1 Known Bugs

t8000167558 Logical S-VLAN interfaces should be deleted automatically but when created bytrunk binding they are not deleted when the VPLS/Pseudowire Service endpointinterface is deleted. When deleting the VPLS/Pseudowire Service endpointinterface in 8800 Node Manager, the corresponding logical S-VLAN interfacerecords should be deleted automatically regardless of the creation application.Release published: SR3.0-SP1Product family: 8800

t8000167516 VPLS service endpoint properties are shown incorrectly in 8800 Node Managerin the case of access VLAN mode and with the 0x88A8 attribute as the Ethernettype. This is only a graphical user interface issue not affecting the service.Release published: SR3.0Product family: 8800

t8000167429 Preplanned channels, bundles and L2s cannot be synchronized with the hardwarewhen moving from no HW mode to HW mode. These preplanned entities must berecreated manually using Node Manager.Release published: SR3.0Product family: 8800

1.6 Accounting Managementt8000259011 When changing the ODUflex circuit capacity, the new exprate capacity is neither

visible in Accounting Management nor included in its reports.Release published: SR6.0-SP3Product family: 7100

1.7 Dashboardt8000221332 It takes a long time to load the background image of the Dashboard when used

through a slow network, or the network has high latency.Release published: SR5.0Workaround: Enable the single-color background by selecting theDashboard - Preferences menu option. If the network is so slowthat this cannot be done, the following flags can be added to thenms.ini file. DASHBOARD_BACKGROUND_PICTURE = NULLDASHBOARD_BACKGROUND_PATTERN = NULL

1.8 Databaset8000167357 Information on the executing maintenance procedures is printed out in trace.log

rather than in the Scheduling Center tool.Release published: SR3.0


12

1 Known Bugs

1.9 Element Software Managementt8000167239 When selecting unit software files in the downloader application from a file share

residing in a Unix file server that is accessed by Samba, the file folders pointed byshortcut links may not be accessible in Windows 7 if the shortcut links have beencreated in a previous Windows version.Release published: SR4.2Workaround: Create a new shortcut link with Windows Explorer to the directorythat is inaccessible. You can navigate to the problematic folders through thisnew shortcut link.

1.10 Fault Managementt8000253907 The XFP faults of the 7100 OTNM-D unit erroneously have the "Comm:"

specifier instead of XFP.Release published: SR6.0-SP2Product family: 7100

t8000168104 NMS Component monitoring is showing faults for DXX Supervisor,Communication Server and Management Server with a name Unknown Computerunder DBSERVER.Release published: SR4.0

t8000167456 7100 HDTG client interface faults are not mapped to the server optical circuit.Release published: SR3.0Product family: 7100

1.11 Macro Managert8000258718 The Macro Manager client console (MMCC.EXE) does not stop on error if the

command line options -rd<number> and -rn<number> are used.Release published: SR6.0-SP3Workaround: Use the Macro Manager window client (MMCW.EXE).

t8000246042 Unlike Router, Macro Manager does not take the existing 7100 add/drop fibersinto account when selecting an optical circuit channel and route.Release published: SR6.0-SP1Product family: 7100

t8000242261 Changing the state of an interface in the Add/Edit Circuit dialog in Router orchanging the optical circuit protections in Time Slot Viewer while Macro Serveris not fully started displays the following error: "This operation requires MacroManager service. Check that you have Macro Manager service configured,running and reachable, then try again by restarting the application." The problemstill exists after the Macro Manager service is up and running.Release published: SR6.0Workaround: Restart Router/Time Slot Viewer.


13

1 Known Bugs

t8000198644 In Tellabs 8000 intelligent network manager SR2.1 or later, executing recordedmacros for creating, editing and deleting 8800 L1 interfaces fails since therecorded macro contains a question mark for the unit type.Release published: SR4.2Product family: 8800Workaround: Comment out the unit type row containing the question mark in therecorded macro and try executing the macro again.

t8000168365 If parameters are missing from the BMP_NODE_COMMUNICATION_SECU-RITY, BMP_AUTHENTICATION_KEYS or BMP_ENCRYPTION_KEYSmacro and the command is UPDATE, the missing parameters are set to 0.Release published: SR4.0-SP1

t8000168316 Only the first IS-IS_PROCESS macro is recorded when more than one IS-IS areaaddress entry is added or removed while recording is enabled.Release published: SR4.0-SP1

t8000168312 A wrong SYNCHRONIZATION macro is recorded when an IEEE1588 masterentry is added to the node clock fallback list.Release published: SR4.0-SP1

t8000168210 There is no macro support for the 7100 optical channel regeneration.Release published: SR5.0Product family: 7100

1.12 Management Servert8000167454 The 8600 EMS Service must be running in Management Server if the user wants

to use the FTP User Profiles application even if the network does not contain 8600NEs. This application is used also for 7100 and 8800 network elements.Release published: SR3.0Workaround: The 8600 EMS Service needs to be installed e.g. for 7100 SingleServer Configuration.

1.13 Network Editing Toolst8000255357 There is no warning message when raising the state of an ODU trunk if the optical

circuit providing the physical connection is missing.Release published: SR6.0-SP2Product family: 7100

t8000248303 Unbinding an ODU (1.25G) External trunk fails if ODU1 or ODU2 time slotsare still bound.Release published: SR6.0-SP1Product family: 7100Workaround: Unbind the ODUk time slots in Time Slot Editor after which youare able to unbind the trunk.

t8000247937 Node Editor may show an error "Could not start Fault Management Networkwindow" if you open some Fault Management tool for the second time.Nevertheless, Fault Management is usually opened correctly, so the message canbe ignored.Release published: SR6.0-SP1


14

1 Known Bugs

t8000241614 It is not possible to bind an Ethernet trunk to a VLAN interface on LAG.Release published: SR6.0-SP1Product family: 8600Workaround: A cable link trunk, Ethernet 100M or Ethernet 1G trunk can bebound to a VLAN interface on LAG.

t8000240152 If a 7100 node is equipped with a tunable DWDM XFP/SFP+, raising the state ofa HDTG, HGTM-M, OSM20, OSM-2s, ESM20, PSM-1S or OMM-X OTU2 fails.Release published: SR6.0Product family: 7100Workaround: Create OTU2 with 7100 Node Manager, Craft Station or TL1, setthe DWDM channel parameter and raise the state using 8000 Intelligent NetworkManager.

t8000232087 In the NE configuration backup report, the size of the backup file for the 7090,7100 and 8800 NEs is always displayed as 0.Release published: SR6.0Product family: 7100, 8800, 7090

t8000168285 None of the site parameters can be updated with the SITE macro if the NAMEparameter is not given.Release published: SR4.0-SP1

t8000168281 The Cell Site Wizard tool can only load one template file per template type (ATM,Abis, ETH, TDM).Release published: SR4.0-SP1

t8000168160 When creating or updating the NE management username and password for the7100 network elements in the Node Parameters dialog, it is mandatory to restart theCommunication Server in order for the change to take effect in the 7100 Adapter.Release published: SR4.0Workaround: Restart the Communication Server where the 7100 Adapter isrunning.

t8000167741 Facility Link Trunk binding does not work for the 5500 or 8800 nodes.Release published: SR3.0-SP1Product family: 5500, 8800

t8000167595 If Node Editor is opened from the Trunk Parameters dialog in Network Editor (orby clicking a trunk in the network view when the Node Editor tool is active) andNode Editor is already open, Node Editor is activated, but the Trunk Bindingdialog does not open.Release published: SR3.0-SP1Workaround: Open the Trunk Binding dialog by selecting the Bind - Trunksmenu option.

t8000167593 STM External trunk cannot be bound to the STM-4 and STM-16 POS interfacesof the 8600 nodes.Release published: SR3.0-SP1Product family: 8600

t8000167546 If you right-click a location symbol in Network Editor and select Expanded andthen move one of the exposed nodes, the node will be moved out of its originallocation.Release published: SR3.0-SP1


15

1 Known Bugs

t8000167540 It is not possible to abort a new Communication Server creation cleanly in NetworkEditor. The Communication Server Parameters dialog will remain in a state whereyou have to finish the server creation before it is resumed to its original state.Release published: SR3.0-SP1

t8000167405 Some operations initiated from Node Editor or Macro Manager and aimed forthe 8600 or 8800 network elements may have incomplete error messages ifthe operation is illegal and unexpectedly terminated. When this happens errormessages may have characters %1, %2, %3 etc. instead of the real name or ID ofthe VPN, circuit, interface etc.Release published: SR3.0Product family: 8600, 8800

t8000167236 In Node Editor, selecting an interface in the tree view while having the TrunkBinding dialog open does not change the free interface setting in the TrunkBinding dialog. In addition, there are similar problems in the Settings dialog.Release published: SR3.0

t8000167205 The 7100 ODU trunk view filtering does not work in Network Editor.Release published: SR3.0Product family: 7100

1.14 Northbound Interfacet8000168204 NBI filters after a LIKE filter do not work. Only the filters given before the LIKE

filter and the LIKE filter itself affect the result.Release published: SR4.0-SP1

t8000168182 MTOSI setTerminationPointDataRequest operation against Ethernet interfacefor the 8660 NEs, requires that InterfaceSpeed attribute parameters are givenin a certain order from the smallest to the biggest value. E.g. if values are“100_MBIT_PER_SEC,10_MBIT_PER_SEC”, only 10_MBIT_PER_SEC willbe set to the target interface.Release published: SR4.0Product family: 8600Workaround: Change the attribute order so that the smallest speed value is givenfirst, e.g. “10_MBIT_PER_SEC,100_MBIT_PER_SEC”.

t8000168112 In MTOSI NBI, the getManagedElement and getInventory operations mayfor some network element FPs or SPs return the softwareVersion value whichidentifies multiple FPs or SPs. E.g. with the Tellabs 8609 FP1.0 and FP1.1 thereturned value is FP1.1/1.0. This happens when the FPs/SPs have the sameinformation model version, i.e. there are no or only minor changes in the software.Release published: SR4.0

t8000167310 If the ESW Management tool has not been used for downloading ESW for aparticular NE, the getAllEquipmentResponse MTOSI query will not return theinstalledVersion attribute for a unit.Release published: SR3.0


16

1 Known Bugs

1.15 Performance Managementt8000257275 In the 7100 SDH/SONET statistics history, if the 24h counter value for SEFS

exceeds 32k, it is incorrectly shown as a huge value in the PerformanceManagement history graph view.Release published: SR6.0-SP3Product family: 7100

t8000256495 The 7090-40 packet history statistics can show huge utilization, packet and octetcounter values if the element is reset.Release published: SR6.0-SP2Product family: 7090

t8000254691 The Performance Overview tool erroneously shows TDM data from the line layerfor the 7100 ODU1 OC-48 facility as only the TDM section layer is supported.Release published: SR6.0-SP2Product family: 7100

t8000251257 Adding or removing counters in the PMS window with several interfaces in thesame window makes the data of one interface disappear from the graph.Release published: SR6.0-SP1Workaround: Either do not modify the shown counters, or only open PMS graphfor a single interface at a time.

t8000243347 When the 7090 or 7100 performance statistics polling intervals are short,the collection processes may cause high CPU and memory usage in theCommunication Server. This can result in delays in the statistics collection andother network operations.Release published: SR6.0-SP2Product family: 7090, 7100Workaround: Increase the performance polling intervals gradually until theprocess load stabilizes.

t8000231525 The QoS policer PM data is occasionally incomplete for the 8800 NEs.Release published: SR5.1Product family: 8800

t8000228220 The G.826 statistics are not shown for the STM-64 trunks when the endpoint isin the 6335 node.Release published: SR5.0-SP1Product family: 6300

t8000168361 PM ageing might fail for large non-partitioned tables.Release published: SR6.0

t8000168265 It is possible that the Performance Management polling statistics write incorrectnegative values to the pmspollinglog.errcode field.Release published: SR4.0-SP1

t8000168070 When a service has as subservice MPLS VPN with the Y.1731 capabilities, thePerformance Overview report for the whole service is not showing that Y.1731data. However, when the report is opened for the subservice VPN, the Y.1731data is shown correctly.Release published: SR4.0Product family: 7090


17

1 Known Bugs

t8000167810 The PMS Real Time graph shows zero utilization for an RSVP tunnel when trafficis going through the secondary path.Release published: SR4.0Product family: 8600

t8000167633 PMS polling statistics for the 7090 details erroneously shows a 7100 performanceindicator (ETH 7100 processing time).Release published: SR3.0-SP1Product family: 7090

t8000167586 The Collectedtime field in the PMS data sometimes shows an earlier time than thestoptime field, which should not be possible.Release published: SR3.0-SP1Product family: 7100, 7090

t8000167567 The 24-hour PMS polling sometimes starts at wrong time.Release published: SR3.0-SP2

t8000167497 Changing the workstation clock to daylight saving time changes the time whenPM data is configured to be deleted.Release published: SR3.0-SP1

t8000167281 The CDC switchover causes real-time performance monitoring to show atemporary false fluctuation for Ethernet interface traffic. The actual traffic on theinterface is unaffected.Release published: SR3.0Product family: 8600

1.16 Routert8000253854 Manual routing erroneously does not allow selecting the same trunk for both the

protected and protecting subcircuits of an optical pp circuit with the integratedDPRing protection and endpoints in the 7100 HDTG unit OTM-1 interfaces.Autorouting, however, allows this setup.Release published: SR6.0-SP2Product family: 7100

t8000252080 ODU timeslot bindings are not always correctly drawn in Time Slot Editor. Forinstance, for the ODUO circuits having timeslot bindings larger than ODU0:8, thebindings are displayed outside the actual drawing area. However, this is onlya display problem, and the bindings are shown correctly in the list view of theBindings dialog.Release published: SR6.0-SP2Product family: 7100

t8000251363 8000 INM does not support two-stage multiplexing for the 7100 OSM20 unit andthe mTera OSM-2C, OSM-2S and OSM-1S units.Release published: SR6.0-SP2Product family: 7100

t8000250770 If a directionless unit is selected for an integrated DPRing protected opticalchannel pp circuit OTNM-D endpoint, it is erroneously autoselected also for theprotecting subcircuit. Since the integrated DPRIng with OTNM-D requires thesame channel to be used in both directions and the same channel cannot be usedtwice with the same directionless unit, connecting a circuit fails.Release published: SR6.0-SP1Product family: 7100


18

1 Known Bugs

t8000250031 A virtual trunk created by 7100 optical circuit discovery always has the defaultlength parameter value 1 km.Release published: SR6.0-SP1Product family: 7100Workaround: It is recommended to edit the value to ensure the correct routeselection when autorouting.

t8000247060 Discovery of incomplete circuits is not supported but the 7100 circuit discoveryshould report the existence of incomplete circuits in the discovery GUI.Release published: SR6.0-SP1Product family: 7100

t8000246996 When creating an ODU3 circuit, Router reserves an additional tributary slot (32instead of 31) from the mTera ODU4 trunk and MUAP interfaces involved. Thetributary slot is still available in the network element but it cannot be utilizedwith Router.Release published: SR6.0-SP3Product family: 7100

t8000242470 The following problems have been identified when rerouting or moving endpointsof optical circuits.- When routing an alternative route, the optical channel from the original routemay be used although the alternative route is bound to an alternative endpointwhose interface is using another optical channel.- When autorouting or manually routing an alternative route, there may be an errorstating that the connection point identifier (=optical channel) is already used.- When manually routing an alternative route, Router may prompt a dialog forselecting an optical channel from a list, but the optical channel used in the originalroute is not offered in the list.- When adding an optical regeneration point (OEO) for an alternative route,Router crashes.Release published: SR6.0Product family: 7100

t8000242142 When moving optical circuit endpoints, it is not possible to reuse the sameadd/drop port for the alternative endpoint as the original endpoint has.Release published: SR6.0Product family: 7100

t8000241071 Router erroneously allows creating the SDH and SONET circuits correspondingto the 7100 node backplane cross-connection between an SSM-D/X and anSMTM-U(X) unit. This is not supported by the hardware and thus connecting acircuit fails.Release published: SR6.0-SP1Product family: 7100

t8000239890 When creating an SDH 4/4 pp diverse or SONET STS-1 pp diverse circuit with anendpoint in the SSM-D/SSM-X STM-64 or OC-192 MUAP interface of the 7100node, an extra diverse parent end node is created if the following workflow is used:1. Select the node from the Network Nodes drop-down list in the Add/Edit CircuitNodes tab and click the Select Node button.2. Open Node Editor and select the end interface.Release published: SR6.0Product family: 7100Workaround: Select the end interface without first selecting the end node.


19

1 Known Bugs

t8000239141 Router does not take into account the add/drop fibers related to the intermediateoptical regeneration circuit endpoints and circuits using DPRing protection withthe OPSM unit when selecting a channel and route.Release published: SR6.0-SP1Product family: 7100

t8000236315 When creating an ODU2 circuit that is autorouted over an ODU2 trunk betweenthe OSM-20 and HGTM-M ODU2 interfaces in the same node, connecting willfail with the error message CICO internal error. A manually routed circuit doesnot have this problem.Release published: SR6.0Product family: 7100Workaround: Use manual routing.

t8000235628 The combination of OPSM and RCMM-8D88-DX does not work. The secondadd-drop port for RCMM-8D88-DX can be selected but is ignored when theconnection is created.Release published: SR6.0Product family: 7100

t8000234290 When creating a SONET STS-1 pp diverse circuit with the STS-3c-Xvconcatenation and the endpoint in the SSM-D/SSM-X OC-192 MUAP interface ofthe 7100 node, only 1xSTS-1 can be selected per MUAP endpoint with Time SlotEditor instead of the needed 3xSTS-1.Release published: SR6.0Product family: 7100Workaround: Leave 2xSTS-1 free after each selected 1xSTS-1. The 2xSTS-1appears as free capacity in 8000 Intelligent Network Manager even if it is actuallyused. Thus, other circuits cannot be routed using those.

t8000234126 In the OADMF8 unit of a 7100 node 8 channels (the channel numbers depend onthe unit version) are reserved for the add-drop and the rest for the pass-throughconnections. It is also possible to create a pass-through connection using theadd-drop ports but this is not supported by 8000 Intelligent Network Manager.Release published: SR6.0Product family: 7100

t8000234009 When creating a SONET STS-1 pp diverse circuit with an endpoint inSSM-D/SSM-X OC-192 MUAP of the 7100 node, no interface is selected for thediverse parent, only for the diverse child.Release published: SR6.0Product family: 7100

t8000231615 Router erroneously allows the creation of the Y-cable protected optical circuits forunits other than HDTG, TGTM-E, FGTM, FGTM-E and HGTM.Release published: SR6.0Product family: 7100

t8000230608 Using the Auto Add button in the Manual Trunk Time Slot Selection dialog mayselect incorrect timeslots for the SONET STS-1 pp circuit with the STS-3c-Xvconcatenation, depending on the timeslots that are already reserved.Release published: SR5.1Product family: 7100Workaround: Use manual instead of automatic timeslot selection for theSTS-3c-Xv concatenated circuits in the Manual Trunk Time Slot Selection dialog.


20

1 Known Bugs

t8000222681 Trunk Wizard for multi-layer routing gives the "Missing statement parameterXPORTUSAGE" error if you add, undo and then again add the trunk.Release published: SR5.0Workaround: Close the Trunk Wizard and route the circuit again. This shouldtrigger a new instance of the Trunk Wizard that does not have this problem.

t8000207957 Router does not set the circuit use to Virtual Trunk (Edge) for the optical circuitshaving a SONET/SDH layered interface bound to the one end of the circuit anda non-SONET/SDH layered interface (e.g. OTM-1.3) on the other end of thecircuit. This causes Router to incorrectly start Trunk Wizard with a "Failed toread Interface data" error.Release published: SR6.0Product family: 7100Workaround: Select the end nodes and interfaces to the circuit in reverse order.

t8000168079 Circuit Network Viewer shows the cross-connection info as missing for the SNCprotecting branch points.Release published: SR4.0

t8000167458 If a switch command is invoked on a protected cross-connection in a 7100 networkelement, any attempt to disconnect the related circuit through Router fails.Release published: SR3.0Product family: 7100Workaround: Release any switch command before attempting to disconnecta circuit.

t8000167380 Trunk unbinding may fail on error 20 (function input parameter error) after thefollowing errors:1. A VC-4 External trunk is bound to a VC-4 SUAP interface (SUAP accidentallyselected instead of MUAP).2. An SDH 4/4 pp circuit is added between a VC-4 SUAP and General use STM-1interface, the circuit creation is cancelled because the STM-1 interface is nota SUAP.Release published: SR3.0

t8000167353 Creating a SONET diverse circuit with 22 x STS-1 capacity between an SSMand SMTM unit is allowed in 8000 Intelligent Network Manager, but it fails inthe 7100 NE.Release published: SR3.0Product family: 7100

t8000143401 When connecting OEO regenerated circuits using the TGTM-E units, 8000Intelligent Network Manager automatically creates the correct type of facilityin the intermediate nodes. However, these facilities do not automatically showup as modules and interfaces in Node Editor. After successfully connecting anOEO circuit it is recommended to run the Discovery tool for all nodes traversedby the circuit.Release published: SR4.0-SP1Product family: 7100Workaround: The correct types of interfaces may be provisioned in the node byNode Editor prior to connecting the circuit.


21

1 Known Bugs

1.17 Securityt8000167222 Queuing several operations in the Node Communication Security dialog (e.g.

changing properties and states of several authentication keys before clickingUpdate) may create a HW/DB inconsistency.Release published: SR3.0Product family: 8600Workaround: Operations should not be queued, but instead any incrementalchange should be updated.

1.18 Tunnel Engineeringt8000247803 The Tunnel Engineering application does not show the tunnels between the end

nodes in two regions unless both end nodes belong to the regions that have beenselected for showing in the Region Selection for VPN Provisioning dialog onthe Dashboard.Release published: SR6.0-SP1

t8000235025 The customer-specific tunnel templates for the 8800 NEs are not updated with thenew LMA parameters during the 8000 Intelligent Network Manager upgrade, andtherefore the customer-specific templates must be recreated.Release published: SR5.0-SP2Product family: 8800

t8000168101 In Tunnel Engineering, the supported value range for the Wait to Restore optionis 0 - 180 000 ms. However, the Tellabs 8620, Tellabs 8630 and Tellabs 8660network elements with FP4.0 support value range 0 - 2 592 000 000 ms.Release published: SR4.0Product family: 8600

t8000165400 Tellabs 8600 network elements misleadingly interpret the 60-second retry timervalue of the RSVP-TE tunnel to be the default value when the configuration isdone via BMI. In this case, the effective retry timer value is 30 seconds and theretry timer configuration is not shown in CLI running configuration. However, thetunnels can be normally operated. This problem concerns Tellabs 8600 networkelement feature packs older than 2.11A, Tellabs 8605 1.3 SP1 and Tellabs 8607 1.1.Release published: SR6.0Product family: 8600Workaround: To use the 60-second retry timer value, update the network elementESW and reconnect the RSVP-TE tunnels having the 60-second retry timer value.

1.19 VPN Provisioningt8000256275 When creating an Ethernet pseudowire between two 8600 network elements with

the Fixed Service Class For VC parameter set to Undefined in the pseudowiremesh settings, policers are not created for any other service class than RT.Release published: SR6.0-SP2Product family: 8600Workaround: Update Fixed Service Class For VC to RT and back to Undefinedin the pseudowire settings when creating the pseudowire. For the already existingpseudowires, the workaround can be applied when the pseudowire is in a Plannedstate.


22

1 Known Bugs

t8000249182 The VPN Provisioning application may crash when operating the network libraryin the Windows Server 2008/2012 operating systems.Release published: SR6.0-SP1Workaround: Install the Microsoft Desktop Experience feature for Windows.

t8000242656 Rerouting the primary or secondary path of the connected MPLS-TP tunnel maycause a short traffic break.Release published: SR6.0-SP1

t8000231401 When an RVT tunnel has an endpoint as PPNP and the endpoint NE type is7090-05 CE or 7090-07 CE, traffic incorrectly goes also through the protectingroute.Release published: SR6.0Product family: 7090

t8000228657 When a protection group of an RVT between the 7090 and 7100 nodes isdisconnected and then reconnected, the traffic stays down for several minutes.Release published: SR5.0-SP1Product family: 7100, 7090

t8000220518 There are two 7100 Ethernet ring protection parameters missing from VPNProvisioning. As a result, it is not possible to define the Interconnection nodeand Multiple Failure settings to ERP.Release published: SR5.1Product family: 7100

t8000216037 When updating a tunnel affinity template of a pseudowire which is in theconnected state, the template for the forward direction is used for both directionsof the pseudowire, and the template for the backward direction is ignored.Release published: SR6.0

t8000210925 Connecting a VLAN VPN endpoint fails if the network element is 7090-05 CE,the customer port mode is CNPP, and Ethernet OAM is enabled for the endpoint.Release published: SR6.0Product family: 7090

t8000208466 It is not possible to successfully perform the Create Configuration command fora pseudowire mesh if the mesh contains more than one protecting pseudowire(pseudowire redundancy). This only concerns the 8600 network elements.Release published: SR6.0Product family: 8600Workaround: Perform the Create Configuration command for each pseudowireseparately.

t8000168167 In VPN Provisioning, the Test Loopback Interface selection does not work when aloopback interface has been added to the same VRF.Release published: SR4.0

t8000168129 IP VPN discovery does not discover the Optimize VRF Generation parametercorrectly in all cases.Release published: SR4.0


23

1 Known Bugs

t8000168125 VCCV BFD session may remain down between the 8600 and 8800 networkelements on the Ethernet pseudowire when the BFD Fault detection option isbeing used.Release published: SR4.0Product family: 8600, 8800Workaround: If the pseudowire does not get connected after connect, use 8800Node Manager to disable and enable the pseudowire circuit admin state.

t8000168082 In 8800 network elements, disabling MAC learning for a connected VPLS setsalso the MAC aging time to 0.Release published: SR4.0

t8000167393 The VPN Discovery tool does not support discovering ATM N-to-1 (ATM CC)configuration in 8800 network elements.Release published: SR3.0

t8000167102 Disconnecting a single item from a pseudowire mesh by using the AdvancedConnect dialog will lower the state of all items in the mesh. Only the state islowered, nothing is removed from the network elements. The states can be raisedto connected by selecting the rows in the Advanced Connect dialog and clickingthe Connect button.Release published: SR3.0

t8000167060 The Max Routes and Route Map settings in the OSPF process of an IP VPNendpoint are only stored in the database.Release published: SR3.0

1.20 Web Reportert8000257929 Web Reporter does not show the ODUflex circuit capacity (Exprate) value.

Release published: SR6.0-SP3Product family: 7100

t8000167571 Web Reporter shows erroneous capacity (n x AU-4) for the 8600 OC POSinterfaces.Release published: SR3.0-SP1Product family: 8600

t8000167505 Web Reporter shows erroneous free capacity for the 7100 OPSM GOPT-W/Pinterfaces involved in a circuit.Release published: SR3.0-SP1Product family: 7100

t8000167372 Optical PM data is not collected to the database from the following types of 7100units: LIAME88, LRAM, ELRAME88, CCMIR, CCMLR, OLAIR, OLALR,OADM88IR, OADM88LR and OADM88ER.Release published: SR4.0-SP1Product family: 7100

t8000164343 VLAN QoS Drop Queue counters are missing from Web Reporter.Release published: SR3.0


24

8000 inm sr6.0 service pack 3 bug notes

Documents

node management

dbug notes

bug notes76

document conventions

international copyright

adobe reader

united states andor

service pack