11-29-2024 09:51 AM
applying a template to 3560cx (15.2.7.E6) and 9200cx (17.9.4a) automatically adds a bunch of enable traps that I did not configure in the template, other platform models do not have this issue c9300 and 3850s
Do I need to upgrade to a different code version for this to stop getting added automatically?
thanks
11-29-2024 10:52 AM
Once the device is discovered by Catalyst Center and Telemetry is enabled for the device, Catalyst Center will add a number of enable trap commands in the device configuration.
This is the expected behaviour - it's one of the ways Catalyst Center collects assurance data from devices.
Hope this helps.
11-29-2024 05:44 PM
telemetry and device controllability is turned off on our network
12-02-2024 09:07 AM
Catalyst Center shouldn't be adding specific snmp traps. By default, Catalyst Center pushes "snmp-server enable traps" and enables all traps on the device. This helps to avoid attempting to configure traps by PID and the device not accepting the trap command, which then causing the operation to fail.
12-03-2024 08:43 AM
this is weird. other devices did not get pushed this additional config and they are running the same platform 9200, same IOS.. same template
12-03-2024 09:13 AM
Without further details, my guess would be that a telemetry push was also done during the provision task. You can check this by going to Provision → Inventory, then changing the focus to Provision. Then for the device in question, check the status under the provision column to see what jobs where done.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide