TSW-SP08 - HealthCheck routine? 4

[nikk0r]

Hi all,

I just want to know a little bit about health check routine for my PBX system.

Every 3 months our vendor will come to our site and perform the health check. They will execute some commands & check the battery voltage and take the log.
Here i share the command that they do.

ALREI;
ALLIP;
ALLOP;
HIMDP;
HIREI;
CNLIP:LIM=ALL;
CNBIP:LIM=ALL;
CNBIP:LIM=1;
CNBIP:LIM=2;
CNBIP:LIM=3;
CNBIP:LIM=4;
GSFTI:GSM=0,GSSIDE=0,TEST=SLOT;
GSFTI:GSM=1,GSSIDE=1,TEST=SLOT;
GSFTI:GSM=2,GSSIDE=2,TEST=SLOT;
GSFTI:GSM=3,GSSIDE=3,TEST=SLOT;
GSFTI:GSM=4,GSSIDE=4,TEST=SLOT;
GJTSP:LIM=ALL;
FTMDI:LIM=ALL;
FTMFI:LIM=ALL;
FISCP:IODEV=SYSDISK1;
FTFCI:LIM=1;
FTFCI:LIM=2;
FTFCI:LIM=3;
FTFCI:LIM=4;
LIDAP;
SYECP:LIM=ALL;
DUSYI:DUMP=CHANGES;

HIMDP History manual diagnostic information print

DIAGNOSTICS FROM OPERATING SYSTEM

TIME     DATE
06:30:03 01OCT14

DIAGNOSTICS FROM LIM 001, LAST HIREI: 22:41:27 29SEP14

TIME     DATE        ERROR CODE
06:06:13 01OCT14     H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02005B1A
ENTER
SWSW   B-LEVEL SIGNAL  PRNOK             (H'005C)
FROM   OCM     (H'017) EXE A IN LIM 001
TO     DRDH    (H'01D) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL =  4    
WITH     0   1   2   3   4   5   6   7   8   9
000     00  02  6A  01
STACK ADDRESS        = 00000000
SIGNAL SEND ADDRESS  = 020037AE


TIME     DATE        ERROR CODE
12:59:43 30SEP14     H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02019BE6
BRANCHVALUE                   = 00000000
ENTER
SWSW   B-LEVEL SIGNAL  READWRITEBRDRES   (H'0070)
FROM   DCP     (H'07E) EXE A IN LIM 001
TO     DCP     (H'07E) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL =  62   
WITH     0   1   2   3   4   5   6   7   8   9
000     00  60  86  00  06  22  12  1E  23  50
010     00  23  00  00  00  00  00  00  00  00
020     70  00  00  00  02  00  00  00  00  05
030     02  00  04  FC  02  00  03  F0  00  03
040     54  01  00  03  57  03  02  02  00  9B
050     5C  02  00  1A  74  FF  00  00  00  00
060     02  04

USER STACK DUMP
 0   1   2   3   4   5   6   7   8   9   A   B   C   D   E   F
02  00  10  7A

the result for HIMDP is so many,i just paste a little bit of it.

and, the thing that i'm really² want to know is..
i - can anyone share with me, how you do and perform the healthcheck.
ii- for the himdp log, it shud be clear and no error rite? because they shud fix any error on my system.
[ i'm very suprise because my vendor just execute command and take the report only, they not fix any error that they found. ]

rgds,
nikk0r.pbx.jR

 

[INLSP04]

hi
they just test some parametr and config in your system
pcm link&tmu&lic state and same .....
no do any important job can do your self this test its so easy
himdp log history just can be translate with plex view
regard

 

[nikk0r]

Hi INLSP04,

Thanks for your reply. Where can i get the plex view? Because when i search , just got plex media server

rgds
nikk0r.pbx.jR

 

[INLSP04]

plex view just show unit and signal you can get plex view from ericsson because this software is ericsson produce
so you can try this comman dfor check health your system:
1-dubdp; for check dump state
2- blfdp; for see block equ
3- gjtsp:............... for check pcm link

 

[fcpli]

My advice:
This "health check" 1s a good way to charge for nothing. Even the first row (ALREI) is definitely removing all old alarms from the log. Sending ALLIP after 1 or 2 seconds shows only level 3 faults (depending of the fault). The rest of the commands are just scrap. History (HIMDP) shows problems, but a MD110 without any history for 3 months - not possible, or then somebody has removed all history logging. Just a hint: If there are several types of the same faults in the himdp during a short time period, then that fault should be taken care of. If your support team does not take any action (if something is really wrong), fire them.

 

[INLSP04]

100000 for fcpli

 

[nikk0r]

Thank you so much for your input guys...
Before this when i ask the vendor about the log. They said there are no problem n issues. But now after 7 years i know this... Haha pittty me. This happen after our LIMs 2 is corrupted. And we sont have any backup..
So now i create some batch script to do ftp backup every weeks n keep it on our networkstorage .

INLSP04: can u share with me the plex view software . Because i cannot found it. When i ask our vendor. They said they dont know about the software..

Rgds
nikk0r.

nikk0r.pbx.jR

 

[himdp]

Hi nikk0r,
The question of Plexview has been raised a number of times, do a search, but to summarise,:
The PlexView application is part of SAM toolbox but it is useless without the Plex database which is proprietary Aastra/ Mitel and is not available outside their organisation. As the Plexview database is the source code for the system software it is obviously commercially sensitive; you would not expect Cisco or Microsoft to publish their proprietary code would you.

Plexview can also be used with the SigView database which describes signal contents and was available on the support database to authorised third parties.

No MD110/TSW system in existence which carries live traffic will be entirely free of errors in the HI log. The trick is to know the severity of the problem indicated by them. Try to determine if signals in the HI print coincide with problems with the system or end user. Most HI signals or "lost signals" as they are know are the result of software problems but some hardware issues can show as lost signals. If there are no problems then do not worry too much about the lost signals. (If it isn't broken, don't fix it )

If the lost signals are an indication of an issue with the system, this is best handled by reporting the error through official support channels but beware, the first reply will always be "ensure the system is at the latest released service pack". If you are not able to keep the system software up to date you cannot expect to get much attention from the support department.

Fixing software faults using patches is not an end user function. It requires acess to the Plex source code for the given release including all implemented patches, it also requires knowledge of the internal software structure and signalling as well as Plex and Motorola assembly language programming.

The location of a software fault is indicated by signals in the HI log but usually signal tracing is required to locate the exact cause. The software error is corrected by design engineers with a patch which is then, lab tested, beta tested and released.

As a historical note, most Ericsson local companies had copies of the Plex database but this led to a large number of unauthorized and poor quality customer/market patch adaptations which placed a disproportionate burden on the main support organization. Progressively the access to the source code was withdrawn and the last few companies with access to the code were required to pay a fee for the privilege. Use of this was restricted to fault fixes only and not for adaptations. This particularly led to management at those companies paying for code access to question the logic behind paying for the 'privilege' of fixing Aastra's bugs for them. Incidentally even when the source code was available to those outside Aastra, there was always one program unit not available and that was LISH.

If you are interested in a basic understanding of MD110 software there is a pdf of some training slides called "022-03 MD110 Software slides.pdf"at this link-

https://onedrive.live.com/redir?resid=5FC098E631ED...

I hope this helps clarify.

 

[nikk0r]

Hi himdp,

Thanks for your reply...

it's start from frustrated and make me become like this. 7 years is very a long time to be fooled by "some person" , but its ok for me, because from that issue its make make me learn a lot of thing and want to know how to solve the problems.

I already raise up this issue to the top management, we pay them to do maintenance & health-check at our side. but they not fix anything from the error.. haha very easy to get money. never mind the this is already happen.

thanks to INLSP04, FCPLI & HIMDP because help me to understand this. i hope i can gain my knowledge from you all.

rgds

nikk0r.pbx.jR

 

[INLSP04]

hi nikk0r
about plex i not have that
and for more issue i accept fcpli convertion .
regard

 

[himdp]

Hi nikk0r,
You should not assume that all service organisations are taking money for doing nothing.
If all you are paying for is the health check then perhaps you are wasting your money but normally this regular visit is the tangible part of a more comprehensive service agreement which could include keeping the system up to date with service packs. In this case, the "health check" is a useful way for both parties to build a relationship so that if/when something serious does happen, it can be resolved quickly.

The fact that your system has lost signals in the HIMDP does not mean that your service people are doing nothing. As stated before, even a healthy system will have errors in the HI print so you cannot expect them all to be cleared.

Look at the service agreement as an insurance policy. I have been paying an insurance company for 10 years to insure my house and have never claimed because my house has never been burgled or caught fire which I am happy about. The insurers have never come to my house to check that I am OK so does this mean I am being "fooled" by them? The answer would only be yes, if I ever needed their help and they did not provide it, so like an insurance company, you cannot judge a service organisation until they have been tested with a real emergency and handled it well or let you down.

Before you get your senior management to cancel your relationship with your service company you should see what else you are paying for which is less visible. It is always reassuring to have backup from an experienced source if things go wrong, even if it is only to blame them when there is a disaster and people start pointing fingers at you ;-)

 

[INLSP04]

nikk0r
It is better that you take care of your system
When the system came into existence and basic shapes
Eat with a contract for solving it
Flash is always a backup of your system
And careful linkage analog line Vdyjytal
Be Vzyt call center and storage temperature
If this is the right debt
You only need to upgrade every 10 years.

 

[nikk0r]

Hi himdp,

i do not mean all organisation are like that, i'm sorry if you are disappointed with me.

My friends also using the same system with me, but with different vendor. They dont have any problem like me. when they claim warranty for any part, they got it. But at my site when we claim warranty, they take almost 3 years.. we send 5 analog card, we just return only 1. another 4? we have the job sheet, and for our new installation system they told me any problem card they will replace 1 by 1. and now we still waiting another 4 card.
angry? yes i am....
happy? yes!! why? i learn a lot from it. because i'm start from '0' knowledge with pbx system. and now i'm still learn, because i just know basic only

and now what i'm doing is.. do a backup for my system every week.

rgds

nikk0r.pbx.jR

 

[himdp]

Hi nikk0r,
I was not being critical and I am certainly not disappointed in you. Regardless of how knowledgeable they are now, everyone on this forum started at zero and worked up. You have come to the right place to get advice but just be aware that not all advice (including mine) is appropriate for your situation.

I was just trying to let you know that in my experience most vendors will treat you fairly and give you good service for your money and it is better to have the support of a specialist organisation than to try and go it alone.

If you are dissatisfied with your current vendor perhaps a threat to move elsewhere might be enough to get some better service (or a discount/compensation)from these people.

Anyway, good luck with whatever you decide.

 

[INLSP04]

himdp
I SEE very very this health checker in many site they just got free money and nothing do and when happen a force problem they request big money .

 

[himdp]

INLSP04,
I stand by my earlier posts.

 

[CAF2009]

Hello
The check list is only for historical process, HIMDP lost signal only important if related with abnormal circumstances in the system or if they are high in short periods (hours).

Most important check&health should be a compact flash swap or hdu swap, keeping at least one backup outside the system; together with a regen of entire system to get all data commands that could be used to rebuild the system from scratch. Regen should be given to costumer in the end of each visit.