glpi-project / sysobject.ids

Repository to store sysobject.ids file, used for snmp network discovery
GNU General Public License v2.0
2 stars 9 forks source link

Add Dell S5212F-ON network switch #30

Closed GuidoWilden closed 4 months ago

GuidoWilden commented 4 months ago

Here the details:

glpi-netdiscovery --credentials version:2c,community:private --debug --host 10.120.20.3
[debug] initializing job 1
[debug] initializing block 10.120.20.3-10.120.20.3
[debug] Current netdiscovery run expiration timeout: few minutes
[debug] using 1 netdiscovery worker
[debug] starting job 1 with 1 ip to scan using 1 worker
[debug] #1, scanning 10.120.20.3
[debug] #1, partial match for sysobjectID .1.3.6.1.4.1.674.11000.5000.100.2.1.18 on partial SysObject ID
[debug] #1, - scanning 10.120.20.3 with SNMP, credentials 1: success
[debug] #1, - scanning 10.120.20.3 with netbios: no result
[debug] #1, - scanning 10.120.20.3 with echo ping: success
[debug] #1, - scanning 10.120.20.3 in arp table: no result
<?xml version="1.0" encoding="UTF-8"?>
<REQUEST>
  <CONTENT>
    <DEVICE>
      <AUTHSNMP>1</AUTHSNMP>
      <CONTACT>Contact Support</CONTACT>
      <DESCRIPTION>Dell EMC Networking OS10 Enterprise.
Copyright (c) 1999-2022 by Dell Inc. All Rights Reserved.
System Description: OS10 Enterprise.
OS Version: 10.5.3.3.
System Type: S5212F-ON</DESCRIPTION>
      <DNSHOSTNAME>10.120.20.3</DNSHOSTNAME>
      <FIRMWARE>10.5.3.3</FIRMWARE>
      <IP>10.120.20.3</IP>
      <IPS>
        <IP>10.1.1.9</IP>
        <IP>10.120.20.3</IP>
        <IP>127.0.0.1</IP>
        <IP>127.100.101.2</IP>
      </IPS>
      <LOCATION>United States</LOCATION>
      <MAC>1c:72:1d:b5:f6:ff</MAC>
      <MANUFACTURER>Dell</MANUFACTURER>
      <MODEL>S5212F-ON</MODEL>
      <SERIAL>TH0WND1VCET0005I001L</SERIAL>
      <SNMPHOSTNAME>ldnaz-edgesw01</SNMPHOSTNAME>
      <TYPE>NETWORKING</TYPE>
      <UPTIME>195 days, 22:07:36.91</UPTIME>
    </DEVICE>
    <MODULEVERSION>6.1</MODULEVERSION>
    <PROCESSNUMBER>1</PROCESSNUMBER>
  </CONTENT>
  <DEVICEID>foo</DEVICEID>
  <QUERY>NETDISCOVERY</QUERY>
</REQUEST>
[debug] #1, #1, worker termination
[debug] #1, Netdiscovery worker terminated

snmpwalk output: snmpwalk.txt.zip

GuidoWilden commented 4 months ago

Not sure if this one has slipped through the cracks.

g-bougard commented 4 months ago

Hi @GuidoWilden

do you have this line in your sysobject.ids ?

674.11000.5000.100.2    Dell    NETWORKING

Anyway the following should help:

674.11000.5000.100.2.1.18   Dell    NETWORKING  S5212F-ON

I still have to check if I can improve new Dell MibSupport module to better support this kind of Dell devices.

GuidoWilden commented 4 months ago

Thank you @g-bougard , made that change but still didn't work as expected. The switch did get created in the databases all along but weirdly no ports, or only the management port. I now created the xml on command line and imported it, so all good. I have seen this before though. There is the odd switch that just will not import properly via the task triggered from the GUI. Run it on command line and all is fine.

g-bougard commented 4 months ago

Maybe you have configured a too short snmp timeout for netinventory task in GLPI and the device doesn't respond in time in that case during ports inventory.

GuidoWilden commented 4 months ago

Cranked it all the way up to 60 but still no ports.

g-bougard commented 4 months ago

That's really weird. Can you share the log part for such a device when run from service with debug2 enabled ?

Also I just pushed an update on Dell MibSupport module to enhance support for Dell os10 products. This means sysobjectid.ids file updates should not be required for other models.

Also the module will set ServiceTag as AssetTag, not sure this is really valuable or in the right place, tell me.

GuidoWilden commented 4 months ago

Maybe the xml's reveal something. Archive.zip

GuidoWilden commented 4 months ago

Rereading your previous post: these are the only two switches running OS/firmware 10.5.3.3. Maybe worth updating. We have more switches on v10 but they are running 10.5.4.0 and these came in perfectly fine.

g-bougard commented 4 months ago

In the log you posted earlier, I only saw the netdiscovery part, and this is the netinventory part which is really interesting. You can eventually create a job with a single ip to scan to limit the output.

GuidoWilden commented 4 months ago

Thank you for the tip. I have limited it to those two switches. glpi-agent.log.zip

g-bougard commented 4 months ago

Okay, this is a well-known problem which I think comes from glpi-inventory plugin: as few ips are reported during netdiscovery, the plugin doesn't register the right ip to use when netinventory is requested. Here the first one will be tried on 10.1.1.9 and the second on 10.1.1.10. As SNMP is not answering on these ips, you only have datas related to netdiscovery.

Is there any good reason these ips exist on these devices ?

We still tried to figure out this problem in the past but I don't remember exactly why @skita told me we can't make it works.

My guess is if you use GLPI-Agent ToolBox feature you'll obtain what you expect as it runs netinventory immediatly with the ip used for netdiscovery. But I don't know what could be done with glpi-inventory plugin at that time. Maybe you can manage to remove these ips from the device if they are not really used.

GuidoWilden commented 4 months ago

Thank you @g-bougard, I will enquire with our network folks regarding those IPs. If they can't be deleted I will try and use the Toolbox feature. Something I have yet to play with.