Mandalika's scratchpad | [ Work blog @Oracle | My Music Compositions ] |
Old Posts: 09.04 10.04 11.04 12.04 01.05 02.05 03.05 04.05 05.05 06.05 07.05 08.05 09.05 10.05 11.05 12.05 01.06 02.06 03.06 04.06 05.06 06.06 07.06 08.06 09.06 10.06 11.06 12.06 01.07 02.07 03.07 04.07 05.07 06.07 08.07 09.07 10.07 11.07 12.07 01.08 02.08 03.08 04.08 05.08 06.08 07.08 08.08 09.08 10.08 11.08 12.08 01.09 02.09 03.09 04.09 05.09 06.09 07.09 08.09 09.09 10.09 11.09 12.09 01.10 02.10 03.10 04.10 05.10 06.10 07.10 08.10 09.10 10.10 11.10 12.10 01.11 02.11 03.11 04.11 05.11 07.11 08.11 09.11 10.11 11.11 12.11 01.12 02.12 03.12 04.12 05.12 06.12 07.12 08.12 09.12 10.12 11.12 12.12 01.13 02.13 03.13 04.13 05.13 06.13 07.13 08.13 09.13 10.13 11.13 12.13 01.14 02.14 03.14 04.14 05.14 06.14 07.14 09.14 10.14 11.14 12.14 01.15 02.15 03.15 04.15 06.15 09.15 12.15 01.16 03.16 04.16 05.16 06.16 07.16 08.16 09.16 12.16 01.17 02.17 03.17 04.17 06.17 07.17 08.17 09.17 10.17 12.17 01.18 02.18 03.18 04.18 05.18 06.18 07.18 08.18 09.18 11.18 12.18 01.19 02.19 05.19 06.19 08.19 10.19 11.19 05.20 10.20 11.20 12.20 09.21 11.21 12.22
To check if memory blacklist operation by LDoms Manager (ldm
) is in progress, run:
echo "zeus ::print -a zeus_t mem_blacklist_inprog" | mdb -p `pgrep ldmd`
If no blacklist operation is in progress, the above may return output that is similar to:
<hex-address> mem_blacklist_inprog = 0 (false)
When a memory blacklist operation is in progress, the above may return output that is similar to:
<hex-address> mem_blacklist_inprog = 0x1 (true)
In such a situation, any attempt to run ldm
commands related to memory management may fail with error:
A memory blacklist operation is being processed. Other memory operations are disabled until it completes
Sometimes a power cycle may clear the blacklist operation. In not-so-lucky situations, the affected DIMM(s) may have to be serviced.
(Credit: Eunice M.)
If two nodes [running Solaris] on a network share the same IP address, Solaris kernel detects the duplicate address, marks it as duplicate
and eventually disables and turns off the IP interface if the problem persists. These actions are typically recorded in the system log with warnings such as the following.
Dec 23 16:46:18 some-host ip: [ID 759807 kern.warning] WARNING: net0 has duplicate address xx.xx.xx.xx (in use by 00:10:e0:5d:9c:83); disabled Dec 23 16:46:18 some-host in.routed[737]: [ID 238047 daemon.warning] interface net0 to xx.xx.xx.xx turned off
When the IP interface was disabled/turned off, ipadm show-if
shows down
state for that interface.
Once the problem was discovered and fixed [by the administrator or user] to avoid duplication of IP address, Solaris kernel enables and brings up the IP interface that it turned off earlier upon detecting a duplicate IP address. This action too is recorded in the system log.
Dec 23 16:51:18 some-host ip: [ID 636139 kern.notice] NOTICE: recovered address ::ffff:xx.xx.xx.xx on net0
Once the system marks an interface down due to the conflicting IP address in a remote system, the local system checks periodically to see if the conflict persists. In Solaris 11.3, the time between the checks is 300,000 milliseconds (300 seconds or 5 minutes). However in some cases waiting for 5 minutes might not be desirable. In such cases, the time between the duplicate IP address checks can be tuned by modifying the IP tunable parameter, _dup_recovery
, to appropriate value.
eg.,
Reduce the _dup_recovery
value to 90 seconds.
Temporary change (non-persistent)
# ndd -get /dev/ip ip_dup_recovery 300000 # ndd -set /dev/ip ip_dup_recovery 90000 # ndd -get /dev/ip ip_dup_recovery 90000
Permanent change (persistent across reboots)
# ipadm show-prop -p _dup_recovery ip PROTO PROPERTY PERM CURRENT PERSISTENT DEFAULT POSSIBLE ip _dup_recovery rw 300000 -- 300000 0-3600000 # ipadm set-prop -p _dup_recovery=90000 ip # ipadm show-prop -p _dup_recovery ip PROTO PROPERTY PERM CURRENT PERSISTENT DEFAULT POSSIBLE ip _dup_recovery rw 90000 90000 300000 0-3600000
Notice the slight difference in parameter names when ndd
and ipadm
were used to tune the same value.
pkg list
on target system shows this information.
# pkg list | grep "group/system/solaris" | grep server group/system/solaris-minimal-server 0.5.11-0.175.3.1.0.5.0 i--
List all packages that are part of the group package that was installed by running:
pkg list -as `pkg contents -r -H -o fmri -t depend -a type=group <group-package>`
List available group packages to install Solaris server:
# pkg search solaris-*-server | awk '{ print $3 "\t" $4}' VALUE PACKAGE solaris/group/system/solaris-large-server pkg:/group/system/solaris-large-server@0.5.11-0.175.3.1.0.5.0 solaris/group/system/solaris-minimal-server pkg:/group/system/solaris-minimal-server@0.5.11-0.175.3.1.0.5.0 solaris/group/system/solaris-small-server pkg:/group/system/solaris-small-server@0.5.11-0.175.3.1.0.5.0
solaris-large-server
provides an Oracle Solaris large server environment that contain all of the common network services that an enterprise server must provide. Hardware drivers that are required for servers such as InfiniBand drivers are also part of this group package.
solaris-small-server
installs a smaller set of packages on a server and provides command-line environment
solaris-minimal-server
installs the smallest possible set of Solaris packages which provides a minimal command-line environment
In addition to the above, solaris/group/system/solaris-desktop
group package provides Solaris desktop environment. This package contains the GNOME desktop environment that includes GUI applications such as web browsers and mail clients, and drivers for graphics and audio devices.
Keep in mind that solaris-desktop
group package has a lot more packages compared to the other three group packages outlined above.
On target system, locate the AI manifest file that was used to perform the Solaris installation at:
/var/log/install/ai.xml
Installation log can also be found in the same directory.
pkg history
shows command history related to a specific package or all packages installed on the system. This includes information such as who initiated the package operation, the complete command, how long it took to complete the operation, whether a new boot environment (BE) was created and the errors encountered, if any.
Refer to pkg(1)
man page for the options and description.
Fancy Separator Credit: jkneb
Labels: ldm solaris tips pkg
2004-2019 |