You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -471,6 +473,18 @@ When upgrading the switches, traffic traversing a Leaf Switch that is connected
471
473
472
474
To prevent this scenario, ensure that every leaf is connected to at least two Spine Switches (or tier-1 Leaf Switches). This check will alert if any Leaf Switches are found to only be connected to a single Spine Switch (or tier-1 Leaf Switch).
473
475
476
+
### Large APIC Database
477
+
478
+
It is generally expected that individual APIC DB Shard sizes remain below 5G in steady state, even in high scale configurations. If a single shard goes above this size, it can lead to an elongated upgrade timing, or even an upgrade failure, and in most cases is indicative of an underlying condition.
479
+
480
+
The script performs 2 different checks depending on the version you are running.
481
+
482
+
If current version is below 6.1(3), the script checks all APICs' class's object count. If the count is found to be above 150*1000*1000 then it will flag the DME for further investigation.
483
+
484
+
If the current version is 6.1(3f) or above, the script will utilize the newly added `acidiag dbsize` command and check if any of the top large DB files have exceeded 5G.
485
+
486
+
When alerted to this specific warning, Contact TAC to collect a database dump of the DME and shards that are in question for further analysis.
0 commit comments