Definition of UNIX target
Unix targets are defined by the operating system group that comprises:
- Solaris
- AIX
- HP-UX
These O/S can be scanned by the Illuminate 360 product but restrictions do apply of which a customer should be aware. This document attempts to identify these restrictions and associated best practices familiar to the customer. A summary of the coverage of all O/S is available on the Scanning Support Matrix.
Metrics
The following operating systems do not support the generation of O/S metrics. Metrics in this case would typically include, network traffic, CPU load, etc. taken over an extended period of time (typically 2 weeks). The collection of metrics is used by the product to identify the migration of targets to cloud equivalents by establishing the right-sizing of the target cloud environments. Right-sizing is the practice of ensuring that the cloud target environment has appropriate CPU, network, and disk resources to properly accommodate the migration.
|
Unix Target O/S |
Version Supported |
Metrics Collection |
|
Solaris |
8.x → 11.4 |
No - rightsizing cannot be generated |
|
AIX |
5.x, 6.x, 7.x |
No - rightsizing cannot be generated |
|
HP-UX |
10x, 11x |
No - rightsizing cannot be generated |
Scanning
The following information relates to scanning operations across Unix-based environments
Unique Identifier Scanning
Scanning of UNIX targets is typically based on O/S commands to generate a unique ID using commands that are “native” to O/S. Within the LINUX and Windows domains, the tools used tend to be ubiquitous across these domains. However, within UNIX, a standard set of commands is more differentiated and may or may not be present depending on O/S configuration options that have been supplied.
|
Unix Target O/S |
Version Supported |
|
|
Solaris |
8.x → 11.4 |
Uses commands Requires admin privilege escalation SUDO for inventory/scanning for credentials used for scanning. The sudo utility is considered as part of the Oracle Solaris 10 1/13 release but due to technical reasons sudo packages were released independently and they are not within Oracle Solaris 10 1/13 media |
|
AIX |
5.x, 6.x, 7.x |
Uses commands Requires availability of lsof or netstat and admin privilege escalation SUDO for inventory/scanning for credentials used for scanning |
|
HP-UX |
10x, 11x |
Uses commands Requires availability of lsof or netstat and admin privilege escalation SUDO for inventory/scanning for credentials used for scanning |
For these operating systems, is not unusual for some or all of these commands not to return enough information to allow Illuminate 360 to uniquely identify a target server. The Illuminate 360 scan of such a target will be marked with a warning stating that specific commands could not be used/did not generate enough information.
In the case that a server could not use native commands to generate a unique identifier,
Illuminate 360 provides the functionality to generate a unique identifier.
This unique identifier is written to the target and is retained for future scan operations.
The unique identifier is stored in the file:/var/tmp/CloudSphere/uuid/uniqueIdentifier.txt
All targets that cannot generate their own identifier should be moved to a separate scan job (either remove or exclude them from the original scan job).
Remediation Process for Unique Identifier
- Create a new scan job.
- Select the details tab.
- Under the “Enablings” field, add the option
EnableGeneratedID. - Once the servers within this job's scope have been scanned, they will be discovered using an Illuminate 360 generated identifier.
Disk Scanning
Within a Solaris Zones virtualized environment, the VMs that reside in the non-global zone do not have access to global disk information. This will cause a ‘partial scan’ status to be identified when scanning these server types. This is an expected scenario for these servers.