- Juniper Networks full set of alarms and statistics ... to all 96 wavelengths in the DWDM 50 GHz...

Copyright © 2016 Juniper Networks, Inc. ALL RIGHTS RESERVED.

BTI7800

Release 2.1.1

Release Notes

Part No.: BT8A78PD0021 Rev. 02

August 2016

BTI7800 Release 2.1.1 ii



This product is the property of Juniper Networks, Inc. and its licensors, and is protected by copyright. Any reproduction in whole or in part is strictly prohibited. Juniper, Juniper Networks, BTI, BTI SYSTEMS, packetVX, proNX, and The Network You Need are trademarks or registered trademarks of Juniper Networks, Inc. and/or its subsidiaries in the U.S. and/or other countries.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

Copyright 2003-2016 BTI Systems, Inc. All rights reserved.

BTI7800 Release 2.1.1 iii


Obtaining technical support

Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or Partner Support Service support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.

You can open a case with JTAC on the Web or by telephone. • Use the Case Management tool in the CSC at http://www.juniper.net/cm/.

• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico). For international or direct-dial options in countries without toll-free numbers, see http://www.juniper.net/support/requesting-support.html.

End User License Agreement

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)

Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License

Agreement (EULA) posted at http://www.juniper.net/cm/. By downloading, installing or using such software, you agree to

the terms and conditions of that EULA.

Document Identification

Juniper Networks BTI7800 Release 2.1.1 Release Notes Rev. 02

Abstract

This document provides information related to the current release.

Publication History

Revision Date Changes

01 July 2016 Baseline

02 August 2016 Added 41921

http://www.juniper.net/cm/

http://www.juniper.net/support/requesting-support.html

http://www.juniper.net/cm/

BTI7800 Release 2.1.1 iv


BTI7800 Release 2.1.1 v


Contents

1. Introduction .................................................................................. 1

1.1 Purpose ....................................................................................................... 1

1.2 New Features .............................................................................................. 1

1.3 Upgrade Information .................................................................................. 2

1.4 Restrictions ................................................................................................ 3

1.5 proNX Service Manager ............................................................................. 3

2 Resolved Issues .......................................................................... 4

3 Known Issues............................................................................... 8

4 Known Limitations .................................................................... 15

5 Related Documentation ............................................................ 17

BTI7800 Release 2.1.1 vi


BTI7800 Release 2.1.1 1


1. Introduction

1.1 Purpose

This document lists the BTI7800 software features, known software issues, and fixed

software issues in release 2.1.1.

1.2 New Features

NOTE: Juniper Networks has introduced a new filler module (BT8A78FLR7). This filler

module must be used to cover empty slots in a BTI7814 chassis running release 2.1.0

software or higher. See the following TIB for more information: BTI-TIB002-2016.

BTI7800 Series Release 2.1.1 provides support for the following:

Additional ROADM features:

o support for ROADM ring topologies

o support for split-ROADM node configurations, where ROADM modules in

a ROADM node reside on separate network elements

o support for add/drop (alien) wavelengths to external endpoints

ILA (BT8A78AMPL) module

o EDFA inline amplifier, composite DWDM signal amplification

o for deployment in transit sites with span losses of up to 33 dB (with the

PRE module installed)

o initial support for 96 channels (50 GHz grid)

o full set of alarms and statistics

Inband management of the BTI7800 node

o initial support for carrying management traffic inband in an optical

network

o gateway function allows management traffic to be routed between the

inband and out-of-band management networks

o static routes only

BTI7800 Series Release 2.1.0 provides support for the following:

BTI7801 (BT8A78CH1) one-slot chassis:

o 1RU (H) x 17.3 in (W) x 24.2 in (D)

o can be installed in 19-in and 23-in data center cabinets, compliant with

GR-3160 for data centers

o same management as the BTI7814 and BTI7802, same CMM

management module

o supports existing BTI7800 service modules (with initial release

supporting UFM3, UFM4, WPS4)

o powered by existing BTI7802 AC and DC PEMs

o new FAN5 front cooling module and Ethernet and Serial Link (ESL)

module



NOTE: The BTI7801 requires a CMM running release 2.1.0 or higher. See

section 1.3 Upgrade Information below for additional upgrade information for

the BTI7801.

ROADM2 (BT8A78RDM2) module:

o 2-port reconfigurable optical add/drop multiplexer

o for deployment in terminal, add/drop, and transit sites, with span losses

of up to 33 dB (with the PRE module installed)

o initial support for 96 channels (50 GHz grid)

o initial support for linear spans, hardware-ready for ring configurations

o full set of alarms and statistics

o simple point-and-click service activation when managed with the proNX

Service Manager

PRE (BT8A78AMPP) module:

o CFP2 form factor EDFA pluggable preamplifier module

o provides supplementary amplification for the host ROADM module

FMD96 (BT8A78MD03) module:

o passive, rack-mounted 96-channel fixed multiplexer/demultiplexer

o for deployment with ROADM modules to provide local fixed grid access

to all 96 wavelengths in the DWDM 50 GHz grid

Improved internal system communications and robustness:

o The processor on the CMM is automatically rebooted if it is

unresponsive. Traffic is not affected.

o The processor on the UFM is automatically rebooted if it is unresponsive.

Traffic is not affected.

Additional PM statistics for the 100G Coherent MSA XCVR (UFM1, UFM4) and

the 100G Coherent CFP (BP3AMCTL):

o X-polarization signal-to-noise ratio (current, minimum, maximum,

average)

o Y-polarization signal-to-noise ratio (current, minimum, maximum,

average)

Automatic CMM SHMM firmware upgrade if new SHMM firmware is detected

when a software upgrade is performed

Ability to filter management source IP addresses (to restrict which management

stations can gain management access to the system)

IP MIB and RMON MIB

1.3 Upgrade Information

You can upgrade to Release 2.1.1 from Releases 1.5.x, 1.6, 1.7, and 2.1.0.

Contact Juniper Networks Support if you would like to upgrade from a release different

from the above.

If you are installing software on a BTI7801, it is important that you upgrade the CMM

SHMM firmware immediately after commissioning the system. The required firmware is



included in the software package for the release. See section 13.2 Upgrading the CMM

firmware in the BTI7800 Series Software Configuration Guide for information on how to

upgrade the CMM SHMM firmware.

1.4 Restrictions

The BP3AM6DL-xx and BP3AM6TL SFP+ DWDM multi-rate transceivers are only

supported when running 10GE over OTN. These transceivers cannot be used for any

other protocol in this release.

These transceivers are only supported in the following configuration: The following

contains important information regarding upgrading to this release:

1.5 proNX Service Manager

BTI7800 Series Release 2.1.1 is supported by PSM Release 6.3 or later, with the

following exception:

NOTE: ROADM alien wavelength support requires PSM Release 7.0.



2 Resolved Issues

The following issues have been resolved cumulatively in releases 2.1.0 and 2.1.1:

Issue Description

42462 If the PRE module is enabled, and the fiber is disconnected between the

PRE module and the host ROADM or ILA module, the show statistics

current port command for the PRE port incorrectly displays the Optical

power loss in recv. direction as 3.5 dB. The correct value should be 99.0

dB.

42342 When you execute the show tech-support command while modules are

restarting in the system, the command sometimes does not terminate, and

the CLI becomes unresponsive.

42333 On a ROADM or ILA port, if a ‘Loss of Light, Receive’ (loLightRx) condition

exists on the OMS but not on the OSC, the Fault LED on the port will fail to

light up.

42157 DOL fiber connections (fiber-conn) with a fiber-type of teralight are not

supported.

42102 Both the no equipment and the no equipment chassis command (without

any other parameters) fail to check for the existence of associated DOL

components prior to equipment deletion. The equipment is deleted but the

DOL components remain.

41921 Unstable sensor readings cause spurious No Power Available

(powerAbsent), Environment Voltage Above High Threshold

(envVoltHighTh), and Environment Voltage Below Low Threshold

(envVoltLowTh) alarms on AC PEMs.

41575 If an intra-node fiber is accidentally connected to a wrong port, and then

reconnected properly, the system may raise a Far End Identification

Mismatch (feim) alarm. Traffic is not affected (i.e. traffic is re-established

after the fiber is reconnected properly).

41536 The OpenSSH client (version 7.1p2) cannot connect to the BTI7800 CLI.

41526 The CLI allows you to delete the management IP address while

management static routes exist. In these situations, the node becomes

unreachable even after a new management IP address is configured.

41498 When a ROADM module is warm reloaded while an OSC on a connected

module is administratively disabled, the system may raise spurious Optical

Channel Unequipped (ochUeq) alarms for some channels. Traffic is not

affected.



Issue Description

41494 If the CMMs in a chassis switch roles (active becomes standby, standby

becomes active), system database backup, system database restore,

and system upgrade download may fail with a ‘Connection timed out’

error. This problem only occurs on non-gateway nodes configured for

inband management.

41150 After a software rollback, the show interface command sometimes does not

display the payload type for some ODU interfaces.

40978 The Fault LED on ROADM or ILA ports does not always reflect the status

of the port.

40945

40831

38542

38533

38346

38021

Various problems related to the laser settings on the 100G Coherent MSA XCVR (UFM1, UFM4) and the 100G Coherent CFP (BP3AMCTL). The lasers on these transceivers occasionally fail to recover from various down/up situations, such as occasionally failing to recover when a 100G Coherent CFP is unplugged and re-inserted.

40891 An ‘Equipment Management Communications Failure’ (eqptComm) alarm

raised against a CMM may erroneously clear by itself even though the

condition causing the alarm still exists.

40834 One or more BICs sometimes fail to recover after a system reload all cold

command is issued.

40541 The OMS optical power transmitted statistics on the L1 port may show an

aberrant minimum value (e.g. from -75 dBm to -110 dBm) in some bins.

40400 When an Equipment Degrade (eqptDgrd) alarm is raised on a UFM, the

UFM may automatically undergo a cold reboot, resulting in traffic loss.

40395 A memory corruption interferes with proper FPGA boot-up on a UFM. The

FPGA boots up but an Equipment Degrade (eqptDgrd) alarm is raised.

40289 The show inventory transceiver opticalAttributes command displays an

incorrect wavelength setting for the 100GBASE-SR10 (BP3AMASS) CFP

transceiver.

40193 During an upgrade, an Inventory Unknown (invUnknown) alarm is

occasionally raised against a slot that contains a UFM.

40141 If a character is entered on the CMM console port while the CMM is

booting, the boot process stops and the CMM does not come up.

40133 Software upgrade fails due to CMM flash memory corruption. After the

failed upgrade, the CMM with the corrupted flash continually reboots.

40061 When running 10GE over an ODU infrastructure, faults injected at one

10GE may cause an incorrect laser status setting at the other 10GE.

39952 When connected ROADM modules are simultaneously warm reloaded in a

chassis, the system may raise various spurious alarms (e.g. ochUeq) as

the modules come back up. Traffic is not affected.



Issue Description

39890 An incorrectly-formatted show statistics command does not return an

error. The command is accepted but no statistics are displayed.

39888 Setting the fec-type to no-fec does not take effect on the 100G Coherent

MSA XCVR (UFM1, UFM4).

39880 An Equipment Missing (eqptMiss) alarm may be raised against a UFM

even though the UFM is installed in the slot.

39681 When the 100G Coherent CFP (BP3AMCTL) transitions from enabled to

disabled back to enabled state in rapid succession, the Loss of Signal

(LOS) threshold that is in effect may deviate by as much as 10dBm from

the intended setting.

39645 The signal-to-noise ratio reported for the 100G Coherent CFP

(BP3AMCTL) may be incorrect.

39483 When the 100G Coherent MSA XCVR (UFM1, UFM4) recovers from a

fault, the transceiver may change the frequency/wavelength to an adjacent

channel, causing a loss of traffic.

39374 When upgrading the SHMM firmware, the system upgrade firmware

shmm command may not work the first time it is issued.

38785

32790

Traffic continues to flow after the admin-status of a transceiver is set to down.

38675 Changing the UFM type of an installed and in-service UFM should not be

allowed because it will cause a service-affecting Equipment Mismatch

(eqptMism) alarm to be raised.

38582

38568

The PM Errored Seconds (ES) and Severely-Errored Seconds (SES)

counts do not update correctly on ODU interfaces.

38571 The environment temperature threshold values are set incorrectly for the

BTI7814 AC PEMs, resulting in envTempLowTh and envTempHighTh

alarms under normal operating conditions.

38372 Users cannot log in to the CMM after the time zone is changed.

38275 Pulling out and reseating a CMM during a software upgrade may cause the

software upgrade to fail.

38202 The show inventory command does not show Fan modules or Power

Entry Modules (PEMs).

37782 Equipment can be missing from inventory even when the equipment is

present. This problem is resolved by updated CMM SHMM firmware.

37762

37806

The standby CMM incorrectly creates a default route out of its Management

Ethernet interface, leading to connectivity problems with the proNX Service

Manager and other devices.



Issue Description

37216 After performing a software upgrade to this release, or after rebooting or

reseating both CMMs (or single CMM in a single CMM system), the group

privileges for all manually-created local users change to btiuser. The

admin user is not affected as it is automatically created by the system.

RADIUS-authenticated users are also not affected.

36851 A new system reload cpu-reset ufm:identifier command has been

implemented to allow the operator to reset a UFM. This command is not

service affecting.

36703

36699

After a power outage or system brownout, some modules may not recover

properly.

36506 After a software upgrade has been successfully committed, the show

system version command continues to show the previous version of UFM

software up until the UFMs have finished rebooting.

35661 This is an OTN framer firmware enhancement to improve the

manufacturing yield of UFM1, UFM4, and BICs.

35102

36459

All users and management systems (such as the proNX Service Manager)

will be locked out of the network element if the lifetime limit of 1024

unsuccessful login attempts is reached. This limit represents the total

number of unsuccessful login attempts from all sources.

34052 When the idle-timeout is set to 0 (meaning no timeout) for a user CLI session, the session remains up even when network connectivity is lost. This may result in stale sessions which count towards the maximum session limit. If network connectivity is lost when the number of sessions is at the maximum, all subsequent CLI session attempts will be refused.

33826 An ODU LCK alarm may be raised when trying to create a cross-connect between an otu4 (odu3) and a 40ge interface.

33547 After recovering from a power outage lasting more than 24 hours, the system may show an incorrect time.

33174 After a software upgrade, the NE may revert to using older syslog servers.

33020 Under certain situations, the CLI may become unresponsive. The CLI becomes unresponsive when two warm reboot commands are issued in rapid succession on the 96-Channel Amplifier.

32819 When a fan module fails on a BTI7802, the Equipment Failure (eqptFail) alarm is not raised.

32793 The show interface command for an OTU interface may display incorrect lane 0 receive power values when issued immediately after a show statistics command on that same interface.

31609 When a CMM is replaced, the individual IP address for the management interface may not be set for the new CMM.

27597 When an interface is provisioned without the accompanying cross connect, no signal is transmitted on the link.



3 Known Issues

The following are known issues in this release:

Issue Description

42687 To properly delete an optical channel cross-connect, you must also delete the

line port optical channels.

Workaround: The proper procedure to delete optical channel cross-connects

is as follows:

1) Use the no dol och-xcon endpoint1 endpoint2 command to delete

the cross-connect.

2) Use the no dol och:identifier command to delete the line port OCH

endpoint.

42673

42541

When you perform a system software upgrade (system upgrade commit),

the upgrade may fail occasionally (the show system upgrade command

shows a commit-failed status).

Workaround: Perform the software upgrade again.

42600 A single BTI7800 system (either single or multi-chassis) supports the

following limits:

A maximum of 4 ROADM modules. The other slots can be populated

with other BTI7800 modules but cannot be populated with ROADM

or ILA modules.

A maximum of 2 ILA modules. The other slots can be populated with

other BTI7800 modules but cannot be populated with ROADM or ILA

modules.

42585 The l1-interface parameter of an mgt interface cannot be changed once it is

initially set. The CLI accepts the change but the change does not take effect.

Workaround: To change the l1-interface parameter, delete and recreate the

mgt interface with the desired l1-interface value.

42577 The CLI allows you to change or delete an mgt interface while management

static routes associated with that interface exist.

Workaround: Delete associated management static routes before changing

or deleting an mgt interface.

42376 The CMM sometimes raises a Memory High Usage (memHighUsage) alarm.

Workaround: If this occurs, perform a warm reload of the affected CMM.

42344 When you perform a system software upgrade (system upgrade commit),

the system may return an “Error: application communication failure”

message. This message does not affect the upgrade, and can be ignored.



Issue Description

42341 The Fault LED on ROADM or ILA PRE ports does not always reflect the

status of the port.

Workaround: If the PRE port LED is on but no fault exists, or if the PRE port

LED is off but a fault exists, perform a warm reload of the ROADM or ILA

module.

42335 Traffic continues to flow after the admin-status of a MSA transceiver is set to

down.

Workaround: To stop traffic, use the laser-enabled false command on the

interface instead.

42286 If a BTI7800 chassis is powered off and on, the red FAIL LED on the CMM

sometimes remains lit even after the CMM boots up successfully and

becomes active.

Workaround: Verify this problem is occurring by confirming that the CMM is

active (show equipment, show system). To clear the red FAIL LED,

perform a warm reload of the CMM.

42254 When inserting an AC PEM into a BTI7802 chassis, the AC PEM is auto-

provisioned as a DC PEM.

Workaround: After insertion, de-provision the DC PEM and manually

provision the AC PEM.

42039 The show statistics current oms and show statistics current osc

commands return inaccurate average and standard deviation values at the

beginning of a bin interval.

Workaround: To obtain more accurate values, issue the command again

near the end of the bin interval.

41960 Not all IP management addresses may be reported in the IP MIB. The

problem is in the reporting of the IP MIB only. Management connectivity is

not affected.

Workaround: None.

41917 If the system time changes (including changes due to daylight savings

switchover), the show statistics historical command may display an

“Internal error” message in the 1Day bin in which the time change occurs.

The other 1Day bins are correct.

Workaround: None.

41639 If you manually upgrade the SHMM firmware on the CMMs immediately after

upgrading the L2-switch firmware, one of the CMMs may disappear from the

system, and an Equipment Missing (eqptMiss) alarm is raised.

Workaround: Unseat and reseat the affected CMM. To reduce the risk of this

occurring, wait 60 seconds after upgrading the L2-switch firmware before you

upgrade the SHMM firmware.



Issue Description

41615 After the SHMM firmware is automatically upgraded, one of the CMMs may

raise a spurious SHMM Firmware Upgrade Required (firmUpgrdReqd) alarm.

Workaround: Perform a warm reload of the CMM raising the alarm.

41528 The CLI allows historical statistics bins to be deleted, but this capability is not

supported.

Workaround: If the bins are accidentally deleted, use the statistics bin-

settings command to add back the missing bins.

41169 After a cold reload, the ROADM module sometimes does not recover. An

Equipment Fail (eqptFail) alarm is raised but not cleared.

Workaround: Perform a cold reload of the module again.

41089 During an L2-switch firmware upgrade on the CMM, management

connectivity may be lost temporarily.

41027 The show dol fiber-conn command sometimes shows the Far End (FE)

endpoints between a UFM interface and a mux/demux client port as “NOT-

CONNECTED”. This text is misleading and should be ignored. The system is

not supposed to display the Far End endpoints for this type of fiber

connection.

41012 If the network element is being managed inband on the optical network, the

network element still raises a System Controller Management Interface Down

(scmNmiDown) alarm when it detects that no physical management Ethernet

connection exists.

Workaround: If the system is being managed inband on the optical network,

disable the scmNmiDown alarm using the conditions settings

scmNmiDown disable command.

40947 After a successful software upgrade, the output of the show system

upgrade command sometimes does not show the upgrade status of the

service modules.

Workaround: To verify that the modules have been upgraded properly, use

the show equipment command to see that the service modules have come

back up, and then use the show system version command to see the

version of software the service modules are running.

40829 When the active CMM in a dual-CMM chassis is warm reloaded, the output of

the show equipment command shows the reloading CMM as operationally

up before it has actually come back up.

40781 The Far End Configuration Inconsistent (feci) alarm is raised against the osc

component when it should be raised against the port component.

40661 If you specify a metric when you delete a management static route (i.e. no

mgt static ip_address interface interface metric), the CLI accepts

the command but does not delete the static route.

Workaround: When you delete a static route, do not specify the metric (i.e.

no mgt static ip_address interface interface).



Issue Description

40616 A Firmware Upgrade Required (firmUpgrdReqd) alarm may be raised

spuriously against the CMM after a cold reload of the system.

Workaround: Perform a warm reload of the CMM to clear the alarm.

40514 The show dol och-power command can only be run from one CLI session at

a time.

39954

39810

Active conditions against dol components do not appear in the show

conditions output when the component against which the conditions exist is

administratively down.

Workaround: Enable the component to see the outstanding conditions.

39940 When the management IP address is changed and auto-provisioning is

enabled, the ROADM node and connected nodes may automatically create

new fiber connections and raise Far End Identification Mismatch (feim)

alarms. Traffic is not affected.

Workaround: Perform the following procedure to change the management IP

address:

1. Turn auto-provisioning off (system auto-prov false) on the target

node and on all connected nodes. The target node is the node where

you want to change the management IP address. A connected node

is a node that has a fiber connection to the target node.

2. On the target node, change the management IP address.

3. On each connected node, delete any fiber connection whose

endpoint refers to the target node’s previous management IP

address.

4. On each connected node, create a new fiber connection to the target

node. Use the target node’s new management IP address.

5. On both the target node and the connected nodes, re-enable auto-

provisioning if desired (system auto-prov true).

39898 When an OMS or OSC component is disabled and then re-enabled, the

show statistics command may not show the disabled and re-enabled

component in the CLI auto-completion list.

Workaround: Specify the full component name instead of relying on the CLI

auto-completion feature.

39803 When a user issues a system reload command but does not respond

affirmatively to the confirmation dialog, the command returns a prompt and

appears in the log file as if the command was executed when in fact it was

not.

39773 If the PRE module is enabled when there are no optical channels configured

on the line, the system may raise an Automatic Power Reduction (apr) alarm

on the host module PRE port. The alarm should clear when optical channels

are configured.



Issue Description

38891 The CLI allows a user to provision a 100GE interface on the 100G Coherent

MSA and the 100G Coherent CFP transceivers. This should not be allowed

as 100GE is not supported on either of these transceivers.

Workaround: Provision a 100GE interface on another CFP instead.

38825 If a cold reboot occurs on a UFM1 or UFM4 where the interface on the 100G

Coherent MSA transceiver is in facility loopback, the interface on the 100G

Coherent MSA transceiver does not come back up.

Workaround: When this occurs, release the facility loopback, delete and re-

add the OTU4 interface, and re-enable the facility loopback.

38728 A warm reboot of a UFM while provisioning changes are being committed

may cause an Equipment Degrade (eqptDgrd) alarm.

Workaround: If this occurs, perform a cold reboot of the UFM. To prevent

this problem from occurring, wait 30 seconds after the provisioning changes

have been committed and services are back up before performing a warm

reboot of a UFM.

38719 In a multi-chassis system, when one of the inter-chassis cables is

disconnected, the One Multichassis Cable Disconnected

(oneCableDisconnected) alarm may be raised against the incorrect CMM.

38713 CLI auto-completion is not supported when specifying the target ports in the

WPS4 protection wavelength switch command.

Workaround: Specify the target ports manually.

38476 When repeatedly removing a pluggable transceiver and inserting a new one

in its place, a spurious Equipment Mismatch (eqptMism) alarm may be raised

even though the final insertion did not result in a mismatch.

Workaround: If this problem occurs, remove the transceiver and re-insert it

after 30 seconds. To avoid this problem, after removing a transceiver, wait 30

seconds before inserting a new one in.

38084 PRBS signal generation and validation are not supported on OTU4

interfaces.

38051 If a terminal loopback is in effect on a SONET port when the UFM is cold

booted, the terminal loopback may not work properly after the UFM finishes

rebooting.

Workaround: If this occurs, disable and re-enable the terminal loopback.

37947 When a port is placed into terminal loopback, the port does not raise an LOS

alarm to indicate that the port has gone down. Instead, the port raises an

Optical Power Rx Low Threshold (oprLowTh) alarm to indicate that the

receive power on the port is below the low threshold.

Workaround: Use the show statistics current command for the interface to

verify that the optical power received is -99.90dBm, which, in effect, indicates

an LOS.



Issue Description

37441 The BTI7800-EQUIPMENT-MIB contains extra TEXTUAL-CONVENTION

definitions. See Appendix A for details.

Workaround: These definitions are not needed and can be ignored.

37350 A communication timeout can occur between the two CMMs or between the

CMM and a UFM, leading to an Equipment Management Communications

Failure (eqptComm) alarm. Traffic is not affected when this occurs.

NOTE: This release includes a software change that automatically detects

and tries to recover from these situations.

37313 When provisioning equipment, the PEC must be specified but the CLI does

not enforce this. If equipment is provisioned without specifying a PEC, the

system raises an Equipment Mismatch (eqptMism) alarm when the actual

module is inserted.

Workaround: Specify the correct PEC when provisioning a module.

37120 An ODU Open Connection Indication (OCI) alarm is raised when the interface

receives an OCI alarm signal, regardless of whether there is a local cross-

connect provisioned.

Workaround: Use the conditions settings command to set the OCI fault to

not-alarmed, or enable AINS for the interface.

35898 When deleting and adding an OCH cross-connect (och-xcon) where the new

cross-connect contains an endpoint that is in the deleted cross-connect, the

new cross-connect may not be set up properly.

Workaround: After deleting the old cross-connect, commit the changes

before adding the new cross-connect.

35068 The show amp commands may display incorrect power values.

Workaround: Use the show statistics current command for the amplifier

instead.

34529 If an Equipment Degrade (eqptDgrd) alarm is raised against a BIC, no new provisioning can be applied to any other component on the same UFM as long as the alarm is in effect.

Workaround: Disable and re-enable the alarmed BIC to clear the alarm. This is service-affecting.

34338 The show statistics command for UFMs displays an incorrect name for the CPU load average value. The displayed name is always “CPU 1-minute load avg.”, which may be misleading.

34112 The show interface command does not display the wavelength/frequency for fixed wavelength transceivers.

Workaround: Use the show interface table command instead.

33501 De-provisioning a CMM as a system controller and then adding it back within a short time period may cause the CMM to come up in an incorrect state.

Workaround: After de-provisioning a CMM, wait for a period of time before adding it back.



Issue Description

33098 The output of the show running config command cannot be used as input to the CLI. When you take the output of the show running config command

and input that into the CLI, the CLI returns errors for all def- parameters.

Workaround: Delete all parameters beginning with def- before inputting to

the CLI. The def- parameters are read-only default parameters.

32149 When a module is replaced in a chassis, the CLI commands show system version and show system firmware will not display the correct software and firmware information for this module until the operational state of the module changes to UP. Prior to this occurring, the output displays the software and firmware versions of the previous module.

32146 In a system with two CMMs, upgrades should only be performed if both CMMs are operationally up.

31812 De-provisioning a CMM while another CMM is synchronizing with it may lead to an unrecoverable error that requires a reboot from the USB port.

Workaround: Wait until the CMMs are synchronized before de-provisioning a CMM. The CMMs are synchronized when the show system command displays the HA Status as In Sync.

30642 The AINS countdown timer is not preserved over an SCM (System Control Management module) failover.

30630 Provisioning tasks cannot be performed during a system upgrade.

32196

29562

A password must consist of only alphanumeric characters.

28745 The actions of the following commands are not completed until the next system restart:

system database restore remote-url

system upgrade remote-url path



4 Known Limitations

Known limitations are issues that are not planned to be resolved, and that may not be

described in the documentation set for this release. These limitations may be described in a

future release of the documentation set where applicable and necessary. Once a limitation is

described in the documentation set, the limitation may be removed from this list (without

notice).

Issue Description

40749 A Disk Partition Fault (partitionFault) alarm is sometimes raised on a UFM.

Workaround: Perform a warm reboot of the UFM. If the fault does not clear,

contact Juniper Networks Support.

40063 When rolling back software to this release or to an older release, the system

may exhibit intermittent traffic loss and unpredictable behavior such as

raising a spurious Upgrade in Progress (upgr) alarm.

Workaround: Unseat each service module from the backplane before

rolling back software. After the rollback is successful, re-seat the service

modules.

40004 FPSD is disabled during a software upgrade. Therefore, if a condition

causing FPSD to turn off the laser occurs prior to a software upgrade, the

laser will remain off until both of the following occur:

FPSD is re-enabled after the upgrade completes

the condition causing FPSD to turn off the laser has lifted

Workaround: If this is an issue that you want to avoid, disable FPSD on the

interface before performing a software upgrade.

38310 The 40GE QSFP+ interfaces do not support optical power transmit and laser temperature PMs.

37980 During commissioning, the following error sometimes appears: BTI CMM Commissioning Shell exiting as failed to read

fru_info.ini file

Workaround: If this occurs, unseat both CMMs and then re-seat both

CMMs.

37381 When restoring the configuration database (system database restore), the

system may exhibit intermittent traffic loss and unpredictable behavior.

Workaround: Restoring the configuration database is service affecting.

After restoring the configuration database, reboot each service module

individually by issuing the system reload cold command for each service

module. Once all the service modules have started rebooting, issue the

system reload cold command for the management modules.

34580 The no system snmp notify-target command fails to remove the target.

Workaround: When using the no form of this command, do not specify the

port number.



Issue Description

34579 The system snmp notify-target command does not allow entries with the same IP address but with different port numbers.

33963 After the system time has been changed, timestamps on the current statistics bins (e.g. unTimed bin) are not automatically adjusted and will be incorrect.

Workaround: To correct the timestamps of the current statistics bins, perform a warm restart of the traffic modules (for current traffic-related bins) and a warm restart of the active CMM (for current system-related statistics). To prevent this problem from occurring, use reliable NTP servers.

33164 The DCM time delay is not updated on the AMP after the DCM’s PEC is changed.

Workaround: Perform a warm reload of the AMP after changing the DCM.

33163 The DCM time delay is not reset on the AMP after DCM equipment is removed from it.

Workaround: Perform a warm reload of the AMP after de-provisioning the DCM.

32908 When both CMMs (or the single CMM in a single-CMM system) are restarted or re-seated, the show equipment command may temporarily indicate that no equipment is present. This condition occurs for approximately 30 seconds within the first 6 minutes of the CMMs restarting.

Workaround: Use the show inventory command to see the equipment. To verify that there are no issues with the equipment, use the show conditions command and verify that there are no equipment missing alarms.

32806 The 10GE interface does not return a Remote Fault (RF) when it detects a Local Fault (LF).

Workaround: None. However, compliant end devices will return a Remote Fault (RF) so all upstream devices will see the failure.

32624

32597

A cold reboot must not be performed on the Chassis Management Module (CMM) in slots A and B at the same time, or in a single CMM system at any time.

Workaround: In a system with more than one CMM, perform a cold reboot on one of the CMMs, and wait until it becomes operationally up before you cold reboot the second CMM.

32511 In a multi-chassis system, pulling a CMM module from the hub chassis and pulling its attached counterpart from the satellite chassis may cause the other CMM on the satellite chassis to restart.

Workaround: Wait a minimum of 10 seconds after pulling a CMM module before pulling the other.

30507 When using a Spirent or IXIA test set to conduct tests over a 10GE interface with the BTI7800, the BTI7800 may occasionally report a RF.

Workaround: Use the equivalent test sets from JDSU or EXFO.

29705 Cross connects between interfaces on two different SFP+ BICs are not supported.

Workaround: When creating a cross connect between SFP+ interfaces, make sure both interfaces are on the same SFP+ BIC.



5 Related Documentation

For more information on the BTI7800, refer to these publications:

■ BTI7800 Series Command Line Reference Guide

■ BTI7800 Series Hardware Overview and Installation Guide

■ BTI7800 Series Software Configuration Guide

- Juniper Networks full set of alarms and statistics ... to all 96 wavelengths in the DWDM 50 GHz...

Documents

Transcript of - Juniper Networks full set of alarms and statistics ... to all 96 wavelengths in the DWDM 50 GHz...