02-01-2016 12:00 AM
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 output (UCSM version 2.2)
<configScope ...>
<outConfigs ...>
<topSystem dn="sys" ...>
<networkElement ...>
<swFcSanBorder childAction="deleteNonPresent" fsmDescr="" fsmPrev="DeploySuccess" fsmProgr="100" fsmRmtInvErrCode="none" fsmRmtInvErrDescr="" fsmRmtInvRslt="" fsmStageDescr="" fsmStamp="2016-01-25T11:04:14.742" fsmStatus="nop" fsmTry="0" locale="external" name="" rn="border-fc" switchId="B" transport="fc" type="san" uplinkTrunking="disabled">
<swFcoeSanEp adminSpeed="auto" adminState="enabled" chassisId="N/A" childAction="deleteNonPresent" epDn="sys/switch-B/slot-1/switch-ether/port-18" ifRole="fcoe-uplink" ifType="physical" lc="allocated" locale="external" name="" pcId="2" peerChassisId="N/A" peerDn="fabric/san/B/fcoesanpc-2/fcoesanpcep-slot-1-port-18" peerPortId="0" peerSlotId="0" peerState="nonexisting" portId="18" portVsanId="1" rn="fcoesan-ep-slot-1port-18" slotId="1" switchId="B" transport="ether" type="san" udldAdminState="disabled" udldMode="normal"/>
Under <swFcSanBorder...>, we check for ifrole == "fcoe-uplink". But now, the tool throws error because the ifrole value is "network-fcoe-uplink" (UCSM version 2.2(6) )
Note: there were 2 ports configured as FCoE uplink. The ifrole value of 1 port is "network-fcoe-uplink" and the value of 2nd port is "fcoe-uplink"
My question is:
Is API got changed in 2.2(6) OR is this a bug ?
Should I include a OR condition as (network-fcoe-uplink || fcoe-uplink) ?
Thanks,
Karthick
Solved! Go to Solution.
02-01-2016 11:01 PM
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 you.
02-01-2016 11:01 PM
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 you.
02-02-2016 06:04 AM
Hi Karthick,
That makes sense. If you do not already have it be sure to download the UCS emulator, Cisco UCS Platform Emulator (2.5(2aPE1))
Include with the emulator is the API Model documentation, in the documentation all the UCS objects, their attributes and values are shown. For example the ifRole attribute of the swSanFcoeEp is shown as follows
Type: network:PortRole Primitive Type: scalar:Enum8
Overrides:network:IfEp:ifRole
Units: null
Encrypted: false
Access: implicit
Category: TopLevelRegular
Property Validators:
Comments:
|
Hope that helps.
Regards,
John
02-02-2016 08:27 PM
Thank you John. I haven't tried the UCS Emulator. My next step would be using it. Thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide