Device entry field descriptions in oid2type_Field.conf describes the device entry fields for a field-based certification.
| Field |
Description |
|---|---|
| TYPE |
Type of device. This value can be any unitary computer system class. This field is mandatory. |
| VENDOR |
Manufacturer of the device. This value must be a single word. This field is mandatory. |
| MODEL |
Model name of the device. The field name, MODEL, is required. The value of MODEL is optional, and can be more than one word. |
| CERTIFICATION |
Level of certification for the device. The value should always be CERTIFIED which means that the system is recognized by the IP Manager, but there is no knowledge about support for various MIBS used in the discovery process. |
| Discovery driver keywords |
|
| ADNR |
Parameter name of the autodiscovery name resolution driver that is to be used by the IP Manager to discover interface and IP (v4 and v6) address information for the device, for the purpose of determining if the device is a “match” to another device. The driver gathers the information from MIB-II-like tables in vendor-specific MIBs on the device. The full name of the autodiscovery name resolution driver is AD-MIB2-Data-<param-name>-Driver. Examples: AD-MIB2-Data-Unisphere-Access-Driver, AD-MIB2-Data-Tellabs-Access-Driver |
| DSCVDATA |
Parameter name of the discovery data driver that is to be used by the IP Manager, in conjunction with the ADNR driver, to discover interface and IP (v4 and v6) address information for the device, for the purpose of determining if the device is a “match” to another device. The driver gathers the information from MIB-II-like tables in vendor-specific MIBs on the device. The full name of the discovery data driver is MIB2-Data-<param-name>-Driver. Examples: MIB2-Data-ERX-VR-Cont-Driver, MIB2-Data-Tellabs-Access-Driver |
| BRIDGE |
Applicable to bridge or switch device only:Parameter name of the Bridge driver that is to be used by the IP Manager to collect bridge-forwarding tables and STP information for the bridge or switch device. The full name of the Bridge driver is Bridge-<param-name>-Driver. Examples: Bridge-Bay-C100-Driver, Bridge-Tut-MXL2300-BRIDGE-Driver |
| CONT |
Parameter name of the Containment driver that is to be used by the IP Manager to discover the components of the device, including ports, interfaces, MAC endpoints, and any cards or modules. The full name of the Containment driver is Containment-<param-name>-Driver. Examples: Containment-Generic-MIB2-Driver, Containment-Cisco-Router-Driver |
| HEALTH |
Parameter name of the Performance driver that is to be used by the IP Manager to collect performance-related information for the device’s components such as ports, interfaces, processors, memory, fans, power supplies, voltage sensors, and temperature sensors. The full name of the Performance driver is Performance-<param-name>-Driver. Examples: Performance-Max-TNT-Driver, Performance-AvayaVPNet-Driver |
| HOSTRESRCS |
Applicable to host device only:Parameter name of the Host Resources driver that is to be used by the IP Manager to collect additional performance-related information for the host device’s components. The Host Resources driver collects metrics about host disks and file systems as well as additional information about host processors and memory. The full name of the Host Resources driver is HostResrcs-<param-name>-Driver. Examples: HostResrcs-MIB2-Driver, HostResrcs-HP-Driver |
| IPNETWORK |
Parameter name of the IP Network driver that is to be used by the IP Manager to examine the device’s IP address table, to combine the IP (v4 and v6) addresses and the netmask for each interface on the device to create IPNetwork and IPv6Network objects, and to build the connected relationships between IP endpoints and IP networks and between IPv6 endpoints and IPv6 networks. The full name of the IP Network driver is IPNetwork-<param-name>-Driver. Examples: IPNetwork-Access-Driver, IPNetwork-3Com-CB9000L2-Driver |
| NEIGHBOR |
Parameter name of the Neighbor driver that is to be used by the IP Manager to collect information about the device’s neighbors by reading CDP, EDP, FDP, and other tables to discover remote addresses on the already discovered networks, and to discover ATM information. The full name of the Neighbor driver is Neighbor-<param-name>-Driver. Examples: Neighbor-ATM-Peer-Driver, Neighbor-Foundry-Fdp-Driver |
| RESOLVER |
Parameter name of the Name Resolution driver that is to be used by the IP Manager to discover the IP (v4 and v6) addresses that are available for the device, and to provide a unique name for the device. The full name of the Name Resolution driver is Name-Resolver-<param-name>-Driver. Examples: Name-Resolver-Access-Driver, Name-Resolver-OnlyData-Driver |
| VLAN |
Applicable to bridge or switch device only:Parameter name of the VLAN driver that is to be used by the IP Manager to collect VLAN information for the bridge or switch device, including VLAN identifiers, VLAN trunks, VLAN trunk ports, and VLAN port memberships. The full name of the VLAN driver is Vlan-<param-name>-Driver. Examples: Vlan-ERX-Driver, Vlan-Cisco-Membership-Driver |
| VROUTER |
Applicable to router or switch device only:Parameter name of the Virtual Router driver that is to be used by the IP Manager to discover the virtual routers in the IPv4 physical router or switch device that contains virtual routers. The full name of the Virtual Router driver is VRouter-<param-name>-Driver. Examples: VRouter-ERX-Driver, VRouter-Cosine-Orion-Driver |
| VRRP |
Applicable to router only:Parameter name of the VRRP driver that is to be used by the IP Manager to collect information from the router device about the redundancy group of routers that are involved in a VRRP group. The full name of the VRRP driver is VRRPGroup-<param-name>-Driver. Example: VRRPGroup-Unisphere-ERX-Driver |
| INSTRUMENTATION: |
Introduces the instrumentation portion of a device entry. |
| Instrumentation keywords |
|
| CPU/Memory |
Name of the instrumentation set that is to be used by the IP Manager to monitor the performance of the device’s CPU and memory. Examples: HostResources:DeviceID, CiscoSwitch:DeviceID, BluecoatRsc:DeviceID |
| Card-Fault |
Name of the instrumentation set that is to be used by the IP Manager to monitor the status of the device’s cards. Examples: Default, CiscoStack, AlcatelTimex |
| Disk-Fault |
Name of the instrumentation set that is to be used by the IP Manager to monitor the status of the device’s disks. Examples: HostResources:DeviceID, BluecoatRsc:DeviceID |
| Chassis-Performance |
Name of the instrumentation set that is to be used by the IP Manager to monitor the performance of the device’s chassis. Example: = CiscoStack |
| FileSystem-Performance |
Name of the instrumentation set that is to be used by the IP Manager to monitor the performance of the device’s file systems. Examples: HostResources:DeviceID, HostResources_HP:DeviceID |
| Environment |
Name of the instrumentation set that is to be used by the IP Manager to monitor the device’s fans, memory, power supplies, temperature sensors, and voltage sensors. Examples: = CiscoStack, MrvEnvMon:DeviceID, DellEnvMon3248OID3:DeviceID |
| Interface-Fault |
Name of the instrumentation set that is to be used by the IP Manager to monitor the status of the device’s interfaces. Examples: MIB2, WellfleetRouter MIB2 means that the IP Manager polls ifAdminStatus and ifOperStatus for interface status. |
| Interface-Performance |
Name of the instrumentation set that is to be used by the IP Manager to monitor the performance of the device’s interfaces. Examples: MIB2, MIB2SNMP, CiscoRouter MIB2 means that the IP Manager polls ifInOctets, ifOutOctets, and other counters in the ifTable to report interface utilization and other statistics. |
| Interface-Ethernet-Performance |
Name of the instrumentation set that is to be used by the IP Manager to monitor the performance of the device’s Ethernet interfaces. Examples: MIB2, CiscoRouter_Ethernet |
| Port-Fault |
Name of the instrumentation set that is to be used by the IP Manager to monitor the status of the device’s ports. Examples: MIB2, AlcatelTimex:DeviceID, Brocade:PortKey |
| Port-Performance |
Name of the instrumentation set that is to be used by the IP Manager to monitor the performance of the device’s ports. This value is always MIB2. |
| Port-Ethernet-Performance |
Name of the instrumentation set that is to be used by the IP Manager to monitor the performance of the device’s Ethernet ports. Examples: MIB2, dot3_Ethernet |
