Debugging Eagle DDB using DDB commands in Release 41.

0 - Tekpedia

Page 1

Debugging Eagle DDB using DDB commands in Release 41.0

From Tekpedia
Debugging DDB issues in Release 41.0 with DDB (Phase-2) commands To go back to main page -> Debugging Eagle DDB The DDB audit is automatic and periodic. Following are the commands provided to find the status of the Dynamic Database in an Eagle System. DDBAUDTIMER SS7OPTS option helps to enable and disable the background audit.
Chg-ss7opts:ddbaudtime = {None, [5-1440]} Rtrv-ss7opts:ddbaudtimer

Use this command to manual trigger the dynamic database audit:

aud-data: [type=<ddb|fixed>]: [display=<all|brief|except>]: [ddbqp=<quite quite period in msec>] Fixed: Triggers a static database audit. DDB: Triggers a Dynamic Database (DDB) audit.

Display a report of the last DDB audit:

rept-stat-ddb: [display=<all|brief>]

dbg-ddb: action=<aud|disp|stats> loc=<1101..6118> tbl=<lnk|ls|rte>: [audtype=<mc|uc>] [dpc=<dpc Point code>] [dpci=dpci Point code>] [dpcn=dpcn Point code>] [dpcn24=<dpcn24 Point code>] [link=<port>] [lsn=lsn ayyyyyyyy [rloc=<1101..6118>] [tidx=<table_index>]

Debugging Route Table Entries for DDB issues Audit the dynamic database (DDB) of the Eagle system by the following command: aud-data:type=ddb:display=all Command output is as follows:
DDB AUDIT REPORT SYSTEM STATUS: CORRUPT INCONSISTENT CARDS: 1201 1205 (2) AUDIT START TIME: 08/10/2008 16:15:31 NON RESPONDING CARDS: 3101 (1) DDB QUIET PERIOD: 500 ms LINK CM CM MATED MTP SET LINK CARD CLSTR APPL GLOBLS H'e213 H'c123 H'ae12 H'e123 -----H'0000 H'e213 H'c123 H'ae12 H'e123 H'ab23 H'0000 H'e213 H'c123 H'ae12 H'e123 -----H'0000 H'e213 H'c123 H'ae12 H'e123 -----H'0000 H'e213 H'c123 H'ae12 H'e123 -----H'0000 H'e213 H'c123 H'ae12 H'e123 H'ab23 H'0000 H'e213 H'c123 H'ae12 H'e123 -----H'0000 IDLE PERIOD 1200 1200 1200 1200 1200 1200 1200 DDB UPDATES 899 899 899 899 899 899 899

LOC 1101 1103 1105 1109 * 1201 1203 * 1205 ;

RTE H'ab12 H'ab12 H'ab12 H'ab12 H'ac72 H'ab12 H'ae62

Here * indicates the inconsistent cards. DDB System Status Following are the possible system status:
OK CORRUPT

http://tekpedia.ssz.tekelec.com/tekpedia/index.php/Debugging_Eagle_DDB_using_DDB_commands_in_Release_41.0

26/10/2011 03:36:15

Debugging Eagle DDB using DDB commands in Release 41.0 - Tekpedia

UNKNOWN ABORTED

Page 2

Apart from OK state any of the other 3 system status indicates DDB is unstable. System status CORRUPT indicates that there are cards in the system with inconsistent DDB checksums. Select one of the inconsistent cards (marked with * in full report) from the INCONSISTENT CARDS list, and one of the consistent cards and run the following command: dbg-ddb:loc=<inconsistent card addr>:rloc=<consistent card>:tbl=rte: action=aud:audtype=uc Here you can see card 1205 and 1201 have different check sum value for Route (RTE) entries. So we can select the inconsistent card 1205 and consistent card 1101 and analyze further. Also note all effected PC.
dbg-ddb:loc=1205:rloc=1101:tbl=rte:action=aud:audtype=uc Command output comes as follows: Card[1205]->card[1101] (Tbl:2) TblAuditDone:TotalMisses:h'2 FirstMiss:h'1 ; tekelecstp 09-06-30 15:33:03 MST UNKNOWN ??.?.?-62.34.1 [1205] [Route:h'1] Chksum h'8fec at h'8fc3fb (75 bytes) PC: 001-001-002 LstRt:0 CmbRt:6 Dyn:h'1 TFC:0 Xlst:0 MOBR:0 NAdj:1 3 3 3 3 3 NmTFR:0 PrevSt:1 SRT:h'8807b8 (28 bytes) AKT:h'8bb448 (12 bytes) ; tekelecstp 09-06-30 15:33:03 MST UNKNOWN ??.?.?-62.34.1 [1101] [Route: h1] Chksum h'662f at h'8517b6 (54 bytes) PC: 001-001-002 LstRt:0 CmbRt: 6 Dyn: h1 TFC:0 Xlst: 0 MOBR:0 NAdj: 1 3 3 3 3 3 NmTFR:0 PrevSt:1 SRT: h80b7ac (28 bytes) AKT: h99f994 (12 bytes) ;

TotalMisses indicates the no. of mismatched entries in the route table. Only first mismatch entry is displayed on the command output. Now in this case the PC on card 1205 is 1-1-2 .Now we need to deactivate and activate those SLK which are provisioned with this PC. After correcting this entry again execute the dbg-ddb command to find the next mismatch entry. If there are multiple mismatched entries then similar process needs to be followed for all the PCs. Output comes as follows
rtrv-rte:dpc=1-1-2 tekelecstp 09-06-30 14:54:32 MST DPCA 001-001-002 ALIASI -------------UNKNOWN ??.?.?-62.34.1 ALIASN/N24 RTX LSN RC -------------No ls112 10 CLLI APCA ----------001-001-002

rtrv-ls:lsn=ls112 L3T SLT GWS GWS GWS SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS none 1 1 no A 1 off off off no off

LSN ls112

APCA (SS7) 001-001-002

SPCA CLLI TFATCABMLQ MTPRSE ASL8 ---------------- ----------- 1 --no RANDSLS off IPSG no IPGWAPC no GTTMODE CdPA L2T SET 1 CGGTMOD no PCR PCR E1 E1 ECM N1 N2 LOC PORT TS BASIC ---- ------ 1201 1 6

LOC LINK SLC TYPE 1201 B1 0 LIME1

BPS 56000

Link set table is (17 of 1024) 1% full. ;

Based on above data we need to deactivate and activate the following link:
dact-slk:loc=1201:link=b1 act-slk:loc=1201:link=b1

In case of multiple PCs and links, at each step of deactivating and activating links you need to verify the DDB status (using aud-data command), as you might not need to deactivate all the links. Now run the aud-data command and if still cards are shown as INCONSISTENT then follow similar steps for the inconsistent cards. Retrieved from "http://tekpedia.ssz.tekelec.com/tekpedia/index.php/Debugging_Eagle_DDB_using_DDB_commands_in_Release_41.0"

http://tekpedia.ssz.tekelec.com/tekpedia/index.php/Debugging_Eagle_DDB_using_DDB_commands_in_Release_41.0

26/10/2011 03:36:15

Debugging Eagle DDB using DDB commands in Release 41.0 - Tekpedia

Page 3

This page was last modified 10:30, 8 January 2010.

http://tekpedia.ssz.tekelec.com/tekpedia/index.php/Debugging_Eagle_DDB_using_DDB_commands_in_Release_41.0

26/10/2011 03:36:15