'invl' moshell command are not display some licenses

4G LTE
, ,
1

Hello team!

The ‘invl’ command shows the status of some licenses is not displayed, but only like N/A. This problem is only on DUS, but on the all Basebands are OK. AMOS ver. 22.0f. It was checked in Moshell 22.0v too.

Please help to find issue. Thanks in advance!

'invl' moshell command are not display some licenses
'invl' moshell command are not display some licenses941×942 67.2 KB

1 Like
2

Hi, @Nekto can you share output? Maybe this licenses is Not/Available on DUS?

2 Likes
3

Hi @vlr9999 ! Thanks for attention!

there are some outputs from DUS:

dus> get synchronization=1
…
featureStatePtpFreq 1 (ACTIVATED)
featureStatePtpTime 1 (ACTIVATED)
…
licenseStatePtpFreq 1 (ENABLED)
licenseStatePtpTime 1 (ENABLED)
…

And this from ‘invlr’ command:

=====================================================================================================================================
Feature                            keyId       FAJ           LicenseState  FeatureState     ValidFrom   ValidUntil  Description
=====================================================================================================================================
...
Synchronization:ptpFreq            CXC4040007  FAJ1212021    N/A           N/A              2022-09-30  No Limit    IEEE1588 Frequency Synchronization (CPP)`
Synchronization:ptpTime            CXC4040008  FAJ1212022    N/A           N/A              2022-09-30  No Limit    IEEE1588 Time and Phase Synchronization (CPP)

…

1 Like
4

For DUS it is only available if you have license, check license file:

http://<nodeip>/keyfiles/Licensing.xml

for this

<featureKey id="CXC4040007">
<description>IEEE1588 Frequency Synchronization</description>
<start>2022-09-08</start>
<noStop/>
</featureKey>
2 Likes
5

The feature itself is in the license file and is available, otherwise the start/stop would not be visible.
And there is some print from invlr:

=====================================================================================================================================
LicenseKeyFile: Installed, Mon Dec 19 09:38:29 2022, SequenceNumber: XXXX, FingerPrint: xxxxxxxxx
=====================================================================================================================================
FeatureId       FAJ          StartDate  StopDate   Status   ChangeReason  Description
=====================================================================================================================================
...
CXC4040007      FAJ1212021   2022-09-30 No Limit   Enabled  Licensed      IEEE1588 Frequency Synchronization (CPP)
CXC4040008      FAJ1212022   2022-09-30 No Limit   Enabled  Licensed      IEEE1588 Time and Phase Synchronization (CPP)
1 Like
6

Check some DUS in our network and it is same as yours:

CXC4040007      FAJ1212021   2022-09-08 No Limit   Enabled  Licensed      IEEE1588 Frequency Synchronization (CPP)
CXC4040008      FAJ1212022                         Disabled Not activated IEEE1588 Time and Phase Synchronization (CPP)
8

please check it on the first Table of invl command:

=====================================================================================================================================
Feature                            keyId       FAJ           LicenseState  FeatureState     ValidFrom   ValidUntil  Description
=====================================================================================================================================
9

Can anyone approve that this is a moshell bug?

10

Hi, could you confirm me which sw version do you use in DUS?

11

Hi @Cristopher_Polanco !
There is SW from DUS:
“DUS_MAINT-7 (CXP102051/27_R85N40) 20.Q1_1”

and Moshell SW:
“Welcome to MoShell 22.0v (LPA108514/1_R22V)…”

12

Hi, @Cristopher_Polanco !
Have you any comments/answers to my message? thanks in advance!

13

@Nekto my friend, I was checking and it appears just as it appears to you.

14

@Cristopher_Polanco, ok!
It is a pity that no one has an answer to this question…

15

The question is not relevant. The decision will be made soon :slight_smile: