Topic
  • 21 replies
  • Latest Post - ‏2013-04-24T01:35:33Z by ECX2_ki
SystemAdmin
SystemAdmin
430 Posts

Pinned topic ITNM discovery can not find some devices

‏2012-08-29T06:04:23Z |
We installed ITNM3.8(FP6) in Aix 6.1 server successfully and All the services started perfectly.

When Discovery process ended , some devices can not be found network/hop view and NCIM DB. Though these are in discovery scope and out of filtering process, it happen.

What's happen ?

(In Discovery Phase 1 , all devices are found in log file, but some devices had disappeared in the end. Such devices have duplicated sysName. Is this because of the problem ?)
Updated on 2013-03-25T07:32:58Z at 2013-03-25T07:32:58Z by SystemAdmin
  • neil.billett
    neil.billett
    22 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-08-31T14:34:33Z  
    Hi,

    A few questions in response:

    1) Do you know the type of devices that are not being discovered? - are they all the same type?
    2) Which discovery agents do you have enabled?
    3) Can you post your discovery log file?

    thanks,

    Neil
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-03T00:43:59Z  
    Hi,

    A few questions in response:

    1) Do you know the type of devices that are not being discovered? - are they all the same type?
    2) Which discovery agents do you have enabled?
    3) Can you post your discovery log file?

    thanks,

    Neil
    > 1) Do you know the type of devices that are not being discovered? - are they all the same type?
    Types are not same. ( Windows Server,Aix Server,Network S/W...)

    > 2) Which discovery agents do you have enabled?
    Default Setting.

    > 3) Can you post your discovery log file?
    Too big to post. But, if necessary, I try .
  • neil.billett
    neil.billett
    22 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-03T11:13:37Z  
    > 1) Do you know the type of devices that are not being discovered? - are they all the same type?
    Types are not same. ( Windows Server,Aix Server,Network S/W...)

    > 2) Which discovery agents do you have enabled?
    Default Setting.

    > 3) Can you post your discovery log file?
    Too big to post. But, if necessary, I try .
    Hi,

    You mentioned that you were discovering Windows and AIX servers. As you probably know these would be considered to be 'end-nodes' and would certainly not be shown in the Hop View unless you toggled the display of those end nodes. Can you also clarify that end-nodes are definitely not filtered out as part of the Discovery filtering (pre or post discovery)?

    You mentioned also that you had looked in the NCIM db - what was your search query?

    Also - are there any obvious errors or warnings in any of the discovery process logs?

    Sorry for all the questions in response but this is, naturally, a tricky problem to debug without being in front of your system.

    thanks,

    Neil
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-04T01:50:46Z  
    Hi,

    You mentioned that you were discovering Windows and AIX servers. As you probably know these would be considered to be 'end-nodes' and would certainly not be shown in the Hop View unless you toggled the display of those end nodes. Can you also clarify that end-nodes are definitely not filtered out as part of the Discovery filtering (pre or post discovery)?

    You mentioned also that you had looked in the NCIM db - what was your search query?

    Also - are there any obvious errors or warnings in any of the discovery process logs?

    Sorry for all the questions in response but this is, naturally, a tricky problem to debug without being in front of your system.

    thanks,

    Neil
    > You mentioned also that you had looked in the NCIM db - what was your search query?

    I try to query in the NCIM db, but some devices can not be found . By entityName , ipAddress also.
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-04T02:12:34Z  
    Hi,

    You mentioned that you were discovering Windows and AIX servers. As you probably know these would be considered to be 'end-nodes' and would certainly not be shown in the Hop View unless you toggled the display of those end nodes. Can you also clarify that end-nodes are definitely not filtered out as part of the Discovery filtering (pre or post discovery)?

    You mentioned also that you had looked in the NCIM db - what was your search query?

    Also - are there any obvious errors or warnings in any of the discovery process logs?

    Sorry for all the questions in response but this is, naturally, a tricky problem to debug without being in front of your system.

    thanks,

    Neil
    Log file and Trace file is attached.
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-04T09:09:16Z  
    Log file and Trace file is attached.
    Hi ECX2_Ken_Iida..

    Confirm your discovery configuration:
    1) Is the missing device in scope?
    2) Is the ping finder or file finder configured to find the missing device?
    3) Are passwords (snmp and telnet) configured for the missing device and it's neighbours ?

    Check discovery results:
    1) Did ncp_disco find the device (query using ncp_oql):
    does it exist in finders.returns?
    does it exist in Details.returns?
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-07T06:12:20Z  
    Hi ECX2_Ken_Iida..

    Confirm your discovery configuration:
    1) Is the missing device in scope?
    2) Is the ping finder or file finder configured to find the missing device?
    3) Are passwords (snmp and telnet) configured for the missing device and it's neighbours ?

    Check discovery results:
    1) Did ncp_disco find the device (query using ncp_oql):
    does it exist in finders.returns?
    does it exist in Details.returns?
    >Confirm your discovery configuration:
    >1) Is the missing device in scope?
    in scope (checked!)

    >2) Is the ping finder or file finder configured to find the missing device?

    Not missing. Same configuration node was found by discovery.

    >3) Are passwords (snmp and telnet) configured for the missing device and it's neighbours ?

    Not missing (checked!)

    >Check discovery results:
    >1) Did ncp_disco find the device (query using ncp_oql):
    >does it exist in finders.returns?
    >does it exist in Details.returns?

    Exists.
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-07T07:48:58Z  
    >Confirm your discovery configuration:
    >1) Is the missing device in scope?
    in scope (checked!)

    >2) Is the ping finder or file finder configured to find the missing device?

    Not missing. Same configuration node was found by discovery.

    >3) Are passwords (snmp and telnet) configured for the missing device and it's neighbours ?

    Not missing (checked!)

    >Check discovery results:
    >1) Did ncp_disco find the device (query using ncp_oql):
    >does it exist in finders.returns?
    >does it exist in Details.returns?

    Exists.
    Take a look in translations.ipToBaseName table in disco. You mentioned these devices share the same name, so they might have been merged into one device with multiple addresses.

    http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=%2Fcom.ibm.networkmanagerip.doc_3.8%2Fitnm%2Fip%2Fwip%2Fdisco%2Freference%2Fnmip_dsc_track_discov_db_trans_db_iptobasename_tab.html
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-09-07T08:15:43Z  
    Take a look in translations.ipToBaseName table in disco. You mentioned these devices share the same name, so they might have been merged into one device with multiple addresses.

    http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=%2Fcom.ibm.networkmanagerip.doc_3.8%2Fitnm%2Fip%2Fwip%2Fdisco%2Freference%2Fnmip_dsc_track_discov_db_trans_db_iptobasename_tab.html
    I understand.

    Is there no solution to this problem, only I rename them different sysName each other?
  • raffaee
    raffaee
    21 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-11-18T08:04:12Z  
    Hi,
    I notice there is "Undefined symbol ARG_1" warning in ncp_disco trace file.
    See below snapshot taken from ncp_disco trace file in your environment.

    Mon Aug 27 22:17:02 2012 Warning: A required stitcher symbol does not exist. found in file CRivStitcherSymbolTable.cc at line 147 - Undefined symbol ARG_1 referenced in stitcher ModifyIPContainment

    This might cause some devices disappear during discovery stitching.
    Would you mind sharing ModifyIPContainment.stch in your environment?
    Have this stitcher been changed in your environment?

    Aside to this stitcher issue, first step i would take to check whether or not the device is discovered is :

    Step 1 : Go to OQL prompt via "ncp_oql -service disco -username admin -domain <your domain>" where you need to export PATH=$NCHOME/precision/bin:$PATH first
    Or in GUI, you can go to OQL via Management Database Option.

    Step 2 : At OQL prompt, do "select * from Details.returns where m_UniqueAddress = '<IP Address for your missing end-node device>';"
    Pls substitute <IP Address for your missing end-node device> with IP Address for your missing end-node device.

    Pls share with me your result in Step 2 and ModifyIPContainment stitcher which probably has problem.
    Regards,
    Raffaee
  • raffaee
    raffaee
    21 Posts

    Re: ITNM discovery can not find some devices

    ‏2012-11-18T08:22:15Z  
    Hi,
    I notice there is "Undefined symbol ARG_1" warning in ncp_disco trace file.
    See below snapshot taken from ncp_disco trace file in your environment.

    Mon Aug 27 22:17:02 2012 Warning: A required stitcher symbol does not exist. found in file CRivStitcherSymbolTable.cc at line 147 - Undefined symbol ARG_1 referenced in stitcher ModifyIPContainment

    This might cause some devices disappear during discovery stitching.
    Would you mind sharing ModifyIPContainment.stch in your environment?
    Have this stitcher been changed in your environment?

    Aside to this stitcher issue, first step i would take to check whether or not the device is discovered is :

    Step 1 : Go to OQL prompt via "ncp_oql -service disco -username admin -domain <your domain>" where you need to export PATH=$NCHOME/precision/bin:$PATH first
    Or in GUI, you can go to OQL via Management Database Option.

    Step 2 : At OQL prompt, do "select * from Details.returns where m_UniqueAddress = '<IP Address for your missing end-node device>';"
    Pls substitute <IP Address for your missing end-node device> with IP Address for your missing end-node device.

    Pls share with me your result in Step 2 and ModifyIPContainment stitcher which probably has problem.
    Regards,
    Raffaee
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-02-21T08:02:03Z  
    • raffaee
    • ‏2012-11-18T08:22:15Z
    Hi,
    I notice there is "Undefined symbol ARG_1" warning in ncp_disco trace file.
    See below snapshot taken from ncp_disco trace file in your environment.

    Mon Aug 27 22:17:02 2012 Warning: A required stitcher symbol does not exist. found in file CRivStitcherSymbolTable.cc at line 147 - Undefined symbol ARG_1 referenced in stitcher ModifyIPContainment

    This might cause some devices disappear during discovery stitching.
    Would you mind sharing ModifyIPContainment.stch in your environment?
    Have this stitcher been changed in your environment?

    Aside to this stitcher issue, first step i would take to check whether or not the device is discovered is :

    Step 1 : Go to OQL prompt via "ncp_oql -service disco -username admin -domain <your domain>" where you need to export PATH=$NCHOME/precision/bin:$PATH first
    Or in GUI, you can go to OQL via Management Database Option.

    Step 2 : At OQL prompt, do "select * from Details.returns where m_UniqueAddress = '<IP Address for your missing end-node device>';"
    Pls substitute <IP Address for your missing end-node device> with IP Address for your missing end-node device.

    Pls share with me your result in Step 2 and ModifyIPContainment stitcher which probably has problem.
    Regards,
    Raffaee
    ncp_oql Result is attached. Sorry too late.
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-02-21T09:56:39Z  
    • raffaee
    • ‏2012-11-18T08:22:15Z
    Hi,
    I notice there is "Undefined symbol ARG_1" warning in ncp_disco trace file.
    See below snapshot taken from ncp_disco trace file in your environment.

    Mon Aug 27 22:17:02 2012 Warning: A required stitcher symbol does not exist. found in file CRivStitcherSymbolTable.cc at line 147 - Undefined symbol ARG_1 referenced in stitcher ModifyIPContainment

    This might cause some devices disappear during discovery stitching.
    Would you mind sharing ModifyIPContainment.stch in your environment?
    Have this stitcher been changed in your environment?

    Aside to this stitcher issue, first step i would take to check whether or not the device is discovered is :

    Step 1 : Go to OQL prompt via "ncp_oql -service disco -username admin -domain <your domain>" where you need to export PATH=$NCHOME/precision/bin:$PATH first
    Or in GUI, you can go to OQL via Management Database Option.

    Step 2 : At OQL prompt, do "select * from Details.returns where m_UniqueAddress = '<IP Address for your missing end-node device>';"
    Pls substitute <IP Address for your missing end-node device> with IP Address for your missing end-node device.

    Pls share with me your result in Step 2 and ModifyIPContainment stitcher which probably has problem.
    Regards,
    Raffaee
    Additional information.

    Missing end-node devices are not in translations.ipToBaseName.
  • raffaee
    raffaee
    21 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-02-28T06:24:22Z  
    Additional information.

    Missing end-node devices are not in translations.ipToBaseName.
    It seems AssocAddress discovery agent fails to download IP information from the end-node devices.
    Can you do the followings :
    (1) login to OQL
    (2) do "select * from AssocAddress.returns where m_UniqueAddress = '<IP Address for your missing end-node device>';"
    Pls substitute <IP Address for your missing end-node device> with IP Address for your missing end-node device.

    Please share result for (2).
    I'm thinking you can probably use File Discovery to discover your end-node, seed your file with IP Addresses for the end-node devices.

    Regards,
    Raffaee
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-03-04T07:05:06Z  
    • raffaee
    • ‏2013-02-28T06:24:22Z
    It seems AssocAddress discovery agent fails to download IP information from the end-node devices.
    Can you do the followings :
    (1) login to OQL
    (2) do "select * from AssocAddress.returns where m_UniqueAddress = '<IP Address for your missing end-node device>';"
    Pls substitute <IP Address for your missing end-node device> with IP Address for your missing end-node device.

    Please share result for (2).
    I'm thinking you can probably use File Discovery to discover your end-node, seed your file with IP Addresses for the end-node devices.

    Regards,
    Raffaee
    ncp_oql Result is attached.

    Attachments

  • raffaee
    raffaee
    21 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-03-04T10:53:45Z  
    ncp_oql Result is attached.
    Hi ECX2_ki,
    AssocAddress discovery agent is able to download IP Addresses from the end-node devices.
    From data in AssocAddress discovery agent and translations.ipToBaseName, I believe all the end-node devices are present in your topology.

    It seems mgmt ip address for the end-node devices are different from what you've been expecting.
    Here is the list of device name and mgmt ip address :
    (1) Device Name = stcsdsim, Device type = Win Server, "Windows Version 5.2 (Build 3790 Multiprocessor Free)" Mgmt IP Address = 172.30.231.65
    (2) Device Name = stcsdde7, Device type = Linux Server, "Linux stcsdde7.local.toyota-finance.co.jp 2.6.18-238.ESX" Mgmt IP Address = 172.30.231.153
    (3) Device Name = stcsxaa1, Device type = HP Server, "HP Onboard Administrator" Mgmt IP Address = 172.30.238.207
    (4) Device Name = stcsdaa2, Device type = HP Server, "HP Onboard Administrator" Mgmt IP Address = 172.30.238.37

    for each mgmt IP Address listed as above, do a search in OQL using this OQL stmt,
    "select * from workingEntities.finalEntity where m_EntityType = 1 and m_UniqueAddress in ('172.30.231.65','172.30.231.153','172.30.238.207','172.30.238.37'); "
  • SystemAdmin
    SystemAdmin
    430 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-03-25T07:32:58Z  
    • raffaee
    • ‏2013-03-04T10:53:45Z
    Hi ECX2_ki,
    AssocAddress discovery agent is able to download IP Addresses from the end-node devices.
    From data in AssocAddress discovery agent and translations.ipToBaseName, I believe all the end-node devices are present in your topology.

    It seems mgmt ip address for the end-node devices are different from what you've been expecting.
    Here is the list of device name and mgmt ip address :
    (1) Device Name = stcsdsim, Device type = Win Server, "Windows Version 5.2 (Build 3790 Multiprocessor Free)" Mgmt IP Address = 172.30.231.65
    (2) Device Name = stcsdde7, Device type = Linux Server, "Linux stcsdde7.local.toyota-finance.co.jp 2.6.18-238.ESX" Mgmt IP Address = 172.30.231.153
    (3) Device Name = stcsxaa1, Device type = HP Server, "HP Onboard Administrator" Mgmt IP Address = 172.30.238.207
    (4) Device Name = stcsdaa2, Device type = HP Server, "HP Onboard Administrator" Mgmt IP Address = 172.30.238.37

    for each mgmt IP Address listed as above, do a search in OQL using this OQL stmt,
    "select * from workingEntities.finalEntity where m_EntityType = 1 and m_UniqueAddress in ('172.30.231.65','172.30.231.153','172.30.238.207','172.30.238.37'); "
    >"select * from workingEntities.finalEntity where m_EntityType = 1 and
    >m_UniqueAddress in
    >('172.30.231.65','172.30.231.153','172.30.238.207','172.30.238.37'); "

    OK. 
    ('172.30.231.65','172.30.231.153','172.30.238.207','172.30.238.37') are exists , but ('172.30.231.66','172.30.238.197','172.30.238.208','172.30.238.38') are not exists anywhere .
    Why? What's happen?

    For example , 172.30.231.65 and 172.30.231.66 are not same devices , but 172.30.231.65 is discovered and 172.30.231.66 is not discovered.
  • raffaee
    raffaee
    21 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-04-16T05:31:11Z  
    >"select * from workingEntities.finalEntity where m_EntityType = 1 and
    >m_UniqueAddress in
    >('172.30.231.65','172.30.231.153','172.30.238.207','172.30.238.37'); "

    OK. 
    ('172.30.231.65','172.30.231.153','172.30.238.207','172.30.238.37') are exists , but ('172.30.231.66','172.30.238.197','172.30.238.208','172.30.238.38') are not exists anywhere .
    Why? What's happen?

    For example , 172.30.231.65 and 172.30.231.66 are not same devices , but 172.30.231.65 is discovered and 172.30.231.66 is not discovered.

    Hi,

    Let's focus our investigation for 172.30.231.65 & 172.30.231.66 which both devices arent identical.

    (a)Can you do snmpwalk for devices listed below and its command ?

    (a1) snmpwalk -v1 -c <communityString> 172.30.231.65 system

    (a2) snmpwalk -v1 -c <communityString> 172.30.231.66 system

     

    (b) Can you pull Details.returns data from OQL using below command ?

    (b1) select * from Details.returns where m_UniqueAddress in ('172.30.231.65' , '172.30.231.66');

    Im interested to see whether or not m_ExtraInfo->m_SysName or m_ExtraInfo->m_DNSName for '172.30.231.65' and '172.30.231.66' devices are the same.

    Regards,

    Raffaee

  • ECX2_ki
    ECX2_ki
    3 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-04-22T18:58:21Z  
    • raffaee
    • ‏2013-04-16T05:31:11Z

    Hi,

    Let's focus our investigation for 172.30.231.65 & 172.30.231.66 which both devices arent identical.

    (a)Can you do snmpwalk for devices listed below and its command ?

    (a1) snmpwalk -v1 -c <communityString> 172.30.231.65 system

    (a2) snmpwalk -v1 -c <communityString> 172.30.231.66 system

     

    (b) Can you pull Details.returns data from OQL using below command ?

    (b1) select * from Details.returns where m_UniqueAddress in ('172.30.231.65' , '172.30.231.66');

    Im interested to see whether or not m_ExtraInfo->m_SysName or m_ExtraInfo->m_DNSName for '172.30.231.65' and '172.30.231.66' devices are the same.

    Regards,

    Raffaee

    Result of (a)

    # /usr/sbin/snmpinfo -m dump -c public -h 172.30.231.65 system
    1.3.6.1.2.1.1.1.0 = "Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor Free)"
    1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.311.1.1.3.1.2
    1.3.6.1.2.1.1.3.0 = 1616158732
    1.3.6.1.2.1.1.4.0 = ""
    1.3.6.1.2.1.1.5.0 = "STCSDSIA"
    1.3.6.1.2.1.1.6.0 = ""
    1.3.6.1.2.1.1.7.0 = 76

    #  /usr/sbin/snmpinfo -m dump -c public -h 172.30.231.66 system
    1.3.6.1.2.1.1.1.0 = "Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor Free)"
    1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.311.1.1.3.1.2
    1.3.6.1.2.1.1.3.0 = 1616159738
    1.3.6.1.2.1.1.4.0 = ""
    1.3.6.1.2.1.1.5.0 = "STCSDSIA"
    1.3.6.1.2.1.1.6.0 = ""
    1.3.6.1.2.1.1.7.0 = 76

     

    Result of (b)

    |znck:2.> select * from Details.returns where m_UniqueAddress in
    ('172.30.231.65' , '172.30.231.66');

    |znck:3.> |znck:4.> |znck:5.>
    |znck:6.> go
    .
    {
            m_Name='stcsdsim';
            m_UniqueAddress='172.30.231.65';
            m_ManagerId='';
            m_Protocol=1;
            m_UpdAgent='Details';
            m_HaveAccess=1;
            m_PhysAddr='00:1A:4B:4E:5F:20';
            m_ExtraInfo={
                    m_IpForwarding=2;
                    m_SysName='STCSDSIA';
                    m_DNSName='stcsdsim';
                    };
            m_Description='Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT
    COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor
    Free)';
            m_ObjectId='1.3.6.1.4.1.311.1.1.3.1.2';
            m_LastRecord=1;
    }
    {
            m_Name='stcsdsia';
            m_UniqueAddress='172.30.231.66';
            m_ManagerId='';
            m_Protocol=1;
            m_UpdAgent='Details';
            m_HaveAccess=1;
            m_PhysAddr='00:1A:4B:4E:5F:22';
            m_ExtraInfo={
                    m_IpForwarding=2;
                    m_SysName='STCSDSIA';
                    m_DNSName='stcsdsia';
                    };
            m_Description='Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT
    COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor
    Free)';
            m_ObjectId='1.3.6.1.4.1.311.1.1.3.1.2';
            m_LastRecord=1;
    }
    ( 2 record(s) : Transaction complete )
    |znck:1.>

  • raffaee
    raffaee
    21 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-04-23T04:33:32Z  
    • ECX2_ki
    • ‏2013-04-22T18:58:21Z

    Result of (a)

    # /usr/sbin/snmpinfo -m dump -c public -h 172.30.231.65 system
    1.3.6.1.2.1.1.1.0 = "Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor Free)"
    1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.311.1.1.3.1.2
    1.3.6.1.2.1.1.3.0 = 1616158732
    1.3.6.1.2.1.1.4.0 = ""
    1.3.6.1.2.1.1.5.0 = "STCSDSIA"
    1.3.6.1.2.1.1.6.0 = ""
    1.3.6.1.2.1.1.7.0 = 76

    #  /usr/sbin/snmpinfo -m dump -c public -h 172.30.231.66 system
    1.3.6.1.2.1.1.1.0 = "Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor Free)"
    1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.311.1.1.3.1.2
    1.3.6.1.2.1.1.3.0 = 1616159738
    1.3.6.1.2.1.1.4.0 = ""
    1.3.6.1.2.1.1.5.0 = "STCSDSIA"
    1.3.6.1.2.1.1.6.0 = ""
    1.3.6.1.2.1.1.7.0 = 76

     

    Result of (b)

    |znck:2.> select * from Details.returns where m_UniqueAddress in
    ('172.30.231.65' , '172.30.231.66');

    |znck:3.> |znck:4.> |znck:5.>
    |znck:6.> go
    .
    {
            m_Name='stcsdsim';
            m_UniqueAddress='172.30.231.65';
            m_ManagerId='';
            m_Protocol=1;
            m_UpdAgent='Details';
            m_HaveAccess=1;
            m_PhysAddr='00:1A:4B:4E:5F:20';
            m_ExtraInfo={
                    m_IpForwarding=2;
                    m_SysName='STCSDSIA';
                    m_DNSName='stcsdsim';
                    };
            m_Description='Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT
    COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor
    Free)';
            m_ObjectId='1.3.6.1.4.1.311.1.1.3.1.2';
            m_LastRecord=1;
    }
    {
            m_Name='stcsdsia';
            m_UniqueAddress='172.30.231.66';
            m_ManagerId='';
            m_Protocol=1;
            m_UpdAgent='Details';
            m_HaveAccess=1;
            m_PhysAddr='00:1A:4B:4E:5F:22';
            m_ExtraInfo={
                    m_IpForwarding=2;
                    m_SysName='STCSDSIA';
                    m_DNSName='stcsdsia';
                    };
            m_Description='Hardware: x86 Family 6 Model 15 Stepping 6 AT/AT
    COMPATIBLE - Software: Windows Version 5.2 (Build 3790 Multiprocessor
    Free)';
            m_ObjectId='1.3.6.1.4.1.311.1.1.3.1.2';
            m_LastRecord=1;
    }
    ( 2 record(s) : Transaction complete )
    |znck:1.>

    Hi,

    My suggestion is for your to name the windows servers after DNSName, it's apparent DNSName is distinct between 172.30.231.65 and 172.30.231.66 which are stcsdsim and stcsdsia respectively. Any reason why SysName is the same for these 2 devices whereas DNSName is different.

    The reason for that is IpToBaseName.stch discovery stitcher compares SysName from Details.returns table to know whether or not the device is a new device. For this case, the device on 172.30.231.66 is assumed not a device because SysName is present before.

    Look at code snippet from IpToBaseName.stch at line 126 & 127 where SysName comparison is in place.

       110              if( okToAddAddresses == 1 )
       111              {
       112                  Record detailsMatch = NULL;
       113                  foreach( ipNameCheck )
       114                  {
       115                      // Check to see if this is a new device.
       116                      // Note: only data from Details, AssocAddress or
       117                      // translations.ipToBaseName is available at this
       118                      // point in the discovery.
       119                      //
       120                      detailsMatch = RetrieveSingleOQL(
       121                         "select m_UniqueAddress
       122                          from  Details.returns
       123                          where m_UniqueAddress = eval(text,'&m_WorkAddress')
       124                           and m_AddressSpace = eval(text,'&m_AddressSpace')
       125                           and m_ExtraInfo->m_SysName <> NULL
       126                           and m_ExtraInfo->m_SysName =
       127                                  eval(text,'&&m_ExtraInfo->m_SysName')
       128                           and m_ObjectId <> NULL
       129                           and m_ObjectId = eval(text,'&&m_ObjectId');"
       130                      );
     

    Regards,

    Raffaee

  • ECX2_ki
    ECX2_ki
    3 Posts

    Re: ITNM discovery can not find some devices

    ‏2013-04-24T01:35:33Z  
    • raffaee
    • ‏2013-04-23T04:33:32Z

    Hi,

    My suggestion is for your to name the windows servers after DNSName, it's apparent DNSName is distinct between 172.30.231.65 and 172.30.231.66 which are stcsdsim and stcsdsia respectively. Any reason why SysName is the same for these 2 devices whereas DNSName is different.

    The reason for that is IpToBaseName.stch discovery stitcher compares SysName from Details.returns table to know whether or not the device is a new device. For this case, the device on 172.30.231.66 is assumed not a device because SysName is present before.

    Look at code snippet from IpToBaseName.stch at line 126 & 127 where SysName comparison is in place.

       110              if( okToAddAddresses == 1 )
       111              {
       112                  Record detailsMatch = NULL;
       113                  foreach( ipNameCheck )
       114                  {
       115                      // Check to see if this is a new device.
       116                      // Note: only data from Details, AssocAddress or
       117                      // translations.ipToBaseName is available at this
       118                      // point in the discovery.
       119                      //
       120                      detailsMatch = RetrieveSingleOQL(
       121                         "select m_UniqueAddress
       122                          from  Details.returns
       123                          where m_UniqueAddress = eval(text,'&m_WorkAddress')
       124                           and m_AddressSpace = eval(text,'&m_AddressSpace')
       125                           and m_ExtraInfo->m_SysName <> NULL
       126                           and m_ExtraInfo->m_SysName =
       127                                  eval(text,'&&m_ExtraInfo->m_SysName')
       128                           and m_ObjectId <> NULL
       129                           and m_ObjectId = eval(text,'&&m_ObjectId');"
       130                      );
     

    Regards,

    Raffaee

    Thanks . I understand .