Device Queue is a group of input devices waiting for a Qapp to loop.

At this node, you can define the pattern to load input devices into the Device Queue:

▪Device — loads devices in a single device pattern and each device is an independent individual in the Device Queue.

▪Neighbor Pair — loads devices in pairs and each pair contains two devices in neighbors. This Device Queue pattern is often used to compare a device and its neighbor's difference, such as MTU and Duplex mismatch.

▪Path — loads devices in hop pattern. This Device Queue pattern is often used in Qapps to troubleshoot path problems.

▪Table — loads devices from a specified table.

Defining a Device Queue Node

1.Click the Device Queue node on the Canvas tab.

2.Select the device input from the Device Input drop-down list. There are four options as follows:

Device

1)Click the drop-down menu of Device From and select Device.

2)Click Advanced to configure whether to include interface information in the device queue based on your needs.

Neighbor Pair

1)Click the drop-down menu of Device From and select Neighbor Pair.

2)Specify the type of neighbor pairs (such as this and nbr in the device queue table) from the Neighbor Type drop-down list.

▪IPV4/IPV6 L3 topology — includes each device and its Layer 3 neighbor devices.

▪L2 topology — includes each device and its Layer 2 neighbor devices.

▪Any combination — considers every two devices as neighbor pairs. If you select this option, you can skip the next step.

3)Click Advanced to configure the following options based on your needs.

▪Logic to build device pair:

oFilter visible neighbors by map — select the neighbor pairs which are displayed on the map.

Note: This option only takes effect when you run the Qapp from a map.

oFilter neighbors by group — select the neighbor pairs which are both in the group you selected in step 1).

Note: If you select Auto in step 1), the group here refers to the device inputs you will add before running the Qapp.

oOrder of devices is significant — the neighbor pairs are order-sensitive.

▪Whether to include interface column:

oDo not include interfaces — default option.

oInclude Interfaces — adds a new interface column (such as $_intf) in the device queue table at the right side.
Path

Note: With this option selected, you need to run the Qapp from a map with devices and paths among them.

1)Click the drop-down menu of Device From and select Neighbor Pair. The involved devices will be displayed in the device queue table at the right side.

▪One device per Path (each hop) — includes each device only.

▪Downstream Pair — includes each device and its next hop (such as next).

▪Upstream Pair — includes each device and its previous hop (such as prev).

▪Path Triplet — includes each device, its previous and next hop.

2)Click Advanced to configure whether to include interface information in the device queue table based on your needs.

▪Do not include interfaces — only includes the device column (such as $this).

▪Include Interfaces — the default option to add two interface columns (such as $_in_intf and $_out_intf).
Table

Note: To use this option, make sure you have already specified the Global Table.

1)Click the drop-down menu of Device From and select Table.

2)Select the variables you want to include in the device queue from the Variable drop-down list.

3)Select the check box in the device column to set a variable as a device if it stands for a device.  

Tip: You can rename a table header under the Header in the DQ column by double-clicking a table cell.

3.Extend the next node for the Device Queue node based on your needs. For how to extend nodes, see Extending a node for details.

▪Output

▪Device (such as this, nbr, prev, and next, which can be extended depends on the settings you selected in step 2).

 

Next nodes:

▪Device

▪Command

▪Table