A SaaS chassis is cabled to fabric interconnect ports, and UCS Manager never discovers it. Those ports were configured as Ethernet uplink ports toward the LAN. Which port role lets a chassis be discovered?
Select an answer to reveal the explanation.
Short Explanation
You parked the delivery truck at the highway on-ramp and waited for it in the loading dock. Chassis discovery rides the links from the IOM into ports configured as server ports. An uplink port faces the LAN, and a chassis on that port is never discovered.
Full Explanation
UCS Manager discovers a blade chassis when the IOM links land on server ports. The discovery policy then looks at how many of those links are up. Ports left as Ethernet uplinks are northbound ports. They do not run chassis discovery, which is why this chassis stays invisible while the cables look fine. Appliance ports connect an appliance such as a storage array's Ethernet. They are not chassis server links. Fibre Channel storage ports face an array on the SAN. They do not discover an Ethernet-attached IOM. The engineer already used Ethernet uplink ports, and that is the role that fails this job. Caveat: after you change the ports to server ports, the chassis can still sit undiscovered if the discovery policy wants more links than you cabled, or if nobody acknowledged it. Operational check: confirm the port role is server, confirm the link count matches the discovery policy, and then acknowledge the chassis if it is waiting.