When Failed to get the SNCP state of N3EAS2 board, NMS error code 38752

Issue Description

Customer created many VC4 SNCP services for the N3EAS2 board in slot 11, but a NMS error appaeared when try to get the SNCP state for the VC4 timeslot bigger than 64, plese find it in attachment.
version information:
U2000       V100R005C00SPC600
OSN7500  V100R010C03SPC200

Alarm Information

Invalid parameter returned by board.Error Code:38752

Handling Process

workaround:
1.Dont configure the SNCP services on the N3EAS2 board with the VC4 timeslot bigger than 64,
Or use a normal cross-connection service instead of it.
2.Configure the SNCP to a line board instead of the N3EAS2 board.
solution:
R&D will release a hot patch(V1R10C03SPH201) to solve this issue in May 2012.
In this version, the max value for VC4IdPort parameter is modified to 256.

Root Cause

We make a simulation enviroment in our lab and re-produce the issue:
1.make a SNCP services on the N3EAS2 board in slot 8,then check the SNCP infomartion:
:cfg-get-sncpbdmap:8
SNCP-PU-MAP
PG-ID   PU-ID     SRC-BID  SRC-PID  SRC-AU4  SRC-PATH  DST-BID  DST-PID  DST-AU4  DST-PATH  XC-LEVEL
8       work      2        1        3        0         7        1        76       0         vc4
8       backup    11       1        3        0         7        1        76       0         vc4
Total records :2

:cfg-get-sncpstate:8
failed! cmd:0x8552 error:0x9760 NSERR_BDRSP_BAD_PARA
Configuration exists on the GSCC board.But cant get the state.

2. Compare the SNCP configuration on the GSCC and SXCS board:
:cfg-get-sncppg
SNCP-PROTECTION-GROUP
PG-ID   REVERT-MODE  ACTIVE-FLAG
1       rvt          active
2       rvt          active
3       rvt          active
8       rvt          active
Total records :4
Four sncp protection groups are confiuged on the GSCC board.
:optp:a,0,ad,1,23,03
Optp cmd : 2303
00 03 00 03 00 02 00 01
Total records :1
Three sncp protection groups are confiuged on the 10-SXCS board.
So we find the sncp protection group does not exist on the SXCS board.
3.Check the black box of SXCS board,and find follow records from bb9.log &bb4.log during creating the SNCP serivces:
bb9.log                               2012-04-18 05:32:48+00:00      Level:3, algx_config.cpp, Line:9216, wPairID[8],VC4IdInPort[76],UnitID[2],sncxpType[0],Algx Add Sncx
bb9.log                               2012-04-18 05:32:48+00:00      Level:2, algx_config.cpp, Line:1515, Cmd[0x2300] Err: ErrNum[2]
bb9.log                               2012-04-18 05:32:48+00:00      Level:2, algx_config.cpp, Line:1515, Cmd[0x2700] Err: ErrNum[4]
bb9.log                               2012-04-18 05:32:49+00:00      Level:3, Sncp.cpp, Line:2591, wPairID[8],sncxpType[SNCP],Evt HpState Mointor Non-existant.

bb4.log                               2012-04-18 05:32:48+00:00      23 00 00 08 00 43 02 01 00 03 00 02 83 0b 01 00 03 00 01 cc 07 01 00 4c 00 01 01 02 58 01 ff ff ff

The highest bandwidth is 10G for an optical port of SDH board Normally, so there is a limitation on the SXCS board that the VC4IdInPort parameter cant be bigger than 64.
In this scenario, GSCC board would send the command to SXCS board with VC4IdInPort-0x004c(76), then SXCS board will discard this configuration and write an error record in black box.

Suggestions

This problem only happened on N3EAS2 board by now.
When the problem happened, the SNCP services can work,but cant switch.

 

Categories:

Tags:

Comments are closed