OpenScape 4000 V7 License Issue

[plokijuh]

Hi guys,

have an issue with the license.

When using DISPLAY-CODEW:; command from Comwin I see proper information about license but Assistant shows me V7 (Grace Period).

The system is duplex but at the moment only one proccessor is working.

I had an issue with the station couple days ago.
After fixing the problem got wrong date which I fixed with these commands:

CHANGE-DBC:LOCATION=TESTLAB;
EXEC-DATE:YEAR=2020,MONTH=03,DAY=05,SYNC=NOSYNC;
CHANGE-DBC:LOCATION=CUSTOMER;

Before using above command I've checked date and time on linux server and those was alright.

What could be the problem?

 

[sbcsu]

On V7 the time/date is set by SUSE Linux - you have to set an NTP server in the XML setup or you can if necessary get into YaST to amend that NTP server address.
Changing the date/time via Comwin is no longer required.

If the Codeword is in a grace period it could be because of an incorrect date/time
Can you get the second processor working - what is the problem with that ?

 

[plokijuh]

Thank you for reply sbcsu.

Before using CHA-DBC command I corrected time from yast2 on Linux and then issued the command:
CHANGE-DATE:GMTDIR=EAST,TIMEOFFS=240,MODE=NT,DSTOFFS=0;
This approach didn't help me.
Only after that I used CHA-DBC.

I cannot get second processor working at the moment. Some kind of OS problem.
Second processor is not plugged in at the moment.
When both processor plugged in the system is not booted. Stuck at step 4.

 

[plokijuh]

Any suggestions ?

 

[plokijuh]

Will Assistant reinstalling help me?

 

[plokijuh]

I found this post

Restart HiPath 4000 Assistant

https://www.tek-tips.com/viewthread.cfm?qid=1773975

When using DISPLAY-CODEW:; command from Comwin I see proper information about license but Assistant shows me V7 (Grace Period).

Will Assistant reinstalling help me?

Guys maybe someone faced this problem.

 

[sbcsu]

That information is for a Version 5 - Version 6 and above run on a different platform - SUSE Linux
If possible get the 2nd processor working.
If not then reinstall from scratch.

 

[plokijuh]

Thank you sbcsu.

I will connect the second processor and try to start it.

On the Assitant, when I go to the Licence Management I saw the message: RMX data cannot be read.
Can I reinstall only Assistant?

 

[sbcsu]

I'm not sure where you are with this.
If it was me I would restart from the very start.
If you have licenses already then keep the same server names and IP addressing and the existing licenses will work.
Work methodically from the start.
You should already have XML files to begin with.
You should make sure that the system is connected on the network to an NTP server.

 

[plokijuh]

Thank you sbcsu.

I couldn't restart the system at last 10 days.

Completely agree with you.
At first, I gonna plug in second server and check what is wrong with it.
If I can't start duplex system correctly I just restart system only with one processor.

"Work methodically from the start."
The only right way to find out what is the cause of the problem.

 

[sbcsu]

Do you have your xml file ready ?
Remove the hard disks from the processors
Remove the joining cables from the processors
Put xml file into config folder on USB
Startup from USB
Proceed with install using LCD

 

[plokijuh]

Thank you sbcsu.

I will try to recover the system and get second cpu working.

If this does not help me, then reinstalling is the only way.

I have xml file.

 

[plokijuh]

I did restart to Assistant from Portal website but got same issue.

Could't get second processor work.

I think maybe I can enter license information from License Manager in Assistant.

 

[sbcsu]

Did you re-install from start using USB and Display on Processors ?

 

[plokijuh]

No sbcsu, I didn't reinstall using USB.

Problem with second processor started after updating version 7 to one of minor releases.

I understand that reinstalling can help, but system working 24/7 and I'm trying to do whatever I can do in live.

 

[Moriendi]

As long as the 4K telephony has the correct codeword, and AMO interface is not locked, I would concentrate on fixing the dead processor.

If the processor is good and the HD is good, then you can fix it by starting "Node Recovery" from the Portal of the working processor and rebooting processor B. This was supported from V7.

Node Recovery works by starting a DHCP server on the Corosync interface. B will boot from A, and A will supply the install files and XML.

For it to work
- Processor B must be set to network boot first, in the BIOS
- The install XML in processor A must contain details of both processor A and processor B (ie, inside the XML, you must see both node1 and node2)

I can't remember if you need to relicense afterwards. I would expect it. You can take the existing license from processor B if it is at least bootable by SFTPing it from /opt/cla/license.

This all works best with a monitor on processor B so you can see what is happening.

 

[plokijuh]

Thanks for the answer Moriendi.

Despite the fact that I have a problem with the license in Assistant, the PBX is working without any problems.

So far I didn't touch anything because of unfavorable time.

Second CPU stucks at 4th stage of loading.

I got this error in Assistant:
When I go to the Licence Management I saw the message: RMX data cannot be read.

Probably I need to enter license from Assistant.

I have no issue with the license when connectioned via CommWin.

 

[Moriendi]

The PBX is working fine because the CODEW config is correct. Assistant will enter the codeword to the PBX part with AMO ADD-CODEW once a license is imported (which you would have done a long time ago). Once that is done, it's done. It won't undo that config. What can go wrong after that is SLES update license might expire, or you over-configure the ports on 4K, example, you have bought 500 ports in the license but then add 510 in the 4K DB. Then you will have a problem. If you don't exceed the license counts, PBX will be fine. You don't need to enter a license from Assistant as you suggest, it won't help here.

When you say CPU is stuck at 4th stage, you mean you get a 4 on the 2nd processor display? That is usually ATLAN problem. Are you sure your LAN corrections between the processors are correct? Post a photo if not sure.

 

[plokijuh]

Thanks for the answer Moriendi.

"The PBX is working fine because the CODEW config is correct."
CODEW config seems ok when I run DIS-CODEW; command.

Got it. So I shouldn't enter license from the Assistant.

"When you say CPU is stuck at 4th stage, you mean you get a 4 on the 2nd processor display?"
Yes. Exactly.
LAN is ok and all cables connected correctly, but I'll check it one more time.

Can "RMX data cannot be read" error occur because of bad LAN connection between processors?

 

[Moriendi]

Can "RMX data cannot be read" error occur because of bad LAN connection between processors?"

No. Assistant will try to connect to the ADP 192.0.2.3, and that is running on the same processor as the Assistant, it's all running on the first processor. Assistant won't try to connect to the other processor. So sure, there is some problem. But that's not it.

I would concentrate on getting that 2nd processor working. It sounds like it is looking for the ADP and cannot find it (maybe, almost like the Assistant ). But you can access through Comwin, so we know the ADP is working. Strange.

tcpdump can show what is happening on the atlan, if there is a problem. A photo of the 2 processors might be useful.