You are on page 1of 9

M-MGw Health Check

1 PURPOSE.....................................................................................................2
2 M-MGw health check with MoShell................................................................3
2.1 M-MGw time................................................................................................3
2.2 Print alarms.................................................................................................3
2.3 Print boards.................................................................................................3
2.4 M-MGw CV and software.............................................................................3
2.5 Alarm List.....................................................................................................3
2.6 Alarm, Event, Availability and System log....................................................3
2.7 Board related...............................................................................................4
2.8 Trace & Error logs .......................................................................................4
2.9 Status of the plug-in units............................................................................4
2.10 VMGw status.............................................................................................4
2.11 MTP3b protocol status...............................................................................4
2.12 TDM termination .......................................................................................5
2.13 Device pools .............................................................................................5
2.14 AAL2 path .................................................................................................5
2.15 Performance Measurement (PM)...............................................................5
2.16 M-MGw capacity vs. license......................................................................6
2.17 M-MGw traces to default settings...............................................................6
2.18 M-MGw health check command file...........................................................6
2.19 Automatic health check function................................................................7
3 MGw health check with GUI..........................................................................7
3.1 MGw health check with NM.........................................................................7
3.2 MGw health check with EM..........................................................................8
4 Abbreviations.................................................................................................9

PURPOSE
The purpose of this document is to establish what information is required when
making a health check on M-MGw. This health check document can for
example be used when monitoring an MGw or for statistic gathering, before
and after a SW Upgrade.

M-MGw health check with MoShell


All the commands in this chapter should be executed when making a health
check on the MGw. In some cases all commands will not be applicable, due to
MGw network configuration. The output from the commands should be logged
a file and analyzed.

2.1

M-MGw time
> readclock

2.2

Print alarms
Al

2.3

Print boards
>cab or cabx
Prints boards per subrack, includes subrack number and board number.

Also LEDs for boards and product number and revision.

2.4

M-MGw CV and software


Check the current CV and software level in use in the MGw.
> cvcu
Check the amount off CV on the node
> cvls

2.5

Alarm List
Prints the active and acknowledged alarms with timestamps
> altk

2.6

Alarm, Event, Availability and System log


Prints alarm, event, availability and system logs for the last 24 hours
> lgaevsrm 24h
List error log
> llog l

2.7

Board related

List loaded modules.


>lhsh 001000 listloaded
Print all load modules on that board.
>lhsh 001000 pglist
Print active processes on board and load module number.
>lhsh 001000 sma all

2.8

Trace & Error logs


Look for errors in the Trace & Error logs from all boards.
> all err

2.9

Status of the plug-in units


Prints all plug-in units status, disk space, CPU load, restarts and errors.
> cabxlradg

2.10

VMGw status
Prints the operationalState for the VMGw.
> st vmgw
Prints the VMGw GCP-profile info.
> get vmgw profile
Verify that the correct GCP-profile is in use.
The correct profiles to be used are:
M-MGw R3 & R4
Ericsson_FAY11232_2/1
M-MGw R4
Ericsson_FAY112145_1/1
M-MGw R4 & R5
Ericsson_FAY112163_1/1
M-MGw R5
Ericsson_FAY112165_1/1

2.11

(EP1)
(EP2)
(EP5)
(EP6)

MTP3b protocol status


Prints the operationalState for the MTP3b protocol managed objects.
> st mtp3bs

2.12

TDM termination
Prints the operationalState for the TDM terminations.
> st tdmterm

2.13

Device pools
Prints the status of the device pools.
> std

2.14

AAL2 path
Prints the operationalState for the AAL2 paths.
> hget aal2pathv state

2.15

Performance Measurement (PM)

2.15.1

PM counters to check for Node statistics


The following PM:s should be checked to get some basic node statistics.
> pget vmgw
> hpget tdmterm
> pget mtp3b
If Sigtran/IP is used:
> pget m3ua
> pget sctp
> pget ipacc

2.15.2

Printing the disturbance counters


Use below command to print all PM counters related to disturbances. Check
there is no counters stepping too often.
> pget all forced|fail|unsucc|rej|rele|err|overflow|down|unavail|lost|missing !^0|-1
Wait a while and then give the above command again and compare the first
and second print to see if there are any counters that are increasing.
In case the above pget command print out will be too large i.e. too much info, it
is possible to narrow down the command to include only failed, unsuccessful
and rejected counters.
> pget all fail|unsucc|rej !^0|-1

To verify if the counter stepping is normal or abnormal, read the Alex CPI
document User Guide for Performance Measurements. In case of abnormal
behavior, give the following command for further analysis.
> pget < mo name>
2.15.3

PM to OSS-RC
Prints the active scanners in the M-MGw.
> pgets

2.16

M-MGw capacity vs. license


Check the current level of calls vs. the M-MGw license.
Print the licensed maximum amount of channels
> get mgwapplication maxNrOfLicMediaStreamChannels
Print the currently active channels
> pget mgwapplication
//parameter pmNrOfMediaStreamChannelsBusy for active channels
//parameter pmNrOfMediaStreamChannelsRejectedDueToCapacity for
capacity overload counter
Prints all the enabled features
> all fro_lici_data_list

2.17

M-MGw traces to default settings


The Trace & Error log settings should be in default level when there is no need
for further trouble shooting. Extra traces can cause excess CPU load for the
particular board. Use below MoShell command to restore the default traces.
> all te default

2.18

//Set default traces to every board in the node.

M-MGw health check command file


Here is a command file for printing all the commands in this health check
document.

health_check.txt

The command file can be either copy/pasted into MoShell or alternatively


executed with the command run <path>\health_check.txt

2.19

Automatic health check function


There is a MoShell command hc for collecting a health check for the M-MGw.
There is lot of data included in this log file e.g. alarms, te logs, event logs,
different protocol and equipment status info. With the hc command, all the
basic info is received from the node. The health check can be taken to store
the node state for further analysis.
NOTE:

This command may take a long time to execute.

MGw health check with GUI

3.1

MGw health check with NM

3.1.1

Check SW level

3.1.2

Board status
In the Startup View choose Cabinet View there you can see the operational
state for all boards and the MACU unit.

3.1.3

Download logs from MGw


From the Tools menu choose File List. To download the log files right click
on the log type and choose Download.
The following logs/files should be downloaded:
- License Key File
- Security Log
- Audit Trail Log (Shell)
- Audit Trail Log (CORBA)
- Availability Log
- Alarm Log
- Event Log

3.1.4

Locked and Disabled MOs


From the Search menu view the For Disabled MOs and For Locked MOs.
These will search for all Disabled/Locked MOs in the node and list them.

3.1.5

General Health check with NM


In the Startup View chooseResource View.
From here the following should be checked visually:
- Status of the Message Transfer Part (MTP) links.
- Status of the Virtual Media Gateways (VMGws).
- Status of the TDM Termination Groups.

- Status of the Device Pools.


- Status of the Aal2paths
- Status of the Interactive Messages

3.2

MGw health check with EM.

3.2.1

Check SW level
Select Software folder, click upgrade package and check package state.
The current package state should be Yes.

3.2.2

Check alarm and event


Select Configurationfolder, Click Alarm and Event to check related alarms
and event messages.

3.2.3

General Health check with EM


The following should be checked visually
- Status of the Message Transfer Part (MTP) links.
- Status of the Virtual Media Gateways (VMGws).
- Status of the TDM Termination Groups.
- Status of the Device Pools.
- Status of the Aal2paths
- Status of the Interactive Messages
- Status of the Plug-In Units

Abbreviations

AAL2
CV
EM
GCP
GPB
GUI
M-MGw
MO
MTP3b
NM
OSS-RC
TDM
VMGw

ATM Adaptation Layer Type 2


Configuration Version
Element Manager
Gateway Control Protocol
General Processing Board
Graphical User Interface
Mobile Media Gateway
Manage Object
Message Transfer Part layer 3
Node Manager
Operations Support System, Radio and
Core network
Time Division Multiplexing
Virtual Media Gateway