White Paper

May 2000 175758-001 Prepared by: Industry Standard Server Division Compaq Computer Corporation

Compaq Insight Manager XE Device Type Manager Utility

Abstract: Device Type Manager (DTM) is a utility included with Compaq Insight Manager XE V2.0. DTM enables third party partners to add information to the identification database. The new information enables administrators to create new product categories for more precise or customized identification.

Contents
Extending Identification..............3 Why Extend Your Management Capability? ...........3 Identification Basics in Device Type Manager................3 The Rule Set..............................5 Before You Begin.......................7 When Can Identification Be Modified? ...................................8 Using Device Type Manager.......8 Using the Graphical Interface ....8 Creating New Device Categories .................................9 Editing Device Categories .......16 Deleting Device Categories .....17 Using the Command Line Utility ..........................................18 Working Examples using the DTM Command Line................22 Seeing the Results of Adding an SNMP Rule Set...................23 Using the Edit Command to Modify an Existing SNMP Rule Set...................................26 Using the Delete Command to Remove an SNMP Rule Set ...........................................27 Using the Add Command to Add a DMI Rule Set .................28 Appendix A: Compaq Insight Manager XE Identification ........30 Discovery.................................30 Transient Identification States ......................................30 SNMP and DMI Precedence....30 SNMP Identification .................31 Third Party Rules .....................33 DMI Identification .....................34 Appendix B: Identification Flowcharts .................................36

Compaq Insight Manager XE Device Type Manager Utility

Notice
The information in this publication is subject to change without notice and is provided AS IS WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS INFORMATION REMAINS WITH RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS INFORMATION), EVEN IF COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The limited warranties for Compaq products are exclusively set forth in the documentation accompanying such products. Nothing herein should be construed as constituting a further or additional warranty. This publication does not constitute an endorsement of the product or products that were tested. The configuration or configurations tested or described may or may not be the only available solution. This test is not a determination of product quality or correctness, nor does it ensure compliance with any federal, state or local requirements. Compaq, NonStop, Deskpro, Compaq Insight Manager, Systempro, Systempro/LT, ProLiant, ROMPaq, QVision, SmartStart, NetFlex, QuickFind, PaqFax, and Prosignia are registered with the United States Patent and Trademark Office. ActiveAnswers, Netelligent, Systempro/XL, SoftPaq, Fastart, QuickBlank, QuickLock are trademarks and/or service marks of Compaq Computer Corporation. Microsoft, Windows and Windows NT are trademarks and/or registered trademarks of Microsoft Corporation. Intel, Pentium and Xeon are trademarks and/or registered trademarks of Intel Corporation. Other product names mentioned herein may be trademarks and/or registered trademarks of their respective companies.

2000 Compaq Computer Corporation. All rights reserved. Printed in the U.S.A. Compaq Insight Manager XE Device Type Manager Utility White Paper prepared by Industry Standard Server Division First Edition (May 2000) Document Number 175758-001

175758-001

Compaq Insight Manager XE Device Type Manager Utility

Extending Identification
Compaq Insight Manager XE V2.0 attempts to discover all devices on your network. After a device is discovered, it attempts to identify the device by asking each device a series of questions. The answers to the questions are compared to the expected answers stored in the Compaq Insight Manager XE database. In this way, Compaq Insight Manager XE classifies devices that it discovers. Using Compaq Insight Manager XE, Compaq products are easily and precisely identified. However, most networks contain devices from multiple vendors. With the addition of Device Type Manager, or DTM, administrators can also extend the identification capability of Compaq Insight Manager XE to third party devices.

Why Extend Your Management Capability?

You might use DTM in a number of circumstances, for example: As a partner, you have a device that you want to be identified in a specific way. Consequently, you define a unique set of criteria or rules that is only satisfied by your device or sets of devices. You assign a meaningful Product Name. As part of your product deliverables, you include a DTM command line script file that an administrator can use to quickly add the device identification rule set to the Compaq Insight Manager XE database. You have a new Compaq product that was released after you installed Compaq Insight Manager XE. Although the product can be discovered, it might not be identified as completely as you would like, or you may want to add to the description. Therefore, you can create a new rule set, give it a unique Product Name, and pick the appropriate Device Type to use until the next release of a Compaq Insight Manager XE SoftPaq that includes a corresponding DTM script file of updates. You have a device that is identified using an existing rule set. However, in your organization, you would prefer to group it logically, for example, by business application. You may simply wish to assign the identifying rule set to a different Device Type.

It is important to remember that some rule sets cannot be replaced or modified. Compaq Insight Manager XE will always recognize Compaq devices in the same way when using SNMP. You have complete flexibility however, when using DMI, as Compaq identification is applied only when there is no identification based on third party DMI rule sets. See Appendix A and Appendix B for descriptions of the identification process.

Identification Basics in Device Type Manager

DTM provides a mechanism for adding new identification rules for previously discovered but unidentified devices and for changing the way discovered devices are grouped. The mechanism used is the rule set. A rule set is a set of questions and corresponding answers, which if replied to correctly, label the device with a particular product name and an associated device type. The rule set information is stored in the database. Each rule set must be unique because identification is a deterministic process. If the device answers all the questions of a given rule set correctly, the device is included in the list of all devices that satisfy that rule set and assumes that rule set Product Name. The device may satisfy more than one rule set.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

Rule sets are prioritized such that if a device does match more than one rule set, the rule set with the highest priority wins. Compaq Insight Manager XE includes the following device types: Cluster Desktop Portable Printer Server Unknown. Workstation Repeater Router Management Processor Other Remote Access Device Switch

Device types are static and cannot be changed or added to in Compaq Insight Manager XE. The Device Type of Other has been added to provide a Device Type for collecting devices that do not fit into any of the other specific Device Types. For example, the DEC Bridge 500, a network bridge, may be classified as Other. A discovered device assumes the type of Unknown and no assigned Product Name. This is changed only if the device then matches some identification rule. The Product Name is simply a logical name to refer to the rule set. The administrator can add as many rule sets as needed to identify devices discovered on the network and later modify or delete these same rules. Some rule sets such as those that identify Compaq devices using SNMP cannot be changed, nor can third party rules take precedence. With DMI, the hard coded rules can be overruled. Some devices may meet the requirements of more than one rule set. For this situation, each rule set is assigned a number or priority. When a device meets the requirements of more than one rule set, the rule set with the lowest numberwhich is also the highest prioritydetermines the device Product Name identity. Unless you specify a priority, the last rule set added has the highest priority. Note: The Compaq Insight Manager XE database is updated immediately with each DTM command. However, the device will not be identified or appear in a Query Result with the new product category until you run a discovery and identification task. HTTP Automatic Discovery does not find the new product category.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

The Rule Set

In DTM, you will create a rule set for the device category you are adding. The rule set is a series of questions or requests that are communicated to a device. The requests are made to determine device identity. The responses are evaluated. The requests and the responses are communicated using either SNMP (Simple Network Management Protocol) or DMI (Desktop Management Identification) protocol. Characteristics of any rule set: The rule set is defined using either the SNMP or DMI management protocol. You can specify up to two separate SNMP-based questions and answers and up to three separate DMI questions and answers. The request sent to a device is derived from data repositories supplied by vendors. SNMP data is derived from a MIB (Management Information Base) and DMI data is derived from a MIF (Management Information File). These data repositories are integral to the agent installed on the target devices. If a device includes both SNMP and DMI support, and is capable of replying using either SNMP or DMI, an identification is established where SNMP takes precedence. Each rule set has an assigned priority. The scope of the priority is different for SNMP and DMI. If the device satisfies more than one rule set, rule set priority is used to determine which rule set is used to identify the device. The default priority is one (1), the highest priority. As each rule is entered, it assumes a priority of one (unless otherwise specified), and all other related rule set priorities are adjusted accordingly when more than one rule set applies. The expected response value to a request is part of the rule set. However, it is possible to define a rule set where the exact value is not important. The key is that some reasonable value is returned. For example, numerous device descriptions begin with Hardware This value might be sufficient for your device category. The response can be matched to the expected value using one of the following conditions: Starts With The condition is met if either string is fully contained by the other, with the first character of both as the anchor. In the graphical interface, this condition appears as the option StartsWith in the graphical interface. Contains The rule set value is contained within the response string. The response string will not match if it is shorter than the rule set string. Matches The value of the response string is an exact match with the rule set string. If one string is longer than the other is, the compare fails. Ends With The condition is met if either string is fully contained by the other, with the last character both as the anchor. In the graphical interface, this condition appears as the option EndsWith in the graphical interface. Any ValueThe value of the returned string is irrelevant as long as a value is returned. In the graphical interface, this condition appears as the option AnyValue in the graphical interface.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

DMI Rule Sets in Device Type Manager

Each rule in a DMI rule includes the following constituents: Component Name Group Class Name Same group Class Name Attribute Name Index Value

All constituents are optional provided that at least one constituent is not NULL. The wildcard character of the asterisk (*), is an acceptable entry for a constituent. The wildcard instructs the identification process to continue searching for an expected response if a match is not found in the first MIF that is encountered. When a device is discovered, the components of each DMI element are then sent to the device in turn. The response value is then compared with the expected value in each case, as per the value compare rule required. Using the Any Value compare rule implies that any response is sufficient. When a full match is made and its priority is higher than the last full match, the device then assumes this new identity. If the priority is one, the identification process is complete. When there are multiple elements in a rule set for a DMI device, the rule elements must be entered with the most unique element as the first element across all rules in a specific rule set. In the following table, the product name Desktop 1 is identified uniquely by Element A for a given rule set. Desktop 2 is identified by Elements A and B and Desktop 3 meets the criteria of Elements A, B, and C. For Desktop 2 to be identified successfully enter Element B as the first element, and Element A as the second element. To successfully identify Desktop 3, enter Element C as the first Element, enter Element B as the second element and Element A as the last Element.
Table 1. DMI Element Order
Product Name Desktop 1 Desktop 2 Desktop 3 Correct order of Entry for Each Element A BA CBA

Prioritization
A device might satisfy the specifications of several members of an SNMP rule set family, which is identified by a system object identifier (sysOID). (Appendix A contains more information about OIDs.) For example, a machine can be running Windows NT and providing routing service functionality. One rule set can be defined that identifies this device as an NT server and another rule set might identify it as a router. Which identity is correct? To set the identity the user prefers for this discovered device, the user assigns an identification priority to all rule sets that share a common SysOID. The highest priority rule set determines the device identity. An identification priority of one (1) is highest. When a rule set matches with priority one, the process stops whether all rule sets have been checked or not. A priority of one implies that the best match has been found,

175758-001

Compaq Insight Manager XE Device Type Manager Utility

If the user adds a new rule set without specifying a priority, DTM assigns a priority of one to the new rule set and adjusts all of the other members of that family. No matter how the priority of one rule set is changed, DTM appropriately adjusts the priority of the other family members. When an arbitrary MIB variable is used, the user must supply the variable OID in the standard number-dot format (i.e. 1.2.3.1.2.1.1). When using the DTM graphical client, the user can take advantage of the Compaq Insight Manager XE MIB database. The user is allowed to search the MIB database for a specific MIB and a specific MIB variable. DTM will look for the variable in that MIB definition and provide the user with the corresponding OID. The MIB variable name can only be translated to its OID by DTM using the MIB database, provided the corresponding MIB has been previously compiled into the database using the SNMP Extensions Toolkit. The DTM graphical client also allows the user to query a user specified target device using SNMP or DMI to determine or verify suitable rules and corresponding values. Some devices are both SNMP- and DMI-compliant. Positive identification using SNMP takes precedence over DMI. That is, if DMI cannot identify a device, the SNMP device information is applied.

Before You Begin

Use the following guidelines to configure your environment: Be familiar with SNMP and DMI protocols. You should understand how SNMP and DMI work on your systems. Appendix A contains a brief overview but is not intended to be a complete explanation of the behavior of these protocols. These protocols are described in numerous documents published by the respective industry consortiums that devised them. The IETF (Internet Engineering Task Force) and the DMTF (Distributed Management Task Force) continue to support these protocols. Install SNMP and set up SNMP services and trap destinations on the managed devices and the management server. Without SNMP service running, you may not discover a device and you cannot get responses to requests of SNMP devices. Consult the user documentation for your operating system for complete instructions. Make sure that DMI has been configured on those devices that are to be used with DMI. This is the obligation of the vendor. Also check that one or more MIFs reside on the system. For example, the Win32sl.MIF may be found on desktop devices using Intel processors. Make sure DMI is running as a service on those devices to be identified using DMI. The DMI service must be running for requests and responses to be communicated. If these devices also support SNMP, disable the SNMP, if possible, to ensure DMI identification resolution. Use the SNMP Extensions Utility to register (compile) the MIBs that support devices you are adding to your network. Registering the MIB assures you of receiving and interpreting as much information as possible about the device. To learn more about registering MIBs, read the document Compiling MIBs in Compaq Insight Manager XE Using SNMP Extensions (175759-1). DTM operates under basic Windows NT user security in command line mode and within Compaq Insight Manager XE client authentication when running as part of the Compaq Insight Manager XE client. DTM is available only to users with Administrator privilege from within the client.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

Register the MIBs for any third party devices on your network. Registering associated MIBs with Compaq Insight Manager XE allows you to reference that MIB when defining SNMP based rule sets.

CAUTION: Use either the DTM graphical user interface or the DTM command line to access a specific database. Do not use the programs simultaneously.

When Can Identification Be Modified?

Device Type Manager does not modify the identification of most Compaq devices that are identified using SNMP. Agents running on the devices base the identification of these devices on resident MIBs and values returned. The identification process continues to interrogate a device until the device answers the questions in a rule set in a manner consistent with the associated compare rule. The questions and responses are based on either SNMP or DMI rules in each specific case but not both. If a rule is visible using DTM, it can be modified or deleted using DTM. All rules that are inserted using DTM can be modified or deleted using DTM.

Using Device Type Manager

DTM is installed as part of the Compaq Insight Manager XE V2.0 server system. DTM provides a choice of interfaces: A command line interface that is run directly from the command line. This interface is the one-third party developers will find most useful. A graphical interface that is run from the Compaq Insight Manager XE V2.0 client under the Tools category of functions. This interface provides you with a convenient mechanism to fine tune device identification in your environment by allowing you to add a new product category with minimal input, modify a product category, or delete a product category. This client interface is available to Administrators only.

Using the Graphical Interface

You can perform the following DTM operations from Compaq Insight Manager XE V2.0 client: Add a new product category for those devices whose identification can be modified. Modify an existing product category for those devices whose identification can be modified. Delete a product category. Create a URL link to be displayed on the Device page for devices identified in the Links area when this device is a member of this category. The prefix http:// is not needed. The tokens $ipaddress, $address and $hostname are available. The default is $ipaddress, which you do not need to enter. These tokens are replaced with the corresponding value for the specific device shown on the device page that displays this URL link.

The opening page of DTM is used to select a Product Category and then act on it by adding to it, editing the existing information, or deleting it from the database. The Device Type field is used to filter the product category name list.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

Creating New Device Categories

Product names can be composed of alphanumeric characters or space characters only. You begin creating a new category by selecting a device type or product name or a protocol, depending on your objective. If the device category to be added is new to the database, choose New and the protocol that will be used to communicate with it. If you intend to use part of an existing product name to create a new category with a similar product name, select the product name, but not the device type. The product name acts as a template for creating the new product name If you want to choose from product names that are already associated with a device type, select the device type and/or a product name and modify the product name as necessary.

To create a new product category: 1. From the toolbar, click on Tools. 2. From the menu, select Device Type Manager. 3. In the Device Category Information box, select a device type to filter the product names that are associated with the device type. You can also select a product name if you plan to create a new name using it as a template (within the restrictions of identification of Compaq devices). 4. Click New to create a new device identification rule. If you have not selected a product name, you are prompted to select a management protocol. Select the appropriate protocol, which opens the Add page for the protocol you selected.

Figure 1: The Device Type Manager Page.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

10

Adding a New SNMP Device Category

To add an SNMP rule set that identifies SNMP devices, select SNMP as the protocol, and the Add page for SNMP devices will open. See Figure 2. To complete the rule set for the device, you would need the following information: Community string. The community is the authentication for establishing communication between the management server and the target device. If the strings do not match, the target device will not respond. Target IP address. This is the IP address of the device that will be identified by the new rule set or a similar device. In this case, similar means having one or more characteristics in common with the target device so identification will be the same for both. MIB variable OID. You may already know this value if you also know the name of the MIB and the variable. You can simply enter the OID if you know it. If you do not, use the Get button to retrieve it. Expected response values. Know the actual value and data type of the value you anticipate as a response. The value can be specific, such as Hardware or it can be any value, including a NULL value. For SNMP devices, only string and integer data types are returned. For DMI devices, only strings are returned.

Figure 2: The Add Page for Device Type Manager

1. On the Add New SNMP Category page, complete the following fields: a. Select a Device Type is one is not yet selected. b. Enter a Product Name or change the Default name (When used by a Template having Device type and Product Name selected when creating a New DTM Rule). c. Specify a priority for the rule set if it is not the default of one (1). d. Enter a launch URL to be shown on the device links field on the device page if needed.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

11

2. Enter the System Object Identifier in a number dot format. You may know the SysOID for the target device. If you do not, use the Get assist tool button to query a specific target node for its SysOID. Figure 3 illustrates the Get Device Response for this OID page. a. Enter the community string if it is not the default "public." b. Enter the IP address of the target device. c. Click Get Value. If the device is found, the correct SysOID is entered in the field. Click Apply to transfer the value to the Add page.

Figure 3: Get Device Response for this OID Page.

Figure 4 shows the Get Device Response to this OID page with the value transferred.

Figure 4: Get Device Response to this OID with retrieved sysOID.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

12

3. On the Add page continue building the rule set by specifying additional criteria using MIB variables. Assuming that you do not know the MIB variable OID, click the MIB Variable OID Get button. See Figure 2. The Get SNMP Object Identifier page opens, as shown in Figure 5,. Select the MIB Definition File Name and variable and click Get Object ID. The OID is returned. Click Apply to transfer it to the Add page.

Figure 5: Get SNMP Object Identifier Page

4. On the Add page, click the Object Value Get button to get the value of the MIB variable on the target device. The Get Device Response to this OID page opens, but has a different purpose than earlier. Because DTM knows the device, the value retrieved is the value for the MIB OID on this device. This value will be specific. For example, for the sysDescr value might be "Hardware: x86 Family 6 Model 7 At/AT" See Figure 6. 5. Select a data type. The type must match the variable data type in the MIB. Note that only String and Integer are supported. 6. Select the appropriate comparison rule. This is your choice of value testing, based on the response you expect. 7. Click the Add button to create the new product category. A successful add operation will result in the device being displayed using the new identification after the next discovery and identification task runs. 8. Click Clear to clear the screen to default values or click Cancel to return to the opening screen without executing a change.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

13

Figure 6: Completed Page for New SNMP Device Category

Adding New DMI Device Categories

To add a DMI rule set that identifies DMI devices, select DMI as the protocol follow your selection of DMI device type and product name from the main page of DTM. The Add page for DMI devices will open.

Figure 7: The Add New DMI Device Category Page.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

14

To complete a rule set for a new DMI product category, you need the information from a MIF for the device. Table 2 describes the constituents of the elements that you specify in the rule set. You can specify up to three elements.
Table 2. DMI Element Constituents
Element Constituent Component Name Group Class Value The MIF on the system or an asterisk (*) to represent any MIF in place on the system. The name of the group class from the MIF. For example DMTF|ComponentID is a group class. You must be familiar with a specific MIF to get the correct Group Class name. The name of a second group constituent of the Class. For example, DMTF|Processor or DMTF|Filter Information are "same" group class names in DMTF|ComponentID. The name of a characteristic identified as an Attribute in a MIF. Examples are Manufacturer or Version Number in the Win32sl.MIF. Use the default of zero unless you are familiar with DMI indices.

Same Group Class

Attribute Index

You will also need the IP address of the target device or a similar device that will be identified by the new rule set. As with SNMP devices, choose a Device Type or Product Name based on your objective of creating a new category or modifying the device type and/or the product name. To complete the new DMI product category 1. On the Add New DMI Category page, complete the following fields shown in Figure 7: a. Device type. b. Product Name. c. Priority Note: The default priority for the rule set is 1. Enter a different priority if the default value will not be used. d. URL Launch Note: If needed, enter a launch URL to be shown in the Device Links field on the device page. If you leave the field blank, the default URL is used. 2. Enter the DMI elements for one to three elements. Select the Get button for each element you create. 3. On the Get DMI Element Value page, shown in Figure 8, complete the following steps: a. Enter the component name, group class, same group class, and attribute from the device MIF. You can use a wildcard for all entries except the attribute. Use the index default of zero. b. Enter the IP address of the target device. c. Select the Get Value button to retrieve a value. d. Select Apply to transfer the DMI elements and values to the Add page. You must specify at least one element and value. The results of the previous steps are shown in Figure 9.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

15

Figure 8: Get DMI Element Value Page.

Figure 9 shows the response for the value on the target device.

Figure 9: Get DMI Element Value Page and Response.

4. DTM displays the elements on the Add page by separating the constituents with a caret (^) for readability only. For example: Compaq PC Systems MIF ^ DMTF|ComponentID ^ ^ Manufacturer ^ 0 5. For each element, select the appropriate comparison rule. Note that only string is supported. 6. Click the Apply button to create the new product category. Click Clear to clear the screen back to the default values or click Cancel to return to the opening screen with no change. Figure 10 illustrates the added DMI category and rule set.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

16

Figure 10: Add New DMI Category Rule Set with Two Elements Defined.

Editing Device Categories

To edit a product category, select a Product Name from the main page of DTM (see Figure 1) before selecting Edit. If the device type is known, select it first to filter the product name list. 1. From the toolbar, click on Tools. 2. Select the desired Product Name from the drop down list. If the device type is known, select it first to filter the product name list. 3. Click Edit. 4. The information about the device is displayed. All fields that have entries are filled in as illustrated in Figure 11 for an SNMP device.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

17

Figure 11: An Edit Page for a Device Category.

5. Modify any editable fields that you want to change. Grayed fields cannot be edited. 6. Click Apply when all changes have been made. Select Cancel to return with no change.

Deleting Device Categories

To delete a product category, select a Product Name from the main page of DTM before selecting Delete. If the device type is known, select it first to filter the product name list. To delete 1. From the toolbar, click on Tool. 2. Select the desired Product Name from the drop down list. If the device type is known, select it first to filter the product name list. 3. Click Delete. 4. The information about the device is displayed. All fields that have entries are filled in. 5. Click Delete to execute the deletion.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

18

Using the Command Line Utility

The command line interface is intended for silent or expert installs, bulk loading, and support for other automatic processes such as SoftPaq. Command line syntax guidelines include: DTM can run as the standalone program DTMgr. It operates within the Compaq Insight Manager XE environment and must always be co-located with it. Move to the root directory of Compaq Insight Manager XE and type DTMgr from a console application shell. It cannot be moved from its home directory, as it needs support from other XE components. The parameter list can be specified as a single parameter on the same line as the DTMgr command or as lines in a file. If a file is used, DTMgr is launched with the f command that has a fully qualified path and file name as its argument. The DTMgr parameter list must be enclosed in double quotes. It is a single string. DTMgr provides its list of commands and arguments when typed with no parameter or with -? as a parameter otherwise it is always qualified with commands and command-argument pairs. Separate commands and arguments with the space character as a delimiter. Specifically, a command is prefixed with a dash ( - ) followed by one or two command characters followed by a space, followed by the argument for this command. There is no significance in the order in which commands appear on the command line. The argument for a command must follow the corresponding command. Product names and other parameters can include space character

To use the command line DTM utility: 1. From the desktop, click on Start. 2. Select Programs. 3. Select Command Prompt. 4. At the prompt, change to the root directory of Compaq Insight Manager XE 2.0 using a command shell line, for example: >cd \Compaq Insight Manager XE V2.0. 5. At the prompt, enter the DTMgr command and the appropriate parameter list. The following tables list and describe the switches, commands, and arguments for SNMP and DMI rule sets.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

19

Table 3. DTMgr Command Line Switches

Switch -D -v, V Function Debug mode. This switch enables DTM to display full detail as the command line is processed. Enabling Debug mode also enables Verbose mode Verbose mode. Verbose mode is the normal conversation mode of DTM. This switch enables DTM to display normal detail (but far less than Debug) as the command line processing continues. Verbose mode is also enabled by Debug mode Quiet mode. DTM is silent. Quiet mode turns off Verbose and Debug modes.

-q, Q

Table 4. DTMgr Commands with No Arguments

Command -c, C Function Check command. Instructs DTM to check the complete database looking for: Non-Unique names across both DMI and SNMP Non-Unique rule sets Incorrect priority assignment

Table 5. Common DTMgr Commands and Corresponding Arguments

Command and Argument -f, F -a, A (record definition) Function File: Instructs DTM to look in the specified file for command lines, one full command per file line (line terminated with a NEWLINE). Add: Instructs DTM to add this record (as defined on this command line) into the appropriate database. The product name and rule set must be specified and must be unique. If the priority is not specified, the highest priority, one (1) is assumed. The priorities of all other rules sets are adjusted accordingly. Delete: This command instructs DTM to delete the product category indicated. The Product Name or the rule set can be used to identify the product category to be deleted. The product name is specified using the n command with the product name as an argument. When using the rule set as the record identifier, a full rule set specification is required. The link protocol must be included.

-d (note lower case only)

-e, E

Edit: Instructs DTM to make the changes indicated by the commands and arguments included in this command line. Product Name or Rule Set is specified to identify the rule set record to change. The product name is specified using the n command with the product name as an argument. When using the rule set as the record identifier, a full rule set specification is required. The link protocol must be included. Items that can be changed using edit including Priority, LaunchURL, compare rule and device type.

-l, L <Link Protocol>

Used to identify the rule set management protocol. The protocol is specified as an argument either as a string or integer: for SNMP use SNMP or the value 1; for DMI, the string DMI or the value 2. Used to specify the name of the product category. <Product Name> is specified as a string which may include SPACE character.

-n, N <Product Name>

t, T <Device Type>

Use this command to specify the Device Type. This command is optional. The default <Device Type> is server. <Device Type> can be specified as either an integer value or by its equivalent string name. e.g. t 1 or - t server

u, U <URL string> *

The URL string that is displayed in the device page, links section for that particular device. $HOSTNAME, $IPADDRESS or $ADDRESS can be used to generate a host independent launch specification that is completed when the link for a particular device is shown.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

20

These commands form the SNMP specific commands and corresponding arguments for SNMP rule set definition.
Table 6. SNMP DTMgr Commands and Arguments
s, S <SysOID string> Specify SysOID. An SNMP dot-number format ID string that specifies MIB II System Object ID. This command and argument are mandatory. Specify priority. The argument is a number that specifies the priority of this rule set in relation to other rule sets in the same SysOID family. If no priority is specified, a value of one is assumed (highest priority). The priority of all other members of this SysOID family will be adjusted accordingly. This priority bares no relation to the DMI rule set priority mentioned in the DMI section. This command and argument are optional. o, O The O command argument is enclosed by ( ). Each argument must include a MIB OID, value, data type specification and string compare rule specification. This command and argument are optional. .

-p, P <priority>

(<MIB variable OID string>, <MIB variable value string>, <MIB variable OID string> <MIB variable value string> <MIB variable DataType>

SNMP style dot-format OID string used to identify the user selected MIB variable This argument specifies the value this variable must have for the object to be identified as in this category. This argument is used to specify the data type for the specified variable value. It is specified as either a string or as an integer: String (or 1) Integer (or 2)

<MIB value string compare rule> *

Specified as of 5 compare rule types: StartsWith (or 1) implies that the condition is met if either string is fully contained by the other with the first character anchored. Contains (or 2) implies that the compare string is contained within the source string. The compare string will not match if it is longer or invalid string than the source string. Match or Exact (or 3) implies an exact match with strings of equal length and matching string. If one string is longer than the other, this compare will fail. EndsWith (or 4) implies that the condition is met if either string is fully contained by the other with the last character anchored. AnyValue (or 5) implies that the string compare will always succeed provided there is a response.

Example DTMgr Commands

In these examples, the edit command is being used to change the priority, device type, the launch URL, and the compare rule. The following command line uses all the arguments for the command.
> DTMgr t 5 s 1.1.2.2.4 o (1.1.2.3.4.5,Windy,String,AnyValue) p 5 e v u mymachine.com

The next command uses a named rule that includes arguments. > DTMgr t 5 n wind p 5 e v -u mymachine.com

175758-001

Compaq Insight Manager XE Device Type Manager Utility

21

These command lines are equivalent if wind is the name of the rule set defined in the first example. (Note that the OID compare rule is changeable without affecting the rule set definition). The commands in Table 7 are DMI specific commands.
Table 7. DMI DTMgr Commands and Arguments
-p, P <priority> Specify the priority. The argument is a number that specifies the priority for this rule set in relation to all other DMI rule sets. If no priority is specified, a value of one is assumed (highest priority). This priority bares no relation to the SNMP rule set priority mentioned in that section. This command and argument are optional. mn, Mn (<MIF component name>, <MIF group class name>, <MIF same group class name>, <MIF attribute name>, <MIF index value>, This is the command and argument for specifying a DMI MIF rule set. There can be up to 3 rules in the rule set and these are correspondingly entered as m1, m2 and m3 for rule set 1, 2 and 3 correspondingly. Rule set 1 must always be specified when creating a new rule set and similarly for rule set 2, if there are 2 rules. The rule set is enclosed in (), contains no spaces, and each component is separated from its neighbors using a comma. The element value is always assumed to be a string. All seven components must be specified as either a string or as NULL. <MIF element value>, This argument specifies the value this element must have for the object to be identified as in this category.

<MIF value string compare rule> *

Specified as: StartsWith (or 1) implies that the condition is met if either string is fully contained by the other with the first character anchored. Contains (or 2) implies that the compare string is contained within the source string. The compare string will not match if it is longer or invalid string than the source string. Match or Exact (or 3) implies an exact match with strings of equal length and matching string. If one string is longer than the other, this compare will fail. EndsWith (or 4) implies that the condition is met if either string is fully contained by the other with the last character anchored. AnyValue (or 5) implies that the string compare will always succeed provided there is a response.

The following example is a DMI command line that adds a record to the database. Commands must be on one line. (For legibility, the following example extends across two lines.) dtmgr -a -l dmi -p 1 -t workstation -n MyMachine -m1 (*,DMTF|ComponentID|*,DMTF|Processor|*,1,0,Compaq,anyvalue)"

175758-001

Compaq Insight Manager XE Device Type Manager Utility

22

Working Examples using the DTM Command Line

DTM includes help information that can be presented on demand on the command line as follows:
>C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>dtmgr
>C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>runtime\bin\jre -ms8m -mx750m cp lib\jgl3.1.0.jar;.;lib\swing.jar;lib\windows.jar;lib\msxml.jar; lib\activation.jar;lib\mail.jar compaq.Discovery.DTMgr.DTMgr Usage: (Version 1.16) ----Device Type Manager ( DTMgr ): -----------------------------The entire parameter string must be enclosed in double quotes when being passed directly on the command line. Parameter strings contained in DTM script files are not contained within double quotes. Switches Optional: -D Debug mode (includes Verbose mode) -v,V Verbose mode Must specify one of: -a,A Add -d Delete -e,E Edit Commands -c,C check database for unique names and rule sets.

Commands with arguments Must specify: -f,F File <full path and file name> -l,L <Link protocol> -n,N <Product Name> -t,T <Product Type> (as a code value or string name Optional: -p,P Specify name priority in case of multiple identities. -u,U Specify <default URL string> to associate with this type. SNMP:Mandatory -s,S SNMP:Optional: -o,O DMI:

<System Object Identifier, sysOID>

{<OID string>,<value string>,<data type>,<CompareRule>)

-m1,2,3 -M1,2,3 {ComponentName,GroupClassName,SameGroupClassName, AttributeName,Index,Value,CompareRule)

Must specify rule set 1, rule sets 2,3 are optional. CompareRule: StartsWith, Contains, Match or Exact, EndsWith, AnyValue. DATABASE ACCESS: --------------WARNING!!! Don't use this program when Maple is active. WARNING!!! C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>

175758-001

Compaq Insight Manager XE Device Type Manager Utility

23

Note the difference between -d for delete and -D for Debug mode. Nothing harmful should happen if you get use the wrong switch because -D is not a command and without any other command, the line will not have a valid command as required. Furthermore, if -d is intended as Debug, -d together with the intended command will result in the line failing, as it would have two commands specified. Two commands on a line are not allowed.

Seeing the Results of Adding an SNMP Rule Set

The following example shows how to add a new rule set using DTM to change how a device is categorized. On displaying the Query Result - All Devices Page, the node, tag, is not being identified well and has been assigned the device type unknown. It does not have an assigned Product Name.

Figure 12: Query Results before modifying device identification of the device tag.

The administrator of this network has decided to identify the device tag as a Server with the Product Name of VAX. This can be accomplished using either the DTM graphical interface or the command line. This example uses the command line method. As a first step, the administrator will have to identify the System Object Identifier used by this device, a name for the product category, and a device type.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

24

The resulting command line is:

DTMgr -a -l SNMP -t Server -s 1.3.6.1.4.36.2.15.1.6.1 -n VAX Server

Executing this command will result in a console dialog similar to the dialog in the following table. The command failed because spaces were used in the filename. DTM uses the space character as parameter delimiter and consequently, names with spaces must be enclosed within quotes. Note too that the entire DTM parameter is enclosed in double quotes. The command is then executed again after reducing the name to VAX and the rule set is successfully added to the database.
C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>dtmgr "-a -l SNMP -t Server -s 1.3.6.1.4.36.2.15.1.6.1 -n VAX Server" C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>runtime\bin\jre -ms8m mx750m cp lib\jgl3.1.0.jar;.;lib\swing.jar;lib\windows.jar;lib\msxml.jar; lib\activation.jar;lib\mail.jar compaq.Discovery.DTMgr.DTMgr "-a -l SNMP -t Server -s 1.3.6.1.4.36.2.15.1.6.1 -n VAX Server" Trying connection to database using property file: \config\database.props Database connection test successful for URL: jdbc:odbc:insight_db User: sa pwd: Database Machine: KDD3A Database Version: Microsoft SQL Server 6.50 - 6.50.258 (Intel X86) Aug 15 1997 19:06:08 Copyright (c) 1988-1997 Microsoft Corporation Database Driver: JDBC-ODBC Bridge (SQLSRV32.DLL) 1.1001 (03.70.0623) An argument was found when a command was expected at position: 9 C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>DTMgr "-a -l SNMP -t Server -s 1.3.6.1.4.36.2.15.1.6.1 -n VAX" C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>runtime\bin\jre -ms8m mx750m -cp lib\jgl3.1.0.jar;.;lib\swing.jar;lib\windows.jar;lib\msxml.jar; lib\activation.jar;lib\mail.jar compaq.Discovery.DTMgr.DTMgr "-a -l SNMP -t Server -s 1.3.6.1.4.36.2.15.1.6.1 -n VAX" Trying connection to database using property file: \config\database.props Database connection test successful for URL: jdbc:odbc:insight_db User: sa pwd: Database Machine: KDD3A Database Version: Microsoft SQL Server 6.50 - 6.50.258 (Intel X86) Aug 15 1997 19:06:08 Copyright (c) 1988-1997 Microsoft Corporation Database Driver: JDBC-ODBC Bridge (SQLSRV32.DLL) 1.1001 (03.70.0623) Success, added record VAX to the SNMP database. C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>

175758-001

Compaq Insight Manager XE Device Type Manager Utility

25

The following diagram shows the result of adding the new product category in the Query Results of All Devices.

Figure 13: Query Results after Modifying Identification of the device tag.

These results were displayed by performing discovery or running device identification task. The device is now identified with the product name of VAX and has a device type of server. DTM added the new identification information to the database immediately. The change will be reflected in the next run of or executing device identification task for the device.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

26

Using the Edit Command to Modify an Existing SNMP Rule Set

The following code shows the progress of using the Edit command to add a LaunchURL to the record. In this case, the administrator wants to add a link, for example, which allows the LaunchURL link in the Links section on the page for a specific device to launch to the agent home page for the device being shown. The $ipaddress macro will be replaced with the actual IP address for the device being shown when the link is executed by clicking on it.
C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>DTMgr "-e -l SNMP -n

VAX -u $ipaddress:2301"
C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>runtime\bin\jre -ms8m

-mx750m -cp lib\jgl3.1.0.jar;.;lib\swing.jar; lib\windows.jar;lib\msxml.jar;lib\activation.jar;lib\mail.jar compaq.Discovery.DTMgr.DTMgr "-e -l SNMP -n VAX -u $ipaddress:2301" Trying connection to database using property file: \config\database.props Database connection test successful for URL: jdbc:odbc:insight_db User: sa pwd: Database Machine: KDD3A Database Version: Microsoft SQL Server 6.50 - 6.50.258 (Intel X86) Aug 15 1997 19:06:08 Copyright (c) 1988-1997 Microsoft Corporation Database Driver: JDBC-ODBC Bridge (SQLSRV32.DLL) 1.1001 (03.70.0623) Success, edited record VAX in the SNMP database.
C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>

175758-001

Compaq Insight Manager XE Device Type Manager Utility

27

Using the Delete Command to Remove an SNMP Rule Set

The following code shows the progress of using the Delete command.
C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>DTMgr "-d -l SNMP -n

VAX" d:\maple>runtime\bin\jre -ms8m -mx750m -cp lib\jgl3.1.0.jar;.; lib\swing.jar;lib\windows.jar;lib\msxml.jar; lib\activation.jar;lib\mail.jar compaq.Discovery.DTMgr.DTMgr "-d -l SNMP -n VAX" Trying connection to database using property file:\config\database.props Database connection test successful for URL: jdbc:odbc:insight_db User: sa pwd: Database Machine: KDD3A Database Version: Microsoft SQL Server 6.50 - 6.50.258 (Intel X86) Aug 15 1997 19:06:08 Copyright (c) 1988-1997 Microsoft Corporation Database Driver: JDBC-ODBC Bridge (SQLSRV32.DLL) 1.1001 (03.70.0623) Success, deleted record VAX from the SNMP database.
C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>

Running a discovery and identification task again will reveal that the device tag has reverted to the type unknown.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

28

Using the Add Command to Add a DMI Rule Set

The following example shows how to add a new DMI rule set. The administrator of this network has decided to have the device MyTag identified as a Workstation with the Product Name of MyMachine. As a first step, the administrator will have to identify the DMI reference element supported by this device, a name for the product category, and a device type. The resulting command line, which would be on one line at the command prompt, is as follows: dtmgr -a -l dmi -p 1 -t workstation -n MyMachine -m1 (*,DMTF|ComponentID|*,DMTF|Processor|*,1,0,Compaq,anyvalue)" Where -a is for add, -l specifies a DMI based rule set, -p specifies priority, -t specifies the device type, -n specifies the product name, and -m1 specifies a DMI element rule set. A minimal requirement to add a new DMI rule set that accepts all default values, including the device type as server is: dtmgr -a -l dmi -n MyMachine -m1 (*,DMTF|ComponentID|*,DMTF|Processor|*,1,0,Compaq,anyvalue)"

175758-001

Compaq Insight Manager XE Device Type Manager Utility

29

Executing this command will result in a console dialog similar to the dialog in the following table.
C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0> d:\maple>dtmgr "-a -l dmi -p 1 -t workstation -n MyMachine -m1 (*,DMTF|ComponentID|*,DMTF|Processor|*,1,0,Compaq,anyvalue)" d:\maple>runtime\bin\jre -ms8m -mx750m -cp lib\jgl3.1.0.jar;.;lib\swing.jar;lib\windows.jar;lib\msxml.jar;lib\activation.ja r;lib ail.jar compaq.Discovery.DTMgr.DTMgr "-a -l dmi -p 1 -t workstation -n MyMachine -m1 (*,DMTF|ComponentID|*,DMTF|Processor|*,1, Compaq,anyvalue)" Trying connection to database using property file: \config\database.props Database connection test successful for URL: jdbc:odbc:insight_db User: sa pwd: Database Machine: KDD3A Database Version: Microsoft SQL Server 6.50 - 6.50.258 (Intel X86) Aug 15 1997 19:06:08 Copyright (c) 1988-1997 Microsoft Corporation Database Driver: JDBC-ODBC Bridge (SQLSRV32.DLL) 1.1001 (03.70.0623) Success, added record MyMachine to the DMI database. C:\Program Files\COMPAQ\Compaq Insight Manager XE 2.0>

Editing and deleting rule sets from the DMI database is done in exactly the same manner as illustrated earlier for SNMP. Specify the following items: -e for edit or -d for delete, the rule set name, the management protocol, and the items to change or add.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

30

Appendix A: Compaq Insight Manager XE Identification

Discovery
Automatic discovery is based on a ping spray. An ICMP echo request command or ping is sent to each address in the permitted address space. A response from the addressed device results in the creation of an object for the newly discovered device in the database, which in turn, launches an identification thread to determine the identity of that discovered device. Each discovered device identification thread runs independently of all others. When a user-started Automatic Discovery indicates it has completed, it has only completed the ping spray portion of the process. Most likely, the individual identification threads have not finished their progress. There is no clear indication from Compaq Insight Manager XE when all the identification threads have completed. Viewing all or selected device objects after a userstarted Automatic Discovery may not show a completely accurate picture. Each device object may remain in a transient state of identification. That is, some devices may have type UNKNOWN FullStop However, after some time, will change to something else.

Transient Identification States

Newly discovered devices first enter the initial identification of type UNKNOWN with no name assigned. If the device supports SNMP and is not identified using SNMP, it enters the next transient state where the type assigned is OTHER and the name is the name returned from the device or IP address of the device and Product Name is assigned as unknown SNMP Device. If DMI is supported and enabled, the device identification may change from unknown SNMP Device accordingly to the DMI identified Product Name. If not, then this transient state becomes the final state. If a device is recognized as a Compaq device but is not fully identified, for any reason, the product name assigned is Unknown Compaq SNMP Device. If the device was partially recognized as a desktop, the type remains DESKTOP. If the device was partially recognized as a server, the type becomes SERVER. If the device was not recognized enough to distinguish SERVER from DESKTOP, it is assigned type OTHER. These are the transient identification states if DMI is enabled and supported. If DMI fails, this becomes the final identification.

SNMP and DMI Precedence

If SNMP and DMI are both enabled, successful SNMP identification always takes precedent over DMI. If a device is identified based on SNMP responses, DMI identification is not run, whether or not it is enabled. SNMP identification first attempt to fetch: 1. SysObjectId 2. SysName 3. SysUptime If this fails with every user-provided community string, SNMP identification fails and the object is left as type Unknown and the name is set to NULL string. DMI identification is then used if DMI is enabled. If DMI also fails, the type is left as Unknown and the name is set to NULL string.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

31

If this succeeds, Compaq Computer identification is attempted. If Compaq identification succeeds, identification will then check to see if DMI is supported on the device and will then, update the device info with the product type and product name information. If Compaq identification does not identify the device, third party rules are checked. Third party identification assigns the identity with the highest priority if there is more than one match. If third party identification succeeds, identification will then check to see if DMI is supported on the device and finally, update the device information with the product type and product name information. If there is no match using third party rules, the device is marked as type OTHER and product named Unknown SNMP Device. DMI identification then proceeds if: 1. DMI is enabled 2. SNMP is enabled and SNMP identification fails 3. SNMP is enabled and SNMP identifies object as Unknown SNMP Device, Unknown Compaq SNMP device, or Type UNKNOWN There are three steps in DMI identification. First, DMI identification looks for a match with one or more third party DMI rule sets. If third party identification succeeds, identification terminates and the device information is updated. If the device is not identified using third party rule sets, identification using hard-coded rules based on the Compaq Systems MIF is tried. Finally, if identification fails using the Compaq MIF hard-coded checks, generic MIF queries are issued. If the initial SNMP get of the sysName, sysOID and sysUpTime fails on any of these three variables on all attempts with all community strings, the SNMP identification is abandoned and the existing object identity is not changed. In general, if an SNMP get fails by returning a NULL value or a time out error, SNMP identification of this device is assumed to be invalid and is abandoned.

SNMP Identification
Identification loops while trying to retrieve SysObjectId, SysName SysUptime

with each user defined community string. If there is an error in fetching any one of these values for any reason including Time Out, for all known values of community string, SNMP identification fails and the identification of the device is not changed via SNMP. If there is no error, the device name is set to the value returned as the SysName. The device is also marked as SNMP enabled.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

32

Compaq Rules
We then check for Compaq Computer MIB cpqHoMibStatusArray (OID 1.3.6.1.4.1.232.11.2.10.1) variable on the target device. If the MIB is present and responds with a value, the process of identifying using Compaq rules continues otherwise we move on to checking the third Party rules. If the response value is NULL, the object is labeled as type OTHER, product name as Unknown SNMP Device. From the cpqHoMibStatusArray value response, characters at index 4,5 ( 0 based) which represents the second Octet (System Flags) in the response string are converted to an integer. If the least significant bit is 1, the object is a desktop and is running the Desktop Management agents, and the product type is correspondingly set to DESKTOP. If it is 0, the object is a Server and the product type is set to SERVER. All other possible values are considered as not valid.

Compaq Desktop
Get the cpqProductName (OID 1.3.6.1.4.1.232.2.2.4.2) variable from the device. If the response is NULL or there is a Time Out, SNMP identification is cancelled, as the result may not be correct at this time. If there is a NOSUCHNAME error response, identification is set to indicate an error to allow third party SNMP identification to have a go next. If the returned value is NULL or NULL string, the product name is set to Unknown Compaq SNMP device and the type is left as DESKTOP. Otherwise, the product name is set to the product name response value and the type left as DESKTOP. From the cpqHoMibStatusArray value response, the presence of Compaq MIB ID 2 is checked to see if the device has form factor information. If it does, get product form factor (OID 1.3.6.1.4.1.232.2.2.2.2) variable from the device. If the response is NULL or there is a Time Out, SNMP identification is cancelled, as the result may not be correct at this time. If there is a NOSUCHNAME error response, identification is set to indicate an error to allow third party SNMP identification to have a go next as the MIB did indicate it should have this information. If the form factor is for a laptop (type 2 or 3) the device type is changed to PORTABLE.

Compaq Server
Get the cpqProductName (OID 1.3.6.1.4.1.232.2.2.4.2) variable from the device. If the response is NULL or there is a Time Out, SNMP identification is cancelled as the result may not be correct at this time. If there is a NOSUCHNAME error response, identification is set to indicate an error to allow third party SNMP identification to have a go next. If the returned value is NULL or NULL string, the product name is set to Unknown Compaq SNMP device and the type is left as SERVER. From the cpqHoMibStatusArray value response, the presence of Compaq MIB ID 2 is checked to see if the device has RIB information. If it does, get the RIB card type (OID 1.3.6.1.4.1.232.9.2.2.10) variable from the device. If the response is NULL or there is a Time Out, SNMP identification is cancelled, as the result may not be correct at this time. If there is a NOSUCHNAME error response, identification is set to indicate an error to allow third party SNMP identification to have a go next as the MIB did indicate it should have this information. If the rib response value is 2 or 3, the device type is changed to Management card.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

33

Third Party Rules

If the device does not respond when we then check for Compaq Computer MIB cpqHoMibStatusArray OID (1.3.6.1.4.1.232.11.2.10.1) or there was Compaq identification error, the object is then compare against the third party rules. or if the device has been previously identified as a cluster FullStop. The sysOID priority is checked. If highest (one), the identification has been determined and is done. If not, we need to check the remaining family members, that is, the rule sets extended with SNMP OID rules, until the highest priority match or priority 1 is found. The sysOID family and the SNMP OID family members are retrieved from the cached tables, one by one and the OID value is fetched from the device and compared to the expected value using the specified compare rule. If there is a match and the priority is one, we are done. If there is a match and the priority is not one, comparing continues until the highest priority match is found (and this may not be one). If there have been no SNMP Get NULL or Time Out responses during this process and a match has been found, object identity is updated with the highest priority matching type and name. If there is an error, SNMP identification does not update object identification information. If the discovered device has been previously identified as part of a cluster, SNMP identification does not update object identification information.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

34

DMI Identification
DMI checking includes: Confirmation that DMI is supported (on the discovered device); the DMI flag for the device on the XE server is then enabled. Application of the third party rules. Application of Compaq rules if third party rules fail to identify. Application of generic DMI rules if Compaq rules fail to identify.

Third Party Rules

The discovered object is queried with each rule set in turn. If the response matches the expected value for each rule in the rule in accordance with the compare rule, the match is noted. If the priority of the rule set is one, DMI identification is successful and complete. If one or more rule set matches have been found, the object will assume the highest priority identity.

Compaq Specific Rule Set

If object has not been identified using the third party rule set, the object is queried to see if might include the Compaq MIF as follows: Compaq PC Systems MIF ^ DMTF|ComponentID ^ ^ Manufacturer ^ 0 Compaq PC Systems MIF ^ DMTF|ComponentID ^ ^ Version Compaq PC Systems MIF ^ DMTF|ComponentID ^ ^ Product ^0 ^0

where the caret (^) used to distinguish the components of the MIF element. If the manufacturer (rule1) includes the word Compaq, a Compaq Computer object is assumed. If the version (rule2) response includes the word Deskpro, the product name assigned is the version response string. If it does not include this string, the product response string is examined. If the product response string is longer than 5 characters in length, the product name assigned is the product response string. If it is 5 or less characters in length, the product name assigned is Compaq client. If the product name assigned includes the strings server (case insensitive) or ProLiant, the type is marked as SERVER. If the product name assigned includes the strings laptop, notebook or portable, the type is marked as PORTABLE. Otherwise, the type assigned is DESKTOP. If the DMI query response is NULL or the manufacturer does not include the word Compaq, there is no Compaq specific rule set match.

Generic Rule Set

If object has not been identified using the Compaq rule set, the object is queried for its responses to the generic query based on the rule set: * ^ DMTF|ComponentID|* ^ DMTF|Processor|* ^ Product ^ 0 * ^ DMTF|ComponentID|* ^ DMTF|Processor|* ^ Version ^ 0

175758-001

Compaq Insight Manager XE Device Type Manager Utility

35

If the response to the DMI query is not NULL, the individual responses are examined. If the response to rule 1 is not NULL, it is checked to see if the response value matches any of the following strings: Portable Personal Computer Notebook Personal Computer Desktop Personal Computer Tower Personal Computer Mini-tower Personal Computer Rack-mount Personal Computer Small Form Factor Personal Computer Personal Computer

If it matches any of these strings, the product type is set to DESKTOP. This product name match checking attempts to find legacy DMI devices that do not follow the DMI naming standards. If the name does not match any of the above and the response is not a NULL string, the product name is still set to the response to rule1. However, the response is also examined for several key words to determine the type as follows Type is set to SERVER if the word server is included in the name. The check is case insensitive. Type is set to DESKTOP if the word desktop is included in the name. The check is case insensitive. Type is set to PORTABLE if the any of the words laptop, notebook, portable are included. The check is case insensitive.

If the response to rule1 is a NULL or NULL string, and the response to rule2 is not NULL, the product name is set to the response to rule2. Again the type is determined in a similar fashion. If both the responses to rule 1 and rule2 is a NULL string, the device is not marked as identified and the responses are ignored. Regardless of the outcome of the generic rule check, a form factor check is made using the rule

^ DMTF|System Enclosure|* ^ ^ 1 ^ 0
If a valid response is received and the form factor matches NoteBook, Laptop or Portable, the product name is set to NoteBook, Laptop, or Portable and the product type is PORTABLE. The object type and name are changed only if a positive match has been made in any of the DMI identification steps listed above.

175758-001

Compaq Insight Manager XE Device Type Manager Utility

36

Appendix B: Identification Flowcharts

Overall Logic of Identification

Figure 14: Overall Logic of Identification

175758-001

Compaq Insight Manager XE Device Type Manager Utility

37

SNMP Identification Logic

Figure 15: SNMP Identification Logic

175758-001

Compaq Insight Manager XE Device Type Manager Utility

38

SNMP Check for Compaq Device Identification Logic

Figure 16: SNMP Check for Compaq Device

175758-001

Compaq Insight Manager XE Device Type Manager Utility

39

SNMP Third Party Identification Logic

Figure 17: SNMP Third Party Identification Logic

175758-001

Compaq Insight Manager XE Device Type Manager Utility

40

DMI Identification Logic

Figure 18: DMI Identification Logic

175758-001

Compaq Insight Manager XE Device Type Manager Utility

41

DMI Compaq Identification Logic

Figure 19: DMI Compaq Identification Logic

175758-001

Compaq Insight Manager XE Device Type Manager Utility

42

DMI Third Party Identification Logic

Figure 20: DMI Third Party Identification Logic

175758-001

Compaq Insight Manager XE Device Type Manager Utility

43

Identification Logic to Check for Any DMI Response Using Any MIF

Figure 21: Identification Logic to Check for Any DMI Response Using Any MIF

175758-001