OIDs for UCS 6300 Series Fabric Interconnect

[smurdza]

How to i add this switch : UCS 6300 Series Fabric Interconnect to sysobject.ids. ?
partial match for sysobjectID .1.3.6.1.4.1.9.12.3.1.3.1662 in database: unknown device ID

I don't find it in : ftp://ftp.cisco.com/pub/mibs/v2/CISCO-PRODUCTS-MIB.my

[g-bougard]

Hi @smurdza
before adding anything to sysobject.ids file, is the partial match sufficient to get the device in GLPI ?
If not, can you join the output of a run of fusioninventory-netinventory script over your device ?
If yes, is there any important missing information ? Indeed, on a partial sysobjectid match, only the device model may be missing.

[smurdza]

Ok,
Thank you @g-bougard .
I think everything is ok in GLPI, switch appear in GLPI and information about firmware and switch ports.
I think device model is missing.

@g-bougard Can you tell me why the same devices, one is correct inventry in GLPI and other has missing information ?
I think firmware information and device firmware is not correct to join do switches.
Example.

[g-bougard]

UCS 6300 Series Fabric Interconnect is probably what find the agent in a standard OID. So yes, this is definitively not what we can expect as an exact model name.
Then I think the sysobject.ids line you expect if the right expected model is UCS 6332 is (each field separated by only one tabulation char):

9.12.3.1.3.1662	Cisco	NETWORKING	UCS 6332

Try to put this line anywhere in the sysobject.ids file.

About the firmware version missing... maybe the installed firmware doesn't provide its version. But this weird if you're sure they are the same and the devices share the same security level for snmp.

[smurdza]

@g-bougard I try did that, but in files CISCO-ENTITY-VENDORTYPE-OID-MIB.my, miss ID 1662 and agent can't join records :

Second firmware qustion, one and second switch have the same information firmware:
Only version is different : 5.0(3)N2(4.04a) and 5.0(3)N2(4.01c)

        <COMPONENT>
          <CONTAINEDININDEX>214</CONTAINEDININDEX>
          <DESCRIPTION>16x10GE + 24X40G Supervisor in Fixed Module-1</DESCRIPTION>
          <FIRMWARE>5.0(3)N2(4.04a)</FIRMWARE>
          <FRU>2</FRU>
          <INDEX>22</INDEX>
          <MANUFACTURER>Cisco Systems, Inc.</MANUFACTURER>
          <MODEL>UCS-FI-6332-16UP</MODEL>
          <NAME>16x10GE + 24X40G Supervisor in Fixed Module-1</NAME>
          <REVISION>1.3</REVISION>
          <SERIAL>XXXXXXXXX</SERIAL>
          <TYPE>module</TYPE>
          <VERSION>5.0(3)N2(4.04a)</VERSION>
        </COMPONENT>

        <COMPONENT>
          <CONTAINEDININDEX>214</CONTAINEDININDEX>
          <DESCRIPTION>16x10GE + 24X40G Supervisor in Fixed Module-1</DESCRIPTION>
          <FIRMWARE>5.0(3)N2(4.01c)</FIRMWARE>
          <FRU>2</FRU>
          <INDEX>22</INDEX>
          <MANUFACTURER>Cisco Systems, Inc.</MANUFACTURER>
          <MODEL>UCS-FI-6332-16UP</MODEL>
          <NAME>16x10GE + 24X40G Supervisor in Fixed Module-1</NAME>
          <REVISION>1.3</REVISION>
          <SERIAL>YYYYYYYYY</SERIAL>
          <TYPE>module</TYPE>
          <VERSION>5.0(3)N2(4.01c)</VERSION>
        </COMPONENT>

[g-bougard]

Okay, I see the component with another firmware version. So I can only guess the 4.01c version is not reporting the version in a standard way, but 4.04a does. Of course, you can upgrade the firmware to verify by yourself. Maybe you can check that in the firmware changelog too.

About the entry missing in the MIB... what can I say ? Report that missing to Cisco ? The MIB in their ftp has its "LAST-UPDATED" date set to june 2018... maybe it is just outdated even if it seems it has been updated on ftp in july this year. Maybe another version exists elsewhere.

Anyway if you want us to investigate more the subject, I can look forward to make a fix in GLPI-Agent but I'll need the snmpwalk for the 2 devices (the one with the 4.01c firmware version and the one with the 4.04a firmware version).

[smurdza]

Hi @g-bougard ,
I did snmpwalk and mib for firmware is the same:

SNMPv2-SMI::mib-2.47.1.1.1.1.9.22 = STRING: "5.0(3)N2(4.01c)"
SNMPv2-SMI::mib-2.47.1.1.1.1.9.1000022 = STRING: "5.0(3)N2(4.01c)"
SNMPv2-SMI::mib-2.47.1.1.1.1.10.22 = STRING: "5.0(3)N2(4.01c)"
SNMPv2-SMI::mib-2.47.1.1.1.1.10.1000022 = STRING: "5.0(3)N2(4.01c)"

SNMPv2-SMI::mib-2.47.1.1.1.1.9.22 = STRING: "5.0(3)N2(4.04a)"
SNMPv2-SMI::mib-2.47.1.1.1.1.9.1000022 = STRING: "5.0(3)N2(4.04a)"
SNMPv2-SMI::mib-2.47.1.1.1.1.10.22 = STRING: "5.0(3)N2(4.04a)"
SNMPv2-SMI::mib-2.47.1.1.1.1.10.1000022 = STRING: "5.0(3)N2(4.04a)"

[smurdza]

@g-bougard
Why GLPI create two device for the same switch ?
Maybe it is problem ?

[g-bougard]

As you're using localized glpi on your screenshot, I'm not sure what you're trying to exactly show.
I can only guess your switch is maybe a stacked switch so "components" are the stacked components and an update in FI4G handles this case in the way you see.
Anyway, I asked you the snmpwalks for the 2 devices. Just exposing few OIDs is not sufficient as this may not be what the agent is looking for.
Just tell if you can't provide them, even in private and we will close this issue as we can do nothing without them.

[smurdza]

I can send you to privat e-mail....

[g-bougard]

Nice, send it to gbougard <at> teclib <dot> com, thanks.