Quantcast
Channel: SRX Services Gateway topics
Viewing all articles
Browse latest Browse all 3959

jnxJdhcpLocalServerDuplicateClient traps

$
0
0

I recently reconfigured an SRX300 to use JDHCP. It had been using the deprecated DHCP configuration. Now the firewall is sending hundreds of SNMP traps like those below.

As far as I understand the trap is caused by clients on two different networks with identical MAC addresses requesting DHCP addresses. The problem is that the MAC address in the SNMP trap is invalid and no MAC address on our networks matches any part of it. It is not encoded in any way because the MIB defines it as:
  jnxJdhcpLocalServerMacAddress  OBJECT-TYPE
      SYNTAX       MacAddress
      MAX-ACCESS   accessible-for-notify
      STATUS       current


Attached is a log created by setting the traceoptions for dhcp-service. I don't see anything in the log to indicate what is going on.


Here are the traps generated when the log was created:
SNMPv2-MIB
        snmpTrapEnterprise : JUNIPER-SMI::jnxProducts.1.1.2.133
        sysUpTime : 53:11:14:35.11
        snmpTrapOID : JUNIPER-JDHCP-MIB::jnxJdhcpLocalServerDuplicateClient
JUNIPER-JDHCP-MIB
        jnxJdhcpLocalServerLastDetected : 2017-6-20
        jnxJdhcpLocalServerInterfaceName : ge-0/0/0.0
        jnxJdhcpLocalServerMacAddress : 66:66:66:66:66:66:65:63:3a:66:66:66:66:66:66:38:65:3a:66:66:66:66:66:66:62:35:3a:34:34:3a:36:36:3a:31:35
        jnxJdhcpRouterName : default/default

SNMPv2-MIB
        snmpTrapEnterprise : JUNIPER-SMI::jnxProducts.1.1.2.133
        sysUpTime : 53:11:14:35.12
        snmpTrapOID : JUNIPER-JDHCP-MIB::jnxJdhcpLocalServerDuplicateClient
JUNIPER-JDHCP-MIB
        jnxJdhcpLocalServerLastDetected : 2017-6-20
        jnxJdhcpLocalServerInterfaceName : ge-0/0/2.0
        jnxJdhcpLocalServerMacAddress : 66:66:66:66:66:66:65:63:3a:66:66:66:66:66:66:38:65:3a:66:66:66:66:66:66:62:35:3a:34:34:3a:36:36:3a:31:35
        jnxJdhcpRouterName : default/default

Here are more examples of the jnxJdhcpLocalServerMacAddress field in traps that have been received:

 34:30:3a:34:39:3a:30:66:3a:32:32:3a:32:35:3a:66:66:66:66:66:66:63:33
 34:30:3a:34:39:3a:30:66:3a:32:32:3a:33:35:3a:31:35
 34:30:3a:34:39:3a:30:66:3a:32:32:3a:33:35:3a:37:33
 34:30:3a:34:39:3a:30:66:3a:32:32:3a:33:61:3a:66:66:66:66:66:66:66:66
 34:30:3a:34:39:3a:30:66:3a:32:32:3a:33:64:3a:34:35
 34:30:3a:34:39:3a:30:66:3a:32:32:3a:33:66:3a:37:35
 36:30:3a:66:66:66:66:66:66:66:31:3a:66:66:66:66:66:66:38:39:3a:66:66:66:66:66:66:38:36:3a:37:66:3a:66:66
 66:66:66:66:66:66:62:30:3a:66:66:66:66:66:66:63:30:3a:66:66:66:66:66:66:39:30:3a:36:65:3a:31:63:3a:37:35
 66:66:66:66:66:66:64:63:3a:66:66:66:66:66:66:61:39:3a:37:31:3a:66:66:66:66:66:66:66:65:3a:34:61:3a:66:66
 66:66:66:66:66:66:65:63:3a:66:66:66:66:66:66:38:65:3a:66:66:66:66:66:66:62:35:3a:34:34:3a:36:32:3a:35:38
 66:66:66:66:66:66:65:63:3a:66:66:66:66:66:66:38:65:3a:66:66:66:66:66:66:62:35:3a:34:34:3a:36:34:3a:66:66
 66:66:66:66:66:66:65:63:3a:66:66:66:66:66:66:38:65:3a:66:66:66:66:66:66:62:35:3a:34:34:3a:36:35:3a:66:66
 66:66:66:66:66:66:65:63:3a:66:66:66:66:66:66:38:65:3a:66:66:66:66:66:66:62:35:3a:34:34:3a:36:36:3a:31:35
 66:66:66:66:66:66:65:63:3a:66:66:66:66:66:66:38:65:3a:66:66:66:66:66:66:62:35:3a:34:34:3a:36:37:3a:37:64

Any ideas you have would be appreciated. Thanks.


Viewing all articles
Browse latest Browse all 3959

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>