Refta and clearing Errors 1

[NYPQ-EN]

Good morning all,

I am presently monitoring my T1s with the command Refta .
How am I able to clear the errors that I see when I run Refta?

Also, is there a way to do this in Openscape Assistant?

Question 2 : I need a way to monitor or look up my Stmi cards and Branch Shelves.

Question 3 : Is there a listing of what we should be checking every morning on the Hi-Path to make sure all is well.
What should we be checking throughout the day and before we leave for the day?

Thanks

PS - Deployment of new phone system is weeks away and we still have many questions to be answered.

Eric (still fighting Management to get the proper Training - thanks all for helping)

 

[LoPath]

If you're running a 4K, then BSSU will show you the status of your T1's:
[highlight #FCE94F]Last 15 minutes:[/highlight]
DIS-BSSU:1,6,9,0,CURR,;
H500: AMO BSSU STARTED
H40: PARAMETER CIR IGNORED. FOR TMDN/DIU2U BOARD
DATA OF WHOLE BOARD WILL BE DISPLAYED: 1.6.9 .
CIRCUIT 0 :
+==============================================================================+
| CURRENT 15 MIN. STATISTICS FOR TMDN/DIU2U LTG.LTU.EBT: 1 .6 .9
+------------------------------------------------------------------------------+
| |
| ESF 116 |
| ES CURR 0 PREV 0 |
| FS CURR 0 PREV 0 |
| BES CURR 0 PREV 0 |
| OES CURR 0 PREV 0 |
| US CURR 0 PREV 0 |
| DS CURR 0 PREV 0 |
| |
| 6 MINUTES 22 SECONDS INTO CURRENT INTERVAL. |
+------------------------------------------------------------------------------+
| |
| ALARM STATUS : NO ERRORS(GREEN) |
+------------------------------------------------------------------------------+
[highlight #FCE94F]Last 24 hours:[/highlight]
DIS-BSSU:1,6,9,0;
H500: AMO BSSU STARTED
H40: PARAMETER CIR IGNORED. FOR TMDN/DIU2U BOARD
DATA OF WHOLE BOARD WILL BE DISPLAYED: 1.6.9 .
CIRCUIT 0 :
+==============================================================================+
| 24 HOUR TOTAL STATISTICS FOR TMDN/DIU2U LTG.LTU.EBT : 1 .6 .9
+------------------------------------------------------------------------------+
| ESF 116 |
| ES 65535 FS 111 |
| BES 0 OES 113 |
| US 0 DS 0 |
+------------------------------------------------------------------------------+
| LOOPBACK STATUS: |
| |
| LOCAL : SET PAYLOAD : CLEAR |
| REMOTE REQUEST : SET |
+------------------------------------------------------------------------------+
| |
| ALARM STATUS : NO ERRORS(GREEN) |
+------------------------------------------------------------------------------+

[highlight #D3D7CF]ESF - Extended Superframe Errors? (Not in the documentation)
ES - Errored seconds
FS - Failed seconds
BES - Bipolar errored seconds
OES - Out of frame errored seconds
US - Up-slips
DS - Down-slips[/highlight]

[highlight #FCE94F]SDSU will show you what channels are in-use on your T-1's and their overall health:[/highlight]
DIS-SDSU:,,PEN,PER3,1,6,9,0;
H500: AMO SDSU STARTED

LTG1 (PERIPHERY)
------
MOUNTING LOCATION MODULE NAME BDL BD(#=ACT) STATUS
** .LTG 1.LTU 6.009 DIU2U-M A Q2216-X READY/BUSY
CCT LINE STNO SI BUS TYPE
000 4693 PP NW READY/BUSY
MULTLINE 30 . . . . . . . . . . . . . .READY/BUSY
007 NETWORK SUBUNIT . TMD CO ISDN READY/BUSY/CP
CPH
(ALT_ROUT: N) (S1COD )
LINE: 4693 STNO: SI:
001 . . . . . . . . TMD CO ISDN READY/BUSY
008 NETWORK SUBUNIT . TMD CO ISDN READY/BUSY/CP
CPH
(ALT_ROUT: N) (S1COD )
LINE: 4693 STNO: SI:
001 . . . . . . . . TMD CO ISDN READY/BUSY

AMO-SDSU -111 STATUS DISPLAY IN SWITCHING UNIT
DISPLAY COMPLETED;
<
[highlight #FCE94F]SDSU Statuses[/highlight]
[ul]
[li]AMO = manually blocked by amo[/li]
[li][/li]
[li]BUSY = busy, in use (the terminal/terminals is/are operational,[/li]
[li]and the terminal is busy at the moment)[/li]
[li][/li]
[li]CP = seized by call processing[/li]
[li][/li]
[li]CPH = cph bit of call processing[/li]
[li][/li]
[li]DEF = blocked by dependability because of a fault[/li]
[li][/li]
[li]DEFIL = circuit alarm (defect in line)[/li]
[li][/li]
[li]DEP = seized by dependability[/li]
[li][/li]
[li]DEPLOCK = block caused by L2 error[/li]
[li][/li]
[li]GENNR = generated but not ready[/li]
[li][/li]
[li]HIRAMO = blocked due to lock by amo[/li]
[li][/li]
[li]LHB = local hardware block[/li]
[li][/li]
[li]LMB = local maintenance block[/li]
[li][/li]
[li]LOCK = hard block/out of service[/li]
[li][/li]
[li]LSB = local software block[/li]
[li][/li]
[li]NL = not loaded[/li]
[li][/li]
[li]NOGEN = not assigned (for swu)[/li]
[li][/li]
[li]NPR = not present[/li]
[li][/li]
[li]READY = in service (the terminal/terminals is/are ready for use)[/li]
[li][/li]
[li]RHB = remote hardware block[/li]
[li][/li]
[li]RMB = remote maintenance block[/li]
[li][/li]
[li]RSB = remote software block[/li]
[li][/li]
[li]SIGNOFF = signed off[/li]
[li][/li]
[li]SOFTLOCK = soft block/out of service pending[/li]
[li][/li]
[li]TRS = remote block[/li]
[li][/li]
[li]UNACH = hierarchical block[/li]
[li][/li]
[li]UNAVA = blocked due to interrelationships[/li]
[li][/li]
[li]WAIT = waiting for an event (e.g. end of loading)[/li]
[li][/li]
[li]WBT = wrong board type[/li]
[/ul]

As far as your question about what should be checked.... Your best bet would be to just look at the HISTA error logs. This search shows me everything from today 3AM-8:30AM:
STA-HISTA:SEARCH,2018-08-30/03:00,2018-08-30/08:30,,;
H500: AMO HISTA STARTED
H1: 00003 ERROR MESSAGES FOUND

F5645 M4 N7115 OUT SERV BPB CIRCUIT L1 ERROR S0 18-08-30 04:54:53
ALARM CLASS:SWU-PER:004
** :LTG1 :LTU1 :001: 06 : 0 Q2324-X500 STMI4/1 BST:01 PLS:-11
REASON:04H NO SIGNAL (RED) (LOCAL ALARM)
FORMAT:36 DEVICE NAME: ONLYSYM

F5992 M4 N7116 IN SERV BPB CIRCUIT LX ACTIVE S0 18-08-30 04:57:29
ALARM CLASS:SWU-PER:004
** :LTG1 :LTU1 :001: 06 : 0 Q2324-X500 STMI4/1 BST:01 PLS:-11
REASON:07H LAYER 1 ACTIVE (GREEN)
FORMAT:36 DEVICE NAME: ONLYSYM

F5455 M4 N7117 IN SERV BPB TERM LX ACTIVE 18-08-30 04:57:31
ALARM CLASS:SWU-PER:004
** :LTG1 :LTU1 :001: 06 : 1 Q2324-X500 STMI4/1 BST:01 PLS:-11
FORMAT:22 DEVICE NAME: OPTIIP EXTENSION NUMBER: 8011
5F08000000FFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF

AMO-HISTA-111 READ HTS HISTORY FILE
START COMPLETED;
<
But looking at that can make you have a panic attack. It looks bad, because you see alarms and the text is in red. All it's telling me is that I had one phone reboot. The user likely unplugged it and plugged it back in.

I'd highly recommend getting a support contract with proactive monitoring. Black Box has a remote monitoring device attached to both of my PBX's and they "phone home" when there's an issue. Black Box would then check things out and only bother me if there's a major problem. If it's something minor, I may never even hear about it. Which is nice.

Looking up your STMI cards? Best bet is with the GUI. It depends on what version of PBX you have as to where this info is located. On my V6, it's under Expert Mode > Gateway Dashboard. It tells you the status of your boards and gives you the links to web based management (WBM). Great starting point. The Gateway Manager tells you the firmware versions on your boards.

Want some resiliency in your STMI cards? You can arrange them in board pools, so if a STMI card fails another board will come online and takeover. The AMO is BPOOL.

Enough to give you a headache yet?

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, OpenScape Xpressions, OpenScape Contact Center V8, OpenScape Voice V9

 

[NYPQ-EN]

Thank you LoPath.

Great help and thanks for the heads up on the RED writing .

Be on the look out for more of my questions.

I appreciate all of the help.

Have a blessed day.

Eric

 

[Hocinidz]

when you you have a problem with phone number and you trying troubleshooting this problem and try this command
DIS-SDSU:,,PEN,PER3,1,6,9,0;
and you finded SDSU status : DEFIL/CP
The question is what that meaning and what the solution for resolve this problem?
thanks

 

[sbcsu]

DIS-SDSU:ALL,,PEN,PER3,1,2,3,4;
OR
DIS-SDSU:ALL,,STNO,PER3,1234;

If above shows DEFIL then the circuit is down, the station number (telephone) is disconnected.
You can try resetting the link

RES-DSSUEN,1-2-3-4;
OR
RES-DSSU:STNO,1234;

But it is normally an indicator that the cables or the phone itself need to be checked.

 

[Moriendi]

If the circuit is defil then the best thing to do is reset it, then look in hista to see what the problem is, Layer 1,2,3 etc, red yellow blue AIS. Hista will tell you more than SDSU.

 

[Hocinidz]

thanks but how i can use HISTA to will find my problem?

 

[LoPath]

This search shows me everything on 8/30/2018 from 3AM-8:30AM:
STA-HISTA:SEARCH,2018-08-30/03:00,2018-08-30/08:30,,;

As far as deciphering the output, it takes a bit of work. Using the built-in documentation on the platform portal helps immensely. (Depending on what version of PBX you have)


LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, OpenScape Xpressions, OpenScape Contact Center V8, OpenScape Voice V9

 

[luvarne]

Clear the error with this --> CHA-REFTA:CIRCUIT,1-1-25-0,,,,0;
where 1-1-25-0 is the PEN for the T1/E1