Untitled

************************************************************************************
***
pcr[cfpda]/lpcr[cfpda] <scannerName>
<moclass-filter>|<moinstance-filter>|<mo-group>|<counter-file> [<counter-filter>]
[<granularity>]
************************************************************************************
***
Create a statistics scanner.
Note: EVENT scanners are already created by default and shall be set with the "pset"
command.
The granularity field is optional and can be set to 300, 900, or 3600 seconds. By
default it will be set to 900 (15 minutes).
Options:
- c:
for activating counters on all MO classes matching the filter as well as all
their children/grandchildren, etc.
- f:
for adding counters even if they are already included in another scanner.
- p:
for creating a PREDEF scanner. By default a USERDEF scanner is created.
- d[a]: for debug. The syntax of "pcrd" is: pcrd/pcrda <counter-file>
where the format of the counter-file shall be as per below. The purpose of "pcrd" is
to test a counter file and identify any pm counters that are not supported by the
node SW.
With option "a" (pcrda), it is also possible to test which regular attributes can be
included in a scanner.
A negative filter (!) can be used on the moclass or counter filter in order to
exclude certain MOs or counters. See more info about regular expressions used in the
filters in chapter 3.2 of the README (or command "h syntax").
Note: for certain MO classes, the configuration attributes can be included in the
scanner. The user variable "include_nonpm" must be set to 1.
Example:
>> pcr atmport_vcltp atmport|vcltp
--> all counters are activated for all MOs of
class AtmPort and VclTp
>> pcr atmport_vcltp atmport=ms-6-1 received 300 --> Only the MO instances whose
RDN match "atmport=ms-6" are included. Only counters matching "received" will be
activated. The granularity period will 5 minutes (300 seconds).
>> lpcr vp1_vc100 atmport=ms-6-1,vptlp=1,.*vcltp=100 --> only the MO instances
whose LDN match "atmport=ms-6-1,vptlp=1,.*vcltp=100" are included.
>> pcr atmport atmportgroup
---> all counters are activated for all MO instances
found in the MO-group "atmportgroup"
>> pcr atmport_utrancell ~/mycounters.txt ---> all counters stored in the file
~/mycounters.txt are activated . See format of the counter file below.
>> pcrc all_transport transportnetwork --> all counters for all MO classes lying
under the TransportNetwork MO are activated.
>> pcrc all_transport_notMtp transportnetwork!mtp3 --> all counters for all MO
classes lying under the TransportNetwork except Mtp3 MOs are activated.
>> pcrc all_rnc_without_utranrel rncfunction!utranrelation|utrancell !rej ---> all
counters for all MOs lying under rncfunction except utranrelation and utrancell MOs
and not counters matching "rej"
>> pcrp myscanner atmport --> all counters in MO classes matching "atmport" are
included in the scanner PREDEF.myscanner.STATS
>> pcrp PRIMARY ~/primarycounters.txt --> all counters stored in the file
~/primarycounters.txt are included in the scanner PREDEF.PRIMARY.STATS
Notes:
* If certain counters are already defined in another scanner of that node, they will
be automatically excluded from the new scanner in order not to have duplicate lines
in the XML file. This can be bypassed by using the "f" option, eg: pcrf
atmport_vcltp atmport|vcltp (not recommended).
* By default, the counters that are marked as "deprecated" or "notInMOM" are not
Page 1

Untitled
included by the pcr command. This behaviour can be changed by setting the
uservariable "exclude_deprecated" to 0.
Format of the counter file:
**************************
The spaces at the beginning of the line are not necessary, they are just shown for
readability purposes.
To comment out some lines, just precede the line with a hash sign (#). Any words
after the first word are ignored.
Example:
AtmPort
pmReceivedAtmCells
pmSecondsWithUnexp
UtranCell
pmCellDowntimeAuto
pmCellDowntimeMan
pmChSwitchDch128Fach
pmChSwitchDch384Fach
pmChSwitchDch64Fach
It is also possible to take the printout from pmom as is. This will work as well and
saves having to do any editing.
#############################################
MO Class
Pm Counters
#############################################
UtranCell
296
pmCellDowntimeAuto
pmCellDowntimeMan
pmChSwitchDch128Fach
pmChSwitchDch384Fach
pmChSwitchDch64Fach
pmChSwitchFachDch
pmChSwitchFachIdle
It is also possible to use the following format for the counter file (for creating
counters on MO instances where each MO instance will use a different set of
counters).
Example:
ManagedElement=1,RncFunction=1,UtranCell=30124
pmRes1
pmRes2
ManagedElement=1,RncFunction=1,UtranCell=30125
pmRes3
ManagedElement=1,RncFunction=1,UtranCell=30126
pmRes2
pmRes4
It is also possible to take the printout of pgets as is. This is useful to clone an
existing scanner, eg with a different rop period.
Example:
l+
pgets <oldscanner>
lpbl <oldscanner>
pcrf <newscanner> $logfile . 300

Page 2