Red Led on face of HiPath 4000 communication server A-1 card. 1

[pbxtechron]

I noticed the LED with the letters W\E is lit red. I havent had to deal with any issues like this and cant seem to find what the LED means. I have a pic but it wont upload. Anyway, from left to right on the front of the card is a reset button with an led lit green R\A, then an led lit red W\A, then another reset button and an LED lct, not lit. This is a HiPath 4000, Version 5. The card I'm talking about is the bottom card on the server, labeled A-1 by the install tech, next card up is the A card, then the card for back up's, then a blank, then the B card.

 

[sbcsu]

It is just an urgent alarm.
It could be anything from an ISDN circuit down, or an operator console not working etc. depends on configuration.
If everything seems to be working fine then ignore it until you can log on using Comwin.

 

[pbxtechron]

Thanks for the reply. I had to go in last night for a one way audio problem. First thought it was a PRI, then when I got onsight isolated to incoming calls from Hipath to OSV having the issue. Ended up reseting the STIMI for the SIP trunking between the 4K and OSV, but that was after I reset a PRI. So I'm not experianced at looking into alarms, and have limited experiance with AMO commands. They used Assistant in training. Before I left about 45 minutes ago I also noticed the PC I use for CDR was off so I powered it up and was hoping it was because it needed to dump 2 weeks of logs, but it was done before I left and still have the LED. So is there a way in assistant to see those alarms, or AMO cammands?

 

[sbcsu]

When you log on to Comwin
Use the command
DIS-SIGNL:SYSTEM;
to see if any alarms.

If there are alarms showing then:
STA-HISTA;
That will show some alarms, CDR normally would be number 29 (Maintenance Alarm)

 

[pbxtechron]

Just got onsite again. Ran those commands, ( thank you ) there is a major alarm " in swu" and when I run the sta-hista get the amo signal code 111 for an "error signalling control

 

[pbxtechron]

Just got off the phone with Support, they say its the CDR logs, however the Tech I was talking with is more of a system down tech and said it was no big deal to wait, that the logs were not big enough to cause an issue, and maybe tonite when the system syncs drives it might clear, since I restored the CDR pc. Well I hope so. Ha! I guess Siemens/Unify/Atos is cutting back on support for after hours/weekends unless somethng is down.

 

[pbxtechron]

SBCSU
I have to update what I said earlyer about the 111 code. I ran the commands again and see I misspelled the first time. So I spelled sta-hista; correct and got the 029 you talked about, and the alarm name is "maintenance_note"
I took the time to update the CDR PC, and reboot it, hoping it might help, but it did not. All calls do show up in the CDR software. So I dont understand why the alarm is still there if it sent all CDR records to the CDR PC software.

 

[sbcsu]

To delete the alarm (will not fix the problem) DEL-GRA:A1,29; and/or DEL-GRA:BP,29;

To see the status of the CDR (if it is real time coming out of the HiPath) DIS-LSSM;
You should see an entry (other than zero) on the right hand side under User/Port if the CDR is working (real time cdr)

If the CDR is not working then, DIS-SELS;
Which ever SELGRNO is 'ON' then turn it Off and On again
Example:
DEA-SELS:3;
ACT-SELS:3;