RSS
 

VMware Smart Assurance | 01 JUL 2021

Check for additions and updates to these release notes.

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     | May 2022    | First release of the document. Lists 04 simple certifications.
# 2.0     | June 2022   | Second release of the document. Lists 04 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.7.1
# 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     306617      .1.3.6.1.4.1.3375.2.1.3.4.117                    F5           bigipi15800
#    2     306710      .1.3.6.1.4.1.41916.3.2.81                        VIPTELA      ISR1100-4G 
#    3     306653      .1.3.6.1.4.1.9.1.2570                            CISCO        ciscoNCS55A2MODSES 
#    4     306657      .1.3.6.1.4.1.19041.1.1.2                         APPNETA      MONITORING-POINT 
#    5     306709      .1.3.6.1.4.1.41916.3.2.80                        VIPTELA       vEdge-100M
#    6     306718      .1.3.6.1.4.1.25053.3.1.10                        RUCKUS        ruckusWirelessSmartCellGatewayProducts
#    7     306651      .1.3.6.1.4.1.9.1.2661                            CISCO         ciscoIR1101K9
#    8     306728      .1.3.6.1.4.1.12356.101.1.441                     FORTINET      FGT40F 
#
#New certifications available in the 1.0 version released in May 2022
#New certifications available in the 2.0 version released in June 2022
##

#F5 Networks bigipi15800 LoadBalancer
.1.3.6.1.4.1.3375.2.1.3.4.117 { 
    TYPE            = LoadBalancer 
    VENDOR          = F5Networks 
    MODEL           = bigipi15800
    CERTIFICATION   = CERTIFIED 
    CONT            = F5-BIGIP-Select 
    HEALTH          = F5-LoadBalancer 
    HOSTRESRCS      = F5-MIB2 
    VLAN            = F5-Vlan
    NEIGHBOR        = LLDP

INSTRUMENTATION: 
    Environment             = F5LBEnvMon:DeviceID 
    CPU/Memory              = F5Rsc 
    Disk-Fault              = HostResources:DeviceID 
    FileSystem-Performance  = HostResources:DeviceID 
    Interface-Fault         = MIB2 
    Interface-Performance   = MIB2 
    Port-Fault              = MIB2:PortKey
    Port-Performance        = MIB2:PortKey
}

#Viptela ISR1100-4G Router
.1.3.6.1.4.1.41916.3.2.81 {
    TYPE            = Router
    VENDOR          = Viptela
    MODEL           = ISR1100-4G
    CERTIFICATION   = CERTIFIED
    CONT            = Viptela-Vedge-Selector
    HEALTH          = Viptela
    HOSTRESRCS      = Viptela
    VRRP            = VIPTELA-DATA
    NEIGHBOR        = LLDP

INSTRUMENTATION:
    Environment            = Viptela:DeviceID
    CPU/Memory             = Viptela_Vedge:DeviceID
    Card-Fault             = Viptela
    Disk-Fault             = Viptela:DeviceID
    VRRP-Fault             = Viptela
    FileSystem-Performance = Viptela:DeviceID
    Interface-Fault        = MIB2
    Interface-Performance  = MIB2:InterfaceKey
}

#Cisco NCS 55A2-MOD-SE-S
.1.3.6.1.4.1.9.1.2570 {
    TYPE 	    = Router
    VENDOR 	    = Cisco
    MODEL 	    = ciscoNCS55A2MODSES
    CERTIFICATION   = CERTIFIED
    CONT 	    = Cisco-Entity
    HEALTH 	    = Cisco-ASR9k-EntSensor
    NEIGHBOR 	    = LLDP-CDP

INSTRUMENTATION:
    Environment                     = CiscoEntityFRU:DeviceID
    CPU/Memory                      = CiscoRouter:DeviceID
    Card-Fault                      = CiscoEntityFRU
    Interface-Fault                 = MIB2
    Interface-Performance           = CiscoRouter
    Interface-Ethernet-Performance  = CiscoRouter_Ethernet
}

#Apparent Networks MONITORING-POINT
.1.3.6.1.4.1.19041.1.1.2 {
    TYPE            = Hub
    VENDOR          = AppNeta
    MODEL           = MONITORING-POINT
    CERTIFICATION   = CERTIFIED
    CONT 	    = Generic-MIB2
    HOSTRESRCS 	    = UCD-Sensor
    NEIGHBOR 	    = LLDP

INSTRUMENTATION:
   Disk-Fault 		  = HostResources:DeviceID
   FileSystem-Performance = HostResources:DeviceID
   Environment	          = UCD_Sensor:DeviceID
   CPU/Memory 		  = HostResources:DeviceID
   Interface-Fault 	  = MIB2
   Interface-Performance  = MIB2
}

#Viptela vEdge-100M Router
.1.3.6.1.4.1.41916.3.2.80 {
    TYPE          = Router
    VENDOR        = Viptela
    MODEL         = vEdge-100M
    CERTIFICATION = CERTIFIED
    CONT          = Viptela-Vedge-Selector
    HEALTH        = Viptela
    HOSTRESRCS    = Viptela
    VRRP          = VIPTELA-DATA
    NEIGHBOR      = LLDP

INSTRUMENTATION:
    Environment            = Viptela:DeviceID
    CPU/Memory             = Viptela_Vedge:DeviceID
    Card-Fault             = Viptela
    Disk-Fault             = Viptela:DeviceID
    VRRP-Fault             = Viptela
    FileSystem-Performance = Viptela:DeviceID
    Interface-Fault        = MIB2
    Interface-Performance  = MIB2:InterfaceKey
}

#Ruckus	ruckusWirelessSmartCellGatewayProducts
.1.3.6.1.4.1.25053.3.1.10 {
    TYPE 			= WirelessController
    VENDOR 			= Ruckus
    MODEL 			= ruckusWirelessSmartCellGatewayProducts
    CERTIFICATION 	        = CERTIFIED
    CONT 			= Generic-MIB2
    HOSTRESRCS 		        = MIB2
    NEIGHBOR 		        = LLDP
	
INSTRUMENTATION:
    CPU/Memory 			= HostResources:DeviceID
    Disk-Fault			= HostResources:DeviceID
    FileSystem-Performance 	= HostResources:DeviceID
    Interface-Fault 		= MIB2
    Interface-Performance 	= MIB2
}

#Cisco ciscoIR1101K9 Switch
.1.3.6.1.4.1.9.1.2661 {
    TYPE                          = Switch
    VENDOR                        = Cisco
    MODEL                         = ciscoIR1101K9              
    CERTIFICATION                 = CERTIFIED
    CONT                          = Cisco-L3Switch
    HEALTH                        = Cisco-Router-CRS-EntSensor
    VLAN                          = Cisco-Membership
    NEIGHBOR                      = LLDP-CDP
      
INSTRUMENTATION:
    Card-Fault                              = CiscoEntityFRU
    Environment                             = CiscoEntityFRU:DeviceID
    CPU/Memory                              = CiscoRouter:DeviceID
    Interface-Fault                         = MIB2
    Interface-Performance                   = CiscoRouter
    Interface-Ethernet-Performance          = CiscoRouter_Ethernet
    Port-Fault                              = MIB2
    Port-Performance                        = MIB2
    Port-Ethernet-Performance               = dot3_Ethernet
}

#Fortinet Firewall FortiGate-40F
.1.3.6.1.4.1.12356.101.1.441 { 
        TYPE 				= Firewall 
	VENDOR 				= Fortinet 
	MODEL 				= FGT40F
	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
}

check-circle-line exclamation-circle-line close-line
Scroll to top icon