Overview

The subnets graphs are not updating or showing 'no data available.' The optimizers are active and you can still create an active subnet report. You may be seeing Subnet graph issues similar to the screenshots below:

And you find the following errors in the logs on the Exinda Appliance which indicate there are duplicate network objects on the device:

Aug 20 16:20:18 exinda mgmtd[2006]: [mgmtd.ERR]: netobj_rename(), md_network_object.c:968, build 1: Error code 14005 (item unexpectedly already exists) returned

Aug 20 16:20:18 exinda mgmtd[2006]: [mgmtd.NOTICE]: md_network_object: Network object 'WAN-ARL' already exists#012

Solution

1. Open an Exinda support ticket with a diagnostic file and a PDF report for the date range that encompasses the issue (e.g. last 24 hours), the error messages in the log that indicate there are duplicate network objects and request a temporary restricted shell license. 
2. If the agent finds that duplicate network objects are the cause of the subnet graphs not updating or showing data, a temporary restricted shell license will be provided for you to resolve this issue or a call can be scheduled for an agent to walk you through the process of performing the following:
   1. Remove the duplicated network objects from any policies

      • To Find and Remove the duplicate Network Objects by querying them using internal commands, follow the instructions provided below:

        1. Check the duplicate Network Objects in our Exinda config by entering the following command:
           

           1. exinda (config t) internal q i s /exinda/system/network_object

           2. Sampe output of the above command for finding the duplicate Network Objects:

              /exinda/system/network_object/static/262 = 262 (uint32)
              /exinda/system/network_object/static/262/location = internal (string)
              /exinda/system/network_object/static/262/monitor = false (bool)
              /exinda/system/network_object/static/262/name = test (string)
              /exinda/system/network_object/static/262/object/10.10.10.10\/32 = 10.10.10.10/32 (inetprefix)
              /exinda/system/network_object/static/263 = 263 (uint32)
              /exinda/system/network_object/static/263/location = internal (string)
              /exinda/system/network_object/static/263/monitor = false (bool)
              /exinda/system/network_object/static/263/name = test (string)
              /exinda/system/network_object/static/263/object/10.10.10.10\/32 = 10.10.10.10/32 (inetprefix)
              
              

           3. Note the ID of the offending Network Object from the example above that would be 262 and 263.

   2. Delete Network Objects as noted in Step-1 by entering the following commands at the CLI (Command Line Interface):

      • exinda (config t) internal set delete - /exinda/system/network_object/static/<network object ID>

   3. Restart the device.

   4. Generate a diagnostic file and check if the duplication is removed

<supportagent> Please see Shell Unlock Key article to generate a customer-specific, temporary restricted shell license.
</supportagent>

Testing

Check that the subnets graphs are now updating and showing data.