Device Certification


SevOne certifies new SNMP devices in 10 business days or less, while competitors often take months to programmatically certify a new device. The ability to quickly discover and certify new devices ensures that there is no gap in performance reporting when you deploy a new SNMP enabled device. SevOne Support Engineers will certify your device within 10 days from the day when you file a support case that provides the applicable information. Alternatively, the SevOne NMS supports a self-certification process that you can perform with or without our assistance.

The SevOne standard support agreement includes the ability for customers to request SevOne assistance with the certification of network devices and servers for inclusion in their SevOne SNMP certified device library. This is a no-charge event that provides you with a fast and effective way to ensure that you have the most complete visibility of your network and related devices.

Device Certification Process

SevOne supports a three step process for device certification is as follows:

Step 1: Customer Provides Device Information

The customer provides SevOne with the following information:

  • Device Manufacturer (e.g., Cisco, Alcatel)
  • Device Role (e.g., Router, Packet Shaper)
  • The name and IP address of the device as it was added into SevOne
  • Key object and indicator information required, including OID names
  • Any relevant new MIBs associated with the device
  • An SNMP walk from the new device

Step 2: SevOne Builds Device Certification

After you submit a support ticket or send the required information via e-mail, SevOne reviews the files and interprets where the data resides and how the SevOne system should properly import the values the device provides. The SevOne team performs this as a collaborative process with you by studying the MIBs and the walk file to determine how to properly interpret the values the device returns when SevOne performs a snmpget for the OIDs you request.

SevOne then assembles the OIDs and related metadata into a SevOne proprietary definition file, (.s1o) that contains the SevOne certified object and indicator definitions for the device.

Step 3: SevOne Delivers Device Certification

SevOne imports the .s1o file into your SevOne NMS master configuration database. After the import, the SevOne NMS must rediscover the device. After the discovery completes and the device polls for three polling cycles (to get enough data to graph), SevOne or the customer should then run an Instant Graphs report on the new objects to verify that the definitions are correct.