You are on page 1of 8

1.1 Check for any alarms and events 1.1.1 Connect to Mgw using EMAS.

Click on TAB Alarm => Alarm List. Look for any relevant alarms. 1.1.2 FTP to Mgw and download the alarm log to local PC $ ftp < i.p. address > $ bin $ hash $ cd /c/log files/cello $ get CELLO_ALARM_LOG.xml $ bye This file can be decoded using standard xml decoders. 1.2 Check the status of all plug-in units Connect to Mgw through EMAS Select Equipment folder Check that every plug-in unit state should be Enabled . 1.3 Check Status of Signaling Links 1. In the Element Manager SS7 view, expand the folder MTP3b Signaling Points. The current Signalling Points are displayed. 2. Expand the relevant folder MTP3b Signalling Point. 3. Click on the folder MTP3b Signalling Link Sets. The Status of all Link sets can be seen here. 4. Select the Attribute folder and click on Refresh to verify the present states of MTP3b Signalling Links. 1.4 Check the status of M3UA Associations 1. In the Element Manager SS7 view, expand the folder MTP3b Signaling Points. The current Signalling Points are displayed. 2. Expand the relevant folder MTP3b Signalling Point. 3. Expand the folder M3U Association. The Signalling associations are displayed. 4. Select the Attribute folder and click on Refresh to verify the present states of MTP3b Signalling Links. 1.5 Check tdmTermGrp status In Element Manager, select TDM Termination Groups view from drop-down list and verify that no TDM Termination is in disabled state. 1.6 Check Board LED status $ vii 1.7 Check FAN Board status

$ fan_vii 1.8 Check clock status $ readclock 1.9 Check which O&M GPB is active $ mirror stat This command goes to GPB 000200, so if status here shows Passive, it means that GPB 000200 is passive. So Other GPB 000300 should be active. Alternatively that can be checked using: $ lhsh 000300 000300>mirror stat 1.10 Check loadmodules RPU state $ sma all 1.11 Look for any errors on the board $ llog $ llog -l Look for any recent board restarts or corresponding errors. 1.12 Keep a printout of trace and error log $ te log read Look for errors in trace and error logs from all boards: all te log read | grep i error 1.13 Check Processor Load $ capi tot 1.14 Verify Disk Space on main GPB board Check all GPB board /c/ and /d/ free space with command: $ vols Free space for d/ partition should be at least 30%. 1.15 Check for any GCP errors Access MESC controlling GPB board. For example, in GMPV3 GPB board position 0102 00 and 010300 are controlling GPBs.

$ lhsh 010200 On the following prompt, give command 010200>mesc_counters_gcp all These counters a accumulative, so taking this command twice and looking at the d ifference in values of the latest printout from previous one, exact cause of pro blem in GVP can be found. 1.16 Look for any hanging contexts Access MESC controlling GPB board. For example, in GMPV3 GPB board position 0102 00 and 010300 are controlling GPBs. $ lhsh 010200 On the following prompt, give command 010200> mesc_info_ctx -alive 7200 defer 010200> mesc_info_ctx errors This will list all contexts active for more than 2 hours. Check the same in boar d 010300 / 650200 /650300 as well. 1.17 Check status of Vmgw $ st Vmgw $ get Vmgw profile ! Check if correct profile is loaded ! $ lhsh 001000 ch_info_vmgw $ lhsh 001100 ch_info_vmgw VMGw associated with CH0 will be visible in 001000 & VMGw associated with CH1 wi ll be visible in 001100 . 1.18 Check Vmgw counters for any ambiguities Access MESC controlling GPB board. For example, in GMPV3 GPB board position 0102 00 and 010300 are controlling GPBs. $ lhsh 010200 On the following prompt, give command 010200> mesc_info_vmgw all Also look for any Hanging Moves in a Vmgw. Use following command: 010200> mesc_info_vmgw all moveHangPrint There should be no hanging move terminations present. Check the same in board 010300 / 650200 /650300 as well. 1.19 Check MESC device counters for a Vmgw Access MESC controlling GPB board. For example, in GMPV3 GPB board position 0102 00 and 010300 are controlling GPBs. $ lhsh 010200 On the following prompt, give command 010200> mesc_counters_device 0 010200> mesc_counters_device all Look for rejections for any particular device ( if any ). Reasons of rejections can be found in GCP counters as described in section 2.12 of this document. Check the same in board 010300 / 650200 /650300 as well. 1.20 Check the status and utilization of TDM terminations

Access MESC controlling GPB board. For example, in GMPV3 GPB board position 0102 00 and 010300 are controlling GPBs. $ lhsh 010200 On the following prompt, give command 010200> mesc_info_tdm -group_total all Individual TDM termination group status can be found using command 010200> mesc_info_tdm -group_stat -pcm <PCM system number> 1.21 Check status of SCTP Associations $ lhsh 000600 rof_assoc_info $ lhsh 000800 rof_assoc_info Check that all associations are active 1.22 Check status of Signaling Routes $ lhsh 000600 000600> rof_congestion_info $ lhsh 000800 000800> rof_congestion_info Output may be available on one board only. It depends on no. of SS7 stacks loade d in the system and on which board the stack is running. 1.23 Check status of Switch Planes A and B $ spaspccinfo

SOLUTION: CONDITION: 1. Health check of Media gateway using Moshell. PROCEDURE:

1 1.1 ALTK

Advanced Status check using Moshell Check Alarms in the system

Here, C = Critical Alarms M = Major Alarms m = Minor Alarms w = Warnings

To check details about an alarm ALA 1.2 Cabxlradg 1.3 Std Print Hardware, LED status and restart info Check device status in MGw pools

1.3.1 Check for any congestion in Pool Devices lhsh 010200 mesc_counters_device all 1.3.2 Advanced info on pool devices lhsh 010200 gradsl mfd lhsh 010200 gradsl ipb lhsh 010200 grapmd ma 1.4 Check the status of Signaling Links 1.4.1 Check status of Link set st Mtp3bSls To get further detailed data use : get <proxy id> To print user Label in above st command: UL 1.4.2 Check status of Individual Signaling Links st Mtp3bSlItu To get further detailed data use get <proxy id> 1.5 Verify if external synchronization is working fine pr Synchronisation get <proxy id>

1.6 Check TDM termination Groups state $ st TdmTermGrp DISABLED # make sure no terminations are in disabled state. 1.7 Inv To check Hardware and Software inventory

( Can be useful to find software allocated to the boards ) 1.8 uv 1.9 Print User variable To print Moshell settings variables

pv 1.10 hi 1.11 cvls 1.12 Look for any abnormality in Alarm and Event Logs lgaer yyyy-mm-dd where, yyyy-mm-dd can be date when event log was last checked More detailed info can be found in lgaevsur yyyy-mm-dd 1.13 Hc Moshell complete Health Check History of all commands during current session Check if last and active backup is correct one Check if Auto backup is happening or not

This command can be used to save the complete healthcheck of the MGw in one file . 1.14 Check the state of DSP all pingdsp 1.15 Check licensed SCC capacity lhsh 000300 fro_lici_data_list Where, licensed SCC capacity = capacityLimit / 2 Compare with actual SCC capacity being used: Pget MgwApplication Actual SCC used capacity = pmNrOfMediaStreamChannelsBusy / 2 1.16 Interactive messaging Maintenance counters lhsh 010200 crhimrapmd

1.17 Check for Interactive Messaging (Im) errors with frequency lh mesc mesc_info_im all

1.18 Check each MSB for any errors lhsh xxxxxx rev Where, xxxxxx is MSB position If any of the MSBs show "not loaded", then there is a problem with the MSB.

1.19

Check abnormal performance counters

1.19.1 All Disturbance counters pget all forced|fail|unsucc|rej|rele|err|overflow|down|unavail|lost|missing !^0| -1 1.19.2 Imp. Disturbance counters (failed, unsuccessful & rejections) pget all fail|unsucc|rej !^0|-1 Take above 2 prints again after a gap of 1-2 minutes to find out error counters that are increasing.

1.20 Check Mgw capacity w.r.t. licensed capacity Get licensed max. no. of channels: > Get MgwApplication maxNrOfLicMediaStreamChannels Alternatively, this can be found using: > lhsh 000300 fro_lici_data_list or > lhsh 001300 / 002700 db_info_license > cd /c/license cat licensekeys.xml Print current active channels > Pget MgwApplication # Parameter "pmNrOfMediaStreamChannelsBusy" for active channels # Parameter "pmNrOfMediaStreamChannelsRejectedDueToCapacity" for capacity overlo ad counter

1.21 Check if any ET board is hanging $ all ps -w Aet_locDs0Bundle_proc Status column should contain ult in the board. rcv(any) . If status is other than this, there is a fa

1.22 Check for Overload of Vmgw $ lh mesc mesc_command_aal1Delay count Look for counter Number of OverloadInd sent to CH:

1.23 Check processor load for all boards ( 5-min average) pget plugin

1.24 Transactions per VMgw $ lhsh 001000 ch_info_tc $ lhsh 001100 ch_info_tc

You might also like