A SaaS platform operator wants the published hardware advisory that affects a claimed UCS server, not a copy of that server's frames. Where should the operator look?
Select an answer to reveal the explanation.
Short Explanation
An advisory is a recall notice on the equipment, not a camera pointed at the traffic. You open the Intersight advisories for the claimed server and read the hardware or firmware issue listed there. A monitoring session can copy frames, and it will not tell you that the server is named in a published advisory.
Full Explanation
Intersight advisories match claimed devices against published hardware and software issues and show the operator which servers are affected. That is the list a SaaS operator opens when the question is a published advisory rather than a packet. Traffic monitoring on a fabric interconnect copies frames from a source such as a virtual NIC to a destination. It proves what was on the wire, and it does not list advisories. The Fibre Channel name server records which fibre devices have logged in. It has no inventory of UCS hardware advisories. The boot policy sets the order of boot devices for a server profile. It does not change when Cisco publishes an advisory, and reading it will not show the advisory text. Caveat: the server has to be claimed in the Intersight account, or the advisory list has no device to match against this published notice. Operational check: open the advisories for the claimed server, confirm the advisory identifier matches the notice you are tracking, and confirm a frame capture was not the source of that finding at all.