OptiX High-level Training Manual Part 2 Equipment Commissioning

Chapter 5 Standard of Command Line Provisioning

File for SDH Equipment

Chapter 5 Standard of Command Line Provisioning

File for SDH Equipment

5.1 Standard of Command Line Provisioning File for

OptiX155/622H
5.1.1 Announcements

1）Purpose
This specification aims at standardizing the contents and format of the MML
batch files and specifying the data that need to be configured in the MML for
the convenience of future maintenance. For the office deployed after the
specification is issued, its MML should be written in accordance with this
specification. Software project QC to be conducted hereafter shall also refer
to this specification. The statements that fall short of the writing specification
in the MML files will be handled as off-specification items.

2） All the commands should be sent one by one by pressing the "Y" key
after a prompt shows up in the command entry window.

3 ） After the batch files are sent and checked successfully and the NE
status becomes stable, the databases (drdb, fdb0 and fdb1) must be
backed up using the following commands:

:dbms-copy-all:mdb,drdb;
:dbms-backup-all:fdb0;

:dbms-backup-all:fdb1;

4） When the command is sent from the "sbsterm" in the workstation, the
writing format of "#5:cfg-set-stgpara:sync=intr:" cannot be used. Instead, it
should be written in two lines:

#5:

:cfg-set-stgpara:sync=intr;

That is to say, NE switchover is only conducted in the format of "#5:".

5 ） For 155/622H, it is probable that the result back display of the 4.02
serial commands can be inexplicable. In this case, the command
":tm155a:false" can be used to convert it into the format we habitually use.

2-1
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

6）Explanation is given below using the example of OptiX 155/622H MML

writing. It is applicable for the NEsoftware 4.02.X.

5.1.2 Writing Standard for OptiX155/622H

1 ） The first line of the batch file cannot be a null line, otherwise the
"sbsterm" software of the workstation will not give the prompt of "(Yes, No,
or All)".

2 ） Log in NE (supposing the NE ID is 1). Notice the NE ID (PC network

management) should be added prior to the login statement:

#1:login:1,"nesoft";

3）Setting the display mode

:tm155a:false;

The set display mode is false. If it is set as true, a large bunch of 155A-
exclusive return codes will be returned whenever a command is sent, which
is quite difficult to understand, so normally the above command is sent.

4）Stopping performance monitoring

:per-set-endtime:15m&24h,1990-0-0,0*0;

This line is to avoid the situation where a large number of performance

events are reported, thus affecting the sending of batch files. If there is a
performance event to be reported, the next command should be sent after
reporting is complete. Restart performance monitoring in the end after all
the configurations are sent.

5）Initializing the system

:cfg-init<sysall>;

6）Setting the NE parameters

:cfg-set-nepara:nename="1- local office":device=sbs155a:gne=true;

The NE is named in a uniform manner as "ID-Station Name". The same

station can take several NEs and be named something like "ID-Station
Name (Ring 1)". The device of 155/622H is "sbs155a".

7）Creating the logic system

:cfg-create-lgcsys:sys1&sys2;

8）Defining the name of the logic system

:cfg-set-sysname<sys1>: "ring1";

:cfg-set-sysname<sys2>: "shanghai";

2-2
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

The name of the logic system must be defined, or the display of logic
system names in the network management will likely be abnormal.

Advise that the logic system should be defined with the direction connected
by the relevant line unit ： the logic system is defined as "ring" if it's a
ring，or "the name of the opposite station" if it's a chain。

9）Creating the logic slot

:cfg-create-board:4,pd2d:11,oi2d:12,oi2s:9,x42:15,stg:18,ohp2;

10）Setting order wire telephone parameters

:cfg-set-ohppara:tel1=101:meet=999;

:cfg-set-ohppara:reqt=5:dial=dtmf;

:cfg-set-ohppara:rax=sys1&sys2;

11）Setting clock parameters

:cfg-set-stgpara:sync=w1s8k :syncclass=w1s8k&intr;

12）Setting the mapping from logic equipment to physical equipment

:cfg-set-gutumap<sys1&&sys2>:t4,4,pd2d,0;

:cfg-set-gutumap<sys1>:gw1,11,oi2d,1;

:cfg-set-gutumap<sys1>:ge1,11,oi2d,2;

:cfg-set-gutumap<sys2>:ge1,12,oi2s,0;

13）Setting the parameters of the line unit

:cfg-set-gupara<sys1,gw1>:srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara<sys1,gw1>:src2=tugs:stc2=tugs;

:cfg-set-gupara<sys1,ge1>:srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara<sys1,ge1>:src2=tugs:stc2=tugs;

:cfg-set-gupara<sys2,ge1>:srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara<sys2,ge1>:src2=tugs:stc2=tugs;

14）Setting the parameters of the tributary unit

:cfg-set-tupara:tu4,1&&10,p&75o;

:cfg-set-tupara:tu4,11&&32,np&75o;

15）Setting the mapping relationships of the cross-connect unit

:cfg-set-xcmap<sys1&&sys2>:xlwork,9,x42;

2-3
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

16）Setting the attributes of the logic system

:cfg-set-attrib<sys1>:155:2f:uni:pp:ring:adm;

:cfg-set-attrib<sys2>:155:2f:bi:nopr:line:tm;

17）Initializing all the time slot configurations

:cfg-init-slot<sysall>;

18）Configuring time slots

//Station 1--Station 2 10*2M

:cfg-create-vc12:sys1,gw1,1&&10,sys1,t4,1&&10;

:cfg-create-vc12:sys1,t4,1&&10,sys1,ge1,1&&10;

//Station 1--Station 3 10*2M

:cfg-create-vc12:sys2,ge1,11&&20,sys2,t4,11&&20;

:cfg-create-vc12:sys2,t4,11&&20,sys2,ge1,11&&20;

Notes must be given after time slot configuration to mark the direction of the
time slot. For the adding and dropping VC12 payloads of this station, the
format of Notes is "//name of the station-- name of the opposite end station-
number of VC12* time slots"; for VC4 payloads, the format of Notes is
"//name of the station-- opposite end station name VC4-which VC4". The
VC4 numbers at both ends should be consistent (for example, both of them
should be the first VC4); for the pass-through payloads of this station, the
format of Notes is "//pass-through" or more detailed notes. The payloads of
different destinations can be separated by null strings. It is believed that
notes made in this way will also be beneficial to the notes maker.

19）Check on downloading of configurations

:cfg-checkout;

20）Querying NE status

:cfg-get-nestate;

5.2 Standard of Command Line Provisioning File for

OptiX155/622
5.2.1 Announcements
1) Purpose

This standard is to unify the writing contents and writing format of command
line provisioning batch files, and to specify the configuration data in

2-4
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

command line and make the future maintenance convenient. For the project
which is deployed after the issuing date of this standard, the statements in
its command line file should also be written according to this standard. And
the future quality inspection of software should also be executed according
to this standard. The statements which do not accord with this standard will
be treated invalid.

2) This standard is based on NE software version 4.01.15.52.

30 Press Y to send all commands one by one after the prompts.

4) After provisioning batch files are all sent and verified successfully, wait till
the NE states are stable, then execute the following commands one by one
to back up database of NE software (drdb, fdb0 and fdb1).

:dbms-copy-all:mdb,drdb;

:dbms-backup-all:fdb0;

:dbms-backup-all:fdb1;

5) When a command is sent via "sbsterm" software of workstation , the

writing format of "#5:cfg-set-stgpara:sync=intr;" can not be used, and the
command must be written in two lines separately as follows:

#5:

:cfg-set-stgpara:sync=intr;

That means, in order to switchover the operated NE, only the "#5:" format is
available.

5.2.2 Writing Standard for OptiX155/622

1) The first line of provisioning batch files can not be blank line, otherwise,
the sbsterm software of the workstation will not prompt "(Yes，No，or All)".

2) Login NE (take NE ID=1 as example). Please note that the ID number of

NE should be added before the login statement (for OptiX Navigator
software).
#1:login:1,"nesoft";
For the batch files for SUN workstation NMS, the writing format should be
as follows:
#1:
:login:1,"nesoft";
Write in two lines separately, and note that there should be no space after
"#1:", otherwise, it can not be sent to the correct NE!!

3) Stop monitoring performance

2-5
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

:per-set-endtime:15m&24h,1990-0-0,0*0;
This statement is to avoid that large amount of performance data is reported
and sending of provisioning batch file will be blocked. If there is any
performance data reported, the following command should not be sent until
the report is over. After sending all commands in batch file, start
performance monitoring finally.

4) Initialize the NE

:cfg-init<sysall>;

5) Set NE parameters

:cfg-set-nepara:nename="1-head
office":device=sbs622:bp_type=type3:gne=true;

NE name is specified as "ID-station name" in a unified manner. If there are

multiple NEs in the same station, NE name can be specified as "ID-station
name (r1)" similarly (r1 means ring 1).

The device of OptiX155/622 is "sbs622", the device of OptiX155/622H is

"sbs155a". Under general condition (enhanced subrack, SS12PL1 or
SS11PD1 allocated), "type3" is selected for "bp_type" parameter.

If this NE is gateway network element, "gne=true" should be set. Otherwise,

set "gne=false" or do not set this parameter (the default is false).

6) Create logical system

:cfg-create-lgcsys:sys1&&sys2;

7) Define logical system name

:cfg-set-sysname<sys1>: "sys1";

:cfg-set-sysname<sys2>: "sys2";

Note: The logical system name must be defined, otherwise, the display of
logical system name on NMS might be abnormal.

8) Create logical board

:cfg-create-board:1&&3,pd1:4,tda:9,gtc:11&12,sl4:13,sl1:15,stg:18,ohp2;

9) Set the work mode of GTC

:cfg-set-gtcpara:work_mode=main;

10) Set order-wire parameters

:cfg-set-ohppara:tel1=1101:meet=9999;

:cfg-set-ohppara:reqt=5:dial=dtmf;

2-6
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

:cfg-set-ohppara:rax=sys1;

If there is the requirement for setting multiple order-wire numbers or inter-

subnetwork order-wire etc., parameters should be set additionally.

11) Set clock parameters

:cfg-set-stgpara:sync=w1s8k :syncclass=w1s8k&intr;

:cfg-set-stgbackup:12,stg ,0;

:cfg-set-stgbackup:13,stg ,1;

If a NE has two STG units, the active/standby relation between these two
units should be set, as illustrated in the second and third statements.
Otherwise, it is not required.

If there are other parameters such as protection switching of clock source

etc., they should be set correspondingly, and set them in command lines as
possible as you can.

12) Set the mapping from physical equipment to logical equipment

:cfg-set-gutumap<sys1>:gw1&&gw4,11,sl4,0;

:cfg-set-gutumap<sys1>:ge1&&ge4,12,sl4,0;

:cfg-set-gutumap<sys2>:gw1,13,sl1,0;

:cfg-set-gutumap<sys1&sys2>:t1,1,pd1,0;

:cfg-set-gutumap<sys1&sys2>:t2,2,pd1,0;

:cfg-set-gutumap<sys1&sys2>:t3,3,pd1,0;

:cfg-set-gutumap<sys1&sys2>:t4,4,tda,0;

13) Set parameters of LU

:cfg-set-gupara<sys1,gw1&&gw4>:srj1="HuaWei SBS":stj1="HuaWei
SBS";

:cfg-set-gupara<sys1,gw1&&gw4>:src2=tugs:stc2=tugs;

:cfg-set-gupara<sys1,ge1&&ge4>:srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara<sys1,ge1&&ge4>:src2=tugs:stc2=tugs;

:cfg-set-gupara<sys2,gw1>:srj1="HuaWei SBS":stj1="HuaWei SBS"；

:cfg-set-gupara<sys2,gw1>:src2=tugs:stc2=tugs;

For the project which is deployed newly, this setting is not required
generally, and the default is used (By default, the J1 bytes which should be

2-7
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

received and sent are HuaWei SBS). For the upgrading and expansion of
existing network, this setting might be required, so as to keep J1 and C2
bytes consistent with the exitsting ones of other NEs, refer to Data Setting
standard for details.

14) Set parameters of TU

:cfg-set-tupara:tu1&&tu3,1&&32, np&75o;

:cfg-set-tupara:tu4,1&&4, np&75o;

15) Set the mapping relation of cross-connect unit

:cfg-set-xcmap<sys1&sys2>:xlwork,9,gtc;

16) Set the attribute of logical system

:cfg-set-attrib<sys1>:622:2f:bi:msp:ring:adm;

:cfg-set-attrib<sys2>:155:2f:bi:nopr:line:tm;

17) Initialize all timeslot configurations

:cfg-init-slot<sysall>;

18) Configure timeslots(traffic)

:cfg-create-vc12:sys1,ge1,1&&32,sys1,t1,1&&32; //Central station

-- Station 3 VC12*32

:cfg-create-vc12:sys1,t1,1&&32,sys1,ge1,1&&32;

:cfg-create-vc12:sys1,gw1,33&&48,sys1,ge1,33&&48; //passing
through

:cfg-create-vc12:sys1,ge1,33&&48,sys1,gw1,33&&48;

:cfg-init-64k:4; //TDA traffic must be initialized before the

configuration

:cfg-create-vc12:sys1,ge1,63,sys1,t4,1; //Central station -- TDA traffic in

station 8

:cfg-create-vc12:sys1,t4,1,sys1,ge1,63;

:cfg-create-64k:4,bi,0,3,2,1; //Configure 64K

traffic

A comment must be added following the timeslot configuration, so as to

mark the direction of this traffic. For the VC12 traffic added droped in this
station, the comment format is //this station name -- opposite station name

2-8
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

VC12*timeslot quantity; for VC4 traffic, the comment format is //this station
name -- opposite station name VC4- number, the VC4 numbers at both
ends should be consistent (e.g., both are VC4-1); for the traffic passing
through in this station, the comment is //pass through, or in more details.
The traffics with different destinations can be spaced by an blank line. For
the method of configuring TDA traffic, please refer to the relative file, which
is required to be mastered by each engineer.

Believe that such comments will also benefit youself.

19) Set Multi-Section Protection parameters

:apsc-set-para:sys1,0,1,600;

20) Checkout all the configurations and download them to each unit

:cfg-checkout;

21) Query NE state

:cfg-get-nestate;

5.3 Standard of Command Line Provisioning File for

OptiX2500+
5.3.1 Announcements
1) Purpose

This standard is to unify the writing contents and writing format of command
line provisioning batch files, and to specify the configuration data in
command line and make the future maintenance convenient. For the project
which is deployed after the issuing date of this standard, the statements in
its command line file should also be written according to this standard. And
the future quality inspection of software should also be executed according
to this standard. The statements which do not accord with this standard will
be treated invalid.

2) This standard is based on NE software version 4.05.02.02.

30 Press Y to send all commands one by one after the prompts.

4) After provisioning batch files are all sent and verified successfully, wait till
the NE states are stable, then execute the following commands one by one
to backup database of NE software (fdb0 and fdb1).

:dbms-backup-all:fdb0;

:dbms-backup-all:fdb1;

2-9
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

5) When a command is sent via "sbsterm" software of workstation , the

writing format of "#5:cfg-set-stgpara:sync=sets;" can not be used, and the
command must be written in two lines separately as follows:

#5:

:cfg-set-stgpara:sync=sets;

That means, in order to switchover the operated NE, only the "#5:" format is
available.

5.3.2 Writing Standard for OptiX2500+

1) The first line of provisioning batch files can not be blank line, otherwise,
the sbsterm software of the workstation will not prompt "(Yes，No，or All)".

2) Login NE (take NE ID=1 as example). Please note that the ID number of

NE should be added before the login statement (for OptiXNavigator
software).
#1:login:1,"nesoft";
For the batch files for SUN workstation NMS, the writing format should be
as follows:

:login:1,"nesoft";
Write in two lines separately, and note that there should be no space after
"#1:", otherwise, it can not be sent to the correct NE!!

3) Stop performance monitoring

:per-set-endtime:15m&24h,1990-0-0,0*0;
This statement is to avoid that large amount of performance data is reported
and sending of provisioning batch file will be blocked. If there is any
performance data reported, the following command should not be sent until
the report is over. After sending all commands in batch file, start
performance monitoring finally.

4) Initialize the NE

:cfg-init<sysall>;

5) Set NE parameters

:cfg-set-nepara:nename="1-
shenzhen":device=sbs2500+:bp_type=enhance:gne=true;

NE name is specified as "ID-station name" in a unified manner. If there are

multiple NEs in the same station, NE name can be specified as "ID-station
name (r1)" similarly (r1 means ring 1).

2-10
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

The device of OptiX2500+ is sbs2500+. If the subrack is standard, the value

of "bp_type"should be "standard"; if the subrack is enhanced, the value be
"enhance". If this NE is a gateway NE, gne=true should be set, otherwise,
set gne=false, or do not set this parameter (the default is false).

6) Create logical system

:cfg-create-lgcsys:sys1&&sys2;

7) Define logical system name

:cfg-set-sysname<sys1>: "sys1";

:cfg-set-sysname<sys2>: "sys2";

8) Set the attribute of logical system

:cfg-set-attrib<sys1>:2500:2f:bi:msp:ring:adm;

:cfg-set-attrib<sys2>:155:2f:bi:nopr:line:tm;

These two commands must be ahead of the commands which set the
mapping from physical equipment to logical equipment.

9) Create logical board

:cfg-create-board:2,ba2:3&4,pq1:5&6,s16:7&8,xcs:10,sde:16:pq1:17:eipc;

The board position of PMU is 19, but it's not necessary to create this board
in command line. After the OptiX equipment is powered on, the PMU will
enter running state automatically. The last work to do is to add PMU in
board-position window of NMS after provisioning.

10) Set the work mode of XCS

:cfg-set-workback:0,7,8;

11) Set order-wire parameters

:cfg-set-
ohppara:tel=1&1103:tel=2&1203:tel=3&1303:meet=9999:rax=sys1&sys2:sn
etlen=1;
:cfg-set-
ohppara:snetbd=0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&1&0&0&0&1&0
&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0&0;

If there is the requirement for setting multiple order-wire numbers or inter-

subnetwork order-wire etc., parameters should be set additionally.

12) Set clock parameters

:cfg-set-stgpara:syncclass=ex18k&sl5p1&sets;

2-11
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

If there are other parameters such as protection switching of clock source

etc., they should be set correspondingly, and set them in command lines as
possible as you can.

13) Set the mapping from physical equipment to logical equipment

:cfg-set-gutumap<sys1>:g1wall,5,s16,1;

:cfg-set-gutumap<sys1>:g1eall,6,s16,1;

:cfg-set-gutumap<sys2>:g1w1,10,sde,1;

:cfg-set-gutumap<sys1&&sys2>:t3p1,3,pq1,0;

:cfg-set-gutumap<sys1&&sys2>:t4p1,4,pq1,0;

14) Set parameters of LU (usually take the default value instead of setting
the parameters manually)

:cfg-set-gupara:iu5,0,srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara:iu5,0,src2=tugs:stc2=tugs;

:cfg-set-gupara:iu6,0,srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara: iu6,0,src2=tugs:stc2=tugs;

:cfg-set-gupara:iu10,0,srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara:iu10,0,src2=tugs:stc2=tugs;

:cfg-set-gupara:iu16,0,srj1="HuaWei SBS":stj1="HuaWei SBS";

:cfg-set-gupara:iu16,0,src2=tugs:stc2=tugs

For the project which is deployed newly, this setting is not required
generally, and the default is used (By default, the J1 bytes which should be
received and sent are HuaWei SBS). For the upgrading and expansion of
existing network, this setting might be required, so as to keep J1 and C2
bytes consistent with the exitsting ones of other NEs, refer to Data Setting
standard for details.

15) Set parameters of TU

:cfg-set-tupara:iu3&iu4,1&&63, np;

16) Configure timeslots (traffic)

//shenzhen--guangzhou VC12*16

:cfg-create-vc12:sys1,g1w4,1&&16,sys1,t3p1,1&&16;

:cfg-create-vc12:sys1,t3p1,1&&16,sys1,g1w4,1&&16;

2-12
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

A comment must be added following the timeslot configuration, so as to

mark the direction of this traffic. For the VC12 traffic added droped in this
station, the comment format is //this station name -- opposite station name
VC12*timeslot quantity; for VC4 traffic, the comment format is //this station
name -- opposite station name VC4- number, the VC4 numbers at both
ends should be consistent (e.g., both are VC4-1); for the traffic passing
through in this station, the comment is //pass through, or in more details.
The traffics with different destinations can be spaced by an blank line. For
the method of configuring TDA traffic, please refer to the relative file, which
is required to be mastered by each engineer.

Believe that such comments will also benefit youself.

17) Set Multi-Section Protection parameters

:apsc-set-para:sys1,0,4,600;

18) Checkout all the configurations and download them to each unit

:cfg-checkout;

19) Query NE state

:cfg-get-nestate;

2-13
OptiX High-level Training Manual Part 2 Equipment Commissioning
Chapter 5 Standard of Command Line Provisioning
File for SDH Equipment

Chapter 5 Standard of Command Line Provisioning File for SDH Equipment................2-5-1

5.1 Standard of Command Line Provisioning File for OptiX155/622H.........................2-5-1

5.1.1 Announcements...........................................................................................2-5-1

5.1.2 Writing Standard for OptiX155/622H...........................................................2-5-2

5.2 Standard of Command Line Provisioning File for OptiX155/622............................2-5-4

5.2.1 Announcements...........................................................................................2-5-4

5.2.2 Writing Standard for OptiX155/622..............................................................2-5-5

5.3 Standard of Command Line Provisioning File for OptiX2500+..............................2-5-9

5.3.1 Announcements...........................................................................................2-5-9

5.3.2 Writing Standard for OptiX2500+...............................................................2-5-10

2-14