Administrator Handbook Table of contents version française LinkedIn social network LinkedIn social network LinkedIn social network LinkedIn social network Share on social media

Building a Device View

A Device View shows the physical or schematic view of a network device front panel or rear panel.

To build the physical view for a network device, a router, a switch, a server, use the provided cliparts in EMF or WMF format. You could extend the clipart library and design your own cliparts from third party vector graphic software tools like Corel draw from Adobe or Visio from Microsoft.

Clipart of device template for building network devices are stored in card/devices, card/parts and card/connectors.

The /devices sub directory contains a sub directory for each hardware manufacturer. You find in it some of the main chassis and boards that are specific to a single manufacturer. We will add more cliparts in the future to provide more type of devices.

The /connectors clipart contains the usual connectors find on communication equipments.

connecteurs routeur

The /parts sub directory contains generic elements composing hardware devices, chassis of multiple sizes, generic daughterboard, power supply, fans, power switch, grid etc…

chassis router

In summary, to build a network equipment, you need a chassis, power supply, daughter boards (select them under the /parts clipart directory or try to find it in the device subdirectory. Then you add the connectors and build your interfaces. Finally you activate the interface or any object of the view.

In the following example, we will build a rear panel view of a Cisco Router 3640 with few network interfaces and add Active behavior to interface object.

Remark: The device element provided here have been realized with Microsoft Visio then saved under an emf format.

To create the Active View we open the Editor interface from the menu, option Tools the Edit Active View.

The editor asks you to load an existing Active View file, answer No. An empty view is displayed, do a File Save under a new name.

We drag and drop the clipart folder from the Object Navigator to the drawing window.

The Clipart File Selector is displayed. Reach the device subdirectory that contains the clipart file for your equipment.

Remark: We do not provide yet all the cliparts for all equipments. Send us mail to get specific equipments. We will try to provide you with templates.

In our example, we choose the cisco3640-chassis.emf File. This file represents an empty chassis.

We move the image in the upper left corner of the drawing window, size it to fit in the screen and jump to the process mode to see the overall view.

When done we could add the other interface and power supply.

We come back to the edit mode and repeat the preceding operation to import another clipart to the drawing.

We import the power supply from /devices/cisco/cisco3640-power.emf.

We import the power supply from /connectors/sectorswitch.emf.

We import the power supply from /connectors/prisesectors.emf.

For all this clipart we check the Hidden text option in their properties to remove the text under the clipart.

We add now the interface card of WIC type. This Interface are small daughter card that fit in an NM Card.

We import the WIC empty card from /devices/cisco/cisco3640-power.emf.

The first Interface is a WIC-1T with a Serial Port. We import the Serial Port from /connectors/scsi-5.emf. We move it to the WIC and move the WIC in the Slot of the 3640 chassis.

For each object do not forget to check the Hidden text and the No Polling border.

We get the following result:

The same operation could be done for each Interface.

We will create the NM-4T interface.

We import to the drawing window the /devices/cisco/cisco36xxnm.emf.

This is a template for the NM module that fit in 36xx router series.

We import the connector which is high density connector from /connectors/hdcisco.emf.

When we have one connector we could duplicate it with a copy paste.

We set them on the NM modules. Align them on their base, and space then evenly with a space across button.

Each used connector is then associated to a host and to a SNMP OID. We choose to test the operational status of the network interface by performing a SNMP request on the MIB 2-> Interface -> ifoperstatus object. The index of the interface is 3 in our example.

We create two actions in the list, the first one tests the value on the "up" keyword and colors the connector in red if it is different.

The second action colors in green by default

The object is immediately active after configuration (If the polling is started). Object that are not dynamic do not have a grey background by default.

The serial port IP address has a bad status and is red colored.

The final view with a populated router is given below as example.