EDD Invalid Block Length 7

[pshook]

Have anyone ever seen this come up int he Data Dump.

DB SEQ NUM = 4556
CONFIG
CIOD157 INFO: FMD 0 is ACTIVE, RDUN is ENABLED

PHYSICAL MAP
BCS TEMPLATE
PBX TEMPLATE
SUPER
CUST
ICI TBL
ACUST
CLID
ROUTE
DAPC
CRS
LTN TN
LTN LNK
TN
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
GRP DND
SCL
ESN 00
ESN 01
NCTL
ACD
ACD SCH
ACD IO
AUTH 00
DISA
CPK
DIGITAL
DTI
ASNCH
AML / ELAN
VAS
TRSH
BG-TIME
BG-CAT
DCH
PRI
ARIES
FDL
SYSP
XPEC
XTDT
MCAD
FCAD
FDCT
FFC
LAPW
MSDL/MISP BLK
SOCKET ID BLK
SAR
TIME
DTI PDCA
STS BLK
BKPR
CPND
CPND NM
CPND NM
SPECIFIC DATA
HI
ALARM_MGT
ZONE_MGT
SYSCFG_MGT
ACCOUNT_MGT
ERL DB
SUBNET DB
ELIN DB
BANNER_MGT
Backing NTP files
NTP_MGT
ZBD ZONES DB
ZBD DB
SYSTEM_PARAMS
PORT_STATE_MGT
CHECKING

SIZE (KBYTES) = 1639
DATADUMP COMPLETE

 

[johnpoole]

run a template audit.. ld 1.. then try the edd.. if that does not help i would go the edd clear route.. if a normal edd does not work past that, contact someone with pdt access

john poole
bellsouth business
columbia,sc

 

[pshook]

I tried the EDD CLR command but it still had the invalid block length. It looks like the back does complete it just has that error when backing up the TN's.

 

[NortelGuy1979]

Run that audit JP suggested; 99% he's right.

Matthew - Technical Support Engineer

http://www.linkedin.com/in/matty79

 

[pshook]

I ran the ld 1 audit but it still fails.

 

[NortelGuy1979]

What release of PBX? Run LD 1 twice, in a row, does it output any errors or corrections?

Matthew - Technical Support Engineer

http://www.linkedin.com/in/matty79

 

[pshook]

Opt 81c rls 6.0 and I ran it twice the first run encountered serveral duplication and 2nd was clear. I then did a EDD and it still had the error.

 

[Triton101]

are you getting any errors during regular operation?

BUG errors?

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[pshook]

NOC looked at the PDT and the error was not in PDT at all. It looked clean. I do get a few bug codes during the day but it seem normal with 8000 lines.

 

[NortelGuy1979]

Either NOC doesn't know what they're looking at, you have corruption (possible /u corruption), or something else we're not seeing from the posts.

6.0 has several corruption patches already.

Matthew - Technical Support Engineer

http://www.linkedin.com/in/matty79

 

[Triton101]

try swapping cores during a maint window and then EDD on the other core..... had weird things happen on pentium 4 cores....

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[curtismo]

I am having this on my 6.0 HA system with CPPM cores, so it appears to be across several core types. Happened after some early-on patches were installed, as we did not have this problem after the original install. Provider can't find a solution either and we've tried everything you have. And I'm worried if I have a Sysload my database may be corrupt.

My other 6.0 systems (one with single-core CPPM on VxWorks, multiple others on Co-res) are not having this issue.

 

[Firebird Scrambler]

I've found this below.

FROM RLSE 21.16J THERE IS AN ENHANCEMENT TO DATA DUMP.IF AN INVALID BLOCK LENGTH IS ENCOUNTERED IT WILL OUTPUT "INVALID DATA BLOCK LEN" AND CARRY ON WITH THE DATA DUMP.A DIAG PATCH CAN BE FITTED TO IDENTIFY THE AREA CONCERNED FOR CORRECTION.PATCH 6845 IS AVAILABLE FROM RLSE 18 ONWARDS TO GIVE THIS ENHANCEMENT TO EARLIER SOFTWARES TO I/O DEVICES ONLY (SDI/CSL/DCH).

##############################################################

ESN Corruption on Upgrade to 25 .15

There is a possible problem with ESN block corruption on Rlse 25.15 following an upgrade from an earlier release.

Symptoms

The ESN block is corrupted. An error message "invalid block length" is displayed during EDD. The problem occurs during the database conversion.

Systems Affected

It affects 25.15 sites that were upgraded from a release below 23.51.

Solution

There is a patch mplr13089 which is available on the MPL for all the relevant machine types.

To avoid this issue :
First upgrade to 25.15 using default database.

Insert mplr13089

To ensure that the patch is not kicked out of service during sysload, use the following procedure


pdt> cd /u/patch
pdt> ll
Directory of '/u/patch':

SIZE DATE TIME NAME
---------- ----------- -------- ------------
512 Feb-03-1993 16:42:00 . <DIR>
512 Feb-03-1993 16:42:00 .. <DIR>
512 Feb-03-1993 16:44:08 RETEN <DIR>
512 Sep-08-1998 16:42:22 PCH_TMP <DIR>


pdt> pload
Patch filename? p13089_1.cp4
Retain patch (y/n)? [y] Y
Days patch vulnerable to sysload? [3] 0
In-service initialize threshold? [5] 0
In-service days to monitor inits? [7] 0
Loading patch from "/u/patch/p13089_1.cp4"

Patch handle is: 0

pdt> pins 0
Modifying a longword at 0xbbb5d2a from 0x0 to 0x44f2dc2
Modifying a longword at 0xbbb5d08 from 0x0 to 0x44eff02
Modifying a longword at 0xbbb5cb4 from 0x0 to 0x44e0762
X81CONVESNLOC at 0x44df480 will be patched to jump to 0xbbb5c94
Proceed with patch activation (y/n)? [y] y
Patch 0 has been activated successfully.
pdt> exit
PDT in Progress. Please Wait....Done!

>ld 22
PT2000
REQ issp
VERSION 3011
RELEASE 25
ISSUE 15 +
IN-SERVICE PATCHES : 1
PAT# PRS PATCH REF # NAME DATE FILENAME
00 MP09967 ISS1:1OF1 CORE 2/0/0 p13089_1.cp4

Then install customer database.

Below is a copy of the edd with bad database :

ld 43
EDD000

.edd

DB SEQ NUM = 1457
CONFIG
CIOD157 INFO: CMDU 1 is ACTIVE, RDUN is ENABLED

PHYSICAL MAP
BCS TEMPLATE
PBX TEMPLATE
CUST
ICI TBL
ACUST
CLID
ROUTE
DAPC
LTN TN
LTN LNK
PGRP
TN
SCL
ESN 00
INVALID BLOCK LENGTH
INVALID BLOCK LENGTH
NCTL
ACD
AUTH 00
CPK
FRL
NFCR TREES
DTI
ASNCH
AML / ELAN
VAS
BG-TIME
BG-CAT
DCH
PRI2
ARIES
FDL
SYSP
XPEC
XTDT
FTC
MCAD
FCAD
FDCT
DTI2
FFC
LAPW
MSDL/MISP BLK
SOCKET ID BLK
MISP
TBAR RCDT
TBAR ART
SAR
TIME
DTSL
PLUGIN
CPND
CPND NM
GPHT
SPECIFIC DATA
HI
ALARM_MGT

CHECKING

RECORD COUNT = 1056
DATADUMP COMPLETE

Starting database backup
to floppy diskette on CMDU 1
KEYCODE
DIRECTORY
CONFIG
DATA
HI
ZONE
ESET1
ESET2
Database backup Complete!

#########################################################

Error message "invalid block length" is displayed during EDD

MPLR18455 applies to all Succession switches rel 03.00. Fixed in 03.70J

INVALID BLOCK LENGTH during EDD after conversion to Succession.
Special Instructions: This PEP must be loaded after installing the new release and outing all other patches/servicepacks. Then type 'pload -s 0 p18455_1.xxx ' (where xxx is the switch type) and reload (SYS) the machine. The PEP can then be removed. Then refit patches/ servicepacks.
Watch out in case switch reverts to mu law.



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[pshook]

NOC found that a deplist needs to be added to repair the issue. Thanks for everyones help!

 

[gteabc]

Had this same problem with an upgrade to 6.0 on a cppm co-res after installing the deplist. My noc took it to nortel and their answer was to power cycle the switch and that cleared the problem.