IBM AIX OS
CloudFabrix RDA provides out of the box agent-less integration for inventory data collection from AIX server OS editions using SSH protocol. Using this integration, inventory data like AIX OS version, server make & model, running services and processes and TCP/UDP network connections will be collected.
AIX (Advanced Interactive eXecutive) is a proprietary UNIX operating system developed and maintained by IBM. It is designed for enterprise-level systems and runs on IBM's Power Systems servers. AIX is known for its reliability, scalability, and robustness, making it popular for mission-critical applications in industries.
Using RDA's integration with AIX Server OS, below are the two primary use cases that are supported and consumed within the CloudFabrix Asset Intelligence and AIOps platforms
-
AIX Server OS inventory
-
Application Dependency
1. AIX OS Inventory
1.1 Prerequisites
Supported AIX server OS distributions version 6.1 and above. SSH user account that is used to connect and collect the data should have sudo privileges for the below commands.
-
/usr/sbin/netstat -Aan
-
/usr/sbin/lsof -RnP
-
/usr/sbin/lsdev -Cc disk
-
/usr/bin/lsmpio
-
/usr/bin/lsmpio -ar
-
/usr/bin/lsmpio -ql {disk_name}
On AIX edit /etc/sudoers
file and add the above commands for the user account that is used for data collection.
<user_name> ALL=(root) NOPASSWD: /usr/sbin/netstat -Aan,/usr/sbin/lsof -RnP,/usr/sbin/lsdev -Cc disk,/usr/bin/lsmpio,/usr/bin/lsmpio -ar,/usr/bin/lsmpio -ql
1.2 Test SSH Connection with CLI Access
To verify the SSH configuration, use ssh command which helps to test the remote connection to target AIX server over SSH protocol and an ability to execute a command.
2. Adding AIX OS as Datasource/Extension in RDA
AIX OS or any other datasource/extension's configuration is configured in RDA's user interface. Login into RDA's user interface using a browser.
Under Notebook, click on CFXDX Python 3 box
In the Notebook command box, type botadmin() and alt (or option) + Enter to open datasource administration menu.
Click on Add menu and under Type drop down, select ibm-aix
-
Secret Type: ibm-AIX: IBM AIX-OS & Application Inventory Collection
-
name: Datasource/Extension label which should be unique within the RDA
-
Hostname: IP Address / DNS name of AIX host
-
Username: AIX username
-
Password: AIX password
-
Private Key Passphrase: SSH private key passphrase (optional)
-
SSH Private Key: SSH private key (optional)
-
Port: 22
Click on Check Connectivity to verify the network access and credentials. Once it is validated, click on Add button to add the ibm-aix as a datasource.
2.1 Steps to Add IBM AIX Credentials in RDAF Platform
Please use the below mentioned Navigation Path, after logging into the CFX Portal
- Navigation Path : Home Menu -> Configuration -> RDA Integrations -> Credentials -> Add -> Click on the Dropdown to select the Credential ibm-AIX -> enter the data and Check Connectivity and Save.
Secret Type : ibm-AIX: IBM AIX-OS & Application Inventory Collection
3. AIX Bots
Below are the available bots for AIX OS integration.
3.1 @ibm-aix:system-info
This bot collects AIX system and hardware information such as Hostname,OS Version, Hardware Model,Kernal Version, hostname, CPU, Memory & Network information and file systems
When the user runs the system-info
bot, the below commands will collect the system inventory data
Command | Attribute | Description |
---|---|---|
uname -p |
Processor Type | Architecture of the processor (e.g., powerpc). |
oslevel -s |
OS Version & Service Pack | Complete OS level including TL, SP, and build date. |
/usr/sbin/prtconf |
System Configuration and Hardware Info | Summary of hardware and system configuration, including processors, memory, and firmware. |
/usr/sbin/lsattr -l sys0 -a os_uuid -E |
OS UUID | A unique identifier for the AIX operating system instance. |
3.2 @ibm-aix:network-config
This bot collects AIX network configuration information like inet ,IPv4 address,mtu,media,interface name, interface state,flag etc.
When the user runs the network-config
bot, the below command will collect the network config data
Attribute | Description |
---|---|
Interface Name | Name of the network interface (e.g., en0, et0, lo0). |
IP Address | IPv4 address assigned to the interface. |
IPv6 Address | IPv6 address assigned to the interface (if applicable). |
Subnet Mask | Subnet mask for the IPv4 address, indicating the network portion of the IP. |
MAC Address | Media Access Control (MAC) address of the interface. |
Interface Flags | Status of the interface, such as UP, RUNNING, BROADCAST, MULTICAST and LOOPBACK. |
3.3 @ibm-aix:netstat
This bot collects network statistics information like default gateway address,protocol,local IP address,port,PID,foreign address
When the user runs the netstat
bot, the below command will collect the netstat data
Column A | Column B |
---|---|
Address Family | The protocol family of the socket (e.g., AF_INET for IPv4, AF_INET6 for IPv6, AF_UNIX for local sockets). |
Protocol Type | Type of protocol in use (e.g., TCP, UDP or RAW). |
State | The current state of the socket (e.g., LISTEN, ESTABLISHED, CLOSE_WAIT, etc., for TCP). |
Local Address | The IP address and port number of the local endpoint. |
Remote Address | The IP address and port number of the remote endpoint (or * if not connected). |
Socket Identifier (SOCKET) | A unique identifier for the socket. |
Queue Lengths | Information about send and receive queues for the socket. |
Interface Details | Network interface associated with the socket, if applicable. |
3.4 @ibm-aix:software-packages
This bot collects data like software package name, category, architecture, version, description
When the user runs the software-packages
bot, the below command will collect the software packages data
Attribute | Description |
---|---|
Fileset Name | The name of the installed fileset (software package). |
Level | The version and release level of the fileset. |
State | The installation state of the fileset (e.g., COMMITTED, APPLIED). |
Type | Indicates whether the fileset is a BASE or UPDATE. |
Description | A brief description of the fileset or software package. |
3.5 @ibm-aix:services
This bot collects AIX OS all subsystems controlled by the System Resource Controller (SRC), along with their current statuses. This command provides a snapshot of the state of all managed services (subsystems) on the system.
When the user runs the services
bot, the below command will collect the services data
Attribute | Description |
---|---|
Subsystem Name | The name of the subsystem or service being managed by SRC. |
Group | The SRC group to which the subsystem belongs. |
PID | The Process ID (PID) of the subsystem (if active). |
Status | The current status of the subsystem, such as active, inoperative, or unknown. |
3.6 @ibm-aix:processes
This bot collects information like Process ID, process user , process status , TTY , START ,TIME etc..
When the user runs the processes
bot, the below command will collect the processes data
Attribute | Description |
---|---|
UID | The user ID of the process owner (e.g., root, daemon, or a specific user). |
PID | The process ID (unique identifier for the process). |
PPID | The parent process ID (the process that spawned this process). |
C | The CPU usage (percentage) of the process. |
STIME | The start time or date of the process (e.g., Nov 27 or 14:32). |
TTY | The terminal associated with the process. ? indicates no terminal (e.g., system daemons). |
TIME | The cumulative CPU time the process has consumed. |
CMD | The full command-line used to start the process, including its arguments (not truncated with ww) |
3.7 @ibm-aix:disks
This bot collects AIX disk information of filesystem like name, total space , used space and available space, capacity(percentage of file system currently being used), mounted directory.
When the user runs the disks
bot, the below command will collect the disks data
Attribute | Description |
---|---|
Filesystem | The device or resource associated with the file system (e.g., /, /home, /tmp) |
Size | The total size of the file system in human-readable units (e.g., GB, MB). |
Used | The amount of space currently used on the file system. |
Avail | The amount of free space available for use. |
Capacity | The percentage of the file system's total size that is currently in use. |
Mounted On | The mount point where the file system is attached in the directory structure. |
3.8 @ibm-aix:lsmpio
This bot collects information about Multi-Path I/O (MPIO) devices on the system. MPIO is a method of managing multiple physical paths between a system and its storage devices to improve redundancy and performance. When you run the lsmpio command, it collects and displays various attributes related to the MPIO configuration and status of the system's devices.
When the user runs the lsmpio
bot, the below command will collect the Multi-Path I/O (MPIO) devices data
Attribute | Description |
---|---|
Device Name | The name of the MPIO device, typically in the form of mpathX (e.g., mpath0, mpath1). |
Path | Lists the individual physical paths that are part of the MPIO configuration for the device (e.g., hdisk1, hdisk2). |
Status | The status of the MPIO device (e.g., active, failed, inactive). |
Policy | The policy used by the MPIO device, such as round-robin, failover, or loadbalance. |
Preferred Path | The preferred or primary path for accessing the device in the MPIO configuration. |
Failover Status | The failover status, indicating whether a path has failed and failover to another path has occurred. |
IO Errors | The number of input/output errors encountered for the MPIO device. |
Load Balance Mode | Indicates whether load balancing is being used and its mode (e.g., round-robin or active-passive). |
3.9 @ibm-aix:lsmpio-q
This bot gets detailed information about Multi-Path I/O (MPIO) devices, including information about the paths and their configuration in a more verbose format.
The -ql option shows detailed per-path and per-device information.
When the user runs the lsmpio-q
bot, the below command will collect the Multi-Path I/O (MPIO) devices data
Note
The -ql
parameter is used to display the attributes of all MPIO devices in a concise, one-line format.
3.10 @ibm-aix:lsmpio-ar
This bot gets detailed information about Multi-Path I/O (MPIO) devices, specifically focusing on path attributes and their recovery status. The -ar option combines the listing of the attributes related to the MPIO configuration with the recovery status of each path
By using the below mentioned command administrators can gather detailed insights into the recovery status and health of the paths within their MPIO configuration, aiding in the maintenance of system performance and reliability.
3.11 @ibm-aix:lsof
This bot collects a list of open files information. It collects info like process ID,process owner,file descriptor mode,filetype,device,Inode number,file size,filename,file node.
When the user runs the lsof
bot, the below command will collect the open files information
Attribute | Description |
---|---|
COMMAND | The name of the command or executable associated with the process holding the open file or connection. |
PID | The Process ID (PID) of the process that has the file open. |
USER | The username of the user who owns the process holding the open file. |
FD | The file descriptor used by the process to refer to the open file. This could be a number (e.g., 4), or special notations (e.g., cwd, txt, or mem). |
TYPE | The type of file (e.g., REG for regular files, DIR for directories, CHR for character devices, etc.). |
DEVICE | The device on which the file is located, presented in major/minor device number format. |
SIZE/OFF | The size of the file or the offset in the file (in bytes), depending on the type of file. |