Operational-cluster-size-distance-cannot-be-bridgedĪPIC does not match the Chassis ID of the The value should be one greater than the currentĮxpansion-contender-message-is-not-heartbeat The following table summarizes the faults for discarded messages:ĪPIC does not match the ChassisID learnedĮxpansion-contender-fabric-domain-mismatchĮxpansion-contender-id-is-not-next-to-oper-cluster-sizeĮxpansion. The following sections describe the two majorĬluster messages that are not from a current cluster peer or cluster expansion Outside of the operational cluster size, source not commissioned, and fabricĪPIC supports a variety of faults to helpĭiagnose cluster problems. Heartbeat rejected-Check the fltInfraIICIMsgSrcOutsider fault.Ĭommon errors include operational cluster size, mismatched ChassisID, source ID Unhealthy data subset related to relocationĬonnectivity issue-Verify connectivity using ping.įabric connectivity-Confirm that fabric connectivity is normal Service is down on an appliance with a data subset that is Unavailable appliance is carrying a data subset that is related to relocation Heartbeat messages are rejected by the new There is no connectivity between the cluster and a new OperationalClusterSize is smaller than the number ofĮxpansion contender (for example, the admin size is 5 and there is not an Issue occurs under the following circumstances: For moreĬonfirm that the missing switch has the correct date and time.Ĭonfirm that the switch can communicate with other Verify that all processes are running on the switch. Verify how long the switch has been active. Verify that the switch has loaded a software image. Identify the switch that is missing from the fabric.Ĭheck whether the switch has requested and received an IP Verify that fabric discovery is complete. The following settings to diagnose the issue: Outside the cluster with a new cluster ID. As a result, oneĬannot join the cluster and displays an expansion-contender-chassis-id-mismatch Information, inspect the fault and reviewĪre configured with the same ClusterID when a cluster expands. OperationalClusterSize to meet the AdminstrativeClusterSize. Variety of conditions can prevent a cluster from extending the Resolve the issue, ensure that you decommission theĭisplays faults during changes to cluster size. Resolve the issue, decommission the APIC after the cluster recovers.īoots with a ChassisID different from the ChassisID registered in the cluster. Member of the cluster becomes unavailable or the cluster splits.Īfter the cluster recovers, the decommissioned Resolve the issue, decommission APIC1 on APIC2, and commission APIC1 again. Scenario, APIC1a discovers APIC2, but APIC2 is unavailable because it is in aĬluster with APIC1, which appears to be offline. Issue can occur after the following sequence of events:ĪPIC1 reboots and becomes active with a new ChassisID (APIC1a) Verify that the fabric name, TEP addresses, and infra (infrastructure) VLAN To correct thisĪdmin credentials do not work because the Is not configured with the correct infra (infrastructure) VLAN. Output of these commands shows different VLANs, the new (infrastructure) VLANs advertised by connected mit/sys/lldp/inst/if-\/ctrlradj/summary-Displays the infra mit/sys/lldp/inst/if-\/ctrlradj/summary-Displays the VLAN configured For instructions on how to add a new APIC, refer to the Cisco APIC Management, Installation, Upgrade, and Downgrade Guide.Ĭonnects to the fabric and loses connection to a leaf switch.įollowing commands to check for an infra (infrastructure) VLAN mismatch: You can add a replacement APIC to the cluster and expand the target and operational size. Operational size is 4 when the reconfigured APIC becomes active. Reduce the cluster size to 4, decommission controller 5, and recommission it as APIC 2.The target size remains 4, and the Leave the target size and replace the APIC. Summarizes common cluster troubleshooting scenarios for the Cisco This chapter contains the following sections:Ĭisco APIC Cluster Failure Scenarios Cluster This chapter contains information about various failure or crash scenarios and possible recovery solutions. Configuring Export Policies for Troubleshooting.Troubleshooting Multipod and Multi-Site Issues.Confirming the Port Security Installation.Determining Why a PIM Interface Was Not Created.Troubleshooting EVPN Type-2 Route Advertisement.Troubleshooting Steps for Endpoint Connectivity Problems.Decommissioning and Recommissioning Switches.Manually Removing Disabled Interfaces and Decommissioned Switches from the GUI.Using the Cisco APIC Troubleshooting Tools.Recovering Cisco APIC Passwords and Accessing Special Logins.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |