Hi Team,
I was able to get all the client patch status and report from SMT server using smt-client -v command but how I can get the same from RMT server? What is the command and procedure to achieve it?
Hi Team,
I was able to get all the client patch status and report from SMT server using smt-client -v command but how I can get the same from RMT server? What is the command and procedure to achieve it?
@rajadurainainan Hi and welcome to the Forum
I’m not running SMT, however on a SLE system you can use the zypper
command to see package information, for example zypper se -s -t patch
where -t
specifies type, in this case patches and zypper se -si -t patch
to see installed patches… Maybe smt-reports will provide more information on what your after?
@malcolmlewis1 Thanks for your reply. I would required below command output from RMT server.
smt-client -v
.----------------------------------------------------------------------------------------------------------------------------------------------------------------------.
| GUID | Hostname | Patch Status | Security | Package Manager | Recommended | Optional | Patch Status Date | Last Contact |
| | | | Patches | Patches | Patches | Patches | | |
±-------------------------------------±-------------±-------------±---------±----------------±------------±---------±--------------------±--------------------+
@rajadurainainan then zypper lp
should give what you need.
smt-client -v will get all the clients connected to the SMT server that will help us to get all the server patch status. Likewise, I could not find an option to get the same from RMT server.
PFB output
smt-client -v
.----------------------------------------------------------------------------------------------------------------------------------------------------------------------.
| GUID | Hostname | Patch Status | Security | Package Manager | Recommended | Optional | Patch Status Date | Last Contact |
| | | | Patches | Patches | Patches | Patches | | |
±-------------------------------------±-------------±-------------±---------±----------------±------------±---------±--------------------±--------------------+
| SCC_257bd647177846da8984986eb7299c56 | node1 | Critical | 61 | 0 | 11 | 0 | 2023-11-15 09:19:17 | 2023-11-16 06:19:01 |
| SCC_6dee1f28679e4663a95a82cf35972e9a | node-01 | Critical | 61 | 0 | 11 | 0 | 2023-11-15 09:43:17 | 2023-11-16 06:43:01 |
| SCC_4be115edd3f349bfbe0dd4e46ec802c6 |node-02 | Critical | 62 | 0 | 11 | 0 | 2023-11-15 09:36:05 | 2023-11-16 06:36:01 |
| SCC_a6323d15f7e34c9e8cd01d96a2944b74 | node03 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:19:18 | 2023-11-16 06:19:02 |
| SCC_edef79b20e25477497e46f135d356748 |node4 | Critical | 57 | 0 | 11 | 0 | 2023-11-15 12:13:10 | 2023-11-16 06:13:02 |
| SCC_0cb7f185640d4640ab63a38c3bf8d9c8 | node5 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 12:00:10 | 2023-11-16 06:00:01 |
| SCC_b925997a968b4dcfb1e8380fcb4ca4df | node6 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:58:10 | 2023-11-16 06:58:01 |
| SCC_a820de4e1c0140789dbd579be0c67f15 | node7 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:21:10 | 2023-11-16 06:21:01 |
| SCC_523f60fcb3bf4c0aa0754e9cd0cacc17 | node8 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:37:10 | 2023-11-16 06:37:01 |
| SCC_56087892e409492b95316c55536ff2f0 |node9 | Critical | 61 | 0 | 11 | 0 | 2023-11-15 09:34:11 | 2023-11-16 06:34:01 |
| SCC_f1d6f1b23ce64e16bf2f4f0096f69f17 |node10 | Critical | 55 | 0 | 8 | 0 | 2023-11-15 09:49:15 | 2023-11-16 06:49:02 |
smt-client -v will get all the clients connected to the SMT server that will help us to get all the server patch status. Likewise, I could not find an option to get the same from RMT server.
PFB output
smt-client -v
.----------------------------------------------------------------------------------------------------------------------------------------------------------------------.
| GUID | Hostname | Patch Status | Security | Package Manager | Recommended | Optional | Patch Status Date | Last Contact |
| | | | Patches | Patches | Patches | Patches | | |
±-------------------------------------±-------------±-------------±---------±----------------±------------±---------±--------------------±--------------------+
| SCC_257bd647177846da8984986eb7299c56 | node1 | Critical | 61 | 0 | 11 | 0 | 2023-11-15 09:19:17 | 2023-11-16 06:19:01 |
| SCC_6dee1f28679e4663a95a82cf35972e9a | node-01 | Critical | 61 | 0 | 11 | 0 | 2023-11-15 09:43:17 | 2023-11-16 06:43:01 |
| SCC_4be115edd3f349bfbe0dd4e46ec802c6 |node-02 | Critical | 62 | 0 | 11 | 0 | 2023-11-15 09:36:05 | 2023-11-16 06:36:01 |
| SCC_a6323d15f7e34c9e8cd01d96a2944b74 | node03 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:19:18 | 2023-11-16 06:19:02 |
| SCC_edef79b20e25477497e46f135d356748 |node4 | Critical | 57 | 0 | 11 | 0 | 2023-11-15 12:13:10 | 2023-11-16 06:13:02 |
| SCC_0cb7f185640d4640ab63a38c3bf8d9c8 | node5 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 12:00:10 | 2023-11-16 06:00:01 |
| SCC_b925997a968b4dcfb1e8380fcb4ca4df | node6 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:58:10 | 2023-11-16 06:58:01 |
| SCC_a820de4e1c0140789dbd579be0c67f15 | node7 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:21:10 | 2023-11-16 06:21:01 |
| SCC_523f60fcb3bf4c0aa0754e9cd0cacc17 | node8 | Critical | 55 | 0 | 9 | 0 | 2023-11-15 09:37:10 | 2023-11-16 06:37:01 |
| SCC_56087892e409492b95316c55536ff2f0 |node9 | Critical | 61 | 0 | 11 | 0 | 2023-11-15 09:34:11 | 2023-11-16 06:34:01 |
| SCC_f1d6f1b23ce64e16bf2f4f0096f69f17 |node10 | Critical | 55 | 0 | 8 | 0 | 2023-11-15 09:49:15 | 2023-11-16 06:49:02 |
@rajadurainainan Did you try zypper lp
command?
Repository | Name | Category | Severity | Interactive | Status | Since | Summary
------------------------------------+---------------------------------------------+----------+-----------+-------------+--------+-------+-------------------------------------
Whilst not as informative, I think “rmt-cli systems list” is the closest you’ll get from an RMT-related command. RMT just isn’t as full featured as SMT.
The command-line syntax for retrieving patch status and client reports can vary. Check the tool’s documentation for the specific command or set of commands used to obtain this information from the RMT server.