Professional Documents
Culture Documents
OptiX 155622H (Metro 1000) V300R005C01SPH307 Patch Release Notes PDF
OptiX 155622H (Metro 1000) V300R005C01SPH307 Patch Release Notes PDF
Issue 01
Date 2018-01-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and feat ures are stipulated by the contract made bet ween Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchas e scope or the usage scope. Unless otherwis e specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. E very effort has been made in the
preparation of this document to ensure accuracy of the contents , but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Change History
Contents
3 Known Issues............................................................................................................................... 13
3.1 V300R005C01SPC302 .................................................................................................................................................................13
1 Patch Overview
Result OK
Result OK
Result OK
Result OK
Result OK
2 Resolved Issues
2.1 V300R005C01SPH307
This section describes the known issues in V300R005C01SPH305 that have been resolved in
V300R005C01SPH307.
Description Condition:
More than 100 SNCP protection groups are configured on an NE, and
bit-error-triggered SNCP switching is configured.
Symptom:
When one more SNCP protection group is created, the NE undergoes a
software watchdog reset.
Impact:
The NE undergoes an abnormal warm reset.
Severity Minor
Root Cause When a large number of protection groups are configured on the SNCP
module of the NE, there is a low probability that a data conflict occurs
between configuration tasks and detection tasks during deletion and
addition of bit error detection tasks. As a result, a detection task is
abnormal, and a software watchdog reset occurs on the NE.
Solution None
Impact
New Service Failed to Be Provisioned on the SS49EFS Board of the Metro 1000
V300, and Is Recovered to Normal After a Cold Reset Is Performed on the Board
Trouble DTS: DTS2017122903786
Ticket
Number
Description Condition:
A Metro 1000 V300 NE undergoes a power outage.
Symptom:
A new service cannot be provisioned on the SS49EFS board, but can be
provisioned after a cold reset is performed on the board.
Impact:
The new service cannot be provisioned on the SS49EFS board.
Severity Minor
Root Cause The power outage of the PHY chip on the SS49EFS board causes the logic
module abnormal. As a result, the service on the board cannot be
provisioned.
Solution Modifications have been made to the board software so that the chip
on the board is hard reset upon the board restart from a power outage.
Solution The services will be restored completely until the SS49EFS board hard
Impact reset twice on the hard resetting or pulling out or power off scenes.
2.2 V300R005C01SPH305
This section describes the known issues in V300R005C01SP H303 that have been resolved in
V300R005C01SPH305.
Description Condition:
A loopback is configured at a port of an SS49EFS board.
Symptom:
The loopback is automatically released 5 minutes after it is configured.
Impact:
The automatic loopback release cannot be disabled.
Severity Suggestion
Solution The NE software has been updated so it delivers a command for disabling
automatic loopback release to the SS49EFS board when a loopback is
configured at a port of the SS49EFS board.
Solution After installing the patch, you must reconfigure a loopback on the
Impact SS49EFS board.
2.3 V300R005C01SPH303
This section describes the known issues in V300R005C01SPC302 that have been resolved in
V300R005C01SPH303.
Description Condition:
The NMS and devices run SSL for communication.
The attacker is in an environment ready for initiating attacks and poses
attack methods.
Symptom:
The information exchanged between the NMS and devices is encrypted
using low-security keys. The attacker initiates man-in-the-middle (MITM)
attacks and the information exchanged is decrypted and modified.
Impact:
The attacker, acting as a man-in-the-middle device, can simulate an NMS
Severity Minor
Root Cause During the SSL handshake process, the CCS (key update) message is sent
to the attacker prior to the key negotiation process. As a result, the
attacked user uses an empty key to set up an SSL connection to the
attacker.
Solution Install related patches on the devices.
After the patch installation, set up SSL connections between the NMS and
devices again.
Solution None
Impact
2.4 V300R005C01SPC302
This section describes the known issues in V300R005C01SPC300 that have been resolved in
V300R005C01SPC302.
After 1+1 Linear MSP Is Configured on an NE and Then SNCP Services Are
Configured on the MSP Protection Path Using the Navigator, No Error Message
Is Reported on the NE
Trouble DTS: DTS2013040201055
Ticket
Number
Description After 1+1 linear MSP is configured on an NE and then SNCP services are
configured on the MSP protection path using the Navigator, no error message
is reported on the NE.
Severity Minor
Root Cause The NE software does not check whether SNCP services are configured on
the MSP protection path when the operation is performed on the Navigator.
This issue does not occur when the operation is performed on the NMS.
Solution The NE software has been updated so it checks the SNCP configuration on
the Navigator.
Impact None
Description Loading a simulation package using the DC fails repeatedly on an NE. The
system displays the error message "NE error (0x19): verification failed. "
Severity Minor
Root Cause When the NE software runs the related protocol to receive the package from
the DC and fails to write the temporary file, it does not clear the flag for
determination. Even though loading attempts are made, the temporary file is
not saved. This causes a verification failure after the package is loaded.
Solution The platform software has been updated so the flag for determination is
cleared based on the actual status.
Impact None
SFP Information Can Be Queried on the U2000 Client but Cannot Be Queried
Using the NBI of the U2000
Trouble DTS: DTS2013070200102
Ticket
Number
Description SFP information can be queried on the U2000 client but cannot be queried
using the NBI of the U2000.
Severity Minor
Root Cause The OptiX 155/622H(Metro 1000) does not support the latest electronic label
specifications V3.0. Therefore, the NBI of the U2000 cannot obtain the SFP
information.
Solution The NE software has been updated to support electronic label specifications
V3.0.
Impact None
Severity Minor
Root Cause The basic BIOS of the SS49SCB can only be upgraded by chip burning
previously. For easy manufacturing and processing, in-service loading of
basic BIOS is required.
Solution The NE software has been updated to support in-service loading of basic
BIOS.
Impact None
After the Laser Is Shut Down, the Transmit Power of an Optical Module Retains
the Original Value When Being Queried Through the S oftware, Instead of Being
–60 dB
Trouble DTS: DTS2014021102655
Ticket
Number
Description After the laser is shut down, the transmit power of an optical module retains
the original value when being queried through the software, instead of being
–60 dB.
Severity Minor
Root Cause After the laser is shut down, the board software reads an invalid transmit
power value from the EEPROM of the laser. Therefore, it reports the saved
historical value to the NE software.
Solution The board software has been updated. It reports the transmit power –60 dB to
the NE software for a query through the software after the laser is shut down.
Impact None
If SS48 Series Line Boards Use SFP Optical Modules, the LOS State of Optical
Interfaces on the SFP Optical Modules Are Shown by the LOS Indicator on the
Line Unit Integrated into the System Control Board
Trouble DTS: DTS2011100800101
Ticket
Number
Description If SS48 series line boards use SFP optical modules, the LOS state of optical
interfaces on the SFP optical modules are shown by the LOS indicator on the line
unit integrated into the system control board.
Severity Minor
Root Cause The SS48 series line boards do not support control of their o wn LOS indicators
based on the receive optical power alarm. To facilitate deployment, the LOS state
is shown by the LOS indicator on the line unit integrated into the system control
board.
Solution The SS48 series line board software has been updated, so the LOS indicator on
the line unit integrated into the system control no longer shows the LOS state of
these boards.
Impact None
2.5 V300R005C01SPC300
This section describes the known issues in V300R005C01SPC201 that have been resolved in
V300R005C01SPC300.
2.5.1.1 If J2 Overhead Bytes Are Set to Values Other Than the Default Value for
an SS49EFS Board, the SS49EFS Board Reports an LP_TIM_VC12 Alarm After
Recovering from a Cold Reset
Trouble DTS2013021804030
Ticket
Number
Description If J2 overhead bytes are set to values other than the default value for an
SS49EFS board, the SS49EFS board reports an LP_TIM_VC12 alarm after
recovering from a cold reset.
Severity Minor
Root Cause On an SS49EFS board, J2 overhead bytes of VC-12s and J1 overhead bytes
for VC-3s share the same register. After the SS49EFS board is cold reset, the
NE software delivers J2 overhead bytes of VC-12s and then J1 overhead
bytes of VC-3s to the SS49EFS board. The J1 overhead bytes of VC-3s
overwrite the J2 overhead bytes of VC-12s. As a result, the J2 overhead bytes
of VC-12s take the default value and the SS49EFS board reports an
LP_TIM_VC12 alarm.
Solution The SS49EFS board software has been updated to set values of path
overhead bytes based on actual service types.
Solution None
Impact
Severity Minor
Root Cause The SS49EFS board software has a bug so it directly discards LACP packets
when the port entry detection function is enabled. As a result, the SS49EFS
board cannot transparently transmit LACP packets.
Solution The SS49EFS board software has been updated to fix the bug.
Solution None
Impact
2.5.1.3 After an SS49EFS Board Is Enabled with LCAS and Is Cold Reset, the
First Three VC-12s in the Second and Fourth VC-4s Report LP_SLM_VC12
Alarms
Trouble DTS2013021803985
Ticket
Number
Description After an SS49EFS board is enabled with link capacity adjustment scheme
(LCAS) and is cold reset, the first three VC-12s in the second and fourth
VC-4s report LP_SLM_VC12 alarms.
Severity Minor
Root Cause On an SS49EFS board, V5 overhead bytes of VC-12s in the second and
fourth VC-4s and C2 overhead bytes of VC-3s share the same register. After
the SS49EFS board recovers from a cold reset, the NE software delivers V5
overhead bytes of VC-12s and then C2 overhead bytes of VC-3s to the
SS49EFS board. The C2 overhead bytes of VC-3s overwrite the V5 overhead
bytes of VC-12s. As a result, the SS49EFS board reports LP_SLM_VC12
alarms.
Solution The SS49EFS board software has been updated to set values of path
overhead bytes based on actual service types.
Solution None
Impact
3 Known Issues
3.1 V300R005C01SPC302
This section describes the known issues in OptiX Metro 1000 V300R005C01SPC302.
Description For an SS49EFS board with VC-12 services and SNCP configured, link
capacity adjustment scheme (LCAS) is enabled. A user shuts down the laser
on the line board to trigger SNCP switching. LCAS occasionally changes to
the switching state. As a result, some data services are discarded. The
services recover 5 minutes later.
Severity Minor
Workaround Do not enable LCAS or set the WTR time of LCAS to shorter than 5 minutes.
Domain Coupling of SNCP (MSP) with LCAS and SNCP (MSP) switching triggered
Progress The cause of this issue has been found and the issue will be resolved in a later
version.