MRV Chatsworth Product Division EM316LNXNM-OT v4.7 fdr 35 Release Notes Published 2012/03/21 at 09:48:57 r20134- for-v4.
Copyright © 2007,2008,2009,2010,2011,2012 Communications, Inc. MRV All rights reserved. No part of the contents of this document may be reproduced in any form or by any other means without written permission from the publisher. Fiber Driver, Media Cross Connect, MegaVision, and other MRV product names and terms belong to MRV Communications or affiliates. All other brand names or trademarks referenced are the property of their respective owners.
Table of Contents Confidential ................................................................................................................... xi 1. Introduction ................................................................................................................... 1 1.1. Overview ............................................................................................................ 1 1.2. Abstract .........................................................................................
MRV Chatsworth Product Division 5.12.2. Loopback mac at 10 Mbps does not return frames ......................................... 5.12.3. LIN configuration that is issued while CPE is disconnected is not sent to the CPE after reconnection ...................................................................................... 5.13. EM316EUSM (Stage1) issues .............................................................................. 5.13.1. Administratively disabled trunk port may enable transmitter .......
MRV Chatsworth Product Division 6.2.19. SSH session denied due to low available memory. ........................................ 6.2.20. Image size is too big, unable to upgrade. ..................................................... 6.3. CLI Issues-All Fiber Driver Modules ..................................................................... 6.3.1. Time/process intensive commands and the "Q" key ......................................... 6.3.2. Time lag when a command is entered ............................
MRV Chatsworth Product Division 6.11.7. A few no loopback issues ................................................................... 49 6.11.8. Inactive trunk SP LED blinks during user port loopback ................................. 49 6.11.9. Error message "traffic-gen action is invalid" displayed : when and why ? ........... 50 6.11.10. After power cycle of CPE, 'Traffic Generation' status incorrect ....................... 51 6.11.11. Link aggregation per source MAC address does not work ................
MRV Chatsworth Product Division 6.15.5. Dribble error packets are not recorded as error packets ................................... 68 6.16. EM316E1MUX4RJRM, EM316E1MUX4RM, EM316T1MUX4RM issues .................. 69 6.16.1. 'off-line' configuration of CPE is not always guaranteed ................................. 69 6.16.2. Notes about a CPE module in the same chassis with LNXNM ......................... 69 6.16.3. "Hardware Revision: 0" for CPE module .....................................................
MRV Chatsworth Product Division 6.22.15. Multi-CO mode: Rare miss-reporting of lost frames ..................................... 6.22.16. Multi-CO mode: Slow updates on remote status .......................................... 6.22.17. Multi-CO mode: Incorrect 'Auto Neg Wait' and 'MDI Pinout' shown for CPE copper user port after reset of NM or CO .............................................................. 6.22.18.
List of Tables 4.1. 4.2. 4.3. 4.4. 5.1. Currently supported modules(CA/GA) .............................................................................. 4 Currently supported modules (Beta) ................................................................................. 5 Newly supported modules (CA/GA) ................................................................................ 6 Modules with updated line-card code ...............................................................................
Confidential The information contained herein is the property of MRV Communications and is strictly confidential.
Chapter 1. Introduction 1.1. Overview This document lists the changes made from the previous and formally released EM316LNXNM-OT network management module firmware version of - v4.5 build NN; including fixes and issues for the new version. As and if new issues are found, this document will be updated and redistributed accordingly. Please refer to the MRV website for the latest version of this document. 1.2. Abstract The EM316LNXNM-OT is Fiber Driver network management module (NMM) from MRV Communications.
Chapter 2. IMPORTANT: Read the following. 2.1. Overview This chapter lists a few very important steps that need to be considered before attempting to upgrade to the new version of the EM316LNXNM-OT firmware. 2.2. BZ# NNNN notation used in this document Throughout this document you will notice reference numbers as shown above. You may choose to ignore this number, as this number refers to the database maintained within MRV CPD. 2.3.
Chapter 3. CLI Syntax changes Important Please read this chapter completely before upgrading to this software version. 3.1. CLI syntax changes since v4.5 build NN Please read this document completely before using this EM316LNXNM-OT software version, as you may have to take measures to keep your system configuration intact. 1. The following command has been replaced: snmp-server trap-port <1-65535> Recommend to use the following command instead: snmp-server host A.B.C.
Chapter 4. List of modules supported 4.1. Currently supported modules The following currently supported modules underwent full validation testing and were formally released as Controlled Availability/General Availability as defined in the Product Life Cycle. Table 4.1.
List of modules supported Module name Line-card version(if applicable) EM316ERM/xx EM316EFRM/xx EM316FRM/xx EM316O3C/xx EM316DS3/xx EM316E3/xx EM316E1/xx EM316T1/xx NC316BU-4S EM316FC400 FPGA: 0x5b,0x5c NC316BU-2/15 EM316-10G-XY FPGA: 0x68 EM316GSW-XY FPGA: 0x70, 0x72 EM316T1E1-XY FPGA: 0x65,0x67 EM316EUSM-10G FPGA: 115A.0004, CPLD: 0202/1.0 (026), FPGA: 115A.0006, CPLD: 0202/1.3 (040) EM316-10G8SW-XY FPGA: 215A.0007, CPLD: 1031/1.1 (025), FPGA: 215A.0008, CPLD: 1032/1.
List of modules supported Module name Line-card version(if applicable) EM316E/xx EM316OSW128 Firmware 0x5A NC316-MDX46MA002 NC316-MDX46MA003 4.2. Newly added modules The following newly supported modules underwent full validation testing and were formally released as Controlled Availability/General Availability as defined in the Product Life Cycle. Table 4.3.
Chapter 5. Issues fixed with firmware v4.7 fdr 35 5.1. Overview The following is a list of issues fixed. For more information please contact support@mrv.com. 5.2. EM316LNXNM-OT 5.2.1. memo level log messages are for debug users only (BZ#: 2591) Description: Debug messages at the memo level (set by log level running memo command) are only available to debug users after issuing a log debug command.
Issues fixed with firmware v4.7 fdr 35 5.2.3. LNXNM cards lockup occasionally (BZ#: 9084) Description: LNXNM modules locked up and stopped management communications. The chassis had EM316OSA, EDFA, EUSM10G and EUSM modules. There seemed to be a memory shortage. The remedy was to manually powercycle the LNXNM module. Suggested Work-Around: Manually powercycle the LNXNM module. Customer Impact: Major inconvenience.
Issues fixed with firmware v4.7 fdr 35 5.4. EM316EUSM (Stage2) issues 5.4.1. firmware download issues (BZ#: 6089) Description: Multiple 'revisions' of the firmware can not be used to update the line-card code at the same time in a given chassis. For example, you can not use firmware download euRel_0070.rev on slot 1.2 and at the same time use firmware download eu-Rel_0069.rev on slot 1.5. Corrective Action: This issue has been fixed. 5.4.2.
Issues fixed with firmware v4.7 fdr 35 5.4.4. EM316EUSM: 'traffic-gen-load' command changes 'Frame Size Type'. (BZ#: 8575) Description: When using the traffic generation 'load' command to specify percentage traffic load for traffic generation, the translation of this value to a fixed inter-packet-gap requires a fixed frame size. If 'frame-size-type' is set to 'random', the run-time setting is changed to 'fixed' to allow for the load-to-ipg translation.
Issues fixed with firmware v4.7 fdr 35 5.6.2. Loopback timer does not work on ports in remote CPE modules (BZ#: 5862) Description: The loopback-timeout command has no effect on loopback status on ports in remote CPE modules. Ports on remote CPE modules remain in loopback even after loopback timer expires. Corrective Action: This issue has been fixed. 5.7. EM316EFE1RM, EM316EFT1RM, EM316EFE1RJRM, EM316EFE1MUXRJ, EM316EFE1MUX4, EFT1MUX4 issues 5.7.1.
Issues fixed with firmware v4.7 fdr 35 5.8.2. Loopback timer does not work on ports in remote CPE modules (BZ#: 5862) Description: The loopback-timeout command has no effect on loopback status on ports in remote CPE modules. Ports on remote CPE modules remain in loopback even after loopback timer expires. Corrective Action: This issue has been fixed. 5.9. EM316E1MUX4RJRM, EM316E1MUX4RM, EM316T1MUX4RM issues 5.9.1.
Issues fixed with firmware v4.7 fdr 35 5.11. EM316DMR3G-3R issues 5.11.1. Mapping changes might not be saved after an NM restart cold (BZ#: 8780,8777) Description: User changes DMR3G from a redundant module to a repeater by issuing no redundancy command, and then modifies the default mapping and saves it. If user then does a restart cold of the NM, the saved mapping might not be applied upon reboot, due to timing issues.
Issues fixed with firmware v4.7 fdr 35 5.12.3. LIN configuration that is issued while CPE is disconnected is not sent to the CPE after reconnection (BZ#: 7655) Description: LIN is ON on both CO and CPE. CPE is then disconnected and LIN is turned off on the CO. When CPE is reconnected, its LIN status is not changed and stays ON. Suggested Work-Around: Reissue no LIN once CPE is reconnected. Customer Impact: Minor inconvenience. Corrective Action: This issue has been fixed. 5.13.
Issues fixed with firmware v4.7 fdr 35 5.13.3. Dual Home: No CO switch-over when disconnecting active CO user port (BZ#: 4891) Description: In a dual-home setup with LIN disabled, loss of the active CO user port did not initiate a switchover to the inactive CO. Suggested Work-Around: For dual-home setups, it is strongly suggested to enable LIN service (lin command) on both COs. Customer Impact: Minimal. Informational only. Corrective Action: This feature works per design. 5.14.
Issues fixed with firmware v4.7 fdr 35 5.15. EM316E1MUX4RJRM, EM316E1MUX4RM, EM316T1MUX4RM issues 5.15.1. In Unmanaged-Remote loopback, LEDs for user ports show wrong information (BZ#: 4513) Description: The Unmanaged-Remote loopback is implemented on the LIU instead of on the Teknovus. When the LIU is put in remote loopback, the link shows OK, but there is no traffic going to the LIU transmitting side.
Issues fixed with firmware v4.7 fdr 35 5.17. EM316-10G-XY issues 5.17.1. Module reboots when redundant power supply is powercycled repeatedly (BZ#: 8295) Description: Powercycle repeatedly and very fast (fast switching) the standby power supply of a 16BU or BU16/15 chassis. The 10G-XY modules in the chassis reboot once in a while and traffic is lost. Suggested Work-Around: None. Repeated fast switching of a power supply will happen very rarely. Customer Impact: Moderate to severe.
Issues fixed with firmware v4.7 fdr 35 5.18.2. Repeater mode RJ48 port loopback leaks through (BZ#: 7266) Description: In repeater mode selecting loopback on one RJ48 port loops the traffic back to the source and also leaks through to the other RJ48 port. Suggested Work-Around: None. Customer Impact: Minor. Corrective Action: This issue has been fixed. 5.19. EM316FDT1E1RM issues 5.19.1.
Issues fixed with firmware v4.7 fdr 35 5.19.2. Fast Ethernet performance numbers (BZ#: 8225) Description: The current implementation (FPGA rev 0x8B) supports maximum FE (Fast Ethernet) performance as explained in the following paragraphs. When E1 traffic exists on both port 1 and 4, on CO/CPE port 3 sending and receiving ethernet packets at 100% utilizations at 100M full duplex speed from the tester and measuring the Tx/Rx packets sent and received by the tester use the following formula.
Issues fixed with firmware v4.7 fdr 35 5.21. EM316DMR10G-3R issues 5.21.1. Pattern check duration is not restored after restart warm (BZ#: 8986) Description: Pattern check duration is not restored after a restart warm or powercyle of the NM. Suggested Work-Around: User has to reissue the pattern-check duration command. Customer Impact: Moderate. Corrective Action: This issue is fixed in v4.7 fdr 30 and later releases. 5.21.2.
Chapter 6. Known issues with firmware v4.7 fdr 35 6.1. Overview Presented here is a list of known issues and limitations found for the most recent software build with the EM316LNXNM-OT and its supported line cards. Suggested work-around is supplied where possible. For more information please contact support@mrv.com. mailto:support@mrv.com 6.2. EM316LNXNM-OT 6.2.1. Message "i2c irq timeout, bus hung?" (BZ#: 854,3806) Description: "i2c irq timeout, bus hung?" message continues repeating itself.
Known issues with firmware v4.7 fdr 35 6.2.3. Behavior of un-supported modules (BZ#: 4358) Description: Modules that are not yet supported by the EM316LNXNM-OT network manager will NOT be seen by show slots. It is as if the module does not exist in the chassis. Please refer to supported modules for up to date list. Few really old/legacy unsupported modules may affect the i2c bus and hence destabilize the whole chassis. It is strongly recommended NOT to keep the unsupported modules in the chassis.
Known issues with firmware v4.7 fdr 35 6.2.6. Broadcast IP address is automatically set (BZ#: 914) Description: The EM316LNXNM-OT automatically sets the broadcast IP address when its IP address is set. Suggested Work-Around: None. Customer Impact: Minimal. Informational only. Corrective Action: This issue will be addressed in future software upgrades. 6.2.7.
Known issues with firmware v4.7 fdr 35 6.2.9. Startup-config can be overwritten by ">" and ">>" for SUPER level users (BZ#: 5311) Description: Using the new ">" and ">>" arguments at the end of each command, it is possible to overwrite the current startup-config file (if the user has permission to the file). Only SUPER users have access to this file, so it is not a security hazard. Since this is mostly used as a dynamic system, this shouldn't be a problem for most users.
Known issues with firmware v4.7 fdr 35 6.2.10. SFP port on LNXNM shows Tx octets when there is nothing plugged in (BZ#: 5620) Description: SFP port 2 on LNXNM displays increasing Tx counters even though port is not populated and discovery is disabled with no sys discovery. fiberdriver(config)# Slot Model ==== ============= 1.1 EM316LNXNM-OT show slots Name ==================== EM316LNXNM-OT at 1.1 Mac Address ================= 00:20:1a:02:13:ef fiberdriver(config)# show 1.1.2 Port: 1.1.
Known issues with firmware v4.7 fdr 35 6.2.11. Host IPs with all zeroes or all ones are not accepted (BZ#: 5688) Description: When setting up an IP on the network management module, all zeroes or all ones host IPs are not accepted. fiberdriver(config)# ip interface 192.168.0.0 'ip interface' not supported or bad argument. fiberdriver(config)# ip interface 192.168.12.0 'ip interface' not supported or bad argument. fiberdriver(config)# ip interface 192.168.12.
Known issues with firmware v4.7 fdr 35 6.2.13. NM with VLAN ID 0 (disabled) will not forward VLAN packets (BZ#: 7461) Description: An NM that has VLAN tagging disabled does NOT forward VLAN tagged packets between its RJ45 and SFP ports. Suggested Work-Around: None. Customer Impact: Minimal. Informational only. Corrective Action: This feature works per design. 6.2.14. LNXNM-OT: SSH session from serial CLI timeout is too long. (BZ#: 8601) Description: Hung SSH sessions within the console appear frozen.
Known issues with firmware v4.7 fdr 35 6.2.17. LNXNM-OT: RmonDeleteRow: . . .can't fetch variable (no such). (BZ#: 8625) Description: On module removal and re-insertion, this is expected behavior. On removal the module RMON settings in the LNXNM-OT are removed, but they persist in MegaVision. When the settings are polled, the error is seen until the RMON settings are available in the LNXNM-OT. Suggested Work-Around: None. This is expected behavior. Customer Impact: Minimal.
Known issues with firmware v4.7 fdr 35 6.2.20. Image size is too big, unable to upgrade. (BZ#: 9162,9365) Description: User was unable to upgrade from v4.3fdr18 to v4.7fdr30 or higher. Suggested Work-Around: It is suggested to first upgrade with the image without megavision, uImage-v47fdr30-no-mvj.initrd, and then install the mvj megavision package. Customer Impact: Moderate. Corrective Action: This issue will be addressed in future software upgrades. 6.3. CLI Issues-All Fiber Driver Modules 6.3.1.
Known issues with firmware v4.7 fdr 35 6.3.3. freeSSHd telnet server problem (BZ#: 3756) Description: The telnet client on the NM does not work with the freeSSHd telnet server. The login (username and password) works properly. After the login, no input is accepted and the CLI is frozen. Suggested Work-Around: Use a different TELNET SERVER product. Customer Impact: Minimal. Informational only. Corrective Action: This issue will be addressed in future software upgrades. 6.3.4.
Known issues with firmware v4.7 fdr 35 6.3.5. Fan Failure/Restored repeated traps/messages (BZ#: 3832) Description: When the FAN is forcefully stopped (by putting obstruction to the fan blades) "FAN Failure" and "Fan Restored" traps are sent repeatedly. Suggested Work-Around: None. Customer Impact: Minimal. Informational only. Corrective Action: This issue will be addressed in future software upgrades.
Known issues with firmware v4.7 fdr 35 6.3.6. A note about command syntax in the scripts (BZ#: 4633) Description: Limited amount of syntax checking is implemented in LNXNM. The permitted command syntax is the one which follows the syntax of the commands displayed in show defaults or show config at each context (chassis, slot or port). As soon as a syntax error occurs at any given context, the remaining commands in the script, that follow the syntax error, also fail for that given context.
Known issues with firmware v4.7 fdr 35 6.3.7. The interactive login banner doesn't accept arrow keys (BZ#: 4016,5150) Description: The arrow keys are not supported when adding an login banner interactively. Suggested Work-Around: Instead of using the right arrow key use Ctrl-F to move the cursor to the right. Instead of using the left arrow key use Ctrl-B to move the curse to the left. Customer Impact: Minimal. Informational only. Corrective Action: This issue will be addressed in future software upgrades.
Known issues with firmware v4.7 fdr 35 6.3.10. Module hot swap shows error condition (BZ#: 8572) Description: After removing a module, the following meassage is observed: fdrd[115]|kern| failed fdrd[115]|kern| fdrd[115]|kern| PEM read failed fdrd[115]|kern| fdrd[115]|kern| fdrd[115]|kern| PEM read failed fdrd[115]|kern| err|May 11 09:46:57 user_counters: 1.5: PEM read warn|May 11 09:46:57 1.5: failed sdr_reg_flush_ll err|May 11 09:46:57 port_get_pluggables_data: 1.5.1: warn|May 11 09:46:57 1.
Known issues with firmware v4.7 fdr 35 6.4.3. SNMP GET on icmpOutEchos.0 is always zero (BZ#: 4614) Description: When ping is used from LNXNM CLI, the counter icmpOutEchos is expected to increase. However, since this is a Linux kernel level bug, this counter remains at 0. Suggested Work-Around: None. Customer Impact: Minimal. Informational only. Corrective Action: This issue will be addressed in future software upgrades.
Known issues with firmware v4.7 fdr 35 6.5. EM316DMR3G-3R issues 6.5.1. Unexpected traps from Beacon-LIN (BZ#: 4346) The DMR3G-3R board is not designed to handle "Beacon-LIN". Beacon-LIN is only available on copper-to-fiber converters, with fiber serving as the trunk. When the converter detects loss of link on the trunk, it disables its user transmitter and begins rapidly toggling the trunk link to its peer as a backward failure notification. The beacon causes the peer to disable its user port transmitter.
Known issues with firmware v4.7 fdr 35 6.5.2. Administrative and Operational Port Map (BZ#: 4357) Description: Any changes to the port map while operating the EM316DMR3G-3R in Redundant Mode will only apply to the administrative port map, not the operational map. The administrative port map and changes made to it will become the operational port map when switching out of redundant mode to repeater mode. Suggested Work-Around: None.
Known issues with firmware v4.7 fdr 35 6.5.5. No "User-Defined" protocol available (BZ#: 716) Description: There is no "User-Defined" protocol supported for this module. Suggested Work-Around: None. Most of the popular protocols are already supported. If there is any need for a specific protocol, please contact support@mrv.com to be incorporated in the syntax for protocol. Customer Impact: Minimal. Informational only. Corrective Action: This issue will be addressed in future software upgrades. 6.5.6.
Known issues with firmware v4.7 fdr 35 6.5.8. Standby port disable/enable causes active port toggle (BZ#: 9105) Description: Two redundant mode DMR3G modules are connected together via ports 1 and 2 trunk ports. User ports 3 (active) are connected to traffic source. Ports 4 are standby. If user issues shutdown / no shutdown commands on the standby user port 4, which is not a common occurrence, the active user port 3 will toggle to become standby and then active again.
Known issues with firmware v4.7 fdr 35 6.7. EM316GEMX2R issues 6.7.1. Issues on 1:1 redundant-tx-mode (BZ#: 2675,4098,4070) Description: It is important to note that 1:1 revertive-mode is not supported. 1:1 non-revertive mode also has certain issues described in this section. For most applications it is recommended to use 1+1 revertive-mode. A redundant trunk is used to provide an alternate path for traffic to continue flowing in the event that the primary trunk becomes disabled.
Known issues with firmware v4.7 fdr 35 6.7.2. Three DIP-switch status improperly reported in UN-managed mode (BZ#: 4180) Description: LIN functionality is OK, but show can display the wrong state. If the management enable DIP switch is OFF (SW1.0), and the LIN DIP switch is ON(SW1.1), the show command can report LIN as "disable" even though the switch is ON. The same is true for DIP switches SW1.2 and SW1.3.
Known issues with firmware v4.7 fdr 35 6.7.5. Tester ports don't get link after GEMX2R reboot (BZ#: 8851) Description: Connect GEMX2R ports directly to a tester or EUSM ports that are auto-negotiating. Occasionally, the tester ports don't show link after GEMX2R reboots. Suggested Work-Around: Issue shutdown and then no shutdown commands on affected GEMX2R or tester port to recover link. Customer Impact: Moderate. Corrective Action: This issue will be addressed in future software upgrades.
Known issues with firmware v4.7 fdr 35 6.8. EM316MRMX2R issues 6.8.1. Issues on 1:1 redundant-tx-mode (BZ#: 2675,4098,4070) Description: It is important to note that 1:1 revertive-mode is not supported. 1:1 non-revertive mode also has certain issues described in this section. For most applications it is recommended to use 1+1 revertive-mode. A redundant trunk is used to provide an alternate path for traffic to continue flowing in the event that the primary trunk becomes disabled.
Known issues with firmware v4.7 fdr 35 6.8.2. Three DIP-switch status improperly reported in UN-managed mode (BZ#: 4180) Description: LIN functionality is OK, but show can display the wrong state. If the management enable DIP switch is OFF (SW1.0), and the LIN DIP switch is ON(SW1.1), the show command can report LIN as "disable" even though the switch is ON. The same is true for DIP switches SW1.2 and SW1.3.
Known issues with firmware v4.7 fdr 35 6.10. EM316FRM,EM316ERM,EM316EFRM issues 6.10.1. IPLESS port shutdown status issue (BZ#: 4578) Description: When a pair of above listed modules are used as CO-CPE pair with a valid physical connection between the CO-CPE trunk ports, status update for shutdown on IPLESS port (port 3) works properly and almost instantaneously. Confusion arises when the connection between the CO-CPE is missing.
Known issues with firmware v4.7 fdr 35 6.11.2. Incorrect copper user port counter value(s) after link down event (BZ#: 6195) Description: A link down event on a user port configured for auto-negotiation may cause one or more of its statistic values to become incorrect. The correct value may increase by 4,294,967,296, due to a mistaken counter wrap-around increment, or be replaced by a neighboring value. Both of these inaccuracies are illustrated by the following example: fiberdriver(port/2.4.
Known issues with firmware v4.7 fdr 35 6.11.3. New bandwidth provisioning commands (BZ#: 5932) Description: There are two new slot-level commands for specifying bandwidth provisioning on EUSM (Stage 2) modules. 1. The command user-port-limit replaces threshold to limit the amount of traffic incoming on the user port. Whereas the value range for threshold is 0-1000 (Mbps) and zero is equivalent to no limit, the value range for user-port-limit is 0-1000000 (Kbps) and zero means no bandwidth. 2.
Known issues with firmware v4.7 fdr 35 6.11.6. Warning message "loopback restriction violation" displayed : when and why ? (BZ#: 5509,5749) Description: A warning level log message gets generated after a significant delay, following a loopback... command. There are several reasons why a loopback is rejected by the line-card. The following list shows a few of such reasons. 1. Loopback is rejected on the inactive user port. 2. Loopback is rejected if trunk aggregation is enabled. 3.
Known issues with firmware v4.7 fdr 35 6.11.7. A few no loopback issues (BZ#: 5971,5975,6000) Description: Issuing no loopback on certain ports causes some unexpected behavior. There are several new advanced loopback options implemented. no loopback is also implemented for consistency. However, issuing no loopback causes some unexpected "Auto-adjusted" commands being issued, creating confusion. CO user ports 3,4 and CPE trunk ports 1,2 exhibit the unexpected behavior as described below.
Known issues with firmware v4.7 fdr 35 6.11.9. Error message "traffic-gen action is invalid" displayed : when and why ? (BZ#: 5613) Description: Whenever traffic generation on a port is not allowed, above indicated error message is displayed after using command traffic-gen action start. There are several reasons why a traffic-gen action start is rejected by the line-card. The following list shows a few of such reasons. 1. Using traffic-gen on a non-preferred user port. fiberdriver(port/1.2.
Known issues with firmware v4.7 fdr 35 6.11.10. After power cycle of CPE, 'Traffic Generation' status incorrect (BZ#: 5926) Description: If traffic generation is begun on a CPE port, and the CPE goes through a power cycle, the port is no longer generating traffic but the NM command show eusm for that port reports that it still is. Suggested Work-Around: Traffic generation may be resumed on the same port with the command traffic-gen action start.
Known issues with firmware v4.7 fdr 35 6.11.12. Dual Home: Unexpected CO switchover on CPE user reconnect (BZ#: 5457) Description: When LIN is enabled, losing then regaining link on the CPE user port may cause a switchover to the inactive CO. This is possible whether the CPE user port is configured for auto-negotiation or fixed speed/duplex. Suggested Work-Around: There is nothing that can be done to prevent this from happening.
Known issues with firmware v4.7 fdr 35 6.11.13. Dual Home: Disabling auto-negotiation on CO user port causes switchover (BZ#: 5547) Description: In a dual-homing setup, disabling auto-negotiation on the active CO's user port causes a switchover to the inactive CO, if its user port can establish link. Suggested Work-Around: To prevent a change in active COs while reconfiguring the user port, make the inactive CO unavailable for service by disabling its trunk port: shutdown.
Known issues with firmware v4.7 fdr 35 6.11.16. Some tagged user frames may be stripped of their VLAN tag during PM in FE mode (BZ#: 8156) Description: This misbehavior has been observed for a small percentage of tagged user frames when the Management Vid has a value in the range 1-255; untagged user frames are unaffected. Suggested Work-Around: Set the Management Vid to a value in the range 256-4094. Customer Impact: Minor inconvenience.
Known issues with firmware v4.7 fdr 35 6.12. EM316EUSM (Stage1) issues 6.12.1. Notes about a CPE module in the same chassis with EM316LNXNM-OT (BZ#: 4295) Description: CPE module in the same chassis as EM316LNXNM-OT is supported for identification purpose only. However, a CPE module is expected to be connected to a CO module and the management happens through the CO and EM316LNXNM-OT management interface. show at the slot-context is expected to display enough information for identification purpose.
Known issues with firmware v4.7 fdr 35 6.13. EM316GRMAHSH issues 6.13.1. Changing "auto-negotiation" appears to have no effect on non-preferred user port (BZ#: 4198) Description: auto-negotiation and no auto-negotiation appear to have no effect on fiber user port, if the port is not preferred. show does not confirm that auto-negotiation has changed. Suggested Work-Around: The configuration change can be confirmed using show config instead of just show . show is supposed to report operational state.
Known issues with firmware v4.7 fdr 35 6.13.4. Dual Home: setup precautions (BZ#: 4208,4338) Description: When using the dual home setup, please follow listed precautions. Important a) Enable LIN; the CPE will make better decisions about which CO should be active. b) AVOID using operation-type(formerly select-homing), as careless use of this command will put the connection to the CPE at risk.
Known issues with firmware v4.7 fdr 35 6.13.5. Connected for Dual-Home, but configured as Single-Home may cause inconsistent behavior. (BZ#: 4341) Description: A setup meant for Dual-Home operation using 3 EM316GRMAHSH boards, could be configured (via CLI or MegaVision) to be Single-Home operation, even though the connection is meant for Dual-Home operation. After issuing homing singleco to change from a dual-homing to a single home, both CLI and MegaVision will show CPEs connected/managed from both COs.
Known issues with firmware v4.7 fdr 35 6.13.7. When local user port loopback is ON, trunk port MAC counters behavior is different. (BZ#: 4384) Description: Trunk port counter behavior is slightly different between the AH products when the local user port loopback is ON. The difference is described in the following paragraphs. In the case of EM316EFRMAHSH modules, the trunk port MAC counters only reflect the management packets and the user traffic is reflected only on the user ports. fiberdriver(slot/1.
Known issues with firmware v4.7 fdr 35 6.13.9. "no shutdown" does not seem to work on inactive-CO (BZ#: 4273) Description: On an inactive-CO, shutdown disables the user port and show confirms the same. But consequent no shutdown does not seem to re-enable the user port for the same inactive-CO. In other words, it can not be confirmed by using show. Suggested Work-Around: The inactive-CO (in a dual-home setup) user port transmitter is always disabled regardless of its desired state.
Known issues with firmware v4.7 fdr 35 6.14. EM316EFRMAHSH issues 6.14.1. Occasionally "auto-negotiation" on CPE user port switches the active trunk on CPE (BZ#: 4192) Description: This problem happens every once in a while. The active trunk on the CPE can switch to the other trunk when commands are sent to change the 'auto-negotiation' on the CPE user port. Suggested Work-Around: select-link active can be used to revert back to the original CPE trunk port, if needed. Customer Impact: Minimal.
Known issues with firmware v4.7 fdr 35 6.14.3. Dual Home: setup precautions (BZ#: 4208,4338) Description: When using the dual home setup, please follow listed precautions. Important a) Enable LIN; the CPE will make better decisions about which CO should be active. b) AVOID using operation-type(formerly select-homing), as careless use of this command will put the connection to the CPE at risk.
Known issues with firmware v4.7 fdr 35 6.14.4. Traffic counts shown on ports without link (BZ#: 4285) Description: Ports with no connection may show traffic count values when show statistics is used. Example: trunk port 2 may be disconnected but showing the same traffic count values as on trunk port 1. The same is true for user ports. Example: user port 3 may be disconnected but showing the same traffic count values as on the port which was set as the preferred port, port 4. Suggested Work-Around: None.
Known issues with firmware v4.7 fdr 35 6.14.5. When local user port loopback is ON, trunk port MAC counters behavior is different. (BZ#: 4384) Description: Trunk port counter behavior is slightly different between the AH products when the local user port loopback is ON. The difference is described in the following paragraphs. In the case of EM316EFRMAHSH modules, the trunk port MAC counters only reflect the management packets and the user traffic is reflected only on the user ports. fiberdriver(slot/1.
Known issues with firmware v4.7 fdr 35 6.14.6. "no shutdown" does not seem to work on inactive-CO (BZ#: 4273) Description: On an inactive-CO, shutdown disables the user port and show confirms the same. But consequent no shutdown does not seem to re-enable the user port for the same inactive-CO. In other words, it can not be confirmed by using show. Suggested Work-Around: The inactive-CO (in a dual-home setup) user port transmitter is always disabled regardless of its desired state.
Known issues with firmware v4.7 fdr 35 6.14.8. Notes about a CPE module in the same chassis with LNXNM (BZ#: 4295) Description: CPE module in the same chassis as the LNXNM is supported for identification purposes only. However, a CPE module is expected to be connected to a CO module and the management to happen through the CO and LNXNM management interface. show at the slot-context is expected to display enough information for identification purpose.
Known issues with firmware v4.7 fdr 35 6.15. EM316EFE1RM, EM316EFT1RM, EM316EFE1RJRM, EM316EFE1MUXRJ, EM316EFE1MUX4, EFT1MUX4 issues 6.15.1. "shutdown" on RJ45 user port does not drop link (BZ#: 4348) Description: On most products shutdown is intended to disable the port transmitter(Tx). But in this product, it stops the data traffic but the Tx is not disabled, thus the subtending link partner does not lose link. In addition, the LED indication on the RJ45 port shows linked status.
Known issues with firmware v4.7 fdr 35 6.15.3. Notes about a CPE module in the same chassis with LNXNM (BZ#: 4295) Description: CPE module in the same chassis as LNXNM is supported for identification purpose only. However, a CPE module is expected to be connected to a CO module and the management to happen through the CO and LNXNM management interface. show at the slot-context is expected to display enough information for identification purpose.
Known issues with firmware v4.7 fdr 35 6.16. EM316E1MUX4RJRM, EM316E1MUX4RM, EM316T1MUX4RM issues 6.16.1. 'off-line' configuration of CPE is not always guaranteed (BZ#: 4290) Description: Normally, you can configure a board's parameters even if it is not installed in a chassis slot. In that case the configured parameters are retained in a run time database on the LNXNM, and applied to the line card, when the specified line card is inserted into the chassis.
Known issues with firmware v4.7 fdr 35 6.16.3. "Hardware Revision: 0" for CPE module (BZ#: 4181,4694) Description: The hardware revision of the CPE module shown in the show at slot context is 0 (zero). This information is not retrieved in the current implementation. Suggested Work-Around: None. As long as CO and CPE communication is healthy, one can assume that hardware revision of the CPE module is same as the CO module. Customer Impact: Minimal. Informational only.
Known issues with firmware v4.7 fdr 35 6.17.3. Loopback status is not reflected in port counters (BZ#: 7142) Description: Issue a loopback command on any port. This results in traffic being looped back correctly. However, show statistics displays the counters on the ports as forwarding traffic. Suggested Work-Around: Read counters on the receiving port to observe that traffic is not transmitted from the looped back port. Customer Impact: Minor inconvenience.
Known issues with firmware v4.7 fdr 35 6.17.6. Longer auto-negotiation time and LIN issue (BZ#: 7244) Description: In repeater-mode, with auto-negotiation ON and LIN ON, depending on the link partner equipment used the link could flap. Some of the network equipments could take over 20 seconds to autonegotiate. This type of delay causes confusion with the LIN implementation. Suggested Work-Around: None. Customer Impact: Minimal. Informational only.
Known issues with firmware v4.7 fdr 35 6.17.9. LIN acts on port Tx fiber cut and port disable (BZ#: 8804 ) Description: When Auto negotiation and LIN are enabled, disconnecting the TX link of the SFP causes that SFP RX link to go down as well. This in turn causes the other SFP port to shut down in repeater mode or RJ45 port in converter mode. Suggested Work-Around: It is recommended that user disable Auto negotiation when using the LIN feature.
Known issues with firmware v4.7 fdr 35 6.19. EM316T1E1-XY issues 6.19.1. Issues when CPE is looping back (BZ#: 6872,6948,7684) Description: When loopback is used on the CPE board (generally used for testing links), all configuration commands are ignored. There is no feedback about it in the CLI. When "restart cold" is used on LNXNM while loopback is used on CPE, normal behavior is that loopback is turned off, as "restart cold" is equivalent to a power-cycle.
Known issues with firmware v4.7 fdr 35 6.19.3. CO+CPE wrong connection and wrong DIP switch setting issues. (BZ#: 7821,7871) Description: If the Tx of CO or the Rx or the CPE is cut, status and the configuration of the CPE boards are not reliable. Either in the single CPE setup or the dual CPE setup, the fiber port connection should follow the recommendations in the user guide. If the fiber port 2 and 3 are cross-connected results are unpredictable.
Known issues with firmware v4.7 fdr 35 6.20.2. Behavior details when BPV injected (BZ#: 8343) Description: When BPV (bi-polar violation) or CV (code violation) is injected into the module you will not see link status change and so no traps. Suggested Work-Around: None. Customer Impact: Minor inconvenience. Corrective Action: This issue will be addressed in future software upgrades. 6.20.3.
Known issues with firmware v4.7 fdr 35 6.20.6. Local loopback and PWR LED behavior issue (BZ#: 8294) Description: When local loopback command is issued, both CO and CPE board PWR LEDs do not blink simultaneously. PWR LED blinks only on the module where local loopback is issued. Suggested Work-Around: None. Customer Impact: Minor inconvenience. Corrective Action: This issue will be addressed in future firmware upgrades. 6.20.7.
Known issues with firmware v4.7 fdr 35 6.20.9. CPE local loopback issues. (BZ#: 8362) Description: CPE user port (local) loopback retained when CPE is power cycled. CPE user port (local) loopback is retained when there is disconnect/reconnect of trunk port fibers. However CPE user port (local) loopback is cleared when "shutdown/no shutdown" command sequence is used on the CO trunk port. CPE user port (local) loopback is cleared when "restart warm" is used on LNXNM.
Known issues with firmware v4.7 fdr 35 6.21.3. LNXNM-OT may restart with an assertion. (BZ#: 7852) Description: This issue is hard to reproduce. However the typical symptom is that you will notice LNXNM-OT restart with an assertion as shown below. pollerd: ll-driver.c:235: eep_read: Assertion `elem->con_devid != elem->main_devid' failed.
Known issues with firmware v4.7 fdr 35 6.21.6. OAM stats not available for CPE trunk 2 (BZ#: 8423) Description: OAM statistics are not available for port P2 on the CPE module. This does not affect it ability to function as the active trunk. Suggested Work-Around: None. Customer Impact: Minimal. Informational only. Corrective Action: This issue will be addressed in future software upgrades. 6.22. EM316-10G8SW-XY issues 6.22.1. Switch mode aging timer issue.
Known issues with firmware v4.7 fdr 35 6.22.4. Internal loopback and port link issue (BZ#: 7980) Description: Enabling internal loopback on an access port with no SFP inserted will result in a "link up" msg for that port. Suggested Work-Around: None. Customer Impact: Minimal: informational only. Corrective Action: This issue will be addressed in future software upgrades. 6.22.5.
Known issues with firmware v4.7 fdr 35 6.22.8. SFP-FDSGMII-M autonegotiation (BZ#: 8447) Description: LNXNM accepts commands to enable/disable auto-negotiation on a port with a SFP-FDSGMII-M transceiver installed, but always reports that auto-negotiation is off. Since the SFPFDSGMII-M transceiver does not provide auto-negotiation, this report is accurate. Suggested Work-Around: None. Customer Impact: Minimal; potential configuration confusion. Corrective Action: None; information only. 6.22.9.
Known issues with firmware v4.7 fdr 35 6.22.11. Multi-CO mode: LIN does not react for CPE trunk Tx cut (BZ#: 8439) Description: When just the Tx fiber from the CPE trunk port is cut, LIN does not react on the CPE by disabling the user port. This is because the 10G8SW-XY SFP port does not operate in uni-directional mode so its fault indication is not sent. Link remains up on the CPE trunk Rx fiber so it thinks the communication path is still operational.
Known issues with firmware v4.7 fdr 35 6.22.14. Multi-CO mode: OAM transparency (BZ#: 8470) Description: The OAM transparency feature was originally designed for EUSM CO/CPE pairs, to facilitate the exchange of IEEE standard OAMPDU frames between their connected devices. This feature is configured by dip-switch, and both cards must have the same setting, either OFF or ON. Conflicting settings prevent normal management. This feature is also recognized by a 10G8SW-XY running in Multi-CO mode.
Known issues with firmware v4.7 fdr 35 6.22.17. Multi-CO mode: Incorrect 'Auto Neg Wait' and 'MDI Pinout' shown for CPE copper user port after reset of NM or CO (BZ#: 8552) Description: When the NM is cold reset or only the EM316-10G8SW-XY Multi-CO is reset, the reported 'Auto Neg Wait' for remote EUSM (CPE) copper user ports will be the default value (4) instead of the configured value. Also, 'MDI Pinout' may be reported as (null). Desired configuration values can be checked with the show config command.
Known issues with firmware v4.7 fdr 35 6.22.20. Slot temperature display is sometimes incorrect (BZ#: 9269) Description: The module temperature is sometimes displayed incorrectly because of slow polling. Suggested Work-Around: None. Customer Impact: Moderate. Corrective Action: This issue will be addressed in future software upgrades. 6.23. EM316GEMX4R issues 6.23.1.
Known issues with firmware v4.7 fdr 35 6.23.3. Counters are not displayed in unmanaged mode (BZ#: 8567) Description: NM does not issue any write commands in unmanaged mode. Thus, user could never reset counters to 0. When the card comes up there may be counter information that is not relevant. It would be confusing to display counters that are not accurate, hence no counters are displayed in unmanaged mode. Suggested Work-Around: If need be, read the counters on the receiving/sending device.
Known issues with firmware v4.7 fdr 35 6.24. EM316DMR10G-3R issues 6.24.1. User can set the active port of a redundant pair as a sniffer (BZ#: 8706) Description: User will not be disallowed from designating the active port of a redundant pair as a sniffer port. However, there will be a strong warning against it and select-link command will not be allowed since redundancy gets disabled when a port is a sniffer. marg(slot/1.3)# show Slot 1.3 Redundancy: enabled Port Enable Link ===== ====== ==== 1.3.
Known issues with firmware v4.7 fdr 35 6.24.2. Use FPGA 0x000c for 11G+ rate protocols (BZ#: 9348) Description: User should upgrade the DMR10G firmware to 0x000c in order to avoid extra prbs traps while ports are set to 11G and higher rates. Suggested Work-Around: Upgrade to FPGA 0x000c. Customer Impact: Minor. Corrective Action: This issue will be addressed in future software upgrades. 6.24.3.
Known issues with firmware v4.7 fdr 35 6.25.2. Issues when CPE is looping back (BZ#: 9232) Description: When loopback is used on the CPE board (generally used for testing links), all configuration commands are ignored. There is no feedback about it in the CLI. While in loopback, CPE transfers the data stream intact as received from CO, which means "Last Gasp" trap will not be sent, when CPE loses power.
Known issues with firmware v4.7 fdr 35 6.27. MegaVision issues 6.27.1. 'Upload timed out' while using 'device backup utility' (BZ#: 4382) Description: The restoration of NM configuration using the 'device backup utility' from MegaVision may fail with the following error message. Upload timed out. Do not reboot NM. Restore communication and try again. Suggested Work-Around: Use CLI to remove unnecessary files from the LNXNM file-systems flash area.
Chapter 7. New Features. 7.1. Overview This chapter lists a few noteworthy new features implemented in v4.7 fdr 35 version of the EM316LNXNM-OT firmware. For complete list of features please refer to LNXNM.PDF (v4.7 fdr 35). 7.2. MegaVisionJ package can be upgraded independently. show version does not include MegaVisionJ information anymore. Use show packages to see the version information for MegaVisionJ installed on the system. MegaVisionJ included with v4.7 fdr 35 is "v2.41d5".
New Features. log remote-server host ? <1-5> - Entry to modify A.B.C.D - IP address of remote syslog server <0-65535> - UDP port of remote syslog server, optional (default 514) (emerg|alert|crit|error|warning|notice|info|debug) is the log level, optional (default warning) fiberdriver(config)# log remote-server host 1 192.168.12.126 syslo[189]|kern| warn|May 11 09:23:37 added syslog server 192.168.12.126:514 @ warning level fiberdriver(config)# log remote-server host 2 192.168.14.
New Features. fiberdriver(port/1.1.1)# sgmii? sgmii - Set SGMII-PHY mode fiberdriver(port/1.1.1)# sgmii fiberdriver(port/1.1.1)# show plugin Vendor Name: MRV COMM,INC. Vendor Part Number: SFP-FDSGMII-LR Vendor Revision: 10 Vendor Date Code: 091213 Vendor Serial Number: 9DD2000219 Serial Encoding: 4B5B Base Checksum Match: yes Sgmii Phy: yes Ethernet: 100BASE-LX/LX10 Transmission media supported: 9 micron SMF: >0 meters. fiberdriver(port/1.1.1)# no sgmii fiberdriver(port/1.1.
New Features. fiberdriver(slot/1.10)# show hw-config Loc Name State Meaning Description ==== ==== ===== ========= =================================== 1.10 MODE off Off SW1_1: Mode 1 1.10 MODE off Off SW1_2: Mode 2 1.10 FE on 100Base-X SW1_3: FO Speed 1.10 LIN off Disable SW1_4: LIN 1.10 MDIX off MDI SW1_5: Port 4 MDI/MDI-X 1.10 SPD on On SW1_6: Speed 1 1.10 SPD off Off SW1_7: Speed 2 1.10 HDX off Full SW1_8: Duplex 1.10 T-AN on AutoNeg SW2_1: Trunk ports Auto-Negotiation 1.
