fault F1664

How to resolve fault F1664 with the name fltCoopDomCoopDomVersionLower

Cisco System Model: Fault fltCoopDomCoopDomVersionLower

Cisco System Model: Class ifc:eventmgr:fltCoopDomCoopDomVersionLower

This pages provides an overview over ACI Fault: F1664

Explanation: This fault occurs when the version of the Council Of Oracles Protocol (COOP) running on a leaf (citizen node) or spine (oracle node) is determined by a leaf to be lower than what is currently supported. No impact to connectivity should be seen due to running at lower version. However, failure to upgrade the fabric node firmware on the node in question to the highest supported version of coop may impact coop performance or coop may not operate with supported functionalities introduced in the higher coop version.
Recommended Action: To recover from this fault, try the following actions Verify there is no spine (oracle node) with a lower coop version than highest supported version running in the fabric. To verify the spine with lower version: Use the GUI to examine the maxVersion value under Fabric > Inventory > Pod > Leaf > Protocols > COOP > [domain-name] > Oracle Adjacencies > [spine ip]; or Use REST API to examine the maxVersion value from https://[spine-ip]/api/mo/sys/coop/inst/dom-[name].xml?query-target=subtree&target-subtree-class=coopOracleAdj; or Use CLI to examine the maxVersion value in file /mit/sys/coop/inst/dom-[domain-name]/oracle-[spine-ip] Upgrade the fabric node software on the spine in question to a version that has the highest supported coop version running in the fabric. You can examine other spines to determine what switch firmware version to upgrade to. Verify there is no leaf (citizen node) with a lower coop version than highest supported version running in the fabric. Identify the leaf node that has a lower coop version by doing the following on any spine: Use the GUI to examine the lastLowerVersionAddr under Fabric > Inventory > Pod > Leaf > Protocols > COOP > [domain-name] ; or Use REST API to examine the lastLowerVersionAddr value from https://[spine-ip]/api/mo/sys/coop/inst/dom-[domain-name].xml; or Use CLI to examine the lastLowerVersionAddr value in file /mit/sys/coop/inst/dom-[domain-name] Now confirm the supported highest version for the leaf node, identified from above, is lower than highest supported in fabric as follow: Use the GUI to examine the maxVersion under Fabric > Inventory > Pod > Leaf > Protocols > COOP > [domain-name]; or Use REST API to examine the maxVersion value from https://[leaf-ip]/api/mo/sys/coop/inst/dom-[domain-name].xml; or Use CLI to examine the maxVersion value in file /mit/sys/coop/inst/dom-[domain-name] Upgrade the fabric node software on the leaf in question to a version that has the highest supported coop version running in the fabric. You can examine other leafs to determine what switch firmware version to upgrade to. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

Raised on MO: coop:Dom
Fault Name: fltCoopDomCoopDomVersionLower

Unqualified API Name: coopDomVersionLower

Code: F1664
Applied Mo DN Format

  • topology/pod-[id]/node-[id]/sys/coop/inst/dom-[name]
  • sys/coop/inst/dom-[name]

Type: operational
Cause: protocol-coop-version-mismatch
Severity: warning
Weight: 100
Tags:
Message: None
Help: None
Triggered By: councilMinMaxVersion equals unknown and curVersion equals v1 and maxVersion equals v2

Related content