Skip navigation
1 2 Previous Next 4473 Views 17 Replies Latest reply: May 17, 2012 3:15 PM by rpetersen RSS
rpetersen Rank: White Belt 32 posts since
May 2, 2012
Currently Being Moderated

May 3, 2012 3:46 PM

Adding back a removed device

I've removed a network device from our zenoss device list however now when I add the device back in it's not listing the components within the device.  I've added back to the correct device type /Network/Router/Cisco but not getting any love back from the system.  Any idea what may be causing this?

 

Thanks,

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    1. May 3, 2012 3:57 PM (in response to rpetersen)
    Re: Adding back a removed device

    Did you remodel it after re-adding it?

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    3. May 3, 2012 4:01 PM (in response to rpetersen)
    Re: Adding back a removed device

    hmm maybe try

    zenmodeler run -d <devicename> -v 10

     

     

    I don't have any ideas aside from reviewing that output to see what might be up.

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    6. May 3, 2012 10:55 PM (in response to rpetersen)
    Re: Adding back a removed device

    su - zenoss

    You have to run it as the zenoss user

     

    You should see the interfaces immediatly. It could take upwards of 20 minutes for graphs to populate depending on your setup.

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    8. May 5, 2012 11:36 AM (in response to rpetersen)
    Re: Adding back a removed device

    I'm not to sure what the reactor settings message indicate, but the output above indicates the modeler IS making progress, and leads me to believe they are an indication of progress. I color coded where each plugin kicks in. My first reaction without seeing the completion of the output, is that you just didnt wait long enough during manual execution, but of course if the automatted runs are also not working, this is probably an incorrect assumption on my part

     

    Is there any chance you could run the command again and just let it run for as long as it takes to complete and provide the full output. Also Can your run tcpdump and confirm that the communications are happening. I suspect they are, but perhaps the raw packets can tell the tell of what is happening during those twisted messages.

     

     

    Output:

    2012-05-04 13:35:59,518 DEBUG zen.SnmpClient: running <zenoss.snmp.NewDeviceMap.NewDeviceMap object at 0x594d850>

    2012-05-04 13:35:59,518 DEBUG zen.SnmpClient: sending queries for plugin zenoss.snmp.NewDeviceMap

    2012-05-04 13:35:59,518 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,863 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,865 DEBUG zen.SnmpClient: running <zenoss.snmp.DeviceMap.DeviceMap object at 0x5a68e50>

    2012-05-04 13:35:59,865 DEBUG zen.SnmpClient: sending queries for plugin zenoss.snmp.DeviceMap

    2012-05-04 13:35:59,865 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,866 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,868 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,869 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,870 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,871 DEBUG zen.SnmpClient: running <zenoss.snmp.CiscoMap.CiscoMap object at 0x5a74f90>

    2012-05-04 13:35:59,871 DEBUG zen.SnmpClient: sending queries for plugin zenoss.snmp.CiscoMap

    2012-05-04 13:35:59,872 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,873 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,875 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,876 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,882 DEBUG zen.twistedsnmp: reactor settings: [7], None

    2012-05-04 13:35:59,882 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,885 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,888 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,892 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,896 DEBUG zen.SnmpClient: running <zenoss.snmp.InterfaceMap.InterfaceMap object at 0x5a774d0>

    2012-05-04 13:35:59,896 DEBUG zen.SnmpClient: sending queries for plugin zenoss.snmp.InterfaceMap

    2012-05-04 13:35:59,897 DEBUG zen.twistedsnmp: reactor settings: [7], None

    2012-05-04 13:35:59,897 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,899 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,900 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,902 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

    2012-05-04 13:35:59,904 DEBUG zen.twistedsnmp: reactor settings: [7], 1.0

  • dpetzel Rank: Brown Belt 1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    10. May 7, 2012 9:09 PM (in response to rpetersen)
    Re: Adding back a removed device

    So it appears you might have missed the -d flag. This output actually seems to be the output of modeling all devices.

     

    You ran:

      ./zenmodeler run 10.10.10.253 -v 10

     

    A more refined run would be:

      ./zenmodeler run -d 10.10.10.253 -v 10

    This second version will limit the output to ONLY the single device, helping to isolate the issues

     

    I'm not sure which device(s) you might be having issues with but I do see this:

    2012-05-07 10:16:44,899 INFO zen.SnmpClient: Device timed out: SNMP info for 38.75.200.1 at 38.75.200.1:161 timeout: 2.5 tries: 2 version: v2c  community: 0**************

    2012-05-07 10:16:44,899 INFO zen.SnmpClient: snmp client finished collection for 38.75.200.1

    2012-05-07 10:16:44,899 WARNING zen.SnmpClient: Device 38.75.200.1 timed out: are your SNMP settings correct?

    So something is up with SNMP connectivity with this device. If this is the problem child, we can start looking there.

    In total I see 3 devices timed out:

    10.10.10.12

    38.75.200.1

    38.75.200.2

     

    Are those the devices having issues or is it 10.10.10.253 (which I suspect based on your command line arguments). Assuming is the 253, It appears that this IP is an interface IP on another device in the system, with an IP of 10.10.254.31 with an interface index of 129

     

    Do you have the same device, but with different IPs added as different devices?

  • jcurry ZenossMaster 1,021 posts since
    Apr 15, 2008
    Currently Being Moderated
    13. May 9, 2012 2:41 PM (in response to rpetersen)
    Re: Adding back a removed device

    Hi Roy,

    There are 3 configuration properties (also known as zProperties) that you can configure either for device classes or for specific devices.  Bring up the Configuration Properties lefthand menu (follow the DETAILS link at the top of the lefthand menu if you are configuring a device class).  You have the following (with their defaults):

     

    zRouteMapCollectOnlyIndirect                    False

    zRouteMapCollectOnlyLocal                        False

    zRouteMapMaxRoutes                                500

     

    Does that fitr the bill fory ou?

     

    Cheers,

    Jane

  • jcurry ZenossMaster 1,021 posts since
    Apr 15, 2008
    Currently Being Moderated
    14. May 9, 2012 2:45 PM (in response to rpetersen)
    Re: Adding back a removed device

    Typically it tends to take 2 polling intervals before graphs show up.  SNMP default polling is 5 mins.  You shouldn't need to wait hours.

     

    Have you changed anything in the performance template or have you changed the SNMP performance collector 5-minute default?  Either would mess up the underlying data collection files.  If you don't have any serious data yet, open a commandwindow and navigate to $ZENHOME/perf/Devices . There should be a directory for each of your devices collecting performance data, probably with an os/interfaces subdirectory hierarchy under each device.  See if you actually have any data files down there. 

     

    Cheers,

    Jane

1 2 Previous Next

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points