Specific Troubleshooting

This section describes specific problems you might encounter in SITL simulations and suggests solutions to each. Because there are typically many possible causes of an error, the solution for some problems is a bulleted list of “diagnostic hints”.

Problem

No packets are received by the simulation from the external hardware.

Solution

  • Verify the values of the following gateway node attributes (Table 1 on page 10):

    • Filter String
    • Network Adapter
  • Verify the values of the following workstation node attributes (Table 2 on page 11):

    • IP > IP Host Parameters > Interface Information > Address
    • IP > IP Host Parameters > Interface Information > Subnet Mask

    or router node attributes (Table 3 on page 11):

    • IP > Routing Parameters > Interface Information [row x] > Address

Problem

No packets are received by the external hardware from the simulation.

Solution

  • Verify the values of the following gateway node attribute (Table 1 on page 10):

    • Network Adapter
  • Verify the values of the following workstation node attributes (Table 2 on page 11):

    • IP > IP Host Parameters > Interface Information > Address
    • IP > IP Host Parameters > Interface Information > Subnet Mask

    or router node attributes (Table 3 on page 11):

    • IP > Routing Parameters > Interface Information [row x] > Address

Problem

Real and simulated devices in different subnetworks cannot communicate.

Solution

Set the default gateway of the real hardware to the IP address of the simulated device (router or switch) connected to the SITL gateway.

Problem

Unwanted packets in the network are resulting in unexpected simulation behavior.

Solution

The OPNET Debugger supports a command (ltrace sitl) that enables you to see every packet that flows through SITL. You can use this command to debug simulations to see if unwanted packets are causing unexpected behavior. However, because of the large amounts of output, turning on this trace might slow down your simulation.

Problem

Duplicate responses are received by the external hardware from the simulation.

Solution

Turn on the firewall in the simulation computer. The external hardware might be seeing responses from both the computer and the simulation.