02-02-2009 05:27 PM
Solved! Go to Solution.
02-03-2009 08:51 AM
I think that the issue here lies in the indirection in the IVI layer. First a quick explanation:
Switch Executive configurations use IVI switch device sessions underneath the hood. So however your IVI device is configured is how Switch Exec will try to initialize and use the device.
IVI has a concept of an IVI device and an IVI logical name. The IVI device is the underlying software configuration that tells what topology to use, etc. The logical name is nothing more than a name association to a specific IVI device. The reason that IVI presents these two concepts has to with that first "I" in "IVI"....interchangeable. By allowing users to create logical names it would allow you to create a single piece of test code and then interchange different instruments by only changing the logical name configuration. The logical name is sort of like a "pointer" to a device configuration. IVI allows you to create many different software names and configurations for a single piece of physical hardware.
In order to ease the IVI configuration burden, Switch Executive will actually create these IVI configurations for you automatically so this may be the first time that you are having to interact with them at this level.
So for your specific issue, I believe that the problem is that although Switch Executive is expecting the two Switch Exec Virtual Devices to use two different topologies, the software configuration in IVI is telling it to always use the same topology because it's always using the same name. The best way to fix your problem is to use a different IVI logical/device name to represent the two different topologies.
Hope this helps!
02-03-2009 10:17 AM