Implementing our PNP solution into our environment and got few deployments in production, It was noticed how chatty the switches that is been provisioned with PnP . Failed to broadcast tftp attempts that just fill up logs and make it really difficult to actually see what the log is saying on the switch. Most of the time, end up going and pulling the historical logs from syslog server since these messages exceed the logging buffer.
Jan 2 2017 07:39:37.830 EST: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/network-confg) failed (TEST-3650-SW-STACK-2)
Jan 2 2017 07:40:15.832 EST: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/cisconet.cfg) failed (TEST-3650-SW-STACK-2)
using DHCP to facilitate PnP,along with Microsoft's DHCP. Got global rules in place for DNS and TFTP. Have created some local rules in the scope which was been used for PNP to point DNS and TFTP to APIC-EM IP.
you could include the "no service config"
as part of the configuration you push.
(you can also apply it post deployment to your existing switches)
This will turn off the tftp attempts.
Please sign in to leave a comment.