Anda di halaman 1dari 11

DOCUMENTATION OF CDR COLLECTION FROM EWSD

SWITCH

INDEX

SECTION 1 : Requirements & Connectivity details

SECTION 2 : Creation of X25 Link for Mediation

SECTION 3 : Scheduling for Creation of Disk file Naming and Automatic Deletion of File after 6
days.

SECTION 4 : Responsibilities of Exchange in-charge

Note:- EWSD Switches with SSNC support CDR transfer on X25 link as well as FTP on Ethernet.
Separate documentation will be issued for FTP on Ethernet link for SECTION 1 and SECTION 2
SECTION 1

Requirement of Hardware for CDR collection

CARDS: LAUB &LCUB

CABLE: S38228Z76A150 ( Card to Router)

Other Pre-requisites

1. 100% CDR recording should be generated as per BSNL C.O Lr.No:13-1/2005-PHM(MSE) dated
23.03.08.

2. Additional fields should be enabled in CDR as per the instructions contained in BSNL C.O
Lr.No:13-1-2007-PHM-MSE dated 31.7.08

CONNECTIVITY DIAGRAM

CP Rack IOP
Module
EWSD EXCHANGE
PROVISIONING
X.21 15 PIN X.21 15 PIN

LAU
For S38228Z76A150
Provisio
ning
EWSD SWITCH

ROUTER
2Mbps WAN
CISCO
2811 LINK
CABLE : BSNL TO TOWARDS
PROVIDE UPTO CABLE : HCL TO DATACENTER
2811 ROUTER PROVIDE

LAU S38228Z76A150
For
Mediatio
n

X.21 15 PIN X.21 15 PIN FEMALE

MEDIATI
ON
SECTION 2

NOTES:-

1. Procedure mentioned below is intended to create X25 link 1 as Mediation link . Corresponding
changes in X25LINK and LAU parameters are to be made for other links.

2. Parameter Values in NSADR and DTEADR xxxxxxxxxxxxxx , yyyyyyyyyyyyyy (14digit) are site
dependent and may be ascertained from Networking Administrators.

3. Parameter value in PRONAM="<exchange name>" is also site dependent.

CREATION OF X25 LINK AND OTHER RELATED COMMANDS IN EWSD


EXCHANGES FOR MEDIATION 2Mbps
WAN LI
TOWARD
LIST OF COMMANDS TO BE EXECUTED DATACE
ER

Pre requisites: The IOP hardware (LCUB, LAUB) must have been installed and IOP:LAUs have been
created.

1. Configuration of IOPLAU and LAU to MBL.


<CONFLAU:LAU=0,OST=MBL;
<CONFLAU:LAU=1,OST=MBL;
<CONFIOP:IOP=IOPLAU-0,OST=MBL;
<CONFIOP:IOP=IOPLAU-1,OST=MBL;

2. Creation and configuration of X25 data Links according to MBL.


<CRX25LINK:X25LINK=1,LAU=0,CHAN=1,NET=X25,PRTCL=X25,L1BAUD=B64000,L1DTT=DTE,L1IF=X21,L
1MCA=1,L2DTT=DTE,L2LAM=RESPON,L2N1=4103,L2N2=7,L2K=7,L2T1=5000,L2T2=300,L2T3=60000,L3D
TT=DTE,L3R20=1,L3R22=1,L3R23=1,L3T10=60,L3T11=180,L3T12=60,L3T13=60,L3T20=180,
L3T21=200,L3T22=180,L3T23=180,L3T25=150,L3ICB=0,L3TCB=1&&50, L3OCB=0;

3. Creation of Remote Processors.

<CRPRO:PRONAM="BILL1",PROTYP=OSS;

4. Creation of Local OSI Network Addresses.

<CROSIADR:ADRNAM=OSILBILL,NSADR=36- xxxxxxxxxxxxxx,NET=X25;

5. Creation of Local Applications.


<CRAPPL:APPLID=FTAMR,PRONAM="<exchange name>",ADRNAM=OSILBILL,AUT=0,TSEL=0001;

6. Creation of Remote OSI Network Addresses.

<CROSIADR:ADRNAM=OSIRBILL,NSADR=36- yyyyyyyyyyyyyy,LOCADR=OSILBILL,NET=X25;
7. Creation of Remote Applications.
<CRAPPL:APPLID=FTAM,PRONAM="BILL1",ADRNAM=OSIRBILL,AUT=1,TSEL=0002;

8. Creation of Local DTE Addresses and Local X25 Routes.


<CRX25DTE:DTENAM=LOCDTE,ADRNAM=OSILBILL,NET=X25,BIDIRECT=NO;

<CRX25ROUTE:ROUTNAM=RTLBILL,DTENAM=LOCDTE,X25LINK=1,DTEADR= xxxxxxxxxxxxxx,
FACIL=FLOWNEG, WNDSZ=7-7, PCKSZ =4096-4096;

9. Creation of Remote DTE Addresses.

<CRX25DTE:DTENAM=BILLDTE,ADRNAM=OSIRBILL,DTEADR= yyyyyyyyyyyyyy,NET=X25,
BIDIRECT=NO;

10. Configuration of IOPLAU and LAU to Active.

<CONFIOP:IOP=IOPLAU-0,OST=ACT;
<CONFIOP:IOP=IOPLAU-1,OST=ACT;
<CONFLAU:LAU=0,OST=ACT;
<CONFLAU:LAU=1,OST=ACT;

11. Configuration of X25 data Lnks to Active.


<CONFX25LINK:X25LINK=1,OST=MBL;
<CONFX25LINK:X25LINK=1,OST=ACT;

12.creation of user id.


<CRUSER:USERID=CDRFTR,APPLID=FTAMR,SCOPE=REMOTE,AUT=1,AUTCL=1,PSW= abcdef;

(NOTE:- Password(PSW) to be of 6 characters. Login with the password created and change
password on 1st login and then communicate changed (new) password to the Data Center Staff)

Proper creation can be ensured by comparing with the commands and output given below:-

1) DISPX25LINK:X25LINK=1; EXEC'D

MASKNO:03653

X25LINK=1 LAU =0 CHAN =1


OST =ACT L1PST=X21 ACTIVE
L2PST=ACTIVE
NET =X25 PRTCL=X25 PRTCLVAR=
L1DTT=DTE L1IF =X21 L1MCA=1 L1BAUD=B64000
L2DTT=DTE L2LAM=RESPON L2K =7 L2N1 =4103 L2N2 =7
L2T1 =5000 L2T2 =300 L2T3 =60000
L3DTT=DTE L3R20=1 L3R22=1 L3R23 =1
L3T10=60 L3T11=180 L3T12=60 L3T13 =60 L3T24=60
L3T20=180 L3T21=200 L3T22=180 L3T23 =180 L3T25=150
L3ICB= 0 L3TCB=1 && 50 L3OCB = 0

END JOB 0681

2) DISPOSIADR:ADRNAM=OSILBILL; EXEC'D
NET ADRNAM/ PRONAM/ NSADR
LOCADR APPLID
-----+--------+--------+--------------------------------------------

X25 OSILBILL CHARM 36-40405017550003


LOCAL FTAMR

3) DISPOSIADR:ADRNAM=OSIRBILL; EXEC'D

NET ADRNAM/ PRONAM/ NSADR


LOCADR APPLID
-----+--------+--------+--------------------------------------------

X25 OSIRBILL BILL1 36-40405017550004


OSILBILL FTAM

4) DISPX25DTE:DTENAM=LOCDTE;

CHARM/A39336D0169/INDCPK1V16314607/100 08-07-21 12:24:49


0685 OMT-00/SURYAM 2970/04289

DISPX25DTE:DTENAM=LOCDTE; EXEC'D

DTENAM/ TYPE/ SALEN/ MAX LNKGRP/ LINK GROUP IDI/ DTE


PRONAM NET CUGIND SVC BIDIR STATE DTEADR FACIL
--------+------+------+----+-------+----------+---------------+---------
LOCDTE LOCAL NO 40405017550003
CHARM X25 NO

END JOB 0685

5) DISPX25ROUTE:X25LINK=1;

CHARM/A39336D0169/INDCPK1V16314607/100 08-07-21 12:25:03


0688 OMT-00/SURYAM 2970/04286

DISPX25ROUTE:X25LINK=1; EXEC'D

ROUTE DTENAM TYPE LINK LOCAL DTEADR/ WND PCK W-NS P-NS FACIL
REMOTE DTEADR I/O I/O I/O I/O
--------+--------+------+----+---------------+---+----+---+----+-------
RTLBILL LOCDTE LOCAL 1 40405017550003 7 4096 2 128
7 4096 2 128 FLOWNEG

END JOB 0688

6) DISPAPPL:APPLID=FTAM;

CHARM/A39336D0169/INDCPK1V16314607/100 08-07-21 12:25:19


0693 OMT-00/SURYAM 2970/07866

DISPAPPL:APPLID=FTAM; EXEC'D

APPLICATIONS IN O&M-NETWORK

APPLID PRONAM SPROCESS ADRNAM1 ADRNAM2 AUT


--------+--------+--------+--------+--------+------
FTAM BILL1 OSIRBILL 1

END JOB 0693


7) DISPAPPL:APPLID=FTAMR;

CHARM/A39336D0169/INDCPK1V16314607/100 08-07-21 12:25:19


0693 OMT-00/SURYAM 2970/07866

DISPAPPL:APPLID=FTAMR; EXEC'D

APPLICATIONS IN O&M-NETWORK

APPLID PRONAM SPROCESS ADRNAM1 ADRNAM2 AUT


--------+--------+--------+--------+--------+------
FTAMR CHARM OSILBILL 0

END JOB 0693

8) DISPUSERID:USERID=CDRFTR;
CHARM/A39336D0169/INDCPK1V16314607/100 08-07-21 12:25:53
0695 OMT-00/SURYAM 2970/06300

DISPUSERID:USERID=CDRFTR; EXEC'D

TABLE OF USER-IDENTIFICATIONS:

USERID STATE APPLID SCOPE REPLPROT AUT AUTHORIZATION CLASS


--------+------+------+------+--------+------+--------------------------
CDRFTR UNLOCK FTAMR REMOTE RPPWOPT 1 1

END JOB 0695


SECTION 3

Scheduling for Creation of Disk file Naming and Automatic Deletion of File after 6
days.

Notes:-

1. The procedure outlined below assumes that creation of one CDR file per day is sufficient to
cater to the requirements of the Exchange. The number of CDR files per day are to be
increased as per actual requirement of each Exchange based on the volume of CDR. Care
should be taken to ensure no loss of CDR. Naming of corresponding Command file, Day/Time
of execution as required, and CDR file name created are to be incorporated such as
CDRSU2, SUNDAY/21.30 ,AMASU.2 on SUNDAY for 2nd instance of CDR file creation.

2. Scheduling is comprising of two steps a) Creation of command files. b) Planning execution of


command files.

1) Sample Scheduling for creation of 1 CDR file per day at 10.00 Hrs

CDR
COMMAND DAY/TIME OF CDR FILE FILES
FILE EXECUTION CREATED DELETED
CDRSU1 SUNDAY/10.00 AMASU.1 AMAMO.1
CDRMO1 MONNDAY/10.00 AMAMO.1 AMATU.1
CDRTU1 TUESDAY/10.00 AMATU.1 AMAWE.1
CDRWE1 WEDNESDAY/10.00 AMAWE.1 AMATH.1
CDRTH1 THURSDAY/10.00 AMATH.1 AMAFR.1
CDRFR1 FRIDAY/10.00 AMAFR.1 AMASA.1
CDRSA1 SATURDAY/10.00 AMASA.1 AMASU.1

Sample Scheduling for creation of 2 CDR files per day at 09.30Hrs and 21.30 Hrs

COMMAND DAY/TIME OF CDR FILE CDR FILES


FILE EXECUTION CREATED DELETED
CDRSU1 SUNDAY/09.30 AMASU.1 AMAMO.1,AMAMO.2
CDRSU2 SUNDAY/21.30 AMASU.2
CDRMO1 MONDAY/09.30 AMAMO.1 AMATU.1,AMATU.2
CDRMO2 MONDAY/21.30 AMAMO.2
CDRTU1 TUESDAY/09.30 AMATU.1 AMAWE.1,AMAWE.2
CDRTU2 TUESDAY/21.30 AMATU.2
CDRWE1 WEDNESDAY/09.30 AMAWE.1 AMATH.1,AMATH.2
CDRWE2 WEDNESDAY/21.30 AMAWE.2
CDRTH1 THURSDAY/09.30 AMATH.1 AMAFR.1,AMAFR.2
CDRTH2 THURSDAY/21.30 AMATH.2
CDRFR1 FRIDAY/09.30 AMAFR.1 AMASA.1,AMASA.2
CDRFR2 FRIDAY/21.30 AMAFR.2
CDRSA1 SATURDAY/09.30 AMASA.1 AMASU.1,AMASU.2
CDRSA2 SATURDAY/21.30 AMASA.2
2 a) COMMAND FILE CREATION:-

Note:- Command files should be loaded in both MDDs


Number of command files to be created depend on the number of CDR files to be generated
per day.

COMMAND FILE CDRSU1

<CMDFILE;
<SETCFOPT:ACKCFS=ALL,ACKREQ=POS;
<DELFILE:FILE=AMAMO.;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<TRANSBUFFER:TYPE=AMA;
<TRANSFILE:FILE=AMASU.1/IA.ICAMA,COPMOD=POST,MODE=CRD;
<RELCYCFILE:FILE=IA.ICAMA,UNCOND=YES;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<RESETCFOPT;
<ENDFILE;

COMMAND FILE CDRMO1

<CMDFILE;
<SETCFOPT:ACKCFS=ALL,ACKREQ=POS;
<DELFILE:FILE=AMATU.;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<TRANSBUFFER:TYPE=AMA;
<TRANSFILE:FILE=AMAMO.1/IA.ICAMA,COPMOD=POST,MODE=CRD;
<RELCYCFILE:FILE=IA.ICAMA,UNCOND=YES;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<RESETCFOPT;
<ENDFILE;

COMMAND FILE CDRTU1

<CMDFILE;
<SETCFOPT:ACKCFS=ALL,ACKREQ=POS;
<DELFILE:FILE=AMAWE.;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<TRANSBUFFER:TYPE=AMA;
<TRANSFILE:FILE=AMATU.1/IA.ICAMA,COPMOD=POST,MODE=CRD;
<RELCYCFILE:FILE=IA.ICAMA,UNCOND=YES;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<RESETCFOPT;
<ENDFILE;
COMMAND FILE CDRWE1

<CMDFILE;
<SETCFOPT:ACKCFS=ALL,ACKREQ=POS;
<DELFILE:FILE=AMATH.;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<TRANSBUFFER:TYPE=AMA;
<TRANSFILE:FILE=AMAWE.1/IA.ICAMA,COPMOD=POST,MODE=CRD;
<RELCYCFILE:FILE=IA.ICAMA,UNCOND=YES;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<RESETCFOPT;
<ENDFILE;

COMMAND FILE CDRTH1

<CMDFILE;
<SETCFOPT:ACKCFS=ALL,ACKREQ=POS;
<DELFILE:FILE=AMAFR.;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<TRANSBUFFER:TYPE=AMA;
<TRANSFILE:FILE=AMATH.1/IA.ICAMA,COPMOD=POST,MODE=CRD;
<RELCYCFILE:FILE=IA.ICAMA,UNCOND=YES;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<RESETCFOPT;
<ENDFILE;

COMMAND FILE CDRFR1

<CMDFILE;
<SETCFOPT:ACKCFS=ALL,ACKREQ=POS;
<DELFILE:FILE=AMASA.;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<TRANSBUFFER:TYPE=AMA;
<TRANSFILE:FILE=AMAFR.1/IA.ICAMA,COPMOD=POST,MODE=CRD;
<RELCYCFILE:FILE=IA.ICAMA,UNCOND=YES;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<RESETCFOPT;
<ENDFILE;

COMMAND FILE CDRSA1

<CMDFILE;
<SETCFOPT:ACKCFS=ALL,ACKREQ=POS;
<DELFILE:FILE=AMASU.;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<TRANSBUFFER:TYPE=AMA;
<TRANSFILE:FILE=AMASA.1/IA.ICAMA,COPMOD=POST,MODE=CRD;
<RELCYCFILE:FILE=IA.ICAMA,UNCOND=YES;
<DISPFILE:FILE=IA.ICAMA,ALL=YES;
<RESETCFOPT;
<ENDFILE;
2 b) EXECUTION OF COMMAND FILES:-
In case of one CDR file per day

EXECCMDFILE:FILE=CDRSU1, TIME=10.00, PER=SU;


EXECCMDFILE:FILE=CDRMO1, TIME=10.00, PER=MO;
EXECCMDFILE:FILE=CDRTU1, TIME=10.00, PER=TU;
EXECCMDFILE:FILE=CDRWE1, TIME=10.00, PER=WE;
EXECCMDFILE:FILE=CDRTH1, TIME=10.00, PER=TH;
EXECCMDFILE:FILE=CDRFR1, TIME=10.00, PER=FR;
EXECCMDFILE:FILE=CDRSA1, TIME=10.00, PER=SA;

In case of two CDR files per day

EXECCMDFILE:FILE=CDRSU1, TIME=09.30, PER=SU;


EXECCMDFILE:FILE=CDRSU2, TIME=21.30, PER=SU;
EXECCMDFILE:FILE=CDRMO1, TIME=09.30, PER=MO;
EXECCMDFILE:FILE=CDRMO2, TIME=21.30, PER=MO;
EXECCMDFILE:FILE=CDRTU1, TIME=09.30, PER=TU;
EXECCMDFILE:FILE=CDRTU2, TIME=21.30, PER=TU;
EXECCMDFILE:FILE=CDRWE1, TIME=09.30, PER=WE;
EXECCMDFILE:FILE=CDRWE2, TIME=21.30, PER=WE;
EXECCMDFILE:FILE=CDRTH1, TIME=09.30, PER=TH;
EXECCMDFILE:FILE=CDRTH2, TIME=21.30, PER=TH;
EXECCMDFILE:FILE=CDRFR1, TIME=09.30, PER=FR;
EXECCMDFILE:FILE=CDRFR2, TIME=21.30, PER=FR;
EXECCMDFILE:FILE=CDRSA1, TIME=09.30, PER=SA;
EXECCMDFILE:FILE=CDRSA2, TIME=21.30, PER=SA;
SECTION 5

RESPONSIBILITIES OF EXCHANGE -IN-CHARGE

1. The exchange in-charge should daily check up for creation of corresponding


files on both the disks by DISPFILE command.

2. The exchange-in-charge should take back up of the files of previous day on to


MOD by renaming the files along with the date stamp such as AMA010109,
AMA010109A. Log should be maintained for the back up of CDR files.

3. The exchange-in-charge should check up for deletion of CDR files as per the
schedule.

4. To liaison effectively with Data Center staff to ensure that all the CDR files
generated are collected at Data Center.

5. To obtain error CDRs from Data Center, clear the error records and forward
back to Data Center with comments.

6. Presence of the command files on the disks to be ensured whenever


synchronization of disks is done for any activity like initialization. CFT jobs are
to be re-entered after such activity.