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 new devices within 10 days from the day the filing of a support case with the necessary device information.
The standard SevOne support agreement includes the ability for customers to request SevOne assistance with the certification of new devices, such as network devices and servers, for inclusion in their SevOne SNMP certified device library. This is a no-charge event that provides a fast and effective way to ensure users of the SevOne Data Platform have the most complete visibility of your network and related devices.
SNMP 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, Juniper)
Device Role (e.g., Router, Switch, Server)
The name and IP address of the device as it was added into SevOne Data Appliance - NMS
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 certification 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 SNMP 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, and builds a device certification file for you.
Step 3: SevOne Delivers Device Certification
At this point, users import the device certification file into their SevOne Data Appliance - NMS master configuration database. After the import, you may need to associate any new object types to their device types. The SevOne Data Appliance - NMS must then rediscover the device. After the discovery completes and the device polls for three polling cycles (to get enough data to graph), users typically run an instant graphs report on the new objects to verify that the definitions are correct.