I am sure all of us at some point in time would have felt a need to have an infinite storage space so that there is no need to worry about adding new disks or cleaning up old/unwanted files to create more space. The fact …
The post Managing the Data Sprawl in a Cost Effective Way appeared first on Cool Solutions. Guruprasad
If Reflection Desktop is deployed directly via the installer package (*.msi) file (using a msiexec command or third-party tool) problems like the error message described in this article can occur.
1. If no VBA is desired, make sure to install Reflection via a msiexec command line with a TRANFORM file set to remove the Visual Basic for Applications feature.
Example: msiexec /I ReflectionV16.1.msi TRANSFORMS=custom.mst /qb
2. If the VBA feature is desired, deploy the additional Microsoft VBA 7.1 core and language-specific *.msi packages from the ..PrerequisitesVB71 folder via a msiexec command line.
Example: msiexec /I vba71.msi /qb for the VBA Core
msiexec /I vba71_1033.msi /qb for the English language
This release does not include support for iSeries agents or endpoints. To monitor your iSeries assets using the latest release of Secure Configuration Manager, NetIQ recommends that you use TGAudit, which provides enhanced capabilities and reporting. If you are entitled to NetIQ Security Solutions for iSeries, you can use TGAudit at no extra cost. You can download TGAudit from the download page https://download.microfocus.com/Download?buildid=ZoH3ukkXcTc~. For more information about TGAudit or migrating your data, contact your Sales Representative or Technical Support.
If you want to continue monitoring your iSeries assets using your existing agents and endpoints, you will need to use a prior version of Secure Configuration Manager installed on a separate server. You must also maintain separate databases for each version.
multipaths {
multipath {
wwid 36006048000028350131253594d303030
alias mpatha
}
multipath {
wwid 36006048000028350131253594d303041
alias mpathb
}
multipath {
wwid 36006048000028350131253594d303145
alias mpathc
}
multipath {
wwid 36006048000028350131253594d303334
alias mpathd
}
}
If root is not on multipath, but multipath is included in the initrd anyway (this can happen if root is on LVM), and user_friendly_names is used, then one should boot with the parameter “multipath=off”, to avoid problems.
This will disable multipath in the initrd only. Once the system boots, the boot.multipath and multipathd boot scripts will still be able to activate multipathing.
Concerning issue 2. it needs to be assured that the bindings file is available on the system root and multipath can find it.
This be done for example by moving the bindings file to: /etc/multipath/bindings,
and setting the option “bindings_file” in the defaults section of /etc/multipath.conf, e.g:
defaults {
user_friendly_names yes
bindings_file “/etc/multipath/bindings”
}
Note: Since SUSE Linux Enterprise Server 11 Service Pack 3 the bindings are on default already stored in /etc/multipath/bindings.
An extra entry in multipath.conf is not longer needed. (this can be checked with command: # multipath -t | grep bindings)
This document (7023272) is provided subject to the disclaimer at the end of this document.
08/15/18 09:05:27.732]:Data Collection Service Driver ST:DCSShim: BatchFileManager – Initializing state file…
[08/15/18 09:05:27.732]:Data Collection Service Driver ST:
DirXML Log Event ——————-
Driver: DENCHRIS18_TREEsystemdriverset1Data Collection Service Driver
Status: Error
Message: Code(-9010) An exception occurred: java.lang.NoClassDefFoundError: com/microfocus/database/builder/DatabaseBuilder
at com.novell.nds.dirxml.driver.dcsshim.persist.BatchFile.open(Unknown Source)
at com.novell.nds.dirxml.driver.dcsshim.persist.BatchFileManager.<init>(Unknown Source)
at com.novell.nds.dirxml.driver.dcsshim.DCSShim.init(Unknown Source)
at com.novell.nds.dirxml.engine.Driver.startShim(Driver.java:1676)
at com.novell.nds.dirxml.engine.Driver.initialize(Driver.java:329)
at com.novell.nds.dirxml.engine.Driver.<init>(Driver.java:295)
at com.novell.nds.dirxml.engine.DriverEntry.run(DriverEntry.java:626)
at java.lang.Thread.run(Thread.java:748)
[08/15/18 09:05:27.733]:Data Collection Service Driver ST:Driver terminated.
[08/15/18 09:05:27.735]:Data Collection Service Driver ST:Writing XML attribute vnd.nds.stream://DENCHRIS18_TREE/system/driverset1/Data+Collection+Service+Driver#DirXML-PersistentData.
System Requirements:
•Identity Manager 4.7.1 or higher.
•IDM Reporting Module.
Install the 4.7.1 and the driver should start.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.
snapper create -d "cleaned admin node"
cp -a /var/lib/crowbar/cache/etc/resolv.conf /etc/resolv.conf
/etc/bind/named.confExample resolv.conf:
cat >/etc/resolv.conf <<EOF
search examplecloud.suse.com
nameserver 127.0.0.1
nameserver 192.168.124.10
EOF
for service in crowbar crowbar-jobs crowbar-init tftp chef-{server,solr,expander,client} couchdb apache2 named dhcpd xinetd rabbitmq-server postgresql dnsmasq; do systemctl stop $service; donekillall epmd # part of rabbitmq
killall looper_chef_client.sh
zypper rm
`rpm -qa|grep -e crowbar -e chef -e cloud -e apache2`
couchdb createrepo erlang rabbitmq-server sleshammer yum-common
bind bind-chrootenv dhcp-server tftp
rm -rf /opt/dell/* /etc/{bind,chef,crowbar,crowbar.install.key,dhcp3,xinetd.d/tftp}
/etc/sysconfig/{dhcpd,named/*,rabbitmq-server}
/var/lib/{chef,couchdb,crowbar,dhcp,rabbitmq}
/var/run/{chef,crowbar,named/*,rabbitmq}
/var/log/{apache2,chef,couchdb,crowbar,nodes,rabbitmq}
/var/cache/chef
/var/chef
/var/lib/pgsql/*
/srv/tftpboot/{discovery/pxelinux.cfg/*,nodes,validation.pem}
killall epmd
snapper create -d "cleaned admin node"
7. Ensure admin node is resolvable, nslookup and ping works
#e.g. start dnsmasq and add ip/name to /etc/hosts as needed
systemctl start dnsmasq.servicezypper in -t pattern base cloud_admin
hostname -f" if still neededrpm -Fhv /ptf/*.rpm
10. Prepare backup in place
mkdir restore
cd restore
tar -xvf ../backup-restore.tar.gz
cp crowbar/configs/crowbar/network.json /etc/crowbar/network.json
10.2 Copy/Add hostnames to "/etc/hosts" from backup if not sufficient
cp crowbar/configs/hostname /etc/hostname
10.3 If using remote SMT add ip/name to the backup tar (not needed if reachable
via separate bastion network)
echo "10.10.10.10 smt-server.suseexample.com smt-server">> crowbar/configs/hosts
echo "10.10.10.0 192.170.124.1" >> /etc/sysconfig/network/routes
tar -czvf restore.tar.gz crowbar/ knife/ meta.yml
systemctl start crowbar-init
crowbarctl database create
snapper create -d "clean admin node prior uploading/restore backup"
crowbarctl backup upload restore.tar.gz --debug --anonymouscrowbarctl backup list
crowbarctl backup restore <name-from-list>
16 monitor progress
tail -f /var/log/apache2/*log /var/log/crowbar/*
(or access installer within browser
for service in crowbar crowbar-jobs
tftp chef-{server,solr,expander,client} couchdb apache2 named dhcpd xinetd rabbitmq-server postgresql dnsmasq; do systemctl status $service; doneThis document (7023269) is provided subject to the disclaimer at the end of this document.
Run this command to add the edir_root_ca cert to the stores:
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.
This document (7020581) is provided subject to the disclaimer at the end of this document.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.
This document (7016201) is provided subject to the disclaimer at the end of this document.
NetIQ Aegis 3.2
NetIQ Directory and Resource Administrator 9.1.x Workflow Automation 3.3
How to register DRA and Aegis interoperability DLLs.
How to configure the Aegis Business service connection for DRA.
Register the DRA Application DLLS
Import the Aegis Workflow Registry settings into the Windows Registry
After all of the above steps are completed, restart the NetIQ Administration Service
DraWcAegisUtility.dll only applies to customers using the legacy ASP Web Console.
This KB does NOT apply to versions of DRA from version 9.2 , and newer. For details on the DRA 9.2 DRA Server to Workflow Server configuration, including post upgrade steps; please see: www.netiq.com/documentation
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.
Updated Intel microcode (provided through your hardware / BIOS vendor or by SUSE) introduces a new feature called “flush_l1d”. Hypervisors and bare-metal kernels use this feature to flush the L1 data cache during operations which may be susceptible to data leakage (e.g. when switching between VMs in Hypervisor environments).
Software mitigations exist for the Linux Kernel and for Hypervisors. These mitigations include support for new CPU features, passing these features to guests, and support for enabling/disabling/tuning the mitigations. Recommended mitigations vary depending on the environment.
For KVM host environments, mitigation can be achieved through L1D cache flushes, and/or disabling Extended Page Tables (EPT) and Simultaneous MultiThreading (SMT).
kvm-intel.vmentry_l1d_flush=always
The L1D cache is flushed on every VMENTER.kvm-intel.vmentry_l1d_flush=cond
The L1D cache is flushed on VMENTER only when there can be leak of host memory between VMEXIT and VMENTER. This could still leak some host data, like address space layout.kvm-intel.vmentry_l1d_flush=never
Disables the L1D cache flush mitigation.
The default setting here is “cond”.
The l1tf “full” setting overrides the settings of this configuration variable.
kvm-intel.enable_ept=0
The Extended Page tables support is switched off.
To eliminate the risk of untrusted processes or guests exploiting this vulnerability on a sibling hyper-thread, Simultaneous MultiThreading (SMT) can be disabled completely.
On the kernel boot command line:
nosmt
SMT is disabled, but can be later reenabled in the system.nosmt=force
SMT is disabled, and can not be reenabled in the system.
If this option is not passed, SMT is enabled. Any SMT options used with the “l1tf” kernel parameter option overrides this “nosmt” option.
/sys/devices/system/cpu/smt/control
This file allows to read the current control state and allows to disable or (re)enable SMT.
Possible states are:
on
SMT is supported and enabled.off
SMT is supported, but disabled. Only primary SMT threads can be onlined.forceoff
SMT is supported, but disabled. Further control is not possible.notsupported
SMT is not supported.
Potential values that can be written into this file:
on
off
forceoff
/sys/devices/system/cpu/smt/active
This file contains the state of SMT, if it is enabled and active, where active means that multiple threads run on 1 core.
pv-l1tf=[ <bool>, dom0=<bool>, domu=<bool> ]
HVM guests achieve mitigation through a combination of L1D flushes, and disabling SMT.
This parameter determines whether or not the Xen hypervisor performs L1D flushes on VMEntry. Regardless of this setting, this feature is virtualized and passed to HVM guests for in-guest mitigation.
WARNING – The combination of Meltdown mitigation (KPTI) and shadow mode on hardware which supports PCID can result in a severe performance degradation.
NOTE – Efforts are ongoing to implement scheduling improvements that allow hyper-thread siblings to be restricted to threads from a single guest. This will reduce the exposure of L1TF, and the requirement to disable SMT in many environments.