Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-users
97030 Views 9 Replies Latest reply: Oct 28, 2009 3:00 PM by Andrea Consadori RSS
lunelson Rank: White Belt
lunelson
20 posts since
Dec 7, 2007
Currently Being Moderated

Oct 23, 2009 5:51 PM

Modeling problems

I'm adding several identical devices (Adtran TA908e's if anyone's curious) to ZenOSS.  About half of them successfully model and I can see their interfaces, etc.  The others log the warning below and fail to show any interfaces at all.  Does anyone have any ideas about what could be causing this?  I'm running ZenOSS Core 2.4.5 on CentOS 5 if that makes a difference.  Thanks.

 

Traceback (most recent call last):

  File "/opt/zenoss/Products/DataCollector/zenmodeler.py", line 606, in processClient

    datamaps = plugin.process(device, results, self.log)

  File "/opt/zenoss/Products/DataCollector/plugins/./zenoss/snmp/InterfaceMap.py", line 129, in process

    om = self.processInt(log, device, iftable[strindex])

  File "/opt/zenoss/Products/DataCollector/plugins/./zenoss/snmp/InterfaceMap.py", line 239, in processInt

    if hasattr(om, 'macaddress'): om.macaddress = self.asmac(om.macaddress)

  File "/opt/zenoss/Products/DataCollector/plugins/CollectorPlugin.py", line 273, in asmac

    for char in val:

TypeError: iteration over non-sequence

  • guyverix ZenossMaster
    guyverix
    846 posts since
    Jul 10, 2007
    Currently Being Moderated
    1. Oct 23, 2009 10:05 PM (in response to lunelson)
    Re: Modeling problems
    I dont know if it helps any, but from what I have been reading in the forums, and zenpack creation tutorials, it looks like it is attmepting to convert a return value to a mac address.
  • Andrea Consadori ZenossMaster
    Andrea Consadori
    863 posts since
    Feb 11, 2008
    Currently Being Moderated
    2. Oct 24, 2009 6:06 AM (in response to lunelson)
    Re: Modeling problems
    try with

    zencommand run -v10 -d devicename

    and paste the output

     

    in the detail output you can see where and why modeler give you an error

  • lunelson Rank: White Belt
    lunelson
    20 posts since
    Dec 7, 2007
    Currently Being Moderated
    3. Oct 26, 2009 10:23 AM (in response to Andrea Consadori)
    Re: Modeling problems

    That doesn't appear to force a remodel (or otherwise replicate the problem).  I found the root cause of the issue, though -- these units that aren't working have a slightly older version of firmware and the phys-address portion of their SNMP is returning gibberish instead of a valid MAC address.  I don't suppose there's a way to get the zenmodeler to continue modeling if it can't find a proper MAC address, is there?  It seems like very un-robust behavior for a commercial product.

     

    [zenoss@zenoss ~]$ zencommand run -v10 -d ADTRAN-SaxtonRiverside
    DEBUG:zen.zencommand:Starting PBDaemon initialization
    INFO:zen.zencommand:Connecting to localhost:8789
    DEBUG:zen.zencommand:Logging in as admin
    INFO:zen.zencommand:Connected to ZenHub
    DEBUG:zen.zencommand:Setting up initial services: EventService, CommandConfig
    DEBUG:zen.zencommand:Chaining getInitialServices with d2
    DEBUG:zen.zencommand:Loaded service EventService from zenhub
    DEBUG:zen.zencommand:Loaded service CommandConfig from zenhub
    DEBUG:zen.zencommand:Queueing event {'severity': 0, 'component': 'zencommand', 'agent': 'zencommand', 'summary': 'started', 'manager': 'localhost', 'device': 'localhost', 'eventClass': '/App/Start'}
    DEBUG:zen.zencommand:Total of 1 queued events
    DEBUG:zen.zencommand:Calling connected.
    DEBUG:zen.zencommand:Fetching configuration from zenhub
    DEBUG:zen.zencommand:Updated configCycleInterval config to 360
    DEBUG:zen.zencommand:Loading classes ['Products.ZenModel.MinMaxThreshold', 'ZenPacks.community.RangeThreshold.thresholds.RangeThreshold']
    DEBUG:zen.thresholds:Updating threshold ('zeneventlog cycle time', ('localhost', ''))
    DEBUG:zen.thresholds:Updating threshold ('zenmodeler cycle time', ('localhost', ''))
    DEBUG:zen.thresholds:Updating threshold ('zenperfsnmp cycle time', ('localhost', ''))
    DEBUG:zen.thresholds:Updating threshold ('zenping cycle time', ('localhost', ''))
    DEBUG:zen.thresholds:Updating threshold ('zenprocess cycle time', ('localhost', ''))
    DEBUG:zen.thresholds:Updating threshold ('zenwin cycle time', ('localhost', ''))
    DEBUG:zen.zencommand:Sent a 'stop' event
    DEBUG:zen.zencommand:stop() called when not running
    INFO:zen.zencommand:Daemon zencommand shutting down
    DEBUG:zen.zencommand:Removing service EventService
    DEBUG:zen.zencommand:Removing service CommandConfig
    DEBUG:zen.zencommand:Finished config fetch
    DEBUG:zen.zencommand:stop() called when not running
    INFO:zen.zencommand:zencommand shutting down

  • guyverix ZenossMaster
    guyverix
    846 posts since
    Jul 10, 2007
    Currently Being Moderated
    4. Oct 26, 2009 11:17 PM (in response to lunelson)
    Re: Modeling problems
    Post what the return values are that it is choking on.
  • jmp242 ZenossMaster
    jmp242
    4,060 posts since
    Mar 7, 2007
    Currently Being Moderated
    5. Oct 27, 2009 8:45 AM (in response to lunelson)
    Re: Modeling problems

    You could always create a ticket...

    --

    James Pulver

    Information Technology Area Supervisor

    LEPP Computer Group

    Cornell University

     

     

     

    lunelson wrote, On 10/26/2009 10:24 AM:

    That doesn't appear to force a remodel (or otherwise replicate the problem).  I found the root cause of the issue, though -- these units that aren't working have a slightly older version of firmware and the phys-address portion of their SNMP is returning gibberish instead of a valid MAC address.  I don't suppose there's a way to get the zenmodeler to continue modeling if it can't find a proper MAC address, is there?  It seems like very un-robust behavior for a commercial product.

     

    Re: Modeling problems$ zencommand run -v10 -d ADTRAN-SaxtonRiverside

    DEBUG:zen.zencommand:Starting PBDaemon initialization

    INFO:zen.zencommand:Connecting to localhost:8789

    DEBUG:zen.zencommand:Logging in as admin

    INFO:zen.zencommand:Connected to ZenHub

    DEBUG:zen.zencommand:Setting up initial services: EventService, CommandConfig

    DEBUG:zen.zencommand:Chaining getInitialServices with d2

    DEBUG:zen.zencommand:Loaded service EventService from zenhub

    DEBUG:zen.zencommand:Loaded service CommandConfig from zenhub

    DEBUG:zen.zencommand:Queueing event {'severity': 0, 'component': 'zencommand', 'agent': 'zencommand', 'summary': 'started', 'manager': 'localhost', 'device': 'localhost', 'eventClass': '/App/Start'}

    DEBUG:zen.zencommand:Total of 1 queued events

    DEBUG:zen.zencommand:Calling connected.

    DEBUG:zen.zencommand:Fetching configuration from zenhub

    DEBUG:zen.zencommand:Updated configCycleInterval config to 360

    DEBUG:zen.zencommand:Loading classes 'Products.ZenModel.MinMaxThreshold', 'ZenPacks.community.RangeThreshold.thresholds.RangeThreshold'

    DEBUG:zen.thresholds:Updating threshold ('zeneventlog cycle time', ('localhost', ''))

    DEBUG:zen.thresholds:Updating threshold ('zenmodeler cycle time', ('localhost', ''))

    DEBUG:zen.thresholds:Updating threshold ('zenperfsnmp cycle time', ('localhost', ''))

    DEBUG:zen.thresholds:Updating threshold ('zenping cycle time', ('localhost', ''))

    DEBUG:zen.thresholds:Updating threshold ('zenprocess cycle time', ('localhost', ''))

    DEBUG:zen.thresholds:Updating threshold ('zenwin cycle time', ('localhost', ''))

    DEBUG:zen.zencommand:Sent a 'stop' event

    DEBUG:zen.zencommand:stop() called when not running

    INFO:zen.zencommand:Daemon zencommand shutting down

    DEBUG:zen.zencommand:Removing service EventService

    DEBUG:zen.zencommand:Removing service CommandConfig

    DEBUG:zen.zencommand:Finished config fetch

    DEBUG:zen.zencommand:stop() called when not running

    INFO:zen.zencommand:zencommand shutting down

    >

  • lunelson Rank: White Belt
    lunelson
    20 posts since
    Dec 7, 2007
    Currently Being Moderated
    6. Oct 27, 2009 9:21 AM (in response to lunelson)
    Re: Modeling problems

    Snmpwalk shows the following:

    IF-MIB::ifPhysAddress.1 = Wrong Type (should be OCTET STRING): INTEGER: 2
    IF-MIB::ifPhysAddress.2 = Wrong Type (should be OCTET STRING): INTEGER: 2
    IF-MIB::ifPhysAddress.3 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.4 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.5 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.6 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.7 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.8 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.9 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.10 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.11 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.12 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.13 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.14 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.15 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.16 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.17 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.18 = Wrong Type (should be OCTET STRING): INTEGER: 1
    IF-MIB::ifPhysAddress.19 = Wrong Type (should be OCTET STRING): INTEGER: 1

     

    I have no idea why Adtran thought that would be an appropriate way to return MAC addresses.

     

    As far as opening a ticket, we unfortunately have not been able to get ZenOSS in the budget, so we just have the Core version which I don't think allows that for free, does it?

  • guyverix ZenossMaster
    guyverix
    846 posts since
    Jul 10, 2007
    Currently Being Moderated
    7. Oct 27, 2009 1:02 PM (in response to lunelson)
    Re: Modeling problems

    I would think that you would want to open the ticket with Adtran, since it is their equipment that is giving the wrong data.  I would assume that you have a support contract with them..

     

    And you can open a bug report even if you are using the Core version.  It is just not as high of a priority.

  • Andrea Consadori ZenossMaster
    Andrea Consadori
    863 posts since
    Feb 11, 2008
    Currently Being Moderated
    8. Oct 28, 2009 3:00 PM (in response to guyverix)
    Re: Modeling problems

    to open a bug ticket

     

    docs/DOC-2446#Foundabug

     

    Found a bug?

    Give us chance to fix it faster! Submit patch or create ticket in bug tracking system (user/pass zenoss/zenoss).

  • lunelson Rank: White Belt
    lunelson
    20 posts since
    Dec 7, 2007
    Currently Being Moderated
    9. Oct 28, 2009 3:08 PM (in response to Andrea Consadori)
    Re: Modeling problems
    I opened a bug ticket (#5723).  Hopefully I followed the proper procedures for setting that up -- I'm not enough of a power user to try writing a patch myself or anything like that.  Thanks for the info and advice.

More Like This

  • Retrieving data ...

Legend

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