Changing time directly on Linux-Host command line, if duplex do on both processors:
# date -s 17:25 or # date -s "YYYY-MM-TT hh:mm:ss"
# date -s "2012-12-31 09:51:24" => date & time. changed
In our case, the problem was solved after the parameter "ZAND/ALLDATA2/CONFTONE" has been set to "NO" (workaround solution).
The official solution ( provided from product house) is included in the OpenScape4000 RMX-Hotfix 8 for V10 R1.42.0.
One of the OS4kV10R1 duplex node, reports the problem as in the title (see attached file for more details).
What can/should be done in such situation?https://files.engineering.com/getfile.aspx?folder=2acc5872-9c62-46d9-9054-b4f59c2076ec&file=Node2.txt
We have old system with APE module (HiPath 4000 V5).
We have to check HD (AMO DVU) but this AMO can't be run on CC-AP.
"THE CALLED AMO ACTION IS NOT ALLOWED TO RUN ON CC-AP"
Is there any hint to force CC-AP to run AMOS?
Our customer need a following solution: after an identification with a PIN of a virtual subscriber, the SRCGRP of this virtual subscriber will be taken into account, and not the SRCGRP of the home subscriber.
At present, the OS4k takes into account the KNNR/NNO of the virtual subscriber, but...
After activation of the A9.115 loadware, there was a flood of F5870 messages from EnterpriseGWs - for example:
F5870 E8 N5220 NO ACT BPA BOARD LW EXCEPTION 22-10-17 09:28:47
ALARM CLASS:CENTRAL:002
P919:LTG1 :LTU19:007: 00 : 0 Q2347-X EntGW/1 BST:01...
In our case it was definitely related with the AFR2 service and the ":PAS:FBT/FAULTFILE2" file, not with the HISTA and its tasks/files, as described in the documentation above. It was solved with:
[ol 1]
DEACTIVATE-AFR:LDU=AFR2,TYPE=PROT&LDU;
STA-DEL:":PAS:FBT/FAULTFILE2"...
I think that in our case it is related with the AFR service and the ":PAS:FBT/FAULTFILEx" file, not with the HISTA and its tasks/files, as described in the documentation above.
Does anyone can say me something more about such error:
F6524 E8 N1631 NO ACT A1 SM-AM MAINTENANCE 23-04-17 22:54:21
ALARM CLASS:CENTRAL:029
FORMAT:33
WARNING BY AFR TASK: FAULTFILE DAMAGED
FAULTFILE WAS NEW INITIALIZED
Many thanks in advance!
Found in the Unify Knowledge Base.https://files.engineering.com/getfile.aspx?folder=02bfa139-dba2-4fef-ae87-c179a2578274&file=After_installing_Java_version_1.8.0_351,_access_to_Assistant_Configuration_Managemen,is_blocked,_client_preparation_blocks_at_the_Java_related_step_(KB000105286).pdf
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.