A Patch Node represents a software patch in your network environment and is linked to any Host Node which contains it.
You will only find Patch Nodes linked to operating systems which recognize patches. Currently only three operating systems that BMC Atrium Discovery models have the concept of a patch; Solaris, HPUX and Windows.
Patch Node lifecycle
The following section describes the scenarios in which a Patch is created, updated or destroyed. Patch Nodes are identical in behavior to Package Nodes, see Package node.
Creation
Patch Nodes are created when they are first detected on a host. The key of a Patch Node consists of two critical properties; name and operating system information. Therefore, Patch Nodes are shared by all Host Nodes with the same patch installed.
Update
A Patch Node is never updated because its key consists of two critical properties and a change to either of them will result in a new Patch Node being created.
Removal
Patch Nodes are never removed.
Patch Node Attributes
The attributes and relationships of a Patch Node are described in the tables below.
UI Name |
Description |
|---|---|
Name |
Patch name. |
Operating System |
Operating System this Patch is for. |
Not displayed in UI |
Unique key. |
Patch Node Relationships
The relationships of a Patch Node are described in the table below.
UI name |
Relationship |
Description |
|---|---|---|
Hosts |
|
Hosts with this patch. |
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks