# System registration through SMT with different lic. **URL:** \ **Category:** SLES Updates\ **Created:** [August 3, 2015, 7:34pm UTC](https://forums.suse.com/t/system-registration-through-smt-with-different-lic/27295 "2015-08-03T19:34:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![configurationmanagem](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@configurationmanagem](https://forums.suse.com/u/configurationmanagem)\ **Post date:** [August 3, 2015, 7:34pm UTC](https://forums.suse.com/t/system-registration-through-smt-with-different-lic/27295/1 "2015-08-03T19:34:27Z")
Hello! I’ve got several systems (these are very much world-wide distributed) and I need to register them. I can use SMT server as a central “proxy for these”, I’ve done SMT server setup and can see this in SCC, however this is my question: I’ve got severall different licences for different projects. For example: EMEA SLES x86-64 1-2 Sockets with Unlimited VM, Standard Subscription EMEA SLES x86-64 1-2 Sockets or 1-2 VM, Standard Subscription And I need to register different systems using different licences, how I can do this? On what stage I’m able to choose the right one? Or when I use SMT I will use the same Lic. as a SMT registered? Sorry, but I cannot find any find of that information in manuals or in the internet. ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [August 4, 2015, 12:11pm UTC](https://forums.suse.com/t/system-registration-through-smt-with-different-lic/27295/2 "2015-08-04T12:11:18Z")
Hi configurationmanagement, [QUOTE=configurationmanagement;28973]Hello! I’ve got several systems (these are very much world-wide distributed) and I need to register them. I can use SMT server as a central “proxy for these”, I’ve done SMT server setup and can see this in SCC, however this is my question: I’ve got severall different licences for different projects. For example: EMEA SLES x86-64 1-2 Sockets with Unlimited VM, Standard Subscription EMEA SLES x86-64 1-2 Sockets or 1-2 VM, Standard Subscription And I need to register different systems using different licences, how I can do this? On what stage I’m able to choose the right one? Or when I use SMT I will use the same Lic. as a SMT registered? Sorry, but I cannot find any find of that information in manuals or in the internet.[/QUOTE] registration of the systems works like without SMT - you specify the license code while running the registration via command line or via YaST on the (SMT client) server machines. Or did I get the question wrong? Regards, Jens ---
**Author:** ![configurationmanagem](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@configurationmanagem](https://forums.suse.com/u/configurationmanagem)\ **Post date:** [August 13, 2015, 6:30pm UTC](https://forums.suse.com/t/system-registration-through-smt-with-different-lic/27295/3 "2015-08-13T18:30:46Z")
Hello, If I try to run clientSetup4SMT.sh using hostname I’ve got error: (If using IP address that’s going fine) [CODE]# ./clientSetup4SMT.sh --host [ukwcmcsmt01.odops.uk.domain.net](http://ukwcmcsmt01.odops.uk.domain.net) Certificate: Data: Version: 3 (0x2) Serial Number: c1:ee:75:75:f0:04:4f:2e Signature Algorithm: sha1WithRSAEncryption Issuer: C=GB, CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net Validity Not Before: Jun 16 14:20:24 2015 GMT Not After : Jun 13 14:20:24 2025 GMT Subject: C=GB, CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public Key: (2048 bit) Modulus (2048 bit): 00:d0:3c:39:29:5a:d2:c7:11:9b:15:e7:51:a8:f5: … f5:d5:dc:cf:9c:69:f7:9b:b5:55:07:2d:72:ea:7d: d6:61 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Basic Constraints: critical CA:TRUE Netscape Comment: YaST Generated CA Certificate Netscape Cert Type: SSL CA, S/MIME CA X509v3 Key Usage: Certificate Sign, CRL Sign X509v3 Subject Key Identifier: 66:AF:47:EB:E3:64:72:35:89:C0:8E:50:E2:6C:17:C5:B3:7E:4F:B0 X509v3 Authority Key Identifier: keyid:66:AF:47:EB:E3:64:72:35:89:C0:8E:50:E2:6C:17:C5:B3:7E:4F:B0 DirName:/C=GB/CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net serial:C1:EE:75:75:F0:04:4F:2E ``` X509v3 Subject Alternative Name: email:sysadmins@domain.net X509v3 Issuer Alternative Name: email:sysadmins@domain.net Signature Algorithm: sha1WithRSAEncryption 75:c2:a0:37:42:19:3d:f5:a7:04:28:4f:5c:52:0f:b9:d6:cc: ... ec:93:7c:d0:3a:2d:32:86:ec:8e:21:ce:a5:dd:d2:a7:c5:d0: 7e:c2:57:2f ``` Do you accept this certificate? [y/n] y Client setup finished. Start the registration now? [y/n] y /usr/bin/suse\_register -i -L /root/.suse\_register.log Refreshing service ‘SMT-http\_ukwcmcsmt01\_odops\_uk\_domain\_net’. All services have been refreshed. Repository ‘Puppet’ is up to date. Repository ‘SBSOFT-SLE11-SP3-OS’ is up to date. Repository ‘SMT-SLE11-SDK-SP3-Pool’ is up to date. Repository ‘SMT-SLE11-SDK-SP3-updates’ is up to date. Repository ‘SMT-SLE11-SP3-Updates’ is up to date. Repository ‘ruby\_backports’ is up to date. All repositories have been refreshed. ERROR: SSL peer certificate or SSH remote key was not OK: (51) (2) ERROR: SSL peer certificate or SSH remote key was not OK: (51) (2) [/CODE] SSL connection in both cases (using IP address and using hostname) are fine: ## [CODE]# openssl s\_client -connect 10.10.10.10:443 CONNECTED(00000003) depth=1 /C=GB/CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net verify return:1 depth=0 /C=GB/CN=[ukwcmcsmt01.odops.uk.domain.net/emailAddress=sysadmins@domain.net](http://ukwcmcsmt01.odops.uk.domain.net/emailAddress=sysadmins@domain.net) verify return:1 ## Certificate chain 0 s:/C=GB/CN=[ukwcmcsmt01.odops.uk.domain.net/emailAddress=sysadmins@domain.net](http://ukwcmcsmt01.odops.uk.domain.net/emailAddress=sysadmins@domain.net) i:/C=GB/CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net 1 s:/C=GB/CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net i:/C=GB/CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net ## Server certificate -----BEGIN CERTIFICATE----- MIIEzTCCA7WgAwIBAgIBATANBgkqhkiG9w0BAQUFADBfMQswCQYDVQQGEwJHQjEm … /JKyGODS4rac/w4oT58JA9SbR2iaeGowBj1tfHRLlhR9XvhQj4tn1IqmWV1b4ygw B1TLr2GLXCeog7czfcts7YzyNsfDzhcXH0HoIcScWFgA -----END CERTIFICATE----- subject=/C=GB/CN=[ukwcmcsmt01.odops.uk.domain.net/emailAddress=sysadmins@domain.net](http://ukwcmcsmt01.odops.uk.domain.net/emailAddress=sysadmins@domain.net) issuer=/C=GB/CN=YaST Default CA (ukwcmcsmt01)/emailAddress=sysadmins@domain.net ## No client certificate CA names sent ## SSL handshake has read 2934 bytes and written 300 bytes ## New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-SHA Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : ECDHE-RSA-AES256-SHA Session-ID: 8C28DBB94229B2C4B42B1D25A144EB749C1E16075C85FCE2FF4E296153C5F8AD Session-ID-ctx: Master-Key: 735B62280C3F2BBAB355D654F239B7AF0458DF192AFD1EDBA13391B2EAB251583E2129CE4E71B1E4A225A09B375FFF1E Key-Arg : None Start Time: 1439478906 Timeout : 300 (sec) Verify return code: 0 (ok) closed[/CODE] Could you advice what could be wrong? ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [August 17, 2015, 5:13pm UTC](https://forums.suse.com/t/system-registration-through-smt-with-different-lic/27295/4 "2015-08-17T17:13:19Z")
Hi configurationmanagement, I take it the “openssl s\_client” run was from the machine you ran clientSetup4SMT.sh on previously? Does ~root/[FONT=monospace][COLOR=#000000].suse\_register.log[/COLOR] on that host have any clues on what happened and might have caused that error? Regards, Jens [/FONT]