Symptom
DCNM fabric out-of-sync due to configuration mismatch with snmp trap default port configured with snmp_server_host_trap template
Conditions
DCNM version 11.3.1
snmp trap configured with default port
Workaround
Workaround1: Disable "Enable DCNM as Trap Host" in the fabric settings advance tab which will remove the dcnm default intent and then use switch_freeform to have custom command of snmp-server host.
If community string or UDP port is different, make sure to update the server properties also.
Workaround2: Create custom template, remove udp-port variable and adjust CLI configuration
Further Problem Description
Example of custom template:
##template variables
# Copyright (c) 2018-2019 by Cisco Systems, Inc.
# All rights reserved.
@(IsMandatory=true, DisplayName="IP Address", Description="IPv4/v6 Address Of SNMP Notification Host")
ipAddressWithoutPrefix IP;
@(IsMandatory=true, DisplayName="SNMP Version", Description="SNMP Version To Use For Notification Messages")
enum VER {
validValues=1,2c,3;
defaultValue=2c;
};
@(IsMandatory=true, DisplayName="Community String or SNMPv3 user name", Description="Max Size:32")
string CS {
defaultValue=public;
minLength = 1;
maxLength = 32;
};
##
##template content
snmp-server host $$IP$$ traps version $$VER$$ $$CS$$
##
PSIRT Evaluation:
The Cisco PSIRT has evaluated this issue and determined it does not meet the criteria for PSIRT ownership or involvement. This issue will be addressed via normal resolution channels.
If you believe that there is new information that would cause a change in the severity of this issue, please contact psirt@cisco.com for another evaluation.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
