MRV Chatsworth Product DivisionEM316LNXNM-OTv4.7 fdr 35Release NotesPublished 2012/03/21 at09:48:57 r20134- for-v4.7 fdr 35
xList of Tables4.1. Currently supported modules(CA/GA) ... 44.2. Currently
Known issues withfirmware v4.7 fdr 35896.24.2. Use FPGA 0x000c for 11G+ rate protocols(BZ#: 9348)Description: User should upgrade the DMR10G firmware
Known issues withfirmware v4.7 fdr 35906.25.2. Issues when CPE is looping back(BZ#: 9232)Description: When loopback is used on the CPE board
Known issues withfirmware v4.7 fdr 35916.27. MegaVision issues6.27.1. 'Upload timed out' while using 'device backuputility'(BZ#: 4
92Chapter 7. New Features.7.1. OverviewThis chapter lists a few noteworthy new features implemented in v4.7 fdr 35 version of theEM316L
New Features.93log remote-server host ? <1-5> - Entry to modify A.B.C.D - IP address of remote syslog server <0-65535> - UDP port of re
New Features.94fiberdriver(port/1.1.1)# sgmii? sgmii - Set SGMII-PHY modefiberdriver(port/1.1.1)# sgmiifiberdriver(port/1.1.1)# show plugin
New Features.95fiberdriver(slot/1.10)# show hw-config Loc Name State Meaning Description ==== ==== ===== =========
xiConfidentialThe information contained herein is the property of MRV Communications and is strictly confidential.Except as expressly authorized in wr
1Chapter 1. Introduction1.1. OverviewThis document lists the changes made from the previous and formally released EM316LNXNM-OTnetwork managem
2Chapter 2. IMPORTANT: Read thefollowing.2.1. OverviewThis chapter lists a few very important steps that need to be considered before attempting to up
3Chapter 3. CLI Syntax changesImportantPlease read this chapter completely before upgrading to this software version.3.1. CLI syntax changes since v4.
4Chapter 4. List of modules supported4.1. Currently supported modulesThe following currently supported modules underwent full validation testing and w
List of modules supported5Module name Line-card version(if applicable)EM316ERM/xxEM316EFRM/xxEM316FRM/xxEM316O3C/xxEM316DS3/xxEM316E3/xxEM316E1/xxEM31
List of modules supported6Module name Line-card version(if applicable)EM316E/xxEM316OSW128 Firmware 0x5ANC316-MDX46MA002NC316-MDX46MA0034.2. Newly add
7Chapter 5. Issues fixed with firmwarev4.7 fdr 355.1. OverviewThe following is a list of issues fixed.For more information please contact support@mrv.
Issues fixed with firmware v4.7 fdr 3585.2.3. LNXNM cards lockup occasionally(BZ#: 9084)Description: LNXNM modules locked up and stopped management co
Copyright © 2007,2008,2009,2010,2011,2012 MRVCommunications, Inc.All rights reserved.No part of the contents of this document may be reproduced in
Issues fixed with firmware v4.7 fdr 3595.4. EM316EUSM (Stage2) issues5.4.1. firmware download issues(BZ#: 6089)Description: Multiple 'revisions
Issues fixed with firmware v4.7 fdr 35105.4.4. EM316EUSM: 'traffic-gen-load' command changes'Frame Size Type'.(BZ#: 8575)Descripti
Issues fixed with firmware v4.7 fdr 35115.6.2. Loopback timer does not work on ports in remoteCPE modules(BZ#: 5862)Description: The loopback-timeout
Issues fixed with firmware v4.7 fdr 35125.8.2. Loopback timer does not work on ports in remoteCPE modules(BZ#: 5862)Description: The loopback-timeout
Issues fixed with firmware v4.7 fdr 35135.11. EM316DMR3G-3R issues5.11.1. Mapping changes might not be saved after an NMrestart cold(BZ#: 8780,8777)De
Issues fixed with firmware v4.7 fdr 35145.12.3. LIN configuration that is issued while CPE isdisconnected is not sent to the CPE after reconnection(BZ
Issues fixed with firmware v4.7 fdr 35155.13.3. Dual Home: No CO switch-over whendisconnecting active CO user port(BZ#: 4891)Description: In a dual-ho
Issues fixed with firmware v4.7 fdr 35165.15. EM316E1MUX4RJRM, EM316E1MUX4RM,EM316T1MUX4RM issues5.15.1. In Unmanaged-Remote loopback, LEDs for userpo
Issues fixed with firmware v4.7 fdr 35175.17. EM316-10G-XY issues5.17.1. Module reboots when redundant power supply ispowercycled repeatedly(BZ#: 8295
Issues fixed with firmware v4.7 fdr 35185.18.2. Repeater mode RJ48 port loopback leaks through(BZ#: 7266)Description: In repeater mode selecting loopb
Issues fixed with firmware v4.7 fdr 35195.19.2. Fast Ethernet performance numbers(BZ#: 8225)Description: The current implementation (FPGA rev 0x8B) su
Issues fixed with firmware v4.7 fdr 35205.21. EM316DMR10G-3R issues5.21.1. Pattern check duration is not restored afterrestart warm(BZ#: 8986)Descript
21Chapter 6. Known issues with firmwarev4.7 fdr 356.1. OverviewPresented here is a list of known issues and limitations found for the most recent soft
Known issues withfirmware v4.7 fdr 35226.2.3. Behavior of un-supported modules(BZ#: 4358)Description: Modules that are not yet supported by the EM316L
Known issues withfirmware v4.7 fdr 35236.2.6. Broadcast IP address is automatically set(BZ#: 914)Description: The EM316LNXNM-OT automatically sets the
Known issues withfirmware v4.7 fdr 35246.2.9. Startup-config can be overwritten by ">" and ">>"for SUPER level users(BZ#:
Known issues withfirmware v4.7 fdr 35256.2.10. SFP port on LNXNM shows Tx octets when thereis nothing plugged in(BZ#: 5620)Description: SFP port 2
Known issues withfirmware v4.7 fdr 35266.2.11. Host IPs with all zeroes or all ones are notaccepted(BZ#: 5688)Description: When setting up an IP on th
Known issues withfirmware v4.7 fdr 35276.2.13. NM with VLAN ID 0 (disabled) will not forwardVLAN packets(BZ#: 7461)Description: An NM that has VLAN ta
Known issues withfirmware v4.7 fdr 35286.2.17. LNXNM-OT: RmonDeleteRow: . . .can't fetchvariable (no such).(BZ#: 8625)Description: On module remo
ivTable of ContentsConfidential ...
Known issues withfirmware v4.7 fdr 35296.2.20. Image size is too big, unable to upgrade.(BZ#: 9162,9365)Description: User was unable to upgrade from v
Known issues withfirmware v4.7 fdr 35306.3.3. freeSSHd telnet server problem(BZ#: 3756)Description: The telnet client on the NM does not work with the
Known issues withfirmware v4.7 fdr 35316.3.5. Fan Failure/Restored repeated traps/messages(BZ#: 3832)Description: When the FAN is forcefully stopped (
Known issues withfirmware v4.7 fdr 35326.3.6. A note about command syntax in the scripts(BZ#: 4633)Description: Limited amount of syntax checking
Known issues withfirmware v4.7 fdr 35336.3.7. The interactive login banner doesn't accept arrowkeys(BZ#: 4016,5150)Description: The arrow keys ar
Known issues withfirmware v4.7 fdr 35346.3.10. Module hot swap shows error condition(BZ#: 8572)Description: After removing a module, the following mea
Known issues withfirmware v4.7 fdr 35356.4.3. SNMP GET on icmpOutEchos.0 is always zero(BZ#: 4614)Description: When ping is used from LNXNM CLI, the c
Known issues withfirmware v4.7 fdr 35366.5. EM316DMR3G-3R issues6.5.1. Unexpected traps from Beacon-LIN(BZ#: 4346)The DMR3G-3R board is not designed t
Known issues withfirmware v4.7 fdr 35376.5.2. Administrative and Operational Port Map(BZ#: 4357)Description: Any changes to the port map while operati
Known issues withfirmware v4.7 fdr 35386.5.5. No "User-Defined" protocol available(BZ#: 716)Description: There is no "User-Defined"
MRV Chatsworth Product Divisionv5.12.2. Loopback mac at 10 Mbps does not return frames ... 135.12.3. LIN configu
Known issues withfirmware v4.7 fdr 35396.5.8. Standby port disable/enable causes active porttoggle(BZ#: 9105)Description: Two redundant mode DMR3G mod
Known issues withfirmware v4.7 fdr 35406.7. EM316GEMX2R issues6.7.1. Issues on 1:1 redundant-tx-mode(BZ#: 2675,4098,4070)Description: It is important
Known issues withfirmware v4.7 fdr 35416.7.2. Three DIP-switch status improperly reported inUN-managed mode(BZ#: 4180)Description: LIN functionality i
Known issues withfirmware v4.7 fdr 35426.7.5. Tester ports don't get link after GEMX2R reboot(BZ#: 8851)Description: Connect GEMX2R ports directl
Known issues withfirmware v4.7 fdr 35436.8. EM316MRMX2R issues6.8.1. Issues on 1:1 redundant-tx-mode(BZ#: 2675,4098,4070)Description: It is important
Known issues withfirmware v4.7 fdr 35446.8.2. Three DIP-switch status improperly reported inUN-managed mode(BZ#: 4180)Description: LIN functionality i
Known issues withfirmware v4.7 fdr 35456.10. EM316FRM,EM316ERM,EM316EFRMissues6.10.1. IPLESS port shutdown status issue(BZ#: 4578)Description: When a
Known issues withfirmware v4.7 fdr 35466.11.2. Incorrect copper user port counter value(s) afterlink down event(BZ#: 6195)Description: A link down eve
Known issues withfirmware v4.7 fdr 35476.11.3. New bandwidth provisioning commands(BZ#: 5932)Description: There are two new slot-level commands f
Known issues withfirmware v4.7 fdr 35486.11.6. Warning message "loopback restriction violation"displayed : when and why ?(BZ#: 5509,5749)Des
MRV Chatsworth Product Divisionvi6.2.19. SSH session denied due to low available memory. ... 286.2.20. Image siz
Known issues withfirmware v4.7 fdr 35496.11.7. A few no loopback issues(BZ#: 5971,5975,6000)Description: Issuing no loopback on certain ports caus
Known issues withfirmware v4.7 fdr 35506.11.9. Error message "traffic-gen action is invalid"displayed : when and why ?(BZ#: 5613)Description
Known issues withfirmware v4.7 fdr 35516.11.10. After power cycle of CPE, 'Traffic Generation'status incorrect(BZ#: 5926)Description: If tra
Known issues withfirmware v4.7 fdr 35526.11.12. Dual Home: Unexpected CO switchover on CPEuser reconnect(BZ#: 5457)Description: When LIN is enabled, l
Known issues withfirmware v4.7 fdr 35536.11.13. Dual Home: Disabling auto-negotiation on COuser port causes switchover(BZ#: 5547)Description: In a dua
Known issues withfirmware v4.7 fdr 35546.11.16. Some tagged user frames may be stripped oftheir VLAN tag during PM in FE mode(BZ#: 8156)Description: T
Known issues withfirmware v4.7 fdr 35556.12. EM316EUSM (Stage1) issues6.12.1. Notes about a CPE module in the same chassiswith EM316LNXNM-OT(BZ#: 4295
Known issues withfirmware v4.7 fdr 35566.13. EM316GRMAHSH issues6.13.1. Changing "auto-negotiation" appears to have noeffect on non-preferre
Known issues withfirmware v4.7 fdr 35576.13.4. Dual Home: setup precautions(BZ#: 4208,4338)Description: When using the dual home setup, please follow
Known issues withfirmware v4.7 fdr 35586.13.5. Connected for Dual-Home, but configured asSingle-Home may cause inconsistent behavior.(BZ#: 4341)Descri
MRV Chatsworth Product Divisionvii6.11.7. A few no loopback issues ... 496.11.8. Inac
Known issues withfirmware v4.7 fdr 35596.13.7. When local user port loopback is ON, trunk portMAC counters behavior is different.(BZ#: 4384)Descriptio
Known issues withfirmware v4.7 fdr 35606.13.9. "no shutdown" does not seem to work oninactive-CO(BZ#: 4273)Description: On an inactive-CO, s
Known issues withfirmware v4.7 fdr 35616.14. EM316EFRMAHSH issues6.14.1. Occasionally "auto-negotiation" on CPE user portswitches the active
Known issues withfirmware v4.7 fdr 35626.14.3. Dual Home: setup precautions(BZ#: 4208,4338)Description: When using the dual home setup, please follow
Known issues withfirmware v4.7 fdr 35636.14.4. Traffic counts shown on ports without link(BZ#: 4285)Description: Ports with no connection may show tra
Known issues withfirmware v4.7 fdr 35646.14.5. When local user port loopback is ON, trunk portMAC counters behavior is different.(BZ#: 4384)Descriptio
Known issues withfirmware v4.7 fdr 35656.14.6. "no shutdown" does not seem to work oninactive-CO(BZ#: 4273)Description: On an inactive-CO, s
Known issues withfirmware v4.7 fdr 35666.14.8. Notes about a CPE module in the same chassiswith LNXNM(BZ#: 4295)Description: CPE module in the same ch
Known issues withfirmware v4.7 fdr 35676.15. EM316EFE1RM, EM316EFT1RM,EM316EFE1RJRM, EM316EFE1MUXRJ,EM316EFE1MUX4, EFT1MUX4 issues6.15.1. "shutdo
Known issues withfirmware v4.7 fdr 35686.15.3. Notes about a CPE module in the same chassiswith LNXNM(BZ#: 4295)Description: CPE module in the same ch
MRV Chatsworth Product Divisionviii6.15.5. Dribble error packets are not recorded as error packets ... 686.16. EM316E1
Known issues withfirmware v4.7 fdr 35696.16. EM316E1MUX4RJRM, EM316E1MUX4RM,EM316T1MUX4RM issues6.16.1. 'off-line' configuration of CPE is n
Known issues withfirmware v4.7 fdr 35706.16.3. "Hardware Revision: 0" for CPE module(BZ#: 4181,4694)Description: The hardware revision of th
Known issues withfirmware v4.7 fdr 35716.17.3. Loopback status is not reflected in port counters(BZ#: 7142)Description: Issue a loopback command on an
Known issues withfirmware v4.7 fdr 35726.17.6. Longer auto-negotiation time and LIN issue(BZ#: 7244)Description: In repeater-mode, with auto-negotiati
Known issues withfirmware v4.7 fdr 35736.17.9. LIN acts on port Tx fiber cut and port disable(BZ#: 8804 )Description: When Auto negotiation and LIN ar
Known issues withfirmware v4.7 fdr 35746.19. EM316T1E1-XY issues6.19.1. Issues when CPE is looping back(BZ#: 6872,6948,7684)Description: When loopba
Known issues withfirmware v4.7 fdr 35756.19.3. CO+CPE wrong connection and wrong DIP switchsetting issues.(BZ#: 7821,7871)Description: If the Tx of CO
Known issues withfirmware v4.7 fdr 35766.20.2. Behavior details when BPV injected(BZ#: 8343)Description: When BPV (bi-polar violation) or CV (code vio
Known issues withfirmware v4.7 fdr 35776.20.6. Local loopback and PWR LED behavior issue(BZ#: 8294)Description: When local loopback command is issued,
Known issues withfirmware v4.7 fdr 35786.20.9. CPE local loopback issues.(BZ#: 8362)Description: CPE user port (local) loopback retained when CPE is p
MRV Chatsworth Product Divisionix6.22.15. Multi-CO mode: Rare miss-reporting of lost frames ... 846.22.16. Multi-CO
Known issues withfirmware v4.7 fdr 35796.21.3. LNXNM-OT may restart with an assertion.(BZ#: 7852)Description: This issue is hard to reproduce. However
Known issues withfirmware v4.7 fdr 35806.21.6. OAM stats not available for CPE trunk 2(BZ#: 8423)Description: OAM statistics are not available for por
Known issues withfirmware v4.7 fdr 35816.22.4. Internal loopback and port link issue(BZ#: 7980)Description: Enabling internal loopback on an access po
Known issues withfirmware v4.7 fdr 35826.22.8. SFP-FDSGMII-M autonegotiation(BZ#: 8447)Description: LNXNM accepts commands to enable/disable aut
Known issues withfirmware v4.7 fdr 35836.22.11. Multi-CO mode: LIN does not react for CPE trunkTx cut(BZ#: 8439)Description: When just the Tx fiber fr
Known issues withfirmware v4.7 fdr 35846.22.14. Multi-CO mode: OAM transparency(BZ#: 8470)Description: The OAM transparency feature was originally des
Known issues withfirmware v4.7 fdr 35856.22.17. Multi-CO mode: Incorrect 'Auto Neg Wait' and'MDI Pinout' shown for CPE copper user
Known issues withfirmware v4.7 fdr 35866.22.20. Slot temperature display is sometimes incorrect(BZ#: 9269)Description: The module temperature is somet
Known issues withfirmware v4.7 fdr 35876.23.3. Counters are not displayed in unmanaged mode(BZ#: 8567)Description: NM does not issue any write command
Known issues withfirmware v4.7 fdr 35886.24. EM316DMR10G-3R issues6.24.1. User can set the active port of a redundant pairas a sniffer(BZ#: 8706)Descr
Kommentare zu diesen Handbüchern