About VMware Smart Assurance IP Manager Certification
Certification is a process by which VMware Inc. ensures that the devices that are managed by the IP Manager are properly represented in the modeled topology, and that the devices are correctly monitored for connectivity and performance analysis. Devices are specific models of systems.
The certification process consists of three major parts:
-
Discovery of the device, including the device’s components (such as cards, ports) and endpoints (such as IP addresses, MAC addresses).
-
Building of Layer 2 (data link) and Layer 3 (network) connectivity.
-
Verification of operational status of the device and its components.
The VMware Smart Assurance IP Manager Certification Matrix available at VMware Online Support (https://docs.vmware.com) identifies the vendor-specific models that are supported by the IP Manager.
Certification Levels
A device may have one of three certification levels:
-
CERTIFIED: VMware has successfully tested a simulation of the device by using standard and proprietary MIBs that are supplied by the vendor. The IP Manager discovers the device by using standard MIB-II data and proprietary MIBs.
-
TEMPLATE: VMware Inc. that the device supports some standard and proprietary MIBs, but Dell has not tested the device. The IP Manager recognizes the object ID (OID), but has no information about the MIBs that this device supports.
-
GENERIC: VMware Inc. does not have the OID for the device. The IP Manager does not recognize the OID and responds by classifying the certification level of the device as GENERIC, adding the device to the Node class, and analyzing the device by using MIB-II data.
Note: A certification level named VALIDATED still appears in the oid2type configuration files but is no longer used. VALIDATED has essentially the same meaning as CERTIFIED.
#############################################################################################################################
##
# VERSION HISTORY
#
# Version | Published Date | Description
# 1.0 | November 2021 | First release of the document. Lists 09 simple certifications.
#
#
# INSTRUCTIONS
#
# 1. Find the System Object ID (SysOID) of the device you intend to
# certify in the list of certified devices.
# 2. Copy the device certification code starting from the
# device SysOID till the next SysOID (including the braces).
# 3. Open the oid2type_Field.conf file using sm_edit and paste the
# contents at the end of the file. Then save and close the file.
# 4. If the SysOID is already certified and you are looking to apply an
# updated certification, use sm_edit to remove the old certification from the
# oid2type_/oid2type_misc/oid2type_Field.conf file.
# 5. To load new certifications into a domain, run the following command:
# /smarts/bin/sm_tpmgr -s --reloadoid
# 6. Check IP domain log file for errors.
# 7. You can also see the exact certification used for a device in a running server by executing
# /smarts/bin/dmctl -s get ICF_TopologyManager::ICF-TopologyManager| grep
#
# 8. The certifications in this file will be included in the next GA release.
# If you install a new GA release (hotfix patch, service pack, minor, or major release),
# remove the redundant or duplicate entry from the oid2type_Field.conf file.
#
# The conf files are located in:
# /smarts/conf/discovery and in the
# /smarts/local/conf/discovery directory.
# Use /smarts/bin/sm_edit to ensure that all modifications are
# stored under local and read in by the domain.
#
##
# The following simple certifications are supported on IP versions: IP 10.1.5.4
# Purpose: This file contains the list of certification code entries that
# can be added to the existing oid2type_Field.conf file to enable
# discovery and monitoring of the device.
##
##
#
# SL No TASC SYSOID VENDOR MODEL
#
# 1 306516 .1.3.6.1.4.1.12356.101.1.80008 FORTINET FortiGate-VM64-KVM
# 2 306555 .1.3.6.1.4.1.9.1.1411 CISCO ciscoASA5512sc
# 3 306518 .1.3.6.1.4.1.12356.101.1.18000 FORTINET FortiGate-2200E
# 4 306535 .1.3.6.1.4.1.207.1.4.87 ALLIEDTELESIS at-8088-SC
# 5 306547 .1.3.6.1.4.1.9.1.2759 CISCO ciscoC11278PLteP
# 6 306559 .1.3.6.1.4.1.12356.101.1.845 FORTINET FortiGate 80F
# 7 306481 .1.3.6.1.4.1.12356.101.1.10006 FORTINET FortiGate-1100E
# 8 306557 .1.3.6.1.4.1.12356.109.1.10030 FORTINET FortiProxyVM64
# 9 306513 .1.3.6.1.4.1.12356.101.1.34001 FORTINET FortiGate-3400E
#
#
#New certifications available in the 1.0 version released in November 2021
##
#Fortinet FortiGate-VM64-KVM
.1.3.6.1.4.1.12356.101.1.80008 {
TYPE = Firewall
VENDOR = Fortinet
MODEL = FortiGate-VM64-KVM
CERTIFICATION = CERTIFIED
CONT = Fortinet
HEALTH = Fortigate-Health
NEIGHBOR = LLDP
INSTRUMENTATION:
Disk-Fault = Fortigate:DeviceID
Environment = Fortinet_Fortigate:DeviceID
CPU/Memory = Fortigate:DeviceID
Interface-Fault = MIB2
Interface-Performance = MIB2
}
#Cisco Adaptive Security Appliance
.1.3.6.1.4.1.9.1.1411 {
TYPE = Firewall
VENDOR = Cisco
MODEL = ciscoASA5512sc
CERTIFICATION = CERTIFIED
CONT = Cisco-Router
HEALTH = Cisco-Router
NEIGHBOR = LLDP-CDP
INSTRUMENTATION:
CPU/Memory = CiscoRouter:DeviceID
Interface-Fault = MIB2
Interface-Performance = CiscoRouter
Interface-Ethernet-Performance = CiscoRouter_Ethernet
}
#Fortinet FortiGate-2200E
.1.3.6.1.4.1.12356.101.1.18000 {
TYPE = Firewall
VENDOR = Fortinet
MODEL = FortiGate-2200E
CERTIFICATION = CERTIFIED
CONT = Fortinet
HEALTH = Fortigate-Health
NEIGHBOR = LLDP
INSTRUMENTATION:
Disk-Fault = Fortigate:DeviceID
Environment = Fortinet_Fortigate:DeviceID
CPU/Memory = Fortigate:DeviceID
Interface-Fault = MIB2
Interface-Performance = MIB2
}
#Allied Telesis at-8088-SC Switch
.1.3.6.1.4.1.207.1.4.87 {
TYPE = Switch
VENDOR = AlliedTelesis
MODEL = at-8088-SC
CERTIFICATION = CERTIFIED
CONT = Generic-Bridge
HEALTH = Allied-Telesyn-health
VLAN = Allied-Tel
INSTRUMENTATION:
CPU/Memory = AlliedTelesyn:DeviceID
Environment = AlliedTelesynEnvMon:DeviceID
Interface-Fault = MIB2
Interface-Performance = MIB2
Port-Fault = MIB2
Port-Performance = MIB2
Port-Ethernet-Performance = dot3_Ethernet
}
#Cisco ciscoC11278PLteP Router
.1.3.6.1.4.1.9.1.2759 {
TYPE = Router
VENDOR = Cisco
MODEL = ciscoC11278PLteP
CERTIFICATION = CERTIFIED
CONT = Cisco-L3Switch
HEALTH = Cisco-Router-ASR-EntSensor
VLAN = Cisco-Membership
NEIGHBOR = LLDP-CDP
INSTRUMENTATION:
Environment = CiscoEntityFRU:DeviceID
CPU/Memory = CiscoRouter:DeviceID
Card-Fault = CiscoEntityFRU:DeviceID
Interface-Fault = MIB2
Interface-Performance = CiscoRouter
Interface-Ethernet-Performance = CiscoRouter_Ethernet
Port-Fault = MIB2
Port-Performance = MIB2
Port-Ethernet-Performance = dot3_Ethernet
}
#Fortinet FortiGate 80F Firewall
.1.3.6.1.4.1.12356.101.1.845 {
TYPE = Firewall
VENDOR = Fortinet
MODEL = FortiGate 80F
CERTIFICATION = CERTIFIED
CONT = Fortinet
HEALTH = Fortigate-Health
NEIGHBOR = LLDP
INSTRUMENTATION:
Environment = Fortinet_Fortigate:DeviceID
Disk-Fault = Fortigate:DeviceID
CPU/Memory = Fortigate:DeviceID
Interface-Fault = MIB2
Interface-Performance = MIB2
}
#Fortinet FG-1100E
.1.3.6.1.4.1.12356.101.1.10006 {
TYPE = Firewall
VENDOR = Fortinet
MODEL = FortiGate-1100E
CERTIFICATION = CERTIFIED
CONT = Fortinet
HEALTH = Fortigate-Health
NEIGHBOR = LLDP
INSTRUMENTATION:
Disk-Fault = Fortigate:DeviceID
Environment = Fortinet_Fortigate:DeviceID
CPU/Memory = Fortigate:DeviceID
Interface-Fault = MIB2
Interface-Performance = MIB2
}
#Fortinet FortiProxyVM64 Firewall
.1.3.6.1.4.1.12356.109.1.10030 {
TYPE = Firewall
VENDOR = Fortinet
MODEL = FortiProxyVM64
CERTIFICATION = CERTIFIED
CONT = Fortinet
HEALTH = Fortigate-Health
NEIGHBOR = LLDP
INSTRUMENTATION:
Environment = Fortinet_Fortigate:DeviceID
Disk-Fault = Fortigate:DeviceID
CPU/Memory = Fortigate:DeviceID
Interface-Fault = MIB2
Interface-Performance = MIB2
}
#Fortinet FG-3400E
.1.3.6.1.4.1.12356.101.1.34001 {
TYPE = Firewall
VENDOR = Fortinet
MODEL = FortiGate-3400E
CERTIFICATION = CERTIFIED
CONT = Fortinet
HEALTH = Fortigate-Health
NEIGHBOR = LLDP
INSTRUMENTATION:
Disk-Fault = Fortigate:DeviceID
Environment = Fortinet_Fortigate:DeviceID
CPU/Memory = Fortigate:DeviceID
Interface-Fault = MIB2
Interface-Performance = MIB2
}
