Displaying information about a node
Use CLI to view information about nodes in Cloud Pak for Data System.
About this task
A node can be defined by its personality, state and status.
Personalities define the role of the node in the system and they are described in System nodes.
The node state determines its use in the system, not its health. Node state can be one of the
following:
- ENABLED - the node is used to run the applications
- DISABLED - the node is not used to run the applications
- ENABLING - node enablement is in progress
- DISABLING - node disablement is in progress
- UNMANAGED - the node is not managed by Platform Manager
You can also check the status of the node, which is its health, for example, OK, or WARNING.
Procedure
- To display detailed information about the node state, personality, and its role in the
system, use the ap node -d command:
[root@e1n1 ~]# ap node -d +------------------+---------+-------------+-----------+-----------+--------+---------------+ | Node | State | Personality | Monitored | Is Master | Is HUB | Is VDB Master | +------------------+---------+-------------+-----------+-----------+--------+---------------+ | enclosure1.node1 | ENABLED | CONTROL | YES | YES | YES | YES | | enclosure1.node2 | ENABLED | CONTROL | YES | NO | NO | NO | | enclosure1.node3 | ENABLED | CONTROL | YES | NO | NO | NO | | enclosure1.node4 | ENABLED | WORKER | YES | NO | NO | NO | | enclosure2.node1 | ENABLED | WORKER | YES | NO | NO | NO | | enclosure2.node2 | ENABLED | WORKER | YES | NO | NO | NO | | enclosure2.node3 | ENABLED | UNSET | YES | NO | NO | NO | | enclosure2.node4 | ENABLED | UNSET | YES | NO | NO | NO | +------------------+---------+-------------+-----------+-----------+--------+---------------+ IPS nodes +------------------+-----------+---------------+-----------+------------+----------+ | Node | State | Personality | Monitored | IPS Status | IPS Role | +------------------+-----------+---------------+-----------+------------+----------+ | enclosure3.node1 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | | enclosure3.node2 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | | enclosure3.node3 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | | enclosure3.node4 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | | enclosure4.node1 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | | enclosure4.node2 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | | enclosure4.node3 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | | enclosure4.node4 | UNMANAGED | VDB[IPS1NODE] | NO | OK | Active | +------------------+-----------+---------------+-----------+------------+----------+ Generated: 2022-03-14 12:40:00Nodes other than NPS are listed in the first table.Is Master- You can check which node is the Control Plane master node. The master control node is elected to run additional services and service additional network endpoints. The customer-designated floating IP follows the master node to provide a uniform method of connecting to the system.
Is HUB- You can check which node is a Platform Manager Hub. The hub node is running the Policy Engine. It also contains some additional log files that can be used for troubleshooting. The Platform Manager Hub node is one of the Control Plane nodes. The Hub node does not necessarily have to be the master node.
Is VDB Master- You can check which node is the NPS master node which is running the NPS host container.
If NPS is installed on a system without connector nodes, one of the control nodes is the NPS host (
VDB master). If NPS is installed on a system with connector nodes, the NPS host runs on a connector node.
NPS compute nodes are listed in a separate table (
IPS nodes). Their state is always UNMANAGED, and their personality is VDB. They are not monitored by Platform Manager. - To display node status, use the ap hw -t node command:
[root@e1n1 ~]# ap hw -t node +--------------+------------------+-----------+----------+------------+--------------+ | Name | Location | Status | SN | Model | FW | +--------------+------------------+-----------+----------+------------+--------------+ | Compute Node | enclosure1.node1 | OK | J100E7AF | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure1.node2 | OK | J100E7BP | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure1.node3 | OK | J100E7CG | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure1.node4 | OK | J100E79A | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure2.node1 | OK | J100E7BE | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure2.node2 | OK | J100E7CN | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure2.node3 | OK | J100E79Z | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure2.node4 | ATTENTION | J100E7D2 | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure3.node1 | OK | J100E099 | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure3.node2 | OK | J100BN3H | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure3.node3 | OK | J100BN3R | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure3.node4 | OK | J100BN41 | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure4.node1 | OK | J100DT8X | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure4.node2 | OK | J100DT7Z | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure4.node3 | OK | J100CW1C | 7X21CTO1WW | TEE172G-3.01 | | Compute Node | enclosure4.node4 | OK | J100E09C | 7X21CTO1WW | TEE172G-3.01 | +--------------+------------------+-----------+----------+------------+--------------+ Generated: 2022-03-14 15:05:25
how do we mark connector nodes in this command?