Showing posts with label N4GSCC. Show all posts
Showing posts with label N4GSCC. Show all posts

Wednesday, June 8, 2016

The SCC Board Reports the HARD_BAD Alarm

The SCC board reports the HARD_BAD alarm. When you query the version information about the BPA board and the GSCC board, you find that the version of the BPA board does not match the version of the GSCC board. After you upgrade the BPA board, the HARD_BAD alarm is cleared.

Product

Fault Type

HARD_BAD
Others

Symptom

The SCC board reports the HARD_BAD alarm. After the working and protection SCC boards are switched, the HARD_BAD alarm persists.

Cause Analysis

Check the HARD_BAD alarm on the T2000 to determine the slot of the faulty board and the cause of the fault.

Procedure

  1. Check the HARD_BAD alarm on the T2000. Location Information displays information about the board that causes the alarm. After you select an alarm on the T2000, the alarm location information is displayed in the lower left corner of the page.
  2. Check the software version of the board.
    1. Choose Report > Board Information Report from the Main Menu.
    2. Select the NE, and then click .
    3. Right-click a parameter name in Board Information Report and choose Software Version to display the software version of the board.
  3. Check the software version of the board, and you can find that the version of the BPA board does not match the software version of the GSCC board.
  4. Upgrade the BPA board. After the BPA board is upgraded, the HARD_BAD alarm is cleared.

Monday, April 4, 2016

Warning of Unexpected NE Resets Resulted from Reseating Boards Without a CPU on MSTP NEs

Reseating Boards Without a CPU on MSTP NEs

Product Line
Transport network product line
Product Family
Product Model
Release Date
2014-10-25
Severity
Major
Urgency
Non-urgent
Versions Involved
Versions earlier than V100R008C02SPC500
R009 and R010 versions earlier than V100R010C03SPC203
Devices Involved
OSN 1500/OSN 2500/OSN 3500/OSN 7500
Application Scope
Globally
Operation Category
Pre-warning
Warning ID
21212
Operation Requirements
Learning and prevention
Expected Completion Date

Manpower Required

Contacts
Product Line Contact
Huang Deng (employee ID: 00254844)
Regional Office Rectification Contact

Representative Office Rectification Contact


Keywords
Unexpected N4GSCC reset, reseating boards without a CPU, unreachable

[Problem Description]
Triggering conditions
An NE houses N4GSCC boards.
The NE runs a version involved.
A technician reseats a board without a CPU or its serving processing board on the NE.
The following lists boards without a CPU:
Interface boards: SSN1D75S, SSN1D12S, SSN1D34S, SSN1EU08, SSN1EU08A, SSN1OU08, SSN1TSB4, SSN1TSB8, SSN1EU04, SSN1C34S, SSN1MU04, SSN2OU08, SSN1D12B, SSN1ETF8, SSN1EFF8, SSN1ETS8, SSN1DM12, SSN1ETF8A, SSN1ETF8A, SSR1L75S, SSR1L12S, SSN1EOD41, SSN1PETF8, SSN1CQ1, SSN1MD75, SSN1MD12, SSN1PEFF8, TNN1CO1, TNN1ETMC, TNN1AFO1, TNN1D75E, TNN1D12E, SSN1CMD2, and TNN1EFF8.
Service boards: SSN1FIB, SSN1MR2A, SSR1MR2B, SSN1MR2C, TNN1XMD2, and DCU.
Auxiliary boards: SSQ2PIU, SSN1PIU, SST1PIU, SSR2PIU, SSN1FAN, SSN1FANB, SSN1FANA, SSN1FANC, and SSN1RPWR.
Symptoms
The system control boards of a problematic NE reset unexpectedly, and the NE is unreachable to the NMS within a short time.
Identification method
Check whether the unexpected resets cause the NE being unreachable to the NMS.
Check whether the reset task is tVos1s.
Run the :errlog command, and check whether the following exception information occurs within the period during which the NE is unreachable.
No.6: 2014-8-20 7:5:57
BOARD=24 TYPE=0xf0000010 SOFTTYPE=2
# 2014-8-20 7:5:13
ExcptErr: taskname=tVos1s, pc=235970, SR=1230, FaultAddr=300, DataBuff=2dcc26c
SymBol::ResetCommTaskFun__10CCommonCmdS EIPADDR=0x2399ac, Depth=0, 7:5
SymBol::Vos1sTask__Fv EIPADDR=0x1aa4664, Depth=1, 7:5
SymBol::tskAllTaskEntry EIPADDR=0x1a69510, Depth=2, 7:5
SymBol::vxTaskEntry EIPADDR=0x1b79070, Depth=3, 7:5
SymBol::0x0 EIPADDR=0000, Depth=4, 7:5
SymBol::0x0 EIPADDR=0000, Depth=5, 7:5

[Root Cause]
Compilers of system control boards of the N4 type are defective. As a result, when a board without a CPU is removed, deregistering the callback function fails and the pointer resides. When the board is installed or removed again, the corresponding task fails occasionally, resulting in a reset.

[Impact and Risk]
NEs involved are unreachable to the NMS within a short time and cannot respond to operations in time.

[Measures and Solutions]
Recovery measures
NEs involved can automatically recover.
Workarounds
None
Preventive measures
Upgrade NEs involved to V100R008C02SPC500 or a later R008 version or V100R010C03SPC203 or a later version.
Material handling after replacement
None

[Inspector Applicable or Not]
None

[Rectification Scope and Time Requirements]
None

[Rectification Instructions]
None

[Attachment]
None

More blog:

NE Configuration Loss Due to Disabling of the Automatic and Periodic Database Backup Functions on MSTP Products