H 3

###################################################################################
#########
Command syntax, regular expressions
###################################################################################
#########
#################################################
3.1- How MOs are identified
#################################################
- RDN (Relative Distinguished Name)
This is used to identify an MO in relation to its nearest parent in the MO tree.
The RDN contains MO Class (also called MO Type), the equal sign, and MO identity.
Example: AtmPort=MS-24-1 ==> "AtmPort" is the MO Class, "MS-24-1" is the
identity
- LDN (Local Distinguised Name)
This is used to uniquely identify an MO within a node.
The LDN shows the hierarchy above the MO, within the Managed Element's MO tree.
Example: ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1
- FDN (Full Distinguished Name)
This is used to uniquely identify an MO within a network (used by RANOS/CNOSS).
Example:
SubNetwork=AUS,SubNetwork=H2RG_0201,MeContext=St_Leonards_Station_2065010,ManagedEl
ement=1,TransportNetwork=1,AtmPort=MS-24-1
##################################################
3.2- How to address the MOs in MO-related commands
##################################################
The first argument in the MO-related commands is usually used to specify the MOs
that should be affected by the command.
Six ways can be used to specify the MO(s):
1) all
==> all MOs in the proxy table will be affected
Example: get all userlabel ---> get attribute "UserLabel" on all MOs
Note: instead of "all", it is also possible a wildcard such as "." or "*". This has
the same effect.
2) proxy id(s)
==> MO(s) with the given proxy id(s) will be affected.
To specify several MO proxies, there are two ways:
- Specify each proxy id with a space in between
Example: pr 0 2 5 --> print MO proxies 0, 2, and 5
- Give a range
Example: pr 4-10 --> print MO proxies from 4 to 10
pr 10-4 --> print MO proxies from 10 to 4 (reverse order, useful for
deleting MOs)
acc 10-20 restart ---> restart MOs with proxy 10 to 20
Note: proxy ranges and individual proxy Ids can be mixed on the same line.
Example: pr 0 2 3-5 8 10-12
3) link handler (for pluginunit and spm MOs only)

Example: acc 001400 restart ---> to restart the MO Subrack=MS,Slot=14,PlugInUnit=1
bl 001900/sp0.lnh ---> to lock the spm
Subrack=MS,Slot=19,PlugInUnit=1,Spu=1,Spm=1
4) mo group
==> MO Groups are user defined groups of MOs. MO(s) belonging to the given MO group
will be operated upon.
MO groups can be created using the commands ma/lma and mr/lmr, as well as
hget/lhget, lk/llk, st/lst, pdiff/lpdiff.
See command description for these commands.
Note: In RNC, running the "bo" command will automatically create a number of MO
groups containing the cc/dc/pdr device MOs for each module.
5) board group
==> MOs (PlugInUnit or Spm) mapped onto the boards belonging to the given board
group will be operated upon.
Example1: baw sccp sccp ---> all boards with the swallocation matching "sccp"
will go into the board group "sccp"
bl sccp ---> all PlugInUnit or Spm MOs connected to boards of
this board group will be locked
Example2:In RNC, using the default board groups created after running the bo
command:
acc mod10 restart
pr dc10
acc dc10 restart (the board group dc10 is mapped onto the Spm MOs)
bl dc10dev (in this case we are using the MO group containing
the Device MOs, see paragraph 4. above)
6) mo-filter
==> MO(s) whose LDN/RDN match the pattern will be operated upon.
If the command starts with "l" then the pattern will match agains the LDN.
If the command doesn't start with "l", and the filter contains no commas, then the
pattern will match against the RDN.
If the command doesn't start with "l", and the filter contains commas, then the
pattern will match against the LDN but will not include the children.
Examples:
>> pr ms-24-1
returns: TransportNetwork=1,AtmPort=MS-24-1
>> lpr ms-24-1
returns: TransportNetwork=1,AtmPort=MS-24-1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc32
>> pr ms,slot=5,plug
returns: Equipment=1,Subrack=MS,PlugInUnit=1
>> lpr ms,slot=5,plug
returns: Equipment=1,Subrack=MS,PlugInUnit=1
Equipment=1,Subrack=MS,PlugInUnit=1,Program=basic
Equipment=1,Subrack=MS,PlugInUnit=1,Program=nss
Equipment=1,Subrack=MS,PlugInUnit=1,Programs=spas
....
When using the mo-filter, it is a good idea to test the pattern with "pr/lpr"
command before issuing a get/set/acc/cr/del command, in order to see which MOs will
be matched by the pattern.
Sometimes, a second or third argument can be given, which is usually a string

matching the attribute or attribute value that you want to display.
The search string that is used in the filters is a Unix Regular Expression (like
the patterns used in grep
command). Therefore, special meta-characters such as . * [ ] ^ $ can be used. Short
description of some
meta-characters:
"." --> any single character
"*" --> 0 or more occurences of the previous character
[] --> matches a character or range of characters inside the brackets
[^] --> NOT matching a character or range of characters inside the brackets
| --> OR
^ --> beginning of string
$ --> end of string
! --> negation
% --> reverse order
E.g: "a*" means a or aa or aaa, etc.
".*" is like a wildcard as it matches 0 or more occurences of any character
"[a-z]" matches all letters from a to z
"[abe]" matches letters a,b, and e
"[^3]" matches any character but not 3
3|5|6 matches 3 or 5 or 6
^a.*4$ matches a string beginning with a and finishing with 4, with any
character in the middle
Regular expressions can be grouped using brackets, e.g:
"cell(11|23|45) matches cell11 or cell23 or cell45
!!!! Note: MOSHELL pattern matching is NOT case sensitive !!!!!
Examples of using regular expressions in the filters:
lpr ms-24-1.*vp2
lpr %ms-24-1.*vp2
lpr !loadmodule|program
==> all MOs except those matching "loadmodule" or "program" will be printed.
lpr 20.*os
Equipment=1,Subrack=1,Slot=20,PlugInUnit=1,Etm4=1,Os155PhysPathTerm=1
Equipment=1,Subrack=1,Slot=20,PlugInUnit=1,Etm4=1,Os155PhysPathTerm=2
pr cc[1-4]
TransportNetwork=1,AtmCrossConnection=AtmCC1
pr cc[135]
lpr =6.*prog.*=1
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=15
lpr =6.*prog.*=1$
lpr ms-24-1
TransportNetwork=1,AtmPort=MS-24-1
lpr ms-24-1.*=vc[^3]
##################################################
3.3- How to specify attribute values in set/cr/acc commands
##################################################
a) For attributes of type Struct, use the following syntax:
attr1=val1[,attr2=val2[,attr3=val3]]]...
It is not necessary to specify all the struct members, only those that are required
to change can be specified.
Example:
>> set sid sib11 sib11repperiod=128
>> set mtp3bspitu sppriority prioslt=2
>> set mtp3bspitu sppriority prioslt=2,prioco=2
b) For attributes of type MoRef, just type the MO LDN (without

"ManagedElement=1"). Eg:
>> lset AtmPort=1221,VplTp=vp1 atmTrafficDescriptor
transportnetwork=1,atmtrafficdescriptor=C1P4500
It is also possible to skip the first parent (eg transportnetwork, swmanagement,
etc). Eg:
>> cr rncfunction=1,utrancell=30451,utranrelation=30451to30521
Attribute 1 of 1, utrancellref (moRef:UtranCell): utrancell=30521 #in this
case we don't have to specify rncfunction=1
c) For attributes of type array of MoRefs, separate each element of the array
with spaces. Eg:
>> set jvm admclasspath loadmodule=oms loadmodule=vbjorb loadmodule=asms_sharp
loadmodule=iaik loadmodule=cma loadmodule=roam
>> acc aal2pathdistributionunit=1 addPath
Parameter 1 of 1, aal2PathVccTpId (sequence-moRef-Aal2PathVccTp):
aal2pathvcctp=csa aal2pathvcctp=csb
d) For attributes of type array of Struct, separate each element of the array
with semicolons. Eg:
>> set rncfunction aliasPlmnIdentities
mcc=300,mnc=23,mnclength=2;mcc=345,mnc=32,mnclength=2;mcc=208,mnc=123,mnclength=3
e) For attributes of type array of integer/long/float/string/boolean, separate

each element of the array with commas or spaces. Eg:
>> set antfeedercable=6 ulattenuation 10,10,10,10,10,10,10,10,10
>> set antfeedercable=6 ulattenuation 10 10 10 10 10 10 10 10 10
>> set jvm options -Xms65000k,-Dhttp.root=/c/public_html,-
Dse.ericsson.security.PropertyFileLocation=/c/java/SecurityManagement.prp
>> set cell=3041 ActiveOverlaidCDMAChannelList true,true,false,true
>> set cell=3041 ActiveOverlaidCDMAChannelList true true false true
>> acc managedelementdata addDhcpServerAddress
Parameter 1 of 1, ipAddressArray (sequence-string): 10.1.1.3,10.1.1.4
e) For attributes of type array of integer, it is also possible to specify ranges

of values.
Eg, in the command below, the attribute will be set to 1,2,3,4,5,23,24,25,26
>> set IpInterface=1,DscpGroup=1 dscpValues 1-5,23-26
f) To input an empty value:

* in set command, just leave the value field blank. Eg:
>> set 0 userlabel (# attribute type is string)
>> set reliableprogramuniter admpassiveslot (#attribute type is MoRef)
* in cr command, type "null" or "d". This is only supported for non-
mandatory (restricted) attributes, because mandatory attributes must have a value
* in acc command, type "null". This is only supported for parameters of
type MoRef or String.
##################################################
3.4- Moshell command line
##################################################
The command line uses the Readline library from bash.
Here are some of the supported function keys:
- right arrow or Ctrl-f : move forward one character
- left arrow or Ctrl-b : move backward one character
- up arrow : previous command in history buffer
- down arrow : next command in history buffer
- backspace : delete one character backward
- Ctrl-d or <del> : delete one character forward
- Ctrl-a or <home> : go to beginning of line
- Ctrl-e or <end> : go to end of line
- Ctrl-u : erase all characters backward
- Ctrl-k : erase all characters forward
- Alt-f : move forward one word
- Alt-b : move backward one word
- select or select + ctrl-<insert> : copy to clipboard
- <insert> or shift-<insert> : paste from clipboard
Note about command history: if you type the beginning of a command and then use the
up/down arrow key, you will see all previous commands starting with this string
##################################################
3.5- Piping
##################################################
Some commands support piping, eg: OSE shell commands, lh, tg, str, etc.
This is usually indicated in the menu and the help for that command.
Examples:
>> te log read | grep ERROR
>> lh mp te log read | grep ERROR
>> str | grep cell=30456
For other commands that don't support piping (like MO commands), the workaround is
to save the output to a logfile then run the unix command on that logfile by using
the "l" or "!" command. Example:
>> l+ #open the logfile, an arbitrary name will be given
>> prod loadmodule #run the command
>> l- #close the logfile
>> l sort $logfile #run the unix command on the logfile. $logfile is a default
variable that stores the name of the latest log created
>> l grep -i basic $logfile

H 3

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

H 3

Hochgeladen von

Copyright:

Verfügbare Formate

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

3) link handler (for pluginunit and spm MOs only)

Sometimes, a second or third argument can be given, which is usually a string

!!!! Note: MOSHELL pattern matching is NOT case sensitive !!!!!

Examples of using regular expressions in the filters:

b) For attributes of type MoRef, just type the MO LDN (without

e) For attributes of type array of integer/long/float/string/boolean, separate

e) For attributes of type array of integer, it is also possible to specify ranges

f) To input an empty value:

Das könnte Ihnen auch gefallen