Override Device Types

Based on the device service information, the Data Aggregator automatically classifies manageable devices. Classifications include Router, Switch, Server, Firewall, Load Balancer, Wireless Controller, and Wireless Access Point. During synchronization, the Data Aggregator inspects each device and its classification. The Data Aggregator designates a primary device type, and forwards any additional types as context types. The associated context types, including the primary device types, appear listed in a column within the device inventory tables in npc.
capm350
Based on the device service information, the Data Aggregator automatically classifies manageable devices. Classifications include Router, Switch, Server, Firewall, Load Balancer, Wireless Controller, and Wireless Access Point. During synchronization, the Data Aggregator inspects each device and its classification. The Data Aggregator designates a primary device type, and forwards any additional types as context types. The associated context types, including the primary device types, appear listed in a column within the device inventory tables in
NetOps Portal
.
The following list describes more device type classifications:
  • Pingable
    The device is not manageable.
    Example:
    The device does not respond to SNMP requests and its device type cannot be determined.
  • Manageable
    The device type is classified as 'Manageable' when the following criteria are true:
    • The manageable device cannot be classified as Router, Switch, or Server.
    • The manageable device
      can
      be classified as Firewall, Load Balancer, Wireless Controller, or Wireless Access Point.
  • Other
    The device type is classified as 'Other' when the following criteria are true:
    • The manageable device cannot be classified as Router, Switch, or Server.
    • The manageable device cannot be classified as Firewall, Load Balancer, Wireless Controller, or Wireless Access Point.
Override Device Types
If the device types of some SNMP manageable devices were not classified as expected, you can fully override the device types.
Scenarios:
  • An existing device is discovered as 'Other'. However, you want the device to be classified as 'Router' instead. To override the existing 'Other' classification, you can add 'Router' to the DeviceTypes.xml.
  • An existing device is discovered as 'Switch'. The SNMP agent advertised the wrong type. The device should have been advertised as 'Router' and it is also a 'Firewall'. To override the incorrectly discovered types, you can add 'Router' and 'Firewall' to the DeviceTypes.xml.
Map the device
sysObjectID
MIB value explicitly to the correct device type in the following file on the Data Aggregator host:
DA_install_directory
/data/custom/devicetypes/DeviceTypes.xml
In a fault tolerant environment, a shared directory (example:
/DASharedRepo
) is defined to help limit data loss. Therefore, in a fault tolerant environment the file would be located in the following directory:
DASharedRepo
/custom/devicetypes/DeviceTypes.xml
For more information, see Fault Tolerance.
You cannot add new device types to the DeviceTypes.xml file.
The DeviceTypes.xml file contains a template to map the
sysObjectID
to appropriate device types. By default, the file does not contain any
sysObjectID
-to-type mapping entry. To classify a device type with a particular
sysObjectID
, modify the template to add the
sysObjectID
-to-type entries into the file. Before you add a
sysObjectID
, uncomment the section where you are adding the
sysObjectID
.
Updates to the DeviceTypes.xml file can take up to one minute to apply.
A device can be classified into multiple device types. However, the type, Device, is mutually exclusive to other device types. For example, if you add a
sysObjectID
to one or more of the Router, Switch, or Server device types and you also add that
sysObjectID
to the 'Device' device type, the 'Device' device type is dropped and is not recognized.
Fully override the device types when the following criteria are true:
  • No automatically discovered device types were found or the discovered device types are wrong.
  • You want to override the types discovered during device discovery.
  • You want to assign the correct types manually.
Example: Map a Device sysObjectID to Another Device Type
The
sysObjectID
-to-type mappings in the following example override any already discovered device types.
Follow these steps:
  1. Open the following file:
    DA_install_directory
    /data/custom/devicetypes/DeviceTypes.xml
    In a fault tolerant environment, the file would be located in the following directory:
    DASharedRepo
    /custom/devicetypes/DeviceTypes.xml
  2. Enter the following information:
    <DeviceType>
    <Routers>
    <sysObjectID>1.3.6.5.1.34</sysObjectID>
    </Routers>
    <Switches>
    <sysObjectID>1.3.6.5.5.3</sysObjectID>
    <sysObjectID>1.3.6.5.1.34</sysObjectID>
    </Switches>
    <Servers>
    <sysObjectID>1.3.6.5.567.1</sysObjectID>
    </Servers>
    <Devices>
    <sysObjectID>1.3.6.5.49.1</sysObjectID>
    </Devices>
    </DeviceType>
  3. Run discovery on the discovery profile that contains the devices.
    The changes that you make to the DeviceTypes.xml file do not take effect on existing devices until you rerun discovery.
    When discovery is run, the following results occur:
    • All devices that have a
      sysObjectID
      of 1.3.6.5.1.34 are classified as a device type of Router and Switch.
    • All devices that have a
      sysObjectID
      of 1.3.6.5.5.3 are classified as a device type of Switch.
    • All devices that have a
      sysObjectID
      of 1.3.6.5.567.1 are classified as a device type of Server.
    • All devices that have a
      sysObjectID
      of 1.3.6.5.49.1 are classified as a device type of Device.
  4. To verify your changes, go to the following locations:
    • Hover over
      Administration
      , and click
      Monitored Items Management: Device Life Cycle
      .
    • Hover over
      Inventory
      , and click
      Devices
      .
Preserve Device Types
Sometimes, a device might have an incomplete classification. For example, a device that is discovered as a Router may be a Firewall too. In this case, you want to preserve the discovered Router classification. You also want to augment the classification with one or more manually assigned device types (in this example, Firewall).
Scenarios:
  • An existing device is discovered automatically as a 'Server'. You want the device to be classified as a 'Firewall' too. To preserve the discovered 'Server' classification, add 'Firewall' to the DeviceTypes.xml with the
    sysServiceOverride
    tag attribute set to 'false'.
  • An existing device is discovered automatically as a 'Router'. You want the device to be classified as a 'Firewall' and 'Switch' too. To preserve the existing 'Router' classification, add 'Firewall' and 'Switch' to the DeviceTypes.xml with
    ysServiceOverride
    tag attribute set to 'false'.
The
sysServiceOverride
tag attribute provides a way to disable the default override behavior. You can assign a
sysObjectID
to one or more device types in the DeviceTypes.xml (for example, Firewall) in addition to the types that the system automatically discovers (for example, Router). To preserve the device types, use the
sysServiceOverride
tag attribute and set it to 'false' for the
sysObjectIDs
or device types.
Use the
sysServicesOverride
tag attribute when the following criteria are true:
  • You want to preserve the type that is discovered during device discovery.
  • You accept the automatically discovered device type as correct and do not want to lose it.
  • You want to add more types.
Example: Preserve the device types already mapped to the sysObjectIDs
Follow these steps:
  1. Open the following file:
    DA_install_directory
    /data/custom/devicetypes/DeviceTypes.xml
    In a fault tolerant environment, the file would be located in the following directory:
    DASharedRepo
    /custom/devicetypes/DeviceTypes.xml
  2. Enter the following information:
    <DeviceType>
    <Routers>
    <sysObjectID
    sysServicesOverride="false"
    >1.3.6.5.1.34</sysObjectID>
    </Routers>
    <Firewalls>
    <sysObjectID
    sysServicesOverride="false"
    >1.3.6.1.4.1.8072.3.2.10</sysObjectID>
    </Firewalls>
    <Firewalls
    sysServicesOverride="false"
    >
    <sysObjectID>1.3.6.1.4.1.9.1.522</sysObjectID> <!-- cat6500FirewallSm -->
    <sysObjectID>1.3.6.1.4.1.2620.1.6.123.1.56</sysObjectID> <!-- Check Point 21800 -->
    <sysObjectID>1.3.6.1.4.1.2620.1.6.123.1.16</sysObjectID> <!-- Smart-1 150 -->
    </Firewalls>
    <WirelessAccessPoints>
    <sysObjectID>1.3.6.1.4.1.2620.1.6.123.1.48</sysObjectID>
    </WirelessAccessPoints>
    <WirelessControllers>
    <sysObjectID>1.3.6.1.4.1.9.1.770</sysObjectID>
    </WirelessControllers>
    <LoadBalancers>
    <sysObjectID>1.3.6.1.4.1.6527.1.6.1</sysObjectID>
    </LoadBalancers>
    </DeviceType>
  3. Run discovery on the discovery profile that contains the devices.
    The changes that you make to the DeviceTypes.xml file do not take effect on existing devices until you rerun discovery.
    When discovery is run, the following results occur:
    • All devices that have a
      sysObjectID
      of 1.3.6.5.1.34 are classified as a device type of Router. The device types that are already mapped to the
      sysObjectID
      are preserved.
    • All devices that have a
      sysObjectID
      of 1.3.6.1.4.1.8072.3.2.10 are classified as a context type of Firewall. The device types that are already mapped to the
      sysObjectID
      are preserved.
    • All devices that have a
      sysObjectID
      of 1.3.6.1.4.1.9.1.522 are classified as a context type of Firewall. The device types that are already mapped to the
      sysObjectID
      are preserved.
    • All devices that have a
      sysObjectID
      of 1.3.6.1.4.1.2620.1.6.123.1.56 are classified as a context type of Firewall. The device types that are already mapped to the
      sysObjectID
      are preserved.
    • All devices that have a
      sysObjectID
      of 1.3.6.1.4.1.2620.1.6.123.1.16 are classified as a context type of Firewall. The device types that are already mapped to the
      sysObjectID
      are preserved.
    • All devices that have a
      sysObjectID
      of 1.3.6.1.4.1.2620.1.6.123.1.48 are classified as a context type of Wireless Access Point. The device types that are already mapped to the
      sysObjectID
      are preserved.
    • All devices that have a
      sysObjectID
      of 1.3.6.1.4.1.9.1.770 are classified as a context type of Wireless Controller. The device types that are already mapped to the
      sysObjectID
      are preserved.
    • All devices that have a
      sysObjectID
      of 1.3.6.1.4.1.6527.1.6.1 are classified as a context type of Load Balancer. The device types that are already mapped to the
      sysObjectID
      are preserved.
  4. To verify your changes, go to the following locations:
    • Hover over
      Administration
      , and click
      Monitored Items Management: Device Life Cycle
      .
    • Hover over
      Inventory
      , and click
      Devices
      .