Cisco Bug: CSCvi72804 - Faults raised due to fabricId not updated for dhcpClient MO's
Dec 11, 2018
- Cisco Application Policy Infrastructure Controller (APIC)
Known Affected Releases
Symptom: The following faults are raised in APIC: # fault.Record id : 4294967813 ack : no affected : client-[0x010050566234ec] cause : invalid-configuration changeSet : clientEvent:requesting, configIssues:Wrong-fabric-id,duplicate-ip,invalid-podid, configNodeRole:unspecified, decomissioned:no, fabricId:1, hwAddr:00:00:00:00:00:00, id:0x010050566234ec, ip:0.0.0.0, model:0a:00:28:42, nodeId:0, nodeRole:vleaf, podId:1, relayIp:10.0.0.30, spineLevel:0, supported:no childAction : code : F2543 created : 2018-03-28T23:40:48.481+00:00 delegated : no delegatedFrom : descr : Issue - Wrong Fabric Id in MO. Configure the Node Identity policy,Dhcp has assigned duplicate ip. Please decommission this client.,Invalid Pod Id. Check Pod Setup policy dn : subj-[client-[0x010050566234ec]]/fr-4294967813 domain : infra highestSeverity : major ind : modification lc : raised modTs : never occur : 1 origSeverity : major prevSeverity : major rn : fr-4294967813 rule : dhcp-client-invalid-configuration severity : major status : subject : dhcp type : operational Conditions: The "fabricId" used during the initial setup of the APIC Cluster was configured with a value other than "1". The cause of the issue is that the dhcpClient objects that get created are hard coded with a fabricId of 1, so faults are raised since the fabricId's do not match on the system.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases