NSMEMSTR not routing IKED messages from Syslogd to Operlog to Automate

book

Article ID: 109897

calendar_today

Updated On:

Products

CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu

Issue/Introduction

Today, on one of our development systems, IKED messages were NOT routing the tmessages to OPERLOG inorder to capture the message and Automate it. We could see only TRMD messages passing through the OPERLOG and rest all were not. Because of this, we are missing alert related to certificate expiration and Automation could trap it. Below is the syslog.conf we have setup. #All non Packet Filtering messages *.*;*.TRMD*.*.none;*.IKED.*.none;*.SSHD.*.none;*.NSSD.*.none;*.TN3270*.*.none;*.ftp*.*.none;*.OMPROUTE.*.none /var/log/syslogd/syslo #Console Messages *.crit;local4.none /dev/console #Info sent to soft link for PIPE for NETCOOL *.debug /opt/lpp/cai/nsmem/opr/config/ADEV/pipe/oprpipe0059 Please let us know what all the documentation required for investigation. 

Cause

 OPS 12.3 doesn't have option to route SYSLOGD messages to OPSLOG? 
Could you please let us know if there is any way or setup that we can configure to route syslogd messages to opslog in 12.3 version? 
The Documentation is correct on your question: This feature is available only with CA OPS/MVS 13.5. 
 

Environment

z/OS

Resolution

Yes, OPS/MVS 12.3 has a method to route syslogd messages to OPSLOG as USS events to be eligible for automation. 
So I guess this means you have never implemented this feature? 
Please refer to the OPS/MVS Install Guide: Install the Event Management of CCS for z/OS - please read the entire chapter. Here is the DocOPS link: 
https://docops.ca.com/ca-opsmvs/12-3/en/installing/configuring-and-installing-optional-components/configuration-tasks-for-optional-base-components/install-the-unix-system-services