Daily Archives: April 6, 2016

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

[Problem Description]

Triggering conditions

l An NE houses N4GSCC boards.

l The NE runs a version involved.

l 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::0×0 EIPADDR=0000, Depth=4, 7:5

SymBol::0×0 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

 

TwitterLinkedInGoogle+FacebookPinterestTumblrStumbleUponRedditShare