About SNMP settings

You can define IBM® Sterling Control Center Monitor rules and actions to generate SNMP traps and send them to an Enterprise System Management tool when certain events occur. These traps contain information from the event that can be used for diagnostic tests. Before you can use an SNMP trap rule, specify the host computers where the traps are sent.

IBM Sterling Control Center Monitor supports any Enterprise System Management tool that accepts SNMP version 2 (SNMPv2) traps.

The configuration file named SnmpAdaptorWrapper.xml controls the content of the SNMP traps that IBM Sterling Control Center Monitor generates and the length of the traps. To edit the SnmpAdaptorWrapper.xml file, in the IBM Sterling Control Center Monitor web console, go to your user ID, and then click System configuration > Properties > SnmpAdaptorWrapper.xml.

- <service>

     <serviceClass>com.sterlingcommerce.scc.agent.services.jmx.SnmpAdaptorWrapper</serviceClass> 
     <serviceId>SNMPAdaptorWrapper</serviceId> 
  <serviceType>SNMPAdaptor</serviceType> 
  <snmpPort>161</snmpPort> 
  <trapPort>162</trapPort> 
  <bufferSize>1024</bufferSize> 
  <omitIfEmpty>false</omitIfEmpty> 
- <trapElements>
  <eventId>255</eventId> 
  <nodeId>255</nodeId> 
  <nodeType>255</nodeType> 
  <messageId>255</messageId> 
  <returnCode>255</returnCode> 
  <processId>255</processId> 
  <processName>255</processName> 
  <stepName>255</stepName> 
  <submitterId>255</submitterId> 
  <remoteNode>255</remoteNode> 
  <shortText>255</shortText> 
  <fileSize>255</fileSize> 
  <percentComplete>255</percentComplete> 
  <dateTime>255</dateTime> 
  <ruleId>255</ruleId> 
  <actionId>255</actionId> 
  <origNode>255</origNode> 
  <sourceFile>0</sourceFile> 
  <destFile>0</destFile> 
  <fromNode>0</fromNode> 
  <userData1>255</userData1> 
  <userData2>0</userData2> 
  <userData3>0</userData3> 
  <userData4>0</userData4> 
  <slcId>0</slcId> 
  <bytesSent>0</bytesSent> 
  <bytesRead>0</bytesRead> 
  <processQueue>0</processQueue> 
  <isAlert>0</isAlert> 
  <ccName>0</ccName> 
  <ruleInstanceId>0</ruleInstanceId> 
  <slcInstanceId>0</slcInstanceId> 
  <slcSource1>0</slcSource1> 
  <slcSource2>0</slcSource2> 
  <slcSourceEventId>0</slcSourceEventId> 
  <SESSION.ADAPTER_TYPE>0</SESSION.ADAPTER_TYPE> 
  <SESSION.ADAPTER_NAME>0</SESSION.ADAPTER_NAME> 
  <daemonName>0</daemonName> 
  <daemonState>0</daemonState> 
  <userId>0</userId> 
  <certIssuer>0</certIssuer> 
  <certSubject>0</certSubject> 
  <cipherSuite>0</cipherSuite> 
  <secureEnabled>0</secureEnabled> 
  <secureProtocol>0</secureProtocol> 
  <eventType>255</eventType> 
  <nodeName>0</nodeName> 
  <localNode>0</localNode> 
  <bytesXferred>0</bytesXferred> 
  <recordId>0</recordId> 
  <alert>255</alert> 
  <sourceEventTime>0</sourceEventTime> 
  <objectType>0</objectType> 
  <objectId>0</objectId> 
  <objectVersion>0</objectVersion> 
  <activityType>0</activityType> 
  <suspended>0</suspended> 
  <triggerMilestoneId>0</triggerMilestoneId> 
  <action>0</action> 
  <daemonHost>0</daemonHost> 
  <daemonOriginator>0</daemonOriginator> 
  <daemonPid>0</daemonPid> 
  <daemonResource>0</daemonResource> 
  <daemonSid>0</daemonSid> 
  <daemonType>0</daemonType> 
  <SESSION.ADAPTER_NAME>0</SESSION.ADAPTER_NAME> 
  <SESSION.ADAPTER_TYPE>0</SESSION.ADAPTER_TYPE> 
  <SESSION.PROTOCOL>0</SESSION.PROTOCOL> 
  <XFER.MESSAGE_NAME>0</XFER.MESSAGE_NAME> 
  <XFER.DOC_NAME>0</XFER.DOC_NAME> 
  <XFER.MBOX_PATH>0</XFER.MBOX_PATH> 
  <direction>0</direction> 
  <serverMetaData1>0</serverMetaData1> 
  <serverMetaData2>0</serverMetaData2> 
  <serverMetaData3>0</serverMetaData3> 
  <serverMetaData4>0</serverMetaData4> 
  <serverMetaData5>0</serverMetaData5> 
  <serverMetaData6>0</serverMetaData6> 
  <serverMetaData7>0</serverMetaData7> 
  <serverMetaData8>0</serverMetaData8> 
  <serverMetaData9>0</serverMetaData9> 
  <serverMetaData10>0</serverMetaData10> 
  <fgActivityType>0</fgActivityType> 
  <FG.FILE_NAME>0</FG.FILE_NAME> 
  <FG.STATE>0</FG.STATE> 
  <FG.PROD_ORG_KEY>0</FG.PROD_ORG_KEY> 
  <FG.CONS_ORG_KEY>0</FG.CONS_ORG_KEY> 
  <FG.EVENT_CODE>0</FG.EVENT_CODE> 
  <FG.DATA_FLOW_ID>0</FG.DATA_FLOW_ID> 
  <SI.MESSAGE_ID>0</SI.MESSAGE_ID> 
  <QF.file>0</QF.file> 
  <QF.recipient.userEmail>0</QF.recipient.userEmail> 
  <QF.recipient.userId>0</QF.recipient.userId> 
  <QF.userEmail>0</QF.userEmail> 
  <QF.userId>0</QF.userId> 
  <QF.operation>0</QF.operation> 
  <QF.eventType>0</QF.eventType> 
  <QF.userRegistered>0</QF.userRegistered> 
    </trapElements>
- <aclEntry>
  <manager>localhost</manager> 
  <community>public</community> 
  <access>read-write</access> 
    </aclEntry>
- <trapEntry>
  <host>localhost</host> 
  <community>public</community> 
  <trapPort>162</trapPort> 
    </trapEntry>
    </service>

How to Turn off SNMP from Listening on Port 161 in IBM Sterling Control Center

By default SNMP has the listen port 161 turned on in IBM Sterling Control Center Monitor.

Follow the below steps to Turn off SNMP from Listening on port 161:

Go to the IBM Sterling Control Center Web Console > System Settings > Properties > snmpAdaptorWrapper.xml.
Alter the value <snmpPort>161</snmpPort> to <snmpPort>0</snmpPort>, save and then recycle Control Center.