<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cisco Management Pack Fabric Interconnect Name in VMware Aria Operations  Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Cisco-Management-Pack-Fabric-Interconnect-Name/m-p/2974795#M19568</link>
    <description>&lt;P&gt;I see the same and this is a true visibility suite drawback. sys/ starting names make it really confusing to tell what blade center issues are on. It should be a bladecenter/sys/device name not sys/devicename. I'm quite surprised TVS has had this around for so long without fixing coding. The dashboards with several&amp;nbsp; sys/blade names (one per blade center) are confusing as user doesn't know which bladecenter is in question until several clicks into the situation.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Jun 2023 19:01:36 GMT</pubDate>
    <dc:creator>vmCalgary</dc:creator>
    <dc:date>2023-06-27T19:01:36Z</dc:date>
    <item>
      <title>Cisco Management Pack Fabric Interconnect Name</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Cisco-Management-Pack-Fabric-Interconnect-Name/m-p/2974657#M19567</link>
      <description>&lt;P&gt;I have the&amp;nbsp;Cisco Management Pack installed and it pulls the UCSM domain information. However, vROPs does not pull the Blade name blade name. It gives the default&amp;nbsp;&lt;SPAN&gt;sys/chassis-3/blade-2. The fabric interconnects do the same thing. I know for the ports you can use the user labels. However, user label is not available under Fabric Interconnect.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jun 2023 20:20:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Cisco-Management-Pack-Fabric-Interconnect-Name/m-p/2974657#M19567</guid>
      <dc:creator>mtnbkr0918</dc:creator>
      <dc:date>2023-06-26T20:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Management Pack Fabric Interconnect Name</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Cisco-Management-Pack-Fabric-Interconnect-Name/m-p/2974795#M19568</link>
      <description>&lt;P&gt;I see the same and this is a true visibility suite drawback. sys/ starting names make it really confusing to tell what blade center issues are on. It should be a bladecenter/sys/device name not sys/devicename. I'm quite surprised TVS has had this around for so long without fixing coding. The dashboards with several&amp;nbsp; sys/blade names (one per blade center) are confusing as user doesn't know which bladecenter is in question until several clicks into the situation.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jun 2023 19:01:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Cisco-Management-Pack-Fabric-Interconnect-Name/m-p/2974795#M19568</guid>
      <dc:creator>vmCalgary</dc:creator>
      <dc:date>2023-06-27T19:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Management Pack Fabric Interconnect Name</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Cisco-Management-Pack-Fabric-Interconnect-Name/m-p/2975873#M19581</link>
      <description>&lt;P&gt;I'm trying to figure out a way around this but it is frustrating when you sell management on an idea and you get this type of information.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jul 2023 11:55:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Cisco-Management-Pack-Fabric-Interconnect-Name/m-p/2975873#M19581</guid>
      <dc:creator>mtnbkr0918</dc:creator>
      <dc:date>2023-07-05T11:55:13Z</dc:date>
    </item>
  </channel>
</rss>

