Hi ACI board,
I performed an upgrade from ACI 4.2 to 5.2. In our environment, when we add a new pair of leaf switches, we are performing a number of tasks using the API like:
- Registering the switches (fabricNodeIdentP)
- Creating fabric and access leaf switch profiles (fabricLeafP, infraNodeP)
- Switch IP addresses (mgmtRsOoBStNode, mgmtRsInBStNode)
- ... and some more .. .and finally
- Placing the switches in the corresponding firmware maintenance group (maintMaintGrp)
In ACI 5.2 the script runs through without any problem. However, the new switches are not placed in the group. Obviously the MO model changed somehow. Problem is, that:
- The API inspector does not show anything useful when doing this manually using the GUI
- A snapshot comparison before and after placing a switch in a maintenance group using the GUI does not show any differences.
Anybody knows the correct MO class for this? I really, really hope, that Cisco does not do any magic outside the MO tree here (like with Intersight configuration).
