TL1Guru.com Your Gateway to the TL1 World
    
TL1 Articles
TL1 Tutorial
OSMINE
Developer Zone
Ask TL1 Guru
Contact
TL1 Tutorial

Home > TL1 Tutorial > Online TL1 Tutorial (HTML Version)

 Download PDF (zipped)

Page 9   [Contents]  < Prev  Next > 

3.6 Verb  List

The table contains a list of generic TL 1 command verbs.
S.no
Verb 
Definition
1

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
ABT
ACPT 
ACT  
ALW  
AUD  
CANC  
CHG   
CMPR  
CONN  
COPY  
CPY  
CRPT  
CRTE  
DGN  
DISC  
DLT  
ED  
ENCAP  
ENT  
EX  
EXIT  
FLTLOC  
INH   
INIT  
MEAS  
MON  
OPR  
RD  
REC  
RECNFGR  
REPT  
RLS   
RMV  
RST  
RTRV  
SCHED  
SET  
SND  
STA  
STP  
TEST  
TRACE  
WRT  
Abort
Accept
Activate
Allow
Audit
Cancel
Change
Compare
Connect
Copy
Copy
Corrupt
Create
Diagnose
Disconnect
Delete
Edit
Encapsulation
Enter
Exercise
Exit
FaultLocate
Inhibit
Initialize
Measure
Monitor
Operate
Read
Recover
Reconfigure
Report
Release
Remove
Restore
Retrieve
Schedule
Set
Send
Start
Stop
Test
Trace
Write
 

3.7 TL1 Parameters

The parameters used in TL1 message can be broadly classified into two : Position-defined parameters and Name-defined parameters.

3.7.1 Position-Defined Parameters

Position-defined parameters take the following form
ValueA, ValueB, .... (comma separated values)

They appear in the same block in any TL1 message. It is necessary to retain delimiters for position-defined parameters. Meaning, if a position defined parameter takes a null value, then empty commas exist to represent the null value.

Example : ValueA,,, ValueB, (here the two commas represented in red indicate the presence of two null values valueA and valueC). Good example for position defined parameters is the CTAG

3.7.2 Name-Defined Parameters

Name-defined parameters take the following form
Name1=Value1, name2=value2, ….

The parameter names are case sensitive, whereas the value are not case-sensitive. You need not retain delimiters to mention the null value of the values.

Example: name1=value1, name3=value3…..(though the parameter 2 is missing here, you need not have an empty comma)

NOTE : In a TL1 message you can't mix name-defined and position-defined parameters inside a single block. The type of parameter used inside a single block (separated by colon) should be of only one type either name-defined or position-defined. However, you can have multiple blocks inside the payload block each of different type.

For example, in the cross connect command given below
ED-CRS-STS1:TID:FROM_AID, TO_AID:CTAG::common_block:specific_block:state_block;  the common block and the state block are position defined, whereas the specific block is name defined.


Page 9   [Contents]  < Prev  Next > 

 

OpManager - For Complete Network Monitoring
Network Monitor

Terms of use | Privacy Policy
© Copyright 2009 TL1Guru.com
All Rights Reserved