All posts by vogler

How to set dns-server and search domain in solaris 5.11

root@solaris:~# svccfg

svc:> select dns/client
svc:/network/dns/client> setprop config/nameserver = net_address: 192.168.1.14
svc:/network/dns/client> setprop config/search = astring: rocworks.local
svc:/network/dns/client> select default
svc:/network/dns/client:default> refresh
svc:/network/dns/client:default> validate

svc:/network/dns/client:default> select name-service/switch
svc:/system/name-service/switch> setprop config/host = astring: “files dns
svc:/system/name-service/switch> select default
svc:/system/name-service/switch:default> refresh
svc:/system/name-service/switch:default> validate

check the result in /etc/resolv.conf (don’t edit this file, it will be set by svc on (re)boot)

search rocworks.local
nameserver 192.168.1.14

Oracle RAC ologgerd process high cpu load…

The ologgerd is part of Oracle Cluster Health Monitor and is used by the Oracle Support to troubleshoot RAC problems. If ologgerd process is consuming a lot of CPU and writes a lot of data to disk, it can be stopped by executing on both nodes:

# crsctl stop resource ora.crf -init

to disable ologgerd permanently, execute:

# crsctl delete resource ora.crf -init

Windows uninstall nonpresent devices…

When you want to rename a network adapter and you go “Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.” You get this message for examle exwhen you changed the network card and you want to change the name of the new one to the same name the old one had.

Solution is to remove the old unused network adapter:

1.Click Start, click Run, type cmd.exe, and then press ENTER.
2.Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
3.Type Start DEVMGMT.MSC, and then press ENTER.
4.Click View, and then click Show Hidden Devices.
5.Expand the Network Adapters tree.
6.Right-click the dimmed network adapter, and then click Uninstall

Nested Virtualization/Hypervisor ESXi => HyperV….

To run HyperV in ESXi modify the vmx file of the HyperV guest vm:

vhv.enable = "TRUE"
hypervisor.cpuid.v0 = "FALSE"

To allow network communication from VMs on the HyperV over the HyperV virtual switches to the ESXi network the “Promiscuous Mode” of the ESXi network switch has to be set to “Accept” – ESXi-Host => configuration => networking => select vSwitch<X> => properties => select vSwitch => Edit => Security => Policy Exceptions => Promiscuous Mode => Accept