Hi,
Would like to understand what are the several ways SNMP shouts are sent.
In our environment we are forwarding SNMP shouts to ITO tool.
what are the ports used for forwarding these shouts.
Found that '/usr/lbin/cmsnmpd' is used on control M server & agent.
Just fyi - We are migrating ITO tool so need to understand how to forward SNMP shouts to ITO.
Thanks
Control M integration with ITO Tool
The SNMP destination is configured by 4 parameters set on the Enterprise Manager (the main thing is to switch the messaging on - SnmpSendActive & SendSnmp - and tell EM what the name of the ITO host is - SnmpHost). You can get all EM Alerts sent across - you'll need to configure ITO templates to handle the messages accordingly.
Use the Control-M Server utility ctm2snmp to test basic connectivity.
On the ITO side you'll have to tell it the SNMP number of Control-M (either .1031 or .954 depending on which version of Control-M you have).
Also make sure you have a snmp-trap entry in /etc/services ...
Use the Control-M Server utility ctm2snmp to test basic connectivity.
On the ITO side you'll have to tell it the SNMP number of Control-M (either .1031 or .954 depending on which version of Control-M you have).
Also make sure you have a snmp-trap entry in /etc/services ...
Usually a SNMP management application (e.g. ITO or Tivoli) must be customized so that it recognizes the Enterprise ID (1031) of CONTROL-M/EM alert. We went to 6.3.1 and it seems that Control-M used to use 954 as it's Enterprise number, but that should have changed to 1031 (but I have seen some sites where 954 still works ok).
Whoever runs your ITO side should be familiar with SNMP Enterprise Numbers. It is basically a way of identifying the originating tool.
Whoever runs your ITO side should be familiar with SNMP Enterprise Numbers. It is basically a way of identifying the originating tool.