General iTest Topics

[bbaker]

I'd like to suggest a feature to add to topologies.

Display the IP address of a device when you mouse over it.

I've run a test case and one of the devices had died.  I received a failure message that stated "...Failed to connect to: /192.168.1.173...".  When I was using Testbeds, this was fine since the IP address of each device was easily viewable.  However, now that I have built a topology, it is a real pain to try and discover which device has failed.

Thanks!

[IvanS]

Actually in early prototype of editor we had editable text field for IP on device figure below device name. But in final vesion of editor it was removed.

I'll create feature request for it.

[HosoonK]

As a workaround, you can use the device label to include the IP address of the target device.

Note, you can also find all the IP addresses of the associated sessions from the topology editor by,

1. select a device, and from the Properties" View select on the "Session" tab

Thanks,

[PadmajaG]

Two ways to get to the Session tab on the properties view:

Select the device that is associated with the session:

1) Select the Properties view tab in the bottom pane and then select the Session tab and view the ip address

OR

2) Right click for the context menu and then select the "Show Properties view" option. This will bring up the Properties View in the bottom pane and then you can select the "Session" tab and view the ip address

[bbaker]

Thanks for all the responses.

I understand how to find the IP address in a topology, my point was that it is cumbersome when a topology contains 40-60 units.  With a testbed, you could see a single list of all device names with IP addresses without having to click on each individual device.  This made referencing an IP address based on a device name quite simple.  Using a topology, you must click on each device individually before you can see an IP address for it.  All I was trying to suggest was that you could display the IP address for a device along with the name of a device inside the diagram.  That way both pieces of information are easily viewable for all devices without having to perform any additional mouse clicks.

Thanks!

[PaulD]

Thanks for the suggestion.  There are a few complications.  For example, a single device might have multiple IP addresses.  For example, a router that you access via a terminal server may be contacted through the IP address of the terminal server, but the router itself has a different IP address.  Likewise, a single router may have several different IP addresses.  

I realize that in the simple cases, this isn't a problem, and I understand the benefit of seeing that IP address in the diagram.  We'll take a look and perhaps add back in the capability of allowing you to display it there if you choose.