3 Replies Latest reply on Jul 30, 2019 4:01 PM by Lisa Keeler

    Modeling the Physical Device for Cisco Nexus VDC

    Jason Cheung
      Share This:

      Hello All!

       

      We're currently leveraging cisco nexus VDCs and we create multiple partitions from a single physical nexus switch. It is currently causing a problem because our CMDB folks believe that all Serial Numbers should be unique. Fine... easy to do with a custom sync mapping and use the partitionID instead. However, we also didnt like the fact that all the partitions are discovered without any relationship to one another. That is to say, if the physical switch ever goes down, it will impact all of the partitions and that is not modeled. However, I am having a hard time writing a sync pattern for this because there are also no attributes that I can traverse into in order to create the relationship.

       

      Does anyone have an idea of tying these VDCs together?

       

      Thanks -

        • 1. Re: Modeling the Physical Device for Cisco Nexus VDC
          Lisa Keeler

          Would it help to create SerialNumber in the CMDB by concatenating the serial and the partition_id?

           

          as far as modeling, I don't know.  This is a virtual device? 

           

          Is Cisco Nexus VDC supported OOTB?  (I don't see it on the list).  Or, do you have an SNMPManagedDevice?

           

          Send your syncmapping pattern and more details for more discussion, or open a support case.

          1 of 1 people found this helpful
          • 2. Re: Modeling the Physical Device for Cisco Nexus VDC
            Jason Cheung

            Hi Lisa,

             

            We made the Serial Numbers Unique by essentially syncing the partition_id. The Partition_ID appears to be a concatenated format of the $SerialNumber.$VDC_ID which works well for us. The Cisco Nexus VDCs are Nexus switches with logical partitions that are created. I believe we do support cisco nexus' devices and there are even attributes for the Nexus VDC ID.

             

            The only problem now is to do a syncmapping that will make all these logical partitions a child of a physical chassis which is not modeled in ADDM.

            I took a stab at this, but I was told by support that since we do not have a model for the physical chassis, it will not be possible and would probably be best left as a RFE for the next TKU.

            • 3. Re: Modeling the Physical Device for Cisco Nexus VDC
              Lisa Keeler

              Hi Jason,

               

              I see a similar discussion here:  Re: Switch Stack Represented in Atrium

               

              On the 2nd page of the posting, our Product manager said:

              "

              We are still in development on the solution for the switch stack serial number logic.  At this time, we are targeting the August TKU release.

              "

               

              Lisa

              1 of 1 people found this helpful