Typically when discovery fails to start without a specific error it has something to do with the Management connection. First thing to look at is the Management Connection Policy in the Policies Tab under equipment.
If it is not set to Auto Acknowledge then you will need to go to the server (assuming it shows up in the equipment tree) and Select Inventory->CIMC->then select management connection (note it will be grayed out unless the policy is set to user acknowledge).
Then Select Sidband for Single Wire Managment (Single Connect) or Shared LOM for Dual Wire.
If that is not the case then verify that the cables are actually connected to the 2232. You could try differnt ports, but if you do make sure you decom/recom to clear the DME entries in UCSM.
If the server is not even showing up in the equipment tree you should decom, connect a crash cart to the server (keybord and monitor) F8 into CIMC and restore factory defaults. Once the CIMC reboots and you see a link light on the VIC you can then recom the server.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...