I think it prevents the switch from inserting Option 82 header into the DHCP packet while forwarding. If DHCP option 82 information is being inserted, upstream routed interfaces must be configured with a trust relationship to the downstream DHCP snooping switches that add option 82. This is done with the IP DHCP relay information trusted command, in the VLAN interface configuration toward the downstream switch.
Those messages are debug log messages. Are you debugging DHCP snooping? What exactly is the problem you are having on the 3560?
FYI, that output looks normal to me. A DHCP request is being broadcast from a client that is upstream on the uplink (gi0/1). This switch is seeing that. Then a DHCP reply is seen via broadcast. The switch sees that too. Since the client is not local to the switch, it is ignoring the DHCP reply.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...