Types of imported objects

Topology and CLI device-access objects imported from IP Availability Manager identifies the types of objects that are imported by Network Protocol Manager from IP Availability Manager. Network Protocol Manager imports the topology and CLI device-access objects in accordance to the dxa-am.conf file in the BASEDIR/smarts/conf/bgp|eigrp|isis|ospf directory.

Figure 1. Topology and CLI device-access objects imported from IP Availability Manager

Through the UnitaryComputerSystem class in the dxa-am.conf file, Network Protocol Manager imports routing devices that are running BGP, EIGRP, IS-IS, or OSPF services. Those devices may be physical routers, virtual routers that are implemented within physical routers or switches, or the following types of router cards in switches:

• Route switch module (RSM)

• Route switch feature card (RSFC)

• Multilayer switch feature card (MSFC)

  Through the UnitaryComputerSystem class in the dxa-am.conf file, Network Protocol Manager also imports switch devices that contain interface cards that are running BGP, EIGRP, IS-IS, or OSPF services.

  UnitaryComputerSystem is the parent class of Router and Switch. Router is the parent class of MSFC, RSFC, and RSM.

  IP Availability Manager discovers instances of the Router class and its subclasses, as well as instances of the Switch class. In turn, Network Protocol Manager imports the router and switch objects from IP Availability Manager, along with the network objects that are associated with the router and switch objects. Those network objects are identified in the dxa-am.conf file.

  Also, for instances of the classes that are preceded with “proxy” in the dxa-am.conf file, Network Protocol Manager subscribes to routing-protocol-relevant status updates for those instances from IP Availability Manager. Partial list of DXA configuration commands describes “proxy” and the other data exchange adapter (DXA) commands that are included in the dxa-am.conf file.

Table 1. Partial list of DXA configuration commands

Keyword	Value	Description
class	<remote class name>  [<local class name>] Example:class  IP	Identifies a class and the start of a class block that ends one line before another class block begins. A class block represents instances of a particular class and its subclasses, and contains all interested properties of those instances.
proxy	<remote class name>  [<local class name>] Example:proxy UnitaryComputerSystem	Same as “class” with the following additional behavior: For the specified class, all instances of the remote class will be instrumented locally. That is, the local server will continuously monitor the instrumented attributes or events of the class instances on the remote server, and reflect changes in the local objects as changes occur in the remote objects.
attr	<remote attribute name>  [<local attribute name>] Example:class  IPattr  DisplayName	Identifies the class attributes that are to be imported from the remote server.
rel	<remote relationship name>  [<local relationship name>] Example:class  IPrel  Underlying	Identifies the class relationships that are to be imported from the remote server.
ignoreclass	<subclass name> Example:class  IPignoreclass  DuplicateIP	Stops the import of instances of the specified subclass from the remote server.
in	<container class name>  <relation name>       [<instance name>] Example:class  UnitaryComputerSystemin  TopologyCollection  ConsistsOf  EIGRP-System	Directs the local server to import instances that are related to a remote container-type class. The example directs the local server to import only those device instances that are members of the EIGRP-System ConsistsOf relationship.
probe	<element type> Example:class  SNMPAgentprobe  EIGRP	Enables postprocessing scripts to be invoked from the local server whenever a new instance of the given class, with the specified element type, is created on the remote server.
conditionalprobe	<element type>  <method>  <remote attribute value>      <same local attribute value> Example:class  SNMPAgentconditionalprobe EIGRP getSystem      DiscoveredLastAt DiscoveredLastAt	Behaves the same as “probe” when a new instance of the given class, with the specified element type, is created on the remote server. In addition, for an existing instance, “conditionalprobe” compares the value of the specified attribute in the remote instance to the same attribute in the local instance. If the value has changed in the remote instance, the probe takes place even though this instance is not new.