Difference between revisions of "OpenScapeFM License"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | <span style="font-size: 10px;"> [[OpenScapeFM_FAQs| -> Back to FAQ]]</span> <br/><br/> | + | <span style="font-size: 10px;"> [[OpenScapeFM_FAQs| --> Back to FAQ]]</span> <br/> |
| + | ---- | ||
| + | <br/> | ||
| + | <span style="font-size: 13px;"> [[#lic_faq_1|1. What are OSFM redundancy licenses and what can I do with them?]]</span> | ||
| + | <span style="font-size: 13px;"> [[#lic_faq_2|2. How to create a ALI for the CLA License on command line?]]</span> | ||
| + | ---- | ||
| + | ---- | ||
| + | <br/> | ||
| + | <span id="lic_faq_1" style="font-size: 13px;">1. What are OSFM redundancy licenses and what can I do with them?</span> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
The redundancy licenses are just a commercial aspect - they do not refer to any technical solution. | The redundancy licenses are just a commercial aspect - they do not refer to any technical solution. | ||
| − | |||
This basically means: If you want to run a seconds OSFM server in the same environment, you can get a discount for the second installation by ordering the redundancy licenses. | This basically means: If you want to run a seconds OSFM server in the same environment, you can get a discount for the second installation by ordering the redundancy licenses. | ||
| − | |||
Best practice and the easiest way to achieve a higher availability is to just run two equally configured OSFM servers in parallel, may be at different geographically locations. If one fails, you can manually log in to the other. | Best practice and the easiest way to achieve a higher availability is to just run two equally configured OSFM servers in parallel, may be at different geographically locations. If one fails, you can manually log in to the other. | ||
| − | |||
There are two points to consider here: | There are two points to consider here: | ||
| − | |||
1) All monitored devices like OS4k Manager, OSV etc. have to be configured in a way so that SNMP Traps (Alarms etc.) are send to both OSFM servers | 1) All monitored devices like OS4k Manager, OSV etc. have to be configured in a way so that SNMP Traps (Alarms etc.) are send to both OSFM servers | ||
| − | |||
2) All configuration steps on one OSFM server have to be transferred manually to the other one - either by reproducing all configuration steps on the other OSFM, or by copying some DB/Config files (this is the quicker way) | 2) All configuration steps on one OSFM server have to be transferred manually to the other one - either by reproducing all configuration steps on the other OSFM, or by copying some DB/Config files (this is the quicker way) | ||
| − | |||
In theory, more sophisticated solutions would be possible as well, e.g. setting up a Linux cluster with pacemaker and run OSFM on this, or create a bunch of scripts to copy over the configuration from one server to another automatically and implement a switch-over. But I think you could not build such a solution without additional help/services from us. | In theory, more sophisticated solutions would be possible as well, e.g. setting up a Linux cluster with pacemaker and run OSFM on this, or create a bunch of scripts to copy over the configuration from one server to another automatically and implement a switch-over. But I think you could not build such a solution without additional help/services from us. | ||
| − | |||
If you are looking for an easy redundancy solution you can install/maintain by yourself, just run two OSFMs in parallel as I have described at the beginning.</span> | If you are looking for an easy redundancy solution you can install/maintain by yourself, just run two OSFMs in parallel as I have described at the beginning.</span> | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <span id="lic_faq_2" style="font-size: 13px;">2. How to create an ALI for the CLA License on command line?</span> | ||
| + | |||
| + | For virtual machines you need a so called ALI, a advanced locking ID, | ||
| + | to create a CLA license. | ||
| + | That is because the MAC Address does not work for a virtual maschine. | ||
| + | |||
| + | This ALI can be retrieved by using the following command: | ||
| + | ./get_ali -d 000406020005110305061104110511051605110621012001220110 | ||
| + | |||
| + | The get_ali command is found under: | ||
| + | Windows: C:\Program Files (x86)\Licensing\License Agent\bin\get_ali.exe | ||
| + | Linux: /opt/cla/bin/get_ali | ||
| + | |||
| + | The ID in the command is the product ID for the OSFM. | ||
| + | The get_ali command will create serveral ALIs which can be use to create valid CLA licenses. | ||
| + | |||
| + | For example: | ||
| + | |||
| + | ./get_ali -d 000406020005110305061104110511051605110621012001220110 | ||
| + | |||
| + | Advanced Locking Id(ALI) 1: F5R*7NMELL4:ES3CFMZ+UP: | ||
| + | |||
| + | Advanced Locking Id(ALI) 2: F5R*7NMELL4KF*:JKMZ+UPQ | ||
| + | |||
| + | Advanced Locking Id(ALI) 3: F5R*7NMELL4:NH3CGJY#UPN | ||
| + | |||
| + | Advanced Locking Id(ALI) 4: F5R*7NMELL4KF*:SDFFY#UPC | ||
| + | <br/> | ||
| + | The product ID can also be found in one of the *.alf files below the <osfm_installdir>/server/conf | ||
| + | <br/> | ||
| + | ---- | ||
Latest revision as of 12:26, 22 February 2019
1. What are OSFM redundancy licenses and what can I do with them?
2. How to create a ALI for the CLA License on command line?
1. What are OSFM redundancy licenses and what can I do with them?
The redundancy licenses are just a commercial aspect - they do not refer to any technical solution.
This basically means: If you want to run a seconds OSFM server in the same environment, you can get a discount for the second installation by ordering the redundancy licenses.
Best practice and the easiest way to achieve a higher availability is to just run two equally configured OSFM servers in parallel, may be at different geographically locations. If one fails, you can manually log in to the other.
There are two points to consider here:
1) All monitored devices like OS4k Manager, OSV etc. have to be configured in a way so that SNMP Traps (Alarms etc.) are send to both OSFM servers
2) All configuration steps on one OSFM server have to be transferred manually to the other one - either by reproducing all configuration steps on the other OSFM, or by copying some DB/Config files (this is the quicker way)
In theory, more sophisticated solutions would be possible as well, e.g. setting up a Linux cluster with pacemaker and run OSFM on this, or create a bunch of scripts to copy over the configuration from one server to another automatically and implement a switch-over. But I think you could not build such a solution without additional help/services from us.
If you are looking for an easy redundancy solution you can install/maintain by yourself, just run two OSFMs in parallel as I have described at the beginning.</span>
2. How to create an ALI for the CLA License on command line?
For virtual machines you need a so called ALI, a advanced locking ID, to create a CLA license. That is because the MAC Address does not work for a virtual maschine.
This ALI can be retrieved by using the following command: ./get_ali -d 000406020005110305061104110511051605110621012001220110
The get_ali command is found under: Windows: C:\Program Files (x86)\Licensing\License Agent\bin\get_ali.exe Linux: /opt/cla/bin/get_ali
The ID in the command is the product ID for the OSFM. The get_ali command will create serveral ALIs which can be use to create valid CLA licenses.
For example:
./get_ali -d 000406020005110305061104110511051605110621012001220110
Advanced Locking Id(ALI) 1: F5R*7NMELL4:ES3CFMZ+UP:
Advanced Locking Id(ALI) 2: F5R*7NMELL4KF*:JKMZ+UPQ
Advanced Locking Id(ALI) 3: F5R*7NMELL4:NH3CGJY#UPN
Advanced Locking Id(ALI) 4: F5R*7NMELL4KF*:SDFFY#UPC
The product ID can also be found in one of the *.alf files below the <osfm_installdir>/server/conf
