Overview
What is its Purpose?
What is its Purpose?
Trap/Inform Message Matching
Used to match SNMP trap/inform messages from network and infrastructure devices with Apinizer Integration Flow components
Alarm Management
Facilitates alarm management for operations teams by routing multiple message types over the same connection
Multi-Version Support
Ensures consistent communication with devices having different security levels through SNMP v1, v2c, and v3 support
Environment Migration
Accelerates migration of connection configurations to environments through project-based authorization and export/import support
How it Works
How it Works
Connection Initialization
When an SNMP connection is requested from Integration Flow or Connector, the system reads the configured connection parameters
Connection Pool Management
A logical connection pool is maintained for lightweight UDP sessions; if an active socket exists, it is reused, otherwise a new SNMP session is opened
Authentication
Community string for SNMP v1/v2c, USM-based Authentication mechanism for SNMP v3 is activated
Data Communication
Trap, inform, or get requests are sent over UDP ports 161/162 according to the defined message type, and responses are read
Connection Management
After the operation is completed, the connection returns to the pool; the socket is kept open for continuous trap listening
Error Management
In case of connection error, timeout, or authentication error, retry is attempted up to the retryCount value, then the error is logged and transmitted to the user
Use Cases
Use Cases
Event Management System
Forwarding traps from network devices to the event management system
Data Center Monitoring
Monitoring energy and climate control equipment in the data center with SNMP OID values
SIEM Integration
Routing SNMP inform messages from security devices to SIEM integration
REST API Bridges
Communicating with SNMP-based REST API bridges provided by hardware manufacturers
Technical Features and Capabilities
Basic Features
Basic Features
Multi-SNMP Version Support
Can connect to both legacy and secure USM-based devices with V1, V2c, and V3 selections.
Message Type Flexibility
Different alarm scenarios are managed from a single connection by selecting Trap, Inform, or Get requests.
Dynamic PDU OID Management
Device-specific fields are easily mapped through PDU OID for Message/Time fields and PDU Variable Map.
Environment-Based Configuration
Ability to define separate connection parameters for each environment (Development, Test, Production).
Enable/Disable Control
Activating or deactivating the connection (enable/disable toggle). In passive state, the connection cannot be used but its configuration is preserved.
Advanced Features
Advanced Features
PDU Variable Map Editor
OIDs in the SNMP payload are renamed according to business rules using a key/value table.
USM Security Level Automation
Required authentication/privilege fields automatically become mandatory based on Security Level selection.
Global Migration and Project Sharing
Connection can be migrated to the global area through Project Operations services and reused across multiple projects.
Connection Test Feature
Ability to validate connection parameters before saving through the “Test Connection” button.
Export/Import Feature
Exporting connection configuration as a ZIP file. Importing to different environments (Development, Test, Production). Version control and backup capability.
Connection Monitoring
Monitoring connection health, pool status, and performance metrics.
Connection Parameters
Required Parameters
Required Parameters
Name
Description: Connection name (must be unique)
Example Value:
Notes: Cannot start with space, special characters should not be used
Example Value:
Production_SNMPNotes: Cannot start with space, special characters should not be used
Version
Description: SNMP version to use (V1, V2c, V3)
Example Value:
Notes: It is recommended to select the highest version supported by the device
Example Value:
V3Notes: It is recommended to select the highest version supported by the device
Connection String
Description: UDP address and port of the SNMP target
Example Value:
Notes: Port 162 is used for trap, 161 for get/inform
Example Value:
udp:10.10.10.5/162Notes: Port 162 is used for trap, 161 for get/inform
Security/Community Name
Description: Community string or security name according to version
Example Value:
Notes: Used as security name in V3, community is required in v1/v2c
Example Value:
publicNotes: Used as security name in V3, community is required in v1/v2c
Retry Count
Description: Number of retry attempts for failed messages
Example Value:
Notes: A value of 0 means no retry will be performed
Example Value:
2Notes: A value of 0 means no retry will be performed
Timeout (seconds)
Description: Maximum wait time for SNMP request response
Example Value:
Notes: Very low durations can cause packet loss
Example Value:
30Notes: Very low durations can cause packet loss
Message Type
Description: Trap, Inform, or Get selections
Example Value:
Notes: The selected type triggers Integration Flow steps
Example Value:
TRAPNotes: The selected type triggers Integration Flow steps
PDU OID for Message
Description: OID from which the alarm message will be read
Example Value:
Notes: Should be updated according to device documentation
Example Value:
.1.3.6.1.2.1.1.6Notes: Should be updated according to device documentation
Security Level
Description: USM security level to be used only in V3
Example Value:
Notes: Additional authentication/priv fields become mandatory based on selection
Example Value:
AUTH_PRIVNotes: Additional authentication/priv fields become mandatory based on selection
Optional Parameters
Optional Parameters
Description
Description: Description about the purpose of the connection
Default Value: (Empty)
Recommended Value: DC Trap Forwarder
Default Value: (Empty)
Recommended Value: DC Trap Forwarder
PDU OID for Time
Description: OID to read for message timestamp
Default Value:
Recommended Value: Match with the device’s sysUpTime OID
Default Value:
.1.3.6.1.2.1.1.3.0Recommended Value: Match with the device’s sysUpTime OID
PDU Variable Map
Description: Additional OID field name mappings
Default Value: (Empty)
Recommended Value: Add key/value pairs for critical fields
Default Value: (Empty)
Recommended Value: Add key/value pairs for critical fields
Privacy Protocol List
Description: Privacy algorithms supported for V3
Default Value: (AES128)
Recommended Value: Select all algorithms compatible with the device
Default Value: (AES128)
Recommended Value: Select all algorithms compatible with the device
Enable User Authentication
Description: User-based USM authorization
Default Value: false
Recommended Value: Set to true for V3 and critical devices
Default Value: false
Recommended Value: Set to true for V3 and critical devices
Security Name
Description: Name to use when user auth is enabled
Default Value: (Empty)
Recommended Value: Using the same value as Community is consistent
Default Value: (Empty)
Recommended Value: Using the same value as Community is consistent
USM Authentication Protocol
Description: Authentication algorithm such as MD5/SHA
Default Value: (Empty)
Recommended Value: Select a strong algorithm (e.g., SHA256)
Default Value: (Empty)
Recommended Value: Select a strong algorithm (e.g., SHA256)
Auth Passphrase
Description: Password for authentication
Default Value: (Empty)
Recommended Value: Provide at least 8 characters + complexity
Default Value: (Empty)
Recommended Value: Provide at least 8 characters + complexity
USM Privacy Protocol
Description: Privacy algorithm such as DES/AES
Default Value: (Empty)
Recommended Value: Prefer AES256 if supported
Default Value: (Empty)
Recommended Value: Prefer AES256 if supported
Priv Passphrase
Description: Privacy password
Default Value: (Empty)
Recommended Value: Manage passwords through secret manager
Default Value: (Empty)
Recommended Value: Manage passwords through secret manager
Timeout and Connection Pool Parameters
Connection Timeout
Description: Maximum wait time for establishing connection
Default: 30000 ms
Min: 1000 ms | Max: 120000 ms
Default: 30000 ms
Min: 1000 ms | Max: 120000 ms
Request Timeout
Description: Maximum wait time for request response
Default: 30000 ms
Min: 1000 ms | Max: 120000 ms
Default: 30000 ms
Min: 1000 ms | Max: 120000 ms
Pool Size
Description: Maximum number of connections in connection pool
Default: 5
Min: 1 | Max: 50
Default: 5
Min: 1 | Max: 50
SNMP Retry Interval
Description: Wait time between retry attempts
Default: 5000 ms
Min: 1000 ms | Max: 30000 ms
Default: 5000 ms
Min: 1000 ms | Max: 30000 ms
Usage Scenarios
Network Alarm Consolidation
Situation: Hundreds of traps coming from core switches
Solution: Version V2c, message type TRAP, retry count 1, label interface OIDs in PDU map
Expected Result: All traps are collected over a single connection and routed to the relevant queue within Flow
Solution: Version V2c, message type TRAP, retry count 1, label interface OIDs in PDU map
Expected Result: All traps are collected over a single connection and routed to the relevant queue within Flow
Security Device Inform Flow
Situation: UTM device port 162 is closed
Solution: Message type INFORM, connection string udp:utm01/161, timeout 45, enable user authentication true
Expected Result: Connection automatically uses port 161, inform response is awaited
Solution: Message type INFORM, connection string udp:utm01/161, timeout 45, enable user authentication true
Expected Result: Connection automatically uses port 161, inform response is awaited
Energy Monitoring
Situation: UPS devices sending sysUpTime information
Solution: PDU OID for Time .1.3.6.1.2.1.1.3.0, define batteryStatus OID in variable map
Expected Result: Flow generates alerts based on batteryStatus value
Solution: PDU OID for Time .1.3.6.1.2.1.1.3.0, define batteryStatus OID in variable map
Expected Result: Flow generates alerts based on batteryStatus value
SNMPv3 Secure Trap
Situation: Unauthorized access attempts detected
Solution: Version V3, security level AUTH_PRIV, select SHA256 + AES128, read passphrase from secret manager
Expected Result: Traps arrive encrypted, authentication errors are logged
Solution: Version V3, security level AUTH_PRIV, select SHA256 + AES128, read passphrase from secret manager
Expected Result: Traps arrive encrypted, authentication errors are logged
Test Environment Simulation
Situation: Fake traps from lab devices will be used in testing
Solution: Connection string udp:lab-simulator/162, parameters are set while enable is false, then enabled
Expected Result: Trap flow is validated in test scenarios without affecting the real production configuration
Solution: Connection string udp:lab-simulator/162, parameters are set while enable is false, then enabled
Expected Result: Trap flow is validated in test scenarios without affecting the real production configuration
Connection Configuration
Creating a New SNMP Connection
Configuration Steps
1
Navigating to Creation Page
- Go to Connection → SNMP section from the left menu.
- Click the [+ Create] button at the top right.
2
Entering Basic Information
Enable Status (Active Status):
- Set active/passive status with toggle. New connections are active by default.
- Example:
Production_SNMP - Enter a unique name, cannot start with space.
- System automatically checks. Green checkmark: available. Red cross: existing name.
- Example: “SNMP trap collector”
- Max. 1000 characters.
- Describe the purpose of the connection.
3
Environment Selection
- Select environment from dropdown menu: Development, Test, or Production.
- Different connection parameters can be defined for each environment.
4
SNMP Basic Parameters
- Fill in Version, Connection String, Message Type, Retry Count, and Timeout fields.
- Write the correct port according to device documentation, adjust retryCount value according to network quality, remember that timeout value is in seconds.
5
OID and Message Maps
- Determine PDU OID for Message/Time fields according to your device’s MIB files.
- If additional fields are needed, add OID and the field name to be read as key/value to the PDU Variable Map table.
6
Timeout and Connection Pool Settings
- Review connection/request timeout values in milliseconds in the advanced section.
- Determine concurrent trap processing capacity with Pool Size and enter a value appropriate for network delay for SNMP Retry Interval.
7
Security and Authentication Settings
- If you selected SNMPv3, determine Security Level.
- When Enable User Authentication is enabled, select USM Authentication/Privacy protocols, set passphrase fields to at least 8 characters, and use secret manager information.
8
Test Connection
- Click the [Test Connection] button.
- Test whether connection parameters are correct.
- Success: Green confirmation message
- Failed: Error details are shown
9
Saving
- Click the [Save and Deploy] button at the top right.
- Unique name
- Required fields filled
- Test connection successful (recommended)
- Connection is added to the list
- Becomes available in Integration Flow and Connector steps
- Becomes active according to environment
Connection created successfully! You can now use it in Integration Flow and Connector steps.
Deleting a Connection
Deletion Process
Select Delete from the ⋮ menu at the end of the row or click the [Delete] button on the connection detail page
Deletion Tips
Check Before Deleting: It may be used in Integration Flow or Connector steps. If necessary, assign an alternative connection. Take a backup with Export before deleting
Alternative: Deactivation
Use the Disable option instead of deleting. Connection becomes passive but is not deleted. Can be reactivated when needed
Exporting/Importing Connections
In this step, users can export existing connections for backup, migration to different environments, or sharing purposes, or import a previously exported connection again. This operation is used to maintain data integrity in version management, transitions between test and production environments, or inter-team sharing processes.
Export
Export
Method 1
Select ⋮ → Export from the action menu. ZIP file is automatically downloaded.
Method 2
Click the [Export] button on the connection detail page. ZIP file is downloaded.
File Format
Format:
Example:
Date-connection-SNMP-export.zipExample:
13 Nov 2025-connection-Production_SNMP-export.zipZIP Contents
- Connection JSON file
- Metadata information
- Dependency information (e.g., certificates, key store)
Use Cases
- Backup
- Migration between environments (Test → Prod)
- Versioning
- Team or project-based sharing
Import
Import
Import Steps
- Click the [Import SNMP] button on the main list.
- Select the downloaded ZIP file.
- System checks: Is format valid? Is there a name conflict? Are dependencies available?
- Then click the [Import] button.
Import Scenarios
Scenario 1: Name Conflict → Overwrite the old connection or create with a new name.Scenario 2: Missing Dependencies → Create missing certificates or key stores first or remove them during import.
Connection Usage Areas
Creating and Activating Connection
Steps:
- Create the connection
- Validate the connection with Test Connection
- Save and activate with Save and Deploy
- Ensure the connection is in Enabled status
Usage in Integration / Connector Steps
Connection is selected in steps that require communication with external systems such as message queue (queue), topic, email, FTP/SFTP, LDAP, or similar. Example: Steps like “Send Message”, “Consume Message”, “Upload File”, “Read Directory”. Connection selection is made from the Connection field in the configuration of these steps
Scheduled Job Usage
Access to external systems is provided by selecting the connection in scheduled tasks (e.g., sending messages at certain intervals, file processing, etc.). When the connection changes, the job execution behavior is updated accordingly
Test Usage
The correctness of the connection can be checked independently from Integration Flow with the Connection Test feature. This test is critical in the debugging process
Best Practices
Do's and Best Practices
Do's and Best Practices
Trap Addressing
Bad: Leaving all devices with a single community
Good: Defining separate community for each device class
Best: Assigning different security names to each device group using SNMPv3 USM users
Good: Defining separate community for each device class
Best: Assigning different security names to each device group using SNMPv3 USM users
OID Management
Bad: Leaving PDU Variable Map empty
Good: Adding only critical OIDs
Best: Mapping all OIDs to be used in business rules with meaningful names and versioning
Good: Adding only critical OIDs
Best: Mapping all OIDs to be used in business rules with meaningful names and versioning
Retry/Timeout Setting
Bad: Leaving default retryCount and timeout values in every environment
Good: Updating retryCount according to network quality
Best: Measuring latency in Prod environment and optimizing timeout/interval values with data
Good: Updating retryCount according to network quality
Best: Measuring latency in Prod environment and optimizing timeout/interval values with data
Flow Integration
Bad: Using the same connection in independent flows without version control
Good: Documenting the connection version used per flow
Best: Versioning the exported connection with Git repository or artifact management and matching with flow changes
Good: Documenting the connection version used per flow
Best: Versioning the exported connection with Git repository or artifact management and matching with flow changes
Environment Management
Bad: Using the same connection parameters in all environments
Good: Creating separate connection for each environment
Best: Managing all environments in a single connection using Environment option, only changing environment during inter-environment transitions
Good: Creating separate connection for each environment
Best: Managing all environments in a single connection using Environment option, only changing environment during inter-environment transitions
Connection Test
Bad: Saving and deploying connection without testing
Good: Validating with Test Connection before saving
Best: Testing after every parameter change, performing full integration test in test environment before moving to production
Good: Validating with Test Connection before saving
Best: Testing after every parameter change, performing full integration test in test environment before moving to production
Security Best Practices
Security Best Practices
Community String Management
Do not use default public/private strings in production environment. Determine unique string per device and store in secret manager
USM Password Policy
Passwords shorter than 8 characters carry brute-force risk. Make auth/priv passphrase fields complex and change them at regular intervals
SNMP Network Segmentation
Open traffic only to management VLANs, allow only necessary source IPs in firewall, drop the rest
Credential Management
Store sensitive information such as usernames and passwords using environment variables or secret manager. Do not hardcode credentials in code or configuration files. Update passwords periodically
SSL/TLS Usage
Always enable SSL/TLS in production environment. Use self-signed certificates only in development environment. Track certificate expiration dates and renew them on time
Access Control
Allow only authorized users to change connection configuration. Store connection change logs. Implement change approval process for critical connections
Don'ts
Don'ts
Static OID Maps
Why avoid: OID changes are not noticed when new devices are added
Alternative: Regularly review and version PDU Variable Map
Alternative: Regularly review and version PDU Variable Map
Unlimited Retransmission
Why avoid: Infinite retry unnecessarily loads devices and network
Alternative: Keep retryCount value low, manage errors with Flow logic
Alternative: Keep retryCount value low, manage errors with Flow logic
Not Opening Firewall Ports
Why avoid: Connection constantly times out when UDP 161/162 is closed
Alternative: Coordinate port opening with network teams and automate access tests
Alternative: Coordinate port opening with network teams and automate access tests
Using Production Connection in Test Environment
Why avoid: Test data can be written to production system, real users can be affected, security risk occurs
Alternative: Create separate connection for each environment, use environment parameter, separate connection names by adding prefix according to environment (Test_, Prod_)
Alternative: Create separate connection for each environment, use environment parameter, separate connection names by adding prefix according to environment (Test_, Prod_)
Very Low Timeout Values
Why avoid: Connection constantly times out in network delays, Integration steps fail
Alternative: Adjust timeout values according to real usage scenarios, measure network latency and determine timeouts accordingly
Alternative: Adjust timeout values according to real usage scenarios, measure network latency and determine timeouts accordingly
Not Using Connection Pool
Why avoid: New connection is opened for each request, performance decreases, resource consumption increases, target system load increases
Alternative: Enable connection pool, adjust pool size according to traffic volume, set up pool monitoring
Alternative: Enable connection pool, adjust pool size according to traffic volume, set up pool monitoring
Performance Tips
Performance Tips
Trap Prioritization
Recommendation: Define separate connection or higher pool size for critical devices
Impact: Prevents delay of vital alarms
Impact: Prevents delay of vital alarms
Retry Policy
Recommendation: Adjust retry and interval values according to latency measurements
Impact: Unnecessary packet transmission decreases, network efficiency increases
Impact: Unnecessary packet transmission decreases, network efficiency increases
OID Caching
Recommendation: Cache frequently used OID results within Flow
Impact: PDU processing time shortens, CPU consumption decreases
Impact: PDU processing time shortens, CPU consumption decreases
Connection Pool Optimization
Recommendation: Adjust pool size according to peak traffic (recommended: concurrent request count × 1.5), set idle connection timeouts, perform pool health check
Impact: Connection opening cost decreases by 80%, response times decrease, resource usage is optimized
Impact: Connection opening cost decreases by 80%, response times decrease, resource usage is optimized
Timeout Values Optimization
Recommendation: Measure real network latency, adjust timeout values accordingly, avoid very low or very high timeouts
Impact: Unnecessary waits are prevented, fast fail-over is provided, user experience improves
Impact: Unnecessary waits are prevented, fast fail-over is provided, user experience improves
Connection Monitoring
Recommendation: Monitor connection pool usage, track timeout rates, perform connection health check, set up alerting
Impact: Problems are detected proactively, performance bottlenecks are identified early, downtime decreases
Impact: Problems are detected proactively, performance bottlenecks are identified early, downtime decreases
Troubleshooting
Trap Not Reaching Target
Trap Not Reaching Target
1
Connection String Validation
Verify IP/port in connection string.
2
UDP Port Access
Test UDP 162 access with network team.
3
Device Test
Send manual trap from device and examine logs.
SNMPv3 Authentication Failed
SNMPv3 Authentication Failed
1
Security Level Matching
Match security level and protocols with device.
2
Password Update
Re-enter passwords in secret manager.
3
Time Synchronization
Align device and Apinizer clocks with NTP.
Connection Timeout
Connection Timeout
1
Network Check
Check network connectivity.
2
System Health
Check target system health.
3
Timeout Settings
Increase timeout values.
4
Log Review
Review connection logs.
Authentication Failed
Authentication Failed
1
Credentials
Verify credentials.
2
User Status
Check that user is active in target system.
3
Permission Check
Check that necessary permissions are granted.
4
Certificate Check
Check SSL/TLS certificates.
Pool Exhausted
Pool Exhausted
1
Pool Size
Increase pool size.
2
Connection Check
Check that connections are properly closed.
3
Idle Timeout
Set idle connection timeouts.
4
Metric Monitoring
Monitor connection usage metrics.
Connection Test Successful But Integration Flow Gives Error
Connection Test Successful But Integration Flow Gives Error
1
Enable Toggle
Check that connection’s enable toggle is active.
2
Connection Selection
Verify that correct connection is selected in Integration Flow.
3
Connection Deploy
Redeploy the connection.
4
Flow/Job Deploy
Redeploy Integration Flow or Job.
5
Log Check
Check Gateway logs.
Frequently Asked Questions (FAQ)
Which versions does SNMP Connection support?
Which versions does SNMP Connection support?
V1, V2c, and V3 are supported; USM security options open when V3 is selected.
Can I send both trap and inform with the same connection?
Can I send both trap and inform with the same connection?
No, message type takes a single value. You need to create two connections for two different types or duplicate with export/import.
What is PDU Variable Map used for?
What is PDU Variable Map used for?
Provides readable field names on the Integration Flow side by mapping OID field names and allows you to easily add new OIDs.
How should security level selection be in SNMPv3?
How should security level selection be in SNMPv3?
AUTH_PRIV is recommended if device supports it; in this case, you need to select authentication and privacy protocols and enter passwords.
What happens if trap port is closed?
What happens if trap port is closed?
Can I use the same connection in multiple Integration Flows?
Can I use the same connection in multiple Integration Flows?
Yes, the same connection can be used in multiple Integration Flow or Connector steps. This provides centralized management and guarantees configuration consistency. However, changes made to the connection will affect all usage locations, so care should be taken.
Is using connection pool mandatory?
Is using connection pool mandatory?
Using connection pool is not mandatory but strongly recommended in high-traffic systems. Reusing existing connections instead of opening new connection for each request significantly increases performance.
Should I create different connections for Test and Production?
Should I create different connections for Test and Production?
Yes, it is recommended to create separate connection for each environment. Alternatively, you can manage all environments within a single connection using the environment parameter. This approach provides easier management and less error risk.
Connection Test is successful but not working in Integration Flow, why?
Connection Test is successful but not working in Integration Flow, why?
- Connection enable toggle may be passive
- Different connection may be selected in Integration step
- Connection may not be deployed
- Integration Flow may not be redeployed yet