Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We migrated from Catalyst 6k5 to 9k platform and found that DHCP snooping works different on the new platform. I cannot find if it is a feature or bug. So far we had DHCP snooping only in access layer, not in core. After migration, the end hosts were...
I found the same behaviour on IOS XE 16.6.4, 16.8.1s and 16.9.1. I tested with Catalyst 9500 and 9300. With IOS 16.6.3 speed auto negotiation works, but when I upgraded one switch the link did not come up until I configured speed nonegotiate.
Befo...
The workaround description of the bug is not precise. In fact there are two options how to fix the issue.
1. remove source template from the interface and put all access-session related commands directly on the interface
interface TenGigabitEtherne...
Hi guys,
I struggled several days with upgrade of the DNA appliance from 1.1 to 1.1.2, but in the end I found a working workaround for this bug.
From the CLI I could see the system was failing upgrading:
$ maglev package status
maglev-1 [main -...
Hi,
Anybody knows what is my switch trying to say by "Configuration register = 0x2102 (will be 0x2942 at next reload)"
I googled the meaning of config register 0x2942 but I cannot find any explanation.
Here is the whole CLI output containing th...
Hi,I had the same issue, adding required telemetry subscription solved the issue. Add this to your config:telemetry ietf subscription 10002encoding encode-tdlfilter tdl-uri /services;serviceName=iosevent/syslog_msgstream nativeupdate-policy on-change...
Hi, the sad truth is, that I missed that command Now I check the configuration history I see ip dhcp relay information trust-all on the C6k as well. My bad! Thanks for your tips! M
Configuring "ip dhcp relay information trust-all" on the core switch did the trick. Now DHCP works with snooping enabled on access layer only.RegardsMichal
My issue is that I used to run DHCP snooping on the access layer only, but with 9k in the core I have to enable it on the core switch as well. The question is: Is this a kind of change in the new platform, or is it wrong behaviour?
