Red Hat' a bağlanırlığın sınanması
2.3.3.4 ya da 2.3.3.5üzeriyseniz, Red Hat Satellite Server Version 6.10 sanal sistem örüntülerinin konuşlandırılması, İnternet üzerinden Red Hat ile bağlantı kurulmasını gerektirir. 2.3.3.6'ta yer alıyorsanız, Red Hat Satellite Server Sürüm 6.11 sanal sistem kalıbı ' in devreye alınması, İnternet üzerinden Red Hat ' e bağlantı kurulmasını gerektirir.
- Red Hat Ağı
- https://access.redhat.com
- subscription.rhsm.redhat.com
- Red Hat İçerik Dağıtımı Ağı
- https://cdn.redhat.com
- Önce Güvenlik
- https://ipayum.securityfirstcorp.com
Red Hat Satellite Server sanal sistem kalıbı 'i konuşlandırmayı planladığınız IP grubunda yer alan bir sanal makinenin söz konusu URL' lere erişebildiğini doğrulamanız önerilir. wget ya da curlgibi bir araç kullanın.
[virtuser@hostname1 ~]$ curl -v -k -I https://access.redhat.com/
* About to connect() to access.redhat.com port 443 (#0)
* Trying <hostname1_IPaddress>... connected
* Connected to access.redhat.com (<hostname1_IPaddress>) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
* subject: C=US; ST=NC; L=Raleigh; O=Red Hat, Inc.; OU=Web Operations;
CN=access.redhat.com
* start date: 2014-10-17 20:30:01 GMT
* expire date: 2015-10-17 20:29:57 GMT
* subjectAltName: access.redhat.com matched
* issuer: C=NL; L=Amsterdam; O=Verizon Enterprise Solutions; OU=Cybertrust;
CN=Verizon Akamai SureServer CA G14-SHA1
* SSL certificate verify ok.
> HEAD / HTTP/1.1
> User-Agent: curl/7.21.3 (x86_64-unknown-linux-gnu) libcurl/7.21.3 OpenSSL/1.0.1e
zlib/1.2.3
> Host: access.redhat.com
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Server: Apache
Server: Apache
< X-Powered-By: PHP/5.3.3
X-Powered-By: PHP/5.3.3
< X-Trace: 1B9F961738EA37FCDAC82C5B1CFD4A4D50F0CD41A2E62CB8819FEC5940
X-Trace: 1B9F961738EA37FCDAC82C5B1CFD4A4D50F0CD41A2E62CB8819FEC5940
< Content-Language: en
Content-Language: en
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
< Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
< Expires: Tue, 21 Jul 2015 14:19:14 GMT
Expires: Tue, 21 Jul 2015 14:19:14 GMT
< Date: Tue, 21 Jul 2015 14:19:14 GMT
Date: Tue, 21 Jul 2015 14:19:14 GMT
< Connection: keep-alive
Connection: keep-alive
* no chunk, no close, no size. Assume close to signal end
Veri merkezinizin içinden Internet 'e doğrudan bağlanmasanız, Internet 'e bağlanmak için ileri bir yetkili sunucu kullanabilirsiniz. https://access.redhat.com ve https://cdn.redhat.com arasındaki giden SSL bağlantısının ileri yetkili sunucu tarafından sonlandırılmadığından emin olun. Aşağıdaki örnekte, böyle bir bağlantıya ilişkin bir dış örnek gösterilmektedir; * yayıncısı ile başlayan hat, sertifika verenin bir dış taraf olduğunu gösterir. Bunun yerine, kendi kuruluşunuzda bir sertifika vereni görüyorsanız, bu, SSL bağlantısının ileriye dönük yetkili sunucu (kendi kuruluşunuz tarafından verilmiş bir sertifikası olan) tarafından sonlandırıldığını kanıtlıyor.
[virtuser@hostname1 ~]$ curl -v -k -I -x proxy.emea.ibm.com:80
https://access.redhat.com/
* About to connect() to proxy proxy.emea.ibm.com port 80 (#0)
* Trying <hostname1_IPaddress>... connected
* Connected to proxy.emea.ibm.com (<hostname1_IPaddress>) port 80 (#0)
* Establish HTTP proxy tunnel to access.redhat.com:443
> CONNECT access.redhat.com:443 HTTP/1.1
> Host: access.redhat.com:443
> User-Agent: curl/7.21.3 (x86_64-unknown-linux-gnu) libcurl/7.21.3 OpenSSL/1.0.1e
zlib/1.2.3
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
* subject: C=US; ST=NC; L=Raleigh; O=Red Hat, Inc.; OU=Web Operations;
CN=access.redhat.com
* start date: 2014-10-17 20:30:01 GMT
* expire date: 2015-10-17 20:29:57 GMT
* subjectAltName: access.redhat.com matched
* issuer: C=NL; L=Amsterdam; O=Verizon Enterprise Solutions; OU=Cybertrust;
CN=Verizon Akamai SureServer CA G14-SHA1
* SSL certificate verify ok.
> HEAD / HTTP/1.1
> User-Agent: curl/7.21.3 (x86_64-unknown-linux-gnu) libcurl/7.21.3 OpenSSL/1.0.1e
zlib/1.2.3
> Host: access.redhat.com
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Server: Apache
Server: Apache
< X-Powered-By: PHP/5.3.3
X-Powered-By: PHP/5.3.3
< Content-Language: en
Content-Language: en
< X-Cnection: close
X-Cnection: close
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
< Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
Cache-Control: no-cache, must-revalidate, post-check=0, pre-check=0
< Expires: Tue, 21 Jul 2015 14:22:26 GMT
Expires: Tue, 21 Jul 2015 14:22:26 GMT
< Date: Tue, 21 Jul 2015 14:22:26 GMT
Date: Tue, 21 Jul 2015 14:22:26 GMT
< Connection: keep-alive
Connection: keep-alive
* no chunk, no close, no size. Assume close to signal end
<
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):