08-15-2012 04:00 PM - edited 03-21-2019 09:50 AM
I downloaded the config.xml file from my ATA before I upgraded the firmware from 1.1.0(011) to 1.2.1(004), then upgraded the firmware. Afterwards, I reset the ATA to factory defaults, provisioned it again, and then downloaded the new config.xml.
I compared the two files and observed the following changes. None of these were set via provisioning, all were the default values.
CWT1_Cadence
CDP_ENABLE
LLDP_ENABLE
Are these changes intentional? Are they correct? The CWT1 setting looks wrong, while the other two just look like someone decided to enable a feature.
If the parameters are incorrect, should I be overwriting them via provisioning back to their previous values?
Solved! Go to Solution.
12-10-2012 04:01 PM
Lance was supposed to communicate the issue back in August that the change was intentional. * means infinity. Documentation to update the docs was to occur as well.
08-16-2012 10:41 AM
I've submitted the cadence change as a bug. It should have stayed at 30.
For the other two, it's as designed.
12-10-2012 03:55 PM
I've been working with Patrick and Lance to test the SPA1x2 lock-up issue (https://supportforums.cisco.com/message/3803687#3803687). Per their instructions, I've been testing the beta of v1.3.1(002).
Just FYI, I notice that the factory default value for CWT1_Cadence is still incorrect in this version. Perhaps it can be addressed before the next firmware goes live?
CWT1_Cadence
I'm fixing this value for our deployed devices via provisioning, but I'm assuming that not everyone has realized they would need to do so.
12-10-2012 04:01 PM
Lance was supposed to communicate the issue back in August that the change was intentional. * means infinity. Documentation to update the docs was to occur as well.
12-10-2012 04:08 PM
Got it. Thanks for the updated info!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: