General
Feature template push fails when device is on boarded fresh or it is on boarded after PNP due to the fact that vManage is trying to push "negotiation auto" for TenGig interface.
Symptom
When vManage creates the template for the device with tenGig interface, it will be rejected by device with following error.
[16-Feb-2022 12:54:11 PST] Device: Data provider returned CONFD_ERRCODE_INCONSISTENT_VALUE (38): inconsistent value: Device refused one or more commands:
negotiation auto
^
% Invalid input detected at '^' marker.
Component Response: "
negotiation auto not allowed on this port"
negotiation auto
^
% Invalid input detected at '^' marker.
Component Response: "
negotiation auto not allowed on this port"
negotiation auto
^
% Invalid input detected at '^' marker.
Component Response: "
negotiation auto not allowed on this port"
Conditions
Issue seen on :
ASR1K platform, for dual rate(Tengig) ports (that support both 1G/10G)
Platforms affected:
1. ASR1001-HX
2. Cisco Catalyst 8500-12X4QC
3. Cisco Catalyst 8500-12X
Conditions:-
Device has no configuration
Device is on Boarded using PnP after config reset
Workaround
Create a add-on CLI template for all the available TenGig interfaces in device and attach it to device feature template.
Set "no negotiation auto" for all the available TenGig interfaces
interface TenGigabitEthernet 0/x/y
no negotiation auto
Further Problem Description
none
