I was trying to map between FI's server port and Chassis IOM's fabric port, using Get-UcsFabricPort cmdlet.
The output of the cmdlet has PeerChassisId as N/A, while PeerDn clearly shows the Chassis id:
PeerChassisId : N/A
PeerDn : sys/chassis-1/slot-1/fabric/port-1
Could it be a bug at the output of this cmdlet?


 
Hi Jason,
 
it's not a bug in Get-UcsFabricPort, that cmdlet is faithfully retreiveing the etherPIo objects in the UCS Managment Information Tree. Take alook at the output below, it is probably very similar to what you are seeing 
 
 
PS C:\> Get-UcsFabricPort -Dn sys/switch-B/slot-1/switch-ether/port-1
 
 
AdminState     : enabled
AdminTransport : ether
ChassisId      : 1
Encap          : unknown
EpDn           : fabric/server/sw-B/slot-1-port-1
IfRole         : server
IfType         : physical
Lc             : available
LicGP          : 0
LicState       : unknown
Locale         : internal
Mac            : 00:07:85:00:00:01
Mode           : fabric
Model          :
Name           :
OperSpeed      : 188
OperState      : up
PeerChassisId  : N/A
PeerDn         : sys/chassis-1/slot-2/fabric/port-1
PeerPortId     : 1
PeerSlotId     : 2
PortId         : 1
Revision       : 0
Serial         :
SlotId         : 1
StateQual      :
SwitchId       : B
Transport      : {ether}
Ts             : 1970-01-01T01:00:00.000
Type           : lan
UnifiedPort    : no
UsrLbl         :
Vendor         :
XcvrType       : unknown
Dn             : sys/switch-B/slot-1/switch-ether/port-1
Rn             : port-1
Status         :
Ucs            : machine
 
 
Now you can add the -Xml option to the cmdlet and your can see the raw XML that goes to and is returned from the Fabric Interconnect.  If you do that for Get-UcsFabricPort you'll see that the XML does not contain a value either. I formated the output a little bit for easier reading.
 
 
PS C:\> Get-UcsFabricPort -Dn sys/switch-B/slot-1/switch-ether/port-1 -Xml
==>machine:
<configResolveClass classId="etherPIo" inHierarchical="false">
  <inFilter>
    <eq class="etherPIo" property="dn" value="sys/switch-B/slot-1/switch-ether/port-1" />
  </inFilter>
</configResolveClass>
 
<==machine:
<configResolveClass cookie="" response="yes" classId="etherPIo">
  <outConfigs>  
    <etherPIo adminState="enabled" adminTransport="ether" chassisId="1"  dn="sys/switch-B/slot-1/switch-ether/port-1" encap="unknown" epDn="fabric/server/sw-B/slot-1-port-1" fltAggr="0" fsmDescr="" fsmPrev="nop" fsmProgr="100" fsmRmtInvErrCode="none" fsmRmtInvErrDescr="" fsmRmtInvRslt="" fsmStageDescr="" fsmStamp="never" fsmStatus="nop" fsmTry="0" ifRole="server" ifType="physical" lc="available" licGP="0" licState="unknown" locale="internal" mac="00:07:85:00:00:01" mode="fabric" model="" name="" operSpeed="52" operState="up" peerChassisId="N/A" peerDn="sys/chassis-1/slot-2/fabric/port-1" peerPortId="1" peerSlotId="2" portId="1" revision="0"  serial="" slotId="1" stateQual=""  switchId="B" transport="ether" ts="1970-01-01T01:00:00.000" type="lan" unifiedPort="no" usrLbl="" vendor="" xcvrType="unknown"/>
  </outConfigs>
</configResolveClass>
 
Hope that helps, what the peerChassisId attribute is intended for and why it says "N/A"? I don't know, perhaps a future feature.
 
Regards,
John