Use this configuration file as an import of nodes, interfaces, and services to OpenNMS by-passing several phases of discovery and capabilities polling. A node in OpenNMS is a network entity that is used to contain network interfaces and those interface's services. This optional attribute can be used to facilitate integration by making the key from the integrating DB available adjacent to the OpenNMS key. This optional attribute can be used to facilitate building node relationships. This optional attribute can be used to facilitate building node relationships. This optional attribute can be used to facilitate building node relationships. This optional attribute can be used to associate a node with a location. This optional attribute can be used to persist an asset value to the building column in the OpenNMS DB. This optional attribute can be used to persist an asset value to the building column in the OpenNMS DB. A network interface. This will be used to set a description field. Currently a calculation of (ifDescr | ifName | ifAlias) Set this optional value to 3 to indicate "testing". Any other value is ignored. This attribute is used by OpenNMS to control SNMP data collection. P - Primary interface. This is the "preferred interface used in data collection. S - Secondary interface. This interface meets all the qualifications to be a primary interface. N - Not a collectable interface. This is a manual setting controlled by the user. If the snmpStorageFlag is set to "all", then all interfaces not set to 'N' will be collected. If the snmpStorageFlag is set to "select", then all interfaces with 'P|S' will be collected. If the snmpStorageFlag is set to "primary", then only the interfaces set to 'P' will be collected. This element is defined outside of the interface element for future use where it is expected that services on other network entities will be able to be defined (i.e. networks, nodes and applications) This element is used to specify OpenNMS specific categories. Note: currently, these categories are defined in a separate configuration file and are related directly to monitored services. I have separated out this element so that it can be referenced by other entities (nodes, interfaces, etc.) however, they will be ignored until the domain model is changed and the service layer is adapted for this behavior. This element is used to specify an asset record attribute. This element is used to associated meta-data with a node.