cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10561
Views
6
Helpful
11
Replies
Highlighted
Beginner

DHCP snooping not working dropping packets

Dear all,

I recently installed DHCP snooping on a 3750v2 switch (Version 12.2(55)SE4) and configured the uplink(Po2) as a trusted port. The problem is that clients cannot receive an IP address. When I disable DHCP snooping it is working properly. DHCP snooping is configured corectly but I don't have an idea how to resolve it. The debug dhcp snooping packets resulted in the following output;

Jan 9 15:29:29.713: DHCP_SNOOPING: process new DHCP packet, message type: DHCPINFORM, input interface: Po2, MAC da: ffff.ffff.ffff, MAC sa: 0025.b31a.55eb, IP da: 255.255.255.255, IP sa: 172.30.214.47, DHCP ciaddr: 172.30.214.47, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0025.b31a.55eb

Jan 9 15:29:29.713: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 9 15:29:29.722: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 9 15:29:31.509: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

Jan 9 15:29:31.509: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak. Was Po2

Jan 9 15:29:31.509: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

Jan 9 15:29:31.517: DHCP_SNOOPING: received new DHCP packet from input interface (Port-channel2)

Jan 9 15:29:31.517: DHCP_SNOOPING: process new DHCP packet, message type: DHCPINFORM, input interface: Po2, MAC da: ffff.ffff.ffff, MAC sa: 1803.7316.a6f8, IP da: 255.255.255.255, IP sa: 172.30.212.235, DHCP ciaddr: 172.30.212.235, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 1803.7316.a6f8

Jan 9 15:29:31.517: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 9 15:29:31.517: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 9 15:29:40.157: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa2/0/46 for pak. Was Vl1

Jan 9 15:29:40.157: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak. Was Fa2/0/46

Jan 9 15:29:40.157: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa2/0/46 for pak. Was Vl1

Jan 9 15:29:45.140: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

Jan 9 15:29:45.140: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak. Was Po2

Jan 9 15:29:45.140: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

Jan 9 15:29:45.140: DHCP_SNOOPING: received new DHCP packet from input interface (Port-channel2)

Jan 9 15:29:45.140: DHCP_SNOOPING_SW: client address lookup failed to locate client interface, retry lookup using packet mac DA: ffff.ffff.ffff

Jan 9 15:29:45.140: DHCP_SNOOPING_SW: lookup packet destination port failed to get mat entry for mac: 0022.fae9.f204

Jan 9 15:29:45.140: DHCP_SNOOPING_SW: SVI destination port lookup failed for mac: 0022.fae9.f204

Jan 9 15:29:45.140: DHCP_SNOOPING: process new DHCP packet, message type: DHCPINFORM, input interface: Po2, MAC da: ffff.ffff.ffff, MAC sa: 0022.fae9.f204, IP da: 255.255.255.255, IP sa: 172.30.214.79, DHCP ciaddr: 172.30.214.79, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0022.fae9.f204

Jan 9 15:29:45.140: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 9 15:29:45.140: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 9 15:29:45.157: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

Jan 9 15:29:45.157: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak. Was Po2

Jan 9 15:29:45.157: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

Jan 9 15:29:45.157: DHCP_SNOOPING: received new DHCP packet from input interface (Port-channel2)

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: client address lookup failed to locate client interface, retry lookup using packet mac DA: ffff.ffff.ffff

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: lookup packet destination port failed to get mat entry for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: SVI destination port lookup failed for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING: process new DHCP packet, message type: DHCPACK, input interface: Po2, MAC da: ffff.ffff.ffff, MAC sa: 000f.8ff1.7ec0, IP da: 255.255.255.255, IP sa: 172.30.205.218, DHCP ciaddr: 172.30.214.79, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 172.30.205.218, DHCP chaddr: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: client address lookup failed to locate client interface, retry lookup using packet mac DA: ffff.ffff.ffff

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: lookup packet destination port failed to get mat entry for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: SVI destination port lookup failed for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING: can't find client's destination port, packet is assumed to be not from local switch, no binding update is needed.

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: client address lookup failed to locate client interface, retry lookup using packet mac DA: ffff.ffff.ffff

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: lookup packet destination port failed to get mat entry for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: SVI destination port lookup failed for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: client address lookup failed to locate client interface, retry lookup using packet mac DA: ffff.ffff.ffff

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: lookup packet destination port failed to get mat entry for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING_SW: SVI destination port lookup failed for mac: 0022.fae9.f204

Jan 9 15:29:45.157: DHCP_SNOOPING: can't find output interface for dhcp reply. the message is dropped.

Jan 9 15:29:45.207: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

Jan 9 15:29:45.207: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak. Was Po2

Jan 9 15:29:45.207: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Po2 for pak. Was Vl1

nlsw050p#sh ip dhcp snooping statistics

Packets Forwarded                                     = 138

Packets Dropped                                       = 61

Packets Dropped From untrusted ports                  = 0

   

I tested the solution on the same kind of hardware switch and firmware and it worked out fine.

Does anyone have an idea what is causing the clients not to receive an IP address from the DHCP server?

Regards,


Wim

Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

DHCP snooping not working dropping packets

Based on your output I suggest you configure the following command:

no ip dhcp snooping information option

View solution in original post

11 REPLIES 11
Highlighted
Beginner

DHCP snooping not working dropping packets

Based on your output I suggest you configure the following command:

no ip dhcp snooping information option

View solution in original post

Highlighted
Enthusiast

Re: DHCP snooping not working dropping packets

Hi Kyle and Wim,

Kyle,

why do you suggest to issue that command?

no ip dhcp snooping information option

I think that the root of the problem might be elsewhere. But first of all - turning off option 82 is not a good idea. Option 82 is a great thing as it helps to identify from which client did the DHCP message came from and is used to deliver messages back to this client.

Moreover as you see in debug - option 82 is not mentioned anywhere - it seems like it is completely missing.

Wim,

this idea does not come from my mind, but the problem could be in DHCP server. What type of DHCP server do you use Wim? Are you sure that it can insert the received Option 82 into its own messages? Have you tried other DHCP servers or try to take a look at DHCP server debug?

You could try to sniff DHCP messages originated by DHCP server and try to look if Option 82 is present.

The thing is, assuming from output you provided, that Switch does not know to which client deliver messages from server - and that is because of missing Option 82.

Best regards,

Jan

Highlighted
Beginner

Re: DHCP snooping not working dropping packets

I've had countless issues with this feature on 6500's. This feature continues to be 'buggy'.

Sent from Cisco Technical Support iPhone App

Highlighted
Contributor

Re: DHCP snooping not working dropping packets

I agree with Kyle. Unless your dhcp server is configured to handle option 82, which the Cisco router dhcp server is NOT by default, you need to disable the option on the switch. Give it a shot. If it works, you've found the problem.

Sent from Cisco Technical Support iPad App

Highlighted
Hall of Fame Cisco Employee

Re: DHCP snooping not working dropping packets

Kyle and Jeff,

I believe what Jan says is reasonable, and I agree with him. There seems to be an endless confusion about what the Option-82 in DHCP Snooping is for. As the explanation of the Option-82 is lengthy, I suggest first reading the following thread:

https://supportforums.cisco.com/thread/2060498

In short, the Option-82 is used by the switch performing DHCP Snooping to properly guide the related DHCP response back to the client it belongs to, even if the response was broadcasted. Turning off the insertion of Option-82 removes a very helpful clue that helps to limit the delivery of the response only to the client for which it is intended.

An important point, however, that the Option-82 is not the only information used by DHCP Snooping to forward the response back to the corresponding client. The complete order is:

  1. DHCP Option-82, if it has been inserted by the switch processing the response
  2. If the DHCP Option-82 is not present or was not inserted by the switch processing the response, ignore it and use the chaddr field from the DHCP response to look up the egress port in the CAM
  3. If the lookup was unsuccessful, use the frame's destination MAC address to look up the egress port in the CAM
  4. If the lookup was unsuccessful, drop the message

This information was confirmed by Zhizhen Gao from Cisco, see

https://supportforums.cisco.com/message/3409873#3409873

Note that as the broadcast destination MAC address can never successfully looked up in CAM, a broadcast DHCP response will be dropped if the Option-82 cannot be used and the MAC address in the chaddr field was not found in the CAM. By the way, notice that this is what the debugs say: a DHCPACK comes in, the switch does not report any Option-82 present, so it tries to locate the client using the chaddr and fails, then tries to use the destination MAC which is broadcast, and fails again. So it drops the DHCP message altogether. If there was an Option-82 present, the message would be switched out the port described in the Option-82.

Unless your dhcp server is configured to handle option 82, which the  Cisco router dhcp server is NOT by default, you need to disable the  option on the switch.

I beg to differ in several aspects. First, the DHCP server is not supposed to interpret the Option-82. The DHCP server is only expected to take the value of the Option-82 from the client's request and copy it into its own response. And even if it does not, the sequence of steps described earlier shows that the DHCP Snooping-enabled switch can cope with a missing Option-82. So by default, whether the DHCP server does or does not know about Option-82 is not a show-stopper.

Second, you are writing that "Cisco router dhcp is NOT configured to handle option 82 by default". This is a matter of debate. As I explained earlier, DHCP server does not really handle the Option-82 at all, it is only supposed to put it back into its response. This misunderstanding causes a lot of confusion so I am very peculiar about pointing that out. However, what Cisco DHCP implementation does is making a sanity check of received DHCP client messages. If the contain Option-82 but the giaddr field is zero, they consider the packet to be a client's fraud and drop it. However, note that this is a validity verification of the DHCP message contents - not a matter of supporting/not supporting the Option-82 per se. In addition, I have not seen any other DHCP server implementation besides Cisco to do the same - most certainly, the ISC DHCP server does not do anything similar and happily accepts messages with giaddr set to zero and Option-82 present without any additional configuration.

Third, because of how DHCP Snooping works and how it handles the presence/impresence of the Option-82 in the DHCP responses, if any device on the path between the switch and the DHCP server does anything wrong with the DHCP messages carrying Option-82 (like dropping them or doing incorrect choices based on the Option-82 and its contents), it is those devices' fault, not the fault of the DHCP Snooping. It is those devices whose configuration should be corrected, not the DHCP Snooping. The RFC 3046 is very clear on the fact that the Option-82 contents SHOULD be treated as opaque values by the DHCP server. Turning off the insertion of Option-82 in these cases is just a bad practice - it may apparently solve the problem but what it really does is just a workaround, and the problem of mishandling the Option-82-tagged DHCP messages stays unsolved.

I strongly recommend removing the insertion of the Option-82 to be used as a last-resort solution.

Best regards,

Peter

Highlighted

I am completely with Peter in

THE MILK:

  1. put ip helper-address command on your clients gateway if your client and DHCP server are on two different subnets
  2. configure trust relationships on any L2 device all the way to the DHCP from that point forward (including the clients gateway) with the ip dhcp relay information trust-all command.  
  3. Don't put more than one ip helper-address command along your path to the server.
  4. make sure your server is reachable from the client by testing using a static assignment before troubleshooting/debugging snooping.
    1. if not make sure your dynamic routing protocols are FULL/LOADED or static routes are in place end-to-end.
  5. make sure you have configured a DHCP pool for the client to get his IP from.


NOW FOR THE MEAT:

I am completely with Peter in doing things the right way. The issue with doing things the right way sometimes, is that its a painful learning experience.  Futhermore, I will detail my painful findings step by step.  

I've tested in an enterprise hierarchical network (the topology was: client to Access Layer, Access Layer to Distribution Layer, Distribution Layer to Core Layer, and Core Layer to DHCP server).  I shut down all redundancy interfaces so that I was only dealing with these five devices (client, access, distro, core, and dhcp).

Two things I must mention first and foremost:

  1. If you keep placing your client behind a new default gateway for your tests, DON'T forget to write the pool for each layer 3 subnet your host could possibly reside behind!!! I can't stress this enough, if your host has no where to get its address from because there is no pool, you can forget about troubleshooting trust relationships.
  2. If a device is EITHER:
    1. acting as a relay (has ip helper-address command configured) OR
    2. is an IOS device running DHCP, THEN:
  3. You need to configure the ip dhcp relay information trust-all command.

For all tests, the access layer switch had the same commands for all tests:

ip dhcp snooping

ip dhcp snooping vlan 1

int (facing distribution)

   ip dhcp snooping trust

int (facing client)

   ip dhcp snooping limit rate 16

For all tests, the DHCP Server (IOS based) had the same commands for all tests:

ip dhcp relay information trust-all

interface (facing core)

   ip address 10.0.1.1 255.255.255.0

ip dhcp pool NETA

  network 10.0.1.0 /24

  default-router 10.0.1.1

ip dhcp pool NETB

  network 10.0.2.0 /24

  default-router 10.0.2.1

ip dhcp pool NETC

  network 10.0.3.0 /24

  default-router 10.0.3.1

Test 1:  

Client connected to a flat layer 2 network (DHCP server and client on same vlan/broadcast domain). 

Not much was needed for test 1.  

Enable snooping default commands on the access switch, set trust, limit rate, and snoop vlan.  Done.


Test 2:  

Client is on same vlan all the way to the Core Layer. Next, I turned off switchports and made layer 3 routed interfaces.

1. facing the DHCP server (10.0.1.2)

2. facing the distribution layer (10.0.2.1)

Next, I enabled OSPF area 1 for both routed interfaces on the core. (10.0.1.2 and 10.0.2.1)

Next, I enabled OSPF area 1 for my IOS router running DHCP server. (10.0.1.1)

Next, I needed to configure the ip helper-address 10.0.1.1 command on the interface facing the distribution layer.

Finally, I had to configure the ip dhcp relay information trust-all on the core switch.

Test 3:  

Client is on same vlan all the way to the Distribution Layer. Next, I configured SVI's on VLAN 1 (facing client) and VLAN 2 (facing the Core Layer's physical routed interface and set this interface as an access port member of VLAN 2.

interface vlan 1

ip address 10.0.3.1 255.255.255.0

ip helper-address 10.0.1.1 <- acting as a relay so, needs the trust-all association

int vlan 2

ip address 10.0.2.2 255.255.255.0

router ospf 1 

network 10.0.0.0 0.0.255.255 a 0

On the core, OSPF was enabled previously to form a relationship with all 10. interfaces.

Make sure you can source ping vlan 1 to 10.0.1.1

ip dhcp relay information trust-all

In Summary:

For each 'ring outwards', if you will, of layer 3 addresses that your client's DHCP request has to 'hop' through, you'll need at the very least the following two commands: ip dhcp relay information trust-all (or the interface only version of the command) and the ip helper-address <x.x.x.x> command. 

DO NOT PLACE THE HELPER-ADDRESS ON TWO INTERFACES IN THE PATH, IT WILL SCREW YOU UP.

Highlighted
Beginner

Re: DHCP snooping not working dropping packets

Thanks Kyle,

It worked out just fine! The problem has to do with relaying information.

Regards,

Wim

Highlighted
Beginner

DHCP snooping not working dropping packets

We are using Microsoft DHCP server 2008 and the DHCP request are relayed towards it, so we don't use a switch for that purpose. Another switch with exactly the same hardware, firmware and DHCP snooping configuration gave me the following output using debug ip dhcp snooping packets.

I am going to test the no ip dhcp snooping information option command and see if it works. I will keep you posted. Thanks for the fast reply!

Jan 10 07:51:56.707: DHCP_SNOOPING: add relay information option.

Jan 10 07:51:56.707: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:51:56.707: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:51:56.707: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x3 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:51:56.707: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:51:56.707: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:04.022: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:04.022: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/1

Jan 10 07:52:04.022: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:04.022: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/1)

Jan 10 07:52:04.022: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/1, MAC da: ffff.ffff.ffff, MAC sa: 0024.8105.8765, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.8105.8765

Jan 10 07:52:04.022: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:04.022: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:04.022: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:04.022: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x3 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:04.022: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:04.022: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:10.204: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:10.204: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:10.204: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:10.204: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:10.204: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.810d.9dae, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.810d.9dae

Jan 10 07:52:10.212: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:10.212: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:10.212: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:10.212: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:10.212: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:10.212: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:16.454: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:16.454: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:16.454: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:16.454: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:16.454: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.81c4.22d7, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.81c4.22d7

Jan 10 07:52:16.454: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:16.454: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:16.454: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:16.454: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:16.454: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:16.462: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:17.838: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:17.838: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/20

Jan 10 07:52:17.838: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:17.838: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/20)

Jan 10 07:52:17.838: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/20, MAC da: ffff.ffff.ffff, MAC sa: 0025.b319.a1f2, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0025.b319.a1f2

Jan 10 07:52:17.838: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:17.838: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:17.838: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:17.838: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x16 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:17.846: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:17.846: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:20.254: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:20.262: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/1

Jan 10 07:52:20.262: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:20.262: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/1)

Jan 10 07:52:20.262: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/1, MAC da: ffff.ffff.ffff, MAC sa: 0024.8105.8765, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.8105.8765

Jan 10 07:52:20.262: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:20.262: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:20.262: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:20.262: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x3 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:20.262: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:20.262: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:21.260: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:21.260: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:21.260: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:21.260: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:21.260: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.81c4.22d7, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.81c4.22d7

Jan 10 07:52:21.260: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:21.260: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:21.260: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:21.260: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:21.260: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:21.260: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:21.847: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:21.847: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/20

Jan 10 07:52:21.847: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:21.847: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/20)

Jan 10 07:52:21.847: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/20, MAC da: ffff.ffff.ffff, MAC sa: 0025.b319.a1f2, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0025.b319.a1f2

Jan 10 07:52:21.847: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:21.847: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:21.847: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:21.847: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x16 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:21.847: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:21.847: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:28.340: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:28.340: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:28.340: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:28.340: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:28.340: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.81c4.22d7, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.81c4.22d7

Jan 10 07:52:28.340: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:28.340: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:28.340: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:28.340: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:28.349: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:28.349: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:30.848: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:30.848: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/20

Jan 10 07:52:30.848: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:30.848: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/20)

Jan 10 07:52:30.848: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/20, MAC da: ffff.ffff.ffff, MAC sa: 0025.b319.a1f2, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0025.b319.a1f2

Jan 10 07:52:30.848: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:30.848: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:30.848: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:30.848: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x16 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:30.848: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:30.848: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:41.989: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:41.989: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:41.989: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:41.989: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:41.989: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.810d.9dae, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.810d.9dae

Jan 10 07:52:41.989: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:41.989: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:41.989: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:41.989: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:41.989: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:41.989: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:45.344: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:45.344: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:45.344: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:45.344: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:45.344: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.81c4.22d7, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.81c4.22d7

Jan 10 07:52:45.344: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:45.344: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:45.344: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:45.344: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:45.352: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:45.352: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:45.789: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:45.789: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:45.789: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:45.789: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:45.789: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.810d.9dae, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.810d.9dae

Jan 10 07:52:45.789: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:45.789: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:45.789: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:45.789: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:45.789: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:45.797: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:46.074: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:46.074: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/20

Jan 10 07:52:46.074: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/20 for pak.  Was Vl1

Jan 10 07:52:46.074: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/20)

Jan 10 07:52:46.074: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/20, MAC da: ffff.ffff.ffff, MAC sa: 0025.b319.a1f2, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0025.b319.a1f2

Jan 10 07:52:46.074: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:46.074: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:46.074: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:46.074: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x16 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:46.074: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:46.074: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:52.726: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:52.726: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/1

Jan 10 07:52:52.726: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:52.726: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/1)

Jan 10 07:52:52.726: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/1, MAC da: ffff.ffff.ffff, MAC sa: 0024.8105.8765, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.8105.8765

Jan 10 07:52:52.726: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:52.726: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:52.726: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:52.726: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x3 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:52.726: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:52.726: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:53.154: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:53.154: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:52:53.154: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:52:53.154: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:52:53.154: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.810d.9dae, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.810d.9dae

Jan 10 07:52:53.154: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:53.154: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:53.154: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:53.154: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:53.154: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:53.162: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:52:56.526: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:56.526: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/1

Jan 10 07:52:56.526: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:52:56.526: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/1)

Jan 10 07:52:56.526: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/1, MAC da: ffff.ffff.ffff, MAC sa: 0024.8105.8765, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.8105.8765

Jan 10 07:52:56.526: DHCP_SNOOPING: add relay information option.

Jan 10 07:52:56.526: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:52:56.526: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:52:56.534: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x3 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:52:56.534: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:52:56.534: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:53:05.158: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:53:05.158: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/1

Jan 10 07:53:05.158: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/1 for pak.  Was Vl1

Jan 10 07:53:05.158: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/1)

Jan 10 07:53:05.158: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/1, MAC da: ffff.ffff.ffff, MAC sa: 0024.8105.8765, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.8105.8765

Jan 10 07:53:05.158: DHCP_SNOOPING: add relay information option.

Jan 10 07:53:05.158: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:53:05.158: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:53:05.158: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x3 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:53:05.158: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:53:05.158: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Jan 10 07:53:10.158: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:53:10.158: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Vl1 for pak.  Was Fa1/0/4

Jan 10 07:53:10.158: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Fa1/0/4 for pak.  Was Vl1

Jan 10 07:53:10.158: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/4)

Jan 10 07:53:10.158: DHCP_SNOOPING: process new DHCP packet, message type: DHCPDISCOVER, input interface: Fa1/0/4, MAC da: ffff.ffff.ffff, MAC sa: 0024.810d.9dae, IP da: 255.255.255.255, IP sa: 0.0.0.0, DHCP ciaddr: 0.0.0.0, DHCP yiaddr: 0.0.0.0, DHCP siaddr: 0.0.0.0, DHCP giaddr: 0.0.0.0, DHCP chaddr: 0024.810d.9dae

Jan 10 07:53:10.158: DHCP_SNOOPING: add relay information option.

Jan 10 07:53:10.158: DHCP_SNOOPING_SW: Encoding opt82 CID in vlan-mod-port format

Jan 10 07:53:10.158: DHCP_SNOOPING_SW: Encoding opt82 RID in MAC address format

Jan 10 07:53:10.158: DHCP_SNOOPING: binary dump of relay info option, length: 20 data:

0x52 0x12 0x1 0x6 0x0 0x4 0x0 0x1 0x1 0x6 0x2 0x8 0x0 0x6 0x2C 0x36 0xF8 0x56 0x1D 0x80

Jan 10 07:53:10.166: DHCP_SNOOPING_SW: bridge packet get invalid mat entry: FFFF.FFFF.FFFF, packet is flooded to ingress VLAN: (1)

Jan 10 07:53:10.166: DHCP_SNOOPING_SW: bridge packet send packet to cpu port: Vlan1.

Highlighted

Re: DHCP snooping not working dropping packets

!

interface FastEthernet1/0/20

switchport mode access

spanning-tree portfast

ip dhcp snooping limit rate 100

!

Jan 10 07:52:46.074: DHCP_SNOOPING: received new DHCP packet from input interface (FastEthernet1/0/20)

Sounds fishy though but what ports does your DHCP server sit on and what ports are being used for trunking?

Regard

Daniel

Highlighted
Beginner

Re: DHCP snooping not working dropping packets

The problem is solved by using the command no ip dhcp snooping information option provided by Kyle. You need to use this command when you are relaying DHCP packets.

Thanks for your help!

Highlighted
Hall of Fame Cisco Employee

Re: DHCP snooping not working dropping packets

Hello Wim,

It may seem like I'm beating a dead horse here but I still don't believe the deactivation of the Option-82 is the correct solution here. First, read my response here:

https://supportforums.cisco.com/message/3825001#3825001

Second, would you mind posting a topology of your network with the depiction of the placement of the switch doing the DHCP Snooping, the DHCP server, and any devices inbetween. In particular, is there any other switch between the access switch and the DHCP server that also performs DHCP Snooping? Chaining switches that perform DHCP Snooping will cause troubles where the deactivation of the Option-82 apparently helps but the correct solution is to run DHCP Snooping on access switches only.

Best regards,

Peter

Content for Community-Ad