crontab – Scheduling moshell command


For Scheduling your task in Ericsson Moshell command, we can use crontab like in bash unix and combine with mobatch command.

connect your network, for see the list activated crontab with this script

Script: crontab -l
Result: 25 08 * * * /home/nw/ridho/test_crontab.sh>/home/nw/ridho/log
Explanation:
this crontab regulary run script test_crontab.sh every day in 08.25 and save the log /home/eadmwil/ridho/log
sample this sh test_crontab.sh is mobatch: /opt/../opt/ericsson/amos/moshell/mobatch -t 0 -p 40 ridho/IP_RBS_3G.txt “ylt all;rbs;rbs;cabx;rbs;rbs;q;”
we could see the mobacth with command cabx, for example for see the Digital unit Status every day without manually mobatch

Script: crontab -e
Explanation: this script for editing crontab or add new script in crontab list, for editing/adding line for this script we can use vi command like dd=delete line, dw=delete word, a=instert after, i=instert, :wq=save and quit

Script: crontab -r
Explanation: Remove all active crontab

the interesting fact how we make a schedule with this configuration

25 08 * * * = every day in 08.25
25 = minute(0-59)
08 = hour(0-23)
* = day_of_the_month (1-31)
* = month_of_the_year_(1-12)
* = day_of_the _week_(0-6 with 0=Sunday)

0 12,14,16 * * * = Run the script every day at 12:00, 14:00 and 16:00
30 13 * * 0 = Run the script every Sunday at 13:30
0 12,14,16 * * 6 = Run the script every Saturday at 12:00, 14:00 and 16:00.
0 0 1,15,20 * * = Run the script on the first, fifteenth and twentieth of every month
0 */3 * * * = Run the script every day from 3 to 3 hours: 00:00, 03:00, 06:00 etc.

this is full doc for crontab from oss ericsson

User Commands crontab(1)

NAME
crontab – user crontab file

SYNOPSIS
/usr/bin/crontab [filename]

/usr/bin/crontab -e [username]

/usr/bin/crontab -l [username]

/usr/bin/crontab -r [username]

/usr/xpg4/bin/crontab [filename]

/usr/xpg4/bin/crontab -e [username]

/usr/xpg4/bin/crontab -l [username]

/usr/xpg4/bin/crontab -r [username]

/usr/xpg6/bin/crontab [filename]

/usr/xpg6/bin/crontab -e [username]

/usr/xpg6/bin/crontab -l [username]

/usr/xpg6/bin/crontab -r [username]

DESCRIPTION
The crontab utility manages a user’s access with cron (see
cron(1M)) by copying, creating, listing, and removing cron-
tab files. If invoked without options, crontab copies the
specified file, or the standard input if no file is speci-
fied, into a directory that holds all users’ crontabs.

If crontab is invoked with filename, this overwrites an
existing crontab entry for the user that invokes it.

SunOS 5.10 Last change: 1 Mar 2011 1

User Commands crontab(1)

crontab Access Control
Users: Access to crontab is allowed:

o if the user’s name appears in
/etc/cron.d/cron.allow.

o if /etc/cron.d/cron.allow does not exist and the
user’s name is not in /etc/cron.d/cron.deny.

Users: Access to crontab is denied:

o if /etc/cron.d/cron.allow exists and the user’s
name is not in it.

o if /etc/cron.d/cron.allow does not exist and user’s
name is in /etc/cron.d/cron.deny.

o if neither file exists, only a user with the
solaris.jobs.user authorization is allowed to sub-
mit a job.

o if BSM audit is enabled, the user’s shell is not
audited and the user is not the crontab owner. This
can occur if the user logs in by way of a program,
such as some versions of SSH, which does not set
audit parameters.

The rules for allow and deny apply to root only if the
allow/deny files exist.

The allow/deny files consist of one user name per line.

crontab Entry Format
A crontab file consists of lines of six fields each. The
fields are separated by spaces or tabs. The first five are
integer patterns that specify the following:

minute (0-59),
hour (0-23),
day of the month (1-31),
month of the year (1-12),
day of the week (0-6 with 0=Sunday).

Each of these patterns can be either an asterisk (meaning
all legal values) or a list of elements separated by commas.
An element is either a number or two numbers separated by a

SunOS 5.10 Last change: 1 Mar 2011 2

User Commands crontab(1)

minus sign (meaning an inclusive range). Time specified here
is interpreted in the timezone of the cron(1M) daemon, which
is set system-wide in /etc/default/init. Entries do not use
the invoking user’s timezone. The specification of days can
be made by two fields (day of the month and day of the
week). Both are adhered to if specified as a list of ele-
ments. See EXAMPLES.

The sixth field of a line in a crontab file is a string that
is executed by the shell at the specified times. A percent
character in this field (unless escaped by \) is translated
to a NEWLINE character.

Only the first line (up to a `%’ or end of line) of the com-
mand field is executed by the shell. Other lines are made
available to the command as standard input. Any blank line
or line beginning with a `#’ is a comment and is ignored.

The shell is invoked from your $HOME directory with an arg0
of sh. Users who desire to have their .profile executed must
explicitly do so in the crontab file. cron supplies a
default environment for every shell, defining HOME, LOGNAME,
SHELL(=/bin/sh), TZ, and PATH. The default PATH for user
cron jobs is /usr/bin; while root cron jobs default to
/usr/sbin:/usr/bin. The default PATH can be set in
/etc/default/cron (see cron(1M)).

If you do not redirect the standard output and standard
error of your commands, any generated output or errors are
mailed to you.

Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide
timezone for cron entries. This, in turn, is by set by
default system-wide using /etc/default/init.

If some form of daylight savings or summer/winter time is in
effect, then jobs scheduled during the switchover period
could be executed once, twice, or not at all.

OPTIONS
The following options are supported:

-e Edits a copy of the current user’s crontab file, or
creates an empty file to edit if crontab does not
exist. When editing is complete, the file is installed
as the user’s crontab file.

SunOS 5.10 Last change: 1 Mar 2011 3

User Commands crontab(1)

The environment variable EDITOR determines which edi-
tor is invoked with the -e option. All crontab jobs
should be submitted using crontab. Do not add jobs by
just editing the crontab file, because cron is not
aware of changes made this way.

If all lines in the crontab file are deleted, the old
crontab file is restored. The correct way to delete
all lines is to remove the crontab file using the -r
option.

If username is specified, the specified user’s crontab
file is edited, rather than the current user’s crontab
file. This can only be done by root or by a user with
the solaris.jobs.admin authorization.

-l Lists the crontab file for the invoking user. Only
root or a user with the solaris.jobs.admin authoriza-
tion can specify a username following the -l option to
list the crontab file of the specified user.

-r Removes a user’s crontab from the crontab directory.
Only root or a user with the solaris.jobs.admin
authorization can specify a username following the -r
option to remove the crontab file of the specified
user.

EXAMPLES
Example 1 Cleaning up Core Files

This example cleans up core files every weekday morning at
3:15 am:

15 3 * * 1-5 find $HOME -name core 2>/dev/null | xargs rm-f

Example 2 Mailing a Birthday Greeting

This example mails a birthday greeting:

0 12 14 2 * mailx john%Happy Birthday!%Time for lunch.

SunOS 5.10 Last change: 1 Mar 2011 4

User Commands crontab(1)

Example 3 Specifying Days of the Month and Week

This example runs a command on the first and fifteenth of
each month, as well as on every Monday:

0 0 1,15 * 1

To specify days by only one field, the other field should be
set to *. For example:

0 0 * * 1

would run a command only on Mondays.

ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that affect the execution of crontab: LANG,
LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.

/usr/bin/crontab
EDITOR Determine the editor to be invoked when the -e
option is specified. This is overridden by the
VISUAL environmental variable. The default editor
is ed(1).

PATH The search path used to find the default ed util-
ity.

VISUAL Determine the visual editor to be invoked when the
-e option is specified. If VISUAL is not speci-
fied, then the environment variable EDITOR is
used. If that is not set, the default is ed(1).

/usr/xpg4/bin/crontab
EDITOR Determine the editor to be invoked when the -e
option is specified. The default editor is
/usr/xpg4/bin/vi(1).

SunOS 5.10 Last change: 1 Mar 2011 5

User Commands crontab(1)

/usr/xpg6/bin/crontab
EDITOR Determine the editor to be invoked when the -e
option is specified. The default editor is
/usr/xpg6/bin/vi(1).

EXIT STATUS
The following exit values are returned:

0 Successful completion.

>0 An error occurred.

FILES
/etc/cron.d main cron directory

/etc/cron.d/cron.allow list of allowed users

/etc/default/cron contains cron default settings

/etc/cron.d/cron.deny list of denied users

/var/cron/log accounting information

/var/spool/cron/crontabs spool area for crontab

ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:

/usr/bin/crontab
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWcsu |
|_____________________________|_____________________________|
| Interface Stability | Standard |
|_____________________________|_____________________________|

/usr/xpg4/bin/crontab

SunOS 5.10 Last change: 1 Mar 2011 6

User Commands crontab(1)

____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWxcu4 |
|_____________________________|_____________________________|
| Interface Stability | Standard |
|_____________________________|_____________________________|

/usr/xpg6/bin/crontab
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWxcu6 |
|_____________________________|_____________________________|
| Interface Stability | Standard |
|_____________________________|_____________________________|

SEE ALSO
atq(1), atrm(1), auths(1), ed(1), sh(1), vi(1), cron(1M),
su(1M), auth_attr(4), attributes(5), environ(5), stan-
dards(5)

NOTES
If you inadvertently enter the crontab command with no argu-
ments, do not attempt to get out with Control-d. This
removes all entries in your crontab file. Instead, exit with
Control-c.

When updating cron, check first for existing crontab entries
that can be scheduled close to the time of the update. Such
entries can be lost if the update process completes after
the scheduled event. This can happen because, when cron is
notified by crontab to update the internal view of a user’s
crontab file, it first removes the user’s existing internal
crontab and any internal scheduled events. Then it reads the
new crontab file and rebuilds the internal crontab and
events. This last step takes time, especially with a large
crontab file, and can complete after an existing crontab
entry is scheduled to run if it is scheduled too close to
the update. To be safe, start a new job at least 60 seconds
after the current date and time.

Simultaneous modifications of the same crontab file may lead
to unexpected results.

LTE TDD Uplink-downlink configurations


when your network has LTE tdd, the basic configuration is UL-DL Configuration which explained in 3gpp 36.211 need to be configured

Table 4.2-2: Uplink-downlink configurations

Uplink-downlink

configuration

Downlink-to-Uplink

Switch-point periodicity

Subframe number
0 1 2 3 4 5 6 7 8 9
0 5 ms D S U U U D S U U U
1 5 ms D S U U D D S U U D
2 5 ms D S U D D D S U D D
3 10 ms D S U U U D D D D D
4 10 ms D S U U D D D D D D
5 10 ms D S U D D D D D D D
6 5 ms D S U U U D S U U D

D = Downlink
U = Uplink
S = Special Subframe

if your network has multiple cells TDD you should configure same UL-DL configuration, you can’t configure with different configure because if subframe in cell on downlink, this rules also in subframe uplink

how to see on your network, example  Ericsson (moshell) and Huawei (u2000)

Ericsson: MO: EutranCellTDD attribute: subframeassigment

2019-02-22 09_34_58-Window

2019-02-22 09_37_31-Window

Huawei: MO: CELL , Parameter: Subframe Assignment

2019-02-22 09_40_03-Window

2019-02-22 09_43_12-Window

not only Subframe Assignment we have to configure also special subframe for configure Downlink part time slot, guard period, and Uplink Part time slot

Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS)

2019-02-22 10_09_56-Window

Ericsson: MO: EutranCellTDD attribute: specialSubframePattern

2019-02-22 10_11_00-Window

Huawei: MO: CELL , Parameter: Special subframe patterns

2019-02-22 09_40_03-Window

in our network using Uplink-downlink configurations 2 and special subframe 7 with Normal CP. See 3GPP table again, we can calculate this:

UL-DL Config 2 => D:L = 3:1 with 2 Special Subframe

How many DwPTS UpPTS and GP?

2019-02-22 15_18_08-Window

DwPTS = 21952*Ts
UpPTS 4384*Ts

1 Radio Frame = 10ms = 307200Ts
1 Subframe = 1ms = 30720Ts

DwPTS+UpPTS+GP= 1 Subframe = 30720Ts
2192Ts+4384Ts+GP = 30720Ts
GP = 4384Ts

DwPTS ~ 5*GP ~ 5UpPTS, which means 10 Symbol will be allocated for DwPTS + 2 Symbol for GP + 2 Symbol for UpPTS on one special subframe

 

MoShell Command Counter + KPI


Beberapa command dari variasi pmx dan pmr
pmx => untuk menquery nilai counter
pmxh => sama dengan pmx namun ditampilkan dalam bentuk horizontal
pmxe => untuk menquery nilai KPI based on formula yang telah di definisikan
pmxl => untuk menquerynilai counter dan di export dalam bentuk report excell
pmr => untuk menquery KPI based on Reporting yang telah di definisikan
pmrw => untuk menquery KPI based on Reporting yang telah di definisikan dan direportkan dalam bentuk web report

pmx option yang biasa digunakan adalah sebagai berikut:
-tz => menyesuaikan time zone, biasanya di indonesia +7 (-tz 7)
-m => waktu hour yang kita akan query (-m 3 artinya 3 jam akan diambil)
-h => pada dasarnya counter pmx based on rop (15 menit) kalah di option -h maka setiap 4 rop (1 jam) akan diakumulasikan
-a => aggregation semua -m akan di aggregasi menjadi satu value]
| => digunakan untuk mengambil lebih dari satu counter, bisa juga digunakan untuk cellid (rbs003w1|rbs003w2)

Berikut tips and trick penggunaan function diatas:

untuk query drop dari channel PS, URA, HS dalam waktu 2 jam
RNC> pmx cellid pmNoSystemRabReleasePacket|pmNoSystemRabReleasePacketUra|pmNoSystemRbReleaseHs -m 2 -tz 7
hasil:
Date: 2017-10-04
Object Counter 07:00 07:15 07:30 07:45 08:00 08:15 08:30 08:45
UtranCell=cellid pmNoSystemRabReleasePacket 16 7 7 6 10 12 6 11

query rejection yang ada di 3G dalam waktu 3 jam dan diaggregasikan dalam jam/hour
RNC> pmx cellid failedafteradm|pmNoRrcReqDeniedAdmDlChnlCode|pmNoRrcReqDeniedAdmDlHw|pmNoRrcReqDeniedAdmDlPwr|pmNoRrcReqDeniedAdmUlHw|pmNoOfNonHoReqDeniedHs|pmNoServingCellReqDeniedEul|pmNoOfNonHoReqDeniedEul -m 3 -tz 7 -h

Date: 2017-10-03
Object Counter 21:00 22:00 23:00
UtranCell=cellid pmNoFailedAfterAdm 3 1 2
UtranCell=cellid pmNoOfNonHoReqDeniedEul 0 0 0
UtranCell=cellid pmNoOfNonHoReqDeniedHs 0 0 0
UtranCell=cellid pmNoRrcReqDeniedAdmDlChnlCode 0 0 0
UtranCell=cellid pmNoRrcReqDeniedAdmDlHw 0 0 0
UtranCell=cellid pmNoRrcReqDeniedAdmDlPwr 0 0 0
UtranCell=cellid pmNoRrcReqDeniedAdmUlHw 0 0 0
UtranCell=cellid pmNoServingCellReqDeniedEul 0 0 0
UtranCell=cellid pmNoServingCellReqDeniedEulTti2 0 0 0

setelah contoh pmx diatas, sekarang kita mencoba untuk pmxe yang digunakan untuk mengenerate KPI:

Contoh:kita akan mengenerate accessibility dan availability dalam waktu 3 jam dan dibagi per ROP
RNC> pmxe cellid HsAccess$|SpchAccess$|EULAcces$|PSAccess$|availability$ -m 4 -tz 7
Date: 2017-10-04
Object Counter 05:00 05:15 05:30 05:45 06:00 06:15 06:30 06:45 07:00 07:15 07:30 07:45
UtranCell=cellid Availability 100 100 100 100 100 100 100 100 100 100 100 100
UtranCell=cellid HsAccess 100 98.9 99.3 100 99.7 99.4 98.0 98.2 97.5 98.6 99.3 98.4
UtranCell=cellid PSAccess 100 98.9 99.3 100 99.7 99.4 98.0 98.2 97.5 98.6 99.3 98.4
UtranCell=cellid SpchAccess N/A N/A N/A N/A 100 100 100 100 93.8 100 100 100

bagaimana dengan formula yang digunakan?, kita bisa cek di saat kita merunning command tersebut. contoh /opt/../opt/ericsson/amos/moshell/commonjars/pm/FORMULA_RNC_N_1_360.txt

didalam formula text tersebut berisi formula sbb:
HsAccess = ( 100 * pmTotNoRrcConnectReqPsSucc / ( pmTotNoRrcConnectReqPs – pmNoLoadSharingRrcConnPs ) ) * ( 100 * pmNoRabEstablishSuccessPacketInteractiveHs / pmNoRabEstablishAttemptPacketInteractiveHs ) * ( 100 * pmNoNormalNasSignReleasePs / ( pmNoNormalNasSignReleasePs + pmNoSystemNasSignReleasePs ) ) / 10000
PSAccess = ( 100 * pmTotNoRrcConnectReqPsSucc / ( pmTotNoRrcConnectReqPs – pmNoLoadSharingRrcConnPs ) ) * ( 100 * pmNoRabEstablishSuccessPacketInteractive / pmNoRabEstablishAttemptPacketInteractive ) * ( 100 * pmNoNormalNasSignReleasePs / ( pmNoNormalNasSignReleasePs + pmNoSystemNasSignReleasePs ) ) / 10000
SpchAccess = ( 100 * pmTotNoRrcConnectReqCsSucc / ( pmTotNoRrcConnectReqCs – pmNoLoadSharingRrcConnCs ) ) * ( 100 * pmNoRabEstablishSuccessSpeech / pmNoRabEstablishAttemptSpeech ) * ( 100 * pmNoNormalNasSignReleaseCs / ( pmNoNormalNasSignReleaseCs + pmNoSystemNasSignReleaseCs ) ) / 10000
Availability = 100 * ( 3600 – ( pmCellDowntimeAuto + pmCellDowntimeMan ) ) / 3600

bagaimana jika formula tersebut tidak sesuai dengan standart yang kita punya, kita bisa menggunakan formula kita sendiri dan kita simpan di folder moshell kita dan menambahkan -f lokasiformula

pmxe TTN297W HsAccessNew$|PSAccessNew$ -m 4 -tz 7 -f /home/username/ridho/FORMULA_RNC_ridh.txt

sekarang kita coba lebih advance lagi untuk menambahan script unix sort and head. case ini sangat berguna misal didalam satu RNC kita mempunyai 1000 cell, dalam kurun waktu 4 jam kita ingin mencari 10 cell mana yang memiliki masalah dalam 1 jam terakhir. Script ini sangat berguna untuk contoh pmNoFailedAfterAdm memiliki nilai besar biasanya ada transport issue
sort => untuk nge-sort dari nilai terbesar sampai terkecil atau sebaliknya
head => untuk mengambil top n line
contoh:
kita ingin mengambil 15 contributor cell yang memiliki failafteradm yang tinggi di 1 jam terakhir tambahkan script berikut
=> (sort -k6 -n -r => untuk meng-sort dari kolom keenam)
=> (head -15 ==> untuk mengambil 15 top)
RNC> pmx UtranCell=.* failedafteradm -m 4 -tz 7 -h | sort -k6 -n -r | head -15

Report from 2017-10-03 22:15 UTC to 2017-10-04 02:14 UTC (16 ropfiles)
Node SW: CXP9021776/4_R4YB04 (W15B)
UtranCell=XXX042W2 pmNoFailedAfterAdm 78 41 9 26 34
UtranCell=XXX304W1 pmNoFailedAfterAdm 0 1 3 44 33
UtranCell=XXX885W3 pmNoFailedAfterAdm 5 29 28 83 20
UtranCell=XXX967W1 pmNoFailedAfterAdm 13 39 37 66 16
UtranCell=XXX702W2 pmNoFailedAfterAdm 3 7 14 36 15
UtranCell=XXX351W1 pmNoFailedAfterAdm 0 2 2 6 14
UtranCell=XXX311W6 pmNoFailedAfterAdm 6 6 14 48 14
UtranCell=XXX508MA2 pmNoFailedAfterAdm 3 23 25 25 14
UtranCell=XXX042W5 pmNoFailedAfterAdm 11 16 6 19 14
UtranCell=XXX002W9 pmNoFailedAfterAdm 1 2 5 10 14
UtranCell=XXX516MA2 pmNoFailedAfterAdm 2 10 22 30 13
UtranCell=XXX365W3 pmNoFailedAfterAdm 13 23 26 38 11
UtranCell=XXX933W3 pmNoFailedAfterAdm 4 20 9 9 11
UtranCell=XXX730MA2 pmNoFailedAfterAdm 2 5 14 12 11
UtranCell=XXX508MA1 pmNoFailedAfterAdm 20 54 29 69 11

Note: untuk sort dan head diatas, masih belum ketemu cara exclude time ROP nya agar ngak ikut di sort, tetapi tidak merubah result analisa secara keseluruhan

kita coba satu case lagi untuk pmx, misal kita ingin mencari NodeB yang flicker, flicker ya bukan down. counter yang kita pakai pmCellDowntimeAuto yang menunjukan nodeB outage yang bukan di locked. Jika nodeB itu outage full 1 jam (60 menit) maka pmCellDowntimeAuto akan bernilai 3600 (pmCellDowntimeAuto satuannya second). jadi kita ingin menexclude node B yang down selama 1 jam dan menampilkan RBS yang memiliki downtime flicker. Script ini sangat berguna untuk memonitor nodeB yang flicker due to Transport problem
RNC> pmx . pmCellDowntimeAuto -m 12 -tz 7 -h | sed -e ‘s/3600/Mati/g’ | sort -rk14 | head -40 | grep -v “Mati”

Object Counter 00:00 01:00 02:00 03:00 04:00 05:00 06:00 07:00 08:00 09:00 10:00 11:00 12:00
UtranCell=XXX516W9 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W8 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W7 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W6 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W5 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W4 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W3 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W2 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX516W1 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1558 1090 0
UtranCell=XXX506W9 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W8 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W7 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W6 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W5 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W4 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W3 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W2 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX506W1 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 0 0 1556 863 0
UtranCell=XXX605W9 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 1632 0 1558 859 0
UtranCell=XXX605W8 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 1632 0 1558 859 0
UtranCell=XXX605W7 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 1632 0 1558 859 0
UtranCell=XXX605W6 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 1632 0 1558 859 0
UtranCell=XXX605W5 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 1632 0 1558 859 0
UtranCell=XXX605W4 pmCellDowntimeAuto 0 0 0 0 0 0 0 0 1632 0 1558 859 0

Berkikut beberapa script yang mungkin berguna khusus nya untuk monitoring performance

//query contributor rejection due to, sort and head
RNC> pmxe UtranCell=.* DlConnLimit$|DlAse$|DlChnlCode$|DlHw$|DlHwBest$|DDlPwr$ -m 6 -tz 7 -h | sort -nrk9 | head -40
//query contributor fail due to, sort and head
RNC> pmxe UtranCell=.* Fail$ -m 6 -tz 7 -h | sort -nrk9 | head -40
//query KPI accessability, sort and head
RNC> pmxe UtranCell=.* HsAccess$|EULAcces$|PSAccess$ -m 6 -tz 7 -h | sort -k9 | head -40
//query KPI Drop, sort and head
RNC> pmxe UtranCell=.* CS64Drop$|SpchDrop$|CS57Drop$|PSDrop$|HsDrop$ -m 6 -tz 7 -h | sort -rk8 | head -40
//query afteradm, sort and head
RNC> pmx UtranCell=.* failedafteradm -m 4 -tz 7 | sort -k17 -n -r | head -15
//query Rejection license EUL, sort and head
RNC> pmx UtranCell=.* pmNoOfNonHoReqDeniedEul -m 4 -tz 7 | sort -k18 -n -r |head -30
//query Rejection Code, HW, Pwr, License HS, sort and head
RNC> pmx UtranCell=.* pmNoRrcReqDeniedAdmDlChnlCode|pmNoRrcReqDeniedAdmDlHw|pmNoRrcReqDeniedAdmDlPwr|pmNoRrcReqDeniedAdmUlHw|pmNoOfNonHoReqDeniedHs -m 4 -tz 7 | sort -k18 -n -r |head -30
//query RBS Flicker
RNC> pmx . pmCellDowntimeAuto -m 12 -tz 7 -h | sed -e ‘s/3600/Mati/g’ | sort -rk14 | head -40 | grep -v “Mati”
//ini buat liat attempt hand over
RNC> pmxh UtranCell pmrladd.*bestcellspeec -m 48 -tz 7 -a
//query speech drop
RNC> pmx cellid pmNoSysRelSpeechNeighbr|pmNoSystemRabReleaseSpeech -m 4 -tz 7

//check frame lost
RBS> pmxl . pmHsData -m 48 -tz 7
RBS> pmx . pmHsData -m 4 -tz 7

Untuk yang pmr dan yg 4G, next kita bahas kembali

MoShell Command (Troubleshooting)


Berikut Moshell Command yang biasa digunakan untuk troubleshooting RBS Ericsson

Site3G> lt all (load all)
Site3G> alt (cek alarm)
Site3G> lge
Site3G> lga 1d (alarm 1hari)
Site3G> lgo (perubahan database)
Site3G> lgn (perubahan database & user)
Site3G> cabx (cek RBS)
Site3G> invhl (cek inventory)
Site3G> cvls (cek activity RBS)
Site3G> cvms ….. (create CV)
Site3G> lst host
Site3G> lst carr
Site3G> lst iub
Site3G> get . antennasupervision (cek antena supervise)
Site3G> set . antennaSupervisionThreshold 80

cek TA/ TP (Timing Advance)
Site3G> pmx prach pmpropagationdelay -m 48 -a
Site3G> pmx . pmPrachPropagationDelay -m 48 -a ==> ngecek prach di base band 3G

Site3G> hget radio no –> cek traffic
Site3G> st ru –> cek status RU
Site3G> pmr –> cek RSSI
Site3G> hget sector long|lat –>cek longlat
Site3G> get node chann

Site3G> get . txmaxdl
Site3G> get . maxdl
Site3G> get . maxtot (cek maxTotalOutputPower)
Site3G> set . maxTotalOutputPower 80
Site3G> get . maxtot
Site3G> st plugin –> cek status RU/cari proxy brp yg mau direstart
Site3G> acl (proxy)80 (restart per modul)
Site3G> acc 80 manualrestart -> y ->2 (coldrestart) ->6 ->0

Site3G> st plug
Site3G> acl 189
Site3G> acc 189 restartAuxUnit (reset RU)
Site3G> y

cek konfigurasi DUW/RRU
Site3G> get . dbcc

restart RBS
================
Site3G> acc 0 manualrestart
Site3G> y
Site3G> 3
Site3G> 6
Site3G> 0
Site3G> lt all

restart restartAuxUnit
Site3G> acl (proxy)
Site3G> acc (proxy) restartAuxUnit -> y

Site3G> st plug
Site3G> acl 357
Site3G> acc 357 restartauxunit -> y