76 8670 50177b 8600 smart routers SR7 0 embedded software release notes (SR7 0 SP1 GA)

8600 Smart Routers SR7.0 Embedded Software Release Notes 76.8670-50177B 19.05.2015 Document Information Revision History Document No Date Description of Changes 76.867050177B 19.05.2015 New application software version for SR7.0 SP1 GA in chapter 12.1 Version SR7.0 SP1 GA (Application SW Version 7.0.172) 8665 Smart Router added to the scope of the document Ch Embedded Software Interrelation Tables updated Ch Supported Upgrade Paths updated Note regarding 8615 Smart Router boot and mini-application upgrade added to ch Software Upgrade Order and 5.2 Upgrade Related Notifications for 8615 Smart Router The last sentence added to Step in ch 6.1 8611 Smart Router Service Affecting Hardware and Software Upgrade of the Whole NE Step 13 added to ch 8.1 Upgrading CDC1 to CDC2 Ch Non-Service Affecting Software Upgrade added Ch 14 Restrictions in 8600 Smart Routers SR7.0 added Ch 15 Restrictions in 8600 Smart Routers reorganized Ch BGP Labeled Unicast (S-MPLS) removed from ch 15 Restrictions in 8600 Smart Routers The restrictions previously listed in the chapter are now discussed in 8600 Smart Routers MPLS Configuration Guide Added as known bugs since the previous, SR7.0 CIR1, ESW Release Notes: cq300240667, cq300253544, cq300254046, cq300254432, cq300254475, cq300254704, cq300255453, cq300255466, cq300255504, cq300255513, cq300255768, cq300255844, cq300256215, cq300256432, cq300256561, cq300256576, cq300256607, cq300256619, cq300256793, cq300256900, cq300257006, cq300257042, cq300257073, cq300257126, cq300257150, cq300257154, cq300257278, cq300257287, cq300257358, cq300257373, cq300257393, cq300257423, cq300257427, cq300257442 76.867050177A 11.03.2015 Initial version of the document for 8600 Smart Routers SR7.0 CIR1 (8602 Smart Router FP7.0 CIR1) ESW version 7.0.92 8600 Smart Routers SR7.0 Embedded Software Release Notes 76.8670-50177B © 2015 Coriant This revision of the manual documents the following network elements and the corresponding feature pack 8602 Smart Router FP7.0 8609 Smart Router FP7.0 8615 Smart Router FP7.0 8630 Smart Router FP7.0 8660 Smart Router FP7.0 8665 Smart Router FP7.0 If a different feature pack of 8600 products is in use, please refer to the relevant product document program on the Tellabs and Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation & Software > Data Networking > Tellabs 8600 Smart Routers > Technical Documentation © 2015 Coriant All rights reserved This manual is protected by U.S and international copyright laws, conventions and treaties Your right to use this manual is subject 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 Unless otherwise agreed in a written document, the software in the product is licensed under the license terms found at http://coriant.com/legal/documents/coriant_tandc_global_deliverables.pdf and http://coriant.com/legal/documents/tellabs_product_specific_tandc.pdf 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 8600 Smart Routers SR7.0 Embedded Software Release Notes 76.8670-50177B © 2015 Coriant Document Information Terms and Abbreviations Term Explanation BGP Border Gateway Protocol CIR Controlled Introduction Ready CLI Command Line Interface CDC Control and DC Power Card (used in 8630 Smart Router and 8660 Smart Router) Control card The control card in the 8600 system consists of a Control and DC Power Card CDC (used in 8630 Smart Router and 8660 Smart Router), Switching and Control Module SCM (used in 8611 Smart Router) In 8000 Intelligent Network Manager and CLI referred to as unit 76.8670-50177B © 2015 Coriant CU Control functionality (used in 8615 Smart Router and 8665 Smart Router) ELC1 Ethernet Line Card (used in 8630 Smart Router and 8660 Smart Router) ESW Embedded Software FP Feature Pack GA General Availability GE Gigabit Ethernet HM High Speed Module (used in 8611 Smart Router) HW Hardware IFC Interface Module Concentrator is a line card baseboard and it can be equipped with one or two IFMs There are three variants available: IFC1-A, IFC1-B and IFC2-B (used in 8630 Smart Router and 8660 Smart Router) IFM Interface Module A specific term of the module which can be placed on the IFC line card or 8620 Smart Router baseboard and which consists of the physical interfaces (used in 8620 Smart Router, 8630 Smart Router and 8660 Smart Router) INM 8000 Intelligent Network Manager Line card The line card in the 8600 system consists of an Ethernet Line Card (ELC1), Interface Module Concentrator (IFC) and up to two Interface Modules (IFMs) (used in 8630 Smart Router and 8660 Smart Router) In 8000 Intelligent Network Manager and CLI referred to as unit Line Unit The line unit in the 8665 Smart Router is the basic building block for the element One line unit contains traffic functionality (LU) and control functionality (CU) LM Line module (used in 8607 Smart Router, 8609 Smart Router and 8611 Smart Router) LU Traffic functionality (used in 8615 Smart Router and 8665 Smart Router) LU1 Line Unit in 8665 Smart Router NE Network Element SCM Switching and Control Module (used in 8611 Smart Router) SFP Small Form-Factor Pluggable A transceiver type used in 8600 IFMs, HMs, LMs and network elements SR System Release 8600 Smart Routers SR7.0 Embedded Software Release Notes Document Information SU Switch Unit (used in 8665 Smart Router) SW Software 8600 Smart Routers SR7.0 Embedded Software Release Notes 76.8670-50177B © 2015 Coriant Table of Contents Table of Contents About This Manual 11 Objectives 11 Audience 11 8600 Smart Routers Technical Documentation 12 Documentation Feedback 15 8600 Smart Routers Discontinued Products 16 Embedded Software Interrelation Tables 17 1.1 1.2 1.3 1.4 1.5 1.6 8600 Boot and Mini-Applications Software 18 8602 Smart Router Applications Software Compatibility Matrix 24 8609 Smart Router Applications Software Compatibility Matrix 24 8615 Smart Router Applications Software Compatibility Matrix 26 8630 Smart Router and 8660 Smart Router Applications Software Compatibility Matrix 28 8665 Smart Router Applications Software Compatibility Matrix 33 Supported Upgrade Paths 35 Software Upgrade Order 38 Operations Before Upgrade 39 4.1 4.2 4.3 4.4 Operations Before Upgrading 8602 Smart Router and 8609 Smart Router 39 Operations Before Upgrading 8611 Smart Router 40 Operations Before Upgrading 8615 Smart Router and 8665 Smart Router 41 Operations Before Upgrading 8630 Smart Router and 8660 Smart Router 42 Upgrade Related Notifications 44 5.1 76.8670-50177B © 2015 Coriant Upgrade Related Notifications for 8609 Smart Router and 8611 Smart Router 44 8600 Smart Routers SR7.0 Embedded Software Release Notes Table of Contents 5.2 5.3 Service Affecting Software Upgrade of the Whole NE 46 6.1 8611 Smart Router Non-Service Affecting Software Upgrade 50 8630 Smart Router and 8660 Smart Router Non-Service Affecting Software Upgrade 51 Upgrading Cards 55 8.1 8.2 8611 Smart Router Service Affecting Hardware and Software Upgrade of the Whole NE 48 Non-Service Affecting Software Upgrade 50 7.1 7.2 5.1.1 Recommended Procedure for Upgrading to 8609 Smart Router and 8611 Smart Router FP1.3 SP1 44 Upgrade Related Notifications for 8615 Smart Router 44 Upgrade Related Notifications for 8630 Smart Router and 8660 Smart Router 45 5.3.1 Notification Regarding ELC1 ESW Upgrade to 8630 Smart Router and 8660 Smart Router FP4.1 SP1 45 Upgrading CDC1 to CDC2 55 IFC1 to IFC2 Upgrade 58 8.2.1 Service Affecting Upgrade of IFC1 to IFC2 59 8.2.2 Non-Service Affecting Upgrade of IFC1 to IFC2 61 ESW Upgrade with Downgrade Support for 8602 Smart Router and 8615 Smart Router 62 10 Restoring Previous FP and Configuration in Case of Upgrade Failure 64 10.1 Restoring Previous FP and Configuration in Case of Upgrade Failure in 8602 Smart Router and 8609 Smart Router 64 10.2 Restoring Previous FP and Configuration in Case of Upgrade Failure in 8611 Smart Router, 8615 Smart Router, 8630 Smart Router, 8660 Smart Router and 8665 Smart Router 65 11 SR7.0 Features 67 12 Application Software 69 12.1 Version SR7.0 SP1 GA (Application SW Version 7.0.172) 69 8600 Smart Routers SR7.0 Embedded Software Release Notes 76.8670-50177B © 2015 Coriant Table of Contents 13 Enhancements and Fixed Bugs in SR7.0 SP1 71 13.1 Control, Routing and Signaling Protocols 71 13.1.1 Enhancements 71 13.1.2 Fixed Bugs 71 13.2 Ethernet Forwarding and Services 73 13.2.1 Fixed Bugs 73 13.3 IP/MPLS Forwarding and Services 74 13.3.1 Enhancements 74 13.3.2 Fixed Bugs 74 13.4 Management Plane 76 13.4.1 Fixed Bugs 76 13.5 Multiservice 76 13.5.1 Fixed Bugs 76 13.6 Platform Services 77 13.6.1 Enhancements 77 13.6.2 Fixed Bugs 77 13.7 Resiliency and Robustness 78 13.7.1 Fixed Bugs 78 13.8 Synchronization 78 13.8.1 Enhancements 78 13.8.2 Fixed Bugs 79 13.9 Traffic Management 81 13.9.1 Fixed Bugs 81 13.10 Troubleshooting, OAM, Statistics and Performance Monitoring 81 13.10.1 Fixed Bugs 81 13.11 Other 82 13.11.1 Fixed Bugs 82 14 Restrictions in 8600 Smart Routers SR7.0 84 14.1 Control, Routing and Signaling Protocols 84 14.2 Ethernet Forwarding and Services 84 15 Restrictions in 8600 Smart Routers 85 15.1 General 85 15.2 Synchronization 85 15.3 Product Specific Restrictions in 8600 Smart Routers 86 15.3.1 8602 Smart Router 86 15.3.2 8609 Smart Router and 8611 Smart Router 86 15.3.3 8615 Smart Router 86 15.3.4 8630 Smart Router and 8660 Smart Router 87 16 Known Bugs 88 16.1 Control, Routing and Signaling Protocols 88 16.2 Ethernet Forwarding and Services 88 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes Table of Contents 16.3 16.4 16.5 16.6 16.7 16.8 16.9 16.10 IP/MPLS Forwarding and Services 91 Management Plane 94 Platform Services 94 Resiliency and Robustness 96 Synchronization 97 Traffic Management 97 Troubleshooting, OAM, Statistics and Performance Monitoring 98 Other 99 17 Rejected Bugs 101 8600 Smart Routers SR7.0 Embedded Software Release Notes 10 76.8670-50177B © 2015 Coriant 16 Known Bugs cq300215625 IFC2 VLAN statistics cannot be activated for a VSI port Impact: Once an interface is attached to a VSI, VLAN statistics cannot be activated or deactivated Risk of occurrence: Always under the described circumstances Workaround: If VLAN statistics are required for a VSI port, they should be enabled before the port is attached to a VSI To enable or disable VLAN statistics for a VSI port, the port needs to be detached from the VSI, VLAN statistics then enabled or disabled, and reattached to the VSI cq300225896 CDC1, IFC1, IFC2, ELC1, CDC2, 8615 NE Gateway ARP resolution may hang on IRB when the IRB interface administrative state is changed to 'up' The problem is automatically resolved after the ARP timeout period (default 1200 seconds) Impact: Traffic will not flow through a gateway route until the gateway MAC is resolved Risk of occurrence: Low Workaround: Give the "shutdown" CLI command and then the "no shutdown" command to the IRB interface cq300239055 IFC1, IFC2 For pseudowires attached to ETHoPPP/ETHoMLPPP interfaces, the Rx bit rate field in the pseudowire performance statistics shows incorrect value The value will be slightly less than the actual rate Impact: Rx bit rate field will display incorrect value for ETHoPPP/ETHoMLPPP pseudowires Risk of occurrence: Always for ETHoPPP/ETHoMLPPP interfaces Workaround: Not available cq300239602 8609 NE Ethernet PWE3 redundancy feature for 8609 Smart Router exceeds the expected switchover timing target of 50ms for 25 protection groups in revertive switchover case if PWs are dynamically (LDP) provisioned This occurs regardless of VCCV BFD Interval and Multiplier options because of slowness of LDP session negotiations compared to VCCV BFD sessions Impact: A few protection groups will not complete their protection switching within the 50ms time limit Risk of occurrence: Always under the described circumstances Workaround: Use static pseudowires cq300239762 ELC1, 8615 NE The number of learned MAC addresses exceeding 256K limit will be visible in the MAC forwarding table (show bridging-instance) until manually cleared Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Clear MAC table manually (clear bridging-instance name macs) cq300254432 ELC1 Conflicting module alarm may be raised for 10 seconds in any ELC1 GE interfaces if one or more of the GE interfaces on the same ELC1 is/are configured as a clock source and listed on the node timing fallback list Impact: All the services will be cut in that interface reporting conflicting module alarm The services will restore after the alarm is cleared Risk of occurrence: From one to tens of times a day Workaround: Remove all the ELC1 GE clock sources from running configuration 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 89 16 Known Bugs cq300255504 8665 CU Traffic loss is occasionally observed when a master router with VRRP mastership returns to the master role after reload of the said router is completed Impact: A traffic drop of - seconds Risk of occurrence: Very rare Workaround: Not available cq300255513 CDC1, ELC1 H-VPLS LDP MAC withdraw message does not always get generated by VPLS PE:s at the edgre of the VPLS mesh when "mac-withdraw pw-down" mode is used Impact: When MTU-rs node switches traffic between primary and secondary spoke PW:s, there may be some traffic loss (extend depends on minutia of the H-VPLS topology and traffic streams in use) Risk of occurrence: Often with specific topologies Workaround: Workaround (mitigation): configure smaller mac aging timers to reduce impact on missing MAC withdraws Workaround (avoid problem altogether, but causes heavier mac flushes): Configure "mac-withdraw pw-up" in MTU-rs node instead of the "mach-withdraw pw-down" in PEs This workaround should only be used if customer experiences severe problems due to this bug cq300255768 8615 NE In 8615 Smart Router stacked, reset-hw of the slave line unit may lead to NPXD error dumps in os-log as well as console An example error log: "NPXD ERROR: UNIV_ING: [rc=1] "handle < NPXD_MAX_ELINKS" failed at " Impact: It does not affect live traffic Risk of occurrence: Rare Workaround: Not available cq300256432 8665 LU1 The speed configured on the backup interface before ELP creation is not retained after ELP group removal After ELP removal the backup interface and its pair interface will be configured to the default speed (10G) Note that when an interface mode speed in 8665 LU M1 and M2 is being changed, the mode speed of its pair interface is also automatically changed As an example, after ELP removal the GE backup interface xe3/1/0 is changed to operate in 10 GE mode This change will also set the pairing interface xe3/1/1 to operate in 10 GE mode A pair of interfaces in a virtual module within the LU1 is defined by neighboring even-odd numbers, i.e., 0-1; 2-3 12-13 Impact: It will affect traffic on the backup interface and pair interface of the backup interface after ELP removal Risk of occurrence: Always under the described circumstances Workaround: Before creating the ELP group, configure the same speed on the primary and backup interfaces After deleting the ELP group, make sure the backup and backup pair interfaces are configured to the same speed cq300256793 8615 NE, IFC1, IFC2, ELC1, 8665 LU1 The link MTU configuration on the backup interface is not removed after removing the ELP group, if MTU is configured on that ELP group Impact: Unintuitive default value for MTU Risk of occurrence: Always during snapshot restore or NE reload without a clean start Workaround: The MTU configurations in the backup interface can be deleted using the 'no mtu ' CLI command 8600 Smart Routers SR7.0 Embedded Software Release Notes 90 76.8670-50177B © 2015 Coriant 16 Known Bugs cq300257073 8665 LU1 LAG load distribution to the LAG members does not happen evenly to all members Impact: Traffic might not be distributed evenly among the LAG members Risk of occurrence: This happens only when traffic headers used for load balancing have only MPLS or VLAN fields Workaround: Automatic rebalancing should be enabled That mechanism will redistribute the load evenly between the members in a situation where any of the members may get almost fully loaded cq300257154 8665 CU, 8665 LU1 On 8665 when ELP is configured between units and 13: If CU and ELP activity is on the same card, which is then extracted, a traffic loss of up to - seconds is observed in the ELP protected port traffic Impact: Traffic loss under the described circumstances Risk of occurrence: Always under the described circumstances Workaround: Standard active card replacement procedure needs to be attempted First the active CU must be switched over using manual CU switchover commands, and then the card can be removed This problem can be avoided by using ELP only on cards 3, 4, 11 and 12 cq300257373 8615 NE Ethernet OAM ping/traceroute to the 'UP' MEP fails after CU switchover in 8615 Smart Router stacked Impact: Ethernet OAM ping/traceroute to the 'UP' MEP fails after CU switchover Risk of occurrence: Always under the described circumstances Workaround: Issue commands 'shutdown' and 'no shutdown' under the interface where MEP is attached to 16.3 IP/MPLS Forwarding and Services cq300201508 8609 NE, IFC1, IFC2 Action "ac-defect-action pw-down" does not work for TDM pseudowires Impact: In the case of CESoPSN or SAToP attachment circuit failure, the pseudowire is not torn down and it still sends AIS traffic through the network, thus consuming bandwidth unnecessarily This is a problem if the network bandwidth is a bottleneck Risk of occurrence: Always under the described circumstances Workaround: Do not configure non-active TDM pseudowires cq300226053 IFC1, IFC2 If line loopback (loopback-to-line) is enabled on a 4xchSTM-1/chOC-3 Multiservice IFM (LIO2234) and a pseudowire redundancy group is configured on the IFM, the operational states of the pseudowires belonging to the group go DOWN Impact: If loopback-to-line is configured in 4xchSTM-1/chOC-3 MS IFM, the pseudowire redundancy group configured in the interface will go DOWN and traffic cut will be observed When the loop is removed, the traffic recovers Risk of occurrence: Always under the described circumstances Workaround: Not available 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 91 16 Known Bugs cq300231048 IFC1, IFC2, ELC1, 8665 LU1, 8615 NE Error message in linecard's os-log when VRF is deleted without unbinding it first VRF is deleted successfully despite of os-log error message Impact: It does not affect live traffic Risk of occurrence: Always when VRF is deleted without unbinding it first Workaround: Unbind VRF from all interfaces using it before deleting VRF cq300232626 CDC1, CDC2, 8609 NE, 8602 NE ARP table entries for static routes are not removed immediately after deleting the route Impact: Obsolete ARP entries are temporarily shown in the ARP table Risk of occurrence: Always when static routes are deleted Workaround: Obsolete ARP entries are removed after ARP timeouts or interface link status changes cq300232742 CDC1, CDC2 Some short IS-IS frames may have bytes of additional padding Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Not available cq300238998 ELC1, 8615 NE When associated ACL contains unsupported actions for ELC1 or 8615 Smart Router, faults are not raised accordingly Impact: Faults are raised and cleared incorrectly This has no impact on services Risk of occurrence: Always when configuring unsupported ACL actions for ELC1 or 8615 Smart Router Workaround: Do not configure unsupported ACL actions for ELC1 or 8615 Smart Router, e.g action Policer or reverse action lookup (RAL) cq300242522 CDC1, IFC1, IFC2, ELC1, 8609 NE, 8615 NE, CDC2, 8602 NE ARP cache entry may be left unexpired for an indefinite time Impact: It does not affect live traffic Risk of occurrence: Dependent of ARP cache timer values, thus rare Workaround: ARP cache can be cleared, which should resolve the issue cq300244461 CDC2, ELC1 With 450 or more MPLS-TP protection groups (each group having MPLS-TP tunnels), the traffic loss is sometimes present for more than 50 ms in the event of link failure This is seen when the attachment circuit is in the same line card as the MPLS-TP back-up tunnels With 400 groups or less this loss is always less than 50 ms Impact: In this scenario, the traffic loss will be around 60 ms Risk of occurrence: Low Workaround: If 450 protection groups are needed, then the attachment circuits must be configured on some other line card which is not having the MPLS-TP backup tunnels cq300245824 ELC1 ACLs containing the map-route option cause an ACL statistics counting failure That is, ACL statistics counters will not increment when traffic hits the ACL rules on the list Impact: No impact to traffic When this issue is met, ACL statistics for the ACL instance is useless Risk of occurrence: Always under the described circumstances Workaround: Not available 8600 Smart Routers SR7.0 Embedded Software Release Notes 92 76.8670-50177B © 2015 Coriant 16 Known Bugs cq300249839 8615 NE IP host access list statistics are not counting Impact: IP host statistics are not usable e.g for debugging on which ACL rule certain packets are hitting Risk of occurrence: Always under the described circumstances Workaround: Not available cq300250802 ELC1, 8609 NE, CDC2, CDC1, 8602 NE, 8615 NE The tunnel protection status of some MPLS-TP tunnels remains in passive state only when both primary/backup links are changed to DOWN and then to UP at the same time in both the ingress and the egress node Impact: When the issue occurs, it impacts PSC packet transmission for some tunnels and protection switchover does not work Risk of occurrence: Always under the described circumstances Workaround: When hold-off timer is not configured, the issue does not occur cq300255453 8665 SU1 Some CRC errors of internal data bus have been observed in 8665 Smart Router causing a few packet drops Impact: A few packet drops may occur Risk of occurrence: Occasionally under the described circumstances Workaround: Not available cq300256215 8615 NE CU switchover on 8615 Smart Router stacked that has a large number of RSVP sessions (~2.5K sessions) with path protection causes error print "slot13:ERROR:BatLspProtCb: ret=1" on the console Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Not available cq300256561 8665 LU1 When ACLs are used, 8665 LU1 may not reach its maximum forwarding performance for small packets Impact: Decreased forwarding performance with ACLs for small packets Risk of occurrence: Occasionally under the described circumstances Workaround: Not available cq300257427 8665 LU1 The user shall not hang the LU1 boot-up by entering to the U-Boot command mode A hanged boot-up may cause traffic loss in all LU1s Impact: Loss of traffic in all LU1s Risk of occurrence: High if LU1 boot-up is hanged up Workaround: Do not enter to U-Boot command mode during LU1 boot-up 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 93 16 Known Bugs 16.4 Management Plane cq300253544 CDC1, CDC2, 8665 CU SNMP collector fails to fetch some of the VLANs during snmpwalk on logical interfaces This issue can be seen: When the same VLAN ID is configured on a different port of the same module, the interface on port on that particular module alone is listed The others are ignored Ignores VLAN IDs on the other ports which are smaller than the smallest VLAN id on port of that module snmpwalk on logical interface for that module will start with the smallest VLAN ID on port and collected in ascending order of VLAN ID without considering the physical interface Impact: Some of the VLANs will not be listed in SNMP Fetch Risk of occurrence: Always under the described circumstances Workaround: Not available cq300257393 CDC1, CDC2 BMI does not work when either one of the CDCs is running mini-application SW Impact: 8000 Intelligent Network Manager commands not working, return timeout Risk of occurrence: Always under the described circumstances Workaround: Access the network element via Telnet cq300257442 8615 NE If the LU process of 8615 Smart Router stacked resets spontaneously, ELP protected management connectivity is lost for 75 seconds if the active CU process is situated on the same card as the reset LU process Impact: ELP protected management connectivity is lost for up to 75 seconds Risk of occurrence: Only on the rare occasion of LU resetting spontaneously This issue has been observed only in test cases where LU reset has been intentionally simulated Workaround: Not available 16.5 Platform Services cq300231620 CDC1 8000 Intelligent Network Manager operations may slow down if query rate (queries/second) from 8000 Intelligent Network Manager to the network element is continuously high Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances, more likely with big configurations Workaround: Not available cq300235687 IFC1 The far end link state is down after giving "shutdown-if" command in the near end Impact: Whenever the "shutdown-if" command is given in the near end, the far end link will go down Risk of occurrence: Always under the described circumstances Workaround: shut/no-shut on the near end link will make the far end link go up 8600 Smart Routers SR7.0 Embedded Software Release Notes 94 76.8670-50177B © 2015 Coriant 16 Known Bugs cq300254046 8665 CU If fan module microcontroller needs to be re-programmed, the programming may fail if the network element has two functional CUs, i.e., LU1s are both in slot and in slot 13 Impact: Fan module microcontroller re-programming may fail Risk of occurrence: Rare Fan module microcontroller reprogramming is rarely needed Workaround: Before re-programming the fan unit microcontroller, pull out one of the LU1s in slot or 13 cq300254475 8665 CU When removing and inserting LU1 in 8665 Smart Router slots and 13, PIM related faults appear in the fault history ("Power Input Module Primary/Backup: Expected module not activated") These faults not indicate faulty PIM units but are harmless and due to internal communication transitions Impact: Harmless extra faults in the fault history Risk of occurrence: Always under the described circumstances Workaround: Not available cq300255844 8665 CU If the primary power input module (PIM) is not part of hw-inventory, but the backup PIM is, the "missing input voltage" fault is not reported for the backup PIM even if voltage is missing The "missing input voltage" fault should be reported for a PIM belonging to hw-inventory if the input voltage is missing Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Add both PIMs to the hw inventory cq300256576 8615 NE Active and passive side fan failure is reported as "slot14 'Cooling FANs not running'", but the user does not really know on which side the problematic fans are Impact: If the fans are broken, the unit temperature goes up, causing the unit to go to power save state Risk of occurrence: If the fans are broken, the problematic unit goes down always Workaround: In case the active fault 'Cooling FANs not running' is shown for slot 14, check the fault history of slot and slot 14 to see on which side the fans have failed cq300256619 CDC1, CDC2 The 'show environment power' command gets estimated power consumption values for CDC1 CDC2 cards measure the real power consumption, so 'show environment power' is not supported Impact: Estimated consumption is not shown on the CDC2 cards Risk of occurrence: Always under the described circumstances Workaround: Not available cq300256900 CDC1, CDC2, 8615 NE, 8665 CU, 8609 NE, 8602 NE Setting Ntp Md5AuthenticationKeyList with 8000 Intelligent Network Manager has a side effect which removes all but one entry from Ntp TrustedKeyList Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: After modifying Ntp Md5AuthenticationKeyList with 8000 INM, set again the Ntp TrustedKeyList as well 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 95 16 Known Bugs 16.6 Resiliency and Robustness cq300136667 CDC1, IFC1, 8609 NE, 8602 NE, IFC2 RSVP FRR switchover times 500) are updated at once Impact: BFD session flapping leading to traffic losses and protocol adjacency flaps Risk of occurrence: Always under the described circumstances Workaround: On the network elements in question, avoid BFD detection times shorter than 100 ms Examples of safe parameter sets: - 100 ms interval multipler - 100 ms interval multiplier cq300257423 8665 CU If watchdog reset happens in control units, some packet loss is seen in the line units Packet loss can be up to 3% Impact: Traffic-affecting Risk of occurrence: Always under the described circumstances Workaround: Not available 8600 Smart Routers SR7.0 Embedded Software Release Notes 96 76.8670-50177B © 2015 Coriant 16 Known Bugs 16.7 Synchronization cq300245891 8602 NE, 8609 NE When the IEEE1588 L2 master is referenced from a GNSS SFP which is operated in GLONASS mode, a static phase error of microseconds is introduced to the sent PTP frames Impact: It is not possible to meet the LTE TDD or LTE-A phase/time synchronization requirement of 1.5 microseconds Risk of occurrence: Always under the described circumstances Workaround: Use GPS operating mode for the GNSS SFP cq300257042 CDC2, CDC1, IFC2, IFC1 When more than ten 24xchE1/chT1 Multiservice (LIE2226) are added to the NE, issuing the CLI command “show node-timing” freezes the network element Impact: Control traffic will mostly be affected Risk of occurrence: Always under the described circumstances Workaround: Not available cq300257287 CDC2, 8665 CU, CDC1, 8615 NE Clock source IDs over 2147483647 are shown as negative for the secondary (protecting control card/unit) SCI clocks The primary SCI Clocks not have this problem Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Do not use clock IDs over 2147483647 16.8 Traffic Management cq300134123 CDC1, IFC1, CDC2 The number of shapers that can be associated to a VLAN is limited to 961 in an 8630 or 8660 Smart Router cq300235456 8609 NE, 8602 NE QoS markings for CCM/LMM/DMM (EOAM UP MEPs packets) not follow Ethernet VLAN PWE3 VC-QoS settings When vc-qos option is set on Ethernet VLAN PWE3, the EOAM packets traversing the VLAN should be re-marked using vc-qos value as long as the qos ingress setting is set to 'qos mapping use ingress traffic layer2-frame' Instead, the defined per EOAM VLAN settings are still used Impact: EOAM traffic may get affected during network congestion Risk of occurrence: Always under the described circumstances Workaround: It is recommended to set LM and DM QoS with VC QoS setting cq300248884 8609 NE, 8602 NE Low priority exception frames are raised to management CPU in the same queue as frames addressed to local CPU in BE, AF1-4 and EF classes This means that exception frames (e.g packets that not have the available route and will need ICMP error to be generated for) may saturate the queue and hamper other communications Routing protocols and CS7 traffic use high priority queue, and are not affected Impact: Communications to CPU on non-CS7 classes may be hampered under specific circumstances Risk of occurrence: Always under the described circumstances Workaround: Not available 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 97 16 Known Bugs 16.9 Troubleshooting, OAM, Statistics and Performance Monitoring cq300220057 ELC1, 8615 NE When multicast/broadcast frames greater than 1518 bytes are received in a line card or sent from it, the Rx/Tx multicast/broadcast frame counts are not incremented Instead, these packets are counted as unicast packets Impact: Statistics not work correctly for the mentioned packets Risk of occurrence: Always under the described circumstances Workaround: Not available cq300228011 CDC1, CDC2, 8609 NE, 8602 NE, 8615 NE SNMP tlab8600FaultMIB eventHistoryTable object value for eventHistoryLastTimeString shows value "01/01/2000 00:00:00" as null value (i.e the value to indicate that the event never happened) According to specification the null value should be "01/01/1970 00:00:00" Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: The user shall interpret "01/01/2000 00:00:00" as “never happened” cq300244475 IFC1, IFC2 When VC4 unequipped error is received in an STM-1 port of the 4xchSTM-1/chOC-3 Multiservice IFM (LIO2248), the port does not send back the VC4 RDI (Remote Defect Indicator) alarm Impact: VC4 Remote Defect Indicator alarm is not reported even when the STM-1 port is in VC4 unequipped state Risk of occurrence: Always under the described circumstances Workaround: Not available cq300245581 8615 NE When LSP traceroute command is executed for an unknown destination address, instead of "destination not reachable", the "timedout message" is seen Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Not available cq300248248 8615 NE Ethernet OAM ping is not working for a packet size of 1500 bytes and above with default link and IP MTU values There are no increments on the egress side (Tx) when Ethernet OAM ping is done with packet sizes of 1500 bytes and above Impact: Ethernet OAM ping request will not work for a packet size of 1500 bytes and above Risk of occurrence: Always under the described circumstances Workaround: By configuring both link MTU and IP MTU with 1530, ping works for a maximum packet size of 1504 bytes (1530-header(26)) cq300248949 ELC1 ELC1 has a reduced Ethernet OAM scalability in ELP protected interfaces ELP interfaces shall not contain more than 200 Remote-MEPs per ELC1 If the limit is exceeded, there is a risk that after ELC1 boot up, traffic connections are not restored properly Impact: Impact to live traffic if the limit is exceed Risk of occurrence: High under the described circumstances Workaround: Not available 8600 Smart Routers SR7.0 Embedded Software Release Notes 98 76.8670-50177B © 2015 Coriant 16 Known Bugs cq300255466 8615 NE, 8665 CU The drop precedence of ping and traceroute packets is always set to 'low' even if the user requests 'medium' or 'high' drop precedence Impact: Ping and traceroute miss the possibility to send AFx packets with drop precedence 'high' or 'medium' Risk of occurrence: Always under the described circumstances Workaround: Not available cq300256607 8665 CU When vlan-statistics is enabled/cleared for some 200 VLANs, the statistics value for or among them may not be cleared Impact: This does not have an impact on the traffic flow Only the VLAN statistics will not be cleared for the failed interface Risk of occurrence: Always under the described circumstances Workaround: Retrying the enable/clear command on the earlier failed VLAN interface will enable/clear the statistcs properly cq300257006 8615 NE While performing 'poweroff- reset', the 'Controlled unit reset' fault is raised instead of the 'Power off unit reset' fault This issue occurs very inconsistently Impact: It does not affect live traffic Risk of occurrence: Very rare Workaround: Not available 16.10 Other cq300240667 CDC1, CDC2, 8609 NE, ELC1, IFC1, IFC2 The 'set clock' command will not set the year with the maximum range specified in the 'help' command Impact: Trying to set the year as 2136 will fail In the info model page, the maximum limit for the year is from 2000 - 2135 The same is implemented in the code But in the help string, the range is wrongly given as (2000 - 2136), hence while setting the year 2136 alone there was a problem It is fixed by changing the help string as per the info model Risk of occurrence: Always under the described circumstances Workaround: Not available cq300254704 CDC1, CDC2, IFC1, IFC2, ELC1, 8609 NE, 8602 NE, 8665 CU, 8615 NE The values of attributes in managed objects tamHwResourceMeasure and tamHwResourceMeasureNe are changed to default values when upgrading element software to FP7.0 from earlier FPs Impact: If values have been changed from the default values, there will be inconsistency between the 8000 Intelligent Network Manager database and NE configuration Risk of occurrence: Always when values are changed from the default in pre-FP7.0 software Workaround: The values need to be reset after the upgrade cq300257126 8602 NE Change in 'qos mapping use ingress' parameters on a redundant PWE does not take effect as expected Impact: The 'qos mapping use ingress' does not take effect and the traffic is treated using old values Risk of occurrence: Always under the described circumstances Workaround: After configuring the 'qos mapping use ingress' values, that interface must be set to go down and then up again using 'shut' and 'no-shut' 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 99 16 Known Bugs cq300257150 CDC2, ELC1 When there is high traffic to the NE, fetching the current information from the HW-Inventory during NE reload is not working for the first 10 minutes of boot up It works fine after 10 minutes Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Not available cq300257278 8665 CU When a new software version is activated on the LU card, BFD starts flapping when BFD timers are set to value 10 Impact: Traffic is disrupted Risk of occurrence: Always under the described circumstances Workaround: Set BFD timers to value 100 cq300257358 8615 NE, 8615 NE Occasionally data traffic drop is seen (say around 0.01 to 0.09%) after multiple manual CU switchovers, only when the network element is enabled with different traffic flows (IP_VPN, ETH_PWE3 and IRB_VRRP) Impact: Data traffic will be dropped Risk of occurrence: Occasionally under the described circumstances Workaround: Not available 8600 Smart Routers SR7.0 Embedded Software Release Notes 100 76.8670-50177B © 2015 Coriant 17 Rejected Bugs 17 Rejected Bugs The CRs listed in this chapter have previously been communicated as known bugs They will not be fixed in future software releases and will thus be considered and documented as features, restrictions and limitations Consequently they are removed from the list of known bugs cq300200379 IFC1, IFC2 PPP links may not always be inserted into an MLPPP group Impact: MLPPP group cannot be configured with a desired PPP interface Risk of occurrence: Rare Workaround: Line card reload should be performed to enable all configurations pertaining to PPP interface cq300226103 8611 NE SCO1 sends AIS in E1 Framed mode Impact: If SCO1 is used as clock reference with E1 Framed mode configured, the receiving end sees AIS and discards the clock Risk of occurrence: Always on SCO1 Workaround: SCO1 should not be used for clock source, SCO2 should be used instead cq300230282 8609 NE Interoperability issue found between 8800 Smart Router STM-1/OC-3 IMA functionality and 8609 Smart Router, when the 8800 Smart Router STM-1/OC-3 interface is connected to 8609 Smart Router using 6335 Switch Node 6335 Switch Node is a cross-connect device to convert E1/T1 to STM-1/OC-3 If a protection switch occurs on an 8800 Smart Router IMA interface in a protection group, it is possible the IMA group on the 8609 Smart Router will not transition states correctly, causing the IMA group to transition to a DOWN state for approx twenty seconds This problem has been found in ETSI and ANSI modes with multiple links configured in the IMA group Impact: Potential 20 - 25 second traffic outage Risk of occurrence: Usually with four or more active IMA members Workaround: Not available 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 101 17 Rejected Bugs cq300230985 IFC2 When VLAN statistics are enabled for a VLAN interface on an IFC2, a line card that is rebooted (for example due to software upgrade) may enter into a very long reconfiguration loop The reconfiguration loop will eventually finish, but uses a lot of CPU This may starve other tasks in the system of CPU, and cause network protocols to timeout and clear established sessions The problem has been corrected in FP4.0 SP3, but older SW may have left internal databases in inconsistent state Thus upgrade to FP4.0 SP3 may also be affected Upgrade from FP4.0 SP3 to newer SW is not affected Impact: Network protocols may timeout and clear established sessions This will cause traffic cut until the sessions are re-established The duration of the cut depends on the number of VLANs with statistics enabled This may be several minutes in large configurations Risk of occurrence: Increases in direct proportion to the increase in the number of statistics enabled VLANs Hundreds of statistics enabled VLANs are almost certain to cause data breaks Workaround: Disable VLAN statistics during SW upgrade cq300242297 IFC1, IFC2 ATM circuits, which are members of a VCG group, not send OAM AIS cells when the VCG PWE3 is down Impact: OAM AIS consequent action is missing from the VCG member ATM circuits Risk of occurrence: Always under the described circumstances Workaround: Not available cq300243917 CDC2 The IEEE1588 clock identity is incorrectly set in dual CDC2 environments By default, both CDCs have a unique clockId while this identity should be global on one NE Impact: In case of CDC2 switchover, the IEEE1588 clockId is changed unless it was manually overwritten As a result the other IEEE1588 clocks may change their BMCA selection, and the synchronization topology of the network may be altered Risk of occurrence: Always under the described circumstances Workaround: Overwrite the IEEE clockId manually For example, from the CLI command 'node-timing ieee1588 clock-id' cq300244527 CDC2, ELC1, CDC1 When the passive CDC control card is rebooted, Y.1731 Loss Measurement counters may get too high values: existing counter values are incremented by 32-bit maximum value 4294967296 This issue happens on both UP and DOWN MEP, and also when MEPs not reside on the same line card (ELC1) Impact: Loss Measurement shows too high values Risk of occurrence: Low Workaround: For Current statistics, clear the statistics with CLI command 'clear eth cfm mp lm', and for History records, re-initiate the LM sessions (e.g remove and add LM Initiator config) 8600 Smart Routers SR7.0 Embedded Software Release Notes 102 76.8670-50177B © 2015 Coriant 17 Rejected Bugs cq300245984 8609 NE, 8611 NE After SW upgrade from 8609 Smart Router FP1.0.x to 8609 Smart Router or 8611 Smart Router FP1.2 SP2or FP1.3.x, IEEE1588 configurations related to acceptable-master settings will be lost Impact: IEEE1588 frequency synchronization is not recovered after the upgrade, until the acceptable-master settings have been reapplied Risk of occurrence: Always under the described circumstances Workaround: 1) Reapply the missing configurations manually or 2) Upgrade to FP1.1 first, and upgrade again to FP1.2 SP2 or FP1.3 cq300246007 8609 NE, ELC1, 8602 NE, 8611 NE If L2 priority mapping is used for non-VLAN MPLS trunk interface, behavior differs between and other 8600 products Non 8609/8611 products will not permit MPLS EXP classification (->BE class) while other 8600 products permit it (BE class can be overriddent by EXP classification) Impact: It does not affect live traffic Workaround: Do not use l2 classification for MPLS trunk interfaces if you not want L2 classification to be used Typical configuration for trunk interfaces is l3+l2 out, l3 in cq300252752 IFC2, ELC1 When a Gigabit Ethernet (GE) or a 10-Gigabit Ethernet (XE) port enters into hold down state based on the Loss of Signal (LOS), the 'If hold down' fault is not raised The 'show faults active' CLI command does not have a fault entry for this particular fault This is observed with GE/XE interfaces in the following module types: - 8x100/1000BASE-X R2 (LIO2252) - 8x10/100/1000BASE-TX R2 IFM (LIE2256) - 1x10GBASE-R R2 IFM (LIO2257) - ELC1 fixed interfaces 2x10GBASE-R and 12x1000BASE-X Impact: It does not affect live traffic Risk of occurrence: Always under the described circumstances Workaround: Not available 76.8670-50177B © 2015 Coriant 8600 Smart Routers SR7.0 Embedded Software Release Notes 103 ... cq 300 256432, cq 300 256561, cq 300 256 576, cq 300 256 607 , cq 300 256619, cq 300 256793, cq 300 256 900 , cq 300 25 700 6, cq 300 25 704 2, cq 300 25 707 3, cq 300 257126, cq 300 2571 50, cq 300 257154, cq 300 257278, cq 300 257287, cq 300 257358,... Release Notes: cq 300 2 406 67, cq 300 253544, cq 300 25 404 6, cq 300 254432, cq 300 254475, cq 300 254 704 , cq 300 255453, cq 300 255466, cq 300 255 504 , cq 300 255513, cq 300 25 5768 , cq 300 255844, cq 300 256215, cq 300 256432,... http://coriant.com/legal/documents/tellabs_product_specific_tandc.pdf 76. 86 70- 501 77B © 201 5 Coriant 8 600 Smart Routers SR7. 0 Embedded Software Release Notes 8 600 Smart Routers SR7. 0 Embedded Software Release Notes 76. 86 70- 501 77B © 201 5 Coriant Document