Viewing Doors and Devices in the Hardware Tree View

The Device view in the Hardware Tree module displays a list of configured gateways, expansion modules, and other devices in a hierarchical tree, as shown in the figure below.

To open the device view, select Hardware Tree from the Doors menu. In the Hardware Tree window, select Device from the View menu. Controllers are listed by name (such as Cisco Gateway, EM-100 Controller, or Mx Controller) and represented by a blue icon, as shown in the following figure. Click the box next to the icon to expand the hierarchical tree and view the expansion modules and other devices associated with the gateway.

 

hardware_tree_detail_3.jpg

 

Note          Some devices, such as tamper inputs, fire sensors, and cameras, are not part of door configurations.

Tip          The names of all hardware tree elements are editable, including drivers, controllers, expansion modules, and door devices.

The following table describes the icons and drivers shown in the previous figure.

 

Type

Description

1

Site Location

Read-only. A site location corresponds to a single instance of an ICPAM database. It generally, but does not necessarily, correspond with a single geographical location, such as a building complex, building, or part of a building. Most installations of ICPAM only have a single database, and hence a single site location. Multiple locations are used in larger configurations, such as a company with offices in distant locations that have a separate ICPAM database at each office.

2

Driver Manager

Read-only. The Driver Manager enables ICPAM hardware and software drivers, such as the GW Driver, Identiv EM-100 Driver, Mx Driver, Automation Driver, Cisco VSM Driver, or the EDI Driver. The Driver Manager cannot be deleted.

Note:   If you disable the Driver Manager then all the drivers, doors, gateway controllers and expansion modules are also disabled. If you later re-enable the Driver Manager, then you need to manually re-enable all driver modules, gateways, doors, and expansion modules.

3

Access GW Driver

The Access GW Driver allows you to add controller hardware modules to the system configuration, and supports the additional expansion modules (reader, input and output) connected to a gateway. The Access GW Driver also manages the events and alarms generated by devices, modules, and gateways. The Access GW Driver is enabled by default.

Note:   The access controller driver is an example of a device driver. Device drivers enable software and hardware functionality. Additional device drivers include the Automation Driver, EDI Driver, and Cisco VSM Driver. Each of these drivers enables the functionality for that feature, and provides basic configuration settings. There can only be one instance of each driver.

4

Gateway Controller

A gateway is added for each controller device. The modules and devices configured on the gateway are listed below the gateway and include the gateway controller module, any expansion modules and the other devices attached to the module interfaces. The previous figure shows an example hardware tree with the gateways, expansion modules, and other devices.

To add a gateway to the configuration, right-click on the Access GW Driver and select New Gateway Controller.

5

Access Control Modules

Modules include the gateway, reader, input and output modules. Each configured module is listed under the controller, including the controller itself.

Note:   The gateway module is displayed by default. Expansion modules are displayed only if added to the configuration. For information and instructions to install modules, see the Cisco Physical Access Gateway User Guide. For instructions to configure modules, see System Configuration Settings .

6

Module Interface

Each module includes a set of interfaces for connecting door hardware and other devices. For descriptions of each module interface, see the Cisco Physical Access Gateway User Guide.

7

 Devices

Devices include hardware such as card readers and locks. Device configurations are applied using pre-defined templates, or for a specific interface. See System Configuration Settings and System Configuration Settings .

8

Identiv Driver

Devices associated with the EM-100 controller.

For more on this, refer to Modifying Identiv EM-100 Drivers.