Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello, As per https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/unified-computing-system-adapters/datasheet-c78-741130.html , I don't see Catalyst is supported switch with VIC1400 series. There was a question posted in our communit...
Hello Folks,I'm looking for Visio stencils for the below products and couldn't find it in https://www.cisco.com/c/en/us/products/visio-stencil-listing.html Products that I need Visio stencils are:N9K-C9364N9K-C9348GC-FXPCisco MDS switches: C9396S-K9C...
Hello,We have a validation tool that checks for UCS cabling best practices. For End-to-End FCoE, the tool checks for 2 FCoE links connected from Nexus switch A to Fabric Interconnect A. We capture the same by using the below XPATH of the UCS XML out...
Hello,I have a script that pulls the UCS version and the Blade adaptor information (model, firmware, etc) from UCS XML API output. The object dn="sys" has all the information I need. But I'm getting the UCS version which is different from <aaaLogin> ...
Hello,I'm trying to get VIC adaptor on the blade and its running firmware. I have preloaded VIC adaptor details in my script which are supported for the Cisco UCS blades. For eg, (1240, 1225, 1227, M81KR, etc). So, I need to match any one from this l...
Hello,FYI. Found the answer to the query.Looks like “network-fcoe-uplink” value shows up in XML output if the port is configured as unified uplink and “fcoe-uplink” value shows up in the XML output if the port is configured as FcoE Uplink port.Thank ...
The tool uses UCSM XML API and we cannot deviate from that. Anyways, I have figured it out in the XML API. To get the VIC adapter models(like 1240, 1280, etc) one has to map the model or pid. Below is the list I came up with and it worked in multiple...
