Fortigate 200F devices not showing the Firmware version in Spectrum

Products

• Network Observability
• Spectrum

Issue/Introduction

Fortigate 200F devices do not display the Firmware version under Asset Information in Spectrum OneClick Device Information.

 

This article shows how this can be added by using the Model Type Editor (MTE) to customise the Model Type associated to this device.

 

Environment

DX NetOps Spectrum all currently supported releases

Resolution

The OID that contains the version is:

1.3.6.1.4.1.12356.103.2.1.7.0 , OctetString , v7.4.7-build2685 250527 (GA.M)

This is fmSysVersion

Searching for this on the FortinetFortiManager ModelType, it is attribute 0х5b109аб:

Adding this to the NRM_RunningFirmwareAttr using MTE (NOTE: you need to shutdown SpectroSERVER first) for the device Model Type (in this case - FortinetFortiManager):

And then adding the following filter to extract the firmware version number (7.4.7) from the string - v7.4.7-build2685 250527 (GA.M)

v(\d+\.\d+\.\d+)

where:

• v: Matches the literal character "v" at the start of the version string.

• ( ... ): A Capturing Group that isolates the part you want to extract.

• \d+: Matches one or more digits (e.g., "7").

• \.: Matches a literal dot (.).

• \d+: Matches the second set of digits (e.g., "4").

• \.: Matches the second literal dot (.).

• \d+: Matches the final set of digits (e.g., "7").

Add this to NRM_RunningFirmwareFilters attribute using MTE, then commit to database.

This will allow it to fill in the Firmware after device reconfigure or discovery:

Additional Information

NOTE: While the above is for a Fortinet device, the same process can be used for any other make/model. The steps are:

1. Identify the value of the Firmware version on the device
   
   
2. Get a MIB walk of the device using the sapwalk2 utility as per:
   
   KB : How to generate a MIB dump using sapwalk2 / sapwalk
   
   
3. Search through the MIB walk generated in step 2 above to find the Object Identifier (OID) that holds this value.
   
   
4. Find what attribute maps to this OID. If there isn't any, then you can customise a mapping as per:
   
   KB : Mapping Device MIB Object Identifiers (OIDs) to Spectrum model Attributes
   
   
5. Add the Attribute ID from step 4 to the NRM_RunningFirmwareAttr using MTE to the Model Type for the device. In the above example, this was FortinetFortiManager.
   
   
6. Then, if required, add a filter to extract the Firmware version from Attribute ID to the NRM_RunningFirmwareFilters attribute using MTE for same Model Type, then commit to database.