On the day of writing, the newest version of Solaris 10 is u11 (1\/13) and Cluster (for Solaris 10) is 3.3u2.
\nCluster 3.2 is still supported by Oracle, but patches are no longer released. Update 11 for Solaris 10 is probably last Release of Solaris 10 and has some new features, which are not available if you only patching a system with Recommended Patches.
\nBefore starting with upgrade it is good to check and fix any issues with current system and environment.
\nPlease check a Cluster status, Quorum device status, running services, zpools, metadevices, metasets, hardware components etc.
\nIf you have any issues, fix them before you start. Plan your Maintenance Window, make backup of your files and configuration.
\n
\nNow let’s check which Solaris Release and Cluster Release is installed:<\/p>\n
\r\n$ cat \/etc\/release\r\n Oracle Solaris 10 9\/10 s10s_u9wos_14a SPARC\r\n Copyright (c) 2010, Oracle and\/or its affiliates. All rights reserved.\r\n Assembled 11 August 2010\r\n$ cat \/etc\/cluster\/release\r\n Sun Cluster 3.2u1 for Solaris 10 sparc\r\n Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.\r\n<\/pre>\nIf you have the newest version of OS or Cluster, you can just omit related part of this article.
\nPrepare ISO with Solaris 10 u11, Recommended Patch Cluster, LU patch, Cluster 3.3u2 package and newest Cluster Core patch. You can download binaries from Oracle after login to Oracle Support. If you don’t have account, you can create it. AFAIK Contract is not needed to download software and patches.
\nCopy above software to servers and unpack in local directory. Do not use shared directory from NFS, because you will not be able to install patches. Leave ISO image as is, it will be mounted as lofs.
\nA propos lofs: if you have automounter (autofs service) and SUNW.nfs resource enabled, you probably have lofs disabled in your \/etc\/system.<\/p>\n\r\n# grep lofs \/etc\/system\r\nexclude: lofs\r\n<\/pre>\nIn that case, before you start OS Release upgrade you will need to enable lofs (remove or comment above line in \/etc\/system) and reboot. There is no other way, sorry.
\nLet’s start with preparation phase, I will use \/var\/tmp\/patching as software dir and \/mnt as ISO\/ABE dir. To \/var\/tmp\/patching\/prereq I copied patches which is good to have installed before Alternate Boot Environment creation and patching. This is my list:
\n119254-92
\n121428-15
\n121430-93
\n140914-02
\n142911-01
\n142933-05
\n146578-06
\n148027-06<\/p>\n\r\n# mkdir \/var\/tmp\/patching && cd \/var\/tmp\/patching\r\n# unzip -q 10_Recommended.zip && rm 10_Recommended.zip\r\n# cd prereq\r\n# for a in `ls *.zip`; do unzip -q $a && rm $a; done\r\n# for a in `ls *`; do patchadd $a; done\r\n# cd ..\r\n<\/pre>\nDo not worry if one or more of above patches won’t install, the most important patch is 121430-XX, which is Live Upgrade Patch. Without this patch your chances to hit a bug with ABE creation are significally increased. For x86 systems this patch has number increased by one: 121431-XX.
\nNow it’s time to apply Prereq patches from Recommended Patch Cluster:<\/p>\n\r\n# cd \/var\/tmp\/patching\/10_Recommended\r\n# .\/installpatchset --apply-prereq --s10patchset\r\nRecommended OS Patchset Solaris 10 SPARC (2015.12.24)\r\n\r\nApplication of patches started : 2016.02.19 07:23:42\r\n\r\nApplying 120900-04 ( 1 of 10) ... skipped\r\nApplying 121133-02 ( 2 of 10) ... skipped\r\nApplying 119254-92 ( 3 of 10) ... skipped\r\nApplying 119317-01 ( 4 of 10) ... skipped\r\nApplying 121296-01 ( 5 of 10) ... skipped\r\nApplying 138215-02 ( 6 of 10) ... success\r\nApplying 148336-02 ( 7 of 10) ... success\r\nApplying 146054-07 ( 8 of 10) ... skipped\r\nApplying 142251-02 ( 9 of 10) ... skipped\r\nApplying 125555-16 (10 of 10) ... success\r\n\r\nApplication of patches finished : 2016.02.19 07:25:41\r\n\r\nFollowing patches were applied :\r\n 138215-02 148336-02 125555-16\r\n\r\nFollowing patches were skipped :\r\n Patches already applied\r\n 120900-04 119254-92 121296-01 146054-07 142251-02\r\n 121133-02 119317-01\r\n\r\nInstallation of prerequisite patches complete.\r\n\r\nInstall log files written :\r\n \/var\/sadm\/install_data\/s10s_rec_patchset_short_2016.02.19_07.23.42.log\r\n \/var\/sadm\/install_data\/s10s_rec_patchset_verbose_2016.02.19_07.23.42.log\r\n<\/pre>\nIt’s about 10 patches which should be installed on running system before patching. Patch the system before patching the system \ud83d\ude42
\nNow we will create an Alternate Boot Environment (ABE). If you have root filesystem on ZFS, just make:<\/p>\n\r\n# lucreate -c CURRENT_NAME -n NEW_BE_NAME\r\n<\/pre>\nand that’s all. ZFS snapshots will be created and new ZFS filesystems for ABE. You can check this with ‘zfs list’ and ‘lustatus’ commands.
\nIf you have UFS mirror for root filesystem, you need to split mirror and create ABE on deattached metadevice. But first you need to remove ‘global’ option from \/etc\/vfstab for \/global\/.devices\/node@X. Make a copy, use your favorite editor and replace ‘global’ with ‘-‘, like below:<\/p>\n\r\n#\/dev\/md\/dsk\/d1160 \/dev\/md\/rdsk\/d1160 \/global\/.devices\/node@1 ufs 2 no global\r\n\/dev\/md\/dsk\/d1160 \/dev\/md\/rdsk\/d1160 \/global\/.devices\/node@1 ufs 2 no -\r\n<\/pre>\nAnd the same on other Cluster nodes.
\nLet’s assume that metadevices and mountpoints are like follows:<\/p>\n\r\nd1160 m 516MB d1161 d1162\r\n d1161 s 516MB c0t2d0s6\r\n d1162 s 516MB c0t3d0s6\r\nd1130 m 19GB d1131 d1132\r\n d1131 s 19GB c0t2d0s3\r\n d1132 s 19GB c0t3d0s3\r\nd1100 m 43GB d1101 d1102\r\n d1101 s 43GB c0t2d0s0\r\n d1102 s 43GB c0t3d0s0\r\nd1110 m 4.0GB d1111 d1112\r\n d1111 s 4.0GB c0t2d0s1\r\n d1112 s 4.0GB c0t3d0s1\r\n<\/pre>\n\r\n\/dev\/md\/dsk\/d1110 - - swap - no -\r\n\/dev\/md\/dsk\/d1100 \/dev\/md\/rdsk\/d1100 \/ ufs 1 no -\r\n\/dev\/md\/dsk\/d1130 \/dev\/md\/rdsk\/d1130 \/export ufs 2 yes -\r\n#\/dev\/md\/dsk\/d160 \/dev\/md\/rdsk\/d160 \/globaldevices ufs 2 yes -\r\n\/devices - \/devices devfs - no -\r\nctfs - \/system\/contract ctfs - no -\r\nobjfs - \/system\/object objfs - no -\r\nswap - \/tmp tmpfs - yes -\r\n\/dev\/md\/dsk\/d1160 \/dev\/md\/rdsk\/d1160 \/global\/.devices\/node@1 ufs 2 no global\r\n<\/pre>\nI will use truss to collect output during lucreate in case of any issues:<\/p>\n
\r\ntruss -o lucreate.out -elaf \\\r\n lucreate -c s10 -n s10u11_20160219 \\\r\n -m \/:\/dev\/md\/dsk\/d100:ufs,mirror -m \/:\/dev\/md\/dsk\/d1102:detach,attach,preserve \\\r\n -m \/export:\/dev\/md\/dsk\/d130:ufs,mirror -m \/export:\/dev\/md\/dsk\/d1132:detach,attach,preserve \\\r\n -m -:\/dev\/md\/dsk\/d110:swap,mirror -m -:\/dev\/md\/dsk\/d1112:detach,attach,preserve \\\r\n -m \/global\/.devices\/node@1:\/dev\/md\/dsk\/d160:ufs,mirror \\\r\n -m \/global\/.devices\/node@1:\/dev\/md\/dsk\/d1162:detach,attach,preserve\r\n<\/pre>\nThere is another school, which tells that one should split mirror manually and then make a lucreate, but above scenario is much faster, because data are up to date, and lucreate does not need to copy them. ABE creation process looks as follows:<\/p>\n
\r\nDetermining types of file systems supported\r\nValidating file system requests\r\nPreparing logical storage devices\r\nPreparing physical storage devices\r\nConfiguring physical storage devices\r\nConfiguring logical storage devices\r\nAnalyzing system configuration.\r\nUpdating boot environment description database on all BEs.\r\nUpdating system configuration files.\r\nThe device <\/dev\/dsk\/c0t3d0s0> is not a root device for any boot environment; cannot get BE ID.\r\nCreating configuration for boot environment <s10u11_20160219>.\r\nSource boot environment is <s10>.\r\nCreating file systems on boot environment <s10u11_20160219>.\r\nCreating <ufs> file system for <\/> in zone <global> on <\/dev\/md\/dsk\/d100>.\r\nCreating <ufs> file system for <\/export> in zone <global> on <\/dev\/md\/dsk\/d130>.\r\nCreating <ufs> file system for <\/global\/.devices\/node@1> in zone <global> on <\/dev\/md\/dsk\/d160>.\r\nMounting file systems for boot environment <s10u11_20160219>.\r\nCalculating required sizes of file systems for boot environment <s10u11_20160219>.\r\nPopulating file systems on boot environment <s10u11_20160219>.\r\nAnalyzing Primary boot environment.\r\nProcessing alternate boot environment.\r\nMounting ABE <s10u11_20160219>.\r\nCloning mountpoint directories.\r\nGenerating list of files to be copied to ABE.\r\nCopying data from PBE <s10> to ABE <s10u11_20160219>.\r\n100% of filenames transferred\r\nFinalizing ABE.\r\nUnmounting ABE <s10u11_20160219>.\r\nReverting state of zones in PBE <S10U11>.\r\nMaking boot environment <s10u11_20160219> bootable.\r\nSetting root slice to Solaris Volume Manager metadevice <\/dev\/md\/dsk\/d100>.\r\nPopulation of boot environment <s10u11_20160219> successful.\r\nCreation of boot environment <s10u11_20160219> successful.\r\n<\/pre>\nIf you have any issues with ABE creation please check: if LU patch (121430-XX or 121431-XX for x86) is installed, if metadevice names are OK, if you didn’t make a typo in lucreate command etc. If you believe that everything is OK, analyze truss output or send it to Oracle Support. If you made a typo and mirrors are already splitted, do not worry, just do ‘old school’ lucreate, like that.<\/p>\n
\r\ntruss -o lucreate1.out -elaf \\\r\n lucreate -c s10 -n s10u11_20160219 \\\r\n -m \/:\/dev\/md\/dsk\/d100:ufs \\\r\n -m \/export:\/dev\/md\/dsk\/d130:ufs \\\r\n -m -:\/dev\/md\/dsk\/d110:swap \\\r\n -m \/global\/.devices\/node@1:\/dev\/md\/dsk\/d160\r\n<\/pre>\nYou will need to wait some time for data synchronization betweend current and new BE. Check BE with lustatus:<\/p>\n
\r\n# lustatus\r\nBoot Environment Is Active Active Can Copy\r\nName Complete Now On Reboot Delete Status\r\n-------------------------- -------- ------ --------- ------ ----------\r\ns10 yes yes yes no -\r\ns10u11_20160219 yes no no yes -\r\n<\/pre>\nAfter ABE creation you should revert ‘global’ option in \/etc\/vfstab.
\nNow it’s time to upgrade OS Release on ABE if it’s older than u11 (1\/13). Mount the Solaris 10 u11 ISO image and make luupgrade:<\/p>\n\r\n# lofiadm -a \/var\/tmp\/patching\/sol-10-u11-ga-sparc-dvd.iso\r\n\/dev\/lofi\/1\r\n# mount -F hsfs \/dev\/lofi\/1 \/mnt\r\n# echo "autoreg=disable" > \/var\/tmp\/patching\/no-autoreg\r\n# luupgrade -u -s \/mnt -k \/var\/tmp\/patching\/no-autoreg -n s10u11_20160115\r\n<\/pre>\nThis will take a while, so let’s make some coffee \ud83d\ude42
\nIf you have troubles with luupgrade like ‘ERROR: Cannot mount miniroot at …’, scroll up and read about ‘lofs’, you will need additional reboot to go further.
\nAfter successful upgrade it’s time for patching ABE.<\/p>\n\r\n# umount \/mnt\r\n# lofiadm -d \/dev\/lofi\/1\r\n# cd \/var\/tmp\/patching\/10_Recommended\r\n# .\/installpatchset -B s10u11_20160219 --s10patchset\r\n\r\nRecommended OS Patchset Solaris 10 SPARC (2015.12.24)\r\n\r\nApplication of patches started : 2016.02.19 10:55:21\r\n<\/pre>\nThis will also take some time, but finally you should receive:<\/p>\n
\r\nApplication of patches finished : 2016.02.19 14:09:45\r\n\r\n\r\nFollowing patches were applied :\r\n 118666-86 125731-12 148031-05 149175-09 150537-01\r\n 118667-86 126206-11 148049-04 149279-04 150539-01\r\n...\r\nInstallation of patch set to alternate boot environment complete.\r\n\r\nPlease remember to activate boot environment s10u11_20160219 with luactivate(1M)\r\nbefore rebooting.\r\n\r\nInstall log files written :\r\n \/.alt.s10u11_20160219\/var\/sadm\/install_data\/s10s_rec_patchset_short_2016.02.19_10.55.21.log\r\n \/.alt.s10u11_20160219\/var\/sadm\/install_data\/s10s_rec_patchset_verbose_2016.02.19_10.55.21.log\r\n<\/pre>\nIf you don’t have Solaris Cluster installed or you have already newest version with patches, you can just activate new BE with luactivate and reboot system to new Release and Patchstand. DO NOT use ‘reboot’ nor ‘halt’, you need to use ‘init’ command.
\nIf you want to upgrade Cluster, let me continue. Mount ABE and upgrade Cluster Framework:<\/p>\n\r\n# lumount s10u11_20160219 \/mnt\r\n# cd \/var\/tmp\/patching\/SC-3.3\/\r\n# cd Solaris_sparc\/Product\/sun_cluster\/Solaris_10\/Tools\r\n# .\/scinstall -u update -R \/mnt\r\n\r\nStarting upgrade of Oracle Solaris Cluster framework software\r\n\r\nSaving current Oracle Solaris Cluster configuration\r\nDo not boot this node into cluster mode until upgrade is complete.\r\nRenamed "\/mnt\/etc\/cluster\/ccr" to "\/mnt\/etc\/cluster\/ccr.upgrade".\r\n\r\n** Removing Oracle Solaris Cluster framework packages **\r\n...\r\n** Installing SunCluster 3.3 framework **\r\n SUNWscu.....done\r\n SUNWsccomu..done\r\n...\r\nRestored \/mnt\/etc\/cluster\/ccr.upgrade to \/mnt\/etc\/cluster\/ccr\r\nCompleted Oracle Solaris Cluster framework upgrade\r\nUpdating nsswitch.conf ... done\r\nLog file - \/mnt\/var\/cluster\/logs\/install\/scinstall.upgrade.log.20131\r\n<\/pre>\nNow upgrade Cluster Agents:<\/p>\n
\r\n# cd \/mnt\/usr\/cluster\/bin\r\n# .\/scinstall -u update -R \/mnt -s all -d \/var\/tmp\/patching\/SC-3.3\/Solaris_sparc\/Product\/sun_cluster_agents\r\nStarting upgrade of Oracle Solaris Cluster data services agents\r\n\r\nList of upgradable data services agents:\r\n (*) indicates selected for upgrade.\r\n * nfs\r\n** Removing HA-NFS for Oracle Solaris Cluster **\r\n Removing SUNWscnfs...done\r\n\r\n** Installing Oracle Solaris Cluster HA for NFS **\r\n SUNWscnfs...done\r\n\r\nCompleted upgrade of Oracle Solaris Cluster data services agents\r\nLog file - \/mnt\/var\/cluster\/logs\/install\/scinstall.upgrade.log.13042\r\n<\/pre>\nAnd apply the newest Cluster Core Patch:<\/p>\n
\r\n# cd \/var\/tmp\/patching\/SC-3.3\r\n# patchadd -R \/mnt 145333-34\r\n<\/pre>\nDon’t forget to set ‘global’ option in new vfstab, then umount ABE:<\/p>\n
\r\n# vi \/mnt\/etc\/vfstab\r\n# luumount \/mnt\r\n<\/pre>\nMake the same for all nodes in your Cluster, and wait for Maintenance Window to switch Boot Environments.<\/p>\n
What to do during Maintenance Window?
\nIt’s good to upgrade Firmware if you don’t have newest already installed, so download it and upload to Service Controller or TFTP\/FTP server.
\nCheck cluster and quorum status once again:<\/p>\n\r\n# cluster status\r\n# clq status\r\n# clrg status\r\n<\/pre>\nCheck and remove mediators from metasets, if any:<\/p>\n
\r\n# medstat -s metaset1\r\n# metaset -s metaset1 -d -m NODE1 NODE2\r\n# medstat -s metaset1\r\n<\/pre>\nEvacuate first node and activate new BE:<\/p>\n
\r\n# clnode evacuate NODE1\r\n# luactivate s10u11_20160219\r\n# lustatus\r\nBoot Environment Is Active Active Can Copy\r\nName Complete Now On Reboot Delete Status\r\n-------------------------- -------- ------ --------- ------ ----------\r\ns10 yes yes no no -\r\ns10u11_20160219 yes no yes no -\r\n<\/pre>\nShutdown node with ‘init 0’, DO NOT use ‘reboot’ nor ‘halt’<\/p>\n
\r\n# init 0\r\n<\/pre>\nLeave this node down, you can upgrade Firmware if there is any new.
\nMake the same steps, starting with ‘clnode evacuate NODEx’ for all nodes in Cluster.
\nNow you should start nodes in opposite order, so first boot a node, which was last stopped, and then join other nodes to Cluster.
\nThat’s almost all. Almost, because resource types should be upgraded now:<\/p>\n\r\n# clrs list -v\r\n# clrt show -v |grep Upgrade\r\n<\/pre>\nThis will show what types of resources are used and when they can be upgraded. Most of them can be upgraded ‘Anytime’ or ‘When unmonitored’, so downtime is not needed. Lets’s do this for HAStoragePlus and LogicalHostname resources:<\/p>\n
\r\n# clrt register HAStoragePlus\r\n# clrt register SUNW.LogicalHostname\r\n# clrt show -v |grep Upgrade\r\n --- Upgrade tunability for Resource Type SUNW.HAStoragePlus:10 ---\r\n Upgrade from 9: When unmonitored\r\n Upgrade from 8: When unmonitored\r\n Upgrade from 7: When unmonitored\r\n Upgrade from 6: When unmonitored\r\n --- Upgrade tunability for Resource Type SUNW.LogicalHostname:4 ---\r\n Upgrade from 3: Anytime\r\n Upgrade from 2: Anytime\r\n\r\n# for a in `clrs list -v|grep SUNW.HAStoragePlus:6|cut -d" " -f1`; do \r\n> clrs unmonitor $a\r\n> clrs set -p Type_version=10 $a\r\n> clrs monitor $a\r\n> done\r\n# clrt unregister HAStoragePlus:6\r\n#\r\n# for a in `clrs list -v|grep SUNW.LogicalHostname:2|cut -d" " -f1`; do \r\n> clrs set -p Type_version=4 $a\r\n> done\r\n# clrt set -p RT_system=False SUNW.LogicalHostname:2\r\n# clrt unregister SUNW.LogicalHostname:2\r\n<\/pre>\nThat’s all folks, good luck!
\nPssst! Don’t forget to delete old BE and reattach disk to mirror to have redundancy back on UFS.
\n<\/p>","protected":false},"excerpt":{"rendered":"Sorry, this entry is only available in Polish. For the sake of viewer convenience, the content is shown below in the alternative language. You may click the link to switch the active language.Na dzi\u015b...<\/p>\n","protected":false},"author":1,"featured_media":663,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_newsletter_tier_id":0,"footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[108,126],"tags":[125,9,124],"jetpack_publicize_connections":[],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2016\/02\/Solaris_OS_logo.png?fit=800%2C393&ssl=1","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p7M9Tz-9a","jetpack-related-posts":[{"id":314,"url":"https:\/\/drfugazi.eu.org\/en\/instalacja-solarisa-10-cddvd\/","url_meta":{"origin":568,"position":0},"title":"Instalacja Solarisa 10 z CD\/DVD","author":"","date":"Wednesday December 10th, 2008","format":false,"excerpt":"Instalacja z CD\/DVD to spos\u00f3b wymagaj\u0105cy najmniej zachodu i znajomo\u015bci systemu. Instalowania z CD nie polecam, je\u015bli masz mo\u017cliwo\u015b\u0107 to u\u017cyj DVD, je\u015bli nie, to sprawd\u017a w dokumentacji jak wznowi\u0107 instalacj\u0119 po 1-szej p\u0142ycie CD, bo pami\u0119tam, \u017ce si\u0119 z tym kiedy\u015b gimnastykowa\u0142em. Instalacja z DVD nie stwarza problem\u00f3w, oczywi\u015bcie\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":95,"url":"https:\/\/drfugazi.eu.org\/en\/","url_meta":{"origin":568,"position":1},"title":"01.01. CD\/DVD","author":"drfugazi","date":"Wednesday December 10th, 2008","format":false,"excerpt":"Instalacja z CD\/DVD to spos\u00f3b wymagaj\u0105cy najmniej zachodu i znajomo\u015bci systemu. Instalowania z CD nie polecam, je\u015bli masz mo\u017cliwo\u015b\u0107 to u\u017cyj DVD, je\u015bli nie, to sprawd\u017a w dokumentacji jak wznowi\u0107 instalacj\u0119 po 1-szej p\u0142ycie CD, bo pami\u0119tam, \u017ce si\u0119 z tym kiedy\u015b gimnastykowa\u0142em. Instalacja z DVD nie stwarza problem\u00f3w, oczywi\u015bcie\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":313,"url":"https:\/\/drfugazi.eu.org\/en\/instalacja-systemu-solaris-10\/","url_meta":{"origin":568,"position":2},"title":"Instalacja systemu Solaris 10","author":"","date":"Wednesday December 10th, 2008","format":false,"excerpt":"Solarisa mo\u017cna zainstalowa\u0107 na kilka sposob\u00f3w. Najpro\u015bciej zapewne jest w\u0142o\u017cy\u0107 p\u0142ytk\u0119 DVD do nap\u0119du, usi\u0105\u015b\u0107 przy konsoli graficznej, klawiaturze, myszce i wyklika\u0107 opcje. Ale takim sposobem to si\u0119 instaluje pojedyncze instancje na potrzeby Desktopu lub ma\u0142ych instalacji serwerowych. Kiedy jest ju\u017c nieco wi\u0119cej maszyn, a szczeg\u00f3lnie gdy chcesz budowa\u0107 instalacj\u0119\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":176,"url":"https:\/\/drfugazi.eu.org\/en\/","url_meta":{"origin":568,"position":3},"title":"01.03. Custom JumpStart","author":"drfugazi","date":"Monday June 1st, 2009","format":false,"excerpt":"Custom JumpStart to obecnie najcz\u0119\u015bciej wykorzystywany przeze mnie spos\u00f3b instalacji Solarisa. Polega on na przygotowaniu serwera instalacji i zdefiniowaniu regu\u0142 dla poszczeg\u00f3lnych klient\u00f3w. Klient\u00f3w mo\u017cemy rozr\u00f3\u017cnia\u0107 ze wzgl\u0119du na architektur\u0119, ilo\u015b\u0107 pami\u0119ci RAM, ilo\u015b\u0107 i\/lub pojemno\u015b\u0107 dysk\u00f3w itp. itd. Mo\u017cna te\u017c zrobi\u0107 regu\u0142y dla konkretnych klient\u00f3w, identyfikuj\u0105c ich np. po\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":685,"url":"https:\/\/drfugazi.eu.org\/en\/autofs-in-ldap-configuration-linux-solaris\/","url_meta":{"origin":568,"position":4},"title":"Autofs in LDAP configuration – for Linux and Solaris","author":"drfugazi","date":"Friday November 25th, 2016","format":false,"excerpt":"If you have LDAP server as user repository it is also good to have NFS server to store their home directories. To avoid autofs map configuration on every host, you can use LDAP service to store maps. I assume that NFS server (NFSHOME) is already installed, LDAP server and client\u2026","rel":"","context":"In "LDAP"","block_context":{"text":"LDAP","link":"https:\/\/drfugazi.eu.org\/en\/category\/ldap\/"},"img":{"alt_text":"LDAP DIT","src":"https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2016\/06\/LDAP-DIT.jpg?fit=1200%2C1016&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2016\/06\/LDAP-DIT.jpg?fit=1200%2C1016&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2016\/06\/LDAP-DIT.jpg?fit=1200%2C1016&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2016\/06\/LDAP-DIT.jpg?fit=1200%2C1016&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/drfugazi.eu.org\/wp-content\/uploads\/2016\/06\/LDAP-DIT.jpg?fit=1200%2C1016&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":316,"url":"https:\/\/drfugazi.eu.org\/en\/instalacja-solarisa-10-custom-jumpstart\/","url_meta":{"origin":568,"position":5},"title":"Instalacja Solarisa 10 przez Custom JumpStart","author":"","date":"Monday June 1st, 2009","format":false,"excerpt":"Custom JumpStart to obecnie najcz\u0119\u015bciej wykorzystywany przeze mnie spos\u00f3b instalacji Solarisa. Polega on na przygotowaniu serwera instalacji i zdefiniowaniu regu\u0142 dla poszczeg\u00f3lnych klient\u00f3w. Klient\u00f3w mo\u017cemy rozr\u00f3\u017cnia\u0107 ze wzgl\u0119du na architektur\u0119, ilo\u015b\u0107 pami\u0119ci RAM, ilo\u015b\u0107 i\/lub pojemno\u015b\u0107 dysk\u00f3w itp. itd. Mo\u017cna te\u017c zrobi\u0107 regu\u0142y dla konkretnych klient\u00f3w, identyfikuj\u0105c ich np. po\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts\/568"}],"collection":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/comments?post=568"}],"version-history":[{"count":13,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts\/568\/revisions"}],"predecessor-version":[{"id":709,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/posts\/568\/revisions\/709"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/media\/663"}],"wp:attachment":[{"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/media?parent=568"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/categories?post=568"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/drfugazi.eu.org\/en\/wp-json\/wp\/v2\/tags?post=568"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}