DX NetOps

 View Only
  • 1.  Resolving an RPT_SEGMENT

    Posted Nov 03, 2015 02:03 PM

    When you are getting connection information, sometimes there are RPT_SEGMENTS. I can't seem to find any documentation for resolving ip addresses or model handles for the machines on the other side of the virtual switch. I know you can use the fan out on the web interface, I just don't know how to do it from the restful api. Any help would be greatly appreciated.



  • 2.  Re: Resolving an RPT_SEGMENT

    Posted Nov 03, 2015 05:49 PM

    RPT_SEGMENTs are models of model type Fanout.  RPT_SEGMENT is just the model name.  It doesn't extend beyond that.  They have no special intelligence beyond what the Fanout has.  They are created by discovery when two or more devices modeled in Spectrum hear a common MAC address in the transparent bridge table. 


    In the case of VHM, you're seeing them because the switch immediately upstream of the VMs isn't modeled.  Have you modeled the virtual switch?  You aren't missing much without resolving the connections currently resolved to the RPT_SEGMENT models, other than a minor amount of fault suppression.


    As long as the models are set to discover connections on reconfiguration, you can send the reconfigure action 0x1000e to a switch model that hears one of the MAC addresses, and the modeling will complete on its own; or you can just discover the range and let VHM discovery do it for you.  I wouldn't bother with creating associations via the API.  Unless you then lock the connections, discovery is likely to change them anyway.


    Scott



  • 3.  Re: Resolving an RPT_SEGMENT
    Best Answer

    Posted Dec 31, 2015 12:28 PM

    I found a solution, there is a attribute called a segment connection list. This is in the format of 1.0.0.0.145.84.17.0.179.5.24.1 where the first 1 indicates the number of connections and the last 1 indicates the end of the list. This contains model handles and types of devices in this fanout. If you read it as bytes from back to front you will get a type handle and then a type handle.

     

    Process

    1.0.0.0.145.84.17.0.179.5.24.1          Remove tailing 1

    1.0.0.0.145.84.17.0.179.5.24            Remove the count indicator

    145.84.17.0.179.5.24                    Convert to hex

    91.54.11.00.B3.05.18                    Reverse

    18.05.B3.00.11.54.91                    The '00' is a delimiter

    18.05.B3    11.54.91                    Convert to handles

    0x1805B3    0x115491

    model type  model handle