BTI™ 700 Series Ethernet Access Device Release Notes BTI 702, BTI 704, BTI 712, and BTI 718

BTI Systems, Inc. t: +1 613. 287. 1700 www.btisystems.com 1000 Innovation Drive, f: +1 613. 287. 1886 Suite. 200 Ottawa, ON K2K 3E7

Part Number: BT7B76DE product release 1.5.5 Document Version: 01 Published: January 2015 Type: STANDARD Copyright 2003-2015 BTI Systems, Inc. All rights reserved. The information contained herein is the property of BTI Systems, Inc. and is strictly confidential. Except as expressly authorized in writing by BTI Systems, Inc., the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by BTI Systems, Inc., the holder is granted no rights to use the information contained herein. Contents

1.0 BTI 700 Series EAD operational behavior 1-1

1.1 Features introduced in this release ...... 1-2 1.2 Hardware and software limitations of the BTI 700 Series EADs with no fix planned ...... 1-3 1.3 Network element release compatibility ...... 1-4 1.4 proNX Management Suite software compatibility ...... 1-6 1.5 BTI 700 Series EAD features not supported by proNX 900 Node Controller and proNX Service Manager ...... 1-7

2.0 Resolved limitations 2-1

2.1 Resolved BTI 700 Series limitations ...... 2-2 2.2 Resolved proNX 900 Node Controller limitations ...... 2-3

3.0 Known limitations 3-1

3.1 BTI 700 Series EAD limitations ...... 3-2 3.2 proNX 900 Node Controller limitations ...... 3-5

Product Release 1.5.5 STANDARD iii Contents

iv BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 C H A P T E R 1

1.0 BTI 700 Series EAD operational behavior

This section covers the following topics: • 1.1, “Features introduced in this release” • 1.2, “Hardware and software limitations of the BTI 700 Series EADs with no fix planned” • 1.3, “Network element release compatibility” • 1.4, “proNX Management Suite software compatibility” • 1.5, “BTI 700 Series EAD features not supported by proNX 900 Node Controller and proNX Service Manager”

Product Release 1.5.5 STANDARD 1-1 BTI 700 Series EAD operational behavior

1.1 Features introduced in this release

The following are the key features introduced in this release: • #37662 is now resolved [Software Limitations]. Refer to 2.1, “Resolved BTI 700 Series limitations” for details.

1-2 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 BTI 700 Series EAD operational behavior

1.2 Hardware and software limitations of the BTI 700 Series EADs with no fix planned

Table 1-1 Hardware and software limitations of the BTI 700 Series EADs with no fix planned

Limitation Affects The maximum valid value of rate-limit out (egress) is 6654 (approximately 415MB). BTI 702 When CAR is applied, the rate limitations are applied to packets up to 5400 in length. For BTI 702 the most accurate Ingress rate limiting, use the "meters" functionality of the NE. Some CLI commands such as show mac may take up to 30 seconds to display. BTI 702 MEF-9 “non-preservation” functionality is not supported BTI 702 and BTI 704 Egress port filters are not supported. BTI 702 and BTI 704 802.1ag and Y.1731 CCM messages below 1-second intervals are not supported. BTI 702, BTI 704, BTI 712, and BTI 718 It is not possible to apply filters to overlapping customer VLAN IDs. BTI 702, BTI 704, BTI 712, and BTI 718 Back-to-back might not link. For more information, contact your BTI Systems representative BTI 702 to obtain a copy of the Technical Information Bulletin (TIB) BTI-TIB 013-2011 Issue 01 Autoneg. A copper SFP plugged into a port will show “Optical” at the interface level. BTI 718 Virtual untag functionality is not supported. BTI 702 and BTI 704 BTI 702 SNMP walk will be slower if you are using inband management to connect to the BTI 702 BTI 702 node. The Inband communication has a speed limit. The Outband Management port does not have this limitation.

Product Release 1.5.5 STANDARD 1-3 BTI 700 Series EAD operational behavior

1.3 Network element release compatibility

For customers running Release 1.0, 1.2, 1.2.1, 1.4, or 1.4.1 who would prefer to upgrade to Release 1.5/1.5.2/1.5.3/1.5.4/1.5.5, see the system software upgrade procedure in the BTI 700 Series EAD Technical Product Guide or in the BTI 700 Series EAD Technical Product Guide for details on alignment of OS and BIOS files across the EAD portfolio. Important If a system software upgrade or downgrade is not performed correctly, it will result in a nonfunctional system.

Note R1.5.5 software image files are only available through BTI’s support portal.

Table 1-2 OS image files for Release 1.5.5

EAD OS image BTI 702 BTI702_V1.5.5_3_12Dec2014.Z – 2,269,650 bytes BTI 704 BTI704_V1.5.5_3_12Dec2014.Z – 4,294,366 bytes BTI 712 BTI712_V1.5.5_3_12Dec2014.Z – 4,294,025 bytes BTI 718 BTI718_V1.5.5_3_12Dec2014.Z – 4,293,039 bytes

Table 1-3 BIOS image files for Release 1.5/1.5.2/1.5.3/1.5.4/1.5.5

EAD BIOS image BTI 702 702bootrom_V1.3_28Dec2011.bin (359,392 bytes) BTI 704 BTI 712 BTI_704_712_718_V1.6_bootrom_28Dec2011.bin (281,600 bytes) BTI 718

Table 1-4 BIOS file compatibility for BTI 702 EADs

SW release (OS) SW release (OS) for BTI 702 EAD BIOS 1.0 BIOS 1.1 BIOS 1.2 BIOS 1.3 Release 1.2/1.2.1 Yes Yes Yes Yes Release 1.4/1.4.1 Yes Yes Yes Yes Release 1.5/1.5.2/1. Yes Yes Yes Yes 5.3/1.5.4/1.5.5

Table 1-5 BIOS file compatibility for BTI 704 and BTI 712 EADs

SW release (OS) SW release (OS) for BTI 704 and BTI 712 EADs BIOS 1.0 BIOS 1.1 BIOS 1.2 BIOS 1.3 BIOS 1.5 BIOS 1.6 Release 1.2 Yes Yes Yes No No No Release 1.2.1 Yes Yes Yes Yes No No Release 1.4/ 1.4.1 Yes Yes Yes Yes Yes Yes

1-4 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 BTI 700 Series EAD operational behavior

Table 1-5 BIOS file compatibility for BTI 704 and BTI 712 EADs (Continued)

SW release (OS) SW release (OS) for BTI 704 and BTI 712 EADs BIOS 1.0 BIOS 1.1 BIOS 1.2 BIOS 1.3 BIOS 1.5 BIOS 1.6 Release 1.5/1.5.2/1. Yes Yes Yes Yes Yes Yes 5.3/1.5.4/1.5.5

Table 1-6 BIOS file compatibility for BTI 718 EADs

SW release (OS) SW release (OS) for BTI 718 EADs BIOS 1.0 BIOS 1.1 BIOS 1.2 BIOS 1.3 BIOS 1.5 BIOS 1.6 Release 1.2/1.21 N/A N/A N/A N/A N/A N/A Release 1.4 N/A N/A N/A N/A Yes Yes Release 1.5/1.5.2/1. No No No No Yes Yes 5.3/1.5.4/1.5.5

Table 1-7 BIOS file revision history

BIOS release Revision Release 1.1 Added version number of BIOS Release 1.2 Added version number of hardware Revised booting information Release 1.3 Enabled BIOS version to display in CLI Release 1.5 Added OS backup recovery Resolved issue with in-band MAC address overwrite at manufacturing Resolved issue with BIOS version display noted in earlier BIOS versions Release 1.6 Added upgrade protection for upgrading from the Operating System prompt (VxWorks)

Product Release 1.5.5 STANDARD 1-5 BTI 700 Series EAD operational behavior

1.4 proNX Management Suite software compatibility

Table 1-8 proNX Management Suite compatibility matrix for BTI 700 Series EADs

proNX Product Release BTI 700 Series Release proNX 900 proNX Service Manager 1.2 8.1.2 1.0, 1.1, 1.2, 2.1, 2.2, 3.0 1.4 9.1 1.0, 1.1, 1.2, 2.1, 2.2, 3.0 1.5 9.3 2.2, 3.0 1.5.2 9.3 3.1 1.5.3 9.3 3.1, 3.2 1.5.4 9.3 3.3.2, 4.0 1.5.5 9.3 4.0, 5.2.1

For information about proNX Service Manager and proNX 900 Node Controller, refer to the product guides and Release Notes for each software application, which are available on the support portal at www.btisystems.com.

1-6 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 BTI 700 Series EAD operational behavior

1.5 BTI 700 Series EAD features not supported by proNX 900 Node Controller and proNX Service Manager

Table 1-9 BTI 700 Series EAD features not supported by proNX 900 Node Controller and proNX Service Manager

Feature Details Line and Client Protection LACP configuration on Link Aggregation STP, RSTP and MSTP – 802.1D Ethernet Switch Ring – ESR Redundancy Link – RLINK Ethernet Linear Protection Scheme (ITU-T G.8031) Ethernet Ring Protection Scheme (ITU-T G.8032) Ethernet Control Plane Link Layer Discovery Protocol (LLDP - IEEE 802.1AB) Display / Flush MAC Address Table Filter configuration Ethernet OAM Ethernet First Mile - 802.3ah Connectivity Management - 802.1ag Fault Management - Y.1731 Ethernet Local Management Interface (MEF 16 E-LMI) CVLAN Translation Video Applications IGMP Snooping and Proxy IGMP Filter IGMP Fast Leave Cross VLAN Multicast Security 802.1X and AAA Client DHCP Snooping Local Port Mirroring ACLs (MAC, IP, TCP, UDP, VLAN) Management SNMPv3 Provisioning FTP, TFTP, Telnet Syslogs and logging Advanced RMON settings System Software Management Force upgrade

Product Release 1.5.5 STANDARD 1-7 BTI 700 Series EAD operational behavior

1-8 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 C H A P T E R 2

2.0 Resolved limitations

This section covers the following topics: • 2.1, “Resolved BTI 700 Series limitations” • 2.2, “Resolved proNX 900 Node Controller limitations”

Product Release 1.5.5 STANDARD 2-1 Resolved limitations

2.1 Resolved BTI 700 Series limitations

Table 2-1 Resolved BTI 700 Series EAD software limitations

ID Description Affects 37662 Description: The BTI 700 Series device may reboot once or several 702 times if automated telnet / FTP connect and disconnect requests are 704 received frequently and repeatedly. In some instances, devices which have received repeated connect/disconnect requests, may 712 lose management connections and traffic may potentially become 718 disrupted. Additional information: If required, perform a local reload of the Node to restore management communication and enable traffic. Disable any unnecessary automated or repeated telnet or FTP connect/disconnect requests from external sources such as NMS or external Scripts. Upgrade the system to R1.5.5 which contains software to correct this issue. 28080 Description: ERPS CCM will report LOC if execute a resynch All operation on PSM server to retrieve all configuration data from all 700s nodes. 27839 Description: G8032 port status goes to a wrong status once the All ERPS CCM connectivity is broken and recovered. 27591 Description: Eservice VLAN provisioned via PSM fails to be added All to G8032 instance automatically sometimes.

2-2 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 Resolved limitations

2.2 Resolved proNX 900 Node Controller limitations

None in this release.

Product Release 1.5.5 STANDARD 2-3 Resolved limitations

2-4 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 C H A P T E R 3

3.0 Known limitations

This section covers the following topics: • 3.1, “BTI 700 Series EAD limitations” • 3.2, “proNX 900 Node Controller limitations”

Product Release 1.5.5 STANDARD 3-1 Known limitations

3.1 BTI 700 Series EAD limitations

Table 3-1 BTI 700 Series EAD limitations in Release 1.5

ID Description, Workaround, and Status Affects 353/10488 Description: Flow control is enabled on UTP ports by default. As a BTI 704, BTI 712, result, the "flowControl" setting for the port appears to be disabled and BTI 718 even when it is enabled. Workaround: From the UTP port CLI, re-enable or disable flow control as required. Status: Target release 2.0 10108 Description: The BTI 702 should not be the RPL Owner node for a BTI 702 G.8032 ERPS ring. Workaround: Use a BTI 704, BTI 712, BTI 718, or packetVX module as the RPL owner. Status: Target release 2.0 10669 Description: When RSTP is provisioned on one node and MSTP on All another node, packets could be lost for several seconds after a port shut down. Workaround: Avoid mixed-ring management protocols. Status: Target release 2.0 11002 Description: When RSTP is provisioned on one node and MSTP on All another node, the Spanning Tree config-name for RSTP must be configured using a value other than the default, otherwise Spanning Tree convergence may not complete. Workaround: Avoid mixed-ring management protocols. Status: Target release 2.0 11064 Description: For ELMI, following a system save and restart of the All Provider Edge node, additional EVC profiles cannot be configured. Workaround: Do the following: • Perform a system save using thewrite file command. • Perform a database backup. • Edit the database backup configuration file with the required ELMI changes. • Perform a database restore. • Restart the EAD. Status: Target release 2.0

3-2 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 Known limitations

Table 3-1 BTI 700 Series EAD limitations in Release 1.5 (Continued)

ID Description, Workaround, and Status Affects 12402 Description: The ELMI UNI status may read invalid. BTI 718 Workaround: From the CLI, disable and then re-enable elmi to display the proper status information. Status: Target release 2.0 12114 Description: A maximum 14 MSTP instances can be configured. A All 15th MSTP instance may not provide ring protection. Workaround: Do not configure more than 14 MSTP instances. Status: Target release 2.0 12933 Description: Copper SFPs cannot be pre-provisioned for interface BTI 718 speed and duplex mode. Workaround: BTI-qualified copper SFPs will auto detected the far- end Duplex type and speed, and establish handshake. The CLI will properly display the trained link status. Status: Target release 2.0 15685 Description: Error appears when multiple tasks are reading and All writing to flash at the same time; for example, when a configuration is saved via SNMP during system upgrade. Tasks may continue in the background; however communication to the node may be lost. Service is not affected; however, management communications may not be restored. Workaround: Additional care is required when writing to Flash to ensure that other sessions are not running simultaneously. Status: Target release 2.0 15066 Description: Software image in Bank B cannot be read properly. BTI 704, BTI 712, The command show version shows software image in Bank B and BTI 718 as N/A even when Bank B is not empty. Workaround: None. It is important to upgrade Bank B as part of the upgrade process. Status: Target release 2.0 (to be removed from displayed results) 16055/15684 Description: The MIBs wriSntpCommonTable, timeGeneral, All wriSntpClientTable, y1731RMepTable, y1731MepTable, y1731MegTable, and y1731MipTable do not support database change notifications. proNX Service Manager will not be notified of changes at the NE. Workaround: Refresh the proNX Service Manager GUI. Status: Target release 2.0 16121 Description: Virtual untag functionality is not supported on Trunk BTI 712 and BTI 718 ports. Workaround: None Status: Target release 2.0

Note

Virtual untag functionality is not supported on BTI 702 and BTI 704 EADs.

Product Release 1.5.5 STANDARD 3-3 Known limitations

Table 3-1 BTI 700 Series EAD limitations in Release 1.5 (Continued)

ID Description, Workaround, and Status Affects 16341 Description: If running BIOS v1.2, corrupting the OS image in Bank BTI 702 A followed by system reboot may result in non-recovery state. The device may not switch to Bank B for recovery. 19727 Description:The RADIUS default re-transmit time will take longer All than the default stated. This is only a problem at default. Workaround: Set the RADIUS re-transmit setting manually, and the new time will be honored. 23230 Description: Ingress meters should not be applied to LAG ports. All Following a system reboot, the policer throughput on the LAG may change. It is not typical practice to apply ingress policing on NNI ports. UNI LAG port provisioning is the most likely application/ impact. Workaround: None. 23265 Description: Ethernet OAM discovery function will not work across All LAG ports. Workaround: None.

3-4 BTI™ 700 Series Ethernet Access Device Release Notes – Document Version 01 Known limitations

3.2 proNX 900 Node Controller limitations

Table 3-2 proNX 900 software limitations

ID Description, workaround and status Affects 13208 Description: It is not possible to configure the Outband IP address PP2A40GA and the Gateway at the same time. Workaround: Use the CLI to provision the Outbound IP and Gateway addresses. 13902 Description: If two or more bandwidth profiles are created with PP2A40GA identical settings apart from their names, the Policy Map editor will default to the first duplicate in the list regardless of which one is selected. Workaround: Avoid creating duplicate bandwidth profiles. 19693 Description: On a BTI 702 EAD, when an EVP service with an PP2A40GA added policy map is provisioned , the EVP service is not created properly. As a result, the S-VLAN will join the interface; however, the C-VLAN translation (filter) is not created properly and, consequently, the C-VLAN translation data traffic will not pass on the new Eservice. No error response will be provided.

Note

This limitation does not impact existing services. Provisioning of an EVP service with policy map was blocked in earlier proNX 900 releases for BTI 702.

Workaround: The EVP service can be removed using . The C- VLAN EVP service with policy mapping will need to be done using the CLI. Status: Target release proNX 10.1. 23249/18843 Description: The removal of an NNI using proNX SM is not PP2A40GA reflected in proNX 900. Workaround: Re-sync the proNX 900.

Product Release 1.5.5 STANDARD 3-5

BTI Systems, Inc. t: +1 613. 287. 1700 www.btisystems.com 1000 Innovation Drive, f: +1 613. 287. 1886 Suite. 200 Ottawa, ON K2K 3E7

Part Number: BT7B76DE product release 1.5.5 Document Version: 01 Published: January 2015 Type: STANDARD