Guest

Preview Tool

Cisco Bug: CSCvt44565 - After Changing trap.port=162 in server.properties file, DCNM still sends command with port 2162

Last Modified

Apr 30, 2020

Products (1)

  • Cisco Data Center Network Manager

Known Affected Releases

10.3(1)R(1.131) 10.3(1)S(1.9) 10.3(1)ST(0.139)

Description (partial)

Symptom:
As per DCNM design it listens for trap on port 2162,however it is configurable to custom port. Now, once we change trap port to 162 or any customer port ideally DCNM should send the command with port 162 or custom port which DCNM is not doing.

Conditions:
As per DCNM design it listens for trap on port 2162,however it is configurable to custom port. Now, once we change trap port to 162 or any customer port ideally DCNM should send the command with port 162 or custom port which DCNM is not doing.
tested in lab for snmp-server with both(162 and 2162)  ports  and switch is sending traps on both ports. Below is the tcpdump output for communication between switch(10.105.229.245) and DCNM(10.105.229.60):
 
[root@dcnm-ril ~]# tcpdump -nni eth0 host 10.105.229.245
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
19:05:32.796088 IP 10.105.229.245.59936 > 10.105.229.60.162: V2Trap(185) .1.3.6.1.2.1.1.3.0=56007550 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.9.9.117.2.0.2.1.3.6.1.4.1.9.9.117.1.1.2.1.2.470=5 .1.3.6.1.4.1.9.9.117.1.1.2.1.1.470=1 .1.3.6.1.2.1.47.1.1.1.1.2.470="Test-trap physicalDescr" .1.3.6.1.2.1.47.1.1.1.1.7.470="Test-trap physicalName"
19:05:32.796682 IP 10.105.229.245.59726 > 10.105.229.60.2162: UDP, length 202
19:05:32.796700 IP 10.105.229.60> 10.105.229.245: ICMP 10.105.229.60udp port 2162 unreachable, length 238

Below is switch snmp config:
 
snmp-server host 10.105.229.60 traps version 2c public -à this is default port 162
snmp-server host 10.105.229.60 traps version 2c public udp-port 2162

Nexus treats the two as a separate trap receiver
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.