That's right. I set up two identical systems, except the same OID means something different on the two setups because expansion units are listed in a different order.
Ohhhh....I think I misread your question. You are talking the order of the expansion units. 14 hours in the sun working the booth at the county fair and my brain is fried....

On Thu, Aug 6, 2015 at 8:43 PM, Jeremy <jeremysmi...@gmail.com <mailto:jeremysmi...@gmail.com>> wrote:

    No, this. http://tickets.packetflux.com/kb/faq.php?id=17

    On Thu, Aug 6, 2015 at 8:39 PM, George Skorup <geo...@cbcast.com
    <mailto:geo...@cbcast.com>> wrote:

        This? http://tickets.packetflux.com/kb/faq.php?id=14

        That's mostly for modules not being detected at all. I guess
        reordering modules could potentially have an issue with this
        bug. I've had that happen, remotely too. Usually just a couple
        bus rescans or a base reboot will get them back.

        This reminds me, where's that beta firmware for the
        SyncInjectors and PDUs that does the trip auto reset? Forrest?

        On 8/6/2015 9:23 PM, Jeremy wrote:
        The new firmware addressed this issue.

        On Thu, Aug 6, 2015 at 8:15 PM, Adam Moffett
        <dmmoff...@gmail.com <mailto:dmmoff...@gmail.com>> wrote:

            So I just pick new serial numbers like 1,2,3,4,5 ?


            On 8/6/2015 10:14 PM, George Skorup wrote:

                Yeah. Reorder the serial numbers how you want them
                and then rescan the expansion bus.

                On 8/6/2015 9:08 PM, Adam Moffett wrote:

                    Can you change the order of expansion units?  It
                    doesn't seem to correspond to their physical
                    order in the chain of serial ports.....but I
                    would really like it to.








Reply via email to